Chairman's notes

 

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:

  • to investigate whether their organization or any other organization owns IPRs which are, or are likely to become Essential in respect of the work of 3GPP.
  • to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms".

 

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."

 

 

List for Meeting: All Sessions
Temporary Documents List - Ordered by Agenda Item
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-2205392 AGENDA Approval SA WG2 #152E Meeting Agenda SA WG2 Chair Approved Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
3 - - - SA2#152E Meeting report - - Docs:=1 -
3 S2-2205393 REPORT Approval Auto-Generated Report of SA WG2 meeting #151E SA WG2 Secretary Approved Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=35 -
4.1 S2-2205453 LS In Information LS from BBF: Response to SP-220347: Alignment concerning 5G-RG requirements and its remote management BBF (LIAISE-531) - Noted Noted
4.1 S2-2205492 DISCUSSION Information Notes from Call on inter-PLMN VoLTE handover for interested delegates of SA WG3-LI, SA WG3, SA WG2, CT WG1 held on Thursday 7/7/22 Vodafone Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
4.1 S2-2205493 DISCUSSION Approval Proposed Way Forward on VoLTE LI for inter-PLMN handover and idle mode mobility Vodafone Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
4.1 S2-2205400 LS In Action LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions SA WG3-LI (S3i220244) Rel-17 Revision of postponed S2-2203662 from S2#151E. Response drafted in S2-2208090. CC#3: Final response in S2-2207697 Replied to
4.1 S2-2208090 LS OUT Approval [DRAFT] Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions Ericsson Created at CC#2. Response to S2-2205400. CC#3: r01 agreed. Revised to S2-2207697. Shabnam (Ericsson) uploaded in the Revisions folder.
Rainer (Nokia) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Shabnam (Ericsson) repost the link, seems the upload did not work.
Chris (Vodafone) provides r01
Rainer (Nokia) is ok with 8090.
Shabnam (Ericsson) thanks, looks good. Maybe we can see if we can approve in CC#3
Revised
4.1 S2-2207697 LS OUT Approval Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions Ericsson - CC#3: Revision of S2-2208090r01. This LS OUT was approved Approved
4.1 S2-2205401 LS In Information LS from SA WG4: Reply LS to CT WG3 on Data Reporting API SA WG4 (S4-220839) Rel-17 Revision of postponed S2-2203666 from S2#151E. Noted Noted
4.1 S2-2205404 LS In Action LS from CT WG1: Reply LS on EPS fallback enhancements CT WG1 (C1-223535) Rel-17 Noted Wanqiang (Huawei) comments that the LS can be noted as SA2 already gave the feedback to RAN2.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205412 LS In Information LS from CT WG3: Reply LS on Data Reporting API CT WG3 (C3-223571) Rel-17 Noted Noted
4.1 S2-2205418 LS In Action LS from TSG CT: LS on Priority given to Rel-17 LSs from CT TSG CT (CP-221319) Rel-17 Noted Noted
4.1 S2-2205429 LS In Action LS from RAN WG3: Response LS on NAS PDU delivery during PDU Session modification procedure RAN WG3 (R3-223929) Rel-16 Noted Noted
4.1 S2-2205430 LS In Information LS from RAN WG3: Reply LS on open issues for NB-IoT and eMTC support for NTN RAN WG3 (R3-224007) Rel-17 Noted Hannu (Nokia): proposes to note the LS where RAN3 informs RAN2 and SA2 that they agree with SA2 decision. There is no action for SA2.
Steve (Huawei) can be noted.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205436 LS In Information LS from SA WG3: Reply LS on EPS fallback enhancements SA WG3 (S3-221162) Rel-17 Noted Wanqiang (Huawei) proposes to note the LS as SA2 already gave the feedback to RAN2.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205439 LS In Information LS from SA WG3: LS on PLMN ID used in Roaming Scenarios SA WG3 (S3-221214) Rel-17 Response drafted in S2-2205666. Final response in S2-2207391 Replied to
4.1 S2-2205666 LS OUT Approval [DRAFT] Reply LS on PLMN ID used in Roaming Scenarios Ericsson Rel-17 Response to S2-2205439. r06 agreed. Revised to S2-2207391. Laurent (Nokia): provides r01
Fenqin (Huawei) comments
Josep (DT) also supports considering SA3 as the most suitable group. Provides r02
Laurent (Nokia): provides r03
Josep (DT) replies to Laurent (Nokia).
Qian (Ericsson) comments and asks questions.
Fenqin (Huawei) comments and provides r04.
Josep (DT) disagrees with delegating to CT4.
Fenqin (Huawei) provides feedback to Josep(DT)
Josep (DT) comments, provides r06, please disregard r05 (I misssed one change).
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Fenqin (Huawei) we are also fine with r06.
Qian (Ericsson) is ok with r06.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
4.1 S2-2207391 LS OUT Approval [DRAFT] Reply LS on PLMN ID used in Roaming Scenarios Ericsson Rel-17 Revision of S2-2205666r06. Approved Approved
4.1 S2-2205442 LS In Information LS from SA WG3: LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN SA WG3 (S3-221268) Rel-17 Noted Hannu (Nokia): proposes to note the LS where the action is assigned on RAN2 and SA2 is only CC'd for information.
Steve (Huawei) can be noted.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205444 LS In Information LS from SA WG5: LS Reply on network slice LCM consumption and use case SA WG5 (S5-223521) Rel-18 Noted Peter Hedman (Ericsson) proposes to note the LS Noted
4.1 S2-2205459 LS In Information LS from GSMA NRG: LS to 3GPP Hosted SEPP GSMA NRG (5GMRR#37 Doc 11) Noted Peter Hedman (Ericsson) proposes to note the LS
Laurent (Nokia): supports that SA3 takes the lead and as the LS is targeted to SA3 we can note it
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205462 LS In Information LS from ITU-T SG13: LS on the consent of Recommendation ITU-T Y.3181 (ex-Y.ML-IMT2020-sandbox): 'Architectural framework for Machine Learning Sandbox in future networks including IMT-2020' ITU-T SG13 (SG13-LS6) Noted Noted
4.1 S2-2205465 LS In Information LS from RAN WG3: Reply LS on PEI and UE Subgrouping RAN WG3 (R3-224004) Rel-17 Noted Steve (Huawei) can be noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
4.1 S2-2205554 CR Approval 23.401 CR3702 (Rel-17, 'F'): Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming Vodafone Rel-17 Postponed Judy (Ericsson) comments
Haris(Qualcomm) comments and suggests alternative
Leo (Deutsche Telekom) comments
Chris (Vodafone) replies and notes that the 'IMS roaming agreement concept' seems to relate to LBO and NOT to S8HR.
Rainer (Nokia) asks for clarification.
Chris (Vodafone) replies to Nokia.
Rainer (Nokia) replies.
Leo (Deutsche Telekom) comments on proposed solution.
Chris (Vodafone) replies.
Rainer (Nokia) provides clarification.
Haris(Qualcomm) cannot agree on the CR
Chris (Vodafone) answers Nokia.
Chris (Vodafone) is OK to postpone this CR.
Leo (Deutsche Telekom) is also OK to postpone this CR, let's wait for feedback from CT3 and CT4.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Rainer (Nokia) is also ok to postpone the CR and have more discussions in future.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
4.1 S2-2205779 LS OUT Approval [DRAFT] Reply LS on access to multiple IMS networks via a 5GC network slice China Mobile Rel-18 Response to S2-2200042 (Replied to at S2#149E). Noted George Foti (Ericsson) provides comments
Rainer (Nokia) objects to the LS.
Haris(Qualcomm) objects to the LS
Yi (China Mobile) replies.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
4.1 S2-2205903 DISCUSSION Endorsement Cross border mobility related to IMS calls and LI for home routed IMS Ericsson, AT&T Rel-18 Noted Leo (Deutsche Telekom) comments
Rainer (Nokia) comments.
Chris (Vodafone) supports this approach - but the solution should also cover media encryption.
Ashok (Samsung) comments.
Magnus H (Ericsson) provides comment
Antoine (Orange) provides r01 with changes and comments, in particular trying to generalize to any IMS session, not just voice.
Shabnam (Ericsson) proposes some scoping for Rel-18 work and then we need to follow up.
Chris (Vodafone) replies
Rainer (Nokia) agrees with this proposal.
Chris (Vodafone) comments and suggests we need an outgoing LS describing the way forward.
Shabnam (Ericsson) Thanks everyone, let's bring up at CC#2 about the outgoing LS and I can draft something after revision deadline today and share, if we have agreement to send the response aligned with below, then we can do so.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Shabnam (Ericsson) responds to Samsung that if there are no deployment requirements from GSMA to comply with Media encryption then we do not see the need to try and address this issue unilaterally.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
4.1 S2-2205927 CR Approval 23.502 CR3519 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon Rel-17 Postponed Judy (Ericsson) comments
Haris(Qualcomm) asks question for clarification
Chris (Vodafone) asks whether the CR is solving the most likely problem e.g. for GBR flows.
Mirko (Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
4.1 S2-2206379 CR Approval 23.502 CR3536 (Rel-17, 'A'): Clarification on NAS PDU delivery during PDU Session modification Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2207392. LiMeng (Huawei): provides r01.
LiMeng (Huawei): provides r02.
LiMeng (Huawei): provides r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
4.1 S2-2207392 CR Approval 23.502 CR3536R1 (Rel-17, 'A'): Clarification on NAS PDU delivery during PDU Session modification Huawei, HiSilicon Rel-17 Revision of S2-2206379r03. Approved Agreed
4.1 S2-2206380 CR Approval 23.502 CR3537 (Rel-16, 'F'): Clarification on NAS PDU delivery during PDU Session modification Huawei, HiSilicon Rel-16 r04 agreed. Revised to S2-2207393. Hannu (Nokia): proposes revision r01 to improve the wording.
LiMeng (Huawei) is fine for r01.
Stefan (Ericsson) provides r02
LiMeng (Huawei) is fine with r02.
Hannu (Nokia) can live with r02 but asks whether the first deletion takes out too much text?
Hannu (Nokia) can live with r02 and corrects his previous comment due to typo that changed the meaning.
Stefan (Ericsson) replies to Hannu
LiMeng (Huawei) further replies.
LiMeng (Huawei) provides r03.
Stefan (Ericsson) provides r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Hannu (Nokia) supports r04.
Hannu (Nokia) thanks LiMeng and Stefan for addressing the comment on the wording. Supports r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
4.1 S2-2207393 CR Approval 23.502 CR3537R1 (Rel-16, 'F'): Clarification on NAS PDU delivery during PDU Session modification Huawei, HiSilicon Rel-16 Revision of S2-2206380r04. Approved Agreed
4.1 S2-2206389 DISCUSSION Approval Handling of GBR for EPS fallback service in home routed roaming Vivo Rel-17 Noted Chris (Vodafone) comments
Xiaobo (vivo) replies to comments from Chris (Vodafone)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
4.1 S2-2205458 LS In Action LS from SA WG6: LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network SA WG6 (S6-221953) Rel-18 Responses drafted in S2-2206599, S2-2206796, S2-2206900. Final response in S2-2207394 Replied to
4.1 S2-2206599 LS OUT Approval [DRAFT] Reply LS on supporting of NAT deployed within the edge data network China Mobile Rel-18 Response to S2-2205458. Merged into S2-2207394 Hyesung (Samsung) asks questions and comments.
Laurent (Nokia): proposes to use 6796 as a baseline for the answer to SA6.
Magnus (Ericsson) proposes to use 6900 as the base for the answer to SA6
Yan (China Mobile) replies.
Jinsook (DISH) we prefer 6599 as the baseline for the answer to SA6
Dario (Qualcomm) prefers 6900 with indication of further work needed.
Laurent (Nokia): objects to any version of 6599 (will also withdraw/merge his 6796) for the sake of having one thread in 6900 for the LS out
Yan (China Mobile) agrees to merge this 6599 into 6900 and continue to discuss under that thread.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
4.1 S2-2206796 LS OUT Approval [draft] LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2205458. Merged into S2-2207394 Laurent (Nokia): proposes to use 6796 as a baseline for the answer to SA6.
Magnus (Ericsson) proposes to use 6900 as the base for the answer to SA6
Dario (Qualcomm) is fine with 6800 w/ a generic indication that further work is needed.
Fenqin (Huawei) we are fine with 6900 with a generic response.
Laurent (Nokia): withdraws/merges his 6796 for the sake of having one thread in 6900 for the LS out
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
4.1 S2-2206900 LS OUT Approval [DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge Intel Rel-18 r15 agreed. Revised to S2-2207394, merging S2-2206599 and S2-2206796. Laurent (Nokia): proposes to use 6796 as a baseline for the answer to SA6.
Magnus (Ericsson) proposes to use 6900 as the base for the answer to SA6
Saso (Intel) provides r01.
Dario (Qualcomm) proposes r02
Yan (China Mobile) provides r03.
Hyesung (Samsung) comments.
Laurent (Nokia): provides r04
Yan (China Mobile) provides r05.
Magnus O (Ericsson) provides r06
Saso 5intel) provides r07 on top of r06 provides r06
Yan (China Mobile) comments.
Saso (Intel) replies to Yan.
Dario (Qualcomm) comments.
Jinsook (DISH) Comment and suggestion
Dario (Qualcomm) asks question for clarification on usage of DNN/S-NSSAI and provides r08.
Laurent (Nokia): answers
Laurent (Nokia): provides r08
Fenqin (Huawei) provides comment
Laurent (Nokia): provides r09 (R08 was from QC)
Saso (Intel) provides r10
Yan (China Mobile) provides r11.
Fenqin (Huawei) provides r12
Saso (Intel) provides r13.
Jinsook (DISH) provides r14.
Saso (Intel) is OK with r14.
Dan(China Mobile) provides r15 with taking the ipdomain back and object to r13 and r14
Laurent (Nokia): provides r16
Dan (China Mobile) ask
Fenqin (Huawei): provides r17/r18
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Dario (Qualcomm) can live with r17.
Saso (Intel) prefers r16 and r15, can live with r18, r17.
Fenqin (Huawei) Prefer r17 or r18
Fenqin (Huawei) R17/R18 are uploaded to server before revision deadline. We suggest to go with R17
Yan (China Mobile) can live with r17.
Magnus (Ericsson) prefers r16 can live with r15, r17 and r18.
Saso (Intel) seeks clarification from Fenqin; explains why r16 or r15 are more appropriate.
Fenqin (Huawei) provides response
Saso (Intel) seeks clarification from Fenqin.
Fenqin (Huawei) provides response to Saso.
Laurent (Nokia): MUCH prefers R16; there seems to be majority for this version
Fenqin (Huawei): still suggest to go with r17 as operator also think that the related information shall not be exposed outside.
Saso (Intel) replies to Fenqin.
Fenqin (Huawei) we also see some feedback from operator to say that they do not want to expose this information.
Saso (Intel) replies to Fenqin that SA2 needs to be factual in the reply LS; conveying the additional information in r17/r18 is not factual as it does not correspond to any restriction in the specification. So, let's move with r16 (preferably) or r15.
Yan (China Mobile) objects to r16/r18 and suggests to go with r15.
Dario (Qualcomm) is not OK with r16 and still prefers r17.
Fenqin (Huawei) we are ok with R15/R17 and object other revision
Jinsook (DISH) We prefer r15 !
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Saso (Intel) replies to Dario.
Revised
4.1 S2-2207394 LS OUT Approval Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge SA WG2 Rel-18 Revision of S2-2206900r15, merging S2-2206599 and S2-2206796. Approved Approved
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:=8 -
5.1 S2-2205661 CR Approval 23.401 CR3703 (Rel-17, 'F'): Provision with Pscell Information Ericsson Rel-17 r04 agreed. Revised to S2-2206988. Wanqiang (Huawei) comments the CR.
Qian (Ericsson) replies to Wanqiang (Huawei).
Hannu (Nokia) comments that we should not add new Rel-17 requirements any longer.
Qian (Ericsson) replies to Hannu (Nokia) and considers it's SA2 responsibility to provide guidance on the inconsistency among stage 3 groups.
Haris(Qualcomm) supports the CR and provides r01
Chris (Vodafone) comments that the PSCell info should be included whenever it helps enhance the CN's location information.
Wanqiang (Huawei) comments that we should not add new thing for R17.
Qian (Ericsson) provides further comments.
Qian (Ericsson) provides comments.
Wanqiang (Huawei) provides further comments.
Qian (Ericsson) provides responses.
Qian (Ericsson) provides r02.
Tyler (OTD) supports the CR and prefers r02.
Hannu (Nokia) comments and shares r03.
Wanqiang (Huawei) provides r04.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Qian (Ericsson) prefers r01, but can live with r04.
Hannu (Nokia) proposes to agree r04.
Wanqiang (Huawei) can only live with r04.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
5.1 S2-2206988 CR Approval 23.401 CR3703R1 (Rel-17, 'F'): Provision with Pscell Information Ericsson Rel-17 Revision of S2-2205661r04. Approved Agreed
5.1 S2-2205748 CR Approval 23.401 CR3704 (Rel-15, 'F'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-15 CC#3: r01 + changes agreed. Revised to S2-2206989. Chris (Vodafone) says that the CR goes too far, and provides a rev 1.
Haris(Qualcomm) comments on r01
Chris (Vodafone) answer the Qualcomm comment
Haris(Qualcomm) proposes r02
alessio(Nokia) can live with r02
Qian (Ericsson) provides comments
Chris (Vodafone) thinks r01 is OK but r02 causes problems
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haris(Qualcomm) responds
Chris (Vodafone) responds
Haris(Qualcomm) comments that can accept r01 but still thinks the text is misleading
alessio(Nokia) proposes then to remove the text everyone agrees at this meeting, then come back with a more thought out text for the rest at next meeting. can Haris generate a revision for approval at CC#2 like this?
Haris(Qualcomm) indicates that the original text is in r01 without the additional text ', e.g. by not including any E-UTRA related radio capability information'
Alessio(Nokia) thanks Haris(Qualcomm) and wonders then what is the value of the 'e.g.' and would suggest to remove it and maybe think about the right approach for next meeting on this paragraph.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Haris(Qualcomm) indicates that the correct disposition is to agree r01 without this text: , e.g. by not including any E-UTRA related radio capability information' and proposes to discuss in CC#3
Alessio(Nokia) agrees with Haris(Qualcomm) who indicates that the correct disposition is to agree r01 without this text: , e.g. by not including any E-UTRA related radio capability information' and proposes to discuss in CC#3
Revised
5.1 S2-2206989 CR Approval 23.401 CR3704R1 (Rel-15, 'F'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-15 CC#3: Revision of S2-2205748r01 + changes. Approved Agreed
5.1 S2-2205749 CR Approval 23.401 CR3705 (Rel-16, 'A'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-16 Revised to S2-2206990. Chris (Vodafone) says this is a mirror CR - we should wait for the outcome on 5748.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
5.1 S2-2206990 CR Approval 23.401 CR3705R1 (Rel-16, 'A'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-16 Revision of S2-2205749. Approved Agreed
5.1 S2-2205750 CR Approval 23.401 CR3706 (Rel-17, 'A'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-17 Revised to S2-2206991. Chris (Vodafone) says this is a mirror CR - we should wait for the outcome on 5748.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
5.1 S2-2206991 CR Approval 23.401 CR3706R1 (Rel-17, 'A'): Removal of misaligned text with stage-3 Qualcomm Incorporated Rel-17 Revision of S2-2205750. Approved Agreed
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:=6 -
6.1 S2-2205508 CR Approval 23.501 CR3661 (Rel-17, 'F'): Correction on Reference Architecture NTT Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
6.1 S2-2205509 CR Approval 23.501 CR3662 (Rel-18, 'A'): Correction on Reference Architecture NTT Rel-18 Approved. CC#3: Noted Fenqin (Huawei) suggest to note this paper
Chris (Vodafone) agrees with Huawei's logic and suggests to note this CR
Kazuki (NTT) accepts the suggestion (note this CR).
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Shabnam (Ericsson) there is no Rel-18 spec and as commented and agreed the CR needs to be NOTED and not APPROVED.
Noted
6.1 S2-2205700 CR Approval 23.501 CR3583R2 (Rel-17, 'F'): Clarification on Mapped NSSAI Huawei, HiSilicon Rel-17 Revision of (TSG SA noted) S2-2202047 from S2#150E. CC#3: Postponed Dongeun (Samsung) comments
Peter Hedman (Ericsson) provides comments and suggests with aligning with stage 3 i.e. to use 05753 as basis.
Haris(Qualcomm) objects to the CR
Haiyang (Huawei) responds to Haris(Qualcomm), Peter(Ericsson) and Dongeun (Samsung), and disagrees with Haris(Qualcomm)'s statement
Guillaume (MediaTek Inc.) objects to this CR.
Haiyang (Huawei) provides r01 to remove the roaming related description.
Haiyang (Huawei) provides r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments, status 'mirror' is not correct and propose to either note the CR or that additional change is done to r02
Haiyang (Huawei) provides r03: which is r02 + removing 'if the mapping information is provided to the UE'.
Haris(Qualcomm) suggests to move forward with S2-2205753
Haiyang (Huawei) clarifies that r02/r03 have removed all the changes related to 5753
Haiyang (Huawei) prefers to go with r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
6.1 S2-2205751 CR Approval 23.501 CR3671 (Rel-15, 'F'): Mapped NSSAI alignment with stage-3 Qualcomm Incorporated, MediaTek Inc. Rel-15 CC#3: Postponed Peter Hedman (Ericsson) supports the way forward
Haiyang (Huawei) suggests to note this paper
Haris(Qualcomm) responds
Haiyang (Huawei) comments
Guillaume (MediaTek Inc.) comments and recommends approving the CR (and mirrors in 5752, 5753).
Haris(Qualcomm) comments
Krisztian (Apple) provides r01 to co-sign and suggests to approve this CR along with 5752, 5753.
Haiyang (Huawei) suggests a way forward
Peter Hedman (Ericsson) provides r02
Haris(Qualcomm) indicates why it is important to align rel.15
Guillaume (MediaTek Inc.) agrees with Haris (Qualcomm)
Haiyang (Huawei) provides feedback
Haiyang (Huawei) provides r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) can only accept r03
Alessio(Nokia) can only accept r03 if the Shall that Ericsson has introduced is returned to the current MAY. would object to r03 as is.
Haris(Qualcomm) indicates that r03 can be accepted if this text: 'Due to stage 3 misimplementation of the stage 2 functionality, the support of mapping S-NSSAIs in HPLMN has to be removed from the stage 2 specification.' is removed
Guillaume (MediaTek Inc.) would also support updating the coversheet in r03
Alessio(Nokia) comments since we have to stick to the issue of alignment to stage 3:, we ask any change of the roaming case has to be linked to corresponding CT1 text. we do not change our stage 2 unless there is a FASMO or a misalignment.
Peter Hedman (Ericsson) provides reply that we need a consistent logic for when mapping is sent also considering the feedback from CT1
Alessio(Nokia) insofar as the UE can handle the no mapping the aMF will not send it as implied since rel-15... and of course if indeed there is no need of mapping. my understanding is the AMF shall always send the mapping when one exists. but why are we having all these rel-15 discussions now?
Antoine (Orange) makes a suggestion.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Alessio(Nokia) comments that we should not change rel-15 unless we find a FASMO or stage 3 since rel-15 did something else
alessio(Nokia) even if we state it is mandatory to provide a mapping if the value is the same technically this is not a mapping. So from SA2 perspective the text is fine. if in cT1 they want to include always a IE even if empty or populated with same value it is not our business. too bad they do this now for rel-15 and in THEORY rel-15 implementations should be already there in the field and CHECK the presence of the IE as indicated (by definition of mandatory). A IE is NOT mandatory in 3GPP if the UE can ignore its absence.
Haris(Qualcomm) makes a suggestion
Alessio (nokia) provides text he can agree with.
Guillaume (MediaTek Inc.) responds and agrees with Peter (Ericsson).
alessio(Nokia) maintains the roaming case is not ins cope of this CR.
Guillaume (MediaTek Inc.) comments.
alessio (nokia) does not believe the stage two was uncertain for the roaming case at least... there was a MAY and not people to adapt to the thing you want it is changed to SHALL so I assume that we have a different standard but the first was as clear as the second, only different.
Postponed
6.1 S2-2205752 CR Approval 23.501 CR3672 (Rel-16, 'A'): Mapped NSSAI alignment with stage-3 Qualcomm Incorporated, MediaTek Inc. Rel-16 CC#3: Postponed Haiyang (Huawei) suggests to note this paper
Guillaume (MediaTek Inc.) recommends approving this CR alongside 5751 and 5753.
Krisztian (Apple) provides r01.
Peter Hedman (Ericsson) provides r02
Haiyang (Huawei) provides r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) can only accept r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
6.1 S2-2205753 CR Approval 23.501 CR3673 (Rel-17, 'A'): Mapped NSSAI alignment with stage-3 Qualcomm Incorporated, MediaTek Inc. Rel-17 CC#3: Postponed Haiyang (Huawei) suggests to note this paper
Guillaume (MediaTek Inc.) recommends approving this CR alongside 5751 and 5752.
Krisztian (Apple) provides r02.
Haiyang (Huawei) provides r01
Haiyang (Huawei) comments and objects r02
Peter Hedman (Ericsson) provides r03
Peter Hedman (Ericsson) provides reply
Haiyang (Huawei) clarifies comments
Alessio(Nokia) provides comments and support the Qualcomm et al approach despite with mixed feelings
Peter Hedman (Ericsson) provides reply and ok with proposal to update CR cover sheet, but asks if ok for others supporting the CR
Haiyang(Huawei) supports Alessio(Nokia) on the LS to CT1, provides r04 accordingly
Haris(Qualcomm) proposes r05
Haiyang(Huawei) provides reply
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang(Huawei) can only accept r04 or r05
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
6.2 - - - Common Access Control, RM and CM functions and procedure flows - - Docs:=7 -
6.2 S2-2205600 CR Approval 23.502 CR3504 (Rel-17, 'F'): Correction to PLMN ID used in Nudm services Ericsson Rel-17 r00 agreed. Revised to S2-2206992. LiMeng (Huawei) questions
Judy (Ericsson) responds to LiMeng (Huawei)
Hannu (Nokia) asks whether the approval of this CR would cause any CT4 action?
Judy (Ericsson) responds to Hannu (Nokia)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.2 S2-2206992 CR Approval 23.502 CR3504R1 (Rel-17, 'F'): Correction to PLMN ID used in Nudm services Ericsson Rel-17 Revision of S2-2205600r00. Approved Agreed
6.2 S2-2206570 DISCUSSION Agreement Discussion on Home eNB ID as target for 5GS to EPS HO Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, NEC, Verizon Rel-17 Noted LiMeng (Huawei) comments
Guillaume (MediaTek Inc.) proposes to note this discussion paper
Hannu (Nokia) agrees to note the discussion paper but points out that the supporting companies see that inter-system HO from 5GS to EPS is broken.
Hugh(AT&T) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.2 S2-2206571 CR Approval 23.401 CR3711 (Rel-17, 'F'): Inter-system handover to Home eNB Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, NEC, Verizon Rel-17 Noted Guillaume (MediaTek Inc.) questions this being FASMO.
Qian (Ericsson) provides comments.
Hannu (Nokia) comments that S2-2206571 and S2-2206572 were submitted to clarify that HeNB is (implicitly) part of E-UTRAN already.
Haris(Qualcomm) comments and proposes to note the CRs
Chris (Vodafone) supports noting the 23.401 CR. If we need any CR it should be possible to just do a 23.501 CR.
Hannu (Nokia) can accept noting this 23.401 CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.2 S2-2206572 CR Approval 23.501 CR3691 (Rel-17, 'F'): Inter-system handover to Home eNB Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, NEC, Verizon Rel-17 Confirm Specification Number - CR states 23.502! Noted Guillaume (MediaTek Inc.) questions this being FASMO.
Qian (Ericsson) provides comments.
Hannu (Nokia) comments that S2-2206571 and S2-2206572 were submitted to clarify that HeNB is (implicitly) part of E-UTRAN already.
Haris(Qualcomm) comments and proposes to note the CRs
Chris (Vodafone) is OK to just do LS. Also OK to agree 6572r01 and note 6571.
Hugh (AT&T) is OK to just do LS. Also OK to agree 6572r01 and note 6571.
Hannu (Nokia) supports r01. Proposes to note S2-2206571 (EPS CR), agree S2-2206572 (5GS CR) and the related LS in S2-2206573.
Qian (Ericsson) proposes to NOTE the CR and continue the discussion on LS sending.
Haris(Qualcomm) is not satisfied by r01
Hannu (Nokia) comments to Haris and proposes to go ahead with r01 or show better wording in revision of the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Qian (Ericsson) comments that there seems no need to add any clarification in SA2 at this stage, thus object to any revision of the CR
Haris(Qualcomm) proposes to NOTE the CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.2 S2-2206573 LS OUT Approval [DRAFT] LS on Inter-system handover to Home eNB Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, NEC, Verizon Rel-17 CC#3: r05 agreed. Revised to S2-2207693. Guillaume (MediaTek Inc.) provides r01.
Hannu (Nokia) shares r02 to align with the revision r01 of the related CR.
Guillaume (MediaTek Inc.): ok with r02
Qian (Ericsson) comments and provides r03.
Chris (Vodafone) thinks that r02 gives clearer guidance to RAN 3.
Qian (Ericsson) provides comments and r05.
Hannu (Nokia) prefers r02 as the more clear version but offers r04 as possible compromise.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haris(Qualcomm) prefers r02
Qian (Ericsson) provides comments and says only R05 is acceptable at this moment.
Guillaume (MediaTek Inc.) recommends r02
Hannu (Nokia) proposes to approve r02, which is more accurate. r05 is only a fallback position if we can't agree that HeNB is part of EPS.
Qian (Ericsson) provides further comments and repeats that r05 is the only one that is acceptable and reflects the SA2 current specs (objects to other revisions at this stage).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.2 S2-2207693 LS OUT Approval LS on Inter-system handover to Home eNB Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, NEC, Verizon Rel-17 CC#3: Revision of S2-2206573r05. This LS OUT was approved Approved
6.3 - - - Session management and continuity functions and flows - - Docs:=0 -
6.4 - - - Security related functions and flows - - Docs:=0 -
6.5 - - - QoS concept and functionality - - Docs:=0 -
6.6 - - - Policy and charging control - - Docs:=8 -
6.6 S2-2205633 CR Approval 23.501 CR3663 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Check Affected Clauses! CC#3: Postponed Xinpeng(Huawei) comments.
Pallab (Nokia) has similar comments as raised by Huawei. Requests to clarify the need for such updates
Tugce (NTT DOCOMO) objects this CR and proposes to continue this discussion under R18 EDGE.
Magnus H (Ericsson) provides comment
Magnus H (Ericsson) provides r01
Magnus H (Ericsson) comments
Magnus H (Ericsson) comments and provides r03
Pallab (Nokia) comments and provides r02.
Tugce (NTT DOCOMO) finds r01 better and provides comments.
Pallab (Nokia) comments on r03.
Pallab (Nokia) cannot accept r03 and proposes to rephrase the text describing the technical limitation, instead of limiting it to 5G VN group.
Magnus H (Ericsson) comment and cannot accept r02 and provides r04
Xinpeng(Huawei) provides r05.
Pallab (Nokia) comments and provides r06.
Magnus H (Ericsson) provides r07
Pallab (Nokia) comments.
Pallab (Nokia) responds.
Xinpeng(Huawei) replies.
Pallab (Nokia) provides r08.
Magnus H (Ericsson) provides r09 and comments
Xinpeng(Huawei) provides r10.
Tugce (NTT DOCOMO) provides r11.
Pallab (Nokia) provides r12 based on r10. Objects to r11
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Xinpeng(Huawei) only accept r10, and objects to any other revisions.
Pallab (Nokia) can accept r10, r12. Objects to other revisions. Highlights that in r10 a minor editorial correction is needed.
Tugce (NTT DOCOMO) can accept r01 (with minor editorial correction at Note numbering) and objects to other revisions.
Magnus H (Ericsson) comments and ask if people can accept r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
6.6 S2-2205634 CR Approval 23.502 CR3505 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Noted Xinpeng(Huawei) comments.
Pallab (Nokia) has similar comments as raised by Huawei. Requests to clarify the need for such updates
Tugce (NTT DOCOMO) objects this CR and proposes to continue this discussion under R18 EDGE.
Magnus H (Ericsson) withdraws this contribution
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.6 S2-2205635 CR Approval 23.503 CR0732 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 CC#3: Postponed Xinpeng(Huawei) comments.
Pallab (Nokia) comments.
Tugce (NTT DOCOMO) objects this CR and proposes to continue this discussion under R18 EDGE.
Magnus H (Ericsson) provides r01
Tugce (NTT DOCOMO) finds r01 better and provides comments.
Magnus H (Ericsson) provides r02
Magnus H (Ericsson) provides r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Xinpeng(Huawei): the outcome of 5635 will depend on the outcome of S2-2205633.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
6.6 S2-2206027 CR Approval 23.502 CR3523 (Rel-16, 'F'): Same PCF selection for PDU sessions with the same DNN/S-NSSAI Samsung Rel-16 Noted Susan (Huawei) objects to this CR.
Pallab (Nokia) also objects to the CR.
Josep (DT) comments, provides r01.
Jinguo(ZTE) agree with Susan and provide further information
Belen (Ericsson) also thinks that this CR is not needed.
Dongeun (Samsung) is ok to note the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.6 S2-2206029 CR Approval 23.502 CR3524 (Rel-17, 'A'): Same PCF selection for PDU sessions with the same DNN/S-NSSAI Samsung Rel-17 Noted Susan (Huawei) objects to this CR.
Pallab (Nokia) also objects to the CR. Same comment as in 6027
Dongeun (Samsung) is ok to note the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.6 S2-2206046 CR Approval 23.503 CR0697R2 (Rel-17, 'F'): Clarification of PCF input parameter AF application identifier Huawei, HiSilicon Rel-17 Revision of (Noted) S2-2204270 from S2#151E. r00 agreed. Revised to S2-2206993. Belen (Ericsson) provides comments
Mirko (Huawei) responds
Belen (Ericsson) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Belen (Ericsson) asks a question for clarification.
Belen (Ericsson) replies.
Belen (Ericsson) is okay with the initial revision
Mirko (Huawei) confirms that the original version can be approved.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.6 S2-2206993 CR Approval 23.503 CR0697R3 (Rel-17, 'F'): Clarification of PCF input parameter AF application identifier Huawei, HiSilicon Rel-17 Revision of S2-2206046r00. Approved Agreed
6.6 S2-2206240 CR Approval 23.503 CR0737 (Rel-17, 'F'): TS 23.503: Access and Mobility policy control subscription information Nokia, Nokia Shanghai Bell Rel-17 Noted Belen (Ericsson) provides objects to this CR, needs more discussion.
Belen (Ericsson) objects to this CR, needs more discussion.
Pallab (Nokia) OK to NOTE this and have further discussion
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.7 - - - 3GPP access specific functionality and flows - - Docs:=5 -
6.7 S2-2205662 CR Approval 23.501 CR3665 (Rel-17, 'F'): ULI provision with Pscell Information Ericsson Rel-17 r02 agreed. Revised to S2-2206994. Chris (Vodafone) suggests using the thread on 5661 to discuss this topic first.
Hannu (Nokia) agrees to move the main discussion to 5661 as suggested, but asks a related question on the NG-RAN reporting criteria that might differ slightly between EPS and 5GS?
Qian (Ericsson) responds
Qian (Ericsson) provides r01
Hannu (Nokia) provides r02 and comments.
Wanqiang (Huawei) comments.
Qian (Ericsson) provides comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Qian (Ericsson) comments and says it's ok to go with r02. For the synch between 23.501 and 23.502 can be addressed in next meeting.
Hannu (Nokia) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.7 S2-2206994 CR Approval 23.501 CR3665R1 (Rel-17, 'F'): ULI provision with Pscell Information Ericsson Rel-17 Revision of S2-2205662r02. Approved Agreed
6.7 S2-2205663 CR Approval 23.502 CR3507 (Rel-17, 'F'): UE Presence in AoI clarification Ericsson Rel-17 CC#3: r06 + changes agreed. Revised to S2-2207694. Haris(Qualcomm) asks questions
Qian (Ericsson) suspects that the comment/question from Hannu(Nokia) is for another paper 5662. ??
Hannu (Nokia) asks about the service requirement?
Qian (Ericsson) responds to Haris (Qualcomm)
Hannu (Nokia) withdraws his comment on 5663 and moves on to comment on 5662.
Chris (Vodafone) provides r01
Qian (Ericsson) provides comments
Chris (Vodafone) provides r02.
Qian (Ericsson) thanks for the r02 and provides further comments
Qian (Ericsson) provides comments again.
Qian (Ericsson) comments and provides r03.
Chris (Vodafone) replies.
Chris (Vodafone) prefers rev 2 to rev 3.
Qian (Ericsson) thanks for the comments and considers that r03 is more technically correct ??.
Fenqin (Huawei) ask a question for clarification
Hannu (Nokia) shares r04 and comments.
Fenqin (Huawei) give some suggestion.
Qian (Ericsson) responds further.
Fenqin (Huawei) provides comments.
Qian (Ericsson) responds.
Chris (Vodafone) provides r05 based on r02. R03 and r04 seem problematic.
Qian (Ericsson) comments and provide r06.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Qian (Ericsson) provides further comments.
Hannu (Nokia) prefers either r05 or r06 as r07 is less accurate on the Out of Area conditions.
Qian (Ericsson) comments that r06 (submitted before deadline) is preferred, but ok with r07 == on top of r06, remove all the changes under the 'otherwise' part.
Fenqin (Huawei) provides further comments and r07 and suggest bring this to CC#2.
Fenqin(Huawei) Provides response
Chris (Vodafone) prefers r05 to r06.
Qian (Ericsson) provides comments.
Fenqin (Huawei) provides comments and suggest to r06+ removing the otherwise case change.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.7 S2-2207694 CR Approval 23.502 CR3507R1 (Rel-17, 'F'): UE Presence in AoI clarification Ericsson Rel-17 CC#3: Revision of S2-2205663r06 + changes. This CR was agreed Agreed
6.7 S2-2205728 CR Approval 23.502 CR3511 (Rel-17, 'F'): Correnction to the description on step 5c of clause 4.23.7.3.2 OPPO Rel-17 Merged into S2-2207014 Fenqin (Huawei) suggest to merge to 6522 or 5484.
Yang (OPPO) agrees to merge 5728 into 5484.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
6.8 - - - Specific services support - - Docs:=2 -
6.8 S2-2205491 CR Approval 23.501 CR3659 (Rel-17, 'F'): Handling of PDU Sessions for Emergency services Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2206995. zhendong (ZTE) comments
Fenqin (Huawei) provides comments.
George Foti (Ericsson) provides comments. Please convert this to a note. This is not a Fasmo
Guillaume (MediaTek Inc.) comments: this is not FASMO, but seems to be Cat C.
Hannu (Nokia) replies to feedback and shares r01 seeking clarification on the intended UE and SMF behaviour?
Fei (OPPO) supports the option 1.
Krisztian (Apple) provides comments.
Guillaume (MediaTek) comments
Shabnam (Ericsson) comments as confirmed by stage 3 spec, question is if one statement on the overall description can be acceptable for Rel-17 and then we can follow up to see if the detailed updates are needed further in Rel-18? Comments
Hannu (Nokia) seeks the agreement on the principle shown by Guillaume in preparation for the next revision.
Hannu (Nokia) proposes r02 with systematic removal of all text on multiple emergency PDU sessions.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Leo (Deutsche Telekom) supports r02, objects r00 and r01
Guillaume (MediaTek Inc.) supports r02
Krisztian (Apple) supports r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.8 S2-2206995 CR Approval 23.501 CR3659R1 (Rel-17, 'F'): Handling of PDU Sessions for Emergency services Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2205491r02. Approved Agreed
6.9 - - - Interworking and Migration - - Docs:=3 -
6.9 S2-2205598 CR Approval 23.502 CR3472R1 (Rel-16, 'F'): EPS to 5GS mobility with V-SMF insertion and PDU Sessions to be activated Ericsson Rel-16 Revision (Postponed) of S2-2203847 from S2#151E. Noted zhendong (ZTE) provides the comment
Fenqin (Huawei) comments
Judy (Ericsson) responds to Fenqin (Huawei) and believes correction to the missing EPS to 5GS mobility scenario is needed
Judy (Ericsson) provides r01 and responds to zhendong (ZTE) and Fenqin (Huawei)
Fenqin (Huawei) provides comment
Thomas(Nokia) provides comment
Judy (Ericsson) responds to Thomas(Nokia) and Fenqin (Huawei)
Fenqin (Huawei) propose to note this paper.
Thomas(Nokia) responds to Judy (Ericsson)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Judy (Ericsson) comments that this CR is to have a consistent handling of List of PDU Sessions To Be Activated in different mobility scenarios and ask Fenqin (Huawei) to reconsider his position.
Fenqin (Huawei) still propose to note this paper.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
6.9 S2-2205599 CR Approval 23.502 CR3473R1 (Rel-17, 'A'): EPS to 5GS mobility with V-SMF insertion and PDU Sessions to be activated Ericsson Rel-17 Revision (Postponed) of S2-2203848 from S2#151E. r01 agreed. CC#3: This CR was agreed Judy (Ericsson) responds to Fenqin (Huawei) and believes correction to the missing EPS to 5GS mobility scenario is needed
Fenqin (Huawei) comments
Judy (Ericsson) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
6.9 S2-2206996 CR Approval 23.502 CR3473R2 (Rel-17, 'A'): EPS to 5GS mobility with V-SMF insertion and PDU Sessions to be activated Ericsson Rel-17 Revision of S2-2205599r01. Approved. CC#3: WITHDRAWN Withdrawn
6.10 - - - Non-3GPP access specific functionality and flows - - Docs:=0 -
6.11 - - - Framework functions - - Docs:=5 -
6.11 S2-2205769 CR Approval 23.501 CR3677 (Rel-17, 'F'): Missing UDSF timer service Intel Rel-17 r04 agreed. Revised to S2-2206997. Josep (DT) comments, provides r01.
Magnus H (Ericsson) provides r02
Saso (Intel) is OK with r02
Fenqin (Huawei) provides r03
Fenqin (Huawei) provides r04
Magnus H (Ericsson) disagrees with Fenqin's comment
Saso (Intel) is ok with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.11 S2-2206997 CR Approval 23.501 CR3677R1 (Rel-17, 'F'): Missing UDSF timer service Intel Rel-17 Revision of S2-2205769r04. Approved Agreed
6.11 S2-2205771 CR Approval 23.502 CR3515 (Rel-17, 'F'): Missing UDSF timer service Intel Rel-17 r06 agreed. Revised to S2-2206998. Josep (DT) comments, provides r01.
Magnus H (Ericsson) provides r02
Magnus H (Ericsson) comments
Josep (DT) comments that timer value is not mandatory for the update operation.
Magnus H (Ericsson) provides comment
Josep (DT) replies to Magnus H (Ericsson).
Saso (Intel) is OK with r02 in principle. Asks Magnus H for clarification.
Josep (DT) provides r03 moving the timer expiry to optional in update.
Magnus H (Ericsson) provides r04 and comments
Saso (Intel) provides r05
Fenqin (Huawei) provides r06
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
6.11 S2-2206998 CR Approval 23.502 CR3515R1 (Rel-17, 'F'): Missing UDSF timer service Intel Rel-17 Revision of S2-2205771r06. Approved Agreed
6.11 S2-2205949 CR Approval 23.502 CR3520 (Rel-17, 'F'): Provision of NRF to be used when Nnssf_NSSelection_Get service operation is involked during PDU Session Establishment procedure Orange Rel-17 Noted Uri (Oracle) provides comments.
Thomas (Nokia) raises concerns
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Thomas (Nokia) suggest noting this contribution
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
7 - - - Rel-16 Maintenance for 5G (excluding 5GS_Ph1) - - Docs:=0 -
7.1 - - - Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) - - Docs:=0 -
7.2 - - - Wireless and Wireline Convergence for the 5G system architecture (5WWC) - - Docs:=8 -
7.2 S2-2205438 LS In Action LS from SA WG3: LS on TNAP mobility security aspect SA WG3 (S3-221165) Rel-18 Responses drafted in S2-2205490, S2-2205861. Final response in S2-2206999 Replied to
7.2 S2-2205490 LS OUT Approval [DRAFT] LS on TNAP mobility security aspect Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2205438. Merged into S2-2206999 Marco (Huawei) propose to considered merged in S2-225861
Laurent (Nokia): agrees that S2-2205490 is merged in S2-225861
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
7.2 S2-2205861 LS OUT Approval [DRAFT] Reply LS on TNAP mobility security aspect Ericsson Rel-18 r04 agreed. Revised to S2-2206999, merging S2-2205490 Laurent (Nokia): Suggests to take 5861 (stefan's) as the basis and to merge in 5490 (mine)
Stefan (Ericsson) provides r01
Yishan (Huawei) asks for questions
Stefan (Ericsson) replies to Yishan
Marco (Huawei) comments to Stefan (Ericsson)
Stefan (Ericsson) replies to Marco
Marco (Huawei) replies to Stefan (Ericsson)
Yildirim (Charter) comments on the preference on the wording proposals.
Stefan (Ericsson) provides comments
Yildirim (Charter) further comments
Marco (Huawei) further comments
Stefan (Ericsson) provides r02
Sriram(CableLabs) comments
Laurent (Nokia): provides r04
Sriram(CableLabs) provides r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Laurent (Nokia): objects to R03.
Marco (Huawei) objects r03 & ok with r04.
Sriram(CableLabs) support r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.2 S2-2206999 LS OUT Approval [DRAFT] Reply LS on TNAP mobility security aspect Ericsson Rel-18 Revision of S2-2205861r04, merging S2-2205490. Approved Approved
7.2 S2-2206583 CR Approval 23.502 CR3542 (Rel-16, 'F'): Removal of EAP Re-authentication Ericsson Rel-16 r02 agreed. Revised to S2-2207000. Marco (Huawei) comment and provides r01
Myungjune (LGE) comment
Laurent (Nokia): provides r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Laurent (Nokia): objects to R01; happy with R02 (cosigned)
Stefan (Ericsson) OK with r02
Marco (Huawei) OK with r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.2 S2-2207000 CR Approval 23.502 CR3542R1 (Rel-16, 'F'): Removal of EAP Re-authentication Ericsson Rel-16 Revision of S2-2206583r02. Approved Agreed
7.2 S2-2206584 CR Approval 23.502 CR3543 (Rel-17, 'A'): Removal of EAP Re-authentication Ericsson Rel-17 Confirm Spec version used - CR states 17.4.0! Revised to S2-2207001.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.2 S2-2207001 CR Approval 23.502 CR3543R1 (Rel-17, 'A'): Removal of EAP Re-authentication Ericsson Rel-17 Revision of S2-2206584. Approved 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:=4 -
7.4 S2-2205664 CR Approval 23.501 CR3666 (Rel-17, 'F'): Periodic update time from UE Ericsson Rel-17 r01 agreed. Revised to S2-2207002. Steve (Huawei) is this needed now?
Steve (Huawei) comments, Cat B?
Sebastian (Qualcomm) supports the CR
Qian (Ericsson) replies
Qian (Ericsson) responds to Steve (Huawei)
Hannu (Nokia) supports the view that this is a modification of a feature in 5GS, but it's an alignment with EPS so a revision would be necessary.
Qian (Ericsson) comments and provide r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Miguel (Qualcomm) provides his understanding of what happened in Rel-15/Rel-16
Revised
7.4 S2-2207002 CR Approval 23.501 CR3666R1 (Rel-17, 'F'): Periodic update time from UE Ericsson Rel-17 Revision of S2-2205664r01. Approved Agreed
7.4 S2-2205665 CR Approval 23.502 CR3508 (Rel-17, 'F'): Periodic update time from UE Ericsson Rel-17 r01 agreed. Revised to S2-2207003. Steve (Huawei) is this needed now? Is it optional?
Steve (Huawei) comments on optional
Sebastian (Qualcomm) supports the CR
Qian (Ericsson) replies
Hannu (Nokia) points out that this CR depends on S2-2205664 on TS 23.501. No objection but suggests the same cover page revision as on S2-2205664.
Qian (Ericsson) comments and provide r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Steve (Huawei) Cat C does not meet FASMO? Let's look at Rel-18 for it.
Qian (Ericsson) comments and propose to go with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.4 S2-2207003 CR Approval 23.502 CR3508R1 (Rel-17, 'F'): Periodic update time from UE Ericsson Rel-17 Revision of S2-2205665r01. Approved Agreed
7.5 - - - Enablers for Network Automation for 5G (eNA) - - Docs:=4 -
7.5 S2-2205583 CR Agreement 23.288 CR0534 (Rel-16, 'F'): Correction for packet retransmission input for service experience analytics Nokia, Nokia Shanghai Bell Rel-16 r01 agreed. Revised to S2-2207004. Wang Yuan (Huawei) provides comments on r00 and provides r01.
Yannick (Nokia): Nokia asks for clarification on r01.
Belen (Ericsson) prefers r01.
Wang Yuan (Huawei) replies to Yannick (Nokia) and Belen (Ericsson) and provides r02.
Yannick (Nokia): Nokia can live with r01. Does not believe r02 is correct.
Jungshin (Samsung) provides a comment on r03
Wang Yuan (Huawei) is OK with r03.
Yannick (Nokia): Nokia provides alternative for the note in r03.
Yannick (Nokia): Nokia suggests to go for r01.
Belen (Ericsson) is okay with r01, not okay with r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is also fine to go with r01.
Jungshin (Samsung) is ok with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.5 S2-2207004 CR Agreement 23.288 CR0534R1 (Rel-16, 'F'): Correction for packet retransmission input for service experience analytics Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2205583r01. Approved Agreed
7.5 S2-2205584 CR Agreement 23.288 CR0535 (Rel-17, 'A'): Correction for packet retransmission input for service experience analytics Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2207005.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.5 S2-2207005 CR Agreement 23.288 CR0535R1 (Rel-17, 'A'): Correction for packet retransmission input for service experience analytics Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2205584. Approved Agreed
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:=13 -
7.7 S2-2205951 CR Approval 23.502 CR3521 (Rel-16, 'F'): Clarification on RAN sharing in case of SNPN LG Electronics Rel-16 r05 agreed. Revised to S2-2207006. zhendong (ZTE) comments
Fei (OPPO) comments.
Youngkyo(Samsung) is okay with the proposed change but may need update the cover page.
Myungjune (LGE) replies to Youngkyo (Samsung)
Youngkyo(Samsung) provide a comment.
Peter Hedman (Ericsson) provides r01
Myungjune (LGE) provides r02.
Myungjune (LGE) provides r03 to further update cover page.
Antoine (Orange) provides r04.
Myungjune (LGE) provides r05.
Peter Hedman (Ericsson) ok with r05
Antoine (Orange) OK with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Youngkyo(Samsung) is okay with r05
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207006 CR Approval 23.502 CR3521R1 (Rel-16, 'F'): Clarification on RAN sharing in case of SNPN LG Electronics Rel-16 Revision of S2-2205951r05. Approved Agreed
7.7 S2-2205952 CR Approval 23.502 CR3522 (Rel-17, 'A'): Clarification on RAN sharing in case of SNPN LG Electronics Rel-17 Revised to S2-2207007. Youngkyo(Samsung) provide a same comment as S2-2205951 .
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207007 CR Approval 23.502 CR3522R1 (Rel-17, 'A'): Clarification on RAN sharing in case of SNPN LG Electronics Rel-17 Revision of S2-2205952. Approved Agreed
7.7 S2-2206047 CR Approval 23.501 CR3646R1 (Rel-16, 'F'): Clarification of UE egress terminology Huawei, HiSilicon Rel-16 Revision of (Noted) S2-2204273 from S2#151E. r02 agreed. Revised to S2-2207008. Chia-Lin (MediaTek) provides comments and proposes to note this CR
Sebastian(Qualcomm) objects to the CR for the same reason as given by MediaTek
Mirko (Huawei) responds
Devaki (Nokia) proposes to note the CR.
Mirko (Huawei) provides r01
Devaki (Nokia) comments.
Sebastian (Qualcomm) comments
Mirko (Huawei) provides r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Sebastian (Qualcomm) is ok with r02, objects to other versions
Devaki (Nokia) is ok with r02 only (cannot accept other revisions).
Chia-Lin (MediaTek) is also only ok with r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207008 CR Approval 23.501 CR3646R2 (Rel-16, 'F'): Clarification of UE egress terminology Huawei, HiSilicon Rel-16 Revision of S2-2206047r02. Approved Agreed
7.7 S2-2206048 CR Approval 23.501 CR3647R1 (Rel-17, 'A'): Clarification of UE egress terminology Huawei, HiSilicon Rel-17 Revision of (Noted) S2-2204274 from S2#151E. Revised to S2-2207009. Sebastian(Qualcomm) objects to the CR for the same reason as given for S2-2206047
Devaki (Nokia) proposes to note the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207009 CR Approval 23.501 CR3647R2 (Rel-17, 'A'): Clarification of UE egress terminology Huawei, HiSilicon Rel-17 Revision of S2-2206048. Approved Agreed
7.7 S2-2206541 DISCUSSION Discussion Discussion on 5G VN group management Huawei, HiSilicon Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
7.7 S2-2206542 CR Approval 23.501 CR3688 (Rel-16, 'F'): Correction on 5G VN group management Huawei, HiSilicon Rel-16 r03 agreed. Revised to S2-2207010. Laurent (Nokia): provides r01
Qianghua (Huawei) OK with r01
Laurent (Nokia): provides r02
Qianghua (Huawei) provides r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207010 CR Approval 23.501 CR3688R1 (Rel-16, 'F'): Correction on 5G VN group management Huawei, HiSilicon Rel-16 Revision of S2-2206542r03. Approved Agreed
7.7 S2-2206544 CR Approval 23.501 CR3689 (Rel-17, 'A'): Correction on 5G VN group management Huawei, HiSilicon Rel-17 Revised to S2-2207011.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.7 S2-2207011 CR Approval 23.501 CR3689R1 (Rel-17, 'A'): Correction on 5G VN group management Huawei, HiSilicon Rel-17 Revision of S2-2206544. Approved Agreed
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:=0 -
7.11 - - - Enhancement of Network Slicing (eNS) - - Docs:=1 -
7.11 S2-2205747 CR Approval 23.502 CR3513 (Rel-17, 'F'): Clarification on NSSAA related mobility restrictions Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
7.12 - - - Optimisations on UE radio capability signalling (RACS) - - Docs:=4 -
7.12 S2-2205754 CR Approval 23.502 CR3514 (Rel-17, 'F'): Handover capability detection Qualcomm Incorporated Rel-17 r02 agreed. Revised to S2-2207012. Qian (Ericsson) provides comments and r01
Haris(Qualcomm) proposes r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.12 S2-2207012 CR Approval 23.502 CR3514R1 (Rel-17, 'F'): Handover capability detection Qualcomm Incorporated Rel-17 Revision of S2-2205754r02. Approved Agreed
7.12 S2-2205755 CR Approval 23.501 CR3674 (Rel-17, 'F'): Handover capability detection Qualcomm Incorporated Rel-17 r02 agreed. Revised to S2-2207013. Qian (Ericsson) provides comments and r01
Haris(Qualcomm) proposes r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.12 S2-2207013 CR Approval 23.501 CR3674R1 (Rel-17, 'F'): Handover capability detection Qualcomm Incorporated Rel-17 Revision of S2-2205755r02. Approved Agreed
7.13 - - - Enhanced IMS to 5GC Integration (eIMS5G_SBA) - - Docs:=0 -
7.14 - - - User Data Interworking and Coexistence (UDICoM) - - Docs:=1 -
7.14 S2-2205524 CR Approval 23.502 CR3502 (Rel-17, 'F'): Clarification on UE reachability for SMS event subscription by NEF Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
7.15 - - - Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) - - Docs:=7 -
7.15 S2-2205484 CR Approval 23.502 CR3500 (Rel-17, 'F'): Correction to N2 based HO in ETSUN case Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2207014, merging S2-2205728, S2-2206197 and S2-2206522. Laurent (Nokia): provides r01
Zhuoyi (ChinaTelecom) agree to merge 6197 to 5484r01.
Fenqin (Huawei) provide r02.
Yang (OPPO) agrees to merge 5728 into 5484, provides r03 with adding OPPO as co-signer.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
7.15 S2-2207014 CR Approval 23.502 CR3500R1 (Rel-17, 'F'): Correction to N2 based HO in ETSUN case Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2205484r03, merging S2-2205728, S2-2206197 and S2-2206522. Approved Agreed
7.15 S2-2206197 CR Approval 23.502 CR3530 (Rel-17, 'F'): Correction on procedure in clause 4.23.7.3, Inter NG-RAN node N2 based handover China Telecom, Inspur Rel-17 Check Affected Clauses! Merged into S2-2207014 Laurent (Nokia): suggest to take 5484 as the baseline (merge 6197 into 5484)
Zhuoyi (ChinaTelecom) agrees to merge 6197 to 5484.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
7.15 S2-2206215 CR Approval 23.502 CR3533 (Rel-16, 'F'): Correction on procedure in clause 4.23.7.3, Inter NG-RAN node N2 based handover China Telecom, Inspur Rel-16 Check Affected Clauses! Noted Laurent (Nokia): objects to 6215 (any R16 CR on this)
Stefan (Ericsson) agrees that rel-16 is not needed
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Laurent (Nokia): objects to 6215 (any R16 CR on this) so this Tdoc shall be NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
7.15 S2-2206522 CR Approval 23.502 CR3538 (Rel-17, 'F'): Correction of the HO preparation description Huawei, HiSilicon Rel-17 Merged into S2-2207014 Laurent (Nokia): Suggests to take 5484 as baseline
Stefan (Ericsson) also thinks that rel-17 is sufficient
Fenqin (Huawei) Clarifies that this is Rel-17 CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Laurent (Nokia): objects to any version of this Tdoc as Fenqin (Than you Fenqin) wrote: 'I see Laurent have provided a revision of 5484. As this is a small issue, we are ok to merge our paper into 5484.'
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
7.15 S2-2206665 CR Approval 23.502 CR3545 (Rel-16, 'F'): Correction on I-SMF removal ZTE Rel-16 Noted Fenqin (Huawei) provides comments.
Stefan (Ericsson) provides comments
Jinguo(ZTE) provides answer to Fenqin and Stefan
Stefan (Ericsson) replies
Fenqin (Huawei) comments.
Jinguo(ZTE) agree to note this paper
Laurent (Nokia): same view as Stefan and Fenqin: quite unlikely scenario and question is if we need a solution for that
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
7.15 S2-2206666 CR Approval 23.502 CR3546 (Rel-17, 'A'): Correction on I-SMF removal ZTE Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
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:=26 -
8.1 S2-2205410 LS In Action LS from CT WG3: LS on Issues on Nadrf_DataManagement Service CT WG3 (C3-223295) Rel-17 Responses drafted in S2-2205683, S2-2206123. Final response in S2-2207015 Replied to
8.1 S2-2205683 LS OUT Approval [DRAFT] Reply LS on Issues on Nadrf_DataManagement Service Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2205410. Merged into S2-2207015 Wang Yuan (Huawei) has concerns for the initial version.
Yannick (Nokia): Nokia replies to Huawei.
xiaobo(vivo) provides comments.
Zhang (Ericsson) response to Xiaobo (vivo)
Yannick (Nokia): Nokia replies to Vivo.
Yannick (Nokia): Nokia requests to mark this Tdoc as merged with S2-2206123.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.1 S2-2206123 LS OUT Approval [DRAFT] LS reply on Issues on Nadrf_DataManagement Service Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2207015, merging S2-2205683. Wang Yuan (Huawei) provides r01.
Zhang (Ericsson) response to Yuan (Huawei)
Yannick (Nokia): Nokia provides r02.
Zhang (Ericsson) is OK with r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is also ok for r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207015 LS OUT Approval Reply LS on Issues on Nadrf_DataManagement Service SA WG2 Rel-17 Revision of S2-2206123r02, merging S2-2205683. Approved Approved
8.1 S2-2205413 LS In Action LS from CT WG3: LS on eNA_Ph2 issues CT WG3 (C3-223775) Rel-17 Responses drafted in S2-2205682, S2-2206125. Final response in S2-2207016 Replied to
8.1 S2-2205682 LS OUT Approval [DRAFT] Reply LS on eNA_Ph2 issues Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2207016, merging S2-2206125. Zhang (Ericsson) provides comments
Wang Yuan (Huawei) provides comments.
Yannick (Nokia): Nokia replies to Huawei and Ericsson.
Zhang (Ericsson) response to Yannick (Nokia)
Yannick (Nokia): Nokia provides r01.
Wang Yuan (Huawei) provides some additional comments on Question 1.
Wang Yuan (Huawei) suggests to postpone the Reply LS and continue the discussion between next meetings.
Yannick (Nokia): Nokia replies to Huawei and suggest to proceed with the LS reply. CT3 need our reply to progress stage 3.
Yannick (Nokia): Nokia relies to Huawei.
Wang Yuan (Huawei) still concerns the related CR since the merging may lose some parameters dedicated to 'bulked data collection' and the CR completely removed all the clues about 'bulked data collection'
Yannick (Nokia): Nokia provides r02.
Yannick (Nokia): Nokia provides r04. r03 is incorrect for answer to question 1.
Zhang (Ericsson) provides r03
Zhang (Ericsson) is OK with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is OK with r04.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207016 LS OUT Approval Reply LS on eNA_Ph2 issues SA WG2 Rel-17 Revision of S2-2205682r04, merging S2-2206125. Approved Approved
8.1 S2-2206125 LS OUT Approval [DRAFT] LS reply on eNA_Ph2 issues Huawei, HiSilicon Rel-17 Response to S2-2205413. Merged into S2-2207016 Zhang (Ericsson) suggest to merge the paper into S2-2205682
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) confirms that this paper is merged into S2-2205682.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.1 S2-2205549 CR Approval 23.288 CR0532 (Rel-17, 'F'): Clarification to Data Delivery and Data Collection via DCCF and via MFAF Ericsson Rel-17 r01 agreed. Revised to S2-2207017. Yannick (Nokia): Nokia provides comments.
Belen (Ericsson) provides r01
Yannick (Nokia): Nokia is ok with r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207017 CR Approval 23.288 CR0532R1 (Rel-17, 'F'): Clarification to Data Delivery and Data Collection via DCCF and via MFAF Ericsson Rel-17 Revision of S2-2205549r01. Approved Agreed
8.1 S2-2205551 CR Approval 23.288 CR0533 (Rel-17, 'F'): Clarification on granularity of time and location for NWDAF analytics results Ericsson Rel-17 r02 agreed. Revised to S2-2207018. Yannick (Nokia): Nokia provides comments.
Belen (Ericsson) provides r01
Yannick (Nokia): Nokia provides r02.
Yannick (Nokia): Nokia comments on r03.
Belen (Ericsson) provides r03
Belen (Ericsson) asks Nokia for clarification
Yannick (Nokia): Nokia replies to Ericsson.
Yannick (Nokia): Nokia ok to go with r02.
Belen (Ericsson) accepts r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Antoine (Orange) suggests to approve r02, not r03.
Yannick (Nokia): Nokia agree with Orange and support approving r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207018 CR Approval 23.288 CR0533R1 (Rel-17, 'F'): Clarification on granularity of time and location for NWDAF analytics results Ericsson Rel-17 Revision of S2-2205551r02. Approved Agreed
8.1 S2-2205670 CR Approval 23.288 CR0536 (Rel-17, 'D'): Correction on wrong reference clause number China Unicom Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.1 S2-2205680 CR Approval 23.288 CR0537 (Rel-17, 'F'): Alignment of DCCF and NWDAF Data Management services and corrections to ADRF Data Management service Nokia, Nokia Shanghai Bell Rel-17 r05 agreed. Revised to S2-2207019. Yannick (Nokia): Nokia provides r01.
Zhang (Ericsson) response to Yannick (Nokia)
Yannick (Nokia): Nokia provides r03.
Zhang (Ericsson) provides r02
Wang Yuan (Huawei) provides comments and suggest to postpone this CR and related LS.
Zhang (Ericsson) suggest to proceed with the CR
Wang Yuan (Huawei) still concerns the CR since the merging may lose some parameters dedicated to 'bulked data collection' and completely removed all the clues about 'bulked data collection'
Yannick (Nokia): Nokia replies to Huawei.
Yannick (Nokia): Nokia is surprised by Huawei's comments. Suggest to proceed with the CR for aspects that we reached consensus on.
Zhang (Ericsson) provide comments
Yannick (Nokia): Nokia provides r04.
Zhang (Ericsson) provide r05 and co-sign
Yannick (Nokia): Nokia is ok with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is also OK with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207019 CR Approval 23.288 CR0537R1 (Rel-17, 'F'): Alignment of DCCF and NWDAF Data Management services and corrections to ADRF Data Management service Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2205680r05. Approved Agreed
8.1 S2-2205681 CR Approval 23.288 CR0538 (Rel-17, 'F'): Corrections on information of previous analytics subscription Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2207020. Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia replies to Ericsson.
Zhang (Ericsson) provides response to Yannick (Nokia)
Yannick (Nokia): Nokia requests for clarification.
Zhang (Ericsson) response to Yannick (Nokia)
Wang Yuan (Huawei) comments.
Zhang (Ericsson) response to Yuan (Huawei)
Wang Yuan (Huawei) replies to Zhang (Ericsson).
Zhang (Ericsson) is OK with r02 and co-sign
Yannick (Nokia): Nokia provides r02.
Zhang (Ericsson) response to Yannick (Nokia) and provide r01
Wang Yuan (Huawei) also OK with r02 and would like to co-sign.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207020 CR Approval 23.288 CR0538R1 (Rel-17, 'F'): Corrections on information of previous analytics subscription Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2205681r02. Approved Agreed
8.1 S2-2205732 CR Approval 23.288 CR0539 (Rel-17, 'F'): Correction of wrong references to TS28.532 KDDI Rel-17 r02 agreed. Revised to S2-2207021. Yannick (Nokia): Nokia provides r01 and ask for clarification.
Malla (NTT DOCOMO) provides r02.
Belen (Ericsson) provides comments to both r01 and initial version
Yannick (Nokia): Nokia supports r02.
Akito (KDDI) is fine with r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207021 CR Approval 23.288 CR0539R1 (Rel-17, 'F'): Correction of wrong references to TS28.532 KDDI Rel-17 Revision of S2-2205732r02. Approved Agreed
8.1 S2-2206124 CR Approval 23.288 CR0540 (Rel-17, 'F'): Clarify the Nadrf_DataManagement_RetrievalRequest service Huawei, HiSilicon Rel-17 r07 agreed. Revised to S2-2207022. Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) replies to Yannick (Nokia) and provides r01.
Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia provides r02.
Zhang (Ericsson) response to Yannick (Nokia)
Wang Yuan (Huawei) replies to Zhang(Ericsson) and Yannick (Nokia).
Zhang (Ericsson) response to Yuan (Huawei)
Wang Yuan (Huawei) accept the suggestion from Zhang (Ericsson) and Yannick (Nokia), and provides r03.
Yannick (Nokia): Nokia provides r04.
Wang Yuan (Huawei) asks for clarification on r04.
Zhang (Ericsson) provides r05
Yannick (Nokia): Nokia provides r06.
Zhang (Ericsson) provide r07 and co-sign
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is OK with r07.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.1 S2-2207022 CR Approval 23.288 CR0540R1 (Rel-17, 'F'): Clarify the Nadrf_DataManagement_RetrievalRequest service Huawei, HiSilicon Rel-17 Revision of S2-2206124r07. Approved Agreed
8.1 S2-2206128 CR Approval 23.502 CR3528 (Rel-17, 'F'): Clarify the analytics context transfer between two AMFs Huawei, HiSilicon Rel-17 Noted Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia concurs with Ericsson.
Wang Yuan (Huawei) replies to Zhang (Ericsson) and Yannick (Nokia), and provides r01.
Zhang (Ericsson) propose to NOTE the paper
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Wang Yuan (Huawei) is OK to note this paper.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.1 S2-2206650 CR Approval 23.288 CR0543 (Rel-17, 'B'): Enabling Analytics for NSAG priority Samsung Rel-17 Noted Peter Hedman (Ericsson) provides comments and suggests that CR is made dependent on the outcome of 8.28 CRs
Yannick (Nokia): Nokia believes this CR should rather be discussed as part of AI# 8.28.
Malla (NTT DOCOMO) We think it's not FASMO and too late for R17 to enhance it.
Peter Hedman (Ericsson) Sorry, ignore as I re-sent to correct AI
Dongeun (Samsung) replies to Peter (Ericsson)
Dongeun (Samsung) replies to Malla (NTT DOCOMO) and Yannick (Nokia)
Leo (Deutsche Telekom) objects to all versions of the CR
Juan Zhang (Qualcomm) provides comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.1 S2-2206653 CR Approval 23.501 CR3695 (Rel-17, 'B'): Enabling Analytics for NSAG priority Samsung Rel-17 Noted Peter Hedman (Ericsson) provides comments and suggests that CR is made dependent on the outcome of 8.28 CRs
Yannick (Nokia): Nokia believes this CR should rather be discussed as part of AI# 8.28.
Peter Hedman (Ericsson) Sorry, ignore as I re-sent to correct AI
Leo (Deutsche Telekom) objects to all versions of the CR
Malla (NTT DOCOMO) objects to all versions of the CR
Dongeun (Samsung) replies to Leo (Deutsche Telekom) and Malla (NTT DOCOMO) that r01 does not intoduce new analytics
Leo (Deutsche Telekom) confirms DT objects to all versions of this CR
Dongeun (Samsung) provides r02 and replies to Leo (DT)
Leo (Deutsche Telekom) objects all versions, including r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.1 - - - Documents exceeding TU Budget - - Docs:=2 -
8.1 S2-2206126 CR Approval 23.288 CR0541 (Rel-17, 'F'): Clarify some issues on Ndccf_DataManagement and Nnwdaf_DataManagement services Huawei, HiSilicon Rel-17 Check Affected Clauses! Not Handled -
8.1 S2-2206127 CR Approval 23.288 CR0542 (Rel-17, 'F'): Clarify the Time Window for the Nadrf_DataManagement service Huawei, HiSilicon Rel-17 Not Handled -
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=6 -
8.2 S2-2205504 CR Approval 23.501 CR3629R1 (Rel-17, 'F'): DN-AAA server selection during UE onboarding Intel Rel-17 Revision of (Postponed) S2-2203829 from S2-151E. r02 agreed. Revised to S2-2207395. Yishan (Huawei) asks for clarification and provides revision option
Yishan (Huawei) further provides r01
Saso (Intel) thinks that r00 is correct.
Peter Hedman (Ericsson) provides r02 based on r00
Yishan (Huawei) provides further clarifications and r03.
Rainer (Nokia) prefers r02..
Saso (Intel) prefers r02..
Yishan (Huawei) provides clarification and can live with r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.2 S2-2207395 CR Approval 23.501 CR3629R2 (Rel-17, 'F'): DN-AAA server selection during UE onboarding Intel Rel-17 Revision of S2-2205504r02. Approved Agreed
8.2 S2-2205505 CR Approval 23.502 CR3463R2 (Rel-17, 'F'): DN-AAA server selection during UE onboarding Intel Rel-17 Revision of (Postponed) S2-2203821 from S2-151E. r01 agreed. Revised to S2-2207396. Peter Hedman (Ericsson) provides r01
Saso (Intel) is OK with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.2 S2-2207396 CR Approval 23.502 CR3463R3 (Rel-17, 'F'): DN-AAA server selection during UE onboarding Intel Rel-17 Revision of S2-2205505r01. Approved Agreed
8.2 S2-2205756 CR Approval 23.501 CR3675 (Rel-17, 'F'): Alignment with SA WG3 agreement on usage of SUCI when CH is legacy AAA Qualcomm Incorporated Rel-17 Postponed Chia-Lin (MediaTek) provides comments
Qianghua (Huawei) provides comments
Peter Hedman (Ericsson) provides comments/questions
Haris(Qualcomm) responds
Chia-Lin (MediaTek) responds to Haris (Qualcomm)
Saso (Intel) comments
Fei (OPPO) comments
Haris(Qualcomm) responds to comments
Saso (Intel) suggests a revision wrt MSK indication
Fei (OPPO) provides comments.
Haris(Qualcomm) proposes r01
Peter Hedman (Ericsson) provides reply that from our understanding when CH=AAA there is lack of support for more than one SNPN.
Peter Hedman (Ericsson) provides question
Haris(Qualcomm) responds that is OK to postpone the CR
Peter Hedman (Ericsson) ok with postponing whole CR while we could have progressed parts of it
Qianghua (Huawei) suggests to use S2-2206546 to align with SA3, move forward with minimum agreeable part
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haris(Qualcomm) objects to the CR
Chia-Lin (MediaTek) is also ok to postpone this CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.2 S2-2206546 CR Approval 23.501 CR3690 (Rel-17, 'F'): Clarification of SUPI for SNPN Huawei, HiSilicon Rel-17 Merged into S2-2205756 (Postponed) Rainer (Nokia) agrees with Haris (Qualcomm).
Haris(Qualcomm) comments and proposes to use S2-2205756 as baseline
Qianghua (Huawei) OK to merge into 5756 for further discussion
Qianghua (Huawei) the fate of 5756 is most likely to be postponed. So I suggest to reconsider to use this CR to go forward to address the EN.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haris(Qualcomm) objects to the CR
Peter Hedman (Ericsson) proposes to maintain merged (or postponed) status for the CR as discussions were in 05756 thread.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=14 -
8.3 S2-2205396 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-2203642 from S2#151E. Response drafted in S2-2205632. Postponed Postponed
8.3 S2-2205632 LS OUT Approval [DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures Ericsson Rel-17 Revision (Postponed) of S2-2203880 from S2#151E. Response to S2-2205396. Postponed Shubhranshu (Nokia) with correct Agenda Item
Xinpeng(Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Shubhranshu (Nokia) proposes to postpone this LS response
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.3 S2-2205414 LS In Information LS from CT WG3: LS on user s consent for EDGEAPP CT WG3 (C3-223780) Rel-17 Noted Shubhranshu (Nokia) Note this paper
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.3 S2-2205435 LS In Information LS from SA WG3: Reply LS on AF specific UE ID retrieval SA WG3 (S3-221161) Rel-17 Noted Shubhranshu (Nokia) Note this paper
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.3 S2-2205627 CR Approval 23.502 CR3470R1 (Rel-17, 'F'): Clarification on Authorization of Service Specific parameter provisioning Ericsson Rel-17 Revision (Postponed) of S2-2203722 from S2#151E. r03 agreed. Revised to S2-2207397. Dario (Qualcomm) provides r01
Magnus (Ericsson) provides r02
Tingfang Tang (Lenovo) comments.
Magnus (Ericsson) provides r03
Shubhranshu (Nokia) asks for clarification
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Dario (Qualcomm) is OK w/ r03 for the removal of 'precedence'.
Magnus (Ericsson) provides answers
Magnus (Ericsson) replies
Shubhranshu (Nokia) comments
Magnus (Ericsson) provides late r04, also ok to approve on time r03
Shubhranshu (Nokia) agrees to approve r04, and not r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.3 S2-2207397 CR Approval 23.502 CR3470R2 (Rel-17, 'F'): Clarification on Authorization of Service Specific parameter provisioning Ericsson Rel-17 Revision of S2-2205627r03. Approved Agreed
8.3 S2-2205628 CR Approval 23.548 CR0059R1 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Revision (Postponed) of S2-2203878 from S2#151E. Noted Xinpeng(Huawei) comments
Shubhranshu (Nokia) asks for clarifications
Magnus H (Ericsson) provides comment
Tingfang Tang (Lenovo) Clarifies and comments.
Magnus H (Ericsson) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Tingfang Tang (Lenovo) proposes to note this contribution as it is aligned with result for the new indication in 5629.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.3 S2-2205629 CR Approval 23.501 CR3634R1 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Revision (Postponed) of S2-2203875 from S2#151E. Confirm Spec version used - CR states 17.4.0! Postponed Xinpeng(Huawei) comments.
Shubhranshu (Nokia) comments
Magnus H (Ericsson) provides comment
Xinpeng(Huawei) replies to Magnus(Ericsson) and Shubhranshu (Nokia).
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Tingfang Tang (Lenovo) Clarifies and comments.
Shubhranshu (Nokia) responds
Zhuoyun (Tencent) comments.
Magnus H (Ericsson) ask question
Xinpeng(Huawei) provides r01.
Zhuoyun (Tencent) provides r02.
Serge (T-Mobile USA) agrees with Tencent and supports r02
Serge (T-Mobile USA) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Xinpeng(Huawei) replies to Zhuoyun (Tencent) and Serge (T-Mobile USA).
Zhuoyun (Tencent) replies.
Xinpeng(Huawei) replies to Zhuoyun (Tencent).
Tingfang Tang (Lenovo) objects r00, is ok with r01 or r02 with cover page aligned.
Magnus H (Ericsson) objects to r02, can live with r01.
Zhuoyun (Tencent) is ok with r01.
Shubhranshu (Nokia) objects to r01, r02, r00 and proposes to Postpone this to next meeting
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.3 S2-2205630 CR Approval 23.502 CR3474R1 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Revision (Postponed) of S2-2203876 from S2#151E. Noted Xinpeng(Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Tingfang Tang (Lenovo) proposes to note this contribution to align the position for the new indication in 5629.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.3 S2-2205631 CR Approval 23.503 CR0721R1 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Revision (Postponed) of S2-2203877 from S2#151E. Noted Xinpeng(Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Tingfang Tang (Lenovo) proposes to note this contribution to align the position for the new indication in 5629.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.3 S2-2205730 DISCUSSION Agreement DP on role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.3 S2-2205733 CR Approval 23.502 CR3512 (Rel-17, 'F'): Adding the EAS rediscovery indication on the PDU session modification procedure China Unicom Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.3 S2-2206891 CR Approval 23.548 CR0062 (Rel-17, 'F'): Corrections related to EDNS Client Subnet option Nokia, Nokia Shanghai Bell Rel-17 r06 agreed. Revised to S2-2207398. Xinpeng(Huawei) provides r01.
Magnus H (Ericsson) provides r01
Shubhranshu (Nokia) provides r03
Magnus H (Ericsson) comments
Xinpeng(Huawei) comments.
Shubhranshu (Nokia) provides r04
Shubhranshu (Nokia) comments
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) responds
Magnus H (Ericsson) ask question
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Magnus H (Ericsson comment to Xinpeng
Shubhranshu (Nokia) provides r05
Shubhranshu (Nokia) provides r06
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Shubhranshu (Nokia) provides r07 correcting grammatical error i.e. adding 's'
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.3 S2-2207398 CR Approval 23.548 CR0062R1 (Rel-17, 'F'): Corrections related to EDNS Client Subnet option Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2206891r06. Approved Agreed
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=47 -
8.4 S2-2205402 LS In Action LS from CT WG3: LS on Clarifications related to UE-Slice-MBR handling CT WG3 (C3-223476) Rel-17 Revision of postponed S2-2203668 from S2#151E. Responses drafted in S2-2205705, S2-2206193, S2-2206765. Final response in S2-2207401 Replied to
8.4 S2-2205705 LS OUT Approval [DRAFT] LS Reply on Clarifications related to UE-Slice-MBR handling Huawei, HiSilicon Rel-17 Response to S2-2205402. Merged into S2-2207401 Jinguo(ZTE) suggest to merge this paper into 6765
Haiyang (Huawei) is OK to merge this paper into 6765
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2206193 LS OUT Approval [DRAFT] Reply LS on Clarifications related to UE-Slice-MBR handling. Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2205402. Merged into S2-2207401 Jinguo(ZTE) suggest to merge this paper into 6765
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2206765 LS OUT Approval [DRAFT] LS on Clarifications related to UE-Slice-MBR handling ZTE r01 agreed. Revised to S2-2207401, merging S2-2205705 and S2-2206193. Haiyang (Huawei) provides r01
Belen (Ericsson) provides comments
Jinguo(ZTE) provides answer to Belen(Ericsson)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.4 S2-2207401 LS OUT Approval LS on Clarifications related to UE-Slice-MBR handling SA WG2 - Revision of S2-2206765r01, merging S2-2205705 and S2-2206193. Approved Approved
8.4 S2-2205406 LS In Action LS from CT WG1: LS on NSSRG restriction on pending NSSAI CT WG1 (C1-224073) Rel-17 Responses drafted in S2-2205701, S2-2206147, S2-2206649, S2-2206762, S2-2206867. CC#3: Postponed Postponed
8.4 S2-2205701 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction on pending NSSAI Huawei, HiSilicon Rel-17 Response to S2-2205406. To be merged into revision of S2-2206762 (Noted). Noted alessio(nokia) proposes to merge into 6762
Haiyang (Huawei) is OK to merge into 6762
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206147 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction on pending NSSAI Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2205406. To be merged into revision of S2-2206762 (Noted). Noted alessio(nokia) proposes to merge into 6762
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206649 LS OUT Approval [DRAFT] Response LS on NSSRG restriction on pending NSSAI NEC Corporation Rel-17 Response to S2-2205406. To be merged into revision of S2-2206762 (Noted). Noted alessio(nokia) proposes to merge into 6762
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206762 LS OUT Approval [DRAFT] LS on NSSRG restriction on pending NSSAI ZTE Response to S2-2205406. CC#3: Noted Genadi (Lenovo) proposes to take this LS as baseline to draft reply to CT1. Propose to merge 5701, 6147, 6649 and 6867 into 6762.
Alessio (nokia) ok to use this LS but we need to add what to do whit the pending NSSAI as in r01
alessio(nokia) agrees with the better text of r02.
Genadi (Lenovo) supports the principle of r01 and provides r02 with some clarifications.
Peter Hedman (Ericsson) provides r03
alessio(nokia) does not agree with r03 conceptually, and even more with quoting snippets of discussions we had out of context in a LS.
Jinguo(ZTE) is ok with r03. The LS may need further update if the CR can not be approved.
Stefano (Qualcomm) supports r03 ONLY. We cannot accept R01 and R02.
Kundan (NEC) supports r03 ONLY. NEC is not fine with v01 and v02 which is against the CT1 specification.
Haiyang (Huawei) is OK with r03.
We reiterate our objection to r03 as it is not consistent with the requested NSSAI formation.
Alessio(Nokia) We reiterate our objection to r03 as it is not consistent with the existing requested NSSAI formation and that shall be preserved.
Haiyang (Huawei) provides r04.
Peter Hedman (Ericsson) supports r03 only, objects to other revisions.
alessio(nokia) strongly objects to the LS r03
Peter Hedman (Ericsson) wasn't CT1 question for the case UE supports NSSRG?
Alessio(Nokia) comments that Ericsson wanted to enable the evaluation of compatibility in the network also for UEs not indicating NSSRG support (alongside HUAWAEI) and this is now in the standards (remember the long drawn out fight?)
Alessio(nokia) asks to postpone the issue as now new elements emerged (like the support of non-supporting UEs that still are using the NSSRG encumbered slices as per the part of the feature strongly desired by Ericsson and Huawei)
Haiyang (Huawei) provides answer, suggest to go with r03.
Haiyang (Huawei) provides response to Alessio (Nokia).
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Kundan (NEC): CT1 has discussed scenario for supporting UE. non supporting UE there is no problem.
Haiyang (Huawei) agrees with Kundan (NEC).
Alessio(Nokia) suggests to take this topic to CC#2 and postpone this topic in general as it is clear the discussion is no more productive.
Alessio(Nokia) based on Kundan's email on another thread we propose then to just postpone without any CC#2 handling of this.
Kundan(NEC) has wrong understanding. NEC proposed or proposes to discuss the LS in CC#2 not any CRs.
Nokia has wrong understanding. NEC proposed or proposes to discuss the LS in CC#2 not any CRs.
Alessio(Nokia) regardless of Kundan's statement: Nokia has correct understanding of the nokia position: this LS shall be noted and the discussion continued till next meeting.
Peter Hedman (Ericsson) support to progress the LS in CC#2.
Majority of the companies (as indicated in this email thread) want to progress the LS and we would like to treat this in CC#2.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206867 LS OUT Approval [DRAFT] LS Reply on NSSRG restriction on pending NS QUALCOMM Europe Inc. - Italy Rel-17 Response to S2-2205406. To be merged into revision of S2-2206762 (Noted). Noted alessio(nokia) proposes to merge into 6762
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2205416 LS In Action LS from CT WG4: Reply LS on Parameter adding in UEContext to support NSSRG feature CT WG4 (C4-223357) Rel-17 Responses drafted in S2-2206523, S2-2206764. Final response in S2-2207388 Replied to
8.4 S2-2206523 LS OUT Approval [DRAFT] Response LS on Parameter adding in UEContext to support NSSRG feature Huawei, HiSilicon Rel-17 r00 agreed. Revised to S2-2207388, merging S2-2206764.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.4 S2-2207388 LS OUT Approval [DRAFT] Response LS on Parameter adding in UEContext to support NSSRG feature Huawei, HiSilicon Rel-17 Revision of S2-2206523r00, merging S2-2206764. Approved Approved
8.4 S2-2206764 LS OUT Approval [DRAFT] LS on Parameter adding in UE Context to support NSSRG feature ZTE Response to S2-2205416. Merged into S2-2207388 Jinguo(ZTE) asks to merge this paper into 2206523
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2205437 LS In Action LS from SA WG3: LS on EAC Mode for NSAC SA WG3 (S3-221164) Rel-17 Response drafted in S2-2205698. Postponed Postponed
8.4 S2-2205698 LS OUT Approval [DRAFT] Reply LS on EAC Mode for NSAC Huawei, HiSilicon Rel-17 Response to S2-2205437. Noted Haiyang (Huawei) provides r01
Ashok (Samsung) request clarification from Haiyang (Huawei) and Jinguo (ZTE)
Jinguo(ZTE) answers
Ashok (Samsung) responds to Jinguo (ZTE) and suggests not to add anything in 23502 spec
Jinguo(ZTE) answers to Ashok(Samsung)
Haiyang (Huawei) provides reply
alessio(Nokia) the CR is not needed
Ashok (Samsung) comments
Haiyang (Huawei) provides comments
Ashok (Samsung) responds to Haiyang (Huawei)
Haiyang (Huawei) responds to Ashok (Samsung)
Alessio(Nokia) repeats we need not the note as this adds nothing to the existing normative capability to set the threshold. operators will set the threshold already to ensure that the feature works properly in the expected scenarios.
Ashok (Samsung) replies to Haiyang (Huawei)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) comments to Ashok (Samsung)
alessio(Nokia) requests to note the LS as it is not needed. objects to sending this as there is no related agreeable cR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2205561 CR Approval 23.502 CR3503 (Rel-17, 'F'): Correction on NSSRG information KDDI Corporation Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.4 S2-2205702 CR Approval 23.501 CR3669 (Rel-17, 'F'): Correction on UE-slice-MBR Provisioning for an S-NSSAI Huawei, HiSilicon Rel-17 Noted Jinguo(ZTE) supports the idea of this paper and asks comments
Myungjune (LGE) provides comments
Dongeun (Samsung) comments
Haiyang (Huawei) clarifies.
Genadi (Lenovo) provides comments and agrees with Myungjune (LGE) and Dongeun (Samsung).
Alessio(Nokia) agrees with Samsung this is a new feature not a Category F FASMO. objects to this CR
Haiyang (Huawei) further clarifies.
alessio(nokia) fully understands the proposal but this is a new feature never discussed so we cannot accept it now.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2205703 CR Approval 23.502 CR3510 (Rel-17, 'F'): Correction on UE-slice-MBR Provisioning for an S-NSSAI Huawei, HiSilicon Rel-17 Noted Dongeun (Samsung) comments (same view with 5702)
Myungjune (LGE) provides comments
Alessio(Nokia) agrees with Samsung/LG this is a new feature not a Category F FASMO. objects to this CR
Haiyang (Huawei) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2205704 CR Approval 23.503 CR0733 (Rel-17, 'F'): Correction on UE-slice-MBR Provisioning for an S-NSSAI Huawei, HiSilicon Rel-17 Noted Dongeun (Samsung) comments (same view with 5702)
Myungjune (LGE) provides comments
Alessio(Nokia) agrees with Samsung/LG this is a new feature not a Category F FASMO. objects to this CR
Haiyang (Huawei) responds
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2205447 LS In Action LS from SA WG6: LS on Support for managing slice for trusted third-party owned application SA WG6 (S6-221484) Rel-18 Responses drafted in S2-2205709, S2-2206018, S2-2206643, S2-2206763. Final response in S2-2207399 Replied to
8.4 S2-2205709 LS OUT Approval [DRAFT] Reply LS on Support for managing slice for trusted third-party owned application Huawei, HiSilicon Rel-18 Response to S2-2205447. Merged into S2-2207399 Jinguo(ZTE) suggests to use 6763 as basis for discussion
Haiyang (Huawei) is OK to merge this paper into 6763
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2206018 LS OUT Approval [DRAFT] LS-Reply-Support for managing slice for trusted third-party owned application Samsung Rel-17 Response to S2-2205447. Merged into S2-2207399 Jinguo(ZTE) suggests to use 6763 as basis for discussion
Ashok (Samsung) is OK to merge this paper into 6763
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2206643 LS OUT Approval [DRAFT] Reply to LS on Support for managing slice for trusted third-party owned application China Mobile Rel-18 Response to S2-2205447. Merged into S2-2207399 Jinguo(ZTE) suggests to use 6763 as basis for discussion
Dan(China Mobile) OK to merge this paper into 6763
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.4 S2-2206763 LS OUT Approval [DRAFT] LS on Support for managing slice for trusted third-party owned application ZTE r03 agreed. Revised to S2-2207399, merging S2-2205709, S2-2206018 and S2-2206643. Ashok (Samsung) comments on r01
Jinguo(ZTE) suggests to use 6763 as basis for discussion and provides r01
Jinguo(ZTE) provides answers
alessio(nokia) agrees with jinguo. that we should not conclude we wil agree to work on this.
Genadi (Lenovo) supports the answers in r01 which apply for Rel-17 and currently agreed Rel-18.
Alessio(nokia) is ok to just say that SA2 may need to study further the necessity of this use case in a contribution driven manner.
Alessio(nokia) provides r02
Ashok (Samsung) thanks Alessio(Nokia) and fine with r02
Haiyang (Huawei) provides r03 based on r02
Jinguo(ZTE) is fine with r02
Dan (China Mobile) is fine with r02 and r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) can only accept r03
Genadi (Lenovo) is fine with r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.4 S2-2207399 LS OUT Approval LS Out on Support for managing slice for trusted third-party owned application SA WG2 - Revision of S2-2206763r03, merging S2-2205709, S2-2206018 and S2-2206643. Approved Approved
8.4 S2-2206030 CR Approval 23.502 CR3525 (Rel-17, 'F'): UE-Slice-MBR exemption for the new PDU session during SSC mode 3 operation Samsung Rel-17 Noted Jinguo(ZTE) provides comments
Haiyang (Huawei) comments
Dongeun (Samsung) replies to Haiyang (Huawei) and Jinguo (ZTE)
Belen (Ericsson) provides comments
Alessio(Nokia) comments that the assumption underlying this paper is that both legs experience the replica of same data (bicasting). if unicast is used the data will go only on one of the legs. the bicasting is not common (infrequent). also the duration of the possible misoperation is short if any (packet dropped) so all in all we see this should not be an issue deserving a FASMO CR.
Haiyang (Huawei) provides comments
Dongeun (Samsung) provides r01 and replies to Belen (Ericsson), Alessio (Nokia), and Haiyang (Huawei)
Haiyang (Huawei) provides further comments
Dongeun (Samsung) replies Haiyang (Huawei)
Dongeun (Samsung) provides r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) provides comments, suggests to note this CR. (objects r00, r01,r02)
Dongeun (Samsung) replies to Jinguo (ZTE)
Jinguo(ZTE) provides response
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206034 CR Approval 23.501 CR3682 (Rel-17, 'F'): UE-Slice-MBR exemption for priority services Samsung Rel-17 Postponed Haiyang (Huawei) provides comments
Genadi (Lenovo) provides comments.
Belen (Ericsson) provides comments
Alessio(Nokia) comments there is no need of a CR
Dongeun (Samsung) replies to Huawei, Lenovo, Ericsson, Nokia
Haiyang (Huawei) clarifies comments
Dongeun (Samsung) replies to Haiyang (Huawei)
Haiyang (Huawei) further clarifies
Dongeun (Samsung) provides r01
Alessio(Nokia) can live with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) further comments
Jinguo(ZTE) share view of Haiyang(Huawei) and provides comments
Dongeun (Samsung) replies to Haiyaing (Huawei) and Belen (Ericsson)
Belen (Ericsson) objects to r01 and initial revision. Ask to postpone.
Dongeun (Samsung) replies to Jinguo (ZTE)
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.4 S2-2206152 CR Approval 23.501 CR3684 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG Nokia, Nokia Shanghai Bell Rel-17 Check Affected Clauses! Postponed Kundan (NEC) comments that the proposed CR violates the NSSRG principle.
Genadi (Lenovo) agrees with the principle of this CR and proposed r01 to be more clear that the AMF does not update the Allowed NSSAI.
alessio is ok with r01
Peter Hedman (Ericsson) provides comments and suggests to follow principle of existing specs and not add the additional AMF logic proposed in this CR
alessio(Nokia) comments the CR follows strictly the current logic. and addresses the issue identified by CT1.
Kundan (NEC) responds to Alessio.
Alessio(Nokia) replies...
Kundan(NEC) replies...
Haiyang (Huawei) provides comments
Kundan(NEC) responds to Jinguo.
Jinguo(ZTE) provides comments
Kundan (NEC) responds to Huawei.
alessio(nokia ) comments on proposal by jinguo
Jinguo(ZTE) replies to Alessio
Alessio(nokia) replies to Jinguo
Jinguo(ZTE) answers
Ashok (Samsung) comments
alessio(nokia) comments that Jinguo may not have fully understood the scenario yet
Kundan(NEC) responds to Alessio (Nokia)
Ashok (Samsung) clarifies to Kundan (NEC)
Jinguo(ZTE) provides r03
alessio (nokia ) cannot accept r02 as Kundan says it add little value and requires more update in stage 3 (the coincidence of an ongoing registration when NSSAA complies is not something we should leverage for an optimization). the UCU is sufficient. so we should stick with r01
Kundan (NEC) responds to Ashok (Samsung)
Kundan (NEC) responds to Jinguo.
Jinguo(ZTE) provides r02
Jinguo(ZTE) provides r04
alessio(Nokia) thinks this Cr is incorrect: the AMF shall ensure the Allowed NSSAI is of S-NSSAIs sharing a NSSRG. there is no requirement the pending is compatible with the allowed. if it is incompatible the pending at NSSA success is removed from Pending but not added to allowed, as we say, and the UCU instead of updating the allowed, updates the pending. easy and consistent with the existing procedures.
alessio(Nokia) thinks this r04 is incorrect: the AMF shall ensure the Allowed NSSAI is of S-NSSAIs sharing a NSSRG. there is no requirement the pending is compatible with the allowed. if it is incompatible the pending at NSSA success is removed from Pending but not added to allowed, as we say, and the UCU instead of updating the allowed, updates the pending. easy and consistent with the existing procedures.
Jinguo(ZTE) response to Alessio(Nokia)
Peter Hedman (Ericsson) objects to r04, r03, r02, r01, r00
Alessio(Nokia) will ask how Ericsson plans on supporting support the non-supporting UEs that they wanted to enable using NSSRG feature and be configured with all the S-NSSAIs in the subscription.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Kundan (NEC) objects all revisions and initial version as well.
Alessio(Nokia) suggests to take this topic to CC#2 and postpone this topic in general as it is clear the discussion is no more productive.
Kundan (NEC) responds that many company rejected this CR so we shouldn't take this to CC#2 instead LS response should be treated in CC#2.
Alessio(Nokia) is ok to postpone the whole topic and all related CRs if this is preferable.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.4 S2-2206159 CR Approval 23.502 CR3529 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG Nokia, Nokia Shanghai Bell Rel-17 Noted Peter Hedman (Ericsson) provides comments that CR is not needed
alessio(Nokia) comments that ericsson did not grasp the issue that we DO NOT want to change the formation of requested NSSAI , the time issue is just a secondary aspect.
Peter Hedman (Ericsson) provides comments that CR is against current design as discussed in related thread.
alessio (nokia) disagrees: the formation of requested NSSAI today is oblivious of the compatibility with pending NSSAI. we should not change that
Kundan(NEC) proposes to note this CR. As it is not needed. the reasons were given in other thread. This proposal is not aligned what CT1 is asking.
Alessio(Nokia) comments on the wrong comment by kundan who seem to imply CT1 asked us to changed the UE behaviour for requested NNSAI . this is the wrong interpretation of the LS .
alessio(Nokia) the existing logic AT UE does not check the pending NSSAI sorry. nor in CT1
Peter Hedman (Ericsson) objects to all versions of the CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206189 DISCUSSION Agreement Discussion on NSSAA and Simultaneous Use of Network Slices constraints features interaction Nokia, Nokia Shanghai Bell Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206214 CR Approval 23.501 CR3686 (Rel-17, 'F'): Correction on TARGET NSSAI excluding some S-NSSAI(s) of the Allowed NSSAI Nokia, Nokia Shanghai Bell Rel-17 Noted Dongeun (Samsung) comments
alessio(Nokia) thanks Samsung for sharing the opinion with nokia we need to consider the relative importance of slices based on home policy per UE, but disagrees to bundle this with 8.28. while we see the synergies we should keep the discussion separate.
Peter Hedman (Ericsson) provides comments and object to non-FASMO CR
alessio(Nokia) comments that this is FASMO as there are no means to determine which slice is to be in target NSSAI without this addition.. invites Ericsson to show how this works without this.
Haiyang (Huawei) provides comments
Peter Hedman (Ericsson) provides reply
alessio(Nokia) comments that S2-2205881 use case cannot exist unless we have a deterministic way for HPLMN to tell the serving node which Slice is more important.
Kundan (NEC) finds Alessio has contradictory statements regarding slice priority and subscription. In NSSRG and NSSAA interaction topics he stated that slice has not priority and in this contributions he said the slice has priority in subscription. so his statement is contradictory.
Until the slice priority is clarified this CR is not needed and also this is not FASMO. so we are not fine with this CR.
Alessio notes the comment by Kundan (NEC) is mixing up some independent issues in an incorrect way. also quotes statements nokia never made and in any case would not apply to the other issue.
Kundan(NEC) proposes to note this CR as it is not FASMO. Operator preference and local policies can take care of the target NSSAI.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Iskren(NEC) - after further discussion we no more object to this CR.
Alessio(Nokia) thanks Iskren(NEC) , proposes this goes to CC#2 as the other opinions that proposed to use RFPS are technically wrong as RFSP is based on TARGET NSSAI and target NSSAI is what we need to formulate based on the received priorities from UDM as per this CR.
Haiyang (Huawei) comments and suggests to note this paper.
Peter Hedman (Ericsson) re-confirms the objection and provides comments
Alessio(Nokia) does NOT understand why RFSP is even mentioned here as the issue is the TARGET NSSAI formation that is before any RFSP is obtained from AMF
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206238 CR Approval 23.502 CR3534 (Rel-17, 'F'): Correction on TARGET NSSAI excluding some S-NSSAI(s) of the Allowed NSSAI Nokia, Nokia Shanghai Bell Rel-17 Noted Dongeun (Samsung) comments
alessio(Nokia) thanks Samsung for sharing the opinion with nokia we need to consider the relative importance of slices based on home policy per UE, but disagrees to bundle this with 8.28. while we see the synergies we should keep the discussion separate.
Peter Hedman (Ericsson) provides comments and object to non-FASMO CR
Alessio (nokia) asks perter Peter Hedman (Ericsson) to prove it is NOT FASMO and describe how the thing works now without the proposed changes.
alessio(Nokia) Asks Peter to provide how he resolves the cases in the email
Haiyang (Huawei) comments
Peter Hedman (Ericsson) provides reply
alessio(nokia) replied that the ability to dynamically know in the network a slice priority on a time of day basis can be added (if that is the intention) in the subscription info. but if this is to be decided by the UE at run time we have no means to do that normatively. in any case this is indeed a per UE thing and based on the operator (i.e. HPLMN)commercial offering.
Haiyang (Huawei) further comments
Peter Hedman (Ericsson) provides comments and maintains objection
Haiyang (Huawei) agrees with Peter Hedman (Ericsson) that RFSP index should be used as current design
alessio(Nokia) points our both Huawei and Ericsson miss the point the RFSP of the TARGET NSSAI is obtained AFTER the target NSSAI is obtained, the issue is HOW we come to a TARGEET NSSAI excluding Some of the Allowed NSSAIs. We contend it is not possible without indication some of the Allowed are of lesser importance to the HPLMN (as the current text already say it is based on customer-operator agreement and the operator that can agree with customer is ONLY the HPLMN. hence subscribes s-NSSAI priority is needed to drive this.
alessio(nokia) cannot accept inter-PLMN configuration as basis also because the priorities can be different for different UEs.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) comments and suggests to discuss slice priority in one thread.
Alessio(Nokia) proposes this goes to CC#2 for resolution.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206239 DISCUSSION Agreement Discussion on TARGET NSSAI excluding some S-NSSAI(s) of the Allowed NSSAI Nokia, Nokia Shanghai Bell Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206524 CR Approval 23.502 CR3539 (Rel-17, 'F'): UE context transferring between AMF Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2207400. Jinguo(ZTE) supports this paper
Fenqin (Huawei) Responds
Tyler (OTD) comments
Dongeun (Samsung) comments
Myungjune (LGE) provides comments
Fenqin (Huawei) provides responses and r01.
Alessio(Nokia) can be OK with rewording by Fenqin and provides r02 with Nokia support
Tyler (OTD) comments on R2 and supports change.
George (Ericsson) provides r03 including minor editorial changes and co-signed
Alessio prefers R02 as this is confusing a bit as it says this is the list of parameters to be transferred (which in theory istrue) but we know it is not the case for all of them
Fenqin (Huawei) provides responses and r04.
Tyler (OTD) provides comment and support for r04.
alessio (Nokia) is ok with r04.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
George (Ericsson) OK with r04 as well.
Fenqin(Huawei) suggest to go with r04
Tao(VC) add previous comments manually and check go with r04.
Alessio(nokia) OK with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.4 S2-2207400 CR Approval 23.502 CR3539R1 (Rel-17, 'F'): UE context transferring between AMF Huawei, HiSilicon Rel-17 Revision of S2-2206524r04. Approved Agreed
8.4 S2-2206644 CR Approval 23.501 CR3693 (Rel-17, 'F'): Pending NSSAI and NSSRG NEC Rel-17 Postponed Jinguo(ZTE) corrects the title and propose to focus on the LS, the CR can be noted.
Kundan (NEC) clarifies with Jinguo. Hope other CRs on this topic from other companies are also noted.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
alessio(Nokia) reiterates this topic has to be postponed and CR noted. (BTW seems like comments are lost from notes on many documents in this AI?)
alessio(Nokia) would like to remark in the notes that a CR will be needed in SA2 (unklike junguo stated) . what the Cr will say we will discuss until next meeting hoping to converge.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.4 S2-2206652 CR Approval 23.501 CR3694 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.501 NEC Rel-17 Postponed Peter Hedman (Ericsson) provides comments that the topic was handled and CR agreed at the last meeting i.e. CR is not needed
Kundan(NEC) responds to Peter.
Jinguo(ZTE) agree that this CR is not needed
Kundan (NEC) responds to Haiyang.
Haiyang (Huawei) provides a question on r01
Kundan (NEC) provides r01 incorporating Peters comment.
Kundan (NEC) comments
Ashok (Samsung) comments
Jinguo(ZTE) provides comments
Genadi (Lenovo) provides questions.
alessio(Nokia) objects to all revisions as there is no FASMO issue to solve identified.
Peter Hedman (Ericsson) provides comments that logic is solving an issue.
Kundan(NEC) provides response to Genardi(Lenovo).
Genadi (Lenovo) provides response to Kundan (NEC).
Kundan (NEC) responds to Genadi (Lenovo).
Alessio(Nokia) proposes to postpone this CR as we need to consider what happens if the Pending and new requested are incompatible. we do have NSSRG interaction issue here.
Alessio(Nokia) cannot accept r02 as if the behaviour is FFS you do not draft a FASMO CR .
NEC (Kundan) provides r02 Alessio comment.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
A FASMO CR (3102)/ S2-2201474 with ENs on a frozen release was agreed in the Meeting #149-e. Nokia was one the co-signing companies. So we request Nokia to accept the CR with ENs or r01 which doesn't have ENs.
Alessio(nokia) retains this topic and CR has to be postponed to allow more time to discuss. no need to add ENs.
Jinguo(ZTE) is ok with r00, r01, object to r02
Haiyang (Huawei) can live with r01, objects to r00 and r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.4 S2-2206667 CR Approval 23.502 CR3547 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.502 NEC Rel-17 Noted Peter Hedman (Ericsson) provides comments that the topic was handled and CR agreed at the last meeting i.e. CR is not needed
Haiyang (Huawei) suggests to note this CR (based on the 501 discussion, no need to update NSSF service/procedure)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206668 CR Approval 23.501 CR3616R1 (Rel-17, 'F'): Clarification on UE-Slice-MBR ZTE Rel-17 Revision of (Postponed) S2-2202661 from S2#150E. Confirm Spec version used - CR states 17.4.0! CC#3: r05 + changes agreed. Revised to S2-2207688. Alessio(Nokia) provides r01
Jinguo(ZTE) provides r02
Haiyang (Huawei) supports this paper.
Jinguo(ZTE) provides r03 and response to Dongeun (Samsung)
Dongeun (Samsung) ask quesiton
alessio(nokia) provides a cleaned up version and also uses the right normative language.
Belen (Ericsson) provides r04
Belen (Ericsson) provides r05, disregard r04.
Jinguo(ZTE) is fine with r05
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Alessio(Nokia) can live with r05
Genadi (Lenovo) proposes to open this CR in CC#2. Agree with the principle of the CR, but text update is needed. r05 is not according to the drafting rules (as it deletes new proposed text). R04 also need fixes.
Jinguo(ZTE) suggest to approve r05
Genadi (Lenovo) comments to Jinguo(ZTE) that the text in r05 is unclear and proposes further revision.
Alessio(Nokia) is ok with this update proposed by Genadi(lenovo)
Jinguo(ZTE) is ok with Genadi(lenovo) proposal. Ask CC#3.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.4 S2-2207688 CR Approval 23.501 CR3616R2 (Rel-17, 'F'): Clarification on UE-Slice-MBR ZTE Rel-17 CC#3: Revision of S2-2206668. This CR was agreed Agreed
8.4 S2-2206760 CR Approval 23.502 CR3548 (Rel-17, 'F'): Clarification on EAC mode ZTE Rel-17 Noted Alessio(Nokia) asks to note the CR as it is not FASMO (FASMO happens if a threshold is not configured properly but no CR can be FASMO because we assume the operator will misconfigure networks as otherwise the right configuration shall be standardized.)
Haiyang (Huawei) provides r01
Ashok (Samsung) is not OK with r01
Haiyang (Huawei) provides r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
alessio(Nokia) reiterates the CR is not needed. also a 'shall' statement cannot be in a note. objects to all revisions
Haiyang (Huawei) suggest to agree r02 with changing 'shall' to 'should'
Alessio(Nokia)still does not agree with this.CR.
Haiyang (Huawei) seeks clarification from Alessio (Nokia)
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 - - - Documents exceeding quota per company - - Docs:=4 -
8.4 S2-2205706 CR Approval 23.501 CR3670 (Rel-17, 'F'): Clarifications on UE-Slice-MBR handling Huawei, HiSilicon Rel-17 Not Handled -
8.4 S2-2205699 CR Approval 23.502 CR3509 (Rel-17, 'F'): Clarification on EAC Mode for NSAC Huawei, HiSilicon Rel-17 Noted Ashok (Samsung) comments
Alessio (nokia) asks a question on this note (notes are not normative so cannot be FASMO so we would like to say this CR cannot be approved at this stage of the release)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.4 S2-2206669 CR Approval 23.501 CR3696 (Rel-17, 'F'): Change of mapping of .allowed NSSAI NEC Rel-17 Not Handled -
8.4 S2-2206761 CR Approval 23.502 CR3549 (Rel-17, 'F'): Clarification on UE context transfer ZTE Rel-17 Not Handled -
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=22 -
8.5 S2-2205411 LS In Action LS from CT WG3: LS on AF session with required QoS procedures support for TSC traffic CT WG3 (C3-223553) Rel-17 Responses drafted in S2-2206053, S2-2206202. CC#3: Final response in S2-2207695 Replied to
8.5 S2-2206053 LS OUT Approval [DRAFT] Response to LS on AF session with required QoS procedures support for TSC traffic Huawei, HiSilicon Rel-17 Response to S2-2205411. CC#3: r01 + changes agreed. Revised to S2-2207695. Shabnam (Ericsson) we need to decide if the feature is supported or not, ZTE paper 6202 has clearer position aligned with the situation that we did not discuss the service in the context of TSN, this response assumes the feature is enabled? But not clear in the statement.
zhendong (ZTE) comments
Shabnam (Ericsson) at least to me that is not clear in Huawei CR and I thought we have said TSC will use dedicated PDU session/DNN or?
zhendong (ZTE) provides response
Sang-Jun (Samsung) comments.
Mirko (Huawei) responds
zhendong (ZTE) provides the response
Shabnam (Ericsson) comments that the assumption is not correct, see clause 5.27.0, 23.501
zhendong (ZTE) provides the response.
Devaki (Nokia) comments.
Devaki (Nokia) proposes r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Shabnam (Ericsson) does not agree with current wording of r01, as it is NOT necessary for TSC to support sponsored connectivity. If we want to support this, then needs to rephrase to say 'if' it is necessary so a revision will be needed.
Mirko (Huawei) responds and suggests to accept r01.
Shabnam (Ericsson) does not share same view on the interpretation, comments
Mirko (Huawei) responds.
Devaki (Nokia) shares same understanding as Mirko, with regards to the wording 'if or when' is better than 'possible' (as it makes it sound quite ambiguous for an LS response).
Shabnam (Ericsson) thanks Mirko and the text proposal 'SA2 expects that sponsored data connectivity functionality is possible for scenarios....' is acceptable. So we will make this change on top of r01.
Devaki (Nokia) can also with r01 plus the proposed text proposal 'SA2 expects that sponsored data connectivity functionality is possible for scenarios....'
zhendong (ZTE) can accpet the r01 plus 'possible'
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.5 S2-2207695 LS OUT Approval Reply to LS on AF session with required QoS procedures support for TSC traffic SA WG2 Rel-17 CC#3: Revision of S2-2206053r01 + changes. This LS OUT was approved Approved
8.5 S2-2206202 LS OUT Approval [DRAFT] Reply LS on AF session with required QoS procedures support for TSC traffic ZTE Response to S2-2205411. Noted Shabnam (Ericsson) proposes to NOTE this response and continue on 6053 thread.
zhendong (ZTE) provides the response
Jari (NTT DOCOMO) proposes to note.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.5 S2-2205562 CR Agreement 23.501 CR3603R2 (Rel-17, 'F'): Revisions on Exposure of Time Synchronization Inspur Rel-17 Revision of (Postponed) S2-2202279 from S2#151E. Merged into S2-2207026 Devaki (Nokia) comments that this paper could be merged with S2-2205794.
Shabnam (Ericsson) proposes to use 5794 as the basis since that is more accurate and has following additional comments
Haiyang (Huawei) supports to merge 5562 and 5794.
Scott(Inspur) relies to all.
Sang-Jun (Samsung) also proposes to use 5794 as the basis.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.5 S2-2205563 CR Agreement 23.501 CR3636R1 (Rel-17, 'F'): Miscellaneous changes on Distribution of gPTP Sync and Follow_Up messages Inspur Rel-17 Revision of (Unhandled) S2-2203999 from S2#151E. Confirm CR Number - CR states 3603! Noted Devaki (Nokia) proposes to note the CR as it is technically incorrect.
Jari (NTT DOCOMO) agrees with Nokia
zhendong (ZTE) comments
zhendong (ZTE) respond to scott
Sebastian (Qualcomm) has the same view as Nokia and NTT DoCoMo and proposes to note the CR
Qianghua (Huawei) shares the previous comments
Scott (Inspur) respond to zhendong and all
Sang-Jun (Samsung) have same views as the the previous comments.
Scott(inspur) replies to Sang-Jun (Samsung).
Sang-Jun (Samsung) replies to Scott(inspur).
Scott(Inpsur)provides r01
Scott(Inpsur)provides r01 to correct revision folder.
Sang-Jun (Samsung) replies to Scott (inspur).
Sebastian (Qualcomm) comments
Scott (inspur) replies to Sang-Jun (Samsung).
Scott(Inspur) replies to Sebastian (Qualcomm)
Sebastian (Qualcomm) replies inline
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Sang-Jun (Samsung) comments.
Devaki (Nokia) objects to the CR as it is technically incorrect (it seems there was a misunderstanding that the text is duplicated while it is not).
Scott(Inspur) may accept to postpone the paper, but it is expected that Devaki can give more explanation.
Devaki (Nokia) replies to Scott (Inspur) that the rationale for our objection was provided in the very first email sent already - acknowledged by others as well. Repeating again, (g)PtP message must be forwarded to all leader ports, DS-TT and NW-TT ports thus the sentence is not redundant as the CR claims - one is for DS-TT and one is for NW-TT.
Scott(Inspur) replies to Devaki.
Devaki (Nokia) comments.
Jari (NTT DOCOMO) objects r00 and r01
Sang-Jun (Samsung) also objects to the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.5 S2-2205446 LS In Action LS from SA WG6: LS on TSN scenarios SA WG6 (S6-221449) Rel-17 Response drafted in S2-2205793. Final response in S2-2207023 Replied to
8.5 S2-2205793 LS OUT Approval [DRAFT] Reply LS on TSN scenarios Ericsson Rel-17 Response to S2-2205446. r02 agreed. Revised to S2-2207023. Sebastian (Qualcomm) provides r01
György (Ericsson) provides r02
Qianghua (Huawei) provides comments
Sang-Jun (Samsung) provides comments.
György (Ericsson) responds.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.5 S2-2207023 LS OUT Approval [DRAFT] Reply LS on TSN scenarios Ericsson Rel-17 Revision of S2-2205793r02. Approved Approved
8.5 S2-2205791 CR Approval 23.502 CR3516 (Rel-17, 'F'): Mapping GPSIs and Group Identifiers to a SUPI list Ericsson Rel-17 r01 agreed. Revised to S2-2207024. Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
György (Ericsson) comments.
György (Ericsson) provides r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.5 S2-2207024 CR Approval 23.502 CR3516R1 (Rel-17, 'F'): Mapping GPSIs and Group Identifiers to a SUPI list Ericsson Rel-17 Revision of S2-2205791r01. Approved Agreed
8.5 S2-2205792 CR Approval 23.502 CR3517 (Rel-17, 'F'): Clarification that NEF uses time sync services provided by TSCTSF Ericsson Rel-17 Revised to S2-2207025. CC#3: This CR was agreed Devaki (Nokia) wonders why this CR is a FASMO?
Shabnam (Ericsson) As the procedures are wrongly placed and NEF is common to the architecture, we had quite some confusion to clarify to stage 3 work what goes with what. As we continue to develop the feature in Rel-18, we believe it is FASMO to ensure we have correct specification base specially for SBI.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.5 S2-2207025 CR Approval 23.502 CR3517R1 (Rel-17, 'F'): Clarification that NEF uses time sync services provided by TSCTSF Ericsson Rel-17 Revision of S2-2205792. Approved. CC#3: WITHDRAWN Withdrawn
8.5 S2-2205794 CR Approval 23.501 CR3603R3 (Rel-17, 'F'): Defining the time distribution methods Samsung, Ericsson Rel-17 r05 agreed. Revised to S2-2207026, merging S2-2205562. Devaki (Nokia) comments.
Josep (DT) comments. Wonders whether we should also add text to 5.27.1.1
Sebastian (Qualcomm) provides r01
Josep (DT) provides r02.
Haiyang (Huawei) comments and supports to merge 5562 and 5794.
Scott (Inspur) comments and supports to merge 5562 to 5794.
Haiyang (Huawei) responds to Shabnam (Ericsson).
Scott (Inspur) asks for cosigning the paper.
Shabnam (Ericsson) asks for clarification on the changes
Haiyang (Huawei) provides r04.
Shabnam (Ericsson) provides r03, updated according to comments received.
Shabnam (Ericsson) provides r05, considers FASMO as the relationship between methods have caused confusion within and outside 3GPP.
Josep (DT) comments on being FASMO and Devaki's (Nokia) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Sang-Jun (Samsung) is fine with r05.
Scott (Inspur) comments that we can live with r05 and would like to cosign the paper.
Devaki (Nokia) comments that we can live with r05 for now.
Haiyang (Huawei) is OK with r05.
Josep (DT) is OK with r05, would like to co-sign.
zhendong (ZTE) is fine with r05
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.5 S2-2207026 CR Approval 23.501 CR3603R4 (Rel-17, 'F'): Defining the time distribution methods Samsung, Ericsson Rel-17 Revision of S2-2205794r05, merging S2-2205562. Approved Agreed
8.5 S2-2206051 CR Approval 23.503 CR0735 (Rel-17, 'F'): Alignment of IIoT related parameter description Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2207027, merging S2-2206204. György (Ericsson) provides r01.
Mirko (Huawei) provides r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.5 S2-2207027 CR Approval 23.503 CR0735R1 (Rel-17, 'F'): Alignment of IIoT related parameter description Huawei, HiSilicon Rel-17 Revision of S2-2206051r02, merging S2-2206204. Approved Agreed
8.5 S2-2206052 CR Approval 23.502 CR3527 (Rel-17, 'F'): Alignment of IIoT related parameter description Huawei, HiSilicon Rel-17 Noted Devaki (Nokia) has strong concerns with this paper - Reason for changes indicate that it resolves inconsistencies, duplication but then it is actually making functional changes and/or removing features which is not acceptable at this point.
György (Ericsson) agrees with Nokia.
Mirko (Huawei) responds.
zhendong (ZTE) provides the way forward
Devaki (Nokia) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Devaki (Nokia) objects to this CR as this CR is not a FASMO, also our concern is that this risks destabilizing existing spec (detailed reasons provided in the earlier emails).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.5 S2-2206200 CR Approval 23.501 CR3685 (Rel-17, 'F'): Clarification on 5G access stratum distribution in mobility and AM policy modification ZTE Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.5 S2-2206201 CR Approval 23.502 CR3531 (Rel-17, 'F'): Clarification on 5G access stratum distribution in mobility and AM policy modification ZTE Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.5 S2-2206203 CR Approval 23.502 CR3532 (Rel-17, 'F'): Clarification on AF session with required QoS procedures support for TSC traffic ZTE Rel-17 Noted Shabnam (Ericsson) asks should we not also make the changes in clause 4.15.6.6a, Update clause?
zhendong (ZTE) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Jari (NTT DOCOMO) proposes to note
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.5 S2-2206204 CR Approval 23.503 CR0736 (Rel-17, 'F'): Clarification on AF session with required QoS procedures support for TSC traffic ZTE Rel-17 Merged into S2-2207027 Mirko (Huawei) suggests to consider this CR as merged into S2-2206051.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.6 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) - - Docs:=7 -
8.6 S2-2205405 LS In Action LS from CT WG1: LS on response messages for UE assistance operation CT WG1 (C1-223974) Rel-17 Response drafted in S2-2205858. CC#3: Final response in S2-2207696 Replied to
8.6 S2-2205858 LS OUT Approval [DRAFT] Reply LS on response messages for UE assistance operation Ericsson Rel-17 Response to S2-2205405. CC#3: r01 agreed. Revised, merging S2-2206787, to S2-2207696. DongYeon (Samsung) proposes to merge 2205858 and 2206787.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Myungjune (LGE) provides r01.
Stefan (Ericsson) OK with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.6 S2-2207696 LS OUT Approval Reply LS on response messages for UE assistance operation Ericsson Rel-17 CC#3: Revision of S2-2205858r01, merging S2-2206787. This LS OUT was approved Approved
8.6 S2-2205857 CR Approval 23.501 CR3678 (Rel-17, 'F'): PMF UAD and UAT message handling clarifications Ericsson Rel-17 r01 agreed. Revised to S2-2207028, merging S2-2206784. DongYeon (Samsung) proposes to merge 2205857 and 2206784.
Jinguo(ZTE) provides comments
Myungjune (LGE) provides comments
Rainer (Nokia) comments.
Stefan (Ericsson) provides r01
Rainer (Nokia) is ok with r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.6 S2-2207028 CR Approval 23.501 CR3678R1 (Rel-17, 'F'): PMF UAD and UAT message handling clarifications Ericsson Rel-17 Revision of S2-2205857r01, merging S2-2206784. Approved Agreed
8.6 S2-2206784 CR Approval 23.501 CR3699 (Rel-17, 'F'): Addition of acknowledgement on UE assistance procedures Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2207028 DongYeon (Samsung) proposes to merge 2205857 and 2206784.
Rainer (Nokia) replies.
Andy (VC, Samsung) will mark 6784 as merged into 5857.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.6 S2-2206787 LS OUT Approval [DRAFT] Reply LS on Acknowledging reception of UE assistance operation messages Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2207696 DongYeon (Samsung) proposes to merge 2205858 and 2206787.
Rainer (Nokia) replies.
Andy (VC, Samsung) will mark 6787 as merged into 5858.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.7 - - - Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) - - Docs:=8 -
8.7 S2-2205417 LS In Action LS from CT WG4: LS on UAV authorization container CT WG4 (C4-223513) Rel-17 Responses drafted in S2-2206241, S2-2206870. CC#3: Postponed Postponed
8.7 S2-2206241 LS OUT Approval [DRAFT] Reply LS on UAV authorization container Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2205417. CC#3: Postponed Stefano (Qualcomm) recommends noting this paper and proceeding with S2-2206870 due to technical concerns.
Pallab (Nokia) responds to Stefano (Qualcomm) and proposes to go with this LS response. The LS response in 6870 is incorrect
Ashok (Samsung) agrees with Pallab (Nokia) and proposes to use 6241 for the LS OUT.
Stefano (Qualcomm) disagree with Nokia and disagree with proceeding with the LS response in 6870.
Shabnam (Ericsson) comments that both response has issues in our view, SMF is transparent we agree but Nokia LS response states transparent to 3GPP system which is not correct since UAV NF/NEF will not be transparent to the container type, see below.
Ashok (Samsung) comments
Dimitris (Lenovo) comments
Guanzhou (InterDigital) shares Stefano(QC)'s view.
Pallab (Nokia) responds to Guanzhou (InterDigital)
Guanzhou (InterDigital) responds to Pallab (Nokia).
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Pallab (Nokia) responds to Guanzhou (InterDigital).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.7 S2-2206870 LS OUT Approval [DRAFT] LS Reply on UAV authorization container QUALCOMM Europe Inc. - Italy Rel-17 Response to S2-2205417. Noted Pallab (Nokia) proposes to NOTE this as the LS response is incorrect. More comments in the discussion thread of 6241.
Shabnam (Ericsson) as stated in the other response thread, we believe SMF is transparent whereas UAS NF/NEF is not.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.7 S2-2205441 LS In Information LS from SA WG3: Reply LS on Indication of Network Assisted Positioning method SA WG3 (S3-221254) Rel-17 Noted Shabnam (Ericsson) proposes to note this LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.7 S2-2205901 CR Approval 23.256 CR0065 (Rel-17, 'F'): Clarifications on subscription control for UUAA-SM and C2 authorization Ericsson Rel-17 r12 agreed. Revised to S2-2207402. Guanglei (Huawei) provides comments and ask questions
Jaewoo (LGE) provides comment.
Dimitris (Lenovo) comments
Pallab (Nokia) comments and provides r01.
Stefano (Qualcomm) comments, agree r01 is not acceptable.
Shabnam (Ericsson) r01 is not acceptable for us, some initial response before providing revision, we also need to resolve the incoming LS & issue about SMF transparent or not. See in line:
Guanglei (Huawei) further comments
Ashok (Samsung) comments
Pallab (Nokia) comments.
Dimitris (Lenovo) provides a few points to address regarding transparency of the UAS container at the SMF.
Jaewoo (LGE) provides comments.
Guanglei (Huawei) provides r02 based on r01
Guanglei (Huawei) is fine to not mention the API indication
Shabnam (Ericsson) thanks LGE for the clarification, but still don't believe we need to add every single parameter in stage 2 specially we don't show the details anywhere else.
Shabnam (Ericsson) thanks Ashok for the information, need to think if it equally applies for EPS and also we should fix the spec to change the 'may' to 'can' as specification rules dictate.
Ashok (Samsung) comments on the changes done on r05
Shabnam (Ericsson) r06 is not really in line with others comments, so I provide response for you below and ask how others feel before providing revision
Guanzhou (InterDigital) provides r06 based on r04
Shabnam (Ericsson) asks where these new requirement for re-AA comes from and we can't place normative statement in NOTE. Asks justification since none provided.
Ashok (Samsung) provides r05
Shabnam (Ericsson) provides r04
Antoine (Orange) provides r03.
Stefano (Qualcomm) comments and is not OK with the content of these revisions, sorry.
Pallab (Nokia) provides r07 based on r04. Also provides responses.
Pallab (Nokia) responds to Stefano (Qualcomm).
Antoine (Orange) provides r08, reintating a sentence removed in r07.
Pallab (Nokia) comments on r08.
Antoine (Orange) replies to Pallab.
Pallab (Nokia) responds to Antoine (Orange).
Antoine (Orange) responds.
Antoine (Orange) replies.
Antoine (Orange) .
Shabnam (Ericsson) provides comments for agreement before providing r09 & r01 with two alternatives to choose from.
Antoine (Orange) supports r09.
Pallab (Nokia) responds to Shabnam
Shabnam (Ericsson) comments that we still have time to do revision before submission deadline
Shabnam (Ericsson) provides r11, based on r10.
Guanzhou (InterDigital) comments on r09/r10 and provides r12.
Shabnam (Ericsson) comments that r12 changes are not correct, provides explanation
Guanzhou (InterDigital) responds to Shabnam
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Shabnam (Ericsson) comments asks Interdigital to provide exactly what text he is having issue with
Guanzhou (InterDigital) has issues with most of the revisions due incorrect text.
Guanglei (Huawei) comments on r12
Guanzhou (InterDigital) responds to Shabnam and BTW points out that Stefano(Qualcomm) had wrong delegate/company name in his previous email.
Stefano (Qualcomm) indicates previous comments were solely by Qualcomm and replies.
Pallab (Nokia) OK with r10, 12. Objects to all other revisions
Guanglei (Huawei) accepts r12 + Cover Sheet 'summary of change' alignment: remove the bullet#3&4 and replace 'allowed' with 'dedicated' in bullet#2, objects other all reversions
Shabnam (Ericsson) can live with r12 if others are ok, provides comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.7 S2-2207402 CR Approval 23.256 CR0065R1 (Rel-17, 'F'): Clarifications on subscription control for UUAA-SM and C2 authorization Ericsson Rel-17 Revision of S2-2205901r12. Approved Agreed
8.7 S2-2206869 CR Approval 23.256 CR0066 (Rel-17, 'F'): Corrections to definition of transparent container Qualcomm Incorporated Rel-17 Noted Pallab (Nokia) comments that this CR depends on the outcome of LS OUT discussion
Guanglei (Huawei) comments
Shabnam (Ericsson) We have slightly different view and that is SMF is transparent but UAS NF/NEF is not, so we don't agree it is transparent to 3GPP system.
Pallab (Nokia) comments and objects to the CR
Guanglei (Huawei) provides CT1's intention
Pallab (Nokia) responds to Guanglei (Huawei)
Antoine (Orange) provides r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Pallab (Nokia) proposes to NOTE the CR
Antoine (Orange) replies to Pallab.
Pallab (Nokia) responds to Antoine (Orange)
Antoine (Orange) responds.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.7 S2-2206887 CR Approval 23.256 CR0067 (Rel-17, 'F'): Correction on reference on UAV re-authentication procedure in 5GS Qualcomm Incorporated Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=19 -
8.8 - - - LS for information - - Docs:=3 -
8.8 S2-2205408 LS In Information LS from CT WG1: LS on name of the interface for usage information collection CT WG1 (C1-224296) Rel-17 Noted Steve (Huawei) Proposes to note
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.8 S2-2205457 LS In Information Reply LS on name of the interface for usage information collection SA WG5 (S5-224463) Rel-17 Noted Steve (Huawei) Proposes to note
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.8 S2-2205419 LS In Information LS from TSG CT: LS on CT specification on Control Plane based security procedures for 5G ProSe UE-to-Network Relay TSG CT (CP-221322) Rel-17 Noted Steve (Huawei) Proposes to note
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.8 - - - SDU type - - Docs:=3 -
8.8 S2-2205464 LS In Information LS from RAN WG2: Reply LS on SDU type used over user plane for NR PC5 reference point RAN WG2 (R2-2206597) Rel-17 Noted Guillaume (MediaTek Inc.) proposed the LS to be noted.
Steve (Huawei) agrees about noting.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.8 S2-2206186 CR Approval 23.304 CR0110 (Rel-17, 'F'): Clarification on PDCP SDU Types ZTE Rel-17 r03 agreed. Revised to S2-2207403. Guillaume (MediaTek Inc.) provides r01
Judy (Ericsson) provides r02
Deng Qiang (CATT) why RAN and CN box are ticked?
Hao (ZTE) responds and provides r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Judy (Ericsson) is fine with r03
Guillaume (MediaTek Inc.): ok with r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.8 S2-2207403 CR Approval 23.304 CR0110R1 (Rel-17, 'F'): Clarification on PDCP SDU Types ZTE Rel-17 Revision of S2-2206186r03. Approved Agreed
8.8 - - - Discovery cast type - - Docs:=4 -
8.8 S2-2205424 LS In Action LS from RAN WG2: LS on Cast Type for Discovery message RAN WG2 (R2-2206391) Rel-17 Responses drafted in S2-2205994, S2-2206836. Postponed Postponed
8.8 S2-2205994 LS OUT Approval [DRAFT] Reply LS on Cast Type for Discovery message OPPO Rel-17 Response to S2-2205424. Noted Guillaume (MediaTek Inc.) provides r01.
Steve (Huawei) supports the LSout.
Hannu (Nokia) asks about the upper layer criteria to determine the cast type?
Sudeep (Apple) has the same question as Hannu(Nokia).
Hong (Qualcomm) objects the LS Out draft, and prefer to go with S2-2206836 as the baseline.
Fei (OPPO) responds to Hong (Qualcomm), Hannu (Nokia) and Sudeep (Apple)
Hong (Qualcomm) replies to Fei.
Deng Qiang (CATT) prefers not to introduce new cast type as RAN2 can resolve the issue by themselves.
Hong (Qualcomm) replies to Steve.
Steve (Huawei) comments on who knows what
Fei (OPPO) provides replies to Hong
Fei (OPPO) responds to Changhong (Intel)
Changhong (Intel) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.8 S2-2206836 LS OUT Approval [DRAFT] Reply LS on Cast Type for Discovery message Qualcomm Incorporated Rel-17 Response to S2-2205424. Noted Judy (Ericsson) comments
LaeYoung (LGE) provides r01.
Fei (OPPO) comments.
Guillaume (MediaTek Inc.) comments
Steve (Huawei) prefers providing the AS layer with the cast type and not to pursue this way.
Wen (vivo) prefers providing the AS layer with the cast type.
Hannu (Nokia) supports this LS unless the prose layer condition to select cast type is specified.
Sudeep (Apple) supports this LS and has a question to Judy (Ericsson).
Hong (Qualcomm) comments.
Fei (OPPO) responds to Hong (Qualcomm), Hannu (Nokia)
Hong (Qualcomm) replies to Fei.
Deng Qiang (CATT) supports the direction in this LS as also commented in 5994.
Fei (OPPO) provides r01.
Fei (OPPO) indicates the revision is provided for the CR S2-2205993.
Changhong (Intel) comments and supports the LS OUT proposed by Qualcomm.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Fei (OPPO) objects r00 and r01.
Judy (Ericsson) comments and can live with this LS out
LaeYoung (LGE) clarifies that r01 was provided NOT from Fei (OPPO) But from LaeYoung (LGE).
Hannu (Nokia) still supports r01 even though LaeYoung admits having written it ??
Fei (OPPO) replied to Hannu.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Sudeep (Apple) responds to Judy (Ericsson).
Noted
8.8 S2-2205993 CR Approval 23.304 CR0108 (Rel-17, 'F'): Cast Type for Discovery message OPPO Rel-17 Noted Guillaume (MediaTek Inc.) supports the CR
Judy (Ericsson) also support this CR.
Steve (Huawei) supports the CR.
Hannu (Nokia) asks what is the ProSe layer criteria to indicate the cast type?
Hong (Qualcomm) OBJECTs this CR and propose to NOTE it.
Guillaume (MediaTek Inc.) responds to Hong (Qualcomm) and recommends CC#2 discussion.
Hong (Qualcomm) replies to Guillaume.
Fei (OPPO) replied to Hong (Qualcomm)
Fei (OPPO) provides r01.
Sudeep (Apple) comments that r01 does not solve the issue.
Hannu (Nokia) shares the concerns from Hong and Sudeep.
Changhong (Intel) doesn't think the CR is needed.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.8 - - - CP based security procedure - - Docs:=4 -
8.8 S2-2205808 CR Approval 23.304 CR0107 (Rel-17, 'F'): CP and UP-based security procedures for 5G ProSe UE-to-Network Relay Ericsson Rel-17 CC#3: r08 + changes agreed. Revised to S2-2207690. Judy (Ericsson) responds to Myungjune (LGE)
Myungjune (LGE) responds to Judy (Ericsson).
Judy (Ericsson) responds to Myungjune (LGE).
Myungjune (LGE) asks question.
Judy (Ericsson) Fei (OPPO) and Wen(vivo)
Wen(vivo) shares similar view with Fei (OPPO).
Fei (OPPO) comments.
Judy (Ericsson) provides r01
Guillaume (Mediatek Inc.): this CR is not FASMO.
Judy (Ericsson) clarifies the FASMO aspects to Guillaume (Mediatek Inc.)
Steve (Huawei) comments CR is not needed.
Judy (Ericsson) responds to Steve (Huawei) and comments that Reason For Change justifies the FASMO aspects.
Hannu (Nokia) has concerns on late introduction of new requirements (such as the configuration)
Hong (Qualcomm) comments and propose to remove change #4.
Judy (Ericsson) provide r02, taking out the new parameters.
Steve (Huawei) 2 questions/comment on r02
Steve (Huawei) expands point 3)
Guillaume (MediaTek Inc.) comments and provides r03.
Judy (Ericsson) comments on r03
Guillaume (MediaTek Inc.) replies to Judy (Ericsson)
Judy (Ericsson) provides r04
Guillaume (MediaTek Inc.): ok with r04 (with clean-up)
Steve (Huawei) provides r05
Steve (Huawei) provides r07
Judy (Ericsson) provides r06
Judy (Ericsson) provides r08
Sherry (Xiaomi) provides r09.
Antoine (Orange) comments.
Judy (Ericsson) comments on r09.
Steve (Huawei) comments on the note
Fei (OPPO) comments on r09
Hannu (Nokia) proposes to agree r08 instead of r09.
Antoine (Orange) comments on r08.
Judy (Ericsson) provides r10 based on r08 to address Antoine's comment on which entity decides CP or UP-based security procedure.
Steve (Huawei) no justification for the parameter
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Sherry (Xiaomi) replies.
Sherry (Xiaomi) replies to Judy.
Sherry (Xiaomi) replies to Steve.
Sherry (Xiaomi) replies to Fei.
Sherry (Xiaomi) comments.
Sherry (Xiaomi) comments on r10.
Tao(VC) let's check whether r08 agreeable or not
Fei (OPPO) responds to Judy
Judy (Ericsson): Fei (OPPO), please clarify how to address the question without the network preference parameter
Fei (OPPO) comments on r10 and can not accept r10.
Fei (OPPO) replies to Sherry.
Steve (Huawei) objects to original, r01, r02, r03, r04, r05, r06, r09, r10. Can live with r07, r08.
Sherry (Xiaomi) objects to all revisions and r00.
Fei (OPPO) comments that this is r08+ based on r08 and the changes in clause 5.1.4.3.2 are taken out from r08.
Steve (Huawei) The numbering here is very confusing - we already have an r09 and this adds 'post DL-r09' with the same zip name. Give it a non-clashing number at least.
Judy (Ericsson) comments that the NOTE Sherry is objecting to is not in the scope of r07/r08. A post DL-r09 based on r08 is provided in draft folder for CC#3 check.
Judy (Ericsson) corrects: r11_postDL = r08 + removes change in clause 5.1.4.3.1
Hannu (Nokia) asks whether we should postpone this document?
Judy (Ericsson) propose to proceed with r11_post DL as it is essential to correct the fault that RSC w/o CPSI is ruled out.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Steve (Huawei) For the CR not to be noted, I guess we are going to CC#3. Maybe some other parts are not right as well,
Revised
8.8 S2-2207690 CR Approval 23.304 CR0107R1 (Rel-17, 'F'): CP and UP-based security procedures for 5G ProSe UE-to-Network Relay Ericsson Rel-17 CC#3: Revision of S2-2205808r08 + changes. This CR was agreed. Approved. A newCR to 23.247 CR0133 was created in S2-2207689 Agreed
8.8 S2-2206824 CR Approval 23.304 CR0114 (Rel-18, 'F'): Updates to Policy/Parameter provisioning for CP authentication and authorisation Xiaomi Rel-18 r04 agreed. Revised to S2-2207404. Wen (vivo) comments.
Judy (Ericsson) comments.
Fei (OPPO) proposes to note this CR.
Steve (Huawei) comments
Sherry (Xiaomi) replies to Fei.
Sherry (Xiaomi) replies to Wen.
Sherry (Xiaomi) replies to Steve.
Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) comments.
Fei (OPPO) comments on r01.
Jung Je (Interdigital) propose to note this CR
Steve (Huawei) provides r02, some parts are good in the CR, let's keep those.
Deng Qiang (CATT) supports r03.
Judy (Ericsson) provides r03
Jung Je (Interdigital) comments.
Steve (Huawei) we can make this more concise, and may be is maybe not correct.
Steve (Huawei) on the optional
Judy (Ericsson): Steve (Huawei)'s further improvement looks good to me
Fei (OPPO) comments.
Steve (Huawei) provides r04 with the changes discussed.
Steve (Huawei) confirms both places
Sherry (Xiaomi) provides r05.
Sherry (Xiaomi) provides r06.
Fei (OPPO) provides comment.
Steve (Huawei) comments on use
Judy (Ericsson) is on the same page as Steve (Huawei).
Sherry (Xiaomi) fully agree with what Steve says.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Sherry (Xiaomi) replies to Judy.
Jung Je(Interdigital) replies to Sherry(Xiaomi)
Judy (Ericsson) accepts r03/r04, objects to other revisions including r00.
Fei (OPPO) replied to Sherry and Steve.
Steve (Huawei) is ok with r03/r04, prefers r04
Sherry (Xiaomi) can accept r03,r04, r05, r06.
Jung Je (Interdigital) is OK with r04.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.8 S2-2207404 CR Approval 23.304 CR0114R1 (Rel-18, 'F'): Updates to Policy/Parameter provisioning for CP authentication and authorisation Xiaomi Rel-18 Revision of S2-2206824r04. Approved Agreed
8.8 - - - others - - Docs:=5 -
8.8 S2-2206011 CR Approval 23.304 CR0109 (Rel-17, 'F'): Supporting multiple PDU sessions over a L2 link between L2 remote UE and L2 U2N relay UE ASUSTeK Rel-17 r05 agreed. Revised to S2-2207405. Wen (vivo) comments.
Fei (OPPO) comments and proposes to note this CR.
Lider (ASUSTeK) replies to OPPO and vivo.
Fei (OPPO) provides comments.
Lider (ASUSTeK) provides r01.
Wen (vivo) is ok with r01.
Zhang (Ericsson) provides comment
Steve (Huawei) provides r02, but not entirely sure there is a need.
Lider (ASUSTeK) is fine with r02.
Hong (Qualcomm) comments and don't think the CR is needed.
Lider (ASUSTeK) replies to Qualcomm.
Guillaume (MediaTek Inc.): ok with r02
Lider (ASUSTeK) provides r03.
Judy (Ericsson) comments on r04
Lider (ASUSTeK) provides r04 and comments.
Deng Qiang (CATT) comments.
Hong (Qualcomm) comments.
Judy (Ericsson) comments.
Lider (ASUSTeK) provides r05.
Steve (Huawei) comments on title change
Judy (Ericsson) responds to Steve (Huawei)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Steve (Huawei) is ok with r05
Judy (Ericsson) is fine with r05
Fei (OPPO) is fine with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.8 S2-2207405 CR Approval 23.304 CR0109R1 (Rel-17, 'F'): Supporting multiple PDU sessions over a L2 link between L2 remote UE and L2 U2N relay UE ASUSTeK Rel-17 Revision of S2-2206011r05. Approved Agreed
8.8 S2-2206346 CR Approval 23.304 CR0111 (Rel-17, 'F'): SL DRX for L2 U2N Relay MediaTek Inc., Apple, CATT, Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, Sony, ZTE Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.8 S2-2206627 CR Approval 23.304 CR0112 (Rel-17, 'F'): Correction on 5G ProSe Policy Provisioning Huawei, HiSilicon Rel-17 Postponed Judy (Ericsson) comments
Judy (Ericsson) proposes to postpone this paper as the update depends on the ongoing CT1 discussion.
Steve (Huawei) We can postpone and come back if there is no conclusion in CT1 by our deadline today.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.8 S2-2206628 CR Approval 23.304 CR0113 (Rel-17, 'F'): Update NEF functionality to support Npc2 reference point Huawei, HiSilicon Rel-17 Noted Guanglei (Huawei) replies to Judy (Ericsson).
Judy (Ericsson) comments and propose to note this paper.
Judy (Ericsson) responds to Guanglei (Huawei)
Guanglei (Huawei) replies to Judy (Ericsson) and provides SA3 TS 33.503 reference.
Deng Qiang (CATT) comments SA3 should follow SA2 architecture design.
Guanglei (Huawei) replies to Judy (Ericsson) and DengQiang (CATT).
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Judy (Ericsson) propose to NOTE this paper as no action in SA2 is expected.
Guanglei (Huawei) is fine to postpone
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=49 -
8.9 - - - LS related to N5 - - Docs:=4 -
8.9 S2-2205445 LS In Action LS from SA WG6: LS on N5 clarification for MBS usage SA WG6 (S6-221440) Rel-18 Responses drafted in S2-2205950, S2-2206078. Final response in S2-2207406 Replied to
8.9 S2-2205950 LS OUT Approval [DRAFT] Reply LS on N5 clarification for MBS usage Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2207406, merging S2-2206078. LiMeng (Huawei) provides r01
Robbie (Ericsson) asks which one will be selected as basis? 5950 or 6078?
LiMeng (Huawei) provides r02
LiMeng (Huawei) clarifies r02 is from Thomas (Nokia), but is fine with r02.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Robbie (Ericsson) is fine with r02, just wonders whether Rel-17 should be included in the Release field, and whether MCOver5MBS should be included in Work Item field.
LiMeng (Huawei) considers we may keep Rel-18 only in the LS to SA6.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207406 LS OUT Approval LS on N5 clarification for MBS usage SA WG2 Rel-17 Revision of S2-2205950r02, merging S2-2206078. Approved Approved
8.9 S2-2206078 LS OUT Approval [DRAFT] Reply LS on N5 clarification for MBS usage Huawei, HiSilicon Rel-18 Response to S2-2205445. Merged into S2-2207406 LiMeng (Huawei) proposes to merge this document into S2-2205950.
LiMeng (Huawei) considers both are fine since they are similar in principle.
Robbie (Ericsson) asks which one will be selected as basis? 5950 or 6078?
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 - - - UE pre-configuration - - Docs:=3 -
8.9 S2-2205758 LS OUT Approval [DRAFT] Reply LS on parameters preconfigured in the UE to receive MBS service Qualcomm Rel-17 Response to S2-2205394. CC#3: Noted Thomas (Nokia) provides r01
Haris(Qualcomm) indicates the problem and objects to r01
Shabnam (Ericsson) added the title of the document to the email. I believe what we are discussing is related to Q2, and that leads to addressing the use as well as parameters that are required from stage 2.
Haris(Qualcomm) responds
Thomas(Nokia) replies to Haris(Qualcomm)
Thomas(Nokia) replies to Haris(Qualcomm) and objects to r00
Asks Haris to reconsider objection against r01 or provide improved text
LiMeng (Huawei) comments and object to the LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Thomas (Nokia) provides r02
==== 9.X, 10.X Revisions Deadline ====
Noted
8.9 S2-2205757 CR Approval 23.247 CR0100R3 (Rel-17, 'F'): Need for pre-configured USD and service announcement Qualcomm Incorporated, Ericsson, Deutsche Telekom, AT&T, Orange Rel-17 Revision of (Postponed) of S2-2204319. CC#3: Noted Thomas (Nokia) provides r01
Haris(Qualcomm) objects to r01
LiMeng (Huawei) comments that the LS from CT plenary is asking what parameters should be pre-configured, which has nothing to do with Rel-17 scope.
Agrees with Thomas we should focusing on the questions from CT.
Antoine (Orange): It's a good idea to base the WF on the Rel-17 scope. Otherwise there is no longer any need to agree WIDs, neither to set Release freeze dates.
Shabnam (Ericsson) Agree with Thomas that we need to find a way forward, and I think such approach needs to be based on the scope of Rel-17 we agreed upon and receiving data/service without network interaction was taken out of scope. r01 we cannot accept.
Thomas (Nokia) provides r02
Antoine (Orange) The LS from CT highlighted some ambiguous text in the TS, that can be interpreted in a way that goes beyond the approved Rel-17 scope. Since the scope of a Release is not captured in specifications, this text in the TS has to be corrected.
LiMeng (Huawei) replies.
Haris(Qualcomm) responds
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
LiMeng (Huawei) comments that we will determine the way forward in CC#3 instead of approve any versions before.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.9 S2-2206089 CR Approval 23.247 CR0128 (Rel-17, 'F'): Pre-configured USD and service announcement Huawei, HiSilicon, ZTE, CATT, CBN Rel-17 CC#3: Noted Thomas (Nokia) provides r01
Haris(Qualcomm) object to r0 and r01
Thomas (Nokia) provides r02 as compromise proposal
Shabnam (Ericsson) objects to r0, r01 as adds new function to a frozen release feature outside of the scope of the original work scope.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
LiMeng (Huawei) comments that we will determine the way forward in CC#3 instead of approve any versions before.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.9 - - - LS related to RAN3 outstanding issues - - Docs:=3 -
8.9 S2-2205395 LS In Action LS from RAN WG3: LS on further outstanding issues in TS 23.247 RAN WG3 (R3-222867) Rel-17 Revision of postponed S2-2203635 from S2#151E. Response drafted in S2-2206525. Final response in S2-2207389 Replied to
8.9 S2-2206525 LS OUT Approval [DRAFT] Response LS on further outstanding issues in TS 23.247 Huawei, HiSilicon Rel-17 Response to S2-2205395. r00 agreed. Revised to S2-2207389.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207389 LS OUT Approval [DRAFT] Response LS on further outstanding issues in TS 23.247 Huawei, HiSilicon Rel-17 Revision of S2-2206525r00. Approved Approved
8.9 - - - MBS PCC - - Docs:=10 -
8.9 S2-2205398 LS In Action LS from CT WG3: Questions on PCC aspects related to 5MBS CT WG3 (C3-222578) Rel-17 Revision of postponed S2-2203646 from S2#151E. Responses drafted in S2-2205835, S2-2205897, S2-2206050. Final response in S2-2207407 Replied to
8.9 S2-2205835 LS OUT Approval [DRAFT] Reply to LS on PCC aspects related to 5MBS Ericsson Rel-17 Response to S2-2205398. Merged into S2-2207407 Judy (Ericsson) proposes to discuss the LS out in 6050 thread
Judy (Ericsson): Thomas' merging proposal in 5897 reminds that this paper can also be considered as merged to 6050
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2205897 LS OUT Approval [DRAFT] Reply LS on Questions on PCC aspects related to 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) of S2-2203968. Response to S2-2205398. Merged into S2-2207407 Judy (Ericsson) proposes to discuss on 6050 thread
Thomas(Nokia) suggest to consider this LS as merged into S2-2206050
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2206050 LS OUT Approval [DRAFT] Response to LS on Questions on PCC aspects related to 5MBS Huawei, HiSilicon Rel-17 Response to S2-2205398. r02 agreed. Revised to S2-2207407, merging S2-2205835 and S2-2205897. Judy (Ericsson) propose to use this thread to discuss the LS out
Thomas (Nokia) provides r01
Judy (Ericsson) provides r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207407 LS OUT Approval Response to LS on Questions on PCC aspects related to 5MBS SA WG2 Rel-17 Revision of S2-2206050r02, merging S2-2205835 and S2-2205897. Approved Approved
8.9 S2-2205834 DISCUSSION Agreement Discussion on Questions on PCC aspects related to 5MBS Ericsson Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.9 S2-2205836 CR Approval 23.247 CR0125 (Rel-17, 'F'): Update of PCC procedure for 5MBS Ericsson Rel-17 Merged into S2-2207408 Judy (Ericsson) comments this paper will be NOTED as the related discussion is in 6049
Judy (Ericsson): Thomas' merging proposal in 5896 reminds that this paper should also be considered as merged to 6049
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2205896 CR Approval 23.247 CR0118R1 (Rel-17, 'F'): Corrections related to PCC aspects related to 5MBS Nokia, Nokia Shanghai-Bell Rel-17 Revision of (Postponed) of S2-2203969. Merged into S2-2207408 Judy (Ericsson) assume this paper will be NOTED as the related discussion is in 6049
Thomas(Nokia) suggests to consider this merged into S2-2206049
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2206049 CR Approval 23.247 CR0109R3 (Rel-17, 'F'): Update of PCC procedure for 5MBS Huawei, HiSilicon Rel-17 r08 agreed. Revised to S2-2207408, merging S2-2205836 and S2-2205896. Thomas (Nokia) provides r01
Judy (Ericsson) provides r02
Thomas (Nokia) provides r03 and objects against r02
Thomas (Nokia) provides r04
Mirko (Huawei) provides r05
Judy (Ericsson) provide r06, UDR interaction included as a compromise for the sake of progress.
Judy (Ericsson) provides r08 with the only change of removing text in 'other comments' in cover sheet
Thomas (Nokia) provides r07
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207408 CR Approval 23.247 CR0109R4 (Rel-17, 'F'): Update of PCC procedure for 5MBS Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson, ZTE Rel-17 Revision of S2-2206049r08, merging S2-2205836 and S2-2205896. Approved Agreed
8.9 - - - LS related to AS-NAS interaction - - Docs:=4 -
8.9 S2-2205426 LS In Information LS from RAN WG2: LS on AS-NAS layer interactions for MBS RAN WG2 (R2-2206609) Rel-17 Responses drafted in S2-2205604, S2-2206077. Final response in S2-2207409 Robbie (Ericsson) replies to Thomas (Nokia)
Thomas (Nokia) provides comment
Thomas (Nokia) replies to Robbie (Ericsson)
Robbie (Ericsson) asks Thomas (Nokia)
Robbie (Ericsson) provides comments to Thomas (Nokia)
Miguel (Qualcomm) comments
Fenqin (Huawei) comments
Robbie (Ericsson) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Replied to
8.9 S2-2205604 LS OUT Approval [DRAFT] Reply LS on AS-NAS layer interactions for MBS Ericsson Rel-17 Response to S2-2205426. Merged into S2-2207409 Robbie (Ericsson) suggests discussing in S2-2205426 thread.
Robbie (Ericsson) merges it in S2-2206077.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2206077 LS OUT Approval [DRAFT] LS response to RAN WG2 regarding AS-NAS layer interactions Huawei, HiSilicon Rel-17 r13 agreed. Revised to S2-2207409, merging S2-2205604. Thomas(Nokia) provides r01
But agrees to focus discussion in S2-2205426 thread.
Robbie (Ericsson) suggests discussing in S2-2205426 thread.
Fenqin (Huawei) provides r02
Robbie (Ericsson) provides r03, merged in S2-2205604
Thomas (Nokia) comments against r02
zhendong (ZTE) comments
Fenqin (Huawei) provides comments and provides r07.
Robbie(Ericsson) provides r06, objects against r05, r01, r00.
Thomas (Nokia) also objects against r03
Thomas(Nokia) Provides r05, objects against r04
Fenqin(Huawei) Provide r04
Robbie (Ericsson) comments
Thomas(Nokia) objects against r06, r03, r04
Replies to Robbie
Robbie (Ericsson) replies to Thomas(Nokia)
Fenqin (Huawei) provides feedback
Thomas(Nokia) Provides r08 that is the result of some offline discussions
Robbie (Ericsson) asks Thomas(Nokia) to upload a new revision, r08 is empty
Thomas(Nokia) Provides r09
Fenqin (Huawei) is ok with r09
Robbie (Ericsson) provides r10
Miguel (Qualcomm) provides r12 and r13 prefers r13
Thomas (Nokia) provides r11
Fenqin (Huawei) is ok with R10
Thomas(Nokia) replies to Robbie
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Thomas(Nokia) suggests agreeing r10
Thomas(Nokia) proposes to move forward with r13
zhendong (ZTE) is fine with r13
Thomas(Nokia) comments it was Miguel(Qualcomm) who really proposed moving forward with r13.
But Thomas can agree r13
Fenqin (Huawei) We are also fine with r13
Robbie (Ericsson) prefers r13.
Miguel(Qualcomm) ratifies error in Comment for notes, it was Miguel (Qualcomm) and not Thomas (Nokia) that proposed to move forward with r13
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207409 LS OUT Approval [DRAFT] LS response to RAN WG2 regarding AS-NAS layer interactions Huawei, HiSilicon Rel-17 Revision of S2-2206077r13, merging S2-2205604. Approved Approved
8.9 - - - LS related to MBS User service - - Docs:=6 -
8.9 S2-2205463 LS In Information LS from SA WG4: Reply LS on 5MBS User Services SA WG4 (S4-220829) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 S2-2205450 LS In Action LS from SA WG4: Reply LS on 5MBS User Services SA WG4 (S4-220828) Rel-17 Responses drafted in S2-2205605, S2-2206205. Postponed Postponed
8.9 S2-2205605 LS OUT Approval [DRAFT] Reply LS on 5MBS User Services Ericsson Rel-17 Response to S2-2205450. Postponed Robbie (Ericsson) provides r01, merges in S2-2206205
Robbie (Ericsson) comments
LiMeng (Huawei) replies to Zhendong
zhendong (ZTE) comments
LiMeng (Huawei) considers that the LS should be checked together with the CR S2-2206206.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
LiMeng (Huawei) suggests to postpone this LS out.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.9 S2-2206205 LS OUT Approval [DRAFT] Reply LS on 5MBS User Services ZTE Rel-17 Response to S2-2205450. merged into S2-2206206 (Postponed) Robbie (Ericsson) suggests to merge it to S2-2205605
zhendong (ZTE) is fine with merge proposal
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.9 S2-2205606 CR Approval 23.247 CR0123 (Rel-17, 'F'): Clarification on interworking at reference point of MB2 Ericsson Rel-17 Merged into S2-2206206 (Postponed). Postponed Robbie (Ericsson) merges it to S2-2206206
Robbie (Ericsson) comments it has been merged to S2-2206206
Thomas (Nokia) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.9 S2-2206206 CR Approval 23.247 CR0129 (Rel-17, 'F'): Clarification on the traffic handling in MBSTF for interworking ZTE Rel-17 Postponed Robbie (Ericsson) merges S2-2205606 in, provides r01.
Miguel (Qualcomm) provides r02
Robbie (Ericsson) replies to LiMeng (Huawei).
LiMeng (Huawei) comments to the original version and revisions.
LiMeng (Huawei) replies
zhendong (ZTE) provides the comments
LiMeng (Huawei) further clarifies the questions.
Thomas(Nokia) is fine with r02 and agrees with Miguel and Robbie.
Provides extra information for MB2 interworking for Limeng
Miguel (Qualcomm) agrees with Robbie's response
LiMeng (Huawei) further clarifies.
Robbie (Ericsson) provides comments.
LiMeng (Huawei) further provides comments.
zhendong (ZTE) comments
LiMeng (Huawei) comments and replies to Zhendong and Robbie.
Thomas(Nokia) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Miguel (Qualcomm) asks question to LiMeng
LiMeng (Huawei) further responds to Zhendong (ZTE) and Robbie (Ericsson), suggest to postpone t the related documents.
Robbie (Ericsson) shares Zhendong's view, and replies to LiMeng (Huawei).
zhendong (ZTE) respond to li meng
LiMeng (Huawei) replies to Robbie (Ericsson) and Zhendong (ZTE), and comments.
Robbie (Ericsson) replies to LiMeng (Huawei), comments that LiMeng's concerns can be resolved using MB2.
zhendong (ZTE) provides the response
LiMeng (Huawei) responds with Robbie, clarifies the scenario, and considers the proposed scenario cannot be really addressed by MB2.
Robbie (Ericsson) suggests LiMeng (Huawei) withdrawing his objection to 6206 which aligns with normative Annex C and clause 5.2 of TS 23.247.
LiMeng (Huawei) responds to Miguel and Robbie and disagrees the proposal of 6206.
Robbie (Ericsson) agrees with Zhendong (ZTE) and Thomas (Nokia) that geographical areas are not supported by MB2
zhendong (ZTE) agree with thomas, geographical areas are not supported by MB2
Thomas(Nokia) replies to Limeng, shares the views of Robbie and Zhendong
Thomas(Nokia) provides additional information about MB2 service areas to LiMeng
Thomas (Nokia) replies to LiMeng, asks LiMeng to reconsider objection
LiMeng (Huawei) replies to Thomas, Zhendong and Robbie, suggests to postpone the CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.9 - - - LS related to Security aspects - - Docs:=3 -
8.9 S2-2205466 LS In Information LS from SA WG3: Reply LS on Security architecture for 5G multicast/broadcast services SA WG3 (S3-221158) Rel-17 Response drafted in S2-2205759. Final response in S2-2207390 Replied to
8.9 S2-2205759 LS OUT Approval [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services Qualcomm Rel-17 Response to S2-2205466. r00 agreed. Revised to S2-2207390.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207390 LS OUT Approval Reply LS on Security architecture for 5G multicast/broadcast services SA WG2 Rel-17 Revision of S2-2205759r00. Approved Approved
8.9 - - - Other LSs - - Docs:=5 -
8.9 S2-2205403 LS In Information LS from CT WG4: LS on Clarification on MBS Security Keys CT WG4 (C4-223302) Rel-17 Revision of postponed S2-2203669 from S2#151E. Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 S2-2205415 LS In Information LS from CT WG4: LS on Support of Broadcast and Multicast MBS sessions with AMF Set CT WG4 (C4-223303) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 S2-2205449 LS In Information LS from SA WG4: Reply LS on the MBS broadcast service continuity and MBS session identification SA WG4 (S4-220827) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 S2-2205456 LS In Information LS from SA WG3: Reply LS on Clarification on MBS Security Keys SA WG3 (S3-221665) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 S2-2205469 LS In Information LS from SA WG3: Reply LS on Clarification on MBS Security Keys SA WG3 (S3-221262) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.9 - - - CRs - - Docs:=11 -
8.9 S2-2206076 CR Approval 23.247 CR0127 (Rel-17, 'F'): Corrections and improvement of TS 23.247 Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2207410, merging S2-2206208. Robbie (Ericsson) asks a question.
Robbie (Ericsson) provides r01, merges in S2-2206208.
Thomas (Nokia) provides r02.
LiMeng (Huawei) provides r03.
Robbie (Ericsson) provides r04.
Thomas (Nokia) provides r05.
LiMeng (Huawei) is fine with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Robbie (Ericsson) is fine with r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207410 CR Approval 23.247 CR0127R1 (Rel-17, 'F'): Corrections and improvement of TS 23.247 Huawei, HiSilicon Rel-17 Revision of S2-2206076r05, merging S2-2206208. Approved Agreed
8.9 S2-2205603 CR Approval 23.247 CR0122 (Rel-17, 'F'): MBS Session Status and broadcast MBS Session Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.9 S2-2205686 CR Approval 23.247 CR0124 (Rel-17, 'F'): Clarification on local multicast LG Electronics Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.9 S2-2205837 CR Approval 23.247 CR0126 (Rel-17, 'F'): Correction to MB-SMF update in NRF Ericsson Rel-17 r01 agreed. Revised to S2-2207411. Judy (Ericsson) provides r01, and prefers to handle this paper separately to avoid dependency with 6049 with already drastic changes.
Fenqin (Huawei) comments and suggest to merge this paper with 6049.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207411 CR Approval 23.247 CR0126R1 (Rel-17, 'F'): Correction to MB-SMF update in NRF Ericsson Rel-17 Revision of S2-2205837r01. Approved Agreed
8.9 S2-2206207 CR Approval 23.247 CR0130 (Rel-17, 'F'): Clarificaiton on the mobility in RRC inactive ZTE Rel-17 r14 agreed. Revised to S2-2207412. zhendong (ZTE) provides the response
Fenqin (Huawei) provide comments
Thomas (Nokia)
Judy (Ericsson) provides r02
Fenqin (Huawei) provide comments and r03
zhendong (ZTE) provides the r04
Miguel (Qualcomm) provides r05
Youngkyo(Samsung) provide a comment.
Fenqin (Huawei) responds
zhendong (ZTE) provides the wording proposal
Fenqin (Huawei) Provides r06
Judy (Ericsson) provides r12 to address Fenqin's offline comment.
Judy (Ericsson) provides r11
Fenqin (Huawei) responds to Judy (Ericsson)
Judy (Ericsson) asks Fenqin (Huawei) questions
Fenqin (Huawei) provides r10
Judy (Ericsson) provides r09
Youngkyo(Samsung) provides a comment
Thomas (Nokia) Provides r08
Thomas (Nokia) Provides r07 and clarifies that he also provided r01
Miguel (Qualcomm) provides r13
Judy (Ericsson) comments and provide r14
Thomas (Nokia) objects against r13
zhendong (ZTE) comments
Miguel (Qualcomm) responds
Judy (Ericsson) responds to Miguel (Qualcomm)
Miguel (Qualcomm) responds to Judy, not sure about r14
Thomas(Nokia) replies to Miguel
Miguel (Qualcomm) responds to Zhendong
zhendong (ZTE) provides response
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207412 CR Approval 23.247 CR0130R1 (Rel-17, 'F'): Clarificaiton on the mobility in RRC inactive ZTE Rel-17 Revision of S2-2206207r14. Approved Agreed
8.9 S2-2206208 CR Approval 23.247 CR0131 (Rel-17, 'F'): Clarification on the MBS Broadcast ZTE Rel-17 Merged into S2-2207410 Robbie (Ericsson) provides comments
zhendong (ZTE) provides response
Robbie (Ericsson) merges it to S2-2206076
zhendong (ZTE) is fine with the merge proposal
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.9 S2-2206209 CR Approval 23.247 CR0132 (Rel-17, 'F'): Removing the EN on the HO ZTE Rel-17 r02 agreed. Revised to S2-2207413. Judy (Ericsson) provides r01
Thomas (Nokia) provides r03
Thomas (Nokia) provides r02
Fenqin(Huawei) provides comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Fenqin(Huawei) suggest to go r02.
Fenqin (Huawei) accept only r00 or r02, object r01 &r03.
Judy (Ericsson) proposed to go for r01 or r02, which are actually the same, objects to r00 &r03.
zhendong (ZTE) prefer r02
Thomas(Nokia) objects against r01, suggests r02
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.9 S2-2207413 CR Approval 23.247 CR0132R1 (Rel-17, 'F'): Removing the EN on the HO ZTE Rel-17 Revision of S2-2206209r02. Approved Agreed
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=5 -
8.10 S2-2205428 LS In Information LS from RAN WG2: LS on NAS busy indication in RRC_INACTIVE RAN WG2 (R2-2206837) Rel-17 Response drafted in S2-2206771. Final response in S2-2207029 Replied to
8.10 S2-2206771 LS OUT Approval [DRAFT] Reply LS on NAS busy indication in RRC_INACTIVE Samsung Response to S2-2205428. r00 agreed. Revised to S2-2207029.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.10 S2-2207029 LS OUT Approval [DRAFT] Reply LS on NAS busy indication in RRC_INACTIVE Samsung - Revision of S2-2206771r00. Approved Approved
8.10 S2-2206775 CR Approval 23.501 CR3698 (Rel-17, 'F'): Clarification related to Inactive state Samsung Rel-17 r01 agreed. Revised to S2-2207030. Guillaume (MediaTek Inc.) provides r01
Saso (Intel) comments that there is a corresponding CT1 CR in C1-224815.
Lalith(Samsung) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Lalith(Samsung) is ok with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.10 S2-2207030 CR Approval 23.501 CR3698R1 (Rel-17, 'F'): Clarification related to Inactive state Samsung Rel-17 Revision of S2-2206775r01. Approved Agreed
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=6 -
8.11 S2-2205427 LS In Information LS from RAN WG2: Reply LS on NR satellite RAT type in UE NAS RAN WG2 (R2-2206664) Rel-17 Noted DongYeon (Samsung) proposes that this LS can be noted.
Steve (Huawei) similar view, can be noted.
Jean Yves (Thales) ok to note this LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.11 S2-2205434 LS In Information LS from SA WG1: Reply LS on Emergency services and UE rejected with PLMN not allowed to operate in the country of the UE s location SA WG1 (S1-221290) Rel-17 Noted Steve (Huawei) Proposes to note.
Jean Yves (Thales) ok to note this LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.11 S2-2206262 CR Approval 23.501 CR3687 (Rel-17, 'F'): AMF sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2207031. DongYeon (Samsung) asks questions for clarification.
Steve (Huawei) comments, provides r01
Guillaume (MediaTek Inc.) supports the proposal
Chris (Vodafone) comments
Hannu (Nokia) agrees with the comments and provides r02.
Steve (Huawei) is ok with r02
Stefan (Ericsson) provides r03
DongYeon (Samsung) provides r04.
Steve (Huawei) is ok with r04
Hannu (Nokia) supports the latest revision r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Stephen (Qualcomm) can also agree the r04
Jean Yves (Thales) ok with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.11 S2-2207031 CR Approval 23.501 CR3687R1 (Rel-17, 'F'): AMF sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 Revision of S2-2206262r04. Approved Agreed
8.11 S2-2206263 CR Approval 23.502 CR3535 (Rel-17, 'F'): AMF sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2207032. Steve (Huawei) provides r01.
Steve (Huawei) provides r02
DongYeon (Samsung) provides r03.
Steve (Huawei) is ok with r03
Hannu (Nokia) is not sure if we skipped some revision here, but r03 seems fine.
Steve (Huawei) comments on no skip
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Stephen (Qualcomm) can also agree the r03
DongYeon (Samsung) comments, there is no skip.
Jean Yves (Thales) ok with r03
Guillaume (MediaTek Inc.) ok with r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.11 S2-2207032 CR Approval 23.502 CR3535R1 (Rel-17, 'F'): AMF sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 Revision of S2-2206263r03. Approved Agreed
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=9 -
8.12 S2-2205422 LS In Action LS from RAN WG2: Reply LS to SA WG2 on Tx Profile RAN WG2 (R2-2206299) Rel-17 Responses drafted in S2-2206362, S2-2206381. Final response in S2-2207033 Replied to
8.12 S2-2206362 LS OUT Approval [DRAFT] Reply LS to RAN WG2 on Tx profile vivo Rel-17 r03 agreed. Revised to S2-2207033, merging S2-2206381. Wen (vivo) provides r01.
Fei (OPPO) asks questions.
Wen (vivo) replies to Fei.
Wen (vivo) provides r02.
LaeYoung (LGE) thinks r02 is simpler and works. :)
Wen (vivo): thanks for LaeYoung (LGE) 's reminder and confirmation . :)
Fei (OPPO) comment on r02.
Wen (vivo) provides r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
LaeYoung (LGE) is OK with r03.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.12 S2-2207033 LS OUT Approval [DRAFT] Reply LS to RAN WG2 on Tx profile vivo Rel-17 Revision of S2-2206362r02, merging S2-2206381. Approved Approved
8.12 S2-2206381 LS OUT Approval [DRAFT] LS out to RAN WG2 on Tx Profile Huawei, HiSilicon Rel-17 Response to S2-2205422. Merged into S2-2207033 LaeYoung (LGE) proposes to take S2-2206362 (vivo) as reply LS and to Merge this draft LS to 6362 or NOTE this draft LS.
Mehrdad (Mediatek Inc.) also suggests to use S2-2206362 (vivo) as the baseline.
LiMeng (Huawei) agrees to use S2-2206362 as the reply basis and mark this LS as merged into S2-2206362.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.12 S2-2205555 CR Approval 23.287 CR0181 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, vivo, Qualcomm Incorporated Rel-17 r05 agreed. Revised to S2-2207034, merging S2-2206110. LaeYoung (LGE) provides r02.
Fei (OPPO) comments and provides r01.
Wen (vivo) provides r03.
LaeYoung (LGE) provides r04.
Fei (OPPO) comments on r04.
LaeYoung (LGE) provides r05.
LiMeng (Huawei) asks for clarification.
Wen (vivo) tries to reply to LiMeng (Huawei).
LaeYoung (LGE) replies to LiMeng (Huawei).
LiMeng (Huawei) thanks to the answer from Wen and LaeYoung, and asks further questions.
LaeYoung (LGE) responds to LiMeng (Huawei).
Wen (vivo) responds to LiMeng (Huawei).
LaeYoung (LGE) provides comment and clarifies that LiMeng (Huawei) used incorrect file names, i.e. S2-2206382r06/r07 instead of S2-2205555r06/07 when providing r06 and r07.
Wen (vivo) comments on r06 and r07.
LiMeng (Huawei) further responds to Wen (vivo) and LaeYoung (LGE). And provides r06 and r07.
LiMeng (Huawei) corrects the link of r06 and r07.
LaeYoung (LGE) cannot accept r06 and r07 because the proposals in r06/r07 break principles and agreements made by SA2 and RAN2.
Mehrdad (Mediatek Inc.) comments on r07
Mehrdad (Mediatek Inc.) thinks the same issue as r07 is relevant for r06 as well.
Fei (OPPO) also has concern on V2X layer generating non DRX Tx profiles to AS layer in r06 and r07.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
LaeYoung (LGE) thanks to LiMeng (Huawei) and provides answer.
LiMeng (Huawei) can live with r05 for the sake of progress.
Mehrdad (Mediatek Inc.) is OK with r05 and would like to co-sign the CR based on r05.
Cai Simon (Nokia) agrees with Mehrdad (Mediatek Inc.) and LiMeng (Huawei)
LaeYoung (LGE) thanks co-sign from Mehrdad (Mediatek Inc.).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.12 S2-2207034 CR Approval 23.287 CR0181R1 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, vivo, Qualcomm Incorporated Rel-17 Revision of S2-2205555r05, merging S2-2206110. Approved Agreed
8.12 S2-2206110 CR Approval 23.287 CR0182 (Rel-17, 'F'): Clarifications on Tx profiles for default SL DRX OPPO Rel-17 Merged into S2-2207034 Wen (vivo) comments.
LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) responds to LaeYoung (LGE)
LaeYoung (LGE) proposes to merge this CR to S2-2205555 and provides comment.
Mehrdad (Mediatek Inc.) suggests to merge this CR into S2-2205555
Fei (OPPO) responds to Wen (vivo) and LaeYoung (LGE).
Fei (OPPO) would be ok to use 5555 as basis for discussion.
LaeYoung (LGE) asks Fei to confirm about merging this CR into 5555.
Fei (OPPO) is ok to mark this as merged or noted.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.12 S2-2206361 DISCUSSION Discussion Discussion on Tx profile Vivo Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.12 S2-2206382 CR Approval 23.287 CR0183 (Rel-17, 'F'): Clarification on Tx profile Huawei, HiSilicon Rel-17 Noted Wen (vivo) comments.
LaeYoung (LGE) asks a Q.
LiMeng (Huawei) replies.
LaeYoung (LGE) responds to LiMeng (Huawei).
Mehrdad (Mediatek Inc.) agrees with LGE and suggests to use 0555 as the baseline.
LaeYoung (LGE) proposes to NOTE this CR.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
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:=7 -
8.14 S2-2205423 LS In Information LS from RAN WG2: LS on GNSS integrity RAN WG2 (R2-2206389) Rel-17 Response drafted in S2-2206744. CC#3: Final response in S2-2207691 Replied to
8.14 S2-2206744 LS OUT Approval [DRAFT] LS response on GNSS integrity Huawei Rel-17 Response to S2-2205423. CC#3: r01 agreed. Revised to S2-2207691. Yunjing (CATT) provides comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Stephen (Qualcomm) provides comments
Runze (Huawei) relies to Stephen, and suggest to approve r00.
Leo (Deutsche Telekom) only can accept the LS when text updates proposed below are included, objects to the original version of the LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Runze (Huawei) provides r01, for CC#3 discussion.
Leo (Deutsche Telekom) provides comments on r01.
Runze (Huawei) replies to Leo (Deutsche Telekom) provides r02 on the CC#3 folder.
Revised
8.14 S2-2207691 LS OUT Approval LS response on GNSS integrity Huawei Rel-17 Revision of S2-2206744r01. This LS OUT was approved Approved
8.14 S2-2206502 CR Approval 23.273 CR0231 (Rel-17, 'F'): Clarification and correction on country verification for satellite access Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2207414. Yunjing (CATT) provides comments.
Cai Simon (Nokia) provides comments
Guanglei (Huawei) replies to Yunjing(CATT).
Guanglei (Huawei) replies to Simon(Nokia).
Cai Simon (Nokia) replies to Guanglei (Huawei)
Guanglei (Huawei) further replies to Simon(Nokia).
Guanglei (Huawei) provides r01 and thanks Leo (Deutsche Telekom) supporting
Leo (Deutsche Telekom) provides comments.
Cai Simon (Nokia) provides r02
Stephen (Qualcomm) provides r03
Cai Simon (Nokia) provides r04
Guanglei (Huawei) is fine with r05
Yunjing (CATT) provides r05.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Stephen (Qualcomm) can agree the r05
Richard (Ericsson) is fine with r05
Leo (Deutsche Telekom) also supports r05
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.14 S2-2207414 CR Approval 23.273 CR0231R1 (Rel-17, 'F'): Clarification and correction on country verification for satellite access Huawei, HiSilicon Rel-17 Revision of S2-2206502r05. Approved Agreed
8.14 S2-2206745 CR Approval 23.273 CR0232 (Rel-17, 'F'): Addition of GNSS integrity requirement to in the location request Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2207415. Yunjing (CATT) provides comments.
Leo (Deutsche Telekom) provides comments.
Cai Simon (Nokia) supports Leo (Deutsche Telekom) and emphasizes backward compatibility
Cai Simon (Nokia) provides r02
Cai Simon (Nokia) requests to remove the two comments below which should be S2-2206502
Stephen (Qualcomm) comments and provides an r01
Stephen (Qualcomm) replies to Yunjing (CATT)
Runze (Huawei) provides r02.
Runze (Huawei) replies to Stephen, and believe r02 covers the r01 content.
Runze (Huawei) replies to Yunjing.
Leo (Deutsche Telekom) is fine with r02
Yunjing (CATT) replies.
Runze (Huawei) thanks Yunjing (CATT) and propose to approve r02.
Stephen (Qualcomm) provides an r03
Runze (Huawei) provides r04.
Leo (Deutsche Telekom) comments on r04.
Yunjing (CATT) accepts r04.
Runze (Huawei) provides r05.
Leo (Deutsche Telekom) is fine with r05, thanks.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Cai Simon (Nokia) provide comments
Stephen (Qualcomm) can agree the r05
Yunjing (CATT) can agree the r05.
Richard (Ericsson) is fine with r05.
Cai Simon (Nokia) accepts r05` with comments
Runze (Huawei) replies to Cai Simon (Nokia).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.14 S2-2207415 CR Approval 23.273 CR0232R1 (Rel-17, 'F'): Addition of GNSS integrity requirement to in the location request Huawei, HiSilicon Rel-17 Revision of S2-2206745r05. Approved Agreed
8.15 - - - Multimedia Priority Service (MPS) Phase 2 (MPS2) - - Docs:=4 -
8.15 S2-2206035 CR Approval 23.501 CR3683 (Rel-17, 'F'): Clarifications on Priority Subscription Samsung, Peraton Labs, CISA ECD Rel-17 r01 agreed. Revised to S2-2207416. Dongeun (Samsung) replies to Mirko (Huawei)
Mirko (Huawei) comments.
Dongeun (Samsung) provides r01
Mirko (Huawei) is ok with r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.15 S2-2207416 CR Approval 23.501 CR3683R1 (Rel-17, 'F'): Clarifications on Priority Subscription Samsung, Peraton Labs, CISA ECD Rel-17 Revision of S2-2206035r01. Approved Agreed
8.15 S2-2206036 CR Approval 23.502 CR3526 (Rel-17, 'F'): Clarifications on Priority Subscription Samsung, Peraton Labs, CISA ECD Rel-17 r01 agreed. Revised to S2-2207417. Dongeun (Samsung) provides r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.15 S2-2207417 CR Approval 23.502 CR3526R1 (Rel-17, 'F'): Clarifications on Priority Subscription Samsung, Peraton Labs, CISA ECD Rel-17 Revision of S2-2206036r01. Approved Agreed
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:=0 -
8.25 - - - Minimization of Service Interruption (MINT) - - Docs:=6 -
8.25 S2-2205425 LS In Information LS from RAN WG2: Reply LS on system information extensions for minimization of service interruption (MINT) RAN WG2 (R2-2206480) Rel-17 Noted Hyunsook (LGE) proposes to note the LS.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.25 S2-2205647 CR Approval 23.501 CR3664 (Rel-17, 'F'): UCU for MINT update Ericsson, LG Electronics, Qualcomm Rel-17 r01 agreed. Revised to S2-2207418. Lalith(Samsung) provides r01 of 5647
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Lalith(Samsung) objects r00. Fine to agree r01
Qian (Ericsson) is ok with r01
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.25 S2-2207418 CR Approval 23.501 CR3664R1 (Rel-17, 'F'): UCU for MINT update Ericsson, LG Electronics, Qualcomm Rel-17 Revision of S2-2205647r01. Approved Agreed
8.25 S2-2205648 CR Approval 23.502 CR3506 (Rel-17, 'F'): UCU for MINT update Ericsson, LG Electronics, Qualcomm Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.25 S2-2206798 CR Approval 23.501 CR3700 (Rel-17, 'F'): Clarification related to emergency service Samsung Rel-17 r03 agreed. Revised to S2-2207419. Haiyang (Huawei) provides r01.
Hyunsook (LGE) provides a comment.
Lalith(Samsung) is OK with r01.
Chris (Vodafone) objects to the removal of the Editor's note.
Lalith(Samsung) retains EN and provides r02.
Qian (Ericsson) comments that the EN can be removed since it has been covered by a CR agreed in previous meeting.
Hyunsook (LGE) comments.
Lalith(Samsung) provides r03
Chris accepts Ericsson and LGE comments and removes his objection.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Lalith(Samsung) suggests to agree r03
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.25 S2-2207419 CR Approval 23.501 CR3700R1 (Rel-17, 'F'): Clarification related to emergency service Samsung Rel-17 Revision of S2-2206798r03. Approved Agreed
8.26 - - - Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) - - Docs:=0 -
8.27 - - - Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) - - Docs:=11 -
8.27 S2-2205409 LS In Action LS from CT WG1: LS on the deactivation of access stratum due to discontinuous coverage CT WG1 (C1-224297) Rel-17 Responses drafted in S2-2205761, S2-2206266, S2-2206625. Final response in S2-2207420 Replied to
8.27 S2-2205761 LS OUT Approval [DRAFT] Reply LS on the deactivation of access stratum due to discontinuous coverage Qualcomm Rel-17 r02 agreed. Revised to S2-2207420, merging S2-2206266, and S2-2206625. Guillaume (MediaTek Inc.): Placeholder for discussion on 5761, 6266, 6625 (6612).
Lalith(Samsung) comments.
Haris(Qualcomm) comments
Guillaume (MediaTek Inc.) comments
Steve (Huawei) comments
Hannu (Nokia) comments
Lalith(Samsung) comments is fine with Way forward from Guillaume
Haris(Qualcomm) provides r01
Guillaume (MediaTek Inc.) responds to Lalith
Lalith(Samsung) provides r02
Guillaume (MediaTek Inc.): ok with r02. (Canada can be fixed to TBD when the final version is made)
Steve (Huawei) checking with RAN2 is ok, but we are potentially restricting their answers
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Guillaume (MediaTek Inc.): r02 ok
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.27 S2-2207420 LS OUT Approval Reply LS on the deactivation of access stratum due to discontinuous coverage SA WG2 Rel-17 Revision of S2-2205761r02, merging S2-2206266, and S2-2206625. Approved Approved
8.27 S2-2206266 LS OUT Approval [DRAFT] LS Reply on LS on the deactivation of access stratum due to discontinuous coverage Huawei, HiSilicon Rel-17 Response to S2-2205409. Merged into S2-2207420 Guillaume (MediaTek Inc.): To be discussed under S2-2205761.
Guillaume (MediaTek Inc.) proposes to mark it 'Merged to 5761'
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.27 S2-2206625 LS OUT Approval [DRAFT] Reply LS on the deactivation of access stratum due to discontinuous coverage Samsung Response to S2-2205409. Merged into S2-2207420 Guillaume (MediaTek Inc.): To be discussed under S2-2205761.
Guillaume (MediaTek Inc.) proposes to mark it 'Merged to 5761'
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Lalith (Samsung) is OK to Merge into 5761
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.27 S2-2205760 CR Approval 23.401 CR3707 (Rel-17, 'F'): Handling of radio capabilities across TN and NTN IoT Qualcomm Incorporated Rel-17 Confirm Spec version used - CR states ! Postponed Guillaume (MediaTek Inc.) supports the CR (with an upcoming change to the coversheet)
Hannu (Nokia) asks question on the foreseen RAN2 decision.
Haris(Qualcomm) comments
Guillaume (MediaTek Inc.) comments
Chris (Vodafone) provides r01
Haris(Qualcomm) provides r02
Haris(Qualcomm) responds to Chris
Chris (Vodafone) provides r03
Chris (Vodafone) suggests only endorsing the CR and sending an LS to RAN 2 to establish whether this issue also applies to NR-NTN. In which case the RACS impact will be large and an alternative RAN 2 solution might be better.
Chris (Vodafone) suggests that another alternative is to do no SA2 CR and reuse TAU for 'UE radio capability update'
Chris (Vodafone) responds and feels that no SA2 CR is needed as we can reuse TAU for 'UE radio capability update'
Wanqiang (Huawei) comments.
Chris (Vodafone) replies. His current preference is still 'do no SA2 CR'.
Stefan (Ericsson) provides comments and r04
Haris(Qualcomm) proposes to postpone the CR and instead send LS response
Chris (Vodafone) supports sending LS response to RAN 2 and no CR at this meeting
Wanqiang (Huawei) OK to postpone the CR.
Hannu (Nokia) is also agrees to postpone the CR but corrects one incorrect assumption that was made earlier in the discussion.
Chris (Vodafone) comments
Stefan (Ericsson) is also ok to postpone the CR and replies to Hannu
Stefan (Ericsson) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
DongYeon (Samsung) agrees to postpone of this CR and checking with RAN2.
Guillaume (MediaTek Inc.): Ok to postpone
Hannu (Nokia) agrees to postpone and comments to Stefan.
Chris (Vodafone) says that response to the RAN2 LS in S2-2205470 will be drafted in S2-2208091.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Chris (Vodafone) provides S2-2208091 in the INBOX as the draft response to the RAN2 LS in S2-2205470.
Haris(Qualcomm) provides r01
Chris (Vodafone) provides 8091r02
Postponed
8.27 S2-2206264 CR Approval 23.401 CR3708 (Rel-17, 'F'): MME sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2207421. Steve (Huawei) provides r01.
Hannu (Nokia) provides r02.
Steve (Huawei) is ok with r02
Stefan (Ericsson) provides r03
DongYeon (Samsung) provides r04.
Steve (Huawei) is ok with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Guillaume (MediaTek Inc.) ok with r04
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.27 S2-2207421 CR Approval 23.401 CR3708R1 (Rel-17, 'F'): MME sends forbidden TAI(s) to UE Huawei, HiSilicon Rel-17 Revision of S2-2206264r04. Approved Agreed
8.27 S2-2206265 CR Approval 23.401 CR3709 (Rel-17, 'F'): Clarification on UE deactivation of AS function Huawei, HiSilicon Rel-17 Postponed Guillaume (MediaTek Inc.) recommends to note/postpone the CR
Steve (Huawei) As we are asking RAN2, it is ok to postpone.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.27 S2-2206345 CR Approval 23.401 CR3710 (Rel-17, 'F'): RAN Initiated UE Context Release for UE using IoT satellite access MediaTek Inc. Rel-17 Approved Chunhui (Xiaomi) comments and proposes the changes to align with RAN3 TS36.413.
Guillaume (MediaTek) provides r01.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
DongYeon (Samsung) prefers r00.
Steve (Huawei) original or r01 is ok, but slight preference for r00 if we are picking one.
Haris(Qualcomm) prefers approving r0
Guillaume (MediaTek Inc.) recommends approved r0
Chunhui(Xiaomi) can accept r0.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.27 S2-2206612 DISCUSSION Discussion Discussion on the deactivation of AS due to discontinuous coverage Samsung Noted Guillaume (MediaTek Inc.): To be discussed under S2-2205761.
Guillaume (MediaTek Inc.) proposes to note the document.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Lalith (Samsung) agrees to note the document.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 - - - Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups - - Docs:=29 -
8.28 S2-2205461 LS In Information LS from ITU-T SG11: LS on status of draft Recommendation Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment' ITU-T SG11 (SG11-LS15) Noted Noted
8.28 S2-2205397 LS In Information LS from CT WG3: Reply LS on 5G NSWO roaming aspects CT WG3 (C3-222487) Rel-17 Revision of postponed S2-2203645 from S2#151E. Noted Laurent (Nokia): suggests to note this Ls in that is just for information
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.28 S2-2205399 LS In Information LS from CT WG4: Reply LS on 5G NSWO roaming aspects CT WG4 (C4-222436) Rel-17 Revision of postponed S2-2203649 from S2#151E. Noted Noted
8.28 S2-2205407 LS In Information LS from CT WG1: Reply LS on Slice list and priority information for cell reselection CT WG1 (C1-224295) Rel-17 Noted Noted
8.28 S2-2205432 LS In Information LS from RAN WG1: Reply LS on IMS emergency communication improvement-SM RAN WG1 (S1-221221) Rel-18 Noted Noted
8.28 S2-2205440 LS In Action LS from SA WG3: LS reply on 5G NSWO roaming aspects SA WG3 (S3-221220) Rel-17 Noted Laurent (Nokia): suggests to note this LS in that is just to tell that SA3 has Agreed to refer to SA2 specs
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Noted
8.28 S2-2205460 CR Approval 23.501 CR3658 (Rel-17, 'D'): Correction of Network Slice AS Groups IPLOOK Rel-17 Confirm CR Revision - CR states 1! Noted Weizhi WU(IPLOOK) provides r01
Alessio(Nokia) proposes to note this CR as it is editorial and merge the correction into any other CR set that will be including technical content.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2205502 CR Approval 23.501 CR3660 (Rel-17, 'B'): Alignment of SBI-based SMS Chinatelecom Cloud Rel-17 r01 agreed. Revised to S2-2207422. Liu Liu (China Telecom) replies George Foti (Ericsson)
George Foti (Ericsson) provides comments
Leo (Deutsche Telekom) provides comments
George (Ericsson) provides comments
Liu Liu (China Telecom) replies George (Ericsson)
Liu Liu (China Telecom) replies Leo (Deutsche Telekom)
Leo (Deutsche Telekom) is fine with r01, thanks.
Liu Liu (China Telecom) replies George (Ericsson) and Leo (Deutsche Telecom)
George (Ericsson) We are OK with r01
George (Ericsson) provides response
Hannu (Nokia) supports r01 and replies to George.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.28 S2-2207422 CR Approval 23.501 CR3660R1 (Rel-17, 'B'): Alignment of SBI-based SMS Chinatelecom Cloud Rel-17 Revision of S2-2205502r01. Approved Agreed
8.28 S2-2205503 CR Approval 23.502 CR3501 (Rel-17, 'B'): TS23.502 Alignment of SBI-based SMS Chinatelecom Cloud Rel-17 Revised to S2-2206022 Revised
8.28 S2-2206022 CR Approval 23.502 CR3501R1 (Rel-17, 'B'): TS23.502 Alignment of SBI-based SMS China Telecom, Orange, Ericsson Rel-17 Revision of of S2-2205503. Confirm CR Revision - CR states 0! Approved
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Agreed
8.28 S2-2205671 CR Approval 23.501 CR3667 (Rel-17, 'F'): NSAGs and their priorities based on S-NSSAIs in both the Allowed NSSAI and the Pending NSSAI NEC Rel-17 Noted Dongeun (Samsung) comments
Peter Hedman (Ericsson) provides r01
Alessio(Nokia) can only accept passing the pending NSSAI to the RAN for the UE in connected mode if this is what people agree to do. in fact NSSAA happens in connected mode! so this Cr is technically wrong as you do not go idle while NSSA is ongoing. really are we saying that in the middle of NSSA the UE gets released awaiting for NSSAA to complete?
Tamura (NEC) comments.
Haiyang (Huawei) comments
Tamura (NEC) provides comments.
Jinguo(ZTE) provides comments
Tamura (NEC) replies to Jinguo (ZTE).
Jinguo(ZTE) thanks Tamura explanation and provides further comments.
Tamura (NEC) replies to Sun Haiyang (Huawei).
Haiyang (Huawei) provides comments
Tamura (NEC) comments to Haiyang.
Haiyang (Huawei) provides comments, suggests to note this paper (objects all revisions).
Tamura (NEC) provides r02.
Peter Hedman (Ericsson) provides comments
alessio(Nokia) supports Huawei
Tamura (NEC) proposes to agree r01.
Haiyang (Huawei) provides comments.
Haiyang (Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) comments and repeats the position (suggests to note the paper, objects r00, r01 and r02).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2205672 CR Approval 23.501 CR3668 (Rel-17, 'F'): NSAG for TA(s) just outside of the RA has a specific association to those TA(s) NEC Rel-17 Postponed Dongeun (Samsung) provides comments
Alessio(Nokia) comments
Tamura (NEC) provides r01.
Peter Hedman (Ericsson) provides r02 and comments
Alessio(Nokia) thinks that we cannot agree to a CAT-F Cr that is a note at this stage of the release.
Tamura (NEC) proposes to agree on r01.
Tamura (NEC) provides r03.
Jinguo(ZTE) provides comments
Tamura (NEC) provides comments.
Haiyang (Huawei) provides comments.
Tamura provides comments.
Dongeun (Samsung) comments
alessio (Nokia) proposes to agree on r03 as R01 text may be confusing
Peter Hedman (Ericsson) provides r04
alessio(Nokia ) ask to note all revisions and not approve any version of this document
Peter Hedman (Ericsson) agrees that for RACH we would need a completely different clarification i.e. the existing 'at least' is good enough.
alessio(nokia) does not see any difference... for both it is better to know what NSAG is outside of RA TAIs if this is not the same as inside the TAIs or RA. but the current text works for both.
Haiyang (Huawei) provides a question on r04
Dongeun (Samsung) comments and provides r05
Peter Hedman (Ericsson) provides comments that latest discussions shows that existing text is good enough.
Alessio(nokia) fully supports Peter Hedman (Ericsson) in saying that the existing text is sufficient (there is hence no FASMO)
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Peter Hedman (Ericsson) proposes to postpone the CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Postponed
8.28 S2-2205762 DISCUSSION Approval Way Forward proposal for RAN slicing open issues Qualcomm Incorporated Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2205763 CR Approval 23.501 CR3676 (Rel-17, 'F'): Closing open issues on RAN slicing Qualcomm Incorporated Rel-17 CC#3: r08 agreed. Revised, merging S2-2205878, to S2-2207692. Haiyang (Huawei) comments and suggests to use this paper as baseline for RAN slicing open issues
Peter Hedman (Ericsson) provides comments
Jinguo(ZTE) provides comments
Haris(Qualcomm) comments
alessio(Nokia) comments
Haris(Qualcomm) responds
Jinguo(ZTE) provides r01
alessio(nokia) provides comments
Dieter (Deutsche Telekom) provides comments
Peter Hedman (Ericsson) provides reply on no need for referencing MAC spec
Peter Hedman (Ericsson) provides reply to the question on equal NSAG priority
Peter Hedman (Ericsson) provides r02
alessio (Nokia) objects to r02 as it is even less agreeable than any other paper submitted to this meeting as it makes RACH behaviour totally opaque to SA2 without a indication of the logic .
Haiyang (Huawei) provides r02 based on r01
Alessio(Nokia) comments this is the second r02. anyhow r01 also its not ok for us.
Haris(Qualcomm) responds on referencing the MAC spec
Jinguo(ZTE) provides r04
Alessio(Nokia) objects to this CR r03 as like r02 and r01 do not define how the priority is set (in a vendor independent way) and a testable RACH configuration behaviour for the UE (which instead many of the papers coming into the meeting did, so this a worse version of any input paper).
Haiyang (Huawei) provides r03 (r02 was provided)
Dongeun (Samsung) comments and object to the original version
Peter Hedman (Ericsson) provides comments to off-line comments
Peter Hedman (Ericsson) provides reply that there is no issue with SA2 referencing 38.331 that in turn reference 38.321.
Peter Hedman (Ericsson) provides r05
Alessio(Nokia) objects to all revisions and focus discussion on 6638
Dan(China Mobile) suggest the discussion on this paper.Would like to remind that based on chairman's suggestion, the comment for 'objects all revisions' is not allowed or acceptable statement,Since you have never seen the future revision yet
Alessio(Nokia ) objects to all past revisions so far
Peter Hedman (Ericsson) provides r06
Jinguo(ZTE) provides comments on r06
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Jinguo(ZTE) suggest to go for r05 then
Peter Hedman (Ericsson) provides comments and ok with r06, r05
Alessio(nokia) requests discussion of this topic in CC#2 to finalize this effort. Notes that any Network based setting of NSAG priority will complicate the configuration of NSAGs in RAN (and require more NSAGs - hence larger SIBs - as uniform priority mean no single UE will be allowed to have in same NSAG S-NSSAIs with different importance to the use case), and will not allow for any per UE policy without the roaming unfriendly per IMSI range settings (which we could avoid if we do subscription based approach).
Alessio(Nokia) objects to r05 (and all other revisions). r05 in particular has no testable description of RACH configuration and is a step backwards wrt any submitted ddocument
Haris(Qualcomm) responds and reiterates earlier comment
alessio(Nokia) provides additional requests for update
Jinguo(ZTE) provides new revision based on suggestion at CC#2
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Peter Hedman (Ericsson) provides comments and suggests to clarify SNPNs can also use the feature
Alessio(Nokia) provides notes that need to make aware the operators of constraints of this solution
Peter Hedman (Ericsson) provides reply to Nokia
alessio (nokia) notes it has been acknowledged the solution is insufficient (there is a wish to further enhance the Rel-17 functionality that is possible in later release.)
Peter Hedman (Ericsson) provides reply and confirms that with slice priority as proposed by Nokia we would not at all serve the purpose of the work as explained in prevoius reply and any enhancement to a feature can be discussed if there is a need for it.
Alessio(Nokia) observes there is no agreement on the purpose of the work that is why I had tried to reach the agreement last week on this but Ericsson escaped it with extreme care. the SID was about fast access to the intended slice and the intended slice must be the one that is more important for the UE. Ericsson differs from it but cannot explain what is and how the solution maps to his different intended purpose.
Revised
8.28 S2-2207692 CR Approval 23.501 CR3676R1 (Rel-17, 'F'): Closing open issues on RAN slicing Qualcomm Incorporated Rel-17 CC#3: Revision of S2-2205763r08, merging S2-2205878. This CR was agreed with concern from Nokia Agreed
8.28 S2-2205877 DISCUSSION Agreement Discussion on the Action points from SA#96 Ericsson Rel-17 Noted Alessio(Nokia) comments that we need to agree on the stage one first.
Guillaume (MediaTek Inc.) comments
Peter Hedman (Ericsson) provides reply to MediaTek
alessio comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2205878 CR Approval 23.501 CR3681 (Rel-17, 'F'): Network Slice based cell reselection and Random Access Ericsson Rel-17 Merged into S2-2207692 Jinguo(ZTE) suggests to merge this CR to 5763
Dongeun (Samsung) comments
Peter Hedman (Ericsson) provides comments that as per CC#1 discussions are kept for 5763 when it relates to SA guidance.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Merged
8.28 S2-2205879 CR Approval 23.502 CR3518 (Rel-17, 'F'): NSAG Information in NSSF Ericsson Rel-17 Noted alessio(Nokia) comments this paper is on a topic outside the tasks of SA guidance, is NOT FASMO and technically incorrect so we cannot accept it.
Peter Hedman (Ericsson) provides comments that NSSF is involved in how NSAGs are determined and currently the usage of the Nnssf_NSSelection_Get does not work i.e. CAT F
Jinguo(ZTE) supports this paper.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
alessio(Nokia) Asks to mark this CR as NOTED in the notes based on our earlier comments requesting this handling.
Peter Hedman (Ericsson) explains why the CR is FASMO
Alessio(Nokia) repeats this is not FASMO.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206037 CR Approval 23.503 CR0734 (Rel-17, 'F'): Support of UE policy PCR trigger for Slice Priority Samsung Rel-17 Noted Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides questions
Dongeun (Samsung) replies to Peter (Ericsson)
Jinguo(ZTE) provides comments
Haiyang (Huawei) provides questions
Dongeun (Samsung) replies to Jinguo (ZTE) and Haiyang (Huawei)
alessio(nokia) agrees the URSP is totally unrelated to the feature
alessio(nokia0 agrees with Jinguo and proposes to not the CR which BTW seems like a new feature and we are not supposed to work on other than what SA plenary is asking at this meeting.
Dieter (Deutsche Telekom) agrees with previous comments and proposes to note the CR.
Haris(Qualcomm) proposes to NOTE the CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206626 DISCUSSION Discussion Presentation about NR_Slice_Core issues from SA#96 Nokia, Nokia Shanghai Bell Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206637 DISCUSSION Agreement Discussion on the Action points from SA#96 on NR_Slice_Core Nokia, Nokia Shanghai Bell, OPPO, Xiaomi Rel-17 Noted Guillaume (MediaTek Inc.) comments
Alessio(nokia) replies to Guillaume (MediaTek Inc.) comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206638 CR Approval 23.501 CR3692 (Rel-17, 'F'): Clarification of the NR_Slice_core feature. Nokia, Nokia Shanghai Bell, Oppo, Xiaomi... Rel-17 CC#3: Noted Peter Hedman (Ericsson) provides comments e.g. the subscribed slice priorities addition is not acceptable
Haris(Qualcomm) cannot accept r02
Alessio (Nokia) provides R02 based on discussion on the call organized earlier today (r01 is just the same but without the text capturing Guillaume's comment so please ignore it)
Alessio(nokia) replies to Haris(Qualcomm) comments and provides r04 and asks to ignore r03 that had been submitted in error.
Haiyang (Huawei) comments
Alessio(Nokia) replies to Haiyang (Huawei) comments
Peter Hedman (Ericsson) OBJECTS to the revisions including the slice priorities
Dan (China Mobile) do not agree with r04
alessio(nokia) comments
Dieter (Deutsche Telekom) provides comments
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Haiyang (Huawei) further comments
Peter Hedman (Ericsson) objects to r04, r03, r02, r01, r00
Alessio(nokia) requests discussion of this topic in CC#2 to finalize this effort. Notes that any Network based setting of NSAG priority will complicate the configuration of NSAGs in RAN (and require more NSAGs - hence larger SIBs - as uniform priority mean no single UE will be allowed to have in same NSAG S-NSSAIs with different importance to the use case), and will not allow for any per UE policy without the roaming unfriendly per IMSI range settings (which we could avoid if we do subscription based approach).
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206640 CR Approval 23.502 CR3544 (Rel-17, 'F'): Clarification of the NR_Slice_core feature. Nokia, Nokia Shanghai Bell, Oppo, Xiaomi Rel-17 Noted Peter Hedman (Ericsson) provides comments that the subscribed slice priorities addition is not acceptable
alessio(Nokia) comments that we need to make this feature work according to a intended goal of the feature. our understanding of the feature has been clarified but I see Ericsson is escaping to clarify what their view is on what the feature is. Maybe you would like to care to provide the stage one opinion of what this feature is about? I started a suitable thread under your DP tdoc number to give you're the opportunity to explain what is the goodies you can provide with the feature based on your 'solution' which in our opinion does not work as static OAM NSAG priority values are a nonstarter as documented in our DPs and slides.
Peter Hedman (Ericsson) objects to the CR
alessio(Nokia) comments that if a study is needed for slice prioritization even the NSAG priority should be part of that as it has to be linked to the ranking of the underlying slices. that is why we miss still the input on what the feature delivers if the Slices priority from service level is NOT considered. it is not clear why the AMF should e.g. be configurable with some 'priority values' but not the UDM with per UE info.
Alessio(Nokia) does not think a study is need as we do not study how the NSAG priorities are set and why. same logic.
Ouerdia Chelibane (Orange) provides comments.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
Alessio(nokia) requests discussion of this topic in CC#2 to finalize this effort. Notes that any Network based setting of NSAG priority will complicate the configuration of NSAGs in RAN (and require more NSAGs - hence larger SIBs - as uniform priority mean no single UE will be allowed to have in same NSAG S-NSSAIs with different importance to the use case), and will not allow for any per UE policy without the roaming unfriendly per IMSI range settings (which we could avoid if we do subscription based approach). so we would like to suggest the indication of subscribed s-NSSAI prioiry from UDM is quite helpful to this feature eb voth flavors suggested in the companion 6639 CRr04
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206732 DISCUSSION Discussion Access Network selection for 5G NSWO Lenovo, Broadcom Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Noted
8.28 S2-2206736 CR Approval 23.501 CR3697 (Rel-17, 'B'): Access Network selection for 5G NSWO Lenovo, Broadcom Rel-17 r02 agreed. Revised to S2-2207423. Stefan (Ericsson) provides comments and questions
Haris(Qualcomm) objects to the CR
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.28 S2-2207423 CR Approval 23.501 CR3697R1 (Rel-17, 'B'): Access Network selection for 5G NSWO Lenovo, Broadcom Rel-17 Revision of S2-2206736r02. Approved Agreed
8.28 S2-2208089 LS OUT Approval [DRAFT] LS on LS on slice list and priority information for cell reselection and Random Access ZTE Created at CC#2. CC#3: Revised to S2-2207698.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Revised
8.28 S2-2207698 LS OUT Approval LS Out on LS on slice list and priority information for cell reselection and Random Access SA WG2 - CC#3: Revision of S2-2208089. This LS OUT was approved Approved
9 - - - Rel-18 SIDs - - Docs:=0 -
9.1 - - - Study on System Enabler for Service Function Chaining (FS_SFC) - - Docs:=15 -
9.1 - - - Solution Updates - - Docs:=6 -
9.1 S2-2205568 P-CR Approval 23.700-18: KI#2: Update of Solution 7 clarifying terminology Lenovo Rel-18 r01 agreed. Revised to S2-2207704. Stefan (Ericsson) provides comments
Dimitris (Lenovo) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.1 S2-2207704 P-CR Approval 23.700-18: KI#2: Update of Solution 7 clarifying terminology Lenovo Rel-18 Revision of S2-2205568r01. Approved Approved
9.1 S2-2206526 P-CR Approval 23.700-18: KI#1, Update Sol#8 figure Huawei, HiSilicon Rel-18 Approved Yoohwa (ETRI) provides comments.
Fenqin (Huawei) provides responds.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.1 S2-2206727 P-CR Approval 23.700-18: KI #1, Sol #5: Update to remove EN ETRI Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.1 S2-2206728 P-CR Approval 23.700-18: KI #1, Sol #6: Update to add Impacts ETRI Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.1 S2-2206814 P-CR Approval 23.700-18: (KI2) update to solution 3 Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.1 - - - Evaluation and conclusion - - Docs:=9 -
9.1 S2-2205577 P-CR Approval 23.700-18: Evaluation and interim conclusions Lenovo Rel-18 r07 + changes agreed. Revised to S2-2207705, merging S2-2205646, S2-2205920 and S2-2206528 Megha(Intel) proposes to use S2-2205577 as baseline for KI#2 conclusion discussion.
Stefan (Ericsson) provides comments
Dimitris (Lenovo) provides r01 to focus on KI#2 conclusion discussions
Fenqin (Huawei) comments.
Stefan (Ericsson) replies to Dimitris
Megha(Intel) provides comments and r02
Stefan (Ericsson) provides r03
Megha (Intel) provides r04
Laurent (Nokia): provides r05
Fenqin (Huawei) provides r06
Stefan (Ericsson) provides r07
Laurent (Nokia): Comments
Fenqin (Huawei) support r07
Stefan (Ericsson) replies to Laurent
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): can only live with R02/R04/R05; objects to any other version; can easily live with R06+R07 with an added EN 'support of metadata is optional'
Fenqin (Huawei) accept only r07 and object other version
Dimitris (Lenovo) is OK with r07
Stefan (Ericsson) accept only r03 and r07 and object other revisions
Megha (Intel) is ok with r07.
==== 9.X, 10.X Final Deadline ====
Revised
9.1 S2-2207705 P-CR Approval 23.700-18: Evaluation and interim conclusions Lenovo Rel-18 Revision of S2-2205577r07 + changes, merging S2-2205646, S2-2205920 and S2-2206528. Approved Approved
9.1 S2-2205646 P-CR Approval 23.700-18: Overall evaluation of solutions for KI#1 and KI#2 Intel Rel-18 Merged into S2-2207705 Megha(Intel) proposes to merge S2-2205646 with S2-2205577.
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.1 S2-2205850 P-CR Approval 23.700-18: Conclusions on deployment scenarios Ericsson, Huawei Rel-18 To be merged into S2-2205919 (noted). Noted Megha(Intel) - can this document be merged with S2-2205919 ?
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
Stefan (Ericsson) OK to consider it merged
==== 9.X, 10.X Final Deadline ====
Noted
9.1 S2-2205851 P-CR Approval 23.700-18: Basic evaluation and conclusions Ericsson Rel-18 To be merged into S2-2205919 (noted). Noted Megha(Intel) - can this document be merged with S2-2205919 ?
==== 9.X, 10.X Revisions Deadline ====
Stefan (Ericsson) OK to consider it merged
==== 9.X, 10.X Final Deadline ====
Noted
9.1 S2-2205919 P-CR Approval 23.700-18: KI#1: Conclusion Intel, AT&T, Deutsche Telekom Rel-18 Noted Fenqin(Huawei) provides comments
Megha(Intel) provides r01
Megha(Intel) proposes to use S2-2205919 as baseline for KI#1 conclusion discussion. Provides r01
Stefan (Ericsson) provides comments
Megha(Intel) provides responds to Stefan and Fenqin.
Jinguo(ZTE) provides comments
Stefan (Ericsson) replies to Megha
Megha(Intel) addresses questions/comments from Stefan, Fenqin, Jinguo and provides r02.
Fenqin (Huawei) replies to Megha
Fenqin(Huawei) provides comments and r03
Laurent (Nokia): provides r04
Laurent (Nokia): asks to have only 1 or 2 threads for conclusion discusison
Megha provides comments
Megha(Intel) provides clarification to Laurent (Nokia)
Fenqin(Huawei) provides r05
Laurent (Nokia): provides r06
Laurent (Nokia): provides r07
Fenqin(Huawei) comments
Megha(Intel) provides r08 and comments
Fenqin(Huawei) comments and provides r09
Laurent (Nokia): provides r10
Stefan (Ericsson) supports r09
Fenqin(Huawei) provides r11
Megha (Intel) provides r12 and comments
Laurent (Nokia): provides r13
Megha(Intel) provides r14
Fenqin (Huawei): provides comments
==== 9.X, 10.X Revisions Deadline ====
Jinguo(ZTE) provides comments and prefer r13.
Rohit (AT&T) supports r14
Laurent (Nokia): can live with R13, R11, R10; objects to any other version
Stefan (Ericsson) can accept 03, r05, r09, r11, r13. Objects to other revisions
Fenqin (Huawei) we also can only accept 03, r05, r09, r11, r13. Objects to other revisions
Megha (Intel) provides comments and can only accept r08, r12, r14. Objects to all other revisions. Also propose to open this document on CC#5.
==== 9.X, 10.X Final Deadline ====
Noted
9.1 S2-2205920 P-CR Approval 23.700-18: KI#2: Conclusion Intel, AT&T, Deutsche Telekom Rel-18 Merged into S2-2207705 Megha(Intel) proposes to merge S2-2205920 with S2-2205577.
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.1 S2-2206527 P-CR Approval 23.700-18: KI#1, Evaluation and conclusion of KI#1 Huawei, HiSilicon Rel-18 Merged into S2-2205919 (noted). Noted Fenqin (Huawei) - Suggest to discuss the concept level first
Megha(Intel) - can this document be merged with S2-2205919 ?
==== 9.X, 10.X Revisions Deadline ====
Fenqin (Huawei) we are ok to merge to 5919.
==== 9.X, 10.X Final Deadline ====
Noted
9.1 S2-2206528 P-CR Approval 23.700-18: KI#2, Evaluation and conclusion of KI#2 Huawei, HiSilicon Rel-18 Merged into S2-2207705 Fenqin (Huawei) - Suggest to discuss the concept level first
Megha(Intel) - can this document be merged with S2-2205577 ?
==== 9.X, 10.X Revisions Deadline ====
Fenqin (Huawei) we are ok to merge to 5577.
==== 9.X, 10.X Final Deadline ====
Merged
9.2 - - - Study on Generic group management, exposure and communication enhancements (FS_GMEC) - - Docs:=53 -
9.2 - - - Solution Updates for KI#1 - - Docs:=9 -
9.2 S2-2205864 P-CR Approval 23.700-74: KI#1, Sol#8, 9: Updates to clarify relation to non-5GVN groups Ericsson Rel-18 r02 agreed. Revised to S2-2207035. Shubhranshu (Nokia) responds
Qianghua (Huawei) provides comments
Stefan (Ericsson) replies to Qianghua
Qianghua (Huawei) provides r01
Stefan (Ericsson) provides r02
Qianghua (Huawei) r02 OK for me
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207035 P-CR Approval 23.700-74: KI#1, Sol#8, 9: Updates to clarify relation to non-5GVN groups Ericsson Rel-18 Revision of S2-2205864r02. Approved Approved
9.2 S2-2206278 P-CR Approval 23.700-74: 23.700-74 KI #1,Sol#18: Update to resolve the editor s note which provides the UE with the area restriction information CATT Rel-18 r02 agreed. Revised to S2-2207036, merging and S2-2206714 Sang-Jun (Samsung) proposes to merge 6278 with 6714 as they are updating the same solution.
Liping Wu (CATT) provides r01.
Sebastian (Qualcomm) objects to r00 and r01
Liping(CATT) provides r02
zhendong (ZTE) is fine with r02
==== 9.X, 10.X Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207036 P-CR Approval 23.700-74: 23.700-74 KI #1,Sol#18: Update to resolve the editor s note which provides the UE with the area restriction information CATT Rel-18 Revision of S2-2206278r02, merging and S2-2206714. Approved Approved
9.2 S2-2206279 P-CR Approval 23.700-74: 23.700-74 KI#1,Sol#21: Update to resolve the editor s notes CATT Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.2 S2-2206547 P-CR Approval 23.700-74: KI#1, Update sol1 to address the EN Huawei, HiSilicon Rel-18 Approved Sebastian (Qualcomm) asks question
Qianghua (Huawei) replies
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.2 S2-2206714 P-CR Approval 23.700-74: KI#1, update the solution#18 ZTE Rel-18 Merged into S2-2207036 Sang-Jun (Samsung) proposes to merge 6714 with 6278 as they are updating the same solution.
zhendong (ZTE) prefer to keep it seperately
Qianghua (Huawei) thinks now it is OK to consider to merge this into 6278
==== 9.X, 10.X Revisions Deadline ====
Sang-Jun (Samsung) also thinks this can be considered to be merged into 6278.
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2206894 P-CR Approval 23.700-74: Solution #13 Updates Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2207037. Sebastian (Qualcomm) objects to the PCR
zhendong (ZTE) ask question for clarification
Sebastian (Qualcomm) replies
Qianghua (Huawei) provides additional comments
Stefan (Ericsson) comments
Shubhranshu (Nokia) comments
Shubhranshu (Nokia) responds
zhendong (ZTE) provides response
Shubhranshu (Nokia) provides r01
Qianghua (Huawei) still holds concerns
Qianghua (Huawei) provides r02 and further replies
Sebastian (Qualcomm) provides r03
Shubhranshu (Nokia) provides r04
==== 9.X, 10.X Revisions Deadline ====
Qianghua (Huawei) proposes to go r03, and disagrees with new additions on step 7 in r04
Shubhranshu (Nokia) proposes to agree r04
Qianghua (Huawei) objects r00, r01, r04
Shubhranshu (Nokia) prefers r04, but OK to r03 (as a compromise)
Sebastian (Qualcomm) is ok with r03 and r04, objects to other versions
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207037 P-CR Approval 23.700-74: Solution #13 Updates Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206894r03. Approved Approved
9.2 - - - Solution Updates for KI#3 - - Docs:=4 -
9.2 S2-2205863 P-CR Approval 23.700-74: KI#3, Sol#21: Updates to resolve editor s notes and add clarifications Ericsson Rel-18 r02 agreed. Revised to S2-2207038. Sang-Jun (Samsung) proposes to correct Sol#21 into Sol#22 in Title and Discussion.
Qianghua (Huawei) provides comments
Stefan (Ericsson) provides r01
Qianghua (Huawei) provides additional comments
Stefan (Ericsson) replies to Qianghua
Qianghua (Huawei) further replies to Stefan's comments
Stefan (Ericsson) provides replies
Qianghua (Huawei) provides r02 and replies
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207038 P-CR Approval 23.700-74: KI#3, Sol#21: Updates to resolve editor s notes and add clarifications Ericsson Rel-18 Revision of S2-2205863r02. Approved Approved
9.2 S2-2206550 P-CR Approval 23.700-74: KI#3: Update on Sol#2 Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207039. Stefan (Ericsson) provides comments and questions
Qianghua (Huawei) replies
Stefan (Ericsson) provides comments and replies
Qianghua (Huawei) provides r01 and further replies to Stefan
Stefan (Ericsson) replies to Qianghua
Qianghua (Huawei) provides further replies
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207039 P-CR Approval 23.700-74: KI#3: Update on Sol#2 Huawei, HiSilicon Rel-18 Revision of S2-2206550r01. Approved Approved
9.2 - - - Solution Updates for KI#4 - - Docs:=20 -
9.2 S2-2205865 P-CR Approval 23.700-74: KI#4, Sol#16: Updates to resolve ENs Ericsson Rel-18 r01 agreed. Revised to S2-2207040. Qianghua (Huawei) provides comments and suggests to merge with S2-2206795
Laurent (Nokia): answers
Stefan (Ericsson) replies and prferes to keep separate
Qianghua (Huawei) replies to Stefan
Qianghua (Huawei) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207040 P-CR Approval 23.700-74: KI#4, Sol#16: Updates to resolve ENs Ericsson Rel-18 Revision of S2-2205865r01. Approved Approved
9.2 S2-2205485 P-CR Approval 23.700-74: Update to solution 3 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207041. Sang-Jun (Samsung) asks for clarification.
Laurent (Nokia): answers
Sang-Jun (Samsung) thanks Laurent for providing the answer and correcting the mail title.
Qianghua (Huawei) provides comments
Qianghua (Huawei) provides further comments and replies
Qianghua (Huawei) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207041 P-CR Approval 23.700-74: Update to solution 3 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205485r01. Approved Approved
9.2 S2-2206098 P-CR Approval 23.700-74: KI#4: Update to Solution #19 China Telecom Rel-18 Merged into S2-2207042 Sang-Jun (Samsung) proposes to merge 6098 with 5785 and 5786 as they are updating the same solution.
Liping Wu(CATT) provides comments and asks for clarification.
Yue (China Telecom) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2205784 P-CR Approval 23.700-74: Update to solution #5 on GSMF selection China Mobile Com. Corporation, China Southern Power Grid Rel-18 Merged into S2-2207044 Sang-Jun (Samsung) proposes to merge 5784 with 6277, 6552 and 6641 as they are updating the same solution.
Laurent (Nokia): is it ok to merge 5784 into 6552 as proposed by the rapporteur
Laurent (Nokia): objects to 5784 as it is merged into 6552 as proposed by the rapporteur
Yi (China Mobile) we are ok to merge into 6552.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2205785 P-CR Approval 23.700-74: Update to solution #19 on Single-SMF indicator China Mobile, China Southern Power Grid Rel-18 r01 agreed. Revised to S2-2207042, merging and S2-2206098 Sang-Jun (Samsung) proposes to merge 5785 with 6098 and 5786 as they are updating the same solution.
Yi (China Mobile) provides r01 which has merged 6098 5786 and update the procedure for solution#19.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207042 P-CR Approval 23.700-74: Update to solution #19 on Single-SMF indicator China Mobile, China Southern Power Grid Rel-18 Revision of S2-2205785r01, merging S2-2205786 and S2-2206098. Approved Approved
9.2 S2-2205786 P-CR Approval 23.700-74: Update to solution #19_on the impacts to existing network China Mobile, China Southern Power Grid Rel-18 Merged into S2-2207042 Sang-Jun (Samsung) proposes to merge 5786 with 6098 and 5785 as they are updating the same solution.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2206276 P-CR Approval 23.700-74: 23.700-74 KI#4, Sol#4: Update to clarify relevant descriptions about SMF selection and N4 session setup CATT Rel-18 r06 agreed. Revised to S2-2207043, merging and S2-2206716 Sang-Jun (Samsung) proposes to merge 6276 with 6716 as they are updating the same solution.
Liping Wu (CATT) provides r01.
zhendong (ZTE) provides r02
zhendong (ZTE) provides the comments
Liping Wu(CATT) responds zhendong (ZTE) and provides r03
Laurent (Nokia): provides r04
Liping Wu(CATT)provides r05
Stefan (Ericsson) provides r06
==== 9.X, 10.X Revisions Deadline ====
Liping Wu (CATT) is fine with r06.
Laurent (Nokia): Laurent (Nokia): objects to any version between R00 and R03 both included; R06 is the best version.
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207043 P-CR Approval 23.700-74: 23.700-74 KI#4, Sol#4: Update to clarify relevant descriptions about SMF selection and N4 session setup CATT Rel-18 Revision of S2-2206276r06, merging and S2-2206716. Approved Approved
9.2 S2-2206277 P-CR Approval 23.700-74: 23.700-74 KI #4, Sol#5: Update to resolve the editor's notes CATT Rel-18 Merged into S2-2207044 Sang-Jun (Samsung) proposes to merge 6277 with 5784, 6552 and 6641 as they are updating the same solution.
Liping (CATT) agrees to merge 6277 into 6552.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2206552 P-CR Approval 23.700-74: KI#4: Update Solution 5 to address Editor's notes Huawei, HiSilicon Rel-18 r10 agreed. Revised to S2-2207044, merging S2-2205784, S2-2206277 and S2-2206641 Sang-Jun (Samsung) proposes to merge 6552 with 5784, 6277 and 6641 as they are updating the same solution.
zhendong (ZTE) propose this paper as baseline for sol#5
Dan (China Mobile) provide r01 with merging S2-2206641 into this paper
Liping (CATT) is fine to merged 6277 into 6552, and provide some comments.
Qianghua (Huawei) Fine to merged 6641, 6277 and 5784 into 6552, please find r02.
Qianghua (Huawei) provides r03
Laurent (Nokia): provides r04
Qianghua (Huawei) provides r05
Stefan (Ericsson) provides questions and r06
Qianghua (Huawei) provides r07 and replies to Stefan
Stefan (Ericsson) provides r08
Qianghua (Huawei) provides r09
Stefan (Ericsson) provides r10
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R07 and R09; objects to any version between R00 and R03 both included
Laurent (Nokia): objects also to R05
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207044 P-CR Approval 23.700-74: KI#4: Update Solution 5 to address Editor's notes Huawei, HiSilicon Rel-18 Revision of S2-2206552r10, merging S2-2205784, S2-2206277 and S2-2206641. Approved Approved
9.2 S2-2206641 P-CR Approval 23.700-74: Update to solution#5 China Mobile Rel-18 Merged into S2-2207044 Sang-Jun (Samsung) proposes to merge 6641 with 6552, 5784 and 6277 as they are updating the same solution.
Dan(China Mobile) merge this paper into S2-2206552
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2206716 P-CR Approval 23.700-74: KI#4, update the solution#4 ZTE Rel-18 Merged into S2-2207043 Sang-Jun (Samsung) proposes to merge 6716 with 6276 as they are updating the same solution.
Laurent (Nokia): objects to any version of this Tdoc that has been merged in 6276
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.2 S2-2206717 P-CR Approval 23.700-74: KI#4, update the solution#20 ZTE Rel-18 r01 agreed. Revised to S2-2207045. Laurent (Nokia): Comments: can't accept R00
zhendong (ZTE) provides the response and r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207045 P-CR Approval 23.700-74: KI#4, update the solution#20 ZTE Rel-18 Revision of S2-2206717r01. Approved Approved
9.2 S2-2206795 P-CR Approval 23.700-74: Update to solution 16 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207046. Qianghua (Huawei) provides comments
Qianghua (Huawei) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207046 P-CR Approval 23.700-74: Update to solution 16 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206795r01. Approved Approved
9.2 - - - Solution Updates for KI#5 - - Docs:=1 -
9.2 S2-2206106 P-CR Approval 23.700-74: Update of Solution #7 for FS_GMEC KI#5 Samsung Rel-18 Noted Sebastian (Qualcomm) objects to the PCR
Sang-Jun (Samsung) replies to Sebastian (Qualcomm). and provides r01.
Laurent (Nokia): Comments
Sang-Jun (Samsung) replies to Laurent (Nokia), and provides r02.
Stefan (Ericsson) provides questions
Sang-Jun (Samsung) answers to Stefan (Ericsson), and provides r03.
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) objects to all versions
==== 9.X, 10.X Final Deadline ====
Noted
9.2 - - - Evaluations and Conclusions for KI#1 - - Docs:=2 -
9.2 S2-2206548 P-CR Approval 23.700-74: KI#1 evaluations update and conclusions Huawei, HiSilicon, Samsung Rel-18 r17 agreed. Revised to S2-2207047. Sang-Jun (Samsung) proposes to use S2-2206548 for KI#1 evaluations and conclusions, and to merge S2-2205862, S2-2206217, S2-2206715 into S2-2206548.
Sebastian (Qualcomm) comments
Stefan (Ericsson) provides comments
Qianghua (Huawei) provides r01, merging 05862
Shubhranshu (Nokia) provides r02
zhendong (ZTE) provides r04
Dan (China Mobile) provides r03
Hyunsook (LGE) provides a comment.
zhendong (ZTE) provides r07
Hyunsook (LGE) provides the comment on r05 and r06.
Qianghua (Huawei) provides r06 and responses
Stefan (Ericsson) provides r05
Liping Wu (CATT) provides a comment.
Shubhranshu (Nokia) comments
Liping Wu (CATT) provides r08.
Jun (Chinatelecom) comments
Qianghua (Huawei) provides r09
Liping (CATT) is fine with r09 and would like to co-sign.
Wonjung (LG Uplus) agrees with r09 and would like to co-sign.
Jun Yin (Chinatelecom) agrees with r09 and would like to co-sign.
Sungpyo (KT) agrees with r09 and would like to co-sign.
zhendong (ZTE) agree with r09
Stefan (Ericsson) cannot agree r09, provides r10
Qianghua (Huawei) provides r11
zhendong (ZTE) provides r13
Shubhranshu (Nokia) provides r14, objects to r13
Sebastian (Qualcomm) provides r15
Qianghua (Huawei) provides r16
Shubhranshu (Nokia) provides r17, objects to r15, r16
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207047 P-CR Approval 23.700-74: KI#1 evaluations update and conclusions Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2206548r17. Approved Approved
9.2 - - - Evaluations and Conclusions for KI#2 - - Docs:=2 -
9.2 S2-2206549 P-CR Approval 23.700-74: KI#2 conclusion proposal Huawei, HiSilicon, Samsung Rel-18 r03 agreed. Revised to S2-2207048. Stefan (Ericsson) provides comments
Qianghua (Huawei) replies
Stefan (Ericsson) replies to Qianghua and provides r01
Shubhranshu (Nokia) comments
Qianghua (Huawei) provides r02 and further replies
Stefan (Ericsson) provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207048 P-CR Approval 23.700-74: KI#2 conclusion proposal Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2206549r03. Approved Approved
9.2 - - - Evaluations and Conclusions for KI#3 - - Docs:=2 -
9.2 S2-2206551 P-CR Approval 23.700-74: KI#3, solution evaluations and conclusions proposal Huawei, HiSilicon, Samsung Rel-18 r05 agreed. Revised to S2-2207049. Stefan (Ericsson) comments and provides r01
Qianghua (Huawei) replies
Stefan (Ericsson) replies to Qianghua
Shubhranshu (Nokia) comments
Qianghua (Huawei) provides r02 and replies
Stefan (Ericsson) provides question
Shubhranshu (Nokia) provides r03, objects to r02
Stefan (Ericsson) provides r04
Qianghua (Huawei) replies to Shubhranshu and provided r05
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) can accept either r04 (preferred) or r05 but only if NOTE 3 is removed; objects to other versions
Qianghua (Huawei) proposes to go r05 + removing NOTE 3: Parameter mapping between 3GPP parameters and ACIA parameters may be discussed as part of SA6 SEAL framework, but this is out of scope for SA2
Sang-Jun (Samsung) can accept r05 + removing NOTE 3.
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207049 P-CR Approval 23.700-74: KI#3, solution evaluations and conclusions proposal Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2206551r05. Approved Approved
9.2 - - - Evaluations and Conclusions for KI#4 - - Docs:=2 -
9.2 S2-2206112 P-CR Approval 23.700-74: Conclusion for FS_GMEC KI#4 Samsung, Huawei Rel-18 CC#5: Postponed Sang-Jun (Samsung) proposes to use S2-2206112 for KI#4 conclusions, and to merge S2-2205486 into S2-2206112.
Laurent (Nokia): provides r01
Laurent (Nokia): provides r02
Qianghua (Huawei) provides r03 and responses
Stefan (Ericsson) supports r02 and comments
zhendong (ZTE) provides r04
Sang-Jun (Samsung) agrees with Qianghua and is fine with r04 changes.
Qianghua (Huawei) OK with r04 and replies
Marco (Huawei) answer to Stefan (Ericsson)
Stefan (Ericsson) replies to Marco
Laurent (Nokia): answers
Qianghua (Huawei) provides further replies
Liping Wu provides comments for r04
Sang-Jun (Samsung) supports Qianghua (Huawei)'s views.
Sungpyo (KT) agrees with Qianghua and is fine with r04 changes.
zhendong (ZTE) support r04 as way forward
Wonjung (LG Uplus) is OK with r04.
Sang-Jun (Samsung) provides r05 which has small updates on top of r04.
Qianghua (Huawei) provides r06
Yi (China Mobile) we provides r07and would like to co-sign..
Stefan (Ericsson) provides question regarding r07
Laurent (Nokia): Comments
Qianghua (Huawei) provides r08
==== 9.X, 10.X Revisions Deadline ====
Sang-Jun (Samsung) is fine with r08.
Sungpyo(KT)is fine with r08 and would like to co-sign.
Liping(CATT)is fine with r08 and would like to co-sign.
Wonjung (LG Uplus) is fine with r08.
Yue (China Telecom) is fine with r08 and would like to co-sign.
Yi (China Mobile) is fine with r08 and would like to co-sign.
Laurent (Nokia): can only live with r01 and R02; objects to any other version; suggests to postpone the decision on this KI
Stefan (Ericsson) accepts r01 or r02, objects to other revisions.
Qianghua (Huawei) proposes to go R08, which is a good comprise for this KI# conclusion. object r01 and r02. In sake of progress, request to check at CC#5 whether we can make a way forward.
Sang-Jun (Samsung) also proposes to go with r08.
==== 9.X, 10.X Final Deadline ====
Postponed
9.2 S2-2206553 P-CR Approval 23.700-74: KI#4, solution evaluations Huawei, HiSilicon Rel-18 CC#5: Postponed Sang-Jun (Samsung) proposes to use S2-2206553 for KI#4 conclusions, and to merge S2-2206109 into S2-2206553.
Laurent (Nokia): provides r01
Qianghua (Huawei) provides r02
Laurent (Nokia): provides r03
Qianghua (Huawei) provides r04
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R00, R02, R04
Qianghua (Huawei) objects r01, r03. Ask Laurent what part do you see problems? I hope we can find a comprise so to not lose the progress we have spent so much efforts on. So request for CC#5.
Sang-Jun (Samsung) proposes to go with r02 or r04.
==== 9.X, 10.X Final Deadline ====
Postponed
9.2 - - - Evaluations and Conclusions for KI#5 - - Docs:=4 -
9.2 S2-2206107 P-CR Approval 23.700-74: Evaluation for FS_GMEC KI#5 Samsung Rel-18 r01 agreed. Revised to S2-2207050. Laurent (Nokia): provides r01
Sang-Jun (Samsung) provides r02.
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R00 and R02; suggests to concentrate on the conclusions
Sang-Jun prefers r02 but can live with r01 to make progress.
==== 9.X, 10.X Final Deadline ====
Revised
9.2 S2-2207050 P-CR Approval 23.700-74: Evaluation for FS_GMEC KI#5 Samsung Rel-18 Revision of S2-2206107r01. Approved Approved
9.2 S2-2206111 P-CR Approval 23.700-74: Conclusion for FS_GMEC KI#5 Samsung, Huawei Rel-18 CC#4: r03 + changes proposed. r03 agreed. Revised to S2-2207051. Sang-Jun (Samsung) proposes to use S2-2206111 for KI#5 conclusions, and to merge S2-2205487 into S2-2206111.
Laurent (Nokia): provides r01
Sebastian (Qualcomm) objects to r00 and supports r01
Heng (china Telecom) comment on solution#7
Sang-Jun (Samsung) provides r02, provides answers to Sebastian (Qualcomm) and Laurent (Nokia) and agrees with Heng (china Telecom).
Laurent (Nokia): Comments
Stefan (Ericsson) provides r03
Sang-Jun (Samsung) replies to Stefan (Ericsson) and Laurent (Nokia), and provides r04.
Heng (China Telecom) comment .
Sungpyo (KT) agree with r04.
Wonjung (LG Uplus) is fine with r04.
Sang-Jun (Samsung) provides r05 which has small updates on top of r04.
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R00, R02, R04, R05; proposes as a way forward postdealine r06V1 based on R03 (text discussed offline)
Stefan (Ericsson) objects to R00, R02, R04, R05; provides r06V2 in DRAFTS
Sang-Jun (Samsung) provides r06V3 in DRAFTS.
Heng(China Telecom) provides r06V4 in DRAFTS.
Sang-Jun (Samsung) to go with r03 + Changes. (1 Replace, Add 1 sentence and 5 bullets, co-signer) as discussed offline.
Sebastian (Qualcomm) is ok with r01, objects to other versions; not ok (yet) with proposed changes
Sang-Jun (Samsung) repilies to Sebastian (Qualcomm), and provides r06V5 (r03+changes: marked in the mail text) in DRAFTS.
Sebastian (Qualcomm) replies; not yet ok with the changes proposed by Samsung
Sang-Jun (Samsung) repliese to Sebastian (Qualcomm).
Based on S2-2206111r03:
+ Replace 'Solution #6 and Solution #17 shall be the baseline for the solution' with 'In case when Application is capable to replicate multiple copies of the data, the following are way forwards'
+ Add 'In case when Application is not capable to replicate multiple copies of the data, the following are way forwards.'
+ Add 5 bullents:
- UE establishes a PDU Session to a DNN/S-NSSAI, as per R17 specifications. This can be a special DNN/S-NSSAI configured by the operator for e.g. an electrical system.
- Each group and group combination is associated with a separate multicast address
- Application sends traffic to a multicast address depending on what group(s) it wants to target.his allows an application to send a single packet reaching multiple destinations and also multiple groups.
- The network configures a QoS policy for each UE where a multicast address is associated with a QoS level. The QoS level is set according to the QoS requirements for the group(s) the multicast address represents. Corresponding QoS Flow(s) is activated on each UE's PDU Session, as needed.
- Application sends one UL copy to the multicast address representing the destination group(s), and with the corresponding QoS. Multicast packet forwarding takes place as per existing functionality.
+ add co-signer.
Sebastian (Qualcomm) objects to last proposal by Samsung
Sebastian (Qualcomm) proposes to use r03 + Replace 'Solution #6 and Solution #17 shall be the baseline for the solution' with 'In case when Application is capable to replicate multiple copies of the data, the following are way forwards'
+ Add 'In case when Application is not capable to replicate multiple copies of the data, the following are way forwards.'
+ Add 5 bullets and a NOTE:

- UE establishes a PDU Session to a DNN/S-NSSAI, as per R17 specifications. This can be a special DNN/S-NSSAI configured by the operator for e.g. an electrical system.
- Each group and group combination is associated with a separate multicast address
- Application sends traffic to a multicast address depending on what group(s) it wants to target. This allows an application to send a single packet reaching multiple destinations and also multiple groups.
- The network configures a QoS policy for each UE where a multicast address is associated with a QoS level. The QoS level is set according to the QoS requirements for the group(s) the multicast address represents. Corresponding QoS Flow(s) is activated on each UE's PDU Session, as needed.
- Application sends one UL copy
- NOTE: No normative changes will result from this conclusion.
Sebastian (Qualcomm) objects to last proposal by Samsung
Sebastian (Qualcomm) proposes to use r03 + Replace 'Solution #6 and Solution #17 shall be the baseline for the solution' with 'In case when Application is capable to replicate multiple copies of the data, the following are way forwards'
+ Add 'In case when Application is not capable to replicate multiple copies of the data, the following are way forwards.'
+ Add 5 bullets and a NOTE:

- UE establishes a PDU Session to a DNN/S-NSSAI, as per R17 specifications. This can be a special DNN/S-NSSAI configured by the operator for e.g. an electrical system.
- Each group and group combination is associated with a separate multicast address
- Application sends traffic to a multicast address depending on what group(s) it wants to target. This allows an application to send a single packet reaching multiple destinations and also multiple groups.
- The network configures a QoS policy for each UE where a multicast address is associated with a QoS level. The QoS level is set according to the QoS requirements for the group(s) the multicast address represents. Corresponding QoS Flow(s) is activated on each UE's PDU Session, as needed.
- Application sends one UL copy
- NOTE: No normative changes will result from this conclusion.
Sang-Jun (Samsung) replies to Sebastian (Qualcomm).
==== 9.X, 10.X Final Deadline ====
Sang-Jun (Samsung) proposes to modify a little the changes to Sebastian (Qualcomm). Bsed on r03 + Replace 'Solution #6 and Solution #17 shall be the baseline for the solution' with 'In case when Application is capable to replicate multiple copies of the data, the following are way forwards'
+ Add 'In case when Application is not capable to replicate multiple copies of the data, the following are way forwards.'
+ Add 5 bullets and a NOTE:

- UE establishes a PDU Session to a DNN/S-NSSAI, as per R17 specifications. This can be a special DNN/S-NSSAI configured by the operator for e.g. an electrical system.
- Each group and group combination is associated with a separate multicast address
- Application sends traffic to a multicast address depending on what group(s) it wants to target. This allows an application to send a single packet reaching multiple destinations and also multiple groups.
- The network configures a QoS policy for each UE where a multicast address is associated with a QoS level. The QoS level is set according to the QoS requirements for the group(s) the multicast address represents. Corresponding QoS Flow(s) is activated on each UE's PDU Session, as needed.
- Application sends one UL copy
- NOTE: No normative changes may result from this conclusion.
Sebastian (Qualcomm) comments
Sang-Jun (Samsung) replies to Sebastian (Qualcomm) and propoes to go with Qianghua (Huawei)'s suggest.
NOTE: No normative changes may result from this conclusion.
->
NOTE: No NF nor interface impacts are expected for normative changes, except that conclusions in clause 8.1 may be used to support QoS policy result from this conclusion.
Revised
9.2 S2-2207051 P-CR Approval 23.700-74: Conclusion for FS_GMEC KI#5 Samsung, Huawei Rel-18 Revision of S2-2206111r03. Approved Approved
9.2 - - - Merged documents and Documents exceeding TU Budget - - Docs:=7 -
9.2 S2-2206280 P-CR Approval 23.700-74: 23.700-74 KI#4, New Sol: Group level session transfer between SMFs for VN group communication CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2205862 P-CR Approval 23.700-74: KI#1: Evaluation and conclusion Ericsson Rel-18 Not Handled Merged to S2-2206548
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2206217 P-CR Approval 23.700-74: Conclusion for KI#1 service area China Mobile Rel-18 Not Handled Merged to S2-2206548
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2206715 P-CR Approval 23.700-74: KI#1, evaluation and conclusion for the service area restriction ZTE Rel-18 Not Handled Merged to S2-2206548
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2205486 P-CR Approval 23.700-74: Conclusion for KI 4 Nokia, Nokia Shanghai Bell Rel-18 Not Handled Merged to S2-2206112 Laurent (Nokia): is OK to merge in 6112 as suggested by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2206109 P-CR Approval 23.700-74: Evaluation for FS_GMEC KI#4 Samsung Rel-18 Not Handled Merged to S2-2206553 Laurent (Nokia): objects to any version of 6109 for it to be merged in 6553 (Rapporteur proposal)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.2 S2-2205487 P-CR Approval 23.700-74: Conclusion for KI 5 Nokia, Nokia Shanghai Bell Rel-18 Not Handled Merged to S2-2206111 Laurent (Nokia): OK to merge in 6111 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.3 - - - Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) - - Docs:=40 -
9.3 - - - Liaisons - - Docs:=2 -
9.3 S2-2205467 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) Response drafted in S2-2206710. Postponed Apostolis (Lenovo) provides comments.
Apostolis (Lenovo) provides additional comments.
Marco (Huawei) comment to Apostolis (Lenovo)
Lalith(Samsung) provides r01.
Dieter (Deutsche Telekom) provides comments
Qian (Ericsson) comments that the tdoc in this thread shall be 5647??.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm): this is an LS in, and should be either marked as noted/replied or postponed to the next meeting.
Dieter (Deutsche Telekom): as this LS asks for an answer and there is no agreed answer at this meeting it should be marked as postponed to the next meeting
Postponed
9.3 S2-2206710 LS OUT Approval [DRAFT] Reply LS on BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) Deutsche Telekom Response to S2-2205467. Postponed Florin (Broadcom) comments and requests clarifications.
Dario (Qualcomm) points out that the approval of this LS is pending the decision on 5898.
==== 9.X, 10.X Revisions Deadline ====
Florin (Broadcom) shares a similar opinion with Dario (Qualcomm) and
objects to the current version r00. We cannot conclude on this reply
before we can conclude on issues like the ones in 5898.
Dario (Qualcomm) is not OK with r00 until the issue w/ 5898 is not resolved.
Rainer (Nokia) agrees with Dario (Qualcomm) to postpone the reply LS.
==== 9.X, 10.X Final Deadline ====
Postponed
9.3 - - - KI and assumption updates - - Docs:=2 -
9.3 S2-2205898 P-CR Approval 23.700-53: KI #2, Resolution of editor s note Telecom Italia, Deutsche Telekom AG, Rel-18 Noted Apostolis (Lenovo) provides comments.
Stefan (Ericsson) provides comments
Marco (Huawei) provides comments
Dario (Qualcomm) comments
Florin (Broadcom) provides comments
Myungjune (LGE) comments
Rainer (Nokia) comments.
Dieter (Deutsche Telekom) provides comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.3 S2-2206682 P-CR Approval 23.700-53: Architecture and assumption for HO on same RAT-type supported by MOBIKE Huawei, HiSilicon Rel-18 Approved Marco(Huawei) answers to Stefan (Ericsson)
Rainer (Nokia) comments.
Stefan (Ericsson) asks questions
Marco (Huawei) answers to Rainer (Nokia)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.3 - - - KI#2 - Solution updates / new solutions - - Docs:=5 -
9.3 S2-2205560 P-CR Approval 23.700-53: KI#2 Sol#3.5 Update to enable asynchronized redundant traffic steering mode Alibaba Group Rel-18 Revision of (Postponed) S2-2203810 from S2#151E. CC#4: r03 proposed. Noted Dario (Qualcomm) asks question for clarification
Xiaobo Yu (Alibaba) provides clarification to Dario (Qualcomm)
Stefan (Ericsson) provides comments
Xiaobo Yu (Alibaba) provides r01 and replies to Stefan (Ericsson)
Guanzhou (InterDigital) still thinks the solution is not in study scope.
Xiaobo Yu (Alibaba) replies to the comments from Apostolis (Lenovo).
Xiaobo Yu (Alibaba) provides r01 and replies to Guanzhou (InterDigital) that the solution addresses the KI#2 and KI#3 which is in the scope of this study.
Guanzhou (InterDigital) responds to Xiaobo (Alibaba). points out r02 instead r01 is provided in his previous email and asks for guidance how to treat r02.
Xiaobo Yu (Alibaba) provide r03 and replies to the comments from Guanzhou (InterDigital) regarding r02
==== 9.X, 10.X Revisions Deadline ====
Noted
9.3 S2-2205899 P-CR Approval 23.700-53: KI#2 Sol2.1 Update Deutsche Telekom AG Rel-18 WITHDRAWN Apostolis (Lenovo) asks questions and kindly requests changes.
Florin (Broadcom) requests clarifications and suggests updates
Dieter (Deutsche Telekom) provides answers and r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Withdrawn
9.3 S2-2205900 P-CR Approval 23.700-53: KI #2, New Sol: Re-ordering Deutsche Telekom AG Rel-18 Noted Apostolis (Lenovo) provides r01.
Dieter (Deutsche Telekom) provides r02.
Florin (Broadcom) provides comments and requests updates on the current proposal.
==== 9.X, 10.X Revisions Deadline ====
Florin (Broadcom) provides comments and requests this contribution to be noted as he objects to the original contribution as well as the revisions in 01 and 02
==== 9.X, 10.X Final Deadline ====
Noted
9.3 S2-2206759 P-CR Approval 23.700-53: Updates to solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP Lenovo, Apple, Nokia, Nokia Shanghai Bell, Broadcom, Tencent, Charter Communications Rel-18 Noted Susan (Huawei) raises questions and comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.3 S2-2206766 P-CR Approval 23.700-53: Updates to solution #2.3: MPQUIC steering functionality using IP proxying over HTTP Lenovo Rel-18 Noted Susan (Huawei) raises similar questions and comments as to S2-22-6759.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.3 - - - KI#3 - Solution updates / new solutions - - Docs:=4 -
9.3 S2-2206165 P-CR Approval 23.700-53: KI#3, update Sol#3.1 to support redundant transmission between two non-3GPP accesses Huawei, HiSilicon Rel-18 Noted Dario (Qualcomm) comments
Stefan (Ericsson) provides comments
Yishan (Huawei) answers to Dario (Qualcomm) and Stefan (Ericsson)
Rainer (Nokia) asks for clarification.
Yishan (Huawei) answers to Rainer (Nokia)
Guanzhou (InterDigital) shares the view with Stefan(Ericsson) and Dario(Qualcomm)
Yishan (Huawei) responds to Myungjune (LGE)
Myungjune comments
Myungjune (LGE) replies to Yishan (Huawei)
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) proposes to note this pCR.
Myungjune (LGE) proposes to note this pCR.
Stefan (Ericsson) also propose to note
Guanzhou (InterDigital) also proposes to note this.
==== 9.X, 10.X Final Deadline ====
Noted
9.3 S2-2206780 P-CR Approval 23.700-53: KI#3, Sol #3.3 update: New traffic duplication steering mode Nokia, Nokia Shanghai Bell Rel-18 Approved Stefan (Ericsson) provides comments
Rainer (Nokia) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.3 S2-2206781 P-CR Approval 23.700-53: KI#3, new Sol #3.y: Suspending the redundancy steering mode Nokia, Nokia Shanghai Bell Rel-18 Approved Dario (Qualcomm) asks about benefit of this solution wrt. dynamic RSM.
Rainer (Nokia) replies.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) thanks and is fine w/ r00.
==== 9.X, 10.X Final Deadline ====
Approved
9.3 S2-2206872 P-CR Approval 23.700-53: Ki#3: Sol. 3.4 update Qualcomm Incorporated Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.3 - - - KI#5 - Solution updates - - Docs:=4 -
9.3 S2-2205855 P-CR Approval 23.700-53: KI #5, Sol #5.5: Update to resolve ENs and align with mobility registration procedure Ericsson Rel-18 Approved Stefan (Ericsson) replies to Marco
Marco (Huawei) ask questions
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.3 S2-2206166 P-CR Approval 23.700-53: KI#5, update Sol#5.1 to add an indication sent by AMF to SMF Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.3 S2-2206921 P-CR Approval 23.700-53: KI#5, Solution #5.4 Update: Non-3GPP access path switching in MA PDU Session Samsung Rel-18 r03 agreed. Revised to S2-2207424. Paul R. (Charter) provides questions and comments
Stefan (Ericsson) provides questions and comments
DongYeon (Samsung) replies to Stefan and Paul R., and provides r01.
DongYeon (Samsung) provides r02.
DongYeon (Samsung) provides r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207424 P-CR Approval 23.700-53: KI#5, Solution #5.4 Update: Non-3GPP access path switching in MA PDU Session Samsung Rel-18 Revision of S2-2206921r03. Approved Approved
9.3 - - - KI#6 - Solution updates - - Docs:=1 -
9.3 S2-2205953 P-CR Approval 23.700-53: KI #6, Sol #6.1 Update LG Electronics Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.3 - - - KI#2 - Evaluation / conclusions - - Docs:=5 -
9.3 S2-2206691 P-CR Approval 23.700-53: KI#2: Evaluation of solutions InterDigital Rel-18 r01 agreed. Revised to S2-2207425. Xiaobo Yu (Alibaba) provides comments.
Dieter (Deutsche Telekom) provides comments
Guanzhou (InterDigital) responds to Dieter(DT) and Xiaobo(Alibabab) and provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207425 P-CR Approval 23.700-53: KI#2: Evaluation of solutions InterDigital Rel-18 Revision of S2-2206691r01. Approved Approved
9.3 S2-2206699 P-CR Approval 23.700-53: KI#2: Conclusions for KI#2 InterDigital Rel-18 Noted Dieter (Deutsche Telekom) provides comments
Guanzhou (InterDigital) provides r01.
Stefan (Ericsson) comments
Guanzhou (InterDigital) provides r02.
Dario (Qualcomm) provides r03
Guanzhou (InterDigital) OK with r03.
==== 9.X, 10.X Revisions Deadline ====
Apostolis (Lenovo) requests to postpone this paper.
==== 9.X, 10.X Final Deadline ====
Noted
9.3 S2-2206769 P-CR Approval 23.700-53: Evaluation and Conclusions for KI#2 Lenovo, Motorola Mobility, Apple, Broadcom, Tencent Rel-18 CC#4: Solution update should be progressed and the work continued at the next meeting. Noted Apostolis (Lenovo) provides r01.
Susan (Huawei) propose to postpone this paper to next meeting.
Rainer (Nokia) replies.
Susan (Huawei) replies to Rainer (Nokia).
Apostolis (Lenovo) provides r02 and proposes to consider this in CC#4.
==== 9.X, 10.X Revisions Deadline ====
Dieter (Deutsche Telekom) objects to all revisions of this paper as commented earlier and copied here again.
Noted
9.3 S2-2206871 P-CR Approval 23.700-53: KI#2: Way forward Qualcomm Incorporated, Meta USA, LG Electronics, Apple, Tencent, Ericsson, Lenovo Rel-18 Noted Dieter (Deutsche Telekom) provides comments and proposes to note this paper
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.3 - - - KI#3 - Evaluation / conclusions - - Docs:=9 -
9.3 S2-2205856 P-CR Approval 23.700-53: KI#3: views on evaluation and conclusion Ericsson Rel-18 Merged into S2-2207427 Apostolis (Lenovo) proposes to remove the Conclusions from this paper and use the document 6770 as the baseline for the KI#3 conclusions.
Stefan (Ericsson) ok to merge conclusion part into 6770 and evolution part into 6561
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206561 P-CR Approval 23.700-53: KI#3: Evaluation for redundant traffic steering Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2207426, merging and S2-2206777 Apostolis (Lenovo) provides r01
Rainer (Nokia) provides r02.
Stefan (Ericsson) provides r03 and proposes that the evaluation part of 5856 is considered merged into 6561
Guanzhou (InterDigital) provides r04.
Dario (Qualcomm) comments and provides r05.
Susan (Huawei) provides r06.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) objects to r06 and proposes to go with r05 (potentially with an additional EN).
Susan (Huawei) provides r07, with double ENs added on top of r05 for 7.x.1 and 7.x.2 respectively, and asks for CC#4 or CC#5 discussion/approval: Editor's note: Evaluation of the duplication factor is FFS.
Rainer (Nokia) replies.
Susan (Huawei) replies to Rainer (Nokia).
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207426 P-CR Approval 23.700-53: KI#3: Evaluation for redundant traffic steering Huawei, HiSilicon Rel-18 Revision of S2-2206561r05, merging and S2-2206777. Approved Approved
9.3 S2-2206562 P-CR Approval 23.700-53: KI#3: Conclusion on KI#3 Huawei, HiSilicon Rel-18 Merged into S2-2207427 Apostolis (Lenovo) proposes to merge this paper into 6770 and use 6770 as the baseline for the KI#3 conclusions.
Susan (Huawei) agrees to merge this paper into 6770 and use 6770 as the baseline for the KI#3 conclusions.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206770 P-CR Approval 23.700-53: Conclusions for KI#3 Lenovo, InterDigital Rel-18 r09 agreed. Revised to S2-2207427, merging S2-2205856, S2-2206562, S2-2206778 and S2-2206873 Xiaobo Yu (Alibaba) provides comments.
Apostolis (Lenovo) provides r01.
Yishan (Huawei) cannot accept r01 and provides r02 based on r00
Xiaobo Yu (Alibaba) provides r03 based on r02.
Stefan (Ericsson) provides r04
Rainer (Nokia) provides r05.
Dario (Qualcomm) comments and provides r06
Apostolis (Lenovo) responds to Rainer's (Nokia) question.
Stefan (Ericsson) provides comments to Dario
Susan (Huawei) agrees with Stefan (Ericsson) and cannot accept r06.
Rainer (Nokia) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207427 P-CR Approval 23.700-53: Conclusions for KI#3 Lenovo, InterDigital Rel-18 Revision of S2-2206770r09, merging S2-2205856, S2-2206562, S2-2206778 and S2-2206873. Approved Approved
9.3 S2-2206777 P-CR Approval 23.700-53: KI#3: Evaluation of solutions on support of redundant traffic steering Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207426 Marco (Huawei) proposes to merge with document in S2-2206561
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206778 P-CR Approval 23.700-53: KI#3: Conclusions for support of redundant traffic steering Nokia, Nokia Shanghai Bell, Qualcomm Incorporated Rel-18 Merged into S2-2207427 Apostolis (Lenovo) proposes to merge this paper into 6770 and use 6770 as the baseline for the KI#3 conclusions.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206873 P-CR Approval 23.700-53: Ki#3: Conclusion on RSM trigger Qualcomm Incorporated Rel-18 Merged into S2-2207427 Xiaobo Yu(Alibaba) asks for clarification.
Apostolis (Lenovo) proposes to merge this paper into 6770 and use 6770 as the baseline for the KI#3 conclusions.
Dario (Qualcomm) replies to Xiaobo.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) confirms this is merged into 6770.
==== 9.X, 10.X Final Deadline ====
Merged
9.3 - - - KI#5 - Evaluation / conclusions - - Docs:=7 -
9.3