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

 

Statement Regarding Engagement with Companies Added to the
U.S. Export Administration Regulations (EAR) Entity List in 3GPP Activities:

1. Public Information is Not Subject to EAR

3GPP is an open platform where all contributions (including technology protected or not by patent) made by the different Individual Members under the membership of each respective Organizational Partner are publicly available. Indeed, contributions by all and any Individual Members are uploaded to a public file server when received and then the documents are effectively in the public domain.

In addition, since membership of email distribution lists is open to all, documents and emails distributed by that means are considered to be publicly available.

As a result, information contained in 3GPP contributions, documents, and emails distributed at 3GPP meetings or by 3GPP email distribution lists, because it is made available to the public without restrictions upon its further dissemination, is not subject to the export restrictions of the EAR.

Meeting minutes are maintained for 3GPP meetings. Such meeting minutes for 3GPP meetings are made available to the public without restrictions upon its further dissemination. As a result, information, including information conveyed orally, contained in 3GPP meetings is not subject to the export restriction of the EAR; this would include information conveyed during side meetings that may occur during the main meetings, if these meetings are open to any participants and the results of all said meetings are publicly available without restrictions upon their further dissemination.

2. Non-Public Information

Non-public information refers to the information not contained or not intended to be contained in 3GPP contributions, documents or emails. Such non-public information may be disclosed during informal meetings, exchanges, discussions or any form of other communication outside the 3GPP meetings and email distribution lists, and may be subject to the EAR.

3. Other Information

Certain encryption software controlled under the International Traffic in Arms Regulations (ITAR), even if publicly available, may still be subject to US export controls other than the EAR.

4. Conduct of Meetings

The situation should be considered as "business as usual" during all the meetings called by 3GPP.

5. Responsibility of Individual Members

It should be remembered that contributions, meetings, exchanges, discussions or any form of other communication in or outside the 3GPP meetings are of the accountability, integrity and the responsibility of each Individual Member. In addition, Individual Members remain responsible for ensuring their compliance with all applicable export control regulations, including but not limited to EAR.

Individual Members with questions regarding the impact of laws and regulations on their participation in 3GPP should contact their companies' legal counsels.

 

 

 

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
1.1 - - - Opening of the meeting - Phase 1 - - Docs:=0 -
2 - - - Agenda - - Docs:=1 -
2 S2-2003511 AGENDA Approval SA WG2 #139E Meeting Agenda SA WG2 Chairman Approved
==== Ph1 Revisions Deadline ====
Approved
3 - - - SA2#138E Meeting report - - Docs:=1 -
3 S2-2003512 REPORT Approval Auto-Generated Report of SA WG2 meeting #138E SA WG2 Secretary Approved
==== Ph1 Revisions Deadline ====
Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - Phase 1 - - Docs:=212 -
4.1 - - - For Information - - Docs:=9 -
4.1 S2-2003562 LS In Information LS from RAN WG2: LS on RLF Agreements RAN WG2 (R2-2004086) Rel-16 Noted LaeYoung (LGE) proposes to NOTE this LS because of no action required for SA2 CCed in this LS.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003576 LS In Information LS from RAN WG2: LS on UAC applicability to IABs RAN WG2 (R2-2003941) Rel-16 Noted Hong (Qualcomm Inc.) proposes to NOTE the LS.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004321 LS In Information LS from SA WG1: reply LS on UAC applicability to IABs SA WG1 (S1-202274) Rel-16 Noted Hong (Qualcomm Inc.) proposes to NOTE the LS.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003537 LS In Information LS from CT WG1: LS on security context for 5GC to EPC mobility CT WG1 (C1-202666) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004306 LS In Information LS from SA WG3: LS reply on security context for 5GC to EPC mobility SA WG3 (S3-201453) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004303 LS In Information LS from BBF: LS on the applicability of 5G NAS protocol for 5G-RG and FN-RG BBF (LIAISE-397-03) Noted Laurent (Nokia): proposes to note the document
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004305 LS In Information LS from SA WG3: Reply LS on SUCI computation from an NSI SA WG3 (S3-201432) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004307 LS In Information LS from SA WG3: LS reply to RAN WG3 LS on AS rekeying handling SA WG3 (S3-201484) Rel-15 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004309 LS In Information LS from SA WG3: LS on security consideration of performance measurement function protocol SA WG3 (S3-201490) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 - - - Service Area Restriction - - Docs:=9 -
4.1 S2-2003524 LS In Action LS from CT WG1: LS on service area restriction for CIoT 5GS optimization CT WG1 (C1-200839) Rel-16 Revision of postponed S2-2002636 from S2-138E. Responses drafted in S2-2003711 and S2-2004199. Final response in S2-2004440
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004199 LS OUT Approval [DRAFT] Reply LS on service area restriction for CIoT 5GS optimization Qualcomm Technologies Int Rel-16 Response, merging S2-2003711, to S2-2003524. R06 agreed. Revised to S2-2004440. Lalith (Samsung) objects to base version and provides r01.
Qian Chen (Ericsson) provides comments.
Hannu (Nokia) replies to Lalith and Qian Chen and provides r02. Nokia shares Samsung concern and cannot accept the initial version.
Mike (Convida Wireless) supports r01 and has concerns about r02.
Hannu (Nokia) replies to Mike (Convida).
Mike (Convida Wireless) replies to Hannu (Nokia).
Hannu (Nokia) replies to Mike (Convida Wireless).
Mike (Convida Wireless) replies Hannu (Nokia) and provides r04
Steve (Huawei) provides r05.
Miguel Griot (Qualcomm) is ok with r03, r04 or r05.
Hannu (Nokia) can agree r03 and objects to r04 or r05 and provides also r06.
Hannu (Nokia) replies to comment from Qian Chen (Ericsson).
Miguel Griot (Qualcomm) supports r06, responds to Qian
Miguel Griot (Qualcomm) provides r07 in the unlikely event the CR attached to the LS is not agreed, but still prefers and supports r06 which contains the CR attached to the LS.
Toon Norp (KPN) comments on r07
Miguel Griot provides r08 (revision of r07) still prefers r06
==== Ph1 Revisions Deadline ====
Toon Norp (KPN) is OK with r08, still prefers r06
Lalith (Samsung) is not OK with r07 and r08
Miguel Griot (Qualcomm) comments that r13 (the agreeable version) of S2-2003712 CR was objected by Ericsson, we do need to consider r08 unfortunately. Proposes to keep r06 and r08 alive until the objection to the CR is resolved (agree r06) or sustained (agree r08).
Qian Chen (Ericsson) supports r08 even if S2-2003712 is not agreed since it's agreeable that service restriction shall be applied to CIoT optimization. It's just we missed to have correct wording in r13 before deadline. We also support the use of r06 If S2-2003712 is agreed in CC#2.
Hannu (Nokia) supports revisions that ask about Exception Data in Non-Allowed Area without mixing in the AC10 that is already clear for all. Nokia can agree r08, r07 or r06.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004440 LS OUT Approval Reply LS on service area restriction for CIoT 5GS optimization SA WG2 Rel-16 Revision of S2-2004199_R06, merging S2-2003711. Approved Approved
4.1 S2-2003711 LS OUT Approval [DRAFT] Reply LS on service area restriction for CIoT 5GS optimization Ericsson Rel-16 Response to S2-2003524. Merged into S2-2004440 Steve (Huawei) suggests noting/merge with S2-2004199?
Miguel Griot (Qualcomm) agrees with Steve to note/merge this document and proceed with S2-2004199
Qian Chen (Ericsson) agrees to note/merge this document and proceed with S2-2004199
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003712 CR Approval 23.501 CR2243R1 (Rel-16, 'F'): Service Area Restriction clarification Ericsson Rel-16 Revision of S2-2002773. R13 agreed. Revised, merging S2-2004204, to S2-2004439. Steve (Huawei) comments
Qian Chen (Ericsson) provides comments
Lalith (Samsung) provides r01
Steve (Huawei) provides comments and r02
Hannu (Nokia) agrees Steve's proposal on bullet item list and provides r03
Hannu (Nokia) proposes two alternative revisions, r05 and r06.
Miguel Griot (Qualcomm) objects to S2-2003712 and all revisions up to r06 and any CR revision that includes any change in behavior for SMS/LCS from Rel-15 or additional configuration in UE. Proposes to proceed with S2-2004204 instead.
Qian Chen (Ericsson) provides comments.
Miguel Griot (Qualcomm) responds to Qian.
Lalith Kumar (Samsung) agrees with Qian Chen (Ericsson) and ask question to Miguel Griot (Qualcomm) .
Qian Chen (Ericsson) responds to Miguel Griot (Qualcomm)
Qian Chen (Ericsson) provides rev07 on top of rev06, and comment on rev05.
Qian Chen (Ericsson) provides rev08 as another alternative.
Lalith (Samsung) provides comments on rev08.
Hannu (Nokia) comments and provides r09
Miguel Griot (Qualcomm) responds that Lalith (Ericsson)
Miguel Griot (Qualcomm) is OK with r09 conditional to everyone is reading the text the same way?
Lalith (Samsung) responds to Miguel
Miguel Griot (Qualcomm) provides r10 removing SMS, in case the understanding is not clear from r09. Prefers r10 but can live with r09 conditional to same understanding by everyone.
Miguel Griot (Qualcomm) responds to Lalith (Samsung)
Hannu (Nokia) confirms the assumption of Miguel (Qualcomm).
Hannu (Nokia) supports Miguel's r10.
Lalith (Samsung) provides r11.
Steve (Huawei) r10 is ok.
Hannu (Nokia) provides r12 as requested by Lalith (Samsung).
Lalith (Samsung) provides r13.
Miguel Griot (Qualcomm) is OK with r13.
Steve (Huawei): r13 is ok.
==== Ph1 Revisions Deadline ====
Qian Chen (Ericsson) propose to go with r10 since r13 introduces conflicting text.
Lalith (Samsung) propose to go with r13 and objects all other revisions. Because r13 captures the discussion accurately.
Qian Chen (Ericsson) provides comments to Lalith(Samsung)
Qian Chen (Ericsson) provides further comments
Lalith(Samsung) responds to Qian Chen (Ericsson)
Qian Chen (Ericsson) objects to r13 since it missed some aspects of the agreement in the discussion, and propose to ask the permission on Friday CC to update the r13 with simple text enhancement.
Steve (Huawei) comments.
Miguel Griot (Qualcomm) asks Qian to please reconsider his objection to r13, provides reasons.
Qian Chen (Ericsson) provides new text enhancement proposal, responds to Miguel Griot (Qualcomm), maintains the objection to current r13.
Hannu (Nokia) agrees with r13.
Steve (Huawei) does not agree with new text proposal. R10 and r13 is acceptable.
Hannu (Nokia) supports r013.
Qian Chen (Ericsson) responds to Steve (Huawei).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004439 CR Approval 23.501 CR2243R3 (Rel-16, 'F'): Service Area Restriction clarification Ericsson, Qualcomm Rel-16 Revision of S2-2003712_R13, merging S2-2004204. This CR was agreed Agreed
4.1 S2-2003713 CR Approval 23.502 CR2315 (Rel-16, 'F'): Service Area Restriction clarification Ericsson Rel-16 Noted Lalith (Samsung) comments: this CR should be progressed only if in 3712(23.501) CR we are able to agree to have special treatment for SMS/LCS/Exception.
Miguel Griot (Qualcomm) objects to S2-2003713 and any CR revision that includes any change in behavior for SMS/LCS from Rel-15 or additional configuration in UE. Proposes to proceed with S2-2004204 instead.
Steve (Huawei) proposes to NOTE.
Miguel Griot (Qualcomm) agrees with Steve (Huawei) this CR should be noted.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004194 DISCUSSION Agreement Proposed way forward for service area restriction for CIoT 5GS optimization. Qualcomm Incorporated Rel-16 Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004204 CR Approval 23.501 CR2243R2 (Rel-16, 'F'): Service Area Restriction clarification Qualcomm Incorporated Rel-16 Revision of S2-2002773. Merged into S2-2004439 Lalith (Samsung) prefers 3712r01 over 4204. Thus proposes to merge this CR into 3712r01.
Hannu (Nokia) comments on the merge of 4204 to 3712.
Qian Chen (Ericsson) provides comments.
Hannu (Nokia) replies to Qian Chen's comment and provides r04.
Steve (Huawei) comments.
Hannu (Nokia) responds to comments and proposes to look at 3712 r05 and r06 instead.
Hannu (Nokia) proposes two alternative revisions, r05 and r06.
Miguel Griot (Qualcomm) responds to comments on 4204, proposes to proceed with 4204 instead of 3712/3713.
Lalith (Samsung) responds to comments.
Hannu (Nokia) can live with 4204 but prefers 3712r06.
Qian Chen (Ericsson) Objects to this CR since some content in the current revision is incorrect, and continues the work in S2-2003712 where intensive efforts from different companies provided.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 - - - I-NEF - - Docs:=6 -
4.1 S2-2003528 LS In Action LS from CT WG3: Reply LS on Service on I-NEF Event Exposure CT WG3 (C3-201494) Rel-16 Revision of postponed S2-2002645 from S2-138E. Response drafted in S2-2004035. Final response in S22004451 Replied to
4.1 S2-2004035 LS OUT Approval [DRAFT] LS on I-NEF Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003528. R01 agreed. Revised to S2-2004451. Hannu (Nokia) provides r01 of the I-NEF LS.
==== Ph1 Revisions Deadline ====
Andy (Vice Chair, Samsung) allocates S2-2004451 for the approved r01.
Hannu (Nokia) has uploaded S2-2004451 as the revision of S2-2004035.
Revised
4.1 S2-2004451 LS OUT Approval Reply LS on Service on I-NEF Event Exposure SA WG2 Rel-16 Revision of S2-2004035r01. Approved Approved
4.1 S2-2004036 CR Approval 23.501 CR2374 (Rel-16, 'F'): Removal of I-NEF Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-16 This CR was agreed Farooq (AT&T) asks a question for clarification
Judy (Ericsson) responded.
Gerald (Matrixx) asks a question for clarification
Judy (Ericsson) responded and ask to clarify the questions.
Hannu (Nokia) replies to Farooq (AT&T)
==== Ph1 Revisions Deadline ====
Agreed
4.1 S2-2004037 CR Approval 23.502 CR2320 (Rel-16, 'F'): Removal of I-NEF Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon Rel-16 This CR was agreed
==== Ph1 Revisions Deadline ====
Agreed
4.1 S2-2004038 CR Approval 23.273 CR0126 (Rel-16, 'F'): Removal of I-NEF Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon Rel-16 This CR was agreed
==== Ph1 Revisions Deadline ====
Agreed
4.1 - - - CAG-related - - Docs:=28 -
4.1 S2-2003527 LS In Action LS from CT WG1: Reply LS on sending CAG ID CT WG1 (C1-201027) Rel-16 Revision of postponed S2-2002642 from S2-138E. Noted Peter Hedman (Ericsson) proposes to note the LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003538 LS In Information LS from CT WG1: Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs CT WG1 (C1-202846) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003539 LS In Information LS from CT WG1: LS on manual CAG selection CT WG1 (C1-202927) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003574 LS In Information LS from RAN WG2: Reply LS on manual CAG selection RAN WG2 (R2-2003870) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003530 LS In Action LS from RAN WG2: LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs RAN WG2 (R2-2002417) Rel-16 Revision of postponed S2-2002656 from S2-138E. Response drafted in S2-2003723. Final response in S2-2004335 Replied to
4.1 S2-2003640 LS OUT Approval [DRAFT] Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs vivo Rel-16 Response to S2-2003530. Revised to S2-2004335. Wen (vivo) provides r01.
==== Ph1 Revisions Deadline ====
Revised
4.1 S2-2004335 LS OUT Approval Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs SA WG2 Rel-16 Revision of S2-2003640_r01. Approved
==== Ph1 Revisions Deadline ====
Approved
4.1 S2-2003535 LS In Action LS from CT WG1: LS on manipulation of CAG Information element by a VPLMN CT WG1 (C1-202617) Rel-16 Response drafted in S2-2003600, S2-2003641 and S2-2004261. Final response in S2-2004453
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004261 LS OUT Approval [DRAFT] Reply LS on manipulation of CAG Information element by a VPLMN Samsung R&D Institute India Rel-16 Response, merging S2-2003641, to S2-2003535. Revised to S2-2004453.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004453 LS OUT Approval Reply LS on manipulation of CAG Information element by a VPLMN SA WG2 Rel-16 Revision of S2-2004261, merging S2-2003641. Approved Approved
4.1 S2-2004255 DISCUSSION Agreement Disc on manipulation of CAG Information element by a VPLMN. Samsung Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003601 CR Approval 23.501 CR2367 (Rel-16, 'F'): UE handling of CAG information Ericsson, Qualcomm Incorporated Rel-16 Merged into S2-2004313 Merged
4.1 S2-2004258 CR Approval 23.501 CR2380 (Rel-16, 'F'): Handling manipulation of CAG by VPLMN -Sol 1 Samsung Rel-16 Revised, merging S2-2003601, to S2-2004313 Revised
4.1 S2-2004313 CR Approval 23.501 CR2380R1 (Rel-16, 'F'): Handling manipulation of CAG by VPLMN -Sol 1 Samsung, Ericsson, Qualcomm Incorporated, InterDigital Rel-16 Revision of S2-2004258, merging S2-2003601. R02 agreed. Revised to S2-2004454 Devaki (Nokia) provides r0
Lalith (Samsung) confirms: Fine with re-wording proposed by Nokia. But, filename is corrected.
Qianghua (Huawei) provides r02
Xiaowan (vivo) provides comment to r02
Qianghua (Huawei) agrees with Vivo.
Peter Hedman (Ericsson) provides comments.
==== Ph1 Revisions Deadline ====
Lalith (Samsung) agrees with the comments from Peter Hedman (Ericsson). Thus proposes to select r02 as way forward.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004454 CR Approval 23.501 CR2380R2 (Rel-16, 'F'): Handling manipulation of CAG by VPLMN -Sol 1 Samsung, Ericsson, Qualcomm Incorporated, InterDigital, Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2004313_r02. This CR was agreed Agreed
4.1 S2-2004260 CR Approval 23.501 CR2381 (Rel-16, 'F'): Handling manipulation of CAG by VPLMN -Sol 2 Samsung Rel-16 Noted Peter Hedman (Ericsson) provides comments and proposes to note the CR.
Sebastian (Qualcomm) supports Peter and comments that the solution in 4313 is sufficient; further enhancements can be discussed in a later release. Sebastian (Qualcomm) objects to the CR.
==== Ph1 Revisions Deadline ====
Lalith (Samsung) proposes to note this CR(Sol-2). As sol-1 in 4313 is preferred way forward.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003600 LS OUT Approval LS reply on manipulation of CAG Information element by a VPLMN Ericsson Rel-16 Response to S2-2003535. Noted Qianghua (Huawei) provides r01
Lalith (Samsung) proposes to merge this LS into S2-2004261 and S2-2004301.
Guanzhou (InterDigital) agrees with Lalith (Samsung) suggestion to merge LSs.
Peter Hedman (Ericsson) provides comments and is ok to note the draft LS reply and use the other two LS replies.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2004302 CR Approval 23.501 CR2135R4 (Rel-16, 'F'): Updating the UE with new CAG information Ericsson??, Qualcomm Incorporated??, China Mobile?? InterDigital Rel-16 Revision of S2-2003249. Confirm Sources! Merged into S2-2004311 Merged
4.1 S2-2003599 CR Approval 23.501 CR2135R3 (Rel-16, 'F'): Updating the UE with new CAG information Ericsson, Qualcomm Incorporated, China Mobile Rel-16 Revision of (agreed) S2-2003249 from S2#138E. Revised, merging S2-2004302, to S2-2004311 Revised
4.1 S2-2004311 CR Approval 23.501 CR2135R5 (Rel-16, 'F'): Updating the UE with new CAG information Ericsson, Qualcomm Incorporated, China Mobile, InterDigital Rel-16 Revision of S2-2003599, merging S2-2004302. This CR was agreed Qianghua (Huawei) provides r01
Peter Hedman (Ericsson) provides comments and proposes to not use r01 as the proposed changes overlaps with S2-2004313. Please, consider original revision.
Qianghua (Huawei) agrees that MITM issue can be addressed in S2-2004313, we can consider the original revision for further updates
Xiaowan (vivo) provides r02
Hyunsook (LGE) comments.
Peter Hedman (Ericsson) provides comments and proposes to go with original version.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Agreed
4.1 S2-2003641 LS OUT Approval [DRAFT] Reply LS on manipulation of CAG Information element by a VPLMN vivo Rel-16 Response to S2-2003535. Merged into S2-2004453 Lalith (Samsung) proposes to merge this LS into S2-2004261.
Devaki (Nokia) agrees with Samsung proposal to note/merge the LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2004315 LS In Action LS from SA WG1: Reply LS on CMAS/ETWS and emergency services for SNPNs SA WG1 (S1-202220) Rel-16 Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2004317 LS In Information LS from SA WG1: Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs SA WG1 (S1-202265) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003602 CR Approval 23.502 CR2309 (Rel-16, 'F'): Handling of MRL with updated CAG information Ericsson Rel-16 Noted Devaki (Nokia) proposes to note this CR. It is not related to any LS, not in the agenda for this meeting.
Xiaowan (vivo) shares the view with Nokia to note this CR and provides comment.
Peter Hedman (Ericsson) provides comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004304 LS In Action LS from SA WG3: LS on protection of allowed CAG list against MITM Attack SA WG3 (S3-201414) Rel-16 Response drafted in S2-2004301. Final response in S2-2004455
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004301 LS OUT Approval [DRAFT] Reply LS on protection of allowed CAG list against MITM Attack InterDigital, Europe, Ltd. Rel-16 Response to S2-2004304. R04 agreed. Revised to S2-2004455 Qianghua (Huawei) provides comments.
Guanzhou (InterDigital) provides revision 1.
Qianghua (Huawei) provides R02.
Guanzhou (InterDigital) responds to Qianghua (HW) comments and objects to r02.
Qianghua (Huawei) disagrees with the responses.
Lalith Kumar (Samsung) agree with Guanzhou (InterDigital) and comments on r02.
Qianghua (Huawei) agrees with Lalith Kumar (Samsung) and provides r03 to reflect this.
Peter Hedman (Ericsson) provides r04
Guanzhou (InterDigital) is OK with r04
==== Ph1 Revisions Deadline ====
Qianghua (Huawei) is OK with r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004455 LS OUT Approval Reply LS on protection of allowed CAG list against MITM Attack SA WG2 Rel-16 Revision of S2-2004301_r04. Approved Approved
4.1 S2-2004322 LS In Information LS from SA WG1: Reply LS on manual CAG selection SA WG1 (S1-202277) Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 - - - Frame Routing Feature - - Docs:=12 -
4.1 S2-2003542 LS In Action LS from CT WG3: LS on Clarification of Support of Frame Routing Feature CT WG3 (C3-202350) Rel-16 Response drafted in S2-2003657 and S2-2003885. Final response in S2-2004456
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003657 LS OUT Approval [DRAFT] Reply LS on Clarification of Support of Frame Routing Feature Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003542. R02 agreed. Revised to S2-2004456 Haiyang (Huawei) provides r01 based on the discussion in 3886
Laurent (Nokia) provides r02
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004456 LS OUT Approval Reply LS on Clarification of the support of the Frame Routing Feature SA WG2 Rel-16 Revision of S2-2003657_r02 . Approved Approved
4.1 S2-2003655 CR Approval 23.501 CR2369 (Rel-16, 'F'): Clarification of the Support of the Frame Routing Feature Nokia, Nokia Shanghai Bell Rel-16 R03 agreed. Revised to S2-2004457 Haiyang (Huawei) provides r01 based on the discussion in 3886
Stefan (Ericsson) provides r02
Haiyang (Huawei) provides r03 as a cosigner
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004457 CR Approval 23.501 CR2369R1 (Rel-16, 'F'): Clarification of the Support of the Frame Routing Feature Nokia, Nokia Shanghai Bell, Ericsson, Huawei Rel-16 Revision of S2-2003655_r03. This CR was agreed Agreed
4.1 S2-2003656 CR Approval 23.502 CR2314 (Rel-16, 'F'): Clarification of Support of Frame Routing Feature Nokia, Nokia Shanghai Bell Rel-16 WITHDRAWN Laurent (Nokia): we withdraw S2-2003656 in order to discuss an unique 23.502 CR (the HW one) on the Support of Frame Route(s)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Withdrawn
4.1 S2-2003885 LS OUT Approval [DRAFT] LS Reply on clarification of Support of Frame Routing Feature Huawei, HiSilicon Rel-16 Response to S2-2003542. Noted Laurent (Nokia): we object to S2-2003885 in order to discuss an unique LS out (S2-2003657) on the Support of Frame Route(s)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003886 CR Approval 23.503 CR0470 (Rel-16, 'F'): Correction on Framed Routing information reporting Huawei, HiSilicon Rel-16 R04 agreed. Revised to S2-2004458 Laurent (Nokia): provides r01 and comments
Haiyang (Huawei) asks for clarification
Stefan (Ericsson) comments
Haiyang (Huawei) provides r02 based on r01
Laurent (Nokia) provides r03
Stefan (Ericsson) comments and provides r04
Laurent (nokia) answers and provides
Laurent (nokia) provides comments, r05 and r06
Haiyang (Huawei) comments
Stefan (Ericsson) agrees with Sun Haiyang comments and also prefers r04
Laurent (nokia) comments: Haiyang if you look at r06, it does not refer to SMF sets anymore
Haiyang (Huawei) clarifies the comments
==== Ph1 Revisions Deadline ====
Laurent (Nokia) prefers r06: if you look at r06, it does not refer to SMF sets anymore. It is just to not make BSF mandatory for all deployments
Haiyang (Huawei) prefers r04
Stefan (Ericsson) prefers r04 and objects to r05/r06
Laurent (Nokia) comment: to make it clear we accept r04 and can live with it
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004458 CR Approval 23.503 CR0470R1 (Rel-16, 'F'): Correction on Framed Route information reporting Huawei, HiSilicon, Nokia, Nokia Shaghai Bell, Ericsson Rel-16 Revision of S2-2003886_r04. This CR was agreed Agreed
4.1 S2-2003887 CR Approval 23.501 CR2373 (Rel-16, 'F'): Correction on Framed Routing information reporting Huawei, HiSilicon Rel-16 Noted Laurent (Nokia): we object to S2-2003887 in order to discuss an unique 23.501 CR on the Support of Frame Route(s)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003888 CR Approval 23.502 CR2319 (Rel-16, 'F'): Correction on Framed Routing information reporting Huawei, HiSilicon Rel-16 R05 agreed. Revised to S2-2004459 Haiyang (Huawei) provides r01 based on the discussion in 3886
Laurent (Nokia) aks a question on the 2 revisions in the 3888r01 zip file
Haiyang (Huawei) is OK with r03 and clarifies.
Stefan (Ericsson) provides r04
Mirko (Huawei) provides r05.
==== Ph1 Revisions Deadline ====
Laurent (Nokia) supports any revision from r03 on. So OK to approve 05.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004459 CR Approval 23.502 CR2319R1 (Rel-16, 'F'): Correction on Framed Route information reporting Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson Rel-16 Revision of S2-2003888_r05. This CR was agreed Agreed
4.1 - - - NA Info in BDT policy - - Docs:=9 -
4.1 S2-2003543 LS In Action LS from CT WG3: LS on Network Area Information in BDT Policy CT WG3 (C3-202420) Rel-16 Response drafted in S2-2004250. Final response in S2-2004460
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004250 LS OUT Approval [DRAFT] LS Reply to LS on Network Area Information in BDT Policy Nokia, Nokia Shanghai Bell Rel-16 Response, merging S2-2003868, to S2-2003543. R05 agreed. Revised to S2-2004460 Leo (DT) provides rev1
Sherry (Nokia) provides r02.
Mirko (Huawei) provides r03.
Sherry (Nokia) comments.
Sherry (Nokia) provides r04 and r05.
==== Ph1 Revisions Deadline ====
Mirko (Huawei) is ok with r03 or r05 and objects to the other versions.
Sherry (Nokia) is fine to go with r03 or r05.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004460 LS OUT Approval LS Reply to LS on Network Area Information in BDT Policy SA WG2 Rel-16 Revision of S2-2004250_r05 merging S2-2003868. Approved, Approved
4.1 S2-2004251 CR Approval 23.503 CR0474 (Rel-16, 'F'): Clarification on Network Area Information Nokia, Nokia Shanghai Bell Rel-16 Noted Sherry (Nokia) provides r01.
==== Ph1 Revisions Deadline ====
Jinguo(ZTE) comment.
Sherry (Nokia) replies and agrees to note this CR due to the conflicts with the approved Tdoc S2-2003502, expecting to resolve it by submitting a revision of S2-2003502 to SA plenary.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004252 CR Approval 23.502 CR2325 (Rel-16, 'F'): Clarification on Network Area Information Nokia, Nokia Shanghai Bell Rel-16 . Merged into S2-2004402
==== Ph1 Revisions Deadline ====
Sherry (Nokia) proposes to merge this paper into S2-2003870.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003868 LS OUT Approval [DRAFT] Reply LS on Network Area Information in BDT Policy (C3-202420) Huawei, HiSilicon Rel-16 . Merged into S2-2004460
==== Ph1 Revisions Deadline ====
Leo (Deutsche Telekom) proposes to mark this contribution MERGED into S2-2004250
Sherry (Nokia) proposes to mark this contribution MERGED into S2-2004250
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003869 CR Approval 23.503 CR0439R1 (Rel-16, 'F'): Correction of BDT policy re-negotiation description Huawei, HiSilicon Rel-16 Revision of S2-2002754. Noted Mirko (Huawei) provides r01.
Sherry (Nokia) proposes to merge this paper into 4251, as the major change in this CR doesn't address the issue raised in the CT3 LS.
Mirko (Huawei) responds to Nokia.
Belen (Ericsson) shares Nokia view, i.e.major change in this CR doesn't address the issue raised in the CT3 LS.
Belen (Ericsson) objects to this CR.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003870 CR Approval 23.502 CR2237R1 (Rel-16, 'F'): Correction of BDT policy re-negotiation procedure Huawei, HiSilicon Rel-16 Revision of S2-2002971. R04 agreed. Revised to S2-2004461 Sherry (Nokia) provides r01.
Mirko (Huawei) provides r02.
Sherry (Nokia) proposes to merge this paper into 4251, as the major change in this CR doesn't address the issue raised in the CT3 LS.
Sherry (Nokia) takes back the previous Nokia comment, and prefers r01.
Mirko (Huawei) responds to Nokia.
Belen (Ericsson) provide rev03
Mirko (Huawei) provide rev04
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004461 CR Approval 23.502 CR2237R2 (Rel-16, 'F'): Correction of BDT policy re-negotiation procedure Huawei, HiSilicon Rel-16 Revision of S2-2003870_r04. This CR was agreed Agreed
4.1 - - - TSN for Vertical_LAN - - Docs:=10 -
4.1 S2-2003546 LS In Action LS from CT WG3: LS on clarification on TSN for Vertical_LAN CT WG3 (C3-202515) Rel-16 Response drafted in S2-2003757, S2-2003889, S2-2003950 and S2-2004187. Final response in S2-2004462 zhendong (ZTE) provides the response to Ericsson.
Saso (Intel) comments and proposes LS replies according to the discussion so far.
Haiyang (Huawei) comments
Belen (Ericsson) comments
zhendong (ZTE) provides the comments.
Haiyang (Huawei) suggests a way forward.
Saso (Intel) disagrees that a CR is needed.
Haiyang (Huawei) comments.
zhendong (ZTE) provises the comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003757 LS OUT Approval [DRAFT] Reply LS on clarification on TSN for Vertical_LAN Intel Rel-16 Response to S2-2003546. Noted Haiyang (Huawei) proposes to 'merge' this LS to S2-2003889 to have a single LS.
Saso (Intel) proposes to NOTE S2-2003757 and use S2-2003889 instead.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003889 LS OUT Approval [DRAFT] LS Reply on clarifications on TSN for Vertical_LAN Huawei, HiSilicon Rel-16 Response, merging S2-2003950 and S2-2004187, to S2-2003546. R03 agreed. Revised to S2-2004462 Haiyang (Huawei) provides r01.
Saso (Intel) provides r02.
zhendong (ZTE) provides comments.
Haiyang (Huawei) prefers r01 as Saso (Intel) now is fine with the attachment (S2-2003891) based on the discussion
Belen (Ericsson) comments on Q1 reply and provides r03.
Haiyang (Huawei) is ok with r03
==== Ph1 Revisions Deadline ====
Saso (Intel) is OK with r03
zhendong (ZTE) is ok with r03
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004462 LS OUT Approval LS Reply on clarification on TSN for Vertical_LAN SA WG2 Rel-16 Revision of S2-2003889_r03, merging S2-2003950 and S2-2004187. Approved Approved
4.1 S2-2003949 DISCUSSION Discussion Discussion on the issue raised by CT WG3 LS (S2-2003546) on the TSN. ZTE Rel-16 Noted
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003891 CR Approval 23.502 CR2297R2 (Rel-16, 'F'): Missing important assumptions on how Npcf_PolicyAuthorization_Notify is used in TSN context Huawei, HiSilicon, [Intel] Rel-16 Revision of S2-2003244. R08 agreed. Revised to S2-2004463 zhendong (ZTE) provides the r01.
Saso (Intel) proposes to note the CR.
Haiyang (Huawei) provides r02.
zhendong (ZTE) provides comments to r02 and provides the r03.
Saso (Intel) objects to this CR.
Haiyang (Huawei) provides r04 based on r03 and clarifies.
Saso (Intel) withdraws objection for r04 and seeks clarification.
Devaki (Nokia) provides r05.
zhendong (ZTE) provide the comments
zhendong (ZTE) provides the response to intel.
Haiyang (Huawei) agrees the clarification from ZTE.
Saso (Intel) provides r06.
zhendong (ZTE) provides response.
Sebastian (Qualcomm) provides r07 to clarify the note about DS-TT MAC address in UE address.
Haiyang (Huawei) provides r08 based on r07.
==== Ph1 Revisions Deadline ====
Saso (Intel) is OK with r08 based.
zhendong (ZTE) r08 is fine
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004463 CR Approval 23.502 CR2297R3 (Rel-16, 'F'): Missing important assumptions on how Npcf_PolicyAuthorization_Notify is used in TSN context Intel, Huawei, HiSilicon Rel-16 Revision of S2-2003891_r08. This CR was agreed Agreed
4.1 S2-2003890 CR Approval 23.503 CR0471 (Rel-16, 'F'): Correction on the interaction between PCF and TSN AF Huawei, HiSilicon Rel-16 Noted Devaki (Nokia) proposes to Note this CR, 3891 is sufficient, this one is unnecessarily restrictive (to assume TSN AF is always pre-configured and that there is only one in the network).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003950 LS OUT Approval [DRAFT] Reply LS on clarification on TSN for Vertical_LAN ZTE Rel-16 Response to S2-2003546. Merged into S2-2004462 Haiyang (Huawei) proposes to 'merge' this LS to S2-2003889 to have a single LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2004187 LS OUT Approval [DRAFT] Reply LS on clarification on TSN for Vertical_LAN Ericsson Inc. Rel-16 Response to S2-2003546. Merged into S2-2004462 Haiyang (Huawei) proposes to 'merge' this LS to S2-2003889 to have a single LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 - - - PEI in Nudm_UECM_Registration - - Docs:=9 -
4.1 S2-2003547 LS In Action LS from CT WG4: LS on Presence of PEI in Nudm_UECM_Registration Requests CT WG4 (C4-202344) Rel-15 Response drafted in S2-2003613 and S2-2004145. Final response in S2-2004464
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004145 LS OUT Approval [DRAFT] Reply LS on Presence of PEI in Nudm_UECM_Registration Requests Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003547. R03 agreed. Revised to S2-2004464 Stefan (Ericsson) provides r02
Stefan (Ericsson) provides r03 to fix spec number
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004464 LS OUT Approval Reply LS on Presence of PEI in Nudm_UECM_Registration Requests SA WG2 Rel-16 Revision of S2-2004145_r03. Approved Approved
4.1 S2-2004144 CR Approval 23.502 CR2323 (Rel-16, 'F'): CR to Fix PEI inclusion in Nudm_UECM_Registration Nokia, Nokia Shanghai Bell Rel-16 . Merged into S2-2004466 Marco (Huawei) comment/clarification on PEI support between features (WWC).
Stefan (Ericsson) comments
Devaki (Nokia) comments.
Marco (Huawei) concern to this CR.
Stefan (Ericsson) objects to CR and comments
Marco Huawei (Ericsson) support to note the CR
Devaki (Nokia) proposes a compromise way forward, merging both Nokia and Ericsson papers. Proposes to make PEI conditional with clarity on the conditions
Devaki provides revision 2.
Stefan (Ericsson) proposes to consider this CR noted and/or merged into 3614/3615
==== Ph1 Revisions Deadline ====
Stefan (Ericsson) for the record objects to this CR and proposes to consider it merged into 3614/3615
Marco (Huawei) this shall be noted or considered merged into 3614/3615 (up to author)
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003613 LS OUT Approval Reply LS on 'LS on Presence of PEI in Nudm_UECM_Registration Requests' Ericsson Rel-15 Response to S2-2003547. Noted Devaki (Nokia) proposes to note and/or consider this as merged with S2-2004145.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003614 CR Approval 23.502 CR2310 (Rel-15, 'F'): Presence of PEI in Nudm_UECM_Registration Request Ericsson Rel-15 R04 agreed. Revised to S2-2004465 Marco (Huawei) see comment/clarification to S2-2004144.
Devaki (Nokia) objects to the CR as the PEI shouldn't be made optional.
Stefan (Ericsson) comments that the PEI is already optional
Stefan (Ericsson) objects to the CR.
Stefan (Ericsson) withdraws objection.
Devaki (Nokia) comments.
Marco (Huawei) support proposal this CR (for PEI optional).
Stefan (Ericsson) comments and provides r01
Devaki (Nokia) comments that r01 has not addressed our concern, thus our objection remains. Proposes to postpone this and the LS response.
Stefan (Ericsson) replies to Devaki
Marco (Huawei) not agree R01 changes to 'AMF shall retrieve...'
Stefan (Ericsson) comments and is of course OK also with original version
Stefan (Ericsson) provides r02
Devaki (Nokia) provides r03.
==== Ph1 Revisions Deadline ====
Marco (huawei) OK with r04.
Stefan (Ericsson) prefers r02 but can live with r04
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004465 CR Approval 23.502 CR2310R1 (Rel-15, 'F'): Presence of PEI in Nudm_UECM_Registration Request Ericsson, Nokia, Nokia Shanghai Bell Rel-15 Revision of S2-2003614_r04. This CR was agreed Agreed
4.1 S2-2003615 CR Approval 23.502 CR2311 (Rel-16, 'A'): Presence of PEI in Nudm_UECM_Registration Request Ericsson Rel-16 Mirror, merging S2-2004144, to S2-2003614_R04. Revised to S2-2004466.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004466 CR Approval 23.502 CR2311R1 (Rel-16, 'A'): Presence of PEI in Nudm_UECM_Registration Request Ericsson, Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2003615, merging S2-2004144. This CR was agreed Agreed
4.1 - - - Config params in Monitoring Events - - Docs:=6 -
4.1 S2-2003548 LS In Action LS from CT WG4: LS on Network Configuration Parameters in Monitoring Events CT WG4 (C4-202355) Rel-16 Response drafted in S2-2003616 and S2-2003861. Final response in S2-2004467
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004027 LS OUT Approval [DRAFT] ReplyLS on Network Configuration Parameters in Monitoring Events Huawei, HiSilicon Rel-16 Response to S2-2003548. Merged into S2-2004467 Judy (Ericsson) asks question.
Hannu (Nokia) supports the proposal to merge the two LSs and makes a further proposal that SA2 should consider this as Rel-16 item.
Hannu (Nokia) proposes a revision of the LS in 4027.
Qianghua (Huawei) suggests to merge this into S2-2003616.
Hannu (Nokia) agrees with Qianghua's comment to merge this LS into S2-2003616
Hannu (Nokia) provides r04 to align NOTE7 with CT4 warning note.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003616 LS OUT Approval Reply LS on 'LS on Network Configuration Parameters in Monitoring Events' Ericsson Rel-16 Response, merging S2-2004027, to S2-2003548. R05 agreed. Revised to S2-2004467 Qianghua (Huawei) provides comments.
Hannu (Nokia) provides r01.
Qianghua (Huawei) provides comments and r02.
Judy (Ericsson) provides r04. Please skip r03 which has 0 byte.
Qianghua (Huawei) provides r05.
Judy (Ericsson) can live with r05
Hannu (Nokia) can agree r05 that adds a warning on parallel provisioning methods without deleting anything yet.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004467 LS OUT Approval Reply LS on 'LS on Network Configuration Parameters in Monitoring Events' SA WG2 Rel-16 Revision of S2-2003616_r05, merging S2-2004027. Approved Approved
4.1 S2-2003617 CR Approval 23.502 CR2312 (Rel-16, 'F'): Network Parameters Configuration by Parameter Provisioning and Event Exposure Subscription Ericsson Rel-16 R06 agreed. Revised to S2-2004468 Hannu (Nokia) proposes a revision of the CR.
Judy (Ericsson) responds and provides r02.
Qianghua (Huawei) proposes to go with the original and cannot accept R01 and R02.
Hannu (Nokia) provides r03
Qianghua (Huawei) provides r05.
Judy (Ericsson) provides r06.
Hannu (Nokia) provides r07 and comments.
Qianghua (Huawei) provides responses.
==== Ph1 Revisions Deadline ====
Qianghua (Huawei) provides a preference order (high->low) for the acceptable version:
r06 -> r05 -> r00
Judy (Ericsson) prefers r06/r00, can accept r05/r07.
Hannu (Nokia) preference order: r07 -> r06 -> r04. The other versions are not good.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004468 CR Approval 23.502 CR2312R1 (Rel-16, 'F'): Network Parameters Configuration by Parameter Provisioning and Event Exposure Subscription Ericsson Rel-16 Revision of S2-2003617_r06. This CR was agreed Agreed
4.1 - - - Interworking with ETSUN - - Docs:=9 -
4.1 S2-2003549 LS In Action LS from CT WG4: LS on which features cannot interwork with ETSUN CT WG4 (C4-202536) Rel-16 Response drafted in S2-2003706 and S2-2004124. Final response in S2-2004443
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003706 LS OUT Approval [DRAFT] Reply LS on which features cannot interwork with ETSUN Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003549. WITHDRAWN Laurent (Nokia): based on the agreed Tdoc work split Nokia withdraws S2-2003706
==== Ph1 Revisions Deadline ====
Withdrawn
4.1 S2-2004124 LS OUT Approval [DRAFT] LS response on which features cannot interwork with ETSUN Huawei,HiSilicon Rel-16 Response to S2-2003549. R04 agreed. Revised to S2-2004443. Fenqin (Huawei): provides r01 version per CC.
Laurent (Nokia): provides a proposed work split to avoid duplication of effort.
Laurent (Nokia): provides r02 and comments (it may be better to work first on the CR)
Fenqin (Huawei): provides comments and r03
Fenqin (Huawei): provides feedback.
Laurent (Nokia): provides comment and r04
Laurent (Nokia): provides comments
Fenqin (Huawei): provides comments and r05 version.
Fenqin (Huawei): provides comments and suggest go back to r04 version.
==== Ph1 Revisions Deadline ====
Laurent (Nokia) we suggest to freeze the status of S2-2004124 until the CC tomorrow as it depends on the result of S2-2003705 and S2-2004126 which are at the agenda of this CC. otherwise we support r04 and object to other versions
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004443 LS OUT Approval LS Response on which features cannot interwork with ETSUN SA WG2 Rel-16 Revision of S2-2004124_R04. Approved Approved
4.1 S2-2004125 CR Approval 23.501 CR2375 (Rel-16, 'F'): Interworking between ETSUN and URLLC/TSN Huawei, HiSilicon, China Mobile Rel-16 Noted Laurent (Nokia): based on the agreed Tdoc work split Nokia 'objects' to S2-2004125
Dan (China Mobile) supports this paper, and comments to Laurent's objection
* Shabnam (Ericsson) assumes that we progress S2-2003705 and provides revision on that thread.
*
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004126 CR Approval 23.502 CR2322 (Rel-16, 'F'): Interworking between ETSUN and URLLC/TSN Huawei, HiSilicon,China Mobile Rel-16 Revised to S2-2004441. Laurent (Nokia): provides 2 revisions
Fenqin (Huawei): comments and provides r03.
Laurent (Nokia): comments and provides r04.
Shabnam (Ericsson) provides r05 aligned with 23.501 updated proposed.
zhendong (ZTE) provides r06.
Laurent (Nokia) provides r07.
Shabnam (Ericsson) provides r08.
Laurent (Nokia) provides r09.
Fenqin (Huawei) provides r10
==== Ph1 Revisions Deadline ====
Laurent (Nokia) objects to any revision of S2-2004126 so that this is further discussed off line and decided upon at the CC tomorrow
==== Ph1 Final Deadline ====
Fenqin (Huawei): provides the updated version per offline discussion.
Fenqin (Huawei): a small update and upload it on the draft folder.
Fenqin (Huawei): provide r04 version.
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004441 CR Approval 23.502 CR2322R1 (Rel-16, 'F'): Interworking between ETSUN and URLLC/TSN Huawei, HiSilicon,China Mobile, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Rel-16 Revision of S2-2004126. This CR was agreed Agreed
4.1 S2-2003705 CR Approval 23.501 CR2371 (Rel-16, 'F'): URLLC - TSN interworking with ETSUN Nokia, Nokia Shanghai Bell Rel-16 Revised to S2-2004442. Laurent (Nokia): provides r01 based on feedback received at the SA2 CC
Dan Wang (China Mobile) do not agree with the URLLC part in this CR and we would like to see the ETSUN supporting QoS monitoring and Dynamic CN PDB, therefore object to this CR.
* Shabnam (Ericsson) provides r02 and explains the reasons for the updates.
*
Laurent (Nokia) provides r03 and explains the reasons for the updates.
Fenqin(Huawei) provides r04.
Laurent (Nokia) provides comments and r05.
Fenqin(Huawei) provides comment.
Dan (China Mobile) is OK with r05
Shabnam (Ericsson) provides r06 clarifying TSC and URLLC, see details below.
Shabnam (Ericsson) responds to Huawei comments.
Fenqin(Huawei) provides comment and r07.
Laurent Nokia) provides r08.
Laurent Nokia) provides r09.
Shabnam (Ericsson) objects to r08.
Laurent Nokia) provides r09 and comments
Stefan (Ericsson) comments
Shabnam (Ericsson) objects to r09, see the statement that we consider is wrong.
==== Ph1 Revisions Deadline ====
Laurent (Nokia) objects to any revision so that this is further discussed off line and decided upon at the CC tomorrow
Laurent (Nokia) objects to any revision of S2-2003705 so that this is further discussed off line and decided upon at the CC tomorrow
Dan(China Mobile) reply to Laurent's object and maybe at least support what Laurent has provided version i.e.r05.
==== Ph1 Final Deadline ====
Laurent (nokia) shares a revision that has been discussed off-line and that is proposed for approval tomorrow during CC#2
Fenqin(Huawei) upload the document to the draft folders
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004442 CR Approval 23.501 CR2371R1 (Rel-16, 'F'): URLLC - TSN interworking with ETSUN Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE Rel-16 Revision of S2-2003705. This CR was agreed Agreed
4.1 - - - IAB supporting in NPN - - Docs:=6 -
4.1 S2-2003577 LS In Action LS from RAN WG2: LS on IAB supporting in NPN deployment RAN WG2 (R2-2004282) Rel-16 Response drafted in S2-2004161 and S2-2004278. Final response in S2-2004469
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004161 LS OUT Approval [DRAFT] Reply LS on IAB supporting in NPN deployment Huawei, Hisilicon Rel-16 Response to S2-2003577. Merged into S2-2004469 Hong (Qualcomm Inc.) comments and propose to merge this LS into S2-2004278.
Wanqiang (Huawei) provided feedback
Hong (Qualcomm Inc.) provides comments.
==== Ph1 Revisions Deadline ====
Wanqiang (Huawei) is ok with the merge into 4278.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2004278 LS OUT Approval [DRAFT] Reply LS on IAB supporting in NPN deployment Qualcomm Incorperated Rel-16 Response, merging S2-2004161, to S2-2003577. R01 agreed. Revised to S2-2004469 Wanqiang (Huawei) comments and provides r01.
Hong (Qualcomm Inc.) is OK with r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004469 LS OUT Approval Reply LS on IAB supporting in NPN deployment SA WG2 Rel-16 Revision of S2-2004278_r01, merging S2-2004161. Approved Approved
4.1 S2-2004281 CR Approval 23.501 CR2382 (Rel-16, 'F'): IAB support in NPN deployment Qualcomm Incorporated, AT&T Rel-16 R03 agreed. Revised to S2-2004470 Hong (Qualcomm Inc.) provides r01.
Mehrdad (Samsung) provides comment on original version and r01.
Hong (Qualcomm Inc.) responds to Mehrdad (Samsung).
Mehrdad (Samsung) provides comment.
Devaki (Nokia) uploads r02.
Wanqiang (Huawei) ok with r02.
David (Kyocera) requests to add Kyocera to CR.
Hong (Qualcomm Inc.) provides r03.
==== Ph1 Revisions Deadline ====
Mehrdad (Samsung) is OK with r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004470 CR Approval 23.501 CR2382R1 (Rel-16, 'F'): IAB support in NPN deployment Qualcomm Incorporated, AT&T, Ericsson, Nokia, Kyocera Rel-16 Revision of S2-2004281_r03. This CR was agreed Agreed
4.1 - - - Alternative QoS profile - - Docs:=12 -
4.1 S2-2003578 LS In Action LS from RAN WG3: LS on Stage 3 for V2X QoS RAN WG3 (R3-202856) Rel-16 Response drafted in S2-2003911 and S2-2004242. Final response in S2-2004445
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003911 LS OUT Approval [DRAFT] Reply LS on Stage 3 for V2X QoS Huawei Rel-16 Response to S2-2003578. Noted LaeYoung (LGE) proposes to NOTE this draft LS and progress S2-2004242 (Vodafone).
Sherry (Nokia) proposes to NOTE this draft LS and progress S2-2004242 (Vodafone).
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) confirms that this LS can be NOTED.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003909 DISCUSSION Agreement Discussion on way forward for content of Alternative QoS Profiles. Huawei, HiSilicon Noted LaeYoung (LGE) proposes to NOTE this paper because SA2 already agreed to take the RAN3 suggested parameters for AQP and align SA2 specs with the RAN3 WA.
Chris (Vodafone) comments that at least MDBV may be needed.
Sherry (Nokia) proposes to NOTE this paper because SA2 already agreed to take the RAN3 suggested parameters for AQP and align SA2 specs with the RAN3 WA.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003910 CR Approval 23.501 CR2228R1 (Rel-16, 'F'): Correction of Alternative QoS Profile handling Huawei, HiSilicon Rel-16 Revision of S2-2002697. Merged into S2-2004471 Sherry (Nokia) proposes to NOTE this paper or merge it into 4228.
LaeYoung (LGE) also proposes to NOTE this CR or merge it into 4228.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003618 CR Approval 23.502 CR2313 (Rel-16, 'F'): Alignment with RAN stage 3 on Alternative QoS Profile Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Interdigital, ZTE, CATT Rel-16 This CR was agreed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Agreed
4.1 S2-2003704 CR Approval 23.501 CR2370 (Rel-16, 'F'): Alignment on Alternative QoS Profile Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell Rel-16 Revised to S2-2004444 Leo (DT) asks for clarification.
LaeYoung (LGE) provides answer.
Dario (Huawei) provides comments and r01.
Rev 01 is acceptable to Vodafone but Chris expects others to object. Hence Chris (Vodafone) provides comments and r02.
Rev 0 is not acceptable as the originators have failed to address pre-meeting, onlist questions sent 1719 UTC 20/5/20.
Sherry (Nokia) comments.
Dario (Huawei) replies pointing out that no technical justifications where provided for not including the proposed parameters.
Chris (Vodafone)provides r03 that just adds MDBV.
Paul Schliwa-Bertling (Ericsson) provides r04. Content is kept aligned with SA2 agreement to align with the RAN3 CRs. Chris' new text added as a note.
Dario (Huawei) provides r05 and re-instates his previous question on why parameters are not needed.
Chris (Vodafone) comments.
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) accepts r00 and r04, is fine with r02 and object to r01, r03 and r05.
Sherry (Nokia) agrees with r00 and r04, can live with r02 and objects to r01, r03 and r05.
Antoine (Orange) supports r05 and requests to open this CR during CC#2.
Paul Schliwa-Bertling (Ericsson) agrees with r00 and r04 and objects to r01, r02, r03 and r05.
Dan(China Mobile) supports r05 and also supports the discussion in CC#2
Chris (Vodafone) also supports the discussion in CC#2.
Dario (Huawei) asks to open this CR during CC#2.(supports r01, r05 and objects the other revisions)
Mario (Telecom Italia) I'll not able to attend CC#2 tomorrow but I support r01, r05 and object the other revisions.
Sherry (Nokia) proposes to agree either r00 or r04 and objects to open this CR during CC#2 as this issue is already concluded before the meeting.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004444 CR Approval 23.501 CR2370R1 (Rel-16, 'F'): Alignment on Alternative QoS Profile Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2003704. This CR was agreed Agreed
4.1 S2-2004242 LS OUT Approval [DRAFT] Reply LS on Stage 3 for V2X QoS VODAFONE Group Plc Rel-16 Response to S2-2003578. R04 agreed. Revised to S2-2004445. Chris (Vodafone) provides r01 to address Ericsson and Nokia comments made in CC#1 folder
Sherry (Nokia) provides r02.
Haris (Qualcomm) provides r03 not for immediate agreement but as backup plan in case no agreement is reached on the alignment CRs
Sherry (Nokia) provides r04.
Chris (Vodafone) provides r05 to add MDBV.
Chris (Vodafone) provides r06 to add MDBV.
Please withdraw r05.
Paul Schliwa-Bertling (Ericsson) provides r07.
It is clarified that NG-RAN node should be able to notify the SMF that the lowest priority Alternative QoS Profile cannot be supported.
Dario (Huawei) provides r08.
Chris (Vodafone) says that the text in R07 does not address the issue and is not acceptable..
Hong (Qualcomm Inc.) comments and thinks r07 addressed the NG-RAN indications.
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) proposes to go with r07.
r00, r01, r05 and r06 are not acceptable. If there is no version acceptable, not sending reply LS to RAN3 is fine.
Sherry (Nokia) accepts r04 and r07, and objects to r00, r01, r05, r06 and r08.
Paul Schliwa-Bertling (Ericsson) prefers r07, can live with r08 and r04 and objects to r00, r01, r02, r03, r05, r06.
Dario (Huawei) asks to open this document during CC#2 (supports r08 and objects all other revisions)
Chris (Vodafone) this draft o/g LS needs to be updated by CC#2 to reflect the outcome on the other Alt QoS CRs.
Sherry (Nokia) objects to open this document during CC#2, as there's no controversial issue, and convergence is achieved to the related CR (S2-2004228).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004445 LS OUT Approval Reply LS on Stage 3 for V2X QoS SA WG2 Rel-16 Revision of S2-2004242_R04. Approved Approved
4.1 S2-2004228 CR Approval 23.501 CR2379 (Rel-16, 'F'): Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles Vodafone Rel-16 R04 agreed. Revised, merging S2-2003910, to S2-2004471 Sherry (Nokia) provides r01.
Paul Schliwa-Bertling (Ericsson) provides r02.
Sherry (Nokia) provides r03.
Chris (Vodafone) provides rev 04.
Mirko (Huawei) provides r05.
==== Ph1 Revisions Deadline ====
Sherry (Nokia) can accept r03, r04 and r05.
LaeYoung (LGE) proposes to go with r04 and can live with r01 and r03. r05 is not acceptable. The coversheet of r00 and r02 is not preferred.
Paul Schliwa-Bertling (Ericsson) accepts r03, r02, r04 and r05 and objects to r00, r01.
Chris (Vodafone) objects to r01, r02, r03 but supports r0, r4, r5
Dario (Huawei) supports r05; can live with r04 and r00; objects the other revisions.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004471 CR Approval 23.501 CR2379R1 (Rel-16, 'F'): Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles Vodafone Rel-16 Revision of S2-2004228_r04, merging S2-2003910. This CR was agreed Agreed
4.1 S2-2004241 CR Approval 23.503 CR0472 (Rel-16, 'F'): Update about Alternative QoS Profile Nokia, Nokia Shanghai Bell, Ericsson, CATT, LGE, ZTE, Samsung, InterDigital Rel-16 This CR was agreed Dario (Huawei) provides comments and r01.
Sherry (Nokia) comments.
Chris(Vodafone) provides r02 that adds MDBV to r00.
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) proposes to approve r00 and objects to r01 and r02.
Sherry (Nokia) proposes to approve r00 and objects to r01 and r02.
Chris (Vodafone) states that we are rushing into a big, late change from RAN 3 and companies objecting to r02 (keeping MDBV in the Alt QoS Profile) should provide some technical rationale for that objection. Delegates seem to have forgotten that MDBV is linked to the 'instantaneous bit rate' while GFBR is the long term average bit rate, and it is the 'instantaneous bit rate' that is impacting on the RAN node (which is why we added MDBV in R15).
Antoine (Orange) explains why AQP is needed, supports r01 and requests to open this CR during CC#2.
Antoine (Orange) explains why *ARP* is needed, supports r01 and requests to open this CR during CC#2.
Shabnam (Ericsson) comments on Orange narrative.
Dario (Huawei) asks to open this CR during CC#2 (supports r01, objects r00 and r02).
Mario (Telecom Italia) I'll not able to attend CC#2 tomorrow but I support r01 and object r00 and r02.
Sherry (Nokia) proposes to approve r00 and objects to open this CR during CC#2.
Chris (Vodafone) states that this CR is clearly part of a topic that needs to be discussed during CC#2.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Agreed
4.1 - - - DAPS HO - - Docs:=8 -
4.1 S2-2003579 LS In Action LS from RAN WG3: LS on S1/NG DAPS handover RAN WG3 (R3-202932) Rel-16 Response drafted in S2-2003861 and S2-2004010. Final response in S2-2004474
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003861 LS OUT Approval [DRAFT] Reply LS on S1/NG DAPS handover QUALCOMM Europe Inc. - Italy Rel-16 Response to S2-2003579. Noted Laurent (Nokia): objects to any version of S2-2003861 (in order to have an unique version of the LS out for discussion)
Juan Zhang (Qualcomm) is OK to note the paper.
Juan Zhang (Qualcomm) is OK to note S2-2003861..
Laurent (Nokia) question to Juan: are you ok to note / withdraw 3861 and work on revisions of 4010?
Juan Zhang (Qualcomm) is OK to note 3861 and work on revisions of 4010
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003848 CR Approval 23.401 CR3602 (Rel-16, 'F'): Alignment CR for DAPS HO Qualcomm Incorporated Rel-16 R05 agreed. Revised to S2-2004472 Qian Chen (Ericsson) provides r01 and asks question.
Juan Zhang (Qualcomm) provides r02
Juan Zhang (Qualcomm) provides r03
Chris (Vodafone) provides r04
Laurent (Nokia) provide r05
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004472 CR Approval 23.401 CR3602R1 (Rel-16, 'F'): Alignment CR for DAPS HO Qualcomm Incorporated, Ericsson Rel-16 Revision of S2-2003848_r05. This CR was agreed Agreed
4.1 S2-2003860 CR Approval 23.502 CR2318 (Rel-16, 'F'): Alignment CR for DAPS HO Qualcomm Incorporated Rel-16 R07 agreed. Revised to S2-2004473 Qian Chen (Ericsson) provides r01 and asks question.
LiMeng (Huawei) provides r02 and ask questions for clarification.
Juan Zhang (Qualcomm) agree with r02 and comments.
Qian Chen (Ericsson) provides comments.
LiMeng (Huawei) provides comments.
Hucheng(CATT) comments.
Laurent (Nokia) provides r03.
Juan Zhang (Qualcomm) provides r04 to update the user plane path in the call flow
Hucheng(CATT) supports r04 and would like to co-sign it
Juan Zhang (Qualcomm)provides r05 with the only change that adding CATT as co-signer.
Yang Xu (OPPO) provides comments
Chris (Vodafone) provide r06
Laurent (Nokia) provide r07
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004473 CR Approval 23.502 CR2318R1 (Rel-16, 'F'): Alignment CR for DAPS HO Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, CATT Rel-16 Revision of S2-2003860_r07. This CR was agreed Agreed
4.1 S2-2004010 LS OUT Approval [DRAFT] Reply LS on S1/NG DAPS handover Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003579. R04 agreed. Revised to S2-2004474 Laurent (Nokia): provides r01 as per conclusions of SA2 139e CC1
Juan Zhang (Qualcomm) provides r02.
LiMeng (Huawei) provides r03.
LiMeng (Huawei) provides r04.
==== Ph1 Revisions Deadline ====
Laurent (Nokia) objects to r03 (not in the spirit of the agreement of the SA2 CC)
Wanqiang (Huawei) comments
Juan Zhang (Qualcomm) can agree either r03 or r04.
Laurent (Nokia) answers to comments
Wanqiang (Huawei) ok with the r04 to go to make progress.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004474 LS OUT Approval Reply LS on S1/NG DAPS handover SA WG2 Rel-16 Revision of S2-2004010_r04. Approved Approved
4.1 - - - V2X subscription - - Docs:=4 -
4.1 S2-2003541 LS In Action LS from CT WG3: LS on subscription to V2X services CT WG3 (C3-202347) Rel-16 Response drafted in S2-2003908. Final response in S2-2004475
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003908 LS OUT Approval [DRAFT] Reply LS on subscription to V2X Services Huawei Rel-16 Response to S2-2003541. R08 agreed. Revised to S2-2004475 Changhong (Intel) provides r01 and suggests noting the corresponding CR-0140 in S2-2003907.
Sherry (Nokia) provides r01.
Belen (Ericsson) provides r02.
Sherry (Nokia) provides r03.
LaeYoung (LGE) provides r04.
Changhong (Intel) provides r05.
Hao Dong (ZTE) provides comment.
LaeYoung (LGE) provides r06.
LaeYoung (LGE) answers to Q from Hao Dong (ZTE).
Sherry (Nokia) provides comments.
Sherry (Nokia) provides r07.
HaoDong (ZTE) provides comment.
LaeYoung (LGE) provides r08.
LiMeng (Huawei) provides r09.
Changhong (Intel) is fine with r08 but not OK with r09.
Belen (Ericsson)provides r10
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) proposes to go with r08.
Changhong (Intel) also proposes to go with r08.
Sherry (Nokia) proposes to go with r08.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004475 LS OUT Approval Reply LS on subscription to V2X services SA WG2 Rel-16 Revision of S2-2003908_r08. Approved Approved
4.1 S2-2003907 CR Approval 23.287 CR0140 (Rel-16, 'F'): On Subscription to V2X services Huawei, HiSilicon Rel-16 Noted Changhong (Intel) proposes to note the paper and provides reasons.
Sherry (Nokia) provides r01.
Belen (Ericsson) provides r02.
LaeYoung (LGE) comments.
LaeYoung (LGE) provides r03.
Changhong (Intel) objects to the original version and any following revision.
LaeYoung (LGE) is fine to NOTE this CR.
Sherry (Nokia) can live with r01 or r03, and also fine to note this CR.
Belen (Ericsson) comments.
Sherry (Nokia) comments.
Belen (Ericsson) replies to comments and proves r03
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) confirms this CR can be NOTED.
Changhong (Intel) double confirms this CR can be NOTED.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 - - - Slice specific authentication - - Docs:=8 -
4.1 S2-2003550 LS In Action LS from SA WG3: Reply LS on AUSF role in slice specific authentication SA WG3 (S3-200821) Rel-16 Response drafted in S2-2003745. Final response in S2-2004476
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003745 LS OUT Approval [DRAFT] Reply LS on NSSAAF in slice specific authentication ZTE Wistron Telecom AB Rel-16 Response to S2-2003550. Revised to update attachments in S2-2004476. Patrice(Huawei) comments that an update will be required for the Tdoc numbers.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004476 LS OUT Approval Reply LS on NSSAAF in slice specific authentication SA WG2 Rel-16 Revision of S2-2003745. Approved Approved
4.1 S2-2003743 CR Approval 23.501 CR2372 (Rel-16, 'F'): Replacing AUSF by NSSAAF to support NSSAA ZTE, Ericsson, Qualcomm, Nokia, Nokia shanghai Bell Rel-16 R01 agreed. Revised to S2-2004477 Patrice(Huawei) comments and provides r1 (objects to r0).
Peter Hedman (Ericsson) provides comments.
Alessio (nokia) provides comments.
Patrice (Huawei) comments, sustains objection to original version, proposes r02 as an alternative.
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) accepts r02, but suggests author allowed to change 'network slice specific authentication' and 'slice specific authentication' to 'NSSAA' in clause 6.3.x
Tricci (ZTE) accepts r02 and agrees with Ericsson's comment to use consistent term - NSSAA.
Alessio(Nokia) Question: what is the reason why because of NPN we need S-NSSAI based NSSAAF selection but not AUSF or UDM selection? Mind you we are considering the same PLMN here. Depending on answer I will decide whether to support r01 or r02.
Peter Hedman (Ericsson) provides reply to Alessio.
Alessio(Nokia) we have to be consistent with UDM and AUSF selection, so we should use the NID. Hence we prefer r0. Patrice can you motivate why the NID is not good since it is used already for UDM and AUSF?
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004477 CR Approval 23.501 CR2372R1 (Rel-16, 'F'): Replacing AUSF by NSSAAF to support NSSAA ZTE, Ericsson, Qualcomm, Nokia, Nokia shanghai Bell Rel-16 Revision of S2-2003743_r01. This CR was agreed Agreed
4.1 S2-2003744 CR Approval 23.502 CR2316 (Rel-16, 'F'): Replacing AUSF by NSSAAF to support NSSAA ZTE, Ericsson, Nokia, Nokia Shanghai Bell. Rel-16 This CR was agreed Patrice(Huawei) comments and provides r1 (merges content from S2-2004165).
Peter Hedman (Ericsson) provides r02.
Patrice (Huawei) comments, prefers that we go with the original CR for now despite its lack of completeness (thus formally, objects to r02)
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) ok with original CR (r00) or r02 (i.e. OBJECTS to r01) and clarifies that for Rel-16 we can only accept FASMO/alignments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Agreed
4.1 S2-2004164 CR Approval 23.501 CR2376 (Rel-16, 'F'): Unsubscribe the notification of Re-authentication and Re-authorization or Revocation Huawei, HiSilicon Rel-16 Noted Peter Hedman (Ericsson) provides comments and objects to the CR.
Hoyeon (Samsung) propose to note or postpone the CR.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004165 CR Approval 23.502 CR2324 (Rel-16, 'F'): Unsubscribe the notification of Re-authentication and Re-authorization or Revocation Huawei, HiSilicon Rel-16 Noted Peter Hedman (Ericsson) provides comments and objects to the CR.
Hoyeon (Samsung) propose to object the CR.
Patrice (Huawei) comments, agrees to postpone
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) proposes to note the CR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 - - - Other - - Docs:=67 -
4.1 S2-2003526 LS In Action LS from CT WG1: LS on the applicability of LADN in an SNPN CT WG1 (C1-200994) Rel-16 Revision of postponed S2-2002639 from S2-138E. Response drafted in S2-2003664. Final response in S2-2004478
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003664 LS OUT Approval [DRAFT] Reply LS on the applicability of LADN in an SNPN LG Electronics Rel-16 Response, merging S2-2003723, to S2-2003526. R02 agreed. Revised to S2-2004478 Chen (OPPO) provides r01.
Patrice (Huawei) comments, provides r02.
Hyunsook (LGE) provides a comment.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004478 LS OUT Approval Reply LS on the applicability of LADN in an SNPN SA WG2 Rel-16 Revision of S2-2003664_r02, merging S2-2003723. Approved Approved
4.1 S2-2003723 LS OUT Approval [DRAFT] Reply LS on applicability of LADN in an SNPN OPPO Rel-16 Response to S2-2003526. Merged into S2-2004478 Chen (OPPO) proposes to merge S2-2003723 into rev of S2-2003664.
Hyunsook (LGE) proposes it to be marked as 'merged into revision of S2-2003664'
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003523 LS In Action LS from ETSI TC LI: LS on making PSCELL ID available at the SGW of EPC ETSI TC LI (LI(20)P53048r2) Revision of postponed S2-2002625 from S2-138E. Noted Qian Chen (Ericsson) Propose to NOTE the LS since no paper related to the LS is submitted to this meeting
Leo (Deutsche Telekom) Propose to POSTPONE the LS since no paper related to the LS is submitted to this meeting. It is a valid requirement SA2 needs to work on.
Qian Chen (Ericsson) agrees to postpone the LS
Hannu (Nokia) volunteers to contribute on this in Rel-17 and asks whether to note or to postpone the LS?
Leo (Deutsche Telekom) agrees with Hannu and volunteers to provide reply-LS for the next SA2 meeting.
Hannu (Nokia) proposes to note the incoming LS.
Leo (Deutsche Telekom) is fine with the proposal made by Hannu (Nokia).
Wanqiang (Huawei) proposes to postpone the incoming LS.
Hannu (Nokia) supports Wanqiang (Huawei) who proposes to postpone the incoming LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003513 LS In Action LS from ETSI TC LI: LS to SA WG5 and SA WG2 on 5G Cell ID(s) in the SA WG5 billing system, related to Retained Data regulations ETSI TC LI (LI(19)P52055) Revision of postponed S2-2002607 from S2-138E. Noted Qian Chen (Ericsson) Propose to NOTE the LS since no paper related to the LS is submitted to this meeting
Leo (Deutsche Telekom) Propose to POSTPONE the LS since no paper related to the LS is submitted to this meeting.
Qian Chen (Ericsson) agrees with to postpone the LS
Hannu (Nokia) volunteers to contribute on Rel-17 and asks for guidance on whether to note or postpone the LS?
Andy (Vice Chair, Samsung) suggests we could note the LS.
Leo (Deutsche Telekom) prefers to reply, as mentioned by Andy, but would not object to note the LS.
Hannu (Nokia) proposes to note the incoming LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003531 LS In Action LS from RAN WG3: LS on NAS Non delivery for RRC Inactive state RAN WG3 (R3-201362) Rel-15 Revision of postponed S2-2002658 from S2-138E. Response drafted in S2-2003805. Final response in S2-2004452 Replied to
4.1 S2-2003805 LS OUT Approval [DRAFT] Reply LS on NAS Non delivery for RRC Inactive state Cisco Systems Rel-15 Response to S2-2003531. R06 agreed. R06 agreed. Revised to S2-2004452 Irfan (Cisco) provides r01.
Fenqin (Huawei) comments and provide a R02 version.
Hannu (Nokia) comments and provides r03.
Fenqin (Huawei) comments.
Hannu (Nokia) comments and provides r04
Qian Chen (Ericsson) asks questions for clarification
Hannu (Nokia) provides r05 and answers to questions from Fenqin and Qian.
Irfan (Cisco) provides r06
Hannu (Nokia) supports r06 by Irfan (Cisco)
Hannu (Nokia) replies to Fenqin (Huawei) supports r06 by Irfan (Cisco)
Qian Chen (Ericsson) is ok with r06
==== Ph1 Revisions Deadline ====
Hannu (Nokia) proposes that r06 should be marked 'approved' in the Chairman's Report
Fenqin (Huawei) agree to go with r06.
Juan Zhang (Qualcomm) is OK with r06.
Andy (Vice Chair, Samsung) allocates S2-2004452 for the approved r06.
Revised
4.1 S2-2004452 LS OUT Approval Reply LS on NAS Non delivery for RRC Inactive state SA WG2 Rel-15 Revision of S2-2003805r06. Approved Approved
4.1 S2-2003515 LS In Action LS from SA WG5: LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF SA WG5 (S5-197495) Revision of postponed S2-2002609 from S2-138E. Response drafted in S2-2004247. Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004249 CR Approval 23.503 CR0473 (Rel-16, 'F'): Alignment with SA WG5 on Introduction of CHF Address from PCF Nokia, Nokia Shanghai Bell Rel-16 Noted Belen (Ericsson) objects to this CR
Mirko (Huawei) objects to the CR.
Sherry (Nokia) comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004247 LS OUT Approval [DRAFT] LS Reply to LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003515. Noted Belen (Ericsson) propose to NOTE this LS out.
Mirko (Huawei) provides r01.
Belen (Ericsson) is fine with r01 and also fine to note the LS since the LS out is not strictly needed.
Sherry (Nokia) is fine to note the LS.
Mirko (Huawei) responds to Nokia.
Sherry (Nokia) would like to note this LS reply.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003521 LS In Action LS from SA WG3LI: LS on uniqueness of PEI in certain FN-RG configurations SA WG3LI (s3i200069) Revision of postponed S2-2002623 from S2-138E. Response drafted in S2-2003684. Final response in S2-2004479
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003683 CR Approval 23.316 CR2045 (Rel-16, 'F'): Corrections to description of lawful intercept Ericsson, Nokia, Nokia Shanghai Bell Rel-16 This CR was agreed Marco (Huawei) comment/clarification on PEI support between features .See also comment to 4144.
Laurent (Nokia) answers to Marco
Marco (Huawei) answers to Laurent
Marco (Huawei) we are OK with the CR
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Agreed
4.1 S2-2003684 LS OUT Approval [DRAFT] Reply LS on uniqueness of PEI in certain FN-RG configurations Ericsson Rel-16 Response to S2-2003521. Revised to remove 'draft' in S2-2004479.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004479 LS OUT Approval Reply LS on uniqueness of PEI in certain FN-RG configurations SA WG2 Rel-16 Revision of S2-2003684. Approved Approved
4.1 S2-2003529 LS In Action LS from CT WG4: LS on End Marker Indication CT WG4 (C4-201165) Rel-16 Revision of postponed S2-2002649 from S2-138E. Postponed Laurent (Nokia): proposes the Note the LS in as handled at last meeting by agreed S2-2002693 23.502 CR 2176
Fenqin(Huawei) Provide comment.
Stefan (Ericsson) proposes to postpone the LS
Laurent (nokia) proposes to postpone the LS
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003525 LS In Action LS from CT WG1: Reply LS on Non-UE N2 Message Services Operations CT WG1 (C1-200889) Rel-16 Revision of postponed S2-2002637 from S2-138E. Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003536 LS In Action LS from CT WG1: Reply LS on Non-UE N2 Message Services Operations CT WG1 (C1-202663) Rel-16 Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004066 CR Approval 23.502 CR2321 (Rel-16, 'F'): Missing parameters in Namf_Communication_NonUeN2MessageTransfer NTT DOCOMO, one2many Rel-16 R01 agreed. Revised to S2-2004480 Hannu (Nokia) provides r01 to clean up the cover page.
Atsushi (NTT DOCOMO) agrees with r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004480 CR Approval 23.502 CR2321R1 (Rel-16, 'F'): Missing parameters in Namf_Communication_NonUeN2MessageTransfer NTT DOCOMO, one2many Rel-16 Revision of S2-2004066_r01. This CR was agreed Agreed
4.1 S2-2003540 LS In Action LS from CT WG1: PAP/CHAP and other point-to-point protocols usage in 5GS CT WG1 (C1-202933) Rel-16 Response drafted in S2-2004196. Final response in S2-2004481
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004196 LS OUT Approval [DRAFT] Reply PAP/CHAP and other point-to-point protocols usage in 5GS Qualcomm Incorporated Rel-16 Response to S2-2003540. R06 agreed. Revised to S2-2004481 Haris (Qualcomm) comments and provides r01
Laurent (Nokia) comments and provides r02
Stefan (Ericsson) comments and provides r03
Fenqin (Huawei) comments and provide r04.
Saso (Intel) asks a clarification on L2TP.
Laurent (Nokia) answers and provides r05.
Chris (Vodafone) provides r06. This is for R15.
==== Ph1 Revisions Deadline ====
Chris (Vodafone) proposes to approve r06.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004481 LS OUT Approval Reply PAP/CHAP and other point-to-point protocols usage in 5GS SA WG2 Rel-16 Revision of S2-2004196_r06. Approved Approved
4.1 S2-2003544 LS In Action LS from CT WG3: LS on Clarification on eNA CT WG3 (C3-202507) Rel-16 Response drafted in S2-2004327. Final response in S2-2004482
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003866 LS OUT Approval [DRAFT] Reply LS on Clarification on eNA (C3-202507) Huawei, HiSilicon Rel-16 Merged into S2-2004327 Merged
4.1 S2-2003667 LS OUT Approval [DRAFT] Reply LS on Clarification on eNA Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2004327. Revised, merging S2-2003866, to S2-2003544 Revised
4.1 S2-2004327 LS OUT Approval [DRAFT] Reply LS on Clarification on eNA Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-16 Revision of S2-2003667, merging S2-2003866. Response to S2-2004327. Revised to remove 'draft' in S2-2004482. Approved, remove draft word.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004482 LS OUT Approval Reply LS on Clarification on eNA SA WG2 Rel-16 Revision of S2-2004327. Approved Approved
4.1 S2-2003867 CR Approval 23.288 CR0172R2 (Rel-16, 'F'): Corrections to Nnwdaf service operations Nokia, Nokia Shanghai Bell, Samsung, Huawei Rel-16 Revision of S2-2003339 Merged into S2-2004328. S2-2003339 from S2#138E remains agreed. Merged
4.1 S2-2003668 CR Approval 23.288 CR0176 (Rel-16, 'F'): Corrections for maximum number of objects and Maximum number of SUPIs Nokia, Nokia Shanghai Bell Rel-16 Revised, merging S2-2003867, to S2-2004328 Revised
4.1 S2-2004328 CR Approval 23.288 CR0176R1 (Rel-16, 'F'): Corrections for maximum number of objects and Maximum number of SUPIs Nokia, Nokia Shanghai Bell, Samsung, Huawei Rel-16 Revision of S2-2003668, merging S2-2003867. This CR was agreed
==== Ph1 Revisions Deadline ====
Agreed
4.1 S2-2003545 LS In Action LS from CT WG3: LS on Access Type Report for a MA PDU session CT WG3 (C3-202512) Rel-16 Response drafted in S2-2003665 and S2-2003691. Final response in S2-2004483
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2003665 LS OUT Approval [DRAFT] Reply LS on Access Type Report for a MA PDU session Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003545. Merged into S2-2004483 Jinguo(ZTE) propose to merge this LS OUT to 3691
Yannick (Nokia) agrees that S2-2003665 can be merged with S2-2003691.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
4.1 S2-2003666 CR Approval 23.503 CR0469 (Rel-16, 'F'): Correction for access type change for MA PDU session Nokia, Nokia Shanghai Bell Rel-16 Noted Jinguo(ZTE) propose note the CR
Yannick (Nokia) agrees that S2-2003666 (Nokia) can be noted.
==== Ph1 Revisions Deadline ====
Noted
4.1 S2-2003691 LS OUT Approval [DRAFT] Reply LS on Access Type Report for a MA PDU session Ericsson Rel-16 Response, merging S2-2003665, to S2-2003545. R01 agreed. Revised to S2-2004483 Yannick (Nokia) provides r01.
Belen (Ericsson) is fine with r01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004483 LS OUT Approval Reply LS on Access Type Report for a MA PDU session SA WG2 Rel-16 Revision of S2-2003691_r01, merging S2-2003665. Approved Approved
4.1 S2-2003551 LS In Action LS from SA WG3LI: LS on Location information for SMS over IMS SA WG3LI (S3i200161) Rel-16 Postponed George (Ericsson) proposes to postpone due to lack of input/contribution
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003557 LS In Action LS from RAN WG3: LS on AS rekeying handling RAN WG3 (R3-202833) Rel-15 Postponed Qian Chen (Ericsson) Propose to NOTE the LS since no paper related to the LS is submitted to this meeting
Qian Chen (Ericsson) proposes to POSTPONE the LS, and withdraws the previous NOTE proposal.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003558 LS In Information LS from SA WG5: LS to CT4 on SNSSAI support in N4 Session Establishment SA WG5 (S5-202308) Rel-16 Response drafted in S2-2003653. Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003653 LS OUT Approval [DRAFT] Reply LS on SNSSAI support in N4 Session Establishment Nokia, Nokia Shanghai Bell Rel-16 Response to S2-2003558. Noted Qianghua (Huawei) suggests to NOTE this LS.
Laurent (Nokia) answers to Qianghua we need to send the LS.
David (Samsung) agrees with Nokia on the need to send the LS.
Qianghua (Huawei) answers.
Laurent (Nokia) answers.
David (Samsung) requests clarification from Huawei.
Hyunsook (LGE) asks a question.
Qianghua (Huawei) provides responses.
Laurent (Nokia) answers to Hyunsook .
Stefan (Ericsson) comments
==== Ph1 Revisions Deadline ====
Qianghua (Huawei) objects this LS.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003559 LS In Action LS from SA WG5: LS to SA2 on QoS requirements for OAM traffic on IAB SA WG5 (S5-202458) Rel-16 Postponed Andy (Vice Chair, Samsung) suggests to postpone this.
Hong (Qualcomm Inc.) agrees that the LS should be postponed.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003560 LS In Action LS from RAN WG2: Reply LS on category M devices and NR RAN WG2 (R2-2003934) Rel-16 Noted Hans (Ericsson) propose LS in to be noted. Has already been handled in SA2.
Hannu (Nokia) supports Hans (Ericsson) to note the LS. No action SA2.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003561 LS In Action LS from RAN WG2: LS on SIB indication for UE specific DRX RAN WG2 (R2-2004057) Rel-16 Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2004210 CR Approval 23.501 CR2378 (Rel-16, 'F'): UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057 Qualcomm Incorporated Rel-16 R04 agreed. Revised to S2-2004484 Qian Chen (Ericsson) provides r01.
Miguel Griot (Qualcomm) is OK with r01 provided by Ericsson.
Hannu (Nokia) proposes r02.
Steve (Huawei) comments on whether we can make the text even simpler.
Hannu (Nokia) replies to Steve (Huawei) comment.
Steve (Huawei) provides r03 along the lines discussed.
Miguel Griot (Qualcomm) is OK with r03
Hannu (Nokia) supports Steve (Huawei) revision r03.
Qian Chen (Ericsson) provides r04 (adding Ericsson as supporting company).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004484 CR Approval 23.501 CR2378R1 (Rel-16, 'F'): UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057 Qualcomm Incorporated, Ericsson Rel-16 Revision of S2-2004210_r04. This CR was agreed Agreed
4.1 S2-2004216 CR Approval 23.401 CR3604 (Rel-16, 'F'): UE specific DRX for NB-IoT RAN support clarification Qualcomm Incorporated Rel-16 R06 agreed. Revised to S2-2004485 Qian Chen (Ericsson) provides r01.
Miguel Griot (Qualcomm) is OK with r01 provided by Ericsson.
Hannu (Nokia) proposes a further revision of the CR.
Steve (Huawei) asks whether all the detail is needed
Steve (Huawei) provides r03 along the lines discussed.
Miguel Griot (Qualcomm) is OK with r02 but not ok with r03
Hannu (Nokia) supports Miguel Griot (Qualcomm) and provides r04
Steve (Huawei) provides r05.
Hannu (Nokia) agrees r05.
Miguel Griot (Qualcomm) is OK with r05
Qian Chen (Ericsson) provides r06 (adding Ericsson as supporting company).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004485 CR Approval 23.401 CR3604R1 (Rel-16, 'F'): UE specific DRX for NB-IoT RAN support clarification Qualcomm Incorporated, Ericsson Rel-16 Revision of S2-2004216_r06. This CR was agreed Agreed
4.1 S2-2003566 LS In Action LS from RAN WG2: Response LS on the support for ECN in 5GS RAN WG2 (R2-2004284) Rel-15 Noted Haiyang (Huawei) suggests to note this LS.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003575 LS In Action LS from RAN WG2: LS on early UE capability retrieval for eMTC RAN WG2 (R2-2003935) Rel-16 Response drafted in S2-2004188. Final response in S2-2004446
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
4.1 S2-2004188 LS OUT Approval [DRAFT] Reply LS on early UE capability retrieval for eMTC Qualcomm Technologies Int Rel-16 Response to S2-2003575. R07 agreed. Revised to S2-2004446. Sebastian (Qualcomm) provides r01, which was already shared as a draft last week.
Steve (Hauwei) Comments.
Qian Chen (Ericsson) provides comments.
Hannu (Nokia) proposes that this new requirement can't be added to Rel-16.
Sebastian (Qualcomm) replies to Nokia.
Sebastian (Qualcomm) suggests to not create unnecessary dependencies between EPS and 5GS discussions and responds to Huawei's comments.
Steve (Huawei) comments.
Steve (Huawei) provides r02.
Hannu (Nokia) agrees with Steve (Huawei) and provides minor cleanup of wording in r03.
Sebastian (QC) provides r04
Hannu (Nokia) replies to Sebastian (QC).
Steve (Huawei) cannot accept r04
Sebastian (QC) provides r05
==== Ph1 Revisions Deadline ====
Steve (Huawei) objects to all revisions except r03
Sebastian (Qualcomm) objects to r03 since statements like 'concerns about introducing to EPS capabilities that are not supported by 5GS, or no clear path exists for its addition to 5GS.' are not acceptable and proposes this LS to be discussed during the Friday conference call.
Hannu (Nokia) comments on the LS.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004446 LS OUT Approval Reply LS on early UE capability retrieval for eMTC SA WG2 Rel-16 Revision of S2-2004188_R07. Approved Approved
4.1 S2-2004189 CR Approval 23.501 CR2377 (Rel-16, 'B'): Truncated 5G S-TMSI for early UE capability retrieval Qualcomm Incorporated Rel-16 Noted Sebastian (Qualcomm) provides r01.
Steve (Huawei) proposes to NOTE the CR
==== Ph1 Revisions Deadline ====
Steve (Huawei) objects to all versions.
Hannu (Nokia) objects to this CR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2004193 CR Approval 23.401 CR3603 (Rel-16, 'B'): Early UE capability retrieval support Qualcomm Incorporated Rel-16 Confirm Spec version used - CR states 16.4.0!. Noted Sebastian (Qualcomm) provides r01 to fix the spec version on the cover page.
Steve (Huawei) suggests to NOTE the CR.
Sebastian (QC) disagrees with Steve.
==== Ph1 Revisions Deadline ====
Steve (Huawei) objects to all versions.
Sebastian (QC) disagrees with noting the CR as no technical issue has been pointed out. We would like to propose to handle the CR in the Friday call.
Hannu (Nokia) supports Huawei proposal to note the document.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003627 LS In Action LS from BBF: Issue with FN-RG IPv6 support BBF (LIAISE-394) (LIAISE-394) Response drafted in S2-2003686. Postponed Marco (Huawei) comments to BBF Q3 DHCP support in SMF
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003686 LS OUT Approval [DRAFT] Reply LS on Issue with FN-RG IPv6 support Ericsson Rel-16 Response to S2-2003627. Postponed Marco (Huawei) propose R01 revision answer for DHCP relay option
Marco (Huawei) propose revision R02 on top of R01 removing IPv6 part (assuming CR not approved)
Stefan (Ericsson) provides r03 based on the compromise CR
==== Ph1 Revisions Deadline ====
Marco (Huawei) considering objection to 3685 support r02
Stefan (Ericsson) comments
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003685 CR Approval 23.316 CR2046 (Rel-16, 'F'): Handling of IPv6 addresses for FN-RG Ericsson Rel-16 Postponed Marco (Huawei) ask for clarification and comment.
Laurent (Nokia) provide comment.
Marco (Huawei) reply to Nokia.
Stefan (Ericsson) replies to Marco
Marco (Huawei) concern on CR proposal due to impact on SMF
Marco (Huawei) confirm concern due to impact to SMF
Marco (Huawei) still have concern and prefer to note the CR
Stefan (Ericsson) provides r01
==== Ph1 Revisions Deadline ====
Marco (Huawei) object any version
Curt (Charter) supports Ericsson and sees that r01 is a good way forward.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2003654 CR Approval 23.501 CR2368 (Rel-16, 'F'): PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic) Nokia, Nokia Shanghai Bell, Qualcomm Incorporated Rel-16 R03 agreed. Revised to S2-2004486 Tom (Spreadtrum) provides r01.
Haris (Qualcomm) comments on r01
Tom/Chunhui(Spreadtrum) replies Haris (Qualcomm)'s comments on r01. Spreadtrum would suggest S2-2003654 to be NOTED.
Laurent (Nokia) replies to Tom and provides r02
Lalith (Samsung) supports Laurent (Nokia) to agree this CR and not remain dependent on CT1 progress.
Stefan (Ericsson) comments and provides r03
Tom/Chunhui (Spreadtrum) can accept r03.
==== Ph1 Revisions Deadline ====
Laurent (Nokia) supports r00, r02 and r03. Objects to r01 that (not intentionaly I guess) removes whole clause 2
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004486 CR Approval 23.501 CR2368R1 (Rel-16, 'F'): PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic) Nokia, Nokia Shanghai Bell, Qualcomm Incorporated Rel-16 Revision of S2-2003654_r03. This CR was agreed Agreed
4.1 S2-2004308 LS In Action LS from SA WG3: LS on Updated User Plane Integrity Protection advice SA WG3 (S3-201487) Rel-16 Response drafted in S2-2004262.Postponed
==== Ph1 Revisions Deadline ====
Lalith (Samsung) proposes to postpone this LS to next meeting.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
4.1 S2-2004262 LS OUT Approval [DRAFT] Reply LS on Updated User Plane Integrity Protection advice Samsung R&D Institute India Rel-16 Response to S2-2004308. Noted Tom (Spreadtrum) provides r01.
Lalith (Samsung) comments on r01.
Hui Ni (Huawei) provide r02.
Tom(Spreadtrum) replies Lalith (Samsung)'s comments on r01.
Haris (Qualcomm) agrees with Spreadtrum
Laurent (Nokia) supports Hui's comment (r02).
Chris (Vodafone) provides r01 to address Ericsson and Nokia comments made in CC#1 folder
Stefan (Ericsson) support previous comments
Lalith (Samsung) replies to all previous comments.
Laurent (Nokia) comments: please clarify your proposal
Lalith (Samsung) clarifies the proposal
Hui Ni (Huawei) provides comments
Lalith(Samsung) responds Hui Ni comments
Stefan (Ericsson) comments
Lalith (Samsung) responds to comments
Hui NI (Huawei) provide comments and insist on r02.
Stefan (Ericsson) provides r04
Hui Ni (Huawei) fine with r04
Florin (Broadcom) supports Stefan's (Ericsson) comments and the text in r04. Cannot agree on r03.
==== Ph1 Revisions Deadline ====
Lalith (Samsung) objects r01, ro2, r04. ro1 - because it does not document what are the SA2 specification impact, r02,r04-because these are based on wrong understanding of the solution.
Florin (Broadcom) answers Lalith (Samsung) comments and continues to support r04 and r02 and objects to r03.
Tom/Chunhui(Spreadtrum) suggests to postpone this Relpy LS to next meeting.
Lalith (Samsung) responds to Florin (Broadcom).
Laurent (Nokia) objects to r00 and r03 (SA2 cannot endorse a solution with VERY different understanding of the solution). The best you can get Lalith is r04
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003763 CR Approval 23.502 CR2057R1 (Rel-16, 'F'): Correction of the Registration with AMF re-allocation procedure Nokia, Nokia Shanghai Bell, Telecom Italia Rel-16 Revision of S2-2000819. Noted Fenqin (Huawei) propose to Note this paper.
Qian Chen (Ericsson) proposes also to NOTE this paper.
Changhong (Intel) proposes also to NOTE this paper.
==== Ph1 Revisions Deadline ====
Changhong (Intel) proposes to postpone or note the CR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003814 CR Approval 23.502 CR2317 (Rel-16, 'F'): Clarification on Registration with AMF re-allocation ZTE Rel-16 Noted Changhong (Intel) provides comments.
Fenqin (Huawei) provides comments.
Jinguo(ZTE) provides r01.
==== Ph1 Revisions Deadline ====
Changhong (Intel) proposes to postpone or note the CR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
4.1 S2-2003864 CR Approval 23.501 CR2237R1 (Rel-15, 'F'): Reflective QoS Huawei, HiSilicon, Ericsson Rel-15 Revision of S2-2002750. R05 agreed. Revised to S2-2004447. Chunshan Xiong (Tencent) provides r01
Mirko (Huawei) provides r02
Judy (Ericsson) provides comment.
Chunshan Xiong (Tencent) provides r03.
Judy (Ericsson) provides r04 (based on r02).
Devaki (Nokia) provides comments and requests authors to create a revision.
Judy (Ericsson) replies to Nokia.
Mirko (Huawei) replies and objects to r03 and r04.
==== Ph1 Revisions Deadline ====
Devaki (Nokia) comments.
Chunshan Xiong (Tencent) comments.
Mirko (Huawei) responds to comments from Nokia and Tencent.
Judy (Ericsson) proposes to go for r02.
Devaki (Nokia) asks question for clarification, still has major concerns to specify UPF behaviour as part of SMF, especially considering Rel-15/Rel-16 are deeply frozen.
Mirko (Huawei) responds to Nokia's comment.
Devaki (Nokia) requests for a revision in order to accept the CR. At the moment, has objections to the wording in r02.
Judy (Ericsson) responded to Devaki.
==== Ph1 Final Deadline ====
Devaki (Nokia) responds to Ericsson.
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004447 CR Approval 23.501 CR2237R2 (Rel-15, 'F'): Reflective QoS Huawei, HiSilicon, Ericsson, Tencent Rel-15 Revision of S2-2003864_R05. This CR was agreed Agreed
4.1 S2-2003865 CR Approval 23.501 CR1732R4 (Rel-16, 'A'): Reflective QoS Huawei, HiSilicon, Ericsson Rel-16 Revision of S2-2002751. Revised to S2-2004448. Chunshan Xiong (Tencent) provides r01
Devaki (Nokia) provides r02.
Devaki (Nokia) requests authors to apply the changes proposed in r02 of this CR also to revision of S2-2003864.
==== Ph1 Revisions Deadline ====
Mirko (Huawei) responds and clarifies that this is a mirror CR and should therefore not be revised/agreed independently.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
4.1 S2-2004448 CR Approval 23.501 CR1732R5 (Rel-16, 'A'): Reflective QoS Huawei, HiSilicon, Ericsson, Tencent Rel-16 Revision of S2-2003865. This CR was agreed Agreed
8 - - - Rel-17 SIDs - - Docs:=0 -
8.1 - - - Study on Enablers for Network Automation for 5G - phase 2 (FS_eNA_Ph2) - - Docs:=129 -
8.1 - - - General - - Docs:=1 -
8.1 S2-2003871 P-CR Approval 23.700-91: Miscellaneous corrections for TR 23.700-91. Huawei, HiSilicon Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.1 - - - UC 5: NWDAF supporting the detection of cyber-attacks - - Docs:=1 -
8.1 S2-2004283 LS OUT Approval [DRAFT] LS on NWDAF supporting the detection of cyber-attacks Orange, KPN Rel-17 Noted Yannick (Nokia) provides comment.
Belen (Ericsson) objects to sending this LS to SA3.
Juan (Qualcomm) objects to sending this LS to SA3.
Antoine (Orange) responds to Ericsson and Qualcomm.
Toni (KPN) supports sending this LS to SA3.
Ericsson replies to Orange proposal that this is part of KI#8. This is incorrect, it is related to a use case that has no key issue associated.
Antoine (Orange) asks Belen what she means by 'associated'.
Belen (Ericsson) clarifies to Antoine.
==== Ph1 Revisions Deadline ====
Antoine (Orange) asks the group for opinion on the way forward.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 - - - KI X: Energy Saving - - Docs:=4 -
8.1 S2-2003532 LS In Information LS from 3GPP Rel16: Reply LS on analytics support for energy saving SA WG5 (S5-201472) Rel-17 Revision of postponed S2-2002664 from S2-138E. Response drafted in S2-2004284. Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.1 S2-2004284 LS OUT Approval [DRAFT] Reply LS on analytics support for energy saving Orange Rel-17 Response to S2-2003532. Noted Yannick (Nokia) : this draft reply LS is related to proposals in S2-2003922 and S2-2004226. We do not think SA5 provided SA2 specific requirements that would allow SA2 to start working on energy saving use cases, key issues nor solutions. Nokia suggest to NOTE this document.
Juan (Qualcomm) : we do not think SA2 encourage SA2 to further discuss the solution and key issue. As the guidance from SA in SP-191378, it is SA plenary to make the decision about the following process about this topic. Qualcomm proposed to note this reply LS.
David (Samsung) agrees with Nokia, Qualcomm to note this reply LS.
Song(China Telecom): reply Juan's comments on the discussion in SA2: The SA2's discussion in this area is the continued discussion started in SA5 and this LS proposal does not challenge the SA's guidance.
Antoine (Orange): Explains the intention of the LS and suggests to keep it open.
==== Ph1 Revisions Deadline ====
Yannick (Nokia) : based on the discussion on the related pCRs in S2-2003922 and S2-2004226 we believe there is no need to reply to SA5 and we should note this proposal.
Juan Zhang (Qualcomm) proposes to note the reply LS.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003922 P-CR Approval 23.700-91: New KI on NWDAF assisted energy saving in FS_eNA_Ph2. China Telecom, Orange Rel-17 Noted Yannick (Nokia) suggests to NOTE this document. Energy saving has been down-scoped from eNA_Ph2 study, and we have not receive specific requirements from SA5 other than encouragements to work in this area.
Song replies Yannick's comments and further clarification the proposal on keeping this KI
David (Samsung) provides comments to Song (China Telecom)
Song (China Telecom) provides reply to David(Samsung)'s comments.
Yannick (Nokia) : Nokia objects to this key issue.
Susana (Vodafone) proposes to NOTE this document.
Ericsson proposes to NOTE the document.
Song (China Teleocm) : provide further clarification. Provide r01. However, the r01 file is corrupted during the FTP uploading.Therefore, the r01 may be abandoned and the r02 is provided.
Juan Zhang (Qualcomm) proposed to note the paper.
==== Ph1 Revisions Deadline ====
Susana (Vodafone) objects to all versions of this document. This is out of the scope of this study.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2004226 P-CR Approval 23.700-91: Solution for NWDAF assisted energy saving in FS_eNA_Ph2. China Telecom, Orange Rel-17 Noted Yannick (Nokia) suggests to NOTE this document. Energy saving has been down-scoped from eNA_Ph2 study, and we have not receive specific requirements from SA5 other than encouragements to work in this area.
Susana (Vodafone) proposes to NOTE this document
Belen (Ericsson)) proposes to NOTE this document
Juan Zhang (Qualcomm) proposes to NOTE this document
Song (China Telecom) provides r01
Song (China Telecom) provides further clarification on r01
==== Ph1 Revisions Deadline ====
Susana (Vodafone) objects to all versions of this document. This is out of the scope of this study.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 - - - KI 1: Logical decomposition of NWDAF and possible interactions between logical functions - - Docs:=10 -
8.1 S2-2003632 P-CR Approval 23.700-91: Solution to AI Model sharing architecture. ZTE Rel-17 R03 agreed. Revised to S2-2004450. David (Samsung) provides comments, proposes to note this pCR.
Yingjie(ZTE) replys to David(Samsung).
Malla (NTT DOCOMO) provides comments.
Yingjie(ZTE) replys to Malla(NTT DOCOMO) and provides r02.
David (Samsung) shares concerns with r01, r02.
Yingjie(ZTE) replys to David and provided r03.
==== Ph1 Revisions Deadline ====
Belen (Ericsson) proposes to NOTE this contribution
Yingjie(ZTE) replys to Belen.
==== Ph1 Final Deadline ====
Yingjie(ZTE) ask for clarify from Belen and would provide r04 including a NOTE ('NOTE: The AIF could be collocated with decomposed NWDAF which is discussing in KI#1.')
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004450 P-CR Approval 23.700-91: Solution to AI Model sharing architecture. ZTE Rel-17 Revision of S2-2003632_R03. Approved Approved
8.1 S2-2003862 P-CR Approval 23.700-91: NWDAF Decompose Architecture . Qualcomm Incorporated Rel-17 Revised to S2-2004523. Yang Xu (OPPO) provides comments
Juan Zhang (Qualcomm) reply OPPO's comments.
David (Samsung) provides comments, requests clarifications
Yang Xu (OPPO) provides more questions
Xiaobo(Huawei) provide r01 and mainly clarify which part is out of 3GPP scope and the relationship with other KIs.
Juan Zhang (Qualcomm) agree with r01 and reply comments.
Yannick (Nokia) provides a general comment.
Yingjie (ZTE) provides r02.
Juan Zhang (Qualcomm) provides r03 and reply comments.
David (Samsung) provides further comments on Option 1.
Juan Zhang (Qualcomm) reply comments to Samsung.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004523 P-CR Approval 23.700-91: NWDAF Decompose Architecture . Qualcomm Incorporated Rel-17 Revision of S2-2003862. Approved Approved
8.1 S2-2004058 P-CR Approval 23.700-91: KI #1, New Sol: NWDAF functionality Split. China Mobile Rel-17 Revised to S2-2004524. Yannick (Nokia) : Nokia objects to this version.
Aihua (China Mobile) replies and provides r01.
Yannick (Nokia) : Nokia objects to r01.
Aihua (China Mobile) replies and provides r02.
David (Samsung) shares concerns, provides comments to r02.
Yannick (Nokia) : Nokia shares some concerns from Samsung. r02 is still not acceptable.
Aihua (China Mobile) replies and provides r03.
David (Samsung) requests further clarification.
==== Ph1 Revisions Deadline ====
Aihua (China Mobile) provides clarification to David (Samsung).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004524 P-CR Approval 23.700-91: KI #1, New Sol: NWDAF functionality Split. China Mobile Rel-17 Revision of S2-2004058. Approved Approved
8.1 S2-2004181 P-CR Approval 23.700-91: KI #1, New Sol: NWDAF decomposition. CATT Rel-17 Revised to S2-2004525. David (Samsung) requests clarification.
Xiaoyan (CATT) clarifies and provides r01.
Yannick (Nokia) provides comments.
Xiaoyan (CATT) replies and provides r02.
David (Samsung) provides further comments.
Susana (Vodafone) request clarification and provides comments.
Xiaoyan (CATT) replies and provides r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004525 P-CR Approval 23.700-91: KI #1, New Sol: NWDAF decomposition. CATT Rel-17 Revision of S2-2004181. Approved Approved
8.1 S2-2003669 P-CR Approval 23.700-91: KI #1 #2 #11, New Solution: Data Collection and Sharing Architecture. Nokia, Nokia Shanghai Bell, AT&T Rel-17 Revised to S2-2004526. Mehrdad (Samsung) comments on this contribution.
Dimitris (Lenovo) request for clarification
Yannick (Nokia) answers to Dimitris' request.
Ericsson (Belen) provides r01 and comment.
Dimitris (Lenovo) has an additional question.
Yannick (Nokia) answers to Mehrdad questions.
Yannick (Nokia) provides r02.
Gerald (Matrixx) provided comments.
Aihua (China Mobile) requests for clarification.
Mehrdad (Samsung) provides r03.
Dimitris (Lenovo) provides r04
Yannick (Nokia) replies to Dimitris (Lenovo).
Yannick (Nokia) provides r05.
Xiaoyan (CATT) asks for clarification.
Yannick (Nokia) replies to Xiaoyan (CATT).
Yannick (Nokia) answers to Gerald's comments.
Xiaoyan (CATT) provides further comments.
Yannick (Nokia) replies to Xiaoyan (CATT) and provides r06.
==== Ph1 Revisions Deadline ====
Manuel (Sandvine) express concerns about this proposal. Sandvine suggests to NOTE this document; this proposal does not address real-time use cases neither data collection corresponds to a massive amount of data.
Farooq (AT&T) responds to Manuel comments. The comments/concerns from Manuel are of solution evaluation nature and should not be a reason for not including the proposal in the TR.
Sudhakar (Verizon) responds to Manuel's comments. Agree with AT&T's observation.
Manuel (Sandvine) responds to Farooq and Sudhakar. Ok, please disregard my previous email where I suggest to NOTE this document.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004526 P-CR Approval 23.700-91: KI #1 #2 #11, New Solution: Data Collection and Sharing Architecture. Nokia, Nokia Shanghai Bell, AT&T Rel-17 Revision of S2-2003669. Approved Approved
8.1 - - - KI 2: Multiple NWDAF instances - - Docs:=34 -
8.1 S2-2003692 P-CR Approval 23.700-91: KI #2,11; New Sol: Solution on handling of distributed and mixed NWDAF deployments. Ericsson, AT&T Rel-17 Revised to S2-2004527. Yingjie(ZTE) ask for clarification.
Hucheng(CATT) has questions for clarification.
Dimitris (Lenovo) has a question for clarification
Yannick (Nokia) requests for clarification.
Belen (Ericsson) answers questions and provide r01 that aims to include comments-
Hucheng(CATT) comments that r01 doesn't address concerns from CATT
Yannick (Nokia) comments on r01.
Belen (Ericsson) provide r02 that aims to include comments.
Belen (Ericsson) provide r03 that aims to include CATT comments too.
==== Ph1 Revisions Deadline ====
Hucheng(CATT) can live with r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004527 P-CR Approval 23.700-91: KI #2,11; New Sol: Solution on handling of distributed and mixed NWDAF deployments. Ericsson, AT&T Rel-17 Revision of S2-2003692. Approved Approved
8.1 S2-2003758 P-CR Approval 23.700-91: Two-level hierarchical NWDAF Architecture. OPPO Rel-17 Revised to S2-2004528. Yingjie(ZTE) ask for clarification.
Yang Xu (OPPO) replies
Dimitris (Lenovo) ask for clarification.
Mehrdad (Samsung) provides comments.
Yang Xu (OPPO) replies to lenovo.
Yannick (Nokia) requests for clarifications.
Hucheng(CATT) asks for clarifications.
Yang Xu (OPPO) provides answer to Nokia
Seungik (ETRI) provides comments.
Yang Xu (OPPO) replies to CATT
Yang Xu (OPPO) replies to ETRI
Yang Xu (OPPO) propose to consider the merging in future meeting
Hucheng(CATT) provides a comment.
Yang Xu(OPPO) provides rev01.
Yannick (Nokia) provides r02.
Yang Xu (OPPO) replies.
Yannick (Nokia) answers to Yang Xu (OPPO).
Yang Xu (OPPO) replies to Nokia
Yang Xu (OPPO) resubmits the revision
Yannick (Nokia) provides r04.
Yang Xu (OPPO) provides r05.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004528 P-CR Approval 23.700-91: Two-level hierarchical NWDAF Architecture. OPPO Rel-17 Revision of S2-2003758. Approved Approved
8.1 S2-2003779 P-CR Approval 23.700-91: KI #2,11, New Sol: Support for NWDAF interactions within SBA framework. ETRI, UANGEL Rel-17 Revised to S2-2004529. Mehrdad (Samsung) provides comment and suggests a possible merger between similar proposals.
Yannick (Nokia) : Nokia express concerns on this proposal.
Yannick (Nokia) replies to Mehrdad (Samsung).
Seungik (ETRI) replies to Yannick (Nokia) and provides r01.
Seungik (ETRI) replies to Mehrdad (Samsung) and Yannick (Nokia).
Yannick (Nokia) provides comment on r01.
Seungik (ETRI) replies to Yannick (Nokia) and provides r02.
Yannick (Nokia) is fine with r02 contents.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004529 P-CR Approval 23.700-91: KI #2,11, New Sol: Support for NWDAF interactions within SBA framework. ETRI, UANGEL Rel-17 Revision of S2-2003779. Approved Approved
8.1 S2-2003781 P-CR Approval 23.700-91: KI#2, New Sol: Time coordination for Multiple NWDAFs. Samsung, AT&T Rel-17 Revision of S2-2000872. Revised to S2-2004530. Yannick (Nokia) requests for clarification.
Hucheng (CATT) comments.
Mehrdad (Samsung) answers NOK request.
Mehrdad (Samsung) answers CATT comments.
Dimitris (Lenovo) comments.
Mehrdad (Samsung) answers Lenovo comments.
Yannick (Nokia) requests for further clarifications.
Mehrdad (Samsung) provides revision r01.
Yannick (Nokia) comments on r01.
Mehrdad (Samsung) replies to Nokia.
Mehrdad (Samsung) provides revision r02.
Farooq (ATT) OK with rev02 and responds to Yannick
Belen (Ericsson) provides comments, and request to further update this contribution
Mehrdad (Samsung) replies to Ericsson and provides revision r03.
Yannick (Nokia) is fine with r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004530 P-CR Approval 23.700-91: KI#2, New Sol: Time coordination for Multiple NWDAFs. Samsung, AT&T Rel-17 Revision of S2-2003781. Approved Approved
8.1 S2-2003782 P-CR Approval 23.700-91: KI #2, New Sol: support flexible data collection model for multiple NWDAFs. Samsung Rel-17 Revised to S2-2004531. Yingjie(ZTE) ask for clarification.
Belen (Ericsson) asks for clarifications
Mehrdad (Samsung) answers ZTE and Ericsson.
Mehrdad (Samsung) replies Ericsson
Belen (Ericsson) replies and asks for clarifications
Yang Xu (OPPO) asks questions
Yannick (Nokia) provides comments.
Mehrdad (Samsung) replies to Nokia.
Mehrdad (Samsung) provides revision r01.
Yang Xu (OPPO) comments
Yannick (Nokia) : r01 is fine for Nokia.
Mehrdad (Samsung) replies to Yang Xu (OPPO).
==== Ph1 Revisions Deadline ====
Belen (Ericsson) comments to Samsung updates, r01 is okay.
Mehrdad (Samsung) answers Ericsson.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004531 P-CR Approval 23.700-91: KI #2, New Sol: support flexible data collection model for multiple NWDAFs. Samsung Rel-17 Revision of S2-2003782. Approved Approved
8.1 S2-2003875 P-CR Approval 23.700-91: KI #2, KI #11, New Sol: Data Collection Coordination for Multiple NWDAF Instances. Huawei, HiSilicon Rel-17 Revised to S2-2004532. Yannick (Nokia) provides comments.
Mehrdad (Samsung) provides comment and suggests a possible merger between similar proposals.
Antoine (Orange) requests to fix the title of 6.X.2.
Xiaobo (Huawei) provide r01 to answer Nokia and Orange's concerns and also provide clarification to Samsung.
Yannick (Nokia) provides r02.
Xiaobo (Huawei) is ok with r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004532 P-CR Approval 23.700-91: KI #2, KI #11, New Sol: Data Collection Coordination for Multiple NWDAF Instances. Huawei, HiSilicon Rel-17 Revision of S2-2003875. Approved Approved
8.1 S2-2003876 P-CR Approval 23.700-91: KI #2, KI #11, New Sol: Data collection reduction in hierarchical Lower-to-Upper Level NWDAFs Interactions. Huawei, HiSilicon Rel-17 Revised to S2-2004533. Yannick (Nokia) provides comments.
Mehrdad (Samsung) provides comments.
Xiaobo (Huawei) respond to Nokia and Samsung's comments.
Yannick (Nokia) provides r01.
Xiaobo (Huawei) is fine with r01 provided by Yannick(Nokia).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004533 P-CR Approval 23.700-91: KI #2, KI #11, New Sol: Data collection reduction in hierarchical Lower-to-Upper Level NWDAFs Interactions. Huawei, HiSilicon Rel-17 Revision of S2-2003876. Approved Approved
8.1 S2-2003877 P-CR Approval 23.700-91: KI #2, New Sol: Interactions of Hierarchical NWDAFs for Analytics Generation related to Large Areas . Huawei, HiSilicon Rel-17 Revised to S2-2004534. Yingjie(ZTE) ask for clarification.
Mehrdad (Samsung) provides comment and suggests merging.
Yannick (Nokia) provides comments.
Yang Xu (OPPO) asks a question for clarification
Xiaobo (Huawei) provides clarifications as well as revision r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004534 P-CR Approval 23.700-91: KI #2, New Sol: Interactions of Hierarchical NWDAFs for Analytics Generation related to Large Areas . Huawei, HiSilicon Rel-17 Revision of S2-2003877. Approved Approved
8.1 S2-2003879 P-CR Approval 23.700-91: KI #2, New Sol: Data collection in hierarchical Upper-to-Lower Levels NWDAF interactions. Huawei, HiSilicon Rel-17 Revised to S2-2004535. Mehrdad (Samsung) provides comment and suggests merging.
Yannick (Nokia) provides comments.
Mehrdad (Samsung) provides comment.
Xiaobo (Huawei) provides clarifications as well as r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004535 P-CR Approval 23.700-91: KI #2, New Sol: Data collection in hierarchical Upper-to-Lower Levels NWDAF interactions. Huawei, HiSilicon Rel-17 Revision of S2-2003879. Approved Approved
8.1 S2-2003880 P-CR Approval 23.700-91: KI #2, New Sol: Enhancements of NWDAF services to support consistency in NWDAFs consuming analytics IDs. Huawei, HiSilicon Rel-17 Revised to S2-2004536. Yannick (Nokia) provides comments.
Antoine (Orange) requests clarification.
Xiaobo (Huawei) provides clarification to Yannick(Nokia).
Xiaobo (Huawei) provides further clarifications as well as revision r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004536 P-CR Approval 23.700-91: KI #2, New Sol: Enhancements of NWDAF services to support consistency in NWDAFs consuming analytics IDs. Huawei, HiSilicon Rel-17 Revision of S2-2003880. Approved Approved
8.1 S2-2003881 P-CR Approval 23.700-91: KI#2,New Sol: UE abnormal behavior analytics interaction between multiple NWDAFs. Huawei, HiSilicon Rel-17 Revised to S2-2004537. Yannick (Nokia) requests for clarification on the proposal.
Xiaobo (Huawei) provides the clarification to Yannick(Nokia ).
Yannick (Nokia) requests for further clarification.
Xiaobo (Huawei) provides further clarification to Yannick(Nokia). Also r01 is provided.
Yannick (Nokia) requests additional clarifications.
Yannick (Nokia) still does not understand the intention with the proposal.
Juan Zhang (Qualcomm) provides comments
Xiaobo (Huawei) provides clarification to Juan(QC).
Xiaobo (Huawei) provides r02 based on Yannick(Nokia) comments.
Yannick (Nokia) provides r03, which removed NWDAF implementation details.
Xiaobo (Huawei) provides r04.
Yannick (Nokia) cannot accept r04.
Xiaobo (Huawei) provides r05.
Xiaobo (Huawei) cannot accept r05, provides r06.
==== Ph1 Revisions Deadline ====
Xiaobo (Huawei) is ok with r06.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004537 P-CR Approval 23.700-91: KI#2,New Sol: UE abnormal behavior analytics interaction between multiple NWDAFs. Huawei, HiSilicon Rel-17 Revision of S2-2003881. Approved Approved
8.1 S2-2003883 P-CR Approval 23.700-91: KI#2, New Sol: Solution to multiple NWDAF instances. Huawei, HiSilicon Rel-17 Revised to S2-2004538. Yannick (Nokia) provides comments.
Xiaobo(Huawei) provides clarification as well as r01 clarifying the meaning of processed data.
Yannick (Nokia) provides comments on r01.
Sudhakar (Verizon) provides comments.
Yannick (Nokia) provides r02.
Xiaobo(Huawei) is fine with the r02 provided by Yannick(Nokia).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004538 P-CR Approval 23.700-91: KI#2, New Sol: Solution to multiple NWDAF instances. Huawei, HiSilicon Rel-17 Revision of S2-2003883. Approved Approved
8.1 S2-2003898 P-CR Approval 23.700-91: KI#2, New solution for KI#2: Mitigating the load for Data Collection . CATT Rel-17 Revised to S2-2004539. Mehrdad (Samsung) provides comment and suggests a possible merger between similar proposals.
Yannick (Nokia) provides comments and asks for clarification.
Hucheng(CATT) replies to Nokia and ask for a clarification.
Hucheng(CATT) provides r01 and replies comments.
Yannick (Nokia) replies to Hucheng (CATT).
Yannick (Nokia) is fine with r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004539 P-CR Approval 23.700-91: KI#2, New solution for KI#2: Mitigating the load for Data Collection . CATT Rel-17 Revision of S2-2003898. Approved Approved
8.1 S2-2003927 P-CR Approval 23.700-91: Solution to flexible data collection and data analysis for hierarchical NWDAF architecture. ZTE Rel-17 Revised to S2-2004540. Yannick (Nokia) requests for clarification.
Yingjie(ZTE) reply to Yannick(Nokia).
Antoine (Orange) finds that Yannick's comments apply to the KI, not to the solution.
Yannick (Nokia) clarifies his comment applies to the solution proposal, not the key issue.
Yingjie(ZTE) replys to Yannick
==== Ph1 Revisions Deadline ====
Yannick (Nokia) : r01 was provided by Yingjie yesterday but this was not indicated in the comments tags part, so Chairman's notes propose to go with r00. I suggest that Chairman's notes are updated to capture this r01 version and that we go for r01 for this contribution.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004540 P-CR Approval 23.700-91: Solution to flexible data collection and data analysis for hierarchical NWDAF architecture. ZTE Rel-17 Revision of S2-2003927. Approved Approved
8.1 S2-2004029 P-CR Approval 23.700-91: KI #2, New Sol, Federated Learning among Multiple NWDAF Instances. China Mobile, AsiaInfo Rel-17 Revised to S2-2004541. Jungshin (Samsung) request clarification
Aihua (China Mobile) replies.
Yang Xu (OPPO) coments.
Aihua (China Mobile) replies and provides r01.
Belen (Ericsson) provides r02.
Soohwan (ETRI) requests clarification.
Soohwan (ETRI) provides r03.
Jungshin (Samsung) provides r04.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004541 P-CR Approval 23.700-91: KI #2, New Sol, Federated Learning among Multiple NWDAF Instances. China Mobile, AsiaInfo, CATT Rel-17 Revision of S2-2004029. Approved Approved
8.1 S2-2004041 P-CR Approval 23.700-91: KI #2, New Sol, exposing UE mobility analytics for multiple NWDAFs case. China Mobile, AsiaInfo Rel-17 Revised to S2-2004542. Yannick (Nokia) requests for clarification. It is unclear why we need a new solution for the use case.
Aihua (China Mobile) replies.
Jungshin (Samsung) request clarification
Jungshin (Samsung) provides comments
Aihua (China Mobile) replies and provides r01.
Yannick (Nokia) comments and provides r02.
==== Ph1 Revisions Deadline ====
Jungshin (Samsung) can accept r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004542 P-CR Approval 23.700-91: KI #2, New Sol, exposing UE mobility analytics for multiple NWDAFs case. China Mobile, AsiaInfo Rel-17 Revision of S2-2004041. Approved Approved
8.1 S2-2004148 P-CR Approval 23.700-91: KI #2, New Sol: Supporting reselection of serving NWDAF. Samsung Rel-17 Revised to S2-2004543. Yannick (Nokia) provides comments.
Jungshin (Samsung) answers to questions from Nokia and provides r01.
Yannick (Nokia) is fine with r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004543 P-CR Approval 23.700-91: KI #2, New Sol: Supporting reselection of serving NWDAF. Samsung Rel-17 Revision of S2-2004148. Approved Approved
8.1 - - - KI 4: Remaining aspects on how to ensure that slice SLA is guaranteed - - Docs:=2 -
8.1 S2-2003792 P-CR Approval 23.700-91: Updates to Sol#2 on support for slice SLA guarantee. Samsung Rel-17 Revised to S2-2004544. David (Samsung) provides r01.
LaeYoung (LGE) comments.
Gerald (Matrixx) provided comments.
David (Samsung) provides r02, answers comments from Matrixx.
Peretz (Spirent) provided r03 with added notes.
David (Samsung) objects to r03.
Aihua(China Mobile) comments to the adoption of QM NF in paralleled SID.
Belen (Ericsson) shares China Mobile comments to the adoption of QM NF in paralleled SID.
David (Samsung) replies to Aihua and Belen.
Belen (Ericsson) objects to this contribution
David (Samsung) replies to Belen, offers way forward revision alternatives to the late objection
Belen (Ericsson) proposes a new way forward for a revision for this contribution
David (Samsung) agrees with Ericsson's proposal for way forward, provides new revisions (r04, r05)
Xiaoyan (CATT) asks for clarification.
David (Samsung) replies to CATT.
Xiaoyan (CATT) provides further comments.
David (Samsung) replies to Xiaoyan.
==== Ph1 Revisions Deadline ====
Belen (Ericsson) is okay with r04 and objects to any other revision.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004544 P-CR Approval 23.700-91: Updates to Sol#2 on support for slice SLA guarantee. Samsung Rel-17 Revision of S2-2003792. Approved Approved
8.1 - - - KI 7: Adding Application attributes and KPIs as the Input data in some services described in TS 23.288 [5] - - Docs:=0 -
8.1 - - - KI 8: UE data as an input for analytics generation - - Docs:=12 -
8.1 S2-2003695 P-CR Approval 23.700-91: KI #8, New Sol: Providing UE Analytics to the NWDAF via the User Plane. Ericsson Rel-17 Approved Mehrdad (Samsung) comments on this solution.
Belen (Ericsson) answers Samsung questions and provides clarifications
Antoine (Orange) asks if this is in our scope.
Mehrdad (Samsung) feedbacks to Orange.
Belen (Ericsson) replies to Orange.
Juan Zhang (Qualcomm) provides r01.
==== Ph1 Revisions Deadline ====
Yang Xu (oppo) can only live with orginal version.
Belen (Ericsson) is okay with both r01 and original version. Replies to OPPO too.
Mehrdad (Samsung) prefers r01 but also okay with original version.
Juan Zhang (Qualcomm) prefers r01 and reply OPPO's comment.
Yang Xu (OPPO) replies.
Juan Zhang (Qualcomm) replies OPPO's comment.
Yang Xu (OPPO) replies to juan.
Juan Zhang (Qualcomm) can agree with both r01 and original version and reply comments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.1 S2-2003759 P-CR Approval 23.700-91: Solution for KI#8 UE assisted analysis for usage of network slice . OPPO Rel-17 Revised to S2-2004545. Juan Zhang (Qualcomm) provides comments.
Dimitris (Lenovo) provides comments
Mehrdad (Samsung) provides comments.
Yang Xu (OPPO) provides answer.
Yang Xu (OPPO) provides answers.
Mehrdad (Samsung) requests more clarification.
Yang Xu (OPPO) replies to Lenovo
Yang Xu (OPPO) replies to samsung.
Yannick (Nokia) requests for clarification.
Yang Xu (OPPO) repliesto Nokia.
Yannick (Nokia) asks again the same question for clarification.
Yang Xu(OPPO) replies to Nokia again
Mike (Convida Wireless) comments
Yang Xu (OPPO) replies to Convida.
Juan Zhang (Qualcomm) support Nokia's comments and requests for clarification.
Yang Xu (OPPO) provides r01.
Juan Zhang (Qualcomm) provides further comments
Yang Xu (OPPO) provides further reply
Aihua (China Mobile) suggests that we can further evaluate the value of the feature in evaluation phase, not right now.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004545 P-CR Approval 23.700-91: Solution for KI#8 UE assisted analysis for usage of network slice . OPPO Rel-17 Revision of S2-2003759. Approved Approved
8.1 S2-2003760 P-CR Approval 23.700-91: UE assisted analytics for false base station detection. OPPO, China Unicom Rel-17 Noted Juan Zhang provides comments.
Belen (Ericsson) comments that 1) this is in the scope of SA3 work, 2) there is no particular reason why UE sends data that NWDAF or the NW as such has not requested, 3) NW has RRC measurements available to be used for this purpose.
Ericsson Objects to this document and suggests to NOTE it.
Yannick (Nokia) concurs with comments provided by Qualcomm and Ericsson. We suggest to note this proposal.
Yang Xu (OPPO) replies
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003772 P-CR Approval 23.700-91: KI #8, New Sol: Providing UE Analytics to the NWDAF via the User Plane. Convida Wireless LLC, AT&T, NEC Rel-17 Noted Juan Zhang provides comments.
Yannick (Nokia) suggests to note this proposal.
Mike (Convida Wireless) replies to Yannick (Nokia) and Juan (Qualcomm) and provides r01.
Juan Zhang (Qualcomm) provides further comments.
Farooq (AT&T) agrees with Mike's understanding that UPCAS down prioritization does not have impact on proposals for collecting data from user plane in eNA_Ph2.
Mike (Convida Wireless) responds to Juan Zhang (Qualcomm) and provides rev02.
Aihua (China Mobile) shares the same view with Mike that data collection from UPF by NWDAF could be in the scope of FS_ eNA_Ph2, and r02 looks good.
Mike (Convida Wireless) provides additional comments and provides rev03.
Juan Zhang (Qualcomm) can agree with r03 and ask a comment for clarification.
Mike (Convida Wireless) responds.
Juan Zhang (Qualcomm) reply comment.
==== Ph1 Revisions Deadline ====
Yannick (Nokia) : Nokia object to all versions for this proposal.
Convida Wireless (Mike) expresses his opinion that Nokia's objection is invalid. We explained why it was invalid on Monday. At least two other companies stated that they agree that the objection is not valid.
Yannick (Nokia) replies to Mike (Convida Wireless).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003783 P-CR Approval 23.700-91: KI#8, New Sol: UE data as an input for Control Plane load balancing analytics. Samsung Rel-17 Revision of S2-2000873. Revised to S2-2004546. Juan Zhang provides comments.
Yannick (Nokia) asks for clarifications.
Mehrdad (Samsung) replies to Qualcomm and Nokia.
Mehrdad (Samsung) provides r01.
Juan Zhang (Qualcomm) provides further comments
Mehrdad (Samsung) provides r02, r03.
Mehrdad (Samsung) provides r04, r05.
==== Ph1 Revisions Deadline ====
Yannick (Nokia) prefers r04.
Juan Zhang (Qualcomm) is OK with r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004546 P-CR Approval 23.700-91: KI#8, New Sol: UE data as an input for Control Plane load balancing analytics. Samsung Rel-17 Revision of S2-2003783. Approved Approved
8.1 S2-2003841 P-CR Approval 23.700-91: KI #8, New Sol: Analytics for WLAN Usage Experience using UE WLAN Usage Data. LG Electronics Rel-17 Noted Dimitris (Lenovo) has questions for clarification
Yannick (Nokia) asks for clarifications.
Juan Zhang (Qualcomm) supports Nokia's comments and requests to note the paper.
Xiaobo(Huawei) supports the principle of the paper from LGE and propose a way forward instead note the paper.
Jaehyu (LGE) replies to the comments and provides r01.
Belen (Ericsson) requests clarification in the contribution.
==== Ph1 Revisions Deadline ====
Juan Zhang (Qualcomm) ask to clarify why does NWDAF need to do this analytics.
Yannick (Nokia) asks for clarifications on r01.
Jaehyu (LGE) responds to Juan (Qualcomm)
Jaehyu (LGE) responds to Yannick (Nokia)
Yannick (Nokia) fine with r01 with the understanding that NWDAF will use WLANSP rules and Prioritized SSID list, in addition to MDT/SON data .
Belen (Ericsson) objects to all revisions of this contribution and initial version in the current form.
Belen (Ericsson) is not okay with this contribution, and request to remove the requirements for PCF to collect the data and then add an EN.
Yang Xu (OPPO) provides clarification. The benefit to go via PCF can be less impact to UE since the UE policy container is already there, which can be reused. So it should be ok to adopt the solution in TR and leave it to evaluation.
Jaehyu (LGE) responds to Yannick (Nokia) and Belen (Ericsson)
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003863 P-CR Approval 23.700-91: User Plane Based UE Data Collection . Qualcomm Incorporated Rel-17 Noted Dimitris (Lenovo) has questions for clarification
Yannick (Nokia) ask a general question on the proposal.
Mike (Convida Wireless) asks questions.
Juan Zhang (Qualcomm) answer Convida's question.
Yang Xu (OPPO) request for clarification
Juan Zhang (Qualcomm) answer the questions.
Juan Zhang (Qualcomm) answer the question from Nokia.
Juan Zhang (Qualcomm) reply OPPO's comments
Yang Xu (OPPO) comments more
Mike (Convida Wireless) further clarifies his concern.
Dimitris (Lenovo) responds to Juan
Mehrdad (Samsung) provides clarification to Convida.
Belen (Ericsson) provides r01
Mike (Convida Wireless) replies.
Juan Zhang (Qualcomm) replies.
Juan Zhang (Qualcomm) is OK with r01.
Yang Xu (OPPO) provides r01.
Juan Zhang (Qualcomm) is fine with OPPO's proposal which is r02.
==== Ph1 Revisions Deadline ====
Mehrdad (Samsung) supports both r01, r02 and would like to co-sign this.
Juan Zhang (Qualcomm) is OK to add Samsung as co-signer.
Aihua (China Mobile) comments.
Mehrdad (Samsung) comments to clarify for Aihua (China Mobile).
Yannick (Nokia) have similar comments as Aihua (China Mobile).
Mehrdad (Samsung) comments Nokia
Juan Zhang (Qualcomm) reply comments to Nokia and CMCC.
Aihua (China Mobile) objects to any version of this proposal.
Yannick (Nokia) can accept r02 at this stage.
Juan Zhang (Qualcomm) can not accept the rude rejection reason after the revision deadline and no any comments before.
Mehrdad (Samsung) asks China Mobile to reconsider its position.
Aihua (China Mobile) replies.
==== Ph1 Final Deadline ====
Yang Xu (OPPO) provides comments for moving on the solution
Juan Zhang (Qualcomm) provides comments to OPPO.
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003915 P-CR Approval 23.700-91: KI#8, New Sol: Analytics for Session Management Congestion Control Experience using UE Data. LG Electronics, SK Telecom, LG Uplus Rel-17 Revised to S2-2004547. Yannick (Nokia) provides comments.
LaeYoung (LGE) provides r01 and answers.
Mehrdad (Samsung) comments on original version and r01.
LaeYoung (LGE) provides r02 and answers.
Juan Zhang (Qualcomm) provides comments on all the versions
Yannick (Nokia) agrees with Qualcomm.
LaeYoung (LGE) provides r03 and answers to comments from Juan and Yannick.
==== Ph1 Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r03 proposed by chameLaeYoung.
Yannick (Nokia) comments on r03 and asks for clarification.
Mehrdad (Samsung) is OK with r03
Xiaobo (Huawei) support r03 proposed by chameLaeYoung.
Xiaobo (Huawei) respond to Yannick(Nokia).
LaeYoung (LGE) provides answers to comments from Yannick (Nokia).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004547 P-CR Approval 23.700-91: KI#8, New Sol: Analytics for Session Management Congestion Control Experience using UE Data. LG Electronics, SK Telecom, LG Uplus Rel-17 Revision of S2-2003915. Approved Approved
8.1 S2-2004153 P-CR Approval 23.700-91: KI #8, New Sols, Providing UE Analytics to the NWDAF. China Mobile Rel-17 Noted LaeYoung (LGE) asks a Q for clarification.
Yannick (Nokia) doesn't see the need for any of the two solutions.
Aihua (China Mobile) replies.
Mike (Convida Wireless) provides comments and questions.
Juan Zhang (Qualcomm) provides comment.
==== Ph1 Revisions Deadline ====
Juan Zhang (Qualcomm) suggests to note this proposal.
Yannick (Nokia) agrees with Juan (Qualcomm). Nokia object to the proposal.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 - - - KI 9: Dispersion analytic output provided by NWDAF - - Docs:=2 -
8.1 S2-2003649 P-CR Approval 23.700-91: KI #9, New Solution: Dispersion Analytic Output Provided by NWDAF. Spirent, AT&T, Sandvine, Convida Wireles Rel-17 Revised to S2-2004548. Yoonseon (Samsung) requests clarification.
Yingjie(ZTE) comments.
Dimitris (Lenovo) has a question for clarification
Peretz (Spirent) responds to Yoonseon
Peretz (Spirent) responds to Dimitris
Peretz (Spirent) responds to Yingjie
Malla (NTT DOCOMO) provides r01.
David (Samsung) provides r02.
Peretz (Spirent) reply to Malla (NTT DOCOMO) provided S2-2003649r01 modification.
Peretz (Spirent) replies to David's (Samsung) provided r02.
Peretz (Spirent) replying to Malla (NTT DOCOMO) with agreement to her proposed s2-2003649r01.
Gerald (Matrixx) provided comments.
David (Samsung) replies to Peretz.
Peretz (Spirent) replies to David with r03, slightly modifying David's r02
Peretz (Spirent) replied to Gerald's recommendation with rev04.
David (Samsung) is OK with r04.
==== Ph1 Revisions Deadline ====
Gerald (Matrixx) with no further comments on r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004548 P-CR Approval 23.700-91: KI #9, New Solution: Dispersion Analytic Output Provided by NWDAF. Spirent, AT&T, Sandvine, Convida Wireles Rel-17 Revision of S2-2003649. Approved Approved
8.1 - - - KI 11: Increasing efficiency of data collection - - Docs:=22 -
8.1 S2-2003580 P-CR Approval 23.700-91: Solution for reducing the redundancy of event reporting for NWDAF data collection. China Telecom Rel-17 Revised to S2-2004549. Dimitris (Lenovo) has questions for clarification
Song replies Dimitris (Lenovo)'s questions
Song(China Telecom) correct the email title and reply Dimitrios(Lenovel)'s comments.
Mehrdad (Samsung) comments
Leo (Deutsche Telekom) expresses concerns about this solution proposal
Song (China Telecom) replies Mehrdad(Samsung)'s comments.
Song (China Telecom) makes clarification on the concerns of Leo (Deutsche Telekom).
Yannick (Nokia) shares concerns from Deutsche Telekom.
Dimitris (Lenovo) supports Mehrdad comments
Song (China Telecom) provides further clarification based on Yannick (Nokia)'s comments and provide r01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004549 P-CR Approval 23.700-91: Solution for reducing the redundancy of event reporting for NWDAF data collection. China Telecom Rel-17 Revision of S2-2003580. Approved Approved
8.1 S2-2003802 P-CR Approval 23.700-91: Solution on efficient data collection by multiple NWDAF . Motorola Mobility, Lenovo Rel-17 Revision of S2-2000773. Revised to S2-2004550. Yannick (Nokia) provides comments.
Dimitris (Lenovo) responds to Yannick and provides r01.
Mehrdad (Samsung) provides comment on original version and r01 and suggests a possible merger between similar proposals.
Dimitris (Lenovo) responds to Mehrdad
Dimitris (Lenovo) comments on r01.
Dimitris (Lenovo) provides r02
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004550 P-CR Approval 23.700-91: Solution on efficient data collection by multiple NWDAF . Motorola Mobility, Lenovo Rel-17 Revision of S2-2003802. Approved Approved
8.1 S2-2003847 P-CR Approval 23.700-91: TR23700-91_KI#11_Solution on storing high frequency behaviours and related important information in NWDAF China Telecom Corporation Ltd. Rel-17 Noted Yoonseon(Samsung) asks clarification.
Yannick (Nokia) provides comments.
On behalf of Liu Liu (China Telecom)replies comments from Yannick (Nokia)
On behalf of Liu Liu (China Telecom)replies comments from Yoonseon(Samsung)
On behalf of Liu Liu (China Telecom)replies comments from Yoonseon(Samsung) and Yannick (Nokia)
Belen (Ericsson) asks for clarifications in the contribution
Liu Liu (China Telecom)replies comments from Belen (Ericsson)
==== Ph1 Revisions Deadline ====
Yannick (Nokia) suggests to note this document and come back to this issue in the next meeting.
Belen (Ericsson) suggests to note this document and come back to this issue in the next meeting.
==== Ph1 Final Deadline ====
Liu Liu (China Telecom)replies suggestions from Yannick (Nokia) and Belen (Ericsson)
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003873 P-CR Approval 23.700-91: KI #11, New Sol: Efficient determination of UPFs serving UEs and AoI. Huawei, HiSilicon Rel-17 Revised to S2-2004551. Yannick (Nokia) provides comments.
Xiaobo (Huawei) provide r01 to answer Nokia concerns.
Linghang (NEC) asks question for clarification.
Xiaobo (Huawei) provides further clarification as well as r02.
Linghang (NEC) is fine with r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004551 P-CR Approval 23.700-91: KI #11, New Sol: Efficient determination of UPFs serving UEs and AoI. Huawei, HiSilicon Rel-17 Revision of S2-2003873. Approved Approved
8.1 S2-2003874 P-CR Approval 23.700-91: KI #11, New Sol: Offline Data Collection for preparing NWDAF for future requests . Huawei, HiSilicon Rel-17 Revised to S2-2004552. Jungshin (Samsung) requests clarification
Yingjie(ZTE) ask for clarification.
Xiaobo (Huawei) provides clarification.
Jungshin (Samsung) requests further clarification
Gerald (Matrixx) provided comments.
Xiaobo (Huawei) provides further clarification as well as r01.
Gerald (Matrixx) provided the answer for Huawei and please for revision.
==== Ph1 Revisions Deadline ====
Jungshin (Samsung) is fine with r01 for this meeting.
Gerald (Matrixx) concern is not resolved in r01.
Xiaobo (Huawei) understand the concern from Gerald (Matrixx) and propose to live with r01 this meeting and fix it next meeting .
Gerald (Matrixx) confirm the correction at SA2#140E.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004552 P-CR Approval 23.700-91: KI #11, New Sol: Offline Data Collection for preparing NWDAF for future requests . Huawei, HiSilicon Rel-17 Revision of S2-2003874. Approved Approved
8.1 S2-2003878 P-CR Approval 23.700-91: KI #11, New Sol: Efficient data collection for AoI reusing existing 5GS signalling. Huawei, HiSilicon Rel-17 Approved Jungshin (Samsung) provides comments
Xiaobo(Huawei) provides clarification.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.1 S2-2003941 P-CR Approval 23.700-91: KI#11 and #18, New Sol: Enhancement on network exposure to allow data approximation. ETRI Rel-17 Revised to S2-2004553. Jungshin (Samsung) request clarification
Yannick (Nokia) provides comments and requests for clarification.
Soohwan (ETRI) replies to Samsung and Nokia.
Jungshin (Samsung) provides comments
Soohwan (ETRI) provides r01.
Soohwan (ETRI) replies to Jungshin (Samsung).
Gerald (Matrixx) provided comments.
Soohwan (ETRI) replies to Gerald (Matrixx)
Gerald (Matrixx) replies to ETRI in conjunction to S2-2004087.
Lei (Tencent) replies to Gerald(Matrixx) and provide comments.
Soohwan (ETRI) replies to Gerald (Matrixx) and Lei (Tencent)
Lei (Tencent) respond and fully agree with Soohwan to have separate threads and also the proposed way forward.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004553 P-CR Approval 23.700-91: KI#11 and #18, New Sol: Enhancement on network exposure to allow data approximation. ETRI Rel-17 Revision of S2-2003941. Approved Approved
8.1 S2-2003971 P-CR Approval 23.700-91: KI #11 & #2, New Sol: Efficient data management . NTT DOCOMO Rel-17 Revised to S2-2004554. Mehrdad (Samsung) provides comment and suggests a possible merger between similar proposals.
Dimitris (Lenovo) has questions for clarification
Yannick (Nokia) provides comments.
Malla (NTT DOCOMO) replies to Samsung.
Malla (NTT DOCOMO) provides r01.
Mehrdad (Samsung) provides comment.
Xiaobo (Huawei) provides comment.
Yannick (Nokia) provides comments on r01.
Malla (NTT DOCOMO) replies to Nokia.
Yannick (Nokia) is fine with r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004554 P-CR Approval 23.700-91: KI #11 & #2, New Sol: Efficient data management . NTT DOCOMO Rel-17 Revision of S2-2003971. Approved Approved
8.1 S2-2004274 P-CR Approval 23.700-91: KI #11, New Sol: User-Plane specialized NWDAF. Sandvine, SK, Spirent Rel-17 Noted Yannick (Nokia) express concerns about this proposal. Nokia suggest to NOTE this document, this is out of the scope of eNA_Ph2 study.
Boris Lifshitz (Allot) raised questions for clarification.
Manuel (Sandvine) response to Allot questions.
Manuel (Sandvine) responds to Nokia; explaining why the solution S2-2004274 is into the scope of eNA_Ph2 study.
David (Samsung) agrees with Nokia wrt the proposal to note this document.
Boris (Allot) ask to clarify the questions.
Manuel (Sandvine) responding to David (Samsung), I already answered to Nokia and here you have your answer.
Manuel (Sandvine) provides r01
Manuel (Sandvine) response for Nokia concerns. The S2-2004274r01 is part of the scope of eNA_Ph2 study.
==== Ph1 Revisions Deadline ====
Ericsson (Belen) supports r01 and believes that is the scope of this study.
Yannick (Nokia) : Nokia object to r00 and r01.
Susana (Vodafone) supports r01
==== Ph1 Final Deadline ====
Manuel (Sandvine) responds to Jannick (Nokia) in regards to the objection of the document.
==== Close of meeting Ph1 ====
Noted
8.1 S2-2004285 P-CR Approval 23.700-91: KI #11, New Sol: Sobriety and efficiency mechanisms. Orange, Huawei Rel-17 Revision of S2-2000099. Approved Yannick (Nokia) provides comments.
==== Ph1 Revisions Deadline ====
Yannick (Nokia) asks what we should do with this contribution.
Xiaobo (Huawei) responds to Yannick (Nokia).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.1 S2-2004299 DISCUSSION Information KI #11, Use Case QoS sustainability low latency Use case Sandvine Incorporated Rel-17 Noted
==== Ph1 Revisions Deadline ====
Noted
8.1 S2-2003753 P-CR Approval 23.700-40: KI #5, New Sol: NSQ assisted dynamic adjustment of data rate per slice via NAS signalling . Apple Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.1 S2-2003804 P-CR Approval 23.700-40: KI #5, New Sol: NSQ assisted dynamic adjustment of data rate per slice via user plane adjustment. Apple Rel-17 Revised to S2-2004579. Krisztian (Apple) provides r01.
Stefano Faccin (Qualcomm) asks for clarification as to what comments from other companies lead to Apple posting rev. 01 (perhaps we missed some emails), or whether rev. 01 is just a post-deadline update of the paper by the original authors.
Krisztian (Apple) responds to Stefano.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004579 P-CR Approval 23.700-40: KI #5, New Sol: NSQ assisted dynamic adjustment of data rate per slice via user plane adjustment. Apple Rel-17 Revision of S2-2003804. Approved Approved
8.1 S2-2003770 P-CR Approval 23.700-40: KI#5 new solution On enforcement of MBR UL/DL per S-NSSAI. Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2004580. Hoyeon (Samsung) provides r01.
Jinguo(ZTE) provides comment.
Alessio(nokia) provides response: we use the concept of master PCF that is also described in the contribution on counting of PDU sessions per slice.
Alessio(nokia) asks Samsung to clarify why they added the note. The PCF triggers the modification when its policy is to do so!
Hoyeon (Samsung) replies to Alessio.
==== Ph1 Revisions Deadline ====
Alessio(nokia) Actually both. Anyhow I can live with the revision r01 with EN and will provide update at next meeting.
Jinguo(ZTE) comments
Hoyeon (Samsung) comments
Jinguo(ZTE) response
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004580 P-CR Approval 23.700-40: KI#5 new solution On enforcement of MBR UL/DL per S-NSSAI. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003770. Approved Approved
8.1 - - - KI 12: NWDAF-assisted RFSP policy - - Docs:=12 -
8.1 S2-2003693 P-CR Approval 23.700-91: KI#12, New Solution: Reusing Service Experience Analytics. Ericsson Rel-17 Revised to S2-2004555. Yoonseon (Samsung) provides comments.
Yingjie(ZTE) comments.
Xiaobo (Huawei) provides the comments to Yingjie(ZTE).
Antoine (Orange): requests the clarification of a paragraph.
Jiayifan Liu(China Telecom) provides r01.
Belen (Ericsson) provides r02, provides clarifications.
Belen(Ericsson) provides r03 clarifying the paragraph.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004555 P-CR Approval 23.700-91: KI#12, New Solution: Reusing Service Experience Analytics. Ericsson Rel-17 Revision of S2-2003693. Approved Approved
8.1 S2-2003694 P-CR Approval 23.700-91: Removing Editor´s note on KI#12: NWDAF-assisted RFSP policy. Ericsson Rel-17 Revised to S2-2004556. Yoonseon (Samsung) provides r01 and comments
Xiaobo (Huawei) supports the r01 provided by Samsung.
Belen (Ericsson) asks for clarifications.
Yingjie(ZTE) comments.
Yoonseon (Samsung) replies to Belen
Belen (Ericsson) is okay with r01, would add Huawei as cosigner as requested.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Xiaoyan (CATT) asks questions for clarification.
LiMeng (Huawei) replies to Xiaoyan (CATT).
Revised
8.1 S2-2004556 P-CR Approval 23.700-91: Removing Editor´s note on KI#12: NWDAF-assisted RFSP policy. Ericsson, Samsung, Huawei Rel-17 Revision of S2-2003694. Approved Approved
8.1 S2-2003825 P-CR Approval 23.700-91: KI #12, New Sol: NWDAF-assisted RFSP Policy. Apple Rel-17 Noted Jiayifan Liu(China Telecom) provides comments.
Juan Zhang (Qualcomm) provides comments.
Krisztian (Apple) provides r01 and responds to Jiayifan.
Yoonseon(Samsung) requests clarification.
Krisztian (Apple) provides r02.
Krisztian (Apple) responds to Juan.
Yoonseon(Samsung) requests clarification further.
Belen (Ericsson) asks for clarifications in the contribution
Krisztian (Apple) provides r03.
==== Ph1 Revisions Deadline ====
Haris (Qualcomm) proposes to note this pCR since the solution is based on incorrect assumption about use of RFSP by RAN, use of radio capabilities and assignment of UE Radio Capability ID in RACS
Krisztian (Apple) responds to Haris.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.1 S2-2003872 P-CR Approval 23.700-91: KI#12, New Sol: Congestion Info as input for RFSP generation. Huawei, HiSilicon Rel-17 Approved Yoonseon (Samsung) requests clarification.
Haiyang (Huawei) clarifies.
Yoonseon (Samsung) replies.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.1 S2-2003925 DISCUSSION Discussion Draft discussion paper on NWDAF provides service experience/behavior statistics and prediction to assist RFSP policy. China telecom Noted
==== Ph1 Revisions Deadline ====
Noted
8.1 S2-2004008 P-CR Approval 23.700-91: Solution update for Key Issue #12: NWDAF-assisted RFSP policy . China Telecom Rel-17 Revised to S2-2004557. Antoine (Orange): provides r01 to remove user profile information (career, gender, age).
Jiayifan Liu(China Telecom) responds to Antoine.
David (Samsung) agrees with Orange; proposes to note this pCR (r00, r01).
Juan Zhang (Qualcomm) supports Orange's comment to remove the user profile information (career, gender, age).
Susana (Vodafone) agrees to removing career, gender and age for user profile information in r01. Objects to initial version of S2-2004008
On behalf of Jiayifan Liu(China Telecom) responds to David and provides r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004557 P-CR Approval 23.700-91: Solution update for Key Issue #12: NWDAF-assisted RFSP policy . China Telecom Rel-17 Revision of S2-2004008. Approved Approved
8.1 S2-2004074 P-CR Approval 23.700-91: KI#12, New Sol: NWDAF-assisted RFSP Policy Configuration. Tencent Rel-17 Revised to S2-2004436. Antoine (Orange): objects to r00 but could accept a revision complying to the NWDAF architectural model.
Lei (Tencent): thanks for the two comments and will provide a revision ASAP.
Lei (Tencent): provide S2-4074r01 .
Yoonseon(Samsung) asks clarification.
Lei(Tencent) provides r02 .
==== Ph1 Revisions Deadline ====
Belen (Ericsson) objects to any revision and initial version.
Lei(Tencent) is surprised with last minute objection from Belen (Ericsson). The concern is not concrete, Ericsson didn't provide any comment before the revision deadline. To address the concern, Lei(Tencent) proposed to add an EN to about the RFSP policy configuration (capture in MoM) and document the solution in this meeting.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004436 P-CR Approval 23.700-91: KI#12, New Sol: NWDAF-assisted RFSP Policy Configuration. Tencent Rel-17 Revision of S2-2004074. Approved Approved
8.1 S2-2004082 P-CR Approval 23.700-91: KI #12, New Sol: NWDAF-assisted RFSP index selection. Samsung Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.1 - - - KI 13: Triggering conditions for analytics - - Docs:=2 -
8.1 S2-2004182 P-CR Approval 23.700-91: KI #13, New Sol: Triggers for requesting analytics. CATT Rel-17 Revised to S2-2004558. David (Samsung) provides comments.
Xiaoyan (CATT) clarifies and provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004558 P-CR Approval 23.700-91: KI #13, New Sol: Triggers for requesting analytics. CATT Rel-17 Revision of S2-2004182. Approved Approved
8.1 - - - KI 14: NWDAF-assisted application detection - - Docs:=2 -
8.1 S2-2004183 P-CR Approval 23.700-91: KI #14, New Sol: new application detection. Samsung Rel-17 Revised to S2-2004559. Linghang (NEC) has questions for clarification
Yoonseon (Samsung) replies to Linghang
Peretz (Spirent) has a question for clarification
Yoonseon (Samsung) replies to Peretz
Peretz (Spirent) follow question to Yoonseon
Yoonseon (Samsung) provides r01, and replies to Peretz.
Peretz (Spirent) response to Yoonseon's r01 update.
Yoonseon (Samsung) replies to Peretz.
Linghang (NEC) provides further comments.
Yoonseon (Samsung) provide r02 and replies to Linghang
Linghang (NEC) replies to Yoonseon on r02.
Peretz (Spirent) further modified revision 02 and providing r03
Yoonseon(Samsung) is Ok for r03.
Yoonseon(Samsung) replies to Linghang
Linghang (NEC) is fine for r03
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004559 P-CR Approval 23.700-91: KI #14, New Sol: new application detection. Samsung Rel-17 Revision of S2-2004183. Approved Approved
8.1 - - - KI 15: User consent for UE data collection/analysis - - Docs:=5 -
8.1 S2-2003670 LS OUT Approval [DRAFT] LS on user consent for analytics Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2004560. Mehrdad (Samsung) comments on this LS.
Yannick (Nokia) replies to Samsung comments.
Mehrdad (Samsung) provides r01.
Yannick (Nokia) provides r02.
==== Ph1 Revisions Deadline ====
Mehrdad (Samsung) is OK with r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004560 LS OUT Approval LS on user consent requirements for analytics SA WG2 Rel-17 Revision of S2-2003670. Approved Approved
8.1 S2-2003671 P-CR Approval 23.700-91: KI #15, Solution #3: updates to call flow. Nokia, Nokia Shanghai Bell Rel-17 Noted Yannick (Nokia) suggests to NOTE this document (from Nokia) and focus only on NEC proposal in S2-2003762.
==== Ph1 Revisions Deadline ====
Noted
8.1 S2-2003762 P-CR Approval 23.700-91: KI#15 Sol#3: Update to User consent for UE data colection . NEC Rel-17 Revised to S2-2004561. Iskren (NEC) provides r01.
Yannick (Nokia) provides comments.
Mehrdad (Samsung) comments.
Iskren (NEC) answers questions from Yannick (Nokia) and Mehrdad (Samsung).
Susana (Vodafone) makes question for clarification
Iskren (NEC) answers questions from Susana (Vodafone).
Susana (Vodafone) replies to Iskran answers.
Iskren (NEC) answers Susana (Vodafone).
Mehrdad (Samsung) comments on original version and r01.
Iskren (NEC) answers questions from Mehrdad (Samsung).
Susana (Vodafone) comments on EN proposal from Iskren
Iskren (NEC) responds to comments from Susana (Vodafone), Yannick (Nokia) and Mehrdad (Samsung) and provides r02.
Susana (Vodafone) can accept r02
Yannick (Nokia) provides r03.
Iskren (NEC) agrees with r03 provided by Yannick (Nokia).
==== Ph1 Revisions Deadline ====
Susana (Vodafone) agrees with r03
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004561 P-CR Approval 23.700-91: KI#15 Sol#3: Update to User consent for UE data colection . NEC Rel-17 Revision of S2-2003762. Approved Approved
8.1 - - - KI 16: UP optimization for edge computing - - Docs:=11 -
8.1 S2-2003803 P-CR Approval 23.700-91: Solution for Key Issue 16 - Selecting an Edge Application Server based on NWDAF analytics . Motorola Mobility, Lenovo Rel-17 Revised to S2-2004562. Yoonseon(Samsung) asks clarification.
Dimitris (Lenovo) provides r01
Belen (Ericsson) propose to NOTE this contribution since the scoop of the KI says that it should be aligned with the agreements on EC that have not been reached yet.
Dimitris (Lenovo) responds to Belen (Ericsson) and indicates that this solution is within the scope of Key Issue 16
Belen (Ericsson) replies to Lenovo.
Dimitris (Lenovo) provides r02 to address concerns of Belen (Ericsson)
==== Ph1 Revisions Deadline ====
Belen (Ericsson) can accept t02
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004562 P-CR Approval 23.700-91: Solution for Key Issue 16 - Selecting an Edge Application Server based on NWDAF analytics . Motorola Mobility, Lenovo Rel-17 Revision of S2-2003803. Approved Approved
8.1 S2-2003826 P-CR Approval 23.700-91: KI #16, New Sol: UP optimization for Edge Computing. Apple Rel-17 Postponed LaeYoung (LGE) ask a question.
Yannick (Nokia) requests for clarification.
Krisztian (Apple) responds to LaeYoung and Yannick.
LaeYoung (LGE) ask a f-up question.
Belen (Ericsson) asks questions for clarification.
Krisztian (Apple) provides r01 and responds to Belen and LaeYoung.
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this paper and cannot accept all versions because there are so many unclear points.
Belen (Ericsson) prefers to NOTE or POSTPONE this paper and work further on this
Susana (Vodafone) can support postponing to next meeting to work out some incomplete/inconsistent points, and comments to the paper.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.1 S2-2003843 P-CR Approval 23.700-91: KI#16, New Sol: UE Presence Pattern analytics to support edge computing. LG Electronics, SK Telecom, LG Uplus Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.1 S2-2003882 P-CR Approval 23.700-91: KI #10 & #16, New Sol: Solution for NWDAF assisted UP optimization for edge computing. Huawei, HiSilicon Rel-17 Revised to S2-2004563. Dimitris (Lenovo) comments
Linghang (NEC) provides comments.
Xiaobo (Huawei) provides clarification to Dimitris (Lenovo) and also r01 is provided based on comments from Linghang (NEC).
Dimitris (Lenovo) responds to Xiaobo
Xiaobo (Huawei) provides further clarification to Dimitris (Lenovo).
Dimitris (Lenovo) responds to Xiaobo (Huawei).
Yannick (Nokia) agrees with NEC and provides additional comments.
Peretz (Spirent) asking for location=RAN clarification
Xiaobo (Huawei) provides r02 per comment from Yannick(Nokia)/Peretz(Spirent) .
Dimitris (Lenovo) provides r03
Xiaobo (Huawei) is ok with r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004563 P-CR Approval 23.700-91: KI #10 & #16, New Sol: Solution for NWDAF assisted UP optimization for edge computing. Huawei, HiSilicon Rel-17 Revision of S2-2003882. Approved Approved
8.1 S2-2003899 P-CR Approval 23.700-91: KI#16, New solution for KI#16: NWDAF assisted UP optimization for EC. CATT Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.1 S2-2004084 P-CR Approval 23.700-91: KI #16, New Sol: Network Assisted DNAI selection. Samsung Rel-17 Revised to S2-2004564. Linghang (NEC) provides comment.
Yoonseon(Samsung) Replies to Linghang for clarification.
LaeYoung (LGE) comments.
Yoonseon (Samsung) replies to LaeYoung
Linghang (NEC) replies to Yoonseon's question.
Yoonseon(Samsung) provides r02 and replies to Linghang.
Linghang (NEC) is fine with r02.
Xiaobo (Huawei) provides r03.
Yoonseon(Samsung) is ok for r03
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004564 P-CR Approval 23.700-91: KI #16, New Sol: Network Assisted DNAI selection. Samsung, Huawei Rel-17 Revision of S2-2004084. Approved Approved
8.1 S2-2004156 P-CR Approval 23.700-91: Key Issue #16, New Sol: UP optimization for edge computing. China Mobile Rel-17 Revised to S2-2004565. Yoonseon (Samsung) asks clarification.
Aihua (China Mobile) replies and provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004565 P-CR Approval 23.700-91: Key Issue #16, New Sol: UP optimization for edge computing. China Mobile Rel-17 Revision of S2-2004156. Approved Approved
8.1 - - - KI 17: Definition of accuracy levels - - Docs:=2 -
8.1 S2-2004286 P-CR Approval 23.700-91: KI #17, New Sol: Accuracy levels and options. Orange Rel-17 Revised to S2-2004566. Yannick (Nokia) asks for clarification.
David (Samsung) asks for clarifications.
Antoine (Orange) replies to Samsung.
Antoine (Orange) provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004566 P-CR Approval 23.700-91: KI #17, New Sol: Accuracy levels and options. Orange Rel-17 Revision of S2-2004286. Approved Approved
8.1 - - - KI 18: Enhancement for real-time communication with NWDAF - - Docs:=5 -
8.1 S2-2003905 P-CR Approval 23.700-91: KI #18, New Sol: Pre-analytics based solution for Real-Time communication with NWDAF. China Unicom Rel-17 Revised to S2-2004567. Yannick (Nokia) provides comments and requests for clarification.
Chi (China Unicom) replies to Yannick and provides r01.
Yoonseon (Samsung) comments.
Chi (China Unicom) provides r02.
Gerald (Matrixx) provided comments.
Chi (China Unicom) replies to Gerald (Matrixx).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004567 P-CR Approval 23.700-91: KI #18, New Sol: Pre-analytics based solution for Real-Time communication with NWDAF. China Unicom Rel-17 Revision of S2-2003905. Approved Approved
8.1 S2-2004083 P-CR Approval 23.700-91: KI#18, New Sol: Support of Multiple NWDAF with Efficient Cooperation. Tencent Rel-17 Approved Yoonseon(Samsung) comments.
Lei(Tencent) responds to Yoonseon(Samsung) comments.
Yannick (Nokia) provides comments.
Lei(Tencent) provides comments to Yannick(Nokia).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.1 S2-2004087 P-CR Approval 23.700-91: KI#18, New Sol: Enhancement for Real-Time Communication with NWDAF. Tencent Rel-17 Revised to S2-2004568. Linghang (NEC) provides comments.
Lei (Tencent) provides response.
Yannick (Nokia) provides comments and requests for clarification.
Lei (Tencent) provides clarification to Yannick(Nokia).
Linghang (NEC) provides further comments.
Lei (Tencent) provides further comments and provide r01 .
Linghang (NEC) provides r02.
Lei (Tencent) in general ok with NEC's change and provides r03 on top of r02 with alignment of text and figure.
Linghang (NEC) is fine with r03
Gerald (Matrixx) provided comments.
Lei(Tencent) respond to Gerald (Matrixx).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004568 P-CR Approval 23.700-91: KI#18, New Sol: Enhancement for Real-Time Communication with NWDAF. Tencent Rel-17 Revision of S2-2004087. Approved Approved
8.1 - - - KI 19: Trained data model sharing between multiple NWDAF instances - - Docs:=2 -
8.1 S2-2004043 P-CR Approval 23.700-91: KI #19, New Sol, Trained Data Model Sharing between NWDAF instances. China Mobile Rel-17 Revised to S2-2004569. Jungshin (Samsung) request clarification
Aihua (China Mobile) replies.
==== Ph1 Revisions Deadline ====
Leo (Deutsche Telekom) prefers r01 rather than the original version.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.1 S2-2004569 P-CR Approval 23.700-91: KI #19, New Sol, Trained Data Model Sharing between NWDAF instances. China Mobile Rel-17 Revision of S2-2004043. Approved Approved
8.1 - - - KI 20: NWDAF assisting in detecting anomaly events for the user plane - - Docs:=0 -
8.1 - - - KI 21: NWDAF assisting in user plane performance - - Docs:=0 -
8.2 - - - Study on enhanced support of Non-Public Networks (FS_eNPN) - - Docs:=130 -
8.2 - - - TR Cover Sheet - - Docs:=1 -
8.2 S2-2003603 TS OR TR COVER Approval Presentation of Report to TSG for information: TR 23.700-07 Ericsson (Rapporteur) Rel-17 Noted Hualin (Huawei) propose to note this paper, because the study is far from 60% and too pre-mature for information.
Dieter (Deutsche Telekom) agrees with Huawei and alos proposes to note this paper.
Peter Hedman (Ericsson) provides comments and r01.
Saso (Intel) supports sending out the TR to SA for information. At the end of this meeting the 60% level of completion should be reached.
Hualin (Huawei) we get few conclusion currently, just a batch of solutions even without evaluation contradicting with each other. How can we say 60% should be reached?
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) proposes to agree r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 - - - Solution to KI#1 - - Docs:=26 -
8.2 S2-2003604 P-CR Approval 23.700-07: KI#1, Update solution#3: SNPN access using MOCN. Ericsson Rel-17 R03 agreed. Revised to S2-2004341 Devaki (Nokia) provides r01.
Saso (Intel) proposes to NOTE this document.
Qianghua (Huawei) provides comments.
Peter Hedman (Ericsson) provides answers to the comments and a r02.
Peter Hedman (Ericsson) provides reply to Qianghua.
Saso (Intel) provides r03.
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) r03 is ok.
Qianghua (Huawei) is OK with r03
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004341 P-CR Approval 23.700-07: KI#1, Update solution#3: SNPN access using MOCN. Ericsson Rel-17 Revision of S2-2003604_R03. Approved Approved
8.2 S2-2003736 P-CR Approval 23.700-07: KI #1, Sol #1: Update to remove ENs. Intel Rel-17 Revised, merging S2-2003724, S2-2003605 and S2-2004061 to S2-2004310 Chia-Lin (MediaTek) provides comments and r01
Lei(Tencent) think Chia-Lin (MediaTek) should comment and provide comments on 4310 instead of 3736. Also request clarification about the proposed change.
Saso (Intel) points that this contributions has been merged with three other and revised to S2-2004310. Please provide your comments on the correct threa
Revised
8.2 S2-2004310 P-CR Approval 23.700-07: KI #1, Sol #1: Update to remove ENs. Intel, Ericsson, Tencent, OPPO Rel-17 Revision of S2-2003736, merging S2-2003724, S2-2004061 and S2-2003605. R13 agreed. EN wording needs to be finalized. Revised to S2-2004342 Qianghua (Huawei) provides r01 and comments.
Saso (Intel) provides answers to Qianghua (Huawei).
Chia-Lin (MediaTek) provides comments.
Saso (Intel) provides r02.
Josep (DT) comments.
Chen (OPPO) provides r03.
Saso (Intel) seeks clarifications.
Devaki (Nokia) provides r03
Chen (OPPO) loaded r03 on 01/Jun/2020, around 16:50CEST.
Devaki (Nokia) indicated provision of r03, email 01/Jun/2020, 19:40CEST.
Request Nokia to resend comment under a non-clashing revision number.
Devaki (Nokia) provides r04.
Saso (Intel) provides r05.
Josep (DT) replies to Saso (Intel).
Qianghua (Huawei) provides r06 and comments.
Saso (Intel) asks Josep (DT) for urgent clarification.
Josep (DT) provides a quick reply to Saso (Intel).
Peter Hedman (Ericsson) provides question to Josep.
Saso (Intel) asks Josep (DT) to clarify their position wrt equal treatment of S2-2004310 and S2-2004332.
Josep (DT) answers Saso the missing part of the question.
Antoine (Orange) support Josep's comments and makes additional comments.
Saso (Intel) replies to Antoine (Orange) and Josep (DT).
Sebastian (Qualcomm) suggests to avoid terminology fights and to discuss whether SNPN access based on PLMN credentials needs to be supported during conclusion phase.
Dieter (Deutsche Telekom) provides r07.
Josep (DT) replies to Saso's comment regarding unfairness.
Saso (Intel) provides r07.
Saso (Intel) provides r08 building on r06.
Dieter (Deutsche Telekom) provides r09.
Qianghua (Huawei) provides responses and r10.
Josep (DT) replies to Saso (Intel) and advises to review r11.
Saso (Intel) proposes r12.
Chris (Vodafone) proposes r13 to not ban normal IoT devices.
Qianghua (Huawei) provides responses and r13.
Josep (DT) provides r14 correcting the ED.
Qianghua (Huawei) provides responses and r14.
==== Ph1 Revisions Deadline ====
Qianghua (Huawei) provides a preference order (high->low) for the acceptable version:
r11 -> r10 ->r07->r06
Peter Hedman (Ericsson) proposes to approve r14 and provides reply to Qianghua.
Qianghua (Huawei) can live with r14 for progress
Saso (Intel) is OK with r14.
Chris (Vodafone) requests an explanation on why the changes in R13 are not used. (R14 seems to be an editorial on top of R12 that ignored the R13 changes)
Saso replies to Chris (Vodafone) and confirms being OK with r13.
Peter Hedman (Ericsson) is ok with r13
Qianghua (Huawei) can live with r13 for progress
Antoine (Orange) supports r14 but can live with r13.
Dieter (Deutsche Telekom) can conditionally live with r13 for the sake of progress. Alternatively r11 would work.
The condition is that for the EN on PLMN selection the service requirement need to be clarified with SA1 first, not just CT1.
Chris (Vodafone) is fine with Dieter (Deutsche Telekom)'s condition.
Saso (Intel) seeks clarification on Dieter (Deutsche Telekom)'s condition.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004342 P-CR Approval 23.700-07: KI #1, Sol #1: Update to remove ENs. Intel, Ericsson, Tencent, OPPO Rel-17 Revision of S2-2004310_R13 . Approved Approved
8.2 S2-2003605 P-CR Approval 23.700-07: KI#1: Merged solution for SNPN access using credentials owned by an entity separate from the SNPN. Ericsson Rel-17 Merged into S2-2004310 Merged
8.2 S2-2003724 P-CR Approval 23.700-07: KI#1, Sol#1 Update: Missing UE requirements on configured Service Provider lists. OPPO Rel-17 Merged into S2-2004310 Merged
8.2 S2-2004061 P-CR Approval 23.700-07: KI#1, Sol#1: Update to clarify Rel-17 UE attempting to register Rel-16 SNPN. Tencent Rel-17 Merged into S2-2004310 Merged
8.2 S2-2003606 P-CR Approval 23.700-07: KI#1, New Sol: Solution to support SNPN access using 3rd party credentials via external Credential Provider. Ericsson Rel-17 R04 agreed. Revised to S2-2004343 Devaki (Nokia) comments.
Chia-Lin (MediaTek) provides comments.
Qianghua (Huawei) provides comments.
Sebastian (Qualcomm) provides r01.
Saso (Intel) asks for clarification.
Peter Hedman (Ericsson) provides answers to the comments received.
Qianghua (Huawei) provides comments and r01.
Peter Hedman (Ericsson) provides r02 and comments.
Qianghua (Huawei) provides r03.
Antoine (Orange) provides r04.
Peter Hedman (Ericsson) provides r05.
==== Ph1 Revisions Deadline ====
Qianghua (Huawei) provides a preference order (high->low) for the acceptable version:
r04 -> r05
Antoine (Orange) objects to r05, accepts r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004343 P-CR Approval 23.700-07: KI#1, New Sol: Solution to support SNPN access using 3rd party credentials via external Credential Provider. Ericsson Rel-17 Revision of S2-2003606_R04. Approved Approved
8.2 S2-2003994 P-CR Approval 23.700-07: KI #1, Sol #4: Update to remove ENs. Huawei, HiSilicon Rel-17 R09 agreed. Revised to S2-2004344 Genadi (Motorola Mobility) provides revision r01.
Devaki (Nokia) provides revision r02.
Qianghua (Huawei) provides r03
Sebastian (Qualcomm) provides r04
Qianghua (Huawei) provides r05
Dieter (Deutsche Telekom) provides r06.
Peter Hedman (Ericsson) provides r07 and comments
Dieter (Deutsche Telekom) comments.
Antoine (Orange) provides r08.
Qianghua (Huawei) provides r09
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004344 P-CR Approval 23.700-07: KI #1, Sol #4: Update to remove ENs. Huawei, HiSilicon Rel-17 Revision of S2-2003994_R09. Approved Approved
8.2 S2-2004024 P-CR Approval 23.700-07: KI #1, New Sol: Solution #1 plus support for UEs that do not have sufficient information for SNPN selection. Intel Rel-17 Approved Chia-Lin (MediaTek) provides comments and ask for clarification
Saso (Intel) provides clarification
Amanda Xiang (Futurewei) ask questions for clarification.
Devaki (Nokia) raises concerns with the solution.
Saso (Intel) replies to Devaki (Nokia).
Saso (Intel) replies to Amanda Xiang (Futurewei).
Antoine (Orange) raises strong concerns.
Saso (Intel) replies to the strong concerns from Antoine (Orange).
==== Ph1 Revisions Deadline ====
Antoine (Orange) objects to this pCR.
==== Ph1 Final Deadline ====
Saso (Intel) replies to Antoine (Orange) that his objection is unjustified.
==== Close of meeting Ph1 ====
Approved
8.2 S2-2004140 P-CR Approval 23.700-07: KI #1, Sol #2: Updated to enhance and support SNPN along with credentials owned by an entity separate from the SNPN. Nokia, Nokia Shanghai Bell Rel-17 R03 agreed. Revised to S2-2004345 Chia-Lin (MediaTek) provides comments and r01.
Devaki (Nokia) provides r02
Sebastian (QC) provides r03.
Dieter (Deutsche Telekom) provides r04.
==== Ph1 Revisions Deadline ====
Devaki (Nokia) answers to DT / QCOM.
Peter Hedman (Ericsson) provides question while ok with r04 for this meeting.
Devaki (Nokia) answers Ericsson (Peter)'s question.
Sebastian (Qualcomm) objects to r04 but is fine with r03.
==== Ph1 Final Deadline ====.
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004345 P-CR Approval 23.700-07: KI #1, Sol #2: Updated to enhance and support SNPN along with credentials owned by an entity separate from the SNPN. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2004140_R03. Approved Approved
8.2 S2-2004192 P-CR Approval 23.700-07: Solution for SNPN credential provisioning via PLMN. Alibaba Group Rel-17 Merged into S2-2004373 Devaki (Nokia) provides comments.
Irfan (Cisco) comments
==== Ph1 Revisions Deadline ====
Youngkyo(Samsung) proposes to note as merged to 4096
Josep (DT) objects to this pCR.
Peter Hedman (Ericsson) propose to mark it as merged to 4096 as suggested by Youngkyo
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2004212 P-CR Approval 23.700-07: KI #1, New Sol: UE external subscription data stored in the SNPN. Motorola Mobility, Lenovo Rel-17 R01 agreed. Revised to S2-2004346 Marco(Huawei) makes questions/comments for clarification and welcomes a revision from the author for addressing them
Devaki (Nokia) has similar questions as Huawei/Marco.
Genadi (Motorola Mobility) answers questions from Huawei/Marco and Nokia/Devaki and provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004346 P-CR Approval 23.700-07: KI #1, New Sol: UE external subscription data stored in the SNPN. Motorola Mobility, Lenovo Rel-17 Revision of S2-2004212_R01. Approved Approved
8.2 S2-2004232 P-CR Approval 23.700-07: KI #1, Network assisted service continuity and mobility consideration for solution 1 and 2. Futurewei, Philips Rel-17 R06 agreed. Revised to S2-2004347 Devaki (Nokia) proposes to merge this with solution #2 (S2-2004332).
Genadi (Motorola Mobility) provides comments/questions.
Josep (DT) comments and asks question.
Amanda Xiang (Futurewei) provides response to Motorola and Nokia comments. Also provide revision r01 to address the comments.
Saso (Intel) comments.
Amanda Xiang (Futurewei) response for Intel comments and provide new revision r03.
Amanda Xiang (Futurewei) responses to the comments inline.
Sebastian (Qualcomm) provides r04.
Amanda Xiang (Futurewei) responses to the revision r04.
Peter Hedman (Ericsson) provides comments and r05.
Dieter (Deutsche Telekom) provides r06.
Amanda Xiang (Futurewei) provides responses to Ericsson's comments and revision inline.
==== Ph1 Revisions Deadline ====
Amanda Xiang (Futurewei) is ok with r06.
Saso (Intel) is OK with r06.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004347 P-CR Approval 23.700-07: KI #1, Network assisted service continuity and mobility consideration for solution 1 and 2. Futurewei, Philips Rel-17 Revision of S2-2004232_R06. Approved Approved
8.2 S2-2004222 P-CR Approval 23.700-07: Addressing open issues for Solution 2. Qualcomm Incorporated Rel-17 Revised, merging S2-2003725, to S2-2004332 Revised
8.2 S2-2004332 P-CR Approval 23.700-07: Addressing open issues for Solution 2. Qualcomm Incorporated, OPPO, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2004222, merging S2-2003725. R08 agreed. Revised to S2-2004348 Qianghua (Huawei) provides comments.
Sebastian (Qualcomm) replies to Qianghua.
Xiaowan (vivo) provides comments and r01.
Sebastian (QC) replies to vivo and provides r02
Josep (DT) asks a question for basic understanding of the solution (based on r01).
Qianghua (Huawei) provides further responses.
Sebastian (Qualcomm) replies to Josep and provides r03.
Josep (DT) replies to Sebastian (Qualcomm) and comments.
Sebastian (Qualcomm) replies to Josep and provides r04.
Peter Hedman (Ericsson) provides comments
Josep (DT) replies to Sebastian (Qualcomm).
Dieter (Deutsche Telekom) provides r05.
Saso (Intel) supports Sebastian (Qualcomm)'s replies to Josep
Josep (DT) replies to Sebastian and Saso.
Sebastian (QC) replies to Dieter.
Sebastian (Qualcomm) replies to Josep and provides r07.
Sebastian (QC) replies to Peter
Dieter (Deutsche Telekom) clarifies by providing r08.
Sebastian (QC) provides r09.
Dieter (Deutsche Telekom) comments.
Sebastian (Qualcomm) replies and provides r10
Dieter (Deutsche Telekom) asks question for clarification.
==== Ph1 Revisions Deadline ====
Devaki (Nokia) comments.
Dieter (Deutsche Telekom) replies..
Xiaowan (vivo) replies to Sebastian.
Sebastian (Qualcomm) replies to Dieter
Sebastian (Qualcomm) replies to Devaki and proposes to approve r10.
Dieter (Deutsche Telekom) can only accept r08.
Sebastian (Qualcomm) replies to DT
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004348 P-CR Approval 23.700-07: Addressing open issues for Solution 2. Qualcomm Incorporated, OPPO, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2004332_R08. Approved Approved
8.2 S2-2003725 P-CR Approval 23.700-07: KI#1, Sol#2 Update: Service Provider Identifier in UE configuration data. OPPO Rel-17 Merged into S2-2004332 Merged
8.2 S2-2003884 P-CR Approval 23.700-07: KI#1: New Sol: NF and service discovery between SNPN and separate entity . Huawei, HiSilicon Rel-17 R03 agreed. Revised to S2-2004349 Devaki (Nokia) proposes to Note this paper or at least defer this discussion until the relationship between V-SNPN and H-SNPN are clarified.
Hualin (Huawei) response and rev01 to Devaki(Nokia).
Hualin (Huawei) provide rev02.
Devaki (Nokia) comments.
Hualin (Huawei) provide rev03.
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) ok with r03, but whether solution is needed or not depends on solution(s) to be part of the conclusions of the KI.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004349 P-CR Approval 23.700-07: KI#1: New Sol: NF and service discovery between SNPN and separate entity . Huawei, HiSilicon Rel-17 Revision of S2-2003884_R03. Approved Approved
8.2 - - - Solution to KI#2 - - Docs:=19 -
8.2 S2-2003608 P-CR Approval 23.700-07: KI#2, new solution, policy based control. Ericsson Rel-17 Noted Chia-Lin (MediaTek) proposes to note this pCR
Saso (Intel) comments and proposes to note this pCR
Guanzhou (InterDigital) comments.
Belen (Ericsson) provides clarifications, and a r01.
Peter Hedman (Ericsson) provides comments.
Sebastian (Qualcomm) provides r02.
Hualin (Huawei) ask question on the solution.
Belen (Ericsson) replies to Huawei´s question and accepts QC proposed r01
==== Ph1 Revisions Deadline ====
Chia-Lin (MediaTek) asks more clarification
Sebastian (Qualcomm) replies to Belen.
Sebastian (Qualcomm) prefers r02.
Chia-Lin (MediaTek) objects to this pCR
Belen (Ericsson) replies to MediaTek, disagrees with providing new and late comments and proposes to address them in future meetings.
Saso (Intel) can live with r02 (only).
Belen (Ericsson) corrects previous comment.
Ericsson accepts QC proposed r02
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003607 P-CR Approval 23.700-07: Solution to support service continuity between two networks and paging from both networks. Ericsson Rel-17 R04 agreed. Revised to S2-2004350 Amanda Xiang (Futurewei) provides r01.
Peter Hedman (Ericsson) provides r02
Saso (Intel) comments.
Sebastian (Qualcomm) provides r03.
Hualin (Huawei) provides fundamental comments on the paper.
Dieter (Deutsche Telekom) ask question for clarification.
Peter Hedman (Ericsson) provides r04 and comments.
==== Ph1 Revisions Deadline ====
Sebastian (Qualcomm) ask questions to Peter
Peter Hedman (Ericsson) provides reply to Sebastian.
Sebastian (QC) can live with r04.
Saso (Intel) can live with r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004350 P-CR Approval 23.700-07: Solution to support service continuity between two networks and paging from both networks. Ericsson Rel-17 Revision of S2-2003607_R04. Approved Approved
8.2 S2-2003638 P-CR Approval 23.700-07: KI #2, New Sol: MUSIM-based solution. Intel Rel-17 Noted Amanda Xiang (Futurewei) provides comments.
Devaki (Nokia) has objection to this proposal i.e. we shall avoid changing SID scope for eNPN, MUSIM rather move on based on existing KIs.
Saso (Intel) replies to Nokia and Futurewei and asks a question.
Devaki (Nokia) clarifies Nokia views.
Wanqiang (Huawei) comments and proposes to note the paper (should not extend the MUSIM scope).
Dieter (Deutsche Telekom) objects to this solution. NPN is out of scope of MUSIM.
Saso (Intel) replies to Dieter (Deutsche Telekom) and others.
Peter Hedman (Ericsson) provides comments.
Guillaume (MediaTek) provides comments.
Dieter (Deutsche Telekom) comments.
==== Ph1 Revisions Deadline ====
Saso (Intel) provides comments and proposes to agree r00.
Devaki (Nokia) proposes to bring this up during the Conference call on Friday to decide on the way forward.
Peter Hedman (Ericsson) provides questions, and agree that it is suitable as a topic for Friday Conference call
Saso (Intel) replies to Peter Hedman (Ericsson) and Devaki (Nokia) that it is OK to take this topic for Friday Conference call
Steve (Huawei) Objects to extending the MUSIM scope, discussion on Friday is fine.
Dieter (Deutsche Telekom) still this needs to be based on service requirements.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003677 P-CR Approval 23.700-07: KI#2, New Sol: Always in CM Connected state in the two networks. Sony Rel-17 R01 agreed. Revised to S2-2004351 Sebastian (Qualcomm) provides comments and r01
Marco (Huawei) provides comments to r01
Lars (Sony) provides comments to r01 and suggest go with original version
==== Ph1 Revisions Deadline ====
Sebastian (Qualcomm) replies to marco.
Sebastian (Qualcomm) replies and *objects* to r00
Lars (Sony) can accept r01
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004351 P-CR Approval 23.700-07: KI#2, New Sol: Always in CM Connected state in the two networks. Sony Rel-17 Revision of S2-2003677_R01. Approved Approved
8.2 S2-2003835 P-CR Approval 23.700-07: KI #2, New Sol: Simultaneous communication using N3IWF. LG Electronics, LG Uplus Rel-17 Noted Guanzhou (InterDigital) comments and proposes to note this.
Qianghua (Huawei) provides comments.
Myungjune (LGE) provides response to InterDigital and Huawei.
Guanzhou (InterDigital) comments on Myungjune (LGE)'s responses.
Myungjune (LGE) replies to Guanzhou (InterDigital).
Saso (Intel) comments.
Myungjune (LGE) provides r01.
Guanzhou(InterDigital) objects to this PCR and its revision r01.
==== Ph1 Revisions Deadline ====
Myungjune (LGE) asks Guanzhou (InterDigital­) to clarify objection.
Guanzhou (InterDigital­) clarifies the objection.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004057 P-CR Approval 23.700-07: KI #2: Update to KI#2 to clarify the service continuity and simultaneous reception on data services and paging. MediaTek Inc. Rel-17 R02 agreed. Revised to S2-2004352 Amanda Xiang (Futurewei) provide comments
Devaki (Nokia) asks question for clarification.
Chia-Lin (MediaTek) responds to Nokia and FutureWei.
Saso (Intel) comments.
Zhenhua (vivo) comments.
Marco (Huawei) propose to note the pCR. Are proposed Notes saying that nothing is needed ?
Marco (Huawei) responds
Saso (Intel) replies
Kisuk (Samsung) provides comments.
Chia-Lin (MediaTek) provides r02
Marco (Huawei) provides a revision 04.
Chia-Lin (MediaTek) responds to Huawei
==== Ph1 Revisions Deadline ====
Devaki (Nokia) proposes to go with r02 (although it is radically different from original paper).
Intel (Saso) is OK with r02. Can also accept r01.
Marco (Huawei) we can accept only r04 or r02
Sebastian (Qualcomm) can live with r02
Peter Hedman (Ericsson) ok with r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004352 P-CR Approval 23.700-07: KI #2: Update to KI#2 to clarify the service continuity and simultaneous reception on data services and paging. MediaTek Inc. Rel-17 Revision of S2-2004057_R02. Approved Approved
8.2 S2-2004064 P-CR Approval 23.700-07: KI #2, New Sol: Service Continuity between PNI-NPN and PLMN . Tencent Rel-17 R03 agreed. Revised to S2-2004353 Zhenhua (vivo) comments
Lei (Tencent) provide response and r01 to address the comments.
zhendong(ZTE) provide comments.
Lei(Tencent) responds to Zhendong(ZTE).
Zhenhua (vivo) replies to Zhendong (ZTE).
Chia-Lin (MediaTek) proposes to note the pCR.
Zhenhua (vivo) provide r02.
Lei (Tencent): Thanks and accept r02. Also respond to ZTE and MTK.
Sebastian (Qualcomm) provides r03
Lei (Tencent): Respond to Sebastian(QC) and provide comments to r03.
Lei(Tencent) provide comments.
==== Ph1 Revisions Deadline ====
Sebastian (QC) can only accept r03
zhendong (ZTE) is also fine with r03
Lei(Tencent) double confirm can live with r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004353 P-CR Approval 23.700-07: KI #2, New Sol: Service Continuity between PNI-NPN and PLMN . Tencent Rel-17 Revision of S2-2004064_R03. Approved Approved
8.2 S2-2004111 P-CR Approval 23.700-07: KI #2, New Sol: Data notification for SNPN/PLMN support VIAPA. Vivo Rel-17 R04 agreed. Revised to S2-2004354 Lars Nord (Sony) Comment and asks for clarifications
zhendong (ZTE) provides comments and questions
Josep (DT) comments and proposes to note this pCR
Saso (Intel) comments and proposes to note this pCR
Zhenhua (vivo) provide r01
Zhenhua (vivo) response
Zhenhua (vivo) response to Zhendong
Zhenhua (vivo) response to Saso
Saso (intel) replies to Zhenhua (vivo)
Zhenhua (vivo) replies to Saso (Intel)
Zhenhua (vivo) provide r02 and replies to Saso (Intel)
Sebastian (QC) comments and provides r03
Marco (Huawe) question on relationship with RFC IKEv2 security
Zhenhua (vivo) replies to Marco (Huawe)
Marco (Huawei) replies to back.
Zhenhua (vivo) replies Marco (Huawei).
Zhenhua (vivo) provide r04.
==== Ph1 Revisions Deadline ====
Saso (Intel) thinks this proposal cannot work without IKEv2 changes, but can live with r04.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004354 P-CR Approval 23.700-07: KI #2, New Sol: Data notification for SNPN/PLMN support VIAPA. Vivo Rel-17 Revision of S2-2004111_R04. Approved Approved
8.2 S2-2004141 P-CR Approval 23.700-07: KI#2, New Sol: Solution for prioritization from PLMN to SNPN. Nokia, Nokia Shanghai Bell Rel-17 Noted Zhenhua (vivo) comment for clarification.
Saso (Intel) asks clarification.
Devaki (Nokia) responds to the comments.
Saso (Intel) follows up on Nokia's comments.
Hualin (Huawei) feel the paper is not correct and ask question for understanding.
Devaki (Nokia) responds to HUA, Intel questions.
Saso (Intel) proposes this pCR to be noted as it lacks description of solution details.
Devaki (Nokia) respectfully disagrees with Intel that it lacks solution details. It has in fact been explained what exactly the normative spec change will be as a result of this solution.
Hualin(Huawei) response to Devaki (Nokia).
Josep (DT) comments and provides r02
Peter Hedman (Ericsson) Ericsson has fundamental concerns with the paper.
Devaki (Nokia) responds to E/// comments.
Peter Hedman (Ericsson) provides r03
Amanda Xiang (Futurewei) provides revision r01 which merge partial content from S2-2004235
==== Ph1 Revisions Deadline ====
Saso (Intel) objects to any revision of this pCR because the solution lacks details.
Respectfully disagrees with Intel comment that it lacks solution details. Devaki (Nokia) requests Intel to consider r03 for approval still and proposes that evolve this in the future meeting to address further open questions.
Saso (Intel) sustains objection to any revision and replies to Devaki (Nokia).
Devaki (Nokia) responds to Saso.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004175 P-CR Approval 23.700-07: Solution for KI#2: Enabling service continuity with pre-established backup connection. InterDigital Inc. Rel-17 Noted Zhenhua (vivo) comments for clarification
Saso (Intel) provides questions and comments.
Devaki (Nokia) asks question for clarification.
Guanzhou (InterDigital) responds to Saso (Intel) and Zhenhua (Vivo)'s comments.
Guanzhou (InterDigital) responds to Devaki (Nokia)'s question.
Marco (Huawei) comment on MA PDU session usage.
Guanzhou (InterDigital) responds to Marco (Huawei)'s question.
Chia-Lin (MediaTek) comments
Hualin (Huawei) provide comment to Guanzhou(Interdigital)
Guanzhou(Interdigital) responds to HW and MediaTek comments and provides revision 01.
Hualin(Huawei) provides revision 02. We can't accept r01 and the previous version.
==== Ph1 Revisions Deadline ====
Chia-Lin (MediaTek) cannot accept r02.
==== Ph1 Final Deadline ====.
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004208 P-CR Approval 23.700-07: Support for eMBMS with 5GS independent unicast KI#2. Qualcomm Incorporated Rel-17 Noted Josep (DT) comments and proposes to note this pCR.
Haris (Qualcomm) comments
Saso (Intel) comments
Devaki (Nokia) asks question for clarification.
Marco (Huawei) object to this pCR and propose to note.
Haris (Qualcomm) provides answers
Saso (Intel) follows up with a comment
Xiaobo Yu (Alibaba) provides comments and asks for the pCR to be noted since the proposed solution is based on 4G and is out of scope of TR23.700-07.
Shabnam (Ericsson) supports the proposal and provides r01.
Marco (Huawei) confirm the concern that is not changed by R01.
Saso (Intel) provides r02.
Marco (Huawei) provides comment.
Wanqiang (Huawei) objects the original version and following revisions.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004235 P-CR Approval 23.700-07: KI #2, New Sol: simultaneous connection with NPN and PLMN with QoS consideration for VIAPA. Futurewei, Sennheiser, Philips Rel-17 R06 agreed. Revised to S2-2004355 Dieter (Deutsche Telekom) objects to this solution.
Amanda Xiang (Futurewei) response to LGE comments with new revision r05 .
Chia-Lin (MediaTek) asks the questions for clarification.
Saso (Intel) asks clarification.
Peter Hedman (Ericsson) Ericsson has fundamental concerns with the paper.
Peter Hedman (Ericsson) withdraw previous comments as was to wrong document (should have been to S2-2004141).
Amanda Xiang (Futurewei) response to the questions from Saso and Chia-Lin, also provides revision r06
Walter Dees (Philips) responds to the comments from DT, Intel and LGE, and provide a new revision r04
Amanda Xiang (Futurewei) response to the objection from Deutsche Telekom
Amanda Xiang (Futurewei) response to the comments from Intel and DT, and provide a new revision r03
Amanda Xiang (Futurewei) provides answers for the questions from LGE and Nokia in line, also provide revision R02 to address those comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004355 P-CR Approval 23.700-07: KI #2, New Sol: simultaneous connection with NPN and PLMN with QoS consideration for VIAPA. Futurewei, Sennheiser, Philips Rel-17 Revision of S2-2004235_R06. Approved Approved
8.2 S2-2004253 P-CR Approval 23.700-07: KI #2, New Sol: Paging in one network for another network. Samsung Rel-17 Noted Josep (DT) provides comments.
Sebastian (Qualcomm) provides r01
==== Ph1 Revisions Deadline ====
Kisuk (Samsung) replies Qualcomm.
Kisuk (Samsung) replies to DT.
Josep (DT) objects to this pCR and proposes the author to re-submit a complete version next meeting.
Kisuk (Samsung) provides comments to DT.
Kisuk (Samsung) provides comments.
Sebastian (QC) can only accept r01
Kisuk (Samsung) replies to Qualcomm.
Saso (Intel) would prefer this pCR to be noted, but can live with r01.
Kisuk (Samsung) replies to Intel.
Saso (Intel) replies to Kisuk.
Kisuk (Samsung) is ok with r01 and replies to Saso.
Kisuk (Samsung) replies to Josep.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 - - - Conclusions to KI#2 - - Docs:=1 -
8.2 S2-2004099 P-CR Approval 23.700-07: Conclusion for eNPN about MBS support. Huawei, HiSilicon Rel-17 Noted Zhenhua (vivo) provide r01
Josep (DT) comments and provides r02
Zhenhua (vivo) comments on r02
Haris (Qualcomm) objects to this pCR and any of the revisions
Devaki (Nokia) objects to this CR as it is a pre-mature conclusion proposal.
Hualin (Huawei) provide response to Zhenhua(vivo).
Hualin (Huawei) provide response to Haris(Qualcomm) and Devaki(Nokia).
Zhenhua (vivo) comments to Hualin (Huawei).
Hualin (Huawei) provide rev03.
Devaki (Nokia) responds to HUA.
Hualin (Huawei) responds to Devaki(Nokia).
Zhenhua (vivo) provide r04.
Hualin (Huawei) responds to Zhenhua(vivo) and provide r05.
Hualin (Huawei) response to Zhenhua(vivo).
Hualin (Huawei) response to Zhenhua(vivo) and provide r06.
==== Ph1 Revisions Deadline ====
Devaki (Nokia) objects to any revision of this paper (as we believe this is a pre-mature conclusion) for this meeting.
We are open to re-considering this for future meeting once TR has collected all solutions.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 - - - Solution to KI#3 - - Docs:=17 -
8.2 S2-2003584 P-CR Approval 23.700-07: KI #3, New Sol eSIM based solution for Providing IMS voice and emergency services for SNPN subscribers. Ericsson Rel-17 R02 agreed. Revised to S2-2004437. Haris (Qualcomm) comments and proposes to note this pCR
George (Ericsson) provides a response and does not agree with the proposal.
Haris (Qualcomm) comments and proposes to note this pCR (again)
Chris J (T-Mobile USA) supports this p-CR.
George (Ericsson) provides a response.
Chris J (T-Mobile USA) proposes way forward
Devaki (Nokia) shares the same view as QCOM, comments that this solution is not in scope of any of FS_eNPN Key issues (#3, #4).
George (Ericsson) There is a fixation on the provisioning part. But U can ignore the provisioning part, as we can assume these UE have subscriptions already with the PLMN, and just look at the solution and what it supports in terms of IMS and emergency services. It is wishful thinking that every SNPN wants to own and run an IMS network.
George (Ericsson) provides r01
Antoine (Orange) provides r02.
George (Ericsson) provides r03, and responses to Antoine
==== Ph1 Revisions Deadline ====
Haris (Qualcomm) objects to r03 and all the revisions since all contain this text:
This solution addresses Key Issue #3 ('Support of IMS voice and emergency services for SNPN'). The solution enables SNPN UEs to receive IMS and emergency services through provisioning a USIM profile containing an ISIM using GSMA RSP for that purpose.
And references to GSMA RSP that are out of scope of KI#3 and incorrect.
George (Ericsson) Ericsson provides a response. This is a superficial reason. This procedure is supported and allowed today. There has to be more substance to an objection. This is not a beauty contest.
George (Ericsson)Ericsson provides update to address the concern, see proposed text below and propose to check on CC#2 Friday.
Replace in 6.x.1 this text 'The solution enables SNPN UEs to receive IMS and emergency services through provisioning a USIM profile containing an ISIM using GSMA RSP for that purpose'
With this text 'The solution enables SNPN UEs to receive IMS and emergency services through provisioning a UICC containing an ISIM'
And remove GSMA references.
==== Ph1 Final Deadline ====
Haris (Qualcomm) with the text modification George suggest the pCR is acceptable to Qualcomm
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004437 P-CR Approval 23.700-07: KI #3, New Sol eSIM based solution for Providing IMS voice and emergency services for SNPN subscribers. Ericsson Rel-17 Revision of S2-2003584_R02. Approved Approved
8.2 S2-2003585 P-CR Approval 23.700-07: KI #3, New Sol Providing IMS voice and emergency services for SNPN subscribers reusing access level identifiers and credentials. Ericsson Rel-17 R03 agreed. Revised to S2-2004356 Megha(Intel) asks a question
George (Ericsson) provides a response. Regarding the use of NATs similar considerations as the ones defined in Annex V of TS 33.203 should apply when adapting the use of GIBA to 5G.
Megha(Intel) provides comments
George (Ericsson) provides a response. Actually rethinking this again, and given that the SNPN uses 5G, there is no NAT and as such I propose removing this completely. It does not apply. Would U be OK with that?
Megha(Intel) provides further comments.
George (Ericsson) provides a response. There is nothing to remove. My apology. Basically NAT does not apply./
Megha(Intel) provides r01
Dieter (Deutsche Telekom) provides r02.
George (Ericsson) provides r3 to address NAT comment.
==== Ph1 Revisions Deadline ====
Megha(Intel) can accept r03
Dieter (Deutsche Telekom) is ok with r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004356 P-CR Approval 23.700-07: KI #3, New Sol : Providing IMS voice and emergency services for SNPN subscribers reusing access level identifiers and credentials. Ericsson Rel-17 Revision of S2-2003585_R03. Approved Approved
8.2 S2-2003720 P-CR Approval 23.700-07: Solution for IMS voice and emergency services support in SNPN. Intel, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2000166. R03 agreed. Revised to S2-2004357 Chris J (T-Mobile USA) requests clarification.
Dieter (Deutsche Telekom) asks questions for clarification.
Saso (Intel) replies to Chris (T-Mobile USA).
Saso (Intel) replies to Dieter (Deutsche Telekom).
Dieter (Deutsche Telekom) replies to Saso (Intel).
Peter Hedman (Ericsson) replies to Dieter.
Dieter (Deutsche Telekom) comments.
Dieter (Deutsche Telekom) comments/questions.
George (Ericsson) provied comments.
Dieter (Deutsche Telekom) revision r01.
Chris J (T-Mobile USA) replies to Dieter/Saso.
Chris J (T-Mobile USA) replies to Intel's answers to T-Mobile's questions
Chris J (T-Mobile USA) follows up previous comments after further re-reading.
Peter Hedman (Ericsson) provides comments.
Saso (Intel) replies to Dieter (DT) and provides r02.
Saso (Intel) seeks clarification from Chris J (T-Mobile USA)
Chris J (T-Mobile USA) requests solution title change
Chris J (T-Mobile USA) Ask for clarification on absence of USIM for SNPN.
Saso (Intel) replies to Chris J (T-Mobile USA) and provides r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004357 P-CR Approval 23.700-07: Solution for IMS voice and emergency services support in SNPN. Intel, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003720_R03. Approved Approved
8.2 S2-2003840 P-CR Approval 23.700-07: KI #3, New Sol: SNPN IMS Access with PLMN support. Apple Rel-17 Noted George (Ericsson) provides comments and questions.
Haris (Qualcomm) provides comments and proposes to note the pCR
Chris J(T-Mobile) provides comments and questions.
Devaki (Nokia) asks questions for clarification.
Huawei (Susan) provides comments.
Dieter (Deutsche Telekom) proposes to note this solution.
Krisztian (Apple) responds to all comments and provides r01.
Krisztian (Apple) comments.
Krisztian (Apple) responds to Haris.
George (Ericsson) has additional comments.
Krisztian (Apple) provides r02 to address George's comments.
George (Ericsson) asks additional question. Are the 2 IMS clients independents and is only one used at a time, or is there a single IMS client only used. Dual registration implies 2 clients. Not clear. These aspects are vague. Assume they are buried in the relay. We need some EN to keep that opened. Please add something related to IMS clients and operation of relay mode of PBX.
Haris (Qualcomm) indicates the solution is out of scope of the study and should be noted
Krisztian (Apple) provides r03 to address George's comments.
George (Ericsson) Ericsson has one more question Are there 2 IMS clients or one.
==== Ph1 Revisions Deadline ====
Krisztian (Apple) responds to George: it is marked as FFS.
Haris (Qualcomm) objects to r03 and all previous revisions since the solution is addressing a problem that is not part of service requirements and not in scope of KI#3
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003951 P-CR Approval 23.700-07: KI#3, New Sol - extend the IMS voice and emergency service to SNPN. ZTE Rel-17 R02 agreed. Revised to S2-2004358 Haris (Qualcomm) provides comments and proposes to merge this pCR in S2-2004200
Chris J (T-Mobile USA) agrees this pCR should merge into S2-2004200
Zhendong (ZTE) provides response
Dieter (Deutsche Telekom) prefers this solution to be merged into other documents as it is very incomplete. In case it is not merged here is r01.
Zhendong (ZTE) provides response and r02
==== Ph1 Revisions Deadline ====
Haris (Qualcomm) indicates that is ok with r02
Dieter (Deutsche Telekom) can accept r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004358 P-CR Approval 23.700-07: KI#3, New Sol - extend the IMS voice to SNPN. ZTE Rel-17 Revision of S2-2003951_R02. Approved Approved
8.2 S2-2004200 P-CR Approval 23.700-07: Support for emergency services in SNPN. Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 R04 agreed. Revised to S2-2004359 Dieter (Deutsche Telekom) comments.
Megha(Intel) provides r01
Dieter (Deutsche Telekom) provides r02.
Haris (Qualcomm) comments and provides r03
Dieter (Deutsche Telekom) replies to Haris (Qualcomm) .
zhendong (ZTE) provides r04
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004359 P-CR Approval 23.700-07: Support for emergency services in SNPN. Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, ZTE Rel-17 Revision of S2-2004200_R04. Approved Approved
8.2 S2-2004213 P-CR Approval 23.700-07: No IMS roaming interface for SNPN. Charter Communications Rel-17 R01 agreed. Revised to S2-2004360 George (Ericsson) provides comments and questions.
Curt (Charter) provides response to George (Ericsson).
Chris J (T-Mobile USA) seeks clarification and solution update
George (Ericsson) provides additional comments
Dieter (Deutsche Telekom) comments.
Curt (Charter) provides response to George (Ericsson) and Chris (T-Mobile).
Curt (Charter) provides response to Dieter (Deutsche Telekom).
Dieter (Deutsche Telekom) provides response to Curt (Charter).
George (Ericsson) provides additional comment.
George (Ericsson) provides a comment to Curt.
Curt (Charter) provides response...
George (Ericsson) provides a response..
Dieter (Deutsche Telekom) objects to this solution.
Curt (Charter) provides response...and seeking understanding from Dieter
George (Ericsson) seeks clarification. So service level agreement basically would be in extreme case allows a PLMN to provide full service to an SNPN equivalent to roaming today between 2 PLMNs. SNPN UEs must have PLMN subscription. Whether they have 5GC subscription is out of scope. Is this a fair summary.
Curt (Charter) provides R01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004360 P-CR Approval 23.700-07: No IMS roaming interface for SNPN. Charter Communications Rel-17 Revision of S2-2004213_R01. Approved Approved
8.2 S2-2004217 P-CR Approval 23.700-07: IMS emergency call support for SNPN without IMS roaming interface. Charter Communications Rel-17 R03 agreed. Revised to S2-2004361 George (Ericsson) provides comments.
Curt (Charter) provides comments and asks a question.
Chris J (T-Mobile USA) asks for clarification on assumptions
Curt (Charter) provides responses to Chris (T-Mobile USA)
Dieter (Deutsche Telekom) comments/asks questions for clarification.
Curt (Charter) provides response to Dieter (Deutsche Telekom).
Dieter (Deutsche Telekom) provides response to Curt (Charter).
Dieter (Deutsche Telekom) provides r01.
Curt (Charter) provides R02
Dieter (Deutsche Telekom) provides r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004361 P-CR Approval 23.700-07: IMS emergency call support for SNPN without IMS roaming interface. Charter Communications Rel-17 Revision of S2-2004217_R03. Approved Approved
8.2 S2-2004238 P-CR Approval 23.700-07: KI #3: New solution: PLMN assisted IMS voice service for SNPN. China Mobile Rel-17 R01 agreed. Revised to S2-2004362 George (Ericsson) provides comments.
Chris J(T-Mobile USA) provides comments.
Yi Jiang (China Mobile) responds to comments from George and Chris and provides revision 01.
zhendong (ZTE) provides comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004362 P-CR Approval 23.700-07: KI #3: New solution: PLMN assisted IMS voice service for SNPN. China Mobile Rel-17 Revision of S2-2004238_R01. Approved Approved
8.2 - - - KI#4 Update - - Docs:=2 -
8.2 S2-2004205 P-CR Approval 23.700-07: Compartmentalise key issue #4. Qualcomm Incorporated Rel-17 R14 agreed. Revised, merging S2-2004287, to S2-2004363 Josep (DT) comments and provides r01
Haris (Qualcomm) comments and provides r02
Marco (Huawei) comments to r02
Antoine (Orange): provides r03.
Haris (Qualcomm) ok with r03 and asks whether S2-2004287 can be marked as merged
Peter Hedman (Ericsson) provide comments.
Haris (Qualcomm) provide answers to the questions
Antoine (Orange): replies to Qualcomm and Ericsson.
Peter Hedman (Ericsson) provides reply to Antoine.
Peter Hedman (Ericsson) provides answers to Haris.
Haris (Qualcomm) provides revision r04 along the lines of the comments
Antoine (Orange): provides r05.
Xiaobo Yu (Alibaba) provides comment that the proposed compartmentalize is not necessary.
Josep (DT): provides r06.
Haris (Qualcomm) proposes r07
Dieter (Deutsche Telekom): provides r08 (on top of r07)
Josep (DT) comments on Xiaobo Yu's (Alibaba) comment.
Haris (Qualcomm) provides comment that the proposed pCR is very much necessary if we want to ever conclude this KI
Antoine (Orange) provides r09 to replace secondary authentication by NSSAA.
Dan Wang (China Mobile) provides r10 to add the 'and/or secondary authentication for PDU sessions'.
Jianning (Lenovo): provides r11.
Dieter (Deutsche Telekom) provides answer to Jianning (Lenovo).
Peter Hedman (Ericsson) provides r12.
Walter Dees (Philips) provides r13.
Dieter (Deutsche Telekom) supports r12 and would like to co-sign.
Dieter (Deutsche Telekom) comments and objects to r13.
Walter (Philips) comments to Deutsche Telekom.
Dieter (Deutsche Telekom) comments to Walter (Philips).
==== Ph1 Revisions Deadline ====
Walter (Philips) responds to Deutsche Telekom.
Antoine (Orange) replies that there is no ambiguity on '3GPP credentials', objects to r13 and supports r12.
Haris (Qualcomm) supports r12 and indicates that r13 creates ambiguity
Walter (Philips) proposes to add definition of term 3GPP credentials to section 3.1 of the study, since r12 also creates ambiguity.
Josep (DT) also supports r12 and co-signs.
Walter (Philips) responds to Josep (DT).
Walter (Philips) objects to r05 until r12, unless an explicit statement that the term 3GPP credentials only applies to PLMNs and not SNPNs is added either in the document or agreed in the minutes/reflector. Agrees with r04.
Antoine (Orange) objects to r00 to r04 unless S2-2004287 can be approved in complement.
Megha(Intel) supports r12.
Peter Hedman (Ericsson) suggests to agree r12, and note in the MoM the agreement that restriction for 3GPP credentials only applies to PLMNs and not SNPNs, and that will be clarified at the next meeting.
Dieter (Deutsche Telekom) comments. This is not correct, please look into 22.261.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004363 P-CR Approval 23.700-07: Compartmentalise key issue #4. Qualcomm Incorporated, Orange, Ericsson, Deutsche Telekom Rel-17 Revision of S2-2004205_R14, merging S2-2004287. Approved Approved
8.2 - - - Solution to KI#4 - - Docs:=59 -
8.2 S2-2003609 P-CR Approval 23.700-07: KI#4, New Sol: General Onboarding procedure supporting both User and Control Plane UE Provisioning Procedures. Ericsson Rel-17 R06 agreed. Revised, merging S2-2003610, to S2-2004364 Haris (Qualcomm) provides r01
Josep (DT) asks question for clarification
Guanzhou (InterDigital) provided comments.
Qianghua (Huawei) provides comments.
Amanda Xiang (Futurewei) provides questions and comments.
Josep (DT) provides comments.
Peter Hedman (Ericsson) provides comments and accepts r01.
Josep (DT) comments and provides r02
Peter Hedman (Ericsson) provides r03 and replies to Josep, Qianghua and Guanzhou.
Genadi (Motorola Mobility) provides comments/questions.
Devaki (Nokia) proposes to update an existing solution rather than documenting as a new solution.
Peter Hedman (Ericsson) provides r04 and comments.
Devaki (Nokia) has fundamental concerns with the approach as it does not explain how to reach the SNPN during onboarding procedure.
Peter Hedman (Ericsson) provides reply to Devaki.
Qianghua (Huawei) provides comments and r05.
Genadi (Motorola Mobility) answers comments from Ericsson/Peter and provide r06.
==== Ph1 Revisions Deadline ====
Josep (DT) can only live with r06 (objects to other revisions).
Peter Hedman (Ericsson) ok with r06.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004364 P-CR Approval 23.700-07: KI#4, New Sol: General Onboarding procedure supporting both User and Control Plane UE Provisioning Procedures. Ericsson Rel-17 Revision of S2-2003609_R06, merging S2-2003610. Approved Approved
8.2 S2-2003610 P-CR Approval 23.700-07: KI#4, New Sol: Simplified Onboarding procedure supporting both User and Control Plane UE Provisioning Procedures. Ericsson Rel-17 Merged into S2-2004364 Guanzhou (InterDigital) asked questions for clarification
Devaki (Nokia) shares similar views as Interdigital. Proposes that this paper shall be merged with S2-2003609 or noted. The only difference seems to be SA3 aspect (Unique UE shared secret (shared key))...
==== Ph1 Revisions Deadline ====
Josep (DT) requests clarification on whether this pCR is merged with S2-2003609 or not.
Peter Hedman (Ericsson) provides comments.
Guanzhou (InterDigital) would like to see this merged into 3609 and otherwise would object to this PCR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2003611 P-CR Approval 23.700-07: KI#4, new solution, RAN impacts due to KI#4. Ericsson Rel-17 Noted Mike (Convida Wireless) objects to the original version and provides r01.
Antoine (Orange) objects to r00 and r01.
Devaki (Nokia) proposes a way forward: document this under impact section (RAN impacts) for solution 5. Requests author to provide a revision as solution 5 update with RAN impacts.
Peter Hedman (Ericsson) provides r02
Dieter (Deutsche Telekom) comments.
Peter Hedman (Ericsson) provides r03
==== Ph1 Revisions Deadline ====
Josep (DT) objects to this pCR (this is not a solution for KI#4) but would have supported Nokia's way forward.
Antoine (Orange) also objects to this all revisions of pCR (this is not a solution for KI#4) but would have supported Nokia's way forward.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003612 P-CR Approval 23.700-07: KI#4, new solution, Onboarding of NPN in a PLMN subscription. Ericsson Rel-17 Approved Devaki (Nokia) proposes to note this paper as onboarding slice specific credentials are not in scope of this work item. In fact, it may not be in scope of 3GPP even as this is application specific.
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and propose to go with original version as it is in scope as per SA1 LS.
Haris (Qualcomm) indicates that as per response of SA1 S1-202266 provisioning for NSSAA credentials is in scope of service requirements and there are several other pCR updating the KI#4 and solutions for this topic in this meeting proposing
Devaki (Nokia) clarifies Nokia position.
Peter Hedman (Ericsson) provides reply to Devaki.
Haris (Qualcomm) provides reply to Devaki
Devaki (Nokia) can withdraw objection, ok to discuss post SA2#139E consideration related solutions and KI update.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.2 S2-2003639 P-CR Approval 23.700-07: KI #4, Sol #5: Update to remove ENs on O-SNPN-level authentication. Intel, Cisco Systems Rel-17 R05 agreed. Revised to S2-2004365 Haris (Qualcomm) comments and ask question
marco (Huawei) makes questions/comments for clarification and welcomes a revision from the author for addressing them.
Megha(Intel) provides clarification.
Mike (Convida Wireless) asks a question.
Haris (Qualcomm) proposes author drafts revision that allows the option of bypassing primary authentication but not as only option in this solution
Marco (Huawei) proposes author to consider in revision also clarification text related to email exchange
Megha(Intel) provides r01.
Antoine (Orange) requests some updates but cannot provide a revision because the figures are not editable.
Megha(Intel) provides r02.
Haris (Qualcomm) provides r03
Megha(Intel) asks for clarification.
Megha(Intel) provides r04.
Megha(Intel) provides r05.
Haris (Qualcomm) clarifies the issue he sees with the figure in all revisions except r03
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004365 P-CR Approval 23.700-07: KI #4, Sol #5: Update to remove ENs on O-SNPN-level authentication. Intel, Cisco Systems, Samsung Rel-17 Revision of S2-2003639_R05. Approved Approved
8.2 S2-2003726 P-CR Approval 23.700-07: KI#4, New Solution: Onboarding and remote provisioning for PNI-NPN UE. OPPO, China Telecom Rel-17 Revised, merging S2-2003845, to S2-2004325 Revised
8.2 S2-2004325 P-CR Approval 23.700-07: KI#4, New Solution: Onboarding and remote provisioning for PNI-NPN UE. OPPO, China Telecom, Huawei, HiSilicon Rel-17 Revision of S2-2003726, merging S2-2003845. Merged into S2-2004371 Chen (OPPO) indicates merge of S2-2004325 to the revision of S2-2004028
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2003845 P-CR Approval 23.700-07: KI #4, New Sol: Solution for UE Onboarding and remote provisioning for a PNI-NPN. China Telecom, Huawei, HiSilicon Rel-17 Merged into S2-2004325 Merged
8.2 S2-2003773 P-CR Approval 23.700-07: KI #4, New Sol: Network Discovery for Onboarding. Convida Wireless LLC Rel-17 R08 agreed. Revised to S2-2004366 George (Ericsson) provides comments and questions.
Mike (Convida Wireless) provides answers.
George (Ericsson) provides more comments.
Mike (Convida Wireless) replies.
George (Ericsson) request additional clarification.
Mike (Convida Wireless) replies and provides r01.
Hualin (Huawei) ask question on this solution.
Chen (OPPO) provides r02 and comments and seek other clarifications.
Mike (Convida Wireless) provides r03 and replies to Chen (OPPO) and Hualin (Huawei).
Irfan (Cisco) This is covered by Solution #5 and #6.
Mike (Convida Wireless) responds to Ifran (Cisco) and provides rev04
Haris (Qualcomm) comments on the solution and identifies gaps and issues that need to be clarified
Mike (Convida Wireless) replies to Haris (Qualcomm) and provides clarifications in r05.
Josep (DT) comments and asks questions for clarification.
Mike (Convida Wireless) replies to Josep (DT) and provides rev06.
Hualin (Huawei) provides rev07.
Mike Convida Wireless replies and provides rev08.
==== Ph1 Revisions Deadline ====
Haris (Qualcomm) indicates that can accept r08 to be documented in TR 23.700-07 but for the record Qualcomm disagrees with this text: The benefit of the temporary Network Identifier/Network readable name for Onboarding is that, compared to a network that only broadcasts a single 'Onboarding Supported' indication, it minimizes the chances that a UE will attempt to onboard with the wrong network and that a UE will be tricked to attempt to onboard with a rouge network that broadcasts a single 'Onboarding Supported' indication.

Since a SIB indicator without any form of protection and without authentication cannot be adequate measure to avoid false BS attack. SA3 needs to evaluate whether there is a need for such solution for NPN onboarding.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004366 P-CR Approval 23.700-07: KI #4, New Sol: Network Discovery for Onboarding. Convida Wireless LLC Rel-17 Revision of S2-2003773_R08. Approved Approved
8.2 S2-2003807 P-CR Approval 23.700-07: KI #4, Sol #5: Update to remove ENs on DCS and PS. Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 R04 agreed. Revised, merging S2-2003953, to S2-2004367 Qianghua (Huawei) provides r01
Amanda Xiang (Futurewei): provides comments
Megha(Intel) provides clarification.
Amanda Xiang (Futurewei) response to Megha's clarification
Mike (Convida Wireless) asks a question
youngkyo (Samsung) support Megha's view on registration following De-registration.
Mike (Convida Wireless) provides rev02.
Xiaowan (vivo) provides r03 and comments
Megha(Intel) provides r04.
==== Ph1 Revisions Deadline ====
Jianning (Lenovo) provides questions for clarification.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004367 P-CR Approval 23.700-07: KI #4, Sol #5: Update to remove ENs on DCS and PS. Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Samsung Rel-17 Revision of S2-2003807_R04, merging S2-2003953. Approved Approved
8.2 S2-2003830 P-CR Approval 23.700-07: KI#4, Sol#5: update to clarify the DCS related . Vivo Rel-17 Noted Qianghua (Huawei) provides comments.
Haris (Qualcomm) provides comments and indicates that pCR should be noted since before defining the onboarding architecture will be waste of time to spend time on identities
Josep (DT) comments.
Megha(Intel) proposes to note the pCR.
Xiaowan (vivo) replies to the comments
Xiaowan (vivo) clarifies the DCS owner types has been merged into S2-2003807r03
==== Ph1 Revisions Deadline ====
Josep (DT) objects to this pCR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003902 P-CR Approval 23.700-07: KI#4, Solution #5: update on UE onboarding and remote provisioning UP solution. Samsung Rel-17 R02 agreed. Revised to S2-2004368 Haris (Qualcomm) provides comments and provides r01
George (Ericsson) provides comments
Megha(Intel) provides comments/questions for clarification.
Youngkyo (Samsung) provides reply to the comment.
Josep (DT) asks questions for clarification.
Youngkyo(Samsung) answer to the questions.
Youngkyo(Samsung) provide the revision r02.
==== Ph1 Revisions Deadline ====
Antoine (Orange) warns about a clash and suggests approving without update to Figure 6.5s.3-1.
Megha(Intel) ok with r02 and suggests approving without update to Figure 6.5.3-1.
==== Ph1 Final Deadline ====
Chen (OPPO) ok that r02 gets revised S2-2004368 and approved, but the Office Word comments has to be removed.
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004368 P-CR Approval 23.700-07: KI#4, Solution #5: update on UE onboarding and remote provisioning UP solution. Samsung Rel-17 Revision of S2-2003902_R02. Approved Approved
8.2 S2-2003903 P-CR Approval 23.700-07: KI#4, new Solution: UE onboarding via control plane. Samsung Rel-17 R02 agreed. Revised to S2-2004369 Qianghua (Huawei) provides comments
Youngkyo (Samsung) provides answers to the questions and its revision r01.
Qianghua (Huawei) provides comments.
Youngkyo (Samsung) provides revision r02 according to Qianghua's comment.
Josep (DT) provides comments.
==== Ph1 Revisions Deadline ====
Youngkyo (Samsung) provides reply to the comments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004369 P-CR Approval 23.700-07: KI#4, new Solution: UE onboarding via control plane. Samsung, Huawei, HiSilicon Rel-17 Revision of S2-2003903_R02. Approved Approved
8.2 S2-2003904 P-CR Approval 23.700-07: KI#4, new Solution: SNPN subscription provisioning via PLMN. Samsung Rel-17 Merged into S2-2004373 Hualin (Huawei) propose to merge this paper to S2-2004096.
Youngkyo (Samsung) is okay to merge this paper to the revision of S2-2004096.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2003952 P-CR Approval 23.700-07: KI#4, new sol, discussion on the AS or non-AS solution for the UP UE Onboarding. ZTE Rel-17 Noted Haris (Qualcomm) comments and proposes to note this pCR
George (Ericsson) objects to this pCR.
Megha(Intel) provides comments/questions and propose to note the pCR.
zhendong (ZTE) provides the response
Haris (Qualcomm) provides comments
zhendong (ZTE) provides comments
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2003953 P-CR Approval 23.700-07: KI#4, sol#5,6, update to clarify the DCS ownership. ZTE Rel-17 Merged into S2-2004367 Qianghua (Huawei) provides comments.
Guanzhou (InterDigital) provides comments.
Megha(Intel) provides comments
zhendong (ZTE) provides comments.
==== Ph1 Revisions Deadline ====
Josep (DT) remarks this pCR should be marked 'merged into 3807' in the chairman's notes as per the last comment from Zhendong (ZTE).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2003995 P-CR Approval 23.700-07: KI #4, New Sol: UE onboarding and provisioning for SNPN subscription. Huawei, HiSilicon Rel-17 R03 agreed. Revised to S2-2004370 Haris (Qualcomm) asks questions for the solution
Qianghua (Huawei) provides responses.
Genadi (Motorola Mobility) provides comments/questions.
Josep (DT) provides comments.
Qianghua (Huawei) provides responses and r01.
Josep (DT) replies to Quanghua (Huawei) and provides r02.
Qianghua (Huawei) provides responses and r03.
==== Ph1 Revisions Deadline ====
Josep (DT) is OK with r02 or r03 only.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004370 P-CR Approval 23.700-07: KI #4, New Sol: UE onboarding and provisioning for SNPN subscription. Huawei, HiSilicon Rel-17 Revision of S2-2003995_R03. Approved Approved
8.2 S2-2004028 P-CR Approval 23.700-07: KI #4 New solution: UE onboarding for PNI-NPN with Provisioning Server integrated in PLMN. China Mobile Rel-17 R06 agreed. Revised, merging S2-2004325, to S2-2004371 Haris (Qualcomm) comments and provides r01
Chen (OPPO) provides r02 and comments
Haris (Qualcomm) indicates that is ok r02 and asks whether we should consider S2-2004325 merged
Chen (OPPO) indicates the merging of S2-2004325 to revisions of S2-2004028.
OPPO request to be added as co-source of revision of S2-2004028.
Shuyi Tian (China Telecom) request to add China Telecom as co-source of revision of S2-2004028.
Yi Jiang (China Mobile) provides revision v03 of S2-2004028 to add OPPO and China Telecom as cosigner.
Josep (DT) asks some questions for clarification and provides r04.
Yi Jiang (China Mobile) provides revision 05 based on DT comments.
Shuyi Tian (China Telecom) responses to Josep (DT) questions and provides r06.
==== Ph1 Revisions Deadline ====
Josep (DT) is OK with r06 only.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004371 P-CR Approval 23.700-07: KI #4 New solution: UE onboarding for PNI-NPN with Provisioning Server integrated in PLMN. China Mobile, OPPO, China Telecom Rel-17 Revision of S2-2004028_R06, merging S2-2004325. Approved Approved
8.2 S2-2004040 P-CR Approval 23.700-07: KI #4: Update of KI#4 on UE onboarding for IMS related credentials. China Mobile Rel-17 Noted Haris (Qualcomm) comments and objects to this pCR
Megha(Intel) provides comments and proposes to note the pCR.
George (Ericsson) provides a response
Devaki (Nokia) also believes that this solution is not in scope of eNPN. Propose to note the P-CR.
==== Ph1 Revisions Deadline ====
Yi (China Mobile) agree to note the P-CR.
Peter Hedman (Ericsson) provides comments on Nokia claims that provisioning of IMS related credentials is out of scope.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004055 P-CR Approval 23.700-07: KI #4, New Sol: Onboarding of UEs without any credentials. MediaTek Inc. Rel-17 Noted George (Ericsson) provides comments and questions.
Chia-Lin (MediaTek) provides the answers
Youngkyo (Samsung) provides a question.
Chia-Lin (MediaTek) provides the responses and revision r01.
Haris (Qualcomm) comments and proposes solution to be revised (not to be based on UAC) or noted
Devaki (Nokia) asks question for clarification.
Chia-Lin (MediaTek) agreed to note this paper
==== Ph1 Revisions Deadline ====
Noted
8.2 S2-2004056 P-CR Approval 23.700-07: FS_eNPN: KI #4, New Sol: UE Onboarding and remote provisioning based on eSIM. MediaTek Inc. Rel-17 R06 agreed. Revised to S2-2004372 Qianghua (Huawei) provides comments.
Haris (Qualcomm) provides comments.
Josep (DT) provides comments.
Chia-Lin (MediaTek) provides the response to Huawei and Qualcomm.
Haris (Qualcomm) comments and provides r02
Chia-Lin (MediaTek) responds and provides r03
Haris (Qualcomm) objects to r03
Chia-Lin (MediaTek) provides the response to Qualcomm
Haris (Qualcomm) comments to r04
Chia-Lin (MediaTek) responds to Qualcomm
Haris (Qualcomm) provides r05
Chia-Lin (MediaTek) provides r06
Michael (Siemens) comments that UE onboarding in SNPNs with default credentials that are not USIM/eSIM and are independent from PLMNs is the more relevant scenario for verticals (industrial automation)
Walter Dees (Philips) comments on r06
==== Ph1 Revisions Deadline ====
Jianning (Lenovo) provides questions for clarification on r06
Chia-Lin (MediaTek) responds to Lenovo
Chia-Lin (MediaTek) responds to Philips
Walter (Philips) responds to MediaTek
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004372 P-CR Approval 23.700-07: FS_eNPN: KI #4, New Sol: UE Onboarding and remote provisioning based on eSIM. MediaTek Inc., Deutsche Telekom Rel-17 Revision of S2-2004056_R06. Approved Approved
8.2 S2-2004096 P-CR Approval 23.700-07: KI #4, New Sol: PLMN assisted On-boarding Procedures. Huawei, HiSilicon, China Mobile Rel-17 R12 agreed. Revised, merging S2-2003904 and S2-2004192, to S2-2004373 Hualin (Huawei) provides rev01 to S2-2004096.
Youngkyo (Samsung) provides comment and corresponding further rev02 of S2-2004096.
Xiaobo Yu (Alibaba) provides comment and corresponding further rev03 of S2-2004096.
Haris (Qualcomm) asks questions and provides comments
Xiaobo (Alibaba) provides answers and feedback to questions and comments from Haris (Qualcomm)
Haris (Qualcomm) comments further
Hualin (Huawei) provide rev04 and response.
Xiaobo (Alibaba) replies to the questions and comments from Haris (Qualcomm)
Haris (Qualcomm) provides r05
Xiaobo Yu (Alibaba) provides r06
Haris (Qualcomm) comments that there some typos but technically ok w/ r06
Xiaobo Yu (Alibaba) provide r07
Youngkyo(Samsung) provide some comments and request for the further revision
Xiaobo Yu(Alibaba) replies to the comments from Youngkyo(Samsung)
Youngkyo(Samsung) provides further comment on Xiaobo Yu(Alibaba)'s reply
Xiaobo Yu(Alibaba) provide r08 and replies to the comments from Youngkyo(Samsung)
Youngkyo(Samsung) provides further comment and corresponding revision r09.
Hualin(Huawei) provides r10.
Xiaobo Yu(Alibaba) provides r12 and replies to the comments from YoungKyo (Samsung)
Hualin(Huawei) is fine with r12.
==== Ph1 Revisions Deadline ====
Jianning (Lenovo) provide comments.
Xiaobo Yu (Alibaba) replies to the comment from Jianning (Lenovo)
Youngkyo (Samsung) replies to the comment from Jianning (Lenovo)
Hualin(Huawei) replies to the comment from Jianning (Lenovo)
Jianning (Lenovo) further comments for Hualin(Huawei), Xiaobo(Alibaba) and Youngkyo (Samsung)
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004373 P-CR Approval 23.700-07: KI #4, New Sol: PLMN assisted On-boarding Procedures. Huawei, HiSilicon, China Mobile, Samsung, Alibaba Group Rel-17 Revision of S2-2004096_R12, merging S2-2003904 and S2-2004192. Approved Approved
8.2 S2-2004100 P-CR Approval 23.700-07: KI #4, Sol #7: Update the existing solution #7 to clarify the solution and remove several ENs. Huawei, HiSilicon Rel-17 R03 agreed. Revised to S2-2004374 Josep (DT) asks question for clarification
Hualin(Huawei) provide response and rev01 to Josep (DT).
Haris (Qualcomm) comments on r01
Hualin (Huawei) response to Haris (Qualcomm) and provide r02.
Haris (Qualcomm) provides r03
Hualin(Huawei) is fine with r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004374 P-CR Approval 23.700-07: KI #4, Sol #7: Update the existing solution #7 to clarify the solution and remove several ENs. Huawei, HiSilicon Rel-17 Revision of S2-2004100_R03. Approved Approved
8.2 S2-2004101 P-CR Approval 23.700-07: KI #4, New Sol: Solution for On Boarding for SNPN Compatible with SO's Existing Provisioning Server. Huawei, Hisilicon Rel-17 R01 agreed. Revised to S2-2004375 Haris (Qualcomm) indicates support for the solution and provides r01
Hualin(Huawei) thanks to Haris (Qualcomm) and is fine with r01
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and can accept r01.
Hualin (Huawei) response to Peter(Ericsson).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004375 P-CR Approval 23.700-07: KI #4, New Sol: Solution for On Boarding for SNPN Compatible with SO's Existing Provisioning Server. Huawei, Hisilicon Rel-17 Revision of S2-2004101_R01. Approved Approved
8.2 S2-2004142 P-CR Approval 23.700-07: KI#4, Sol #5: Update for Provisioning Server address configuration at SNPN providing onboarding access. Nokia, Nokia Shanghai Bell Rel-17 R02 agreed. Revised to S2-2004376 George (Ericsson) provides comments and questions.
Hualin (Huawei) think the paper is good and provide minor wording correction in rev01 .
Devaki (Nokia) responds to Ericsson, Huawei.
Devaki (Nokia) happy with r01.
George (Ericsson) provides r02 Added EN on URSP conveying PS address.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004376 P-CR Approval 23.700-07: KI#4, Sol #5: Update for Provisioning Server address configuration at SNPN providing onboarding access. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2004142_R02. Approved Approved
8.2 S2-2004143 P-CR Approval 23.700-07: KI#4, New Sol: Solution for providing provisioning details to UE using local provisioning server and central provisioning server. Nokia, Nokia Shanghai Bell Rel-17 R03 agreed. Revised to S2-2004377 XX (Huawei) makes questions/comments for clarification and welcomes a revision from the author for addressing them
George (Ericsson) propose to note the pCR.
Devaki (Nokia) answers Ericsson, Huawei comments and questions.
Devaki (Nokia) also provides r01.
George (Ericsson) requires additional clarification based on Nokias response
Devaki (Nokia) responds to E/// question.
Josep (DT) comments and asks question for clarification.
George (Ericsson) requires additional clarification.
Devaki (Nokia) provides additional answers Ericsson.
Devaki (Nokia) comments that evaluation comment should be reserved for evaluation phase.
George (Ericsson) has additional comment
Devaki (Nokia) responds to the comment.
Devaki (Nokia) provides r03.
==== Ph1 Revisions Deadline ====
Josep (DT) objects to at least r01.
Devaki (Nokia) proposes to go with r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004377 P-CR Approval 23.700-07: KI#4, New Sol: Solution for providing provisioning details to UE using local provisioning server and central provisioning server. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2004143_R03. Approved Approved
8.2 S2-2004147 P-CR Approval 23.700-07: Solution: UE Onboarding and remote Provisioning . Lenovo, Motorola Mobility Rel-17 R01 agreed. Revised to S2-2004378 Josep (DT) asks question for clarification
Marco (Huawei) makes questions/comments for clarification and welcomes a revision from the author for addressing them
Jianning (Lenovo) provides response to questions from Macro (Huawei) and Josep (T-Mobile)
Marco (Huawei) provides further comment and ask to produce a revision addressing clarification
Jianning (Lenovo) provides further replies and revision r01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004378 P-CR Approval 23.700-07: Solution: UE Onboarding and remote Provisioning for SNPN . Lenovo, Motorola Mobility Rel-17 Revision of S2-2004147_R01. Approved Approved
8.2 S2-2004174 P-CR Approval 23.700-07: Update to Solution #5: UE Onboarding and provisioning for an SNPN. InterDigital Inc. Rel-17 R01 agreed. Revised to S2-2004379 Antoine (Orange) objects because there is no requirement was would justify extending this solution to PLMNs.
Guanzhou (InterDigital) comments on Antoine (Orange)'s objection.
Guanzhou (InterDigital) provides r01.
==== Ph1 Revisions Deadline ====
Josep (DT) objects to the original pCR, is OK with r01.
Antoine (Orange) also objects to the original pCR, is OK with r01.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004379 P-CR Approval 23.700-07: Update to Solution #5: UE Onboarding and provisioning for an SNPN. InterDigital Inc. Rel-17 Revision of S2-2004174_R01. Approved Approved
8.2 S2-2004197 P-CR Approval 23.700-07: Closing open issues in Solution 5. Qualcomm Incorporated Rel-17 R01 agreed. Revised to S2-2004380 Josep (DT) comments
Haris (Qualcomm) responds and provides r01
Youngkyo (Samsung) provides some questions
Xiaobo Yu (Alibaba) provides comments and asks for the pCR to be noted since the proposed solution have too much assumption of DCS.
Haris (Qualcomm) responds to the comment and indicates that Alibaba comment should be disregarded
Xiaobo Yu (Alibaba) replies to Haris (Qualcomm)
==== Ph1 Revisions Deadline ====
Josep (DT) can live with r01.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004380 P-CR Approval 23.700-07: Closing open issues in Solution 5. Qualcomm Incorporated Rel-17 Revision of S2-2004197_R01. Approved Approved
8.2 S2-2004215 P-CR Approval 23.700-07: KI #4, New Sol: Re-selection of preferred Onboarding Network. Motorola Mobility, Lenovo Rel-17 Noted George (Ericsson) proposes to note this pCR.
Megha(Intel) provides comments/questions.
Genadi (Motorola Mobility) answers questions from Ericsson/George and Intel/Megha and provides r01.
Haris (Qualcomm) comments and proposes this pCR to be noted
Genadi (Motorola Mobility) answers comments from Qualcomm/Haris.
Haris (Qualcomm) comments further
Genadi (Motorola Mobility) answers further comments from Qualcomm/Haris.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004220 P-CR Approval 23.700-07: KI #4, New Sol: Provisioning for PNI-NPN. Motorola Mobility, Lenovo Rel-17 Approved Megha(Intel) provides comments
Genadi (Motorola Mobility) answers comments from Intel/Megha.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.2 S2-2004254 P-CR Approval 23.700-07: KI #4, Sol #5: Update to clarify discovering and selecting DCS, PS and SNPN owning the subscription. Samsung Rel-17 R03 agreed. Revised to S2-2004381 George (Ericsson) provides comments and questions.
Marco (Huawei) questions for clarification.
Megha(Intel) provides questions/comments.
Kisuk (Samsung) replies Ericsson's comments and questions and provides r01.
Kisuk (Samsung) replies to Huawei
Kisuk(Samsung) replies to Intel.
Josep (DT) comments.
Kisuk (Samsung) replies to DT.
Josep (DT) replies to Kisuk.
Kisuk (Samsung) replies DT and provides r02.
Josep (DT) replies to Kisuk (Samsung).
==== Ph1 Revisions Deadline ====
Josep (DT) can live with r03 only.
Kisuk (Samsung) is ok with r03.
Megha(Intel) can live with r03, but we have concerns with the description. We are ok with the option of DCS assisting PS and SO selection, but this needs to be clearly described as an option, which is not the case in r03.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004381 P-CR Approval 23.700-07: KI #4, Sol #5: Update to clarify discovering and selecting DCS, PS and SNPN owning the subscription. Samsung Rel-17 Revision of S2-2004254_R03. Approved Approved
8.2 S2-2004257 P-CR Approval 23.700-07: KI #4, Sol #5: Update to clarify how the UE discovers and selects the onboarding network. Samsung Rel-17 Noted Josep (DT) comments
Guanzhou (InterDigital) asks questions for clarification.
George (Ericsson) object to the pCR.
Megha(Intel) proposes to note the pCR.
Kisuk (Samsung) comments
Josep (DT) replies to comment
Kisuk (Samsung) replied to InterDigital's questions for clarification.
Kisuk (Samsung) replies to Ericsson
Kisuk(Samsung) replies to Intel.
Kisuk (Samung) replies to comment
Jianning(Lenovo) provides questions for clarification
Kisuk (Samsung) replies to Lenovo.
==== Ph1 Revisions Deadline ====
Josep (DT) objects to this pCR.
Megha(Intel) cannot accept r00.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004259 P-CR Approval 23.700-07: KI #4, Sol #5: Update to clarify the terminologies and the abbreviations. Samsung Rel-17 R03 agreed. Revised to S2-2004382 Marco (Huawei) makes questions/comments for clarification on 'onboarding network' definition
Kisuk (Samsung) provides the revised paper.
Peter Hedman (Ericsson) provides r02.
Peter Hedman (Ericsson) provides r03
Saso (Intel) proposes to either NOTE this pCR.
==== Ph1 Revisions Deadline ====
Kisuk (Samsung) replies to Intel.
Kisuk (Samsung) replies to Ericsson.
Saso (Intel) withdraws comment which was made on wrongly titled thread.
Kisuk (Samsung) provides comment.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004382 P-CR Approval 23.700-07: KI #4, Sol #5: Update to clarify the terminologies and the abbreviations. Samsung, Ericsson Rel-17 Revision of S2-2004259_R03. Approved Approved
8.2 S2-2004287 P-CR Approval 23.700-07: KI #4: Update to KI#4 to clarify credential aspects. Orange, Telecom Italia, MediaTek Inc., AT&T, China Mobile, NTT DOCOMO Rel-17 Revision of S2-2001360. Merged into S2-2004363 Haris(Qualcomm) indicates that this pCR should be marked as merged in S2-2004205 (latest revisions)
Antoine (Orange) agrees to mark this pCR as merged in S2-2004205 if S2-2004205 can be approved.
==== Ph1 Revisions Deadline ====
Walter (Philips) objects to all versions of this document.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.2 S2-2004288 P-CR Approval 23.700-07: KI #4, New Sol: UE onboarding using PLMNs. Orange, MediaTek Inc., Telecom Italia, AT&T, China Mobile Rel-17 R07 agreed. Revised to S2-2004383 Qianghua (Huawei) provides comments.
Haris (Qualcomm) provides comments and highlights issues that need to be documented
Antoine (Orange) replies to Qualcomm and provides r01.
Haris (Qualcomm) indicates and is ok with r01
Megha(Intel) provides r02.
Megha(Intel) provides r03.
Irfan (Cisco) comments
Antoine (Orange) replies to Intel and provides r04.
Haris (Qualcomm) questions the validity of this text: The Provisioning Server pushes the UE's NPN credentials for the SNPN and other configuration information into the UE and the UE stores them in the ME and for this reason indicates that Qualcomm cannot agree with r04
Antoine (Orange) confirms that this text is valid because the credentials are non-AKA credentials that, independently of this solution, are stored in ME.
TenhagenD (HA/AG) questions the proposal for having only _one_ shown process for onboarding using PLMNs in the text:
It should be considered (by the assumptions in the text) that in the explained NPN credentials init process should also allow onboarding UEs through an appropriate (standardized) API -> In example like that one currently developed as GTA 'Generic Trust Anchor' in ISO/IEC JTC1/SC41/WG3 -
This with the - alternative - ability to maintain UEs in this process fully independent to an (outside/external) initially and therefore locally. (Independent from PLMN)
(Furthermore such an API would allow more business models for servitization to the UEs OEMs - as well as for System Integrators -and End Users, and also allows the provisioning of additional and secure elements under the control of -all- these Stakeholders for benefit.
Thank you.

Best regards

Detlef Tenhagen
TenhagenD (HA/AG) questions the proposal for having only _one_ shown process for onboarding using PLMNs in the text:
It should be considered (by the assumptions in the text) that in the explained NPN credentials init process should also allow onboarding UEs through an appropriate (standardized) API -> In example like that one currently developed as GTA 'Generic Trust Anchor' in ISO/IEC JTC1/SC41/WG3 -
This with the - alternative - ability to maintain UEs in this process fully independent to an (outside/external) initially and therefore locally. (Independent from PLMN)
(Furthermore such an API would allow more business models for servitization to the UEs OEMs - as well as for System Integrators -and End Users, and also allows the provisioning of additional and secure elements under the control of -all- these Stakeholders for benefit.
Thank you.

Best regards

Detlef Tenhagen
TenhagenD (HA/AG) questions the proposal for having only _one_ shown process for onboarding using PLMNs in the text:
It should be considered (by the assumptions in the text) that in the explained NPN credentials init process should also allow onboarding UEs through an appropriate (standardized) API -> In example like that one currently developed as GTA 'Generic Trust Anchor' in ISO/IEC JTC1/SC41/WG3 -
This with the - alternative - ability to maintain UEs in this process fully independent to an (outside/external) initially and therefore locally. (Independent from PLMN)
(Furthermore such an API would allow more business models for servitization to the UEs OEMs - as well as for System Integrators -and End Users, and also allows the provisioning of additional and secure elements under the control of -all- these Stakeholders for benefit.
Thank you.

Best regards

Detlef Tenhagen
Ernst (Volkswagen AG) agrees to have PLMN based solutions however we strongly advocate for additional / alternative PLMN independent solutions to enable also our foreseen deployment scenarios of NPN.
Josep (DT) replies to Detlev (HA/AG).
Megha(Intel) provides r05.
Antoine (Orange) replies to Intel and provides r06.
Michael (Siemens) comments that UE onboarding in SNPNs with default credentials that are not USIM and are independent from PLMNs is the more relevant scenario for verticals (industrial automation); concern with step D2
Antoine (Orange) replies to Siemens.
Saso (Intel) shares the concern with Michael (Siemens) about the practicality of this solution for verticals in general, and with the specific concern with step D2 in particular.
==== Ph1 Revisions Deadline ====
TenhagenD (HA/AG) questions the proposal for having only _one_ shown process for onboarding using PLMNs in the text:
It should be considered (by the assumptions in the text) that in the explained NPN credentials init process should also allow onboarding UEs through an appropriate (standardized) API -> In example like that one currently developed as GTA 'Generic Trust Anchor' in ISO/IEC JTC1/SC41/WG3 -
This with the - alternative - ability to maintain UEs in this process fully independent to an (outside/external) initially and therefore locally. (Independent from PLMN)
(Furthermore such an API would allow more business models for servitization to the UEs OEMs - as well as for System Integrators -and End Users, and also allows the provisioning of additional and secure elements under the control of -all- these Stakeholders for benefit.
Thank you.

Best regards

Detlef Tenhagen
Megha(Intel) can accept r07
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004383 P-CR Approval 23.700-07: KI #4, New Sol: UE onboarding using PLMNs. Orange, MediaTek Inc., Telecom Italia, AT&T, China Mobile, Deutsche Telekom, Telenor Rel-17 Revision of S2-2004288_R07. Approved Approved
8.2 S2-2004237 P-CR Approval 23.700-07: Solution for UE onboarding and remote provisioning. Alibaba Group. Rel-17 R06 agreed. Revised to S2-2004384 Marco(Huawei) makes questions/comments for clarification and welcomes a revision from the author for addressing them
Haris (Qualcomm) provides comments and asks for the pCR to be noted since it is incomplete
Genadi (Motorola Mobility) provides comments/questions.
Xiaobo Yu (Alibaba) provides r01 and replies to the comments from Marco (Huawei)
Xiaobo Yu (Alibaba) provides r03 to resolve comments from Qualcomm, Motorola.
Xiaobo Yu (Alibaba) provides r05
Haris (Qualcomm) provides r06
Xiaobo Yu (Alibaba) replies to comments from Haris (Qualcomm)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004384 P-CR Approval 23.700-07: Solution for UE onboarding and remote provisioning. Alibaba Group. Rel-17 Revision of S2-2004237_R06. Approved Approved
8.2 S2-2004240 P-CR Approval 23.700-07: Solution for UE onboarding and remote provisioning using non-3GPP access. Alibaba Group. Rel-17 Noted Marco (Huawei) not in SID scope
George (Ericsson) proposes to note this pCR as there is no support for Non-3GPP access yet. .
Genadi (Motorola Mobility) proposes to note this pCR as the Trusted Non-3GPP access was excluded from the Rel-17 SNPN scope.
Xiaobo Yu (Alibaba) replies to comments from Huawei, Ericsson and Motorola Mobility
==== Ph1 Revisions Deadline ====
Josep (DT) objects to this pCR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 - - - LS In/Out - - Docs:=5 -
8.2 S2-2004318 LS In Action LS from SA WG1: Reply LS on Questions on onboarding requirements SA WG1 (S1-202266) Rel-17 Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.2 S2-2003648 LS OUT Approval [DRAFT] LS on FS_eNPN progress and request for input to resolve open issues Ericsson Rel-17 Noted Chris J (T-Mobile USA) suggests this LS focuses on RAN aspects
Sebastian (Qualcomm) supports Chris.
Marco (Huawei) avoid generic questions, make specific questions. Difficult to judge the LS due lack of content.
Peter Hedman (Ericsson) provides r01 and comments.
Marco (Huawei) still questioning benefit of such generic question of feedback LS.
Sebastian (QC) agrees with Marco and proposes to note the LS.
==== Ph1 Revisions Deadline ====
Marco (Nokia) confirm request to Note the LS (NOK any version).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004203 LS OUT Approval [DRAFT] LS on UE onboarding security aspects Qualcomm Incorporated Rel-17 Noted Marco (Huawei) avoid generic request of feedabck, send LS only with precise question(s), if any.
Peter Hedman (Ericsson) provides r01 and comments.
Marco (Huawei) propose to note this LS as is in r01.
Haris (Qualcomm) responds to comments and indicates r01 is acceptable
==== Ph1 Revisions Deadline ====
Antoine (Orange) agrees with Huawei and objects to r00 and r01.
Haris (Qualcomm) provides response to Orange
Megha(Intel) supports r01 and proposes to consider this LS out for conference call on Friday
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.2 S2-2004225 LS OUT Approval [DRAFT] LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN Qualcomm Incorporated Rel-17 R02 agreed. Revised to S2-2004385 Qianghua (Huawei) provides r01
Sebastian (Qualcomm) replies to Huawei and provides r02.
Hualin (Huawei) did think one LS about security is enough and ask to merge them.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.2 S2-2004385 LS OUT Approval LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN SA WG2 Rel-17 Revision of S2-2004225_R02. Approved Approved
8.3 - - - Study on enhancement of support for Edge Computing in 5GC (FS_enh_EC) - - Docs:=131 -
8.3 - - - LS In/Out - - Docs:=11 -
8.3 S2-2003514 LS In Action LS from SA WG6: LS on Application Architecture for enabling Edge Applications SA WG6 (S6-192399) Revision of postponed S2-2002608 from S2-138E. Response drafted in S2-2004115. Final response in S2-2004386
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
8.3 S2-2004115 LS OUT Approval [DRAFT] Reply LS on Application Architecture for enabling Edge Applications Huawei, Hisilicon Rel-17 Response to S2-2003514. Revised to remove 'draft' in S2-2004386
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004386 LS OUT Approval Reply LS on Application Architecture for enabling Edge Applications SA WG2 Rel-17 Revision of S2-2004115. Approved Approved
8.3 S2-2003519 LS In Action LS from SA WG6: Reply LS on Split of work responsibilities between SA WG2 and SA WG6 SA WG6 (S6-200357) Revision of postponed S2-2002620 from S2-138E. Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.3 S2-2003534 LS In Action LS from SA WG6: LS on provisioning EDN connection info by Edge Configuration Server SA WG6 (S6-200617) Rel-17 Revision of postponed S2-2003201 from S2-138E. Response drafted in S2-2003710, S2-2003756, S2-2003801, S2-2004114 and S2-2004154. Final response in S2-2004387
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Replied to
8.3 S2-2003710 LS OUT Approval [DRAFT] Reply LS on provisioning 'EDN connection info' by Edge Configuration Server Intel Rel-17 Response to S2-2003534. Merged into S2-2004387 Magnus Olsson (Ericsson) proposes to merge S2-2003710 into S2-2004114
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003756 LS OUT Approval [DRAFT] Reply LS on provisioning 'EDN connection info' by Edge Configuration Server Apple Rel-17 Response to S2-2003534. Merged into S2-2004387 Hui Ni(Huawei): this tdoc is merged into S2-2004114.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003801 LS OUT Approval [DRAFT] Reply LS on provisioning 'EDN connection info' by Edge Configuration Server Qualcomm Wireless GmbH Response to S2-2003534. Merged into S2-2004387 Hui Ni(Huawei): suggest to merge this tdoc into S2-2004114.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2004114 LS OUT Approval [DRAFT] Reply LS on provisioning EDN connection info by Edge Configuration Server Huawei, Hisilicon Rel-17 Response to S2-2003534. R09 agreed. Revised, merging S2-2003710, S2-2003756, to S2-2004387 Hui Ni (Huawei) provides rev01 according to pre-meeting discussion.
Jicheol Lee (Samsung) provides rev02.
Changhong Shan (Intel) provides rev03 and comments.
Dieter (Deutsche Telekom) comments.
Jari (NTT DOCOMO) responds to Changdong.
Changhong (Intel) responds to Jari.
Yang Xu (OPPO) comments and provides rev04.
Krisztian (Apple) comments and provides r05.
Yang Xu (OPPO) asks question to Apple.
Changhong (Intel) is fine with r05 and proposes to use r05 as final answer to SA6.
Jicheol Lee (Samsung) is also fine with r05 and agree with Intel's proposal.
Hui Ni (Huawei) provide r06.
Magnus Olsson (Ericsson) provides r07.
Changhong (Intel) is fine with r07 and proposes to use r07 as final answer to SA6.
Jicheol Lee (Samsung) provides r08 with minor clarification.
Krisztian (Apple) is fine to proceed with r08.
Hui Ni (Huawei) is fine with r08.
Yang Xu (OPPO) commetns and provides rev09.
==== Ph1 Revisions Deadline ====
Jicheol Lee (Samsung) prefers r09.
Yang Xu (OPPO) can only accept rev09
Xiaowan (vivo) can only accept r09
Changhong (Intel) comments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004387 LS OUT Approval Reply LS on provisioning 'EDN connection info' by Edge Configuration Server SA WG2 Rel-17 Revision of S2-2004114_R09, merging S2-2003710, S2-2003756, S2-2003801 and S2-2004154. Approved Approved
8.3 S2-2004154 LS OUT Approval [DRAFT] Reply LS to SA WG6 on provisioning EDN connection info by ECS Samsung Rel-17 Response to S2-2003534. Merged into S2-2004387 Hui Ni(Huawei): suggest to merge this tdoc into S2-2004114.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 - - - Requirements/Assumptions - - Docs:=2 -
8.3 S2-2003586 P-CR Approval 23.748: Requirement related to DNS encryption. Ericsson, China Mobile Rel-17 R01 agreed. Revised to S2-2004388 Laurent (Nokia): provides comments and r01
Magnus H (Ericsson): We are OK with r01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004388 P-CR Approval 23.748: Requirement related to DNS encryption. Ericsson, China Mobile Rel-17 Revision of S2-2003586_R01. Approved Approved
8.3 - - - Solution to KI#1 - - Docs:=48 -
8.3 S2-2003552 P-CR Approval 23.748: Solution for KI#1: IP address discovery based on LDNS . China Telecom Rel-17 . Merged into S2-2004433 Magnus O (Ericson) provides a comment
==== Ph1 Revisions Deadline ====
Jicheol ask a question whether to merge this pCR to S2-2004117.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003553 P-CR Approval 23.748: PCR 23.748 - solution to KI#1, Edge Application Server discovery using anycast DNS . ChinaTelecom Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.3 S2-2003569 P-CR Approval 23.748: KI #1, New Sol: assist DNS resolution without connectivity between local and central data network. NTT DOCOMO Rel-17 R07 agreed. Revised to S2-2004389 Laurent (Nokia): provides r01 and comments
Riccardo (NTT DOCOMO): provides r02 and responds to Laurent
Stefano Faccin (Qualcomm): provides r03 with editor's notes on some unclear aspects.
Jinguo(ZTE):provides r04
Riccardo (NTT DOCOMO): provides r05 and responds to Stefano and Jinguo
Jinguo(ZTE):comment
Riccardo (NTT DOCOMO): responds to Jinguo
Stefano Faccin (Qualcomm): provides r06 re-adding an important editor's note.
Jeffrey (Juniper) asks a question
Riccardo (NTT DOCOMO) responds to Jeffrey
Riccardo (NTT DOCOMO) provides r07
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004389 P-CR Approval 23.748: KI #1, New Sol: assist DNS resolution without connectivity between local and central data network. NTT DOCOMO Rel-17 Revision of S2-2003569_R07. Approved Approved
8.3 S2-2003571 P-CR Approval 23.748: KI #1, Sol #1: Update to resolve editor's notes. NTT DOCOMO Rel-17 R02 agreed. Revised to S2-2004390 Hui Ni (Huawei) comments.
Laurent (Nokia): provides r01 and comments
Jari (NTT DOCOMO) responds to Hui
Jari (NTT DOCOMO) provides r02 and responds to Laurent
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004390 P-CR Approval 23.748: KI #1, Sol #1: Update to resolve editor's notes. NTT DOCOMO Rel-17 Revision of S2-2003571_R02. Approved Approved
8.3 S2-2003587 P-CR Discussion 23.748: KI#1, Way Forward: DNS for AS Discovery Enablers Summary. Ericsson Rel-17 Postponed Hyunsook (LGE) proposes this pCR to be NOTED.
Changhong (Intel) proposes to postpone the paper.
Magnus Olsson (Ericsson) Replies and propose to Note or Postpone the document.
Hui Ni (Huawei) propose to postpone the document.
==== Ph1 Revisions Deadline ====
Postponed
8.3 S2-2003588 P-CR Approval 23.748: KI#1, New Sol: DNS for AS Discovery for Distributed Anchor. Ericsson Rel-17 R05 agreed. Revised to S2-2004391 Laurent (Nokia): provides r01 and comments
Hui Ni(Huawei): provides r02.
Magnus (Ericsson): provides r03 and comments
John (Futurewei) provides r04.
Jicheol Lee (Samsung) provides r05.
Magnus (Ericsson): still prefers r03 and comments r04
==== Ph1 Revisions Deadline ====
Magnus O (Ericsson): We prefer r03, are ok with r04 and can live with r05
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004391 P-CR Approval 23.748: KI#1, New Sol: DNS for AS Discovery for Distributed Anchor. Ericsson Rel-17 Revision of S2-2003588_R05. Approved Approved
8.3 S2-2003589 P-CR Approval 23.748: KI #1, Sol #3: Update to remove ENs. Ericsson Rel-17 R04 agreed. Revised, merging S2-2004159, to S2-2004392 Laurent (Nokia): provides r01
Hui Ni (Huawei) comments.
Magnus (Ericsson) reply to comments.
Magnus (Ericsson): we are ok with r01
Zhuoyun (Tencent) provides r02.
Hui Ni (Huawei) provides r03.
Magnus Olsson (Ericsson) provides r04.
Zhuoyun Zhang (Tencent) is fine with r04.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004392 P-CR Approval 23.748: KI #1, Sol #3: Update to remove ENs. Ericsson Rel-17 Revision of S2-2003589_R04, merging S2-2004159 and S2-2004416. Approved Approved
8.3 S2-2003590 P-CR Approval 23.748: KI #1, New Sol: DNS over HTTP. Ericsson Rel-17 R01 agreed. Revised to S2-2004393 Jicheol Lee (Samsung) provides comments.
Magnus H (Ericsson): Answers comments
Hui Ni(Huawei) provide r01
Magnus H (Ericsson): Accepts r01
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004393 P-CR Approval 23.748: KI #1, New Sol: DNS over HTTP. Ericsson Rel-17 Revision of S2-2003590_R01. Approved Approved
8.3 S2-2003591 P-CR Approval 23.748: KI#1, New Sol: Session re-anchoring by SMF. Ericsson Rel-17 R06 agreed. Revised to S2-2004394 Hui Ni(Huawei) provide comments.
Magnus H (Ericsson): answer comments
John (Futurewei) provides r01.
Dan Wang (China Mobile) provides r02
Hui Ni (Huawei) comments
Magnus H (Ericsson): answers comments and provides r03
Changhong (Intel) comments and provides r04.
Magnus H (Ericsson): Answer comments and provides r05
Jinguo(ZTE): provide comments
Jinguo(ZTE): provide r06
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004394 P-CR Approval 23.748: KI#1, New Sol: Session re-anchoring by SMF. Ericsson Rel-17 Revision of S2-2003591_R06. Approved Approved
8.3 S2-2003643 P-CR Approval 23.748: KI#1, Solution Update - Connectivity Models, Private Access and Architecture Assumptions . Futurewei, ITRI Rel-17 R01 agreed. Revised to S2-2004395 John (Futurewei) provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004395 P-CR Approval 23.748: KI#1, Solution Update - Connectivity Models, Private Access and Architecture Assumptions . Futurewei, ITRI Rel-17 Revision of S2-2003643_R01. Approved Approved
8.3 S2-2003645 P-CR Approval 23.748: KI#1, Considerations on Way Forward. Futurewei Rel-17 Postponed Changhong (Intel) proposes to postpone the paper.
Jicheol Lee (Samsung) agrees with postponing the paper.
Hyunsook (LGE) proposes this pCR to be NOTED.
Magnus Olsson (Ericsson) comments that this pCR should be Noted or Postponed.
Hui Ni (Huawei) propose to postpone the pCR.
==== Ph1 Revisions Deadline ====
Postponed
8.3 S2-2003658 P-CR Approval 23.748: KI #1, New Solution: 5GC support for UE selection of the DNS to use. Nokia, Nokia Shanghai Bell Rel-17 R02 agreed. Revised to S2-2004396 Jari (NTT DOCOMO) comments
Magnus (Ericsson): provides revision r01
Jari (NTT DOCOMO) provides r02
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004396 P-CR Approval 23.748: KI #1, New Solution: 5GC support for UE selection of the DNS to use. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003658_R02. Approved Approved
8.3 S2-2003659 P-CR Approval 23.748: KI 1, Solution #4 (Providing the DNS authoritative server with IP addressing information about where the UE is located) Update. Nokia, Nokia Shanghai Bell Rel-17 R07 agreed. Revised to S2-2004397 Hui Ni(Huawei) provide r01.
Laurent (Nokia) provides r02 and comment
Hui Ni(Huawei) comments.
John (Futurewei) comments
Laurent (Nokia) provides r03 and comment
John (Futurewei) provides comments
Laurent (Nokia) comments and provides r04.
Magnus (Ericsson) asks a question
Laurent (Nokia) comments and provides r05.
Hui Ni (Huawei) provide comments
Jari (NTT DOCOMO) provides r06
Laurent (Nokia) comments and provides r07.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004397 P-CR Approval 23.748: KI 1, Solution #4 (Providing the DNS authoritative server with IP addressing information about where the UE is located) Update. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003659_R07. Approved Approved
8.3 S2-2003708 P-CR Approval 23.748: KI #1, New Sol: IP address discovery- DNS handling in both UPF and EC. Tencent Rel-17 Revision of S2-2000701. R02 agreed. Revised to S2-2004398 Zhuoyun Zhang (Tencent) provides r01.
Wen (vivo) comments.
Zhuoyun (Tencent) replies to Wen.
Magnus Olsson (Ericsson) provides r02.
Zhuoyun Zhang (Tencent) is fine with r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004398 P-CR Approval 23.748: KI #1, New Sol: IP address discovery- DNS handling in both UPF and EC. Tencent Rel-17 Revision of S2-2003708_R02. Approved Approved
8.3 S2-2003709 P-CR Approval 23.748: KI #1, New Sol: IP address discovery- DNS handling in UPF. Tencent Rel-17 Revision of S2-2000703. R01 agreed. Revised to S2-2004399
==== Ph1 Revisions Deadline ====
Zhuoyun Zhang (Tencent) is fine with r01.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004399 P-CR Approval 23.748: KI #1, New Sol: IP address discovery- DNS handling in UPF. Tencent Rel-17 Revision of S2-2003709_R01. Approved Approved
8.3 S2-2003774 P-CR Approval 23.748: KI #1, New Sol: Edge Configuration Server Based Discovery. Convida Wireless LLC, AT&T, Samsung Rel-17 R11 agreed. Revised to S2-2004400 Magnus H (Ericsson): Object to option 1 in solution.
Magnus (Ericsson): provides revision r01
Hui Ni(Huawei): provides revision r02
Jicheol Lee (Samsung) provides revision r03
Mike (Convida Wireless) replies to Hui (Huawei) and Magnus (Ericsson) and provides r04.
Jicheol Lee(Samsung) provides revision r05
Mike (Convida Wireless) provides r06 to make clarifications.
Hui Ni (Huawei provides r07.
Magnus (Ericsson): comments
Mike (Convida Wireless) replies to Magnus (Ericsson) and provides rev09.
Hui Ni (Huawei) provides rev10.
Mike Starsinic (Convida Wireless) comments and is good with rev10.
Mike Starsinic (Convida Wireless) provides rev11, prefers rev10.
==== Ph1 Revisions Deadline ====
Magnus H (Ericsson): Object to all revision with option 1, we accept revision 10.
Magnus H (Ericsson): correcting previous comment: Object to all revision with option 1, we accept revision 11.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004400 P-CR Approval 23.748: KI #1, New Sol: Edge Configuration Server Based Discovery. Convida Wireless LLC, AT&T, Samsung Rel-17 Revision of S2-2003774_R11. Approved Approved
8.3 S2-2003780 P-CR Approval 23.748: KI#1, Sol#2: Update to clarify the DNS request offload in edge DN for ULCL, and remove the EN1 and EN3. China Mobile Rel-17 Merged into S2-2004402 Dan Wang(China Mobile) this paper is merged into S2-2003832
Changhong (Intel) comments.
Dan Wang (China Mobile) reply to Changhong (Intel) comments.
Changhong (Intel) comments and provides r01.
Dan (China Mobile) reply to Changhong's comments
==== Ph1 Revisions Deadline ====
Changhong (Intel) replies to Dan.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003812 P-CR Approval 23.748: KI#1, Sol#7, Update to resolve editor note. ZTE Rel-17 R02 agreed. Revised to S2-2004401 Magnus Olsson (Ericsson) provides r01.
Jinguo (ZTE) provides r02
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004401 P-CR Approval 23.748: KI#1, Sol#7, Update to resolve editor note. ZTE Rel-17 Revision of S2-2003812_R02. Approved Approved
8.3 S2-2003832 P-CR Approval 23.748: KI#1, Sol#2: Update to remove ENs . Vivo Rel-17 R04 agreed. Revised, merging S2-2003780 and S2-2004252, to S2-2004402 Xiaowan (vivo) provide r01
Xiaowan (vivo) provide r02
Hui NI(Huawei) provides comments.
Magnus O (Ericsson) provides r03.
Magnus O (Ericsson) provides r03 with link.
xiaowan (vivo) provides r04 and response to the comments from nihui
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004402 P-CR Approval 23.748: KI#1, Sol#2: Update to remove ENs . Vivo, China Mobile Rel-17 Revision of S2-2003832_R04, merging S2-2003780 and S2-2004252. Approved Approved
8.3 S2-2003918 P-CR Approval 23.748: KI #1, Sol #1: Update to support UE mobility. CATT Rel-17 R03 agreed. Revised to S2-2004403 Jari (NTT DOCOMO) provides r01
Yuan (CATT) provides r02 and seeks clarification.
Magus Olsson (Ericsson) provides comments.
Jari (NTT DOCOMO) provides r03 and comments
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004403 P-CR Approval 23.748: KI #1, Sol #1: Update to support UE mobility. CATT Rel-17 Revision of S2-2003918_R03. Approved Approved
8.3 S2-2003926 P-CR Approval 23.748: KI#1, New Sol: Provisioning MEC Policy including EAS information to the UE. LG Electronics, SK Telecom, LG Uplus Rel-17 R06 agreed. Revised to S2-2004404 Hui Ni (Huawei) comments.
Jicheol Lee (Samsung) comments.
Jari (NTT DOCOMO) comments
Jinguo (ZTE) comments.
LaeYoung (LGE) provides r01 and answers.
Jari (NTT DOCOMO) provides r02
Changhong (Intel) provides comments.
LaeYoung (LGE) provides r03 and answers.
Jari (NTT DOCOMO) responds to LaeYoung
LaeYoung (LGE) thanks to Jari's response.
Jinguo (ZTE) provides further comment.
LaeYoung (LGE) provides answer.
Magnus (Ericsson) provides a comment and question.
LaeYoung (LGE) provides r04 and answer.
Yang Xu (OPPO) asks a question.
LaeYoung (LGE) provides answer to Q from Yang Xu (OPPO).
Magnus Olsson (Ericsson) provides follow up comments.
LaeYoung (LGE) provides r05.
Jicheol Lee (Samsung) provides comments questioning how the proposal works.
LaeYoung (LGE) answers to comments from Jicheol Lee (Samsung).
Jari (NTT DOCOMO) provides r06
==== Ph1 Revisions Deadline ====
LaeYoung (LGE) is OK with r06 and thanks to Jari (NTT DOCOMO).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004404 P-CR Approval 23.748: KI#1, New Sol: Provisioning MEC Policy including EAS information to the UE. LG Electronics, SK Telecom, LG Uplus Rel-17 Revision of S2-2003926_R06. Approved Approved
8.3 S2-2003984 P-CR Approval 23.748: KI #1, New Sol: Mapping the AS IP address to Edge Server IP address. Tencent Rel-17 R01 agreed. Revised to S2-2004405 Jicheol Lee (Samsung) comments.
Chunshan Xiong (Tencent) provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004405 P-CR Approval 23.748: KI #1, New Sol: Mapping the AS IP address to Edge Server IP address. Tencent Rel-17 Revision of S2-2003984_R01. Approved Approved
8.3 S2-2003996 P-CR Approval 23.748: KI#1, new solution: Edge Application Server discovery using an Address Resolution Function. Motorola Mobility, Lenovo Rel-17 R01 agreed. Revised to S2-2004406 Magnus Olsson (Ericsson) provides r01.
Tingfang Tang (Lenovo) response to Magnus that r01 is OK for me.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Jianhua (OPPO) provide r01 and co-sign.
Revised
8.3 S2-2004406 P-CR Approval 23.748: KI#1, new solution: Edge Application Server discovery using an Address Resolution Function. Motorola Mobility, Lenovo Rel-17 Revision of S2-2003996_R01. Approved Approved
8.3 S2-2004067 P-CR Approval 23.748: KI#1, New Solution: DNS Inspector based EAS Discovery with UL CL. Intel Rel-17 R02 agreed. Revised to S2-2004407 John (Futurewei) provides comments.
Changhong (Intel) replies to John's comments.
Magnus Olsson (Ericsson) asks question.
Changhong (Intel) replies to Magnus' question.
Magnus Olsson (Ericsson) provides follow up comment.
Ulises Olvera (InterDigital) provide comments.
Changhong (Intel) provides r01 based on Magnus' and r02 based on Ulises' comments and answers to Ulises' comments.

Ulises Olvera (InterDigital Inc) comments to r02 and addressing Changhong's comments/questions.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004407 P-CR Approval 23.748: KI#1, New Solution: DNS Inspector based EAS Discovery with UL CL. Intel Rel-17 Revision of S2-2004067_R02. Approved Approved
8.3 S2-2004159 P-CR Approval 23.748: KI# 1, Sol #3,6: Update to Clarify DNS Handling. Tencent Rel-17 Merged into S2-2004392 Zhuoyun Zhang (Tencent) proposes to merge the update of solution 6 to S2-2004116.
Zhuoyun Zhang (Tencent) proposes to merge to both S2-2004116 and S2-2003589.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2004116 P-CR Approval 23.748: Update solution #6: Discovery of EAS based on DNS. Huawei, HiSilicon Rel-17 R01 agreed. Revised to S2-2004408 Hui Ni (Huawei) provides rev01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004408 P-CR Approval 23.748: Update solution #6: Discovery of EAS based on DNS. Huawei, HiSilicon, Tencent Rel-17 Revision of S2-2004116_R01. Approved Approved
8.3 S2-2004231 P-CR Approval 23.748: Update to Solution 1 in TR 23.758 'Provisioning URSP configuration to the UE to establish PDU Sessions for edge applications' based on PvDs. InterDigital Inc. Rel-17 R02 agreed. Revised to S2-2004409 Jari (NTT DOCOMO) comments
Changhong (Intel) comments.
Changhong (Intel) comments and proposes to NOTE this paper.
Magnus Olsson (Ericsson) same comment as Changhong.
Changhong (Intel) requests to ignore the mail as the TD number should be corrected to S2-2004234.
Hui Ni (Huawei) has same comments.
Ulises Olvera (InterDigital) addressing comments and providing r01.
Ulises Olvera (InterDigital) addressing Jari's comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004409 P-CR Approval 23.748: Update to Solution 1 in TR 23.758 'Provisioning URSP configuration to the UE to establish PDU Sessions for edge applications' based on PvDs. InterDigital Inc. Rel-17 Revision of S2-2004231_R02. Approved Approved
8.3 - - - Solution to KI#2 - - Docs:=45 -
8.3 S2-2003592 P-CR Approval 23.748: KI#2, New Sol: DNS for AS Discovery at Edge Relocation. Ericsson Rel-17 R03 agreed. Revised to S2-2004410 Jicheol Lee (Samsung) asks clarification what is proposed.
Changhong (Intel) comments and provides r01.
Magnus H (Ericsson): don't accept r01
Magnus H (Ericsson): answer comment
Magnus H (Ericsson): revision r03 provided
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004410 P-CR Approval 23.748: KI#2, New Sol: DNS for AS Discovery at Edge Relocation. Ericsson Rel-17 Revision of S2-2003592_R03. Approved Approved
8.3 S2-2003593 P-CR Approval 23.748: KI#2, New Sol: Support of edge relocation, triggering of new DNS query by the UE. Ericsson Rel-17 R07 agreed. Revised to S2-2004449. John (Futurewei) provides r01.
Dan Wang(China Mobile) provides comments for clarification
Tingfang Tang(Lenovo) provides comments for clarification
Magnus H (Ericsson): Answers comments and provides r02
John (Futurewei) accepts updates in revision r02.
Jicheol Lee (Samsung) raised a security concern on this solution.
Magnus H (Ericsson): comments
Jicheol Lee (Samsung) comments.
Magnus H (Ericsson): provides r03
Tingfang Tang (Lenovo) provide r05 to clarify the trigger for the SMF/UPF ICMP processing.
==== Ph1 Revisions Deadline ====
Jicheol Lee (Samsung) objects all the versions of this pCR because the security concern using ICMP is neither resolve nor captured as an Editor's Note.
Magnus H (Ericsson): comments to objection
Jicheol Lee (Samsung) explains about 'comments to objection from Magnus H (Ericsson)'
Tingfang Tang (Lenovo) To correct that the number of latest version for revision should be r04.
Magnus (Ericsson): Asks to open this document in CC#2 tomorrow to find a way forward
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004449 P-CR Approval 23.748: KI#2, New Sol: Support of edge relocation, triggering of new DNS query by the UE. Ericsson Rel-17 Revision of S2-2003593_R07. Approved Approved
8.3 S2-2003644 P-CR Approval 23.748: KI#2, New Solution - Seamless Change of Edge for Stateful Applications . Futurewei, ITRI Rel-17 R02 agreed. Revised to S2-2004411 Magnus H (Ericsson): provides r01
John (Futurewei) addresses comments and provides r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004411 P-CR Approval 23.748: KI#2, New Solution - Seamless Change of Edge for Stateful Applications . Futurewei, ITRI Rel-17 Revision of S2-2003644_R02. Approved Approved
8.3 S2-2003737 P-CR Approval 23.748: KI #2, New Sol: Edge Relocation triggered by a central AF. Apple, AT&T Rel-17 Merged into S2-2004413 Changhong (Intel) proposes to merge it into ZTE's paper S2-2003813.
Jinguo(ZTE) comments and proposes to to merge it into ZTE's paper S2-2003813
Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson): provides comments
Hui Ni (Huawei): provides comments
Stefano Faccin (Qualcomm) proposes to mark this paper as merged if indeed it is merged with ZTE's paper S2-2003813 (I cannot find trace of that). Otherwise we propose to note the paper since valid comments were raised and we would like to see answers to those open issues.
Krisztian (Apple): we are fine to merge S2-2003737 into S2-2003813.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003721 P-CR Approval 23.748: Persistent UE address across multiple UPFs. Juniper Networks Rel-17 R01 agreed. Revised to S2-2004412 Changhong (Intel) comments.
Jeffrey (Juniper) responds to Changhong's (Intel) comments.
Hui Ni (Huawei) comments.
Jeffrey (Juniper) replies to Hui Ni (Huawei)'s comments.
R01 was provided in earlier email but it was not mentioned in the notes.
Tingfang Tang (Lenovo) comments.
Jeffrey (Juniper) responds to Tingfang Tang (Lenovo)'s comments.
Tingfang Tang (Lenovo) provide comments.
Jeffrey (Juniper) responds to Tingfang Tang (Lenovo)'s latest comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004412 P-CR Approval 23.748: Persistent UE address across multiple UPFs. Juniper Networks Rel-17 Revision of S2-2003721_R01. Approved Approved
8.3 S2-2003813 P-CR Approval 23.748: KI#2, New Sol: Reducing packet loss during EAS relocation. ZTE, NTT Docomo, Lenovo, Motorola Mobility Rel-17 R09 agreed. Revised, merging S2-2003737, to S2-2004413 Jinguo (ZTE) provides r01.
Fenqin (Huawei) comments.
Changhong (Intel) provides comments.
Jinguo(ZTE) response and provides r02.
Jinguo(ZTE) response and provides r03.
Riccardo (NTT DOCOMO) provides r04.
Magnus H (Ericsson): Comments provided.
Riccardo (NTT DOCOMO): responds to Magnus.
Jinguo(ZTE): provides r05.
Magnus H (Ericsson): provides comments
Jinguo (ZTe): provides r06.
Changhong (Intel) provides r07 and adds Intel as source company.
Krisztian (Apple) provides r08 with Apple as co-source.
Jinguo (ZTE) provides r09 with AT&T as co-source.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004413 P-CR Approval 23.748: KI#2, New Sol: Reducing packet loss during EAS relocation. ZTE, NTT Docomo, Lenovo, Motorola Mobility, Intel, Apple, AT&T Rel-17 Revision of S2-2003813_R09, merging S2-2003737. Approved Approved
8.3 S2-2003842 P-CR Approval 23.748: KI#2: New Sol: Supporting application server change based on AF notification. LG Electronics, SK Telecom, LG Uplus Rel-17 R05 agreed. Revised, merging S2-2003998, to S2-2004414 Wen (vivo) provides r01.
Hyunsook (LGE) provides r02 by merging with S2-2003998 from Lenovo (by offline discussion).
Magnus H (Ericsson): Provides comments
Tingfang Tang (Lenovo) Response for comments.
Changhong (Intel) comments. It's unacceptable to use NAS message to notify UE about the EAS change.
Hyunsook (LGE) replies to Intel and Ericsson.
Changhong (Intel) replies to Hyunsook.
Hyunsook (LGE) replies to Changhong.
Wen (vivo) comments and provide r03.
Hyunsook (LGE) comments.
Hyunsook (LGE) provides r04.
Wen (vivo) comments.
Hyunsook (LGE) provides r05.
==== Ph1 Revisions Deadline ====
Changhong (Intel) proposes to merge this paper into S2-2004127.
Hyunsook (LGE) replies to Changhong, We will co-work for the next meeting.
With the clarification on the difference with S2-2004127 in the previous email,
Hyunsook (LGE) proposes to approve r05 in this meeting.
Wen (vivo): we are fine with the r05, r03 and r01 and object to the rest.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004414 P-CR Approval 23.748: KI#2: New Sol: Supporting application server change based on AF notification. LG Electronics, SK Telecom, LG Uplus, Lenovo, Motorola Mobility Rel-17 Revision of S2-2003842_R05, merging S2-2003998. Approved Approved
8.3 S2-2003917 P-CR Approval 23.748: KI #2, New Sol: Support of application seamless change. CATT Rel-17 . Merged into S2-2004417 Wen (vivo) provides r01.
Changhong (Intel) comments. It's unacceptable to abuse NAS message to notify UE about the EAS IP address since the EAS change can be very frequent due to mobility and a UE can be served by multiple MEC services simultaneously.
S2-2003917 is merged into S2-2004127.
Yuan (CATT) responds to Changhong (Intel)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003997 DISCUSSION Endorsement Discussion on KI#2 to support service continuity for edge application server relocation. Lenovo, Motorola Mobility, Huawei? CATT? NTT DOCOMO? Alibaba? Rel-17 Confirm Sources! Noted Noted
8.3 S2-2003998 P-CR Approval 23.748: KI#2, new solution: UE aware edge relocation. Lenovo, Motorola Mobility, Huawei? CATT? LG Electronics? Alibaba? Rel-17 Confirm Sources! Merged into S2-2004414 and S2-2004417 Wen (vivo) provides r01.
Tingfang Tang (Lenovo) responses to Wen(vivo) and provides r02.
Tingfang Tang (Lenovo) responses to Yang Xu.
Fenqin(Huawei) comments.
Tingfang Tang (Lenovo) response to Fenqin.
Changhong (Intel) comments. It's unacceptable to abuse NAS message to notify UE about the EAS IP address since the EAS change can be very frequent due to mobility and a UE can be served by multiple MEC services simultaneously.
Changhong (Intel) proposes to mark this paper being merged into S2-2004127 and S2-2003813.
Tingfang Tang (Lenovo) reply to Changhong.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003999 P-CR Approval 23.748: KI#2, new solution: CN-based edge relocation. Lenovo, Motorola Mobility, Intel? China Telecom? Rel-17 Confirm Sources!. R02 agreed. Revised to S2-2004415 Changhong (Intel) proposes to merge it into S2-2003813 as S2-2003813 also supports UE unaware option in the latest revision. The call flows are overlapping with the one in S2-2003813.
Magnus O (Ericsson): provides r01 to gage the support for simplified solution.
Tingfang Tang (Lenovo) provide feedback.
Tingfang Tang (Lenovo) response to the comments from Magus and provide r02.
==== Ph1 Revisions Deadline ====
Changhong (Intel) proposes to merge it into S2-2003813 for this meeting as 3813 is also CN based edge relocation.
Tingfang Tang (Lenovo) response Changhong.
Changhong (Intel) proposes to either NOTE this paper or merge it into S2-2003813 as the major aspect of preventing packet loss and EAS IP address replacement is missing, which makes it not work.
Tingfang Tang (Lenovo) response to Changhong.
Changhong (Intel) asks to postpone this paper as two major aspects of preventing packet loss and EAS IP address replacement are missing.
Changhong (Intel) responds to Tingfang.
Changhong (Intel) can live with r02 after offline discussion.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004415 P-CR Approval 23.748: KI#2, new solution: CN-based edge relocation. Lenovo, Motorola Mobility Rel-17 Revision of S2-2003999_R02. Approved Approved
8.3 S2-2004069 P-CR Approval 23.748: KI#2, New Solution: UE Agnostic EAS IP address replacement for traffic subject to edge computing. Intel, Tencent Rel-17 Revised, merging S2-2003554 and S2-2004186 to S2-2004314 Revised
8.3 S2-2004314 P-CR Approval 23.748: KI#2, New Solution: UE Agnostic EAS IP address replacement for traffic subject to edge computing Intel, Tencent, China Telecom Rel-17 Revision of S2-2004069, merging S2-2003554 and S2-2004186. R04 agreed. Revised to S2-2004416 Riccardo (NTT DOCOMO): provides r01
Tingfang Tang (Lenovo) comments.
Changhong (Intel) replies to Tingfang's comments.
Changhong (Intel) replies to Tingfang's comments and provides r02 to address the EN added by Riccardo (NTT DOCOMO).
Tingfang Tang (Lenovo) provide r03.
Magnus H (Ericsson): provides r04
Tingfang Tang (Lenovo) provide r05 to merge S2-2003999.
==== Ph1 Revisions Deadline ====
Changhong (Intel) cannot accept r05 and proposes to accept r04.
Tingfang Tang (Lenovo) response Changhong.
Tingfang Tang (Lenovo) Lenovo can only accept r05 with Anchor EAS optional, otherwise Lenovo objects this solution.
Tingfang Tang (Lenovo) Lenovo can accept r04 as solution without Anchor EAS can be included in 3999 agreed by Intel.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004416 P-CR Approval 23.748: KI#2, New Solution: UE Agnostic EAS IP address replacement for traffic subject to edge computing. Intel, Tencent, China Telecom Rel-17 Revision of S2-2004314_R04. Approved Approved
8.3 S2-2003554 P-CR Approval 23.748: Solution for KI#2: Edge Relocation based on PFDF under EAS abnormal condition . China Telecom Rel-17 Merged into S2-2004314 Merged
8.3 S2-2004186 P-CR Approval 23.748: KI #2, New Sol: Edge Server Relocation. Tencent Rel-17 Merged into S2-2004314 Merged
8.3 S2-2004127 P-CR Approval 23.748: KI#2, New solution: Application Relocation with UE assistance. Huawei, Hisilicon Rel-17 R16 agreed. Revised, merging S2-2003917 and S2-2004190, to S2-2004417 Wen (vivo) provides r01.
Fenqin(Huawei) comments and provides r02
Jicheol Lee (Samsung) comments.
Yuan (CATT) comments.
Tingfang Tang (Lenovo) comments.
Fenqin(Huawei) comments and provide r03
Changhong (Intel) comments. It's unacceptable to abuse NAS message to notify UE about the EAS IP address since the EAS change can be very frequent due to mobility and a UE can be served by multiple MEC services simultaneously.
Hyunsook (LGE) replies to Intel.
Wen (vivo) comments and provides r04.
Changhong (Intel) replies to Hyunsook.
Fenqin(Huawei) comments.
Changhong (Intel) replies to Fenqin(Huawei)'s comments.
Yuan (CATT) provides S2-2004127r05.
Tingfang Tang (Lenovo) reply to changhong.
Wen (vivo) comments.
Yuan (CATT) provides response to Changhong(Intel).
Jinguo(ZTE) provides comment.
Fenqin (Huawei) provides response to Jinguo and suggest go back to r05 version.
Xiaobo Yu (Alibaba) provides r07
Fenqin (Huawei) provides response.
Fenqin (Huawei) provides response and r08
Jinguo (ZTE) provides response.
Tingfang Tang (Lenovo) provide comments and r09.
Fenqin (Huawei) provides response and suggest go back to r08 version.
Xiaobo Yu (Alibaba) provides r10 and replies to the comments from Fenqin (Huawei)
Fenqin (Huawei) provides response and r11
Wen (vivo) reply.
Xiaobo Yu (Alibaba) provides response and r12
Magnus(Ericsson): new revision r13
Fenqin(Huawei)provides response and r14.
Wen (vivo) comments and provide new revision r15.
Fenqin(Huawei)provides response and r16.
==== Ph1 Revisions Deadline ====
Wen (vivo): we are fine with the r01,r04,r15 and r16 and object to the rest.
Jicheol Lee (Samsung) comments the original concern is not resolved and proposes additional EN.
Fenqin(Huawei)provides feedback.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004417 P-CR Approval 23.748: KI#2, New solution: Application Relocation with UE assistance. Huawei, Hisilicon, Lenovo, Motorola Mobility, CATT, Alibaba Group Rel-17 Revision of S2-2004127_R16, merging S2-2003917, S2-2003998 and S2-2004190. Approved Approved
8.3 S2-2004128 P-CR Approval 23.748: KI#2, New solution: UE DNS cache flush. Huawei, Hisilicon Rel-17 Revision of S2-2000373 Revised, merging S2-2004068, to S2-2004326. Wen (vivo) provides comments for clarification
Fenqin(Huawei) provides feedback.
Tingfang Tang (Lenovo) comments.
==== Ph1 Revisions Deadline ====
Revised
8.3 S2-2004326 P-CR Approval 23.748: KI#2, New solution: UE DNS cache flush. Huawei, Hisilicon, Intel Rel-17 Revision of S2-2004128, merging S2-2004068. R01 agreed. Revised to S2-2004418 Fenqin(Huawei) provide feedback.
Tingfang Tang (Lenovo) comments.
Fenqin(Huawei) provide feedback and r01.
Tingfang Tang (Lenovo) provide feedback that Lenovo is OK with the r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004418 P-CR Approval 23.748: KI#2, New solution: UE DNS cache flush. Huawei, Hisilicon, Intel Rel-17 Revision of S2-2004326_R01. Approved Approved
8.3 S2-2004068 P-CR Approval 23.748: KI#1, New Solution: EAS IP address Re-resolution Solution. Intel Rel-17 Merged into S2-2004326 Merged
8.3 S2-2004149 P-CR Approval 23.748: KI#2, New Sol: IP preserving relocation for SSC mode 3. Samsung Rel-17 R01 agreed. Revised to S2-2004419 Changhong (Intel) comments.
Jicheol Lee (Samsung) answers Intel's question.
Jeffrey (Juniper) follows up on Jicheol Lee's (Samsung) answers to Intel's question.
Hui NI (Huawei) comments.
Tingfang Tang (Lenovo) comments.
Jicheol Lee (Samsung) provides r01 with clarifications.
Tingfang Tang (Lenovo) provide comments.
==== Ph1 Revisions Deadline ====
Jicheol Lee (Samsung) clarified the question from Tingfang Tang (Lenovo)
Tingfang Tang (Lenovo) response.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004419 P-CR Approval 23.748: KI#2, New Sol: IP preserving PSA relocation with two simultaneous PDU Sessions. Samsung Rel-17 Revision of S2-2004149_R01. Approved Approved
8.3 S2-2004151 P-CR Approval 23.748: KI#2 New Sol: local DN notification to the UE. Samsung Rel-17 R01 agreed. Revised to S2-2004420 Changhong (Intel) comments.
Jicheol Lee (Samsung) provides r01 with answers to Intel's questions.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004420 P-CR Approval 23.748: KI#2 New Sol: local DN notification to the UE. Samsung Rel-17 Revision of S2-2004151_R01. Approved Approved
8.3 S2-2004152 P-CR Approval 23.748: KI#2 New Sol: Edge relocation considering user plane latency. Samsung Rel-17 R01 agreed. Revised to S2-2004421 Xiaobo Yu (Alibaba) provides comments.
Changhong (Intel) comments.
Jicheol Lee (Samsung) provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004421 P-CR Approval 23.748: KI#2 New Sol: Edge relocation considering user plane latency. Samsung Rel-17 Revision of S2-2004152_R01. Approved Approved
8.3 S2-2004234 P-CR Approval 23.748: New Solution to KI 2: Addressing Edge Relocation using External Parameter Provisioning. InterDigital Inc. Rel-17 R03 agreed. Revised to S2-2004422 Changhong (Intel) comments and proposes to NOTE this paper.
Ulises Olvera (InterDigital Inc) comments arguing why our paper is a valid option.
Jinguo (ZTE) comments
Magnus (Ericsson): r02 provided
Ulises Olvera (InterDigital Inc): r03 provided to correct typo (purely editorial).
Ulises Olvera (InterDigital Inc) addressing ZTE's comments
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004422 P-CR Approval 23.748: New Solution to KI 2: Addressing Edge Relocation using External Parameter Provisioning. InterDigital Inc. Rel-17 Revision of S2-2004234_R03. Approved Approved
8.3 S2-2004118 P-CR Approval 23.748: Solution for KI#2: EAS change with reducing packet loss. Huawei, HiSilicon, Lenovo, Motorola Mobility Rel-17 R02 agreed. Revised to S2-2004423 Jicheol Lee (Samsung) comments.
Hui Ni (Huawei) responses and provide rev01.
Changhong (Intel) comments.
Hui Ni (Huawei) responses and provide r02
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004423 P-CR Approval 23.748: Solution for KI#2: EAS change with reducing packet loss. Huawei, HiSilicon, Lenovo, Motorola Mobility Rel-17 Revision of S2-2004118_R02. Approved Approved
8.3 S2-2004190 P-CR Approval 23.748: Solution for the KI#2: Edge relocation across different networks belonging to the same operator. Alibaba Group Rel-17 . Merged into S2-2004417 Wen (vivo) provides r01.
Changhong (Intel) provides comments.
Xiaobo Yu (Alibaba) responses to the comments from Changhong (Intel)
Fenqin(Huawei ) provides this contribution to be merged into 4127.
Changhong (Intel) also proposes to merge this contribution into 4127.
Xiaobo Yu (Alibaba) agrees to merge 2004190 to 2004127
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2004191 P-CR Approval 23.748: Solution for the KI#2: Edge relocation between inter-connected 5GC. Alibaba Group Rel-17 Noted Fenqin(Huawei) provides comment and suggest to NOTE this paper.
Changhong (Intel) shares Huawei's view and proposes to NOTE this paper.
Changhong (Intel) provides comments and proposes to merge it into S2-2004190.
Xiaobo Yu (Alibaba) replies to comments from Intel, Huawei
==== Ph1 Revisions Deadline ====
Noted
8.3 S2-2004236 P-CR Approval 23.748: Solution for KI#2: Edge relocation based on MPTCP. Huawei, HiSilicon, InterDigital Inc., Apple? Rel-17 R01 agreed. Revised to S2-2004424. Jicheol Lee (Samsung) expresses concerns on this pCR.
Ulises Olvera (InterDigital) addressing expressed concerns.
Changhong (Intel) shares the concerns from Jicheol (Samsung) and comments.
Hui Ni(Huawei) responses.
Jinguo(ZTE) Comment
==== Ph1 Revisions Deadline ====
Changhong (Intel) comments.
Hui Ni (Huawei) responses.
Ulises Olvera (InterDigital Inc) agree with Hui.
Jicheol Lee (Samsung) objects this pCR.
Ulises Olvera (InterDigital Inc) questions the objection from Samsung.
Jicheol Lee (Samsung) responds Ulises Olvera (InterDigital Inc).
Jicheol Lee(Samsung) responds to Hui NI (Huawei) response.
Hui NI (Huawei) questions the objections.
Magnus H (Ericsson): Missing impacts on UE and SMF that should be fixed for next SA2 meeting.
Changhong (Intel) comments on time-saving and fairness.
Hui Ni (Huawei): provides to add ENs for this meeting.
Jicheol Lee (Samsung) comments 'with conditional withdraw of objection'
Hui Ni (Huawei) provides a draft r01.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004424 P-CR Approval 23.748: Solution for KI#2: Edge relocation based on MPTCP Huawei, HiSilicon, InterDigital Inc., Apple Rel-17 Revision of S2-2004236_R01. Approved Jicheol Lee (Samsung) expresses concerns on this pCR.
Ulises Olvera (InterDigital) addressing expressed concerns.
Changhong (Intel) shares the concerns from Jicheol (Samsung) and comments.
Hui Ni(Huawei) responses.
Jinguo(ZTE) Comment
==== Ph1 Revisions Deadline ====
Changhong (Intel) comments.
Hui Ni (Huawei) responses.
Ulises Olvera (InterDigital Inc) agree with Hui.
Jicheol Lee (Samsung) objects this pCR.
Ulises Olvera (InterDigital Inc) questions the objection from Samsung.
Jicheol Lee (Samsung) responds Ulises Olvera (InterDigital Inc).
Jicheol Lee(Samsung) responds to Hui NI (Huawei) response.
Hui NI (Huawei) questions the objections.
Magnus H (Ericsson): Missing impacts on UE and SMF that should be fixed for next SA2 meeting.
Changhong (Intel) comments on time-saving and fairness.
Hui Ni (Huawei): provides to add ENs for this meeting.
Jicheol Lee (Samsung) comments 'with conditional withdraw of objection'
Hui Ni (Huawei) provides a draft r01.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.3 S2-2003778 P-CR Approval 23.748: KI#2,New Solution: Seamless change of Edge Application Sever for stateful applications by caching application status information in NEF China Mobile Rel-17 R03 agreed. Revised to S2-2004425 Changhong (Intel) comments.
Dan (China Mobile) reply to Changhong (Intel) comments.
Tingfang Tang (Lenovo) comments and provides r02.
Magnus H (Ericsson): provides comments
Dan (China Mobile) replies to Magnus comments and provides r03
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004425 P-CR Approval 23.748: KI#2,New Solution: Seamless change of Edge Application Sever for stateful applications by caching application status information in NEF . China Mobile Rel-17 Revision of S2-2003778_R03. Approved Approved
8.3 - - - Solution to KI#3 - - Docs:=21 -
8.3 S2-2003594 P-CR Approval 23.748: KI#3, New Sol: Network Information Provisioning using the IP path. Ericsson Rel-17 Revised to S2-2004438. Jinguo (ZTE) propose to keep it open.
==== Ph1 Revisions Deadline ====
Jinguo (ZTE) propose to note this paper as RAN impact
==== Ph1 Final Deadline ====
Magnus O (Ericsson) propose to approve the document.
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004438 P-CR Approval 23.748: KI#3, New Sol: Network Information Provisioning using the IP path. Ericsson Rel-17 Revision of S2-2003594. Approved Approved
8.3 S2-2003660 P-CR Approval 23.748: KI#3, new solution: Providing selected radio information to an App requiring it. Nokia, Nokia Shanghai Bell Rel-17 R05 agreed. Revised to S2-2004426 Hui Ni(Huawei) comments.
Laurent (Nokia): provides comments and r01
Hui Ni (Huawei) objects.
Laurent (Nokia) answers.
Hui Ni (Huawei) answers.
Dan(China Mobile) comments
Laurent (Nokia): provides comments and r02
Hui Ni(Huawei) provide comments and propose to consider the solution is merged into S2-2003707.
Laurent (Nokia) can't merge into S2-2003707.
Magnus H (Ericsson): comments
Laurent (Nokia): comments and provides r05
Dan (China Mobile): comments
Hui Ni(Huawei) objects all revisions and can only live with r04.
Hui Ni(Huawei) provide r05..
==== Ph1 Revisions Deadline ====
Laurent (Nokia) wants to express it is REALLY unfair to scratch a solution by removing ½ of its content (which is what r04 and R05 are doing) , while not explaining why the removed part does not work. We are not at a phase of evaluating solutions. We should include r03 in the TR. I request this to be discussed as part of Friday CC
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004426 P-CR Approval 23.748: KI#3, new solution: Providing selected radio information to an App requiring it. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003660_R05. Approved Approved
8.3 S2-2003676 P-CR Approval 23.748: KI #3, New Sol: Low latency exposure API solution. Sony Rel-17 R04 agreed. Revised to S2-2004427 LaeYoung (LGE) provides comments.
Lars Nord (Sony) provides rev01.
Hui Ni (Huawei) provides rev02.
Magnus H (Ericsson): We agree rev02
LaeYoung (LGE) comments.
Lars Nord (Sony) comment Hui rev2
Lars Nord (Sony) provides r03
Hui Ni (Huawei) responses
Lars Nord (Sony) responds to Hui
Lars Nord (Sony):
Magnus H (Ericsson): provides comments and wants rev2
Laurent (nokia): provides comments and provides rev04
==== Ph1 Revisions Deadline ====
Lars (Sony): We can accept rev04
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004427 P-CR Approval 23.748: KI #3, New Sol: Low latency exposure API solution. Sony Rel-17 Revision of S2-2003676_R04. Approved Approved
8.3 S2-2003707 P-CR Approval 23.748: KI #3, New Sol: Network Information Exposure to Local AF with Low Latency. Tencent Rel-17 Revision of S2-2000704. R04 agreed. Revised to S2-2004428 Jicheol Lee (Samsung) questioned if there is RAN impact.
Zhuoyun (Tencent) provides r01.
Hui Ni(Huawei) comments.
Zhuoyun (Tencent) replies to Hui and provides r02.
Hui Ni (Huawei) provides comments.
Zhuoyun Zhang (Tencent) provides r03.
Laurent (Nokia) comments.and provides r04
==== Ph1 Revisions Deadline ====
Zhuoyun (Tencent) is fine with r04
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004428 P-CR Approval 23.748: KI #3, New Sol: Network Information Exposure to Local AF with Low Latency. Tencent Rel-17 Revision of S2-2003707_R04. Approved Approved
8.3 S2-2003761 P-CR Approval 23.748: Solution for KI#3 . OPPO Rel-17 R03 agreed. Revised to S2-2004429 LaeYoung (LGE) provides comments.
Jicheol Lee (Samsung) provides comments.
Yang Xu (OPPO) answers.
LaeYoung (LGE) provides answer.
Magnus H (Ericsson): comments
Hui NI (Huawei): comments
Yang Xu (OPPO) answers to Huawei
Yang Xu (OPPO) provides rev01.
LaeYoung (LGE) provides comments to r01.
Laurent (nokia) provides comments and r02.
Yang Xu (OPPO) provides r03.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004429 P-CR Approval 23.748: Solution for KI#3 . OPPO Rel-17 Revision of S2-2003761_R03. Approved Approved
8.3 S2-2003771 P-CR Approval 23.748: KI#3, New Solution: Local NEF Deployment for network information exposure to Local AF with Low Latency. China Mobile,AT&T Rel-17 Approved Magnus H (Ericsson): Suggest to merge with S2-2004078
Dan Wang (China Mobile) reply to Ericsson and can not be merged with S2-2004078
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.3 S2-2003985 P-CR Approval 23.748: KI #3, New Sol: User Plane based Network Information Provisioning . Tencent Rel-17 R03 agreed. Revised to S2-2004430 LaeYoung (LGE) comments.
Chunshan Xiong (Tencent) responses to LGE.
Chunshan Xiong(Tencent) provides a revision.
Laurent (Nokia) comments and provides r02
Chunshan Xiong (Tencent) response the comments.
Chunshan Xiong (Tencent) provides r03
==== Ph1 Revisions Deadline ====
Jicheol Lee (Samsung) raises the security issue using ICMP and propose NOTE or POSTPONE this CR.
Chunshan Xiong (Tencent) responses to Samsung and ask Samsung to change its Note/Postpone Comments.
Jicheol Lee (Samsung) comments
Chunshan Xiong (Tencent) responses to Samsung.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004430 P-CR Approval 23.748: KI #3, New Sol: User Plane based Network Information Provisioning . Tencent Rel-17 Revision of S2-2003985_R03. Approved Approved
8.3 S2-2004011 P-CR Approval 23.748: KI #3, New Solution: Network Information delivery from NG-RAN to EAS via User Plane . Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2004431 LaeYoung (LGE) comments.
Jicheol Lee (Samsung) comments.
Magnus H (Ericsson): comments
Changhong (Intel) comments.
Laurent (Nokia) comments and provides r01.
Changhong (Intel) provides r02.
Laurent (Nokia) provides r03.
==== Ph1 Revisions Deadline ====
Jicheol Lee (Samsung) objects this pCR. (or merged to S2-2004119)
Changhong (Intel) proposes to merge this paper into S2-2004078.
==== Ph1 Final Deadline ====
Laurent (Nokia) answers that it is different from S2-2004119 as information is sent in band on N6 and it is an objection without a previous corresponding comment
Laurent (Nokia) answers that it is an objection without a previous corresponding comment; Sending a proposal for merging after the revision deadline does not allow to do the merge
==== Close of meeting Ph1 ====
Merged
8.3 S2-2004070 P-CR Approval 23.748: KI#3, New Solution: Network Information Provisioning from NG-RAN to 5GC via User Plane. Intel Rel-17 . Merged into S2-2004432 LaeYoung (LGE) comments.
Changhong replies to LaeYoung comments and proposes to mark this paper 'merge into S2-2004119'.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2004078 P-CR Approval 23.748: KI #3, New Sol: QoS monitoring information exposure based on unstructured data transmission mechanism. CATT Rel-17 R01 agreed. Revised, merging S2-2004011, to S2-2004431 Magnus H (Ericsson): Suggest to merge with S2-2003771
Changhong (Intel) provides r01.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004431 P-CR Approval 23.748: KI #3, New Sol: QoS monitoring information exposure based on unstructured data transmission mechanism. CATT Rel-17 Revision of S2-2004078_R01, merging S2-2004011. Approved Approved
8.3 S2-2004119 P-CR Approval 23.748: Solution for the KI#3: Network Information Provisioning to EAS with low latency. Huawei, HiSilicon Rel-17 R03 agreed. Revised, merging S2-2004070, to S2-2004432 LaeYoung (LGE) provides r01.
Laurent (Nokia) provides r02 and comments
Magnus H (Ericsson): provides r3
Hui Ni(Huawei) responses.
==== Ph1 Revisions Deadline ====
Hui Ni(Huawei) prefers to r02.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004432 P-CR Approval 23.748: Solution for the KI#3: Network Information Provisioning to EAS with low latency. Huawei, HiSilicon Rel-17 Revision of S2-2004119_R03, merging S2-2004070. Approved Approved
8.3 S2-2004117 P-CR Approval 23.748: DNS based EAS discovery supporting session breakout. Huawei, Hisilicon, Motorola Mobility, Lenovo, NTT Docomo, Ericsson? Intel? Nokia? Futurewei? ... Rel-17 Confirm Sources!. R10 agreed. Revised, merging S2-2003552, to S2-2004433 Hui Ni (Huawei) provides rev01 according to pre-meeting discussion.
Laurent (Nokia) provides rev02.
Riccardo (NTT DOCOMO) provides rev03.
Changhong (Intel) provides rev04.
Zhuoyun (Tencent) provides rev05.
John (Futurewei) provides r06.
Tingfang Tang (Lenovo) provides r07.
Changhong (Intel) provides r08.
Riccardo (NTT DOCOMO) provides r09.
Hui Ni (Huawei) provides r10.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004433 P-CR Approval 23.748: DNS based EAS discovery supporting session breakout. Huawei, Motorola Mobility, Lenovo, NTT Docomo, Intel, Futurewei, ITRI, China Telecom Rel-17 Revision of S2-2004117_R10, merging S2-2003552. Approved Approved
8.3 - - - Solution to KI#5 - - Docs:=4 -
8.3 S2-2003738 P-CR Approval 23.748: KI #5, New Sol: Activating traffic routing towards Local DN per AF request by NRF providing new I-SMF information connected to the requested DNAI. Apple Rel-17 Merged into S2-2004435 Krisztian (Apple): S2-2003738 is merged into S2-2003916r01.
Xiaobo Yu (Alibaba) provides comments.
Laurent (Nokia): asks Krisztian do you withdraw 3738??
Laurent (Nokia): provides r01 In case it would not be withdrawn/merged
==== Ph1 Revisions Deadline ====
Krisztian (Apple): S2-2003738 is merged into S2-2003916 (as indicated in my previous reply).
Laurent (Nokia) as it is NOT clear that S2-2003738 has been withdrawn I objects to any revision of this Tdoc
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003811 P-CR Approval 23.748: KI#5, Sol#7, Update to resolve KI#5 activating the traffic routing per AF request. ZTE Rel-17 Merged into S2-2004435 Jinguo (ZTE) suggest to merge with 3916.
Laurent (Nokia): asks Jinguo do you withdraw 3738??
Laurent (Nokia): asks Jinguodo you withdraw 3738??
Laurent (Nokia): asks Jinguodo: do you withdraw 3811 as you suggested to merge with 3916??
Laurent (Nokia): provides r01 In case it would not be withdrawn/merged
==== Ph1 Revisions Deadline ====
Jinguo(ZTE) agree merged with 3916.
Laurent (Nokia) as it is NOT clear that S2-2003811 has been withdrawn I objects to any revision of this Tdoc
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.3 S2-2003916 P-CR Approval 23.748: KI #5, New Sol: Activating the traffic routing towards LDN per AF request. CATT, ZTE Rel-17 R04 agreed. Revised, merging S2-2003738 and S2-2003811, to S2-2004435 Krisztian (Apple) provides r01.
Xiaobo Yu (Alibaba) provides comments to 3916r1.
Jinguo (ZTE) response
Hyunsook (LGE) asks a question.
Jinguo(ZTE) response.
Hyunsook (LGE) provides a comment.
Jinguo(ZTE) provides r02
Fenqin(Huawei) Comments. .
Jinguo(ZTE) provide r03. .
Laurent (Nokia) provides r04
Jinguo (ZTE) provide r05 and r06.
==== Ph1 Revisions Deadline ====
Yuan (CATT) comments.
Laurent (Nokia) objects to any revision other than r04
Jinguo(ZTE) ok with r04
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.3 S2-2004435 P-CR Approval 23.748: KI #5, New Sol: Activating the traffic routing towards LDN per AF request. CATT, ZTE, Apple Rel-17 Revision of S2-2003916_R04, merging S2-2003738 and S2-2003811. Approved Approved
8.4 - - - Study on Enhancement of Network Slicing Phase 2 (FS_eNS_Ph2) - - Docs:=77 -
8.4 - - - LS and General Aspects - - Docs:=9 -
8.4 S2-2003518 LS In Action LS from SA WG5: LS on analysis of GSMA GST attributes SA WG5 (S5-197853) Revision of postponed S2-2002614 from S2-138E. Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2003626 LS In Action LS from GSMA 5GJA: Reply LS on NG.116 GST publication and cooperation with 3GPP SA WG2 GSMA 5GJA (5GJA12_121) (5GJA12_121) Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003533 LS In Action LS from GSMA 5GJA: LS reply to SA WG2 on PLMN Selection GSMA 5GJA (5GJA12_115r3) Revision of postponed S2-2002668 from S2-138E. Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2004316 LS In Action LS from SA WG1: LS on 5GC assisted cell selection for accessing network slice SA WG1 (S1-202264) Rel-17 Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2004323 LS In Information LS from SA WG1: reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN SA WG1 (S1-202294) Rel-17 Postponed
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2003555 LS In Action LS from RAN WG3: Response to 5GC assisted cell selection for accessing network slice RAN WG3 (R3-202558) Rel-17 Noted
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2004131 DISCUSSION Agreement General: Key Aspects of Solutions for Architectural Requirements. Huawei, HiSilicon Rel-17 Noted Alessio (Nokia) provides comments on the aim of this paper and provides r01
Sangsoo (Samsung) asks questions.
Tricci (ZTE) proposed to NOTE this PCR to defer the evaluation discussions until Aug.2020 eMeeting.
Fenqin(Huawei) proposed feedback
==== Ph1 Revisions Deadline ====
Tricci (ZTE) would like to Postpone or to NOTE this PCR.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003582 P-CR Approval 23.700-40: KI#1-8: Additions to Architectural Assumptions. Ericsson Rel-17 Noted Tricci So (ZTE) Objects this PCR.
Alessio(Nokia) Objects this PCR.
George Foti (Ericsson) provides responses. The pCR DOES NOT remove roaming support for network slicing.
It simply removes applying the current quotas while roaming. Roaming does not depend on counting. Current solutions for handling quotas while roaming are not based on any requirements. GSMA did not reach a decision yet.
Alessio(Nokia) provides responses. We need to enforce a quota per slice. This, in today's system, means supporting this quota irrespective of whether UEs in the slice are at home or roaming, as network slice is end to end concept. The solutions we have, have to work in roaming. What GSMA will do then (i.e. how they operate this) is not for us to discuss. GSMA uses 3GPP solutions for roaming. If there are no solutions GSMA cannot even wish to support roaming ??. We never waited for GSMA to define operation in roaming (like NG.113) to have solutions that support roaming. GSMA may provide additional requirements if the 3GPP solutions are not meeting all their requirements at some point.
George Foti (Ericsson) provides responses. Roaming works without quotas, and nothing breaks. Until GSMA provides a way to handle quotas while romaing, we can safely assume that quotas don't apply while roaming.
U have to show what breaks and how; rather than making generic statements. Roaming depends on roaming agreements and today don't include quotas. Until that changes we should not create anything ourselves.
Tricci S0 (ZTE) remained her objection of this PCR and provides responses.to Ericsson's comments.
Please allow me to repeat the reason for ZTE's objection to this PCR.
Unlike to the PLMN selection parameter, there is no 'formal' request from GSMA to 3GPP ask for 'no roaming support' for GSMA GST parameters study in this Rel-17 study. Therefore, there is no ground for individual company to suppress other individual company's proposal to provide roaming support for this study. Please kindly stop using this roaming argument, which has not been agreed and approved, to prohibit the progress of other companies' PCRs on this SA2#139E eMeeting. This is not a constructive way forwards for everyone. Thanks in advance for your kind considerations.
Fenqin (Huawei) provides comments.
Alessio(Nokia) this is non-sense, all parameters apply to a network slice and network slices are end to end. If so let's stop everything on slicing as WAS has not worked on roaming for slicing yet (BTW WAS is still working on some aspects of EPS roaming ?? ). Slicing is mandatory in the system so we shall not work on roaming and deprecate roaming since rel-15 specs. If this was true then also rate per slice is only in non-roaming and everything else. if while roaming there is no limitation and when in home PLMN there is a limitation then everyone will want to be always roaming ??. NOKIA sustains objection and would like operators to weigh in on the need to show how solutions support the roaming use case. If roaming use case is not supported by a solution Nokia will evaluate that as not acceptable. Also regarding 'If this is the requirement to HPLMN it seems some strange as the user does not occupy the resource from the HPLMN.' This is wrong: there is SMF and UPF in HPLMN in HR PDU sessions. And also users in a slice in roaming are likely to use HR PDU sessions.
Tricci So (ZTE) responded to Huawei's comments.
George (Ericsson) provides comments.
Sangsoo (Samsung) proposes to note this pCR.
Alessio(Nokia) agrees with Samsung
George (Ericsson) provides r01 adding DT as supporting company.
George (Ericsson) provides r02 remove DT.
Toon Norp (KPN) agrees that this pCR should be noted. 3GPP should at least study roaming solutions.
==== Ph1 Revisions Deadline ====
Tricci (ZTE) sustained objection against this PCR and will not accept any version.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003740 P-CR Approval 23.700-40: New KI: Service continuity across network slices . ZTE, Intel Rel-17 Noted Stefano Faccin (Qualcomm) Revision 01 enclosed
Hyunsook (LGE) objects this pCR.
Dieter (Deutsche Telekom) agrees with LGE, SA2 may align with RAN later.
Alessio (Nokia) provides objection as this paper would require a WID update first and we should not start to wok in parallel to RAN WGs.
Patrice (Huawei) asks for clarifications, and likely will object.
Patrice (Huawei) proposes to note this document.
Jinguo (ZTE) is fine to note this document.
==== Ph1 Revisions Deadline ====
Noted
8.4 - - - Key issue 1 related - - Docs:=14 -
8.4 S2-2003597 P-CR Approval 23.700-40: KI#1-#2, Solution #8 updates. Ericsson Rel-17 Approved Hoyeon (Samsung) asks a question for clarification.
Peter Hedman (Ericsson) provides reply.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2003624 P-CR Approval 23.700-40: KI#1 Sol#2: Update to Solution #2 Max number of UEs per Network Slice control at registration . NEC, Apple Rel-17 Revision of (unhandled) S2-2000317 fr4om S2#136AH. Revised to S2-2004570. Tricci So (ZTE) provided revision r01 enclosed.
George Foti (Ericsson) provided comments and questions for clarification.
Iskren (NEC) responds to comments and provides r02.
Iskren (NEC) answers questions from George Foti (Ericsson) and provides r03.
George (Ericsson) provides a response.
Srisakul (NTT DOCOMO) provides questions for clarification.
Tricci (ZTE) responded to NEC and provided version r04.
Iskren answers questions from Srisakul (NTT DOCOMO), George (Ericsson), Tricci (ZTE) and provides r05.
Iskren (NEC) answers Tricci (ZTE)
Jinguo (ZTE) provide comments
Gerald (Matrixx) provided comments.
Dan Wang(China Mobile) provided comments.
Iskren (NEC) responds to comments from Dan Wang(China Mobile), Gerald (Matrixx) and Jinguo (ZTE) and provides r06
Iskren (NEC) answers Jinguo (ZTE)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004570 P-CR Approval 23.700-40: KI#1 Sol#2: Update to Solution #2 Max number of UEs per Network Slice control at registration . NEC, Apple Rel-17 Revision of S2-2003624. Approved Approved
8.4 S2-2003742 P-CR Approval 23.700-40: KI#1,2,4,5, New Sol: Proactive Slice Quota Management in AMF. ZTE Rel-17 Revised to S2-2004571. Zhenhua (vivo) comments for clarification
Jinguo (ZTE) response.
Zhenhua (vivo) provide r01
Tricci So (ZTE) respond to Vivo r01
George Foti (Ericsson) provided comments and questions for clarification.
Jinguo(ZTE) response.
George Foti (Ericsson) provides additional comments.
Zhenhua (vivo) respond to Tricci
Jinguo (ZTE) respond to Zhenhua
Jinguo (ZTE) provides r02
Tricci So (ZTE) provided respond to Vivo.
George (Ericsson) object to r2, and provides additional comments
Gerald (Matrixx) provides QM and functional comments.
Zhenhua (vivo) reply
Jinguo (ZTE) thanks Zhenhua(vivo) for comments.
Jinguo(ZTE) provides r03
Fenqin (Huawei) provides comment and r04 version
Jinguo(ZTE) provides response and provide r05.
Srisakul (NTT DOCOMO) provides comment.
Jinguo(ZTE) provides r06.
Gerald (Matrixx) provided comment on r06..
Gerald (Matrixx) provided r07.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004571 P-CR Approval 23.700-40: KI#1,2,4,5, New Sol: Proactive Slice Quota Management in AMF. ZTE Rel-17 Revision of S2-2003742. Approved Approved
8.4 S2-2003775 P-CR Approval 23.700-40: KI#1 updated solution 6.3 On Integrity of counters. Nokia, Nokia Shanghai Bell, Telecom Italia Rel-17 Revised to S2-2004572. Hyunsook (LGE) provides comments
Alessio(Nokia) provides r01
George Foti (Ericsson) provided comments and questions for clarification.
Alessio(nokia) provides response
Gerald (Matrixx) provided comments.
Farooq (ATT) comments that this contribution does not address the fundamental question asked previously of this proposal which was not about the integrity of the database but rather about complete reliance on increment / decrement of a counter to ascertain a count with no ability to check on absolute count through the life of a slice. I had suggested in the past that perhaps an asynchronous synch up with OAM for absolute count be possible.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004572 P-CR Approval 23.700-40: KI#1 updated solution 6.3 On Integrity of counters. Nokia, Nokia Shanghai Bell, Telecom Italia Rel-17 Revision of S2-2003775. Approved Approved
8.4 S2-2003923 P-CR Approval 23.700-40: KI #1, New Sol: Registration via multiple access networks . Samsung Rel-17 Postponed Hyunsook (LGE) provides r01.
Jinuo(ZTE) provides comment.
Hyunsook (LGE) provides comments
George Foti (Ericsson) propose to Note the pCR given that GSMA did not decide on how to handle N3GPP.
Hoyeon (Samsung) provides comments
Iskren (NEC) provides comments.
George Foti (Ericsson) corrected the mismatch between the title pCR number.
Hoyeon (Samsung) replies to Hyunsook.
Hoyeon (Samsung) provides comments.
Alessio(Nokia) comments that we need not indication of preferred access type, we can just work out of these principles: if UE registers with the same AMF, the UE is counted once in the slice, if the UE registers over different PLMNs for different access types, the UE is counted twice (once per PLMN).
George (Ericsson) the pCR should be noted. GSMA did not address how to handle registrations via N3GPP and whether quotas applied there are separate from 3GPP access even for the same S-NSSAI subject to quota over 3GPP. Hence we can't decide in a vacuum. U can send an LS to GSMA for that very specific aspect U addressed in this case if U so desire.
Hoyeon (Samsung) replies to George. To be fair, GSMA didn't even indicate 3gpp access neither. We believe SA2 should care about non-3gpp access as much as we do for 3gpp access, especially, we're doing work for core network. I'm OK to send an LS to GSMA if you desire!
Hoyeon (Samsung) replies to Alessio. We think both approaches (registration basis vs. terminal basis) work and should be available for comparison.
Curt (Charter) agrees with Samsung that SA2 needs to care about N3GPP access as well especially when developing new feature from 5GC perspective.
George (Ericsson) provides a response. SA2 needs to care about N3GPP access if we know what GSMA wants. Please see LS S2-2001788. We will raise the issue with GSMA. These attributes are for verticals and they may not care about N3GPP as it wont apply to them. Postponing the issue is the right course of action.
Alessio(Nokia) We DO NOT think both approaches (registration basis vs. terminal basis) work and a UE should be counted once per PLMN/AMF. But provide rev02 to have further discussion.
George (Ericsson) proposes postponing the discussion until we get clarification from GSMA. For the record the current quotas apply only to3GPP access based on the LS from GSMA.
==== Ph1 Revisions Deadline ====
Hoyeon (Samsung) is OK with rev02 to have further discussion.
Hoyeon (Samsung) comments: The GSMA LS sent to SA2 (S2-2001788) is for KI#3 and KI#5 while the solution in this PCR is for KI#1.So, Ericsson comment 'For the record the current quotas apply only to3GPP access based on the LS from GSMA.' is not correct.
Hoyeon (Samsung) proposes to go with and approve r02 in this meeting.
Alessio(Nokia) agrees with Samsung. Also, 3GPP can work on this regardless as a solution has to be available considering the multiple registrations case.
Curt (Charter) agrees with Samsung as well. We can go with R02 from this meeting.
George (Ericsson) provides a response. Ericsson objects to r02. This again extends the scope of the solution while we don't have clear input from GSMA. Adding this preferred access indicator is coming from nowhere. Only the vertical can make such a decision. We need input from GSMA. We acknowledge that this is a gap that needs to be addressed before the study is over.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2004121 P-CR Approval 23.700-40: KI #1, New Sol: Using Back-off timer. Samsung, SK Telecom Rel-17 Revision of S2-2000686. Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 S2-2004129 P-CR Approval 23.700-40: KI #1, Sol #1: Updates to remove ENs . Huawei, HiSilicon, China Unicom, China Mobile Rel-17 Revision of S2-2000630. Approved George Foti (Ericsson) provided comments for clarification.
Fenqin (Huawei) provided feedback.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2003933 P-CR Approval 23.700-40: Update of Solution#4 for Key Issue #1. NTT DOCOMO, Motorola Mobility, Lenovo Rel-17 Revised to S2-2004573. George Foti (Ericsson) provided comments and questions for clarification.
Srisakul (NTT DOCOMO) clarified George's questions (Ericsson) and provided r01.
Fenqin (Huawei) ask questions for clarification.
Srisakul (NTT DOCOMO) responded to Fenqin and provided r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004573 P-CR Approval 23.700-40: Update of Solution#4 for Key Issue #1. NTT DOCOMO, Motorola Mobility, Lenovo Rel-17 Revision of S2-2003933. Approved Approved
8.4 S2-2004075 P-CR Approval 23.700-40: KI #1, 2&5, New Sol: Support of network slice quota control and enforcement. CATT Rel-17 Revised to S2-2004574. George Foti (Ericsson) provided comments and questions for clarification.
Gerald (Matrixx) provided comments.
Yunjing (CATT) clarifies and provides r01.
George Foti (Ericsson) provided additional comments and questions for clarification.
Yunjing (CATT) clarifies and provides r02.
Yunjing (CATT) clarifies and provides r03.
Yunjing (CATT) clarifies.
Gerald (Matrixx) provided comments for another revision.
==== Ph1 Revisions Deadline ====
Yunjing (CATT) proposes to go with r03 in this meeting.
Gerald (Matrixx) note the status.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004574 P-CR Approval 23.700-40: KI #1, 2&5, New Sol: Support of network slice quota control and enforcement. CATT Rel-17 Revision of S2-2004075. Approved Approved
8.4 - - - Key issue 2 related - - Docs:=8 -
8.4 S2-2003625 P-CR Approval 23.700-40: KI#2 Sol#10: Updates to Solution #10 Max number of PDU Sessions per Network Slice control . NEC, Apple Rel-17 Approved George Foti (Ericsson) provided comments and questions for clarification.
Iskren (NEC) answered questions from George (Ericsson).
George Foti (Ericsson) provide comments.
Iskren (NEC) answers comments from George Foti (Ericsson).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2004122 P-CR Approval 23.700-40: KI #2, Sol #11: Update to remove ENs. Samsung Rel-17 Approved George Foti (Ericsson) provided comments.
Sangsoo (Samsung) replies to George (Ericsson).
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2003776 P-CR Approval 23.700-40: KI#2 solution 6.6 update adding support of Multiple PCFs . Nokia, Nokia Shanghai Bell, Telecom Italia Rel-17 Approved George Foti (Ericsson) provided comments and questions for clarification.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2004130 P-CR Approval 23.700-40: KI#2, Sol#7: Updates to remove EN. Huawei, HiSilicon, China Unicom, China Mobile Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 S2-2003935 P-CR Approval 23.700-40: Update of Solution#5 for Key Issue #2. NTT DOCOMO, Motorola Mobility, Lenovo Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 S2-2003768 P-CR Approval 23.700-40: KI#2 New solution On support of fairness . Nokia, Nokia Shanghai Bell Rel-17 Noted George Foti (Ericsson) objects to this pCR as this is out scope of the KI.
Alessio(nokia) Asks why Ericsson believes providing fair usage among users when there is a constraint on number of PDU sessions is not in scope of KI..
Alessio(Nokia) responds: these aspects (prioritization of PDU sessions and limit of PDU sessions per UE/S-NSSAI) are not capabilities of the system so far so this contribution proposes to add these so we can add these as options in the toolbox.
George Foti (Ericsson) provides response. This session priority should be proposed outside the scope of this study. This is an option for U. There are more impacts from this than U are addressing anyway; charging; backward compatibility; may be subscription related issues, potential interaction with priority sessions, etc..
This is why the pCR has to be noted.
alessio (Nokia) provides response. We disagree , this is the only study in rel-17 where it makes sense to propose this enhancement in scope of KI#2
Fenqin(Huawei) Provide comments and r01.
George Foti (Ericsson) Ericsson objects to r1. Any solution must be network based using existing capabilities, such as ARP, probably extended.
Fenqin(Huawei) Provide comments.
George Foti (Ericsson) Ericsson provides a response. r01 has session priority as a solution. In addition the current KI has some hints so we don't need this added EN. What is missing is a network based proposal. This is why we object to r01.
Alessi(nokia) the action the operator can take when quota is exceeded is left unspecified in GSMA. So the operator can do many things including rejecting new PDU sessions but at same time asking all UEs to respect a maximum number of PDU sessions for the s-NSSAI. Note the Ue can already be provided a max number of PDU sessions per Ue by the network today. The Ue enforces this limit and the AMF can check this is respected. So can you agree that the note is note needed as already today we have a similar mechanism per UE 9here we just make it applicable at a finer granularity)
Jinguo(ZTE) Provide comments .
Fenqin(Huawei) Provide comments and suggest to NOTE this paper.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003924 P-CR Approval 23.700-40: KI #2, New Sol: Handover of a PDU session . Samsung Rel-17 Postponed George Foti (Ericsson) proposes to note the pCR since GSMA has not provided any handling for N3GPP so this is a premature solution.
Hoyeon (Samsung) don't agree with Ericsson comments.
George Foti (Ericsson) don't think the UE should be informed about when a quota has been reached.
Alessio(Nokia) comments 'George Foti (Ericsson) don't think the UE should be informed about when a quota has been reached. ' this is weird, the User /UE should have opportunity to adapt its behaviour upon reqching quota. Even, when a a quota is reached and network rejects, the cause code should say this is cause of quota limit ...
George (Ericsson) UE policies on handover should not be based on quotas and where the UE is not even aware if any exists, and for what S-NSSAI and what access.
Hoyeon (Samsung) replies to George (Ericsson). This is an interesting comment. All solutions including Ericsson solutions for this KI in the TR (Sol #5, #6, #7, #8, #9, #10 and #11) propose to use a new cause code.
George Foti (Ericsson) some wrong comments creeped in this thread. As stated before GSMA stated that these attributes apply only to 3GPP. It is not clear how to handle mobility aspects. We will discuss this in GSMA and after GSMA makes a statement we can handle this. So we prefer to postpone this pCR, i.e note this pCR.
Hoyeon (Samsung) asks George Foti (Ericsson) to provide a reference on his comment 'GSMA stated that these attributes apply only to 3GPP.' Otherwise, reason for objection from Ericsson is not valid.
George (Ericsson) provides a response. GSMA sent an LS to SA2 some time ago responding to SA2 question related to this.
George (Ericsson) provides a response. GSMA LS sent to SA2 (S2-2001788)
==== Ph1 Revisions Deadline ====
Hoyeon (Samsung) comments: The GSMA LS sent to SA2 (S2-2001788) is for KI#3 and KI#5 while the solution in this PCR is for KI#2. So, we consider objection from Ericsson is not valid at all.
Hoyeon (Samsung) proposes to go with and approve the original version in this meeting.
Alessio(Nokia) agrees with samsung. Regardless, 3GPP can work on this while GSMA figures out. If this was at all required.
George Foti (Ericsson) We are seeking input from GSMA on how to deal with handovers. Again, these are input attributes from verticals that may have different constraints; Samsung had an option to send an LS to GSMA. We would like this postponed. We acknowledge this as an issue to be addressed before the end of the study.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Postponed
8.4 S2-2004123 P-CR Approval 23.700-40: KI #2, New Sol: Service Selection for Enforcement. Samsung Rel-17 Noted George Foti (Ericsson) proposes to note this pCR since it is out scope of the KI.
Sangsoo (Samsung) replies to George (Ericsson).
Alessio(Nokia) agrees with Samsung that it is important to define the concept of priority among a UE PDU sessions when there are limitations imposed. Ericsson position is arbitrary as this is a component of the solution for enforcement of a PDU sessions# capping. The UE and network should be enable to decide on priority of a PDU session.
George (Ericsson) We prefer a network based session pre-emption solution using existing mechanisms potentially (e.g ARP) with extensions if need be. UE schemes are not OK for us.
Sangsoo (Samsung) provides r01 as per the comment from George (Ericsson).
George Foti (Ericsson) objects to r01. It essentially is a UE based solution. We are OK only with network based solution based on existing mechanisms that may need to be extended.
Sangsoo (Samsung) provides a clarification and asks a question to George (Ericsson).
Jinguo(ZTE) provides comment and question
George Foti (Ericsson) provides a response. This solution introduces a notion of service priority to make a decision. It is not clear what service priority is, who decides on it and how. We have an existing mechanism ARP, that can be extended for example. If it is not suitable than this needs to be explained. So what is proposed is incomplete at best for inclusion.
Sangsoo (Samsung) provides a reponse.
Sangsoo (Samsung) provides clarifications to ZTE (Jinguo).
ZTE (Jinguo).provides r03
==== Ph1 Revisions Deadline ====
George (Ericsson) objects to r03
Sangsoo (Samsung) proposes to go with r03 in this meeting.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 - - - Key issue 3 related - - Docs:=13 -
8.4 S2-2003739 P-CR Approval 23.700-40: KI #3 & KI#5: Update KI#3&5 to align with recent GSMA LS feedback. ZTE Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 S2-2003647 P-CR Approval 23.700-40: Solution for KI#3 and KI#5 on limitation of data rate per network slice . Ericsson Rel-17 Revised to S2-2004575. Haiyang (Huawei) provides r01.
Alessio (Nokia) objects to this solution as it unnecessarily imposes limited sessions AMBRs per PDU sessions and this is reduce for each additional PDU session added. Also adding all GBRs and session AMBR is inappropriate as also the GFBR allotted to GBR QoS flows will reduce further the session AMBRs. In practice this is summing non uniform things when all we need is to just enforce a per slice UE Maximum rate and not fragment the rate across PDU sessions. This is made even worse when this solution is applied across all UEs in a Network slice (KI#5)
Belen (Ericsson) accepts r01, and replies to Nokia´s.
Belen (Ericsson) kindly request for the second time for Nokia to substantiate their objection by pointing to the text in the P-CR that offends them. So far no text has been pointed out, thus not allowing for a corrective revision. As such Ericsson does not recognize Nokia objection as valid.
==== Ph1 Revisions Deadline ====
Alessio(Nokia) the problem is that the PCF can only assess if the total of the guaranteed rates per UE exceeds the slice MBR... that of course could be done. But then you still have the issue that the non GBR traffic cumulatively needs to be restricted in the RAN so a PCF based solution only does not work. That is why we believe this is not a working solution : how does the RAN know to limit the aggregate of SDFs to the slice MBR? This is the key. Can you explain this?
Belen (Ericsson) replies to Nokia late clarifications.
Belen (Ericsson) provides explanation about our solution.
Alessio(nokia) thanks for you late explanation. So we understand that you achieve per slice limitation by PCF allotting a session AMBR_any GFBRs per PDU session for all PDU sessions in a slice according to PCF policy up to the slice AMBR. To us this is suboptimal but we can certainly document this approach and then evaluate at the end.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004575 P-CR Approval 23.700-40: Solution for KI#3 and KI#5 on limitation of data rate per network slice . Ericsson Rel-17 Revision of S2-2003647. Approved Approved
8.4 S2-2003652 P-CR Approval 23.700-40: KI #3, New Sol: Limitation of data rate per network slice in UL and DL per UE without RAN involvement. Apple Rel-17 Revised to S2-2004576. Tricci So (ZTE) provided revision r01 enclosed.
Krisztian (Apple) provides r02.
Stefano Faccin (Qualcomm) supports ZTE addition of the note. However, we would like to asks for clarification on Apple rev. 02 where a new procedure has been added, as to what comments from other companies lead to Apple posting rev. 02 since the changes are unrelated to the only comment received.
Tricci So (ZTE) commented the latest r02 version.
Krisztian (Apple) responds to Stefano.
Krisztian (Apple) provides r03 to fix Figure 6.X.3.2-1 per Tricci's comment.
Jinguo (ZTE) provides questions.
Hoyeon (Samsung) provides r04.
Krisztian (Apple) provides r05.
Alessio(Nokia) comments: The AMF is not supposed to look into the PDU session QoS parameters. The entities that look into the SM information are the RAN and the SMF (which populates it), so this does not work 'the AMF shall maintain the latest actualUESliceAMBR, which is essentially the accumulated session AMBR across all the active PDU sessions (across all SMFs) associated with the same network slice per UE' without impacting the AMF beyond its current role. So we object to this solution.
Dieter (Deutsche Telekom) objects this solution as AMF would look into the SM information which violates MM/SM separation.
Krisztian (Apple) provides r06 to address comments by Nokia and DT. In r06, AMF is not involved in actualUESliceAMBR calculation.
Zhuoyi Chen (China Telecom) provides questions for GBR flows to be established
Krisztian (Apple) provides r07 to address Zhuoyi's question.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004576 P-CR Approval 23.700-40: KI #3, New Sol: Limitation of data rate per network slice in UL and DL per UE without RAN involvement. Apple Rel-17 Revision of S2-2003652. Approved Approved
8.4 S2-2003663 P-CR Approval 23.700-40: KI #3, New Sol: Limitation of data rate per network slice in UL and DL per UE based on RAN enforcement. Apple Rel-17 . Merged into S2-2004577 Zhenhua (vivo) comments for clarification
Jinguo (ZTE) comments for clarification
Alessio(Nokia) Comments: would it be possible for Apple to consider merging this paper into S2-2003769?
Jinguo(ZTE) Comments.
Alessio(Nokia) Comments on merger proposal by ZTE.
Haiyang (Huawei) supports the merger proposal from ZTE and comments.
Krisztian (Apple) supports the merge of S2-2003663 & S2-2003815 & S2-2003892 & S2-2003769 and use S2-2003892 as a baseline.
Haiyang (Huawei) proposes to 'merge' this pCR to S2-2003892 based on the discussion.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.4 S2-2003769 P-CR Approval 23.700-40: KI#3 New Solution On enforcement of UE MBR UL/DL per S-NSSAI. Nokia, Nokia Shanghai Bell Rel-17 . Merged into S2-2004577 Jinguo(ZTE) Comments.
Michelle Li (China Telecom) provide comments.
Haiyang (Huawei) proposes to 'merge' this pCR to S2-2003892 based on the discussion.
Alessio(Nokia) it is ok by us.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.4 S2-2003815 P-CR Approval 23.700-40: KI#3, new sol: data rate per slice per UE. ZTE Rel-17 . Merged into S2-2004577 Haiyang (Huawei) proposes to 'merge' this pCR to S2-2003892 based on the discussion.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.4 S2-2003892 P-CR Approval 23.700-40: KI#3, new Sol: Solution on limitation of data rate per Network Slice in UL and DL per UE. Huawei, HiSilicon Rel-17 Revised, merging S2-2003663, S2-2003769, to S2-2004577. and S2-2003815 and S2-2003769, to S2-2004577. Michelle Li (China Telecom) provide comments.
Haiyang (Huawei) provides r01 as a merger with S2-2003663, S2-2003769, and S2-2003815
Alessio(nokia) provides rev02.
Haiyang (Huawei) corrects the link of r02.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004577 P-CR Approval 23.700-40: KI#3, new Sol: Solution on limitation of data rate per Network Slice in UL and DL per UE. Huawei, HiSilicon, ZTE, Apple, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2003892, merging S2-2003663, S2-2003769 and S2-2003815. Approved Approved
8.4 S2-2003928 P-CR Approval 23.700-40: KI #3, New Sol: Data rate control per network slice per UE. Samsung, SK Telecom Rel-17 Noted Haiyang (Huawei) provides r01.
Michelle Li (China Telecom) provide comments.
Hoyeon (Samsung) is OK with r01.
Hoyeon (Samsung) replies to Michelle Li (China Telecom).
Jinguo(ZTE) comments
Hoyeon (Samsung) replies to Jinguo
Jinguo(ZTE) further comment.
Alessio(nokia) I received comments on the support of case of multiple PCFs in all solutions, how come we can accept any solutions that does not work if >1 SMF is used? I am afraid this is not going to fly as it is not guaranteed it is possible to have all the PDU sessions for a S-NSSAI in same SMF in all possible use cases and deployments.
Hoyeon (Samsung) relies to Michelle Li (China Telecom).
Hoyeon (Samsung) replies to Jinguo.
Hoyeon (Samsung) replies to Alessio. The solution allows having multiple SMFs for an S-NSSAI.
==== Ph1 Revisions Deadline ====
Alessio(nokia) we do not agree that enforcement of Slice maximum bit rate UL/DL can only work if wee allocate a single SMF for a UE as it means all DNNs for a slice need to work on same SMF for a UE and this creates unnecessary constraint on deployments (as when this is enabled for a slice all SMFs in the slice need to support all DNNs of the slice). So for this meeting we have to object to this document. Please provide a solution that allows deployment flexibility
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2004009 P-CR Approval 23.700-40: Solution for KI#3 on limitation of data rate per network slice in UL and DL per UE. China Telecom Rel-17 Approved Jinguo(ZTE) Comments.
Michelle Li(China Telecom) Comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Approved
8.4 S2-2004076 P-CR Approval 23.700-40: KI #3, New Sol: UE-Slice-AMBR support based on UE-AMBR control and notification control mechanism. CATT Rel-17 Noted Michelle Li (China Telecom) provide comments.
Yunjing (CATT) clarifies.
Jinguo(ZTE) comments and propose to merge with S2-2003892 .
Yunjing(CATT) clarifies and ok to merge the first part with S2-2003892.
Yunjing (CATT) provides r01 to merge first part to S2-2003892.
Srisakul (NTT DOCOMO) removes his comments as it is sent on the wrong Tdoc number. Sorry.
==== Ph1 Revisions Deadline ====
Alessio(Nokia) objects to solution: This solution seems not to address the KI: the KI is about rate limiting the UE, this seems to provide a method to guarantee a rate to the UE by notifying when it cannot be fulfilled.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 - - - Key issue 4 related - - Docs:=2 -
8.4 S2-2003628 P-CR Approval 23.700-40: KI#4 New Sol#X: Network slice quota event notification. NEC Rel-17 Revised to S2-2004578. George Foti (Ericsson) provided comments for clarification.
Hyunsook (LGE) provides comments
George Foti (Ericsson) asking a question.
Iskren (NEC) answers questions from George (Ericsson) and Hyunsook (LGE).
George Foti (Ericsson) provide comment. Why would this apply to O&M and NWDAF based solutions This is redundant.
Iskren (NEC) responds to comments from George Foti (Ericsson).
Gerald (Matrixx) provided comments.
Iskren answers questions from Gerald (Matrixx) and provides r01
Iskren responds to comments from Gerald (Matrixx)
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004578 P-CR Approval 23.700-40: KI#4 New Sol#X: Network slice quota event notification. NEC Rel-17 Revision of S2-2003628. Approved Approved
8.4 - - - Key issue 5 related - - Docs:=2 -
8.4 S2-2004077 P-CR Approval 23.700-40: KI #5, New Sol: UE-Slice-AMBR adjustment to meet the limitation of data rate per Network Slice. CATT Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 S2-2004133 P-CR Approval 23.700-40: KI#5, New Solution: Slice data rate enforcement and dynamic adjustment Huawei, HiSilicon Rel-17 Approved
==== Ph1 Revisions Deadline ====
Approved
8.4 - - - Key issue 6 related - - Docs:=6 -
8.4 S2-2003596 P-CR Approval 23.700-40: Key Issue #6 new Solution: Network controlled enforcement of simultaneous usage of network slices based on user preference. Ericsson Rel-17 Revised to S2-2004581. Tricci So (ZTE) provided revision r01 enclosed.
Stefano Faccin (Qualcomm) provided revision r02.
Patrice (Huawei) comments and provides an initial revision 3.
Peter Hedman (Ericsson) provides comments.
Patrice (Huawei)continues the discussion.
Alessio (Nokia) provides comment: the goal we have to achieve is to just allow an operator to configure in subscription what slices can be allowed at same time based on customer policy. This is for instance a corporate requirement when they have say N subscribers and they want them to avoid using slice A if slice B is in use and viceversa. That is all. It is a policy in UDM so OAM configures this in UDM. Then aMF will tell the UE this policy so it avoid registering for non-permitted configs and waste signalling by trial and error. I know it describe our solution but that is all there is to it for this rather undemanding feature. Not sure why in 3GPP we get into endless loops to avoid simple solutions.
Patrice (Huawei) comments to Nokia (Alessio) that Alessio describes his solution, nothing more. That does not make it the objective of KI#6.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004581 P-CR Approval 23.700-40: Key Issue #6 new Solution: Network controlled enforcement of simultaneous usage of network slices based on user preference. Ericsson Rel-17 Revision of S2-2003596. Approved Approved
8.4 S2-2003630 P-CR Approval 23.700-40: KI#6 New Sol#X: Network slices simultaneous usage incompatibility support. NEC Rel-17 Revised to S2-2004582. Patrice (Huawei) comments and provides r01.
Alessio (Nokia) comments
Iskren (NEC) responds to Patrice (Huawei) and provides r02.
Iskren (NEC) answers Alessio (Nokia)
Stefano Faccin (Qualcomm) provides revision 02
Iskren (NEC) agrees with r03 provided by Stefano Faccin (Qualcomm).
Alessio(Nokia) we have already objected to this P-CR but I wonder one thing: why do we need to allow a UE to register for incompatible slices and then only allow PDU sessions establishment for slices that are compatible? Why would a Ue want to remain registered for slices it cannot possible us as soon as one PDU session is established for the an incompatible slice? Also if the Ue is given info on incompatibility why would the UE want to nonetheless register for incompatible sets?
Iskren (NEC) responds to Alessio(Nokia)
The network slice simultaneous usage incompatibility attribute is already there defined by GSMA and required by KI#6. We have two options:
1) Not provide some of the UE subscribed S-NSSAI to the UE to avoid incompatibility and this way deprive the UE from services on these network slices (Nokia approach); or
2) Provide all requested by the UE S-NSSAI and control the simultaneous usage incompatibility in the UE and the network as required by the KI and thus allow the UE a possibility to access services that are denied in option 1 (NEC approach).
Anyway, Alessio's objection should not stand not only because it is technically incorrect but it is also of an evaluation type.
Patrice (Huawei) comments, provides r04.
Iskren (NEC) agrees with r04 provided by Patrice (Huawei) and provides r05 with an editorial update only.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004582 P-CR Approval 23.700-40: KI#6 New Sol#X: Network slices simultaneous usage incompatibility support. NEC Rel-17 Revision of S2-2003630. Approved Approved
8.4 S2-2003787 P-CR Approval 23.700-40: KI#6 New solution on Simultaneous use of the network slice . Nokia, Nokia Shanghai Bell, Telecom Italia, T-Mobile USA Rel-17 Revised to S2-2004583. Patrice (Huawei) comments and provides r01.
Iskren (NEC) provides comments.
Alessio(Nokia) responds to comment. The UE uses a network slice when it registers with it. That is why our solution impacts the registration procedure. The allowed s-NSSAI shall not include slices that in the UE subscription are marked to belong to incompatible classes. This is nothing to do with what AMFs supports or not. These are policies set by the slices customer. This also ensures as side effect that the moment PDU sessions are set up, they are in compatible slices.
Iskren (NEC) provides comments.
I have concern with this solution. I do not think it follows to the requirements in the KI#6. The main KI#6 requirement is: How to enforce the constraints related to simultaneous usage of Network Slices in the UE and in the network, both in roaming and non-roaming scenarios. This requirement is clearly about network slice simultaneous usage. The question is when do you use the network slice, just being registered for it or when the UE requests a service on it? KI#6 is different from the Rel-16 discussions we had about the mutual inconclusive network slices for which the main bases was that the UE shall not be assigned allowed S-NSSAIs that are not supported by the same AMF. The new GSMA attribute for network slice simultaneous usage incompatibility in KI#6 is a further development from the mutually exclusive network slices. It is more about isolation for some network slices (as mentioned in the GST spec) for which higher security is required, that is why KI#6 says simultaneous usage control required in the UE and in the network so that these higher security network slices are not used at the same time with other network slices. In this Nokia solution the network provides to the UE only network slices that can be used simultaneously and there is no need for control, neither in the UE nor in the network. And most importantly, the network slices that would require isolation (i.e. higher security) would not be provided to the UE as allowed S-NSSAIs as they are likely to be incompatible for simultaneous use with the rest of the network slices! So, the UE will not have access to these network slices. I believe this Nokia solution cancels KI#6 rather than provides a solution for it.
Patrice (Huawei) comments, clarifies that he objects to r0.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004583 P-CR Approval 23.700-40: KI#6 New solution on Simultaneous use of the network slice . Nokia, Nokia Shanghai Bell, Telecom Italia, T-Mobile USA Rel-17 Revision of S2-2003787. Approved Approved
8.4 - - - Key issue 7 related - - Docs:=18 -
8.4 S2-2003646 P-CR Approval 23.700-40: Key Issue #7 architecture assumptions and requirements. Ericsson, Telecom Italia, Nokia; Nokia Shanghai-Bell, Qualcomm Incorporated, T-Mobile USA Rel-17 Noted Tricci So (ZTE) provided r01 revision
Hoyeon (Samsung) don't agree with r01.
Patrice (Huawei) comments and does not agree with r01, may provide a revision later depending on the answers.
Alessio(nokia) comments that it is not possible to have random support of S-NSSAI in TA: cell selection happens inside the TA using the TAC not the band as criterion, a UE expects uniform network slicing behaviour from cells advertising a TAC. If some services of a S-NSSAI are not available in a cell advertising a TAC where the Ue is expecting the S-NSSAI to be available (but it is not if we allow the exception!) TAC then it means that when the UE is in idle mode the UE cannot be paged on those cells for PDU sessions related to S-NSSAIs not supported in that cell. However the network does not know in which cell the UE is in idle mode... so this is utter mess.
Can companies that want to destroy the propose system operation justify the benefit? What is the concept of S-NSSAI support if it is random in a TA?
Peter Hedman (Ericsson) provides comments.
Alessio(Nokia): 'On the different understanding of whether we can deploy cells with different support wrt S-NSSAIs having the same TAI and still comply with the assumption, I'd support that we get this clarified from RAN WGs.' Well I assume we also have a say as RAN WGs built the RAN based on SA2 requirements on this ??... but more importantly there is a bit of a worry as I would expect the code for Rel-15 UEs cell selection should be working ad AFAIK cells are selected if the TAC they advertise marches one in the TAI list... and radio condition is good and of course any RF selection priorities. But the RF selection in idle mode is based on the ALLOWED NSSAIS and not on the YET to be allowed NSSAI. The RF selection after S-NSSAI is allowed is not the theme of this KI. The theme of this KI was selection before a S-NSSAI is allowed as the issue was a S-NSSAI may never be allowed if the selection steers the UE away from the cells / bands and ultimately TACs where this can be allowed.. so having this discussion with RAN is odd in the context of this KI that is dealing with what to do before a S-NSSAI is allowed.
Patrice (Huawei) answers Peter's comment.
Alessio (Nokia) provides r02 and comment on r01, saying the note is not needed unless it is changed to be positive that the AMF assumes all cells in the TA are assumed to support the S-NSSAIS that are advertised to be supported in the TA.
Patrice (Huawei) can accept the original version for now, and objects both r01 and r02.
Alessio(Nokia). Nokia ok with original text BUT asks clarifications on this 'But the added text by Alessio goes way beyond what is necessary to provide such availability and is not already something required in Rel-15/16 to make it work.' As if some cells at random in a TA do not support a S-NSSAI the system expects to be supported in the TA, we are in uncharted territory and we need FASMO cRs in rel-15/16.
==== Ph1 Revisions Deadline ====
Hoyeon (Samsung) can accept the original version, and objects both r01 and r02.
Tricci (ZTE) accepts only r01.
Alessio(Nokia) Tricci (ZTE) says 'Today Rel-15/16, 5GC is not aware of any cell configuration within the TA.' We agree, that is why all cells should support the same set of S-NSSAIs else the location of a Ue in idle mode should be known on a cell basis.
Alessio(Nokia) Nokia prefers to note all revisions as the assumption seems to have no meaning to push towards a solution type or another now that people seems to disagree on long standing principles of system operation. We will need rel-15/16 work on this. This is not even in this Study scope.
Peter Hedman (Ericsson) provides comments, we prefer to simply agree original version that is exactly what we have in current specs. Then we need an LS to RAN WGs, but that will need to be sent from next meeting.
Alessio(nokia) we can live with the original version which we consigned of course. But the handling of disagreements should not result in necessarily agreeing SA2 does not know how the system works till rel-15/16 and we need to ask RAN WGs how it works by LS. I provided eloquent 38.300 text that should put any doubt to rest. The main reason why we signal support per TA for many features is to make sure they work in idle mode without knowing in which cell the UE is. This principle shall not be challenged or we will have to go back to drawing board and do may FASMO CRs. ALSO most importantly there is no reason to create this turmoil in scope of a KI to support an attribute to make sure a slice supports at least a certain band (it is not said this means the slice shall not be supported in other bands).
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003595 P-CR Approval 23.700-40: Key Issue #7 New Solution: Support of radio spectrum attribute by configuration. Ericsson Rel-17 Noted Stefano Faccin (Qualcomm) Revision 01 enclosed
Alessio(nokia) Objects to this solution being included in the TR as manual and or a-priori UE configuration per PLMN is not something we would want to see as solution
Patrice (Huawei) asks questions for clarification and may provide an update later accordingly.
Alessio(Nokia) main reason of objection is that there is an embedded assumption there is a static configuration of the UE... even operated manually by the user. This is unacceptable as we have removed from spec any such requirements for network slicing to operate based on the famous comment by Haris the only time he attended slicing in study phase as Stefano was missing ??. Not that if the PLMN decides to change operating bands of a s-NSSAI all of a sudden you may have UEs stranded! This is not evaluation, it is a concept level objection on technical soundness. So this objection is sustained!
Peter Hedman (Ericsson) provides comments.
Alessio(Nokia) If the terminal is restricted in terms of frequencies it supports, it needs not be configured to restrict the bands as it is restricted, so your manual config of the UE is not required as it is a generic UE limitation. So the UE will only select the bands it can use. It is like a radio capability restriction. This means it is the network then that is required to support these bands in the slice. Which is what GSMA was requesting and the essence of the attribute. So I think that the solution to support restricted UEs then does not rely on configuring the UE, but in deploying the slice in bands the UE supports. For this reason we sustain the objection to this Cr that has got the issue backwards it seems.
Guillaume (MediaTek) proposes to note the contribution.
Patrice (Huawei) comments further and welcomes a revision from the author that addresses the comment.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003598 P-CR Approval 23.700-40: Key Issue #7 New Solution: CN assisted radio spectrum selection. Ericsson Rel-17 Revised to S2-2004521. Stefano Faccin (Qualcomm) Revision 01 enclosed
Tricci So (ZTE) Revision 02 enclosed
Alessio(Nokia) provides comment to all revisions: the use case is too narrow and relies on UE requesting always the default S-NSSAI to trigger the solution into action.
Patrice (Huawei) comments and provides r03.
Alessio(Nokia) this solution is going nowhere and it gets worse with revisions. Nokia objects to any revision of this paper.
Peter Hedman (Ericsson) provides comments and r04
Alessio (Nokia) provides comments and r04 ''The Allowed NSSAI has not been changed, but the fact that the default Subscribed S-NSSAI has been used as the Allowed NSSAI is taken as a trigger for AMF Policy Update towards the PCF,' The issue here is that if the UE had indicated a requested NSSAI including a non-default S-NSSAI that is supported in the TA, in addition to this 'vertical S-NSSAI' (not sure now all of a sudden we have vertical S-NSSAIs , this is undefined concept), nothing would happen, the solution does not work. So we cannot add to a TR a solution that does not work in general but only for some configurations. Can you make it generic? If so we lift objection.
Peter Hedman (Ericsson) provides r05
Alessio(Nokia) provides r06
Peter Hedman (Ericsson) provides comments and r07.
Alessio(nokia) objects to r07 because the issue of having sets of s-NSSAIs that are incompatible as sets but a subset of these sets is compatible creates sort of situation that is not decidable by the network without knowing what the UE eventually really wants. This is captured in r06.
==== Ph1 Revisions Deadline ====
Peter Hedman (Ericsson) provide comments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004521 P-CR Approval 23.700-40: Key Issue #7 New Solution: CN assisted radio spectrum selection. Ericsson Rel-17 Revision of S2-2003598. Approved Approved
8.4 S2-2003629 P-CR Approval 23.700-40: KI#7 New Sol#X: Steering the UE to a network slice in a different frequency band. NEC Rel-17 Revised to S2-2004587. Stefano Faccin (Qualcomm) Revision 01 enclosed
Iskren (NEC) provides r02.
Zhenhua (vivo) comments for clarification
Dieter (Deutsche Telekom) comments.
Iskren (NEC) answers comments from Zhenhua (Vivo) and provides r03.
Hoyeon (Samsung) provides r04.
Alessio(Nokia) object to this CR as it contains a violation of the rule the allowed NSSAI only contains S-NSSAIs that work on all cells of the RA/TA and also wrongly assumes this solution works with legacy UEs. The behavior to establish a PDU session and tearing it down when there is no data to send is not defined today as the PDU session can be kept to receive MT data.
Iskren (NEC) responds to Alessio(Nokia) and Hoyeon (Samsung) comments.
Alessio(Nokia) comments: the reason of our objection, which we sustain, is that now the assignment of TACs will not have to take into account the S-NSSAIs supported. If so, this will impede the proper operation of rel-16 and rel-15 UEs in the network but also require now to report to the CN with cell basis granularity the support of S-NSSAIs. Which is a huge impact in the CN and in the RAN. The advertisement of a TAC in the RA will no longer mean that the S-NSSAIs in the allowed NSSAI are supported in the cell. This disrupts Rel-15/16 UEs cell selection in idle mode. So we sustain objection to all papers that cause this disruption.
Patrice (Huawei) has concerns, comments, provides r05.
Iskren(NEC) answers comment from Alessio (Nokia). We are not evaluating the solutions yet.
Iskren (NEC) responds to Patrice (Huawei). Iskren agrees with r05 provided by Patrice (Huawei).
Stefano Faccin (Qualcomm) provides revision 06 and comments.
Iskren(NEC) aggress with r06 provided by Stefano Faccin (Qualcomm). Thanks Stefano.
The assumption in the solution now reads: The UE is allocated Allowed NSSAI which can contain S-NSSAIs supported in different frequency bands, however all S-NSSAIs are supported in all Tracking Areas or the Registration Area.
So, the reason for objection 'cell basis granularity of S-NSSAIs support that is against the current network slice agreements' from Alessio does not stand as the solution assumption is all allowed S-NSSAI are supported in all TAs or the Registration Area.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004587 P-CR Approval 23.700-40: KI#7 New Sol#X: Steering the UE to a network slice in a different frequency band. NEC Rel-17 Revision of S2-2003629. Approved Approved
8.4 S2-2003732 P-CR Approval 23.700-40: KI #7, New Sol: Including supported operating frequency bands in Allowed NSSAI. Apple Rel-17 Noted Stefano Faccin (Qualcomm) Revision 01 enclosed
Iskren (NEC) provides r02.
Stefano Faccin (Qualcomm) adds questions and expresses concerns about the missing details.
Hoyeon (Samsung) provides r03 and ask a question.
Krisztian (Apple) provides r04 and responds to comments.
Alessio(Nokia) Objects to this paper as it is not in line with the principle all S-NSSAIs in the allowed NSSAI work in all the cells in the TA,
Patrice (Huawei) shares concerns, comments, provides update r05.
Peter Hedman (Ericsson) provides comments.
Krisztian provides r06 to address Peter's comment and responds to Alessio.
Stefano Faccin (Qualcomm) Revision 07 enclosed. After the details being added, it is clear this solution is for idle mode only and must be classified as such.
Alessio(Nokia) provides comment: if the current system supports this mix of incompatible bands in a TA for the allowed NSSAI, why are we seeing a flurry of solutions attempting (and IMHO failing) to make it work? It is the first time that we see tens of solutions in a study that people claim is supported by the current system assumptions. Also the main objection is that this has nothing to do with support of the GSMA parameter that defines the bands a S-NSSAI shall at least support. So we have technical and procedural concerns we sustain.
Guillaume (MediaTek) provides comments, sharing many of the concerns raised by Nokia, Huawei, Qualcomm.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003733 P-CR Approval 23.700-40: KI #7, New Sol: AMF assistance to NG-RAN during PDU Session establishment procedure. Apple Rel-17 Noted Stefano Faccin (Qualcomm) Revision 01 enclosed
Dieter (Deutsche Telekom) comments
Krisztian (Apple) provides r02.
Dieter (Deutsche Telekom) comments.
Alessio(nokia) provides comment: how does this solution work if the UE establishes a PDU session for all the S-NSSAI it is registered with? Is this a disallowed behaviour by this solution?
Alessio(Nokia) if the S-NSSAIs have conflicting band requirements then the solution does not work unless a new behaviour is introduced invoilvin sequential establishment and tear down of PDU sessions that may have profound system signalling and application behabiour. If so we object to the solution.
Patrice (Huawei) asks questions, comments, and provides r03.
Krisztian (Apple) provides r04 addressing comments by Dieter. Response to Nokia's concern is provided as part of S2-2003732 email thread. ENs added in r03 by Patrice also document Nokia's concerns.
Stefano Faccin (Qualcomm) Qualcomm objects to the solution. After the details added, Qualcomm is not convinced that the solution can work in the generic case of multiple PDU sessions with S-NSSAIs requiring different bands, since the decision to prioritize one S-NSSAI or the other needs to be taken in the CN, not the NG-RAN, and the solution written as is moves such decision to the NG-RAN.
==== Ph1 Revisions Deadline ====
Krisztian (Apple) responds to Stefano.
Stefano Faccin (Qualcomm) replies to comments.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003741 P-CR Approval 23.700-40: KI#7, New Sol: Steering the UE towards the 5G-AN during PDU session Establishment . ZTE Rel-17 Noted Hoyeon (Samsung) provides r01.
Alessio(Nokia) provides objection 'the KI is about 'Today, the UE would have to attempt to select 5G-AN with no awareness as to whether a 5G-AN support a S-NSSAI till the S-NSSAI is allowed. We need to study whether and how to support S-NSSAI-aware 5G-AN selection.' It implies a selection the UE does in idle mode. This is the scope of the KI. The green highlight implies that once the Ue has aan allowed NSSAI the selection is trivial as the TAC will assisted the selection (if it belonging to TAI LIST, SELECT CELL ELSE, SELECT only if there is no other suitable cell in TAI LIST and PERFORM a Registration request in this new TAI)
So, we object to considering any other aspect than cell selection in idle mode. Consistently we object to this PCR and any other that does not stick to the aspect of cell selection in idle mode when the UE needs to request a S-NSSAI not yet in the allowed NSSAI.
Patrice (Huawei) comments, provides r02.
Peter Hedman (Ericsson) provides r03
Tricci (ZTE) responded to Samsung, Nokia, Huawei and Ericsson, and proposed revision r04.
Jinguo (ZTE) reponse to peter(Ericsson)
Stefano Faccin (Qualcomm) provides rev.05
Tricci (ZTE) thank you and accept rev.05 from Qualcomm
Patrice (Huawei) answers to reply from ZTE, provides r06, objects to r00,r01,r04,r05 that do not address his concerns.
Alessio(nokia) indeed the assumption all S-NSSAIs in allowed NSSAI can be used concurrently as Patrizio says has been there and not sure we can ever remove. If an operator wants to allow s-NSSAIs at same time that use different bands for user plane, I think some form of CA/Dual connectivity needs to be used but this is fully a RAN matter. If the UE uses one band at a time, only the S-NSSAIs in that band can be allowed. That is why we sustain objection until, there is an agreement to lift the assumption on allowed NSSAI. Not sure why at this meeting there is a flourishing of this new way to form the Allowed NSSAI. Note that this is also outside the goal of the KI that is to select a band before the S-NSSAI is allowed.
Tricci (ZTE) accepts HW's r06 with the expectation that the opposite view is also considered, i.e. it is FFS whether it is acceptable to limit the Allowed NSSAI contains ONLY S-NSSAIs that the UE can use concurrently.
Tricci (ZTE) rejects Nokia's objection and comment which are based on personal opinion and preference. This is not a constructive way forward to progress the work without providing the concrete proof from today specifications to justify his claims.
==== Ph1 Revisions Deadline ====
Alessio( Nokia) objection is sustained: Our objection is based on the solid long standing assumption documented also in RAN specs: 38.300 section 16.

Slice Availability
- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

So this goes against the above. Also the KI#7 GSMA parameter is targeting to support AT least a certain band in a slice, not to not support a certain slice in a TA. This is more a issue to be discussed if someone had rel-15/16 CRs of CAT-F nature.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003793 P-CR Approval 23.700-40: KI #7, New Sol: Compatibility of S-NSSAIs operating frequency bands with UE Radio Capabilities. Qualcomm Incorporated Rel-17 Noted Tricci So (ZTE) asked for clarifications.
Alessio(Nokia) provides comments: we assume the UE that has a S-NSSAI allowed in a TAI/RA can use the S-NSSAI as long as the RAN can serve it in the RA in its supported bands. But all bands advertising the TAIs in the TAI list support the S-NSSAIs in the Allowed NSSAI. If the UE cannot find any more cells in the RA in its supported bands, it loses service or it finds a TAI outside the RA in its supported bands... and what this TA supports is business as usual and the UE finds it out when it does a registration (and upon connected mode mobility some PDU sessions may also be dropped etc if a certain s-NSSAI is no longer supported).
Stefano Faccin (Qualcomm) provides clarifications and responses, and revision 01 to implement those clarifications.
Alessio (Nokia) provides comments

S2-2003646
'The following 5G System architectural principle shall be maintained:
all S-NSSAIs of the Allowed NSSAI for a Registration Area are available in all Tracking Areas of the Registration Area.'
this means clearly that in each and every TA of the RA all S-NSSAIs in the allowed NSSAI are available.

This means you pick one of the TAIs at random in the TAI list, all the S-NSSAIs in the Allowed NSSAI work there. Irrespective a TAI is made of one cell or 3000 cells. Of one band or 20 bands. They work inside every cell and every band supported by the TA.

So nothing has changed from rel-15 and we have the paper above to reaffirm that.
Stefano Faccin (Qualcomm) replies to Nokia's comments. Qualcomm disagrees that the statement quoted by Nokia should be interpreted as 'all S-NSSAIs of the Allowed NSSAI for a Registration Area are available in all cells of all Tracking Areas of the Registration Area'. A TA may have two cells on different frequency bands, with S-NSSAI1 on cell1, and S-NSSAI2 on cell2, both still available in the TA.
Mike (Convida Wireless) agrees with Qualcomm's comments. There is nothing in our specifications that says 'all S-NSSAIs of the Allowed NSSAI for a Registration Area are available in all cells of all Tracking Areas of the Registration Area'.
Tricci So (ZTE) agrees with Qualcomm's understanding and interpretation of the frequency bands support for the given TA within the Allowed NSSAI.
Farooq (AT&T) agrees with Qualcomm. It's the same discussion as S2-2004195 where Nokia has an opinion but no documentation to back it.
Hoyeon (Samsung) provides comments.
Alessio(Nokia) provides comment regarding 'it is very common to have multiple cells on different frequency bands within a TA.' Yes, true, but we assume that these support the same s-NSSAIs. Else rel-15 UE does not work. Rel-16 UE does not work. A network deployed like that will automatically mean legacy UEs do not work. We sustain objection to changing the rel-15 and 16 assumption and also that was the spirit of the architectural assumption paper we all cosigned.
Hyunsook (LG) provides comments.
Iskren (NEC) provides comments
Peter Hedman (Ericsson) provides comments.
Alessio(nokia) provides this basic comment:
* A tracking area is a set of cells. These cells advertise a certain TAC (tracking area code)
* If I says: something is available over a tracking area, it means all cells that comprise the tracking area support that thing. i.e. we have a set whose components support a fundamental property. Another property is that all these cells advertise the same tracking area code. So if a UE camps on a cell advertising that tracking area code, it shall be able to use that S-NSSAI.
* If I wanted to say anything different we would say: something is available in parts of a TA.
alessio (Nokia) if this is what the existing assumption is from rel-15, then all UEs work with this arrangement you describe, so we need not study or provide a solution for this. If they do not work it means the existing 5GS principle is not what you say. But then why did you cosign this to retain the existing principle:

The following 5G System architectural principle shall be maintained:
- all S-NSSAIs of the Allowed NSSAI for a Registration Area are available in all Tracking Areas of the Registration Area.



Note: a tracking area is defined by ALL the cells that advertise the same tracking area code, none excluded. When se way a S-NSSAI is supported by a TA, it means all the cells that advertise that TAC support the S-NSSAI. That is it. No alternative interpretation.
Alessio(nokia) the GSMA parameter indicates that the Network slice only supports certain bands. So we need to stick this this and not construe it is a GSMA requirement to have TAs that have non uniform support of S-NSSAIs. So nokia objects to anything that misconstrues the GSMA parameter to imply this. We object to any revision of this paper.
Alessio(nokia) comments that the example by LG clarifies the issue at hand. The issue highlighted for IMS applies to any other application that is relying on the PDU session to work in the RA.
Mike (Convida Wireless) provides comments. The architecture principle does not say that all cells in the TA must support the same slices. The example where the Rel-15/16 UE picks one cell at random in the TA and expects the Allowed NSSAI to work is not a valid example. The UE does not pick cells at random. In Rel-15/16, the RFSP index can be selected by the network such that the UE will not pick cells that does not support in the Allowed NSSAI.
Serge (T-Mobile USA) also agrees with Qualcomm's comments. T-Mobile believes slices can be deployed across different cells in different bands while being part of the same RA.
Patrice (Huawei) comments and provides r02.
Stefano Faccin (Qualcomm) comments and provides r03.
Stefano Faccin (Qualcomm) accepts Nokia's view, and asks for detailed explanation to how S2-2003793 'misconstrues the GSMA parameter to imply that TAs have non uniform support of S-NSSAIs', since we cannot find any text in the P-CR stating that. We kindly ask Nokia to point out such text, if it exists.
Stefano Faccin (Qualcomm) kindly request for the second time for Nokia to substantiate their objection by pointing to the text in the P-CR that offends them. So far no text has been pointed out, thus not allowing for a corrective revision. As such Qualcomm does not recognize Nokia objection as valid.
Patrice (Huawei) comments and is OK with r03.
Alessio(Nokia) provides for detailed explanation that S2-2003793 'implies that TAs have non uniform support of S-NSSAIs' as it states the lack of a certain band support means the Ue may not be able to use a certain S-NSSAI in a TA.
Stefano Faccin (Qualcomm) thanks Nokia for the explanation, but unfortunately can find only a personal opinion and not a factual explanation of the reason for objection. Please point to text in R15/R16 saying that the S-NSSAI needs to be available in every cell of every TA of the RA, and we will agree.
==== Ph1 Revisions Deadline ====
Alessio( Nokia) objection is sustained: Our objection is based on the solid long standing assumption documented also in RAN specs: 38.300 section 16.

Slice Availability
- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

So this PCR goes against the above. Also the KI#7 GSMA parameter is targeting to support at least a certain band in a slice, not to not support a certain slice in a TA. This PCR seems is more an issue to be discussed if someone had rel-15/16 CRs of CAT-F nature as they found out the assumptions are broken.
Stefano Faccin (Qualcomm) objection is still invalid. The P-CR does not challenge the text in 38.300, but cover the issue of the AMF inability to determine the UE radio capabilities when deciding the Allowed NSSAI. The rest is Nokia's interpretation not sustained by the text in the P-CR.
Alessio(NoKia) it is unnecessary to check UE capabilities before determining the allowed NSSAI. If this was necessary you would need a rel-15 CR. So we sustain the objection even more and suggest qualcomm writes suitable rel-15/16 CRs if they believe this is a problem. It is a personal opinion by qualcomm we need to check the UE capabilities to determine the allowed NSSAI.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003929 P-CR Approval 23.700-40: KI #7, New Sol: Reusing RFSP index mechanism . Samsung, SK Telecom Rel-17 Noted Tricci So (ZTE) provided revision r01.
Hoyeon (Samsung) asks a question to Tricci.
Tricci So (ZTE) Responded to Samsung's question for EN#3
Patrice (Huawei) comments and asks for clarification, and may provide a revision later.
Alessio(nokia). Comments and later may provide revision or object depending on answer
Hoyeon (Samsung) is OK with r01.
Hoyeon (Samsung) replies to Patrice.
Hoyeon (Samsung) replies to Alessio.
Patrice (Huawei) comments.
==== Ph1 Revisions Deadline ====
Alessio( Nokia) objection is sustained: Our objection is based on the solid long standing assumption documented also in RAN specs: 38.300 section 16.

Slice Availability
- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

So this PCR goes against the above. Also the KI#7 GSMA parameter is targeting to support at least a certain band in a slice, not to not support a certain slice in a TA. This PCR seems is more an issue to be discussed if someone had rel-15/16 CRs of CAT-F nature as they found out the assumptions are broken. This contribution in particular is not providing a deterministic behaviour in cell selection when a UE needs to register for a S-NSSAI.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003963 P-CR Approval 23.700-40: KI#7 new solution On selection of suitable cell for a S-NSSAI. Nokia, Nokia Shanghai Bell Rel-17 Noted Peter Hedman (Ericsson) provides comments.
Alessio (Nokia) responds to comment by Ericsson.
Patrice (Huawei) comments and provides an update r01.
Peter Hedman (Ericsson) objects to any rev using CAG for a specific slice.
Alessio(nokia) in fact we DO NOT advertise support of a Single s-NSSAI with the CAG, rather criteria for selection of cells that can support a bunch of s-NSSAI when these s=-NSSAI have no universal support. so in aPLMN we only need to advertise CAGs when some s-NSSAIs are only available in certain cells. Lots of s-NSSAIs can map to a CAG. A CAG here maps more to a band or a compatible set of band. So you have the wrong interpretation. In this light I hope you can lift the objection as this is a property of the cell, not of the slice.
Alessio(nokia)the CAG here is a property of the cell/band(s). The UE for a S-NSSAI can be provided with a list of CAGs . how CAGS will be allocated is up to operators and the aim would be to have a rational assignment that is conforming to the rather uncomplicated way that operators hopefully will wish to operate their network so in here lies the scalability of the solution (an operator that fragmented the RAN so much into incompatible slices would not do a favour to itself). For sake of progress and further steps to document this approach in the solution, we are happy with r01 though.
==== Ph1 Revisions Deadline ====
Stefano Faccin (Qualcomm) we see some potential in the concept, but share Ericsson's concerns, and we believe this may cause backward incompatibility. We suggest to note or at least postpone the P-CR until further discussion takes place.
Peter Hedman (Ericsson) still object to any revision with CAG in it, but ok to accept the P-CR if CAG is removed.
Alessio(nokia) I assume it can be marked in MoM that CAG will be removed and then P-CR can be accepted.

If that is what the meeting agrees on call tomorrow I can do that BUT we need to consider this offline for next meeting as a group as it would provide also a way to mitigate need to configure the UE if frequency band allocation changes, and also would allow to reuse the existing CAG based cell selection in idle mode (so no new cell selection algo required). Since I trust we are a great group of people willing to cooperate, I can work with you and stefano on CAG based solution for next meeting.
Stefano Faccin (Qualcomm) clarifies the issue Qualcomm sees is with the CAG part of the proposal.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2004132 P-CR Approval 23.700-40: KI#7, New Sol: Assist UE to access network slices with RFSP Index Huawei, HiSilicon Rel-17 Noted Alessio (Nokia) provides comments and conditional objection to this PCR.: why do we need to report per cell the support of S-NSSAI? If there is a change on the fundamental assumption that a S-NSSAI is supported uniformly in a TA, then we object to this PCR.
Mike (Convida Wireless) asks questions.
Fenqin(Huawei) provide feedback
Stefano Faccin (Qualcomm) replies to comment and disagrees.
Alessio(Nokia) provides objection 'the KI is about 'Today, the UE would have to attempt to select 5G-AN with no awareness as to whether a 5G-AN support a S-NSSAI till the S-NSSAI is allowed. We need to study whether and how to support S-NSSAI-aware 5G-AN selection.' It implies a selection the UE does in idle mode. This is the scope of the KI. The green highlight implies that once the Ue has aan allowed NSSAI the selection is trivial as the TAC will assisted the selection (if it belonging to TAI LIST, SELECT CELL ELSE, SELECT only if there is no other suitable cell in TAI LIST and PERFORM a Registration request in this new TAI)
So, we object to considering any other aspect than cell selection in idle mode. Consistently we object to this PCR and any other that does not stick to the aspect of cell selection in idle mode when the UE needs to request a S-NSSAI not yet in the allowed NSSAI.
Tricci (ZTE) proposed r01 to add EN to discuss further whether it is valid to limit all S-NSSAIs within the Allowed NSSAI to be able to operated simultaneously within the current cell or neighbor cell.
Fenqin(Huawei) provide comments,
==== Ph1 Revisions Deadline ====
Alessio( Nokia) objection is sustained: Our objection is based on the solid long standing assumption documented also in RAN specs: 38.300 section 16.

Slice Availability
- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

So this PCR goes against the above. Also the KI#7 GSMA parameter is targeting to support at least a certain band in a slice, not to not support a certain slice in a TA. This PCR seems is more an issue to be discussed if someone had rel-15/16 CRs of CAT-F nature as they found out the assumptions are broken.

In particular since this PCR assumes this:

* NSSAIs in the Allowed NSSAI shall be able to be operated simultaneously
* It determines the Allowed NSSAI o a cell basis
* It follows the UE shall report mobility at every cell change, also consistently with the reporting per cell of S-NSSAI support over NG.This is unacceptable.
Fenqin(Huawei) provide comments and suggest bring this working assumption issue to Friday CC#2
Fenqin(Huawei) provide feedback.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2004195 P-CR Approval 23.700-40: KI #7, New Sol: Providing Operating Band Information in the Configured NSSAI. Convida Wireless LLC, AT&T, Telecom Italia, Samsung Rel-17 Revised to S2-2004584. Alessio(Nokia) provides comment and a conditional objection
Mike (Convida Wireless) responds
Farooq (ATT) provides response to Nokia's comment
Alessio (Nokia) The RAN reports to the AMF support of S-NSSAI per TA in rel-16 and in rel15. This is stage 3 and in 38.41 3is there for you to read. Do you mean that the 3GPP stage 3 is my personal opinion?

If a TA supports a S-NSSAI, it means ALL cells in the TA support the S-NSSAI. None excluded. The concept that the RAN would report support of a S-NSSAI in a TA as a stochastic event that may or may not happen depending on the cell is untenable... Farooq please provide me with text this is what reporting per TA means.
Mike (Convida Wireless) comments. Alessio, you say 'The RAN reports to the AMF support of S-NSSAI per TA in rel-16 and in rel15. This is stage 3 and in 38.413 is there for you to read' But 38.413 says that the RAN reports what slices are supported in the TA. No where does it say 'these slices are supported in every cell of the TA'. This this is all consistent with stage 2 and does not prove your point. In Rel-15/16 an operator can consider the Allowed NSSAI and configure the RFSP index so that the UE does not use certain bands if that is how they choose to configure their network..
Farooq (ATT) agrees with Mike' comments. What Alessio's has is his own interpretation of RAN specs and he has failed to provide actual reference to text to support his view.
Mike (Convida Wireless) provides rev01 adding Verizon as a supporting company. Also, in attempt to address Alessio's comments, I added a statement that points out that we are not changing the principle that 'A TA is the set of all cells that broadcast the same TAC'.
Stefano Faccin (Qualcomm) provides rev02 adding clarifications.
Mike (Convida Wireless) replies to Stefano (Qualcomm).
Alessio(Nokia) comments
Mike Starsinic (Convida Wireless) comments and provides rev03
Alessio(Nokia) provides r03
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004584 P-CR Approval 23.700-40: KI #7, New Sol: Providing Operating Band Information in the Configured NSSAI. Convida Wireless LLC, AT&T, Telecom Italia, Samsung, Verizon UK Rel-17 Revision of S2-2004195. Approved Approved
8.4 S2-2004198 P-CR Approval 23.700-40: KI #7, New Sol: Providing Operating Band Information with the RFSP Index. Convida Wireless LLC Rel-17 Noted Alessio(Nokia) provides objection
Mike (Convida Wireless) responds and fixes the thread title.
Mike (Convida Wireless) responds to Nokia.
Mike (Convida Wireless) provides r01 which attempts to address at least some of Nokia's concerns.
Patrice (Huawei) comments and provides r02.
Mike (Convida Wireless) replies.
==== Ph1 Revisions Deadline ====
Alessio( Nokia) objection is sustained: Our objection is based on the solid long standing assumption documented also in RAN specs: 38.300 section 16.

Slice Availability
- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

So this goes against the above. Also the KI#7 GSMA parameter is targeting to support At least a certain band in a slice, not to not support a certain slice in a TA.
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2004207 P-CR Approval 23.700-40: KI #7, New Sol: Preferred frequency bands in Configured NSSAI. Motorola Mobility, Lenovo Rel-17 Revised to S2-2004585. Peter Hedman (Ericsson) provides comments.
Genadi (Motorola Mobility) answers comments from Ericsson/Peter.
Patrice (Huawei) comments and provides r01.
Genadi (Motorola Mobility) answers comments from Huawei/Patrice and accepts r01.
Patrice (Huawei) further comments.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004585 P-CR Approval 23.700-40: KI #7, New Sol: Preferred frequency bands in Configured NSSAI. Motorola Mobility, Lenovo Rel-17 Revision of S2-2004207. Approved Approved
8.4 - - - Key issue 8 related - - Docs:=5 -
8.4 S2-2004275 P-CR Approval 23.700-40: KI#8: Deprecation. vivo Mobile Communications Ltd Rel-17 . Merged into S2-2004586 Peter Hedman (Ericsson) proposes to 'merge' the P-CR into S2-2003583.
Adrian (vivo) is fine with the proposal from Ericsson.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Merged
8.4 S2-2003583 P-CR Approval 23.700-40: KI#8: Update to KI#8 to not study the Area of Service Attribute . Ericsson Rel-17 Revised, merging S2-2004275, to S2-2004586. Hyunsook (LGE) provides r01 and r02.
Peter Hedman (Ericsson) provides comments.
Hyunsook (LGE) provides comments.
George (Ericsson) provides r03 added as cosigner.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Revised
8.4 S2-2004586 P-CR Approval 23.700-40: KI#8: Update to KI#8 to not study the Area of Service Attribute . Ericsson, Deutsche Telekom Rel-17 Revision of S2-2003583, merging S2-2004275. Approved Approved
8.4 S2-2003734 P-CR Approval 23.700-40: KI #8, New Sol: Support of S-NSSAI-aware PLMN selection in roaming scenarios. Apple Rel-17 Noted Tricci So (ZTE) maintained recommendation for this PCR to be NOTED.
Dieter (Deutsche Telekom) proposes also to note this PCR.
Hyunsook (LGE) proposes to note this pCR.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
8.4 S2-2003735 P-CR Approval 23.700-40: KI #8, New Sol: Including supported PLMN list in Allowed NSSAI. Apple Rel-17 Noted Tricci So (ZTE) recommended this PCR to be NOTED.
Hyunsook (LGE) prefers to note this pCR.
Dieter (Deutsche Telekom) proposes also to note this pCR.
Alessio(Nokia) proposes also to note this pCR and all other pCRs providing solutions for KI#8, and just approve the pCR to KI#8 that updates the KI#8 to say that there is no further work in it in this in this Study.
==== Ph1 Revisions Deadline ====
==== Ph1 Final Deadline ====
==== Close of meeting Ph1 ====
Noted
9 - - - Project Planning and Management - - Docs:=0 -
9.1 - - - New and Revised Work Items, Cover sheets for completed work items - - Docs:=5 -
9.1 - - - SIDs updating content - - Docs:=2 -
9.1 S2-2004089 SID REVISED Approval Revised SID: Study on System enhancement for Proximity based Services in 5GS CATT, OPPO Rel-17 R02 agreed. Revised to S2-2004333 Laurent (Nokia): provides r01. Updated to S2-2004089_r02 at CC#1
Puneet (Chair): provides r02 as per discussion during CC 1
==== Ph1 Revisions Deadline ====
Revised
9.1 S2-2004333 SID REVISED Approval Revised SID: Study on System enhancement for Proximity based Services in 5GS CATT, OPPO Rel-17 Revision of S2-2004089_r02. Approved
==== Ph1 Revisions Deadline ====
Approved
9.1 - - - SIDs updating timeline only - - Docs:=3 -
9.1 S2-2003969 SID REVISED Approval Revised SID: Architectural enhancements for 5G multicast-broadcast services Huawei (Rapporteur) Rel-17 Noted at CC#1 NOTED? Noted
9.1 S2-2004042 SID REVISED Approval Revised_SID_FS_eNA_Ph2 China Mobile Rel-17 Noted at CC#1 NOTED? Noted
9.1 S2-2004120 SID REVISED Approval Update FS_enh_EC SID Huawei Rel-17 Noted at CC#1 NOTED?
==== Ph1 Revisions Deadline ====
Noted
9.2 - - - Review of the Work Plan - - Docs:=1 -
9.2 S2-2003722 WI STATUS REPORT Endorsement FS_eNPN Status Report Ericsson Inc. Rel-17 Noted at CC#1 NOTED?
==== Ph1 Revisions Deadline ====
Noted
9.3 - - - Planning future meetings - - Docs:=0 -
11.1 - - - Close of Phase 1 of the meeting - - Docs:=0 -
CC#1 - - - SA2#139E_CC#1 - - Docs:=0 -
CC#2 - - - SA2#139E_CC#2 - - Docs:=0 -
CC#2 - - - SA2#139E_CC#3 - - Docs:=0 -
CC#4 - - - SA2#139E_CC#4 - - Docs:=0 -
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 218
Replied to LSs: 0
Noted: 116
Merged: 50
For e-mail approval: 0
Postponed: 21
Withdrawn: 2
Total documents: 687