Chairman's notes

 

IPR call reminder:

"I draw your attention to your obligations under the 3GPP Partner Organizations' IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP.

Delegates are asked to take note that they are thereby invited:

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

 

Antitrust policy Reminder:

"I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this TSG/WG meeting including the Chairman and Vice Chairman. In case of question I recommend that you contact your legal counsel.

The leadership shall conduct the present meeting with impartiality and in the interests of 3GPP.

 

Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG meetings is important to allow for full and fair consideration of such matters."

 

 

List for Meeting: All Sessions
Temporary Documents List - Ordered by Agenda Item
AI TD# Type Doc For Subject Source Rel Comments e-mail_Discussion Result
0 - - - All Agenda Items - - Docs:=0 -
1.1 - - - Opening of the meeting - - Docs:=0 -
2 - - - Agenda - - Docs:=1 -
2 S2-2105222 AGENDA Approval SA WG2 #146E Meeting Agenda SA WG2 Chair CC#1: The meeting agenda was approved. Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
3 - - - SA2#145E Meeting report - - Docs:=1 -
3 S2-2105223 REPORT Approval Auto-Generated Report of SA WG2 meeting #145E SA WG2 Secretary Approved Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=55 -
4.1 - - - LSs for Information - - Docs:=13 -
4.1 S2-2105231 LS In Information LS from WBA 5G Work Group: Liaison Statement on 5G & Wi-Fi RAN Convergence WBA 5G Work Group (WBA LS on 5G Wi-Fi RAN Convergence) Revision of postponed S2-2103729 from S2-145E. Duplicate LS in S2-2105365. Noted Noted
4.1 S2-2105233 LS In Information LS from GSMA NG NRG: LS to 3GPP SA2 on ARP PL GSMA NG NRG (NRG 009_201 - LS to 3GPP SA2 CT3 ARP) Revision of postponed S2-2103732 from S2-145E. Response drafted in S2-2105659. Final response in S2-2106534
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105275 LS In Information LS from RAN WG3: Reply LS to CT4 on Information on the port number allocation solutions RAN WG3 (R3-212800) Rel-17 Noted Wanqiang (Huawei) proposes to note the LS as no SA2 action needed.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105284 LS In Information LS from RAN WG3: LS on Insufficient UE Capabilities Cause Value RAN WG3 (R3-212934) Rel-16 Noted Wanqiang (Huawei) proposes to note the LS as no SA2 action needed.
Thomas (Nokia) provides r01
Paul (Ericsson) agrees to note this LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105286 LS In Information LS from RAN WG3: LS on (de)activation and failure handling of NR QMC RAN WG3 (R3-212975) Rel-17 Noted Paul (Ericsson) proposes to note this LS as there are no actions for SA2.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105287 LS In Information LS from SA WG1: LS Response on Media-Related Services and Requirements SA WG1 (S1-211364) Rel-18 Noted Hui (Huawei) proposes to note this LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105298 LS In Information LS from SA WG3: Reply-LS on Secondary AUTH for 5GS interworking with EPS SA WG3 (S3-212366) Rel-17 Noted Stefan (Ericsson) proposes to note the LS
Laurent (Nokia): supports to note the LS
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105304 LS In Information LS reply to LS from WSOLU to 3GPP SA5 - 5G charging architecture for wholesale scenarios SA WG5 (S5-213583) Rel-17 Noted Gerald (Matrixx) suggest to note this LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105357 LS In Information LS from GSMA ACJA: 3GPP SA WG1 clarifications on problematic UAV GSMA ACJA (5GJA17_104) Noted Shabnam (Ericsson) provides comments to NOTE the LS as I believe SA2 responded to this from last meeting in 4916.
Runze (Huawei) proposes to NOTE the LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105359 LS In Information LS from BBF: Alignment concerning 5G RG requirements and its remote management BBF (LIAISE-467-03) Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105363 LS In Information LS from ITU-T SG11: LS on the new work item Q.DC-SA 'Signalling architecture of data channel enhanced IMS network' ITU-T SG11 (SG11-LS200.) Noted George Foti (Ericsson) proposes to note the LS
Thomas (Nokia) supports noting the LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105364 LS In Information LS from SMPTE 32NF Technology Committee: PTP device monitoring Public Committee Draft SMPTE 32NF Technology Committee (SLC04-smpte-to-3GPP-PCD-RP2059-15-2021-04-28) Noted Shabnam (Ericsson) provides comments related to agenda 8.5, that we don't expect any 3GPP response to this LS so should we NOTE it?
Devaki (Nokia) proposes to postpone the LS.
Shabnam (Ericsson) comments that only action is to review their draft and provide comments, I don't believe SA2 needs to do this officially, but companies can do so directly as indicated. Then our main interaction would be via IEEE where we have not received any response I believe.
Qianghua (Huawei) also thinks that we can note the LS, they ask 3GPP to review the PTP monitoring YANG data model, somehow beyond the SA2 scope.
Sang-Jun (Samsung) also propose to note the LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105367 LS In Information LS from NGMN: NGMN Liaison Statement on 5G Network Customization Based on Service-Based Architecture NGMN (210728 Liaison_NGMN) Noted Magnus O (Ericsson) propose to note the LS.
Thomas (Nokia) supports noting the LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 - - - LSs for action (no input) - - Docs:=6 -
4.1 S2-2105272 LS In Action LS from RAN WG2: LS on Paging Subgrouping RAN WG2 (R2-2106552) Rel-17 Postponed Miguel (Qualcomm) proposes to postpone this incoming LS
Steve (Huawei) agrees about postponing.
Chris (Vodafone) agrees with Qualcomm on postponing this incoming LS
Miguel (Qualcomm) insists on marking this incoming LS as 'postponed' and not as 'noted'
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
4.1 S2-2105277 LS In Action LS from RAN WG3: Reply LS to LS on User Plane Integrity Protection for eUTRA connected to EPC RAN WG3 (R3-212812) Noted Chris (Vodafone) proposes to note this reply LS
Laurent (Nokia): supports noting this LS. there is no real action for us
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105356 LS In Action LS from GSMA 5GJA: LS on Traffic Categories in URSP GSMA 5GJA (5GJA17_104) Postponed Belen (Ericsson) asks to postpone this LS for next SA2 meeting
Krisztian (Apple) thinks a corresponding objective should be created for a planned R18 SID to address this request by GSMA.
Yang (OPPO) share the view to put it into R18 SID, since it is unclear if and whether the 5GS impact exists.
Dan(China Mobile) also suggest to postpond this LS
Alessio (Nokia) is ok to postpone the LS response also but notes that 3GPP may have already sufficient tools to identify traffic categories.
Jicheol (Samsung) has no problem to postpone this paper, but the existing 'connection capabilities' in URSP is suffient.
Dieter (Deutsche Telekom) has no problem to postpone this paper, but doubts that this would need a Rel18 study.
Gerry (Verizon) also thinks a corresponding objective should be added to the proposed R18 SID to address this request by GSMA.
Yusuke (KDDI) shares views of Apple and Verizon. We propose FS_UEPO SI (S2-2105955) should address the request by GSMA.
Sherry (Xiaomi) comments that the motivation of introducing 'Traffic Categories' in addition to 'connection capabilities' is unclear.
Krisztian (Apple) responds to Sherry and proposes to treat this LS together with S2-2105955. During the R18 study we could evaluate whether separate 'Traffic Categories' are needed or they can be incorporated into 'Connection Capabilities'.
Belen (Ericsson) is okay to add the contents of this LS as Objective in S2-2105955 (FS_UEPO). Also ok to postpone to next meeting to prepare LS response to GSMA.
Alessio(Nokia) prefers to not conclude in this thread this is added to a SID. scoping of a SID should be done in contribution driven manner in the SID discussion itself. so let's just postpone this LS for this meeting.
Dieter (Deutsche Telekom) agrees with Alessio(Nokia) to leave SID scoping to SID contributions and just postpone this LS .
Susana (Vodafone) agrees to use the UEPO SID thread to add the objective as seen needed, and postpone the LS reply.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
4.1 S2-2105365 LS In Action LS from WBA PMO: Liaison Statement on 5G & Wi-Fi RAN Convergence WBA PMO (WBA_LS_2021 v1F-3GPP SA) Response drafted in S2-2106527. Final response in S2-2106533
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2106527 LS OUT Approval [DRAFT] Rely LS to Liaison Statement on 5G & Wi-Fi RAN Convergence Huawei Created at CC#1. Response to S2-2105365. Revised to S2-2106533. Marco (Huawei) provides the proposed LSout to WBA per CC#1 call.
Laurent (Nokia): provides r01
Marco (Huawei) OK with r01
Maurice (MCC) Provides r02 correcting To: WBA
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106533 LS OUT Approval Reply LS to Liaison Statement on 5G & Wi-Fi RAN Convergence SA WG2 - Revision of S2-2106527r02. Approved Approved
4.1 - - - ARP PL - - Docs:=6 -
4.1 S2-2105360 LS In Action LS from GSMA NRG: LS to 3GPP SA2 on ARP PL GSMA NRG (NRG 009_201) Duplicate LS in S2-2105233. Noted Noted
4.1 S2-2105659 LS OUT Approval [DRAFT] Rely LS to LS SA WG2 on ARP PL Ericsson Response to S2-2105233. Revised to S2-2106534.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106534 LS OUT Approval Reply LS to LS to 3GPP SA2 on ARP PL SA WG2 Rel-17 Revision of S2-2105659r00. Approved Approved
4.1 S2-2105657 DISCUSSION Agreement ARP PL in EPS. Ericsson Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2105658 CR Approval 23.401 CR3648 (Rel-17, 'F'): ARP PL applied by MME per local configruation Ericsson Rel-17 Revised to S2-2106535. Laurent (Nokia): asks a question
Judy (Ericsson) responds to Laurent (Nokia)
Chris (Vodafone) comments.
Judy (Ericsson) provides r01
Mirko (Huawei) provides r02
Judy (Ericsson) is fine with r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106535 CR Approval 23.401 CR3648R1 (Rel-17, 'F'): ARP PL applied by MME per local configruation Ericsson Rel-17 Revision of S2-2105658r02. Approved Agreed
4.1 - - - Reliable Data Service Serialization - - Docs:=6 -
4.1 S2-2105225 LS In Action LS on stage 3 aspects for Reliable Data Service Serialization Indication CT WG1 (C1-207769) Revision of postponed S2-2103718 from S2-145E. Response drafted in S2-2105386. Final response in S2-2106536
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105386 LS OUT Approval [DRAFT] LS on Reliable Data Service Serialization Indications in Rel-16 Convida Wireless LLC Rel-16 Response to S2-2105225. Revised to S2-2106536. Mike (Convida Wireless) provides r01 with no changes so that if this LS gets approved it will be revised with a new number and [Draft] can be removed from the title.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106536 LS OUT Approval LS on Reliable Data Service Serialization Indications in Rel-16 SA WG2 Rel-16 Revision of S2-2105386r01. Approved Approved
4.1 S2-2105387 CR Approval 23.682 CR0480 (Rel-16, 'F'): Removal of Reliable Data Service Serialization Indications Convida Wireless LLC Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
4.1 S2-2105388 CR Approval 23.501 CR3008 (Rel-16, 'F'): Removal of Reliable Data Service Serialization Indications Convida Wireless LLC Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
4.1 S2-2105389 CR Approval 23.502 CR2897 (Rel-16, 'F'): Removal of Reliable Data Service Serialization Indications Convida Wireless LLC Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
4.1 - - - Capabilities exposure - - Docs:=6 -
4.1 S2-2105229 LS In Action LS from 5G-ACIA: 5G capabilities exposure for factories of the future - revised 5G-ACIA (5G-ACIA_LS_3GPP_Exposure_18032021) Revision of postponed S2-2103727 from S2-145E. Response drafted in S2-2105854. Final response in S2-2106683
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105355 LS In Action LS from 5G-ACIA: 5G capabilities exposure for factories of the future - revised 5G-ACIA (5G-ACIA_LS_3GPP_Exposure_18032021_Final) Response drafted in S2-2106047. Noted Riccardo (NT DOCOMO) proposes to note this paper and reply only to S2-2105229.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2106047 LS OUT Approval [DRAFT] LS on 5G capabilities exposure for factories of the future Huawei, HiSilicon Rel-18 Response to S2-2105355. Merged into S2-2106683 Qianghua (Huawei) provides r01
Laurent (Nokia): Comments and suggests to discuss a minimalistic interim answer as per 5854R02
Qianghua (Huawei) provides r02
Dieter (Deutsche Telekom) provides r03.
Dieter (Deutsche Telekom) propose to note this or 5854 and just send one answer to ACIA.
Riccardo (NT DOCOMO) proposes to note this paper and work on S2-2105854.
Qianghua (Huawei) suggests to use this as baseline
Laurent (Nokia): Proposes to note 6047 and to work only on 5854
Magnus O (Ericsson) proposes to note 6047 and work on a revision of 5854.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
4.1 S2-2105854 LS OUT Approval [DRAFT] LS on 5G capabilities exposure for factories of the future Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2105229. CC#2: r11 + changes agreed. Revised, merging S2-2106047, to S2-2106683. Tricci (OPPO) would like to ask for clarifications for the intent of the LSout to SA and to suggest to replace some of the 'definite' wordings to be replaced by an 'optimistic' wordings.
Laurent (Nokia): answers
Hyunsook (LGE) has a comment.
Qianghua (Huawei) provides comments and proposes to use S2-2106047 as baseline
Serge (T-Mobile USA) supports deferring response until Oct meeting.
Tricci (OPPO) supports to defer the response until Oct meeting and may be even later dependent on when the Rel18 Sis/WIs are prioritized.
Tricci (OPPO) thanks Nokia's suggestion and supports to send simple quick LS response to ACIA.
Laurent (Nokia): provides r02
Marco (Huawei) comment that current versions are too minimalistic and not consistent with the current status.
Sebastian (Qualcomm) comments
Laurent (Nokia): provides r03 an a bit less minimalistic version
Qianghua (Huawei) provides r04
Dieter (Deutsche Telekom) propose to note this or 6047 and just send one answer to ACIA.
Laurent (Nokia): provides r05 and suggests we work only on 5854 (not on 6047) (there is another version of 5854 that is more minimalistic)
Marco (Huawei) answers to Dieter (Deutsche Telekom).
Dieter (Deutsche Telekom) comments.
Sebastian (Qualcomm) provides r06 with additional simplifications on top of r05 and a comment about a sentence that is incomplete
Qianghua (Huawei) provides r07
Laurent (Nokia): provides r07 and r08
Laurent (Nokia): provides r08 (correcting the previous mail)
Magnus O (Ericsson): provides r09
Qianghua (Huawei) provides r10
Dieter (Deutsche Telekom) provides r11 and objects to any previous revision.
Laurent (Nokia): provides r12
Qianghua (Huawei) replies
Dieter (Deutsche Telekom) objects to r12 and provides answer to Laurent.
Sebastian (Qualcomm) provides r13
Sang-Jun (Samsung) proposes a comprimise.
Laurent (Nokia): Comments
Sebastian (Qualcomm) prefers r13
Dieter (Deutsche Telekom) prefers r11 with some wording improvements, r13 does not work for us.
Marco (Huawei) comments on select a version with list of topic as in R10 or r12 and not a R11 and R13.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106683 LS OUT Approval LS on 5G capabilities exposure for factories of the future SA WG2 Rel-18 Revision of S2-2105854r11 + changes, merging S2-2106047. Approved Approved
4.1 S2-2105305 LS In Information LS from SA WG6: LS on 5G capabilities exposure for factories of the future SA WG6 (S6-211497) Rel-17 Noted Qianghua (Huawei) this LS is for information, it is proposed to note this LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 - - - ATC in N1N2Message Transfer - - Docs:=6 -
4.1 S2-2105239 LS In Action LS from CT WG4: LS on Support of Asynchronous Type Communication in N1N2MessageTransfer CT WG4 (C4-212401) Rel-17 Revision of postponed S2-2103765 from S2-145E. Responses drafted in S2-2105696 and S2-2106177. Final response in S2-2106684
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105696 LS OUT Approval [DRAFT] LS Reply on Support of Asynchronous Type Communication in N1N2MessageTransfer Huawei, HiSilicon Rel-17 Response to S2-2105239. CC#2: r10 agreed. Revised, merging S2-2106177, to S2-2106684. Qian (Ericsson) provides comments and considers 6177 has better form as LS out
Hannu (Nokia) can take either 5696 or 6177 as the template, but would like to focus on the (lack of) need for the ATC procedure first.
Haiyang(Huawei) provides r01
Haiyang(Huawei) provides r02
Hannu (Nokia) proposes clarification and includes the handling of backwards compatibility in SA2 answer #5.
Haiyang(Huawei) provides r04 based on r03
Qian (Ericsson) comments and provides r05
Hannu (Nokia) replies to Haiyang(Huawei) and provides r06. Can agree either r03 or r06.
Haiyang(Huawei) provides r07
Hannu (Nokia) can still agree either r03 or r06 but objects to r07.
Qian (Ericsson) can only accept r05, or r08 with 2 extra updates listed below and objects to all other revisions. The other alternative is to use 6177.
Haiyang(Huawei) provides r10 based on r09
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106684 LS OUT Approval LS Reply on Support of Asynchronous Type Communication in N1N2MessageTransfer SA WG2 Rel-17 Revision of S2-2105696r10, merging S2-2106177. Approved Approved
4.1 S2-2106177 LS OUT Approval [DRAFT] Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer Ericsson Inc. Rel-17 Response to S2-2105239. Merged into S2-2106684 Haiyang(Huawei) suggests to use S2-2105956 instead (mark this paper noted or merged into 5956)
Qian (Ericsson) provides comments and consider this paper has better foundation as a LS response.
Haiyang(Huawei) comments
Hannu (Nokia) proposes to deal with the CR first asks what happens if the AMF does not support ATC at all?
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
4.1 S2-2105695 CR Approval 23.501 CR3062 (Rel-17, 'C'): Explicit indication for ATC Huawei, HiSilicon Rel-17 CC#2: r07 agreed. Revised to S2-2106685. Myungjune (LGE) provides comments.
Qian (Ericsson) provides comments and suggest to NOTE the paper.
Hannu (Nokia) proposes to either remove the ATC feature or to add an explicit ATC indicator if real use case can be identified for the feature.
Haiyang (Huawei) provides response and r01.
Hannu (Nokia) provides r02 to show how he understood the proposal. This is not a voice in favour of the CR, just to understand what it intends to say.
Qian (Ericsson) comments and objects to r00 and r01.
Hannu (Nokia) skips r03 and provides r04 to address backwards compatibility with Rel-16 AMF.
Haiyang (Huawei) provides response and r05.
Hannu (Nokia) asks a question on r05.
Haiyang (Huawei) provides r06.
Qian (Ericsson) provides comments.
Haiyang (Huawei) provides response to Qian(Ericsson).
Qian (Ericsson) provides further comments.
Hannu (Nokia) proposes to add explicit ATC indication, liaise back to CT4 and provides r07.
Haiyang (Huawei) is OK with r07.
Qian (Ericsson) provides comments and propose to NOTE the paper.
Hannu (Nokia) proposes to escalate this topic to SA2 CC since CT1 and CT4 work depends on our decision.
Qian (Ericsson) response to Hannu.
Haiyang (Huawei) comments.
Qian (Ericsson) responds.
Haiyang (Huawei) further comments.
Qian (Ericsson) objects this CR and all revisions.
Hannu (Nokia) can only agree r07 as interim reaction to CT4 request. Can also agree to remove the ATC completely, if no valid use case can be identified.
Haiyang (Huawei) suggests to endorse r07 as a compromise.
Qian (Ericsson) can only accept r05, or r08 with 2 extra updates listed below and objects to all other revisions. The other alternative is to use 6177.
Haiyang (Huawei) indicates the previous comment from Qian(Ericsson) is in a wrong thread...
Qian (Ericsson) comments and says we can go with r07 if the LS out can be update as requested in the 5696 thread. Qian also says the previous mail/comments is for 5696.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106685 CR Approval 23.501 CR3062R1 (Rel-17, 'C'): Explicit indication for ATC Huawei, HiSilicon Rel-17 Revision of S2-2105695r07. Approved Agreed
4.1 - - - Service type to slice mapping - - Docs:=3 -
4.1 S2-2105281 LS In Information LS from RAN WG3: LS on the mapping between service types and slice at application RAN WG3 (R3-212904) Rel-17 Response drafted in S2-2105862. Final response in S2-2106537
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105862 LS OUT Approval [DRAFT] Reply LS on the mapping between service types and slice at application Qualcomm Austria RFFE GmbH Response to S2-2105281. r03 agreed. Revised to S2-2106537. Paul (Ericsson) provides comments and r01.
Alessio (Nokia) provides r02
Dieter (Deutsche Telekom) provides r03.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106537 LS OUT Approval Reply LS on the mapping between service types and slice at application SA WG2 - Revision of S2-2105862r03. Approved Approved
4.1 - - - Slice selection during AMF reallocation - - Docs:=5 -
4.1 S2-2105289 LS In Action LS from A WG3: LS on Clarifications of Network slice selection during AMF Reallocation SA WG3 (S3-212124) Rel-17 Responses drafted in S2-2105344, S2-2105482 and S2-2106113. Final response in S2-2106686
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
4.1 S2-2105344 LS OUT Approval [DRAFT] Reply LS on Clarifications of Network slice selection during AMF Reallocation Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2105289. Merged into S2-2106686 Fenqin (Huawei) suggest to have the discussion in 6113 thread
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
4.1 S2-2105482 LS OUT Action [DRAFT] Reply LS on Clarifications of Network slice selection during AMF Reallocation Lenovo, Motorola Mobility Rel-17 Response to S2-2105289. Merged into S2-2106686 Fenqin (Huawei) suggest to have the discussion in 6113 thread
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
4.1 S2-2106113 LS OUT Approval [DRAFT] LS Response on Clarifications of Network slice selection during AMF Reallocation Huawei, HiSilicon Rel-17 Response to S2-2105289. CC#2: r15 + changes agreed. Revised, merging S2-2105344 and S2-2105482, to S2-2106686. Josep (DT) understands this is the discussion thread and asks a question for clarification.
Fenqin (Huawei) responds
Dan (China Mobile)ask question for clarification
Peter (Ericsson) provides comments
Fenqin (Huawei) responds and provides r01
Fenqin (Huawei)responds
Josep (DT) proposes clearer wording in r02.
Fenqin (Huawei) proposes r03.
Peter Hedman (Ericsson) provides comments
Jinguo(ZTE) provides comments
Genadi (Lenovo) provides comments and revision r04.
Alessio(Nokia) provides r05
Peter Hedman (Ericsson) provides r06
Fenqin (Huawei) provides r07
Alessio(Nokia) provides r08
Jinguo(ZTE) provides r09
Fenqin (Huawei) provides r10
Genadi (Lenovo) provides revision r11.
Peter Hedman (Ericsson) provides r12
Fenqin (Huawei) provides revision r13.
Miguel (Qualcomm) provides r14.
Genadi (Lenovo) supports revision r12 and cannot accept the later revisions.
Fenqin (Huawei ) propose r15 and bring it to CC#2
Genadi (Lenovo) supports revision r14 and suggests that we should discuss this in CC#2 if we do not reach consensus now. We are not in favor of r12
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Peter Hedman (Ericsson) provides question
Peter Hedman (Ericsson) provides comments on injecting false comments to chair notes
Alessio (Nokia) supports revision r14 and suggests that we should discuss this in CC#2 if we do not reach consensus now. We are not in favor of r12
Genadi (Lenovo) provides replies to Peter Hedman (Ericsson).
Genadi (Lenovo) provides r16 to be discussed during the CC#2. The changes compared to r14 are highlighted in green.
Fenqin (Huawei) provides comment.
Revised
4.1 S2-2106686 LS OUT Approval LS Response on Clarifications of Network slice selection during AMF Reallocation SA WG2 Rel-17 Revision of S2-2106113r15 + changes, merging S2-2105344 and S2-2105482. Approved Approved
4.1 - - - IP Address to GPSI translation - - Docs:=18 -
4.1 - - - Other - - Docs:=4 -
4.1 S2-2106223 CR Approval 23.501 CR3170 (Rel-17, 'B'): AUSF/UDM discovery based SUCI information China Mobile Rel-17 Revised to S2-2106538. Devaki (Nokia) provides r01.
Fenqin (Huawei) provides r02.
Devaki (Nokia) has concerns with r02.
Josep (DT) provides r03, co-signs.
Yi (China Mobile) thanks to DT's cosigning and provides R04.
Devaki (Nokia) provides r05 (and supports the proposal).
Fenqin (Huawei) is fine with the change.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106538 CR Approval 23.501 CR3170R1 (Rel-17, 'B'): AUSF/UDM discovery based SUCI information China Mobile, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2106223r05. Approved Agreed
4.1 S2-2106224 CR Approval 23.502 CR3069 (Rel-17, 'B'): AUSF/UDM discovery based SUCI information China Mobile Rel-17 Revised to S2-2106539. Devaki (Nokia) provides r01.
Josep (DT) co-signs, provides r02.
Yi (China Mobile) thanks to DT's cosigning and provides R03.
Yi (China Mobile) thanks to Nokia cosigning and provides R04.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2106539 CR Approval 23.502 CR3069R1 (Rel-17, 'B'): AUSF/UDM discovery based SUCI information China Mobile, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2106224r04. Approved Agreed
4.2 - - - P-CRs/CRs related to use of inclusive language in 3GPP - - Docs:=0 -
5 - - - Pre-Rel-17 Maintenance (excluding all 5G topics) - - Docs:=0 -
5.1 - - - 3GPP Packet Access Maintenance - - Docs:=4 -
5.1 S2-2106213 CR Approval 23.682 CR0481 (Rel-16, 'F'): Idle Status Indication correction Nokia, Nokia Shanghai Bell Rel-16 Revised to S2-2106540. Qian (Ericsson) asks few questions
Hannu (Nokia) replies to Qian (Ericsson)
Qian (Ericsson) provides further comments
Qianghua (Huawei) provides comments
Qian (Ericsson) provides comments and r02
Hannu (Nokia) answers to Qian (Ericsson) and asks further question.
Hannu (Nokia) replies to Qianghua
Hannu (Nokia) agrees r02 and thanks Qian for using reference instead of duplicated requirement.
Qianghua (Huawei) also OK for r02.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
5.1 S2-2106540 CR Approval 23.682 CR0481R1 (Rel-16, 'F'): Idle Status Indication correction Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2106213r02. Approved Agreed
5.1 S2-2106214 CR Approval 23.682 CR0482 (Rel-17, 'A'): 5GS Idle Status Indication correction Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106541.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
5.1 S2-2106541 CR Approval 23.682 CR0482R1 (Rel-17, 'A'): 5GS Idle Status Indication correction Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106214r00. Approved Agreed
5.2 - - - QoS and PCC Maintenance - - Docs:=0 -
5.3 - - - Non-3GPP Access Maintenance - - Docs:=0 -
5.4 - - - IMS and IMS-Related Maintenance - - Docs:=0 -
6 - - - Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) - - Docs:=0 -
6.1 - - - General aspects, concepts and reference models - - Docs:=14 -
6.1 S2-2105309 CR Approval 23.501 CR2993 (Rel-17, 'F'): Clarifying that at least one default S-NSSAI is mandatory Nokia, Nokia Shanghai Bell, Telecom Italia, Orange, AT&T, ZTE, Deutsche Telekom, Oppo, NTT Docomo Rel-17 Revised to S2-2106542. Peter (Ericsson) provides comments and r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2106542 CR Approval 23.501 CR2993R1 (Rel-17, 'F'): Clarifying that at least one default S-NSSAI is mandatory Nokia, Nokia Shanghai Bell, Telecom Italia, Orange, AT&T, ZTE, Deutsche Telekom, Oppo, NTT Docomo, Ericsson Rel-17 Revision of S2-2105309r01. Approved Agreed
6.1 S2-2105310 CR Approval 23.502 CR2882 (Rel-17, 'F'): Clarification on selection of the hNRF Nokia, Nokia Shanghai Bell, Telecom Italia Rel-17 Revised to S2-2106543. Peter (Ericsson) provides comments and r01
Alessio(Nokia) is ok with r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2106543 CR Approval 23.502 CR2882R1 (Rel-17, 'F'): Clarification on selection of the hNRF Nokia, Nokia Shanghai Bell, Telecom Italia, Ericsson Rel-17 Revision of S2-2105310r01. Approved Agreed
6.1 S2-2105454 CR Approval 23.501 CR3016 (Rel-17, 'F'): Nnssf_NSSelection service for connected mode Inter-PLMN mobility Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) request for clarification
Patrice (Huawei) disagrees with the CR (not required, major impact) and requests it to be noted.
Alessio replies to Malla (NTT DOCOMO) request for clarification
alessio(Nokia) comments and asks question.
Peter Hedman (Ericsson) provides reply and do not see the CR as Cat F but rather it is changing/adding functionality.
alessio(nokia) explains that the NRF requires knowing the S-NSSAI of the target PLMN and this is not know as these are based on mapping of the UE HPLMN S-NSSAIs
Peter Hedman (Ericsson) provides comments and objects
Alessio(Nokia) believes ericsson misunderstood what we wrote: we do not believe the current NRF-based method works in all plausible use cases.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2105455 CR Approval 23.502 CR2912 (Rel-17, 'F'): Nnssf_NSSelection service clarification for connected mode Inter-PLMN mobility Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) same comment as S2-2105454
Patrice (Huawei) disagrees with the CR (not required, major impact) and requests it to be noted.
Alessio (Nokia) same replies apply as for S2-2105454
alessio(Nokia) comments and asks same question as for S2-2105454
Peter Hedman (Ericsson) provides question
Peter Hedman (Ericsson) provides reply and do not see the CR as Cat F but rather it is changing/adding functionality.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2105625 CR Approval 23.501 CR3054 (Rel-17, 'F'): Correction on charging Matrixx Rel-17 Revised to S2-2106544. Gerald (Matrixx) provides r01
Stefan (Ericsson) provides r02
Gerald (Matrixx) thanks for the provided r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2106544 CR Approval 23.501 CR3054R1 (Rel-17, 'F'): Correction on Charging Matrixx Rel-17 Revision of S2-2105625r02. Approved Agreed
6.1 S2-2106253 CR Approval 23.502 CR3074 (Rel-16, 'F'): Update on EventExposure Subscribe services Huawei, Hisilicon Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.1 S2-2106254 CR Approval 23.502 CR3075 (Rel-17, 'A'): Update on EventExposure Subscribe services Huawei, Hisilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.1 S2-2106390 CR Approval 23.501 CR3207 (Rel-16, 'F'): Correction of N26 message relaying between S1 and N26 messages Deutsche Telekom Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.1 S2-2106393 CR Approval 23.501 CR3208 (Rel-17, 'A'): Correction of N26 message relaying between S1 and N26 messages Deutsche Telekom Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.1 S2-2106403 CR Approval 23.501 CR3213 (Rel-17, 'F'): Update Reference architecture with UPF SBI Samsung Rel-17 Revised to S2-2106545. Laurent (Nokia): provides r01
Hyunsook (LGE) asks a question on roaming case.
Runze (Huawei) agrees with Hyunsook (LGE) and provides r02.
Stefan (Ericsson) also agrees and supports r02
Hyunsook (LGE) supports r02.
Kisuk (Samsung) is ok with r02.
Runze (Huawei) provides r03.
Kisuk (Samsung) fine with r03.
Dan (China Mobile) also fine with r03. But suggest when upload the paper, the changing for removing the new figure(new added 4.2.3-1) should be removed to avoid the misunderstanding.
Kisuk (Samsung) provides r04.
Runze (Huawei) supports r04.
Laurent (Nokia): objects to R00 up to R02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2106545 CR Approval 23.501 CR3213R1 (Rel-17, 'F'): Update Reference architecture with UPF SBI Samsung Rel-17 Revision of S2-2106403r04. Approved Agreed
6.2 - - - Common Access Control, RM and CM functions and procedure flows - - Docs:=15 -
6.2 S2-2105258 LS In Action LS from CT WG4: Reply LS on Group Subscriptions CT WG4 (C4-213379) Rel-15 Response drafted in S2-2106038. Final response in S2-2106546
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
6.2 S2-2106038 LS OUT Approval [DRAFT] Reply LS on Group Subscriptions Huawei, HiSilicon Rel-15 Response to S2-2105258. Revised to S2-2106546.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106546 LS OUT Approval Reply LS on Group Subscriptions SA WG2 Rel-15 Revision of S2-2106038r00. Approved Approved
6.2 S2-2105814 CR Approval 23.502 CR2991 (Rel-17, 'F'): Direct event subscription from NEF Ericsson Rel-17 Noted Qianghua (Huawei) proposes to note this CR since NEF cannot directly subscribe PDU session status event on SMF.
Qian (Ericsson) provides response to Qianghua (Huawei) and provide r01.
Qianghua (Huawei) still proposes to note the CR
Hannu (Nokia) proposes to keep the AMF call flow as it stands and to isolate the SMF specific steps to a different call flow if a valid condition to direct SMF subscription can be identified.
Qian (Ericsson) provides response and r02.
Qian (Ericsson) provides further comments.
Qianghua (Huawei) asks questions further
Hannu (Nokia) replies to Qian (Ericsson)
Qianghua (Huawei) objects this CR and its revisions
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.2 S2-2105815 CR Approval 23.502 CR2992 (Rel-16, 'F'): Initial event reporting during event subscription Ericsson, Verizon Rel-16 CC#2: r02 + changes agreed. Revised to S2-2106687. Hannu (Nokia) supports the immediate notification principle and provides r01.
Qian (Ericsson) comments and provides r02.
Qianghua(Huawei) comments
Qian (Ericsson) comments and provide r04 (please ignore r03)
Qianghua(Huawei) OK for r04
Qianghua (Huawei) we can confirm the small fix on top of r02, if needed at CC#2
Hannu (Nokia) thanks Qiand and Qianghua for improvements on this CR and proposes to ask for support of r04 in CC.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106687 CR Approval 23.502 CR2992R1 (Rel-16, 'F'): Initial event reporting during event subscription Ericsson, Verizon Rel-16 Revision of S2-2105815r02 + changes. Approved Agreed
6.2 S2-2105816 CR Approval 23.502 CR2993 (Rel-17, 'A'): Initial event reporting during subscription Ericsson, Verizon Rel-17 CC#2: Aligned with S2-2106687. Revised to S2-2106688.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106688 CR Approval 23.502 CR2993R1 (Rel-17, 'A'): Initial event reporting during subscription Ericsson, Verizon Rel-17 Revision of S2-2105816. Approved Agreed
6.2 S2-2105871 CR Approval 23.501 CR3104 (Rel-17, 'F'): Correction of 5G-EIR Discovery and Selection to select the specific 5G-EIR for the access type or RAT type Rakuten Mobile, Inc Rel-17 Noted Josep (DT) asks questions for clarification.
Aoken (Rakuten Mobile) answers the questions.
Josep (DT) replies, comments.
Aoken (Rakuten Mobile) replies to clarify the use case.
Haris (Qualcomm) comments and asks question
Aoken (Rakuten Mobile) answers to the question.
Josep (DT) proposes to note this CR.
Aoken (Rakuten Mobile) answers to the comment and provides the r01
Runze (Huawei) agrees with Joseph (DT).
Hannu (Nokia) supports the proposal to note the CR and provides further explanation.
Josep (DT) objects to this CR.
Aoken (Rakuten Mobile) comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.2 S2-2106202 CR Approval 23.502 CR3059 (Rel-16, 'F'): Inter-AMF mobility with group monitoring Nokia, Nokia Shanghai Bell Rel-16 Revised to S2-2106547. Qianghua (Huawei) provides comments and r01
Hannu (Nokia) can live with r01 but asks what's the difference between the original version and r01?
Qianghua (Huawei) OK with r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106547 CR Approval 23.502 CR3059R1 (Rel-16, 'F'): Inter-AMF mobility with group monitoring Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2106202r01. Approved Agreed
6.2 S2-2106203 CR Approval 23.502 CR3060 (Rel-17, 'A'): Inter-AMF mobility with group monitoring Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106548.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106548 CR Approval 23.502 CR3060R1 (Rel-17, 'A'): Inter-AMF mobility with group monitoring Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106203r00. Approved Agreed
6.2 S2-2106464 CR Approval 23.502 CR3110 (Rel-17, 'F'): Updating AMF with new Routing Indicator Data if re-registration is not triggered Apple Rel-17 Revised to S2-2106549. Josep (DT) asks questions for clarification.
Fenqin (Huawei) asks similar question.
Hannu (Nokia) asks which tool was used to draw the updated Figure?
Krisztian (Apple) responds to Josep and Fenqin.
Krisztian (Apple) responds to Hannu.
Josep (DT) says thanks for the clear reference and r01. Proposes minor additions in r02.
Fenqin (Huawei) fine with the change.
Qian (Ericsson) asks further questions.
Hannu (Nokia) is OK with r02.
Krisztian (Apple) is fine with r02.
Krisztian (Apple) responds to Qian.
Qian (Ericsson) comments.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2106549 CR Approval 23.502 CR3110R1 (Rel-17, 'F'): Updating AMF with new Routing Indicator Data if re-registration is not triggered Apple Rel-17 Revision of S2-2106464r02. Approved Agreed
6.3 - - - Session management and continuity functions and flows - - Docs:=26 -
6.3 - - - UPF support for multiple slices - - Docs:=10 -
6.3 S2-2105318 CR Approval 23.502 CR2886 (Rel-17, 'F'): Nnssf_NSSAIAvailability service clarification Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.3 S2-2105240 LS In Action LS from CT WG4: LS on UPF support for multiple network slices CT WG4 (C4-212560) Rel-17 Revision of postponed S2-2103766 from S2-145E. Responses drafted in S2-2105533 and S2-2106193. Final response in S2-2106550
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
6.3 S2-2105302 LS In Information LS from SA WG5: Reply LS on UPF support for multiple slices SA WG5 (S5-213447) Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2105533 LS OUT Approval [DRAFT] Reply LS on UPF support for multiple network slices Ericsson Rel-17 Response to S2-2105240. Merged into S2-2106550 Laurent (Nokia): suggests that we start from Tdoc 6193 to answer to CT4
Yubing (China Telecom): agrees with Nokia and suggest to use S2-2106193 as discussion baseline.
Runze (Huawei) supports the view from China Telecom and Nokia.
Stefan (Ericsson) OK to use 6193 as a base
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
6.3 S2-2106193 LS OUT Approval [DRAFT] Reply LS on UPF support for multiple network slices China Telecommunications Rel-17 Response to S2-2105240. Revised to S2-2106550, merging S2-2105533 Laurent (Nokia): Provides r01
Yubing (China Telecom) is ok with r01
Runze (Huawei) comments.
Stefan (Ericsson) comments and provides r02
Runze (Huawei) provides r03.
Josep (DT) provides r04.
Runze (Huawei) supports r04.
Yubing (China Telecom) is ok with r04.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.3 S2-2106550 LS OUT Approval Reply LS on UPF support for multiple network slices SA WG2 Rel-17 Revision of S2-2106193r04, merging S2-2105533. Approved Approved
6.3 S2-2105532 DISCUSSION Approval Analysis of CT WG4's options to support multiple slices in UPF . Ericsson Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2106401 DISCUSSION Information Analysis of solutions to support multiple slices in UPF related to CT WG4's LS (S2-2105240). China Telecom, ZTE Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2105396 CR Approval 23.501 CR3010 (Rel-17, 'C'): Allowing usage of S-NSSAI and Network Instance for internal UPF resource allocation Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106551. Runze (Huawei) provides comments
Laurent (Nokia): provides r02
Andy (Samsung, VC): the revision provided by Nokia was r01.
Runze (Huawei) supports either original version or r01, and prefers original CR.
Yubing (China Telecom) is ok with both original version and r01, and please add China Telecom as the support company.
Stefan (Ericsson) comments and provides r02
Runze (Huawei) comments on r02 and provide r03.
DongEun (Samsung) asks for a clarification.
Laurent (Nokia): answers
Yubing (China Telecom) supports r03 and please add China Telecom as the co-signer.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.3 S2-2106551 CR Approval 23.501 CR3010R1 (Rel-17, 'C'): Allowing usage of S-NSSAI and Network Instance for internal UPF resource allocation Nokia, Nokia Shanghai Bell, China Telecom Rel-17 Revision of S2-2105396r03. Approved Agreed
6.3 - - - Simultaneous uplink/downlink data race condition - - Docs:=4 -
6.3 S2-2105932 CR Approval 23.502 CR3010 (Rel-16, 'F'): Racing condition between simultaneous uplink and downlink data Huawei, HiSilicon Rel-16 6.3 is not a WI Code, Should be 5GS_Ph1. Postponed Stefan (Ericsson) comments and provides r01
Laurent (Nokia): Comments
Ouyang(Huawei) replies to Stefan (Ericsson).
Stefan (Ericsson) replies
Stefan (Ericsson) replies to Ouyang
Ouyang(Huawei) replies to Stefan and provide r02.
Stefan (Ericsson) cannot accept r02.
Ouyang(Huawei) replies to Stefan and provide r03.
Haris (Qualcomm) indicates that RAN box should not be ticked
Ouyang(Huawei) provides r04.
Stefan (Ericsson) comments and provides r05
Tyler (OTD) comments and supports r05 (or r01)
Ouyang(Huawei) cannot accept r05.
Stefan (Ericsson) replies to Ouyang. Can only accept r01 or r05. Objects to all other revisions.
Ouyang(Huawei) can't accept either r01 and r05. Suggest to postpone this discussion.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.3 S2-2105933 CR Approval 23.502 CR3011 (Rel-17, 'A'): Racing condition between simultaneous uplink and downlink data Huawei, HiSilicon Rel-17 6.3 is not a WI Code, Should be 5GS_Ph1. Postponed Ouyang(Huawei) provides r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.3 S2-2105934 DISCUSSION Agreement Discussion of racing condition between simultaneous uplink and downlink data Huawei, HiSilicon Rel-16 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2105935 LS OUT Approval [DRAFT] LS on racing condition between simultaneous uplink and downlink data Huawei, HiSilicon Rel-16 Noted Stefan (Ericsson) questions the need for this LS
Laurent (Nokia): Supports Stefan that the LS is not needed
Ouyang(Huawei) replies to Laurent (Nokia) and Stefan (Ericsson)
Haris (Qualcomm) proposes to NOTE the draft LS
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 - - - Other - - Docs:=12 -
6.3 S2-2105297 LS In Information Reply-LS on the Security consideration to support L2TP with CUPS SA WG3 (S3-212365) Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2105534 CR Approval 23.502 CR2931 (Rel-17, 'F'): Corrections to L2TP call flow Ericsson Rel-17 CC#2: Alignment with S2-2106693 should be included. Revised to S2-2106552. Runze (Huawei) comments.
Stefan (Ericsson) replies to Runze and provides r01
Runze (Huawei) supports r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.3 S2-2106552 CR Approval 23.502 CR2931R1 (Rel-17, 'F'): Corrections to L2TP call flow Ericsson Rel-17 Revision of S2-2105534r01. Approved Agreed
6.3 S2-2105583 CR Approval 23.502 CR2939 (Rel-15, 'F'): Correction of the ' Notification of User Plane Management Events' procedure KDDI Rel-15 Noted Mirko (Huawei) asks whether a Rel-15 change is really necessary
Koji (KDDI) responds to Mirko (Huawei).
Laurent (Nokia): objects to 5583
Koji (KDDI) responds and proposes.
Laurent (Nokia): answers; I objected only for the R15 CR so we should have a 'Cat-F for Rel-16' (and not Cat A) and 'Cat-A for Rel-17'
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2105584 CR Approval 23.502 CR2940 (Rel-16, 'A'): Correction of the ' Notification of User Plane Management Events' procedure KDDI Rel-16 Should be Cat 'F'. Revised to S2-2106553.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.3 S2-2106553 CR Approval 23.502 CR2940R1 (Rel-16, 'F'): Correction of the ' Notification of User Plane Management Events' procedure KDDI Rel-16 Revision of S2-2105584r00. Approved Agreed
6.3 S2-2105585 CR Approval 23.502 CR2941 (Rel-17, 'A'): Correction of the ' Notification of User Plane Management Events' procedure KDDI Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.3 S2-2105662 CR Approval 23.502 CR2947 (Rel-17, 'F'): Correction to UE or network requested PDU Session Release for Home-routed Roaming Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.3 S2-2106114 CR Approval 23.502 CR3038 (Rel-16, 'F'): DN-AAA triggered re- authorization/authentication Huawei, HiSilicon Rel-16 Noted Stefan (Ericsson) comments
Laurent (Nokia): provides r01
Stefan (Ericsson) provides r02
Fenqin (Huawei) provides r03
Ashok (Samsung) comments
Fenqin (Huawei) propose to withdraw this paper
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2106115 CR Approval 23.502 CR3039 (Rel-17, 'A'): DN-AAA triggered re- authorization/authentication Huawei, HiSilicon Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 S2-2106512 CR Approval 23.502 CR3117 (Rel-16, 'F'): RAN-triggered PDU Session Release Samsung Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.3 S2-2106513 CR Approval 23.502 CR3118 (Rel-17, 'A'): RAN-triggered PDU Session Release Samsung Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.4 - - - Security related functions and flows - - Docs:=0 -
6.5 - - - QoS concept and functionality - - Docs:=4 -
6.5 S2-2105660 CR Approval 23.501 CR3056 (Rel-16, 'F'): Derivation of UL Packet Filter from DL encapsulated IPsec protected packet Ericsson Rel-16 Revised to S2-2106554. Haiyang(Huawei) seeks for clarification
Judy (Ericsson) responds to Haiyang(Huawei)
Haiyang(Huawei) provides r01
Judy (Ericsson) provides r02
Haiyang(Huawei) is ok with r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.5 S2-2106554 CR Approval 23.501 CR3056R1 (Rel-16, 'F'): Derivation of UL Packet Filter from DL encapsulated IPsec protected packet Ericsson Rel-16 Revision of S2-2105660r02. Approved Agreed
6.5 S2-2105661 CR Approval 23.501 CR3057 (Rel-17, 'A'): Derivation of UL Packet Filter from DL encapsulated IPsec protected packet Ericsson Rel-17 Revised to S2-2106555.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.5 S2-2106555 CR Approval 23.501 CR3057R1 (Rel-17, 'A'): Derivation of UL Packet Filter from DL encapsulated IPsec protected packet Ericsson Rel-17 Revision of S2-2105661r00. Approved Agreed
6.6 - - - Policy and charging control - - Docs:=25 -
6.6 - - - URSP Traffic Descriptor - - Docs:=8 -
6.6 S2-2105243 LS In Action LS from GSMA 5GJA: LS to 3GPP SA2 on URSP Traffic Descriptor GSMA 5GJA (5GJA16_109r2) Rel-17 Revision of postponed S2-2103774 from S2-145E. Responses drafted in S2-2105422 and S2-2106316. Final response in S2-2106556
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
6.6 S2-2105422 LS OUT Approval [DRAFT] LS reply to GSMA on URSP Traffic Descriptor Ericsson Rel-17 Response to S2-2105243. Revised to S2-2106556, merging S2-2106316 Dieter (Deutsche Telekom) provides r01.
Pinghui(China Telecom) prefers r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106556 LS OUT Approval LS reply to GSMA on URSP Traffic Descriptor SA WG2 Rel-17 Revision of S2-2105422r01, merging S2-2106316. Approved Approved
6.6 S2-2105421 CR Approval 23.503 CR0607 (Rel-17, 'C'): DNN in URSP Traffic Descriptor and Route Selection Descriptor Ericsson, AT&T Rel-17 r01 + CC#2 changes agreed. Revised to S2-2106557, merging S2-2106330 Mike (Convida Wireless) asks a question
Sherry (Xiaomi) comments.
Mirko (Huawei) responds to the comments and provides r01.
Alessio(Nokia) provides comments.
Myungjune (LGE) provides comments.
Hong (Qualcomm) comments and provides r02.
Alessio(Nokia)) provides comments.
Belen (Ericsson) is okay with r02 and also r01.
Dieter (Deutsche Telekom) is okay with r02 and also r01 and would like to co-sign and asks whether LS to CT1 is needed.
Alessio(Nokia) asks a question on r02
Mike (Convida Wireless) has concerns with r02
Belen (Ericsson) provides r04.
Hong (Qualcomm) comments.
Mike (Convida Wireless) comments and indicates a preference for r00 or r01
Hong (Qualcomm) replies to Sherry (Xiaomi).
Alessio(Nokia) comments that it is not a misconfigured UE that would use a different DNN, rather a UE that uses the DNN in the TD as it should as per rel-15/16. let's find a way forward and discuss in CC#2 as it seems we miss more documentation aspects .
Krisztian (Apple) prefers r01 for now. Once CT1 adopts this feature, we could further update the text and change to a reference of TS 24.526 for completeness.
Pinghui(China Telecom) prefers r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Belen (Ericsson) provides r02 in draft folder for CC#2
Revised
6.6 S2-2106557 CR Approval 23.503 CR0607R1 (Rel-17, 'C'): DNN in URSP Traffic Descriptor and Route Selection Descriptor Ericsson, AT&T, Deutsche Telekom, China Telecom, Convida Wireless, Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105421r01 + CC#2 changes, merging S2-2106330. Approved Agreed
6.6 S2-2106316 LS OUT Approval [DRAFT] Reply LS from GSMA 5GJA on URSP Traffic Descriptor China Telecommunications Rel-17 Response to S2-2105243. Merged into S2-2106556 Belen (Ericsson) proposes to merge this Reply LS into S2-2105422.
Pinghui(China Telecom) is OK to merge this CR into S2-2105422
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
6.6 S2-2106330 CR Approval 23.503 CR0646 (Rel-17, 'C'): DNN Selection and match in URSP China Telecom Rel-17 Merged into S2-2106557 Belen (Ericsson) proposes to merge this CR into S2-2105421
Farooq (AT&T) agrees with E/// to merge this CR into S2-2105421
Pinghui(China Telecom) is OK to merge this CR into S2-2105421
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
6.6 S2-2106283 CR Approval 23.503 CR0645 (Rel-17, 'F'): Indication of default URSP rule not applicable for the application MediaTek Inc., Google, Intel Rel-17 Noted Pallab (Nokia): comments and requests for clarification
Guillaume (MediaTek) replies to Pallab (Nokia).
Myungjune (LGE) comments.
Gerald (Matrixx) with charging comment.
Haiyang (Huawei) comments and requests for clarification.
Dan(China Mobile) suggest to change normative text into a NOTE
Pallab (Nokia): provides further comments
Guillaume (MediaTek) replies.
Pallab (Nokia): asks further questions.
Belen (Ericsson) supports adding a NOTE if anything is to be clarified.
Pallab (Nokia): suggests to move this CR to AI #6.6 (as WI code is 5GS_Ph1 & TEI17) and also NOTE this CR as it is not a CAT F correction.
Guillaume (MediaTek) is surprised about the comment.
Guillaume (MediaTek) provides r01.
Hong (Qualcomm) comments.
Krisztian (Apple) shares the comments raised by Hong.
Pallab (Nokia): Objects to both r01 and initial version. Shares views with Krisztian (Apple), Hong (Qualcomm)
Guillaume (MediaTek): ok to note the CR
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.6 - - - Other - - Docs:=17 -
6.6 S2-2105255 LS In Action LS from CT WG3: LS on Clarifications on the offline charging only indication CT WG3 (C3-213546) Rel-17 Response drafted in S2-2106150. Final response in S2-2106558
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
6.6 S2-2106150 LS OUT Approval [DRAFT] LS Reply on the offline charging only indication Huawei, HiSilicon Rel-17 Response to S2-2105255. Revised to S2-2106558. Gerald (Matrixx) with comments
Belen (Ericsson) provides r01
Gerald (Matrixx) provides r02 with the comment to holt the CR till final clarification.
Haiyang(Huawei) provides a comment on Answer 3 of r01/r02, and provides r03.
Gerald (Matrixx) with comments.
Haiyang(Huawei) provides response.
Belen (Ericsson) provides r04, objects to r03.
Haiyang(Huawei) provides r05.
Gerald (Matrixx) with more background.
Gerald (Matrixx) supports r04 with comments.
Gerald (Matrixx) supports r05 as well.
Belen (Ericsson) provides r06
Haiyang(Huawei) is ok with r06.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106558 LS OUT Approval LS Reply on the offline charging only indication SA WG2 Rel-17 Revision of S2-2106150r06. Approved Approved
6.6 S2-2106151 CR Approval 23.503 CR0639 (Rel-17, 'F'): Clarifications on offline charging only indication Huawei, HiSilicon Rel-17 Revised to S2-2106559. Belen (Ericsson) provides r01
Gerald (Matrixx) with a question for clarification.
Haiyang (Huawei) provides r02
Gerald (Matrixx) with comment.
Haiyang (Huawei) suggests to endorse r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106559 CR Approval 23.503 CR0639R1 (Rel-17, 'F'): Clarifications on offline charging only indication Huawei, HiSilicon Rel-17 Revision of S2-2106151r02. CC#2: Endorsed Endorsed
6.6 S2-2105227 LS In Action LS from CT WG3: LS on Session Management Policy Data per PLMN CT WG3 (C3-211469) Revision of postponed S2-2103722 from S2-145E. Response drafted in S2-2105703. Final response in S2-2106560
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
6.6 S2-2105703 LS OUT Approval [DRAFT] LS Reply on Session Management Policy Data per PLMN Huawei, HiSilicon Rel-17 Response to S2-2105227. Revised to S2-2106560. Gerald (Matrixx) suggest a rewording.
Haiyang(Huawei) clarifies to Gerald (Matrixx).
Gerald (Matrixx) with comment.
Gerald (Matrixx) with a better way forward in r01.
Haiyang(Huawei) is OK with r01 and correct the link.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106560 LS OUT Approval LS Reply on Session Management Policy Data per PLMN SA WG2 Rel-17 Revision of S2-2105703r01. Approved Approved
6.6 S2-2105704 CR Approval 23.502 CR2959 (Rel-17, 'F'): Clarification on Session Management Policy Data per PLMN Huawei, HiSilicon, Ericsson Rel-17 Revised to S2-2106561. Gerald (Matrixx) suggest a rewording.
Haiyang(Huawei) clarifies to Gerald (Matrixx).
Gerald (Matrixx) with comment.
Haiyang(Huawei) suggests a way forward.
Gerald (Matrixx) with a better way forward in r01.
Haiyang(Huawei) is OK with r01.
Biao(China Telecom) supports this CR and requests to add China Telecom as the co-signer if it is possible.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106561 CR Approval 23.502 CR2959R1 (Rel-17, 'F'): Clarification on Session Management Policy Data per PLMN Huawei, HiSilicon, Ericsson, China Telecom Rel-17 Revision of S2-2105704r01. Approved Agreed
6.6 S2-2105700 CR Approval 23.501 CR3064 (Rel-17, 'F'): Corrections on the AF related identifier Huawei, HiSilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.6 S2-2105701 CR Approval 23.502 CR2958 (Rel-17, 'F'): Corrections on the AF related identifier Huawei, HiSilicon Rel-17 Revised to S2-2106562. Belen (Ericsson) asks question for clarification
Haiyang(Huawei) responds to Belen (Ericsson)
Pallab (Nokia): requests for clarification
Haiyang(Huawei) responds to Pallab(Nokia)
Belen (Ericsson) replies to Huawei, thinks also that removing AF Application Identifier will cause backward compatibility issues.
Haiyang(Huawei) further responds to Belen (Ericsson)
Pallab(Nokia) responds to Haiyang(Huawei)
Pallab(Nokia) provides r01
Haiyang(Huawei) further responds to Pallab(Nokia)
Belen (Ericsson) replies to Huawei and states that AF Applicatin Identifier cannot be removed.
Haiyang(Huawei) is OK with r01
Belen (Ericsson) provides r02, objects to r01 and initial revision
Haiyang(Huawei) is also OK with r02
Pallab (Nokia) OK with r02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106562 CR Approval 23.502 CR2958R1 (Rel-17, 'F'): Corrections on the AF related identifier Huawei, HiSilicon Rel-17 Revision of S2-2105701r02. Approved Agreed
6.6 S2-2105702 CR Approval 23.503 CR0619 (Rel-17, 'F'): Corrections on the AF related identifier Huawei, HiSilicon Rel-17 Revised to S2-2106563. Belen (Ericsson) provides r02
Pallab (Nokia) asks for clarification to Belen (Ericsson). Also corrects for Chair's notes that latest revision is r01 (not r02)
Belen (Ericsson) replies to Nokia questions
Pallab (Nokia) provides r02
Haiyang (Huawei) provides r03
Pallab (Nokia) comments on r03
Belen (Ericsson) objects to all revisions and asks to note or postpone this CR
Haiyang (Huawei) provides r04 for consideration
Belen (Ericsson) asks about r04
Haiyang (Huawei) clarifies to Belen (Ericsson)
Belen (Ericsson) objects to r04
Pallab (Nokia) comments on r04
Haiyang (Huawei) clarifies and provides r05
Pallab (Nokia) asks for clarification to Haiyang (Huawei)
Belen (Ericsson) cannot accept r05.
Haiyang (Huawei) provides r06
Belen (Ericsson) provides r07
Mirko (Huawei) provides r08
Belen (Ericsson) replies and objects to r08
Belen (Ericsson) can accept r07, objects to r08 and any other revision.
Haiyang (Huawei) is OK with r07
Pallab (Nokia) is OK with r07
Belen (Ericsson) asks Huawei and Nokia
Pallab (Nokia) responds to Belen (Ericsson)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2106563 CR Approval 23.503 CR0619R1 (Rel-17, 'F'): Corrections on the AF related identifier Huawei, HiSilicon Rel-17 Revision of S2-2105702r07. Approved Agreed
6.6 S2-2106142 CR Approval 23.502 CR3041 (Rel-16, 'F'): Usage monitoring for a user in SSC mode #3 Nokia, Nokia Shanghai Bell Rel-16 Postponed Haiyang(Huawei) provides a comment
Pallab (Nokia) clarifies to Haiyang(Huawei)
Belen (Ericsson) provides comments and asks questions.
Pallab (Nokia) responds to Belen (Ericsson)
Haiyang(Huawei) provides his view
Pallab (Nokia) responds to Haiyang(Huawei)
Pallab (Nokia) requests Belen (Ericsson) to propose another solution that works if none of the solutions discussed is acceptable
Belen (Ericsson) objects to the initial version of the CR, and provides comments
Belen (Ericsson) states that we are discussung anoter solution, if no agreement we can postpone for next meeting
Jinguo(ZTE) comments
Haiyang(Huawei) clarifies and provides r01.
Belen (Ericsson) objexts to r01 and initial version.
Pallab (Nokia) is OK r01 and requests Ericsson to reconsider its position or propose an alternative solution.
Belen (Ericsson) mantains objection to r01 and r00 and ask to postpone.
Pallab (Nokia) agrees to Postpone this CR for further analysis
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.6 S2-2106143 CR Approval 23.502 CR3042 (Rel-17, 'A'): Usage monitoring for a user in SSC mode #3 Nokia, Nokia Shanghai Bell Rel-17 Postponed
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.7 - - - 3GPP access specific functionality and flows - - Docs:=2 -
6.7 S2-2106492 CR Approval 23.501 CR3230 (Rel-17, 'F'): Overlapping LADN Service area Samsung Rel-17 Revised to S2-2106564. Hui(Huawei) provides r01.
Lalith(Samsung) provides r02.
Haris(Qualcomm) comments and provides r03
Lalith(Samsung) is OK with r03
Hui(Huawei) provides r04
Lalith(Samsung) is OK with r04
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.7 S2-2106564 CR Approval 23.501 CR3230R1 (Rel-17, 'F'): Overlapping LADN Service area Samsung Rel-17 Revision of S2-2106492r04. Approved Agreed
6.8 - - - Specific services support - - Docs:=8 -
6.8 S2-2105382 CR Approval 23.167 CR0365 (Rel-17, 'F'): Usage of alternate P-CSCF for emergency registration Nokia, Nokia Shanghai-Bell, Ericsson, AT&T, FirstNet Rel-17 Approved Haris(Qualcomm) proposes to note the CR and resolve the issue in TS 24.229
Leo (Deutsche Telekom) supports the changes proposed by this CR.
Thomas(Nokia) replies to Harris
George (Ericsson) agrees with Thomas. These wording led to the need for a change here.
Susan (Huawei) provides r01.
Thomas(Nokia) accepts r01.
Haris (Qualcomm) comments on r01
George (Ericsson) provides a response.
Thomas(Nokia) replies to Haris
Thomas (Nokia) provides a response.
George (Ericsson) co-signed the 00. So we are definitely OK with it
Haris (Qualcomm) can live with r00 after the discussion
Susan (Huawei) is ok with r00.
James Hu (AT&T) as a co-signer is certainly OK with r00
Thomas (Nokia) is fine with r00 and replies to Harris
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.8 S2-2106206 CR Approval 23.502 CR3061 (Rel-15, 'F'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-15 Revised to S2-2106565. George Foti (Ericsson) provides r01. I don't see a need for the second change.
Leo (Deutsche Telekom) comments on original version and r01.
Hannu (Nokia) responds to George and Leo and provides r02.
Leo (Deutsche Telekom) is fine with r02.
George (Ericsson) OK with r02.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2106565 CR Approval 23.502 CR3061R1 (Rel-15, 'F'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-15 Revision of S2-2106206r02. Approved Agreed
6.8 S2-2106207 CR Approval 23.502 CR3062 (Rel-16, 'A'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-16 Revised to S2-2106566. George Foti (Ericsson) provides a comment.
Leo (Deutsche Telekom) provides a comment. We can approve r00, but not only Cat has to be changed to F, also the WI code needs to be updated.
Hannu (Nokia) supports the WI coding comment from Leo (Deutsche Telekom), but questions whether Cat F would be appropriate as this is a genuine mirror CR?
Leo (Deutsche Telekom) provides comments and is fine with Cat A
George (Ericsson) would accept an exact mirror of S2-2106206r02.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Hannu (Nokia) agrees and thanks Leo for verifying the details.
Revised
6.8 S2-2106566 CR Approval 23.502 CR3062R1 (Rel-16, 'A'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2106207r00. Approved Agreed
6.8 S2-2106208 CR Approval 23.502 CR3063 (Rel-17, 'A'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106567. George Foti (Ericsson) comments. Please see 6207
Hannu (Nokia) agrees with George that even though two candidate solutions have been identified, Cat A CRs in 6207 and 6208 should follow the same principle as the agreed Cat F CR that is being discussed in document 6206.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2106567 CR Approval 23.502 CR3063R1 (Rel-17, 'A'): Dual Access Type SMS registration Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106208r00. Approved Agreed
6.8 S2-2106516 CR Approval 23.502 CR3119 (Rel-17, 'F'): EPS fallback for a UE moving from EPS to 5GS with a bearer for IMS voice . Samsung Rel-17 Noted George Foti (Ericsson) provides comments
Myungjune (LGE) provides comments.
Fei (OPPO) comments.
Leo (Deutsche Telekom) requests clarification.
Haris (Qualcomm) proposes to note
zhendong(ZTE), proposes to note this CR
Susan (Huawei) proposes to note this CR.
Jungshin (Samsung) provides clarification on the issue.
Hannu (Nokia) proposes to note the CR.
Jungshin (Samsung) provides response to Nokia comment..
zhendong(ZTE), provides the response
Jungshin (Samsung) provides response to ZTE (Zhendong).
zhendong(ZTE), provides the comments
Jungshin (Samsung) replies to LGE Myungjune.
Jungshin (Samsung) replies to ZTE (Zhendong) comment.
Leo (Deutsche Telekom) objects this CR, please note.
Jungshin (Samsung) is ok to note the CR to have more discussion.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 - - - Interworking and Migration - - Docs:=21 -
6.9 S2-2105391 CR Approval 23.502 CR2858R1 (Rel-17, 'B'): 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage Vodafone Rel-17 Revision of (Postponed) S2-2104684from S2-145E. Revised to S2-2106568. Laurent (Nokia): asks a question
Qian (Ericsson) comments and provides r01
Chris is OK with Nokia's comment and Ericsson's r01. Chris provides r02 as a clean version.
Irfan (Cisco) adds BSS_Container in r03
Laurent (Nokia): objects to R00 and R01
Irfan (Cisco) supports r03 and requests to add Cisco as co-signer.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106568 CR Approval 23.502 CR2858R2 (Rel-17, 'B'): 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage Vodafone Rel-17 Revision of S2-2105391r03. Approved Agreed
6.9 S2-2105580 DISCUSSION Information Enabling 2G3G<->4G IWK in 5GS. Cisco Systems Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2105581 CR Approval 23.501 CR3044 (Rel-17, 'F'): Updates to enable mobility between GERAN/UTRAN and E-UTRAN in 5GS Cisco Systems Rel-17 Revised to S2-2106569. Qian (Ericsson) provides comments and propose to NOTE the paper
Irfan (Cisco) provides r01
Qian (Ericsson) provides comments related to new proposal.
Irfan (Cisco) provides comments.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106569 CR Approval 23.501 CR3044R1 (Rel-17, 'F'): Updates to enable mobility between GERAN/UTRAN and E-UTRAN in 5GS Cisco Systems Rel-17 Revision of S2-2105581r01. Approved Agreed
6.9 S2-2105582 CR Approval 23.502 CR2938 (Rel-17, 'F'): Updates to enable mobility between GERAN/UTRAN and E-UTRAN in 5GS Cisco Systems Rel-17 Noted Qian (Ericsson) provides comments and proposes to NOTE the paper (same reason as stated in 5581)
Irfan (Cisco) is OK to NOTE this CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2105654 CR Approval 23.502 CR2755R1 (Rel-15, 'F'): Correction to EPS bearer ID transfer Ericsson Rel-15 Revision of (Postponed) S2-2103969 from S2-145E. Revised to S2-2106570. Chris (Vodafone) comments.
Judy (Ericsson) provide r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106570 CR Approval 23.502 CR2755R2 (Rel-15, 'F'): Correction to EPS bearer ID transfer Ericsson Rel-15 Revision of S2-2105654r01. Approved Agreed
6.9 S2-2105655 CR Approval 23.502 CR2751R1 (Rel-16, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-16 Revision of (Postponed) S2-2103943 from S2-145E. Revised to S2-2106571.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106571 CR Approval 23.502 CR2751R2 (Rel-16, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-16 Revision of S2-2105655r00. Approved Agreed
6.9 S2-2105656 CR Approval 23.502 CR2752R1 (Rel-17, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-17 Revision of (Postponed) S2-2103944 from S2-145E. Revised to S2-2106572.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106572 CR Approval 23.502 CR2752R2 (Rel-17, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-17 Revision of S2-2105656r00. Approved Agreed
6.9 S2-2105663 CR Approval 23.502 CR2948 (Rel-17, 'C'): N1 mode capability disabled/enabled and interworking between EPC/ePDG and 5GS Ericsson, AT&T, Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106573. Haris(Qualcomm) indicates that if the CR is to be approved the text in new clause of 4.11.4.3.x related to deletion of PDN connections without a mapped S-NSSAI has to be aligned with stage-3
Judy (Ericsson) comments that the proposed update from Haris(Qualcomm) is not consistent with stage 3 TS 24.501.
Irfan (Cisco) provides r01
Haris (Qualcomm) provides r02
Judy (Ericsson) provide r04, please ignore r03.
Irfan (Cisco) provides r05 that includes changes from r01.
Judy (Ericsson) thanks Irfan and is fine with r05.
Laurent (Nokia): provides r06
Judy (Ericsson) provides r07
Haris (Qualcomm) is ok with rev7 but changes in clause 2 not needed anymore
Judy (Ericsson) provide r08
Laurent (Nokia): provides r09
Judy (Ericsson) provide r10
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106573 CR Approval 23.502 CR2948R1 (Rel-17, 'C'): N1 mode capability disabled/enabled and interworking between EPC/ePDG and 5GS Ericsson, AT&T, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105663r10. Approved Agreed
6.9 S2-2106179 CR Approval 23.501 CR3164 (Rel-16, 'F'): Correction to subscription data updates for EPS/5GS interworking Samsung Rel-16 Noted Laurent (Nokia): makes a remark
Qian (Ericsson): fixed the tdoc number in the Subject (it should be 6179 instead of 6171).
DongYeon (Samsung) replies.
Laurent (Nokia): objects to any version of 6179 which is not FASMO
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2106191 CR Approval 23.501 CR3167 (Rel-17, 'A'): Correction to subscription data updates for EPS/5GS interworking Samsung Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2106194 CR Approval 23.502 CR3057 (Rel-16, 'F'): Session Management Subscription data for EPS/5GS interworking Samsung Rel-16 Revised to S2-2106574. Laurent (Nokia): provides r01
zhendong(ZTE), provdies r02
DongYeon (Samsung) provides r03.
Laurent (Nokia): provides r04
zhendong(ZTE), provides the comments
Qian (Ericsson) provides comments and r05
Fenqin (Huawei) agree with the r05 version.
Laurent (Nokia): objects to r00
DongYeon (Samsung) is fine with r05.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106574 CR Approval 23.502 CR3057R1 (Rel-16, 'F'): Session Management Subscription data for EPS/5GS interworking Samsung Rel-16 Revision of S2-2106194r05. Approved Agreed
6.9 S2-2106199 CR Approval 23.502 CR3058 (Rel-17, 'A'): Session Management Subscription data for EPS/5GS interworking Samsung Rel-17 Revised to S2-2106575. zhendong(ZTE), provides r01
DongYeon (Samsung) provides r02.
Fenqin (Huawei) provides comments.
Laurent (Nokia): I suggest we don't update the mirrors before the approval phase
zhendong(ZTE) provides the repsonse
DongYeon (Samsung) replies, and corrects the title of this thread.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2106575 CR Approval 23.502 CR3058R1 (Rel-17, 'A'): Session Management Subscription data for EPS/5GS interworking Samsung Rel-17 Revision of S2-2106199r00. Approved Agreed
6.9 S2-2106455 CR Approval 23.501 CR3222 (Rel-17, 'F'): Indicate the number of supported packet filters for signalled QoS rules only if the UE supports more than 16 packet filters for the PDU session Apple Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.10 - - - Non-3GPP access specific functionality and flows - - Docs:=2 -
6.10 S2-2105535 CR Approval 23.502 CR2932 (Rel-16, 'F'): Support for TCP source port in AMF event exposure of UE location Ericsson Rel-16 Postponed Apostolis (Lenovo) asks question for clarification.
Stefan (Ericsson) replies to Apostolis
Laurent (Nokia): cannot live with the CR at least for this meeting
Apostolis (Lenovo) replies to Stefan.
Laurent (Nokia): Supports Apostolis comments and objects to any revision of this document
Marco (Huawei) supports Apostolis (Lenovo) and Laurent (Nokia).
Laurent (Nokia): cannot live with the CR in 5535/5536 at least for this meeting
Stefan (Ericsson) OK to postpone
Laurent (Nokia): requires to POSTPONE this topic
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.10 S2-2105536 CR Approval 23.502 CR2933 (Rel-17, 'A'): Support for TCP source port in AMF event exposure of UE location Ericsson Rel-17 Postponed Laurent (Nokia): cannot live with the CR at least for this meeting
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.11 - - - Framework functions - - Docs:=1 -
6.11 S2-2105228 LS In Action LS from CT WG4: LS on update a Binding Indication for multiple contexts CT WG4 (C4-211709) Revision of postponed S2-2103726 from S2-145E. Postponed Thomas (Nokia) proposes to postpone this LS (again)
Comments that this relates to AI#7.8
Fenqin (Huawei) agree that we need postpone this LS again.
Youngkyo(Samsung) agree to postpone it.
Magnus (Ericsson) proposes to postpone this LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
7 - - - Rel-16 Maintenance for 5G (excluding 5GS_Ph1) - - Docs:=0 -
7.1 - - - Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) - - Docs:=7 -
7.1 S2-2105260 LS In Information LS from ITU-T SG16: LS on new work item on draft Recommendation ITU-T F.VG-VMA 'Architecture of vehicular multimedia systems' ITU-T SG16 (SG16-LS248) Noted LaeYoung (LGE) proposes to NOTE this incoming LS because this LS is just for information.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.1 S2-2105552 CR Approval 23.287 CR0158 (Rel-17, 'F'): Missing NEF in clause 4.4 Functional Entities Ericsson Rel-17 Revised to S2-2106576. LaeYoung (LGE) does not think that this CR is needed.
Judy (Ericsson) responds to LaeYoung (LGE)
LaeYoung (LGE) provides r01.
Judy (Ericsson) thanks LaeYoung and is fine with r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.1 S2-2106576 CR Approval 23.287 CR0158R1 (Rel-17, 'F'): Missing NEF in clause 4.4 Functional Entities Ericsson Rel-17 Revision of S2-2105552r01. Approved Agreed
7.1 S2-2105553 CR Approval 23.503 CR0613 (Rel-16, 'F'): UE Policy Container with V2X Policy Provisioning Request and alignment with stage 3 Ericsson, LG Electronics Rel-16 Noted Fei (OPPO) provides r01.
Judy (Ericsson) provides r02
LaeYoung (LGE) is OK with r02.
Mirko (Huawei) provides r03
LaeYoung (LGE) is OK with r03.
Judy (Ericsson) is fine with r03 too
Hong (Qualcomm) objects to all revision of the CR.
LaeYoung (LGE) is fine to postpone this CR.
Changhong (Intel) objects to all revision of the CR and clarifies why the CR is technically incorrect.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.1 S2-2105554 CR Approval 23.503 CR0614 (Rel-17, 'A'): UE Policy Container with V2X Policy Provisioning Request and alignment with stage 3 Ericsson, LG Electronics Rel-17 Noted Hong (Qualcomm) objects to all revision of the CR.
LaeYoung (LGE) is fine to postpone this CR.
Changhong (Intel) also propose to NOTE this paper.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.1 S2-2105573 CR Approval 23.287 CR0159 (Rel-16, 'F'): Alignment of UE Policy Container including V2X Policy Provisioning Request with stage 3 LG Electronics, Ericsson Rel-16 Noted Hong (Qualcomm) objects to all revision of the CR.
LaeYoung (LGE) is fine to postpone this CR.
Changhong (Intel) also proposes to NOTE this CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.1 S2-2105574 CR Approval 23.287 CR0160 (Rel-17, 'A'): Alignment of UE Policy Container including V2X Policy Provisioning Request with stage 3 LG Electronics, Ericsson Rel-17 Noted Hong (Qualcomm) objects to all revision of the CR.
LaeYoung (LGE) is fine to postpone this CR.
Changhong (Intel) also proposes to NOTE this CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.2 - - - Wireless and Wireline Convergence for the 5G system architecture (5WWC) - - Docs:=10 -
7.2 - - - BBF LS, including SSC modes for FN-RG - - Docs:=8 -
7.2 S2-2105358 LS In Action LS from BBF: Topics of concern to the BBF BBF (LIAISE-464) Responses drafted in S2-2105348 and S2-2105526. Final response in S2-2106577
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Replied to
7.2 S2-2105348 LS OUT Approval [DRAFT] LS on Topics of concern to the BBF Nokia, Nokia Shanghai Bell Response to S2-2105358. Merged into S2-2106577 Marco (Huawei) proposes to merge 5348 & 5526 providing comments for merging
Stefan (Ericsson) agrees that merching is needed and proposed a merged version in 5526r01
Laurent (Nokia): OK to merge in 5526
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
7.2 S2-2105526 LS OUT Approval [DRAFT] Reply LS on Topics of concern to the BBF Ericsson Response to S2-2105358. Revised to S2-2106577, merging S2-2105348 Marco (Huawei) proposes to merge 5348 & 5526. See email referring to 5348 for additional comments
Stefan (Ericsson) replies to Marco and provides r01
Laurent (Nokia): provides r02
Marco (Huawei) ask clarification for Q4
Marco (Huawei) replies
Apostolis (Lenovo) is fine with r02
Stefan (Ericsson) provides r03
Marco (Huawei) support r03
Laurent (Nokia): objects to any version other than R03
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.2 S2-2106577 LS OUT Approval Reply LS on Topics of concern to the BBF SA WG2 Rel-17 Revision of S2-2105526r03, merging S2-2105348. Approved Approved
7.2 S2-2105524 CR Approval 23.316 CR2057 (Rel-16, 'F'): SSC modes for FN-RG Ericsson Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2105525 CR Approval 23.316 CR2058 (Rel-17, 'A'): SSC modes for FN-RG Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2106232 CR Approval 23.316 CR2059 (Rel-16, 'F'): Clarification on SSC mode that different types of FN-RG can use Huawei, HiSilicon Rel-16 Noted Laurent (Nokia): if the group assumes a 23.316 CR is needed, prefers 5524 to 6232
Marco (Huawei) proposes revision merging 5524 & 6232 and provide answer to Laurent (Nokia)
Curt (Charter) asks for a clarification and suggests a NOTE instead.
Laurent (Nokia): answers
Marco (huawei) answers to Laurent (Nokia) and Curt (Charter)
Laurent (Nokia) answers Marco (huawei)
Stefan (Ericsson) comments
Curt (Charter) comments
Marco (Huawei) answers and provides r02
Laurent (Nokia): objects to any revision of 6232 (as anyhow 5524 is approved)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.2 S2-2106233 CR Approval 23.316 CR2060 (Rel-17, 'A'): Clarification on SSC mode that different types of FN-RG can use Huawei, HiSilicon Rel-17 Noted Marco (Huawei) proposes mirror revision of 6232 merging 5523 & 6233
Laurent (Nokia): Comments
Laurent (Nokia): objects to any revision of 6233 (as anyhow 5525 is approved)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.2 - - - Other - - Docs:=2 -
7.2 S2-2106234 CR Approval 23.501 CR3177 (Rel-16, 'F'): Emergency services for non-3GPP access Huawei, HiSilicon Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2106235 CR Approval 23.501 CR3178 (Rel-17, 'A'): Emergency services for non-3GPP access Huawei, HiSilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.3 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) - - Docs:=8 -
7.3 S2-2105537 CR Approval 23.501 CR3032 (Rel-16, 'F'): ATSSS Rule ID Ericsson, Qualcomm Incorporated, LG Electronics, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-16 Revised to S2-2106578. Susan (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.3 S2-2106578 CR Approval 23.501 CR3032R1 (Rel-16, 'F'): ATSSS Rule ID Ericsson, Qualcomm Incorporated, LG Electronics, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-16 Revision of S2-2105537r01. Approved Agreed
7.3 S2-2105538 CR Approval 23.501 CR3033 (Rel-17, 'F'): ATSSS Rule ID Ericsson, Qualcomm Incorporated, LG Electronics, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 Revised to S2-2106579. Susan (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.3 S2-2106579 CR Approval 23.501 CR3033R1 (Rel-17, 'F'): ATSSS Rule ID Ericsson, Qualcomm Incorporated, LG Electronics, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 Revision of S2-2105538r01. Approved Agreed
7.3 S2-2105957 CR Approval 23.502 CR3019 (Rel-17, 'F'): Removal of ATSSS Rule ID indication LG Electronics, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo, Motorola Mobility, Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.3 S2-2105784 CR Approval 23.502 CR2980 (Rel-16, 'F'): ATSSS_update target access type during secondary reauth Samsung Rel-16 Confirm CR Number - CR states xxxx!. TEI is an invalid WI Code: Should be TEI16. Noted Yannick (Nokia): Nokia requests for clarification. Assumes the CR is for Rel-16, although coversheet says Rel-17.
Ashok (Samsung) clarifies to Yannick (Nokia)
Dario (Qualcomm) ask question to Ashok
Ashok (Samsung ) replies to Dario
Dario (Qualcomm) replies to Ashok
Susan (Huawei) provides comments.
Ashok (Samsung) replies
Myungjune (LGE) comments.
Ashok (Samsung) provides comments.
Ashok (Samsung) provides r01
Stefan (Ericsson) comments
Dario (Qualcomm) comments on r02
Ashok (Samsung) comments
Apostolis (Lenovo) responds to Ashok (Samsung).
Ashok (Samsung) clarifies to Apostolis, Dario,
Yannick (Nokia): Nokia provides comments, do not see the need for Rel-16 correction.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.3 S2-2105786 CR Approval 23.502 CR2981 (Rel-17, 'A'): ATSSS_update target access type during secondary reauth Samsung Rel-17 Confirm CR Number - CR states xxxx!. TEI is an invalid WI Code: Should be TEI16. Revised to S2-2106580. Dario (Qualcomm) comments
Yannick (Nokia): Nokia provides r01.
Ashok (Samsung) is fine with r01.
Stefan (Ericsson) comments
Susan (Huawei) cannot accept either r00 or r01.
Ashok (Samsung) responds to Susan
Ashok (Samsung) provides r02
Yannick (Nokia): Nokia comments on r02.
Ashok (Samsung) agrees with Yannick and provides r03
Dario (Qualcomm) comments on the consequences if not approved and asks if the change is essential.
Ashok (Samsung) comments Dario
Stefan (Ericsson) asks whether CR is needed
Yannick (Nokia): Nokia notes that Samsung provided r04.
Stefan (Ericsson) provides r05
Marco (Huawei) provides r06 even if I confirm that we see no need of this CR at all.
Dario (Qualcomm) asks clarification on r06 and r05
Dario (Qualcomm) think it is unclear how r04/5/6 solve the issue
Ashok (Samsung) responds to Dario
Susan (Huawei) can accept r06.
Jinguo (ZTE) comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.3 S2-2106580 CR Approval 23.502 CR2981R1 (Rel-17, 'F'): ATSSS_update target access type during secondary reauth Samsung Rel-17 Revision of S2-2105786r06. Approved Agreed
7.4 - - - Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT - - Docs:=6 -
7.4 S2-2106209 CR Approval 23.501 CR3168 (Rel-16, 'F'): 5GS Idle Status Indication Nokia, Nokia Shanghai Bell Rel-16 Approved Qian (Ericsson) asks question for clarification
Hannu (Nokia) replies to Qian and proposes to treat Idle Status Indication in 'Availability after DDN failure' the same way in both EPS and 5GS for the sake of T8 / N33 API.
Qianghua (Huawei) provides comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.4 S2-2106210 CR Approval 23.501 CR3169 (Rel-17, 'A'): 5GS Idle Status Indication Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.4 S2-2106211 CR Approval 23.502 CR3064 (Rel-16, 'F'): 5GS Idle Status Indication Nokia, Nokia Shanghai Bell Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.4 S2-2106212 CR Approval 23.502 CR3065 (Rel-17, 'A'): 5GS Idle Status Indication Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.4 S2-2106216 CR Approval 23.502 CR3066 (Rel-16, 'F'): Device Triggering parameter correction Nokia, Nokia Shanghai Bell Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.4 S2-2106217 CR Approval 23.502 CR3067 (Rel-17, 'A'): Device Triggering parameter correction Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.5 - - - Enablers for Network Automation for 5G (eNA) - - Docs:=4 -
7.5 S2-2105680 CR Approval 23.288 CR0397 (Rel-16, 'F'): Clarify the data source of UE behavioural information and expected UE behavioural parameters Huawei, HiSilicon Rel-16 Revised to S2-2106581. Yannick (Nokia): Nokia requests for clarification.
Belen (Ericsson) objects to the initial version of this CR.
Malla (NTT DOCOMO) propose to NOTE.
Juan Zhang (Qualcomm) provides comment.
Wang Yuan (Huawei) replies to Yannick (Nokia), Belen (Ericsson), Malla (NTT DOCOMO) and Juan (Qualcomm), and provides r01.
Malla (NTT DOCOMO) objects r00 and r01.
Leo (Deutsche Telekom) agrees with NTT DOCOMO , this is not a FASMO correction, CR shall be NOTED.
Wang Yuan (Huawei) replies to Malla (NTT DOCOMO) and Leo (Deutsche Telekom) and provide r02.
Leo (Deutsche Telekom) can accept r02.
Belen (Ericsson) asks to replace UDR by UDM in the text, okay with r02 otherwise.
Malla (NTT DOCOMO) provide comment on r02.
Wang Yuan (Huawei) accepts the changes proposed by Belen (Ericsson) and Malla (NTT DOCOMO), and provide r03.
Yannick (Nokia): Nokia provides r04.
Wang Yuan (Huawei) accepts r04.
Malla (NTT DOCOMO) provide r05 and fine also with r04.
Wang Yuan (Huawei) is fine with either r04 or r05, prefer r05.
Yannick (Nokia): Nokia is fine with both r04 and r05.
Belen (Ericsson) also prefers r05.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2106581 CR Approval 23.288 CR0397R1 (Rel-16, 'F'): Clarify the data source of UE behavioural information and expected UE behavioural parameters Huawei, HiSilicon Rel-16 Revision of S2-2105680r05. Approved Agreed
7.5 S2-2105681 CR Approval 23.288 CR0398 (Rel-17, 'A'): Clarify the data source of UE behavioural information and expected UE behavioural parameters Huawei, HiSilicon Rel-17 Revised to S2-2106582. Malla (NTT DOCOMO) propose to NOTE.
Wang Yuan (Huawei) provides r01.
Juan Zhang (Qualcomm) provides comment to r01.
Wang Yuan (Huawei) corrects the email title and replies to Juan (Qualcomm).
Yannick (Nokia): Nokia provides r02.
Wang Yuan (Huawei) provides r03, fine with either r02 or r03.
Yannick (Nokia): Nokia is fine with both r02 and r03.
Malla (NTT DOCOMO) is fine with both r02 and r03.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2106582 CR Approval 23.288 CR0398R1 (Rel-17, 'A'): Clarify the data source of UE behavioural information and expected UE behavioural parameters Huawei, HiSilicon Rel-17 Revision of S2-2105681r03. Approved Agreed
7.6 - - - Enhancement to the 5GC Location Services (5G_eLCS) - - Docs:=6 -
7.6 S2-2105460 CR Approval 23.273 CR0181 (Rel-16, 'F'): Inconsistent Location Information for Non-3GPP Access Ericsson Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.6 S2-2105461 CR Approval 23.273 CR0182 (Rel-17, 'A'): Inconsistent Location Information for Non-3GPP Access Ericsson Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.6 S2-2105462 CR Approval 23.273 CR0183 (Rel-16, 'F'): Clarify conveyance of Service type Ericsson Rel-16 Revised to S2-2106583. Runze (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.6 S2-2106583 CR Approval 23.273 CR0183R1 (Rel-16, 'F'): Clarify conveyance of Service type Ericsson, Huawei Rel-16 Revision of S2-2105462r01. Approved Agreed
7.6 S2-2105463 CR Approval 23.273 CR0184 (Rel-17, 'A'): Clarify conveyance of Service type Ericsson Rel-17 Revised to S2-2106584. Runze (Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.6 S2-2106584 CR Approval 23.273 CR0184R1 (Rel-17, 'A'): Clarify conveyance of Service type Ericsson, Huawei Rel-17 Revision of S2-2105463r00. Approved Agreed
7.7 - - - 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) - - Docs:=1 -
7.7 S2-2106225 CR Approval 23.501 CR3171 (Rel-16, 'F'): Limitation on number of Allowed CAG identifiers per PLMN China Mobile Rel-16 Noted Peter (Ericsson) moving CR to AI 7.7.3, and provides comments and r01
Sebastian (Qualcomm) objects to the CR
Josep (DT) cleans up a coupe of typos, adds reference to 24.501 in r02, co-signs.
Peter Hedman (Ericsson) provides comments and a suggested wording
Sebastian (Qualcomm) objects to r01/r02 also
Devaki (Nokia) believes this CR is not a FASMO thus proposes to note it.
Yi (China Mobile) comments.
Sebastian (Qualcomm) replies
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.1 - - - 5GS Enhanced support of Vertical and LAN Services - 5G-LAN aspects - - Docs:=0 -
7.7.2 - - - 5GS Enhanced support of Vertical and LAN Services - TSN aspects - - Docs:=24 -
7.7.2 S2-2105497 CR Approval 23.502 CR2923 (Rel-16, 'F'): Update PCF service operation Ericsson Rel-16 Revised to S2-2106600. Qianghua (Huawei) proposes to merge this into S2-2106389
Shabnam (Ericsson) Proposes not to merge with 6389, as this is an alignment of already approved CR whereas 6389 adds lot more and can be questioned if needed in Rel-16?
Qianghua (Huawei) provides r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106600 CR Approval 23.502 CR2923R1 (Rel-16, 'F'): Update PCF service operation Ericsson Rel-16 Revision of S2-2105497r01. Approved Agreed
7.7.2 S2-2106039 CR Approval 23.501 CR3131 (Rel-16, 'F'): Clarification for Ethernet priority usage in PCF Huawei, HiSilicon Rel-16 Revised to S2-2106585. Devaki (Nokia) comments.
Qianghua (Huawei) replies
zhendong(ZTE), propose to clarify in clause 5.27.3
György (Ericsson) responds.
Jari (NTT DOCOMO) comments
zhendong(ZTE), provides r01
György (Ericsson) responds to ZTE.
zhendong(ZTE), respond to György
zhendong(ZTE), provides comments
Qianghua (Huawei) provides r02
György (Ericsson) responds to Huawei.
György (Ericsson) disagrees with r02.
Qianghua (Huawei) comments
Qianghua (Huawei) asks further for clarification
Qianghua (Huawei) provides r03
György (Ericsson) responds to DOCOMO.
Jari (NTT DOCOMO) provides r04
Jari (NTT DOCOMO) responds to György
Qianghua (Huawei) provides r05
György (Ericsson) responds and provides r06
Qianghua (Huawei) provides r07
György (Ericsson) provides r08
Qianghua (Huawei) provided r09
György (Ericsson) proposes to go with r08.
György (Ericsson) proposes to go with r08, could also accept r06 or r01, objects to all other revisions.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106585 CR Approval 23.501 CR3131R1 (Rel-16, 'F'): Clarification for Ethernet priority usage in PCF Huawei, HiSilicon Rel-16 Revision of S2-2106039r08. Approved Agreed
7.7.2 S2-2106010 CR Approval 23.503 CR0636 (Rel-16, 'F'): Clarification on 5GS Bridge information Notification when no AF Session exists Huawei, HiSilicon Rel-16 Approved zhendong(ZTE), question for clarification
Qianghua (Huawei) replies
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.7.2 S2-2106011 CR Approval 23.503 CR0637 (Rel-17, 'A'): Clarification on 5GS Bridge information Notification when no AF Session exists Huawei, HiSilicon Rel-17 Revised to S2-2106586. Devaki (Nokia) provides r01.
Qianghua (Huawei) replies
Jari (NTT DOCOMO) provides r02.
Sang-Jun (Samsung) provides r03.
György (Ericsson) responds to DoCoMo.
Jari (NTT DOCOMO) responds to György
György (Ericsson) responds to Jari, provides r04, and proposes that this document is handled under AI#8.5 and the corresponding deadlines.
Jari (NTT DOCOMO) responds to György (Ericsson)
György (Ericsson) responds and proposes to go with r01.
Jari (NTT DOCOMO) comments, is this Cat A or F?
György (Ericsson) responds.
György (Ericsson) proposes to go with r01 and objects to all other revisions to keep the contents as a 'mirror' to 6010.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106586 CR Approval 23.503 CR0637R1 (Rel-17, 'A'): Clarification on 5GS Bridge Information Notification when no AF Session exists Huawei, HiSilicon Rel-17 Revision of S2-2106011r01. Approved Agreed
7.7.2 S2-2106389 CR Approval 23.502 CR3095 (Rel-16, 'F'): Clarification for 5GS Bridge available event Huawei, HiSilicon Rel-16 Revised to S2-2106587. Devaki (Nokia) merge with 6040. It is a duplicate CR by the same author.
Andy (Samsung, VC): It looks as if 06040 is withdrawn.
Qianghua (Huawei) replies
Qianghua (Huawei) provides r01
Devaki (Nokia) comments.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106587 CR Approval 23.502 CR3095R1 (Rel-16, 'F'): Clarification for 5GS Bridge available event Huawei, HiSilicon Rel-16 Revision of S2-2106389r01. Approved Agreed
7.7.2 S2-2106162 CR Approval 23.501 CR3156 (Rel-16, 'F'): Clarification on the Bridge delay calculating ZTE Rel-16 Revised to S2-2106588. Devaki (Nokia) comments.
zhendong(ZTE), provides the response.
György (Ericsson) responds.
zhendong(ZTE), provides r01
Jari (NTT DOCOMO) comments
zhendong(ZTE), provides the repsonse
Qianghua (Huawei) provides comments
Sang-Jun (Samsung) comments
GYörgy (Ericsson) comments
Jari (NTT DOCOMO) responds to zhendong
zhendong(ZTE),provides the response
György (Ericsson) responds to DOCOMO.
György (Ericsson) ok with r01, objects to original version.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106588 CR Approval 23.501 CR3156R1 (Rel-16, 'F'): Clarification on the Bridge delay calculating ZTE Rel-16 Revision of S2-2106162r01. Approved Agreed
7.7.2 S2-2106163 CR Approval 23.501 CR3157 (Rel-17, 'A'): Clarification on the Bridge delay calculating ZTE Rel-17 Revised to S2-2106589. György (Ericsson) comments
zhendong(ZTE), provides the response
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106589 CR Approval 23.501 CR3157R1 (Rel-17, 'A'): Clarification on the Bridge delay calculating ZTE Rel-17 Revision of S2-2106163r00. Approved Agreed
7.7.2 S2-2106369 DISCUSSION Discussion Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock. Qualcomm Noted Devaki (Nokia) comments.
zhendong(ZTE), similar comments with nokia
Qianghua (Huawei) share same comments from Nokia and ZTE
Shabnam (Ericsson) provides Ericsson view in comments below.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.2 S2-2106370 CR Approval 23.501 CR3203 (Rel-16, 'F'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-16 CC#2: r07 + changes agreed. Revised to S2-2106689. Shabnam (Ericsson) provides comments on the 6369 document thread and provides r01 accordingly.
Devaki (Nokia) comments.
Devaki (Nokia) provides r02.
Shabnam (Ericsson) responds to Nokia comment.
Sebastian (Qualcomm) comments
Jari (NTT DOCOMO) comments
Sang-Jun (Samsung) comments
Shabnam (Ericsson) comments on Qualcomm and NTT DoCoMo input.
Sebastian (Qualcomm) replies to Ericsson
Jari (NTT DOCOMO) responds to Shabnam and Sebastian
Jari (NTT DOCOMO) provides r04
Shabnam (Ericsson) provides r05 with PMIC use for both DS-TT and NW-TT, should be possible unless we miss something.
Devaki (Nokia) provides r06.
Sebastian (Qualcomm) provides r07
Sebastian (Qualcomm) suggests r07 to be marked for approval
Sebastian (Qualcomm) provides r08 as a fallback option in case r07 is not agreeable
Qianghua (Huawei) express concerns
Qianghua (Huawei) provides updates on top of r08 as a way forward
Sebastian (Qualcomm) proposes to approve r08 with the following changes:
Clause 5.28.1:
Replace 'DS-TT maps txPropagationDelay from 5GS clock to the TSN GM clock identified by the TSN time domain number received in PMIC before reporting txPropagationDelay to the TSN AF.' by 'DS-TT reports txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC).'
Replace 'NW-TT maps txPropagationDelay from 5GS clock to the TSN GM clock used by the CNC before reporting txPropagationDelay to the TSN AF.' by 'NW-TT reports txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock used.'
Clause 5.28.2:
Replace 'If TSN AF provides PSFP and/or scheduled traffic information to DS-TT then DS-TT maps this information from the TSN GM clock identified by the TSN time domain number received in PMIC to the 5GS clock before executing on the PSFP and scheduled traffic information.' by 'If TSN AF provides PSFP and/or scheduled traffic information to DS-TT then DS-TT executes on this information relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC).'
Replace 'If TSN AF provides PSFP and/or scheduled traffic information to NW-TT then NW-TT maps this information from the TSN GM clock used by the CNC to the 5GS clock before executing on the PSFP and scheduled traffic information.' by 'If TSN AF provides PSFP and/or scheduled traffic information to NW-TT then NW-TT executes on this information relative to the time base of the TSN GM clock.'
Qianghua (Huawei) confirms that we are OK with the proposed changes, we can confirm this at CC#2 if needed
Shabnam (Ericsson) comments regarding if Huawei could clarify why we should not use consistent approach for DSTT and NWTT with option where NW-TT is not preconfigured? Also, for Rel-16 UMIC should be replaced by BMIC?
Qianghua (Huawei) replies
zhendong(ZTE), provides the comemtns
zhendong(ZTE),confirm the answer
Sebastian (Qualcomm) clarifies that in R16 version of 23.501 we also use the term UMIC
Sebastian (Qualcomm) proposes to go ahead with r08 with the changes proposed earlier to close this Rel-16 FASMO issue
Sebastian (Qualcomm) also comments that we can revise the CR again for plenary to potentially add back the signaling of the domain number to NW-TT
Devaki (Nokia) proposes to go with r07 (and updates to the note as needed), not accept r08.
Sebastian (Qualcomm) replies to Devaki
Sebastian (Qualcomm) proposes another alternative: agree r07 with the following changes:
Clause 5.28.1:
Replace 'DS-TT and NW-TT map txPropagationDelay from 5GS clock to the TSN GM clock identified by the IEEE TSN time domain number received in PMIC before reporting txPropagationDelay to the TSN AF.' by 'DS-TT and NW-TT report txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC).''
Clause 5.28.2:
Replace 'If TSN AF provides PSFP and/or scheduled traffic information to DS-TT or NW-TT, then DS-TT or NW-TT map this information from the TSN GM clock (identified by the TSN time domain number received in PMIC) to the 5GS clock before executing on the PSFP and scheduled traffic information.' by 'If TSN AF provides PSFP and/or scheduled traffic information to DS-TT and NW-TT then DS-TT and NW-TT execute on this information relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC).'
Shabnam (Ericsson) comments on what the Note 3 Huawei refers to means from our understanding and proposes we go without preconfiguration option in NWTT.
Sang-Jun (Samsung) prefers r07 based way forward.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106689 CR Approval 23.501 CR3203R1 (Rel-16, 'F'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung Rel-16 Revision of S2-2106370r07 + changes. Wrong version uploaded. Revised to S2-2106825. Revised
7.7.2 S2-2106825 CR Approval 23.501 CR3203R2 (Rel-16, 'F'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung Rel-16 Revision of S2-2106689. Approved Agreed
7.7.2 S2-2106372 CR Approval 23.501 CR3204 (Rel-17, 'A'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-17 CC#2: Alignment with S2-2106370 agreed. Revised to S2-2106690. Sebastian (Qualcomm) provides r01
Sang-Jun (Samsung) asks Sebastian (Qualcomm) for clarification.
Sebastian (Qualcomm) replies to Samsung; propose to approve r01 with the following additional changes: 'add X in Applicability for NW-TT in PMIC table for txPropagationDelayDeltaThreshold and TSN time domain number, and add 'and NW-TT' in Note 23 behind DS-TT.
Qianghua (Huawei) this CR should align with the approved S2-2106370 later, we suggest this be a pure mirror of CR3203. object r00/r01 for notes.
Sebastian (Qualcomm) proposes to agree this CR as a pure mirror of S2-2106370 (if agreed)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.2 S2-2106690 CR Approval 23.501 CR3204R1 (Rel-17, 'A'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung Rel-17 Revision of S2-2106372. . Wrong version uploaded. Revised to S2-2106826. Revised
7.7.2 S2-2106826 CR Approval 23.501 CR3204R2 (Rel-17, 'A'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung Rel-17 Revision of S2-2106690. Approved Agreed
7.7.2 S2-2106373 CR Approval 23.502 CR3092 (Rel-16, 'F'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-16 Noted Devaki (Nokia) comments - same comments as provided for S2-2106369, S2-2106370 apply (this CR and it's mirror may not be needed based on that discussion).
Shabnam (Ericsson) asks if the latest r04 CR on 23.501 requires an updated revision here as well to show the additional information transfer on PMIC?
Sebastian (Qualcomm): this paper can be noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.2 S2-2106379 CR Approval 23.502 CR3093 (Rel-17, 'A'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-17 Noted Sebastian (Qualcomm): This paper can be noted.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.2 S2-2106382 CR Approval 23.503 CR0648 (Rel-16, 'F'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-16 Noted Devaki (Nokia) comments - same comments as provided for S2-2106369, S2-2106370 apply (this CR and it's mirror may not be needed based on that discussion).
Sebastian (Qualcomm): This paper can be noted.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.2 S2-2106385 CR Approval 23.503 CR0649 (Rel-17, 'A'): Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock Qualcomm Rel-17 Noted Sebastian (Qualcomm): This paper can be noted.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 - - - 5GS Enhanced support of Vertical and LAN Services - Type a/b aspects - - Docs:=14 -
7.7.3 S2-2105323 CR Approval 23.501 CR2997 (Rel-16, 'F'): Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility Qualcomm Rel-16 Revised to S2-2106590. Devaki (Nokia) asks questions for clarification.
Peter (Ericsson) provides comments and r01
Qianghua (Huawei) provides comments
Sebastian (Qualcomm) is ok with r01 and replies to Huawei and Ericsson
Sebastian (Qualcomm) replies to Nokia
Qianghua (Huawei) provides r02
Sebastian (Qualcomm) is ok with r02
Devaki (Nokia) comments that this CR is not consistent with 6042 P2.
Peter Hedman (Ericsson) provides reply
Sebastian (Qualcomm) replies to Devaki
Devaki (Nokia) comments.
Peter Hedman (Ericsson) provides comments and ok with r02 (or r01)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.3 S2-2106590 CR Approval 23.501 CR2997R1 (Rel-16, 'F'): Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility Qualcomm, Ericsson Rel-16 Revision of S2-2105323r02. Approved Agreed
7.7.3 S2-2105324 CR Approval 23.501 CR2998 (Rel-17, 'A'): Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility Qualcomm Rel-17 Revised to S2-2106591.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Peter (Ericsson) provides comments on r00 being approved.
Revised
7.7.3 S2-2106591 CR Approval 23.501 CR2998R1 (Rel-17, 'A'): Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility Qualcomm, Ericsson Rel-17 Revision of S2-2105324r00. Approved Agreed
7.7.3 S2-2106041 DISCUSSION Discussion Discussion on EPS-5GS HO considering CAG. Huawei, HiSilicon Rel-16 Noted
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106042 CR Approval 23.501 CR3133 (Rel-16, 'F'): EPS<->5GS HO considering CAG Huawei, HiSilicon Rel-16 Noted Devaki (Nokia) comments.
Hyunsook (LGE) asks for the clarification.
Peter (Ericsson) provides comments and r01
Josep (DT) further comments.
Qianghua (Huawei) replies
Sebastian (Qualcomm) objects to the CR
Qianghua (Huawei) asks questions for r01
Peter Hedman (Ericsson) provides comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106043 CR Approval 23.501 CR3134 (Rel-17, 'A'): EPS<->5GS HO considering CAG Huawei, HiSilicon Rel-17 Noted Sebastian (Qualcomm) objects to the CR for the same reasons as given for 6042
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106044 CR Approval 23.502 CR3030 (Rel-16, 'F'): EPS<->5GS HO considering CAG Huawei, HiSilicon Rel-16 Noted Peter (Ericsson) provides comments
Sebastian (Qualcomm) objects to the CR for the same reason as Ericsson (UDM interaction will delay the handover and therefore can lead to increased number of failed hand-overs)
Qianghua (Huawei) replies
Sebastian (Qualcomm) replies to Qianghua
Qianghua (Huawei) OK to note
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106045 CR Approval 23.502 CR3031 (Rel-17, 'A'): EPS<->5GS HO considering CAG Huawei, HiSilicon Rel-17 Noted Peter (Ericsson) provides comments
Sebastian (Qualcomm) objects to the CR for the same reason as given for 6044
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106046 LS OUT Approval [DRAFT] LS on Clarification of UE with CAG information in UE subscription Huawei, HiSilicon Rel-16 Revised to S2-2106592. Peter (Ericsson) provides comments
Sebastian (Qualcomm) provides r01
Qianghua (Huawei) OK with r01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.3 S2-2106592 LS OUT Approval LS on Clarification of UE with CAG information in UE subscription SA WG2 Rel-16 Revision of S2-2106046r01. Approved Approved
7.7.3 S2-2105559 CR Approval 23.502 CR2934 (Rel-16, 'F'): NRF service operations Nokia, Nokia Shangai Bell Rel-16 CC#2: Noted Peter (Ericsson) provides comments and r01
Patrice (Huawei) remembers that this proposal has been discussed a few times already, and still being incorrect for Rel-16, respectfully objects to the CR and all its revisions.
Devaki (Nokia) replies to Huawei/Patrice.
Patrice (Huawei) is puzzled by the comments.
Devaki (Nokia) comments.
Devaki (Nokia) comments and provides r02.
Patrice (Huawei) confirms that r02 is not agreeable either. A conclusion from this discussion is maybe that an LS to CT4 should be sent to request them to not depart from stage 2 system-level design.
Devaki (Nokia) replies and proposes to discuss this in CC#2.
Patrice (Huawei) wonders if each CR which does not find consensus should be discussed in CC#2.
Devaki (Nokia) comments that this is a frozen release, inconsistent stage 2/3 can mislead implementations resulting in IOT issues thus a FASMO issue to be considered in CC#2.
Peter Hedman (Ericsson) provides comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.7.3 S2-2106395 CR Approval 23.501 CR3210 (Rel-16, 'F'): Clarification on support of CAG in SNPN Deutsche Telekom Rel-16 Approved Peter (Ericsson) provides comments
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.7.3 S2-2106494 CR Approval 23.501 CR3231 (Rel-17, 'A'): Clarification on support of CAG in SNPN Deutsche Telekom Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.8 - - - Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - - Docs:=0 -
7.9 - - - Architecture enhancements for the support of Integrated access and backhaul (IABARC) - - Docs:=0 -
7.10 - - - Other Rel-16 WIDs - - Docs:=0 -
7.10.1 - - - Enhancement of URLLC supporting in 5GC (5G_URLLC) - - Docs:=1 -
7.10.1 S2-2105285 LS In Information LS from RAN WG3: Reply LS on LS Reply on QoS Monitoring for URLLC RAN WG3 (R3-212937) Rel-16 Noted Shabnam (Ericsson) provides comments to NOTE the LS as there is no further/any action to take by SA2.
Hui(Huawei) fine to NOTE the LS.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.10.2 - - - Enhancement of Network Slicing (eNS) - - Docs:=7 -
7.10.2 S2-2106219 CR Approval 23.502 CR3068 (Rel-17, 'F'): UE specific subscription proposal for AAA Server China Mobile Rel-17 Approved. CC#2: Objection from Ericsson. CC#4: Ericsson sustained their objection. Noted. Ashok (Samsung) provides comments
Aihua(China Mobile) replies to the comment.
Ashok (Samsung) respond to Aihua
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Peter Hedman (Ericsson) provides comments and object to the CR as instead it is the NSSAAF that should get UE specific address from UDM.
Noted
7.10.2 S2-2106226 CR Approval 23.501 CR3172 (Rel-17, 'F'): NSSAAF Discovery and Selection based on S-NSSAI or UE ID Range China Mobile, Rel-17 Revised to S2-2106593. Patrice (Huawei) proposes r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.2 S2-2106593 CR Approval 23.501 CR3172R1 (Rel-17, 'F'): NSSAAF Discovery and Selection based on S-NSSAI or UE ID Range China Mobile, Rel-17 CC#4: Ericsson commented that they had no technical objection to this, as they could not understand the reason for change, summary of change or consequences if not approved of this CR, as they are copied from S2-2106219, but it needs to be clarified why these changes are needed and the consequences if not approved. China Mobile agreed to update the cover sheet. This was revised in S2-2106677">Revision of S2-2106226r01. Approved. CC#2: Objection from Ericsson. CC#4: Cover sheet clarifications requested. Revised to S2-2106677. Peter Hedman (Ericsson) provides comments and object to the CR as instead it is the NSSAAF that should get UE specific address from UDM. Revised
7.10.2 S2-2106677 CR Approval 23.501 CR3172R2 (Rel-17, 'F'): NSSAAF Discovery and Selection based on S-NSSAI or UE ID Range China Mobile, Rel-17 Revision of S2-2106593. CC#4: This was left open for review at CC#5. CC#5: Approved Agreed
7.10.2 S2-2106282 CR Approval 23.501 CR3190 (Rel-17, 'F'): No empty allowed NSSAI at REGISTRATION ACCEPT MediaTek Inc. Rel-17 CC#2: r01 changing Cat A and WI Code agreed. Revised to S2-2106692. Ashok (Samsung) is OK with the proposal but seeks clarification about the WI code
Jinguo(ZTE) correct the AI#
Guillaume (MediaTek) replies
Guillaume (MediaTek) provides r01 and Rel-16 version
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.2 S2-2106692 CR Approval 23.501 CR3190R2 (Rel-17, 'A'): No empty allowed NSSAI at REGISTRATION ACCEPT MediaTek Inc., Deutsche Telekom AG Rel-17 Revision of S2-2106282. Approved Agreed
7.10.2 S2-2106691 CR Approval 23.501 CR3234 (Rel-16, 'F'): No empty allowed NSSAI at REGISTRATION ACCEPT MediaTek Inc., Deutsche Telekom AG Rel-16 Created at CC#2. Approved Agreed
7.10.3 - - - Optimisations on UE radio capability signalling (RACS) - - Docs:=7 -
7.10.3 S2-2105327 CR Approval 23.501 CR3000 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-16 CC#2: r03 + changes agreed. Revised to S2-2106693. Wanqiang (Huawei): Huawei requests for clarification. The change is not a 'F' type correction.
Haris (Qualcomm) proposes to note the CRs at this meeting and instead send LS to RAN2/3 with questions re the calculation of UE Radio Capability for Paging
Alessio(Nokia) replies
Qian (Ericsson) shares the view from Haris(Qualcomm) and consider it's reasonable to check with RAN group on this issue
alessio (Nokia) proposes to not note the CRs at this meeting and instead fox our specs as we have a problem
Chris (Vodafone) thinks that Nokia are correct and that SA2 has a problem to fix
Haris (Qualcomm) comments
Wanqiang (Huawei) proposes to have more discussions on this issue before we agree anything.
Lalith(Samsung) comments
Alessio(Nokia) comments
Chris (Vodafone) gives scenario as to why this CR is probably needed.
Wanqiang (Huawei) comments.
Chris (Vodafone) comments and provides rev 1.
Chris (Vodafone) describes a FASMO problem that causes RACS capability ID generation at every mobility event between EPS and 5GS.
Alessio(nokia) provides r02 with improved text and also clearer reason for change further highlighting why we need the CRs in the context of an optimization aiming at not requiring upload of UE radio capabilities from a UE providing a valid RACS ID.
Chris (Vodafone) provide r03
Haris (Qualcomm) is now ok with r01 or r02
Qian (Ericsson) comments
Qian (Ericsson) provides comments.
Chris (Vodafone) answers Qian (Ericsson)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Wanqiang (Huawei) provides r04 for CC discussion..
Chris (Vodafone) is OK with r04.
Revised
7.10.3 S2-2106693 CR Approval 23.501 CR3000R1 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-16 Revision of S2-2105327r03 + changes. Approved Agreed
7.10.3 S2-2105334 CR Approval 23.501 CR3003 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-17 CC#2: Revised in S2-2106694
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2106694 CR Approval 23.501 CR3003R1 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-17 Revision of S2-2105334. Approved Agreed
7.10.3 S2-2106459 CR Approval 23.401 CR3656 (Rel-16, 'F'): Correction to deletion procedure for PLMN-assigned UE Radio Capability IDs Apple Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.3 S2-2106461 CR Approval 23.401 CR3657 (Rel-17, 'F'): Correction to deletion procedure for PLMN-assigned UE Radio Capability IDs Apple Rel-17 Revised to S2-2106594. Chris (Vodafone) comments that this looks like a Cat A mirror CR.
Krisztian (Apple) provides r01 to fix the cover page (Cat F -> Cat A)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2106594 CR Approval 23.401 CR3657R1 (Rel-17, 'A'): Correction to deletion procedure for PLMN-assigned UE Radio Capability IDs Apple Rel-17 Revision of S2-2106461r01. Approved Agreed
7.10.4 - - - Enhanced IMS to 5GC Integration (eIMS5G_SBA) - - Docs:=0 -
7.10.5 - - - User Data Interworking and Coexistence (UDICoM) - - Docs:=0 -
7.10.6 - - - Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) - - Docs:=10 -
7.10.6 S2-2105353 CR Approval 23.502 CR2894 (Rel-16, 'F'): L-PSA and I-SMF release during mobiity procedure with I-SMF change or removal Nokia, Nokia Shanghai Bell Rel-16 Merged into S2-2106595 Fenqin (Huawei) suggest to take the discussion in 6116 thread.
Laurent (Nokia): provides r01
Fenqin (Huawei): propose to note this paper
Laurent (Nokia): answers
Laurent (Nokia): provides r02
Fenqin (Huawei): propose to merge to 6116
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
7.10.6 S2-2105354 CR Approval 23.502 CR2895 (Rel-17, 'A'): L-PSA and I-SMF release during mobiity procedure with I-SMF change or removal Nokia, Nokia Shanghai Bell Rel-17 Postponed Fenqin (Huawei) suggest to take the discussion in 6116 thread.
Laurent (Nokia): provides r01
Fenqin (Huawei): propose to postpone this paper.
Stefan (Ericsson) supports to postpone
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
7.10.6 S2-2106116 CR Approval 23.502 CR2812R2 (Rel-16, 'F'): L-PSA release during mobiity procedure with I-SMF removal Huawei, HiSilicon Rel-16 Revision of (Postponed) S2-2104382 from S2-145E. Revised to S2-2106595, merging S2-2105353 Laurent (Nokia): suggests to take Tdoc 5353 as the baseline and to consider 6116 as merged
Fenqin (Huawei): suggests to take this paper for discussion and split the work of R16/R17 two CR
Laurent (Nokia): answers
Fenqin (Huawei): responds
Fenqin (Huawei): correct the AI and the Tdoc name in the title
Stefan (Ericsson) comments
Fenqin(Huawei) Correct the e-mail thread title.
Fenqin (Huawei) comments
Laurent (Nokia) comments
Fenqin (Huawei) provides r01
Laurent (Nokia): provides r02
Fenqin (Huawei) do not agree with r02 and suggest to go with r01
Laurent (Nokia): answers, does not agree with r00/r01 and suggest to go with r02
Fenqin (Huawei) propose r03
Laurent (Nokia): objects to R00 and R01
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2106595 CR Approval 23.502 CR2812R3 (Rel-16, 'F'): L-PSA release during mobiity procedure with I-SMF removal Huawei, HiSilicon Rel-16 Revision of S2-2106116r03, merging S2-2105353. Approved Agreed
7.10.6 S2-2106117 CR Approval 23.502 CR2813R2 (Rel-17, 'A'): L-PSA release during mobiity procedure with I-SMF removal Huawei, HiSilicon Rel-17 Revision of (Postponed) S2-2104383 from S2-145E. Revised to S2-2106596.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2106596 CR Approval 23.502 CR2813R3 (Rel-17, 'A'): L-PSA release during mobiity procedure with I-SMF removal Huawei, HiSilicon Rel-17 Revision of S2-2106117r00. Approved Agreed
7.10.6 S2-2105750 CR Approval 23.502 CR2971 (Rel-16, 'F'): Source I-SMF release for PDU Session not requested for handover ZTE Rel-16 Revised to S2-2106597. Fenqin (Huawei): ask a question for clarification
Jinguo(ZTE) response
Fenqin(Huawei) response and provides r01
Laurent (Nokia): Comments
Jinguo(ZTE) comments
Jinguo(ZTE) provide r02 and r03 and ask to ignore r02.
Stefan (Ericsson) comments
Fenqin(Huawei) provides r04
Jinguo(ZTE) provides r05
Fenqin(Huawei) provides r06
Jinguo(ZTE) is fine with r06
Laurent (Nokia): provides r07
Jinguo(ZTE) is fine with r07
Laurent (Nokia): provides r08
Stefan (Ericsson) provides r09
Laurent (Nokia): objects to any version between R00 and R06 both included
Jinguo(ZTE) suggests to go with r09.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2106597 CR Approval 23.502 CR2971R1 (Rel-16, 'F'): Source I-SMF release for PDU Session not requested for handover ZTE, Huawei, Nokia, Nokia Shanghai Bell, Ericsson Rel-16 Revision of S2-2105750r09. Approved Agreed
7.10.6 S2-2105751 CR Approval 23.502 CR2972 (Rel-17, 'A'): Source I-SMF release for PDU Session not requested for handover ZTE Rel-17 Revised to S2-2106598.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2106598 CR Approval 23.502 CR2972R1 (Rel-17, 'A'): Source I-SMF release for PDU Session not requested for handover ZTE, Huawei, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2105751r00. Approved Agreed
7.10.7 - - - 5GS Transfer of Policies for Background Data Transfer (xBDT) - - Docs:=2 -
7.10.7 S2-2105927 CR Approval 23.503 CR0632 (Rel-17, 'F'): URSP rule generation based on BDT policy and related information Huawei, HiSilicon Rel-17 Revised to S2-2106599. Belen (Ericsson) provides r01, objects to initial version
Mirko (Huawei) responds and provides r02.
Yang (OPPO) comments.
Mirko (Huawei) responds and provides r03.
Yang (OPPO) is ok with r03
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.7 S2-2106599 CR Approval 23.503 CR0632R1 (Rel-17, 'F'): URSP rule generation based on BDT policy and related information Huawei, HiSilicon Rel-17 Revision of S2-2105927r03. Approved Agreed
7.10.8 - - - Single radio voice continuity from 5GS to 3G (5G_SRVCC) - - Docs:=0 -
8 - - - Rel-17 WID - - Docs:=0 -
8.1 - - - Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) - - Docs:=142 -
8.1 - - - General - - Docs:=5 -
8.1 S2-2105844 CR Approval 23.288 CR0413 (Rel-17, 'D'): Editorial corrections and harmonization Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106625 Vivian (vivo) comments
Gerald (Nokia): Nokia confirms merger of this CR into S2-2106348(vivo)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2106026 CR Approval 23.288 CR0427 (Rel-17, 'F'): Miscellaneous correction for TS 23.288 vivo Rel-17 Revised in S2-2106348 Revised
8.1 S2-2106348 CR Approval 23.288 CR0427R1 (Rel-17, 'F'): Miscellaneous correction for TS 23.288 vivo Rel-17 Revision of S2-2106026. r03 agreed. Revised to S2-2106625, merging S2-2105844 Vivian (vivo) provides r01.
Gerald (Nokia): Nokia thanks VIVO for the merger.
Megha(Intel) provides r02
Gerald (Nokia): Nokia co-signs this CR
Vivian (vivo): replies to Nokia and Intel, and provides r03
Vivian (vivo): updates the link address for the r03.
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is ok with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106625 CR Approval 23.288 CR0427R2 (Rel-17, 'F'): Miscellaneous correction for TS 23.288 Vivo, Nokia Rel-17 Revision of S2-2106348r03, merging S2-2105844. Approved Agreed
8.1 S2-2105373 LS In Action LS from SA WG4: LS on UE data collection and reporting SA WG4 (S4-211221) Rel-17 Postponed Leo (Deutsche Telekom) requests to postpone the LS
==== 8.X, 9.X Final Deadline ====
Postponed
8.1 - - - KI#1 - - Docs:=3 -
8.1 S2-2105683 CR Approval 23.502 CR2954 (Rel-17, 'F'): Remove the target of analytics reporting during the NWDAF(MTLF) registration Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2106145 CR Approval 23.288 CR0432 (Rel-17, 'F'): ML model storage alignment NTT DOCOMO Rel-17 r04 agreed. Revised to S2-2106626 Yannick (Nokia): Nokia provides r01.
Aihua (China Mobile) provides comments.
Malla (NTT DOCOMO) replies to Aihua (China Mobile) and fine with r01.
Aihua (China Mobile) replies and provides r02.
Yannick (Nokia): Nokia is fine with the proposed approach and provides r03.
Yannick (Nokia): Nokia provides r04 with additional note clarifying that storage of ML models in ADRF is not specified in this release of the specifications.
Zhang (Ericsson) is OK with r04
Malla (NTT DOCOMO) is OK with r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106626 CR Approval 23.288 CR0432R1 (Rel-17, 'F'): ML model storage alignment NTT DOCOMO, Nokia Rel-17 Revision of S2-2106145r04. Approved Agreed
8.1 - - - KI#2 - - Docs:=35 -
8.1 S2-2105436 CR Approval 23.288 CR0383 (Rel-17, 'C'): Defines the Analytics Context identifiers Ericsson, NTT DoCoMo Rel-17 r04 agreed. Revised to S2-2106627 Gerald (Nokia): Nokia provides comments.
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia responds to Ericsson and disagrees with original.
Zhang (Ericsson) defends against the disagreement
Zhang (Ericsson) responds to Nokia
Gerald (Nokia): Nokia responds to Zhang (Ericsson)
Zhang (Ericsson) response to Nokia and provide r01
Gerald (Nokia): Nokia asks for clarification on r01
Zhang (Ericsson) respond to Gerald and provide r02
Gerald (Nokia): Nokia comments on r03
Gerald (Nokia): Nokia clarifies that earlier comment had been meant for r02.
Gerald (Nokia): Nokia replies to Ericsson on the NOTE.
Jungshin (Samsung) provides comments
Zhang (Ericsson) provides r03
Zhang (Ericsson) provides r04
==== 8.X, 9.X Revisions Deadline ====
Jungshin (Samsung): Samsung is ok with r04
Gerald (Nokia): Nokia is okay with r04
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106627 CR Approval 23.288 CR0383R1 (Rel-17, 'C'): Defines the Analytics Context identifiers Ericsson, NTT DoCoMo Rel-17 Revision of S2-2105436r04. Approved Agreed
8.1 S2-2105437 CR Approval 23.288 CR0384 (Rel-17, 'C'): Updates to Analytics Context information Ericsson, NTT DoCoMo Rel-17 r04 agreed. Revised to S2-2106628 Gerald (Nokia): Nokia ask for clarification on original
Zhang (Ericsson) thanks the comments and provide r01
Gerald (Nokia): Nokia comments on r01 and responds to Zhang
Zhang (Ericsson) respond to Nokia and provide r02
Gerald (Nokia): Nokia provides comments on r02
Zhang (Ericsson) respond to Nokia and provide r03
Gerald (Nokia): Nokia replies to r03
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia replies to Ericsson's proposal
Zhang (Ericsson) provides r04
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r04
Xiaoyan (CATT) is fine with r04 and would like to co-sign this CR.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106628 CR Approval 23.288 CR0384R1 (Rel-17, 'C'): Updates to Analytics Context information Ericsson, NTT DoCoMo, CATT Rel-17 Revision of S2-2105437r04. Approved Agreed
8.1 S2-2105438 CR Approval 23.288 CR0385 (Rel-17, 'C'): Updates for Analytics Context Information Transfer Ericsson, NTT DoCoMo Rel-17 r01 agreed. Revised to S2-2106629 Aihua (China Mobile) provides comments.
Gerald (Nokia): Nokia provides a comment.
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia provides comments
Aihua (China Mobile) provides r01.
Zhang (Ericsson) is OK for r01
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106629 CR Approval 23.288 CR0385R1 (Rel-17, 'C'): Updates for Analytics Context Information Transfer Ericsson, NTT DoCoMo Rel-17 Revision of S2-2105438r01. Approved Agreed
8.1 S2-2105439 CR Approval 23.288 CR0386 (Rel-17, 'F'): NWDAF procedures for Analytics transfer update Ericsson Rel-17 r04 agreed. Revised to S2-2106630 Leo (Deutsche Telekom) provides r01
Zhang (Ericsson) is OK with r01
Gerald (Nokia): Nokia has comments and asks for clarification
Zhang (Ericsson) responds to Nokia
Zhang (Ericsson) provides r02
Jungshin (Samsung) provides comments and r03
Zhang (Ericsson) is OK with r03
Gerald (Nokia): Nokia comments on r03 and provides r04
Zhang (Ericsson) object r04 and provide r05
Gerald (Nokia): Nokia is not okay with r05
Zhang (Ericsson) provides comments
==== 8.X, 9.X Revisions Deadline ====
Jungshin (Samsung): Samsung prefers r04, but can live with r05 as well.
Gerald (Nokia): Nokia prefers r04.
Zhang (Ericsson) can accept r04
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106630 CR Approval 23.288 CR0386R1 (Rel-17, 'F'): NWDAF procedures for Analytics transfer update Ericsson Rel-17 Revision of S2-2105439r04. Approved Agreed
8.1 S2-2105440 CR Approval 23.288 CR0387 (Rel-17, 'B'): NWDAF selection including transfer of Analytics context Ericsson, NTT DoCoMo Rel-17 r07 agreed. Revised to S2-2106631, merging S2-2105926 and S2-2106514 Zhang (Ericsson) provides r01
Gerald (Nokia): Nokia provides comments original
Xiaoyan (CATT) provides comments to r01.
Zhang (Ericsson) thanks the comments and provides r02
Yingying (CATT) ask questions for clarification
Zhang (Ericsson) response to YingYing (CATT)
Gerald (Nokia): Nokia provides comments on r02
Zhang (Ericsson) provides response to Nokia
Gerald (Nokia): Nokia responds to Zhang
Zhang (Ericsson) respond to Nokia
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia replies to Ericsson related to 'TerminationRequest'
Gerald (Nokia): Nokia responds to Zhang (Ericsson)
Xiaoyan (CATT) provides r03 to merge S2-2105926 with this CR.
Jungshin (Samsung) provides r04
Zhang (Ericsson) provides comments and r05
Gerald (Nokia): Nokia comments on r05 and replies to Ericsson.
Jungshin (Samsung) provides a comment.
Zhang (Ericsson) provides comments and provide r06
Gerald (Nokia): Nokia comments on r06
Zhang (Ericsson) provides r07
==== 8.X, 9.X Revisions Deadline ====
Jungshin (Samsung): Samsung can accept r07
Malla (NTT DOCOMO) is fine with r07
Gerald (Nokia): Nokia is okay with r07
Xiaoyan (CATT) is fine with r07.
Zhang (Ericsson) prefers r07
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106631 CR Approval 23.288 CR0387R1 (Rel-17, 'B'): NWDAF selection including transfer of Analytics context Ericsson, NTT DoCoMo, CATT, Samsung Rel-17 Revision of S2-2105440r07, merging S2-2105926 and S2-2106514. Approved Agreed
8.1 S2-2105441 CR Approval 23.288 CR0388 (Rel-17, 'C'): NWDAF re-selection for Multiple NWDAF deployments - procedures -update Ericsson, NTT DoCoMo Rel-17 r05 agreed. Revised to S2-2106632 Gerald (Nokia): Nokia provides comments
Zhang (Ericsson) respond to Gerald and provide r01
Gerald (Nokia): Nokia comments on r01 and disagrees
Zhang (Ericsson) provides comments and provide r02
Zhang (Ericsson) provides r03
Jungshin (Samsung) provides comments
Gerald (Nokia): Nokia provides comments on r03
Gerald (Nokia): Nokia replies to Ericsson
Gerald (Nokia): Nokia is okay to add a NOTE
Zhang (Ericsson) provides r04
Gerald (Nokia): Nokia comments on r04
Zhang (Ericsson) provides r05
Gerald (Nokia): Nokia comments on r05
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia can live with r05; okay to resolve comments in next meeting.
Zhang (Ericsson) prefer r05
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106632 CR Approval 23.288 CR0388R1 (Rel-17, 'C'): NWDAF re-selection for Multiple NWDAF deployments - procedures -update Ericsson, NTT DoCoMo Rel-17 Revision of S2-2105441r05. Approved Agreed
8.1 S2-2105444 CR Approval 23.288 CR0390 (Rel-17, 'F'): Editorial fix in clause 5.2 Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105445 CR Approval 23.288 CR0391 (Rel-17, 'F'): Clean up references to Annex A Ericsson Rel-17 Merged into S2-2106601 Megha(Intel) proposes to merge this document with S2-2105785.
Zhang (Ericsson) agrees to merge this document with S2-2105785
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105684 CR Approval 23.288 CR0400 (Rel-17, 'F'): Remove the FFS on how to remove the noise data by the abnormal UE list Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105773 CR Approval 23.501 CR3078 (Rel-17, 'F'): Update to NWDAF Discovery and Selection Samsung Rel-17 Merged into S2-2106604 Gerald (Nokia): Nokia proposes to merge S2-2105773 into S2-2105852
Mehrdad (Samsung) confirms merging S2-2105773 into S2-2105852r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105785 CR Approval 23.288 CR0409 (Rel-17, 'F'): Correction to Annex A reference Intel Rel-17 r01 agreed. Revised to S2-2106601, merging S2-2105445 and S2-2105869 Zhang (Ericsson) agrees merge S2-2105445 into S2-2105785 and co-sign
Gerald (Nokia): changes are also covered in S2-2106348
Megha(Intel) provides r01
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) agrees, r01 can be approved, but cover sheet needs to be corrected.
Megha (Intel) is ok with r01 and will correct the cover sheet (tick 'Core Network') in the final approved TDoc.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106601 CR Approval 23.288 CR0409R1 (Rel-17, 'F'): Correction to Annex A reference Intel,Ericsson Rel-17 Revision of S2-2105785r01, merging S2-2105445 and S2-2105869. Approved Agreed
8.1 S2-2105788 CR Approval 23.501 CR3082 (Rel-17, 'F'): NWDAF discovery and selection - clarification on analytics metadata provisioning capability Intel Rel-17 Merged into S2-2106604 Gerald (Nokia): Nokia proposes to merge S2-2105788 into S2-2105852
Megha(Intel) is OK to merge S2-2105788 into S2-2105852.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105845 CR Approval 23.288 CR0414 (Rel-17, 'F'): Corrections and clarifications related to analytics subscription transfer Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2106602 Zhang (Ericsson) ask questions
Gerald (Nokia): Nokia provides r01
Zhang (Ericsson) is OK with r01
Malla (NTT DOCOMO) some changes are overlapping with S2-2106145.
Xiaoyan (CATT) provides a comment and r02.
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia provides r03 addressing Ericsson's comments and removing overlap with other CRs
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia confirms that latest version for approval is r03
Zhang (Ericsson) is OK with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106602 CR Approval 23.288 CR0414R1 (Rel-17, 'F'): Corrections and clarifications related to analytics subscription transfer Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105845r03. Approved Agreed
8.1 S2-2105848 CR Approval 23.288 CR0417 (Rel-17, 'F'): Corrections related to analytics aggregation Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2106603 Zhang (Ericsson) ask questions for clarification
Gerald (Nokia): Nokia replies to Ericsson
Zhang (Ericsson) provides comments
Gerald (Nokia): Nokia responds to Ericsson and provides r01.
Xiaoyan (CATT) provides a comment and r02.
Xiaoyan (CATT) requests to ignore her comment on S2-2105848 for it intends to another CR.
Mehrdad (Samsung) comments on original version.
Gerald (Nokia): Nokia responds to Samsung.
Mehrdad (Samsung) comments on original version and r01 and suggests to remove (Identifier) of ML model.
Zhang (Ericsson) provides r02
Mehrdad (Samsung) comments on r02 and still does not see the need for Identifier of ML model.
Gerald (Nokia): Nokia provides r03 addressing Samsungs comment.
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) can accept r03
Mehrdad (Samsung) is OK with r03 but objects to original version and all other revisions.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106603 CR Approval 23.288 CR0417R1 (Rel-17, 'F'): Corrections related to analytics aggregation Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105848r03. Approved Agreed
8.1 S2-2105852 CR Approval 23.501 CR3101 (Rel-17, 'F'): Resolve Editor's Note on analytics metadata provisioning capability Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2106604, merging S2-2105773 and S2-2105788 Gerald (Nokia): Nokia provides S2-2105852r1 merging S2-2105788 and S2-2105773.
Mehrdad (Samsung) is OK with S2-2105852r01.
Megha(Intel) is ok with S2-2105852r01.
Gerald (Nokia): Nokia provides r02 with an editorial correction
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106604 CR Approval 23.501 CR3101R1 (Rel-17, 'F'): Resolve Editor's Note on analytics metadata provisioning capability Nokia, Nokia Shanghai Bell, Samsung, Intel Rel-17 Revision of S2-2105852r02, merging S2-2105773 and S2-2105788. Approved Agreed
8.1 S2-2105853 CR Approval 23.501 CR3102 (Rel-17, 'F'): Clarification related to NWDAF discovery Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) asks for clarification.
Gerald (Nokia): Nokia responds to DOCOMO
Malla (NTT DOCOMO) asks further clarification
Mehrdad (Samsung) comments on original version.
Gerald (Nokia): Nokia responds to Samsung and provides r01
Malla (NTT DOCOMO) provides comments
Gerald (Nokia): Nokia responds to Malla (NTT DOCOMO)
Mehrdad (Samsung) comments on original version and r01 and suggests to NOTE this CR.
Malla (NTT DOCOMO) provides comments.
Gerald (Nokia): Nokia clarifies to DOCOMO
==== 8.X, 9.X Revisions Deadline ====
Mehrdad (Samsung) objects to original version and all revisions of this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105869 CR Approval 23.288 CR0419 (Rel-17, 'F'): Clarification on the reference to Annex A in TS 23.288 China Unicom Rel-17 Merged into S2-2106601 Megha(Intel) proposes to merge this document with S2-2105785.
Chi (China Unicom) is fine to merge S2-2105869 with S2-2105785.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105897 CR Approval 23.288 CR0422 (Rel-17, 'F'): Clarifications for analytics subscription transfer between NWDAFs that provide analytics for analytics aggregation CATT Rel-17 Postponed Zhang (Ericsson) propose to merge the paper into S2-2105440
Yingying(CATT) provides clarification to Zhang Fu(Ericsson) and suggests discussing this CR and S2-2105440 separately so far.
Zhang (Ericsson) provides comments
Zhang (Ericsson) ask questions for clarification
Yingying(CATT) provides clarification to Zhang Fu(Ericsson).
Yingying(CATT) replies to Zhang Fu(Ericsson).
Zhang (Ericsson) provides comments and agree to not merge the paper into S2-2105440, also ask revision of the paper
Yingying(CATT) provides S2-2105897r01.
Gerald (Nokia): Nokia asks for clarification
Yingying(CATT) provides clarification to Gerald (Nokia).
Gerald (Nokia): Nokia asks for further clarification on CATT's repsonse
Yingying(CATT) replies to Ericsson.
Yingying(CATT) provides clarification to Gerald (Nokia) and provides r02.
Gerald (Nokia): Nokia responds to CATT and comments on r02.
Yingying(CATT) responds to Nokia and Ericsson, and provides r03.
Gerald (Nokia): Nokia comments on r03
==== 8.X, 9.X Revisions Deadline ====
Yingying(CATT) replies to Gerald.
Zhang (Ericsson) propose to have r04 and discuss in CC
Gerald (Nokia): Nokia objects to r03 and earlier versions. Prefers to postpone.
Yingying(CATT) agrees with an 'r03+changes on top' and suggests discussing it in CC.
==== 8.X, 9.X Final Deadline ====
Postponed
8.1 S2-2105913 CR Approval 23.288 CR0423 (Rel-17, 'F'): Clarification on contents of analytics exposure CATT Rel-17 Noted Zhang (Ericsson) ask clarification
Gerald (Nokia): Nokia has concerns and asks for clarification
Xiaoyan (CATT) reponds to Zhang (Ericsson) and Gerald (Nokia).
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) provides comments
Xiaoyan (CATT) responds to Gerald and Zhang.
Gerald (Nokia): Nokia objects to this CR
Xiaoyan (CATT) is fine with noting this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105914 CR Approval 23.288 CR0424 (Rel-17, 'F'): Clarification on Analytics Subscription Transfer CATT Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105926 CR Approval 23.288 CR0281R2 (Rel-17, 'F'): Analytics Subscription Transfer when analytics consumer changes CATT Rel-17 Revision of (Noted) S2-2104275 from S2-145E. Merged into S2-2106631 Zhang (Ericsson) propose to merge the paper into S2-2105440
Zhang (Ericsson) confirms the paper is merged into S2-2105440
Gerald (Nokia): Nokia asks for confirmation of merger to CATT
Xiaoyan (CATT) agrees to merge this CR to S2-2105440.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2106514 CR Approval 23.288 CR0435 (Rel-17, 'C'): NWDAF reselection triggered by consumer NF changes Samsung Rel-17 Merged into S2-2106631 Zhang (Ericsson) propose to merge the paper into S2-2105440
Gerald (Nokia): Nokia provides comments
Zhang (Ericsson) provides comments
Zhang (Ericsson) confirms the paper is merged into S2-2105440
Gerald (Nokia): Nokia asks for confirmation of merger to Samsung
Jungshin (Samsung) confirms merging S2-2106514 into S2-2105440r04
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) confirms S2-2106514 in merged into S2-2105440r04 and any revision after that
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2106515 CR Approval 23.288 CR0436 (Rel-17, 'F'): Correction on NWDAF information for Namf CreateUEContext service Samsung Rel-17 r01 agreed. Revised to S2-2106605 Gerald (Nokia): Nokia provides comments
Zhang (Ericsson) is OK with r01
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106605 CR Approval 23.288 CR0436R1 (Rel-17, 'F'): Correction on NWDAF information for Namf CreateUEContext service Samsung Rel-17 Revision of S2-2106515r01. CC#5: This should be 23.502 CR3122. Revised to S2-2106984. Revised
8.1 S2-2106984 CR Approval 23.502 CR3122 (Rel-17, 'F'): Correction on NWDAF information for Namf CreateUEContext service Samsung Rel-17 Revision of S2-2106605. Approved Agreed
8.1 - - - KI#4 - - Docs:=9 -
8.1 S2-2105410 CR Approval 23.288 CR0382 (Rel-17, 'B'): Collection of input data for Analytics ID 'Load level information' Ericsson Rel-17 r06 agreed. Revised to S2-2106633 Yannick (Nokia): Nokia provides r01.
David (Samsung) provides r02 with minor modifications, would like to co-sign.
Malla (NTT DOCOMO) raise concerns and ask for clarification.
Peretz (Spirent) is asking a question about r02.
Belen (Ericsson) provides a response to DOCOMO and asks for feedback
Belen (Ericsson) replies to Spirent
Malla (NTT DOCOMO) provides r03
Belen (Ericsson) is okay with sending an LS and ask about r03
Malla (NTT DOCOMO) replies to Belen (Ericsson)
David (Samsung) provides r04.
Malla (NTT DOCOMO) replies to David (Samsung) and provided a draft LS in a draft folder.
David (Samsung) comments.
Malla (NTT DOCOMO) provides r05.
Peretz (Spirent) replies to Ericsson
Peretz (Spirent) replies to Malla about the proposes LS.
Belen (Ericsson) asks about r05
Malla (NTT DOCOMO) replies to Peretz (Spirent)
Malla (NTT DOCOMO) agrees with Belen (Ericsson)
Belen (Ericsson) provides r06.
Malla (NTT DOCOMO) replies to Peretz (Spirent).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106633 CR Approval 23.288 CR0382R1 (Rel-17, 'B'): Collection of input data for Analytics ID 'Load level information' Ericsson, Samsung Rel-17 Revision of S2-2105410r06. Approved Agreed
8.1 S2-2106698 LS OUT Approval [DRAFT] Network slice information from OAM NTT DOCOMO Rel-17 Created at CC#2. r05 agreed. Revised to S2-2106634 Malla (NTT DOCOMO) LS draft is available in the inbox.
Malla (NTT DOCOMO) provided r01.
Susan (Huawei) provided r02.
Malla (NTT DOCOMO) provided r03.
Belen (Ericsson) provides r04
Malla (NTT DOCOMO) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106634 LS OUT Approval Network slice information from OAM SA WG2 Rel-17 Revision of S2-2106698r05. Approved Approved
8.1 S2-2105411 CR Approval 23.502 CR2901 (Rel-17, 'F'): Event ID Number of UEs served by the AMF and located in 'Area Of Interest' Ericsson Rel-17 r01 agreed. Revised to S2-2106618 Malla (NTT DOCOMO) propose to NOTE.
Belen (Ericsson) provides r01
Belen (Ericsson) asks Malla if r01 is fine.
Malla (NTT DOCOMO) r01 is fine.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106618 CR Approval 23.502 CR2901R1 (Rel-17, 'F'): Event ID Number of UEs served by the AMF and located in 'Area Of Interest' Ericsson Rel-17 Revision of S2-2105411r01. Approved Agreed
8.1 S2-2105484 CR Approval 23.288 CR0395 (Rel-17, 'F'): Correction to reference descriptions for slice load level analytics KDDI, Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105766 CR Approval 23.288 CR0406 (Rel-17, 'F'): Update to analytics summary table Samsung, KDDI Rel-17 r01 agreed. Revised to S2-2106606 Yannick (Nokia): Nokia provides r01.
David (Samsung) confirms r01 is OK.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106606 CR Approval 23.288 CR0406R1 (Rel-17, 'F'): Update to analytics summary table Samsung, KDDI Rel-17 Revision of S2-2105766r01. Approved Agreed
8.1 - - - KI#7 - - Docs:=1 -
8.1 S2-2105465 CR Approval 23.503 CR0609 (Rel-17, 'F'): User data Congestion analytic including list of most contributing applications Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 - - - KI#8 - - Docs:=17 -
8.1 S2-2105299 LS In Action LS from SA WG4: Reply LS to SA2 on UE Data Collection SA WG4 (S4-210961) Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.1 S2-2105442 CR Approval 23.502 CR2910 (Rel-17, 'F'): Support for internal group ID in Naf services Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105443 CR Approval 23.288 CR0389 (Rel-17, 'F'): Data collection from AF support for internal group ID Ericsson Rel-17 r01 agreed. Revised to S2-2106607 Yang (OPPO) comments
Belen (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106607 CR Approval 23.288 CR0389R1 (Rel-17, 'F'): Data collection from AF support for internal group ID Ericsson Rel-17 Revision of S2-2105443r01. Approved Agreed
8.1 S2-2105774 CR Approval 23.501 CR3079 (Rel-17, 'F'): Update to AF Discovery and Selection Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105778 CR Approval 23.502 CR2978 (Rel-17, 'F'): Event Filters for Collective Behaviour of multiple UEs Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105779 CR Approval 23.502 CR2979 (Rel-17, 'F'): Update to AF Profile Registration and Discovery Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105776 CR Approval 23.501 CR3081 (Rel-17, 'F'): Clarification on AMF Load Balancing Samsung Rel-17 Noted Dimitris (Lenovo) provides r01
Yannick (Nokia): Nokia provides comments.
Mehrdad (Samsung) replies to Lenovo and Nokia and provides r02.
Malla (NTT DOCOMO) provides comments.
Mehrdad (Samsung) replies to NTT DOCOMO.
Mehrdad (Samsung) replies further to NTT DOCOMO.
Yannick (Nokia): Nokia does not see the need for the proposed note in TS 23.501.
==== 8.X, 9.X Revisions Deadline ====
Yannick (Nokia): Nokia objects to all versions for this proposal.
Malla (NTT DOCOMO) propose to note.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105985 CR Approval 23.288 CR0426 (Rel-17, 'F'): Mapping information update in UE data collection procedure Qualcomm Incorporated Rel-17 r04 agreed. Revised to S2-2106635 Yang (OPPO) comments whether the SMF can support to store the mapping between UE ID/IP address and NEF/AF already
Juan Zhang (Qualcomm) replies to Yang (OPPO)
Malla (NTT DOCOMO) asks for clarification
Juan Zhang (Qualcomm) replies to Malla (NTT Docomo) and provides r01.
Yannick (Nokia): Nokia provides r02 and asks for clarification.
Malla (NTT DOCOMO) asks clarification to Yannick (Nokia) on r02.
Yannick (Nokia): Nokia replies to NTT DOCOMO.
Malla (NTT DOCOMO) provide comment.
Malla (NTT DOCOMO) provided comment.
Juan Zhang (Qualcomm) is OK with r02 and replies to Yannick and Malla.
Yannick (Nokia): Nokia believes a further revision is needed.
Juan Zhang (Qualcomm) replies to Yannick.
Malla (NTT DOCOMO) provides r03.
Juan Zhang (Qualcomm) is OK with r03.
Juan Zhang (Qualcomm) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106635 CR Approval 23.288 CR0426R1 (Rel-17, 'F'): Mapping information update in UE data collection procedure Qualcomm Incorporated Rel-17 Revision of S2-2105985r04. Approved Agreed
8.1 S2-2106176 CR Approval 23.502 CR3051 (Rel-17, 'F'): Allowing NRF to provides S-NSSAI/DNN to NEF corresponding to an untrusted AF OPPO Rel-17 r04 agreed. Revised to S2-2106636 Yannick (Nokia): Nokia provides comments.
Dimitris (Lenovo) requests clarification
Yang (OPPO) provides r01.
Yang (OPPO) responds to Dimitris that TS 23.288 has described one AF (untrusted) can have more than one combinations of S-NSSAI/DNN.
Dimitris (Lenovo) responds
Malla (NTT DOCOMO) asks for clarification
Mehrdad (Samsung) comments on original version
Yang (OPPO) provides r02
Mehrdad (Samsung) comments on r02.
Yang (OPPO) responds to Mehrdad and provides r03
Yannick (Nokia): Nokia comments on r03.
Yang (OPPO) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106636 CR Approval 23.502 CR3051R1 (Rel-17, 'F'): Allowing NRF to provides S-NSSAI/DNN to NEF corresponding to an untrusted AF OPPO Rel-17 Revision of S2-2106176r04. Approved Agreed
8.1 S2-2106178 CR Approval 23.288 CR0433 (Rel-17, 'F'): Clarification on the NWDAF or AF triggered mapping procedure OPPO Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2106027 CR Approval 23.288 CR0428 (Rel-17, 'F'): Update description for AF registration to the NRF in TS 23.288 vivo Rel-17 Revised in S2-2106371 Revised
8.1 S2-2106371 CR Approval 23.288 CR0428R1 (Rel-17, 'F'): Update description for AF registration to the NRF in TS 23.288 vivo Rel-17 Revision of S2-2106027. Approved Yang (OPPO) comments
Vivian (vivo) replies to Yang
Yang (OPPO) is ok with original version
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2106030 CR Approval 23.288 CR0431 (Rel-17, 'F'): Clarification about the Application ID in the NF profile for AF registration to the NRF vivo Rel-17 Revised in S2-2106383 Revised
8.1 S2-2106383 CR Approval 23.288 CR0431R1 (Rel-17, 'F'): Clarification about the Application ID in the NF profile for AF registration to the NRF vivo Rel-17 Revision of S2-2106030. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 - - - KI#9 - - Docs:=6 -
8.1 S2-2105291 LS In Action LS from SA WG3: Reply LS on Transaction Information - Dispersion Analytics SA WG3 (S3-212159) Rel-17 Response drafted in S2-2105459. Final response in S2-2106637
==== 8.X, 9.X Final Deadline ====
Replied to
8.1 S2-2105459 LS OUT Approval [DRAFT] Reply LS on Transaction Information - Dispersion Analytics Spirent Communications Rel-17 Response to S2-2105291. r00 agreed. Revised to S2-2106637
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106637 LS OUT Approval Reply LS on Transaction Information - Dispersion Analytics SA WG2 Rel-17 Revision of S2-2105459r00. Approved Approved
8.1 S2-2105466 CR Approval 23.288 CR0393 (Rel-17, 'C'): Update to Suspicion of DDoS attack Spirent Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105483 CR Approval 23.288 CR0394 (Rel-17, 'C'): Application ID - an optional input in Dispersion Analytics Spirent Rel-17 r01 agreed. Revised to S2-2106608 Peretz (Spirent) is providing r01 per Nokia's comments received prior to meeting start.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106608 CR Approval 23.288 CR0394R1 (Rel-17, 'C'): Application ID - an optional input in Dispersion Analytics Spirent Rel-17 Revision of S2-2105483r01. Approved Agreed
8.1 - - - KI#10 - - Docs:=1 -
8.1 S2-2105575 CR Approval 23.502 CR2937 (Rel-17, 'F'): Clarification on Inactivity Timer set by SMF LG Electronics Rel-17 Noted Zhang (Ericsson) provides comments
LaeYoung (LGE) replies to Zhang (Ericsson).
Juan Zhang (Qualcomm) provides comments.
LaeYoung (LGE) is fine to NOTE this CR. ^___^
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 - - - KI#11 - - Docs:=30 -
8.1 S2-2105259 LS In Action LS from CT WG4: LS on restricted and unrestricted S-NSSAIs per PLMN of the TA(s) CT WG4 (C4-213471) Rel-17 Responses drafted in S2-2105686 and S2-2106001. Final response in S2-2106609
==== 8.X, 9.X Final Deadline ====
Replied to
8.1 S2-2105686 LS OUT Approval [DRAFT] LS reply on restricted and unrestricted S-NSSAIs per PLMN of the TA(s) Huawei, HiSilicon Rel-17 Response to S2-2105259. r03 agreed. Revised to S2-2106609, merging S2-2106001 David (Samsung) provides r01.
Wang Yuan (Huawei) can accept r01.
Wang Yuan (Huawei) provides r02 based on the agreements reached in 5688 and 5768.
David (Samsung) agrees to r02.
Yannick (Nokia): Nokia comments on r02.
Wang Yuan (Huawei) provides r03.
Yannick (Nokia): Nokia is fine with r03.
David (Samsung) is OK with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106609 LS OUT Approval LS reply on restricted and unrestricted S-NSSAIs per PLMN of the TA(s) SA WG2 Rel-17 Revision of S2-2105686r03, merging S2-2106001. Approved Approved
8.1 S2-2106001 LS OUT Approval [DRAFT] Reply LS on restricted and unrestricted S-NSSAIs per PLMN of the TA(s) Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2105259. Merged into S2-2106609 Yannick (Nokia): Nokia suggest to take Huawei's S2-2105686 as version for discussion for the LS reply to CT4 regarding slice restrictions, and to mark Nokia's S2-2106001 as merged into S2-2105686.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105687 CR Approval 23.288 CR0402 (Rel-17, 'F'): Remove the roaming information for the slice association information Huawei, HiSilicon Rel-17 Merged into S2-2106611 Wang Yuan (Huawei) confirms that S2-2105687 is merged into S2-2105768r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105688 CR Approval 23.502 CR2955 (Rel-17, 'F'): Remove the roaming information for the slice association information Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106610, merging S2-2105767 Wang Yuan (Huawei) provides r01, merging Nokia's CR in S2-2105767 into Huawei's CR in S2-2105688.
David (Samsung) provides r02 and comments.
Yannick (Nokia): Nokia objects to r02, requests clarifications on 'slice restriction' wording.
Wang Yuan (Huawei) can accept r02.
David (Samsung) thanks Huawei for accepting the way forward, wonders if Nokia would be fine with r02.
Yannick (Nokia): Nokia still objects to r02, provides r03 as a compromise proposal to get some progress in this meeting.
David (Samsung) thanks Nokia for the compromise proposal, is OK with r03.
Wang Yuan (Huawei) thanks Nokia for the revision and is OK with r03.
Yannick (Nokia): Nokia provides r04 with change on the cover sheet.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) is fine with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106610 CR Approval 23.502 CR2955R1 (Rel-17, 'F'): Remove the roaming information for the slice association information Huawei, HiSilicon, Nokia Rel-17 Revision of S2-2105688r04, merging S2-2105767. Approved Agreed
8.1 S2-2105767 CR Approval 23.502 CR2974 (Rel-17, 'F'): Correction for AMF event 'S-NSSAIs per TA mapping' Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106610 Yannick (Nokia): Nokia requests to mark this CR as merged into S2-2105688.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105768 CR Approval 23.288 CR0407 (Rel-17, 'F'): Correction for slice restrictions information Nokia, Nokia Shanghai Bell Rel-17 r05 agreed. Revised to S2-2106611, merging S2-2105687 Yannick (Nokia): Nokia provides r01, merging Huawei's CR in S2-2105687 into Nokia's CR in S2-2105768.
Yannick (Nokia): Nokia provides r02.
Wang Yuan (Huawei) is fine with r02.
David (Samsung) provides r03 and comments.
Yannick (Nokia): Nokia requests Samsung for clarification.
David (Samsung) provides clarification to Nokia.
Peretz (Spirent) provides one more clarification.
Yannick (Nokia): Nokia objects to r03, requests clarifications on 'slice restriction' wording.
David (Samsung) comments.
David (Samsung) wonders what's the way forward for this CR, can only accept r00 or r03.
Wang Yuan (Huawei) can accepts r03.
Yannick (Nokia): Nokia provides r04 as a compromise proposal to get some progress in this meeting.
David (Samsung) thanks Nokia for the compromise proposal, is OK with r04.
Wang Yuan (Huawei) thanks Nokia for the revision and is OK with r04.
Yannick (Nokia): Nokia provides r05 with change on the cover sheet.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) is fine with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106611 CR Approval 23.288 CR0407R1 (Rel-17, 'F'): Correction for slice restrictions information Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-17 Revision of S2-2105768r05, merging S2-2105687. Approved Agreed
8.1 S2-2105693 DISCUSSION Agreement Discussion on the security issues when MFAF processes the raw data. Huawei, HiSilicon Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105328 CR Agreement 23.288 CR0377 (Rel-17, 'F'): Resolving editor's notes for references to NWDAF services and cleanup for call flows Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2106612, merging S2-2105783 Yannick (Nokia): Nokia provides r01, merging Intel's CR in S2-2105783 into Nokia's CR in S2-2105328.
Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106612 CR Agreement 23.288 CR0377R1 (Rel-17, 'F'): Resolving editor's notes for references to NWDAF services and cleanup for call flows Nokia, Nokia Shanghai Bell, Intel Rel-17 Revision of S2-2105328r02, merging S2-2105783. Approved Agreed
8.1 S2-2105329 CR Agreement 23.288 CR0378 (Rel-17, 'F'): DCCF for data collection from applications in the UE Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105330 CR Agreement 23.501 CR3001 (Rel-17, 'F'): TS 23.288 reference update for ADRF services Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2106613 Malla (NTT DOCOMO) provided r01
Yannick (Nokia): Nokia provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106613 CR Agreement 23.501 CR3001R1 (Rel-17, 'F'): TS 23.288 reference update for ADRF services Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105330r02. Approved Agreed
8.1 S2-2105331 CR Agreement 23.501 CR3002 (Rel-17, 'F'): Resolving editor's note for ADRF discovery and selection Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106614 Zhang (Ericsson) have concerns
Malla (NTT DOCOMO) share Ericsson's comments and agree that it fits better into R-18.
Aihua (China Mobile) comments on original version.
Yannick (Nokia): Nokia provides r01, which reverts the additions and only remove the editor's notes. Let's further work on the ADRF selection aspects in Rel-18 if there is support for that.
Aihua (China Mobile) is OK with r01
Zhang (Ericsson) is OK with r01
==== 8.X, 9.X Revisions Deadline ====
Malla (NTT DOCOMO) is OK with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106614 CR Agreement 23.501 CR3002R1 (Rel-17, 'F'): Resolving editor's note for ADRF discovery and selection Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105331r01. Approved Agreed
8.1 S2-2105332 CR Agreement 23.288 CR0379 (Rel-17, 'F'): ADRF ID in Nmfaf_3daDataManagement_Configure service operation Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106615 Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) provides comments
Yannick (Nokia): Nokia replies to Ericsson and NTT DOCOMO.
Yannick (Nokia): Nokia provides r01.
Zhang (Ericsson) is OK with r01
Malla (NTT DOCOMO) is OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106615 CR Agreement 23.288 CR0379R1 (Rel-17, 'F'): ADRF ID in Nmfaf_3daDataManagement_Configure service operation Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105332r01. Approved Agreed
8.1 S2-2105333 CR Agreement 23.288 CR0380 (Rel-17, 'F'): NF type and NF id for ADRF storage Nokia, Nokia Shanghai Bell Rel-17 Noted Zhang (Ericsson) have concerns
Malla (NTT DOCOMO) provides comments
Yannick (Nokia): Nokia replies to NTT DOCOMO.
Aihua (China Mobile) replies to NTT DOCOMO and provides comments.
Zhang (Ericsson) provides comments
Zhang (Ericsson) propose the paper to be NOTED
Yannick (Nokia): Nokia assumes Ericsson's objection is due to SA3 dependency. Nokia is fine to note the paper with the understanding that this is related to security issues that should first be concluded by SA3.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105447 CR Approval 23.502 CR2911 (Rel-17, 'F'): Data Collection parameters Ericsson Rel-17 r01 agreed. Revised to S2-2106619, merging S2-2105691 Yannick (Nokia): Nokia provides r01.
Zhang (Ericsson) is OK with r01
Wang Yuan (Huawei) propose to merge S2-2105691 into S2-2105447 and accepts r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106619 CR Approval 23.502 CR2911R1 (Rel-17, 'F'): Data Collection parameters Ericsson Rel-17 Revision of S2-2105447r01, merging S2-2105691. Approved Agreed
8.1 S2-2105689 CR Approval 23.288 CR0403 (Rel-17, 'F'): Clarify the Data collection parameters of the NWDAF Huawei, HiSilicon Rel-17 Noted Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) we need to align with S2-2105447.
Yannick (Nokia): Nokia do not think the CR is needed if we go with proposal in S2-2105447.
Wang Yuan (Huawei) is OK to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105690 CR Approval 23.501 CR3061 (Rel-17, 'F'): Clarify the Data collection parameters of the NWDAF Huawei, HiSilicon Rel-17 Noted Malla (NTT DOCOMO) we need to align with S2-2105447.
Yannick (Nokia): Nokia do not think the CR is needed if we go with proposal in S2-2105447.
Wang Yuan (Huawei) is OK to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105691 CR Approval 23.502 CR2956 (Rel-17, 'F'): Clarify the Data collection parameters of the NWDAF Huawei, HiSilicon Rel-17 Merged into S2-2106619 Malla (NTT DOCOMO) propose to merge into S2-2105447.
Yannick (Nokia): Nokia supports taking S2-2105447 as basis.
Wang Yuan (Huawei) agrees to merge this CR into S2-2105447.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105694 CR Approval 23.288 CR0405 (Rel-17, 'F'): Clarify the data processing and formatting when MFAF is deployed Huawei, HiSilicon Rel-17 Noted Yannick (Nokia): Nokia disagrees with this proposal and suggest to note it.
Wang Yuan (Huawei) provides clarification to Yannick(Nokia) and asks whether it is OK to changes the NOTE to an Editor's Note.
Dimitris (Lenovo) shares the view of Nokia
Yannick (Nokia): Nokia prefers to note the proposal and wait for SA3 discussions outcomes.
Malla (NTT DOCOMO) provided comments.
Wang Yuan (Huawei) is fine to note this proposal.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105783 CR Approval 23.288 CR0408 (Rel-17, 'F'): Correction to ADRF, NWDAF service operations in various procedures Intel Rel-17 Merged into S2-2106612 Yannick (Nokia): Nokia's understanding is that changes in this CR are now covered by initial revision for Nokia's CR in S2-2105328.
Megha(Intel) is ok to merge S2-2105783 to S2-2105328.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105789 CR Approval 23.288 CR0411 (Rel-17, 'F'): Correction to NWDAF Data management service operation Intel Rel-17 r01 agreed. Revised to S2-2106616 Zhang (Ericsson) provides comments
Megha(Intel) provides clarification
Zhang (Ericsson) respond to Intel
Megha(Intel) responds to Zhang (Ericsson)
Megha (Intel) provides r01
Zhang (Ericsson) is OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106616 CR Approval 23.288 CR0411R1 (Rel-17, 'F'): Correction to NWDAF Data management service operation Intel Rel-17 Revision of S2-2105789r01. Approved Agreed
8.1 - - - KI#12 - - Docs:=7 -
8.1 S2-2105290 LS In Action LS from SA WG3: Reply to Reply LS on RAT type for network monitoring SA WG3 (S3-212158) Rel-17 Noted Yannick (Nokia): Nokia suggests to note this LS. There is no specific action required from SA2 beyond taking information provided by SA3 into account, hence we do not see a reply is needed.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105588 CR Approval 23.288 CR0396 (Rel-17, 'B'): Removing EN on Frequency in OSE China Telecom Rel-17 r04 agreed. Revised to S2-2106617 Yannick (Nokia): Nokia provides r01 and requests for clarification.
Zhuoyi (China Telecom): Replies to Nokia and provides r02.
Yannick (Nokia): Nokia replies to China Telecom.
Belen (Ericsson) asks a question about r01 and original version.
Zhuoyi (China Telecom) replies to Belen.
Belen (Ericsson) replies to China Telecom and asks questions.
Zhuoyi (China Telecom) replies to Ericsson.
Belen (Ericsson) provides r03
Zhuoyi (China Telecom) accepts r03.
Zhuoyi (China Telecom) provides r04.
Belen (Ericsson) is okay with r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106617 CR Approval 23.288 CR0396R1 (Rel-17, 'B'): Removing EN on Frequency in OSE China Telecom Rel-17 Revision of S2-2105588r04. Approved Agreed
8.1 S2-2105589 DISCUSSION Information Discussion on NWDAF's retrieval of Cell-Frequency Information from OAM via MDT. China Telecom Noted Belen (Ericsson) provides comments
Zhuoyi (China Telecom) replies to Belen.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105938 CR Approval 23.288 CR0425 (Rel-17, 'F'): Update of Data Collection from OAM Huawei, HiSilicon Rel-17 Postponed Malla (NTT DOCOMO) object r00.
Susan (Huawei) replies to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to Susan (Huawei).
Susan (Huawei) provides r02.
Malla (NTT DOCOMO) provides comment on r02 and propose to note the CR as we need input from SA5.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) is ok to postpone this CR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.1 S2-2106028 CR Approval 23.288 CR0429 (Rel-17, 'F'): Clarifying that some data types for a specific UE collected from OAM via MDT vivo Rel-17 Revised in S2-2106374 Revised
8.1 S2-2106374 CR Approval 23.288 CR0429R1 (Rel-17, 'F'): Clarifying that some data types for a specific UE collected from OAM via MDT vivo Rel-17 Revision of S2-2106028. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 - - - KI#15 - - Docs:=12 -
8.1 S2-2105226 LS In Action LS from SA WG3: Reply-LS on Reply-LS on user consent requirements for analytics SA WG3 (S3-210689) Revision of postponed S2-2103719 from S2-145E. Response drafted in S2-2105851. Noted Malla (NTT DOCOMO) propose to NOTE this LS and we can respond to the newest LS from SA3 S2-2105288.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105851 LS OUT Approval [DRAFT] LS Reply on user consent Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2105226. r04 agreed. Revised to S2-2106638 Gerald (Nokia): Nokia clarifies that the LS is in response to S2-2105288
Belen (Ericsson) provides r01.
Gerald (Nokia): Nokia provides r02
Belen (Ericsson) provides r03
Gerald (Nokia): Nokia comments on r03
Malla (NTT DOCOMO) provides r04
Gerald (Nokia): Nokia provides r05
Belen (Ericsson) provides r06.
Malla (NTT DOCOMO) comment r05/r06.
Belen (Ericsson) is fine with r04
Gerald (Nokia): Nokia clarifies to DOCOMO about scope of this LS
Gerald (Nokia): Nokia provides r07
==== 8.X, 9.X Revisions Deadline ====
Malla (NTT DOCOMO) prefer r01, r04, and object all revisions
Gerald (Nokia): Nokia asks for clarification on DOCOMO's objection
Malla (NTT DOCOMO) replies Nokia
Gerald (Nokia): Nokia replies to DOCOMO; can live with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106638 LS OUT Approval Reply LS on user consent SA WG2 Rel-17 Revision of S2-2105851r04. Approved Approved
8.1 S2-2105288 LS In Action LS from SA WG3: LS on User consent SA WG3 (S3-212123) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.1 S2-2105407 DISCUSSION Agreement KI#15 - Location of the tracking functionality . Ericsson Noted Gerald (Nokia): Nokia provides comments
Belen (Ericsson) replies to Nokia
Gerald (Nokia): Nokia replies to Ericsson
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2105408 CR Approval 23.288 CR0381 (Rel-17, 'B'): KI#15 - User consent Ericsson Rel-17 r08 agreed. Revised to S2-2106639, merging S2-2105682 and S2-2105849 Gerald (Nokia): Nokia provides r01
Malla (NTT DOCOMO) provides r02
Gerald (Nokia): Nokia asks for clarification to DOCOMO on r02
Malla (NTT DOCOMO) replies to Gerald (Nokia)
Belen (Ericsson) asks Nokia about r01 and replies to DOCOMO
Gerald (Nokia): Nokia responds to Belen (Ericsson)
Gerald (Nokia): Nokia responds to Belen's question/comments.
Belen (Ericsson) replies.
Gerald (Nokia): Nokia replies
Belen (Ericsson) provides r03
Gerald (Nokia): Nokia comments on r03
Belen (Ericsson) provides r04.
Belen (Ericsson) provides r05
Gerald (Nokia): Nokia comments on r04
Belen (Ericsson) replies to Nokia, provides r06
Gerald (Nokia): Nokia replies to Ericsson; provides r07; co-signs the CR.
Belen (Ericsson) asks about r07
Gerald (Nokia): Nokia responds to Ericsson, provides r08
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r07, r08; could live with r06; objects to earlier versions
Malla (NTT DOCOMO) comment on r07
Gerald (Nokia): Nokia replies to DOCOMO
Malla (NTT DOCOMO) could live with r06/07/08.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106639 CR Approval 23.288 CR0381R1 (Rel-17, 'B'): KI#15 - User consent Ericsson, Nokia Rel-17 Revision of S2-2105408r08, merging S2-2105682 and S2-2105849. Approved Agreed
8.1 S2-2105409 CR Approval 23.502 CR2733R1 (Rel-17, 'B'): User consent to data collection Ericsson Rel-17 Revision of (Noted) S2-2103818 from S2-145E. Merged into S2-2106640 Gerald (Nokia): Nokia provides a comment. Proposes to merge S2-2105850 into this CR.
Gerald (Nokia): Nokia comments that is was proposed to merge this CR into S2-2105850.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105682 CR Approval 23.288 CR0399 (Rel-17, 'B'): User consent for UE data colletion Huawei Rel-17 Merged into S2-2106639 Malla (NTT DOCOMO) propose to merge into S2-2105408
Gerald (Nokia): Nokia proposes to merge this CR into S2-2105408
Wang Yuan (Huawei) confirms that S2-2105682 can be merged into S2-2105408.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105849 CR Approval 23.288 CR0418 (Rel-17, 'B'): User consent for data collection related to network analytics Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106639 Mehrdad (Samsung) suggests to mark this CR as merged into S2-2105408
Belen (Ericsson) objects to this CR.
Ericsson understands that this CR and S2-2105408 are providing different proposals for the same topic, as such to had been merged both already.
Belen (Ericsson) proposes to merge this CR into S2-2105408.
Ericsson withdraws objection.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia confirms this CR as merged into S2-2105408
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105850 CR Approval 23.502 CR2998 (Rel-17, 'B'): User consent for network analytics Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2106640, merging S2-2105409 Gerald (Nokia): Nokia proposes to mark this CR merged into S2-2105409
Belen (Ericsson) thinks that this CR is more detailed and prefer to take it as basis. i.e. prefer to merge S2-2105409 into this one.
Malla (NTT DOCOMO) provide comments.
Gerald (Nokia): Nokia provides r01, merging S2-2105409 into this one.
Belen (Ericsson) comments on DOCOMO proposal.
Belen (Ericsson) is okay with r01.
Belen (Ericsson) provides r02
Gerald (Nokia): Nokia provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106640 CR Approval 23.502 CR2998R1 (Rel-17, 'B'): User consent for network analytics Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2105850r03, merging S2-2105409. Approved Agreed
8.1 - - - KI#16 - - Docs:=5 -
8.1 S2-2105446 CR Approval 23.288 CR0392 (Rel-17, 'F'): EASDF as consumer of analytics Ericsson Rel-17 Merged into S2-2106641 Dario S. Tonesi (Qualcomm) proposes to merge with 6479.
Zhang (Ericsson) agree to merge into S2-2106479
Dario (Qualcomm) thanks Fu Zhang.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2105843 CR Approval 23.288 CR0412 (Rel-17, 'F'): Correction in General description of DN Performance Analytics Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2105847 CR Approval 23.288 CR0416 (Rel-17, 'F'): Removing EASDF as NWDAF service consumer Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106641 Dario S. Tonesi (Qualcomm) proposes to merge with 6479.
Gerald (Nokia): Nokia is okay with the proposed merge into 6479
Dario (Qualcomm) thanks Gerald!
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2106479 CR Approval 23.288 CR0434 (Rel-17, 'F'): Removal of EASDF Qualcomm Incorporated Rel-17 r02 agreed. Revised to S2-2106641, merging S2-2105446 and S2-2105847 Dario S. Tonesi (Qualcomm) provides r01
Zhang (Ericsson) agree to merge 5446 into S2-2106479 and co-sign
Dario (Qualcomm) provides r02
Zhang (Ericsson) is OK with r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106641 CR Approval 23.288 CR0434R1 (Rel-17, 'F'): Removal of EASDF Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2106479r02, merging S2-2105446 and S2-2105847. Approved Agreed
8.1 - - - KI#17 - - Docs:=2 -
8.1 S2-2105787 CR Approval 23.288 CR0410 (Rel-17, 'F'): Resolve EN on how the level of accuracy can be derived for analytics reports Intel Rel-17 r01 agreed. Revised to S2-2106642 Gerald (Nokia): Nokia provides comments and asks for clarification.
Megha(Intel) provides response to Gerald(Nokia)
Gerald (Nokia): Nokia provides r01
Xiaoyan (CATT) provides comments.
Gerald (Nokia): Nokia responds to CATT
Xiaoyan (CATT) asks for clarification.
Gerald (Nokia): Nokia responds to Xiaoyan (CATT)
Megha (Intel) provides further comments
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia objects to original, is okay with r01
Megha (Intel) is okay with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106642 CR Approval 23.288 CR0410R1 (Rel-17, 'F'): Resolve EN on how the level of accuracy can be derived for analytics reports Intel Rel-17 Revision of S2-2105787r01. Approved Agreed
8.1 - - - KI#18 - - Docs:=2 -
8.1 S2-2105872 CR Approval 23.288 CR0421 (Rel-17, 'F'): Clarification on the usage of Supported Analytics Delay when the NWDAF also supports Analytics Aggregation China Unicom Rel-17 r05 agreed. Revised to S2-2106643 Gerald (Nokia): Nokia asks for clarification
Zhang (Ericsson) provides comments
Chi (China Unicom) replies to Gerald (Nokia) and Zhang (Ericsson), and provides r01.
Gerald (Nokia): Nokia asks for further clarifications on r01.
Chi (China Unicom) replies to Gerald (Nokia).
Gerald (Nokia): Nokia replies to Chi
Chi (China Unicom) provides further clarification to Gerald (Nokia).
Chi (China Unicom) replies to Zhang (Ericsson).
Chi (China Unicom) provides r02.
Gerald (Nokia): Nokia comments on r02
Gerald (Nokia): Nokia replies to Chi (China Unicom)
Chi (China Unicom) replies to Gerald (Nokia) and provides r03.
Gerald (Nokia): Nokia comments on r03 and provides r04.
Chi (China Unicom) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with 05; objects to r03 and earlier versions
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106643 CR Approval 23.288 CR0421R1 (Rel-17, 'F'): Clarification on the usage of Supported Analytics Delay when the NWDAF also supports Analytics Aggregation China Unicom Rel-17 Revision of S2-2105872r05. Approved Agreed
8.1 - - - KI#19 - - Docs:=7 -
8.1 S2-2105685 CR Approval 23.288 CR0401 (Rel-17, 'F'): Alignment of the ML Model subscription and ML Model request Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106644 Malla (NTT DOCOMO) asks for clarification.
Wang Yuan (Huawei) provides clarifications to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to Wang Yuan (Huawei).
Wang Yuan (Huawei) provides r01 and r02 respectively based on Malla's comments, and prefer r02.
Aihua (China Mobile) provides r03.
Dimitris (Lenovo) provides r04
Wang Yuan (Huawei) provides comments on r04.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) can accept r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106644 CR Approval 23.288 CR0401R1 (Rel-17, 'F'): Alignment of the ML Model subscription and ML Model request Huawei, HiSilicon Rel-17 Revision of S2-2105685r04. Approved Agreed
8.1 S2-2105692 CR Approval 23.288 CR0404 (Rel-17, 'F'): Clarify the Analytics Filter Information of the ML Model provisioning Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106645 Megha(Intel) asks question for clarification.
Yannick (Nokia): Nokia requests for clarification on the proposal.
Wang Yuan (Huawei) provides clarification to Megha(Intel) and Yannick(Nokia).
Yannick (Nokia): Nokia replies to Huawei and makes a suggestion.
Malla (NTT DOCOMO) agrees with Nokia and asks for further clarification on proposed text.
Dimitris (Lenovo) agrees with NTT DOCOMO and NOKIA requests further clarification
Yannick (Nokia): Nokia provides further wording change proposal.
Wang Yuan (Huawei) provides replies to Yannick(Nokia), Malla (NTT DOCOMO) and Dimitris (Lenovo), and provides r01.
Yannick (Nokia): Nokia provides comments on r03.
Malla (NTT DOCOMO) provided the comment.
Yannick (Nokia): Nokia replies to NTT DOCOMO.
Malla (NTT DOCOMO) replies to Yannick (Nokia)
Megha( Intel) provides comments
Wang Yuan (Huawei) provides r02 to align this new terminology in other sections
Yannick (Nokia): Nokia thanks Huawei for taking onboard additional changes and provides r03 with changes on CR coversheet only.
Wang Yuan (Huawei) is fine with r03.
Dimitris (Lenovo) is ok with r03
Malla (NTT DOCOMO) is ok with r03
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is ok with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106645 CR Approval 23.288 CR0404R1 (Rel-17, 'F'): Clarify the Analytics Filter Information of the ML Model provisioning Huawei, HiSilicon, Nokia Rel-17 Revision of S2-2105692r03. Approved Agreed
8.1 S2-2106029 CR Approval 23.288 CR0430 (Rel-17, 'F'): Clarify and complement the data source for data collection for NWDAF containing MTLF vivo Rel-17 Revised in S2-2106381 Revised
8.1 S2-2106381 CR Approval 23.288 CR0430R1 (Rel-17, 'F'): Clarify and complement the data source for data collection for NWDAF containing MTLF vivo Rel-17 Revision of S2-2106029. r02 agreed. Revised to S2-2106646 Megha(Intel) provides r01
Vivian(vivo) replies to Megha(Intel) and provides r02
Zhang (Ericsson) provides comments
Vivian (vivo) replies to Zhang
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is ok with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2106646 CR Approval 23.288 CR0430R2 (Rel-17, 'F'): Clarify and complement the data source for data collection for NWDAF containing MTLF Vivo Rel-17 Revision of S2-2106381r02. Approved Agreed
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=146 -
8.2 - - - General - - Docs:=31 -
8.2 S2-2105248 LS In Action LS from CT WG1: LS on reconfiguring a subscription parameter in the UE CT WG1 (C1-213876) Rel-17 Responses drafted in S2-2105321, S2-2105622 and S2-2106436. Final response in S2-2106701
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105321 LS OUT Approval [DRAFT] Reply LS on reconfiguring a subscription parameter in the UE Qualcomm Rel-17 Response to S2-2105248. r03 agreed. Revised to S2-2106701, merging S2-2105622 and S2-2106436 Josep (DT) comments, prefers this approach but would prefer to also fix Rel'16. Proposes to also fix 23.502.
Rainer (Nokia) prefers also 5321.
Kundan(NEC) provides response to Josep.
Sebastian (Qualcomm) replies to Kundan
Lalith(Samsung) seeks clarification.
Josep (DT) seeks to better understand if this is a real a problem.
Kundan(NEC) provides the explanation to Josep (DT).
Peter Hedman (Ericsson) provides comments.
Fei (OPPO) comments.
Kundan (NEC) clarifies Fei (Oppo) that the USIM stores the security context and once there is security context all initial registration message is integrity protected.
Lalith(Samsung) shares views of Peter Hedman (Ericsson) and Kundan(NEC)
Fei (OPPO) responds to Kundan (NEC)
Chia-Lin (MediaTek) also prefers 5321 and share same view as Josep
xiaowan (vivo) provides comments
Peter Hedman (Ericsson) provides reply and r01
Kundan (NEC) responds to Fei (Oppo)
Kundan (NEC) supports r01 from Peter.
Sebastian (Qualcomm) objects to r01 and provides r02
Kundan (NEC) objects to r02.
Peter Hedman (Ericsson) provides r03 and comments
==== 8.X, 9.X Revisions Deadline ====
Kundan (NEC) seeks clarification from Peter.
Kundan (NEC) seeks further clarification from Peter.
Josep (DT) prefers r02, is OK with r03.
Sebastian (Qualcomm) prefers r02, is ok with r03 or r00 and objects to r01
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106701 LS OUT Approval Reply LS on reconfiguring a subscription parameter in the UE SA WG2 Rel-17 Revision of S2-2105321r03, merging S2-2105622 and S2-2106436. Approved Approved
8.2 S2-2105622 LS OUT Approval [DRAFT] LS reply on reconfiguring a subscription parameter in the UE vivo Rel-17 Response to S2-2105248. Merged into S2-2106701 Josep (DT) proposes to use S2-2105321 for discussion.
xiaowan (vivo) is OK to merge the CR and the discussion into S2-2105321 since the replies are similar
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106436 LS OUT Approval [DRAFT] Response to LS on reconfiguring a subscription parameter in the UE NEC Corporation Rel-17 Response to S2-2105248. Merged into S2-2106701 Josep (DT) proposes to use S2-2105321 for discussion.
Sebastian (Qualcomm) objects to this LS out since there is no issue to be solved; AMF can already include those configuration parameters during Initial Registration, which will address the issue
Kundan (NEC) clarifies that Sebastian (Qualcomm) understanding is wrong.
Sebastian (Qualcomm) suggests to NEC to read Qualcomm's earlier comments again.
Kundan (NEC) indicates Sebastian (Qualcomm) WON'T work if it leaves to AMF implementation.
Peter Hedman (Ericsson) suggests that final discussions uses thread of 5321 and we note this as merged into that LS out.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106415 CR Approval 23.502 CR3104 (Rel-17, 'F'): Updating the UE with configuration parameter(s) by the UDM on PEI-SUPI association change. NEC Rel-17 Noted Sebastian (Qualcomm) objects to the CR since there is no issue to be solved; AMF can already include those configuration parameters during Initial Registration
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106439 DISCUSSION Agreement DISC on reconfiguring a subscription parameter in the UE. NEC Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105247 LS In Information LS from CT WG1: Reply LS on support of PWS over SNPN CT WG1 (C1-213640) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105308 LS In Information LS from TSG SA: Reply LS on support of PWS over NPN TSG SA (SP-210584) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105278 LS In Information LS from RAN WG3: Reply LS on support of PWS over SNPN in R17 RAN WG3 (R3-212863) Rel-17 Response drafted in S2-2105801. Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105279 LS In Action LS from RAN WG3: LS on clarifications on eNPN features RAN WG3 (R3-212867) Rel-17 Responses drafted in S2-2105312, S2-2105621, S2-2105827 and S2-2106048. Final response in S2-2106702
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105312 LS OUT Approval [DRAFT] Reply LS on clarifications on eNPN features Qualcomm Rel-17 Response to S2-2105279. Merged into S2-2106702 Sebastian (Qualcomm) this draft LS can be marked as merged into S2-2105312
Peter Hedman (Ericsson) I assumes merged into 5827 was meant.
Sebastian (Qualcomm) confirms that this draft LS can be marked as merged into 5827
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105621 LS OUT Approval [DRAFT] LS reply on clarifications on eNPN features vivo Rel-17 Response to S2-2105279. Merged into S2-2106702 Sebastian (Qualcomm) proposes to consider merged into S2-2105827
xiaowan (vivo) is OK to merge the LS out into S2-2105827
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105827 LS OUT Approval [DRAFT] Reply to LS on clarifications on eNPN features Ericsson Rel-17 Response to S2-2105279. Revised to S2-2106702, merging S2-2105312, S2-2105621, S2-2105801 and S2-2106048 Peter (Ericsson) provides comments and r01
Qianghua (Huawei) asks for clarification
Rainer (Nokia) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r03 as inline with SoH
Sebastian (Qualcomm) is ok with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106702 LS OUT Approval Reply to LS on clarifications on eNPN features SA WG2 Rel-17 Revision of S2-2105827r03, merging S2-2105312, S2-2105621, S2-2105801 and S2-2106048. (Response to S2-2105279 and S2-2105294). Approved Approved
8.2 S2-2106048 LS OUT Approval [DRAFT] Reply LS on clarifications on eNPN features Huawei, HiSilicon Rel-17 Response to S2-2105279. Merged into S2-2106702 Sebastian (Qualcomm) proposes to consider merged into S2-2105827
Qianghua (Huawei) agrees to mark this merged into S2-2105827
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105801 LS OUT Approval [DRAFT] Reply LS on clarifications on eNPN features Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2105279. Merged into S2-2106702 Rainer (Nokia) marks S2-2105801 as merged into S2-2105827
Rainer (Nokia) proposes to mark 5801 as merged into LS 5827.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105237 LS In Action LS from CT WG1: Reply LS on UE capabilities indication in UPU CT WG1 (C1-212599) Rel-17 Revision of postponed S2-2103760 from S2-145E. Response drafted in S2-2105821 and S2-2106277. Final response in S2-2106703
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105821 LS OUT Approval [DRAFT] Reply LS on UE capabilities indication in UPU Qualcomm Rel-17 Response to S2-2105237. r01 agreed. Revised to S2-2106703, merging S2-2106277 Qianghua (Huawei) proposes alt2, suggests use S2-2106277 as baseline
Peter (Ericsson) provides comments and r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106703 LS OUT Approval Reply LS on UE capabilities indication in UPU SA WG2 Rel-17 Revision of S2-2105821r01, merging S2-2106277. Approved Approved
8.2 S2-2106277 LS OUT Approval [DRAFT] Reply LS OUT on UE capabilities indication in UPU MediaTek Inc. Rel-17 Response to S2-2105237. Merged into S2-2106703 Peter (Ericsson) provides comments and suggests to mark the LS as merged into 5821.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105820 DISCUSSION Approval Way forward on UE capabilities indication in UPU. Qualcomm Incorporated Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105841 CR Approval 23.502 CR2997 (Rel-17, 'C'): Providing UE capability for additional parameters using UE Parameters Update via UDM Control Plane Procedure Ericsson Rel-17 Postponed Qianghua (Huawei) proposes to use alt.2, so proposes to use S2-2106279 as baseline
Peter Hedman (Ericsson) suggests to mark the CR as postponed
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106278 DISCUSSION Discussion The supported parameters set type indication for UPU procedure. MediaTek Inc., Huawei Rel-17 Noted Peter (Ericsson) provides comments
Chia-Lin (MediaTek) provides response
Peter Hedman (Ericsson) provides comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106279 CR Approval 23.502 CR3082 (Rel-17, 'B'): The supported parameters set type indication for UPU procedure MediaTek Inc., Huawei, [Nokia], [Nokia Shanghai Bell] Rel-17 Postponed Haris(Qualcomm) proposes to NOTE the CR and agree a CR based on alternative 1 instead or only send LS reply to CT1, SA3
Chia-Lin (MediaTek) disagreed to note the CR
Rainer (Nokia) comments.
Peter Hedman (Ericsson) provides comments and prefer alt-1 rather than alt-2 proposed in this CR.
Rainer (Nokia) replies to Peter (Ericsson).
Peter Hedman (Ericsson) provides reply
Rainer (Nokia) replies.
Qianghua (Huawei) comments
Peter Hedman (Ericsson) provides comments and seems we need to take this whole issue to CC for resolution
Qianghua (Huawei) replies
Jianning (Xiaomi) provides comment. We couldn't progress this CR furhter unless the dependent CR is agreed to introduce new parameters for UPU first.
Peter Hedman (Ericsson) suggests to mark the CR as postponed
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106280 CR Approval 23.502 CR3083 (Rel-17, 'B'): Update the UE parameters to UPU procedure MediaTek Inc. Rel-17 Merged into S2-2106722 Chia-Lin (MediaTek) suggests this tdoc merged to S2-2105828
Jihoon (ETRI) agrees with Chia-Lin (MediaTek).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106405 CR Approval 23.501 CR3215 (Rel-17, 'F'): Indication in UE capability supporting UE Parameter Update for eNPN-enabled UE Samsung Rel-17 Noted Qianghua (Huawei) provides comments
Kisuk (Samsung) provides comments.
Josep (DT) objects to this CR.
Peter Hedman (Ericsson) suggests to note the CR as we could not progress the UE capability aspects
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106406 CR Approval 23.502 CR3099 (Rel-17, 'F'): Indication in UE capability supporting UE Parameter Update for eNPN-enabled UE Samsung Rel-17 Noted Qianghua (Huawei) provides comments
Peter Hedman (Ericsson) suggests to note the CR as we could not progress the UE capability aspects
==== 8.X, 9.X Revisions Deadline ====
Kisuk (Samsung) ask to merge to 6280.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105368 LS In Information LS from ITU-T SG13: LS on the new work item ITU-T Y.NGNe-IBN-arch: 'Functional architecture of NGN evolution by adoption of Intent-Based Network' ITU-T SG13 (SG13-LS221) Postponed Peter (Ericsson) asks if this LS was misplaced to eNPN agenda item 8.2?
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106227 CR Approval 23.502 CR3070 (Rel-17, 'F'): Clarification on NRF service in case of SNPN Huawei, HiSilicon Rel-17 r07 agreed. Revised to S2-2106704 Xiaowan(vivo) provide r01
Hualin(Huawei) replied to Xiaowan(vivo).
Antoine (Orange) expresses concerns with the wording.
Dieter (Deutsche Telekom) agrees with Antoine (Orange) expresses concerns with the wording.
Hualin(Huawei) provide r02.
Peter Hedman (Ericsson) provides a question
Malla (NTT DOCOMO) provides comments.
Hualin(Huawei) replied to Malla (NTT DOCOMO).
Hualin(Huawei) replied to Peter Hedman (Ericsson).
Devaki (Nokia) comments.
Josep (DT) comments that the proposed wording makes a required parameter applicable to all NFs mutable. This would make the Rel'17 API not backwards-compatible.
Hualin(Huawei) replied to Devaki (Nokia).
Hualin(Huawei) replied to Josep (DT).
Hualin(Huawei) provide r04.
Josep (DT) proposes r05.
Peter Hedman (Ericsson) provides r06
Josep (DT) provides r07.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106704 CR Approval 23.502 CR3070R1 (Rel-17, 'F'): Clarification on NRF service in case of SNPN Huawei, HiSilicon Rel-17 Revision of S2-2106227r07. Approved Agreed
8.2 - - - KI#1 related - - Docs:=46 -
8.2 S2-2105236 LS In Action Reply LS on updating the Credentials Holder controlled lists for SNPN selection CT WG1 (C1-212419) Rel-17 Revision of postponed S2-2103747 from S2-145E. Response drafted in S2-2105832. Final response in S2-2106705
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105294 LS In Action LS from SA WG3: Reply LS on updating the Credentials Holder controlled lists for SNPN selection SA WG3 (S3-212208) Rel-17 Response drafted in S2-2105832. Final response in S2-2106702
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105832 LS OUT Approval [DRAFT] Reply LS on updating the Credentials Holder controlled lists for SNPN selection Ericsson Rel-17 Response to S2-2105236 and S2-2105294. r03 agreed. Revised to S2-2106702 Sebastian (Qualcomm) provides r01
Qianghua (Huawei) provides r02
Jianning (Xiaomi) shares the view with Qianghua (Huawei) and provide r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106705 LS OUT Approval Reply LS on updating the Credentials Holder controlled lists for SNPN selection SA WG2 Rel-17 Revision of S2-2105832r03. Approved Approved
8.2 S2-2105325 CR Approval 23.501 CR2999 (Rel-17, 'F'): Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR Qualcomm, Deutsche Telekom Rel-17 r05 agreed. Revised to S2-2106706, merging S2-2105833 and S2-2106306 Jianning (Xiaomi) provides r01 by merging the 6306, as this CR was agreed as basis for SoR progresses in the eNPN pre-eMeeting
Peter (Ericsson) provides r02 and supports the CR
Sebastian (Qualcomm) provides r03
Devaki (Nokia) provides r04 and supports this approach using SoR.
Qianghua (Huawei) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106706 CR Approval 23.501 CR2999R1 (Rel-17, 'F'): Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR Qualcomm, Deutsche Telekom, Xiaomi, Ericsson, Nokia, Nokia Shanghai Bell, Huawei Rel-17 Revision of S2-2105325r05, merging S2-2105833 and S2-2106306. Approved Agreed
8.2 S2-2105326 CR Approval 23.502 CR2889 (Rel-17, 'F'): Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR Qualcomm, Deutsche Telekom Rel-17 r05 agreed. Revised to S2-2106707, merging S2-2106305 Jianning (Xiaomi) provides r01 by merging the 6305, as this CR was agreed as basis for SoR progresses in the eNPN pre-eMeeting
Peter (Ericsson) provides comments and r02
Sebastian (Qualcomm) provides r03
Devaki (Nokia) provides r04 with minor fix and supports the CR.
Qianghua (Huawei) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106707 CR Approval 23.502 CR2889R1 (Rel-17, 'F'): Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR Qualcomm, Deutsche Telekom, Xiaomi, Ericsson, Nokia, Nokia Shanghai Bell, Huawei Rel-17 Revision of S2-2105326r05, merging S2-2106305. Approved Agreed
8.2 S2-2105558 DISCUSSION Endorsement Use of UPU or SoR to update CH controlled SNPN selection lists. Nokia, Nokia Shanghai Bell Rel-17 Noted Jianning (Xiaomi) proposes to NOTE this discussion paper, as most prefers SoR during the discussion in the eNPN pre-meeting
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105833 CR Approval 23.501 CR3096 (Rel-17, 'B'): Updating the Credentials Holder controlled lists for SNPN selection Ericsson Rel-17 Merged into S2-2106706 Jianning (Xiaomi) proposes to merge into 5325 that was agreed as basis for SoR progresses in the eNPN pre-eMeeting call
Peter (Ericsson) proposes to note the CR and mark the CR as merged into S2-2105325
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106059 CR Approval 23.501 CR3141 (Rel-17, 'F'): Update of CH controlled prioritized list of preferred SNPNs and GINs Huawei, HiSilicon Rel-17 Noted Antoine (Orange) proposes to Note this CR .
Qianghua (Huawei) OK to use SoR and note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106060 CR Approval 23.502 CR3034 (Rel-17, 'F'): Update of CH controlled prioritized list of preferred SNPNs and GINs Huawei, HiSilicon Rel-17 Noted Antoine (Orange) proposes to Note this CR .
Dieter (Deutsche Telekom) also proposes to note the CR.
Qianghua (Huawei) OK to use SoR and note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106305 CR Approval 23.502 CR3087 (Rel-17, 'B'): Support for update of Credentials Holder controlled prioritized list of preferred SNPNs Xiaomi Rel-17 Merged into S2-2106707 Jihoon (ETRI) asks for clarification.
Qianghua (Huawei) points out that this CR uses wrong TS version/template for updates, and proposes to merge this into other similar CR
Jianning (Xiaomi) proposes to merge into 5326 that was agreed as basis for SoR progresses in the eNPN pre-eMeeting
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106306 CR Approval 23.501 CR3195 (Rel-17, 'B'): Support for update of Credentials Holder controlled prioritized list of preferred SNPNs Xiaomi Rel-17 Merged into S2-2106706 Jianning (Xiaomi) proposes to merge into 5325 that was agreed as basis for SoR progresses in the eNPN pre-eMeeting
Sebastian (Qualcomm) proposes to mark as merged into 5325
Sebastian (Qualcomm): This CR overlaps with 5325 and hence it needs to be merged.
Jianning (Xiaomi) is ok to merge into 5325
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106307 DISCUSSION Discussion Discussion for updating the preferred list. Xiaomi Rel-17 Noted Jianning (Xiaomi) proposes to NOTE this discussion paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106407 CR Approval 23.502 CR3100 (Rel-17, 'F'): Update SNPN-enabled UE configured information for subscribed SNPN with UPU Samsung Rel-17 Merged into S2-2106722 Jianning (Xiaomi) proposes to NOTE this CR, as most prefers to progress SoR based on the discussion in the eNPN pre-meeting call.
Sebastian (Qualcomm) proposes to consider the CR merged into S2-2105828, which contains the credentials part
Kisuk (Samsung) provides comments.
Kisuk (Samsung) merges into S2-2105828.
Josep (DT) proposes to consider this CR merged with S2-2105828.
Rainer (Nokia) asks for clarification.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105271 LS In Action LS from RAN WG2: LS on Group IDs for Network selection (GINs) RAN WG2 (R2-2106545) Rel-17 Responses drafted in S2-2105314, S2-2105594, S2-2105826, S2-2106056 and S2-2106281. Final response in S2-2106708
==== 8.X, 9.X Final Deadline ====
Replied to
8.2 S2-2105314 LS OUT Approval [DRAFT] Reply LS on Group IDs for Network selection (GINs) Qualcomm Rel-17 Response to S2-2105271. Merged into S2-2106708 Antoine (Orange) proposes to Note this draft reply LS .
Sebastian (Qualcomm): the draft LS can be marked as merged into 5826
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105594 LS OUT Approval [DRAFT] LS reply on Group IDs for Network selection (GINs) vivo Rel-17 Response to S2-2105271. Merged into S2-2106708 Antoine (Orange) proposes to Note this draft reply LS .
xiaowan (vivo) replies to Antoine (Orange)
Amanda ( Futurewei ) support Vivo view that GIN should be encoded as an SNPN ID ( option a)
Sebastian (Qualcomm) suggests to merge into 5826
xiaowan (vivo) replies 5826 doesn't align with WA in CC#3
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) comments that there can only be one LS OUT.
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105826 LS OUT Approval [DRAFT] Reply to LS on Group IDs for Network selection (GINs) Ericsson Rel-17 Response to S2-2105271. r03 agreed. Revised to S2-2106708, merging S2-2105314, S2-2106056 and S2-2106281 xiaowan (vivo) comments
Peter Hedman (Ericsson) provides r01 being a compromise
Devaki (Nokia) is fine with r02.
Qianghua (Huawei) provides r02
Peter Hedman (Ericsson) provides r03 and comments
Qianghua (Huawei) asks for clarification
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides reply
Qianghua (Huawei) still asks
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106708 LS OUT Approval Reply to LS on Group IDs for Network selection (GINs) SA WG2 Rel-17 Revision of S2-2105826r03, merging S2-2105314, S2-2106056, S2-2106281 and S2-2105594. Approved Approved
8.2 S2-2106056 LS OUT Approval [DRAFT] Reply LS on Group IDs for Network selection (GINs) Huawei, HiSilicon Rel-17 Response to S2-2105271. Merged into S2-2106708 Antoine (Orange) proposes to Note this CR .
Antoine (Orange) proposes to Note this draft reply LS .
Sebastian (Qualcomm) suggests to merge into 5826
Qianghua (Huawei) OK to merge into 5826
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106281 LS OUT Approval [DRAFT] Reply LS OUT on Group IDs for Network selection (GINs) MediaTek Inc. Rel-17 Response to S2-2105271. Merged into S2-2106708 xiaowan (vivo) comments
Sebastian (Qualcomm) suggests to merge into 5826
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105556 CR Approval 23.501 CR3036 (Rel-17, 'F'): GIN Encoding Nokia, Nokia Shangai Bell Rel-17 r02 agreed. Revised to S2-2106709 Antoine (Orange) objects to this CR .
Devaki (Nokia) comments.
Devaki (Nokia) provides r01.
Josep (DT) asks for clarification.
Josep (DT) retracts the request for clarification.
Antoine (Orange): the coversheet is too pale!
Devaki (Nokia) provides r02 with updated cover sheet.
==== 8.X, 9.X Revisions Deadline ====
Hualin(Huawei) support the paper and hope can cosign it when uploading.
Xiaowan(vivo) support r02 and would like to cosign it
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106709 CR Approval 23.501 CR3036R1 (Rel-17, 'F'): GIN Encoding Nokia, Nokia Shangai Bell, Vivo, Huawei, HiSilicon Rel-17 Revision of S2-2105556r02. Approved Agreed
8.2 S2-2106055 CR Approval 23.501 CR3138 (Rel-17, 'F'): Corrections of the GIN encoding Huawei, HiSilicon Rel-17 Noted Antoine (Orange) objects to this CR .
Qianghua (Huawei) replies
Devaki (Nokia) provides r01, merge changes to section 5.30.2.1 to 5556.
Qianghua (Huawei) provides r02
Sebastian (Qualcomm) objects to the CR
Antoine (Orange) objects to r00, r01 and r02 .
xiaowan (vivo) provides r03
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) also objects to r03.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106229 CR Approval 23.501 CR3174 (Rel-17, 'F'): Clarification on GIN assignment model Huawei, HiSilicon Rel-17 Noted Sebastian (Qualcomm) objects to the CR because it is not FASMO (CR adds a note only)
Antoine (Orange) objects to this CR .
Hualin(Huawei) indicate this is R17 paper, not R16. 'Not FASMO' is not valid comments.
Hualin(Huawei) replied to Antoine (Orange).
Devaki (Nokia) also objects to the CR.
Peter Hedman (Ericsson) provides comment that CR is not needed and propose to note the CR
Hualin(Huawei) is ok to note.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105592 CR Approval 23.501 CR3045 (Rel-17, 'F'): Handling of SUPI/SUCI format when accessing to a SNPN vivo Rel-17 r04 agreed. Revised to S2-2106710 xiaowan (vivo) provides r01 to clarify: 'PLMN ID of the SNPN is not necessary to be unique among SNPNs' for option of 'different PLMN ID'
Peter Hedman (Ericsson) provides comment
Josep (DT) comments. Most importantly that PLMN ID assignment is not in scope of 3GPP. Does not add anything new. Proposes to NOTE.
Devaki (Nokia) comments and provides r02.
Qianghua (Huawei) provides r03
Peter Hedman (Ericsson) provides r04
Saso (Intel) supports r04 and is happy to co-sign
==== 8.X, 9.X Revisions Deadline ====
xiaowan (vivo) is also OK with r04
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106710 CR Approval 23.501 CR3045R1 (Rel-17, 'F'): Handling of SUPI/SUCI format when accessing to a SNPN Vivo, Nokia, Nokia Shanghai Bell, Ericsson, Intel Rel-17 Revision of S2-2105592r04. Approved Agreed
8.2 S2-2105830 DISCUSSION Agreement KI#1, IMSI based SUPI support when access an SNPN using credentials owned by CH. Ericsson Rel-17 Noted Xiaowan(vivo) comment
Sebastian (Qualcomm) comments
Xiaowan(vivo) replies to Sebastian (Qualcomm)
Peter Hedman (Ericsson) provides reply
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105831 CR Approval 23.502 CR2994 (Rel-17, 'B'): IMSI based SUPI support when access an SNPN using credentials owned by CH Ericsson Rel-17 r03 agreed. Revised to S2-2106711 Xiaowan(vivo) comments and suggest to discuss under S2-2105830 firstly
Sebastian (Qualcomm) asks a question
Peter Hedman (Ericsson) provides reply
Peter Hedman (Ericsson) provides replies
Peter Hedman (Ericsson) provides r01 and a question
Devaki (Nokia) comments.
xiaowan (vivo) replies to Peter Hedman (Ericsson)
Sebastian (Qualcomm) provides r02
Devaki (Nokia) objects to the CR. Sorry, we cannot make N(R)F deployment option based on network identifier.
Jianning (Xiaomi) provides comment
Peter Hedman (Ericsson) ok with r02 and provides a reply
Josep (DT) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) comments that r03 (Note X) duplicates text from 23.501 to the call flow in 23.502, do not see the need for r03. Objects to r02, r01, r00 as NRF deployment cannot be determined by network identifier.
Devaki (Nokia) can live with r03 (although I don't think same text is necessary in 502, can live with it if others are ok with it as well).
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106711 CR Approval 23.502 CR2994R1 (Rel-17, 'B'): IMSI based SUPI support when access an SNPN using credentials owned by CH Ericsson Rel-17 Revision of S2-2105831r03. Approved Agreed
8.2 S2-2105797 CR Approval 23.501 CR2919R1 (Rel-17, 'B'): IMSI based SUPI support when access an SNPN using credentials owned by CH Ericsson Rel-17 Revision of (Postponed) S2-2104332 from S2-145E. CC#4: r03 agreed. Revised to S2-2106669. Xiaowan(vivo) comments and suggest to discuss under S2-2105830 firstly
Peter (Ericsson) provides comments and r01
Devaki (Nokia) objects to this CR and its revisions. Assuming Routing ID to be centrally managed or coordinated is not backward compatible nor practical for deployments.
Devaki (Nokia) comments.
Peter Hedman (Ericsson) provides r02 and comments
Josep (DT) objects to r00, r01. Asks to ignore erroneous r02
Qianghua (Huawei) asks questions
Peter Hedman (Ericsson) provides r03 and comments
Devaki (Nokia) proposes to merge this paper with 5592 as the proposed addition does not work without the background assumption in the note.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) comment that the CR was not merged into 5592 and question the technical correctness of Nokia comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106669 CR Approval 23.501 CR2919R2 (Rel-17, 'B'): IMSI based SUPI support when access an SNPN using credentials owned by CH Ericsson Rel-17 Revision of S2-2105797r03. Approved Agreed
8.2 S2-2106057 CR Approval 23.501 CR3139 (Rel-17, 'F'): Selection of AUSF supporting primary authentication towards AAA server Huawei, HiSilicon Rel-17 Approved Xiaowan(vivo) comments and suggest to discuss under S2-2105830 firstly
Qianghua (Huawei) replies
xiaowan (vivo) seeks clarification for the need of 'routing indicator' in AAA case
Qianghua (Huawei) provides r01
Peter Hedman (Ericsson) provides question to vivo
xiaowan (vivo) replies to Peter Hedman (Ericsson)
==== 8.X, 9.X Revisions Deadline ====
Qianghua (Huawei) thanks Vivo confirmation for r00, I also prefer r00
Devaki (Nokia) comments that the addition must refer to the note added by 5592r04 as Routing ID does not work in this proposal when the stated assumption is not valid.
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2105829 CR Approval 23.501 CR3095 (Rel-17, 'B'): Reference point AUSF - NSSAAF Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2106417 CR Approval 23.501 CR3218 (Rel-17, 'F'): UE Authentication/Authorization with AAA Server in Credentials Holder Samsung Rel-17 Noted Haris(Qualcomm) proposes to note this CR
Qianghua (Huawei) proposes to note this CR
Kisuk (Samsung) notes this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105873 CR Approval 23.502 CR3003 (Rel-17, 'F'): UE context fetch during registration procedure considering SNPN involved. Samsung Rel-17 Noted Qianghua (Huawei) provides comments
Sebastian (Qualcomm) objects to the CR. There is no need for this change as the same needs to be done already between PLMNs.
Youngkyo(Samsung) provides reply to the comments
Peter Hedman (Ericsson) provides question
Devaki (Nokia) comments.
Youngkyo(Samsung) replies and provides a revision r02.
Sebastian (Qualcomm) objects also to the revisions
Youngkyo(Samsung) asks Sebastian (Qualcomm) a reason for objection on the r02.
Josep (DT) objects to r00, r01, r02.
Youngkyo(Samsung) replies to Josep(DT).
Peter Hedman (Ericsson) provides comments
Youngkyo(Samsung) replies to the comment.
==== 8.X, 9.X Revisions Deadline ====
Youngkyo(Samsung) provides a new wording.
Sebastian (Qualcomm) objects to all revs and suggests to bring this CR back at the next meeting
Youngkyo(Samsung) is okay to note it for now and will bring this CR back at the next meeting as a general topic
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106058 CR Approval 23.501 CR3140 (Rel-17, 'F'): Support of the default configured NSSAI and Network Slicing Subscription Change Indication in the SNPN Huawei, HiSilicon Rel-17 Noted Sebastian (Qualcomm) objects to the CR because it is an alignment with Stage 3, will therefore not lead to any change from functional or protocol perspective and hence is not FASMO
Peter Hedman (Ericsson) provides comment
Devaki (Nokia) comments.
Qianghua (Huawei) replies
Peter Hedman (Ericsson) provides reply
==== 8.X, 9.X Revisions Deadline ====
Sebastian (Qualcomm) confirms objection
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106061 CR Approval 23.502 CR3035 (Rel-17, 'F'): Update UE subscription to contain information indicating authentication towards AAA server Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106712 Sebastian (Qualcomm) provides r01
xiaowan (vivo) provides comments
Qianghua (Huawei) replies
Devaki (Nokia) comments and provides r02.
xiaowan (vivo) seeks clarification
xiaowan (vivo) further comments
xiaowan (vivo) provides r03
Qianghua (Huawei) replies, prefer r02
Peter Hedman (Ericsson) provides r04
xiaowan (vivo) replies
==== 8.X, 9.X Revisions Deadline ====
xiaowan (vivo) is fine with r04
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106712 CR Approval 23.502 CR3035R1 (Rel-17, 'F'): Update UE subscription to contain information indicating authentication towards AAA server Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2106061r04. Approved Agreed
8.2 S2-2106228 CR Approval 23.501 CR3173 (Rel-17, 'F'): Clarification on NF profile in case of SNPN Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2106713 Antoine (Orange): change is incorrect.
Hualin(Huawei) replied to Antoine (Orange).
Devaki (Nokia) comments.
Josep (DT) objects to r00, provides r01.
xiaowan (vivo) comments
Josep (DT) replies to xiaowan (vivo).
Hualin(Huawei) replied to Devaki (Nokia).
Josep (DT) comments that the prior comment should state 'Hualing (Huawei) comments, provides r02'.
Josep (DT) comments, provides r03.
Peter Hedman (Ericsson) provides r04
Josep (DT) clarifies that it is not OK to add in r04 this generalization that now applies to all NFs, not only UDM/AUSF.
Antoine (Orange): agrees with Josep and provides r05.
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) objects to r00, r04
Peter Hedman (Ericsson) ok with r05, the intention was not to spread to other NFs
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106713 CR Approval 23.501 CR3173R1 (Rel-17, 'F'): Clarification on NF profile in case of SNPN Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2106228r05. Approved Agreed
8.2 S2-2106230 CR Approval 23.501 CR3175 (Rel-17, 'F'): Clarification on functionality of NF in SNPN Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106714 Sebastian (Qualcomm) comments that the new bullet needs to be moved to the first list in that clause (the second list is about non-3GPP related functionality)
Antoine (Orange) provides r01 .
Devaki (Nokia) comments.
Hualin(Huawei) is also fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106714 CR Approval 23.501 CR3175R1 (Rel-17, 'F'): Clarification on functionality of NF in SNPN Huawei, HiSilicon Rel-17 Revision of S2-2106230r01. Approved Agreed
8.2 S2-2106231 CR Approval 23.501 CR3176 (Rel-17, 'F'): Clarification on CAG list Huawei, HiSilicon Rel-17 Noted Sebastian (Qualcomm) objects to the CR as it is not FASMO; CAG list provisioning is orthogonal to provisioning for NSSAA or secondary auth.
Hualin(Huawei) indicate this is R17 CR, 'not FASMO' is not valid comments
Sebastian (Qualcomm) comments
Hualin(Huawei) replied to Sebastian (Qualcomm).
Sebastian (Qualcomm) confirms objection
Jianning (Xiaomi) provide comments
Hualin(Huawei) indicate this is not new feature and don't need to be in the exception sheet, so Qualcomm's comment is not valid.
Josep (DT) comments that the CR is unclear regardless of its objectability on grounds of the exception sheet.
Peter Hedman (Ericsson) provides comment
Hualin(Huawei) replied to Peter Hedman (Ericsson).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 - - - KI#2 related - - Docs:=4 -
8.2 S2-2105412 CR Approval 23.501 CR3012 (Rel-17, 'B'): Example of utilizing exposure capability between overlay network and underlay network Ericsson, Futurewei Rel-17 Merged into S2-2106715 Devaki (Nokia) proposes that this should be considered merged with S2-2105608 or noted (as already indicated during last meeting, implementation details are not needed in a spec annex).
Jihoon (ETRI) provides comments.
Sebastian (Qualcomm) proposes to consider this merged into 5608
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105557 CR Approval 23.501 CR3037 (Rel-17, 'F'): Exposure capability between overlay network and underlay network Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106715 Devaki (Nokia) proposes to consider this merged with S2-2105608.
Jihoon (ETRI) provides comments with concerns.
Devaki (Nokia) proposes to consider this merged with S2-2105608 as the two CRs are related to resolving the same EN.
==== 8.X, 9.X Revisions Deadline ====
Jihoon (ETRI) agrees with Devaki (Nokia).
Jihoon (ETRI) indicates that we agrees with Devaki(Nokia)'s proposal to accept S2-2105608r03, not to merge this CR with S2-2105608 for now.
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105608 CR Approval 23.501 CR3052 (Rel-17, 'F'): Informative guidelines for usage of QoS related exposure capabilities to leverage between underlay network and overlay network ETRI Rel-17 r03 agreed. Revised to S2-2106715, merging S2-2105412 and S2-2105557 Devaki (Nokia) provides r01.
Jihoon (ETRI) is okay with r01, but has a few questions.
Devaki (Nokia) replies to ETRI.
Marco (Huawei) considering past history of this discussion, OK with r01
Amanda ( Futurewei ) prefers to keep the note as original version if we decide to use this contribution as compromising between 3 contributions
Belen (Ericsson) asks a question for clarification.
Devaki (Nokia) replies.
Jihoon (ETRI) replies to Belen (Ericsson).
Belen (Ericsson) asks ETRI for an example of how QoS Monitoring will work.
Belen (Ericsson) replies to ETRI and asks further questions.
Belen (Ericsson) provides r02, objects to r01 and initial version
Hualin(Huawei) object r02.
Belen (Ericsson) replies to Huawei.
Belen (Ericsson) provides r03 removing the EN, and replies to ETRI.
Jihoon (ETRI) does not agree at least with r03.
Devaki (Nokia) objects to r02, original version. OK with r01 or r03.
Saso (intel) proposes to agree r03.
Marco (Huawei) is ok with r03.
==== 8.X, 9.X Revisions Deadline ====
Futurewei is ok with r03 to move forward and consider S2-2105412 is merged with S2-2105608r03.
Jihoon (ETRI) accepts r03 to move forward.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106715 CR Approval 23.501 CR3052R1 (Rel-17, 'B'): Informative guidelines for usage of QoS related exposure capabilities to leverage between underlay network and overlay network ETRI, Nokia, Nokia Shanghai Bell, Ericsson, Futurewei Rel-17 Revision of S2-2105608r03, merging S2-2105412 and S2-2105557. Approved Agreed
8.2 - - - KI#3 related - - Docs:=13 -
8.2 S2-2105238 LS In Information LS on limited service availability of an SNPN CT WG1 (C1-212601) Rel-17 Revision of postponed S2-2103762 from S2-145E. Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105274 LS In Information LS from RAN WG2: Reply LS on limited service availability of an SNPN RAN WG2 (R2-2106777) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105250 LS In Information LS from CT WG1: LS on emergency services in an SNPN deployed in an area which does not belong to any country CT WG1 (C1-213960) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105424 CR Approval 23.228 CR1245 (Rel-17, 'F'): SNPN support for 1 to N independent IMS Providers Ericsson Rel-17 eNPN_Ph2 is not a valid WI Code. r04 agreed. Revised to S2-2106716, merging S2-2106242 Haris(Qualcomm) comments and asks question for clarification
George (Ericsson) provides responses inline.
Rainer (Nokia) comments.
Ashok (Samsung) provides comments
George (Ericsson) provides responses.
Rainer (Nokia) replies and proposes new text.
George (Ericsson) provides a response
Haris (Qualcomm) comments
George (Ericsson) provides r01, and comments
Hualin(Huawei) provide comments.
zhendong(ZTE), provides r02
Saso (Intel) supports r02
George (Ericsson)provides a response.
Hualin(Huawei) replied to George (Ericsson).
George (Ericsson)provides a response. The UE subscribed DNN exists in both the AMF and SMF subscription data. This is how it is today. However as clearly seen in the r02 the SMF selects the P-CSCF as is this case today.
Hualin (Huawei) comments.
Hualin (Huawei) provide r03 to clarify the existing procedure.
Haris (Qualcomm) asks question for clarification
George (Ericsson) provides a response.
Haris (Qualcomm) comments and provides r04
Ashok (Samsung) needs clarification
George (Ericsson) asks a question. Not sure I follow the use case. Can U please clarify with more details. What subscriptions the UE has, and what is the UE connected to do, and trying to do.
Ashok (Samsung) responds to George
George (Ericsson) responds. This is not a use case that is supported. A UE will have credentials of only a single ISH if the SNPN supports multiple IMS providers. We need normative text to support the use case, and I don't see any requirement for that in Release 17 at least. It is possible that the UE has an IMS PLMN subscription in addition to this SNPN ISH subscription. That will work and is not an issue.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) is OK with r04
Rainer (Nokia) is ok with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106716 CR Approval 23.228 CR1245R1 (Rel-17, 'F'): SNPN support for 1 to N independent IMS Providers Ericsson Rel-17 Revision of S2-2105424r04, merging S2-2106242. Approved Agreed
8.2 S2-2106241 CR Approval 23.167 CR0366 (Rel-17, 'B'): 23.167 SNPN use IMS service from multiple IMS providers Huawei, HiSilicon Rel-17 Postponed George Foti (Ericsson) provides comment. This is conditional on 5424 progressing.
Haris (Qualcomm) comments
Hualin(Huawei) replied to Haris (Qualcomm) and provide r01.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) we need to postpone this CR. This has to many cases and such a simplistic statement may be wrong. We need to examine all the cases thoroughly now that we have many more to consider
Hualin(Huawei) replied to George(Ericsson): we have two weeks to consider and comments. Can you clarify what is the specific technical issue you discover in the last day?
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106242 CR Approval 23.228 CR1247 (Rel-17, 'B'): 23.228 SNPN use IMS service from multiple IMS providers Huawei, HiSilicon Rel-17 Merged into S2-2106716 George Foti (Ericsson) proposes to note the CR as it is merged in 5424
Hualin(Huawei) ok to merge it to 5424
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105593 CR Approval 23.501 CR3046 (Rel-17, 'F'): Correct emergency services for SNPN case vivo Rel-17 Noted Rainer (Nokia) asks for clarification.
Xiaowan(vivo) replies to Rainer (Nokia)
Haris(Qualcomm) indicates that we can only accept the CR with the first change
George (Ericsson) proposed to note the CR. 5837 covers clearly all what is needed.
xiaowan (vivo) replies to Haris(Qualcomm)
Myungjune (LGE) comments.
zhendong(ZTE), provides r01
Dieter (Deutsche Telekom) agrees with George (Ericsson) and also proposes to note the CR.
Xiaowan (vivo)provides r02 and seek clarification for the reverse direction.
Haris(Qualcomm) objects to the CR given the first change is covered in other CR
xiaowan (vivo) replies and provide r03
George (Ericsson) provides a response. I don't see the ambiguity, There is select SNPN or PLMN. There is nothing implying from both. This text is not ther.
So this CR is not needed.
==== 8.X, 9.X Revisions Deadline ====
Haris(Qualcomm) objects to the CR, all revisions included
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105837 CR Approval 23.501 CR3098 (Rel-17, 'C'): SNPN support for emergency Ericsson Rel-17 Approved Rainer (Nokia) prefers S2-2105837.
Dieter (Deutsche Telekom) agrees with Rainer (Nokia) and also prefers S2-2105837.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2106404 CR Approval 23.501 CR3214 (Rel-17, 'F'): Correction on emergency services in SNPN Samsung Rel-17 Noted George Foti (Ericsson) proposes to note the CR. 5837 covers what is needed
Dieter (Deutsche Telekom) agrees with George (Ericsson) and also proposes to note the CR.
Kisuk (Samsung) notes this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106304 CR Approval 23.501 CR3194 (Rel-17, 'F'): Alignment for supporting emergency service in SNPN Xiaomi Rel-17 Noted. Covered by S2-2105837 George Foti (Ericsson) proposes to note the CR. 5837 covers all what is needed
Dieter (Deutsche Telekom) agrees with George (Ericsson) and also proposes to note the CR.
Jianning (Xiaomi) propose to merge and select 5837 for further progress, and prefer to mark this CR as merged
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106052 CR Approval 23.228 CR1246 (Rel-17, 'F'): IMS Support for SNPN Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106717 Ashok (Samsung) seeks clarification
Qianghua (Huawei) replies
Ashok (Samsung) comments
Rainer (Nokia) comments.
George (Ericsson) comments.
Saso (Intel) proposes r01.
Rainer (Nokia) if ok with r01.
Ashok (Samsung) is fine with r01.
George (Ericsson) OK with r01.
Qianghua (Huawei) OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106717 CR Approval 23.228 CR1246R1 (Rel-17, 'F'): IMS Support for SNPN Huawei, HiSilicon, Intel Rel-17 Revision of S2-2106052r01. Approved Agreed
8.2 - - - KI#4 related - - Docs:=52 -
8.2 S2-2105456 DISCUSSION Approval NSSAA procedure for UE without pre-provisioned credentials Qualcomm Rel-17 Noted Hualin(Huawei) comments.
Saso (Intel) seeks clarification.
Huan(Vivo) seeks clarification.
Kundan(NEC) provides comments.
Haris (Qualcomm) comments
Rainer (Nokia) asks for clarification.
Hualin(Huawei) replied to Haris (Qualcomm).
Haris (Qualcomm) responds
Huan (Vivo) asks for clarifications
Chia-Lin (MediaTek) ask for clarification and think the condition itself does not exist
Huan (Vivo) comments that the problem may not exist and ask for clarification
Hualin(Huawei) propose to note, since this is a new feature but not in the exception sheet. And the technical issue is still not clear to several companies.
Saso (Intel) proposes to postpone the CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105457 CR Approval 23.501 CR3017 (Rel-17, 'F'): NSSAA without pre-provisioned credentials Qualcomm Incorporated Rel-17 Noted Hualin(Huawei) propose to note, since this is a new feature but not in the exception sheet. And the technical issue is still not clear to several companies as discussed in S2-2105456.
Saso (Intel) proposes to postpone the CR given that the underlying issue is proposed for discussion for the first time, was not detected during the study and is not part of the approved exceptions.
Haris (Qualcomm) comments that is fine to note the CR based on technical arguments but this is a Cat.F CR and there is no justification to note it because it is not in the exception sheet
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105458 CR Approval 23.502 CR2913 (Rel-17, 'F'): NSSAA without provisioned credentials Qualcomm Incorporated Rel-17 Noted Rainer (Nokia) asks for clarification.
Hualin(Huawei) propose to note, since this is a new feature but not in the exception sheet. And the technical issue is still not clear to several companies as discussed in S2-2105456.
Saso (Intel) proposes to postpone the CR given that the underlying issue is proposed for discussion for the first time, was not detected during the study and is not part of the approved exceptions.
Haris (Qualcomm) comments that is fine to note the CR based on technical arguments but this is a Cat.F CR and there is no justification to note it because it is not in the exception sheet
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105602 CR Approval 23.501 CR3049 (Rel-17, 'F'): KI#4-SNPN UE Onboarding using existing DNN Samsung Rel-17 r01 agreed. Revised to S2-2106718 Antoine (Orange): provides r01 (terminology fix).
Ashok (Samsung) is Ok with r01
Hualin(Huawei) is Ok with r01
Rainer (Nokia) comments.
Ashok (Samsung) responds to Rainer
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106718 CR Approval 23.501 CR3049R1 (Rel-17, 'F'): KI#4-SNPN UE Onboarding using existing DNN Samsung Rel-17 Revision of S2-2105602r01. Approved Agreed
8.2 S2-2105603 CR Approval 23.502 CR2945 (Rel-17, 'F'): KI#4-SNPN UE Onboarding using existing DNN Samsung Rel-17 Postponed Huan (vivo) seeks clarification for the motivation of S2-2105603.
Ashok (Samsung) clarifies to Huan
Huan (vivo) response to Ashok.
Ashok (Samsung) provides comments to Huan
Qianghua (Huawei) questions the need for this CR
Ashok (Samsung) explains to Qianghua
Huan (Vivo) comments
Ashok (Samsung) clarifies to Huan (Vivo)
Ashok (Samsung) responds Huan (Vivo)
Josep (DT) points out that 'ME impact' must be also checked in this CR. Objects to r00
Huan (Vivo) comments and suggests to postpone this CR
Ashok (Samsung) does not agree with Josep (DT) and gives more explanation
Ashok (Samsung) responds to Huan (Vivo)
Josep (DT) clarifies. Also supports to postpone this CR.
Ashok (Samsung) agrees to postpone it
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2105604 CR Approval 23.501 CR3050 (Rel-17, 'F'): KI#4- PDU Session release after SNPN UE onboarding Samsung Rel-17 Noted Huan (vivo) seeks clarification for SMF releases Onboarding PDU session in S2-2105604.
Rainer (Nokia) objects to S2-2105604
Ashok (Samsung) clarifies
Qianghua (Huawei) comments
Ashok (Samsung) responds to Qianghua
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105620 CR Approval 23.501 CR3053 (Rel-17, 'F'): Correct the UE Configuration for ON-SNPN selection w.r.t. prioritized list of preferred SNPNs and GINs vivo Rel-17 Noted Haris(Qualcomm) objects to the CR
Xiaowan(vivo) replies to Haris(Qualcomm) and provide r01
Qianghua (Huawei) provides comments
xiaowan (vivo) replies
==== 8.X, 9.X Revisions Deadline ====
Haris(Qualcomm) objects to r01 and all revisions
Peter Hedman (Ericsson) provides comment that agree that CR is not needed
Xiaowan(vivo) questions Peter Hedman (Ericsson) : do you think the credential holder can explicitly exclude the holder of default credential ?
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105791 CR Approval 23.501 CR3084 (Rel-17, 'F'): Interaction between PVS and SO-SNPN Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2105792 CR Approval 23.501 CR3085 (Rel-17, 'C'): DCS providing PVS address to ONN Nokia, Nokia Shanghai Bell, Ericsson Rel-17 CC#4: Approved Megha(Intel) asks for clarification
Rainer (Nokia) replies.
Hualin(Huawei) replied to Rainer (Nokia).
Rainer (Nokia) replies to Hualin (Huawei).
zhendong(ZTE), provides the comments to hualin
Hualin(Huawei) replied to zhendong(ZTE).
Peter Hedman (Ericsson) provides replies
Hualin(Huawei) replied to Peter Hedman (Ericsson).
Peter Hedman (Ericsson) provides reply
Hualin(Huawei) propose to use 5822 as the baseline and merge this paper to 5822.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) does not agree with the merge proposal from Huawei
Hualin(Huawei) propose to note. Not merge.
Hualin(Huawei) withdraw the objection to make progress.
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2105793 CR Approval 23.502 CR2982 (Rel-17, 'C'): DCS providing PVS address to ONN Nokia, Nokia Shanghai Bell, Ericsson Rel-17 CC#4: r01 agreed. Revised, Merging S2-2106429, to S2-2106670. Hualin (Huawei) propose to note this paper, and take S2-2105822 as baseline.
Rainer (Nokia) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106670 CR Approval 23.502 CR2982R1 (Rel-17, 'C'): DCS providing PVS address to ONN Nokia, Nokia Shanghai Bell, Ericsson, Samsung Rel-17 Revision of S2-2105793r01, merging S2-2106429. Approved Agreed
8.2 S2-2105822 CR Approval 23.501 CR3093 (Rel-17, 'F'): Provisioning data configuration Qualcomm Incorporated Rel-17 Noted Rainer (Nokia) asks for clarification.
Haris (Qualcomm) comments
Peter Hedman (Ericsson) provides question
Hualin(Huawei) consider 5822(this paper) is a better way in this release. So, we support this paper.
Haris (Qualcomm) comments that the CR has dependency in other CRs e.g. S2-2105792 or S2-2106165 but can be considered 'fallback' if nothing is agreed
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) proposes to note or postpone the CR
Rainer (Nokia) proposes to note 5822.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106165 CR Approval 23.501 CR3158 (Rel-17, 'B'): KI#4, clarification on the PVS IP address or PVS FQDN for UP Remote Provisioning ZTE Rel-17 Noted Jihoon (ETRI) does not see the need for this CR.
zhendong(ZTE), provides the response
Jihoon (ETRI) replies to zhendong (ZTE).
Hualin(Huawei) provide r01.
Rainer (Nokia) asks for clarification.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and object to r01
zhendong(ZTE) ask peter to confirm your comment is not align with r01,
Rainer (Nokia) objects to r01.
zhendong(ZTE) if 5792 is aprroved, r01 can be apprvoded, otherwise Note this.
Hualin(Huawei) is ok with r01 or original version.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106243 CR Approval 23.501 CR3180 (Rel-17, 'B'): 23.501 proposal in case DCS provide the PVS address Huawei, HiSilicon Rel-17 WITHDRAWN Marco (Huawei) withdraws the document and point out that only the SID proposal in S2-2106240 has to be considered for any further discussion.
==== 8.X, 9.X Revisions Deadline ====
Rainer (Nokia) proposes to note or postpone 6243 and go with 5792 for this meeting.
==== 8.X, 9.X Final Deadline ====
Withdrawn
8.2 S2-2106426 CR Approval 23.501 CR3219 (Rel-17, 'F'): Obtaining PVS IP address or PVS FQDN for UP Remote Provisioning Samsung Rel-17 Noted. Covered by (noted) S2-2105822 Peter (Ericsson) provides comments and suggest to consider the CR merged into 5792
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) objects to this CR. It should not be approved by mistake.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106429 CR Approval 23.502 CR3107 (Rel-17, 'F'): Obtaining PVS IP address or PVS FQDN for UP Remote Provisioning Samsung Rel-17 Merged into S2-2106670 Peter (Ericsson) provides comment that CR overlaps with 5793 i.e. can they be merged?
Rainer (Nokia) replies.
==== 8.X, 9.X Revisions Deadline ====
Kisuk (Samsung) replies.
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105795 CR Approval 23.501 CR3086 (Rel-17, 'C'): Onboarding de-registration timer handling in case of AMF re-allocation Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106719 Antoine (Orange) asks a question.
Hualin(Huawei) have similar question as Antoine (Orange).
Rainer (Nokia) replies.
Qianghua (Huawei) proposes merge this into 06053
Rainer (Nokia) agrees and proposes to mark 5795 as merged into 6053.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105839 CR Approval 23.501 CR3100 (Rel-17, 'C'): Support for change of AMF and implementation specific deregistration timer Ericsson Rel-17 Merged into S2-2106719 Qianghua (Huawei) proposes merge this into 06053
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105840 CR Approval 23.502 CR2996 (Rel-17, 'C'): Support for change of AMF when onboarding Ericsson Rel-17 Merged into S2-2106720 Qianghua (Huawei) proposes merge this into 06054
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106053 CR Approval 23.501 CR3137 (Rel-17, 'F'): AMF relocation for UE registered for onboarding Huawei, HiSilicon Rel-17 r07 agreed. Revised to S2-2106719, merging S2-2105795, S2-2105839 and S2-2106166 Qianghua (Huawei) provides r01
Rainer (Nokia) provides r02.
xiaowan (vivo) seeks clarification on an indicator in UE context that the UE is registered for onboarding
Qianghua (Huawei) replies
Josep (DT) clarifies that it is 'SNPN onboarding', provides r04, asks to disregard r03.
Peter Hedman (Ericsson) provides r05 and comments partly question the new logic for AMF selection
Haris (Qualcomm) asks question for clarification and suggests r06
Qianghua (Huawei) provides r07 and replies
Haris (Qualcomm) is fine with r07 but asks question
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106719 CR Approval 23.501 CR3137R1 (Rel-17, 'F'): AMF relocation for UE registered for onboarding Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2106053r07, merging S2-2105795, S2-2105839 and S2-2106166. Approved Agreed
8.2 S2-2106054 CR Approval 23.502 CR3033 (Rel-17, 'F'): AMF relocation for UE registered for onboarding Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2106720, merging S2-2105840 Qianghua (Huawei) provides r01
Josep (DT) provides r02.
Josep (DT) proves r03, retracts r02.
Peter Hedman (Ericsson) provides r04
Rainer (Nokia) provides r05.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106720 CR Approval 23.502 CR3033R1 (Rel-17, 'F'): AMF relocation for UE registered for onboarding Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106054r05, merging S2-2105840. Approved Agreed
8.2 S2-2106166 CR Approval 23.501 CR3159 (Rel-17, 'B'): KI#4, clarification on the AMF re-allocation and Deregistration timer ZTE Rel-17 Merged into S2-2106719 Antoine (Orange) asks a question.
zhendong(ZTE), provides the response
Antoine (Orange): But how does the target AMF know that the UE is registered for onboarding?
Qianghua (Huawei) proposes merge this into 06053
zhendong(ZTE), it is fine to me on the merge proposal
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106412 CR Approval 23.501 CR3217 (Rel-17, 'F'): Extending Deregistration Timer for UE Onboarding Samsung Rel-17 Noted Antoine (Orange): Since the timer is implementation specific, it can't be extended at the UE request.
Kisuk (Samsung): provides comments to Antonie.
Qianghua (Huawei) provides comments
Peter Hedman (Ericsson) provides comments and propose to not impact the UE
Kisuk (Samsung) provides comments.
Haris (Qualcomm) objects to the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106414 CR Approval 23.502 CR3103 (Rel-17, 'F'): Extending Deregistration Timer for UE Onboarding Samsung Rel-17 Noted Antoine (Orange) doesn't agree with this CR.
Kisuk (Samsung) provides comments to Antoine.
Rainer (Nokia) comments.
Kisuk (Samsung) provides comments.
Josep (DT) proposes to note this CR. CR removes agreed functionlity and adds new functionality.
Qianghua (Huawei) provides comments
xiaowan (vivo) provides comments
Kisuk (Samsung) notes this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105794 CR Approval 23.502 CR2983 (Rel-17, 'C'): Onboarding indication from NG-RAN to AMF Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106721 Qianghua (Huawei) proposes to postpone this CR
Peter (Ericsson) provides comments that CR now overlaps with 5835 i.e. propose we consider this merged into 5835
Rainer (Nokia) agrees that 5794 can be marked as merged into 5835.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105796 CR Approval 23.502 CR2984 (Rel-17, 'C'): ME identity check in case of onboarding Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106721 Qianghua (Huawei) proposes to merge with S2-2105835
Rainer (Nokia) replies.
Peter Hedman (Ericsson) provides replies and also propose to consider the CR merged
Rainer (Nokia) is ok to mark 5796 as merged into 5835.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105798 CR Approval 23.501 CR3087 (Rel-17, 'C'): Consistent configuration of onboarding S-NSSAI in NG-RAN and AMF Nokia, Nokia Shanghai Bell Rel-17 Noted Huan(Vivo) seeks clarification.
Rainer (Nokia) replies and provides r1.
Peter Hedman (Ericsson) questioning the need for the modified functionality
Rainer (Nokia) replies.
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) does not understand the NPN-specifics here.
Rainer (Nokia) proposes to postpone the CR.
Peter Hedman (Ericsson) objects to the CR, all revisions
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105799 CR Approval 23.502 CR2985 (Rel-17, 'C'): Handling Allowed NSSAI during onboarding Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106721 Haris(Qualcomm) comments on the wording of one sentence
Rainer (Nokia) replies to Haris (Qualcomm).
Haris(Qualcomm) proposes r01
Rainer (Nokia) is ok with r01.
Rainer (Nokia) proposes to mark 5799 as merged into 5835.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105835 CR Approval 23.502 CR2995 (Rel-17, 'C'): Registration procedure for onboarding SNPN Ericsson Rel-17 r03 agreed. Revised to S2-2106721, merging S2-2105794, S2-2105796, S2-2105799, S2-2106164 and S2-2106187 Qianghua (Huawei) provides r01
Rainer (Nokia) provides r02.
Hualin(Huawei) provides r03.
zhendong(ZTE) also proposes to move forward in this way
Rainer (Nokia) asks for clarification.
==== 8.X, 9.X Revisions Deadline ====
Yunjing (CATT) proposes a way forward.
Rainer (Nokia) replies.
Haris (Qualcomm) comments
Peter Hedman (Ericsson) ok with r02 or r03
Hualin(Huawei) can only accept r03.
Rainer (Nokia) can accept r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106721 CR Approval 23.502 CR2995R1 (Rel-17, 'C'): Registration procedure for Onboarding SNPN Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105835r03, merging S2-2105794, S2-2105796, S2-2105799, S2-2106164 and S2-2106187. Approved Agreed
8.2 S2-2106187 CR Approval 23.502 CR3054 (Rel-17, 'F'): Solve FFS in Registration with Onboarding SNPN procedure CATT Rel-17 Merged into S2-2106721 Qianghua (Huawei) proposes to postpone this CR
Peter (Ericsson) proposes to mark the CR as merged into 5835
==== 8.X, 9.X Revisions Deadline ====
Yunjing (CATT) is ok to merged this CR into 5835
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2106049 CR Approval 23.501 CR3135 (Rel-17, 'B'): AN sends onboarding indication to AMF in registration procedure Huawei, HiSilicon Rel-17 Postponed Josep (DT) asks question for clarification.
Qianghua (Huawei) agrees to postpone
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106050 CR Approval 23.502 CR3032 (Rel-17, 'B'): AN sends onboarding indication to AMF in registration procedure Huawei, HiSilicon Rel-17 Postponed Josep (DT) has a similar comment as with 6049.
Qianghua (Huawei) agrees to postpone
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2106164 CR Approval 23.502 CR3047 (Rel-17, 'F'): KI#4, clarification on the onboarding indication from AN to AMF. ZTE Rel-17 Merged into S2-2106721 Qianghua (Huawei) proposes to postpone this CR
zhendong(ZTE) proposes, this CR is merged into S2-2105835,
Peter (Ericsson) proposes we consider the CR as merged into 5835 in which the same EN is removed.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2105828 CR Approval 23.502 CR2801R1 (Rel-17, 'C'): Additional parameters using UE Parameters Update via UDM Control Plane Procedure Ericsson, Huawei Rel-17 Revision of (Postponed) S2-2104338 from S2-145E. r03 agreed. Revised to S2-2106722, merging S2-2106280 and S2-2106407 Haris(Qualcomm) comments and asks question
Devaki (Nokia) comments.
Jianning (Xiaomi) provides comment
Peter Hedman (Ericsson) provides r01 and comments
Peter Hedman (Ericsson) provides r02
Jihoon (ETRI) provides r03 to add ETRI as cosigner.
==== 8.X, 9.X Revisions Deadline ====
Jianning (Xiaomi) prefer to pontpone this CR, wait for progress from SA3.
Peter Hedman (Ericsson) prefer to agree the CR as it will finalize the functional aspects under SA2 responsibility and further guide SA3
Qianghua (Huawei) same view as Peter, SA2 needs to make a decision, taking also that 23501 already supports UPU for PNI-NPN remote provisioning
Antoine (Orange) also thinks we should agree this CR (r03) at this meeting..
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106722 CR Approval 23.502 CR2801R2 (Rel-17, 'C'): Additional parameters using UE Parameters Update via UDM Control Plane Procedure Ericsson, Huawei, Samsung, ETRI Rel-17 Revision of S2-2105828r03, merging S2-2106280 and S2-2106407. Approved Agreed
8.2 S2-2106129 CR Approval 23.501 CR3146 (Rel-17, 'F'): Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization vivo Rel-17 r03 agreed. Revised to S2-2106723 Peter (Ericsson) provides comments and questions
Haris(Qualcomm) comments and provides r01
Hualin(Huawei) further clarify it in r02.
xiaowan (vivo) replies to Peter (Ericsson)
xiaowan (vivo) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106723 CR Approval 23.501 CR3146R1 (Rel-17, 'F'): Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization Vivo Rel-17 Revision of S2-2106129r03. Approved Agreed
8.2 S2-2106398 CR Approval 23.501 CR3211 (Rel-17, 'B'): Removal of editor's note for remote provisioning of credentials for NSSAA or secondary authentication/authorization China Mobile Rel-17 Noted Haris(Qualcomm) proposes to NOTE and wait for SA3
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2105834 CR Approval 23.501 CR3097 (Rel-17, 'B'): Format of SUCI/SUPI used for Onboarding Ericsson Rel-17 r04 agreed. Revised to S2-2106724 Megha(Intel) provides r01 and comments
Xiaowan(vivo) provides comments
Rainer (Nokia) ask for clarification.
Haris (Qualcomm) proposes r02
Josep (DT) asks a basic question for clarification.
Qianghua (Huawei) provides comments
Peter Hedman (Ericsson) provides r03
Peter Hedman (Ericsson) provides r04
Rainer (Nokia) replies.
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is ok with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106724 CR Approval 23.501 CR3097R1 (Rel-17, 'B'): Format of SUCI/SUPI used for Onboarding Ericsson Rel-17 Revision of S2-2105834r04. Approved Agreed
8.2 S2-2105836 CR Approval 23.501 CR2921R1 (Rel-17, 'B'): UE onboarding architecture Ericsson, Rel-17 Revision of (Noted) S2-2104335 from S2-145E. r02 agreed. Revised to S2-2106725 Megha(Intel) provides r01 and comments
Haris (Qualcomm) objects to r01
Jianning (Xiaomi) provide comment
Peter Hedman (Ericsson) provides r02
Jianning (Xiaomi) is ok to r02
Haris (Qualcomm) provides r03
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is ok with r03
Jianning (Xiaomi) is ok with r03. But still believe the text in NOTE x should show somewhere
Peter Hedman (Ericsson) prefer to approve r02 as with r03 it is hard to understand whether the UE uses onboarding procedure or normal procedures when having CH credentials
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2106725 CR Approval 23.501 CR2921R2 (Rel-17, 'B'): UE onboarding architecture Ericsson Rel-17 Revision of S2-2105836r02. Approved Agreed
8.2 S2-2105912 CR Approval 23.502 CR3008 (Rel-17, 'F'): Correct the NRF services between SNPN and DCS vivo Rel-17 Noted Jihoon (ETRI) provides r01.
Qianghua (Huawei) replies
Peter Hedman (Ericsson) proposes to postpone the CR due to disagreement on DCS architecture.
xiaowan (vivo) provides r02
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) objects to this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106051 CR Approval 23.501 CR3136 (Rel-17, 'F'): Terminology correction for UE onboarding Huawei, HiSilicon Rel-17 Approved Josep (DT) objects to this CR.
Qianghua (Huawei) replies and clarifies the intention
Josep (DT) accepts r00. r01 can be disregarded.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2106186 CR Approval 23.501 CR3165 (Rel-17, 'F'): Clarification of the AMF Onboarding Configuration Data CATT Rel-17 Approved Hualin(Huawei) indicate this paper rely on discussion on S2-2106243.
==== 8.X, 9.X Revisions Deadline ====
Rainer (Nokia) comments.
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2106244 CR Approval 23.501 CR3181 (Rel-17, 'F'): Secondary authentication for onboarding Huawei, HiSilicon Rel-17 Noted Jianning (Xiaomi) provides comments
Hualin(Huawei) replied to Jianning (Xiaomi).
Haris(Qualcomm) comments and proposes to note
Rainer (Nokia) agrees with Haris (Qualcomm).
Jianning (Xiaomi) provides furhter comments
Jianning (Xiaomi) shares the view with Haris (Qualcomm) and Rainer (Nokia)
Hualin(Huawei) replied.
==== 8.X, 9.X Revisions Deadline ====
Haris (Qualcomm) objects to r00
Peter Hedman (Ericsson) provides comment
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106408 CR Approval 23.501 CR3216 (Rel-17, 'F'): Registration with PDU Session Establishment for UE Onboarding Samsung Rel-17 Noted Antoine (Orange): It is not the role of the AMF to initiate the establishment of a PDU Session.
Kisuk (Samsung) provides comments to Antoine.
Qianghua (Huawei) comments that this violates the SM/MM separation principle
Jianning (Xiaomi) shares the view that SM/MM seperation principle should be not violated
Josep (DT) comments that this also has RAN impact. Objects to this CR.
Kisuk (Samsung) provides comments.
Josep (DT) has severe doubts the TEID allocation would work in this form without RAN impact.
Rainer (Nokia) objects to 6408.
Rainer (Nokia) replies.
Qianghua (Huawei) asks for clarification
Kisuk (Samsung) replies.
Kisuk (Samsung) provides revision r01.
Antoine (Orange) objects to this CR (r00 and r01).
Peter Hedman (Ericsson) agree that CR is proposing new functionality not part of exception i.e. we object to the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2106410 CR Approval 23.502 CR3101 (Rel-17, 'F'): Registration with PDU Session Establishment for UE Onboarding Samsung Rel-17 Noted Antoine (Orange): This CR proposes a new functionality, not acceptable after the freeze.
Kisuk (Samsung) provides comments to Antoine.
Rainer (Nokia) comments.
Kisuk (Samsung) comments.
Haris (Qualcomm) objects to the CR
Qianghua (Huawei) share same views with other commenters
Kisuk (Samsung) provides comments.
Jianning (Xiaomi) provides comment
Peter Hedman (Ericsson) provides comment that proposal is adding new functionality not part of exception
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=153 -
8.3 S2-2105296 LS In Action Reply LS on IP address to GPSI translation SA WG3 (S3-212355) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2105235 LS In Action LS from SA WG6: Reply LS on IP address to GPSI translation SA WG6 (S6-211082) Rel-17 Revision of postponed S2-2103745 from S2-145E. Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2105346 CR Approval 23.501 CR2385R4 (Rel-17, 'B'): Support of the mapping from IP addressing information provided to an AF to the user identity Nokia, Nokia Shanghai Bell, Rel-17 Revision of (Postponed) S2-2100229 from S2#143-e. Noted Laurent (Nokia): comments on Tdocs 5501/5502 versus Tdoc 5346/5347
Josep (DT) comments for 5346/5347, 5501/5502; prefers the approach of setting a new NF service for the identifier translation.
Magnus (Ericsson) is ok to focus the discussion on this thread and provides S2-2105346r01 . Ericsson prefers the approach in 5501/5502 but a revision of 5346 is needed regardless of the approach taken.
Dario (Qualcomm) explains we need to describe how to enforce different IDs for different AFs/AF requests and provides r02
Magnus (Ericsson) provides S2-2105346r03 and a link to r01 .
Dan(China Mobile) provides r04 and support the non-MSISDN AF specific GPSI
Hyesung (Samsung) provides r05 and comments.
Laurent (Nokia): answers and provides r06
Magnus (Nokia): ask questions provide comments
Hui (Huawei) provide comments
Dario (Qualcomm) replies to Laurent that it is up to Stage 2 to solve the issue of having unique UE ext IDs per AF/AF request.
Hyesung (Samsung) agrees with Dario (Qualcomm) that it is up to stage 2 to solve this issue.
Hui (Huawei) provides r07.
Magnus O (Ericsson) provides r08.
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) asks for clarification.
Hyesung (Samsung) is ok with r08, but not ok with r06 and r07.
Dario (Qualcomm) comments and asks questions for clarification.
Susana (Vodafone) objects to r08 as it introduces an EN that is not needed. 23.003 indicates the multiplicity of External Identifiers and the normative text in this CR addresses the need to have different External Identifiers for different AFs. Vodafone supports r07.
Magnus (Ericsson) can only accept r08 and objects to r00-r07 in their current form.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105347 CR Approval 23.502 CR2329R3 (Rel-17, 'B'): Support of the mapping from IP addressing information provided to an AF to the user identity Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2100230 from S2#143-e. Noted Laurent (Nokia): comments on Tdocs 5501/5502 versus Tdoc 5346/5347
Dan (China Mobile) would like to have less impact in 502
Magnus (Ericsson) comments
Laurent (Nokia): answers
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) prefers to less changes to existing services.
Dario (Qualcomm)'s understanding is that 5347 and 5502 are mutually exclusive and asks clarification.
Susana (Vodafone) prefers 5502 to this CR for the impacts related to UE ID retrieval
Susana (Vodafone) comments
Magnus O (Ericson) object to the document in it's current form
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105501 CR Approval 23.501 CR3024 (Rel-17, 'B'): AF specific UE ID retrieval Ericsson Rel-17 CC#4: Technically Endorsed Laurent (Nokia): comments on Tdocs 5501/5502 versus Tdoc 5346/5347
==== 8.X, 9.X Revisions Deadline ====
Susana (Vodafone) can agree with this CR as it does not clash with 5346. This CR is a complement to the description in 5346 and is acceptable for Vodafone
Magnus (Ericsson) clarifies that 5501/02 is a complement to 5346 (does not replace it).
Laurent (Nokia): Can accept 5501/5502 as a complement of 5346/5347. thinks that the whole topic should be postpone
==== 8.X, 9.X Final Deadline ====
Endorsed
8.3 S2-2105502 CR Approval 23.502 CR2926 (Rel-17, 'B'): AF specific UE ID retrieval Ericsson Rel-17 r02 agreed. Revised to S2-2106726 Dario S. Tonesi (Qualcomm) ask question for clarification
Laurent (Nokia): comments on Tdocs 5501/5502 versus Tdoc 5346/5347
Magnus O (Ericsson) provides an answer
Dario (Qualcomm) provides r01
Magnus O (Ericsson) provides r02
==== 8.X, 9.X Revisions Deadline ====
Susana (Vodafone) can live with either r02 or r01
Laurent (Nokia): objects to R00 and R01. Could accept 5501/5502 as a complement of 5346/5347. thinks that the whole topic should be postponed
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106726 CR Approval 23.502 CR2926R1 (Rel-17, 'B'): AF specific UE ID retrieval Ericsson Rel-17 Revision of S2-2105502r02. CC#4: Technically Endorsed Endorsed
8.3 - - - General - - Docs:=11 -
8.3 S2-2105230 LS In Information LS from GSMA Operator Platform Group on edge computing definition and integration GSMA OPG (OPG_52_Doc_03) Revision of postponed S2-2103728 from S2-145E. Noted Hui (Huawei) proposes to note this LS.
Magnus (Ericsson) agrees with Hui, this LS should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105361 LS In Action LS from GSMA OPG: LS from GSMA Operator Platform Group on edge computing definition and integration. GSMA OPG (OPG_52_Doc_03) Noted Hui (Huawei) proposes to note this LS.
Magnus (Ericsson) agrees with Hui, this LS should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105300 LS In Information LS from SA WG5: Reply LS on Edge computing definition and integration SA WG5 (S5-213443) Rel-17 Noted Hui (Huawei) proposes to note this LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105301 LS In Information LS from SA WG5: Reply LS on EDGEAPP SA WG5 (S5-213445) Rel-17 Noted Hui (Huawei) proposes to note this LS.
Magnus (Ericsson) agrees with Hui, this LS should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105303 LS In Action LS from SA WG5: LS reply to SA on GSMA 3GPP Edge Computing coordination.doc SA WG5 (S5-213449) Rel-17 Noted Hui (Huawei) proposes to note this LS.
Magnus (Ericsson) agrees with Hui, this LS should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105366 LS In Information LS from TSG SA: Reply LS to GSMA Operator Platform Group on edge computing definition and integration TSG SA (SP-210583) Rel-17 Noted Hui (Huawei) proposes to note this LS.
Magnus (Ericsson) agrees with Hui, this LS should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105352 P-CR Approval 23.548: 23.548 should be equally applicable to PLMN(s) and to SNPN(s). Nokia, Nokia Shanghai Bell Rel-17 Approved Dan(China Mobile) comments
Laurent (Nokia): answers
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2105763 P-CR Approval 23.548: Change ME to MT. Tencent Rel-17 r01 agreed. Revised to S2-2106727 Hui (Huawei) provides r01.
Chunshan(Tencent) is OK with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106727 P-CR Approval 23.548: Change ME to MT. Tencent Rel-17 Revision of S2-2105763r01. Approved Approved
8.3 S2-2105993 P-CR Approval 23.548: Differentiated DNS services. vivo Rel-17 r02 agreed. Revised to S2-2106728 Dario S. Tonesi (Qualcomm) asks question for understanding.
Huazhang (vivo) replies to Dario
Hui (Huawei) provides comments.
Huazhang (vivo) provides r01 and reply to Hui
Dario (Qualcomm) replies to Huazhang that this seems a new feature.
Hui (Huawei) provides r02
Laurent (Nokia): Comments , supporting Darios' concerns
Huazhang (vivo) is ok to r02 and response to Dario and Laurent
Hui (Huawei): responses.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) cannot accept r00, r01 but he is OK with r02.
Huazhang (vivo) agree to move on r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106728 P-CR Approval 23.548: Differentiated DNS services. Vivo Rel-17 Revision of S2-2105993r02. Approved Approved
8.3 - - - Issue on UE doesn't use EASDF - - Docs:=8 -
8.3 S2-2105579 P-CR Approval 23.548: Network action related with the UE not using the EASDF's IP address for its DNS Query. Nokia, Nokia Shanghai Bell Rel-17 Noted Magnus H (Ericsson) provides comments
Dan (China Mobile) support this paper and please add CMCC as supporting company
Jicheol (Samsung) asks a question for clarification
Laurent (Nokia): Answers
Zhuoyun (Tencent) questions the need of this paper and prefers the way forward in 6256.
Hui(Huawei) asks questions.
Josep (DT) sees this pCR is useful, but it does agree that it solves the EN. Provides r01
Dario (Qualcomm) provides r02.
Zhuoyun (Tencent) doesn't think this contribution is needed and suggests the way forward in 6256.
Jicheol (Samsung) asks a question for clarification.
Tingfang Tang (Lenovo) comments and provide r03.
Magnus H (Ericsson) comments
Xiaobo Yu (Alibaba) provides comments and suggests to consider merging this contribution to 6256
==== 8.X, 9.X Revisions Deadline ====
Zhuoyun (Tencent) objects to r00-r02, and is fine to consider merging this contribution to 6256.
Josep (DT) objects to r00.
Sudeep (Apple) asks a question.
Susana (Vodafone) objects to r00 and agrees with Josep (DT)
Laurent (Nokia): Comments; I agree R00 is not suitable. R02 is the preferred one
Susana (Vodafone) prefers r02, objecting to r03 since it precludes other nodes to log this information e.g. for charging.
Zhuoyun (Tencent) still questions the need of this contribution and objects to r00-r02.
Hui (Huawei) objects to any revision of the paper.
Zhuoyun (Tencent) also objects r03.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105984 P-CR Approval 23.548: How to guarantee that the UE uses the EASDF as DNS Server . Sony Rel-17 Noted Dario S. Tonesi (Qualcomm) comments
Zhuoyun (Tencent) supports the contribution.
Susana (Vodafone) proposes to note this proposal
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) objects this contribution.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105992 P-CR Approval 23.548: Correction the statement of DNS overriding to user's private DNS configuration. vivo Rel-17 CC#4: r02 + changes agreed. Revised to S2-2106671. Dario S. Tonesi (Qualcomm) comments
huazhang (vivo) reply to Dario(QC) and provide r01
huazhang (vivo) provides r02 and add Futurewei as co-sign
==== 8.X, 9.X Revisions Deadline ====
Susana (Vodafone) objects to any revision of this paper. The modifications of the normative text (in 6.2.3.2.2) introduced in the different revisions are not acceptable.
Huazhang (vivo) can's accept Susana's objection because r02 there is no 6.2.3.2.2, all of the changes in 6.2.3.2.2 is removed, only the Annex C is changing for informative.
Hui (Huawei) objects to r01-r02 and clarify this paper should be updated before agreed to remove the first change to 6.2.3.2.2.
==== 8.X, 9.X Final Deadline ====
Huazhang (vivo) thanks for the suggestion from NiHui and move to CC#4
Revised
8.3 S2-2106671 P-CR Approval 23.548: Correction the statement of DNS overriding to user's private DNS configuration. Vivo, Futurewei Rel-17 Revision of S2-2105992r02 + changes. Approved Approved
8.3 S2-2106256 P-CR Approval 23.548: Remove EN on UE using MNO DNS configuration. Huawei, Hisilicon Rel-17 Revision of (Noted) S2-2104505 from S2-145E. Noted Sudeep (Apple) comments on the proposed NOTE1 from Hui (Huawei)
Dario (Qualcomm) explains that this pCR does not solve the problem we need to address.
Sudeep (Apple) provides r01.
Sudeep (Apple) responds to Dario (Qualcomm).
Jicheol (Samsung) answers to Susana (Vodafone)
Zhuoyun (Tencent) supports this contribution.
Huazhang (vivo) has concerns about this indication and provides r02
Riccardo (NTT DOCOMO) provides r03 to apply the edge indication to other cases
Zhuoyun (Tencent) provides r04 based on r03 provided by Riccardo.
Riccardo (NTT DOCOMO) comments on r04
Huazhang (vivo) provides r05 based on r04
Zhuoyun (Tencent) replies.
==== 8.X, 9.X Revisions Deadline ====
Zhuoyun (Tencent) is fine with r00-r05.
Dario (Qualcomm) objects to r00-r05
Susana (Vodafone) objects r00-r05 and comments
Yang (OPPO) objects all revisions and original version since it is unclear how the UE is informed (explicitly or implicitly) as question provided before.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106257 CR Approval 23.501 CR3185 (Rel-17, 'B'): Indication of DNS configuration for edge service Huawei, Hisilicon Rel-17 Noted Dario S. Tonesi (Qualcomm) points out that this CR does not solve the problem we need to address.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) objects to this document.
Susana (Vodafone) proposes to note this document with the same comment expressed in 6256 thread .
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106258 CR Approval 23.502 CR3076 (Rel-17, 'B'): Indication and update of DNS configuration for edge service Huawei, Hisilicon Rel-17 Noted Dario S. Tonesi (Qualcomm) points out that this CR does not solve the problem we need to address.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) objects to this document.
Susana (Vodafone) proposes to note this document with the same comment expressed in 6256 thread .
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106480 P-CR Approval 23.548: EAS rediscovery: Edge DNS Client based EAS (re-)discovery. Qualcomm Incorporated, Vodafone, T-Mobile, AT&T, Charter, CMCC, Telecom Italia, NTT DoCoMo, Telstra, Orange, Ericsson, Deutsche Telekom, Verizon Wireless, Telefonica Rel-17 Noted Hui (Huawei) provides r01.
Huazhang (vivo) triggers technique discussion of EDC
Josep (DT) comments.
Riccardo (NTT DOCOMO) comments
Svante (Sony) comments with concerns
Dario (Qualcomm) provides r02 and replies to Huawei and Apple.
Huazhang (vivo) replies to Josep
Huazhang (vivo) comments
Josep (DT) replies to Sudeep (Apple).
Dario (Qualcomm) replies to Huazhang (Vivo).
Susana (Vodafone) agrees with Josep (DT) mail and adds comments
Sudeep (Apple) responds to comments. Objects to r02.
Zhuoyun (Tencent) needs clarification on the intention of the solution and has concerns on the solution.
Riccardo (NTT DOCOMO) asks a clarification to Sudeep (Apple)
Josep (DT) replies to Sundeep (Apple).
Dario (Qualcomm) replies to Sundeep (Apple)
Huazhang (vivo) don't agree with there exist no DNS hijacking
Huazhang (vivo) replies to Dario (QC).
Tingfang Tang (Lenovo) asks clarification on the EDC solution and clarifies indication that a DNS server is for Edge services .
Jicheol proposes to note this paper.
John (Futurewei) has some concerns
Dario (Qualcomm) replies to Samsung, Lenovo, Vivo, Tencent and Futurewei and provides r03
Zhuoyun (Tencent) comments.
Tingfang Tang (Lenovo) comments.
Dario (Qualcomm) provides r04
Jicheol (Samsung) objects to the original version, r01, r02, r03, and r04.
Apostolis (Lenovo) comments.
Riccardo (NTT DOCOMO) have a question on Apostolis' comment.
Sudeep (Apple) adds comments.
Magnus H (Ericsson) asks questions
Sudeep (Apple) requests this contribution to be NOTED.
==== 8.X, 9.X Revisions Deadline ====
Sudeep (Apple) objects to the original version and all revisions of this contribution (r01, r02, r03, r04 and r05).
Microsoft echoes the concerns raised by Apple and other device vendors and objects to the original version and all revisions of 6480.
==== 8.X, 9.X Final Deadline ====
Dario (Qualcomm) asks questions to Apostolis
Noted
8.3 - - - Multiple ECS options - - Docs:=3 -
8.3 S2-2105349 P-CR Approval 23.548: Allowing (in some cases) the usage of multiple DNS ECS options / L-DNS servers in clause 6.2.3.2.2 . Nokia, Nokia Shanghai Bell Rel-17 Noted Hui (Huawei) provides comment.
Laurent (Nokia): answers
Hui (Huawei) responses to Laurent.
Magnus O (Ericsson) comments.
Hui (Huawei): further comments
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) proposes to note this paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106140 P-CR Approval 23.548: Update of the EAS discovery procedure with EASDF. Tencent Rel-17 Noted. Covered by S2-2106260 Hui (Huawei) proposes to consider this paper as merged into S2-2106260.
Laurent (Nokia): Comments
Magnus O (Ericsson): Propose to note or consider this document merged with 6260.
Zhuoyun (Tencent) is fine to merge this contribution to 6260.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106260 P-CR Approval 23.548: Determine the information for ECS option from multiple candidate DNAIs. Huawei, Hisilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 - - - Support node level EAS deployment info - - Docs:=36 -
8.3 S2-2105400 P-CR Approval 23.548: EAS Deployment Information Management / procedural aspects. Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105401 P-CR Approval 23.548: EAS Deployment Information Management / data aspects. Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. CC#4: Postponed Hui (Huawei) suggests to take this paper as baseline for UDR data structure of EAS Deployment Info.
Xinpeng (Huawei) ask for clarification.
Xinpeng (Huawei) provides r01.
Laurent (Nokia): provides r02
==== 8.X, 9.X Revisions Deadline ====
Xinpeng(Huawei) comments.
Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson) comments
Magnus H (Ericsson) we object to all revisions. We can accept r02 if the following changes is provided:
- add 'and/or Application ID' as part of 'Data Key = S-NSSAI and/or DNN and/or DNAI ' and align text in 7.X.1.1.2
- remove bullet 2
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2106729 P-CR Approval 23.548: EAS Deployment Information Management / data aspects. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105401r02. CC#4: WITHDRAWN Withdrawn
8.3 S2-2105503 P-CR Approval 23.548: EAS deployment info provisioning. Ericsson Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105504 CR Approval 23.501 CR3025 (Rel-17, 'B'): NEF service to support EAS deployment info Ericsson Rel-17 r05 agreed. Revised to S2-2106730, merging S2-2105986, S2-2106033, S2-2106035, S2-2106037, S2-2106131 and S2-2106290 Hui (Huawei) suggests to take this paper as baseline for 23.501 CR for node level EAS deployment info.
Xinpeng (Huawei) ask for clarifications.
Laurent (Nokia): provides r01
Tingfang Tang (Lenovo) provides r02.
Magnus H (Ericsson) provides r03
Xinpeng(Huawei) provides r04.
Tingfang Tang (Lenovo) provides r05.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106730 CR Approval 23.501 CR3025R1 (Rel-17, 'B'): NEF service to support EAS deployment info Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 Revision of S2-2105504r05, merging S2-2105986, S2-2106033, S2-2106035, S2-2106037, S2-2106131 and S2-2106290. Approved Agreed
8.3 S2-2105505 CR Approval 23.502 CR2927 (Rel-17, 'B'): New NEF service to support EAS deployment info Ericsson Rel-17 r03 agreed. Revised to S2-2106731, merging S2-2105590, S2-2106032, S2-2106291 and S2-2106495 Hui (Huawei) suggests to take this paper as baseline for 23.502 CR for node level EAS deployment info.
Laurent (Nokia): aks a question
Laurent (Nokia): provides r01
Xinpeng(Huawei) provides r02.
Tingfang Tang (Lenovo) provides r03.
Magnus H (Ericsson) provides r04
Xinpeng (Huawei) comments.
Laurent (Nokia): provides r05
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) comments
Xinpeng (Huawei) agree with r03 and objects to all other revisions.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106731 CR Approval 23.502 CR2927R1 (Rel-17, 'B'): New NEF service to support EAS deployment info Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 Revision of S2-2105505r03, merging S2-2105590, S2-2106032, S2-2106291 and S2-2106495. Approved Agreed
8.3 S2-2105506 CR Approval 23.503 CR0610 (Rel-17, 'B'): EC service info for DNS handling Ericsson Rel-17 Noted Hui (Huawei) suggests to take this paper as baseline for 23.503 CR for node level EAS deployment info.
Laurent (Nokia): Comments / potential concern
Zhuoyun (Tencent) Comments.
Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson) provides r01 and comments
Magnus H (Ericsson) comments
==== 8.X, 9.X Revisions Deadline ====
Xinpeng (Huawei) objects to any revision of 5506.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105510 P-CR Approval 23.548: Solving EN about uniqueness of DNS handling Rules Ericsson Rel-17 r01 agreed. Revised to S2-2106732 Jicheol (Samsung) supports this paper, i.e. introduction of 'DNS Handling Rule Identity'.
and asks a question whether 'rule operation (e.g. add/update/delete)' is also needed.
Magnus H (Ericsson) answers
Hui (Huawei) suggests to consider this paper merged into S2-2106294.
Tingfang Tang (Lenovo) provides r01.
Magnus H (Ericsson) comments
Tingfang Tang (Lenovo) replied to Magnus.
==== 8.X, 9.X Revisions Deadline ====
Xinpeng(Huawei) suggest to merge 5510 into 6294.
Tingfang Tang (Lenovo) replies to Xinpeng.
Xinpeng (Huawei) agree keep 5510 alone, not merged into 6294.
Tingfang Tang (Lenovo) is OK with r01, objects r00.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106732 P-CR Approval 23.548: Solving EN about uniqueness of DNS handling Rules Ericsson Rel-17 Revision of S2-2105510r01. Approved Approved
8.3 S2-2105511 P-CR Approval 23.548: Provisioning of node level DNS handling rules to EASDF Ericsson Rel-17 Merged into S2-2106734 Hui (Huawei) suggests to consider this paper merged into S2-2106294.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105512 P-CR Approval 23.548: Solving EN about EASDF retrieving node-level DNS message handling rules uniqueness of DNS handling Rules Ericsson Rel-17 Merged into S2-2106734 Hui (Huawei) suggests to consider this paper merged into S2-2106294.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105586 P-CR Agreement 23.548: Solving the conflict between Session level DNS message handling rules and Node level DNS message handling rules. China Unicom Rel-17 Merged into S2-2106734 Hui (Huawei) suggests to consider this paper merged into S2-2106294.
Tianqi (ChinaUnicom) approves this paper merged into S2-2106294.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105590 CR Agreement 23.502 CR2942 (Rel-17, 'F'): Session level and Node level EAS deployment information China Unicom Rel-17 Merged into S2-2106731 Hui (Huawei) suggests to consider this paper merged into S2-2105505
.
Tianqi (ChinaUnicom) approves this paper merged into S2-2105505.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105616 P-CR Approval 23.548: Dynamic retrieval of EAS Deployment Information by EASDF. Samsung Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105986 CR Approval 23.501 CR3123 (Rel-17, 'F'): Update of EAS information in PCC rules vivo Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105987 CR Approval 23.503 CR0635 (Rel-17, 'F'): Update of EAS deployment information in PCC rules vivo Rel-17 Merged into S2-2105506 (noted). Noted Hui (Huawei) suggests to consider this paper merged into S2-2105506
.
Laurent (Nokia): objects to any revision of this paper
Huazhang (vivo) agree to merge
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106031 P-CR Approval 23.548: EAS Deployment Information provision from AF. Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106733, merging S2-2105503, S2-2105616, S2-2106292, S2-2106293, S2-2105994 and S2-2105400 Hui (Huawei) suggests to take this paper as baseline for node level EDI between AF-NEF-UDR and SMF.
Xinpeng (Huawei) provides r01.
Laurent (Nokia): provides r02
Magnus H (Ericsson) comments
Xinpeng(Huawei) provides r03.
Tingfang Tang (Lenovo) suggests to move the NEF services to 5505 for 23.502 as it is better to have the 5G NEF service in one place.
Magnus H (Ericsson) provides r05
Laurent (Nokia): provides r06
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) asks about potential issues with Figure 6.2.3.4.Y-1.
Xinpeng(Huawei) confirms to Dario (Qualcomm) that the message 4 should goes to the NEF in Figure 6.2.3.4.Y-1.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106733 P-CR Approval 23.548: EAS Deployment Information provision from AF. Huawei, HiSilicon, Lenovo, Motorola Mobility Rel-17 Revision of S2-2106031r06, merging S2-2105503, S2-2105616, S2-2106292, S2-2106293, S2-2105994 and S2-2105400. Approved Approved
8.3 S2-2106032 CR Approval 23.502 CR3029 (Rel-17, 'F'): EAS Deployment Information Management Huawei, HiSilicon Rel-17 Merged into S2-2106731 Hui (Huawei) suggests to consider this paper merged into S2-2105505
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106033 CR Approval 23.501 CR3128 (Rel-17, 'F'): EAS Deployment information management in NEF Huawei, HiSilicon Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106034 P-CR Approval 23.548: Node Level DNS handling information on EASDF. Huawei, HiSilicon Rel-17 Merged into S2-2106734 Hui (Huawei) suggests to consider this paper merged into S2-2106294.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106035 CR Approval 23.501 CR3129 (Rel-17, 'F'): Node Level DNS handling Information Management in the EASDF Huawei, HiSilicon Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106037 CR Approval 23.501 CR3130 (Rel-17, 'F'): EAS Provision Information via AF Request Huawei, HiSilicon Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105994 P-CR Approval 23.548: EAS deployment information provided from AF and the node-level based DNS handling rules. vivo Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106131 CR Approval 23.501 CR3147 (Rel-17, 'F'): Update with EAS deployment information Tencent Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
Zhuoyun (Tencent) is ok to merge this paper into S2-2105504 as suggested by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106141 P-CR Approval 23.548: Solving the editor's notes in the node level EAS deployment information management. Tencent Rel-17 Merged into S2-2106734 Hui (Huawei) suggests to consider this paper merged into S2-2106294.
Zhuoyun (Tencent) is ok to merge this paper into S2-2106294 as suggested by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106289 DISCUSSION Approval Updating the Node Level EAS Deployment Information Management. Lenovo, Motorola Mobility Rel-17 Noted Hui (Huawei) proposes to note this discussion paper.
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106290 CR Approval 23.501 CR3191 (Rel-17, 'F'): Update the feature of AF influence on traffic routing Lenovo, Motorola Mobility Rel-17 Merged into S2-2106730 Hui (Huawei) suggests to consider this paper merged into S2-2105504
.
Tingfang Tang (Lenovo) is ok to merge 6290 into 5504 as proposed by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106291 CR Approval 23.502 CR3085 (Rel-17, 'F'): Update the procedure of AF influence on traffic routing Lenovo, Motorola Mobility Rel-17 Merged into S2-2106731 Hui (Huawei) suggests to consider this paper merged into S2-2105505
.
Tingfang Tang (Lenovo) is ok to merge 6291 into 5505 as proposed by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106292 P-CR Approval 23.548: Update the EAS deployment information management via the procedure of AF influence on traffic routing-23.548. Lenovo, Motorola Mobility Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
Tingfang Tang (Lenovo) is ok to merge 6292 into 6031 as proposed by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106293 P-CR Approval 23.548: Update the EAS deployment information management via the procedure similar to that of PFDF management-23.548. Lenovo, Motorola Mobility Rel-17 Merged into S2-2106733 Hui (Huawei) suggests to consider this paper merged into S2-2106031
.
Tingfang Tang (Lenovo) is ok to merge 6293 into 6031 as proposed by Hui.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106294 P-CR Approval 23.548: Update the EAS deployment information management in EASDF-23.548. Lenovo, Motorola Mobility Rel-17 r05 agreed. Revised to S2-2106734, merging S2-2105511, S2-2105512, S2-2105586, S2-2106034 and S2-2106141 Hui (Huawei) suggests to take this paper as baseline for node level info between SMF and EASDF.
Xinpeng (Huawei) provides r01.
Magnus H (Ericsson) provides r02
Xinpeng (Huawei) provides comments.
Magnus H (Ericsson) comments
Xinpeng (Huawei) Response.
Zhuoyun (Tencent) comments.
Tingfang Tang (Lenovo) comments.
Tingfang Tang (Lenovo) further clarifies.
Xinpeng (Huawei) Replies.
Tingfang Tang (Lenovo) further clarifies and provides r03.
Tingfang Tang (Lenovo) further clarifies on r03.
Magnus H (Ericsson) provides r04
Xinpeng(Huawei) replies.
Tingfang Tang (Lenovo) clarifies to Magnus.
Tingfang Tang (Lenovo) further clarifies to Magnus on DNS query handling.
Tingfang Tang (Lenovo) provides r05 based on r03.
==== 8.X, 9.X Revisions Deadline ====
Tingfang Tang (Lenovo) replies to Magnus.
Magnus H (Ericsson) objects to all revisions except r02 and r04
Hui (Huawei) responses.
Tingfang Tang (Lenovo) replies to Magnus and propose to go with r05.
Magnus H (Ericsson) can accept r05 with the following changes.
- Replace 'Node level DNS handling actions Information for each local DN/DNAI' including sub bullets under the sentence with: 'Node level DNS handling actions Information' and sub bullet 'DNS server address'
==== 8.X, 9.X Final Deadline ====
Magnus H (Ericsson) can accept r05 with the following changes.
- Replace 'Node level DNS handling actions Information for each local DN/DNAI' including sub bullets under the sentence with: 'Node level DNS handling actions Information' and sub bullet 'DNS server address'
Magnus H (Ericsson) can accept r05 with the following changes.
- Replace 'Node level DNS handling actions Information for each local DN/DNAI' including sub bullets under the sentence with: 'Node level DNS handling actions Information' and sub bullet 'DNS server address'
Magnus H (Ericsson) can accept r05 with the following changes.
- Replace 'Node level DNS handling actions Information for each local DN/DNAI' including sub bullets under the sentence with: 'Node level DNS handling actions Information' and sub bullet 'DNS server address'
Revised
8.3 S2-2106734 P-CR Approval 23.548: Update the EAS deployment information management in EASDF-23.548. Lenovo, Motorola Mobility, Huawei, HiSilicon, Tencent Rel-17 Revision of S2-2106294r05, merging S2-2105511, S2-2105512, S2-2105586, S2-2106034 and S2-2106141. Approved Approved
8.3 S2-2106495 CR Approval 23.502 CR3115 (Rel-17, 'C'): EAS Deployment Information Management / data aspects Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106731 Hui (Huawei) suggests to consider this paper merged into S2-2105505
.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 - - - Other updates to EASDF solution - - Docs:=15 -
8.3 S2-2105350 P-CR Approval 23.548: Baseline miscellaneous changes to § 6.2.3.2.2 and § 6.4.2. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106735 Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106735 P-CR Approval 23.548: Baseline miscellaneous changes to § 6.2.3.2.2 and § 6.4.2. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105350r01. Approved Approved
8.3 S2-2105351 P-CR Approval 23.548: Matching DNS message handling rules with DNS messages stored at the EASDF (§ 6.2.3.2.2). Nokia, Nokia Shanghai Bell Rel-17 Noted Magnus (Ericsson) provides comments
Magnus H (Ericsson) question
Tingfang Tang (Lenovo) comments.
Laurent (Nokia): answers
Laurent (Nokia): provides r01
Tingfang Tang (Lenovo) still concerns the problem for the solution.
Laurent (Nokia): provides r02
Magnus H (Ericsson) comments
Tingfang Tang (Lenovo) replied to Magnus.
Xinpeng(Huawei) provides r03.
Tingfang Tang (Lenovo) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) objects to r04 and suggests to go for r03
Tingfang Tang (Lenovo) objects r01-r03, can accept r04, can also accept r03 with the update of adding clarification on 'FQDN + message type' could act implicitly as such an identifier' into the new NOTE in clause 6.2.3.2.2.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105513 DISCUSSION Discussion Flow consistency in 6.2.3.2.2 Ericsson Rel-17 Noted Laurent (Nokia): comments to find a way forward between the 2 solutions on the table
Magnus H (Ericsson) comments and answers and proposes way forward
Xinpeng (Huawei) don't see the necessary to define a new service.
Xinpeng(Huawei) replies.
Laurent (Nokia): answers
Tingfang Tang (Lenovo) comments and concerns the problem for Flow consistency in 6.2.3.2.2.
Tingfang Tang (Lenovo) discusses the context ID with Laurent.
Magnus H (Ericsson) suggest we go for Laurent's alt 1
Tingfang Tang (Lenovo) still concerns the problem for Flow consistency in 6.2.3.2.2.
Xinpeng(Huawei) replies and ask for clarification.
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) proposes to note this discussion paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105514 P-CR Approval 23.548: Flow consistency in 6.2.3.2.2 Ericsson Rel-17 Merge into S2-2105351 (Noted). Noted Xinpeng (Huawei) provides comment.
Magnus H (Ericsson) replies
Laurent (Nokia): suggests if Magnus agrees to merge this paper in 5351
Tingfang Tang (Lenovo) not convinced on the problem for Flow consistency in 6.2.3.2.2.
Xinpeng(Huawei) comments.
Magnus H (Ericsson) comments
Xinpeng (Huawei) ask for clarification.
Tingfang Tang (Lenovo) replied to Magnus.
==== 8.X, 9.X Revisions Deadline ====
Xinpeng (Huawei) suggest to merge 5514 into 5351.
Magnus H (Ericsson) agrees with the merge
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105515 P-CR Approval 23.548: Flow consistency in 6.2.3.2.2 Ericsson Rel-17 Noted Xinpeng (Huawei) provides comment.
Magnus H (Ericsson) replies
Xinpeng(Huawei) Reply.
Magnus H (Ericsson) answers
Laurent (Nokia): objects to any revision of 5515
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105665 CR Approval 23.502 CR2949 (Rel-17, 'B'): New service in SMF to support edge computing Ericsson Rel-17 Noted Laurent (Nokia): is not ok with using a new SMF service to solve the message consistency issue
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105617 P-CR Approval 23.548: Avoiding the repetition of DNS message event reporting. Samsung Rel-17 r06 agreed. Revised to S2-2106736, merging S2-2106036 Magnus (Ericsson) provides comments
Jicheol answers the question from Ericsson.
Magnus H (Ericsson)
Laurent (Nokia): provides r01
Xinpeng(Huawei) Provides additional clarification (re-post in thread 5617 ).
Magnus H (Ericsson) provides r02
Xinpeng(Huawei) provides r03.
Laurent (Nokia): Can we check whether 5617 and 6295 are not 2 mechanisms for the same goal?
Xinpeng (Huawei) replies.
Xinpeng (Huawei) provides r04.
Tingfang Tang (Lenovo) provides r05.
Xinpeng(Huawei) provides r06.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106736 P-CR Approval 23.548: Avoiding the repetition of DNS message event reporting. Samsung Rel-17 Revision of S2-2105617r06, merging S2-2106036. Approved Approved
8.3 S2-2106036 P-CR Approval 23.548: DNS Response optimization in EAS discovery procedure. Huawei, HiSilicon Rel-17 Merged into S2-2106736 Magnus H (Ericsson) provides comments
Xinpeng(Huawei) provides r01, and ask for clarification of why EASDF could not have DNAI knowledge.
Magnus H (Ericsson) replies
Xinpeng(Huawei) reply.
Magnus H (Ericsson) comments.
Xinpeng(Huawei) Reply to Magnus.
Xinpeng(Huawei) response to Magnus.
Laurent (Nokia): Suggests that we discuss this topic only via the thread of Tdoc 5617 i.e. we consider 6036 merged in 5617
Xinpeng(Huawei) Provides additional clarification.
Xinpeng(Huawei) reply to Laurent (Nokia)
Xinpeng(Huawei) replies to Magnus(Ericsson).
Laurent (Nokia): objects to 6036 and any of its revisions as we discuss this topic only via the thread of Tdoc 5617 i.e. we consider 6036 merged in 5617
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105508 P-CR Approval 23.548: UE supports receiving DNS settings in PCO Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2106259 CR Approval 23.502 CR3077 (Rel-17, 'B'): Support for EASDF registration and discovery Huawei, Hisilicon Rel-17 Approved Magnus H (Ericsson) ask question
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) responses to Magnus.
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2106261 CR Approval 23.501 CR3186 (Rel-17, 'B'): Use UPF to transfer DNS message between EASDF and DNS server Huawei, Hisilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2106295 P-CR Approval 23.548: Update the description for Session Breakout-23.548. Lenovo, Motorola Mobility Rel-17 r04 agreed. Revised to S2-2106737 Laurent (Nokia): provides r01
Tingfang Tang (Lenovo) replies to Laurent and provides r02.
Hui (Huawei) asks for clarification.
Laurent (Nokia): provides r03
Tingfang Tang (Lenovo) replies to Hui and Laurent and provides r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106737 P-CR Approval 23.548: Update the description for Session Breakout-23.548. Lenovo, Motorola Mobility Rel-17 Revision of S2-2106295r04. Approved Approved
8.3 - - - EAS Discovery Procedure with Local DNS server/resolver - - Docs:=3 -
8.3 S2-2105618 P-CR Approval 23.548: Refreshing the old DNS cache information for Option C. Samsung Rel-17 r05 agreed. Revised to S2-2106738 Fenqin (Huawei) provides command and r01
Dario (Qualcomm) provides r02 (UE behavior dependent on UE implementation)
Fenqin (Huawei) provides r03
Jicheol (Samsung) provides r04.
Shubhranshu (Nokia) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106738 P-CR Approval 23.548: Refreshing the old DNS cache information for Option C. Samsung Rel-17 Revision of S2-2105618r05. Approved Approved
8.3 S2-2106262 P-CR Approval 23.548: Update EAS Discovery Procedure with Local DNS Server/Resolver. Huawei, Hisilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 - - - EAS Re-discovery for session breakout - - Docs:=4 -
8.3 S2-2105996 P-CR Approval 23.548: DNS cache refresh indication is not used in EAS IP replacement situation. vivo Rel-17 r04 agreed. Revised to S2-2106739 Fenqin (Huawei) provides r01
Huazhang (vivo) provides r02
Dario (Qualcomm) provides r03
Fenqini (Huawei) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106739 P-CR Approval 23.548: DNS cache refresh indication is not used in EAS IP replacement situation. Vivo Rel-17 Revision of S2-2105996r04. Approved Approved
8.3 S2-2106486 P-CR Approval 23.548: EAS rediscovery: corrections related to DNS cache handling. Qualcomm Incorporated, Futurewei Rel-17 Revision of (Noted) S2-2104666 from S2-145E. r02 agreed. Revised to S2-2106740 Fenqin (Huawei) ask question for clarification
Dario (Qualcomm) replies to Fenqin and provides r02
Dario (Qualcomm) clarifies that he provided r01, not r02.
Fenqin (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106740 P-CR Approval 23.548: EAS rediscovery: corrections related to DNS cache handling. Qualcomm Incorporated, Futurewei Rel-17 Revision of S2-2106486r02. Approved Approved
8.3 - - - EAS Re-discovery for distributed anchor - - Docs:=1 -
8.3 S2-2105983 P-CR Approval 23.548: EAS Rediscovery over Distributed Anchor Connectivity Model . Sony Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 - - - EAS Discovery with dynamic PSA distribution - - Docs:=3 -
8.3 S2-2105507 P-CR Approval 23.548: Corrections for Distributed Anchor connectivity model Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2106263 P-CR Approval 23.548: Update to EAS Discovery with Dynamic PSA Distribution. Huawei, Hisilicon Rel-17 r01 agreed. Revised to S2-2106741 Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106741 P-CR Approval 23.548: Update to EAS Discovery with Dynamic PSA Distribution. Huawei, HiSilicon Rel-17 Revision of S2-2106263r01. Approved Approved
8.3 - - - Simultaneous connectivity over source and target PSA - - Docs:=6 -
8.3 S2-2105516 P-CR Approval 23.548: AF Guidance for Simultaneous Connectivity at Edge Relocation Ericsson Rel-17 r?? agreed. Revised to S2-2106742 Shubhranshu (Nokia) asks for clarification
Tingfang Tang (Lenovo) concerns on 5516 and related CRs(5517/5518/5519)
Magnus O (Ericsson) responds
Shubhranshu (Nokia) comments to this and related CRs (5517/5518/5519)
Magnus (Ericsson) provide replies
==== 8.X, 9.X Revisions Deadline ====
Tingfang Tang (Lenovo) comments
Magnus O (Ericsson) replies
Tingfang Tang (Lenovo) objects this contribution(there is only r00), and can accept r00 with the update of removing the first item in paragraph 2 of clause 6.3.4, which is for Distributed Anchor with Change of SSC mode 3.
Shubhranshu (Nokia) responds
Magnus O (Ericsson) can accept the suggestion from Tingfang and places a r01 in the drafts folder
Shubhranshu (Nokia) also prefers to note this paper
Magnus O (Ericsson) answers
Tingfang Tang (Lenovo) can live with r01 in the drafts folder (r00 with suggested change).
Magnus O (Ericsson) hopes the chair allows a quick look at 5516r01 at CC#4
Shubhranshu (Nokia) can live with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106742 P-CR Approval 23.548: AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation Ericsson Rel-17 Revision of S2-2105516r?? Approved Approved
8.3 S2-2105517 CR Approval 23.501 CR3026 (Rel-17, 'F'): AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation Ericsson Rel-17 Approved Tingfang Tang (Lenovo) aligns the status with 5516, objects this paper unless 5516r00 with suggested change is agreed.
Magnus O (Ericsson) There's a 5516r01 in the drafts folder that addresses the suggested change.
Tingfang Tang (Lenovo) can accept r00 as a companion paper for 5516r01 in the drafts folder (5516r00 with suggested change).
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2105518 CR Approval 23.502 CR2928 (Rel-17, 'F'): AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation Ericsson Rel-17 Approved Tingfang Tang (Lenovo) aligns the status with 5516, objects this paper unless 5516r00 with suggested change is agreed.
Magnus O (Ericsson) There's a 5516r01 in the drafts folder that addresses the suggested change.
Tingfang Tang (Lenovo) can accept r00 as a companion paper for 5516r01 in the drafts folder (5516r00 with suggested change).
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2105519 CR Approval 23.503 CR0611 (Rel-17, 'F'): AF Request for Simultaneous Connectivity at Edge Relocation Ericsson Rel-17 r01 agreed. Revised to S2-2106743 Hui (Huawei) provides r01.
Magnus (Ericsson) is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
Tingfang Tang (Lenovo) aligns the status with 5516, objects this paper unless 5516r00 with suggested change is agreed. If 5516r00 with suggested change is agreed, 5519r01 is OK without any change.
Magnus O (Ericsson) There's a 5516r01 in the drafts folder that addresses the suggested change.
Tingfang Tang (Lenovo) can accept r01 as a companion paper for 5516r01 in the drafts folder (5516r00 with suggested change).
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106743 CR Approval 23.503 CR0611R1 (Rel-17, 'F'): AF Request for Simultaneous Connectivity at Edge Relocation Ericsson Rel-17 Revision of S2-2105519r01. Approved Agreed
8.3 - - - User Plane latency requirement - - Docs:=3 -
8.3 S2-2105614 CR Approval 23.503 CR0617 (Rel-17, 'F'): Corrections for User Plane Latency Requirement Samsung Rel-17 r06 agreed. Revised to S2-2106744 Shubhranshu (Nokia) provides r01
Hui(Huawei) provides r02
Jicheol (Samsung) provides r03.
Shubhranshu (Nokia) comments
Magnus H (Ericsson) provides r04
Shubhranshu (Nokia) comments and provides r05
Jicheol (Samsung) provides r06.
==== 8.X, 9.X Revisions Deadline ====
Shubhranshu (Nokia) is OK with r06
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106744 CR Approval 23.503 CR0617R1 (Rel-17, 'F'): Corrections for User Plane Latency Requirement Samsung Rel-17 Revision of S2-2105614r06. Approved Agreed
8.3 S2-2105615 P-CR Approval 23.548: Abstract procedure of AF requested User Plane Latency Requirement. Samsung Rel-17 Noted Shubhranshu (Nokia) provides comments
Jicheol (Samsung) provides r01 based on Nokia comments.
Shubhranshu (Nokia) asks for further clarification
Magnus H (Ericsson) provides r03. R02 should be disregarded.
Shubhranshu (Nokia) comments
Jicheol (Samsung) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) comments
Shubhranshu (Nokia) proposes to note this paper, not OK with r04 and previous revisions
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - ECS address provision - - Docs:=17 -
8.3 S2-2105738 CR Approval 23.502 CR2968 (Rel-17, 'F'): ECS Address Configuration in UDM ZTE Rel-17 CC#4: r02 + changes agreed. Revised, merging S2-2105948, to S2-2106672. Tingfang Tang (Lenovo) suggests to take 5738 as basis to address EN with DNN and S-NSSAI.
Hui (Huawei) supports to take 5738 as basis to address EN with DNN and S-NSSAI.
Jinguo (ZTE) asks the need for application data (AF provided ECS Address Configuration Information)
Hyesung (Samsung) agrees to take 5738 as basis.
Magnus (Ericsson) provides S2-2105738r02.
Dario (Qualcomm) is not OK with r01 and r02.
Jinguo(ZTE) responds to Dario (Qualcomm) and proposed r03.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) objects to r00-03
Jinguo(ZTE) provides r04 to simply remove the first change. ask for CC#4 to discuss
Hui(Huawei) provide comments to r04
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106672 CR Approval 23.502 CR2968R1 (Rel-17, 'F'): ECS Address Configuration in UDM ZTE Rel-17 Revision of S2-2105738r02 + changes, merging S2-2105948. Approved Agreed
8.3 S2-2105948 CR Approval 23.502 CR3016 (Rel-17, 'C'): Update IEs in AF provided ECS Address Configuration Information Samsung Rel-17 Merged into S2-2106672 Tingfang Tang (Lenovo) suggests to merge 5948 into 5738 to address EN with DNN and S-NSSAI.
Hyesung (Samsung) agrees to merge 5948 into 5738.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2105950 P-CR Approval 23.548: ECS address configuration for any UE. Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2105988 CR Approval 23.501 CR3124 (Rel-17, 'F'): Update of ECS address in External Exposure of Network Capability vivo Rel-17 r02 agreed. Revised to S2-2106745 Tingfang Tang (Lenovo) comments.
Huazhang (vivo) replys to Tingfang(Lenove) and provides r01
Huazhang (vivo) is ok with r02, and list the r02 again
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) thanks Huazhang and supports r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106745 CR Approval 23.501 CR3124R1 (Rel-17, 'F'): Update of ECS address in External Exposure of Network Capability Vivo Rel-17 Revision of S2-2105988r02. Approved Agreed
8.3 S2-2105991 CR Approval 23.502 CR3025 (Rel-17, 'F'): Update the procedure and details in ECS Configuration Information provision vivo Rel-17 r02 agreed. Revised to S2-2106746 Huazhang (vivo) trigger technique discussion of ECS address
Jinguo(ZTE) comments
Huazhang(vivo) reply to Jinguo
Tingfang Tang (Lenovo) comments.
Huazhang (vivo) provides r01
Dario (Qualcomm) provides r02
Magnus (Ericsson) comments
Jinguo (ZTE) comments on r02
Huazhang (vivo) replys to Jingguo(ZTE) and Dario, Magnus
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106746 CR Approval 23.502 CR3025R1 (Rel-17, 'F'): Update the procedure and details in ECS Configuration Information provision Vivo Rel-17 Revision of S2-2105991r02. Approved Agreed
8.3 S2-2105995 P-CR Approval 23.548: Resolves the remaining ENs in ECS address delivering. vivo Rel-17 r04 agreed. Revised to S2-2106747 Dario S. Tonesi (Qualcomm) is not OK with this proposal
Magnus O (Ericsson) is not OK with this proposal either
Tingfang Tang (Lenovo) comments.
Huazhang (vivo) replys to Magnus and Dario, and seek for the technique reason
Huazhang (vivo) provides r01 and response
Hui (Huawei) comments
Huazhang (vivo) reply to Hui
Magnus O (Ericsson) is not OK with r01 either
Huazhang (vivo) provides r03 and reply to Tingfang
Shubhranshu (Nokia) comments
Huazhang (vivo) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106747 P-CR Approval 23.548: Resolves the remaining ENs in ECS address delivering. Vivo Rel-17 Revision of S2-2105995r04. Approved Approved
8.3 S2-2106481 DISCUSSION Discussion Correction of ECS Address Configuration Information . Qualcomm Incorporated Rel-17 Noted Tingfang Tang (Lenovo) discusses on EN for Spatial Validity Condition.
Huazhang (vivo) comments
Jinguo(ZTE) comments
Mike (Convida Wireless) comments
Dario (Qualcomm) replies to Convida, Lenovo and Vivo and proposes to go with Option 2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106482 CR Approval 23.502 CR3112 (Rel-17, 'F'): Correction of ECS Address Configuration Information - Option 1 Qualcomm Incorporated Rel-17 Noted Tingfang Tang (Lenovo) comments.
Dario (Qualcomm) provides r01
Hui(Huawei) provides r02
Hui(Huawei) provides further comments
Shubhranshu (Nokia) comments
Huazhang (vivo) comments
Tingfang Tang (Lenovo) prefers updating option 2 and suggests to node this paper.
Dario (Qualcomm) is OK with focusing on option 2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106483 CR Approval 23.502 CR3113 (Rel-17, 'F'): Correction of ECS Address Configuration Information - Option 2 Qualcomm Incorporated Rel-17 r01 agreed. Revised to S2-2106748 Hui (Huawei) provides r01.
Tingfang Tang (Lenovo) comments and provides r02.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) asks update reason for change on r02.
Hui (Huawei) objects r02, support r01.
Dario (Qualcomm) is OK with Jinguo's suggestion and asks to consider r03 which was mistakenly sent only to TingFang.
Dario (Qualcomm) is also OK with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106748 CR Approval 23.502 CR3113R1 (Rel-17, 'F'): Correction of ECS Address Configuration Information - Option 2 Qualcomm Incorporated Rel-17 Revision of S2-2106483r01. Approved Agreed
8.3 S2-2106484 P-CR Approval 23.548: Correction of ECS Address Configuration Information - Option 1. Qualcomm Incorporated Rel-17 Noted Huazhang (vivo) comments
Hui(Huawei) provides comments
Tingfang Tang (Lenovo) prefers updating option 2 and suggests to node this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106485 P-CR Approval 23.548: Correction of ECS Address Configuration Information - Option 2. Qualcomm Incorporated Rel-17 r04 agreed. CC#4: r01 + changes agreed. Revised to S2-2106749 Huazhang (vivo) comments
Hui (Huawei) provides r01.
Tingfang Tang (Lenovo) comments and provides r02.
Dario (Qualcomm) provides r03 and replies to Huazhang.
Huazhang (vivo) provides r04 based on r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106749 P-CR Approval 23.548: Correction of ECS Address Configuration Information - Option 2. Qualcomm Incorporated Rel-17 Revision of S2-2106485r01 + changes. Approved Approved
8.3 - - - AF triggered EAS relocation - - Docs:=2 -
8.3 S2-2105739 P-CR Approval 23.548: KI#2 AF triggered EAS relocation. ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 r05 agreed. Revised to S2-2106750 Fenqin (Huawei) ask a question for clarification
Magnus (Ericsson) provides S2-2105739r01
Tingfang Tang (Lenovo) replies to Fenqin.
Jinguo (ZTE) provides r02
Shubhranshu (Nokia) comments to r01
Shubhranshu (Nokia) responds
Shubhranshu (Nokia) provides r03
Jinguo(ZTE) is fine with r03
Magnus (Ericsson) provides r04.
Fenqin (Huawei) provides r05, r06.
Fenqin (Huawei) comments
==== 8.X, 9.X Revisions Deadline ====
Jinguo (ZTE) suggest to go with r05 based on simultaneous connectivity discussion.
Magnus (Ericsson) also suggest to go with r05 and object to r06
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106750 P-CR Approval 23.548: KI#2 AF triggered EAS relocation. ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility Rel-17 Revision of S2-2105739r05. Approved Approved
8.3 - - - Network info exposure via Local NEF - - Docs:=11 -
8.3 S2-2105397 CR Approval 23.502 CR2899 (Rel-17, 'C'): Procedure updates to support local NEF selection Nokia, Nokia Shanghai Bell Rel-17 Noted Haiyang(Huawei) comments and seeks for clarification
Magnus (Ericsson) comments
Laurent (Nokia): answers
Magnus (Ericsson): comments
Haiyang(Huawei) responds
==== 8.X, 9.X Revisions Deadline ====
Magnus (Ericsson) objects to r00
Haiyang(Huawei) also objects r00, suggest to note/postpone this paper
Laurent (Nokia): Comments
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105398 P-CR Approval 23.548: Procedure for local NEF selection. Nokia, Nokia Shanghai Bell Rel-17 Noted Laurent (Nokia): provides r01
Haiyang(Huawei): provides comments and seeks for clarification
Magnus (Ericsson) comments
Laurent (Nokia): provides r02
==== 8.X, 9.X Revisions Deadline ====
Haiyang(Huawei) suggests to note this paper as well (objects r00, r01 and r02)
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105399 P-CR Approval 23.548: N4 updates to support local NEF/AF Subscriptions to QoS monitoring events . Nokia, Nokia Shanghai Bell Rel-17 Noted Haiyang (Huawei) seeks for clarification.
Laurent (Nokia): answers
Magnus (Ericsson) asks why the API version is needed.
Haiyang (Huawei) comments.
Laurent (Nokia): Comments
==== 8.X, 9.X Revisions Deadline ====
Magnus (Ericsson) is inclined to object to this document.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105989 CR Approval 23.502 CR3023 (Rel-17, 'F'): Procedure of discovery of local NEF from NRF vivo Rel-17 Noted Haiyang (Huawei) provides r01.
Huazhang (vivo) is ok with r01.
Laurent (Nokia): Comments
Huazhang (vivo): replys
==== 8.X, 9.X Revisions Deadline ====
Huazhang (vivo): replys to Laurent(Nokia)
Laurent (Nokia): objects to any revision of this paper as the procedure is not complete, noting that the revision R02 of 5398 has a complete description
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2105990 CR Approval 23.502 CR3024 (Rel-17, 'F'): Registration of local NEF to NRF vivo Rel-17 r01 agreed. Revised to S2-2106751 Haiyang (Huawei) provides r01.
huazhang (vivo) is ok for r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106751 CR Approval 23.502 CR3024R1 (Rel-17, 'F'): Registration of local NEF to NRF Vivo Rel-17 Revision of S2-2105990r01. Approved Agreed
8.3 S2-2106152 P-CR Approval 23.548: Correction on NEF related services. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106752 Laurent (Nokia): suggest to merge with 5398
Haiyang (Huawei): suggest to handle it independently (at least for now)
Magnus O (Ericsson): comments
Haiyang (Huawei):provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106752 P-CR Approval 23.548: Correction on NEF related services. Huawei, HiSilicon Rel-17 Revision of S2-2106152r01. Approved Approved
8.3 S2-2106153 CR Approval 23.502 CR3043 (Rel-17, 'F'): Correction on NEF related services Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2106368 P-CR Approval 23.548: Support AF subscribes QoS monitoring information exposed from UPF through local NEF after the initial Event Notification. China Mobile Rel-17 Noted Dan (China Mobile) provides r01
Laurent (Nokia): Comments
Dan(China Mobile) reply to Laurent and would like ask whether r00 is ok or not.
Magnus (Ericsson) comments
Dan (China Mobile) provide r03, please ignore r02
Laurent (Nokia): answers
==== 8.X, 9.X Revisions Deadline ====
Haiyang (Huawei) share similar view as Magnus (Ericsson) and comment
Laurent (Nokia): objects to any version of this document
Magnus (Ericsson): objects to any version of this document
Dan (China Mobile) agree that this paper is NOTED
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106392 CR Approval 23.502 CR3097 (Rel-17, 'B'): UPF event exposure service update China Mobile Rel-17 Noted Dan (China Mobile) provides r01
Laurent (Nokia): comments
Magnus (Ericsson): comments
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version of this document
Kisuk (Samsung): supports this CR
Magnus (Ericsson): objects to any version of this document
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - AF guidance to URSP rules & service specific authorization - - Docs:=13 -
8.3 S2-2105509 P-CR Approval 23.548: EAS (re)Discovery with Multiple PDU Sessions Ericsson Rel-17 r02 agreed. Revised to S2-2106753 Hui (Huawei) provides r01.
Magnus (Ericsson) provides r02.
Hui (Huawei) fine with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106753 P-CR Approval 23.548: EAS (re)Discovery with Multiple PDU Sessions Ericsson Rel-17 Revision of S2-2105509r02. Approved Approved
8.3 S2-2105520 CR Approval 23.502 CR2929 (Rel-17, 'F'): Service Specific Authorization for Group of UEs Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2105612 CR Approval 23.503 CR0616 (Rel-17, 'B'): Enhancement of UE policy delivery notification Samsung Rel-17 CC#4: Postponed Hui (Huawei) provides comment.
Shubhranshu (Nokia) comments
Jicheol (Samsung) comments.
Shubhranshu (Nokia) asks for further clarification
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) proposes to note this paper.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2105613 CR Approval 23.502 CR2946 (Rel-17, 'B'): Enhancement of UE Policies delivery notification Samsung Rel-17 CC#4: Postponed Shubhranshu (Nokia) proposes to note this paper
==== 8.X, 9.X Final Deadline ====
Hui (Huawei) asks to discuss this paper in CC#4.
Jicheol (Samsung) comments.
Shubhranshu (Nokia) responds
Postponed
8.3 S2-2106138 CR Approval 23.503 CR0638 (Rel-17, 'F'): Update with AF guidance Tencent Rel-17 r01 agreed. Revised to S2-2106754 Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106754 CR Approval 23.503 CR0638R1 (Rel-17, 'F'): Update with AF guidance Tencent Rel-17 Revision of S2-2106138r01. Approved Agreed
8.3 S2-2106264 CR Approval 23.502 CR3078 (Rel-17, 'F'): Update of Nudm_ServiceSpecificAuthorisation service operations Huawei, Hisilicon Rel-17 CC#4: r00 + changes as in r01 agreed. Revised to S2-2106675. Dario S. Tonesi (Qualcomm) asks question on third change.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) cannot accept r00 because of issues w/ 3rd change.
Hui (Huawei) responses to Dario and asks to reconsider the objection.
==== 8.X, 9.X Final Deadline ====
Hui (Huawei) proposes r01 and ask for confirmation in CC#4.
Revised
8.3 S2-2106675 CR Approval 23.502 CR3078R1 (Rel-17, 'F'): Update of Nudm_ServiceSpecificAuthorisation service operations Huawei, HiSilicon Rel-17 Revision of S2-2106264r00 + changes as in r01. Approved Agreed
8.3 S2-2106265 CR Approval 23.501 CR3187 (Rel-17, 'F'): Add Nudm_ServiceSpecificAuthorisation service Huawei, Hisilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2106287 P-CR Approval 23.548: Support of AF Guidance to PCF Determination of Proper URSP Rules with taking subscription information into account. China Mobile Rel-17 r04 agreed. Revised to S2-2106755 Hui (Huawei) provides r01.
Magnus O (Ericsson) is not ok with this pCR.
Dan (China Mobile) reply to Magnus
Dan (China Mobile) provides r02
Magnus (Ericsson) comments
Dan (China Mobile)provide r03
Magnus (Ericsson) is ok with r03.
Shubhranshu (Nokia) provides r04
==== 8.X, 9.X Revisions Deadline ====
Dan (China Mobile) is OK for r03 or r04
Shubhranshu (Nokia) prefers r04
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106755 P-CR Approval 23.548: Support of AF Guidance to PCF Determination of Proper URSP Rules with taking subscription information into account. China Mobile Rel-17 Revision of S2-2106287r04. Approved Approved
8.3 S2-2106493 CR Approval 23.502 CR3114 (Rel-17, 'B'): Support of AF Guidance to PCF Determination of Proper URSP Rules with taking subscription information into account China Mobile Rel-17 Noted Magnus O (Ericsson) is not ok with this CR
Dan(China Mobile) reply to Magnus because the reason is not correct
==== 8.X, 9.X Revisions Deadline ====
Dan(China Mobile) would like to ask Magnus to reply Dan's previous response.
Magnus O (Ericsson) object to this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - AF change - - Docs:=8 -
8.3 S2-2106132 CR Approval 23.502 CR3040 (Rel-17, 'B'): Updates on transferring AF request to PCF CATT Rel-17 r02 agreed. Revised to S2-2106756 Fenqin (Huawei) comments.
Shubhranshu (Nokia) asks for clarification
Yuan Tao (CATT) replies and provides r01.
Shubhranshu (Nokia) responds
Yuan Tao (CATT) replies to Shubhranshu and provides r02.
Magnus (Ericsson) don't see the need for this CR
Yuan Tao (CATT) replies to Magnus (Ericsson).
Magnus O (Ericsson) is ok with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106756 CR Approval 23.502 CR3040R1 (Rel-17, 'B'): Updates on transferring AF request to PCF CATT Rel-17 Revision of S2-2106132r02. Approved Agreed
8.3 S2-2106133 CR Approval 23.501 CR3148 (Rel-17, 'B'): Updates to AF requests to influence traffic routing CATT Rel-17 Noted Fenqin (Huawei) comments.
Shubhranshu (Nokia) comments
Tingfang Tang (Lenovo) comments.
Yuan Tao (CATT)replies to Tingfang Tang (Lenovo).
Magnus O (Ericsson) I don't see the need for this CR.
Fenqin (Huawei ) propose to note this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2106134 CR Approval 23.501 CR3149 (Rel-17, 'F'): Updates on edge computing CATT Rel-17 r01 agreed. Revised to S2-2106757 Shubhranshu (Nokia) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106757 CR Approval 23.501 CR3149R1 (Rel-17, 'F'): Updates on edge computing CATT Rel-17 Revision of S2-2106134r01. Approved Agreed
8.3 S2-2106135 P-CR Approval 23.548: Updates on edge relocation involving AF change. CATT Rel-17 Merged into S2-2106758 Hyesung (Samsung) comments and asks questions.
Fenqin (Huawei) comments.
Shubhranshu (Nokia) responds and is OK to merge into S2-2106504
Yuan Tao (CATT) replies and agrees to merge this paper into S2-2106504.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2106504 P-CR Approval 23.548: Updates to Edge Relocation Involving AF change. Nokia, Nokia Shanghai Bell, NTT Docomo Rel-17 r01 agreed. Revised to S2-2106758, merging S2-2106135 Hyesung (Samsung) comments.
Shubhranshu (Nokia) responds
Yuan (CATT) is ok to merge S2-2106135 into this paper and provides r01.
Shubhranshu (Nokia) is OK to merge
Fenqin (Huawei) ask question for clarification
Hyesung (Samsung) provides comments and r02.
Yuan Tao (CATT) asks Hyesung (Samsung) for clarification.
Yuan Tao (CATT) prefers r01.
==== 8.X, 9.X Revisions Deadline ====
Shubhranshu (Nokia) also prefers r01
Hyesung (Samsung) prefers r02 and is also fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106758 P-CR Approval 23.548: Updates to Edge Relocation Involving AF change Nokia, Nokia Shanghai Bell, NTT Docomo, CATT Rel-17 Revision of S2-2106504r01, merging S2-2106135. Approved Approved
8.3 - - - DNAI based SMF/I-SMF selection - - Docs:=2 -
8.3 S2-2106266 CR Approval 23.502 CR3079 (Rel-17, 'B'): Support of I-SMF removal Huawei, Hisilicon Rel-17 r05 agreed. Revised to S2-2106759 Shubhranshu (Nokia) provides comment
Hui(Huawei) replies to Shubhranshu.
Shubhranshu (Nokia) responds
Hui (Huawei) response.
Jinguo(ZTE) comment.
Yuan (CATT) comment.
Hyunsook (LGE) provides a comment.
Hui (Huawei) responses.
Hui (Huawei) provides r01.
Jinguo (ZTE) provides r02 and add ZTEas cosigner
Shubhranshu (Nokia) comments
Yuan Tao (CATT) comments.
Jinguo(ZTE) responds
Shubhranshu (Nokia) provides r03
Jinguo (ZTE) responds
Yuan Tao (CATT) replies.
Shubhranshu (Nokia) responds and provides r04
Hui (Huawei) provides r05
Hui (Huawei) provides comments.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) provides comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2106759 CR Approval 23.502 CR3079R1 (Rel-17, 'B'): Support of I-SMF removal Huawei, HiSilicon, ZTE, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106266r05. Approved Agreed
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=132 -
8.4 - - - General - - Docs:=16 -
8.4 S2-2105254 LS In Action LS from CT WG3: LS on Clarifications to the operation of network slice status reporting CT WG3 (C3-213457) Rel-17 Response drafted in S2-2105714. Final response in S2-2106836
==== 8.X, 9.X Final Deadline ====
Replied to
8.4 S2-2105715 CR Approval 23.502 CR2963 (Rel-17, 'F'): Clarification to the operation of network slice status reporting Huawei, HiSilicon Rel-17 r08 agreed. Revised to S2-2106835 George Foti (Ericsson) provides comments
Haiyang (Huawei) responds to George Foti (Ericsson)
Gerald (Matrixx) with further comments on the concern from Ericsson.
Haiyang (Huawei) responds to Gerald (Matrixx)
George Foti (Ericsson) provides response.
Iskren (Huawei) comments subscriptions should be separate.
Iskren (NEC) comments the CR is not acceptable with the current changes.
George (Ericsson) provide comments. Basically yes, my proposal is to remove ' or both' and then nothing else is needed.
George (Ericsson) provide an additional comment. For the reporting, the proposal is that it is reported once when it is exceeds the threshold, and once when it below the threshold. If we need to optimize that we can do that in Release 18.
Gerald (Matrixx) with reply and consolidation.
George (Ericsson) provides comment. That is also what I propose for Release 17. Anything beyond clarifying the behavior for a single threshold has to be postponed
Haiyang (Huawei) provides r01
Srisakul (NTT DOCOMO) provides comment. No need to go into details of two types of threshold.
George (Ericsson) provides comment. We also agree with a single threshold. Notification is sent only once when the threshold is crossed or gone below. Also replace the word may concern, with covers.
Iskren (NEC) comments.
Iskren (NEC) does not agree with upper and lower thresholds. The CR is not acceptable.
Iskren (NEC) does not agree with upper and lower thresholds. R01 is not acceptable.
Haiyang (Huawei) seeks for clarification from Iskren(NEC) and George(Ericssion)
Iskren (NEC) answers question
George (Ericsson) provides an answer.
Haiyang (Huawei) provides r02
George (Ericsson) provides r03. Reworded the text for clarity
Kaisu (Nokia) comments that there is something wrong with the sentence editing in rev03.
George (Ericsson) provides rev 04. It should be every time.
Gerald (Matrixx) provides rev 05 which refers to the LS discussion on S2-2105714
George (Ericsson) asks a question. Does attaining incorporate exceeding ?
Gerald (Matrixx) answers to Georges
George (Ericsson) asks another question.
Srisakul (NTT DOCOMO) provides r06.
Gerald (Matrixx) with answer to George
Iskren (NEC) provides r07
George (Ericsson) provides r08. Sorry Srisakul, but adding the when is linguistically incorrect. I just removed it.
==== 8.X, 9.X Revisions Deadline ====
Haiyang (Huawei) is OK with r08
Srisakul (NTT DOCOMO) is OK with r08.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106835 CR Approval 23.502 CR2963R1 (Rel-17, 'F'): Clarification to the operation of network slice status reporting Huawei, HiSilicon, Ericsson, NEC Rel-17 Revision of S2-2105715r08. Approved Agreed
8.4 S2-2105714 LS OUT Approval [DRAFT] LS Reply on Clarifications to the operation of network slice status reporting Huawei, HiSilicon Rel-17 Response to S2-2105254. r08 agreed. Revised to S2-2106836 Gerald (Matrixx) with similar concern on threshold as under the CR discussion with S2-2105715.
Haiyang(Huawei) provides r01.
Gerald (Matrixx) object r01 with fundamental concern
George (Ericsson) proposes to first agree on a CR, and just attach it.
Haiyang(Huawei) comments to Gerald (Matrixx)
Gerald (Matrixx) with reply
Haiyang(Huawei) responds to Gerald (Matrixx)
Gerald (Matrixx) with clarification and resolution
Haiyang(Huawei) provides r02 based on the wording from Gerald (Matrixx)
Gerald (Matrixx) with suggestion for another needed revision to align the answers for Q3.
Haiyang(Huawei) seeks clarification from Gerald (Matrixx)
Gerald (Matrixx) with indicated text for improvement on Q3.
Gerald (Matrixx) does not agree on changing thresholds and is proposing a new wording.
George (Ericsson) comments. We update the spec to address all the issues. I think we should just include the approved CR and no need to address each question separately. The questions are mute given the CR content.
Gerald (Matrixx) provides r03 to be consistent with the achievements of the corresponding CR S2-2105715r07.
Haiyang(Huawei) provides r04
Gerald (Matrixx) suggest to move on with r03 and object to r04.
Haiyang(Huawei) comments on r03 and provides r05.
Iskren (NEC) - the LS is not acceptable as it diverges from the related CR and from the questions.
Iskren (NEC) agrees with George to attach the agreed CR without answering the questions as currently there is a big discrepancy between the two.
Haiyang(Huawei) provides r06.
Iskren (NEC) comments.
Haiyang(Huawei) provides Reply.
Iskren (NEC) maybe we only attached the CR as it answers all their meaningful questions.
George (Ericsson) will agree to just attaching the CR.
Haiyang(Huawei) provides r07.
George (Ericsson) comments. Question 2 is already fully addressed in the CR. No reason for the response.
Haiyang(Huawei) asks what is wrong in A2?
George (Ericsson) repeating the CR again. Just reference the CR.
Haiyang(Huawei) provides r08 as an Alt.
==== 8.X, 9.X Revisions Deadline ====
Tao(VC) can we go with r08 then?
Jinguo(ZTE) suggest to go with r08.
Haiyang(Huawei)is OK to go with r08.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106836 LS OUT Approval LS Reply on Clarifications to the operation of network slice status reporting SA WG2 Rel-17 Revision of S2-2105714r08. Approved Approved
8.4 S2-2105257 LS In Action LS from CT WG4: LS on NSAC service and service operation CT WG4 (C4-213048) Rel-17 Response drafted in S2-2106127. Final response in S2-2106838
==== 8.X, 9.X Final Deadline ====
Replied to
8.4 S2-2105743 CR Approval 23.501 CR3071 (Rel-17, 'F'): KI#1KI#2 - NSACF Service operation name update ZTE Rel-17 Merged into S2-2106848 George Foti (Ericsson) proposes to note this CR as this is already covered in 5713.
Jinguo(ZTE) suggest to merge the service part of 5713 into 5743
Jinhua(Xiaomi) update description of Nnsacf_ SliceEventExposure, r01 is provided
George Foti (Ericsson) makes a comment. 5743 is incomplete. Please use 5713 r1 as a base.
Jinhua (Xiaomi) propose to merge 5743 into 5713(with the agreement achieved).
George (Ericsson) provides a response.
Jinguo(ZTE) confirms the merge with 5713.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105744 CR Approval 23.502 CR2970 (Rel-17, 'F'): KI#1KI#2 - NSACF Service operation name update ZTE Rel-17 r03 agreed. Revised to S2-2106837 Iskren (NEC)provides r01
George (Ericsson). We don't this CR. Per slice is not appropriate., and as such we should note the CR
Jinguo(ZTE) asks question to George (Ericsson) and prefers orignal version
George (Ericsson) responds. U misunderstood what I said. I am OK with the original version not with the r01.
Jinhua(Xiaomi) provide r02 based on the original version, with update NumOfUEsUpdate consumer with AMF and SMF+PGW-C.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) is OK with r02..
Jinguo(ZTE) propose to remove the overlapping with 6006. ask for CC#4.
Jinguo(ZTE) add the link of r03. ask for CC#4.
Srisakul (NTT DOCOMO) comments on r03.
Jinguo(ZTE) replies to Srisakul (NTT DOCOMO)
Srisakul (NTT DOCOMO) ok with r03.
Jinhua(Xiaomi)response to Jinguo, then it's better to propose the original version(same as r03) for approval.
Jinguo(ZTE) suggests to go with r03. r00 has SMF there.
Jinhua(Xiaomi) replies to Jinguo, agree with you that r03 is needed to avoid the overlap.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106837 CR Approval 23.502 CR2970R1 (Rel-17, 'F'): KI#1KI#2 - NSACF Service operation name update ZTE Rel-17 Revision of S2-2105744r03. CC#4: Approved. Agreed
8.4 S2-2106127 LS OUT Approval [DRAFT] Reply LS on NSAC service and service operation ZTE Rel-17 Response to S2-2105257. r01 agreed. Revised to S2-2106838 Gerald (Matrixx) with recommendation.
Jinguo (ZTE) will update the LS based on 5713.
Jinguo (ZTE) provide r01 to update the CR number
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106838 LS OUT Approval Reply LS on NSAC service and service operation SA WG2 Rel-17 Revision of S2-2106127r01. Approved Approved
8.4 S2-2105856 CR Approval 23.502 CR2999 (Rel-17, 'F'): Undo wrongly implemented changes Lenovo, Motorola Mobility, ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105453 DISCUSSION Decision KI#8 solution for TR 23.700-40 ('Study on enhancement of network slicing; Phase 2'). MITRE Noted Stefano (Qualcomm) provides comments and questions for clarifications.
Jinguo(ZTE) object to this paper. It is not in the exception list.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105369 LS In Information LS from GSMA NG: New Whitepaper: 'E2E Network Slicing Architecture' GSMA NG (E2E-NS WP Publish LS) Noted Jinguo(ZTE) suggest to note this new LS
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105371 LS In Action LS from RAN WG2: Reply LS on Cell reselection with band-specific network slices RAN WG2 (R2-2108868) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2105377 LS In Action LS from RAN WG3: Response to LS on Cell reselection with band-specific network slices RAN WG3 (R3-214472) Rel-17 Received 27/08/2021. Noted Noted
8.4 - - - NSAC(EAC) - - Docs:=8 -
8.4 S2-2105341 CR Approval 23.502 CR2892 (Rel-17, 'B'): Support NSAC register to NRF III Rel-17 Noted George Foti (Ericsson) objects to this CR and provides comments
NEC (Iskren) suggest this CR is noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105426 CR Approval 23.501 CR3014 (Rel-17, 'B'): KI#1 : NRF Support for EAC Flag Ericsson Rel-17 Noted Ashok (Samsung) propose to note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105429 CR Approval 23.502 CR2907 (Rel-17, 'B'): KI#1: NRF Support for EAC Flag Ericsson Rel-17 Noted Jinguo(ZTE) provides comments and propose to note it
Fenqin (Huawei) agree to note this paper.
George Foti (Ericsson) provides comments. The implicit solution does not work, and is incomplete.
Ashok (Samsung) propose to note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106510 CR Approval 23.502 CR2876R1 (Rel-17, 'B'): AMF - NSACF discovery via NRF Apple Rel-17 Revision of (Noted) S2-2104776 from S2-145E. Noted George Foti (Ericsson) objects to this CR. Please see comments on 5341.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106388 CR Approval 23.502 CR3094 (Rel-17, 'F'): KI#1KI#2 - Resolve EN for NSAC procedure ZTE Rel-17 r11 agreed. Revised to S2-2106839 George Foti (Ericsson) proposes to note the CR. Additional comments below.
George Foti (Ericsson) provides comment. We don't need the second change, so please provide an update with the first change only.
Jinguo(ZTE) response to George (Ericsson)
Fenqin (Huawei) comment
George Foti (Ericsson) provides a response.
Iskren (NEC)proposes to note this CR as it does not work.
Jinguo(ZTE) provides r01
Kaisu(Nokia) prefers the subscription of the EAC flag to be handled on the AMF <=> NSACF interface.
George Foti (Ericsson) provides a comment. There is still a key question is how the NSCAF discovers the AMFs.
U addressed a subset ignoring the other part. That is why this is an incomplete solution. Implicit subscription may not work if we resolve the discovery in a way that renders this unusable.
Fenqin (Huawei) provides a comment.
Jinguo(ZTE) provides r02
Iskren (NEC) asks question
Jinguo (ZTE) replies.
Iskren (NEC) is OK with this revision.
George Foti (Ericsson) still object to the CR and provides a comment. This does not make sense. Please see more
Jinguo (ZTE) explains to George(Ericsson)
Jinguo (ZTE) provides a response.
George Foti (Ericsson) asks a question. How does NSACF knows that this flag is intended only for AMF2.
Jinguo(ZTE) provides r03
George (Ericsson) provides r05. Added Ericsson Co-signer, minor editorial. We can lay this EAC to rest now.
Ashok (Samsung) is ok with r05
George (Ericsson) provides comment. Not sure I follow. The EAC is check for UE initiated registration. If a slice is removed, the AMF knows what did depending on the EAC flag and can act accordingly. In some cases, it does not even need to interact at all with NSACF.
Ashok (Samsung) responds to George
George (Ericsson) provides a response. I agree the check is not needed. The AMF will have to do what it has to do. We can remove this check completely.
Fenqin(Huawei) provides a comment.
Ashok (Samsung) comments
Jinguo(ZTE) provides r06
Heng (China Telecom) provide comments on unsubscribe
Jinhua(Xiaomi) provides r07, with update of triggered cases in 4.2.11.2
Jinhua(Xiaomi) reply to George (Ericsson), For bullet one and two, the EAC mode is both active, but apply it only increase. It's the point
Jinguo(ZTE) suggest to go with r06
George (Ericsson) asks a question. I had another question on my note. Please respond to it
Yunjing (CATT) asks a question for clarification.
Jinguo(ZTE) responds
George (Ericsson) The AMF can assume the EAC active or inactive. We don't need to ay anything. Stage 3 can add a default behaviour
Yunjing (CATT) is ok for the implementation option.
George (Ericsson) provides r0. Added the word reatime to the note Also incorporates the first change from 5777 in here. This is a valid change
Jinguo (ZTE) provides r09
Genadi (Lenovo) provides r10.
George (Ericsson) OK with r10
Ashok (Samsung) provides comments
George (Ericsson) responds. Callback URI is only a stage 3 term.
Jinguo(ZTE) is fine with r10
Jinguo(ZTE) provides r11, clean up the change over change and add Samsung as cosigner.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) is OK with r11
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106839 CR Approval 23.502 CR3094R1 (Rel-17, 'F'): KI#1KI#2 - Resolve EN for NSAC procedure ZTE, Ericsson, Samsung Rel-17 Revision of S2-2106388r11. Approved Agreed
8.4 S2-2105777 CR Approval 23.502 CR2977 (Rel-17, 'F'): TS23.502 Correction to the NSAC related to the EAC mode NEC Rel-17 r03 agreed. Revised to S2-2106840 George Foti (Ericsson) proposes to note this. The first change is already in 6388r08
Iskren (NEC) suggests to keep this CR open for now. If we find it covered in 6388, then we can mark it as a merged.
Jinguo(ZTE) provides r01
Iskren (NEC) is OK with r01.
George (Ericsson) comment. Why do we need to rewrite the text but not reference the applicable section. I am not OK with r01
Iskren (NEC) removed duplicated text. Provides r02.
George (Ericsson) comments; U should have left the output optional as is. This is part of the template everywhere for consistency. Can U please add it.
Iskren (NEC) provides r03 with restored output optional parameter.
George (Ericsson) OK with r03.
Jinguo(ZTE) comments that r03 of this CR becomes editorial update. The coverpage needs to be changed..
Iskren (NEC) answers Jinguo(ZTE) - why, we are deleting a whole section.
Jinguo(ZTE) answers
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) asks to update the coversheet in r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106840 CR Approval 23.502 CR2977R1 (Rel-17, 'F'): TS23.502 Correction to the NSAC related to the EAC mode NEC Rel-17 Revision of S2-2105777r03. Approved Agreed
8.4 - - - NSAC(EPC interworking) - - Docs:=22 -
8.4 S2-2105666 CR Approval 23.501 CR3058 (Rel-17, 'F'): TS23.501 Correction to the NSAC to maintain service continuity NEC Rel-17 CC#4: S2-2105666r07 agreed. Revised to S2-2106661. George Foti (Ericsson) proposes to note the CR. See additional comments.
Jinhua(Xiaomi) provides comments and r01.
George (Ericsson) provides a response.
Iskren (NEC) responds to George (Ericsson).
Iskren (NEC) answers question from George (Ericsson)
Hoyeon (Samsung) provides comments.
Iskren (NEC) answers comments from Hoyeon (Samsung) and George (Ericsson).
George (Ericsson) provides comment.
Srisakul (NTT DOCOMO) provides comment.
Iskren (NEC) answers question from Srisakul (NTT DOCOMO)
Iskren (NEC) provides r01.
Srisakul (NTT DOCOMO) comments and provides r02. But still to check whether we should go in this direction or better to take a simpler approach as proposed in NOTE 3 of 6004r02.
Iskren (NEC) answers Srisakul (NTT DOCOMO)..
George (Ericsson) provides a response. Ericsson objects to r03. It does not address the issue. We provide r04 which is an update of r02 which has just editorial changes.
Jinhua(Xiaomi) provides a comments.
Srisakul (NTT DOCOMO) comments. Do not agree on r03. Support r02 or r04.
Iskren (NEC) is OK with r02 and r04.
Jinhua(Xiaomi) provides a response to Iskren (NEC)
George (Ericsson) provides r05. Just added Ericsson as co-signer. The SCC mode 3 is addressed in 5431. Please check the latest revision.
Ashok (Samsung) objects to all revisions including original CR
Iskren (NEC) disagrees with the objection from Ashok (Samsung) and explains why it is not valid.
Ashok (Samsung) maintains its objection and clarifies to Iskren . Also propose to go with the Jinguo's original proposal
George (Ericsson) provides a response. Ashok, it is very common that operator policies do dictate these things. Its all over the spec. I would propose this goes to CC#3 than. One size does not fit all. The ultimate decision has to be left to the operator not us dictating something on them. Actually some may charge more for these sessions. So this is a very reasonable compromise to satisfy everyone.
Ashok (Samsung) agrees with George's (Ericsson) proposal to discuss in CC#3
Ericsson (George) SSC mode 2 and 3 are already addressed with much more clarity this time. And how is that related to this anyways. Ashok, I thought U are pragmatic. U have not provided any valid reason.
Iskren (NEC) agrees to take this CR to CC#3.
Iskren (NEC) provides r06 with the only change added Xiaomi as a co-signer.
Kaisu(Nokia) provides r07 where 'may not reject' is changed to 'may accept'.
Ashok (Samsung) maintains its objections on all the revisions including the original paper
George (Ericsson) This needs to go to CC#4. Please add it Jinguo. We have a single objection.
Iskren (NEC) agrees with George (Ericsson) to bring this CR to CC#4 and provides comments.
Ashok (Samsung) responds to Iskren (NEC)
Iskren (NEC) answers Ashok (Samsung)
Jinguo (ZTE) comments
Iskren (NEC) answers Jinguo (ZTE)
==== 8.X, 9.X Revisions Deadline ====
Gerald (Matrixx) is requesting at least to remove 'has been exceeded' in r07.
George (Ericsson) responds to Gerald. We have the reached condition there, so this will be fulfilled before exceeded is reached anyway. Given that we passed the deadline lets handle this next meeting and we approve this revision. This is not a show stopper
Gerald (Matrixx) will not block r07 if the quality improvement to just remove 'has been exceeded' is not feasible
George (Ericsson) Thanks Gerald. We will handle it next meeting.
Kaisu (Nokia) recommends to add some further explanation in the next meeting.
Iskren (NEC) answers Kaisu (Nokia).
George (Ericsson) provides comment. I think we have the action dependent on operator policies; and give examples of some of these policies as example.
==== 8.X, 9.X Final Deadline ====
Iskren (NEC) comments - Dear Tao, the only objection from Ashok (Samsung) was withdrawn. I believe it does not now need to go to CC#4 and you can put the latest version r07 for approval.
Revised
8.4 S2-2106661 CR Approval 23.501 CR3058R1 (Rel-17, 'F'): TS23.501 Correction to the NSAC to maintain service continuity NEC, Ericsson, Xiaomi Rel-17 Revision of S2-2105666r07. Approved Agreed
8.4 S2-2105667 CR Approval 23.502 CR2950 (Rel-17, 'F'): TS23.502 Correction to the NSAC to maintain service continuity NEC Rel-17 CC#4: S2-2105667r03 agreed. Revised to S2-2106662. George Foti (Ericsson) proposes to note the CR. Please see 5666.
Iskren (NEC) provides r01.
George (Ericsson) objects to r1. This is not aligned with the consensus of the group and which is reflected in 5666r04.
Iskren (NEC) is ok with the original version.
George (Ericsson) provides a response. The original version does not consider operator policy which in 5666r04. It rejects everything. So neither revisions are OK
Iskren (NEC) answers George (Ericsson).
George (Ericsson) provides a response. Please read the 5666r04. It is safer.
Iskren (NEC) answers George (Ericsson) and provides r02
Ashok (Samsung) objects to all revisions including original CR
Iskren (NEC) disagrees with the objection from Ashok (Samsung) and explains why it is not valid.
Ashok (Samsung) maintains its objection and clarifies to Iskren . Also propose to go with the Jinguo's original proposal
George (Ericsson) provides a response. We have to take this to CC#3.
Iskren (NEC) agrees with George to take this to CC#3..
Kaisu(Nokia) provides r3, to align with 5666r7
Ashok (Samsung) maintains its objections on all the revisions including the original paper
George (Ericsson) provides comment. Please take this one Jinguo to CC#4. We have operator policies already in the text. The statement U added Ashok is operator policy. We don't standardize operator policy. In short there is no valid basis for rejection. What U want is already there and permitted.
Ashok (Samsung) responds to George . I have provided so many points and particularly the 4th points which is leading to release of existing PDU session which itself is a valid reason. In my proposal at least there was no impact to the slice threshold or impact on existing PDU. So in summary agree to discuss in CC#4
George (Ericsson). U don't seem to understand that some operators may charge for over use and they want to allow the session to HO successfully, and to charge it but reject new request even in 5G. Its all called the magic unspecified operator policies. I presume that vendors don't run operator networks.
U are the only company objecting. I have not heard anyone else.
Iskren (NEC) answers Ashok (Samsung) and explains why the reasons for objection are not valid. See bellow.
Iskren (NEC comments
==== 8.X, 9.X Revisions Deadline ====
Gerald (Matrixx) is requesting at least to remove 'has been exceeded' in r03.
George (Ericsson) responds to Gerald. We have the reached condition there, so this will be fulfilled before exceeded is reached anyway. Given that we passed the deadline lets handle this next meeting and we approve this revision. This is not a show stopper.
Gerald (Matrixx) will not block r03 if the quality improvement to just remove 'has been exceeded' is not feasible
==== 8.X, 9.X Final Deadline ====
Iskren (NEC) comments - Dear Tao, the only objection from Ashok (Samsung) was withdrawn. I believe it does not now need to go to CC#4 and you can put the latest version r03 for approval.
Revised
8.4 S2-2106662 CR Approval 23.502 CR2950R1 (Rel-17, 'F'): TS23.502 Correction to the NSAC to maintain service continuity NEC Rel-17 Revision of S2-2105667r03. Approved Agreed
8.4 S2-2105668 CR Approval 23.501 CR3059 (Rel-17, 'F'): TS23.501 Correction to the NSAC for signalling optimisation NEC Rel-17 Noted George Foti (Ericsson) proposes to note CR. Please see 5666.
Iskren (NEC) answers George(Ericsson) and points that this CR is not related to 5666.
George (Ericsson)maintains objection. I indicated that we can fix this in a different way. I don't want AMF be contaminated with this EPS status granted that U are proposing.
Iskren (NEC answers George (Ericsson).
George (Ericsson) provides response inline.
George (Ericsson) provides a response in line.
Iskren(NEC) answers George(Ericsson).
George (Ericsson) provides a response.
Iskren (NEC) answers George (Ericsson)
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) please note this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105669 CR Approval 23.502 CR2951 (Rel-17, 'F'): TS23.502 Correction to the NSAC for signalling optimisation NEC Rel-17 Noted George Foti (Ericsson) proposes to note CR. Please see 5666
Iskren (NEC) answers George(Ericsson) and points that this CR is not related to 5666.
George(Ericsson) maintain my objection. This CR relates to the same issue of support for service continuity between EPS and 5G. It has the same text that U never explained what it means. 'If EPS supports NSAC, the SMF+PGW-C includes the NSAC support indicator in the Nsmf_PDUSession_ContextResponse to the AMF.'
Comments for
Iskren (NEC answers George (Ericsson).
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) please note this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105488 CR Approval 23.501 CR3021 (Rel-17, 'B'): Resolving the editor's note on session continuity in EPC Interworking scenario (Alternative 1) LG Electronics Rel-17 Noted George Foti (Ericsson) proposes to note the CR. Ericsson supports alternative 2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105740 CR Approval 23.501 CR3069 (Rel-17, 'B'): Resolve ENs in NSAC support for EPC interworking ZTE Rel-17 Merged into S2-2106841 George Foti (Ericsson) proposes to note the CR. The changes are already addressed in other CRs in a much clearer fashion.
Jinguo(ZTE) provides r01
George(Ericsson) provides r02. This may need another update depending on the inclusion of the UE ID for the PDU Sessions
Hoyeon (Samsung) provides comments.
Jinguo(ZTE) is fine to merge 5740 into 6004.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105741 CR Approval 23.502 CR2969 (Rel-17, 'B'): NSAC support for EPC interworking ZTE Rel-17 Merged into S2-2106843 George Foti (Ericsson) provides comments
Hoyeon (Samsung) proposes to merge 5714 in 6006.
George (Ericsson) provides a comment.
Haiyang (Huawei) proposes to merge this paper in S2-2106157r01.
Jinguo(ZTE) agree to merge 5741 with 6157
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105775 CR Approval 23.501 CR3080 (Rel-17, 'F'): TS23.501 Correction to the NSAC related to the UEs count in EPC interworking NEC Rel-17 Merged into S2-2106841 Jinguo(ZTE) suggest to merge this paper into 6004 as both of them cover same clause.
Iskren (NEC) suggests to keep this CR separate from S2-2106004 which is controversial and still argued.
Jinguo(ZTE) suggests to merge this paper into 6004
Iskren (NEC) Agrees with Jinguo (ZTE). If S2-2106004 is approved, this CR to be marked as merged to it.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105883 CR Approval 23.501 CR3105 (Rel-17, 'F'): Resolving the editor's note on session continuity in EPC Interworking scenario (Alternative 2) LG Electronics Rel-17 Merged into S2-2106841 George Foti (Ericsson) supports this alterative. We propose to note the CR and merge it in 6004.
Iskren (NEC) proposes to note this CR.
George (Ericsson) provides a response.
Iskren (NEC) provides comments.
Jinguo(ZTE) provides comments.
Jinguo (ZTE) provides comments.
Iskren (NEC) provides comments and propose to use S2-2105666(NEC) as baseline.
George (Ericsson) comments. If EPS counting is not supported Session continuity will not be guaranteed. As stated operators who want to ensure session continuity have to go for EPS counting.
Iskren NEC) answers George (Ericsson).
Iskren (NEC) comments.
Hyunsook (LGE) provides a comment.
Hoyeon (Samsung) provides comments and proposes to merge this in 6004.
George (Ericsson) We support this proposal for this Release 17. We have to enable proper analysis of solutions for option 1. We cant do that in Release 17.
Hyunsook (LGE) agrees to merge this CR into 6004.
NEC (Kundan) provides further comments.
George (Ericsson) provides a comment. Please don't include a reference to another CR with the wrong subject. This CR is about 5883 and U are including a reference to 6004r02. It is confusing.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106004 CR Approval 23.501 CR3126 (Rel-17, 'B'): Resolve ENs in NSAC support for EPC interworking Samsung, NTT DOCOMO Rel-17 CC#4: r24 + changes agreed. Revised to S2-2106841, merging S2-2105740, S2-2105775, S2-2105883, S2-2106156, S2-2106246 and S2-2106247 George Foti (Ericsson) provides comments.
Hoyeon (Samsung) provides r01.
George (Ericsson) provides a response..
Iskren (NEC) comments. The current versions r01 and r02 are not acceptable.
Srisakul (NTT DOCOMO) provides r02.
Kundan (NEC) provides r02. Sending also to the correct thread.
George (Ericsson) provides r03. Minor typo. I am good with the reduction.
George (Ericsson) provides a comment. The only r02 on the 3GPP site is DOCOMO CR. So what U are attaching is not there. SO something is gone wrong Please check
Hoyeon (Samsung) is OK with r03 and provides comments.
Kundan (NEC) provides rev04 which enhances the captured text in rev 03.
Haiyang (Huawei) provides r05.
George (Ericsson) provides r06 which added Ericsson as con-signer. I don't know why there are r04, and 05 created.
Srisakul (NTT DOCOMO) provides r07 and r08.
George (Ericsson) supports r07 only. The added text about different NSACFs is redundant. It is in the spec. Do we need to repeat 2 dozen times.
Iskren (NEC) provides r09 with restored EN on session continuity.
Iskren (NEC) provides r10.
George (Ericsson) ask a question. Why was the text about mobility when EPS counting is not supported as well as the note 3 removed. That was a reasonable text to include.
Hoyeon (Samsung) can support r07 and provides r11 and comments.
Hoyeon (Samsung) provides r12 (merge 5740 in here).
correcting the sender's details.
Kundan(NEC) seeks clarification with Srisakul.
Srisakul (NTT DOCOMO) responds to Kundan and provides r13.
George (Ericsson) provides r14. Minor editorial.
Kaisu (Nokia) provides r15. Clarification of text by treating different cases in separate sentences.
Hoyeon (Samsung) provides suggestion to rephrase the sentence.
Kundan(NEC) is fine with r14 or r15.
Jinguo(ZTE) has further comments and provides r16
Srisakul (NTT DOCOMO) has further comments and provides r17. Object to r16.
Hoyeon (Samsung) provides comments on how to handle when the quota is exceeded, and provides r17 for comparison.
Srisakul (NTT DOCOMO) proposes r18 as alternative. OK with Samsung's suggestion earlier and the NOTE in r18.
Kundan (NEC) supports r18 but not r17 because the UE action is missing in r17. Without the UE action the CR doesn't give any clear direction to stage 3.
Srisakul (NTT DOCOMO) asks Hoyeon to upload her r17 version on the server again, since r17 has already been uploaded by Srisakul.
Hoyeon (Samsung) is OK with r17 and r18.
George (Ericsson) provides r19 Linguistic corrections only. .
Jinguo(ZTE) asks further question
Srisakul (NTT DOCOMO) provides clarification to Jinguo.
Jinguo(ZTE) if fine with r19, Thanks Srisakul for clarification
Haiyang(Huawei) asks questions on PDU Session ID
Kundan (NEC) NOT ok with r017 or 18 or 19. We can't accept it. you changed S-NSSAI with slice availability again. slice availability has no meaning at all very ambiguous. We support release 15 Only.
Kundan (NEC) provides further comment on r17/18/19 and don't accept this as it prevents UE to attach to 5G for all slices.
George (Ericsson) provides r20 using r16 as a base. There is no basis for this statement: If the maximum number of UEs and/or the maximum number of PDU sessions is reached, the SMF+PGW-C may accept the PDN connection without sending any S-NSSAI to the UE in the PCO IE. If we want operator policies to playa role than this can be added.
Srisakul (NTT DOCOMO) responds to Kundan.
George (Ericsson) already provide r20 using r16 as a base.
Srisakul (NTT DOCOMO) objects r20 and provides r21.
Kundan (NEC) responds to Srisakul. In short the 'slice availability in 5GC' is ambiguous term. Is it S-NSSAI or APN or what is it???
George (Ericsson) comments that slice availability is unclear. Either clarify what it is or at least remove that part; nothing breaks if it is gone. The rest is OK in r21.
Srisakul (NTT DOCOMO) comments. Provide r22 and r23.
Srisakul (NTT DOCOMO) please check r22 and r23 that I just provided.
George (Ericsson) comments r22 is clearer, and we can accept it.
Haiyang (Huawei) comments. Provide r24 and r25(respectively based on r22 and r23).
George (Ericsson) commented. PDU session ID is now mandatory. So your 2 revisions are wrong
Kundan (NEC) r22 is fine with us and we accept it.
Iskren (NEC) could you please go with one revision at a time.
Jinguo(ZTE) asks one more question on r22
George (Ericsson) I think this is because U have 2 different quotas, EPS quota is gone, 5GC quota is still there.
Jinguo (Ericsson) asks further question
George (Ericsson) comments. Jinguo U are not Ericsson yet. Remember I asked in several email for clarity on how these 2 quotas will work. I said we needed more details. No one responded. The short answer is stage 3 will complete this. But we designed a lot of these things during the normative phase, 75%. Last time ??
Ashok (Samsung) shares same view as Jinguo
George (Ericsson) comments. It is a common SMF+PGW. I am not a fan of separate quotas but this is not an issue.
Ashok (Samsung) responds to George (Ericsson) . The question how SMF+PGW-C will know that quota for 5G is available. NSACF just respond by saying that quota is exceeded for EPC and the PDN connections will be rejected
Kaisu (Nokia) asks about the usage of the PDU session ID for NSAC for the number of UEs.
George (Ericsson) comments. It is a common SMF+PGW. It can store both quotas. These slices are subject to IWK.
Kaisu (Nokia) does not see it critical to indicate 5GS slice availability to the UE.
George (Ericsson). Now I see that this PDU session ID was added at the wrong clause. Well when U have may revisions flying no time to properly read.
Ashok (Samsung) comments. NSACF only stores quota. NF consumer like AMF/SMF/SMF+PGW-C gets status as accepted or rejected
Malla (NTT DOCOMO) replies to Ashok (Samsung).
==== 8.X, 9.X Revisions Deadline ====
Ashok (Samsung) ask clarification from Malla (NTT DOCOMO)
Jinguo(ZTE) provides answer to Hoyeon(Samsung)
Hoyeon (Samsung) replies to Kaisu (Nokia) regarding the number of signalling.
Hoyeon (Samsung) clarifies the use of PDU session ID in registration counting request.
Kundan(NEC) is fine with r24.
George (Ericsson) can live with r24, although there are some language problems with the added text. Subjected is not a correct word.
Malla (NT DOCOMO) replies to Ashok (Samsung)
Kundan(NEC) indicates that rev 25 is available (not sure if it was made available after tdoc deadline as I can't see this in chairman report). We don't support r25 as it is not clear. We support r24 or r15.
Hoyeon (Samsung) proposes to approve r24 and discuss the NSACF logic to decrease the number of UEs in the next meeting.
Jinguo(ZTE) points that r24 still have two issues, but can live with it at this meeting. Ask to continue the discussion at next meeting.
Srisakul (NTT DOCOMO) r24 is ok. Let's discuss other issues in the next meeting.
Genadi (Lenovo) can live with r24 and proposes to add an Editor's Note.
George (Ericsson) provides comment. We stated we are OK with r24, but I don't actually understand the scenario by Hoyeon to justify the PDU session ID inclusion by AMF. Please explain completely the scenario.
Hoyeon (Samsung) replies to George (Ericsson) and provides further explanation.
George (Ericsson) The PDU session ID is already added in 5431 r06, which hopefully will progress. Is that not sufficient. ?.
Jinguo(ZTE) supports the proposal from Genadi (Lenovo) to add an Editor's Note on top of r24 at CC#4.
Hoyeon (Samsung) asks a clarification on the Editor's Note proposed by Genadi (Lenovo).
Haiyang(Huawei) can only accept r24 or r25. R24+EN is also OK.
Hoyeon (Samsung) replies to George (Ericsson). NSAC for the number of UEs and NSAC for the number of sessions can be performed in different NSACFs, the session ID could be not available for the NSACF for the number of UEs.
George (Ericsson) responds. Let's leave it for now and rethink it over after the meeting. We will come back to it at the next meeting. In the meantime, The NSACF will know if the UE has already a second session. So even if the SMF + PGW1 decreased the UE blindly, the NSCAF will not act on it. Isn't that simpler. The NSACF has all the info to act correctly regardless of the SMF +PGW1 ignorance
Srisakul (NTT DOCOMO) suggests to go with r24. Let's have a common understanding that the issues raised by Jinguo earlier can be further discussed, if texts of EN to be added could not be agreed.
Hoyeon (Samsung) agrees to leave it for now and come back to it at the next meeting. That was my earlier comments :)
Kundan (NEC) requests to agree r24. Let's discuss remaining thing in next meeting as suggested by many delegates.
Genadi (Lenovo) provides a reply to Hoyeon.
Srisakul (NTT DOCOMO) provides comments to Genadi.
Kaisu (Nokia) also supports the proposal from Genadi (Lenovo) to add an Editor's Note on top of r24 at CC#4.
George (Ericsson) asks a question.
Genadi (Lenovo) provides a comment Srisakul (NTT DOCOMO) and requests to open the CR during the CC#4.
George (Ericsson) provides comment. We may not have time to discuss so lets just add the EN at CC4. We at least move one step forward.
Jinhua (Xiaomi) provides comment. Agree with George that move one step forward. Propose r24 for approval, and have the consummate discussion next time.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106841 CR Approval 23.501 CR3126R1 (Rel-17, 'B'): Resolve ENs in NSAC support for EPC interworking Samsung, NTT DOCOMO, Ericsson, ZTE Rel-17 Revision of S2-2106004r24 + changes, merging S2-2105740, S2-2105775, S2-2105883, S2-2106156, S2-2106246 and S2-2106247. Approved Agreed
8.4 S2-2106006 CR Approval 23.502 CR3026 (Rel-17, 'B'): NSAC support for EPC interworking Samsung Rel-17 CC#4: r07 + changes agreed. Revised to S2-2106842 George Foti (Ericsson) provides comments
Hoyeon (Samsung) provides r01.
Hoyeon (Samsung) provides r02.
George (Ericsson) provides a comment.
George (Ericsson) asks a question. Where is the description for the handling of independent or integrated limits be described. In 23.50 or 23.502.
Kundan (NEC) provides revision 3.
Haiyang (Huawei) provides r04 and proposes to discuss multiple NSACF scenarios in S2-2106157.
Hoyeon (Samsung) provides r05.
Kundan (NEC) expresses the concern for r04.
Jinguo (ZTE) proposes to use 6157 as basis for 3rd change
George (Ericsson) provides a comment. I agree with Jinguo. Third change to be discussed with 6157. WE are OK only with r04.
Hoyeon (Samsung) is OK to use 6157 as basis for 3rd change. Then, let's consider r04 as a revision of this CR (6006).
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) provides r06 in draft folder, the service name should be updated to align with 5744. ask for CC#4
Haiyang(Huawei) comments on r06
Hoyeon (Samsung) proposes to approve r04 in this meeting and have one rapporteur CR in the next meeting for all the clean-up.
Jinguo(ZTE) asks for CC#4. We can do it at this meeting.
Srisakul (NTT DOCOMO) ok with r04. If r06 with small changes as proposed earlier could be accepted in CC#4, it is fine as well.
Hoyeon (Samsung) had offline disucssino with Jinguo, and OK to discuss r07 with small changes in the CC#4.
George (Ericsson) Ok with r06 as well.
George (Ericsson) cant see any changes
Srisakul (NTT DOCOMO) ok with changes proposed in r07
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106842 CR Approval 23.502 CR3026R1 (Rel-17, 'B'): NSAC support for EPC interworking Samsung, NTT DOCOMO, ZTE Rel-17 Revision of S2-2106006r07 + changes. Approved Agreed
8.4 S2-2106156 CR Approval 23.501 CR3152 (Rel-17, 'C'): Update NSAC for interworking Huawei, HiSilicon Rel-17 Merged into S2-2106841 George Foti (Ericsson) proposes to note the CR. Additional comments below
Haiyang(Huawei) clarifies to George Foti (Ericsson) and provides r01
Ashok (Samsung) agrees with George and feel this CR is not needed
George Foti (Ericsson) provide a comment.
Srisakul (NTT DOCOMO) proposes to merge 6156 into 6004 and uses 6004 as a basis.
Hoyeon (Samsung) also believe that the sequence of service invocations is implementation and no need to describe in the spec.
Haiyang(Huawei) is OK to merge 6156 into 6004 and uses 6004 as a basis as proposed by Srisakul (NTT DOCOMO).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106157 CR Approval 23.502 CR3045 (Rel-17, 'C'): Update NSAC for interworking Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106843, merging S2-2105741 George Foti (Ericsson) provides comments
Haiyang (Huawei) provides r01
Haiyang (Huawei) provides r02
George (Ericsson) provides r03. Did language related clean up, cut redundant text, and added Ericsson.
Haiyang (Huawei) provides r04 for editorials
Jinguo(ZTE) provides r05
Hoyeon (Samsung) provides r07
==== 8.X, 9.X Revisions Deadline ====
TAO(VC) let's check r06 then
George (Ericsson) is OK with r03, r04, r05 or r06. We object to all other revisions. Adding the Session ID in a procedure about number of Registered UEs is wrong. It is not even in that procedure referenced in here.
Haiyang (Huawei) is OK with r06
Hoyeon (Samsung) is OK with r06, and happy to co-sign.
Kaisu (Nokia) is OK with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106843 CR Approval 23.502 CR3045R1 (Rel-17, 'C'): Update NSAC for interworking Huawei, HiSilicon, Ericsson, ZTE, NTT DOCOMO, Samsung Rel-17 Revision of S2-2106157r06, merging S2-2105741. Approved Agreed
8.4 S2-2106246 CR Approval 23.501 CR3183 (Rel-17, 'B'): Support of Session Continuity with NSAC from EPC to 5GS Xiaomi Rel-17 Merged into S2-2106841 George Foti (Ericsson) proposes to note the CR. This is already covered in numerous other CRs. Please see 6157, 6006, 6157. They need to be consolidated in one.
Jinhua(Xiaomi) responds to George Foti (Ericsson), comment need to be clarified. We propose to choose one of them(including 5666,5488,5740,5883,6004, and 6246) as the base document for further discussion, and merge others into it.
George Foti (Ericsson) proposes to use 6004 as the basis. I did provide some comments on 6004. But all other CRs can be considered merged in this one.
Jinhua(Xiaomi) reply to George Foti (Ericsson) merge 6246 into 6004 is OK, use 6004 as the base for discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106247 CR Approval 23.501 CR3184 (Rel-17, 'B'): Update of NSACF Discovery and Selection with NSAC in EPC Xiaomi Rel-17 Merged into S2-2106841 George Foti (Ericsson) proposes to note the CR. Please see 6246
Jinhua(Xiaomi) responds to George Foti (Ericsson), comment need to be clarified, as the reply of 6246. We propose to choose one of them(6004,6156,6247) as the base document for further discussion, and merge others into it.
George Foti (Ericsson) proposes to use 6004 as the base taking into account comments provided on 6004.
Jinhua(Xiaomi) reply to George Foti (Ericsson) merge 6247 into 6004 is fine, and use 6004 as the base for discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106430 CR Approval 23.501 CR3220 (Rel-17, 'F'): NSAC procedure in EPS when APN maps to more than one S-NSSAI. NEC Rel-17 r04 agreed. Revised to S2-2106844 George Foti (Ericsson) proposes to note the CR. It is the UE and not the SMF that selects the slice
NEC provides response to Ericsson. George comments applies to 5GS not for EPS. The CR is for EPS.
Srisakul (NTT DOCOMO) provides comments. Current spec TS23.501 clause 5.15.7.1 already allows selecting a S-NSSAI based on operator's policy. We do not need to go into details of which one to select first.
George Foti (Ericsson) provides a comment. The actual selection is out of scope of this CR as stated below. SO we would like to note the CR.
Kundan(NEC) provides a revision based on Srisakul feedback and also provides some more explanation.
Ashok (Samsung) provides comments and r02
Kundan (NEC) provides comments to Ashok (Samsung) on revision 02.
Kundan (NEC) provides comments to Ashok (Samsung).
Ashok (Samsung) comments
Srisakul (NTT DOCOMO) comments
George Foti (Ericsson) provides a response.
Fenqin (Huawei) provides a comment.
Srisakul (NTT DOCOMO) provides comment.
Kundan(NEC) revised CR (rev 3) based on comments from Srisakul, Fenqin and Geroge.
George Foti (Ericsson) provides r04. Minor update
Srisakul (NTT DOCOMO) comments.
Ashok (Samsung) responds Srisakul
George (Ericsson) I purposely kept it as an implementation option. This is not an issue if the operator properly configures his network. I assume most will. But to complete the spec. it is OK to include it.
Kundan(NEC) is fine with rev 04 from Srisakul.
Kundan (NEC) responds to Srisakul(DOCOMO) and Ashok (Samsung) to clarify further.
Ashok (Samsung) responds to Kundan
Kundan (NEC) responds to Ashok.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106844 CR Approval 23.501 CR3220R1 (Rel-17, 'F'): NSAC procedure in EPS when APN maps to more than one S-NSSAI. NEC Rel-17 Revision of S2-2106430r04. Approved Agreed
8.4 - - - NSAC(roaming) - - Docs:=8 -
8.4 S2-2105742 CR Approval 23.501 CR3070 (Rel-17, 'B'): KI#1KI#2 - Roaming support for NSAC ZTE Rel-17 Noted George Foti (Ericsson) proposes to note the CR. This CR does not address the issue in any meaningful way.
Jinhua(Xiaomi) support 5742 with H-SMF enhanced to support NSAC for both number of UEs and PDU sessions in HR roaming case. r01 is provided .
Fenqin (Huawei) agree with George and do not see that this paper solve the NSAC with HPLMN control issue.
Jinguo(ZTE) response.
Heng(China Telecom) provide comments.
Fenqin (Huawei ) comments.
Jinguo(ZTE ) is ok to note this CR since no support.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) objects to this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105756 CR Approval 23.501 CR3074 (Rel-17, 'B'): Roaming support for NSAC in VPLMN China Telecom Rel-17 r05 agreed. Revised to S2-2106845 George Foti (Ericsson) provides comments
Heng(China Telecom) provides reply
George Foti (Ericsson) provides comments.
Heng(China Telecom) provides r01
George (Ericsson) provides r02. Added Ericsson cosigner and some minor editorial changes.
Heng(China Telecom) is ok with r02.
Fenqin (Huawei) provides r03.
George (Ericsson) provides r04. More clean up
Heng(China Telecom) ask clarification for r04.
George (Ericsson) restored. It was a mistake.
Heng(China Telecom) is fine with r05.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106845 CR Approval 23.501 CR3074R1 (Rel-17, 'B'): Roaming support for NSAC in VPLMN China Telecom, Ericsson Rel-17 Revision of S2-2105756r05. Approved Agreed
8.4 S2-2105764 CR Approval 23.502 CR2973 (Rel-17, 'F'): Clarification on NSACF registration to support roaming China Telecom Rel-17 Approved Fenqin (Huawei) provides r01
Heng(China Telecom) ask clarification on r01
George (Ericsson) accepts only the original.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105769 CR Approval 23.501 CR3076 (Rel-17, 'B'): Roaming support for NSAC with HPLMN control Huawei, HiSilicon, China Telecom Rel-17 Noted George Foti (Ericsson) proposes to note the CR. This is already covered in a much clearer fashion in 5756. The NSACF will not have all slices configured in it. This is not required. A VPLMN has to map the subscribed slices to the VPLMN slices today and that continue to be valid here. The NSACF needs to only register in NRF the PLMN slices and nothing else. Please see comments on 5756
Fenqin(Huawei) responds
Iskren (NEC) provides comments
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105770 CR Approval 23.502 CR2975 (Rel-17, 'B'): Roaming support for NSAC with HPLMN control Huawei, HiSilicon, China Telecom Rel-17 Noted George Foti (Ericsson) proposes to note the CR. Please see additional comments.
Fenqin (Huawei) Responds
Iskren (NEC) provides comments
George (Ericsson) provides comments
Fenqin (Huawei) provides comments
George (Ericsson) provides comments.
Kaisu (Nokia) asks question for clarification
Fenqin (Huawei) provides a asks question for clarification
Kaisu (Nokia) provides a comment
George (Ericsson) provides a comment.
Fenqin (Huawei) provides a comment
George Foti (Ericsson) responds. I see no need for this at this point. Therefore the CR should be noted
Iskren (NEC) provides a comment.
Fenqin (Huawei) provides a response.
George (Ericsson) provides a response.
George (Ericsson) provides a response. U misunderstood the pull -push. The HPLMN is pulling. I am not in favor of every VPLMN to interrogate the Home; that's a push. So we maintain our objection.
George (Ericsson). I don't think any NSACF in HPLMN can be used. It is an HPLMN decision. And if one is designated and discovered than what additional functionality will we have to support in this one and only one. I think we need to have clear requirements before jumping here. This can wait
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) is objects to all revisions as well as original
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106458 CR Approval 23.501 CR3225 (Rel-17, 'B'): HPLMN based Admission Control of UEs registering to a Network Slice via VPLMN Nokia, Nokia Shanghai Bell Rel-17 Check WI Code spelling. Noted. Covered by (noted) S2-2105770 George Foti (Ericsson) proposes to note the CR. Please see provides comments
Iskren (NEC) provides comments
Fenqin (Huawei) propose to merge this paper to 5770
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106462 CR Approval 23.502 CR3109 (Rel-17, 'B'): HPLMN based Admission Control of UEs registering to a Network Slice via VPLMN Nokia, Nokia Shanghai Bell Rel-17 Check WI Code spelling. Noted. Covered by (noted) S2-2105770 George Foti (Ericsson) proposes to note the CR. Please see 6458
Iskren (NEC) provides comments
Fenqin (Huawei) propose to merge to 5770
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 - - - NSAC(multiple NSACFs) - - Docs:=7 -
8.4 S2-2105340 CR Approval 23.501 CR3005 (Rel-17, 'B'): Support multiple NSAC selection for AMF III Rel-17 Merged into S2-2106846 George Foti (Ericsson) proposes to note this CR, and merge in 5771 r01
Yan (China Mobile) supports the merge, and provides comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105342 CR Approval 23.501 CR3006 (Rel-17, 'B'): Support UE interact with multiple NSAC. III Rel-17 Noted George Foti (Ericsson) provides comments. Is this really needed. ?
Iskren (NEC) suggests this CR to be noted
Jinguo(ZTE) comments. This CR does not use correct 501 version.
Fenqin (Huawei) provides r01.
George (Ericsson) objects to the CR. I indicated this is not the NEFs role. The whole text is not needed.
Fenqin (Huawei) provides comments
George (Ericsson) responds. I am OK with the query part, and where the NEF role is fine. I am not OK with the subscribe part as this is a much bigger issue.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) objects to rev01. We need to align the CR with our 23.502 decision
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105771 CR Approval 23.501 CR3077 (Rel-17, 'F'): Support of multiple NSACF instance Huawei, HiSilicon, China Mobile Rel-17 r03 agreed. Revised to S2-2106846, merging S2-2105340 George Foti (Ericsson) provides r01
Fenqin (Huawei) ask question for clarification
George Foti (Ericsson) provides response
Fenqin (Huawei) provides r02
George (Ericsson) provides r03. Just made first NSACF plural.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106846 CR Approval 23.501 CR3077R1 (Rel-17, 'F'): Support of multiple NSACF instance Huawei, HiSilicon, China Mobile Rel-17 Revision of S2-2105771r03, merging S2-2105340. Approved Agreed
8.4 S2-2105772 CR Approval 23.502 CR2976 (Rel-17, 'B'): Status Exposure for multiple NSACF instances Huawei, HiSilicon, China Telecom Rel-17 r05 agreed. Revised to S2-2106822 George Foti (Ericsson) seek clarification
Fenqin (Huawei) responds
George Foti (Ericsson) provides comment
Iskren (NEC) proposes this CR to be noted
Iskren (NEC) suggest this CR to be noted.
Ashok (Samsung) provides comments
Fenqin (Huawei) provides comments
Fenqin (Huawei) seeks clarification
George (Ericsson) asks a question.
Fenqin (Huawei ) responds and provide r01
Ashok (Samsung) comments
George (Ericsson) provides a comment.
George (Ericsson) responds. I don't see this approach as feasible. It's not the NEF role to make this kind of decision on behalf of an AF, and will require logic in the NEF that is out of its role. I would support only individual notifications (aggregation is an option not implementation dependent). I am not Ok with the Note.
George (Ericsson) comments.
George (Ericsson) more comments. I think the NWDAF may have a role to play here but this has to be Release 18.
Iskren (NEC) - this CR is not acceptable. It should be noted
Fenqin (Huawei) - ask question for clarification
Fenqin (Huawei) comments.
Ashok (Samsung) responds to Fenqin
Jinguo(ZTE) comments
Fenqin (Huawei)responds
George (Ericsson) provides comment.
George Foti (Ericsson) provides comment. I already indicated its not the NEF role to do what U are proposing. In addition, U seem to be proposing model 1. So we are not in agreement on either.
George Foti (Ericsson) provides comment. The aggregation part for the Request/Response is straight forward We don't need to say anything. The device in the SUBBSCRIBE case. Also U did not indicate which model below U are supporting or if U have a different variant please spell it.
Ashok (Samsung) responds to Fenqin (Huawei)
Heng(China Telecom)support multiple NSACFs
George (Ericsson) provides a response.
Fenqin (Huawei) provides a response.
George (Ericsson) provides r02. This is the only thing that I could up with to allow us to deal with this next Release.
Fenqin (Huawei) provides r03.
George (Ericsson) provides a response.Given the complexity of this, and need for consistent behavior we prefer postponing it. We can accept r02 or just postpone.
Fenqin (Huawei) ask question for clarification .
George (Ericsson) comments. The NEF behavior is now contaminated with one specific event details. This does not respect separation of concerns. NEFs exposes events but don't understand any specifics for any event. Does that help ?
Fenqin (Huawei) ask George to check the event exposure handling at the TS23.502.
Jinguo (ZTE) provides response
George (Ericsson) provides response. We have the option of passing the info to the AF as is, by including the node address, or even to transparently pass the notifications the AF when they are being received. Let the AF do what it wants. I think the NEF interaction with NWDAF is OK. I already indicated that this is one possibility. But this does not imply understanding the event specifics
Iskren (NEC) - The NEF can not play the role of primary NSACF. This CR should be noted.
Fenqin (Huawei ) disagree with the statement from Iskren(NEC)
Heng (China Telecom ) agree with Fenqin,
Fenqin (Huawei ) provides r04
Iskren (NEC) comments on r04
Fenqin (Huawei ) provides r05
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) is OK with r05
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106822 CR Approval 23.502 CR2976R1 (Rel-17, 'B'): Status Exposure for multiple NSACF instances Huawei, HiSilicon, China Telecom Rel-17 Revision of S2-2105772r05. Approved Agreed
8.4 S2-2105910 CR Approval 23.502 CR3007 (Rel-17, 'B'): AF aggregates the number of registered UEs and established PDU Sessions exposed by multiple NSACFs China Mobile Rel-17 Noted Iskren (NEC) proposes to note this CR.
Ashok (Samsung) shares same view as Iskren and proposes to note this CR.
Dan (China Mobile) reply and do not agree with the above comment
Ashok (Samsung) clarifies to Dan
Dan(China Mobile) reply to Ashok(Samsung) and give a suggestion
Dan(China Mobile) provide r01 to reflect the discussion
George (Ericsson) proposes to note the CR. 4772 is addressing the same issue. So this CR is merged in there.
Dan (China Mobile) reply to George(Ericsson)
==== 8.X, 9.X Revisions Deadline ====
Dan (China Mobile) provide a suggestion and ask George(Ericsson) question whether this update proposal is ok.
George(Ericsson) comment. Isnt that already allowed in 23.502 ?
==== 8.X, 9.X Final Deadline ====
Noted
8.4 - - - NSAC(Other aspects) - - Docs:=27 -
8.4 S2-2105857 CR Approval 23.502 CR3000 (Rel-17, 'F'): NSACF receiving update requests from multiple consumer NFs Lenovo, Motorola Mobility, Samsung, NEC Rel-17 CC#4: r03 + changes agreed. Revised to S2-2106663. George Foti (Ericsson) seek clarification.
Jinguo(ZTE) supports this paper and propose to store NF Set ID in the NSACF
George (Ericsson) provides a comment. U are not addressing the question. This has nothing to do with SET ID.
Genadi (Lenovo) provides reply to George (Ericsson).
Genadi (Lenovo) provides reply to Jinguo (ZTE).
George Foti (Ericsson) provides a response. That's fine, but lets than make that clearer to ensure we re-use what exists.
Genadi (Lenovo) provides r01.
Haiyang(Huawei) provides r02.
Genadi (Lenovo) provides comments to r02 by Haiyang(Huawei).
George (Ericsson) only supports r01. This added entry is internal implementation. Mandating it is not relevant, nor enforceable.
Haiyang(Huawei) responds
Haiyang(Huawei) provides r03
Genadi (Lenovo) is OK with the r03.
Ashok (Samsung) is fine with r03.
George (Ericsson) provides r04. Remove this confusing and superfluous phrase (including the NF ID) . The entry is gone. That all what we need. Saying the same thing in multiple ways is uncalled for.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106663 CR Approval 23.502 CR3000R1 (Rel-17, 'F'): NSACF receiving update requests from multiple consumer NFs Lenovo, Motorola Mobility, Samsung, NEC, Huawei, HiSilicon Rel-17 Revision of S2-2105857r03 + changes. Approved Agreed
8.4 S2-2106155 CR Approval 23.501 CR3151 (Rel-17, 'F'): NSAC for priority services Huawei, HiSilicon Rel-17 Postponed Ashok (Samsung) seeks clarification
Haiyang(Huawei) clarifies to Ashok (Samsung)
Jinguo(ZTE) comments
Haiyang(Huawei) clarifies to Jinguo(ZTE)
George Foti (Ericsson) asks a question.
Haiyang(Huawei) replies to George Foti (Ericsson)
George Foti (Ericsson) responds.
Haiyang(Huawei) comments
George (Ericsson) comments. This has to been solved already. The AMF has to know that during the UE context exchange from MME, otherwise how will it set the ARP for this session correctly.
George (Ericsson) ask for clarification
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2106189 CR Approval 23.502 CR3055 (Rel-17, 'F'): Delete FFS related to Network Slice Admission Control CATT Rel-17 Merged into S2-2106849 George Foti (Ericsson) is partially OK with the CR and provides comments
Ashok (Samsung) supports the proposal
Kundan[NEC] seeks clarifications.
Yunjing (CATT) replies to Kundan (NEC).
Jinguo (ZTE) comments.
George Foti (Ericsson) support option 3 or option 4. The backoff timer is equivalent to shooting in the dark. The NSACF has no clue as to what is the slice congestion status as it does not have the overall picture.
Jinguo(ZTE) is also fine with option 3.
Ashok (Samsung) is not OK with option 3.
Kaisu (Nokia) does not agree on introducing a backoff-timer in the AMF<=>NSACF signalling interface, proposes to note 6189.
Iskren (NEC) provides comments
Yunjing (CATT) replies to Iskren (NEC).
Yunjing(CATT) replies to Kaisu (Nokia) and does not agree to note 6189 which includes more content except introducing a backoff-timer.
Yunjing (CATT) replies to George Foti (Ericsson). The NSACF can obtain the slice congestion status from NWDAF which have the overall picture and decide the timer based on the slice congestion status.
Kaisu(Nokia) agrees with Yunjing that we need to remove the two FFSs (on high admission control accuracy and SMF/AMF interaction with NSACF)
Jinguo(ZTE) suggests to use 5431 as basis to resolve these Editor Note
George (Ericsson) will provide a new revision adding aspects from this one.
Yunjing(CATT) is ok to merge 6189 to 5431.
George (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106346 CR Approval 23.502 CR3090 (Rel-17, 'F'): Resolve EN on signalling restriction when the maximum number of UEs has been reached for prolonged time Lenovo, Motorola Mobility, Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105425 CR Approval 23.501 CR3013 (Rel-17, 'B'): KI#1 : Support for Signalling Restriction Flag. Ericsson Rel-17 Noted Kaisu (Nokia) does not agree on adding a Signalling Restriction Flag in the NRF and proposes to note 5425.
Iskren (NEC) suggest we note this CR.
Ashok (Samsung) proposes to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105428 CR Approval 23.502 CR2906 (Rel-17, 'B'): KI#1 : Support for Signalling Restriction Flag Ericsson Rel-17 Noted Kaisu (Nokia) does not agree on adding a Signalling Restriction Flag in the NRF and proposes to note 5428.
Iskren (NEC) proposes to note this CR as it does not work.
Ashok (Samsung) shares same view as Iskren and proposes to note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106496 CR Approval 23.502 CR3116 (Rel-17, 'B'): AMF updating NSACF to decrement the count for UE's deemed not reachable. Nokia, Nokia Shanghai Bell, Rel-17 Postponed Ashok (Samsung) provides comment
Jinguo(ZTE) agrees with Ashok
Kaisu(Nokia) responds to comments.
Srisakul (NTT DOCOMO) provides comment.
Fenqin (Huawei) provides comment.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) propose to postpone or note this CR
Tao(VC) can we agree r00?.
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2106345 CR Approval 23.501 CR3201 (Rel-17, 'B'): Completion of NSAC per access type Lenovo, Motorola Mobility Rel-17 r04 agreed. Revised to S2-2106847 George Foti (Ericsson) seek clarification
Genadi (Lenovo) provides answers to George (Ericsson)
George Foti (Ericsson) provides a response
Kundan (NEC) seeks clarification.
Yunjing (CATT) provides comments.
George Foti (Ericsson) proposes to remove the notes about multiple entries. This is really implementation and we have not means for verification. As such it has to be removed or watered down to clearly say it is an implementation option. I prefer removing it completely. There is no need for it.
Genadi (Lenovo) provides answers to Kundan (NEC) on the inclusion of the AT parameter to AMF and UE.
Genadi (Lenovo) provides answers to Yunjing (CATT) on the NOTE 1.
Fenqin (Huawei) ask one question for clarification
Ashok (Samsung) comments
Genadi (Lenovo) provides answers to George (Ericsson) on the multiple entries per AT in the NSACF.
George (Ericsson) comments. I am Ok with the new proposal.
Genadi (Lenovo) provides comments to Ashok (Samsung).
Genadi (Lenovo) provides answers to Fenqin (Huawei).
Fenqin (Huawei) provides a response
Ashok (Samsung) responds to Genadi (Lenovo)
Genadi (Lenovo) provides comment to George (Ericsson) and provides r01.
George (Ericsson) provides a comment
Genadi (Lenovo) agrees with suggestion by George (Ericsson) and provides r02.
Yunjing (CATT) provides comments and r03.
Ashok (Samsung) responds Genadi (Lenovo)
Genadi (Lenovo) is OK with the r03 and provides an answer to a question by Yunjing (CATT) .
Genadi (Lenovo) provides r04 to capture the counting of UE registered with both Access Types based on comment by Ashok (Samsung).
==== 8.X, 9.X Revisions Deadline ====
Ashok (Samsung) is fine with r04.
Jinguo(ZTE) suggesst to go with r04.
George (Ericsson) is OK with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106847 CR Approval 23.501 CR3201R1 (Rel-17, 'B'): Completion of NSAC per access type Lenovo, Motorola Mobility Rel-17 Revision of S2-2106345r04. Approved Agreed
8.4 S2-2106349 CR Approval 23.502 CR3091 (Rel-17, 'B'): Completion of NSAC per access type Lenovo, Motorola Mobility Rel-17 Approved George Foti (Ericsson) asks clarification. What does it mean takes into account. Are U implying that of the access type does not apply for the slice, the NASCF will ignore it. This is really unclear.
Genadi (Lenovo) provides comments to George (Ericsson).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2106432 CR Approval 23.501 CR3221 (Rel-17, 'F'): NSAC procedure when 5G subscription withdrawn NEC Rel-17 Noted George Foti (Ericsson) proposes to note the CR. This will happen as part of the exiting procedures. Please explain what is missing.
Fenqin (Huawei ) ask question for clarification.
Kundan (NEC) provides clarification to George.
Kundan(NEC) provides answers to Fenqin's question. Hope this clarifies your concern.
Kundan (NEC ) provide response to Fenqin.
Fenqin (Huawei ) suggest to note this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105487 CR Approval 23.501 CR3020 (Rel-17, 'F'): Updating the functionality of AMF and SMF on support for NSAC LG Electronics Rel-17 Merged into S2-2106848 George Foti (Ericsson) proposes to note this CR and to merge in 5713
Hyunsook (LGE) agrees to merge this CR into 5713
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105713 CR Approval 23.501 CR3066 (Rel-17, 'F'): Addition of NSACF services Huawei, HiSilicon Rel-17 r11 agreed. Revised to S2-2106848, merging S2-2105487, S2-2105743 and S2-2105973 George Foti (Ericsson) provides r01. There is no consensus yet on the EAC flag.
Jinguo(ZTE) suggest to move 7.2.x(new) into 5743
George (Ericsson) provides comment. The merge will be in 5713 r01.
Haiyang (Huawei) is OK to use 5713 r01 as baseline.
Jinguo(ZTE) is ok to use 5713 as basis
Haiyang (Huawei) provides r03.
George Foti (Ericsson) provides comment. I don't see this service defined in 23.502. Looks like a mistake in r03.
Haiyang (Huawei) clarifies to George(Ericsson).
Srisakul (NTT DOCOMO) provides comment on r03.
George (Ericsson) provides comment. I see the Nnef service, so thats good. I also agree that the SMF needs to consider the SMF ++ PGW-C.
Iskren (NEC)provides rev.4
George (Ericsson) provides rev.5. Added Ericsson as cosigned and added SMF + PGW-C
Jinhua(Xiaomi) provides r06, update of SMF+PGW-C for UEs counting with EPC interworking
Hyunsook (LGE) provides r07 with update of cover page
Haiyang (Huawei) provides r08 with editorials .
Yifan (China Telecom) is ok to use 5713 as baseline.
Gerald (Matrixx) provides rev09 with correct references at AMF/SMF
Ashok (Samsung) provides r10 and cosigned the paper
Jinguo(ZTE) provides r11 to add China Telecom as cosigner
==== 8.X, 9.X Revisions Deadline ====
Hyunsook (LGE) is OK with r11
George (Ericsson) is OK with r11.
Haiyang (Huawei) is OK with r11 .
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106848 CR Approval 23.501 CR3066R1 (Rel-17, 'F'): Addition of NSACF services Huawei, HiSilicon, ZTE, NEC, Ericsson, Xiaomi, LG Electronics, Matrixx,Samsung, China Telecom Rel-17 Revision of S2-2105713r11, merging S2-2105487, S2-2105743 and S2-2105973. Approved Agreed
8.4 S2-2105973 CR Approval 23.501 CR3120 (Rel-17, 'F'): Adding NSACF services in Network Function Services China Telecom Rel-17 Merged into S2-2106848 George Foti (Ericsson) proposes to note this CR and to merge in 5713
Jinguo (ZTE) suggest to merge in 5743 instead of 5713
Jinhua(Xiaomi) propose to update service including NumberOfPDUsPerSlice, and merge 5973 into 5743 for discussion.
Yifan (China Telecom) agrees to merge into S2-2105743.
Yifan (China Telecom) prefers to merge into S2-2105743.
George (Ericsson) objects. S2-2105743 is incomplete and missing things in 5713. Please read.
Iskren (NEC) comments.
Jinhua (Xiaomi) propose to merge 5973 into 5713(with the agreement achieved).
Yifan (China Telecom) agrees to merge into 5713.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105427 CR Approval 23.501 CR3015 (Rel-17, 'F'): KI#2 PDU Sessions subject to NSAC functional description alignment. Ericsson Rel-17 Noted Jinguo(ZTE) provides comments and propose to note it, see comments in 5429
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105431 CR Approval 23.502 CR2909 (Rel-17, 'B'): KI#2_Support-For-Accurate-Count-for-MaxPDUSessions Ericsson Rel-17 r06 agreed. Revised to S2-2106849, merging S2-2106189 and S2-2106297 Jinguo(ZTE) suggest to use 5431 as basis
Hoyeon (Samsung) is OK to use 5431 as a baseline and provides r01.
Fenqin (Huawei ) comments
George (Ericsson) provides r02 to handle that scenario which is valid.
Ashok (Samsung) comments
Jinguo(ZTE) comments
Ashok ( Samsung) responds to Jinguo
Jinguo(ZTE) responds to Ashok ( Samsung)
George (Ericsson) provides a response. Ashok adequately addressed all issues and he is correct on all the points. Everything is covered in this CR. There is nothing missing. I did go through 23.501.
George (Ericsson) provides a response to Jinguo
Jinguo(ZTE) replies, object r02, can live with r01
George (Ericsson) responds. The statement is incoherent. Whether a new or an old SMF is chosen makes no difference. It works either case, as the old or the new SMF has all the needed information. The AMF sends it. It is mandatory in 23.501. Please read. This was the initial complaint. Now U moved to say that this PDU session is not needed. That's a different complaint. Lets see if U are alone
George (Ericsson) provides r03. It states clearly that the SMF anchoring the old PDU session does not interact with NSACF when it tears down the old PDU session in support of SSC mode 3.
Fenqin (Huawei) provides a response
Ashok (Samsung) responds to Fenqin
Fenqin (Huawei) comments
Jinguo(ZTE) agree with Fenqin and Ashok.
George (Ericsson) comments.
George (Ericsson) provides r04. Added a note to mention the 2 SMF scenario.
Jinguo(ZTE) responds to George (Ericsson) on two SMFs case
George (Ericsson) see below.
Fenqin (Huawei ) comments.
George (Ericsson) comments. The new SMF will know the old PDU session ID. So it knows that this is for SSC mode 3. SO I don't understand when U say there will be 2 PDU session established. The difference is that the UE sends the old PDU session ID to the new SMF. The AMF is not involved. The SCC mode 3 has to work the same way whether a new SMF or the same SMF is involved. In either case, the old PDU session is conveyed.
George (Ericsson) makes a comment. After discussing indeed if 2 SMFs are selected, new SMF does not receive the old PDU session IS This means that r03 is correct, please ignore r04.
Jinguo(ZTE) provides r05.
George (Ericsson) provides a comment. We can accept r03 or r05
Fenqin (Huawei ) ask the value of this paper.
George (Ericsson) there is a lot more added. Please see r05
Fenqin (Huawei ) provides r06.
George (Ericsson) r03 or accepts r05. This is normative behavior anyway. Putting it in a note does not even make sense. It is self-contradictory.
Fenqin (Huawei ) object r03.
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei ) suggest to go with r06 and object any previous version.
George (Ericsson) can live with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106849 CR Approval 23.502 CR2909R1 (Rel-17, 'B'): KI#2_Support-For-Accurate-Count-for-MaxPDUSessions Ericsson Rel-17 Revision of S2-2105431r06, merging S2-2106189 and S2-2106297. Approved Agreed
8.4 S2-2106007 CR Approval 23.502 CR3027 (Rel-17, 'B'): Admission control accuracy Samsung Rel-17 Noted George Foti (Ericsson) provides comments. If there is consensus I can add it to 5431 and we can note this CR.
Hoyeon (Samsung) proposes to merge this paper (6007) into 5431.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) please note the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2105591 CR Approval 23.502 CR2943 (Rel-17, 'F'): Aligning TR conclusion of adding back-off timer to KI#2 Samsung Rel-17 Approved Kundan (NEC)provides comments and seeking some clarification
Ashok (Samsung) clarifies to Kundan (NEC)
Kundan (NEC) thanks Ashok (Samsung)for providing the clarification.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2106297 CR Approval 23.502 CR3086 (Rel-17, 'F'): Resolve EN on AMF interacting with NSACF for NSAC in terms of number of PDU Sessions NTT DOCOMO Rel-17 Merged into S2-2106849 George Foti (Ericsson) proposes to note the CR. This is merged in 5431.
Srisakul (NTT DOCOMO) ok to merge 6297 into 5431. Use 5431 as a baseline document.
Srisakul (NTT DOCOMO) asks to keep this one opened, since discussions of 5431 may end up with no consensus. If 5431 can be agreed, we can merge this one into 5431.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105601 CR Approval 23.502 CR2944 (Rel-17, 'F'): NSAC procedure in planned AMF removal case Samsung Rel-17 Postponed George Foti (Ericsson) proposes to note the CR Please see comments
Ashok (Samsung) replies to George Foti (Ericsson)
Jinguo (ZTE) comments
George Foti (Ericsson) provides comments
Ashok (Samsung) explains to George
George (Ericsson) provides a response. Seems to me that this section reinforces the no need to do anything else, as the planned AMF does do it in a gradual fashion. So I don't see any need for anything else.
Ashok (Samsung) does not agree with George and explain how the AMF planned removal scenario has impact to NSAC feature
George (Foti) provides a response in line.
Iskren (NEC) comments.
George (Ericsson) would like to point out that this was not in the exception from last meeting. Quite frankly, as a general comment, most of the normative text we have was not even in the TR. This should not have been allowed. So we end up debating solution merits in the wrong time and place; EAC is one of these thorny things which was invented in the normative phase.
Ashok (Samsung) replies to Iskren and George
George (Ericsson) provides a response. This was not in the exception sheet. We have to have the chance to evaluate proposals. We cannot every meeting think about new capabilities and start introducing them. This is not critical and can wait to Release 18.
Ashok (Samsung) provides r01
Jinguo(ZTE) comments
George (Ericsson) objects to the CR.
Ashok (Samsung) provides comments
George (Ericsson) provides comments. U misunderstood one of my comments
Ashok (Samsung) replies to George (Ericsson)
George (Ericsson) The fact that it is technically correct does not mean we should agree to it given that we never discussed this before. The purpose of a study is to allow solutions, and they are usually all correct, to be compared. Doing things in normative phase is not how the process is intended to work.
Ashok (Samsung) agrees with George.
Iskren (NEC) proposes to postpone this CR for Rel-18.
Ashok (Samsung) responds to Iskren
Iskren (NEC) objects to all versions of this CR, see comments.
Ashok (Samsung) agrees to postpone it
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2106248 CR Approval 23.502 CR3071 (Rel-17, 'F'): Correction of NSACF service with AF consumer Xiaomi Rel-17 r03 agreed. Revised to S2-2106850 George Foti (Ericsson) objects to the CR. The AF can subscribe through the NEF, but not directly.
Jinhua(Xiaomi) reply to George Foti (Ericsson) for clarification.
George (Ericsson). The clarification need is to add a note stating that an AF can subscribe through a NEF. We should not allow direct interaction with the NSACF
Ashok (Samsung) comments that if AF is belongs to operator domain and trusted (not third party) it can directly contact NF
George (Ericsson). Comments. That's Ok as well.
Jinhua(Xiaomi) reply to Ashok (Samsung) and George (Ericsson).
Srisakul (NTT DOCOMO). Comments and provide r01.
George (Ericsson) provides a comment. Please add a note to the AF to state that the AF can either via NEF in case of untrusted AF or directly to NSACF in case of trusted AF
Jinhua (Xiaomi) reply to George and provides r02.
George (Ericsson) provides comment.
Jinhua(Xiaomi) reply to Srisakul (NTT DOCOMO), update the 2nd Change with AF via NEF.
Iskren (NEC) suggests to note this CR. Now it is just a Note that is not needed.
Jinhua(Xiaomi) reply to Iskren (NEC), It's not about the note, the CR update the NSAC consumer with AF, then add the note to clarify the use case of AF and NEF.
Jinhua(Xiaomi) reply to George (Ericsson) with r03.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) oK with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106850 CR Approval 23.502 CR3071R1 (Rel-17, 'F'): Correction of NSACF service with AF consumer Xiaomi Rel-17 Revision of S2-2106248r03. Approved Agreed
8.4 S2-2106250 CR Approval 23.502 CR3072 (Rel-17, 'F'): Update of NSACF Report Information and Event Trigger Xiaomi Rel-17 r01 agreed. Revised to S2-2106851 George Foti (Ericsson) provides comments r01. Clean up
Jinhua(Xiaomi) reply to George Foti (Ericsson), r01 is fine, thanks for the correction.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106851 CR Approval 23.502 CR3072R1 (Rel-17, 'F'): Update of NSACF Report Information and Event Trigger Xiaomi Rel-17 Revision of S2-2106250r01. Approved Agreed
8.4 - - - KI#3 - - Docs:=4 -
8.4 S2-2105745 CR Approval 23.503 CR0626 (Rel-17, 'F'): KI#3 Subscribed UE-Slice-MBR in PDU Session policy control subscription ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105746 CR Approval 23.501 CR3072 (Rel-17, 'F'): KI#5 UE-Slice-MBR enforcement in PCF ZTE Rel-17 r02 agreed. Revised to S2-2106852 Mirko (Huawei) comments and provides r01.
Jinhua(Xiaomi) provides comments r02. Clean up
Jinguo(ZTE) is fine with r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106852 CR Approval 23.501 CR3072R1 (Rel-17, 'F'): KI#5 UE-Slice-MBR enforcement in PCF ZTE Rel-17 Revision of S2-2105746r02. Approved Agreed
8.4 S2-2106508 CR Approval 23.501 CR3232 (Rel-17, 'F'): Clarification on S-NSSAI mapping China Telecom Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 - - - KI#5 - - Docs:=12 -
8.4 S2-2105423 CR Approval 23.503 CR0608 (Rel-17, 'B'): KI#5 - Monitoring Remaining Data Rate per S-NSSAI Ericsson Rel-17 r05 agreed. Revised to S2-2106853, merging S2-2105748 and S2-2106249 Jinguo(ZTE) suggest to merge this paper into 5748
Belen (Ericsson) is okay to merge into 5748
Belen (Ericsson) asks Jinguo not to add Ericsson as cosigner yet.
Mirko (Huawei) provides r01 and suggests to instead merge 5748 into this CR.
Belen (Ericsson) is okay with r01.
Jinguo (ZTE) provides r02
Mirko (Huawei) provides r03.
Jinguo(ZTE) is fine with r03
Jinhua(Xiaomi) provides r04, clean up and cosign to support it.
nokia provides r05
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) asks Tao(VC) to change the status of 5423. We should approve 5423r05
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106853 CR Approval 23.503 CR0608R1 (Rel-17, 'B'): KI#5 - Monitoring Remaining Data Rate per S-NSSAI Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell, Xiaomi Rel-17 Revision of S2-2105423r05, merging S2-2105748 and S2-2106249. Approved Agreed
8.4 S2-2105748 CR Approval 23.503 CR0628 (Rel-17, 'B'): KI#5 - Monitoring Remaining Data Rate per S-NSSAI ZTE, Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106853 Jinhua(Xiaomi) provide r01 , update with 6249 merged in.
Mirko (Huawei) questions that the proposed mechanism can work.
Jinguo(ZTE) responds to Mirko(Huawei)
Mirko (Huawei) responds.
Belen (Ericsson) provides r02.
Jinguo(ZTE) responds.
Belen (Ericsson) is okay with adding a note or similar
Jinguo(ZTE) has a proposal
Belen (Ericsson) replies
Belen (Ericsson) provides r04
Jinguo (ZTE) responds to Mirko(Huawei)
Mirko (Huawei) responds and proposes to merge 5748 into 5423.
Jinhua(Xiaomi) provides r05, update terminology to keep align with 5928, and clarification about clause 6.2.1.10.
Belen (Ericsson) is okay to merge 5748 into 5423.
Jinguo (ZTE) is okay to merge 5748 into 5423.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2105749 CR Approval 23.503 CR0629 (Rel-17, 'B'): KI#5-Policy control for data rate per network slice with assistance of the NWDAF ZTE, Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2106854 Jinhua(Xiaomi) provide comments for multiple PCFs and Network Slice Specific Control Data clarification
Mirko (Huawei) provides r01.
Jinguo(ZTE) provides r02
Jinguo(ZTE) provides r03 to remove the second change. This has been captured in 5928
Jinhua(Xiaomi) response to Jinguo, fine with the clarification, provides r04 with clean up and cosign it.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106854 CR Approval 23.503 CR0629R1 (Rel-17, 'B'): KI#5-Policy control for data rate per network slice with assistance of the NWDAF ZTE, Nokia, Nokia Shanghai Bell, Huawei, Xiaomi Rel-17 Revision of S2-2105749r04. Approved Agreed
8.4 S2-2105928 CR Approval 23.503 CR0633 (Rel-17, 'F'): Clarifications for slice related policy control Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106855, merging S2-2106251 Jinguo(ZTE) provides comments.
Alessio(Nokia) also is not happy to approve this paper
Mirko (Huawei) responds to the comments.
Jinhua(Xiaomi) provides comments.
Jinguo (ZTE) responds.
Mirko (Huawei) provides r01.
Mirko (Huawei) provides r02.
Jinhua(Xiaomi) provides comments about clause 6.2.1.3.
Mirko (Huawei) provides r03.
Jinguo(ZTE) provides r04.
Mirko (Huawei) responds.
Alessio(Nokia) is ok with r04 provided by ZTE
Mirko (Huawei) provides r05.
Jinguo (ZTE) provides r06 to add cosigner.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106855 CR Approval 23.503 CR0633R1 (Rel-17, 'F'): Clarifications for slice related policy control Huawei, HiSilicon, Xiaomi, ZTE Rel-17 Revision of S2-2105928r06, merging S2-2106251. Approved Agreed
8.4 S2-2106154 CR Approval 23.502 CR3044 (Rel-17, 'F'): Correction on the Data Subset for Slice-MBR Huawei, HiSilicon Rel-17 Merged into S2-2106856 Jinguo(ZTE) suggest to merge this paper into 6288
Haiyang(Huawei) is OK to merge this paper into 6288
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106249 CR Approval 23.503 CR0643 (Rel-17, 'F'): Correction of Remaining Data Rate Xiaomi Rel-17 Merged into S2-2106853 Jinguo(ZTE) suggest to merge this paper into 5748
Jinhua(Xiaomi) reply to Jinguo(ZTE) , merge 6249 into 5748 is fine with me.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106251 CR Approval 23.503 CR0644 (Rel-17, 'B'): Resolve the Editor's Note on Policy Control for Data Rate per Network Slice Xiaomi Rel-17 Merged into S2-2106855 Jinguo(ZTE) suggest to merge this paper into 5928
Jinhua(Xiaomi) reply to Jinguo(ZTE) , merge 6251 into 5928 is fine with me.
Mirko (Huawei) responds.
Jinhua(Xiaomi) responds to Mirko (Huawei), merge 6251 into 5928 with text the usage of a single PCF for all PDU Sessions of an S-NSSAI as a configuration scenario is fine.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106288 CR Approval 23.502 CR3084 (Rel-17, 'F'): KI#5 Correction on Data subset name for Network Slice Specific Control Data ZTE Rel-17 r01 agreed. Revised to S2-2106856, merging S2-2106154 Jinguo(ZTE) provides r01, add Huawei as cosource company
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106856 CR Approval 23.502 CR3084R1 (Rel-17, 'F'): KI#5 Correction on Data subset name for Network Slice Specific Control Data ZTE, Huawei Rel-17 Revision of S2-2106288r01, merging S2-2106154. Approved Agreed
8.4 - - - KI#6 - - Docs:=18 -
8.4 S2-2105311 CR Approval 23.501 CR2994 (Rel-17, 'F'): Correction to the re-configuration requirements for NSSRG non-supporting UEs Nokia Nokia Shanghai Bell, Telecom Italia Rel-17 r05 agreed. Revised to S2-2106857, merging S2-2106188 Yunjing(CATT) provides r01 to merge S2-2106188.
alessio(Nokia) provides R02 to further implement the concepts by CATT.
George (Ericsson) provides r03. We object to r01, and ro2. The only acceptable change is the 5GMM change. The rest changes the previous agreement and is removed in r03.
Alessio(nokia) proposes this goes to CC#3 as the change is correct and Ericsson is not providing the rationale why it is wrong..
Alessio(Nokia) Objects to r03
George (Ericsson) provides r04.
Yunjing (CATT) asks a question for clarification.
George (Ericsson) provides an answer. Yes, this is clear from the whole section. This is about backward compatibility. The added text breaks this.
Yunjing(CATT) is ok with r04.
Patrice (Huawei) objects to r00-r02, r04, provides r05 with a number of corrections (incl. editorial).
George (Ericsson) is OK with r05
==== 8.X, 9.X Revisions Deadline ====
Ashok (Samsung) need clarification from Alessio
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106857 CR Approval 23.501 CR2994R1 (Rel-17, 'F'): Correction to the re-configuration requirements for NSSRG non-supporting UEs Nokia Nokia Shanghai Bell, Telecom Italia, CATT Rel-17 Revision of S2-2105311r05, merging S2-2106188. Approved Agreed
8.4 S2-2105313 CR Approval 23.502 CR2883 (Rel-17, 'F'): Clarification on NSSRG info sent to NSSF Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105315 CR Approval 23.502 CR2884 (Rel-17, 'F'): Clarification on the interaction of the AMF with NSSF when NSSRG information is provided by UDM Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106858 George Foti (Ericsson) objects to the CR
Patrice (Huawei) concurs that a revision is needed at least.
alessio(Nokia) comments that George may have misunderstood what we propose
George Foti (Ericsson) provides comments. So is this just an editorial CR ?
alessio(nokia) replies to George Foti (Ericsson) this in NOT just an editorial CR, as it clarifies the NSSRG info is sent to NSSF irrespective of UE support of NSSRG. the support indication by UE is added by another CR as indicated.
George Foti (Ericsson) maintain objection. Why do U want the NSSRG info to the NSSF if the UE does not support that. ?
Alessio(Nokia) notes the reason for change explains that and that I have already said in this thread that the NSSF MUST consider the NSSRG as 'we say we always send the NSSRG info to NSSF even if the UE does not support the feature so we always avoid allowing incompatible slices and also to detect misconfigurations of the UE when it is network policy to always provide only compatible S-NSSAIs to non-supporting UEs.'
George Foti (Ericsson) responds. This means that legacy UEs will not receive their Subscribed Slices even if they cant be used simultaneously as is the case today. Ur change remove such a capability for good.
Alessio(Nokia) responds the all the subscribed slices can be given to the UE in the configured NSSAI (subject to the UDM indication) but the AMF and NSSF cannot provide together slices that are constrained to not be used together based on NSSRG... this is already agreed. a further CR provides the indication of support to NSSF to implement the right logic.
Patrice (Huawei) provides r01, including important missing information from the CR. r00 cannot be approved.
George Foti (Ericsson) accepts r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106858 CR Approval 23.502 CR2884R1 (Rel-17, 'F'): Clarification on the interaction of the AMF with NSSF when NSSRG information is provided by UDM Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105315r01. Approved Agreed
8.4 S2-2105316 CR Approval 23.501 CR2995 (Rel-17, 'F'): Clarification on obtaining the Configured NSSAI from NSSF when NSSRG for UE changes Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2105319 CR Approval 23.502 CR2887 (Rel-17, 'D'): Editorial CR on NSSRG related aspects Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2106859 Haiyang (Huawei) provides r01.
Alessio (Nokia) provides r02 adding back the second clause changes that for some reason were accepted!
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) OK with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106859 CR Approval 23.502 CR2887R1 (Rel-17, 'D'): Editorial CR on NSSRG related aspects Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105319r02. Approved Agreed
8.4 S2-2105320 CR Approval 23.502 CR2888 (Rel-17, 'F'): Missing indication of UE support of NSSRG functionality in NSSF services Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106860 Patrice (Huawei) provides r01 adding the UDM indication in the request to the NSSF, otherwise the NSSF cannot decide what to send back in Configured NSSAI. r00 cannot be approved.
George Foti (Ericsson) supports r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106860 CR Approval 23.502 CR2888R1 (Rel-17, 'F'): Missing indication of UE support of NSSRG functionality in NSSF services Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105320r01. Approved Agreed
8.4 S2-2106158 CR Approval 23.502 CR3046 (Rel-17, 'F'): NSSRG information in the UE context of AMF Huawei, HiSilicon Rel-17 Noted Ashok (Samsung) supports the proposal and propose to merge S2-2106190
Yunjing (CATT) is ok to merge and thinks the proposal in S2-2105311 is also a possible way to go.
George (Ericsson) provide comment. There is a competing proposal in 5311 to move this to 5GMM.
Alessio(Nokia) confirms that the Nokia CR in S2-2105311 places this indication in the 5G MM info in the UE context as George (Ericsson) suggested. We do not need to keep this separate from 5GMM info. so we do not agree to approve this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106188 CR Approval 23.501 CR3166 (Rel-17, 'F'): Clarification of the subscription-based restrictions to simultaneous registration of network slices feature CATT Rel-17 Merged into S2-2106857 Jinguo(ZTE) suggest to merge this paper into 5311
Alessio(Nokia) proposes to merge this paper in 5311 also
Yunjing (CATT) is ok to merge this paper in 5311.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2106190 CR Approval 23.502 CR3056 (Rel-17, 'F'): Update the UE context in AMF CATT Rel-17 r01 agreed. Revised to S2-2106861 alessio(Nokia) proposes to note this CR as the way forward is to include this in 5GMM capabilities and this is already in the UE context.
Yunjing (CATT) is ok to update 5GMM capabilities and provides r01 to reflect the discussion in 5311.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) comments
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106861 CR Approval 23.502 CR3056R1 (Rel-17, 'F'): Update the UE context in AMF CATT Rel-17 Revision of S2-2106190r01. Approved Agreed
8.4 S2-2106380 DISCUSSION Agreement DISC NSSRG procedure when the UE performs registration via both accesses. NEC Rel-17 Noted Jinhua(Xiaomi) proposes to note the CR. It is discussed in 6384, 6386 and 6341.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106384 CR Approval 23.501 CR3205 (Rel-17, 'F'): NSSRG procedure when the UE is registered to same PLMN via 3GPP access and non-3GPP access NEC Rel-17 Postponed George Foti (Ericsson) provides r01. All what we need is a note.
Kundan (NEC) provides response to George.
George (Ericsson) provides a response..
Patrice (Huawei) objects to the original CR as well as the revisions.
Kundan (NEC) seeking clarifications from Patric(Huawei).
Alessio(Nokia) provides r02 and clarifies that the GSMA expectation is that the simultaneous use is constrained so this has to be across any access type.
Kundan(NEC) is fine with r02 provided by Alessio.
Yunjing (CATT) asks a question for clarification.
Kundan (NEC) provide response to Yunjing.
Yunjing (CATT) replies to Kundan (NEC).
Patrice (Huawei) confirms his objection, including r00-r02, provides r03 to include the proper resolution of this matter.
Kundan (NES) replies to Yunjing (NEC). Hope my response clarifies your concern.
Kundan (NEC) clarifies with Patrice.
Alessio(Nokia) Nokia Objects to r03 as this violates the simultaneous use policy ! if you use simultaneously slices A and B which hare no NSSRG value over two accesses with same UE, the UE is using them simultaneously!!! this violates GSMA requirement. NSSRG is at UE level. by the way we do not have a subscribed S-NSSAI per access type! NSSRG applies to the subscription not to the access type! so we retain proceeding with r02. let's discuss in CC#4 if this is not resolved here.
Kundan (NEC) has same understanding as Alessio (Nokia). We propose to discuss this in CC#4.
George (Ericsson) Comments. While I agree with what Alessio says, the text in r02 only considers UE supporting NSSRG, and this is why it is not complete. Patrice tried to complete it. But the text may need more work. I think we all says the same thing bit no revision captures everything. R03 can be extended to add expectation for NSSRR which gives Alessio what he wants. There is time. Otherwise, we will reject all
Alessio(Nokia) thinks clearly only UEs that handle NSSRG can do anything about it. so r02 is ok. I do not think we can continue with the Ericsson and Huawei myth that NSSRG compatibility enforcement can work in UEs that do not support NSSRG (if we still needed further proof of it, we found it).
Kundan (NEC) seeks clarification from George.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2106386 CR Approval 23.501 CR3206 (Rel-17, 'F'): NSSRG procedure when the UE is registered to two different PLMNs NEC Rel-17 Noted George Foti (Ericsson) proposes to note the CR. I don't think we need to say anything here. This is clearly obvious. At most a note is all what is needed.
Kundan (NEC) provides response to George.
George Foti (Ericsson) provides a response.
Patrice (Huawei) objects to the CR.
Alessio(Nokia) concurs we should not allow a UE to request incompatible slices over same or different accesses or PLMNs. so this is not a good way to document the topic. proposes to note.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2106411 CR Approval 23.502 CR3102 (Rel-17, 'F'): AMF relocation in connected state (NSSRG) NEC Rel-17 Postponed George Foti (Ericsson) provides comments. This CR has nothing to do with this WI.
Jinguo(ZTE) provides comments
Kundan (NEC) clarifies with George.
Kundan(ENC) further clarifies with Jinguo (ZTE)
Jinguo(ZTE) responses
Kundan(NEC) further clarifies with Jinguo (ZTE).
Jinguo(ZTE) response to Kundan(NEC)
George (Ericsson) comments. I see nothing about NSSRG in the text U added. The added text seems to be generic change. So I don understand what we are trying to solve here.
Alessio(Nokia) provides r01 andcomments that this CR is valid but not in the scope of eNS_Ph2 (in fact the author did not include its WI code either!). If we understand the CR, it is about a UE that is in connected mode and the UE requests a new set of slices via a MRU. this behavior is allowed in our view. however the clause 4.2.2.2.3 is only for Initial Registration (from Idle) despite the intro to the clause says differently! This should be actually on CC#2 as the CR itself is not for this AI.
Kundan (NEC) is fine with the r01 provided by Alessio.
Kundan (NEC) is provides r02 which fixes minor editorial error.
Jinguo(ZTE) suggest to postpone this paper
alessio(Nokia) does not think it is questionable a UE can change the sillies set in connected mode... it is allowed by the specs. this may imply change of AMF indeed.
alessio(Nokia) please use this corrected comment : Alessio(Nokia) does not think it is questionable a UE can change the slices set in connected mode... it is allowed by the specs. this may imply change of AMF indeed.
Kundan(NEC) responds to Jinguo questions.
Jinguo(ZTE) responds.
Kundan (NEC) provides responds to Ginguo.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 - - - KI#7 - - Docs:=10 -
8.4 S2-2105322 CR Approval 23.501 CR2996 (Rel-17, 'F'): Alignment with RAN conclusion on providing Configured NSSAI to the RAN Nokia, Nokia Shanghai Bell, Convida Wireless LLC Rel-17 CC#4: Postponed Peter (Ericsson) provides comments and suggest to keep CR open until LS received from Ran2 and RAN3
Stefano (Qualcomm) supports Ericsson's proposal to keep CR open until LS received from Ran2 and RAN3
Susan (Huawei) Similar view as Peter and Stefano to keep this CR open until LS received from RAN2 and RAN3.
alessio(Nokia) replies and asks this to be marked for special handling as it may need update after revision deadline if the reply is coming later than that.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) agree to keep CR open, awaiting LS from RAN3
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2105339 CR Approval 23.501 CR3004 (Rel-17, 'F'): Missing Definition of Target NSSAI Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2106862 Peter (Ericsson) provides comments
Alessio(Nokia) provides reply to Peter (Ericsson) comments
Peter Hedman (Ericsson) provides r01
Alessio(nokia) replies we would like to proceed with r0 as r01 is not changing parts we need also to fix.
Alessio (nokia) provides r02
Alessio (nokia) provides r03 based on further feedback received on the quality of the existing allowed NSSAI definition and related suggestions for improvement
Peter Hedman (Ericsson) provides r04 and question why we need to change SDF filter definition
alessio(Nokia) is OK with r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106862 CR Approval 23.501 CR3004R1 (Rel-17, 'F'): Missing Definition of Target NSSAI Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2105339r04. Approved Agreed
8.4 S2-2105716 CR Approval 23.501 CR3067 (Rel-17, 'F'): Redirection to dedicated frequency band(s) at the end of NSSAA Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106863 Peter (Ericsson) provides comments
alessio(Nokia) provides r01
Haiyang(Huawei) clarifies and provides r02
Peter Hedman (Ericsson) provides question
Peter Hedman (Ericsson) provides r03
alessio(NOKIA) can accept r04.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) objects to r04 and can only accept r03
Haiyang(Huawei) can accept r03.
Jinguo(ZTE) comments the cover page should be correct
Haiyang(Huawei) responds.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106863 CR Approval 23.501 CR3067R1 (Rel-17, 'F'): Redirection to dedicated frequency band(s) at the end of NSSAA Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2105716r03. Approved Agreed
8.4 S2-2105717 CR Approval 23.502 CR2964 (Rel-17, 'F'): Redirection to dedicated frequency band(s) at the end of NSSAA Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106864 Peter (Ericsson) provides comments and r01
Iskren (NEC) provides r02
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r02 (or r01)
Haiyang(Huawei) is ok with r02
Jinguo(ZTE) comments that the cover page should be updated
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106864 CR Approval 23.502 CR2964R1 (Rel-17, 'F'): Redirection to dedicated frequency band(s) at the end of NSSAA Huawei, HiSilicon, Ericsson, NEC Rel-17 Revision of S2-2105717r02. Approved Agreed
8.4 S2-2105718 CR Approval 23.503 CR0622 (Rel-17, 'F'): Change of the Target NSSAI Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106865 alessio(Nokia) Based on our analysis this CR is not needed
Haiyang(Huawei) clarifies to alessio(Nokia)
alessio(Nokia)Would not agree to approving this CR as it changes the target NSSAI into something that needs to be maintained like the Allowed NSSAI.
Haiyang(Huawei) provides r01
Alessio(Nokia) provides r02
==== 8.X, 9.X Revisions Deadline ====
Haiyang(Huawei) is OK with r02
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2106865 CR Approval 23.503 CR0622R1 (Rel-17, 'F'): Change of the Target NSSAI Huawei, HiSilicon Rel-17 Revision of S2-2105718r02. Approved Agreed
8.4 S2-2105838 CR Approval 23.501 CR3099 (Rel-17, 'F'): Whether 5GC is to provide additional information to NG-RAN for enhancing RRM logic Ericsson Rel-17 CC#4: Postponed Peter (Ericsson) provides comments and suggest that this CR is kept open as well - waiting for RAN WGs LSes
Alessio(Nokia) requests to put this on hold till a LS is received from RAN2/3 on what to do.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) propose to keep this CR open until the end of this week. We still need response from RAN3.
Tao(VC) can this be clear way forward? Can LS IN S2-2105371 help on this
Peter Hedman (Ericsson) agree to keep CR open, awaiting LS from RAN3
Hoyeon (Samsung) also agrees to keep 5322 and 5838 open. RAN3 feedback is also needed to make a progress.
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=86 -
8.5 - - - LS In - - Docs:=5 -
8.5 S2-2105234 LS In Action LS from SA WG4: Reply LS to SA2 on hold and forward buffer support for VIAPA services SA WG4 (S4-210619) Revision of postponed S2-2103738 from S2-145E. Noted zhendong(ZTE), propose to Note this LS
Sang-Jun (Samsung) also proposes to Note this LS
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2105245 LS In Action LS from SA WG1: LS Response on hold and forward buffer support for VIAPA services SA WG1 (S1-211324) Rel-17 Revision of postponed S2-2105095 from S2-145E. Noted zhendong(ZTE), propose to Note this LS
Sang-Jun (Samsung) also proposes to Note this LS
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2105244 LS In Information LS from SMPTE 32NF Technology Committee: PTP device monitoring Public Committee Draft SMPTE 32NF Technology Committee (SLC04-smpte-to-3GPP-PCD-RP2059-15-2021-04-2) Revision of postponed S2-2104791 from S2-145E. Noted Shabnam (Ericsson) provides comments that same LS is duplicated in 5364 under AI 4.1 and comments ongoing so we can either withdraw or give whatever status is appropriate for duplicate document.
Qianghua (Huawei) proposes to note this, there is a duplicated LS in 4.1: S2-2105364
Sang-Jun (Samsung) also propose to note the LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2105273 LS In Action LS from RAN WG2: Reply LS on Time Synchronization assistance parameters RAN WG2 (R2-2106560) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2105362 LS In Information LS from IEEE: RE: LS on Time Synchronization IEEE (reply to 3GPP liaison time sync) Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 - - - General Arch - - Docs:=15 -
8.5 S2-2105498 CR Approval 23.502 CR2924 (Rel-17, 'F'): Trusted AF notify or response directly from PCF or TSCTSF Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2105562 CR Approval 23.501 CR3040 (Rel-17, 'F'): Architecture to enable Time Sensitive Communication and Time Synchronization Nokia, Nokia Shangai Bell Rel-17 r02 agreed. Revised to S2-2106760 Sebastian (Qualcomm) provides r01
Devaki (Nokia) replies.
Shabnam (Ericsson) also supports r01.
Qianghua (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106760 CR Approval 23.501 CR3040R1 (Rel-17, 'F'): Architecture to enable Time Sensitive Communication and Time Synchronization Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105562r02. Approved Agreed
8.5 S2-2105565 CR Approval 23.503 CR0615 (Rel-17, 'F'): Updates for TSC text - policy specification Nokia, Nokia Shangai Bell Rel-17 r04 agreed. Revised to S2-2106761 Qianghua (Huawei) provides r01
Mirko (Huawei) proposes to merge this CR into S2-2106167 (or to resolve the overlap for clause 6.1.3.18).
Devaki (Nokia) provides r02.
Qianghua (Huawei) replies
Devaki (Nokia) comments.
Devaki (Nokia) provides r03.
Qianghua (Huawei) provides further comments
Qianghua (Huawei) corrects previous comments
Devaki (Nokia) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) comments that the Chair notes should be corrected to ask if r04 (latest version) can be approved?
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106761 CR Approval 23.503 CR0615R1 (Rel-17, 'F'): Updates for TSC text - policy specification Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105565r04. Approved Agreed
8.5 S2-2105560 CR Approval 23.501 CR3038 (Rel-17, 'F'): TSN AF functional description and reference point Nokia, Nokia Shangai Bell Rel-17 r02 agreed. Revised to S2-2106762 zhendong(ZTE) provides r01,
Qianghua (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106762 CR Approval 23.501 CR3038R1 (Rel-17, 'F'): TSN AF functional description and reference point Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105560r02. Approved Agreed
8.5 S2-2105563 CR Approval 23.501 CR3041 (Rel-17, 'F'): Updates for TSCTSF text - description Nokia, Nokia Shangai Bell Rel-17 r01 agreed. Revised to S2-2106763 Qianghua (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106763 CR Approval 23.501 CR3041R1 (Rel-17, 'F'): Updates for TSCTSF text - description Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105563r01. Approved Agreed
8.5 S2-2105712 CR Approval 23.502 CR2962 (Rel-17, 'F'): Update related services for interaction between TSCTSF and PCF Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2105944 CR Approval 23.501 CR3112 (Rel-17, 'F'): Classification of NEF or TSCTSF Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2106063 CR Approval 23.501 CR3143 (Rel-17, 'F'): Clarify interworking with EPS is not supported for TSC or time synchronization Huawei, HiSilicon Rel-17 Approved Sebastian (Qualcomm) provides r01
Devaki (Nokia) objects to r01 but prefers original version (or even text in the current spec) as it could be misleading that IWK with EPS is supported when UE has TSC PDU session.
Qianghua (Huawei) comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2106064 CR Approval 23.501 CR3144 (Rel-17, 'F'): Granularity of TSCTSF Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106764 Devaki (Nokia) comments.
GYörgy (Ericsson) responds to Nokia and raises questions.
Jari (NTT DOCOMO) responds to György
zhendong(ZTE) wonder if this is needed,
Qianghua (Huawei) replies
Qianghua (Huawei) asks
Jari (NTT DOCOMO) comments
György (Ericsson) comments
György (Ericsson) responds to Nokia.
Jari (NTT DOCOMO) provides r01
Qianghua (Huawei) provides r02 fixing cover page and minor corrections
==== 8.X, 9.X Revisions Deadline ====
Qianghua (Huawei) provides changes on top of r01, if we need to confirm this on CC:
Summary of the change: add 'or stored in UDR after discovery and selection via NRF'
Clauses affected: change 6.3.24 from 4.4.8.3
Change part: Add 'all' before the 'the PDU Session(s) for the given DNN and S-NSSAI are released'
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106764 CR Approval 23.501 CR3144R1 (Rel-17, 'F'): Granularity of TSCTSF Huawei, HiSilicon Rel-17 Revision of S2-2106064r01. Approved Agreed
8.5 S2-2106391 CR Approval 23.502 CR3096 (Rel-17, 'F'): Clarification for 5GS Bridge available event Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 - - - QoS/TSCAI - - Docs:=9 -
8.5 S2-2105499 CR Approval 23.502 CR2925 (Rel-17, 'F'): UE-DS-TT Residence Time and calculation of Required PDB Ericsson Rel-17 r05 agreed. Revised to S2-2106765 Devaki (Nokia) prefers to go with option 2 proposed in this paper.
Sang-Jun (Samsung) also prefers option 2 proposed in this paper.
Jari (NTT DOCOMO) prefers option 1 proposed in this paper.
zhendong(ZTE), propose the option 2 which has been approved in the last meeting
Jari (NTT DOCOMO) responds to zhendong(ZTE)
Qianghua (Huawei) thinks both option 2 and option 3 are needed
György (Ericsson) responds to Jari
György (Ericsson) agrees with Huawei to support options 2 and 3 and provides r01 accordingly.
Jari (NTT DOCOMO) objects r01
Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
György (Ericsson) comments.
György (Ericsson) responds.
Jari (NTT DOCOMO) responds.
zhendong(ZTE), provides the comments
György (Ericsson) responds to Nokia
György (Ericsson) responds to DOCOMO.
Qianghua (Huawei) provides r02
Jari (NTT DOCOMO) provides r03
Qianghua (Huawei) provides comments
György (Ericsson) provides r05. (r04 got corrupted on the server)
Devaki (Nokia) has strong concerns with the latest version.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) ok with r05 in the interest of progress as long as we agree to revisit and remove duplication, especially discovery & selection part from 502 in the next meeting.
Jari (NTT DOCOMO) agrees with r05. Agrees that alignment between 502 and 501 can be done in the next meeting
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106765 CR Approval 23.502 CR2925R1 (Rel-17, 'F'): UE-DS-TT Residence Time and calculation of Required PDB Ericsson, Huawei Rel-17 Revision of S2-2105499r05. Approved Agreed
8.5 S2-2105761 CR Approval 23.503 CR0630 (Rel-17, 'F'): Periodicity handling for the TSC Tencent, CATT Rel-17 Merged into S2-2106778 Qianghua (Huawei) provides r01
Shabnam (Ericsson) objects to original and r01 of the CR, duplication of 23.501 text.
Chunshan (Tencent) proposes this paper to be merged into S2-2106168.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2105929 CR Approval 23.501 CR3107 (Rel-17, 'F'): QoS parameter handling for TSC Huawei, HiSilicon Rel-17 Noted Devaki (Nokia) has strong concerns that this CR (and the related 502/3 CRs) that results in significant re-write of the QoS/TSCAI sections, not limited to corrections.
Mirko (Huawei) responds to Devaki's comments.
Sebastian (Qualcomm) objects to the CR as it is not FASMO
Mirko (Huawei) responds to Sebastian's comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2105930 CR Approval 23.503 CR0634 (Rel-17, 'F'): QoS parameter handling for TSC Huawei, HiSilicon Rel-17 Postponed Sebastian (Qualcomm) objects to the CR as it is not FASMO
Mirko (Huawei) responds to Sebastian's comments.
Shabnam (Ericsson) also has concerns with the changes and would prefer to postpone such restructuring when the content is more stable.
Devaki (Nokia) shares similar concerns as QCOM and Ericsson.
Sang-Jun (Samsung) comments
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) proposes to postpone the CR and discuss the need for restructuring offline (technical concerns provided already).
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2105931 CR Approval 23.502 CR3009 (Rel-17, 'F'): QoS parameter handling for TSC Huawei, HiSilicon Rel-17 Postponed Shabnam (Ericsson) provides comments asking clarification of the changes and questions the need for the proposal.
Mirko (Huawei) responds to the comments and provides r01.
Sebastian (Qualcomm) objects to the CR as it is not FASMO
Mirko (Huawei) responds to Sebastian's comments.
Devaki (Nokia) comments.
Sang-Jun (Samsung) comments.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) proposes to postpone the CR and discuss the need for restructuring offline (technical concerns provided already).
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2106174 CR Approval 23.502 CR3050 (Rel-17, 'B'): KI#3, complete the Ntsctsf_TSCQoSandAssistance service operation ZTE Rel-17 Merged into S2-2106770 Shabnam (Ericsson) provides r01 for editorial fixes.
Sebastian (Qualcomm) provides r02; but also suggests to merge with Nokia CR in 5564
Devaki (Nokia) proposes to merge with 5564 (as also proposed by Zhendong offline).
zhendong(ZTE) is fine to merge this CR into 5564,
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2105605 CR Approval 23.501 CR3051 (Rel-17, 'D'): Correcting the usage of Survival Time Siemens Rel-17 r06 agreed. Revised to S2-2106766 Joachim Walewski (Siemens) announces r01 of this CR. This revision adds Nokia as a source and corrects a spelling error in the second proposed change.
Shabnam (Ericsson) provides r02 and in order for the CR to be Cat D, the table update would not be correct.
Devaki (Nokia) comments.
Sang-Jun (Samsung) provides r03.
Joachim Walewski (Siemens) replies to Sang-Jun (Samsung) and provides r04.
Shabnam (Ericsson) comments on r01, r03 and r04 as not acceptable. Provides r05 as compromise.
Joachim Walewski (Siemens) replies to Shabnam (Ericsson).
Joachim Walewski (Siemens) provides r06.
Shabnam (Ericsson) accepts r06, thanks.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106766 CR Approval 23.501 CR3051R1 (Rel-17, 'D'): Correcting the usage of Survival Time Siemens, Nokia, Ericsson Rel-17 Revision of S2-2105605r06. Approved Agreed
8.5 - - - Management Information exchange - - Docs:=9 -
8.5 S2-2105494 CR Approval 23.501 CR3023 (Rel-17, 'B'): Support for BMCA reporting and improved PTP instance configuration management Intel Rel-17 Noted Yuan Tao (CATT) comments.
Jari (NTT DOCOMO) comments.
zhendong(ZTE), provides the comments
Saso (Intel) replies
zhendong(ZTE), respond to saso
Saso (Intel) replies to zhendong(ZTE)
Sebastian (Qualcomm) objects to the CR
Saso (Intel) replies to Sebastian (Qualcomm)
Saso (Intel) provides r01
Sebastian (Qualcomm) objects to r01
==== 8.X, 9.X Revisions Deadline ====
Saso (Intel) asks a question to Sebastian (Qualcomm)
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2106696 LS OUT Approval [DRAFT] LS on more efficient PMIC/UMIC signalling exchange for time synchronization Intel Rel-17 Created at CC#2. r03 agreed. Revised to S2-2106767 Saso (Intel) provides r00.
Jari (NTT DOCOMO) provides r01.
Saso (Intel) seeks clarification from Jari.
Jari (NTT DOCOMO) responds to Saso
Saso (Intel) replies to Jari.
Shabnam (Ericsson) comments
Sebastian (Qualcomm) comments
Saso (Intel) provides r02.
Saso (Intel) provides r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106767 LS OUT Approval LS on more efficient PMIC/UMIC signalling exchange for time synchronization SA WG2 Rel-17 Revision of S2-2106696r03. Approved Approved
8.5 S2-2105495 CR Approval 23.502 CR2922 (Rel-17, 'F'): Support for BMCA reporting and improved PTP instance configuration management Intel Rel-17 Noted Devaki (Nokia) provides r01
Jari (NTT DOCOMO) comments
Sebastian (Qualcomm) objects to the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2105945 CR Approval 23.501 CR3113 (Rel-17, 'F'): Principle for Handling of PMIC exchange with UE(s) in idle mode Samsung Rel-17 Postponed Qianghua (Huawei) provides comments
Sebastian (Qualcomm) provides r01 to remove the EN
Devaki (Nokia) objects to original version as we don't believe there is a need for paging indication from AF.
Sang-Jun (Samsung) provides r02 and provides responses.
Devaki (Nokia) is fine with r02.
Qianghua (Huawei) still comments
zhendong(ZTE), propose this CR is merged to S2-2105566
György (Ericsson) proposes to go with r01.
zhendong(ZTE) is fine with idea in r01
Devaki (Nokia) comments.
Sang-Jun (Samsung) proposes to go with r02 as Devaki (Nokia)'s comments resolved concerns.
Qianghua (Huawei) our concerns still remain in r00 and r02, so we suggest to go with r01 or merge with 05566.
zhendong(ZTE) similar view with qinaghua, go with r01 or merged with 5566,
György (Ericsson) cannot accept r00 or r02.
==== 8.X, 9.X Revisions Deadline ====
Sang-Jun (Samsung) supports r00 or r02, and cannot accept r01, and also provides r03 as a compromise.
Qianghua (Huawei) still holds concerns
György (Ericsson) objects to r03.
Sang-Jun (Samsung) proposes to postpone the CR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2105946 CR Approval 23.502 CR3014 (Rel-17, 'F'): Procedure for Handling of PMIC exchange with UE(s) in idle mode Samsung Rel-17 Postponed Qianghua (Huawei) proposes to note
Sebastian (Qualcomm) objects to the CR
Shabnam (Ericsson) proposes to Note the CR, aligned with 23.501 proposal (revised).
Sang-Jun (Samsung) provides r01.
Sang-Jun (Samsung) responses to Sebastian (Qualcomm).
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) objects to all versions including the original and provides comments.
Sang-Jun provides response to Shabnam (Ericsson).
Sang-Jun (Samsung) proposes to postpone the CR
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2106172 CR Approval 23.501 CR3162 (Rel-17, 'B'): Clean up on the BMIC and bridge Management Information Container ZTE Rel-17 r01 agreed. Revised to S2-2106768 Qianghua (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) comments that r01 has significantly reduced content and should change the category from B to F?
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106768 CR Approval 23.501 CR3162R1 (Rel-17, 'F'): Clean up on the BMIC and bridge Management Information Container ZTE Rel-17 Revision of S2-2106172r01. Approved Agreed
8.5 S2-2106245 CR Approval 23.501 CR3182 (Rel-17, 'F'): Corrections to TSC Management Information exchange ETRI Rel-17 Merged into S2-2106779 Yoohwa (ETRI) merges 6245 into 6169.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 - - - Time Sync - - Docs:=48 -
8.5 S2-2105561 CR Approval 23.501 CR3039 (Rel-17, 'F'): Updates for time synchronization text - description Nokia, Nokia Shangai Bell Rel-17 r01 agreed. Revised to S2-2106769 Jari (NTT DOCOMO) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106769 CR Approval 23.501 CR3039R1 (Rel-17, 'F'): Updates for time synchronization text - description Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105561r01. Approved Agreed
8.5 S2-2105564 CR Approval 23.502 CR2935 (Rel-17, 'F'): Updates for TSC and time synchronization text - procedure Nokia, Nokia Shangai Bell Rel-17 r03 agreed. Revised to S2-2106770, merging S2-2106174 Jari (NTT DOCOMO) provides r01
Sebastian (Qualcomm) provides r02
Qianghua (Huawei) provides r03
Devaki (Nokia) fine with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106770 CR Approval 23.502 CR2935R1 (Rel-17, 'F'): Updates for TSC and time synchronization text - procedure Nokia, Nokia Shangai Bell, Huawei Rel-17 Revision of S2-2105564r03, merging S2-2106174. Approved Agreed
8.5 S2-2105566 CR Approval 23.501 CR3042 (Rel-17, 'C'): Exposure of Time synchronization as a service - description Nokia, Nokia Shangai Bell, Samsung, Deutsche Telekom, Huawei, HiSilicon, ETRI Rel-17 r10 agreed. Revised to S2-2106771, merging S2-2106343 Saso (Intel) comments and proposes to check the validity of this proposal with RAN1 and RAN4.
Devaki (Nokia) provides r01.
Saso (Intel) provides r02.
Shabnam (Ericsson) our preference is to go with CR in 6343 instead of this one.
Devaki (Nokia) proposes that we use this as a basis and update.
Sang-Jun (Samsung) also proposes to use 5566 as a basis and update.
Sebastian (Qualcomm) objects to r00, r01 and r02; provides r04 (please ignore r03, which was an upload error)
Shabnam (Ericsson) objects to r00, r01 and r02. r03; provides r05
Devaki (Nokia) provides r06 with mainly terminology alignment.
zhendong(ZTE) provides r07,
Devaki (Nokia) provides r08 with fix to the reference as pointed out by Zhendong.
Sebastian (Qualcomm) provides r09
Shabnam (Ericsson) provides r10 moving the text to 23.501 as per Qualcomm comment on 5567 thread
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106771 CR Approval 23.501 CR3042R1 (Rel-17, 'C'): Exposure of Time synchronization as a service - description Nokia, Nokia Shangai Bell, Samsung, Deutsche Telekom, Huawei, HiSilicon, ETRI, Ericsson, ZTE Rel-17 Revision of S2-2105566r10, merging S2-2106343. Approved Agreed
8.5 S2-2105567 CR Approval 23.502 CR2936 (Rel-17, 'C'): Control of the 5G reference time distribution Nokia, Nokia Shangai Bell, Samsung, Huawei, HiSilicon, ETRI Rel-17 r08 agreed. Revised to S2-2106772, merging S2-2105736 and S2-2106344 Jari (NTT DOCOMO) provides r01
Shabnam (Ericsson) has preference to use 6344 as a baseline and asks a question about do we need to pass the information via AM-PCF and AMF or could we reuse TSCAI container and SMF path?
Devaki (Nokia) comments.
zhendong(ZTE) respond the issue raised by ericsson,
Jari (NTT DOCOMO) comments.
zhendong(ZTE), respond
Sebastian (Qualcomm) provides r02
Devaki (Nokia) provides r07.
Shabnam (Ericsson) provides r04 and cosigns, Nokia revision was r03 and not r07.
Devaki (Nokia) confirms that the earlier revision was r03 (not r07, sorry it was a copy/paste error). Ok with r04.
zhendong(ZTE), provides the r05.
Devaki (Nokia) provides r06.
Jari (NTT DOCOMO) provides r07.
Sebastian (Qualcomm) provides r08
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106772 CR Approval 23.502 CR2936R1 (Rel-17, 'C'): Control of the 5G reference time distribution Nokia, Nokia Shangai Bell, Samsung, Huawei, HiSilicon, ETRI, Ericsson, ZTE, NTT DOCOMO Rel-17 Revision of S2-2105567r08, merging S2-2105736 and S2-2106344. Approved Agreed
8.5 S2-2105719 CR Approval 23.502 CR2965 (Rel-17, 'C'): Corrections to the Time Synchronization service procedures NTT DOCOMO Rel-17 r02 agreed. Revised to S2-2106773, merging S2-2105947, S2-2106173 and S2-2106271 Jari (NTT DOCOMO) provides r01
Qianghua (Huawei) provides comments
Jari (NTT DOCOMO) responds to Qianghua
Qianghua (Huawei) comments
zhendong(ZTE) provides r02,
==== 8.X, 9.X Revisions Deadline ====
Sang-Jun (Samsung) is ok with r02, and requests to add Samsung as co-signer.
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106773 CR Approval 23.502 CR2965R1 (Rel-17, 'C'): Corrections to the Time Synchronization service procedures NTT DOCOMO, ZTE, Samsung Rel-17 Revision of S2-2105719r02, merging S2-2105947, S2-2106173 and S2-2106271. Approved Agreed
8.5 S2-2105736 CR Approval 23.502 CR2967 (Rel-17, 'C'): Control of the 5G reference time distribution NTT DOCOMO Rel-17 Merged into S2-2106772 zhendong(ZTE), proposes this CR is merged into S2-2105567
Sebastian (Qualcomm): this should be considered merged with 5567
Sang-Jun (Samsung) also proposes 5736 to be merged into S2-2105567.
Jari (NTT DOCOMO) agrees to merge into S2-2105567.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2105737 CR Approval 23.503 CR0625 (Rel-17, 'C'): Control of the 5G reference time distribution NTT DOCOMO Rel-17 r04 agreed. Revised to S2-2106774 Devaki (Nokia) provides r01.
Jari (NTT DOCOMO) provides r02.
Qianghua (Huawei) provides r03
Jari (NTT DOCOMO) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106774 CR Approval 23.503 CR0625R1 (Rel-17, 'C'): Control of the 5G reference time distribution NTT DOCOMO, Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2105737r04. Approved Agreed
8.5 S2-2105755 CR Approval 23.501 CR3073 (Rel-17, 'C'): Update of the PTP instance initialization NTT DOCOMO Rel-17 Postponed Saso (Intel) seeks clarification.
Jari (NTT DOCOMO) responds to Saso.
Yuan Tao (CATT) merges S2-2106136 into S2-2105755 per suggestions, and provides r01.
zhendong(ZTE) provides the comments,
Saso (Intel) replies to Jari (NTT DOCOMO).
Jari (NTT DOCOMO) responds to zhendong
zhendong(ZTE) provides the repsonse to jari,
Qianghua (Huawei) we have the same view that one single PTP instance should be associated with multiple instance IDs
Jari (NTT DOCOMO) comments
Shabnam (Ericsson) comments and provides r02.
Jari (NTT DOCOMO) responds to Shabnam
Saso (Intel) responds to Jari and Shabnam
Jari (NT DOCOMO) objects r02, responds to Saso
Shabnam (Ericsson) comments if it makes sense to postpone and try sorting it offline? Give comment.
Saso (Intel) objects all revisions of this CR; proposes to postpone the CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2105762 CR Approval 23.501 CR3075 (Rel-17, 'F'): Update the correction field Tencent, CATT Rel-17 Noted Devaki (Nokia) has strong concerns that this CR (and the related 502/3 CRs) that results in significant re-write of the QoS/TSCAI sections, not limited to corrections.
Devaki (Nokia) provides r01.
Chunshan (Tencent) provides r02.
Yuan Tao (CATT) provides r03.
Jari (NTT DOCOMO) objects r00-r03
Chunshan (Tencent) response to Jari and request a new tdoc for a LS to IEEE TSN WG.
Jari (NTT DOCOMO) responds to Chunshan (Tencent)
Chunshan (Tencent) responds to Jari (NTT DOCOMO)
Chunshan (Tencent) provides r04.
Jari (NTT DOCOMO) proposes to postpone, this is related to LS OUT in S2-2106695
Chunshan (Tencent) proposes to progress this CR and check with the LS in.
Sebastian (Qualcomm) objects to the CR; we need to first get feedback from IEEEE
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2106695 LS OUT Approval [DRAFT] LS on Correction Field update for Transparent Clock Tencent Rel-17 Created at CC#2. r01 agreed. Revised to S2-2106775 Chunshan (Tencent) requests this LS during the CC#2 and provides r00.
Shabnam (Ericsson) provides detailed comments.
Chunshan (Tencent) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106775 LS OUT Approval LS on Correction Field update for Transparent Clock SA WG2 Rel-17 Revision of S2-2106695r01. Approved Approved
8.5 S2-2105947 CR Approval 23.502 CR3015 (Rel-17, 'F'): Procedure for Validity Condition Samsung Rel-17 Merged into S2-2106773 Jari (NTT DOCOMO) proposes to be merged with S2-2105719
Sang-Jun (Samsung) agrees to mrege S2-2105947 to S2-2105719.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106062 CR Approval 23.501 CR3142 (Rel-17, 'F'): Clarify distribution of Announce message Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2106136 CR Approval 23.501 CR2915R1 (Rel-17, 'F'): Updates on initialization of PTP instance CATT Rel-17 Revision of (Postponed) S2-2104292 from S2-145E. Merge with S2-2105755 (postponed). Postponed Sebastian (Qualcomm) proposes to consider merged into S2-2105755
Sang-Jun (Samsung) has similar views as Sebastian (Qualcomm) and proposes to consider merged into S2-2105755
Yuan Tao (CATT) is fine to merge this paper into S2-2105755.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2106137 CR Approval 23.501 CR3150 (Rel-17, 'F'): Updates on PTP instance type CATT Rel-17 r02 agreed. Revised to S2-2106776 Jari (NTT DOCOMO) comments
Yuan (CATT) replies.
zhendong(ZTE),provides the comments
Yuan Tao (CATT) replies to zhendong(ZTE).
zhendong(ZTE) provides the response,
Yuan Tao (CATT) provides r01.
Yuan Tao (CATT) replies.
Yuan Tao (CATT) provides r02.
==== 8.X, 9.X Revisions Deadline ====
Sebastian (Qualcomm) supports r02
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106776 CR Approval 23.501 CR3150R1 (Rel-17, 'F'): Updates on PTP instance type CATT Rel-17 Revision of S2-2106137r02. Approved Agreed
8.5 S2-2106160 CR Approval 23.501 CR3154 (Rel-17, 'F'): Correction on Transparent Clock ports states Intel Rel-17 Merged into S2-2106783 zhendong(ZTE) ask for clarification
Jari (NTT DOCOMO) proposes to merge with S2-2106270
Saso (Intel) is OK to merge with S2-2106270, if the latter is agreeable. Otherwise wants to keep this CR separately
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106167 CR Approval 23.503 CR0640 (Rel-17, 'B'): KI#3, clarification on the TSC Assistance Container provider, AF functionality and PCF report ZTE Rel-17 r01 agreed. Revised to S2-2106777 Devaki (Nokia) provides r01, merged 6.3.1.18 with 5565 as per discussions with Zhendong.
Mirko (Huawei) provides r02.
zhendong(ZTE) is fine with r02 style,
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) objects to r02 as it removes critical details about TSC assistance container that is not present elsewhere in the specs. r01 comprises of the essential fix that can be approved.
zhendong(ZTE) proposes to approve r01,
Mirko (Huawei) responds to Devaki's comment.
Devaki (Nokia) comments.
Mirko (Huawei) responds.
zhendong(ZTE) is fine with r01 and r02,
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106777 CR Approval 23.503 CR0640R1 (Rel-17, 'B'): KI#3, clarification on the TSC Assistance Container provider, AF functionality and PCF report ZTE Rel-17 Revision of S2-2106167r01. Approved Agreed
8.5 S2-2106168 CR Approval 23.503 CR0641 (Rel-17, 'B'): KI#3, clarification on the TSCTSF provides the Qos and traffic information ZTE Rel-17 r03 agreed. Revised to S2-2106778, merging S2-2105761 Sebastian (Qualcomm) provides r01
Qianghua (Huawei) provides r02
zhendong(ZTE) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106778 CR Approval 23.503 CR0641R1 (Rel-17, 'B'): KI#3, clarification on the TSCTSF provides the Qos and traffic information ZTE, Tencent Rel-17 Revision of S2-2106168r03, merging S2-2105761. Approved Agreed
8.5 S2-2106169 CR Approval 23.501 CR3160 (Rel-17, 'B'): KI#3, clarification on the TSCTSF functionality and configuration for transport protocols ZTE Rel-17 r04 agreed. Revised to S2-2106779, merging S2-2106245 Devaki (Nokia) provides r01.
Devaki (Nokia) provides r02 with minor updates (merging the change from 5562 for TSCTSF clause).
Yoohwa (ETRI) provides r03 with updates to be merged with 6245.
zhendong(ZTE) provides the response,
Qianghua (Huawei) provides r04
zhendong(ZTE) provides the comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106779 CR Approval 23.501 CR3160R1 (Rel-17, 'F'): KI#3, clarification on the TSCTSF functionality and configuration for transport protocols ZTE, Nokia, Nokia Shanghai Bell, ETRI, Huawei Rel-17 Revision of S2-2106169r04, merging S2-2106245. Approved Agreed
8.5 S2-2106170 CR Approval 23.502 CR3048 (Rel-17, 'B'): KI#1, update the BMCA procedure ZTE Rel-17 r02 agreed. Revised to S2-2106780 Qianghua (Huawei) provides r01
György (Ericsson) provides r02.
Sang-Jun (Samsung) is fine with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106780 CR Approval 23.502 CR3048R1 (Rel-17, 'B'): KI#1, update the BMCA procedure ZTE Rel-17 Revision of S2-2106170r02. Approved Agreed
8.5 S2-2106171 CR Approval 23.501 CR3161 (Rel-17, 'B'): KI#3, clarification on the exposure of time sync service ZTE Rel-17 r02 agreed. Revised to S2-2106781 Laurent (Nokia): makes a remark
Devaki (Nokia) provides r01.
Jari (NT DOCOMO) provides r02.
Shabnam (Ericsson) supports r02.
Sang-Jun (Samsung) objects to r02.
zhendong(ZTE) provides the response,
Shabnam (Ericsson) objects to original and r01, supports r02.
==== 8.X, 9.X Revisions Deadline ====
Sang-Jun (Samsung) supports r01, and objects to original and r02.
zhendong(ZTE) provides the response and ask clarification,
Sang-Jun (Samsung) reponses to zhendong(ZTE)
Sang-Jun (Samsung) reponses to zhendong(ZTE) and accetps r02.
zhendong(ZTE) thanks samsung confirmation
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106781 CR Approval 23.501 CR3161R1 (Rel-17, 'B'): KI#3, clarification on the exposure of time sync service ZTE Rel-17 Revision of S2-2106171r02. Approved Agreed
8.5 S2-2106173 CR Approval 23.502 CR3049 (Rel-17, 'B'): KI#3, time synchronization modification and deactivation ZTE Rel-17 Merged into S2-2106773 Jari (NTT DOCOMO) proposes to be merged with S2-2105719
zhendong(ZTE), prefer to keep as seperate CR
Jari (NTT DOCOMO) comments, prefers to merge
Sebastian (Qualcomm) suggest to consider the CR merged into 5719
Sebastian (Qualcomm) objects to the CR as it overlaps with 5719 (to avoid approval by mistake..)
zhendong(ZTE) proposes, this CR is merged to 5719
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106252 CR Approval 23.502 CR3073 (Rel-17, 'F'): Updating a trusted AF for time synchronization service ETRI Rel-17 r01 agreed. Revised to S2-2106782 Jari (NTT DOCOMO) provides r01
Yoohwa (ETRI) is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106782 CR Approval 23.502 CR3073R1 (Rel-17, 'F'): Updating a trusted AF for time synchronization service ETRI Rel-17 Revision of S2-2106252r01. Approved Agreed
8.5 S2-2106269 CR Approval 23.501 CR3188 (Rel-17, 'F'): Update for Time Synchronization Information in PMIC and UMIC Huawei, Hisilicon Rel-17 Noted Shabnam (Ericsson) provides r01 correcting editorials and use consistently User plane node management, as in the Table.
Hui (Huawei) fine with r01.
Jari (NTT DOCOMO) comments
Hui (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
Jari (NTT DOCOMO) objects r00-r02
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2106270 CR Approval 23.501 CR3189 (Rel-17, 'B'): Update for (g)PTP messages forwarding in UPF/NW-TT Huawei, Hisilicon Rel-17 r04 agreed. Revised to S2-2106783, merging S2-2106160 Devaki (Nokia) provides r01 (includes comments/questions for clarification).
Sang-Jun (Samsung) comments.
Devaki (Nokia) comments.
Jari (NTT DOCOMO) provides r02
Hui (Huawei) provide r03.
Sebastian (Qualcomm) asks which item in the exception sheet this CR related to since it is CAT B?
Sang-Jun (Samsung) provides r04 which have a cover sheet with CAT F.
Hui (Huawei) fine with r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106783 CR Approval 23.501 CR3189R1 (Rel-17, 'F'): Update for (g)PTP messages forwarding in UPF/NW-TT Huawei, HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, Intel Rel-17 Revision of S2-2106270r04, merging S2-2106160. Approved Agreed
8.5 S2-2106271 CR Approval 23.502 CR3080 (Rel-17, 'F'): Update for Time Synchronization operations Huawei, Hisilicon Rel-17 Merged into S2-2106773 Jari (NTT DOCOMO) proposes to be merged with S2-2105719
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106272 CR Approval 23.502 CR3081 (Rel-17, 'F'): Update on accessing the UDR data for time synchronization ETRI Rel-17 r01 agreed. Revised to S2-2106784 Qianghua (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
Yoohwa (ETRI) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106784 CR Approval 23.502 CR3081R1 (Rel-17, 'F'): Update on accessing the UDR data for time synchronization ETRI Rel-17 Revision of S2-2106272r01. Approved Agreed
8.5 S2-2106312 CR Approval 23.501 CR3198 (Rel-17, 'C'): Correcting the residence time calculation for the delay measurements NTT DOCOMO Rel-17 r01 agreed. Revised to S2-2106785 Devaki (Nokia) provides r01.
Chunshan (Tencent) provides r02.
Jari (NTT DOCOMO) objects r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106785 CR Approval 23.501 CR3198R1 (Rel-17, 'C'): Correcting the residence time calculation for the delay measurements NTT DOCOMO Rel-17 Revision of S2-2106312r01. Approved Agreed
8.5 S2-2106343 CR Approval 23.501 CR3200 (Rel-17, 'C'): Providing reference time distribution information from AF to NG-RAN Qualcomm Rel-17 Merged into S2-2106771 Shabnam (Ericsson) provides comments and r01 and prefers this CR over CR documented in 5566.
Qianghua (Huawei) proposes to merge this with S2-2105566
Sebastian (Qualcomm) confirms that paper can be merged with 5566
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106344 CR Approval 23.502 CR3089 (Rel-17, 'C'): Providing reference time distribution information from AF to NG-RAN Qualcomm Rel-17 Merged into S2-2106772 Qianghua (Huawei) proposes to merge this with S2-2105567
Sebastian (Qualcomm): This paper can be marked as merged into 5567
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2106460 LS OUT Approval [DRAFT] LS on Time Synchronization support in 3GPP specification Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106786 Sebastian (Qualcomm) provides r01
Devaki (Nokia) is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2106786 LS OUT Approval LS on Time Synchronization support in 3GPP specification SA WG2 Rel-17 Revision of S2-2106460r01. Approved Approved
8.6 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) - - Docs:=18 -
8.6 - - - UE-assistance and UPF traffic steering - - Docs:=7 -
8.6 S2-2105521 DISCUSSION Approval Analysis of how UE-assistance operation can be used to influence DL traffic steering in UPF . Ericsson Rel-17 Noted Apostolis (Lenovo) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105522 CR Approval 23.501 CR3027 (Rel-17, 'F'): UE-assistance operation on traffic aggregate granularity Ericsson Rel-17 r01 agreed. Revised to S2-2106647 Apostolis (Lenovo) agrees to adopt the solution in this CR and provides r01.
Stefan (Ericsson) is ok with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2106647 CR Approval 23.501 CR3027R1 (Rel-17, 'F'): UE-assistance operation on traffic aggregate granularity Ericsson, Lenovo, Motorola Mobility Rel-17 Revision of S2-2105522r01. Approved Agreed
8.6 S2-2105523 CR Approval 23.501 CR3028 (Rel-17, 'F'): UE-assistance operation on per-SDF granularity Ericsson Rel-17 Noted Susan (Huawei) proposes to note this CR, and agree with the proposal in S2-2105522.
Rainer (Nokia) agrees with Susan (Huawei).
Rainer (Nokia) proposes to note 5523.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) supports noting this CR and going with 5522r01
Stefan (Ericsson) agrees to NOTE and go with 5522 instead
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105790 CR Approval 23.501 CR3083 (Rel-17, 'F'): Restructuring of clause 5.32.5.1 on Access Network Performance Measurements Nokia, Nokia Shanghai Bell Rel-17 Noted Dario S. Tonesi (Qualcomm) asks question for clarification.
Rainer (Nokia) replies.
Apostolis (Lenovo) agrees with the changes in this CR.
Susan (Huawei) comments and provides r01.
Stefan (Ericsson) cannot agree with r01
Rainer (Nokia) agrees with Stefan (Ericsson).
Susan (Huawei) can live with r00.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) withdraw her comment to accept r00. I can only accept r01 and object to r00, due to the problem identified during the discussion on S2-2105941.
Dario (Qualcomm) is OK with r00
Stefan (Ericsson) provides comments and objects to r01
Rainer (Nokia) is ok with r01.
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105939 DISCUSSION Decision Discussion on PMF extension for sending UE-assistance data to UPF. Huawei, HiSilicon Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105940 CR Approval 23.501 CR3109 (Rel-17, 'F'): PMF extension for sending UE-assistance data to UPF Huawei, HiSilicon Rel-17 Noted Rainer (Nokia) proposes to note 5940.
Stefan (Ericsson) also proposes to note this CR
Susan (Huawei) agrees to note this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.6 - - - Other - - Docs:=11 -
8.6 S2-2105941 CR Approval 23.501 CR3110 (Rel-17, 'F'): PMF information transported via N4 Huawei, HiSilicon Rel-17 Noted Stefan (Ericsson) comments and provides r01
Myungjune (LGE) comments and provides r02.
Stefan (Ericsson) provides r03
Dario (Qualcomm) ask question on plural form of 'ports' and 'MAC addresses' in r03
Stefan (Ericsson) agrees with Dario and provides r04
Susan (Huawei) can only accept r00, and object to all revisions, i.e. r01, r02, r03 and r04.
Stefan (Ericsson) comments that r00 is not aligned with rest of 23.501 and previous agreements
Susan (Huawei) replies and sustain objection to all revisions, i.e. r01, r02, r03 and r04.
Stefan (Ericsson) provides r05
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) replies to Myungjune and provides r06 in draft folder.
Susan (Huawei) cannot accept r05, and sustain objection to r01, r02, r03, r04.
Myungjune (LGE) supports r04 and can live with r05.
Stefan (Ericsson) objects to r00
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105942 CR Approval 23.502 CR3013 (Rel-17, 'F'): PMF information transported via N4 Huawei, HiSilicon Rel-17 Noted Stefan (Ericsson) provides r01
Myungjune (LGE) comments and provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2105943 CR Approval 23.501 CR3111 (Rel-17, 'F'): Termination on UE assistance mode Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106648 Myungjune (LGE) comments and provides r01.
Rainer (Nokia) is ok with r01.
Dario (Qualcomm) is not OK with r00 and supports r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2106648 CR Approval 23.501 CR3111R1 (Rel-17, 'F'): Termination on UE assistance mode Huawei, HiSilicon Rel-17 Revision of S2-2105943r01. Approved Agreed
8.6 S2-2105958 CR Approval 23.501 CR3114 (Rel-17, 'F'): Removal of 5G-RG limitation on 3GPP access leg support in EPC LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.6 S2-2105959 CR Approval 23.501 CR3115 (Rel-17, 'F'): Clarification on steeing mode LG Electronics Rel-17 Postponed DongYeon (Samsung) asks a question for clarification.
Myungjune (LGE) replies to DongYeon (Samsung).
Rainer (Nokia) provides r01.
DongYeon (Samsung) provides r01.
Dario (Qualcomm) provides r02
Rainer (Nokia) provides r03.
Myungjune (LGE) provides r04 and replies to Dario (Qualcomm) and Rainer (Nokia)
Apostolis (Lenovo) is fine with r04 and recommends a small change.
Myungjune (LGE) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Myungjune (LGE) replies to Marco (Huawei).
DongYeon (Samsung) supports r05.
Dario (Qualcomm) supports r05
Marco (Huawei) objects all versions from r00 to r05. I can accept r05 if only if Note Y is removed.
Rainer (Nokia) is ok with r05.
Marco (Huawei) comments and confirm objection to any version with Note Y
==== 8.X, 9.X Final Deadline ====
Postponed
8.6 S2-2105960 CR Approval 23.501 CR3116 (Rel-17, 'F'): Clarification on source and destination addresses setting for PMF messages LG Electronics Rel-17 r02 agreed. Revised to S2-2106649 Dario S. Tonesi (Qualcomm) provides r01
Myungjune (LGE) is ok with r01
Apostolis (Lenovo) provides comments to r01.
Stefan (Ericsson) provides a question
Myungjune (LGE) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2106649 CR Approval 23.501 CR3116R1 (Rel-17, 'F'): Clarification on source and destination addresses setting for PMF messages LG Electronics Rel-17 Revision of S2-2105960r02. Approved Agreed
8.6 S2-2106236 CR Approval 23.501 CR3179 (Rel-17, 'F'): Clarification on threshold values Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106650 Stefan (Ericsson) comments and provides r01
Dario (Qualcomm) provides r02
Myungjune (LGE) comments.
Hualin(Huawei) replied to Stefan(Ericsson).
Rainer (Nokia) comments.
Stefan (Ericsson) agrees with Rainer and replies to Hualin
Stefan (Ericsson) provides r04
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) supports r04.
Rainer (Nokia) is ok with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2106650 CR Approval 23.501 CR3179R1 (Rel-17, 'F'): Clarification on threshold values Huawei, HiSilicon Rel-17 Revision of S2-2106236r04. Approved Agreed
8.6 S2-2106237 CR Approval 23.503 CR0642 (Rel-17, 'F'): Clarification on threshold values Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.7 - - - Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) - - Docs:=55 -
8.7 S2-2105232 LS In Information LS from GSMA-ACJA: 3GPP SA1 clarifications on problematic UAV GSMA-ACJA (GSMA-ACJA LS 3GPP SA2 S1-210359) Revision of postponed S2-2103731 from S2-145E. Noted Stefano (Qualcomm) suggests noting, we already sent a reply to relevant parties.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2105306 LS In Information LS from TSG SA: LS on UAS terminology alignment TSG SA (SP-210579) Rel-17 Noted Stefano (Qualcomm) suggests noting, we already sent a reply to relevant parties.
Stefano (Qualcomm) question for clarification.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2105474 P-CR Approval 23.256: TS 23.256: Updates to add missing service operations. Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106876 Stefano (Qualcomm) recommends merging with 5672, waiting for resolution on 5670.
Tricci (OPPO) agrees with Qualcomm's comments. In addition, it does not understand why not reuse PDU Session ID with DNN instead of introducing new correlation id?
Pallab (Nokia) OK with the merger proposal. Revision to be provided based on outcome of 5670. Also responds to Tricci (OPPO)
Guanglei (Huawei) proposes to merge 5474 into 5672.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2105468 P-CR Approval 23.256: TS 23.256: Updates to Procedure for Unknown UAV tracking. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106866, merging S2-2106361 Tricci (OPPO) believes the original intents of this Unknown UAV tracking has been mistaken by this PCR. The Unknown UAV tracking is to ensure the list of authorized UAVs in the AOI, and not the list of UEs that have UAS subscriptions.
Stefano (Qualcomm) question for clarification.
Pallab (Nokia) responds to Stefano (Qualcomm).
Pallab (Nokia) responds to Tricci (Oppo).
Stefano (Qualcomm) responds to Tricci (Oppo) and Pallab (Nokia).
Tricci (OPPO) responds to Stefano (Qualcomm) to clarify previous comments
Tricci (OPPO) provides r01 to restore the required filtering operation and not to make it optional.
Pallab (Nokia) OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106866 P-CR Approval 23.256: TS 23.256: Updates to Procedure for Unknown UAV tracking. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105468r01, merging S2-2106361. Approved Approved
8.7 S2-2106285 P-CR Approval 23.256: TS 23.256: Clarifications to Procedure for Unknown UAV tracking. Samsung Rel-17 r03 agreed. Revised to S2-2106867 Guanzhou (InterDigital) asks for clarifications.
Tricci (OPPO) agrees with InterDigital and don't see the need for major rewrite of the procedures for no reason.
DongYeon (Samsung) replies, and provides r02 which includes the discussion part.
Tricci (OPPO) thanks the good intention from DongYeon (Samsung), but CANNOT accept any of the versions that have been proposed.
DongYeon (Samsung) provides r03.
Tricci (OPPO) thanks DongYeon (Samsung) to provides r01 and would accepts r01.
Stefano (Qualcomm) can accept r03 but not previous revisions.
Tricci (OPPO) correct the previous typos and thanks DongYeon (Samsung) to provides r03 and would accepts r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106867 P-CR Approval 23.256: TS 23.256: Clarifications to Procedure for Unknown UAV tracking. Samsung Rel-17 Revision of S2-2106285r03. Approved Approved
8.7 S2-2105607 P-CR Approval 23.256: TS 23.256: Clean up and alignment for UAV tracking. OPPO Rel-17 r02 agreed. Revised to S2-2106868 Jaewoo (LGE) provides comments.
Pallab (Nokia) provides comments and proposes to merge with 5469
Tricci (OPPO) is confused by Nokia's comments and would like to ask for clarifications. OPPO also would like to address LG's comments for including AMF/MME support for Presence Monitoring.
Pallab (Nokia) responds to Tricci (OPPO)
Pallab (Nokia) asks for further clarification
Tricci (OPPO) responds to Pallab (Nokia) to try to sort out on the confusion of GLMC support for presence monitoring.
Pallab (Nokia) thanks Tricci (OPPO) for clarifying and raises some points for discussion.
Tricci (OPPO) thanks Pallab (Nokia) for the detailed analysis and would like to respond to Nokia's suggestions.
Tricci (OPPO) provides further responses to Pallab (Nokia) and proposes r01.
Pallab (Nokia) responds to Tricci (OPPO).
Tricci (OPPO) responds to Jaewoo (LGE)'s ncomments.
Pallab (Nokia) tries to clarify.
Tricci (OPPO) thanks for Pallab (Nokia) clarifications, however, 5607 is still needed to fix the inconsistent issue between 5.3.1.1 and 5.3.2. Just want to confirm such fix is still needed
Tricci (OPPO) asks Pallab (Nokia) for the clarifications for his latest solution preference.
Tricci (Oppo) thanks Pallab (Nokia) feedback and would like to respond.
Tricci (OPPO) thanks Pallab (Nokia) confirmation for option 2, and proposes to approve the initial version of the 5607 and no need for any revision.
Pallab (Nokia) provides r02 based on r00, removing third change (clause 5.3.3) as it is covered in 5469.
Tricci (OPPO) thanks Pallab (Nokia) to provide r02 and it is okay to go with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106868 P-CR Approval 23.256: TS 23.256: Clean up and alignment for UAV tracking OPPO Rel-17 Revision of S2-2105607r02. Approved Approved
8.7 S2-2105469 P-CR Approval 23.256: TS 23.256: Updates to Procedure for UAV presence monitoring. Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2105673 P-CR Approval 23.256: Clarification on policies and rules used for UAV Presence Monitoring. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106869 Stefano (Qualcomm) question for clarification.
Guanglei (Huawei) provides r01
Tricci (OPPO) objects r01 for removing of the current text that allows the 'option' for USS to provide policy prior to the monitoring detection.
Guanglei (Huawei) clarifies that we are ok to use the original version to help stage 3 work.
Guanglei (Huawei) provides r02 to avoid overlap with 2105607.
Pallab (Nokia) comments.
Tricci (OPPO) thanks Guanglei (Huawei) update and accepts r02.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) OK with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106869 P-CR Approval 23.256: Clarification on policies and rules used for UAV Presence Monitoring. Huawei, HiSilicon Rel-17 Revision of S2-2105673r02. Approved Approved
8.7 S2-2105470 P-CR Approval 23.256: TS 23.256: Updates to Procedure for UAV location reporting. Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2106002 P-CR Approval 23.256: UAV-C replacement procedure. Lenovo, Motorola Mobility, Ericsson Rel-17 CC#4: r00 + changes agreed. Revised to S2-2106870. Guanzhou (InterDigital) repeats the concerns raised before.
Guanzhou (InterDigital) proposes to postpone this.
Dimitris (Lenovo) comments
==== 8.X, 9.X Revisions Deadline ====
Guanzhou (InterDigital) conditionally accepts this with an EN saying the procedure needs to be revisited with new C2 authorization procedures in place.
Dimitris (Lenovo) suggests to handle 6002 in CC#4 adding an EN
Guanzhou (InterDigital) OK with the proposed EN wording.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106870 P-CR Approval 23.256: UAV-C replacement procedure. Lenovo, Motorola Mobility, Ericsson Rel-17 Revision of S2-2106002r00 + changes. Approved Approved
8.7 S2-2106328 P-CR Approval 23.256: TS 23.256: UAV Controller Replacement. InterDigital Rel-17 Postponed Dimitris (Lenovo) indicates there is a counter proposal in S2-2106002. Provides comments
Shabnam (Ericsson) provides comments and do not support this proposal (also see 6500).
Guanzhou (InterDigital) replies Shabnam (Ericsson) and Dimitris (Lenovo).
Dimitris (Lenovo) inline with agreements made in 6501, considers 6328 is merged in 6002. Take 6002 as a basis for the UAV-C replacement procedure
Guanzhou (InterDigital) proposes to postpone this.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.7 S2-2106326 P-CR Approval 23.256: Handling of UAV authorization failure and other service unavailability in CN. InterDigital Rel-17 Merged into S2-2106875 Pallab (Nokia) comments and indicates overlap with 5866
Guanzhou (InterDigital) responds to Pallab (Nokia) comments and provides r01.
Stefano (Qualcomm) expresses concerns on the use of the timer, and suggests the first part of the paper is merged with 5866.
Pallab (Nokia) proposes to postpone this pCR
Guanzhou (InterDigital) consider this merged with 5866.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2105471 P-CR Approval 23.256: TS 23.256: Updates to UUAA-SM procedure. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106871 Stefano (Qualcomm) recommends merging with 5670, 6329, and 6500. A resolution is required on the differences between the papers.
Guanzhou (InterDigital) comments.
Pallab (Nokia) comments.
Guanglei (Huawei) provides r01 to avoid overlapping with 5670.
Pallab (Nokia) OK with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106871 P-CR Approval 23.256: TS 23.256: Updates to UUAA-SM procedure. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105471r01. Approved Approved
8.7 S2-2105472 P-CR Approval 23.256: TS 23.256: Updates to UUAA-SM procedure at EPS Attach. Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2105473 P-CR Approval 23.256: TS 23.256: Updates to UUAA-MM Procedure. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106872 Tricci (OPPO) agrees with Nokia to consolidate the status indication into single one. However, Nokia's proposed changes do not justify to remove the EN. OPPO provides r01 to undo the removal of the EN and to provide some editorial clarifications.
Pallab (Nokia) OK with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106872 P-CR Approval 23.256: TS 23.256: Updates to UUAA-MM Procedure. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105473r01. Approved Approved
8.7 S2-2106409 P-CR Approval 23.256: TS 23.256: Clarifications to UUAA-MM procedure. Samsung Rel-17 r01 agreed. Revised to S2-2106873 Pallab (Nokia) comments and request for clarification
DongYeon (Samsung) replies, and provides r01 which includes the introduction part.
Pallab (Nokia) OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106873 P-CR Approval 23.256: TS 23.256: Clarifications to UUAA-MM procedure. Samsung Rel-17 Revision of S2-2106409r01. Approved Approved
8.7 S2-2105475 CR Approval 23.502 CR2915 (Rel-17, 'F'): UE subscription data types to support UAS Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106874 Stefano (Qualcomm) indicates there is overlap with 6448 for the part related to the UDM subscription and suggest using 6448 for that.
Tricci (OPPO) asks for additional clarification for the need of additional indication for API based Secondary Authentication & Authorization.
Pallab (Nokia) responds to Stefano (Qualcomm).
Pallab (Nokia) responds to Tricci (OPPO)
Tricci (OPPO) thanks Pallab (Nokia) for clarification.
Pallab (Nokia) provides r01, adapting the AM subscription data from 6448 (CR3108).
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) proposes to approve r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106874 CR Approval 23.502 CR2915R1 (Rel-17, 'F'): UE subscription data types to support UAS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105475r01. Approved Agreed
8.7 S2-2105476 CR Approval 23.502 CR2916 (Rel-17, 'F'): Update to UE context in AMF to support UAS Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.7 S2-2105477 CR Approval 23.502 CR2917 (Rel-17, 'F'): Update to Event Filters for AMF exposure events to support UAS Nokia, Nokia Shanghai Bell Rel-17 Approved Tricci (OPPO) asks for clarification for what reason that additional PDU Session Status is needed because the DNN itself is sufficient to reflect whether the given PDU session is corresponding to UAS or not?
Pallab (Nokia) responds to Tricci (OPPO)
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) proposes to approve r00
Tricci (OPPO) agrees to approve r00
==== 8.X, 9.X Final Deadline ====
Agreed
8.7 S2-2105670 P-CR Approval 23.256: Clarification on SMF reports the status of PDU Session to UAS NF for UUAA-SM. Huawei, HiSilicon Rel-17 r06 agreed. Revised, merging S2-2106329, to S2-2106983 Dimitris (Lenovo) provides comments
Stefano (Qualcomm) recommends merging with 5471, 6329, and 6500. A resolution is required on the differences between the papers.
Guanglei (Huawei) replies Dimitris (Lenovo) and provides r01.
Guanglei (Huawei) further replies Dimitris (Lenovo) and think r0 can work well.
Guanzhou (InterDigital) comments and provides r02.
Guanglei (Huawei) replies and provides r03.
Dimitris (Lenovo) provides additional questions
Tricci (OPPO) would like to ask Lenovo for clarification.
Guanglei (Huawei) replies Dimitris(Lenovo) and provides r04.
Pallab (Nokia) comments.
Guanglei (Huawei) replies and thinks r03 can work well.
Dimitris (Lenovo) comments
Tricci (OPPO) supports Guanglei (Huawei) to use the r03 based on the latest general agreement in 6501
Guanglei (Huawei) provides r05 based on r03 to cover the second change of 6500 and the second change of 5471.
Pallab (Nokia) provides r06
Dimitris (Lenovo) provides r07
Pallab (Nokia) cannot agree to r07
Dimitris (Lenovo) responds to Pallab (Nokia)
Pallab (Nokia) responds to Dimitris (Lenovo)
Dimitris (Lenovo) thanks Pallab for clarifying
Guanzhou (InterDigital) can't accept r07.
Shabnam (Ericsson) agrees to go with r06 and asks to cosign the pCR.
==== 8.X, 9.X Revisions Deadline ====
Tricci (OPPO) supports r06.
Guanglei (Huawei) also agrees to go with r06.
Dimitris (Lenovo) is OK with r06
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106983 P-CR Approval 23.256: Clarification on SMF reports the status of PDU Session to UAS NF for UUAA-SM. Huawei, HiSilicon, Ericsson,InterDigital Rel-17 Revision of S2-2105670r06, merging S2-2106329. Approved Approved
8.7 S2-2106329 P-CR Approval 23.256: TS 23.256: Correction on UUAA-SM procedure. InterDigital Rel-17 Merged into S2-2106983 Stefano (Qualcomm) recommends merging with 5471, 5670, and 6500. A resolution is required on the differences between the papers.
Guanglei (Huawei) proposes to merge 6329 into 5670.
Pallab (Nokia) suggests to merge this to 5670
Guanzhou (InterDigital) OK to merge with 5670
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2105671 P-CR Approval 23.256: Clarification on AMF triggers UUAA Re-authentication. Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2105866 P-CR Approval 23.256: TS 23.256: Clarifications to UUAA Re-Authentication Failure. Qualcomm Incorporated Rel-17 r03 agreed. Revised to S2-2106875, merging S2-2106326 Pallab (Nokia) requests for clarification
Guanzhou (InterDigital) comments and provide r01 for potential merge with part of 6326.
Stefano (Qualcomm) comments and asks for clarifications.
Guanzhou (InterDigital) responds to Stefano (Qualcomm).
Stefano (Qualcomm) provides r02.
Pallab (Nokia) comments and provides r03
Guanzhou (InterDigital) is OK with r02 or r03.
Pallab (Nokia) clarifies that r03 is not dependent on 5670. Instead it uses 5475
==== 8.X, 9.X Revisions Deadline ====
Stefano (Qualcomm) is OK with r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106875 P-CR Approval 23.256: TS 23.256: Clarifications to UUAA Re-Authentication Failure. Qualcomm Incorporated Rel-17 Revision of S2-2105866r03, merging S2-2106326. Approved Approved
8.7 S2-2105865 P-CR Approval 23.256: TS 23.256: Clarifications to UUAA procedure . Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2106499 P-CR Approval 23.256: UUAA Clarifications and Corrections. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2106324 P-CR Approval 23.256: Update of UUAA At PDN Connection/PDU Session Establishment Huawei, HiSilicon Rel-17 Noted Pallab (Nokia) comments
Tricci (OPPO) asks whether 6324 or 5474 is to be agreed? Please clarify.
Guanglei (Huawei) replies Pallab (Nokia) and Tricci(OPPO) and propose to merge 5474 into 5672.
==== 8.X, 9.X Revisions Deadline ====
Tao(VC) let's check whether r00 agreeable then.
Guanglei (Huawei) clarify this can be approved.
Pallab (Nokia) thinks this can be NOTED
Guanglei (Huawei) agrees NOTED.
Pallab (Nokia) responds to Guanglei (Huawei)
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2105571 P-CR Approval 23.256: TS 23.256 PCR for UAV UUAA status harmonization between UAS and USS. OPPO Rel-17 Noted Guanzhou (InterDigital) asks for clarifications.
Tricci (OPPO) responds to InterDigital question.
Guanzhou (InterDigital) asks further questions.
Tricci (OPPO) responds to InterDigital.
Guanzhou (InterDigital) proposes to Note this.
==== 8.X, 9.X Revisions Deadline ====
Tricci (OPPO) is okay to note 5571.
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2105672 P-CR Approval 23.256: Clarification on Nnef_Authentication and Naf_Authentication service. Huawei, HiSilicon Rel-17 r02 agreed. CC#4: r01 agreed. Revised to S2-2106876, merging S2-2105474 Stefano (Qualcomm) recommends merging with 5474, waiting for resolution on 5670.
Tricci (OPPO) asks for clarification regarding to the consolidate SBI proposed by Huawei for UUAA reauthentication and revocation
Guanglei (Huawei) replies Tricci (OPPO) and kindly remind that we do not remove the 'revocation cause'.
Guanglei (Huawei) provides r01 to merge 5474 into 5672.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) OK with r01, checks the possibility of a revision in CC#4, with some corrections/updates
Guanglei (Huawei) replies and agrees to provide a revision.
Pallab (Nokia) OK with the proposal from Guanglei (Huawei).
Guanglei (Huawei) provides r02 to correct errors and asks for CC#4 based on reached consensus with Pallab (Nokia).
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106876 P-CR Approval 23.256: Clarification on Nnef_Authentication and Naf_Authentication service. Huawei, HiSilicon Rel-17 Revision of S2-2105672r01, merging S2-2105474. Approved Approved
8.7 S2-2105867 P-CR Approval 23.256: TS 23.256: Clarifications to Nnef services . Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2105674 CR Approval 23.502 CR2952 (Rel-17, 'B'): Update NEF Monitoring Events to Support Area of Interest event Huawei, HiSilicon Rel-17 Approved Tricci (OPPO) asks for clarification regarding the introduction of new event 'Area of Interest' in this CR. Why the existing event, Location Reporting, cannot be used?
Guanglei (Huawei) replies Tricci (OPPO) and kindly remind that 'Area of Interest' and 'Location Reporting' are different.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.7 S2-2105478 CR Approval 23.502 CR2918 (Rel-17, 'F'): NEF discovery and selection based on AF address Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106981 Tricci (OPPO) proposed to note S2-2105478 because the FQDN parameter has already been included to support NEF discovery. No need to specify UAS specific parameter. This PCR is not needed.
Pallab (Nokia) responds to Tricci (OPPO) and insists that the CR is needed. The CR does not introduce any UAS specific parameter.
Tricci (OPPO) still thinks the current CR is not needed and asks why would the existing 'domain name' parameter is not sufficient to apply to support AF's FQDN?
Tricci (OPPO) thanks Pallab (Nokia) for further clarifications and prefers the additional note approach.
Pallab (Nokia) provides r01.
Tricci (OPPO) thanks Pallab (Nokia) to provide r01 and can accept r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106981 CR Approval 23.502 CR2918R1 (Rel-17, 'F'): NEF discovery and selection based on AF address Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105478r01. Approved Agreed
8.7 S2-2105479 CR Approval 23.501 CR3018 (Rel-17, 'F'): NEF discovery and selection based on AF address Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106982 Tricci (OPPO) proposed to note S2-2105479 because the FQDN parameter has already been included to support NEF discovery. No need to specify UAS specific parameter. This PCR is not needed.
Pallab (Nokia) responds to Tricci (OPPO) and insists that the CR is needed.
Pallab (Nokia) provides r01.
Tricci (OPPO) thanks Pallab (Nokia) to provide r01 and can accept r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106982 CR Approval 23.501 CR3018R1 (Rel-17, 'F'): NEF discovery and selection based on AF address Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105479r01. Approved Agreed
8.7 S2-2105868 P-CR Approval 23.256: TS 23.256: Corrections on USS and UAS NF/NEF interactions. Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2106317 P-CR Approval 23.256: USS Initiated C2 Authorization. InterDigital Rel-17 Noted Stefano (Qualcomm) question for clarification.
Guanzhou (InterDigital) replies and provides r01.
Shabnam (Ericsson) do not agree with the proposal which relies on pCR 6328, provides comments that 6500/6501 also addresses alternative approach.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2106325 P-CR Approval 23.256: Clarification on support of UAS NF in SCEF+NEF. Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2105859 CR Approval 23.501 CR3103 (Rel-17, 'C'): Subscription handling for Aerial UEs Qualcomm Incorporated, AT&T, Oppo, Verizon, Ericsson Rel-17 Postponed Pallab (Nokia) points that the CR is not related to ID_UAS and hence shall be moved to a different/relevant AI
Stefano (Qualcomm) provides a clarification.
Pallab (Nokia) proposes to postpone this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.7 S2-2106448 CR Approval 23.502 CR3108 (Rel-17, 'C'): Subscription handling for Aerial UEs Qualcomm Incorporated Rel-17 Postponed Pallab (Nokia) asks for clarification
Stefano (Qualcomm) provides rev. 01 and a clarification.
Pallab (Nokia) proposes to postpone this CR and adapt the AM subscription data changes in 5475
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.7 S2-2106500 P-CR Approval 23.256: Correction of C2 Authorization procedures (clauses 3, 5,2,3, 5,2,4). Ericsson Rel-17 r05 agreed. Revised to S2-2106877 Stefano (Qualcomm) recommends merging with 5471, 5670, and 6329. A resolution is required on the differences between the papers. Adds comments
Guanzhou (InterDigital) comments and asks for clarifications.
Pallab (Nokia) shares the same views as Guanzhou (InterDigital)
Shabnam (Ericsson) please see responses in line to the comments below.
Guanzhou (InterDigital) further comments.
Shabnam (Ericsson) provides r01 according to the discussion, comments on the two flows.
Guanzhou (InterDigital) provides r02.
Shabnam (Ericsson) accepts r02, thanks.
Guanglei (Huawei) provides r03 to avoid overlapping with 5670.
Pallab (Nokia) provides r05, based on r03. Please ignore r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106877 P-CR Approval 23.256: Correction of C2 Authorization procedures (clauses 3, 5,2,3, 5,2,4). Ericsson Rel-17 Revision of S2-2106500r05. Approved Approved
8.7 S2-2106501 P-CR Approval 23.256: Correction of C2 Authorization procedures (clauses 5.2.5, 5.2.8. 5.2.9). Ericsson Rel-17 r10 agreed. Revised to S2-2106878 Pallab (Nokia) comments. Raises concerns with some of the proposed changes.
Guanzhou (InterDigital) shares the concerns.
Shabnam (Ericsson) provides response to Nokia comments.
Guanglei (Huawei) comments.
Pallab (Nokia) responds to Shabnam (Ericsson).
Shabnam (Ericsson) responds to Nokia comments since Huawei seem to share that as well, and provide proposed way forward.
Shabnam (Ericsson) provides r01 according to the principles below and with the assumption that Huawei proposal (5670) of reuse is ok.
Dimitris (Lenovo) supports the proposal. Provides r02
Shabnam (Ericsson) ok with the proposal from Nokia. r02 is ok for us as well, thanks.
Guanzhou (InterDigital) provides r03.
Guanglei (Huawei) provides r04 based on r03.
Dimitris (Lenovo) provides r05 based on r04
Pallab (Nokia) provides r06 based on r05
Guanglei (Huawei) provides r07 based on r06.
Shabnam (Ericsson) provides r08 to update the UAV Re-authorization to re-Authentication to address InterDigital comment.
Guanzhou (InterDigital) provides r09.
Pallab (Nokia) cannot accept the re-insertion of C2 pending indication in r09
Dimitris (Lenovo) cannot accept r09
Shabnam (Ericsson) agrees that update on r09 is not really accurate as per our understanding, gives some comments and proposes to go with r08.
Guanzhou (InterDigital) can only accept r09.
Shabnam (Ericsson) but in 6501 we now refer to reauthentication right? Can we consider an EN on if such indication is needed on top of r08 instead of wasting all the work/efforts? Provides r10, though believes r08 is correct.
Shabnam (Ericsson) includes the link to r10.
Guanzhou (InterDigital) can only provides r11.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) also prefers r08. r10 can be accepted as a compromise, although feels that r08 is correct. Cannot accept r09, r11
Tricci (OPPO) also prefers R08, and can accept R10 as a compromise for a way forward.
Stefano (Qualcomm) prefers R08, cannot accept R09 or R11, and can accept R10 which is a good compromise to keep the sticky point open and to not block the remaining necessary changes to the TS.
Dimitris (Lenovo) can accept r10, prefers r08
Guanzhou (InterDigital) accepts r10.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2106878 P-CR Approval 23.256: Correction of C2 Authorization procedures (clauses 5.2.5, 5.2.8. 5.2.9). Ericsson Rel-17 Revision of S2-2106501r10. Approved Approved
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=114 -
8.8 S2-2105293 LS In Information LS from SA WG3: Rely LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism SA WG3 (S3-212204) Rel-17 Noted Fei (OPPO) proposes to note this LS
Deng Qiang (CATT) this LS should be discussed under AI#8.8.
Hannu (Nokia) agrees the move to AI#8.8 and confirms the intention to note the LS with no SA2 action
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105267 LS In Information LS from RAN WG2: LS on establishment/resume cause value and UAC on L2 SL Relay RAN WG2 (R2-2106520) Rel-17 Noted Fei (OPPO) proposes to note this LS
Deng Qiang (CATT) this LS should be discussed under AI#8.8.
Hannu (Nokia) agrees to move the LS to AI#8.8 but it should be still noted as no SA2 action is requested.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105242 LS In Action LS from RAN WG2: LS on discovery and relay (re)selection RAN WG2 (R2-2104649) Rel-17 Revision of postponed S2-2103771 from S2-145E. Responses drafted in S2-2106097 and S2-2106146. CC#4: Postponed
==== 8.X, 9.X Final Deadline ====
Deng Qiang (CATT) this LS should be marked as POSTPONED as no reply LS agreed this meeting.
Postponed
8.8 S2-2106097 LS OUT Approval [DRAFT] Reply LS on discovery and relay (re)selection CATT Rel-17 Response to S2-2105242. r01 agreed. Revised to S2-2106879. CC#4: Noted Deng Qiang (CATT) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Mehrdad (Samsung) suggests to keep this LS open for CC#4 to align with final outcome of S2-2106094.
==== 8.X, 9.X Final Deadline ====
Deng Qiang (CATT) this LS should be NOTED at CC#4 as no conclusion reached at this meeting.
Noted
8.8 S2-2106879 LS OUT Approval [DRAFT] Reply LS on discovery and relay (re)selection CATT Rel-17 Revision of S2-2106097r01. WITHDRAWN Withdrawn
8.8 S2-2106146 LS OUT Approval [DRAFT] Reply LS on discovery and relay (re)selection OPPO Rel-17 Revision of (Noted) S2-2104479 from S2-145E. Response to S2-2105242. Noted Zhang (Ericsson) provides comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - Identification of ProSe Services - - Docs:=2 -
8.8 S2-2105780 P-CR Approval 23.304: Clarification on ProSe Service Type. Samsung Rel-17 Revision of (Postponed) S2-2104583 from S2-145E. CC#4: r11 + changes agreed. Revised to S2-2106880 Changhong (Intel) comments and provides r01.
Mehrdad (Samsung) comments on r01 and provides r02.
Yali (OPPO) asks a question.
Mehrdad (Samsung) replies to OPPO.
Wen (vivo) comments on r02.
Mehrdad (Samsung) provides r03.
Judy (Ericsson) comments
Mehrdad (Samsung) replies to Ericsson and provides r04 and r05
Yali (OPPO) thank Mehrdad for the answer.
Changhong (Intel) provides r06 and replies to Judy.
Mehrdad (Samsung) replies to Intel and Ericsson.
Mehrdad (Samsung) provides r07
LaeYoung (LGE) comments.
Mehrdad (Samsung) replies to LGE.
LaeYoung (LGE) answers to Mehrdad (Samsung).
Changhong (Intel) replies.
Mehrdad (Samsung) replies to LGE and Intel and provides r08.
Mehrdad (Samsung) provides r09.
Steve (Huawei) comments
Mehrdad (Samsung) replies to Huawei.
Mehrdad (Samsung) provides r10.
Changhong (Intel) is fine with r10 and thanks to Mehrdad.
Sudeep (Apple) comments on r10.
Mehrdad (Samsung) provides r11.
Mehrdad (Samsung) replies to Ericsson.
Judy (Ericsson) responds Mehrdad (Samsung)
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) cannot accept r11 as is, and request to change '...ProSe identifier is determined by stage 3' to '...ProSe identifier is to be determined'
Hong (Qualcomm) comments and is fine with r11.
Mehrdad (Samsung) suggests to go for r11+ change '...ProSe identifier is determined by stage 3' to Editor NOTE '...ProSe identifier is to be determined'.
Deng Qiang (CATT) asks question on the EN.
Judy (Ericsson) is fine with Mehrdad (Samsung)'s proposal.
Changhong (Intel) can live with Mehrdad proposed change based on r11 by including the EN.
Judy (Ericsson) responds to Changhong (Intel) what I mean is what ProSe ID mean, but not how ProSe ID is encoded (e.g. binary or octet string which is in the remit of stage 3).
Mehrdad (Samsung) uploaded r12 in CC#4 folder. This is r11+ change '...ProSe identifier is determined by stage 3' to Editor NOTE '...ProSe identifier is to be determined'
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106880 P-CR Approval 23.304: Clarification on ProSe Service Type. Samsung, Intel Rel-17 Revision of S2-2105780r11+ changes. Approved Approved
8.8 - - - Identifiers for UE-NW Relay discovery - - Docs:=5 -
8.8 S2-2105539 P-CR Approval 23.304: Update Identifiers for 5G ProSe UE-to-Network Relay . Ericsson Rel-17 Revision of (Postponed) S2-2103847 from S2-145E. Merged into S2-2106881 (withdrawn). CC#4: Noted Deng Qiang (CATT) comment and proposes to partially merge this paper into S2-2106094.
Fei (OPPO) comments.
Xiaoyan Shi (Interdigital) comments.
Mehrdad (Samsung) suggests to merge 5539, 5877, 6017 and 6094 and adopt one as the baseline.
Xiaoyan Shi (Interdigital) suggests to merge this contribution to S2-2106094.
Zhang (Ericsson) agree to merge the paper into S2-2106094
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105877 P-CR Approval 23.304: Additional IDs in discovery message for relay. OPPO Rel-17 Merged into S2-2106881 (withdrawn). CC#4: Noted Deng Qiang (CATT) proposes to merge this paper into S2-2106094.
Fei (OPPO) responds
Zhang (Ericsson) provides comments
Mehrdad (Samsung) suggests to merge 5539, 5877, 6017 and 6094 and adopt one as the baseline.
Xiaoyan Shi (Interdigital) suggests to merge this contribution to S2-2106094.
Deng Qiang (CATT) suggests to merge this contribution to S2-2106094.
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) has assumed this was MERGED into 6094 (or note if not merged)
Mehrdad (Samsung) also suggests to mark this either as merged to 6094 or noted.
Fei (OPPO) responds to Mehrdad (Samsung) and Steve (Huawei)
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106017 P-CR Approval 23.304: TS 23.304: Relay TAI for UE-to-Network Relay. vivo Rel-17 Merged into S2-2106881 (withdrawn). CC#4: Noted Deng Qiang (CATT) proposes to merge this paper into S2-2106094.
Fei (OPPO) comments.
Wen (vivo) replies.
Zhang (Ericsson) provides comments
Xiaoyan Shi (interdigital) agrees with Zhang to include TAI into Relay Discovery Additional Information message.
Mehrdad (Samsung) suggests to merge 5539, 5877, 6017 and 6094 and adopt one as the baseline.
Deng Qiang (CATT) suggests to merge this contribution to S2-2106094.
Wen (vivo) agrees to merge this contribution to S2-2106094.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106094 P-CR Approval 23.304: TS 23.304: Identifiers for UE-to-Network Relay discovery. CATT Rel-17 r13 agreed. Revised to S2-2106881, merging S2-2105539, S2-2105877 and S2-2106017. CC#4: Noted Xiaoyan Shi (Interdigital) comments.
Wen (vivo) comments and provides r01.
Deng Qiang (CATT) responds and provides r02.
Wen (vivo) responds to Deng Qiang (CATT).
Mehrdad (Samsung) suggests to merge 5539, 5877, 6017 and 6094 and adopt one as the baseline.
Xiaoyan Shi (Interdigital) suggests to use S2-2106094 as the baseline.
Deng Qiang (CATT) propose to establish some agreements before next revision, and correct the email subject.
Zhang (Ericsson) provides comments
Steve (Huawei) comments
Xiaoyan Shi (interdigital) replies to Zhang (Ericsson)
Wen (vivo) responds to Zhang (Ericsson)
Deng Qiang (CATT) ask to people to comment on the right thread as this email subject is not correct.
Fei (OPPO) comments.
Deng Qiang (CATT) replies to Fei (OPPO).
Mehrdad (Samsung) comments on all revisions.
Steve (Huawei) is ok with r04.
Xiaoyan Shi (Interdigital) provides r05 to remove description that Discovery Additional information message is used for relay selection.
Mehrdad (Samsung) has concern on original version and all revisions of this PCR
Fei (OPPO) comments and provides r06.
Deng Qiang (CATT) comments on r05 and r06, and provides r07.
Fei (OPPO) comments on r07.
Wen (vivo) comments on r07.
Deng Qiang (CATT) ask questions to Fei (OPPO) and Wen (vivo).
Fei (OPPO) responds to Deng Qiang (CATT)
Deng Qiang (CATT) replies to Fei (OPPO) and provides r08.
Fei (OPPO) responds to Deng Qiang (CATT).
Wen (vivo) replies to Deng Qiang (CATT).
Fei (OPPO) responds to Zhang (Ericsson)
Deng Qiang (CATT) comments.
Mehrdad comments on all revisions.
Steve (Huawei) comments, provides r09
Mehrdad (Samsung) provides r10
Steve (Huawei) provides r11
Mehrdad (Samsung ) comments on r11
Deng Qiang (CATT ) provide r12 on top of r10.
Wen (vivo ) comments
Mehrdad (Samsung) replies to Huawei.
Steve (Huawei) provides r13
Mehrdad (Samsung) replies to Vivo
Wen(vivo) replies to Mehrdad (Samsung)
Mehrdad (Samsung) replies to further Vivo
Wen (vivo) replies to Mehrdad
Mehrdad (Samsung) cannot agree with r13
Fei (OPPO) replies to Mehrdad (Samsung)
Deng Qiang (CATT) comments on r13.
Hong (Qualcomm) comments.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) asks to go with r12.
Zhang (Ericsson) object r12, can accept r13
Deng Qiang (CATT) clarifies to Zhang (Ericsson) r13 removed TAI for Layer-3 entirely.
Xiaoyan Shi (Interdigital) prefers r13 and can live with r12 with adding EN.
Mehrdad (Samsung) is ok with r12 and r10 but objects to all other revisions .
Fei (OPPO) comments and is OK with r12 at this meeting for progress.
Deng Qiang responds to Zhang (Ericsson).
Zhang (Ericsson) prefers r09, can accept r13 and object all the other revisions
Steve (Huawei) another option...
Steve (Huawei) I liked r09
Mehrdad (Samsung) cannot agree with r09 or r13 and already objected to those revisions.
Deng Qiang (CATT) asks what about keeping second change only in r12 and thus response LS to RAN2.
Mehrdad (Samsung) clarifies to Ericsson that there was no Relay with N3IWF in ProSe LTE
Mehrdad (Samsung) agrees with CATT proposal, i.e. keeping second change only in r12 and thus response LS to RAN2.
Fei (OPPO) responds to Zhang (Ericsson) .
Mehrdad comment.
==== 8.X, 9.X Final Deadline ====
Mehrdad (Samsung) does not agree with Steve's view.
Deng Qiang (CATT) r13 should not be approved with at least two objections, proposes to be NOTED at CC#4.
Noted
8.8 S2-2106881 P-CR Approval 23.304: TS 23.304: Identifiers for UE-to-Network Relay discovery. CATT Rel-17 Revision of S2-2106094r13, merging S2-2105539, S2-2105877 and S2-2106017. CC#4: WITHDRAWN Withdrawn
8.8 - - - Mobility restriction for Relay UE and Remote UE - - Docs:=6 -
8.8 S2-2105781 P-CR Approval 23.304: Common identifiers for 5G ProSe UE-to-Network Relay. Samsung Rel-17 Postponed LaeYoung (LGE) provides comment.
Mehrdad (Samsung) replies to LG.
Zhang (Ericsson) provides comments
LaeYoung (LGE) responds to Mehrdad (Samsung) and Zhang (Ericsson).
Xiaoyan Shi (Interdigital) asks question for clarification.
Deng Qiang (CATT) comments.
Mehrdad (Samsung) replies further to LG, Ericsson, InterDigital and CATT.
Xiaoyan Shi (Interdigital) asks further questions.
Fei (OPPO) comments.
Steve (Huawei) comments
Mehrdad (Samsung) replies to InterDigital and OPPO.
Xiaoyan Shi (Interdigital) comments.
Fei (OPPO) responds to Mehrdad (Samsung)
Mehrdad (Samsung) replies to OPPO.
Mehrdad (Samsung) provides r01.
Zhang (Ericsson) propose to NOTE the paper
Mehrdad (Samsung) explains to Ericsson that this is related to mobility restrictions
Deng Qiang (CATT) comments on r01.
Mehrdad (Samsung) replies to CATT
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this paper.
Steve (Huawei) agrees should be noted.
Mehrdad (Samsung) suggests to mark this as POSTPONED until mobility restrictions are fully clarified.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2105782 P-CR Approval 23.304: Mobility restrictions for ProSe UE-to-Network Relay and Remote UE. Samsung Rel-17 Merged into S2-2106882 Deng Qiang (CATT) proposed to merge it into S2-2106015 per ProSe CC discussion.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) also thinks this paper can be merged into S2-2106015.
Mehrdad (Samsung) agrees to mark this pCR as merged into S2-2106015.
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2105977 P-CR Approval 23.304: Update [6.3] UE-to-NW Relay Mobility Restriction. Panasonic Corporation, DENSO CORPORATION Rel-17 Merged into S2-2106882 Deng Qiang (CATT) comments.
Mehrdad (Samsung) suggests to merge this to 6015.
Liu Wei(Panasonic) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2106015 P-CR Approval 23.304: TS 23.304: Mobility Restrictions for U2N relay. vivo Rel-17 r18 agreed. Revised to S2-2106882, merging S2-2105782, S2-2105977 and S2-2106424 Steve (Huawei) comments
Xiaoyan Shi (Interdigital) provides r01.
LaeYoung (LGE) asks a Q.
Fei (OPPO) comments
Wen (vivo) responds and provides r02
Fei (OPPO) comments.
Mehrdad (Samsung) comments on r02
Xiaoyan Shi (Interdigital) replies to LaeYoung, Fei and provides r03.
LaeYoung (LGE) comments.
Deng Qiang (CATT) comments.
Fei (OPPO) responds to Xiaoyan (Interdigital)
Wen (vivo) replies to the comments from Deng Qiang (CATT), Fei (OPPO), Steve (Huawei), LaeYoung (LGE), Mehrdad (Samsung) .
Xiaoyan Shi (Interdigital) replies comments .
LaeYoung (LGE) responds to Xiaoyan Shi (Interdigital).
Judy (Ericsson) provide comments
Mehrdad (Samsung) comments on r04
Xiaoyan Shi (Interdigital) replies to LaeYoung and Mehrdad.
Mehrdad (Samsung) replies to InterDigital and provides r06.
Wen (vivo) replies and provides r07.
Steve (Huawei) provides r08
Hong (Qualcomm) comments on r08.
LaeYoung (LGE) provides r09.
Wen (vivo) comments.
LaeYoung (LGE) replies to Wen (vivo).
Mehrdad (Samsung) objects to r09
Mehrdad (Samsung) addresses questions from Qualcomm and provides r10 based on r08.
LaeYoung (LGE) asks a Q to Mehrdad (Samsung).
Steve (Huawei) comments, provides r11.
Mehrdad (Samsung) replies to LGE.
LaeYoung (LGE) provides r12 on top of r09.
Mehrdad (Samsung) comments on r12
Xiaoyan Shi (Interdigital) prefers r10 and r11.
Mehrdad (Samsung) provides r13.
Mehrdad (Samsung) also prefers with r10 or r11. Can live with r13 but objects to r09 and r12.
LaeYoung (LGE) provides r14 on top of r13.
Deng Qiang (CATT) comments on r14.
Steve (Huawei) keeping it simple ok
Mehrdad (Samsung) replies to CATT
Mehrdad (Samsung) replies to Huawei.
LiuWei (Panasonic) provides r15 on top of r14.
Mehrdad (Samsung) comments on r15.
Xiaoyan Shi (Interdigital) objects all version from r12 to r15 and provides r16
Mehrdad (Samsung) objects to R15 and R16.
Mehrdad (Samsung) provides r17.
Xiaoyan Shi (interdigital) suggest to move Non-allowed area discussion to next meeting and provides r18.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) can accept r17 and r18 for peace. ;-)
Steve (Huawei) can live with r18
Deng Qiang (CATT) asks whether resolving the new EN requires a Cat B CR next meeting.
Xiaoyan Shi (Interdigital) thinks we don't need exception. Cat F CR can work well since it's 'correction' rather than 'addition of feature' (Feature is there).
Fei (OPPO) supports Xiaoyan (Interdigital)'s understanding.
Mehrdad (Samsung) can live with r18 with the assumption that we will handle non-allowed area as Cat F CR in the next meeting.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106882 P-CR Approval 23.304: TS 23.304: Mobility Restrictions for U2N relay. Vivo, Interdigital Inc., Samsung Rel-17 Revision of S2-2106015r18, merging S2-2105782, S2-2105977 and S2-2106424. Approved Approved
8.8 S2-2106424 P-CR Approval 23.304: TS 23.304: 5.X Mobility restriction for 5G ProSe UE-to-Network Relay. Interdigital Inc. Rel-17 Merged into S2-2106882 Deng Qiang (CATT) proposed to merge it into S2-2106015 per ProSe CC discussion.
Xiaoyan Shi (Interdigital) is fine to merge this contribution into S2-2106015.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 - - - Path switching for Layer-3 UE-NW Relay - - Docs:=2 -
8.8 S2-2105545 P-CR Approval 23.304: Update [6.5.1.2] UE to Network Relay Communication, switching between Relays. Ericsson Rel-17 Approved Hannu (Nokia) asks whether everyone is OK to remove SA2 extension item switch between two different Relay UEs in L3 relaying? Both options have been proposed and if this CR is agreed, then Nokia paper in S2-2106205 is not needed.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106205 P-CR Approval 23.304: Path switch from one indirect PC5 connection to another in L3 U2N relaying. Nokia, Nokia Shanghai Bell Rel-17 Noted. Covered by S2-2105545 Deng Qiang (CATT) prefers the WF in S2-2105545.
Mehrdad (Samsung) suggests to merge this into S2-2105545.
Hannu (Nokia) asks whether feature parity is required between L2 and L3 relaying?
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - Layer-2 and Layer-3 UE-NW Relay distinction - - Docs:=3 -
8.8 S2-2105874 P-CR Approval 23.304: L2 and L3 distinction for U2N relay discovery. OPPO Rel-17 Merged into S2-2106885 Deng Qiang (CATT) comments.
Fei (OPPO) responds to Deng Qiang (CATT)
Changhong (Intel) proposes to merge it into S2-2106467.
Hong (Qualcomm) suggest to consider it merged into S2-2106467.
Fei (OPPO) is fine to mark this PCR merged into S2-2106467.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2106018 P-CR Approval 23.304: TS 23.304: Relay type distinction. vivo Rel-17 r02 agreed. Revised to S2-2106883 Deng Qiang (CATT) comments.
Zhang (Ericsson) provides comments
Steve (Huawei) comments
Wen (vivo) responds to some comments
Fei (OPPO) comments.
Changhong (Intel) proposes to merge it into S2-2106467.
Wen (vivo) ask a question for clarification.
Fei (OPPO) responds to to Wen (vivo)
Wen (vivo) responds to Fei (OPPO)
Fei (OPPO) responds to Wen (vivo)
Hong (Qualcomm) replied to Wen (vivo).
Wen (vivo) responds to Hong and Fei (OPPO).
Steve (Huawei) comments, provides r02
Wen (vivo) is fine with r02
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) is OK with r02
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106883 P-CR Approval 23.304: TS 23.304: Relay type distinction. Vivo Rel-17 Revision of S2-2106018r02. Approved Approved
8.8 - - - IPv6 Prefix Delegation for Layer-3 UE-NW Relay - - Docs:=4 -
8.8 S2-2105902 CR Approval 23.501 CR3106 (Rel-17, 'B'): IP prefix delegation LG Electronics, Ericsson, OPPO Rel-17 Noted Steve (Huawei) Is this the correct spec? 304 is better. Need a pCR to put it in.
LaeYoung (LGE) provides answer to Steve (Huawei).
Judy (Ericsson) comment
Gerald (Matrixx) is supporting a generic solution
Steve (Huawei) comments
Deng Qiang (CATT) also prefers a generic solution.
LaeYoung (LGE) provides comment.
Fei (OPPO) comments.
LaeYoung (LGE) responds to Fei (OPPO).
LaeYoung (LGE) replies to Steve (Huawei).
LaeYoung (LGE) responds to Steve (Huawei).
Deng Qiang (CATT) comments.
Gerald (Matrixx) with comment to Steve (Huawei)
Steve (Huawei) adding a new system wide generic feature should be TEI18? - let's keep it as ProSe only.
LaeYoung (LGE) answers to Steve (Huawei).
Deng Qiang (CATT) can live with putting IPv6 prefix delegation in TS 23.304 and thanks LaeYoung (LGE) effort.
Steve (Huawei) thanks LaeYoung and suggests we now NOTE this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105879 CR Approval 23.502 CR3004 (Rel-17, 'B'): IP prefix delegation OPPO Rel-17 Noted Judy (Ericsson) comments that the new parameter is not needed as it is already supported (explained) and propose to note this paper.
Fei (OPPO) responds to Judy (Ericsson)
Judy (Ericsson) responds to Fei (OPPO).
Steve (Huawei) comments
Fei (OPPO) responds to Steve (Huawei)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105880 CR Approval 23.503 CR0631 (Rel-17, 'B'): IP prefix delegation OPPO Rel-17 New title proposed for revision of this CR. r02 agreed. Revised to S2-2106974 Judy (Ericsson) comments that the new parameter is not needed as it is already supported (explained below) and propose to note this paper.
Fei (OPPO) responds to Judy (Ericsson).
Judy (Ericsson) provide r01
Steve (Huawei) comments
Fei (OPPO) provides r02 to correct the title of the CR.
==== 8.X, 9.X Revisions Deadline ====
Fei (OPPO) responds to Hong (Qualcomm) and provides an updated version to drafts
Hong (Qualcomm) comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106980 CR Approval 23.503 CR0631R1 (Rel-17, 'B'): IP prefix delegation for ProSe OPPO, Ericsson Rel-17 Revision of S2-2105880r02. Approved Agreed
8.8 - - - Remote UE traffic handling - - Docs:=6 -
8.8 S2-2105730 P-CR Approval 23.304: Update on Remote UE traffic handling. Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105732 P-CR Approval 23.304: RSC determination by the Remote UE. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106884 Zhang (Ericsson) provides comments
Xiaoyan Shi (Interdigital) supports option#1 and objects option#2 and option#3.
Mehrdad (Samsung) is also OK with option#1 but cannot agree with option#2 or option #3
Changhong (intel) disagrees with Option #1 and asks Mehrdad and Xiaoyan question.
Steve (Huawei) comments
Mehrdad (Samsung) asks for clarification from Intel and Huawei
Xiaoyan Shi (Interdigital) objects option #2 and #3.
Steve (Huawei) comments on relationship between S2-2106467 and S2-2105732
Changhong (Intel) has concern with Option #1 and #3, asks question to Mehrdad and Xiaoyan.
Xiaoyan Shi (Interdigital) replies to Changhong.
Hong (Qualcomm) comments.
Mehrdad (Samsung) replies to Intel and Huawei.
Mehrdad (Samsung) replies to Huawei.
Hong (Qualcomm) replies to Steve.
Hong (Qualcomm) suggest to NOTE this paper, and consider any needed changes merged into 6457.
Changhong (Intel) shares Hong's view.
Deng Qiang (CATT) also thinks current spec works and neither of options in this paper is needed.
Steve (Huawei) provides r01
Steve (Huawei) comments, to correct typo.
Mehrdad (Samsung) comments on r01
Steve (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) propose to NOTE the paper
Xiaoyan Shi (Interdigital) is fine with r02.
TAO(VC) this will be noted if Fu is not convinced.
Mehrdad (Samsung) can live with r02 but objects to original version and other revisions.
Steve (Huawei) r02 is ok.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106884 P-CR Approval 23.304: RSC determination by the Remote UE. Huawei, HiSilicon Rel-17 Revision of S2-2105732r02. Approved Approved
8.8 S2-2105733 CR Approval 23.503 CR0624 (Rel-17, 'B'): Addition of Relay Service Code to Route Selection Descriptor Huawei, HiSilicon Rel-17 Noted Zhang (Ericsson) ask for clarification
Steve (Huawei) comments
Hong (Qualcomm) suggest to NOTE this CR.
Changhong (Intel) shares Hong's view.
Deng Qiang (CATT) also suggest to NOTE this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106467 P-CR Approval 23.304: TS 23.304: Relay Service Code configuration for Remote UE using UE-to-Network Relay service. Qualcomm Incorporated Rel-17 r07 agreed. Revised to S2-2106885, merging S2-2105874 Zhang (Ericsson) provides comments
Xiaoyan Shi (Interdigital) provides comments
Hong (Qualcomm) comments and provides r01.
Fei (OPPO) comments.
Hong (Qualcomm) replies to Fei.
Fei (OPPO) responds to Hong (Qualcomm).
Hong (Qualcomm) provides r02.
Changhong (Intel) provides r03.
Mehrdad (Samsung) comments
Steve (Huawei) comments on relationship between S2-2106467 and S2-2105732
Changhong (Intel) provides r04 and r05 and asks to ignore r04.
Xiaoyan Shi (Interdigital) provides r06.
Hong (Qualcomm) provides r07.
Zhang (Ericsson) is OK with r07
Fei (OPPO) is fine with r07.
Steve (Huawei) provides r08
Hong (Qualcomm) asks for clarification regarding r08.
Hong (Qualcomm) comments.
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) cannot accept r08. Prefers r07. Can accept r06.
Hong (Qualcomm) suggests to go with r07.
Steve (Huawei) why is the indication needed?
Deng Qiang (CATT) responds to Steve (Huawei).
Hong (Qualcomm) replies to Steve.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106885 P-CR Approval 23.304: TS 23.304: Relay Service Code configuration for Remote UE using UE-to-Network Relay service. Qualcomm Incorporated, Intel Rel-17 Revision of S2-2106467r07, merging S2-2105874. Approved Approved
8.8 - - - QoS handling for Layer-3 UE-NW Relay - - Docs:=6 -
8.8 S2-2105540 P-CR Approval 23.304: Clarify QoS Handling for Layer-3 UE-to-Network Relay in clause 5.6.2.1. Ericsson Rel-17 Revision of (Postponed) S2-2103844 from S2-145E. Merged into S2-2106664 Yali (OPPO) proposes to merge this paper into S2-2105623
Zhang (Ericsson) agrees to merge the paper into S2-2105623
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2105623 P-CR Approval 23.304: TS 23.304: Clarification on PC5 QoS context and QoS Info. OPPO, LG Electronics Rel-17 CC#4: r04 + changes agreed. Revised, merging S2-2105540, to S2-2106664. Mehrdad (Samsung) provides r01.
Yali (OPPO) provides r02.
Zhang (Ericsson) provides comments
Zhang (Ericsson) is fine with r02
Hong (Qualcomm) requires clarification regarding r02.
Yali (OPPO) replies to Hong (Qualcomm).
Walter (Philips) provides comment
Hong (Qualcomm) replies to Yali.
Yali (OPPO) replies to Hong and Walter, and provides r03.
Zhang (Ericsson) is OK with r03
Hong (Qualcomm) replies and provides r04.
Yali (OPPO) replies to Hong, prefers r03 but can live with r04.
Hong (Qualcomm) comments.
Yali (OPPO) replies to Hong.
==== 8.X, 9.X Revisions Deadline ====
Yali (OPPO) provides 'S2-2105623r05 after rev deadline' in draft folder.
Hong (Qualcomm) prefers r04.
Wen (vivo) is fine with 'S2-2105623r05 after rev deadline' and hope it can be discussed in CC#4.
Steve (Huawei) is fine with either r03 or 'r05 after rev deadline'.
Zhang (Ericsson) prefers r04 and object r05
Steve (Huawei) objects to r04, prefers r03/r06
Wen (vivo) objects to r04, prefers r03/r05
Yali (OPPO) provides 'S2-2105623r06' in draft folder.
Wen (vivo) is fine with 'S2-2105623r06'.
Steve (Huawei) is ok 'S2-2105623r06' in draft folder.
Mehrdad (Samsung) thinks this paper should be discussed along S2-2105780r12 for CC#4 as some changes have dependency .
Zhang (Ericsson) is OK with r06 and agree we need alignment with S2-2105780
Yali (OPPO) asks to mark this pCR for CC#4, and open S2-2105780 first in CC#4, proposes to approve r04 with changing 'used to derive' to 'interpreted as' in clause 5.6.2.1.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106664 P-CR Approval 23.304: TS 23.304: Clarification on PC5 QoS context and QoS Info. OPPO, LG Electronics, Samsung, Ericsson Rel-17 Revision of S2-2105623r04 + changes, merging S2-2105540. Approved Approved
8.8 S2-2105731 P-CR Approval 23.304: Update on L3 UE-to-Network Relay QoS. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106886 Mehrdad (Samsung) provides r01.
Yali (OPPO) proposes to NOTE this pCR.
Steve (Huawei) provides r02
Yali (OPPO) can live with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106886 P-CR Approval 23.304: Update on L3 UE-to-Network Relay QoS. Huawei, HiSilicon Rel-17 Revision of S2-2105731r02. Approved Approved
8.8 S2-2106509 P-CR Approval 23.304: TS 23.304: Clarifying use of QFI for Downlink Traffic over L3 relay. Philips International B.V. Rel-17 Noted Steve (Huawei) asks a question
Walter (Philips) responds to Steve (Huawei)
Yali (OPPO) comments
Zhang (Ericsson) provides comments
Walter (Philips) responds to Oppo and Ericsson
Yali (OPPO) replies to Walter (Philips)
Myungjune (LGE) provides comments.
Mehrdad (Samsung) has concern on this CR
Steve (Huawei) should be noted
Walter (Philips) responds to comments
==== 8.X, 9.X Revisions Deadline ====
Zhang (Ericsson) propose to NOTE the paper
Mehrdad (Samsung) also suggests to NOTE this paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - App Layer Group ID - - Docs:=6 -
8.8 S2-2105481 P-CR Agreement 23.304: Provisioning parameters for public safety discovery out of coverage operations. MITRE Rel-17 Noted Steve (Huawei) comments
Mehrdad (Samsung) comments
Xiaoyan Shi (interdigital) comments
LaeYoung (LGE) proposes to NOTE this pCR.
Fei (OPPO) also proposes to note this PCR
Wen (vivo) proposes to NOTE this pCR as well.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105549 P-CR Approval 23.304: Replacing 'Discovery Group ID' with 'Application Layer Group ID' in clauses 6.3.2.2.2 and 6.3.2.2.3. Ericsson Rel-17 Merged into S2-2106887 Steve (Huawei) should be merged with S2-2105734?
Zhang (Ericsson) agree to merge into S2-2105734 and co-sign
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2105734 P-CR Approval 23.304: Addition of Application Layer Group ID to Identifiers for 5G ProSe Direct Discovery. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106887, merging S2-2105549 Deng Qiang (CATT) comments
Guanglei (Huawei) replies Deng Qiang (CATT) and provides r01.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106887 P-CR Approval 23.304: Addition of Application Layer Group ID to Identifiers for 5G ProSe Direct Discovery. Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2105734r01, merging S2-2105549. Approved Approved
8.8 S2-2105878 P-CR Approval 23.304: Reference update and application group id . OPPO Rel-17 r01 agreed. Revised to S2-2106888 Steve (Huawei) comments on partial merge with S2-2105734
Fei (OPPO) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106888 P-CR Approval 23.304: Reference update and application group id . OPPO Rel-17 Revision of S2-2105878r01. Approved Approved
8.8 - - - Architecture and ref points corrections - - Docs:=5 -
8.8 S2-2106093 P-CR Approval 23.304: TS 23.304: Correction on architecture and reference point. CATT, Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105720 P-CR Approval 23.304: Alignment of reference point names. Huawei, HiSilicon Rel-17 Noted. Covered by S2-2106093 Deng Qiang (CATT) comments and proposes this merged into S2-2106093.
Steve (Huawei) it's good to merge with 6093, let's do it!
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106299 CR Approval 23.501 CR3193 (Rel-17, 'F'): Alignment of 5G ProSe reference point names Huawei, HiSilicon Rel-17 Merged into S2-2106889 Deng Qiang (CATT) proposed it merged into S2-2105544r01.
Steve (Huawei) it's good to merge with 5544, let's do it!
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2105544 CR Approval 23.501 CR3034 (Rel-17, 'F'): Update the naming convention for the reference points for 5G ProSe Ericsson Rel-17 r01 agreed. Revised to S2-2106889, merging S2-2106299 Deng Qiang (CATT) provides r01 to generalize the description.
Judy (Ericsson) comments that Deng Qiang (CATT)'s proposal is also my preferred way of handling documentation.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106889 CR Approval 23.501 CR3034R1 (Rel-17, 'F'): Update the naming convention for the reference points for 5G ProSe Ericsson Rel-17 Revision of S2-2105544r01, merging S2-2106299. Approved Agreed
8.8 - - - ProSe UE capabilities and policy provisioning - - Docs:=7 -
8.8 S2-2105541 P-CR Approval 23.304: Updates on usage of UE capabilities and ProSe Services. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105546 P-CR Approval 23.304: Update [6.6.2] on 5G ProSe Capability sent from AMF to PCF. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105548 P-CR Approval 23.304: UE Policy Provisioning Request in Registration Request. Ericsson, LG Electronics Rel-17 Noted Changhong (Intel) objects to this paper.
Hong (Qualcomm) propose to NOTE.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105551 CR Approval 23.503 CR0612 (Rel-17, 'F'): UE Policy Container with 5G ProSe Policy Provisioning Request and alignment with stage 3 Ericsson, LG Electronics Rel-17 Noted Judy (Ericsson) provides r01
Hong (Qualcomm) comments, and suggests to send LS to CT1 to align with SA2 text.
Judy (Ericsson) responds to Hong (Qualcomm).
LaeYoung (LGE) provides comment.
Fei (OPPO) comments and asks questions.
Hong (Qualcomm) replies to Judy.
Changhong (Intel) replies to Judy and objects to this paper.
Changhong (Intel) replies to Fei.
Changhong (Intel) further explains why V2XP and ProSeP provisioning request indication in UE Policy container is needed.
Judy (Ericsson) asks a further question.
Changhong (Intel) replies to Judy.
Hong (Qualcomm) comments.
Judy (Ericsson) responds to Hong (Qualcomm) and Changhong (Intel)
Changhong (Intel) relies to Judy.
Hong (Qualcomm) suggest to NOTE this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106697 LS OUT Approval LS on UE POLICY PROVISIONING REQUEST message SA WG2 Rel-17 Created at CC#2. Approved Deng Qiang (CATT) shared the draft LS to CT1 based on discussion of S2-2105551 and S2-2105553, and asks Tao (Chair) to put this LS under chairnote AI#8.8
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) thinks this LS is not controversial but stable, so we can check r00 can be approved.
Deng Qiang (CATT) asks to check whether r00 can be approved.
TAO(VC) ask can we go with r00
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105725 P-CR Approval 23.304: Clarification on 5G ProSe Capability and the PCF. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106890 LaeYoung (LGE) provides r01 to take some change in clause 6.2.2 out in order to avoid clash with 5548 (Ericsson, LGE).
Mehrdad (Samsung) cannot agree with original version and r01 and provides r02.
Changhong (Intel) provides r03 and objects to r00, r01 and r02.
Steve (Huawei) comments and asks which are the right procedures to refer to?
Changhong (Intel) answers to Steve.
==== 8.X, 9.X Revisions Deadline ====
Mehrdad (Samsung) is OK with r03 but objects to original version and r01.
Steve (Huawei) is ok with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106890 P-CR Approval 23.304: Clarification on 5G ProSe Capability and the PCF. Huawei, HiSilicon Rel-17 Revision of S2-2105725r03. Approved Approved
8.8 - - - PC5 link mngt for UE-NW Relay - - Docs:=8 -
8.8 S2-2105624 P-CR Approval 23.304: TS 23.304: Layer-2 link management over PC5 for U2N Relay. OPPO Rel-17 r06 agreed. Revised to S2-2106891 Xiaoyan Shi (Interdigital) asks questions for clarification.
Yali (OPPO) replies to Xiaoyan.
Zhang (Ericsson) provides comments
Yali (OPPO) provides r01.
Xiaoyan Shi (interdigital) is fine with r01.
Steve (Huawei) provides r02, bringing over the last bits of the merge from S2-2105727
Hong (Qualcomm) comments and does not agree to exclude LIU procedure.
Yali (OPPO) provides r03 and r04, prefers r03, but can live with r04.
Wen(vivo) prefers r03 and comments on r04.
Walter (Philips) has an additional comment
Hannu (Nokia) asks why is the L2 link modification not applicable on L2 relaying?
Hannu (Nokia) asks what does the 'UE oriented' Layer-2 link mean in r03 and r04?
Yali (OPPO) replies to Hannu.
Hong (Qualcomm) replies to Yali.
Steve (Huawei) Prefers to keep removal of link on revocation (r04).
Yali (OPPO) provides r05.
Xiaoyan Shi (Interdigital) provides r06 with rewording on last paragraph.
Yali (OPPO) is fine with r06.
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) is fine with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106891 P-CR Approval 23.304: TS 23.304: Layer-2 link management over PC5 for U2N Relay. OPPO Rel-17 Revision of S2-2105624r06. Approved Approved
8.8 S2-2105726 P-CR Approval 23.304: Clarification on Layer-2 link establishment for UE-to-Network Relay. Huawei, HiSilicon Rel-17 r07 agreed. Revised to S2-2106892 Fei (OPPO) comments and provides r01.
Wen (vivo) comments and provides r02.
Deng Qiang (CATT) comments.
Steve (Huawei) comments
Hong (Qualcomm) provides r03.
Steve (Huawei) comments, provides r04.
Hong (Qualcomm) replies and objects to r04.
Deng Qiang (CATT) shared the same concern on r04 with Hong (Qualcomm).
Zhang (Ericsson) provides comments
Steve (Huawei) provides r05
LaeYoung (LGE) comments.
Yali (OPPO) comments
LaeYoung (LGE) provides comment.
Steve (Huawei) Agrees with the analysis, provides r06.
Wen (vivo) also thinks the separate PC5 links for relay and non-relay traffic are simple and easier to be managed.
Walter (Philips) thinks separate PC5 links for relay and non-relay traffic are also needed from security perspective
Ihab Guirguis (FirstNet) FirstNet is concerned that this will limit the flexibility to utilize Layer-3 UE-to-Network relay solution to support UE-to-UE relay
Hong (Qualcomm) OBJECTs all revisions up to r06, and provides r07.
Xiaoyan Shi (Interdigital) also agrees 'no-sharing' link and prefers r06.
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) replies to Xiaoyan and can only accept r07.
Zhang (Ericsson) prefer r06, but can accept r07
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106892 P-CR Approval 23.304: Clarification on Layer-2 link establishment for UE-to-Network Relay. Huawei, HiSilicon Rel-17 Revision of S2-2105726r07. Approved Approved
8.8 S2-2105727 P-CR Approval 23.304: Clarification on Layer-2 link release for UE-to-Network Relay. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106893 Yali (OPPO) comments.
Steve (Huawei) provides r01
Yali (OPPO) is ok with r01.
Deng Qiang (CATT) comments on r01.
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) comments
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) can live with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106893 P-CR Approval 23.304: Clarification on Layer-2 link release for UE-to-Network Relay. Huawei, HiSilicon Rel-17 Revision of S2-2105727r01. Approved Approved
8.8 S2-2106201 P-CR Approval 23.304: PC5 link for UE-to-Network relay in CM-IDLE. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106894 LaeYoung (LGE) provides comment.
Wen (vivo) provides comment.
Jianning (Xiaomi) asks question for clarification
Zhang (Ericsson) provides comments
Xiaoyan Shi (Interdigital) provides comments
Hannu (Nokia) replies to comments and provides r01.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) is fine with r01.
Xiaoyan Shi (Interdigital) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106894 P-CR Approval 23.304: PC5 link for UE-to-Network relay in CM-IDLE. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106201r01. Approved Approved
8.8 - - - DST L2 ID clarifications - - Docs:=6 -
8.8 S2-2105875 P-CR Approval 23.304: Clarification on destination L2 ID. OPPO Rel-17 r01 agreed. Revised to S2-2106895 Zhang (Ericsson) provides comments
Hao Dong (ZTE) comments
LaeYoung (LGE) thinks that the first change is NOT needed.
Fei (OPPO) responds to Zhang (Ericsson), Hao (ZTE) and LaeYoung (LGE).
Wen (vivo) comments.
Fei (OPPO) responds to Zhang (Ericsson).
Steve (Huawei) comments
Zhang (Ericsson) provide comments
Deng Qiang (CATT) comments 1st change is not correct based on last meeting conclusion.
Fei (OPPO) provides r01.
Zhang (Ericsson) is OK with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106895 P-CR Approval 23.304: Clarification on destination L2 ID. OPPO Rel-17 Revision of S2-2105875r01. Approved Approved
8.8 S2-2106347 P-CR Approval 23.304: Clarification on Destination Layer-2 ID(s) . Samsung Rel-17 r03 agreed. Revised to S2-2106896 Zhang (Ericsson) provides comments
Mehrdad (Samsung) replies to Ericsson.
Hong (Qualcomm) comments.
Mehrdad (Samsung) replies to Qualcomm
Fei (OPPO) supports this proposal in general
Steve (Huawei) comments
Mehrdad (Samsung) replies to Huawei.
Xiaoyan Shi (Interdigital) comments.
LaeYoung (LGE) provides comment.
Xiaoyan Shi (Interdigital) is fine with r03.
LaeYoung (LGE) is fine with r03.
Fei (OPPO) is fine with r03 as well.
Zhang (Ericsson) is fine with r03
Steve (Huawei) does r03 go far enough?
Mehrdad (Samsung) feels r03 is good enough for this meeting.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106896 P-CR Approval 23.304: Clarification on Destination Layer-2 ID(s) . Samsung Rel-17 Revision of S2-2106347r03. Approved Approved
8.8 S2-2106014 P-CR Approval 23.304: TS 23.304: DST L2 ID of group member discovery. vivo Rel-17 r01 agreed. Revised to S2-2106897 Steve (Huawei) comments on partial overlap with S2-2105734
Wen (vivo) agree with merging the overlap into S2-2105734 and only keep the first change in r01
Hao Dong (ZTE) comments.
Wen (vivo) replies to Hao Dong (ZTE).
Deng Qiang (CATT) asks question for clarification.
Wen (vivo) replies to Deng Qiang (CATT).
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106897 P-CR Approval 23.304: TS 23.304: DST L2 ID of group member discovery. Vivo Rel-17 Revision of S2-2106014r01. Approved Approved
8.8 - - - Other corrections and clarifications - - Docs:=42 -
8.8 S2-2105550 P-CR Approval 23.304: Missing NEF in clause 4.3 Functional Entities. Ericsson Rel-17 r01 agreed. Revised to S2-2106898 Steve (Huawei) provides r01, for editorial changes.
Judy (Ericsson) prefers r00, but can live with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106898 P-CR Approval 23.304: Missing NEF in clause 4.3 Functional Entities. Ericsson Rel-17 Revision of S2-2105550r01. Approved Approved
8.8 S2-2105722 P-CR Approval 23.304: Clarification on AQP and MBS support in UE-to-Network Relay. Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106899 Judy (Ericsson) comments
Deng Qiang (CATT) comments.
Hong (Qualcomm) asks for clarifications on AQP support.
Yali (OPPO) comments.
Steve (Huawei) provides r01
Hong (Qualcomm) replies to Yali.
Wen (vivo) comments.
Deng Qiang (CATT) comments and provides r02.
Steve (Huawei) provides r03
Hong (Qualcomm) comments on r03.
Steve (Huawei) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106899 P-CR Approval 23.304: Clarification on AQP and MBS support in UE-to-Network Relay. Huawei, HiSilicon Rel-17 Revision of S2-2105722r04. Approved Approved
8.8 S2-2105723 P-CR Approval 23.304: Clarification on PC5 QoS parameters provisioning. Huawei, HiSilicon Rel-17 Noted Zhang (Ericsson) provides comments
Steve (Huawei) comments
Zhang (Ericsson) suggest to NOTE the paper
Hong (Qualcomm) comments.
Changhong (Intel) shares comments in below and doesn't think this paper is needed.
Hong (Qualcomm) replies to Zhang.
Hong (Qualcomm) replies to Steve.
Deng Qiang (CATT) can't accept signal adjustment factor to gNB, and propose to NOTED this paper.
Steve (Huawei) proposal does not say PDB is delivered to the RAN
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) propose to NOTE.
Steve (Huawei) The proposal to NOTE is based on something NOT in the pCR.
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2105724 CR Approval 23.503 CR0623 (Rel-17, 'F'): Clarification on L3 U2N Relay Offload indication in URSP Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106900 Deng Qiang (CATT) comments and proposes to NOTED.
Changhong (Intel) comments and has concern with the CR.
Hong (Qualcomm) share the concern of Intel and CATT, and propose to NOTE the CR.
Steve (Huawei) comments
Changhong (Intel) replies to Steve comments and propose to NOTE the CR.
Steve (Huawei) comments and provides r01.
Hong (Qualcomm) comments.
Steve (Huawei) provides r02
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106900 CR Approval 23.503 CR0623R1 (Rel-17, 'F'): Clarification on L3 U2N Relay Offload indication in URSP Huawei, HiSilicon Rel-17 Revision of S2-2105724r03. Approved Agreed
8.8 S2-2105728 P-CR Approval 23.304: Update on protocol stack for UE-to-Network Relay. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106901 Hannu (Nokia) clarifies the reference to 23.501 clause 8.3 in r01.
Fei (OPPO) comments on r01.
Steve (Huawei) provides r02, prefers r00 (original), r01 it not correct.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106901 P-CR Approval 23.304: Update on protocol stack for UE-to-Network Relay. Huawei, HiSilicon Rel-17 Revision of S2-2105728r02. Approved Approved
8.8 S2-2105729 P-CR Approval 23.304: Updates on L2 U2N Relay. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106902 Wen (vivo) provides r01.
Deng Qiang (CATT) comments.
Zhang (Ericsson) propose to merge the last change into S2-2106094
Steve (Huawei) comments, provides r02.
Zhang (Ericsson) is OK with r02
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106902 P-CR Approval 23.304: Updates on L2 U2N Relay. Huawei, HiSilicon Rel-17 Revision of S2-2105729r03. Approved Approved
8.8 S2-2105735 CR Approval 23.502 CR2966 (Rel-17, 'F'): Correction of the Naf_ProSe_AuthorizeDiscovery service parameters Huawei, HiSilicon, CATT Rel-17 r02 agreed. Revised to S2-2106903. CC#5: Issue discovered with r02. Postponed Judy (Ericsson) propose to document the AF service for 5G ProSe in the self-contained TS 23.304 and add a reference in 23.502 to avoid future update on multiple documents for the same change.
Deng Qiang (CATT) replies to Judy (Ericsson).
Guanglei (Huawei) can accept the proposal from Judy if we have an agreement on 6092.
Judy (Ericsson) provides r01 to move the Naf_ProSe service definition to the ProSe spec and include in 23.502 only a reference of 23.304
Guanglei (Huawei) is fine with r01.
Guanglei (Huawei) provides r02 based on r01 to add Ericsson as a co-source.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2106903 CR Approval 23.502 CR2966R1 (Rel-17, 'F'): Correction of the Naf_ProSe_AuthorizeDiscovery service parameters Huawei, HiSilicon, CATT Rel-17 Revision of S2-2105735r02. Approved. WITHDRAWN Withdrawn
8.8 S2-2105876 P-CR Approval 23.304: NRF for DDNMF discovery. OPPO Rel-17 r01 agreed. Revised to S2-2106904 Zhang (Ericsson) provides comments
Fei (OPPO) responds and provides r01.
Zhang (Ericsson) is fine with r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106904 P-CR Approval 23.304: NRF for DDNMF discovery. OPPO Rel-17 Revision of S2-2105876r01. Approved Approved
8.8 S2-2105882 P-CR Approval 23.304: Link identifier update procedure for ProSe communication. ASUSTeK Rel-17 Postponed LaeYoung (LGE) proposes to NOTE this pCR because the proposals do not work.
Lider (ASUSTeK) comments.
LaeYoung (LGE) provides answer to Lider (ASUSTeK) and still thinks that this pCR can be NOTED.
Wen (vivo) comments.
Fei (OPPO) comments
LaeYoung (LGE) provides clarification to Wen (vivo).
Wen (vivo) responds to LaeYoung (LGE) and comments.
Lider (ASUSTeK) replies to Fei (OPPO).
Lider (ASUSTeK) replies to LaeYoung (LGE) and Wen (vivo).
Hong (Qualcomm) comments and suggest to NOTE, as this is a stage 3 description.
Xiaoyan Shi (Interdigital) agrees with Hong, Fei and Laeyoung, and suggest to NOTE this contribution.
Lider (ASUSTeK) replies to Hong (Qualcomm) and Xiaoyan (Interdigital), and has question for clarification.
LaeYoung (LGE) replies to Lider (ASUSTeK).
Fei (OPPO) comments.
Lider (ASUSTeK) considers to postpone this contribution.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2105903 P-CR Approval 23.304: Policy control aspects for L3 Remote UE. LG Electronics, Ericsson Rel-17 r03 agreed. Revised to S2-2106905 Yali (OPPO) asks a question.
LaeYoung (LGE) replies to Yali (OPPO).
Yali (OPPO) replies to LaeYoung.
LaeYoung (LGE) answers to Yali (OPPO).
LaeYoung (LGE) responds to Yali (OPPO).
Yali (OPPO) provides r01.
LaeYoung (LGE) provides r02.
Fei (OPPO) comments on structure on clause 5.5 and 5.5A.
LaeYoung (LGE) responds to Fei (OPPO).
Steve (Huawei) A couple of questions for clarification
LaeYoung (LGE) provides r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106905 P-CR Approval 23.304: Policy control aspects for L3 Remote UE. LG Electronics, Ericsson Rel-17 Revision of S2-2105903r03. Approved Approved
8.8 S2-2105904 P-CR Approval 23.304: Clause 5.6.1: Adding Ethernet Packet Filter Set. LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2105968 P-CR Approval 23.304: Clarification on N3IWF selection for Remote UE. LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106016 P-CR Approval 23.304: TS 23.304: Context alignment. vivo Rel-17 r02 agreed. Revised to S2-2106906 Deng Qiang (CATT) comments.
Wen (vivo) responds and provide r01.
Fei (OPPO) asks questions on r01.
Wen (vivo) responds to Fei (OPPO).
Fei (OPPO) responds to Wen (vivo)
Fei (OPPO) responds to Wen (vivo) and confirms this understanding.
Steve (Huawei) comments and provides r02.
Fei (OPPO) responds to Steve (Huawei).
Wen (vivo) shares the same view with Fei (OPPO) and provides r03.
Fei (OPPO) comments.
Wen (vivo) responds to Steve (Huawei)
==== 8.X, 9.X Revisions Deadline ====
Wen (vivo) thinks the state of this paper should be 'Agree r03'.
Steve (Huawei) lets go with r02.
Tao(VC) ask whether can go with r02
Fei (OPPO) is ok with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106906 P-CR Approval 23.304: TS 23.304: Context alignment. Vivo Rel-17 Revision of S2-2106016r02. Approved Approved
8.8 S2-2106069 P-CR Approval 23.304: Clause 5.8.1 Clarification on Target Info for Group Member Discovery. ZTE Rel-17 Approved Steve (Huawei) questions for clarification
Hao Dong (ZTE) responds to Steve (Huawei).
Steve (Huawei) thanks, a further question...
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) thanks for answering my questions.
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106075 P-CR Approval 23.304: Clause 6.3.1.7 Add ProSe Application Server Triggers Direct Discovery Update Procedure. ZTE Rel-17 Approved Steve (Huawei) questions for clarification
Hao Dong (ZTE) responds to Steve (Huawei).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106092 P-CR Approval 23.304: TS 23.304: 5G DDNMF Services used by AF. CATT Rel-17 r04 agreed. Revised to S2-2106907 Judy (Ericsson) comments and provide r01
Hao Dong (ZTE) comments.
Deng Qiang (CATT) can't accept r01 and responds.
Judy (Ericsson) responds to Deng Qiang (CATT) and Hao Dong (ZTE), and ask to reconsider r01 as r00 does not seem to follow SBA design, explained
Guanglei (Huawei) agrees with Judy (Ericsson).
Judy (Ericsson) thanks Guanglei (Huawei) for support and provide r02: moving Naf_Prose from 23.502 to 23.304 taking also the update from 5735
Deng Qiang (CATT) is fine with r02 and thanks Judy (Ericsson) effort.
Hao Dong (ZTE) comments and provides r03.
Guanglei (Huawei) provides r04 to update the abstract and add Huawei and Ericsson as co-source.
Deng Qiang (CATT) is fine with r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106907 P-CR Approval 23.304: TS 23.304: AF Services used by 5G DDNMF. CATT, Huawei, Ericsson Rel-17 Revision of S2-2106092r04. Approved Approved
8.8 S2-2106095 P-CR Approval 23.304: TS 23.304: Clarification on the TS scope. CATT Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106096 P-CR Approval 23.304: TS 23.304: Terminology alignment across the TS. CATT, ZTE Rel-17 r01 agreed. Revised to S2-2106908, merging S2-2106331 Jianning (Xiaomi) merges 6331 into 6096 and provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106908 P-CR Approval 23.304: TS 23.304: Terminology alignment across the TS. CATT, ZTE Rel-17 Revision of S2-2106096r01, merging S2-2106331. Approved Approved
8.8 S2-2106100 P-CR Approval 23.304: Clause 6.3.2 Add Type of Discovery Message Parameter in ProSe Direct Discovery Messages. ZTE Rel-17 r01 agreed. Revised to S2-2106909 Deng Qiang (CATT) comments
Hao Dong (ZTE) responds to Deng Qiang (CATT) and provides r01.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106909 P-CR Approval 23.304: Clause 6.3.2 Add Type of Discovery Message Parameter in ProSe Direct Discovery Messages. ZTE Rel-17 Revision of S2-2106100r01. Approved Approved
8.8 S2-2106125 P-CR Approval 23.304: Clause 5.1 Modify the Descriptions Regarding the Provisioning of the Parameters. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106204 CR Approval 23.303 CR0329 (Rel-17, 'F'): Call flow corrections Nokia, Nokia Shanghai Bell Rel-17 Noted Deng Qiang (CATT) proposed to NOTED this CR as it is not FASMO.
Hannu (Nokia) agrees the CR is not FASMO. This is why only Rel-17 version is submitted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2106218 P-CR Approval 23.304: Cell ID announcement . Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106910 Judy (Ericsson) comments.
Hao Dong (ZTE) comments.
Wen (vivo) comments.
Fei (OPPO) comments.
Deng Qiang (CATT) clarifies the usage of this procedure.
Steve (Huawei) comments
Fei (OPPO) responds to Steve (Huawei)
Hong (Qualcomm) comments.
Xiaoyan Shi (Interdigital) comments.
Fei (OPPO) comments and proposes a way forward on the cell id delivery.
Deng Qiang (CATT) comments.
Zhang (Ericsson) provides comments and propose the cell ID in the additional message
Fei (OPPO) comments and provides r01.
Hannu (Nokia) supports r01 as the CR aims at solving the missing Cell ID for L3 solution. Nokia is also willing to consider the proposal to include Cell ID in discovery messages in all cases.
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106910 P-CR Approval 23.304: Cell ID announcement . Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106218r01. Approved Approved
8.8 S2-2106220 P-CR Approval 23.304: Clause 5.10: Removal of EN. LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2106315 P-CR Approval 23.304: Correction for the reference number Xiaomi Rel-17 r01 agreed. Revised to S2-2106911 Zhang (Ericsson) provides comments
Jianning (Xiaomi) replies to Zhang (Ericssion) and provide r01
LaeYoung (LGE) comments.
Zhang (Ericsson) is OK with r01
Deng Qiang (CATT) comments.
Jianning (Xiaomi) replies to Qiang (CATT)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106911 P-CR Approval 23.304: Correction for the reference number. Xiaomi Rel-17 Revision of S2-2106315r01. Approved Approved
8.8 S2-2106331 P-CR Approval 23.304: Adding Abbreviations in clause 3.2 Xiaomi Rel-17 Merged into S2-2106908 Jianning (Xiaomi) provide r01
Hao Dong (ZTE) comments.
Jianning (Xiaomi) replies to Hao Dong (ZTE) and provides r02
Steve (Huawei) UCU not needed? merge with S2-2106096?
Fei (OPPO) comments.
Jianning (Xiaomi) agrees to merge into S2-2106096
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2106418 P-CR Approval 23.304: TS 23.304: 6.3.2.3.2 Update procedure for UE-to-Network Relay Discovery with Model A. Interdigital Inc. Rel-17 r01 agreed. Revised to S2-2106912 Deng Qiang (CATT) comments
Hao Dong (ZTE) responds to Deng Qiang (CATT) and provides r01.
Xiaoyan Shi(Interdigital) replies to Deng Qiang and provide r01. Hao Dong (ZTE) responds in wrong thread.
Hao Dong (ZTE) responds to Xiaoyan (Interdigital) and apologizes for sending the previous reply for another thread.
Fei (OPPO) comments.
Xiaoyan Shi (Interdigital) replies to Fei.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2106912 P-CR Approval 23.304: TS 23.304: 6.3.2.3.2 Update procedure for UE-to-Network Relay Discovery with Model A. Interdigital Inc. Rel-17 Revision of S2-2106418r01. Approved Approved
8.8 S2-2106526 P-CR Approval 23.304: TS 23.304: Updating the spec to enable NPN support. Philips International B.V. Rel-17 Postponed Judy (Ericsson) comments that feature interaction between NPN and 5G ProSe has not be discussed and the implication is not clear yet, i.e. this paper lacks justification.
Fei (OPPO) comments.
Hao Dong (ZTE) asks a question.
Jianning (Xiaomi) provides comments
Deng Qiang (CATT) shares the concerns with others and proposes to NOTED.
Josep (DT) objects to the original and any revision .
Xiaoyan Shi (Interdigital) share same concerns.
Walter (Philips) ok with postponing to release 18 and asked it to be included in NPN phase 2
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=203 -
8.9 - - - General - - Docs:=9 -
8.9 S2-2106084 LS OUT Approval [DRAFT] LS to RAN on outstanding issues Huawei, HiSilicon Rel-17 r00 agreed. Revised to remove 'DRAFT' in S2-2106833
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106833 LS OUT Approval LS on latest progress and outstanding issues in SA WG2 SA WG2 Rel-17 Revision of S2-2106084r00. CC#4: Approved Approved
8.9 S2-2106085 LS OUT Approval [DRAFT] LS to SA WG4 and SA WG6 on Service announcement issues Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106913 Robbie (Ericsson) corrects the pCR number to 6085
Thomas (Nokia) provides r01
Robbie (Ericsson) provides r02
Thomas (Nokia) provides r03
Robbie (Ericsson) comments
Robbie (Ericsson) provides r04 to fix the reference clause
Thomas(Nokia) replies
Zhenhua (vivo) comments
Zhenhua (vivo) provides r05
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) provides r06, and suggest to checkin CC#4.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106913 LS OUT Approval LS on latest progress and outstanding issues in SA WG2 SA WG2 Rel-17 Revision of S2-2106085r06. Approved Approved
8.9 S2-2106079 P-CR Approval 23.247: Miscellaneous clarification. Huawei, HiSilicon, Qualcomm Rel-17 r08 agreed. Revised to S2-2106914, merging S2-2105432, S2-2105629, S2-2105887 and S2-2105889 Thomas (Nokia) provides r01
Thomas (Nokia) provides r02, asks to ignore r01
LiMeng (Huawei) provides r03 to further remove some sections to avoid overlapping with other documents.
Thomas (Nokia) comments on r03.
LiMeng (Huawei) provides r04.
Youngkyo(Samsung) provides r05.
LiMeng (Huawei) accepts r05.
Robbie (Ericsson) provides r06, merges 5629 in, and proposes to merge clause 6.6 in 6079 to 5644
LiMeng (Huawei) provides r07, and replies Robbie.
Robbie (Ericsson) provides r08 to merge clause 6.6 out to 5644.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106914 P-CR Approval 23.247: Miscellaneous clarification. Huawei, HiSilicon, Qualcomm, Ericsson Rel-17 Revision of S2-2106079r08, merging S2-2105432, S2-2105629, S2-2105887 and S2-2105889. Approved Approved
8.9 S2-2105900 DISCUSSION Agreement MBS Session handling when its associated PDU session is released. Samsung Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106024 DISCUSSION Discussion Discussion on AF triggered MBS Join. Apple Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2105374 LS In Action LS from SA WG4: Reply LS on work split for MBSF and MBSTF definition SA WG4 (S4-211292) Rel-17 Postponed LiMeng (Huawei) suggests to postpone this LS.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - Subscription and Authorization - - Docs:=8 -
8.9 S2-2106082 P-CR Approval 23.247: Clarification on MBS UE authorization. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106915 Thomas (Nokia) provides r01
LiMeng (Huawei) provides r02 with removing 6.4 in r01.
Judy (Ericsson) provide r03
LiMeng (Huawei) is fine with r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106915 P-CR Approval 23.247: Clarification on MBS UE authorization. Huawei, HiSilicon Rel-17 Revision of S2-2106082r03. Approved Approved
8.9 S2-2105908 P-CR Approval 23.247: Update to Clause 6.4: UE context in SMF data to MBS Subscription data. LG Electronics Rel-17 Merged into S2-2106916 LiMeng (Huawei) suggests to merge this document into S2-2105917.
LaeYoung (LGE) agrees to merge this document into S2-2105917.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105917 P-CR Approval 23.247: MBS information storage in UDM and UDR. CATT, CBN Rel-17 r06 agreed. Revised to S2-2106916, merging S2-2105908, S2-2106355 and S2-2106473 Thomas (Nokia) r01
Xiaoyan (CATT) provides r02.
Judy (Ericsson) comment provides r03, proposing to use existing parameter provisioning procedure in 4.15.6.2 of TS 23.502.
Xiaoyan (CATT) replies to Judy (Ericsson).
Xiaoyan (CATT) provides r04.
Thomas (Nokia) provides r05.
Judy (Ericsson) comments
Thomas (Nokia) provides r06.
Xiaoyan (CATT) replies to Judy (Ericsson) and Thomas (Nokia).
Xiaoyan (CATT) provides r07.
Thomas (Nokia) replies to Xiaoyan
zhendong(ZTE) provides r08,
Xiaoyan (CATT) provides r09.
Thomas (Nokia) provides r10.
==== 8.X, 9.X Revisions Deadline ====
Xiaoyan (CATT) supports also r04, r07, r09 and can live with r10.
Xiaoyan (CATT) can live with r06/r03, prefers r06.
Judy (Ericsson) accepts r03, r06, objects to other revisions which requires completely new UDM-UDR interaction for subscription data management, explained
LiMeng (Huawei) can accept r06.
Thomas (Nokia) is fine with r06.
zhendong(ZTE) is fine with r06,
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106916 P-CR Approval 23.247: MBS information storage in UDM and UDR. CATT, CBN, Nokia, Nokia Shanghai-Bell, ZTE, Huawei Rel-17 Revision of S2-2105917r06, merging S2-2105908, S2-2106355 and S2-2106473. Approved Approved
8.9 S2-2106355 P-CR Approval 23.247: Clarification on the SMF selection. ZTE Rel-17 Merged into S2-2106916 LiMeng (Huawei) suggests to merge this document into S2-2105917.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106473 P-CR Approval 23.247: 5MBS Information in UDM. Nokia, Nokia Shanghai-Bell Rel-17 Revision of (Postponed) S2-2104300 from S2-145E. Merged into S2-2106916 LiMeng (Huawei) suggests to merge this document into S2-2105917.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106441 P-CR Approval 23.247: 5MBS Information in UDR. Nokia, Nokia Shanghai-Bell Rel-17 Revision of (Postponed) S2-2104313 from S2-145E. Merged into S2-2106927 LiMeng (Huawei) suggests to merge this document into S2-2106431.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - User Plane management - - Docs:=8 -
8.9 S2-2105648 P-CR Approval 23.247: Update [6.7] MBS UP Management: packet detection and forwarding . Ericsson Rel-17 Merged into S2-2106917 Thomas (Nokia) suggest to focus the discussion in the S2-2106469 thread
Thomas (Nokia) suggest to consider this paper merged into S2-2106469
Judy (Ericsson) agrees to merge 5648 to 6469
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105649 CR Approval 23.501 CR3055 (Rel-17, 'C'): MBS Packet detection and forwarding Ericsson Rel-17 Merge into S2-2106470 (Postponed). Postponed Thomas (Nokia) suggest to focus the discussion in the S2-2106469 thread
LiMeng (Huawei) suggests to merge this document into S2-2106470.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106361 P-CR Approval 23.247: Discussion and proposal on the UPF packet detection and forwarding for MBS data traffic. ZTE Rel-17 Merged into S2-2106866 Thomas (Nokia) suggest to focus the discussion in the S2-2106469 thread
LiMeng (Huawei) suggests to merge this document into S2-2105648.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106362 CR Approval 23.501 CR3202 (Rel-17, 'C'): Clarification on the packet detection and forwarding for MBS traffic ZTE Rel-17 Postponed Thomas (Nokia) suggest to focus the discussion in the S2-2106469 thread
Thomas (Nokia) suggest to postpone this contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106469 P-CR Approval 23.247: UPF configuration to replicate packets. Nokia, Nokia Shanghai-Bell Rel-17 r03 agreed. Revised to S2-2106917, merging S2-2105648 Thomas (Nokia) provides a compromise proposal in r01
Judy (Ericsson) prefers to use either 5648 or 6361 as basis for merging, but can discuss in this thread to focus on the needed technical change and avoid multiple thread discussions. See comments below.
zhendong(ZTE), provides the comments
Judy (Ericsson) comments.
Fenqin (Huawei) comments.
Thomas(Nokia) replies to Judy
Thomas(Nokia) replies to Zhendong and Fenqin
Judy (Ericsson) responds to Thomas (Nokia)
Thomas (Nokia) provides a compromise proposal in r02
Judy (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106917 P-CR Approval 23.247: UPF configuration to replicate packets. Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2106469r03, merging S2-2105648. Approved Approved
8.9 S2-2106700 LS OUT Approval [DRAFT] LS on User plane management in UPF for MBS service Huawei Rel-17 Created at CC#3. CC#4: This was left for discussion at CC#5. CC#5: r02 agreed. Revised to S2-2106678. LiMeng (Huawei) provide r00
LiMeng (Huawei) provide r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106678 LS OUT Approval LS on User plane management in UPF for MBS service SA WG2 Rel-17 Revision of S2-2106700r02. Approved Approved
8.9 - - - Other documents on concepts, principles and service provisioning - - Docs:=31 -
8.9 S2-2105645 P-CR Approval 23.247: Update [4.1] on service levels for the multicast communication service . Ericsson Rel-17 Merged into S2-2106918 Thomas (Nokia) provides r01
LiMeng (Huawei) suggests to merge this document into S2-2105885.
Judy (Ericsson) is fine with LiMeng (Huawei)'s proposal to merge this paper to 5885.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105885 P-CR Approval 23.247: Update [4.1] Principles of multicast and broadcast communication. Samsung Rel-17 r04 agreed. Revised to S2-2106918, merging S2-2105645 Thomas (Nokia) provides r01
Youngkyo(Samsung) replies to r01
Robbie(Ericsson) agrees with Thomas (Nokia)
Thomas(Nokia) replies to Youngkyo
LiMeng (Huawei) comments.
Youngkyo(Samsung) accepts view from Robbie(Ericsson) and Thomas (Nokia)
Youngkyo(Samsung) provides the revision r02.
Judy (Ericsson) provides r03
Thomas (Nokia) provides r04
==== 8.X, 9.X Revisions Deadline ====
Youngkyo(Samsung) is okay with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106918 P-CR Approval 23.247: Update [4.1] Principles of multicast and broadcast communication. Samsung, Ericsson, Huawei, HiSilicon, Qualcomm Rel-17 Revision of S2-2105885r04, merging S2-2105645. Approved Approved
8.9 S2-2105646 P-CR Approval 23.247: Correct [4.2.2] Broadcast data provisioning . Ericsson Rel-17 r02 agreed. Revised to S2-2106919 Thomas (Nokia) proposes to Note this contribution
Judy (Ericsson) comments that Thomas (Nokia)'s proposal to note the paper lacks technical basis.
Thomas (Nokia) replies to Judy that the CR lacks a technical basis and brings misalignment
Thomas (Nokia) provides r02
LiMeng (Huawei) provides r01.
Judy (Ericsson) provide r03
Judy (Ericsson) provide r04
Judy (Ericsson) commented that r04 is provided by Thomas (not by Judy), and there is no agreement in CC to use 'Configuration' for MBS Session management. r04 is not acceptable.
Youngkyo(Samsung) provides comments.
LiMeng (Huawei) agrees Youngkyo and provides comments.
Judy (Ericsson) insists on using 'MBS Session Creation' instead of 'MBS Session Configuration' for MBS Session management procedure.
Thomas (Nokia) confirms that he provided r04, replies to Judy that in a preparatory Telco everyone except her was fine with 'configuration', and object against r00, r01 and r03
==== 8.X, 9.X Revisions Deadline ====
Youngkyo(Samsung) supports r02 and objects the other revision.
Tao(VC) R02 seems the only one without objection. Can we go with r02?
Judy (Ericsson) comment that per offline discussion, we will go for r04 + removing 'configure information about and', there CC#4 discussion is needed
LiMeng (Huawei) accepts the proposal of Judy.
Thomas (Nokia) accepts bringing this to CC.
Youngkyo(Samsung) withdraws objection and is okay to bring this to CC.
Judy (Ericsson) thanks Youngkyo(Samsung) and propose to go for r04 + remove 'configure information about and' + add 'Editor's Note: Term alignment in the TS for MBS Session Management is needed in place of configuration' per offline discussion
Xiaoyan (CATT) accepts only r02, and objects to other revisions (including r00).
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106919 P-CR Approval 23.247: Correct [4.2.2] Broadcast data provisioning . Ericsson Rel-17 Revision of S2-2105646r02. Approved Approved
8.9 S2-2105886 P-CR Approval 23.247: Update [4.2] MB service provisioning. Samsung Rel-17 r01 agreed. Revised to S2-2106920, merging S2-2106080 LiMeng (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106920 P-CR Approval 23.247: Update [4.2] MB service provisioning. Samsung, Huawei, HiSilicon Rel-17 Revision of S2-2105886r01, merging S2-2106080. Approved Approved
8.9 S2-2106080 P-CR Approval 23.247: Clarification on MB service provisioning. Huawei, HiSilicon Rel-17 Merged into S2-2106920 LiMeng (Huawei) proposes to merge this document into S2-2105886.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105636 P-CR Approval 23.247: Update [4.3] Multicast session state model. Ericsson Rel-17 Merged into S2-2106921 Thomas (Nokia) proposes to note this contribution
Robbie(Ericsson) disagrees with Thomas (Nokia), and asks to work on consensus.
Thomas (Nokia) replies to Robbie
Robbie (Ericsson) asks Thomas (Nokia)
LiMeng (Huawei) tries to clarify.
Robbie (Ericsson) thanks the clarification from LiMeng (Huawei) and comments.
LiMeng (Huawei) thanks Robbie the merging effort, and suggests to update S2-2106081 for a focused discussion.
Robbie (Ericsson) replies to Thomas (Nokia) replies
Thomas(Nokia) agrees with Robbies proposal to consider the paper as merged into 6081
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106081 P-CR Approval 23.247: Multicast session state model. Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2106921, merging S2-2105636 Thomas (Nokia) provides r01
Robbie(Ericsson) provides r02, and objects to r00 and r01
Thomas(Nokia) provides r03
Robbie (Ericsson) provides r03, merge SMF state machine figure from 5636
Thomas(Nokia) is fine with r04 and replies to Robbie
Zhenhua (vivo) provides r04
LiMeng (Huawei) accepts r04.
==== 8.X, 9.X Revisions Deadline ====
Tao (VC) let's check r05 which is provided before revision deadline but not reflects in the NOTES log
LiMeng (Huawei) confirms that he can accepts r05.
Robbie (Ericsson) clarifies that Robbie (Ericsson) provides r04, Zhenhua (Vivo) provides r05, and LiMeng (Huawei) accepts r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106921 P-CR Approval 23.247: Multicast session state model. Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2106081r05, merging S2-2105636. Approved Approved
8.9 S2-2105887 P-CR Approval 23.247: Update [5.1] general architecture and [5.3] Reference points. Samsung Rel-17 Merged into S2-2106914 Thomas (Nokia) provides a comment
Youngkyo(Samsung) replies to Thomas (Nokia)
Thomas(Nokia) replies to Youngkyo
LiMeng (Huawei) suggests to merge this document into S2-2106079.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105432 P-CR Approval 23.247: Update [5.3.2] Functional Entities. Ericsson Rel-17 Merged into S2-2106914 LiMeng (Huawei) suggests to merge this document into S2-2106079.
Robbie (Ericsson) agrees to merge this document into S2-2106079.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105647 P-CR Approval 23.247: Update [5.3.2] NRF. Ericsson Rel-17 r03 agreed. Revised to S2-2106922 Thomas (Nokia) provides r01
Judy (Ericsson) provides r02
Thomas (Nokia) objects to r02
Comments that documentation of NF profile extensions is required.
Thomas (Nokia) provides r03
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) is fine with r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106922 P-CR Approval 23.247: Update [5.3.2] NRF. Ericsson, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2105647r03. Approved Approved
8.9 S2-2105628 P-CR Approval 23.247: Update [5.3.2] & [7.1.1] & [7.3] & [7.X] Clarification of MBSF and NEF. Ericsson Rel-17 r03 agreed. Revised to S2-2106923 Thomas (Nokia) proposes to merge changes in 5.3.2.10 into S2-2106079 and note the document
Robbie(Ericsson) disagrees with Thomas(Nokia), provides r01 for the discussion in MBS CC#3
Thomas(Nokia) provides r02 for the discussion in MBS CC#3
Robbie(Ericsson) provides r03 based on merging proposal
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106923 P-CR Approval 23.247: Update [5.3.2] & [7.1.1] & [7.3] & [7.X] Clarification of MBSF and NEF. Ericsson Rel-17 Revision of S2-2105628r03. Approved Approved
8.9 S2-2105629 P-CR Approval 23.247: Update [6.5.1] MBS Session ID. Ericsson Rel-17 Merged into S2-2106914 LiMeng (Huawei) asks to merge this document into S2-2106079, since 6079 contains the same change and such aspect is rather a miscellaneous clarification.
Robbie (Ericsson) agrees to merge this document into S2-2106079.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105889 P-CR Approval 23.247: Update [6.5.2] Temporary Mobile Group Identity. Samsung Rel-17 Merged into S2-2106914 LiMeng (Huawei) suggests to merge this document into S2-2106079.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105630 P-CR Approval 23.247: Update [6.11] NID in Service Announcement. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2106365 P-CR Approval 23.247: Update the clause 6.11 service announcement. ZTE Rel-17 r02 agreed. Revised to S2-2106924 zhendong(ZTE) provides the r01
Zhenhua (vivo) provides r02
Thomas (Nokia) provides r03
LiMeng (Huawei) considers geographical information is useful for some cases and consider r02 would be OK.
Thomas (Nokia) can live with r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106924 P-CR Approval 23.247: Update the clause 6.11 service announcement. ZTE Rel-17 Revision of S2-2106365r02. Approved Approved
8.9 S2-2106197 P-CR Approval 23.247: MBS Session and Service Context. Tencent Rel-17 Merged into S2-2106925 LiMeng (Huawei) suggests to merge this document into S2-2106351.
Chunshan (Tencent) confirms to merge this document into S2-2106351.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106351 P-CR Approval 23.247: Update the clause 6.9.1 MBS Session/Service Context. ZTE Rel-17 r03 agreed. Revised to S2-2106925, merging S2-2105909 and S2-2106197 Robbie (Ericsson) asks a question.
zhendong(ZTE) prvides response,
Robbie (Ericsson) provide r01, also merging 5909
zhendong(ZTE) provides r02,
LiMeng (Huawei) is fine with r02 and adds the link of r02.
zhendong(ZTE) provides r03,
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106925 P-CR Approval 23.247: Update the clause 6.9.1 MBS Session/Service Context. ZTE, Ericsson, Tencent, LG Electronics Rel-17 Revision of S2-2106351r03, merging S2-2105909 and S2-2106197. Approved Approved
8.9 S2-2105818 CR Approval 23.501 CR3091 (Rel-17, 'D'): Update clause number for MB-UPF, MBSF and MBSTF in clause 6.2 Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.9 S2-2105644 P-CR Approval 23.247: Update to [6.6] QoS handling. Ericsson Rel-17 Revision of (Postponed) S2-2103950 from S2-145E. r12 agreed. Revised to S2-2106926 Judy (Ericsson) provides r01, also proposing to merge 6.6 from 6079 in this paper
LiMeng (Huawei) provides r02, and is fine to merge 6.6 from 6079.
Judy (Ericsson) provide r03
Zhenhua (vivo) provide r04
Youngkyo(Samsung) asks a question.
Zhenhua (vivo) replise to Youngkyo(Samsung).
Judy (Ericsson) provide r05 and responds to Youngkyo(Samsung)
Thomas (Nokia) provide r06 and objects to all previous revisions
Judy (Ericsson) provides r07, cannot accept r06 and responds to Thomas (Nokia)
Thomas(Nokia) objects against r07, replies to Judy
Zhenhua (vivo) comments to Thomas(Nokia)
Thomas(Nokia) replies to Zhenhua (vivo)
Judy (Ericsson) ask a question to Thomas(Nokia)
Zhenhua (vivo) replies to Thomas(Nokia)
Judy (Ericsson) provides r08
Zhenhua(vivo) comments
Fenqin (Huawei) provides r09
Thomas (Nokia) provides r10
Thomas (Nokia) provides r11
zhendong(ZTE) agree with vivo,
zhendong(ZTE) provides r12,
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106926 P-CR Approval 23.247: Update to [6.6] QoS handling. Ericsson Rel-17 Revision of S2-2105644r12. Approved Approved
8.9 S2-2106431 P-CR Approval 23.247: MBS Policy . Nokia, Nokia Shanghai-Bell Rel-17 r03 agreed. Revised to S2-2106927, merging S2-2106441 Thomas (Nokia) provides r01 to merge contents of S2-2106441
Judy (Ericsson) comments this paper propopose to apply PDU Session policy/QoS parameter to MBS Session without considering the applicability. R02 is provided .
Thomas(Nokia) replies to Judy and provides r03
Judy (Ericsson) responds to Thomas (Nokia)
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) is fine with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106927 P-CR Approval 23.247: MBS Policy . Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2106431r03, merging S2-2106441. Approved Approved
8.9 S2-2105643 P-CR Approval 23.247: Update [4.1] Potential issue of Individual MBS traffic delivery and its Mitigation . Ericsson Rel-17 Revision of (Noted) S2-2103947 from S2-145E. Noted Thomas (Nokia) proposes to note this P-CR
Judy (Ericsson) asks Thomas (Nokia) why a NOTE, that makes the possible consequence of individual delivery visible and gives guideline to operator for their deployment choice, is not acceptable.
LiMeng (Huawei) questions the necessity of this document.
Judy (Ericsson) ask Li Meng (Huawei) and Thomas (Nokia) what is your concern with a NOTE that could give operator a quick input in making their deployment choice. Comments.
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) objects to this document. Reasons provided.
zhendong(ZTE) proposes to NOTE this CR,
Judy (Ericsson) responds to zhendong(ZTE) and LiMeng (Huawei) that you can choose to ignore the fact that Individual MBS traffic delivery mechanism does not save radio resource thus not not scalable.
==== 8.X, 9.X Final Deadline ====
Noted
8.9 - - - Session Join/Leave/Update - - Docs:=27 -
8.9 S2-2106332 P-CR Approval 23.247: AF requested multicast session management procedure. vivo, juniper Rel-17 Revision of (Postponed) S2-2104242 from S2-145E. Noted Jeffrey Zhang (Juniper) provides r01 to address questions/comments brough up in 5MBS CC#5.
Thomas replies to Jeffrey and raises concerns against the CR
Jeffrey responds to Thomas' concerns
Thomas(Nokia) suggest to note the contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2105890 P-CR Approval 23.247: Update [7.2.1] MBS Join and Session establishment procedure. Samsung Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105891 P-CR Approval 23.247: Update [7.2.2] MBS Session leave and Session release procedure. Samsung Rel-17 r02 agreed. Revised to S2-2106928, merging S2-2106088 LiMeng (Huawei) provide r01.
LaeYoung (LGE) provide r02.
Youngkyo(Samsung) is okay with r01.
Youngkyo(Samsung) is okay with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106928 P-CR Approval 23.247: Update [7.2.2] MBS Session leave and Session release procedure. Samsung Rel-17 Revision of S2-2105891r02, merging S2-2106088. Approved Approved
8.9 S2-2105651 P-CR Approval 23.247: Update [7.2.2] UE leave MBS Session and MBS Session release. Ericsson Rel-17 r03 agreed. Revised to S2-2106929, merging S2-2105633 Robbie (Ericsson) provides r01, merges 5633, 5891, 6078, 6466 in for clause 7.2.2.3, based on merging proposal
LiMeng (Huawei) thanks Robbie for the merging effort, and ask for clarification
Thomas (Nokia) provides r02
Robbie (Ericsson) responds and provides r03
Thomas (Nokia) responds to Robbie
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106929 P-CR Approval 23.247: Update [7.2.2] UE leave MBS Session and MBS Session release. Ericsson Rel-17 Revision of S2-2105651r03, merging S2-2105633. Approved Approved
8.9 S2-2105915 P-CR Approval 23.247: MBS Session join and Session establishment. CATT, CBN Rel-17 r04 agreed. Revised to S2-2106930 Xiaoyan (CATT) provides r01.
LiMeng (Huawei) provides r02.
Xiaoyan (CATT) provides r03.
zhendong(ZTE) provides the r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106930 P-CR Approval 23.247: MBS Session join and Session establishment. CATT, CBN, Huawei, ZTE Rel-17 Revision of S2-2105915r04. Approved Approved
8.9 S2-2106507 P-CR Approval 23.247: Updates to Multicast session join and session establishment procedure. Nokia, Nokia Shanghai-Bell Rel-17 CC#4: r08 + changes agreed. Revised, merging S2-2105890, S2-2106083, S2-2106359, S2-2105631, S2-2105652, S2-2106435 and S2-2105640, to S2-2106665. Thomas (Nokia) provides r01 to merge all proposals for Clause 7.2.1.3 as proposed by the rapporteur
Zhenhua (vivo) provides r02
Judy (Ericsson) provides r03, including merging 5631 & 5652, replace service operations etc
LiMeng (Huawei) provides r04 base on r03, including merging 6083, and further modify the text to align the service operations.
zhendong(ZTE) provides the r05
Thomas(Nokia) provides the r06
Thomas(Nokia) provides the r07
Miguel (Qualcomm) provides r08
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) clarifies r07 is provided by LiMeng (Huawei).
Judy (Ericsson) accepts r04 & r05, does not accept r06 &r07&08 as is and request some changes, explained below.
Xiaoyan (CATT) prefers r05.
Thomas (Nokia) objects against r05, but supports the proposal of Judy to go with r08 and the improvements she suggested
Suggest bringing this to the CC
LiMeng (Huawei) is fine to bring it to CC#4, but suggests we offline work out an agreeable version.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106665 P-CR Approval 23.247: Updates to Multicast session join and session establishment procedure. Nokia, Nokia Shanghai-Bell, ZTE Rel-17 Revision of S2-2106507r08 + changes, merging S2-2105890, S2-2106083, S2-2106359, S2-2105631, S2-2105652, S2-2106435 and S2-2105640. Approved Approved
8.9 S2-2106083 P-CR Approval 23.247: Clarification of Session Join procedure. Huawei, HiSilicon, Qualcomm Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106339 P-CR Approval 23.247: Modification on UE leave. vivo Rel-17 r12 agreed. Revised to S2-2106931, merging S2-2105758 Zhenhua (vivo) provides r01 to merge content of S2-2105758.
Youngkyo(Samsung) provides r02
Robbie (Ericsson) provides r03 to merge content of S2-2105631.
LiMeng (Huawei) provides r04 to merge content of S2-2106088 on top of r03.
Zhenhua (vivo) provides r05 on top of r04 to merge 6466.
Youngkyo(Samsung) provides reply to Robbie (Ericsson) and 06.
Robbie(Ericsson) provides r07.
LiMeng (Huawei) accepts r07.
Zhenhua (vivo) ask Youngkyo(Samsung) for clarification
Zhenhua (vivo) replies to Robbie(Ericsson).
Zhenhua (vivo) provides r08.
Robbie (Ericsson) is fine with r08.
LaeYoung (LGE) asks a Q on r08.
Robbie (Ericsson) clarifies to LaeYoung (LGE)
Youngkyo(Samsung) adds some comments upon Robbie (Ericsson)
Thomas (Nokia) suggest removing the EN in r08
LaeYoung (LGE) also suggests removing the EN in r08.
Youngkyo(Samsung) replies to Thomas (Nokia) and provide r09.
Youngkyo(Samsung) provide r10.
LaeYoung (LGE) provides r11.
Youngkyo(Samsung) replies to LaeYoung (LGE) and provides r12.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) is fine with r12.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106931 P-CR Approval 23.247: Modification on UE leave. Vivo, Samsung, Ericsson, Tencent Rel-17 Revision of S2-2106339r12, merging S2-2105758. Approved Approved
8.9 S2-2106088 P-CR Approval 23.247: Clarification on Session leave procedure. Huawei, HiSilicon Rel-17 Merged into S2-2106928 LiMeng (Huawei) suggests to merge this document into S2-2105891.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106359 P-CR Approval 23.247: Modification on the Multicast session join and session establishment procedure. ZTE Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105758 P-CR Approval 23.247: Update the MBS Session Leave procedure. Tencent Rel-17 Merged into S2-2106931 LiMeng (Huawei) suggests to merge this document into S2-2106339.
Chunshan (Tencent) confirms this document to be merged into S2-2106339.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106433 DISCUSSION Agreement How to handle associated QoS flows for individual fallback in policy control Nokia, Nokia Shanghai-Bell Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106090 P-CR Approval 23.247: Updates about MB-UPF Configuration. Huawei, HiSilicon Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106078 P-CR Approval 23.247: Clarification on SMF removing and Session release procedure. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2106932 LiMeng (Huawei) suggests to only touch the abbreviation changes in this document, and 7.2.2.3 will be addressed in other document. r01 is provided.
Judy (Ericsson) provide r02 and would like to update the pCR subject if possible to reflect the actual change.
LiMeng (Huawei) agrees r02 and provides r03 to update the pCR title.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106932 P-CR Approval 23.247: Update abbreviations . Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2106078r03. Approved Approved
8.9 S2-2105631 P-CR Approval 23.247: Update [7.2.1.3] & [7.2.2.2] interactions between SMF and UPF for individual delivery. Ericsson Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
Robbie (Ericsson) confirms it is merged into S2-2106507.
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105652 P-CR Approval 23.247: Implication of associating UEs with an MBS Session in NG-RAN using PDU Session resource procedure. Ericsson Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
Robbie (Ericsson) confirms it is merged into S2-2106507.
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106435 P-CR Approval 23.247: Corrections to Clause 7.2.1.3 to address PCF interactions. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106337 P-CR Approval 23.247: Modification on multicast session update procedure. vivo Rel-17 Merged into S2-2106933 LiMeng (Huawei) suggests to merge this document into S2-2106366.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106366 P-CR Approval 23.247: Update the clause 7.2.6 Multicast session update procedure. ZTE Rel-17 r07 agreed. Revised to S2-2106933, merging S2-2105952 and S2-2106337 zhendong(ZTE) provides r01,
Thomas(Nokia) provides r02,
Zhenhua (vivo) provides r03,
LiMeng (Huawei) provides r04
zhendong(ZTE) provides r05
LiMeng (Huawei) provides r07 to adopt the change proposal of S2-2106450
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106933 P-CR Approval 23.247: Update the clause 7.2.6 Multicast session update procedure. ZTE Rel-17 Revision of S2-2106366r07, merging S2-2105952 and S2-2106337. Approved Approved
8.9 S2-2105952 P-CR Approval 23.247: Update [7.2] MBS Scalable QoS modification. Panasonic Corporation, DENSO CORPORATION Rel-17 Merged into S2-2106933 LaeYoung (LGE) proposes to NOTE this pCR because she has doubt how the proposal can address scalability.
Zhenhua (vivo) proposes to NOTE this pCR too.
Thomas (Nokia) supports to NOTE this pCR too.
LiuWei (Panasonic) provides response about the doubt.
LiMeng (Huawei) suggests to merge this document into S2-2106366.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - Shared tunnel management - - Docs:=12 -
8.9 S2-2105632 P-CR Approval 23.247: Update [7.2.1.4] & [7.2.2.4] & [7.2.5.2] & [7.2.5.3] & [7.2.6] Store RAN ID List. Ericsson Rel-17 r02 agreed. Revised to S2-2106934 LiMeng (Huawei) provides r02 and asks to ignore r01.
==== 8.X, 9.X Revisions Deadline ====
Robbie (Ericsson) accepts r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106934 P-CR Approval 23.247: Update [7.2.1.4] & [7.2.2.4] & [7.2.5.2] & [7.2.5.3] & [7.2.6] Store RAN ID List. Ericsson Rel-17 Revision of S2-2105632r02. Approved Approved
8.9 S2-2106338 P-CR Approval 23.247: Modification on release of shared delivery. vivo Rel-17 Merged into S2-2106936 LiMeng (Huawei) suggests to merge this document into S2-2106367.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105919 P-CR Approval 23.247: Establishment of shared delivery toward RAN node. CATT Rel-17 r08 agreed. Revised to S2-2106935, merging S2-2106358 Xiaoyan (CATT) provides r01.
Zhenhua (vivo) provides r02 to merge content of 6333.
LiMeng (Huawei) provides r03 to align the service operation in 6427.
zhendong(ZTE) provides the r04,
Xiaoyan (CATT) replies to Zhendong (ZTE).
Xiaoyan (CATT) provides r05.
Judy (Ericsson) ask a question
Xiaoyan (CATT) replies to Judy (Ericsson).
Xiaoyan (CATT) provides r07.
Thomas (Nokia) provides r08.
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) accepts r08.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106935 P-CR Approval 23.247: Establishment of shared delivery toward RAN node. CATT, ZTE, Huawei Rel-17 Revision of S2-2105919r08, merging S2-2106358. Approved Approved
8.9 S2-2105920 P-CR Approval 23.247: Release of shared delivery toward RAN node. CATT Rel-17 Merged into S2-2106936 LiMeng (Huawei) suggests to merge this document into S2-2106367.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106333 P-CR Approval 23.247: Make shared tunnel establishment common. vivo Rel-17 Merged into S2-2106936 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106367 P-CR Approval 23.247: Update the clause 7.2.2.4 on Release of shared delivery toward RAN node. ZTE Rel-17 r03 agreed. Revised to S2-2106936, merging S2-2105920, S2-2106333 and S2-2106338 zhendong(ZTE) provides the r01,
zhendong(ZTE) clarify the service operation.
Zhenhua (vivo) provides r02 to merge content of 6338
LiMeng (Huawei) provides r03 to merge content of 6088.
Xiaoyan (CATT) provides r04.
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) would like to the propose a change to r04 as suggested in r03, i.e., replace 'terminate sending multicast data' in step 2 with 'release the N3mb tunnel used'.
Xiaoyan (CATT) provides r05. Changes compared to r04: replace 'terminate sending multicast data' in step 2 with 'release the N3mb tunnel used'.
zhendong(ZTE) is fine with r04. and proposes it for CC#4 for approval,
Thomas(Nokia) objects against r04
LiMeng (Huawei) clarifies.
Thomas (Nokia) replies to Limeng.
zhendong(ZTE) provides the response,
Xiaoyan (CATT) request clarification from Thomas.
Thomas (Nokia) replies to Xiaoyan
Thomas replies to Zhendong
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106936 P-CR Approval 23.247: Update the clause 7.2.2.4 on Release of shared delivery toward RAN node. ZTE, CATT Rel-17 Revision of S2-2106367r03, merging S2-2105920, S2-2106333 and S2-2106338. Approved Approved
8.9 S2-2106358 P-CR Approval 23.247: Clarification on Establishment of shared delivery toward RAN node. ZTE Rel-17 Merged into S2-2106935 LiMeng (Huawei) suggests to merge this document to S2-2105919, as they are dealing with the same topic/section.
LiMeng (Huawei) suggests to merge this document into S2-2105919.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106466 P-CR Approval 23.247: Multicast message transfer between MB-SMF and NG-RAN. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105905 P-CR Approval 23.247: Update to Clause 7.2.2.4: Release of shared delivery toward RAN node. LG Electronics, LG Uplus, KT Corp. Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 - - - Session Activation/Deactivation - - Docs:=9 -
8.9 S2-2105637 P-CR Approval 23.247: Update [7.2.5][7.2.6] Parallel Activation/Deactivation/Update. Ericsson Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
Robbie (Ericsson) agrees to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105650 P-CR Approval 23.247: Update [7.2.5.1] MBS Session Activation . Ericsson Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105633 P-CR Approval 23.247: Update [7.2.2.3] Deactivation before SMF removing joined UEs. Ericsson Rel-17 Merged into S2-2106929 LiMeng (Huawei) suggests to merge this document into S2-2105651.
Robbie (Ericsson) agrees to merge this document into S2-2105651.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105893 P-CR Approval 23.247: Update [7.2.5] MBS session activation and deactivation. Samsung Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105916 P-CR Approval 23.247: Clarification on MBS Session activation and deactivation. CATT, CBN Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106121 P-CR Approval 23.247: Further clarification for MBS session activation and deactivation. Huawei, HiSilicon Rel-17 r11 agreed. Revised to S2-2106937, merging S2-2105637, S2-2105650, S2-2105893, S2-2105916, S2-2106334, S2-2106360 and S2-2106466 Fenqin (Huawei) provides r01
Zhenhua (vivo) provides r02 to merge content from 6334
Thomas (Nokia) provides r03
Xiaoyan (CATT) provides r04.
Fenqin (Huawei) provides r05
Judy (Ericsson) provides r06
Fenqin (Huawei) provides r07
zhendong(ZTE) provides r08,
Fenqin (Huawei) provides r09
Judy (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) provides r11
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106937 P-CR Approval 23.247: Further clarification for MBS session activation and deactivation. Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, CATT, CBN, ZTE, Ericsson Rel-17 Revision of S2-2106121r11, merging S2-2105637, S2-2105650, S2-2105893, S2-2105916, S2-2106334, S2-2106360 and S2-2106466. Approved Approved
8.9 S2-2106360 P-CR Approval 23.247: Resolving the ENs in the MBS session activation and deactivation procedure. ZTE Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106334 P-CR Approval 23.247: Modification on activation and deactivation. vivo Rel-17 Merged into S2-2106937 LiMeng (Huawei) suggests to merge this document into S2-2106121.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - MBS Session configuration and PCC - - Docs:=12 -
8.9 S2-2105653 P-CR Approval 23.247: Policy Control for MBS Session . Ericsson Rel-17 Postponed Thomas (Nokia) suggest noting this PCR
Judy (Ericsson) encourages Thomas (Nokia) to read the justification of 5653, and reconsider his position. r01 is provided.
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) thinks we can focus on S2-2106453 for clause 7.1.1. Suggests to postpone this document.
zhendong(ZTE) agree with limeng, to focus on 6453 and postpone this one,
Judy (Ericsson) responds to zhendong(ZTE) and LiMeng (Huawei): it seems that issues/complexities raised in 5653 haven't got sufficient awareness. If you need more time, I assume postponing is the only choice. I request to revisit the MBS PCC solution next meeting.
LiMeng (Huawei) agrees to have further offline discussion before the next meeting.
Thomas(Nokia) also support to focus on 6453 and postpone this one,
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106076 P-CR Approval 23.247: Combine MBS session parameter provisioning. Huawei, HiSilicon Rel-17 Merged into S2-2106938 LiMeng (Huawei) proposes to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106443 P-CR Approval 23.247: Initial MBS session configuration with PCC for broadcast. Nokia, Nokia Shanghai-Bell Rel-17 CC#4: Merged into S2-2106938.
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106353 P-CR Approval 23.247: Update the clause 7.1.1 Configuration for MBS Session. ZTE Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106352 P-CR Approval 23.247: Resolving the ENs in the clause 7.1.1.2 Initial MBS session configuration with PCC. ZTE Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106198 P-CR Approval 23.247: Update the Initial MBS session configuration procedure with PCC. Tencent Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106453 P-CR Approval 23.247: Updates to configuration procedures . Nokia, Nokia Shanghai-Bell Rel-17 r07 agreed. CC#4: r03 + changes agreed. Revised to S2-2106938, merging S2-2105639, S2-2105918, S2-2105956, S2-2106076, S2-2106090, S2-2106198, S2-2106352, S2-2106353 and S2-2106443 Thomas (Nokia) provides r01 to perform merging
Xiaoyan (CATT) provides r02.
Judy (Ericsson) provide r03 and does not accept revisions that uses 'Configuration' to name the MBS session management procedure and includes proposal to let UDM handle application data in UDR.
Chunshan (Tencent) provide r04.
LiMeng (Huawei) wonder if we need to remove the changes on 7.1.1.0 of 6453 to avoid having overlapping proposals with 5628.
LiuWei(Panasonic) provide r05.
Robbie (Ericsson) provides r06 to move 7.1.1.0 to 5628.
Xiaoyan (CATT) provides r07.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) accepts r03, objects to all other revisions, and comments
Youngkyo(Samsung) prefer to keeping the current terms and so objects r03 and prefers r07.
Thomas (Nokia) asks Judy if she can accept r06 (provided by Ericsson), perhaps with some improvements
Suggest bringing this issue to the CC
Xiaoyan (CATT) accepts r01 and r02, and objects to other versions.
Xiaoyan (CATT) accepts r01, r02 and r07, and objects to other versions.
Youngkyo(Samsung) withdraw objection and may bring to CC.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106938 P-CR Approval 23.247: Updates to configuration procedures . Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2106453r03 + changes at CC#4, merging S2-2105639, S2-2105918, S2-2105956, S2-2106076, S2-2106090, S2-2106198, S2-2106352, S2-2106353 and S2-2106443. Approved Approved
8.9 S2-2106089 P-CR Approval 23.247: Updates to address the Editor's Note about how SMF requests MB-SMF to configure the multicast session. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106939 Judy (Ericsson) provide r01
Thomas (Nokia) provide r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106939 P-CR Approval 23.247: Updates to address the Editor's Note about how SMF requests MB-SMF to configure the multicast session. Huawei, HiSilicon Rel-17 Revision of S2-2106089r02. Approved Approved
8.9 S2-2105956 P-CR Approval 23.247: Update [7.1] MBS PCC configuration. Panasonic Corporation, DENSO CORPORATION Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
LiuWei (Panasonic) agrees to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105918 P-CR Approval 23.247: MBS authorization information provision during Session Configuration. CATT Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - Broadcast session management - - Docs:=8 -
8.9 S2-2105911 P-CR Approval 23.247: MBS Broadcast clarification. CBN, Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2106940 LiMeng (Huawei) provides r01.
Robbie (Ericsson) provides r02.
Thomas (Nokia) provides r03.
zhendong(ZTE) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106940 P-CR Approval 23.247: MBS Broadcast clarification. CBN, Huawei, HiSilicon, Ericsson, ZTE Rel-17 Revision of S2-2105911r04. Approved Approved
8.9 S2-2105921 P-CR Approval 23.247: MBS procedures for broadcast session. CATT Rel-17 r02 agreed. Revised to S2-2106941 Robbie (Ericsson) provides r01.
Robbie (Ericsson) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106941 P-CR Approval 23.247: MBS procedures for broadcast session. CATT, Ericsson Rel-17 Revision of S2-2105921r02. Approved Approved
8.9 S2-2105898 P-CR Approval 23.247: Update [7.3] MBS procedures for Broadcast Session. Samsung Rel-17 r01 agreed. Revised to S2-2106942 Youngkyo(Samsung) provides r01 based on the merging proposal
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106942 P-CR Approval 23.247: Update [7.3] MBS procedures for Broadcast Session. Samsung Rel-17 Revision of S2-2105898r01. Approved Approved
8.9 S2-2106525 P-CR Approval 23.247: Updates to Delivery Status Indication for Broadcast. Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2106943 Judy (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106943 P-CR Approval 23.247: Updates to Delivery Status Indication for Broadcast. Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2106525r01. Approved Approved
8.9 - - - Inter system mobility - - Docs:=9 -
8.9 S2-2106118 P-CR Approval 23.247: MBS procedures for inter System Mobility. Huawei, HiSilicon, LG Electronics Rel-17 Revision of (Noted) S2-2104393 from S2-145E. Noted Dario (Qualcomm) proposes to note this paper (following the outcome of CC#3's SoH).
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106119 P-CR Approval 23.247: Clarification on 5MBS interworking with eMBMS at transport layer. Huawei, HiSilicon, Rel-17 Merged with S2-2106363 (noted). Noted LiMeng (Huawei) suggests to merge this document into S2-2106363.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) supports the merge to 6363 (as per CC#3).
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106120 P-CR Approval 23.247: 5MBS interworking with eMBMS for same MBS service at both side. Huawei, HiSilicon Rel-17 Merged with S2-2106363 (noted). Noted LiMeng (Huawei) suggests to merge this document into S2-2106363.
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) supports the merge to 6363 (as per CC#3).
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106487 P-CR Approval 23.247: 5MBS interworking with eMBMS. Qualcomm Incorporated, Ericsson, LG Electronics, AT&T, FirstNet, Norwegian Communications Authority, Softil, Ministère de l'Intérieur Français, UK Home Office, Erillisverkot Rel-17 Revision of (Noted) S2-2104664 from S2-145E. r02 agreed. Revised to S2-2106944 Fenqin (Huawei) provides r01
Zhenhua (vivo) provides r02
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) is OK with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106944 P-CR Approval 23.247: 5MBS interworking with eMBMS. Qualcomm Incorporated, Ericsson, LG Electronics, AT&T, FirstNet, Norwegian Communications Authority, Softil, Ministère de l'Intérieur Français, UK Home Office, Erillisverkot Rel-17 Revision of S2-2106487r02. Approved Approved
8.9 S2-2106488 P-CR Approval 23.247: 5MBS interworking with eMBMS at transport layer. Qualcomm Incorporated, Ericsson, AT&T, FirstNet, Norwegian Communications Authority, Softil, Ministère de l'Intérieur Français, UK Home Office, Erillisverkot Rel-17 Revision of (Noted) S2-2104665 from S2-145E. r02 agreed. Revised to S2-2106945 Fenqin (Huawei) provides r01
Zhenhua (vivo) provides r02
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) is OK with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106945 P-CR Approval 23.247: 5MBS interworking with eMBMS at transport layer. Qualcomm Incorporated, Ericsson, AT&T, FirstNet, Norwegian Communications Authority, Softil, Ministère de l'Intérieur Français, UK Home Office, Erillisverkot Rel-17 Revision of S2-2106488r02. Approved Approved
8.9 S2-2106363 P-CR Approval 23.247: Adding 5G MBS and EPS eMBMS interworking architecture and modify the functionality description. ZTE Rel-17 Noted Fenqin (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) proposes to note this paper (following the outcome of CC#3's SoH).
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106364 P-CR Approval 23.247: Adding clause 7.4.2, MBMS interworking when the same service is not provided via eMBMS and 5MBS. ZTE Rel-17 Noted zhendong(ZTE) provides r01,
Zhenhua (vivo) comments
Fenqin (Huawei) comments
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) proposes to note this paper (following the outcome of CC#3's SoH).
==== 8.X, 9.X Final Deadline ====
Noted
8.9 - - - Intra system mobility and Handover related - - Docs:=10 -
8.9 S2-2106354 P-CR Approval 23.247: Discussion and proposal on the SMF awareness of target NG-RAN MBS capability in Xn HO. ZTE Rel-17 r03 agreed. Revised to S2-2106946 zhendong(ZTE) provides r01,
Zhenhua (vivo) provides r02,
Fenqin (Huawei) provides r03,
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) objects to r00, r01, r02 and can accept r03. Though it needs to be noted that the terminology '...giving MBS Context to..' needs to be corrected.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106946 P-CR Approval 23.247: Discussion and proposal on the SMF awareness of target NG-RAN MBS capability in Xn HO. ZTE Rel-17 Revision of S2-2106354r03. Approved Approved
8.9 S2-2105433 P-CR Approval 23.247: Update [7.2.3.4] Handover from non-supporting NG-RAN. Ericsson Rel-17 Merged into S2-2106948 LiMeng (Huawei) suggests to merge this document into S2-2106123.
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) suggests to note this paper.
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105888 P-CR Approval 23.247: Update [6.3] Mobility support of MBS service. Samsung Rel-17 r01 agreed. Revised to S2-2106947 LiMeng (Huawei) provides r01.
Youngkyo(Samsung) is okay with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106947 P-CR Approval 23.247: Update [6.3] Mobility support of MBS service. Samsung, Huawei Rel-17 Revision of S2-2105888r01. Approved Approved
8.9 S2-2106123 P-CR Approval 23.247: Resolve the EN for mobility support of MBS. Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106948, merging S2-2105433 Fenqin (Huawei) provides r01
Paul (Ericsson) provides r02.
Fenqin (Huawei) provides r03
zhendong(ZTE) provides the comments,
Fenqin (Huawei) provides response
Paul (Ericsson) provides r04.
Fenqin (Huawei ) provides r05.
Youngkyo(Samsung) provides r06.
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) objects to r00, 01, 03 and can accept r02, r04, r05 and r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106948 P-CR Approval 23.247: Resolve the EN for mobility support of MBS. Huawei, HiSilicon, Samsung Rel-17 Revision of S2-2106123r06, merging S2-2105433. Approved Approved
8.9 S2-2106124 P-CR Approval 23.247: Minimization of data loss. Huawei, HiSilicon Rel-17 Noted Paul (Ericsson) objects to this pCR. Given that RAN WGs have not yet progressed that topic, the proposal is not acceptable to be introduced.
Thomas (Nokia) provides r01
zhendong(ZTE) provides comments,
Fenqin (Huawei ) propose r02
Youngkyo(Samsung) proposes to note it and waiting RAN3 decision.
Zhenhua (vivo) cannot agree r00-r02
Fenqin (Huawei) provide a response
Zhenhua (vivo) provides r03
==== 8.X, 9.X Revisions Deadline ====
Youngkyo(Samsung) is okay with r03, but opposes to the other versions r00-r02.
Paul (Ericsson) objects to all revisions of this pCR, i.e. r00, r01, r02 and r03.
Fenqin (Huawei) suggest to bring it to CC#4.
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106356 P-CR Approval 23.247: Modification on the mobility clause 6.3.1 and 7.2.3 to resolve the EN and avoid the duplication. ZTE Rel-17 r03 agreed. Revised to S2-2106949 zhendong(ZTE) provides r01,
Fenqin (Huawei) provides r02,
Paul (Ericsson) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) objects to r01 and r02.
zhendong(ZTE) let go with r03 and make align with RAN3 in next meeting
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106949 P-CR Approval 23.247: Modification on the mobility clause 6.3.1 and 7.2.3 to resolve the EN and avoid the duplication. ZTE Rel-17 Revision of S2-2106356r03. Approved Approved
8.9 - - - Local MBS - - Docs:=16 -
8.9 S2-2105909 P-CR Approval 23.247: Update to Clause 6.9.1 about MBS Service Area. LG Electronics Rel-17 Merged into S2-2106925 LiMeng (Huawei) suggests to merge this document into S2-2106351.
LaeYoung (LGE) agrees to merge this document into S2-2106351.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105627 P-CR Approval 23.247: Local MBS Service with support for Group Message Delivery. KPN Rel-17 Noted Thomas (Nokia) proposes to note this contribution
Robbie (Ericsson) also propose to note this paper and the Group Message Delivery function could be a candidate for Rel-18 SID.
LiMeng (Huawei) wonders if the intention of this paper is only for clarifying the MBS service area can be geographical area.
Robbie (Ericsson) comments.
Jarmo (KPN) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106357 P-CR Approval 23.247: Resolving the ENs on Localised service [7.2.4]. ZTE Rel-17 Merged into S2-2106950 LiMeng (Huawei) suggests to merge this document into S2-2106077.
LiMeng (Huawei) suggests to merge this document into S2-2106122.
LiMeng (Huawei) withdraw the suggestion of merging S2-2106357 into S2-2106122.
Thomas (Nokia) suggest to merge this contribution into S2-2106077 as in LiMeng´s merging plan
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106420 P-CR Approval 23.247: Individual Delivery for location-Based Multicast services. Nokia, Nokia Shanghai-Bell Rel-17 Postponed Thomas (Nokia) provides r01
Robbie (Ericsson) raises concerns.
Thomas(Nokia) provides r02 to address the concerns of Robbie.
LiMeng (Huawei) provides r03 to simplify the content and remove the part not related to local MBS/location-dependent MBS.
Robbie (Ericsson) comments.
Fenqin (Huawei) provides r04.
Youngkyo(Samsung)provides r05.
==== 8.X, 9.X Revisions Deadline ====
Robbie (Ericsson) proposes to postpone this pCR.
Thomas(Nokia) replies to Robbie, suggest bringing this to cc
LiMeng (Huawei) agrees with Thomas.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106077 P-CR Approval 23.247: Local MBS term clarification. Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2106950, merging S2-2106335 and S2-2106357 Thomas (Nokia) comments and provides r01
Judy (Ericsson) provide comments
LiMeng (Huawei) responses and in general OK with the ideas in r01.
LaeYoung (LGE) comments.
LiMeng (Huawei) agrees LaeYoung that a separate clause would be clearer.
Judy (Ericsson) support LaeYoung's proposal to have a more structured sub-clause
LiMeng (Huawei) provides r02 based on r01 to include the merger of clause 6.2.
LaeYoung (LGE) asks a Q for clarification.
LiMeng (Huawei) replies to LaeYoung.
LaeYoung (LGE) replies to LiMeng (Huawei).
Paul (Ericsson) asks questions for clarification.
Thomas (Nokia) replies to Paul.
Paul (Ericsson) provides r04.
LiMeng (Huawei) provides r05, fix the title issue and remove the non-local MBS description.
Paul (Ericsson) provides r06.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106950 P-CR Approval 23.247: Local MBS term clarification. Huawei, HiSilicon Rel-17 Revision of S2-2106077r06, merging S2-2106335 and S2-2106357. Approved Approved
8.9 S2-2106335 P-CR Approval 23.247: Update of UUAA At PDN Connection/PDU Session Establishment. Huawei, HiSilicon Rel-17 Merged into S2-2106950 LiMeng (Huawei) suggests to merge this document into S2-2106122.
LiMeng (Huawei) suggests to merge this document into S2-2106077.
LiMeng (Huawei) withdraws the proposal for merging it into S2-2106122, suggests to merge it into 6077.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105759 P-CR Approval 23.247: MBS Session activation and deactivation for local MBS. Tencent Rel-17 Noted Thomas (Nokia) suggest to note this contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2105760 P-CR Approval 23.247: MBS Session Update for local MBS. Tencent Rel-17 Noted Thomas (Nokia) suggest to Note this contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2105892 P-CR Approval 23.247: Update [7.2.4.3] Handover procedure with limited area MBS session. Samsung Rel-17 Merged into S2-2106666 LiMeng (Huawei) suggests to merge this document into S2-2106122.
Thomas (Nokia) suggest to merge this contribution into S2-2106122 (as in the merging plan)
Youngkyo(Samsung)is okay to merge
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105906 P-CR Approval 23.247: Editorial update to Clause 7.2.4.3. LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2106122 P-CR Approval 23.247: Support of multicast service available within a limited area. Huawei, HiSilicon Rel-17 CC#4: r05 + changes agreed. Revised, merging S2-2105892 and S2-2106336, to S2-2106666. Fenqin (Huawei) provides r01
LaeYoung (LGE) provides r02.
Youngkyo(Samsung) provides r03.
Zhenhua (vivo) provides r04.
Paul (Ericsson) asks question for clarification.
Fenqin (Huawei) provide a response
Paul (Ericsson) provides r05.
Fenqin (Huawei) provides r06.
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) comments and proposes to add an EN: Details of Xn handover procedure will be aligned with RAN3. This section makes a lot of assumption on Xn handover stage 3 level details and thus we think it is appropriate to add that EN.
R07 is uploaded in DRAFTS folder.
Thomas(Nokia) accepts r05, objects against other revisions
Fenqin (Huawei) provide a comment and propose to bring it to CC#4
Thomas(Nokia) replies to Fenqin
Fenqin (Huawei) suggest to check with r07.
Thomas(Nokia) replies to Fenqin and suggests to postpone this document
==== 8.X, 9.X Final Deadline ====
Youngkyo(Samsung) prefers not to postpone the whole paper.
Thomas(Nokia) could agree r05 with editor´s notes
Fenqin (Huawei) propose to bring this to CC#4
Revised
8.9 S2-2106666 P-CR Approval 23.247: Support of multicast service available within a limited area. Huawei, HiSilicon, Samsung Rel-17 Revision of S2-2106122r05 + changes, merging S2-2105892 and S2-2106336. Approved Approved
8.9 S2-2106336 P-CR Approval 23.247: Modification on local MBS service with limited area. vivo Rel-17 Merged into S2-2106666 LiMeng (Huawei) suggests to merge this document into S2-2106122.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106450 P-CR Approval 23.247: Changing service area of multicast session. Nokia, Nokia Shanghai-Bell Rel-17 CC#4: r02 + changes agreed. Revised to S2-2106667. Judy (Ericsson) ask a Q
LiMeng (Huawei) considers to use a separate clause.
LiMeng (Huawei) provides r01.
Judy (Ericsson) comments
LiMeng (Huawei) provides r02
Thomas(Nokia) accepts r02
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comments that having QoS update clause separated from MBS service area update does not show the synergy when both QoS and Area are updated, therefore propose to postpone.
Thomas(Nokia) replies to Judy,
raises concern that Judy came with her comment very shortly before revision deadline.
Suggest a way forward for the CC.
Judy (Ericsson) responds to Thomas(Nokia) and propose to postpone to next meeting when a more stable baseline is available.
Thomas(Nokia) replies to Judy.
LiMeng (Huawei) suggests to discuss it in CC#4, based on r02 and add a NOTE.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106667 P-CR Approval 23.247: Changing service area of multicast session. Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2106450 r02 + changes. Approved Approved
8.9 - - - Protocol Stack - - Docs:=7 -
8.9 S2-2105634 P-CR Approval 23.247: Update [8.1] Control Plane Protocol Stack. Ericsson Rel-17 r01 agreed. Revised to S2-2106951, merging S2-2105899 Youngkyo(Samsung) provide r01.
Zhenhua (vivo) comments.
Youngkyo(Samsung) replies
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106951 P-CR Approval 23.247: Update [8.1] Control Plane Protocol Stack. Ericsson, Samsung Rel-17 Revision of S2-2105634r01, merging S2-2105899. Approved Approved
8.9 S2-2105635 P-CR Approval 23.247: Update [8.2] User Plane Protocol Stack. Ericsson Rel-17 Merged into S2-2106952 LiMeng (Huawei) suggests to merge this document into S2-2106350
Robbie (Ericsson) confirms 5635 is merged in 6350
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105757 P-CR Approval 23.247: Update the User Plane Protocol Stack for MBS session. Tencent Rel-17 Merged into S2-2106952 LiMeng (Huawei) suggests to merge this document into S2-2106350
LiMeng (Huawei) comments.
Chunshan (Tencent) confirms this paper to be merged into S2-2106350.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105899 P-CR Approval 23.247: Update [8] Control and user plane stacks. Samsung Rel-17 Merged into S2-2106951 LiMeng (Huawei) suggests to merge this document into S2-2105634
==== 8.X, 9.X Revisions Deadline ====
Youngkyo(Samsung) is okay to merge into S2-2105634
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106350 P-CR Approval 23.247: Modification on clause 8, Protocol stack description. ZTE Rel-17 r06 agreed. Revised to S2-2106952, merging S2-2105635 and S2-2105757 Robbie (Ericsson) provides r01, merge 5635 in.
Youngkyo(Samsung) provides r02 and ask a question.
Robbie (Ericsson) provides r03 and clarifies to Youngkyo(Samsung).
Youngkyo(Samsung) provide comments.
Robbie (Ericsson) provides r04 and clarifies to Youngkyo(Samsung).
zhendong(ZTE) is fine with r04,
Chunshan (Tencent) requests to add as co-sign company, but still has some comments.
Robbie (Ericsson) provides r05 and answers to Chunshan (Tencent).
Thomas (Nokia) provides r06
Robbie (Ericsson) asks Thomas (Nokia)
Thomas (Nokia) replies to Robbie
Robbie (Ericsson) replies to Thomas (Nokia)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106952 P-CR Approval 23.247: Modification on clause 8, Protocol stack description. ZTE, Ericsson, Samsung, Tencent Rel-17 Revision of S2-2106350r06, merging S2-2105635 and S2-2105757. Approved Approved
8.9 - - - NF services - - Docs:=26 -
8.9 S2-2105638 P-CR Approval 23.247: Update [9.1] MB-SMF services and Resolving ENs. Ericsson Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
Judy (Ericsson) is OK to merge 5638 to 6427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105639 P-CR Approval 23.247: Update [7.1] Common Procedure with modified MB-SMF service operation . Ericsson Rel-17 Merged into S2-2106938 LiMeng (Huawei) suggests to merge this document into S2-2105653 or S2-2106453.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105640 P-CR Approval 23.247: Update [7.2] Multicast procedures with updated MB-SMF services . Ericsson Rel-17 Merged into S2-2106665 LiMeng (Huawei) suggests to merge this document into S2-2106507.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105641 P-CR Approval 23.247: Add in [9.3] new AMF service for broadcast communication. Ericsson Rel-17 r02 agreed. Revised to S2-2106953 zhendong(ZTE) provides r01,
Xiaoyan (CATT) provides r02.
zhendong(ZTE) provides the comments,
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106953 P-CR Approval 23.247: Add in [9.3] new AMF service for broadcast communication. Ericsson, CATT Rel-17 Revision of S2-2105641r02. Approved Approved
8.9 S2-2105642 P-CR Approval 23.247: Update [7.3] with the new AMF service for broadcast MBS Session. Ericsson Rel-17 r01 agreed. Revised to S2-2106954 Robbie (Ericsson) provides r01 based on merging proposal
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106954 P-CR Approval 23.247: Update [7.3] with the new AMF service for broadcast MBS Session. Ericsson Rel-17 Revision of S2-2105642r01. Approved Approved
8.9 S2-2105817 P-CR Approval 23.247: Add in [9.x] new NEF service for MBS. Ericsson Rel-17 Merged into S2-2106958 LiMeng (Huawei) suggests to merge this document into S2-2106445.
Judy (Ericsson) comments that this paper is merged into 6445 propose by the rapporteur.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105819 CR Approval 23.501 CR3092 (Rel-17, 'B'): Add NF services for 5G MBS Ericsson Rel-17 r02 agreed. Revised to S2-2106955, merging S2-2106456, S2-2106457 and S2-2106520. CC#5: Huawei object to r02. Ericsson could not accept r01. Noted Thomas (Nokia) provides r01
Judy (Ericsson) provide r02 to avoid repeating the description of enhanced NF functionality in both 23.501 and 23.247
Thomas (Nokia) objects against r02, and clarifies that the disputed change is not about general NRF functionality but about NF profiles stored in NRF
Judy (Ericsson) responds to Thomas (Nokia)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106955 CR Approval 23.501 CR3092R1 (Rel-17, 'B'): Add NF services for 5G MBS Ericsson Rel-17 Revision of S2-2105819r02, merging S2-2106456, S2-2106457 and S2-2106520. Approved. WITHDRAWN Withdrawn
8.9 S2-2105907 P-CR Approval 23.247: Clause 9.1.4: adding MBS service area to Nmbsmf_Information service. LG Electronics Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
LaeYoung (LGE) agrees to merge this document into S2-2106427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106454 P-CR Approval 23.247: AMF multicast service notification service. Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2106956 Judy (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106956 P-CR Approval 23.247: AMF multicast service notification service. Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2106454r01. Approved Approved
8.9 S2-2106427 P-CR Approval 23.247: MB-SMF Service Operation names. Nokia, Nokia Shanghai-Bell, Huawei Rel-17 r10 agreed. Revised to S2-2106957, merging S2-2105638, S2-2105907, S2-2105922, S2-2106449, S2-2106463 and S2-2106465 Thomas (Nokia) provides r01
This also merges content of S2-2106463, S2-2106449, S2-2106465, S2-2105907 and S2-2105922
LiMeng (Huawei) agrees the merging proposals and provides r02.
Thomas (Nokia) provides r03.
Judy (Ericsson) provides r04
Thomas (Nokia) provides r05 and objects against r04
Judy (Ericsson) objects to r05, as some of the proposed service operations are not consistent with the SBI design practice in our view. Explained.
Thomas(Nokia) reminds Judy that in the preparatory Telco the majority wanted to keep service operations separate and only merge the underlying service.
We should take an evolutionary approach and refine understood operations instead of defining poorly understood new ones. Progress is important for stage 3 groups.
Judy (Ericsson) request Thomas(Nokia) to provide technical reasons.
Fenqin (Huawei ) provides comments.
Judy (Ericsson) thanks Fenqin (Huawei)'s comment and responds.
Judy (Ericsson) responds to Fenqin (Huawei)
Judy (Ericsson) responds to Fenqin (Huawei )
Judy (Ericsson) provide r06 based on our offline discussion
Thomas (Nokia) provide r07
Judy (Ericsson) provide r08
Thomas (Nokia) accepts r08
Xiaoyan (CATT) provide r09.
Thomas (Nokia) provide r10.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106957 P-CR Approval 23.247: MB-SMF Service Operation names. Nokia, Nokia Shanghai-Bell, Huawei, Ericsson, CATT Rel-17 Revision of S2-2106427r10, merging S2-2105638, S2-2105907, S2-2105922, S2-2106449, S2-2106463 and S2-2106465. Approved Approved
8.9 S2-2106445 P-CR Approval 23.247: NEF MBS services. Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2106958, merging S2-2105817 Judy (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106958 P-CR Approval 23.247: NEF MBS services. Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2106445r01, merging S2-2105817. Approved Approved
8.9 S2-2105922 P-CR Approval 23.247: MB-SMF Services. CATT Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2105923 P-CR Approval 23.247: MBSF Services. CATT Rel-17 r01 agreed. Revised to S2-2106959 Xiaoyan (CATT) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106959 P-CR Approval 23.247: MBSF Services. CATT Rel-17 Revision of S2-2105923r01. Approved Approved
8.9 S2-2105924 P-CR Approval 23.247: SMF Services. CATT Rel-17 Noted LiMeng (Huawei) suggests to note this document
Xiaoyan (CATT) is fine with noting this pCR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2105925 P-CR Approval 23.247: AMF services. CATT Rel-17 r01 agreed. Revised to S2-2106960 Thomas (Nokia) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106960 P-CR Approval 23.247: AMF services. CATT Rel-17 Revision of S2-2105925r01. Approved Approved
8.9 S2-2106449 P-CR Approval 23.247: Nmbsmf_TMGI and Nmbsmf_MBSSession service updates. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106463 P-CR Approval 23.247: Updates to Nmbsmf_Information service. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106465 P-CR Approval 23.247: Updates to Nmbsmf_Reception service. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2106957 LiMeng (Huawei) suggests to merge this document into S2-2106427.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - Other 501/502/503 - - Docs:=11 -
8.9 S2-2105901 CR Approval 23.502 CR3006 (Rel-17, 'F'): Release of PDU Session associated with an MBS session Samsung Rel-17 Postponed Thomas (Nokia) raises concerns against this contribution
Youngkyo(Samsung) replies to Thomas (Nokia) and provides r01
Judy (Ericsson) comments the issue raised in this paper may be valid, and the enhancement (if any) to the procedure in 23.502 should be captured in 23.287
LaeYoung (LGE) proposes to postpone this CR.
Zhenhua (vivo) proposes to note or postpone this CR.
Youngkyo(Samsung) is okay to postpone this CR, but provide additional explanation on the idea.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106470 CR Approval 23.501 CR3226 (Rel-17, 'F'): UPF configuration for traffic replication for MBS Nokia, Nokia Shanghai-Bell Rel-17 Postponed Thomas (Nokia) suggest to focus the discussion in the S2-2106469 thread
Thomas (Nokia) suggest to postpone this contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106472 CR Approval 23.501 CR3227 (Rel-17, 'B'): SMF discovery for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Noted LiMeng (Huawei) proposes to note this document.
Judy (Ericsson) assumes this paper is NOTED as the new SMF capability of MBS is considered unnecessary.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2106475 CR Approval 23.502 CR2757R3 (Rel-17, 'B'): UDM extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Withdrawn) S2-2104009 from S2-145E. Merged into S2-2106961 LiMeng (Huawei) suggests to merge this document into S2-2106491.
Thomas (Nokia) accepts to merge this document into S2-2106491.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106491 CR Approval 23.502 CR2878R1 (Rel-17, 'B'): BSF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2104785 from S2-145E. r05 agreed. Revised to S2-2106961, merging S2-2106475 and S2-2106523 Thomas (Nokia) provides r01 to add extensions to Namf_MT service
Zhenhua (vivo) ask for clarification for r01
Thomas(Nokia) replies to Zhenhua
Zhenhua (vivo) comments
Thomas (Nokia) replies to Zhenhua
Thomas (Nokia) provides r02 to merge S2-2106523
Thomas (Nokia) provides r03 to merge S2-2106475
Judy (Ericsson) asks if the correct TS revision is used.
Thomas (Nokia) provides r04 to address the concerns of Judy
Judy (Ericsson) provide r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2106961 CR Approval 23.502 CR2878R2 (Rel-17, 'B'): Service extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106491r05, merging S2-2106475 and S2-2106523. Approved Agreed
8.9 S2-2106520 CR Approval 23.501 CR2877R1 (Rel-17, 'B'): NRF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Noted) S2-2104003 from S2-145E. Confirm CR Revision - CR states -1! Merged into S2-2106955 LiMeng (Huawei) suggests to merge this document into S2-2105819.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106523 CR Approval 23.502 CR3121 (Rel-17, 'B'): NRF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106961 LiMeng (Huawei) suggests to merge this document into S2-2106491.
Thomas (Nokia) provides r01
Thomas (Nokia) accepts to merge this document into S2-2106491.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106437 CR Approval 23.503 CR0579R1 (Rel-17, 'B'): PCC impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2104017 from S2-145E. Postponed Judy (Ericsson) comments and propose to postpone this paper.
Thomas (Nokia) raises concerns that this contribution was already postponed to give other companies time to check but there were no other proposals and this is the last meeting.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2106456 CR Approval 23.501 CR3223 (Rel-17, 'B'): AMF impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106955 LiMeng (Huawei) suggests to merge this document into S2-2105819.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2106457 CR Approval 23.501 CR3224 (Rel-17, 'B'): NEF impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2106955 LiMeng (Huawei) suggests to merge this document into S2-2105819.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=59 -
8.10 - - - Exception #1: Enabling of paging reception for 5GS - - Docs:=9 -
8.10 S2-2105266 LS In Action LS from RAN WG2: Reply LS on UE assistance information for paging collision avoidance RAN WG2 (R2-2106517) Rel-17 Responses drafted in S2-2105597 and S2-2105998. Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 S2-2105597 LS OUT Approval [DRAFT] LS reply on UE assistance information for paging collision avoidance vivo Rel-17 Response to S2-2105266. Noted Qian (Ericsson) comments that this paper shall be NOTED if 5998 is to be used as baseline.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105998 LS OUT Approval [DRAFT] Reply LS on UE assistance information for paging collision avoidance Sony Rel-17 Response to S2-2105266. Noted Lars (Sony) provides r01
Qian (Ericsson) comments that the fate of the LS shall be linked to outcome of 5975
==== 8.X, 9.X Revisions Deadline ====
Lars (Sony) confirms that r01 is linked to the approval of 5975 and 5982
Saso (Intel) thinks that regardless of the outcome on 5975, there is no need for this LS. Proposes to NOTE it.
Lars (Sony) RAN2 asked SA2 to confirm NAS based solution. This is the reason to send an LS in the first place.
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105951 DISCUSSION Agreement Discussion on enabling paging reception in 5GS. Sony, Nokia, Nokia Shanghai Bell, Convida Wireless, NEC, Interdigital Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105489 CR Approval 23.502 CR2920 (Rel-17, 'F'): Exception #1: Enabling of paging reception for 5GS Intel Rel-17 CC#5: r01 revised to S2-2106824. xiaowan (vivo) comments the need of the CR
Saso (Intel) replies to xiaowan (vivo)
Alessio(Nokia) comments this is alternative to S2-2105982 so it should be approved only if the other CR is not approved.
Guillaume (MediaTek) agrees with Saso (Intel)
xiaowan (vivo) replies Saso(Intel) and has further comments
Lars (Sony) comments
Xiaowan(vivo) shares Lars (Sony) 's view and proposes to postpone or note this CR
Steve (Huawei) comments
Saso (Intel) disagrees with postponing. This CR has been postponed THREE times already.
Saso (Intel) provides r01
Lars (Sony) this CR is not needed
Alessio(Nokia) we also agree this is not needed if no AI is provided as this becomes an option any UE vendor can use (there is no prohibition to originate a MRU at any time I think)... but also we reaffirm that this approach would be suboptimal and also more energy inefficient so we still hope the CR by Lars is approved.
Saso (Intel) fails to see the logic in Lars's and Alessio's replies. Whether AI is used or not, the trigger needs to be described. The AI-based alternative in 5982 uses identical wording for the description of the trigger.
Lars (Sony) responds to Saso
==== 8.X, 9.X Revisions Deadline ====
Lars (Sony) propose to Note this CR.
Xiaowan (vivo) objects r00 and r01
Alessio(Nokia) requests this topic to be handled in CC#4 and objects to an approach that does not allow AI to be provided (including this CR). some companies are not allowing some others to have a more energy efficient solution.
Lars (Sony) I support Alessio(Nokia) and also requests this topic to be handled in CC#4.
Jianning (Xiaomi) share the view with Xiaowan (vivo), don't see the need of new trigger for new 5G-GUTI assignment, instead of UE implementation way.
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106824 CR Approval 23.502 CR2920R1 (Rel-17, 'F'): Exception #1: Enabling of paging reception for 5GS Intel, MediaTek Inc., Ericsson, Huawei, HiSilicon, Charter Communications, LG Electronics, OPPO, T-Mobile USA, Orange, Samsung, Telefónica, Vodafone, Apple Rel-17 Revision of S2-2105489r01. Technically endorsed Endorsed
8.10 S2-2105954 CR Approval 23.761 CR0001 (Rel-17, 'B'): Conclusion enabling paging reception in 5GS Sony, Nokia, Nokia Shanghai Bell, NEC, Convida Wireless, Interdigital Rel-17 Noted Saso (Intel) proposes to NOTE the CR.
Steve (Huawei) Agrees with Saso (Intel), NOTING is best.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105975 CR Approval 23.501 CR3121 (Rel-17, 'B'): Introduction of enabling paging reception Sony, Nokia, Nokia Shanghai Bell, NEC, Convida Wireless, Interdigital Rel-17 Noted Saso (Intel) seeks clarification on the Assistance Information.
Lars (Sony) reply to Saso in order to clarify on the Assistance Information.
Guillaume (MediaTek) comments.
Lars (Sony) comments.
Guillaume (MediaTek) replies.
Steve (Huawei) comments, no agreement to added it.
Jianning (Xiaomi) shares view with Guillaume (MediaTek) and Steven (Huawei),
Alessio(Nokia) supports including assistance information
Xiaowan(vivo) supports including assistance information with regard to extra benefit, e.g. power saving
Saad (Interdigital) supports including assistance info for 5GS
Juan Zhang (Qualcomm) is fine to provide assistance information
Saso (Intel) seeks clarification from Juan Zhang (Qualcomm)
Juan Zhang (Qualcomm) replies to Saso (intel)
Lars (Sony) replies to Saso (intel)
Guillaume (MediaTek) provides comments.
Guillaume (MediaTek) asks for clarification
Lars (Sony) reply to Guillaume (MediaTek).
Guillaume (MediaTek) replies to Lars (Sony)
Lars (Sony) provides r01
Ouyang(Huawei) objects to this CR.
alessio(Nokia) is ok with r01 and also believes there is no need to have further LS interactions. However a reply LS to RAN2 with CT1 in CC could be useful to announce the decision SA2 has taken (and ofcourse the receiving groups may provide any feedback if something is wrong in the CR we attach)
Jianning (Xiaomi) provides comment
Lars (Sony) provides r02
Qian (Ericsson) provides comments and ask questions
Lars (Sony) responds to Qian (Ericsson)
Lars (Sony) provides r03
Steve (Huawei) objects to all revisions of the CR.
alessio(Nokia) notes power saving is a general standing criterion for anything we do in 3GPP. We normally choose the most power efficient solution if alternatives are possible.
Guillaume (MediaTek) comments (incl. repetitions).
Lars (Sony) responds to Guillaume (MediaTek) and provides r04.
alessio(nokia) can accept r04.
==== 8.X, 9.X Revisions Deadline ====
alessio(nokia) kindly requests to discuss this in CC#4 as the majority of companies seemed in favor of adding the AI as an option.
Lars (Sony) request this topic to be discussed in CC4
Jianning (Xiaomi) insist object the 5GS reception with AI as we expressed many times before.
Steve (Huawei) repeats objection to all revisions.
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105982 CR Approval 23.502 CR2631R3 (Rel-17, 'B'): Introduction of enabling paging reception Sony, Nokia, Nokia Shanghai Bell, NEC, Convida Wireless, Interdigital, [Intel] Rel-17 Revision of (Postponed) S2-2104159 from S2-145E. Noted Guillaume (MediaTek) comments.
Lars (Sony) provides r01.
Steve (Huawei) objects to all revisions of the CR.
Lars (Sony) provides r02
==== 8.X, 9.X Revisions Deadline ====
Lars (Sony) request this topic to be discussed in CC4
Steve (Huawei) repeats objection to all revisions.
==== 8.X, 9.X Final Deadline ====
Noted
8.10 - - - Exception #2: Alignment with RAN WG2 regarding Rejection of RAN Paging - - Docs:=4 -
8.10 S2-2105280 LS In Information LS from RAN WG3: Reply LS on NAS-based busy indication RAN WG3 (R3-212877) Rel-17 Noted Steve (Huawei) should be noted?
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105370 LS In Action LS from RAN WG2: Reply LS on NAS-based busy indication RAN WG2 (R2-2108855) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 S2-2105490 CR Approval 23.502 CR2921 (Rel-17, 'F'): Exception #2: On alignment with RAN WG2 regarding Rejection of RAN paging Intel Rel-17 r01 agreed. Revised to S2-2106787 Saso (Intel) proposes r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106787 CR Approval 23.502 CR2921R1 (Rel-17, 'F'): Exception #2: On alignment with RAN WG2 regarding Rejection of RAN paging Intel Rel-17 Revision of S2-2105490r01. Approved Agreed
8.10 - - - Exception #3: Applicability of 5GS NAS vs AS leaving procedure - - Docs:=13 -
8.10 S2-2105265 LS In Action LS from RAN WG2: LS on Network Switching for MUSIM RAN WG2 (R2-2106504) Rel-17 Responses drafted in S2-2105596 and S2-2106003. FInal response in S2-2106673
==== 8.X, 9.X Final Deadline ====
Replied to
8.10 S2-2105596 LS OUT Approval [DRAFT] LS reply on Network Switching for MUSIM vivo Rel-17 Response to S2-2105265. CC#4: Merged into S2-2106673. Saso (Intel) proposes to NOTE this document and use S2-2106003 as the basis for the reply LS.
Xiaowan(vivo) ask Saso (Intel) to give technical comment firstly rather than proposes to NOTE only
Saso (Intel) replies to Xiaowan.
Xiaowan (vivo) provides r01 based on the discussion in S2-2105598
Alessio(nokia) thinks that the proposal by Saso makes sense. (i.e. Nokia supports Intel)
Steve (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) re-uploads as r03, as there was some problem with the zip of r02.
Steve (Huawei) checks of we send this should we note S2-2106003?
Juan Zhang (Qualcomm) proposes to note this one and go with S2-2106003r05.
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2106003 LS OUT Approval [DRAFT] Reply LS on Network Switching for MUSIM Qualcomm communications-France Rel-17 Response to S2-2105265. CC#4: r05 agreed. Revised, merging S2-2105596, to S2-2106673. Juan Zhang (Qualcomm) provides r01.
xiaowan (vivo) disagree original version and r01
Alessio(Nokia) comments that it is up to the UE to decide what to do also taking into account the differences. this is not in conflict with the text
Xiaowan(vivo) replies to Alessio(Nokia) : the text doesn't state what you said 'also taking into account the differences'
Juan Zhang (Qualcomm) replies to Xiaowan
Saso (Intel) provides r02
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) provides r04
Curt (Charter) supports r03
xiaowan (vivo) replies
Juan Zhang (Qualcomm) provides r05 for further wording update
Steve (Huawei) is ok with r05
Qian (Ericsson) supports r05
Guillaume (MediaTek) also supports r05.
Steve (Huawei) checks of we send this should we note S2-2105596?
==== 8.X, 9.X Final Deadline ====
Saso (Intel) indicates that the proponents of 5596 have confirmed that they can live with certain revision of 6003. Therefore 6003 should be the LS reply.
Revised
8.10 S2-2106673 LS OUT Approval Reply LS on Network Switching for MUSIM SA WG2 Rel-17 Revision of S2-2106003r05, merging S2-2105596. Approved Approved
8.10 S2-2105595 DISCUSSION Agreement Discussion on Paging Restriction Information for RAN level connection release. vivo Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105491 DISCUSSION Agreement Exception #3: On applicability of the 5GS NAS leaving procedure vs the AS leaving procedure(s). Intel Rel-17 Noted Lalith(Samsung) agrees with proposals in the paper. For CR prefers S2-2106000
Ouyang(Huawei) proposes to NOTE this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105679 DISCUSSION Agreement Discussion on AN Release Procedure for MUSIM Connection Release. Huawei, HiSilicon Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105999 DISCUSSION Discussion Discussion about NAS and AS leaving. Qualcomm Incorporated Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105492 CR Approval 23.501 CR3022 (Rel-17, 'F'): Exception #3: On applicability of the 5GS NAS leaving procedure vs the AS leaving procedure(s) Intel Rel-17 Merged into S2-2106674 Lalith(Samsung) proposes to merge this CR into S2-2106000
Saso (Intel) is fine to merge, but prefers using S2-2105807 as a basis
Juan Zhang (Qualcomm) replies to Saso (Intel).
Saso (Intel) replies to Juan Zhang (Qualcomm).
Lars (Sony) proposes to mark this merged in S2-2105807
Saso (Intel) is OK to merge this document in S2-2105807
Curt (Charter) comments
Ouyang(Huawei) comments
Alessio(Nokia) also proposes to merge this CR into S2-2106000
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2105598 CR Approval 23.501 CR3047 (Rel-17, 'F'): Update for NAS level connection and RAN level connection release vivo Rel-17 Merged into S2-2106674 Saso (Intel) proposes to NOTE this document or consider it merged in 5492, 6000 or 5807 (whichever is chosen as the basis).
Xiaowan(vivo) replies to Saso (Intel)
Myungjune (LGE) provides comment.
Saso (Intel) replies to Xiaowan(vivo)
Xiaowan(vivo)replies to Saso (Intel) and Myungjune (LGE)
Curt (Charter) comments
Saso (Intel) replies to Curt (Charter) and Xiaowan (vivo).
Lars (Sony) ask a question
Qian (Ericsson) comments
Steve (Huawei) comments
Myungjune (LGE) comments
Ouyang(Huawei) comments.
Myungjune (LGE) replies to Ouyang (Huawei)
Juan Zhang (Qualcomm) provides comments
Lars (Sony) agrees with Juan Zhang (Qualcomm)
Saso (Rapporteur) proposes to agree that there are no PRs in AS connection release.
Lars (Sony) proposes to mark this merged in S2-2105807
In order not to bring in extra complexity in the maintenance phase, Xiaowan (vivo) can compromise to agree that there are no PRs in AS connection release and propose to send LS to RAN, as alt1 in draft LS S2-2105596.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2106000 CR Approval 23.501 CR3125 (Rel-17, 'F'): Clarification about RRC leaving and NAS leaving procedure Qualcomm Incorporated Rel-17 Merged into S2-2106674 Lars (Sony) proposes to mark this merged in S2-2105807
Juan Zhang (Qualcomm) is fine to merge in S2-2105807.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2105807 CR Approval 23.501 CR3088 (Rel-17, 'B'): 5GS Connection release support for 5GC/NR Ericsson, Charter, Comcast Rel-17 CC#4: r21 + changes agreed. Revised, merging S2-2105492, S2-2105598 and S2-2106000, to S2-2106674. xiaowan (vivo) comments
Lars (Sony) provides r01
Juan Zhang (Qualcomm) provides r03.
Curt (Charter) comments
Steve (Huawei) comments
xiaowan (vivo) provides r04
Curt (Charter) provides r05.
Saso (Intel) comments.
Qian (Ericsson) provides comments.
Juan Zhang (Qualcomm) provides comments
Saso (Intel) replies to Qian (Ericsson).
Steve (Huawei) provides r06
Lars (Sony) provides r07
Juan Zhang (Qualcomm) provides r08.
Lars (Sony) r08 looks good, fixing typo in NOTE 1 and provides r09.
Qian (Ericsson) comments and provides r10.
Juan Zhang (Qualcomm) is OK with r10.
Steve (Huawei) approach in r10 is fine, minor editorial update in r11.
Alessio(Nokia) provides r12
Qian (Ericsson) comments and provides r13.
Myungjune (LGE) provides r14.
Juan Zhang (Qualcomm) is fine with r14.
Lars (Sony) we are also fine with r14, fixing one type and provides r15.
xiaowan (vivo) disagree r14, r15 and provide r16
alessio(Nokia provides r17 to clean up and provide improved text and support.
Qian (Ericsson) provides comments and r18.
Juan Zhang (Qualcomm) comments and provides r19.
alessio(Nokia) is ok with r19.
xiaowan (vivo) provides r20
Saso (Intel) provides r21
Juan Zhang (Qualcomm) supports r19 or r21.
xiaowan (vivo) comments and provide r22
Saso (Intel) invites Xiaowan to check the LS reply in S2-2106003r02. This should alleviate vivo's concern and allow SA2#146E to proceed with r21 of this document.
==== 8.X, 9.X Revisions Deadline ====
Xiaowan(vivo) replies to Saso (Intel) that the wording in S2-2106003r03/r04 is acceptable
Juan Zhang (Qualcomm) provides r23 to add the example in NOTE 1.
Qian (Ericsson) can accept r21 or r22.
Juan Zhang (Qualcomm) replies to Qian
Qian (Ericsson) asks further questions
Juan Zhang (Qualcomm) provides r24
Qian (Ericsson) says ok with r24
Saso (Intel) supports r24.
Xiaowan (vivo) can live with r24, but disagree r23
Qian (Ericsson) addresses the comment from Xiaowan(vivo) in r25
Alessio(Nokia) provides some editorials in r26.
Juan Zhang (Qualcomm) replies to Qian.
Steve (Huawei) provides r27, another editorial version.
Qian (Ericsson) indicates that r27 seems a good revision to go and requests this to be discussed in CC#4
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106674 CR Approval 23.501 CR3088R1 (Rel-17, 'B'): 5GS Connection release support for 5GC/NR Ericsson, Charter, Comcast, Nokia, Nokia Shanghai Bell, LG Electronics, vivo, Intel, Lenovo, Motorola Mobility, Qualcomm Incorporated Rel-17 Revision of S2-2105807r21 + changes, merging S2-2105492, S2-2105598 and S2-2106000. Approved Agreed
8.10 - - - Missing stage 2 functional description - - Docs:=2 -
8.10 S2-2105765 CR Approval 23.401 CR3650 (Rel-17, 'F'): MUSIM and CIOT Intel Rel-17 Approved Myungjune (LGE) comments.
Ouyang(Huawei) comments
Saso (Intel) replies
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2106490 CR Approval 23.272 CR0974 (Rel-17, 'F'): Reject Paging for CS domain paging Intel Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 - - - Capability exchange - - Docs:=3 -
8.10 S2-2106340 CR Approval 23.502 CR3088 (Rel-17, 'F'): Clarification on MUSIM capcability exchange China Telecom Rel-17 r02 agreed. Revised to S2-2106788 xiaowan (vivo) provides r01
Jianning (Xiaomi) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106788 CR Approval 23.502 CR3088R1 (Rel-17, 'F'): Clarification on MUSIM capability exchange China Telecom Rel-17 Revision of S2-2106340r02. Approved Agreed
8.10 S2-2105496 CR Approval 23.401 CR3646 (Rel-17, 'F'): UE indication of support for Paging Timing Collision Control Intel Rel-17 CC#4: Postponed Juan Zhang (Qualcomm) provides comments
Alessio(nokia) provides r01 that selects Option 2
Saso (Intel) is OK with r01 if the group prefers to move forward with Option 2
Juan Zhang (Qualcomm) is fine with r01.
Qian (Ericsson) asks question.
Saso (Intel) replies to Qian. Provides r02 which is based on r01 with cleaned up cover page
==== 8.X, 9.X Revisions Deadline ====
Jianning (Xiaomi) provides question for clarification on r01 and r02
Saso (Intel) replies to Jianning (Xiaomi)
Jianning (Xiaomi) provides further comment
Jianning (Xiaomi) replies to Saso (Intel), and suggest to postpone this CR to next meeting.
Saso (Intel) thinks there is no reason provided for postponing and from Intel's perspective there is no remaining issue to fix.
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 - - - Paging Cause - - Docs:=8 -
8.10 S2-2105599 CR Approval 23.401 CR3647 (Rel-17, 'F'): Update Paging Cause Feature in EPS vivo Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2105600 CR Approval 23.501 CR3048 (Rel-17, 'F'): Update Paging Cause Feature in 5GS vivo Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2105809 CR Approval 23.501 CR3089 (Rel-17, 'F'): Paging cause indication correct for 5GC/E-UTRA Ericsson Rel-17 Noted xiaowan (vivo) comment the need of the CR
Myungjune (LGE) comments.
Saso (Intel) has the same view as Xiaowan (vivo) and Myungjune (LGE) comments. Proposes to NOTE the CR.
Qian (Ericsson) provides comments.
Juan Zhang (Qualcomm) supports the comments from xiaowan and Saso and proposes to NOTE the CR.
Saso (Intel) replies to Qian (Ericsson).
Qian (Ericsson) replies to Saso (Intel).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105810 CR Approval 23.502 CR2989 (Rel-17, 'F'): Paging cause indication correct for 5GC/E-UTRA Ericsson Rel-17 Noted xiaowan (vivo) comment the need of the CR
Saso (Intel) has the same view as Xiaowan (vivo). Proposes to NOTE the CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105961 DISCUSSION Discussion Discussion on paging cause for P-CSCF restoration. LG Electronics, SK Telecom, KT Corp., LG Uplus Rel-17 Noted Saso (Intel) comments.
xiaowan (vivo) seeks clarification for the feasibility
Myungjune (LGE) replies to Saso (Intel) and Xiaowan (vivo).
Saso (Intel) replies to Myungjune.
Qian (Ericsson) provides comments.
Myungjune (LGE) replies.
Steve (Huawei) comments
Myungjune (LGE) replies to Steve (Huawei)
==== 8.X, 9.X Revisions Deadline ====
Ouyang(Huawei) indicates this is a discussion paper and should be noted.
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105962 CR Approval 23.401 CR3651 (Rel-17, 'F'): Paging Cause for Voice in case of P-CSCF restoration LG Electronics, SK Telecom, KT Corp., LG Uplus Rel-17 Noted Myungjune (LGE) provides r01.
Steve (Huawei) As per the discussion in S2-2105961, this should be noted.
Saso (Intel) thinks this is not a FASMO.
Myungjune (LGE) provides r02.
==== 8.X, 9.X Revisions Deadline ====
Ouyang(Huawei) comments.
Myungjune (LGE) replies to Ouyang (Huawei).
xiaowan (vivo) object to the CR
Myungjune (LGE) replies to Xiaowan (vivo)
Myungjune (LGE) clarifies to Ouyang (Huawei)
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105963 CR Approval 23.501 CR3117 (Rel-17, 'F'): Paging Cause for Voice in case of P-CSCF restoration LG Electronics, SK Telecom, KT Corp., LG Uplus Rel-17 Noted Myungjune (LGE) provides r01.
Steve (Huawei) As per the discussion in S2-2105961, this should be noted.
Saso (Intel) thinks this is not a FASMO.
Myungjune (LGE) provides r02.
==== 8.X, 9.X Revisions Deadline ====
xiaowan (vivo) objects to the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105964 CR Approval 23.502 CR3020 (Rel-17, 'F'): Paging Cause for Voice in case of P-CSCF restoration LG Electronics, SK Telecom, KT Corp., LG Uplus Rel-17 Noted Steve (Huawei) As per the discussion in S2-2105961, this should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 - - - Reject Paging - - Docs:=1 -
8.10 S2-2105949 CR Approval 23.502 CR3017 (Rel-17, 'F'): Correction of Reject Paging Indication in Service Request Sony Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 - - - Connection Release - - Docs:=2 -
8.10 S2-2105808 CR Approval 23.502 CR2988 (Rel-17, 'F'): Connection Release procedure correction Ericsson Rel-17 r02 agreed. Revised to S2-2106789 Lalith(Samsung) provides r01
alessio(Nokia) remarks clause 4.2.2.2.2 no longer has any change in this CR and should be removed from CR.
Lalith(Samsung) replies to alessio(Nokia)
Qian (Ericsson) comments and is ok with r01
Steve (Huawei) provides r02, very minor terminology alignment.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106789 CR Approval 23.502 CR2988R1 (Rel-17, 'F'): Connection Release procedure correction Ericsson Rel-17 Revision of S2-2105808r02. Approved Agreed
8.10 - - - Paging Restrictions - - Docs:=5 -
8.10 S2-2105965 CR Approval 23.401 CR3652 (Rel-17, 'F'): Clarification on removing condition of paging restriction and IMSI Offset LG Electronics Rel-17 r01 agreed. Revised to S2-2106790 Lalith (Samsung) comments
Myungjune (LGE) responses to Lalith (Samsung)
Saso (Intel) prefers the current handling without the proposed optimization.
Lalith(Samsung) replies to Myungjune (LGE)
Steve (Huawei) does not see the need for this change.
Myungjune (LGE) provides r01.
Lalith (Samsung) is OK with r01.
Steve (Huawei) comments
Myungjune (LGE) replies to Steve (Huawei).
Lalith(Samsung) comments.
Alessio (Nokia) is ok with r01 but wonders whether at all we were assuming the Offset is included in PTAU... I thought it was only in Mobility/Initial...
Jianning (Xiaomi) is ok with r01.
==== 8.X, 9.X Revisions Deadline ====
Alessio(nokia) reports CT1 was discussing this week removal of the option to send IMSI OFFSET in PTAU
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106790 CR Approval 23.401 CR3652R1 (Rel-17, 'F'): Clarification on removing condition of paging restriction and IMSI Offset LG Electronics Rel-17 Revision of S2-2105965r01. Approved Agreed
8.10 S2-2105966 CR Approval 23.501 CR3118 (Rel-17, 'F'): Clarification on removing condition of paging restriction LG Electronics Rel-17 Noted Lalith (Samsung) proposes to note this CR
Myungjune (LGE) is ok to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2105967 CR Approval 23.502 CR3021 (Rel-17, 'F'): Clarification on removing condition of paging restriction LG Electronics Rel-17 Noted Lalith (Samsung) proposes to note this CR.
Myungjune (LGE) is ok to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2106477 CR Approval 23.501 CR3229 (Rel-17, 'F'): Deleting PRs in non allowed area Samsung Rel-17 CC#4: Postponed Qian (Ericsson) asks questions for clarification
Myungjune (LGE) comments.
Lalith(Samsung) replies to Myungjune (LGE) and Qian (Ericsson)
Juan Zhang (Qualcomm) provides comments
Myungjune (LGE) replies.
Qian Chen (Ericsson) comments.
Lalith(Samsung) replies to Qian Chen (Ericsson)
Lalith(Samsung) replies to Juan Zhang (Qualcomm)
Lalith(Samsung) replie to Myungjune (LGE)
Qian Chen (Ericsson) provides further comments.
Juan Zhang (Qualcomm) replies to Lalith (Samsung)
Lalith(Samsung) replies to Myungjune (LGE) .
Myungjune (LGE) replies to Lalith (Samsung) .
alessio(Nokia) asks a question
Lalith(Samsung) replies to alessio(Nokia)
alessio(Nokia) proposes to postpone the topic to the next meeting as the topic is new and deserved to be dealt with properly
alessio(Nokia) replies
alessio(Nokia) has no problem to allow this CR to progress if UE vendors are ok with it.
Steve (Huawei) asks a question
Lalith(Samsung) replies to Steve (Huawei)
Juan Zhang (Qualcomm) provides to Lalith
Steve (Huawei) comments
Jianning (Xiaomi) provides comment
Lalith(Samsung) replies to Jianning (Xiaomi)
Jianning (Xiaomi) provides further comment
Saso (Intel) comments
Lalith(Samsung) replies to Saso (Intel)
Alessio(Nokia) confirms that if UE vendors or other players are happy to proceed at this meeting we are also happy. we are also equally happy to postpone.
==== 8.X, 9.X Revisions Deadline ====
Jianning (Xiaomi) prefer to postpone this for next meeting, as Lalith (Samsung) brings a good issue that we need furhter work on this.
Lalith(Samsung) replies to Jianning (Xiaomi).
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 - - - Terminology alignment - - Docs:=9 -
8.10 S2-2106298 CR Approval 23.501 CR3192 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2106791, merging S2-2106309 Lars (Sony) provides r01
Steve (Huawei) comments, provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106791 CR Approval 23.501 CR3192R1 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 Revision of S2-2106298r02, merging S2-2106309. Approved Agreed
8.10 S2-2106308 CR Approval 23.501 CR3196 (Rel-17, 'F'): Terminology correction Xiaomi Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2106309 CR Approval 23.501 CR3197 (Rel-17, 'D'): Editorial monification for Terminology alignment Xiaomi Rel-17 Merged into S2-2106791 Steve (Huawei) suggests merging with S2-2106298
Jianning (Xiaomi) is ok to merge into 6298
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2106310 CR Approval 23.401 CR3654 (Rel-17, 'F'): Terminologies Correction Xiaomi Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2106311 CR Approval 23.401 CR3655 (Rel-17, 'D'): Editorial monification for Terminology alignment Xiaomi Rel-17 LATE DOC: Rx 11/08, 05:50. Merged into S2-2106792 Steve (Huawei) suggests merging with S2-2105678
Jianning (Xiaomi) is ok to merge into 5678
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2105677 CR Approval 23.502 CR2953 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2105678 CR Approval 23.401 CR3649 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106792, merging S2-2106311 Lars (Sony) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2106792 CR Approval 23.401 CR3649R1 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 Revision of S2-2105678r01, merging S2-2106311. Approved Agreed
8.10 - - - Other - - Docs:=3 -
8.10 S2-2105824 CR Approval 23.501 CR3094 (Rel-17, 'F'): MUSIM support for SNPN access mode Qualcomm Incorporated Rel-17 Noted Saso (Intel) provides r01.
Guillaume (MediaTek) supports the proposal (and r01).
xiaowan (vivo) provides r02
Ouyang(Huawei) requests clarification.
Malla (NTT DOCOMO) request for clarification.
Saso (Intel) replies to Ouyang.
Saso (Intel) replies to Malla (NTT DOCOMO).
Curt (Charter) supports Saso (Intel) that MUSIM features can be applied to UEs with credentials stored on the ME as well.
Ouyang(Huawei) comments
Curt (Charter) comments
Malla (NTT DOCOMO) replies to Saso (Intel).
Lalith(Samsung) provides r03
Josep (DT) objects to r02, r03, provides r04. Asks what about the PEI for ME credentials
Saso (Intel) proposes r05 and co-signs.
Myungjune (LGE) comments.
Ouyang(Huawei) provides r06, considering a NOTE is sufficient
Juan Zhang (Qualcomm) supports r05 and objects r06
Saso (Intel) provides r07
Juan Zhang (Qualcomm) is OK with r07.
Steve (Huawei) provides r08.
Guillaume (MediaTek) provides r09
Guillaume (MediaTek Inc.) provides r10
Alessio(Nokia) provides r11 attempting to simplify the text.
Jianning (Xiaomi) provides comment
Saso (Intel) is fine with both r10 and r11
Curt (Charter) - r12 is just adding Charter as supporting company on top of R11.
Guillaume (MediaTek Inc.): r11 is good
Steve (Huawei) provides r13
Lalith(Samsung) comments on r13 and suggest to move forward with r12
Juan Zhang (Qualcomm) prefers r12.
Steve (Huawei) comments
Lalith(Samsung) provides r14
Alessio(Nokia) is ok with r14
Steve (Huawei) comments, provides r15
alessio(Nokia) is ok with r15.
Lalith(Samsung) is OK with r15
Guillaume (MediaTek) is OK with r15.
Juan Zhang (Qualcomm) is OK with r15.
Saso (Intel) is OK with r15.
==== 8.X, 9.X Revisions Deadline ====
Xiaowan (vivo) comment r15, and can accept r15 with removal of the change'A Multi-USIM UE shall use a separate PEI for each network subscription (i.e. SUPI associated with a PLMN or SNPN) when it registers with the network. '
Ouyang(Huawei) support the revoke the change back the PEI for each USIM.
Provide r16 in the Draft folder.
Saso (Intel) supports agreeing r16 in this meeting.
Jianning (Xiaomi) provide the r17, to propose the focusing on SNPN UE with USIM case, without impact on MUSIM features. also solve the concern from Ouyang (Huawei) and Xiaowan (vivo)
Yang (OPPO) prefer to agree r17 and can live with r16. And object r15 as the reason mentioned by vivo.
Juan Zhang (Qualcomm) is fine with r16, but object r17.
Saso (Intel) objects r17
Dieter (Deutsche Telekom) objects to all revisions.
Juan Zhang (Qualcomm) replies to Jianning (xiaomi)
Saso (Intel) finds it unfair for someone who did not comment at all before revision deadline to object after revision deadline.
Dieter (Deutsche Telekom) that is the problem of this e-meeting mode.
Jianning (Xiaomi) replies to Juan (Qualcomm)
Ouyang(Huawei) considers the baby step 'SNPN UE with USIM case' is the middle ground so far? Suggests Dieter to double check r17, which mandates physical SIM.
Jianning (Xiaomi) provides r18 with resolving Saso (Intel)'s concens.
Saso (Intel) does not think r18 is any better. Proposes to agree r16 and add a note in the official meeting report that the case of PEI when the credential is stored in the ME needs to be further clarified.
Saso (Intel) replies to Dieter (Deutsche Telekom).
Juan Zhang (Qualcomm) supports Saso's comments and objects r17, r18, we can support r16.
Alessio(Nokia) can live with r16 but not r17.
==== 8.X, 9.X Final Deadline ====
Jianning (Xiaomi) replies to Saso(Intel)
Noted
8.10 S2-2106474 CR Approval 23.501 CR3228 (Rel-17, 'F'): Clarification related to access type Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.10 S2-2106476 CR Approval 23.502 CR3111 (Rel-17, 'F'): Clarificaiton on registration procedure and access type Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=44 -
8.11 - - - UE location aspects in NTN - - Docs:=26 -
8.11 S2-2105270 LS In Action LS from RAN WG2: New LS on UE location aspects in NTN RAN WG2 (R2-2106543) Rel-17 Responses drafted in S2-2105619 and S2-2106071. Noted Hucheng (CATT) comments.
Hannu (Nokia) supports the way forward identified in this LS in from RAN2, assuming it is acceptable for SA3.
Jean Yves (Nokia) supports also the way forward identified in this LS in from RAN2.
Jean Yves (Thales) correcting the company name for the notes...
Hucheng(CATT) proposes to ask RAN2/3 to clarify how the solution works before sending a confirmation.
Stephen (Qualcomm) comments that the LS aligns with previous SA2 agreements and can be noted
Hucheng (CATT) asks Stephen (Qualcomm) how to solve the identified issue if not sending a LS to RAN WGs.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) points out to Jean Yves that Nokia is a correct company name also in the notes
Hannu (Nokia) comments that 2 km accuracy is sufficient for SA2 requirement. We can trust RAN can achieve it as that's what they promised in their LS.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105283 LS In Action LS from RAN WG3: Reply LS on UE location aspects in NTN RAN WG3 (R3-212917) Responses drafted in S2-2105969 and S2-2106524. Final response in S2-2106651
==== 8.X, 9.X Final Deadline ====
Replied to
8.11 S2-2105295 LS In Action LS from SA WG3: Reply LS on UE location aspects in NTN SA WG3 (S3-212306) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2105246 LS In Information LS from SA WG1: Reply LS on selecting a PLMN not allowed in the country where a UE is physically located SA WG1 (S1-211503) Rel-17 Revision of postponed S2-2105096 from S2-145E. Noted DongYeon (Samsung) proposes to NOTE: no action is required from SA2.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105619 LS OUT Approval [DRAFT] Reply to New LS on UE location aspects in NTN THALES Rel-17 Response to S2-2105270. Noted Jean Yves (Thales) provides r01 introducing Q2 from S2-2106071
Stefan (Ericsson) comments
Jean Yves (Thales) responds to Stefan and provides r02
Hucheng(CATT) provides r03.
Jean Yves(Thales) comments on r03.
Hucheng (CATT) clarifies to Thales.
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) supports r03.
Stephen (Qualcomm) can agree r02 but not r03
Stefan (Ericsson) OK with r02 but cannot accept r03
Hucheng can only accept r03 since it is not clear how a UE location with 2km radius accuracy is mapped to an accurate CGI.
Hannu (Nokia) objects against r03. Can only agree r02.
==== 8.X, 9.X Final Deadline ====
Jean Yves (Thales) provides draft r04 for possible discussion in CC#4
Hannu (Nokia) thanks Jean Yves for seeking compromise, but can't accept r04.
Jean Yves (Thales) responds to Hannu.
Stefan (Ericsson) also cannot agree on r04, and propose the postpone the incoming LS
DongYeon (Samsung) is okay with r02.
Hannu (Nokia) supports r02 if it is brought up in today's CC. Can't agree any other version.
Noted
8.11 S2-2106071 LS OUT Approval [DRAFT] Reply LS on UE location aspects in NTN CATT Rel-17 Response to S2-2105270. Merged with S2-2105619 (noted). Noted Stephen (Qualcomm) comments that the LS needs to be revised and trimmed down
Hucheng(CATT) clarifies to Qualcomm.
Jean Yves (Thales) comments and proposes to add Q2 to S2-2105619
Hucheng (CATT) replies to the comment from Thales and proposes to send this LS to ask for more information.
Jean Yves (Thales) replies to the comment from CATT and maintain its proposal.
Stefan (Ericsson) provides comments
Hannu (Nokia) proposes to take 5619 as the template for LS out instead of this.
Andy (Samsung, VC) asks CATT if it is OK to mark 6071 as merged into 5619.
Hucheng (CATT) replies to comments from Ericsson and Thales.
Hucheng (CATT) replies to VC and asks for more discussion before making a decision.
Stefan (Ericsson) comments and suggests to focus on replying to the RAN3 LS
Yuxin (Xiaomi) cares the same issues
Hucheng (CATT) comments and thinks it is better to have different LS threads.
Hucheng (CATT) indicates this document can be merged into 5619.
Jean Yves (Thales) indicates that Q2 is already merged into 5619.
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) comments that the LS was not corrected and trimmed down as we proposed and thus does not seem useful
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105969 LS OUT Approval [DRAFT] Reply LS on UE location aspects in NTN Xiaomi Rel-17 Response to S2-2105283. Merged into S2-2106651 Stephen (Qualcomm) comments that the LS might be merged into another LS such as S2-2106524
Yuxin (Xiaomi) agrees to be merged into S2-2106524 and supports draft LS S2-2106524 as the base
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.11 S2-2106070 DISCUSSION Decision Discussion on Location aspects for NTN. CATT Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2106524 LS OUT Approval [DRAFT] LS Response to Reply LS on UE location aspects in NTN Qualcomm Incorporated Rel-17 Response to S2-2105283. r05 agreed. Revised to S2-2106651, merging S2-2105969 Yuxin (Xiaomi) provides r01
Stefan (Ericsson) comments and provides r02
Wanqiang (Huawei) comments.
Jean Yves (Thales) comments and ask questions
Stefan (Ericsson) replies to Jean Yves
Yuxin (Xiaomi) comments and provides r03
Stephen (Qualcomm) provides an r04
Stefan (Ericsson) provides r05
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) comments on Option C.
Stephen (Qualcomm) can agree the r05
Jean Yves (Thales) is ok with r05
Hucheng (CATT) is ok with either r04 or r05.
Yuxin (Xiaomi) is ok with r05
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2106651 LS OUT Approval LS Response to Reply LS on UE location aspects in NTN SA WG2 Rel-17 Revision of S2-2106524r05, merging S2-2105969. Approved Approved
8.11 S2-2106519 DISCUSSION Agreement Discussion of Tracking Area Support with Hard and Soft TAC Update. Qualcomm Incorporated Rel-17 Noted DongYeon (Samsung) asks a question.
Stefan (Ericsson) provides comments
Stephen (Qualcomm) provides responses
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2106521 CR Approval 23.501 CR2748R2 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2104777 from S2-145E. r01 agreed. Revised to S2-2106652, merging S2-2105531 Stefan (Ericsson) provides r01
Stephen (Qualcomm) comments on the r01
Stefan (Ericsson) replies to Stephen
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) prefers r00 but can accept r01
Stefan (Ericsson) can only accept r01, not r00
Leo (Deutsche Telekom) can accept r01, but cover sheet needs to be updated
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2106652 CR Approval 23.501 CR2748R3 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 Revision of S2-2106521r01, merging S2-2105531. Approved Agreed
8.11 S2-2106522 CR Approval 23.502 CR2875R1 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2104774 from S2-145E. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.11 S2-2105251 LS In Action LS from CT WG1: LS reply on multiple TACs per PLMN CT WG1 (C1-213965) Rel-17 Response drafted in S2-2105800. Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2105375 LS In Action LS from RAN WG2: Response LS on Multiple TACs per PLMN RAN WG2 (R2-2108888) Rel-17 Postponed Hannu (Nokia) proposes to postpone this LS. There is SA2 (and CT1) action but we haven't got any CR to carry out our task.
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) proposes to postpone this LS.
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2105800 LS OUT Approval [DRAFT] Reply LS on multiple TACs per PLMN Ericsson Rel-17 Response to S2-2105251. Noted Stephen (Qualcomm) comments that more discussion is needed to agree a solution for multiple TACs per PLMN before agreeing an associated LS and CR(s)
Stefan (Ericsson) replies
Stephen (Qualcomm) replies to Stefan (Ericsson)
Hannu (Nokia) provides r01
Hannu (Nokia) replies to Stephen and Stefan
Stephen (Qualcomm) replies to Hannu (Nokia)
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to note this draft reply LS
Stefan (Ericsson) agress to note/postpone
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105376 LS In Information LS from CT WG1: Indication of country of UE location and its use in PLMN selection CT WG1 (C1-214778) Rel-17 Noted Hannu (Nokia) proposes to note the LS as there is no SA2 action.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105530 DISCUSSION Approval TA handling for moving cells . Ericsson Rel-17 Noted Stephen (Qualcomm) provides comments
Stefan (Ericsson) replies to Stephen
Stephen (Qualcomm) agrees with Stefan (Ericsson) to aim for resolution in October
==== 8.X, 9.X Revisions Deadline ====
Stefan (Ericsson) provides follow-up questions to Stephen
Stephen (Qualcomm) provides a further response to Stefan (Ericsson)
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105531 CR Approval 23.501 CR3031 (Rel-17, 'C'): TA handling in satellite access Ericsson Rel-17 Merged into S2-2106652 Leo (Deutsche Telekom) provides comments
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to merge this CR into S2-2106521
Stefan (Ericsson) agress to merge in 6521
==== 8.X, 9.X Final Deadline ====
Merged
8.11 S2-2105976 DISCUSSION Approval Discussion of Soft TAC issues to support NR Satellite Access. OPPO Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105981 CR Approval 23.501 CR3122 (Rel-17, 'C'): Verification of UE location to support multiple TACs for 5G Satellite Access OPPO Rel-17 Postponed Stefan (Ericsson) comments
Stephen (Qualcomm) agrees that the CR has some problems
Jingran (OPPO) replies to Stefan (Ericsson) and Stephen (Qualcomm)
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone the CR
Stefan (Ericsson) also proposes to postpone the CR
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2106517 CR Approval 23.501 CR3233 (Rel-17, 'F'): Clarification of Initiation of UE Location for country verification for NR satellite access Qualcomm Incorporated Rel-17 Noted. Covered by (noted) S2-2105528 Stephen (Qualcomm) proposes to merge this into S2-2105528
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) sees 6517 has been merged to 5528, but asks if it is agreed.
Hannu (Nokia) confirms DongYeon's assumption that 6517 is merged to 5528 and it's too late to return to this CR as the discussion has moved to 5528.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2106518 CR Approval 23.502 CR3120 (Rel-17, 'F'): Clarification of Initiation of UE Location for country verification for NR satellite access Qualcomm Incorporated Rel-17 Noted Stephen (Qualcomm) provides an r01
Yuxin (Xiaomi) provides r02
Stefan (Ericsson) comments
Stephen (Qualcomm) provides an r03
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) supports r03
Yuxin (Xiaomi) proposes to note the CR, for same reasons as S2-2105528, S2-2105529.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105528 CR Approval 23.501 CR3030 (Rel-17, 'F'): UE location verification handling Ericsson Rel-17 Noted Stephen (Qualcomm) provides an r01 which merges in changes from S2-2106517 and S2-2106518
Chris (Vodafone) provides r02.
Yuxin (Xiaomi) asks for clarification
Stephen (Qualcomm) answers to Yuxin (Xiaomi)
DongYeon (Samsung) provides comment, and remarks that r01 is not the exact merge of 6517 and 5528.
DongYeon (Samsung) corrects the comment, r01 is merge 6517&6518&5528.
Yuxin (Xiaomi) provides r03
Chris (Vodafone) requests that r03 is updated to include the important change made in r02.
Yuxin (Xiaomi) withdraws r03 and provides r04 to include the change made in r02.
Jingran(OPPO)provides comment.
Jean Yves(Thales) provides comment.
Hannu (Nokia) replies to Jingran.
Hannu (Nokia) supports the CR and provides r05
Hannu (Nokia) provides r06
Stephen (Qualcomm) comments that the r06 can be acceptable after 2 apparent errors are resolved
Stefan (Ericsson) replies to Stephen and Hannu
Yuxin(Xiao) provides comment.
Yuxin(Xiaomi) provides comment.
Wanqiang (Huawei) comments and proposes to remove the note 2
Stefan (Ericsson) replies to Chris
Chris (Vodafone) provides some comments
Stephen (Qualcomm) provides an r07 to resolve the comments
Wanqiang (Huawei) not convinced to clearly mention the 901 case. And propose r08
Stefan (Ericsson) provides r09 but prefers r08
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) comments that r08 is acceptable but not r09
Hucheng(CATT) comments, and thinks r08 is OK at present.
Yuxin (Xiaomi) prefers r09
Jingran (OPPO) prefers r09
DongYeon (Samsung) supports r09, can accept r00, objects to any other revisions.
Jean Yves (Thales) proposes to note this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105529 CR Approval 23.502 CR2930 (Rel-17, 'F'): UE location verification handling Ericsson Rel-17 Noted Stephen (Qualcomm) provides an r01 which merges in changes from S2-2106518
Hannu (Nokia) provides r02 to update the cover page on 23.502 requirements moving to 23.501 and to so-sign.
Stefan (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) prefers r02 but can live with r03
Yuxin (Xiaomi) prefers r03
Jingran (OPPO) prefers r03
DongYeon (Samsung) supports r03, objects to r02 and r01.
Jean Yves (Thales) proposes to note the CR, for same reasons as S2-2105528.
==== 8.X, 9.X Final Deadline ====
Noted
8.11 - - - Other - - Docs:=18 -
8.11 S2-2105264 LS In Action LS from RAN WG1: Reply LS on PDB for new 5QI RAN WG1 (R1-2106331) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2105268 LS In Action LS from RAN WG2: Reply LS on PDB for new 5QI RAN WG2 (R2-2106533) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2105527 CR Approval 23.501 CR3029 (Rel-17, 'C'): PDB value for 5QI 10 Ericsson Rel-17 r02 agreed. Revised to S2-2106653 Haris(Qualcomm) proposes r01
Mirko (Huawei) asks whether we can move up the 5QI 10 line to restore the order in the table.
Stefan (Ericsson) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Jean Yves (Thales) is ok with r02
Revised
8.11 S2-2106653 CR Approval 23.501 CR3029R1 (Rel-17, 'C'): PDB value for 5QI 10 Ericsson Rel-17 Revision of S2-2105527r02. Approved Agreed
8.11 S2-2105224 LS In Action LS from RAN WG2: LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G RAN WG2 (R2-2008229) Revision of postponed S2-2103716 from S2-145E. Noted Stefan (Ericsson) proposes to note the LS
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105276 LS In Action LS from RAN WG3: Reply LS to LS on IoT-NTN basic architecture RAN WG3 (R3-212806) Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105282 LS In Action LS from RAN WG3: Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G RAN WG3 (R3-212916) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105675 CR Approval 23.503 CR0618 (Rel-17, 'F'): Clarification on SMF determines satellite backhaul and PCF reports satellite backhaul category change event Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106654, merging S2-2106341 Stefan (Ericsson) provides comments
Guanglei (Huawei) replies and provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2106654 CR Approval 23.503 CR0618R1 (Rel-17, 'F'): Clarification on SMF determines satellite backhaul and PCF reports satellite backhaul category change event Huawei, HiSilicon Rel-17 Revision of S2-2105675r01, merging S2-2106341. Approved Agreed
8.11 S2-2106341 CR Approval 23.503 CR0647 (Rel-17, 'F'): SMF subscribes Satellite backhaul category backhaul change from AMF Huawei, Hisilicon Rel-17 Merged into S2-2106654 Yuxin (Xiaomi): proposes to merge into S2-2105675 or be discussed together
Guanglei (Huawei) agrees to merge into 5675.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.11 S2-2106342 CR Approval 23.501 CR3199 (Rel-17, 'F'): SMF subscribes Satellite backhaul category backhaul change from AMF Huawei, Hisilicon Rel-17 r02 agreed. Revised to S2-2106655 Stefan (Ericsson) provides comments
Hannu (Nokia) asks further question from Stefan
Stefan (Ericsson) replies to Hannu
Guanglei (Huawei) replies and provides r01.
Stefan (Ericsson) provides r02
Guanglei (Huawei) is fine with r02.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) supports r02 and thanks Stefan for explanation.
==== 8.X, 9.X Final Deadline ====
Jean Yves (Thales) is ok with r02.
Revised
8.11 S2-2106655 CR Approval 23.501 CR3199R1 (Rel-17, 'F'): SMF subscribes Satellite backhaul category backhaul change from AMF Huawei, HiSilicon Rel-17 Revision of S2-2106342r02. Approved Agreed
8.11 S2-2105884 CR Approval 23.502 CR3005 (Rel-17, 'B'): PDU session establishment for NR satellite access ASUSTeK Rel-17 Noted DongYeon (Samsung) asks questions for clarification.
Josep (DT) comments that such a request should best come from RAN (RAN1, I guess?) instead of SA2 deciding it.
Yuxin (Xiaomi) provides comments
Lider (ASUSTeK) replies to DongYeon (Samsung) and Josep (DT).
Lider (ASUSTeK) replies to Yuxin (Xiaomi).
Lider (ASUSTeK) replies to Dan (IPLOOK).
Dan (IPLOOK) replies to Lider (ASUSTeK) .
Yuxin (Xiaomi) replies to Lider (ASUSTeK)
DongYeon (Samsung) provides comment.
Lider (ASUSTeK) replies to DongYeon (Samsung).
Jingran (OPPO) provides comments.
Lider (ASUSTeK) replies to Jingran (OPPO).
Jingran (OPPO) replies to Lider (ASUSTeK).
Patrice (Huawei) comments, from a network slicing perspective. The CR is not needed.
Hannu (Nokia) shares the view of Patrice that this CR should be noted.
Lider (ASUSTeK) follows majority's view and provides an r01.
Haris (Qualcomm) comments on r00 and r01 and proposes to note
Stefan (Ericsson) expresses similar concerns
Lider (ASUSTeK) provides an r02.
Stefan (Ericsson) comments that CR does not seem to be needed
Patrice (Huawei) agrees that r02 is not needed.
==== 8.X, 9.X Revisions Deadline ====
Lider (ASUSTeK) thinks that the change really addresses the issue and does not cause any other technical issue.
Patrice (Huawei) comments that all aspects that this CR intends to solve are already covered by 23.501 §5.15, therefore the CR is not needed.
Hannu (Nokia) still proposes to note the CR in all revisions.
Stefan (Ericsson) objects to any revision of this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105970 CR Approval 23.501 CR3119 (Rel-17, 'D'): Remove Editor's note in clause 5.4.11.1 in TS 23.501 Xiaomi Rel-17 CC#4: r01 + changes agreed. Revised to S2-2106676. Stefan (Ericsson) provides r01
Yuxin (Xiaomi) agrees to the change
Hannu (Nokia) supports r01
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) objects to all revisions of this CR
Yuxin(Xiaomi) requests to mark it for a CC#4 5GSAT_ARCH topic
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2106676 CR Approval 23.501 CR3119R1 (Rel-17, 'F'): Remove Editor's note in clause 5.4.11.1 in TS 23.501 Xiaomi Rel-17 Revision of S2-2105970r01 + changes. Approved Agreed
8.11 S2-2105971 DISCUSSION Approval Discussion of Registration Update under NR Satellite Access. Xiaomi Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2105972 CR Approval 23.502 CR3022 (Rel-17, 'C'): Registration Update under NR Satellite Access Xiaomi Rel-17 Postponed Stefan (Ericsson) comments that CR may need to be postponed
==== 8.X, 9.X Revisions Deadline ====
Yuxin (Xiaomi) agrees to postpone this CR
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2106215 CR Approval 23.273 CR0188 (Rel-17, 'F'): Satellite RAT Type in LMF selection Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Åke (Ericsson) This CR is identical to CR 0192 in S2-2106423 submitted to AI 8.14
Sherry (Xiaomi) comments.
Ming (CATT) comments.
Åke (Ericsson) Asks if any of CRs is planned to be withdrawn.
Hannu (Nokia) withdraws 6215, proposes to discuss the same proposal in 6423 in AI 8.14 and answers to Ming.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Withdrawn
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=7 -
8.12 S2-2105894 DISCUSSION Discussion Discussion about PC5 DRX configuration for unicast. LG Electronics, Deutsche Telekom Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.12 S2-2105577 CR Approval 23.287 CR0161 (Rel-17, 'B'): PC5 DRX configuration for broadcast and groupcast LG Electronics, Deutsche Telekom, ZTE, Intel, Lenovo, Motorola Mobility, vivo, Tencent Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.12 S2-2105578 CR Approval 23.287 CR0162 (Rel-17, 'F'): EN resolution about determination of the PC5 DRX parameter values LG Electronics, Deutsche Telekom, ZTE, Intel, Lenovo, Motorola Mobility, vivo, Tencent Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.12 S2-2105895 CR Approval 23.287 CR0163 (Rel-17, 'F'): Removal of EN about PC5 DRX configuration for unicast LG Electronics, Deutsche Telekom Rel-17 r01 agreed. Revised to S2-2106656 Shabnam (Ericsson) comments that since we have not received any input from RAN2, shall we postpone this CR?
LaeYoung (LGE) replies to Shabnam (Ericsson) and thinks we can wait for RAN2 decision because RAN2 will have a discussion on this topic during their CC on Tue 14:25-15:45 UTC.
LaeYoung (LGE) provides r01 with just coversheet update.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.12 S2-2106656 CR Approval 23.287 CR0163R1 (Rel-17, 'F'): Removal of EN about PC5 DRX configuration for unicast LG Electronics, Deutsche Telekom Rel-17 Revision of S2-2105895r01. Approved Agreed
8.12 S2-2105896 CR Approval 23.287 CR0164 (Rel-17, 'B'): PC5 DRX configuration for unicast LG Electronics, Deutsche Telekom Rel-17 Noted Shabnam (Ericsson) comments that since we have not received any input from RAN2, shall we postpone this CR?
LaeYoung (LGE) replies to Shabnam (Ericsson) and thinks we can wait for RAN2 decision because RAN2 will have a discussion on this topic during their CC on Tue 14:25-15:45 UTC.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.12 S2-2106139 DISCUSSION Discussion Discussion about transmission schedule info to V2X application layer. LG Electronics Rel-17 Noted Cai Simon (Nokia) provides comments
LaeYoung (LGE) responds to Cai Simon (Nokia).
Cai Simon (Nokia) provides further comments
LaeYoung (LGE) replies to Cai Simon (Nokia).
Hong (Qualcomm) comments.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) replies to Hong (Qualcomm).
==== 8.X, 9.X Final Deadline ====
Noted
8.13 - - - 5G System Enhancement for Advanced Interactive Services (5G_AIS) - - Docs:=1 -
8.13 S2-2105261 LS In Action LS from RAN WG1: LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) RAN WG1 (R1-2106149) Rel-17 Noted Lei (Tencent) propose to note this LS, because in last SA2 e-meeting the content of the LS has already been taken into consideration by SA2.
Haiyang (Huawei) support to note this LS as no action is needed.
Devaki (Nokia) supports noting the LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.14 - - - Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) - - Docs:=21 -
8.14 - - - General - - Docs:=3 -
8.14 S2-2105262 LS In Action LS from RAN WG1: Reply LS to SA WG2 on Scheduling Location in Advance RAN WG1 (R1-2106312) Rel-17 Response drafted in S2-2106319. Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2106319 LS OUT Approval [DRAFT] LS response on scheduled location time Huawei Rel-17 Response to S2-2105262. Noted Stephen (Qualcomm) comments that this seems an LS response to a future LS not yet sent by RAN2
Runze (Huawei) suggest to wait until next Monday for the potential RAN2 feedback.
Åke (Ericsson) Object to any revision of LS
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to note the Response LS
==== 8.X, 9.X Final Deadline ====
Noted
8.14 S2-2105263 LS In Information LS from RAN WG1: LS on Positioning Reference Units (PRUs) for enhancing positioning performance RAN WG1 (R1-2106326) Rel-17 Postponed Runze (Huawei) proposes to postpone the LS to the next meeting.
Leo (Deutsche Telekom) proposes to note the LS
Yunjing (CATT) proposes to keep the LS open.
Cai Simon (Nokia) agrees with Runze (Huawei)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 - - - Scheduled Location Time - - Docs:=6 -
8.14 S2-2105464 CR Approval 23.273 CR0147R3 (Rel-17, 'C'): Add time of position determination to Deferred MT-LR periodic Ericsson Rel-17 Revision of (Postponed) S2-2103801 from S2-145E. r02 agreed. Revised to S2-2106657 Yunjing (CATT) suggests to merge this CR into S2-2106183.
Leo (Deutsche Telekom) objects to r00 of this CR and provides comments.
Åke (Ericsson) Provides r01 and comments
Yunjing (CATT) provides r02.
Leo (Deutsche Telekom) is fine with r02.
Åke (Ericsson) Support r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106657 CR Approval 23.273 CR0147R4 (Rel-17, 'F'): Add time of position determination to Deferred MT-LR periodic Ericsson Rel-17 Revision of S2-2105464r02. Approved Agreed
8.14 S2-2106183 CR Approval 23.273 CR0187 (Rel-17, 'B'): Introduction of the Scheduled Location Time CATT Rel-17 r02 agreed. Revised to S2-2106658 Leo (Deutsche Telekom) provides comments and r01.
Cai Simon (Nokia) asks questions to both r01 and original tdoc
Stephen (Qualcomm) provides comments and corrects a formatting error in the Subject Line
Yunjing (CATT) replies to Stephen and provides r02.
Stephen (Qualcomm) can accept the r02
Yunjing (CATT) is ok to move on based on S2-2102047 in next SA2 meeting.
Åke (Ericsson) can accept r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106658 CR Approval 23.273 CR0187R1 (Rel-17, 'B'): Introduction of the Scheduled Location Time CATT Rel-17 Revision of S2-2106183r02. Approved Agreed
8.14 S2-2106184 CR Approval 23.502 CR3052 (Rel-17, 'B'): Introduce the Scheduled location time CATT Rel-17 Noted Åke (Ericsson) Objects to any revision of CR
==== 8.X, 9.X Revisions Deadline ====
Yunjing (CATT) is fine to note the CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.14 S2-2106320 CR Approval 23.273 CR0189 (Rel-17, 'B'): Addition of a Scheduled Location Time Huawei Rel-17 Postponed Yunjing (CATT) suggests to merge this CR into S2-2106183.
Runze (Huawei) proposes the updated version of 6183 should take into account the contents of 6320.
Leo (Deutsche Telekom) also proposes to merge S2-2106320 into S2-2106183.
Stephen (Qualcomm) provides comments
Åke (Ericsson) Objects to any revision of CR
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone the CR
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 - - - Local Co-ordinates - - Docs:=2 -
8.14 S2-2106180 CR Approval 23.032 CR0019 (Rel-17, 'F'): Add message formats for Local 2D point with uncertainty ellipse and Local 3D point with uncertainty ellipsoid CATT Rel-17 r01 agreed. Revised to S2-2106620 Stephen (Qualcomm) comments that the CR may not be needed
Åke (Ericsson) Questions need of CR
Yunjing (CATT) replies to comments and provides r01.
Stephen (Qualcomm) can agree the r01
Åke (Ericsson) Support r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106620 CR Approval 23.032 CR0019R1 (Rel-17, 'F'): Add message formats for Local 2D point with uncertainty ellipse and Local 3D point with uncertainty ellipsoid CATT Rel-17 Revision of S2-2106180r01. Approved Agreed
8.14 - - - UE Positioning Capability - - Docs:=2 -
8.14 S2-2106181 CR Approval 23.273 CR0185 (Rel-17, 'F'): Update LMF function and service operation CATT Rel-17 r01 agreed. Revised to S2-2106621 Åke (Ericsson) provides r01
Yunjing(CATT) is ok with r01.
Runze (Huawei) supports r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106621 CR Approval 23.273 CR0185R1 (Rel-17, 'F'): Update LMF function and service operation CATT, Ericsson Rel-17 Revision of S2-2106181r01. Approved Agreed
8.14 - - - Multiple QoS - - Docs:=2 -
8.14 S2-2106185 CR Approval 23.502 CR3053 (Rel-17, 'F'): Update AMF location service operation to add the multiple QoS class CATT Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.14 S2-2106321 CR Approval 23.273 CR0190 (Rel-17, 'C'): Solution update for multiple LCS QoS Huawei Rel-17 Noted Stephen (Qualcomm) comments that the CR does not seem needed
Tyler (OTD) comments and agrees with Stephen (Qualcomm).
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) proposes to note the CR in line with previous comments
==== 8.X, 9.X Final Deadline ====
Noted
8.14 - - - Satellite Access related - - Docs:=4 -
8.14 S2-2106182 CR Approval 23.273 CR0186 (Rel-17, 'F'): Update 5GC-NI-LR procedure CATT Rel-17 r01 agreed. Revised to S2-2106622 Leo (Deutsche Telekom) provides r01.
Yunjing(CATT) is ok with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106622 CR Approval 23.273 CR0186R1 (Rel-17, 'F'): Update 5GC-NI-LR procedure CATT Rel-17 Revision of S2-2106182r01. Approved Agreed
8.14 S2-2106423 CR Approval 23.273 CR0192 (Rel-17, 'F'): Satellite RAT Type in LMF selection Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2106623 Cai Simon (Nokia) provides r01 and clarifies to S2-2106215
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2106623 CR Approval 23.273 CR0192R1 (Rel-17, 'F'): Satellite RAT Type in LMF selection Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106423r01. Approved Agreed
8.14 - - - Paging Suppress - - Docs:=2 -
8.14 S2-2106421 CR Approval 23.273 CR0191 (Rel-17, 'B'): Adding Paging Suppress Indication in LCS Request Nokia, Nokia Shanghai Bell Rel-17 Noted Yunjing (CATT) provides comments.
Stephen (Qualcomm) also questions whether the CR is needed
Cai Simon (Nokia) replies to Stephen (Qualcomm) and Yunjing (CATT)
Tyler Hawbaker (OTD) provides comment.
Chris (Vodafone) supports the concept of controlling whether or not to do paging. It does need to be extend to RRC Inactive as well.
Yunjing (CATT) supports the concept and proposes to study the issue in Rel-18.
Cai Simon (Nokia) thanks to the support and clarifies the scope of extension
Cai Simon (Nokia) thanks to the support, answers the questions and provides r01
Runze (Huawei) supports CATT's view and proposes to study the issue in Rel-18.
Cai Simon (Nokia) provides r01 with the correct filename
Leo (Deutsche Telekom) provides r02.
Stephen (Qualcomm) agrees with Yunjing (CATT) and supports study in Rel-18
Ming (CATT) propose to convert the problem this CR want to address into an objective of eLCS_ph3 SID.
Leo (Deutsche Telekom) supports this proposal to address this topic in eLCS_ph3 SID.
Åke (Ericsson) objects r00, r01 and r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.14 S2-2106422 CR Approval 23.502 CR3105 (Rel-17, 'B'): Adding Paging Suppress Indication in LCS Request Nokia, Nokia Shanghai Bell Rel-17 Noted Leo (Deutsche Telekom) objects to original version of the CR.
Cai Simon (Nokia) provides r01 with the editorial update
Leo (Deutsche Telekom) objects to r01 of the CR.
Cai Simon (Nokia) provides r02
Åke (Ericsson) objects r00, r01 and r02
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) agrees to note the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.15 - - - Multimedia Priority Service (MPS) Phase 2 (MPS2) - - Docs:=4 -
8.15 S2-2105390 DISCUSSION Information MPS for 5GC LBO Authorization Gap Peraton Labs, CISA ECD Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.15 S2-2105383 CR Approval 23.501 CR3007 (Rel-17, 'F'): MPS for 5GC LBO Peraton Labs, CISA ECD, T-Mobile USA, Verizon, AT&T, Nokia, Nokia Shanghai-Bell Rel-17 Postponed Shabnam (Ericsson) provides comments regarding the category of the CR and the solution.
Thomas(Nokia) replies to Shabnam.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.15 S2-2105384 CR Approval 23.502 CR2896 (Rel-17, 'F'): MPS for 5GC LBO Peraton Labs, CISA ECD, T-Mobile USA, Verizon, AT&T, Nokia, Nokia Shanghai-Bell Rel-17 Postponed Robert (Peraton Labs) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.15 S2-2105385 CR Approval 23.503 CR0605 (Rel-17, 'F'): MPS for 5GC LBO Peraton Labs, CISA ECD, T-Mobile USA, Verizon, AT&T, Nokia, Nokia Shanghai-Bell Rel-17 Postponed Robert (Peraton Labs) provides r01.
Shabnam (Ericsson) comments that the category of the CR is independent of scope of the WI, it is functional change compared to previous version of the function, see comments.
Robert (Peraton Labs) comments and asks for clarification..
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.16 - - - Dynamic management of group-based event monitoring (TEI17_GEM) - - Docs:=2 -
8.16 S2-2106419 CR Approval 23.682 CR0483 (Rel-17, 'F'): Update Configuration for Group Monitoring Event with adding Users Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.16 S2-2106425 CR Approval 23.502 CR3106 (Rel-17, 'F'): Update Configuration for Group Monitoring Event with adding Users Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.17 - - - N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) - - Docs:=0 -
8.18 - - - System enhancement for Redundant PDU Session (TEI17_SE_RPS) - - Docs:=3 -
8.18 S2-2105555 CR Approval 23.501 CR3035 (Rel-17, 'F'): 5G URLLC Redundant PDU Session correction for NGAP parameters Nokia, Nokia Shanghai Bell, Convida Wireless LLC, LG Electronics Rel-17 WI Code should be TEI17_SE_RPS. r01 agreed. Revised to S2-2106624 Shabnam (Ericsson) provides r01 correcting the WI code and cosigns.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.18 S2-2106624 CR Approval 23.501 CR3035R1 (Rel-17, 'F'): 5G URLLC Redundant PDU Session correction for NGAP parameters Nokia, Nokia Shanghai Bell, Convida Wireless LLC, LG Electronics, Ericsson Rel-17 Revision of S2-2105555r01. Approved Agreed
8.18 S2-2105572 CR Approval 23.501 CR3043 (Rel-17, 'F'): Correction on Redundant PDU Session LG Electronics, Nokia, Nokia Shanghai Bell, Convida Wireless, Huawei, HiSilicon, ZTE, Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.19 - - - IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) - - Docs:=0 -
8.20 - - - Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) - - Docs:=0 -
8.21 - - - Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) - - Docs:=35 -
8.21 S2-2105253 LS In Action LS from CT WG3: LS on AM Influence requests for multiple applications CT WG3 (C3-213359) Rel-17 Responses drafted in S2-2105415 and S2-2105709. Final response in S2-2106962
==== 8.X, 9.X Final Deadline ====
Replied to
8.21 S2-2105415 LS OUT Approval [DRAFT] LS reply on AM Influence requests for multiple applications Ericsson Rel-17 Response to S2-2105253. r01 agreed. Revised to S2-2106962, merging S2-2105709 Haiyang (Huawei) suggests to merge this into S2-2105709 to have a single thread for discussion.
Belen (Ericsson) requests to use this thread and this draft LS as basis.
Haiyang(Huawei) is OK to use this thread and this draft LS as basis and provides comments.
Belen (Ericsson) replies to Huawei
Pallab (Nokia) comments.
Haiyang(Huawei) is OK to follow the majority and provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106962 LS OUT Approval LS reply on AM Influence requests for multiple applications SA WG2 Rel-17 Revision of S2-2105415r01, merging S2-2105709. Approved Approved
8.21 S2-2105709 LS OUT Approval [DRAFT] LS Reply on AM Influence requests for multiple applications Huawei, HiSilicon Rel-17 Response to S2-2105253. Merged into S2-2106962 Zhuoyi (China Telecom) asks for some clarifications.
Haiyang (Huawei) clarifies to Zhuoyi (China Telecom)
Haiyang (Huawei) is OK to merge this paper into 5415
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.21 S2-2105256 LS In Action LS from CT WG3: LS on Nnef_AMPolicyAuthorization input parameters CT WG3 (C3-213552) Rel-17 Responses drafted in S2-2105413, S2-2105609 and S2-2105705. Final response in S2-2106963
==== 8.X, 9.X Final Deadline ====
Replied to
8.21 S2-2105413 LS OUT Approval [DRAFT] LS reply on Nnef_AMPolicyAuthorization input parameters Ericsson Rel-17 Response to S2-2105256. r02 agreed. Revised to S2-2106963, merging S2-2105609 and S2-2105705 Zhuoyi (China Telecom) suggests this LS can merge with S2-2105705 and ask for discussion on Answer 1.
Haiyang(Huawei) provides r01 with clarification.
Belen (Ericsson) asks to use this LS as basis for discussion. OK with r01
Zhuoyi (China Telecom) replies to Huawei's anwers.
Pallab (Nokia) asks questions on r01
Belen (Ericsson) shares Nokia understanding on the Policy duration.
Haiyang(Huawei) provides clarification.
Zhuoyi (China Telecom) provides comments.
Pallab (Nokia) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106963 LS OUT Approval LS reply on Nnef_AMPolicyAuthorization input parameters SA WG2 Rel-17 Revision of S2-2105413r02, merging S2-2105609 and S2-2105705. Approved Approved
8.21 S2-2105609 LS OUT Approval [DRAFT] LS on Nnef_AMPolicyAuthorization input parameters China Telecom Corporation Ltd. Response to S2-2105256. Merged into S2-2106963 Belen (Ericsson) proposes to merge this Draft LS into S2-2105413
Zhuoyi (China Telecom) accepts to merge this Draft LS into S2-2105413
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.21 S2-2105705 LS OUT Approval [DRAFT] LS Reply on AMPolicyAuthorization input parameters Huawei, HiSilicon Rel-17 Response to S2-2105256. Merged into S2-2106963 Zhuoyi (China Telecom) suggests this LS can merge into S2-2105413 and continue the discussion in the thread of that paper.
Haiyang(Huawei) is OK to merge into S2-2105413 to have a single thread for discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.21 S2-2105403 CR Approval 23.502 CR2900 (Rel-17, 'F'): BSF related update of NRF services (23.502) Oracle Corporation Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.21 S2-2105404 CR Approval 23.501 CR3011 (Rel-17, 'F'): BSF related update of NRF services (23.501) Oracle Corporation, Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.21 S2-2105414 CR Approval 23.502 CR2902 (Rel-17, 'F'): Nnef_AMPolicyAuthorization clarifications Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.21 S2-2105706 CR Approval 23.503 CR0620 (Rel-17, 'F'): Clarifications on Nnef_AMPolicyAuthorization input parameters Huawei, HiSilicon, Ericsson Rel-17 r01 agreed. Revised to S2-2106964 Pallab (Nokia) provides r01
Haiyang(Huawei) accepts r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106964 CR Approval 23.503 CR0620R1 (Rel-17, 'F'): Clarifications on Nnef_AMPolicyAuthorization input parameters Huawei, HiSilicon Rel-17 Revision of S2-2105706r01. Approved Agreed
8.21 S2-2105416 CR Approval 23.502 CR2903 (Rel-17, 'F'): AM influence request for multiple applications Ericsson Rel-17 r02 agreed. Revised to S2-2106965 Zhuoyi (China Telecom) provide r01 with editorial updates.
Pallab (Nokia) requests for clarification
Belen (Ericsson) provides r02.
Pallab (Nokia) comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106965 CR Approval 23.502 CR2903R1 (Rel-17, 'F'): AM influence request for multiple applications Ericsson Rel-17 Revision of S2-2105416r02. Approved Agreed
8.21 S2-2105710 CR Approval 23.502 CR2961 (Rel-17, 'F'): Clarifications on AM Influence requests for multiple applications Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.21 S2-2105711 CR Approval 23.503 CR0621 (Rel-17, 'F'): Clarifications on AM Influence requests for multiple applications Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106966 Haiyang(Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106966 CR Approval 23.503 CR0621R1 (Rel-17, 'F'): Clarifications on AM influence requests for multiple applications Huawei, HiSilicon Rel-17 Revision of S2-2105711r01. Approved Agreed
8.21 S2-2105417 CR Approval 23.502 CR2904 (Rel-17, 'F'): Corrections to BSF subscription Ericsson Rel-17 r01 agreed. Revised to S2-2106967 Zhuoyi (China Telecom) provides comments.
Belen (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106967 CR Approval 23.502 CR2904R1 (Rel-17, 'F'): Corrections to BSF subscription Ericsson Rel-17 Revision of S2-2105417r01. Approved Agreed
8.21 S2-2105418 DISCUSSION Agreement Notification of SM Policy Association establishment . Ericsson Approved Pallab (Nokia): requests for clarification
Jinguo(ZTE) comments
Pallab (Nokia): responds to Jinguo(ZTE)
Belen (Ericsson) replies to Nokia
Pallab (Nokia) responds
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.21 S2-2105419 CR Approval 23.503 CR0606 (Rel-17, 'F'): Notification of SM Policy Association establishment Ericsson Rel-17 r01 agreed. Revised to S2-2106968 Haiyang (Huawei) provides r01
Haiyang (Huawei) provides more clarification
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106968 CR Approval 23.503 CR0606R1 (Rel-17, 'F'): Notification of SM Policy Association Establishment Ericsson, Huawei, HiSilicon, China Mobile Rel-17 Revision of S2-2105419r01. Approved Agreed
8.21 S2-2105420 CR Approval 23.502 CR2905 (Rel-17, 'F'): Notification of SM Policy Association establishment Ericsson Rel-17 r03 agreed. Revised to S2-2106969 Zhuoyi (China Telecom) ask for clarification.
Belen (Ericsson) provides r01
Haiyang(Huawei) provides r01
Zhuoyi (China Telecom) provides r02 and further comments.
Belen (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106969 CR Approval 23.502 CR2905R1 (Rel-17, 'F'): Notification of SM Policy Association Establishment Ericsson, China Mobile Rel-17 Revision of S2-2105420r03. Approved Agreed
8.21 S2-2105707 CR Approval 23.501 CR3065 (Rel-17, 'F'): Corrections on geographical area Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106970 Belen (Ericsson) provides comments
Haiyang(Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106970 CR Approval 23.501 CR3065R1 (Rel-17, 'F'): Corrections on geographical area Huawei, HiSilicon Rel-17 Revision of S2-2105707r01. Approved Agreed
8.21 S2-2105708 CR Approval 23.502 CR2960 (Rel-17, 'F'): Corrections on geographical area Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106971 Belen (Ericsson) provides comments
Pallab (Nokia) shares the same view as Ericsson.
Haiyang (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106971 CR Approval 23.502 CR2960R1 (Rel-17, 'F'): Corrections on geographical area Huawei, HiSilicon Rel-17 Revision of S2-2105708r01. Approved Agreed
8.21 S2-2105936 CR Approval 23.502 CR3012 (Rel-17, 'F'): Correction on dynamic updates of AM Policy Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2106972 Yifan (China Telecom) provides r01.
Haiyang (Huawei) accepts r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106972 CR Approval 23.502 CR3012R1 (Rel-17, 'F'): Correction on dynamic updates of AM Policy Huawei, HiSilicon Rel-17 Revision of S2-2105936r01. Approved Agreed
8.21 S2-2105937 CR Approval 23.501 CR3108 (Rel-17, 'F'): Update BSF NF profile to support SUPI and GPSI Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.21 S2-2105953 CR Approval 23.502 CR3018 (Rel-17, 'F'): Update PCF services table and NEF services table China Telecom Rel-17 r01 agreed. Revised to S2-2106973 Pallab (Nokia) requests to provide a revision with revision marks showing the changes
Yifan (China Telecom) provides r01.
Pallab (Nokia) points that there is some overlap with 5936. OK with r01
Yifan (China Telecom) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.21 S2-2106973 CR Approval 23.502 CR3018R1 (Rel-17, 'F'): Update PCF services table and NEF services table China Telecom Rel-17 Revision of S2-2105953r01. Approved Agreed
8.22 - - - IP address pool information from UDM (TEI17_IPU) - - Docs:=0 -
8.23 - - - Same PCF selection for AMF and SMF (TEI17-SPSFAS) - - Docs:=0 -
8.24 - - - Support of different slices over different Non-3GPP access (TEI17_N3SLICE) - - Docs:=0 -
8.25 - - - Minimization of Service Interruption (MINT) - - Docs:=14 -
8.25 S2-2105249 LS In Action LS from CT WG1: LS on the final conclusion of FS_MINT-CT CT WG1 (C1-213908) Rel-17 Response drafted in S2-2106128. Postponed Hyunsook (LGE) proposes to postpone it.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.25 S2-2105307 LS In Action LS from TSG SA: Reply LS on the conclusion of FS_MINT-CT TSG SA (SP-210581) Rel-17 Response drafted in S2-2106128. Postponed Hyunsook (LGE) proposes to postpone it.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.25 S2-2106128 LS OUT Approval [DRAFT] LS on MINT functionality for Disaster Roaming LG Electronics Rel-17 Response to S2-2105307 and S2-2105249. Postponed Hyunsook (LGE) proposes to postpone the reply LS.
However, just for the case we want to send agreed CRs, provides r01 before the revision deadline.
Lalith(Samsung) agrees to postpone the reply LS.
Wen(vivo) agrees to postpone the reply LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.25 S2-2105813 LS OUT Approval [DRAFT] LS on introduction of disaster roaming service Ericsson Rel-17 Noted Hyunsook (LGE) proposes to note this draft LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.25 S2-2105485 DISCUSSION Discussion SA WG2 specification impact on FS_MINT-CT . LG Electronics, KT Corp., LG Uplus, SK Telecom Rel-17 Noted Hyunsook (LGE) thinks this paper can be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.25 S2-2105486 CR Approval 23.501 CR3019 (Rel-17, 'B'): Adding the functionality on MINT LG Electronics, KT Corp., LG Uplus, SK Telecom Rel-17 r11 agreed. Revised to S2-2106659, merging S2-2105811 and S2-2106012 Lalith (Samsung) comments
Wen (vivo) comments
Hyunsook (LGE) proposes to discuss the MINT basic functionality with S2-2105486 as a single thread.
Haris (Qualcomm) supports the suggestion from Hyunsook and provides r01 to S2-2105486
Lalith (Samsung) provides r02
Wen (vivo) provides r03
Qian (Ericsson) provides r04
Hyunsook (LGE) provides r05.
Hyunsook (LGE) provides r06.
Lalith(Samsung) provides r07.
Mike (Convida Wireless) provide r08
Haris (Qualcomm) comments on r08
Hyunsook (LGE) thinks the comment from Haris is reasonable and provides r09.
Haris (Qualcomm) provides r10
Chris (Vodafone) provides r11
==== 8.X, 9.X Revisions Deadline ====
Hyunsook (LGE) is ok with r11
Qian (Ericsson) provides comments
Chris (Vodafone) answers Ericsson
==== 8.X, 9.X Final Deadline ====
Revised
8.25 S2-2106659 CR Approval 23.501 CR3019R1 (Rel-17, 'B'): Adding the functionality on MINT LG Electronics, KT Corp., LG Uplus, SK Telecom, vivo, Ericsson, Samsung, Convida Wireless LLC Rel-17 Revision of S2-2105486r11, merging S2-2105811 and S2-2106012. Approved Agreed
8.25 S2-2105811 CR Approval 23.501 CR3090 (Rel-17, 'B'): Introduction of MINT support Ericsson, Convida Wireless LLC Rel-17 Merged into S2-2106659 Hyunsook (LGE) proposes to merge this CR with S2-2105486.,
and to discuss it in a single thread.
==== 8.X, 9.X Revisions Deadline ====
Hyunsook (LGE) notes this CR was merged into S2-2105486.
Qian (Ericsson) confirms that this paper is merged into S2-2105486.
==== 8.X, 9.X Final Deadline ====
Merged
8.25 S2-2106012 CR Approval 23.501 CR3127 (Rel-17, 'B'): Support for MINT vivo Rel-17 Merged into S2-2106659 Hyunsook (LGE) proposes to merge this CR with S2-2105486.,
and to discuss it in a single thread.
Wen(vivo) responds to Hyunsook (LGE) and suggests to keep the 'Network selection in Disaster Condition' in S2-2106012 with r01.
Hyunsook (LGE) thinks the contents of r01 (details of the network selection) should be specified in CT1 TS 23.122.
Wen (vivo) responds to Hyunsook (LGE) and agrees to merge this CR with S2-2105486.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.25 S2-2105812 CR Approval 23.502 CR2990 (Rel-17, 'B'): Introduction of MINT support Ericsson, Convida Wireless LLC Rel-17 r03 agreed. Revised to S2-2106660, merging S2-2106013 Haris(Qualcomm) proposes r01
Hyunsook (LGE) proposes r02 as another alternative.
Qian (Ericsson) provides comments and asks question.
Hyunsook (LGE) provides r03.
Wen (vivo) ask a question for clarification.
Qian (Ericsson) responds.
Lalith(Samsung) supports Qian.
Wen (vivo) can live with r03.
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson) says we can continue to work on this based on ENs and agrees to go with r03 for now.
Hyunsook (LGE) is happy to go with r03.
Please, add 'LG Electronics' as supporting companies in the final version.
Haris (Qualcomm) indicates that is ok with r03 but contains typo that needs to be corrected in final version
Qian (Ericsson) says that we can fixed the typo in the final version (Roaing ->Roaming, Registarion -> Registration)
==== 8.X, 9.X Final Deadline ====
Revised
8.25 S2-2106660 CR Approval 23.502 CR2990R1 (Rel-17, 'B'): Introduction of MINT support Ericsson, Convida Wireless LLC, LG Electronics Rel-17 Revision of S2-2105812r03, merging S2-2106013. Approved Agreed
8.25 S2-2105858 CR Approval 23.502 CR3001 (Rel-17, 'B'): UE configuration with disaster area information Lenovo, Motorola Mobility Rel-17 Noted Hyunsook (LGE) objects this CR.
Haris (Qualcomm) objects to the CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.25 S2-2105861 CR Approval 23.502 CR3002 (Rel-17, 'B'): Steering the UE to RAT and frequencies in the PLMN providing disaster roaming Lenovo, Motorola Mobility Rel-17 Noted Hyunsook (LGE) objects this CR.
Haris (Qualcomm) objects to this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.25 S2-2106013 CR Approval 23.502 CR3028 (Rel-17, 'B'): Support for MINT vivo Rel-17 Merged into S2-2106660 Hyunsook (LGE) objects to have a separate registration procedure for disaster roaming.
Wen (vivo) responds to Hyunsook (LGE).
Lalith(Samsung) comments.
Wen(vivo) replies to Lalith(Samsung) and provides r01.
Lalith(Samsung) and provides r02.
Hyunsook (LGE) proposes to merge this CR into S2-2105812.
Wen (vivo) agrees to merge this CR into S2-2105812.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.26 - - - Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups - - Docs:=37 -
8.26 S2-2105292 LS In Action LS from SA WG3: LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS SA WG3 (S3-212196) Rel-17 Response drafted in S2-2105697. Final response in S2-2106974
==== 8.X, 9.X Final Deadline ====
Replied to
8.26 S2-2105697 LS OUT Approval [DRAFT] LS reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS Huawei, HiSilicon Rel-17 Response to S2-2105292. Revised to S2-2106974. Haiyang (Huawei) provides r01
Chris (Vodafone) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106974 LS OUT Approval LS Reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS SA WG2 Rel-17 Revision of S2-2105697r02. Approved Approved
8.26 S2-2105698 CR Approval 23.501 CR3063 (Rel-17, 'B'): Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS Huawei, HiSilicon Rel-17 Merged into S2-2106976 Laurent (Nokia): comments for agreement before doing CR update.
Haiyang (Huawei) responds to Laurent (Nokia)
Haiyang (Huawei) indicates this paper has been merged into S2-2105393
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.26 S2-2105699 CR Approval 23.502 CR2957 (Rel-17, 'B'): Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS Huawei, HiSilicon Rel-17 CC#4: r07 + changes agreed. Revised, merging S2-2105394, to S2-2106668. Chris (Vodafone) provides the merge of S2-2105394 into S2-2105699
Haiyang(Huawei) is OK with r01 provided by Chris (Vodafone)
Stefan (Ericsson) provides r02
Chris (Vodafone) does not (yet) object to r02 but requests Ericsson to provide an aligned update to the 23.501 CR.
Laurent (Nokia): provides r09
Laurent (Nokia): correction provides r03 (not r09 as indicated by mistake)
Chris (Vodafone) provides r04
Stefan (Ericsson) provides question on r04
Laurent (Nokia): provides r05( plaese forget it ) and r06
Stefan (Ericsson) comments on r06
Stefan (Ericsson) provides r07
==== 8.X, 9.X Revisions Deadline ====
Chris (Vodafone) points out an error with r07 but can accept r07.
Haiyang (Huawei) thinks r08 is better but can accept r07.
Haris (Qualcomm) also thinks r08 is better than r07
Chris (Vodafone) provides an r09 in drafts folder. Turquoise and green show changes compared to r07.

R07 remains OK, but it would be good to improve to r09 in CC#4
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106668 CR Approval 23.502 CR2957R1 (Rel-17, 'B'): Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS Huawei, HiSilicon, Vodafone, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2105699r07 + changes, merging S2-2105394. Approved Agreed
8.26 S2-2105392 CR Approval 23.401 CR3645 (Rel-17, 'B'): EPS User Plane Integrity Protection with minimal core network changes Vodafone Rel-17 r14 agreed. Revised to S2-2106975 Laurent (Nokia): comments and provides r01 (in case a 23.401 CR was finally chosen)
Stefan (Ericsson) comments and provides r02
Chris (Vodafone) replies to Nokia that the main reason for the 23.401 CR is for LTE-UPIP with NO core network changes except to the MME.
Haiyang (Huawei) provides his view on the documentation
Guillaume (MediaTek) comments.
Chris (Vodafone) replies to Mediatek: the SA3 WID covers both option 1 and option 3.
Haris (Qualcomm) provides r03
Chris (Vodafone) provides r04
Haiyang(Huawei) provides r05
Stefan (Ericsson) provides r06
Guillaume (MediaTek Inc.) provides r07
Laurent (Nokia): provides r08
Laurent (Nokia): provides r09 (you can forget r08)
Stefan (Ericsson) comments on r09
Chris (Vodafone) provides r10
Haiyang(Huawei) provides clarification
Laurent (Nokia): answers
Stefan (Ericsson) replies to Laurent
Guillaume (MediaTek) comments and provides r11.
Laurent (Nokia): provides r12
Chris (Vodafone) comments
Chris (Vodafone) provides R13
Laurent (Nokia): provides r14
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106975 CR Approval 23.401 CR3645R1 (Rel-17, 'B'): EPS User Plane Integrity Protection with minimal core network changes Vodafone, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2105392r14. Approved Agreed
8.26 S2-2105393 CR Approval 23.501 CR3009 (Rel-17, 'B'): EPS User Plane Integrity Protection using SMF+PGW-C Vodafone (based on earlier draft from Huawei, HiSilicon) Rel-17 r06 agreed. Revised to S2-2106976, merging S2-2105698 Laurent (Nokia): Comments (same as for Tdoc 5698 which is on AI 6.9)
Tdoc 5698 and 5393 SHOULD be in the same AI!!
Stefan (Ericsson) provides r01
Chris (Vodafone) is OK with r01
Chris (Vodafone) replies to comments from Nokia that Laurent sent on the CC#1 agenda thread
Laurent (Nokia): provides r02
Chris (Vodafone) accepts r02
Haiyang(Huawei) provides r03
Stefan (Ericsson) provides question
Stefan (Ericsson) provides another question
Stefan (Ericsson) provides r04
Haris (Qualcomm) asks question on r04
Chris (Vodafone) answers both Ericsson questions
Laurent (Nokia): provides r05
Chris (Vodafone) answers Haris' (Qualcomm) question and provides an r06
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106976 CR Approval 23.501 CR3009R1 (Rel-17, 'B'): EPS User Plane Integrity Protection using SMF+PGW-C Vodafone, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2105393r06, merging S2-2105698. Approved Agreed
8.26 S2-2105394 CR Approval 23.502 CR2898 (Rel-17, 'B'): EPS User Plane Integrity Protection using SMF+PGW-C Vodafone (based on earlier draft from Huawei, HiSilicon) Rel-17 Merge into S2-2106668 Haiyang (Huawei) suggests this paper to be merged into S2-2105699
Chrs (Vodafone) accepts Haiyang (Huawei) proposal to merge this paper into S2-2105699
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.26 S2-2105269 LS In Action LS from RAN WG2: LS on lower bound for eDRX cycle length RAN WG2 (R2-2106537) Rel-17 Response drafted in S2-2106413 (noted). Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.26 S2-2106413 LS OUT Approval [DRAFT] Reply LS on lower bound for eDRX cycle length Qualcomm Technologies Int Rel-17 Response to S2-2105269. Noted Mike (Convida Wireless) supports sending the LS
Steve (Huawei) comments
Miguel (Qualcomm) responds to Steve, Sudeep and Kyunghun and asks operators what is their opinion.
Guillaume (MediaTek) shares the view expressed by Apple/Huawei/Facebook.
Hannu (Nokia) points out that the support of 2.56 s eDRX won't bring overhead as it is not proposed as the only eDRX cycle, but just the shortest possible eDRX cycle that can be supported along with the longer ones as necessary.
Lars (Sony) supports the introduction of 2.56 s eDRX. No need to send an LS reply.
Sherry (Xiaomi) shares the view that introducing 2.56s as lower bound value doesn't bring any additional overhead.
Kyunghun (Facebook) supports the introduction of 2.56 s eDRX, and could not find enough reason for sending an reply LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2105252 LS In Information LS from CT WG1: Reply LS on introducing extended DRX for RedCap UEs CT WG1 (C1-213966) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106025 DISCUSSION Discussion Discussion on eDRX in RRC_Inactive for RedCap. Apple Noted Sherry (Xiaomi) asks if we can take a value smaller than 10485.76s as the upper bound eDRX value to support eDRX >10.24s in CM-CONNECTED with RRC_Inactive state in R17?
Miguel (Qualcomm) answers to Sherry (Xiaomi) that anything above 10.24s for RRC inactive requires system impacts, so lowering the maximum eDRX value upper does not help.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) replies to Sherry eDRX >10.24s in RRC_Inactive state is not possible in Rel-17. We should strive to add it as part of Rel-18 where we have got more time to evaluate the candidate solutions.
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106394 CR Approval 23.501 CR3209 (Rel-17, 'C'): Extended DRX for NR (RedCap) Qualcomm Inc. Rel-17 r05 agreed. Revised to S2-2106977, merging S2-2106159 and S2-2106175 Wanqiang (Huawei) asks questions for clarification.
Miguel (Qualcomm) responds to Wanqiang
Hannu (Nokia) provides r01 to tidy up the cover page and asks why 2.56 s eDRX cycle is left out from the NR eDRX range?
Steve (Huawei) provides r02, comments on applicability to NR UEs and RAN2.
Aihua(China Mobile) provides r03 to correct the Work item code, and suggests S2-2106175 to merged.
Paul (Ericsson) provides r04.
Chris (Vodafone) (Ericsson) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Lars (Sony) we are ok with r05.
Miguel (Qualcomm) is OK with r05
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106977 CR Approval 23.501 CR3209R1 (Rel-17, 'C'): Extended DRX for NR (RedCap) Qualcomm Inc. Rel-17 Revision of S2-2106394r05, merging S2-2106159 and S2-2106175. Approved Agreed
8.26 S2-2106396 DISCUSSION Agreement RRC inactive and eDRX longer than 10.24s. Qualcomm Inc Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106399 CR Approval 23.501 CR3212 (Rel-17, 'B'): RRC inactive with CM-IDLE for eDRX>10.24s Qualcomm Incorporated Rel-17 Check WI Code spelling. Noted Paul (Ericsson) asks question for clarification.
Miguel (Qualcomm) asks for clarification on the question
Wanqiang (Huawei) comments and proposes to note this CR
Paul (Ericsson) provides response to Miguel (Qualcomm) and asks further questions for clarification.
Miguel (Qualcomm) provides answers to Paul (Ericsson)
Paul (Ericsson) comments and proposes to note this CR.
Sudeep (Apple) provides comments and proposes to NOTE this CR.
Hannu (Nokia) comments that the introduction of RRC-Inactive + CM-IDLE state combination should not be done without consulting RAN2.
Sherry (Xiaomi) comments that the proposed solution is over-complex with RAN impact to resolve the issue.
Miguel (Qualcomm) comments that this and any Rel-17 CR on RRC inactive > 10.24s should be noted as per show of hands in CC#2.
Sherry (Xiaomi) would confirm show of hands result in CC#2.
Paul (Ericsson) objects to this CR as it does not meet the objectives of power saving due to adding signaling for MM and page response, increasing paging load on radio interface compared to RAN paging (as not supported in this solution), increases system complexity by impacting multiple interface necessarily as well as unnecessarily impacting the UE by introducing a new state.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106400 CR Approval 23.502 CR3098 (Rel-17, 'B'): CM-IDLE with RRC inactive procedures Qualcomm Incorporated Rel-17 Noted Steve (Huawei) Should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2105241 LS In Action LS from RAN WG2: LS on introducing extended DRX for RedCap UEs RAN WG2 (R2-2104374) Rel-17 Revision of postponed S2-2103769 from S2-145E. Responses drafted in S2-2105802 and S2-2106402. Final response in S2-2106978
==== 8.X, 9.X Final Deadline ====
Replied to
8.26 S2-2105802 LS OUT Approval [DRAFT] Reply LS on introducing extended DRX for RedCap UEs Ericsson Rel-17 Response to S2-2105241. Noted Miguel (Qualcomm) proposes to NOTE this proposed reply LS and use S2-2106402 as baseline.
Steve (Huawei) This LSout can't be sent without S2-2105804 and S2-2105805 which go beyond the common understanding
Hannu (Nokia) supports Miguel and Steve that for Rel-17 it is more practical to note this LS and to use S2-2106402 as baseline for further work
Paul (Ericsson) provides r01.
Miguel (Qualcomm) cannot accept r01 and insists we should use S2-2106402 as baseline as is inline with the SoH on CC#2.
Sherry (Xiaomi) comments.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) proposes to work this out via document S2-2106402.
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106402 LS OUT Approval [DRAFT] Reply LS on introducing extended DRX for RedCap UEs Qualcomm Technologies Int Rel-17 Response to S2-2105241. r01 agreed. Revised to S2-2106978 Paul (Ericsson) provides r01.
Hannu (Nokia) supports r01.
==== 8.X, 9.X Revisions Deadline ====
Miguel (Qualcomm) is OK with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106978 LS OUT Approval Reply LS on introducing extended DRX for RedCap UEs SA WG2 Rel-17 Revision of S2-2106402r01. Approved Approved
8.26 S2-2105803 DISCUSSION Agreement Discussion on long eDRX value system impact to support RedCap. Ericsson, MediaTek Inc, Deutsche Telekom Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2105804 CR Approval 23.501 CR2869R1 (Rel-17, 'B'): Support for RedCap UE indication and eDRX Ericsson, MediaTek Inc, Deutsche Telekom Rel-17 Revision of (Noted) S2-2103903 from S2-145E. Noted Miguel (Qualcomm) Proposes to note this CR, instead use for the S2-2106394 for the non-controversial part of eDRX and S2-2106161 for RedCap Indication.
Wanqiang (Huawei) agrees to note this CR and uses the Qualcomm and CMCC papers as the baseline for the non-controversial part.
Aihua (China Mobile) agrees to use S2-2106394 and S2-2106161 as the basislines, and also suggests to use S2-2106159 as the basislines for AMF paging strategy of 10.24s cycle.
Hannu (Nokia) supports the proposal to note this CR. Rel-17 part of the work should be designed using the existing Rel-17 CN capabilities.
Paul (Ericsson) provides r02, removing impacts from support for HLCOM.
Sherry (Xiaomi) proposes to merge this CR (e.g. RedCap Indication) into 6394 to reuse the existing solutions to support the no-controversial part, expecting further R17 enhancements to support eDRX >10.24s in CM-CONNECTED with RRC_Inactive state.
Miguel (Qualcomm) has serious concerns with r02 and proposes to NOTE this CR.
Lars (Sony) responds to Miguel (Qualcomm)
Miguel (Qualcomm) still finds the proposal not acceptable
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) requests that this paper is postponed for the reasons explained in S2-2105805.
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2105805 CR Approval 23.502 CR2986 (Rel-17, 'B'): Support for RedCap UE indication and eDRX Ericsson, MediaTek Inc, Deutsche Telekom Rel-17 Noted Miguel (Qualcomm) Proposes to note this CR
Paul (Ericsson) provides r01 addressing comments by Miguel (Qualcomm).
Steve (Huawei) As for the 501 counterpart (5804), Qualcomm and CMCC papers should be the baseline. This does not match that baseline and can't be agreed without its 501 counterpart.
Sudeep (Apple) prefers the concept in 5805, 5804.
Miguel (Qualcomm) still not ok with this CR, it's clear to use eDRX>10.24s for RRC inactive needs to be deferred to Rel-18 to be properly studied.
Lars (Sony) comments and suggest a way forward for rel-17.
Hannu (Nokia) can't agree this proposal and supports Lars (Sony) in specifying Rel-17 using the existing behaviour.
Lars (Sony) responds to Hannu (Nokia) and confirm that his understanding of the proposal is correct.
Paul (Ericsson) replies to Lars (Sony) and Hannu (Nokia) and clarifies that buffering in RAN may result in serious mis-operation.
Lars (Sony) responds to Paul (Ericsson).
Paul (Ericsson) clarifies that UE may wake up from eDRX cyle at a new serving gNB without connectivity to the old serving gNB that buffers the data. Hence the data can't be forwarded and will be lost.
Gerry (Verizon) supports the Ericsson CR for Release 17.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) requests to postpone this CR. Since we have got more than one candidate solutions, we must not rush to agree any of them before proper evaluation.
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2105806 CR Approval 23.502 CR2987 (Rel-17, 'C'): Event subscription parameters With DNN and S-NSSAI Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.26 S2-2106159 CR Approval 23.501 CR3153 (Rel-17, 'B'): EDRX enhancement for 10.24s cycle for RedCap China Mobile Rel-17 Merged into S2-2106977 Aihua(China Mobile) provides r01 to correct work item code.
Miguel (Qualcomm) believes this document can be considered merged into S2-2106394
==== 8.X, 9.X Revisions Deadline ====
Aihua(China Mobile) replies to Miguel.
==== 8.X, 9.X Final Deadline ====
Merged
8.26 S2-2106161 CR Approval 23.501 CR3155 (Rel-17, 'B'): Support RedCap UEs differentiation in 5GC China Mobile Rel-17 r04 agreed. Revised to S2-2106979 Aihua(China Mobile) provides r01 to correct work item code.
Paul (Ericsson) provides r02.
Lars (Sony) asks a question.
Paul (Ericsson) replies to Lars (Sony).
Lars (Sony) asks Paul (Ericsson) if the EN can be exchanged.
Lars (Sony) follow up with Paul.
Paul (Ericsson) replies to Lars.
Hannu (Nokia) provides r03 and co-signs.
Dieter (Deutsche Telekom) comments.
Steve (Huawei) comments
Huawei Wanqiang provides r04.
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) can agree either r03 or r04 and asks Dieter to clarify the need for two NR RedCap categories?
Guillaume (MediaTek) agrees with Hannu (Nokia)
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106979 CR Approval 23.501 CR3155R1 (Rel-17, 'B'): Support RedCap UEs differentiation in 5GC China Mobile, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2106161r04. Approved Agreed
8.26 S2-2106175 CR Approval 23.501 CR3163 (Rel-17, 'B'): Support Idle mode eDRX up to 10485.76 s for RedCap China Mobile Rel-17 Merged into S2-2106977 Aihua(China Mobile) suggests to mark S2-2106175 as 'merged with S2-2106394'.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.26 S2-2106273 DISCUSSION Decision EPS Support for IoT NTN. MediaTek Inc., Deutsche Telekom AG, Eutelsat, Intelsat, Sateliot, THALES Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.26 S2-2106275 CR Approval 23.401 CR3653 (Rel-17, 'B'): Introduction of Satellite support for Cellular IoT MediaTek Inc. Rel-17 Postponed Wanqiang (Huawei) provides r01.
Chris (Vodafone) is OK with r01 but we still need to add more next meeting - e.g. for RAN enforcement of 'in-country-MME'.
Stefan (Ericsson) provides r02
Guillaume (MediaTek) replies and suggest to postpone/note the CR in this meeting.
==== 8.X, 9.X Revisions Deadline ====
Guillaume (MediaTek) replies to Haris (Qualcomm)
Haris(Qualcomm) comments on r01
Hannu (Nokia) proposes to postpone rather than note the paper as SA2 intends to continue this work in future meetings.
Guillaume (MediaTek): ok to postpone
==== 8.X, 9.X Final Deadline ====
Postponed
8.26 S2-2106276 LS OUT Approval [DRAFT] LS on EPS support for IoT NTN in Rel-17 MediaTek Inc. Rel-17 r00 agreed. Revised to remove 'draft' in S2-2106834
==== 8.X, 9.X Final Deadline ====
Revised
8.26 S2-2106834 LS OUT Approval [DRAFT] LS on EPS support for IoT NTN in Rel-17 MediaTek Inc. Rel-17 Revision of S2-2106276r00. CC#4: Left open for further discussion before CC#5. CC#5: r01 agreed. Revised to S2-2106679. Guillaume (MediaTek) provides S2-2106834 following CC#4
Guillaume (MediaTek) provides r01.
Hannu (Nokia) prefers r01 even though it was distributed after deadline.
Revised
8.26 S2-2106679 LS OUT Approval LS on EPS support for IoT NTN in Rel-17 SA WG2 Rel-17 Revision of S2-2106834r01. Approved Approved
9 - - - Project Planning and Management - - Docs:=0 -
9.1 - - - New and Revised Work Items, TS/TR Cover sheets, Exception Sheets - - Docs:=0 -
9.1.1 - - - Rel-17 new and revised Work Items - - Docs:=4 -
9.1.1 S2-2106148 WID NEW Approval New WID: 5G System Enhancements for Reduced Capability NR Devices. China Mobile Rel-17 Revision of (Noted) S2-2104324 from S2-145E. r01 agreed. Revised to S2-2106793 Aihua(China Mobile) provides r01 to add more supporting companies and correct work item code.
Hannu (Nokia) supports r01 and comments on WID timing and terminology in the WID and the CR.
==== 8.X, 9.X Revisions Deadline ====
Aihua(China Mobile) replies.
Hannu (Nokia) comments on the WI completion time (but does NOT imply any objections against having it done as part of Rel-17).
Aihua(China Mobile) replies to Hannu.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.1 S2-2106793 WID NEW Approval New WID: 5G System Enhancements for Reduced Capability NR Devices. China Mobile Rel-17 Revision of S2-2106148r01. Approved Approved
9.1.1 S2-2106274 WID NEW Approval New Rel-17 WID on IoT NTN support for EPS . MediaTek Inc. Rel-17 r02 agreed. Revised to S2-2106794 Guillaume (MediaTek Inc.) provides r1
Guillaume (MediaTek Inc.) provides r2
Chunhui (Spreadtrum) comments.
Hannu (Nokia) questions whether this could be realistic Rel-17 WID and proposes a study phase first.
Guillaume (MediaTek) confirms this is realistic.
Guillaume (MediaTek Inc.) replies to Chunhui (Spreadtrum).
Hannu (Nokia) comments on the potential ambiguity in overloading an existing term (LTE-M, NB-IoT) in a new technical meaning.
Guillaume (MediaTek) replies to Hannu (Nokia)
==== 8.X, 9.X Revisions Deadline ====
Hannu (Nokia) thanks Guillaume for explanation.
Chunhui (Spreadtrum) objects to r1 & r2 since the merged contents from S2-2105842 are not within Rel17 scope.
Guillaume (MediaTek) does not understand Spreadtrum statement (that was not either made earlier in the discussion)
Guillaume (MediaTek) provides further clarification to Chunhui (Spreadtrum)
Chunhui(Spreadtrum) withdraws the objection with the clarification from Guillaume (MediaTek) that no content in r1/r2 is from S2-2105842(R18 SID from Qualcomm).
==== 8.X, 9.X Final Deadline ====
Revised
9.1.1 S2-2106794 WID NEW Approval New Rel-17 WID on IoT NTN support for EPS . MediaTek Inc. Rel-17 Revision of S2-2106274r02. Approved Approved
9.1.2 - - - TS/TR Cover sheets - - Docs:=8 -
9.1.2 S2-2105864 TS OR TR COVER Approval Cover Sheet for TS 23.256 for Approval to TSG SA Qualcomm Austria RFFE GmbH Rel-17 CC#5: Revised to S2-2106680. LaeYoung (LGE) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2106680 TS OR TR COVER Approval Cover Sheet for TS 23.256 for Approval to TSG SA Qualcomm Austria RFFE GmbH Rel-17 Revision of S2-2105864. Approved Approved
9.1.2 S2-2105881 TS OR TR COVER Approval Cover Sheet for TS 23.304 (to TSG SA for Approval) OPPO Rel-17 CC#5: r02 + changes agreed. Revised to S2-2106681. LaeYoung (LGE) thinks the cover page needs to be updated to reflect outcome of this meeting as the comment '(it will be updated in SA2#146E meeting)' in the document reads instead of approving r00.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2106681 TS OR TR COVER Approval Cover Sheet for TS 23.304 (to TSG SA for Approval) OPPO Rel-17 Revision of S2-2105881r02 + changes. Approved Approved
9.1.2 S2-2106091 TS OR TR COVER Approval Cover page of TS 23.247 Huawei, HiSilicon Rel-17 CC#5: r01 agreed. Revised to S2-2106682. LaeYoung (LGE) thinks the cover page needs to be updated to reflect outcome of this meeting as the comment 'TBD based on the progress of the meeting.' in the document reads instead of approving r00.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2106682 TS OR TR COVER Approval Cover page of TS 23.247 Huawei, HiSilicon Rel-17 Revision of S2-2106091r01. Approved Approved
9.1.2 S2-2106268 TS OR TR COVER Approval Cover sheet of TS 23.548 for Approval to TSG SA Huawei Rel-17 CC#5: r01 + changes agreed. Revised to S2-2106823. Dario S. Tonesi (Qualcomm) cannot accept r00
==== 8.X, 9.X Final Deadline ====
Hui (Huawei) provides r01
Revised
9.1.2 S2-2106823 TS OR TR COVER Approval Cover sheet of TS 23.548 for Approval to TSG SA Huawei Rel-17 Revision of S2-2106268r01 + changes. Approved Approved
9.1.3 - - - Rel-18 new Study Items/Work Items proposal - - Docs:=103 -
9.1.3 S2-2106239 DISCUSSION Discussion Discussion Paper for additional objectives in new SID FS_5WWC_Ph2. Huawei, HiSilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106240 SID NEW Approval New SID for FS_5WWC_Ph2 extension . Huawei, HiSilicon Rel-18 Noted Marco (Huawei) provides r01 with additional supporting companies.
Tyler (OTD) provides question on r01.
Marco (Huawei) answers to Tyle (OTD).
Curt (Charter) proposes to NOTE this thread and to discuss any related topic under S2-2105345.
Marco (Huawei) answers to Curt (Charter) and disagree to note it before discussing.
Curt (Charter) replies that my point is to have one thread to discuss WWC SID (pls check S2-2105345). There is already a question for you.
Susana (Vodafone) asks for clarification on the objective to study whether and how to support the scenario with two layers of RGs, i.e. 5G-RGs that are connected via another 5G-RG to the same or different 5GC.
Hualin(Huawei) replied to Susana (Vodafone).
Laurent (Nokia): objects to any revision of this SID
==== 8.X, 9.X Revisions Deadline ====
Stefan (Ericsson) also objects to any revision of this SID, to discuss using single baseline (5345)
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105345 WID NEW Approval New Study on the support for 5WWC, Phase 2. Nokia, Nokia Shanghai Bell Rel-18 r11 agreed. Revised to S2-2106795 Curt (Charter) superimposed texts from 6240r1 to 5345r1 for the sake of discussing/consolidation under one thread..
Myungjune (LGE) asks question on r01.
Laurent (Nokia): provides r02 (rm) and r04 (clean); you can disregard r03
Curt (Charter) comments on Myungjune (LG) questions.
Omkar (CableLabs) responding to Myungjune (LG) question on bullet 5.
Marco (Huawei) answers to questions.
Gerald (Matrixx) with support and comments.
Laurent (Nokia): Comments: let's discuss the bulleted objectives in 5345 and forget the other tdocs on 5WWC and who the rapporteur will be
Laurent (Nokia): Comments. I have created a file in INBOX where you can write your position wrt each of the numbered objectives
Dario (Qualcomm) asks questions for clarification
Marco (Huawei): provides Huawei position in the file in Draft folder
Stefan (Ericsson) provides comments and concerns on some objectives
Marco (Huawei): provides Huawei position Version 2 in the file in Draft folder
Tyler (OTD) expresses concern with some of the objectives of this SID.
Omkar (CableLabs) responds to question from Stefan (Ericsson)
Marco (Huawei) provides answers to several questions
Stefan (Ericsson) replies to Omkar
Hualin(Huawei) replied to Gerald (Matrixx).
Hualin(Huawei) replied to Curt (Charter).
Hualin(Huawei) object r02, 03, 04.
And comments why 'Whether and how to support mobility between 3GPP access network and trusted Non-3GPP access network for N5CW device' is removed? Propose to add it back.
Hualin(Huawei) comments on r04.
Marco(Huawei) provides r05 as 'maybe-rapporteur'.
Marco(Huawei) provides comments to R05 as Huawei, where objectives 2 & 9 are removed.
Laurent (Nokia): provides r06 as a clean version and r07
Adrian (vivo): asks question for clarification
Laurent (Nokia): answers
Laurent (Nokia): provides r08
Adrian (vivo) responds to Laurent
Laurent (Nokia): provides r09
Marco (Huawei): provides r10
Stefan (Ericsson) provides update in drafts folder based on r10
Dieter (Deutsche Telekom) comments and asks question for clarification.
Marco (Huawei) comments to Dieter (Deutsche Telekom).
Adrian (vivo): Is happy this morning.
Dieter (Deutsche Telekom) answers Marco.
Marco (Huawei) clarifies to Stefan (Ericsson) r10
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): is OK with R11 except following objective items 2c) 3c) 9), 10) and 11)
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106795 WID NEW Approval New Study on the support for 5WWC, Phase 2. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2105345r11. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105395 WID NEW Approval New WID on MPS when access to EPC/5GC is WLAN . Peraton Labs, CISA ECD, Verizon UK Ltd, AT&T, T-Mobile USA Rel-18 r02 agreed. Revised to S2-2106796 Haris(Qualcomm) comments
Marco (Huawei) asks clarifications.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106796 WID NEW Approval New WID on MPS when access to EPC/5GC is WLAN . Peraton Labs, CISA ECD, Verizon UK Ltd, AT&T, T-Mobile USA Rel-18 Revision of S2-2105395r02. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105434 DISCUSSION Agreement Use of L4S in 5GS Ericsson, Deutsche Telekom, AT&T, Verizon, Apple, T-Mobile USA Inc., Telefonica S.A., MediaTek Inc., CableLabs Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105435 WID NEW Approval New WID on Use of L4S in 5GS (5G_L4S) . Ericsson Rel-18 Noted Dario S. Tonesi (Qualcomm) comments
Youngkyo(Samsung) provides a question for clarification.
Jianning (Xiaomi) provides comment
Paul (Ericsson) replies to Youngkyo (Samsung) and Jianning (Xiaomi).
Curt (Charter) supports this WID as standalone.
xiaowan (vivo) provides comments
Dieter (Deutsche Telekom) supports this WID as standalone.
Omkar (CableLabs) supports this WID as standalone.
Paul (Ericsson) replies to Dario (Qualcomm).
Gerry (Verizon) supports the proposed WID as standalone.
Farooq (AT&T) supports this WID as standalone.
Dario (Qualcomm) replies to Paul that he cannot accept this proposal as stand-alone WID.
Hui (Huawei) prefers to perform study firstly on generic QoS exposure.
Jianning (Xiaomi) shares the view with Hui (Huawei) to start with study, to give more time to make best usage of the L4S for 5GS
Youngkyo(Samsung) shares the view with Hui (Huawei) and Jianning(Xiaomi).
Jari (NTT DOCOMO) seeks for clarification
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) replies to Youngkyo(Samsung), Jianning (Xiaomi) and Hui (Huawei).
Paul (Ericsson) replies to Jari (NTT DOCOMO).
Dieter (Deutsche Telekom) agrees to Paul's comment and proposes to move forward with a WID.
Dario (Qualcomm) objects to this WID.
Devaki (Nokia) proposes to consider L4S as part of XR services work (similar views as HUA, Xiaomi, Samsung).
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105449 DISCUSSION Information Motivations for eProSe R18 OPPO Rel-18 Revision of (Noted) S2-2103752 from S2-145E. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105448 SID NEW Approval New SID on enhancement for ProSe in 5G. OPPO Rel-18 Revision of (Noted) S2-2103751 from S2-145E. Merged into S2-2106806 Tricci (OPPO) proposed to converge the new Rel18 ProSe SID discussions to single thread for the merge of the two SIDs - i.e. Merge S2-2106099 into S2-2105448.
Hao Dong (ZTE) supports the proposal of merging these two SIDs and discussing the detail in a single thread.
Fei (OPPO) provides r02 to improve TU descriptions for the merged proposal.
Tricci (OPPO) provides r03 to propose the kick start of the technical discussions for this study.
Zhenhua (vivo) provides r03-vivo in draft folder with new objectives proposed.
Fei (OPPO) responds to Zhenhua (vivo).
Hannu (Nokia) shares r03-Nokia and asks questions on both the original r03 and the proposed additions in r03-Vivo
Changhong (Intel) proposes to merge it into S2-2106099
Mehrdad (Samsung) assumes this SID is already merged into S2-2106099r04+.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
9.1.3 S2-2105451 DISCUSSION Information Discussion on 5GS support for vertical layer AIML analytics for R18 OPPO Rel-18 Revision of (Noted) S2-2103759 from S2-145E. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105450 SID NEW Approval New SID on 5G System Support for AI/ML-based Services. OPPO, Samsung Rel-18 Revision of (Noted) S2-2103758 from S2-145E. r05 agreed. Revised to S2-2106797, merging S2-2106126 Dimitris (Lenovo) comments on the proposed SID
David (Samsung) replies to Lenovo.
Hyunsook (LGE) asks a question for the clarification.
Tricci (OPPO) responds to Hyunsook (LGE)
Juan Zhang (Qualcomm) provides comments
David (Samsung) replies to Qualcomm.
Paul (Ericsson) provides comments.
Yannick (Nokia): Nokia provides comments.
David (Samsung) replies to Ericsson.
Juan Zhang (Qualcomm) replies to David (Samsung).
Tricci (OPPO) thanks Juan for your questions and would like to respond.
Tricci (OPPO) thanks Yannick (Nokia) comments and would like to provide feedback.
Wang Yuan (Huawei) provides comments on r01.
Chia-Lin (MediaTek) ask for the clarification on the SID
Xiaobo(vivo) ask for the clarification on coordination with SA4.
Tricci (OPPO) thanks Chia-Lin (MediaTek) for the questions and would like to provides feedback.
Hyunsook (LGE) asks to include the potential impact on SA6.
Aihua(China Mobile) comments.
Tricci (OPPO) thanks Wang Yuan (Huawei) comments and would like to provide responses.
Tricci (OPPO) responds to Aihua(China Mobile) question.
Juan Zhang (Qualcomm) replies to Tricci and provides comments to r01.
David (Samsung) replies to LGE and vivo.
David (Samsung) thanks Juan for her comments, replies, provides r02.
Aihua(China Mobile) requests clarification for objective 3.
Yannick (Nokia): Nokia provides comments in a SID version in drafts folder.
David (Samsung) replies to China Mobile.
Tricci (OPPO) thanks. Yannick (Nokia) for the additional comments and would like to provide feedback.
Wang Yuan (Huawei): Huawei adds further comments in a SID version in drafts folder.
Tricci (OPPO) thanks Wang Yuan (Huawei) for the draft proposal and will take it into consideration for the next revisions.
David (Samsung) provides r03.
Juan Zhang (Qualcomm) provides comments.
Aihua(China Mobile) comments on r03.
David (Samsung) replies to CMCC.
Yannick (Nokia): Nokia comments on r03.
Ulises Olvera (InterDigital Inc.) agrees to r03 + modification on real time control for applications, agreed by David (Samsung), and asks authors to add InterDigital as supporting company.
David (Samsung) thanks Interdigital for the support, provides r04.
==== 8.X, 9.X Revisions Deadline ====
David (Samsung) replies to Nokia
Tricci (OPPO) thanks Yannick (Nokia)'s patient for further clarifications of his comments, and OPPO would like to further clarify Objective 1a.
Yannick (Nokia): Nokia replies to Samsung.
Chia-Lin (MediaTek) ask more following Nokia's Questions
David (Samsung) provides r05 with more supporting companies, replies to MediaTek
Chia-Lin (MediaTek) reply to David (Samsung)
David (Samsung) provides further replies to MediaTek
Wang Yuan (Huawei) is supportive to study the potential enhancements for analytics/predication exposure extensions but also prefer to study it in one place.
Xiao (TMC) supports this SID.
Juan Zhang (Qualcomm) provides further comments and proposed to technical endorse r05.
Yannick (Nokia): Nokia replies to OPPO and would still like to get clarify on objective 1a.
Paul (Ericsson) objects to approval of this SID at this meeting, though support the study in principle, e.g. r05 looks promising. In our view more time needs to be spent in Q4/21 on the overall Rel-18 content.
David (Samsung) replies to Nokia.
David (Samsung) can accept technical endorsement for this meeting as suggested by Qualcomm.
==== 8.X, 9.X Final Deadline ====
Tricci (OPPO) accepts kind technical endorsement from Juan (Qualcomm) for this meeting.
Revised
9.1.3 S2-2106797 SID NEW Approval New SID on 5G System Support for AI/ML-based Services. OPPO, Samsung Rel-18 Revision of S2-2105450r05, merging S2-2106126. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105493 SID NEW Approval New Study on Service-based N2. Intel, Cisco, Verizon UK Ltd, Qualcomm Incorporated, AT&T, Deutsche Telekom Rel-18 Noted Wanqiang(Huawei) comments
Haris (Qualcomm) comments
Saso (Intel) replies to Wanqiang(Huawei) and Haris (Qualcomm)
Jinguo(ZTE) comments
Saso (Intel) replies to Jinguo; proposes r01
Laurent (Nokia): Comments
Saso (Intel) replies to Laurent
Jinguo(ZTE) further comments
Biao(China Telecom) has similar comments with Nokia and Huawei, and suggests not to trigger such study at the early stage of 5G-Advanced.
Wanqiang (Huawei) replies to Saso
Saso (Intel) replies to Jinguo(ZTE)
Saso (Intel) replies to Wanqiang (Huawei)
Saso (intel) replies to Biao(China Telecom).
Wanqiang (Huawei) replies to Saso (Intel)
Shabnam (Ericsson) have concerns and do not support this study, provides further detailed comments.
Tony (Futurewei) has concerns with this study and provides comments.
Chi (China Unicom) provides comments.
Saso (Intel) replies and provides r02 with numbered objectives.
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) sees no fruitful addition in the versions/revisions of the is study proposal compared to original version and has provided technical comments already and proposes to Note this study.
Wanqiang (Huawei) proposes to Note this study.
Laurent (Nokia): objects to any revision of 5493
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105500 WID NEW Agreement New WID: Extensions to the TSC Framework to support DetNet (DetNet) . Ericsson Rel-18 Noted Yusuke (KDDI) asks a question for clarification.
György (Ericsson) responds.
Yusuke (KDDI) provides a comment for further clarification.
xiaowan (vivo) provides comments
Yusuke (KDDI) provides further comments.
Joachim Walewski (Ericsson) identified shortcomings proposed study from an object technology perspective.
György (Ericsson) responds to KDDI
György (Ericsson) responds to Joachim Walewski (Siemens).
Joachim Walewski (Siemens) responds to György (Ericsson).
Devaki (Nokia) comments.
György (Ericsson) responds to Siemens.
György (Ericsson) responds to Nokia.
György (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Yusuke (KDDI) proposes to add an objective for the study.
Devaki (Nokia) proposes that we consider a single SID for TSN/TSC/DetNet aspects to maximize solution re-use (as commented earlier), our proposal would be to consider this merged with S2-2105569.
György (Ericsson) responds and provides r02 in the drafts.
Devaki (Nokia) indicates that we are supportive of considering DETNET for Rel-18 together with TSN/TSC aspects in 5569, however we are not convinced of doing this study standalone at this time for technical reasons mentioned earlier thus object to standalone SID at this time, we are happy to continue the discussion until next meeting, let us postpone, Thanks.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105569 SID NEW Approval New SID: Study on 5G Timing Resiliency and TSC enhancements. Nokia, Nokia Shanghai Bell, Verizon, AT&T, Siemens, Sennheiser, Huawei, HiSilicon, Matrixx, ZTE, China Unicom, Vivo, NTT Docomo, ETRI, Xiaomi. Rel-18 r08 agreed. Revised to S2-2106798 Shabnam (Ericsson) provides comments and commented revisions in Drafts folder.
Devaki (Nokia) provides r01 (answering Ericsson questions/comments, adding additional supporting companies).
Joachim Walewski (Siemens) provides input on LRP and RAP.
György (Ericsson) comments.
Haiyang (Huawei) provides feedback in drafts folder.
György (Ericsson) provides comments in drafts folder.
Haiyang (Huawei) provides further feedback in drafts folder.
Chia-Lin (MediaTek) ask for the clear justification and clear objectives in this SID
György (Ericsson) comments in drafts folder.
Sebastian (Qualcomm) comments
Sang-Jun (Samsung) comments
György (Ericsson) responds.
Haiyang (Huawei) provides responses in the draft folder.
Devaki (Nokia) replies to Sebastian (Qualcomm).
Devaki (Nokia) replies to Chia-Lin (Mediatek).
Devaki (Nokia) provides r03.
Masa (KDDI) supports this SID and comments.
Haiyang(Huawei) provides suggestions on the objectives.
Sang-Jun (Samsung) comments.
Devaki (Nokia) comments.
Haiyang (Huawei) provides further feedback for URLLC aspects.
Devaki (Nokia) replies.
György (Ericsson) responds to Huawei.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) provides r06 to add Samsung, Interdigital as supporting companies.
Sang-Jun (Samsung) supports the SID.
Devaki (Nokia) provides r04 reflecting the status of this discussion.
Yuan Tao (CATT) supports this SID.
Dieter (Deutsche Telekom) supports this SID.
György (Ericsson) comments about r04.
György (Ericsson) responds to Nokia.
Haiyang(Huawei) provides further clarification and r07 in the draft folder
Devaki (Nokia) requests Ericsson for their views on exposure for reliability.
Devaki (Nokia) provides r07 with additional cosigning companies (KDDI, DT, CATT), also updates to the objectives considering discussions (E///, HUA) in the email thread.
Sebastian (Qualcomm) objects to the SID (r00 and all revisions)
György (Ericsson) provides r08 in the drafts folder.
György (Ericsson) responds to Huawei comments.
Shabnam (Ericsson) objects approval at this meeting, support parts of the study proposal in principle (e.g. using baseline as indicated in Draftr08_ERI), SA2 needs to do more work during Q4/2021 on the overall Rel-18 content.
Devaki (Nokia) thanks E/// for the revision proposal, replies and provides r08.
Haiyang (Huawei) suggests to.endorse r08 this meeting
==== 8.X, 9.X Final Deadline ====
Sebastian (Qualcomm) objects to r08; supports to spend more time on the SID during Q4/21 as suggested by Ericsson
Devaki (Nokia) clarifies r08 is same as Draftr08_ERI (minus the question for objective 1) - seems emails crossed. Agree with Haiyang that it would indeed be good to endorse at least as a baseline for continuing the discussions next meeting.
Devaki (Nokia) provides r09 (minus the same highlighted question also from justification 1) - including revision marked and clean version.
Revised
9.1.3 S2-2106798 SID NEW Approval New SID: Study on 5G Timing Resiliency and TSC enhancements. Nokia, Nokia Shanghai Bell, Verizon, AT&T, Siemens, Sennheiser, Huawei, HiSilicon, Matrixx, ZTE, China Unicom, Vivo, NTT Docomo, ETRI, Xiaomi. Rel-18 Revision of S2-2105569r08. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105587 SID NEW Approval New SID: Study on enhancement of 5G AM Policy. China Telecom Rel-18 Revision of (Noted) S2-2104448 from S2-145E. r04 agreed. Revised to S2-2106799 Belen (Ericsson) provides comments
Zhuoyi (China Telecom) replies to Ericsson's comments.
Pallab (Nokia) provides comments
Zhuoyi (China Telecom) replies to Ericsson and Nokia and provide r01.
Sherry (Xiaomi) comments.
Haris (Qualcomm) comments
Zhuoyi (China Telecom) provides r02.
Belen (Ericsson) comments on r02, still don't see our comments addressed.
Pallab (Nokia) comments on r02. Can only accept objectives 2 (reworded as below) & 3
Zhuoyi (China Telecom) provides r03.
Pallab (Nokia) comments on r03.
Belen (Ericsson) is okay with r03, some clarifications are requested
Zhuoyi (China Telecom) provides r04 with the suggested NOTE from Ericsson.
Chi (China Unicom) provides comments.
==== 8.X, 9.X Revisions Deadline ====
Yan (China Mobile) supports to keep the objective 1.
Pallab (Nokia) objects to r04 unless Objective #1 is removed and #3 is either removed or reworded. Also provides reasoning why it feels objective #1 is not needed and why #3 needs more work
Zhuoyi (China Telecom) replies to Pallab.
Pallab (Nokia) replies
Belen (Ericsson) objects approval at this meeting, support the study proposal in principle using baseline r03, SA2 needs to do more work during Q4/2021 on the overall Rel-18 content
Zhuoyi (China Telecom) replies to Nokia/Ericsson, provides r05 and asks whether 'Technically Endorsed' is ok
Susana (Vodafone) agrees with Belen (Ericsson) to not proceed to approval and continue work in Q4.
Pallab (Nokia) requests not to 'Technically Endorse' r05
==== 8.X, 9.X Final Deadline ====
Belen (Ericsson) provides detailed comments
Zhuoyi (China Telecom) replies to Ericsson and provide r06 for CC#5
Revised
9.1.3 S2-2106799 SID NEW Approval New SID: Study on enhancement of 5G AM Policy. China Telecom Rel-18 Revision of S2-2105587r04. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105753 DISCUSSION Discussion Discussion on ATSSS Enhancements for Rel-18 Lenovo, Motorola Mobility Revision of (Noted) S2-2104582 from S2-145E. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105606 SID NEW Approval New SID: Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. Lenovo, Motorola Mobility Revision of (Noted) S2-2104599 from S2-145E. r03 agreed. Revised to S2-2106800, merging S2-2106497 Susan (Huawei) provides comments.
Myungjune (LGE) provides comments.
Rainer (Nokia) comments.
Robert Olesen (Intelsat) comments.
Curt (Charter) comments.
Hualin(Huawei) provide comments.
Stefan (Ericsson) provides comments
Dieter (Deutsche Telekom) provides comments.
Apostolis (Lenovo) responds to Rainer (Nokia).
Omkar (CableLabs) responds to Stefan
Rainer (Nokia) replies.
DongYeon (Samsung) comments.
Apostolis (Lenovo) provides r01.
Xiaobo Yu (Alibaba) provides r02 and suggest to keep bullet 4.
Susan (Huawei) cannot accept objective 3) as in either r00 and r01.
Susan (Huawei) rephrases objective 3).
Curt (Charter) opposes dropping QUIC, and propose a revise obj 2 for this study.
Adi (Apple) objects to dropping QUIC (RFC 9000) from objective 3.
Myungjune (LGE) comments on r01.
Myungjune (LGE) replies to DongYeon (Samsung).
Dieter (Deutsche Telekom) asks question for clarification.
Chia-Lin (MediaTek) ask for the clarification and ask if the Obj.5 is not clear to everyone, it should be removed for the time being
Stefan (Ericsson) cannot agree to remove QUIC from obj.3 and agrees with Cia-Lin that obj5 is too unclear to be included right now
Susan (Huawei) responds to Adi (Apple).
Susan replies to Stefan (Ericsson) on obj.3.
Xiaobo Yu (Alibaba) supports to highlight traffic splitting and keep MP-QUIC in bullet 3.
Apostolis (Lenovo) objects to dropping QUIC (RFC 9000) from objective 3 and responds to Susan.
Apostolis (Lenovo) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) responds to Apostolis (Lenovo).
Hualin(Huawei) also think objective 5 should be removed.
Susan (Huawei) is ok with the texts proposed by Xiaobo Yu (Alibaba) for objective 3.
Susan (Huawei) objects to objective 3 as in r03.
Curt (Charter) provides clarifications on obj 5.
Xiaobo Yu (Alibaba) asks to consider the LS-2105979 for the issue of QUIC with MP extension.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106800 SID NEW Approval New SID: Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. Lenovo, Motorola Mobility - Revision of S2-2105606r03, merging S2-2106497. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106497 SID NEW Approval New SID: Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. Deutsche Telekom Rel-18 Merged into S2-2106800 Stefan (Ericsson) assumes that the discusssion on ATSSS rel-18 SID is taken on the 5345 document
Dieter (Deutsche Telekom) answers Stefan: You probably mean document 5606 - yes, discussion happens there and we still hope to get to a merged SID...
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
9.1.3 S2-2105979 LS OUT Approval [DRAFT] LS on progress of multi-path QUIC for ATSSS Vivo Noted Dario S. Tonesi (Qualcomm) asks question for clarification.
Stefan (Ericsson) has same question as Dario
Rainer (Nokia) agrees to Dario and Thomas.
Xiaobo Yu (Alibaba) provides responses to Dario (Qualcomm), Stefan (Ericsson) and Rainer (Nokia) .
Dieter (Deutsche Telekom) agrees with previous comments. The LS to IETF should not be send from this meeting.
Xiaobo Yu (Alibaba) replies to Dieter (DT).
==== 8.X, 9.X Revisions Deadline ====
Dario (Qualcomm) proposes to note this LS.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105610 SID NEW Approval New SID on Study on Passive Internet of Things (Passive IoT) for 5G Advanced. China Mobile, Spreadtrum Communications, Huawei, HiSilicon, China Telecom, China Unicom, CATT, Tencent, vivo Rel-18 Noted Guillaume (MediaTek Inc.) asks for clarification.
Sherry (Xiaomi) asks for clarification.
LaeYoung (LGE) asks some questions for clarification.
Chunhui(Spreadtrum) replies the comments from Guillaume, Sherry and LaeYoung.
Miguel (Qualcomm) questions what are the Stage 1 requirements to support these use scenarios, and believes there is a related Rel-19 Study proposal in SA1 related to this. Prefers this effort goes through proper channel of Stage 1 study first.
Sherry (Xiaomi) comments.
Hualin(Huawei) support the Study in R18 and replied to Miguel (Qualcomm).
Chunhui (Spreadtrum) replies Sherry(Xiaomi)'s comments and provides the revision(r02).
Hannu (Nokia) supports Miguel in thinking that this study would benefit from getting the requirements from SA1.
Chunhui(Spreadtrum) replies the comments from Hannu(Nokia) and Miguel(QC) that there is Rel-17 SA1 requirement 'Asset tracking' for this SID.
Aihua(China Mobile) replies to Hannu and Miguel.
Qian (Ericsson) provides comments and questions
Miguel (Qualcomm) asks Aihua(China Mobile) to be more specific on the SA1 work as asset tracking outcome does not seem to fit the objectives of this SID
Chunhui(Spreadtrum) replies the comments from Qian(Ericsson).
Chunhui (Spreadtrum) replies Miguel(Qualcomm) that SA1 asset tracking outcome can be applied to this SID and asks for technical comments.
Huan (Vivo) support the Study in R18.
Hannu (Nokia) shares the concerns of Miguel and Qian and considers it premature to start this study now.
Miguel (Qualcomm) checked the actual text in TS 22.261 and is still not convinced there are service requirements for passive IoT
Hualin(Huawei) replied and confirm support of the study in R18.
==== 8.X, 9.X Revisions Deadline ====
Chi (China Unicom) is supportive of starting the study of Passive IoT in R18.
Biao(China Telecom) supports to start Passive IoT study in R18.
Ming (CATT) agree with Chi (China Unicom), i.e. support starting the study of Passive IoT in R18.
Lars (Sony) ok with r02. Whether it goes into rel-18 depends on prioritization task in SA and RAN.
LaeYoung (LGE) would like to step back to understand service requirements, mobility model, communication model and QoS requirements for Passive IoT in order to figure out more clear and concrete objectives, thus proposes to NOTE this SID in this meeting.
Dieter (Deutsche Telekom) proposes postpone this SID to Rel19 and to start this work in SA1 first.
Hannu (Nokia) supports the proposals from Dieter and LaeYoung that it would be premature to decide on this SID in its present form. It should be noted or postponed.
Qian (Ericsson) share the view from other companies. Without clear requirements on what is needed/lacking and the dependency to the RAN study, it's premature to have agreement on this, thus we object to this study.
Miguel (Qualcomm) objects to this study proposal, as my concerns regarding lack of service requirements remain and RAN discussions are only speculative at the moment.
Chunhui(Spreadtrum) objects to Miguel (Qualcomm)'s objection since it is totally unreasonable and misleading other companies.
Chris (Vodafone) thinks that Passive IoT is an interesting area but feels that RAN study conclusions are needed before spend SA2 time on this.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105611 DISCUSSION Discussion Key Issue: Discussion on connected protocols in case of GEO SAT long delays . THALES Rel-18 Noted Jean-Yves (Thales) provides r01, adding companies co-sourcing the discussion paper.
Jean Yves (Thales) requests for comments
Hucheng (CATT) provides comments.
Jean Yves (Thales) provides comments.
Jean Yves (Thales) integrate the point in S2-2106296 r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105863 DISCUSSION Agreement ENS_Ph3: Human Readable Slice Names. Qualcomm Incorporated Noted Patrice (Huawei) assumes this document to be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105752 SID NEW Approval New SID: New SID on Network Slicing Phase 3. ZTE, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Alibaba, AT&T, CATT ,China Telecom, China Unicom, Convida Wireless LLC, Intel, InterDigital, Lenovo, Matrixx, Motorola Mobility NEC, NTT Docomo, OPPO, Sanechips, T-Mobile USA, Spreadtrum, Tencent, r07 agreed. Revised to S2-2106801 Stefano (Qualcomm) express supports for the work but provides questions, comments, and a revision.
Jinguo(ZTE) response and provide r01.
Gerry (VZ) supports FS_eNS_Ph3 and proposes to add texts in Justification and update the text Objective 5.
George (Ericsson) provide comments.
Antoine (Orange) generally supports the WID and comments on objectives 1, 2, 9 and 10 .
Jinguo(ZTE) thanks the support and provides r02
Patrice (Huawei) provides comments to the latest revision of the SID proposal, and may provide a draft revision later accordingly.
Stefano (Qualcomm) thanks Jinguo for r01.
Krisztian (Apple) asks Jinguo to add Apple as supporting company in the next revision.
Dieter (Deutsche Telekom) has concerns with most objectives and provides comments.
Alessio(Nokia) comments and can work wit r1 but r02 has some problems (like the UE provides the priority to the CN is a solution not a problem statement)
Peter Hedman (Ericsson) provides comments on r02
Patrice (Huawei) provides as promised a draft with some required changes to the study.
Patrice (Huawei) provides comments to r02 and suggested change for bullet 1
Xiaobo Yu (Alibaba) provides comments to r02 and suggested change for bullet 1
alessio(Nokia) cannot agree with this proposed revision by Huawei. proposes to use r01 by the convenor /editor .
Alessio(nokia) provides some comments in response to some comments
Jinguo(ZTE) provides r03
Antoine (Orange) still cannot agree with objective 1.
Alessio(Nokia) provides a comment and requests for change.
Jinguo(ZTE) provides r04.
Ashok (Samsung) responds to Peter Hedman (Ericsson)
alessio apologized but has one more comment, which he failed to express in previous message
Jinguo(ZTE) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Patrice (Huawei) thanks Jinguo for the great effort to improve the SID, however, there are still points that need to be corrected before it is acceptable (i.e. for the notes: I object to all versions so far, hoping to see an acceptable version before the end of the meeting).
Patrice (Huawei) has not seen any compelling evidence that the Earth is flat, nor that there is a problem with 'UE pest control' or that there is a necessity to start considering radio network topology in SA2. Therefore, Huawei cannot accept the SID revisions r00-r05.
Alessio(Nokia) believes that the comments by Huawei are speculative (not the text in Jinguo's revision!)... arguments like 'it is the 4th release we discuss slicing makes it look like it is immature' are not valid as we discuss several topics for all 3GPP releases but this means not they are immature, they just need some refinements from operations or service requirement standpoint. The fact Huawei says 'a UE connecting to multiple PLMNs simultaneously is not supported today so we cannot add an objective meeting a SA1 requirement' is odd as this would set a precedent that we can only add topics that are based on existing capabilities!
Alessio (Nokia) requests Huawei to use technical arguments and not analogies of dubious effectiveness in proving their arguments. We think the objectives in the SID are valid (with maybe the exception of one or two we can however fix when we discuss the KI)
Jinguo(ZTE) provides r06 and responds to Patrice(Huawei)
alessio(Nokia) comments r06 is not acceptable (object) as some of the 'request to be removed' subject to justification are untenable since the justification has been provided... multiple times. also some request have been ignored some implemented arbitrarily in r06. So to me we have to go back to r05 or R01/2. Also some comments like 'the operator has to accommodate all slices together so the disjoint slices case is an error case, and against the operator will'.
Gerry (Verizon) responds to Jinguo
Peter Hedman (Ericsson) provides reply
Alessio(Nokia) comments that some objectives maybe are not eventually progress to normative but to me it is impossible to conclude one way or another by consensus till we at least have the KI discussion.
Peter Hedman (Ericsson) We support the study as such, but we object approval at this meeting as there needs to be more work done to get the SID in a stable set of objectives that all can agree to; and in general SA2 needs to do more work during Q4/2021 on the overall Rel-18 content.
Patrice (Huawei) acknowledges the effort from the rapporteur (Jinguo, ZTE), but r06 (and all revisions before it) are unfortunately unacceptable (I object to 5752 and its revisions), although we do support the work on some objectives, and even to add informative improvements to our specifications to help proper deployments with network slicing.
Jinguo(ZTE) provides r07, mainly focus on objective 5.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106801 SID NEW Approval New SID: New SID on Network Slicing Phase 3. ZTE, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Alibaba, AT&T, CATT ,China Telecom, China Unicom, Convida Wireless LLC, Intel, InterDigital, Lenovo, Matrixx, Motorola Mobility NEC, NTT Docomo, OPPO, Sanechips, T-Mobile USA, Spreadtrum, Tencent, - Revision of S2-2105752r07. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105825 SID NEW Approval New SID: Study on enhanced support of Non-Public Networks phase 2. Ericsson, Futurewei, Convida Wireless, Charter, China Unicom, ETRI; Cisco, China Mobile, Lenovo, Motorola Mobility, Qualcomm, ZTE, Philips, Intel Rel-18 r05 agreed. Revised to S2-2106802 Hualin(Huawei) comments.
Saso (Intel) replies to Hualin.
Peter Hedman (Ericsson) provides r01
xiaowan (vivo) provides comments
Curt (Charter) comments
Omkar (CableLabs) supports inclusion of 'Support for non-3GPP access for SNPN' as an objective.
Rainer (Nokia) comments.
Guanzhou (InterDigital) supports the SID and comments on the content.
Jihoon (ETRI) comments.
Hualin(Huawei) have further comments.
Peter (Ericsson) provides replies and r02
Antoine (Orange) cannot accept objective 1; objective 4b is not clear.
Rainer (Nokia) replies.
Jihoon (ETRI) replies.
Walter (Philips) proposes to add NPN support for ProSe, eLCS and enh_EC
Chia-Lin (MediaTek) also for the clarification for eNPN_Ph2
Dieter (Deutsche Telekom) provides comments.
Hualin(Huawei) replied to Peter
Peter Hedman (Ericsson) provides r03
Patrice (Huawei) would like the requirement on 'equivalent SNPNs' to be further explicited, or removed.
Peter Hedman (Ericsson) provides replies
Walter (Philips) provides response to Peter and corrects the thread.
Jihoon (ETRI) provides further comments for clarification.
Fei (OPPO) comments.
Peter Hedman (Ericsson) provides r04 and comments
Antoine (Orange) cannot accept objective 1b; asks clarification on objective 4b.
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) objects to all versions.
Peter Hedman (Ericsson) provides r05 and comments
George (Ericsson) provides comments. I would like to get some time to explain the removed objective, and that it is not controversial, but given the lack of time, may be we can postpone approving the SID this meeting. Sorry Peter, U are still my buddy and colleague ??
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106802 SID NEW Approval New SID: Study on enhanced support of Non-Public Networks phase 2. Ericsson, Futurewei, Convida Wireless, Charter, China Unicom, ETRI; Cisco, China Mobile, Lenovo, Motorola Mobility, Qualcomm, ZTE, Philips, Intel Rel-18 Revision of S2-2105825r05. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105842 SID NEW Approval New SID on CIoT support in NTN. Qualcomm Incorporated Rel-18 Noted Jean Yves(Thales) proposes to include S2-2105842 as dedicated chapter in S2-2106296, in order to handle single R18 SID for NTN access
Chunhui(Spreadtrum) supports Jean Yves(Thales)'s proposal to include S2-2105842 as dedicated chapter in S2-2106296.
Haris (Qualcomm) proposes to NOTE S2-2105842
==== 8.X, 9.X Revisions Deadline ====
Chunhui(Spreadtrum) confirms with Guillaume (MediaTek) that no content in S2-2106274(R17 IoT NTN WID) is from S2-2105842(R18 SID). The clarification is in the S2-2106274 email discussion thread.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105855 SID NEW Approval New Study about AF control on 5GC groups . Nokia, Nokia Shanghai Bell Rel-18 Noted Sebastian (Qualcomm) comments
Dieter (Deutsche Telekom) agrees with comments provided by Sebastian and provides additional comments.
Dieter (Deutsche Telekom) proposes to merge 6067 and 5855.
Sang-Jun (Samsung) also proposes to merge 6067 and 5855.
Rainer (Nokia) replies and provides r01.
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) comments that the objectives in the SID are covered by 6322, thus the SID should be NOTED.
Dieter (Deutsche Telekom) requests author to confirm that this SID is merged or noted.
Rainer (Nokia) proposes to postpone 5855.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105860 SID NEW Approval New SID on Study of Further Architecture Enhancement for UAV and UAM. Qualcomm Incorporated r02 agreed. Revised to S2-2106803 Pallab (Nokia): comments and provides a draft revision
Tricci (OPPO) asked for clarifications from Nokia's proposed update to the SID
Pallab (Nokia): responds to Tricci (OPPO)
LaeYoung (LGE) provides comment on the objective added by Pallab (Nokia).
Pallab (Nokia): responds to LaeYoung (LGE)
Guanzhou (InterDigial) comments and provides a draft revision.
Shabnam (Ericsson) provides comments that Ericsson is supportive of the Study but have comments on revision proposal.
Pallab (Nokia): responds to Guanzhou (InterDigial)
Pallab (Nokia) clarifies to Shabnam (Ericsson) on the objective of monitoring.
Magnus O (Ericsson) provides comments
Guanzhou (InterDigial) responds to Pallab (Nokia).
Chunhui(Spreadtrum) questions what are the Stage1 R18 requirements of this SID, and believes there is a related Rel-19 Study proposal in SA1(S1-213086) related to this SID. Prefers this effort goes through proper channel of Stage1 study first.
Stefano (Qualcomm) clarifies this work is not related to the work of SA2 Rel.19, which has not been performed yet, but to satisfying requirements from SA1 Rel. 17 that have not been supported yet, and to study architectural enhancements left over from SA2 Rel. 17 work.
Stefano (Qualcomm) replies and provides R01.
DongYeon (Samsung) asks questions for clarification.
Pallab (Nokia) comments on R01.
Stefano (Qualcomm) replies and provides R02.
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) supports the study and r02 objectives, though would prefer, as commented before, less details that is somewhat soln oriented in the Justification.
Pallab (Nokia) thanks Stefano (Qualcomm) for r02 and supports the study and r02 objectives
Chunhui (Spreadtrum) objects to this SID since it has unclear requirements from neither 3GPP SA1 nor other formal forum/group's official LS.
Guanzhou (InterDigital) supports r02.
Stefano (Qualcomm) asks why one objective of the SID being of concern to Spedtrum leads the company to object to the whole SID, whose other objectives are clear and brought over from Rel. 17. Also, I suggest learning, since ACJA documents are published GSMA documents and thus public.
Shabnam (Ericsson) objects approval at this meeting, support the study proposal in principle (e.g. using baseline r01), SA2 needs to do more work during Q4/2021 on the overall Rel-18 content
Pallab (Nokia) echoes the voice from Stefano (Qualcomm). Most of the objectives are based on unfulfilled requirements from SA1. Also ACJA has been working in coordinating the aviation industry requirements with 3GPP and the ACJA documents are publicly available.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106803 SID NEW Approval New SID on Study of Further Architecture Enhancement for UAV and UAM. Qualcomm Incorporated - Revision of S2-2105860r02. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105955 SID NEW Approval New SID: Study on enhancement of 5G UE Policy. Intel, Qualcomm Incorporated Rel-18 r08 agreed. Revised to S2-2106804 Krisztian (Apple) provides r01 to reflect the discussion in the thread of S2-2105356. In this study, we should investigate how to support both standardized (e.g. Enterprise, Gaming, Video Streaming, etc.) and operator-specific traffic categories in the traffic descriptor of URSP.
Yusuke (KDDI) supports r01 provided by Apple. And adds procedural comment.
Changhong (Intel) thanks Yusuke for the procedural comment.
Magnus (Ericsson) comments.
Gerry (Verizon) also supports r01 provided by Apple and requests that Verizon UK Ltd be added as a supporting company to the SID proposal.
Changhong (Intel) replies to Magnus (Ericsson) comments.
Changhong (Intel) provides r02 and added Verizon as supporting company.
Pallab (Nokia) comments on r01.
Sherry (Xiaomi) replies to Pallab (Nokia).
Changhong (Intel) replies to Pallab.
Sherry (Xiaomi) provides the texts which defines the interaction between PCF-AM and PCF-SM.
Pallab (Nokia) responds to Changhong (Intel).
Yang (OPPO) provides comments to r02.
Changhong (Intel) responds to Pallab and provides r03 with deleting fourth bullet in objective.
Pallab (Nokia) comments and raises concerns with r03.
Yang (OPPO) provides some answer to Nokia's question.
Hong (Qualcomm) comments.
Sherry (Xiaomi) replies.
Hyunsook (LGE) suggests to add a note about coordination with Edge Computing.
Changhong (Intel) agrees with Hyunsook's suggestion.
Changhong (Intel) thanks Hong's answer.
Changhong (Intel) provides r04 and thanks for Samsung's support.
Dimitris (Lenovo) supports the SID requests an additional objective
Pallab (Nokia) responds Changhong (Intel) and Hong (Qualcomm).
Sherry (Xiaomi) comments.
Dimitris (Lenovo) responds to Sherry (Xiaomi)
Belen (Ericsson) comments
Belen (Ericsson) asks about r03
Changhong (Intel) responds to Dimitris.
Belen (Ericsson) comments on r03
Changhong (Intel) provides r05 and r06, asks to ignore r05, replies to Belen.
Pallab (Nokia) comments on r06. Can only accept objectives #4, #6 (reworded as proposed below) and #7
Yusuke (KDDI) provides comments.
Changhong (Intel) provides r07 by adding LG Electronics.
Changhong (Intel) provides r08 by adding Rakuten Mobile Inc.as supporting company.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) objects to r08 and all previous revisions unless:
- Objective #1 & #5 from r08 are removed and
- Objective #4 & #6 in r08 are reworded as proposed earlier.
Yang (OPPO) cannot accept to remove obj-1 and 5 since we see it as valuable objectives as explained before
Changhong (Intel) replies to Pallab and agrees to simply the objective #4 and #6 as suggested, asks for the technical reason of removing objective #1 and #5.
Pallab (Nokia) thanks Changhong (Intel) for agreeing to simply the objective #4 and #6 as suggested, also responds on #1 & #5
Belen (Ericsson) objects approval at this meeting, support the study proposal in principle using baseline r07/r08, SA2 needs to do more work during Q4/2021 on the overall Rel-18 content
Yang (OPPO) replies to Pallab (Nokia)
Changhong (Intel) thanks to Belen's cosigning and feels a big pity on the objection for approval at this meeting.
Laurent (Nokia): we would object if the number of TU(s) on this always contentious topic is not realistic (kind of 2 TU(s) per item)
==== 8.X, 9.X Final Deadline ====
Belen (Ericsson) comments on r08
Changhong (Intel) replies to Belen and Laurent.
Revised
9.1.3 S2-2106804 SID NEW Approval New SID: Study on enhancement of 5G UE Policy Intel, Qualcomm Incorporated, OPPO, ZTE, NTT Docomo, vivo, Telecom Italia, China Unicom, Huawei, HiSilicon, Vodafone, CATT, MediaTek, KPN, China Telecom, CMCC, KDDI, Xiaomi, Apple, Verizon UK Ltd, Samsung, Lenovo, Motorola Mobility, LG Electronics, Rakute Rel-18 Revision of S2-2105955r08. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2105974 SID NEW Approval New SID on 5G System Support for Group Communications for Verticals. Samsung, LG Uplus, SK Telecom, Sennheiser, KT Corp. Rel-18 Merged with S2-2106322 (noted). Noted Qian (Ericsson) provides comments and ask questions
Rainer (Nokia) comments.
Sang-Jun (Samsung) repies to Rainer (Nokia) and Qian (Ericsson).
Sebastian (Qualcomm) comments
Sang-Jun (Samsung) provides responses to Sebastian (Qualcomm)
Huan (Vivo) asks for clarifications
Sang-Jun (Samsung) replises to Huan (Vivo).
Sang-Jun (Samsung) informs that 5974 is merged with 6322 and 6067.
Sebastian (Qualcomm) objects to the WID
==== 8.X, 9.X Revisions Deadline ====
Sang-Jun (Samsung) reponses to Sebastian (Qualcomm).
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105980 DISCUSSION Discussion Discussion for Mobile Computing Power Network in 5GS China Telecomunication Corp. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105978 SID NEW Approval New SID on Mobile Computing Power Network in 5GS. China Telecom Noted Laurent (Nokia): Comments
Yifan (China Telecom) responds to Laurent.
Saso (Intel) seeks clarification.
Yifan (China Telecom) replies to Saso.
Shabnam (Ericsson) asks to understand what would be 3GPP/SA2 role.
Yifan (China Telecom) answers to Shabnam.
Vivian (vivo) provides comments and supports the study in SA2.
Chia-Lin (MediaTek) ask for the clarification
Yifan (China Telecom) replies to Chia-Lin.
Haris (Qualcomm) comments and proposes to note
Yifan (China Telecom) replies to Haris.
Saso (intel) agrees with Haris (Qualcomm); proposes to note
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) agrees with Intel and Qualcomm; proposes to note this SI.
Laurent (Nokia): agrees with Intel and Qualcomm and Ericsson and objects to any revision of this SID/Tdoc
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2105997 WID NEW Approval New WID on Study of Enhanced System enablers for Multi-USIM devices . Sony Rel-18 Noted Juan Zhang (Qualcomm) provides comments
Qian (Ericsson) provides comments and asks questions
Ouyang(Huawei) comments
Saso (Intel) seeks clarification
Lars (Sony) responds with clarifications.
Saso (Intel) seeks further clarification
Lars (Sony) responds to Saso
Juan Zhang (Qualcomm) seeks for clarification.
Lars (Sony) responds to Juan Zhang (Qualcomm)
Lars (Sony) provides r01
Yang (OPPO) comments to r01.
Lars (Sony) responds to Yang (OPPO)
Juan Zhang (Qualcomm) provides comments to r01
Lars (Sony responds to Juan Zhang (Qualcomm)
Jianning (Xiaomi) provides questions for clarification
Lars (Sony) responds to Jianning (Xiaomi)
Juan Zhang (Qualcomm) replies to Lars
Antoine (Orange) cannot agree with the first objective.
Lars (Sony) provides r02
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) objects to r00, r01 and r02.
Ouyang(Huawei) suggests to note this SID, due to the time division (TD) scheme requires RAN support first.
Lars (Sony) responds to Ouyang and ask whether Huawei asks to note all SID/WID that has RAN dependences in rel.18.
Juan Zhang (Qualcomm) also proposes to note this SID. There is no such requirement about simultaneously communication.
Jianning (Xiaomi) share the view with Juan(Qualcomm) also propose to Note this SID
Yang (OPPO) propose to note or postpone the SID
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106005 DISCUSSION Discussion RAN AI/ML analytics data connection to NWDAF. Qualcomm Incorporated Rel-18 Noted Wang Yuan (Huawei) provides comments.
Leo (Deutsche Telekom) provides comments.
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) replies to Yannick, Leo and Wang Yuan
Yannick (Nokia): Nokia replies to Qualcomm.
Juan Zhang (Qualcomm) replies to Yannick.
Paul (Ericsson) provides comments.
Chunhui(Spreadtrum) asks for clarifaction about the relationship between the proposal and O-RAN RIC(RAN Intelligent Controller).
Aihua(China Mobile) agrees generally that NWDAF could collect data or exchange analytics from RAN side.
Chris (Vodafone) supports Qualcomm.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106008 DISCUSSION Discussion Introduction of network based Sensing in 5G Advanced vivo,China Telecom,China Unicom Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106019 DISCUSSION Discussion Motivation for SID on 5GC autonomous operation Lenovo, Motorola Mobility Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106009 SID NEW Approval New SID on 5GC autonomous operation. Lenovo, Motorola Mobility Rel-18 Noted Wang Yuan (Huawei) provides comments.
Belen (Ericsson) provides comments
Yannick (Nokia): Nokia also sees this proposal targeting SA5, not SA2.
Leo (Deutsche Telekom) agrees with Nokia and Ericsson, this should be handled in SA5, not in SA2
Dimitris (Lenovo) responds and provides r01
Juan Zhang (Qualcomm) provides comments to r01.
Dimitris (Lenovo) responds to Juan (Qualcomm)
Belen (Ericsson) provides comments to r01
Aihua(China Mobile) provides comments.
Dimitris (Lenovo) provides r02
Dimitris (Lenovo) provides r03
Juan Zhang (Qualcomm) provides comments on r03.
Dimitris (Lenovo) responds to Juan (Qualcomm) and provides r04
==== 8.X, 9.X Revisions Deadline ====
Farooq (AT&T) asks a clarification question
Wang Yuan (Huawei) cannot accept r04 as it is and asks for further clarifications/modifications.
Dimitris (Lenovo) responds to Farooq (AT&T)
Dimitris (Lenovo) responds to Wang Yuan (Huawei)
Juan Zhang (Qualcomm) provides further comments
Belen (Ericsson) comments on r04, this is still on SA5 scope.
Belen (Ericsson) objects to all revisions.
Juan Zhang (Qualcomm) still think the objectives are not justified and the gap between eNA_ph3 is not clear, we proposed to postpone the SID in this meeting.
Wang Yuan (Huawei) agrees with the views from Ericsson and Qualcomm, and also think the objectives are not well justified, we suggest to postpone this SID in this meeting.
Leo (Deutsche Telekom) agrees with Ericsson, this is SA5 scope, and objects to all revisions of this SID.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106023 DISCUSSION Discussion New SID Proposal on 5G Harmonized Communication and Sensing service (HCS) Huawei, HiSilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106022 SID NEW Approval New SID: 5G Architecture enhancements for Harmonized Communication and Sensing service. Huawei, HiSilicon, vivo, CAICT, China Unicom, China Mobile, China Telecom, CATT, ZTE, OPPO Rel-18 Noted Wanqiang (Huawei) opens the thread to collect views for this new direction.
Leo (Deutsche Telekom) proposes to postpone the SID and wait for SA1 requirements in Rel-19.
Saso (Intel) comments.
Wanqiang (Huawei) responds.
Hong (Qualcomm) comments.
Xiaobo (vivo) provides further clarification.
Sherry (Xiaomi) clarifies about Xiaomi's proposal.
Wanqiang (Huawei) clarifies.
Aihua(China Mobile) suggests to try to find what we can do in R18.
Chi (China Unicom) provides comments and expresses support to this SID.
Alessio(Nokia) provides again the same comment that we support those that indicate we should first have clear use cases and requirements from SA1.
Leo (Deutsche Telekom) again requests to wait for Rel-19 requirements from SA1, and SA2 should do no work in Rel-18 on this topic.
Xiaobo(vivo) suggest also having some technical discussion to analyze whether/how to have the study in R18.
Jinguo(ZTE) express the support of this study
Biao (China Telecom) supports to trigger the this study in R18.
Hucheng (CATT) comments and also proposes to have a study on this topic.
Shabnam (Ericsson) shares similar view as Intel expressed as well as others and believe we should not start this in SA2 first.
Jing Zhang (CAICT) gives comments and prefer to trigger the study in SA2/R18.
Saso (Intel) provides further comments. Think that this work should be initiated in SA1 and RAN WGs.
Wanqiang (Huawei) provides feedback to Saso (Intel).
Saso (Intel) replies to Wanqiang.
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) share view with DT that this work should wait for SA1 requirements and potential Rel-19. Proposes to Note the SI.
Leo (Deutsche Telekom) objects to approve the SID, SA2 should wait for SA1 requirements. Proposes to Note the SI.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106066 DISCUSSION Discussion Work analytics on 5G capabilities for factories of the future requested by 5G-ACIA. Huawei, HiSilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106067 SID NEW Approval New SID: Study on enhancement of 5G CAPability EXPosure for Industrial Applications. Huawei, HiSilicon Rel-18 Merge with S2-2106322 (noted). Noted Joachim Walewski (Siemens) provides comments on this study item proposal.
Qianghua (Huawei) provides r01
Rainer (Nokia) comments.
Joachim Walewski (Siemens) replies to Qianghua's email from 9:48 CEST today.
Qianghua (Huawei) provides r02
Joachim Walewski (Siemens) thanks Qianghua (Huawei) for r02 and provides detailed feedback.
Qianghua (Huawei) replies
Joachim Walewski (Siemens) replies to Qianghua (Huawei) and provides r03.
Riccardo (NTT DOCOMO) comments
Joachim Walewski (Siemens) replies to Riccardo (NTT DOCOMO)
Sebastian (Qualcomm) comments
Dieter (Deutsche Telekom) provides comments and recommends to merge 6067 and 5855.
Qianghua (Huawei) replies and provides r04
Qianghua (Huawei) proposed to merge this into 6322 per offline discussion
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) comments that the objectives in the SID are covered by 6322, thus the SID should be NOTED.
Runze (Huawei) withdraws the comments because it is sent to wrong document.
Qianghua (Huawei) responses
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106068 SID NEW Approval New SID on user deployed devices in customer premises network . Apple Noted Marco (Huawei) ask clarification and provides comments.
Laurent (Nokia): asks clarification and provides comments.
Stefan (Ericsson) provides questions and comments
Sudeep (Apple) responds to comments from Marco (Huawei).
Sudeep (Apple) responds to comments from Stefan (Ericsson)
Sudeep (Apple) provides r01 and responds to comments from Laurent (Nokia).
Sudeep (Apple) provides r02.
Marco (Huawei) object to this SID.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to this SID (supports Marco)
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106072 DISCUSSION Discussion Discussion on Support of Satellite Backhaul in 5GS CATT Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106073 SID NEW Approval New SID on Study on Support of Satellite Backhauling in 5GS. CATT, Thales Rel-18 Noted Stefan (Ericsson) provides comments and questions on the objectives
Haris (Qualcomm) comments
Hucheng(CATT) replies to the comments from Qualcomm and Ericsson, and provides r01.
Jean Yves(Thales) provides r02, adding supporting companies.
Hannu (Nokia) is not convinced on the goals of this proposed WID, If any SA2 work is necessary, it should be aligned with RAN work.
Stefan (Ericsson) provides additional concerns
Hucheng(CATT) tries to address concerns from Ericsson by providing clarifications
Hucheng (CATT) clarifies to Hannu (Nokia) that the objectives are in scope of SA2, and then proposes to discuss technical part to decide whether any issue should go to RAN WGs
==== 8.X, 9.X Revisions Deadline ====
Haris (Qualcomm) objects to this SID (any revision) for the reason mentioned in my original email
Hucheng(CATT) clarifies to Haris again, and hopes Haris (Qualcomm) can clarify which part(s) is technically not acceptable.
Stefan (Ericsson) objects to any revision of this SID
Hucheng(CATT) points out that CATT has already replied the comments from Stefan (Ericsson), and no further technical comments were received, so would like to ask him to indicate technical issues/suggestions to move forward.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106086 SID NEW Approval New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2. Huawei Rel-18 Revision of (Noted) S2-2104312 from S2-145E. r05 agreed. Revised to S2-2106805 Zhenhua (vivo): provides r00+vivo in draft folder
Thomas (Nokia): provides r00+nokia in draft folder
Youngkyo(Samsung) provides comments
Zhenhua (vivo) responses
zhendong(ZTE), provides the comments
Robbie(Ericsson) provides comments
Zhenhua (vivo) responses to Zhendong (ZTE)
Robbie (Ericsson) comments
Thomas (Nokia) replies to Robbie
Miguel (Qualcomm) comments and provides r01
Jeffrey (Juniper) provides r02
Robbie(Ericsson) is supportive of the work and provides r00+Ericsson in Drafts folder
Jeffrey (Juniper) merged r02 addition to r00+Ericsson in Drafts folder
Miguel (Qualcomm) asks for justification and clarification of new proposed requirements on top of r00
Jarmo (KPN) would like to express support and suggest an additional enhancement objective covering support for efficient broadcast message delivery
Zhenhua (vivo) provide r00+vivo-r02 in draft folder
LiMeng (Huawei) provides r03 with considering the merger of the proposals.
Jarmo (KPN) agrees with r03 with minor adjustments
Jeffrey (Juniper) responds to LiMeng (Huawei)
Miguel (Qualcomm) comments the objective on RAN sharing is not actually RAN sharing based on LiMeng explanation, it's more like service sharing.
LiMeng (Huawei) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Robbie (Ericsson) supports this SID.
James Hu (AT&T) supports this SID.
LaeYoung (LGE) asks some questions for clarification.
Robbie (Ericsson) clarifies to LaeYoung (LGE) and Thomas (Nokia)
LaeYoung (LGE) responds to Robbie (Ericsson).
Robbie (Ericsson) responds to LaeYoung (LGE).
LiMeng (Huawei) provides r05
LaeYoung (LGE) provides comment on r05.
Miguel (Qualcomm) objects to this SID proposal up to latest revisions
LiMeng (Huawei) provides r06 and clarifies.
LaeYoung (LGE) replies to LiMeng (Huawei).
Robbie (Ericsson) objects to approval of this SID at this meeting, supports the study in principle. In our view more time needs to be spent in Q4/21 on the overall Rel-18 content.
Ihab Guirguis (FirstNet) Please add FirstNet as a supporting company
==== 8.X, 9.X Final Deadline ====
James Hu (AT&T) provide a comment: Need to change ATT to AT&T.
Revised
9.1.3 S2-2106805 SID NEW Approval New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2. Huawei Rel-18 Revision of S2-2106086r05. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106099 SID NEW Approval New SID on Study on Proximity based Services in 5GS - Phase 2. CATT r10 agreed. Revised to S2-2106806, merging S2-2105448 Tricci (OPPO) proposed to move the discussion for this SID S2-2106099 to the email thread S2-2105448 in order to discuss the merge of the two SIDs. Thanks.
Deng Qiang (CATT) provides r01 that merged S2-2105448.
LaeYoung (LGE) provides updated version on top of r01 (i.e. 6099r01+LGE) in DRAFTS folder.
Sherry (Xiaomi) comments.
LaeYoung (LGE) provides comment.
James Hu (AT&T) supports the merger of the two SID proposals and provides further comments.
Tricci (OPPO) applauses LaeYoung (LG) and Sherry (Xiaomi) for their kind intentions and efforts to try to help moving things forward and would like to propose to have a fresh start on the real technical discussions over the email thread of S2-2105448.
Zhenhua (vivo) comments.
Deng Qiang (CATT) thanks people's effort to make progress and provides r02.
Changhong (Intel) comments and proposes to use this paper as base.
Steve (Huawei) comments on the contents and the additions since submission.
LaeYoung (LGE) responds to Steve (Huawei).
Zhang (Ericsson) provides comments
Deng Qiang (CATT) provides clarifications and r03.
Lars (Sony) try to clarify the PWS part.
Fei (OPPO) comments.
Guillaume (MediaTek) asks for clarification.
Dimitris (Lenovo) asks for clarifications
Ihab Guirguis (FirstNet) Please add FirstNet and a supporter for the merged SID.
Hannu (Nokia) provides r03-Nokia and asks questions
Tricci (OPPO) thanks Deng Qiang (CATT) for his initiative to provide the draft merged proposal. OPPO provides the updated merge proposal r04 as the way forward.
James Hu (AT&T) support the merged SID proposal.
Zhenhua (vivo) ask for clarification.
Zhenhua (vivo) response to Fei (OPPO), Hannu (OPPO) that asked in 5448 thread considering it is merged in 6099.
Fei (OPPO) responds to Hannu (Nokia)
Deng Qiang (CATT) thanks the comments and support, and provides r05.
Steve (Huawei) comments on PWS
Mehrdad (Samsung) comments based on r05 and requests CATT/OPPO to add Samsung as a supporting company to the merged SID.
LaeYoung (LGE) provides comment on power consumption optimization/efficiency aspect.
Fei (OPPO) responds to Mehrdad (Samsung).
Hong (Qualcomm) provide comments on r05.
Dimitris (Lenovo) comments
Walter (Philips) comments and proposes to reinstate some statements about IoT support
Fei (OPPO) responds to Dimitrios (Lenovo) and Hong (Qualcomm)
Zhang (Ericsson) share views as Steve (Huawei)
Deng Qiang (CATT) thanks the good discussion and provides r06.
Hannu (Nokia) makes two further proposals on top of r06.
Mehrdad (Samsung) comments on r06.
Deng Qiang (CATT) provides r07.
Wen (vivo) comments.
Wen (vivo) comments and hopes we can consider power saving.
Mehrdad (Samsung) comments on r07
Lars (Sony) comments and don't agree on r07
Fei (OPPO) responds to Dimitris (Lenovo)
Walter (Philips) disagrees with r07
Mehrdad (Samsung) requests clarification in next revision.
Jianning (Xiaomi) proposes to consider the ProSe supporting for SNPN case
Lars (Sony) asks Jianning (Xiaomi) a question
Dimitris (Lenovo) responds to Fei (Oppo)
Walter (Philips) responds to Jianning (Xiaomi) and Lars (Sony)
Lars (Sony) thanks Walter for the pointer
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) provides r08.
Lars (Sony) provides wording proposal.
Wen (vivo) responds on Deng Qiang (CATT).
Lars (Sony) just to be clear we can't accept r08
Deng Qiang comment on Lars (Sony) wording proposal.
Lars (Sony) responds to Deng Qiang.
Fei (OPPO) responds to Lars (Sony)
Deng Qiang (CATT) provides r10.
Lars (Sony) responds to Deng Qiang (CATT)
Hannu (Nokia) prefers SID with 2a and 2b removed.
Walter (Philips) responds to Deng Qiang
Jianning (Xiaomi) replies
Zhang (Ericsson) objects to approval of this SID at this meeting, supports the study in principle. In our view more time needs to be spent in Q4/21 on the overall Rel-18 content.
==== 8.X, 9.X Final Deadline ====
Deng Qiang (CATT) provides r11 in CC#5 folder.
Revised
9.1.3 S2-2106806 SID NEW Approval New SID on Study on Proximity based Services in 5GS - Phase 2. CATT - Revision of S2-2106099r10, merging S2-2105448. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106126 SID NEW Approval New SID on Just-in-time communication . TOYOTA MOTOR CORPORATION Rel-18 Merged into S2-2106797 Wang Yuan (Huawei) asks questions for clarification.
Yang (OPPO) supports the intension of the SID and believe the objective can be clearer by some wording improvement
Xiao (TMC) request to Yuan.
Jianning (Xiaomi) provides questions for clarification
Xiao (TMC) answers to Jianning's questions.
Sherry (Xiaomi) comments.
Xiao (TMC) responds to Sherry.
Shabnam (Ericsson) questions if this proposal is not already fulfilled within network automation work?
Pallab (Nokia) shares the same view as Ericsson and requests Xiao (TMC) to clarify the problem statement.
Tricci (OPPO) asks for clarification from Pallab (Nokia) on Just-in-time BDT policy renegotiation.
Pallab (Nokia) responds to Tricci (Oppo).
Xiao (TMC) responds to Shabnam and Pallab.
Shabnam (Ericsson) provides further comments.
==== 8.X, 9.X Revisions Deadline ====
Yang (OPPO) provides some explanation and interpretation about Toyota's requirement and also suggest to merge it into 5GAI/ML SID (S2-215450) since 5G/AI/ML SID also addressed some similar things.
Xiao (TMC) responds to Shabnam and Yang. We agree to merge this SID into 5GAI/ML SID (S2-215450) and suggest to note this contribution (S2-2106126).
==== 8.X, 9.X Final Deadline ====
Merged
9.1.3 S2-2106130 SID NEW Approval New Study on enhancement of support for Indirect Communications between Vertical Network and Public Network. China Telecom Rel-18 r04 agreed. Revised to S2-2106807 Yubing (China Telecom) provides r01.
Rainer (Nokia) comments.
Saso (Intel) shares the views from Rainer (Nokia).
Yubing (China Telecom) responds.
Saso (Intel) comments.
Hualin(Huawei) support the SID proposal in SA2.
Rainer (Nokia) replies to Hualin (Huawei).
Tyler Hawbaker (OTD) comments.
Hualin(Huawei) replied to Rainer (Nokia).
Saso (Intel) asks Yubing (China Telecom) to provide new revision.
Qian (Ericsson) provides comments.
Amanda ( Futurewei ) asks for clarification on vertical network.
Yubing (China Telecom) replies to Saso (intel), Qian (Ericsson), Amanda (Futurewei) and provides r02 .
Dieter (Deutsche Telekom) provides comments and asks question for clarification.
Yubing (China Telecon) responds and provides r03
Yubing (China Telecon) update the link of r03
Peter Hedman (Ericsson) provides comments
Yubing (China Telecom) responds and provides r04
==== 8.X, 9.X Revisions Deadline ====
Haris (Qualcomm) comments and proposes to postpone
Dieter (Deutsche Telekom) agrees with previous commenters and also proposes to postpone.
Yubing(China Telecom) responds and provide further clarification.
Qian (Ericsson) comments that it seems there are still different views on the scenarios and use cases, even though we consider some of the aspects can be looked into, thus we consider it's premature to agree the study in this meeting and propose also to postpone.
Yubing(China Telecom) responds.
==== 8.X, 9.X Final Deadline ====
Yubing(China Telecom) provide r05 in CC#5 folder.
Yubing(China Telecom) provide r06 in CC#5 folder.
Revised
9.1.3 S2-2106807 SID NEW Approval New Study on enhancement of support for Indirect Communications between Vertical Network and Public Network. China Telecom Rel-18 Revision of S2-2106130r04. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106144 DISCUSSION Discussion The Discussion on the motivation of Passive IoT China Mobile M2M Company Ltd. Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106147 SID NEW Information Study on Enablers for Network Automation for 5G - phase 3. China Mobile, vivo Rel-18 Revision of (Noted) S2-2104231 from S2-145E. r06 agreed. Revised to S2-2106808 Dimitris (Lenovo) comments
Aihua (China Mobile) replies to the comments raised by Lenovo.
Antoine (Orange) replies to Dimitris.
Belen (Ericsson) asks Orange a question on the DP.
Juan Zhang (Qualcomm) provides comments to the SID
Xiaobo(vivo) propose to first focus on technical discussion to get converged and then we can discuss to study which objective in which SID.
Belen (Ericsson) provides comments to SID.
Leo (Deutsche Telekom) provides comments to SID and asks for clarification.
Peretz (Spirent) provides a comment regarding the prospect of a new NWDAF architecture.
Aoken (Rakuten Mobile) provides a comment and ask clarification.
Aihua (China Mobile) clarifies and provides r01.
Antoine (Orange) replies to Belen.
Juan Zhang (Qualcomm) provides comments to r01.
Xiaobo(vivo) thanks the support and provide clarification.
Xiaobo(vivo) responds to Feder(spirent).
Malla (NTT DOCOMO) replies to Belen.
Megha(Intel) provides a few comments on the SID
Peretz (Spirent) provides a follow up comment as it seems r01 didn't address the comments.
Peretz (Spirent) is asking Uri to clarify.
Xiaobo(vivo) responds to Feder(spirent)/ Aoken(Rakuten Mobile)/Megha(Intel).
Uri (Oracle) provides comments on SID.
Malla (NTT DOCOMO) provides comments on SID.
Belen (Ericsson) asks Malla for clarifications
Yannick (Nokia): Nokia provides comments to eNA_Ph3 SID proposal.
Xiaobo(vivo) responds to Malla (NTT DOCOMO) and Juan(QUALCOMM) and provide r03 to address the comments.
Xiaobo(vivo) responds to Belen(Ericsson).
Megha(Intel) provides a few comments on r03
Yang (OPPO) provides comments on r03
David (Samsung) provides comments on r03 of the SID.
Peretz (Spirent) provides a comment.
Peretz (Spirent) also supports: Study interaction between NWDAF and MDAS/MDAF for data collection and analytics
Xiaobo (vivo) provides r04 to address comments from Yannick(Nokia), David(Samsung), Yang(OPPO), Feder(Spirent) and Megha(intel).
Xiaobo(vivo) responds to Leo(DT).
Zhuoyi (China Telecom) provides comments.
Belen (Ericsson) provides comments to r04.
Yang (OPPO) comments it is inappropriate to add the new bullet.
Antoine (Orange) replies to Belen on overly sensitive actions and conflictual loops.
Juan Zhang (Qualcomm) provides comments to r04.
Aihua(China Mobile) replies to Yang.
Aihua (China Mobile) replies.
Xiaobo(vivo) responds to Belen (Ericsson)/Zhuoyi(China Telecom) provides r05.
Belen (Ericsson) replies to Vivo
Aihua(China Mobile) responds to Belen (Ericsson) on Objective 2a.
David (Samsung) provides further comments
Yannick (Nokia): Nokia replies on the ADRF aspects.
Yannick (Nokia): Nokia concurs with Samsung, objective 5 for NWDAF deployment options should rather be removed.
Juan Zhang (Qualcomm) replies to Yannick
Juan Zhang (Qualcomm) replies to Aihua and further comments to r05
Yannick (Nokia): Nokia comments on r05.
==== 8.X, 9.X Revisions Deadline ====
Xiaobo (vivo) replies to Juan(QC) and will provide new revision to address Juan's comments.
Aihua(CMCC) replies to Belen.
Zhuoyi (China Telecom) replies to Belen's concern on RSPF.
Yang (OPPO) replies to Aihua.
Xiaobo (vivo) provides r05 to address comments from Yannick(Nokia), Belen(Ericsson), Zhuoyi(China Telecom) and Juan(QC).
Belen (Ericsson) replies to CMCC and provides further comments on r05.
Juan Zhang (QC) has a general question that why are several independent new bullets added in every update version?
Juan Zhang (QC) has comments to r05
Juan Zhang (QC) provides comments to r06
Yannick (Nokia): Nokia comments on r06 and believes more time is needed to stabilize contents for the SID and the different objectives (including newly added ones) and avoid overlap with other SID (e.g. eLCS_Ph3).
Belen (Ericsson) objects approval at this meeting, support the study proposal in principle, although more work on r06 is needed.
SA2 needs to do more work during Q4/2021 on the overall Rel-18 content
Leo (Deutsche Telekom) supports the SID but agrees, more time is needed to fine-tune the text. Proposal to postpone the SID to the next SA2 meeting.
Susana (Vodafone) supports the work but objects to approval at this meeting as more discussion is needed in Q4.
Juan Zhang (Qualcomm) thanks Xiaobo and Aihua for the progress in these two weeks, but we think more times are needed to stable the objectives, propose to postpone this SID in this meeting and give people more time for coordination.
Xiaobo (vivo) agree more time needed to refine the text and thanks all for the contribution and effort.
==== 8.X, 9.X Final Deadline ====
Aihua(CMCC) proposes to continue work and try to technically endorse this SID.
Revised
9.1.3 S2-2106808 SID NEW Information Study on Enablers for Network Automation for 5G - phase 3. China Mobile, vivo Rel-18 Revision of S2-2106147r06. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106149 SID NEW Approval New SID on Enhancement to the 5GC LoCation Services Phase 3. CATT, Huawei Rel-18 Revision of (Noted) S2-2103834 from S2-145E. r06 agreed. Revised to S2-2106809 LaeYoung (LGE) provides comment.
Leo (Deutsche Telekom) supports the SID and provides comment.
Ming (CATT) thanks LaeYoung and Leo firstly, then provides answers and the r01.
Åke (Ericsson) Provides comments
Stephen (Qualcomm) provides comments on the r01
Ming (CATT) responses to Åke (Ericsson), and provide r02.
Cai Simon (Nokia) provides comments
Åke (Ericsson) supports the work proposed but believes some changes are required as commented below.
Chia-Lin (MediaTek) prefers the original text on the bullet not the revised text in r01 and r02 and provides some comments on SID
Åke (Ericsson) Responds to Chia-Lin and propose objective wording.
Tyler (OTD) provides comment on PRU objective wording, supports Ericsson proposal.
Stephen (Qualcomm) comments on the r03
Åke (Ericsson) comment needed modifications to r03
Ming (CATT) thanks James (AT&T) support, responses to Stephen (Qualcomm), and provides the r04.
Ming (CATT) response to Åke (Ericsson).
David (Samsung) comments on this SID.
Åke (Ericsson) comment needed modifications to r04
Runze (Huawei) asks a question to Ake.
Åke (Ericsson) responds to Runze.
Cai Simon (Nokia) objects to the removal of leftover issues
Ming (CATT) responses to David (Samsung), and uploaded r05.
Ming responses to Åke (Ericsson).
Ming (CATT) responses to Cai Simon (Nokia).
Cai Simon (Nokia) supports r05, r03, not r04
Åke (Ericsson) responds to Ming: Objective I is acceptable without sub-bullets.
==== 8.X, 9.X Revisions Deadline ====
Ming (CATT) responds to Åke (Ericsson): will remove sub-bullets of Objective I.
Stephen (Qualcomm) cannot agree any version or revision of this SID
Runze (Huawei) replies to Stephen and suggest to withdraw the objection.
Ming (CATT) responds to Stephen (Qualcomm), and suggests to approve R06, which was uploaded in draft folder.
Åke (Ericsson) object to r00 to r06.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106809 SID NEW Approval New SID on Enhancement to the 5GC LoCation Services Phase 3. CATT, Huawei Rel-18 Revision of S2-2106149r06. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106192 DISCUSSION Information Discussion on support for indirect communications between vertical network and public network. China Telecom Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106195 DISCUSSION Information New SID on Enhancements on High Data Rate and Low Latency Services. Tencent Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106196 SID NEW Approval New SID on Enhancements on High Data Rate and Low Latency Services . Tencent, Oracle, Spreadtrum, NEC Rel-18 Revision of (Noted) S2-2103940 from S2-145E. Merged into S2-2106810 Dan (China Mobile) suggest that this SID can be merged into S2-2106284 and let's focus discussion on S2-2106284
Chunshan (Tencent) does not agree to merge this into S2-2106284.
Hui(Huawei) supports to merge this into S2-2106284.
Youngkyo(Samsung) would support Tencent's SID proposal.
Chunshan(Tencent) provides r01.
Chunshan(Tencent) provides r02 to add more support companies.
LaeYoung (LGE) provides r02+LGE in DRAFTS folder.
Chunshan (Tencent) provides r03.
Chunshan (Tencent) provides r04 to add BT as support company.
Guillaume (MediaTek) provides comments
Chunshan (Tencent) responses to Guillaume (MediaTek) .
Devaki (Nokia) comments that we are supportive of enh. for XR services but also prefer a single SID for media/XR services.
Chunshan (Tencent) provides r05.
Dieter (Deutsche Telekom) that Deutsche Telekom is supportive of enhancements for XR services but prefers either a single (merged) SID for media/XR services, or if not possible clear separate independent objectives between 6196 and S2-2106284.
Jarmo (KPN) will also support a merged SID taking S2-2106284 as baseline due to its additional 'multi-modality' service objective.
Farooq (AT&T) proposes a way forward for S2-2106196 and S2-2106284
Chunshan(Tencent) respond to Farooq(AT&T), Jarmo (KPN), Dieter (Deutsche Telekom), Devaki (Nokia) and also provide comments on way forward.
Chunshan(Tencent) provides r06.
Dario (Qualcomm) provides comments and proposed additional text for r05.
Chunshan (Tencent) provides r07 to reflect Dario (Qualcomm) comments.
Dario (Qualcomm) provides r07-Qualcomm in the draft folder
==== 8.X, 9.X Revisions Deadline ====
Chunshan (Tencent) provides r09.
Chunshan (Tencent) points out that the r09 has implement QC proposed merged version. It is proposed 6196r09 to be selected as the baseline for merging the 6196 and 8284.
Paul (Ericsson) objects to this SID in all revisions and propose to consider this merged into 6284.
Chunshan (Tencent) questions to Paul (Ericsson)'s objection.
Hui (Huawei) objects r09 and proposes to continue with S2-2106284.
Dan(China Mobile) objects r00- r09 (all revision)and proposes to continue with S2-2106284.
==== 8.X, 9.X Final Deadline ====
Merged
9.1.3 S2-2106238 SID NEW Approval New SID for FS_5WWC_Ph2. Huawei, HiSilicon, China Unicom, China Telecom Rel-18 WITHDRAWN Marco (Huawei) withdraws the document and point out that only the SID proposal in S2-2106240 has to be considered for any further discussion.
Curt (Charter) asks why we don't consider the other 5WWC SID in xx5345? I think both SIDs need to be merged so we can discuss one common SID in the same thread.
Laurent (Nokia): objects to any revision of this SID
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Withdrawn
9.1.3 S2-2106255 SID NEW Approval New SID on Enhancement of support for Edge Computing in 5G Core network - phase 2. Huawei, HiSilicon, Alibaba, China Unicom, Convida Wireless, Intel, Toyota, vivo Rel-18 Revision of (Noted) S2-2104498 from S2-145E. r06 agreed. Revised to S2-2106812, merging S2-2106397 Hui (Huawei) provides r01.
Shubhranshu (Nokia) proposes to merge this paper into S2-2106397
Hui (Huawei) suggests to take this paper as baseline to discuss the technical issues firstly.
Mario (Telecom Italia) suggests to merge S2-2106255 and S2-2106397.
Farooq (AT&T) supports merger of the two proposals and comments further
Serge (T-Mobile USA) supports merger of the two proposals and comments further
Shubhranshu (Nokia) responds
Hui (Huawei) responses to Farooq.
Hui (Huawei) responses to Serge.
Patrice (Huawei) provides update r02.
Dario (Qualcomm) asks questions about network exposure and PSA/EAS relocation influence
Jeffrey (Juniper) provides r03 for a new objective.
Shubhranshu (Nokia) asks for clarification
Magnus (Ericsson) comments and suggest a revision
Jeffrey (Juniper) responds to Shubhranshu (Nokia)
Hui(Huawei) responds to Jeffery.
Farooq (AT&T) asks about progress on merger of two proposals (255 and 397) and proposes a way forward
Shubhranshu (Nokia) proposes to merge S2-2106397 and S2-2106255, and provides S2-2106397r02
Patrice (Huawei) replies to some comments.
Jeffrey (Juniper) replies to Patrice and Hui (Huawei).
Hyunsook (LGE) asks for the clarification on Ericsson's update.
Magnus (Ericsson) answers
Tingfang Tang (Lenovo) supports the work on enhancement of support of edge computing work within R18.
Patrice (Huawei) answers comments and provides r04.
==== 8.X, 9.X Revisions Deadline ====
Jeffrey (Juniper) responds to Patrice (Huawei) and provides r05.
Magnus (Ericsson) objects to this SID at this meeting, we are positive to an EC SID more work is needed to consolidate and stabilize the objectives
Patrice (Huawei) comments that to reopen the conclusion of Rel-17 would require the broad consensus from SA2, and prefers not to add the objective for now.
Shubhranshu (Nokia) proposes way forward and suggests update to r04
Patrice (Huawei) provdes a draft r06 in the revision folder
Patrice (Huawei) is of course saddened to see such objection, and would be happy if Magnus reconsiders as this provides a good basis for discussion already in September, which of course can and will be refined in Q4.
==== 8.X, 9.X Final Deadline ====
Shubhranshu (Nokia) proposes to take r07 as final version
Revised
9.1.3 S2-2106812 SID NEW Approval New SID on Enhancement of support for Edge Computing in 5G Core network - phase 2. Huawei, HiSilicon, Alibaba, China Unicom, Convida Wireless, Intel, Toyota, vivo Rel-18 Revision of S2-2106255r06, merging S2-2106397. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106284 SID NEW Approval New SID: Study on architecture enhancement for tactile and media services China Mobile, Huawei, Hisilicon, Xiaomi Rel-18 r12 agreed. Revised to S2-2106810, merging S2-2106196 Dan(China Mobile) provides r01
Chunshan (Tencent) suggests this SID be merged into S2-2106196 and let's focus discussion on S2-2106196.
Dan (China Mobile) do not agree to merge this into S2-2106197.
Hui (Huawei) supports to take S2-2106284 as baseline for media service SID discussion
Chunshan (Tencent) responses to Dan (China Mobile) and think the comments don't make sense.
Youngkyo(Samsung) supports Chunshan(Tencent)'s view.
LaeYoung (LGE) has similar view with Youngkyo (Samsung) and Chunshan (Tencent).
Dan(China Mobile) reply to LaeYoung(LGE) and Youngkyo(Samsung) comment
Sherry(Xiaomi) comments.
Lars (Sony) ask a question and seek clarification on the objectives
Dan (China Mobile) reply to Lars(Sony) question and provide a suggestion for update
Lars(Sony) reply to Dan (China Mobile)
Dan(China Mobile) reply to Lars (Sony)
xiaowan (vivo) support to study both TACMM and XR together, and propose leave TACMM related objective open in this meeting
Guillaume (MediaTek Inc.) provides comments.
Dan (China Mobile) reply to Guillaume
Shabnam (Ericsson) provides commented version of revision proposal in Drafts folder, Ericsson is supportive of the study and agrees on the merger of 6196 into this one.
Sherry (Xiaomi) comments.
Dan (China Mobile) provides r02
Chunshan (Tencent) provides some comments.
Dan(China Mobile) provides some reply.
Chunshan (Tencent) responses to Dan (China Mobile).
Dan(China Mobile) responses to Chunshan
Dieter (Deutsche Telekom) that we are supportive of enhancements for XR services but prefers either a single (merged) SID for media/XR services, or if not possible clear separate independent objectives between 6196 and S2-2106284.
Jarmo (KPN) will also support a merged SID taking S2-2106284 as baseline due to its additional 'multi-modality' service objective.
Chunshan (Tencent) provides some comments on the bullet of multiple flows per UE.
Dan(China Mobile) provide r05,please check this version.
Dan(China Mobile) reply to Dieter
Dan(China Mobile) provide r06 to reflect technical discussion
Dan(China Mobile) provide r07 to reflect technical discussion
Chunshan(Tencent) respond to Farooq(AT&T), Jarmo (KPN), Dieter (Deutsche Telekom), Devaki (Nokia) and also provide comments on way forward.
Dieter (Deutsche Telekom) comments on way forward.
Dan (China Mobile) provide r08 to reflect technical discussion
Hui (Huawei) responds to Chunshan and suggest to focus on technical and way forward discussion.
Hui (Huawei) responses to Dieter.
Dan (China Mobile) response to Chunshan that r08 considering your comment to clarify the sentences
Chunshan (Tencent) response to Dan (China Mobile).
Dario (Qualcomm) asks questions and is not supportive of r08
Dan (China Mobile) reply to Dario
Hui (Huawei) responses to Dario.
Hui(Huawei) suggests we stop the discussion on these issues.
Dario (Qualcomm) provides r08-Qualcomm in the draft folder
Dan(China Mobile) provide r09 to reflect discussion
Dan (China Mobile) provides r10 based on Dario's merged version
==== 8.X, 9.X Revisions Deadline ====
Chunshan (Tencent) cannot accept r10. Because in r10 uploaded, what Dario has added into 6284 from 6196 has been removed. In this sense, r10 is missing some content of 6196 thus is not an acceptable merge. Also think r10 is still not stable.
Dan (China Mobile) thanks for Farooq's support
Farooq (AT&T) requests that AT&T be added to the list of supporting companies when the document gets updated.
Hui (Huawei) responses.
Dan(China Mobile) provide r11 to remove change over change.
Chunshan (Tencent) responds and suggests to use 6196r09 as baseline.
Chunshan (Tencent) object r11 as the problem of r10 is not solved.
Hui (Huawei) explains why some texts are proposed to remove to avoid duplication.
Hui (Huawei) responses to Chunshan.
Dan(China Mobile) response to Chunshan
Chunshan (Tencent) responses to Hui (Huawei) and Dan (China Mobile).
Dan (China Mobile) responses to Chunshan
Dan (China Mobile) provide r12
Chunshan (Tencent) objects all the revisions (including r10/11/12), and still proposes to use the 6196r09 as baseline.
==== 8.X, 9.X Final Deadline ====
Dan(China Mobile) proposes to continue work and try to technically endorse this SID.
Hui(Huawei) proposes to continue work and try to technically endorse this SID.
Dan(China Mobile) provide r14 with TUs update
Dan(China Mobile) provides r15 in CC#5 folder with adding co-source company and supporting company
Revised
9.1.3 S2-2106810 SID NEW Approval New SID: Study on architecture enhancement for tactile and media services . China Mobile, Huawei, Hisilicon, Xiaomi Rel-18 Revision of S2-2106284r12, merging S2-2106196. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106286 SID NEW Information New SID: Study on UPF enhancement for control and SBA . China Mobile, AT&T, Vodafone, CATT, Tencent, Deutsche Telekom, SK Telecom, Sandvine Rel-18 Revision of (Noted) S2-2104357 from S2-145E. r05 agreed. Revised to S2-2106811 Laurent (Nokia): Comments
Fenqin (Huawei): Comments
Saso (Intel) comments
Stefan (Ericsson) comments
Laurent (Nokia): answers
Baruch Pinto (Allot): question to Laurent
Dan (China Mobile) answers some comment
Ellen (Intel): ask question to Laurent for clarification
Gerry (Verizon) supports the SID proposal and requests that Verizon UK Ltd be added as a supporting company.
Dan (China Mobile) thanks for Gerry's support
Fenqin (Huawei) comment
==== 8.X, 9.X Revisions Deadline ====
Michael Brown (Microsoft)provides comment.
Revision 6 introduces architectural inconsistencies, specifically for SBA integration
SCP support:
· N4 signaling will not be subject to the architectural benefits available with the SCP described in TS 23.501 section 6.2.19
Security: Multiple methods for securing the interface UPF interfaces
· TLS for the proposed exposure service(s
· IPSEC for existing N4 interface
· Service Authorization: OAUTH2.0 applies only to the proposed exposure service(s)
The study should include providing service-based equivalency for existing N4 procedures.
Dan(China Mobile) reply to Michael's comment
Stefan (Ericsson) objects to this SID at this meeting. OK with the study proposal in principle (changes still needed), but SA2 needs to do more work during Q4-2021 on the overall Rel-18 content
Saso (intel) supports the proposal from Michael Brown (Microsoft) for re-instating the objective on a service-based equivalent for the existing N4 Node and Session related procedures
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106811 SID NEW Information New SID: Study on UPF enhancement for control and SBA . China Mobile, AT&T, Vodafone, CATT, Tencent, Deutsche Telekom, SK Telecom, Sandvine Rel-18 Revision of S2-2106286r05. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106300 SID NEW Approval Study on Integration of satellite components in the 5G architecture Phase II THALES, XIAOMI Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106296 SID NEW Approval New SID on Study on Integration of satellite components in the 5G architecture Phase II. THALES, XIAOMI Rel-18 Noted Jean Yves(Thales) provides r01 adding supporting companies
DongYeon (Samsung) provides comments.
Stefan (Ericsson) provides comments and questions
Haris (Qualcomm) comments
Wanqiang (Huawei) comments
Hannu (Nokia) comments and asks questions.
Hannu (Nokia) corrects his previous comment as there was incorrect tdoc number involved.
Jean Yves (Thales) responses to Hannu and comments
DongYeon (Samsung) comments.
Jean Yves (Thales) provides answers together with revision r02.
Hannu (Nokia) asks further questions on r02.
Jean Yves (Thales) answers to Hannu.
Jean Yves (Thales) provides r03.
Sherry (Xiaomi) replies to Hannu.
Haris (Qualcomm) comments on r02
Sherry (Xiaomi) replies to Hannu again.
Jean Yves (Thales) responds to Haris
Sherry (Xiaomi) replies to Haris.
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) requests to postpone the SID.
Jean Yves (Thales) challenges the request and ask question to Leo.
Haris (Qualcomm) objects to approving the SID at this meeting and proposes to postpone to understand the related objectives of TSG RAN
Leo (Deutsche Telekom) replies to Jean Yves
Stefan (Ericsson) agrees with Haris and Leo and objects to this SID. SA2 needs to do more work to ensure objectives align with RAN scope.
Jean Yves (Thales) notes that this R18 NTN SID is considered too early by some companies and that its content definition needs to be consolidated later in Q4 2021
Sherry (Xiaomi) agrees to postpone the SID proposal and further work on it in Q4 to align with RAN.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106301 DISCUSSION Discussion Discussion about power efficiency aspect for Rel-18 ProSe. LG Electronics Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106313 DISCUSSION Information Open Discussion _x00B_about eNA work in R18 vivo,China Mobile Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106322 SID NEW Approval New SID on enhancement on 5G LAN-type service. Huawei, China Mobile, China Telecom, China Unicom Rel-18 Noted Stefan (Ericsson) provides comments and questions on the objectives
Laurent (Nokia): Comments /questions
Jeffrey (Juniper) comments and provides r01
Sebastian (Qualcomm) comments
Dieter (Deutsche Telekom) has same questions/comments as already raised by Laurent and Stefan.
Marco (Huawei) replies to the questions
Jeffrey (Juniper) responds to Marco (Huawei)
Runze (Huawei) provides r02, merging 5974 and 6067.
Jeffrey (Juniper) merges r01 changes into r03 since r02 was only based on r00 (and other documents)
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any revision of this Tdoc
Runze (Huawei) asks for technical reason of the objection.
Runze (Huawei) provides r04.
Sang-Jun (Samsung) also asks for technical reason of the objection.
Laurent (Nokia): answers
Heng(China Telecom) ask for reason to decouple Group management from 5G VN communication.
Runze (Huawei) supports Heng (China Telecom).
Sang-Jun (Samsung) responses to Laurent (Nokia)
zhendong(ZTE) support r04,
Stefan (Ericsson) objects to all revisions of this SID
Runze (Huawei) replies to Stefan.
Yi (China Mobile) support that VN group management and VN communication are combined and should be covered both in the SID.
Jeffrey (Juniper) responds to Runze
Sang-Jun (Samsung) responses to Stefan (Ericsson).
Qianghua (Huawei) responds
Runze (Huawei) provides r05
Chi (China Unicom) proposes not to decouple Group management from 5G VN communication.
==== 8.X, 9.X Final Deadline ====
Sang-Jun (Samsung) provides r06-SEC with some some changes on controversial objectives.
Noted
9.1.3 S2-2106323 DISCUSSION Approval New SID on Enhancement to the 5GC LoCation Services Phase 3 CATT, Huawei Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106327 SID NEW Approval New SID on UE Aggregation for Industry with Multi-connectivity. vivo Mobile Communications Ltd, China Telecom, China Unicom, CATT, Spreadtrum Communications Rel-18 Noted Haris(Qualcomm) comments
Hualin(Huawei) ask for clarification
Zhenhua (vivo) responses
Sherry(Xiaomi) requests for clarifications.
Zhenhua (vivo) responses.
Guillaume (MediaTek Inc.) comments.
Sherry (Xiaomi) comments.
Saso (Intel) comments.
Devaki (Nokia) comments.
Zhenhua (vivo) responses to Guillaume (MediaTek Inc).
Zhenhua (vivo) reponses to Sherry (Xiaomi).
Zhenhua (vivo) reponses to Saso (Intel).
Zhenhua (vivo) responses to Devaki (Nokia).
Devaki (Nokia) replies.
Paul (Ericsson) comments.
Zhenhua (vivo) responses to Paul (Ericsson).
==== 8.X, 9.X Revisions Deadline ====
Haris (Qualcomm) objects to the approval of this SID
Paul (Ericsson) objects the approval of this SID.
Devaki (Nokia) comments that we share similar views as QCOM and Ericsson, we object to approval during this meeting (for additional considerations regarding the objectives and the use cases).
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106375 DISCUSSION Discussion Study on Architecture Enhancement to support Ranging-based services and relative positioning Xiaomi Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106376 SID NEW Approval New SID on Study on Ranging based services and relative positioning. Xiaomi Rel-18 Noted LaeYoung (LGE) provides comment.
Sherry (Xiaomi) replies.
LaeYoung (LGE) responds to Sherry (Xiaomi).
Walter (Philips) responds to LaeYoung's (LGE) suggestion to postpone
Åke (Ericsson) Support proposal to postpone.
Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) comments.
LaeYoung (LGE) proposes to postpone this SID and does not think this postponing has any effect on prioritization exercise planned in December SA.
Walter (Philips) thinks that postponing does influence the prioritization exercise in SA plenary
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) responds to Walter (Philips).
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106377 DISCUSSION Discussion Study on Sensing based services Xiaomi Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106378 SID NEW Approval New SID on Study on Sensing based services. Xiaomi Rel-18 Noted Wanqiang (Huawei) comments and proposes that in the following discussion, we differentiate the Uu based sensing and direct communication based sensing to better formulate the future work.
Leo (Deutsche Telekom) prefers to postpone the SID and wait for SA1 requirements in Rel-19.
Alessio(Nokia) supports Leo (Deutsche Telekom) and prefers to postpone the SID and wait for SA1 requirements in Rel-19.
Sherry(Xiaomi) clarifies that this SID proposal is for information only in SA2.
Hong (Qualcomm) comments and suugests to start from SA1.
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) requests to note the SID proposal.
Sherry (Xiaomi) is fine to note the SID proposal, and clarifies that it is for information.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106387 DISCUSSION Agreement Discussion on adding MP-DCCP to ATSSS phase3 SID. Deutsche Telekom Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106397 SID NEW Approval Study on enhancement to support Edge Computing in 5GC. Nokia, Nokia Shanghai Bell, Charter, NTT Docomo, Telecom Italia Rel-18 Revision of (Noted) S2-2103996 from S2-145E. Merged into S2-2106812 Shubhranshu (Nokia) provides r01
Dario (Qualcomm) asks question for clarifciation on first objective and proposes to take 625 as baseline SID.
Shubhranshu (Nokia) responds
Shubhranshu (Nokia) provides S2-2106397r02, which merges S2-2106397 and S2-2106255
Shubhranshu (Nokia) provides S2-2106397r03
Dieter (Deutsche Telekom) provides comments.
Shubhranshu (Nokia) comments and provides r04
Changhong (Intel) proposes to merge it into S2-2106255.
==== 8.X, 9.X Revisions Deadline ====
Magnus (Ericsson) objects to this SID at this meeting, we are positive to an EC SID more work is needed to consolidate and stabilize the objectives
==== 8.X, 9.X Final Deadline ====
Shubhranshu (Nokia) proposes as a way forward to merge this into S2-2106255
Merged
9.1.3 S2-2106434 DISCUSSION Agreement Rel-18 Proposal to support LTE-based 5G Terrestrial Broadcast (Rel-16 EnTV) connected to 5GC. . Qualcomm Inc, SWR Rel-18 Noted Thomas (Nokia) questions the need for this proposal.
Miguel (Qualcomm) provides answer to Thomas (Nokia)
Thomas (Nokia) replies to Miguel
LiMeng (Huawei) corrects the AI# of the email title, and comments.
zhendong(ZTE) comments that, it uses the wrong AI
Chunhui(Spreadtrum) supports Thomas (Nokia) to question the need for this proposal. From the technical and commercial perspectives, this proposal should not be pursued in SA2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106440 SID NEW Approval New SID on Personal IoT and Residential Networks architecture. Vivo Mobile Communications Ltd, CATT, China Telecom, Convida Wireless, InterDigital, KPN, OPPO, Spreadtrum Communications, T-Mobile USA Rel-18 r04 agreed. Revised to S2-2106813 Zhenhua (vivo) provides r01.
Marco (Huawei) provides comments and expresses concern.
Zhenhua (vivo) responses to Marco (Huawei) and provides r02.
Laurent (Nokia): Comments, echoing Marco's Concerns
Sherry (Xiaomi) comments.
Adrian (vivo) responds to Sherrys questions.
Walter (Philips) makes a suggestion and requests Philips to be added as supporting company.
Adrian (vivo) adds some text to address Walter(Philips) proposal, adds Philips and adds a NOTE and clarification into the text to address BBF concerns and provides r3.
Stefan (Ericsson) comments, sharing many of Marco's and Laurent's concerns
Walter (Philips) responds to Adrian (vivo) and provides a draft revision.
Dieter (Deutsche Telekom) shares concerns raised by Stefan, Marco and Laurent.
Adrian (vivo & captain of the ship) address's ship mates comments and provides r04.
Sebastian (Qualcomm) expresses concerns and comments
Marco (Huawei) provides revision in Draft folder 'S2-2106440r03_PIRatesSID Huawei' removing residential part
==== 8.X, 9.X Revisions Deadline ====
Chris Joul (T-Mobile USA) disagrees with Huawei Draft to r03 proposal and proposes to continue with r03 provided by Vivo as baseline.
Chris Joul (T-Mobile USA) disagrees with Huawei Draft to r03 proposal and proposes to continue with r03 provided by Vivo as baseline. [possibly duplicate]
Chris Joul (T-Mobile USA) Clarifies that r04 is also acceptable as baseline.
Laurent (Nokia): strongly suggests to POSTPONE this SID. (objects to any current version but agrees that further work may lead to an agreeable content)
Sebastian (Qualcomm) proposes to postpone the SID
Stefan (Ericsson) also proposes to postpone
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106813 SID NEW Approval New SID on Personal IoT and Residential Networks architecture. Vivo Mobile Communications Ltd, CATT, China Telecom, Convida Wireless, InterDigital, KPN, OPPO, Spreadtrum Communications, T-Mobile USA Rel-18 Revision of S2-2106440r04. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106451 SID NEW Approval New SID: PWS over non-3GPP access. Apple, Verizon UK Ltd Rel-18 Noted Haris(Qualcomm) comments
Cai Simon (Nokia) clarifies to Haris(Qualcomm) & provides comments
Marco (Huawei) agrees with Haris (Qualcomm)
Magnus (Ericsson) shares the concerns raised by Haris
Krisztian (Apple) responds to the comments
Dieter (Deutsche Telekom) shares concerns raised by Haris and agrees with comment by Magnus .
Krisztian (Apple) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106452 WORK PLAN Presentation Public Safety Requirements for Release 18 FirstNet, AT&T, UK Home Office, Netherlands Police, Erillisverkot, SyncTechno Inc, BDBOS, Nkom, BMWi Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106471 DISCUSSION Information Motivation for Study of Architecture Enhancements for Vehicle Mounted Relays (FS_VMR_ARC) Qualcomm Incorporated Rel-18 Revision of (Noted) S2-2104762 from S2-145E. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106468 SID NEW Approval New SID on Study of Architecture Enhancement for Vehicle Mounted Relays. Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2106814 Hong (Qualcomm) provides r01.
Hong (Qualcomm) provides r02.
Wanqiang (Huawei) comments.
Fei (OPPO) comments.
Shabnam (Ericsson) comments.
Spreadtrum (Chunhui) prefers to postpone this SID to next meeting for waiting for the SA1 output(if any).
Laurent (Nokia): Comments
Hong (Qualcomm) replies and provides r03.
Shabnam (Ericsson) provides comments in line with responses.
Chunhui (Spreadtrum) provides further RAN/technical/market comments and proposes to wait for RAN result before SA2 starting the work like IAB did before in Rel-16.
Wanqiang (Huawei) provides further comments and show strong concern regarding the VMR is a mobile device.
Hong (Qualcomm) replies to Wanqiang.
Hong (Qualcomm) replies to Fei.
Hong (Qualcomm) replies and provides r04.
==== 8.X, 9.X Revisions Deadline ====
Wanqiang (Huawei) proposes to postpone the proposal now.
Laurent (Nokia): supports the postponing of this SID
Chunhui (Spreadtrum) supports Huawei and Nokia to postpone this SID.
Hong (Qualcomm) replies to Wanqiang and requests a consistent handling of all SIDs proposals.
Shabnam (Ericsson) objects approval at this meeting, seems companies need more time to discuss and SA2 needs to do more work during Q4/2021 on the overall Rel-18 content
==== 8.X, 9.X Final Deadline ====
Hong (Qualcomm) provides r05 to CC#5 folder.
Revised
9.1.3 S2-2106814 SID NEW Approval New SID on Study of Architecture Enhancement for Vehicle Mounted Relays. Qualcomm Incorporated Rel-18 Revision of S2-2106468r04. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106478 DISCUSSION Discussion Discussion on Seamless UE context recovery Samsung Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106489 SID NEW Approval New SID: Study on Seamless UE context recovery. Samsung, NEC, CableLabs, Cisco Rel-18 Noted Haris(Qualcomm) comments
Lalith(Samsung) replies.
Laurent (Nokia): Comments
Jinguo(ZTE): Comments
Qian (Ericsson): provides Comments
Myungjune (LGE) comments.
Lalith(Samsung) replies to Laurent(Nokia)
Lalith(Samsung) replies to Jinguo(ZTE)
Lalith(Samsung) replies to Qian (Ericsson)
Lalith(Samsung) replies to Myungjune (LGE).
Ouyang(Huawei) comments
Sherry (Xiaomi) comments.
Lalith(Samsung) replies to Sherry (Xiaomi).
Lalith(Samsung) replies to Ouyang(Huawei)
Lalith(Samsung) provides r01
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any revision of this Tdoc
Qian (Ericsson) objects to the paper based on it's current content. We consider the study shall focus on the possibility maintaining the UE in Registered state as commented early
Ouyang(Huawei) prefers to note this SID.
Lalith(Samsung) replies to Laurent (Nokia)
Sherry(Xiaomi) proposes to note the SID, but is open to discuss the potential enhancement to existing solution to resolve the problem, i.e. it may be proposed as TEI18 mini WID.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106498 SID NEW Approval New SID: Study on System Enabler for Service Function Chaining. Intel, Telecom Italia, Spreadtrum, Sandvine, Convida Wireless, KPN, InterDigital, Microsoft, Matrixx, KDDI, AT&T, Deutsche Telekom, Cisco, Charter Communications Rel-18 r07 agreed. Revised to S2-2106815 Laurent (Nokia): provides r01
Laurent (Nokia): provides r01-Nokia
Fenqin (Huawei): provides comments
Sherry(Xiaomi) comments and requests for clarification about SFC policy.
Ellen (Intel) provides feedback to Nokia's revision and provided revision r02.
Sherry(Xiaomi) replies.
Jinguo(ZTE) comments
Dimitris (Lenovo) supports the study
Laurent (Nokia): Comments
Fenqin (Huawei) provides comments
Ellen (Intel): responds comments from companies and provide r03.
Curt (Charter) comments.
Fenqin (Huawei): provides a draft .
Ellen (Intel): provides r04 based on comments from Huawei and Charter Comm.
Fenqin (Huawei): ask question for clarification.
Ellen (Intel): respond to Huawei's questions
Stefan (Ericsson) provides comments and questions
Ellen (Intel) provides feedback to Ericsson
Fenqin (Huawei) provides a comment
Ellen (Intel) provides feedback to Huawei
Curt (Charter) asks Stefan (Ericsson) for a clarification.
Fenqin (Huawei) provides a response.
Fenqin (Huawei) provides a draft.
Laurent (Nokia): insists that This study considers only traffic handled over N6 by PSA UPF(s)
Stefan (Ericsson) replies to Curt
Stefan (Ericsson) replies to Ellen
Laurent (Nokia): aks a question
Stefan (Ericsson) provides comments and an update in drafts folder
Laurent (Nokia): provides r05-stro-lth
Laurent (Nokia): provides r05-Nokia
Stefan (Ericsson) provides comments and updates in draft folder
Ellen (Intel) provides r06
Ellen (Intel) provides r07
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version between R00 and R05, both included
Stefan (Ericsson) objects approval at this meeting. We support the study proposal in principle (e.g. using r07 as baseline), but we think SA2 needs to do more work during Q4 on the overall Rel-18 content
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2106815 SID NEW Approval New SID: Study on System Enabler for Service Function Chaining. Intel, Telecom Italia, Spreadtrum, Sandvine, Convida Wireless, KPN, InterDigital, Microsoft, Matrixx, KDDI, AT&T, Deutsche Telekom, Cisco, Charter Communications Rel-18 Revision of S2-2106498r07. Noted. To be used as a basis for further discussion Noted
9.1.3 S2-2106506 DISCUSSION Discussion Access Traffic Steering, Switch and Splitting support in an NTN system architecture (ATSSS) . Intelsat Rel-18 Noted Robert Olesen (Intelsat) - The document S2-2106506r03 has been updated in the revisions folder.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106221 DISCUSSION Discussion Discussion on NG-RTC new requirements in R18. China Mobile Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.3 S2-2106222 SID NEW Approval New SID: Study on system architecture for next generation real time communication services. China Mobile, China Unicom, Huawei, Hisilicon, ZTE, CATT, Vivo Rel-18 r04 agreed. Revised to S2-2106816 Thomas (Nokia) requests improvements of the objectives
Yi (China Mobile) responds to Thomas.
Leo (Deutsche Telekom) supports this SID, 'Deutsche Telekom' should be added to Supporting Individual Members (please remove the '?'), and DT provides comments.
Thomas(Nokia) replies to Yi
Suggest postponing the objectives with dependencies on the Rel-17 CT FS_eIMS5G2
Susan replies to Thomas(Nokia) and provides r01 in draft folder.
Ashok (Samsung) comments
Yi (China Mobile) provides comments.
George (Ericsson) provides some comments.
Haris (Qualcomm) comments
Susan (Huawei) replies to Ashok.
Susan (Huawei) replies to Haris.
Yi (China Mobile) responds to George.
Yi (China Mobile) comments
Thomas(Nokia) reminds that none of his comments on the objectives in the beginning of the thread has so far been taken into account.
Yi (China Mobile) provides R01 and provides clarification.
George (Ericsson) provides a comment.
George (Ericsson) provides r02. We are not OK with adding ISC, and Mw. I restored the original bullet from the original document.
Thomas(Nokia) suggest additional updates in a draft version.
Yi (China Mobile) provides r03.
George (Ericsson) provides comment.
Yi (China) responds to George.
==== 8.X, 9.X Revisions Deadline ====
Yi (China Mobile) will add T-mobile USA as supporter in the next version.
Chris Joul (T-Mobile USA) Asks to be added as supporter.
Haris (Qualcomm) proposes to only technically endorse and not approve
Yi (China Mobile) proposes to approve the SID and work further in Q4 to update the SID if needed.
Leo (Deutsche Telekom) agrees with China Mobile to approve the SID at this meeting.
George (Ericsson) We would like a clear mandate in an updated revision to CT groups not to impact the use of SIP for call control. We see this is essential. Once this is done we are supportive of the SID.
George (Ericsson) proposes the existing revision in Draft folder to update the note for WGs on SIP as call control being excluded.
Yi (China Mobile) provides r04 based on draft from Ericsson and add T-Mobile USA and Ericsson as supporting companies .
Susan (Huawei) is ok with r04 and support to approve the SID at this meeting.
==== 8.X, 9.X Final Deadline ====
James Hu (AT&T) supports this SID.
Revised
9.1.3 S2-2106816 SID NEW Approval New SID: Study on system architecture for next generation real time communication services. China Mobile, China Unicom, Huawei, Hisilicon, ZTE, CATT, Vivo Rel-18 Revision of S2-2106222r04. Noted. To be used as a basis for further discussion Noted
9.1.4 - - - TEI18 mini WID proposals - - Docs:=14 -
9.1.4 S2-2105402 WID NEW Information New TEI18 on the support of secondary DN Authentication in EPC IWK cases. Nokia, Nokia Shanghai Bell Noted Runze (Huawei) comments.
Runze (Huawei) updates the previous comments.
Hyunsook (LGE) asks for the clarification.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2105570 WID NEW Approval New WID: Dual Registration between two 5GS networks. Nokia, Nokia Shanghai Bell, Apple Rel-18 Noted Yusuke (KDDI) asks a question for the justification of the WID proposal.
Haris(Qualcomm) comments
Saso (Intel) seeks clarification.
Jinguo(ZTE) corrects the subject title, and comments
Devaki (Nokia) replies and provides r01:
Devaki (Nokia) corrects subject agenda item from 9.1.3 to 9.1.4.
Qian (Ericsson) provides comments.
Devaki (Nokia) replies.
Devaki (Nokia) comments.
Ouyang(Huawei) has concerns on this SID.
Saso (Intel) seeks further clarification (on RAN sharing).
Jianning (Xiaomi) provides comments
Ouyang(Huawei) replies to Devaki.
Lalith(Samsung) comments.
Huan(Vivo) seeks clarifications about the requirement and comments about the objectives
Devaki (Nokia) replies to Ouyang.
Jianning (Xiaomi) provides further comments
Devaki (Nokia) replies to Lalith (Samsung).
Devaki (Nokia) replies to Jianning (Xiaomi).
Qian (Ericsson) ask for clarification if the paper is submitted as a WID or SID.
Devaki (Nokia) provides r02 to fix section 2.
Hyunsook (LGE) provides a comment..
Guillaume (MediaTek Inc.) comments
Saso (Intel) re-sends a question re RAN sharing.
Lalith(Samsung) replies to Devaki (Nokia)
Ouyang(Huawei) requests to confirm the AI of this WIDs . Ouyang provides additional comments.
Guillaume (MediaTek) replies to Devaki (Nokia)
Devaki (Nokia) replies to Guillaume.
Saso (Intel) replies to Devaki; sees little value in this study.
Devaki (Nokia) provides r04 (updated to SID).
==== 8.X, 9.X Revisions Deadline ====
Dieter (Deutsche Telekom) objects this SID/WID.
Jianning (Xiaomi) share the view with Dieter (DT), propose to NOTE this WID
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2105664 DISCUSSION Information Providing DNN for N6 routing to I-SMF. Ericsson Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106303 WID NEW Information TEI18 WID: PC5 DRX for 5GS ProSe. LG Electronics Rel-18 Noted Steve (Huawei) Should be in the ProSe study.
Fei (OPPO) comments.
LaeYoung (LGE) responds to Steve (Huawei) and Fei (OPPO).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Sherry (Xiaomi) comments.
Noted
9.1.4 S2-2106314 WID NEW Information New TEI18 on 'Access type identification for untrusted non-3GPP access'. Lenovo, Motorola Mobility Noted Marco (Huawei) asks clarifications
Hualin(Huawei) comments
Gerald (Matrixx) with support and comments.
Apostolis (Lenovo) responds to Hualin (Huawei).
Tyler (OTD) provides comment.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106438 DISCUSSION Agreement Rel-18 Proposal to optimize GUTI reallocation. Qualcomm Inc Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106442 DRAFTCR Information 5G-GUTI reallocation optimization for fast release scenarios Qualcomm Incorporated Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106444 DRAFTCR Information 5G-GUTI reallocation optimization for fast release scenarios Qualcomm Incorporated Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106446 WID NEW Approval New WID on 5G-GUTI reallocation optimization for fast release scenarios. Qualcomm Incorporated Rel-18 Noted Qian (Ericsson) provides comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106502 WID NEW Information New WID: TEI18_REFLQOS - Improving Reflective QoS Control Indication. Apple Rel-18 Noted Haiyang (Huawei) seeks for clarification
==== 8.X, 9.X Revisions Deadline ====
Krisztian (Apple) responds to Haiyang.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2106503 WID NEW Information New WID: TEI18_CAPCONN - UE MM Core Network Capability change in ECM/CM-CONNECTED state. Apple Rel-18 Noted Qian (Ericsson) provides comments
Krisztian (Apple) responds to Qian.
Wanqiang (Huawei) asks clarification
Qian (Ericsson) provides further comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Krisztian (Apple) responds to Wanqiang
Noted
9.1.4 S2-2106505 WID NEW Information New WID: TEI18_ALTSNSSAI - Providing alternative S-NSSAI(s) to the UE in EPC to 5GC interworking. Apple Rel-18 Noted Peter (Ericsson) provides comments
Ashok (Samsung) shares same view as Peter (Ericsson)
Alessio(Nokia) agrees the problem space is very narrows and conditional to a very unusual set up. questions the urgency of addressing this.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Krisztian (Apple) responds to Peter, Alessio.
Krisztian (Apple) responds to Ashok.
Noted
9.1.4 S2-2105405 DISCUSSION Discussion Discussion on the use of Spending Limits for AM and UE Policies . Oracle, Verizon, Ericsson, Huawei, HiSilicon, Xiaomi, Dish networks. Noted Belen (Ericsson) supports the work and asks some questions.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2105406 WID NEW Approval WID: TEI18_SLAMUP - Spending Limits for AM and UE Policies in the 5GC . Oracle, Verizon, Huawei, HiSilicon, Xiaomi, Dish networks Noted Uri (oracle) comments on S2-2105406r01 (9.1.4 mini WID) and uploads r02 (S2-2105406r02).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.2 - - - Review of the Work Plan, Rel-17 WID Status Reports - - Docs:=24 -
9.2 S2-2105452 WORK PLAN Information Work_plan_3gpp_210409_Filtered_SA WG2 MCC CC#5: This was noted.
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2105568 WI STATUS REPORT Information IIoT status report Nokia, Nokia Shanghai Bell Rel-17 Revised to S2-2106829.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106829 WI STATUS REPORT Information IIoT status report Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105568. Noted Noted
9.2 S2-2105576 WI STATUS REPORT Information EV2XARC_Ph2 status report LG Electronics Rel-17 Revised in S2-2106531 Revised
9.2 S2-2106531 WI STATUS REPORT Information eV2XARC_Ph2 status report LG Electronics (Rapporteur) Created at CC#1. Revision of S2-2105576. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2105754 WI STATUS REPORT Information ENS_Ph2 status report ZTE Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2105823 WI STATUS REPORT Information ENPN status report Ericsson Inc. Rel-17 r02 Revised to S2-2106827.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106827 WI STATUS REPORT Information ENPN status report Ericsson Inc. Rel-17 Revision of S2-2105823r02. Noted Noted
9.2 S2-2106074 WI STATUS REPORT Information MINT status report LG Electronics Rel-17 Revised to S2-2106830.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106830 WI STATUS REPORT Information MINT status report LG Electronics Rel-17 Revision of S2-2106074. Noted Noted
9.2 S2-2106087 WI STATUS REPORT Approval Status report of 5MBS Huawei, HiSilicon Rel-17 Revised to S2-2106828.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106828 WI STATUS REPORT Approval Status report of 5MBS Huawei, HiSilicon Rel-17 Revision of S2-2106087. Noted Noted
9.2 S2-2106098 WI STATUS REPORT Information 5G_ProSe Status Report CATT (Rapporteur) Rel-17 Revised to S2-2106986.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106986 WI STATUS REPORT Information 5G_ProSe Status Report CATT (Rapporteur) Rel-17 Revision of S2-2106098. Noted Noted
9.2 S2-2106267 WI STATUS REPORT Information eEdge_5GC status report Huawei Rel-17 Revised to S2-2106832.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106832 WI STATUS REPORT Information eEdge_5GC status report Huawei Rel-17 Revision of S2-2106267. Noted Noted
9.2 S2-2106302 WI STATUS REPORT Information eNA_Ph2 Status Report vivo Communication Technology Revised to S2-2106985.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106985 WI STATUS REPORT Information eNA_Ph2 Status Report Vivo Communication Technology, China Mobile Revision of S2-2106302. Noted Noted
9.2 S2-2106511 WI STATUS REPORT Information SA WG2 Status report for ID_UAS Qualcomm Austria RFFE GmbH Revised to S2-2106831.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2106831 WI STATUS REPORT Information SA WG2 Status report for ID_UAS Qualcomm Austria RFFE GmbH - Revision of S2-2106511. Noted Noted
9.2 S2-2106528 WI STATUS REPORT Information SA WG2 Status report for MUSIM Intel (Rapporteur) Created at CC#1. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2106529 WI STATUS REPORT Information SA WG2 Status report for 5GSAT_ARCH Thales (Rapporteur) Created at CC#1. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2106530 WI STATUS REPORT Information MPS2 Status Report Perspecta Labs (Rapporteur) Created at CC#1. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2106532 WI STATUS REPORT Information SA WG2 Status report for LCS_Ph2 CATT (Rapporteur) Created at CC#1. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.3 - - - Planning future meetings - - Docs:=0 -
9.4 - - - Items moved from earlier agenda items at CC#2 - - Docs:=11 -
9.4 S2-2105372 LS In Information LS from SA WG3: Reply LS on Small data transmissions SA WG3 (S3-213034) Rel-17 Postponed
==== 8.X, 9.X Final Deadline ====
Postponed
9.4 S2-2105335 CR Approval 23.502 CR2890 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-16 CC#2: Moved to new agenda item 9.4. r03 agreed. Revised to S2-2106817
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Alessio(Nokia) provides r01
Chris (Vodafone) provides r02
alessio(Nokia) is ok with r02 and thanks Chris for the accurate review.
Haris (Qualcomm) provides r03
Alessio (Nokia) is ok with r03
==== 8.X, 9.X Revisions Deadline ====
Wanqiang (Huawei) is ok with r03
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2106817 CR Approval 23.502 CR2890R1 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-16 Revision of S2-2105335r03. Approved Agreed
9.4 S2-2105336 CR Approval 23.502 CR2891 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-17 CC#2: Moved to new agenda item 9.4. r?? agreed. Revised to S2-2106818
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Alessio(Nokia) provides r01
==== 8.X, 9.X Revisions Deadline ====
Alessio(Nokia) provides r02 in the drafts folder just FYI
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2106818 CR Approval 23.502 CR2891R1 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-17 Revision of S2-2105336r?? Approved Agreed
9.4 S2-2105337 CR Approval 23.401 CR3643 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-16 CC#2: Moved to new agenda item 9.4. r04 agreed. Revised to S2-2106819
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Alessio(Nokia) provides r01
Chris (Vodafone) provides r02
Qian (Ericsson) comments and provides r03
alessio (Nokia) comments and provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2106819 CR Approval 23.401 CR3643R1 (Rel-16, 'F'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-16 Revision of S2-2105337r04. Approved Agreed
9.4 S2-2105338 CR Approval 23.401 CR3644 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell Rel-17 CC#2: Moved to new agenda item 9.4. r?? agreed. Revised to S2-2106820
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Alessio(Nokia) provides r01
==== 8.X, 9.X Revisions Deadline ====
Alessio(Nokia) provides r02 in the drafts folder just FYI
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2106820 CR Approval 23.401 CR3644R1 (Rel-17, 'A'): Handling of UE Radio Capability for Paging Nokia, Nokia Shanghai Bell, Vodafone Rel-17 Revision of S2-2105338r?? Approved Agreed
9.4 S2-2106699 LS OUT Approval [DRAFT] LS on the UE Radio Capability for Paging in RACS context Nokia Rel-16 Created at CC#2. r00 agreed. Revised to remove 'draft' in S2-2106821 Alessio(Nokia) provides the base version of a possible LS, if we agree to send it
Chris (Vodafone) comments that 6699r0 looks good: Just need to update the 'attachments' with the agreed CRs.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2106821 LS OUT Approval LS on the UE Radio Capability for Paging in RACS context SA WG2 Rel-16 Revision of S2-2106699r00. Approved Approved
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=39 -
99 S2-2105626 SID NEW Approval New SID on Enhancement to the 5GC LoCation Services Phase 3. CATT, Huawei Rel-18 Revision of (Noted) S2-2103834 from S2-145E. WITHDRAWN Withdrawn
99 S2-2106200 DISCUSSION Information Analysis of solutions to support multiple slices in UPF related to CT WG4's LS (S2-2105240). China Telecom, ZTE Rel-17 WITHDRAWN Withdrawn
99 S2-2106040 CR Approval 23.501 CR3132 (Rel-16, 'F'): Clarification for 5GS Bridge available event Huawei, HiSilicon Rel-16 Confirm Specification Number - CR states 23.502! WITHDRAWN Devaki (Nokia) comments. Withdrawn
99 S2-2105846 CR Approval 23.288 CR0415 (Rel-17, 'F'): Placeholder Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2106065 CR Approval 23.501 CR3145 (Rel-17, 'F'): Clarification for 5GS Bridge available event Huawei, HiSilicon Rel-17 Confirm Specification Number - CR states 23.502! WITHDRAWN Withdrawn
99 S2-2106428 LS OUT Approval [DRAFT] LS on Time Synchronization support in 3GPP specification Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2106416 P-CR Approval 23.247: Changing service area of multicast session Nokia, Nokia Shanghai-Bell Rel-17 Revised in S2-2106447. WITHDRAWN Withdrawn
99 S2-2106020 SID NEW Approval New SID: 5G Architecture enhancements for Harmonized Communication and Sensing service Huawei, HiSilicon, vivo, CAICT, China Unicom, China Mobile, China Telecom, CATT, ZTE Rel-18 WITHDRAWN Withdrawn
99 S2-2106021 DISCUSSION Discussion New SID Proposal on 5G Harmonized Communication and Sensing service (HCS) Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2105747 CR Approval 23.503 CR0627 (Rel-17, 'F'): KI#5 Correction on Data subset name for Network Slice Specific Control Data ZTE Rel-17 WITHDRAWN Withdrawn
99 S2-2105721 CR Approval 23.501 CR3068 (Rel-17, 'F'): Alignment of 5G ProSe reference point names Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2105676 CR Approval 23.501 CR3060 (Rel-17, 'F'): MUSIM Terminology Alignment Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106101 LS OUT Approval [DRAFT] LS Response on Clarifications of Network slice selection during AMF Reallocation Huawei,HiSilicon Rel-17 Response to S2-2105289. WITHDRAWN Withdrawn
99 S2-2106102 CR Approval 23.502 CR3036 (Rel-16, 'F'): DN-AAA triggered re- authorization/authentication Huawei,HiSilicon Rel-16 WITHDRAWN Withdrawn
99 S2-2106103 CR Approval 23.502 CR3037 (Rel-17, 'A'): DN-AAA triggered re- authorization/authentication Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106104 CR Approval 23.502 CR2812R1 (Rel-16, 'F'): L-PSA release during HO procedure with I-SMF removal Huawei,HiSilicon Rel-16 Revision of (Postponed) S2-2104382 from S2-145E. WITHDRAWN Withdrawn
99 S2-2106105 CR Approval 23.502 CR2813R1 (Rel-17, 'A'): L-PSA release during HO procedure with I-SMF removal Huawei,HiSilicon Rel-17 Revision of (Postponed) S2-2104383 from S2-145E. WITHDRAWN Withdrawn
99 S2-2106106 P-CR Approval 23.247: MBS procedures for inter System Mobility Huawei,HiSilicon Rel-17 Revision of (Noted) S2-2104393 from S2-145E. WITHDRAWN Withdrawn
99 S2-2106107 P-CR Approval 23.247: Clarification on 5MBS interworking with eMBMS at transport layer Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106108 P-CR Approval 23.247: 5MBS interworking with eMBMS for same MBS service at both side Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106109 P-CR Approval 23.247: Further clarification for MBS session activation and deactivation Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106110 P-CR Approval 23.247: Support of multicast service available within a limited area Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106111 P-CR Approval 23.247: Resolve the EN for mobility support of MBS Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2106112 P-CR Approval 23.247: Minimization of data loss Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2105430 CR Approval 23.502 CR2908 (Rel-17, 'B'): TS23.502 KI#1: Reporting while roaming Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2105542 P-CR Approval 23.304: Corrections of architectural reference model Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2105543 P-CR Approval 23.304: Update naming convention for new reference points in 5G ProSe Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2105547 P-CR Approval 23.304: Clarification on PC2a reference point Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2105870 CR Approval 23.288 CR0420 (Rel-17, 'F'): Clarification on the usage of Supported Analytics Delay when the NWDAF also supports Analytics Aggregation China Unicom Rel-17 WITHDRAWN Withdrawn
99 S2-2105480 CR Approval 23.502 CR2919 (Rel-17, 'B'): Registration Procedure Updates for MINT Convida Wireless LLC Rel-17 WITHDRAWN Withdrawn
99 S2-2105467 CR Agreement 23.502 CR2914 (Rel-15, 'F'): Correction of the 'Notification of User Plane Management Events' procedure KDDI Corporation Rel-15 WITHDRAWN Withdrawn
99 S2-2105317 CR Approval 23.502 CR2885 (Rel-17, 'F'): Missing functionality in NSSF service to support NSSRG Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2105343 CR Approval 23.502 CR2893 (Rel-17, 'F'): UE context update Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2105378 LS In Information NOT USED: Reserved for incoming LS MCC () WITHDRAWN Withdrawn
99 S2-2105379 LS In Information NOT USED: Reserved for incoming LS MCC () WITHDRAWN Withdrawn
99 S2-2105380 LS In Information NOT USED: Reserved for incoming LS MCC () WITHDRAWN Withdrawn
99 S2-2105381 LS In Information NOT USED: Reserved for incoming LS MCC () WITHDRAWN Withdrawn
99 S2-2106318 SID NEW Approval Study on Personal IoT and Residential Networks Architecture vivo Mobile Communications Ltd, China Telecom, T-Mobile USA, CATT, OPPO, Spreadtrum Communications, Convida Wireless Rel-18 WITHDRAWN Withdrawn
99 S2-2106447 P-CR Approval 23.247: Nmbsmf_TMGI and Nmbsmf_MBSSession service updates Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2106416. WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 197
Replied to LSs: 29
Noted: 398
Merged: 209
For e-mail approval: 0
Postponed: 83
Withdrawn: 47
Total documents: 1765