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 S2-2205954 P-CR Approval 23.700-53: Evaluation for KI#5 LG Electronics Rel-18 Merged into S2-2207428 Apostolis (Lenovo) proposes to merge this document into 6167.
Myungjune (LGE) is ok to merge this document into 6167.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2205955 P-CR Approval 23.700-53: Conclusion for KI#5 LG Electronics Rel-18 Merged into S2-2207429 Marco (Huawei) proposed to merge S2-2205955, S2-2206734 & S2-2206167 for conclusion part
Apostolis (Lenovo) proposes to merge this document into 6734.
Myungjune (LGE) is ok to merge this document into 6734.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206167 P-CR Approval 23.700-53: KI #5 Evaluation and conclusion for switching traffic of an MA PDU Session between two non-3GPP access paths Huawei, HiSilicon Rel-18 r07 agreed. Revised to S2-2207428, merging S2-2205954, and S2-2206729 Marco (Huawei) proposed to merge S2-2205955, S2-2206734 & S2-2206167 for conclusion part
Paul R. (Charter) response to Apostolis (Lenovo), we are fine with merging the evaluation papers for KI5.
Provided 6167r02
Myungjune (LGE) provides r03.
Stefan (Ericsson) provides r04
Paul R (Charter) questions for clarification to Marco (Huawei) and Myungjune (LGE).
Marco (Huawei) provides r05 and answer to comments.
Myungjune (LGE) answers to Paul R (Charter).
DongYeon (Samsung) provides r06.
Myungjune (LGE) asks question on r06.
Yishan (Huawei) provides r07
DongYeon (Samsung) replies to Myungjune (LGE).
Paul R (Charter) replies to Myungjune (LGE).
Paul R (Charter) further replies to Myungjune (LGE).
Myungjune (LGE).replies to Paul R (Charter)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207428 P-CR Approval 23.700-53: KI #5 Evaluation and conclusion for switching traffic of an MA PDU Session between two non-3GPP access paths Huawei, HiSilicon Rel-18 Revision of S2-2206167r07, merging S2-2205954, and S2-2206729. Approved Approved
9.3 S2-2206729 P-CR Approval 23.700-53: Evaluation of KI#5 Solutions Charter Communications, Lenovo Rel-18 Merged into S2-2207428 Marco (Huawei) proposes that evaluation is merged in S2-2206167
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.3 S2-2206734 P-CR Approval 23.700-53: Conclusion for KI#5 Charter Communications, Lenovo Rel-18 r06 agreed. Revised to S2-2207429, merging and S2-2205955 Marco (Huawei) disagree on bullet 1) which selects the path switching during registration.
Paul R (Charter) agrees with proposal to merge S2-2205955, S2-2206734 & S2-2206167 for conclusion.
Provides comments to S2-2206734r01 and provides S2-2206734r02
Marco (Huawei) proposed to merge S2-2205955, S2-2206734 & S2-2206167 for conclusion part
Apostolis (Lenovo) provides r01 and proposes to take this document as the baseline for KI#5 conclusions.
Paul R (Charter) further replies to Stefan
Paul R (Charter) provides r07 on top of r05
==== 9.X, 10.X Revisions Deadline ====
DongYeon (Samsung) supports 07.
TAO(VC) it shows to me r07 was provided just after the revision deadline. Therefore, please indicate the changes on top of r05, which we will try to agree with
Stefan (Ericsson) explains about r06: was provided before deadline but was mistakenly announced as r05
Paul R (Charter) withdraws r07 which was late and based on the incorrect revision baseline. Charter supports r06 from Ericsson.
Omkar (CableLabs) supports r06 from Ericsson.
==== 9.X, 10.X Final Deadline ====
Revised
9.3 S2-2207429 P-CR Approval 23.700-53: Conclusion for KI#5 Charter Communications, Lenovo Rel-18 Revision of S2-2206734r06, merging and S2-2205955. Approved Approved
9.3 - - - KI#6 - Evaluation / conclusions - - Docs:=1 -
9.3 S2-2206560 P-CR Approval 23.700-53: KI#6: Conclusion on KI#6 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 - - - Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) - - Docs:=75 -
9.4 - - - KI#1 - - Docs:=11 -
9.4 - - - Evaluation, conclusions - - Docs:=2 -
9.4 S2-2205796 P-CR Approval 23.700-08: KI #1: Evaluation and Conclusion of Key Issue #1 Ericsson, MediaTek Inc., OPPO, LG Electronics Rel-18 CC#4: Way forward: r00, removing Option 1 and related editor's note in r01. Revised to S2-2207706. Chia-Lin (MediaTek) prefers Option 1.
Fei (OPPO) prefers option1
Rainer (Nokia) comments, prefers option 2.
Peter Hedman (Ericsson) request feedback on open issue and ask how to resolve it e.g. whether to do SoH
Yishan (Huawei) prefers Option 2.
Peter Hedman (Ericsson) proposes to check option 1 vs option 2 at CC with SoH
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) informs that slides for SoH been uploaded
Saso (Intel) prefers Option 2
Revised
9.4 S2-2207706 P-CR Approval 23.700-08: KI #1: Evaluation and Conclusion of Key Issue #1 Ericsson, MediaTek Inc., OPPO, LG Electronics Rel-18 Revision of S2-2205796. Approved Approved
9.4 - - - KI#2 - - Docs:=14 -
9.4 - - - Solutions - - Docs:=1 -
9.4 S2-2205556 DISCUSSION Information Discussion Paper on Sol#6, Sol#20 and Sol#21 CableLabs Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.4 - - - Evaluation, conclusions - - Docs:=8 -
9.4 S2-2205506 P-CR Approval 23.700-08: KI#2: Evaluation of Solutions for KI#2 and initial conclusions Intel, Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207707. Peter Hedman (Ericsson) provides comments
Saso (Intel) provides r01.
==== 9.X, 10.X Revisions Deadline ====
Qianghua (Huawei) comments that r01 needs to remove some evaluation text for sol#19, which we cannot agree now.
Peter Hedman (Ericsson) ok with r01, or with r01+remove 'Configuration of IP address ranges in the N3IWF adds lot of complexity without clear benefits.'
Saso (Intel) proposes to quickly open in CC#4.
Saso (Intel) proposes to agree r01 + removal of 'Configuration of IP address ranges in the N3IWF adds lot of complexity without clear benefits.'. If needed, take a quick check on CC#5.
Qianghua (Huawei) only OK with r01+ removal of 'Configuration of IP address ranges in the N3IWF adds lot of complexity without clear benefits.'
Rainer (Nokia) ok to remove the sentence from r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207707 P-CR Approval 23.700-08: KI#2: Evaluation of Solutions for KI#2 and initial conclusions Intel, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205506r01. Approved Approved
9.4 S2-2206174 DISCUSSION Discussion KI#2, Discussion on conclusion on KI#2 Huawei, HiSilicon Rel-18 Noted Haris(Qualcomm) provides comments
Josep (DT) comments on support for UE onboarding via SNPN non-3GPP access.
Yishan (Huawei) answers to Haris (Qualcomm)
Haris(Qualcomm) responds
Saso (Intel) comments
Yishan (Huawei) responds to Haris (Qualcomm) and Saso (Intel)
Huan (vivo) supports for onboarding via non-3GPP access/N3IWF to SNPN
Josep (DT) replies to Huan, provides r01.
Rainer (Nokia) comments.
Yishan (Huawei) supports the scenario mentioned by Huan (vivo) and answers to Josep (DT) and Rainer (Nokia)
Josep (DT) replies to Yishan (Huawei).
Yishan (Huawei) replies to Josep (DT) and asks for questions.
Josep (DT) comments.
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) indicates that this document is discussion paper and should be noted
Peter Hedman (Ericsson) the paper is assigned as DP and meant to be taken into account when discussing related P-CR i.e. we can note the paper
Saso (Intel) agrees with Peter and Haris that the paper should be NOTED.
==== 9.X, 10.X Final Deadline ====
Noted
9.4 S2-2205764 LS OUT Approval [DRAFT] Questions for SUCI protection requirements for non-3GPP (WLAN) access to SNPN Qualcomm Rel-18 Revised to S2-2207700.
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207700 LS OUT Approval [DRAFT] Questions for SUCI protection requirements for non-3GPP (WLAN) access to SNPN Qualcomm Rel-18 Revision of S2-2205764. Approved Approved
9.4 S2-2206558 P-CR Approval 23.700-08: KI#2: Initial conclusions Intel, Nokia, Nokia Shanghai Bell Rel-18 r17 agreed. Revised to S2-2207708. Omkar (CableLabs) provides r01 and asks for clarification
Josep (DT) replies to Rainer (Nokia).
Rainer (Nokia) comments.
Josep (DT) retracts r02, provides r03.
Josep (DT) provides r02.
Saso (Intel) comments.
Omkar (CableLabs) responds with a suggestion
Genadi (Lenovo) comments on the need to expand the NSWO access authorization and proposes r04.
Marco (Huawei) ask clarification on wireline support.
Yishan (Huawei) proposes r05
Rainer (Nokia) cannot accept r05.
Yishan (Huawei) replies to Rainer (Nokia)
Rainer (Nokia) replies.
Yishan (Huawei) provides r06 based on comments from Rainer (Nokia)
Huan (vivo) provides r07
Saso (Intel) provides r08
Peter Hedman (Ericsson) provides comments and questions
Saso (Intel) provides r09
Omkar (CableLabs) provides r11
Marco (Huawei) provides r10 and asks clarification to Saso (intel)
Haris(Qualcomm) indicates which parts are not acceptable in r10 and r11 and which parts need to be improved
Qianghua (Huawei) provides comments on r09
Saso (Intel) replies to Haris, Marco, Qianghua.
Rainer (Nokia) agrees with Saso (Intel).
Chunhui(Xiaomi) clarifies the new RAT Type of untrusted non-3GPP satellite in S2-2206090.
Josep (DT) is also against adding a new RAT type.
Yishan (Huawei) replies to Haris (Qualcomm)
Genadi (Lenovo) replies to Haris (Qualcomm) and proposed an improvement.
Haris(Qualcomm) responds to Yishan (Huawei)
Saso (Intel) provides r12 (unzipped, as I am experiencing IT issues with zip)
Rainer (Nokia) is ok with r13.
Saso (Intel) provides r13 to fix the EN on GIN.
Peter Hedman (Ericsson) provides r14
Yishan (Huawei) is ok to move GIN to the EN and resolve it in the next meeting.
Rainer (Nokia) agrees with r14.
Saso (Intel) is ok with r14.
Haris(Qualcomm) asks question on r14 and indicates text that is not acceptable
Saso (Intel) provides r15 removing NOTE 3.
Genadi (Lenovo) provides reference to Haris (Qualcomm) to old email and also r16.
Saso (Intel) provides r17.
Haris(Qualcomm) comments on r16
==== 9.X, 10.X Revisions Deadline ====
Genadi (Lenovo) comments to Haris(Qualcomm).
Genadi (Lenovo) can live with r17.
Haris(Qualcomm) is ok with r17, r15, r0. Objects to all other revisions
Peter Hedman (Ericsson) ok with r17, and agree that normative phase is not meant for continuing the study
Rainer (Nokia) is ok with r17.
Huan (vivo) is ok with r17.
Marco (Huawei) comment to Peter Hedman (Ericsson)
Marco (Huawei) ok with R17, r15, r13 and r12 and object any other versions
Omkar (CableLabs) ok with r17, can live with any revision post r11
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207708 P-CR Approval 23.700-08: KI#2: Initial conclusions Intel, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206558r17. Approved Approved
9.4 S2-2206604 DISCUSSION Approval KI#2 Discussion on evaluation for KI#2 for onboarding when using untrusted non-3GPP architecture Vivo Rel-18 Noted Josep (DT) proposes to use 6174 as basis for discussion and mark this discussion paper as noted.
Huan(vivo) agrees to use 6174 as basis for discussion and clarifies
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.4 - - - KI#3 - - Docs:=20 -
9.4 - - - Solutions - - Docs:=1 -
9.4 S2-2206281 P-CR Approval 23.700-08: 23.700-08 KI #3,#4,#5, Sol#13: Update to resolve the Editor's notes that how PCF of hosting network updates the parameters to AMF and SMF CATT Rel-18 Approved Peter Hedman (Ericsson) provides questions for clarification
==== 9.X, 10.X Revisions Deadline ====
Liping (CATT) replies to Peter Hedman (Ericsson)
Peter Hedman (Ericsson) ok with r00
==== 9.X, 10.X Final Deadline ====
Approved
9.4 - - - Evaluation, conclusions - - Docs:=2 -
9.4 S2-2206902 P-CR Approval 23.700-08: PCR_5G_eNPN_Ph2- evaluation for key issue#3 Xiaomi Rel-18 r02 agreed. Revised to S2-2207709. Peter Hedman (Ericsson) provides r02
Huan (vivo) comments and provides r01
==== 9.X, 10.X Revisions Deadline ====
Jianning (Xiaomi) is ok with r02
Huan (vivo) is OK to r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207709 P-CR Approval 23.700-08: PCR_5G_eNPN_Ph2- evaluation for key issue#3 Xiaomi Rel-18 Revision of S2-2206902r02. Approved Approved
9.4 - - - KI#4 - - Docs:=9 -
9.4 - - - Solutions - - Docs:=23 -
9.4 S2-2206838 P-CR Approval 23.700-08: Solution #10 additions for enforcing access in Subnetwork of SNPN hosting network Qualcomm Inc. Rel-18 Approved Jianning (Xiaomi) provides question for clarification
Huan (vivo) asks question for clarification
Miguel (Qualcomm) replies to Huan (vivo)
Peter Hedman (Ericsson) provides comments
Josep (DT) comments.
Miguel (Qualcomm) clarifies to Josep (DT)
Miguel (Qualcomm) responds to Peter (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments, ok with r00
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206192 P-CR Approval 23.700-08: Update Sol#18 and proposal for removing EN of Sol#12 Samsung Rel-18 r03 agreed. Revised to S2-2207710. Yishan (Huawei) provides r01
Pallab (Nokia) comments on r01 and has concerns with the solution
Yishan (Huawei) is confused about comments from Pallab (Nokia)
Pallab (Nokia) responds
Yishan (Huawei) asks for more clarification
Peter Hedman (Ericsson) provides r02
Pallab (Nokia) responds and requests for a revision
Yishan (Huawei) replies to Pallab (Nokia)
Naman (Samsung) replies to Peter Hedman (Ericsson)
Pallab (Nokia) responds Yishan (Huawei)
Yishan (Huawei) replies to Pallab (Nokia) and provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207710 P-CR Approval 23.700-08: Update Sol#18 and proposal for removing EN of Sol#12 Samsung Rel-18 Revision of S2-2206192r03. Approved Approved
9.4 S2-2206243 P-CR Approval 23.700-08: 23.700-08: Update to Solution #12 Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2207711. Pallab (Nokia) provides r01
Josep (DT) asks question for clarification.
Huan (vivo) asks for clarifications
Pallab (Nokia) responds to Huan (vivo), Josep (DT) and provides r02
Peter Hedman (Ericsson) provides questions
Pallab (Nokia) responds to Peter Hedman (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207711 P-CR Approval 23.700-08: 23.700-08: Update to Solution #12 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206243r02. Approved Approved
9.4 S2-2206601 P-CR Approval 23.700-08: KI#4: Update to Solution #14 Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2205801 P-CR Approval 23.700-08: KI #4, Sol #24: update to resolve the editor's note Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2205802 P-CR Approval 23.700-08: KI #4, KI #6, Sol #25: update to resolve the editor's note Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206698 P-CR Approval 23.700-08: KI#4, Sol#26: update to address the Editor notes Futurewei Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206282 P-CR Approval 23.700-08: 23.700-08 KI#4,#5, Sol#27: Update to resolve the Editor's notes to extend the LADN information CATT Rel-18 r01 agreed. Revised to S2-2207712. Myungjune (LGE) provides comments and questions.
Liping Wu (CATT) replies to Myungjune.
Myungjune.(LGE) replies to Liping Wu (CATT)
Liping Wu (CATT) replies to Myungjune.(LGE)
Myungjune.(LGE) responses to Liping Wu (CATT)
Myungjune.(LGE) provides r01.
Liping(CATT) provides r02.
Myungjune (LGE) comments on r02.
==== 9.X, 10.X Revisions Deadline ====
Myungjune (LGE) objects r02. Only accepts r01.
Liping (CATT) accepts r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207712 P-CR Approval 23.700-08: 23.700-08 KI#4,#5, Sol#27: Update to resolve the Editor's notes to extend the LADN information CATT Rel-18 Revision of S2-2206282r01. Approved Approved
9.4 S2-2205803 P-CR Approval 23.700-08: KI #4, KI #5, Sol #35: update to ensure localized service is accessed by UE per agreement Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2205804 P-CR Approval 23.700-08: KI #4, KI #5, New Sol: Credential provisioning for access to hosting network Ericsson Rel-18 r04 agreed. Revised to S2-2207713. Guanzhou (InterDigital) asks for clarifications and provides r01
Chia-Lin (MediaTek) provides r02 based on r01
Huan (vivo) asks for clarifications
Pallab (Nokia) asks for clarifications
Peter Hedman (Ericsson) provides r03 and replies
Amanda ( Futurewei ) provide comments
Genadi (Lenovo) provides comments.
Peter Hedman (Ericsson) provides r04
Miguel (Qualcomm) asks a question
Peter Hedman (Ericsson) provides reply
==== 9.X, 10.X Revisions Deadline ====
Guanzhou (InterDigital) is OK with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207713 P-CR Approval 23.700-08: KI #4, KI #5, New Sol: Credential provisioning for access to hosting network Ericsson Rel-18 Revision of S2-2205804r04. Approved Approved
9.4 S2-2206158 P-CR Approval 23.700-08: New solution for Key Issue#4. Provisioning of credentials via Hosting network Samsung Rel-18 r05 agreed. Revised to S2-2207714. Josep (DT) objects to this solution.
Guanzhou (InterDigital) shares the concern of Josep (DT)
Naman (Samsung) replies to Josep (DT) and Guanzhou (InterDigital) and provides r01
Josep (DT) asks questions for clarification.
Naman (Samsung) replies and requests for clarifications
Josep (DT) replies to Naman (Samsung).
Naman (Samsung) replies and provides r02
Josep (DT) can live with r02.
Yishan (Huawei) asks questions
Yishan (Huawei) replies to Naman (Samsung) and asks for questions
Guanzhou (InterDigital) provides some further comments.
Josep (DT) provides r03 with additional ENs that should be addressed.
Naman (Samsung) replies and provides r04
Yishan (Huawei) asks for further clarification
Josep (DT) comments.
Naman (Samsung) replies and provides r05
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207714 P-CR Approval 23.700-08: New solution for Key Issue#4. Provisioning of credentials via Hosting network Samsung Rel-18 Revision of S2-2206158r05. Approved Approved
9.4 S2-2206194 P-CR Approval 23.700-08: New solution for KI#4, Authentication and authorization for localized services Samsung Rel-18 Noted Josep (DT) asks questions for clarification.
Pallab (Nokia) comments
Naman (Samsung) replies and provides r01
Huan(vivo) comments and asks for clarifications
Josep (DT) comments.
Naman (Samsung) replies and provides r02
Yishan (Huawei) ask questions to Naman (Samsung)
Naman (Samsung) replies to Yishan (Huawei)
==== 9.X, 10.X Revisions Deadline ====
Josep (DT) objects to this solution.
==== 9.X, 10.X Final Deadline ====
Noted
9.4 S2-2206602 P-CR Approval 23.700-08: KI#4 New Sol: UE requesting for hosting network selection and access information via visiting network Vivo Rel-18 r02 agreed. Revised to S2-2207715. Jianning (Xiaomi) provide qeustions for clarification
Huan (vivo) provides feedback
Pallab (Nokia) comments and requests clarification
Huan (vivo) provides feedback and r01
Pallab (Nokia) asks for further clarification. Thinks that the solution technically does not work.
Huan (vivo) provides feedback and r02
Pallab (Nokia) thanks Huan (vivo) for r02. OK with it
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207715 P-CR Approval 23.700-08: KI#4 New Sol: UE requesting for hosting network selection and access information via visiting network Vivo Rel-18 Revision of S2-2206602r02. Approved Approved
9.4 S2-2206603 P-CR Approval 23.700-08: KI#4 New Sol: Transferring hosting network selection information from hosting network to UE s home network Vivo Rel-18 r04 agreed. Revised to S2-2207716. Pallab (Nokia) comments and requests clarification
Huan (vivo) provides feedback and r01
Pallab (Nokia) provides further comments
Huan (vivo) provides feedback and r02
Pallab (Nokia) indicates that further revision is needed to update the figure.
Huan (vivo) updates the figure and provides r03
Peter Hedman (Ericsson) provides r04
Huan (vivo) feedback and provides the correct link for r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207716 P-CR Approval 23.700-08: KI#4 New Sol: Transferring hosting network selection information from hosting network to UE s home network Vivo Rel-18 Revision of S2-2206603r04. Approved Approved
9.4 S2-2206783 P-CR Approval 23.700-08: KI #4, New Sol: Discovery and selection of Hosting network based on URSP rules and configuration information Lenovo Rel-18 Noted Naman (Samsung) provides comments and r01
Genadi (Lenovo) replies to Yishan (Huawei).
Yishan (Huawei) asks for clarification
Genadi (Lenovo) provides r02. The r02 provides a new structure of the solution to highlight the high-level principles and also to include the aspects of S2-2206783.
Yishan (Huawei) asks for further clarification
Chia-Lin (MediaTek) provides comments and cannot accept the URSP rules trigger UE automatic Hosting Selection
Genadi (Lenovo) replies to Yishan (Huawei) that the URSP rule only triggers the Hosting NW discovery, but the Hosting NW selection is performed using the Hosting NW selection information provisioned via SoR.
Genadi (Lenovo) provides comments to Chia-Lin (MediaTek) and r03 to clarify the automatic Hosting network selection.
Yishan (Huawei) asks questions to Genadi (Lenovo)
Chia-Lin (MediaTek) provides response to Genadi (Lenovo)
Huan (vivo) asks for clarification
Myungjune (LGE) provides comments.
Genadi (Lenovo) replies to Chia-Lin (MediaTek) and provides r04.
Genadi (Lenovo) replies to Myungjune (LGE).
==== 9.X, 10.X Revisions Deadline ====
Chia-Lin (MediaTek) cannot accept any version including the original one
Genadi (Lenovo) comments that the provided statements are not technical comments, but evaluation comments; and kindly asks Chia-Lin (MediaTek) to reconsider to accept the r04.
==== 9.X, 10.X Final Deadline ====
Noted
9.4 S2-2206835 P-CR Approval 23.700-08: KI #4, New Solution on top of Solution #10 to assist UE in discovering hosting network. Qualcomm Inc. Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 - - - Evaluation, conclusions - - Docs:=2 -
9.4 S2-2205798 P-CR Approval 23.700-08: KI #4: Evaluation of Key Issue #4 Ericsson Rel-18 r02 agreed. Revised to S2-2207717. Huan (vivo) comments and provides r01
Peter Hedman (Ericsson) provides comments
Huan (vivo) agrees to further discuss at next meeting
Genadi (Lenovo) provides r02.
==== 9.X, 10.X Revisions Deadline ====
Amanda ( Futurewei ) supports Ericsson and Vivo proposal to postpone this contribution and evaluation discussion to next meeting.
Peter Hedman (Ericsson) provides comments and proposes to agree r02 with the understanding that evaluation will continue at the next meeting when we also are meant to conclude the study
Huan (vivo) is OK to r02.
Amanda (Futurewei) is OK with r02.
Guanzhou (InterDigital) is OK with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207717 P-CR Approval 23.700-08: KI #4: Evaluation of Key Issue #4 Ericsson Rel-18 Revision of S2-2205798r02. Approved Approved
9.4 - - - KI#5 - - Docs:=0 -
9.4 - - - Solutions - - Docs:=7 -
9.4 S2-2206163 P-CR Approval 23.700-08: KI#5, New solution for ensuring UE access localized services in the service area/time Huawei, HiSilicon Rel-18 Approved Chia-Lin (MediaTek) provides comments
Yishan (Huawei) answers to Chia-Lin (MediaTek)
Chia-Lin (MediaTek) responds to Yishan (Huawei)
Yishan (Huawei) responds to Chia-Lin (MediaTek)
Guanzhou (InterDigital) asks questions.
Yishan (Huawei) answers to Guanzhou (InterDigital)
Yishan (Huawei) provides more clarification to Guanzhou (InterDigital)
Guanzhou (InterDigital) responds.
Yishan (Huawei) responds to Guanzhou (InterDigital)
Yishan (Huawei) replies to Chia-Lin (MediaTek)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206164 DISCUSSION Discussion KI#5, Discussion on solution on ensuring UE accesses localized service in the service area/time Huawei, HiSilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.4 S2-2206693 P-CR Approval 23.700-08: KI#5, Sol#36: update to address the Editor notes Futurewei Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206348 P-CR Approval 23.700-08: KI#5, New sol.: Access Localized Services via URSP rules MediaTek Inc. Rel-18 r03 agreed. Revised to S2-2207718. Pallab (Nokia) comments and requests clarification
Chia-Lin (MediaTek) responds to Pallab (Nokia) and provides r01
Pallab (Nokia) requests for further clarification
Pallab (Nokia) provides comments
Chia-Lin (MediaTek) responds to Pallab (Nokia) and provides r02
Liping Wu(CATT) provides comments
Chia-Lin (MediaTek) responds to Liping (CATT)
Pallab (Nokia) responds to Chia-Lin (MediaTek)
Chia-Lin (MediaTek) responds to Pallab (Nokia) and provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207718 P-CR Approval 23.700-08: KI#5, New sol.: Access Localized Services via URSP rules MediaTek Inc. Rel-18 Revision of S2-2206348r03. Approved Approved
9.4 S2-2206713 P-CR Approval 23.700-08: KI#5: Evaluation of solutions for KI#5 and conclusion InterDigital Rel-18 r09 agreed. Revised to S2-2207719. Pallab (Nokia) comments and provides r01
Josep (DT) comments on Pallab's (Nokia) r01, is of the opinion that the removed content is indeed part of the KI
Guanzhou (InterDigital) resends the ftp link of r03
Guanzhou (InterDigital) provides r03.
Marco (Huawei) comments and provides r02
Guanzhou (InterDigital) responds to Miguel (Qualcomm)
Miguel (Qualcomm) provides r04
Josep (DT) responds to Miguel (Qualcomm), provides r05.
Pallab (Nokia) provides r06.
Josep (DT) objects to r06.
Miguel (Qualcomm) asks a question to Josep (DT) on r05
Josep (DT) replies to Miguel (Qualcomm), Pallab (Nokia) provides r07.
Pallab (Nokia) replies to Josep (DT)
Genadi (Lenovo) supports the original text provided for the overlay/underlay arch conclusions and provides r08.
Peter Hedman (Ericsson) provides r09
==== 9.X, 10.X Revisions Deadline ====
Futurewei prefer r03, but can live with r09 only we consider its conclusion as partial conclusion for KI #5 and allow continue discussion the conclusion in next meeting
Peter Hedman (Ericsson) agrees that KI#5 conclusion is a partial conclusion and further work, finalization, of the conclusion will be conducted at the next meeting
Marco (Huawei) ok with r09
Guanzhou (InterDigital) is OK with r09
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207719 P-CR Approval 23.700-08: KI#5: Evaluation of solutions for KI#5 and conclusion InterDigital Rel-18 Revision of S2-2206713r09. Approved Approved
9.4 - - - KI#6 - - Docs:=0 -
9.4 - - - Solutions - - Docs:=5 -
9.4 S2-2206555 P-CR Approval 23.700-08: KI#6: Updates for solution 13 to address the KI#6 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.4 S2-2206045 P-CR Approval 23.700-08: KI #6, Sol #38: Update to remove an Editor s note and update to solution #38 NEC Rel-18 r04 agreed. Revised to S2-2207720. Myungjune (LGE) comments and provides r01.
Chia-Lin (MediaTek) provides comments
Prabhu (NEC) responds to Myungjune (LGE) and Chia-Lin (MediaTek), and provides r02.
Myungjune (LGE) provides r03.
Hiroshi (NEC) provides r04.
Ashok (Samsung) comments
Liping(CATT) provide comments and proposes to add SUPI in r04.
Yishan (Huawei) provides comments
Liping(CATT) provides comments and agree Yishan (Huawei) suggestion.
Myungjune (LGE) provides comments SUCI/SUPI is not needed.
Peter Hedman (Ericsson) provides comments
Myungjune (LGE) replies to Peter Hedman (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
Liping Wu(CATT) provides comments
Myungjune (LGE) replies Liping Wu(CATT)
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207720 P-CR Approval 23.700-08: KI #6, Sol #38: Update to remove an Editor s note and update to solution #38 NEC Rel-18 Revision of S2-2206045r04. Approved Approved
9.4 S2-2206043 P-CR Approval 23.700-08: KI#6, New Sol: Solution for mitigating overload at home network NEC Rel-18 r05 agreed. Revised to S2-2207721. Guanzhou (InterDigital) comments and kindly asks for clarification.
Myungjune (LGE) comments
Jianning (Xiaomi) provides comments
Prabhu (NEC) responds to Guanzhou (InterDigital) and Myungjune (LGE), and provides r01.
Prabhu (NEC) responds to Jianning (Xiaomi), and provides r02.
Huan (vivo) asks for clarifications
Pallab (Nokia) comments and requests to upload a file with change marks if possible
Prabhu (NEC) responds to Huan (vivo).
Prabhu (NEC) responds to Pallab (Nokia), and provides r03 with change marks.
Myungjune (LGE) comments.
Prabhu (NEC) responds to Myungjune (LGE), and provides r04.
Pallab (Nokia) comments and thinks that a revision is needed.
Ashok (Samsung) thinks that the solution does not work at its present form
Prabhu (NEC) responds to Pallab (Nokia) and Ashok (Samsung), and provides r05.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.4 S2-2207721 P-CR Approval 23.700-08: KI#6, New Sol: Solution for mitigating overload at home network NEC Rel-18 Revision of S2-2206043r05. Approved Approved
9.4 - - - Evaluation, conclusions - - Docs:=2 -
9.4 S2-2206349 P-CR Approval 23.700-08: KI#6: Evaluation and interim conclusions MediaTek Inc. Rel-18 r06 agreed. Revised to S2-2207722. Peter Hedman (Ericsson) provides r01
Pallab (Nokia) provides r02
Guanzhou (InterDigital) can't accept any version and proposes to make preliminary choice between so-called 'avoidance-based' and 'runtime-based' solutions.
Myungjune (LGE) comments
Miguel (Qualcomm) provides r03
Chia-Lin (MediaTek) provides comments and r04
Josep (DT) objects to r01, r02.
Miguel (Qualcomm) can live with r04
Guanzhou (InterDigital) can't accept any version.
Chia-Lin (MediaTek) responds to Guanzhou (InterDigital)
Peter Hedman (Ericsson) provides r05
Guanzhou (InterDigital) responds to Chia-Lin.
Guanzhou (InterDigital) provides r06.
Guanzhou (InterDigital) provides r06. //resend
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments that r06 or r05 is ok
Guanzhou (InterDigital) indicates wrong file was uploaded for r06 :( and objects to all versions if the rule allows (objecting one's own revision)
Guanzhou (InterDigital) withdrew r06 and objects to all other versions.
Chia-Lin (MediaTek) suggests this can be discussed in CC#5 to include the changes suggested by Guanzhou based on r05
Guanzhou (InterDigital) thinks this can be resolved via email and doesn't have to go through CC#5.
Chia-Lin (MediaTek) is ok using email to solve the issue not go to CC#5
Peter Hedman (Ericsson) understand suggestion is then to approve r06 + removing sentence 'There is no additional normative work required for overload condition management at the home/serving network ' + + add a note 'Whether any enhancement to the existing mechanisms is needed is FFS' + remove 'avoidance-based' from the existing note.
==== 9.X, 10.X Final Deadline ====
Guanzhou (InterDigital) is OK with changes stated by Peter (Ericsson).
Revised
9.4 S2-2207722 P-CR Approval 23.700-08: KI#6: Evaluation and interim conclusions MediaTek Inc. Rel-18 Revision of S2-2206349r06. Approved Approved
9.4 - - - Documents exceeding TU Budget - - Docs:=0 -
9.4 - - - KI#1 - - Docs:=1 -
9.4 S2-2206042 P-CR Approval 23.700-08: KI#1, New Sol: Support service continuity between distributed equivalent SNPNs NEC Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 - - - KI#2 - - Docs:=7 -
9.4 S2-2205557 P-CR Discussion 23.700-08: KI#2 updates NICT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206172 P-CR Approval 23.700-08: KI#2, Update Solution #4 to include trusted N3GPP access Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206554 P-CR Approval 23.700-08: KI#2: Updates for solution 19 to address the EN Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206683 P-CR Approval 23.700-08: KI#2 Sol #20 revision Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206424 P-CR Approval 23.700-08: KI#2, update to Solution 21 Lenovo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206684 P-CR Approval 23.700-08: KI#2 Sol#21 revision: Wireline support of NSWO Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206786 P-CR Approval 23.700-08: New Solution KI#2: Provisioning N3IWF info for Credential Holder scenarios Samsung Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 - - - KI#3 - - Docs:=1 -
9.4 S2-2205797 P-CR Approval 23.700-08: KI #3: Evaluation and conclusion for Key Issue #3 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 - - - KI#4 - - Docs:=8 -
9.4 S2-2206173 P-CR Approval 23.700-08: KI#4, Update Solution #12 about UDM involvement Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206242 P-CR Approval 23.700-08: 23.700-08:PNI-NPN specific updates to the solution#12 Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2205956 P-CR Approval 23.700-08: KI #4, #5, Sol #27 Update to resolve EN LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206782 P-CR Approval 23.700-08: KI #4, New Sol: Discovery and selection of hosting network as overlay network Lenovo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206175 P-CR Approval 23.700-08: KI#4, Evaluation on KI#4 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206347 P-CR Approval 23.700-08: KI#4: Evaluation and interim conclusions on automatic Hosting Network selection MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206712 P-CR Approval 23.700-08: KI#4: Evaluation of solutions and conclusion for KI#4 InterDigital Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206901 P-CR Approval 23.700-08: PCR_5G_eNPN_Ph2- evaluation on enhancement of network selection for key issue#4 Xiaomi Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 - - - KI#5 - - Docs:=1 -
9.4 S2-2205799 P-CR Approval 23.700-08: KI #5: Evaluation of Key Issue #5 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 - - - KI#6 - - Docs:=4 -
9.4 S2-2205957 P-CR Approval 23.700-08: KI #6, Sol #38 Update to resolve EN LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206283 P-CR Approval 23.700-08: 23.700-08 KI #6, Sol#38: Update to resolve the Editor's notes that how the hosting AMF knows the UE s home network CATT Rel-18 Not Handled Pallab (Nokia) comments and requests clarification
Liping Wu(CATT) responds to Pallab (Nokia) and indicate the pCR is 'not-handled'
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2205800 P-CR Approval 23.700-08: KI #6: Evaluation and Conclusion of Key Issue #6 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.4 S2-2206726 P-CR Approval 23.700-08: KI#6: Evaluation of Solutions for KI#6 and conclusion InterDigital Rel-18 Not Handled Pallab (Nokia) comments and provides r01
Guanzhou (InterDigital) reminds Pallab (Nokia) that this is marked as 'not handled'.
Miguel (Qualcomm) prefers we move forward with S2-2206349.
Pallab (Nokia) understand that this is marked as Not Handled and have further commented in 6349. Sorry for this
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.5 - - - Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) - - Docs:=22 -
9.5 - - - KI#1 - - Docs:=8 -
9.5 S2-2206244 P-CR Approval 23.700-58: 23.700-58: Updates to Solution #1 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207052. Stefano (Qualcomm) has questions for clarifications.
Pallab (Nokia) responds to Stefano (Qualcomm) and provided r01.
Stefano (Qualcomm) thanks Nokia for the changes.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.5 S2-2207052 P-CR Approval 23.700-58: 23.700-58: Updates to Solution #1 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206244r01. Approved Approved
9.5 S2-2206576 P-CR Approval 23.700-58: KI#1, Evaluation LG Electronics Rel-18 Merged into S2-2207053 LaeYoung (LGE) proposes to Merge this pCR into S2-2206702.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.5 S2-2206702 P-CR Approval 23.700-58: KI#1: Evaluation of solutions for KI#1 InterDigital Rel-18 r01 agreed. Revised to S2-2207053, merging and S2-2206576 LaeYoung (LGE) provides r01.
LaeYoung (LGE) comments.
Guanzhou (InterDigital) is OK with r01.
==== 9.X, 10.X Revisions Deadline ====
LaeYoung (LGE) replies to Guanzhou (InterDigital).
==== 9.X, 10.X Final Deadline ====
Revised
9.5 S2-2207053 P-CR Approval 23.700-58: KI#1: Evaluation of solutions for KI#1 InterDigital Rel-18 Revision of S2-2206702r01, merging and S2-2206576. Approved Approved
9.5 S2-2206577 P-CR Approval 23.700-58: KI#1, Conclusion LG Electronics Rel-18 Merged into S2-2207054 LaeYoung (LGE) answers to Stefano (Qualcomm).
Stefano (Qualcomm) expresses concerns and has questions for clarification.
Stefano (Qualcomm) suggests merging with 6704.
LaeYoung (LGE) replies to Stefano (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.5 S2-2206704 P-CR Approval 23.700-58: KI#1: Conclusion for KI#1 InterDigital Rel-18 r05 agreed. Revised to S2-2207054, merging and S2-2206577 Stefano (Qualcomm) provides R01.
LaeYoung (LGE) provides R02.
Pallab (Nokia) comments and provides r03.
LaeYoung (LGE) replies to Pallab (Nokia).
Pallab (Nokia) responds to LaeYoung (LGE).
LaeYoung (LGE) responds to Pallab (Nokia).
Guanzhou (InterDigital) responds to Pallab(Nokia)'s comments
Pallab (Nokia) responds to Guanzhou (InterDigital)
Guanzhou (InterDigital) provides r04.
Pallab (Nokia) responds to Guanzhou (InterDigital) and provided r05
Guanzhou (InterDigital) responds to Pallab that USS can't act as Prose App Server.
LaeYoung (LGE) comments.
Guanzhou (InterDigital) responds to Pallab (Nokia) and LaeYoung.
Guanzhou (InterDigital) is OK with r05.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.5 S2-2207054 P-CR Approval 23.700-58: KI#1: Conclusion for KI#1 InterDigital Rel-18 Revision of S2-2206704r05, merging and S2-2206577. Approved Approved
9.5 - - - KI#2 - - Docs:=4 -
9.5 S2-2206688 P-CR Approval 23.700-58: KI#2, Sol#3: update with clarification on different broadcast sessions and RAN support Futurewei Rel-18 r01 agreed. Revised to S2-2207055. Stefano (Qualcomm) has questions for clarifications
Amanda ( Futurewei ) responses to Qualcomm and provide revision r01
Runze ( Huawei ) thanks Amanda and supports r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.5 S2-2207055 P-CR Approval 23.700-58: KI#2, Sol#3: update with clarification on different broadcast sessions and RAN support Futurewei Rel-18 Revision of S2-2206688r01. Approved Approved
9.5 S2-2206750 P-CR Approval 23.700-58: KI #2, Sol #3: update to remove editor s note Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.5 S2-2206888 P-CR Approval 23.700-58: TR 23.700-58: Key Issue 2 evaluation Qualcomm Incorporated Rel-18 Noted Runze ( Huawei ) comments.
Stefano (Qualcomm) comments.
Runze (Huawei) replies to Stefano (Qualcomm), and suggest to note the paper as only conclusion paper should be focused.
Stefano (Qualcomm) disagree completely with the meaningless proposal.
==== 9.X, 10.X Revisions Deadline ====
Runze (Huawei) replies to Stefano (Qualcomm), and sustain to NOTE the paper.
LaeYoung (LGE) provides comment.
==== 9.X, 10.X Final Deadline ====
Noted
9.5 - - - KI#3 - - Docs:=6 -
9.5 S2-2206753 P-CR Approval 23.700-58: KI#3, Sol#2, Update to add another option Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.5 S2-2206705 P-CR Approval 23.700-58: KI#3: Evaluation of solutions for KI#3 InterDigital Rel-18 r02 agreed. Revised to S2-2207056, merging and S2-2206889 Stefano (Qualcomm) proposes r01 merging 6889 into 6705
Shabnam (Ericsson) believes the evaluation of Soln#5 is incomplete specially regarding broadcasting big amount of data between UAVs. Comments
Stefano (Qualcomm) provides R02.
==== 9.X, 10.X Revisions Deadline ====
Guanzhou (InterDigital) OK with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.5 S2-2207056 P-CR Approval 23.700-58: KI#3: Evaluation of solutions for KI#3 InterDigital Rel-18 Revision of S2-2206705r02, merging and S2-2206889. Approved Approved
9.5 S2-2206889 P-CR Approval 23.700-58: TR 23.700-58: Key Issue 3 evaluation Qualcomm Incorporated Rel-18 Merged into S2-2207056 Stefano (Qualcomm) proposes to merge into 6705.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.5 S2-2206706 P-CR Approval 23.700-58: KI#3: Conclusions for KI#3 InterDigital Rel-18 Merged into S2-2207057 (withdrawn). Postponed Stefano (Qualcomm) proposes to consider 6706 merged into 6890.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
9.5 S2-2206754 P-CR Approval 23.700-58: KI#3, Conclusion for network-assisted DAA in KI#3 Huawei, HiSilicon Rel-18 Merged into S2-2207057 (withdrawn). Postponed Stefano (Qualcomm) proposes to merge the conclusion part of the document in 6890
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
9.5 - - - General - - Docs:=4 -
9.5 S2-2206890 P-CR Approval 23.700-58: TR 23.700-58 Interim Conclusions Qualcomm Incorporated Rel-18 r09 agreed. Revised to S2-2207057, merging S2-2206706 and S2-2206754. Noted Stefano (Qualcomm) now provides R01
Stefano (Qualcomm) proposes to use 6890 as the basis for initial conclusions and will provides R01 when possible
Pallab (Nokia) comments and provides r02. Objects to r00, r01
Pallab (Nokia) provides further clarification
Guanzhou (InterDigital) shares the concern of Pallab(Nokia) on Sol#2 and #3.
Pallab (Nokia) responds to Stefano (Qualcomm)
Stefano (Qualcomm) comments and has questions.
Guanzhou (InterDigital) responds to Pallab(Nokia)'s comments.
Stefano (Qualcomm) comments and suggests a revision is provided.
Guanzhou (InterDigital) provides r03.
Pallab (Nokia) responds to Guanzhou (InterDigital)
Guanzhou (InterDigital) responds to Pallab (Nokia).
Stefano (Qualcomm) responds to Guanzhou (InterDigital).
Runze (Huawei) objects to r02 and r03.
Stefano (Qualcomm) provides r04
Runze (Huawei) comments on r04.
Stefano (Qualcomm) replies.
LaeYoung (LGE) comments about PC5.
Pallab (Nokia) comments and provides r05
Runze (Huawei) replies to Pallab (Nokia) and comments on r05
Runze (Huawei) replies to Stefano (Qualcomm)
Runze (Huawei) provides r06, on top of r04
Stefano (Qualcomm) urges again people to read regulations
Stefano (Qualcomm) comments on r06 and provides R07
Pallab (Nokia) responds to Runze (Huawei)
LaeYoung (LGE) provides r08.
Runze (Huawei) replies Stefano (Qualcomm), objects to r07.
Runze (Huawei) asks LaeYoung (LGE) a question .
Runze (Huawei) replies to Pallab (Nokia).
Pallab (Nokia) provides r09. Objects to all other revisions.
LaeYoung (LGE) replies to Runze (Huawei).
Shabnam (Ericsson) as commented on the evaluation document 6705, we need to address the two open issues that some form of mitigation is needed if we are to go forward with soln#5. Since we have not checked with SA3 and we have not anticipated RAN impacts, shall we add ENs in conclusion to check them as well?
Runze (Huawei) thanks LaeYoung (LGE).
Runze (Huawei) replies to Pallab (Nokia), and provides r10
==== 9.X, 10.X Revisions Deadline ====
Guanzhou (InterDigital) comments and proposes to go with r09
Shabnam (Ericsson) whichever revision is used as a basis since there seems to be added aspects not clearly concluded, there needs to be ENs added regarding 'soln#5 privacy aspects and amount of Data being transported which may need to be confirmed by RAN WGs, if large amount.'
Pallab (Nokia) objects to r10. Can only accept r09
Runze (Huawei) only accepts r06 and r10, and objects to all other versions.
Runze (Huawei) provides r11.
Pallab (Nokia) points that r11 comes after revision deadline and cannot be accepted. Maintains objections to all other revisions except r09
LaeYoung (LGE) supports to go with r09.
==== 9.X, 10.X Final Deadline ====
Noted
9.5 S2-2207057 P-CR Approval 23.700-58: TR 23.700-58 Interim Conclusions Qualcomm Incorporated Rel-18 Revision of S2-2206890r09, merging S2-2206706 and S2-2206754. WITHDRAWN Withdrawn
9.5 S2-2206892 P-CR Approval 23.700-58: Sol #5: removal of ENs Qualcomm Incorporated Rel-18 Revised to S2-2206945 Revised
9.5 S2-2206945 P-CR Approval 23.700-58: Sol #5: removal of ENs Qualcomm Incorporated Rel-18 Revision of S2-2206892. Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.6 - - - Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) - - Docs:=18 -
9.6 S2-2205589 P-CR Approval 23.700-46: DetNet conclusions Ericsson, AT&T, Intel, Samsung, NTT DOCOMO Rel-18 CC#4: r15 proposed. r15 agreed. Revised to S2-2207430. Laurent (Nokia): provides r01
György (Ericsson) comments.
Sebastian (Qualcomm) supports r00 and would like to cosign r00; objects to r01
zhendong (ZTE) provides r02
György (Ericsson) provides r03
Xiaowen Sun (vivo) provides comments
György (Ericsson) responds
Xiaowen Sun (vivo) responds and provide further comments
György(Ericsson) responds
Xiaowen Sun (vivo) responds.
Haiyang (Huawei) provides r04.
György (Ericsson) provides r05.
Laurent (Nokia): provides r06
Laurent (Nokia): provides r07
Haiyang (Huawei) comments to r05.
zhendong (ZTE) responds
György (Ericsson): provides r08
György (Ericsson) responds to Huawei
Laurent (Nokia): provides r09
Laurent (Nokia): asks a question
Haiyang (Huawei) provides r10.
György (Ericsson) comments on r10
Jinyan (China Telecom) provides r11.
György (Ericsson) responds to China Telecom
Haiyang (Huawei) responds to Laurent (Nokia).
György (Ericsson): provides r12 on top of r09
Dan (China Mobile): provides r14 on top of r12, please ignore r13
György (Ericsson) responds to China Mobile.
Laurent (Nokia): provides r15
György (Ericsson): provides r16
Dimitris (Lenovo) supports the conclusions in r16
zhendong (ZTE) comments
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) suggests to go with R17: R16+ NOTE: whether DetNet AF is involved in the mapping is to be determined in the normative phase.
Laurent (Nokia): can only live with r01, R06, R07, R09, R15; objects to hiding the issues in Notes (to be determined in normative phase) instead of EN
György (Ericsson) proposes to go with R15.
György (Ericsson) proposes to go with R15 as that is the most widely agreed way forward
Haiyang (Huawei) proposes to go with R15 + 'EN: whether DetNet AF is involved in the mapping is FFS'.
György (Ericsson) proposes to go with R15 without an additional note. The question of DetNet AF was already discussed and was ruled out when the SID was approved at SA plenary.
Sebastian (Qualcomm) supports the proposal by György (Ericsson)
==== 9.X, 10.X Final Deadline ====
Saso (Intel) proposes to move forward with r15 as proposed by the Rapporteur.
Revised
9.6 S2-2207430 P-CR Approval 23.700-46: DetNet conclusions Ericsson, AT&T, Intel, Samsung, NTT DOCOMO Rel-18 Revision of S2-2205589r15. Approved Approved
9.6 S2-2205688 P-CR Approval 23.700-46: KI #1, Sol #2 and KI #2, Sol #6: Update to remove ENs China Telecom Rel-18 r01 agreed. Revised to S2-2207431, merging and S2-2206340 György (Ericsson) comments and asks questions.
Reply to György (Ericsson) comments and merged with 6340.
György (Ericsson) comments.
Reply to György (Ericsson)'s comments. And clarify R01.
György (Ericsson) responds.
Replies to György (Ericsson).
György (Ericsson) replies to Jinyan.
Jinyan replies to György (Ericsson).
Haiyang (Huawei) comments.
György (Ericsson) responds to China Telecom.
György (Ericsson) responds to Huawei.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.6 S2-2207431 P-CR Approval 23.700-46: KI #1, Sol #2 and KI #2, Sol #6: Update to remove ENs China Telecom Rel-18 Revision of S2-2205688r01, merging and S2-2206340. Approved Approved
9.6 S2-2205722 P-CR Approval 23.700-46: Update to Solution #4 to address the EN Huawei, HiSilicon Rel-18 Approved György (Ericsson) comments and asks questions.
Xiaowen Sun (vivo) provide comments.
Haiyang (Huawei) responds.
György (Ericsson) responds.
Haiyang (Huawei) further responds.
György (Ericsson) responds to Huawei.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.6 S2-2205724 LS OUT Approval [DRAFT] LS on DetNet node exposure and Node level requirements Huawei, HiSilicon Rel-18 Merged into S2-2207432 György (Ericsson) Proposes to consider this merged into 6103
Haiyang (Huawei) is OK to merged this into 6103
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.6 S2-2205883 P-CR Approval 23.700-46: DetNet solution #8 Update Nokia, Nokia Shanghai Bell Rel-18 Approved György (Ericsson) comments.
Sebastian (Qualcomm) comments and raises concerns
Xiaowen Sun (vivo) provides comments.
Laurent (Nokia): answers
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.6 S2-2206103 LS OUT Approval [DRAFT] LS on 3GPP 5G System acting as a Detnet Node Nokia, Nokia Shanghai Bell Rel-18 r09 agreed. Revised to S2-2207432, merging and S2-2205724 Sebastian (Qualcomm) raises concerns
György (Ericsson) provides r01
Haiyang(Huawei) provides r02
György (Ericsson) provides r03
Haiyang(Huawei) comments to r03
György (Ericsson) responds to Huawei
Laurent (Nokia): provides r04
György (Ericsson) responds to Huawei.
Haiyang(Huawei) provides r05
György (Ericsson) provides r06 on top of r04.
Laurent (Nokia): provides r07
György (Ericsson) comments.
Laurent (Nokia): provides r08
György (Ericsson): provides r09
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) comments.
Laurent (Nokia): objects to R01 R02 R03 R05 R06
==== 9.X, 10.X Final Deadline ====
Revised
9.6 S2-2207432 LS OUT Approval [DRAFT] LS on 3GPP 5G System acting as a Detnet Node Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206103r09, merging and S2-2205724. Approved Approved
9.6 S2-2206340 P-CR Approval 23.700-46: Update of Solution#2 China Mobile Rel-18 Merged into S2-2207431 György (Ericsson) comments.
Dan (China Mobile) reply and this paper is merged into 5688
György (Ericsson) responds.
Dan (China Mobile) responds.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.6 S2-2206586 P-CR Approval 23.700-46: KI#2, solution#7 update ZTE Rel-18 r01 agreed. Revised to S2-2207433. György (Ericsson) comments.
zhendong (ZTE) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.6 S2-2207433 P-CR Approval 23.700-46: KI#2, solution#7 update ZTE Rel-18 Revision of S2-2206586r01. Approved Approved
9.6 S2-2206735 P-CR Approval 23.700-46: KI #2, Sol #5: Update to remove EN ETRI Rel-18 r02 agreed. Revised to S2-2207434. György (Ericsson) comments.
Yoohwa (ETRI) provides r01.
György (Ericsson) responds to ETRI.
Yoohwa (ETRI) provides r02.
Yoohwa (ETRI) responds to György.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.6 S2-2207434 P-CR Approval 23.700-46: KI #2, Sol #5: Update to remove EN ETRI Rel-18 Revision of S2-2206735r02. Approved Approved
9.6 - - - Documents exceeding TU Budget - - Docs:=4 -
9.6 S2-2205588 P-CR Approval 23.700-46: Sol 3 update Ericsson, AT&T, Intel, Samsung, NTT DOCOMO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.6 S2-2205723 P-CR Approval 23.700-46: Evaluation and conclusion for KI #1 and KI #2 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.6 S2-2205884 P-CR Approval 23.700-46: Detnet conclusions Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.6 S2-2206585 P-CR Approval 23.700-46: KI#2, proposal on the conclusion way forward ZTE Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.7 - - - Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) - - Docs:=59 -
9.7 - - - Key issue #1 - - Docs:=40 -
9.7 - - - Conclusion papers - - Docs:=3 -
9.7 S2-2205514 P-CR Approval 23.700-25: Conclusion for key issue 1 Qualcomm, AT&T, Orange Rel-18 Noted Runze (Huawei) asks questions .
Shabnam (Ericsson) as we have focused more on describing the procedures in 5593 and we have distinctly different options chosen for SIB, it maybe better to choose the content of 5593 as a basis, not too picky on which document itself but rather the content.
Sebastian (Qualcomm) replies
Josep (DT) asks a question for clarification.
Shabnam (Ericsson) asks how conclusion 7 first part of the requirement will be fulfilled in case of SIB usage?
Josep (DT) co-signs, provides r02 including minor addition to the description part.
Runze (Huawei) provides r03.
Runze (Huawei) replies to Sebastian (Qualcomm)
Runze (Huawei) replies to Sebastian (Qualcomm).
Shabnam (Ericsson) comments we need to start on high level and principles agreement first, comments
Sebastian (Qualcomm) provides r04
Josep (DT) comments regarding r05.
Jari (NTT DOCOMO) comments
Runze (Huawei) provides r05
Runze (Huawei) replies to Josep (DT), and provides the changes in r05..
Josep (DT) disagrees with Runze (Huawei) on the removal of clock quality. Co-signs. Provides r07, please ignore r06.
Sebastian (Qualcomm) objects to r05
Shabnam (Ericsson) comments on r05 - r07 aspects that are not acceptable at this point
Josep (DT) clarifies that he would actually much prefer r04.
zhendong (ZTE) proposes r04 as initial way forward
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) proposes to go with r04.
Josep (DT) supports to go with r04.
Runze (Huawei) provides r08..
Sebastian (Qualcomm) objects to r05-r08
Runze (Huawei) only accepts r05, r08 and objects to other versions.
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2205593 P-CR Approval 23.700-25: KI#1: Conclusions Ericsson Rel-18 Merged into S2-2205514 (noted). Noted Merge with S2-2205514 Devaki (Nokia) proposes to be merged with 5514.
Shabnam (Ericsson) we would prefer to first address differences, since the two have distinctly different proposals regarding use of SIB & content of solution description from this document which is clearer against Rel-17 baseline but which tdoc is used as basis is not an issue.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2205929 P-CR Approval 23.700-25: Conclusions for KI#1 Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2205514 (noted). Noted Merge with S2-2205514 Shabnam (Ericsson) proposes we use one baseline for the conclusion, we are ok to use 5514 but we believe it will need some major changes.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 - - - LS out, Solution update papers - - Docs:=11 -
9.7 S2-2205596 LS OUT Approval [DRAFT] LS on 5G Timing Resiliency Ericsson Rel-18 Noted Devaki (Nokia) proposes r01.
Sebastian (Qualcomm) raises concerns on the LS
Shabnam (Ericsson) provides comments
Shabnam (Ericsson) provides r02 focusing on questions and feedback on soln 14 only
Devaki (Nokia) cannot accept any revision of the LS yet due to reasons mentioned in r01/email below.
Sebastian (Qualcomm) objects to the LS
Shabnam (Ericsson) r03 provided, let's hope we can get the LS out to get some responses back so we can decide.
Sebastian (Qualcomm) objects to the LS for the same reasons as given for 5594
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) requests Qualcomm to reconsider, if RAN WGs don't think this is feasible or impacts are wrong, we can close the topic. But we should have a chance to see if we can provide full timing soln.
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2205931 LS OUT Approval [DRAFT] LS on Monitoring of network time synchronization and relevant parameters Nokia, Nokia Shanghai Bell r04 agreed. Revised to S2-2207723, merging and S2-2205517 Use this as a basis? Sebastian (Qualcomm) provides r01
zhendong (ZTE) comments
Josep (DT) comments, provides r02.
Sebastian (Qualcomm) comments inline
Runze (Huawei) comments.
Shabnam (Ericsson) 2nd paragraph, we don't see the relevance of those list of parameters, whereas 5517 whose content seem to be merged here is more precise.
Devaki (Nokia) provides r03.
Shabnam (Ericsson) provides r04 and still have some hesitancy in sending the LS at this point without reaching any conclusion, so we will wait before we agree to send such LS regarding what the status is for this work.
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) proposes to go with r04, also wonders about E/// comment about waiting to send such an LS? IMHO, this has been blocking our progress with parameters for number of meetings already (it is a chicken and egg story). Would be best to send the LS out to avoid further delay for the SID.
Josep (DT) prefers r03 to r04, supports sending the LS.
Sebastian (Qualcomm) objects to r00, prefers r04
Shabnam (Ericsson) objects to all except r04, for the sake of compromise & progress we can send the LS though I believe it is clear we have more work to do than just parameters and for the record, final decision on parameters will have to be in 3GPP with RAN WGs as relevant.
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207723 LS OUT Approval LS on Monitoring of network time synchronization and relevant parameters SA WG2 - Revision of S2-2205931r04, merging and S2-2205517. Approved Approved
9.7 S2-2205517 LS OUT Approval [DRAFT] LS on clock quality information Qualcomm Rel-18 Merged into S2-2207723 Merge with S2-2205517 Shabnam (Ericsson) comments that we need to update/reflect questions according to what we can conclude.
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) should be NOTED or considered merged into 5931, otherwise we object to this version.
Devaki (Nokia) comments that this should be considered as merged into 5931.
Sebastian (Qualcomm) confirms that LS can be considered merged
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2206190 P-CR Approval 23.700-25: KI #1, Sol #4 Update to clarify 5GC learning and reporting network timing synchronization status China Mobile Rel-18 r01 agreed. Revised to S2-2207724. zhendong (ZTE) comments
Aihua (CMCC) responds to zhendong
Aihua (CMCC) responds to Shabnam.
Shabnam (Ericsson) asks for some clarification.
Sebastian (Qualcomm) provides r01
Aihua (CMCC) is fine with r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207724 P-CR Approval 23.700-25: KI #1, Sol #4 Update to clarify 5GC learning and reporting network timing synchronization status China Mobile Rel-18 Revision of S2-2206190r01. Approved Approved
9.7 S2-2205594 P-CR Approval 23.700-25: KI#1, Sol #14: Update to address ENs Ericsson Rel-18 Postponed Devaki (Nokia) proposes r01.
Sebastian (Qualcomm) comments
Shabnam (Ericsson) provides response to the comments
Devaki (Nokia) wonders whether and why the solution and the updates are really in scope of the SID?!
Shabnam (Ericsson) provides r02, addressing Nokia ENs and other comments.
Shabnam (Ericsson) responds to Nokia comments
Devaki (Nokia) comments that we can live with the update only with the proposed ENs that can be removed only based on RAN1/RAN4 feedback regarding short term vs long term errors, impact due to phase/frequency sync/accuracy. For us, original version and r02 are not acceptable without these two ENs that need to be clarified based on RAN1/4 feedback.
Shabnam (Ericsson) provides r03, reinstates ENs except for duplicated ones and hopes we are able to send out the LS to RAN WGs in order to get their feedback. Provides response
Sebastian (Qualcomm) cannot accept the solution update as is (objects to the pCR)
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) Requests Qualcomm to reconsider as it is clarifying how the soln provides the total framework for timing and not just time. If we are allowed to send the LS to get clarification from RAN WGs, since that was the agreement for this work with RAN, we can determine with knowledge if moving forward or not.
Haiyang (Huawei) suggests to postpone this paper
==== 9.X, 10.X Final Deadline ====
Postponed
9.7 S2-2205734 P-CR Approval 23.700-25: KI#1, Sol#4: Update to address ENs Huawei, HiSilicon Rel-18 Merged into S2-2207725 Devaki (Nokia) proposes to merge with 5930.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2205930 P-CR Approval 23.700-25: KI#1 solution#4 update and discussion of open Ens Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207725, merging and S2-2205734 Sebastian (Qualcomm) comments and suggests changes
Devaki (Nokia) provides r01.
Shabnam (Ericsson) supports QC comments and in addition we need to address why and how to mange same information provided both to UE and AF and how to resolve conflict.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207725 P-CR Approval 23.700-25: KI#1 solution#4 update and discussion of open Ens Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205930r01, merging and S2-2205734. Approved Approved
9.7 S2-2205725 P-CR Approval 23.700-25: Update to Solution #17 to address the EN Huawei, HiSilicon Rel-18 Noted Sebastian (Qualcomm) asks questions
Haiyang (Huawei) responds
zhendong (ZTE) comments
Shabnam (Ericsson) similar to ZTE and Qualcomm comments, we are struggling to understand and we don't believe the first EN can be removed without clarifying the case, comments
Haiyang (Huawei) clarifies
Sebastian (Qualcomm) objects to r00
Haiyang (Huawei) responds to Sebastian (Qualcomm) , provides r01
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) objects to r01
==== 9.X, 10.X Final Deadline ====
Noted
9.7 - - - Key issue #2 - - Docs:=13 -
9.7 - - - Solution & Conclusion update papers - - Docs:=10 -
9.7 S2-2205564 P-CR Agreement 23.700-25: TR 23.700-25-030: Sol#2_Updates to conclusion of Key Issue #2 Inspur Rel-18 r02 agreed. Revised to S2-2207726. zhendong (ZTE) comments
Scott(Inspur) relies to zhendong (ZTE) comments
Shabnam (Ericsson) same comments ZTE already provided, new soln in Conclusion directly without justification or explanation how it works & why? Suggest to NOTE the paper unless revised to contain relevant information.
Sebastian (Qualcomm) objects to r00
Scott (Inspur) replies to all
Josep (DT) agrees with Shabnam (Ericsson), objects to r00, r01, provides r02 without conclusions section based on r01.
Josep (DT) provides the r02 link.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207726 P-CR Agreement 23.700-25: TR 23.700-25-030: Sol#2_Updates to conclusion of Key Issue #2 Inspur Rel-18 Revision of S2-2205564r02. Approved Approved
9.7 S2-2205735 P-CR Approval 23.700-25: KI#2, Sol#6: Update of solution#6 Huawei, HiSilicon Rel-18 Noted Shabnam (Ericsson) has concerns on the proposal as it really does not explain how it works and what actually will happen, comments
Runze (Huewei) replies to Shabnam and provides r01.
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) objects to r00 and r01
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2205736 P-CR Approval 23.700-25: KI#2, con#2: Update of conclusion#2 Huawei, HiSilicon Rel-18 Noted Devaki (Nokia) proposes r01.
Jari (NTT DOCOMO) provides r01.
zhendong (ZTE) similar view with jari
Runze (Huawei) replies to Jari and Zhendong, and provides r03
Shabnam (Ericsson) cannot agree to this conclusion change as this aspect was never in scope of the work or any of the solution when we reached conclusion. So objects to original and all revisions.
Runze (Huawei) clarifies to Shabnam (Ericsson) this proposal and conclusion are in the scope.
Shabnam (Ericsson) does not believe this conclusion is needed and will be part of the updates reflected in 6606 overall without having to 'monitor' anything. As such, suggest to consider this also merged as part of 6606.
==== 9.X, 10.X Revisions Deadline ====
Jari (NTT DOCOMO) Can agree r02. Objects other revisions and r00. The notes have a mistake, r02 is the latest revision.
Shabnam (Ericsson) sorry I have an issue with the term 'monitor' and as such can't accept any revision. Also, KI#1 conclusion will need to apply KI#2 feature if available, not other way around in my view since this function also applies without KI#1?
Sebastian (Qualcomm) objects to the PCF (all versions)
Sebastian (Qualcomm) objects to the PCR (all versions)
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2206434 P-CR Approval 23.700-25: 23.700-25 KI #2: Updating conclusion for key issue #2 CATT Rel-18 Noted Shabnam (Ericsson) requests clarification why this is needed and why standards need to couple the two conditions as no explanations are provided.
Yuan Tao (CATT) replies to Shabnam (Ericsson).
Shabnam (Ericsson) comments inline
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) proposes to NOTE this, as the text does not add any value and already part of the existing handling in our view since Spatial validity is added on top of existing conditions.
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2206587 P-CR Approval 23.700-25: KI#2, update the conclusion ZTE Rel-18 r02 agreed. Revised to S2-2207727. zhendong (ZTE) provides the r01
Jari (NTT DOCOMO) proposes to merge with 6606
Shabnam (Ericsson) supports DoCoMo proposal to consider relevant aspects to merge into 6606.
zhendong (ZTE) provides the response
zhendong (ZTE) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207727 P-CR Approval 23.700-25: KI#2, update the conclusion ZTE Rel-18 Revision of S2-2206587r02. Approved Approved
9.7 S2-2206606 P-CR Approval 23.700-25: Update of conclusions for KI#2 NTT DOCOMO Rel-18 r06 agreed. Revised to S2-2207728. Yuan Tao (CATT) comments.
Jari (NTT DOCOMO) provides r01
Yuan Tao replies to Jari (NTT DOCOMO).
zhendong (ZTE) propose to merge this paper into 6587
Shabnam (Ericsson) don't agree this paper should be merged into 6587 as 6587 brings in new elements not agreeable at this point. Updates the EN to state Whether and then how so we should have further discussions on the need to support IDLE mode mobility, cosigns the proposal.
Runze (Huawei) provides r03, in which remove the EN.
Jari (NTT DOCOMO) responds to Runze, prefers to keep the EN
Sebastian (Qualcomm) provides r04
Runze (Huawei) replies to Sebastian (Qualcomm).
zhendong (ZTE) provides the response
Shabnam (Ericsson) I have provided the comment on its own thread about combining the two conditions, please check.
zhendong (ZTE) similar view with runze
Devaki (Nokia) provides r05, supports the principles of the paper
Jari (NTT DOCOMO) responds to zhendong and runze
Runze (Huawei) replies.
Runze (Huawei) replies to Jari (NTT DOCOMO).
zhendong (ZTE) responds to hari
Sebastian (Qualcomm) replies
Sebastian (Qualcomm) comments
Runze (Huawei) provides r06.
zhendong (ZTE) provides r07
==== 9.X, 10.X Revisions Deadline ====
Runze (Huawei) supports r06, r07, and objects to all other versions.
Jari (NTT DOCOMO) can agree r07
Sebastian (Qualcomm) can accept r04, r06. Objects to r07. Can accept r07 if the EN is changed to: 'EN: Whether to support Coverage Area on cell-level granularity depends on how to support cell-level granularity for UEs in Idle mode or CM-connected with RRC Inactive mode and is FFS. '
Jari (NTT DOCOMO) can agree r06 or r07
zhendong (ZTE) i am fine with your change on top of r07
zhendong (ZTE) is fine with r06 and r07
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207728 P-CR Approval 23.700-25: Update of conclusions for KI#2 NTT DOCOMO Rel-18 Revision of S2-2206606r06. Approved Approved
9.7 S2-2206433 P-CR Approval 23.700-25: 23.700-25 KI #2, Sol #7: Update to clarify time synchronization service based temporal validity condition CATT Rel-18 Noted zhendong (ZTE), question for clarification
Yuan Tao (CATT) replies to zhendong (ZTE).
Yuan Tao (CATT) replies to Shabnam (Ericsson).
Shabnam (Ericsson) trying to understand the implications of updating individual soln when we have conclusion documenting the actual agreement, proposes to NOTE this and focus on discussion of any updates via 6606.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 - - - Key issue #3 - - Docs:=13 -
9.7 - - - Conclusion papers - - Docs:=4 -
9.7 S2-2205932 P-CR Approval 23.700-25: Conclusions for KI#3 Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2206928 Revised
9.7 S2-2206928 P-CR Approval 23.700-25: Conclusions for KI#3 Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 Revision of S2-2205932. Noted Sebastian (Qualcomm) comments
Jari (NTT DOCOMO) provides r01
zhendong (ZTE) comments
Jari (NTT DOCOMO) comments
Devaki (Nokia) provides r02 (minor edits on top of r01 by Jari).
zhendong (ZTE) provides r03
Qianghua (Huawei) provides comments
Jari (NTT DOCOMO) provides r04
Runze (Huawei) provides comments, proposes to remove the conclusion for the subscription data the 'AF request Authorization'.
Shabnam (Ericsson) provides r05, asks clarification about Start/Stop time and cosigns
Runze (Huawei) provides r06.
Sebastian (Qualcomm) provides r07
zhendong (ZTE) respond
Shabnam (Ericsson) asks another question
zhendong (ZTE) provides response
Devaki (Nokia) comments.
Shabnam (Ericsson) provides r08 to change the text according to comment provided
Sang-Jun comments.
zhendong (ZTE) provides r09
Devaki (Nokia) provides r10.
Jari (NTT DOCOMO) responds to Runze
Jari (NTT DOCOMO) responds to Devaki, Shabnam, Zhendong
Jari (NTT DOCOMO) provides r11
Runze (Huawei) provides r12.
zhendong (ZTE) provides r07
zhendong (ZTE) clarify the wrong email
- Shabnam (Ericsson) cannot accept Huawei addition '(Optionally) Maximum periodicity with which reference time information should be provisioned to the UE.'
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) comments. Wonders if we should add an EN to resolve the concern with maximum periodicity e.g. whether this parameter is needed?
Runze (Huawei) replies to Jari (NTT DOCOMO).
Jari (NTT DOCOMO) prefers r11, responds to Runze
Sang-Jun (Samsung) is fine with r12.
Runze (Huawei) provides r13, and thank you Sang-Jun (Samsung) for support r12.
Runze (Huawei) can only accepts r12, r13, and objects to all other versions. .
Shabnam (Ericsson) asks where in the current TR Maximum Periodicity is defined and r013 (after deadline) has spelling mistake ASIT instead of ASTI?
Jari (NTT DOCOMO) r12 is technically inconsistent, r13 was provided after the deadline
Devaki (Nokia) proposes that we go with r11 + EN for maximum periodicity in the interest of progress.
Runze (Huawei) replies Devaki (Nokia), suggest to approve r13 minus the EN for periodicity.
Sebastian (Qualcomm) is ok with r07 and r11, objects to other versions and comments that EN on maximum periodicity is not acceptable
==== 9.X, 10.X Final Deadline ====
Devaki (Nokia) provides r15 (r12 provided before the deadline + 4 bullets removed related to coverage area, periodicity, PTP instance and 2 ENs added) as discussed with Huawei, DCM, Qualcomm, Ericsson, Samsung, ZTE and agreed.
Noted
9.7 S2-2206119 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#3 Samsung Rel-18 Merged into S2-2206928 (noted). Noted Merge with S2-2206928 Devaki (Nokia) proposes to merge with 6928.
Sang-Jun (Samsung) agrees to merge 6119 with 6928.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2206589 P-CR Approval 23.700-25: KI#3, proposal on the conclusion ZTE Rel-18 Merged into S2-2206928 (noted). Noted Merge with S2-2206928 Devaki (Nokia) proposes that this paper can be merged with S2-2205932.
Jari (NTT DOCOMO) proposes to merge with 6928
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 - - - Solution updates, Evaluation papers - - Docs:=11 -
9.7 S2-2205737 P-CR Approval 23.700-25: KI#3, sol#19: Update of solution #19 Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207729. Sebastian (Qualcomm) provides r01
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) objects to r00
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207729 P-CR Approval 23.700-25: KI#3, sol#19: Update of solution #19 Huawei, HiSilicon Rel-18 Revision of S2-2205737r01. Approved Approved
9.7 S2-2206588 P-CR Approval 23.700-25: KI#3, adding a new solution about the time sync area subscription ZTE Rel-18 Merged into S2-2207730 Devaki (Nokia) proposes that this paper can be merged with S2-2206927.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2206590 P-CR Approval 23.700-25: KI#3, update the solution 18 ZTE Rel-18 Merged into S2-2207730 Devaki (Nokia) proposes that this paper can be merged with S2-2206927.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2205944 P-CR Approval 23.700-25: KI#3, Sol#18: Update of Solution #18 Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2206927 Revised
9.7 S2-2206927 P-CR Approval 23.700-25: KI#3, Sol#18: Update of Solution #18 Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 r06 + changes agreed. Revised to S2-2207730, merging S2-2206188, S2-2206588 and S2-2206590 Devaki (Nokia) provides r01 (merges 6588 and 6188).
zhendong (ZTE) provides r02
Sebastian (Qualcomm) provides r03
Sebastian (Qualcomm) provides r01
Aihua (CMCC) objects to r01.
Jari (NTT DOCOMO) responds to Aihua
Aihua (CMCC) replies and comments.
Aihua (CMCC) responds to Jari.
Devaki (Nokia) comments.
Sebastian (Qualcomm) replies
Runze (Huawei) replies to Sebastian (Qualcomm) and Devaki (Nokia).
Shabnam (Ericsson) provides comments that require update and clarification according to the response
Devaki (Nokia) provides r05.
Shabnam (Ericsson) can we have an agreement then to focus on conclusion only, this meeting we have too many papers updating various solutions that are really waste of time. Also the Stop/Start time unit EN was not added yet in the Conclusion, should we?
zhendong (ZTE) provides r06
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) proposes to go with r06. We should allow solution updates this meeting to resolve EN but for future, I agree that we should avoid solution update (should that be considered as 'not handled' perhaps?)
Sebastian (Qualcomm) can accept r03 and objects to other versions; can accept r06 if the following is removed: '(Optionally) A valid list of AFs for time synchronization (e.g. a list of AF identifiers). '
Devaki (Nokia) is fine with r06 minus '(Optionally) A valid list of AFs for time synchronization (e.g. a list of AF identifiers). '
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207730 P-CR Approval 23.700-25: KI#3, Sol#18: Update of Solution #18 Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 Revision of S2-2206927r06 + changes, merging S2-2206188, S2-2206588 and S2-2206590. Approved Approved
9.7 S2-2206115 P-CR Approval 23.700-25: Evaluation for FS_5TRS_URLLC KI#3 Samsung Rel-18 r02 agreed. Revised to S2-2207731. Devaki (Nokia) comments.
Sang-Jun (Samsung) provides r01.
Devaki (Nokia) provides r02.
Sang-Jun (Samsung) is fine with r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207731 P-CR Approval 23.700-25: Evaluation for FS_5TRS_URLLC KI#3 Samsung Rel-18 Revision of S2-2206115r02. Approved Approved
9.7 S2-2206187 P-CR Approval 23.700-25: KI #3, Sol #19 Update to clarify Supporting for controlling 5G time synchronization_service_based_on_subscriptio China Mobile, Huawei Rel-18 Noted Aihua (CMCC) responds to Shabnam.
Shabnam (Ericsson) we have a general principle of one TSCTSF during the connectivity and we have not handled TSCTSF change on the fly, so we don't think the changes are in scope and as such is not needed as defined in clause 6.3.24 in TS 23.501.
Sebastian (Qualcomm) asks questions
Shabnam (Ericsson) agrees with China Mobile, I have misread the text. I don't believe the proposed changes are needed as the Conclusion handles it and we are not referring to any solution in the conclusion so better to focus on the Conclusion paper.
Aihua (CMCC) responds to Sebastian.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.7 S2-2206188 P-CR Approval 23.700-25: KI #3, Sol #18 Update to clarify supporting for subscription based control of time synchronization service China Mobile Rel-18 Merged into S2-2207730 Sebastian (Qualcomm) provides r01
Aihua (CMCC) is ok with ro1.
Jari (NTT DOCOMO) comments
Jari (NTT DOCOMO) proposes to discuss this under 6927
Aihua (CMCC) responds to Jari.
zhendong (ZTE) comments
Shabnam (Ericsson) believes this document has more focused scope whereas 6927 has quite more details that we believe need some trimming. In parallel, we need to also ensure conclusion is aligned. So wondering if we can focus on Conclusion paper first?
Aihua (CMCC) replies and comments.
==== 9.X, 10.X Revisions Deadline ====
Jari (NTT DOCOMO) proposes to mark as merged into 6927
==== 9.X, 10.X Final Deadline ====
Merged
9.7 - - - Key Issue #5 - - Docs:=4 -
9.7 - - - Evaluation & Conclusion papers - - Docs:=6 -
9.7 S2-2206116 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#5 Samsung Rel-18 Merged into S2-2207732 Merge with S2-2205726 Haiyang (Huawei) suggests to merge this paper into S2-2205726
Sang-Jun (Samsung) agrees to merge this paper into S2-2205726
Sang-Jun (Samsung) corrected 6616 into 6116 in the mail title, and agrees to merge 6616 paper into S2-2205726.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2205726 P-CR Approval 23.700-25: Evaluation & Conclusion of KI#5 Huawei, HiSilicon, NTT DOCOMO Rel-18 r02 + changes agreed. Revised to S2-2207732, merging S2-2206116 and S2-2206592 Use this as a basis for conclusion? Haiyang(Huawei) provides r01
Devaki (Nokia) comments: Nokia, Nokia Shanghai Bell can support/co-sign this conclusion paper.
zhendong (ZTE) provides r02
Jari (NTT DOCOMO) comments
zhendong (ZTE) respond
Haiyang(Huawei) comments to zhendong (ZTE)
zhendong (ZTE) provides the response
Sang-Jun (Samsung) is fine with r02, as it is aligned with merged 6116.
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) suggests to change which 5GS entity into 'whether SMF or TSCNF' in the EN of r02
Devaki (Nokia) shares Haiyang's view that we can change 5GS to SMF or new TSCNF as collocated with CUC to avoid this being too open ended. Otherwise, we might waste the progress we have made.
zhendong (ZTE) is fine with haiyang proposal
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207732 P-CR Approval 23.700-25: Evaluation & Conclusion of KI#5 Huawei, HiSilicon, NTT DOCOMO Rel-18 Revision of S2-2205726r02 + changes, merging S2-2206116 and S2-2206592. Approved Approved
9.7 S2-2206592 P-CR Approval 23.700-25: KI#5, evaluation and interim conclusion ZTE Rel-18 Merged into S2-2207732 Merge with S2-2205726 (conclusion), S2-2206113 (evaluation) Haiyang (Huawei) suggests to Merge this paper into S2-2205726 (conclusion) and S2-2206113 (evaluation)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2206113 P-CR Approval 23.700-25: Evaluation for FS_5TRS_URLLC KI#5 Samsung Rel-18 r03 agreed. Revised to S2-2207733. Use this as a basis for evaluation? Jari (NTT DOCOMO) provides r02
zhendong (ZTE) provides r03
Sang-Jun (Samsung) is fine with r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207733 P-CR Approval 23.700-25: Evaluation for FS_5TRS_URLLC KI#5 Samsung Rel-18 Revision of S2-2206113r03. Approved Approved
9.7 - - - Solution update, Evaluation papers - - Docs:=4 -
9.7 S2-2206591 P-CR Approval 23.700-25: KI#5, update solution 11 ZTE Rel-18 r01 agreed. Revised to S2-2207734. Haiyang (Huawei) provides a question
zhendong (ZTE) provides r01
Jari (NTT DOCOMO) comments
Haiyang (Huawei) comments
zhendong (ZTE) provides the response
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207734 P-CR Approval 23.700-25: KI#5, update solution 11 ZTE Rel-18 Revision of S2-2206591r01. Approved Approved
9.7 S2-2205934 P-CR Approval 23.700-25: KI#5 solution#9 update implementation correction Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.7 S2-2206610 P-CR Approval 23.700-25: Update on Solution #9 NTT DOCOMO, Nokia, Huawei Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.7 - - - Key Issue #6 - - Docs:=0 -
9.7 - - - Evaluation & Conclusion papers - - Docs:=6 -
9.7 S2-2205595 P-CR Approval 23.700-25: KI#6: evaluation and conclusions Ericsson Rel-18 Merged into S2-2207735 Jari (NTT DOCOMO) proposes to merge with 5935
Devaki (Nokia) agrees with Jari, as per our plan discussed prior to the meeting, let us merge this with 5935.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2205727 P-CR Approval 23.700-25: Evaluation & Conclusion of KI#6 Huawei, HiSilicon Rel-18 Merged into S2-2207735 Jari (NTT DOCOMO) proposes to merge with 6540 (evaluation) and 5935 (conclusions).
Haiyang (Huawei) is OK to merge this paper with 6540 (evaluation) and 5935 (conclusions).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.7 S2-2205935 P-CR Approval 23.700-25: Conclusions for KI#6 Nokia, Nokia Shanghai Bell, Qualcomm Rel-18 r07 agreed. Revised to S2-2207735, merging S2-2205595 and S2-2205727 Jari (NTT DOCOMO) comments
Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
György (Ericsson) comments.
Jari (NTT DOCOMOI) comments.
Devaki (Nokia) provides r01 (merging also conclusion from 6540).
György (Ericsson) responds to DOCOMO.
Jari (NTT DOCOMO) responds to György (Ericsson)
György (Ericsson) provides r02
Haiyang (Huawei) comments to r02.
Jari (NTT DOCOMO) provides r03
György (Ericsson) responds to Huawei.
Sebastian (Qualcomm) comments
Haiyang (Huawei) supports Jari (NTT DOCOMO).
Devaki (Nokia) provides r05.
Haiyang (Huawei) provides r06.
György (Ericsson) provides r07.
Herve (Mitsubishi) comments.
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) can agree with r07.
Devaki (Nokia) is fine with r07, thanks Huawei, HiSilicon for the support.
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207735 P-CR Approval 23.700-25: Conclusions for KI#6 Nokia, Nokia Shanghai Bell, Qualcomm Rel-18 Revision of S2-2205935r07, merging S2-2205595 and S2-2205727. Approved Approved
9.7 S2-2206540 P-CR Approval 23.700-25: Evaluation and conclusion of KI#6 NTT DOCOMO Rel-18 r02 agreed. Revised to S2-2207736. Devaki (Nokia) proposes r02 (please ignore r01) to use this as the basis for evaluation paper (as discussed), also striving to keep this paper neutral.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207736 P-CR Approval 23.700-25: Evaluation and conclusion of KI#6 NTT DOCOMO Rel-18 Revision of S2-2206540r02. Approved Approved
9.7 - - - Solution update papers - - Docs:=4 -
9.7 S2-2206608 P-CR Approval 23.700-25: Update on Solution #12 NTT DOCOMO, Huawei Rel-18 r01 agreed. Revised to S2-2207737. Jari (NTT DOCOMO) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.7 S2-2207737 P-CR Approval 23.700-25: Update on Solution #12 NTT DOCOMO, Huawei Rel-18 Revision of S2-2206608r01. Approved Approved
9.7 S2-2206593 P-CR Approval 23.700-25: KI#6, update the solution 21 ZTE Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.7 S2-2205933 P-CR Approval 23.700-25: Periodicity provisioning in RAN Feedback Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.8 - - - Study on RedCap Phase 2 (FS_RedCAP_Ph2) - - Docs:=8 -
9.8 - - - Evaluations - - Docs:=3 -
9.8 S2-2206655 P-CR Approval 23.700-68: FS_RedCAP_Ph2 evaluation ZTE Rel-18 r02 agreed. Revised to S2-2207058. Jinguo(ZTE) answer to Steven(Huawei)
Steve (Huawei) proposes to note this update
Qian (Ericsson) comments and provides r01
Jinguo(ZTE) provides r02
==== 9.X, 10.X Revisions Deadline ====
Qian (Ericsson) is ok with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.8 S2-2207058 P-CR Approval 23.700-68: FS_RedCAP_Ph2 evaluation ZTE Rel-18 Revision of S2-2206655r02. Approved Approved
9.8 S2-2208098 LS In Action LS from RAN WG3: Reply LS on FS_REDCAP_Ph2 option feasibility RAN WG3 (R3-225119) Rel-18 Postponed Qian (Ericsson) propose to NOTE the LS. The response has taken into the consideration during conclusion discussion.
Hannu (Nokia) proposes to postpone the LS as suggested in charman's minutes.
Postponed
9.8 - - - Conclusions - - Docs:=5 -
9.8 S2-2205649 P-CR Approval 23.700-68: KI#1, Conclusion Ericsson Rel-18 Merged into S2-2207059 Qian (Ericsson) proposes to use this mail thread for KI#1 conclusion discussion.
Lars (Sony) share some views.
Jinguo(ZTE) provides comments
Lars (Sony) resonds to Jinguo.
Hannu (Nokia) supports using S2-2205649 as the basis and provides r01
Qian (Ericsson) provides comments
Miguel (Qualcomm) comments, not OK with a conclusion proposal that includes RAN buffering solution.
Lars (Sony) comments
Qian (Ericsson) comments and proposes to go with 6865 as baseline for conclusion.
Qian (Ericsson) add some further comments.
Lars (Sony) comments.
Steve (Huawei) agrees with taking 6865 as the most fitting conclusion direction.
Qian (Ericsson) responds.
Miguel (Qualcomm) clarifies
Lars (Sony) don't understand the Miguel's clarification.
Miguel (Qualcomm) asks Lars if he wants to define UP optimization in NR? Otherwise comparing CN buffering for long eDRX with UP optimization makes no sense, as this is not supported in NR. You need to compare with CM-IDLE/RRC-IDLE which is the status quo.
Lars (Sony) I have not decided, but it should be an option to define UP optimization in NR.
Miguel (Qualcomm) responds to Lars: ok, then please check Solution #4 :-)
Lars (Sony) I have looked at sol#4 and don't like it ?
Hannu (Nokia) comments.
Hannu (Nokia) comments to Lars
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) should be noted or marked as merged to 6865 as we are focusing there.
==== 9.X, 10.X Final Deadline ====
Merged
9.8 S2-2206199 P-CR Approval 23.700-68: Interim Conclusion Sony Rel-18 Merged into S2-2207059 Hannu (Nokia) proposes to note and to focus the discussion on conclusions on S2-2205649.
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) should be noted or marked as merged to 6865 as we are focusing there.
==== 9.X, 10.X Final Deadline ====
Merged
9.8 S2-2206275 P-CR Approval 23.700-68: KI#1: Conclusion Huawei, HiSilicon Rel-18 Merged into S2-2207059 Hannu (Nokia) proposes to note and to focus the discussion on conclusions on S2-2205649.
Steve (Huawei) No problem to discuss in one place. Once we know what we are doing we can come back around to work out status of this contribution.
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) should be noted or marked as merged to 6865 as we are focusing there.
==== 9.X, 10.X Final Deadline ====
Merged
9.8 S2-2206865 P-CR Approval 23.700-68: Conclusion proposal for KI#1 Qualcomm Inc. Rel-18 CC#5: r09 + changes agreed. Revised to S2-2207059, merging S2-2205649, S2-2206199 and S2-2206275. Hannu (Nokia) proposes to note and to focus the discussion on conclusions on S2-2205649.
Miguel (Qualcomm) responds to Hannu
Qian (Ericsson) proposes to use this paper as baseline for KI#1 conclusion.
Jinguo(ZTE) provides r01
Lars (Sony) comments
Qian (Ericsson) provides comments
Qian (Ericsson) responds
Jinguo(ZTE) response to Qian (Ericsson)
Lars (Sony) responds to Qian
Steve (Huawei) comments on mobility
Qian (Ericsson) provides comments.
Miguel (Qualcomm) comments
Qian (Ericsson) comments
Miguel (Qualcomm) replies to Lars
Jinguo(ZTE) response to Qian(Ericsson)
Jinguo(ZTE) response to Steven(Huawei)
Steve (Huawei) comments on scenarios
Steve (Huawei) comments on most power efficient
Lars (Sony replies to Miguel
Miguel (Qualcomm) further comments in response to Lars
Qian (Ericsson) provides comments and proposes the way forward and r02
Lars (Sony) asks question on r02
Steve (Huawei) comments on r01 and r02, they are not inline with RAN3 and does not address data during mobility
Steve (Huawei) comments on RAN remaining silent and the following assumptions
Lars (Sony) on the RAN3 LS
Qian (Ericsson) provides comments and r03 (only CN buffering), r04 (possibility of using existing RAN buffering capability)
Jinguo(ZTE) agrees with Qian(Ericsson) and response to Steve(Huawei)
Qian (Ericsson) provides comments on the LS
Hannu (Nokia) responds to JInguo.
Lars (Sony) provides r05.
Hannu (Nokia) asks for 5 minutes to upload revisions that I have edited already.
Hannu (Nokia) shares r06 and r07 which BOTH rely on CN buffering and comments. Prefers r06, but can live with r07 also.
Steve (Huawei) RAN3 LS has arrived as S2-2208098
Steve (Huawei) provides r08
Jinguo(ZTE) : r08 is not acceptable and prefer r06
Steve (Huawei) provides r09
Lars (Sony) provides r10
Steve (Huawei) comments on r10
Miguel (Qualcomm) does not understand the NOTE in r10, could it be clarified?
Lars (Sony) provides r11
Jinguo(ZTE) provides comments
Qian (Ericsson) provides comments and r12
==== 9.X, 10.X Revisions Deadline ====
Qian (Ericsson) provides comments and propose to agree on r12
Lars (Sony) propose to agree on r11
Steve (Huawei) only agrees to r08, r09, r12.
Lars (Sony) comments.
Jinguo(ZTE) prefers r11
Lars (Sony) cannot accept r08, r09 and r12.
Steve (Huawei) only agrees to r08, r09 or r12. Objects to all other revisions.
Qian (Ericsson) asks question.
Lars (Sony) responds to Qian.
Qian (Ericsson) thanks Lars(Sony) for the response and propose way forward (r13).
Steve (Huawei) the gNB is not is a position to make the determinations, r13 needs more work.
Lars (Sony) provides r14 in Redcap draft folder.
Steve (Huawei) comments on buffering determination
Qian (Ericsson) provides further comments.
Steve (Huawei) comments on way forward
Qian (Huawei) comments and provides r15 in the draft folder.
Lars (Sony) comments on r15.
Qian (Ericsson) responds to Lars (Sony)
Steve (Huawei) comments on r15
Lars (Sony) responds to Qian (Ericsson)
Qian (Ericsson) responds.
Lars (Sony) comments on the NOTE
Miguel(Qualcomm) provides r16 in drafts folder
Steve (Huawei) comments on keep it simple and actionable.
Qian (Ericson) provides r17 in draft folder
Steve (Huawei) provides a draft r18.
Lars (Sony) Comments on r18.
Lars (Sony) further comment on r18.
Lars (Sony) even if r18 is not official rev, to make it clear I object to r18. Let's go with r17.
Jinguo(ZTE) supports Lars(sony) comment
Steve (Huawei) Documents the latest proposal (may is under discussion) is r09 + the following 2 changes: 1) Replace 2nd bullet with 'When the UE is entering or the UE has entered RRC_INACTIVE state with long eDRX, the gNB may send an indication to the CN and provides unreachability information (e.g., eDRX values negotiated between UE and gNB for RRC_INACTIVE state) . When this occurs, the CN applies the HLCOM functions based on gNB provided unreachability information (as described in solution #6).', and 2) replace note 1 with 'NOTE 1: If the indication of UE transition to RRC_INACTIVE is not sent (or sent after UE has entered RRC_INACTIVE) by the gNB then until CN receives it the CN cannot apply HLCOM functionality and other NFs will not be aware of the UE reachability, and certain HLCom related services provided to the AF via NEF would not be available. Downlink data transmitted from the UPF to RAN might be discarded and not delivered to the UE.'
Qian (Ericsson) suggests to bring this up in CC#5
==== 9.X, 10.X Final Deadline ====
Qian (Ericsson) indicates agreement (now in draft folder r21) on this paper with following changes on top of r09 (submitted before deadline):
Replace 2nd bullet with 'When the gNB sends an indication to the CN and provides unreachability information (e.g., eDRX values negotiated between UE and gNB for RRC_INACTIVE state), the CN applies the HLCOM functions based on gNB provided unreachability information (as described in solution #6).
- If the gNB has indicated the UE has entered RRC_INACTIVE to the CN, the gNB also notifies the CN about the RRC State transition back to RRC_CONNECTED (as described in solution #6).
Editor's Note: Details on possible triggers for gNB to send indication are FFS.'
Replace NOTE1 with 'If the indication of UE transition to RRC_INACTIVE is not sent (or sent after UE has entered RRC_INACTIVE) by the gNB then until CN receives it the CN cannot apply HLCOM functionality and other NFs will not be aware of the UE reachability, and certain HLCom related services provided to the AF via NEF would not be available. Downlink data transmitted from the UPF to RAN might be discarded and not delivered to the UE'
Miguel (Qualcomm) confirms agreement provided by Qian, ATTN Andy.
Steve (Huawei) is ok with the proposed r21 draft text.
Lars (Sony) also confirms that I am ok with the proposed agreement by Qian.
Jinguo(ZTE) can live with r21 at this meeting. Let's further discuss the open issue at next meeting.
Hannu (Nokia) comments on the second bullet point in clause 8.1 that HLCom is an optional and configurable feature. Are any changes on HLcom are expected as the consequence of this text?
Revised
9.8 S2-2207059 P-CR Approval 23.700-68: Conclusion proposal for KI#1 Qualcomm Inc. Rel-18 Revision of S2-2206865r09 + changes, merging S2-2205649, S2-2206199 and S2-2206275. Approved Approved
9.9 - - - Study on Vehicle Mounted Relays (FS_VMR) - - Docs:=42 -
9.9 - - - New solutions: 10 submitted - - Docs:=9 -
9.9 S2-2206092 P-CR Approval 23.700-05: KI#3, New solution of UE mobility management in case of IAB-node mobility with dynamic TAC provisioning Huawei, HiSilicon Rel-18 Approved Qian (Ericsson) asks question
LiMeng (Huawei) replies to Qian.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.9 S2-2206093 P-CR Approval 23.700-05: KI#3, New solution of IAB-node mobility with dedicated TA Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207060. New solution for KI#3 [Consider merging in the contents from S2-2206854] Qian (Ericsson) asks questions
LiMeng (Huawei) replies.
LiMeng (Huawei) asks for clarifications regarding merging S2-2206854.
LiMeng (Huawei) provides r01.
Hong (Qualcomm) replies to Xiaoyan.
Xiaoyan Shi (Intel) comments.
Lars (Sony) comments and ask for clarification.
Hong (Qualcomm) replies to LiMeng regarding the merging of S2-2206854.
LiMeng (Huawei) provides r01 of S2-2206093 considering the merging of S2-2206854.
LiMeng (Huawei) provides r02 of S2-2206093 considering the merging of S2-2206854.
Lars (Sony) comments on r02.
Lars (Sony) responds to LiMeng.
Hong (Qualcomm) comments and provides r03.
LiMeng (Huawei) is fine with r03 and comments.
Lars (Sony) comments and requests a r04.
LiMeng (Sony) provides r04.
Hong (Qualcomm) comments.
Lars (Sony) responds to Hong.
Hong (Qualcomm) replies to Lars.
==== 9.X, 10.X Revisions Deadline ====
Hong (Qualcomm) is fine with r04.
Lars (Sony) fine with r04.
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207060 P-CR Approval 23.700-05: KI#3, New solution of IAB-node mobility with dedicated TA Huawei, HiSilicon Rel-18 Revision of S2-2206093r04. Approved Approved
9.9 S2-2205653 P-CR Approval 23.700-05: KI#5, New Sol, Solution for UE location service via mobile IAB-node Ericsson Rel-18 r05 agreed. Revised to S2-2207061. New solution for KI#5 LiMeng (Huawei) asks questions
Qian (Ericsson) provides responses
alessio(nokia) comments this solution seems not working well
Qian (Ericsson) provides responses and indicate that r01 is provided in previous response.
Xiaoyan Shi (Intel) asks question for clarification.
Alessio(Nokia) I think we do need a revision to explain how what I commented on is resolved. as is the solution seems to have holes and is technically incomplete.
Qian (Ericsson) provides comments and r02.
Qian (Ericsson) provides responses.
Alessio(Nokia) comments that the solutions is still incomplete (meaning seems not working) as the AMF-UE is not known in the RAN
alessio(Nokia) comments that Qiam misunderstood the issue, r02 is not acceptable till the issue is resolved
Qian (Ericsson) provides comments indicating it's a misunderstanding of the functionality.
Xiaoyan Shi (Intel) replies to Qian.
Qian (Ericsson) provides comments and r03.
alessio(Nokia) provides r04
Hong (Qualcomm) comments.
Qian (Ericsson) responds.
Alessio(Nokia) replies to Hong (Qualcomm) comments.
alessio (nokia ) Comments that GUTI change happens at every MRU as per standards. we cannot change that. even when a Ue is in connected mode.
Qian (Ericsson) provides comments and r05.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207061 P-CR Approval 23.700-05: KI#5, New Sol, Solution for UE location service via mobile IAB-node Ericsson Rel-18 Revision of S2-2205653r05. Approved Approved
9.9 S2-2206856 P-CR Approval 23.700-05: TR 23.700-05: KI#5, New solution: Privacy check support for LCS via mobile base station relay Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2207062. New solution for KI#5 [resubmission of a not handled paper from last meeting.] LiMeng (Huawei) asks for clarification.
Hong (Qualcomm) replies to LiMeng and provides r01.
Yunjing (CATT) provides comments.
Hong (Qualcomm) replies to Yunjing and provides r02.
Yunjing(CATT) comments.
Hong (Qualcomm) replies to Yunjing.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207062 P-CR Approval 23.700-05: TR 23.700-05: KI#5, New solution: Privacy check support for LCS via mobile base station relay Qualcomm Incorporated Rel-18 Revision of S2-2206856r02. Approved Approved
9.9 S2-2205656 P-CR Approval 23.700-05: KI#7, New Sol, Solution for UE access via IAB-node control Ericsson Rel-18 r02 agreed. Revised to S2-2207063. New solution for KI#7 [to be used as baseline to merge S2-2206864 and S2-2206920, which are very similar]. LiMeng (Huawei) asks questions
alessio(Nokia) asks questions
Hong (Qualcomm) provides r01.
LiMeng (Huawei) comments on r01.
Alessio provides r02
==== 9.X, 10.X Revisions Deadline ====
Hong (Qualcomm) replies to LiMeng, and fine with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207063 P-CR Approval 23.700-05: KI#7, New Sol, Solution for UE access via IAB-node control Ericsson Rel-18 Revision of S2-2205656r02. Approved Approved
9.9 - - - Solution Updates: 9 submitted - - Docs:=8 -
9.9 S2-2206473 P-CR Approval 23.700-05: KI#2&3, Sol#4: resolve Ens Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.9 S2-2205652 P-CR Approval 23.700-05: KI#4, Sol#6, Update for mobility aspect Ericsson Rel-18 r05 agreed. Revised to S2-2207064. Solution#6 updates Lalith (Samsung) provides r01.
Qian (Ericsson) provides r02.
Lalith(Samsung) comments.
Qian (Ericsson) responds.
Lalith(Samsung) replies to Qian (Ericsson)
Hong (Qualcomm) comments, and prefer to use existing procedure description, instead of introducing a new one.
LiMeng (Huawei) prefers to not introduce a new procedure, and comments.
Xiaoyan Shi (Intel) comments.
Lalith (Samsung) provides r03.
Lalith (Samsung) comments.
Hong (Qualcomm) comments.
LiMeng (Huawei) comments on r03.
Lalith (Samsung) replies
Lalith(Samsung) provides r04.
Lalith(Samsung) replies to LiMeng (Huawei) and agrees to use a new term instead of forbidden area.
LiMeng (Huawei) responds to Lalith (Samsung). Suggests to use a new term instead of forbidden area.
LiMeng (Huawei) provides r05 with completing the procedure.
Lalith (Samsung) is OK with r05
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207064 P-CR Approval 23.700-05: KI#4, Sol#6, Update for mobility aspect Ericsson Rel-18 Revision of S2-2205652r05. Approved Approved
9.9 S2-2206623 P-CR Approval 23.700-05: KI #5, Sol #7: Update sol#7 to remove EN CATT Rel-18 Merged into S2-2207065 Solution#7 updates Lars (Sony) comments and provides r01
Hong (Qualcomm) asks about the overlap with S2-2206774.
Lars (Sony) I merged remaining update into S2-2206774r04. Please check.
Alessio(Nokia) ok with r04
Hong (Qualcomm) proposes to mark this contribution as merged with S2-2206774 and close this thread.
Yunjing (CATT) is fine to merge this contribution with S2-2206774.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.9 S2-2206774 P-CR Approval 23.700-05: 23.700-05: KI#5: updated Solution 7 Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2207065, merging and S2-2206623. Solution#7 update. Overlap w/ S2-2206623. To be converted to a new solution. Qian (Ericsson) asks questions
Alessio(Nokia) replies to Qian (Ericsson) and provides r01
Lars (Sony) asks questions and provides r02
Lars (Sony) asks questions and provides r03
Hong (Qualcomm) asks about the overlap with S2-2206623.
Lars (Sony) provides r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207065 P-CR Approval 23.700-05: 23.700-05: KI#5: updated Solution 7 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206774r04, merging and S2-2206623. Approved Approved
9.9 S2-2206622 P-CR Approval 23.700-05: KI #5, Sol #8: Update solution #8 CATT Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.9 S2-2206094 P-CR Approval 23.700-05: KI#5, Update solution#14 to remove EN Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.9 - - - Evaluations: 9 submitted - - Docs:=8 -
9.9 S2-2206791 P-CR Approval 23.700-05: 23.700-05: KI#1,3,6 evaluations and conclusions Nokia, Nokia Shanghai Bell Rel-18 CC#4: r06 with changes was proposed. r06 agreed. Revised to S2-2207066. To be used as placeholder for KI#1 evaluation/conclusion. [rest of the contents to be merged to other papers.] Alessio(nokia) provides r01 as focused on KI#1 as requested.
LiMeng (Huawei) comments.
Lars (Sony) comments.
Alessio(nokia) replies.
Hong (Qualcomm) provides r02.
Hong (Qualcomm) comments and fine with r03.
Qian (Ericsson) comments and provides r03.
LiMeng (Huawei) comments on r03 and provides r04.
Lars (Sony) ask a question.
alessio(Nokia) provides r05
Qian (Ericsson) provides r06
Alessio(nokia) cannot accept r06 unless Ericsson explains what sync is needed. here we are discussing establishing a secure connection to a OAM server and there is no particular RAN expertise that is involved hence our reluctance to accept r06.
Qian (Ericsson) provides responses
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) agrees Qian's view: it is too early to adopt solution#10 as the basis. Object to r05 and r06.
alessio(Nokia) proposes to use r06 with the note changed to 'Editor's note: this conclusion needs further discussion and is not final'
LiMeng (Huawei) proposes to use r06 with the note changed to 'Editor's note: this conclusion needs further discussion and is not final' + remove 'along the lines of solution 10'
alessio(Nokia) asks questions
alessio(Nokia) objects to r06 as is.
Hong (Qualcomm) suggests bringing this to CC#4 or CC#5.
Hong (Qualcomm) is fine with the proposal from LiMeng.
==== 9.X, 10.X Final Deadline ====
alessio(Nokia) Andy: this has to go to CC#5 as r06 is not acceptable and it is written in the notes.
Alessio(nokia) can live with 'LiMeng (Huawei) proposes to use r06 with the note changed to 'Editor's note: this conclusion needs further discussion and is not final' + remove 'along the lines of solution 10''
Revised
9.9 S2-2207066 P-CR Approval 23.700-05: 23.700-05: KI#1,3,6 evaluations and conclusions Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206791r06. Approved Approved
9.9 S2-2206095 P-CR Approval 23.700-05: Evaluation for KI#1 to KI#5 Huawei, HiSilicon Rel-18 r07 agreed. Revised to S2-2207067. To be used as placeholder for KI#4 evaluation/conclusion. [rest of the contents to be merged to other papers] LiMeng (Huawei) provides r01
LiMeng (Huawei) provides r03.
Hong (Qualcomm) provides r02.
Lalith(Samsung) provides r04.
LiMeng (Huawei) comments on r04.
Lalith (Samsung) provides r05
Hong (Qualcomm) comments and provide r06.
LiMeng (Huawei) prefers r06.
Lalith(Samsung) provides r07
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207067 P-CR Approval 23.700-05: Evaluation for KI#1 to KI#5 Huawei, HiSilicon Rel-18 Revision of S2-2206095r07. Approved Approved
9.9 S2-2206474 P-CR Approval 23.700-05: Evaluation and conclusion on KI#2 and KI#3 Vivo Rel-18 r09 agreed. Revised to S2-2207068. To be used as placeholder for KI#2 & #3 evaluation/conclusion. Zhenhua (vivo) provides r01.
LiMeng (Huawei) suggests to have the conclusion per KI, and comments.
Zhenhua (vivo) provides r02 and responds to LiMeng (Huawei).
Lars (Sony) comments on the conclusion part.
Qian (Ericsson) provides r03.
LiMeng (Huawei) agrees Lars (Sony), we can focus on evaluation in this meeting.
Zhenhua (vivo) provides r04
Lars (Sony) ask a question on r04
Zhenhua (vivo) answers to Lars (Sony)
Zhenhua (vivo) asks a general comments to Lars (Sony) and rapporteur
Lars (Sony) comments and propose that this tdoc only focus on evaluation.
Hong (Qualcomm) provides r05.
Zhenhua (vivo) provides r06.
Hong (Qualcomm) provides r07.
LiMeng (Huawei) provides r08.
alessio(nokia) kindly request the author to split out KI#2 and KI#3 evaluations. I read 'all solutions have no UE impact' but this is not correct if we consider IAB UE as a UE ??. can you clarify that the UE here is mean the UE served by the MBSR? Also is it so group mobility solutions proposed have no UE impact?
Hong (Qualcomm) provides r09.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207068 P-CR Approval 23.700-05: Evaluation and conclusion on KI#2 and KI#3 Vivo Rel-18 Revision of S2-2206474r09. Approved Approved
9.9 S2-2206859 P-CR Approval 23.700-05: TR 23.700-05: KI#5 and KI#6, Initial evaluation and conclusion Qualcomm Incorporated Rel-18 r10 agreed. Revised to S2-2207069. To be used as placeholder for KI#5 and #6 evaluation/conclusion. Lars (Sony) how to proceed with merging other papers into this
Hong (Qualcomm) provides r01 as placeholder of KI#5,#6 evaluation and conclusion. It incorporated contents from S2-2206452/6453/6624/6096/5655.
Lars (Sony) comment on r01 (on KI#5).
Hong (Qualcomm) replies to LiMeng.
Lars (Sony) replies to LiMeng.
LiMeng (Huawei) comments.
Lars (sony) provides r02.
LiMeng (Huawei) comments on r02.
Alessio (nokia) provides r03 to take into account the current shape of Sol7 after this meeting.
Hong (Qualcomm) replies to Qian.
Qian (Ericsson) asks questions.
Hong (Qualcomm) provides r04.
Lars (Sony) provides r05.
Qian (Ericsson) provides r06.
Lars (Sony) provides r07.
LiMeng (Huawei) provides r08.
alessio(nokia) provides r10
==== 9.X, 10.X Revisions Deadline ====
Hong (Qualcomm) is fine with r08 or r10.
Lars (Sony) is fine with r10.
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207069 P-CR Approval 23.700-05: TR 23.700-05: KI#5 and KI#6, Initial evaluation and conclusion Qualcomm Incorporated Rel-18 Revision of S2-2206859r10. Approved Approved
9.9 - - - LS Out (not counted for quota) - - Docs:=2 -
9.9 S2-2206841 LS OUT Approval [DRAFT] LS on FS_VMR solutions review Qualcomm Incorporated Rel-18 r05 agreed. Revised to S2-2207070, merging and S2-2206097 To merge in contents from S2-2206097. LiMeng (Huawei) provides r01 and merges the content of S2-2206097
Hong (Qualcomm) provides r02.
Qian (Ericsson) provides r03.
LiMeng (Huawei) provides r04.
Alessio(nokia) provides r05 which removes lengthy list of solutions and also removes questions not in scope of RAN (like whether OAM security makes sense or authorizing a MBSR makes sense).
Hong (Qualcomm) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.9 S2-2207070 LS OUT Approval [DRAFT] LS on FS_VMR solutions review Qualcomm Incorporated Rel-18 Revision of S2-2206841r05, merging and S2-2206097. Approved Approved
9.9 - - - Misc. (discussion papers) (not counted for quota) - - Docs:=1 -
9.9 S2-2206091 P-CR Discussion 23.700-05: Discussion on TAC of MBSR during IAB-node mobility Huawei, HiSilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.9 - - - Documents exceeding TU Budget - - Docs:=14 -
9.9 S2-2206854 P-CR Approval 23.700-05: TR 23.700-05: KI#3, new solution for efficient mobility when served by MBSR Qualcomm Incorporated Rel-18 Not Handled New solution for KI#3. Similar to that of 6093, and can consider merging w/ S2-2206093
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206639 P-CR Approval 23.700-05: KI #4, New Sol: Enabling roaming of MBSR using FPLMN list Samsung Rel-18 Not Handled New solution for KI#4. But, it overlaps w/ existing sol#6. Consider merging this into S2-2205652 Lalith (Samsung) comments S2-2206639 is merged into S2-2205652
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2205983 P-CR Approval 23.700-05: New Solution: Reusing existing procedures for Control of UE's access to 5GS via a mobile base station relay Rakuten Mobile Rel-18 Not Handled To be merged into S2-2206095
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206845 P-CR Approval 23.700-05: TR 23.700-05: KI#7, New solution: Control of UE s access to MBSR Qualcomm Rel-18 Not Handled New Solution for KI#7 Consider merging w/ S2-2205656
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206920 P-CR Approval 23.700-05: KI#7 new solution CAG based MBSR access control Intel Rel-18 Not Handled New solution for KI#7 Consider merging w/ S2-2205656.
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2205984 P-CR Approval 23.700-05: Update Solution#3 to consider the case of Macro base station in LTE Rakuten Mobile Rel-18 Not Handled Solution#3 update. Out of scope of current SID.
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2205654 P-CR Approval 23.700-05: KI#6, Sol#9, Update to remove ENs Ericsson Rel-18 Not Handled Postponed
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206858 P-CR Approval 23.700-05: TR 23.700-05: Sol#12, update on F1-C support during full migration Qualcomm Incorporated Rel-18 Not Handled Solution#12 update. Incorporated into evaluation of Sol#12.
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206452 P-CR Approval 23.700-05: KI#5: Initial Evaluation Sony Rel-18 Not Handled KI#5 evaluation [to be merged into S2-2206859]
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206453 P-CR Approval 23.700-05: KI#5: Initial Conclusions Sony Rel-18 Not Handled KI#5 conclusion [to be merged into S2-2206859]
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206624 P-CR Approval 23.700-05: KI #5: solution evaluation and conclusion for key issue#5 CATT Rel-18 Not Handled KI#5 evaluation [to be merged into S2-2206859]
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206096 P-CR Approval 23.700-05: KI#6, Evaluation and conclusion Huawei, HiSilicon Rel-18 Not Handled KI#6 evaluation [to be merged into 6859]
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2205655 P-CR Approval 23.700-05: KI#6, Evaluation and Conclusion Ericsson Rel-18 Not Handled KI#6 evaluation [to be merged into S2-2206859]
==== 9.X, 10.X Final Deadline ====
Not Handled
9.9 S2-2206097 LS OUT Approval [DRAFT] LS to RAN regarding Rel-18 FS_VMR Huawei, HiSilicon Rel-18 Merged into S2-2207070 To be merged into S2-2206841. Hong (Qualcomm) request to mark this as merged into S2-2206841.
Alessio(Nokia) assumes this is NOTED (or anyhow requests to do so) as we shall have one LS to RAN wGs
==== 9.X, 10.X Final Deadline ====
Merged
9.10 - - - Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) - - Docs:=64 -
9.10 - - - LS Out - - Docs:=2 -
9.10 S2-2206510 LS OUT Approval [DRAFT] LS on positioning information exchange between NG-RAN nodes Huawei, HiSilicon Rel-18 Noted Yunjing (CATT) provides comments
Guanglei (Huawei) is fine to postpone the LS
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.10 S2-2208093 LS OUT Approval [DRAFT] LS on Applicability of RAN PRUs for NTN scenarios Nokia Created at CC#2. Noted Guillaume (MediaTek Inc.) provides S2-2208093 in the inbox
Stephen (Qualcomm) comments that the LS is not needed
Guillaume (MediaTek Inc.) disagrees with Stephen (Qualcomm) on the need for the LS
Cai Simon (Nokia) provides r01
Guillaume (MediaTek Inc.): provides r02
Cai Simon (Nokia) accepts only r01, objects to all other revisions
Leo (Deutsche Telekom) objects r01, accepts r02
Cai Simon (Nokia) supports Stephen (Qualcomm) comments that the LS is not needed or r01 only, objects to all other revisions
Guillaume (MediaTek Inc.) provides r03. Cannot accept r01
Cai Simon (Nokia) objects also to r03
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) prefers r03 or r02 but is also okay with r01
Guillaume (MediaTek Inc.) repeats objecting to r01, and recommends r03. (provides r04 postDL just in case)
Cai Simon (Nokia) accepts r01 and objects to all other revisions
Leo (Deutsche Telekom) can accept r03 and r04, but objects to r01
==== 9.X, 10.X Final Deadline ====
Noted
9.10 - - - New Solutions - - Docs:=12 -
9.10 - - - New Solutions to KI#3 - - Docs:=3 -
9.10 S2-2206937 P-CR Approval 23.700-71: Use Group Information to Correlate GMLC and LMF Nokia, Nokia Shanghai Bell Rel-18 WITHDRAWN Cai Simon (Nokia) requests to withdraw the tdoc S2-2206937
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Withdrawn
9.10 S2-2206941 P-CR Approval 23.700-71: Use Group Information to Correlate GMLC and LMF Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207071. Runze (Huawei) provides comments.
Cai Simon (Nokia) clarifies Runze (Huawei) and provides r01
Runze (Huawei) replies to Simon(Nokia).
Cai Simon (Nokia) agrees with Runze (Huawei)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207071 P-CR Approval 23.700-71: Use Group Information to Correlate GMLC and LMF Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206941r01. Approved Approved
9.10 - - - New Solutions to KI#6 - - Docs:=1 -
9.10 S2-2205495 P-CR Approval 23.700-71: KI#6, New Solution on UE Positioning without UE/User Awareness IPLOOK Rel-18 Noted Yunjing(CATT) asks questions for clarification.
Junle Liao(IPLOOK) provides r01
Junle Liao(IPLOOK) replies and clarifies
Runze (Huawei) questions how this solution resolve the key issue.
Junle Liao(IPLOOK) replies that there may have different scenarios in the key issue.
Runze (Huawei) replies to Junle Liao(IPLOOK).
Leo (Deutsche Telekom) provides comments and objects this solution
Runze (Huawei) agrees with Leo (Deutsche Telekom), this solution cannot provide accurate UE location result.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.10 - - - New Solutions to KI#7 - - Docs:=3 -
9.10 S2-2206931 P-CR Approval 23.700-71: New Solution for KI#7: support of Positioning Reference Units Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2207072. Cai Simon (Nokia) asks questions
Yunjing(CATT) asks questions for clarification.
Stephen (Qualcomm) provides an r01 and responses to Yunjing (CATT) and Cai Simon (Nokia)
Guanglei (Huawei) comments and ask questions
Stephen (Qualcomm) replies to Guanglei (Huawei)
Yunjing (CATT) replies to Stephen (Qualcomm).
Stephen (Qualcomm) replies to Yunjing (CATT)
Yunjing (CATT) replies and provides r02.
Yunjing (CATT) replies and is fine to r01.
==== 9.X, 10.X Revisions Deadline ====
Leo (Deutsche Telekom) objects to r02 and is fine with r01.
Stephen (Qualcomm) also supports only r01
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207072 P-CR Approval 23.700-71: New Solution for KI#7: support of Positioning Reference Units Qualcomm Incorporated Rel-18 Revision of S2-2206931r01. Approved Approved
9.10 S2-2206942 P-CR Approval 23.700-71: Use PRU in 5G LCS Procedures Nokia, Nokia Shanghai Bell Rel-18 Approved Guanglei (Huawei) comments
Guanglei (Huawei) further comments and asks questions
Stephen (Qualcomm) provides some questions
Cai Simon (Nokia) clarifies to Stephen (Qualcomm)
Cai Simon (Nokia) clarifies to Guanglei (Huawei)
Richard (Ericsson) provides comments
Cai Simon (Nokia) clarifies to Richard (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 - - - New Solutions to KI#8 - - Docs:=7 -
9.10 S2-2206508 P-CR Approval 23.700-71: KI#8, New solution for location service contunity between NG-RAN nodes Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207073. Cai Simon (Nokia) provides comments
Yunjing (CATT) provides comments
Guanglei (Huawei) replies to Simon (Nokia), Yunjing (CATT) and provides r01
Cai Simon (Nokia) provides further response
==== 9.X, 10.X Revisions Deadline ====
Guanglei (Huawei) replies to Simon(Nokia).
Cai Simon (Nokia) agrees with further discussion and provides related materials
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207073 P-CR Approval 23.700-71: KI#8, New solution for location service contunity between NG-RAN nodes Huawei, HiSilicon Rel-18 Revision of S2-2206508r01. Approved Approved
9.10 S2-2206509 P-CR Approval 23.700-71: KI#8, New solution for location service continuity between EPS and 5GS (bi-direction) Huawei, HiSilicon Rel-18 Approved Cai Simon (Nokia) asks questions
Guanglei (Huawei) replies to Simon(Nokia)
Cai Simon (Nokia) provides further comments
Guanglei (Huawei) further replies to Simon(Nokia).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206618 P-CR Approval 23.700-71: KI#8, new Solution: LCS continuity Support for N26 based Handover CATT Rel-18 Approved Cai Simon (Nokia) provides comments
Yunjing (CATT) replies to Cai Simon (Nokia).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206749 P-CR Approval 23.700-71: KI #8, New solution: LCS session continuity due to UE mobility between NG-RAN Huawei, HiSilicon Rel-18 Noted Stephen (Qualcomm) provides comments
Runze (Huawei) replies to Qualcomm.
Stephen (Qualcomm) replies to Runze (Huawei)
Runze (Huawei) replies to Stephen (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) replies again to Runze (Huawei)
Stephen (Qualcomm) proposes to note this pCR
==== 9.X, 10.X Final Deadline ====
Noted
9.10 S2-2206950 P-CR Approval 23.700-71: KI#8 Support of LCS continuity when UE moves between 5GS and EPS Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207074. Guanglei (Huawei) provides comments and asks questions
Guanglei (Huawei) further comments..
Cai Simon (Nokia) clarifies to Guanglei (Huawei)
Cai Simon (Nokia) provides r01
Guanglei (Huawei) thanks Simon(Nokia) revision and further comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207074 P-CR Approval 23.700-71: KI#8 Support of LCS continuity when UE moves between 5GS and EPS Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206950r01. Approved Approved
9.10 - - - New Solutions to KI#9 - - Docs:=3 -
9.10 S2-2206507 P-CR Approval 23.700-71: KI#9, New Solution, UE location determination for Mobility Restriction enforcement Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207075. Cai Simon (Nokia) asks questions
Yuxin (Xiaomi) provides comments
Guanglei(Huawei) replies to Simon (Nokia) and provides r01
Guanglei (Huawei) replies to Yuxin(Xiaomi)
Stephen (Qualcomm) provides comments
Guanglei (Huawei) replies to Stephen(Qualcomm) and provides r02
Richard (Ericsson) provides comments
Guanglei (Huawei) replies to Richard (Ericsson) and provides r03
Yuxin (Xiaomi) comments
Richard (Ericsson) answers to Guanglei (Huawei)
Guanglei (Huawei) replies to Yuxin (Xiaomi) and Richard (E), provides r04
Richard (Ericsson) replies to Guanglei (Huawei)
Guanglei (Huawei) further replies to Richard (Ericsson).
Scott(Inspur) comments.
Guanglei (Huawei) replies to Scott(Inspur).
==== 9.X, 10.X Revisions Deadline ====
Leo (Deutsche Telekom) supports r04.
Jean Yves (Thales) comments
Guanglei (Huawei) thanks Leo(Deutsche Telekom) and Jean Yves (Thales)
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207075 P-CR Approval 23.700-71: KI#9, New Solution, UE location determination for Mobility Restriction enforcement Huawei, HiSilicon Rel-18 Revision of S2-2206507r04. Approved Approved
9.10 S2-2206943 P-CR Approval 23.700-71: FS_eLCS_Ph3 TR Solution to KI#9 Nokia, Nokia Shanghai Bell Rel-18 Noted Guillaume (MediaTek Inc.) objects to this pCR
Cai Simon (Nokia) clarifies to Guillaume (MediaTek Inc.)
Guillaume (MediaTek Inc.) responds to Simon (Nokia)
Cai Simon (Nokia) provides r01
Guillaume (MediaTek Inc.) objects to r01 (and any other version (original and future)) - this is out of scope.
Yunjing(CATT) provides comment.
Cai Simon (Nokia) clarifies to Guillaume (MediaTek Inc.) the R17 PRU usage
Cai Simon (Nokia) clarifies to Yunjing(CATT)
Guillaume (MediaTek Inc.) recommends Cai Simon (Nokia) to check the SID
Cai Simon (Nokia) clarifies the scope concern to Guillaume (MediaTek Inc.)
Guillaume (MediaTek Inc.) responds to Cai Simon (Nokia): your clarification is not in line with 3GPP status:
a. RAN: R18: PRUs not in scope (whether for TN or NTN)
b. RAN: R17: PRUs are TN only (not NTN)
c. SA: R17: eLCS_Ph2 had not support for PRU
d. SA: R18: eLCS_Ph3 introduces PRU support (based on R17 RAN PRU i.e. TN only)
e. SA: R18: eLCS_Ph3 WT#5 and WT#7 are self-contained
Stephen (Qualcomm) provides some comments
Guanglei (Huawei) provides comments
Cai Simon (Nokia) replies to Stephen (Qualcomm)
Cai Simon (Nokia) replies to Guanglei (Huawei)
Ming (CATT) asks Simon (Nokia) to modify procedure part.
Ming (CATT) thinks solutions for KI#7 could use PRU concept in R-17 with necessary add-ons.
Cai Simon (Nokia) clarifies with r02
Jean Yves (Thales) comments
Cai Simon (Nokia) clarifies to Jean Yves (Thales)
Guillaume (MediaTek Inc.) objects r02 and all other revisions of this pCR.
Jean Yves (Thales) is ok for sending LS to RAN1
David (Samsung) also supports the LS to RAN1 as a way forward for this issue.
Cai Simon (Nokia) provides r03 with EN of LS out
Cai Simon (Nokia) clarifies to David (Samsung)
Cai Simon (Nokia) provides r05 as further clarification
Cai Simon (Nokia) provides r04 without PRU
Leo (Deutsche Telekom) objects to this solution - all revisions.
Guillaume (MediaTek Inc.) objects to r05 and all previous revisions. Provides r06.
Guillaume (MediaTek Inc.) comments
Cai Simon (Nokia) provides r07
Cai Simon (Nokia) clarifies to Leo (Deutsche Telekom)
Guillaume (MediaTek Inc.) cannot accept r07, provides r08.
Cai Simon (Nokia) accepts r08
Guillaume (MediaTek Inc.): to be discussed jointly with 8093 (+revs)
Cai Simon (Nokia) reminds that Mediatek expressed r08 not related to PRU in 8093
==== 9.X, 10.X Revisions Deadline ====
Leo (Deutsche Telekom) still objects the original version and all revisions of this PCR
Leo (Deutsche Telekom) replies to Cai Simon (Nokia) and proposes to NOTE the contribution
Guillaume (MediaTek Inc.) suggests to note the paper if 8093 is noted.
==== 9.X, 10.X Final Deadline ====
Noted
9.10 - - - New Solutions to KI#4 & KI#11 - - Docs:=2 -
9.10 S2-2206582 P-CR Approval 23.700-71: KI #4 & KI#11, New Sol, LCS supports reporting the UE location only when the UE locates the target area defined with the finer granularity Vivo Rel-18 Approved Stephen (Qualcomm) provides some comments
Hank (vivo) replies to Stephen(Qualcomm) and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2207076 P-CR Approval 23.700-71: KI #4 & KI#11, New Sol, LCS supports reporting the UE location only when the UE locates the target area defined with the finer granularity Vivo Rel-18 Revision of S2-2206582r01. WITHDRAWN Withdrawn
9.10 - - - New Solutions to KI#12 - - Docs:=1 -
9.10 S2-2206938 P-CR Approval 23.700-71: Negotiable Deferred Location Request Nokia, Nokia Shanghai Bell, vivo Rel-18 Noted Stephen (Qualcomm) provides comments
Cai Simon (Nokia) clarifies to Stephen (Qualcomm)
Stephen (Qualcomm) replies to Cai Simon (Nokia)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.10 - - - Solution Updates to Sol#3,4 and etc.. - - Docs:=22 -
9.10 S2-2205813 P-CR Approval 23.700-71: Update Solution #1: Positioning protocol transport over User Plane Ericsson Rel-18 r01 agreed. Revised to S2-2207077. Cai Simon (Nokia) asks questions
Richard (Ericsson) answers questions from Cai Simon (Nokia)
Cai Simon (Nokia) asks further questions
Yunjing (CATT) asks questions for clarification.
Richard (Ericsson) answering questions from CATT and Nokia
Stephen (Qualcomm) provides comments
Cai Simon (Nokia) reminds risks of the solution
Richard (Ericsson) answering questions from Stephen
Yunjing (CATT) replies to Richard (Ericsson) and provides r01.
Richard (Ericsson) reminds Nokia that the comments are going towards evaluation and should be submitted as such, provides further responses inline
Richard (Ericsson) accepts r01 from Yunjing (CATT)
Cai Simon (Nokia) provides further comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207077 P-CR Approval 23.700-71: Update Solution #1: Positioning protocol transport over User Plane Ericsson Rel-18 Revision of S2-2205813r01. Approved Approved
9.10 S2-2206505 P-CR Approval 23.700-71: KI#1, Update Solution#3 to cover Deffered MT-LR and LMF Change Procedure Huawei, HiSilicon Rel-18 Approved Cai Simon (Nokia) asks questions
Guanglei(Huawei) replies to Simon (Nokia)
Scott(Inspur) comments.
Guanglei (Huawei) thanks Scott (Inspur) supporting
Richard(Ericsson) provides comments
Guanglei (Huawei) responses to Richard (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206656 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#2 Update on Solution 4 ZTE Rel-18 r01 agreed. Revised to S2-2207078. Yunjing(CATT) asks questions for clarification.
Jinguo(ZTE) provides r01 and answers
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207078 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#2 Update on Solution 4 ZTE Rel-18 Revision of S2-2206656r01. Approved Approved
9.10 S2-2206746 P-CR Approval 23.700-71: KI #2, Sol #5: Update to clarify the functionality of any AMF Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207079. Cai Simon (Nokia) asks a question
Yunjing(CATT) asks questions for clarification.
Cai Simon (Nokia) asks for clarifications with pending question
Runze (Huawei) replied to Cai Simon (Nokia) and provides r01.
Runze (Huawei) replies to Yunjing(CATT)..
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207079 P-CR Approval 23.700-71: KI #2, Sol #5: Update to clarify the functionality of any AMF Huawei, HiSilicon Rel-18 Revision of S2-2206746r01. Approved Approved
9.10 S2-2206747 P-CR Approval 23.700-71: KI #3, Sol #9: another option to select LMF and or GMLC Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207080. Yunjing(CATT) asks questions for clarification.
Runze (Huawei) replies to Yunjing (CATT), and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207080 P-CR Approval 23.700-71: KI #3, Sol #9: another option to select LMF and or GMLC Huawei, HiSilicon Rel-18 Revision of S2-2206747r01. Approved Approved
9.10 S2-2206580 P-CR Approval 23.700-71: KI #4, Sol #10, Update to optimize the privacy check between LCS and NWDAF Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206581 P-CR Approval 23.700-71: KI #4, Sol #13, Update to remove Ens Vivo Rel-18 Approved Yunjing(CATT) provides comments.
Hank (vivo) replies to Yunjing(CATT).
Yunjing(CATT) replies.
Hank (vivo) replies to Yunjing(CATT) and believe this solution can be one option for the interaction between LCS and NWDAF.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206730 P-CR Approval 23.700-71: KI#7: Sol#17 updates Samsung Rel-18 r02 agreed. Revised to S2-2207081, merging and S2-2206619 Stephen (Qualcomm) asks some questions
David (Samsung) replies to Qualcomm, provides r01.
David (Samsung) provides also r02 as an attempt to merge S2-2206619.
Yunjing (CATT) thanks for merging the idea from S2-2206619.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207081 P-CR Approval 23.700-71: KI#7: Sol#17 updates Samsung Rel-18 Revision of S2-2206730r02, merging and S2-2206619. Approved Approved
9.10 S2-2206619 P-CR Approval 23.700-71: KI#7, sol#17: update solution to clarify the Reference UE CATT Rel-18 Merged into S2-2207081 Yunjing (CATT) proposes to merge this pCR into S2-2206730.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.10 S2-2206826 P-CR Approval 23.700-71: KI#9: Sol#18 updates to address ENs Samsung Rel-18 r01 agreed. Revised to S2-2207082. David (Samsung) provides r01
==== 9.X, 10.X Revisions Deadline ====
Yuxin (Xiaomi) ok with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207082 P-CR Approval 23.700-71: KI#9: Sol#18 updates to address ENs Samsung Rel-18 Revision of S2-2206826r01. Approved Approved
9.10 S2-2206939 P-CR Approval 23.700-71: NWDAF based Indoor or Outdoor in Location Services Nokia, Nokia Shanghai Bell Rel-18 Approved Hank (vivo) provides comments.
Cai Simon (Nokia) clarifies to Hank (vivo)
Yunjing (CATT) provides comments.
Cai Simon (Nokia) clarifies to Yunjing (CATT)
Yunjing (CATT) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206940 P-CR Approval 23.700-71: Support of LCS mobility when UE moves between NG-RAN nodes Nokia, Nokia Shanghai Bell Rel-18 Approved Guanglei (Huawei) comments
Cai Simon (Nokia) clarifies to Guanglei (Huawei)
Guanglei (Huawei) further comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206461 P-CR Approval 23.700-71: KI#9, Sol #23: Addressing the editor s note in solution#23 Xiaomi Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.10 S2-2206620 P-CR Approval 23.700-71: KI#9, Sol#24: update to sol#24 CATT Rel-18 r01 agreed. Revised to S2-2207083. Cai Simon (Nokia) asks questions
Yuxin (Xiaomi) provides comments
Yunjing (CATT) replies and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207083 P-CR Approval 23.700-71: KI#9, Sol#24: update to sol#24 CATT Rel-18 Revision of S2-2206620r01. Approved Approved
9.10 S2-2206748 P-CR Approval 23.700-71: KI #12, Sol #26: LPHAP indication provisioning to RAN Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.10 - - - Evolutions & Conclusions - - Docs:=2 -
9.10 - - - To KI#1, KI#7, KI#10 - - Docs:=2 -
9.10 S2-2206930 P-CR Approval 23.700-71: KI#1, KI#7, KI#10: Evaluation and Conclusions Qualcomm Incorporated Rel-18 r05 agreed. Revised to S2-2207084. Yunjing(CATT) provides r01 remove the evaluation and conclusion related to KI#7.
Stephen (Qualcomm) provides an r02
Cai Simon (Nokia) objects r00, r01 and provides r02
Guanglei (Huawei) provides r04 based on r02.
Cai Simon (Nokia) provides r05 based on r04 and objects to r00, r01,r02 to r04
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) can agree r02, r04 or r05
Richard (Ericsson) can agree r02, r04 or r05
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207084 P-CR Approval 23.700-71: KI#1, KI#7, KI#10: Evaluation and Conclusions Qualcomm Incorporated Rel-18 Revision of S2-2206930r05. Approved Approved
9.10 - - - To KI#2 - - Docs:=5 -
9.10 S2-2206915 P-CR Approval 23.700-71: KI#2: Conclusions Intel Rel-18 Noted Jinguo(ZTE) disagree the analysis and suggest to merge this paper into 6657 or 6751
Runze (Huawei) objects to the paper.
Saso (Intel) replies to Runze (Huawei).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.10 S2-2206751 P-CR Approval 23.700-71: Key Issue#2:evaluation Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207085. Jinguo(ZTE) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207085 P-CR Approval 23.700-71: Key Issue#2:evaluation Huawei, HiSilicon Rel-18 Revision of S2-2206751r01. Approved Approved
9.10 S2-2206657 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#2 Evaluation and Conclusion ZTE Rel-18 r01 agreed. Revised to S2-2207086. Jinguo(ZTE) provides r01
Yunjing(CATT) provides r02.
Jinguo(ZTE) prefer r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207086 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#2 Evaluation and Conclusion ZTE Rel-18 Revision of S2-2206657r01. Approved Approved
9.10 - - - To KI#3 - - Docs:=3 -
9.10 S2-2206658 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#3 Evaluation and Conclusion ZTE Rel-18 r02 agreed. Revised to S2-2207087. Jinguo(ZTE) provides r01 to remove evaluation part and focus on conclusion only
Stephen (Qualcomm) asks a question
Jinguo(ZTE) provides response.
Stephen (Qualcomm) replies to Jinguo (ZTE)
Jinguo(ZTE) provides r02
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) can agree the r02
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207087 P-CR Approval 23.700-71: FS_eLCS_Ph3 KI#3 Evaluation and Conclusion ZTE Rel-18 Revision of S2-2206658r02. Approved Approved
9.10 S2-2206752 P-CR Approval 23.700-71: Key Issue#3: evaluation Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.10 - - - To KI#4 - - Docs:=3 -
9.10 S2-2205576 P-CR Approval 23.700-71: KI#4: Evaluation and interim conclusions Lenovo Rel-18 Merged into S2-2207088 Yunjing(CATT) propose to merge S2-2205576 into S2-2206615.
==== 9.X, 10.X Final Deadline ====
Merged
9.10 S2-2206615 P-CR Approval 23.700-71: KI#4: solution evaluation and conclusion for key issue #4 CATT Rel-18 r04 agreed. Revised to S2-2207088, merging and S2-2205576 Jinguo(ZTE) disagree the analysis and suggest to merge this paper into 6657 or 6751
Yunjing(CATT) believes Jinguo(ZTE) uses wrong pCR number in the subject.
Yunjing(CATT) provides r01 to merge S2-2205576.
Dimitris (Lenovo) provides r02
Cai Simon (Nokia) provides r03
Hank (vivo) provides r04.
==== 9.X, 10.X Revisions Deadline ====
Yunjing (CATT) replies.
Richard (Ericsson) comments and supports r03
Dimitris (Lenovo) ok with r03
Hank (vivo) corrects the proposed change at the end of the conclusion part of r04 and suggests to discuss at CC#5.
+ remove the last bullet '- the interface between NWDAF and AMF supporting the finer granularity location information delivery is one option to be considered.'
+ Add an EN as 'Editor's NOTE: how to report the UE location only when the UE locates the target area defined with the finer granularity is FFS.'
Yunjing (CATT) replies to Hank (vivo).
Hank (vivo) replies to Yunjing and still suggests treating r04 as the baseline with some corrections I listed.
Hank (vivo) provides r05 based on r04 with corrections.
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207088 P-CR Approval 23.700-71: KI#4: solution evaluation and conclusion for key issue #4 CATT Rel-18 Revision of S2-2206615r04, merging and S2-2205576. Approved Approved
9.10 - - - To KI#5 - - Docs:=1 -
9.10 S2-2206506 P-CR Approval 23.700-71: Evaluation and conclusion of KI# 5 of FS_eLCS_Ph3 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.10 - - - To KI#6 - - Docs:=2 -
9.10 S2-2206616 P-CR Approval 23.700-71: KI #6: Add solution evaluation and conclusion for key issue#6 CATT Rel-18 r01 agreed. Revised to S2-2207089. Devaki (Nokia) proposes that this paper can be merged with S2-2205726.
Yunjing(CATT) believes Devaki (Nokia) uses wrong pCR number in the subject.
Stephen (Qualcomm) provides some comments
Yunjing (CATT) replies and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207089 P-CR Approval 23.700-71: KI #6: Add solution evaluation and conclusion for key issue#6 CATT Rel-18 Revision of S2-2206616r01. Approved Approved
9.10 - - - To KI#7 - - Docs:=2 -
9.10 S2-2206617 P-CR Approval 23.700-71: KI#7: Solution Evaluation and Conclusion for PRU in key issue #7 CATT Rel-18 r07 agreed. Revised to S2-2207090. Yunjing(CATT) provides r01 to merge the evaluation and conclusion related to KI#7 in S2-2206930.
Guanglei (Huawei) provides r02
Stephen (Qualcomm) provides an r03
Guanglei (Huawei) provides r04
Yunjing (CATT) provides r05 and r06.
Guanglei (Huawei) prefers r05
Stephen (Qualcomm) provides an r07 based on the r05
==== 9.X, 10.X Revisions Deadline ====
Yunjing (CATT) can accept r07.
Stephen (Qualcomm) can accept r03 or r07
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207090 P-CR Approval 23.700-71: KI#7: Solution Evaluation and Conclusion for PRU in key issue #7 CATT Rel-18 Revision of S2-2206617r07. Approved Approved
9.10 - - - To KI#9 - - Docs:=2 -
9.10 S2-2206462 P-CR Approval 23.700-71: KI#9: Initial Solution Evaluations for KI#9 Xiaomi Rel-18 r03 agreed. Revised to S2-2207091. Stephen (Qualcomm) provides some comments
David (Samsung) comments and provides r01.
Yuxin (Xiaomi) provides r02.
Cai Simon (Nokia) provides comments
Yuxin (Xiaomi) replies to Cai Simon (Nokia)
David (Samsung) comments.
Stephen (Qualcomm) provides more comments
David (Samsung) provides r03
==== 9.X, 10.X Revisions Deadline ====
Yuxin (Xiaomi) is fine with r03
==== 9.X, 10.X Final Deadline ====
Revised
9.10 S2-2207091 P-CR Approval 23.700-71: KI#9: Initial Solution Evaluations for KI#9 Xiaomi Rel-18 Revision of S2-2206462r03. Approved Approved
9.11 - - - Study on Edge Computing Phase 2 (FS_EDGE_Ph2) - - Docs:=96 -
9.11 - - - LS IN - - Docs:=6 -
9.11 S2-2205454 LS In Information LS from GSMA: East/West Bound Interface for Telco Edge consideration GSMA OPAG (OPAG_25_Doc_05_ETSI-3GPP LS) - Noted Patrice (Huawei) proposes to note the LS as it is provided for information.
==== 9.X, 10.X Revisions Deadline ====
Noted
9.11 S2-2205468 LS In Information LS from SA WG6: LS on Clarification of Edge Node Sharing SA WG6 (S6-222004) Rel-18 Noted Patrice (Huawei) proposes to note the LS as it is provided for information.
==== 9.X, 10.X Revisions Deadline ====
Noted
9.11 S2-2206711 LS OUT Approval [DRAFT] LS on GSMA Hosted EASDF Sony Rel-18 Noted Hyesung (Samsung) comments
Dan(China Mobile) comments and think this LS is not needed
Xinpeng(Huawei) shares the same view with Dan(China Mobile).
Svante (Sony) comments
Dario (Qualcomm) comments that before sending the LS we need to agree on the solution.
==== 9.X, 10.X Revisions Deadline ====
Magnus (Ericsson) assumes this LS will be noted
Dan (China Mobile) object this LS
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2206876 LS OUT Approval [DRAFT] LS on charging model for HR PDU Session with SBO in VPLMN Qualcomm Incorporated Rel-18 Source field incorrect! Noted Dan (China Mobile) provides r01 with adding GSMA OPG charing requirement to SA5.
Hyesung (Samsung) provides r02
Dario (Qualcomm) provides r04 (could not upload r03).
Dan (China Mobile) provides r06 please ignore r05
==== 9.X, 10.X Revisions Deadline ====
Hyesung (Samsung) is fine with r04 and r06.
Xinpeng(Huawei) proposes to note 6876.
Dario (Qualcomm) proposes to go with r06 or r04.
Xinpeng(Huawei) replies to Dario (Qualcomm).
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2206963 LS In Action LS from GSMA OPAG: Network federation interface for Telco edge consideration GSMA OPAG (OPAG_34_Doc_06) Postponed Postponed
9.11 S2-2206964 LS In Action LS from GSMA OPAG: Network integration interface for Telco edge consideration GSMA OPAG (OPAG_34_Doc_07) Postponed Postponed
9.11 - - - KI Updates (removal of ENs) - - Docs:=21 -
9.11 - - - KI#1 - KI update - - Docs:=2 -
9.11 S2-2206846 P-CR Approval 23.700-48: KI#1 Update to remove EN Samsung Rel-18 r01 agreed. Revised to S2-2207738. Yuan Tao (CATT) comments.
Hui (Huawei) don't think the assumption is needed.
Jicheol (Samsung) clarifies the intention of the first sentense.
Patrice (Huawei, rapporteur) informs that an editorial CR is planned for removal of stale ENs before submission of the TR for approval.
Dario (Qualcomm) comments.
Laurent (Nokia): Comments, this PCR not needed
Jicheol (Samsung) comments and provides r01.
==== 9.X, 10.X Revisions Deadline ====
Hui (Huawei) fine with r01.
Patrice (Huawei, rapporteur) comments.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207738 P-CR Approval 23.700-48: KI#1 Update to remove EN Samsung Rel-18 Revision of S2-2206846r01. Approved Approved
9.11 - - - KI#2 - KI update - - Docs:=1 -
9.11 S2-2206227 P-CR Approval 23.700-48: KI#2 update use cases to remove Ens Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.11 - - - Solution updates / New solutions - - Docs:=20 -
9.11 - - - KI#1 - HR scenario solution updates - - Docs:=11 -
9.11 S2-2205618 P-CR Approval 23.700-48: KI #1, Sol #25: Solution update Ericsson Rel-18 r01 agreed. Revised to S2-2207739. Hui (Huawei) provides comments.
Magnus O (Ericsson) provides r01
Hui (Huawei) asks for clarification on r01
Magnus (Ericsson) provides some answers
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207739 P-CR Approval 23.700-48: KI #1, Sol #25: Solution update Ericsson Rel-18 Revision of S2-2205618r01. Approved Approved
9.11 S2-2206017 P-CR Approval 23.700-48: KI#1, Sol#26: Update to remove ENs Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206063 P-CR Approval 23.700-48: KI#1, Solution#24 Update: Reuse Option D after UL-CL Insertion Intel Rel-18 r02 agreed. Revised to S2-2207740. Jicheol (Samsung) provides r01.
Hui (Huawei) provides r02.
Jicheol (Samsung) comments.
Changhong (Intel) is OK with r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207740 P-CR Approval 23.700-48: KI#1, Solution#24 Update: Reuse Option D after UL-CL Insertion Intel Rel-18 Revision of S2-2206063r02. Approved Approved
9.11 S2-2206219 P-CR Approval 23.700-48: Solution update for Sol#1 China Mobile Rel-18 r02 agreed. Revised to S2-2207741. Hui (Huawei) provides comments.
Dan(China Mobile) response and provide r01
Dario (Qualcomm) comments on V-SMF modifying the content of ePCO.
Dan (China Mobile) provide r02 to reflect the comment
Hui (Huawei) provides further comments.
Dan(China Mobile) provides response
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207741 P-CR Approval 23.700-48: Solution update for Sol#1 China Mobile Rel-18 Revision of S2-2206219r02. Approved Approved
9.11 S2-2206224 P-CR Approval 23.700-48: KI#1, Sol#4 update to remove EN Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206428 P-CR Approval 23.700-48: 23.700-48 KI #1, Sol #5: Update to clarify EAS re-discovery CATT Rel-18 r02 agreed. Revised to S2-2207742. Hui (Huawei) provides comments.
Magnus (Ericsson) provides comments
Yuan Tao (CATT) replies and provides r01.
Hui (Huawei) provides further comments to r01.
Yuan Tao (CATT) provides r02.
==== 9.X, 10.X Revisions Deadline ====
Hui (Huawei) fine with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207742 P-CR Approval 23.700-48: 23.700-48 KI #1, Sol #5: Update to clarify EAS re-discovery CATT Rel-18 Revision of S2-2206428r02. Approved Approved
9.11 S2-2206839 P-CR Approval 23.700-48: KI#1 Sol #2 Update Samsung Rel-18 Approved Hui (Huawei) provides comments.
Jicheol (Samsung) comments.
Hui (Huawei) comments.
Tianqi (China Unicom) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 - - - KI#1 - New HR solution - - Docs:=3 -
9.11 S2-2206874 DISCUSSION Discussion KI#1:HR+SBO considerations Qualcomm Incorporated Rel-18 Noted Hui (Huawei) proposes to note the paper since it's a discussion.
Dario (Qualcomm) replies.
Hui (Huawei) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2206875 P-CR Approval 23.700-48: KI#1:HR+SBO: New Solution Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2207743. Huazhang (vivo) provides comments
Hui (Huawei) provides comments
Dario (Qualcomm) replies to Hui and Huazhang.
Huazhang (vivo) reply to Dario (QC), and request to MNO to decide the static DNS server to UE
Hui (Huawei) replies to Dario.
Tingfang Tang (Lenovo) clarifies and comments .
Dario (Qualcomm) comments and provides r01
==== 9.X, 10.X Revisions Deadline ====
Tingfang Tang (Lenovo) further clarifies and comments.
Huazhang (vivo) ask Dario to provide a new revision, to have the impact part of UE.
For example, the indication from UE to 5GC, and the UE selects the DNS server with precedence.
Dario (Qualcomm) OK w/ Huazhang proposal. Proposes to agree r01 + UE Impacts in clause 6.X.3:
- Indicates capability to CN.
- Receives in ePCO two IP addresses and preference indication.
- Considers precedence indication when selecting IP address for DNS resolution.
Dario (Qualcomm) OK w/ Huazhang proposal. Proposes to agree r01 + UE Impacts in clause 6.X.3:
- Indicates capability to CN.
- Receives in ePCO two IP addresses and preference indication.
- Considers precedence indication when selecting IP address for DNS resolution.
==== 9.X, 10.X Final Deadline ====
Huazhang (vivo) is ok to r01B, thank Dario
Revised
9.11 S2-2207743 P-CR Approval 23.700-48: KI#1:HR+SBO: New Solution Qualcomm Incorporated Rel-18 Revision of S2-2206875r01. Approved Approved
9.11 - - - KI#1 - LBO scenario solution updates - - Docs:=6 -
9.11 S2-2205619 P-CR Approval 23.700-48: KI #1, Sol #27: Solution update Ericsson Rel-18 r03 agreed. Revised to S2-2207744. Hongsuk Kim (LGE) merges S2-2205679 in, and provides r01 on S2-2205619 KI#1, Solution_27_update.
Hui (Huawei) provides comments.
Magnus H (Ericsson) provides comment
Hui (Huawei) comments
Magnus O (Ericsson) provides r02
Dario (Qualcomm) asks question for clarification
Hui (Huawei) provides r03
Huazhang (vivo) ask a question
Tingfang Tang (Lenovo) replies to Huazhang.
Huazhang (vivo) reply to Tingfang(Lenovo)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207744 P-CR Approval 23.700-48: KI #1, Sol #27: Solution update Ericsson Rel-18 Revision of S2-2205619r03. Approved Approved
9.11 S2-2206456 P-CR Approval 23.700-48: Update of Solution#9 Sony Rel-18 r03 agreed. Revised to S2-2207745. Mike (InterDigital) comments
Hui (Huawei) provides comments
Svante (Sony) answers on comments
Dario (Qualcomm) asks question for clarification.
Hyesung (Samsung) comments.
Hui (Huawei) further comments
Svante (Sony) provide r01 and answers to questions
Hyesung (Samsung) provides further comments
Svante (Sony) provides comments
Svante (Sony) comments and provide r02
Dario (Qualcomm) comments.
Svante (Sony) comments and provide r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207745 P-CR Approval 23.700-48: Update of Solution#9 Sony Rel-18 Revision of S2-2206456r03. Approved Approved
9.11 S2-2206806 P-CR Approval 23.700-48: Update to solution 6 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207746. Hui (Huawei) provides comments.
Laurent (Nokia): provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207746 P-CR Approval 23.700-48: Update to solution 6 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206806r01. Approved Approved
9.11 - - - KI#3 - Solution update - - Docs:=1 -
9.11 S2-2206737 P-CR Approval 23.700-48: Updates to sol#31 for KI#3 Lenovo Rel-18 Approved Xinpeng(Huawei) asks for clarification.
Tingfang Tang (Lenovo) replies to Xinpeng.
Xinpeng(Huawei) replies to Tingfang Tang (Lenovo).
Laurent (Nokia): asks questions
Tingfang Tang (Lenovo) replies to Xinpeng and Laurent.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 - - - KI#3 - New solution - - Docs:=1 -
9.11 S2-2206044 P-CR Approval 23.700-48: KI#3, New Sol: Providing weighted traffic offload policy for a set of UEs NEC Rel-18 Noted Tingfang Tang (Lenovo) asks for clarification.
Hiroshi (NEC) replies to Tingfang Tang.
Tingfang Tang (Lenovo) comments.
Hiroshi (NEC) reply to Tingfang Tang.
Patrice (Huawei) asks for clarification regarding the relevance with respect to KI#3.
Hiroshi (NEC) provides r01.
Laurent (Nokia): Comments, not sure it is in (sid) scope
Hiroshi (NEC) replies to Laurent(Nokia)
Patrice (Huawei) answers, still has concerns.
==== 9.X, 10.X Revisions Deadline ====
Hiroshi (NEC) replies to Patrice (Huawei).
Patrice (Huawei) maintains the concern.
Patrice (Huawei) is afraid he has to object to the contribution, as it is not within the scope of KI#3.
==== 9.X, 10.X Final Deadline ====
Noted
9.11 - - - KI#4 - Solution updates - - Docs:=7 -
9.11 S2-2206141 P-CR Approval 23.700-48: KI#4 - update sol#16 Selecting the same EAS-DNAI for collection of UEs Huawei, HiSilicon Rel-18 Approved Tingfang Tang (Lenovo) asks for clarification.
Magnus H (Ericsson) comments
Xinpeng(Huawei) replies to Tingfang Tang (Lenovo).
Tingfang Tang (Lenovo) asks for further clarification.
Shubhranshu (Nokia) comments
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Tugce (NTT DOCOMO) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206301 P-CR Approval 23.700-48: KI#4, Sol#18 update to solve the ENs Vivo Rel-18 r05 agreed. Revised to S2-2207747. Xinpeng(Huawei) asks for clarification.
Yuan Tao (CATT) replies to Xinpeng (Huawei) and provides r01.
Tingfang Tang (Lenovo) asks for clarification for r01.
Huazhang (vivo) reply to Tingfang(Lenovo) and provides r02
Yuan Tao (CATT) provides r03.
Tingfang Tang (Lenovo) asks further clarification for r03.
Huazhang (vivo) reply to Tingfang (Lenovo)
Huazhang (vivo) provides r04
Tingfang Tang (Lenovo) asks further clarification.
Yuan Tao (CATT) responses.
Xinpeng(Huawei) replies to Yuan Tao (CATT).
Tingfang Tang (Lenovo) provides r05.
==== 9.X, 10.X Revisions Deadline ====
Huazhang (vivo) agree r05, thanks Tingfang
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207747 P-CR Approval 23.700-48: KI#4, Sol#18 update to solve the ENs Vivo Rel-18 Revision of S2-2206301r05. Approved Approved
9.11 S2-2206738 P-CR Approval 23.700-48: Updates to sol#35&36 for KI#4 Lenovo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206899 P-CR Approval 23.700-48: Solution #19 Updates Nokia, Nokia Shanghai Bell Rel-18 Approved Tingfang Tang (Lenovo) asks for clarification.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) comments.
Shubhranshu (Nokia) comments
Magnus H (Ericsson) comments
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Tingfang Tang (Lenovo) comments.
==== 9.X, 10.X Revisions Deadline ====
Tingfang Tang (Lenovo) prefers r01, can live with r00.
Patrice (Huawei, rapporteur) indicates that r01 was provided by Tingfang (Lenovo) before the revision deadline, but was not mentioned explicitly in her comment.
Shubhranshu (Nokia) proposes to agree r00
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206911 P-CR Approval 23.700-48: Solution #37 Updates Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207748. Xinpeng(Huawei) asks for clarification.
Tingfang Tang (Lenovo) asks for clarification.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207748 P-CR Approval 23.700-48: Solution #37 Updates Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206911r01. Approved Approved
9.11 - - - KI#4 - New solution - - Docs:=2 -
9.11 S2-2205622 P-CR Approval 23.700-48: KI #4, New Sol: PCF controlling common DNAI Ericsson Rel-18 r01 agreed. Revised to S2-2207749. Xinpeng(Huawei) asks for clarification.
Tingfang Tang (Lenovo) asks for clarification.
Magnus H (Ericsson) provides comment
Shubhranshu (Nokia) comments
Magnus H (Ericsson) comments
Xinpeng(Huawei) shares the same view as Magnus H (Ericsson) on the single SMF issue.
Magnus H (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
Tingfang Tang (Lenovo) is OK with r01, objects r00.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207749 P-CR Approval 23.700-48: KI #4, New Sol: PCF controlling common DNAI Ericsson Rel-18 Revision of S2-2205622r01. Approved Approved
9.11 - - - KI#5 - Solution updates - - Docs:=8 -
9.11 S2-2206142 P-CR Approval 23.700-48: KI#5 - update sol#38 EAS Discovery for EHE shared with other PLMN Huawei, HiSilicon Rel-18 Approved Hyesung (Samsung) asks questions.
Xinpeng(Huawei) replies to Hyesung (Samsung).
Dario (Qualcomm) comments.
Hyesung (Samsung) comments.
Xinpeng(Huawei) replies to Dario (Qualcomm).
Tingfang Tang (Lenovo) asks clarification to Xinpeng(Huawei).
Xinpeng(Huawei) replies to Tingfang Tang (Lenovo).
Xinpeng(Huawei) replies to Hyesung (Samsung) and provides r01.
Tingfang Tang (Lenovo) asks further clarification to Xinpeng(Huawei).
Tingfang Tang (Lenovo) provides comments.
Hyesung (Samsung) replies.
Tingfang Tang (Lenovo) replies to Xinpeng(Huawei).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206294 P-CR Approval 23.700-48: Solution update for Sol#40 China Mobile Rel-18 r05 agreed. Revised to S2-2207750. Dario (Qualcomm) asks clarification wrt to this solution and the requirement of GSMA OPG topology hiding
Dan(China Mobile) reply and provide r01
Dario (Qualcomm) comments.
Xinpeng(Huawei) comments.
Dan (China Mobile) please ignore r02 which there are some mistakes
Dan (China Mobile) provide r03
Tingfang Tang (Lenovo) asks clarification on r03
Dan (China Mobile) reply
Tingfang Tang (Lenovo) provides r04
Dan(China Mobile) reply and provide r05
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207750 P-CR Approval 23.700-48: Solution update for Sol#40 China Mobile Rel-18 Revision of S2-2206294r05. Approved Approved
9.11 S2-2206432 P-CR Approval 23.700-48: 23.700-48 KI #5, Sol #39: Update to clarify EAS relocation between operators CATT Rel-18 r05 agreed. Revised to S2-2207751. Jicheol (Samsung) provides r01.
Yuan Tao (CATT) replies to Jicheol (Samsung).
Xinpeng(Huawei) comments.
Yuan Tao (CATT) replies.
Xinpeng(Huawei) asks for clarifications.
Yuan Tao (CATT) replies and provides r02.
Xinpeng(Huawei) replies to Yuan Tao (CATT).
Dario (Qualcomm) asks questions for clarification.
Yuan Tao (CATT) replies to Xinpeng(Huawei) and provides r03.
Yuan Tao (CATT) replies to Dario (Qualcomm).
Yuan Tao (CATT) replies to Xinpeng(Huawei).
Hui (Huawei) provides comments to KI#1 parts.
Tingfang Tang (Lenovo) clarifies.
Yuan Tao (CATT) replies to Tingfang Tang (Lenovo).
Tingfang Tang (Lenovo) further clarifies on the EDI with PLMNID.
Yuan Tao (CATT) replies to Hui (Huawei).
Yuan Tao (CATT) replies and provides r04 .
Tingfang Tang (Lenovo) asks for further clarification and comments.
Yuan Tao (CATT) replies to Tingfang(Lenovo).
Shubhranshu (Nokia) comments
Tingfang Tang (Lenovo) further comments.
Yuan Tao (CATT) provides r05.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207751 P-CR Approval 23.700-48: 23.700-48 KI #5, Sol #39: Update to clarify EAS relocation between operators CATT Rel-18 Revision of S2-2206432r05. Approved Approved
9.11 S2-2206457 P-CR Approval 23.700-48: Update of Solution#20 Sony Rel-18 Approved Dario (Qualcomm) asks to update solution description and impacts on UE
Svante (Sony) provide answers to questions
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2206878 P-CR Approval 23.700-48: KI#5: Sol. 22 update Qualcomm Incorporated, AT&T Rel-18 r04 agreed. Revised to S2-2207752. Xinpeng(Huawei) asks for clarification.
Magnus O (Ericsson) provides r01
Tangqing (China Mobile) asks for clarification.
Dario (Qualcomm) provides r03 (as r02 + co-signer)
Dario (Qualcomm) comments and provides r02 based on r01.
Xinpeng(Huawei) comments.
Dario (Qualcomm) replies to Xinpeng and provides r04.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207752 P-CR Approval 23.700-48: KI#5: Sol. 22 update Qualcomm Incorporated, AT&T Rel-18 Revision of S2-2206878r04. Approved Approved
9.11 - - - KI#5 - New solution - - Docs:=2 -
9.11 S2-2206302 P-CR Approval 23.700-48: KI#5, new Sol Access the shared EAS via N9 tunnel Vivo Rel-18 r03 agreed. Revised to S2-2207753. Dario (Qualcomm) comments that an update is needed.
Xinpeng(Huawei) strong concerns about N9 tunnel.
Huazhang (vivo) provides r01
Tingfang Tang (Lenovo) clarifies on r01
Xinpeng(Huawei) shares the same questions as Tingfang Tang (Lenovo).
Huazhang (vivo) provides R02 to reflect the concerns
Xinpeng(Huawei) replies to Huazhang (vivo).
Tingfang Tang (Lenovo) suggests to merge r02 into 6294(sol#40)
Huazhang (vivo) provides r03 and reply to Tingfang
==== 9.X, 10.X Revisions Deadline ====
Xinpeng(Huawei) is fine with r03 with title of 6.X changed into 'Discover the EAS deployed in another PLMN'.
Tingfang Tang (Lenovo) shares same view with Xinpeng(Huawei) 'is fine with r03 with title of 6.X changed into 'Discover the EAS deployed in another PLMN'.'
Huazhang (vivo) is ok to go ahead r03, and thanks Tingfang and Xinpeng.
And the title of 6.X will be changed into 'Discover the EAS deployed in another PLMN'.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207753 P-CR Approval 23.700-48: KI#5, new Sol Access the shared EAS via N9 tunnel Vivo Rel-18 Revision of S2-2206302r03. Approved Approved
9.11 - - - KI#6 - Solution updates - - Docs:=2 -
9.11 S2-2205624 P-CR Approval 23.700-48: KI #6, Sol #41: Solution update Ericsson Rel-18 Approved Patrice (Huawei) comments.
Magnus (Ericsson) provides answer
==== 9.X, 10.X Revisions Deadline ====
Patrice (Huawei) comments further.
==== 9.X, 10.X Final Deadline ====
Approved
9.11 S2-2205625 P-CR Approval 23.700-48: KI #6, Sol #47: Solution update Ericsson Rel-18 Approved Mike (InterDigital) comments
Sudeep (Apple) provides comments.
Magnus (Ericsson) provides comments
Patrice (Huawei) asks for clarification.
Sudeep (Apple) responds to Magnus (Ericsson).
Magnus (Ericsson) provides some answers
Patrice (Huawei) thanks Magnus for the clarification.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.11 - - - KI#7 - Solution update - - Docs:=1 -
9.11 S2-2206296 P-CR Approval 23.700-48: Solution update for Sol#50 China Mobile Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.11 - - - KI#7 - New solution - - Docs:=1 -
9.11 S2-2206304 P-CR Approval 23.700-48: KI#7, new sol for Obtain and maintain mapping table between IP address IP range with DNAI Vivo Rel-18 Noted Patrice (Huawei) comments, describes how this solution would be harmful to the system.
Huazhang (vivo) provides r01 and reply to Patrice (HW)
Patrice (Huawei) answers Huazhang.
==== 9.X, 10.X Revisions Deadline ====
Patrice (Huawei) is afraid he has to object the contribution, as it does not fit in the scope of KI#7.
==== 9.X, 10.X Final Deadline ====
Noted
9.11 - - - Evaluation / conclusions - - Docs:=0 -
9.11 - - - KI#1 - HR scenarioevaluation / conclusions - - Docs:=7 -
9.11 S2-2205746 P-CR Approval 23.700-48: KI #1: Solution evaluation and conclusions China Unicom Rel-18 Merged into S2-2207754 Patrice (Huawei, rapporteur) proposes to merge to 6848.
==== 9.X, 10.X Revisions Deadline ====
Tianqi (China Unicom) confirms the merge to 6848
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206225 P-CR Approval 23.700-48: KI#1 evaluation and conclusion for HR case Huawei, HiSilicon Rel-18 Merged into S2-2207754 Hui (Huawei) provides r01.
Tangqing (China Mobile) provides r02.
Tianqi (China Unicom) comments.
Patrice (Huawei, rapporteur) proposes to merge to 6848.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206292 P-CR Approval 23.700-48: Conclusion for KI#1 HR PDU session supporting access to V-EHE China Mobile Rel-18 Merged into S2-2207754 Patrice (Huawei, rapporteur) proposes to merge to 6848.
==== 9.X, 10.X Revisions Deadline ====
Dan (China Mobile) confirm the merge to 6848
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206426 P-CR Approval 23.700-48: 23.700-48 KI #1: Evaluation and conclusion for key issue #1 EAS discovery in HR roaming CATT Rel-18 Merged into S2-2207754 Patrice (Huawei, rapporteur) proposes to merge to 6848.
==== 9.X, 10.X Revisions Deadline ====
Yuan Tao (CATT) confirms this paper is merged into 6848.
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206427 P-CR Approval 23.700-48: 23.700-48 KI #1: Evaluation and conclusion for key issue #1 edge relocation in HR roaming CATT Rel-18 Merged into S2-2207754 Patrice (Huawei, rapporteur) proposes to merge to 6848.
==== 9.X, 10.X Revisions Deadline ====
Yuan Tao (CATT) confirms this paper is merged into 6848.
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206848 P-CR Approval 23.700-48: KI#1 Interim conclusion on scenario 2 Samsung Rel-18 CC#5: r16 + changes agreed. Revised to S2-2207754, merging S2-2205620, S2-2205746, S2-2206064, S2-2206225, S2-2206292, S2-2206426 and S2-2206427 Jicheol (Samsung) provides r01.
Patrice (Huawei, rapporteur) proposes to merge 5746, 6225, 6292, 6426, 6427 to this document, and continue the evaluation fo KI#1/HR in this thread.
Dan(China Mobile) provides r02 with an update for this conclusion part
Dario (Qualcomm) asks questions and comments.
Tianqi (China Unicom) provides r05 and ignores r04
Hui (Huawei) provides r06
Tianqi (China Unicom) provides r04.
Jicheol (Samsung) provides r03.
Dan (China Mobile) comments for r05
Tianqi (China Unicom) clarifies for r05.
Laurent (Nokia): provides r07
Yuan Tao (CATT) provides r08 .
Tianqi (China Unicom) provides r09.
Changhong (Intel) provides r10 to merge S2-2206064.
Magnus O (Ericsson) provides r11
Dan (China Mobile) provides r11
Huazhang (vivo) provides r13 based on r12
Hui (Huawei) provides r14
Laurent (Nokia): provides r15
Jicheol (Samsung) objects r14 and r15.
Hui (Huawei) comments.
Dario (Qualcomm) provides r16 (based on r13) and r17 (based on r10).
Jicheol (Samsung) replies to Hui that r10 is acceptable.
Laurent (Nokia): provides r18
Laurent (Nokia): Comments: the wisest thing to do may be to remove text about EASDF as proposed by Hui
Tianqi (China Unicom) objects r18.
==== 9.X, 10.X Revisions Deadline ====
Dan(China Mobile) object r10,r11,r14,r15, r17, r18, accept r12,r13,r16
Dan (China Mobile) sorry to correct the previous notes that china mobile provide r12 not r11.
Hui(Huawei) provides draft r19
Jicheol (Samsung) supports r16 and r17 and objects r14, 15 and r18.
Laurent (Nokia): objects to any version between R00 and R06 both included; Objects to R09, R10, R11, R12, R13, R16, R17
Thinks that a version to be approved should Not be too ambitious on EASDF procedures. let's agree on a baseline
Hui (Huawei) provides a suggestion.
Laurent (Nokia): provides r19v3 post deadline based on R18
Dan (China Mobile) share the view with Jicheol, I suggest we can use r16 as base to move forward.
Dario (Qualcomm) I can only accept r18, r17, r16 and r19v3
Patrice (Huawei, rapporteur) comments on the need to spell out in these captured comments the difference with r18 (for the so-called r19v3 shared after the deadline).
Hui (Huawei) can only accept r10, r17, r18 and r19v3, suggest to go with r19v3
Jicheol (Samsung) will object any revisions using r18 as a baseline since I explicitly shows the objection on r18 already.
Patrice (Huawei, rapporteur) describes 'r19v3' as proposed by Laurent (Nokia) for the sake of meeting notes and approval: removal of 'as described in #4' in bullet 4 ; note in bullet ' reads 'NOTE: Scenario 2.1 is optional because it requires the tight cooperation between the VPLMN and HPLMN' ; following text moved to an EN at the end of bullet '/ Editor's note:the following is FFS: The V-SMF sends the V-EASDF/Local DNS address to the H-SMF for the H-SMF to create PCO for the UE during PDU Session Establishment/Modification procedure, or. H-SMF sends H-DNS server IP address included in PCO to UE via V-SMF during PDU Session Establishment/modification procedure.
==== 9.X, 10.X Final Deadline ====
Magnus (Ericsson) provides 6848r19 v5, not ok with r19v4
Jicheol provides S2-2206848r19v6 (with harmonized version)
Jicheol provides S2-2206848r19v7 (with harmonized version) + Ericsson EN
Magnus (Ericsson) not ok with r19v6 or r19v7, ok with either if bullet 4 is deleted.
Tianqi (China Unicom) provides 6848r19v6, not ok with 6848r19v5 and 6848r19v4
Jicheol provide a way forward based on offline discussion with Magnus and Hui, it was agreed as follows:
Tianqi (China Unicom) provides 6848r19v8
Hui (Huawei) fine with the EN.
Magnus (Ericsson) not ok with r19v8 (ok if bullet 4 is deleted)
Jicheol is okay with EN.
Revised
9.11 S2-2207754 P-CR Approval 23.700-48: KI#1 Interim conclusion on scenario 2 Samsung Rel-18 Revision of S2-2206848r16 + changes, merging S2-2205620, S2-2205746, S2-2206064, S2-2206225, S2-2206292, S2-2206426 and S2-2206427. This P-CR was approved Approved
9.11 - - - KI#1 - LBO scenarioevaluation / conclusions - - Docs:=5 -
9.11 S2-2205905 P-CR Approval 23.700-48: KI #1, New Eval, Conclusion: Key Issue #1 Evaluation and Conclusion for LBO Scenarios InterDigital Inc. Rel-18 r10 + changes agreed. Revised to S2-2207755, merging S2-2206056, S2-2206226 and S2-2206877 Huazhang (vivo) comments and kick off the discussion of ECS address delivery
Mike (InterDigital) replies and provides r01 which is merge proposal for S2-2205905, S2-2206056, S2-2206226, S2-2206877, and S2-2205620
Changhong (Intel) comments.
Patrice (Huawei, rapporteur) comments.
Patrice (Huawei, rapporteur) answers.
Dario (Qualcomm) provides r02
Hui (Huawei) provides r03
Laurent (Nokia): provides r04
Changhong (Intel) is OK with r02 and r03, but not OK with r00 and r01.
Magnus O (Ericsson) provides r05
Mike (InterDigital) provides r06
Jicheol (Samsung) provides r07.
Huazhang (vivo) reply to Jicheol that the URL is linked to revision 6, not revision 7
Laurent (Nokia): provides r08
Mike (InterDigital) comments
Changhong (Intel) provides r09.
Dario (Qualcomm) comments and provides r10
Patrice (Huawei, rapporteur) kindly requests Changhong (Intel) to provide a short summary of his changes when he provides a revision.
==== 9.X, 10.X Revisions Deadline ====
Jicheol (Samsung) is fine with r10 and wants to co-sign this version.
Jicheol acks Huazhang (Vivo) that the url (link) of r07 was wrong by mistake.
Patrice (Huawei, rapporteur) comments on r10, its approval can only be conditional to an explicit statement in the UEPO KI#1 conclusion that it will fulfil the conclusion of KI#1/LBO of this study.
Laurent (Nokia): objects to R00, R01 R02 R03 R05 R06
Suggests that R10 (or any other agreed version) is discussed in CC5 together with UEPO conclusions
Patrice (Huawei) comments that, as mentioned in FS_UEPO in 5529 a statement there should be inserted: 'It is agreed that KI#1 of FS_UEPO will commit to fulfil the conclusion of KI#1/LBO of FS_EDGE_PH2.', to the version being approved.' If this statement is not included there, this contribution would need to be objected and discussed again at next meeting.
Patrice (Huawei, rapporteur) withdraws his previous comment based on the discussion in CC#4, and instead requests to add the following EN to r10: 'The agreement that the normative work for this KI#1/LBO will take place within the WID on FS_eUEPO depends on whether the conclusion for KI#1 UEPO fulfils the conclusion listed in this clause. If this is not the case, the normative work to fulfil this conclusion will have to take place within the WID for EDGE_Ph2.'. If not, the contribution should be postponed.
Mike (InterDigital) agrees with Patrice and proposed to agree to r10 + 'It is agreed that KI#1 of FS_UEPO will commit to fulfil the conclusion of KI#1/LBO of FS_EDGE_PH2.' on CC#5
Patrice (Huawei, rapporteur) replies to Mike (Interdigital).
Mike (InterDigital) replies to Patrice and is ok with Patrice's last proposal: r10 + an EN that reads 'The agreement that the normative work for this KI#1/LBO will take place within the WID on FS_eUEPO depends on whether the conclusion for KI#1 UEPO fulfils the conclusion listed in this clause. If this is not the case, the normative work to fulfil this conclusion will have to take place within the WID for EDGE_Ph2'.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207755 P-CR Approval 23.700-48: KI #1, New Eval, Conclusion: Key Issue #1 Evaluation and Conclusion for LBO Scenarios InterDigital Inc. Rel-18 Revision of S2-2205905r10 + changes, merging S2-2206056, S2-2206226 and S2-2206877. Approved Approved
9.11 S2-2206056 P-CR Approval 23.700-48: KI#1, Conclusion about URSP related solutions LG Electronics Rel-18 Merged into S2-2207755 LaeYoung (LGE) responds to Mike (InterDigital).
Mike (InterDigital) replies to LaeYoung (LGE)
LaeYoung (LGE) replies to Mike (InterDigital).
Mike (InterDigital) comments
Patrice (Huawei, rapporteur) comments.
Mike (InterDigital) replies to LaeYoung (LGE) and Patrice (Huawei)
Hui (Huawei) responds to LaeYoung.
LaeYoung (LGE) comments.
Changhong (Intel) shares same view with LaeYoung.
Patrice (Huawei, rapporteur) proposes to merge to 5905.
LaeYoung (LGE) is OK to merge this pCR to 5905 .
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206226 P-CR Approval 23.700-48: KI#1 evaluation and conclusion for LBO case Huawei, HiSilicon Rel-18 Merged into S2-2207755 Patrice (Huawei, rapporteur) proposes to merge to 5905.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206877 P-CR Approval 23.700-48: KI#1: LBO: Way forward Qualcomm Incorporated, Intel, Samsung Rel-18 Merged into S2-2207755 Mike (InterDigital) comments
Changhong (Intel) comments
Magnus (Ericsson) propose to use 6877 as the starting point
Patrice (Huawei, rapporteur) proposes to merge to 5905.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 - - - KI#1 - mixedevaluation / conclusions - - Docs:=4 -
9.11 S2-2205620 P-CR Approval 23.700-48: KI #1, Solution evaluation and conclusions Ericsson Rel-18 Merged into S2-2207754 Mike (InterDigital) comments
Patrice (Huawei, rapporteur) proposes to merge to 6848+5905.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206064 P-CR Approval 23.700-48: KI#1, Evaluation and Conclusion on Solution#24 Intel Rel-18 Merged into S2-2207754 Patrice (Huawei, rapporteur) proposes to merge to 6848+5905.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206300 P-CR Approval 23.700-48: KI#1, Evaluation and conlusion for ECS address delivery in roaming situation Vivo Rel-18 r02 agreed. Revised to S2-2207756. Patrice (Huawei, rapporteur) proposes to merge to 6848+5905.
Patrice (Huawei) discusses regarding handling of S2-2206300.
Dario (Qualcomm) asks questions for clarificationd and comments.
Huazhang (vivo) reply to Dario(QC) and provide r01
Dario (Qualcomm) provides r02
Huazhang (vivo) reply to Dario(QC), r02 is preferred.
==== 9.X, 10.X Revisions Deadline ====
Hui (Huawei) asks for clarification.
Jicheol (Samsung) proposed to merge this paper into S2-2206848.
Huazhang (vivo) reply to Hui(HW) that hope to keep 6300 alone and I can agree to remove the ECS address related words in 6848 provided by vivo
Huazhang (vivo) reply to Jicheol(Samsung) to keep the discussion of ECS address along, and the discussion in 6848 has many unclear issues, but the discussion in ECS address is stable
Huazhang (vivo) is ok to go with r02, and not ok to merge this paper to 6848, due to 6848 has some uncleared issues, and the ECS address part is stable
Patrice (Huawei) answers Jicheol (Samsung)'s question.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207756 P-CR Approval 23.700-48: KI#1, Evaluation and conlusion for ECS address delivery in roaming situation Vivo Rel-18 Revision of S2-2206300r02. Approved Approved
9.11 - - - KI#2 - Evaluation / conclusions - - Docs:=2 -
9.11 S2-2206228 P-CR Approval 23.700-48: KI#2 evaluation and conclusion Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2207757. Curt (Meta) thinks that exposing Cell ID is useful.
Magnus (Ericsson) proposes a way forward
Shubhranshu (Nokia) comments
Shubhranshu (Nokia) responds and provides r01
Hui (Huawei) replies to Magnus.
Hui (Huawei) responses to Curt.
Hui (Huawei) asks question to Shubhranshu.
Magnus (Ericsson) provides some comments
Curt (Meta) replies to Dario, provided R3
Dario (Qualcomm) comments and provides r02
Curt (Meta) provides a view w.r.t Hui's question to Shubhranshu.
Curt (Meta) relies to Hui
Magnus (Ericsson) provides more comments
Changhong (Intel) prefers to discuss the conclusion in this SID.
Magnus O (Ericsson) provides r04
Patrice (Huawei, rapporteur) comments, strong concerns regarding r04.
Shubhranshu (Nokia) supports comments & concerns on r04 from Patrice (Huawei)
Dario (Qualcomm) supports r04.
Hui (Huawei) provides r05.
Changhong (Intel) replies to Patrice.
Shubhranshu (Nokia) provides r06
==== 9.X, 10.X Revisions Deadline ====
Curt (Meta) suggests we go with r06.
Hui (Huawei) objects r06, and suggest to go with r05.
Magnus (Ericsson) objects to r06 and propose to go with r05 (or r04 ??)
Hui (Huawei) replies to Shubhranshu
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207757 P-CR Approval 23.700-48: KI#2 evaluation and conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206228r05. Approved Approved
9.11 - - - KI#3 - Evaluation / conclusions - - Docs:=2 -
9.11 S2-2205621 P-CR Approval 23.700-48: KI #3, Discussion and conclusion Ericsson Rel-18 Merged into S2-2205488 (noted). Noted Patrice (Huawei, rapporteur) proposes to merge to 5488.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2205488 P-CR Approval 23.700-48: Conclusions for KI#3: Policies for finer granular sets of UEs Nokia, Nokia Shanghai Bell Rel-18 Noted Patrice (Huawei, rapporteur) proposes to merge 5621 into this document.
Laurent (Nokia): Comments trying to understand where we are
Tingfang Tang (Lenovo) comments and provides r01
Magnus H (Ericsson) provides r02
Xinpeng(Huawei) comments
Magnus H (Ericsson) comments
Xinpeng(Huawei) further comments.
Xinpeng(Huawei) asks for clarification.
Tingfang Tang (Lenovo) asks for clarification from Magnus H (Ericsson)
Tingfang Tang (Lenovo) provides r03
Magnus H (Ericsson) cannot agree to r03
Tingfang Tang (Lenovo) replies to Magnus H (Ericsson)
Laurent (Nokia): provides r04 and r05
Tingfang Tang (Lenovo) provides r06, r07 and r08
==== 9.X, 10.X Revisions Deadline ====
Xinpeng(Huawei) replies to Magnus H (Ericsson), Laurent (Nokia).
Xinpeng(Huawei) can only accept r00, r04, r05, r07, r08. and objects to any other revisions.
Tingfang Tang (Lenovo) objects r00 and r02, can accepts all other revisions.
Laurent (Nokia): can only accept r00, R01, r04, r05, r07, r08 and objects to any other revisions.
Magnus H (Ericsson) prefers r02 or r06 can live with r03 and objects to r00, r01, r04, r05, 07, 08
Xinpeng(Huawei) concerns that r02, r06 are based on solution that have never been proposed, it is NOT the way for making evaluatioin/conclusion.
Magnus H (Ericsson) comments that also r00, r01, r04, r05, r07, r08 also have solutions not discussed. All of these revisions also make wrong evaluation with regards to number of affected records in UDR if using group id.
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Tingfang Tang (Lenovo) asks clarification to Magnus H (Ericsson) and Xinpeng(Huawei).
==== 9.X, 10.X Final Deadline ====
Noted
9.11 - - - KI#4 - Evaluation / conclusions - - Docs:=5 -
9.11 S2-2205687 P-CR Approval 23.700-48: KI#4 Evaluation NTT DOCOMO Rel-18 Merged into S2-2207758 Tingfang Tang (Lenovo) comment.
Patrice (Huawei, rapporteur) proposes to merge to 6739.
Tugce (NTT DOCOMO) agrees to merge.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206144 P-CR Approval 23.700-48: KI#4 evaluation and conclusion Huawei, HiSilicon Rel-18 Merged into S2-2207758 Tingfang Tang (Lenovo) comments.
Huazhang (vivo) provide the comments that the 5GC behaviour to support same EAS/DNAI should be determined first
Yuan Tao (CATT) provides r02.
Xinpeng(Huawei) provides r03.
Tingfang Tang (Lenovo) replies and clarifies to Yuan and Huazhang.
Tugce (NTT DOCOMO) comments.
Xinpeng(Huawei) replies to Tugce (NTT DOCOMO).
Yuan Tao (CATT) replies to Tingfang Tang (Lenovo).
Tugce (NTT DOCOMO) provides r04.
Tingfang Tang (Lenovo) replies to Yuan Tao (CATT).
Xinpeng(Huawei) agrees to merge 6144 to 6739.
Patrice (Huawei, rapporteur) proposes to merge to 6739.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206429 P-CR Approval 23.700-48: 23.700-48 KI #4: Evaluation and conclusion for key issue #4 Influencing UPF and EAS (re)location for collections of Ues CATT, vivo Rel-18 Merged into S2-2207758 Xinpeng(Huawei) suggests 6429 merged into 6144.
Xinpeng(Huawei) withdraw the previous suggestion, and suggest 6429 merged into 6739.
==== 9.X, 10.X Revisions Deadline ====
Yuan Tao (CATT) confirms this paper is merged into 6739.
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206739 P-CR Approval 23.700-48: Conclusions for KI#4: KI#4: Influencing UPF and EAS (re)location for collections of Ues Lenovo Rel-18 r22 + changes agreed. Revised to S2-2207758, merging S2-2205687, S2-2206144 and S2-2206429 Xinpeng(Huawei) suggests merging 6739 into 6144.
Xinpeng(Huawei) withdraw previous comment, and agree 6144 is merged into 6739
Tingfang Tang (Lenovo) moves 6144r04 into 6739r02
Xinpeng(Huawei) provides r01.
Xinpeng(Huawei) provides r03 based on r02.
Tugce (NTT DOCOMO) comments.
Shubhranshu (Nokia) comments
Shubhranshu (Nokia) provides r04
Huazhang (vivo) provides r05 based on r04
Magnus H (Ericsson) provides r06
Shubhranshu (Nokia) asks for clarification
Tingfang Tang (Lenovo) comments and asks for clarification.
Xinpeng(Huawei) provides r07.
Tingfang Tang (Lenovo) provides r09.
Xinpeng(Huawei) provides r10.
Yuan Tao (CATT) provides r11.
Tugce (NTT DOCOMO) provides r13.
Tingfang Tang (Lenovo) provides r12.
Tingfang Tang (Lenovo) provides r14.
Xinpeng(Huawei) provides r15.
Xinpeng(Huawei) replies to Tugce (NTT DOCOMO) and objects to r13, r14, r09.
Magnus H (Ericsson) provides r17 and withdraws r16 and comments.
Tugce (NTT DOCOMO) asks Xinpeng(Huawei) for clarification and objects to r15.
Xinpeng(Huawei) provides r18, objects to r17.
Tugce (NTT DOCOMO) provides r19 and comments to Xinpeng(Huawei).
Magnus H (Ericsson) comments
Xinpeng(Huawei) provides r20.
Tingfang Tang (Lenovo) comments on the considering the common DNAI/EAS selection on behalf 5GC.
Xinpeng(Huawei) comments.
Tingfang Tang (Lenovo) replies to Xinpeng(Huawei) and provides r21.
Shubhranshu (Nokia) provides r22
==== 9.X, 10.X Revisions Deadline ====
Tingfang Tang (Lenovo) clarifies the changes on r22 to Shubhranshu (Nokia).
Shubhranshu (Nokia) responds
Tingfang Tang (Lenovo) replies to Shubhranshu(Nokia).
Xinpeng(Huawei) can only accept r01,r03,r07,r10,r11,r12,r15,r18, r20,r21, and r22 with 'PSA UPF' removed from conclusion part; objects to any other revisions.
Tugce (NTT DOCOMO) finds r22 ok by removing 'The SMF may identify whether the UE belongs to UE collection and decides the common DNAI/EAS/PSA UPF for the UE collection.'
Magnus H (Ericsson) are OK r22 and the proposed changes by Xinpeng and Tugce
Huazhang (vivo) are OK with r22 and the proposed changes by Xinpeng and Tugce
Yuan Tao (CATT) accepts r22 with the proposed changes.
Tingfang Tang (Lenovo) is OK with proposal from Xinpeng and Tugce, which is r22+ removing 'The SMF may identify whether the UE belongs to UE collection and decides the common DNAI/EAS/PSA UPF for the UE collection.'
Shubhranshu (Nokia) agrees r22 + removing 'The SMF may identify whether the UE belongs to UE collection and decides the common DNAI/EAS/PSA UPF for the UE collection.'
Xinpeng(Huawei) agrees r22+ removing 'The SMF may identify whether the UE belongs to UE collection and decides the common DNAI/EAS/PSA UPF for the UE collection.'
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207758 P-CR Approval 23.700-48: Conclusions for KI#4: KI#4: Influencing UPF and EAS (re)location for collections of Ues Lenovo Rel-18 Revision of S2-2206739r22 + changes, merging S2-2205687, S2-2206144 and S2-2206429. Approved Approved
9.11 - - - KI#5 - Evaluation / conclusions - - Docs:=4 -
9.11 S2-2206143 P-CR Approval 23.700-48: KI#5 conclusion for EAS discovery of edge node sharing Huawei, HiSilicon Rel-18 Merged into S2-2207759 Magnus O (Ericsson) provides r01 and propose to take 6143 as the base for the conclusion of KI#5
Huazhang (vivo) ask questions
Tangqing (China Mobile) ask for clarification.
Xinpeng(Huawei) confirms 6143 is merged into 6879.
Xinpeng(Huawei) replies to Tangqing (China Mobile).
Patrice (Huawei, rapporteur) proposes to merge to 6879.
Xinpeng(Huawei) replies to Huazhang (vivo).
Xinpeng(Huawei) replies that there is no conflicting with GSMA requirements.
Dario (Qualcomm) comments that conclusion 2 is against GSMA OPG topology hiding requirement.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206431 P-CR Approval 23.700-48: 23.700-48 KI #5: Evaluation and conclusion for key issue #5 EAS discovery and relocation for shared EHE CATT Rel-18 Merged into S2-2207759 Patrice (Huawei, rapporteur) proposes to merge to 6879.
==== 9.X, 10.X Revisions Deadline ====
Yuan Tao (CATT) confirms this paper is merged into 6879.
==== 9.X, 10.X Final Deadline ====
Merged
9.11 S2-2206879 P-CR Approval 23.700-48: KI#5: Evaluation and conclusions Qualcomm Incorporated, AT&T Rel-18 r14 + changes agreed. Revised to S2-2207759, merging S2-2206143 and S2-2206431 Tangqing (China Mobile) provides r01.
Patrice (Huawei, rapporteur) proposes to merge 6143+6431 into this document.
Xinpeng(Huawei) provides r04.
Dan(China Mobile) comments and provides r03
Dario (Qualcomm) comments and provides r02
Yuan Tao (CATT) merges S2-2206431 into this paper per rapporteur's suggestion and provides r05.
Shubhranshu (Nokia) provides r06
Magnus O (Ericsson) provides r07
Xinpeng(Huawei) provides r08.
Xinpeng(Huawei) provides r09.
Tingfang Tang (Lenovo) comments and provides r10.
Dan(China Mobile) comments and provides r11.
Xinpeng(Huawei) replies to Dan(China Mobile).
Magnus O (Ericsson) provides r12
Xinpeng(Huawei) is fine with r12.
Shubhranshu (Nokia) provides r13, objects to r11, r12
Xinpeng(Huawei) provides r14.
Dario (Qualcomm) provides r15.
==== 9.X, 10.X Revisions Deadline ====
Xinpeng(Huawei) only accepts r04, r05, r08, r09, r12, r14 and objects to any other revisions.
Dan(China Mobile) accepts r14 and objects 15.
Tingfang Tang (Lenovo) accepts r10, r12, r14, objects others, and asks clarification to Dario (Qualcomm).
Dario (Qualcomm) is OK w/r14 with the following changes: 1) add 'in line with the GSMA OPG requirement of topology hiding' to 1st EN under 'EAS Deployment Provision'; 2) Add 'and/or whether extensions to the methods are needed' to 1st EN under 'EAS Discovery Procedure'.
Xinpeng(Huawei) is fine with r14 with the following changes: 1) add 'in line with the GSMA OPG requirement of topology hiding' to 1st EN under 'EAS Deployment Provision'; 2) Add 'and/or whether extensions to the methods are needed' to 1st EN under 'EAS Discovery Procedure'.
Tingfang Tang (Lenovo) is OK with Dario's proposal to go with r14 with related update.
Magnus (Ericsson) is also ok with the amended r14
Yuan Tao (CATT) is ok with r14 with changes.
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207759 P-CR Approval 23.700-48: KI#5: Evaluation and conclusions Qualcomm Incorporated, AT&T Rel-18 Revision of S2-2206879r14 + changes, merging S2-2206143 and S2-2206431. Approved Approved
9.11 - - - KI#6 - Evaluation / conclusions - - Docs:=4 -
9.11 S2-2205626 P-CR Approval 23.700-48: KI #6, Solution evaluation and conclusions Ericsson Rel-18 Noted Mike (InterDigital) comments
Huazhang (vivo) comments
Magnus O (Ericsson) provides r01
Patrice (Huawei, rapporteur) proposes to merge 5906/6303/6697 into this document.
Yang (OPPO) provides comments and share the same view with vivo
Dario (Qualcomm) asks questions for clarification.
Huazhang (vivo) reply to Magnus(///) that the vivo has concerns of the enhancement in both URSP rules and ePCO
Changhong (Intel) comments and prefers to use PCO based solution.
Sudeep (Apple) provides r02.
Huazhang (vivo) provides r03 to make a way forward, that this meeting we focus on evaluation, and don't have conclusion part
Shubhranshu (Nokia) comments
Magnus O (Ericsson) provides r04
Huazhang (vivo) is not ok with r04,
Huazhang can only ok with r03, and Huazhang can accept the suggestion from Nokia to let the conclusion part empty
Magnus (Ericsson) asks for feedback
Sudeep (Apple) provides comments on r04.
Huazhang (vivo) reply to Magnus (E///)
Magnus O (Ericsson) provides r05
Mike (InterDigital) objects to r03 and is ok with r04 and r05
Patrice (Huawei) comments, ok with r05.
Sudeep (Apple) has follow-up questions to Magnus O's (Ericsson) comments in r04 and r05.
Shubhranshu (Nokia) provides r06, objects to r04, r05
Yang (OPPO) object r02, r04, r05 and can only live with r03
Magnus (Ericsson) provides soma answers
Magnus (Ericsson) ok with r04, r05 and r06, not ok with r03
Dario (Qualcomm) provides r07
==== 9.X, 10.X Revisions Deadline ====
Mike (InterDigital) objects to r07 and can live with r04, r05, and r06.
Mike (InterDigital) objects to r03 and r07. Is ok with r00, r01, r02, r04, r05, and r06.
Dario (Qualcomm) can only accept r03.
Sudeep (Apple) can accept only r02.
Huazhang (vivo) can only accept r03, r07, and object any other versions
Huazhang (vivo) can't accept that we didn't have any technique discussion and directly writes the conclusion, and also can't accept in evaluation part, we only has the pros of solution but no cons or concerns of KI and solution.
Shubhranshu (Nokia) objects r07
Magnus (Ericsson) comments
Magnus (Ericsson) answers Huazhang
Patrice (Huawei, rapporteur) comments, likely this contribution will have to be postponed, will likely be resolved with SoH at next meeting.
Huazhang (vivo) thanks to Magnus (E///) and agree to have more discussion offline
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2205906 P-CR Approval 23.700-48: KI #6, New Eval, Conclusion: Key Issue #6 Evaluation and Conclusion InterDigital Inc. Rel-18 Noted Patrice (Huawei, rapporteur) proposes to merge to 5626.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2206303 P-CR Approval 23.700-48: KI#6, Evaluation and conlusion for keeping EC traffic on 5GS Vivo, OPPO Rel-18 Noted Mike (InterDigital) comments
Huazhang (vivo) reply to Mike(InterDigital)
Mike (InterDigital) replies to Huazhang (vivo)
Patrice (Huawei, rapporteur) proposes to merge to 5626.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.11 S2-2206697 P-CR Approval 23.700-48: Evaluation of Key Issue #6 Apple Rel-18 Noted Patrice (Huawei, rapporteur) proposes to merge to 5626.
==== 9.X, 10.X Revisions Deadline ====
Sudeep (Apple) confirms this Tdoc is to be considered merged to S2-2205626.
==== 9.X, 10.X Final Deadline ====
Noted
9.11 - - - KI#7 - Evaluation / conclusions - - Docs:=3 -
9.11 S2-2206229 P-CR Approval 23.700-48: KI#7 evaluation and conclusion Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2207760, merging and S2-2206297 Dan (China Mobile) provide r01 with merging S2-2206297 into this paper
Huazhang (vivo) have a comment
Huazhang (vivo) provides r02
Tingfang Tang (Lenovo) asks for clarification
Patrice (Huawei) answers Huazhang, supports r01, objects to r02.
Patrice (Huawei) answers Tingfang (Lenovo).
Tingfang Tang (Lenovo) replies to Patrice (Huawei)
Shubhranshu (Nokia) comments
Huazhang (vivo) reply to Shubhranshu (Nokia)
Huazhang (vivo) reply to Patrice(HW) that the r01 is not ok and not clear to me
Shubhranshu (Nokia) asks for clarification
Patrice (Huawei) answers.
Patrice (Huawei) replies to Huazhang (Vivo).
Magnus H (Ericsson) provides r03 based on r01
Patrice (Huawei) is OK with r03.
Huazhang (vivo) reply to Patrice (HW)
==== 9.X, 10.X Revisions Deadline ====
Magnus H (Ericsson) can only accept r03 objects to all other version
==== 9.X, 10.X Final Deadline ====
Revised
9.11 S2-2207760 P-CR Approval 23.700-48: KI#7 evaluation and conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206229r03, merging and S2-2206297. Approved Approved
9.11 S2-2206297 P-CR Approval 23.700-48: Solution evaluation and conclusion for KI#7 China Mobile Rel-18 Merged into S2-2207760 Dan (China Mobile) this paper has been merged into S2-2206229
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.11 - - - Documents exceeding TU Budget - - Docs:=6 -
9.11 S2-2206844 P-CR Approval 23.700-48: KI#1, Sol#24 Update Samsung Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.11 S2-2205679 P-CR Approval 23.700-48: Update to support EAS discovery with dynamic setup of a LBO PDU Session LG Electronics Deutschland Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.11 S2-2206430 P-CR Approval 23.700-48: 23.700-48 KI #4, Sol #18: Update to remove ENs CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.11 S2-2205623 P-CR Approval 23.700-48: KI #5, Sol #22: Update misleading terminology Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.11 S2-2206842 P-CR Approval 23.700-48: KI#1, Sol #39 Update to classify the key issue Samsung Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.11 S2-2206840 P-CR Approval 23.700-48: KI#1 Evaluation on scenario 2 Samsung Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.12 - - - Study on 5G System with Satellite Backhaul (FS_5GSATB) - - Docs:=21 -
9.12 - - - New solution - - Docs:=1 -
9.12 S2-2206293 P-CR Approval 23.700-27: KI#1, New Sol: NAS timer set identifier NTT DOCOMO Rel-18 Noted Hucheng (CATT) provides comments.
Haris(Qualcomm) objects to the pCR since the specific SID has been approved with no ME impacts
Atsushi (NTT DOCOMO) is fine to Note this pCR.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.12 - - - Solution update - - Docs:=10 -
9.12 S2-2205565 P-CR Approval 23.700-27: KI#2: Update to Solution#8 to support AF indication of in-sequence delivery China Telecom, Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207092. Heng (China Telecom) provide r01 to change the title from KI#2 to KI#1.
Heng (China Telecom) upload r01.
Relja (TNO) is fine with the proposed in r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207092 P-CR Approval 23.700-27: KI#2: Update to Solution#8 to support AF indication of in-sequence delivery China Telecom, Huawei, HiSilicon Rel-18 Revision of S2-2205565r01. Approved Approved
9.12 S2-2206220 P-CR Approval 23.700-27: KI#2 and #3, Sol#4 update to clarify on-board ULCL/BP UPF selection Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207093. Stefan (Ericsson) provides questions
Hui (Huawei) replies to Stefan and provides r01.
Relja (TNO) provides questions.
Hui (Huawei) replies to Relja.
Hui (Huawei) corrects the previous comment. r02 was provided.
Hui (Huawei) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207093 P-CR Approval 23.700-27: KI#2 and #3, Sol#4 update to clarify on-board ULCL/BP UPF selection Huawei, HiSilicon Rel-18 Revision of S2-2206220r02. Approved Approved
9.12 S2-2206221 P-CR Approval 23.700-27: KI#2 and #3, Sol#6 update to clarify on-board PSA UPF selection Huawei, HiSilicon Rel-18 Approved Relja (TNO) provides questions
Hui (Huawei) replies to Relja.
Hui (Huawei) replies to Stefan.
Stefan (Ericsson) provides r01 and replies to Hui
Hucheng (CATT) clarifies the WP and comments.
Hui (Huawei) proposes to go with r0.
Hui (Huawei) replies to Hucheng.
Stefan (Ericsson) OK to go with r00, as discussed
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.12 S2-2206504 P-CR Approval 23.700-27: KI#1, Solution#3, Update solution#3 to remove the EN Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.12 S2-2206720 P-CR Approval 23.700-27: KI#1, Update for solution#2 to supplement solution CATT Rel-18 r02 agreed. Revised to S2-2207094. Stefan (Ericsson) provides comments
Hucheng (CATT) replies to Stefan (Ericsson), and provides r01.
Stefan (Ericsson) replies
Hucheng replies to Stefan (Ericsson).
Stefan (Ericsson) provides r02
Hucheng (CATT) is OK with r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207094 P-CR Approval 23.700-27: KI#1, Update for solution#2 to supplement solution CATT Rel-18 Revision of S2-2206720r02. Approved Approved
9.12 S2-2206721 P-CR Approval 23.700-27: KI#3, Update for solution#7 to modify the I-UPF CATT Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.12 S2-2206922 P-CR Approval 23.700-27: KI#1, Solution #9 Update: QoS Monitoring for dynamic satellite backhaul delay control Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.12 - - - Evaluation and conclusion - - Docs:=12 -
9.12 - - - KI#1 - - Docs:=4 -
9.12 S2-2206503 P-CR Approval 23.700-27: Evaluation of solutions for KI#1 Huawei, HiSilicon Rel-18 Merged into S2-2207095 Guanglei (Huawei) confirms this pCR merged to 6722
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.12 S2-2206575 P-CR Approval 23.700-27: KI#1 solution evaluation and initial conclusions Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207095 Guanglei (Huawei) proposes to merge into 6722
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.12 S2-2206722 P-CR Approval 23.700-27: KI#1: Evaluation and conclusion CATT Rel-18 r11 agreed. Revised to S2-2207095, merging S2-2206503 and S2-2206575 Stefan (Ericsson) provides r01 and r02 (please ignore r01)
Hannu (Nokia) provides r03 and comments.
Hannu (Nokia) proposes to work on S2-2206722 for KI#1 and to note S2-2206503 and S2-2206575 but accepting that agreeable updates of those can be used for this document.
Guanglei (Huawei) provides r04, objects r02 and r03.
Hucheng (CATT) comments, and proposes to merge S2-2206503, S2-2206575 into this paper.
DongYeon (Samsung) provides r05, and comments.
Stefan (Ericsson) provides r06
Heng (China Telecom) comment to Stefan
Guanglei (Huawei) thanks Heng (China Telecom) supporting, provides r07 based on r06
Hannu (Nokia) cannot agree any of the revisions r04 - r07 due to incorrect evaluation of solution #8, specific handling of polar orbit and the PCF handling of out-of-sequence packets.
Stefan (Ericsson) provides comments
Relja (TNO) is fine with r08.
Guanglei (Huawei) provides r09, objects r08
Hucheng (CATT) supports Relja(TNO) to partially conclude KI#1, and proposes r10 to remove out-of-order related eveluation and conclusion for further discussion.
DongYeon (Samsung) comments.
Heng(China Telecom) add a Note in r11.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207095 P-CR Approval 23.700-27: KI#1: Evaluation and conclusion CATT Rel-18 Revision of S2-2206722r11, merging S2-2206503 and S2-2206575. Approved Approved
9.12 - - - KI#2 - - Docs:=3 -
9.12 S2-2206222 P-CR Approval 23.700-27: KI#2 evaluation and conclusion Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207096, merging and S2-2206723 Hucheng (CATT) proposes to use this paper as the baseline to make the conclusion.
Stefan (Ericsson) provides comments
Hui (Huawei) replies to Stefan.
Hucheng (CATT) provides comments.
Hui (Huawei) replies to Hucheng.
Hui (Huawei) provides r01.
Hannu (Nokia) asks for clarification on the suggested URSP configuration?
Haris(Qualcomm) asks question for clarification
Stefan (Ericsson) proposes to more clearly capture the standards impacts in the conclusion
Hui (Huawei) replies to Hannu.
Hui(Huawei) replies to Haris
Hui (Huawei) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207096 P-CR Approval 23.700-27: KI#2 evaluation and conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206222r02, merging and S2-2206723. Approved Approved
9.12 S2-2206723 P-CR Approval 23.700-27: KI#2: Evaluation and conclusion CATT Rel-18 Merged into S2-2207096 Stefan (Ericsson) proposes to merge 6723 into 6222
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.12 - - - KI#3 - - Docs:=3 -
9.12 S2-2206223 P-CR Approval 23.700-27: KI#3 evaluation and conclusion Huawei, HiSilicon Rel-18 Merged into S2-2207097 Hui(Huawei) confirmed the paper has been merged into S2-2206724 as proposed by Rapporteur.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.12 S2-2206724 P-CR Approval 23.700-27: KI#3: Evaluation and conclusion CATT Rel-18 r04 agreed. Revised to S2-2207097, merging and S2-2206223 Hucheng (CATT) proposes to merge S2-2206223 into this paper to capture the conclusions.
Hui (Huawei) provides r02.
Hucheng (CATT) provides r01.
Hannu (Nokia) comments.
Stefan (Ericsson) provides question
Stefan (Ericsson) provides r03
Hucheng(CATT) replies to Stefan (Ericsson).
Stefan (Ericsson) provides r04
Hucheng (CATT) can live with r04.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.12 S2-2207097 P-CR Approval 23.700-27: KI#3: Evaluation and conclusion CATT Rel-18 Revision of S2-2206724r04, merging and S2-2206223. Approved Approved
9.13 - - - Study on the support for 5WWC Phase 3 (FS_5WWC_Ph3) - - Docs:=32 -
9.13 - - - General papers - - Docs:=3 -
9.13 S2-2205476 LS OUT Approval [DRAFT] LS on solutions for 5WWC_Ph2 Key Issue 1 Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2207761. Stefan (Ericsson) provides r01
Huan (vivo) provides r03
Heng(China Telecom) provides r04
Sriram(CableLabs) provides r05
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207761 LS OUT Approval [DRAFT] LS on solutions for 5WWC_Ph2 Key Issue 1 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205476r05. Approved Approved
9.13 S2-2205475 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-17 to TSG SA#97 Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2207863.
==== 9.X, 10.X Final Deadline ====
Revised
9.13 - - - Updates to KI2 solutions - - Docs:=9 -
9.13 S2-2205477 P-CR Approval 23.700-17: Update to solution 13 Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.13 S2-2205478 P-CR Approval 23.700-17: Update to solution 12 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207762, merging and S2-2206741 Myungjune (LGE) provides comments.
Stefan (Ericsson) provides questions
Laurent (Nokia): answers and provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207762 P-CR Approval 23.700-17: Update to solution 12 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205478r01, merging and S2-2206741. Approved Approved
9.13 S2-2206741 P-CR Approval 23.700-17: Update of Solution 12 Lenovo Rel-18 Merged into S2-2207762 Laurent (Nokia): asks whether it is ok to merge 6741 in 5478
Apostolis (Lenovo) is fine to merge 6741 into 5748 but only if his request in bullet 3 is fulfilled.
Apostolis (Lenovo) asks question for clarification.
Laurent (Nokia): answers
marco (huawei) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.13 S2-2205515 P-CR Approval 23.700-17: KI#2: Merging solutions 15 and 16 Qualcomm, China Telecom Rel-18 r05 agreed. Revised to S2-2207763, merging and S2-2206169 Laurent (Nokia): provides r01
Laurent (Nokia): Comments: BTW would it be possible to merge 5515 with 6169 and 6170 (they all touch solution 15)
Heng (China Telecom) comment on r01.
Sebastian (Qualcomm) provides r02
Myungjune (LGE) comment on r02.
Marco (Huawei) object r00 and propose r01
Ashok (Samsung) agrees with Myungjune (LGE) and seeks clarification
Sebastian (Qualcomm) replies to Ashok
Sebastian (Qualcomm) replies and provides r03
Ashok (Samsung) clarifies to Sebastian (Qualcomm)
Marco (Huawei) ASKs to ignore previous comment 'object r00 and propose r01'
Sebastian (Qualcomm) provides r04
Laurent (Nokia): provides r05
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): can only live with r05; objects to any other version
Marco (Huawei): object r00, and ok with r04 and r05
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207763 P-CR Approval 23.700-17: KI#2: Merging solutions 15 and 16 Qualcomm, China Telecom Rel-18 Revision of S2-2205515r05, merging and S2-2206169. Approved Approved
9.13 S2-2206169 P-CR Approval 23.700-17: KI#2, Update Solution #15 on selecting N3IWF supporting the S-NSSAI needed by UE Huawei, HiSilicon Rel-18 Merged into S2-2207763 Laurent (Nokia): BTW would it be possible to merge 5515 with 6169 and 6170 (they all touch solution 15)+ need to update impacts
Sebastian (Qualcomm) replies that he will work with Marco to merge 5515 and 6169
Yishan (Huawei) provides r01 to merge the changes from 5515
Marco (Huawei): consider it merged into 5515
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.13 S2-2206170 P-CR Approval 23.700-17: KI#2, Update Solution #15 to add TNGF selection Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207764. Laurent (Nokia): Question. Tdoc update required
Sebastian (Qualcomm) suggests to document the TNGF aspects as a separate solution
Yishan (Huawei) suggests to keep 6170 independent of 5515 and 6169 since they are targeting to different scenarios.
Marco (Huawei) provides r01 implementing Sebastian (Qualcomm) suggestion
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207764 P-CR Approval 23.700-17: KI#2, Update Solution #15 to add TNGF selection Huawei, HiSilicon Rel-18 Revision of S2-2206170r01. Approved Approved
9.13 - - - SA2 Conclusion for KI 2 - - Docs:=2 -
9.13 S2-2205480 P-CR Approval 23.700-17: Conclusions to KI 2: baseline Nokia, Nokia Shanghai Bell Rel-18 r08 agreed. Revised to S2-2207765. Laurent (Nokia): provides r01
Ashok (Samsung) comments
Marco (Huawei) asks clarification on 'learning' approach
Heng (China Telcom) comment
Sebastian (Qualcomm) suggests to request a separate tdoc number to have two different papers for the N3IWF and TNGF conclusions
Laurent (Nokia): answers
Sebastian (Qualcomm) provides r02
Myungjune (LGE) supports r02 and provides r03 for cosign.
Heng (China Telecom) support to split the N3IWF and TNGF aspects into separate papers
Marco (huawei) proposes r04 . I agree to have in different paper, but a number must be asked.
Marco (Huawei) comment to Laurent (Nokia)
Stefan (Ericsson) provides r05
Heng (China Telecom) provides r06
Laurent (Nokia): provides r07
Sebastian (Qualcomm) provides r08
Marco (Huawei) have problem with version from r00 to r07, while r08 might be ok.
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R00 (empty), R01 (wrong Tdoc reference) . Concerns/objects to any version between R02 and R06 both included. R07/R08 are the way to go
Marco (Huawei) objects r00-r07 and I can live with r08
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207765 P-CR Approval 23.700-17: Conclusions to KI 2: baseline Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205480r08. Approved Approved
9.13 - - - Updates to KI1 solutions - - Docs:=11 -
9.13 S2-2206611 P-CR Approval 23.700-17: KI#1: Update to Solution #4 Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.13 S2-2206213 P-CR Approval 23.700-17: KI#1:Sol #20: update to resolve the ENs China Telecom Rel-18 r01 agreed. Revised to S2-2207766. Marco (Huawei) asks clarifications
Jing (China Telecom) provides r01 and reply to Marco (Huawei).
Stefan (Ericsson) provides questions
Jing (China Telecom) answers to Stefan (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207766 P-CR Approval 23.700-17: KI#1:Sol #20: update to resolve the ENs China Telecom Rel-18 Revision of S2-2206213r01. Approved Approved
9.13 S2-2206405 P-CR Approval 23.700-17: Update to Solution#6 on FS_5WWC_Ph2 China Telecom Rel-18 r01 agreed. Revised to S2-2207767. Stefan (Ericsson) provides comments
Yubing (China Telecom) replies to Stefan (Ericsson)
Yubing (China Telecom) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207767 P-CR Approval 23.700-17: Update to Solution#6 on FS_5WWC_Ph2 China Telecom Rel-18 Revision of S2-2206405r01. Approved Approved
9.13 S2-2206808 P-CR Approval 23.700-17: KI#1: 802.11e s user priority mapping with 5G QoS Meta USA Rel-18 Noted Heng (China Telecom) ask for clarification and provide comment.
Curt (Meta) replies to Heng (China Telecom) and provided r2.
Marco (Huawei) object r00 and propose r01
Marco (Huawei) reply to Curt (Meta) and disagree with r02
Curt (Meta) object r01 and propose r03.
Marco (Huawei) is ok with r03.
==== 9.X, 10.X Revisions Deadline ====
Sebastian (Qualcomm) objects to the pCR (all versions)
Curt (Meta) wants to say to Sebastian (Qualcomm), as a general observation, that objecting to a paper at last minute without prior discussion is just very unprofessional.
Sriram(CableLabs) comments and supports r03.
Yildirim (Charter) supports r03.
Sebastian (Qualcomm) replies to Curt (Meta)
Paul R (Charter) supports r03.
==== 9.X, 10.X Final Deadline ====
Noted
9.13 S2-2205852 P-CR Approval 23.700-17: KI#1, Sol#1: Update of solution to resolve ENs Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.13 S2-2205854 P-CR Approval 23.700-17: KI#1, Sol#21: Update of solution to resolve ENs Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.13 S2-2206168 P-CR Approval 23.700-17: KI#1, update Sol#2 to support uplink QoS differentiation Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207769. Stefan (Ericsson) provides comments
Yishan (Huawei) answers to Stefan (Ericsson) and provides r01
Heng (China Telecom) comment
Yishan (Huawei) answers to Heng (China Telecom)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.13 S2-2207769 P-CR Approval 23.700-17: KI#1, update Sol#2 to support uplink QoS differentiation Huawei, HiSilicon Rel-18 Revision of S2-2206168r01. Approved Approved
9.13 S2-2206685 P-CR Approval 23.700-17: KI#1 Sol#5 Revision Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.13 - - - Company views on Conclusion for KI 2 or Documents exceeding TU Budget - - Docs:=7 -
9.13 S2-2205479 P-CR Approval 23.700-17: Conclusions to KI 2: Nokia views Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2205567 P-CR Approval 23.700-17: KI#2: Evaluation and conclusion on TNGF selection China Telecom, Qualcomm, Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2206171 DISCUSSION Discussion KI#2, Discussion on conclusion on KI#2 about N3IWF selection Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2205516 P-CR Approval 23.700-17: Partial conclusion for key issue 2: How to select an N3IWF that supports the S-NSSAI(s) needed by the UE Qualcomm Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2206743 P-CR Approval 23.700-17: Conclusions about the types of solutions for KI#2 Lenovo, Broadcom Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2205853 P-CR Approval 23.700-17: KI#1, Sol#2: Update of solution to resolve ENs Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.13 S2-2206686 P-CR Approval 23.700-17: KI#1 Sol#9 Revision Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 - - - Study on Network Slicing Phase 3 (FS_eNS_Ph3) - - Docs:=93 -
9.14 - - - General(LS IN/OUT) - - Docs:=6 -
9.14 S2-2205443 LS In Information LS from SA WG5: Reply LS on Issues Network Slice information delivery to a 3rd party SA WG5 (S5-223516) Rel-18 Noted Noted
9.14 S2-2205452 LS In Information LS from BBF: LS on information about BBF s release of technical report on network slicing management BBF (LIAISE-530-04) - Noted Noted
9.14 S2-2206662 LS OUT Approval [DRAFT] LS Out on RAN dependency of FS_eNS_Ph3 ZTE Rel-18 r08 agreed. Revised to S2-2207435. Peter Hedman (Ericsson) provides questions
Jinguo(ZTE) provides r01
alessio(Nokia) provides r03
Jinguo(ZTE) provides r04
alessio(Nokia) provides r05 correcting some questions text. we still think some things can be done in SA2 without asking (like whether timing info can be configured in RAN and provided to AMF from RAN.)
Genadi (Lenovo) asks questions for clarification.
Jinguo(ZTE) asks question for clarification and provides r06
Jinguo(ZTE) provides r07
Genadi (Lenovo) provides r08.
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and depending on the answer proposes to agree r08 + removing question for KI#1.
Alessio(Nokia) can live with removing the Q1 but not because of what ericsson says: the scenario is the AMF gives to selected RAN nodes a remapping to cause load shedding in specific areas and not for all UEs of the slice in all areas of the AoS. so the question to me can be asked but not asking it does not mean it is out of scope, only that we are confident in SA2 this can be done technically (indeed I see no show stopper)
Jinguo(ZTE) provides response and agree r08 + removing question for KI#1+ removing the bar data.
alessio(Nokia) requests also to remove question 5 as this is not agreeable a solution for us.
Haiyang (Huawei) thinks this LS should have the same treatment as LSes to other groups for solution check.
Jinguo(ZTE) provides response to Haiyang(Huawei)
Jinguo(ZTE) response: will update the LS based on outcome of the solution
Srisakul(NTT DOCOMO) agrees with Haiyang (Huawei).
Jinguo(ZTE) provides response to Srisakul(Docomo)
==== 9.X, 10.X Final Deadline ====
Jinguo(ZTE) provides r09 based on the outcome of discussion, ask for CC#5
Jinguo(ZTE) provides r10, ask for CC#5
Revised
9.14 S2-2207435 LS OUT Approval LS Out on RAN dependency of FS_eNS_Ph3 SA WG2 Rel-18 Revision of S2-2206662r08. Approved Approved
9.14 S2-2205715 LS OUT Approval [DRAFT] LS on slice SoR security Huawei, HiSilicon Rel-18 Noted Jinguo(ZTE) replies to Myungjune (LGE)
Myungjune (LGE) provides comments
George (Ericsson) provides comments
Haiyang (Huawei) responds to George Foti (Ericsson)
George Foti (Ericsson) provides comments
Srisakul (NTT DOCOMO) supports to send LS to SA3 at this stage. Can we try to merge drafted LS (6325) into this one or the other way around, and just send one LS on the same SoR topic?
Kundan(NEC) seeks clarification.
Haiyang (Huawei) provides feedback
alessio(Nokia) concurs we should ask questions on solutions we evaluate to proceed with ... for now this LS shall be noted.
Haiyang (Huawei) comments
Dongeun (Samsung) has concern on the LS
Alessio(Nokia) comments on comments and still retains all that matters is the requirement that this shall be secure.
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) further comments
Haiyang (Huawei) clarifies to Dongeun (Samsung)
==== 9.X, 10.X Final Deadline ====
Noted
9.14 S2-2206325 LS OUT Approval [DRAFT] Slice based Steering of Roaming NTT DOCOMO Rel-18 Postponed Stefano (Qualcomm) proposes noting the LS.
George Foti (Ericsson) provides comments
Srisakul (NTT DOCOMO) provides r01 and responses to George (Ericsson) and Stefano (Qualcomm).
alessio(Nokia) proposes also to note the LS
Srisakul (NTT DOCOMO) responds to Alessio (NOKIA). Let's postpone it, so that we do not forget about it in the next SA2 meeting.
alessio(Nokia) we will propose some way forward in the evaluation and conclusions and propose the normative work is done in CT1 so I expecting this fulfills the need to interact with CT1 as the WID will be agreed in CT1 for this work.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
9.14 - - - KI#1 new solution - - Docs:=9 -
9.14 S2-2205559 P-CR Approval 23.700-41: Solution for KI#1 Alibaba Group Rel-18 Noted Genadi (Lenovo) provides comments.
Xiaobo Yu (Alibaba) provides r01 and replies to comments from Genadi (Lenovo).
Haiyang (Huawei) provides comments.
Xiaobo Yu (Alibaba) provides r02 and replies to Haiyang (Huawei).
Jinguo(ZTE) provides comments
Xiaobo Yu (Alibaba) provides r03 and replies to Jinguo (ZTE)
alessio(nokia) has a comment and proposes to note this paper
Xiaobo Yu (Alibaba) provide r04 and replies to comments from alessio(nokia)
alessio(Nokia) still retains we should not specify an API where AFs request slice change or are advised of return to an original slice... the AF should not be involved in driving the network resources control.
Xiaobo Yu (Alibaba) provide r05 and replies to comments from alessio(nokia)
==== 9.X, 10.X Revisions Deadline ====
alessio(nokia) requests to note this paper as it implies customers have to participate actively in the network resources management.
Xiaobo Yu (Alibaba) proposes a way forward and request to review this contribution in CC#5.
Haiyang (Huawei) further comments.
Xiaobo Yu (Alibaba) replies to Haiyang (Huawei).
Alessio(NOKIA) comments that the proposal still entrusts the AF to cause the slice remapping . we do not see this is needed...
==== 9.X, 10.X Final Deadline ====
Xiaobo Yu (Alibaba) replies to Alessio(Nokia)
Alessio(Nokia) can accept the concept the QoE underperformance indication is provided to the network by AF but not an indication to trigger slice swith which is not what the AF can know about (the network may not have a slice to switch to nor the target slice may be less busy if it existed). if this solution is changed to say the AF provides indication of QoE to the network I would be fine.
Xiaobo Yu (Alibaba) is ok with the proposal from Alessio (Nokia) and asks to review this contribution in CC#5.
Noted
9.14 S2-2205780 P-CR Approval 23.700-41: KI#1, New solution: S-NSSAI change decided by PCF China Mobile Rel-18 CC#5: r01 + changes agreed. Revised to S2-2207436. Jinguo(ZTE) provides comments
Genadi (Lenovo) provides comments.
Haiyang (Huawei) provides comments.
Alessio(Nokia) asks to note this paper
Yi (China Mobile) replies and provides r01.
==== 9.X, 10.X Revisions Deadline ====
Alessio(Nokia) asks to note this paper as roaming support is not explained and also we cannot agree with AF being trigger of this
Haiyang (Huawei) comments.
Yi (China Mobile) replies to Alessio.
==== 9.X, 10.X Final Deadline ====
Yi (China Mobile) replies to Haiyang.
Alessio(Nokia) can live with the proposed revision by Yi Jiang
Revised
9.14 S2-2207436 P-CR Approval 23.700-41: KI#1, New solution: S-NSSAI change decided by PCF China Mobile Rel-18 Revision of S2-2205780r01 + changes. Approved Approved
9.14 S2-2205875 P-CR Approval 23.700-41: KI#1, New solution: solution avoiding service interruption Ericsson Rel-18 CC#5: r03 + changes agreed. Revised to S2-2207437. Myungjune (LGE) provides comments
Peter Hedman (Ericsson) provides replies
Myungjune (LGE) requests revision.
Myungjune (LGE) replies to Jinguo(ZTE)
Jinguo(ZTE) provides comments
Peter Hedman (Ericsson) provides comments and r01.
Jinguo(ZTE) provides response
Dongeun (Samsung) comments
Alessio(Nokia) provides comments
Peter Hedman (Ericsson) provides r02
Genadi (Lenovo) asks for clarifications.
Peter Hedman (Ericsson) provides reply
Myungjune provides comments.
Dongeun (Samsung) provides comments
Peter Hedman (Ericsson) provides r03
alessio(Nokia) comments and thinks this solution may not be needed because the UPD does not change and IP address does not change. the NG-RAN mobility driven use case was ruled out so not sure we can add it just for this solution after all other companies had to abstain from it so far (mainly because some, but not us, did not agree this is a valid scenario BTW).
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) proposes to agree r03 as the solution enhances also scenarios to be addressed.
Jinguo(ZTE) suggest agree r03 + removing scenario 2a)
Dongeun (Samsung) shares same view with ZTE (Jinguo)
Tao(VC) let's check Jinguo's proposal, i.e., agree r03 + removing scenario 2a), agreeable or not to all
alessio(Nokia) comments that repartitioning is possible if same pool of resources is used by source or target S-NSSAI (like in jinguo's paper which I will comment on separately - we see no need to change slices using same resources keeping same IP address) hence it is not impacting our specs. so our specs should solely address the case that same pol of resources is not used by source and target Slices (i.e. new PDU session with new address). we can live with this paper if we remove the out of scope scenario and also we clarify in a note that the case of keeping same IP address may not require standard impact as the s-NSSAIs are using same SMF/ UPF
Alessio(Nokia) ok with this but also add this note at functional description clause 'NOTE: whether there is a need for any new S-NSSAI when same SMF/UPF is used and address is preserved is unclear as repartitioning may also work like done in the RAN for similar issue'
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207437 P-CR Approval 23.700-41: KI#1, New solution: solution avoiding service interruption Ericsson Rel-18 Revision of S2-2205875r03 + changes. Approved Approved
9.14 S2-2206406 P-CR Approval 23.700-41: KI#1, New Sol: Network controlled change to an alternative S-NSSAI Lenovo Rel-18 r02 agreed. Revised to S2-2207438. Jinguo(ZTE) provides comments
Myungjune (LGE) provides comments.
Genadi (Lenovo) replies to Myungjune (LGE) and Jinguo(ZTE). Providing r01 to capture AMF impact.
Xiaowen Sun (vivo) provides comments.
Genadi (Lenovo) replies to Xiaowen Sun (vivo).
Jinguo(ZTE) provides further comments
Xiaowen Sun (vivo) provide further comments.
Haiyang (Huawei) comments
Genadi (Lenovo) replies to Haiyang (Huawei).
Genadi (Lenovo) provides comments to Xiaowen Sun (vivo) and Jinguo(ZTE). Also, r02 is provided.
Dongeun (Samsung) provides comments
Haiyang (Huawei) further comments
Genadi (Lenovo) replies to Alessio(Nokia).
Alessio(Nokia) comments that the VPLMN can always update the configured NSSAI with a new mapping or provide even alternate mappings one of which is the fallback S-NSSAI keeping same HPLMN. of course we could add the cap; ability to do the same in HPLMN in rel-18 (as we remove the mapping in HPLMN now)
Genadi (Lenovo) replies to Dongeun (Samsung).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Genadi (Lenovo) provides clarifications to Haiyang (Huawei).
Revised
9.14 S2-2207438 P-CR Approval 23.700-41: KI#1, New Sol: Network controlled change to an alternative S-NSSAI Lenovo Rel-18 Revision of S2-2206406r02. Approved Approved
9.14 S2-2206458 P-CR Approval 23.700-41: KI #1, New Sol:Remapping in Initial Registration to Support Network Slice Service Continuity Vivo Rel-18 r02 agreed. Revised to S2-2207439. Jinguo(ZTE) provides comments
Xiaowen Sun(vivo) provides revised document r01.
Dongeun (Samsung) provides questions
Xiaowen Sun (vivo) provides response.
Genadi (Lenovo) provides comments.
Xiaowen Sun (vivo) provides responses.
Xiaowen Sun (vivo) provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207439 P-CR Approval 23.700-41: KI #1, New Sol:Remapping in Initial Registration to Support Network Slice Service Continuity Vivo Rel-18 Revision of S2-2206458r02. Approved Approved
9.14 - - - KI#1 solution udpate - - Docs:=8 -
9.14 S2-2205823 P-CR Approval 23.700-41: KI#1,6: Update to Solution 32 Ericsson Rel-18 Noted Peretz (Verizon) provides a comment addressing UE supported SSC mode
George (Ericsson) provides r01 to address that aspect.
George (Ericsson) is OK with r02
Peretz (Verizon) provides r02 to complete the change
Dongeun (Samsung) comments
Alessio (Nokia) asks a question as the solution update is confusing.
Alessio (Nokia) comments that missing any reply on our questions will need to ask the PCR to be noted ?
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.14 S2-2205958 P-CR Approval 23.700-41: KI#1, Update Sol #3, #4, #5 and #32 to prevent reusing previous slice LG Electronics Rel-18 r01 agreed. Revised to S2-2207440. Genadi (Lenovo) provides comments.
Myungjune (LGE) replies to Genadi (Lenovo).
Alessio(Nokia) believes the SM BOT is not needed if the S-NSSAI is not allowed.
Genadi (Lenovo) provides comments to Myungjune (LGE).
Myungjune (LGE) answers to Alessio (Nokia) and Genadi (Lenovo)
Jinguo(ZTE) provides comments
Myungjune replies to Jinguo(ZTE)
Alessio(Nokia) comments the S-NSSAI needs not be included in a rejected s-NSSAI, just neither in allowed nor rejected but a BOT can be provided for it by AMF to avoid registration for a while if the network knows congestion wil resolve by then, otherwise a rejected indication and subsequent removal from rejected by configuration update can works also. so this solution is probably needing rework as not acceptable as is (also because the BoT should apply to the slice not to the DNN in the slice)
Myungjune (LGE) provides r01.
alessio(Nokia) is ok with r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207440 P-CR Approval 23.700-41: KI#1, Update Sol #3, #4, #5 and #32 to prevent reusing previous slice LG Electronics Rel-18 Revision of S2-2205958r01. Approved Approved
9.14 S2-2206038 P-CR Approval 23.700-41: FS_eNS_Ph3 K#1 Solution 2 update Samsung Rel-18 Approved Jinguo(ZTE) provides comments
Dongeun (Samsung) replies to Jinguo (ZTE)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.14 S2-2206146 P-CR Approval 23.700-41: ENS_Ph3 KI#1 Sol#5: Updates to Solution 5 NEC Rel-18 r02 agreed. Revised to S2-2207441. Jinguo(ZTE) provides comments
Iskren (NEC) answers comments from Jinguo(ZTE)
Genadi (Lenovo) provides comments to Iskren (NEC).
Jinguo(ZTE) provides further comments
Iskren (NEC) answers comments from Genadi (Lenovo) and Jinguo(ZTE) and provides updates in r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207441 P-CR Approval 23.700-41: ENS_Ph3 KI#1 Sol#5: Updates to Solution 5 NEC Rel-18 Revision of S2-2206146r02. Approved Approved
9.14 S2-2206659 P-CR Approval 23.700-41: FS_eNS_Ph3 KI#1 Update on Solution 1 ZTE Rel-18 Noted Jinguo(ZTE) provides response
Xiaowen Sun (vivo) provides comments.
Myungjune (LGE) asks question
Genadi (Lenovo) comments.
Jinguo(ZTE) provides response to Genadi (Lenovo) and Myungjune (LGE)
Myungjune (LGE) responses to Jinguo(ZTE)
Jinguo(ZTE) response to Myungjune(LGE)
Xiaowen Sun(vivo) provides further comments.
Jinguo(ZTE) provides r01
Haiyang (Huawei) provides comments.
Jinguo(ZTE) response to Haiyang(Huawei)
alessio(nokia) comments that this solution update is misleading.
alessio(Nokia) the point is both slices may use shared resources. there is no need to have dedicated resources rather than in extreme cases! dedicated is meaning no other slice can use unused resources.
==== 9.X, 10.X Revisions Deadline ====
alessio(Nokia) comments that this P-CR update is not needed and introduces some misconceptions. asks to note this P-cR .
Jinguo(ZTE) replies to Alessio(Nokia) and suggest to agree r01+ following NOTE: In this solution the dedicated resource and shared resource in RAN are identified with different S-NSSAI(s).
Haiyang (Huawei) provides a question
Jinguo(ZTE) provides responses to Haiyang(Huawei)
alessio(nokia) comments and believes the existing description in TR was clearer than the new one so better to note the paper
Jinguo(ZTE) still suggest to approve r01.
==== 9.X, 10.X Final Deadline ====
Noted
9.14 S2-2206694 P-CR Approval 23.700-41: KI#1, Solution #3 Update: resolving editor's note Nokia, Nokia Shanghai Bell Rel-18 Approved Genadi (Lenovo) provides comments.
Myungjune (LGE) provides comments.
alessio (Nokia) Replies to comments
Myungjune (LGE) comments
Xiaobo Yu (Alibaba) provides comment.
alessio(nokia) replies to Myungjune (LGE) comments
Myungjune (LGE) clarifies question.
==== 9.X, 10.X Revisions Deadline ====
alessio(Nokia) clarifies that the allowed NSSAI shall indicate in addition whether a allowed S-NSSAI is a replacement of another one. this will mean the PDU session of of the existing S-NSSAI are to be replaced by the new one. do you mean we do not need this? if so we can do a deeper analysis in normative phase (we will not provide useless info if not needed)
==== 9.X, 10.X Final Deadline ====
Approved
9.14 - - - KI#2 solution update - - Docs:=7 -
9.14 S2-2205707 P-CR Approval 23.700-41: KI#2, Solution#20 update to remove ENs Huawei, HiSilicon Rel-18 CC#5: Approved Haiyang (Huawei) responds to George Foti (Ericsson)
George Foti (Ericsson) provides comments
Kundan(NEC) asks question.
Haiyang (Huawei) responds to Kundan (NEC)
Alessio(Nokia) thinks this solution is self contradictory and unclear, doubts this is technically valid.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) proposes to note the CR
Haiyang (Huawei) replies to Alessio(Nokia).
Haiyang (Huawei) thinks George (Ericsson) is commenting on a wrong paper as no concerns raises before
==== 9.X, 10.X Final Deadline ====
Alessio(Nokia) believes the reply was not satisfactory so we ask to note this paper.
Approved
9.14 S2-2205826 P-CR Approval 23.700-41: KI#2: Update to Solution 6 Ericsson Rel-18 r06 agreed. Revised to S2-2207442. Jinguo(ZTE) provides comments
Myungjune (LGE) provides r01
George (Ericsson) provides response
Myungjune (LGE) replies to George (Ericsson)
George (Ericsson) provides r02. Converted EN to note
Alessio(Nokia) provides r03
Ulises (InterDigital): provides comments and provides r05.
Myungjune (LGE) comments on r05.
Ulises (InterDigital): replies to Myungjune.
Myungjune (LGE) replies to Ulises (InterDigital).
Ulises (InterDigital): replies to Myungjune (LGE) and provides r06.
Myungjune (LGE) is ok with r06.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ericsson Ok with r06
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207442 P-CR Approval 23.700-41: KI#2: Update to Solution 6 Ericsson Rel-18 Revision of S2-2205826r06. Approved Approved
9.14 S2-2205959 P-CR Approval 23.700-41: KI#2, Sol #17: Update to resolve ENs LG Electronics Rel-18 r04 agreed. Revised to S2-2207443. Myungjune (LGE) replies to George Foti (Ericsson)
George Foti (Ericsson) provides comments
Jinguo(ZTE) provides comments
Myungjune (LGE) replies to Jinguo(ZTE)
Jinguo(ZTE) provides answers to Myungjune(LGE)
Myungjune(LGE) responses Jinguo(ZTE)
Xiaowen Sun (vivo) provides new comments.
Myungjune (LGE) replies to Xiaowen Sun (vivo)
Chia-Lin (MediaTek) ask for clarification for the revision part and has concern on the yellow highlighted sentence
Myungjune (LGE) responses to Chia-Lin (MediaTek)
Haiyang (Huawei) comments.
Kundan (NEC) asks question for clarification
Myungjune (LGE) replies to Haiyang (Huawei) and provides r02
Myungjune (LGE) answers Kundan (NEC)
Alessio(Nokia) provides r02
Myungjune (LGE) indicates that Alessio (Nokia) does not provided revision.
Alessio(Nokia) provides r03
Myungjune (LGE) provides r04.
Myungjune (LGE) can live with r04
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) OK with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207443 P-CR Approval 23.700-41: KI#2, Sol #17: Update to resolve ENs LG Electronics Rel-18 Revision of S2-2205959r04. Approved Approved
9.14 S2-2206680 P-CR Approval 23.700-41: KI#2 Sol#18: Updates to Solution 18 NEC Rel-18 r02 agreed. Revised to S2-2207444. alessio(Nokia) provides r01
Kundan(NEC) provides r02: adding one minor clarification on top of r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207444 P-CR Approval 23.700-41: KI#2 Sol#18: Updates to Solution 18 NEC Rel-18 Revision of S2-2206680r02. Approved Approved
9.14 - - - KI#3 new solution - - Docs:=4 -
9.14 S2-2205876 P-CR Approval 23.700-41: KI#3, New solution: Network Slice or service availability on a per cell level granularity Ericsson Rel-18 r03 agreed. Revised to S2-2207524. Jinguo(ZTE) provides comments
Xiaowen Sun (vivo) provides comments.
Ashok (Samsung) comments.
Peter Hedman (Ericsson) provides r01
Haiyang (Huawei) comments
Peter Hedman (Ericsson) provides reply
Alessio(Nokia) notes the NSAG is not indicating what the current slice supports but what slices a band supports for cell reselection, so this is wrong understanding of NSAG by Ericsson. Also the NSAG does not apply to all slices and there is a strict limit of 256 per TA so this is a non-scalable solution even if the NSAG was evolved to mean something new. Then NSAG is a VPLMN value so indicating this from UDM does not work like also the cells based restriction in roaming case. We think this is not a workable solution and since it is late we see no need to document it. in addition the per cell solution si similar to CSANs so if we need this we can merge that part of paper in the Huawei paper (if that is acceptable of course). we ask to note this PCR.
Peter Hedman (Ericsson) provides r02
Haiyang (Huawei) further comments
Alessio(nokia) disagrees extending the NSAG is a good choice. But then why not just advertise a new TAC! we oppose this solution on technical grounds as it changes the paradigm of slice when instead of NSAG we used a TAC this would be fully aligned with current slicing signalling and procedures and avoid the downsides. Also NSAG is for Access stratum features while a slice is not an access stratum feature. so we cannot accept the paper with the NSAG in on technical grounds. if you remove this option we can live with the rest being documented.
Peter Hedman (Ericsson) provides replies
Kundan (NEC) supports r02.
Alessio(Nokia) provides more comments and reiterated the document is not acceptable with NSAG option in it. provides r03 which we can accept technically
Peter Hedman (Ericsson) provides r04
Dongeun (Samsung) has a concern on UE impact and provides comments.
==== 9.X, 10.X Revisions Deadline ====
Dieter (Deutsche Telekom): We support adding this a candidate solution to the TR that addresses the aspect of slice/service availability limited to an area smaller than TA of the KI#3.
Alessio(Nokia) has same concerns as Samsung and proposes to note the paper.
Peter Hedman (Ericsson) provides reply on that UDM does not need per cell information as can provide location information as per current 23.501.
Alessio(Nokia) comments further and retains the objection to all revisions except r03
Peter Hedman (Ericsson) It can be note dthat Nokia states additions to SIB does not make sense i.e. that will then also apply for solution #9.
Alessio(Nokia) commented that it does NOT make sense if it is not useful to support the same behaviour of TA (use the SIB anyhow but now we create a totally new behaviour)... Ericsson is please requested to not misrepresent Nokia statements.
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207524 P-CR Approval 23.700-41: KI#3, New solution: Network Slice or service availability on a per cell level granularity Ericsson Rel-18 Revision of S2-2205876r03. Approved Approved
9.14 S2-2206563 P-CR Approval 23.700-41: KI#3, New Sol: Support Area of Service not matching existing TA boundaries Huawei, HiSilicon Rel-18 CC#4: Huawei proposed r01. Revised to S2-2207889. Jinguo(ZTE) provides comments
Susan (Huawei) replies to Jinguo (ZTE).
Ashok (Samsung) comments Susan
Susan (Huawei) replies.
Peter Hedman (Ericsson) provides comments
alessio(Nokia) comments that this solution does not impact UE and hence there is a problem. cannot accept the solution as is.
Susan (Huawei) replies to Peter Hedman (Ericsson).
Susan (Huawei) replies to alessio(Nokia).
Jinguo(ZTE) provides response
alessio(Nokia) comments that if this is the solution we object to it
Susan (Huawei) replies to alessio(Nokia) and provides r01.
==== 9.X, 10.X Revisions Deadline ====
Susan (Huawei) further clarifies to alessio(Nokia).
Dieter (Deutsche Telekom): We support adding this a candidate solution to the TR that addresses the aspect of slice/service availability limited to an area smaller than TA of the KI#3.
alessio(Nokia) believes this 'distance based' criterion is prone to failure as there is no real way to estimate the speed or future mobility pattern. we cannot accept solution that are not deterministically allowing access to the slice in the AoS.
Susan (Huawei) replies to alessio(Nokia) and cannot accept Alessio (Nokia)'s unreasonable objection, and asks him to be more constructive and not always object a paper without reasonable argumentation. Please note that backoff timer he's questioning is widely used in 3GPP, and in addition the solution in this paper can improve the service experience of legacy UEs, which is not well addressed with the existing solutions in the TR.
Susan (Huawei) asks for CC#4 or CC#5 discussion, if Alessio (Nokia) sustains his objection.
Alessio(nokia) replies and keeps objection to us9ing BoT as a way to restrict access outside the AoS.
Susan (Huawei) provides r02 and asks for CC#5 approval.
==== 9.X, 10.X Final Deadline ====
Alessio(Nokia) can live with r02 as now the BoT is not indicated. we will still have evaluation comments
Revised
9.14 S2-2207889 P-CR Approval 23.700-41: KI#3, New Sol: Support Area of Service not matching existing TA boundaries Huawei, HiSilicon Rel-18 Revision of S2-2206563. Approved Approved
9.14 - - - KI#3 solution update - - Docs:=6 -
9.14 S2-2205708 P-CR Approval 23.700-41: KI#3, Solution#21 update to remove ENs Huawei, HiSilicon Rel-18 Noted Ashok (Samsung) comments
Haiyang (Huawei) responds
Alessio(Nokia) provides r01
Haiyang (Huawei) provides r02, not ok with r01
Alessio(Nokia) observes that r02 just states the obvious (i.e. the PCF sets the URSP). the problem is this is not a good way to decommission a slice for maintenance if we need fist to update the URSP and then update again after the slice is back. if the note is not accepted we can leave the EN in as the change you propose(remove the eN) is not satisfactory. we can evaluate the solution even without removing the EN. so please let us know if you prefer r01 or the existing text in TR.
==== 9.X, 10.X Revisions Deadline ====
Alessio(Nokia) can live only with r01
==== 9.X, 10.X Final Deadline ====
Noted
9.14 S2-2206150 P-CR Approval 23.700-41: ENS_Ph3 KI#3 Sol#23: Updates to Solution 23 NEC Rel-18 r02 agreed. Revised to S2-2207445. Jinguo(ZTE) provides comments
Iskren (NEC) answers comments from Jinguo(ZTE) and provides r01
Ashok (Samsung) comments
Jinguo(ZTE) response to Iskren(NEC)
Iskren (NEC) answers comments Jinguo(ZTE) and from Ashok (Samsung) and provides rev02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207445 P-CR Approval 23.700-41: ENS_Ph3 KI#3 Sol#23: Updates to Solution 23 NEC Rel-18 Revision of S2-2206150r02. Approved Approved
9.14 S2-2206298 P-CR Approval 23.700-41: KI#3: Solution#8 Update NTT DOCOMO Rel-18 r03 agreed. Revised to S2-2207446. Myungjune (LGE) comments
Ashok (Samsung) comments
Srisakul (NTT DOCOMO) provides r01 and responds to comments from Ashok (Samsung) and Myungjune (LGE).
Myungjune (LGE) comments on r01.
Srisakul (NTT DOCOMO) responds to Myungjune (LGE).
Myungjune (LGE) responds to Srisakul (NTT DOCOMO).
Srisakul (NTT DOCOMO) provides r02 and responds to Myungjune (LGE).
Srisakul (NTT DOCOMO) provides r03 and responds to Ashok (Samsung)
==== 9.X, 10.X Revisions Deadline ====
Srisakul (NTT DOCOMO) asks Tao to change status whether r03 + updated figure in Sol#8 to align with texts proposed in r03 would be ok to approve. Texts in r03 will remain as it is.
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207446 P-CR Approval 23.700-41: KI#3: Solution#8 Update NTT DOCOMO Rel-18 Revision of S2-2206298r03. Approved Approved
9.14 S2-2206700 P-CR Approval 23.700-41: KI#3, Solution # 29 Update : Editor's Note resolution Nokia, Nokia Shanghai Bell Rel-18 Noted Haiyang(Huawei) comments
==== 9.X, 10.X Revisions Deadline ====
Haiyang(Huawei) suggests to note this paper
Alessio(Nokia) comments the note requested to clarify the relationship with solution 6.9 and this aper did exactly that
==== 9.X, 10.X Final Deadline ====
Alessio(Nokia) comments that the EN resolution is meeting the text of the EN. please take to CC#5
Noted
9.14 - - - KI#4 new solution - - Docs:=1 -
9.14 S2-2205827 P-CR Approval 23.700-41: KI#4: New Solution Centralized Support Ericsson Rel-18 Noted Jinguo(ZTE) provides comments
Alessio(Nokia) notes that architecturally this is not different from Sol12. the other new parts seem to be done to facilitate creating category of UEs (moving and not moving) that are treated differently. we believe this is not correct and we object to this as technically there is no reason to prefer a moving UE to a non-moving UE BUT also we note that with centralized control the issue of moving UEs is resolved as the admission has a single quota. if new aspects need to be added to sol12 that are essential this should be done there.
==== 9.X, 10.X Revisions Deadline ====
Alessio(Nokia) asks to note this (as TAO asked if r00 can be approved) as this is not adding to the existing options (one NSAF across EPS and 5GS already is supported and also the identification of different types of UEs if so desired can be done at NSAF by checking if the UE Id is already in the NSACF or not. but we should not specify in any normative work what happens in the NSACF in terms of admission p;olicies.
==== 9.X, 10.X Final Deadline ====
Noted
9.14 - - - KI#4 solution update - - Docs:=2 -
9.14 S2-2206529 P-CR Approval 23.700-41: KI#4, Sol #13: Updates of Solution #13 Huawei, HiSilicon, China Mobile Rel-18 r01 agreed. Revised to S2-2207447. Jinguo(ZTE) provides comments
Fenqin(Huawei) provides responds
alessio(Nokia) believes that the solution update is not needed. the centralized control seems to be enough (e.g. the NSAF admission policy if so desired may privilege the existing UEIDs.
Alessio(nokia) then proposes to not update this solution on this aspect (not sure any other update was in there )
Fenqin(Huawei) provides r01
==== 9.X, 10.X Revisions Deadline ====
alessio(Nokia) is ok with r01
George Foti (Ericsson) objects to r00 as this includes evaluation aspects.
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207447 P-CR Approval 23.700-41: KI#4, Sol #13: Updates of Solution #13 Huawei, HiSilicon, China Mobile Rel-18 Revision of S2-2206529r01. Approved Approved
9.14 - - - KI#5 solution update - - Docs:=4 -
9.14 S2-2205711 P-CR Approval 23.700-41: Update to Solution #25 for RA determination Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207448. Ashok (Samsung) comments
Haiyang (Huawei) provides r01
Peter Hedman (Ericsson) provides question
Haiyang (Huawei) provides feedback
Peter Hedman (Ericsson) provides comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207448 P-CR Approval 23.700-41: Update to Solution #25 for RA determination Huawei, HiSilicon Rel-18 Revision of S2-2205711r01. Approved Approved
9.14 S2-2205921 P-CR Approval 23.700-41: KI#5, Sol#27 update NTT DOCOMO Rel-18 r02 agreed. Revised to S2-2207449. Ashok (Samsung) comments
Ashok (Samsung) seeks clarification
Tsuyoshi (NTT DOCOMO) provides response
Patrice (Huawei) shares the concern from Ashok (Samsung).
Tsuyoshi (NTT DOCOMO) provides response to Patrice
Tsuyoshi (NTT DOCOMO) provides r02
Alessio(Nokia) does not thing we will eventually discuss the exact encoding anyhow in the conclusions of TR but can live with NEC/docomo providing their view here for illustrative purposes only .
Tsuyoshi (NTT DOCOMO) respond to Alessio(Nokia)
Patrice (Huawei) thanks Tsuyoshi (NTT Docomo) for the clarification.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207449 P-CR Approval 23.700-41: KI#5, Sol#27 update NTT DOCOMO Rel-18 Revision of S2-2205921r02. Approved Approved
9.14 - - - KI#6 new solution - - Docs:=2 -
9.14 S2-2206013 P-CR Approval 23.700-41: KI#6_New Solution_Controling network slice based on UE's inactive PDN connection Samsung Rel-18 Approved George Foti (Ericsson) proposes to note the CR. I don't think this is in scope of thework
Ashok (Samsung) responds to George Foti (Ericsson)
Myungjune (LGE) provides comments
George (Ericsson) responds. We did not discuss 4G in this work item. That's my point. Please point me to where we need to cover this in the actual work item
Ashok (Samsung) comments
Alessio(Nokia) proposes to update this paper as in r02
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) provides comments
Jinguo(ZTE) provides comments
Ashok (Samsung) responds to George (Ericsson)
Ashok (Samsung) responds to Alessio (Nokia) and Jinguo(ZTE) and propose to go with original r00
Alessio (nokia) replies to Jinguo. we are ok with r02 and r00 but we will need to evaluate this carefully
George (Ericsson) provides comment.
Ashok (Samsung) agrees with Alessio (Nokia)
Ashok (Samsung) clarifies to George (Ericsson)
George (Ericsson) asks question
Ashok (Samsung) replies
George (Ericsson) replies
==== 9.X, 10.X Final Deadline ====
Approved
9.14 S2-2206460 P-CR Approval 23.700-41: KI #6, New Sol:Improve Network Control with Network Slice Admission Control Vivo Rel-18 Noted Jinguo(ZTE) provides additional comments
Myungjune (LGE) provides comments
George Foti (Ericsson) provides comments
Xiaowen Sun(vivo) provides response to the comments.
Fenqin(Huawei) provides comments.
Ashok (Samsung) comments.
Xiaowen (vivo) provides response.
Xiaowen (vivo) provides r01.
Fenqin (Huawei) provides comments.
Xiaowen (vivo) responds.
Xiaowen (vivo) provides response to Ashok (Samsung).
Jinguo(ZTE) provides comments
Xiaowen Sun(vivo) provides response to Jinguo.
Ashok (Samsung) explain the scenario to Xiaowen (vivo)
Xiaowen Sun(vivo) replies to Jinguo.
Xiaowen Sun (vivo) provides response.
Ashok (Samsung) comments that the solution does not work in its present form and propose to NOTE
Xiaowen Sun (vivo) provide response and upload r02.
Xiaowen Sun (vivo) provided response.
Ashok (Samsung) still feels the pCR is not needed when it does not work in many scenarios
Fenqin (Huawei) share the similar view as Ashok
Xiaowen Sun (vivo) provides response to Ashok and Fenqin.
Xiaowen Sun (vivo) provides r03.
Ashok (Samsung) still feels the pCR is not needed but will not object if others are fine
Jinguo(ZTE) agree with Ashok(Samsung)
alessio(Nokia) concurs with Samsung that this solution seems to be not solving the problem we are facing and actually is an evolution of NSAC to implement a admission policy that privileges the most recent requests versus long established sessions and it is not clear why this should be done. in brief this documents a NSAC policy that can hardly be standardized, hence this paper would have to be noted as documenting NSAC policies was not in scope
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) proposes to note the CR
==== 9.X, 10.X Final Deadline ====
Noted
9.14 - - - KI#6 solution update - - Docs:=6 -
9.14 S2-2205643 P-CR Approval 23.700-41: KI#6, Sol #32: Update to allow the PCF initiate the move of a PDU session from one slice to another Verizon Switzerland AG Rel-18 r05 agreed. Revised to S2-2207450. Fenqin (Huawei) comments
Jinguo(ZTE) provides comments
Fenqin(Huawei) ask some further question.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207450 P-CR Approval 23.700-41: KI#6, Sol #32: Update to allow the PCF initiate the move of a PDU session from one slice to another Verizon Switzerland AG Rel-18 Revision of S2-2205643r05. Approved Approved
9.14 S2-2205825 P-CR Approval 23.700-41: KI#6: Update to Solution 38 Ericsson Rel-18 r02 agreed. Revised to S2-2207451. Ashok (Samsung) comments
George (Ericsson) replies
Jinguo(ZTE) provides comments
Fenqin (Huawei) comments
George (Ericsson) provides r01
alessio(Nokia) provides r02 to clarify the NSSF option cannot support per UE policies and that in roaming case HPLMN NSSF/PCF need to be involved.
George (Ericsson) provides comments. These can be added during the evaluation. R01 is sufficiently clear. I hope U can accept r01 and leave the rest for evaluation.
alessio(Nokia) thinks the only evaluation related Note is NOTE 3 whih takes text from ericsson ... there rest are solution descriptions. so we can only accept r02.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) can live with r02
Jinguo(ZTE) suggests to agree r02
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207451 P-CR Approval 23.700-41: KI#6: Update to Solution 38 Ericsson Rel-18 Revision of S2-2205825r02. Approved Approved
9.14 S2-2206531 P-CR Approval 23.700-41: KI#6,Sol#37, Update of Sol#37 Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207452. Ashok (Samsung) resends the comments by updating the correct tdoc no in the subject line
Fenqin (Huawei) provides response
Ashok (Samsung) responds to Fenqin (Huawei)
Jinguo(ZTE) provides comments
Fenqin (Huawei) provides response and r01
Ashok (Samsung) comments on r01
Fenqin (Huawei) provides further response
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.14 S2-2207452 P-CR Approval 23.700-41: KI#6,Sol#37, Update of Sol#37 Huawei, HiSilicon Rel-18 Revision of S2-2206531r01. Approved Approved
9.14 - - - Documents exceeding TU Budget - - Docs:=38 -
9.14 S2-2206681 P-CR Approval 23.700-41: KI#3 Sol#10: Updates to Solution 10 NEC Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205494 P-CR Approval 23.700-41: KI#3, Sol#8: Solution Update IPLOOK Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206468 P-CR Approval 23.700-41: KI #6, New Sol: Network Control of UE behavior based on network policy Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205824 P-CR Approval 23.700-41: KI#6: Update to Solution 34 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205710 P-CR Approval 23.700-41: Evaluation for KI#1_Support of Network Slice Service continuity Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205818 P-CR Approval 23.700-41: KI 1: Proposal for Evaluation and Interim Conclusion on KI #1 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205960 P-CR Approval 23.700-41: Evaluation for KI#1 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205961 P-CR Approval 23.700-41: Conclusion for KI#1 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206153 P-CR Approval 23.700-41: ENS_Ph3 KI#1 Evaluation and Conclusion for KI#1 NEC Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206469 P-CR Approval 23.700-41: KI #1, Overall Solution Evaluation Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206471 P-CR Approval 23.700-41: KI#1, Interim Conclusions Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206613 P-CR Approval 23.700-41: KI #1: Add Solution Evaluation for Key Issue #1 CATT Rel-18 Not Handled Devaki (Nokia) proposes r01.
Jari (NTT DOCOMO) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206614 P-CR Approval 23.700-41: KI #1: Add Conclusion for Key Issue #1 CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206646 P-CR Approval 23.700-41: KI#1, Interim conclusions Lenovo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206660 P-CR Approval 23.700-41: FS_eNS_Ph3 KI#1 Evaluation and Conclusion ZTE Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206756 P-CR Approval 23.700-41: Way forward proposal for Conclusions and Evaluations Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205712 P-CR Approval 23.700-41: Evaluation and conclusion of KI#2 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205819 P-CR Approval 23.700-41: KI 2: Proposal for Evaluation and Interim Conclusion on KI #2 Ericsson, Apple Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205962 P-CR Approval 23.700-41: Evaluation for KI#2 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205963 P-CR Approval 23.700-41: Conclusion for KI#2 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206895 P-CR Approval 23.700-41: Proposal for Interim Conclusion on KI #2. Qualcomm Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205713 P-CR Approval 23.700-41: Evaluation and conclusion of KI#3 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205820 P-CR Approval 23.700-41: KI 3: Proposal for Evaluation and Interim Conclusion on KI #3 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205902 P-CR Approval 23.700-41: KI #3, New Eval, Conclusion: Evaluation and Conclusion on the Temporary Network Slices aspects of Key Issue #3 InterDigital Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206893 P-CR Approval 23.700-41: Interim conclusions for key issues 3 and 5 Qualcomm Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205821 P-CR Approval 23.700-41: KI#4: Proposal for Evaluation and Interim Conclusion on KI #4 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206530 P-CR Approval 23.700-41: KI#4: Evaluation and Conclusion for KI#4 Huawei, HiSilicon, China Telecom, China Mobile Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206916 P-CR Approval 23.700-41: 23.700-41: KI#4: Evaluation and Conclusion for KI#4 NEC Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205714 P-CR Approval 23.700-41: Evaluation and conclusion for KI #5 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205822 P-CR Approval 23.700-41: KI#5: Proposal for Evaluation and Interim Conclusion on KI #5 Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205922 P-CR Approval 23.700-41: KI#5, Evaluation NTT DOCOMO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205964 P-CR Approval 23.700-41: Evaluation for KI#5 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2205965 P-CR Approval 23.700-41: Conclusion for KI#5 LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206948 P-CR Approval 23.700-41: KI#5: Evaluation and interim conclusion Apple Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206490 P-CR Approval 23.700-41: KI #6, Solution Evaluation Vivo Rel-18 Not Handled Violeta (Verizon) has concerns with the evaluation provided.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206491 P-CR Approval 23.700-41: KI #6, Interim Conclusions Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206532 P-CR Approval 23.700-41: KI#6,Evaluation and Conclusion for KI#6 Huawei, HiSilicon Rel-18 Not Handled Violeta (Verizon) has concerns with the evaluation and conclusions provided.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.14 S2-2206949 P-CR Approval 23.700-41: KI#6: Evaluation and interim conclusion Apple Rel-18 Not Handled Violeta (Verizon) has concerns with the conclusions provided.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.15 - - - Study on 5G AM Policy (FS_AMP) - - Docs:=18 -
9.15 - - - Solution Update - - Docs:=8 -
9.15 S2-2205525 P-CR Approval 23.700-89: KI#1, Sol#3 update to resolve EN Ericsson Rel-18 Approved Zhuoyi (China Telecom) responds to Judy.
Judy (Ericsson) responds to Zhuoyi (China Telecom)
Zhuoyi (China Telecom) provides asks for clarification.
Zhuoyi (China Telecom) responds to Judy (Ericsson)
Zhuoyi (China Telecom) is ok with Ericsson's reply.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.15 S2-2205716 P-CR Approval 23.700-89: KI#1, Sol#5: Update the procedure for the RFSP index transfer from AMF to HSS via UDM Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.15 S2-2205998 P-CR Approval 23.700-89: KI#1_Sol 6_Update to remove ENs Samsung Rel-18 r04 agreed. Revised to S2-2207098. Judy (Ericsson) provides r01
Ashok (Samsung) provides r02
Ashok (Samsung) provides r03. Please discard r02
Ashok (Samsung) comments
Judy (Ericsson) comments on UDM+HSS maintaining UE's 5G registration state temporarily for some duration
Zhuoyi (China Telecom) comments.
Ashok (Samsung) agrees with Zhuoyi (China Telecom)
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) is fine with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.15 S2-2207098 P-CR Approval 23.700-89: KI#1_Sol 6_Update to remove ENs Samsung Rel-18 Revision of S2-2205998r04. Approved Approved
9.15 S2-2205999 P-CR Approval 23.700-89: KI#1_Sol 7_Update to solution description Samsung Rel-18 Noted Judy (Ericsson) responds to Ashok (Samsung)
Ashok (Samsung) responds to Judy (Ericsson)
Judy (Ericsson) comment
Ashok (Samsung) clarifies to Judy (Ericsson)
Judy (Ericsson) comments
Ashok (Samsung) comments
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) proposes to NOTE this paper due to (1) the proposal is not based on the current stage 2 spec, and (2) agreement not to do normative work for wo N26 deployment
==== 9.X, 10.X Final Deadline ====
Noted
9.15 S2-2206245 P-CR Approval 23.700-89: 23.700-89: Updates to Solution #2 Nokia, Nokia Shanghai Bell Rel-18 Noted Judy (Ericsson) questions how the proposed change address the KI
Pallab (Nokia) responds to Judy (Ericsson)
Judy (Ericsson) responds to Pallab (Nokia) and ask to skip the previous comment
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) proposes to NOTE this paper as the proposal does not work as intended
Judy (Ericsson) objects to this paper, just for the sake of chairman's note.
==== 9.X, 10.X Final Deadline ====
Noted
9.15 S2-2206246 P-CR Approval 23.700-89: 23.700-89: Updates to Solution #10 Nokia, Nokia Shanghai Bell Rel-18 Noted Judy (Ericsson) questions how the proposed change address the KI
Pallab (Nokia) responds to Judy (Ericsson)
Judy (Ericsson) responds to Pallab (Nokia) and propose to note this paper
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.15 S2-2206337 P-CR Approval 23.700-89: FS_AMP,KI#1 Solution#9 Update to remove EN Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.15 - - - Evaluation and Conclusion - - Docs:=10 -
9.15 S2-2205526 P-CR Approval 23.700-89: KI#1, Evaluating solutions for deployment without N26 and conclusion Ericsson Rel-18 r04 agreed. Revised to S2-2207099, merging S2-2205966, S2-2205967, and S2-2206247 Zhuoyi (China Telecom) proposes to use S2-2205526 as baseline for KI#1 evaluation and conclusion for without N26 scenario.
Juan Zhang (Qualcomm) provides comments.
Judy (Ericsson) provides r01 to keep the option of no normative work for noN26 case
Pallab (Nokia) comments on r01
Judy (Ericsson) responds to Pallab (Nokia)
Pallab (Nokia) responds to Judy (Ericsson)
Myungjune (LGE) comments
Susan (Huawei) propose no normative work for without N26.
Judy (Ericsson) responds to Pallab (Nokia) and comments
Susan (Huawei) replies to Judy (Ericsson).
Pallab (Nokia) comments and provides r02
Ashok (Samsung) comments
Judy (Ericsson) provides r03, replacing 'agreed' with 'concluded'
Zhuoyi (China Telecom) provides r04, adding China Telecom as co-source.
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) thanks Zhuoyi (China Telecom) for the support and is fine with r04
Myungjune (LGE) is ok with r04.
Juan Zhang (Qualcomm) is OK with r04.
Pallab (Nokia) OK to approve r04
==== 9.X, 10.X Final Deadline ====
Revised
9.15 S2-2207099 P-CR Approval 23.700-89: KI#1, Evaluating solutions for deployment without N26 and conclusion Ericsson Rel-18 Revision of S2-2205526r04, merging S2-2205966, S2-2205967, and S2-2206247. Approved Approved
9.15 S2-2205527 P-CR Approval 23.700-89: KI#1, Evaluation of solutions for N26 deployment and conclusion Ericsson Rel-18 Merged into S2-2207100 Zhuoyi (China Telecom) proposes to use S2-2206218 and S2-2206237 as baseline for KI#1 evaluation and conclusion for with N26 scenario.
Judy (Ericsson) is fine to mark this paper as merged to 6218 and 6237
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.15 S2-2205966 P-CR Approval 23.700-89: Evaluation for KI#1 LG Electronics Rel-18 Merged into S2-2207099 Zhuoyi (China Telecom) proposes to use S2-2205526 and S2-226218 as baseline for KI#1 evaluation for without N26 and with N26 scenario respectively.
Myungjune (LGE) is ok to merge into S2-2205526.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.15 S2-2205967 P-CR Approval 23.700-89: Conclusion for KI#1 LG Electronics Rel-18 Merged into S2-2207099 Zhuoyi (China Telecom) proposes to use S2-2205526 and S2-226237 as baseline for KI#1 conclusion for without N26 and with N26 scenario respectively.
Myungjune (LGE) is ok to merge into S2-2205526.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.15 S2-2206218 P-CR Approval 23.700-89: 23700-89_Solution Evaluation for KI#1 China Telecom, Huawei Rel-18 r04 agreed. Revised to S2-2207100, merging and S2-2205527 Zhuoyi (China Telecom) proposes to use S2-2206218 as baseline for KI#1 evaluation for with N26 scenario.
Zhuoyi (China Telecom) provide S2-2206218r01 as baseline for KI#1 evaluation for with N26 scenario.
Zhuoyi (China Telecom) is ok with r02.
Judy (Ericsson) provides r02
Ashok (Samsung) provides r03
Zhuoyi (China Telecom) comments the r03 link provided by Samsung is r02.
Ashok (Samsung) provides the r03 with correct link
Zhuoyi (China Telecom) comments on r03.
Ashok (Samsung) responds Zhuoyi
Zhuoyi (China Telecom) responds to Ashok.
Zhuoyi (China Telecom) provide r04.
Ashok (Samsung) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.15 S2-2207100 P-CR Approval 23.700-89: 23700-89_Solution Evaluation for KI#1 China Telecom, Huawei Rel-18 Revision of S2-2206218r04, merging and S2-2205527. Approved Approved
9.15 S2-2206237 P-CR Approval 23.700-89: 23700-89_Conclusion for KI#1 China Telecom, Huawei Rel-18 CC#4: r04 with changes proposed. r04 agreed. Revised to S2-2207101. Zhuoyi (China Telecom) proposes to use S2-2206237 as baseline for KI#1 conclusion for with N26 scenario.
Zhuoyi (China Telecom) provide S2-2206237r01 as baseline for KI#1 conclusion for with N26 scenario.
Ashok (Samsung) comments.
Zhuoyi (China Telecom) replies.
Ashok (Samsung) responds to Zhuoyi (China Telecom) and provides r02
Pallab (Nokia) comments and provides r03
Ashok (Samsung) comments that r03 is not acceptable to us
Susan (Huawei) provides comments.
Zhuoyi (China Telecom) provides comments.
Pallab (Nokia) responds to Zhuoyi (China Telecom)
Juan Zhang (Qualcomm) provides comments
Ashok (Samsung) comments and reiterate that 3rd sub use case of the KI#1 should be considered for conclusions.
Judy (Ericsson) provides r04
==== 9.X, 10.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r04.
Pallab (Nokia) OK to approve r04. Would like to co-sign
Ashok (Samsung) provides comments
Pallab (Nokia) supports Juan Zhang (Qualcomm) views
Judy (Ericsson) shared the view from Juan Zhang (Qualcomm)
Susan (Huawei) is ok with r04 and there is no need to add the new NOTE proposed by Ashok (Samsung).
Ashok (Samsung) propose some changes on top of r04 which needs some update before approval. Also would like co-sign the paper
Judy (Ericsson) comments that RFSP Index is not sent to the UE
Ashok (Samsung) responds to Judy (Ericsson)
Zhuoyi (China Telecom) request to marked this paper (r04) for CC#4 or CC#5 for some change needed.
Pallab (Nokia) comments.
Zhuoyi (China Telecom) comments.
==== 9.X, 10.X Final Deadline ====
Revised
9.15 S2-2207101 P-CR Approval 23.700-89: 23700-89_Conclusion for KI#1 China Telecom, Huawei Rel-18 Revision of S2-2206237r04. Approved Approved
9.15 S2-2206247 P-CR Approval 23.700-89: 23.700-89: Conclusion on KI#1 Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207099 Zhuoyi (China Telecom) proposes to use S2-2205526 and S2-226237 as baseline for KI#1 conclusion for without N26 and with N26 scenario respectively.
Pallab (Nokia) ok to merge this to 5526 and have the discussion in a single thread
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.16 - - - Study on Personal IoT Networks (5G_PIN) - - Docs:=64 -
9.16 - - - Moderator email discussion - - Docs:=1 -
9.16 S2-2206475 DISCUSSION Information Moderator email summary for companies view and way forward proposal Vivo Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.16 - - - General - - Docs:=2 -
9.16 S2-2205742 P-CR Approval 23.700-88: Update definition of terms Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2207453. Marco (Huawei) provides r01 to merge S2-2205742 and S2-2206479
Zhenhua (vivo) provides r02
Jianning (Xiaomi) provide comments
Zhenhua (vivo) answers to Jianning (Xiaomi)
Marco (Huawei) provides r03
Kefeng Zhang (Qualcomm) provides comments on 'network local switch'.
Zhenhua (vivo) answers to Kefeng Zhang (Qualcomm)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207453 P-CR Approval 23.700-88: Update definition of terms Huawei, HiSilicon Rel-18 Revision of S2-2205742r03. Approved Approved
9.16 - - - Solution update - - Docs:=15 -
9.16 S2-2205738 P-CR Approval 23.700-88: KI#3, sol#1: Update of solution #1 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2205739 P-CR Approval 23.700-88: KI#3, sol#6: Update of solution #6 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2205740 P-CR Approval 23.700-88: KI#4, sol#20: Update of solution #20 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2205988 P-CR Approval 23.700-88: KI#2, Sol#15: Update to remove ENs OPPO Rel-18 r01 agreed. Revised to S2-2207454. Boren (OPPO) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207454 P-CR Approval 23.700-88: KI#2, Sol#15: Update to remove ENs OPPO Rel-18 Revision of S2-2205988r01. Approved Approved
9.16 S2-2206248 P-CR Approval 23.700-88: 23.700-88: Updates to Solution #7 Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2206476 P-CR Approval 23.700-88: KI#1, Sol#0C: Update solution Vivo Rel-18 Approved Kefeng Zhang (Qualcomm) provides comments and questions.
Zhenhua (vivo) answers to Kefeng Zhang (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2206477 P-CR Approval 23.700-88: KI#3, Sol#8: Update solution Vivo Rel-18 r01 agreed. Revised to S2-2207455. Zhenhua (vivo) provides r01.
Kefeng Zhang (Qualcomm) asks questions for clarification.
Zhenhua (vivo) answers to Kefeng Zhang (Qualcomm)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207455 P-CR Approval 23.700-88: KI#3, Sol#8: Update solution Vivo Rel-18 Revision of S2-2206477r01. Approved Approved
9.16 S2-2206478 P-CR Approval 23.700-88: KI#4, Sol#12: Update solution Vivo Rel-18 r01 agreed. Revised to S2-2207456. Zhenhua (vivo) provides r01.
Kefeng Zhang (Qualcomm) asks question for clarification.
Zhenhua (vivo) answers to Kefeng Zhang (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207456 P-CR Approval 23.700-88: KI#4, Sol#12: Update solution Vivo Rel-18 Revision of S2-2206478r01. Approved Approved
9.16 S2-2206866 P-CR Approval 23.700-88: KI#6: Update to solution 10 Resolving EN(s) Intel Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2206868 P-CR Approval 23.700-88: KI#4: Update to Solution 13 Resolving EN(s) Intel Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2206903 P-CR Approval 23.700-88: PCR_5G_PIN- update solution#9 Xiaomi Rel-18 r01 agreed. Revised to S2-2207457. Jianning (Xiaomi) provides r01 by merging the S2-2206907, and S2-2206162 as suggested by Rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207457 P-CR Approval 23.700-88: PCR_5G_PIN- update solution#9 Xiaomi Rel-18 Revision of S2-2206903r01. Approved Approved
9.16 - - - Evaluations and conclusions - - Docs:=30 -
9.16 - - - Evaluations and conclusions on KI#1 - - Docs:=4 -
9.16 S2-2206012 P-CR Approval 23.700-88: KI #1, Interim conclusions Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 r07 agreed. Revised to S2-2207458. Saad (Interdigital) has concerns with the current conclusion text
Kefeng Zhang (Qualcomm) has uploaded r01.
Based on documents handling discussion, r01 has merged S2-2206012 and S2-2206481, serving as the baseline of discussion on KI#1 conclusions.
Zhenhua (vivo) provides r02.
Kefeng Zhang (Qualcomm) provides comments and questions to Zhenhua (vivo).
Marco (Huawei) disagree r02 and comments and propose text to bullet 1, 2
Zhenhua (vivo) replies to Kefeng (Qualcomm)
Zhenhua (vivo) asks Q to Marco (Huawei)
Jianning (Xiaomi) also has concerns on currently conclusion text, and seek clarification
Zhenhua (vivo) provides r04 and response to Jianning (Xiaomi), and ask ignore r03
Marco (Huawei) provides r05 and comments
Jianning (Xiaomi) provide further comments
Zhenhua (vivo) answers to Jianning (Xiaomi)
Marco (Huawei) comments to Zhenhua (vivo)
Jianning (Xiaomi) replies to Zhenhua (vivo) and Marco (Huawei)
Kefeng Zhang (Qualcomm) provides comments on Q1,2,3.
Marco (Huawei) share the view of Kefeng Zhang (Qualcomm)
Jianning (Xiaomi) replies Zhenhua(vivo) and Kefeng(Qualcomm) and provide r06
Kefeng Zhang (Qualcomm) comments to have a initial conclusion on whether AF is required in PIN architecture.
Boren (OPPO) comments.
Jianning (Xiaomi) agree to focus on the conclusion discussion of KI#1
Pallab (Nokia) comments.
Zhenhua (vivo) replies to Pallab (Nokia).
Qian (Ericsson) shares the same view as Pallab(Nokia)
Marco (Huawei) agrees with Pallab (Nokia)
Marco (Huawei) comments on AF
Zhenhua (vivo) thanks Marco (Huawei) share the definition of AF
Kefeng Zhang (Qualcomm) provides r07.
Pallab (Nokia) supports the updates done in r07
Kefeng Zhang (Qualcomm) replies Boren (OPPO) comments
Jianning (Xiaomi) thanks Marco (Huawei) to clarify the definition, and provide further comments
Jianning (Xiaomi) provide comments on r07
Zhenhua (vivo) replies to Jianning (Xiaomi)
Boren (OPPO) provides comments
Jianning (Xiaomi) replise to Zhenhua (vivo)
Pallab (Nokia) agrees with Zhenhua (vivo)
Jianning (Xiaomi) provide r08 based on r07
==== 9.X, 10.X Revisions Deadline ====
Pallab (Nokia) not OK with r08. Proposes to approve r07
Qian (Ericsson) prefers also r07 at this stage. Adding an EN on top of r07 is also ok.
Jianning (Xiaomi) replies to Pallab (Nokia) , suggest go with r08, not ok with r07
Zhenhua (vivo) propose for CC#5
Marco (Huawei) objects r08 and r00-r04, we are OK with r07, r06 and r05
Jianning (Xiaomi) object r00-06, but can live with r07 without 2) and 2a), adding an EN
'Editor's note: For PIN management, whether needs supporting with Application Function or 5GC NF is FFS'
Marco (Huawei) we object to bullet 2a as written in r08
Jianning (Xiaomi) replies to Marco(huawei), suggest to go with r07, without 2) and 2a), adding an EN.
==== 9.X, 10.X Final Deadline ====
Kefeng Zhang (Qualcomm) is not OK with r08.
Revised
9.16 S2-2207458 P-CR Approval 23.700-88: KI #1, Interim conclusions Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2206012r07. Approved Approved
9.16 S2-2206481 P-CR Approval 23.700-88: Evaluation and interim conclusions on KI#1 Vivo Rel-18 r04 agreed. Revised to S2-2207459. Zhenhua (vivo) provides r01.
Marco (Huawei) provides r02.
Jianning (Xiaomi) provide r03
Michele (Huawei) provides r04 and makes proposal for the process of selecting a solution for Key Issue 1
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207459 P-CR Approval 23.700-88: Evaluation and interim conclusions on KI#1 Vivo Rel-18 Revision of S2-2206481r04. Approved Approved
9.16 - - - Evaluations and conclusions on KI#2 - - Docs:=5 -
9.16 S2-2205916 P-CR Approval 23.700-88: KI#2, Eval and Conclusion: Evaluation of KI#2 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 r03 agreed. Revised to S2-2207460. Saad (Interdigital) provides r01
Marco (Huawei) provides r02
Michele (Huawei) provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207460 P-CR Approval 23.700-88: KI#2, Eval and Conclusion: Evaluation of KI#2 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 Revision of S2-2205916r03. Approved Approved
9.16 S2-2206014 P-CR Approval 23.700-88: KI #2, Interim conclusions proposal Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 r13 agreed. Revised to S2-2207461, merging and S2-2206905 Kefeng Zhang (Qualcomm) has uploaded r01.
Based on documents handling discussion, r01 has merged S2-2205916, S2-2206014, S2-2206905, and S2-2206482, serving as the baseline of discussion on KI#2 conclusions.
Marco (Huawei comments r01.
Zhenhua (vivo) comments on Marco's comments
Yetong(Inspur) comments on r02
Zhenhua (vivo) provides r02
Zhenhua (vivo) replies
Jianning (Xiaomi) provide comment and provide r03
marco (Huawei) provide comment and provide r04
Zhenhua (vivo) provides r05
Saad (Interdigital) comments on r04
Kefeng Zhang (Qualcomm) provides commenst and proposes to note this pCR.
Zhenhua (vivo) replise to Kefeng Zhang (Qualcomm)
Pallab (Nokia) comments on r05
Marco (Huawei) agrees with Pallab's (Nokia) comments on r05
Zhenhua (vivo) and Kefeng Zhang (Qualcomm) subject to 6014 with title 'LS on authentication and authorization for PINE' which is 6488. (to be checked if in meeting report since ask to note probably wrong pCR)
Marco (Huawei) provide r06
Zhenhua (vivo) answers
Pallab (Nokia) provides r07 based on r06
Saad (Interdigital) does not agree with r07
Kefeng Zhang (Qualcomm) provides comments to Saad (Interdigital)
Qian (Ericsson) provides r08
Zhenhua (vivo) provides r09
Jianning (Xiaomi) provide r10
Boren (OPPO) comments.
Zhenhua (vivo) provides r11
Pallab (Nokia) provides comments
Zhenhua (vivo) provides r12
Pallab (Nokia) OK with r12
Jianning (Xiaomi) provide r13, just removing the Editor's note
==== 9.X, 10.X Revisions Deadline ====
Pallab (Nokia) OK to approve r13
Qian (Ericsson) is OK to go with r13
Jianning (Xiaomi) is ok with r13
Kefeng Zhang (Qualcomm) is ok with r13.
Boren (OPPO) is fine with r13.
Marco (Huawei) OK with r13 and objects r00-r05
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207461 P-CR Approval 23.700-88: KI #2, Interim conclusions proposal Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2206014r13, merging and S2-2206905. Approved Approved
9.16 S2-2206905 P-CR Approval 23.700-88: PCR_5G_PIN- conclusion for KI#2 Xiaomi Rel-18 Merged into S2-2207461 Zhenhua (vivo) proposes to merge this paper into S2-2206014
Jianning (Xiaomi) agrees to merge this paper into S2-2206014
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.16 - - - Evaluations and conclusions on KI#3 - - Docs:=4 -
9.16 S2-2206015 P-CR Approval 23.700-88: KI #3, Interim conclusions proposal Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Merged into S2-2207462 Zhenhua (vivo) proposes to merge this paper into S2-2206906
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.16 S2-2205743 P-CR Approval 23.700-88: Evaluation on the solutions of KI#3 Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.16 S2-2206906 P-CR Approval 23.700-88: PCR_5G_PIN- conclusion for KI#3 Xiaomi Rel-18 r16 agreed. Revised to S2-2207462, merging and S2-2206015 Jianning (Xiaomi) provides r01 by merging the S2-2206015, S2-2206483, S2-2206906, and S2-2205743 as suggested by Rapporteur
Zhenhua (vivo) provides r02
Marco (Huawei) provides r03 and asks questions
Zhenhua (vivo) cannot accept r03 and provides r04
Pallab (Nokia) provides comments.
Marco (Huawei) can not accept r04
Jianning (Xiaomi) provide r06 on top of Kefeng(Qualcomm)'s version.
Jianning (Xiaomi) provides r05
Jianning (Xiaomi) replies to Pallab (Nokia)
Jianning (Xiaomi) provides comment to Zhenhua (vivo)
Kefeng Zhang (Qualcomm) provides r05 with further comments.
Zhenhua (vivo) replies.
Pallab (Nokia) provides r08. Objects to all other previous revisions
Zhenhua (vivo) provides r07.
Zhenhua (vivo) asks questions to Pallab (Nokia)
Zhenhua (vivo) provides r09
Kefeng Zhang (Qualcomm) is not OK with r09 and provides comments.
Zhenhua (vivo) replise to Kefeng Zhang (Qualcomm)
Marco (Huawei) object r09
Saad (Interdigital) agrees with Vivo and supports r09
Zhenhua (vivo) replies to Marco (Huawei)
Zhenhua (vivo) provides r10 and replies to Marco (Huawei)
Qian (Ericsson) comments and provides r11
Zhenhua (vivo) provides r12
Jianning (Xiaomi) provide r13
Zhenhua (vivo) asks questions to Jianning (Xiaomi) and provides r14
Kefeng Zhang (Qualcomm) provides comments to bullet 9a in r14.
Zhenhua (vivo) replies to Kefeng Zhang (Qualcomm)
Pallab (Nokia) responds to Zhenhua (vivo)
Zhenhua (vivo) replise to Pallab (Nokia)
Pallab (Nokia) comments on r14
Jianning (Xiaomi) replies to Zhenhua (vivo) on r14
Zhenhua (vivo) replies to Jianning (Xiaomi)
Zhenhua (vivo) answers to Pallab (Nokia)
Pallab (Nokia) responds to Zhenhua (vivo). Believes that 9a is not clear and needs more justification
Zhenhua (vivo) replies to Pallab (Nokia) and provides r15
Marco (Huawei) provides r16
Marco (Huawei) replies to Zhenhua (vivo) on bullet 9a
==== 9.X, 10.X Revisions Deadline ====
Jianning (Xiaomi) can live with r16
Pallab (Nokia) also OK to approve r16
Qian (Ericsson) is OK with r16
Boren (OPPO) prefers r15, can live with r16
Marco (Huawei) ok R16, objects r00-r02, r04, r09 & r11
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207462 P-CR Approval 23.700-88: PCR_5G_PIN- conclusion for KI#3 Xiaomi Rel-18 Revision of S2-2206906r16, merging and S2-2206015. Approved Approved
9.16 - - - Evaluations and conclusions on KI#4 - - Docs:=5 -
9.16 S2-2205744 P-CR Approval 23.700-88: Conclusion on the solutions of KI#4 Huawei, HiSilicon Rel-18 r14 agreed. Revised to S2-2207463, merging and S2-2206249 Marco (Huawei) provides r01 to merge conclusion part of S2-2205744, S2-2206249, S2-2206484, S2-2206016, and S2-2205745
Zhenhua (vivo) provides r02
Jianning (Xiaomi) provides comment
Zhenhua (vivo) answers to Jianning (Xiaomi)
Kefeng Zhang (Qualcomm) provides r03.
Macro (Huawei) provides r04 and comments
Zhenhua (vivo) answers
Pallab (Nokia) comments and provided r05
Zhenhua (vivo) asks questions to Pallab (Nokia)
Pallab (Nokia) responds to Zhenhua (vivo)
Tyler (OTD) comments.
Pallab (Nokia) provides r06 on top of r05.
Zhenhua (vivo) comments
Zhenhua (vivo) further comments
Kefeng Zhang (Qualcomm) is not OK with r05 and r06,
Qualcomm provides r07.
Zhenhua (vivo) provides r08 based on r07
Jianning (Xiaomi) provide r09 based on r08
Zhenhua (vivo) replies to Jianning (Xiaomi) and provides r10
Pallab (Nokia) comments and have some concerns with the conclusions
Zhenhua (vivo) provides r11
Kefeng Zhang (Qualcomm) is not OK with r11.
Pallab (Nokia) OK with r11 and proposes the work on the ENs in the next meeting
Zhenhua (vivo) ask Kefeng (Qualcomm) to reconsider the position
Boren (Boren) asks questions.
Kefeng Zhang (Qualcomm) provides comments.
Zhenhua (vivo) asks the way forward
Marco (Huawei) comments on QoS parameters provided by AF
Qian (Ericsson) provides comments
Marco (Huawei) comments on r11 bullet 2.
Boren (OPPO) comments on r11 bullet 2.
Zhenhua (vivo) provides r12
Kefeng Zhang (Qualcomm) replies Boren (OPPO) comments.
Kefeng Zhang (Qualcomm) provides r13 for the missing changes.
Boren (OPPO) is fine with r13.
Marco (Huawei) provide r14 which correct bullet 9. This change applies to many other provided versions.
Jianning (Xiaomi) provide comment on r14
==== 9.X, 10.X Revisions Deadline ====
Kefeng Zhang (Qualcomm) replies Jianning (Xiaomi) comment.
Pallab (Nokia) objects to r13, r14 which removes EN for bullet 12. Can accept r14 with an additional EN for bullet 12
Jianning (Xiaomi) replies to Kefeng (Qualcomm)
Kefeng (Qualcomm) replies to Jianning (Xiaomi).
Qian (Ericsson) supports the proposal from Pallab (Nokia) that adding the EN on top of r14
Kefeng Zhang (Qualcomm) replies Qian (Ericsson) and Pallab (Nokia).
Zhenhua (vivo) propose for CC#5
Marco (Huawei) ok r14 objects others revisions
Jianning (Xiaomi) provide comment.
Pallab (Nokia) maintains objection to r14.
Marco (Huawei) are neutral on bullet 12. Not see the use cases but we can live with it IN/OUT/EN for it.
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207463 P-CR Approval 23.700-88: Conclusion on the solutions of KI#4 Huawei, HiSilicon Rel-18 Revision of S2-2205744r14, merging and S2-2206249. Approved Approved
9.16 S2-2206249 P-CR Approval 23.700-88: 23.700-88: KI #4, Interim conclusions proposal Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson Rel-18 Merged into S2-2207463 Zhenhua (vivo) proposes to merge this paper into S2-2205744
Marco (Huawei) this document has been merged in S2-2205744 as per rapporteur indication, so it can be discussed in that thread
Pallab (Nokia) is OK to merge this to in S2-2205744 as per rapporteur indication, so it can be discussed in that thread
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.16 S2-2206484 P-CR Approval 23.700-88: Evaluation update and interim conclusions on KI#4 Vivo Rel-18 r01 agreed. Revised to S2-2207464. Zhenhua (vivo) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207464 P-CR Approval 23.700-88: Evaluation update and interim conclusions on KI#4 Vivo Rel-18 Revision of S2-2206484r01. Approved Approved
9.16 - - - Evaluations and conclusions on KI#5 - - Docs:=4 -
9.16 S2-2205917 P-CR Approval 23.700-88: KI#5, Eval and Conclusion: Evaluation of KI#5 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 r02 agreed. Revised to S2-2207465. DongYeon (Samsung) proposes to merge 2205858 and 2206787.
Saad (Interdigital) provides r01
Marco (Huawei) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207465 P-CR Approval 23.700-88: KI#5, Eval and Conclusion: Evaluation of KI#5 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 Revision of S2-2205917r02. Approved Approved
9.16 S2-2206250 P-CR Approval 23.700-88: 23.700-88: KI #5, Interim conclusions proposal Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson Rel-18 r08 agreed. Revised to S2-2207466. Pallab (Nokia) provides r01.
Zhenhua(vivo) provides r02.
Zhenhua (vivo) replies to Saad (Interdigital).
Saad (Interdigital) comments on r02.
Kefeng Zhang (Qualcomm) provides r03
Zhenhua (vivo) answers to Kefeng Zhang (Qualcomm)
Kefeng Zhang (Qualcomm) replies to Zhenhua (vivo).
Pallab (Nokia) comments
Jianning (Xiaomi) provide comments
Zhenhua (vivo) provides r04
Qian (Ericsson) provides comments.
Zhenhua (vivo) replies to Qian (Ericsson)
Jianning (Xiaomi) provide r05
Zhenhua (vivo) provides r06
Pallab (Nokia) comments and provides r07
Jianning (Xiaomi) provide comment on r07
Zhenhua (vivo) replies to Jianning (Xiaomi)
Serge (T-Mobile USA) comments, agrees with vivo and is OK with r07
Yishan (Huawei) provides r08
==== 9.X, 10.X Revisions Deadline ====
Jianning (Xiaomi) replies to Serge (T-Mobile) and Zhenhua (vivo)
Jianning (Xiaomi) replies to Yishan (Huawei)
Yishan (Huawei) replies to Jianning (Xiaomi)
Qian (Ericsson) is ok r08
Marco (Huawei) ok with r08 and objects any other versions
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207466 P-CR Approval 23.700-88: 23.700-88: KI #5, Interim conclusions proposal Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson Rel-18 Revision of S2-2206250r08. Approved Approved
9.16 - - - Evaluations and conclusions on KI#6 - - Docs:=5 -
9.16 S2-2205658 P-CR Approval 23.700-88: KI#6, Conclusion Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207468 Zhenhua (vivo) proposes to merge this paper into S2-2206486
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.16 S2-2205918 P-CR Approval 23.700-88: KI#6, Eval and Conclusion: Evaluation of KI#6 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 r02 agreed. Revised to S2-2207467. Saad (Interdigital) provides r01
Zhenhua (vivo) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207467 P-CR Approval 23.700-88: KI#6, Eval and Conclusion: Evaluation of KI#6 Solutions and Partial Conclusion Text InterDigital Inc. Rel-18 Revision of S2-2205918r02. Approved Approved
9.16 S2-2206486 P-CR Approval 23.700-88: Interim conclusions on KI#6 Vivo Rel-18 r05 agreed. Revised to S2-2207468, merging and S2-2205658 Zhenhua (vivo) provides r01.
Qian (Ericsson) provides r02.
Kefeng Zhang (Qualcomm) provides r03.
Marco (Qualcomm) provides r03 and comments
Zhenhua (vivo) object r03
Marco (Huawei) answers to Zhenhua (vivo) (probably object r04)
Errata corrige: Marco (Huawei) provides r04 and comments
Zhenhua (vivo) replies to Marco (Huawei)
Jianning (Xiaomi) provide r05
Zhenhua (vivo) provides r06
Pallab (Nokia) comments and provides r07
Qian (Ericsson) comments that there seems overlapping contents among conclusions in this paper and 6906 and 5744,
Qian (Ericsson) comments that there seems overlapping contents among conclusions in this paper and 6486 and 5744,
Sudeep (Apple) seeks clarification on r07.
Pallab (Nokia) responds to Sudeep (Apple)
==== 9.X, 10.X Revisions Deadline ====
Qian (Ericsson) comments and is ok with r07
Marco (Huawei) object r07, ok with r06, r05 & r04, objects r00-r03
Jianning (Xiaomi) propose to go r05, leaving the parameters for further discussion in next meeting.
Pallab (Nokia) can accept r07, r05. Objects to all other revisions
==== 9.X, 10.X Final Deadline ====
Kefeng Zhang (Qualcomm) is OK with r07, r06. Objects to all other revisions
Revised
9.16 S2-2207468 P-CR Approval 23.700-88: Interim conclusions on KI#6 Vivo Rel-18 Revision of S2-2206486r05, merging and S2-2205658. Approved Approved
9.16 - - - Evaluations and conclusions on KI#7 - - Docs:=3 -
9.16 S2-2205660 P-CR Approval 23.700-88: KI#7, Conclusion Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell Rel-18 Noted Saad (Interdigital) has concerns with the current conclusion text
Qian (Ericsson) provides r01 to merge in 6487 and comments
Jianning (Xiaomi) shares the view with Saad(InterDigital), and provide more comments
Zhenhua (vivo) provides r02
Jianning (Xiaomi) provide r02
Yishan (Huawei) provide r03
==== 9.X, 10.X Revisions Deadline ====
Pallab (Nokia) objects to r03
Yishan (Huawei) cannot understand the comment from Pallab (Nokia) and ask for withdrawing the objection.
Jianning (Xiaomi) provide r04 based on r03, ask for CC#4 if possible
Qian (Ericsson) provides comments and propose to go with r02
Pallab (Nokia) responds to Yishan (Huawei) and proposes to go with r02
Jianning (Xiaomi) is ok with r02 or r03, but only with an EN 'Editor's note: whether PIN AF, or PEMC or 5GC NF is responsible for allocation of the PIN related identifiers depends on the final conclusion of Key Issue #1' or r04 after revision deadline if possible
Boren (OPPO) recommends to go with r03 along with the EN proposed by Jianning (Xiaomi).
Marco (Huawei) objects r00 & r01. Objects to r04 and addition of the EN since contradicts bullet 1. Since we have to discuss the rest of conclusion, we can keep only bullet 1)
Jianning (Xiaomi) objects r00, r01. But can live with r02 or 03 with Editor's note as proposed.

we cannot accept the current conclusion text in bullet 1) without the EN, since whether specifical AF or 5GC NF is used to support the PIN management is not decided yet.
Marco (Huawei) comments that EN in r03 refers to bullet 2) in r04 submitted after deadline changed to address bullet 1). So we can NOTE the document and discuss again, since all FFS.
==== 9.X, 10.X Final Deadline ====
Noted
9.16 S2-2206487 P-CR Approval 23.700-88: Interim conclusions on KI#7 Vivo Rel-18 r02 agreed. Revised to S2-2207469. Zhenhua (vivo) provides r01.
Marco (Huawei) provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.16 S2-2207469 P-CR Approval 23.700-88: Interim conclusions on KI#7 Vivo Rel-18 Revision of S2-2206487r02. Approved Approved
9.16 - - - LS Out - - Docs:=1 -
9.16 S2-2206488 LS OUT Approval [DRAFT] LS on authentication and authorization for PINE vivo Noted Pallab (Nokia) points out that the earlier discussion was with wrong Tdcon number in the subject. Comments may not have been captured in Chair's notes.
Marco (Huawei) object to this LS. Since the content does not reflect the discussion on conclusion and proposed Way out.
Jianning (Xiaomi) provides comment
Kefeng Zhang (Qualcomm) provides commenst and proposes to note this pCR.
Pallab (Nokia) also thinks an LS OUT is not needed
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.16 - - - Documents exceeding TU Budget - - Docs:=15 -
9.16 S2-2206161 P-CR Approval 23.700-88: KI #3, Update solution #8 for management of PIN and PIN Elements Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2205741 P-CR Approval 23.700-88: KI#3, sol#12: Update on Solution#12 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206162 P-CR Approval 23.700-88: KI #3, Update solution#9 for PIN management and PINE management Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2205745 P-CR Approval 23.700-88: Evaluation on the solutions of KI#4 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206908 P-CR Approval 23.700-88: PCR_5G_PIN- update solution#15 Xiaomi Rel-18 Not Handled Jianning (Xiaomi) proposes to merge this doc into S2-2205988
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206907 P-CR Approval 23.700-88: PCR_5G_PIN- alternative architecture option abstracted from existing solutions Xiaomi Rel-18 Not Handled Jianning (Xiaomi) proposes to merge this doc into S2-2206903
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206904 P-CR Approval 23.700-88: PCR_5G_PIN- update evaluation for solution#9#15#27 Xiaomi Rel-18 Not Handled Jianning (Xiaomi) proposes to merge this doc into S2-2205916
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2205657 P-CR Approval 23.700-88: KI#6, Evaluation Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2205659 P-CR Approval 23.700-88: KI#7, Evaluation Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2205989 P-CR Approval 23.700-88: KI#2, Evaluation: further summary of solutions related to KI#2 OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206016 P-CR Approval 23.700-88: KI #4, Interim conclusions on PINE - PEGC delay budget consideration Qualcomm Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206482 P-CR Approval 23.700-88: Evaluation update and interim conclusions on KI#2 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206483 P-CR Approval 23.700-88: Evaluation update and interim conclusions on KI#3 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206485 P-CR Approval 23.700-88: Evaluation update and interim conclusions on KI#5 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.16 S2-2206479 P-CR Approval 23.700-88: Update terms and abbreviations Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.17 - - - Study on evolution of IMS multimedia telephony service (FS_NG_RTC) - - Docs:=51 -
9.17 - - - General issues - - Docs:=3 -
9.17 S2-2205778 LS OUT Approval [DRAFT] LS on how to support IMS as part of a network slice in Rel-18 China Mobile Rel-18 Noted Kefeng Zhang (Qualcomm) comments and proposes to note the CR.
Ashok (Samsung) agrees with Kefeng Zhang (Qualcomm) and proposes to note the paper.
Yi (China Mobile) replies and calrifies CT1 eIMS5G2 does not address the objective.
Rainer (Nokia) does not see a need for the LS and proposes to note.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2208094 LS OUT Approval [DRAFT] LS on AR telephony communication media negotiation Huawei Created at CC#2. CC#4: r02 proposed. Revised to S2-2207882. Mu (Huawei) prefer to use the original version and offers a r02.
Rainer (Nokia) replies and prefers r01.
Mu (Huawei) clarifies
==== 9.X, 10.X Revisions Deadline ====
Mu (Huawei) propose to approve r02
Rainer (Nokia) proposes to approve r01 and bring this up in CC#4 or CC#5.
Mu (Huawei) agrees to bring this up in CC
Yi (China Mobile) comments.
Mu (Huawei) replies
Rainer (Nokia) would be ok with this text.
Revised
9.17 S2-2207882 LS OUT Approval [DRAFT] LS on AR telephony communication media negotiation Huawei - Revision of S2-2208094r02. Approved Approved
9.17 - - - KI#1: Solution updates - - Docs:=10 -
9.17 S2-2205521 P-CR Approval 23.700-87: KI#1, 4: Update to solution 16 - MRF Ericsson Rel-18 r04 agreed. Revised to S2-2207102. James Jin (vivo) provides comments.
Yi (China Mobile) comments.
Hao (ZTE) responds to George (Ericsson).
George (Ericsson) provides response
Hao (ZTE) asks for clarification.
Ashok (Samsung) comments
George (Ericsson) provides r01
Rainer (Nokia) asks for clarification.
George (Ericsson) provides responses inline
George (Ericsson) provides r02 to show that DCAR can be outside the DCSF
Chris Joul (TMUS) replies to Samsung
Chris Joul (TMUS) replies to James Jin
Yi (China Mobile) further comments.
George (Ericsson) provides r03
Yi (China Mobile) asks why IF1 is removed.
George (Ericsson) provides r04. A mistake on my part. Added it
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207102 P-CR Approval 23.700-87: KI#1, 4: Update to solution 16 - MRF Ericsson Rel-18 Revision of S2-2205521r04. Approved Approved
9.17 S2-2205522 P-CR Approval 23.700-87: KI#1, 4: Update to solution 16 Ericsson Rel-18 r01 agreed. Revised to S2-2207103. Mu (Huawei) comments
George (Ericsson) provides responses in line
Yi (China Mobile) provides comments.
Ashok (Samsung) comments
Hao (ZTE) asks for clarification.
George (Ericsson) provides comments inline
Hao (ZTE) responds.
Hao (ZTE) provides further comment.
George (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207103 P-CR Approval 23.700-87: KI#1, 4: Update to solution 16 Ericsson Rel-18 Revision of S2-2205522r01. Approved Approved
9.17 S2-2206176 P-CR Approval 23.700-87: KI #1, Sol #1, Resolve EN Regarding Subscription from DC Control Function to IMS AS ZTE Rel-18 Noted Hao (ZTE) responds.
Yi (China Mobile) comments.
George Foti (Ericsson) provides comments
Ashok (Samsung) comments
George (Ericsson) provides comments
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) responds why the pCR is to be noted
Hao (ZTE) proposes to approve the original version.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206177 P-CR Approval 23.700-87: KI #1, Sol #6, Clarification on Procedures in Clause 6.6.3 ZTE Rel-18 r03 agreed. Revised to S2-2207104 (withdrawn). Noted George Foti (Ericsson) provides comments
Hao (ZTE) responds to George (Ericsson) and provides r01.
Yi (China Mobile) provides r02.
George (Ericsson) provides comments
Hao (ZTE) provides r03.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ericsson objects to all revisions
Hao (ZTE) asks George (Ericsson) to reconsider approving r03.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2207104 P-CR Approval 23.700-87: KI #1, Sol #6, Clarification on Procedures in Clause 6.6.3 ZTE Rel-18 Revision of S2-2206177r03. WITHDRAWN Withdrawn
9.17 S2-2206386 P-CR Approval 23.700-87: 23.700-87: KI #1: Update to clarify how to negotiate the data channel applications used in the call Vivo Rel-18 Noted James Jin (vivo) replies to questions from George Foti (Ericsson) and replay that the DC application selected by the peer UE is pushed to the UE.
Yi (China Mobile) supports the idea and ask question for clarification.
George Foti (Ericsson) proposes to note the CR. Additional comments below.
Ashok (Samsung) comments
Mu (Huawei) comments
James Jin (vivo) replies to questions from Ashok (Samsung) and Mu(Huawei)
Hao (ZTE) comments.
George (Ericsson) provides comments
James Jin (vivo) replies to questions from Hao (ZTE) and George Foti (Ericsson).
Yi (China Mobile) asks if this solution does not need standardization in 3GPP.
Yi (China Mobile) further comments.
James Jin (vivo) replies to George Foti (Ericsson).
George (Ericsson) provides response
James Jin (vivo) replies to questions from George Foti (Ericsson).
George (Ericsson) provides responses in line
James Jin (vivo) replies to questions from Yi (China Mobile) .
Rainer (Nokia) provides r01.
James Jin (vivo) replies to Rainer (Nokia) can accept r01.
George (Ericsson) replies
James Jin (vivo) replies to George (Ericsson)
Kefeng Zhang (Qualcomm) asks questions for clarification.
James Jin (vivo) replies Kefeng Zhang (Qualcomm)
James Jin (vivo) replies George (Ericsson)
Rainer (Nokia) replies.
James Jin (vivo) replies to Rainer (Nokia).
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) NOT ok with all revisions including the original
James Jin (vivo) replies to George (Ericsson) and suggest to accept r01
Rainer (Nokia) proposes to note.
James Jin (vivo) replies to Rainer (Nokia) and suggest to accept r01
Yi (China Mobile) comments and is fine with r01.
George (Ericsson) responds. This is different than 6000. This is about a protocol between the UE and DCMF. So we are still Not Ok with this.
James Jin (vivo) replies to Yi (China Mobile) and George (Ericsson)
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206797 P-CR Approval 23.700-87: KI#1, Sol #7 update: Reference architecture to support Data Channel usage in IMS Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207105. Yi (China Mobile) comments that updates in this contribution is not aligned with the interim conclusion.
James Jin (vivo) provides comments
George Foti (Ericsson) provides comments
Ashok (Samsung) comments
Mu (Huawei) clarifies.
Rainer (Nokia) replies.
Mu (Huawei) comments.
George (Ericsson) provides responses.
Chris Joul (TMUS) provides comments
Yi (China Mobile) comments.
Yi (China Mobile) replies to Rainer.
Rainer (Nokia) provides r01.
Mu (Huawei) responds to James.
James Jin (vivo) responds to Mu
Rainer (Nokia) comments.
Mu (Huawei) replies
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ok with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207105 P-CR Approval 23.700-87: KI#1, Sol #7 update: Reference architecture to support Data Channel usage in IMS Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206797r01. Approved Approved
9.17 - - - KI#1: New solutions - - Docs:=9 -
9.17 S2-2205519 P-CR Approval 23.700-87: KI#10: New Solution for Mid Call IMS DC Session setup Ericsson Rel-18 Noted Mu (Huawei) comments
Kefeng Zhang (Qualcomm) comments and proposes to note the CR.
Yi (China Mobile) comments.
George (Ericsson) provides comments
Mu (Huawei) replies, I have replied in thread 5523, it is defined in NG.129.
Mu (Huawei) replies to George
Hao (ZTE) asks for clarification.
George (Ericsson) replies
Mu (Huawei) further replies to George
George (Ericsson) provides comments inline
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) asks what question is not answered.
Hao (ZTE) proposes to Note this pCR.
Hao (ZTE) responds.
George (Ericsson) provides response
Mu (Huawei) asks a question
George (Ericsson) I did respond. I said this is DC content intended for a UE. I gave the use case, and why this will not work unless done this way. Please see the ither email. This has nothing to do with network support.
Hao (ZTE) replies to George (Ericsson) that your response is not for my question, and you just said you didn't even see my question.
Yi (China Mobile) still have concern on introducing a new indication.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2205772 P-CR Approval 23.700-87: KI#1, New solution: Merged solution for DC architecture and procedures China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 r12 agreed. Revised to S2-2207198. George Foti (Ericsson) provides comments
Yi (China Mobile) replies to George.
Rainer (Nokia) comments, does not accept two options for the media function.
Rainer (Nokia) comments, proposes a change.
George (Ericsson) provides responses inline.
George (Ericsson) provides comments
George (Ericsson) provides comments. Please look at 5521r02
Chris Joul (TMUS) Provides comments and revision 01
Mu (Huawei) does not agree DCMF is a kind of MRF and reject r01.
Rainer (Nokia) replies.
Rainer (Nokia) does not agree with r01, provides r02.
Yi (China Mobile) comments and provides r03.
George (Ericsson) provides r05
Rainer (Nokia) provides r04.
Chris Joul (TMUS) Provides r06 and comments
Hao (ZTE) comments.
Mu (Huawei) replies to Kenny and Hao
Kefeng (Qualcomm) replies Hao (ZTE).
Hao (ZTE) responds to Kefeng (Qualcomm).
Kefeng Zhang (Qualcomm) provides comments and questions for clarification.
Kefeng Zhang (Qualcomm) replies to Mu (Huawei) and Hao (ZTE).
Mu (Huawei) comments
Rainer (Nokia) comments, provides r07.
Mu (Huawei) comments. 6318 defines the operations for 5772.
George (Ericsson) provides r08
George (Ericsson) provides r09
Yi (China Mobile) comments on removal of DC4.
Yi (China Mobile) ask question for interaction between IMS AS and DCSF.
George (Ericsson) replies
Kefeng Zhang (Qualcomm) Yi (China Mobile) for interaction between IMS AS and DCSF.
Yi (China Mobile) comments.
Yi (China Mobile) replies to Kenny.
Rainer (Nokia) comments.
Mu (Huawei) ask for clarification
George (Ericsson) replies in line
Mu (Huawei) comments, IMS AS does not store customer info. That is local configuration that I suggested.
George (Ericsson) nothing is stored. Please see my answer in another email exchange.
Mu (Huawei) replies, please carefully check my previous comment.
George (Ericsson) provides reply
Mu (Huawei) provides further comments
George (Ericsson) responds.
Yi (China Mobile) provides r10.
Kefeng Zhang (Qualcomm) provides comments to r10.
Yi (China Mobile) replies to George and provides r11.
George (Ericsson) Can U add my EN. It is clearer what the options are.
Yi (China Mobile) provides r12 with another EN option.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) accepts ONLY R12
Mu (Huawei) propose to approve r11.
Rainer (Nokia) is ok with r12.
Yi (China Mobile) is fine with r11 and r12.
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207198 P-CR Approval 23.700-87: KI#1, New solution: Merged solution for DC architecture and procedures China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 Revision of S2-2205772r12. Approved Approved
9.17 S2-2205775 P-CR Approval 23.700-87: KI#1, New solution: Interworking between a DCMTSI client and an MTSI client CMCC, Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207106. George Foti (Ericsson) provides comments
Hao (ZTE) asks for clarification.
Yi (China Mobile) replies to Hao and George and provides r01.
George (Ericsson) wrong link
James Jin (vivo) provides comments.
Hao (ZTE) comments on r02.
James Jin (vivo) provide r02
Yi (China Mobile) corrects the link again.
Yi (China Mobile) corrects the link.
James Jin (vivo) reply comments from Hao (ZTE) on r02.
Hao (ZTE) comments.
James Jin (vivo) reply comments from Hao (ZTE).
Hao (ZTE) responds to James.
Mu (Huawei) replies
Kefeng Zhang (Qualcomm) provides comments, and provides r03.
Yi (China Mobile) provides r04 based on comments.
George (Ericsson) provides comments
George (Ericsson) provides comments inline
Mu (Huawei) replies inline
George (Ericsson) asks another question.
Mu (Huawei) answers inline
Rainer (Nokia) asks for clarification.
Mu (Huawei) comments
Yi (China Mobile) replies to Rainer.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) can live with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207106 P-CR Approval 23.700-87: KI#1, New solution: Interworking between a DCMTSI client and an MTSI client CMCC, Huawei, HiSilicon Rel-18 Revision of S2-2205775r04. Approved Approved
9.17 S2-2206000 P-CR Approval 23.700-87: KI #1, New Sol: Application Data Channel establishment based on awareness of application ID Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2207107. George Foti (Ericsson) proposes to note the CR. Please see additional comments
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson)'s comments with a example
Mu (Huawei) comments, current GSMA discussion does not decide how both UEs choose the same APP.
James Jin (vivo) provides comments.
Yi (China Mobile) comments.
Mu (Huawei) replies to Yi's questions
Kefeng Zhang (Qualcomm) replies Yi (China Mobile) and Mu (Huawei)
Kefeng Zhang (Qualcomm) replies James Jin (vivo).
Rainer (Nokia) asks for clarification.
Kefeng Zhang (Qualcomm) replies Rainer (Nokia).
George (Ericsson) provides response
Kefeng Zhang (Qualcomm) replies to George (Ericsson) .
George (Ericsson) replies
Rainer (Nokia) comments.
Kefeng Zhang (Qualcomm) replies George (Ericsson)
Kefeng Zhang (Qualcomm) replies Rainer (Nokia) comments.
Kefeng Zhang (Qualcomm) provides r01.
Kefeng Zhang (Qualcomm) replies James Jin (vivo) and provides r02.
Rainer (Nokia) provides r03.
Kefeng Zhang (Qualcomm) replies Yi (China Mobile) comments and provides r04.
Kefeng Zhang (Qualcomm) is OK with r03.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ericsson OK with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207107 P-CR Approval 23.700-87: KI #1, New Sol: Application Data Channel establishment based on awareness of application ID Qualcomm Incorporated Rel-18 Revision of S2-2206000r04. Approved Approved
9.17 S2-2206002 P-CR Approval 23.700-87: KI #1, new solution: UE capabilities detection for IMS DC applications Qualcomm Incorporated Rel-18 Noted George Foti (Ericsson) proposes to note the pCR. This is not needed. See comments on 6000
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson).
Yi (China Mobile) comments.
Kefeng Zhang (Qualcomm) replies Yi (China Mobile)'s comments.
James Jin (vivo) provides comments.
George (Ericsson) provides comments
Kefeng Zhang (Qualcomm) replies to James Jin (vivo).
Kefeng Zhang (Qualcomm) replies George (Ericsson).
James Jin (vivo) replies that it is ok for me.
Kefeng Zhang (Qualcomm) replies James Jin (vivo) and provides r01.
Mu (Huawei) provides comments
Kefeng Zhang (Qualcomm) replies George (Ericsson) and James Jin (vivo).
James Jin (vivo) provides responds. we can collect the view of other delegates
George (Ericsson) provides response. Not in SA2 specs.
James Jin (vivo) provides responds. We can talk about it in TS stage, I think at least it can be specified in 3GPP.
George (Ericsson) provides responds. In what TS do U want to add that.
George (Ericsson) provides comments. More important we need to send an LS to SA4.
Rainer (Nokia) comments.
Kefeng Zhang replies to George (Ericsson) and Rainer (Nokia).
Kefeng Zhang (Qualcomm) replies Yi (China Mobile) comments.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ok with r01
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206318 P-CR Approval 23.700-87: KI#1, New Sol, Service Operations used in IMS Data Channel Architecture Huawei, HiSilicon, China Mobile Rel-18 Noted Kefeng Zhang (Qualcomm) comments the CR.
George Foti (Ericsson) objects to the pCR. Please see additional comments.
Yi (China Mobile) comments.
George (Ericsson) provides comments
Mu (Huawei) provides r01
George (Ericsson) provides comments.
George (Ericsson) responds
Mu (Huawei) replies
Mu (Huawei) replies inline
Yi (China Mobile) replies to George.
George (Ericsson) provides comments inline
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ericsson objects to all revisions including the original.
Mu (Huawei) replies to George and propose to approve r01
Yi (China Mobile) propose to agree r01.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 - - - KI#2: Solution updates - - Docs:=3 -
9.17 S2-2206314 P-CR Approval 23.700-87: KI#2, Sol#9 Update Supporting AR Communication Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207108, merging and S2-2206387 Mu (Huawei) replies.
George Foti (Ericsson) provides comments
James Jin (vivo) provides r01 which merges the S2-2206387 to S2-2206314.
George (Ericsson) provides comments. Please see inline
Mu (Huawei) replies and provide r02
James Jin (vivo) provides comments.
Mu (Huawei) provide r03, and propose to send LS to SA4.
Rainer (Nokia) provides r01 of the LS.
Mu (Huawei) replies to George.
Rainer (Nokia) comments.
Mu (Huawei) provides r04
George (Ericsson) proposes to postpone this.
Mu (Huawei) provides comments
==== 9.X, 10.X Revisions Deadline ====
Mu (Huawei) propose to approve r04
Mu (Huawei) propose to approve r04 with the following EN ' Editor's Note: the services and operations need to align with KI#1'
George (Ericsson) Not Ok with r04. If U want the architecture to progress please remove all section 6.9.1.4.
Mu (Huawei) is ok to approve r04 with removal of section 6.9.1.4'
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207108 P-CR Approval 23.700-87: KI#2, Sol#9 Update Supporting AR Communication Huawei, HiSilicon Rel-18 Revision of S2-2206314r04, merging and S2-2206387. Approved Approved
9.17 S2-2206387 P-CR Approval 23.700-87: 23.700-87: KI #2: Update to Sol#9 to clarify how to support AR split rendering requested by the UE Vivo Rel-18 Merged into S2-2207108 James Jin (vivo) confirms this paper is merged into S2-2206314.
George Foti (Ericsson) Please merge with 6314 . Additional comments below.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.17 - - - KI#3: Solution updates - - Docs:=6 -
9.17 S2-2205520 P-CR Approval 23.700-87: KI#3: Update to Solution 13 Ericsson Rel-18 r05 agreed. Revised to S2-2207109. Mu (Huawei) comments
Ashok (Samsung) does not agree with the Solution 13 paper and thinks many scenarios need to be addressed which comes with the proposal of replacing HSS with EDS
Mu (Huawei) replies
Kefeng Zhang (Qualcomm) provides concern on the end to end security mechanism of Sol #13.
George (Ericsson) provides response
Ashok (Samsung) responds to Mu
Mu (Huawei) responds to Ashok
Mu (Huawei) provides r01
George (Ericsson) not OK with r01.
Mu (Huawei) provide comments
George (Ericsson) provides comments
Mu (Huawei) provide further comments
Mu (Huawei) provides r02 based on the comments
George (Ericsson) provides r03
Mu (Huawei) replies to George
Mu (Huawei) provides r04 based on the comments
George (Ericsson) provides comments. See inline
George (Ericsson) replies. The questions sent in the previous email are not addressed..................................
Mu (Huawei) provide inline comment
George (Ericsson) provides comments inline
Mu(Huawei) provides comments inline
Mu(Huawei) replies
George (Ericsson) additional questions inline
Mu (Huawei) respond inline.
Mu (Huawei) answers inline.
George (Ericsson) asks question
Mu (Huawei) clarifies
Rainer (Nokia) comments.
Mu (Huawei) provides r05 based on the comments, and replies to Rainer
Ashok (Samsung) comments
Rainer (Nokia) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207109 P-CR Approval 23.700-87: KI#3: Update to Solution 13 Ericsson Rel-18 Revision of S2-2205520r05. Approved Approved
9.17 S2-2206004 P-CR Approval 23.700-87: KI #3, update of solution #12 Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2207110. George Foti (Ericsson) provides comments
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson)'s comments and provides r01.
George (Ericsson) provides comments
Kefeng Zhang (Qualcomm) replies George (Ericsson), provides r03 (please ignore r02).
George (Ericsson) OK with this revision
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207110 P-CR Approval 23.700-87: KI #3, update of solution #12 Qualcomm Incorporated Rel-18 Revision of S2-2206004r03. Approved Approved
9.17 S2-2206793 P-CR Approval 23.700-87: KI#3, Sol #10 update: Support of Third Party specific User Identities in IMS using STIR/SHAKEN Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207111. Rainer (Nokia) provides r01.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) OK with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207111 P-CR Approval 23.700-87: KI#3, Sol #10 update: Support of Third Party specific User Identities in IMS using STIR/SHAKEN Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206793r01. Approved Approved
9.17 - - - KI#4: Solution updates - - Docs:=4 -
9.17 S2-2206315 P-CR Approval 23.700-87: KI#4, Sol#15 Update: Solution to Media Plane SBI Huawei, HiSilicon, China Mobile, Reliance Jio Rel-18 Noted Mu (Huawei) replies
Mu (Huawei) provides comments
George Foti (Ericsson) provides comments
George (Ericsson) provides comments . Please see inline
Mu (Huawei) replies and provide r01
George (Ericsson) provides comments. I am not sure that there is support for this work.
Rainer (Nokia) comments.
Chris Joul (TMUS) provides comments
Mu (Huawei) clarifies the purpose of UMF
George (Ericsson) replies
Chris Joul (TMUS) replies to Huawei
Mu (Huawei) provides further comments
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) proposes to note this pCR
Rainer (Nokia) agrees with George (Ericsson) to note.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206792 DISCUSSION Discussion KI#4, Discussion on existing SBA parameters usable for discovery/selection of IMS media functions T-Mobile USA Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206794 P-CR Approval 23.700-87: KI#4, Update to solution #14 to remove editors note T-Mobile USA Rel-18 r02 agreed. Revised to S2-2207112. Chris Joul (T-Mobile USA) replies to Ericsson
George Foti (Ericsson) provides comments
Chris Joul (T-Mobile USA) provides r01
Rainer (Nokia) comments.
Chris Joul (TMUS) provides r02
James Jin (vivo) provides comments
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) OK with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207112 P-CR Approval 23.700-87: KI#4, Update to solution #14 to remove editors note T-Mobile USA Rel-18 Revision of S2-2206794r02. Approved Approved
9.17 - - - Evaluations and conclusions - - Docs:=15 -
9.17 S2-2205523 P-CR Approval 23.700-87: KI#1: Update to Interim Conclusion on KI #1 Ericsson Rel-18 Noted Mu (Huawei) comments.
Kefeng Zhang (Qualcomm) comments the pCR.
Rainer (Nokia) comments.
George (Ericsson) provides comments
Hao (ZTE) comments.
Mu (Huawei) propose to note this pCR
Yi (China Mobile) comments.
==== 9.X, 10.X Revisions Deadline ====
Mu (Huawei) proposes to Note this pCR.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2205773 P-CR Approval 23.700-87: Evaluation and conclusion of KI#1 China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 r05 agreed. Revised to S2-2207113. George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
George (Ericsson) objects to this revision and previous one. We are not OK with the removal of the option of co-locating DCMF in an MRF. No justification for that.
George (Ericsson) provides comments. See my response on 6790. I address that point clearly.
Rainer (Nokia) replies.
Chris Joul (TMUS) provides comments
Kefeng Zhang (Qualcomm) provides comments to remove the last bullet.
Yi (China Mobile) comments.
Kefeng Zhang (Qualcomm) provides comments and r02.
Yi (China Mobile) provides r03.
Rainer (Nokia) provides r04.
George (Ericsson) replies
Rainer (Nokia) provides r05.
George (Ericsson) OK with r05
Yi (China Mobile) ask question about the editor's note.
George (Ericsson)responds. Send an LS to SA4. There are several LSs to be sent to SA4, and soon. None of them is ready as well.
Yi (China Mobile) provides r06.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ericsson accepts r05 only
Mu (Huawei) propose to approve r06
Rainer (Nokia) prefers r05.
Yi (China Mobile) prefer r06, but can live with r05.
Leo (Deutsche Telekom) supports r05.
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207113 P-CR Approval 23.700-87: Evaluation and conclusion of KI#1 China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 Revision of S2-2205773r05. Approved Approved
9.17 S2-2206178 P-CR Approval 23.700-87: KI#2 Evaluation ZTE Rel-18 r04 agreed. Revised to S2-2207114. Hao (ZTE) provides r01 which merges the evaluation part in S2-2206317.
Mu (Huawei) is ok with r01, and propose to use 6178 as the base for KI#2 evaluation.
George (Ericsson) Provides comment. Can we add a note that SA4 has to provide the media negotiation part for the network rendering option
Hao (ZTE) responds.
George (Ericsson) provides comments
Hao (ZTE) provides r02.
George (Ericsson) provides r03. Just cleaned up the EN
Hao (ZTE) provides r04.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ok with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207114 P-CR Approval 23.700-87: KI#2 Evaluation ZTE Rel-18 Revision of S2-2206178r04. Approved Approved
9.17 S2-2206179 P-CR Approval 23.700-87: KI#2 Conclusion ZTE Rel-18 Merged into S2-2207115 Hao (ZTE) responds to George (Ericsson) and suggests to discuss the comment under thread S2-2206317.
George Foti (Ericsson) provides comments
Hao (ZTE) confirms this paper is merged into S2-2206317.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.17 S2-2206317 P-CR Approval 23.700-87: KI#2: Evaluation and Conclusion Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2207115, merging and S2-2206179 Mu (Huawei) replies
Kefeng Zhang (Qualcomm) comments the CR.
George Foti (Ericsson) provides comments
Hao (ZTE) provides r01 which merges S2-2206179 and removes the evaluation part which is merged into S2-2206178r01.
Mu (Huawei) is ok with r01, and propose to use 6317 as the base for KI#2 conclusion.
George (Ericsson) provides comments
Mu (Huawei) comments
Rainer (Nokia) provides r02.
George (Ericsson) We are not OK with any revision. R02 still leaves network rendering in the picture which in our opinion requires SA5
Mu (Huawei) clarifies that SA5 is charge of network rendering, so it is not making sense to send LS to SA5.
Mu (Huawei) provides r03
Mu (Huawei) provides r04
Hao (ZTE) is fine with the change; please add ZTE as supporting company.
Rainer (Nokia) provides r05.
Rainer (Nokia) replies.
Patrice (Huawei) reminds George (Ericsson) and Rainer (Nokia) about how 3GPP progresses work.
Mu (Huawei) provides r06 and LS to SA4
Rainer (Nokia) provide 8094r01.
Mu (Huawei) comments, let discuss 8094 in the new thread for LS out.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) Ok with r06
Rainer (Nokia) also ok with 6317r06.
Leo (Deutsche Telekom) supports r06
Susana (Vodafone) supports r06
==== 9.X, 10.X Final Deadline ====
Revised
9.17 S2-2207115 P-CR Approval 23.700-87: KI#2: Evaluation and Conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206317r06, merging and S2-2206179. Approved Approved
9.17 S2-2206006 P-CR Approval 23.700-87: KI #3, Conclusions Qualcomm Incorporated Rel-18 Merged into S2-2206790 (noted). Noted George Foti (Ericsson) provides comments
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson) and provides r01.
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson).
George (Ericsson) provides response
Rainer (Nokia) proposes to merge in 6790.
Kefeng (Qualcomm) relies to George (Ericsson) and Rainer (Nokia),
agrees to merge 6006 with 6790.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206316 P-CR Approval 23.700-87: KI#3: Evaluation and conclusion Huawei, HiSilicon Rel-18 Covered by S2-2206789 Chris Joul (T-Mobile USA) Agrees with Ericsson to use 6790 as basis
George Foti (Ericsson) prefers to use 6790 as a basis. Additional comments below.
Rainer (Nokia) also prefers to use 6790 as basis.
Mu (Huawei) agrees to use 6789 and 6790 as basis. Mark 6316 as merged into 6789.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206789 P-CR Approval 23.700-87: KI#3: Evaluation of solutions for support of Third Party specific IDs Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.17 S2-2206790 P-CR Approval 23.700-87: KI#3: Conclusions for support of Third Party specific IDs Nokia, Nokia Shanghai Bell Rel-18 Noted Mu (Huawei) comments
George Foti (Ericsson) provides comments
Kefeng Zhang (Qualcomm) provides comments.
Rainer (Nokia) provides r01.
George (Ericsson) provides comments
Rainer (Nokia) replies.
Ashok (Samsung) comments
Ashok (Samsung) comments that EDS approach based on Solution 13 is not acceptable to us and should not be included in conclusion
Ashok (Samsung) comments and provides r02
Rainer (Nokia) provides r03.
George (Ericsson) replies
Kefeng Zhang (Qualcomm) objects r02, r03, and provides r04.
George (Ericsson) provides comments. We need to state that the signing is done by IMS regardless of where the identities are stored
George (Ericsson) provides comments. EDS is an integral part of the solution Please look at 5520 with specific Editor notes that were never addressed directly
Rainer (Nokia) provides r05.
George (Ericsson) asks question
Kefeng Zhang (Qualcomm) is OK with r05 and relies Rainer (Nokia)'s comments.
Mu (Huawei) provides further comment
Kefeng Zhang (Qualcomm) response to Ashok (Samsung) comments.
Ashok (Samsung) comments and provides r06
George (Ericsson) provides r08
Ashok (Samsung) comments and provides r09
George (Ericsson) asks a question
George (Ericsson) asks another question
George (Ericsson) provides r10
Rainer (Nokia) is ok with r10.
Mu (Huawei) provides r011
George (Ericsson) Not OK with r11. I requested clarification on how this works and until I get a reasonable complete response in 5520 I cant agree to this addition.
Rainer (Nokia) cannot accept r11.
Mu (Huawei) replies to George and Rainer
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) accepts only R10
Mu (Huawei) accepts only R11 and object all other revision.
Rainer (Nokia) is ok with r10, but not with r11.
Leo (Deutsche Telekom) proposes to POSTPONE the PCR and continue discussion next SA2 meeting
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2206799 P-CR Approval 23.700-87: KI#4, Conclusions for IMS discovery and selectionKI#4, Conclusions for IMS discovery and selection T-Mobile USA Rel-18 Noted Chris Joul (TMUS) provides r01
Rainer (Nokia) cannot accept r01 and r00.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2205774 P-CR Approval 23.700-87: Evaluation and conclusion of KI#4 China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 r05 agreed. Revised to S2-2207116 (withdrawn). Noted Mu (Huawei) asks for clarification.
George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
George (Ericsson) is not OK with this revision. Our comments are not fully addressed yet.
Mu (Huawei) comments, UMF requires normative work so it should be included in the conclusion.
Chris Joul (TMUS) provides r02
Rainer (Nokia) does not accept r02.
Mu (Huawei) provide comments.
Rainer (Nokia) replies.
Mu (Huawei) provide further clarification.
Mu (Huawei) ask for clarification.
George (Ericsson) not Ok with r02, and provides comments.
Yi (China Mobile) comments and proposes text change.
Yi (China Mobile) sends the rewording proposal.
George (Ericsson) responds
Yi (China Mobile) provides r03.
Rainer (Nokia) does not accept r03.
Mu (Huawei) provides comment
Mu (Huawei) provides r04 based on comments
Rainer (Nokia) cannot accept r04, provides r05.
Yi (China Mobile) believe UMF is in the scope of the study.
Mu (Huawei) replies to Rainer
George (Ericsson) objects to all revisions and original. MRF has to be out of the picture enhanced or not. Additional comments
George (Ericsson) after reading this again, I can accept r05
Mu (Huawei) provide r06 and can only accept r04 and r06, and objects all other revisions.
Rainer (Nokia) cannot accept r06.
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) accepts r05 only
Mu (Huawei) accept r04 and r06 only, and object all other revision
Yi (China Mobile) propose to add a enitor's note on top of r05.
==== 9.X, 10.X Final Deadline ====
Noted
9.17 S2-2207116 P-CR Approval 23.700-87: Evaluation and conclusion of KI#4 China Mobile, Huawei, Hisilicon, Deutsche Telekom, ZTE Rel-18 Revision of S2-2205774r05. WITHDRAWN Withdrawn
9.17 - - - Documents exceeding TU Budget - - Docs:=1 -
9.17 S2-2206388 P-CR Approval 23.700-87: 23.700-87:update conclusion of KI #1:conclusion on how to do the detail DC capabilities negotiate Vivo Rel-18 Not Handled Kefeng Zhang (Qualcomm) comments and proposes to postponed this conclusion.
James Jin (vivo) replies to questions from George Foti (Ericsson) and explains that it is used to negotiate the DC application can be supported by both UEs, but not one UE.
Mu (Huawei) comments
George Foti (Ericsson) objects to this pCR. provides comments
George Foti (Ericsson) provides comments
Hao (ZTE) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.18 - - - Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) - - Docs:=78 -
9.18 - - - LSs - - Docs:=5 -
9.18 S2-2205420 LS In Action LS from RAN WG1: Reply LS on UE capabilities of MBS RAN WG1 (R1-2205461) Rel-18 Noted LiMeng (Huawei) suggests we mark this document as NOTED.
==== 9.X, 10.X Revisions Deadline ====
Noted
9.18 S2-2205431 LS In Action LS from TSG RAN: Reply LS on UE capabilities for MBS TSG RAN (RP-221861) Rel-18 Noted LiMeng (Huawei) suggests we mark this document as NOTED.
==== 9.X, 10.X Revisions Deadline ====
Noted
9.18 S2-2205607 LS OUT Approval [DRAFT] LS on 5MBS Phase 2 Study Issues and Progress Ericsson Rel-18 Merged into S2-2207470 Robbie (Ericsson) agrees to merge it to S2-2206079
LiMeng (Huawei) suggests to merge this document into S2-2206079.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206079 LS OUT Approval [DRAFT] LS to RAN regarding Rel-18 FS_5MBS_Ph2 progress Huawei, HiSilicon Rel-18 r18 + changes agreed. Revised to S2-2207470, merging and S2-2205607 Thomas (Nokia) provides r01
Fenqin (Huawei) provides r02
Thomas (Nokia) provides r03
zhendong (ZTE) provides r04
LaeYoung (LGE) provides r05.
Fenqin (Huawei) provides r06.
Judy (Ericsson) provides r07
Judy (Ericsson) comments
Hugh (AT&T) provides r08
Haris(Qualcomm) provides r09
Thomas(Nokia) provides r12.
Robbie(Ericsson) asks Thomas(Nokia) for the MOCN solution.
Thomas(Nokia) provides r11.
LaeYoung (LGE) provides r10.
Fenqin(Huawei) provides r13
zhendong (ZTE) provides the comments
Judy (Ericsson) provides r14
Fenqin(Huawei) provides r15
Judy (Ericsson) comments and provide r16
zhendong (ZTE) Q5 looks better.
Fenqin(Huawei) provides r17
Thomas(Nokia) provides r18
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) cannot accept r17/r18 as the added text in Q5 assume certain RAN behavior, explained
Fenqin(Huawei) provides r19 which is after revision deadline.
Judy (Ericsson) is fine with post deadline revision r19
Tao(VC) please Fenqin indicate what is the change over certain version before revision deadline
Fenqin(Huawei) responds that r19== r18 + replacement of Q5 as,
'Q5: When MBS Session is activated and MBS data allowed to be received in RRC_INACTIVE state, is it possible that the RRC_INACTIVE UE receives MBS data without going back to RRC connected state? If possible, when the MBS session is being activated, how is the RRC_INACTIVE UE notified ?

For group paging initiated for IDLE UEs, does RRC_INACTIVE UE respond to such paging?'
Thomas(Nokia) is fine with r19== r18 + replacement of Q5
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207470 LS OUT Approval [DRAFT] LS to RAN regarding Rel-18 FS_5MBS_Ph2 progress Huawei, HiSilicon Rel-18 Revision of S2-2206079r18 + changes, merging and S2-2205607. Approved Approved
9.18 - - - Solutions of KI#1 - - Docs:=19 -
9.18 S2-2205608 P-CR Approval 23.700-47: KI#1, New solution: AF providing list of prioritized UEs when creating multicast MBS Session Ericsson Rel-18 r07 agreed. Revised to S2-2207471. LiMeng (Huawei) asks for clarification
Thomas (Nokia) provides r01
Judy (Ericsson) responds to Thomas (Nokia) and LiMeng (Huawei).
LiMeng (Huawei) comments.
Thomas (Nokia) replies to Judy
Judy (Ericsson) responds to Thomas (Nokia) and LiMeng (Huawei), and provides r02
Haris(Qualcomm) provides comments
Thomas (Nokia) provides r03, objects against r02
Aihua(CMCC) provides r04.
Judy (Ericsson) provides r05 and responds
Haris(Qualcomm) comments
Judy (Ericsson) responds and provides r07
Haris(Qualcomm) provides r06
==== 9.X, 10.X Revisions Deadline ====
Aihua(CMCC) comments on r07, requesting to bring the EN back.
Judy (Ericsson) responds to Aihua
Judy (Ericsson) provids more explanation.
Judy (Ericsson) provides r08 == r07 + resume EN 'Editor's note: Whether it is proper to provide non-relevant UEs' GPSIs to SMF is FFS' as requested by Aihua, in case there is objection of r07 and request a check in CC#4 if needed.
Aihua(CMCC) is fine with r08. Thanks a lot for consideration.
Judy (Ericsson) thanks Aihua for confirmation and clarifies to Tao that we'll go for a revision== r07 + resume EN 'Editor's note: Whether it is proper to provide non-relevant UEs' GPSIs to SMF is FFS'
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207471 P-CR Approval 23.700-47: KI#1, New solution: AF providing list of prioritized UEs when creating multicast MBS Session Ericsson Rel-18 Revision of S2-2205608r07. Approved Approved
9.18 S2-2205925 P-CR Approval 23.700-47: Key issue 1 solution 19 updates Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2207472. Judy (Ericsson) comments
LiMeng (Huawei) suggests to add release procedure to complete the whole call-flow
Fenqin (Huawei) comments
Xiaoyan (CATT) provides r01.
Fenqin (Huawei) provides comments and r03.
Thomas (Nokia) provides r02 and replies to comments
Thomas (Nokia) prefers r02 and comments against r03.
Fenqin (Huawei) provides feedback.
Thomas (Nokia) can live with r03
Judy (Ericsson) provides r04
Thomas(Nokia) can accept r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207472 P-CR Approval 23.700-47: Key issue 1 solution 19 updates Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205925r04. Approved Approved
9.18 S2-2206499 P-CR Approval 23.700-47: KI#1, Sol#18: update to resolve ENs on MBS Session Release for RRC_INACTIVE UE Ericsson Rel-18 r04 + changes agreed. Revised to S2-2207473, merging and S2-2206533 Fenqin (Huawei) proposes r01 to include information from S2-2206533.
Fenqin (Huawei) provides comments
Judy (Ericsson) provides r02
Judy (Ericsson) responds to Fenqin (Huawei)
Fenqin (Huawei) provides r03
Judy (Ericsson) provides r04
Fenqin (Huawei) object r04
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) thanks Fenqin (Huawei) for the proposal and check if a post deadline revision = 'r04 + remove 'CN-initiated' in step 7 + resume EN in step 9' is agreeable.
Fenqin (Huawei) provides further comment to Judy(Ericsson)
Judy (Ericsson) responds to Fenqin (Huawei) and objects to r01&r03
Judy (Ericsson) provides a post deadline revision = 'r04 + remove the 1st 'CN-initiated' in step 7 + resume EN in step 9'.
Fenqin (Huawei) provides further comment to Judy(Ericsson) and r07== 'r04 + remove the 1st 'CN-initiated' in step 7 + resume EN in step 9'.
Judy (Ericsson) is fine with Fenqin (Huawei)'s update
Judy (Ericsson) checks with Tao (VC) if the paper still requires CC# discussion?
Tao(VC) NO if people on the list can have clear agreement
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207473 P-CR Approval 23.700-47: KI#1, Sol#18: update to resolve ENs on MBS Session Release for RRC_INACTIVE UE Ericsson Rel-18 Revision of S2-2206499r04 + changes, merging and S2-2206533. Approved Approved
9.18 S2-2206533 P-CR Approval 23.700-47: KI#1, Sol#18, update of sol#18 Huawei, HiSilicon Rel-18 Merged into S2-2207473 LiMeng (Huawei) suggests to merge into S2-2206499
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206440 P-CR Approval 23.700-47: KI#1 Sol#20 update: resolving Editor's notes CATT Rel-18 r04 agreed. Revised to S2-2207474. Thomas (Nokia) provides r01
Xiaoyan (CATT) provides r02
Judy (Ericsson) comments
Thomas (Nokia) provides r03
Xiaoyan (CATT) provides r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207474 P-CR Approval 23.700-47: KI#1 Sol#20 update: resolving Editor's notes CATT Rel-18 Revision of S2-2206440r04. Approved Approved
9.18 S2-2206441 P-CR Approval 23.700-47: KI#1 Sol#21 update CATT Rel-18 r03 agreed. Revised to S2-2207475. Thomas (Nokia) provides r01
Xiaoyan (CATT) provides r02
Judy (Ericsson) comments
Thomas replies Xiaoyan (CATT) and objects against r02
Xiaoyan (CATT) replies to Thomas (Nokia)
Xiaoyan (CATT) replies to Judy (Ericsson)
Thomas (Nokia) replies to Xiaoyan (CATT)
Xiaoyan (CATT) provides r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207475 P-CR Approval 23.700-47: KI#1 Sol#21 update CATT Rel-18 Revision of S2-2206441r03. Approved Approved
9.18 S2-2206534 P-CR Approval 23.700-47: KI#1, Sol#4, Update of sol#4 Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207476. Judy (Ericsson) provides r01
Fenqin (Huawei) provides response
Fenqin(Huawei) provides response
Haris(Qualcomm) asks question
Fenqin(Huawei) provides r02
Judy (Ericsson) responds to Fenqin(Huawei)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207476 P-CR Approval 23.700-47: KI#1, Sol#4, Update of sol#4 Huawei, HiSilicon Rel-18 Revision of S2-2206534r02. Approved Approved
9.18 S2-2206594 P-CR Approval 23.700-47: KI#1, update the solution#6 ZTE Rel-18 r04 agreed. Revised to S2-2207477. Thomas (Nokia) provides r01
LiMeng (Huawei) asks for clarification.
Judy (Ericsson) provides r02 and comments
zhendong (ZTE) provides the response
zhendong (ZTE) provides response
zhendong (ZTE) provides response and r03
Thomas (Nokia) replies to Zhendong
Fenqin (Huawei) provides comments
zhendong (ZTE) provides the repsonse
Thomas(Nokia) replies to zhendong (ZTE)
Judy (Ericsson) provides r04 adding a missing 'not', and comments
zhendong (ZTE) responds to judy
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207477 P-CR Approval 23.700-47: KI#1, update the solution#6 ZTE Rel-18 Revision of S2-2206594r04. Approved Approved
9.18 S2-2206595 P-CR Approval 23.700-47: KI#1, update the solution#23 ZTE Rel-18 r03 agreed. Revised to S2-2207478. Fenqin (Huawei) comments.
Judy (Ericsson) comments
zhendong (ZTE) respond
zhendong (ZTE) responds to fenqin
Fenqin (Huawei) responds to Zhendong
zhendong (ZTE) provides the response
zhendong (ZTE) provides r01
Fenqin (Huawei) responds to Zhendong and provides r02
Judy (Ericsson) responds to zhendong (ZTE) and provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207478 P-CR Approval 23.700-47: KI#1, update the solution#23 ZTE Rel-18 Revision of S2-2206595r03. Approved Approved
9.18 S2-2206596 P-CR Approval 23.700-47: KI#1, add solution on session management and Mobility for RRC Inactive MBS data reception ZTE Rel-18 r01 agreed. Revised to S2-2207479. Thomas (Nokia) provides r01
LiMeng (Huawei) comments.
Thomas(Nokia) replies to LiMeng
Judy (Ericsson) comments
Haris(Qualcomm) comments
zhendong (ZTE) respond
zhendong (ZTE) provides the response
LiMeng (Huawei) asks questions
LiMeng (Huawei) replies to Zhendong
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) can live with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207479 P-CR Approval 23.700-47: KI#1, add solution on session management and Mobility for RRC Inactive MBS data reception ZTE Rel-18 Revision of S2-2206596r01. Approved Approved
9.18 - - - Evaluation and conclusion of KI#1 - - Docs:=8 -
9.18 S2-2205609 P-CR Approval 23.700-47: KI#1, Evaluation, and Interim conclusions Ericsson Rel-18 Merged into S2-2207480 LiMeng (Huawei) proposes to merge this document into S2-2205928.
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) confirmed the merging
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2205765 P-CR Approval 23.700-47: Way Forward for KI#1 (support for UEs in RRC_INACTIVE state) Qualcomm Incorporated Rel-18 Merged into S2-2207481 LiMeng (Huawei) proposes to merge this document into S2-2206535.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2205928 P-CR Approval 23.700-47: Evaluation and interim conclusions for key issue 1 Nokia, Nokia Shanghai Bell Rel-18 r06 + changes agreed. Revised to S2-2207480, merging S2-2205609 and S2-2206597 Xiaoyan (CATT) provides r01.
Thomas (Nokia) provides r02.
Aihua(CMCC) provides r03 to further clarify for the solution#3.
Judy (Ericsson) provides r04
zhendong (ZTE) provides r05
Fenqin (Huawei) provides r06
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) prefers r04, can accept r02, r03 &r05, objects to other revisions, and comment on r06
Fenqin (Huawei) suggest to do the replacement of the 'The RRC_INACTIVE UE need be aware whether the group paging is CN initiated or RAN initiated'
With, 'It is unclear whether the RRC_INACTIVE UE need be aware the group paging is CN initiated or RAN initiated.'
Judy (Ericsson) responds to Fenqin (Huawei)
Fenqin (Huawei) provides r07 after revision deadline.
Fenqin (Huawei) suggest to bring this to CC.

R07==r06 +
- removal of 'The RRC_INACTIVE UE need be aware whether the group paging is CN initiated or RAN initiated'
+ one EN, 'Editor's note: whether the RRC_INACTIVE UE need be aware the group paging is CN initiated or RAN initiated is FFS
Thomas(Nokia) is fine with r06 plus enhancements of LiMeng and bringing to CC.
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207480 P-CR Approval 23.700-47: Evaluation and interim conclusions for key issue 1 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205928r06 + changes, merging S2-2205609 and S2-2206597. Approved Approved
9.18 S2-2206442 P-CR Approval 23.700-47: KI#1 Interim conclusions CATT Rel-18 Merged into S2-2207481 LiMeng (Huawei) proposes to merge this document into S2-2206535.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206535 P-CR Approval 23.700-47: Evaluation of KI#1 FS_5MBS_Ph2 Huawei, HiSilicon Rel-18 r17 agreed. Revised to S2-2207481, merging S2-2205765 and S2-2206442 Fenqin (Huawei) proposes r01.
Xiaoyan (CATT) proposes r03.
Haris(Qualcomm) proposes r02
Hugh (AT&T) provided comments. If we are going to draw any conclusions at this meeting, Public Safety requirements need to be covered.
Fenqin (Huawei) provided r04.
Judy (Ericsson) comments and provide r05
Fenqin(Huawei) provide responses and r06
Haris(Qualcomm) comments on r05
Hugh(AT&T) provides comments
Thomas(Nokia) provides r07
Xiaoyan (CATT) comments and objects to r07
Thomas (Nokia) provides r08 and objects to r06
Fenqin (Huawei) provides r09
zhendong (ZTE) provides r10
Haris(Qualcomm) proposes r11
Judy (Ericsson) provides r13
Fenqin(Huawei) proposes r12
Thomas(Nokia) proposes r14
Fenqin(Huawei) proposes r15
Judy (Ericsson) responds
izhendong (ZTE) provides r16
Xiaoyan (CATT) provides r17
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) is fine with r17 and happy to co-sign
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207481 P-CR Approval 23.700-47: Evaluation of KI#1 FS_5MBS_Ph2 Huawei, HiSilicon Rel-18 Revision of S2-2206535r17, merging S2-2205765 and S2-2206442. Approved Approved
9.18 S2-2206597 P-CR Approval 23.700-47: KI#1, proposal on the way forward for KI#1 ZTE Rel-18 Merged into S2-2207480 LiMeng (Huawei) proposes to merge this document into S2-2205928.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 - - - Solutions of KI#2 - - Docs:=12 -
9.18 S2-2205610 P-CR Approval 23.700-47: KI#2, Sol#7: update to resolve ENs on MOCN RAN Sharing Ericsson Rel-18 r03 agreed. Revised to S2-2207482. LiMeng (Huawe) asks for a wording change.
Robbie (Ericsson) asks Thomas (Nokia).
Thomas (Nokia) provides r01
Robbie (Ericsson) replies to LiMeng (Huawei).
Thomas (Nokia) replies to Robbie (Ericsson)
Robbie (Ericsson) provides r02, and replies to Thomas (Nokia) and LiMeng (Huawei).
LiMeng (Huawei) provides r03.
Robbie (Ericsson) thanks LiMeng (Huawei) for the improvements in r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207482 P-CR Approval 23.700-47: KI#2, Sol#7: update to resolve ENs on MOCN RAN Sharing Ericsson Rel-18 Revision of S2-2205610r03. Approved Approved
9.18 S2-2205767 P-CR Approval 23.700-47: KI#2, Update solution #24 Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2207483. LiMeng (Huawei) comments.
LaeYoung (LGE) comments.
Haris(Qualcomm) responds
Haris(Qualcomm) provides r01
LiMeng (Huawei) asks question.
Haris(Qualcomm) responds and provides r02
LiMeng (Huawei) provides r03.
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) is ok with r02 or r03. R01 and r0 are incorrect
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207483 P-CR Approval 23.700-47: KI#2, Update solution #24 Qualcomm Incorporated Rel-18 Revision of S2-2205767r03. Approved Approved
9.18 S2-2205923 P-CR Approval 23.700-47: Solution proposal for key issue 2 Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207484. LiMeng (Huawei) asks for clarification.
Haris(Qualcomm) comments
Thomas(Nokia) replies to questions
Robbie(Ericsson) provides r01.
Thomas(Nokia) replies no Robbie
Robbie (Ericsson) replies to Thomas(Nokia)
LiMeng (Huawei) asks question
Robbie (Ericsson) comments.
Thomas(Nokia) replies to Robbie (Ericsson)
Thomas (Nokia) replies to Limeng
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) can live with r01.
Haris(Qualcomm) can also live with r01 but provides comments and points out that there is a typo in the figure 6.x.3-1 step 6 MCON->MOCN
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207484 P-CR Approval 23.700-47: Solution proposal for key issue 2 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205923r01. Approved Approved
9.18 S2-2206033 P-CR Approval 23.700-47: KI#2, Sol#8: Update to cover various network sharing scenarios LG Electronics Rel-18 r05 agreed. Revised to S2-2207485. LiMeng (Huawei): asks for clarification.
LaeYoung (LGE) replies to LiMeng (Huawei).
Robbie (Ericsson) asks for clarification.
LaeYoung (LGE) replies to Robbie (Ericsson).
Robbie (Ericsson) asks LaeYoung (LGE).
LaeYoung (LGE) answers to Robbie (Ericsson).
Robbie (Ericsson) provides comments to LaeYoung (LGE).
LaeYoung (LGE) provides r01.
Robbie (Ericsson) replies to LaeYoung (LGE).
LaeYoung (LGE) responds to Robbie (Ericsson).
LaeYoung (LGE) provides r02.
Haris(Qualcomm) comments
Thomas(Nokia) provides r03.
LaeYoung (LGE) responds to Thomas(Nokia) and Haris (Qualcomm).
LiMeng (Huawei) comments.
LaeYoung (LGE) thanks to Robbie (Ericsson) for r05.
Robbie (Ericsson) provides r05.
LaeYoung (LGE) provides r04 and answers to LiMeng (Huawei).
Robbie (Ericsson) thanks LaeYoung (LGE) for the updating in 5611 accordingly.
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) can live with r05.
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207485 P-CR Approval 23.700-47: KI#2, Sol#8: Update to cover various network sharing scenarios LG Electronics Rel-18 Revision of S2-2206033r05. Approved Approved
9.18 S2-2206080 P-CR Approval 23.700-47: KI#1, Sol#2: Update to clarify additional identifier Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207486. Robbie (Ericsson) provides comments.
Thomas (Nokia) provides r01
Robbie (Ericsson) replies to Thomas (Nokia)
Thomas (Nokia) replies to Robbie
Robbie (Ericsson) asks Thomas (Nokia).
Thomas (Nokia) replies to Robbie (Ericsson)
LiMeng (Huawei) replies to Robbie (Ericsson) and Thomas (Nokia)
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) asks questions and prefers r00.
Robbie (Ericsson) agrees with LiMeng (Huawei) and prefers r00.
Thomas(Nokia) objects against r00.
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207486 P-CR Approval 23.700-47: KI#1, Sol#2: Update to clarify additional identifier Huawei, HiSilicon Rel-18 Revision of S2-2206080r01. Approved Approved
9.18 S2-2206344 P-CR Approval 23.700-47: KI #2: Update solution #9 on 5MBS MOCN Network Sharing Samsung Rel-18 r03 agreed. Revised to S2-2207487. Thomas (Nokia) provides r01
Youngkyo(Samsung) replies to the question
Robbie (Ericsson) asks a question
LiMeng (Huawei) asks for clarification.
Youngkyo(Samsung) provides r02.
Youngkyo(Samsung) provides r03.
Haris(Qualcomm) asks question for clarification
Youngkyo(Samsung) replies.
Haris(Qualcomm) asks follow up question
LiMeng (Huawei) asks questions.
LiMeng (Huawei) apologizes that he missed the revision, and is fine with r03, thanks YoungKyo.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207487 P-CR Approval 23.700-47: KI #2: Update solution #9 on 5MBS MOCN Network Sharing Samsung Rel-18 Revision of S2-2206344r03. Approved Approved
9.18 - - - Evaluation and conclusion of KI#2 - - Docs:=9 -
9.18 S2-2205611 P-CR Approval 23.700-47: KI#2, Evaluation on 5MBS MOCN Network Sharing Ericsson Rel-18 r11 agreed. Revised to S2-2207488, merging S2-2206031, S2-2206083 and S2-2206598 LiMeng (Huawei) asks comments
Robbie (Ericsson) replies to LiMeng (Huawei)
Robbie (Ericsson) provides r01.
Robbie (Ericsson) provides r02.
LaeYoung (LGE) provides r03.
Thomas (Nokia) provides r04.
LiMeng (Huawei) comments on previous revisions and provide r06, asks to ignore r05.
LaeYoung (LGE) provides r07.
Robbie (Ericsson) provides r08.
LaeYoung (LGE) provides r09.
Robbie (Ericsson) provides r10.
Haris(Qualcomm) provides r11
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207488 P-CR Approval 23.700-47: KI#2, Evaluation on 5MBS MOCN Network Sharing Ericsson Rel-18 Revision of S2-2205611r11, merging S2-2206031, S2-2206083 and S2-2206598. Approved Approved
9.18 S2-2205943 P-CR Approval 23.700-47: Evaluation and interim conclusions for key issue 2 Nokia, Nokia Shanghai Bell Rel-18 r10 agreed. Revised to S2-2207489, merging S2-2206032 and S2-2206085 Thomas (Nokia) provides r01
Robbie (Ericsson) provides r02.
LaeYoung (LGE) provides r03.
zhendong (ZTE) provides r04
Robbie (Ericsson) comments.
zhendong (ZTE) respond
LiMeng (Huawei) supports Robbie.
LaeYoung (LGE) cannot accept all versions except r03 and postponing KI#2 conclusion is fine.
Thomas (Nokia) provides r05
LiMeng (Huawei) provides r06
LaeYoung (LGE) provides r07.
Youngkyo(Samsung) questions
LaeYoung (LGE) provides r08.
Robbie (Ericsson) provides r09.
LiMeng (Huawei) is fine with r09.
LaeYoung (LGE) provides r10.
LiMeng (Huawei) is fine with r10.
Thomas (Nokia) is fine with r10.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207489 P-CR Approval 23.700-47: Evaluation and interim conclusions for key issue 2 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205943r10, merging S2-2206032 and S2-2206085. Approved Approved
9.18 S2-2206031 P-CR Approval 23.700-47: KI#2, Evaluation LG Electronics Rel-18 Merged into S2-2207488 LiMeng (Huawei) proposes to merge this document into S2-2205611.
LaeYoung (LGE) is fine to merge this document into S2-2205611.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206032 P-CR Approval 23.700-47: KI#2, Conclusion LG Electronics Rel-18 Merged into S2-2207489 LiMeng (Huawei) proposes to merge this document into S2-2205943.
LaeYoung (LGE) is fine to to merge this document into S2-2205943.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206083 P-CR Approval 23.700-47: KI#2: Evaluation Huawei, HiSilicon Rel-18 Merged into S2-2207488 LaeYoung (LGE) proposes to merge this document into S2-2205611.
LiMeng (Huawei) confirms this document will be merged into S2-2205611.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206085 P-CR Approval 23.700-47: KI#2: Interim conclusion Huawei, HiSilicon Rel-18 Merged into S2-2207489 LaeYoung (LGE) proposes to merge this document into S2-2205943.
LiMeng (Huawei) confirms to merge this document into S2-2205943.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206598 P-CR Approval 23.700-47: KI#2, evaluation and interim conclusion ZTE Rel-18 Merged into S2-2207488 LiMeng (Huawei) proposes to merge this document into S2-2205611.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 - - - Solutions of KI#3 - - Docs:=4 -
9.18 S2-2205887 P-CR Approval 23.700-47: FS_5MBS_Ph2 KI#3 Sol#11 Update for making clarification China Mobile, CATT, vivo Rel-18 Noted Thomas (Nokia) provides r01
Aihua(CMCC) provides r02
Judy (Ericsson) provides r03
Aihua(CMCC) replies and objects r03.
Thomas(Nokia) objects against r02 and provides r04
Judy (Ericsson) responds to Aihua (CMCC) and provides r05
Aihua(CMCC) replies and provides r06.
Thomas(Nokia) comments against r06.
zhendong (ZTE) comments
==== 9.X, 10.X Revisions Deadline ====
Aihua(CMCC) is fine with r02, r06 and r00, object any other revision.
Tao(VC) Let's check r00 agreeable or not which is the only one left
Thomas(Nokia) objects against r00, r02, and r06
==== 9.X, 10.X Final Deadline ====
Noted
9.18 S2-2205924 P-CR Approval 23.700-47: Solution proposal for key issue 3 Nokia, Nokia Shanghai Bell Rel-18 r08 agreed. Revised to S2-2207490. LiMeng (Huawei) asks for clarification.
Robbie (Ericsson) asks for clarification.
Robbie(Ericsson) replies to Thomas(Nokia).
Thomas(Nokia) provides r01 and replies to questions.
Fenqin(Huawei) provide comments.
Xiaoyan (CATT) provides comments and objects to r00 and r01.
Thomas(Nokia) replies to Robbie
Thomas(Nokia) replies to Fenqin
Robbie (Ericsson) provides r05, and asks to ignore r04.
Thomas(Nokia) replies to Xiaoyan (CATT) and provides r03.
Thomas(Nokia) provides r06.
Robbie(Ericsson) raises concerns against r06.
Robbie (Ericsson) replies to Thomas(Nokia)
Thomas(Nokia) provides r07 and responds to Robbie
Robbie (Ericsson) asks Thomas(Nokia) whether r07 is uploaded
Thomas(Nokia) has new really uploaded r07
Robbie(Ericsson) provides r08.
Thomas(Nokia) accepts r08.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207490 P-CR Approval 23.700-47: Solution proposal for key issue 3 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205924r08. Approved Approved
9.18 S2-2206472 P-CR Approval 23.700-47: KI#3, Sol#10: resolve Ens Vivo Rel-18 Noted Thomas (Nokia) raises concerns
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) asks the way forward of this document
Judy (Ericsson) propose to note this paper due to no sufficient justification to remove the EN.
==== 9.X, 10.X Final Deadline ====
Noted
9.18 - - - Evaluation and conclusion of KI#3 - - Docs:=3 -
9.18 S2-2205612 P-CR Approval 23.700-47: KI#3, Conclusion Ericsson Rel-18 Postponed LiMeng (Huawei) proposes to use this document as the place holder for conclusion.
Judy (Ericsson) provides r01, adding Qualcomm as co-source that was forgotten during submission.
Aihua(CMCC) provides r02.
Judy (Ericsson) comments on r02
Thomas(Nokia) raises concerns and suggest postponing this contribution
Haris(Qualcomm) cannot agree on r02 and comments further
Aihua(CMCC) replies to Haris(Qualcomm) .
Haris(Qualcomm) responds
==== 9.X, 10.X Revisions Deadline ====
Aihua(CMCC) is fine with r02 , object any other revision including original version.
Thomas(Nokia) request to postpone PCR, objects against r02
==== 9.X, 10.X Final Deadline ====
Postponed
9.18 S2-2205888 P-CR Approval 23.700-47: FS_5MBS_Ph2 KI#3 Evaluation and Conclusion China Mobile, CATT, vivo, ABS, ZTE Rel-18 CC#4: r05 with changes proposed. r05 agreed. Revised to S2-2207491. Aihua(CMCC) provides r01, which focuses on evaluation.
Judy (Ericsson) comments
Thomas(Nokia) provides r02, were comments identify parts that require further improvement
Haris(Qualcomm) provides r03
Aihua(CMCC) replies and provides r04.
Thomas(Nokia) provides r05.
==== 9.X, 10.X Revisions Deadline ====
Aihua(CMCC) proposes to discuss in CC#4 or CC#5.
Thomas(Nokia) if fine with r05 +
Change 'all these solutions have a substantial number of unresolved issues' -> 'Editor´s note: unresolved issues of these solutions need to be addressed'
Revised
9.18 S2-2207491 P-CR Approval 23.700-47: FS_5MBS_Ph2 KI#3 Evaluation and Conclusion China Mobile, CATT, vivo, ABS, ZTE Rel-18 Revision of S2-2205888r05. Approved Approved
9.18 - - - Solutions of KI#4 - - Docs:=3 -
9.18 S2-2205613 P-CR Approval 23.700-47: KI#4, Sol#12: update to resolve ENs on Group Message Delivery Ericsson Rel-18 Approved LiMeng (Huawei) asks a question
Robbie (Ericsson) replies to LiMeng (Huawei)
LiMeng (Huawei) is OK with Robbie's proposal
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.18 S2-2206081 P-CR Approval 23.700-47: KI#4, Sol#13: Update and clarification Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207492. Robbie (Ericsson) asks for clarification.
Robbie (Ericsson) provides r01.
LiMeng (Ericsson) is OK with r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207492 P-CR Approval 23.700-47: KI#4, Sol#13: Update and clarification Huawei, HiSilicon Rel-18 Revision of S2-2206081r01. Approved Approved
9.18 - - - Evaluation and conclusion of KI#4 - - Docs:=2 -
9.18 S2-2205614 P-CR Approval 23.700-47: KI#4, Evaluation and Conclusion on Group Message Delivery Ericsson Rel-18 r03 agreed. Revised to S2-2207493. LiMeng (Huawei) comments
Robbie (Ericsson) replies to LiMeng (Huawei).
Robbie (Ericsson) provides r01.
Thomas (Ericsson) provides r02.
Robbie (Ericsson) is fine with r02.
LiMeng (Huawei) provides r03.
Robbie (Ericsson) is fine with r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207493 P-CR Approval 23.700-47: KI#4, Evaluation and Conclusion on Group Message Delivery Ericsson Rel-18 Revision of S2-2205614r03. Approved Approved
9.18 - - - Solutions of KI#5 - - Docs:=3 -
9.18 S2-2205766 P-CR Approval 23.700-47: KI#5, New Sol: Support for RedCap UEs for Group Communication Qualcomm Incorporated Rel-18 Noted LiMeng (Huawei) doesn't think SA2 should initiate the discussion, thus pCR is not needed.
Haris(Qualcomm) responds
Judy (Ericsson) share the view from LiMeng (Huawei) that this pCR is not needed
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) responds to Haris(Qualcomm) and propose to note this paper.
LiMeng (Huawei) agrees Judy (Ericsson) on noting this paper.
==== 9.X, 10.X Final Deadline ====
Noted
9.18 S2-2206082 P-CR Approval 23.700-47: KI#5, Sol#14: Update to remove EN Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207494. Haris(Qualcomm) asks question for clarification
LiMeng (Huawei) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207494 P-CR Approval 23.700-47: KI#5, Sol#14: Update to remove EN Huawei, HiSilicon Rel-18 Revision of S2-2206082r01. Approved Approved
9.18 - - - Evaluation and conclusion of KI#5 - - Docs:=4 -
9.18 S2-2205615 P-CR Approval 23.700-47: KI#5, Evaluation and Conclusion on broadcast MBS Session Ericsson Rel-18 r02 + changes agreed. Revised to S2-2207495, merging and S2-2206084 LiMeng (Huawei) provides r01.
LiMeng (Huawei) provides r02.
Thomas (Nokia) provides r02, raises concerns against r00 and r01
Thomas(Nokia) corrects that he provided r02, not LiMeng
Judy (Ericsson) provides r03
Thomas(Nokia) objects against r03, r00 and r01
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) suggests 'on top of r03: remove the last paragraph'
Judy (Ericsson) provides post deadline revision r04 == r03+remove 'however it is to be clarified ... at the required point of time', objects to r02
Judy (Ericsson) request to check in CC#4 or CC#5
Thomas (Nokia) Is fine with r04
LiMeng (Huawei) is fine with r04
Judy (Ericsson) is fine with r04 = r02 + remove 'Only' in the beginning of the last paragraph.
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207495 P-CR Approval 23.700-47: KI#5, Evaluation and Conclusion on broadcast MBS Session Ericsson Rel-18 Revision of S2-2205615r02 + changes, merging and S2-2206084. Approved Approved
9.18 S2-2206084 P-CR Approval 23.700-47: KI#5: Evaluation Huawei, HiSilicon Rel-18 Merged into S2-2207495 LiMeng (Huawei) proposes to merge this document into S2-2205615.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.18 S2-2206086 P-CR Approval 23.700-47: KI#5: Conclusion Huawei, HiSilicon Rel-18 Postponed Thomas (Nokia) provides r02
Judy (Ericsson) provides r03 merging 5615 which propose to use Sol#14 as basis for normative (r01 seems not announced?)
Thomas(Nokia) objects against r03
Haris(Qualcomm) cannot accept r02
LiMeng (Huawei) provides r04
Haris(Qualcomm) proposes r05
LiMeng (Huawei) provides comments on r05.
Haris(Qualcomm) comments
Thomas(Nokia) objects against r04 and r05.
Suggest postponing the issue
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) does not understand Thomas(Nokia)'s reasoning of postponing proposal, as Sol#14 inherited from EPS is considered stable enough and r04 seems a good compromise.
Haris(Qualcomm) can only accept r05
Thomas(Nokia) replies to Harris
Thomas(Nokia) suggest r02 +
+ Modify first sentence as follows 'The following interim conclusion apply'
+ convert last bullet to editor´s note by prepending: 'Editor´s Note: The following is ffs'
Judy (Ericsson) comments that the proposal (r02+) is not acceptable to us.
==== 9.X, 10.X Final Deadline ====
Postponed
9.18 - - - Solutions of KI#6 - - Docs:=2 -
9.18 S2-2206075 P-CR Approval 23.700-47: KI#6, New Sol: Multicast access control for high number of public safety UEs Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207496. Robbie (Ericsson) asks questions
LiMeng (Huawei) replies
Robbie (Ericsson) asks LiMeng (Huawei)
Haris(Qualcomm) comments
Thomas(Nokia) comments
LiMeng (Huawei) replies and provides r01.
Haris(Qualcomm) responds
Robbie (Ericsson) provides r02 to add ENs for his concerns.
LiMeng (Huawei) provides r03 and adds EN for the slicing issue.
Thomas (Nokia) provides r04 adding some more ENs.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207496 P-CR Approval 23.700-47: KI#6, New Sol: Multicast access control for high number of public safety UEs Huawei, HiSilicon Rel-18 Revision of S2-2206075r04. Approved Approved
9.18 - - - Evaluation and conclusion of KI#6 - - Docs:=4 -
9.18 S2-2205616 P-CR Approval 23.700-47: KI#6, Sol#17: update to resolve ENs on Performance Improvements for Public Safety Ericsson Rel-18 r07 agreed. Revised to S2-2207497. LiMeng (Huawei) comments.
Robbie (Ericsson) replies to LiMeng (Huawei).
Haris(Qualcomm) proposes addition
Robbie (Ericsson) provides r01.
Fenqin (Huawei) provides comment and r02.
Robbie (Ericsson) provides r03 and replies to Fenqin (Huawei).
Robbie (Ericsson) replies to Fenqin (Huawei).
Fenqin (Huawei) provides feedback.
Fenqin (Huawei) provides feedback to Robbie(Ericsson)
Thomas (Nokia) provides r04
Robbie (Ericsson) provides r05.
Thomas (Nokia) now really uploaded r04
Robbie (Ericsson) asks Thomas (Nokia) whether r04 is uploaded.
Fenqin (Huawei) provides r06.
Robbie (Ericsson) provides r07.
Fenqin (Huawei) provides responds
Robbie (Ericsson) ask question
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207497 P-CR Approval 23.700-47: KI#6, Sol#17: update to resolve ENs on Performance Improvements for Public Safety Ericsson Rel-18 Revision of S2-2205616r07. Approved Approved
9.18 S2-2205617 P-CR Approval 23.700-47: KI#6, Evaluation on Improvement for potential performance issues related to high numbers of public safety UEs Ericsson Rel-18 r06 agreed. Revised to S2-2207498. Haris(Qualcomm) provides comments
Robbie(Ericsson) provides r01.
Fenqin(Huawei) provides r02.
Robbie(Ericsson) provides r03.
Haris(Qualcomm) provides r04
Thomas(Nokia) provides r05
Robbie (Ericsson) provides r06.
Haris(Qualcomm) comments on r06
Robbie (Ericsson) replies to Haris(Qualcomm)
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) is ok with r06
==== 9.X, 10.X Final Deadline ====
Revised
9.18 S2-2207498 P-CR Approval 23.700-47: KI#6, Evaluation on Improvement for potential performance issues related to high numbers of public safety UEs Ericsson Rel-18 Revision of S2-2205617r06. Approved Approved
9.19 - - - Study on XR (Extended Reality) and media services (FS_XRM) - - Docs:=145 -
9.19 - - - Architecture & Requirement - - Docs:=3 -
9.19 S2-2206350 P-CR Approval 23.700-60: Architectural assumption on the PDU Session for XRM services MediaTek Inc., Samsung Rel-18 r04 agreed. Revised to S2-2207770. Devaki (Nokia) objects to the P-CR.
Devaki (Nokia) comments
Shabnam (Ericsson) would support the proposal and asks clarification on Nokia interpretation and what is actually proposed.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Lei (Tencent) can accept r04.
Revised
9.19 S2-2207770 P-CR Approval 23.700-60: Architectural assumption on the PDU Session for XRM services MediaTek Inc., Samsung Rel-18 Revision of S2-2206350r04. Approved Approved
9.19 S2-2206925 P-CR Approval 23.700-60: Architecture Requirement for encrypted media traffics Google Inc. Rel-18 Noted Youngkyo(Samsung) shares the view with Hui .
Hui (Huawei) provides comments.
Dan(China Mobile) shares the view with Hui .
Mengzhen (China Telecom) shares the same view with Dan & Hui.
Ellen (Google) provides feedback to the comments
Hui(Huawei) provides r02.
Shabnam (Ericsson) would like to understand what is the second change mean, what enhancements of this study as the study is ongoing? So it is for future work?
Ellen (Google) replies to Hui (Huawei) r02 and Dario (QC)
Dario (Qualcomm) comments.
Markus (Nokia) comments.
Hui (Huawei) seconds Markus' view.
Ellen (Google) thanks Hui (Huawei) comments and provides r05 with editorials
Curt (Meta) comments...and suggests r05 is the way to go.
Dario (Qualcomm) comments and provides r06
Hui (Huawei) provides r07
Shabnam (Ericsson) do not see the need to change the existing text except for removal of the editorial 'the' as done in r06, r05 ok. Other revisions are not acceptable, and r07 does not make any sense as it removes the critical part of encryption of certain information that we need to take care of.
==== 9.X, 10.X Revisions Deadline ====
Curt (Meta) prefers r05.
Dario (Qualcomm) can only accept r06.
Ellen (Google) prefers r05. The requirement is general for existing XRM services.
Hui (Huawei) clarify r07 didn't remove encryption of information.
Lei (Tencent) is ok with r05.
Hui (Huawei) prefers to r07, can live with r06, or postpone.
Xiaowan (vivo) provides views about whether the two sentences co-exist or not
Hui (Huawei) replies to Xiaowan.
Ellen (Google) agrees to r7+r5 (the best)
Dario (Qualcomm) objects to r05 and r07. Accepts r06.
Ellen (Google) objects to r06 proposed by Qualcomm that removes the partial/full encrypted protocol header consideration for XRM services in R18. It's important to set the right requirement from the beginning for a complete analysis and cross WGs/SDOs plan/discussion to support XRM services at 3GPP.
Shabnam (Ericsson) ok with r05 or r06, objects to all other versions.
Hui (Huawei) ok with r05 with the following change, or r06, r07. Objects to all other versions.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 - - - KI1&2 new sol and sol update - - Docs:=14 -
9.19 S2-2205831 P-CR Approval 23.700-60: KI#1 and KI#2, New Sol: Policy control and exposure for multi-modality services Ericsson Rel-18 r01 agreed. Revised to S2-2207771. Boren (OPPO) comments.
Xinpeng(Huawei) asks for clarification.
Saso (Intel) seeks clarification.
Dan (China Mobile) have question for clarification
Shabnam (Ericsson) thanks for the feedback, please see our responses, I have consolidated them together to keep track better.
Xinpeng(Huawei) comments.
Shabnam (Ericsson) please see in line
Shabnam (Ericsson) provides r01 to update according to the questions and responses.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207771 P-CR Approval 23.700-60: KI#1 and KI#2, New Sol: Policy control and exposure for multi-modality services Ericsson Rel-18 Revision of S2-2205831r01. Approved Approved
9.19 S2-2206148 P-CR Approval 23.700-60: KI#1&2, New Sol: application-layer based synchronization and group QoS Coordination China Telecom Rel-18 r03 agreed. Revised to S2-2207772. Markus (Nokia) comments and asks questions for clarification.
Mengzhen (China Telecom) reply to Markus (Nokia) and provide r01
Dan(China Mobile) comments
Mengzhen (China Telecom) replies to Dan (China Mobile) and provide r02.
Dan (China Mobile) comment
Dan (China Mobile) replies to Mengzhen
Shabnam (Ericsson) asks if China Telecom considers the solution consistent with Ericsson 5831 as well as soln#40, and consider it a merged with them?
Mengzhen (China Telecom) replies to Dan (China Mobile).
Mengzhen (China Telecom) replies to Dan (China Mobile) and Shabnam (Ericsson) and provide r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207772 P-CR Approval 23.700-60: KI#1&2, New Sol: application-layer based synchronization and group QoS Coordination China Telecom Rel-18 Revision of S2-2206148r03. Approved Approved
9.19 S2-2205908 P-CR Approval 23.700-60: KI #1 and KI#2, Consolidated solution InterDigital Inc. Rel-18 Noted Dan (China Mobile) comments
Mike (InterDigital) provides r01
Shabnam (Ericsson) fails to understand what value is added in consolidating all these solutions? Is that evaluation, or does this supersede all other solns so far and we mark them void and only consider this one? Do we add the new solns here in future?
Xinpeng(Huawei) shares the same view that the value of such a consolidated solution is unclear.
Mike (InterDigital) replies to Xinpeng(Huawei) and Shabnam (Ericsson) and indicates that the intention is not to void any solution and only to aid evaluation. This is consistent with what was done in Solution 52.
Shabnam (Ericsson) comments that it does not aid if you designate it as a new soln under clause 6 and if you do not include additional new solns that may come in, provides comments on what could be acceptable
Mike (InterDigital) asks that this solution be treated like Solution #52 and provides r02 to address concerns
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) Objects to all revisions, proposes to discuss at CC#4, Mike, two wrongs do not make a right. I see one version of #52 has gone to r26, and many other solns that are consolidated have updates that now needs to target both #52 & their own so value added is questionable to me. Comments
Mike (InterDigital) agrees to discuss on CC#4. The comparison to the discussion of Solution #52 at this meeting is not fair. When solution #52 was agreed it was to show the common points and differences for a sub-set of KI#4/5 solutions. We are doing the same with this new solution for KI#1/2. At this meeting companies are trying to update solution #52 with features that they think are important. This is a natural (and sometime painful) part of the debate.
Hui (Huawei) comments.
Shabnam (Ericsson) I did not bring in #52, it was mentioned as a precedence for this study and proposal to follow so now if we establish this to be the norm which I don't agree with, to me that is a bad precedence to set.
Dan (China Mobile) suggest to note this paper
Shabnam (Ericsson) thanks Dan for constructive proposal, and I accept this approach. I very much appreciate Mike's hard work, but I am fearful of precedence being set and this one I find it to be not a good one.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205941 P-CR Approval 23.700-60: KI#2, New Sol, NEF based coordination across PCFs Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2207773. Jinhua (Xiaomi) provides comments,
Markus (Nokia) replies to comments from Jinhua (Xiaomi).
Dario (Qualcomm) comments.
Markus replies to Dario (Qualcomm) and provides r01.
Jinhua (Xiaomi) replies to Markus (Nokia),
Dan(China Mobile) comments
Markus (Nokia) replies to Jinhua (Xiaomi) and Dan (China Mobile) and provides r02 addressing their questions.
Jinhua (Xiaomi) replies to Markus (Nokia) and provides r03.
Shabnam (Ericsson) comments on some significant issues potentially and asks for clarifications
Markus (Nokia) replies to Shabnam (Ericsson).
Markus (Nokia) replies to Jinhua (Xiaomi).
Markus (Nokia) provides r04.
Jinhua (Xiaomi) replies to Markus, r04 is OK,
Shabnam (Ericsson) provides r05 and removes all atomic admission control requirements of RAN as this is out of scope.
Markus (Nokia) is fine with r05.
==== 9.X, 10.X Revisions Deadline ====
Jinhua (Xiaomi) comments, r05 is OK. Details behaviour of admission control is up to RAN.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207773 P-CR Approval 23.700-60: KI#2, New Sol, NEF based coordination across PCFs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205941r05. Approved Approved
9.19 S2-2206392 P-CR Approval 23.700-60: Solution for KI#1, KI#2 on QoS enhancement to support coordinated treatment of a group of QoS flows Huawei, HiSilicon, Nokia, China Mobile, China Telecom, Xiaomi, Tencent Rel-18 r15 agreed. Revised to S2-2207774. Markus (Nokia) provides r01.
Xinpeng(Huawei) provides r02.
Youngkyo(Samsung) provides comments and provides r03.
Xiaowan (vivo) provides comments.
Markus (Nokia) replies to Xinpeng (Huawei).
Xinpeng(Huawei) replies to
Mengzhen (China Telecom) comments and provide r05.
Markus (Nokia) provides r06 on top of r04, merging with r05 is still needed.
Xiaowan(vivo) replies to Xinpeng(Huawei) and provides r07
Xinpeng(Huawei) provides r08, and replies to Mengzhen (China Telecom), Markus (Nokia), Xiaowan(vivo).
Markus (Nokia) comments about the 'group size', single vs. multiple AF requests, the 'getting stuck' issue and the multiple UEs case.
Markus (Nokia) provides r09.
Xinpeng(Huawei) replies to Xiaowan (vivo).
Markus (Nokia) comments the coordination across UEs.
Paul (Ericsson) asks questions for clarification.
Paul (Ericsson) provides comments and asks to remove from the solution details on new RAN functionality.
Xinpeng(Huawei) replies to Paul (Ericsson).
Markus provides r10 addressing concerns of Paul (Ericsson).
Paul (Ericsson) clarifies that the existing mechanim uses AQP merely as a reference to currently provided QoS level, i.e. RAN does not choose new AQP but always uses the QoS profile.
Paul (Ericsson) wants to repeat that this not existing mechanism. In existing mechanism RAN does not sets QoS parameters according to AQP. In existing mechanism RAN merely refers to AQP that matches currently supported QoS level.
Paul (Ericsson) provides r11. As commented earlier, we can't accept the details on new RAN functionality.
Dan (China Mobile) based on the discussion, I think 'RAN selects the AQP based on RAN condition' is proper.
Xinpeng(Huawei) provides r12.
Markus (Nokia) provides r13 with minor updates and comments.
Paul (Ericsson) provides comments.
Markus (Nokia) comments.
Xinpeng(Huawei) provides r14.
Xinpeng(Huawei) provides r15.
==== 9.X, 10.X Revisions Deadline ====
Dan(China Mobile) suggest to go with r14, but if Paul insist, I can also accept r11 in order to make progress.
Markus (Nokia) proposes to go with r15, unless there are clear reasons why r14 or r11 are more preferable.
Paul (Ericsson), provides comments.
Markus (Nokia) can accept Paul (Ericsson) proposal for r15 sentence removal. However would like to understand how without similar sentences we can satisfy the WT#1 NOTE which says: 'Any parameters provided by 5GC to NG-RAN via the Control plane need to have a clear explanation about how they are intended to be used by NG-RAN'.
Xinpeng(Huawei) proposes r15 + remove 'RAN can take the information about the total number of critical QoS flows into account when making its admission control decisions for the individual QoS flows.'
Markus (Nokia) agrees with Xinpeng (Huawei) and Paul (Ericsson) proposal to go with r15 with the removed sentence.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207774 P-CR Approval 23.700-60: Solution for KI#1, KI#2 on QoS enhancement to support coordinated treatment of a group of QoS flows Huawei, HiSilicon, Nokia, China Mobile, China Telecom, Xiaomi, Tencent Rel-18 Revision of S2-2206392r15. Approved Approved
9.19 S2-2206396 P-CR Approval 23.700-60: KI #1 and #2: New solution on multi-modality support Samsung Rel-18 r03 agreed. Revised to S2-2207775. Youngkyo(Samsung) provides r01
Dario (Qualcomm) asks question for clarification and comments
Xinpeng(Huawei) asks for clarification.
Shabnam (Ericsson) asks same clarification as Qualcomm, how is it different from soln#1, in our reading they are the same and we don't need two solns that are same?
Youngkyo(Samsung) provides r02.
Jinhua (Xiaomi) provides comments and r03,
Shabnam (Ericsson) the soln still uses delay difference in 6.XX.3.1 NOTE and step 6, so should they be also updated and is the soln then making sense still as it has now changed the concept?
Youngkyo(Samsung) replies.
Youngkyo(Samsung) is okay with adding the EN for now and can accept r03
Dan(China Mobile) reply
==== 9.X, 10.X Revisions Deadline ====
Jinhua (Xiaomi) provide comments,
Youngkyo(Samsung) replies to Dan and Jinhua.
Shabnam (Ericsson) comments again the soln no longer works since delay difference is mentioned in the General but removed from flows so what is the soln now?
==== 9.X, 10.X Final Deadline ====
Youngkyo(Samsung) replies to shabnam.
Revised
9.19 S2-2207775 P-CR Approval 23.700-60: KI #1 and #2: New solution on multi-modality support Samsung Rel-18 Revision of S2-2206396r03. Approved Approved
9.19 S2-2206401 P-CR Approval 23.700-60: Solution on multi-modality support for UE connected with tethered device(s) (Key issue #1 & #2) Samsung Rel-18 Noted Dario (Qualcomm) asks question for clarification.
jaehyeon (Samsung) replies to Dario
Mengzhen (China Telecom) comments this is out of scope.
LaeYoung (LGE) also thinks that handling tethered devices is out of scope, so proposes to NOTE this pCR.
Boren (OPPO) asks question.
Jaehyeon (Samsung) replies to Mengzhen (China Telecom).
Boren (OPPO) comments.
jaehyeon (Samsung) replies to Borren (OPPO), LaeYoung (LGE) and provides r01.
Jaehyeon (Samsung) replies to Boren (OPPO) and provides r02.
Dan(China Mobile) also think this solution is out of KI#1 scope.
Jaehyeon (Samsung) replies to Lei (Tencent), Dario (Qualcomm), Dan (china mobile).
LaeYoung (LGE) provides comment.
Shabnam (Ericsson) we share the concerns from others regarding the scope of explicit mention of tethered devices, and if we take away the differences explicitly used for tethered devices, which are implementation specific/proprietary UE, it seems soln#1 so we don't see the need for this.
Jaehyeon (Samsung) replies to LaeYoung (LGE) and Shabnam (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) proposes to note this document.
Jaeyheon (Samsung) replies to Dario (Qualcomm) and request reconsideration of comments.
Dan (China Mobile) suggest to note this document.
Jahyeon (Samsung) agree with comment form Dan (China Mobile),
but still think it's value to the study, and should be considered practically for multi modlaity service.
Accept to note this paper.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2206880 P-CR Approval 23.700-60: KI#1-2: Sol. 40 update Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2207776. Dan(China Mobile) comments
Dan (China Mobile) replies to Dario and ask more
Dario (Qualcomm) replies to Dan.
Xinpeng(Huawei) asks for clarification.
Dario (Qualcomm) replies and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207776 P-CR Approval 23.700-60: KI#1-2: Sol. 40 update Qualcomm Incorporated Rel-18 Revision of S2-2206880r01. Approved Approved
9.19 - - - KI3 new sol and sol update - - Docs:=16 -
9.19 S2-2205845 DISCUSSION Approval Discussion on ECN/L4S related solutions in KI#3 Vivo Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205829 P-CR Approval 23.700-60: KI#3, Sol #41: update to remove one editor s note, clarification of impacts and correction/clarification of references Ericsson Rel-18 r02 agreed. Revised to S2-2207777. CC#5: Noted and S2-2207777 was withdrawn Yali (OPPO) comments and proposes to address the L4S enabling issue in S2-2205996.
Xiaowan Ke(vivo) provides r01
Xiaowan(vivo) replies Paul (Ericsson) : the new EN is needed in r01 because it is a kind of backward compatibility issue
Paul (Ericsson) replies and explains that r01 with the new EN is not needed.
Paul (Ericsson) clarifies why this new EN is not needed.
Xiaowan(vivo) replies to Paul (Ericsson)
Paul (Ericsson) provides r02.
Curt (Meta) agrees with Paul (Ericsson)
Xiaowan(vivo) objects to r02 and relies to Curt (Meta) and Paul (Ericsson)
Dan(China Mobile) provides some information
Curt (Meta) objects to r01 and relies to Xiaowan (Vivo)
==== 9.X, 10.X Revisions Deadline ====
Paul (Ericsson) asks Xiaowan (vivo) to clarify the objection to r02 that updates references and rephrases a note. Which of these changes are not agreeable?
Xiaowan Ke(vivo) replies to Paul (Ericsson): I objected r02 because you removed my EN. Now I can revoke my objection to r02 if it add : 'NOTE: If the network operator want to apply the ECN marking for L4S, it shall guarantee that any sender (UE or Server) requesting classic ECN congestion control will not tag its packets with the ECT(1) in order to avoid conflicted usage of ECT(1) in L4S. Otherwise, L4S is not supported in network.'
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2207777 P-CR Approval 23.700-60: KI#3, Sol #41: update to remove one editor s note, clarification of impacts and correction/clarification of references Ericsson Rel-18 Revision of S2-2205829r02. WITHDRAWN Withdrawn
9.19 S2-2205848 P-CR Approval 23.700-60: KI#3, Update Sol#41: add clarification Vivo Rel-18 r02 agreed. Revised to S2-2207778. Paul (Ericsson) provides comments. This proposal takes away the benefit of sol #41 which is minimizing impacts on standards and interfaces. Hence, given the new changes are not needed, we do not agree to this solution update and propose to note this contribution.
Xiaowan(vivo) replies to Paul (Ericsson):we disagree with your comments. Sol#41 relies on UE and server capability of L4S. 5GS cannot distinguish L4S support or ECN support from ECT(1) in the real deployment. Since the link between the UE and AS may hybrid support of L4S or ECN. Without UE capability of L4S and AF request we don't see the solution make sense. Two companies paper raise the UE capability impact in 5845/ 6772.
Devaki (Nokia) proposes r01.
Curt (Meta) agrees with Ericsson.
Devaki (Nokia) posting the correct doc r01.
Paul (Ericsson) clarifies and provides r02.
Chunshan (CATT) comments on the L4S static activation.
Paul (Ericsson) provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207778 P-CR Approval 23.700-60: KI#3, Update Sol#41: add clarification Vivo Rel-18 Revision of S2-2205848r02. Approved Approved
9.19 S2-2205936 P-CR Approval 23.700-60: KI#3 Solution#46 Update Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207779 Yali (OPPO) comments and proposes to address the L4S enabling issue in S2-2205996.
Devaki (Nokia) replies to Yali.
Yali (OPPO) replies to Devaki (Nokia) and proposes merge this paper in S2-2205996.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2205996 P-CR Approval 23.700-60: KI#3, Sol#41,43,46: Update of enabling use of ECN OPPO Rel-18 r04 agreed. Revised to S2-2207779, merging and S2-2205936 Yali (OPPO) replies to Hui (Huawei) and proposes to address the L4S enabling issue in this thread.
Hui (Huawei) proposes to merge this paper into S2-2205829, S2-2205936 and S2-2206230 correspondingly.
Yali (OPPO) provides r01.
Paul (Ericsson), question for clarification to Yali (OPPO).
Yali (OPPO) replies to Paul (Ericsson).
Paul (Ericsson) replies to Yali (OPPO) and ask questions for clarification.
Mukesh (MediaTek) provides r02.
Curt (Meta) asks for further clarification on its problem statement.
Devaki (Nokia) comments.
Yali (OPPO) replies to Paul (Ericsson), Curt (Meta) ,Devaki (Nokia) and provides r03 .
Hui (Huawei) have concerns on one paper to update multiple solutions.
Hui (Huawei) clarify that sol43 has already supported AF triggered ECN marking.
Yali (OPPO) replies to Hui (Huawei) and provides r04.
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) can live with r04; since this copies content from our paper as-is for our solution update, we can also cosign.
Paul (Ericsson) can accept r04.
Yali (OPPO) thank Nokia for the cosign.
Hui (Huawei) fine with r04.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207779 P-CR Approval 23.700-60: KI#3, Sol#41,43,46: Update of enabling use of ECN OPPO Rel-18 Revision of S2-2205996r04, merging and S2-2205936. Approved Approved
9.19 S2-2206261 P-CR Approval 23.700-60: KI#3, sol#6, update and clarification on the Requested Alternative QoS Parameter Sets from AF Tencent, Tencent Cloud Rel-18 r01 agreed. Revised to S2-2207780. Chunshan (CATT) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207780 P-CR Approval 23.700-60: KI#3, sol#6, update and clarification on the Requested Alternative QoS Parameter Sets from AF Tencent, Tencent Cloud Rel-18 Revision of S2-2206261r01. Approved Approved
9.19 S2-2206230 P-CR Approval 23.700-60: KI#2, Sol#43 update on uplink services Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207781. Yali (OPPO) comments and proposes to address the L4S enabling issue in S2-2205996.
Chunshan (CATT) comments on steps 8a/b/c.
Hui (Huawei) provides r01.
Yali (OPPO) provides r02.
Hui (Huawei) asks question to Yali (OPPO).
Mukesh (MediaTek) provides comment.
Hui (Huawei) replies.
Curt (Meta) provides a view...
Hui (Huawei) responses.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207781 P-CR Approval 23.700-60: KI#2, Sol#43 update on uplink services Huawei, HiSilicon Rel-18 Revision of S2-2206230r02. Approved Approved
9.19 S2-2206513 P-CR Approval 23.700-60: FS_XRM_KI#3 Sol#47 EN Remove Xiaomi Rel-18 r02 agreed. Revised to S2-2207782. Devaki (Nokia) comments.
Jinhua (Xiaomi) replies to Devaki,
Dan (China Mobile) comments to Jinhua and the new NOTEs are not correct
Jinhua (Xiaomi) replies to Dan, with r02 provided.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207782 P-CR Approval 23.700-60: FS_XRM_KI#3 Sol#47 EN Remove Xiaomi Rel-18 Revision of S2-2206513r02. Approved Approved
9.19 S2-2206772 P-CR Approval 23.700-60: New Solution: Supporting ECN in 5GS for XR/media Enhancements China Mobile Rel-18 r06 agreed. Revised to S2-2207783. Devaki (Nokia) provides r01.
Devaki (Nokia) replies to Xiaowan (Vivo).
Xiaowan(vivo) questions to Devaki (Nokia) when UE /server support ECN, ECT(0) or ECT(1) is used in application layer, when the UE/server support L4S, ECT(1) is used, then how RAN/UPF understand the UE/Server has capability of L4S from ECT(1), please clarify
Xiaowan Ke(vivo) replies Devaki (Nokia) that source (UE/server) support ECN but doesn't support L4S and using ECT(1), RAN support L4S, the mis-operation at source will happen. Since the ECN source node will misunderstand the received L4S congestion mark ('lighter congestion') as ECN CE 'heavier congestion' and over react it.
Chunshan (CATT) comments.
Xiaowan Ke(vivo) provides r02
Dan(China Mobile) reply
Chunshan (CATT) comments that the TCP/RTP is not application layer.
Dan (China Mobile) provide r03 with updating the application layer description
Paul (Ericsson) provides comments and questions for clarification.
Dan (China Mobile) provides r04 and reply
Devaki (Nokia) comments
Curt (Meta) agrees with Paul (Ericsson) that NAS level indication to support L4S is not required.
Dan (China Mobile) reply and provide r05 and r06
==== 9.X, 10.X Revisions Deadline ====
Devaki (Nokia) prefers r05.
Curt (Meta) prefers r05.
Dan(China Mobile) ok for r05 and r06, suggest to go with r05.
Paul (Ericsson) provides comments and a question for clarification). We can live with r06.
Paul (Ericsson) proposes to move forward with r06.
Paul (Ericsson) can accept r06 and objects to all other revisions.
==== 9.X, 10.X Final Deadline ====
Dan(China Mobile) can accept r06
Revised
9.19 S2-2207783 P-CR Approval 23.700-60: New Solution: Supporting ECN in 5GS for XR/media Enhancements China Mobile Rel-18 Revision of S2-2206772r06. Approved Approved
9.19 - - - KI3 evaluation & conclusion - - Docs:=2 -
9.19 S2-2205937 P-CR Approval 23.700-60: Conclusions for KI#3 for Congestion control Nokia, Nokia Shanghai Bell Rel-18 r36 agreed. Revised to S2-2207784. Curt (Meta) supports this conclusion and would like to co-sign.
Zhuoyun (Tencent) provides r04.
Devaki (Nokia) provides r03.
Curt (Meta) provides r02.
Dario (Qualcomm) comments and provides r01
Chunshan(CATT) provides r05.
Hui(Huawei) provides r06.
Hui (Huawei) replies to Dario
Paul (Ericsson) provides r07.
Dan (China Mobile) provides r08
Xiaowan Ke(vivo) provides r09 and comments
Devaki (Nokia) provides r10.
Chunshan (CATT) provides r11.
Zhuoyun (Tencent) provides r13.
Chunshan (CATT) provides r14.
Jinhua (Xiaomi) provides comments and 5937r15.
Jinhua (Xiaomi) provides 5937r16.
Hui (Huawei) provides r17.
Xiaowan Ke(vivo) provides r18
Chunshan (CATT) provides r19.
Paul (Ericsson) provides comments and asks questions for clarification.
Hui (Huawei) comments.
Xiaowan (vivo) replies to Paul (Ericsson)
Hui(Huawei) replies to Paul.
Xiaowan Ke(vivo) replies to Hui (Huawei)
Dario (Qualcomm) asks questions for clarification and provides r20.
Zhuoyun (Tencent) provides r21.
Hui (Huawei) provides r22.
Paul (Ericsson) provides r23.
Mengzhen (China Telecom) provide r24.
Xiaowan (vivo) comments and think we need a LS to RAN about the per QoS flow congestion
Paul (Ericsson) provides comments and asks questions for clarification to Mengzhen (China Telecom) and Xiaowan Ke (vivo).
Xiaowan Ke(vivo) replies to Paul (Ericsson)
Paul (Ericsson) provides r25.
Yali (OPPO) provides r26.
Dan(China Mobile) support to add back the normal data transmission interruption event back
Curt (Meta) supports Vivo/Oppo (e.g, with r26).
Paul (Ericsson) replies to Xiaowan Ke (vivo).
Xiaowan Ke (vivo) replies to Paul (Ericsson) and also provides comments
Devaki (Nokia) provides r27.
Chunshan (CATT) concerns on the UPF to mark L4S CE.
Hui(Huawei) provides comments.
Hui (Huawei) replies to Chunshan.
Hui (Huawei) provides r28.
Mukesh (MediaTek) agrees with Vivo and comments.
Paul (Ericsson) provides r29.
Xiaowan (vivo) provides r30
Dan (China Mobile) provides r31
Jinhua (Xiaomi) replies to Devaki, and provides r33(based on 31fromDan), r34(based on 29fromPaul)
Chunshan (CATT) provides r35.
Hui (Huawei) provides r36 and object to any version from r30-r35.
Xiaowan Ke(vivo) provides r37
Devaki (Nokia) comments that r37 is almost 'voiding' the whole conclusion by making everything an EN, proposes to go with r36 or another version acceptable to all.
Paul (Ericsson) shares Devaki's view.
Xiaowan(vivo) replies Devaki (Nokia) and r36 is unfair to all the options
Devaki (Nokia) comments.
==== 9.X, 10.X Revisions Deadline ====
Hui(Huawei) clarify r36 is fair to all the option. We prefer to a conclusion without delaying the progress.
Curt (Meta) suggests a way forward
Dieter (Deutsche Telekom) shares Devaki's and Paul's view.
Devaki (Nokia) comments that r36 already includes API based approach, also includes EN to check with RAN WGs (addressing Xiaowan's concern). Proposes to go with r36.
Dario (Qualcomm) can accept r36 or r37 with extension of EN and change 'QNC for GBR QoS Flow'.
Devaki (Nokia) is ok with the extension to EN and QNC for GBR QoS Flow as proposed by Dario (Qualcomm).
Hui (Huawei) is ok with Dario's proposal but the revision needs following change.
Xiaowan (vivo) replies to the EN
Zhuoyun (Tencent) is fine with r36 and extending the EN, but needs some clarification on the extended EN, objects to r00-r03, r20.
Zhuoyun (Tencent) is also fine with r37 with the extended EN.
Paul (Ericsson), we can accept r36 with the EN proposed by Hui (Huawei).
Devaki (Nokia) proposes to go with r36 (objects r37 as it is voiding the conclusion) along with 'QNC for GBR QoS Flow' and updated EN: Editor's note: Supports for L4S and for exposure of congestion level, Data rate, delay difference and round trip delay, isare pending RAN WG's feedback on the feasibility of RAN judgment and/or exposure of the corresponding info (e.g. per QoS flow congestion level).
Dan (China Mobile) proposes to go with r36 along with the updated EN: 'QNC for GBR QoS Flow' and updated EN: Editor's note: Supports for L4S and for exposure of congestion level, Data rate, delay difference and round trip delay, isare pending RAN WG's feedback on the feasibility of RAN judgment and/or exposure of the corresponding info (e.g. per QoS flow congestion level).
Chunshan (CATT), we can accept r36 with the EN proposed by Hui (Huawei).
Curt (Meta), we can accept r36 with the EN proposed by Hui (Huawei).
Dan (China Mobile) think the new EN provide by Dario is not correct
Paul (Ericsson) we can accept r36 with Dario's version of the EN as well. We can also accept r07, r23, r25, r27, r29 and object to all other revisions.
Hui (Huawei) we can accept r22, r28, r36, with or without the following EN. Objects to r00 and other revisions.
Dan (China Mobile) request for CC#5. we suggest to go with r36+ EN provided by Hui
Editor's note: Support for L4S options and for exposure of congestion level, Data rate, delay difference and round trip delay, is pending RAN WG's feedbacks on the feasibility of RAN judgment and/or exposure of the corresponding info (e.g. per QoS flow congestion level)
==== 9.X, 10.X Final Deadline ====
Dario (Qualcomm) is ok with 36 plus
1) New EN by Hui,
2) New EN 'the semantics of the exposed congestion level is FFS'',
3) Add 'QoS' after 'QNC for',
4) Remove 'Data rate, delay difference and round trip delay'',
5) New EN 'which information is exposed by which entity and how it is obtained is FFS''
Devaki (Nokia) comments it should be:
1) New EN by Hui,
2) New EN 'the semantics of the exposed congestion level is FFS'',
3) Add 'GBR' after 'QNC for' and before 'QoS Flow',
4) Remove 'Data rate, delay difference and round trip delay'',
5) New EN 'which information is exposed by which entity and how it is obtained is FFS''
Zhuoyun (Tencent) proposes to postpone this contribution. We objects to 4) removing 'Data rate, delay difference and round trip delay''. These parameters can be measured and exposed by UPF in the related solutions in the TR. We could accept 5)Adding New EN 'which information is exposed by which entity and how it is obtained is FFS' as compromise.
Chunshan (CATT) objects to add 'GBR' after 'QNC for' and before 'QoS Flow'. Other parts are OK .
Hui(Huawei) is ok with 36 plus New EN by Hui, but objects the second EN 'the semantics of the exposed congestion level is FFS'',. Questions for last EN.
Hui(Huawei) proposes a way forward.
Chunshan (CATT) comments.
Dan(China Mobile) proposes a way forward based on Hui's version
Revised
9.19 S2-2207784 P-CR Approval 23.700-60: Conclusions for KI#3 for Congestion control Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205937r36. Approved Approved
9.19 - - - KI4 &5 new sol and sol update - - Docs:=41 -
9.19 S2-2206882 LS OUT Approval [DRAFT] LS on PDU Set QoS framework Qualcomm Incorporated Rel-18 Noted Hui (Huawei) clarified this LS should align with (interim) conclusion of KI 4/5 before sending out.
Saso (Intel) proposes to NOTE the LS because the corresponding conclusion papers on KI 4 and 5 are not being handled in this meeting.
Devaki (Nokia) comments.
Dario (Qualcomm) proposes to wait before noting the LS.
Dario (Qualcomm) replies to Devaki
Hui (Huawei) comments on the LS contents.
Paul (Ericsson) provides comments.
Chris (Vodafone) says PSDB should run from 1st PDU
Xiaowan(vivo) shares the view of Chris (Vodafone) : PSDB should run from 1st PDU
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) replies to Paul and is OK w/ noting the LS.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2206883 LS OUT Approval [DRAFT] LS on N6 PDU Set identification and marking Qualcomm Incorporated Rel-18 CC#5: r04 agreed. Revised to S2-2207887. Hui (Huawei) provides comments.
Devaki (Nokia) shares the same view as Hui, believes that the LS out might be a bit too pre-mature. Proposes to note the LS out for this meeting.
Paul (Ericsson) shares also the view that this LS is premature and proposes to note it.
Hui (Huawei) proposes to revise this paper to ask further questions identified during the meeting to SA4, and provide r01.
Saso (Intel) supports r01; asks a question.
Paul (Ericsson) asks question for clarification.
Paul (Ericsson) provides r02.
==== 9.X, 10.X Revisions Deadline ====
Hui (Huawei) replies to Paul.
Dario (Qualcomm) is OK w/ r01 with change '. If yes' --> ', and'.
Dario (Qualcomm) is NOT OK with r02.
Xiaowan Ke(vivo) disagrees the original version and all the revisions.
Hui (Huawei) asks questions.
Xiaowan Ke(vivo) replies to Hui (Huawei) : I can revoke my objection to r01 if r01 add. 'SA2 would like to ask SA4 whether the following scenario exists for some XR service flow: the non-I frames(e.g. P frame or B frame) transmitted/decoded between two successive I frames directly or indirectly refers to the 1st I frame of the two successive I frames'
Hui (Huawei) thanks Xiaowan for revoking the objection and would like to check other's views.
Saso (Intel) replies to Hui (Huawei) that the third question should be checked with Curt.
Hui (Huawei) proposes a draft to continue the discussion until CC#5.
Devaki (Nokia) objects to the original version. R03 (= r01 + 3 changes) could be considered but this is after the deadline thus needs further time for review.
Devaki (Nokia) comments that the LS out to other groups should be based on items with larger consensus in SA2, not simply based on individual solutions.
Hui (Huawei) replies to Devaki.
Zhuoyun (Tencent) is fine with the draft and would like to continue the discussion on it.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207887 LS OUT Approval [DRAFT] LS on N6 PDU Set identification and marking Qualcomm Incorporated Rel-18 Revision of S2-2206883r04. Approved Approved
9.19 S2-2205840 DISCUSSION Approval Discussion on KI#4&5 Vivo Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205639 P-CR Approval 23.700-60: KI #4, 5, Sol #7: Update to remove EN, other solution updates Futurewei Rel-18 r01 agreed. Revised to S2-2207785. Hui (Huawei) provides comments.
John (Futurewei) replies to Hui (Huawei).
Markus (Nokia) comments.
Dario (Qualcomm) comments.
John (Futurewei) comments.
Saso (Intel) comments.
Curt (Meta) comments.
John (Futurewei) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207785 P-CR Approval 23.700-60: KI #4, 5, Sol #7: Update to remove EN, other solution updates Futurewei Rel-18 Revision of S2-2205639r01. Approved Approved
9.19 S2-2205830 P-CR Approval 23.700-60: KI #4, Sol #8: update to remove ENs, add a MASQUE variant and clarify procedures and impacts Ericsson Rel-18 r01 agreed. Revised to S2-2207786. Hui (Huawei) proposes comments.
Markus (Nokia) asks questions.
John (Futurewei) comments and asks questions.
Markus (Nokia) comments.
Saso (Intel) comments.
Dario (Qualcomm) asks a question for clarification
Paul (Ericsson) provides response to Dario and r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207786 P-CR Approval 23.700-60: KI #4, Sol #8: update to remove ENs, add a MASQUE variant and clarify procedures and impacts Ericsson Rel-18 Revision of S2-2205830r01. Approved Approved
9.19 S2-2205838 P-CR Approval 23.700-60: KI#4&5, New Sol: PDU Set identification for the traffic transmitted via HTTPS Vivo Rel-18 Noted Hui (Huawei) provides comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205839 P-CR Approval 23.700-60: KI#4&5, New Sol: Inter PDU Set Dependency Vivo Rel-18 Noted Hui (Huawei) provides comments.
Youngkyo(Samsung) ask questions.
Markus (Nokia) provides comments, asks to consider all dependency information available in IETF framemarking RTP extension header draft.
HI Xiaowan(vivo) replies to Youngkyo(Samsung)
Xiaowan(vivo) replies to Hui (Huawei)
Chunshan(CATT) agree with Markus (Nokia) , asks to consider all dependency information available in IETF framemarking RTP extension header draft.
Dario (Qualcomm) comments
Xiaowan Ke(vivo) replies to the comments from (Qualcomm)
Hui(Huawei) provides comments.
Curt (Meta) provides comments.
Xiaowan Ke(vivo) provides r01 and replies
Mukesh (MediaTek) asks for clarification.
Xiaowan(vivo) replies to Mukesh (MediaTek).
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) proposed to note the paper.
Xiaowan(vivo) replies to Dario (Qualcomm)
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205841 P-CR Approval 23.700-60: KI#4&5, Update Sol#52: add clarification and clear Ens Vivo Rel-18 Merged into S2-2207790 Devaki (Nokia) comments.
Dario (Qualcomm) comments and asks questions for clarification.
Mike (InterDigital) provides r01
Xiaowan (vivo) replies comment from Devaki (Nokia) and Dario (Qualcomm), and propose to merge this paper into S2-2206231
Hui (Huawei) supports to consider this paper as merged into S2-2206231
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206001 P-CR Approval 23.700-60: KI#4, Sol#15,52: update to generate PDU Set related info based on existing RTP OPPO Rel-18 r03 agreed. Revised to S2-2207787. Mukesh (MediaTek) clarification needed.
Yali(OPPO) replies to Mukesh (MediaTek).
Dario (Qualcomm) comments
Devaki (Nokia) comments.
Yali(OPPO) replies to Dario (Qualcomm), Devaki (Nokia) ,and provides r01.
Yali(OPPO) provides r02 to remove the sol#52 part.
Yali(OPPO) is fine with r03.
Dario (Qualcomm) provides r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207787 P-CR Approval 23.700-60: KI#4, Sol#15,52: update to generate PDU Set related info based on existing RTP OPPO Rel-18 Revision of S2-2206001r03. Approved Approved
9.19 S2-2205911 P-CR Approval 23.700-60: KI #4 and KI#5, Solution #52 Update: Resolving ENs on peer-to-peer communication and Uplink QoS InterDigital Inc. Rel-18 Postponed Dario (Qualcomm) comments.
Hui (Huawei) proposes to consider this paper as merged into S2-2206231.
Mike (InterDigital) comments that there is no need to merge this with 6231 and that the changes do not conflict
==== 9.X, 10.X Revisions Deadline ====
Yali (OPPO) proposes to mark this paper as merged into S2-2206231 or Noted.
Hui (Huawei) proposes to postpone this paper.
Mike (InterDigital) replies to Hui (Huawei) and Yali (OPPO) and comments that marking this paper as merged into 6231 is not acceptable to because no content was merged.
==== 9.X, 10.X Final Deadline ====
Postponed
9.19 S2-2205938 P-CR Approval 23.700-60: KI#4 & 5 Solution Update Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207790 Devaki (Nokia) replies to Curt.
Curt (Meta) needs some clarifications...
Dario (Qualcomm) asks questions for clarification.
Devaki (Nokia) comments.
Paul (Ericsson) asks questions for clarification.
Zhuoyun (Tencent) comments.
Mukesh (MediaTek) asks for clarification.
Hui (Huawei) asks for clarification.
Paul (Ericsson) asks a question for clarification.
Kenichi (KDDI) asks for clarification.
Devaki (Nokia) replies to the comments raised.
Paul (Ericsson) provides comments and asks questions for clarification.
Hui (Huawei) replies to Devaki.
Devaki (Nokia) provides r01.
Yali (OPPO) comments.
Paul (Ericsson) provides comments and questions.
Devaki (Nokia) provides r03.
Yali (OPPO) comments on r03.
Zhuoyun (Tencent) provides r04.
Hui (Huawei) provides comments on paper handling.
Zhuoyun (Tencent) provides the link for r04.
Saso (Intel) proposes to NOTE this paper or consider it merged in 6231.
Devaki (Nokia) comments Intel concerns/objection raised hours before the revision deadline unfortunately. This is still a solution update and not a conclusion thus it should be allowed to consider technically feasible options. Feasibility of PDU Set group isn't the question here rather companies have different views on the need for it.
==== 9.X, 10.X Revisions Deadline ====
Hui (Huawei) replies to Devaki and suggest to merge this in S2-2206231.
Zhuoyun (Tencent) is fine with merging this in S2-2206231.
Paul (Ericsson) asks Devaki question for clarification.
Devaki (Nokia) replies to Paul.
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206210 P-CR Approval 23.700-60: KI#4, sol#23, solution update Tencent, Tencent Cloud Rel-18 r01 agreed. Revised to S2-2207788. Haley (Lenovo) asks for clarification.
Hui (Huawei) asks for clarification.
Zhuoyun (Tencent) provides r01 and replies to Haley and Hui.
Zhuoyun (Tencent) replies to Haley.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207788 P-CR Approval 23.700-60: KI#4, sol#23, solution update Tencent, Tencent Cloud Rel-18 Revision of S2-2206210r01. Approved Approved
9.19 S2-2206216 P-CR Approval 23.700-60: KI#4, New solution on PDU set handling enhancements for different kinds of packets Tencent, Tencent Cloud Rel-18 r01 agreed. Revised to S2-2207789. Hui (Huawei) asks for clarification.
Zhuoyun (Tencent) replies to Hui.
Dario (Qualcomm) asks questions for clarification
Zhuoyun (Tencent) replies.
Devaki (Nokia) comments
Curt (Meta) comments...
Dario (Qualcomm) asks further questions.
Hui (Huawei) replies to Devaki
Paul (Ericsson) provides comments and raises concerns to this proposal due to impacts to fundamental RAN architecture.
Zhuoyun (Tencent) provides r01 and replies to Paul.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) objects to r0 and r1
Zhuoyun (Tencent) replies and suggests Dario to further consider the revisions.
Zhuoyun (Tencent) suggests to go forward with r01+ removing the examples + rewording the NOTE as 'If certain parameters can't be differentiated for PDU Sets of different PDU Set types, they are common to all PDU sets.'
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207789 P-CR Approval 23.700-60: KI#4, New solution on PDU set handling enhancements for different kinds of packets Tencent, Tencent Cloud Rel-18 Revision of S2-2206216r01. Approved Approved
9.19 S2-2206231 P-CR Approval 23.700-60: KI#4 and #5, Sol#52 update Huawei, HiSilicon Rel-18 r27 agreed. Revised to S2-2207790, merging S2-2205841, S2-2205938, S2-2206284, S2-2206514, S2-2206663, S2-2206785 and S2-2206812 Hui (Huawei) provides r01 and some key questions for discussion.
Xiaowan Ke(vivo) provides r02 and supports to discuss the key questions raised by Hui (Huawei) in order to move forward
Mike (InterDigital) comments on the merge process
Dario (Qualcomm) comments on the merge process
Xiaowan Ke(vivo) updates the key question provided by Hui(Huawei)
Hui (Huawei) replies to Mike.
Hui (Huawei) provides question list for collecting company views. Please feedback before EoB of Saturday.
Paul (Ericsson ) provides comments. The approach to start evaluation/collection of opinions of solutions to KI#4 and KI#5 in the middle of the ongoing meeting and under a single solution update proposal without a former discussion and agreement is not acceptable to us.
Hui (Huawei) proposes r05.
Hui (Huawei) replies to Paul, Devaki, Mike.
Dario (Qualcomm) provides r04 and asks questions for clarification
John (Futurewei) adds missing option for Q2 - DL PDU set in v1.
Devaki (Nokia) comments.
Mike (InterDigital) agrees with Paul (Ericsson)
Hui(Huawei) provides r07
Hui(Huawei) replies to Saso.
Saso (Intel) seeks clarification on r07.
Curt (Meta) seeks clarification from this paper...
Mukesh (MediaTek) provides comment.
Zhuoyun (Tencent) comments.
Jinguo(ZTE) agree with Mukesh (MediaTek) and Curt (Meta)
Jinguo(ZTE) provides comments
Mike (InterDigital) provides r09
Devaki (Nokia) provides r08, but I also think the revisions are being disguised as a merger while none of the revisions are really a merger of the papers proposing updates to solution #52. Honestly one option might be to simply do a moderated email discussion prior to October meeting to reach a proper conclusion for KI#4/5.
Hui (Huawei) provides comment to r08.
Hui(Huawei) replies to Jinguo(ZTE)
Hui (Huawei) replies to Zhuoyun.
Hui (Huawei) replies to Mukesh.
Hui (Huawei) responses to Curt.
Yali(OPPO) comments.
Mengzhen (China Telecom) asks a question.
Hui(Huawei) provides r10 and replies to Yali.
Hui (Huawei) replies to Mengzhen.
Mengzhen (China Telecom) replies to Hui.
Saso (Intel) provides r11.
Jinhua (Xiaomi) provides comments,
Curt (Meta) provides comments,
Hui (Huawei) replies to Devaki.
Ellen (Google) provides lucky number r13 and comments,
Hui (Huawei) provides r14.
Kenichi (KDDI) provide r15.
Hui (Huawei) replies to Kenichi.
Xiaowan Ke(vivo) provides r17
Hui (Huawei) comments to r17.
Xiaowan(vivo) relies to Hui (Huawei)
John (Futurewei) comments.
Saso (Intel) provides r18 as proposed by John (Futurewei).
Xiaowan Ke(vivo) provides r19
Dario (Qualcomm) comments and provides r20.
Jinhua(Xiaomi) comments and provides r21.
Devaki (Nokia) provides r22.
Xiaowan (vivo) provides r23
Saso (Intel) provides r24
Devaki (Nokia) provides r25.
Devaki (Nokia) provides r26 to expand an existing EN regarding differentiation on PSDB, PSER per PDU Set.
Saso (Intel) provides r27
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) is OK with r20-24, 27 (which arrived at 16:00UTC). Object to the other revisions.
Hui (Huawei) suggests to go with r27.
Xiaowan (vivo) is OK with r27
Zhuoyun (Tencent) is fine with r27, r26.
Devaki (Nokia) can accept only r25-27, objects to other revisions.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207790 P-CR Approval 23.700-60: KI#4 and #5, Sol#52 update Huawei, HiSilicon Rel-18 Revision of S2-2206231r27, merging S2-2205841, S2-2205938, S2-2206284, S2-2206514, S2-2206663, S2-2206785 and S2-2206812. Approved Approved
9.19 S2-2206284 P-CR Approval 23.700-60: Key Issues #4 and #5 update of Solution #52 Lenovo Rel-18 Merged into S2-2207790 Dario (Qualcomm) comments.
Devaki (Nokia) comments.
Hui (Huawei) suggests to merge this paper into S2-2206231.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206285 P-CR Approval 23.700-60: New solution for KI#4 and #5 PDU set handling capability of RAN node Lenovo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206323 P-CR Approval 23.700-60: Update of solution 50 Sony Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206326 P-CR Approval 23.700-60: New solution to support PDU Set with FEC Data for KI 4 and 5 Sony Rel-18 Approved Markus (Nokia) does not agree with the solution.
Hui (Huawei) provides comments.
Svante (Sony) provides answers.
Markus (Nokia) comments and asks a question.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206328 P-CR Approval 23.700-60: KI#5, Update on Solution#53 PDU Set transmission coordination between RAN and UPF Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207791. Mukesh (MediaTek) provides comment.
Xinpeng(Huawei) replies to Mukesh (MediaTek).
Xinpeng(Huawei) replies to Mukesh (MediaTek) and provides r01.
Mukesh (MediaTek) replies to Xinpeng (Huawei) and provides r02.
Xinpeng(Huawei) asks for clarification.
Mukesh (MediaTek) replies to Xinpeng (Huawei) and provides r03.
Xinpeng(Huawei) provides r04.
Mukesh (MediaTek) agrees with r04.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207791 P-CR Approval 23.700-60: KI#5, Update on Solution#53 PDU Set transmission coordination between RAN and UPF Huawei, HiSilicon Rel-18 Revision of S2-2206328r04. Approved Approved
9.19 S2-2206338 P-CR Approval 23.700-60: Solution update for Sol#12 China Mobile Rel-18 Merged into S2-2207792 Dan (China Mobile) merging this paper into S2-2206605
Kenichi (KDDI) fine with merging into S2-2206605.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206605 P-CR Approval 23.700-60: KI #4, Sol #12: Update to resolve EN KDDI Rel-18 r01 agreed. Revised to S2-2207792, merging and S2-2206338 Dan (China Mobile) provide r01 with merging S2-2206338 into this paper
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207792 P-CR Approval 23.700-60: KI #4, Sol #12: Update to resolve EN KDDI Rel-18 Revision of S2-2206605r01, merging and S2-2206338. Approved Approved
9.19 S2-2206607 P-CR Approval 23.700-60: KI #5, Sol #24: Miscellaneous correction to Solution #24 KDDI Rel-18 r01 agreed. Revised to S2-2207793. Kenichi (KDDI) provides r01 to merge with S2-2206332.
Kenichi (KDDI) correct revision number (r1 -> r01).
Hui (Huawei) is fine with the revision.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207793 P-CR Approval 23.700-60: KI #5, Sol #24: Miscellaneous correction to Solution #24 KDDI Rel-18 Revision of S2-2206607r01. Approved Approved
9.19 S2-2206884 P-CR Approval 23.700-60: KI#4-5: Sol. 20 update Qualcomm Incorporated Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206885 P-CR Approval 23.700-60: KI#4-5: Sol. 25 update Qualcomm Incorporated Rel-18 Approved Paul (Ericsson) asks questions for clarification.
Dario (Qualcomm) repllies to Paul.
Paul (Ericsson) provides comments and questions.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) replies to Paul
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206663 P-CR Approval 23.700-60: FS_XRM KI#4_5 Sol52 update ZTE Rel-18 Merged into S2-2207790 Hui (Huawei) suggests to merge this paper into S2-2206231 to avoid conflicting update.
Dario (Qualcomm) comments.
Devaki (Nokia) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206692 P-CR Approval 23.700-60: KI#4 and KI#5, Sol #16: Update to remove ENs Apple Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206785 P-CR Approval 23.700-60: Sol#52 Update for PDU Set based QoS framework Google Inc. Rel-18 Merged into S2-2207790 Hui (Huawei) comments and suggest to merge this paper into S2-2206321.
Ellen (Google) replies to Nokia and QC
Dario (Qualcomm) comments.
Devaki (Nokia) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206812 P-CR Approval 23.700-60: KI#4/5: Attributes for PDU set Meta USA Rel-18 Merged into S2-2207790 Dario (Qualcomm) asks questions for clarification on how to handle this paper.
Curt (Meta) understood that any texts related to conclusion to KI#4/5 will not be considered in this e-meeting. SO we should only talk about the changes to Sol.52.
Yali (OPPO) asks a question.
Curt (Meta) replies to Yali (OPPO) and also provides R01.
Curt (Meta) provides r02
Yali(OPPO) comments on r01.
Jinhua (Xiaomi) comments and provides r03;
Hui (Huawei) suggests to consider this paper as merged into S2-2206231
Curt (Meta) is fine to set this paper as merged into S2-2206231.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2206514 P-CR Approval 23.700-60: FS_XRM_KI#4 KI#5 Sol#52 Update with Charging Offset Xiaomi Rel-18 Merged into S2-2207790 Dario (Qualcomm) asks questions for clarification.
Jinhua (Xiaomi) replies to Dario, agree with the proposal of Hui, merge 6514 into 6231 for discussion together is OK.
Hui (Huawei) confirm this paper is merged into S2-2206231.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 S2-2205912 P-CR Approval 23.700-60: KI #4 and 5, New Eval: Key Issue #4 and #5 Evaluation Text for Solution 55 InterDigital Inc. Rel-18 Postponed John (Futurewei) comments, requests addition to evaluation.
Mike (InterDigital) provide r01
Yali(OPPO) seeks for Rapporteur's guideline, could we agree evaluation for single solution in the chapter of KI#4&5 Overall Evaluation in this meeting?
Yali(OPPO) comments
Mike (InterDigital) comments
Hui(Huawei) comments
Saso (Intel) proposes to NOTE the contribution and work on a joint evaluation of all KI #4/5 solutions.
Mike (InterDigital) replies to Saso (Intel) and provides r02
Dario (Qualcomm) support Intel's proposal.
Saso (Intel) replies to Mike.
==== 9.X, 10.X Revisions Deadline ====
Yali(OPPO) proposes to mark this paper as POSTPONED, same as S2-2206354.
Dario (Qualcomm) supports postponing this paper.
==== 9.X, 10.X Final Deadline ====
Postponed
9.19 S2-2206354 P-CR Approval 23.700-60: KI#4 KI#5: Sol#56: Evaluation and Conclusion MediaTek Inc. Rel-18 Postponed Yali(OPPO) seeks for Rapporteur's guideline, could we agree the evaluation for single solution in the chapter of KI#4&5 Overall Evaluation in this meeting, and also the KI#4&5 conclusion?
Yali(OPPO) comments
Mukesh (MediaTek) provides r01.
Yali(OPPO) comments the conclusion part in this paper should be removed. 7.x is for overall evaluation, not a proper section for the evaluation of a single solution.
Devaki (Nokia) comments that rapporteur proposed rule is as follows '1) The Conclusion/Evaluation for KI 1&2,4&5 will not be handled for this emeeting. One thing needs to be clarified that one paper from MTK(6354) and one from Interdigital(5912) is to do evaluation and conclusion only for single solution, I suggest to try to keep it in handle list.'. It includes this paper in the handle list.
Curt (Meta) asks - according to Rapporteur, I thought there is no overall evaluation and conclusion for KI#4/5 (Section 7/8) in this meeting so this should be not handled(?)
Hui(Huawei) provides r02.
Jinhua (Xiaomi) provides comments and r03.
Yali(OPPO) comments.
Saso (Intel) proposes to NOTE the contribution and work on a joint evaluation of all KI #4/5 solutions.
Jinhua (Xiaomi) provides comments, the 6321 is prefer as the basis for the evaluation discussion, and 6354 is proposed to postpone to next meeting for the evaluation of Sol#56 which Sol#52 didn't covered.
Dario (Qualcomm) supports Intel's proposal to NOTE the contribution and work on an comprehesive evaluation of solutions for KI4/5.
Mukesh (MediaTek) agrees to postpone this paper with the understanding that it will be handled in #153e.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
9.19 - - - KI6 new sol and sol update - - Docs:=1 -
9.19 S2-2206232 P-CR Approval 23.700-60: KI#6, new solultion for RT latency based on UL/DL AQP Adaptation Huawei, HiSilicon Rel-18 Approved Boren (OPPO) asks question.
Devaki (Nokia) raises questions.
Hui (Huawei) replies to Boren.
Hui(Huawei) replies to Devaki.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.19 - - - KI6 evaluation and conclusion - - Docs:=2 -
9.19 S2-2205843 P-CR Approval 23.700-60: KI#6, Conclusions Vivo, China Mobile Rel-18 r09 agreed. Revised to S2-2207794. Devaki (Nokia) provides r01.
Boren (OPPO) provides r02.
Devaki (Nokia) replies to Dario.
Dario (Qualcomm) comments.
Xiaowan(vivo) replies to Devaki (Nokia) and provides r03
Boren (OPPO) replies to Dario (Qualcomm)
Paul (Ericsson) provides comments and questions for clarification.
Xiaowan(vivo) relies to Paul (Ericsson)
Paul (Ericsson) replies Xiaowan(vivo) and asks question for clarification, especially, to show the benefits of the solutions.
Xiaowan (vivo) replies
Boren (OPPO) replies to Paul (Ericsson).
Hui (Huawei) provides r06
Devaki (Nokia) provides r08.
Dario (Qualcomm) provides r07.
Hui (Huawei) replies to Devaki.
Xiaowan(vivo) share Hui (Huawei)'s reply and provided r09.
==== 9.X, 10.X Revisions Deadline ====
Dario (Qualcomm) can accept r07 (or r09 if the word 'NOTE' is removed). Other revs not acceptable.
Hui (Huawei) suggests go with r09 with the word 'NOTE' removed.
Lei (Tencent) is fine with r07,r08 and r09. To make progress, hope people can live with r07 or r09 with NOTE removed. And would like to co-sign.
Hui (Huawei) clarify the comments is r09 with only remove the word 'NOTE' not the whole NOTE.
Xiaowan Ke(vivo) also propose to agree r09 with removal of the word 'NOTE'.
Devaki (Nokia) can accept r09 with the removal of the term NOTE for the last note (in the interest of progress), wishes to cosign the final version.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207794 P-CR Approval 23.700-60: KI#6, Conclusions Vivo, China Mobile Rel-18 Revision of S2-2205843r09. Approved Approved
9.19 - - - KI7 new sol and sol update - - Docs:=2 -
9.19 S2-2206059 P-CR Approval 23.700-60: KI#7, Sol#30: Update to clarify solution procedure description Tencent, Tencent Cloud Rel-18 r02 agreed. Revised to S2-2207795. Devaki (Nokia) provides r01.
==== 9.X, 10.X Revisions Deadline ====
Lei(Tencent) is ok with r02 assuming consensus reached on the second bullet of KI interim conclusion i.e. r04+NOTE. Otherwise this pCR should be noted.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207795 P-CR Approval 23.700-60: KI#7, Sol#30: Update to clarify solution procedure description Tencent, Tencent Cloud Rel-18 Revision of S2-2206059r02. Approved Approved
9.19 - - - KI7 evaluation and conclusion - - Docs:=2 -
9.19 S2-2206060 P-CR Approval 23.700-60: KI#7: Evaluation of Solutions Tencent, Tencent Cloud Rel-18 r04 agreed. Revised to S2-2207796. Dario (Qualcomm) provides r01.
Lei (Tencent) provides comments and also r04.
Dario (Qualcomm) comments.
==== 9.X, 10.X Revisions Deadline ====
Lei(Tencent) is not against r03. And agree with Dario's suggestion to add NOTE on top of r04. Request to confirm this in CC#4 after talking with Rapporteur (Dan).
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207796 P-CR Approval 23.700-60: KI#7: Evaluation of Solutions Tencent, Tencent Cloud Rel-18 Revision of S2-2206060r04. Approved Approved
9.19 - - - KI8 new sol and sol update - - Docs:=7 -
9.19 S2-2206898 LS OUT Approval [DRAFT] LS on XR and Media Services vivo Response to S2-2205421. Noted Mukesh (MediaTek) provides r01
Xiaowan Ke(vivo) replies to Mukesh (MediaTek)
Mukesh (MediaTek) replies to Xiaowan Ke(vivo)
Boren (OPPO) provides r02
Mukesh (MediaTek) provides comment.
Dario (Qualcomm) comments.
Xiaowan(vivo) replies to Dario (Qualcomm) and provide r03
Jinhua (Xiaomi) replies to Mukesh (MediaTek),
Devaki (Nokia) comments that we need to have a coordinated LS out for KI#8/#9.
Xiaowan(ke) replies to Devaki (Nokia) and provide r04
Sudeep (Apple) also prefers to leave out the KI#9 question if this LS is moving forward.
Xiaowan Ke(vivo) Sudeep (Apple) and suggest to keep the question for KI#9
Saso (Intel) comments on r04.
Mukesh (MediaTek) supports Apple in removing KI#9 question.
Xiaowan(vivo) replies to Saso (Intel) and provides r05
Dan(China Mobile) provide r06
Hui(Huawei) provide r08, please ignore r07
Mike (InterDigital) provides r09 which merges in content from 5915
Xiaowan Ke(vivo) replies to Mike (InterDigital)
Xiaowan Ke(vivo) provides r10
Mike (InterDigital) provides r11
==== 9.X, 10.X Revisions Deadline ====
Jinhua (xiaomi) provides r11, with recovering the KI#9 question, for the progress.
Jinhua (xiaomi) comments, r11 is conflict with Mike, propose to add the text with recovering the KI#9 question, for the progress.
'KI#9 studies how to support trade-off of throughput/latency/reliability and power consumption (e.g. device battery life). SA2 seeks RAN2's feedback about the following UE battery aspects: Whether it is feasible for RAN to acquire the UE battery status and forward it the CN.'
Sudeep (Apple) confirms objection to any revision that includes question on KI#9. Can accept r06 or higher.
Jinhua (Xiaomi) replies to Mukesh, Apple share the view of MTK to remove KI#9 question first, then MTK supports Apple for removing KI#9 question. Confused becauseof the circle
Jinhua(Xiaomi) relies to Sudeep, 1)you objection send LS for neutral technical question becauseof no stable evaluation of the KI, and 2) MTK refuse the evaluation discussion becauseof their evaluation paper not handled, also 3) MTK don't agree to remove EN becauseof waiting for the LS feedback...It's still a loop.
Xiaowan Ke(vivo): r10 is the valid latest version and propose to agree r10
Sudeep (Apple) responds to Jinhua (Xiaomi).
Jinhua (Xiaomi) replies to Sudeep(Apple), thanks for identifying that the solution did not appear to rely on any RAN interaction.
Dan (China Mobile) suggest to go with r10 and this seems a possible version with the agreed content
Paul (Ericsson) asks question for clarification.
Xiaowan(vivo) replies to Paul (Ericsson) .
Hui(Huawei) replies to Paul (Ericsson) .
Jinhua (Xiaomi) comments, OK to go with r10. Call for CC#5, since Question from 6520 is not captured in r10, to check the consensus on: whether no required LS for UE battery to RAN;
Paul (Ericsson) can't accept r10, this LS needs more work before going to CC#5.
==== 9.X, 10.X Final Deadline ====
Xiaowan Ke(vivo) replies to Paul (Ericsson)
Xiaowan Ke(vivo) proposes to agree r10 with removal of 'And if RAN has any consideration about congestion, feedback is welcomed.' and request for CC#5
Mukesh (MediaTek) replies to Jinhua (Xiaomi), we have consensus (r10), and Xiaomi had plenty of time to make sure the merge (6520) was treated correctly, therefore CC#5 does not serve any purpose.
Xiaowan Ke(vivo) replies: r10 with the changes are ready to be agreed in CC#5: with addition of 'to RAN3' and removal of the last sentence of the paragraph for KI#3 and removal of the whole paragraph for KI#8
Noted
9.19 S2-2205421 LS In Action LS from RAN WG1: Reply LS on UE Power Saving for XR and Media Services RAN WG1 (R1-2205531) Rel-18 Responses drafted in S2-2205915, S2-2206898. Postponed Postponed
9.19 S2-2205915 LS OUT Approval [DRAFT] Reply LS on UE Power Saving for XR and Media Services InterDigital Inc. Rel-18 Response to S2-2205421. Noted Xiaowan (vivo) provides comment
Mike (InterDigital) replies
Xiaowan Ke(vivo) replies to Mike (InterDigital)
Devaki (Nokia) comments.
Mike (InterDigital) replies to Xiaowan (Vivo)
Xiaowan (Vivo) replies to Mike (InterDigital)
Mike (InterDigital) provides r01 and replies to Xiaowan (Vivo) and Devaki (Nokia)
Boren (OPPO) propose to merge this paper into S2-2206898.
Dan (China Mobile) propose to merge this paper into S2-2206898.
Mike (InterDigital) comments that he will propose a merge in the 6898 thread, but wonders if it is better to just use 5915 as the baseline
Xiaowan Ke(vivo) propose to note this paper
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2205693 P-CR Approval 23.700-60: New Solution for KI-8 -- Enhancements to power savings for XR Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207797. Paul (Ericsson) provides comments and asks questions for clarification.
Boren (OPPO) provides comments.
Michele (Huawei) provides r01 documenting additional impact on NWDAF
Michele (Huawei) provides clarifications as requested by Paul (Ericsson)
Boren (OPPO) comments.
Michele (Huawei) provides some clarifications to Boren (OPPO) wrt jitter statistics
Paul (Ericsson) asks question for clarification.
==== 9.X, 10.X Revisions Deadline ====
Michele (Huawei) replies to Paul (Ericsson).
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207797 P-CR Approval 23.700-60: New Solution for KI-8 -- Enhancements to power savings for XR Huawei, HiSilicon Rel-18 Revision of S2-2205693r01. Approved Approved
9.19 S2-2206151 P-CR Approval 23.700-60: KI#8: Update to Solution #33 for CDRX enhancement China Telecom Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 S2-2206274 P-CR Approval 23.700-60: KI#8, New Sol: Notification to XR AF of CDRX parameters reflecting UE's CDRX preference NTT DOCOMO Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.19 - - - KI8 evaluation and conclusion - - Docs:=2 -
9.19 S2-2206886 P-CR Approval 23.700-60: Ki#8: Evaluation and conclusions Qualcomm Incorporated Rel-18 r11 agreed. Revised to S2-2207798. CC#5: Noted and S2-2207798 was withdrawn. Mike (InterDigital) comments and provides r01.
Dario (Qualcomm) comments and provides r02.
Hui (Huawei) provides r03.
Paul (Ericsson) provides r04.
Xiaowan Ke(vivo) comments and provides r05
Paul (Ericsson) asks Xiaowan Ke (vivo) question for clarification.
Xiaowan Ke(vivo) replies to Paul (Ericsson)
Paul (Ericsson) asks question for clarification.
Curt (Meta) asks question for clarification.
Xiaowan Ke (vivo) asks question for clarification.
Paul (Ericsson) replies to Xiaowan Ke (vivo).
Mike (InterDigital) provides r06
Paul (Ericsson) replies to Curt (Meta).
Devaki (Nokia) comments.
Devaki (Nokia) provides r07.
Boren (OPPO) provides comments.
Curt (Meta) comments.
Paul (Ericsson) replies to Devaki (Nokia) and provides comments.
==== 9.X, 10.X Revisions Deadline ====
Lei(Tencent) accepts r03 and object to other revisions.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2207798 P-CR Approval 23.700-60: Ki#8: Evaluation and conclusions Qualcomm Incorporated Rel-18 Revision of S2-2206886r11. WITHDRAWN Withdrawn
9.19 - - - KI9 new sol and sol update - - Docs:=9 -
9.19 S2-2206518 DISCUSSION Discussion FS_XRM_DP_QoS enhancement to support Trade off of QoE and Power Consumption Xiaomi Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2206520 LS OUT Approval [DRAFT] LS on RAN_FS_XRM_Tradeoff of QoE and Power Saving Xiaomi Rel-18 Merged into S2-2206898 (noted). Noted Jinhua (Xiaomi) replies to Mukesh,
Mukesh (MediaTek) objects to this document.
Dan (China Mobile) replies to Mukesh,
Jinhua (Xiaomi) replies to Devaki (Nokia), keep it neutral is also prefer and r01 is fine for me.
Devaki (Nokia) prefers to consider this LS out only after we have a stable conclusion in SA2, if there is majority to support to send the LS out, I would prefer that the LS out doesn't refer to a specific solution rather keep it neutral thus I provide r01.
Xiaowan Ke(vivo) propose to merge this paper into S2-2206898
Jinhua (Xiaomi) replies to Xiaowan, merge 6520 into 6898 is OK for the discussion together.
Xiaowan Ke(vivo) replies Jinhua (Xiaomi)
==== 9.X, 10.X Revisions Deadline ====
Jinhua (Xiaomi) comments, R01 from Devaki is proposed for progress. (If the EN is still needed, because the solution don't rely on RAN interaction).
Jinhua (Xiaomi) comments, apologize for confusing, withdraw my last comments. It is already marked merged. Thanks.
==== 9.X, 10.X Final Deadline ====
Noted
9.19 S2-2206007 P-CR Approval 23.700-60: KI#9, New Sol: power mode based QoS adjustment OPPO Rel-18 r07 agreed. Revised to S2-2207799r07, merging and S2-2206647 Boren (OPPO) provides r01.
Jinhua (xiaomi) provides comments and r02,
Boren (OPPO) replies to Jinhua (xiaomi), and provides r03.
Jinhua (xiaomi) provides comments and 6007r04,
Mukesh (MediaTek) seeks clarification.
Boren (OPPO) provides r05.
Boren (OPPO) replies to Mukesh (MediaTek), and provides r07.
Devaki (Nokia) wonders whether this is a new solution and/or whether it needs to be documented separately? This seems very close to the solutions/conclusions proposed for KI#9. It would be better to merge this.
Boren (OPPO) replies to Devaki (Nokia), and prefers to keep this solution as a new solution since it has merged another new solution and is technically different from the existing solutions.
Mukesh (MediaTek) provides r08.
Boren (OPPO) replies to Mukesh (MediaTek).
==== 9.X, 10.X Revisions Deadline ====
Jinhua (Xiaomi) replies to Mukesh (MediaTek), you comment that 'EN added for the first option, which requires feedback from RAN', whether sending feasibility question to RAN is your prefer?
Boren (OPPO) proposes to agree with r07.
Jinhua (Xiaomi) proposes to go for r07,
==== 9.X, 10.X Final Deadline ====
Mukesh (MediaTek) r07 is agreeable.
Revised
9.19 S2-2207799 P-CR Approval 23.700-60: KI#9, New Sol: power mode based QoS adjustment OPPO Rel-18 Revision of S2-2206607r07, merging and S2-2206647. Approved Approved
9.19 S2-2206516 P-CR Approval 23.700-60: FS_XRM_KI#9 Sol#61 EN Remove and SMF procedure update Xiaomi Rel-18 r01 agreed. Revised to S2-2207800. Jinhua (xiaomi) provides comments and r01,
Mukesh (MediaTek) seeks clarification.
Jinhua (Xiaomi) replies to Mukesh (MediaTek),
Mukesh (MediaTek) provides r02.
Jinhua (Xiaomi) replies to Mukesh, r02 is OK, keep the EN is fine for now;.
==== 9.X, 10.X Revisions Deadline ====
Jinhua (Xiaomi) comments, r01 is proposed for approval. Not rely on any RAN interaction, no LS and feedback as recommended in r02.
Mukesh (MediaTek) replies to Jinhua(Xiaomi) accepts r01
Jinhua(Xiaomi) replies to Mukesh (MediaTek), thanks.
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207800 P-CR Approval 23.700-60: FS_XRM_KI#9 Sol#61 EN Remove and SMF procedure update Xiaomi Rel-18 Revision of S2-2206516r01. Approved Approved
9.19 S2-2206519 P-CR Approval 23.700-60: FS_XRM KI#9_NewSol_QoS enchancement to support Tradoff of QoE and Power consumption Xiaomi Rel-18 r01 agreed. Revised to S2-2207801. Jinhua (Xiaomi) replies to Devaki (Nokia), with r01 provided.
Devaki (Nokia) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.19 S2-2207801 P-CR Approval 23.700-60: FS_XRM KI#9_NewSol_QoS enchancement to support Tradoff of QoE and Power consumption Xiaomi Rel-18 Revision of S2-2206519r01. Approved Approved
9.19 S2-2206647 P-CR Approval 23.700-60: New solution for KI#9 China Mobile Rel-18 Merged into S2-2207799 Boren (OPPO) asks questions
Mike (InterDigital) comments and asks questions
Dan (China Mobile) reply and this paper is merged into S2-2206007
Jinhua (Xiaomi) provides comments,
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.19 - - - KI9 evaluation and conclusion - - Docs:=1 -
9.19 S2-2206342 P-CR Approval 23.700-60: Conclusion for KI#9 China Mobile Rel-18 Noted Mukesh (MediaTek) objects to this document.
Mike (InterDigital) comments and provides r01
Jinhua (Xiaomi) provides comments and r02,
Mukesh (MediaTek) relies to Jinhua (Xiaomi).
Boren (OPPO) objects to this document and all revisions.
Jinhua (Xiaomi) relies to Mukesh,
Mukesh (MediaTek) replies to Jinhua (Xiaomi),
Jinhua (Xiaomi) relies to Boren,
Jinhua (Xiaomi) replies to Mukesh (MediaTek),
Dan(China Mobile)provide r03
Guillaume (MediaTek Inc.) cannot accept r03, provides r04.
Hui (Huawei) asks for clarification.
Dan (China Mobile) OK for r04
Dan (China Mobile) reply
Sudeep (Apple) provides comments.
Devaki (Nokia) is fine with r04.
Jinhua (xiaomi) provides comments and r05. R04 cannot be acceptable because all solutions included in the TR are excluded.
Dario (Qualcomm) comments.
Jinhua (Xiaomi) comments. The interim conclusion can be agreed and is also prefer, the only concern is r04 can not be acceptable because the description of the conclusion have no any relationship with the TR except the ENs.
Jinhua (Xiaomi) comments. Seek the clarification of r04 provided by MediaTek.
Guillaume (MediaTek Inc.) comments. Objects to r05. Recommends r04 even if odd.
Jinhua (Xiaomi) replies to Guillaume, r06 is provided for progress.
Dan(China Mobile) replies to r06
Jinhua (Xiaomi) replies to Dan, agree that both r04 and 06 seems weird, r03/r05 is prefer, can live with r06;
Guillaume (MediaTek Inc.) recommends to proceed with r04
Jinhua (Xiaomi) replies to Guillaume, r07 is provide to catch the embryo of a workable conclusion and actions for SA2#153e, r04 is unacceptable.
Boren (OPPO) recommends to go with r07.
==== 9.X, 10.X Revisions Deadline ====
Dan(China Mobile) recommends to go with r07.
Guillaume (MediaTek Inc.) translates: objects to r07
Dan(China Mobile) recommends to check to go with r04 and request for CC#5
Jinhua (Xiaomi) replies to Guillaume, the evaluation part can be removed from r07 for progress. R04 is unacceptable.
==== 9.X, 10.X Final Deadline ====
Dan (China Mobile) provide r08v1 based on r07 to try to move forward.
Jinhua (Xiaomi) replies to Dan (China Mobile), can live with r08v1 as the compromise.
Guillaume (MediaTek Inc.) thanks Dan (CMCC) - ok with r08v1
Hui(Huawei) fine with r08v1
Dan(China Mobile) request this for CC#5 with updating r07:
1) removing evaluation part
2) changing the first EN into: Editor's Note: Whether and how UE status related information can be provided to 5GC to help PCF adjust the policy (e.g. the policy change criteria), will be decided in future meeting.
Noted
9.19 - - - Documents exceeding TU Budget - - Docs:=43 -
9.19 S2-2205832 P-CR Approval 23.700-60: KI#1 and KI#2, Solutions evaluation Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205909 P-CR Approval 23.700-60: KI #1, New Eval and New Conclusion: Key Issue #1 Evaluation and Conclusion InterDigital Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205910 P-CR Approval 23.700-60: KI #2, New Eval and New Conclusion: Key Issue #2 Evaluation and Conclusion InterDigital Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206707 P-CR Approval 23.700-60: KI#3, sol#5, solution update Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205846 P-CR Approval 23.700-60: KI#3, Evaluation and conclusion for L4S/ECN related Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205847 P-CR Approval 23.700-60: KI#3, Evaluation and conclusion for exposed parameters Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206236 P-CR Approval 23.700-60: KI#3, Evaluation Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206259 P-CR Approval 23.700-60: KI#3, Interim conclusion on CP-based solutions and UP-based solutions without ECN marking Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206811 P-CR Approval 23.700-60: KI#3: Way forward proposal (user plane congestion control) Meta USA Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206352 P-CR Approval 23.700-60: KI#3: Exposure information via QNC Notification: Evaluation and Conclusion MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206435 P-CR Approval 23.700-60: 23.700-60 KI #3: Evaluation and Conclusion for key issue #3 5GS information exposure for XR/media Enhancements CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206330 P-CR Approval 23.700-60: KI#3, sol#45 update EN Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206212 P-CR Approval 23.700-60: KI#4&5, sol#52, solution update Tencent, Tencent Cloud Rel-18 Not Handled Hui (Huawei) suggests to merge this paper into S2-2206231.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205640 P-CR Agreement 23.700-60: KI #4, 5 Criteria and Principles for Evaluation Futurewei Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205833 P-CR Approval 23.700-60: KI#4 and KI#5: Solutions evaluation and conclusions Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206353 P-CR Approval 23.700-60: KI#4 KI#5: Sol#52: Evaluation and Conclusion MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206355 P-CR Approval 23.700-60: KI#5: Sol#53: Evaluation and Conclusion MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206897 P-CR Approval 23.700-60: KI#4&5, interim conclusions Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206926 P-CR Approval 23.700-60: KI#4, KI#5: Initial conclusions Intel Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206881 P-CR Approval 23.700-60: Ki#4-5: Interim conclusions Qualcomm Incorporated Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206813 P-CR Approval 23.700-60: KI#4/5: PDU markings Meta USA Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206332 P-CR Approval 23.700-60: KI#5, sol#24 update Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206005 P-CR Approval 23.700-60: KI#6 Interim conclusion for uplink-downlink transmission coordination OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205842 P-CR Approval 23.700-60: KI#6, Overall evaluation Vivo, OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205939 P-CR Approval 23.700-60: Conclusions for KI#6 for Round Trip Delay Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206062 P-CR Approval 23.700-60: KI#6: Evaluation of solutions Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206233 P-CR Approval 23.700-60: KI#6 evaluation and conclusion Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206329 P-CR Approval 23.700-60: KI#8, Update on solution #33: support of CDRX enhancement for power saving handling Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206642 P-CR Approval 23.700-60: KI#8 & KI#9, Sol#34: Update to clarify solution procedure description Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206061 P-CR Approval 23.700-60: KI#7: Interim conclusion Tencent, Tencent Cloud Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206234 P-CR Approval 23.700-60: KI#7 evaluation and conclusion Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206299 P-CR Approval 23.700-60: Conclusion for KI#7 China Mobile Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205844 P-CR Approval 23.700-60: KI#8, Interim conclusions Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206235 P-CR Approval 23.700-60: KI#8 evaluation and conclusion Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206356 P-CR Approval 23.700-60: KI#8: Sol#58: Evaluation and Conclusion MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205913 P-CR Approval 23.700-60: KI #8, New Eval: Key Issue #8 Evaluation and Conclusion InterDigital Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205940 P-CR Approval 23.700-60: Conclusions for KI#8 and KI#9 for power savings Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206515 P-CR Approval 23.700-60: FS_XRM_KI#9 Sol#61 EN Remove about AMF procedure Xiaomi Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206517 P-CR Approval 23.700-60: FS_XRM_KI#9 Sol#61 EN Remove about the feasibility Xiaomi Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205849 P-CR Approval 23.700-60: KI#9, Interim conclusions Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2205914 P-CR Approval 23.700-60: KI #9, New Eval: Key Issue #9 Evaluation and Conclusion InterDigital Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206008 P-CR Approval 23.700-60: KI#9, Evaluation OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.19 S2-2206351 P-CR Approval 23.700-60: KI#9: Sol#61: Evaluation and Conclusion (UE Battery Level) MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 - - - Study on Ranging based services and sidelink positioning (FS_Ranging_SL) - - Docs:=47 -
9.20 - - - Term - - Docs:=4 -
9.20 S2-2206358 P-CR Approval 23.700-86: General: Clarification on Location Server UE and peer-to-peer operation MediaTek Inc. Rel-18 r16 agreed. Revised to S2-2207117. Wen (vivo) provides comments.
Lars (Sony) provides comments.
Lars (Sony) please ignore my comments in last email.
Ming (CATT) comments and provides r02.
Xiaoyan Shi (Intel) prefers to keep assistant UE and location server UE defination independently.
Sherry (Xiaomi) provides r04.
Guillaume (MediaTek Inc.) provides r03
Ming (CATT) comments and provide r05.
LiMeng (Huawei) asks for clarification.
Walter Dees (Philips) comments and provides r06
Wen (vivo) comments
Lars (Sony) provides r07
Wen (vivo) comments on r07
Wen (vivo) responds to Lars (Sony).
Lars (Sony) reponds to Wen.
Lars (Sony) responds to Wen.
Sherry (Xiaomi) provides r08.
Guillaume (MediaTek Inc.) provides r09
Guillaume (MediaTek Inc.) provides r10
Lars (Sony)comments on r10, don't like r10.
Guillaume (MediaTek Inc.) replies to Lars (Sony)
Sherry (Xiaomi) provides r11.
Ming (CATT) comment that the server functionality used for Ranging/SL positioning is very different from that of LMF(Server for Location service).
Ming (CATT) provides r12.
Sherry (Xiaomi) provides r13.
LiMeng (Huawei) provides r14.
Guillaume (MediaTek Inc.) provides r15
Sherry (Xiaomi) provides r16.
Guillaume (MediaTek Inc.) ok with r16
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) is ok with r16
Guillaume (MediaTek Inc.): good ?? thanks all
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207117 P-CR Approval 23.700-86: General: Clarification on Location Server UE and peer-to-peer operation MediaTek Inc. Rel-18 Revision of S2-2206358r16. Approved Approved
9.20 S2-2206819 P-CR Approval 23.700-86: Updates to terminologies Xiaomi Rel-18 r07 agreed. Revised to S2-2207118. Wen (vivo) provides comments.
Jingran Chen (OPPO) provides comments.
Lars (Sony) comments.
Wen (vivo) replies.
Lars (Sony) replies.
Ming (CATT) comments and provides r01.
Xiaoyan Shi (Intel) share same view with Lars and Sherry on the assistant UE and Location Server UE.
Sherry (Xiaomi) provides r03.
Sherry (vivo) comments.
Sherry (Xiaomi) comments.
Guillaume (MediaTek Inc.) provides r02
Ming (CATT) comments on r03.
Walter Dees (Philips) makes suggestion and provides r04
Wen (vivo) comments.
Xiaoyan Shi (Intel) replies.
Wen(vivo) replies to Xiaoyan Shi (Intel).
Sherry(Xiaomi) provides r05.
Guillaume (MediaTek Inc.) ok with r05
Xiaoyan Shi(Intel) replies.
LiMeng (Huawei) provides r06.
Sherry (Xiaomi) provides r07.
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) is fine with r07.
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207118 P-CR Approval 23.700-86: Updates to terminologies Xiaomi Rel-18 Revision of S2-2206819r07. Approved Approved
9.20 - - - Solution of KI#2 - - Docs:=5 -
9.20 S2-2206055 P-CR Approval 23.700-86: KI#2, New Solution: Service continuity of periodic ranging with assistant UE Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2207119. Xiaoyan Shi (Intel) comments.
Hong (Qualcomm) comments.
Lars (Sony comments.
Sherry (Xiaomi) comments.
Runze (Huawei) replies to Xiaoyan Shi (Intel).
Runze (Huawei) replies to Lars (Sony).
Wen (vivo) comments.
Lars (Sony) responds to Runze.
Runze (Huawei) replies to Lars (Sony), and provides r01.
Runze (Huawei) replies to Wen (vivo).
Lars (Sony) replies to Runze.
Runze (Huawei) replies to Hong (QC) and Lars (Sony), provides r02.
Hong (Qualcomm) replies to Runze.
Runze (Huawei) replies to Hong (Qualcomm) and provides r03 .
==== 9.X, 10.X Revisions Deadline ====
Runze (Huawei) replies to Sherry (Xiaomi) and suggest to approve r03.
Lars (Sony) comments.
Lars (Sony) replies to Runze (Huawei)
Sherry (Xiaomi) replies to Runze and couldn't accept any revision or r00.
Sherry (Xiaomi) provides r04.
Runze (Huawei) replied to Sherry (Xiaomi).
Sherry (Xiaomi) replied to Runze.
Runze (Huawei) replies to Sherry (Xiaomi).
Sherry (Xiaomi) replies.
Runze (huawei) requests to discuss CC#5
Lars (Sony) propose to agree r03 + new Editor's Note: An alternative solution is that the determination on the use of assistant UE, which assistant UE is selected is independent for each cycle of periodic Ranging. When and how to determinate whether to use the current assistant UE, discover a new assistant UE or no assistant UE in different cycles of periodic Ranging is FFS.
Runze (huawei) can accept the proposal from Lars.
Sherry (Xiaomi) can accept the proposal from Lars.
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207119 P-CR Approval 23.700-86: KI#2, New Solution: Service continuity of periodic ranging with assistant UE Huawei, HiSilicon Rel-18 Revision of S2-2206055r03. Approved Approved
9.20 S2-2206375 P-CR Approval 23.700-86: KI#2, Sol#16_Update to support multiple assistant UEs case Huawei, HiSilicon Rel-18 Approved Wen(vivo) comments.
Xiaoyan Shi (Intel) comments.
Sherry (Xiaomi) comments.
LiMeng (Huawei) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.20 S2-2206917 P-CR Approval 23.700-86: KI#2 new solution Ranging service operation with the assistant UE Intel Rel-18 r01 agreed. Revised to S2-2207120. Lars (Sony) point out a typo.
Wen (vivo) comments.
Xiaoyan Shi (Intel) replies to Wen and Lars.
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) replies to Hong and provides r01.
Xiaoyan Shi (Intel) replies to Sherry.
Sherry (Xiaomi) comments.
LiMeng (Huawei) asks for clarification.
Xiaoyan Shi (Intel) replies to Limeng.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207120 P-CR Approval 23.700-86: KI#2 new solution Ranging service operation with the assistant UE Intel Rel-18 Revision of S2-2206917r01. Approved Approved
9.20 - - - Solution of KI#5 - - Docs:=7 -
9.20 S2-2206118 P-CR Approval 23.700-86: KI#5, solution#8: update solution to resolve some Editor s notes OPPO Rel-18 r02 agreed. Revised to S2-2207121. Wen (vivo) comments
Lars (Sony) comments
Xiaoyan Shi (Intel) asks questions for clarification
Jingran Chen (OPPO) replies to vivo, Sony and Intel and provides r01.
Lars (Sony) comments.
Jingran Chen (OPPO) replies to the comments and provides r02.
Xiaoyan Shi (Intel) comments.
Sherry (Xiaomi) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207121 P-CR Approval 23.700-86: KI#5, solution#8: update solution to resolve some Editor s notes OPPO Rel-18 Revision of S2-2206118r02. Approved Approved
9.20 S2-2206863 P-CR Approval 23.700-86: KI#5, New solution: enabling SL positioning for the UE out of coverage Interdigital Rel-18 r04 agreed. Revised to S2-2207122. Sherry (Xiaomi) comments.
Jung Je (Interdigital) responded Sherry (Xiaomi)
LiMeng (Huawei) asks for clarification.
Jung Je (Interdigital) responded to LiMeng(Huawei)
Hong (Qualcomm) comments.
LiMeng (Huawei) further comments on the document.
Jung Je (Interdigital) provides r01
Hong (Qualcomm) replies to Jung Je.
Jung Je (Interdigital) uploaded r02 and responded to Hong(Qualcomm)
Jung Je (Interdigital) responded Sherry(Xiaomi) and uploaded r03.
Jung Je (Interdigital) responded to Sherry(Xiaomi)
Sherry (Xiaomi) replies to Jung Je.
Jung Je (Interdigital) updated r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207122 P-CR Approval 23.700-86: KI#5, New solution: enabling SL positioning for the UE out of coverage Interdigital Rel-18 Revision of S2-2206863r04. Approved Approved
9.20 S2-2206918 P-CR Approval 23.700-86: KI#5 Sol#6 update assumption on NAS connection between Target UE and AMF Intel Rel-18 Approved Sherry (Xiaomi) comments.
Xiaoyan Shi (Intel) replies to Sherry.
Wen (vivo) comments.
==== 9.X, 10.X Revisions Deadline ====
Sherry (Xiaomi) replies to Xiaoyan.
==== 9.X, 10.X Final Deadline ====
Approved
9.20 S2-2206951 P-CR Approval 23.700-86: KI#4, KI#5 New Solution Involving Multiple Reference UEs for Sidelink positioning Philips International B.V. Rel-18 r02 agreed. Revised to S2-2207123. Wen (vivo) comments.
Xiaoyan Shi (Intel) comments.
Hong (Qualcomm) comments.
LiMeng (Huawei) asks for clarification.
Sherry (Xiaomi) asks for clarification.
Walter Dees (Philips) answers questions and provides revision r01.
Jung Je (Interdigital) comments
Walter (Philips) provides revision r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207123 P-CR Approval 23.700-86: KI#4, KI#5 New Solution Involving Multiple Reference UEs for Sidelink positioning Philips International B.V. Rel-18 Revision of S2-2206951r02. Approved Approved
9.20 - - - Solution of KI#6, KI#7 - - Docs:=8 -
9.20 S2-2206377 P-CR Approval 23.700-86: KI #6, Sol #9: Update with selection of initiator UE by LMF Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207124. Sherry (Xiaomi) comments.
Lars (Sony) comments.
LiMeng (Huawei) provides r01.
Lars (Sony) responds to LiMeng.
Jung Je (Interdigital) comments
LiMeng (Huawei) responds to Jung Je and Lars and provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207124 P-CR Approval 23.700-86: KI #6, Sol #9: Update with selection of initiator UE by LMF Huawei, HiSilicon Rel-18 Revision of S2-2206377r02. Approved Approved
9.20 S2-2206539 P-CR Approval 23.700-86: KI#7, KI#5: Sol#12 updates addressing ENs Samsung Rel-18 r04 agreed. Revised to S2-2207125. Sherry (Xiaomi) comments.
Lars (Sony) comments.
Wen (vivo) comments.
David (Samsung) replies to comments, provides r01.
Hong (Qualcomm) comments.
Jung Je (Interdigital) comments
David (Samsung) provides r02.
Lars (Sony) Provide r03, and ask several question in r03 that should to be resolved in a r04.
David (Samsung) comments r03 is from a different document.
Lars (Sony) responds to David (Samsung)
David (Samsung) provides r04 and replies to Sony and Interdigital
Lars (Sony) comments on r04
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207125 P-CR Approval 23.700-86: KI#7, KI#5: Sol#12 updates addressing ENs Samsung Rel-18 Revision of S2-2206539r04. Approved Approved
9.20 S2-2206816 P-CR Approval 23.700-86: KI#6, KI#7 New Solution: Common Ranging/Sidelink positioning service exposure Xiaomi Rel-18 r02 agreed. Revised to S2-2207126. Wen (vivo) comments.
LiMeng (Huawei) asks some questions for clarification.
Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) provides r02.
==== 9.X, 10.X Revisions Deadline ====
Richard (Ericsson) comments
Sherry (Xiaomi) replies.
Richard (Ericsson) replies to Sherry (Xiaomi) and can accept r02 only
Sherry (Xiaomi) replies to Richard.
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207126 P-CR Approval 23.700-86: KI#6, KI#7 New Solution: Common Ranging/Sidelink positioning service exposure Xiaomi Rel-18 Revision of S2-2206816r02. Approved Approved
9.20 S2-2206817 P-CR Approval 23.700-86: KI#6, Solution#25: Update to include how SUPI of Ranging/Sidelink positioning UE is determined Xiaomi Rel-18 r02 agreed. Revised to S2-2207127. Lars (Sony) comments and asks clarification
Wen(vivo) comments.
Xiaoyan Shi (Intel) comments and asks clarification
Sherry (Xiaomi) provides r01, and responds to Xiaoyan and Lars.
Xiaoyan Shi (Intel) comments.
Sherry (Xiaomi) provides r02.
Ming (CATT) comments.
Sherry replies to Ming.
Ming replies to Sherry.
Richard (Ericsson) comments
Sherry (Xiaomi) replies
==== 9.X, 10.X Revisions Deadline ====
Richard (Ericsson) replies
Xiaoyan Shi (Intel) is fine with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207127 P-CR Approval 23.700-86: KI#6, Solution#25: Update to include how SUPI of Ranging/Sidelink positioning UE is determined Xiaomi Rel-18 Revision of S2-2206817r02. Approved Approved
9.20 - - - Others Solutions - - Docs:=3 -
9.20 S2-2205812 P-CR Approval 23.700-86: KI#3&KI#5, Sol#14: Updates to add 5G DDNMF services Ericsson Rel-18 r01 agreed. Revised to S2-2207128. Xiaoyan Shi (Intel) comments.
Hong (Qualcomm) comments.
Hong (Qualcomm) replies to Zhang.
Zhang (Ericsson) provide reponses
Sherry (Xiaomi) comments.
Zhang (Ericsson) response to Hong(Qualcomm) and Sherry (Xiaomi)
Zhang (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207128 P-CR Approval 23.700-86: KI#3&KI#5, Sol#14: Updates to add 5G DDNMF services Ericsson Rel-18 Revision of S2-2205812r01. Approved Approved
9.20 S2-2206359 P-CR Approval 23.700-86: KI#2 KI#3 KI#6: New Solution: LCS for peer-to-peer SL Positioning and Ranging MediaTek Inc. Rel-18 Noted Cai Simon (Nokia) asks questions
Lars (Sony) provides comments.
Ming (CATT) provides comments.
Guillaume (MediaTek Inc.) replies to Cai Simon (Nokia)
Guillaume (MediaTek Inc.) replies to Lars (Sony)
Guillaume (MediaTek Inc.) responds to Ming (CATT).
Ming (CATT) responds to Guillaume (MediaTek Inc.).
Sherry (Xiaomi) comments.
Guillaume (MediaTek Inc.) replies to Ming (CATT)
Cai Simon (Nokia) clarifies questions
LiMeng (Huawei) asks questions regarding the location information
Guillaume (MediaTek Inc.) provides r01
Hong (Qualcomm) comments.
Guillaume (MediaTek Inc.) replies to Hong (Qualcomm) and provides r02.
Cai Simon (Nokia) provides comments
Guillaume (MediaTek Inc.) replies to Simon (Nokia) (and also Hong (Qualcomm) again). Provides r03.
Ming (CATT) comments.
Guillaume (MediaTek Inc.) comments
Richard (Ericsson) comments
Sherry (Xiaomi) provides r04.
Sherry (Xiaomi) replies to Richard.
Cai Simon (Nokia) comments r04
==== 9.X, 10.X Revisions Deadline ====
Guillaume (MediaTek Inc.) replies. Provides r05
Cai Simon (Nokia) shows r05 out of revision deadline
Sherry (Xiaomi) comments that we have some buffer time for the revision deadline, especially the FTP server doesn't work well tonight, so this paper should still be considered as in time.
Guillaume (MediaTek Inc.) corrects Simon (Nokia): r05 was uploaded on time
Cai Simon (Nokia) clarifies deadline to Guillaume
Cai Simon (Nokia) is willing to review r05
Sherry (Xiaomi) is fine with r05.
Cai Simon (Nokia) objects to all revisions, including r05
Sherry (Xiaomi) asks Cai Simon (Nokia) if possible to improve the solution to resolve the mentioned issue in the next meeting, because the TU allocation for FS_Ranging_SL is very limited, and we had spent quite a lot of time to work on this paper to progress during this meeting. In the next meeting, much likely new solution is not allowed.
Cai Simon (Nokia) keeps objection
Guillaume (MediaTek Inc.) expresses disappointment with Simon(Nokia) comments. And requests this doc to CC#5.
Sherry replies to Cai Simon (Nokia) that you have all your freedom to object, but please nicely consider the project progress.
Cai Simon (Nokia) objects to current revisions and willing to review any further revisions
==== 9.X, 10.X Final Deadline ====
Cai Simon (Nokia) responds to Hong (Qualcomm)
Cai Simon (Nokia) asks for clarifications from Guillaume (MediaTek Inc.) and Hong (Qualcomm)
Cai Simon (Nokia) clarifies to Guillaume
Guillaume (MediaTek Inc.) responds to Simon (Nokia) again: all comments had and have been addressed.
Cai Simon (Nokia) shows the sample
Cai Simon (Nokia) replies Sherry (Xiaomi)
Guillaume (MediaTek Inc.) provides r06 (in drafts) and asks to cover it in CC#5
Cai Simon (Nokia) accepts r06
Noted
9.20 - - - LS Out - - Docs:=3 -
9.20 S2-2205978 LS OUT Approval [DRAFT] LS on transport of RSPP CATT Rel-18 Postponed Runze (Huawei) provides comments.
Hong (Qualcomm) comments.
Guillaume (MediaTek Inc.) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
9.20 S2-2206820 LS OUT Approval [DRAFT] LS on Terminology Alignment for Ranging/Sidelink Positioning Xiaomi Rel-18 r03 agreed. Revised to S2-2207129. Sherry (Xiaomi) provides r01.
Ming (CATT) comments and provides r02
Sherry (Xiaomi) provides r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.20 S2-2207129 LS OUT Approval [DRAFT] LS on Terminology Alignment for Ranging/Sidelink Positioning Xiaomi Rel-18 Revision of S2-2206820r03. Approved Approved
9.20 - - - Discussion - - Docs:=1 -
9.20 S2-2205977 DISCUSSION Discussion Way-forward proposal on transport of RSPP CATT Rel-18 Noted Runze (Huawei) provides comments.
Deng Qiang (CATT) clarifies to Runze (Huawei).
Sherry (Xiaomi) proposes to postpone the discussion on evaluation and conclusion to the next meeting.
==== 9.X, 10.X Revisions Deadline ====
Deng Qiang (CATT) this DP can be noted.
==== 9.X, 10.X Final Deadline ====
Noted
9.20 - - - Documents exceeding TU Budget - - Docs:=16 -
9.20 S2-2206357 P-CR Approval 23.700-86: General: On terminology inconsistencies MediaTek Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206818 P-CR Approval 23.700-86: Terminology Clarifications and Additions Xiaomi Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206054 P-CR Approval 23.700-86: KI#5, Sol#20: Update to support multiple Located UEs and Located UE discovery for specific coordinate systems Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206919 P-CR Approval 23.700-86: KI#5 Sol#7 update Network assisted UE Sidelink Positioning capability Intel Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206378 P-CR Approval 23.700-86: KI #7, Sol #12: Update with selection of initiator UE by NEF or GMLC Huawei, HiSilicon Rel-18 Not Handled Lars (Sony) comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206368 P-CR Approval 23.700-86: KI#2_Evaluation and conclusion on KI#2 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2205975 P-CR Approval 23.700-86: Overall Evaluation and Conclusion on KI#3 CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206369 P-CR Approval 23.700-86: KI#3_Evaluation and conclusion on KI#3 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2205976 P-CR Approval 23.700-86: Overall Evaluation and Conclusion on KI#4 CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206370 P-CR Approval 23.700-86: KI#4_Evaluation and conclusion on KI#4 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206376 P-CR Approval 23.700-86: Evaluation for KI#4 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206195 P-CR Approval 23.700-86: KI#5: Initial Evaluation Sony Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206371 P-CR Approval 23.700-86: KI#5_Evaluation and conclusion on KI#5 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206196 P-CR Approval 23.700-86: KI#6: Initial Evaluation Sony Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206372 P-CR Approval 23.700-86: KI#6_Evaluation and conclusion on KI#6 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.20 S2-2206373 P-CR Approval 23.700-86: KI#7_Evaluation and conclusion on KI#7 Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.21 - - - Study on System Support for AI/ML-based Services (FS_AIMLsys) - - Docs:=95 -
9.21 - - - Incoming LSs - - Docs:=2 -
9.21 S2-2205451 LS In Action LS from SA WG4: LS on User plane solution for 5GC information exposure to UE SA WG4 (S4-220846) Rel-18 Postponed Postponed
9.21 S2-2205455 LS In Action LS from SA WG3: LS reply on 5GC information exposure to UE SA WG3 (S3-221621) Rel-18 Postponed Postponed
9.21 - - - General - Architecture Assumptions Update and Principles Evaluation - - Docs:=5 -
9.21 S2-2206912 P-CR Approval 23.700-80: Evaluation proposal of general architecture principles based on moderated discussion outcome Samsung, CATT, OPPO, Lenovo Rel-18 r14 agreed. Revised to S2-2207802. Tricci (OPPO) proposed additional comments for moderated APs evaluation prepared by the moderator.
Tricci (OPPO) proposed r02 for additional comments which are highlighted in 'green'.
Mehrdad (Mediatek Inc.) requests a clarification on what is being adopted in the TR.
David (Samsung) replies to comments from Mediatek and OPPO.
Yannick (Nokia): Nokia provides comments.
Ulises (InterDigital): replies to comments from Yannick a provides r03.
Tricci (OPPO) thanks Ulises (InterDigital) r03 which is a good start and provides r04 to further trim down the evaluation proposal.
Juan Zhang (Qualcomm) provides comments
David (Samsung) replies to Qualcomm.
Mehrdad (Mediatek Inc.) comments
Tricci (OPPO) uploads r05 with major clean up of the file as it becomes unreadable. I made some updates based on the inputs from Nokia and Mediatek.
Malla (NTT DOCOMO) provides comments.
Tricci (OPPO) responds to Malla (NTT DOCOMO) comments.
Jianning (Xiaomi) provides comments
Juan Zhang (Qualcomm) provides comments.
David (Samsung) provides r06 and comments.
David (Samsung) replies Xiaomi and Docomo's question.
Tricci (OPPO) thanks David (Samsung) for the update of r06, and provides r07.
Sudeep (Apple) provides comments on r07.
Belen (Ericsson) provides comments on r07
Yannick (Nokia): Nokia provides comments and r08.
Mehrdad (Mediatek Inc.) comments on r08
Zhang (Ericsson) provides r09 and comments
Wang Yuan (Huawei) provides r10 and comments
Xiaoyan (CATT) provides comments
David (Samsung) provides r11
Tricci (OPPO) has concern for the latest changes from David (Samsung) r11.
Malla (NTT DOCOMO) provided r13 (Actually it should be r12, but I screwed it up).
Yannick (Nokia): Nokia replies to NTT DOCOMO and suggest different approach.
Tricci (OPPO) thanks Yannick (Nokia) genius idea
David (Samsung) supports Nokia's proposal
Yannick (Nokia): Nokia provides r14 implementing suggested approach.
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPP) BIG THANKS to Yannick (Nokia) great effort to organize our generic AP and can support r14.
Juan Zhang (Qualcomm) is OK with r14.
David (Samsung) is OK with r14
Wang Yuan (Huawei) is OK with r14 and would like to co-sign.
Mehrdad (Mediatek Inc.) is OK with r14.
Malla (NTT DOCOMO) can live with r14.
Zhang (Ericsson) is OK with r14 and co-sign the paper
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207802 P-CR Approval 23.700-80: Evaluation proposal of general architecture principles based on moderated discussion outcome Samsung, CATT, OPPO, Lenovo Rel-18 Revision of S2-2206912r14. Approved Approved
9.21 S2-2205677 P-CR Approval 23.700-80: General: Update of Architecture Assumption Qualcomm Incorporated Rel-18 Merged into S2-2207803 Tricci (OPPO) proposes to merge 5677 to LG's 6040. Thanks.
Mehrdad (Mediatek Inc.) also suggests to merge this PCR into 6040.
Juan Zhang (Qualcomm) is OK to merge into 6040.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206040 P-CR Approval 23.700-80: Architectural Assumptions: Update to resolve EN LG Electronics Rel-18 r18 agreed. Revised to S2-2207803, merging and S2-2205677 Tricci (OPPO) proposed update to LG's revision for the architecture assumptions.
Susan (Huawei) provides r02.
Tricci (OPPO) responds to Susan (Huawei) and provides r03.
David (Samsung) provides r04.
Tricci (OPPO) responds to David (Samsung) provides r05.
Mehrdad (Mediatek Inc.) comments on r05 and kindly requests to remove the example.
Zhang (Ericsson) provide comments to r05
LaeYoung (LGE) provides r06.
David (Samsung) provides r07.
Ulises (InterDigital Inc.) agrees with Samsung regarding their view on that the 5GC awareness of FL operation taking place at the application layer and prefers r07.
Tricci (OPPO) provides r08.
Tricci (OPPO) asks for clarification from InterDigital and anyone for help to understand the added word in r07.
Malla (NTT DOCOMO) Provided comment.
David (Samsung) comments.
Juan Zhang (Qualcomm) provides comments.
David (Samsung) requests clarifications from Qualcomm.
Tricci (OPPO) shares the same concern as Qualcomm and would like to provide the reason.
Malla (NTT DOCOMO) suggests discussing this issue as part of KI#7, not as part of the architectural assumption.
David (Samsung) agrees with Docomo's proposal, provides r09 accordingly.
Malla (NTT DOCOMO) fine with r09.
Tricci (OPPO) provides r12 to restore the EN because the latest text address traffic type and not Application AI/ML operation type. OPPO supports only r12. For some reason, previously uploaded r11 is empty.
Tricci (OPPO) also agrees with Belen (Ericsson) assessment, and provides r11 to restore the EN because the latest text address traffic type and not Application AI/ML operation type. OPPO supports only r11.
Ellen (Google) supports r10 proposed by Belen (Ericsson)
LaeYoung (LGE) prefers r09 than r10.
Belen (Ericsson) provides r10
David (Samsung) provides comments on r12
Tricci (OPPO) thanks David (Samsung) feedback, unfortunately, OPPO cannot accept removing the EN because such issue was raised since the beginning of the study and has not been addressed.
Mehrdad (Mediatek Inc.) requests clarification from OPPO on EN.
Tricci (OPPO) responds to Mehrdad (Mediatek Inc.) for the restored EN.
Jianning (Xiaomi) provide comment
David (Samsung) thanks Tricci and confirms r15 is OK for us
Tricci (OPPO) thanks David (Samsung) updates and proposes r15 with minor clarifications.
David (Samsung) replies to OPPO's proposal and provides r14 (please disregard r13)
Mehrdad (Mediatek Inc.) is OK with r15
David (Samsung) asks a question to Qualcomm
Yannick (Nokia): Nokia is ok with r15 and provides comments.
LaeYoung (LGE) is OK with r15.
Ulises (InterDigital Inc.) is also OK with r015 and provides some comments.
Ellen (Google) is fine with r15 and comments
Malla (NTT DOCOMO) is OK with r15.
Juan Zhang (Qualcomm) replies to David (Samsung)
Susan (Huawei) provides r16 and asks Tricci (OPPO) to provide technical comments why she removed the texts regarding consideration of the KPI requirements from SA1 specification for AI/ML.
Tricci (OPPO) would like to ask Susan (Huawei) to check with the SA2 chair for the fact that he has announced several meetings ago to stop adding new contents to the R18 SIDs on the architecture requirements and architecture assumptions.
David (Samsung) clarifies to Huawei that the decision to leave Huawei's new solutions as unhandled was made jointly by the two rapporteurs and had the support from the rest of companies. New solutions were not allowed in this meeting since we proposed the work plan in February.
Susan (Huawei) replies to David (Samsung).
Tricci (OPPO) would like to request Susan to take our personal arguments offline. Thanks.
Susan (Huawei) replies to Tricci (OPPO) and asks her don't try to lead the discussion to a wrong direction, rather please give technical comments to the proposal.
Belen (Ericsson) provides r17.
Yannick (Nokia): Nokia provides r18.
Mehrdad (Mediatek Inc.) is OK with r17 and r18
LaeYoung (LGE) is OK with r17 and r18.
Mehrdad (Mediatek Inc.) is happy to co-sign based on r17 or r18
LaeYoung (LGE) proposes to go with r18.
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) thanks everyone for the great effort and can go with r18
Juan Zhang (Qualcomm) is OK with r18.
David (Samsung) supports r18 and would like to co-sign
Susan (Huawei) is fine with r17 and r18.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207803 P-CR Approval 23.700-80: Architectural Assumptions: Update to resolve EN LG Electronics Rel-18 Revision of S2-2206040r18, merging and S2-2205677. Approved Approved
9.21 - - - Key Issue #1: Monitoring of network resource utilization for support of Application AI/ML operation - - Docs:=9 -
9.21 S2-2206155 P-CR Approval 23.700-80: KI#1: Evaluation proposal based on moderated discussion outcome Samsung, Apple, CATT, OPPO Rel-18 r02 agreed. Revised to S2-2207804, merging and S2-2206459 Tricci (OPPO) proposes the merge of the evaluation clause from 6459 into 6155.
Yannick (Nokia): Nokia notes that r01 was provided by OPPO.
Yannick (Nokia): Nokia provides r02.
Tricci (OPPO) thanks Yannick (Nokia) for r02 and apologizes to Yannick (Nokia) for not forgetting to post the explicit note on the email reflector for indicating to merge Solution#16 into Solution#37. OPPO is okay with r02.
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) confirms the acceptance of r02.
David (Samsung) can live with r02, although the evaluation needs to be updated in next meeting
Yannick (Nokia): Nokia is ok with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207804 P-CR Approval 23.700-80: KI#1: Evaluation proposal based on moderated discussion outcome Samsung, Apple, CATT, OPPO Rel-18 Revision of S2-2206155r02, merging and S2-2206459. Approved Approved
9.21 S2-2206459 P-CR Approval 23.700-80: TR 23.700-80: FS_AIMLsys KI#1 Evaluations and Proposed Interim Conclusions OPPO, Toyota, Oracle Rel-18 Merged into S2-2207804 Tricci (OPPO) proposes to merge OPPO et al 6459 into Samsung's 6155 and 6788 for the evaluation and interim conclusion for KI#1, respectively.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206788 P-CR Approval 23.700-80: KI#1: Interim conclusion Samsung Rel-18 Noted Tricci (OPPO) proposes to merge 6459 into 6788 to capture the interim conclusion for KI#1.
Yannick (Nokia): Nokia notes that r01 was provided by OPPO.
Wang Yuan (Huawei) provides comments on r01.
David (Samsung) provides r02.
Belen (Ericsson) provides r03
Juan Zhang (Qualcomm) provides r03.
Tricci (OPPO) cannot accept Belen (Ericsson) r03 due to lack of justification.
David (Samsung) clarifies that both Ericsson and Qualcomm seem to have provided r03.
Belen (Ericsson) provides r04.
Replies to ZTE that the technical aspects of the solutions needs to be clear before concluding.
Tricci (OPPO) responds to Juan Zhang (Qualcomm) for Group-MBR proposal to be address in KI#6 is not appropriate. It is more closer to KI#1 and not KI#6.
Tricci (OPPO) not ZTE ?? responds to E///'s comments
Malla (NTT DOCOMO) asks for clarification.
Tricci (OPPO) raised concern regarding r03 and r04 as the authors for both versions have NOT provided any technical justifications and just simply rejected the proposed interim conclusions.
Jianning (Xiaomi) provides comment
Juan Zhang (Qualcomm) provides comments
Belen (Ericsson) replies to Tricci.
David (Samsung) responds to Juan (Qualcomm), provides r05.
Belen (Ericsson) comments
Tricci (OPPO) objects any revision except for r02. OPPO cannot accept any blind objections without companies to provide specific technical justifications for his/her objections.
Juan Zhang (Qualcomm) can not agree with r05.
Belen (Ericsson) cannot agree with r05 either.
David (Samsung) provides r06.
Belen (Ericsson) provides r07, cannot accept r06
David (Samsung) provides r08.
Belen (Ericsson) provides r09
David (Samsung) comments.
Tricci (OPPO) proposed to note this PCR because it is clear that, it is impossible to reach any reasonable conclusion on this KI#1 based on the latest arguments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2205642 P-CR Approval 23.700-80: TR 23.700-80: KI#1 Solution#37 Update for Group-MBR Monitoring Oracle, Toyota, OPPO Rel-18 Approved Belen (Ericsson) provides r01, objects to initial version.
Proposes to use S2-2205532 as basis to resolve the Editor´s Note that is removed in r01.
Tricci (OPPO) cannot accept r01 and rejects Belen (Ericsson) suggestion to use S2-2205532 as the base because S2-2205532 has many fundamental technical issues that has been raised by OPPO.
Belen (Ericsson) provides comments.
I suggest we try to find a way forward, is that possible?
Tricci (OPPO) thanks Belen (Ericsson) for willing to consider a common ground, but we need to first determine if there is a reason for our solutions to merge.
Xiao (Toyota) proposes to concentrate on the discussion about the original proposal in this thread.
Tricci (OPPO) provides r02 to further clarify the addressing to the ENs. Please ignore r01 which was uploaded by mistake.
Belen (Ericsson) provides r03, objects to r02, replies to Toyota
Tricci (OPPO) rejects the objection from Belen (Ericsson) because it is unreasonable for blind objection from Ericsson without any technical justification. The current version of the 5642 has already provided the 'technical' justification why existing slice monitoring cannot be used. Please provide your counter arguments to justify which part of my evaluation is incorrect.
Tricci (OPPO) thanks Belen (Ericsson) to clarify her demand, and responds to the demand to provide detailed technical analysis and technical justifications for removing the corresponding ENs
Uri (Oracle) provides feedback
Belen (Ericsson) provides r05
Yannick (Nokia): just to record that there was an r04 provided by OPPO.
Yannick (Nokia): Nokia requests for clarification.
Tricci (OPPO) requests Belen (Ericsson) to explain exactly what Ericsson wants in order to remove the existing ENs.
Belen (Ericsson) replies to Tricci that Ericsson wants that solutions are evaluated at the Evaluation clause.
Tricci (OPPO) responds to Belen (Ericsson).
Belen (Ericsson) replies to Tricci that Ericsson does not want to block
Tricci (OPPO) responds to Belen (Ericsson) to request to first focus on technical aspect how Ericsson's solution can work to address the EN before we discuss the merging
Tricci (OPPO) provides late response to Yannick (Nokia) and to clarify that Solution#16 has been replaced by Solution#37.
Yannick (Nokia): Nokia asks clarification on status for solution #16.
Belen (Ericsson) can accept initial revision
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) thanks Belen (Ericsson) for accepting the initial revision of 5642.
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2206801 P-CR Approval 23.700-80: KI#1: Sol#1 updates Samsung Rel-18 r06 agreed. Revised to S2-2207805. Tricci (OPPO) asks for clarification for the need of Session Inactivity Time info of analytics, UE Communication.
David (Samsung) replies to OPPO.
Wang Yuan (Huawei) provides comments.
David (Samsung) replies to Huawei.
Belen (Ericsson) provides comments
David (Samsung) replies to Ericsson, provides r01.
Juan Zhang (Qualcomm) provides comments
David (Samsung) replies to Ericsson and Qualcomm, provides r02.
Belen (Ericsson) comments in r02
Belen (Ericsson) asks a question
Tricci (OPPO) thanks David (Samsung) r03 update and asks further clarifications.
David (Samsung) provides r03
David (Samsung) provides clarifications to OPPO
Tricci (OPPO) thanks David (Samsung) clarifications and has more questions and basic concern and may not agree on r04.
Belen (Ericsson) supports r04 and comments on OPPO´s questions
David (Samsung) provides r04 and comments
David (Samsung) provides r05 with minor update
David (Samsung) provides r06 with yet another minor update
==== 9.X, 10.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r06.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207805 P-CR Approval 23.700-80: KI#1: Sol#1 updates Samsung Rel-18 Revision of S2-2206801r06. Approved Approved
9.21 S2-2206454 P-CR Approval 23.700-80: TR 23.700-80: KI#1 Solution#28 and Solution#47 Merger Update OPPO, Toyota, Oracle Rel-18 r01 agreed. Revised to S2-2207806, merging and S2-2206600 David (Samsung) provides comments.
Tricci (OPPO) thanks David (Samsung) comments and provides feedback as well as r01 revision.
Yannick (Nokia): Nokia requests for clarification.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207806 P-CR Approval 23.700-80: TR 23.700-80: KI#1 Solution#28 and Solution#47 Merger Update OPPO, Toyota, Oracle Rel-18 Revision of S2-2206454r01, merging and S2-2206600. Approved Approved
9.21 - - - Key Issue #2: 5GC Information Exposure to UE - - Docs:=20 -
9.21 S2-2206470 P-CR Approval 23.700-80: TR 23.700-80: FS_AIMLsys KI#2 Evaluations and Proposed Interim Conclusions OPPO Rel-18 r19 agreed. Revised to S2-2207807, merging S2-2206335 and S2-2206896 Mehrdad (Mediatek Inc.) comments and requests some revisions.
LaeYoung (LGE) prefers to take conclusion part out in this meeting.
Yannick (Nokia): Nokia concurs with MediaTek and LGE, conclusion part should be removed from the proposal.
Jingran Chen (OPPO) provides r01 and r02. R01 is merged with 6896 and R02 is merged with 6896 and 6335.
Yannick (Nokia): Nokia suggests to use r02 as basis for further revisions, i.e. take the merger of all documents for KI#2 evaluation as basis. Provides r03 and asks for clarification.
Jingran Chen(OPPO) replies to Nokia
LaeYoung (LGE) provides r04.
Malla (NTT DOCOMO) provided r05.
Ulises (InterDigital Inc.) provides comments to address concerns on Sol#5 evaluation and provides r06.
Jingran Chen (OPPO) cannot agree R07 and provides R08.
Jungshin (Samsung) provides r07 and updates evaluation of sol#31.
Wang Yuan (Huawei) has comments on r08 and provides r09.
Mehrdad (Mediatek Inc.) comments and request clarification on evaluation of solutions based on DCAF.
Malla (NTT DOCOMO) replies to Mehrdad (Mediatek Inc.)
Antoine (Orange) asks to clarify if 'N/A' in tbe tables means 'not available' or 'not applicable'.
Jingran(OPPO) replies to the comments.
Wang Yuan (Huawei) replies to Jingran (OPPO).
Yannick (Nokia): Nokia provides r10.
Zhang (Ericsson) provides comments to r09
Jungshin (Samsung) replies to Jingran (OPPO) and provides r10.
Yannick (Nokia): just to record that Samsung provided r11, not r10.
Jungshin (Samsung) provides r12.
Malla (NTT DOCOMO) provides r14.
Jingran Chen (OPPO) supports R13.
Yannick (Nokia): Nokia provides r13.
Jingran Chen (OPPO) provides comments.
Antoine (Orange) provides r15.
Malla (NTT DOCOMO) replies Jingran Chen (OPPO).
Yannick (Nokia): Nokia requests clarification on r16.
Mehrdad (Mediatek Inc.) provides r16
Mehrdad (Mediatek Inc.) replies to Nokia.
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek Inc)
Juan Zhang (Qualcomm) provides r17.
Mehrdad (Mediatek Inc.) replies to Qualcomm.
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek)
Yannick (Nokia): Nokia replies to Samsung and Qualcomm.
Jingran(OPPO) provides comments
Zhang (Ericsson) have similar concerns as Yannick (Nokia) to r16
Juan Zhang (Qualcomm) provides r18 to remove the controversial Cons from solution#2.
Ulises (InterDigital Inc.) provides comments to clarify aspects of Sol#5 evaluation and provides r19.
Mehrdad (Mediatek Inc.) replies to Nokia, Qualcomm, Ericsson and OPPO.
==== 9.X, 10.X Revisions Deadline ====
LaeYoung (LGE) asks a Q.
Jingran (OPPO) replies to LGE.
LaeYoung (LGE) answers to Jingran (OPPO).
Juan Zhang (Qualcomm) is OK with r19.
Antoine (Orange) answers; 3 occurences of 'Not mentioned' (in table cells where there is also some description) need to be removed as part of pCR clean-up.
LaeYoung (LGE) responds to Antoine (Orange).
Mehrdad (Mediatek Inc.) can live with r19
Malla (NTT DOCOMO) fine with r19
Zhang (Ericsson) is fine with r19
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207807 P-CR Approval 23.700-80: TR 23.700-80: FS_AIMLsys KI#2 Evaluations and Proposed Interim Conclusions OPPO Rel-18 Revision of S2-2206470r19, merging S2-2206335 and S2-2206896. Approved Approved
9.21 S2-2206335 P-CR Approval 23.700-80: KI#2, Evaluation and interim conclusion Vivo Rel-18 Merged into S2-2207807 Mehrdad (Mediatek Inc.) suggests to mark this PCR as merged into 6470 (OPPO)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206896 P-CR Approval 23.700-80: PCR_5G_AIMLsys- evaluation for KI#2 Xiaomi Rel-18 Merged into S2-2207807 Jianning (Xiaomi) proposes to merge this paper into S2-2206470
Jingran Chen (OPPO) supports to merge 6896 into 6470 and provides r01.
Yannick (Nokia): Nokia notes that r01 provided is for S2-2206470. There is no r01 for S2-2206896.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2205636 P-CR Approval 23.700-80: KI#2, Sol#31: Updates to add Analytics container between UE and NWDAF Ericsson Rel-18 r02 agreed. Revised to S2-2207808. Yannick (Nokia): Nokia notes that this update for solution #31 changes same step as S2-2206934.
Ulises (InterDigital): provides comments on the newly added text.
Jungshin (Samsung) provides comments.
Zhang (Ericsson) response to Jungshin (Samsung)
Zhang (Ericsson) response to Ulises(Interdigital) and provide r01
Yannick (Nokia): Nokia requests for clarification.
Ulises (InterDigital): is OK with r01.
Zhang (Ericsson) provide r02
==== 9.X, 10.X Revisions Deadline ====
Jungshin (Samsung): We can accept r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207808 P-CR Approval 23.700-80: KI#2, Sol#31: Updates to add Analytics container between UE and NWDAF Ericsson Rel-18 Revision of S2-2205636r02. Approved Approved
9.21 S2-2206039 P-CR Approval 23.700-80: KI#2, Sol#3: Updates to resolve ENs LG Electronics Rel-18 r01 agreed. Revised to S2-2207809. Malla (NTT DOCOMO) asks for clarification.
LaeYoung (LGE) replies to Tricci (OPPO).
Tricci (OPPO) thanks LaeYoung (LGE) for the examples and would like to ask further clarification.
LaeYoung (LGE) replies to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to LaeYoung (LGE)
Yannick (Nokia): Nokia provides comments to the second example.
LaeYoung (LGE) answers to Yannick (Nokia).
LaeYoung (LGE) answers to Malla (NTT DOCOMO).
Yannick (Nokia): Nokia provides comments.
Malla (NTT DOCOMO) provides comments.
LaeYoung (LGE) provides r01 and answers to Malla (NTT DOCOMO) and Yannick (Nokia).
Yannick (Nokia): Nokia is ok with r01.
Malla (NTT DOCOMO) is ok with r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207809 P-CR Approval 23.700-80: KI#2, Sol#3: Updates to resolve ENs LG Electronics Rel-18 Revision of S2-2206039r01. Approved Approved
9.21 S2-2206160 P-CR Approval 23.700-80: AIML R18 KI#2, Solution#4 Update of 5GC Analytics exposure to UE China Mobile Rel-18 r02 agreed. Revised to S2-2207810. Malla (NTT DOCOMO) asks for clarification.
Aihua (CMCC) replies to Malla (NTT DOCOMO).
Ulises (InterDigital): provides comments.
Aihua (CMCC): replies to Ulises.
Jaewoo (LGE) asks for clarifications.
Yannick (Nokia): just to record that there was an r01 provided by CMCC.
Li Aihua (CMCC) provides comments and r02.
==== 9.X, 10.X Revisions Deadline ====
Jaewoo (LGE) is OK with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207810 P-CR Approval 23.700-80: AIML R18 KI#2, Solution#4 Update of 5GC Analytics exposure to UE China Mobile Rel-18 Revision of S2-2206160r02. Approved Approved
9.21 S2-2206336 P-CR Approval 23.700-80: KI#2, Sol#2 update to solve the Ens Vivo Rel-18 r03 agreed. Revised to S2-2207811. Mehrdad (Mediatek Inc.) comments
Huazhang (vivo) replies
Malla (NTT DOCOMO) objects pCR.
Huazhang (vivo) replies.
Please see the ENs: how to UE consumes the analytic, not UE application. And this ENs is in every solution of KI2.
I just want to solve this problem, and give the example of how UE consumes the analytic.
If you think this paper or how to UE consumes analytic is out of scope of KI, why you didn't object the ENs to be added in the solution? The ENs is also out of scope of KI, if by your consideration or standpoint.
Huazhang (vivo) reply to Malla (NTT)
Malla (NTT DOCOMO) replies Huazhang (vivo) replies.
Huazhang (vivo) provides r01 to reflect how to UE deliver the analytic to AI/ML application
Malla (NTT DOCOMO) replies to Huazhang (vivo) and objects r01.
Huazhang (vivo) provides r02
Malla (NTT DOCOMO) replies to Huazhang (vivo) on r02
Mehrdad (Mediatek Inc.) objects to original version, r01 and r02 and provides r03
==== 9.X, 10.X Revisions Deadline ====
Huazhang (vivo) can accept r03
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207811 P-CR Approval 23.700-80: KI#2, Sol#2 update to solve the Ens Vivo Rel-18 Revision of S2-2206336r03. Approved Approved
9.21 S2-2206450 P-CR Approval 23.700-80: KI#2, Sol#29 update: Adding 5GC exposing information to UE via UE policy CATT Rel-18 r06 agreed. Revised to S2-2207812. Wang Yuan (Huawei) provides comments.
Jiahui (China Telecom) provides comments.
Yannick (Nokia): Nokia provides comments.
Mehrdad (Mediatek Inc.) feels this is in the scope of eNA_ph3
Malla (NTT DOCOMO) asks for clarification
Juan Zhang (Qualcomm) provides comments
Xiaoyan (CATT) provides r01.
Xiaoyan (CATT) responds to Malla (NTT DOCOMO)
Jungshin (Samsung) asks for clarification.
Jiahui (China Telecom) is OK with r01 and co-sign.
Mehrdad (Mediatek Inc.) has technical concern on all revisions of this PCR
Xiaoyan (CATT) replies to Jungshin (Samsung) and Yuan (Huawei).
Juan Zhang (Qualcomm) can not agree with all the revisions.
Xiaoyan (CATT) replies to Mehrdad (Mediatek Inc.) and provides r03.
Xiaoyan (CATT) replies to Juan Zhang (Qualcomm).
Juan Zhang (Qualcomm) replies to Xiaoyan (CATT).
Xiaoyan (CATT) provides r04.
Jungshin (Samsung) replies to Xiaoyan (CATT).
Xiaoyan (CATT) replies to Jungshin (Samsung).
Zhang (Ericsson) ask for clarification
Yannick (Nokia): Nokia provides r05.
Xiaoyan (CATT ) clarifies to Zhang (Ericsson).
Xiaoyan (CATT) clarifies to Malla (NTT DOCOMO)
Xiaoyan (CATT) is fine with r05.
Xiaoyan (CATT) thanks to Jiahui (China Telecom) for the support and provides r06.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207812 P-CR Approval 23.700-80: KI#2, Sol#29 update: Adding 5GC exposing information to UE via UE policy CATT Rel-18 Revision of S2-2206450r06. Approved Approved
9.21 S2-2206498 P-CR Approval 23.700-80: TR 23.700-80: Solution#2 to resolve some Editor s notes OPPO Rel-18 r06 agreed. Revised to S2-2207813. Wang Yuan (Huawei) provides r01.
Jingran Chen (OPPO) replies to Huawei and provides r02.
Mehrdad (Mediatek Inc.) comments
Wang Yuan (Huawei) does not agree to remove changes in 6.2.1, and does not agree to merge the changes in 6.2.2.3 to 5676.
Malla (NTT DOCOMO) asks for clarification.
Mehrdad (Mediatek Inc.) can not agree with this PCR based on r01, r02
Jingran Chen (OPPO) replies to the comments and provide a way forward.
Wang Yuan (Huawei) replies to the comments from Mehrdad (Mediatek Inc.).
Mehrdad (Mediatek Inc.) replies to OPPO
Mehrdad (Mediatek Inc.) replies to Huawei.
Zhang (Ericsson) provides comment to both r00 and r01
Wang Yuan (Huawei) replies to Mehrdad and ask for clarification.
Yannick (Nokia): Nokia requests clarification on text initially in r00.
Jingran (OPPO) replies to the comments.
Jingran (OPPO) replies to Nokia.
Wang Yuan (Huawei) replies to Mehrdad (Mediatek Inc.) and provides r03.
Yannick (Nokia): Nokia replies to OPPO.
Mehrdad (Mediatek Inc.) can live with r03.
Jingran (OPPO) replies to Nokia and provides r04.
Yannick (Nokia): Nokia is ok with r04.
Mehrdad (Mediatek Inc.) sees a technical issue in r03, r04 and provides r05.
Wang Yuan (Huawei) didn't see the technical issue indicated by Mehrdad (Mediatek Inc.) thus cannot accept r05, and provides r06.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207813 P-CR Approval 23.700-80: TR 23.700-80: Solution#2 to resolve some Editor s notes OPPO Rel-18 Revision of S2-2206498r06. Approved Approved
9.21 S2-2206934 P-CR Approval 23.700-80: Update of Solution #31 Samsung Rel-18 r02 agreed. Revised to S2-2207814. Yannick (Nokia): Nokia notes that this update for solution #31 changes same step as S2-2205636.
Malla (NTT DOCOMO) asks for clarification.
Ulises (InterDigital Inc.) provides comments
Jungshin (Samsung) provides clarification and r01.
Yannick (Nokia): Nokia comments on r01.
Jungshin (Samsung) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207814 P-CR Approval 23.700-80: Update of Solution #31 Samsung Rel-18 Revision of S2-2206934r02. Approved Approved
9.21 S2-2205676 P-CR Approval 23.700-80: KI#2: update of Solution#2 Qualcomm Incorporated Rel-18 r11 agreed. Revised to S2-2207815. Mehrdad (Mediatek Inc.) provides comments
Huazhang (vivo) ask a question
Vivian(vivo) provides comments and asks for more refinements.
Juan Zhang (Qualcomm) replies to vivo and Mediatek
Jingran Chen (OPPO) provides comments
Malla (NTT DOCOMO) raised that it is a completely different solution, compared to existing DCAF, asks @Tricci/@David to confirm whether it is on agenda or not based on Chair's suggestion in CC#1.
Mehrdad (Mediatek Inc.) comments and asks further clarification from Qualcomm.
Juan Zhang (Qualcomm) replies to Vivian (vivo).
Juan Zhang (Qualcomm) replies to Jingran (OPPO)
Juan Zhang (Qualcomm) replies to Malla.
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek).
Juan Zhang (Qualcomm) replies r01.
Mehrdad (Mediatek Inc.) replied to Qualcomm.
Zhang (Ericsson) provides r02
Mehrdad (Mediatek Inc.) provides r03
Yannick (Nokia): Nokia provides some suggestions.
Malla(NTT DOCOMO) provided r04
Juan Zhang (Qualcomm) is OK with the update in r02
Antoine (Orange) comments on DEAF.
Juan Zhang (Qualcomm) replies to Antoine.
Juan Zhang (Qualcomm) provides r05 based on r02.
Mehrdad (Mediatek Inc.) replies to Qualcomm.
Mehrdad (Mediatek Inc.) can not agree with original version, r01, r02 and r05.
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek) and objects r03, r04.
Mehrdad (Mediatek Inc.) objects to original version, r01, r02 and r05.
Juan Zhang (Qualcomm) provides r06.
Mehrdad (Mediatek Inc.) objects to r06 and provides r07.
Juan Zhang (Qualcomm) provides r08.
Mehrdad (Mediatek Inc.) provides r09.
Juan Zhang (Qualcomm) provides r10.
Antoine (Orange) provides r11 to replace DEAF by IEAF (inclusive language).
Mehrdad (Mediatek Inc.) is OK with r10 and r11 and requests to co-sign.
Juan Zhang (Qualcomm) is OK with r11.
==== 9.X, 10.X Revisions Deadline ====
Mehrdad (Mediatek Inc.) is OK with r11 and support it. We object to original version, r01, r02, r05, r06 and r08.
Malla (NTT DOCOMO) asks clarification on r11.
Malla (NTT DOCOMO) fine with r11.
Mehrdad (Mediatek Inc.) replies to NTT DOCOMO.
Juan Zhang (Qualcomm) replies to NTT DOCOMO.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207815 P-CR Approval 23.700-80: KI#2: update of Solution#2 Qualcomm Incorporated Rel-18 Revision of S2-2205676r11. Approved Approved
9.21 - - - Key Issue #3: 5GC Information Exposure to Authorized 3rd Party for Application Layer AI/ML Operation - - Docs:=7 -
9.21 S2-2206334 P-CR Approval 23.700-80: KI#3: Evaluation proposal based on moderated discussion outcome Vivo, OPPO Rel-18 r06 agreed. Revised to S2-2207816, merging S2-2206287 and S2-2206725 Yingying(CATT) merges S2-2206725 into S2-220634 based on Rapporteur proposal and provides 6334r01.
Yingying(CATT) modifies the link of 6334r01.
Juan Zhang (Qualcomm) provides comments
Mehrdad (Mediatek Inc.) agrees with Qualcomm.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207816 P-CR Approval 23.700-80: KI#3: Evaluation proposal based on moderated discussion outcome Vivo, OPPO Rel-18 Revision of S2-2206334r06, merging S2-2206287 and S2-2206725. Approved Approved
9.21 S2-2206287 P-CR Approval 23.700-80: KI#3 Evalutation and Conclusion Lenovo Rel-18 Merged into S2-2207816 Tricci (OPPO) provides r01 for the comments for 6287 and suggests to merge this PCR to 6334 prepared by vivo as the KI#3 moderator.
Zhang (Ericsson) also suggest to merge the paper into S2-2206334
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206725 P-CR Approval 23.700-80: KI#3: Evaluation of solutions CATT Rel-18 Merged into S2-2207816 Tricci (OPPO) asks CATT for technical justification for its evaluation against Solution#28, and to request CATT to merge 6726 to 6334 prepared by vivo .
Yingying(CATT) replies to Tricci (OPPO) and agrees with merge this 6725 to 6334, provides 6334r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2205545 P-CR Approval 23.700-80: KI#3: Sol#32: Update: 5GC Information Exposure to Authorized 3rd Party for Assisting AI/ML Operation Splitting between AI/ML Endpoints Ericsson Rel-18 r02 agreed. Revised to S2-2207817. Wang Yuan (Huawei) has concerns on the initial version.
Mehrdad (Mediatek Inc.) comments
Zhang (Ericsson) provides r01
Yannick (Nokia): Nokia requests for clarification.
Tricci (OPPO) has fundamental question for step-9 after Ericsson agreed not to collect computational resource info.
Zhang (Ericsson) response to Tricci and Yannick and provide r02
==== 9.X, 10.X Revisions Deadline ====
Wang Yuan (Huawei) thanks Zhang (Ericsson) update and can accept r02.
Tricci (OPPO) thanks Zhang (Ericsson) update of r02 and can live with r02.
Mehrdad (Mediatek Inc.) is OK with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207817 P-CR Approval 23.700-80: KI#3: Sol#32: Update: 5GC Information Exposure to Authorized 3rd Party for Assisting AI/ML Operation Splitting between AI/ML Endpoints Ericsson Rel-18 Revision of S2-2205545r02. Approved Approved
9.21 S2-2206512 P-CR Approval 23.700-80: KI#3, Sol#33: Update to add another option to expose Application AI/ML subscription data China Telecom, OPPO Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 - - - Key Issue #4: Enhancing External Parameter Provisioning - - Docs:=5 -
9.21 S2-2206651 P-CR Approval 23.700-80: KI#4 solutions evaluation Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2205673 P-CR Approval 23.700-80: Update to solution#9 China Telecom Rel-18 r01 agreed. Revised to S2-2207818. Tricci (OPPO) asks for clarifications on how this procedures and the changes handle a group of UEs when they are heading to different directions.
Menghan (China Telecom) replies to Tricci (OPPO)
Tricci (OPPO) confirms the question is target for 5673 and not 5788. Please refer to the diagram extracted from 5673.
Tricci (OPPO) responds to Menghan (China Telecom) to clarify OPPO's question in the original email.
Tricci (OPPO) thanks Menghan (China Telecom) response and asks for solution update.
Menghan (China Telecom) replies to Tricci (OPPO) and Yannick(Nokia)
Yannick (Nokia): Nokia requests for clarification.
Menghan (China Telecom) replies to Tricci (OPPO) and provide r01
Zhang (Ericsson) provides comments
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) responds to Zhang (Ericsson).
Yannick (Nokia): Nokia is ok with r01.
Zhang (Ericsson) is OK with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207818 P-CR Approval 23.700-80: Update to solution#9 China Telecom Rel-18 Revision of S2-2205673r01. Approved Approved
9.21 S2-2205788 P-CR Approval 23.700-80: KI#4: Sol#36 updates to address ENs. Samsung Rel-18 r04 agreed. Revised to S2-2207819. Tricci (OPPO) asks for the clarifications .
David (Samsung) replies to OPPO.
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) provides comments
David (Samsung) replies to Nokia and Qualcomm, provides r01.
Yannick (Nokia): Nokia comments on r01.
David (Samsung) provides r02 and replies to comments from Nokia and Qualcomm
Yannick (Nokia): Nokia comments on r02.
Juan Zhang (Qualcomm) replies to David (Samsung)
David (Samsung) provides r03
Zhang (Ericsson) share Juan (Qualcomm) view
Yannick (Nokia): Nokia comments on r03.
David (Samsung) provides r04 and r05
David (Samsung) replies to Juan Zhang (Qualcomm)
Juan Zhang (Qualcomm) replies to David (Samsung).
==== 9.X, 10.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r04 and object r05.
Yannick (Nokia): Nokia prefers r04.
Zhang (Ericsson) is OK with r04, object r05
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207819 P-CR Approval 23.700-80: KI#4: Sol#36 updates to address ENs. Samsung Rel-18 Revision of S2-2205788r04. Approved Approved
9.21 - - - Key Issue #5: 5GC Enhancement to enable Application AI/ML Traffic Transport - - Docs:=10 -
9.21 S2-2206511 P-CR Approval 23.700-80: TR 23.700-80: FS_AIMLsys KI#5 Evaluations and Proposed Interim Conclusions OPPO, Toyota, Oracle, NTT DoCoMo Rel-18 r06 agreed. Revised to S2-2207820. Belen (Ericsson) provides r01, objects to initial revision since it concludes in solutions that are not agreed and contains Editor´s Note
Yannick (Nokia): Nokia provides r02.
David (Samsung) provides r03
Tricci (OPPO) questions Belen (Ericsson) objection for the initial version of 6511. At this point, OPPO cannot accept any revision that is built on top of r01.
Malla (NTT DOCOMO) objects r01.
Tricci (OPPO) proposes r04 to restore the previous removed interim conclusion part and to update the EN to indicate further discussions are needed for the final conclusion. OPPO can not accept r01, r02 and r03.
Xiao (Toyota) supports r04.
Tricci (OPPO) provides r05 to remove the conclusion part.
David (Samsung) provides r06
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) thanks David (Samsung) for r06 and accept r06
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207820 P-CR Approval 23.700-80: TR 23.700-80: FS_AIMLsys KI#5 Evaluations and Proposed Interim Conclusions OPPO, Toyota, Oracle, NTT DoCoMo Rel-18 Revision of S2-2206511r06. Approved Approved
9.21 S2-2206137 P-CR Approval 23.700-80: KI#5, Sol#10: Update to remove FFS Huawei, HiSilicon Rel-18 Merged into S2-2207822 Tricci (OPPO) proposed to merge Huawei's S2-2206137 into S2-2206695 to align our two companies' proposals for addressing the outstanding Editor's notes.
==== 9.X, 10.X Revisions Deadline ====
Wang Yuan (Huawei) confirms S2-2206137 is merged into S2-2206695
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206448 P-CR Approval 23.700-80: KI#5, Sol#11 update: resolving Editor's notes CATT Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2206449 P-CR Approval 23.700-80: KI#5, Sol#12 update: resolving Editor's notes CATT Rel-18 r01 agreed. Revised to S2-2207821. Tricci (OPPO) corrects the misleading descriptions in the Introduction text for the justification for the solution#12.
Yannick (Nokia): just to record that there was an r01 provided by OPPO.
==== 9.X, 10.X Revisions Deadline ====
Tricci (OPPO) would like to ask Belen (Ericsson) and Xiaoyan (CATT) how to handle their conflicting PCRs 6501 vs. 6449
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207821 P-CR Approval 23.700-80: KI#5, Sol#12 update: resolving Editor's notes CATT Rel-18 Revision of S2-2206449r01. Approved Approved
9.21 S2-2206501 P-CR Approval 23.700-80: KI#5, Sol#12 - updates to remove ENs Ericsson Rel-18 Noted Xiaoyan (CATT) provides comments.
Belen (Ericsson) replies to CATT
==== 9.X, 10.X Revisions Deadline ====
Xiaoyan (CATT) objects to r00 .
Tricci (OPPO) would like to ask Belen (Ericsson) and Xiaoyan (CATT) how to handle their conflicting PCRs 6501 vs. 6449
Belen (Ericsson) replies to Tricci (OPPO) that given CATT objections, there is no conflict any longer.
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206695 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Solution#10 Update for BDT Extensions Oracle, Toyota, NTT DOCOMO, OPPO Rel-18 r04 + changes agreed. Revised to S2-2207822, merging S2-2206137 Tricci (OPPO) proposed to merge Huawei's S2-2206137 into S2-2206695 to align our two companies' proposals for addressing the outstanding Editor's notes.
Belen (Ericsson) provides r03, cannot accept r02.
Wang Yuan (Huawei) replies to Belen (Ericsson) and provides r04.
Uri responds to Belen (Ericsson) and provides r05
Belen (Ericsson) provides r05, objects to r04.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207822 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Solution#10 Update for BDT Extensions Oracle, Toyota, NTT DOCOMO, OPPO Rel-18 Revision of S2-2206695r04 + changes, merging S2-2206137. Approved Approved
9.21 S2-2206862 P-CR Approval 23.700-80: KI#5: Sol#13 updates to address ENs Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 - - - Key Issue #6: QoS and Policy Enhancement - - Docs:=6 -
9.21 S2-2205534 P-CR Approval 23.700-80: KI#6, Evaluation and interim conclusions Ericsson Rel-18 r14 agreed. Revised to S2-2207823, merging S2-2206290 Tricci (OPPO) proposed r01 to update the E///'s prepared evaluation and interim conclusions for KI#6 .
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207823 P-CR Approval 23.700-80: KI#6, Evaluation and interim conclusions Ericsson Rel-18 Revision of S2-2205534r14, merging S2-2206290. Approved Approved
9.21 S2-2206290 P-CR Approval 23.700-80: KI#6 Evalutation and Conclusion Lenovo Rel-18 Merged into S2-2207823 Belen (Ericsson) provides r01, objects to initial revision as there is overlap with S2-2205534.
==== 9.X, 10.X Revisions Deadline ====
Yannick (Nokia): Nokia suggest to mark this contribution as merged with S2-2205534. Discussion on KI#6 evaluation and conclusion took place in S2-2205534 thread.
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2205532 P-CR Approval 23.700-80: KI#6, Sol#37 removing Editor s Notes Ericsson Rel-18 Noted Tricci (OPPO) would like to ask for the clarifications for the proposed alternative from E/// for Solution#37 of which the solution is NOT a solution update to the existing Solution#37, but rather a new solution which does not align with the question from the EN.
Belen (Ericsson) clarifies that this is resolving an Editor´s Note that was added last SA2 meeting, that stated that the alternative proposed was an option that we would like to consider, so we did now.
Tricci (OPPO) asks E/// to review the descriptions of the EN which does not ask for new solution but just ask for evaluation.
Belen (Ericsson) clarifies that this document resolves the same Editor´s note as S2-2205642, so I assume we need to merge or coordinate how to resolve it.
Tricci (OPPO) requests E/// to refer to the EN in Solution#37 to explain where in the EN to suggest new solution is required to update the Solution#37. OPPO also requests E/// to provide answers for the technical questions regarding to E///'s proposal.
Juan Zhang (Qualcomm) provides comments
Belen (Ericsson) replies to OPPO that the EN is proposed to be resolved, and as such a solution to add is added, business as usual I think.
Answers are provided once again.
Tricci (OPPO) thanks Belen (Ericsson) feedback and asks for further clarifications.
Belen (Ericsson) can accept the initial revision of this CR.
Belen (Ericsson) withdraws this CR
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2205533 P-CR Approval 23.700-80: KI#6, Sol#39 removing Editor s Notes Ericsson Rel-18 Merged into S2-2207830 Wang Yuan (Huawei) proposes to merge S2-2205533 to S2-2206138.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206645 P-CR Approval 23.700-80: Solution #38 updates Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 - - - Key Issue #7: 5GS Assistance to Federated Learning Operation - - Docs:=20 -
9.21 S2-2206742 P-CR Approval 23.700-80: FS_AIMLsys KI#7 Evaluation and Proposed interim Conclusions InterDigital Inc. Rel-18 r16 agreed. Revised to S2-2207824. Zhang (Ericsson) provides comments
Ulises (InterDigital Inc.) addresses Ericsson's comments and provides r01
Jihoon (ETRI) provides comments
David (Samsung) provides comments
Belen (Ericsson) provides r02
David (Samsung) provides r03
Megha (Intel) provides r06 and comments
Yannick (Nokia): Nokia provides r05.
Ulises (InterDigital Inc.) thanks Yannick (Nokia) and confirms that r04 is the revision provided not r03
Yannick (Nokia): Nokia believes InterDigital provided r04.
Ulises (InterDigital Inc.) addresses comments/questions from Samsung (David), Belen (Ericsson) and ETRI (Jihoon) and provides r03
Malla (NTT DOCOMO) provided comments
Ulises (InterDigital Inc.) thanks Yannick (Nokia), Megha (Intel) and Malla (NTT DOCOMO) for their comments and provides r07
Malla (NTT DOCOMO) replies to Ulises (InterDigital Inc.) and provided comment on r07
Yannick (Nokia): Nokia provides r08.
Ulises (InterDigital Inc.) thanks Yannick (Nokia), and Zhang (Ericsson) for their comments and provides r09 to address them.
Zhang (Ericsson) provides comments to all the revisions
Yannick (Nokia): Nokia comments on r09 for the conclusion part.
Malla (NTT DOCOMO) agrees with Yannick (Nokia) and provided r10.
Ulises (InterDigital Inc.) provide comments and provides r11
David (Samsung) provides r12
Zhang (Ericsson) provides r13
Yannick (Nokia): Nokia provides r14.
Ulises (InterDigital Inc.) addresses comments and provides r15
David (Samsung) provides r16 with update on Sol#40
Ulises (InterDigital Inc.) is OK with r16
==== 9.X, 10.X Revisions Deadline ====
Yannick (Nokia): Nokia supports r16.
Zhang (Ericsson) is OK for r16 and co-sign
Jihoon (ETRI) also supports r16 and would like to co-sign.
David (Samsung) would also like to co-sign.
Ulises (InterDigital Inc.) confirms that companies who requested to cosign, will be added as cosigners when the approved version is uploaded.
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207824 P-CR Approval 23.700-80: FS_AIMLsys KI#7 Evaluation and Proposed interim Conclusions InterDigital Inc. Rel-18 Revision of S2-2206742r16. Approved Approved
9.21 S2-2205637 P-CR Approval 23.700-80: KI#7, Sol#41: Updates for adding top UEs of high or low performance Ericsson Rel-18 r02 agreed. Revised to S2-2207825. Wang Yuan (Huawei) provides comments on the initial version.
Yannick (Nokia): Nokia provides comments.
Zhang (Ericsson) provides r01
Dongeun (Samsung) provides comments
Wang Yuan (Huawei) has concerns on r01 and provides r02.
Zhang (Ericsson) is OK with r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207825 P-CR Approval 23.700-80: KI#7, Sol#41: Updates for adding top UEs of high or low performance Ericsson Rel-18 Revision of S2-2205637r02. Approved Approved
9.21 S2-2205638 P-CR Approval 23.700-80: KI#7, Solution #45: Update: Dynamic application server and member UE(s) selection Ericsson Rel-18 Approved Dongeun (Samsung) provides comments
Zhang (Ericsson) response to Dongeun (Samsung)
==== 9.X, 10.X Revisions Deadline ====
Menghan (China Telecom) response to Dongeun (Samsung) and Zhang (Ericsson)
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2205674 P-CR Approval 23.700-80: Update to solution#22 China Telecom Rel-18 r04 agreed. Revised to S2-2207826. Jihoon (ETRI) asks questions.
Menghan(China Telecom) provides r01 and replies to Jihoon (ETRI) .
Jihoon (ETRI) provides comments.
Menghan(China Telecom) provides r02 and replies to Jihoon (ETRI) .
Menghan(China Telecom) provides r03 .
Jihoon (ETRI) replies to Menghan(China Telecom).
Dongeun (Samsung) comments.
Menghan(China Telecom) provides r04 and replies to Dongeun (Samsung).
Tricci (OPPO) shares the same concern as Samsung and ETRI and provides reasons below.
Menghan(China Telecom) replies to Tricci (OPPO)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207826 P-CR Approval 23.700-80: Update to solution#22 China Telecom Rel-18 Revision of S2-2205674r04. Approved Approved
9.21 S2-2205684 P-CR Approval 23.700-80: KI #7, Sol #25: Update to support MA PDU Session assistance information LG Electronics Rel-18 Approved Malla (NTT DOCOMO) asks for clarification.
Jaewoo (LGE) replies to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to Jaewoo (LGE).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2205685 P-CR Approval 23.700-80: KI #7, Sol #38: Update to reserve resources requested by AF LG Electronics Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2205787 P-CR Approval 23.700-80: KI#7: Sol#40 updates to address ENs Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.21 S2-2206057 P-CR Approval 23.700-80: KI #7, Sol #21: Update to remove EN ETRI Rel-18 r01 agreed. Revised to S2-2207827. Zhang (Ericsson) provides comments
Jaewook (ETRI) provides r01 and replies Zhang (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
Yannick (Nokia): Nokia indicates that an r01 was provided but was not recorded in Chair's notes. Suggest to approve r01, not r00.
Tricci (OPPO) requests either ETRI or Ericsson to repost the comments because I could not find it under FS_AIMLsys agenda. Many thanks..
Zhang (Ericsson) confirm r01 should be approved, not r00
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207827 P-CR Approval 23.700-80: KI #7, Sol #21: Update to remove EN ETRI Rel-18 Revision of S2-2206057r01. Approved Approved
9.21 S2-2206138 P-CR Approval 23.700-80: KI#7, Sol#39: Update to remove FFS Huawei, HiSilicon Rel-18 r05 + changes agreed. Revised to S2-2207830, merging S2-2205533 and S2-2206773 Wang Yuan (Huawei) proposes to merge 5533 to 6138, and provides 6138r01.
Ellen (Google) comments on 6138r01 and asks clarification on user consent aspects
David (Samsung) provides comments.
Wang Yuan (Huawei) replies to David (Samsung) and Ellen (Google), and provides r02.
Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) replies to Yannick (Nokia) and provides r03.
Ellen (Google) provides r04 for indicating existing mechanism in R17
Wang Yuan (Huawei) thanks Ellen (Google) for r04, and proposes to merge 6773r06 to 6138, and provides 6138r05.
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) is Ok with r05 and confirm as co-signed
David (Samsung) objects to r05, requests a change.
David (Samsung) comments for CC#5: can agree r05 + one of two options, 1) removal of NOTE in cl. 6.39.2, or 2) add in cl. 6.39.2 following EN: 'Whether and how the AF can provide purpose(s) when requesting UE related information is FFS'
==== 9.X, 10.X Final Deadline ====
Wang Yuan (Huawei) is OK for the proposal from David (Samsung) and confirms the agreed changes would be 'r05 + add in cl. 6.39.2 following EN: 'Whether and how the AF can provide purpose(s) when requesting UE related information is FFS''.
Revised
9.21 S2-2207830 P-CR Approval 23.700-80: KI#7, Sol#39: Update to remove FFS Huawei, HiSilicon Rel-18 Revision of S2-2206138r05 + changes, merging S2-2205533 and S2-2206773. Approved Approved
9.21 S2-2206139 P-CR Approval 23.700-80: KI#7, Sol#20: Update to clarify the UE transmission delay assistance to reduce the latency divergence Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207828. Zhang (Ericsson) provides comments
Wang Yuan (Huawei) replies to Zhang (Ericsson) and provides r01.
Zhang (Ericsson) is Ok with r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207828 P-CR Approval 23.700-80: KI#7, Sol#20: Update to clarify the UE transmission delay assistance to reduce the latency divergence Huawei, HiSilicon Rel-18 Revision of S2-2206139r01. Approved Approved
9.21 S2-2206156 P-CR Approval 23.700-80: AIML R18 KI#7, Solution#43 Update of FL member selection China Mobile Rel-18 r04 agreed. Revised to S2-2207829. Yannick (Nokia): Nokia provides comments.
Aihua (CMCC): CMCC respondes to the impact comments.
Jihoon (ETRI) provides comments.
Aihua (CMCC) provides clarification on NWDAF offering candidate list.
Tricci (OPPO) raised the concern for NWDAF to provide the candidate list for UE selection.
Jihoon (ETRI) asks Aihua (CMCC) to provide a new revision again.
Aihua (CMCC) provides r02.
Aihua (CMCC) replies to Tricci (OPPO).
Aihua (CMCC) replies to David(Samsung) and provides with r03.
David (Samsung) requests clarifications on r02.
Tricci (OPPO) agrees with David (Samsung) concern and wondering why Application FL member selection within the scope of NWDAF
Yannick (Nokia): Nokia provides comments to r02.
Aihua (CMCC): deletes option 2 and provides r04.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.21 S2-2207829 P-CR Approval 23.700-80: AIML R18 KI#7, Solution#43 Update of FL member selection China Mobile Rel-18 Revision of S2-2206156r04. Approved Approved
9.21 S2-2206600 P-CR Approval 23.700-80: TR 23.700-80: KI#7 Solution#47 Update to resolve the EN TOYOTA MOTOR CORPORATION Rel-18 Merged into S2-2207806 Tricci (OPPO) proposed to merge S2-2206600 into S2-2206454 from OPPO.
Yannick (Nokia): Nokia provides comments.
Xiao (Toyota) agrees with the merge proposal from OPPO.
Yannick (Nokia): Nokia requests for clarification.
Xiao (Toyota) replies to Yannick (Nokia).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.21 S2-2206773 P-CR Approval 23.700-80: Sol#39 Update: Clarification of User consent for Event/Analytics Exposure Google Inc. Rel-18 Merged into S2-2207830 Jaewoo (LGE) asks questions for clarification.
Ellen (Google) answers questions from Jaewoo (LGE) for clarification.
Wang Yuan (Huawei) provides comments.
Ellen (Google) provides revision r01 to address comments from Yuan (Huawei).
Ellen (Google) provides revision r02 to address comments from Yannick (Nokia) about user consent indication
Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) has concerns on r02 and provides r03.
Ellen (Google) reject r03 which removed all changes provided by this paper and provided by Yuan (Huawei)
Yannick (Nokia): Nokia has a suggestion based on r02.
Ellen (Google) provided r04 based on Nokia's suggestions for Editor's Note in r02.
Wang Yuan (Huawei) provides r05 and proposes to merge 6773r05 to 6138.
Ellen (Google) provides r06 to address Huawei's comment.
Wang Yuan (Huawei) is fine with r06 and proposes to merge 6773r06 to 6138.
==== 9.X, 10.X Revisions Deadline ====
Ellen (Google) proposes to accept r06 or r05 at this meeting if a potential merger proposed by Huawei in 6138r05 cannot resolve questions raised in 6138 thread
==== 9.X, 10.X Final Deadline ====
Wang Yuan (Huawei) confirms that the question raised in 6138 thread has been resolved thus 6773 can still be merged to 6138.
Merged
9.21 - - - Moderated Discussions Summary (For Information ONLY) - - Docs:=8 -
9.21 S2-2205587 DISCUSSION Information Moderated Discussion on General Architecture Principles Samsung Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2205586 DISCUSSION Information Moderated Discussion on KI#1 Architecture Principles Samsung Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206497 DISCUSSION Information FS_AIMLsys Consolidated Moderated Discussions on KI#2 Architecture Principles OPPO, CATT Rel-18 Noted Wang Yuan (Huawei) provides comments on the Principle #9.
Jingran Chen (OPPO) replies to Huawei and suggest to focus on the evaluation Tdoc.
Wang Yuan (Huawei) replies to Jingran (OPPO) and OK to continue to discussion on the evaluation Tdoc.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206333 DISCUSSION Information Moderator discussion for AIML KI#3 architecture principles Vivo, Lenovo Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206648 DISCUSSION Information FS_AIMLsys Moderated Discussions on KI#4 Architecture Principles Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206500 DISCUSSION Information FS_AIMLsys Moderated Discussions on KI#5 Architecture Principles OPPO Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2206768 P-CR Information 23.700-80: FS_AIMLsys Moderated Discussions on KI#6 Architecture Principles Google Inc. Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 S2-2205926 DISCUSSION Agreement FS_AIMLsys Moderated Discussions on KI#7 Architecture Principles InterDigital Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
9.21 - - - Documents exceeding TU Budget - - Docs:=3 -
9.21 S2-2206136 P-CR Approval 23.700-80: KI#2, New Solution - Authorization control of 5GC information exposure to UE Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.21 S2-2206122 P-CR Approval 23.700-80: Solution for KI#4 & KI#7: 5GS Assistance to Federated Learning Operation (Handover in Hierarchical Federated Learning) SONY Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.21 S2-2206564 P-CR Approval 23.700-80: KI#6, New Sol, Add new 5QI and QoS Characteristics for AIML Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 - - - Study on Enhancement of 5G UE Policy (FS_eUEPO) - - Docs:=53 -
9.22 - - - Solution Update for KI#1 (URSP in VPLMN) - - Docs:=4 -
9.22 S2-2205528 P-CR Approval 23.700-85: KI#1, Sol#5 Updates to solution#5 Ericsson, LG Electronics Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206065 P-CR Approval 23.700-85: KI#1, Solution#6 Update: Solution for URSP in VPLMN with PLMN domain indication Intel, Qualcomm Rel-18 r03 agreed. Revised to S2-2207499. Mike (InterDigital) comments
Yang (OPPO) comments and provides r01.
Changhong (Intel) replies to Mike.
Dimitris (Lenovo) requests clarifications
Changhong (Intel) provides r02 to clarify Dimitris (Lenovo) requests
Mike (InterDigital) responds
Hong (Qualcomm) comments.
Changhong (Intel) provides r03.
Mike (InterDigital) comments that r03 is good
Dimitris (Lenovo) has additional questions for clarification
Hong (Qualcomm) replies to Dimitris.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207499 P-CR Approval 23.700-85: KI#1, Solution#6 Update: Solution for URSP in VPLMN with PLMN domain indication Intel, Qualcomm Rel-18 Revision of S2-2206065r03. Approved Approved
9.22 S2-2206834 P-CR Approval 23.700-85: KI#1 Sol #28 Update Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 - - - Evaluation and Conclusion for KI#1 (URSP in VPLMN) - - Docs:=6 -
9.22 S2-2205529 P-CR Approval 23.700-85: KI#1, Evaluation and proposed Way Forward Ericsson Rel-18 r23 + changes agreed. Revised to S2-2207500, merging S2-2205571 and S2-2205907 Baseline paper for KI#1 Changhong (Intel) proposes to use this paper as baseline for KI#1 evaluation and conclusion.
Dimitris (Lenovo) provides initial comments
Wen (vivo) provides comments
Yang (OPPO) provides comments and proposals.
Belen (Ericsson) provides r01
Yang (OPPO) provides r02 because r01 missed some proper evaluation
Pallab (Nokia) provides r03
Yang (OPPO) asks Lenovo for more technical questions
Dimitris (Lenovo) responds to Hong (Qualcomm)
Hong (Qualcomm) replies to Dimitris.
Mike (InterDigital) provides r04
Dimitris (Lenovo) responds to Changhong
Changhong (Intel) asks DK to clarify his comments.
Changhong (Intel) comments.
Jicheol (Samsung) comments.
Dimitris (Lenovo) responds to Yang
Yang (OPPO) responds to Dimitris
Wen (vivo) comments.
Pallab (Nokia) responds to Jicheol (Samsung)
Dimitris (Lenovo) provides responses
Yang (OPPO) provides response to Lenovo
LaeYoung (LGE) comments.
Yang (OPPO) replies to vivo
Susan (Huawei) raises comments and provides r05.
Dimitris (Lenovo) provides r06
Belen (Ericsson) asks Lenovo and Huawei on r06/r05
Dimitris (Lenovo) responds to Belen
LaeYoung (LGE) answers to Changhong (Intel).
Dimitris (Lenovo) comments
LaeYoung (LGE) replies to Dimitris (Lenovo).
Mike (InterDigital) comments and provides r07
Hong (Qualcomm) comments and provide r08.
Pallab (Nokia) provides r09.
LaeYoung (LGE) provides r10.
Changhong (Intel) suggests having a show of hands on the controversial topics for KI#1 at CC#4 or CC#5.
Dimitris (Lenovo) disagrees with r09, r10 provides r11
Dieter (Deutsche Telekom) comments.
Pallab (Nokia) disagrees with r10, r11
Belen (Ericsson) provides r13.
Dimitris (Lenovo) disagrees with r13. Provides r14 including the two options for provisioning VPLMN specific URSP rule and re-instating the EN
Pallab (Nokia) objects to r13.
Yang (OPPO) reask question to Lenovo
Changhong (Intel) asks Pallab to clarify what service parameters from AF to H-PCF is missing from Rel-17.
Dimitris (Lenovo) responds to Changhong.
Mike (InterDigital) replies is ok with r16
Belen (Ericsson) provides r16, objects to r15
Mike (InterDigital) provides r15 and comments
Yang (OPPO) responds to Dimitris and think the UE behaviour needs some extra enhancements if we go with VPLMN specific RSD
Hong (Qualcomm) comments.
Pallab (Nokia) responds to Changhong (Intel)
Pallab (Nokia) objects to r15, 16 and provides r17.
Dimitris (Lenovo) does not agree with Oppo's UE behaviour description
Dimitris (Lenovo) provides r18 based on r17
Jicheol provides r19.
Jicheol provides the link for r19, which was missing from the previous e-mail.
Pallab (Nokia) objects to r19
Susan (Huawei) replies to Dimitris (Lenovo) on re-evaluation indication.
Susan (Huawei) replies to Hong (Qualcomm).
Hong (Qualcomm) replies to Susan.
Jicheol (Samsung) corrects the link to r19.
Mike (InterDigital) comments and provides r20
Changhong (Intel) provides r20.
Hong (Qualcomm) replies to Mike.
Susan (Huawei) provides r21 and objects to all versions including 'VPLMN specific values on the Network Slice Selection, DNN Selection' in the terminology definition for 'VPLMN specific URSP Rules' .
Farooq(AT&T) provides Jicheol (Samsung) feedback.
Yang (OPPO) replies to Susan that PSI based solution can save more signalling in the following configuration
Changhong (Intel) replies to Jicheol.
Changhong (Intel) provides r22 since r20 was occupied by others.
LaeYoung (LGE) asks a Q.
Mike (InterDigital) replies to Hong
Changhong (Intel) provides r23.
==== 9.X, 10.X Revisions Deadline ====
Farooq (AT&T) comments on r23.
Farooq(AT&T) rejects r23 and all revisions of the contribution that includes the text' It is FFS whether to support V-PCF generates and provides VPLMN specific URSP rules to the UE.'
Dieter (Deutsche Telekom) agrees with Farooq(AT&T) and also cannot agree any revision that includes the text' It is FFS whether to support V-PCF generates and provides VPLMN specific URSP rules to the UE.'
Dieter (Deutsche Telekom) agrees with Farooq(AT&T) .
Changhong (Intel) uploads the SoH slides for CC#4.
Changhong (Intel) asks for CC#4 approval.
Belen (Ericsson) proposes to agree on r23 and removing this EN 'It is FFS whether to support V-PCF generates and provides VPLMN specific URSP rules to the UE'
Suggest to remove VPLMN specific URSP Rules given that now URSP Rules only contain HPLMN values, per Huawei objection.
Pallab (Nokia) has concerns with SoH question for KI#1
Pallab (Nokia) proposed SoH question for KI#1
Changhong (Intel) replies to Pallab and provides SoH slides v3 with editorial update.
Patrice (Huawei, rapporteur for FS_EDGE_PH2) requests to add the statement to the conclusion section stating: 'It is agreed that KI#1 of FS_UEPO will commit to fulfil the conclusion of KI#1/LBO of FS_EDGE_PH2.', to the version being approved.
Patrice (Huawei) withdraws his request in his previous comment based on discussion in CC#4.
Changhong (Intel) proposes to have a SoH for KI#1 on how to provide the VPLMN ID to UE at CC#5, we need to see how many companies will object to Option A and C, if both options get massive objection, then we can only rely on Option D which has been supported since Rel-15.
Revised
9.22 S2-2207500 P-CR Approval 23.700-85: KI#1, Evaluation and proposed Way Forward Ericsson Rel-18 Revision of S2-2205529r23 + changes, merging S2-2205571 and S2-2205907. Approved Approved
9.22 S2-2205571 P-CR Approval 23.700-85: KI#1: Evaluation and interim conclusions Lenovo, Apple Rel-18 Merged into S2-2207500 Merge into S2-2205529 Mike (InterDigital) comments
Changhong (Intel) proposes to use S2-2205529 as baseline for KI#1 evaluation and conclusion.
Dimitris (Lenovo) provides initial comments
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205529.
==== 9.X, 10.X Final Deadline ====
Merged
9.22 S2-2205907 P-CR Approval 23.700-85: KI #1, New Eval, Conclusion: Key Issue #1 Evaluation and Conclusion InterDigital Inc. Rel-18 Merged into S2-2207500 Merge into S2-2205529 Changhong (Intel) proposes to use S2-2205529 as baseline for KI#1 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205529.
==== 9.X, 10.X Final Deadline ====
Merged
9.22 S2-2206864 LS OUT Approval [DRAFT] LS on protection of the URSP rules from HPLMN Qualcomm Incorporated Rel-18 CC#4: Qualcomm withdraw objection to r01. r01 agreed. Revised to S2-2207501. LaeYoung (LGE) comments.
Dimitris (Lenovo) agrees with LaeYoung
Hong (Qualcomm) provides r01.
Jicheol (Samsung) support r00. and objects to r01.
LaeYoung (LGE) objects to r00.
==== 9.X, 10.X Revisions Deadline ====
Belen (Ericsson) supports to go for r01.
Ask Samsung if a new LS can be sent to SA3 if there are a decision on VPLMN provided URSP Rules later?
Hong (Qualcomm) comments to go with r01, based on the SoH results.
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207501 LS OUT Approval LS on protection of the URSP rules from HPLMN SA WG2 Rel-18 Revision of S2-2206864r01. Approved Approved
9.22 - - - Solution Update for KI#2 (5GC awareness of URSP enforcement) - - Docs:=8 -
9.22 S2-2205569 P-CR Approval 23.700-85: KI#2: Update of Solution 30 to address editor's notes Lenovo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2205578 P-CR Approval 23.700-85: 23.700-85: KI#2, Sol#31: Update to remove ENs Deutsche Telekom Rel-18 r02 agreed. Revised to S2-2207502. Belen (Ericsson) provides comments/questions
Belen (Ericsson) asks if the questions can be clarified?
Josep (DT) apologizes for the oversight and delay. Answers Belén (Ericsson). Provides comments and r01 addressing comments.
Belen (Ericsson) provide r02.
Josep (DT) is OK with r02, reuploaded Belén's (Ericsson) r02 to the revisions folder.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207502 P-CR Approval 23.700-85: 23.700-85: KI#2, Sol#31: Update to remove ENs Deutsche Telekom Rel-18 Revision of S2-2205578r02. Approved Approved
9.22 S2-2205669 P-CR Agreement 23.700-85: Clarifications for Solution#8 China Unicom Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206402 P-CR Approval 23.700-85: EUEPO KI#2 Sol#15: Update to Solution 15 NEC Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206758 P-CR Approval 23.700-85: Solution#11 Update: 5GC awareness of URSP recognition Google Inc. Rel-18 Noted Jicheol (Samsung) comments.
Dimitris (Lenovo) comments
Pavan (Google) replies to Dimitris (Lenovo) and Jicheol (Samsung)
Krisztian (Apple) provides r01.
Pavan (Google) is fine with r01, and responds to Samsung (Jicheol)
Yang (OPPO) provides r02
Jicheol (Samsung) provides r03.
Pavan (Google) agrees with the changes proposed by OPPO (Yang) Samsung (Jicheol), and provides r04.
Dimitris (Lenovo) asks additional questions objects to added note in r03
Pavan (Google) responds to Dimitrios (Lenovo)
==== 9.X, 10.X Revisions Deadline ====
Krisztian (Apple) is fine with r04. Please add Apple as co-signer in the final version.
Josep (DT) objects to r01-r04.
Josep (DT) additionally objects to r00.
==== 9.X, 10.X Final Deadline ====
Pavan (Google) responds to Josep (DT)
Yang (OPPO) provides r05 based on comments and propose to put it CC#5 for approval
> Yang (OPPO) provides r05 based on comments and propose to put it CC#5 for approval
>
Noted
9.22 S2-2206833 P-CR Approval 23.700-85: KI#2 Sol #7 Update Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206837 P-CR Approval 23.700-85: KI#2 Sol #32 Update Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 - - - Evaluation and Conclusion for KI#2 (5GC awareness of URSP enforcement) - - Docs:=5 -
9.22 S2-2205717 P-CR Approval 23.700-85: Evaluation and conclusion of KI#2 Huawei, HiSilicon Rel-18 CC#4: Various rxx were proposed. CC#5: Noted Baseline paper for KI#2 Changhong (Intel) proposes to use this paper as baseline for KI#2 evaluation and conclusion.
Yang (OPPO) corrected the title (6947->5717), and provide comments and r01.
Yang (OPPO) provides comments and r01.
Yang (OPPO) Further correct the AI number (-> 9.22).
Josep (DT) provides comments, provides r02.
Krisztian (Apple) provides comments and r03.
Huazhang (vivo) provides the comments
Josep (DT) comments, provides r04.
Pavan (Google) provides some comments and r05.
Dimitris (Lenovo) raises concerns with r01, r02, r03 and r04
Jicheol (Samsung) provides r06.
Iskren (NEC) provides comments
Josep (DT) replies to Iskren (NEC).
Belen (Ericsson) provides comments
Huazhang (vivo) provide comments.
I am not ok to define the SMF to reject the PDU session.
And I am also not ok to delete the user consent.
Belen (Ericsson) provides r07
Pinghui(China Telecom) comments
Krisztian (Apple) objects to r07 and r06, supports r05.
Josep (DT) replies to Krisztian (Apple), disagrees to removing UE reporting and his reasons.
Pallab (Nokia) supports r05.
Changhong (Intel) proposes to have a show of hands on the controversial parts at CC#4 or CC#5.
Dimitris (Lenovo) suggests additional questions for SOH
Josep (DT) suggests a much simpler SoH.
Huazhang (vivo) replies to add the question
Belen (Ericsson) agrees to have simpler questions for a SoH.
Yang (OPPO) we do not think the 1st question needs to be asked due to it does not make sense
Haiyang (Huawei) suggests a way forward, provides r08, and objects r01 to r07.
Josep (DT) supports Belén's (Ericsson) wording that the SoH questions should be solution-neutral.
Yang (OPPO) objects r08 as the concern shown in very first email that the evaluation is confusing
Changhong (Intel) asks companies to work in a constructive way in the spirit of 3GPP compromising.
Josep (DT) replies to Changhong (Rapporteur).
Yang (OPPO) supports r05 which is the minimum agreement we possibly can get in this meeting
Jicheol (Samsung) objects r05 and r08 and supports r06 and r07.
And also supports a show-of-hands to make a progress.
Josep (DT) provides a r09 that can be used as basis for the result of the SoH, i.e. remove non-agreeable text.
Dimitris (Lenovo) does not see how any revision helps in arriving at a conclusion prefers to have a SoH first
Josep (DT) replies to Dimitris (Lenovo). Prefers to have a simple SoH as we cannot even agree on the basics
Changhong (Intel) comments and proposes to have a SoH on simple questions.
Changhong (Intel) proposes to ask one more question for SoH.
Josep (DT) replies to Changhong (Intel) and suggests to keep the SoH simple.
Haiyang (Huawei) is open to question 4 for SoH, provides r10.
==== 9.X, 10.X Revisions Deadline ====
Krisztian (Apple) can only accept r05 and proposes a new SoH question.
Changhong (Intel) uploads the SoH slides for CC#4.
Haiyang (Huawei) comments to Krisztian (Apple).
Pinghui(China Telecom) comments.
Yang (OPPO) support Apple's suggestion and comments.
Google (Pavan) also supports Apple's views and prefers Q0 from Apple for SoH.
Josep (DT) supports going with the SoH and depending on its result base the agreed conclusions on r09 or a subset of r09 (+if needed add something related to Q4), completely disagrees with Krisztian (Apple).
Jicheol (Samsung) propose the change of SoH Question 4 to cover all different solutions.
Jicheol (Samsung) comments on SoH Q3 (user consent).
Pallab (Nokia) supports views from Apple, Google, Oppo and prefers Q0 as proposed by Apple for SoH.
Josep (DT) answers to Pallab (Nokia), cites SID justification section. There is no technical or formal argument for including Q0.
Dimitris (Lenovo) agrees with Josep (DT) views
Haiyang (Huawei) agrees with Dimitris (Lenovo) and Josep (DT) views
Yang (OPPO): if the URSP is not supported by a UE, then no way to enforce it. If it is supported by a UE, then it will enforce it as requested by URSP
Pallab (Nokia) responds to Josep (DT)
Huazhang (vivo) agree with OPPO that UE reports the unsupported URSP rules is more valuable, and if the UE is 3GPP UE, and we still have the different understanding of whether UE not enforce URSP rules or the error situaiton. So, this needs time to have more discussion, because the UE is 3GPP UE, whether exists abnormal situation is FFS.
Changhong (Intel) believes Q0 has been covered by Q4 Option B and doubts the need of asking Q1 instead.
Haiyang (Huawei) share similar view as Jicheol (Samsung) , suggest to remove SoH Q3 (user consent).
Changhong (Intel) updated the SoH questions for KI#2.
Josep (DT) requests the word 'supported' to be removed. The word is not part of the text of KI#2
Susana (Vodafone) agrees with Josep. The KI is about enforcement of rules, not support of rules
Josep (DT) replies to Pallan (Nokia).
Google (Pavan) can only support r05
Huazhang (vivo) can only accept r05 at this moment for the minimum agreement, and object any other revisions
Dimitris (Lenovo) can only accept r00 objects to other revisions
Haiyang (Huawei) suggests to go with r08 with only evaluation part
Josep (DT) objects to r00-r08.
Pinghui(China Telecom) support r08 to make a little progress
Noted
9.22 S2-2206041 P-CR Approval 23.700-85: KI#2, Evaluation and way forward China Telecom Rel-18 Merged into S2-2205717 (noted). Noted Merge into S2-2205717 Changhong (Intel) proposes to use S2-2205717 as baseline for KI#2 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205717.
==== 9.X, 10.X Final Deadline ====
Noted
9.22 S2-2206404 P-CR Approval 23.700-85: EUEPO KI#2 Evaluation and Conclusion for KI#2 NEC Rel-18 Merged into S2-2205717 (noted). Noted Merge into S2-2205717 Changhong (Intel) proposes to use S2-2205717 as baseline for KI#2 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205717.
==== 9.X, 10.X Final Deadline ====
Noted
9.22 S2-2206850 P-CR Approval 23.700-85: KI#2 A way forward on UE reporting Samsung Rel-18 Merged into S2-2205717 (noted). Noted Merge into S2-2205717 Changhong (Intel) proposes to use S2-2205717 as baseline for KI#2 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205717.
==== 9.X, 10.X Final Deadline ====
Noted
9.22 S2-2206947 P-CR Approval 23.700-85: KI#2: Evaluation and interim conclusion Apple Rel-18 Merged into S2-2205717 (noted). Noted Merge into S2-2205717 Changhong (Intel) proposes to use S2-2205717 as baseline for KI#2 evaluation and conclusion.
Yang (OPPO): My comment in thread can be ignored since I get the title wrong, the correct title should be '[SA2#152E, AI#9.11, S2-2205717] 23.700-85: Evaluation and conclusion of KI#2'. And I have moved my comment to that thread. Sorry...
Belen (Ericsson) provides comments
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2205717.
==== 9.X, 10.X Final Deadline ====
Noted
9.22 - - - Solution Update for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=5 -
9.22 S2-2205530 P-CR Approval 23.700-85: KI#3, Sol#16 update clarifying handling of PCRTs in mobility Ericsson Rel-18 Approved DongYeon (Samsung) comments.
Belen (Ericsson) replies to Samsung
DongYeon (Samsung) is okay with this paper.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206066 P-CR Approval 23.700-85: KI#3, Solution#33 Update: Consistent URSP Provisioning across 5GS and EPS Intel Rel-18 r01 agreed. Revised to S2-2207503. Huazhang (vivo) ask a question
Changhong (Intel) provides r01 and replies to Huazhang.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207503 P-CR Approval 23.700-85: KI#3, Solution#33 Update: Consistent URSP Provisioning across 5GS and EPS Intel Rel-18 Revision of S2-2206066r01. Approved Approved
9.22 S2-2206254 P-CR Approval 23.700-85: 23.700-85: Updates to Solution #34 Nokia, Nokia Shanghai Bell Rel-18 Noted DongYeon (Samsung) comments.
Pallab (Nokia) responds to DongYeon (Samsung).
Changhong (Intel) comments and has strong concern with this paper.
Pallab (Nokia) responds to Changhong (Intel)
Belen (Ericsson) provides comments, cannot accept the initial version.
Changhong (Intel) objects to this paper and any revision.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.22 S2-2206923 P-CR Approval 23.700-85: KI#3, Solution #20 Update: URSP delivery for the UE in EPS Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 - - - Evaluation and Conclusion for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=3 -
9.22 S2-2206068 P-CR Approval 23.700-85: KI#3 Evaluation and Conclusion Intel Rel-18 CC#4: r08 + changes proposed. Revised to S2-2207883, merging S2-2205729. Baseline paper for KI#3 Changhong (Intel) proposes to use this paper as baseline for KI#3 evaluation and conclusion.
Changhong (Intel) provides r01 per offline discussion.
Pallab (Nokia) comments and provides r02
Belen (Ericsson) cannot accept r02, asks Pallab to work with proposed Principles.
Changhong (Intel) replies to Pallab and asks Nokia to work in a constructive way.
Pallab (Nokia) responds
Changhong (Intel) responds to Pallab and provides r03 with removing the EN in the conclusion
Pallab (Nokia) objects to r03
Yang (OPPO) agree with Intel's comment and support r01 or 03
Changhong (Intel) further replies to Pallab.
Huazhang (vivo) provides r04
Changhong (Intel) proposes to have a show of hands on concluding Sol#34 or ePCO based solution at CC#4 or CC#5 if Nokia still objects to r00, r01, r03 and potentially r04.
Pallab (Nokia) is OK to go with PCO based solution as baseline. Provides r05 with additional evaluation comments and some ENs
Changhong (Intel) thanks Pallab and provides r06.
Belen (Ericsson) provides r07
Huazhang (vivo) not ok with R07 to remove the words about UE return from EPS to 5GS.
Changhong (Intel) provides r08 to address concerns from both Belen and Huazhang.
==== 9.X, 10.X Revisions Deadline ====
Pallab (Nokia) is OK with r08
DongYeon (Samsung) is OK with r08, objects to r07.
Huazhang (vivo) can compromise to go with r08, and not ok with any other revisions.
Changhong (Intel) provides draft r09 and asks for CC#4 approval based on offline comments from Yang.
Yang (OPPO) supports r09 for CC#4 approval
DongYeon (Samsung) comments on r09.
Yang (OPPO) replies to DongYeon (Samsung)
Changhong (Intel) replies to DongYeon
Changhong (Intel) provides changes on top of R08: Remove 'EPS and' from the second bullet of the conclusion and add following EN:
Editor's note: It is FFS whether an explicit URSP Provisioning Support Indication in EPS in UE Policy Container needs to be included when UE does Initial Attached in EPS.
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207883 P-CR Approval 23.700-85: KI#3 Evaluation and Conclusion Intel Rel-18 Revision of S2-2206068r08 + changes, merging S2-2205729. Approved Approved
9.22 S2-2205729 P-CR Approval 23.700-85: KI#3 Evaluation and Conclusion OPPO, vivo Rel-18 Merged into S2-2207883 Merge into S2-2206068 Changhong (Intel) proposes to use S2-2206068 as baseline for KI#3 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2206068.
==== 9.X, 10.X Final Deadline ====
Merged
9.22 - - - Solutions Update for KI#4 (Support standardized and operator-specific traffic categories in URSP) - - Docs:=3 -
9.22 S2-2205518 P-CR Approval 23.700-85: Update to Solution #35 AT&T, Vodafone, Deutsche Telekom, Verizon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206253 P-CR Approval 23.700-85: 23.700-85: Updates to Solution #22 Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 S2-2206307 P-CR Approval 23.700-85: KI#4 Sol#24 update to solve the Ens Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.22 - - - Evaluation and Conclusion for KI#4 (Support standardized and operator-specific traffic categories in URSP) - - Docs:=4 -
9.22 S2-2206805 P-CR Approval 23.700-85: KI #4: Evaluation and Conclusion of Key Issue #4 KDDI, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206439. Merged into S2-2207504 Merge into S2-2206708 Changhong (Intel) proposes to use S2-2206708 as baseline for KI#4 evaluation and conclusion.
Masaharu (KDDI) is fine to merge this paper into S2-2206708.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.22 S2-2206708 P-CR Approval 23.700-85: KI#4: Evaluation and conclusion Vodafone, AT&T, Verizon, Deutsche Telekom, Meta USA Rel-18 r10 + changes agreed. Revised to S2-2207504, merging S2-2206308 and S2-2206805 Baseline paper for KI#4 Changhong (Intel) proposes to use this paper as baseline for KI#4 evaluation and conclusion.
Dimitris (Lenovo) provides initial comments
Curt (Meta) comments that, based on Rapporteur's input, any potential 3GPP 'standardized' traffic categories can be defined/discussed during study or normative phase even when this KI#4/Solution is concluded.
Susana (Vodafone) comments that revisions for conclusion papers, from non-original authors, have been discussed in CC#1 to be in the draft folder and asks Changhong to confirm.
Susana (Vodafone) answers to Dimitris
Masaharu (KDDI) provides r01 merged with S2-2206805.
Huazhang (vivo) provides comments
Changhong (Intel) replies to Susana and Curt.
Pallab (Nokia) comments on r01.
Huazhang (vivo) answer a question to Farooq(AT&T)
Curt (Meta) provides r02.
Farooq(AT&T) responds to Dimitris (Lenovo).
Dimitris (Lenovo) responds to Susana (Vodafone).
Farooq(AT&T) responds to Pallab(Nokia).
Dimitris (Lenovo) responds to Farooq
Susana (Vodafone) provides r03 based on r02 and comments
Belen (Ericsson) provides comments.
Farooq(AT&T) responds to Huazhang (vivo).
Haiyang (Huawei) provides r04.
Farooq (AT&T) cannot accept r04.
Susana (Vodafone) agrees with Farooq and cannot accept r04 as is, provides r05 incorporating some of the comments.
Pallab (Nokia) comments.
Haiyang (Huawei) comments.
Masaharu (KDDI) provides r06, supports it, responds to Haiyang (Huawei)
Susana (Vodafone) responds to Haiyang and Pallab.
Pavan (Google) provides some comments and r07.
Haiyang (Huawei) responds and provides r08.
Pallab (Nokia) responds to Susana (Vodafone)
Haiyang (Huawei) provides r09.
Susana (Vodafone) responds to Haiyang and provides r10.
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) supports r10, objects to other revisions(including r00) in case.
Pallab (Nokia) is OK r10 and co-signs.
Changhong (Intel) supports to move forward with R10 and Intel also co-signs R10.
Google (Pavan) supports r10 as well.
Susana (Vodafone) thanks all for the support. A rev11 adding ONLY new cosigners is in the revisions folder.
==== 9.X, 10.X Final Deadline ====
Revised
9.22 S2-2207504 P-CR Approval 23.700-85: KI#4: Evaluation and conclusion Vodafone, AT&T, Verizon, Deutsche Telekom, Meta USA Rel-18 Revision of S2-2206708r10 + changes, merging S2-2206308 and S2-2206805. Approved Approved
9.22 S2-2206308 P-CR Approval 23.700-85: KI#4_evaluation_and_conclusion Vivo Rel-18 Merged into S2-2207504 Merge into S2-2206708 Changhong (Intel) proposes to use S2-2206708 as baseline for KI#4 evaluation and conclusion.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) proposes to mark it as merged into S2-2206708.
==== 9.X, 10.X Final Deadline ====
Merged
9.22 - - - Documents exceeding TU Budget - - Docs:=15 -
9.22 S2-2205731 P-CR Approval 23.700-85: Clarification to soln#6 OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2205531 P-CR Approval 23.700-85: KI#3, Evaluation and Conclusion Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206067 P-CR Approval 23.700-85: KI#1 Evaluation and Conclusion Intel, Qualcomm Inc. Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206108 P-CR Approval 23.700-85: KI#1, Conclusion LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206251 P-CR Approval 23.700-85: 23.700-85: Conclusions for KI#1 Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206565 P-CR Approval 23.700-85: Evaluation and Conclusion for KI #1 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206306 P-CR Approval 23.700-85: KI#3 Sol# 33 update to solve the multiple UE policy association issue Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206439 P-CR Approval 23.700-85: KI #4: Evaluation and Conclusion of Key Issue #4 KDDI Rel-18 Revised to S2-2206805 Revised
9.22 S2-2206807 P-CR Approval 23.700-85: KI#4: xR as a standardized 3GPP traffic category Meta USA Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2205572 P-CR Approval 23.700-85: KI#2: Evaluation and interim conclusions Lenovo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206252 P-CR Approval 23.700-85: 23.700-85: Conclusions for KI#2 Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2206305 P-CR Approval 23.700-85: KI#2_evaluation_and_conclusion Vivo, OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2205718 P-CR Approval 23.700-85: Evaluation and conclusion of KI#3 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2205573 P-CR Approval 23.700-85: KI#4: Evaluation and interim conclusions Lenovo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.22 S2-2205719 P-CR Approval 23.700-85: Evaluation and conclusion of KI#4 Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 - - - Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) - - Docs:=132 -
9.23 - - - Key Issue #1: How to improve correctness of NWDAF analytics - - Docs:=8 -
9.23 - - - New solution - - Docs:=6 -
9.23 S2-2205675 P-CR Approval 23.700-81: New solution for KI#1 and KI#4_Improving correctness by retrieval historical model from ADRF China Telecom, vivo Rel-18 r02 agreed. Revised to S2-2207130. Zhang (Ericsson) provides comments
Wang Yuan (Huawei) provides comments.
Menghan (China Telecom) replies to Zhang (Ericsson) and Yuan (Huawei).
Juan Zhang (Qualcomm) provides comments.
Fabio (Nokia) provides comments.
Menghan (China Telecom) replies to Zhang (Ericsson), Costas (Lenovo), Juan(Qualcomm) and Fabio(Nokia)
Menghan (China Telecom) replies to Fabio(Nokia)
Malla (NTT DOCOMO) asks for clarification.
Menghan (China Telecom) provides r01 and replies to Malla (NTT DOCOMO)
Antoine (Orange) comments.
Menghan (China Telecom) replies to Antoine (Orange)
Menghan (China Telecom) replies to Fabio (Nokia)
Antoine (Orange) asks a question on the new services.
Antoine (Orange) provides r02 (adding an EN on services impacts).
==== 9.X, 10.X Revisions Deadline ====
Fabio (Nokia) is Ok with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207130 P-CR Approval 23.700-81: New solution for KI#1 and KI#4_Improving correctness by retrieval historical model from ADRF China Telecom, vivo Rel-18 Revision of S2-2205675r02. Approved Approved
9.23 S2-2205946 P-CR Approval 23.700-81: KI#1, New Sol: Improving the correctness of analytics based on the provision of context information Orange Rel-18 r02 agreed. Revised to S2-2207131. Wang Yuan (Huawei) provides comments.
Antoine (Orange) replies to Wang Yuan and provides r01.
Akito (KDDI) provides comments
Juan Zhang (Qualcomm) provides comments
Dimitris (Lenovo) requests clarification on the use case
Antoine (Orange) replies and provides r02.
Zhang (Ericsson) ask for clarification
Antoine (Orange) replies to Malla.
Malla (NTT DOCOMO) provides comments
Antoine (Orange) confirms Zhang's understanding.
Zhang (Ericsson) provides comment
==== 9.X, 10.X Revisions Deadline ====
Malla (NTT DOCOMO) fine with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207131 P-CR Approval 23.700-81: KI#1, New Sol: Improving the correctness of analytics based on the provision of context information Orange Rel-18 Revision of S2-2205946r02. Approved Approved
9.23 S2-2206105 P-CR Approval 23.700-81: Solution to KI#1: Improving the correctness of NWDAF by rating the quality of the data sources Lenovo Rel-18 r05 agreed. Revised to S2-2207132. Zhang (Ericsson) provides comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207132 P-CR Approval 23.700-81: Solution to KI#1: Improving the correctness of NWDAF by rating the quality of the data sources Lenovo Rel-18 Revision of S2-2206105r05. Approved Approved
9.23 - - - Update solution - - Docs:=11 -
9.23 S2-2205542 P-CR Approval 23.700-81: KI#1, Sol#29: Update to remove EN Ericsson Rel-18 r01 agreed. Revised to S2-2207133. Costas (Lenovo) provides comments.
Zhang (Ericsson) response to Costas (Lenovo)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207133 P-CR Approval 23.700-81: KI#1, Sol#29: Update to remove EN Ericsson Rel-18 Revision of S2-2205542r01. Approved Approved
9.23 S2-2205721 P-CR Approval 23.700-81: KI#1, Sol#28 Update to remove the ENs Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207134. Zhang (Ericsson) ask for clarification
Dimitris (Lenovo) comments
Haiyang (Huawei) clarifies
Zhang (Ericsson) asks for further clarification
Haiyang (Huawei) further clarifies
Zhang (Ericsson) response to Haiyang (Huawei)
Haiyang (Huawei) further clarifies, provides r02
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) is OK with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207134 P-CR Approval 23.700-81: KI#1, Sol#28 Update to remove the ENs Huawei, HiSilicon Rel-18 Revision of S2-2205721r02. Approved Approved
9.23 S2-2206073 P-CR Approval 23.700-81: KI#1, Sol#31: Update to resolve an EN ETRI Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206157 P-CR Approval 23.700-81: KI#1: Update to Solution#7 Sony Rel-18 Noted Wang Yuan (Huawei) has concerns for the initial version.
Wang Shuo (Sony) replies to Yuan's comments.
Wang Shuo (Sony) replies to Costas's comments.
Wang Shuo (Sony) replies to Costas (Lenovo)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.23 S2-2206417 P-CR Approval 23.700-81: KI#1, Sol#3, update to remove En Vivo Rel-18 r03 agreed. Revised to S2-2207135. Zhang (Ericsson) provides comments
Xiaobo (vivo) replies to comments from Zhang(Ericsson) and provides r01.
Fabio (Nokia) provides comments.
Xiaobo (vivo) replies to comments from Fabio(Nokia) and provides r02/r03.
Fabio (Nokia) replies to comments
Xiaobo (vivo) replies to Fabio(Nokia) and proposes to go with r03.
==== 9.X, 10.X Revisions Deadline ====
Fabio (Nokia) is Ok with r03.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207135 P-CR Approval 23.700-81: KI#1, Sol#3, update to remove En Vivo Rel-18 Revision of S2-2206417r03. Approved Approved
9.23 S2-2206671 P-CR Approval 23.700-81: KI#1, Sol#7: Updates to remove EN Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207136. Zhang (Ericsson) provides comments
Wang Yuan (Huawei) provides comments.
Fabio (Nokia) replies to comments.
Zhang (Ericsson) response to Fabio (Nokia)
Fabio (Nokia) replies to Zhang (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207136 P-CR Approval 23.700-81: KI#1, Sol#7: Updates to remove EN Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206671r01. Approved Approved
9.23 S2-2206672 P-CR Approval 23.700-81: KI #1, Sol#34: Update to solve ENs Nokia, Nokia Shanghai Bell Rel-18 Approved Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments from Zhang (Ericssson).
Xiaobo (vivo) provides comments
Fabio (Nokia) replies to comments.
Dimitris (Lenovo) asks whether the NWDAF (AnLF) subscription should be to ADRF or DCCF
Xiaobo (vivo) provides further comments and think the proposal is interested.
Fabio (Nokia) replies to Dimitris (Lenovo).
Zhang (Ericsson) response to Fabio (Nokia)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 - - - Evaluation & Conclusion - - Docs:=3 -
9.23 S2-2205541 P-CR Approval 23.700-81: KI#1: Evaluation for solutions for improving correctness of NWDAF Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206412 P-CR Approval 23.700-81: KI#1, Evaluation and interim conclusion Vivo, Inspur Rel-18 r19 agreed. Revised to S2-2207137. Baseline as interim conclusion/principle Zhang (Ericsson) provides comments
xiaobo(vivo) provides clarification.
Dimitris (Lenovo) provides initial comments
Mike (InterDigital) provides r02
Juan Zhang (Qualcomm) provides comments
Fabio (Nokia) provides comments and r03
xiaobo(vivo) provides clarification and provide r04.
Zhang (Ericsson) provides r05
Fabio (Nokia) replies to comments and objects to r05.
xiaobo(vivo) comments and provides r06.
Malla (NTT DOCOMO) provided r07.
Dimitris (Lenovo) provides r08
xiaobo(vivo) comments and provides r09.
Soohwan (ETRI) provides r10.
Malla (NTT DOCOMO) objects r11.
Haiyang (Huawei) provides r11.
Zhang (Ericsson) provides comments and r12 based on r10
Soohwan (ETRI) provides r13.
xiaobo(vivo) shares the concern from Zhang(Ericsson) and prefer r12.
Soohwan (ETRI) provides r14.
Fabio (Nokia) provides r15.
Haiyang (Huawei) provides questions to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to Haiyang (Huawei).
Haiyang (Huawei) provides r16.
Zhang (Ericsson) provides comments to r16
Fabio (Nokia) objects to r16 and provides r17
xiaobo(vivo) comments and provide r18.
Xiaoyan (CATT) provides r19.
==== 9.X, 10.X Revisions Deadline ====
Dimitris (Lenovo) can accept r19 with a change in one of the EN
Malla (NTT DOCOMO) fine with r19 also with a change proposed by Dimitris (Lenovo)
xiaobo(vivo) replies to Dimitris(Lenovo) and ask if Dimitris(Lenovo) could live with R18 .
Fabio (Nokia) is Ok with r19 and the change proposed by Dimitris (Lenovo).
Haiyang (Huawei) is Ok with r19 and the change proposed by Dimitris (Lenovo).
xiaobo(vivo) also proposes to go with r19 and the change proposed by Dimitris (Lenovo).
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207137 P-CR Approval 23.700-81: KI#1, Evaluation and interim conclusion Vivo, Inspur Rel-18 Revision of S2-2206412r19. Approved Approved
9.23 - - - Key Issue #2: NWDAF-assisted application detection - - Docs:=19 -
9.23 - - - New solution & update solution - - Docs:=5 -
9.23 S2-2206408 P-CR Approval 23.700-81: KI#2, New Sol: NWDAF assisted XR service detection Vivo, China Telecom Rel-18 Noted Belen (Ericsson) objects to this contribution, it is not in the scope of this KI
Xiaobo (vivo) replies to questions from Belen (Ericsson) and propose to hold on objection and wait for the discussion outcome of XRM.
Wang Yuan (Huawei) provides comments.
Juan Zhang (Qualcomm) provides comments and propose to note the contribution.
Thomas(Nokia) shares concerns that this contribution is not in scope of the key issue.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.23 S2-2205544 P-CR Approval 23.700-81: KI#2, Solution #9: Update to NWDAF-assisted application detection Ericsson Rel-18 r01 agreed. Revised to S2-2207138. Thomas (Nokia) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207138 P-CR Approval 23.700-81: KI#2, Solution #9: Update to NWDAF-assisted application detection Ericsson Rel-18 Revision of S2-2205544r01. Approved Approved
9.23 S2-2205890 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#2, Sol#9 updates to EN and clarification China Mobile Rel-18 r07 agreed. Revised to S2-2207139. Thomas (Nokia) provides r02
Objects against r00 and r01
Yang (OPPO) is not happy with r00-02 and bring r03
Aihua (CMCC) replies to Tomas (Nokia) and Yang (OPPO), and provides r04.
Yang (OPPO) comments.
Aihua (CMCC) replies to Yang (OPPO) and provides r05.
Yang (OPPO) agrees with the potential benefits and okay to r05
Thomas(Nokia) provides r06.
Aihua (CMCC) replies to Thomas (Nokia) and provides r07.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207139 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#2, Sol#9 updates to EN and clarification China Mobile Rel-18 Revision of S2-2205890r07. Approved Approved
9.23 - - - Evaluation & Conclusion - - Docs:=2 -
9.23 S2-2205891 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#2 evaluation and conclusion China Mobile Rel-18 r03 agreed. Revised to S2-2207140. Thomas (Nokia) provides r01
Aihua (CMCC) replies to Thomas (Nokia) and provides r02.
Thomas (Nokia) provides r03.
Aihua (CMCC) replies to Thomas (Nokia).
Thomas (Nokia) replies to Aihua (CMCC)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207140 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#2 evaluation and conclusion China Mobile Rel-18 Revision of S2-2205891r03. Approved Approved
9.23 - - - Key Issue #3: Data and analytics exchange in roaming case - - Docs:=13 -
9.23 - - - Update solution - - Docs:=6 -
9.23 S2-2206129 P-CR Approval 23.700-81: KI#3, Sol#37 Update to remove some FFS Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207141. Thomas (Nokia) provides r01 and objects against r00
==== 9.X, 10.X Revisions Deadline ====
Wang Yuan (Huawei) can accept r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207141 P-CR Approval 23.700-81: KI#3, Sol#37 Update to remove some FFS Huawei, HiSilicon Rel-18 Revision of S2-2206129r01. Approved Approved
9.23 S2-2206130 LS OUT Approval [DRAFT] LS to SA WG3 on the raw data exchange between two NWDAFs in different PLMNs Huawei, HiSilicon Rel-18 CC#4: r07 with changes proposed. r07 agreed. Revised to S2-2207142. Zhang (Ericsson) provides comments
Juan Zhang (Qualcomm) provides comments
Malla (NTT DOCOMO) provides comments
Thomas(Nokia) provides comments and r01. Objects against r00
Zhang (Ericsson) supports r01
Jungshin (Samsung) provides comments and r02
Wang Yuan (Huawei) suggests to ask GSMA to provide principles or limitations on what kind of data and/or analytics can be exchanged between PLMNs and provide r03
Zhang (Ericsson) provides comment to r03
Wang Yuan (Huawei) replies to Zhang (Ericsson) and provides r04
Malla (NTT DOCOMO) provided r05
Jungshin (Samsung) provides r06
Thomas (Nokia) provides r07
Wang Yuan (Huawei) asks for clarification for Thomas (Nokia)'s comments.
==== 9.X, 10.X Revisions Deadline ====
Thomas (Nokia)'s replies to Wang Yuan
Wang Yuan (Huawei) thanks Thomas for the clarification and can live with r07 to make progress.
Xiaobo (vivo) provides clarification and propose to go with r07 to make progress.
Xiaoyan (CATT) supports to use r07 as a way forward.
Thomas(Nokia) replies to Xiaobo.
Zhang (Ericsson) is OK with r07
Malla (NTT DOCOMO) asks clarification to Thomas(Nokia) and Objects r07.
Malla (NTT DOCOMO) objects r07 and fine with r06/r05.
Thomas(Nokia) provides clarifications to Mala and asks her if she maintains her objection.
Nokia objects against r00, r03, r04, r05 and r06
Malla (NTT DOCOMO) replies to Thomas(Nokia) and still objects r07
Thomas(Nokia) replies to Manilla and suggest
Agreeing r07 +
Append to question 1: 'or are there any privacy and security issues foreseen when exchange data and/or analytics between PLMNs'
(or late r08)
Malla (NTT DOCOMO) fine with r08
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207142 LS OUT Approval [DRAFT] LS to SA WG3 on the raw data exchange between two NWDAFs in different PLMNs Huawei, HiSilicon Rel-18 Revision of S2-2206130r07. Approved Approved
9.23 S2-2206936 P-CR Approval 23.700-81: Update of Solution #40 Samsung Rel-18 r03 agreed. Revised to S2-2207143. Vivian (vivo) asks question.
Thomas (Nokia) provides r01
Vivian (vivo) tries to find way forward to Thomas (Nokia)'s question and provides r02
Jungshin (Samsung) provides clarification and r03
Vivian(vivo) is OK with r03
Thomas (Nokia) is fine with r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207143 P-CR Approval 23.700-81: Update of Solution #40 Samsung Rel-18 Revision of S2-2206936r03. Approved Approved
9.23 - - - Evaluation & Conclusion - - Docs:=7 -
9.23 S2-2205535 P-CR Approval 23.700-81: KI#3, Evaluation and Conclusion Proposals Ericsson Rel-18 Merged into S2-2207144 Focus on architecture part Jari (NTT DOCOMO) comments
Malla (NTT DOCOMO) asks group to select two pCRs for evaluation and conclusion.
Thomas(Nokia) suggest following rapporteur´s proposal and use S2-2206446 as baseline for evaluation and S2-2206447 as baseline for conclusions, but also include architectural conclusions in that contribution.
Thus suggest noting (or merging) the present contribution.
xiaobo(vivo) provides clarification why propose to have two sperate discussions for roaming architecture and roaming use case and still prefer to go with the original handling proposal during eNA sorting .
Vivian (vivo) asks Ericsson (Zhang) if you agree to use S2-2206414 as the architecture baseline and merge S2-2205535 to it.
Zhang (Ericsson) is OK to merge 5535 into 6414. Zhang suggest to remove the evaluation part from 6414. Using 6446 as the baseline for solution evaluations.
Vivian(vivo) thanks to Zhang (Ericsson)'s reminder and has already removed the evaluation part from 6414.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.23 S2-2206414 P-CR Approval 23.700-81: KI#3, Evaluation and interim conclusion Vivo, Inspur Rel-18 r08 agreed. Revised to S2-2207144, merging and S2-2205535 Focus on architecture part Thomas(Nokia) suggest following rapporteur´s proposal and use S2-2206446 as baseline for evaluation and S2-2206447 as baseline for conclusions, but also include architectural conclusions in that contribution.
Thus suggest noting (or merging) the present contribution.
Vivian(vivo) replies to Thomas' (Nokia) comments and provides s2-2206414r01 on architectural conclusions.
Wang Yuan (Huawei) suggests to use 6414 as baseline for the roaming architecture related conclusion, while use the 6447 as the roaming use case related conclusion.
Malla (NTT DOCOMO) provides r02.
Zhang (Ericsson) suggest to remove the evaluation part from this pCR, the evaluation is addressed in 6446.
Jungshin (Samsung) provides comments.
Vivian (vivo) replies to questions and provides r03.
Thomas(Nokia) provides r04.
Malla (NTT DOCOMO) provides r05.
Thomas (Nokia) provides r06.
Wang Yuan (Huawei) provides r07 and co-signs this paper.
Vivian(vivo) provides r08 based on r07.
Jungshin (Samsung) provides a comment on r07
Jungshin (Samsung): we are fine with r08
Zhang (Ericsson) is fine with r08 and co-sign
Xiaoyan (CATT) provides r10
Zhang (Ericsson) response to XiaoYan (CATT)
XiaoYan (CATT) response to Zhang (Ericsson)
Zhang (Ericsson) provide r11
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) response to Thomas (Nokia) and suggest to go with r08
Thomas(Nokia) objects against r10 and r11
Wang Yuan (Huawei) also suggests to go with r08.
Jungshin (Samsung): supports r08 as interim agreement.
Thomas (Nokia) is fine with r08
Vivian (vivo) also suggests to go with r08
Malla (NTT DOCOMO) is fine with r08
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207144 P-CR Approval 23.700-81: KI#3, Evaluation and interim conclusion vivo, Inspur, Huawei, Ericsson, CATT, Nokia Rel-18 Revision of S2-2206414r08, merging and S2-2205535. Approved Approved
9.23 S2-2206446 P-CR Approval 23.700-81: KI#3: Evaluation of solutions CATT Rel-18 r04 agreed. Revised to S2-2207145. Baseline for evaluation Thomas (Nokia) provides r01
Jungshin (Samsung) provides comments and proposes to remove consideration part.
Xiaoyan (CATT) provides r02
Thomas (Nokia) provides r03
Xiaoyan (CATT) provides r04 to address comment from Jungshin (Samsung).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207145 P-CR Approval 23.700-81: KI#3: Evaluation of solutions CATT Rel-18 Revision of S2-2206446r04. Approved Approved
9.23 S2-2206447 P-CR Approval 23.700-81: KI#3 Interim conclusions CATT Rel-18 CC#4: r05 with changes proposed. r05 agreed. Revised to S2-2207146. Baseline for conclusion of roaming use cases and leave architecture part to other papers S2-2205535/S2-2206414/S2-2206437 Thomas (Nokia) provides r01
Zhang (Ericsson) provides comments and suggest to remove the conclusion for architecture aspect.
Jungshin (Samsung) supports proposal from Zhang (Ericsson) to discuss conclusion part for arch aspects in the 6414 thread.
Xiaoyan (CATT) provides r02
Thomas(Nokia) objects against r02 and provides r04
Xiaoyan (CATT) objects to r04 and provides r05
==== 9.X, 10.X Revisions Deadline ====
Thomas(Nokia) objects to r05
Thomas(Nokia) objects to r00
Thomas(Nokia) proposes a change on top of r05, suggest to discuss at CC:
R05 + Remove 'provided by the VPLMN' from last bullet
Xiaoyan (CATT) proposes update on top of r05
Thomas(Nokia) replies to Xiaoyan
Thomas(Nokia) corrects proposed change on top of r05, suggest to discuss at CC:
R05
+ First EN modified to read 'It is ffs if the analytics information is analytics, analytics profiles or both'
+ Remove 'provided by the VPLMN' from last bullet
Xiaoyan (CATT) is fine with the proposed changes from Thomas(Nokia) on top of r05
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207146 P-CR Approval 23.700-81: KI#3 Interim conclusions CATT Rel-18 Revision of S2-2206447r05. Approved Approved
9.23 - - - Key Issue #4: How to Enhance Data collection and Storage - - Docs:=13 -
9.23 - - - New solution - - Docs:=7 -
9.23 S2-2205892 P-CR Approval 23.700-81: FS_eNA_Ph3 KI #4, New Sol Optimization on the collection and reporting of network data China Mobile Rel-18 r02 agreed. Revised to S2-2207147. Aihua(CMCC) replies.
Zhang (Ericsson) provides comments
Zhang (Ericsson) provides r01
Fabio (Nokia) provides comments.
Aihua(CMCC) replies and provides r02.
==== 9.X, 10.X Revisions Deadline ====
Fabio (Nokia) is OK with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207147 P-CR Approval 23.700-81: FS_eNA_Ph3 KI #4, New Sol Optimization on the collection and reporting of network data China Mobile Rel-18 Revision of S2-2205892r02. Approved Approved
9.23 S2-2205947 P-CR Approval 23.700-81: KI#4, New Sol: Optimizing data collection and storage by NWDAF registration in UDM for all Analytics IDs Orange Rel-18 Approved Antoine (Orange) replies to Zhang that his understanding is correct.
Zhang (Ericsson) ask for clarification
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206121 P-CR Approval 23.700-81: FS_eNA_Ph3 KI #4, New Sol DCCF relocation initiated by source DCCF or central DCCF China Mobile Rel-18 Approved Zhang (Ericsson) provides comments and ask for clarification
Aihua (CMCC) replies to Zhang(Ericsson).
Fabio (Nokia) provides comments.
Aihua (CMCC) replies to Fabio(Nokia).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206674 P-CR Approval 23.700-81: KI#4, New Sol: Managing analytics input data from ADRF Nokia, Nokia Shanghai Bell Rel-18 Approved Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments from Zhang (Ericsson).
Malla (NTT DOCOMO) asks for clarification.
Fabio (Nokia) replies to comments.
Zhang (Ericsson) response to comments
Zhang (Ericsson) asks questions
Zhang (Ericsson) responses to Fabio (Nokia)
Zhang (Ericsson) response to Fabio (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206675 P-CR Approval 23.700-81: KI#4 New Sol: using generative models for data storage and transfer Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2207148. Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments from Zhang (Ericsson).
Malla (NTT DOCOMO) provided comment.
Fabio (Nokia) replies to comments.
Juan Zhang (Qualcomm) provides comments.
Wang Yuan (Huawei) provides comments
Zhang (Ericsson) provide comments
Fabio (Nokia) provides r01.
Malla (NTT DOCOMO) fine with r01
Juan Zhang (Qualcomm) is OK with r01
Zhang (Ericsson) is OK with r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207148 P-CR Approval 23.700-81: KI#4 New Sol: using generative models for data storage and transfer Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206675r01. Approved Approved
9.23 - - - Update solution - - Docs:=2 -
9.23 S2-2206670 P-CR Approval 23.700-81: KI #4, Sol #12: Update to EN and Improvements Nokia, Nokia Shanghai Bell Rel-18 CC#4: r00 + NOTE proposed. r00 agreed. Revised to S2-2207149. Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) can go with r00 with the following changes:

NOTE 2 -> 'For this procedure, following constraint is assumed for data collection for group of UEs or any UE. The NF consumer will select a DCCF(s) that serves the area(s) where the group of UEs or any UE reside and the selected DCCF(s) will select MFAF(s) that serves the area(s) where the group of UEs or any UE reside.'
Fabio (Nokia) is Ok with the proposal from Zhang (Ericsson).
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207149 P-CR Approval 23.700-81: KI #4, Sol #12: Update to EN and Improvements Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206670r00. Approved Approved
9.23 - - - Evaluation & Conclusion - - Docs:=4 -
9.23 S2-2205537 P-CR Approval 23.700-81: KI#4: Evaluation and Conclusion for KI#4 Ericsson Rel-18 r04 agreed. Revised to S2-2207150. Baseline for evaluation Aihua(CMCC) provides r01.
Malla (NTT DOCOMO) provides r02.
Zhang (Ericsson) provides comments to r02
Malla (NTT DOCOMO) replies to Zhang (Ericsson)
Zhang (Ericsson) response to comments
Fabio (Nokia) objects all revisions up to r02 and provides r03.
Zhang (Ericsson) object r03 and provide r04
==== 9.X, 10.X Revisions Deadline ====
Fabio (Nokia) is OK with r04
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207150 P-CR Approval 23.700-81: KI#4: Evaluation and Conclusion for KI#4 Ericsson Rel-18 Revision of S2-2205537r04. Approved Approved
9.23 S2-2206679 P-CR Approval 23.700-81: KI#4 Evaluation and Conclusion Nokia, Nokia Shanghai Bell Rel-18 CC#4: r09 with changes proposed. r09 agreed. Revised to S2-2207151. Baseline for conclusion Malla (NTT DOCOMO) proposed that this pCR is merged into S2-2205537
Fabio (Nokia) replies to comments and provides r01.
Malla (NTT DOCOMO) provides r02.
Zhang (Ericsson) object r00, r01, r02 and provides r03
Wang Yuan (Huawei) provides r04.
Malla (NTT DOCOMO) provided r05 and objects r04.
Megha (Intel) provides r06 and provides comments
xiaobo(vivo) provides comments and propose to capture EN and continue the detailed discussion in future meeting.
Wang Yuan (Huawei) objects r05/r06, and provides r07.
xiaobo(vivo) provides comments and prefer r05 or r06
Fabio (Nokia) objects to all revision from r02 to r07 and provides r08.
Zhang (Ericsson) object r08
Fabio (Nokia) replies to comments.
Fabio (Nokia) replies to comments and provides r09.
Zhang (Ericsson) response to Fabio (Nokia) and provide r10
Fabio (Nokia) is not OK with r10 and replies to comments.
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) response to Fabio (Nokia) and object r09
Fabio (Nokia) replies to comments from Zhang (Ericsson).
Aihua (CMCC) provides comments and is fine with r09 or r10.
Zhang (Ericsson) response to Aihua (CMCC) and Fabio (Nokia) and suggest to go with r10
Fabio (Nokia) proposes to go with r09 and removing the first principle
Zhang (Ericsson) can go with r09 and removing the first bullet and change the third bullet to '3. For ADRF / NWDAF Data Storage Management, ADRF is configured with operator policies for data storage as defined in Solution#46.'
Fabio (Nokia) agrees to Zhang (Ericsson)'s proposal, that is, r09 without the first bullet and change the third bullet to '3. For ADRF / NWDAF Data Storage Management, ADRF is configured with operator policies for data storage as defined in Solution#46.'
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207151 P-CR Approval 23.700-81: KI#4 Evaluation and Conclusion Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2206679r09. Approved Approved
9.23 - - - Key Issue #5: Enhance trained ML Model sharing - - Docs:=0 -
9.23 - - - Update solution - - Docs:=4 -
9.23 S2-2205539 P-CR Approval 23.700-81: KI#5: Sol#47: Update: Solving ENs for Sharing of ML Models Ericsson Rel-18 r01 agreed. Revised to S2-2207152. Wang Yuan (Huawei) provides comments.
Zhang (Ericsson) response to Yuan (Huawei)
Vivian (vivo) asks some questions for clarification.
Zhang (Ericsson) response to Vivian (Vivo)
Fabio (Nokia) asks questions for clarification.
Fabio (Nokia) thanks Zhang (Ericsson) for the clarification.
Zhang (Ericsson) response to Fabio (Nokia)
Malla (NTT DOCOMO) asks for clarification
Vivian(vivo) provides r01 according to the discussion in S2-2206829 thread.
Zhang (Ericsson) is OK with r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207152 P-CR Approval 23.700-81: KI#5: Sol#47: Update: Solving ENs for Sharing of ML Models Ericsson Rel-18 Revision of S2-2205539r01. Approved Approved
9.23 S2-2206673 P-CR Approval 23.700-81: KI#5, Sol#15: Update to solve EN Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 r01 agreed. Revised to S2-2207153. Akito (KDDI) provides comments
Zhang (Ericsson) ask for clarification
Malla (NTT DOCOMO) replies to Akito (KDDI)
Fabio (Nokia) replies to comments
Zhang (Ericsson) response to Fabio (Nokia)
Fabio (Nokia) replies to comments.
Akito (KDDI) replies to Malla (NTT DOCOMO)
Zhang (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
Zhang (Ericsson) object r00
Fabio (Nokia) is OK with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207153 P-CR Approval 23.700-81: KI#5, Sol#15: Update to solve EN Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 Revision of S2-2206673r01. Approved Approved
9.23 - - - Evaluation & Conclusion - - Docs:=6 -
9.23 S2-2205538 P-CR Approval 23.700-81: KI#5: Evaluation and conclusion for Sharing of ML Models Ericsson Rel-18 r02 agreed. Revised to S2-2207154. Baseline for evaluation Malla (NTT DOCOMO) provided r01
Megha (Intel) provides r02
==== 9.X, 10.X Revisions Deadline ====
Megha (Intel) can only accept r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207154 P-CR Approval 23.700-81: KI#5: Evaluation and conclusion for Sharing of ML Models Ericsson Rel-18 Revision of S2-2205538r02. Approved Approved
9.23 S2-2206829 P-CR Approval 23.700-81: KI#5 Interim Conclusion Intel Rel-18 r06 agreed. Revised to S2-2207155. Baseline for conclusion Wang Yuan (Huawei) provides comments.
Megha (Intel) provides r01 and comments
Zhang (Ericsson) provides comments and agree with Huawei
xiaobo(vivo) comments and provides r02.
Fabio (Nokia) shares the opinion that the interoperability indicator is generally understood and the work about it can be progressed, whereas the additional ML model filter information (ML model file format supported including serialization file formats, Supported AI Framework Information) is not as well understood and deserves further work.
Megha(Intel) provides comments and would like to notify that a draft LS OUT to SA3 related to the conclusion discussion has been uploaded in the DRAFT folder
Megha(Intel) provides clarification address Fabio's concern and supports sending LS to SA3.
xiaobo(vivo) thanks Megha(Intel) for providing draft LS out to SA3 and will request TDoc number in CC#2.
Wang Yuan (Huawei) replies to Megha (Intel) and Xiaobo (vivo), and provides r03.
Malla (NTT DOCOMO) provide comment.
Zhang (Ericsson) provides r04 and comments
Fabio (Nokia) provides comments
Megha (Intel) provides comments on r04
Wang Yuan (Huawei) replies to Megha (Intel).
Zhang (Ericsson) response to Megha (Intel) and Yuan(Huawei)
Megha(Intel) objects to r04 and provides comments
Vivian (vivo) provides comments and r05 trying to make progress.
Wang Yuan (Huawei) concerns that in r05 we are agreeing an 'on-the-fly' Interoperability token and provides r06.
Zhang provides comment
Vivian (vivo) provides r07 to bring 'Interoperability token' back to the text part.
Zhang (Ericsson) response to Vivian (vivo) and OK with r07
==== 9.X, 10.X Revisions Deadline ====
Megha(Intel) objects to r04, r05,r07. Can accept r00,r01,r02,r03,r06. Provides comments.
Vivian (vivo) is fine with r06.
Zhang (Ericsson) can live with r06 and thanks Vivian (vivo)
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207155 P-CR Approval 23.700-81: KI#5 Interim Conclusion Intel Rel-18 Revision of S2-2206829r06. Approved Approved
9.23 S2-2208092 LS OUT Approval [DRAFT] LS on how ML model privacy is supported between NWDAFs belonging to different vendors vivo Created at CC#2. r02 agreed. Revised to S2-2207156. xiaobo(vivo) provide r0 for draft LS out to SA3 regarding how ML model privacy is supported between NWDAFs belonging to different vendors
Antoine (Orange) asks what 'belonging' means.
xiaobo(vivo) responds to Antoine(Orange) and provides r01
Zhang (Ericsson) ask for clarification
xiaobo(vivo) provides clarification to Zhang(Ericsson)
Fabio (Nokia) asks to clarify what 'ML model privacy' is.
xiaobo(vivo) replies to Fabio(Nokia) and provides r02
==== 9.X, 10.X Revisions Deadline ====
Megha (Intel) is ok with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207156 LS OUT Approval LS on how ML model integrity, confidentiality and availability is supported between NWDAFs from different vendors SA WG2 Rel-18 Revision of S2-2208092r02. Approved Approved
9.23 - - - Key issue #6: NWDAF-assisted URSP - - Docs:=0 -
9.23 - - - New solution - - Docs:=1 -
9.23 S2-2206443 P-CR Approval 23.700-81: KI#6 New Solution: NWDAF assisted URSP for ProSe communication CATT Rel-18 Noted LaeYoung (LGE) proposes to NOTE this pCR because the proposed solution breaks fundamental purpose for UE-to-NW relay feature.
Juan Zhang (Qualcomm) provides comments.
Jiahui (China Telecom) provides comments.
Xiaoyan (CATT) clarifies to LaeYoung (LGE) and Juan Zhang (Qualcomm) that the solution follows the existing 5G ProSe specification and in scope of the KI.
Xiaoyan (CATT) thanks to the support of Jiahui (China Telecom) and provides clarification.
Belen (Ericsson) provides comments
LaeYoung (LGE) responds to Xiaoyan (CATT).
Juan Zhang (Qualcomm) provides further comments.
Xiaoyan (CATT) responds to Belen (Ericsson).
Xiaoyan (CATT) responds to LaeYoung (LGE).
Xiaoyan (CATT) replies to Juan Zhang (Qualcomm).
Xiaoyan (CATT) provides r01.
LaeYoung (LGE) replies to Xiaoyan (CATT).
Juan Zhang (Qualcomm) replies to Xiaoyan (CATT)
Xiaoyan (CATT) clarifies to LaeYoung (LGE).
LaeYoung (LGE) answers to Xiaoyan (CATT).
Xiaoyan (CATT) answers to LaeYoung (LGE).
Xiaoyan (CATT) replies to LaeYoung (LGE).
==== 9.X, 10.X Revisions Deadline ====
Xiaoyan (CATT) provides further clarification to LaeYoung (LGE).
LaeYoung (LGE) proposes to NOTE this pCR because she thinks that this solution brings undesirable sideeffect.
Xiaoyan(CATT) replies to LaeYoung (LGE)
LaeYoung (LGE) asks to NOTE this pCR instead of approving r01.
Xiaoyan(CATT) replies to LaeYoung (LGE).
Thomas(Nokia) suggest noting this PCR
LaeYoung (LGE) provides comment to Xiaoyan (CATT) .
==== 9.X, 10.X Final Deadline ====
Noted
9.23 - - - Update solution - - Docs:=6 -
9.23 S2-2205770 P-CR Approval 23.700-81: KI#6, Update Solution#49: Propose to add new Analytics parameters Futurewei Rel-18 r01 agreed. Revised to S2-2207157. Huazhang (vivo) provides some comments
Abbas (Futurewei) provides response to Vivo questions
Jihoon (ETRI) provides comment again, asking to ignore the previous email because wrong information in the 'Comment for notes' was filled in.
Belen (Ericsson) provides comments
Abbas (Futurewei) provides response to ETRI comments
Abbas (Futurewei) provides response to Ericsson comments
Thomas(Nokia) asks a follow-up question
Abbas Kiani (Futurewei) provides r01.
Abbas (Futurewei) provides response to Nokia (Thomas) comments
Wang Yuan (Huawei) provides comments
Abbas (Futurewei) provides response to Huawei (Yuan) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207157 P-CR Approval 23.700-81: KI#6, Update Solution#49: Propose to add new Analytics parameters Futurewei Rel-18 Revision of S2-2205770r01. Approved Approved
9.23 S2-2206420 P-CR Approval 23.700-81: KI#6, Sol#48 update to solve the Ens Vivo Rel-18 r02 agreed. Revised to S2-2207158. Belen (Ericsson) objects to this contribution, it is not in the scope of the KI
Huazhang (vivo) can't understand the objection, because this is the solution update and to solve the ENs in solution. And ask for details of question.
Huazhang (vivo) provides r01 to remove the data collection from UE
Thomas (Nokia) comments
Jihoon (ETRI) provides comments.
Yang (OPPO) provides a question
Huazhang (vivo) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207158 P-CR Approval 23.700-81: KI#6, Sol#48 update to solve the Ens Vivo Rel-18 Revision of S2-2206420r02. Approved Approved
9.23 S2-2206521 P-CR Approval 23.700-81: KI#6, Sol#16: Update to remove EN China Telecom Rel-18 r01 agreed. Revised to S2-2207159. Jiahui (China Telecom) replies to Ericsson.
Belen (Ericsson) asks questions on the solution.
Juan Zhang (Qualcomm) provides comments.
Belen (Ericsson) objects to this contribution
Thomas (Nokia) shares concerns about making NWDAF applicable for EPC.
Suggest revising the CR to simply remove related EN
Jiahui (China Telecom) replys to Ericsson and Qualcomm, and provides r01 and asks Ericsson to kindly withdraw the objection.
Jiahui (China Telecom) replys to Nokia.
Thomas(Nokia) is fine with r01.
Belen (Ericsson) can accept r01
==== 9.X, 10.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207159 P-CR Approval 23.700-81: KI#6, Sol#16: Update to remove EN China Telecom Rel-18 Revision of S2-2206521r01. Approved Approved
9.23 - - - Evaluation & Conclusion - - Docs:=2 -
9.23 S2-2205550 P-CR Approval 23.700-81: KI#6: Evaluation and Conclusions for NWDAF-assisted URSPs Ericsson Rel-18 r06 agreed. Revised to S2-2207160. Huazhang (vivo) provides comments
Belen (Ericsson) replies
Huazhang (vivo) replies
Huazhang (vivo) replies to Belen
Huazhang (vivo) provides r02
Thomas(Nokia) provides r01
Jihoon (ETRI) asks questions.
Huazhang (vivo) reply to Jihoon(ETRI)
Yang (OPPO) comments that it is not sure whether it can have a tight relation between the configured URSP parameters and Application user experience since the application service is an E2E procedure.
Belen (Ericsson) provides r03
Jihoon (ETRI) asks clarification.
Juan Zhang (Qualcomm) supports r03.
Dimitris (Lenovo) supports r03
Huazhang (vivo) provides r04 based on r03
Belen (Ericsson) provides r05, cannot accept r04
Huazhang (vivo) provides r06 based on r05
==== 9.X, 10.X Revisions Deadline ====
Abbas Kiani (Futurewei) asks for clarification.
Belen (Ericsson) replies to Futurewei
Jihoon (ETRI) is OK with r05 and r06 and would like to co-sign.
Huazhang (vivo) agree with r06, object any other versions
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207160 P-CR Approval 23.700-81: KI#6: Evaluation and Conclusions for NWDAF-assisted URSPs Ericsson Rel-18 Revision of S2-2205550r06. Approved Approved
9.23 - - - Key Issue #7: Enhancements on QoS Sustainability analytics - - Docs:=0 -
9.23 - - - Update solution - - Docs:=6 -
9.23 S2-2206058 P-CR Approval 23.700-81: KI#7, Sol#50: Update to clarify solution procedure description Tencent, Tencent Cloud Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206145 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#7, Sol#19 Update to remove FFS China Mobile, Huawei Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206566 P-CR Approval 23.700-81: Enhancements on Solution #50 for QoS Sustainability Analytics Huawei, HiSilicon Rel-18 Approved Juan Zhang (Qualcomm) provides comments.
Susan (Huawei) replies to Juan Zhang (Qualcomm).
Juan Zhang (Qualcomm) replies to Susan (Huawei)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206567 P-CR Approval 23.700-81: Enhancements on Solution #19 for QoS Sustainability Analytics Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207161. Susan (Huawei) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207161 P-CR Approval 23.700-81: Enhancements on Solution #19 for QoS Sustainability Analytics Huawei, HiSilicon Rel-18 Revision of S2-2206567r01. Approved Approved
9.23 S2-2206709 P-CR Approval 23.700-81: KI#7, Sol#18: Update to clarify solution procedure description Tencent, Tencent Cloud Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 - - - Evaluation & Conclusion - - Docs:=3 -
9.23 S2-2205945 P-CR Approval 23.700-81: KI #7: Evaluation of solutions Orange Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206135 P-CR Approval 23.700-81: KI#7, Evaluation and Conclusion Huawei, HiSilicon Rel-18 Revised to S2-2207162. Baseline for interim conclusion xiaobo(vivo) provides comments
Antoine (Orange) provides r01.
==== 9.X, 10.X Revisions Deadline ====
Wang Yuan (Huawei) is OK with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207162 P-CR Approval 23.700-81: KI#7, Evaluation and Conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206135. Approved Approved
9.23 - - - Key Issue #8: Supporting Federated Learning in 5GC - - Docs:=0 -
9.23 - - - New solution - - Docs:=3 -
9.23 S2-2206568 P-CR Approval 23.700-81: KI #8, New Sol: Model performance guarantee during FL Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2207163. Zhang (Ericsson) ask for clarification
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207163 P-CR Approval 23.700-81: KI #8, New Sol: Model performance guarantee during FL Huawei, HiSilicon Rel-18 Revision of S2-2206568r01. Approved Approved
9.23 S2-2206677 P-CR Approval 23.700-81: KI#8 New Sol: Support for federated reinforcement learning Nokia, Nokia Shanghai Bell Rel-18 Noted Xiaoyan (CATT) asks for clarifications.
Fabio (Nokia) replies to comments and provides r01.
Zhang (Ericsson) object the paper
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.23 - - - Update solution - - Docs:=5 -
9.23 S2-2205548 P-CR Approval 23.700-81: KI#8, Sol#51: Update: Selection, Monitoring, and Maintenance of NWDAF(s) for Federated Learning in 5GC Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206419 P-CR Approval 23.700-81: KI#8, Sol#52, update solution Vivo, Intel, Inspur Rel-18 r01 agreed. Revised to S2-2207164. Zhang (Ericsson) provides comments
xiaobo(vivo): vivo replies to Zhang(Ericsson) and provide r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207164 P-CR Approval 23.700-81: KI#8, Sol#52, update solution Vivo, Intel, Inspur Rel-18 Revision of S2-2206419r01. Approved Approved
9.23 S2-2206538 P-CR Approval 23.700-81: KI#8, Sol#53: Sol Update: Horizontal Federated Learning with Multiple NWDAF China Telecom, vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206578 P-CR Approval 23.700-81: KI#8, Sol #22: Update to resolve ENs Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.23 - - - Evaluation & Conclusion - - Docs:=2 -
9.23 S2-2206114 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#8 evaluation and conclusion China Mobile Rel-18 r14 agreed. Revised to S2-2207165. Baseline to capture principle Dimitris (Lenovo) provides r01 and comments
Vivian (vivo) provides r02 and comments
Aihua(CMCC) provides r04
Zhang (Ericsson) provides r03
Juan Zhang (Qualcomm) provides r05.
Malla (NTT DOCOMO) provides r06.
Zhang (Ericsson) provide comments
Juan Zhang (Qualcomm) replies to Zhang (Ericsson)
Vivian (vivo) replies to Zhang (Ericsson)'s question about Time period of Interest.
Dimitris (Lenovo) responds to Juan and Malla
Malla (NTT DOCOMO) replies to Dimitris (Lenovo) and Juan.
Fabio (Nokia) replies to Malla, Dimitris and Juan and shows concerns on the discovery of FL entities
Wang Yuan (Huawei) provides r07 and co-signs this paper.
Soohwan (ETRI) objects to r07.
Vivian(vivo) provides some comments on Fabio (Nokia)'s concerns on the discovery of FL entities
Zhang (Ericsson) provides r08 and comments
Juan Zhang (Qualcomm) replies to Dimitris (Lenovo).
Dimitris (Lenovo) responds to Malla
Juan Zhang (Qualcomm) replies to Fabio (Nokia)
Wang Yuan (Huawei) replies to Soohwan (ETRI) and Zhang (Ericsson) to persist on the Principle 8 in r07 and resume it in r09.
Malla (NTT DOCOMO) replies to Juan Zhang (Qualcomm) and asks clarification on r09
Fabio (Nokia) replies to Vivian (Vivo)
Zhang (Ericsson) response to Yuan (Huawei) and have concerns for r09
Fabio (Nokia) replies to Juan Zhang (Qualcomm) and expresses concerns on most of the principles documented in r09
Megha(Intel) asks for clarification on Principle 6 in r09.
Wang Yuan (Huawei) replies to Soohwan (ETRI) and Zhang (Ericsson) and provides r10.
Soohwan (ETRI) responses to Yuan and expresses concerns on r09.
Soohwan (ETRI) provides r11..
Fabio (Nokia) replies to comments
Vivian(vivo) replies to Fabio (Nokia)'s comments and provides r12, meanwhile, adds vivo as co-signer.
Aihua(CMCC) is fine with r12.
Dimitris (Lenovo) has a question on how ML model filter information is used for FL server discovery
Vivian(vivo) replies to Dimitris (Lenovo)'s question.
Zhang (Ericsson) provides r13
Vivian (vivo) replies to Zhang (Ericsson) and suggests to keep principle 7.
Megha (Intel) provides r14
Zhang (Ericsson) response to Vivian (Vivo)
==== 9.X, 10.X Revisions Deadline ====
Dimitris (Lenovo) is OK with r14
Zhang (Ericsson) is OK with r14
Aihua(CMCC) is fine with r14
Wang Yuan (Huawei) is also fine with r14.
Vivian(vivo) is also fine with r14.
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207165 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#8 evaluation and conclusion China Mobile Rel-18 Revision of S2-2206114r14. Approved Approved
9.23 - - - Key Issue #9: Enhancement of NWDAF with finer granularity of location information - - Docs:=0 -
9.23 - - - New solution - - Docs:=4 -
9.23 S2-2205948 P-CR Approval 23.700-81: KI#9, New Sol: Improved control of location granularity Orange Rel-18 r01 agreed. Revised to S2-2207166. Thomas (Nokia) asks whether solution fits to key issue
Hank (vivo) asks questions.
Antoine (Orange) replies to Thomas and Hank and provides r01.
Thomas(Nokia) provides r02.
Hank (vivo) provides comments.
Antoine (Orange) replies.
Zhang (Ericsson) ask for clarification if the proposal addressed in S2-2205551
Antoine (Orange) replies that this proposal is not addressed in S2-2205551r02.
Thomas (Nokia) replies to Antoine
Antoine (Orange) replies to Thomas.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207166 P-CR Approval 23.700-81: KI#9, New Sol: Improved control of location granularity Orange Rel-18 Revision of S2-2205948r01. Approved Approved
9.23 S2-2206409 P-CR Approval 23.700-81: KI#9, New Sol, Traffic flow statistics use case with finer granularity location information Vivo, China Telecom Rel-18 Revision of (Unhandled) S2-2204016 from S2#151E. r01 agreed. Revised to S2-2207167. Wang Yuan (Huawei) provides comments.
Hank (vivo) responses to Wang Yuan (Huawei).
Hank(vivo) replies to Yuan(Huawei) and Thomas(Nokia).
Thomas(Nokia) provides comments.
Hank (vivo) provides r01 to address comments from Thomas(Nokia).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207167 P-CR Approval 23.700-81: KI#9, New Sol, Traffic flow statistics use case with finer granularity location information Vivo, China Telecom Rel-18 Revision of S2-2206409r01. Approved Approved
9.23 - - - Update solution - - Docs:=4 -
9.23 S2-2205871 P-CR Approval 23.700-81: KI#9: Sol#27 updates and ENs removal Samsung Rel-18 r03 agreed. Revised to S2-2207168. Wang Yuan (Huawei) provides comments.
David (Samsung) replies to Huawei.
Thomas (Nokia) provides r01
Comments that more discussion for new time-to-collision use case is required in addition.
David (Samsung) replies to Nokia, provides r03 (please disregard r02).
Thomas(Nokia) can accept r03
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207168 P-CR Approval 23.700-81: KI#9: Sol#27 updates and ENs removal Samsung Rel-18 Revision of S2-2205871r03. Approved Approved
9.23 S2-2206383 P-CR Approval 23.700-81: Add NOTE for Solution#54: Finer granular location information based on LCS input data China Telecom Rel-18 r01 agreed. Revised to S2-2207169. Hank (vivo) provides an opinion on the privacy information concealed and provides r01.
Thomas (Nokia) raises concerns
Yifan (China Telecom) is OK with r01.
Malla (NTT DOCOMO) is also fine with r01.
Thomas(Nokia) can accept r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207169 P-CR Approval 23.700-81: Add NOTE for Solution#54: Finer granular location information based on LCS input data China Telecom Rel-18 Revision of S2-2206383r01. Approved Approved
9.23 - - - Key Issue #10: how NWDAF requests analytics from MDAS/MDAF. - - Docs:=0 -
9.23 - - - New solution - - Docs:=5 -
9.23 S2-2205566 P-CR Approval 23.700-81: KI#10: New Solution: Use of MDAS analytics for improving AnLF/MTLF analytics accuracy and data collection. Lenovo Rel-18 Approved Fabio (Nokia) provides comments.
Dimitris (Lenovo) responds
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206132 P-CR Approval 23.700-81: KI#10, New Sol: how NWDAF requests analytics from MDA Management Function [Resubmission] Huawei, HiSilicon Rel-18 Approved Belen (Ericsson) supports this contribution
Fabio (Nokia) provides comments.
Wang Yuan (Huawei) replies to Fabio (Nokia).
Fabio (Nokia) replies to comments
Wang Yuan (Huawei) replies to Fabio (Nokia) and ask whether the r00 is acceptable.
Fabio (Nokia) is OK with r00.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.23 S2-2206133 LS OUT Approval [DRAFT] LS on how NWDAF requests analytics from MDA Management Function Huawei, HiSilicon Rel-18 Noted Dimitris (Lenovo) does not see the need to send an LS to SA5
Fabio (Nokia) also does not see the need to send an LS to SA5
==== 9.X, 10.X Revisions Deadline ====
Wang Yuan (Huawei) replies to Dimitris (Lenovo) and Fabio (Nokia), and OK to postpone this paper to the next meeting.
==== 9.X, 10.X Final Deadline ====
Noted
9.23 S2-2206154 P-CR Approval 23.700-81: KI#10: New solution for supporting NWDAF interaction with MDAF Lenovo Rel-18 r01 agreed. Revised to S2-2207170. Fabio (Nokia) provides comments.
Belen (Ericsson) provides comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.23 S2-2207170 P-CR Approval 23.700-81: KI#10: New solution for supporting NWDAF interaction with MDAF Lenovo Rel-18 Revision of S2-2206154r01. Approved Approved
9.23 - - - Documents exceeding TU Budget - - Docs:=28 -
9.23 S2-2206411 DISCUSSION Approval Discussion on evaluation and interim conclusion for eNA3 KI#1 vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206413 DISCUSSION Approval Discussion on evaluation and interim conclusion for eNA3 KI#3 vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206415 DISCUSSION Approval Discussion on evaluation and interim conclusion for eNA3 KI#8 vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205540 P-CR Approval 23.700-81: KI#1, Sol#1: Update to remove Ens Ericsson Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205574 P-CR Approval 23.700-81: KI#1: Evaluation and interim conclusions Lenovo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205720 P-CR Approval 23.700-81: Evaluation & Conclusion of KI#1 Huawei, HiSilicon Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205904 P-CR Approval 23.700-81: KI #1, Eval, Conclusion: Partial Evaluation and Conclusion for Key Issue #1 InterDigital Inc. Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206117 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#1, Evaluation and Conclusion China Mobile Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206444 P-CR Approval 23.700-81: KI#1: Evaluation of solutions CATT Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206445 P-CR Approval 23.700-81: KI#1 Interim conclusions CATT Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205543 P-CR Approval 23.700-81: KI#2, Evaluation and conclusions Ericsson Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205536 P-CR Approval 23.700-81: KI#3, Sol#10: Resolving remaining ENs. Ericsson Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206418 P-CR Approval 23.700-81: KI#3, Sol#39, update to remove En Vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206120 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#4, Evaluation and Conclusion China Mobile Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206828 P-CR Approval 23.700-81: KI#5 Overall Evaluation Intel, Vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206421 P-CR Approval 23.700-81: KI#6, evaluation and conclusion Vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205889 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#7, Sol#19 Update to remove FFS China Mobile, Huawei Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206134 P-CR Approval 23.700-81: KI#7, Sol#19: Update to remove FFS Huawei, HiSilicon Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205546 P-CR Approval 23.700-81: KI#8, Evaluation and Conclusion Ericsson Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205575 P-CR Approval 23.700-81: KI#8: Evaluation and interim conclusions Lenovo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205678 P-CR Approval 23.700-81: KI#8: Evaluation and Interim Conclusion for Federated Learning Qualcomm Incorporated Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206416 P-CR Approval 23.700-81: KI#8, Evaluation and interim conclusion Vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206410 P-CR Approval 23.700-81: KI#9, Sol #57, Update to resolve the EN related to the area defined with the finer granularity Vivo Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206140 P-CR Approval 23.700-81: FS_eNA_Ph3 KI#10, Evaluation and Conclusion China Mobile Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2205547 P-CR Approval 23.700-81: KI#8, Sol#24: Update: Horizontal Federated Learning among Multiple NWDAFs Ericsson Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206678 P-CR Approval 23.700-81: KI #1 New solution: Trustworthiness information of NWDAF analytics Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not handled Wang Yuan (Huawei) provides comments.
Fabio (Nokia) replies to Yuan (Huawei).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206437 P-CR Approval 23.700-81: KI #3 evaluation and interim conclusions Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.23 S2-2206676 P-CR Approval 23.700-81: KI#8 New Sol: P2P federated learning Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 - - - Study on satellite access Phase 2 (FS_5GSAT_Ph2) - - Docs:=57 -
9.24 - - - General - - Docs:=5 -
9.24 S2-2205512 P-CR Approval 23.700-28: KI#1 and KI#2: proposed methodology for global evaluation THALES Rel-18 Merged into S2-2207186 Stefan (Ericsson) asks whether this contribution can be considered merged into 6935
Jean Yves (Thales) to precise that S2-2205512 is now merged into S2-2206935
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.24 S2-2205768 P-CR Approval 23.700-28: Description of rel.17 solution for discontinuous coverage Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2207171. Stefan (Ericsson) provides r01
Saso (Intel) provides r02
==== 9.X, 10.X Revisions Deadline ====
Jean Yves (Thales) is ok with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207171 P-CR Approval 23.700-28: Description of rel.17 solution for discontinuous coverage Qualcomm Incorporated Rel-18 Revision of S2-2205768r02. Approved Approved
9.24 S2-2206495 DISCUSSION Information Discussion paper on ephemeris information provision via N2 Vivo Rel-18 Noted Steve (Huawei) I assume we note this as it was a discussion for Information.
Jean-Yves (Thales) proposes also to note the discussion paper.
==== 9.X, 10.X Revisions Deadline ====
Amy (vivo) agree wo note this.
==== 9.X, 10.X Final Deadline ====
Noted
9.24 S2-2206496 LS OUT Approval [DRAFT] LS on ephemeris information provision via N2 in 5GSAT_Ph2 vivo Rel-18 Postponed Stephen (Qualcomm) asks whether this LS is needed now
Amy (vivo) replies to Stephen (Qualcomm)
Stefan (Ericsson) comments and provides r01
Jean Yves (Thales) comments
Hannu (Nokia) comments on NTN control function in RAN specs and supports doing the architecture design in SA2 first.
==== 9.X, 10.X Revisions Deadline ====
DongYeon (Samsung) comments.
Stephen (Qualcomm) cannot agree the r00 or r01 at the present time
==== 9.X, 10.X Final Deadline ====
Amy (vivo) agrees to NOTE this LS.
Postponed
9.24 - - - Solutions updates (and self-evaluation) - - Docs:=28 -
9.24 S2-2206467 P-CR Approval 23.700-28: KI#2, Sol#1: Update solutioin to include S1 release procedure triggering power saving parameters update Xiaomi Rel-18 r02 agreed. Revised to S2-2207172. Yuxin (Xiaomi) provides r01 based on Rapporteur proposal
Lalith(Samsung) comments on r01
Yuxin(Xiaomi) replies to Lalith(Samsung) and provides r02
Steve (Huawei) comments
==== 9.X, 10.X Revisions Deadline ====
Jean Yves (Thales) is ok with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207172 P-CR Approval 23.700-28: KI#2, Sol#1: Update solutioin to include S1 release procedure triggering power saving parameters update Xiaomi Rel-18 Revision of S2-2206467r02. Approved Approved
9.24 S2-2205513 P-CR Approval 23.700-28: KI #2, Sol #2: Update to complete the solution description. THALES Rel-18 r03 agreed. Revised to S2-2207173. Yingying(CATT) provides comments.
Jean Yves (Thales) answers to Yingying .
Yingying(CATT) replies to Jean Yves (Thales).
Stefan (Ericsson) provides comments
Stephen (Qualcomm) provides some comments
Jean Yves (Thales) answers questions and provides r01
Lalith (Samsung) seeks clarification.
Steve (Huawei) in the interface / external server access from the MME/AMF
Jean Yves (Thales) responds to Steve and Lalith
Yuxin (Xiaomi) comments
Jean Yves (Thales) answers to Yuxin and provides r02
Lalith(Samsung) comments
Steve (Huawei) is there now a privacy problem?
Jean Yves (Thales) answers Steve
Steve (Huawei) additional thoughts on privacy and signalling
Jean Yves (Thales) answers Steve and ask questions for possible SCEF API enhancement
Steve (Huawei) comments on SCEF
Jean Yves (Thales) asks questions to Yuxin
Yuxin (Xiaomi) replies to Jean Yves (Thales)
Jean Yves (Thales) answers to Yuxin and Steve, provides r03 adding also supporting company
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) is ok with r03, but needs further updates before can be considered for conclusions
Jean Yves (Thales) answers to Steve
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207173 P-CR Approval 23.700-28: KI #2, Sol #2: Update to complete the solution description. THALES Rel-18 Revision of S2-2205513r03. Approved Approved
9.24 S2-2206267 P-CR Approval 23.700-28: KI1 Sol4 Update: UE location report clarifications and add EPS support Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207174. Amy (vivo) provides r01 based on Rapporteur proposal.
Stefan (Ericsson) provides questions
Steve (Huawei) comments
Yuxin (Xiaomi) comments
Amy (vivo) provides r02 based on the discussion of Steve and Stefan.
Stefan (Ericsson) comments
Amy (vivo) comments
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) is ok with r02.
Yuxin (Xiaomi) is ok with r02.
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207174 P-CR Approval 23.700-28: KI1 Sol4 Update: UE location report clarifications and add EPS support Huawei, HiSilicon Rel-18 Revision of S2-2206267r02. Approved Approved
9.24 S2-2206493 P-CR Approval 23.700-28: KI#2 Solution 5 evaluations Vivo Rel-18 r05 agreed. Revised to S2-2207175. Amy (vivo) provides r01 to enhance solution#5 to have the 4G compatibility.
Yuxin (Xiaomi) comments
Lalith(Samsung) provides r02
Stefan (Ericsson) provides questions
Lalith (Samsung) answers the question.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207175 P-CR Approval 23.700-28: KI#2 Solution 5 evaluations Vivo Rel-18 Revision of S2-2206493r05. Approved Approved
9.24 S2-2206494 P-CR Approval 23.700-28: KI#1 and KI#2 Solution 7 updates and evaluations Vivo Rel-18 r05 agreed. Revised to S2-2207176. Atsushi (NTT DOCOMO) asks a question.
Amy (vivo) provides r01 to merge S2-2206288 content into S2-2206494 as rapporteur proposed.
Lalith (Samsung) comments on r01
Atsushi (NTT DOCOMO) comments.
Lailth(Samsung) replies
Steve (Huawei) provides some initial comments
Yuxin (Xiaomi) comments
Atsushi (NTT DOCOMO) provides r02.
Amy (vivo) provides r03 and replies to Yuxin (Xiaomi), Atsushi (NTT DOCOMO) and Steve (Huawei).
Stefan (Ericsson) provides r04
Amy (vivo) asks clarifications
Stefan (Ericsson) provides r05
Amy (vivo) thanks Stefan (Ericsson) and is totally fine with r05
==== 9.X, 10.X Revisions Deadline ====
Jean Yves (Thales) is ok with r05
Steve (Huawei) is ok with r05
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207176 P-CR Approval 23.700-28: KI#1 and KI#2 Solution 7 updates and evaluations Vivo Rel-18 Revision of S2-2206494r05. Approved Approved
9.24 S2-2206269 P-CR Approval 23.700-28: Solution 8 Update: Solution Evaluation Huawei, HiSilicon Rel-18 Approved Yuxin(Xiaomi) provides comments.
Steve (Huawei) replies on MT service
Stefan (Ericsson) provides comments
Steve (Huawei) comments on signalling overhead
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206270 P-CR Approval 23.700-28: Solution 9 Update: Solution Evaluation Huawei, HiSilicon Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206271 P-CR Approval 23.700-28: Solution 10 Update: EN Clarifications and Solution Evaluation Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2207177. Stefan (Ericsson) provides comments
Steve (Huawei) replies
Stefan (Ericsson) replies to Steve
Steve (Huawei) good question on is it the same.
Stefan (Ericsson) provides r01
Steve (Huawei) provides r02
==== 9.X, 10.X Revisions Deadline ====
Jean Yves (Thales) is ok with r02
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207177 P-CR Approval 23.700-28: Solution 10 Update: EN Clarifications and Solution Evaluation Huawei, HiSilicon Rel-18 Revision of S2-2206271r02. Approved Approved
9.24 S2-2206272 P-CR Approval 23.700-28: Solution 11 Update: EN Clarifications and Solution Evaluation Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2207178. Jaewoo (LGE) provides r01 based on Rapporteur proposal.
Stefan (Ericsson) provides questions
Steve (Huawei) replies to Stefan
Steve (Huawei) thanks for the merge, provides r02
Yuxin(Xiaomi) comments
Jaewoo (LGE) is fine with r02, provides r03 with editorial changes.
Steve (Huawei) provides r04
Stephen (Qualcomm) comments that this evaluation is not accurate
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) comments that while the evaluation is not fully accurate, we are okay to agree the r04
Jean Yves (Thales) is ok for r04
Jaewoo (LGE) is ok with r04 and would like to co-sign..
Steve (Huawei) comments
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207178 P-CR Approval 23.700-28: Solution 11 Update: EN Clarifications and Solution Evaluation Huawei, HiSilicon Rel-18 Revision of S2-2206272r04. Approved Approved
9.24 S2-2206464 P-CR Approval 23.700-28: KI#1, Sol #12: Update to resolution of EN Xiaomi Rel-18 r06 agreed. Revised to S2-2207179, merging and S2-2206929 Yingying(CATT) provides comments.
Yuxin (Xiaomi) replies to Yingying(CATT) and provides r01.
Jean Yves (Thales) comments to use r01
Stefan (Ericsson) provides r02
DongYeon (Samsung) comments.
Yuxin (Xiaomi) provides r03.
Yuxin (Xiaomi) provides r04 to merge S2-2206929.
Stefan (Ericsson) provides r05
DongYeon (Samsung) is OK with r04.
DongYeon (Samsung) provides r06.
==== 9.X, 10.X Revisions Deadline ====
Yuxin (Xiaomi) is OK with r06.
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207179 P-CR Approval 23.700-28: KI#1, Sol #12: Update to resolution of EN Xiaomi Rel-18 Revision of S2-2206464r06, merging and S2-2206929. Approved Approved
9.24 S2-2206929 P-CR Approval 23.700-28: KI#1, Solution #12 Update: Minimize discontinuous coverage by inter-RAT handover processing Samsung Rel-18 Merged into S2-2207179 Stefan (Ericsson) suggests that 6929 is merged into 6464
Yuxin (Xiaomi) tries to merge 6929 into 6464
==== 9.X, 10.X Revisions Deadline ====
DongYeon (Samsung) agrees that 6929 is merged to 6464.
==== 9.X, 10.X Final Deadline ====
Merged
9.24 S2-2206803 P-CR Approval 23.700-28: KI #1, Sol#13: Resolving EN and Solution Evaluation Samsung Rel-18 Approved Stefan (Ericsson) provides comments
Lalith(Samsung) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206466 P-CR Approval 23.700-28: KI#2, Sol#13: Update solution#13 to propose UE determines its action during discontinuous coverage Xiaomi Rel-18 r02 agreed. Revised to S2-2207180. Lalith(Samsung) provides r01
Jean Yves (Thales) WARNING, comments on rapporteur sorting final documents.
Yuxin(Xiaomi) replies and provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207180 P-CR Approval 23.700-28: KI#2, Sol#13: Update solution#13 to propose UE determines its action during discontinuous coverage Xiaomi Rel-18 Revision of S2-2206466r02. Approved Approved
9.24 S2-2205558 P-CR Approval 23.700-28: KI #1, Sol #13 Update to resolve editor's note Spreadtrum Communications Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206776 P-CR Approval 23.700-28: Sol#13 Update for Applicability and Power Saving in Discontinuous Coverage Google Inc. Rel-18 Approved Yingying(CATT) provides comments.
Ellen (Google) feedback for comments from Yingying (CATT)
Lufeng(Spreadtrum) ask a question for clarification.
Ellen (Google) answers questions from Lufeng (Spreadtrum)
Yuxin (Xiaomi) comments
Ellen (Google) replies question from Yuxin (Xiaomi)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206804 P-CR Approval 23.700-28: KI #1, Sol#14: Resolving EN and Solution Evaluation Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206932 P-CR Approval 23.700-28: Revision of Solution #15 for KI#1, KI#2: Provision of Coverage Data to a UE Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2207181. Steve (Huawei) provides some initial comments
Stephen (Qualcomm) replies to Steve (Huawei)
DongYeon (Samsung) comments.
Steve (Huawei) comments
Stephen (Qualcomm) provides an r01
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) is ok with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207181 P-CR Approval 23.700-28: Revision of Solution #15 for KI#1, KI#2: Provision of Coverage Data to a UE Qualcomm Incorporated Rel-18 Revision of S2-2206932r01. Approved Approved
9.24 S2-2206933 P-CR Approval 23.700-28: Revision of Solution #16 for KI#1, KI#2: Support of UE Triggered Generalized Unavailability Period Qualcomm Incorporated Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 - - - New solutions - - Docs:=11 -
9.24 S2-2205511 P-CR Approval 23.700-28: KI #1, KI #2, New solution enabler with coverage information over NAS. THALES Rel-18 r01 agreed. Revised to S2-2207182. Costas (Lenovo) provides comments.
Jean Yves (Thales) answers Costas.
Steve (Huawei) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207182 P-CR Approval 23.700-28: KI #1, KI #2, New solution enabler with coverage information over NAS. THALES Rel-18 Revision of S2-2205511r01. Approved Approved
9.24 S2-2205982 P-CR Approval 23.700-28: New Solution: Handling of the UE attempt to Connected mode Rakuten Mobile Rel-18 r01 agreed. Revised to S2-2207183. Yingying(CATT) provides comments.
Aoken(Rakuten Mobile) answers to the comment by Yingying(CATT).
Yingying(CATT) replies to Aoken(Rakuten Mobile).
Jean Yves(Thales) ask question to Aoken.
Hannu (Nokia) comments that such randomization of RRC Connection Request is currently not specified and the rules for randomization would have specification impact.
Aoken (Rakuten Mobile) answers to the comment by Hannu and provides rev1
Aoken(Rakuten Mobile) answers to the question by Jean Yves(Thales)
Stefan (Ericsson) provides questions
Aoken (Rakuten Mobile) answers to the questions
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207183 P-CR Approval 23.700-28: New Solution: Handling of the UE attempt to Connected mode Rakuten Mobile Rel-18 Revision of S2-2205982r01. Approved Approved
9.24 S2-2206291 P-CR Approval 23.700-28: KI#1, New Sol: Response to Nnef_ParameterProvision request containing Maximum Latency NTT DOCOMO Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206701 P-CR Approval 23.700-28: KI#1, KI#2, New Sol: AF-provided coverage time information Ericsson Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 S2-2206703 P-CR Decision 23.700-17: Solution for paging enhancement under discontinuous coverage based on definition and management of UE-specific Dynamic Tracking Areas Sateliot, GateHouse Rel-18 r01 agreed. Revised to S2-2207184. Yuxin (Xiaomi) comments
Steve (Huawei) comments
Stephen (Qualcomm) comments that this solution could be out of scope
Jean Yves (Thales) comments
Ramon (Sateliot) replies to comments and provides r01.
Stefan (Ericsson) provides comments
Ramon (Sateliot) answers Ericsson comments
Hannu (Nokia) supports Steve and Stephen and suggests that if any revisions are made, RAN dependency should be identified in EN.
Thierry (Novamint) comments and supports r01
==== 9.X, 10.X Revisions Deadline ====
Ramon (Sateliot) asnwers to Nokia and ask for support in writing the EN about potential RAN dependency
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207184 P-CR Decision 23.700-17: Solution for paging enhancement under discontinuous coverage based on definition and management of UE-specific Dynamic Tracking Areas Sateliot, GateHouse Rel-18 Revision of S2-2206703r01. Approved Approved
9.24 S2-2206779 P-CR Approval 23.700-28: New Solution for KI#2: Network assisted Power Saving Mechanisms Google Inc. Rel-18 r03 agreed. Revised to S2-2207185. Amy (vivo) provides comments.
Ellen (Google) provides r01 to address Vivo's comment
Yuxin (Xiaomi) comments
Ellen (Google) answers Yuxin (Xiaomi) questions
Amy (vivo) replies to Ellen (Google) and provides comments
Jean Yves (Thales) comments
DongYeon (Samsung) comments.
Stefan (Ericsson) provides questions
Steve (Huawei) comments
Ellen (Google) provides r02 and replies comments from Ericsson, Huawei, Samsung, Vivo
Stephen (Qualcomm) provides comments
Yingying(CATT) provides comments.
Steve (Huawei) comments on overall impact / evaluation
Ellen (Google) provides r03 and replies questions from CATT, Qualcomm, Lenovo, Huawei
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207185 P-CR Approval 23.700-28: New Solution for KI#2: Network assisted Power Saving Mechanisms Google Inc. Rel-18 Revision of S2-2206779r03. Approved Approved
9.24 S2-2206924 P-CR Approval 23.700-28: KI#1, KI#2, New solution: Coverage data transfer in 5GS and EPS Samsung Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.24 - - - Global evaluation & conclusions - - Docs:=3 -
9.24 S2-2206273 P-CR Approval 23.700-28: KI#1 and KI#2: Evaluation and interim conclusions Huawei, HiSilicon Rel-18 Merged into S2-2207186 Hannu (Nokia) asks about the handling of conclusion papers S2-2206273 and S2-2206935 in this meeting?
Jean Yves (Thales) answers Hannu's question and proposes some guidance regarding overall evaluation and conclusions in this meeting
Stefan (Ericsson) asks about evalution/conclusion handling
Jean Yves (Thales) answers Stefan
Lalith(Samsung) provides r01
Steve (Huawei) provides r02
Stephen (Qualcomm) does not see this as a useful evaluation to enable conclusions based on the KIs
Jean Yves (Thales) propose to move forward on overall evaluation using 6935 thread merging 5512
Steve (Huawei) replies to Stephen and Jean Yves
Jean Yves (Thales) comments
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) assumes this evaluation has been merged into S2-2206935 but cannot accept any version of S2-2206273 if it remains unmerged
Steve (Huawei) is ok to merge with 6935
==== 9.X, 10.X Final Deadline ====
Merged
9.24 S2-2206935 P-CR Approval 23.700-28: KI#1, KI#2: Evaluation and Conclusions Qualcomm Incorporated Rel-18 r08 agreed. Revised to S2-2207186, merging S2-2205512 and S2-2206273 Jean Yves(Thales) merges S2-2205512 into S2-2206935 and proposes to use S2-2206935 as basis to build single global evaluation during this meeting
Amy (vivo) provides comments on 6935r01
Jean Yves (Thales) answers Amy and provides r02, with guidelines
Steve (Huawei) comments
Lalith(Samsung) provides r03
Jean-Yves (Thales) answers to Steve
Steve (Huawei) replies on structure
Steve (Huawei) provides r04
Stephen (Qualcomm) provides an r05
Jean Yves (Thales) comments
DongYeon (Samsung) asks which paper should we work for evaluation 6935 or 6235?
Jean Yves (Thales) confirms that for FS_5GSAT_Ph2 single evaluation paper is now S2-2206935
DongYeon (Samsung) corrects last comment - was asking 6935 and 6273.
Stefan (Ericsson) provides comments
Jean Yves (Thales) answers Stefan
Yuxin (Xiaomi) comments
DongYeon (Samsung) provides r06.
Amy (vivo) provides r07.
Jean Yves (Thales) answers Yuxin.
Steve (Huawei) provides r08, comments on targeting only some parts
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) can agree r08 or (if needed) r05, r06 or r07
DongYeon (Samsung) is OK with r08, r07, and r06.
Yuxin (Xiaomi) is OK with r08.
Amy (vivo) is ok with r08, r07, cheers
Steve (Huawei) is ok with r08.
Jean Yves (Thales) is ok with r08.
==== 9.X, 10.X Final Deadline ====
Revised
9.24 S2-2207186 P-CR Approval 23.700-28: KI#1, KI#2: Evaluation and Conclusions Qualcomm Incorporated Rel-18 Revision of S2-2206935r08, merging S2-2205512 and S2-2206273. Approved Approved
9.24 - - - Documents exceeding TU Budget - - Docs:=10 -
9.24 S2-2206463 P-CR Approval 23.700-28: KI#1, Sol #6: Remove EN in solution #6 Xiaomi Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206465 P-CR Approval 23.700-28: KI#1, Sol #12: Add solution evaluation Xiaomi Rel-18 Not Handled Yuxin(Xiaomi) merges this tdoc into S2-2206464 and proposes to discuss in other thread
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206268 P-CR Approval 23.700-28: Solution 1 Update: Solution Evaluation Huawei, HiSilicon Rel-18 Not Handled Yuxin(Xiaomi) merges this tdoc into S2-2206467 based on Rapporteur proposal and proposes to discuss in other thread
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206492 P-CR Approval 23.700-28: KI#1 Solution 4 evaluations Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206288 P-CR Approval 23.700-28: KI#1, Sol#7: Update on wait timer to treat high priority user NTT DOCOMO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206021 P-CR Approval 23.700-28: KI#2&1, Sol#11: Update to resolve ENs LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206718 P-CR Approval 23.700-28: KI#1: Evaluation of solutions CATT Rel-18 Not Handled Stephen (Qualcomm) asks whether this evaluation is useful or needed
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) proposes this evaluation be merged into S2-2206935
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206719 P-CR Approval 23.700-28: KI#2: Evaluation of solutions CATT Rel-18 Not Handled Stephen (Qualcomm) asks whether this evaluation is useful or needed
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) proposes this evaluation be merged into S2-2206935
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206809 P-CR Approval 23.700-28: KI #1, Evaluations Samsung Rel-18 Not Handled Stephen (Qualcomm) suggests this be merged into S2-2206935
==== 9.X, 10.X Final Deadline ====
Not Handled
9.24 S2-2206810 P-CR Approval 23.700-28: KI #1, Interim conclusions Samsung Rel-18 Not Handled Stephen (Qualcomm) believes conclusions for clause 8.x should be postponed
==== 9.X, 10.X Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone this pCR
Jean Yves (Thales) comments that's this Tdoc is not handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.25 - - - Study on UPF enhancement for Exposure And SBA (FS_UPEAS) - - Docs:=43 -
9.25 - - - General - - Docs:=1 -
9.25 S2-2205885 P-CR Approval 23.700-62: TR Update about UPF not able to monitor retransmission Nokia, Nokia Shanghai Bell Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.25 - - - New Solutions - - Docs:=7 -
9.25 S2-2205585 P-CR Approval 23.700-62: KI #2, New Sol: UE IP address mapping information exposure by UPF DISH Network, China Mobile Rel-18 r12 agreed. Revised to S2-2207188. Kisuk(Samsung) supports this paper.
Fenqin(Huawei) comments
Yan (China Mobile) replies.
Magnus H (Ericsson) suggests to note this paper.
Jinsook (DISH) Replied to Saso
Saso (Intel) comments on the relation with the draft LS OUT to SA6 in 6900 (AI#4.1)
Laurent (Nokia): provides r03 (r02 can be skipped)
Jinsook (DISH) replied and suggest r01
Magnus H (Ericsson) comments and provides r04
Yan (China Mobile) replies to Saso and Magnus.
Josep (DT) provides r04 with co-sign based on r03.
Fenqin (Huawei) comments
Magnus H (Ericsson) comments and provides r05
Josep (DT) comments, provides r06.
Laurent (Nokia): answers
Jinsook (DISH) replies and provides r07
Fenqin (Huawei) comments and provide r08
Magnus H (Ericsson) provides r09
Jinsook (DISH) Providing the rev10 link
Jinsook (DISH) Question for clarification to Fenqin and provides rev10.
Fenqin (Huawei) Providing the rev11
Kisuk (Samsung) is ok with r10.
Laurent (Nokia): provides r12
Josep (DT) comments.
Fenqin (Huawei) provides r13.
Fenqin (Huawei) provides responds.
Josep (DT) is fine with 'it is FFS whether the external IP address, which UPF registered to NRF and detected by AF, can be overlapped due to UPF connecting to different domain'.
==== 9.X, 10.X Revisions Deadline ====
Jinsook (DISH) Prefer rev12 but can live with rev13
Fenqin (Huawei) can live with r12.
Kisuk(Samsung) Prefers r12.
Josep (DT) supports going with r12.
Yan (China Mobile) suggests to go with r12.
Magnus H (Ericsson) prefers r12
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207188 P-CR Approval 23.700-62: KI #2, New Sol: UE IP address mapping information exposure by UPF DISH Network, China Mobile Rel-18 Revision of S2-2205585r12. Approved Approved
9.25 S2-2205986 P-CR Approval 23.700-62: KI #2 New Solution: Support exposing codec rate adaptation from UPF to NEF/AF China Telecom Rel-18 Noted Yan (China Mobile) comments
Zhiwei (China Telecom) responses
Yan (China Mobile) replies
Fenqin (Huawei) support the view from Yan(China mobile)
Laurent (Nokia): Comments
Costas (Lenovo) provides comments
Zhiwei (China Telecom) suggests to note this paper.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.25 S2-2206322 P-CR Approval 23.700-62: KI#2: New solution: UPF Event Exposure with consideration on UPF performance LG Electronics Rel-18 r05 agreed. Revised to S2-2207189. Fenqin (Huawei) ask some question for clarification
Hyunsook (LGE) replies to Fenqin.
Laurent (Nokia): provides r01
Fenqin (Huawei) provides comments
Hyunsook (LGE) asks Fenqin's opinion.
Fenqin (Huawei) provides further comments to Hyunsook,
Hyunsook (LGE) provides r02.
Fenqin (Huawei) provides further comments and r03
Hyunsook (LGE) provides r04.
Fenqin (Huawei) ask one question
Hyunsook (LGE) answers to Fenqin.
Fenqin (Huawei) ask some further question
Hyunsook (LGE) clarifies and provides r05.
Magnus H (Ericsson) has the same concerns and questions as Fenqin
Hyunsook (LGE) replies to Magnus.
Magnus H (Ericsson) replies to Hyunsook
Hyunsook (LGE) provides a comment.
==== 9.X, 10.X Revisions Deadline ====
Magnus H (Ericsson) comments
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207189 P-CR Approval 23.700-62: KI#2: New solution: UPF Event Exposure with consideration on UPF performance LG Electronics Rel-18 Revision of S2-2206322r05. Approved Approved
9.25 S2-2206390 P-CR Approval 23.700-62: KI #2, New Sol: Support to subscribe SMF/UPF change notification from the SMF China Mobile Rel-18 r03 agreed. Revised to S2-2207190. Yan (China Mobile) provides r01
Fenqin (Huawei) Comments
Laurent (Nokia): provides r02
Yan (China Mobile) provides r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207190 P-CR Approval 23.700-62: KI #2, New Sol: Support to subscribe SMF/UPF change notification from the SMF China Mobile Rel-18 Revision of S2-2206390r03. Approved Approved
9.25 - - - Updated Solutions - - Docs:=18 -
9.25 S2-2205867 P-CR Approval 23.700-62: KI #1, Sol #1: Updates to solution and ENs removal Ericsson Rel-18 r05 agreed. Revised to S2-2207191, merging and S2-2206289 Yan (China Mobile) provides r01 by merging S2-2206289 into this S2-2205867
Fenqin (Huawei) provides r02
Magnus H (Ericsson) comments and provides r03
Yan (China Mobile) provides r04 based on r03
Magnus H (Ericsson) provides r05
Yan (China Mobile) is ok with r05
Kisuk (Samsung) is ok with r05
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207191 P-CR Approval 23.700-62: KI #1, Sol #1: Updates to solution and ENs removal Ericsson Rel-18 Revision of S2-2205867r05, merging and S2-2206289. Approved Approved
9.25 S2-2206289 P-CR Approval 23.700-62: KI #1, Sol #1: Update to remove ENs China Mobile Rel-18 Merged into S2-2207191 Yan (China Mobile) proposes to merge this S2-2206289 into S2-2205867
Yan (China Mobile) has merged this S2-2206289 into S2-2205867
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206731 P-CR Approval 23.700-62: KI #2, Sol #2: Update to remove EN ETRI Rel-18 Approved Fenqin (Huawei) provides comments
Yoohwa (ETRI) responds to Fenqin.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.25 S2-2205868 P-CR Approval 23.700-62: KI #2, Sol #7: Updates to solution and EN removal Ericsson Rel-18 Approved Fenqin (Huawei) provides comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.25 S2-2205553 P-CR Approval 23.700-62: KI #2, Sol #9: Update of solution 9 for NWDAF collecting data from UPF KDDI,vivo Rel-18 Merged into S2-2207192 Yan (China Mobile) proposes to merge this S2-2205553 into S2-2206733
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206733 P-CR Approval 23.700-62: KI #2, Sol #9: Update to clarify collecting data indirectly ETRI Rel-18 r01 agreed. Revised to S2-2207192, merging and S2-2205553 Tsutomu (KDDI) provides r01 to merge with S2-2205553.
Yoohwa (ETRI) agrees to r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207192 P-CR Approval 23.700-62: KI #2, Sol #9: Update to clarify collecting data indirectly ETRI Rel-18 Revision of S2-2206733r01, merging and S2-2205553. Approved Approved
9.25 S2-2206149 P-CR Approval 23.700-62: UPEAS R18 KI#2, Solution#10 Update of UPF event exposure service to NWDAF China Mobile Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.25 S2-2205985 P-CR Approval 23.700-62: KI #2, Sol #11: Update Solution 11 to remove ENs China Telecom Rel-18 Merged into S2-2207193 Yan (China Mobile) proposes to merge this S2-2205985 into S2-2206295
Zhiwei (China Telecom) agrees to merge this S2-2205985 into S2-2206295
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206295 P-CR Approval 23.700-62: KI #2, Sol #11: Update to remove ENs China Mobile Rel-18 r01 agreed. Revised to S2-2207193, merging and S2-2205985 Yan (China Mobile) provides r01 by merging 5985 into it.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207193 P-CR Approval 23.700-62: KI #2, Sol #11: Update to remove ENs China Mobile Rel-18 Revision of S2-2206295r01, merging and S2-2205985. Approved Approved
9.25 S2-2206309 P-CR Approval 23.700-62: FS_UPEAS, KI#2, Update solution 12 Vivo Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.25 S2-2206312 P-CR Approval 23.700-62: KI #2, Sol #16: Update to remove ENs China Mobile Rel-18 r01 agreed. Revised to S2-2207194. Laurent (Nokia): concerns with the updates
Yan (China Mobile) provides r01.
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): objects to R00
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207194 P-CR Approval 23.700-62: KI #2, Sol #16: Update to remove ENs China Mobile Rel-18 Revision of S2-2206312r01. Approved Approved
9.25 S2-2206313 P-CR Approval 23.700-62: KI #2, Sol #18: Update to remove ENs China Mobile Rel-18 r01 agreed. Revised to S2-2207195. Fenqin (Huawei) question for clarification
Yan (China Mobile) replies.
Yan (China Mobile) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207195 P-CR Approval 23.700-62: KI #2, Sol #18: Update to remove ENs China Mobile Rel-18 Revision of S2-2206313r01. Approved Approved
9.25 S2-2206324 P-CR Approval 23.700-62: KI #2, Sol #19: Update to remove ENs China Mobile Rel-18 Approved Fenqin (Huawei) provides comments
Yan (China Mobile) replies.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.25 - - - Evaluations and Conclusions - - Docs:=14 -
9.25 S2-2205501 P-CR Approval 23.700-62: Conclusion for KI#1 IPLOOK Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2205501 into it.
Laurent (Nokia): objects to any version for the sake of merging into 5866 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2205866 P-CR Approval 23.700-62: KI #1, Solution evaluation and conclusions Ericsson Rel-18 r13 agreed. Revised to S2-2207196, merging S2-2206310, S2-2206327, S2-2206423, S2-2206536, S2-2206913 and S2-2205501 Yan (China Mobile) proposes to use this S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge 5501, 6310, 6327, 6423, 6536, and 6913 into it.
Yan (China Mobile) provides r01 by merging 6327 in.
Junle Liao(IPLOOK) provides r03 by merging 5501 in.
Laurent (Nokia): provides r02
Zhiwei (China Telecom) provides r04 by merging 6423 in.
Fenqin (Huawei) provides r05
Magnus H (Ericsson) provides r06
Yan (China Mobile) provides r07 based on r06.
Huazhang (vivo) provides r08 based on r07
Huazhang (vivo) reply to Laurent (Nokia)
Huazhang (vivo) provides further comments and r09.
Yan (China Mobile) comments.
Huazhang (vivo) replies to Yan (China Mobile) comments.
Yan (China Mobile) replies to Huazhang.
Magnus H (Ericsson) provides r10 and comments
Kisuk (Samsung) is ok with r10.
Laurent (Nokia): provides r11
Fenqin (Huawei) provides r12
Huazhang (vivo) provides r13
Magnus H (Ericsson) comments
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): R12 is by far the best. can live with R05, R06, R07, R13; objects to any other version
Huazhang (vivo) can only live r13, the ENs is needed. And hope to go with r13
Magnus H (Ericsson) prefers r12, can live r13, objects to r09, r08 and r01-r04.
Huawei (Huawei) also prefers r12, can live with r13.
Yan (China Mobile) suggests to go with r13.
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207196 P-CR Approval 23.700-62: KI #1, Solution evaluation and conclusions Ericsson Rel-18 Revision of S2-2205866r13, merging S2-2206310, S2-2206327, S2-2206423, S2-2206536, S2-2206913 and S2-2205501. Approved Approved
9.25 S2-2206310 P-CR Approval 23.700-62: KI#1_evaluation_and_conclusion Vivo Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2206310 into it.
objects to any version for the sake of merging into 5866 as proposed by the rapporteur
Laurent (Nokia): objects to any version for the sake of merging into 5866 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206327 P-CR Approval 23.700-62: Evaluation and Conclusion for KI#1 China Mobile Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2206327 into it.
objects to any version for the sake of merging into 5866 as proposed by the rapporteur
Yan (China Mobile) has merged 6327 into 5866.
Laurent (Nokia): objects to any version for the sake of merging into 5866 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
Yan (China Mobile) proposes to change the status of this paper as 'Merged into 5866'.
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206423 P-CR Approval 23.700-62: KI #1: Evaluation and Conclusions China Telecom Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2206423 into it.
Zhiwei (China Telecom) has merged this S2-2206423 into S2-2205866.
==== 9.X, 10.X Revisions Deadline ====
Zhiwei (China Telecom): The status of this paper should be 'Merged into 5866' for this 6423 has already merged into 5866.
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206536 P-CR Approval 23.700-62: KI#1,Evaluation of solution on UPF discovery Huawei, HiSilicon Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2206536 into it.
objects to any version for the sake of merging into 5866 as proposed by the rapporteur
Laurent (Nokia): objects to any version for the sake of merging into 5866 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206913 P-CR Approval 23.700-62: Conclusions for KI#1 Samsung Rel-18 Merged into S2-2207196 Yan (China Mobile) proposes to use S2-2205866 as the baseline paper for KI#1 evaluation&conclusion and merge this S2-2206913 into it.
Kisuk (Samsung) merges this paper into S2-2205866.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2205869 P-CR Approval 23.700-62: KI #2, Solution evaluation and conclusions Ericsson Rel-18 Merged into S2-2207197 Yan (China Mobile) proposes to use S2-2206537 as the baseline paper for KI#2 evaluation&conclusion and merge this S2-2205869 into it.
objects to any version for the sake of merging into 5867 as proposed by the rapporteur
Laurent (Nokia): objects to any version for the sake of merging into 5867 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2205483 P-CR Approval 23.700-62: UPEAS conclusions Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2207197 Yan (China Mobile) proposes to use S2-2206537 as the baseline paper for KI#2 evaluation&conclusion and merge this S2-2205483 into it.
Laurent (Nokia): OK to merge as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206311 P-CR Approval 23.700-62: KI#2_evaluation_and_conclusion Vivo Rel-18 Merged into S2-2207197 Yan (China Mobile) proposes to use S2-2206537 as the baseline paper for KI#2 evaluation&conclusion and merge this S2-2206311 into it.
objects to any version for the sake of merging into 5867 as proposed by the rapporteur
Laurent (Nokia): objects to any version for the sake of merging into 5867 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 S2-2206537 P-CR Approval 23.700-62: KI#2, Evaluation and conclusion of KI#2 Huawei, HiSilicon Rel-18 r15 agreed. Revised to S2-2207197, merging S2-2205483, S2-2205869, S2-2206311 and S2-2206914 Yan (China Mobile) proposes to use this S2-2206537 as the baseline paper for KI#2 evaluation&conclusion and merge 5869, 5483, 6311, and 6914 into it.
Laurent (Nokia): provides r01
Fenqin (Huawei): responds.
Magnus H (Ericsson) provides r02
Fenqin (Huawei) provides r03
Yan (China Mobile) comments.
Magnus H (Ericsson) comments
Hyunsook (LGE) comments
Jinsook (DISH) support Hyunsook's comment
Laurent (Nokia): provides r05
Fenqin (Huawei): provides comments
Josep (DT) comments.
Fenqin(Huawei) comments.
Josep (DT) replies to Fenqin (Huawei) and asks a question for clarification.
Fenqin(Huawei) provide response to Josep(DT) and r06
Yoohwa (ETRI) provides r07.
Magnus H (Ericsson) added 2 new ENs in r08
Laurent (Nokia): Comments
Hyunsook (LGE) comments and provides r09.
Josep (DT) comments, provides r10.
Hyunsook (LGE) provides a comment.
Laurent (Nokia): provides r11
Fenqin (Huawei) provides r12.
Yan (China Mobile) provides r13 based on r12.
Yan (China Mobile) replies to Laurent.
Laurent (Nokia): provides r14
Huazhang (vivo) provides r15 based on r14
==== 9.X, 10.X Revisions Deadline ====
Laurent (Nokia): can only live with r15 or R14; can live with R11 or R12 + an EN; objects to any other version
Huazhang (vivo) agree to go with r15, thanks all, we have one meeting to solve these
Magnus H (Ericsson) OK to go with r15 or r14
Huazhang (vivo) can only agree with r15, and not ok with other revision
Sorry I forget to bring the other papers in title.
Fenqin (Huawei) we are ok to go with r15.
Yan (China Mobile) suggests to go with r15.
==== 9.X, 10.X Final Deadline ====
Revised
9.25 S2-2207197 P-CR Approval 23.700-62: KI#2, Evaluation and conclusion of KI#2 Huawei, HiSilicon Rel-18 Revision of S2-2206537r15, merging S2-2205483, S2-2205869, S2-2206311 and S2-2206914. Approved Approved
9.25 S2-2206914 P-CR Approval 23.700-62: Conclusions for KI#2 Samsung Rel-18 Merged into S2-2207197 Yan (China Mobile) proposes to use S2-2206537 as the baseline paper for KI#2 evaluation&conclusion and merge this S2-2206914 into it.
Kisuk (Samsung) merges this paper into S2-2206537.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.25 - - - Documents exceeding TU Budget - - Docs:=3 -
9.25 S2-2206394 P-CR Approval 23.700-62: KI #2, New Sol: Support to subscribe UPF change notification from the BSF China Mobile Rel-18 Not Handled Laurent (Nokia): objects to any version of this Tdoc (for the sake of merging into 6390 as suggested by rapporteur)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.25 S2-2206400 P-CR Approval 23.700-62: KI #2, New Sol: Support to subscribe UPF change notification from the NRF China Mobile Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.25 S2-2206331 P-CR Approval 23.700-62: Evaluation and Conclusion for KI#2 China Mobile Rel-18 Not Handled Laurent (Nokia): objects to any version for the sake of merging into 5867 as proposed by the rapporteur
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 - - - Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) - - Docs:=73 -
9.26 - - - KI#1: UE-to-UE Relay - - Docs:=10 -
9.26 S2-2205972 P-CR Approval 23.700-33: Overall Evaluation on KI#1 CATT Rel-18 r10 agreed. Revised to S2-2207505. Deng Qiang (CATT) provides r01 as a merger for KI#1 evaluation papers, and proposes to use this thread for KI#1 evaluation discussion.
Yali (OPPO) provides r02.
Steve (Huawei) provides some initial comments on sol#30.
Guillaume (MediaTek Inc.) provides r03
Steve (Huawei) provides r04, as in interim step.
Jung Je(Interdigital) provides r05.
LaeYoung (LGE) provides r06.
Responded to Hannu(Nokia)'s question
Hannu (Nokia) asks why isn't solution #8 shown at all in KI #1 evaluation?
Yali (OPPO) provides r07.
Jung Je (Interdigital) comments Yali(OPPO) and Steve(Huawei)
Yali (OPPO) replies to Jung Je (Interdigital).
Deng Qiang (CATT) provides r08.
Yali (OPPO) provides r09.
Steve (Huawei) comments on integrated discovery and alignment between solutions evaluations.
Jung Je (Interdigital) provides r10
Deng Qiang (CATT) replies to Jung Je (Interdigital).
==== 9.X, 10.X Revisions Deadline ====
Deng Qiang (CATT) is fine with r10.
Steve (Huawei) is ok with r10
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207505 P-CR Approval 23.700-33: Overall Evaluation on KI#1 CATT Rel-18 Revision of S2-2205972r10. Approved Approved
9.26 S2-2206360 P-CR Approval 23.700-33: KI#1: Sol#13 Sol#30: Layer 2 UE-UE Relay: Evaluation and Conclusion MediaTek Inc. Rel-18 r02 agreed. Revised to S2-2207506. Steve (Huawei) provides r01, so we don't end up with duplicate evaluation and conclusions.
Yali (OPPO) asks questions.
Jung Je (Interdigital) provides r02.
Guillaume (MediaTek Inc.) ok with r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207506 P-CR Approval 23.700-33: KI#1: Sol#13 Sol#30: Layer 2 UE-UE Relay: Evaluation and Conclusion MediaTek Inc. Rel-18 Revision of S2-2206360r02. Approved Approved
9.26 S2-2205997 P-CR Approval 23.700-33: KI#1 conclusion for UE-to-UE Relay OPPO, Ericsson, CATT Rel-18 r14 + changes agreed. Revised to S2-2207507, merging and S2-2206855 Deng Qiang (CATT) proposes to use this thread for KI#1 conclusion discussion.
Jung Je(Interdigital) provides r02
Steve (Huawei) comments in selection
Hannu (Nokia) asks question on r01.
Steve (Huawei) provides r01 for (re)selection
LaeYoung (LGE) provides r03.
Yali (OPPO) provides r04 and replies to Jung Je(Interdigital).
Sudeep (Apple) supports the direction in r04.
Jung je(Interdigital) responded to Yali(OPPO)
Yali (OPPO) provides r05.
Deng Qiang (CATT) comments on r07, and provides r08.
Jung Je (Interdigital) provides r06 and r07.
Jung Je (Interdigital) comments on r08, and provides r09.
Jung Je (Interdigital) provides r11.
Hong (Qualcomm) provides r10.
Yali (OPPO) provides r12.
Hong (Qualcomm) objects r12, and request a version without the sol# in the conclusion.
Yali (OPPO) provides r13.
Steve (Huawei) provides r14
Jung Je (Interdigital) provides r15
==== 9.X, 10.X Revisions Deadline ====
Yali (OPPO) cannot accept r15, r12-r14 is ok for me.
Jung Je (Interdigital) commented.
Hong (Qualcomm) is fine with both r13 and r14.
Yali (OPPO) provides r16 (after revision deadline) based on r14 according to Deng Qiang's comments. Both r14 and r16 are fine for me.
Deng Qiang (CATT) suggested to move forward with r14 + some additions.
Steve (Huawei) is ok with r14, or late r16 (i.e. r14 with the discussed changes). Change summary to follow.
Steve (Huawei) provides summary of change for late r16: R14 + 1) Change EN about Target UE Relay Selection to 'Editor's Note: It is FFS whether target UE may select Relay UE in Model B discovery.', 2) add new bullet 'For service authorization and policy/parameter provisioning to UE for UE-to-UE Relay operation, the PCF based service authorization and provisioning as defined in TS 23.304 [3] are used as basis for normative work.', and 3) change 'before E2E PC5 link establishment is performed' to 'before E2E PC5 messages are transmitted' for L2 Relay Per-hop links bullet. 4) remove the discussion part.
Jung Je (Interdigital) commented and uploaded r17
Jung Je(Interdigital) proposed to accept r14 + removing 'as depicted in Sol#1 Alt1' or r17(after revision deadline).
Yali (OPPO) propose to approve r17. On top of the change summary from Steve, the additional change in this version is: 5) remove 'as depicted in Sol#1 Alt1' from the EN of discovery integrated into PC5 unicast link establishment procedure.
Yali (OPPO) is also ok to approve r14 + removing 'as depicted in Sol#1 Alt1'.
Jung Je(Interdigital) is OK to approve r14 + removing 'as depicted in Sol#1 Alt1'.
Deng Qiang (CATT) is OK to approve r14 + removing 'as depicted in Sol#1 Alt1'.
Zhang (Ericsson) is ok with r17 or r14 + removing 'as depicted in Sol#1 Alt1'
Guillaume (MediaTek Inc.) ok with r14 + removing 'as depicted in Sol#1 Alt1'
Steve (Huawei) for confirmation, I am also ok with r14 + removing 'as depicted in Sol#1 Alt1'
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207507 P-CR Approval 23.700-33: KI#1 conclusion for UE-to-UE Relay OPPO, Ericsson, CATT Rel-18 Revision of S2-2205997r14 + changes, merging and S2-2206855. Approved Approved
9.26 S2-2206855 P-CR Approval 23.700-33: KI#1: conclusion for UE-to-UE Relay Interdigital Rel-18 Merged into S2-2207507 Steve (Huawei) propose to note/merge and concentrate on 5997.
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) as per the chairs notes, this should mark the as merged to 5997.
==== 9.X, 10.X Final Deadline ====
Merged
9.26 S2-2206631 P-CR Approval 23.700-33: KI#1 Sol#34 Update: Additional L2 U2U Details Huawei, HiSilicon Rel-18 Approved Yali (OPPO) asks a question.
Steve (Huawei) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.26 S2-2206191 OTHER Decision KI#1: Assistance information for UE-to-UE relay announcement and selection Contact Mitsubishi Electric RCE Rel-18 WITHDRAWN Withdrawn
9.26 S2-2206260 OTHER Decision KI#1: Assistance information for UE-to-UE relay announcement and selection Mitsubishi Electric Rel-18 Noted Steve (Huawei) should be noted.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.26 - - - KI#2: Path switching btw two indirect paths - - Docs:=3 -
9.26 S2-2206363 P-CR Approval 23.700-33: KI#2_Evaluation and conclusion on KI#2 Vivo, Nokia, Nokia Shanghai Bell, China Telecom Rel-18 r08 agreed. Revised to S2-2207508. Zhang (Ericsson) provides comments
Wen (vivo) replies and provides r01.
Heng (China Telecom) reply to Zhang (Ericsson)
Fei (OPPO) comments.
Steve (Huawei) comments on updates and rules
Heng (China Telecom) reply to Steve (Huawei) and provide r02
Deng Qiang (CATT) provides r03 to shorten the description.
Fei (OPPO) comments on r03.
Wen (vivo) provides r04.
LaeYoung (LGE) comments.
Wen (vivo) provides r05 based on LaeYoung (LGE) comments.
Hannu (Nokia) provides r06 and comments.
Steve (Huawei) comments on application layer reselection rules.
Heng (China Telecom) reply to Steve on application layer reselection rules.
Mehrdad (Mediatek Inc.) requests some clarifications
Wen (vivo) replies and provides r07
Heng (China Telecom) reply to Mehrdad (Mediatek Inc.)
Steve (Huawei) provides r08.
==== 9.X, 10.X Revisions Deadline ====
Fei (OPPO) is fine with r08.
Deng Qiang (CATT) is fine with r08.
Heng (China Telecom) can accept r08.
Wen (vivo) is fine with r08.
Mehrdad (Mediatek Inc.) is OK with r08
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207508 P-CR Approval 23.700-33: KI#2_Evaluation and conclusion on KI#2 Vivo, Nokia, Nokia Shanghai Bell, China Telecom Rel-18 Revision of S2-2206363r08. Approved Approved
9.26 S2-2206198 P-CR Approval 23.700-33: KI#2:Update to Solution#35 China Telecom Rel-18 Approved Mehrdad (Mediatek Inc.) comments
Jing (China Telecom) replies to Mehrdad (Mediatek Inc.).
Zhang (Ericsson) provides comments
Mehrdad (Mediatek Inc.) also agrees with the views shared by Ericsson and not sure if this update is needed.
Jing (China Telecom) replies to Zhang (Ericsson) and Mehrdad (Mediatek Inc.).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.26 - - - KI#3: Direct path switching btw PC5 and Uu - - Docs:=10 -
9.26 S2-2206020 P-CR Approval 23.700-33: KI#3, Conclusion LG Electronics Rel-18 Noted Deng Qiang (CATT) proposes to use this thread for KI#3 conclusion discussion.
Steve (Huawei) Do we note/merge as we seem to be concentrating evaluation and conclusion under 6635?
==== 9.X, 10.X Revisions Deadline ====
LaeYoung (LGE) confirms that this pCR can be NOTED.
==== 9.X, 10.X Final Deadline ====
Noted
9.26 S2-2206181 P-CR Approval 23.700-33: KI#3 Conclusion ZTE Rel-18 Merged into S2-2207509 Hao (ZTE) confirms this paper is merged into S2-2206635.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.26 S2-2206364 P-CR Approval 23.700-33: KI#3_Evaluation and conclusion on KI#3 Vivo Rel-18 Noted Steve (Huawei) Do we note/merge as we seem to be concentrating evaluation and conclusion under 6635?
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) as per the chairs notes, this can be mark the as noted.
Wen (vivo) confirms that this paper can be mark the as noted.
==== 9.X, 10.X Final Deadline ====
Noted
9.26 S2-2206635 P-CR Approval 23.700-33: KI#3: Evaluation and Conclusion Huawei, HiSilicon Rel-18 r13 agreed. Revised to S2-2207509, merging and S2-2206181 Deng Qiang (CATT) proposes to use this thread for KI#3 evaluation discussion.
Zhang (Ericsson) suggest to use this paper as baseline for KI#3 evaluation and conclusion
Steve (Huawei) comments
Zhang (Ericsson) response to Steve (Huawei)
Jung Je (Interdigital) comments
Hong (Qualcomm) comments
Fei (OPPO) comments.
LaeYoung (LGE) comments.
Hao (ZTE) provides r03 which merges path permission policy part from S2-2206181.
Wen (vivo) comments and provides r02
Jung Je (Interdigital) comments.
Steve (Huawei) answers questions, provides r01
LaeYoung (LGE) provides r04.
Steve (Huawei) provides r05 with some editorial clean-up
Jung Je(Interdigital) provides r06 and r07
Steve (Huawei) comments on r07
Deng Qiang (CATT) provides r08, and comments.
Wen (vivo) comments on r08 and provides r09.
LaeYoung (LGE) provides r10 on top of r08 from Deng Qiang (CATT).
LaeYoung (LGE) provides r11.
Wen (vivo) provides r12 on top of r11.
Steve (Huawei) comments - let's stop bouncing solutions in and out and think for a moment.
Fei (OPPO) provides comments.
Heng (China Telecom) agree with Fei.
Steve (Huawei) provides r13 and r14.
Changhong (Intel) provides r15.
Steve (Huawei) objects to r15
Changhong (Intel) ask Steve to clarify.
==== 9.X, 10.X Revisions Deadline ====
LaeYoung (LGE) prefers r11 and r13, and can live with r14.
Fei (OPPO) is fine with r14.
Deng Qiang (CATT) prefers r08, and can live with r14.
Wen (vivo) prefers r09 and r13, and can live with r14.
Steve (Huawei) prefers r13, can live with r14
Steve (Huawei) clarifies
Jung Je (Interdigital) prefers r13, and live with r14.
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207509 P-CR Approval 23.700-33: KI#3: Evaluation and Conclusion Huawei, HiSilicon Rel-18 Revision of S2-2206635r13, merging and S2-2206181. Approved Approved
9.26 S2-2206180 DISCUSSION Discussion KI#3 Discussion on Using Unified Path Permission Policy for Both Path Selection and Switching ZTE Rel-18 Noted Steve (Huawei) I suggested noting (it's a discussion and the discussion looks to be under 6635).
Hao (ZTE) confirms this DP could be noted.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.26 S2-2206398 P-CR Approval 23.700-33: TR 23.700-33: Solution #21: Update on path switch from Uu to PC5 China Telecom Rel-18 r01 agreed. Revised to S2-2207510. Mehrdad (Mediatek Inc.) thinks this change is not needed.
Changzheng(China Telecom) provides r01.
==== 9.X, 10.X Revisions Deadline ====
Mehrdad (Mediatek Inc.) can live with r01
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207510 P-CR Approval 23.700-33: TR 23.700-33: Solution #21: Update on path switch from Uu to PC5 China Telecom Rel-18 Revision of S2-2206398r01. Approved Approved
9.26 S2-2206852 P-CR Approval 23.700-33: KI #3: Solution update on sol#22 Interdigital Rel-18 r02 agreed. Revised to S2-2207511. Changzheng(China Telecom) asks for clarification.
Jung Je(Interdigital) responded Changzheng(China Telecom)
Jing (China Telecom) provides r01 to merge S2-2206211(only update) into S2-2206852.
Steve (Huawei) Comments
Jung Je (Interdigital) respondes Steve(Huawei)
Steve (Huawei) seeks further clarification
Jung Je (Interdigital) provided r02 and responded Steve(Huawei)
Jing (China Telecom) responds to Steve(Huawei).
Hong (Qualcomm) comments.
Jing (China Telecom) responds to Hong (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
Jing (China Telecom) provides r03.
Steve (Huawei) Keeping the EN seems sensible (r02) as it looks like some discussion is still needed.
Jung Je (Interdigital) propose to accept r02
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207511 P-CR Approval 23.700-33: KI #3: Solution update on sol#22 Interdigital Rel-18 Revision of S2-2206852r02. Approved Approved
9.26 - - - KI#4: Path switching for L2 Relay - - Docs:=4 -
9.26 S2-2205973 P-CR Approval 23.700-33: Overall Evaluation and Conclusion on KI#4 CATT Rel-18 CC#4: CATT proposed r06 with changes. Revised to S2-2207512, merging S2-2206910. Deng Qiang (CATT) provides r01 as a merger for KI#4 evaluation/conclusion papers, and proposes to use this thread for KI#4 evaluation/conclusion discussion.
Fei (OPPO) comments and provides r02.
LaeYoung (LGE) asks some questions.
Fei (OPPO) responds to LaeYoung (LGE)
LaeYoung (LGE) responds to Fei (OPPO).
Mehrdad (Mediatek Inc.) comments on all revisions of this PCR
LaeYoung (LGE) comments.
Steve (Huawei) comments on the authorised PLMN list
Judy (Ericsson) comments on all revisions
Deng Qiang (CATT) provides r03.
Mehrdad (Mediatek Inc.) is OK with r03.
Fei (OPPO) replied to LaeYoung
Fei (OPPO) comments on r03.
Deng Qiang (CATT) provides r04.
Judy (Ericsson) provides r05 to convert the notes for RAN dependency to ENs.
LaeYoung (LGE) comments that NOTEs still used in r05 instead of ENs?
Fei (OPPO) comments on r05.
Judy (Ericsson) provides r06 to change text 'note' to 'editor's note'.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) objects to r06, they should be NOTE not EN.
Changhong (Intel) replies to Deng Qiang.
Deng Qiang (CATT) reworded the ENs.
Deng Qiang (CATT) asks for CC#4 approval with rephrasing the two ENs.
Steve (Huawei) supports the suggestion of r06 + ', and the SA2 impact is FFS' added to both ENs.
Deng Qiang (CATT) proposes to approve r06 + ', and the SA2 impact is FFS' added to both ENs.
Revised
9.26 S2-2207512 P-CR Approval 23.700-33: Overall Evaluation and Conclusion on KI#4 CATT Rel-18 Revision of S2-2205973r06 + changes, merging S2-2206910. Approved Approved
9.26 S2-2206910 P-CR Approval 23.700-33: PCR_5G_ProSe- evaluation for KI#4 Xiaomi Rel-18 Merged into S2-2207512 Steve (Huawei) Do we consider this merged to 5973?
Jianning (Xiaomi) is ok to merge into 5973
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.26 S2-2205991 P-CR Approval 23.700-33: KI#4, Solution#23: Update on target relay selection OPPO Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.26 - - - KI#5: multi-path transmission - - Docs:=11 -
9.26 S2-2206069 P-CR Approval 23.700-33: KI#5 Evaluation and Conclusion Intel, Qualcomm Rel-18 r21 + changes agreed. Revised to S2-2207513, merging S2-2206365 and S2-2206909 Deng Qiang (CATT) proposes to use this thread for KI#5 evaluation and conclusion discussion.
Wen (vivo) comments.
Fei (OPPO) comments.
LaeYoung (LGE) comments.
Changhong (Intel) provides r01 and replies to comments.
Wen (vivo) comments on r01.
Heng (China Telecom) comment on r01.
Judy (Ericsson) provides r03
Steve (Huawei) provides r02 as an interim revision
Wen (vivo) provides r05 based on previous response
LaeYoung (LGE) provides r06 on top of r03.
Wen (vivo) replies to Hong
Changhong (Intel) comments on r05.
Wen(vivo) replies Changhong (Intel) and comments on r06.
Heng(China Telecom) provide r07.
Hao (ZTE) comments and provides r08.
Hao (ZTE) responds to LaeYoung (LGE).
LaeYoung (LGE) comments on r07 and r08.
LaeYoung (LGE) responds to Hao (ZTE).
Wen (vivo) comments and provides r09.
Changhong (Intel) provides r09.
Changhong (Intel) corrected it's r10 not r09.
Wen (vivo) provides r11.
Steve (Huawei) comments on policy and RAN impacts.
Hao (ZTE) comments on r12.
Deng Qiang (CATT) provides r12, and comments.
Judy (Ericsson) provides r13, moving Rel-18 ATSSS feature to an EN
Deng Qiang (CATT) replies to Hao (ZTE).
Hong (Qualcomm) asks Judy on the dependency on Rel-18 ATSSS.
Judy (Ericsson) responds to Hong (Qualcomm)
Fei (OPPO) provides r14.
Steve (Huawei) provides r15, comments on NOTE2 - it is a conclusion.
Changhong (Intel) provides r15.
Changhong (Intel) provides r16 since r15 was occupied by Steve.
Deng Qiang (CATT) asks questions on policy authorization.
LaeYoung (LGE) provides r17.
Fei (OPPO) provides comments and r18.
Wen(vivo) comments.
Michele (Huawei) provides r19
Changhong (Intel) replies to comments on L3+N3IWF policy enhancement.
Changhong (Intel) replies to LaeYoung.
Fei (OPPO) comments on r19.
LaeYoung (LGE) cannot accept r19.
Michele (Huawei) replied to Fei (OPPO) comments and provided r20.
Michele (Huawei) provides r21.
Fei (OPPO) Replied to Michele.
Changhong (Intel) provides r22 and objects to any revision doesn't cover the Policy Authorization for multi-path transmission with L3 U2N Relay access with N3IWF and L2 U2N Relay with Multi-PDU-Session access.
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) can only accept r00, r16 and r22.
LaeYoung (LGE) can only accept r18 and r21.
Fei (OPPO) can only accept r18 and r21.
Changhong (Intel) asks questions to Fei and LaeYoung and proposes the way forward.
Changhong (Intel) asks for CC#4 approval with rephrasing the EN.
LaeYoung (LGE) is fine with r21 + 1st EN suggestion from Changhong (Intel).
Fei (OPPO) is fine with r21+ reworded EN
Wen (vivo) is fine with r21+ reworded EN as well
Heng(China Telecom) provides suggestion
Huawei supports r21 + with the following rephrasing of the Editor's Note in the conclusions 'Editor's note: Whether policy authorization for multi-path transmission via direct Uu path and Layer 3 U2N Relay UE with N3IWF is needed is FFS.'
Revised
9.26 S2-2207513 P-CR Approval 23.700-33: KI#5 Evaluation and Conclusion Intel, Qualcomm Rel-18 Revision of S2-2206069r21 + changes, merging S2-2206365 and S2-2206909. Approved Approved
9.26 S2-2206365 P-CR Approval 23.700-33: KI#5_Evaluation and conclusion on KI#5 Vivo Rel-18 CC#4: To be merged into revision of S2-2206069. Merged into S2-2207513 Steve (Huawei) Do we mark this merged to 6069?
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) as per the chairs notes, this should mark the as merged to 6069.
Wen (vivo) confirms that this marks as merged to 6069.
Merged
9.26 S2-2206909 P-CR Approval 23.700-33: PCR_5G_ProSe- evaluation for KI#5 Xiaomi Rel-18 Merged into S2-2207513 Steve (Huawei) Do we mark this merged to 6069?
Jianning (Xiaomi) agrees to merge into 6069
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Merged
9.26 S2-2206633 P-CR Approval 23.700-33: KI#5 Sol#27 Update: Adding Support of multipath transmission via Layer-3 UE to Network Relay Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2207514. Fei (OPPO) comments.
Michele (Huawei) provides r01
Fei (OPPO) provide comments on r01.
Michele (Huawei) provides r02 addressing Fei's (OPPO) comments.
Hong (Qualcomm) asks some questions.
Michele (Huawei) replied to questions from Hong (Qualcomm) and provides r03.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207514 P-CR Approval 23.700-33: KI#5 Sol#27 Update: Adding Support of multipath transmission via Layer-3 UE to Network Relay Huawei, HiSilicon Rel-18 Revision of S2-2206633r03. Approved Approved
9.26 S2-2206395 P-CR Approval 23.700-33: TR 23.700-33: Solution #28: Update on MA-PDU Session Establishment China Telecom Rel-18 Approved Laurent (Nokia): objects to any version of this Tdoc (for the sake of merging into 6390 as suggested by rapporteur))
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Approved
9.26 S2-2206182 P-CR Approval 23.700-33: KI#5, Sol#39 Update to Resolve ENs ZTE Rel-18 Approved
==== 9.X, 10.X Final Deadline ====
Approved
9.26 S2-2205570 P-CR Approval 23.700-33: KI#5: Update to Solution#41 to resolve EN China Telecom Rel-18 r01 agreed. Revised to S2-2207515. LaeYoung (LGE) comments that 7.X should be removed.
Heng (China Telecom) agree with LaeYoung (LGE)
==== 9.X, 10.X Revisions Deadline ====
LaeYoung (LGE) comments that r01 provided from Heng (China Telecom) on this Monday w/o mentioning it within the tag and is OK with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207515 P-CR Approval 23.700-33: KI#5: Update to Solution#41 to resolve EN China Telecom Rel-18 Revision of S2-2205570r01. Approved Approved
9.26 S2-2206687 LS OUT Approval [DRAFT] LS on redundant communication using L3 relay China Telecommunications Rel-18 Noted LaeYoung (LGE) objects and proposes to NOTE this LS because multi-path including L3 Relay cannot have RAN impacts.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
9.26 - - - KI#6: PC5 Parameter Provisioning - - Docs:=6 -
9.26 S2-2206629 P-CR Approval 23.700-33: KI#1 Sol#8 Update: Policy updates to align with R17 ProSe Huawei, HiSilicon, Intel Rel-18 r01 agreed. Revised to S2-2207516. Judy (Ericsson) asks questions
Steve (Huawei) comments on Remote UE
LaeYoung (LGE) comments on the term.
Steve (Huawei) provides r01
Fei (OPPO) comments.
Steve (Huawei) comments on further updates
LaeYoung (LGE) answers to Steve (Huawei) and Fei (OPPO).
Fei (OPPO) thanks for LaeYoung (LGE)'s proposal
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207516 P-CR Approval 23.700-33: KI#1 Sol#8 Update: Policy updates to align with R17 ProSe Huawei, HiSilicon, Intel Rel-18 Revision of S2-2206629r01. Approved Approved
9.26 S2-2206023 P-CR Approval 23.700-33: KI#6&1, Sol#8: Update to add Service Authorization to NG-RAN LG Electronics Rel-18 r03 agreed. Revised to S2-2207517. Judy (Ericsson) provides r01
LaeYoung (LGE) is OK with r01.
Wen (vivo) comments.
LaeYoung (LGE) is provides r02.
LaeYoung (LGE) answers to Wen (vivo).
Fei (OPPO) comments.
Steve (Huawei) comments, I am confused as well
LaeYoung (LGE) is provides r03.
==== 9.X, 10.X Revisions Deadline ====
Fei (OPPO) is fine with r03.
Steve (Huawei) is ok with r03
Wen (vivo) is ok with r03
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207517 P-CR Approval 23.700-33: KI#6&1, Sol#8: Update to add Service Authorization to NG-RAN LG Electronics Rel-18 Revision of S2-2206023r03. Approved Approved
9.26 S2-2206025 LS OUT Approval [DRAFT] LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN LG Electronics Rel-18 r01 agreed. Revised to S2-2207518. LaeYoung (LGE) provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207518 LS OUT Approval LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN SA WG2 Rel-18 Revision of S2-2206025r01. Approved Approved
9.26 - - - KI#7: Emergency service - - Docs:=11 -
9.26 S2-2205433 LS In Action LS from SA WG1: Reply LS on emergency service support over ProSe Relays SA WG1 (S1-221222) Rel-18 Noted Fei (OPPO) proposes to note this incoming LS since there is no action to SA2.
Hannu (Nokia) agrees to note the LS but points out that the SA1 answers to our questions will steer our solution evaluation.
==== 9.X, 10.X Revisions Deadline ====
Noted
9.26 S2-2205990 P-CR Approval 23.700-33: KI#7 KI update: KI description alignment on emergency OPPO Rel-18 r08 agreed. Revised to S2-2207519. Wen (vivo) comments and provides r01.
Judy (Ericsson) provides r02
Sudeep (Apple) has a question on the changes in r01.
Wen (vivo) replies to Sudeep (Apple).
Fei (OPPO) replied to Judy (Ericsson).
Judy (Ericsson) comments
Fei (OPPO) provides responses to Judy (Ericsson)
Mehrdad (Mediatek Inc.) comments on r02
Fei (OPPO) responds to Mehrdad (Mediatek)
Steve (Huawei) comments
Mehrdad (Mediatek Inc.) comments on r03
Hannu (Nokia) provides r03.
Mehrdad (Mediatek Inc.) provides r04.
Steve (Huawei) provides r05
Judy (Ericsson) provides r07
Fei (OPPO) provides r06.
Mehrdad (Mediatek Inc.) is ok with r04 and r05 but can not agree with the rest of revisions so far.
Hannu (Nokia) asks about the service requirement for limited service emergency support
Mehrdad (Mediatek Inc.) replies to OPPO.
Fei (OPPO) replies.
Judy (Ericsson) responds to Mehrdad (Mediatek Inc.) on the prioritized handling of L2 Relay UE by its PLMN
Mehrdad (Mediatek Inc.) replies to Ericsson
Hong (Qualcomm) comments.
Judy (Ericsson) provides r07 taking out NOTE 2
Fei (OPPO) indicates that Judy (Ericsson) provides r08 taking out NOTE 2
Judy (Ericsson) thanks Fei's correction and confirms that she provides r08.
Mehrdad (Mediatek Inc.) is OK with r08 and co-signs the PCR
Fei (OPPO) thanks for Mehrdad's cosign
==== 9.X, 10.X Revisions Deadline ====
Wen (vivo) is ok with r08 and would like to co-sign this PCR
Fei (OPPO) thanks for Wen (vivo)'s cosign.
Steve (Huawei) is ok with r08.
Mehrdad (Mediatek Inc.) is OK with r8 and support and co-sign it. We are also OK with r04 and r05 but we object to the rest of revisions.
Hannu (Nokia) supports r08 and thanks for resolving his earlier concerns on limited service state requirement.
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207519 P-CR Approval 23.700-33: KI#7 KI update: KI description alignment on emergency OPPO Rel-18 Revision of S2-2205990r08. Approved Approved
9.26 S2-2205809 P-CR Approval 23.700-33: KI#7, Sol#42: Update to resolve EN for Emergency Services for UE to Network Relaying Ericsson Rel-18 r06 agreed. Revised to S2-2207520. Sudeep (Apple) seeks clarification.
Judy (Ericsson) responds to Sudeep (Apple) and provide r01.
Fei (OPPO) comments.
Mehrdad (Mediatek Inc.) comments
Judy (Ericsson) responds to Mehrdad
Mehrdad (Mediatek Inc.) still does not agree that the changes are applicable to L2 Relay. We can not agree with original version and r01.
Hong (Qualcomm) provides r02.
Mehrdad (Mediatek Inc.) replies to Qualcomm and Ericsson and provides r03.
Steve (Huawei) provides r04, comments on EN and overlap
Judy (Ericsson) responds and provides r05
Steve (Huawei) comments on network indications
Steve (Huawei) tries the last sentence again.
Judy (Ericsson) comment on indication from AMF to 5G ProSe enabled-UE that is capable of U2N Relay.
Mehrdad (Mediatek Inc.) provides r06
Steve (Huawei) comments on which change and overlap
==== 9.X, 10.X Revisions Deadline ====
Steve (Huawei) Is ok with r06
Mehrdad (Mediatek Inc.) is OK with r06. But we object to the original version, r01, r02 and r05.
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207520 P-CR Approval 23.700-33: KI#7, Sol#42: Update to resolve EN for Emergency Services for UE to Network Relaying Ericsson Rel-18 Revision of S2-2205809r06. Approved Approved
9.26 S2-2206632 P-CR Approval 23.700-33: KI#7 Sol#42 Update: EN removal Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2207521. Sudeep (Apple) seeks clarification on mandating L3 relay without N3IWF for emergency services.
Steve (Huawei) comments
Hong (Qualcomm) raise the question regarding the limit on using N3IWF.
Wen (vivo) comments
Judy (Ericsson) provides r01
Judy (Ericsson) comments
Steve (Huawei) provides r02.
Steve (Huawei) comments on SIB indication
Hong (Qualcomm) provides r03.
Steve (Huawei) comments on the indication
Hong (Qualcomm) comments.
Judy (Ericsson) agrees with Hong's comment
Fei (OPPO) comments.
Mehrdad (Mediatek Inc.) asks a question
Hong (Qualcomm) replies to Mehrdad.
Steve (Huawei) comments on next meeting.
Mehrdad (Mediatek Inc.) is OK with r03 and requests to co-sign.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207521 P-CR Approval 23.700-33: KI#7 Sol#42 Update: EN removal Huawei, HiSilicon Rel-18 Revision of S2-2206632r03. Approved Approved
9.26 S2-2206185 P-CR Approval 23.700-33: KI#7, Sol#44 Updates ZTE Rel-18 r01 agreed. Revised to S2-2207522. Judy (Ericsson) comments
Hao (ZTE) responds.
Judy (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
Hao (ZTE) is fine with r01.
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207522 P-CR Approval 23.700-33: KI#7, Sol#44 Updates ZTE Rel-18 Revision of S2-2206185r01. Approved Approved
9.26 S2-2206367 P-CR Approval 23.700-33: KI#7_Solution#45 Update for EN removal Vivo Rel-18 r01 agreed. Revised to S2-2207523. Judy (Ericsson) comments
Wen (vivo) replies
Wen (vivo) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
9.26 S2-2207523 P-CR Approval 23.700-33: KI#7_Solution#45 Update for EN removal Vivo Rel-18 Revision of S2-2206367r01. Approved Approved
9.26 - - - Documents exceeding TU Budget - - Docs:=18 -
9.26 S2-2205995 P-CR Approval 23.700-33: KI#1 Evaluation for UE-to-UE Relay solutions OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206634 P-CR Approval 23.700-33: KI#1: Evaluation and Conclusion Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206853 P-CR Approval 23.700-33: KI#1: Evaluation on UE-to-UE Relay Interdigital Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206019 P-CR Approval 23.700-33: KI#3, Evaluation LG Electronics Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206211 P-CR Approval 23.700-33: KI#3:Update and evaluate to Solution#22 China Telecom, Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206385 P-CR Approval 23.700-33: TR 23.700-33: Discussion on IPv4 problem in direct path switching from PC5 to Uu China Telecom Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206857 P-CR Approval 23.700-33: KI #3: Evaluation Interdigital Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2205992 P-CR Approval 23.700-33: KI#4: Evaluation and Conclusion for KI#4 OPPO Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2205974 P-CR Approval 23.700-33: Overall Evaluation and Conclusion on KI#5 CATT Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206183 P-CR Approval 23.700-33: KI#5 Evaluation ZTE Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206184 P-CR Approval 23.700-33: KI#5 Conclusion ZTE Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206630 P-CR Approval 23.700-33: KI#5 Sol#29 Update: Policy and Authorization for Multi-path Transmission Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206636 P-CR Approval 23.700-33: KI5: Evaluation and conclusion for Layer-2 UE-to-Network Relay Huawei, HiSilicon Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206366 P-CR Approval 23.700-33: KI#7_Solution#42 Update for mobility restriction Vivo Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2205810 P-CR Approval 23.700-33: KI#7, Evaluation on Emergency Services for UE to Network Relaying Ericsson Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2205811 P-CR Approval 23.700-33: KI#7, Conclusion on Emergency Services for UE to Network Relaying Ericsson Rel-18 Not Handled Mehrdad (Mediatek Inc.) comments
Judy (Ericsson) responds to Mehrdad (Mediatek Inc.) and comment that this paper is 'Documents exceeding TU Budget'.
Hannu (Nokia) volunteers to work together with Judy (Ericsson) and others to minimize documents exceeding budget next time.
Judy (Ericsson) thanks Hannu (Nokia) for the proposal.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206574 P-CR Approval 23.700-33: KI#7 emergency: solution evaluation and initial conclusions Nokia, Nokia Shanghai Bell Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.26 S2-2206696 P-CR Approval 23.700-33: Evaluation of Key Issue #7 Apple Rel-18 Not Handled
==== 9.X, 10.X Final Deadline ====
Not Handled
9.27 - - - Study on Seamless UE context recovery (FS_SUECR) - - Docs:=0 -
10 - - - Project Planning and Management - - Docs:=0 -
10.1 - - - Revised Rel-18 Study Items - - Docs:=8 -
10.1 S2-2205979 SID REVISED Approval Revised SID on Study on Proximity-based Services in 5GS Phase 2 CATT, OPPO Rel-18 Revised to S2-2207701.
==== 9.X, 10.X Final Deadline ====
Revised
10.1 S2-2207701 SID REVISED Approval Revised SID on Study on Proximity-based Services in 5GS Phase 2 CATT, OPPO Rel-18 Revision of S2-2205979. Approved Approved
10.1 S2-2206071 SID REVISED Approval Revised SID: Study on enhancement of 5G UE Policy (FS_eUEPO) Intel (Rapporteur) Rel-18 Revised to S2-2207702. Changhong (Intel) provides r01 with editorial change and adding InterDigital as supporting company.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Changhong (Intel) provides r02 by correcting table in clause 5 and adding AT&T and NEC as supporting company.
Revised
10.1 S2-2207702 SID REVISED Approval Revised SID: Study on enhancement of 5G UE Policy (FS_eUEPO) Intel (Rapporteur) Rel-18 Revision of S2-2206071. Approved Approved
10.1 S2-2206757 SID REVISED Approval Revised SID on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Revised to S2-2207703.
==== 9.X, 10.X Final Deadline ====
Revised
10.1 S2-2207703 SID REVISED Approval Revised SID on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Revision of S2-2206757. Approved Approved
10.1 S2-2206072 WID NEW Approval WID for FS_eUEPO Intel (Rapporteur) CC#5: r03 agreed. Revised to S2-2207881. Belen (Ericsson) provides comments
LaeYoung (LGE) provides comments.
Pallab (Nokia) provides comments
==== 9.X, 10.X Revisions Deadline ====
Changhong(Intel) replies to comments
==== 9.X, 10.X Final Deadline ====
Changhong(Intel) provides r01.
Revised
10.1 S2-2207881 WID NEW Approval WID for FS_eUEPO Intel (Rapporteur) - Revision of S2-2206072r03. CC#5: Approved Approved
10.2 - - - TS/TR Cover sheets - - Docs:=45 -
10.2 S2-2205591 TS OR TR COVER Approval Presentation of Report to TSG: TR 23.700-46, Version 0.2.0 Ericsson Rel-18 Revised to S2-2207842.
==== 9.X, 10.X Final Deadline ====
György (Ericsson) provides the draft in r01.
György (Ericsson) provides r02.
Laurent (Nokia): I am not sure we can leave these 2 points for normative phase: NEF and expose the N6 uplink routing
György (Ericsson): There is no time allocated for DetNet at the next meeting. I suggest to organize an offline CC to help progress in the normative phase.
Laurent (Nokia): answers, sorry Györgi, I doubt we can conclude during an offline CC. we need a meeting with hard decision power
Revised
10.2 S2-2207842 TS OR TR COVER Approval Presentation of Report to TSG: TR 23.700-46, Version 0.2.0 Ericsson Rel-18 Revision of S2-2205591 OPEN
10.2 S2-2205645 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-18 to TSG SA#97 Intel Rel-18 r01 agreed. Revised to S2-2207843. Megha (Intel) provides r01 for the coversheet and comments
==== 9.X, 10.X Final Deadline ====
Megha (Intel) provides r02 for the coversheet and comments
Revised
10.2 S2-2207843 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-18 to TSG SA#97 Intel Rel-18 Revision of S2-2205645r01 OPEN
10.2 S2-2205650 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-68 Ericsson (rapporteur) Rel-18 r01 agreed. Revised to S2-2207844. Qian (Ericsson) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Qian (Ericsson) provides draft revision based on the new tdoc for the coversheet (in DRAFTS folder)
Revised
10.2 S2-2207844 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-68 Ericsson (rapporteur) Rel-18 Revision of S2-2205650r01 OPEN
10.2 S2-2205776 P-CR Approval 23.700-87: Cover sheet for presentation of TR 23.700-87 to TSG SA#97 China Mobile Rel-18 Revised to S2-2207845.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207845 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-87 to TSG SA#97 China Mobile Rel-18 Revision of S2-2205776 OPEN
10.2 S2-2205980 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-33 to TSG SA#97E for information CATT, OPPO Rel-18 Revised to S2-2207846.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207846 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-33 to TSG SA#97E for information CATT, OPPO Rel-18 Revision of S2-2205980 OPEN
10.2 S2-2206070 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-85 to TSG SA#97E Intel (Rapporteur) Rel-18 Revised to S2-2207847.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207847 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-85 to TSG SA#97E Intel (Rapporteur) Rel-18 Revision of S2-2206070 OPEN
10.2 S2-2206436 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-27 to TSG SA#97E for information CATT Rel-18 Revised to S2-2207848.
==== 9.X, 10.X Final Deadline ====
Hucheng (CATT) provides r01.
Revised
10.2 S2-2207848 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-27 to TSG SA#97E for information CATT Rel-18 Revision of S2-2206436 OPEN
10.2 S2-2206489 TS OR TR COVER Approval Cover sheet for FS_PIN vivo Rel-18 Revised to S2-2207849.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207849 TS OR TR COVER Approval Cover sheet for FS_PIN vivo Rel-18 Revision of S2-2206489 OPEN
10.2 S2-2206556 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-74 to TSG SA#97 Huawei, HiSilicon Rel-18 Revised to S2-2207850.
==== 9.X, 10.X Final Deadline ====
Qianghua (Huawei) provides r01 for cover sheet of GMEC
Laurent (Nokia): Comments: I'd suggest the TR is only sent for info, avoiding formal Cr(s) to update it. just a suggestion
Revised
10.2 S2-2207850 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-74 to TSG SA#97 Huawei, HiSilicon Rel-18 Revision of S2-2206556 OPEN
10.2 S2-2206661 TS OR TR COVER Approval TR 23.700 41 FS_eNS_Ph3 for information ZTE, LG Electronic Rel-18 r01 agreed. Revised to S2-2207851. Jinguo(ZTE) provides r01
==== 9.X, 10.X Final Deadline ====
Fenqin(Huawei) provides r02
Jinguo(ZTE) is ok with r02
Revised
10.2 S2-2207851 TS OR TR COVER Approval TR 23.700 41 FS_eNS_Ph3 for information ZTE, LG Electronic Rel-18 Revision of S2-2206661r01 OPEN
10.2 S2-2206952 TS OR TR COVER Approval Cover sheet for 23.700-48 to TSG SA for information Huawei Rel-18 Revised to S2-2207852.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207852 TS OR TR COVER Approval Cover sheet for 23.700-48 to TSG SA for information Huawei Rel-18 Revision of S2-2206952 OPEN
10.2 S2-2206953 TS OR TR COVER Approval Cover sheet for 23.700-05 to TSG SA for information Qualcomm Rel-18 Revised to S2-2207853. Hong (Qualcomm) provides the initial draft.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207853 TS OR TR COVER Approval Cover sheet for 23.700-05 to TSG SA for information Qualcomm Rel-18 Revision of S2-2206953 OPEN
10.2 S2-2206954 TS OR TR COVER Approval Cover sheet for 23.700-25 to TSG SA for approval Nokia Rel-18 Revised to S2-2207854. Devaki (Nokia) provides r0 of S2-2206954 (FS_TRS_URLLC TR 23.600-25). Even if we have progressed beyond 80%, consensus to present TR for information during this Quarter and for approval during Q4. Request chair to update the title of the cover sheet to 'information'.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207854 TS OR TR COVER Approval Cover sheet for 23.700-25 to TSG SA for approval Nokia Rel-18 Revision of S2-2206954 OPEN
10.2 S2-2206955 TS OR TR COVER Approval Cover sheet for 23.700-89 to TSG SA for approval China Telecom Rel-18 Revised to S2-2207855.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207855 TS OR TR COVER Approval Cover sheet for 23.700-89 to TSG SA for approval China Telecom Rel-18 Revision of S2-2206955 OPEN
10.2 S2-2206956 TS OR TR COVER Approval Cover sheet for 23.700-60 to TSG SA for information China Mobile Rel-18 Revised to S2-2207856.
==== 9.X, 10.X Final Deadline ====
Dan (China Mobile) provides draft for TR coversheet of TR 23.700-60
Revised
10.2 S2-2207856 TS OR TR COVER Approval Cover sheet for 23.700-60 to TSG SA for information China Mobile Rel-18 Revision of S2-2206956 OPEN
10.2 S2-2206957 TS OR TR COVER Approval Cover sheet for 23.700-47 to TSG SA for information Huawei Rel-18 Revised to S2-2207857. LiMeng (Huawei) provides the initial draft.
Thomas (Nokia) suggest 70% completion ratio.
Robbie (Ericsson) agrees with Thomas (Nokia)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
LiMeng (Huawei) provides r01 as per the suggestions from Robbie and Thomas.
Revised
10.2 S2-2207857 TS OR TR COVER Approval Cover sheet for 23.700-47 to TSG SA for information Huawei Rel-18 Revision of S2-2206957 OPEN
10.2 S2-2206958 TS OR TR COVER Approval Cover sheet for 23.700-81 for information China Mobile Rel-18 Revised to S2-2207858.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207858 TS OR TR COVER Approval Cover sheet for 23.700-81 for information China Mobile Rel-18 Revision of S2-2206958 OPEN
10.2 S2-2206959 TS OR TR COVER Approval Cover sheet for 23.700-53 to TSG SA for information Motorola Rel-18 Revised to S2-2207859. Apostolis (Lenovo) provides the initial draft.
==== 9.X, 10.X Final Deadline ====
Apostolis (Lenovo) provides r01.
Revised
10.2 S2-2207859 TS OR TR COVER Approval Cover sheet for 23.700-53 to TSG SA for information Motorola Rel-18 Revision of S2-2206959 OPEN
10.2 S2-2206960 TS OR TR COVER Approval Cover sheet for 23.700-71 to TSG SA for information CATT Rel-18 Revised to S2-2207860.
==== 9.X, 10.X Final Deadline ====
CATT (Ming) provides the S2-2206960 into the CC#5 folder.
Revised
10.2 S2-2207860 TS OR TR COVER Approval Cover sheet for 23.700-71 to TSG SA for information CATT Rel-18 Revision of S2-2206960 OPEN
10.2 S2-2206961 TS OR TR COVER Approval Cover sheet for 23.700-62 to TSG SA for information China Mobile Rel-18 Revised to S2-2207861. Yan (China Mobile) provides the initial draft.
==== 9.X, 10.X Final Deadline ====
Fenqin (Huawei) provides r01.
Yan (China Mobile) provides r02 based on r01.
Revised
10.2 S2-2207861 TS OR TR COVER Approval Cover sheet for 23.700-62 to TSG SA for information China Mobile Rel-18 Revision of S2-2206961 OPEN
10.2 S2-2206962 TS OR TR COVER Approval Cover sheet for 23.700-80 to TSG SA for information OPPO, Samsung Rel-18 Revised to S2-2207862.
==== 9.X, 10.X Final Deadline ====
Revised
10.2 S2-2207862 TS OR TR COVER Approval Cover sheet for 23.700-80 to TSG SA for information OPPO, Samsung Rel-18 Revision of S2-2206962 OPEN
10.2 S2-2207863 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-17 to TSG SA#97 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205475 OPEN
10.2 S2-2208088 TS OR TR COVER Approval Cover sheet for 23.700-58 to TSG SA for information Qualcomm Rel-18
==== 9.X, 10.X Final Deadline ====
OPEN
10.2 S2-2208087 TS OR TR COVER Approval Cover sheet for 23.700-86 to TSG SA for information Xiaomi Rel-18 Sherry (Xiaomi) provides the initial draft. OPEN
10.3 - - - New Rel-18 Work Items - - Docs:=36 -
10.3 S2-2205482 WID NEW Approval New WID: support for 5WWC, Phase 2 Nokia, Nokia Shanghai Bell Rel-18 CC#5: r02 + changes agreed. Revised to S2-2207864. Sebastian (Qualcomm) comments
Laurent (Nokia): provides r01
Sebastian (Qualcomm) replies
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Laurent (Nokia): provides r02 (WID update per TR conclusion)
Sebastian (Qualcomm) confirms co-signature and comments
Sebastian (Qualcomm) confirms co-signature and comments on TNGF part
Sriram(CableLabs) comment.
Yildirim (Charter) confirms the support of the WID.
Revised
10.3 S2-2207864 WID NEW Approval New WID: support for 5WWC, Phase 2 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205482r02 + changes. CC#5: Approved Approved
10.3 S2-2205592 WID NEW Approval New WID on Extensions to the TSC Framework to support DetNet Ericsson Rel-18 CC#5: r01 agreed. Revised to S2-2207865. György (Ericsson) provides r01 with new supporting companies: Qualcomm, China Mobile, Lenovo, ,NTT DOCOMO, Nokia, Nokia Shanghai Bell, ZTE, Verizon UK Ltd, China Telecom, ETRI, Vivo
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207865 WID NEW Approval New WID on Extensions to the TSC Framework to support DetNet Ericsson Rel-18 Revision of S2-2205592r01. CC#5: Approved Approved
10.3 S2-2205644 WID NEW Approval New WID: 5G System Enabler for Service Function Chaining Intel Rel-18 CC#5: r05 + changes agreed. Revised to S2-2207866. Megha(Intel) provides r02
Laurent (Nokia): Comments, mandatory update
Megha(Intel) provides r01
Fenqin (Huawei): Comments and provides r03
Laurent (Nokia): answers. I insist to keep Note 2, which is also applicable to normative work (and does not harm)
Megha (Intel) provides comments
==== 9.X, 10.X Revisions Deadline ====
Megha (Intel) provides r03 in DRAFT and comments
Megha (Intel) provides r04 (not r03) and comments
==== 9.X, 10.X Final Deadline ====
Megha (Intel) provides r05 and comments
Laurent (Nokia): suggests to just refer to the TR conclusions as this skips some EN about metadata
Revised
10.3 S2-2207866 WID NEW Approval New WID: 5G System Enabler for Service Function Chaining Intel Rel-18 Revision of S2-2205644r05 + changes. CC#5: Approved Approved
10.3 S2-2205651 WID NEW Approval New WID: 5GS support of NR RedCap UE with long eDRX for RRC INACTIVE State Ericsson Rel-18 CC#5: r03 + changes agreed. Revised to S2-2207867. Hannu (Nokia) re-sends to correct the AI in the email title.
Qian (Ericsson) comments that the correct AI for this thread shall be AI#10.3.
Hannu (Nokia) provides revision r01 and co-signs.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Qian (Ericsson) provides draft revision based on the new tdoc for the WID (in DRAFTS folder)
Revised
10.3 S2-2207867 WID NEW Approval New WID: 5GS support of NR RedCap UE with long eDRX for RRC INACTIVE State Ericsson Rel-18 Revision of S2-2205651r03 + changes. CC#5: Approved Approved
10.3 S2-2205777 WID NEW Approval New WID: System architecture for Next Generation Real time Communication services China Mobile Rel-18 CC#5: r01 + changes agreed. Revised to S2-2207868. Rainer (Nokia) comments and proposes to postpone the WID.
Yi (China Mobile) replies and provides r01.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207868 WID NEW Approval New WID: System architecture for Next Generation Real time Communication services China Mobile Rel-18 Revision of S2-2205777r01 + changes. CC#5: Approved Approved
10.3 S2-2205806 WID NEW Agreement New WID: Enhanced support of Non-Public Networks Phase 2 Ericsson, Rel-18 CC#5: r01 + changes agreed. Revised to S2-2207869. Peter Hedman (Ericsson) provides r01 and asks whether there are supporting companies for normative WID for this partial work (until study concluded for other KIs)
Rainer (Nokia) is ok to remove KI#2 from the WI for the time being.
==== 9.X, 10.X Final Deadline ====
Peter Hedman (Ericsson) provides comments and ask for conformation of supporting companies
Fei (OPPO) comments on r01.
Peter Hedman (Ericsson) provides reply and added 23.502 as impacted
Fei (OPPO) responds to Peter
Saso (Intel) proposes to include the agreeable parts of KI#2; prefers r00
Saso (Intel) replies to the Rapporteur; still sees no reason why KI#2 is excluded from the WID.
Rainer (Nokia) replies
Saso (Intel) replies to the Rapporteur; points out that all the four ENs in 6558r17 refer to additional enhancements.
Peter Hedman (Ericsson) provided r01 in CC#5 folder that keeps KI#2
Saso (Intel) supports the updated r01.
Yildirim (Charter) supports the WID.
Revised
10.3 S2-2207869 WID NEW Agreement New WID: Enhanced support of Non-Public Networks Phase 2 Ericsson, Rel-18 Revision of S2-2205806r01 + changes. CC#5: Approved Approved
10.3 S2-2205981 WID NEW Approval New WID on Proximity-based Services in 5GS Phase 2 CATT, OPPO Rel-18 CC#5: Revised to S2-2207870. Hannu (Nokia) re-sends to correct the AI in the email title.
Hannu (Nokia) comments on the proposed WID
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207870 WID NEW Approval New WID on Proximity-based Services in 5GS Phase 2 CATT, OPPO Rel-18 Revision of S2-2205981. CC#5: Approved Approved
10.3 S2-2205987 WID NEW Approval New WID on 5G AM Policy China Telecom Rel-18 CC#5: r02 agreed. Revised to S2-2207871. Zhuoyi (China Telecom) is OK with r01
Judy (Ericsson) provides r01
Yildirim (Charter) supports the WID
Zhuoyi (China Telecom) provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207871 WID NEW Approval New WID on 5G AM Policy China Telecom Rel-18 Revision of S2-2205987r02. CC#5: Approved Approved
10.3 S2-2206087 WID NEW Approval New WID: Architectural enhancement for 5MBS_Ph2 Huawei, CBN Rel-18 Postponed Thomas (Nokia) provides comments
Suggest postponing this WID
Belen (Ericsson) provides comments
LiMeng (Huawei) agrees to postpone the WID to the next meeting.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Postponed
10.3 S2-2206286 WID NEW Approval New WID on Enhancement of support for Edge Computing in 5G Core Network phase 2 Huawei, HiSilicon Rel-18 Revised to S2-2207872. Magnus O (Ericsson) asks for clarification
Patrice (Huawei) answers Magnus that this depends if Puneet would accept updates to WIDs that of course have to be based on actual conclusions being agreed in the TR (in F2F, we would have concluded the Tdocs earlier, then the WID could then be presented in the next 'round' of discussion in the next session. This mechanism is not so easy when all documents have the same deadline).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Magnus (Ericsson) provides some comments
Laurent (Nokia): as we conclude the TR at next meeting, it is not mandatory to send the WID from this meeting, not a strong opinion though
Revised
10.3 S2-2207872 WID NEW Approval New WID on Enhancement of support for Edge Computing in 5G Core Network phase 2 Huawei, HiSilicon Rel-18 Revision of S2-2206286. CC#5: r01 + changes agreed. Revised to S2-2207890. Revised
10.3 S2-2207890 WID NEW Approval New WID on Enhancement of support for Edge Computing in 5G Core Network phase 2 Huawei, HiSilicon Rel-18 Revision of S2-2207872r01 + changes. CC#5: Approved Approved
10.3 S2-2206407 WID NEW Approval New WID: 5G System with Satellite Backhaul CATT Rel-18 CC#5: r01 + changes agreed. Revised to S2-2207873. Hannu (Nokia) comments on the proposed WID
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Hucheng (CATT) provides r01, responds to the comment, and asks for supporting company checking.
Hannu (Nokia) thanks for the other updates but explains why the EN in clause 4 is not appropriate.
Hucheng (CATT) provides the response and removes the EN.
Hannu (Nokia) thanks Hucheng for removing the EN and agrees that further work is still needed.
Revised
10.3 S2-2207873 WID NEW Approval New WID: 5G System with Satellite Backhaul CATT Rel-18 Revision of S2-2206407r01 + changes. CC#5: Approved Approved
10.3 S2-2206455 WID NEW Approval New WID: UPF enhancement for Exposure and SBA China Mobile Rel-18 CC#5: r01 + changes agreed. Revised to S2-2207874. Laurent (Nokia): Comments requiring mandatory changes
Fenqin (Huawei ): Comments and suggest do some changes.
Yan (China Mobile) provides r01.
Yan (China Mobile) provides r02 and ok with both r01 and r02.
==== 9.X, 10.X Revisions Deadline ====
Yoohwa (ETRI) agrees with r01 but objects to r02.
==== 9.X, 10.X Final Deadline ====
Yan (China Mobile) replies to Yoohwa (ETRI).
Yan (China Mobile) procides r03.
Yildirim (Charter) confirms support to the WID.
Revised
10.3 S2-2207874 WID NEW Approval New WID: UPF enhancement for Exposure and SBA China Mobile Rel-18 Revision of S2-2206455r01 + changes. CC#5: Approved Approved
10.3 S2-2206557 WID NEW Approval New WID on generic group management, exposure and communication enhancements Huawei, HiSilicon, Samsung Rel-18 r01 Revised to S2-2207875. CC#5: Noted and S2-2207875 was withdrawn Laurent (Nokia): Comments on mandatory changes
==== 9.X, 10.X Revisions Deadline ====
Qianghua (Huawei) replies
==== 9.X, 10.X Final Deadline ====
Qianghua (Huawei) provides r01
Noted
10.3 S2-2207875 WID NEW Approval New WID on generic group management, exposure and communication enhancements Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2206557r01. WITHDRAWN Withdrawn
10.3 S2-2206609 WID NEW Approval New WID: Seamless UE context recovery Samsung, Qualcomm, LG Electronics, Apple, KDDI, InterDigital Rel-18 Revised to S2-2207876.
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207876 WID NEW Approval New WID: Seamless UE context recovery Samsung, Qualcomm, LG Electronics, Apple, KDDI, InterDigital Rel-18 Revision of S2-2206609. CC#5: Approved Approved
10.3 S2-2206621 WID NEW Approval New WID on Enhancement to the 5GC LoCation Services Phase 3 CATT, Huawei Rel-18 cc#5: r01 agreed. Revised to S2-2207877.
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207877 WID NEW Approval New WID on Enhancement to the 5GC LoCation Services Phase 3 CATT, Huawei Rel-18 Revision of S2-2206621r01. CC#5: Approved CATT (Ming) provides revision of S2-2206621, i.e. S2-2207877 into the CC#5 folder. Approved
10.3 S2-2206664 WID NEW Approval WID on eNS_Ph3 ZTE, LG Electronics Rel-18 CC#5: r02 + changes agreed. Revised to S2-2207878. George Foti (Ericsson) provides r01. Another question do we need to address the new added objective separately in a TEI-18 or part of this work.
Jinguo(ZTE) provides r02
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Peter Hedman (Ericsson) provides comments, looking for the solution description for the objective
Jinguo(ZTE) provides r03 and response
Jinguo(ZTE) provides response and provide r04 to add TU.
Revised
10.3 S2-2207878 WID NEW Approval WID on eNS_Ph3 ZTE, LG Electronics Rel-18 Revision of S2-2206664r02 + changes. CC#5: Approved Approved
10.3 S2-2206755 WID NEW Approval New WID on Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Revised to S2-2207879.
==== 9.X, 10.X Final Deadline ====
Revised
10.3 S2-2207879 WID NEW Approval New WID on Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Revision of S2-2206755. CC#5: Approved Approved
10.3 S2-2205942 P-CR Approval 23.700-60: New WID on 5G Timing Resiliency and TSC & URLLC enhancements Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2207880. Shabnam (Ericsson) we will need to adjust the scope according to the Conclusions we can reach, which we will not know until potentially at CC#4/CC#5.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Shabnam (Ericsson) as current situation stands, the objectives related to timing resiliency is unfortunately not going to be ready for normative, I include the ones in comments we believe need to be removed from the WI and need further study work based on this meeting discussion.
Devaki (Nokia) comments and provides link to the latest DRAFT version (7880), happy to hear if your company wishes to support the WID.
Devaki (Nokia) provides r01 of 5942 (same technical content as DRAFT 7880) with additional supporting companies.
Revised
10.3 S2-2207880 WID new Approval New WID on 5G Timing Resiliency and TSC & URLLC enhancements Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2205942. CC#5: Approved Approved
10.4 - - - TEI18 WID proposals - - Docs:=108 -
10.4 - - - TEI18 proposal #1 - - Docs:=5 -
10.4 S2-2205471 WID NEW Approval Secondary DN Authentication and authorization in EPC IWK cases Nokia, Nokia Shanghai Bell, Orange, Vodafone Rel-18 Noted CC#5: r02 agreed. Revised to S2-2207885. Stefan (Ericsson) provides comments
Myungjune (LGE) asks question on scope.
Fei (OPPO) comments
Laurent (Nokia): answers
Laurent (Nokia): provides r01
Fei (OPPO) comments on r00 and r01.
Chia-Lin (MediaTek) provides comments and have concerns on this proposal
Laurent (Nokia): provides r02
==== 9.X, 10.X Revisions Deadline ====
Chia-Lin (MediaTek) consider we cannot be always to align EPS with 5GS.
Stefan (Ericsson) supports the WID
==== 9.X, 10.X Final Deadline ====
Revised
10.4 S2-2207885 WID NEW Approval Secondary DN Authentication and authorization in EPC IWK cases Nokia, Nokia Shanghai Bell, Orange, Vodafone Rel-18 Revision of S2-2205471r02. Approved Approved
10.4 S2-2205474 DISCUSSION Information Secondary DN Authentication in EPC case: an introduction Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205472 DRAFTCR Information Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205473 DRAFTCR Information Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #2 - - Docs:=7 -
10.4 S2-2205496 WID NEW Approval WID: TEI18_SLAMUP Spending Limits for AM and UE Policies in the 5GC Oracle Corporation, Verizon UK Ltd, OPPO Rel-18 r02 Revised to S2-2207832. Haiyang (Huawei) comments
Uri (Oracle) replies to the comments from Haiyang (Huawei)
Hong (Qualcomm) comments.
Uri (Oracle) responds to the comments from Hong (Qualcomm).
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.4 S2-2207832 WID NEW Approval WID: TEI18_SLAMUP Spending Limits for AM and UE Policies in the 5GC Oracle Corporation, Verizon UK Ltd, OPPO Rel-18 Revision of S2-2205496r02. Approved Approved
10.4 S2-2205497 DISCUSSION Information Discussion on the use of Spending Limits for AM and UE Policies Oracle Corporation, Verizon UK Ltd, OPPO Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205498 DRAFTCR Information 23.501 Spending Limits for AM and UE Policies in the 5GC Verizon UK Ltd, Oracle Corporation, Ericsson, OPPO Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205499 DRAFTCR Information 23.503 Spending Limits for AM and UE Policies in the 5GC Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205500 DRAFTCR Information 23.502 Spending Limits for UE Policies in the 5GC Oracle, Verizon UK Ltd, Ericsson, OPPO Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206569 DRAFTCR Information Spending Limits for AM Policies in the 5GC Huawei, Oracle, Verizon UK Ltd, Ericsson Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #3 - - Docs:=4 -
10.4 S2-2205579 WID NEW Approval New WID: TEI18_QUPSEC Per-QoS Flow user plane security control Intel Rel-18 Noted Saso (Intel) provides r01 to include the TU estimation.
Jinsook (DISH) ask a clarification
Saso (Intel) replies.
Zhenhua (vivo) asks for clarification
Laurent (Nokia): answers
Zhenhua (vivo): asks for clarification
Saso (Intel) replies to Zhenhua (vivo)
Chunhui(Xiaomi) asks a question for the clarification about the relationship between this WID and the existing Full data rate user plane integrity protection.
Chunhui (Xiaomi) comments.
Dieter (Deutsche Telekom) expresses concerns with this WID proposal. As it is security related we insist that it have to be handled in SA3 first.
Chunhui (Xiaomi) express concerns to the use case and comments that SA1 should take the lead on this.
Ellen (Google) comments
Youngkyo(Samsung) share the view with Jinsook (DISH).
Jinsook (DISH) we're interested in this proposal, and some suggestions
Stefan (Ericsson) expresses concerns and comments that SA3 should take the lead on this
Wanqiang (Huawei) express concerns on the concept and questions the value.
Jinguo(ZTE) provides comments
Jinsook (DISH) Question for clarification and conditional support
Zhuoyi (China Telecom) provides comments.
Haris(Qualcomm) expresses concerns
Saso (Intel) replies to Jinguo, Jinsook, Zhuoyi, Haris.
Jinsook (DISH) replied to Saso
Chia-Lin (MediaTek) also has concerns on this WID
Stefan (Ericsson) repeats concerns and provides comments
Saso (Intel) replies to Chia-Lin and Stefan.
Haris(Qualcomm) indicates the issue with Reflective QoS
Chia-Lin (MediaTek) responds to Saso (Intel)
Saso (Intel) replies to Chia-Lin.
Wanqiang (Huawei) repeats the concern and not convinced the value of the work.
Saso (Intel) replies to Haris.
Saso (Intel) replies to Wanqiang (Huawei).
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) responds
Haris(Qualcomm) object to the WID as works starting from SA2
Dieter (Deutsche Telekom) objects to the WID.
Saso (Intel) replies to Haris and Dieter; notes that objections on the ground that this work should be initiated in SA3 are not justified.
Stefan (Ericsson) objects to the WID
Laurent (Nokia): Same comment as Saso : objections on the ground that this work should be initiated in SA3 are not justified
Chunhui (Xiaomi) objects to the WID.
==== 9.X, 10.X Final Deadline ====
Haris(Qualcomm) responds that per PDU session security policy granularity was decided by SA3
Saso (Intel) replies to Haris (Qualcomm) that nowhere in the SA3 LS is it implied that SA3 had made a decision on the granularity. The LS clearly states: 'In addition, SA3 understands that user plane security policy can be statically configured in SMF or downloaded dynamically during PDU session setup.'
Noted
10.4 S2-2205580 DRAFTCR Information Per-QoS Flow User Plane security control Intel Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205581 DRAFTCR Information Per-QoS Flow User Plane security control Intel Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205582 DRAFTCR Information Per-QoS Flow User Plane security control Intel Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #4 - - Docs:=5 -
10.4 S2-2205690 WID NEW Approval New WID: MBS support for V2X services (TEI18_MBS4V2X) LG Electronics Rel-18 r02 agreed. Revised to S2-2207831. LaeYoung (LGE) thanks to Shabnam (Ericsson) about co-sign and provides r01.
Shabnam (Ericsson) Please add Ericsson as supporting company, if a revision is created.
LaeYoung (LGE) provides r02.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.4 S2-2207831 WID NEW Approval New WID: MBS support for V2X services (TEI18_MBS4V2X) LG Electronics Rel-18 Revision of S2-2205690r02. Approved Approved
10.4 S2-2205689 DISCUSSION Discussion Discussion for TEI18 WID proposal on MBS support for V2X services LG Electronics Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205691 DRAFTCR Information MBS support for V2X services LG Electronics, Tencent, Tencent Cloud Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205692 DRAFTCR Information 5QI for V2X message delivery via MBS LG Electronics, Tencent, Tencent Cloud Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #5 - - Docs:=4 -
10.4 S2-2205695 WID NEW Approval New WID: TEI18_5IOPS Isolated Operation for Public Safety in 5G System (5IOPS). Huawei, HiSilicon Rel-18 Noted Chris (Vodafone) questions how the SUCI (c.f. encrypted IMSI) issue is solved.
Ihab [FirstNet] Add 'FirstNet' as a supporting company
Haiyang (Huawei) replies to Chris (Vodafone).
Haiyang (Huawei) provides r01 to add more supporting company
Chris (Vodafone) thanks Huawei for the explanation
alessio(Nokia) comments that this work should require some study for 5GS as it is not clear the copy of EPS would work fine. As a potential stopgap for urgent needs the adoption of SNPN scheme on surface could help as LG proposed at last meeting (in this end this is case of a SNPN which can be accessed with specific credentials for the SNPN).
Josep (DT) expresses concerns to target TEI18 for specifying IOPS for 5G.
Shabnam (Ericsson) This work requires some study in the context of 5GS and features that have been enabled such as slice, SBA as well as new Rel-18 features that may be available. As such, we believe it is not possible to do a TEI18 but need to have a study first.
Haiyang (Huawei) provides feedback
Hugh (AT&T) asks question for clarifications
Haiyang (Huawei) clarifies to Hugh (AT&T)
Hugh (AT&T) agrees with others that more study is needed, hence may not be suitable for TEI18.
Shabnam (Ericsson) comments to Huawei that we don't know what we use to solve since you propose to copy EPS with informative Annex. That is why we need a study to see what 5G can provide and potentially better. We understand that database (HSS) potentially an issue for EPS.
Haiyang (Huawei) seeks for clarification from Hugh (AT&T) and Shabnam (Ericsson)
Josep (DT) comments that a solution based on the proposed CRs equates to no normative work, contradicting the SID justification.
Hugh (AT&T) provides reply
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) Objects to this WI, the work requires first some study as already stated, to comply/apply 5GS architecture and it is not one to one mapping, comments.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205694 DISCUSSION Agreement Discussion on the Isolated Operation for Public Safety in 5GS Huawei, HiSilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205696 DRAFTCR Information Implementation and deployment guildlines of the Isolated Operation for Public Safety in 5GS (5IOPS) Huawei, Hisilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205697 DRAFTCR Information Procedures of the Isolated Operation for Public Safety in 5GS (5IOPS) Huawei, Hisilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #6 - - Docs:=3 -
10.4 S2-2205781 WID NEW Approval New WID: Support of EPLMN list per UE China Mobile Rel-18 Noted Lalith(Samsung) provides comments
Jianning (Xiaomi) provide questions for clarification
Hannu (Nokia) thinks r01 is a good clarification and asks further questions to understand what is being proposed.
Haris(Qualcomm) indicates concerns and remain unconvinced on the need
Qian (Ericsson) provides comments.
Yi (China Mobile) replies and provides r02.
Hannu (Nokia) comments on r02.
Yi (China Mobile) replies to Hannu.
==== 9.X, 10.X Revisions Deadline ====
Qian (Ericsson) provides comments on r02.
Haris(Qualcomm) objects to the WI
Hannu (Nokia) comments that falling back to r02 does not solve the open questions that have been asked.
Antoine (Orange) agrees with Hanni and Haris and objects to r00, r01 and r02.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205782 DRAFTCR Endorsement Support of EPLMN list per UE China Mobile Rel-18 Noted Hannu (Nokia) comments that the serving AMF role in the VPLMN must be clarified as commented on the WID in S2-2205781.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205783 DRAFTCR Endorsement Support of EPLMN list per UE China Mobile Rel-18 Noted Hannu (Nokia) comments that the same clarification of serving AMF role in the VPLMN as in S2-2205781 and S2-2205782 applies also on this document.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #7 - - Docs:=0 -
10.4 - - - TEI18 proposal #8 - - Docs:=3 -
10.4 S2-2205790 WID NEW Approval New TEI18 WID: URSP rule enhancements for advanced non-3GPP access selection (TEI18_URSP_n3A) Lenovo Rel-18 Noted Dimitris (Lenovo) provides r01
Huazhang (vivo) comments
Dimitris (Lenovo) replies to Vivo
Yishan (Huawei) asks for clarification
Dimitris (Lenovo) responds to Huawei
Mike (InterDigital) supports the WID
Myungjune (LGE) comments.
Hong (Qualcomm) comments.
Jinguo(ZTE) provides comments
Chia-Lin (MediaTek) provides comments
Huazhang (vivo) replies to Dimitris (Lenove)
Belen (Ericsson) asks whether the UE can connect to different SSID simultaneously.
Yang (OPPO) agrees with previous comments about the UE complication
Dimitris (Lenovo) provides r02 adding InterDigital as supporter and addressing comments
Dimitris (Lenovo) responds to Jinguo
Jianning (Xiaomi) provides questions for clarification
Belen (Ericsson) asks questions for clarification
Marco (Huawei) comments and ask question on Untrusted/Trusted difference
Dimitris (Lenovo) responds to Marco (Huawei)
Jianning (Xiaomi) provide comment
Belen (Ericsson) replies to Lenovo, thinks that 0.5 TU is underestimated.
Marco (Huawei) further comments and express concerns on the benefit of the TEI18 in respect the drawback and possible dependency to ATSSS R18 normative work
Dimitris (Lenovo) responds to Belen
Dimitris (Lenovo) provides r03
Krisztian (Apple) shares the concerns raised in this thread.
Yildirim (Charter) supports r03 of the WID.
Dimitris (Lenovo) clarifies that the dependency of a PDU session to WLAN selection is removed in r03
Dimitris (Lenovo) provides r04 adding Charter Communications as a supporting company
==== 9.X, 10.X Revisions Deadline ====
Hong (Qualcomm) comments on r04 and r03 and cannot accept them.
Krisztian (Apple) agrees with Hong and cannot accept any of the revisions.
Changhong (Intel) agrees with Hong and Krisztian.
Chia-Lin (MediaTek) cannot accept any version including the original one
Jinguo(ZTE) shares the view from Chia-Lin (MediaTek),Krisztian (Apple) and Hong (Qualcomm)
Susana (Vodafone) agrees more discussion is needed before approving this TEI18 WID
Dimitris (Lenovo) responds to concerns raised
DongYeon (Samsung) shares the view from ZTE, MediaTek, Apple, and Qualcomm.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205807 DISCUSSION Endorsement Discussion TEI18: URSP rule enhancements for advanced non-3GPP access selection Lenovo Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205817 DISCUSSION Information Draft CR on URSP rule enhancements for advanced non-3GPP access selection Lenovo Rel-18 Noted Dimitris (Lenovo) provides r01 based on the changes in the WID description
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #9 - - Docs:=4 -
10.4 S2-2205814 WID NEW Approval Multiple location report for MT-LR Immediate Location Request for the regulatory service Ericsson, T-Mobile USA Rel-18 r02 Revised to S2-2207833. Cai Simon (Nokia) confirms the support
==== 9.X, 10.X Final Deadline ====

Cheers,
LaeYoung


From: 3GPP_TSG_SA_WG2_EMEET [mailto:3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG] On Behalf Of Antoine G Mouquet
Sent: Friday, August 26, 2022 5:52 PM
To: 3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG
Subject: Re: [SA2#152E, AI#10.4, S2-2205814] New WID: Multiple location report for MT-LR Immediate Location Request for the regulatory service

Hello,

Seems like the below comments have not been recorded in the Chair's Note and r00 was marked for approval.
Also there's a r02 in the Revisions folder but I don't have a corresponding email.


BR,

Antoine


Orange Restricted
De : 3GPP_TSG_SA_WG2_EMEET <3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG > De la part de Richárd Bátorfi
Envoyé : mercredi 24 août 2022 13:27
À : 3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG
Objet : Re: [SA2#152E, AI#10.4, S2-2205814] New WID: Multiple location report for MT-LR Immediate Location Request for the regulatory service

Comment for notes
Revised
10.4 S2-2207833 WID NEW Approval Multiple location report for MT-LR Immediate Location Request for the regulatory service Ericsson, T-Mobile USA Rel-18 Revision of S2-2205814r02. Approved Approved
10.4 S2-2205815 DISCUSSION Agreement Multiple location report for MT-LR Immediate Location Request for the regulatory service Ericsson, T-Mobile USA Rel-18 Noted Cai Simon (Nokia) advises to NOTE the paper
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205816 DISCUSSION Endorsement Multiple location report for MT-LR Immediate Location Request for the regulatory service Ericsson, T-Mobile USA, Verizon ???, AT&T ??? Rel-18 Confirm Sources! Noted Cai Simon (Nokia) asks questions
Hank (vivo) asks questions.
Stephen (Qualcomm) comments
Richard (Ericsson) answering questions from Nokia, Vivo, and Qualcomm
Stephen (Qualcomm) responds to answers from Richard (Ericsson)
Richard (Ericsson) providing r01 and r02
Hank (vivo) comments on r01.
Richard (Ericsson) providing r03
Yunjing (CATT) provides comments.
Cai Simon (Nokia) provides more comments
Richard (Ericsson) answering to CATT and Nokia and providing r04
Cai Simon (Nokia) provides further comments
Richard (Ericsson) answering to Nokia
Cai Simon (Nokia) supports WID of the DP, advise to NOTE this DP
Cai Simon (Nokia) shows the inconsistencies in DP
==== 9.X, 10.X Revisions Deadline ====
Cai Simon (Nokia) advises to NOTE the paper
Stephen (Qualcomm) comments again
Sherry (Xiaomi) comments.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #10 - - Docs:=3 -
10.4 S2-2205874 WID NEW Approval TEI18 WID on 5G VN group multicast service management based on network-v6 China Mobile, China Electric Power Research Institute, China Southern Power Grid Co., Ltd Noted Laurent (Nokia): Comments(questions)
Sebastian (Qualcomm) comments
Stefan (Ericsson) provides comments
Qianghua (Huawei) provides drafts and comments
zhendong (ZTE) comments
Qianghua (Huawei) responds to Zhendong
Aihua(CMCC) provides r01 in revision folder.
Qianghua (Huawei) provides responses to Stefan
Aihua(CMCC) replies and kindly asks Laurent(Nokia) to elaborate the question if any.
Stefan (Ericsson) replies to Qianghua
==== 9.X, 10.X Revisions Deadline ====
Qianghua (Huawei) replies
Aihua(CMCC) replies to Laurent and Stefan.
Stefan (Ericsson) expresses concerns and proposes to note
Laurent (Nokia): objection to R00 and R01. Comments/questions and concerns with R02; (still evaluating objection)
Laurent (Nokia): objects also to R02
Stefan (Ericsson) objects to any revision
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205882 WID NEW Approval TEI18 CR on 5G VN group multicast service management based on network in TS 23.502-v2 China Mobile Rel-18 Noted Sebastian (Qualcomm) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205886 WID NEW Approval TEI18 CR on 5G VN group multicast service management based on network in TS 23.501 China Mobile Rel-18 Noted Sebastian (Qualcomm) proposes to postpone
Qianghua (Huawei) provides r01 for information
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #11 - - Docs:=2 -
10.4 S2-2205880 WID NEW Agreement New WID: Enhancements to usage of Target NSSAI Ericsson Rel-18 Noted alessio(Nokia) provides comments and suggests to consider the alternate proposal by nokia.
Haiyang(Huawei) comments
Peter Hedman (Ericsson) provides reply to Nokia and informs that the related DP includes already the scenarios discussed by Nokia DP i.e. proposed WID has taken into account the scenario and proposes the simplest solutions forward that also work i.e. reasonable for TEI18
Peter Hedman (Ericsson) provides reply to Huawei
Alessio(Nokia) comments
Peter Hedman (Ericsson) provides comments
Jinguo(ZTE) provides comments
Yildirim (Charter) supports the WID.
Genadi (Lenovo) supports the WID.
Alessio(nokia) provides comments and r01 so we can move forward with this.
Peter Hedman (Ericsson) provides r02
==== 9.X, 10.X Revisions Deadline ====
alessio(Nokia) can accept r01 with the compromise on just two alternative target NSSAIs (I can revise) . cannot live with delegating to RAN WG the choice on indication to RAN as this is due to text in sA2 specs. Also the justification clause is not complete and is stating that the RAN today stores the Target NSSAI already which is not what the spec says. so we want to use our justification clause that is referring to text in the specification and not a drawing indicating the only issue is inter-gnb transfer as basis of work. see the link in drafts here below for what we propose.
Jinguo(ZTE) supports this WID and is ok with r02.
Peter Hedman (Ericsson) provides comments and suggests to go with r02 as there is no need to have a very huge justification clause
Alessio(Nokia) cannot live with r02 and at this stage proposes to add target NSSAI enhancements as a topic for rel-19. we cannot continue with random updates to our specs with no good thought based on panic approach. Target NSSAI needs significant work and includes priority handling so we cannot accept partial enhancements.
Peter Hedman (Ericsson) provides comments that main scenario for supporting e.g. factory slices is to allow RAN to store the Target NSSAI and also to allow the Target NSSAI to be provided at HO, other aspects are additional enhancements or clarifications that can be handled separately including clarifications on how Target NSSAI is determined.
Haiyang (Huawei) is ok with r02, cannot accept r01.
Alessio(nokia) clarifies that there is a fundamental issue with Target NSSAI before we do the fine gain work of this SID that is HOW to determine it deterministically and in a scalable manner. Ericsson blocks this so until we do not resolve this all the rest is irrelevant as we cannot properly determine the target NSSAI and the workarounds proposed invalidate some of the proposed solutions in this TEI-18. So we shall do a proper study on target NSSAI enhancements that is holistic and not a partial solution to point issues that may be wrongly resolved if we do not do proper study
Omkar (CableLabs) supports the WID.
alessio (nokia ) comments
Peter Hedman (Ericsson) provides comment that for figure 3 the WID and CR includes a solution
==== 9.X, 10.X Final Deadline ====
Alessio (nokia) quotes the solution Peter Hedman (Ericsson) provides to determine target NSSAI and shows it is problematic wrt proposed solutions to use cases, shows a study is needed if the target NSSAI cannot be scalably based on priority setting of slices.
Peter Hedman (Ericsson) provides reply why the proposed solution works for the mentioned scenario, but it is ok for Ericsson to keep the scope of the TEI18 work limited to 1) RAN storage logic of Target NSSAI and 2) allowing Target NSSAI to be received by target NG-RAN at HO
And draft r03 as to show a compromise.
Alessio(Nokia) wonders how is it possible that storing a wrongly selected target NSSAI that causes the issues identified can be good (in fact it may be worse than what we have as the UE is sent to the wrong band and forced to use the wrong S-NSSAI). This TEI work is already noted and we do not agree to further discuss it. a Study is required to define the long term solution for this. This: 'Then we can hopefully continue separate discussions on the Target NSSAI selection' is not acceptable to us .
Peter Hedman (Ericsson) I understand you object, but there seems at least now not be a technical reasoning as the WID is scoped to only cover aspects that are separated from what is debated i.e. objection is for other reasons than technical it seems.
Noted
10.4 S2-2205881 DISCUSSION Agreement Discussion on possible Target NSSAI enhancements Ericsson Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #12 - - Docs:=3 -
10.4 S2-2205893 WID NEW Agreement Discovery and Selection of Target NF in Target PLMN Nokia, Nokia Shanghai Bell (Rapporteur) Rel-18 Noted Fenqin (Huawei) provides comments
Magnus H (Ericsson) suggest to study this for rel-19
Thomas (Nokia) replies to Fenqin and Magnus
Fenqin (Huawei) responds
Thomas (Nokia) replies to Fenqin (Huawei)
Magnus H (Ericsson) still suggests to study this for rel-19
Thomas (Nokia) replies to Magnus
Josep (DT) expresses some concern to add further features to 5G roaming at this point.
Thomas(Nokia) replies to Josep.
Josep (DT) replies to Thomas (Nokia).
Thomas (Nokia) replies to Josep
==== 9.X, 10.X Revisions Deadline ====
Magnus H (Ericsson) objects to this WID and proposes to study the identified problem in rel-19
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205894 DRAFTCR Information NF discovery and selection by target PLMN Nokia, Nokia Shanghai-Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205895 DRAFTCR Information NF discovery and selection by target PLMN Nokia, Nokia Shanghai-Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #13 - - Docs:=4 -
10.4 S2-2205969 WID NEW Approval New WID: Cell based LADN (TEI18_CLADN) LG Electronics Rel-18 Revision of (Postponed) of S2-2204020. Noted Fei (OPPO) asks questions.
Yishan (Huawei) asks questions
Chia-Lin (MediaTek) provides comments
Myungjune (LGE) replies to Stefano (Qualcomm)
Stefano (Myungjune) replies to Myungjune (LGE)
Stefano (Qualcomm) question for clarification
Myungjune (LGE) replies to Chia-Lin (MediaTek)
Myungjune (LGE) replies to Yishan (Huawei)
Myungjune (LGE) replies to Fei (OPPO).
Chia-Lin (MediaTek) responds to Myungjune (LGE)
Stefan (Ericsson) comments
Myungjune (LGE) replies to Stefan (Ericsson)
Myungjune (LGE) responses to Chia-Lin (MediaTek)
Myungjune (LGE) replies to Jinguo (ZTE)
Jinguo(ZTE) express concerns on this WID proposal and provides comments
Wonjung (LG Uplus) supports the WID.
Laurent (Nokia): Comments
Myungjune (LGE) responses Stefan (Ericsson)
Myungjune (LGE) replies to Laurent (Nokia)
Stefan (Ericsson) replies to Myungjune
Dieter (Deutsche Telekom) provides comments
Laurent (Nokia): answers
Myungjune (LGE) responses to Fei (OPPO).
Fei (OPPO) provides comments.
Sungpyo (KT Corporation) provides comments
Myungjune (LGE) replies to Laurent (Nokia) and provides r01.
Fei (OPPO) replied to Myungjune.
Fei (OPPO) provides replies to Myungjune
Myungjune (LGE) replies to Fei (OPPO) .
Myungjune (LGE) replies to Stefan (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
Changhong (Intel) comments .
Myungjune (LGE) replies to Changhong (intel).
Dieter (Deutsche Telekom): now all issues are touched and clarified - we still support this WID.
Fei (OPPO) thanks for clarication and can live with it.
Laurent (Nokia): Shares Fei issues and thinks further on how to react
Chia-Lin (MediaTek) objects to any revision and the original one
Antoine (Orange) proposes to agree r01.
Myungjune (LGE) proposes agree r01, replies to Chia-Lin (MediaTek)
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205968 DISCUSSION Discussion Discussion for TEI18 WID proposal on cell based LADN LG Electronics Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205970 DRAFTCR Information Support of cell based LADN LG Electronics Rel-18 Noted Stefano (Qualcomm) provides R01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2205971 DRAFTCR Information Support of cell based LADN LG Electronics Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #14 - - Docs:=3 -
10.4 S2-2206003 WID NEW Approval NSSRG in EPS Samsung, Nokia, Nokia Shanghai Bell, Interdigital, LG Uplus Rel-18 Noted Guillaume (MediaTek Inc.) asks for clarification
Ashok (Samsung) clarifies Guillaume (MediaTek Inc.)
Guillaume (MediaTek Inc.) replies to Ashok (Samsung)
Jinguo(ZTE) provides comments
Ashok (Samsung) provides r01
Fenqin (Huawei) provides comments.
Ashok (Samsung) comments
Fenqin (Huawei) provides further comments.
Ashok (Samsung) responds
Peter Hedman (Ericsson) provides comments
Antoine (Orange) asks for a reference to the GSMA requirement that is mentionned to justify this proposal.
==== 9.X, 10.X Revisions Deadline ====
Antoine (Orange) does not agree that the proposed work is required.
Alessio(Nokia) observes that it is exactly the opposite of what Antoine said as it is a service based requirement that drives NSSRG not any network constraint. I know as I wrote the GSMA attibute. so based on Antoine comment this work is needed.
Antoine (Orange): replies: no requirement for restricting services in EPS.
alessio(Nokia) comment is that restricting services in EPS should mirror the restriction in 5GS as otherwise the policy reasons that introduced the NSSRG are immediately lost upon EPS mobility as the connectivity of incompatible slcies can be enjoyed in EPS
Kundan (NEC) provides comment that EPS handling is needed in terms of NSSRG when the PDN connections are being estbblished.
Peter Hedman (Ericsson) provides comments and sympathy with Ornage that GSMA reference does not require restrictions to be applied in EPS
Ashok (Samsung) responds to Kundan (NEC) Peter Hedman (Ericsson)
Dieter (Deutsche Telekom): we agree with Orange and Ericsson that GSMA reference does not require restrictions to be applied in EPS.
Alessio(Nokia) makes the general comment that GSMA NG.116 does not require even the support of PDN connections associated to a slice to be handed over to EPS or be established in EPS but 3GPP can support this (and we do). 3GPP can receive requirements from GSMA to start work but is NOT limited by GSMA requirements absence to do work. so the argument provided is just artificial. the converse is true also. GSMA is not limited to produce requirements that are not yet supported in 3GPP.
Jinguo(ZTE) believes the NSSRG concept in this WID is different with NSSRG in 5GS, therefore it is better to have dedicated study.
Ashok (Samsung) responds to Jinguo(ZTE)
Jinguo(ZTE) provides further comments
Antoine (Orange) replies.
Ashok (Samsung) responds to Antoine (Orange) replies.
Ashok (Samsung) gives update
Antoine (Orange) further replies.
Ashok (Samsung) replies to Peter Hedman (Ericsson)
Ashok (Samsung) thanks for the response to Antoine (Orange)
Antoine (Orange) objects to r00, r01 and r02.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206009 DRAFTCR Information NSSRG in EPS Samsung, Nokia, Nokia Shanghai Bell, Xiaomi Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206010 DISCUSSION Agreement Discussion on the need for NSSRG in EPS Samsung Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #15 - - Docs:=3 -
10.4 S2-2206026 WID NEW Decision New WID: Handling legacy UE in UAM LG Uplus, KT, SKT, ETRI Rel-18 Noted Pallab (Nokia) asks questions and requests for clarification
Runze (Huawei) supports the TEI proposal and provides clarification.
Stefano (Qualcomm) comments and expresses a concern.
Jinguo(ZTE) provides comments
Jungshin (Samsung) provides comments.
Yali (OPPO) asks question.
Shabnam (Ericsson) asks if it is really TEI18 type work as we do need some investigation and also if we should do anything before RAN completes their work in Rel-18?
Jaehyun (LG Uplus) response questions with r01 to Pallab (Nokia).
Jaehyun (LG Uplus) response to Runze (Huawei) with r01.
Jaehyun (LG Uplus) response to Stefano (Qualcomm).
Jaehyun (LG Uplus) responses to Jinguo(ZTE) with r01.
Jaehyun (LG Uplus) responses to Jungshin (Samsung) with r01.
Jaehyun (LG Uplus) responses to Yali (OPPO) with r01.
Jaehyun (LG Uplus) responses to Shabnam (Ericsson) with r01.
Jinsook (DISH) Comment
Shabnam (Ericsson) comments and states additionally that RAN is impacted and thus we need cross TSG agreement?
Jinguo(ZTE) agree with Shabnam(Ericsson)
Zhuoyi (China Telecom) agrees the TEI has impact to RAN and ask further question.
Jungshin (Samsung) agrees with companies' views on RAN impact and propose cross-WG alignment to clarify the work scope.
Jaehyun (LG Uplus) responses to Jinsook (DISH).
Jaehyun (LG Uplus) responses to Jungshin (Samsung). RAN UAV WI considers a UE with UAV capability. A UE without UAV capability is not in the scope of RAN UAV WI.
Jaehyun (LG Uplus) responses to Shabnam (Ericsson), Jinguo(ZTE), and Zhuoyi (China Telecom).
Sudeep (Apple) agrees with the views from Samsung and others on the alignment with RAN.
==== 9.X, 10.X Revisions Deadline ====
Jaehyun (LG Uplus) askes to send LS to be aligned with RAN3 WG since many companies want to hear the opinion of RAN3 WG.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206024 DISCUSSION Decision Handling legacy UE in UAM LG Uplus, KT, SKT, ETRI Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206028 DRAFTCR Information Draft CR: Handling legacy UE in UAM LG Uplus, KT, SKT, ETRI Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #16 - - Docs:=4 -
10.4 S2-2206090 WID NEW Approval New WID: 5GC supporting untrusted Non-3GPP Satellite Access Network Xiaomi, China Mobile, MATRIXX Software, vivo Rel-18 Noted Anindya Saha (Saankhya Labs) supports the proposal and responds to Chunhui (Xiaomi).
Chunhui (Xiaomi) thanks the support from Pranav (IIT Bombay).
Chunhui(Xiaomi) responds to Guillaume (MediaTek Inc.).
Guillaume (MediaTek Inc.) objects to the proposal
Saso (Intel) seeks clarification on how RAT type is determined.
DongYeon (Samsung) asks a question for clarification.
Chunhui(Xiaomi) responds to Saso (Intel) about how & why RAT type is determined.
Saso (Intel) replies and proposes to NOTE the proposal.
Chunhui(Xiaomi) responds to Saso (Intel) and clarifies.
Chunhui(Xiaomi) replies DongYeon (Samsung).
Chunhui(Xiaomi) provides comments about why 3GPP should consider Non-3GPP Satellite access to 5GC.
Saso (Intel) replies to Chunhui.
Chunhui(Xiaomi) replies Saso (Intel) that the stage2 WID & CR for Non-3GPP Satellite are needed for the stage3 CR.
Chunhui(Xiaomi) replies Saso (Intel).
Dieter (Deutsche Telekom) provides comments
Marco (Huawei) provide comments to Chunhui(Xiaomi) provides comments about why 3GPP should consider Non-3GPP Satellite access to 5GC.
Marco (Huawei) provides comments
Chunhui(Xiaomi) replies Marco (Huawei).
Chunhui(Xiaomi) replies Marco (Huawei) about the RAT Type determination.
Chunhui(Xiaomi) replies Dieter (Deutsche Telekom).
Stefan (Ericsson) provides comments
Chunhui(Xiaomi) replies Stefan (Ericsson)' comments and asks for clarification.
Marco (Huawei) replay to Chunhui(Xiaomi)
Guillaume (MediaTek Inc.) replies to Chunhui (Xiamoi)
Hannu (Nokia) shares the concerns of Guillaume (MediaTek).
Chunhui (Xiaomi) provides TEI18 WID and 23501CR revisions r01 without new RAT type.
Guillaume (MediaTek Inc.) replies to Chunhui (Xiaomi) and suggests a possible WF.
Saso (Intel) notes that what is left in r01 is only a definition of 'Untrusted Non 3GPP Satellite Access Network' with no normative work. Proposes to note.
Chunhui (Xiaomi) thanks Guillaume (MediaTek Inc.) WF suggestion and provides r02.
Chunhui (Xiaomi) provides r02 of WID and 501CR.
Marco (Huawei) considering CR S2-2206099r02 to 501, with no normative work the WID can be noted
Haris(Qualcomm) indicates that the WI possibly does more harm than good
Chunhui(Xiaomi) replies Haris(Qualcomm) and Marco(Huawei).
Chunhui (Xiaomi) proposes to move forward with the compromised WID/CR r02.
Hannu (Nokia) comments
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) objects to the WI (all revisions)
DongYeon (Samsung) comments.
Stefan (Ericsson) proposes to NOTE
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206074 DISCUSSION Discussion Discussion for TEI18 WID proposal on 5GC supporting untrusted Non-3GPP Satellite Access Network Xiaomi Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206099 DRAFTCR Information Untrusted Non-3GPP Satellite access to 5GC Xiaomi Rel-18 Noted Guillaume (MediaTek Inc.) objects to this draft CR.
Chunhui(Xiaomi) responds to Guillaume (MediaTek Inc.) and suggests converging the further discussion in the TEI18 WID(S2-2206090) thread.
Chunhui (Xiaomi) provides TEI18 WID and 23501CR revisions r01 without new RAT type.
Guillaume (MediaTek Inc.) replies to Chunhui (Xiaomi) and suggests a possible WF.
Chunhui (Xiaomi) thanks Guillaume (MediaTek Inc.) WF suggestion and provides r02.
Haris(Qualcomm) indicates that the WI possibly does more harm than good
Chunhui(Xiaomi) replies Haris(Qualcomm) and Marco(Huawei).
Hannu (Nokia) comments
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) objects to the WI (all revisions)
DongYeon (Samsung) comments.
Stefan (Ericsson) proposes to NOTE
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206104 DRAFTCR Information Untrusted Non-3GPP Satellite access to 5GC Xiaomi Rel-18 Noted Chunhui (Xiaomi) provides TEI18 WID and 23501CR revisions r01 without new RAT type.
Guillaume (MediaTek Inc.) replies to Chunhui (Xiaomi) and suggests a possible WF.
Chunhui (Xiaomi) thanks Guillaume (MediaTek Inc.) WF suggestion and provides r02.
Haris(Qualcomm) indicates that the WI possibly does more harm than good
Chunhui(Xiaomi) replies Haris(Qualcomm) and Marco(Huawei).
Hannu (Nokia) comments
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) objects to the WI (all revisions)
DongYeon (Samsung) comments.
Stefan (Ericsson) proposes to NOTE
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #17 - - Docs:=4 -
10.4 S2-2206100 WID NEW Approval New TEI18 on the Support of Qos Monitoring also in the Non 3GPP access (N3IWF/TNGF) case Nokia, Nokia Shanghai Bell, Broadcom Rel-18 Revised to S2-2207834. CC#5: Noted and S2-2207834 was withdrawn Saso (Intel) seeks clarification.
Yishan (Huawei) asks a question.
Yildirim (Charter) supports the WID; and asks a question for clarification.
Stefan (Ericsson) questions the need for this WID
Laurent (Nokia): answers
==== 9.X, 10.X Revisions Deadline ====
Omkar (CableLabs) supports the WID; and asks a question for clarification.
==== 9.X, 10.X Final Deadline ====
Saso (Intel) re-sends a request for clarification from August 17th.
Noted
10.4 S2-2207834 WID NEW Approval New TEI18 on the Support of Qos Monitoring also in the Non 3GPP access (N3IWF/TNGF) case Nokia, Nokia Shanghai Bell, Broadcom Rel-18 Revision of S2-2206100. WITHDRAWN Withdrawn
10.4 S2-2206101 DRAFTCR Information New TEI18 on the Support of Qos Monitoring also in the Non 3GPP access (N3IWF/TNGF) case Nokia, Nokia Shanghai Bell, Broadcom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206102 DRAFTCR Information New TEI18 on the Support of Qos Monitoring also in the Non 3GPP access (N3IWF/TNGF) case Nokia, Nokia Shanghai Bell, Broadcom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #18 - - Docs:=5 -
10.4 S2-2206320 WID NEW Approval New WID on Enhanced IMS to 5GC Integration Phase 2 Huawei, HiSilicon Rel-18 Revision of (Postponed) S2-2204398 from S2#151E. Noted Rainer (Nokia) proposes updates to the WID.
Ashok (Samsung) comments that WID needs update to reflect CT1 conclusions
Leo (Deutsche Telekom) proposes updates to the WID.
Haris(Qualcomm) proposes r01
Yang (OPPO) is fine to the WID but not sure if a CR to 23503 is still needed.
Rainer (Nokia) provides r02.
Mu (Huawei) provides replies, and propose two questions.
George (Ericsson) objects to r02. Removing romaing aspects and e2e media optimization is not OK.
Rainer (Nokia) objects to r00 and r01.
Rainer (Nokia) replies.
George (Ericsson) replies
Mu (Huawei) comments and provide r03
Ashok (Samsung) object to original and all the revisions
Mu (Huawei) replies to Ashok
Ashok (Samsung) responds
George (Ericsson) accepts only r00 or r01.
Rainer (Nokia) does not accept r00 and r01, but only r02.
Mu (Huawei) only accepts r03 and objects all other revision.
Rainer (Nokia) clarifies that r02 and r03 are acceptable.
Ashok (Samsung) provides r04
Mu (Huawei) can accepts r03 and r04
Haris(Qualcomm) asks whether ME box needs to be ticked
Rainer (Nokia) comments.
Haris(Qualcomm) replies
Rainer (Nokia) agrees with Haris (Qualcomm).
Mu (Huawei) comments. R05 is provided based on the comment, ME impact is added
==== 9.X, 10.X Revisions Deadline ====
George (Ericsson) accepts only r00 or r01. None of the other revisions are acceptable.
Rainer (Nokia) does not accept r00 and r01, all other revisions are ok.
George (Ericsson) comment. HWA provide r00, so now HWA is rejecting its own TEI1-8 WID
Mu (Huawei) comment, r00 was postpone from last meeting. Requesting addition aspects to be study in TEI18 WID does not make sense.
Mu (Huawei) propose to discuss the issue in CC#4 or CC#5, whether study the additional aspect is allowed in TEI WID.
Haris(Qualcomm) cannot accept r00 but possibly for different reason (inaccurate description of changes required in URSP)
George (Ericsson) answers
George (Ericsson) responds
Mu (Huawei) answers
George (Ericsson) The LS from SA2 will eliminate that. It is simpler and easier that way.
George (Ericsson) I only specified the User Plane optimization part. 23.228 is copying the CT4 solutions anyway. This is the way out of this deadlock. What is the issue with that.
For the other item, we can keep it and update the WID. I am trying to find a way forward.
George (Ericsson) It is an overkill. But what else do we do. We can propose a small CR instead.
Rainer (Nokia) would prefer a TEI18 CR instead.
==== 9.X, 10.X Final Deadline ====
George (Ericsson) asks a question.
George (Ericsson) is Ok with a TE18-CR for the CT1 issue.
Rainer (Nokia) proposes to do this at the next meeting
Noted
10.4 S2-2206319 DISCUSSION Discussion Discussion on proposed WID elMS5G2 Huawei, HiSilicon Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206341 DRAFTCR Information EIMS5G2 CR Convey the IMS home network domain name in Domain descriptors Huawei, HiSilicon Rel-18 Noted Mu (Huawei) provide r01 based on comments.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206800 DRAFTCR Information Storing UPF ID in UDM enabling routing of traffic via localized IMS media plane functions Nokia, Nokia Shanghai-Bell Rel-18 Noted George Foti (Ericsson) Objects to the CR. Additional comments below.
Rainer (Nokia) replies to George (Ericsson).
George (Ericsson) provides comments
Rainer (Nokia) replies.
George (Ericsson) . So we have to postpone this WID. We object to the CR as it is.
George Foti (Ericsson) provides r01
Rainer (Nokia) provides r02.
George (Ericsson) provides comments. We are not Ok with removing the note in option 1. It reflects the fact U can water it down but not remove it completely
Ashok (Samsung) responds to Rainer (Nokia)
Ashok (Samsung) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206802 DRAFTCR Information UPF identity stored in UDM enabling localized routing Nokia, Nokia Shanghai-Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #19 - - Docs:=8 -
10.4 S2-2206740 WID NEW Approval New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18 _DCAMP_Ph2) China Telecom, China Unicom, ZTE, vivo, CATT, Inspur, Huawei, Spreadtrum Communications, InterDigital Rel-18 Revision of (Postponed) S2-2204431 from S2#151E. r03 agreed. Revised to S2-2207835. Pallab (Nokia) asks questions and requests for clarification
Yubing (China Telecom) replies to Pallab (Nokia) and provides clarification
Yubing (China Telecom) replies to Belen (Ericsson)
Belen (Ericsson) asks questions on the need for objective 1
Belen (Ericsson) replies.
Yubing (China Telecom) replies to Belen (Ericsson).
Yubing (China Telecom) replies.
Belen (Ericsson) says that the content of the WID is not agreeable at the moment, needs more time to discuss what the problem is.
Yubing (China Telecom) replies to Belen (Ericsson) and provides r01.
Pallab (Nokia) asks questions further questions and thinks that objective 2 needs to be removed from the WID
Yubing (China Telecom) replies to Pallab (Nokia) and provides r02 and r03
==== 9.X, 10.X Revisions Deadline ====
Sherry (Xiaomi) comments.
Pallab (Nokia) is OK with r03. Do not agree with any other revisions.
Jinguo(ZTE) is fine with r03
Belen (Ericsson) can accept r03
Chi (China Unicom) supports r03.
==== 9.X, 10.X Final Deadline ====
Revised
10.4 S2-2207835 WID NEW Approval New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18 _DCAMP_Ph2) China Telecom, China Unicom, ZTE, vivo, CATT, Inspur, Huawei, Spreadtrum Communications, InterDigital Rel-18 Revision of S2-2206740r03. Approved Approved
10.4 S2-2206374 DISCUSSION Discussion Discussion on supporting dynamically changing AM policies in LBO roaming scenario for AF's request China Telecom Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206384 DRAFTCR Information 23.502 Supporting DCAMP in LBO roaming scenario China Telecom Rel-18 Noted Belen (Ericsson) provides comments
Yubing (China Telecom) replies to Belen (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206397 DRAFTCR Information 23.503 Supporting DCAMP in LBO roaming scenario China Telecom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206343 DISCUSSION Discussion Discussion on supporting dynamically Changing AM policies based on accumulated usage China Telecom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206391 DRAFTCR Information 23.502 Supporting PCF to make AM policies decision based on UE s accumulated usage China Telecom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206403 DRAFTCR Information 23.503 Supporting PCF to make AM policies decision based on UE s accumulated usage China Telecom Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #20 - - Docs:=3 -
10.4 S2-2206399 WID NEW Approval Per UE S-NSSAI priority awareness in the (R)AN Nokia, Nokia Shanghai Bell, Xiaomi Rel-18 Noted Haiyang(Huawei) comments
Peter Hedman (Ericsson) provides comments, and that existing information seems to be enough for RAN to take a an appropriate decision
Alessio(nokia) replies to Peter and Haiyang
Peter Hedman (Ericsson) provides comments and justifications why existing mechanisms seems sufficient for the addressed scenario
alessio(Nokia) comments on comments
Peter Hedman (Ericsson) provides comments and still have concerns
==== 9.X, 10.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and propose to NOTE the work
Dieter (Deutsche Telekom): we agree with Ericsson that we better do a proper study in a later release and proposes to note this WID.
Iskren (NEC) believes this WI is needed, especially in Rel-18 and we support it
Peter Hedman (Ericsson) as clarified there are multiple aspects to consider and look into before doing normative work, i.e. we object to the proposal and ask for a suitable study to be created
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206393 DISCUSSION Discussion TEI18 proposal: Per UE S-NSSAI priority awareness in the (R)AN Nokia, Nokia Shanghai Bell, Xiaomi Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206422 DRAFTCR Information On Providing per UE S-NSSAI priority to the (R)AN Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #21 - - Docs:=2 -
10.4 S2-2206451 WID NEW Approval New WID: Enhancements to usage of Target NSSAI Nokia, Nokia shanghai Bell Rel-18 Merged into S2-2205880 (noted). Noted Haiyang(Huawei) suggests to discuss in the 5880 thread
Peter Hedman (Ericsson) agree with Haiyang to use 05880/05881
Jinguo(ZTE) suggests to use single thread in the 5880 for discussion
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206438 DISCUSSION Agreement Discussion on enhancements of Target NSSAI feature in rel-18 Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #22 - - Docs:=2 -
10.4 S2-2206579 WID NEW Approval New WID on AF managing user priorities for particular slice (TEI18_WID_AFUPS) Samsung Rel-18 Noted Haris(Qualcomm) comments
Jinsook (DISH) provides comment
alessio(Nokia) provides comments
Kundan(NEC) comments
Ashok (Samsung) responds
Jinguo(ZTE) express concerns on this work item
Haiyang (Huawei) comments
Ashok (Samsung) comments
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206559 DRAFTCR Information AF setting user priority for one particular slice Samsung Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #23 - - Docs:=3 -
10.4 S2-2206827 WID NEW Approval New WID: BSF discovery for a MAC address in distributed BSF deployment. China Mobile Rel-18 Revision of (Postponed) S2-2204465 from S2#151E. Noted Haiyang(Huawei) comments
Belen (Ericsson) comments that there are still concerns on this WID that needs more study
Dan(China Mobile) reply
Pallab (Nokia) comments
Belen (Ericsson) comments.
Pallab (Nokia) requests for clarification
Dan(China Mobile) response
==== 9.X, 10.X Revisions Deadline ====
Haiyang (Huawei) comments
==== 9.X, 10.X Final Deadline ====
Haiyang (Huawei) comments. suggests to postpone or note the WID (request for CC5 if needed)
Noted
10.4 S2-2206815 CR Approval 23.502 CR3234R4 (Rel-18, 'B'): BSF service update for AF notification of replacement of UE address(es) China Mobile Rel-18 Revision of (Noted) S2-2204466 from S2#151E. Noted Pallab (Nokia) comments that the CRs accompanied with WIDs are submitted for information only. The CR cannot be approved.
Dan (China Mobile) do not understand Nokia's comment, and this CR is for approval, not for information
Pallab (Nokia) responds to Dan (China Mobile).
Dan (China Mobile) I understand now.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206825 CR Approval 23.503 CR0673R4 (Rel-18, 'B'): BSF service update for AF notification of replacement of UE address(es) China Mobile Rel-18 Revision of (Noted) S2-2204469 from S2#151E. Noted Pallab (Nokia) comments that the CRs accompanied with WIDs are submitted for information only. The CR cannot be approved.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #24 - - Docs:=3 -
10.4 S2-2206830 WID NEW Approval New WID: Enhancements on U2N Relay Selection Xiaomi Rel-18 Noted Jianning (Xiaomi) provides r01
LaeYoung (LGE) comments.
Wen (vivo) comments.
Fei (OPPO) asks questions.
Jianning (Xiaomi) replies to Wen (vivo) and LaeYoung (LGE)
Jianning (Xiaomi) replies to Shabnam (Ericsson),
Jianning (Xiaomi) replies to Fei(OPPO)
Shabnam (Ericsson) we do not see the need for this WI and we also do not see how user interaction/input need to be specified in 3GPP specification.
Steve (Huawei) comments
Jianning (Xiaomi) replies to Steve(Huawei)
Hannu (Nokia) shares the concerns expressed by the others.
Jianning (Xiaomi) replies to Hannu (Nokia)
Sherry (Xiaomi) asks for more clarifications.
Sherry (Xiaomi) replies.
Sherry (Xiaomi) replies to Hannu.
Jianning (Xiaomi) provides r03 based on the received comments
Mehrdad (Mediatek Inc.) supports this proposal based on r03
Shabnam (Ericsson) is not convinced of the value or need for this, comments
Hong (Qualcomm) comments.
Deng Qiang (CATT) shares the same concerns with others, and not clear what is missing in current spec.
Jianning (Xiaomi) replies to Hong (Qualcomm)
Sherry (Xiaomi) replies to Shabnam that this solution is based on the SA1 discussion related to U2N relay enhancement.
Steve (Huawei) comments on configuration and when it is used (narrow window at best), impacts are bigger than stated. Other ways exist.
Biao (China Telecom) supports the principle of this TEI, comments
Jianning (Xiaomi) replies to Steve (Huawei)
Hannu (Nokia) is still not convinced as the target seems to keep moving along with the discussion.
Jianning (Xiaomi) provide r04 to add MediaTek as supporting company
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) we maintain our opposition/objection to this WI as we do not see it as needed.
Jianning (Xiaomi) asks for further explaination for the objection why it is not needed? since we have already justified that this TEI is based on the SA1 requirements that is missing in TS 23.304, and also clarified the additional benefit for operator and user, which are also confirmed by operator.
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206831 DISCUSSION Approval Discussion about Enhancements on U2N Relay Selection Xiaomi Rel-18 Noted Jianning (Xiaomi) provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206832 DISCUSSION Approval Enhancement to U2N Relay Selection Xiaomi Rel-18 Noted Jianning (Xiaomi) provides r01
Hannu (Nokia) points out that this CR depends on the corresponding WID in S2-2206830.
Jianning (Xiaomi) provides r02 based on recieved comments
Hannu (Nokia) points out that the cover page justification for this CR must come from agreed version of S2-2206830.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #25 - - Docs:=4 -
10.4 S2-2206847 WID NEW Approval New WID TEI18_QUIC_CID Differentiating QoS for QUIC using Connection ID Qualcomm Incorporated Rel-18 Noted Susan (Huawei) asks questions for clarification.
Rainer (Nokia) comment and has doubts about the overall applicability of this approach.
Curt (Meta) comments ...
Stefan (Ericsson) provides similar doubts as Rainer
Susan (Huawei) replies to Curt.
Curt (Meta) replies to Susan ...
Miguel (Qualcomm) provides responses to Susan, Rainer and Curt
Susan (Huawei) replies to Miguel (Qualcomm).
Miguel (Qualcomm) replies to Susan (Huawei)
Rainer (Nokia) comments.
Stefan (Ericsson) provides comments
Miguel (Qualcomm) provides answers to Rainer (Nokia)
Miguel (Qualcomm) replies to Stefan (Ericsson)
Rainer (Nokia) replies.
Miguel (Qualcomm) replies to Rainer (Nokia)
Florin(Broadcom) supports the concerns raised by Nokia and Apple below.
Krisztian (Apple) shares the concerns raised in this thread.
==== 9.X, 10.X Revisions Deadline ====
Ellen (Google) shares the concerns raised from companies about CID range solution
Rainer (Nokia) proposes to note.
Stefan (Ericsson) objects to the WID
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206843 DISCUSSION Discussion Motivation for New TEI18 WID on Differentiating QoS for QUIC using Connection ID Qualcomm Europe Inc. Sweden Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206849 DRAFTCR Information QUIC connection ID inclusion in IP packet filter set and reflective QoS. Qualcomm Incorporated Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206851 DRAFTCR Information QUIC connection ID in QoS Qualcomm Incorporated Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #26 - - Docs:=2 -
10.4 S2-2206861 WID NEW Approval New WID: 5G ProSe Secondary Authentication Interdigital, LG Electronics, Samsung, China Telecom, Huawei(?) Confirm Sources! Noted Fei (OPPO) comments
Judy (Ericsson) comments
Jung Je (Interdigital) provided r01
Jung Je (Interdigital) responds Hong(Qualcomm)
Hong (Qualcomm) comments and thinks that a study is needed.
Deng Qiang (CATT) shares the same view as Judy and Hong, and believes a SA3 leading study is required.
Jung Je (Interdigital) responded Judy (Ericsson)
==== 9.X, 10.X Revisions Deadline ====
Judy (Ericsson) objects to this paper, for the clarity of chairman's note
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206860 DISCUSSION Discussion Discussion on Work for Prose Secondary Authentication in Rel-18 Interdigital Rel-18 Noted Jung Je (Interdigital): provides r01
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #27 - - Docs:=3 -
10.4 S2-2206944 WID NEW Approval New WID: TEI18_REFLQOS Improving Reflective QoS Control Indication. Apple Rel-18 Revision of (Postponed) S2-2204191 from S2#151E. Revised to S2-2207836. CC#5: Noted and S2-2207836 was withdrawn Hong (Qualcomm) comments and thinks this had been discussed before in 5G_Ph1 Reflective QoS design and addressed in existing mechanism in TS 23.501.
Judy (Ericsson) asks questions
Krisztian (Apple) responds to questions.
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Hong (Qualcomm) replies to Krisztian.
Noted
10.4 S2-2207836 WID NEW Approval New WID: TEI18_REFLQOS Improving Reflective QoS Control Indication. Apple Rel-18 Revision of S2-2206944. WITHDRAWN Withdrawn
10.4 S2-2206946 DRAFTCR Information Draft CR: Improving Reflective QoS Control Indication Apple Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #28 - - Docs:=3 -
10.4 S2-2205602 WID NEW Approval IPv6 Prefix Delegation in 5GS Ericsson Rel-18 CC#5: r01 agreed. Revised to S2-2207884. Haris(Qualcomm) supports doing the work but the WI cannot be approved 'as is'
==== 9.X, 10.X Final Deadline ====
Shabnam (Ericsson) points out that the discussion took place on the SA2 discussions list and as per Qualcomm proposal, supported by other companies the WI selected to go with Option 1 as indicated in the WI. You can check it out on the discussions list and with Hong/Qualcomm delegate. Can we take this in CC#5?
Laurent (Nokia): we support the WID being discussed at CC5 (and revised version being approved)
Revised
10.4 S2-2207884 WID NEW Approval IPv6 Prefix Delegation in 5GS Ericsson Rel-18 Revision of S2-2205602r01. Approved Approved
10.4 S2-2205601 DISCUSSION Approval IPv6 Prefix Delegation in 5GS Ericsson Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #29 - - Docs:=3 -
10.4 S2-2205873 WID NEW Endorsement TEI18 on enhancement of application detection event exposure. China Mobile, Telecom Italia, China Unicom, Asiainfo, CATT, China Telecom, Huawei Rel-18 Revision of (Postponed) of S2-2204456. Noted. CC#5: r05 agreed. Revised to S2-2207886. Pallab (Nokia) asks questions and requests for clarification
Aihua(CMCC) replies to Pallab (Nokia).
Pallab (Nokia) responds to Aihua(CMCC)
Belen (Ericsson) provides comments
Aihua(CMCC) replies to Pallab (Nokia) and Belen (Ericsson).
Aihua(CMCC) provides r01.
Leo (Deutsche Telekom) provides comments.
Jinguo(ZTE) provides r02, add ZTE as supporting company.
Leo (Deutsche Telekom) is fine with r01, thanks.
Belen (Ericsson) comments that a draft CR to 23.502 would be needed.
Aihua(CMCC) replies to Belen (Ericsson).
Belen (Ericsson) replies to CMCC
Belen (Ericsson) proposes to update the WID to add impacts to 23.502, and TU estimation accordingly
Antoine (Orange) does not see a real use case because in practice, the AF providing the value added service realizes by application-level means that a UE is using its services, so it doesn't need a notification from the network.
==== 9.X, 10.X Revisions Deadline ====
Aihua(CMCC) replies to Belen (Ericsson) and provides r03.
Aihua(CMCC) replies to Antoine (Orange).
Belen (Ericsson) cannot accept any revision, proposes to add impacts on 23.502 for Event Exposure via NEF at least.
Aihua(CMCC) replies to Belen (Ericsson) and provides drafting r04 for reference.
Antoine (Orange) objects to r00, r01 and r02.
Jinguo(ZTE) believes the ground of objection are invalid.
==== 9.X, 10.X Final Deadline ====

Jinguo(ZTE) believes the ground of objection are invalid.
Revised
10.4 S2-2207886 WID NEW Endorsement TEI18 on enhancement of application detection event exposure. China Mobile, Telecom Italia, China Unicom, Asiainfo, CATT, China Telecom, Huawei Rel-18 Revision of S2-2205873r05. Approved Approved
10.4 S2-2205872 DRAFTCR Information Adding application detection event exposure from PCF China Mobile, Asiainfo, CATT, Huawei Rel-18 Revision of (Noted) of S2-2204458. Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #30 - - Docs:=4 -
10.4 S2-2206255 WID NEW Approval New WID: TEI18_CHFSel; CHF Selection information in Subscription Data Nokia, Nokia Shanghai Bell, Verizon UK Ltd Rel-18 Noted Shabnam (Ericsson) does not believe the proposed soln for this WI is stable or clear, provides comments.
Pallab (Nokia) responds to Shabnam (Ericsson).
==== 9.X, 10.X Revisions Deadline ====
Shabnam (Ericsson) but this aspect is not under SA2. TEI18 WI should be self contained for SA2 and should have stable solution base. As such, I don't see how we can proceed with the current proposal.
Antoine (Orange): Shouldn't this be discussed in SA5 first?
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206256 DRAFTCR Information CHF Selection information in subscription data Nokia, Nokia Shanghai Bell, Verizon UK Ltd Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206257 DRAFTCR Information CHF Selection information in subscription data Nokia, Nokia Shanghai Bell, Verizon UK Ltd Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206258 DRAFTCR Information CHF Selection information in subscription data Nokia, Nokia Shanghai Bell, Verizon UK Ltd Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.4 - - - TEI18 proposal #31 - - Docs:=2 -
10.4 S2-2206689 WID NEW Approval New WID: TEI18_SAPR; Self Activating PCC Rules Nokia, Nokia Shanghai Bell Rel-18 Noted Saso (Intel) comments that a 23.502 CR is needed.
Pallab (Nokia) responds to Saso (Intel)
Uri (Oracle) provides a request for clarification.
Belen (Ericsson) comments that 23.502 and 23.501 CRs are needed to explain how it works
Pallab (Nokia) responds Belen and Uri
Uri (Oracle) responds to Pallab and asks Nokia to kindly withdraw the WID for time being
Pallab (Nokia) responds Uri (Oracle)
Uri (Oracle) provides additional feedback to Pallab (Nokia) (still suggesting to note the paper for time being).
Uri (Oracle) responds to feedback from Pallab (Nokia), and suggests to note the paper for time being.
Belen (Ericsson) comments that a CR to 23.502, potential impacts on RAN to reserve GBR resources with no GBR and TU estimation should be provided in WID
==== 9.X, 10.X Revisions Deadline ====
Uri (Oracle) responds to comments from Belen (Ericsson)
Pallab (Nokia) proposes to NOTE this based on comments
==== 9.X, 10.X Final Deadline ====
Noted
10.4 S2-2206690 DRAFTCR Information Self activating PCC rules Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 9.X, 10.X Final Deadline ====
Noted
10.5 - - - Rel-18 SID/WID Status Reports - - Docs:=27 -
10.5 S2-2205481 WI STATUS REPORT Approval SA WG2 Status report for 5WWC Nokia, Nokia Shanghai Bell Rel-18 Block Noted at CC#5
==== 9.X, 10.X Final Deadline ====
Noted
10.5 S2-2206654 WI STATUS REPORT Information Status report for FS_eNS_Ph3 ZTE Rel-18 Block Noted at CC#5
==== 9.X, 10.X Final Deadline ====
Noted
10.5 S2-2205590 WI STATUS REPORT Information FS_DetNet Status Report Ericsson Rel-18 Block Noted at CC#5 Noted
10.5 S2-2205805 WI STATUS REPORT Information FS_eNPN_Ph2 Status Report Ericsson (Rapporteur) Block Noted at CC#5 Noted
10.5 S2-2206965 WI STATUS REPORT Information WI Status Report: Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206966 WI STATUS REPORT Information WI Status Report: Study on satellite access Phase 2 (FS_5GSAT_Ph2) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206967 WI STATUS REPORT Information WI Status Report: Study on 5G System with Satellite Backhaul (FS_5GSATB) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206968 WI STATUS REPORT Information Status report of FS_5MBS_Ph2 Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206969 WI STATUS REPORT Information FS_5TRS_URLLC Status Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206970 WI STATUS REPORT Information WI Status Report: Study on System Support for AI/ML-based Services (FS_AIMLsys) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206971 WI STATUS REPORT Information WI Status Report: Study on 5G AM Policy (FS_AMP) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206972 WI STATUS REPORT Information WI Status Report: Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206973 WI STATUS REPORT Information WI Status Report: Study on Edge Computing Phase 2 (FS_EDGE_Ph2) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206974 WI STATUS REPORT Information WI Status Report: Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206975 WI STATUS REPORT Information WI Status Report: Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206976 WI STATUS REPORT Information WI Status Report: Study on Enhancement of 5G UE Policy (FS_eUEPO) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206977 WI STATUS REPORT Information WI Status Report: Study on Generic group management, exposure and communication enhancements (FS_GMEC) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206978 WI STATUS REPORT Information WI Status Report: Study on evolution of IMS multimedia telephony service (FS_NG_RTC) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206979 WI STATUS REPORT Information WI Status Report: Study on Personal IoT Networks (FS_PIN) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206980 WI STATUS REPORT Information WI Status Report: Study on Ranging based services and sidelink positioning (FS_Ranging_SL) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206981 WI STATUS REPORT Information WI Status Report: Study on RedCap Phase 2 (FS_RedCAP_Ph2) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206982 WI STATUS REPORT Information WI Status Report: Study on System Enabler for Service Function Chaining (FS_SFC) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206983 WI STATUS REPORT Information WI Status Report: Study on Seamless UE context recovery (FS_SUECR) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206984 WI STATUS REPORT Information WI Status Report: Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206985 WI STATUS REPORT Information WI Status Report: Study on UPF enhancement for Exposure And SBA (FS_UPEAS) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206986 WI STATUS REPORT Information WI Status Report: Study on Vehicle Mounted Relays (FS_VMR) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.5 S2-2206987 WI STATUS REPORT Information WI Status Report: Study on XR (Extended Reality) and media services (FS_XRM) Rapporteur Rel-18 Block Noted at CC#5 Noted
10.6 - - - Review of the Work Plan - - Docs:=3 -
10.6 S2-2205667 WORK PLAN Endorsement SA WG2 Work Planning Sheet SA WG2 Chair Revision (Endorsed) of S2-2201217 from S2#149E. r01 agreed. Revised to S2-2207837. Puneet (SA2 Chair) provides r01 based on discussion at CC#1 Revised
10.6 S2-2207837 WORK PLAN Endorsement SA WG2 Work Planning Sheet SA WG2 Chair - Revision of S2-2205667r01. CC#5: This was endorsed Endorsed
10.6 S2-2205668 WORK PLAN Endorsement SA WG2 work planning SA WG2 Chair Endorsed Yannick (Nokia): Nokia provides comments on a few proposals in the work planning slides.
Puneet (SA2 Chair) responds to Yannick (Nokia).
Endorsed
10.7 - - - Planning future meetings - - Docs:=0 -
10.8 - - - Items moved to Deadline 2 - - Docs:=18 -
10.8 S2-2205448 LS In Action LS from TSG SA: Reply LS on 5G ProSe security open items TSG SA (SP-220716) Rel-17 CC#3: Moved to AI 10.8. Response drafted in S2-2207699. Final response in S2-2207838 Fei (OPPO) proposes to note this LS since no reply LS is required for this.
Steve (Huawei) proposes to note.
==== 4.X, 5.X, 6.X, 7.X, 8.X Revisions Deadline ====
==== 9.X, 10.X Revisions Deadline ====
Replied to
10.8 S2-2207699 LS OUT Approval [DRAFT] Reply LS on 5G ProSe security open items InterDigital Rel-17 Created at CC#3. Response to S2-2205448. r04 agreed. Revised to S2-2207838. Jung Je (Interdigital) provides initial draft
Judy (Ericsson) share Hong's view the architecture aspect needs to be studied by SA2
Jung Je (Interdigital) comments.
Hong (Qualcomm) comments.
Jung Je (Interdigital) provides r02.
Judy (Ericsson) provides r01
Hannu (Nokia) supports r02 and the principle of SA3 leading security work items.
Judy (Ericsson) provides r03 with wording improvement
Steve (Huawei) provides r04
==== 9.X, 10.X Revisions Deadline ====
Deng Qiang (CATT) replies.
Sherry (Xiaomi) comments.
Judy (Ericsson): please leave the agenda arrangements to SA2 chair and until we have had an opportunity to get feedback from SA3 officially, we do not see any need to discuss timeline in SA2.
==== 9.X, 10.X Final Deadline ====
Revised
10.8 S2-2207838 LS OUT Approval Reply LS on 5G ProSe security open items SA WG2 Rel-17 Revision of S2-2207699r04. Approved Approved
10.8 S2-2205394 LS In Action LS from TSG CT: LS on parameters preconfigured in the UE to receive MBS service TSG CT (CP-220398) Rel-17 Revision of postponed S2-2203629 from S2#151E. Responses drafted in S2-2205758, S2-2206088. CC#3: moved to AI 10.8. Final response in S2-2207888 Replied to
10.8 S2-2206088 LS OUT Approval [DRAFT] Response to LS on UE pre-configuration Huawei, HiSilicon Rel-17 Revision of (Postponed) S2-2204262 from S2#151E. Response to S2-2205394. CC#3: moved to AI 10.8. CC#5: r07 + changes agreed. Revised to S2-2207888. Thomas (Nokia) provides r01
Shabnam (Ericsson) r01 and r00 object to them as are not accurately reflecting the status and the goal, we should focus on agreement of a CR as per scope then LS response can be handled easily.
==== 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 and r03 and asks to ignore r02
Haris(Qualcomm) provides r04
Shabnam (Ericsson) r05, in case we can reach agreement.
==== 9.X, 10.X Revisions Deadline ====
Haris(Qualcomm) comments that quoting incorrect text from the spec is not appropriate. Suggest to agree r04. Cannot agree on r03
Thomas(Nokia) objects to r04
LiMeng (Huawei) objects to r04, r05
Thomas(Nokia) objects against r00, r01 and r02
==== 9.X, 10.X Final Deadline ====
Haris(Qualcomm) proposes alternative wording in LS response: 'SA2 did not reach consensus to answer the questions from TSG CT and also could not agree CRs on this topic'
LiMeng (Huawei) provides r06.
Haris(Qualcomm) comments that r06 is not acceptable
Revised
10.8 S2-2207888 LS OUT Approval [DRAFT] Response to LS on UE pre-configuration Huawei, HiSilicon Rel-17 Revision of S2-2206088r07 + changes. Approved Approved
10.8 S2-2207689 CR Approval 23.247 CR0133 (Rel-17, 'F'): Alignment with SA WG4 work on MBS service announcements Nokia, Nokia Shanghai-Bell Rel-17 CC#3: New CR based on S2-2207690. CC#4: Postponed Thomas (Nokia) provides the new document (r00)
Haris(Qualcomm) proposes r01
Antoine (Orange) provides r02.
Shabnam (Ericsson) provides r03, preconfiguration aspect that was in both CRs added back. I think this version is also aligned with the LS out 2nd issue proposal. On Pre-configuration, I believe we have text left behind that needs to be removed or we revise the CR to remove leftovers completely and that means the pre-configuration feature is not available in Rel-17?
==== 9.X, 10.X Revisions Deadline ====
LiMeng (Huawei) provides r04, proposes to only making the stage 3 alignment, i.e., undo the removal of the last sentence in r03.
Haris(Qualcomm) can only accept r01, r02, r03. Objects to r0, r04
Thomas(Nokia) objects against r01 and r02
==== 9.X, 10.X Final Deadline ====
Postponed
10.8 S2-2205470 LS In Action LS from RAN WG2: LS On UE capability signalling for IoT-NTN RAN WG2 (R2-2208928) Rel-17 Response drafted in S2-2208091. CC#3: Moved to AI 10.8. Final response in S2-2207839 Replied to
10.8 S2-2208091 LS OUT Approval [DRAFT] Reply LS on UE capability signalling for IoT-NTN Vodafone Rel-17 Created at CC#2. Response to S2-2205470. CC#3: Moved to AI 10.8. r04 agreed. Revised to S2-2207839.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Chris (Vodafone) moves this discussion to the 8091 thread
Guillaume (MediaTek Inc.) provides r03
Chris (Vodafone) provides r04
Guillaume (MediaTek Inc.) OK with r04
Hannu (Nokia) shares r05 and comments
Haris(Qualcomm) prefers r04 but can accept r05
==== 9.X, 10.X Revisions Deadline ====
Chris (Vodafone) prefers r04
Guillaume (MediaTek Inc.) ok with both r05 and r04
Hannu (Nokia) can accept either r04 or r05. I can go along with the majority when this is brought up in CC.
DongYeon (Samsung) is OK with r05, and r04 (will follow the majority).
==== 9.X, 10.X Final Deadline ====
Revised
10.8 S2-2207839 LS OUT Approval Reply to LS on UE capability signalling for IoT-NTN SA WG2 Rel-17 Revision of S2-2208091r04. Approved Approved
10.8 S2-2206543 CR Approval 23.502 CR3540 (Rel-16, 'F'): Correction on 5G VN group management Huawei, HiSilicon Rel-16 CC#3: Moved to AI 10.8. r03 agreed. Revised to S2-2207840.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
Stefan (Ericsson) provides r01
Qianghua (Huawei) provides r02
Stefan (Ericsson) provides r03
Qianghua (Huawei) provides r04
==== 9.X, 10.X Revisions Deadline ====
Stefan (Ericsson) proposes to go with r03. R04 does not seem correct
Qianghua (Huawei) OK with r03
==== 9.X, 10.X Final Deadline ====
Revised
10.8 S2-2207840 CR Approval 23.502 CR3540R1 (Rel-16, 'F'): Correction on 5G VN group management Huawei, HiSilicon Rel-16 Revision of S2-2206543r03. Approved Agreed
10.8 S2-2206545 CR Approval 23.502 CR3541 (Rel-17, 'A'): Correction on 5G VN group management Huawei, HiSilicon Rel-17 Approved. CC#3: Moved to AI 10.8. Revised to S2-2207841.
==== 4.X, 5.X, 6.X, 7.X, 8.X Final Deadline ====
==== 9.X, 10.X Revisions Deadline ====
==== 9.X, 10.X Final Deadline ====
Revised
10.8 S2-2207841 CR Approval 23.502 CR3541R1 (Rel-17, 'A'): Correction on 5G VN group management Huawei, HiSilicon Rel-17 Revision of S2-2206545. Approved Agreed
10.8 S2-2208095 LS In Information Reply LS to CT WG3 on Data Reporting API SA WG4 (S4-221118) Rel-17 CC#4: This was postponed. Postponed
10.8 S2-2208096 LS In Information LS on modifications to MBS User Services architecture SA WG4 (S4-221119) Rel-17 CC#4: This was postponed. Postponed
10.8 S2-2208097 LS In Information Reply LS on Support for managing slice for trusted third-party owned application SA WG1 (S1-222262) Rel-18 CC#4: This was postponed. Postponed
10.8 S2-2208099 LS In Information LS from CT WG4: Reply LS on PLMN ID used in Roaming Scenarios CT WG4 (C4-224444) Rel-17 CC#4: This was postponed. Postponed
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=571 -
99 S2-2205489 REPORT Information Handling of PDU Sessions for Emergency services Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2205507 P-CR Discussion 23.700-08: TR 23.700-08 skeleton Ericsson (rapporteur) Rel-18 Revision of S2-2200487 (Original TR Skeleton pCR at S2#149E). WITHDRAWN Withdrawn
99 S2-2205510 P-CR Approval 23.700-28: KI #2, Sol #2: Update to complete the solution description. THALES Rel-18 WITHDRAWN Withdrawn
99 S2-2205552 P-CR Approval 23.700-80: KI#5, Sol#12: Proposal to remove EN on solution#12 Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2205597 P-CR Approval 23.700-81: KI#6, New Solution: NWDAF analytics assisted redundant transmission mechanism decision and corresponding URSP rules updates Futurewei Technologies Rel-18 WITHDRAWN Withdrawn
99 S2-2205641 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Solution#10 Update for BDT Extensions Oracle, Toyota, DoCoMo, OPPO Rel-18 WITHDRAWN Withdrawn
99 S2-2205859 CR Approval 23.501 CR3679 (Rel-16, 'F'): Removal of EAP Re-authentication Ericsson Rel-16 WITHDRAWN Withdrawn
99 S2-2205860 CR Approval 23.501 CR3680 (Rel-17, 'A'): Removal of EAP Re-authentication Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2205870 WID NEW Approval TEI18 WID on enhancement of application detection event exposure CMCC Rel-18 WITHDRAWN Withdrawn
99 S2-2206131 P-CR Approval 23.700-81: KI#5, Evaluation and Conclusion Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2206321 DISCUSSION Approval EIMS5G2 CR Convey the IMS home network domain name in Domain descriptors Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2206339 WID NEW Approval New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18 _DCAMP_Ph2) China Telecom Rel-18 Revision of (Postponed) S2-2204431 from S2#151E. WITHDRAWN Withdrawn
99 S2-2206425 P-CR Approval 23.700-08: New Solution KI#2: Provisioning N3IWF info for Credential Holder scenarios Samsung Rel-18 WITHDRAWN Withdrawn
99 S2-2206480 P-CR Approval 23.700-88: Update evaluations vivo Rel-18 WITHDRAWN Withdrawn
99 S2-2206767 P-CR Approval 23.700-60: Conclusion for KI#9 China Mobile Rel-18 WITHDRAWN Withdrawn
99 S2-2206821 WID NEW Approval New WID: Enhancements on U2N Relay Selection Xiaomi Rel-18 WITHDRAWN Withdrawn
99 S2-2206822 DISCUSSION Approval Discussion about Enhancements on U2N Relay Selection Xiaomi Rel-18 WITHDRAWN Withdrawn
99 S2-2206823 DISCUSSION Approval Enhancement to U2N Relay Selection Xiaomi Rel-18 WITHDRAWN Withdrawn
99 S2-2205789 WID NEW Approval TEI18 on IMS RDF Deutsche Telekom Rel-18 WITHDRAWN Rainer (Nokia) asks for clarification.
Leo (Deutsche Telekom) replies to Rainer.
Withdrawn
99 S2-2205795 DRAFTCR Information Extending LMF services for RDF for 23.501 Deutsche Telekom Rel-18 No Source to WG! WITHDRAWN Withdrawn
99 S2-2205828 DRAFTCR Information Extending LMF services for RDF for 23.273 Deutsche Telekom Rel-18 No Source to WG! WITHDRAWN Stephen (Qualcomm) comments
Leo (Deutsche Telekom) replies that S2-2205828 is withdrawn and we should not discuss withdrawn documents
Withdrawn
Created:      END OF LIST
OPEN documents: 24
Parallel Agreed: 0
Approved/Endorsed: 606
Agreed: 87
Replied to LSs: 24
Noted: 369
Merged: 161
For e-mail approval: 0
Postponed: 58
Withdrawn: 288
Total documents: 2158