IPR call reminder:
|
"I draw your attention to your
obligations under the 3GPP Partner Organizations' IPR policies. Every
Individual Member organization is obliged to declare to the Partner
Organization or Organizations of which it is a member any IPR owned by the
Individual Member or any other organization which is or is likely to become
essential to the work of 3GPP. Delegates are asked to take note that they
are thereby invited:
|
Antitrust policy Reminder:
|
"I
also draw your attention to the fact that 3GPP activities are subject to all
applicable antitrust and competition laws and that compliance with said laws
is therefore required of any participant of this TSG/WG meeting including the
Chairman and Vice Chairman. In case of question I recommend that you contact
your legal counsel. The
leadership shall conduct the present meeting with impartiality and in the
interests of 3GPP. Furthermore,
I would like to remind you that timely submission of work items in advance of
TSG/WG meetings is important to allow for full and fair consideration of such
matters." |
| AI | TD# | Type | Doc For | Subject | Source | Rel | Comments | e-mail_Discussion | Result |
| 0 | - | - | - | All Agenda Items | - | - | Docs:=0 | - | |
| 1.1 | - | - | - | Opening of the meeting | - | - | Docs:=0 | - | |
| 2 | - | - | - | Agenda | - | - | Docs:=1 | - | |
| 2 | S2-2208100 | Agenda | Approval | SA WG2 #153E Meeting Agenda | SA WG2 Chair | - | Approved | ==== Final Deadline ==== | Approved |
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#152E Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2208101 | Report | Approval | Auto-Generated Report of SA WG2 meeting #152E | SA WG2 Secretary | - | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=50 | - | |
| 4.1 | - | - | - | LS In for Info or potential action | - | - | Docs:=11 | - | |
| 4.1 | S2-2208114 | LS In | Information | Reply LS to CT WG3 on Data Reporting API | SA WG4 (S4-221118) | Rel-17 | Revision of Postponed S2-2208095 from S2#152-e. Noted | Yannick (Nokia): Nokia suggests to note this LS since there is no action for SA2. | Noted |
| 4.1 | S2-2208118 | LS In | Information | LS from CT WG4: Reply LS on PLMN ID used in Roaming Scenarios | CT WG4 (C4-224444) | Rel-17 | Revision of Postponed S2-2208099 from S2#152-e. Noted | Noted | |
| 4.1 | S2-2208119 | LS In | Information | LS from GSMA DESS: LS to 3GPP - Hosted SEPP | GSMA DESS (GSMA DESS LS to 3GPP SA3) | Noted | Peter Hedman (Ericsson) propose to note | Noted | |
| 4.1 | S2-2208120 | LS In | Information | LS from : LS reply to 3GPP SA6 on Clarification of Edge Node Sharing | GSMA OPG (OPG_103_Doc_03) | Noted | Magnus O (Ericsson) proposes to Note this LS | Noted | |
| 4.1 | S2-2208149 | LS In | Information | LS from RAN WG3: LS on NCR Solutions | RAN WG3 (R3-225253) | Rel-18 | Noted | Wanqiang (Huawei): proposes to note this LS as there is no action for SA2. Qian (Ericsson) agrees to NOTE the LS. | Noted |
| 4.1 | S2-2208166 | LS In | Information | LS from ETSI ISG MEC: LS reply to GSMA OPAG on E/WBI | ETSI ISG MEC (MEC(22)000430r2) | Noted | Magnus O (Ericsson) proposes to Note this LS | Noted | |
| 4.1 | S2-2208169 | LS In | Information | LS from IETF LPWAN WG: Liaison statement from the IETF LPWAN WG to 3GPP | IETF LPWAN WG (LS_from_IETF_1796) | Noted | Hannu (Nokia) proposes to note this LS as there is no action for SA2 right now. | Noted | |
| 4.1 | S2-2208154 | LS In | Action | LS from SA WG3-LI: Identifier availability for Lawful Interception during Inter-PLMN handover | SA WG3-LI (S3i220485) | Rel-18 | Response drafted in S2-2209207. Final response in S2-2209262 | Laurent (Nokia): Comments Chris (Vodafone) replies to Nokia. Draft LS response will be in S2-2209207. Chris (Vodafone) provides the draft LS response in S2-2209207. | Replied to |
| 4.1 | S2-2209207 | LS OUT | Approval | [DRAFT] Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover | Vodafone | Rel-18 | Created at CC#1. Response to S2-2208154. r00 agreed. Revised to S2-2209262. | Chris (Vodafone) provides the draft LS response in S2-2209207. ==== Revisions Deadline ==== Leo (Deutsche Telekom) supports to send the LS. ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209262 | LS OUT | Approval | Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover | SA WG2 | Rel-18 | Revision of S2-2209207r00. Approved | Approved | |
| 4.1 | S2-2208155 | LS In | Action | LS from SA WG4: Reply LS to SA2 on EVEX | SA WG4 (S4-221122) | Rel-17 | Noted | Yannick (Nokia): Nokia suggests to note this LS since there is no action for SA2. | Noted |
| 4.1 | - | - | - | Reply LS or CRs | - | - | Docs:=35 | - | |
| 4.1 | S2-2208123 | LS In | Action | LS from CT WG1: LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP accesses | CT WG1 (C1-225230) | Rel-18 | Response drafted in S2-2208376. Final response in S2-2209263 | Replied to | |
| 4.1 | S2-2208376 | LS OUT | Approval | [DRAFT] Reply LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP Access Type | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2208123. r00 agreed. Revised to S2-2209263. | Fei (OPPO) comments and provides r01 to drafts/revisions. Hannu (Nokia) cannot accept r01 as it is not available '403 forbidden: Access denied'. We need to see any revision that is proposed for the meeting. Fei (OPPO) provides links in revisions. Hannu (Nokia) thanks Fei for the link to r01 but can't agree the contents. Considering discussion on the related CRs (8377 - 8378), the original version is more correct. ==== Revisions Deadline ==== Fei (OPPO) indicates that the reply LS is linked to status of S2-2208377. ==== Final Deadline ==== Hannu (Nokia) agrees with Fei and Qianghua that the LS must reflect what was agreed in this meeting, so only agreed CRs can be attached. | Revised |
| 4.1 | S2-2209263 | LS OUT | Approval | Reply LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP accesses | SA WG2 | Rel-17 | Revision of S2-2208376r00. Approved | Approved | |
| 4.1 | S2-2208377 | CR | Approval | 23.501 CR3711 (Rel-17, 'F'): Emergency PDU session transfer | Nokia, Nokia Shanghai Bell, MediaTek, Google Inc., Ericsson | Rel-17 | r08 agreed. Revised to S2-2209264. | Jinguo(ZTE) provides r01 Fei (OPPO) comments and the CR is not needed. Hannu (Nokia) comments to Fei (OPPO) that CR on TS 23.501 is needed for sure, as the present SA2 text mandates rejecting completely valid emergency calls! Hannu (Nokia) agrees the comment from Jinguo and provides r02 with editorial change only. Haris(Qualcomm) asks questions for clarification Hannu (Nokia) answers to Haris and asks for clarification on the emergency call back requirements? Shabnam (Ericsson) provides comments to Qualcomm question Hannu (Nokia) responds to Shabnam Fei (OPPO) responds to Hannu (Nokia) Kundan (NEC) provides comments. Hannu (Nokia) provides r03 and replies to Fei and Kundan. Can also live with r02 which is also correct. Kundan (NEC) provides response to Hannu (Nokia). Fei (OPPO) comments and provides r04 Hannu (Nokia) answers to Kundan Kundan (NEC) responds to Hannu. Hannu (Nokia) provides r05 with the minimum change. UE impact cannot be avoided due to incorrect condition in the second paragraph. Fei (OPPO) provides comments. Hannu (Nokia) comments that both the general rule in clause 5.16.4.1 and its implementation in clause 5.16.4.9 are needed. Fei (OPPO) provides replies Qianghua (Huawei) comments Shabnam (Ericsson) CT1 is wrong and they are not stage 2 responsible and we must also align with 4G, CT4 etc. I understand you want to consider this for Rel-18, but we cannot accept messing up normal emergency calls being messed up for a corner case CT1 found. Simple soln follow existing principles. Jinguo(ZTE) comment Kundan (NEC) answers to Hannu Kundan (NEC) agrees with Huawei to keep both action. both actions are handling different situations. I explained the reason in my previous mail. Hannu (Nokia) provides r06 and answers the questions. Haris(Qualcomm) indicates that r06 is not acceptable Hannu (Nokia) agrees with Haris and provides hopefully less weird r07. Fei (OPPO) requests to untick the ME box. Kundan(NEC) provides the reference. states the abnormal case is well discussed in CT1 from Rel-9. ==== Revisions Deadline ==== Shabnam (Ericsson) prefers r03, can accept r00 and r07 and objects to other revisions. Fei (OPPO) can only accept r03 and objects to other revisions including r00. Hannu (Nokia) can also accept r03. Fei (OPPO) can only accept r04 and objects to other revisions including r00. Please ignore the previous incorrect version. Hannu (Nokia) asks Fei whether the UE that has got emergency PDU Session in one Access Type is allowed to request another emergency PDU session in the same Access Type. Yes or no? Shabnam (Ericsson) believes that the UE impact from stage 2 specification is unavoidable since we have conflicting text for 5G, which one UE should be compliant with if they are conflicting? Qianghua (Huawei) can live with r07. Prefer to untick the ME impacts. Hannu (Nokia) proposes to take this CR to CC in order to check which revision can be agreed. Fei (OPPO) replies to Hannu and can live with r08 which is based on r04 plus additional changes in the 2nd paragraph. Hannu (Nokia) thanks Fei. Kundan(NEC) can live with r08. Qianghua (Huawei) can also live with r08 if majority can accept Hannu (Nokia) thanks for supports and provides a copy of r08 in 'revisions' folder as suggested in CC #2 ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209264 | CR | Approval | 23.501 CR3711R1 (Rel-17, 'F'): Emergency PDU session transfer | Nokia, Nokia Shanghai Bell, MediaTek, Google Inc., Ericsson | Rel-17 | Revision of S2-2208377r08. Approved | Agreed | |
| 4.1 | S2-2208378 | CR | Approval | 23.502 CR3561 (Rel-17, 'F'): Emergency PDU session transfer | Nokia, Nokia Shanghai Bell, MediaTek, Google Inc. | Rel-17 | Noted | Fei (OPPO) comments Jinguo(ZTE) comments and the CR is not needed. Hannu (Nokia) thanks Fei (OPPO) for good comment and explains to Jinguo why the CR is needed and provides r01. Judy (Ericsson) asks how the CR is relevant to the emergency PDU Session transfer Hannu (Nokia) replies to Judy and provides r02 Qianghua (Huawei) shares the same views and provides more reasons why this CR is not needed Judy (Ericsson) checks if the intention is to align with stage 3 regarding deregistration notify due to duplicated PDU Session detected in UDM Hannu (Nokia) responds to comments and proposes to choose between the original version and r02. Judy (Ericsson) provides r03 to make an alignment with stage 3 Qianghua (Huawei) sustains the view ==== Revisions Deadline ==== Judy (Ericsson) propose to go with r03 which is pure stage 3 alignment not specific to emergency PDU Session, objects to other revisions (r00 included) due to incorrect reason for change. Hannu (Nokia) answers to Qianghua's question even though this discussion becomes irrelevant after r03 that aligns SA2 text with the one in 29.503. Hannu (Nokia) thanks Judy for good compromise and supports r03. Qianghua (Huawei) objects all revs including the original Judy (Ericsson) comments Jinguo(ZTE) comments that r03 has issues and is not agreeable. ask to postpone Hannu (Nokia) supports Judy and points out that all emergency PDU session aspects have been removed in r03 making it pure alignment with the existing stage 3 requirements. Hannu (Nokia) proposes to solve the editorial issues in r03 by re-using CR text from the original r00 and proposes the CR for CC. Late revision r04 shows the changes over r03. Qianghua (Huawei) sustains the objection, sorry to say that concerns are still not addressed Hannu (Nokia) answers to Qianghua and provides r05 to fully align with TS 29.503 hoping that such alignment is acceptable? ==== Final Deadline ==== Qianghua (Huawei) still objects given the reasons explained online and offline, sorry Hannu (Nokia) understand that the discussion with Qianghua is a wording issue and uses the wording from Qianghua in r06 | Noted |
| 4.1 | S2-2208125 | LS In | Action | LS from CT WG1: LS on starting a timer in RRC-inactive state | CT WG1 (C1-225319) | Rel-18 | Responses drafted in S2-2208305, S2-2208838. Final response in S2-2209265 | Replied to | |
| 4.1 | S2-2208305 | LS OUT | Approval | [DRAFT] Reply LS on starting a timer in RRC-inactive state | Huawei, HiSilicon | Rel-18 | Response to S2-2208125. r01 agreed. Revised to S2-2209265, merging S2-2208838 | Hannu (Nokia) has got no strong view on which LS to take as template (8305 or 8838) but suggests to attach CR 8837 and to shorten the LS. Haris(Qualcomm) provides r01 ==== Revisions Deadline ==== Hannu (Nokia) supports r01 but points out that this LS still depends on the approval of the CR in S2-2208837 (which is hopefully approved in this meeting) ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209265 | LS OUT | Approval | Reply LS on starting a timer in RRC-inactive state | SA WG2 | Rel-18 | Revision of S2-2208305r01, merging S2-2208838. Approved | Approved | |
| 4.1 | S2-2208838 | LS OUT | Approval | [DRAFT] Reply LS on starting a timer in RRC-inactive state | Qualcomm | Rel-18 | Response to S2-2208125. Merged into S2-2209265 | LiMeng (Huawei) suggests to merge into S2-2208305 Hannu (Nokia) has got no strong view on which LS to take as template but shows the way forward in r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 4.1 | S2-2208837 | CR | Approval | 23.501 CR3733 (Rel-18, 'F'): De-activation timer for eCall only mode UE in RRC_INACTIVE | Qualcomm Incorporated | Rel-18 | Approved | LiMeng (Huawei) has a question on the WID code. Haris(Qualcomm) responds to LiMeng re the WI code Hannu (Nokia) supports the principle but asks about the second change in the CR? ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 4.1 | S2-2208134 | LS In | Action | LS from CT WG4: LS on service operation used in AMF relocation in Inter PLMN handover procedure | CT WG4 (C4-224408) | Rel-17 | Noted | Hannu (Nokia) proposes to note the LS, assuming the CR related CR in S2-2208896 that carries out the SA2 action can be agreed. Qian (Ericsson) agrees to NOTE the LS. | Noted |
| 4.1 | S2-2208253 | CR | Approval | 23.502 CR3554 (Rel-17, 'F'): N2 HO service operation update | Ericsson | Rel-17 | Merged into S2-2209266 | Fenqin (Huawei) suggest to merge this paper to 8896. Qian (Ericsson) is ok to merge. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 4.1 | S2-2208896 | CR | Approval | 23.502 CR3587 (Rel-17, 'F'): Update service operation used in AMF relocation in Inter PLMN handover procedure | Huawei, HiSilicon | Rel-17 | r06 agreed. Revised to S2-2209266, merging S2-2208253 | Fenqin (Huawei) provides r01. Qian (Ericsson) provides r02. Jinguo(ZTE) provides r03. Hannu (Nokia) provides r04 to clean up the cover page. Fenqin (Huawei) provides r06 and ask ignore r05. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r06. Hannu (Nokia) supports r06. ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209266 | CR | Approval | 23.502 CR3587R1 (Rel-17, 'F'): Update service operation used in AMF relocation in Inter PLMN handover procedure | Huawei, HiSilicon, Ericsson, ZTE | Rel-17 | Revision of S2-2208896r06, merging S2-2208253. Approved | Agreed | |
| 4.1 | S2-2208130 | LS In | Action | LS from CT WG3: Reply LS on Traffic Identification within 5G Media Streaming | CT WG3 (C3-224556) | Rel-17 | Response drafted in S2-2208353. Postponed | Postponed | |
| 4.1 | S2-2208353 | LS OUT | Approval | [DRAFT] Reply LS on Traffic Identification within 5G Media Streaming | Ericsson | Rel-17 | Response to S2-2208130. r00 agreed. Revised to S2-2209258. Postponed | ==== Revisions Deadline ==== Mirko (Huawei) proposes to postpone the LS response. ==== Final Deadline ==== | Postponed |
| 4.1 | S2-2209258 | LS OUT | Approval | [DRAFT] Reply LS on Traffic Identification within 5G Media Streaming | Ericsson | Rel-17 | Revision of S2-2208353r00. WITHDRAWN | Withdrawn | |
| 4.1 | S2-2208354 | CR | Approval | 23.502 CR3431R2 (Rel-17, 'F'): Traffic Identification using ToS/TC for 5G Media Streaming | Ericsson | Rel-17 | Revision of (Postponed) S2-2203843 from S2#151E. r03 agreed. Revised to S2-2209267. Postponed | Judy (Ericsson) responds to Dan(China Mobile) Dan(China Mobile) provide suggestion for updating the NOTE Dan(China Mobile) reply suggestion Mirko (Huawei) comments. Judy (Ericsson) provides r01 and responds Dan (China Mobile) ok for r01 NOTE update Pallab (Nokia) shares the view with Mirko (Huawei) and questions whether we need to duplicate the information in TS 23.502 Judy (Ericsson) responds to Pallab (Nokia) and Mirko (Huawei). Mirko (Huawei) responds. Judy (Ericsson) responds to Mirko (Huawei) and provide r02 Pallab (Nokia) NOT OK with r02 Dario (Qualcomm) is not OK with r02 and provides r03. Judy (Ericsson) is fine with r03 and responds ==== Revisions Deadline ==== Mirko (Huawei) objects to the original version and all revisions and suggests to instead clarify those issues in 23.503 clause 6.1.3.6. ==== Final Deadline ==== | Postponed |
| 4.1 | S2-2209267 | CR | Approval | 23.502 CR3431R3 (Rel-17, 'F'): Traffic Identification using ToS/TC for 5G Media Streaming | Ericsson | Rel-17 | Revision of S2-2208354r03. WITHDRAWN | Withdrawn | |
| 4.1 | S2-2208133 | LS In | Action | LS from CT WG4: Reply to LS on VoLTE Roaming GBR Handling | CT WG4 (C4-224401) | Rel-17 | This LS was postponed | Postponed | |
| 4.1 | S2-2208158 | LS In | Action | LS from SA WG4: DRAFT Reply LS to 3GPP SA2 on VoLTE Roaming GBR Handling | SA WG4 (S4-221192) | Rel-17 | This LS was postponed | Postponed | |
| 4.1 | S2-2208504 | DISCUSSION | Discussion | Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming . | Vivo | Rel-17 | Noted | Judy (Ericsson) proposes to have the discussion in 9115 thread ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 4.1 | S2-2208606 | DISCUSSION | Discussion | Discussion paper for VoLTE GBR handling in roaming case | OPPO | Rel-17 | Noted | Judy (Ericsson) proposes to have the discussion in 9115 thread ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 4.1 | S2-2209115 | DISCUSSION | Decision | Avoiding a HPLMN request for a GBR greater than the VPLMN s value for IMS voice in home routed roaming. | Vodafone | Rel-17 | Noted | Judy (Ericsson) proposes to use this paper for further discussion for 9115, 8502, 8504 and 8606. Haris(Qualcomm) provides comments to the indicated papers Yang (OPPO) provides comments Rainer (Nokia) comments. Judy (Ericsson) comment Xiaobo (vivo) asks questions for clarification Chris (Vodafone) replies Xiaobo (vivo) asks further questions for clarification Chris (Vodafone) responds to Vivo's questions Xiaobo (vivo) provides some clarification and share understanding Chris (Vodafone) responds and suggests an outline for an LS to GSMA Leo (Deutsche Telekom) agrees with the proposal and the LS to be sent to GSMA Xiaobo (vivo) agrees with proposal from Chris (Vodafone) and supports to send LS to GSMA. Rainer (Nokia) is ok with a LS to GSMA. Yang (OPPO) is supportive of sending the LS to GSMA. And suggest to ask GSMA if they can define a recommended GBR value for the roaming case Chris (Vodafone) replies an comments EPS fallback and on the difficulty of a common value for TN and NTN Judy (Ericsson) is OK with LS to GSMA Haris(Qualcomm) is ok to send LS to GSMA but asks one question Rainer (Nokia) replies to Haris (Qualcomm). Haris(Qualcomm) responds ==== Revisions Deadline ==== Tao(VC) check the status of the proposed LS out to GSMA Chris (Vodafone) provides the draft LS in the drafts folder. Judy (Ericsson) provides an update to the draft LS in the drafts folder Rainer (Nokia) provides an update. Chris (Vodafone) replies. Chris (Vodafone) provides an updated draft. Chris (Vodafone) uploads that draft into inbox/revisions as S2-2210158. ==== Final Deadline ==== Haris(Qualcomm) provides r01 Chris (Vodafone) is OK with r01 | Noted |
| 4.1 | S2-2210158 | LS OUT | Approval | [DRAFT] Response to 'LS to 3GPP SA WG2 on VoLTE Roaming GBR Handling' | Vodafone | CC#4: r01 agreed. Revised to S2-2209969. | Chris (Vodafone) is OK with r01 Judy (Ericsson) provides r02 Rainer (Nokia) comments. Chris (Vodafone) does not agree with r02. Chris (Vodafone) puts a copy of 10158r01 into the CC#4 folder. | Revised | |
| 4.1 | S2-2209969 | LS OUT | Approval | Response to LS to SA WG2 on VoLTE Roaming GBR Handling | SA WG2 | - | Revision of S2-2210158r01. Approved | Approved | |
| 4.1 | S2-2208502 | CR | Approval | 23.501 CR3718 (Rel-17, 'F'): Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming | Vivo | Rel-17 | Noted | Judy (Ericsson) proposes to have the discussion in 9115 thread Rainer (Nokia) proposes to note 8502 at this meeting. Xiaobo (vivo) replies to questions from Rainer (Nokia) and propose to postpone this. ==== Revisions Deadline ==== Leo (Deutsche Telekom) proposes to NOTE the CR. Xiaobo (vivo) is ok to note the CR. ==== Final Deadline ==== | Noted |
| 4.1 | S2-2209140 | CR | Approval | 23.228 CR1257 (Rel-18, 'F'): IMS cross border mobility with Home routed IMS calls | Vodafone (S2-2205903 was Ericsson, Vodafone?, AT&T) | Rel-18 | Confirm Sources!. Affected clauses under revision history! r06 agreed. Revised to S2-2209268. | Rainer (Nokia) provides r01. Magnus H (Ericsson) provides r02 Rainer (Nokia) provides r03. Chris (Vodafone) provides r04. Rainer (Nokia) replies. Magnus H (Ericsson) comments. Leo (Deutsche Telekom) comments. Haris(Qualcomm) comments Chris (Vodafone) replies to Qualcomm Rainer (Nokia) comments. Rainer (Nokia) provides r05. Shabnam (Ericsson) provides comments that I don't believe this is Category F CR but rather Category C. So I propose to change to a Cat C please. Rainer (Nokia) provides r06. ==== Revisions Deadline ==== Antoine (Orange) comments that the WI code should be 'V8, TEI18', and asks why the 2 new procedures are specific to voice whereas the LS from SA3-LI did not mention voice. Chris (Vodafone) replies to Orange and Ericsson. To help MCC, he will change the WID name from S8HR to V8 during the CR clean up (3GU did not allow a search for 2 letter WID codes). ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209268 | CR | Approval | 23.228 CR1257R1 (Rel-18, 'F'): IMS cross border mobility with Home routed IMS calls | Vodafone, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2209140r06. Approved | Agreed | |
| 4.1 | S2-2208159 | LS In | Action | LS from SA WG5: LS on Reference point allocation to support charging services | SA WG5 (S5-225775) | Rel-18 | Response drafted in S2-2209199. Final response in S2-2209259 | Replied to | |
| 4.1 | S2-2209199 | LS OUT | Approval | [DRAFT] LS reply on Reference point allocation to support charging services | MATRIXX Software | Rel-18 | Response to S2-2208159. r00 agreed. Revised to S2-2209259. | ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209259 | LS OUT | Approval | LS reply on Reference point allocation to support charging services | SA WG2 | Rel-18 | Revision of S2-2209199r00. Approved | Approved | |
| 4.1 | S2-2209200 | CR | Approval | 23.501 CR3752 (Rel-18, 'B'): Reference point numbers for charging | MATRIXX Software | Rel-18 | r01 agreed. Revised to S2-2209347. | Antoine (Orange) comments that the WI code should be MMS_CH_SBI, and wonders whether it's worth spending efforts allocating RP numbers... Gerald (MATRIXX Software) followed the given guidance and provides r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 4.1 | S2-2209347 | CR | Approval | 23.501 CR3752R1 (Rel-18, 'B'): Reference point numbers for charging | MATRIXX Software | Rel-18 | Revision of S2-2209200r01. Approved | Agreed | |
| 4.1 | - | - | - | Common issue CRs | - | - | Docs:=4 | - | |
| 4.1 | S2-2208396 | CR | Approval | 23.502 CR3562 (Rel-17, 'F'): Release of emergency PDU Session without data transfer for a period | Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 4.1 | S2-2209065 | CR | Approval | 23.501 CR3748 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon | Rel-17 | Noted | Antoine (Orange) comments that the WI code should be 'TEI17, 5GS_Ph1' like the CR that introduced this clause (CR#3507). Judy (Ericsson) questions FASMO aspect Laurent (Nokia): would a way forward be that this CR (and its companion) are agreed as R18 CR(s) ==== Revisions Deadline ==== Tao(VC) I see change proposal and way forward by Laurent. Any update/view from the author or co-source company on the way forward? ==== Final Deadline ==== | Noted |
| 4.1 | S2-2209067 | CR | Approval | 23.503 CR0757 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon | Rel-17 | Noted | Antoine (Orange) comments on WI code and wording. Judy (Ericsson) proposes to discuss in 9065 thread Laurent (Nokia): would a way forward be that this CR (and its companion) are agreed as R18 CR(s) ==== Revisions Deadline ==== Tao(VC) I see change proposal and way forward by Laurent. Any update from the author or co-source company on the way forward view? Laurent (Nokia): ok for me for R18 Judy (Ericsson) objects to this paper, and any enhancement in Rel-18 needs to be justified as commented previously in 9065 thread. ==== Final Deadline ==== | Noted |
| 4.1 | S2-2209191 | CR | Approval | 23.502 CR3601 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints | Peraton Labs, CISA ECD, AT&T, Verizon | Rel-17 | Noted | Antoine (Orange) comments that the WI code should be 'TEI17, 5GS_Ph1'. Judy (Ericsson) proposes to discuss in 9065 thread Jinguo(ZTE) fixes the title and provides comment Mirko (Huawei) provides r01. ==== Revisions Deadline ==== Judy (Ericsson) objects to this paper, and any enhancement in Rel-18 needs to be justified as commented previously in 9065 thread. ==== Final Deadline ==== | Noted |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=0 | - | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=0 | - | |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=0 | - | |
| 5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | Docs:=0 | - | |
| 5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | Docs:=0 | - | |
| 6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Docs:=0 | - | |
| 6.1 | - | - | - | General aspects, concepts and reference models | - | - | Docs:=7 | - | |
| 6.1 | S2-2208408 | CR | Approval | 23.501 CR3583R3 (Rel-17, 'F'): Clarification on Mapped NSSAI | Huawei, HiSilicon | Rel-17 | Revision of (agreed, but noted by TSG SA) S2-2202047 from S2#150E. Should be a revision of (Postponed) S2-2205700. r06 agreed. Revised to S2-2209558. | Josep (DT) asks for clarification why roaming mention in normative text is removed. Haiyang (Huawei) responds to Josep (DT). Genadi (Lenovo) provides question for clarification. Haris(Qualcomm) provides r01 Peter Hedman (Ericsson) provides r02 Alessio(Nokia) comments Alessio(Nokia) provides r03 Krisztian (Apple) provides r05. Genadi (Lenovo) provides r04. Peter Hedman (Ericsson) provides comments Alessio(Nokia) is ok with r05. Guillaume (MediaTek Inc.) provides r06 Alessio(Nokia) prefers r05 but can live with r06 Haiyang (Huawei) is ok with r06. Genadi (Lenovo) is fine with r06, but we prefer r05 to avoid repetition of Requested NSSAI. Peter Hedman (Ericsson) ok with r06 and r05 as they have at the end the same meaning ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 6.1 | S2-2209558 | CR | Approval | 23.501 CR3583R4 (Rel-17, 'F'): Clarification on Mapped NSSAI | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Apple | Rel-17 | Revision of S2-2208408r06. Approved | Agreed | |
| 6.1 | S2-2208762 | CR | Approval | 23.501 CR3729 (Rel-17, 'F'): Mapped NSSAI when UE is roaming | Ericsson, Qualcomm Incorporated | Rel-17 | Postponed | Haiyang (Huawei) provides r01 Peter Hedman (Ericsson) provides reply alessio(Nokia) provides r02 Krisztian (Apple) provides r03. Jinguo(ZTE) provides r04 Myungjune (LGE) provides r05. Peter Hedman (Ericsson) provides comments and r06 alessio(Nokia) is ok with r03. alessio(Nokia) objects to r05 and r04 alessio(Nokia) objects to r06 Guillaume (MediaTek Inc.) supports r06 Peter Hedman (Ericsson) provides comments and suggests to postpne the CR due to one company objection Alessio(nokia) rather suggests to approve r03 Peter Hedman (Ericsson) provides comments that r03 is not agreeble before CT1 provided feedback alessio(nokia) so really the reason why this is not approved is Ericsson objection to r03 technical content. ==== Revisions Deadline ==== Haris(Qualcomm) indicates that r03 is useless to solve the issue in reason for change Jinguo(ZTE) suggest to approve r06 Peter Hedman (Ericsson) ok with r06 or to postpone Alessio(Nokia) comments that r03 is the only version that we accept in line with existing CT1 text (so it does align with CT1 text). Nokia objects to changing existing clear specification unless there is a FSMO reason DUE to the specifications. ==== Final Deadline ==== | Postponed |
| 6.1 | S2-2208763 | LS OUT | Approval | [DRAFT] LS on Alignments related to usage of mapped S-NSSAi | Ericsson | Rel-17 | r05 agreed. Revised to S2-2209559. | Peter Hedman (Ericsson) provides r02 adding a statement about possibly doing CRs from Rel-15 at the next meeting. Alessio(Nokia) does not agree we need to state a speculative statement as in r02... if we agree to go to rel-15 at this meeting we just say so. if not we say there was no agreement to go back to rel-15 in which case it is inconsistent spec set (really? do we want that?). we shall take the decision at this meeting. in fact we should ask a number on Thursday to get the job done really...(not sure there is value to postpone?) Peter Hedman (Ericsson) provides comment that time passed for getting new tdoc numbers, as explained by chair att CC-1 Peter Hedman (Ericsson) provides r03 Alessio(Nokia) believes there is nothing preventing the allocation of new tdoc numbers if this is needed and there is consensus. I missed the statement new tdoc numbers are forbidden even if they are needed. asks Ericsson if they would object to allocation of tdoc numbers if we all agree to that. Haris(Qualcomm) comment that CR numbers need to be completed in the LS Peter Hedman (Ericsson) provides r04 alessi(Nokia) provides r05 ==== Revisions Deadline ==== Peter Hedman (Ericsson) propose to approve r05 as r06 simply tries to hide the debate. Peter Hedman (Ericsson) sorry, r05 hides the mapping issue for roaming i.e. we really prefer to be clear and instead approve r04. If Nokia objects to r04 as they want to hide it, we are ok with r05. alessio(Nokia) can only accept r05 ==== Final Deadline ==== | Revised |
| 6.1 | S2-2209559 | LS OUT | Approval | Alignments related to usage of mapped S-NSSAI | SA WG2 | Rel-17 | Revision of S2-2208763r05. Approved | Approved | |
| 6.1 | S2-2208834 | CR | Approval | 23.501 CR3673R1 (Rel-17, 'F'): Mapped NSSAI alignment with stage-3 | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2205753 from S2#152E. r03 agreed. Revised to S2-2209560. | Alessio(Nokia) comments on the release of this CR and asks why it is not rel-15 if this is aligning with stage 3 sing rel-15 Haris(Qualcomm) responds that we are ok to bring the same CR to rel.15/16 at next meeting Krisztian (Apple) provides r01. Peter Hedman (Ericsson) provides r02 Alessio(Nokia) ok with r01. Guillaume (MediaTek Inc.) agrees with r01 (and certainly r02) alessio(nokia) Provides r03 ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03 ==== Final Deadline ==== | Revised |
| 6.1 | S2-2209560 | CR | Approval | 23.501 CR3673R2 (Rel-17, 'F'): Mapped NSSAI alignment with stage-3 | Qualcomm Incorporated, Apple, MediaTek Inc | Rel-17 | Revision of S2-2208834r03. Approved | Agreed | |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=0 | - | |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=4 | - | |
| 6.3 | S2-2208351 | CR | Approval | 23.502 CR3559 (Rel-16, 'F'): 3GPP PS Data Off status in PDU Session Establishment | Ericsson | Rel-16 | r01 agreed. Revised to S2-2209561. | Laurent (Nokia): Comments and suggests to only consider this for R17 Judy (Ericsson) responds to Laurent (Nokia) and prefer to have the correction in Rel-16 as well. Mirko (Huawei) comments. Judy (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 6.3 | S2-2209561 | CR | Approval | 23.502 CR3559R1 (Rel-16, 'F'): 3GPP PS Data Off status in PDU Session Establishment | Ericsson | Rel-16 | Revision of S2-2208351r01. Approved | Agreed | |
| 6.3 | S2-2208352 | CR | Approval | 23.502 CR3560 (Rel-17, 'F'): 3GPP PS Data Off status in PDU Session Establishment | Ericsson | Rel-17 | r00 agreed. Revised to S2-2209562. | ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 6.3 | S2-2209562 | CR | Approval | 23.502 CR3560R1 (Rel-17, 'F'): 3GPP PS Data Off status in PDU Session Establishment | Ericsson | Rel-17 | Revision of S2-2208352r00. Approved | Agreed | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=2 | - | |
| 6.5 | S2-2209058 | CR | Approval | 23.501 CR3747 (Rel-17, 'F'): Correction on conditions for using SPI for UE derived QoS rules | Qualcomm Incorporated | Rel-17 | r02 agreed. Revised to S2-2209563. | Stefan (Ericsson) provides r01 Mirko (Huawei) comments. Hong (Qualcomm) provides r02. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 6.5 | S2-2209563 | CR | Approval | 23.501 CR3747R1 (Rel-17, 'F'): Correction on conditions for using SPI for UE derived QoS rules | Qualcomm Incorporated | Rel-17 | Revision of S2-2209058r02. Approved | Agreed | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=9 | - | |
| 6.6 | S2-2208132 | LS In | Action | LS from CT WG3: UE Policy Control with PCF re-selection during AMF relocation | CT WG3 (C3-224697) | Rel-17 | Responses drafted in S2-2208348, S2-2208859, S2-2209089. Postponed | Haiyang (Huawei) proposes to use this thread to discuss the LS 8132 Belen (Ericsson) provides comments Jinguo(ZTE) provides comments Belen (Ericsson) asks ZTE DongYeon (Samsung) comments. Uri(Oracle) provides comments Haiyang (Huawei) comments Jinguo(ZTE) replies to Belen (Ericsson) Huazhang (vivo) have some observation and join the discussion Yue (China Telecom) provides comment. Belen (Ericsson) replies to the discussion on the PCF needs to know if it is an initial registration or a mobility case Pallab (Nokia) provides views Uri (Oracle) responds to Haiyang Haiyang (Huawei) responds to Uri (Oracle), Ok to postpone the LS discussion Belen (Ericsson) is okay to postpone the LS. DongYeon (Samsung) agrees to postpone this LS. | Postponed |
| 6.6 | S2-2208348 | LS OUT | Approval | [DRAFT] Reply LS on UE Policy Control with PCF re-selection during AMF relocation | Ericsson | Rel-17 | Response to S2-2208132. Postponed | Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) agrees to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2208859 | LS OUT | Approval | [DRAFT] LS on UE Policy Control with PCF re-selection during AMF relocation | Huawei, HiSilicon | Rel-17 | Response to S2-2208132. Postponed | Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) agrees to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2209089 | LS OUT | Approval | [DRAFT] Reply LS on UE Policy Control with PCF re-selection during AMF relocation | Samsung Electronics Romania | Rel-17 | Response to S2-2208132. Postponed | Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) agrees to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2209091 | DISCUSSION | Decision | UE Policy Association Establishment when AMF relocation with PCF change. | Samsung | Rel-17 | Noted | ==== Revisions Deadline ==== DongYeon (Samsung) suggests to note this discussion paper. ==== Final Deadline ==== | Noted |
| 6.6 | S2-2209093 | CR | Approval | 23.502 CR3597 (Rel-17, 'F'): UE Policy Association Establishment when AMF relocation with PCF change | Samsung | Rel-17 | Postponed | Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly. Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) agrees to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2209095 | CR | Approval | 23.503 CR0758 (Rel-17, 'F'): UE Policy Association Establishment when AMF relocation with PCF change | Samsung | Rel-17 | Postponed | Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly. Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) agrees to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2208349 | CR | Approval | 23.502 CR3558 (Rel-17, 'F'): UE Policy determination at AMF relocation with PCF change | Ericsson | Rel-17 | Postponed | DongYeon (Samsung) asks a question. Belen (Ericsson) asks if questions below are replied in S2-2208132 Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly. Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) proposes to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.6 | S2-2208350 | CR | Approval | 23.503 CR0742 (Rel-17, 'F'): UE Policy determination at AMF relocation with PCF change | Ericsson | Rel-17 | Postponed | Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly. Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132. ==== Revisions Deadline ==== DongYeon (Samsung) proposes to postpone this paper. ==== Final Deadline ==== | Postponed |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=3 | - | |
| 6.7 | S2-2208252 | CR | Approval | 23.501 CR3703 (Rel-17, 'F'): PScell handling in 5GS | Ericsson | Rel-17 | Noted | Hannu (Nokia) proposes to note this CR as it is attempting to extend the agreed scope of Rel-17 feature. Qian (Ericsson) provides comments. Wanqiang (Huawei) has concern and proposes to note this CR. Qian (Ericsson) responds. Hannu (Nokia) replies to Qian. Chris (Vodafone) thinks that the Ericsson CR is logical. Hannu (Nokia) comments that this CR is not what we agreed when introducing this feature and that the justification for this 5GS change is derived from EPS. ==== Revisions Deadline ==== Qian (Ericsson) responds to Hannu(Nokia) and propose to approve original revision. Wanqiang (Huawei) is not Ok with original revision as it is not a correction CR. ==== Final Deadline ==== | Noted |
| 6.7 | S2-2209002 | CR | Approval | 23.501 CR3742 (Rel-17, 'F'): Correction of reference for RedCap indication from UE | Qualcomm Inc. | Rel-17 | Bad WI code. CR Number incorrect XXX! Should be 3742 (in revision number cell). r02 agreed. Revised to S2-2209564. | Hannu (Nokia) provides r01. Miguel (Qualcomm) ok with r01. Steve (Huawei) comments on the record rev number and CR number. Miguel (Qualcomm) provides r02 correcting CR number and Rev number ==== Revisions Deadline ==== Qian (Ericsson) is ok with r02 Steve (Huawei) is ok with r02 ==== Final Deadline ==== | Revised |
| 6.7 | S2-2209564 | CR | Approval | 23.501 CR3742R1 (Rel-17, 'F'): Correction of reference for RedCap indication from UE | Qualcomm Inc. | Rel-17 | Revision of S2-2209002r02. Approved | Agreed | |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=0 | - | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=2 | - | |
| 6.9 | S2-2208382 | CR | Approval | 23.501 CR3712 (Rel-17, 'F'): Monitoring event in 5GS to EPS mobility | Nokia, Nokia Shanghai Bell | Rel-17 | r02 agreed. Revised to S2-2209565. | Fenqin (Huawei): Comments and provides r01 Qian (Ericsson) asks questions Hannu (Nokia) asks questions and comments that some changes in r01 are not correct. Fenqin (Huawei) provides a feedback to Hannu Qian (Ericsson) provides comments. Hannu (Nokia) answers to Fenqin. Hannu (Nokia) asks follow-up questions Fenqin (Huawei) answers to Hannu. Hannu (Nokia) provides r02 ==== Revisions Deadline ==== Fenqin (Huawei) is fine with r02 Fenqin (Huawei) provides response to Qian Qian (Ericsson) provides further comments. Hannu (Nokia) proposes to agree r02. Fenqin (Huawei) we are fine to go with r02. ==== Final Deadline ==== | Revised |
| 6.9 | S2-2209565 | CR | Approval | 23.501 CR3712R1 (Rel-17, 'F'): Monitoring event in 5GS to EPS mobility | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2208382r02. Approved | Agreed | |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=0 | - | |
| 7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Docs:=0 | - | |
| 7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | Docs:=2 | - | |
| 7.1 | S2-2208174 | CR | Approval | 23.287 CR0184 (Rel-17, 'F'): Removal of V2X policy request during registration procedure | LG Electronics, Ericsson, CATT, Huawei, ZTE | Rel-17 | Postponed | LaeYoung (LGE) thinks that result for this CR should be same to result of S2-2208356/8357 in AI#8.8 for consistent handling of same topic (i.e. approved or postponed). ==== Revisions Deadline ==== LaeYoung (LGE) proposes to get this CR POSTPONED as well because the result of S2-2208356/8357 in AI#8.8 covering same topic is Postponed. ==== Final Deadline ==== | Postponed |
| 7.1 | S2-2208175 | CR | Approval | 23.503 CR0738 (Rel-17, 'F'): Removal of V2X policy request during registration procedure | LG Electronics, Ericsson, CATT, Huawei, ZTE | Rel-17 | Postponed | LaeYoung (LGE) thinks that result for this CR should be same to result of S2-2208356/8357 in AI#8.8 for consistent handling of same topic (i.e. approved or postponed). ==== Revisions Deadline ==== LaeYoung (LGE) proposes to get this CR POSTPONED as well because the result of S2-2208356/8357 in AI#8.8 covering same topic is Postponed. ==== Final Deadline ==== | Postponed |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=4 | - | |
| 7.2 | S2-2208180 | CR | Approval | 23.316 CR2072 (Rel-17, 'F'): Change the direction of the arrow in figure | IPLOOK | Rel-17 | Spec version incorrect - V17.3.0! r02 agreed. Revised to S2-2209670. | Laurent (Nokia): Comments, shall provide revision marks Weizhi Wu(IPLOOK) provides r01 Weizhi Wu(IPLOOK) provides r02 Stefan (Ericsson) comments on the revision marks ==== Revisions Deadline ==== Weizhi Wu(IPLOOK) provides r03 Stefan (Ericsson) suggest to agree r03 Laurent (Nokia): suggests to agree R03 for the same reason than Stefan Marco (Huawei) ok with r03 since agrees with Stefan (Ericsson) and Laurent (Nokia) ==== Final Deadline ==== | Revised |
| 7.2 | S2-2209670 | CR | Approval | 23.316 CR2072R1 (Rel-17, 'F'): Change the direction of the arrow in figure | IPLOOK | Rel-17 | Revision of S2-2208180r02. Approved | Agreed | |
| 7.2 | S2-2208323 | CR | Approval | 23.501 CR3708 (Rel-16, 'F'): R16 Correction on TNGF functionality | Huawei, HiSilicon | Rel-16 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 7.2 | S2-2208324 | CR | Approval | 23.501 CR3709 (Rel-17, 'A'): R17 Correction on TNGF functionality | Huawei, HiSilicon | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | Docs:=0 | - | |
| 7.4 | - | - | - | Cellular IoT support and evolution for the 5G System (5G_CIoT) | - | - | Docs:=0 | - | |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=0 | - | |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=0 | - | |
| 7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | Docs:=0 | - | |
| 7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | Docs:=0 | - | |
| 7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | Docs:=5 | - | |
| 7.10 | S2-2208138 | LS In | Action | LS from CT WG4: LS on Packet Delay Failure Threshold | CT WG4 (C4-224636) | Rel-17 | Postponed | Postponed | |
| 7.10 | S2-2208572 | CR | Approval | 23.503 CR0750 (Rel-16, 'F'): Clarifications for QoS monitoring control | Huawei, HiSilicon | Rel-16 | Postponed | Shabnam (Ericsson) provides detailed comments and objects to the CR as not FASMO and adds new functions not in scope. Mirko (Huawei) replies to Shabnam's comments. Devaki (Nokia) comments. We also believe the CR changes must be limited to FASMO changes and new enhancements must be removed. Mirko (Huawei) responds to Devaki's questions. ==== Revisions Deadline ==== Shabnam (Ericsson) proposes to note the CR and work offline towards a resolution at the next meeting. Devaki (Nokia) proposes to postpone the paper. ==== Final Deadline ==== | Postponed |
| 7.10 | S2-2208573 | CR | Approval | 23.503 CR0751 (Rel-17, 'A'): Clarifications for QoS monitoring control | Huawei, HiSilicon | Rel-17 | Postponed | ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 7.10 | S2-2208574 | CR | Approval | 23.501 CR3721 (Rel-16, 'F'): Clarifications for QoS monitoring control | Huawei, HiSilicon | Rel-16 | Noted | Shabnam (Ericsson) provides technical comments and objects to the CR as this is not FASMO and changing functions that are stable since Rel-16. Genadi (Lenovo) provides a question for clarification. Mirko (Huawei) responds to Genadi's question. Mirko (Huawei) replies to Shabnam's comments. Genadi (Lenovo) replies to Mirko (Huawei). Mirko (Huawei) comments. Shabnam (Ericsson) provides comments in line and notes that Lenovo has created a separate thread after Ericsson email thread was established... Mirko (Huawei) responds. ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that since we have not created any revision but good discussion, propose to note now and work offline until next meeting. ==== Final Deadline ==== | Noted |
| 7.10 | S2-2208575 | CR | Approval | 23.501 CR3722 (Rel-17, 'A'): Clarifications for QoS monitoring control | Huawei, HiSilicon | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=0 | - | |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=0 | - | |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=0 | - | |
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=1 | - | |
| 7.14 | S2-2208186 | CR | Approval | 23.502 CR3551 (Rel-17, 'F'): Alignment of TS 23.502 with SBI-based SMS | Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=0 | - | |
| 7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | Docs:=0 | - | |
| 7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | Docs:=0 | - | |
| 8 | - | - | - | Rel-17 WIDs | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=16 | - | |
| 8.1 | - | - | - | 5GS information exposure | - | - | Docs:=9 | - | |
| 8.1 | S2-2208167 | LS In | Action | LS from CT WG3: LS on Issues on exposing 5GS information to an untrusted AF | CT WG3 (C3-224688) | Rel-17 | Responses drafted in S2-2208705, S2-2208992. Final response in S2-2209566 | Replied to | |
| 8.1 | S2-2208705 | LS OUT | Approval | [DRAFT] LS reply on Issues on exposing 5GS information to an untrusted AF | Huawei, HiSilicon | Rel-17 | Response to S2-2208167. Merged into S2-2209566 | Josep (DT) would like to point out that A1 is not an answer to Q1. Belen (Ericsson) provides comments Wang Yuan (Huawei) replies to Belen (Ericsson) and Josep(DT), and provides r01. ==== Revisions Deadline ==== Yannick (Nokia): Nokia suggests to merge this into S2-2208992. r01 for this draft LS out is not aligned with further changes made to related CR in S2-2208991. Wang Yuan (Huawei) is OK to merge this into S2-2208992. ==== Final Deadline ==== | Merged |
| 8.1 | S2-2208992 | LS OUT | Approval | [DRAFT] Reply LS on Issues on exposing 5GS information to an untrusted AF | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2208167. r01 agreed. Revised to S2-2209566, merging S2-2208705 | Belen (Ericsson) provides comments Yannick (Nokia): Nokia provides r01 which aligns with S2-2208991r03. ==== Revisions Deadline ==== Leo (Deutsche Telekom) supports r01 ==== Final Deadline ==== | Revised |
| 8.1 | S2-2209566 | LS OUT | Approval | Reply LS on Issues on exposing 5GS information to an untrusted AF | SA WG2 | Rel-17 | Revision of S2-2208992r01, merging S2-2208705. Approved | Approved | |
| 8.1 | S2-2208704 | CR | Approval | 23.288 CR0549 (Rel-17, 'F'): Clarification on exposing 5GS information to an untrusted AF | Huawei, HiSilicon | Rel-17 | Merged into S2-2209671 | Antoine (Orange) asks a fundamental question. Wang Yuan (Huawei) propose to merge this CR into S2-2208991. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.1 | S2-2208991 | CR | Approval | 23.288 CR0553 (Rel-17, 'F'): Corrections on exposing 5GS information to untrusted AF | Nokia, Nokia Shanghai Bell | Rel-17 | r04 agreed. Revised to S2-2209671, merging S2-2208704 | Antoine (Orange) asks a fundamental question. Belen (Ericsson) provides comments. Malla (NTT DOCOMO) provides comments. Yannick (Nokia): Nokia provides r01. Wang Yuan (Huawei) thanks r01 for merging the 'NSI ID' proposal from 8704 and asks question on r01. Yannick (Nokia): Nokia replies to Huawei. Malla (NTT DOCOMO) provided r02. Yannick (Nokia): Nokia requests clarification to Malla (NTT DOCOMO). Malla (NTT DOCOMO) replies to Yannick (Nokia). Belen (Ericsson) cannot agree with the proposed updates in this CR Yannick (Nokia): Nokia asks if comment from Ericsson applies to all revisions that have been provided so far. Yannick (Nokia): Nokia provides r03 and asks if this could be a way forward. Malla (NTT DOCOMO) asks for clarification. Yannick (Nokia): Nokia answers that this revision should be read together with the LS out draft reply in S2-2208992r01. Yannick (Nokia): Nokia provides r04, with same text proposal as r03, but with cover page changes. ==== Revisions Deadline ==== Wang Yuan (Huawei) supports r04 and would like to co-sign. Belen (Ericsson) asks to remove in r04 NOTE 1: Dispersion analytics bound by slice are not provided to untrusted AF. Yannick (Nokia): Nokia agrees with proposal from Ericsson. We suggest to go with 'r04 + removal of NOTE 1 in 6.10.1'. ==== Final Deadline ==== | Revised |
| 8.1 | S2-2209671 | CR | Approval | 23.288 CR0553R1 (Rel-17, 'F'): Corrections on exposing 5GS information to untrusted AF | Nokia, Nokia Shanghai Bell, Huawei | Rel-17 | Revision of S2-2208991r04, merging S2-2208704. Approved | Agreed | |
| 8.1 | S2-2208990 | LS OUT | Approval | [DRAFT] Reply LS on eNA_Ph2 issues | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2205413 (Replied to at S2#151E). r00 agreed. Revised to S2-2209567 | ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.1 | S2-2209567 | LS OUT | Approval | Reply LS on eNA_Ph2 issues | SA WG2 | Rel-17 | Revision of S2-2208990r00. Approved | Approved | |
| 8.1 | - | - | - | Other | - | - | Docs:=7 | - | |
| 8.1 | S2-2208824 | CR | Approval | 23.288 CR0550 (Rel-17, 'F'): Formatting and Processing Instructions related correction to Nadrf_DataManagement service | ZTE | Rel-17 | r03 agreed. Revised to S2-2209672. | Yannick (Nokia): Nokia cannot accept initial version of the CR for Rel-17. Formatting and processing instructions have not been discussed in the context of ADRF, adding this at this stage of Rel-17 is not appropriate. Provides r01. Jinguo(ZTE) provides r02 Yannick (Nokia): Nokia replies to ZTE and provides r03. ==== Revisions Deadline ==== Yannick (Nokia): Nokia comments that if r03 is acceptable some changes to coversheet would be needed. Jinguo(ZTE) is ok with r03 + coversheet change, and thanks Yannick for good suggestion ==== Final Deadline ==== | Revised |
| 8.1 | S2-2209672 | CR | Approval | 23.288 CR0550R1 (Rel-17, 'F'): Formatting and Processing Instructions related correction to Nadrf_DataManagement service | ZTE, Nokia | Rel-17 | Revision of S2-2208824r03. Approved | Agreed | |
| 8.1 | S2-2208989 | CR | Approval | 23.288 CR0552 (Rel-17, 'F'): Corrections for time window in ADRF Nadrf_DataManagement service | Nokia, Nokia Shanghai Bell | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.1 | S2-2208247 | CR | Approval | 23.288 CR0545 (Rel-17, 'F'): Granularity of time and location for NWDAF analytics results | Ericsson | Rel-17 | Postponed | Wang Yuan (Huawei) raises concerns on r00. Belen (Ericsson) replies to Huawei concerns and asks if those are resolved ==== Revisions Deadline ==== Belen (Ericsson) asks Huawei if their comments were addressed, no response was received. Wang Yuan (Huawei) thanks for the clarification and in principle ok with this idea but still suggests to postpones the CR for next meeting since the changes still needs some further considerations. ==== Final Deadline ==== | Postponed |
| 8.1 | S2-2208591 | CR | Approval | 23.288 CR0547 (Rel-17, 'F'): Remove the Editor s Note related to EVEX in SA WG4 | Qualcomm Incorporated | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.1 | S2-2208173 | CR | Approval | 23.288 CR0544 (Rel-17, 'F'): Correction on SMCCE Analytics | LG Electronics, Ericsson | Rel-17 | Postponed | LaeYoung (LGE) comments that the change in this CR conflicts with the change in 8247 (clause 6.12.3). Belen (Ericsson) agrees that this one is not needed if we go with the change in 8247 (clause 6.12.3). ==== Revisions Deadline ==== LaeYoung (LGE) thinks that this CR can be Approved because 8247 is expected to be Noted. Belen (Ericsson) asks to check S2-2208247 first, given that Huawei did not reply. LaeYoung (LGE) proposes to POSTPONE this CR as 8247 is expected to be postponed for further discussion. Belen (Ericsson) is okay to POSTPONE ==== Final Deadline ==== | Postponed |
| 8.1 | S2-2208248 | CR | Approval | 23.288 CR0546 (Rel-17, 'F'): Corrections to Slice Load level Analytics ID | Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=9 | - | |
| 8.2 | S2-2208139 | LS In | Information | LS from CT WG6: Reply LS on Facilitating roaming adoption across 3GPP NPN deployments | CT WG6 (C6-220475) | Rel-17 | Noted | Peter Hedman (Ericsson) provides comments and propose to note the LS | Noted |
| 8.2 | S2-2208766 | CR | Approval | 23.503 CR0753 (Rel-17, 'F'): The list of PSIs associated to an SNPN | Ericsson | Rel-17 | r04 agreed. Revised to S2-2209568. | Josep (DT) comments, provides r01. Mirko (Huawei) comments. Josep (DT) tries, provides r03, please disregard r02. Requets to pelase re-check r03. Josep (DT) provides r04. Belen (Ericsson) is okay with r04. Josep (DT) is happy to co-sign. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.2 | S2-2209568 | CR | Approval | 23.503 CR0753R1 (Rel-17, 'F'): The list of PSIs associated to an SNPN | Ericsson, Deutsche Telekom | Rel-17 | Revision of S2-2208766r04. Approved | Agreed | |
| 8.2 | S2-2208768 | DISCUSSION | Decision | Differentiation of subscribed/non-subscribed SNPN in CH architecture. | Ericsson | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.2 | S2-2208769 | CR | Approval | 23.501 CR3731 (Rel-17, 'F'): Clarification when access SNPN using CH with AAA-S | Ericsson | Rel-17 | r03 agreed. CC#3: r03 + changes agreed. Revised to S2-2209673. | Josep (DT) is not sure whether introducing new terminology (subscribed/non-subscribed) improves clarity. Rainer (Nokia) agrees with Josep (DT). Peter Hedman (Ericsson) provides reply Haris(Qualcomm) comments that the CR is not FASMO but if the majority prefer to do this clarification only option 2 is acceptable without the sentence: 'This is, the AUSF, UDM and NSSAAF in Figure 5.30.2.9.2-1 belong to the subscribed SNPN of the UE.' In NOTE 2 Josep (DT) is OK to add as many clarification NOTEs but not to change normative text. Qianghua (Huawei) comments that the introduction of non-subscribed/subscribed SNPN in CH AAA-S case makes it hard to understand the architecture and doesn't see any benefits or necessities to do so Chia-Lin (MediaTek) provides the comments and considers this is not a FASMO CR Peter Hedman (Ericsson) provides r01 Saso (Intel) provides r02 Peter Hedman (Ericsson) ok with r02 Qianghua (Huawei) the terms 'subscribed/non-subscribed' still confuse me and doesn't match with the network selection logic, miss one case in the NOTE Peter Hedman (Ericsson) provides comments and r03 ==== Revisions Deadline ==== Qianghua (Huawei) asks further clarification. Haris(Qualcomm) proposes changes on top of r03 to add next to SUPI privacy settings 'SUPI privacy settings (when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])' Qianghua (Huawei) replies and can not live the NOTE as it is Peter Hedman (Ericsson) provides replies and ok with QC suggestion i.e. r03 + '(when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])' Qianghua (Huawei) that normative text applies for both 'subscribed SNPN' and 'non-subscribed SNPN' case. ==== Final Deadline ==== Qianghua (Huawei) proposes to make additional changes on the NOTE after offline discussion with Peter, i.e. r03 + '(when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])' + 'same as corresponding NFs in the subscribed SNPN' Antoine (Orange): The green addition is not clear. Peter Hedman (Ericsson) provides reply to Antoine | Revised |
| 8.2 | S2-2209673 | CR | Approval | 23.501 CR3731R1 (Rel-17, 'F'): Clarification when access SNPN using CH with AAA-S | Ericsson | Rel-17 | Revision of S2-2208769r03 + changes. Approved | Agreed | |
| 8.2 | S2-2208839 | CR | Approval | 23.501 CR3675R1 (Rel-17, 'F'): Alignment with SA WG3 agreement on usage of SUCI when CH is legacy AAA | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2205756 from S2#152E. CC#3: r05 agreed. Revised to S2-2209947. | Peter Hedman (Ericsson) provides comments Fei (OPPO) comments Haris(Qualcomm) provides r01 Haris(Qualcomm) responds Genadi (Lenovo) comments to r01. Genadi (Lenovo) responds to Haris (Qualcomm). Qianghua (Huawei) comments on the same point with Genadi Genadi (Lenovo) agrees with the proposal by Qianghua (Huawei). Chia-Lin (MediaTek) provides the comments on r01 and suggest to remove the change from clause 5.30.2.4.2 Peter Hedman (Ericsson) provides r02 Haris(Qualcomm) asks questions on r02 Haris(Qualcomm) provides r03 Fei (OPPO) comments and provides r04. Chia-Lin (MediaTek) provides r05 Haris(Qualcomm) indicates that r05 is not acceptable Peter Hedman (Ericsson) provides reply Peter Hedman (Ericsson) provides reply and r05 is ok Haris(Qualcomm) responds to Peter ==== Revisions Deadline ==== Haris(Qualcomm) can only accept r04, r03. Objects to r05, r02. R00 and R01 contain incorrect text Chia-Lin (MediaTek) can only accept r05 and object all other versions including the original one Fei (OPPO) can accept r04, r02, r05 and objects other revisions including r00. Haris(Qualcomm) asks Chia-Lin (Mediatek) to clarify the objection to r04 Qianghua (Huawei) OK with r01, r02, r03, r04, r05. But not the original Peter Hedman (Ericsson) provides reply that the note in 08769 clarifies that UDM handles the privacy as well i.e. the note is not needed in this CR Chia-Lin (MediaTek) responds to Haris (Qualcomm) ==== Final Deadline ==== | Revised |
| 8.2 | S2-2209947 | CR | Approval | 23.501 CR3675R2 (Rel-17, 'F'): Alignment with SA WG3 agreement on usage of SUCI when CH is legacy AAA | Qualcomm Incorporated | Rel-17 | Revision of S2-2208839r05. Approved | Agreed | |
| 8.2 | S2-2208935 | CR | Approval | 23.501 CR3738 (Rel-17, 'F'): Clarification of SUPI for SNPN | Huawei, HiSilicon | Rel-17 | Merged into (Covered by) S2-2208839 | Peter Hedman (Ericsson) provides comments that changes looks ok, but we can only agree this or 08839. Haris(Qualcomm) suggests to focus the discussion on S2-2208839 Qianghua (Huawei) OK to merge this into S2-2208839 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=18 | - | |
| 8.3 | S2-2208102 | LS In | Action | LS from CT WG3: LS on handling of FQDN ranges in AF influence on traffic routing procedures | CT WG3 (C3-222419) | Rel-17 | Revision of Postponed S2-2205396 from S2#152-e. Response drafted in S2-2208372. Final response in S2-2209269 | Replied to | |
| 8.3 | S2-2208372 | LS OUT | Approval | [DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures | Ericsson [to be SA2] | Rel-17 | Response to S2-2208102. r02 agreed. Revised to S2-2209269. | Xinpeng(Huawei) replies to Yuan Tao (CATT). Yuan Tao (CATT) asks Xinpeng(Huawei) for clarification on r01. Xinpeng(Huawei) provides r01. Yuan Tao (CATT) replies to Xinpeng(Huawei). Shubhranshu (Nokia) comments Jari (NTT DOCOMO) comments Xinpeng(Huawei) replies to Jari (NTT DOCOMO). Jari (NTT DOCOMO) replies to Xinpeng Jari (NTT DOCOMO) responds to Xinpeng Magnus H (Ericsson) comments. Shubhranshu (Nokia) responds Jari (NTT DOCOMO) prefers r01 Jari (NTT DOCOMO) responds to Magnus H Shubhranshu (Nokia) proposes to agree r02 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.3 | S2-2209269 | LS OUT | Approval | Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures | SA WG2 | Rel-17 | Revision of S2-2208372r02. Approved | Approved | |
| 8.3 | S2-2208160 | LS In | Information | LS from SA WG6: Reply LS to OPAG_34_Doc_07_OPAG_LS ETSI-3GPP-Network integration | SA WG6 (S6-222337) | Rel-18 | Noted | Magnus O (Ericsson) proposes to Note this LS | Noted |
| 8.3 | S2-2208162 | LS In | Action | LS from SA WG6: Forward on S6-222332, LS on Network federation interface for Telco edge consideration | SA WG6 (S6-222543) | Rel-18 | Postponed | Magnus O (Ericsson) proposes to postpone this LS to the November meeting | Postponed |
| 8.3 | S2-2208163 | LS In | Information | LS from SA WG6: Reply LS on user’s consent for EDGEAPP | SA WG6 (S6-222555) | Rel-17 | Response drafted in S2-2208373. Final response in S2-2209270 | Replied to | |
| 8.3 | S2-2208373 | LS OUT | Approval | [DRAFT] Response LS on Clarifications for AF specific UE ID retrieval | Ericsson [to be SA2] | Rel-17 | Response to S2-2208163. r00 agreed. Revised to S2-2209270. | Jinsook (DISH) Question for clarification Magnus (Ericsson) Provides answers ==== Revisions Deadline ==== Jinsook (DISH) Thanks for the clarification, further comment ==== Final Deadline ==== | Revised |
| 8.3 | S2-2209270 | LS OUT | Approval | Response LS on Clarifications for AF specific UE ID retrieval | SA WG2 | Rel-17 | Revision of S2-2208373r00. Approved | Approved | |
| 8.3 | S2-2208164 | LS In | Information | LS from SA WG6: Reply LS to Network federation interface for Telco edge consideration | SA WG6 (S6-222557) | Rel-18 | Noted | Noted | |
| 8.3 | S2-2208368 | CR | Approval | 23.501 CR3663R1 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule | Ericsson | Rel-17 | Revision of (Postponed) S2-2205633 from S2#152E. r04 agreed. Revised to S2-2209271. | Xinpeng(Huawei) provides r01. Magnus H (Ericsson) comments and provides r02 Xinpeng(Huawei) provides r03. Shubhranshu (Nokia) asks for clarification Magnus H (Ericsson) this document should be under AI#6.6, could we please move. Sorry for the inconvenience. Shubhranshu (Nokia) comments Magnus H (Ericsson) comments. Jari (NT DOCOMO) provides r04 Shubhranshu (Nokia) responds ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.3 | S2-2209271 | CR | Approval | 23.501 CR3663R2 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule | Ericsson | Rel-17 | Revision of S2-2208368r04. Approved | Agreed | |
| 8.3 | S2-2208369 | CR | Approval | 23.503 CR0732R1 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule | Ericsson | Rel-17 | Revision of (Postponed) S2-2205635 from S2#152E. r01 agreed. Revised to S2-2209272. | Xinpeng(Huawei) comments. Magnus H (Ericsson) provides r01. Shubhranshu (Nokia) comments Magnus H (Ericsson) this document should be under AI#6.6, could we please move. Sorry for the inconvenience. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.3 | S2-2209272 | CR | Approval | 23.503 CR0732R2 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule | Ericsson | Rel-17 | Revision of S2-2208369r01. Approved | Agreed | |
| 8.3 | S2-2208370 | CR | Approval | 23.501 CR3634R2 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF | Ericsson | Rel-17 | Revision of (Postponed) S2-2205629 from S2#152E. Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.3 | S2-2208371 | DISCUSSION | Decision | DP on role of PCC in authorization of EAS Discovery procedure with EASDF. | Ericsson | Rel-17 | Noted | Xinpeng(Huawei) proposes to note this DP paper. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.3 | S2-2208576 | CR | Approval | 23.548 CR0063 (Rel-17, 'F'): Clarifications for local event notification control | Huawei, HiSilicon | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.3 | S2-2209171 | CR | Approval | 23.501 CR3751 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request | Nokia, Nokia Shanghai Bell | Rel-17 | Postponed | Tugce (NTT DOCOMO) comments and provides r01. Jari (NTT DOCOMO) provides r02. Xinpeng(Huawei) proposes merge 9171 into 8370. Magnus H (Ericsson) agrees with Xinpeng that we should merge 9171 into 8370 Shubhranshu (Nokia) responds Shubhranshu (Nokia) proposes NOT to merge Xinpeng(Huawei) replies to Shubhranshu (Nokia). Xinpeng(Huawei) responds to Shubhranshu (Nokia). ==== Revisions Deadline ==== Xinpeng(Huawei) proposes to note this paper. Shubhranshu (Nokia) proposes to postpone this paper Xinpeng(Huawei) is fine to postpone. ==== Final Deadline ==== | Postponed |
| 8.3 | S2-2209172 | CR | Approval | 23.503 CR0759 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request | Nokia, Nokia Shanghai Bell | Rel-17 | Postponed | Xinpeng(Huawei): the result of 9172 depends on the discussion of 9171. Jari (NTT DOCOMO) proposes to postpone Shubhranshu (Nokia) OK to postpone ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=25 | - | |
| 8.4 | S2-2208116 | LS In | Information | Reply LS on Support for managing slice for trusted third-party owned application | SA WG1 (S1-222262) | Rel-18 | Revision of Postponed S2-2208097 from S2#152-e. Noted | Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 | Noted |
| 8.4 | S2-2208151 | LS In | Information | LS from SA WG1: Reply LS on Support for managing slice for trusted third-party owned application | SA WG1 (S1-222267) | Rel-18 | Noted | Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 | Noted |
| 8.4 | S2-2208161 | LS In | Information | LS from SA WG6: Reply LS on Reply LS on Support for managing slice for trusted third-party owned application | SA WG6 (S6-222340) | Rel-18 | Noted | Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 | Noted |
| 8.4 | S2-2208107 | LS In | Action | LS from SA WG3: LS on EAC Mode for NSAC | SA WG3 (S3-221164) | Rel-17 | Revision of Postponed S2-2205437 from S2#152-e. Response drafted in S2-2208415. Final response in S2-2209260 | Replied to | |
| 8.4 | S2-2208415 | LS OUT | Approval | [DRAFT] Reply LS on EAC Mode for NSAC | Huawei, HiSilicon | Rel-17 | Response to S2-2208107. r00 agreed. Revised to S2-2209260. | ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.4 | S2-2209260 | LS OUT | Approval | LS Reply on EAC Mode for NSAC | SA WG2 | Rel-17 | Revision of S2-2208415r00. Approved | Approved | |
| 8.4 | S2-2208416 | CR | Approval | 23.502 CR3563 (Rel-17, 'F'): Clarification on EAC Mode for NSAC | Huawei, HiSilicon, ZTE | Rel-17 | r02 agreed. Revised to S2-2209273. | Haiyang (Huawei) provides r01 George Foti (Ericsson) provides comments Stefano Faccin (Qualcomm) provides comments Haiyang (Huawei) provides clarification Dongeun (Samsung) comments Haiyang (Huawei) provides clarification to Dongeun (Samsung) alessio(Nokia) supports the comment(s) by Stefano. proposes to note this CR also at this meeting as it is not helping to address a FASMO issue so we cannot agree to it. SA3 can put a note in their specs if they see a need and can find consensus in SA3 on a logic to set a proper value that is secure. Haiyang (Huawei) provides comments to Alessio (Nokia) Haiyang (Huawei) provides r02 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.4 | S2-2209273 | CR | Approval | 23.502 CR3563R1 (Rel-17, 'F'): Clarification on EAC Mode for NSAC | Huawei, HiSilicon, ZTE | Rel-17 | Revision of S2-2208416r02. Approved | Agreed | |
| 8.4 | S2-2209003 | CR | Approval | 23.502 CR3592 (Rel-17, 'F'): Update in EAC mode procedure | Samsung | Rel-17 | Noted | Fenqin (Huawei) provides comments George Foti (Ericsson) proposes to note the CR. Please see comments below. Ashok (Samsung) responds to George (Ericsson) and Fenqin (Huawei) George (Ericsson) provides answer. EAC follow the quota. This case is for 3GPP, then that's what it is applied for. Ashok (Samsung) comments Fenqin (Huawei) provides response Ashok (Samsung) provides comments Iskren (NEC) this CR should be noted as the quota is per UE, not per AT Ashok (Samsung) responds to Iskren (NEC) Fenqin (Huawei) reply to Ashok Ashok (Samsung) clarifies to Fenqin Jinguo(ZTE) comments Fenqin (Huawei) provides a further comments Ashok (Samsung) responds to Fenqin , Jinguo alessio(Nokia) also agrees there is no FASMO. the worst case EAC is not activated for both access types. Ashok (Samsung) ask a question to Alessio(Nokia) Iskren (NEC) comments. Ashok (Samsung) explains to Iskren Alessio(Nokia) replies Ashok (Samsung) responds to Alessio(Nokia) George (Ericsson) provides response George (Ericsson) The issue is understood and no action is required. Ashok (Samsung) replies to Iskren Ashok (Samsung) seeks a clarification from George Ashok (Samsung) provides response to George (Ericsson) Ashok (Samsung) comments to George Iskren (NEC) answers Ashok (Samsung) replies to Iskren Ashok (Samsung) replies to Iskren (NEC) Iskren (NEC) replies to Ashok (Samsung) ==== Revisions Deadline ==== Fenqin (Huawei) suggest to note this paper. Ashok (Samsung) agrees to NOTE the paper ==== Final Deadline ==== | Noted |
| 8.4 | S2-2208103 | LS In | Action | LS from CT WG1: LS on NSSRG restriction on pending NSSAI | CT WG1 (C1-224073) | Rel-17 | Revision of Postponed S2-2205406 from S2#152-e. This LS was postponed | Postponed | |
| 8.4 | S2-2209037 | LS OUT | Approval | [DRAFT] LS on NSSRG restriction on pending NSSAI | NEC | Rel-17 | CC#3: r03 agreed. Revised to S2-2209944. | Alessio(Nokia) provides r01 so it can be used in association with Nokia CRs. Alessio(Nokia) provides r01 so it can be used in association with Nokia CRs. (sending zip file) Alessio(Nokia) provides r01 clarifying that when NSSRG Info applies the Pending NSSAI cannot be blindly added to the Requested as (you may imagine) the requested and pending need not be compatible a priory. Kundan (NEC) objects to r01. Nokia has wrong understanding of pending NSSAI. Pending NSSAI is implicit requested NSSAI according to CT1. If the UE is interested in the pending NSSAI but can't send it as a part of requested NSSAI due to CT1 design doesn't mean it is not requested NSSAI. Ashok (Samsung) provides r02 Kundan(NEC) : r02 is very confusing and contradictory alessio(nokia) comments CT1 has not a common understanding that is why they asked the question. even if they had the understanding the pending is always part of requested this is not correct as it violates the NSSRG feature when there is incompatibility with pending. it would be like mandating the allowed or rejected is always part of requested... (given that a pending S-NSSAI can be ultimately allowed or rejected). Alessio(Nokia) also prefers to postpone to next meeting and have a call to discuss this important topi. r02 is to us going in the right direction logically but we need to create the right CR backing it so CT1 eventually does the right thing. And also we need to tell CT1 they have to remove in NSSRG context (i.e. for UEs for which NSSRG applies) the assumption that the pending is virtually part of requested as obviously when the Ue requests incompatible slices with a pending S-NSSAI this cannot be part of the requested. ==== Revisions Deadline ==== Kundan(NEC) provides r03 which is very much aligned with stage 2 and stage3. Xiaowen(vivo) is ok to r03 and propose to go with r03, can live with r02. Tao(VC) remind r03 is provided after revision deadline. Further check whether any version agreeable. r03 is uploaded on the server within the time period. this is before 10/12 16:00 UTC. alessio(nokia) suggest to note the LS as we will postpone the issue nokia is not happy to send any LS till we have a stable state in SA2. this will not be till next meeting. Peter Hedman (Ericsson) propose to send LS as delaying to next meeting means we probably delay the resolution in stage 3 to Q1 2023 Alessio(Nokia) LSs are sent when there is a clear way forward. ==== Final Deadline ==== | Revised |
| 8.4 | S2-2209944 | LS OUT | Approval | LS out on NSSRG restriction on pending NSSAI | SA WG2 | Rel-17 | Revision of S2-2209037r03. Approved | Approved | |
| 8.4 | S2-2209038 | LS OUT | Approval | [DRAFT] LS on NSSRG Restrictions on Pending NSSAI | vivo | Rel-17 | Merged into (Covered by) S2-2209037 | Haiyang (Huawei) suggests to discuss in 9037 thread Jinguo(ZTE) suggest to merge this LS to 9037 Xiaowen (vivo) agrees to merge into 9037. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.4 | S2-2209039 | CR | Approval | 23.501 CR3744 (Rel-17, 'F'): NSSRG restriction on Pending NSSAI | Vivo | Rel-17 | Noted | Jinguo(ZTE) think this CR is not needed Genadi (Lenovo) has concerns with the proposal. Alessio(Nokia) also believes this is not the way forward to resolve the issue. Peter Hedman (Ericsson) provides comments that a way forward without need for any indication is preferred Xiaowen (vivo) provides responses. Jinguo(ZTE) agree with others view ==== Revisions Deadline ==== Stefano (Qualcomm) assumes that based on the previous comments, this CR will be noted. Peter Hedman (Ericsson) agree that CR should be noted vivo confirm this CR can be noted. ==== Final Deadline ==== | Noted |
| 8.4 | S2-2209040 | CR | Approval | 23.502 CR3594 (Rel-17, 'F'): NSSRG restriction on Pending NSSAI | Vivo | Rel-17 | Noted | Jinguo(ZTE) think this CR is not needed Alessio(Nokia) believes this is not the way forward to resolve the issue. ==== Revisions Deadline ==== Stefano (Qualcomm) assumes that based on the previous comments, this CR will be noted. we should note this CR. as we don't need a separate indicator. Peter Hedman (Ericsson) agree that CR should be noted vivo confirm this CR can be noted. ==== Final Deadline ==== | Noted |
| 8.4 | S2-2209201 | CR | Approval | 23.501 CR3684R1 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2206152 from S2#152E. LATE DOC: Rx 03/10, 10:50. Postponed | Peter Hedman (Ericsson) provides question if the late CR is part of the meeting? Kundan (NEC) has same response as Peter. After the document submission deadline it was not in the tdoc list. Kundan(NEC) also proposes to note this paper. alessio(nokia) ... we believe that our CRs are consistent with current UE behaviour in NSSRG handling which is the same as if the S-NSSAI was allowed instead of pending. if we can request one S-NSSAI set incompatible with allowed NSSAI, we surely can request one S-NSSAI incompatible with a pending NSSAI. it is the network then that needs to check the compatibility of the pending with the allowed at time of NSSAA completion. Kundan (NEC) pending NSSAI is considered as part of the requested NSSAI. so Nokia CR is against the current NSSRG principle. Kundan(NEC): Nokia CR has a big drawback, it is always rejecting the pending NSSAI. what is the logic? Alessio(Nokia) clarifies Kundan's doubt alessio(Nokia) clarifies this was a network side behaviour predating the NSSRG introduction. this is no longer valid thereafter. Kundan(NEC) further clarifies Alessio. According to stage 3, receiving incompatible slices at the network side is abnormal case. Alessio(Nokia)replies that consistently with that the requested NSSAI is always made of compatible S-NSSAIs as we say. Haiyang (Huawei) comments. Kundan (NEC) has same understanding as Huawei that pending NSSAI is part of requested NSSAI should be compatible. we have reiterated earlier this also. Kundan(NEC) indicates that the UE can still be interested in the pending NSSAI and an additional slice then the pending slice and new additional must be compatible. Peter Hedman (Ericsson) provides comments and propose we move forward with CR in 09004 Ashok (Samsung) suggests a way forward This CR suffers same issue Genadi raised. AMF will deny the service of most preferred slice for the UE. Alessio(Nokia) comments alessio(nokia) clarifies we are addressing the case here where the UE is no more interested in the pending NSSAI (as the whole discussion is what to do when the Pending s-NSSAI is incompatible with requested) alessio(Nokia) is not in tune with the way forward proposed by Ashok(Samsung) as this is exactly the issue this CR wants to avoid (any blocking factor to requesting service) alessio(Nokia) cannot see any relationship with the access type issue. Kundan (NEC) commented that Nokia CR does not have statement that the UE is no more interested then ignore the pending NSSAI and send the new requested NSSAI. it has very generic statement to send the incompatible requested NSSAI even though the UE is interested. can you show me where it is mentioned that the UE is not interested pending NSSAI statement?? Stefano (Qualcomm) believes the original question has not been answered: this is a LATE CR and as such should not be discussed. If we allow it, then anyone under any WID will start injecting late CRs. This is not acceptable, sorry. Alessio(Nokia) replies to Stefano (Qualcomm) ==== Revisions Deadline ==== Kundan (NEC) CR won't work when the UE is pending over one AMF and UE tries to register on another AMF and ignoring the pending NSSAI and sends the incompatible slices. how the two AMF can co-operate after NSSAA procedure is finished on one AMF? This solution doesn't work in many cases in addition to the case when the UE is registering over two AMFs. I agree with Stefano this this CR shouldn't be treated at all due to late submission. Kundan (NEC) indicates this CR won't work when the UE is pending over one AMF and UE tries to register on another AMF and ignoring the pending NSSAI and sends the incompatible slices. how the two AMF can co-operate after NSSAA procedure is finished on one AMF? This solution doesn't work in many cases in addition to the case when the UE is registering over two AMFs. I agree with Stefano this this CR shouldn't be treated at all due to late submission. alessio(Nokia) the statements below need to be discussed further in a DP as they are not clear. if the UE requests compatible slices set on both accesses both AMFs will react to pending consistently. so the issue is not clear and needs to be discussed but I see ultimately the only argument left is the procedural one so let's postpone the issue Peter Hedman (Ericsson) agree that CR should be noted and we can focus on NEC CR Kundan (NEC) provides list of drawbacks of this solution. alessio (Nokia) the issue is postponed then. ==== Final Deadline ==== | Postponed |
| 8.4 | S2-2209202 | CR | Approval | 23.502 CR3529R1 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2206159 from S2#152E. LATE DOC: Rx 03/10, 10:50. Noted | Peter Hedman (Ericsson) provides comments that we should move forward with CR in 9004 i.e. this CR can be noted. ==== Revisions Deadline ==== Kundan(NEC): this document should be noted. reasons are provided in 09201 thread. ==== Final Deadline ==== | Noted |
| 8.4 | S2-2209004 | CR | Approval | 23.501 CR3693R1 (Rel-17, 'F'): Pending NSSAI and NSSRG | NEC, Ericsson, Huawei, HiSilicon, ZTE | Rel-17 | Revision of (Postponed) S2-2206644 from S2#152E. CC#3: r02 agreed. Revised to S2-2209943. Agree r02? | Genadi (Lenovo) asks a question for clarification. Alessio(Nokia) comments and asks this paper to be noted Ashok (Samsung) comments Peter Hedman (Ericsson) provides comments Kundan(NEC) responds to Genadi. Kundan (NEC) comments Kundan(NEC) asks question to Genadi. Haiyang (Huawei) provides r01 Genadi (Lenovo) comments to Kundan(NEC). Genadi (Lenovo) replies to Kundan(NEC) that the NSSRG applies to Allowed NSSAI and the UE may have one Allowed NSSAI for AT1 and another Allowed NSSAI for AT2. Kundan (NEC) the current specification 23.501 and 24.501 don't allow what you are saying. Please below in details. Genadi (Lenovo) replies to Kundan (NEC). Jinguo(ZTE) provides comment Kundan (NEC) responds to Ashok. Peter Hedman (Ericsson) provides comments and propose we move forward with this CR Ashok (Samsung) suggests a way forward Myungjune comments on way forward proposed by Ashok (Samsung) Ashok (Samsung) responds to Myungjune Alessio(Nokia) cannot accept any revision of this document where there is a concept the Ue needs to wait for NSSAA completion before requesting a new set of slices. we can only accept 9201 approach that is consistent with the behavior when the same S-NSSAI is allowed rather than pending... alessio(Nokia) objects to the approach in this CR as it causes blocking obtaining service. Alessio(Nokia) has problems with this paper being the basis as it is against established 3GPP principle to not delay or potentially block service as already stated, cannot live with this approach. Alessio(Nokia) suggests to keep the discussion focused and not introduce AT distractions... the requested NSSAI is what matters and this is to be irrespective of the Pending NSSAI or allowed NSSAI. Ulises Olvera (InterDigital Inc.) provides comments Jinguo(ZTE) propose a compromise for R17 alessio(nokia) agrees with Ulises(Interdigital) that the only restriction is to ensure the requested NSSAI is made of mutually compatible S-NSSAIs ad we will object to this cR. Peter Hedman (Ericsson) provides reply Peter Hedman (Ericsson) provides reply to Nokia that we should maintain a consistent logic for NSSRG Kundan (NEC) nothing against the 3GPP principle this is following 3GPP specification and GSMA requirement of NSSRG. aligned with stage 3 specification. Mutually exclusive services cannot be attained at the same time. one needs to be dropped. Alessio(Nokia) UE requests compatible slices between themselves at all times. the AMF can allow a pending if compatible with allowed when NSSAA successfully completed, else it will remove from pending the S-NSSAI (if NSSAA does not fails otherwise it rejects the S-NSSAI). there is nothing to add. we have the CR that does this. I stop commenting on this subject as w already said the same thing too many times. Nokia CRs has many issues already highlighted in that thread. Ulises Olvera (InterDigital Inc.) provides reply ==== Revisions Deadline ==== Xiaowen (vivo) provides comments. Kundan(NEC) provides r02. In this revision we have added a condition that UE shall apply the NSSRG rules with respect to pending NSSAI if the UE is interested which is very much aligned with CT1 specification. Kundan(NEC) ask questions to Ulises to understand his comment further. Ulises Olvera (InterDigital Inc.) provides answers to Kundan Kundan (NEC) responds to Xiaowen. Xiaowen (vivo) responds to Kundan. Alessio(Nokia) comment: the fact stage 3 forgot to update this quoted text by kundan on Pnding NSSAI when NSSRG was introduced is undeniable. like we did forget to update our specs. so not sure we can refer to not updated text of CT1 after NSSRG was introduced to resolve this. SA2 anc TCT1 need to resolve the NSSAA and NSSRG feature interaction. we want to do it In a way that des NOT block the Ue to request new services like when the same S-NSSAI is allowed. ==== Final Deadline ==== | Revised |
| 8.4 | S2-2209943 | CR | Approval | 23.501 CR3693R2 (Rel-17, 'F'): Pending NSSAI and NSSRG | NEC, Ericsson, Huawei, HiSilicon, ZTE | Rel-17 | Revision of S2-2209004r02. Approved | Agreed | |
| 8.4 | S2-2209022 | CR | Approval | 23.501 CR3694R1 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.501. | NEC, Ericsson | Rel-17 | Revision of (Postponed) S2-2206652 from S2#152E. Approved. CC#3: This was postponed. | ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 8.4 | S2-2208545 | CR | Approval | 23.501 CR3682R1 (Rel-17, 'F'): UE-Slice-MBR exemption for priority services | Samsung | Rel-17 | Revision of (Postponed) S2-2206034 from S2#152E. CC#3: Postponed | Belen (Ericsson) provides r01 Jinguo(ZTE) provides comment Dongeun (Samsung) replies to Jinguo (ZTE) Dongeun (Samsung) replies to Belen (Ericsson) Haiyang (Huawei) suggests to note this paper Dongeun (Samsung) disagrees to Haiyang (Huawei) Haiyang (Huawei) provides feedback Jinguo(ZTE) replies to Dongeun Dongeun (Samsung) replies to Haiyang (Huawei) and Jinguo (ZTE) Belen (Ericsson) provides comments Dongeun (Samsung) provides r02 alessio(Nokia) comments Belen (Ericsson) provides comments, replies to Samsung as well. Dongeun (Samsung) replies to Belen (Ericsson) and provide r04 ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 8.4 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=4 | - | |
| 8.4 | S2-2208470 | CR | Approval | 23.501 CR3717 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area | NEC | Rel-17 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 8.4 | S2-2208471 | CR | Approval | 23.502 CR3568 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area | NEC | Rel-17 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 8.4 | S2-2208521 | CR | Approval | 23.503 CR0748 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area | NEC | Rel-17 | Not Handled | Mirko (Huawei) comments. ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 8.4 | S2-2208969 | CR | Approval | 23.501 CR3741 (Rel-17, 'F'): Correction to the Target NSSAI feature in RRC redirection | NEC | Rel-17 | Not Handled | Jinguo(ZTE) comments this CR is not handled. Stefano Faccin (Qualcomm) has questions for clarification and concerns ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=7 | - | |
| 8.5 | S2-2208553 | CR | Approval | 23.502 CR3573 (Rel-17, 'F'): Clarification on time synchronization error budget provisioning and ASTI management | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2209569. | Shabnam (Ericsson) provides comments regarding if this is FASMO, if we are to proceed the following comments apply Devaki (Nokia) provides r01 - believes it is a FASMO as current stage 2 has some inconsistencies resulting in ambiguity for stage 3 and implementation. Shabnam (Ericsson) provides comments to remove RAN impacts on cover sheet as there is none, if others don't have any issue on FASMO, I can live with the CR ?? ==== Revisions Deadline ==== Devaki (Nokia) comments that we will remove the RAN impacts from cover page of the final uploaded version of the CR. Thanks! ==== Final Deadline ==== | Revised |
| 8.5 | S2-2209569 | CR | Approval | 23.502 CR3573R1 (Rel-17, 'F'): Clarification on time synchronization error budget provisioning and ASTI management | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2208553r01. Approved | Agreed | |
| 8.5 | S2-2208578 | CR | Approval | 23.502 CR3527R1 (Rel-17, 'F'): Alignment of IIoT related parameter description | Huawei, HiSilicon | Rel-17 | Revision of (Noted) S2-2206052 from S2#152E. r01 agreed. Revised to S2-2209570, merging S2-2208947 | Jari (NTT DOCOMO) comments Mirko (Huawei) provides r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.5 | S2-2209570 | CR | Approval | 23.502 CR3527R2 (Rel-17, 'F'): Alignment of IIoT related parameter description | Huawei, HiSilicon, ZTE, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2208578r01, merging S2-2208947. Approved | Agreed | |
| 8.5 | S2-2208936 | CR | Approval | 23.502 CR3589 (Rel-17, 'F'): Adding SUPI in BSF-DISCOVER output | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Approved | Saso (Intel) provides r01 and cosigns. Devaki (Nokia) comments on r01 (moving all Mandatory parameters to be optional would have backward compatibility issues?) Qianghua (Huawei) provides comments Qianghua (Huawei) provides r02 Shabnam (Ericsson) provides comments isn't this approach too drastic and contradictory to what we usually do? Qianghua (Huawei) agrees with Shabnam and prefers the original. Saso (Intel) withdraws r01; ok with r00. ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.5 | S2-2208522 | CR | Approval | 23.502 CR3570 (Rel-17, 'F'): Correction to BSF service description | Samsung | Rel-17 | Merged into (Covered by) S2-2208936 | Shabnam (Ericsson) proposes to take 8936 as the basis and consider this merged. Sang-Jun (Samsung) confirms 8522 is merged into 8936. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.5 | S2-2208947 | CR | Approval | 23.502 CR3590 (Rel-17, 'F'): Clarification on the AF request Qos procedure. | ZTE | Rel-17 | Merged into S2-2209570 | Mirko (Huawei) suggests to merge this CR into S2-2208578r01. zhendong (ZTE) confirm the merge proposal ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=0 | - | |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=9 | - | |
| 8.7 | S2-2208104 | LS In | Action | LS from CT WG4: LS on UAV authorization container | CT WG4 (C4-223513) | Rel-17 | Revision of Postponed S2-2205417 from S2#152-e. Response drafted in S2-2208295. Final response in S2-2209274 | Replied to | |
| 8.7 | S2-2208295 | LS OUT | Approval | [DRAFT] Reply LS on UAV authorization container | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2208104. r07 agreed. Revised to S2-2209274. | Stefano Faccin (Qualcomm) expresses concerns and proposes R01 Pallab (Nokia) comments on R01 Ashok (Samsung) comments Stefano Faccin (Qualcomm) disagrees Shabnam (Ericsson) provides comments Stefano Faccin (Qualcomm) comments Guanglei (Huawei) provides comments and r02 based on r01 Ashok (Samsung) seeks clarification Pallab (Nokia) comments and provides R03 Guanzhou (InterDigital) can't accept r03. Stefano Faccin (Qualcomm) provides R04 Shabnam (Ericsson) provides comments on the wording see below Pallab (Nokia) responds to Stefano Faccin (Qualcomm) Pallab (Nokia) responds to Shabnam (Ericsson) Shabnam (Ericsson) provides r05 Stefano (Qualcomm) agrees and provides R06 to improve readability. Shabnam (Ericsson) provides comments that maybe there is misunderstanding I understood that payload availability is NOT up to stage 3 since it will be part of the function of the USS/UAS NF and will be forwarded, the only aspect left is payload type is needed or not and that we leave to stage 3. Did I misunderstand that? Stefano (Qualcomm) agrees and provides R07. Pallab (Nokia) is OK with r07 Ashok (Samsung) also fine with r07 Guanzhou (InterDigital) is OK with r07. ==== Revisions Deadline ==== Guanglei (Huawei) is Ok with r07 ==== Final Deadline ==== | Revised |
| 8.7 | S2-2209274 | LS OUT | Approval | Reply LS on UAV authorization container | SA WG2 | Rel-17 | Revision of S2-2208295r07. Approved | Approved | |
| 8.7 | S2-2208137 | LS In | Action | LS from CT WG4: LS on Indication of Network Assisted Positioning method | CT WG4 (C4-224626) | Rel-17 | Postponed | Guanglei (Huawei) comments the corresponding Ls reply is 8744, discussed in 8.14 | Postponed |
| 8.7 | S2-2208296 | CR | Approval | 23.256 CR0068 (Rel-17, 'F'): Corrections to functionality and procedure at UAS NF for C2 authorization | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Postponed | Guanglei (Huawei) comments. Guanzhou (InterDigital) comments and provides r01 Stefano Faccin (Qualcomm) expresses concerns Pallab (Nokia) comments and provide r02 Guanzhou (InterDigital) responds to Pallab (Nokia) and can't accept r02. Pallab (Nokia) comments and provide r03 and r04. Prefers r04 Guanzhou (InterDigital) provides r05. Shabnam (Ericsson) provides comments that we can not accept r05 and comments on proposal Guanzhou (InterDigital) responds to Shabnam (Ericsson). Shabnam (Ericsson) provides comments that the case we are trying to address and CT1 spec in our view needs to be updated and aligned with stage 2 and CT4 discussion. Pallab (Nokia) responds to Guanzhou (InterDigital) Stefano (Qualcomm) asks for clarification on what revision might be acceptable. We see technical concerns with all. Pallab (Nokia) is OK to postpone the CR if there is no agreeable revision Guanzhou (InterDigital) also thinks the CR should be postponed. Shabnam (Ericsson) ok to postpone but we need to come back to this and correct stage 2 consistency, we don't want Rel-18 to be built on misleading text. ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 8.7 | S2-2208843 | CR | Approval | 23.256 CR0070 (Rel-17, 'F'): Aerial Subscription Update | Samsung | Rel-17 | r03 agreed. Revised to S2-2209275. | Guanglei (Huawei) comments. Shabnam (Ericsson) provides comments regarding potential alternative solns and Objects to current approach in these CRs as not suitable for the subscription handling. Ashok (Samsung) comments. Ashok (Samsung) provides r01. Dimitris (Lenovo) has a question for clarification Ashok (Samsung) responds to Dimitris (Lenovo) Stefano (Qualcomm) responds to Ashok (Samsung) Stefano (Qualcomm) asks question for clarification. Ashok (Samsung) agrees to Stefano (Qualcomm) comment and removed the NOTE and provides r02 Ashok (Samsung) provides r03 Shabnam (Ericsson) provides comments , thanks we would be ok and please also update 23.502 and correct one UCU left ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.7 | S2-2209275 | CR | Approval | 23.256 CR0070R1 (Rel-17, 'F'): Aerial Subscription Update | Samsung | Rel-17 | Revision of S2-2208843r03. Approved | Agreed | |
| 8.7 | S2-2208866 | CR | Approval | 23.502 CR3586 (Rel-17, 'F'): Aerial Subscription Update | Samsung | Rel-17 | r01 agreed. Revised to S2-2209276. | Shabnam (Ericsson) provides comments to follow potential soln option as indicated in the thread of document 8843 and objects to the soln in this CR Ashok (Samsung) provides r01 which is inline with 8843 paper discussion ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.7 | S2-2209276 | CR | Approval | 23.502 CR3586R1 (Rel-17, 'F'): Aerial Subscription Update | Samsung | Rel-17 | Revision of S2-2208866r01. Approved | Agreed | |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=27 | - | |
| 8.8 | - | - | - | Discovery message cast type | - | - | Docs:=6 | - | |
| 8.8 | S2-2208106 | LS In | Action | LS from RAN WG2: LS on Cast Type for Discovery message | RAN WG2 (R2-2206391) | Rel-17 | Revision of Postponed S2-2205424 from S2#152-e. Responses drafted in S2-2208515, S2-2209064. Final response in S2-2209277 | Replied to | |
| 8.8 | S2-2208515 | LS OUT | Approval | [DRAFT] Reply LS on Cast Type for Discovery message | OPPO | Rel-17 | Revision of (Noted) S2-2205994 from S2#152E. Response to S2-2208106. Noted | Hannu (Nokia) proposes to note this LS and to proceed as suggested in S2-2209064 which is better aligned with the existing SA2 specifications. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.8 | S2-2209064 | LS OUT | Approval | [DRAFT] Reply LS on Cast Type for Discovery message | Qualcomm Incorporated | Rel-17 | Response to S2-2208106. r03 agreed. Revised to S2-2209277. | Fei (OPPO) comments and provides r01. Hannu (Nokia) provides r02. Fei (OPPO) comments and provides r03. ==== Revisions Deadline ==== Hannu (Nokia) thanks Fei for the update and supports r03. ==== Final Deadline ==== | Revised |
| 8.8 | S2-2209277 | LS OUT | Approval | Reply LS on Cast Type for Discovery message | SA WG2 | Rel-17 | Revision of S2-2209064r03. Approved | Approved | |
| 8.8 | S2-2208513 | DISCUSSION | Discussion | Cast type for direct discovery. | OPPO | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.8 | S2-2208514 | CR | Approval | 23.304 CR0108R1 (Rel-17, 'F'): Cast Type for Discovery message | OPPO | Rel-17 | Revision of (Noted) S2-2205993 from S2#152E. Noted | Hannu (Nokia) proposes to note the document as there is neither requirement nor criteria for the upper layers to determine the cast type. Fei (OPPO) responds to Hannu (Nokia) Hong (Qualcomm) proposes to NOTE the CR. Hannu (Nokia) shares the view of Hong that SA2 hasn't got any requirement but only a question from RAN2 in their LS and we need to reply based on our specifications. Sudeep (Apple) agrees with Hannu (Nokia) and Hong (Qualcomm) and proposes to NOTE this CR. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.8 | - | - | - | 5G DDNMF discovery | - | - | Docs:=4 | - | |
| 8.8 | S2-2208122 | LS In | Action | LS from CT WG1: LS on 5G DDNMF discovery | CT WG1 (C1-225229) | Rel-17 | Response drafted in S2-2208600. Final response in S2-2209261 | Replied to | |
| 8.8 | S2-2208600 | LS OUT | Approval | [DRAFT] Reply LS on 5G DDNMF Discovery | ZTE | Rel-17 | Response to S2-2208122. r00 agreed. Revised to S2-2209261. | ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.8 | S2-2209261 | LS OUT | Approval | Reply LS on 5G DDNMF Discovery | SA WG2 | Rel-17 | Revision of S2-2208600r00. Approved | Approved | |
| 8.8 | S2-2208599 | CR | Approval | 23.304 CR0119 (Rel-17, 'F'): Add 5G DDNMF Address in Parameter Provisioning for 5G ProSe Direct Discovery | ZTE, Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.8 | - | - | - | Policy request during registration procedure | - | - | Docs:=7 | - | |
| 8.8 | S2-2208128 | LS In | Action | LS from CT WG1: LS on V2X policy or ProSe policy request during registration procedure | CT WG1 (C1-225451) | Rel-17 | Responses drafted in S2-2208355, S2-2208700. Postponed | Postponed | |
| 8.8 | S2-2208355 | LS OUT | Approval | [DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure | LG Electronics | Rel-17 | Response to S2-2208128. Noted | Susan (Huawei) proposes to either merge this draft LS to S2-2208700 or note this paper . Hong (Qualcomm) replies to Susan. Susan (Huawei) replies to Hong (Qualcomm). Hannu (Nokia) asks whether we are discussing the removal of the Rel-17 requirement or including it in Rel-18? ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.8 | S2-2208700 | LS OUT | Approval | [DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure | Huawei, HiSilicon | Response to S2-2208128. Noted | LaeYoung (LGE) thinks that this LS may be not needed depending on the discussion outcome for 8356/8357. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted | |
| 8.8 | S2-2208356 | CR | Approval | 23.503 CR0743 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure | Ericsson, LG Electronics, CATT, Huawei, ZTE | Rel-17 | Postponed | Susan (Huawei) provides r01. Hannu (Nokia) supports r01. The cover page update is needed as in the absence of any Rel-18 TS version, we can only decide on Rel-17 in this meeting. Judy (Ericsson) responds to Hannu (Nokia) and Susan (Huawei) and provides r02. Hong (Qualcomm) objects r01. Judy (Ericsson) provides r03 (please ignore r02) Sherry (Xiaomi) comments. Hannu (Nokia) asks whether we can postpone this Rel-17 proposal until Rel-18 TS version exists? ==== Revisions Deadline ==== LaeYoung (LGE) proposes to get this CR POSTPONED because 8357 covering same topic (so coupled together) is postponed. Judy (Ericsson) agrees to postpone this CR until TS spec for Rel-18 is available Hannu (Nokia) adds the comment for the minutes that SA2 did not challenge the applicability of this CR to Rel-17. The CR is postponed to allow us apply it only on Rel-17 without impacting Rel-18. ==== Final Deadline ==== | Postponed |
| 8.8 | S2-2208357 | CR | Approval | 23.304 CR0115 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure | Ericsson, LG Electronics, CATT, Huawei, ZTE | Rel-17 | Postponed | Susan (Huawei) provides r01. Hannu (Nokia) supports r01 as in the absence of any Rel-18 TS, we can't decide on Rel-18 yet. Hong (Qualcomm) objects to r01. Judy (Ericsson) provides r02 to allow the work to be continued in Rel-18 Hong (Qualcomm) is fine with r02. Hannu (Nokia) proposes to postpone the CR on the grounds explained in S2-2208356 discussion thread. Judy (Ericsson) responds to Hannu (Nokia) and OK to postpone ==== Revisions Deadline ==== Hannu (Nokia) adds the comment for the minutes that SA2 did not challenge the applicability of this CR to Rel-17. The CR is postponed to allow us apply it only on Rel-17 without impacting Rel-18. ==== Final Deadline ==== | Postponed |
| 8.8 | S2-2208482 | CR | Approval | 23.304 CR0116 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure | CATT | Rel-17 | Merged into (Covered by) S2-2208357 | Deng Qiang (CATT) this paper can be merged into S2-2208357. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.8 | S2-2208483 | CR | Approval | 23.503 CR0747 (Rel-17, 'F'): Removal of V2X/ProSe policy request during registration procedure | CATT | Rel-17 | Merged into (Covered by) S2-2208356 | Deng Qiang (CATT) this paper can be merged into S2-2208356. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.8 | - | - | - | RRC estbl cause | - | - | Docs:=1 | - | |
| 8.8 | S2-2208129 | LS In | Information | LS from CT WG1: LS on setting RRC establishment cause value when relay UE has its own service | CT WG1 (C1-225453) | Rel-17 | Noted | Deng Qiang (CATT) this LS In is for information and can be noted. | Noted |
| 8.8 | - | - | - | Secondary authentication | - | - | Docs:=3 | - | |
| 8.8 | S2-2208153 | LS In | Information | LS from SA WG3: LS Reply on Reply LS on 5G ProSe security open items | SA WG3 (S3-222434) | Rel-17 | Response drafted in S2-2208359. Postponed | Postponed | |
| 8.8 | S2-2208359 | LS OUT | Approval | [DRAFT] Reply to 5G ProSe security open items | Ericsson | Rel-17 | Response to S2-2208153. Noted | Hannu (Nokia) has got concerns on SA2 telling SA3 what kind of security work they can do. Asking technical questions is of course fine. Judy (Ericsson) provides r01 Steve (Huawei) comments Jungje (Interdigital) comments Judy (Ericsson) responds to Steve (Huawei) and Jungje (Interdigital) Jungje(Interdigital) comments Judy (Ericsson) Hannu (Nokia) is concerned that the LS is not asking SA3 guidance on SA2 specifications but micro-managing SA3 work from SA2. Judy (Ericsson) responds to Jungje(Interdigital) that SA2 is in To but not CCed, and responds to Hannu (Nokia) that inclusion of the draft CR in SA3 LS is for feedback if any and as such no micro managing other WGs work Hong (Qualcomm) comments. Jungje(Interdigital) responds to Judy (Ericsson) Fei (OPPO) comments and provides r02. Judy (Ericsson) provides r03 with wording update Jungje(Interdigital) responds Judy(Ericsson) ==== Revisions Deadline ==== Jungje (Interdigital) responds to Judy(Ericsson) and propose to note. Oppose to original and any version. Judy (Ericsson) responds to Jungje (Interdigital) ==== Final Deadline ==== | Noted |
| 8.8 | S2-2208358 | DISCUSSION | Decision | Discussion of 5G ProSe security open item for L3 Remote UE's secondary AA. | Ericsson | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted | |
| 8.8 | - | - | - | Corrections | - | - | Docs:=6 | - | |
| 8.8 | S2-2208516 | CR | Approval | 23.304 CR0117 (Rel-17, 'F'): Clarification on DCR message for DRX | OPPO | Rel-17 | Merged into S2-2209279 | LaeYoung (LGE) replies to Fei (OPPO). Fei (OPPO) responds to LaeYoung (LGE) LaeYoung (LGE) comments and proposes to MERGE this CR to S2-2208581. Hong (Qualcomm) comments and also thinks separate TX Profile for DCR is not needed. Hannu (Nokia) supports the proposed merging of this document to S2-2208581. Fei (OPPO) responds and fine to NOTE/merge this CR. LaeYoung (LGE) replies to Fei (OPPO), Hannu (Nokia) and Hong (Qualcomm). Wen (vivo) replies. Hong (Qualcomm) comments. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.8 | S2-2208581 | CR | Approval | 23.304 CR0118 (Rel-17, 'F'): Clarifications on PC5 DRX operations | Vivo, LG Electronics | Rel-17 | r01 agreed. Revised to S2-2209279, merging S2-2208516 | Fei (OPPO) provides r01 LaeYoung (LGE) is OK with r01. Hannu (Nokia) supports r01 and considers it reasonable to call the other paper as merged to this one. ==== Revisions Deadline ==== Wen (vivo) is OK with r01. ==== Final Deadline ==== | Revised |
| 8.8 | S2-2209279 | CR | Approval | 23.304 CR0118R1 (Rel-17, 'F'): Clarifications on PC5 DRX operations | Vivo, LG Electronics | Rel-17 | Revision of S2-2208581r01, merging S2-2208516. Approved | Agreed | |
| 8.8 | S2-2208908 | CR | Approval | 23.304 CR0120 (Rel-17, 'F'): Correction on PC5 link release indication | Huawei, HiSilicon, vivo | Rel-17 | r01 agreed. Revised to S2-2209280. | Judy (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.8 | S2-2209280 | CR | Approval | 23.304 CR0120R1 (Rel-17, 'F'): Correction on PC5 link release indication | Huawei, HiSilicon, vivo | Rel-17 | Revision of S2-2208908r01. Approved | Agreed | |
| 8.8 | S2-2209138 | CR | Approval | 23.304 CR0121 (Rel-18, 'F'): Updates to Control Plane based security procedures for 5G ProSe UE-to-Network Relay | Xiaomi | Rel-18 | CR Number missing! Noted | Judy (Ericsson) comments Judy (Ericsson) provides r01 Fei (OPPO) comments. Steve (Huawei) Some small hiccup, the comment from Judy is not about S2-2209138. Steve (Huawei) comments Judy (Ericsson) thanks Steve (Huawei) and corrects that no revison is provided to 9138. Sherry (Xiaomi) replies, and proposes to send a LS to SA3 to confirm whether both user plane based solution and control based solution are supported for 5G ProSe discovery. Sherry (Xiaomi) proposes to send a LS to SA3 to confirm whether 5G ProSe relay discovery security have two options of user plane based solution and control based solution. Deng Qiang (CATT) comments. Fei (OPPO) provides comments. ==== Revisions Deadline ==== Deng Qiang (CATT) think this CR should be NOTED. ==== Final Deadline ==== | Noted |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=40 | - | |
| 8.9 | - | - | - | 5MBS User Services | - | - | Docs:=9 | - | |
| 8.9 | S2-2208108 | LS In | Action | LS from SA WG4: Reply LS on 5MBS User Services | SA WG4 (S4-220828) | Rel-17 | Revision of Postponed S2-2205450 from S2#152-e. Responses drafted in S2-2208329, S2-2208720. Final response in S2-2209281 | Replied to | |
| 8.9 | S2-2208329 | LS OUT | Approval | [DRAFT] Reply LS on 5MBS User Services | Ericsson, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2208108. r02 agreed. Revised to S2-2209281, merging S2-2208720 | Robbie (Ericsson) clarifies to LiMeng (Huawei). LiMeng (Huawei) comments and provides r01 Miguel (Qualcomm) comments Robbie (Ericsson) provides r02. Peng Tan (TELUS) request clarification and put further comments on r02 Robbie (Ericsson) replies to Peng Tan (TELUS). ==== Revisions Deadline ==== Peng Tan (TELUS) provides further comments Peng (TELUS) replies to Robbie (Ericsson) ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209281 | LS OUT | Approval | Reply LS on 5MBS User Services | SA WG2 | Rel-17 | Revision of S2-2208329r02, merging S2-2208720. Approved | Approved | |
| 8.9 | S2-2208951 | CR | Approval | 23.247 CR0129R1 (Rel-17, 'F'): Clarification on the traffic handling in MBSTF for interworking | ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm | Rel-17 | Revision of (Postponed) S2-2206206 from S2#152E. CR Revision incorrect: -1! r04 agreed. Revised to S2-2209282. | LiMeng (Huawei) provides r01 Miguel (Qualcomm) responds to LiMeng (Huawei) finds no merit for r01, supports r00 Thomas(Nokia) raises concerns against r01 zhendong (ZTE) share the similar view with qualcomm and nokia Robbie (Ericsson) prefers r00. LiMeng (Huawei) responds and provides r02. zhendong (ZTE) provides r03 Robbie (Ericsson) provides r04. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209282 | CR | Approval | 23.247 CR0129R2 (Rel-17, 'F'): Clarification on the traffic handling in MBSTF for interworking | ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm | Rel-17 | Revision of S2-2208951r04. Approved | Agreed | |
| 8.9 | S2-2208720 | LS OUT | Approval | [DRAFT] Reply LS on MBS user service | Huawei, HiSilicon | Rel-17 | Response to S2-2208108. Merged into S2-2209281 | LiMeng (Huawei) is fine use the email thread of S2-2208329 for discussions Thomas (Nokia) suggest to use S2-2208329 as basis for discussions Robbie (Ericsson) suggests marking it as merged into S2-2208329 LiMeng (Huawei) agrees to merge this document into S2-2208329 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | S2-2208718 | DISCUSSION | Discussion | Discussion on MBS user service. | Huawei, HiSilicon | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.9 | S2-2208115 | LS In | Information | LS on modifications to MBS User Services architecture | SA WG4 (S4-221119) | Rel-17 | Revision of Postponed S2-2208096 from S2#152-e. Noted | Robbie (Ericsson) suggests marking it as NOTED | Noted |
| 8.9 | S2-2208131 | LS In | Information | LS from CT WG3: Reply LS on 5MBS User Services | CT WG3 (C3-224655) | Rel-17 | Noted | Robbie (Ericsson) suggests marking it as NOTED | Noted |
| 8.9 | - | - | - | Multicast MBS session Deactivation and Reactivation | - | - | Docs:=8 | - | |
| 8.9 | S2-2208136 | LS In | Action | LS from CT WG4: LS on Multicast MBS session Deactivation and Reactivation | CT WG4 (C4-224417) | Rel-17 | Responses drafted in S2-2208201, S2-2208328, S2-2208897. Final response in S2-2209283 | Robbie (Ericsson) provides comments Fenqin (Huawei) provides comments Thomas (Nokia) suggest this thread as basis for discussions Thomas (Nokia) replies to Fenqin Fenqin (Huawei) provides feedback Thomas(Nokia) replies to Fenqin Fenqin (Huawei) replies to Thomas Fenqin (Huawei) further replies to Thomas Thomas(Nokia) replies to Robbie Robbie (Ericsson) replies to Thomas(Nokia) Fenqin (Huawei) replies to Thomas(Nokia) | Replied to |
| 8.9 | S2-2208201 | LS OUT | Approval | [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation | Nokia, Nokia Shanghai-Bell | Rel-17 | Response to S2-2208136. Merged into S2-2209283 | Fenqin (Huawei) suggest to merge this LS to 8897 and take 8897 as base line. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | S2-2208328 | LS OUT | Approval | [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation | Ericsson | Rel-17 | Response to S2-2208136. Merged into S2-2209283 | Fenqin (Huawei) suggest to merge this LS to 8897 and take 8897 as base line. Robbie (Ericsson) confirms it is merged into 8897. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | S2-2208897 | LS OUT | Approval | [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation | Huawei, HiSilicon | Rel-17 | Response to S2-2208136. r04 agreed. Revised to S2-2209283, merging S2-2208201 and S2-2208328 | Fenqin (Huawei) provides r01 Thomas (Nokia) provides r02 Fenqin (Huawei) provides r03 Robbie (Ericsson) provides r04 Fenqin (Huawei) is fine with r04 Thomas (Nokia) is fine with r04 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209283 | LS OUT | Approval | Reply LS on Multicast MBS session Deactivation and Reactivation | SA WG2 | Rel-17 | Revision of S2-2208897r04, merging S2-2208201 and S2-2208328. Approved | Approved | |
| 8.9 | S2-2208200 | CR | Approval | 23.247 CR0134 (Rel-17, 'F'): Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation | Nokia, Nokia Shanghai-Bell | Rel-17 | r07 agreed. Revised to S2-2209284, merging S2-2208331 | Thomas (Nokia) provides r01 to capture results of offline discussions Robbie (Ericsson) provides r02, merge in S2-2208331 Thomas (Nokia) provides r03 Fenqin (Huawei) provides r04 Robbie (Ericsson) provides r05 Thomas (Nokia) is fine with r04 zhendong (ZTE) is fine with r04 Fenqin (Huawei) is not ok with r05 and provide r06. Youngkyo(Samsung) provides a comment. Robbie (Ericsson) provides r07, including the comments from Youngkyo(Samsung). Fenqin (Huawei) provide response to Youngkyo. Robbie (Ericsson) replies to Fenqin (Huawei). Thomas (Nokia) can accept r07 ==== Revisions Deadline ==== Fenqin (Huawei) we are fine with r07 ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209284 | CR | Approval | 23.247 CR0134R1 (Rel-17, 'F'): Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation | Nokia, Nokia Shanghai-Bell, Ericsson, Huawei | Rel-17 | Revision of S2-2208200r07, merging S2-2208331. Approved | Agreed | |
| 8.9 | S2-2208331 | CR | Approval | 23.247 CR0136 (Rel-17, 'F'): Clarification on MBS session activation and deactivation | Ericsson | Rel-17 | Merged into S2-2209284 | Thomas (Nokia) suggest to consider this CR as merged into S2-2208200 Robbie (Ericsson) confirms this CR is merged into S2-2208200 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | - | - | - | shared NG-U Termination among gNBs | - | - | Docs:=8 | - | |
| 8.9 | S2-2208148 | LS In | Information | LS from RAN WG3: LS on shared NG-U Termination among gNBs | RAN WG3 (R3-225247) | Rel-17 | Responses drafted in S2-2208722, S2-2208950. Final response in S2-2209285 | Replied to | |
| 8.9 | S2-2208722 | LS OUT | Approval | [DRAFT] Reply LS on Common CU-UP | Huawei, HiSilicon | Rel-17 | Response to S2-2208148. Merged into S2-2209285 | Thomas (Nokia) suggest to merge into S2-2208950 LiMeng (Huawei) is fine with the merging proposal. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | S2-2208950 | LS OUT | Approval | [DRAFT] Reply LS on shared NG-U Termination among gNBs | ZTE | Rel-17 | Response to S2-2208148. r03 agreed. Revised to S2-2209285, merging S2-2208722 | Fenqin (Huawei) provides the r01 zhendong (ZTE) provides r02 Robbie (Ericsson) provides r03 zhendong (ZTE) provides the response ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209285 | LS OUT | Approval | Reply LS on shared NG-U Termination among gNBs | SA WG2 | Rel-17 | Revision of S2-2208950r03, merging S2-2208722. Approved | Approved | |
| 8.9 | S2-2208721 | DISCUSSION | Discussion | Discussion on the issue of shared NG-U Termination among gNBs. | Huawei, HiSilicon | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.9 | S2-2208948 | DISCUSSION | Discussion | Discussion on the common UP issue raised by RAN WG3 for shared delivery establishment management. | ZTE | Rel-17 | Noted | ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 8.9 | S2-2208949 | CR | Approval | 23.247 CR0141 (Rel-17, 'F'): Clarification on the shared delivery tunnel management for common gNB UP case | ZTE | Rel-17 | r10 agreed. Revised to S2-2209286. | zhendong (ZTE) provides the response zhendong (ZTE) comments Robbie (Ericsson) provides r02 Thomas (Nokia) provides r01 Fenqin (Huawei) provides the comment and r03 Thomas (Nokia) provides r04 and raises concerns against r03 Thomas (Nokia) provides r05 as alternative to r04 Prefers r04 but can also accept r05 Fenqin(Huawei) provides r06 zhendong (ZTE) provides r07 Robbie (Ericsson) provides r08. Fenqin(Huawei) is fine with r08 zhendong (ZTE) reply to robbie(Ericsson) Robbie (Ericsson) replies to zhendong (ZTE) Thomas (Nokia) provides r09, raises concerns about r08 Robbie (Ericsson) provides r10 Thomas (Nokia) is fine with r10 Fenqin(Huawei) is fine with r10 zhendong (ZTE) is fine with r10 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209286 | CR | Approval | 23.247 CR0141R1 (Rel-17, 'F'): Clarification on the shared delivery tunnel management for common gNB UP case | ZTE, Nokia, Nokia Shanghai-Bell, Ericsson, Huawei | Rel-17 | Revision of S2-2208949r10. Approved | Agreed | |
| 8.9 | - | - | - | Other LSs | - | - | Docs:=6 | - | |
| 8.9 | S2-2208152 | LS In | Action | LS from SA WG3: Reply LS on the impact of MSK update on MBS multicast session update procedure | SA WG3 (S3-222391) | Rel-17 | Response drafted in S2-2208327. Final response in S2-2209287 | Replied to | |
| 8.9 | S2-2208327 | LS OUT | Approval | [DRAFT] Reply LS on the impact of MSK update on MBS multicast session update procedure | Ericsson | Rel-17 | Response to S2-2208152. r01 agreed. Revised to S2-2209287. | Fenqin (Huawei) provides r01 Robbie (Ericsson) is fine with r01 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209287 | LS OUT | Approval | Reply LS on the impact of MSK update on MBS multicast session update procedure | SA WG2 | Rel-17 | Revision of S2-2208327r01. Approved | Approved | |
| 8.9 | S2-2208124 | LS In | Information | LS from CT WG1: Reply LS on AS-NAS layer interactions for MBS | CT WG1 (C1-225249) | Rel-17 | Noted | Robbie (Ericsson) suggests marking it as NOTED | Noted |
| 8.9 | S2-2208141 | LS In | Information | LS from RAN WG2: Reply LS on the MBS broadcast service continuity and MBS session identification | RAN WG2 (R2-2208885) | Rel-17 | Noted | Robbie (Ericsson) suggests marking it as NOTED | Noted |
| 8.9 | S2-2208146 | LS In | Information | LS from RAN WG3: Response LS on Support of Broadcast and Multicast MBS sessions with AMF Set | RAN WG3 (R3-225165) | Rel-17 | Noted | Robbie (Ericsson) suggests marking it as NOTED | Noted |
| 8.9 | - | - | - | CRs | - | - | Docs:=8 | - | |
| 8.9 | S2-2208330 | CR | Approval | 23.247 CR0135 (Rel-17, 'F'): Missing NID in output parameters to AF for SNPN | Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.9 | S2-2208577 | CR | Approval | 23.247 CR0137 (Rel-17, 'F'): Clean-up of PCC procedures for 5MBS | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2209288. | Judy (Ericsson) provides r01 Thomas(Nokia) comments Judy (Ericsson) responds to Thomas(Nokia) Thomas(Nokia) provides r02 ==== Revisions Deadline ==== Judy (Ericsson) is fine with r02 ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209288 | CR | Approval | 23.247 CR0137R1 (Rel-17, 'F'): Clean-up of PCC procedures for 5MBS | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2208577r02. Approved | Agreed | |
| 8.9 | S2-2208723 | CR | Approval | 23.247 CR0139 (Rel-17, 'F'): CR on MTK or MSK processing | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2209289. | Robbie (Ericsson) asks for clarification LiMeng (Huawei) thanks for r01, but it seems that the link is broken. Thomas (Nokia) provides r01 Thomas(Nokia) replies that link now works. Thomas (Nokia) replies to Robbie LiMeng (Huawei) replies to Thomas and Robbie. Robbie (Ericsson) provides r02 and replies to LiMeng (Huawei) and Thomas (Nokia) LiMeng (Huawei) asks questions Robbie (Ericsson) replies to LiMeng (Huawei) Thomas (Nokia) is fine with r02 and replies to LiMeng and Robbie ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.9 | S2-2209289 | CR | Approval | 23.247 CR0139R1 (Rel-17, 'F'): CR on MTK or MSK processing | Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson | Rel-17 | Revision of S2-2208723r02. Approved | Agreed | |
| 8.9 | S2-2208170 | CR | Approval | 23.247 CR0133R1 (Rel-17, 'F'): Alignment with SA WG4 work on MBS service announcements | Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of (postponed) S2-2207689 from S2-152E. CC#3: Postponed to CC#4. CC#4: No consensus. Noted | Robbie (Ericsson) comments that S2-2208170 and S2-2208840 are competing, and we need to find a way forward. ==== Revisions Deadline ==== Haris(Qualcomm) proposes to NOTE S2-2208170 and move ahead with S2-2208840 Youngkyo(Samsung) shares the view with Haris(Qualcomm). Robbie (Ericsson) supports Haris(Qualcomm) to note this CR and move ahead with S2-2208840 Thomas(Nokia) suggest bringing both S2-2208170 and S2-2208840 to CC2 as they are competing proposals ==== Final Deadline ==== Thomas(Nokia) provides late r01 | Noted |
| 8.9 | S2-2208840 | CR | Approval | 23.247 CR0140 (Rel-17, 'F'): Alignment with stage-3 for USD and service announcement | Qualcomm Incorporated | Rel-17 | CC#3: Postponed to CC#4. CC#4: No consensus. Noted | Robbie (Ericsson) supports this CR, and adds Ericsson as co-source in r01. LiMeng (Huawei) objects to the proposal. Youngkyo(Samsung) supports wayforward of this CR and provide r02. Leo (Deutsche Telekom) proposes to NOTE this LS, and use S2-2208812 Haris(Qualcomm) responds to LiMeng (Huawei) Haris(Qualcomm) provides r03 ==== Revisions Deadline ==== Wanqiang(Huawei) objects the proposal (any revision). Kaixin (CBN) objects to the proposal. Zhendong (ZTE) agrees with Wanqiang (Huawei), proposes to Note this CR. Haris(Qualcomm) suggests to discuss in CC#2 Antoine (Orange) supports r03. ==== Final Deadline ==== | Noted |
| 8.9 | S2-2209198 | CR | Approval | 23.247 CR0142 (Rel-17, 'F'): Update on service announcement/pre-configuration description | Samsung | Rel-17 | Merged into (Covered by) S2-2208840 | Robbie (Ericsson) suggests merging it to S2-2208840 Thomas (Nokia) suggest to consider this CR covered by S2-2208840or S2-2208170 Youngkyo(Samsung) is okay to handle this issue S2-2208840 instead of me to be continued from the previous meeting. Youngkyo(Samsung) is okay with merging it to S2-2208840 Thomas (Nokia) suggest to consider this CR covered by S2-2208840 or S2-2208170 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 8.9 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=1 | - | |
| 8.9 | S2-2208719 | CR | Approval | 23.247 CR0138 (Rel-17, 'F'): CR on MBS user service | Huawei, HiSilicon | Rel-17 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=0 | - | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=2 | - | |
| 8.11 | S2-2208121 | LS In | Action | LS from CT WG1: LS on UE selecting a non-allowed TAI in satellite access broadcasting multiple TACs per cell | CT WG1 (C1-225160) | Rel-17 | Noted | Steve (Huawei) comments Jean Yves (Thales) comments Stefan (Ericsson) provides comments Hannu (Nokia) proposes to note the LS and agrees the interpretation suggested by Jean Yves and Stefan. Yuxin (Xiaomi) supports to note the LS and provides comments. Chris (Vodafone) is also Ok to note the LS. The example looks like network misconfiguration. | Noted |
| 8.11 | S2-2208135 | LS In | Information | LS from CT WG4: Reply LS on Nudm_UEContextManagement service for satellite NG-RAN | CT WG4 (C4-224409) | Rel-17 | Noted | Jean-Yves (Thales) proposes to note this LS which is for information Steve (Huawei) agrees about noting. We can note it. | Noted |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=4 | - | |
| 8.12 | S2-2208165 | LS In | Information | LS from RAN WG2: LS on TX profile | RAN WG2 (R2-2208853) | Rel-17 | Noted | LaeYoung (LGE) proposes to NOTE this LS because this LS is for Information thus no action is needed in SA2. | Noted |
| 8.12 | S2-2208306 | CR | Approval | 23.287 CR0185 (Rel-17, 'F'): Clarification on the PC5 DRX operation for Groupcast | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2209571. | LaeYoung (LGE) provides r02. LaeYoung (LGE) provides r01, and replies to Wen (vivo) and Fei (OPPO). Fei (OPPO) comments on r01. Wen(vivo) comments. LaeYoung (LGE) provides r01. LiMeng (Huawei) is fine with r02. LaeYoung (LGE) thanks to LiMeng (Huawei) for checking and confirming r02. :) ==== Revisions Deadline ==== Fei (OPPO) is fine with r02. ==== Final Deadline ==== | Revised |
| 8.12 | S2-2209571 | CR | Approval | 23.287 CR0185R1 (Rel-17, 'F'): Clarification on the PC5 DRX operation for Groupcast | Huawei, HiSilicon | Rel-17 | Revision of S2-2208306r02. Approved | Agreed | |
| 8.12 | S2-2208481 | CR | Approval | 23.287 CR0186 (Rel-17, 'F'): Removal of V2X policy request during registration procedure | CATT | Rel-17 | Postponed | LaeYoung (LGE) thanks to Deng Qiang (CATT) and let's merge this CR to S2-2208174. Deng Qiang (CATT) is fine to discuss this issue under AI#7.1, and this paper can be merged into S2-2208174. LaeYoung (LGE) suggests to discuss this issue under AI#7.1 (with S2-2208174). ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=8 | - | |
| 8.14 | S2-2208743 | CR | Approval | 23.273 CR0234 (Rel-17, 'F'): Support an indication of reliable UE location information requirement | Huawei, HiSilicon | Rel-17 | Bad WI Code! Noted | Stephen (Qualcomm) provides an r01 Guanglei (Huawei) provides r02 to correct WI code. Stephen (Qualcomm) flags the r01 with the correct agenda item in the subject line Ming (CATT) comments and provides r03. Stephen (Qualcomm) provides comments and an r04 Guanglei (Huawei) can live with r04 ==== Revisions Deadline ==== Stephen (Qualcomm) can agree r01, r02 or r04 but not r00 or r03 Ming (CATT) comments, can only accept r03 for this meeting. Suggests that SA2 checks SA3 on whether the measurement from UE is trusted or not, and align SA2 spec accordingly in future meeting, if necessary. Guanglei (Huawei) understand the concern from Ming(CATT), supports r03 for the sake of future proof. If the discussion on NTN has conclusion that the UE-based measurement is also trusted, we can further revise SA2/SA3 UAS/LCS specifications. Leo (Deutsche Telekom) supports r03 and considers UE provided information as not reliable. ==== Final Deadline ==== | Noted |
| 8.14 | S2-2208742 | CR | Approval | 23.256 CR0069 (Rel-17, 'F'): Indication of Network Assisted Positioning method for UAV positioning | Huawei, HiSilicon | Rel-17 | Bad WI Code! r01 agreed. Revised to S2-2209572. | Guanglei (Huawei) provides r01 to correct WI code. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 8.14 | S2-2209572 | CR | Approval | 23.256 CR0069R1 (Rel-17, 'F'): Indication of Network Assisted Positioning method for UAV positioning | Huawei, HiSilicon | Rel-17 | Revision of S2-2208742r01. Approved | Agreed | |
| 8.14 | S2-2208744 | LS OUT | Approval | [DRAFT] LS reply on Indication of Network Assisted Positioning method | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2209573. CC#3: This LS was postponed and S2-2209573 was withdrawn | Leo (Deutsche Telekom) provides r01 and comments that incoming LS S2-2208137 is in AI#8.7 Leo (Deutsche Telekom) provides link to r01 ==== Revisions Deadline ==== Guanglei (Huawei) is fine with r01 ==== Final Deadline ==== | Postponed |
| 8.14 | S2-2209573 | LS OUT | Approval | [DRAFT] LS reply on Indication of Network Assisted Positioning method | Huawei, HiSilicon | Rel-17 | Revision of S2-2208744r01. CC#3: WITHDRAWN | Withdrawn | |
| 8.14 | S2-2209074 | CR | Approval | 23.273 CR0235 (Rel-17, 'F'): Update of GNSS integrity requirement provisioing | Huawei, HiSilicon | Rel-17 | Postponed | Cai Simon (Nokia) provides comments Stephen (Qualcomm) provides comments Runze (Huawei) replies to Stephen (Qualcomm). Runze (Huawei) replies to Simon (Nokia). Cai Simon (Nokia) replies to Runze (Huawei) Runze (Huawei) agrees with Cai Simon (Nokia) and provides r01. ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to postpone the CR and agrees with Runze (Huawei) to consult RAN2 ==== Final Deadline ==== | Postponed |
| 8.14 | S2-2210162 | LS OUT | Approval | [DRAFT] LS on GNSS integrity requirement provisioning | Huawei | CC#4: r00 agreed. Revised to S2-2209966. | Runze (Huawei) provides r00 of S2-2210162 in the revision folder. | Revised | |
| 8.14 | S2-2209966 | LS OUT | Approval | LS on GNSS integrity requirement provisioning | SA WG2 | - | Revision of S2-2210162r00. Approved | Approved | |
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=0 | - | |
| 8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | Docs:=0 | - | |
| 8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | Docs:=0 | - | |
| 8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | Docs:=0 | - | |
| 8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | Docs:=0 | - | |
| 8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | Docs:=0 | - | |
| 8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | Docs:=0 | - | |
| 8.22 | - | - | - | IP address pool information from UDM (TEI17_IPU) | - | - | Docs:=0 | - | |
| 8.23 | - | - | - | Same PCF selection for AMF and SMF (TEI17-SPSFAS) | - | - | Docs:=0 | - | |
| 8.24 | - | - | - | Support of different slices over different Non-3GPP access (TEI17_N3SLICE) | - | - | Docs:=3 | - | |
| 8.24 | S2-2208254 | CR | Approval | 23.501 CR3704 (Rel-17, 'F'): ULI with TAI for non-3GPP access | Ericsson | Rel-17 | r03 agreed. Revised to S2-2209290. | Laurent (Nokia): provides r01 Stefan (Ericsson) replies Stefan (Ericsson) provides r02 Marco (Huawei) provide r03 ==== Revisions Deadline ==== Laurent (Nokia): objects to R00 and R02 ==== Final Deadline ==== | Revised |
| 8.24 | S2-2209290 | CR | Approval | 23.501 CR3704R1 (Rel-17, 'F'): ULI with TAI for non-3GPP access | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2208254r03. Approved | Agreed | |
| 8.24 | S2-2208255 | CR | Approval | 23.316 CR2073 (Rel-17, 'F'): ULI with TAI for wireline access | Ericsson | Rel-17 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=3 | - | |
| 8.25 | S2-2208126 | LS In | Information | LS from CT WG1: Reply LS on system information extensions for minimization of service interruption (MINT) | CT WG1 (C1-225386) | Rel-17 | Noted | Hyunsook (LGE) proposes to note the LS. | Noted |
| 8.25 | S2-2209166 | CR | Approval | 23.502 CR3600 (Rel-17, 'F'): PLMN with disaster condition | Samsung | Rel-17 | r02 agreed. Revised to S2-2209291. | Hyunsook (LGE) provides a comment and r01. Haiyang (Huawei) provides a question. Lalith(Samsung) replies Haiyang (Huawei) further provides a question. Lalith(Samsung) replies to Haiyang (Huawei) Haris(Qualcomm) provides r02 Lalith(Samsung) is OK with r02 ==== Revisions Deadline ==== Haiyang (Huawei) is OK with r02. Hyunsook (LGE) is OK with r02. Qian (Ericsson) is OK with r02. ==== Final Deadline ==== | Revised |
| 8.25 | S2-2209291 | CR | Approval | 23.502 CR3600R1 (Rel-17, 'F'): PLMN with disaster condition | Samsung | Rel-17 | Revision of S2-2209166r02. Approved | Agreed | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=1 | - | |
| 8.26 | S2-2208127 | LS In | Information | LS from CT WG1: Reply LS on the maximum PTW length of IDLE eDRX | CT WG1 (C1-225450) | Rel-17 | Noted | Steve (Huawei) proposes to note Chris (Vodafone) comments that when using eDRX, DRX should be short and hence large PTW is not needed. It might be good to inform R2 and C1 about that. | Noted |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=0 | - | |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=4 | - | |
| 8.28 | S2-2208188 | CR | Approval | 23.502 CR3552 (Rel-17, 'F'): Correction to Nnef_UEId_Get and Nbsf_Management_Discovery definition | Intel | Rel-17 | r02 agreed. Revised to S2-2209574. | Saso (Intel) provides r01 by removing the second change (which is merged in 8936). Dario (Qualcomm) provides r02 Saso(Intel) is ok with r02 ==== Revisions Deadline ==== Laurent (Nokia): objects to R00, R01; Supports R02 ==== Final Deadline ==== | Revised |
| 8.28 | S2-2209574 | CR | Approval | 23.502 CR3552R1 (Rel-17, 'F'): Correction to Nnef_UEId_Get | Intel | Rel-17 | Revision of S2-2208188r02. Approved | Agreed | |
| 8.28 | S2-2208469 | CR | Approval | 23.501 CR3668R1 (Rel-17, 'F'): NSAG for TA(s) just outside of the RA has a specific association to those TA(s) | NEC | Rel-17 | Revision of (Postponed) S2-2205672 from S2#152E. Noted | Genadi (Lenovo) asks a question for clarification. Peter Hedman (Ericsson) provides comments that current text is good enough i.e. propose to note the CR Tamura (NEC) responds to Genadi. Genadi (Lenovo) is fine with the clarification by Tamura (NEC). Jinguo(ZTE) shares the same view as Peter Hedman (Ericsson) Tamura (NEC) provides r01. Tamura (NEC) replies to Jinguo (ZTE). Peter Hedman (Ericsson) provides comments and still do not see the need for the CR Alessio(Nokia) shares the view of Ericsson. the operator can configure NSAGs for TAs outside RA already so there is no FASMO. FASMO does not apply to configuration related issues that can be set in a way that does not cause the misoperation. Jinguo(ZTE) is fine with Tamura (NEC) response Haiyang (Huawei) comments Tamura (NEC) provides r02 reflecting given comments from Jinguo (ZTE) and Sunhaiyang (Huawei) but not seeking approval any more in this meeting. As two companies don't qualify it as FASMO, no point to propose it as release 17. As Peter (Ericsson) proposed in his Email, we are happy to work on it as Release 18. ==== Revisions Deadline ==== Andy is right. r02 can be noted. I was not clear. Sorry about it. ==== Final Deadline ==== | Noted |
| 8.28 | S2-2209204 | LS In | Action | LS from SA WG3: LS reply on 5G NSWO roaming aspects | SA WG3 (S3-222397) | Rel-17 | Noted | Laurent (Nokia): Proposes to NOTE the LS Stefan (Ericsson) agrees to NOTE | Noted |
| 9 | - | - | - | Rel-18 SIDs | - | - | Docs:=0 | - | |
| 9.1.1 | - | - | - | Study on System Enabler for Service Function Chaining (FS_SFC) | - | - | Docs:=5 | - | |
| 9.1.1 | S2-2208268 | P-CR | Approval | 23.700-18: KI#1, Basic conclusions . | Ericsson | Rel-18 | Merged into S2-2209858 | Megha(Intel) comments - can this pCR be marked as merged with S2-2209113? ==== Revisions Deadline ==== Megha(Intel) comments -this pCR is to be marked as merged with S2-2209113 ==== Final Deadline ==== | Merged |
| 9.1.1 | S2-2208685 | P-CR | Approval | 23.700-18: Conclusions for FS_SFC. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2209858 | Dongjoo(Nokia) responds to Megha Megha(Intel) comments - can this pCR be marked as merged with S2-2209113? ==== Revisions Deadline ==== Dongjoo(Nokia) confirms this document can be marked as merged into S2-2209113. ==== Final Deadline ==== | Merged |
| 9.1.1 | S2-2208898 | P-CR | Approval | 23.700-18: KI#1, Conclusion for KI#1. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209858 | Megha(Intel) comments - can this pCR be marked as merged with S2-2209113? ==== Revisions Deadline ==== Megha(Intel) comments - this pCR is to be marked merged with S2-2209113. ==== Final Deadline ==== | Merged |
| 9.1.1 | S2-2209113 | P-CR | Approval | 23.700-18: KI#1: Conclusion. | Intel, AT&T, Interdigital, Microsoft, Sandvine, Deutsche Telekom, DISH network, Charter Communications | Rel-18 | CC#4: r09 agreed. Revised to S2-2209858, merging S2-2208268, S2-2208685 and S2-2208898 | Jinguo(ZTE) shares the same view as others Dongjoo(Nokia) responds to Megha Fenqin (Huawei) proposes comments. Megha(Intel) proposes to use this pCR as baseline for all discussions related to KI#1 conclusion. Stefan (Ericsson) also shares the same views Megha(Intel) provides r01 and comments Megha (Intel) provides response to Jinguo (ZTE) Jinguo(ZTE) replies to Megha (Intel) Fenqin (Huawei) provides further comments. Dongjoo(Nokia) asks questions to Jinguo(ZTE) Stefan (Ericsson) replies to Megha Jinguo(ZTE) replies to Dongjoo(Nokia) Megha (Intel) replies to Stefan and provides r02 Dongjoo(Nokia) replies and asks a further question to Jinguo(ZTE) Fenqin (Huawei) provides r03 Dongjoo(Nokia) asks a clarification question to Fenqin(Huawei) Fenqin (Huawei) provides response to Dongjoo. Dongjoo(Nokia) replies to Fenqin(Huawei) and provides r04 Stefan (Ericsson) provides r06 Jinguo(ZTE) provides r07, and points that that Stefan(Ericsson) provides r05 instead of r06, Megha(Intel) provides r08 ==== Revisions Deadline ==== Megha (Intel) provides comments Fenqin (Huawei) provides comments Dongjoo (Nokia) provides feedback to Fenqin (Huawei) Megha (Intel) provides reply to Fenqin(Huawei) Dongjoo (Nokia) supports the response from Megha (Intel) Megha (Intel) provides comment that based on the result of the SoH r05 will be used for KI#1 agreement. Megha (Intel) is ok with r05 with the added underlined text to bullet point 2 - PCF checks whether the indicated SFC policy IDs and Metadata correspond to an authorized SFC policy for the AF. ==== Final Deadline ==== Megha (Intel) proposes to check this pCR in CC#4 to update the approved r05 with the addition of text 'and Metadata' and remove text 'for the AF' in bullet point 2. | Revised |
| 9.1.1 | S2-2209858 | P-CR | Approval | 23.700-18: KI#1: Conclusion. | Intel, AT&T, Interdigital, Microsoft, Sandvine, Deutsche Telekom, DISH network, Charter Communications, KPN | Rel-18 | Revision of S2-2209113r09, merging S2-2208268, S2-2208685 and S2-2208898. Approved | Approved | |
| 9.1.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | Docs:=16 | - | |
| 9.1.2 | S2-2208269 | CR | Approval | 23.501 CR3706 (Rel-18, 'C'): Basic description of Service Function Chaining | Ericsson | Rel-18 | Postponed | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments proposes to postpone the CR. ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208455 | CR | Approval | 23.501 CR3716 (Rel-18, 'B'): Support for Service Function Chaining in 5GS | Intel | Rel-18 | Noted | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments that based on the outcome of SoH , this CR is to be NOTED. ==== Final Deadline ==== | Noted |
| 9.1.2 | S2-2208525 | CR | Approval | 23.501 CR3719 (Rel-18, 'C'): SMF/UPF functionalities for SFC support (based on option 1 for KI#1 Conclusion) | LG Electronics | Rel-18 | Postponed | Dongjoo(Nokia) ask a question Hyunsook (LGE) clarifies. Dongjoo(Nokia) replies to Hyunsook(LGE) Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments to postpone the CR to next meeting. ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208526 | CR | Approval | 23.502 CR3571 (Rel-18, 'B'): Enabling AF to request predefined SFC | ETRI | Rel-18 | Postponed | Stefan (Ericsson) provides comments Yoohwa (ETRI) responds to Stefan (Ericsson). ==== Revisions Deadline ==== ==== Final Deadline ==== Fenqin (Huawei) ask to postpone this paper Megha(Intel) comments - For CC#4 as this CR needs to be marked as postponed. | Postponed |
| 9.1.2 | S2-2208689 | CR | Approval | 23.501 CR3727 (Rel-18, 'B'): Adding a clause for the description of SFC | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments to postpone the CR to next meeting. ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208701 | CR | Approval | 23.501 CR3728 (Rel-18, 'B'): Supporting traffic influence to service functions | Lenovo, | Rel-18 | r01 agreed. Revised to S2-2209859. Postponed | Megha(Intel) provides r01 and comments ==== Revisions Deadline ==== ==== Final Deadline ==== Fenqin (Huawei) ask to postpone this paper Dimitris (Lenovo) is ok to postpone Megha(Intel) comments - For CC#4 this CR needs to be marked as postponed. | Postponed |
| 9.1.2 | S2-2209859 | CR | Approval | 23.501 CR3728R1 (Rel-18, 'B'): Supporting traffic influence to service functions | Lenovo, | Rel-18 | Revision of S2-2208701r01. WITHDRAWN | Withdrawn | |
| 9.1.2 | S2-2208712 | CR | Approval | 23.502 CR3580 (Rel-18, 'B'): Supporting traffic influence to service functions | Lenovo, | Rel-18 | Postponed | Fenqin (Huawei) provides comments Dimitris (Lenovo) responds ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208899 | CR | Approval | 23.501 CR3736 (Rel-18, 'B'): Application Function influence SFC support | Huawei, HiSilicon | Rel-18 | Postponed | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments to postpone the CR to next meeting. ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208456 | CR | Approval | 23.502 CR3567 (Rel-18, 'B'): Procedure update to support Service Function Chaining in 5GS | Intel | Rel-18 | Noted | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments that based on the outcome of SoH , this CR is to be NOTED. ==== Final Deadline ==== | Noted |
| 9.1.2 | S2-2208691 | CR | Approval | 23.502 CR3579 (Rel-18, 'B'): Procedure update for SFC support | Nokia, Nokia Shanghai Bell | Rel-18 | CR Number missing! Postponed | Dongjoo(Nokia) provides r02 Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. Stefan (Ericsson) provides comments Dongjoo (Nokia) provides r03 accepting the comments from Stefan (Ericsson) ==== Revisions Deadline ==== Megha(Intel) comments to postpone this CR for next meeting ==== Final Deadline ==== | Postponed |
| 9.1.2 | S2-2208900 | CR | Approval | 23.502 CR3588 (Rel-18, 'B'): Application Function influence SFC support | Huawei, HiSilicon | Rel-18 | Postponed | Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1. ==== Revisions Deadline ==== Megha(Intel) comments to postpone this CR for next meeting ==== Final Deadline ==== | Postponed |
| 9.1.2 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=4 | - | |
| 9.1.2 | S2-2208270 | CR | Approval | 23.503 CR0740 (Rel-18, 'C'): Basic description of Service Function Chaining | Ericsson | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.1.2 | S2-2208457 | CR | Approval | 23.503 CR0746 (Rel-18, 'B'): Policy update to support Service Function Chaining in 5GS | Intel | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.1.2 | S2-2208702 | CR | Approval | 23.503 CR0752 (Rel-18, 'B'): SFC Support | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.1.2 | S2-2208901 | CR | Approval | 23.503 CR0756 (Rel-18, 'B'): Application Function influence SFC support | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | - | - | - | Study on Generic group management, exposure and communication enhancements (FS_GMEC) | - | - | Docs:=28 | - | |
| 9.2.1 | - | - | - | KI#1 - group service area, group MBR, group QoS | - | - | Docs:=7 | - | |
| 9.2.1 | S2-2208524 | P-CR | Approval | 23.700-74: KI#1: Conclusion update on service area enforcement. | LG Electronics | Rel-18 | r01 agreed. Revised to S2-2209575. | Qianghua (Huawei) provides r01 to capture the assumption to use LADN-based approach Sang-Jun (Samsung) comments. ==== Revisions Deadline ==== Hyunsook (LGE) is OK with r01. ==== Final Deadline ==== | Revised |
| 9.2.1 | S2-2209575 | P-CR | Approval | 23.700-74: KI#1: Conclusion update on service area enforcement. | LG Electronics | Rel-18 | Revision of S2-2208524r01. Approved | Approved | |
| 9.2.1 | S2-2208607 | P-CR | Approval | 23.700-74: Conclusion update for KI#1 for SMF service area control. | China Mobile | Rel-18 | Noted | Sebastian (Qualcomm) objects to the pCR Dan (China Mobile) reply Shubhranshu (Nokia) comments Qianghua (Huawei) provides comments and suggests a way forward Qianghua (Huawei) provides r01, this is an attempt to make a way forward as proposed below ==== Revisions Deadline ==== Shubhranshu (Nokia) concerns to r01 Stefan (Ericsson) shares same concern as Shubhranshu Sebastian (Qualcomm) objects also to r01 for the reasons given by Shubhranshu and Stefan ==== Final Deadline ==== | Noted |
| 9.2.1 | S2-2208594 | P-CR | Approval | 23.700-74: KI#1: Update for Group-MBR conclusion. | CATT | Rel-18 | r01 agreed. Revised to S2-2209576. | Shubhranshu (Nokia) provides r01 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.2.1 | S2-2209576 | P-CR | Approval | 23.700-74: KI#1: Update for Group-MBR conclusion. | CATT | Rel-18 | Revision of S2-2208594r01. Approved | Approved | |
| 9.2.1 | S2-2208714 | P-CR | Approval | 23.700-74: KI#1_Conclusion update for QoS provision for KI#5 muticast group. | China Telecom | Rel-18 | CC#3: r03 agreed. Revised to S2-2209948. | Stefan (Ericsson) provides comments Qianghua (Huawei) also suggests to consider this as part of KI#3, but with different views on how to use such QoS Heng (China Telecom) reply Sebastian (Qualcomm) comments Stefan (Ericsson) comments Sang-Jun (Samsung) comments. Heng (China Telecom) provide r01. Heng (China Telecm) provides r02 Shubhranshu (Nokia) asks for clarification Heng (China Telecom) reply to Shubhranshu and provide r03 to correct the mistake. ==== Revisions Deadline ==== Heng (China Telecom) reply to Shubhranshu (Nokia) Sebastian (Qualcomm) objects to the PCR (all versions) Heng (China Telecom) reply to Sebastian (Qualcomm) Sang-Jun (Samsung) proposes to go with r03. Qianghua (Huawei) proposes to go with r03. ==== Final Deadline ==== | Revised |
| 9.2.1 | S2-2209948 | P-CR | Approval | 23.700-74: KI#3_Conclusion update for QoS provision for KI#5 muticast group. | China Telecom | Rel-18 | Revision of S2-2208714r03. Approved | Approved | |
| 9.2.1 | - | - | - | KI#3 - conclusion updates | - | - | Docs:=3 | - | |
| 9.2.1 | S2-2208280 | P-CR | Approval | 23.700-74: KI#3: Conclusion updates . | Ericsson | Rel-18 | r05 agreed. Revised to S2-2209674. | Qianghua (Huawei) provides comments Sebastian (Qualcomm) comments Stefan (Ericsson) provides comments Sebastian (Qualcomm) provides r01 Qianghua (Huawei) provides r02 Stefan (Ericsson) provides r03 Qianghua (Huawei) provides r04 Stefan (Ericsson) provides r05 Shubhranshu (Nokia) objects r04 Qianghua (Huawei) replies and also asks Sebastian to reconsider again ==== Revisions Deadline ==== Sebastian (Qualcomm) is ok with r01; objects to other versions; can be ok with r05 if this text ('The following example or NOTE may however be added to e.g. TS 23.501 or 23.502) to clarify how the AF does this.') and the two sub-bullets are removed and replaced by 'How the AF does this is not to be standardized (An example or NOTE may however be added to e.g. TS 23.501 or 23.502).' Stefan (Ericsson) OK with r00, r01, r03, r05. Objects to r02, r04 Sebastian (Qualcomm) replies to Stefan Qianghua (Huawei) OK to go with r05+ removal of ('The following example or NOTE may however be added to e.g. TS 23.501 or 23.502) to clarify how the AF does this.') and the two sub-bullets, + addition of 'How the AF does this is not to be standardized in SA2 specifications (A NOTE may however be added to e.g. TS 23.501 or 23.502' + removal of the EN about CSR/CSA Qianghua (Huawei) cannot accept R0, R01, r03, for records ==== Final Deadline ==== Shubhranshu (Nokia) agrees and proposes to capture this in Chair's Note: 'Revision of S2-2208280r05 + changes proposed by Huawei', instead of current Chair's Note which says: 'Revision of S2-2208280r05 + changes proposed by Qualcomm' Antoine (Orange): I don't understand 'removal of the EN about CSR/CSA' because there's no EN and nothing about CSR/CSA in r05. Sebastian (Qualcomm) is ok with the proposal by Shubhranshu (Nokia) | Revised |
| 9.2.1 | S2-2209674 | P-CR | Approval | 23.700-74: KI#3: Conclusion updates . | Ericsson | Rel-18 | Revision of S2-2208280r05. Approved | Approved | |
| 9.2.1 | S2-2208503 | P-CR | Approval | 23.700-74: Update to conclusion of KI#3. | Siemens | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.2.1 | - | - | - | KI#4- Rapp Blank Conclusion | - | - | Docs:=1 | - | |
| 9.2.1 | S2-2208646 | P-CR | Approval | 23.700-74: Merged Conclusion for FS_GMEC KI#4. | Samsung (Rapp), Huawei (Rapp) | Rel-18 | CC#3: Postponed to CC#4. CC#4: Noted | Qianghua (Huawei) provides r01 Laurent (Nokia): provides r02 Qianghua (Huawei) provides r03 ==== Revisions Deadline ==== Stefan (Ericsson) objects to r01-r03 (r00 is empty) Qianghua (Huawei), based on offline discussion, proposes to go with r03 + the following changes: Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism' Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose' Laurent (Nokia): objects to R00-R03 Sang-Jun (Samsung) also supports going with r03 + the following changes: Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism' Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose' Zhendong (ZTE) is fine with qianghua proposal Stefan (Ericsson) cannot accept Qianghua proposal Qianghua (Huawei), based on offline discussion, proposes to go with r03 + the following changes: Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism' Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose' + confirm whether to keep the Ens at CC#3 ==== Final Deadline ==== Laurent (Nokia): my request is to have a written text in front of me at the CC3. Especially I require to SEE where such NOTE would be 'No standard impacts are expected for this purpose' Qianghua (Huawei) provides r04 at CC#3, need to check whether to keep the ENs or not at CC#3, besides the following changes over r03 seem agreeable: - Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism' - Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose' | Noted |
| 9.2.1 | - | - | - | KI#4-contributions from company | - | - | Docs:=3 | - | |
| 9.2.1 | S2-2208283 | P-CR | Approval | 23.700-74: KI#4: Conclusion proposal. | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Qianghua (Huawei) disagrees some observations and thus cannot agree the conclusions pointing to specific solutions. Sang-Jun (Samsung) shares the same veiws as Qianghua. Stefan (Ericsson) provides replies Laurent (Nokia): answers Qianghua (Huawei) provides responses to the comments ==== Revisions Deadline ==== Qianghua (Huawei) agrees to note or merge, discussion already under 08646. Otherwise object for record. ==== Final Deadline ==== | Noted |
| 9.2.1 | S2-2208939 | P-CR | Approval | 23.700-74: KI#4, evaluations and conclusions. | Huawei, HiSilicon | Rel-18 | Noted | Stefan (Ericsson) cannotagree to the conclusions Laurent (Nokia): We cannot also agree to the conclusions, support Stefan's view as we expressed also in 8283 thread Qianghua (Huawei) provides responses to the comments ==== Revisions Deadline ==== Laurent (Nokia): objects to any version (anyhow we are discussing 8646 now) Qianghua (Huawei) OK to note ==== Final Deadline ==== | Noted |
| 9.2.1 | S2-2208954 | P-CR | Approval | 23.700-74: KI#4, adding the evaluation and conclusion for KI#4. | ZTE | Rel-18 | Noted | Stefan (Ericsson) has similar concerns ==== Revisions Deadline ==== Laurent (Nokia): objects to any version (anyhow we are discussing 8646 now) ==== Final Deadline ==== | Noted |
| 9.2.1 | - | - | - | KI#5-conclusion updates | - | - | Docs:=1 | - | |
| 9.2.1 | S2-2208615 | P-CR | Approval | 23.700-74: Conclusion for FS_GMEC KI#5. | Samsung | Rel-18 | Approved | Sebastian (Qualcomm) suggests to note the paper Sang-Jun (Samsung) repiles to Sebastian (Qualcomm). ==== Revisions Deadline ==== Sang-Jun (Samsung) proposes to go with r00 as the NOTEs should be added even before the conclusion for KI1/2/3 are being undated. ==== Final Deadline ==== | Approved |
| 9.2.1 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=13 | - | |
| 9.2.1 | S2-2208279 | P-CR | Approval | 23.700-74: KI#1: Update to conclusions . | Ericsson | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208592 | P-CR | Approval | 23.700-74: Update of Solution #12: Support 5G VN service area restriction with SMF service area. | China Mobile | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208953 | P-CR | Approval | 23.700-74: KI#1, update the solution 18. | ZTE | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208952 | P-CR | Approval | 23.700-74: KI#1, conclusion update. | ZTE | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208937 | P-CR | Approval | 23.700-74: KI#1: Update conclusions to address Editor's notes. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208394 | P-CR | Approval | 23.700-74: Update of Solution #21 for FS_GMEC KI#1. | China Telecom | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208281 | P-CR | Approval | 23.700-74: KI#3, Sol#22: Solution updates to address ENs and clarify solution. | Ericsson | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208938 | P-CR | Approval | 23.700-74: KI#3: Update conclusions to address the ENs. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2209162 | P-CR | Approval | 23.700-74: KI# 3 Conclusion updates. | Nokia, Nokia Shanghai bell | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208223 | P-CR | Approval | 23.700-74: Update to solution 16 ( 6.16.2.5). | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208282 | P-CR | Approval | 23.700-74: KI#4, Sol#16: Updates to resolve editor s notes . | Ericsson | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208613 | P-CR | Approval | 23.700-74: Conclusion for FS_GMEC KI#4. | Samsung | Rel-18 | Not Handled | ==== Revisions Deadline ==== Laurent (Nokia): Objects to any version (rapporteur said not handled anyhow) ==== Final Deadline ==== | Not Handled |
| 9.2.1 | S2-2208618 | P-CR | Approval | 23.700-74: Evaluation for FS_GMEC KI#4. | Samsung | Rel-18 | Not Handled | ==== Revisions Deadline ==== Laurent (Nokia): Objects to any version (rapporteur said not handled anyhow) ==== Final Deadline ==== | Not Handled |
| 9.2.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | Docs:=11 | - | |
| 9.2.2 | - | - | - | KI#2- CRs | - | - | Docs:=6 | - | |
| 9.2.2 | S2-2208428 | CR | Approval | 23.501 CR3715 (Rel-18, 'B'): TS 23.501 Enhancing External Exposure of Network Capability | NTT DOCOMO, Huawei | Rel-18 | CR Number missing! r03 agreed. Revised to S2-2209577, merging S2-2208941 | Tugce (NTT DOCOMO) provides r01. Stefan (Ericsson) provides comments Tugce (NTT DOCOMO) responds. Shubhranshu (Nokia) comments Qianghua (Huawei) comments Stefan (Ericsson) comments Stefan (Ericsson) replies to Tugce Qianghua (Huawei) provides r02, merging 2208941 Stefan (Ericsson) provides r03 ==== Revisions Deadline ==== Qianghua (Huawei) OK with r03, prefer r02 Stefan (Ericsson) proposes to go with r03 ==== Final Deadline ==== | Revised |
| 9.2.2 | S2-2209577 | CR | Approval | 23.501 CR3715R1 (Rel-18, 'B'): TS 23.501 Enhancing External Exposure of Network Capability | NTT DOCOMO, Huawei | Rel-18 | Revision of S2-2208428r03, merging S2-2208941. Approved | Agreed | |
| 9.2.2 | S2-2208432 | CR | Approval | 23.502 CR3566 (Rel-18, 'B'): TS 23.502 Enhancing parameter provisioning services | NTT DOCOMO, Huawei | Rel-18 | CR Number missing! Merged into S2-2209578 | Tugce (NTT DOCOMO) provides r01. Qianghua (Huawei) proposes to mark this CR postponed or merged into 08595 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.2.2 | S2-2208595 | CR | Approval | 23.502 CR3575 (Rel-18, 'B'): Enhance group status event reporting | CATT | Rel-18 | r02 agreed. Revised to S2-2209578, merging S2-2208432 | Stefan (Ericsson) comments and provides r01 and r02 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.2.2 | S2-2209578 | CR | Approval | 23.502 CR3575R1 (Rel-18, 'B'): Enhance group status event reporting | CATT | Rel-18 | Revision of S2-2208595r02, merging S2-2208432. Approved | Agreed | |
| 9.2.2 | S2-2208941 | CR | Approval | 23.501 CR3739 (Rel-18, 'B'): Support the enhance group status event reporting | Huawei, HiSilicon | Rel-18 | Merged into S2-2209577 | Qianghua (Huawei) agrees to merge this in S2-2208428 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.2.2 | - | - | - | KI#5- CRs | - | - | Docs:=1 | - | |
| 9.2.2 | S2-2208643 | CR | Approval | 23.501 CR3725 (Rel-18, 'C'): Allowing UE to simultaneously send data to different groups with different QoS policy | Samsung, Huawei, Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Sebastian (Qualcomm) objects to r00 and in general suggests to postpone the CR Sang-Jun (Samsung) replies to Sebastian (Qualcomm). This is regarding the principle agreed for KI#5 and need to be captured even before the conclusion for KI1/2/3 are being undated. Qianghua (Huawei) provides r01 and asks for clarification from Sebastian Sebastian (Qualcomm) replies and proposes to postpone ==== Revisions Deadline ==== Sang-Jun (Samsung) replies to Sebastian (Qualcomm) and propses to go with r01. Sebastian (Qualcomm) prefers to postpone; (objects to r00 and r01) ==== Final Deadline ==== | Postponed |
| 9.2.2 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=4 | - | |
| 9.2.2 | S2-2208596 | DRAFTCR | Information | Update for 5G VN group data | CATT | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.2 | S2-2208597 | DRAFTCR | Information | Update paramaters for 5G VN group data | CATT | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.2 | S2-2208940 | DRAFTCR | Information | KI#1: Support the enhancement of group attribute management | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.2.2 | S2-2208942 | DRAFTCR | Information | KI#3: provisioning of traffic characteristics and monitoring of performance characteristics | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.3 | - | - | - | Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) | - | - | Docs:=32 | - | |
| 9.3 | - | - | - | Liaisons | - | - | Docs:=1 | - | |
| 9.3 | S2-2208111 | LS In | Action | LS from BBF: BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) | BBF (LIAISE-542-5G-RG-Hybrid-Access-Requirements-00) | Revision of Postponed S2-2205467 from S2#152-e. This LS was postponed | Postponed | ||
| 9.3 | - | - | - | KI#2 - Solution updates | - | - | Docs:=5 | - | |
| 9.3 | S2-2209195 | P-CR | Approval | 23.700-53: KI#2: Sol.2.1 Update. | Deutsche Telekom | Rel-18 | r01 agreed. Revised to S2-2209278. | Apostolis (Lenovo) provides comments and questions. ==== Revisions Deadline ==== Dieter (Deutsche Telekom) provides r01. Tao(VC) still check r00 since r01 is provided after revision deadline and no explict objection to r00 for see. ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209278 | P-CR | Approval | 23.700-53: KI#2: Sol.2.1 Update. | Deutsche Telekom | Rel-18 | Revision of S2-2209195r01. Approved | Approved | |
| 9.3 | S2-2209087 | P-CR | Approval | 23.700-53: Updates to solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, Charter Communications | Rel-18 | r03 agreed. Revised to S2-2209292. | Dieter (Deutsche Telekom) provides comments, questions and suggestions to the solution update. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209292 | P-CR | Approval | 23.700-53: Updates to solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, Charter Communications | Rel-18 | Revision of S2-2209087r03. Approved | Approved | |
| 9.3 | S2-2209090 | P-CR | Approval | 23.700-53: Updates to solution #2.3: MPQUIC steering functionality using IP proxying over HTTP. | Lenovo, Broadcom | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.3 | - | - | - | KI#3 - Solution updates | - | - | Docs:=5 | - | |
| 9.3 | S2-2208801 | DISCUSSION | Discussion | DP on the effectiveness of asynchronous redundant steering mode | Alibaba Group | Rel-18 | Noted | ==== Revisions Deadline ==== Rainer (Nokia) proposes to note the DP in 8801. ==== Final Deadline ==== | Noted |
| 9.3 | S2-2208796 | P-CR | Approval | 23.700-53: New solution on asynchronous redundant traffic steering mode. | Alibaba Group | Rel-18 | Revision of (Noted) S2-2205560 from S2#152E. Noted | Dario (Qualcomm) comments Rainer (Nokia) comments. ==== Revisions Deadline ==== Guanzhou (InterDigital) assumes that no new solution is allowed at this meeting and this should be Noted. Rainer (Nokia) agrees to note the paper. ==== Final Deadline ==== | Noted |
| 9.3 | S2-2209032 | P-CR | Approval | 23.700-53: Updates to solution #3.7: Suspending the Redundancy Steering Mode. | China Telecom | Rel-18 | r01 agreed. Revised to S2-2209293. | Rainer (Nokia) provides r01. Yubing (China Telecom) is ok with r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209293 | P-CR | Approval | 23.700-53: Updates to solution #3.7: Suspending the Redundancy Steering Mode. | China Telecom | Rel-18 | Revision of S2-2209032r01. Approved | Approved | |
| 9.3 | S2-2209034 | P-CR | Approval | 23.700-53: Updates to solution #3.1: Deactivate the RSM during the redundant transmission. | China Telecom | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.3 | - | - | - | KI#5 - Solution updates | - | - | Docs:=1 | - | |
| 9.3 | S2-2208326 | P-CR | Approval | 23.700-53: KI#5, update Sol#5.6. | Huawei, HiSilicon | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.3 | - | - | - | KI#2 - Evaluation and Conclusions | - | - | Docs:=5 | - | |
| 9.3 | S2-2209092 | P-CR | Approval | 23.700-53: Evaluation for KI#2. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent | Rel-18 | r04 agreed. Revised to S2-2209294. | Dieter (Deutsche Telekom) comments and provides r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209294 | P-CR | Approval | 23.700-53: Evaluation for KI#2. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent | Rel-18 | Revision of S2-2209092r04. Approved | Approved | |
| 9.3 | S2-2209094 | P-CR | Approval | 23.700-53: Conclusions for KI#2. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, US Cellular, China Mobile, Qualcomm Incorporated, Charter Communications, AT&T, Samsung, Cisco, HP | Rel-18 | CC#3: Postponed to CC#4. CC#4: r06 + changes agreed. Revised to S2-2209955. | Apostolis (Lenovo) provides r01. Dieter (Deutsche Telekom) provides r02. ==== Revisions Deadline ==== ==== Final Deadline ==== Apostolis (Lenovo) responds to Susan (Huawei) and requests this document to be discussed in CC#3. | Revised |
| 9.3 | S2-2209955 | P-CR | Approval | 23.700-53: Conclusions for KI#2. | Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, US Cellular, China Mobile, Qualcomm Incorporated, Charter Communications, AT&T, Samsung, Cisco, HPE, NICT, KPN, F5, DISH Network, Intel, Tessares, Microsoft, CATT, ETRI | Rel-18 | Revision of S2-2209094r06 + changes. Approved | Approved | |
| 9.3 | S2-2209196 | P-CR | Approval | 23.700-53: Evaluation and Conclusions for KI#2. | Deutsche Telekom | Rel-18 | Noted | Dieter (Deutsche Telekom) provides r01. Dieter (Deutsche Telekom) comments that we could try to merge the evaluation part with 9092 and the conclusion part with 9094. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.3 | - | - | - | KI#3 - Evaluation and Conclusions | - | - | Docs:=10 | - | |
| 9.3 | S2-2208278 | P-CR | Approval | 23.700-53: KI#3: Updates to conclusion . | Ericsson | Rel-18 | CC#3: Postponed to CC#4. CC#4: r10 agreed. Revised to S2-2209956. | Dario (Qualcomm) comments. ==== Revisions Deadline ==== Stefan (Ericsson) comments on slides ==== Final Deadline ==== Apostolis (Lenovo) provides r02 as a possible compromise to be discussed in CC#3. | Revised |
| 9.3 | S2-2209956 | P-CR | Approval | 23.700-53: KI#3: Updates to conclusion . | Ericsson | Rel-18 | Revision of S2-2208278r10. Approved | Approved | |
| 9.3 | S2-2208439 | P-CR | Approval | 23.700-53: KI#3: Evaluation/conclusions update on suspending the redundant steering mode. | Nokia, Nokia Shanghai Bell | Rel-18 | r02 agreed. Revised to S2-2209295. | Stefan (Ericsson) provides comments Rainer (Nokia) replies. Myungjune (LGE) comments Myungjune (LGE) replies to Rainer (Nokia) Myungjune (LGE) replies to Rainer (Nokia). Rainer (Nokia) provides r01. Stefan (Ericsson) provides r02 Rainer (Nokia) is ok with r02. ==== Revisions Deadline ==== Myungjune (LGE) is ok with r02. ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209295 | P-CR | Approval | 23.700-53: KI#3: Evaluation/conclusions update on suspending the redundant steering mode. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2208439r02. Approved | Approved | |
| 9.3 | S2-2208987 | P-CR | Approval | 23.700-53: KI#3: Conclusion update for KI#3 . | InterDigital Inc. | Rel-18 | Merged into S2-2209296 | Dario (Qualcomm) asks questions for clarifications. Rainer (Nokia) proposes to merge 8987 into 9096. Guanzhou (InterDigital) agrees to merge this with S2-2209096 and responds to Dario (Qualcomm)'s questions. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.3 | S2-2209035 | P-CR | Approval | 23.700-53: Updates to the Conclusion for KI #3. | China Telecom | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.3 | S2-2209096 | P-CR | Approval | 23.700-53: Conclusions for KI#3: RTT Thresholds. | Lenovo | Rel-18 | r06 agreed. Revised to S2-2209296, merging S2-2208987 | Dario (Qualcomm) asks questions for clarification. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209296 | P-CR | Approval | 23.700-53: Conclusions for KI#3: RTT Thresholds. | Lenovo, Nokia, Nokia Shanghai Bell, InterDigital | Rel-18 | Revision of S2-2209096r06, merging S2-2208987. Approved | Approved | |
| 9.3 | S2-2209098 | P-CR | Approval | 23.700-53: Conclusions for KI#3: RSM with ATSSS-LL. | Lenovo | Rel-18 | WITHDRAWN | Jinguo(ZTE) asks questions for clarification. ==== Revisions Deadline ==== ==== Final Deadline ==== | Withdrawn |
| 9.3 | S2-2209152 | P-CR | Approval | 23.700-53: KI#3: Removal of EN on duplication factor in evaluation and conclusions. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Charter Communications, Broadcom | Rel-18 | Noted | Myungjune (LGE) provides comments. Stefan (Ericsson) have similar comments as LGE Rainer (Nokia) replies. Jinguo(ZTE) shares same concerns as Ericsson and LGE Susan (Huawei) shares the similar view as Ericsson, LGE, ZTE. Dario (Qualcomm) replies and provides r01 ==== Revisions Deadline ==== Myungjune (LGE) comments. Susan (Huawei) objects to all versions of the paper, i.e. r00 and r01. Susan (Huawei) replies to Rainer (Nokia). Stefan (Ericsson) also objects to all versions of the paper, i.e. r00 and r01. ==== Final Deadline ==== | Noted |
| 9.3 | - | - | - | KI#5 - Evaluation and Conclusions | - | - | Docs:=5 | - | |
| 9.3 | S2-2208276 | P-CR | Approval | 23.700-53: KI#5: Updates to conclusions to resolve Editor s note 1. | Ericsson | Rel-18 | Merged into S2-2209297 | Myungjune (LGE) proposes to merge this pCR into S2-2208460 / S2-2208500. Rainer (Nokia) agrees to merge and asks for clarification. Stefan (Ericsson) replies to Rainer Stefan (Ericsson) OK to consider it merged into S2-2208500 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.3 | S2-2208277 | P-CR | Approval | 23.700-53: KI#5: Updates to conclusions to resolve Editor s note 2. | Ericsson | Rel-18 | Merged into S2-2209297 | Myungjune (LGE) proposes to merge this pCR into S2-2208460 / S2-2208500. ==== Revisions Deadline ==== Stefan (Ericsson) OK to consider it merged into S2-2208500 Marco (Huawei) as per Stefan's comment. Yes consider merged into 8500. ==== Final Deadline ==== | Merged |
| 9.3 | S2-2208460 | P-CR | Approval | 23.700-53: KI#5 Conclusion (clause 8.3), addressing the 1st EN in clause 8.3. | Charter Communications, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Broadcom, Apple, CableLabs | Rel-18 | Merged into S2-2209297 | Myungjune (LGE) provides r01. Marco (Huawei) comments Paul R (Charter) comments Marco (Huawei) consider merged into 8500 as per 8500r06 Paul R (Charter) confirms that S2-2208460r01 has been merged into S2-2208500 during the meeting ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.3 | S2-2208500 | P-CR | Approval | 23.700-53: Conclusion for KI#5. | LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell | Rel-18 | r11 agreed. Revised to S2-2209297, merging S2-2208276, S2-2208277 and S2-2208460 | Myungjune (LGE) replies to Jinguo (ZTE) Jinguo(ZTE) asks questions for clarification. Myungjune (LGE) provides r01. Jinguo(ZTE) asks one question Myungjune (LGE) replies Jinguo (ZTE). Marco (Huawei) ask clarification and comments Stefan (Ericsson) comments and provides r02 Paul R. (Charter) comments and provides r03 Myungjune (LGE) provides r04. Myungjune (LGE) replies to Marco (Huawei) Marco (Huawei) agrees with Paul (charter) to remove of Wireline support . Support R02 NOT r03 & r04 Myungjune (LGE) clarifies that r04 is aligned with r02. Stefan (Ericsson) replies to Paul and Myungjune Myungjune (LGE) replies to Stefan (Ericsson). Paul R. (Charter) provides r06 which merges S2-2208460r01 pCR, because S2-2208500r05 addresses the 1st EN in step 6. Myungjune (LGE) replies to Paul R. (Charter) Stefan (Ericsson) replies and provides r08 DongYeon (Samsung) provides r09. Marco (Huawei) provide r10 without option 'without interruption' Paul R (Charter) agrees to r09 but not r10 Myungjune (LGE) replies to Marco (Huawei) . Stefan (Ericsson) comments to Myungjune and provides r11 ==== Revisions Deadline ==== Paul R (Charter) supports r11 as it improves r09 Rainer (Nokia) is ok with r11. Stefan (Ericsson) responds to Myungjune Marco (Huawei) can live with r11 and object any version from 00 to 09 ==== Final Deadline ==== | Revised |
| 9.3 | S2-2209297 | P-CR | Approval | 23.700-53: Conclusion for KI#5. | LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell, Charter Communications | Rel-18 | Revision of S2-2208500r11, merging S2-2208276, S2-2208277 and S2-2208460. Approved | Approved | |
| 9.4.1 | - | - | - | Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) | - | - | Docs:=56 | - | |
| 9.4.1 | - | - | - | General | - | - | Docs:=3 | - | |
| 9.4.1 | S2-2208776 | LS OUT | Approval | [DRAFT] LS on Progress and open issues for NPN enhancements in Rel-18 | Ericsson | Rel-18 | r01 agreed. Revised to S2-2209860. | Peter Hedman (Ericsson) provides r01 Guanzhou (InterDigital) has some suggestion on Q1 Rainer (Nokia) comments. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r01 but also ok to add the proposals suggested and that is done in r02, i.e. r01+ Add 'and whether it is necessary that the UE needs to use any of these modes to select an SNPN over non-3GPP access' to question 4. Add ', and does it depend on whose credentials the UE uses to access the hosting network' to question 1 Remove ' Rainer (Nokia) is ok with r01 or r02. Saso (Intel) prefers r01 wording for Q4. Peter Hedman (Ericsson) asks if we then can agree r01 or r01+ Add ', and does it depend on whose credentials the UE uses to access the hosting network' to question 1 Remove ' Rainer (Nokia) is ok to remove yellow text. Guanzhou (InterDigital) is OK with r02 and is also OK with r01+changes Peter(Ericsson) mentioned below ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209860 | LS OUT | Approval | Progress and open issues for NPN enhancements in Rel-18 | SA WG2 | Rel-18 | Revision of S2-2208776r01. Approved | Approved | |
| 9.4.1 | S2-2208770 | P-CR | Approval | 23.700-08: Correction of Mapping Solutions to Key Issues. | Ericsson | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.4.1 | - | - | - | KI#2 | - | - | Docs:=3 | - | |
| 9.4.1 | S2-2208438 | P-CR | Approval | 23.700-08: KI#2 on Support of Non-3GPP access for SNPN: Conclusion update. | Nokia, Nokia Shanghai Bell, Intel, Qualcomm Incorporated, Ericsson | Rel-18 | Approved | Huan (vivo) asks questions for clarifications Rainer (Nokia) replies. Huan (vivo) comments Saso (Intel) replies to Huan. Marco (Huawei) comments Rainer (Nokia) comments. Huan(vivo) comments. Saso (Intel) replies to Huan(vivo). Yishan (Huawei) provides comments Saso (Intel) replies to Yishan (Huawei) ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.4.1 | S2-2208945 | P-CR | Approval | 23.700-08: KI#2 Conclusions update to resolve the EN on NSWO enhancements. | Lenovo | Rel-18 | r02 agreed. Revised to S2-2209861. | Peter Hedman (Ericsson) provides comments Saso (Intel) provides comments Rainer (Nokia) comments. Marco (Huawei) shares previous emails' views and concerns Genadi (Lenovo) provides r01 and replies to Peter (Ericsson), Saso (Intel), Rainer (Nokia) and Marco (Huawei). Genadi (Lenovo) replies to Saso (Intel). Marco (Huawei) further comments Genadi (Lenovo) replies to Marco (Huawei). Saso (Intel) comments. Marco (Huawei) can accept Saso's (Intel) proposal to consider for a note in future normative work. Saso (Intel) provides r02 to keep the discussion ongoing. Rainer (Nokia) is ok with r02. ==== Revisions Deadline ==== Peter Hedman (Ericsson) ok with r02 Marco (Huawei) ok with r02 ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209861 | P-CR | Approval | 23.700-08: KI#2 Conclusions update to resolve the EN on NSWO enhancements. | Lenovo | Rel-18 | Revision of S2-2208945r02. Approved | Approved | |
| 9.4.1 | - | - | - | KI#3 | - | - | Docs:=8 | - | |
| 9.4.1 | S2-2208313 | P-CR | Approval | 23.700-08: KI#3, Update evaluation on KI#3. | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2209862, merging S2-2208734 | Marco (Huawei) provide r01 as merging of S2-228734/8775 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209862 | P-CR | Approval | 23.700-08: KI#3, Update evaluation on KI#3. | Huawei, HiSilicon | Rel-18 | Revision of S2-2208313r01, merging S2-2208734. Approved | Approved | |
| 9.4.1 | S2-2208316 | P-CR | Approval | 23.700-08: KI#3, Update conclusion on KI#3. | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2209863. | Peter Hedman (Ericsson) provides comments and questions Yishan (Huawei) answers to Peter Hedman (Ericsson) and provides r01 accordingly Peter Hedman (Ericsson) provides r02, and ok to keep the content of agreement in this paper ==== Revisions Deadline ==== Yishan (Huawei) is ok with r02 ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209863 | P-CR | Approval | 23.700-08: KI#3, Update conclusion on KI#3. | Huawei, HiSilicon | Rel-18 | Revision of S2-2208316r02. Approved | Approved | |
| 9.4.1 | S2-2208734 | P-CR | Approval | 23.700-08: KI#3: Update evaluation of solutions for KI#3. | CATT | Rel-18 | Merged into S2-2209862 | Peter Hedman (Ericsson) provides comments, and suggests to mark the paper as merged into 08313. Liping Wu (CATT) agrees to mark the paper as merged into 08313. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208775 | P-CR | Approval | 23.700-08: KI#3: Evaluation and conclusion for Key Issue #3. | Ericsson, Qualcomm | Rel-18 | r02 agreed. Revised to S2-2209864. | Peter Hedman (Ericsson) provides r01 and suggests to merge in evaluation into 08313, tbd what tdoc to use for conclusions Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209864 | P-CR | Approval | 23.700-08: KI#3: Evaluation and conclusion for Key Issue #3. | Ericsson, Qualcomm | Rel-18 | Revision of S2-2208775r02. Approved | Approved | |
| 9.4.1 | S2-2209173 | P-CR | Approval | 23.700-08: Update evaluation and solution#22 for key issue#3/4. | Xiaomi | Rel-18 | Noted | Peter Hedman (Ericsson) provides comments Jianning (Xiaomi) replies to Peter (Ericsson) Marco (Huawei) provide r01 and comment Josep (DT) agrees with Peter (Ericsson) does not find unsecured connection to the hosting network acceptable. Ashok (Samsung) comments Huan (vivo) comments Jianning (Xiaomi) replies to Josep (DT) Jianning (Xiaomi) replies to Huan(vivo) Josep (DT) replies to Jianning (Xiaomi) and expresses big security concerns with this pCR. ==== Revisions Deadline ==== Josep (DT) objects to this pCR. ==== Final Deadline ==== | Noted |
| 9.4.1 | - | - | - | KI#4 | - | - | Docs:=17 | - | |
| 9.4.1 | S2-2208291 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4 PNI-NPN. | Vivo, China Telecom | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) assumes this will be considered merged into S2-2208774. ==== Revisions Deadline ==== Huan (vivo) confirms this contribution is considered merged into S2-2208774. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208293 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4 SNPN - content of the hosting network selection information. | Vivo, China Telecom | Rel-18 | Merged into S2-2209865 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged into other tdocs? Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774 Huan (vivo) confirms this contribution can be considered the evaluation part is merged into 2208444 and conclusion part into S2-2208774. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208294 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4 SNPN - where and how a UE obtains hosting network selection information. | Vivo, China Telecom | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) assumes this will be considered merged into S2-2208774. ==== Revisions Deadline ==== Huan (vivo) confirms this contribution can be considered as merged into S2-2208774. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208297 | P-CR | Approval | 23.700-08: 23.700-08: Conclusions for KI#4. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) provides an initial bunch of comments and questions. Josep (DT) additionally comments. Finds the conclusion too inconclusive Pallab (Nokia) responds to Josep (DT) Pallab (Nokia) responds to Antoine (Orange) ==== Revisions Deadline ==== Myungjune (LGE) proposes to merge this to S2-2208774. Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774 Peter Hedman (Ericsson) provides comments and suggests to mark 'Merged into S2-2208774' Pallab (Nokia) confirms Merging into S2-2208774 ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208317 | P-CR | Approval | 23.700-08: KI#4, Update conclusion on KI#4. | Huawei, HiSilicon | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) raises an ambiguous sentence. Yishan (Huawei) answers to Antoine (Orange) and provides r01. Guanzhou (InterDigital) points out revisions of S2-2208774 try to merge 8317 and other KI#4 conclusion proposals. ==== Revisions Deadline ==== Guanzhou (InterDigital) considers this is merged in 8774. Otherwise we object to all versions of this. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208444 | P-CR | Approval | 23.700-08: KI#4: Evaluation and interim conclusions on automatic Hosting network selection. | MediaTek Inc. | Rel-18 | r04 agreed. Revised to S2-2209865, merging S2-2208293, S2-2208541 and S2-2208773 | Peter Hedman (Ericsson) provides r03 based on r01, now I need to re-implement based on r02. Peter Hedman (Ericsson) provides r04 ==== Revisions Deadline ==== Josep (DT) objects to r00. Huan (vivo) is OK to r04 ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209865 | P-CR | Approval | 23.700-08: KI#4: Evaluation and interim conclusions on automatic Hosting network selection. | MediaTek Inc., Futurewei, vivo, Ericsson | Rel-18 | Revision of S2-2208444r04, merging S2-2208293, S2-2208541 and S2-2208773. Approved | Approved | |
| 9.4.1 | S2-2208541 | P-CR | Approval | 23.700-08: KI#4, evaluation update on 7.4.2. | Futurewei | Rel-18 | Merged into S2-2209865 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) propose to mark it as 'merged into the revision of S2-2208444' ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208737 | P-CR | Approval | 23.700-08: KI#4, #5, Sol#13: Update to add one precondition for procedure 6.13.3.1. | CATT | Rel-18 | Approved | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged? ==== Final Deadline ==== Liping Wu (CATT) provides comments and ask for approval for this pCR. | Approved |
| 9.4.1 | S2-2208773 | P-CR | Approval | 23.700-08: KI #4: Update evaluation of Key Issue #4. | Ericsson | Rel-18 | Merged into S2-2209865 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) been merged to 08444 ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208774 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4. | Ericsson, LG Electronics | Rel-18 | CC#4: r25 agreed. Revised to S2-2209976. | Peter Hedman (Ericsson) provides r01 Saso (Intel) comments on localized service information advertised via SIB Josep (DT) comments, comments that only S2-2209005 captured automatic/manual selection aspects. Yishan (Huawei) provides comments and agree with comments from Josep (DT) and Saso (Intel) Guanzhou (InterDigital) comments and provides r02. Yishan (Huawei) comments and provides r03. Guanzhou (InterDigital) responds to Yishan (Huawei). Peter Hedman (Ericsson) provides r04 Amanda Xiang ( Futurewei ) provides comments and r04 Amanda Xiang ( Futurewei ) provides r05 on top of Ericsson's r04 Antoine (Orange) comments on r05. Chia-Lin (MediaTek) provides the comments on r05 Josep (DT) comments on r05. Yishan (Huawei) provides the comments on r05 Pallab (Nokia) provides comments on r05 and has concerns with many conclusions Huan (vivo) provides comments on r05 Saso (Intel) provides r06 removing the SIB option Gerald (MATRIXX Software) with comment. Peter Hedman (Ericsson) provides comments and question on the business relationships possible Pallab (Nokia) provides r07 based on comments provided earlier Antoine (Orange) asks Peter why he is discussing roaming interfaces; this is not in the scope of this Study. Peter Hedman (Ericsson) provides reply to Antoine Josep (DT) agrees to Peter (Ericsson's proposal) to clearly separate SNPN and PLMN cases. Huan (vivo) comments Antoine (Orange) Replies to Huan. Amanda Xiang ( Futurewei ) provides responses some questions on r05 and provides r08 Genadi (Lenovo) provides comments and r09. Antoine (Orange) replies to Amanda. Antoine (Orange) agrees with Genadi. Guanzhou (InterDigital) can't accept 7c. Yishan (Huawei) has concerns about 7c and 7d and provides r10. Chia-Lin (MediaTek) provides r11 based on r10 Peter Hedman (Ericsson) provides r12 Peter Hedman (Ericsson) provides some replies Antoine (Orange) provides r13. Chia-Lin (MediaTek) provides r14 based on r13 Huan(vivo) provides r15 Josep (DT) comments on r15, cannot accept point 4 in 8.4.3. Yishan (Huawei) provides r16 to capture comments from Josep (DT) Genadi (Lenovo) comments to Chia-Lin (MediaTek) and provides r17. Miguel (Qualcomm) provides r18 Pallab (Nokia) provides r19 Peter Hedman (Ericsson) provides reply to Josep Josep (DT) replies to Peter (Ericsson). Guanzhou (InterDigital) asks Peter (Ericsson) a question Amanda Xiang ( Futurewei ) provides r20 Peter Hedman (Ericsson) provides r21 Josep (DT) comments. Naman (Samsung) provides r22 on top of r21 Yishan (Huawei) provides r23 Chia-Lin (MediaTek) provides r24 based on r23 ==== Revisions Deadline ==== Josep (DT) asks Rapporteur what the proposed way forward regarding revisions is. Amanda Xiang ( Futurewei ) prefer to approve r23 as we don't agree with the deletion of some text in r24. Guanzhou (InterDigital) provides comments on revisions Josep (DT) is OK to go forward with >=r20, provides some overview of changes in the last five revisions. Peter Hedman (Ericsson) provides comments, and suggests to approve r24 and only do changes on top if really necessary Chia-Lin (MediaTek) also suggests to go with r24 Yishan (Huawei) also suggests to go with r24 or r23 Huan (vivo) is OK to r24 Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions. 1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3 2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.' Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions. 1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3 2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.' Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions. 1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3 2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.' Genadi (Lenovo) can only accept r22. Alternatively, we are OK to r24 + reverting 7d with the accompanying EN. Peter Hedman (Ericsson) suggests r24, or r24 + 'EN: It is FFS whether, e.g. home network, may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting ' + 'EN: (Complementary to Alt.1 in clause 8.4.2 also) It is FFS whether , in case of SNPN as hosting network, the hosting network may broadcast the supported localized service information (e.g. service identifiers and/or human readable service information, such as name, cost, service description) to help UEs discover the service and the hosting network. The localized service identifier may be pre-configured in the UE as per clause 8.4.2. The human readable service information is used for manual hosting network selection. UE may acquire this information from hosting network also via on-demand SIB while UE is RRC_IDLE or RRC_INACTIVE state in serving network. ==== Final Deadline ==== Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions. 1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3 2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.' Pallab (Nokia) is not OK with updates and requests to have conclusion text as proposed earlier. Peter Hedman (Ericsson) provides comments with proposal to go for r24 or r24 + changes Antoine (Orange) comments. Pallab (Nokia) responds to Peter Hedman (Ericsson) Peter Hedman (Ericsson) provides updated proposal as per comments | Revised |
| 9.4.1 | S2-2209976 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4. | Ericsson, LG Electronics, Futurewei | Rel-18 | Revision of S2-2208774r25. Approved | Approved | |
| 9.4.1 | S2-2208973 | P-CR | Approval | 23.700-08: KI#4: Conclusion for KI#4. | InterDigital | Rel-18 | Merged into (Covered by) S2-2208774 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged? Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774 Guanzhou (InterDigital) confirms this is merged into 8774. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2209005 | P-CR | Approval | 23.700-08: KI #4: Conclusion of Key Issue #4. | Qualcomm Inc | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) assumes this will be considered merged into S2-2208774. Miguel (Qualcomm) author confirms this is can be considered merged into S2-2208774 as suggested ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2209167 | P-CR | Approval | 23.700-08: KI #4: Evaluation and Conclusions update. | Samsung | Rel-18 | Merged into (Covered by) S2-2208774 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged? Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774 ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2209168 | P-CR | Approval | 23.700-08: KI#4: Update Sol#41 and remove ENs. | Samsung | Rel-18 | Approved | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged? Naman (Samsung) proposes to approve r00 ==== Final Deadline ==== Peter Hedman (Ericsson) agree to approve r00. | Approved |
| 9.4.1 | S2-2209175 | P-CR | Approval | 23.700-08: Conclusion for key issue#4. | Xiaomi | Rel-18 | Merged into (Covered by) S2-2208774 | Antoine (Orange) assumes this will be considered merged into S2-2208774. Jianning (Xiaomi) is ok to merge this paper into 8774 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | - | - | - | KI#5 | - | - | Docs:=10 | - | |
| 9.4.1 | S2-2208292 | P-CR | Approval | 23.700-08: KI #5: Update of Evaluation and Conclusion of Key Issue #5 PNI-NPN. | Vivo, China Telecom | Rel-18 | Merged into S2-2209867 and S2-2209866 | Peter Hedman (Ericsson) provides comments and suggests to merge in evaluation into 08735 and conclusion to 08298 Huan (vivo) agrees to be merged as suggested and is OK with the revision proposal from Peter ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208298 | P-CR | Approval | 23.700-08: 23.700-08: Updates to conclusions for KI#5. | Nokia, Nokia Shanghai Bell | Rel-18 | r10 agreed. Revised to S2-2209866, merging S2-2208318, S2-2208445 and S2-2209006 | Antoine (Orange) asks (1) what are the use cases and service requirements for accessing localized services via another network used as underlay and (2) which solution of the TR details how home network services can be accessed using a hosting network as overlay. Guanzhou (InterDigital) can't accept removing validity info from SoR. Peter Hedman (Ericsson) provides comments Pallab (Nokia) responds to Antoine (Orange). Pallab (Nokia) responds to Guanzhou (InterDigital). Pallab (Nokia) responds to Peter Hedman (Ericsson) Pallab(Nokia) provides r01 merging S2-2208318, S2-2208445, S2-2208772, to be taken as the basis for further discussion Yishan (Huawei) provides r02 to polish the conclusion Huan (vivo) comments Peter Hedman (Ericsson) provides r03 Josep (DT) comments. Antoine (Orange) provides r05. Guanzhou (InterDigital) comments and provides r04. Pallab (Nokia) provides r06 Antoine (Orange) provides r07. Myungjune (LGE) provides r08. Pallab (Nokia) is OK with r08. Josep (DT) does not agree r08 is correct. Provides r09 Miguel (Qualcomm) provides r10 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r09, r010 Josep (DT) objects to r05-r08. Is OK with 09, r10 Huan (vivo) is ok with r10 Yishan (Huawei) is ok with r10 Pallab (Nokia) proposes to approve r10 Peter Hedman (Ericsson) ok with r10 Chia-Lin (MediaTek) can only accept r10 Guanzhou (InterDigital) is OK with r09/r10. Miguel (Qualcomm) can only accept r10 Amanda (Futurewei) prefer to approve r10, but can live with r09 ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209866 | P-CR | Approval | 23.700-08: 23.700-08: Updates to conclusions for KI#5. | Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics | Rel-18 | Revision of S2-2208298r10, merging S2-2208318, S2-2208445 and S2-2209006. Approved | Approved | |
| 9.4.1 | S2-2208318 | P-CR | Approval | 23.700-08: KI#5, Update conclusion on KI#5. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209866 | Peter Hedman (Ericsson) provides comments and suggests we merge in conclusion to 08298 Pallab (Nokia) comments that a revision r01 has been provided in 08298 merging the conclusion content from 08318 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208445 | P-CR | Approval | 23.700-08: KI#5: Evaluation and interim conclusions on UE for accessing the localized services in a registered Hosting network. | MediaTek Inc. | Rel-18 | Merged into S2-2209866 | Peter Hedman (Ericsson) provides comments and suggests to merge in evaluation to 08735 and conclusion to 08298 Pallab (Nokia) comments that a revision r01 has been provided in 08298 merging the conclusion content from 8445 Chia-Lin (MediaTek) is ok to merge the pCR to S2-2208298 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208542 | P-CR | Approval | 23.700-08: KI#5, evaluation and conclusion update . | Futurewei | Rel-18 | Noted | Guillaume (MediaTek Inc.) comments that the subject of this discussion is wrong (8542): it is commenting on 8452 instead . Guanzhou (InterDigital) asks questions. Amanda Xiang ( Futurewei ) replies to InterDigital Myungjune (LGE) provides comments. Josep (DT) comments on adding 'if UE is in good coverage of the hosting network' as condition Pallab (Nokia) provides comments and concurs with concerns raised by other companies Amanda Xiang ( Futurewei ) provides responses to Nokia, DT and LGE and provide r02 Josep (DT) comments that the issue of coverage is a bit different to that of QoS/QoE. Amanda Xiang ( Futurewei ) response to DT's comment and provides r03 Myungjune (LGE) comments. Josep (DT) comments. Pallab (Nokia) objects to r00-r02 Amanda Xiang ( Futurewei ) provides r04 ==== Revisions Deadline ==== Josep (DT) is fine with r04. Pallab (Nokia) objects to all revisions and proposes to NOTE Guanzhou (InterDigital) objects to all versions. Amanda Xiang ( Futurewei ) responses to Nokia and InterDigital Guanzhou (InterDigital) responds to Amanda (Futurewei). ==== Final Deadline ==== | Noted |
| 9.4.1 | S2-2208735 | P-CR | Approval | 23.700-08: KI#5: Update evaluation of solutions for KI#5. | CATT | Rel-18 | r04 agreed. Revised to S2-2209867, merging S2-2208292 and S2-2208772 | Liping Wu (CATT) provides r01 Amanda Xiang ( Futurewei ) provides r02 Peter Hedman (Ericsson) looks ok and happy to support Liping Wu (CATT ) provides comments and ask Amanda to align the content between evaluation and conclusion paper. Amanda Xiang ( Futurewei ) provides r03 to align with the conclusion and evaluation. Peter Hedman (Ericsson) provides r04 ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209867 | P-CR | Approval | 23.700-08: KI#5: Update evaluation of solutions for KI#5. | CATT, Futurewei, Ericsson | Rel-18 | Revision of S2-2208735r04, merging S2-2208292 and S2-2208772. Approved | Approved | |
| 9.4.1 | S2-2208772 | P-CR | Approval | 23.700-08: KI#5: Evaluation and conclusion for Key Issue #5. | Ericsson | Rel-18 | Merged into S2-2209867 and S2-2209866 | Pallab (Nokia) proposes to merge the conclusions into 08298 and provides r01 removing the conclusions part. A revision of S2-2208298r01 is provided including the conclusions from this paper. Peter Hedman (Ericsson) propose to mark the P-CR as merged into 08735 (evaluation) and 08298 (conclusion) ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2209006 | P-CR | Approval | 23.700-08: KI #5: Conclusion of Key Issue #5. | Qualcomm Inc. | Rel-18 | Merged into S2-2209866 | Pallab (Nokia) comments and thinks that some of the conclusions are not clear Josep (DT) comments on hosting network ID. Peter Hedman (Ericsson) provides comments Josep (DT) finds Peter's proposal regarding network identifiers OK. Guanzhou (InterDigital) asks can we assume this is merged in 8298 Pallab (Nokia) proposes to consider this as merged to 8298 ==== Revisions Deadline ==== Josep (DT) objects to this pCR. Guanzhou (InterDigital) considers this is merged in 8298. Otherwise we object to this tdoc. ==== Final Deadline ==== | Merged |
| 9.4.1 | - | - | - | KI#6 | - | - | Docs:=11 | - | |
| 9.4.1 | S2-2208314 | P-CR | Approval | 23.700-08: KI#6, Update evaluation on KI#6. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209868 | Peter Hedman (Ericsson) proposes to merge this into 09073. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208315 | P-CR | Approval | 23.700-08: KI#6, Update conclusion on KI#6. | Huawei, HiSilicon | Rel-18 | Noted | Peter Hedman (Ericsson) provides question Pallab (Nokia) shares the same view as Ericsson Chia-Lin (MediaTek) shares the same view as Nokia and Ericsson ==== Revisions Deadline ==== Josep (DT) objects to this pCR. Overlapping with main discussion thread in 8771. Pallab (Nokia) also proposes to NOTE the pCR ==== Final Deadline ==== | Noted |
| 9.4.1 | S2-2208446 | P-CR | Approval | 23.700-08: KI#6: Evaluation and interim conclusion on the existing mechanism reused for UE returning from Hosting network. | MediaTek Inc. | Rel-18 | Merged into (Covered by) S2-2208771 | Peter Hedman (Ericsson) provides comments and propose to mark P-CR as merged into other tdocs Chia-Lin (MediaTek) is ok to merge to S2-2208771 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208520 | P-CR | Approval | 23.700-08: Conclusion on KI#6. | LG Electronics | Rel-18 | Merged into (Covered by) S2-2208771 | Guanzhou (InterDigital) assumes this is merged in S2-2208771?. Myungjune (LGE) is ok to merge this into S2-2208871. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2208736 | P-CR | Approval | 23.700-08: KI#6: Update evaluation for KI#6. | CATT | Rel-18 | Merged into (Covered by) S2-2208771 | ==== Revisions Deadline ==== Peter Hedman (Ericsson) I assume this has been merged? Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8771 ==== Final Deadline ==== Liping Wu (CATT) provides comments and ask for marking the pCR 'merged into 2208771'. | Merged |
| 9.4.1 | S2-2208771 | P-CR | Approval | 23.700-08: KI#6: Evaluation and conclusion of Key Issue #6. | Ericsson, Qualcomm | Rel-18 | CC#3: r08 agreed. Revised to S2-2209936. | Myungjune (LGE) provides r01. Pallab (Nokia) provides comments on r01. Myungjune (LGE) replies to Pallab (Nokia). Peter Hedman (Ericsson) provides r02 Huan (vivo) comments Guanzhou (InterDigital) provides r03. Guanzhou (InterDigital) provides r04. And please ignore r03. Prabhu (NEC) responds to Huan (vivo) and Peter (Ericsson), and provides r05. Pallab (Nokia) objects to all revisions from r00-r05. Provides r06 Miguel (Qualcomm) responds to Pallab (Nokia), believes informative annex may be overkill Peter Hedman (Ericsson) provides question why Nokia objects to r00, and provides r07 Guanzhou (InterDigital) provides r08. Miguel (Qualcomm) still prefers r00 over r06 and r07. Prabhu (NEC) clarifies a need for new mechanism to address the requirements of KI #6 and provides r09. Ashok (Samsung) is fine with r08. Not Ok with r09 ==== Revisions Deadline ==== Guanzhou (InterDigital) suggests to go with r08. Myungjune (LGE) support objects r09 and ok with r06 r07, r08. Pallab (Nokia) responds to Peter Hedman (Ericsson). OK with r06, r07. Objects to all other revisions Huan (vivo) prefers r08, is ok to r07. Prabhu (NEC) responds to Ashok (Samsung). Peter Hedman (Ericsson) ok with r08, r07, r06, r02, r00 Prabhu (NEC) responds to Myungjune (LGE). Ashok (Samsung) clarifies to Prabhu (NEC) Chia-Lin (MediaTek) is ok with r07 or r08. Guanzhou (InterDigital) only accepts r08 and points out other versions have evaluation text which is supposed to be merged with 9073 Miguel (Qualcomm) prefers r00, but can live with r08 Genadi (Lenovo) prefers r08 or r07. ==== Final Deadline ==== Pallab (Nokia) OK with r08. | Revised |
| 9.4.1 | S2-2209936 | P-CR | Approval | 23.700-08: KI#6: Evaluation and conclusion of Key Issue #6. | Ericsson, Qualcomm, LG Electronics | Rel-18 | Revision of S2-2208771r08. Approved | Approved | |
| 9.4.1 | S2-2208971 | P-CR | Approval | 23.700-08: KI#6: Update of the evaluation. | InterDigital | Rel-18 | Merged into S2-2209868 | Peter Hedman (Ericsson) provides question if we can mark the paper as merged into 09073? ==== Revisions Deadline ==== Guanzhou (InterDigital) confirms this is merged into 9073. ==== Final Deadline ==== | Merged |
| 9.4.1 | S2-2209073 | P-CR | Approval | 23.700-08: KI#6: Evaluation and conclusion for KI#6. | NEC | Rel-18 | r02 agreed. Revised to S2-2209868, merging S2-2208314 and S2-2208971 | Guanzhou (InterDigital) propose r01 that merges S2-2208971. (resent to correct the wrong meeting number in the subject line) Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== Guanzhou (InterDigital) is OK with r02. ==== Final Deadline ==== | Revised |
| 9.4.1 | S2-2209868 | P-CR | Approval | 23.700-08: KI#6: Evaluation and conclusion for KI#6. | NEC, InterDigital | Rel-18 | Revision of S2-2209073r02, merging S2-2208314 and S2-2208971. Approved | Approved | |
| 9.4.1 | S2-2209139 | P-CR | Approval | 23.700-08: KI#6: Update of the conclusions. | InterDigital | Rel-18 | Noted | Prabhu (NEC) provides r01. Pallab (Nokia) provides comments and raises concerns with the proposal. Proposes to NOTE. Myungjune (LGE) provides comments. Chia-Lin (MediaTek) shares the same view as LGE and Nokia Ashok (Samsung ) comments Josep (DT) also agrees with others, comments that the approach in this pCR would be difficult to deploy. Guanzhou (InterDigital) comments. Prabhu (NEC) responds Josep (DT) and Ashok (Samsung). ==== Revisions Deadline ==== Josep (DT) objects to this pCR. Content is already included in discussion 8771, where the bulk of the discussion happened (e.g. r09 can be considered a merger as it includes avoidance-based) ==== Final Deadline ==== | Noted |
| 9.4.1 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=4 | - | |
| 9.4.1 | S2-2208312 | P-CR | Approval | 23.700-08: KI#5, Update evaluation on KI#5. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.4.1 | S2-2208311 | P-CR | Approval | 23.700-08: KI#4, Update evaluation on KI#4. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.4.1 | S2-2208459 | P-CR | Approval | 23.700-08: KI#2: Additional conclusion on SNPN access mode. | Intel | Rel-18 | Not Handled | Rainer (Nokia) asks for clarification. Saso (Intel) replies to Rainer (Nokia). Rainer (Nokia) replies and is ok with 8459 as is.. Yishan (Huawei) comments Rainer (Nokia) replies. Saso (Intel) replies to Yishan. ==== Revisions Deadline ==== Yishan (Huawei) replies. ==== Final Deadline ==== | Not Handled |
| 9.4.1 | S2-2209174 | P-CR | Approval | 23.700-08: Conclusion for key issue#3. | Xiaomi | Rel-18 | Not Handled | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.4.2 | - | - | - | Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | - | - | Docs:=8 | - | |
| 9.4.2 | S2-2208426 | CR | Approval | 23.501 CR3714 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | r05 agreed. Revised to S2-2209869. | Omkar (CableLabs) provides r01 and comments Saso (Intel) provides r02 and comments Ashok (Samsung) comments Omkar (CableLabs) provides r03 and comments Saso (Intel) replies to Ashok Ashok (Samsung) responds to Saso Saso (Intel) comments on r03 and proposes to focus on r02 Peter Hedman (Ericsson) provides comments/questions Saso (Intel) replies to Peter Yishan (Huawei) provides r04 Saso (Intel) provides r05 Peter Hedman (Ericsson) provides reply ==== Revisions Deadline ==== Yishan (Huawei) is ok with r05 and object to r00~r04 Rainer (Nokia) is ok with r05. Peter Hedman (Ericsson) provides comments that some content is dependent on feedback from CT1 Saso (Intel) proposes to agree the CRs with a note in the official meeting report. Omkar (CableLabs) is ok with r05, objects to r00. ==== Final Deadline ==== Saso (Intel) checks with the Rapporteur whether this CR (currently marked as approved) needs to be reopened. | Revised |
| 9.4.2 | S2-2209869 | CR | Approval | 23.501 CR3714R1 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | Revision of S2-2208426r05. Approved (Some content is dependent on feedback from CT WG1) | Agreed | |
| 9.4.2 | S2-2208427 | CR | Approval | 23.502 CR3565 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Agreed |
| 9.4.2 | S2-2208512 | CR | Approval | 23.502 CR3569 (Rel-18, 'B'): Equivalent SNPN support | OPPO, Ericsson, Nokia, Nokia Shanghai Bell, Mediatek Inc., LG Electronics | Rel-18 | Approved | Marco (Huawei) comments that the CR to 23.502 needs to be aligned to 23.501 on UE capability ==== Revisions Deadline ==== Myungjune (LGE) proposes to approve r00. Fei (OPPO) replies. Peter Hedman (Ericsson) agree that it make sense to agree r00 Peter Hedman (Ericsson) agree to approve r00 ==== Final Deadline ==== | Agreed |
| 9.4.2 | S2-2208767 | CR | Approval | 23.501 CR3730 (Rel-18, 'B'): Equivalent SNPN support | Ericsson, OPPO, LG Electronics, Nokia, Nokia Shanghai Bell, MediaTek Inc. | Rel-18 | Approved | Yishan (Huawei) asks for clarification Fei (OPPO) responds to Yishan (Huawei). Yishan (Huawei) responds to Fei (OPPO) and provides r01. Myungjune (LGE) replies to Yishan (Huawei) Fei (OPPO) agree with Myungjune Yishan (Huawei) asks questions Fei (OPPO) provided response to Yishan Peter Hedman (Ericsson) provides reply Yishan (Huawei) replies to Peter Hedman (Ericsson) and Fei (OPPO) and agree to send the LS to CT1 Myungjune (LGE) replies to Yishan (Huawei). Yishan (Huawei) answers. Peter Hedman (Ericsson) provides question Yishan (Huawei) answers to Peter Hedman (Ericsson) ==== Revisions Deadline ==== Myungjune (LGE) objects r01 and proposes to approve r00. Rainer (Nokia) supports r00. Fei (OPPO) supports r00 ==== Final Deadline ==== | Agreed |
| 9.4.2 | S2-2208429 | CR | Approval | 23.503 CR0745 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | r03 agreed. Revised to S2-2209870. | Peter Hedman (Ericsson) provides questions Saso (Intel) replies to Peter; provides r01 Marco (Huawei) provide r02 Saso (Intel) is OK with r02 Josep (DT) comments, provides r03. Saso (Intel) is OK with r03 ==== Revisions Deadline ==== Peter Hedman (Ericsson) provides comments, and CR depends on CT1 feedback Saso (Intel) replies to Peter Hedman (Ericsson) that there is no intent to introduce SNPN access mode to EPS/EPC. ==== Final Deadline ==== | Revised |
| 9.4.2 | S2-2209870 | CR | Approval | 23.503 CR0745R1 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | Revision of S2-2208429r03. Approved | Agreed | |
| 9.4.2 | S2-2208434 | CR | Approval | 23.402 CR2997 (Rel-18, 'B'): Support of Non-3GPP access for SNPN | Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | Approved | ==== Revisions Deadline ==== Peter Hedman (Ericsson) provides comment that usage of SNPN access mode depends on CT1 feedback, and assume we do not propose to introduce SNPN access mode to EPS/EPC. Saso (Intel) replies to Peter Hedman (Ericsson) that there is no intent to introduce SNPN access mode to EPS/EPC. ==== Final Deadline ==== | Agreed |
| 9.5 | - | - | - | Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) | - | - | Docs:=16 | - | |
| 9.5 | - | - | - | LS’s in | - | - | Docs:=1 | - | |
| 9.5 | S2-2208168 | LS In | Action | LS from MITRE Engenuity Open Generation 5G Consortium: | MITRE Engenuity Open Generation 5G Consortium (S2-2208168) | Postponed | Stefano Faccin (Qualcomm) proposes to postpone answering to this LS | Postponed | |
| 9.5 | - | - | - | KI#1 | - | - | Docs:=4 | - | |
| 9.5 | S2-2208983 | P-CR | Approval | 23.700-58: KI#1: Solution #4 update. | InterDigital | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.5 | S2-2208975 | P-CR | Approval | 23.700-58: KI#1: Update to evaluation. | InterDigital | Rel-18 | Approved | Pallab (Nokia) comments and requests for clarification Guanzhou (InterDigital) responds to Pallab (Nokia). Pallab (Nokia) responds to Guanzhou (InterDigital) ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.5 | S2-2208301 | P-CR | Approval | 23.700-58: 23.700-58: Updates to conclusions for KI#1. | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2209579. | Guanzhou (InterDigital) comments and provides r01 Pallab (Nokia) responds to Guanzhou (InterDigital) Guanzhou (InterDigital) responds to Pallab (Nokia). Ashok (Samsung) need clarification Shabnam (Ericsson) provides comments Ashok (Samsung) responds to Shabnam (Ericsson) Guanzhou (InterDigital) responds to Shabnam(Ericsson) ==== Revisions Deadline ==== Shabnam (Ericsson) thanks for the clarification, I wonder do you plan to address this with soln in future or should we change the EN to a NOTE stating restricted discovery is not supported? Do you believe existing ProSe mechanism can't be reused, I thought that can be reused in cases as described when under MNO. Guanzhou (InterDigital) accepts only r01 and objects to other versions. ==== Final Deadline ==== | Revised |
| 9.5 | S2-2209579 | P-CR | Approval | 23.700-58: 23.700-58: Updates to conclusions for KI#1. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2208301r01. Approved | Approved | |
| 9.5 | - | - | - | KI#2 | - | - | Docs:=3 | - | |
| 9.5 | S2-2209122 | P-CR | Approval | 23.700-58: TR 23.700-58 Conclusions Key Issue #2. | Qualcomm Incorporated | Rel-18 | r03 agreed. Revised to S2-2209580, merging S2-2209079 | Guanzhou (InterDigital) provides r01. Antoine (Orange) comments on the 1st bullet. Stefano (Qualcomm) provides R02. Runze (Huawei) provides R03. Runze (Huawei) provides URL of R03. ==== Revisions Deadline ==== Runze (Huawei) supports R03 only, but no other versions. ==== Final Deadline ==== | Revised |
| 9.5 | S2-2209580 | P-CR | Approval | 23.700-58: TR 23.700-58 Conclusions Key Issue #2. | Qualcomm Incorporated, Huawei | Rel-18 | Revision of S2-2209122r03, merging S2-2209079. Approved | Approved | |
| 9.5 | S2-2209079 | P-CR | Approval | 23.700-58: Conclusion of Key Issue 2. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209580 | Guanzhou (InterDigital) suggests this is merged in 9122. Runze (Huawei) is fine to merge this paper into 2209122 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.5 | - | - | - | KI#3 | - | - | Docs:=8 | - | |
| 9.5 | S2-2208780 | P-CR | Approval | 23.700-58: KI#3, Sol#7 Clarifications & address eNs. | Ericsson | Rel-18 | Approved | Guanzhou (InterDigital) comments and asks for clarifications. Shabnam (Ericsson) provides comments sorry I seems I have missed a few emails including this one ?? bad macros ==== Revisions Deadline ==== Guanzhou (InterDigital) comments. ==== Final Deadline ==== | Approved |
| 9.5 | S2-2208299 | P-CR | Approval | 23.700-58: 23.700-58: Updates to evaluation for KI#3. | Nokia, Nokia Shanghai Bell, InterDigital | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.5 | S2-2209082 | P-CR | Approval | 23.700-58: KI#3: Evaluation update. | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2209581. | Guanzhou (InterDigital) comments and provides r01. Runze (Huawei) accepts r01. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.5 | S2-2209581 | P-CR | Approval | 23.700-58: KI#3: Evaluation update. | Huawei, HiSilicon | Rel-18 | Revision of S2-2209082r01. Approved | Approved | |
| 9.5 | S2-2209083 | P-CR | Approval | 23.700-58: KI#3: interim Conclusion. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209582 | Pallab (Nokia) proposes to NOTE this paper. As discussed in the evaluation paper S2-2208299, we believe the network based DAA mechanism does not work in practical cases. So we do not agree to take Sol#2 into normative phase. Runze (Huawei) proposed to merge the paper into 2209129. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.5 | S2-2208300 | P-CR | Approval | 23.700-58: 23.700-58: Conclusion for KI#3. | Nokia, Nokia Shanghai Bell, InterDigital | Rel-18 | Merged into S2-2209582 | Stefano Faccin (Qualcomm) proposes to merge into 9129 Pallab (Nokia) agrees to merge into 9129 ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.5 | S2-2209129 | P-CR | Approval | 23.700-58: TR 23.700-58 Conclusions Key Issue #3. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2209582, merging S2-2208300 and S2-2209083 | Guanzhou (InterDigital) propose r01. Guanzhou (InterDigital) propose r01. (resent to correct the wrong meeting number in the subject line) Shabnam (Ericsson) provides comments and r02 to include area specific DAA Shabnam (Ericsson) provides r03 adding Ericsson as supporting company and clarify soln# which was missed. Stefano Faccin (Qualcomm) comments and is supportive Runze (Huawei) provides r04. Guanzhou (InterDigital) provides r05 ==== Revisions Deadline ==== Guanzhou (InterDigital) accepts r05 and r01 and objects to other versions. Runze (Huawei) supports r04 and r05, objects to other versions. ==== Final Deadline ==== | Revised |
| 9.5 | S2-2209582 | P-CR | Approval | 23.700-58: TR 23.700-58 Conclusions Key Issue #3. | Qualcomm Incorporated, Ericsson, InterDigital | Rel-18 | Revision of S2-2209129r05, merging S2-2208300 and S2-2209083. Approved | Approved | |
| 9.6 | - | - | - | Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) | - | - | Docs:=0 | - | |
| 9.7.1 | - | - | - | Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) | - | - | Docs:=48 | - | |
| 9.7.1 | - | - | - | Key Issue #1 | - | - | Docs:=19 | - | |
| 9.7.1 | S2-2208398 | P-CR | Approval | 23.700-25: KI #1, Sol #14: Update to address ENs. | Ericsson | Rel-18 | Noted | Sebastian (Qualcomm) objects to the PCR Shabnam (Ericsson) provides comments with r01, as noted we may not choose taking this on board in Rel-18, we would like to update the solution to correct and answer questions for completeness. The EN is still there. Sebastian (Qualcomm) replies Shabnam (Ericsson) and we are providing updates to soln already in the TR to address your comments right and we have not removed the EN which says whether it is in scope is FFS, so no contradiction here other than cleanup of the TR. ==== Revisions Deadline ==== Sebastian (Qualcomm) objects to r01 ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2208399 | LS OUT | Approval | [DRAFT] LS on 5G Timing Resiliency | Ericsson | Rel-18 | Noted | Shabnam (Ericsson) provides r01 as discussed in offline call Sebastian (Qualcomm) objects to the LS for the same reasons as given for S2-2208398 ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2208400 | DISCUSSION | Decision | FS_5TRS_URLLC, KI #1: 5GS network timing synchronization status and reporting | Ericsson | Rel-18 | Noted | Sebastian (Qualcomm) comments ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2208403 | P-CR | Approval | 23.700-25: KI #1, Annex A: An alternative to report a time synchronization status to UEs. | Ericsson | Rel-18 | r03 agreed. Revised to S2-2209871. Rapporteur: Handle independently | Sebastian (Qualcomm) comments Shabnam (Ericsson) provides comments and r02, please ignore r01 as I missed one comment from Qualcomm in that revision. Sebastian (Qualcomm) provides r03 ==== Revisions Deadline ==== Sebastian (Qualcomm) is fine with r03, objects to other versions. ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209871 | P-CR | Approval | 23.700-25: KI #1, Annex A: An alternative to report a time synchronization status to UEs. | Ericsson | Rel-18 | Revision of S2-2208403r03. Approved | Approved | |
| 9.7.1 | S2-2208554 | P-CR | Approval | 23.700-25: Conclusion for key issue 1. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2209875 Rapporteur: Merge into S2-2209101 | Shabnam (Ericsson) provides comments that we would not like to include any conclusion on SIB without RAN consultation. Issues we see are described in 8400, will take the discussion under 9101 as proposed by rapporteur. Devaki (Nokia) proposes that this is merged with 9103. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208555 | P-CR | Approval | 23.700-25: Annex to capture methods to notify UE regarding RAN time sync for KI#1 . | Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2209872. Rapporteur: Handle independently | Shabnam (Ericsson) provides comments ok with the proposal but we also added a general EN on our Annex submission for RAN dependency, additional question Devaki (Nokia) replies to Shabnam. Sebastian (Qualcomm) comments zhendong (ZTE) comments Devaki (Nokia) provides r01. Sebastian (Qualcomm) provides r02 ==== Revisions Deadline ==== Sebastian (Qualcomm) is fine with r02 if the figure is aligned with the text (remove step 2; replace steps 8-10 by one step 'UE enters RRC_Connected', renumber figure and text); objects to other versions Devaki (Nokia) uploaded r03 before the deadline (with fix for the figure) but the email was not sent to the reflector by mistake. ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209872 | P-CR | Approval | 23.700-25: Annex to capture methods to notify UE regarding RAN time sync for KI#1 . | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2208555r03. Approved | Approved | |
| 9.7.1 | S2-2208609 | P-CR | Approval | 23.700-25: Conclusion for FS_5TRS_URLLC KI#1. | Samsung | Rel-18 | Merged into S2-2209875 Rapporteur: Merge into S2-2209101 | Devaki (Nokia) proposes that this is merged with 9103. Sang-Jun (Samsung) agrees that this is merged with 9103. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208626 | P-CR | Approval | 23.700-25: KI#1: Conclusion proposal. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209875 Rapporteur: Merge into S2-2209101 | Devaki (Nokia) proposes that this is merged with 9103. Runze (Huawei) agrees to merge this paper into 9103. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208955 | P-CR | Approval | 23.700-25: KI#1 adding the notifying UE time sync status method to Annex. | ZTE | Rel-18 | r01 agreed. Revised to S2-2209873. Rapporteur: Handle independently | Shabnam (Ericsson) provides comments that the proposal is similar to Ericsson one in 8403, whether ZTE sees opportunity to merge? zhendong (ZTE) provides the response Sebastian (Qualcomm) comments zhendong (ZTE) provides r01 ==== Revisions Deadline ==== Runze (Huawei) comments on r01 Zhendong (ZTE) provides the response to runze (huawei) Sebastian (Qualcomm) supports Zhendong ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209873 | P-CR | Approval | 23.700-25: KI#1 adding the notifying UE time sync status method to Annex. | ZTE | Rel-18 | Revision of S2-2208955r01. Approved | Approved | |
| 9.7.1 | S2-2209101 | P-CR | Approval | 23.700-25: KI#1: Update solution 1 to clarify SIB aspects and add details in annex on ciphering of time synchronization status in SIB. | Qualcomm Incorporated | Rel-18 | r01 agreed. Revised to S2-2209874. Rapporteur: Handle independently (solution update not needed) | Josep (DT) supports this approach, would like to co-sign. Shabnam (Ericsson) provides comments as depending on responses and potential merger revision may be provided later. Shabnam (Ericsson) provides comments for additional update as per offline discussion Sebastian (Qualcomm) provides r01 Sebastian (Qualcomm) replies to Josep ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209874 | P-CR | Approval | 23.700-25: KI#1: Update solution 1 to clarify SIB aspects and add details in annex on ciphering of time synchronization status in SIB. | Qualcomm Incorporated, Deutsche Telekom | Rel-18 | Revision of S2-2209101r01. Approved | Approved | |
| 9.7.1 | S2-2209103 | P-CR | Approval | 23.700-25: Conclusion for key issue 1. | Qualcomm | Rel-18 | r07 agreed. Revised to S2-2209875, merging S2-2208554, S2-2208609 and S2-2208626 Rapporteur: Handle independently. (isolated issue on information reported) | Jari (NTT DOCOMO) comments Devaki (Nokia) provides r01 and comments. Shabnam (Ericsson) provides comments and r02, clarifying some aspects and adding EN on RAN dependency and co-signs Sebastian (Qualcomm) replies to Jari Jari (NTT DOCOMO) responds to Sebastian Sebastian (Qualcomm) provides r03 Runze (Huawei) provides r04. Shabnam (Ericsson) provides comments and r05 Sebastian (Qualcomm) provides r06 Shabnam (Ericsson) provides comments that the updated text is not making sense see below, provides r07 Runze (Huawei) replies to Sebastian (Qualcomm). ==== Revisions Deadline ==== Runze (Huawei) supports r04, r06, r07, and objects to other versions. ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209875 | P-CR | Approval | 23.700-25: Conclusion for key issue 1. | Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, AT&T, Verizon, Huawei | Rel-18 | Revision of S2-2209103r07, merging S2-2208554, S2-2208609 and S2-2208626. Approved | Approved | |
| 9.7.1 | S2-2209118 | P-CR | Approval | 23.700-25: Conclusions based on the reply from ITU-T SG15 Q13/Q15 on monitoring of time synchronization and relevant parameters. | Qualcomm Incorporated | Rel-18 | Postponed | Shabnam (Ericsson) provides comments and r01 on Ericsson view and analysis for the LS response, though it is not yet available for 3GPP. ==== Revisions Deadline ==== Shabnam (Ericsson) comments that to be fair since 3GPP/SA2 has not yet officially received any response and we are creating Annex to capture different options, we should note this paper. though I would encourage companies to review the r01 and consider their responses so we have a common view to work from next meeting. Devaki (Nokia) proposes to postpone this paper as we are waiting for the LS response officially (we cannot accept r01 however). Sebastian (Qualcomm) objects to r01; disagrees with most of the observations in r01 as they go beyond what is contained in the ITU-T LS; r01 also mistakenly assumes that the network would need to calculate the end-to-end accuracy and provide it to the UE but that has not been proposed; Sebastian (Qualcomm) is ok to postpone the paper; suggests to have an offline call soon after this meeting to try to converge on the open points (see email for details) ==== Final Deadline ==== | Postponed |
| 9.7.1 | S2-2209169 | LS OUT | Approval | [DRAFT] LS on Time Synchronization Status notification towards UE(s) | Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2209876. Rapporteur: Use this as the baseline for time sync status notification | Shabnam (Ericsson) provides r01 Sebastian (Qualcomm) provides r02 Devaki (Nokia) provides r03. ==== Revisions Deadline ==== Sebastian (Qualcomm) is ok with r03 and r02; objects to other versions. Runze (Huawei) prefers rev03. ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209876 | LS OUT | Approval | LS on Time Synchronization Status notification towards UE(s) | SA WG2 | Rel-18 | Revision of S2-2209169r03. Approved | Approved | |
| 9.7.1 | - | - | - | Key Issue #2 | - | - | Docs:=9 | - | |
| 9.7.1 | S2-2208401 | P-CR | Approval | 23.700-25: KI#2, Sol#7: Evaluation of the deferred 5GC-MT-LR-based approach. | Ericsson | Rel-18 | Noted | Scott (Inspur) objects the paper. ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2208477 | P-CR | Approval | 23.700-25: TR 23.700-25-040: Updates to the solutions of Key Issue #2 . | Inspur | Rel-18 | Merged into S2-2209877 Rapporteur: 5GC-MT-LR-based approach – variant #2 | Shabnam (Ericsson) provides comments that no budget for soln update as per workplan, Objects proposal to change/revise the solution at this point. Devaki (Nokia) proposes to merge (and discuss) the conclusion aspects (not related to MT-LR) under 8556. Scott(Inspur) replies. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208478 | P-CR | Approval | 23.700-25: TR 23.700-25-040: Updates to the conclusion of Key Issue #2 . | Inspur | Rel-18 | Noted | Shabnam (Ericsson) provides comments as explained in 8401 and as we see no need to have multiple solns for the same issue & as we are only focusing on TA level and homogeneous TA status across RA as Qualcomm is proposing no need for additional complexity of this mechanism, we Object inclusion of this approach. Sebastian (Qualcomm) supports the comments provided by Ericsson and objects to the pCR ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2208556 | P-CR | Approval | 23.700-25: Conclusion for key issue 2 update to address the EN. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | r03 agreed. Revised to S2-2209877, merging S2-2208477, S2-2208791, S2-2209116 and S2-2208627 Rapporteur: Can we this as the baseline for conclusion to capture the way forward regarding cell level granularity for coverage? Variant #1 | Jari (NTT DOCOMO) comments Devaki (Nokia) comments Devaki (Nokia) provides r01. Jari (NTT DOCOMO) provides r02 Sebastian (Qualcomm) provides r03 Devaki (Nokia) provides r04 for consideration. Jari (NTT DOCOMO) responds to Devaki ==== Revisions Deadline ==== Devaki (Nokia) comments. Sebastian (Qualcomm) can only accept r03; objects to other versions Runze (Huawei) proposes to agree r03, but keep the last EN (Editor's note: How ASTI service activation/deactivation is impacted by TA or Cell level Requested Coverage Area is FFS.) in r03. Sebastian (Qualcomm) objects to proposal by Runze to keep the last EN in r03; we can only accept r03 as-is and object to other versions. Shabnam (Ericsson) proposes to go with r03, we concluded we will only use TA level for this release and if any Interactions with ASTI arises for TA then we will need to address that as part of the process? ==== Final Deadline ==== Runze (Huawei) can live with r03 as is. | Revised |
| 9.7.1 | S2-2209877 | P-CR | Approval | 23.700-25: Conclusion for key issue 2 update to address the EN. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2208556r03, merging S2-2208477, S2-2208791, S2-2209116 and S2-2208627. Approved | Approved | |
| 9.7.1 | S2-2208627 | P-CR | Approval | 23.700-25: KI#2: Update of conclusion. | Huawei, HiSilicon | Rel-18 | Merged into S2-2209877 Merged into S2-2208556? | Devaki (Nokia) proposes that this is merged with 8556. Sebastian (Qualcomm) objects to the PCR ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208791 | P-CR | Approval | 23.700-25: KI#2: Update conclusion for time synchronization service enhancements. | CATT | Rel-18 | Merged into S2-2209877 Rapporteur: Handle independently | Devaki (Nokia) proposes that this is merged with 8556. Yuan Tao (CATT) confirms this paper is merged with 8556. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208956 | P-CR | Approval | 23.700-25: KI#2, update the conclusion for the kI#2. | ZTE | Rel-18 | Noted | Sebastian (Qualcomm) objects to the PCR ==== Revisions Deadline ==== ==== Final Deadline ==== | Noted |
| 9.7.1 | S2-2209116 | P-CR | Approval | 23.700-25: Removing Editor's note on cell level granularity for coverage area. | Qualcomm Incorporated | Rel-18 | Merged into S2-2209877 Rapporteur: Cell level coverage area - Variant #2 | Devaki (Nokia) proposes that this is merged with 8556. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | - | - | - | Key Issue #3 | - | - | Docs:=2 | - | |
| 9.7.1 | S2-2208557 | P-CR | Approval | 23.700-25: Conclusions for KI#3 . | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Ericsson, ZTE | Rel-18 | r04 agreed. Revised to S2-2209878. Rapporteur: Use this as the baseline. | Devaki (Nokia) provides r01 as per offline discussion to allow the option to restrict coverage area and/or allow any coverage area in the subscription. Sang-Jun (Samsung) provides r02 with a small editorial change and adding Samsung as co-signer. Runze (Huawei) provides r03. Sebastian (Qualcomm) provides r04 Runze (Huawei) replies to Sebastian (Qualcomm), and provides r05. Sebastian (Qualcomm) replies ==== Revisions Deadline ==== Runze (Huawei) replied to Sebastian (Qualcomm). Devaki (Nokia) comments. Shabnam (Ericsson) provides comments and supports Nokia analysis but prefers to go with r04, can also accept r00. Revisions r01, r02, r03, r05 not acceptable as they either introduces wrong concept or ambiguity. Devaki (Nokia) proposes that we go with original version and work on the newly added bullet for next meeting. R04 is fine as well; r04+ '(optionally) an indication to allow AF requested Uu time synchronization error budget, start/stop time and/or Coverage Area always accepted' is also fine. Sebastian (Qualcomm) is ok with r00 and r04; objects to other versions; proposes to go for r04 with additional EN: 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS' Runze (Huawei) agrees with Sebastian (Qualcomm)'s proposal that go for r04 with additional EN: 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'. Runze (Huawei) objects to r00-r04 (without the EN) Devaki (Nokia) comments that r04 + proposed EN is fine. Shabnam (Ericsson) can accept r04 + proposed EN but wonders if the EN should start with 'Whether and then how...' . Sebastian (Qualcomm) supports Shabnam's (Ericsson) proposal. Also ok to start with 'Whether and then how...' Runze (Huawei) don't agree the EN start with 'Whether and then how...', insist the previous wording. ==== Final Deadline ==== Devaki (Nokia) comments that we should stick with 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'. Devaki (Nokia) proposes to go with r03 with 'enabling an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS' as discussed. Runze (Huawei)agrees with Devaki (Nokia)'s proposal to go with r03 with 'enabling an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'. Runze (Huawei) provides r06 in the revision and CC#4 folder as final revision, per chair's guidance. Devaki (Nokia) agrees with r06, reflects the proposal also from QCOM and E///. | Revised |
| 9.7.1 | S2-2209878 | P-CR | Approval | 23.700-25: Conclusions for KI#3 . | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Ericsson, ZTE, Samsung, Huawei | Rel-18 | Revision of S2-2208557r04. Approved | Approved | |
| 9.7.1 | - | - | - | Key Issue #5 | - | - | Docs:=2 | - | |
| 9.7.1 | S2-2208957 | P-CR | Approval | 23.700-25: KI#5, update the conclusion for the KI#5. | ZTE | Rel-18 | Merged into (Covered by) S2-2208187 | Devaki (Nokia) proposes that this is merged with 8187. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208187 | P-CR | Approval | 23.700-25: Update on conclusions for KI#5. | NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei, Ericsson | Rel-18 | Approved | ==== Revisions Deadline ==== ==== Final Deadline ==== | Approved |
| 9.7.1 | - | - | - | Key Issue #6 | - | - | Docs:=12 | - | |
| 9.7.1 | S2-2208424 | LS OUT | Approval | [DRAFT] LS OUT on UL scenario of reactive RAN feedback for burst sending time adjustment | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2209879. Rapporteur: Merge this into S2-2208612? | György (Ericsson) provides r01. Haiyang (Huawei) provides r02. György (Ericsson) comments. Haiyang (Huawei) provides reply to György (Ericsson). zhendong (ZTE) provides r03 ==== Revisions Deadline ==== Sebastian (Qualcomm) can only accept r00; objects to other versions; can accept r03 with the following changes: remove 'The mechanism allows the RAN to provide feedback to the AF to change the burst sending time based on the RAN TDD pattern.', remove '. SA2 kindly asks RAN2 to provide feedback on the proposal'; replace 'SA2 asks RAN2 group to kindly provide the feedback' by 'SA2 asks RAN2 group to inform SA2 if RAN2 considers it feasible to extend the reactive adaptation mechanism also to the UL case based on UE feedback to RAN using RRC signalling.' Haiyang (Huawei) provides r04 as an Alt: which is r03+ removing 'The mechanism allows the RAN to provide feedback to the AF to change the burst sending time based on the RAN TDD pattern.' and '. SA2 kindly asks RAN2 to provide feedback on the proposal'+ Replacing 'SA2 asks RAN2 group to kindly provide the feedback' by 'SA2 asks RAN2 group to inform SA2 if RAN2 considers it feasible to extend the reactive adaptation mechanism also to the UL case based on UE feedback to RAN using RRC signalling.' ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209879 | LS OUT | Approval | LS on UL scenario of reactive RAN feedback for burst sending time adjustment | SA WG2 | Rel-18 | Revision of S2-2208424r04. Approved | Approved | |
| 9.7.1 | S2-2208142 | LS In | Action | LS from RAN WG2: Reply LS on RAN feedback for low latency | RAN WG2 (R2-2208913) | Rel-18 | Noted | Sebastian (Qualcomm) proposes to note the LS | Noted |
| 9.7.1 | S2-2210161 | LS OUT | Approval | [DRAFT] LS on low latency communication applications to use RAN feedback on periodicity for scheduling | Samsung | Rel-18 | CC#4: r00 agreed. Revised to S2-2209964. | Sang-Jun (Samsung) provides r00 of S2-2210161 in the revision folder. | Revised |
| 9.7.1 | S2-2209964 | LS OUT | Approval | LS on low latency communication applications to use RAN feedback on periodicity for scheduling | SA WG2 | Rel-18 | Revision of S2-2210161r00. Approved | Approved | |
| 9.7.1 | S2-2208425 | P-CR | Approval | 23.700-25: Discussion on periodicity provisioning and update conclusion of KI#6. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2209880 Rapporteur: Merge this into S2-2208612? | György (Ericsson) comments. Devaki (Nokia) proposes that this is merged with 8612 as discussed. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208562 | P-CR | Approval | 23.700-25: Conclusion for key issue 6 update to address the ENs and some clarifications. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2209880 Rapporteur: Merge this into S2-2208612? | György (Ericsson) comments. Devaki (Nokia) proposes that this is merged with 8612 as discussed. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.1 | S2-2208612 | P-CR | Approval | 23.700-25: Conclusion for FS_5TRS_URLLC KI#6. | Samsung | Rel-18 | r06 agreed. Revised to S2-2209880, merging S2-2208425 and S2-2208562 Rapporteur: Can we use this as a baseline for KI#6 conclusion updates? | György (Ericsson) comments. Devaki (Nokia) comments. Sang-Jun (Samsung) provides r01. Sang-Jun (Samsung) replies to György (Ericsson). Jari (NTT DOCOMO) comments. Sang-Jun (Samsung) provides r02. Haiyang (Huawei) provides r03. Sang-Jun (Samsung) provides r04. György (Ericsson) provides r05. Sang-Jun (Samsung) replies to György (Ericsson) and proposes to go with r04 as discussed offline. Devaki (Nokia) comments that the newly proposed EN in r04 is strange (states the obvious that SA1 has to provide requirements which they do already. Sang-Jun (Samsung) provides r06 based on Devaki (Nokia)'s comments. ==== Revisions Deadline ==== Devaki (Nokia) objects to r05, ok with other versions. Sebastian (Qualcomm) objects to r05; proposes to go with r04 but replace 'EN: The above industrial applications behaviours regarding periodicity need to be confirmed by SA1.' by 'EN: Whether periodicity values are provided will be determined in a future meeting based on SA1 feedback' Sang-Jun (Samsung) proposes to go with r06 which is the same as Sebastian (Qualcomm)proposed. That is r04 but replace 'EN: The above industrial applications behaviours regarding periodicity need to be confirmed by SA1.' by 'EN: Whether periodicity values are provided will be determined in a future meeting based on SA1 feedback' ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209880 | P-CR | Approval | 23.700-25: Conclusion for FS_5TRS_URLLC KI#6. | Samsung | Rel-18 | Revision of S2-2208612r06, merging S2-2208425 and S2-2208562. Approved | Approved | |
| 9.7.1 | S2-2208860 | P-CR | Approval | 23.700-25: KI#6: Conclusion update. | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2209881. Rapporteur: Merge this into S2-2208612? | Devaki (Nokia) proposes that this is merged with 8612 as discussed. Haiyang (Huawei) suggests to keep this paper separately. Devaki (Nokia) comments that it is fine to treat this paper independently. György (Ericsson) comments. Haiyang (Huawei) provides r01. Haiyang (Huawei) provides r02. Jari (NTT DOCOMO) comments Haiyang (Huawei) provides reply to Jari (NTT DOCOMO). Sebastian (Qualcomm) provides r03 ==== Revisions Deadline ==== Sebastian (Qualcomm) is ok with r03, objects to other versions ==== Final Deadline ==== | Revised |
| 9.7.1 | S2-2209881 | P-CR | Approval | 23.700-25: KI#6: Conclusion update. | Huawei, HiSilicon | Rel-18 | Revision of S2-2208860r03. Approved | Approved | |
| 9.7.1 | S2-2208958 | P-CR | Approval | 23.700-25: KI#6, update the conclusion for the KI#6. | ZTE | Rel-18 | Noted | Sebastian (Qualcomm) provides r01 Haiyang(Huawei) checks whether this paper has been merged already Zhendong (ZTE) provides the response ==== Revisions Deadline ==== Devaki (Nokia) objects to r01, ok with the original version. Jari (NTTT DOCOMO) objects original and all revisions Zhendong (ZTE) explains the change, and asks Jari to reconsider Jari (NTTT DOCOMO) responds to zhendong ==== Final Deadline ==== | Noted |
| 9.7.1 | - | - | - | Documents exceeding TU Budget | - | - | Docs:=4 | - | |
| 9.7.1 | S2-2208610 | P-CR | Approval | 23.700-25: Conclusion for FS_5TRS_URLLC KI#3. | Samsung | Rel-18 | Not Handled Rapporteur: Merge this with S2-2208557 | Devaki (Nokia) proposes that this is merged with 8557. Sang-Jun (Samsung) agrees that this is merged with 8557. ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.7.1 | S2-2208628 | P-CR | Approval | 23.700-25: KI#3: Update of conclusion. | Huawei, HiSilicon | Rel-18 | Not Handled Rapporteur: Merge this with S2-2208557 | Devaki (Nokia) proposes that this is merged with 8557. ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.7.1 | S2-2208402 | P-CR | Approval | 23.700-25: KI #2, Conclusion: Update to address the EN. | Ericsson | Rel-18 | Not Handled Rapporteur: Merge this into S2-2208556 | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.7.1 | S2-2208976 | P-CR | Approval | 23.700-25: KI#5, Update of Solution #9. | NTT DOCOMO | Rel-18 | Not Handled Rapporteur: | ==== Revisions Deadline ==== ==== Final Deadline ==== | Not Handled |
| 9.7.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | Docs:=19 | - | |
| 9.7.2 | S2-2208171 | DRAFTCR | Approval | Interworking with TSN network deployed in the transport network | NTT DOCOMO | Rel-18 | Postponed | Jari (NTT DOCOMO) provides r01 ==== Revisions Deadline ==== zhendong (ZTE) proposes to postpone ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208558 | CR | Approval | 23.502 CR3574 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2209882, merging S2-2208794 | György (Ericsson) comments. Mirko (Huawei) provides r01. Devaki (Nokia) comments. Yuan Tao (CATT) comments. Mirko (Huawei) responds. ==== Revisions Deadline ==== ==== Final Deadline ==== | Revised |
| 9.7.2 | S2-2209882 | CR | Approval | 23.502 CR3574R1 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2208558r01, merging S2-2208794. Approved | Agreed | |
| 9.7.2 | S2-2208559 | CR | Approval | 23.503 CR0749 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2209883 | ==== Revisions Deadline ==== Devaki (Nokia) comments that this CR should be unapproved as it was merged with 8795r02 (which must be approved). Sorry, we forgot to mention in this thread earlier. ==== Final Deadline ==== | Merged |
| 9.7.2 | S2-2208560 | DRAFTCR | Information | TSN support in TN | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208561 | DRAFTCR | Information | RAN_BATFeedback_For_ AF_Adaptation | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208792 | CR | Approval | 23.501 CR3732 (Rel-18, 'B'): Exposure time synchronization services for requested coverage area | CATT | Rel-18 | Postponed | Jari (NTT DOCOMO) comments Yuan Tao (CATT) provides r01. zhendong (ZTE) proposes to postpone Sebastian (Qualcomm) objects to the CR (conclusions are not table yet) Yuan Tao (CATT) is ok to postpone the CR as offline discussion ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208793 | CR | Approval | 23.502 CR3581 (Rel-18, 'B'): Exposure time synchronization services for requested coverage area | CATT | Rel-18 | Postponed | zhendong (ZTE) proposes to postpone Sebastian (Qualcomm) objects to the CR (conclusions are not table yet) Yuan Tao (CATT) is ok to postpone the CR as offline discussion ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208794 | CR | Approval | 23.502 CR3582 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS | CATT | Rel-18 | Merged into S2-2209882 | Yuan Tao (CATT) confirms this paper is merged into 2208558. ==== Revisions Deadline ==== ==== Final Deadline ==== | Merged |
| 9.7.2 | S2-2208795 | CR | Approval | 23.503 CR0754 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS | CATT | Rel-18 | r02 agreed. Revised to S2-2209883, merging S2-2208559 | Yuan Tao (CATT) provides r01, which merges with 2208559. Devaki (Nokia) comments that r01 is not accessible (seems to have been uploaded to a wrong revisions folder - DRAFT/REVISIONS. Yuan Tao (CATT) updates link for r01. Mirko (Huawei) provides r02. ==== Revisions Deadline ==== Yuan Tao (CATT) is ok with r02. ==== Final Deadline ==== | Revised |
| 9.7.2 | S2-2209883 | CR | Approval | 23.503 CR0754R1 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS | CATT, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2208795r02, merging S2-2208559. Approved | Agreed | |
| 9.7.2 | S2-2208861 | CR | Approval | 23.501 CR3734 (Rel-18, 'B'): RAN feedback for burst sending time adjustment | Huawei, HiSilicon | Rel-18 | Postponed | zhendong (ZTE) proposes to postpone Sebastian (Qualcomm) objects to the CR (conclusions are not stable yet) ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208862 | CR | Approval | 23.503 CR0755 (Rel-18, 'B'): Pro-active RAN feedback for burst sending time adjustment | Huawei, HiSilicon | Rel-18 | Postponed | zhendong (ZTE) proposes to postpone Sebastian (Qualcomm) objects to the CR (conclusions are not stable yet) ==== Revisions Deadline ==== ==== Final Deadline ==== | Postponed |
| 9.7.2 | S2-2208863 | CR | Approval | 23.502 CR3584 (Rel-18, 'B'): CR 23.502 RAN feedback for adaption | Huawei, HiSilicon | Rel-18 | Postponed | Haiyang (Huawei) proposes to p |