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-2300001 AGENDA Approval SA2#154AHE Meeting Agenda SA WG2 Chair Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
3 - - - SA2#154 Meeting report - - Docs:=1 -
3 S2-2300002 REPORT Approval Draft Report of SA WG2 meeting #154 SA WG2 Secretary Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=76 -
4.1 - - - Non 3GPP session in non-allowed area - - Docs:=12 -
4.1 S2-2300029 LS In Action LS from CT WG1: LS on Handling of the Allowed PDU session status IE in Non-allowed service area CT WG1 (C1-227197) Rel-18 Responses drafted in S2-2300216, S2-2300530, S2-2300562, S2-2300604, S2-2301070, S2-2301276. Postponed LiMeng (Huawei) asks for clarification.
Myungjune (LGE) comments.
Hannu (Nokia) responds to LiMeng and Myungjune
Fei (OPPO) comments.
Hannu (Nokia) replies to Fei and challenges the need for SA2 to specify PDU encoding on behalf of CT1.
Guillaume (MediaTek Inc.) comments.
Robert (Apple) highlights that there is an additional aspect regarding the inclusion of the Allowed PDU session status IE.
Lalith(Samsung) shares same view as Hannu (Nokia)
Myungjune (LGE) replies to Robert (Apple)
Myungjune (LGE) replies to Hannu (Nokia) and Lalith (Samsung)
Lalith (Samsung) replies to Myungjune (LGE)
Robert (Apple) replies to Myungjune (LGE)
Lalith (Samsung) proposes to postpone this LS to next meeting.
Postponed
4.1 S2-2300216 LS OUT Approval [DRAFT] Reply LS on handling of the allowed PDU session status IE Ericsson Rel-18 Response to S2-2300029. Noted To be merged into S2-2301276 (Noted) Lalith (Samsung) proposes to merge with S2-2301276
==== Revisions Deadline ====
Qian (Ericsson) is ok to merge with S2-2301276
==== Final Comments Deadline ====
Noted
4.1 S2-2300530 LS OUT Approval [DRAFT] Reply LS on Handling of the Allowed PDU session status IE Huawei, HiSilicon Rel-18 Response to S2-2300029. Noted To be merged into S2-2301276 (Noted) Lalith (Samsung) proposes to merge with S2-2301276
LiMeng (Huawei) agrees the merge proposal from Lalith (Samsung)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
4.1 S2-2300562 LS OUT Approval [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area LG Electronics Rel-18 Response to S2-2300029. Noted To be merged into S2-2301276 (Noted) Lalith(Samsung) proposes to merge with S2-2301276
Myungjune (LGE) provides r01.
Robert (Apple) argues that in certain cases the UE will have to include the Allowed PDU session status IE and indicate that a PDU session can be transferred.
Robert (Apple) provides r02 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2301276r02.zip> .
Myungjune (LGE) points out that r02 provided by Robert (Apple) is revision of S2-2301276 and replies to Robert (Apple).
Robert (Apple) replies to Myungjune (LGE).
Myungjune (LGE) replies to Robert (Apple) and provides r03.
Robert (Apple) responds and indicates a preference for S2-2301276 r02.
==== Revisions Deadline ====
Myungjune (LGE) is ok to merge this S2-2301276.
==== Final Comments Deadline ====
Noted
4.1 S2-2300604 LS OUT Approval [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area OPPO Rel-18 Response to S2-2300029. Noted To be merged into S2-2301276 (Noted) Lalith(Samsung) proposes to merge with S2-2301276
Fei (OPPO) confirms it can be marked as merged.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
4.1 S2-2301070 LS OUT Approval [DRAFT] Reply LS on handling of the Allowed PDU Session status IE in Non-allowed Area Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300029. Noted To be merged into S2-2301276 (Noted) Lalith(Samsung) proposes to merge with S2-2301276
Hannu (Nokia) agrees to merge this paper to S2-2301276
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
4.1 S2-2301276 LS OUT Approval [DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area Samsung Response to S2-2300029. Noted Lalith(Samsung) provides r01.
Robert (Apple) provides r02 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2301276r02.zip> .
Lalith(Samsung) comments on r02 .
Robert (Apple) responds to Lalith(Samsung).
Lalith(Samsung) seeks further clarification from Robert (Apple)
Myungjune comments
Robert (Apple) responds to Lalith (Samsung)
Lalith (Samsung) replies to Robert(Apple)
Myungjune is not ok with r00, r01, r02
Lalith(Samsung) provides r03
Myungjune (LGE) provides r04
Guillaume (MediaTek Inc.) agrees with Robert (Apple)
Robert (Apple) provides r05 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2301276r05.zip>
Haris(Qualcomm) asks question why we discuss support of MPS over non-3GPP access since the related feature is being introduced in rel.18 in MPS_WLAN WI
Guillaume (MediaTek Inc.) support r05
Lalith (Samsung) comments on r05
Myungjune (LGE) provides r06.
Lalith(Samsung) replies to Guillaume (MediaTek Inc.)
Robert (Apple) responds to Haris
Lalith(Samsung) provides r07.
Lalith(Samsung) replies to Robert (Apple)
Robert (Apple) responds to Myungjune (LGE) and objects to r06.
Robert (Apple) comments and provides r10.
Guillaume (MediaTek Inc.) comments
Guillaume (MediaTek Inc.) responds to Lalith (Samsung)
Guillaume (MediaTek Inc.) replies
Lalith(Samsung), provides r09
Kindly ignore r08
Guillaume (MediaTek Inc.) replies to Robert (Apple)
Hannu (Nokia) provides r11 with one word added.
==== Revisions Deadline ====
Myungjune (LGE) is only ok with r10, r11.
Lalith(Samsung) comments.
Lalith(Samsung) objects r10, r11
Robert (Apple) is only ok with r10, r11.
Hannu (Nokia) can live with either r10 or r11
Lalith(Samsung) comments to NOTE this paper.
==== Final Comments Deadline ====
Noted
4.1 S2-2300532 CR Approval 23.502 CR3742 (Rel-18, 'F'): TS23.502: Clarification of handling of the non-3GPP PDU session in Non-allowed service area Huawei, HiSilicon Rel-18 Revised to S2-2302161. Hannu (Nokia) proposes to consider S2-2300531 first. If the other CR is agreed (in a revision), then this one could be revised to add a reference to TS 23.501 clause.
Robert (Apple) proposes to move the reference mentioned by Nokia (if any) to step 6 or 6a.
Myungjune (LGE) comments.
LiMeng (Huawei) provides r01.
Robert (Apple) responds and provides r02.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r02 and wants to cosign.
LiMeng (Huawei) thanks the support of Myungjune and Robert.
Robert (Apple) is ok with r02
==== Final Comments Deadline ====
Revised
4.1 S2-2302161 CR Approval 23.502 CR3742R1 (Rel-18, 'F'): TS23.502: Clarification of handling of the non-3GPP PDU session in Non-allowed service area Huawei, HiSilicon, LG Electronics, Apple Rel-18 Revision of S2-2300532. Approved Agreed
4.1 S2-2300531 CR Approval 23.501 CR3928 (Rel-18, 'F'): TS 23.501: Clarification of handling of the non-3GPP PDU session in Non-allowed service area Huawei, HiSilicon Rel-18 Revised to S2-2302162. Hannu (Nokia) comments and explains why the CR needs a revision (if the CR is needed at all?)
LiMeng (Huawei) responds to Hannu and provides r01.
Lalith(Samsung) provides r02
Myungjune (LGE) comments
LiMeng (Huawei) is fine with r02 and responds.
Myungjune (LGE) replies to LiMeng (Huawei).
Robert (Apple) agrees with Myungjune (LGE) and provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2300531r03.docx.zip> .
LiMeng (Huawei) thanks Robert (Apple) for providing r03 and is fine with r03.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r03.
Lalith(Samsung) is ok with r03.
Robert (Apple) is ok with r03.
Lalith (Samsung) is ok with r03 after fixing a typo:
From:
'the service area restrictions as specified in clause 5.4.3.1.1 apply'
to
'the service area restrictions as specified in clause 5.3.4.1.1 apply'
Hannu (Nokia) supports r03 (with the cover page cleanup proposed by Robert and the reference correction proposed by Lalith)
==== Final Comments Deadline ====
Revised
4.1 S2-2302162 CR Approval 23.501 CR3928R1 (Rel-18, 'F'): TS 23.501: Clarification of handling of the non-3GPP PDU session in Non-allowed service area Huawei, HiSilicon, Apple Rel-18 Revision of S2-2300531. Approved Agreed
4.1 S2-2300217 CR Approval 23.501 CR3846 (Rel-18, 'F'): Non-allowed area clarification Ericsson Rel-18 Noted Hannu (Nokia) shares r01 and clarifies also the cover page hoping to help out drafting the related LS out.
Lalith(Samsung) provides r02.
Qian (Ericsson) provides comments and prefers r01.
Lalith(Samsung) comments.
Qian (Ericsson) provides further comments.
Robert (Apple) comments that the contents of the Allowed PDU session status IE does not depend on whether the UE is in an allowed or non-allowed area and provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2300217r03.zip> .
Myungjune (LGE) provides r04.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r04.
Qian (Ericsson) is ok with r04 and will tick the ME box as commented.
Robert (Apple) is ok with r04.
Lalith(Samsung) is ok with r04. Please add 'Samsung' as supporting company.
Hannu (Nokia) supports r04. Please add 'Nokia, Nokia Shanghai Bell' as supporting companies.
Haris(Qualcomm) object to r04, r02
Myungjune (LGE) replies to Haris(Qualcomm)
Lalith(Samsung) clarifies to Haris(Qualcomm)
Lalith(Samsung) proposes to NOTE
Haris(Qualcomm) responds
==== Final Comments Deadline ====
Noted
4.1 - - - Edge Computing - - Docs:=20 -
4.1 S2-2300066 LS In Information LS from SA WG3: Reply LS on user s consent for EDGEAPP SA WG3 (S3-223904) Rel-17 Noted Noted
4.1 S2-2300081 LS In Information LS from SA WG5: Reply LS to S5-226028 on Network federation interface for Telco edge consideration and proposals to answer GSMA LSs 5-226016 and S5-226017 from SA SA WG5 (S5-227039) Rel-18 Noted Noted
4.1 S2-2300082 LS In Information LS from SA WG6: Reply LS on user s consent for EDGEAPP SA WG6 (S6-223339) Rel-17 Noted Noted
4.1 S2-2300084 LS In Information LS from SA WG6: Reply LS on Clarification of Edge Node Sharing SA WG6 (S6-223506) Rel-18 Noted Noted
4.1 S2-2300085 LS In Information LS from SA WG6: Reply LS on Network federation interface for Telco edge consideration for a consolidated reply SA WG6 (S6-223553) Rel-18 Noted Noted
4.1 S2-2300086 LS In Action LS from SA WG6: LS on the use of a non-network defined identifier for UE identification SA WG6 (S6-223558) Rel-18 Responses drafted in S2-2301160, S2-2301227. Final response in S2-2302163 Proposed to move to 9.17.1 Replied to
4.1 S2-2301160 LS OUT Approval [DRAFT] Reply LS on the use of a non-network defined identifier for UE identification Intel Rel-18 Response to S2-2300086. Merged into S2-2302163 Proposed to move to 9.17.1 Laurent (Nokia): suggests to merge in 1227 (see a r01 of 1227)
Saso (Intel) is OK to merge 1160 in 1227
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
4.1 S2-2301227 LS OUT Approval [DRAFT] LS on the use of a non-network defined identifier for UE identification Nokia Belgium Response to S2-2300086. Revised to S2-2302163, merging S2-2301160 Proposed to move to 9.17.1 Laurent (Nokia): provides a r01 of 1227 sort of merging with 1160
Saso (Intel): provides r02
Josep (DT) comments, supports the approach.
Laurent (Nokia): provides r03
Sudeep (Apple) provides r04.
Fenqin (Huawei): provides comments
Saso (Intel) is ok with r03; prefers r03 over r04
Magnus O (Ericsson) provides r5
Sudeep (Apple) provides r06.
Josep (DT) comments, likes r05.
==== Revisions Deadline ====
Magnus (Ericsson) provides correct link to r05
Sudeep (Apple) insists to proceed with r06.
Laurent (Nokia): objects to R04, R06; prefers much R03 or R02
Saso (Intel) proposes to agree r05 as a middle ground (while preferring r03 or r02)
Sudeep (Apple) can also agree to r05 as a compromise.
Fenqin (Huawei) we are ok with r05
==== Final Comments Deadline ====
Revised
4.1 S2-2302163 LS OUT Approval LS on the use of a non-network defined identifier for UE identification SA WG2 Revision of S2-2301227, merging S2-2301160. Approved Approved
4.1 S2-2300087 LS In Information LS from SA WG6: Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network SA WG6 (S6-223586) Rel-18 Noted Noted
4.1 S2-2300074 LS In Information LS from SA WG4: Reply LS on EAS relocation affinity SA WG4 (S4-221495) Rel-18 Noted Noted
4.1 S2-2300091 LS In Information LS from TSG SA: Reply LS on Network federation interface for Telco edge consideration TSG SA (SP-221321) Rel-18 Noted Noted
4.1 S2-2300070 LS In Action LS from SA WG3: Reply LS on Network federation interface for Telco edge consideration SA WG3 (S3-223914) Rel-18 Noted Noted
4.1 S2-2300083 LS In Action LS from SA WG6: Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network SA WG6 (S6-223487) Rel-18 Responses drafted in S2-2300613, S2-2300633, S2-2300920, S2-2301007, S2-2301097. Final response in S2-2302164 Replied to
4.1 S2-2300633 LS OUT Approval [DRAFT] Reply LS on Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network China Mobile Rel-18 Response to S2-2300083. Merged into S2-2302164 Laurent (Nokia): objects to any version of this LS to have a single thread to discuss : that of 0613
Laurent (Nokia): objects to any version of this tdoc to have a single thread to discuss the LS OUT answer to 0083 : that of 0613
Yan (China Mobile) has merged this 0633 into 1097.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
4.1 S2-2300920 LS OUT Approval [DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network Ericsson Rel-18 Response to S2-2300083. Merged into S2-2302164 Laurent (Nokia): objects to any version of this tdoc to have a single thread to discuss the LS OUT answer to 0083 : that of 0613
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
4.1 S2-2301007 LS OUT Approval [DRAFT] Reply LS on support of NAT deployed within the edge data network Apple Rel-18 Response to S2-2300083. Merged into S2-2302164 Laurent (Nokia): objects to any version of this tdoc to have a single thread to discuss the LS OUT answer to 0083 : that of 0613
Laurent (Nokia): please disregard the previous comment: 'objects to any version of this tdoc to have a single thread to discuss the LS OUT answer to 0083 : that of 0613' that was due to a typo in the mail title
Sudeep (Apple) OK to consider this merged to 1097.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
4.1 S2-2301097 LS OUT Approval [DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network Intel Rel-18 Response to S2-2300083. Revised to S2-2302164, merging S2-2300633, S2-2300920, S2-2301007 and S2-2300613 Laurent (Nokia): objects to any version of this tdoc to have a single thread to discuss the LS OUT answer to 0083 : that of 0613
Saso (Intel) provides r01
Fenqin (Huawei) provides comments and r02
Yan (China Mobile) comments.
Dario (Qualcomm) provides r03
Saso (intel) provides r04
Dario (Qualcomm) provides r05.
Saso (Intel) seeks clarification on r05
Dario (Qualcomm) replies to Saso and provides r06.
Laurent (Nokia): I remove my previous objection that was only intending to have a single thread. Now I may have objections to individual versions, to be decided after revision deadline
Saso (Intel) provides r07.
==== Revisions Deadline ====
Laurent (Nokia): objects to R00, R01, R02, R03, R04
Fenqin (Huawei): we are ok with r07
==== Final Comments Deadline ====
Revised
4.1 S2-2302164 LS OUT Approval Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network SA WG2 Rel-18 Revision of S2-2301097, merging S2-2300633, S2-2300920, S2-2301007 and S2-2300613. Approved Approved
4.1 S2-2300613 LS OUT Approval [DRAFT] LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300083. Merged into S2-2302164 Fenqin (Huawei): suggest to discuss in 1097
==== Revisions Deadline ====
Laurent (Nokia): 0613 is merged in 1097
==== Final Comments Deadline ====
Merged
4.1 - - - V2X - - Docs:=2 -
4.1 S2-2300065 LS In Information LS from SA WG1: Reply LS on QoS Sustainability analytics and V2X service adaptations SA WG1 (S1-223734) Rel-19 Noted Haris(Qualcomm) proposes to NOTE Noted
4.1 S2-2300090 LS In Information LS from TSG SA: Reply LS on QoS Sustainability analytics and V2X service adaptations TSG SA (SP-221320) Rel-19 Noted Haris(Qualcomm) proposes to NOTE since it is sent only for info to SA2 Noted
4.1 - - - XR related - - Docs:=0 -
4.1 - - - Lawful interception - - Docs:=7 -
4.1 S2-2300034 LS In Action LS from CT WG4: Reply LS on Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover CT WG4 (C4-225542) Rel-18 Response drafted in S2-2300614. Final response in S2-2302165 Replied to
4.1 S2-2300614 LS OUT Approval [DRAFT] LS on Identifier availability for Lawful Interception during Inter-PLMN handover Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300034 (and S2-2210210, noted at SA2#154-e). Revised to S2-2302165. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
4.1 S2-2302165 LS OUT Approval LS on Identifier availability for Lawful Interception during Inter-PLMN handover SA WG2 Rel-18 Revision of S2-2300614. Approved Approved
4.1 S2-2300616 CR Approval 23.502 CR3757 (Rel-18, 'B'): Identifier availability for Lawful Interception during MME-5GS handover Nokia, Nokia Shanghai Bell, Vodafone Rel-18 Revised to S2-2302166. Qian (Ericsson) provides comments and r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
4.1 S2-2302166 CR Approval 23.502 CR3757R1 (Rel-18, 'B'): Identifier availability for Lawful Interception during MME-5GS handover Nokia, Nokia Shanghai Bell, Vodafone Rel-18 Revision of S2-2300616. Approved Agreed
4.1 S2-2300615 CR Approval 23.401 CR3720 (Rel-18, 'B'): Identifier availability for Lawful Interception during Inter-MME/ MME-5GS handover Nokia, Nokia Shanghai Bell, Vodafone Rel-18 Revised to S2-2302167. Qian (Ericsson) provides comments and r01
==== Revisions Deadline ====
Chris (Vodafone) prefers r00 but is OK with r01
Qian (Ericsson) indicates that r01 is more consistent at least.
==== Final Comments Deadline ====
Revised
4.1 S2-2302167 CR Approval 23.401 CR3720R1 (Rel-18, 'B'): Identifier availability for Lawful Interception during Inter-MME/ MME-5GS handover Nokia, Nokia Shanghai Bell, Vodafone Rel-18 Revision of S2-2300615. Approved Agreed
4.1 - - - NSWO clarifications - - Docs:=10 -
4.1 S2-2300020 LS In Action LS from CT WG1: LS on NSWO feature CT WG1 (C1-227003) Rel-17 Response drafted in S2-2300619. Final response in S2-2302168 Replied to
4.1 S2-2300619 LS OUT Approval [DRAFT] LS on NSWO feature Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2300020. Revised to S2-2302168. Yishan (Huawei) provides comments
Laurent (Nokia): provides r01
Yishan (Huawei) replies to Laurent (Nokia) and provides r02
Yishan (Huawei) further provides r03
Laurent (Nokia): provides r04
Marco (Huawei) provide r05
Haris(Qualcomm) is ok with the content but proposes to add SA3 in CC
Yildirim (Charter) comments
Laurent (Nokia): provides r06
Marco (Huawei) comments
==== Revisions Deadline ====
Saso (Intel) points out that an editorial fix is needed in r06
Yildirim (Charter) points out that another editorial fix in r06
Laurent (Nokia): proposes to go to R06 with 2 editorial fixes:1) 'can been seen' ==> 'can be seen' AND 2) 'and is not acting an authentication server' => 'and is not acting as an authentication server'
Haris(Qualcomm) SWa needs to be SWa' in r06
Omkar (CableLabs) suggests another editorial fix in r06
==== Final Comments Deadline ====
Revised
4.1 S2-2302168 LS OUT Approval LS on NSWO feature SA WG2 Rel-17 Revision of S2-2300619. Approved Approved
4.1 S2-2300617 CR Approval 23.501 CR3947 (Rel-17, 'F'): 5G NSWO clarifications and corrections Nokia, Nokia Shanghai Bell, Intel Rel-17 Revised to S2-2302169. Genadi (Lenovo) provides comments and r01.
Laurent (Nokia): provides r02
Genadi (Lenovo) is fine with r02.
marco (huawei) provides r03.
Dieter (Deutsche Telekom) comments/asks a questions.
Stefan (Ericsson) provides r04
Marco (Huawei) is OK with r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
4.1 S2-2302169 CR Approval 23.501 CR3947R1 (Rel-17, 'F'): 5G NSWO clarifications and corrections Nokia, Nokia Shanghai Bell, Intel, Ericsson Rel-17 Revision of S2-2300617. Approved Agreed
4.1 S2-2300618 CR Approval 23.501 CR3948 (Rel-18, 'A'): 5G NSWO clarifications and corrections Nokia, Nokia Shanghai Bell, Intel Rel-18 Revised to S2-2302170. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
4.1 S2-2302170 CR Approval 23.501 CR3948R1 (Rel-18, 'A'): 5G NSWO clarifications and corrections Nokia, Nokia Shanghai Bell, Intel Rel-18 Revision of S2-2300618. Approved Agreed
4.1 S2-2300037 LS In Action LS from CT WG4: LS on NAI format for 5G NSWO CT WG4 (C4-225641) Rel-17 Response drafted in S2-2300620. Final response in S2-2302171 Replied to
4.1 S2-2300620 LS OUT Approval [DRAFT] LS on NAI format for 5G NSWO Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2300037. Revised to S2-2302171. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
4.1 S2-2302171 LS OUT Approval LS on NAI format for 5G NSWO SA WG2 Rel-17 Revision of S2-2300620. Approved Approved
4.1 - - - Positioning/Location - - Docs:=0 -
4.1 - - - Capability exposure - - Docs:=3 -
4.1 S2-2300009 LS In Action LS from 5G-ACIA: 5G capabilities exposure for factories of the future identified gaps 5G-ACIA (5G-ACIA-LS-2022-005) Revision of postponed S2-2210183 from S2#154. Responses drafted in S2-2300339, S2-2301189. Postponed Postponed
4.1 S2-2300339 LS OUT Approval [DRAFT] Reply LS on 5G capabilities exposure for factories of the future identified gaps (5G-ACIA-LS-2022-005 / S2-220xxxx) Ericsson Response to S2-2300009. Noted To be merged into S2-2301189 (Noted) Sang-Jun (Samsung) proposes to go with 1189 as the baseline merging 0339.
Laurent (Nokia): as the discussion seems to be in 1189, let's discuss a revision of 1189
Stefan (Ericsson) is OK to use 1189 as a base
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
4.1 S2-2301189 LS OUT Approval [DRAFT] Reply LS on 5G capabilities exposure for factories of the future identified gaps Huawei, HiSilicon Rel-18 Response to S2-2300009. Noted Sang-Jun (Samsung) proposes to go with 1189 as the baseline merging 0339.
Sebastian (Qualcomm) objects to r00 and provides r01
Dieter (Deutsche Telekom) agrees with Sebastian (Qualcomm).
Marco (Huawei) answers and provide r02
Stefan (Ericsson) provides comments and r03
Sebastian (Qualcomm) replies to Marco and objects to r02 and r03
Marco (Huawei) replies to Sebastian (Qualcomm)
Qianghua (Huawei) provides r04
Antoine (Orange) comments on G.2, G.4 and L.6.
Laurent (Nokia): provides r05
Antoine (Orange) provides r06, updating the analysis of G.2 and L.6 per earlier comments.
Laurent (Nokia): provides r07
==== Revisions Deadline ====
Sebastian (Qualcomm) can only accept r01 and objects to all other revisions for the reasons given earlier
Qianghua (Huawei) proposes to go with r07, cannot accept r01 as it is since we believe r01 doesn't provide any valuable information to plenary from technical PoV, OK to postpone
Antoine (Orange) also proposes to go with r07.
==== Final Comments Deadline ====
Noted
4.1 - - - VoLTE Roaming - - Docs:=3 -
4.1 S2-2300005 LS In Action LS from CT WG4: Reply to LS on VoLTE Roaming GBR Handling CT WG4 (C4-224401) Revision of postponed S2-2210171 from S2#154. Noted Chris (Vodafone) proposes to Note this LS as it was taken into account when we sent the LS in S2-2209969 back to GSMA at SA2#153e.
Haris(Qualcomm) proposes to NOTE
Noted
4.1 S2-2300007 LS In Action LS from SA WG4: DRAFT Reply LS to 3GPP SA2 on VoLTE Roaming GBR Handling SA WG4 (S4-221192) Revision of postponed S2-2210178 from S2#154. Noted Chris (Vodafone) proposes to Note this LS as it was taken into account when we sent the LS in S2-2209969 back to GSMA at SA2#153e.
Haris(Qualcomm) proposed to NOTE
Noted
4.1 S2-2300031 LS In Action LS from CT WG3: Reply to LS on VoLTE Roaming GBR Handling CT WG3 (C3-225510) Rel-17 Noted Haris(Qualcomm) proposes to NOTE
Chris (Vodafone) proposes to Note this LS as it does not conflict with the LS SA2 sent to GSMA in S2-2209969 at SA2#153e.
Noted
4.1 - - - MBS related - - Docs:=1 -
4.1 S2-2300036 LS In Action LS from CT WG4: Reply LS on Re-establishment of the MBS context during mobility registration update or service request procedure CT WG4 (C4-225562) Rel-18 Noted LiMeng (Huawei) suggest to mark this paper as NOTED. Noted
4.1 - - - Satellite - - Docs:=1 -
4.1 S2-2300022 LS In Information LS from CT WG1: Reply LS on Nudm_UEContextManagement service for satellite NG-RAN CT WG1 (C1-227090) Rel-17 Noted Noted
4.1 - - - Slicing - - Docs:=1 -
4.1 S2-2300088 LS In Information LS from ITU-T SG13: LS on initiation of new work item Y.CCO-req: 'Requirements of orchestration supporting confidential computing for network slices in IMT-2020 networks and beyond' ITU-T SG13 (SG13-LS39) Noted Peter Hedman (Ericsson) proposes to note the LS that is for info Noted
4.1 - - - Misc - - Docs:=16 -
4.1 S2-2300003 LS In Action LS from BBF: BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) BBF (LIAISE-542-5G-RG-Hybrid-Access-Requirements-00) Revision of postponed S2-2210167 from S2#154. Postponed Postponed
4.1 S2-2300033 LS In Information LS from CT WG4: LS on Enabling operators to deploy N32 purpose specific SEPPs CT WG4 (C4-225493) Rel-18 Noted Noted
4.1 S2-2300050 LS In Action LS from RAN WG2: Reply LS on GNSS integrity requirement provisioning RAN WG2 (R2-2213320) Rel-17 Noted Jianning (Xiaomi) provides comment Noted
4.1 S2-2300054 LS In Action LS from RAN WG3: Reply LS on Time Synchronization Status notification towards UE(s) RAN WG3 (R3-226774) Rel-18 Noted Noted
4.1 S2-2300057 LS In Action LS from RAN WG3: LS on static and dynamic TAC solutions for mobile IAB node RAN WG3 (R3-226831) Rel-18 Noted Hong (Qualcomm) proposes to NOTE the LS in, as it has already been handled with CRs in VMR (9.19.2). Noted
4.1 S2-2300061 LS In Information LS from SA WG1: Reply LS on PIN Management SA WG1 (S1-223538) Rel-18 Noted Pallab (Nokia) proposes to NOTE the incoming LS as it is only for information
Lalith(Samsung) also proposes to NOTE the incoming LS as it is only for information
Noted
4.1 S2-2300064 LS In Action LS from SA WG1: Reply LS on low latency communication applications to use RAN feedback on periodicity for scheduling SA WG1 (S1-223726) Rel-18 Noted Sang-Jun (Samsung) proposes to mark 0064 noted, as it is applied to TR conclusion and CRs in AI#9.18.1 and AI#9.18.2. Noted
4.1 S2-2300067 LS In Action LS from SA WG3: Reply LS on User consent for Application Detection SA WG3 (S3-223907) Rel-18 Noted Jungshin (Samsung) propose to NOTE the LS. Noted
4.1 S2-2300068 LS In Action LS from SA WG3: Reply LS on protection of the URSP rules from HPLMN SA WG3 (S3-223911) Rel-18 Noted Pallab (Nokia) proposes to NOTE the LS. Noted
4.1 S2-2300069 LS In Information LS from SA WG3 : Reply LS on the IMS Data Channel Security Mode SA WG3 (S3-223913) Rel-18 Noted Noted
4.1 S2-2300075 LS In Action LS from SA WG4: LS on split rendering in AR telephony communication SA WG4 (S4-221534) Rel-18 Noted Noted
4.1 S2-2300076 LS In Action LS from SA WG4: Reply LS on N6 PDU Set identification SA WG4 (S4-221548) Rel-18 Postponed Postponed
4.1 S2-2300077 LS In Action LS from SA WG4: Reply LS on the usage of DC application identifier in SDP SA WG4 (S4-221556) Rel-18 Noted Noted
4.1 S2-2300079 LS In Action LS from SA WG5: Reply LS on possibility of providing per UE speed and orientation on FS_eNA_Ph3 SA WG5 (S5-226547) Rel-18 Noted Noted
4.1 S2-2300089 LS In Information LS from ITU-T SG13: LS on the new work item Y.Arch_NGNe_ncp 'Architectural evolution of NGN control plane by applying SDN technology' ITU-T SG13 (SG13-LS43) Noted Noted
4.1 S2-2300092 LS In Information LS from TSG SA: Reply LS on Use Cases and requirements for industrial factory applications TSG SA (SP-221322) Noted Haris(Qualcomm) proposes to NOTE since no action is expected from SA2 Noted
4.2 - - - P-CRs/CRs related to use of inclusive language in 3GPP - - Docs:=0 -
5 - - - Pre-Rel-17 Maintenance (excluding all 5G topics) - - Docs:=0 -
5.1 - - - 3GPP Packet Access Maintenance - - Docs:=3 -
5.1 S2-2301002 CR Approval 23.682 CR0490 (Rel-17, 'F'): Removing inappropriate use of the term device Orange Rel-17 Revised to S2-2301225 Revised
5.1 S2-2301225 CR Approval 23.682 CR0490R1 (Rel-17, 'F'): Removing inappropriate use of the term device Orange Rel-17 Revision of S2-2301002. Check Affected Clauses! r02 agreed. Revised to S2-2301961. Hannu (Nokia) proposes to make this Rel-18 CR
Antoine (Orange) replies to Hannu.
Qian (Ericsson) share the same view as Hannu (Nokia)
Hannu (Nokia) replies to Antoine
Antoine (Orange) provides r01 (changing the Release to Rel-18) and replies to Qian.
Antoine (Orange) provide r02 (fixing the cover page).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
5.1 S2-2301961 CR Approval 23.682 CR0490R2 (Rel-18, 'F'): Removing inappropriate use of the term device Orange Rel-18 Revision of S2-2301225r02. 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:=0 -
6.2 - - - Common Access Control, RM and CM functions and procedure flows - - Docs:=5 -
6.2 S2-2300024 LS In Action LS from CT WG1: LS on mapped NSSAI CT WG1 (C1-227103) Rel-18 Noted Peter Hedman (Ericsson) proposes to note the LS as issue handled by the related CRs Noted
6.2 S2-2301149 CR Approval 23.501 CR3729R1 (Rel-17, 'F'): Mapped NSSAI when UE is roaming Ericsson, Qualcomm Incorporated, Apple, ZTE, MediaTek Inc. Rel-17 Revision of S2-2208762. r01 agreed. Revised to S2-2301962. Hannu (Nokia) shares r01, co-signs the CR and points out that also on the Rel-18 mirror CR needs to be revised once we have agreed the wording.
Peter Hedman (Ericsson) provides reply
Peter Hedman (Ericsson) provides comments and prefer r00 wording + adding co-signer
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and again prefer r00 wording + adding co-signer
Hannu (Nokia) replies to Peter and still prefers r01 with possible replacement of 'it' by 'the UE'
Peter Hedman (Ericsson) provides comments and can accept r01 + replace 'it' with 'UE'
==== Final Comments Deadline ====
Revised
6.2 S2-2301962 CR Approval 23.501 CR3729R2 (Rel-17, 'F'): Mapped NSSAI when UE is roaming Ericsson, Qualcomm Incorporated, Apple, ZTE, MediaTek Inc., Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2301149r01. Approved Agreed
6.2 S2-2301150 CR Approval 23.501 CR4076 (Rel-18, 'A'): Mapped NSSAI when UE is roaming Ericsson, Qualcomm Incorporated, Apple, ZTE, MediaTek Inc. Rel-18 Revised to S2-2301963. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
6.2 S2-2301963 CR Approval 23.501 CR4076R1 (Rel-18, 'A'): Mapped NSSAI when UE is roaming Ericsson, Qualcomm Incorporated, Apple, ZTE, MediaTek Inc., Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301150. Approved Agreed
6.3 - - - Session management and continuity functions and flows - - Docs:=5 -
6.3 S2-2300262 CR Approval 23.502 CR3691 (Rel-18, 'F'): Correcting the step of H-SMF providing Always-On PDU Session granted indication Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.3 S2-2301063 CR Approval 23.502 CR3833 (Rel-18, 'F'): Alignment with stage 3 on handling of UDM deregistration of SMF Nokia, Nokia Shanghai Bell Rel-18 Check Affected Clauses! r02 agreed. Revised to S2-2301964. Shabnam (Ericsson) provides comments and r01 and co-signs as also supports the principle to reflect appropriate stage 3 function missing which lead to some misdirection in stage 2 discussion.
Fenqin (Huawei) provides comments.
Hannu (Nokia) thanks Shabnam for support and can agree either r00 or r01
Hannu (Nokia) replies to Fenqin and explains why some version of the change is needed.
Fenqin (Huawei) provides further comments.
Shabnam (Ericsson) provides comments and responds to Huawei
Hannu (Nokia) points out that r01 enumerates the SMF deregistration reasons that were missing from SA2 specifications also on the cover page as requested by Fenqin.
Jinguo(ZTE) provides r02
==== Revisions Deadline ====
Hannu (Nokia) supports r02
Fenqin (Huawei) we can live with r02.
==== Final Comments Deadline ====
Revised
6.3 S2-2301964 CR Approval 23.502 CR3833R1 (Rel-18, 'F'): Alignment with stage 3 on handling of UDM deregistration of SMF Nokia, Nokia Shanghai Bell, Ericsson, ZTE Rel-18 Revision of S2-2301063r02. Approved Agreed
6.3 S2-2301088 CR Approval 23.501 CR4058 (Rel-18, 'F'): Restructuring of user plane management clause Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301965. Stefan (Ericsson) provides comments
Mirko (Huawei) responds and provides r01.
Laurent (Nokia): Comments, not sure we need this reshuffling
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
6.3 S2-2301965 CR Approval 23.501 CR4058R1 (Rel-18, 'F'): Restructuring of user plane management clause Huawei, HiSilicon Rel-18 Revision of S2-2301088r01. Approved Agreed
6.4 - - - Security related functions and flows - - Docs:=0 -
6.5 - - - QoS concept and functionality - - Docs:=0 -
6.6 - - - Policy and charging control - - Docs:=18 -
6.6 S2-2300973 CR Approval 23.503 CR0872 (Rel-17, 'F'): Corrections to use of RSD validation criteria in URSP rules Nokia, Nokia Shanghai Bell Rel-17 r00 agreed. Revised to S2-2301966. ==== Revisions Deadline ====
Pallab (Nokia) proposes to re-open this at CC#3. There were some discussions in 0974 (mirror CR) to add a NOTE. 0973 shall also be revised to add the same NOTE as below:
NOTE: The precedence set for the different Route Selection Descriptors in a URSP rule has to ensure that Route Selection Descriptors that contain a Time Window or Location Criteria are checked before Route Selection Descriptors that do not contain a Time Window or Location Criteria.
==== Final Comments Deadline ====
Revised
6.6 S2-2301966 CR Approval 23.503 CR0872R1 (Rel-17, 'F'): Corrections to use of RSD validation criteria in URSP rules Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2300973r00. Approved Agreed
6.6 S2-2300974 CR Approval 23.503 CR0873 (Rel-18, 'A'): Corrections to use of RSD validation criteria in URSP rules Nokia, Nokia Shanghai Bell Rel-18 Mirror CR should have same WI Code as base CR. r01 agreed. Revised to S2-2301967. Pallab (Nokia) provides r01 to correct cover sheet
Mirko (Huawei) comments.
Pallab (Nokia) responds to Mirko (Huawei)
Mirko (Huawei) responds.
==== Revisions Deadline ====
Josep (DT) would suggest to try the CC. The change is small and there is agreement.
Pallab (Nokia) proposes to approve r01 + below NOTE. Separate email will be sent to re-open 0973 to add the same NOTE
NOTE: The precedence set for the different Route Selection Descriptors in a URSP rule has to ensure that Route Selection Descriptors that contain a Time Window or Location Criteria are checked before Route Selection Descriptors that do not contain a Time Window or Location Criteria.
Mirko (Huawei) supports the proposal of Pallab (Nokia) and Josep (CC).
==== Final Comments Deadline ====
Revised
6.6 S2-2301967 CR Approval 23.503 CR0873R1 (Rel-18, 'A'): Corrections to use of RSD validation criteria in URSP rules Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300974r01. Approved Agreed
6.6 S2-2300187 CR Approval 23.503 CR0801 (Rel-16, 'F'): PDU Session Type Selection in the URSP Rule Ericsson Rel-16 TEI WI Code should be TEI16. r05 agreed. Revised to S2-2301968. Pallab (Nokia) responds to Hong (Qualcomm).
Hong (Qualcomm) replies to Pallab.
Pallab (Nokia) comments and thinks that this CR is not correct and can be NOTED.
Hong (Qualcomm) agrees with Antoine (Orange), and suggest to change the IE to 'Mandatory' and remote NOTE 8.
Antoine (Orange) comments that it would be clearer to set this IE to 'Mandatory' and remove NOTE 8.
Dimitris (Lenovo) supports Pallab (Nokia) view
Belen (Ericsson) provides r01, fixing cover page, replies to comments.
Josep (DT) comments, proposes 'conditional', provides r02.
Pallab (Nokia) comments and requests for clarification
Mehrdad (MediaTek Inc.) comments and requests some revisions + suggests an LS to CT1.
Belen (Ericsson) clarifies and answers comments from MediaTek and Nokia.
Mehrdad (MediaTek Inc.) replies to Ericsson
Josep (DT) comments.
Haiyang (Huawei) provides r03.
Pallab (Nokia) provides comments.
Haiyang (Huawei) reply.
Belen (Ericsson) is fine with r03.
Mehrdad (MediaTek Inc.) is OK with r03.
Pallab (Nokia) Nokia is OK with r03.
Josep (DT) is OK with r03.
Antoine (Orange) provides r04 to remove an extra '.'.
Belen (Ericsson) provides r05, alternative wording in the NOTE
Mehrdad (MediaTek Inc.) still prefers r03 or r04
Pallab (Nokia) prefers the NOTE wording proposed in r05
Haiyang (Huawei) provides r06.
Huazhang (vivo) reply to Haiyang
==== Revisions Deadline ====
Belen (Ericsson) suggests to approved r05, cannot accept r06
Mehrdad (MediaTek Inc.) prefers r06 or r04 but can live with r05.
==== Final Comments Deadline ====
Revised
6.6 S2-2301968 CR Approval 23.503 CR0801R1 (Rel-16, 'F'): PDU Session Type Selection in the URSP Rule Ericsson Rel-16 Revision of S2-2300187r05. Approved Agreed
6.6 S2-2300188 CR Approval 23.501 CR3838 (Rel-16, 'F'): PDU Session Type Selection in the URSP Rule Ericsson Rel-16 Confirm Spec version used - CR states 18.0.0! TEI WI Code should be TEI16. r05 agreed. Revised to S2-2301969. Pallab (Nokia) comments and provides r02.
Hong (Qualcomm) comments and provides r01.
Antoine (Orange) comments.
Josep (DT) comments on the cover sheet statis Rel'18.
Huazhang (vivo) provide comments about the compatible of former UE
Belen (Ericsson) provides r03, fixing cover page, asking questions.
Mehrdad (MediaTek Inc.) thinks wording in r02 is in the right direction
Belen (Ericsson) asks again to MediaTek, Nokia and Lenovo to provide their understanding,
Mehrdad (MediaTek Inc.) clarifies to Ericsson that we are fine with either r02 or r03.
Haiyang (Huawei) is OK with r03
Pallab (Nokia) responds to Belen(Ericsson). Agrees with the understanding that PDU Session Type is conditional. OK with r03
Belen (Ericsson) provides r04, replies to comments.
Pallab (Nokia) comments.
Mehrdad (MediaTek Inc.) comments in r04
Hong (Qualcomm) comments.
Haiyang (Huawei) suggests to refer to 503 directly..
Belen (Ericsson) provides r05 to address QC and Nokia comments. Replies to Huawei
Pallab (Nokia) OK with r05
==== Revisions Deadline ====
Haiyang (Huawei) can accept r05
Huazhang (vivo) can accept r05
Mehrdad (MediaTek Inc.) is OK with r05.
Belen (Ericsson) is okay with r05
==== Final Comments Deadline ====
Revised
6.6 S2-2301969 CR Approval 23.501 CR3838R1 (Rel-16, 'F'): PDU Session Type Selection in the URSP Rule Ericsson Rel-16 Revision of S2-2300188r05. Approved Agreed
6.6 S2-2300189 CR Approval 23.503 CR0802 (Rel-17, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-17 Confirm Spec version used - CR states 17.6.0! TEI WI Code should be TEI16. r02 + changed note agreed. Revised to S2-2301970. Belen (Ericsson) provides r01, fixing cover page.
Belen (Ericsson) provides r02 to align with the proposed NOTE for Rel16 CR.
Pallab (Nokia) prefers the NOTE wording proposed in r02
==== Revisions Deadline ====
Mehrdad (MediaTek Inc.) prefers a wording like S2-2300187r06 or S2-2300187r04 but can live with r02.
==== Final Comments Deadline ====
Revised
6.6 S2-2301970 CR Approval 23.503 CR0802R1 (Rel-17, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-17 Revision of S2-2300189r02 + changed note. Approved Agreed
6.6 S2-2300191 CR Approval 23.503 CR0803 (Rel-18, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-18 Confirm Spec version used - CR states 17.6.0! TEI WI Code should be TEI16. r02 agreed. Revised to S2-2301971. Belen (Ericsson) provides r01, fixing cover page.
Belen (Ericsson) provides r02, a mirror of Rel17 CR
Pallab (Nokia) prefers the NOTE wording proposed in r02
Mehrdad (MediaTek Inc.) replies to Qualcomm
Hong (Qualcomm) comments.
Mehrdad (MediaTek Inc.) thinks r02 wording can not work for Rel-18.
==== Revisions Deadline ====
Belen (Ericsson) prefers to keep NOTE as is in r02
Mehrdad (MediaTek Inc.) can live with r02 with the understanding that any potential alignment to Rel-18 WIs to be addressed by next meetings.
Hong (Qualcomm) is fine with r02.
==== Final Comments Deadline ====
Revised
6.6 S2-2301971 CR Approval 23.503 CR0803R1 (Rel-18, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-18 Revision of S2-2300191r02. Approved Agreed
6.6 S2-2300190 CR Approval 23.501 CR3839 (Rel-17, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-17 Confirm CR Number - CR states 3840!. Confirm Spec version used - CR states 18.0.0! TEI WI Code should be TEI16. Revised to S2-2301972. Belen (Ericsson) provides r01, fixing cover page.
Huazhang (vivo) prefers to undo the changes in 5.6.1 based on r01
Belen (Ericsson) agrees with vivo that needs updates to align with Rel16 CR and address legacy UEs.
Huazhang (vivo) provides r02 based on r01, to undo the change 2 that to keep the network can still recover the PDU session type for the legacy UE in R16 and R17.
==== Revisions Deadline ====
Mehrdad (MediaTek Inc.) thanks Ericsson for clarification. We are fine with it. I assume the same mirroring applies to S2-2300192 for Rel-18.
Belen (Ericsson) thinks that this CR is a mirror, so I will copy the text that has been agreed for Rel16
Mehrdad (MediaTek Inc.) thinks this CR wording should be aligned with S2-2300188r05. Let's clarify this in CC#3 or CC#4
Belen (Ericsson) says that the same mirror applies for S2-2300192 for Rel-18.
==== Final Comments Deadline ====
Revised
6.6 S2-2301972 CR Approval 23.501 CR3839R1 (Rel-17, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-17 Revision of S2-2300190. Approved Agreed
6.6 S2-2300192 CR Approval 23.501 CR3840 (Rel-18, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-18 Revised to S2-2301973. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
6.6 S2-2301973 CR Approval 23.501 CR3840R1 (Rel-18, 'A'): PDU Session Type Selection in the URSP Rule Ericsson Rel-18 Revision of S2-2300192. Approved Agreed
6.6 S2-2301159 CR Approval 23.503 CR0885 (Rel-17, 'F'): Control Request Triggers relevant for AMF for Non-3GPP access Huawei, HiSilicon Rel-17 Check Affected Clauses!. Confirm CR Number - CR states 8356! Postponed Pallab (Nokia) provides comments.
Hannu (Nokia) asks what the SMF, AMF, PCF are expected to do when the policy control trigger is armed by the UE is registered only via the Access Type where the armed trigger is not applicable?
Stefan (Ericsson) provides comments
Marco (Huawei) answer to Pallab (Nokia) and Stefan (Ericsson) and provide r01
Pallab (Nokia) comments and provides r02.
Myungjune (LGE) provides r03.
Pallab (Nokia) responds to Marco (Huawei)
Marco (Huawei) replies to Pallab (Nokia)
Stefan (Ericsson) provides comments and questions
Marco (Huawei) I propose to postpone since we are close to revision deadline and more discussion is required
Stefan (Ericsson) provides r04, but also ok to postpone
==== Revisions Deadline ====
Marco(Huawei) prefer to postpone
Stefan (Ericsson) OK to postpone
==== Final Comments Deadline ====
Postponed
6.6 S2-2301174 CR Approval 23.503 CR0886 (Rel-18, 'A'): Control Request Triggers relevant for AMF for Non-3GPP access Huawei, HiSilicon Rel-18 Check Affected Clauses! Postponed Marco (Huawei) I propose to postpone since we are close to revision deadline and more discussion is required
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
6.7 - - - 3GPP access specific functionality and flows - - Docs:=4 -
6.7 S2-2300218 CR Approval 23.501 CR3847 (Rel-17, 'F'): Emergency configuration data update Ericsson Rel-17 Approved Ashok (Samsung) ask whether the CR is needed?
Qian (Ericsson) provides answer
Ashok (Samsung) responds to Qian (Ericsson)
Qian (Ericsson) provides further comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.7 S2-2300219 CR Approval 23.501 CR3848 (Rel-18, 'A'): Emergency configuration data update Ericsson Rel-18 Approved Ashok (Samsung) same comment as S2-2300218
Qian (Ericsson) provides answer
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.7 S2-2300263 CR Approval 23.501 CR3594R1 (Rel-18, 'D'): RRC state and CM state terminology alignment Ericsson Rel-18 Revision of S2-2202190. Approved Hannu (Nokia) supports the CR and congratulates the originator for finding a valid Cat D CR that is also useful.
Judy (Ericsson) thanks Hannu (Nokia) for his support
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.7 S2-2300264 CR Approval 23.502 CR3432R1 (Rel-18, 'D'): RRC state and CM state terminology alignment Ericsson Rel-18 Revision of S2-2202191. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.8 - - - Specific services support - - Docs:=1 -
6.8 S2-2301062 CR Approval 23.501 CR4049 (Rel-18, 'F'): Corrections of Nudm service operations list Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
6.9 - - - Interworking and Migration - - Docs:=0 -
6.10 - - - Non-3GPP access specific functionality and flows - - Docs:=0 -
6.11 - - - Framework functions - - Docs:=0 -
7 - - - Rel-16 Maintenance for 5G (excluding 5GS_Ph1) - - Docs:=0 -
7.1 - - - Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) - - Docs:=3 -
7.1 S2-2300364 CR Approval 23.287 CR0188 (Rel-17, 'F'): Removal of V2X policy request during registration procedure LG Electronics, Ericsson, CATT, Huawei, ZTE, OPPO Rel-17 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
7.1 S2-2300365 CR Approval 23.503 CR0821 (Rel-17, 'F'): Removal of V2X policy request during registration procedure LG Electronics, Ericsson, CATT, Huawei, ZTE, OPPO Rel-17 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
7.1 S2-2300366 CR Approval 23.503 CR0822 (Rel-18, 'A'): Removal of V2X policy request during registration procedure LG Electronics, Ericsson, CATT, Huawei, ZTE, OPPO Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
7.2 - - - Wireless and Wireline Convergence for the 5G system architecture (5WWC) - - Docs:=0 -
7.3 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) - - Docs:=0 -
7.4 - - - Cellular IoT support and evolution for the 5G System (5G_CIoT) - - Docs:=0 -
7.5 - - - Enablers for Network Automation for 5G (eNA) - - Docs:=0 -
7.6 - - - Enhancement to the 5GC Location Services (5G_eLCS) - - Docs:=6 -
7.6 S2-2301262 CR Approval 23.273 CR0292 (Rel-16, 'F'): AMF instead of LMF for NI and HO Nokia, Nokia Shanghai Bell Rel-16 r01 agreed. Revised to S2-2301974. Leo (Deutsche Telekom) comments and requests update of CR
Cai Simon (Nokia) provides r01
Guillaume (MediaTek Inc.) comments: WI Code is wrong.
Cai Simon (Nokia) clarifies to Guillaume (MediaTek Inc.)
==== Revisions Deadline ====
Leo (Deutsche Telekom) is fine with r01, objects original version.
==== Final Comments Deadline ====
Revised
7.6 S2-2301974 CR Approval 23.273 CR0292R1 (Rel-16, 'F'): AMF instead of LMF for NI and HO Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2301262r01. Approved Agreed
7.6 S2-2301263 CR Approval 23.273 CR0293 (Rel-17, 'F'): AMF instead of LMF for NI and HO correlation with GMLC Nokia, Nokia Shanghai Bell Rel-17 Should be Cat A? Mirror CR should have same WI Code as base CR. r01 agreed. Revised to S2-2301975. Leo (Deutsche Telekom) comments and requests update of CR
Cai Simon (Nokia) provides r01
Guillaume (MediaTek Inc.) comments: WI Code is wrong.
Cai Simon (Nokia) clarifies to Guillaume (MediaTek Inc.)
==== Revisions Deadline ====
Leo (Deutsche Telekom) is fine with r01, objects original version.
==== Final Comments Deadline ====
Revised
7.6 S2-2301975 CR Approval 23.273 CR0293R1 (Rel-17, 'A'): AMF instead of LMF for NI and HO correlation with GMLC Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2301263r01. Approved Agreed
7.6 S2-2301264 CR Approval 23.273 CR0294 (Rel-18, 'A'): AMF instead of LMF for NI and HO correlation with GMLC Nokia, Nokia Shanghai Bell Rel-18 Mirror CR should have same WI Code as base CR. r01 agreed. Revised to S2-2301976. Leo (Deutsche Telekom) comments and requests update of CR
Cai Simon (Nokia) provides r01
Guillaume (MediaTek Inc.) comments: WI Code is wrong.
Cai Simon (Nokia) clarifies to Guillaume (MediaTek Inc.)
==== Revisions Deadline ====
Leo (Deutsche Telekom) is fine with r01, objects original version.
==== Final Comments Deadline ====
Revised
7.6 S2-2301976 CR Approval 23.273 CR0294R1 (Rel-18, 'A'): AMF instead of LMF for NI and HO correlation with GMLC Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301264r01. Approved Agreed
7.7 - - - 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) - - Docs:=4 -
7.7 S2-2301252 CR Approval 23.501 CR4100 (Rel-17, 'F'): UDM determination Internal Group ID values for 5G VN group management Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2301977. Sang-Jun (Samsung) asks for clarification.
Stefan (Ericsson) provides r01
Laurent (Nokia): provides r02
Qianghua (Huawei) provides comment and only agrees r01 for compromise
Stefan (Ericsson) agrees with Qianghua (Huawei)
Laurent (Nokia): provides r03
==== Revisions Deadline ====
Qianghua (Huawei) only accepts r01, objects the other revisions (incl. original)
Stefan (Ericsson) has same view: only accepts r01, objects the other revisions (incl. original)
Yannick (Convenor): r01 seems to be the only remaining option, asks if r01 could be acceptable.
Sang-Jun (Samsung) is OK with r01
Laurent (Nokia): OK with R01 (much better than current spec)
==== Final Comments Deadline ====
Revised
7.7 S2-2301977 CR Approval 23.501 CR4100R1 (Rel-17, 'F'): UDM determination Internal Group ID values for 5G VN group management Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2301252r01. Approved Agreed
7.7 S2-2301253 CR Approval 23.501 CR4101 (Rel-18, 'A'): UDM determination Internal Group ID values for 5G VN group management Nokia, Nokia Shanghai Bell Rel-18 Mirror CR should have same WI Code as base CR. Revised to S2-2301978. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
7.7 S2-2301978 CR Approval 23.501 CR4101R1 (Rel-18, 'A'): UDM determination Internal Group ID values for 5G VN group management Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301253. Approved Agreed
7.8 - - - Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - - Docs:=0 -
7.9 - - - Architecture enhancements for the support of Integrated access and backhaul (IABARC) - - Docs:=0 -
7.10 - - - Enhancement of URLLC supporting in 5GC (5G_URLLC) - - Docs:=9 -
7.10 S2-2301083 CR Approval 23.503 CR0881 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 Revised to S2-2301454. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
7.10 S2-2301454 CR Approval 23.503 CR0881R1 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 Revision of S2-2301083. Approved Agreed
7.10 S2-2301084 CR Approval 23.501 CR4056 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 CC#4: r05 + changes agreed. Revised to S2-2301455. Tricci <OPPO> thanks Mirko et al for the great effort for the alignment of the QoS Monitoring support in 5GC. OPPO supports the effort and would like to propose some minor update for consistency on the descriptions.
Mirko (Huawei) responds.
Shabnam (Ericsson) provides comments and r01, adding missing functionality
Xiaowan Ke(vivo) provides comments and proposals
David (Samsung) provides comments
Xiaowan Ke(vivo) comments and provides r02
Mirko (Huawei) responds and provides r03.
Jinhua (Xiaomi) provides comments
Tricci (OPPO) asks Jinhua (Xiaomi) for further clarifications for Xiaomi question.
Jinhua (Xiaomi) replies to Tricci and Mirko,
Xiaowan(vivo) comments and provides r04
Mirko (Huawei) responds and provides r05.
==== Revisions Deadline ====
Shabnam (Ericsson) provides r06, though late but important to fix some aspects
Devaki (Nokia) proposes to approve r05 without the EN as the EN is outside the scope of our CRs (also, unable to find r06 in the server, can r06 be uploaded to the revisions folder, is possible, please?). Unclear which SID/WID triggered the EN, also which WID would we use to resolve this?
Shabnam (Ericsson) provides comments that we should not have ENs on rapporteurs CRs and also there is a missing functionality I added as r06 late, but I may have used wrong baseline.
Mirko (Huawei) is fine with removing the EN and updating the Note as suggested by Devaki.
Shabnam (Ericsson) provides comments that we have issues with r05, I provided late r06 but it was not based on r05. Propose to merge r05+changes and r06 additions,provide revision r07 for CC#4 as this is needed as baseline.
Removed EN.
added in clause 5.x.1 NOTE:
NOTE: The QoS parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2.
5.33.3.1, changes are to add that SMF action is an option, not to rule out other option that exists:
The SMF can configure the UPF to report the QoS monitoring results for the QoS Flow as described in clause 5.8.2.X with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration.
5.33.3.3 changes:
The UPF reports the QoS Monitoring results to the SMF baseds on some specific conditions e.g. first time, periodic, event triggered.
and moved the reporting reference at the end of the clause:
If SMF has configured the UPF to report QoS monitoring for the QoS Flow, the UPF reports the QoS Monitoring results as described in clause 5.8.2.X.
==== Final Comments Deadline ====
Shabnam (Ericsson) provides comments that we have issues with r05, I provided late r06 but it was not based on r05. Propose to merge r05+changes and r06 additions,provide revision r07 for CC#4 as this is needed as baseline.
Removed EN.
added in clause 5.x.1 NOTE:
NOTE: The QoS parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2.
5.33.3.1, changes are to add that SMF action is an option, not to rule out other option that exists:
The SMF can configure the UPF to report the QoS monitoring results for the QoS Flow as described in clause 5.8.2.X with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration.
5.33.3.3 changes:
The UPF reports the QoS Monitoring results to the SMF baseds on some specific conditions e.g. first time, periodic, event triggered.
and moved the reporting reference at the end of the clause:
If SMF has configured the UPF to report QoS monitoring for the QoS Flow, the UPF reports the QoS Monitoring results as described in clause 5.8.2.X.
Mirko (Huawei) proposes r08 as outcome of further offline discussion with Shabnam (Ericsson) for checking in CC#4. It is based on r05 with the following changes:
1. Removal of editor's note in clause 5.X.1,
2. Update of note in clause 5.X.1 to: 'The QoS parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2.',
3. Addition of the following text to the last but one bullet in clause 5.33.3.3: 'The UPF reports the measurement results to the SMF based on some specific conditions e.g. first time, periodic, event triggered, when thresholds for reporting towards SMF (via N4) are reached.'
Revised
7.10 S2-2301455 CR Approval 23.501 CR4056R1 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 CC#4: Revision of S2-2301084r05 + changes. Approved Agreed
7.10 S2-2301085 CR Approval 23.502 CR3838 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 Revised to S2-2301456. Antoine (Orange) asks if we really need to introduce Local NEF in 501/502 and comments on the title and place of the new clause.
Mirko (Huawei) responds.
Antoine (Orange) replies.
==== Revisions Deadline ====
Devaki (Nokia) comments
Antoine (Orange) objects r00 unless the following EN is added: 'It is FFS whether Local NEF is introduced or NEF is used instead.'
Mirko (Huawei) suggests to approve this CR with the understanding that further updates of the new clause 4.15.X Event Exposure using Local NEF can be expected.
==== Final Comments Deadline ====
Revised
7.10 S2-2301456 CR Approval 23.502 CR3838R1 (Rel-18, 'F'): Generalization of QoS monitoring control description Huawei (Rapporteur), Nokia (Rapporteur), Ericsson (Rapporteur) Rel-18 Revision of S2-2301085. Approved Agreed
7.10 S2-2301086 CR Approval 23.503 CR0882 (Rel-18, 'F'): Removal of unspecified QoS monitoring control options Huawei Rel-18 Postponed Shabnam (Ericsson) provides comments that the functions have been well specified in stage 3 since Rel-16 (some parts) and any removal needs further actions before proceeding, see below
Mirko (Huawei) responds.
Shabnam (Ericsson) provides comments if we should send an LS from SA2 to CT3/4 and also allow companies to check from this meeting?
==== Revisions Deadline ====
Devaki (Nokia) comments that it would be preferrable to allow companies to check until February meeting (and only approve in Feb. or send an LS out to CT3 from next meeting). Proposes to postpone for now.
Mirko (Huawei) is ok with postponing.
==== Final Comments Deadline ====
Postponed
7.10 S2-2301087 CR Approval 23.501 CR4057 (Rel-18, 'F'): Clarifications for GTP-U Path Monitoring Huawei Rel-18 r01 agreed. Revised to S2-2301979. Shabnam (Ericsson) provides comments that some of the changes are in our view incorrect/not aligned with stage 3, provides further input
Mirko (Huawei) responds.
Shabnam (Ericsson) provides comments that a revision would be helpful, from our perspective we prefer to keep the text being removed and add reference to stage 3 specs for details.
Mirko (Huawei) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
7.10 S2-2301979 CR Approval 23.501 CR4057R1 (Rel-18, 'F'): Clarifications for GTP-U Path Monitoring Huawei Rel-18 Revision of S2-2301087r01. Approved Agreed
7.11 - - - Enhancement of Network Slicing (eNS) - - Docs:=0 -
7.12 - - - Optimisations on UE radio capability signalling (RACS) - - Docs:=0 -
7.13 - - - Enhanced IMS to 5GC Integration (eIMS5G_SBA) - - Docs:=1 -
7.13 S2-2300010 LS In Information LS from GSMA IDCTF: LS from NG to 3GPP SA3 on IMS Data Channel Security Mode GSMA IDCTF (UPG04_109) Revision of postponed S2-2210184 from S2#154. Noted Rainer (Nokia) proposes to note the LS. Noted
7.14 - - - User Data Interworking and Coexistence (UDICoM) - - Docs:=0 -
7.15 - - - Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) - - Docs:=0 -
7.16 - - - 5GS Transfer of Policies for Background Data Transfer (xBDT) - - Docs:=0 -
7.17 - - - Single radio voice continuity from 5GS to 3G (5G_SRVCC) - - Docs:=0 -
8 - - - Rel-17 WIDs - - Docs:=0 -
8.1 - - - Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) - - Docs:=25 -
8.1 S2-2301053 CR Approval 23.288 CR0676 (Rel-17, 'F'): Corrections to Data Delivery and Data Collection via DCCF and via MFAF Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.1 S2-2301310 CR Approval 23.288 CR0695 (Rel-18, 'A'): Corrections to Data Delivery and Data Collection via DCCF and via MFAF Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.1 S2-2300120 CR Approval 23.288 CR0607 (Rel-17, 'F'): Corrections on immediate notification in subscription response Ericsson Rel-17 r01 agreed. Revised to S2-2302064. Yannick (Nokia): Nokia provides suggestion.
Zhang (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.1 S2-2302064 CR Approval 23.288 CR0607R1 (Rel-17, 'F'): Corrections on immediate notification in subscription response Ericsson Rel-17 Revision of S2-2300120r01. Approved Agreed
8.1 S2-2301311 CR Approval 23.288 CR0696 (Rel-18, 'A'): Corrections on immediate notification in subscription response Ericsson Rel-18 Revised to S2-2302065. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.1 S2-2302065 CR Approval 23.288 CR0696R1 (Rel-18, 'A'): Corrections on immediate notification in subscription response Ericsson Rel-18 Revision of S2-2301311. Approved Agreed
8.1 S2-2301187 CR Approval 23.288 CR0686 (Rel-18, 'A'): Adding transferred Analytics ID in Subscription Change Notification ZTE Rel-18 Postponed Zhang (Ericsson) object the paper
Jinguo(ZTE) replies to Zhang (Ericsson)
Yannick (Nokia): Nokia concurs with Ericsson.
Leo (Deutsche Telekom) comments on r00
Jinguo(ZTE) thanks Leo(DT) and response to Yannick (Nokia) and Zhang (Ericsson)
Zhang (Ericsson) response to Jinguo (ZTE)
Yannick (Nokia): Nokia responds to ZTE.
Jinguo(ZTE) replies to Yannick(Nokia)
Jinguo(ZTE) provides r01
==== Revisions Deadline ====
Zhang (Ericsson) propose to postpone the paper
Jinguo(ZTE) replies to Zhang (Ericsson) and believe the problem needs to be addressed.
Yannick (Nokia): Nokia prefers to postpone.
==== Final Comments Deadline ====
Postponed
8.1 S2-2301186 CR Approval 23.288 CR0685 (Rel-17, 'F'): Adding transferred Analytics ID in Subscription Change Notification ZTE Rel-17 Postponed Zhang (Ericsson) object the paper
Jinguo(ZTE) replies to Zhang (Ericsson)
Leo (Deutsche Telekom) comments on r00
Jinguo(ZTE) provides r01
==== Revisions Deadline ====
Zhang (Ericsson) propose to postpone the paper
Jinguo(ZTE) replies to Zhang (Ericsson) and believe the problem needs to be addressed.
Yannick (Nokia): Nokia prefers to postpone, see my comments to S2-2301187.
==== Final Comments Deadline ====
Postponed
8.1 S2-2300999 CR Approval 23.288 CR0668 (Rel-18, 'F'): NWDAF discovery with overlapping Serving Areas Orange Rel-18 Postponed Zhang (Ericsson) ask for clarification
Antoine (Orange) replies to Zhang.
Zhang (Ericsson) response to Antonie (orange)
Juan Zhang (Qualcomm) asks for clarification.
Juan Zhang (Qualcomm) provides comments.
Antoine (Orange) replies and provides r01 (removing the last sentence).
Yannick (Nokia): Nokia provides comments and questions.
Antoine (Orange) replies to Nokia.
==== Revisions Deadline ====
Yannick (Nokia): Nokia requests to postpone this CR and the related CR in S2-2301000.
==== Final Comments Deadline ====
Postponed
8.1 S2-2301000 CR Approval 23.501 CR4037 (Rel-18, 'F'): NWDAF discovery with overlapping Serving Areas Orange Rel-18 Postponed Zhang (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
8.1 S2-2300730 CR Agreement 23.288 CR0650 (Rel-17, 'F'): Correction for NEF service for correlating UE data collection and NWDAF request Samsung Rel-17 Noted Belen (Ericsson) provides comments
Hyesung (Samsung) replies
Belen (Ericsson) objects to this CR, it is incorrect in our view. Asks to postpone the discussion,
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.1 S2-2300833 CR Agreement 23.288 CR0660 (Rel-18, 'A'): Correction for NEF service for correlating UE data collection and NWDAF request Samsung Rel-18 Mirror CR should have same WI Code as base CR. Noted Belen (Ericsson) objects to this mirror CR, it is incorrect in our view. Asks to postpone the discussion.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.1 S2-2300743 CR Agreement 23.502 CR3783 (Rel-17, 'F'): NEF service used in correlating UE data collection and NWDAF request Samsung Rel-17 Noted Belen (Ericsson) provides comments
Hyesung (Samsung) replies
Belen (Ericsson) objects to this CR, it is incorrect in our view. Asks to postpone the discussion,
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.1 S2-2300825 CR Agreement 23.502 CR3794 (Rel-18, 'A'): NEF service used in correlating UE data collection and NWDAF request Samsung Rel-18 Mirror CR should have same WI Code as base CR. Noted Belen (Ericsson) objects to this mirror CR, it is incorrect in our view. Asks to postpone the discussion,
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.1 S2-2300094 LS In Action LS from CT WG3: LS on Issues on historical analytics and Slice Load Level Analytics CT WG3 (C3-225599) Response drafted in S2-2300717. Final response in S2-2302061 Replied to
8.1 S2-2300717 LS OUT Approval [DRAFT] Reply LS on Issues on historical analytics and Slice Load Level Analytics Huawei, HiSilicon Rel-17 Response to S2-2300094. Revised to S2-2302061. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.1 S2-2302061 LS OUT Approval Reply LS on Issues on historical analytics and Slice Load Level Analytics SA WG2 Rel-17 Revision of S2-2300717. Approved Approved
8.1 S2-2300212 CR Approval 23.288 CR0613 (Rel-17, 'F'): Corrections for historical analytics collection Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2302066. Belen (Ericsson) provides comments
Susan (Huawei): share the same view as Belen and propose to discuss in S2-2300716 thread.
Yannick (Nokia): Nokia replies to Ericsson's question.
Susan (Huawei): provides r01.
==== Revisions Deadline ====
Yannick (Nokia): Nokia provides r02.
==== Final Comments Deadline ====
Revised
8.1 S2-2302066 CR Approval 23.288 CR0613R1 (Rel-17, 'F'): Corrections for historical analytics collection Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2300212r02. Approved Agreed
8.1 S2-2300213 CR Approval 23.288 CR0614 (Rel-18, 'A'): Corrections for historical analytics collection Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2302067. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.1 S2-2302067 CR Approval 23.288 CR0614R1 (Rel-18, 'A'): Corrections for historical analytics collection Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300213. Approved Agreed
8.1 S2-2300716 CR Approval 23.288 CR0648 (Rel-17, 'F'): Corrections for historical analytics exposure procedures Huawei, HiSilicon Rel-17 Rel-18 mirror created in S2-2301360. r02 agreed. Revised to S2-2302068. Zhang (Ericsson) ask for clarification
Dimitris (Lenovo) comments
Yannick (Nokia): Nokia has concerns about this proposal.
Zhang (Ericsson) provides comments
Susan (Huawei) replies to Zhang (Ericsson), Dimitris (Lenovo), and Yannick (Nokia).
Dimitris (Lenovo) provides responses
Susan (Huawei) replies to Dimitris (Lenovo).
Yannick (Nokia): Nokia replies to Huawei.
Susan (Huawei) replies to Yannick (Nokia).
Susan (Huawei) further clarifies to Yannick (Nokia).
Dimitris (Lenovo) provides responses to Susan (Huawei)
Yannick (Nokia): Nokia asks question for clarification to Huawei.
Yannick (Nokia): Nokia provides r01.
Susan (Huawei) replies to Yannick (Nokia) and is ok with r01.
Yannick (Nokia): Nokia provides r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.1 S2-2302068 CR Approval 23.288 CR0648R1 (Rel-17, 'F'): Corrections for historical analytics exposure procedures Huawei, HiSilicon Rel-17 Revision of S2-2300716r02. Approved Agreed
8.1 S2-2301360 CR Approval 23.288 CR0697 (Rel-18, 'A'): Corrections for historical analytics exposure procedures Huawei, HiSilicon Rel-18 Rel-18 mirror CR of S2-2300716. Created at CC#2. r02 agreed. Revised to S2-2302069. Susan (Huawei) provides r00 of the new Rel-18 mirror CR for S2-2300716.
Susan (Huawei) provides r01.
==== Revisions Deadline ====
Susan (Huawei) provides r02 to synchronize with S2-2300716r02.
Dimitris (Lenovo) comments on r02
Susan (Huawei) replies to Dimitris (Lenovo).
Yannick (Nokia): Nokia replies to Dimitris (Lenovo) and Susan (Huawei).
Susan (Huawei) replies to Yannick (Nokia).
Susan (Huawei) propose to move forward with r02.
Yannick (Nokia): Nokia supports going forward with r02.
Dimitris (Lenovo) is ok with r02
==== Final Comments Deadline ====
Revised
8.1 S2-2302069 CR Approval 23.288 CR0697R1 (Rel-18, 'A'): Corrections for historical analytics exposure procedures Huawei, HiSilicon Rel-18 Revision of S2-2301360r02. Approved Agreed
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=2 -
8.2 S2-2300160 CR Approval 23.501 CR3831 (Rel-18, 'F'): Impacts of CH architecture in N3IWF selection Qualcomm Incorporated Rel-18 r06 agreed. Revised to S2-2302070. Peter Hedman (Ericsson) provides r01
Saso (Intel) points out that this CR is not based on the Rel-18 version of the specification.
Huan (vivo) asks for clarifications
Rainer (Nokia) provides r02
Haris(Qualcomm) provides r03
Huan (vivo) provides r04
Yishan (Huawei) provides comments
Peter Hedman (Ericsson) provides r05
Yishan (Huawei) replies to Peter Hedman (Ericsson)
Rainer (Nokia) provides r06.
Haris(Qualcomm) comments on why CR is not FASMO and therefore not applied in rel.17
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.2 S2-2302070 CR Approval 23.501 CR3831R1 (Rel-18, 'F'): Impacts of CH architecture in N3IWF selection Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300160r06. Approved Agreed
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=10 -
8.3 S2-2301231 CR Approval 23.503 CR0759R1 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2209172. Noted Dario (Qualcomm) asks questions for clarification.
Shubhranshu (Nokia) responds
Jari (NTT DOCOMO) comments
Xinpeng(Huawei) comments.
Tingfang Tang (Lenovo) comments.
Shubhranshu (Nokia) comments
==== Revisions Deadline ====
Tingfang Tang (Lenovo) objects this contribution as there is no agreed use case requiring introducing FQDN Range in R17.
==== Final Comments Deadline ====
Noted
8.3 S2-2301228 CR Approval 23.501 CR3751R1 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2209171. Noted Dario (Qualcomm) asks questions for clarification.
Shubhranshu (Nokia) responds
Tingfang Tang (Lenovo) comments.
Shubhranshu (Nokia) comments
Tingfang Tang (Lenovo) replies to Shubhranshu.
==== Revisions Deadline ====
Tingfang Tang (Lenovo) objects this contribution as there is no agreed use case requiring introducing FQDN Range in R17.
==== Final Comments Deadline ====
Noted
8.3 S2-2300917 CR Approval 23.501 CR4018 (Rel-18, 'F'): Correction of supported services in UPF Ericsson Rel-18 r01 agreed. Revised to S2-2302071. Magnus H (Ericsson) provides r01 with correct WI code
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.3 S2-2302071 CR Approval 23.501 CR4018R1 (Rel-18, 'A'): Correction of supported services in UPF Ericsson Rel-18 Revision of S2-2300917r01. Approved Agreed
8.3 S2-2300916 CR Approval 23.501 CR4017 (Rel-17, 'F'): Correction of supported services in UPF Ericsson Rel-17 r01 agreed. Revised to S2-2302072. Magnus H (Ericsson) provides r01 with correct WI code
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.3 S2-2302072 CR Approval 23.501 CR4017R1 (Rel-17, 'F'): Correction of supported services in UPF Ericsson Rel-17 Revision of S2-2300916r01. Approved Agreed
8.3 S2-2300170 CR Approval 23.548 CR0085 (Rel-17, 'B'): Correlating the EDI with PCC rule NTT DOCOMO Rel-17 Noted Dario (Qualcomm) asks questions and provides comments.
Jari (NTT DOCOMO) responds to Dario (Qualcomm)
Magnus H (Ericsson) provides comments
Jari (NTT DOCOMO) responds to Magnus
==== Revisions Deadline ====
Dario (Qualcomm): if we go with r00 it needs to be updated to fix the Category (B->F).
Jari (NTT DOCOMO) proposes to agree r00 with the Category fix from B to F (mistake).
Magnus H (Ericsson) objects to this CR
Jari (NTT DOCOMO) proposes to postpone
==== Final Comments Deadline ====
Noted
8.3 S2-2300173 CR Approval 23.548 CR0086 (Rel-18, 'A'): Correlating the EDI with PCC rule NTT DOCOMO Rel-18 Where is the Rel-17 CR? Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.3 S2-2300164 CR Approval 23.501 CR3832 (Rel-17, 'F'): Correlating the EDI with PCC rule NTT DOCOMO Rel-17 Noted Dario (Qualcomm): please see my comments/questions for 0170
==== Revisions Deadline ====
Magnus H (Ericsson) objects to this CR
Jari (NTT DOCOMO) proposes to postpone
==== Final Comments Deadline ====
Noted
8.3 S2-2300168 CR Approval 23.501 CR3833 (Rel-18, 'A'): Correlating the EDI with PCC rule NTT DOCOMO Rel-18 Mirror CR should have same WI Code as base CR. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=34 -
8.4 - - - NSSRG restriction across different access types over different PLMNs - - Docs:=20 -
8.4 S2-2300023 LS In Action LS from CT WG1: LS on NSSRG restriction across different access types over different PLMNs CT WG1 (C1-227101) Rel-17 Responses drafted in S2-2300288, S2-2300563, S2-2300856, S2-2300858. Final response in S2-2300563 Kundan(NEC) clarifies to Ashok (Samsung).
Ashok (Samsung) clarifies Myungjune (LGE)
Myungjune (LGE) responds to Ashok (Samsung).
Ashok (Samsung) responds to Myungjune
Myungjune (LGE) comments
Ashok (Samsung) comments
Haiyang(Huawei) suggests to use this thread to discuss the reply to the LS
Peter Hedman (Ericsson) provides comments with proposed way forward.
Ashok (Samsung) clarifies to Myungjune (LGE) and Kundan (NEC)
Kundan (NEC) clarifies to Ashok.
Kundan(NEC) provides response to Peter (Ericsson).
Jinguo(ZTE) provides comments
Haiyang (Huawei) provides comments
Ashok (Samsung) provide comments
Guillaume (MediaTek Inc.) comments.
Kundan(NEC) responds to the Haiyang (Huawei).
Peter Hedman (Ericsson) provides reply
Haiyang (Huawei) comments, suggests to solve it in R17.
Ashok (Samsung) responds to Peter Hedman (Ericsson)
Myungjune (LGE) replies to Haiyang (Huawei)
Peter Hedman (Ericsson) agrees with LGE
Kundan (NEC) responds to Haiyang(Huawei).
Kundan (NEC) thinks that Rel-18 aspects can be further discussed in next meeting.
Haiyang (Huawei) seeks clarification from Kundan (NEC).
Kundan(NEC) responds to Haiyang (Huawei).
Replied to
8.4 S2-2300853 DISCUSSION Discussion Discussion on NSSRG restriction across different access types over different PLMNs. Samsung Rel-17 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300287 DISCUSSION Discussion Discussion on NSSRG restriction across different access types over different PLMNs. Huawei, HiSilicon Rel-17 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300288 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs Huawei, HiSilicon Rel-17 Response to S2-2300023. Covered by S2-2300563. Noted To be merged into S2-2300563 (Approved) Peter Hedman (Ericsson) for the notes, we can mark this as merged into 0563.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300563 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs LG Electronics Rel-17 Response to S2-2300023. Approved. CC#4: Revised to remove draft in S2-2301468. Stefano Faccin (Qualcomm) proposes to proceed with this LS OUT as response
Haiyang (Huawei) comments and suggests to discuss in 0023 thread
Jinguo(ZTE) agree to use 563 as basis for LS Out discussion.
Guillaume (MediaTek Inc.) agrees with Stefano (Qualcomm) and others to proceed with 563 as basis for LS Out.
Alessio(Nokia) ok to use 563 as basis
Genadi (Lenovo) supports the principles proposed in the LS reply in 0563 and proceed with 0563 as basis for LS Out.
Peter Hedman (Ericsson) ok with r00
Genadi (Lenovo) is fine with r00.
Ashok (Samsung) does not agree with this LS OUT and prefer 856
Krisztian (Apple) supports r00.
Jinguo(ZTE) replies to Ashok(Samsung)
Ashok (Samsung) responds to Jinguo(ZTE)
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comments and proposes to approve r00
Ashok (Samsung) provides reply to Peter (Ericsson)
Myungjune (LGE) replies to Ashok (Samsung)
Ashok (Samsung) explains to Myungjune (LGE)
Myungjune (LGE) replies to Ashok (Samsung).
Ashok (Samsung) clarifies to Myungjune (LGE)
==== Final Comments Deadline ====
Revised
8.4 S2-2301468 LS OUT Approval Reply LS on NSSRG restriction across different access types over different PLMNs SA WG2 Rel-17 Revision of S2-2300563. Aapproved Approved
8.4 S2-2300856 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs Samsung Rel-17 Response to S2-2300023. Noted Stefano Faccin (Qualcomm) proposes to proceed with S2-2300563 as way forward, but for the second answer we need to conclude first on the enforcement mechanism wrt S2-2300564/565 and S2-2300873.
==== Revisions Deadline ====
Ashok (Samsung) mark this as NOTED
==== Final Comments Deadline ====
Noted
8.4 S2-2300858 LS OUT Approval [DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs NEC Corporation Rel-17 Response to S2-2300023. Covered by S2-2300563. Noted To be merged into S2-2300563 (Approved) Stefano Faccin (Qualcomm) proposes to proceed with S2-2300563 as way forward and consider S2-2300858 merged into S2-2300563, with the comments made in 563
==== Revisions Deadline ====
Kundan (NEC) proposes to proceed with S2-2300563 as way forward and consider S2-2300858 merged into S2-2300563.
==== Final Comments Deadline ====
Noted
8.4 S2-2300289 CR Approval 23.501 CR3865 (Rel-17, 'F'): NSSRG restriction enforcement across different access types over different PLMNs Huawei, HiSilicon Rel-17 Noted Peter Hedman (Ericsson) proposes to use 00564 as basis without network enforcement
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300290 CR Approval 23.501 CR3866 (Rel-18, 'A'): NSSRG restriction enforcement across different access types over different PLMNs Huawei, HiSilicon Rel-18 Noted Peter Hedman (Ericsson) proposes to use 00564 as basis without network enforcement
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300291 CR Approval 23.502 CR3696 (Rel-17, 'F'): NSSRG restriction enforcement across different access types over different PLMNs Huawei, HiSilicon Rel-17 Noted Peter Hedman (Ericsson) proposes to not require any network enforcement
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300292 CR Approval 23.502 CR3697 (Rel-18, 'A'): NSSRG restriction enforcement across different access types over different PLMNs Huawei, HiSilicon Rel-18 Noted Peter Hedman (Ericsson) proposes to not require any network enforcement
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300564 CR Approval 23.501 CR3934 (Rel-17, 'F'): Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access LG Electronics Rel-17 r03 agreed. Revised to S2-2302073, merging S2-2300867 Stefano Faccin (Qualcomm) asks why we cannot adopt an enforcement mechanism as in 0870/0873.
Jing(ZTE) supports the view from Myungjune (LGE)
Myungjune (LGE) responses to Stefano Faccin (Qualcomm)
Ouerdia (Orange) supports the view from Myungjune (LGE) and Jinguo (ZTE).
Peter Hedman (Ericsson) provides r01
Alessio(nokia) provides r02
Krisztian (Apple) provides r03 to co-sign.
Kundan(NEC) is fine with r03 and would like to co-sign.
==== Revisions Deadline ====
Haiyang (Huawei) is OK with r03
==== Final Comments Deadline ====
Revised
8.4 S2-2302073 CR Approval 23.501 CR3934R1 (Rel-17, 'F'): Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Apple, NEC, Huawei Rel-17 Revision of S2-2300564r03, merging S2-2300867. Approved Agreed
8.4 S2-2300565 CR Approval 23.501 CR3935 (Rel-18, 'A'): Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access LG Electronics Rel-18 Revised to S2-2302074. Stefano Faccin (Qualcomm) same comment as 0564.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302074 CR Approval 23.501 CR3935R1 (Rel-18, 'A'): Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Apple, NEC, Huawei Rel-18 Revision of S2-2300565. Approved Agreed
8.4 S2-2300867 CR Approval 23.501 CR4001 (Rel-17, 'F'): NSSRG enforcement when a UE is registered to different PLMNs-Rel17 NEC Rel-17 Merged into S2-2302073 Jinguo(ZTE) propose to note this CR as not FASMO
Alessio(Nokia) comments that while it is true this is not FASMO we need to decide whether to add this to clarify fully as CT1 asked a question ??. So we would be flexible to approve this if there is consensus to do so.
==== Revisions Deadline ====
Kundan(NEC) requests to merge this with S2-2300564.
==== Final Comments Deadline ====
Merged
8.4 S2-2300870 CR Approval 23.501 CR4003 (Rel-18, 'F'): NSSRG enforcement when a UE is registered to different PLMNs-Rel18 NEC Corporation Rel-18 Noted Jinguo(ZTE) provides comments.
Genadi (Lenovo) provides comments and has concern with the proposal.
Peter Hedman (Ericsson) proposes to not require any network enforcement
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2300873 CR Approval 23.502 CR3804 (Rel-18, 'F'): NSSRG enforcement when a UE is registered to different PLMNs-Rel18 NEC Rel-18 Noted Jinguo(ZTE) provides same comment as 870.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 S2-2301185 CR Approval 23.501 CR4084 (Rel-17, 'F'): Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access ZTE Rel-17 Noted Stefano Faccin (Qualcomm) asks why we cannot adopt an enforcement mechanism as in 0870/0873.
Peter Hedman (Ericsson) proposes to use 00564 as basis without network enforcement
Jinguo(ZTE) is ok to use 00564 as basis
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.4 - - - Others - - Docs:=14 -
8.4 S2-2301116 CR Approval 23.501 CR4068 (Rel-17, 'F'): UE-Slice-MBR clarifications including for priority services Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon Rel-17 r03 agreed. Revised to S2-2302075. Dongeun (Samsung) comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302075 CR Approval 23.501 CR4068R1 (Rel-17, 'F'): UE-Slice-MBR clarifications including for priority services Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon, ZTE Rel-17 Revision of S2-2301116r03. Approved Agreed
8.4 S2-2300864 CR Approval 23.502 CR3803 (Rel-17, 'F'): Clarification on Number of PDU session slice availability check Samsung Rel-17 CC#1: Rel-18 mirror CR allocated in S2-2301323. r04 agreed. Revised to S2-2302076. George Foti (Ericsson) provides comments
Fenqin (Huawei) provides comments
Jinguo(ZTE) agree the concept of this tdoc and also agree the comments above
Ashok (Samsung) comments
Ashok (Samsung) provides r01
Genadi (Lenovo) provides comments and r02.
Ashok (Samsung) responds to Genadi (Lenovo)
Genadi (Lenovo) responds to Ashok (Samsung).
Fenqin (Huawei) agree with the suggestion from Genai
Ashok (Samsung) provides r03
George (Ericsson) provides r04
Ashok (Samsung) fine with r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302076 CR Approval 23.502 CR3803R1 (Rel-17, 'F'): Clarification on Number of PDU session slice availability check Samsung Rel-17 Revision of S2-2300864r04. Approved Agreed
8.4 S2-2301323 CR Approval 23.502 CR3870 (Rel-18, 'A'): Clarification on Number of PDU session slice availability check Samsung Rel-18 Rel-18 mirror of S2-2300864. Created at CC#1. Revised to S2-2302077. Ashok (Samsung) comments
Ashok (Samsung) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302077 CR Approval 23.502 CR3870R1 (Rel-18, 'A'): Clarification on Number of PDU session slice availability check Samsung Rel-18 Revision of S2-2301323. Approved Agreed
8.4 S2-2300852 CR Approval 23.501 CR3694R2 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.501. NEC, Ericsson, Huawei Rel-17 Revision of S2-2209022. r05 agreed. Revised to S2-2302078. Alessio(Nokia) provides r01 adding nokia and clarifying the text
Peter Hedman (Ericsson) provides question
Ashok (Samsung) seeks clarification
Alessio(Nokia) provides r03 that introduces a MAY so some network vendors can skip the check at AMF. I think Kundan is ok with this based on offline discussion.
Kundan(NEC) provides r03 on top of r2 addressing comment from Jinguo to replace CAN with MAY.
Alessio latest revision was r02.
Kundan (NEC) responds to Ashok.
Peter Hedman (Ericsson) provides comments
Ashok (Samsung) responds to Kundan (NEC) and Peter Hedman (Ericsson)
Alessio(Nokia) can live with r03 (albeit CAN was better)
Kundan (NEC) provides r05 addressing Peter and Ashok comments.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r05
==== Final Comments Deadline ====
Revised
8.4 S2-2302078 CR Approval 23.501 CR3694R3 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.501. NEC, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2300852r05. Approved Agreed
8.4 S2-2300854 CR Agreement 23.501 CR3998 (Rel-18, 'A'): Pending NSSAI and AMF Relocation in Connected mode 23.501. NEC, Ericsson, Huawei Rel-18 Revised to S2-2302079. Alessio(Nokia) provides r01 adding nokia and clarifying the text as per re-17 CR this is mirror of
Peter Hedman (Ericsson) provides comments that CRs are not inline
Kundan(NEC) provides r02 addressing comments from Peter and Ashok.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302079 CR Agreement 23.501 CR3998R1 (Rel-18, 'A'): Pending NSSAI and AMF Relocation in Connected mode 23.501. NEC, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300854. Approved Agreed
8.4 S2-2300654 CR Approval 23.502 CR3766 (Rel-17, 'F'): S-NSSAI correction for the roaming case Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2302080. George Foti (Ericsson) provides r01. Also Ericsson co-signed
Alessio(Nokia) provides r02. Also co-signed
Fenqin (Huawei) provides feedback
Jinguo(ZTE) provides r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302080 CR Approval 23.502 CR3766R1 (Rel-17, 'F'): S-NSSAI correction for the roaming case Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, ZTE Rel-17 Revision of S2-2300654r03. Approved Agreed
8.4 S2-2300655 CR Approval 23.502 CR3767 (Rel-18, 'A'): S-NSSAI correction for the roaming case Huawei, HiSilicon Rel-18 Revised to S2-2302081. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.4 S2-2302081 CR Approval 23.502 CR3767R1 (Rel-18, 'A'): S-NSSAI correction for the roaming case Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, ZTE Rel-18 Revision of S2-2300655. Approved Agreed
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=15 -
8.5 - - - TSCTSF usage determination in AF session with required QoS - - Docs:=9 -
8.5 S2-2300032 LS In Action LS from CT WG3: LS on TSCTSF usage determination in AF session with required QoS CT WG3 (C3-225700) Rel-17 Responses drafted in S2-2300285, S2-2300321, S2-2300675. Final response in S2-2302082 Devaki (Nokia) comments, prefers to update the title for clause 5.28 to be technically accurate.
zhendong (ZTE) proposes the discussion and comment.
Dan (China Mobile) thinks Devaki may provide the wrong comment here.
Sang-Jun (Samsung) agrees with Dan. Devaki's comments must have been addressed to S2-2300206 instead of S2-2300032.
Qianghua (Huawei) shares same views as Zhendong and provides additional reasons
Replied to
8.5 S2-2300672 DISCUSSION Discussion Discussion paper on the issue raised by CT WG3 LS. ZTE Rel-17 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.5 S2-2300942 DISCUSSION Information Discussion on TSCTSF usage determination in AF session with required QoS. China Mobile Rel-17 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.5 S2-2300285 LS OUT Approval [DRAFT] LS Response on TSCTSF usage determination in AF session with required QoS China Mobile Rel-17 Response to S2-2300032. r06 agreed. Revised to S2-2302082. Sang-Jun (Samsung) proposes to go with 0285 as the baseline merging 0321 and 0675.
Dan (China Mobile) suggest to use 0285 (this one) as baseline paper for the LS reply.
Dan (China Mobile) provide some consideration for this LS feedback.
zhendong (ZTE) provides the response.
Jari (NTT DOCOMO) proposes to go with 0285 as the baseline merging 0321 and 0675.
Shabnam (Ericsson) provides comments that we do not agree with the proposed response as well as concept like normal QoS, so we are fine to use this as baseline but needs to be updated taking into account other submitted versions.
Devaki (Nokia) comments
Dan (China Mobile) reply
Dan (China Mobile) provide r01
Shabnam (Ericsson) provides comments that this version is not acceptable, neither of any of them as we don't have normal QoS. r02 provided
==== Revisions Deadline ====
Dan (China Mobile) provides r03
Sang-Jun (Samsung) asks a question about r03
Dan(China Mobile) provide r04
Qianghua (Huawei) comments on r03 and can live with r02
Dan(China Mobile) provide r05 to alleviate Qianghua's comment.
Dan(China Mobile) request to check this LS for CC#3&4.
Shabnam (Ericsson) provides r06 with cleanups on the Q3 response
Qianghua (Huawei) r05 looks good to me
Wanqiang (convenor) comments: if no further view, will go with r06.
Qianghua (Huawei) r06 looks good to me
Sang-Jun (Samsung) is ok with r06
Dan (China Mobile) OK for r06
==== Final Comments Deadline ====
Revised
8.5 S2-2302082 LS OUT Approval LS Response on TSCTSF usage determination in AF session with required QoS SA WG2 Rel-17 Revision of S2-2300285r06. Approved Approved
8.5 S2-2300321 LS OUT Approval [DRAFT] LS Reply on TSCTSF usage determination in AF session with required QoS Ericsson Rel-17 Response to S2-2300032. Noted zhendong (ZTE) is fine to use this as base and proposes to discuss this issue first in the 0032.
Sang-Jun (Samsung) proposes to go with 0285 as the baseline merging 0321 and 0675.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.5 S2-2300675 LS OUT Approval [DRAFT] Reply LS on TSCTSF usage determination in AF session with required QoS ZTE Rel-17 Response to S2-2300032. Noted zhendong (ZTE) is fine to use 0285 as base and proposes to discuss this issue first in the 0032.
Sang-Jun (Samsung) proposes to go with 0285 as the baseline merging 0321 and 0675.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.5 S2-2300673 CR Approval 23.502 CR3772 (Rel-17, 'F'): Clarification on the TSCTSF usage determination in AF session with required QoS ZTE Rel-17 Merged into S2-2302084 Shabnam (Ericsson) provides comments that the CR in its current form is not agreeable, provides comments
Devaki (Nokia) proposes to merge this with 286.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.5 S2-2300674 CR Approval 23.502 CR3773 (Rel-18, 'A'): Clarification on the TSCTSF usage determination in AF session with required QoS ZTE Rel-18 Merged into S2-2302085 Devaki (Nokia) proposes to merge this with mirror of 286 (or this should become the mirror for 286).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.5 - - - Others - - Docs:=6 -
8.5 S2-2300206 CR Approval 23.501 CR3845 (Rel-17, 'F'): Clarification of the TSC clause titles Ericsson Rel-17 r01 agreed. Revised to S2-2302083. Sang-Jun (Samsung) corrects the Tdoc number of the mail title into S2-2300206, so that Devaki's comments are delivered.
Devaki (Nokia) comments and confirms that the comment was for 206, thanks Sang-Jun for correcting the subject line.
György (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.5 S2-2302083 CR Approval 23.501 CR3845R1 (Rel-17, 'F'): Clarification of the TSC clause titles Ericsson Rel-17 Revision of S2-2300206r01. Approved Agreed
8.5 S2-2300310 CR Approval 23.502 CR3701 (Rel-18, 'A'): Clarify the procedure when the NEF reject the AF update request China Mobile Rel-18 Confirm Specification Number - CR states 23.501! r01 agreed. Revised to S2-2302085, merging S2-2300674 Dan(China Mobile) provides r01 for R18, the same change as S2-2300286r03
==== Revisions Deadline ====
Dan (China Mobile) suggest to go with r01.
==== Final Comments Deadline ====
Revised
8.5 S2-2302085 CR Approval 23.502 CR3701R1 (Rel-18, 'A'): Clarify the procedure when the NEF reject the AF update request China Mobile, ZTE Rel-18 Revision of S2-2300310r01, merging S2-2300674. Approved Agreed
8.5 S2-2300286 CR Approval 23.502 CR3695 (Rel-17, 'F'): Clarify the procedure when the NEF reject the AF update request China Mobile Rel-17 r03 agreed. Revised to S2-2302084, merging S2-2300673 Jari (NTT DOCOMO) provides comments
Qianghua (Huawei) provides r01
Dan (China Mobile) reply
zhendong (ZTE) provides r02.
Shabnam (Ericsson) provides comments about the cause code meaning
Dan(China Mobile) provides r03, only removing 'update'
==== Revisions Deadline ====
Devaki (Nokia) comments that we can live with r03.
zhendong (ZTE) is fine with r03.
Dan (China Mobile) suggest to go with r03.
Shabnam (Ericsson) provides comments that r03 is ok as well.
==== Final Comments Deadline ====
Revised
8.5 S2-2302084 CR Approval 23.502 CR3695R1 (Rel-17, 'F'): Clarify the procedure when the NEF reject the AF update request China Mobile, ZTE Rel-17 Revision of S2-2300286r03, merging S2-2300673. Approved Agreed
8.6 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) - - Docs:=0 -
8.7 - - - Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) - - Docs:=3 -
8.7 S2-2300869 CR Approval 23.256 CR0073 (Rel-17, 'F'): Addressing Editor Notes Samsung Rel-17 r02 agreed. Revised to S2-2302086. Jaewoo (LGE) provides comments.
Ashok (Samsung) explain how the proposal works to Jaewoo (LGE)
Jaewoo (LGE) provides further comments to Ashok (Samsung).
Ashok (Samsung) replies to Jaewoo (LGE)
Stefano (Qualcomm) provides further comments.
Ashok (Samsung) responds to Stefano (Qualcomm)
Jaewoo (LGE) provides r01 and r02.
Ashok (Samsung) thanks Jaewoo (LGE) for providing revision and happy with r02.
==== Revisions Deadline ====
Jaewoo (LGE) provides comment on r02.
Stefano (Qualcomm) overall prefers R01 but can live with R02.
Jaewoo (LGE) also prefers r01 but can live with r02.
==== Final Comments Deadline ====
Revised
8.7 S2-2302086 CR Approval 23.256 CR0073R1 (Rel-17, 'F'): Addressing Editor Notes Samsung Rel-17 Revision of S2-2300869r02. Approved Agreed
8.7 S2-2300017 LS In Action LS from CT WG4: LS on UAV authorization container CT WG4 (C4-223513) Rel-17 Revision of postponed S2-2210212 from S2#154. Resubmission of (replied to) S2-2208104 from S2#153-e. Noted Stefano Faccin (Qualcomm) suggest to note based on actions in previous meetings. Noted
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=33 -
8.8 - - - ProSe policy request during registration procedure - - Docs:=8 -
8.8 S2-2300004 LS In Action LS from CT WG1: LS on V2X policy or ProSe policy request during registration procedure CT WG1 (C1-225451) Revision of postponed S2-2210168 from S2#154. Response drafted in S2-2300715. Final response in S2-2302062 Replied to
8.8 S2-2300025 LS In Action LS from CT WG1: LS on UE requesting policies during registration procedure CT WG1 (C1-227137) Rel-18 Response drafted in S2-2300715. Final response in S2-2302062 Replied to
8.8 S2-2300715 LS OUT Approval [DRAFT] LS Reply on V2X policy or ProSe policy request during registration procedure Huawei, HiSilicon Rel-17 Response to S2-2300025 and S2-2300004. Revised to S2-2302062. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302062 LS OUT Approval LS Reply on V2X policy or ProSe policy request during registration procedure SA WG2 Rel-17 Revision of S2-2300715. Approved Approved
8.8 S2-2300243 CR Approval 23.503 CR0743R1 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE, OPPO Rel-17 Revision of S2-2208356. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 S2-2300246 CR Approval 23.304 CR0157 (Rel-18, 'A'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE, OPPO Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 S2-2300245 CR Approval 23.304 CR0115R1 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE, OPPO Rel-17 Revision of S2-2208357. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 S2-2300244 CR Approval 23.503 CR0809 (Rel-18, 'A'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE, OPPO Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 - - - NR TX Profile / PC5 DRX - - Docs:=10 -
8.8 S2-2300019 LS In Action LS from CT WG1: LS on mandating the NR Tx Profiles in broadcast mode and groupcast mode communication CT WG1 (C1-226994) Rel-17 Responses drafted in S2-2300378, S2-2300702. Final response in S2-2302087 Replied to
8.8 S2-2300378 LS OUT Approval [DRAFT] Reply LS on mandating the NR Tx Profiles in broadcast mode and groupcast mode communication LG Electronics Rel-17 Response to S2-2300019. Merged into S2-2302087 Zhang (Ericsson) provides comments
LaeYoung (LGE) responds to Zhang (Ericsson).
Wen (vivo) comments and thanks LaeYoung's work.
==== Revisions Deadline ====
LaeYoung (LGE) is fine to merge this LS to 00702.
Wen (vivo): many thanks for LaeYoung's support and cooperation.
==== Final Comments Deadline ====
Merged
8.8 S2-2300702 LS OUT Approval [DRAFT] Reply LS on mandating the NR Tx Profiles vivo Rel-18 Response to S2-2300019. r07 agreed. Revised to S2-2302087, merging S2-2300378 Wen (vivo) tries to provide the r01 for this LS out.
Hong (Qualcomm) comments.
Wen (vivo) provides r02.
LaeYoung (LGE) comments on r02.
Wen (vivo) provides r03.
Fei (OPPO) comments.
Wen (vivo) replies.
Fei (OPPO) provides comments.
LaeYoung (LGE) replies to Fei (OPPO).
Wen (vivo) shares the same understanding with LaeYoung (LGE).
==== Revisions Deadline ====
Fei (OPPO) can live with r03.
Steve (Huawei) comments.
Wen(vivo) replies to Steve.
Fei (OPPO) provides further comments.
Hong (Qualcomm) comments and suggest answer 'NO' based on the CR.
Wen (vivo) provides r04 and keep the 'NO'.
LaeYoung (LGE) provides comment.
Hong (Qualcomm) replies to Fei.
Fei (OPPO) comments on catch all entry.
LaeYoung (LGE) comments.
Fei (OPPO) proposes to go with mandatory option.
Fei (OPPO) Provided replies.
Wen(vivo) provides the r05.
Hong (Qualcomm) replies to Steve.
Fei (OPPO) replied
Fei (OPPO) comments on r05.
Wen (vivo) provides r06.
Fei (OPPO) is ok with r06.
LaeYoung (LGE) is fine with r06.
Steve (Huawei) provides an r07
Hong (Qualcomm) is fine with R06.
Fei (OPPO) is fine with r07 as well.
LaeYoung (LGE) is also fine with r07.
==== Final Comments Deadline ====
Revised
8.8 S2-2302087 LS OUT Approval Reply LS on mandating the NR Tx Profiles in broadcast mode and groupcast mode communication SA WG2 Rel-18 Revision of S2-2300702r07, merging S2-2300378. Approved Approved
8.8 S2-2300700 CR Approval 23.304 CR0184 (Rel-17, 'B'): Default configuration for ProSe Policy/Parameter Vivo Rel-17 r04 agreed. Revised to S2-2302088. Hong (Qualcomm) comments.
Fei (OPPO) commens.
Zhang (Ericsson) provides comments
Antoine (Orange) cannot agree to a Cat. B CR after the Rel-17 freeze.
Wen (vivo) comments and replies.
Steve (Huawei) comments.
Wen (vivo) replies and provides r01.
Wen (vivo) provides r02.
Antoine (Orange) provides r03.
Wen (vivo) is ok with r03.
LaeYoung (LGE) provides r04.
==== Revisions Deadline ====
Steve (Huawei) is fine with r04
==== Final Comments Deadline ====
Revised
8.8 S2-2302088 CR Approval 23.304 CR0184R1 (Rel-17, 'F'): Default configuration for ProSe Policy/Parameter Vivo Rel-17 Revision of S2-2300700r04. Approved Agreed
8.8 S2-2300701 CR Approval 23.304 CR0185 (Rel-18, 'A'): Default configuration for ProSe Policy/Parameter Vivo Rel-18 Where is the Rel-17 CR? r02 agreed. Revised to S2-2302089. Wen (vivo) provides r01 as the mirror updates corresponding to the S2-2300700 for R18 .
Wen (vivo) provides r02 base on the updates in S2-2300700r04 for R18 .
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302089 CR Approval 23.304 CR0185R1 (Rel-18, 'A'): Default configuration for ProSe Policy/Parameter Vivo Rel-18 Revision of S2-2300701r02. Approved Agreed
8.8 S2-2300602 CR Approval 23.304 CR0182 (Rel-17, 'F'): Correction on PC5 DRX OPPO Rel-17 Postponed Steve (Huawei) checks alignment with discussion in S2-2300700 (and others)
Fei (OPPO) responds.
Hannu (Nokia) is not convinced that the DRX is mandatory to support and to use.
Fei (OPPO) responds to Hannu.
Mehrdad (MediaTek Inc.) wonders why 'shall' has been used in this CR.
Fei (OPPO) responds to Mehrdad.
Hong (Qualcomm) comments.
Fei (OPPO) replied to Hong.
Hannu (Nokia) proposes to postpone both S2-2300602 and 0603 and to resume the discussion in Athens as there is strong RAN2 aspect involved.
Fei (OPPO) replies and indicates this CRs will not be on agenda in Athens.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
8.8 S2-2300603 CR Approval 23.304 CR0183 (Rel-18, 'A'): Correction on PC5 DRX OPPO Rel-18 Postponed Hannu (Nokia) proposes to postpone both S2-2300602 and 0603 and to resume the discussion in Athens as there is strong RAN2 aspect involved.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
8.8 - - - Dedicated DNN for L3 U2N Relay - - Docs:=5 -
8.8 S2-2300030 LS In Action LS from CT WG3: LS on dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity CT WG3 (C3-225374) Rel-17 Response drafted in S2-2300247. Final response in S2-2302063 Replied to
8.8 S2-2300247 LS OUT Approval [DRAFT] Reply LS on dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity Ericsson Rel-17 Response to S2-2300030. Revised to S2-2302063. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302063 LS OUT Approval Reply LS on dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity SA WG2 Rel-17 Revision of S2-2300247. Approved Approved
8.8 S2-2300248 CR Approval 23.304 CR0158 (Rel-17, 'F'): Dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity without N3IWF Ericsson, LG Electronics Rel-17 Approved LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) asks questions.
Judy (Ericsson) responds
Fei (OPPO) responds.
LaeYoung (LGE) comments.
Hannu (Nokia) supports the principle of the CR and the revision suggested by Fei (DNN + S-NSSAI).
Judy (Ericsson) responds to Hannu (Nokia) that configuring DNN in SMF and PCF would be sufficient
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 S2-2300249 CR Approval 23.304 CR0159 (Rel-18, 'A'): Dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity without N3IWF Ericsson, LG Electronics Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.8 - - - Others - - Docs:=10 -
8.8 S2-2301318 CR Approval 23.304 CR0213 (Rel-17, 'F'): Clarification of out-of-coverage operation for U2U and U2N Relays Philips International B.V. Rel-17 r04 agreed. Revised to S2-2302090. Fei (OPPO) comments.
Hong (Qualcomm) comments and suggest to NOTE the CR.
Judy (Ericsson) comments and ask questions
Steve (Huawei) comments.
Fei (OPPO) provides comments.
Walter (Philips) requests clarification from commenters.
Hannu (Nokia) shares the concern of Walter (Philips) and asks questions.
Mehrdad (MediaTek Inc.) comments
Hong (Qualcomm) replies.
Hong (Qualcomm) comments.
Walter (Philips) provides revision r01.
Shabnam (Ericsson) provides comments
Walter (Philips) responds to Shabnam (Ericsson)
Hong (Qualcomm) comments on r01.
Walter (Philips) provides r03.
Fei (OPPO) provides comments on r03.
Walter (Philips) request clarification and provides revision r04.
Walter (Philips) responds to Fei (Oppo).
Fei (OPPO) provides replies to Walter.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302090 CR Approval 23.304 CR0213R1 (Rel-17, 'F'): Clarification of out-of-coverage operation_R17 Philips International B.V. Rel-17 Revision of S2-2301318r04. Approved Agreed
8.8 S2-2301319 CR Approval 23.304 CR0214 (Rel-18, 'A'): Clarification of out-of-coverage operation for U2U and U2N Relays Philips International B.V. Rel-18 Mirror CR should have same WI Code as base CR. Revised to S2-2302091. Fei (OPPO) comments.
Hong (Qualcomm) comments and suggest to NOTE the CR.
Walter (Philips) provides revision r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302091 CR Approval 23.304 CR0214R1 (Rel-18, 'A'): Clarification of out-of-coverage operation_R18 Philips International B.V. Rel-18 Revision of S2-2301319. Approved Agreed
8.8 S2-2301248 CR Approval 23.304 CR0210 (Rel-17, 'F'): Alignment on Remote User ID for L3 U2N Relay w/o N3IWF Interdigital Rel-17 r01 agreed. Revised to S2-2302092. Judy (Ericsson) comments and provides r01
Hannu (Nokia) supports r01
Jung Je (Interdigital) is OK with r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302092 CR Approval 23.304 CR0210R1 (Rel-17, 'F'): Alignment on Remote User ID for L3 U2N Relay w/o N3IWF Interdigital, Ericsson Rel-17 Revision of S2-2301248r01. Approved Agreed
8.8 S2-2301249 CR Approval 23.304 CR0211 (Rel-18, 'A'): Alignment on Remote User ID for L3 U2N Relay w/o N3IWF Interdigital Rel-18 r01 agreed. Revised to S2-2302093. Jungje(Interdigital) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.8 S2-2302093 CR Approval 23.304 CR0211R1 (Rel-18, 'A'): Alignment on Remote User ID for L3 U2N Relay w/o N3IWF Interdigital, Ericsson Rel-18 Revision of S2-2301249r01. Approved Agreed
8.8 S2-2300376 CR Approval 23.304 CR0166 (Rel-17, 'F'): Adding RSC as term defined in TS 23.303 LG Electronics Rel-17 Noted Judy (Ericsson) proposes to have the correction from Rel-18 as the Rel-17 CR seems to lack justification of FASMO consequence.
LaeYoung (LGE) replies to Judy (Ericsson) and is fine to NOTE this CR.
Hannu (Nokia) asks whether the Rel-18 CR still survives (as I hope)?
LaeYoung (LGE) replies to Hannu (Nokia).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.8 S2-2300377 CR Approval 23.304 CR0167 (Rel-18, 'A'): Adding RSC as term defined in TS 23.303 LG Electronics Rel-18 Noted Hannu (Nokia) proposes to convert this to Cat F CR and to note the corresponding Rel-17 CR in S2-2300376
LaeYoung (LGE) replies to Hannu (Nokia).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=38 -
8.9 - - - Shared NG-U Termination - - Docs:=11 -
8.9 S2-2300035 LS In Action LS from CT WG4: Reply LS on shared NG-U Termination among gNBs CT WG4 (C4-225556) Rel-17 Responses drafted in S2-2300327, S2-2300676, S2-2301309. Final response in S2-2302094 Judy (Ericsson) propose to use this thread to discuss the way forward.
zhendong (ZTE) is fine with judy proposal.
Thomas (Nokia) is also fine with Judy`s proposal.
Judy (Ericsson) comments and provide r02. RAN confirmation is required for SA approval of this CR is included in over sheet
Judy (Ericsson) please ignore r02 in previous comment which is intended for S2-2300677
Replied to
8.9 S2-2300327 LS OUT Approval [DRAFT] Rely on Reply LS on shared NG-U Termination among gNBs Ericsson Rel-17 Response to S2-2300035. Merged into S2-2302094 LiMeng (Huawei) suggests to merge this document into S2-2300676.
Judy (Ericsson) agrees with LiMeng (Huawei) to merge.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.9 S2-2300676 LS OUT Approval [DRAFT] Reply LS on shared NG-U Termination among gNBs ZTE Rel-17 Response to S2-2300035. r02 agreed. Revised to S2-2302094, merging S2-2300327 and S2-2301309 Judy (Ericsson) provide r01 based on proposal in S2-2300035
LiMeng (Huawei) provide r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302094 LS OUT Approval Reply LS on shared NG-U Termination among gNBs SA WG2 Rel-17 Revision of S2-2300676r02, merging S2-2300327 and S2-2301309. Approved Approved
8.9 S2-2301309 LS OUT Approval [DRAFT] Reply LS on shared NG-U Termination among gNBs Nokia, Nokia Shanghai-Bell Rel-17 Response to S2-2300035. Merged into S2-2302094 Thomas (Nokia) suggest to consider this LS as merged into S2-2300676
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.9 S2-2301307 CR Approval 23.247 CR0181 (Rel-17, 'F'): Shared shared NG-U Termination for broadcast Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2302095 zhendong (ZTE) proposes this CR is merged into 0677.
Thomas (Nokia) is fine to merge this CR into 0677.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.9 S2-2301308 CR Approval 23.247 CR0182 (Rel-18, 'A'): Shared shared NG-U Termination for broadcast Nokia, Nokia Shanghai-Bell Rel-18 Merged into S2-2302096 LiMeng (Huawei) suggests to merge this document into S2-2300678
Thomas (Nokia) agrees to merge this document into S2-2300678
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
8.9 S2-2300677 CR Approval 23.247 CR0169 (Rel-17, 'F'): Clarification shared NG-U Termination among gNBs for Broadcast MBS session ZTE Rel-17 r06 agreed. Revised to S2-2302095, merging S2-2301307 Thomas (Nokia) provides r01, merging S2-2301307
Judy (Ericsson) comments and provide r02. RAN confirmation is required for SA approval of this CR is included in over sheet
zhendong (ZTE) provides r03.
LiMeng (Huawei) provides r04.
zhendong (ZTE) provides response.
Judy (Ericsson) provides r06 (please ignore r05)
==== Revisions Deadline ====
Judy (Ericsson) accepts r02, r03 & r06, objects to other revsions (including r00)
zhendong (ZTE) prefer r06.
LiMeng (Huawei) thanks Judy for providing the revision, prefers r06.
LiMeng (Huawei) suggests to go with r06+minor change.
Judy (Ericsson) agrees with Li Meng's proposed minor change, i.e. r06 + replace 'Tunnel Identifier of MB-UPF' with 'Tunnel ID allocated by MB-UPF'
Thomas (Nokia) agrees with Li Meng's proposed minor change, i.e. r06 + replace 'Tunnel Identifier of MB-UPF' with 'Tunnel ID allocated by MB-UPF'
==== Final Comments Deadline ====
Revised
8.9 S2-2302095 CR Approval 23.247 CR0169R1 (Rel-17, 'F'): Clarification shared NG-U Termination among gNBs for Broadcast MBS session ZTE, Nokia, Nokia Shanghai-Bell, Ericson Rel-17 Revision of S2-2300677r06, merging S2-2301307. Approved Agreed
8.9 S2-2300678 CR Approval 23.247 CR0170 (Rel-18, 'A'): Clarification shared NG-U Termination among gNBs for Broadcast MBS session ZTE Rel-18 Revised to S2-2302096, merging S2-2301308 ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302096 CR Approval 23.247 CR0170R1 (Rel-18, 'A'): Clarification shared NG-U Termination among gNBs for Broadcast MBS session ZTE, Nokia, Nokia Shanghai-Bell, Ericson Rel-18 Revision of S2-2300678, merging S2-2301308. Approved Agreed
8.9 - - - Security Architecture and Related - - Docs:=5 -
8.9 S2-2300071 LS In Action LS from SA WG3: Reply LS on Security architecture for 5G multicast/broadcast services SA WG3 (S3-223919) Rel-17 Responses drafted in S2-2300328, S2-2301314. Postponed Thomas (Nokia) suggests postponing this LS as related reply LS and CR will likely not be agreed Postponed
8.9 S2-2300328 LS OUT Approval [DRAFT] Rely on Reply LS on Security architecture for 5G multicast/broadcast services Ericsson Rel-17 Response to S2-2300071. Noted To be merged into S2-2301314 (Noted) Judy (Ericsson) responds to LiMeng (Huawei) that the content in this LS reply is SA2's feedback to an attached/agreed CR included in the i/c LS
LiMeng (Huawei) comments that the content in this LS reply is a bit SA3-level information. Should we submit the CR to SA3 directly instead of including that in SA2?
Haris(Qualcomm) comments
Judy (Ericsson) responds to Haris(Qualcomm)
Thomas (Nokia) comments that S2-2301314 is a competing reply LS proposal and only one can be approved.
Suggest to use S2-2301314 as basis
Judy (Ericsson) is OK to use S2-2301314 as basis. Content-wise, 328 and 1314 do not seem to be competing.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
8.9 S2-2301314 LS OUT Approval [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services Nokia, Nokia Shanghai-Bell Rel-17 Response to S2-2300071. Noted Judy (Ericsson) comments
Thomas (Nokia) replies to Judy
Judy (Ericsson) comments and provide r01
LiMeng (Huawei) comments.
Thomas(Nokia) provides r02
Haris(Qualcomm) comments and provides r03
Thomas(Nokia) replies to Haris(Qualcomm)
Haris(Qualcomm) responds
==== Revisions Deadline ====
Judy (Ericsson) accepts r01, objects to other revisions including r00
Wanqiang (Convenor) comments: please all check r01 is acceptable or not.
Haris(Qualcomm) objects to r01, prefers r03
Thomas(Nokia) objects to r01
==== Final Comments Deadline ====
Noted
8.9 S2-2300162 CR Approval 23.247 CR0148 (Rel-18, 'A'): Alignment with security functionality Qualcomm Incorporated Rel-18 Postponed ==== Revisions Deadline ====
Thomas (Nokia) comments that this CR is a mirror for S2-2300161 (that has revisions) and should thus not yet be approved
Judy (Ericsson) comments to WangQiang that this is a mirror CR and its approval will depend on the status of S2-2300161
==== Final Comments Deadline ====
Postponed
8.9 S2-2300161 CR Approval 23.247 CR0147 (Rel-17, 'F'): Alignment with security functionality Qualcomm Incorporated Rel-17 Postponed Thomas (Nokia) provides r01
Judy (Ericsson) propose to postpone this paper due to unclarity in SA3 spec as commented in 1314 thread.
LiMeng (Huawei) provides r02 - only point to 33501 for MBSSF.
Judy (Ericsson) still has concern on the unclarity of MBSSF from SA3 spec
Haris(Qualcomm) asks Judy what clarification is expecting from SA3
==== Revisions Deadline ====
Judy (Ericsson) clarifies to Haris(Qualcomm) and propose to postpone this paper
Haris(Qualcomm) responds
Judy (Ericsson) responds to Haris(Qualcomm)
==== Final Comments Deadline ====
Postponed
8.9 - - - Other LSs and Miscellaneous - - Docs:=22 -
8.9 S2-2300073 LS In Information LS from SA WG4: Reply LS on 5MBS User Services SA WG4 (S4-221415) Rel-17 Noted LiMeng (Huawei) proposes to note this LS (and it was noted in the last meeting in fact) Noted
8.9 S2-2300323 CR Approval 23.247 CR0155 (Rel-17, 'F'): Correction to location dependent service for broadcast Ericsson Rel-17 r01 agreed. Revised to S2-2302097. Judy (Ericsson) provides r01 to address LiMeng (Huawei)'s comment.
LiMeng (Huawei) suggests to also update the services operation for create, i.e., Namf_MBSBroadcast_ContextCreate.
LiMeng (Huawei) is fine with r01 from Judy (Ericsson).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302097 CR Approval 23.247 CR0155R1 (Rel-17, 'F'): Correction to location dependent service for broadcast Ericsson Rel-17 Revision of S2-2300323r01. Approved Agreed
8.9 S2-2300324 CR Approval 23.247 CR0156 (Rel-18, 'A'): Correction to location dependent service for broadcast Ericsson Rel-18 Revised to S2-2302098. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302098 CR Approval 23.247 CR0156R1 (Rel-18, 'A'): Correction to location dependent service for broadcast Ericsson Rel-18 Revision of S2-2300324. Approved Agreed
8.9 S2-2300325 CR Approval 23.247 CR0157 (Rel-17, 'F'): Correction to Broadcast MBS Session handling Ericsson, AT&T Rel-17 r06 agreed. Revised to S2-2302099. Judy (Ericsson) provides r01, the only change is to add FirstNet as co-source
Haris(Qualcomm) comments
Judy (Ericsson) responds to Haris(Qualcomm) and provides r02
Thomas (Nokia) provides r03
Fenqin (Huawei) provides comments
Judy (Ericsson) responds and provides r04
Fenqin (Huawei) provides r05
Judy (Ericsson) is fine with r05
Thomas (Nokia) provides r06
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302099 CR Approval 23.247 CR0157R1 (Rel-17, 'F'): Correction to Broadcast MBS Session handling Ericsson, AT&T, FirstNet, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2300325r06. Approved Agreed
8.9 S2-2300326 CR Approval 23.247 CR0158 (Rel-18, 'A'): Correction to Broadcast MBS Session handling Ericsson, AT&T Rel-18 Revised to S2-2302100. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302100 CR Approval 23.247 CR0158R1 (Rel-18, 'A'): Correction to Broadcast MBS Session handling Ericsson, AT&T, FirstNet, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300326. Approved Agreed
8.9 S2-2300180 CR Approval 23.247 CR0151 (Rel-17, 'F'): AMF knowing MBS support status of NG-RAN node (s) for Multicast Activation Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2302101. Judy (Ericsson) provides r01
Thomas (Nokia) accepts r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302101 CR Approval 23.247 CR0151R1 (Rel-17, 'F'): AMF knowing MBS support status of NG-RAN node (s) for Multicast Activation Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2300180r01. Approved Agreed
8.9 S2-2300181 CR Approval 23.247 CR0152 (Rel-18, 'A'): AMF knowing MBS supporting status of NG-RAN node (s) for Multicast Activation Nokia, Nokia Shanghai-Bell Rel-18 Revised to S2-2301301 Revised
8.9 S2-2301301 CR Approval 23.247 CR0152R1 (Rel-18, 'A'): AMF knowing MBS supporting status of NG-RAN node (s) for Multicast Activation Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300181. Revised to S2-2302102. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302102 CR Approval 23.247 CR0152R2 (Rel-18, 'A'): AMF knowing MBS support status of NG-RAN node (s) for Multicast Activation Nokia, Nokia Shanghai-Bell, Ericsson Rel-18 Revision of S2-2301301. Approved Agreed
8.9 S2-2300182 CR Approval 23.247 CR0153 (Rel-17, 'F'): Correction to description of Fig. 7.1.1.3-1 Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2302103. Judy (Ericsson) provides r01
Thomas (Nokia) accepts r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302103 CR Approval 23.247 CR0153R1 (Rel-17, 'F'): Correction to description of Fig. 7.1.1.3-1 Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2300182r01. Approved Agreed
8.9 S2-2300183 CR Approval 23.247 CR0154 (Rel-18, 'A'): Correction of a typo in Fig. 7.1.1.3-1 of TS 23.247 Nokia, Nokia Shanghai-Bell Rel-18 Revised to S2-2301304 Revised
8.9 S2-2301304 CR Approval 23.247 CR0154R1 (Rel-18, 'A'): Correction of a typo in Fig. 7.1.1.3-1 of TS 23.247 Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300183. Revised to S2-2302104. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.9 S2-2302104 CR Approval 23.247 CR0154R2 (Rel-18, 'A'): Correction to description of Fig. 7.1.1.3-1 Nokia, Nokia Shanghai-Bell, Ericsson Rel-18 Revision of S2-2301304. Approved Agreed
8.9 S2-2301324 CR Approval 23.247 CR0183 (Rel-17, 'F'): Align the MB-SMF discovery enhancement in clause 7.1.2 Huawei, HiSilicon, Ericsson Rel-17 Rel-17 CR related to CR in S2-2300591. Created at CC#1. Noted LiMeng (Huawei) provides r00
Judy (Ericsson) asks the FASMO reason of this Rel-17 CR
==== Revisions Deadline ====
Judy (Ericsson) objects to this CR (for Rel-17) due to lack of FASMO reason, and proposes to proceed with the Rel-18 correction.
LiMeng (Huawei) OK to only go with Rel-18.
==== Final Comments Deadline ====
Noted
8.9 S2-2300591 CR Approval 23.247 CR0166 (Rel-18, 'F'): Align the MB-SMF discovery enhancement in clause 7.1.2 Huawei, HiSilicon Rel-18 Convert to Rel-18 mirror CR. Rel-17 base CR in S2-2301324. r01 agreed. Revised to S2-2302105. Judy (Ericsson) provides r02
LiMeng (Huawei) provides r03
Haris(Qualcomm) provides r04
==== Revisions Deadline ====
Judy (Ericsson) corrects the previous comment that r01 (but not r02) was provided, accepts only r01 and objects to other revisions (including r00).
==== Final Comments Deadline ====
Revised
8.9 S2-2302105 CR Approval 23.247 CR0166R1 (Rel-18, 'F'): Align the MB-SMF discovery enhancement in clause 7.1.2 Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2300591r01. Approved Agreed
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=0 -
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=0 -
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=0 -
8.13 - - - 5G System Enhancement for Advanced Interactive Services (5G_AIS) - - Docs:=0 -
8.14 - - - Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) - - Docs:=2 -
8.14 S2-2300953 CR Approval 23.273 CR0282 (Rel-17, 'F'): Update of GNSS integrity requirement provisioing Huawei, HiSilicon Rel-17 CC#1: Rel-18 mirror CR allocated in S2-2301325. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.14 S2-2301325 CR Approval 23.273 CR0296 (Rel-18, 'A'): Update of GNSS integrity requirement provisioing Huawei, HiSilicon Rel-18 Rel-18 mirror of S2-2300953. Created at CC#1. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
8.15 - - - Multimedia Priority Service (MPS) Phase 2 (MPS2) - - Docs:=0 -
8.16 - - - Dynamic management of group-based event monitoring (TEI17_GEM) - - Docs:=0 -
8.17 - - - N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) - - Docs:=0 -
8.18 - - - System enhancement for Redundant PDU Session (TEI17_SE_RPS) - - Docs:=0 -
8.19 - - - IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) - - Docs:=0 -
8.20 - - - Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) - - Docs:=0 -
8.21 - - - Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) - - Docs:=0 -
8.22 - - - IP address pool information from UDM (TEI17_IPU) - - Docs:=0 -
8.23 - - - Same PCF selection for AMF and SMF (TEI17-SPSFAS) - - Docs:=0 -
8.24 - - - Support of different slices over different Non-3GPP access (TEI17_N3SLICE) - - Docs:=0 -
8.25 - - - Minimization of Service Interruption (MINT) - - Docs:=0 -
8.26 - - - Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) - - Docs:=0 -
8.27 - - - Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) - - Docs:=3 -
8.27 S2-2300045 LS In Action LS from RAN WG2: New TAU trigger to support update of UE s EUTRAN capability upon TN NTN mobility RAN WG2 (R2-2213081) Rel-17 Noted Stefan (Ericsson) proposes to NOTE this LS
Jean Yves (Thales) is ok with Stefan's proposal to NOTE this LS
Noted
8.27 S2-2300163 CR Approval 23.502 CR3677 (Rel-17, 'F'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) Qualcomm Incorporated Rel-17 Postponed Steve (Huawei) asks about the scenario
Hannu (Nokia) responds to Steve and makes further comments.
Steve (Huawei) comments on prevention
Haris(Qualcomm) responds
Haris(Qualcomm) provides r01
Stefan (Ericsson) provides r02
Chris (Vodafone) asks for clarity on the scenario.
Steve (Huawei) comments.
Haris(Qualcomm) responds to comments and indicates that is ok with r02
==== Revisions Deadline ====
Steve (Huawei) suggests postpone
==== Final Comments Deadline ====
Postponed
8.27 S2-2300165 CR Approval 23.502 CR3678 (Rel-18, 'A'): Handling of radio capabilities across TN (in 5GS) and NTN IoT (in EPS) Qualcomm Incorporated Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
8.28 - - - Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups - - Docs:=6 -
8.28 S2-2301068 CR Approval 23.502 CR3835 (Rel-17, 'F'): SMS memory available Nokia, Nokia Shanghai Bell Rel-17 Postponed Qian (Ericsson) provides comments and question
Chris (Vodafone) comments
Hannu (Nokia) replies to Qian and Chris and proposes to remove what is clearly wrong and to come back with further actions if necessary
==== Revisions Deadline ====
Qian (Ericsson) comments that we can either add 'SMSF' to provide a system level solution, or we postpone the paper.
Wanqiang (Convenor) comments: please check Qian proposal 'replace AMF with SMSF' is OK or not. If not, will postpone the paper.
==== Final Comments Deadline ====
Postponed
8.28 S2-2301069 CR Approval 23.502 CR3836 (Rel-18, 'A'): SMS memory available Nokia, Nokia Shanghai Bell Rel-18 Postponed Qian (Ericsson) indicates same comments as for 1068
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
8.28 S2-2300141 CR Approval 23.502 CR3669 (Rel-18, 'A'): Correction of subscribed User Plane Security Policy when UE is in EPC Ericsson Rel-18 Revised to S2-2302107. Haiyang(Huawei) comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
8.28 S2-2302107 CR Approval 23.502 CR3669R1 (Rel-18, 'A'): Correction of subscribed User Plane Security Policy when UE is in EPC Ericsson Rel-18 Revision of S2-2300141. Approved Agreed
8.28 S2-2300140 CR Approval 23.502 CR3668 (Rel-17, 'F'): Correction of subscribed User Plane Security Policy when UE is in EPC Ericsson Rel-17 r02 agreed. Revised to S2-2302106. Haiyang(Huawei) comments
Hannu (Nokia) agrees that the reference to clause 6.3.8 needs further clarification or correction?
Stefan (Ericsson) provides r01
Haris(Qualcomm) provides r02
Haiyang(Huawei) is OK with r02
==== Revisions Deadline ====
Hannu (Nokia) agrees with r02
==== Final Comments Deadline ====
Revised
8.28 S2-2302106 CR Approval 23.502 CR3668R1 (Rel-17, 'F'): Correction of subscribed User Plane Security Policy when UE is in EPC Ericsson Rel-17 Revision of S2-2300140r02. Approved Agreed
9 - - - Rel-18 SIDs - - Docs:=0 -
9.1.1 - - - Study on 5G System with Satellite Backhaul (FS_5GSATB) - - Docs:=0 -
9.1.2 - - - 5G System with Satellite Backhaul (5GSATB) - - Docs:=28 -
9.1.2 - - - Dynamic satellite backhaul - - Docs:=11 -
9.1.2 S2-2300080 LS In Action LS from SA WG5: Reply LS on reporting dynamic satellite backhaul parameters to CHF SA WG5 (S5-226685) Rel-18 Response drafted in S2-2301067. Postponed Postponed
9.1.2 S2-2301067 LS OUT Approval [DRAFT] Reply LS on reporting dynamic satellite backhaul parameters to CHF Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300080. Noted Hucheng (CATT) comments.
Yuxin (Xiaomi) comments.
Hannu (Nokia) responds Hucheng and Yuxin proposes r01
Hannu (Nokia) proposes to go ahead with r01 that acknowledges the SA5 LS, informs them of already agreed SA2 work and waits for SA5 guidance.
Stefan (Ericsson) provides r02
Hannu (Nokia) prefers r01 but can live with r02
==== Revisions Deadline ====
Stefan (Ericsson) can accept r02. Objects to r00, r01.
Yuxin (Xiaomi) proposes to note this LS as no information needs to reply
Hucheng (CATT) supports Yuxin (Xiaomi) to note this LS.
==== Final Comments Deadline ====
Noted
9.1.2 S2-2301066 CR Approval 23.501 CR4051 (Rel-18, 'F'): Charging support for dynamic satellite backhaul Nokia, Nokia Shanghai Bell Rel-18 Noted Stefan (Ericsson) provides comments and asks for the motivation of the CR
Hannu (Nokia) responds to Stefan that SA5 in their LS S2-2300080 deals with QoS related parameters.
Stefan (Ericsson) replies and proposes to note this CR for now
Hucheng(CAT) share same view as Stefan (Ericsson).
Hannu (Nokia) agrees that this CR can be noted for now, as SA2 needs to wait for SA5 decisions
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.1.2 S2-2301099 CR Approval 23.501 CR4061 (Rel-18, 'B'): Remove ENs for QoS monitoring on dynamic satellite backhaul CATT Rel-18 Postponed Hucheng (CATT) provides r01 to capture kinds of proposals.
Yuxin (Xiaomi) comments.
DongYeon (Samsung) comments.
Hannu (Nokia) proposes to postpone or to note the document.
DongYeon (Samsung) provides r02, and responds to Hannu.
Hucheng (CATT) comments.
Hannu (Nokia) is not convinced of the use case for monitoring backhaul delay only. Proposes to choose between S2-2301072 (Nokia) and S2-2300348 (Ericsson).
Hannu (Nokia) is still not convinced of the need for measuring backhaul delay only. Proposes to choose between S2-2301072 and S2-2300348 instead.
Hucheng (CATT) clarifies that S2-2301072 (Nokia) and S2-2300348 (Ericsson) will not be handled as they will be merged into this paper if their proposals are the way forward.
Stefan (Ericsson) provides r03
Hannu (Nokia) can live with r03 but provides r04 to match the cover page with the contents of this revision of the CR.
==== Revisions Deadline ====
Heng (China Telecom) supports r02.
Stefan (Ericsson) proposes to go with r04. Has concerns with r00,r01,r02.
Hannu (Nokia) can only agree r04.
Hucheng (CATT) proposes to postpone the CR, and then not agree any version.
==== Final Comments Deadline ====
Postponed
9.1.2 S2-2300349 CR Approval 23.503 CR0816 (Rel-18, 'C'): Re-using existing QoS monitoring for satellite backhaul Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.1.2 S2-2301102 CR Approval 23.503 CR0883 (Rel-18, 'B'): Update of policy control for dynamical satellite backhaul CATT Rel-18 Noted Stefan (Ericsson) provides comments and has concerns with this CR
Haris(Qualcomm) proposes to NOTE the CR
==== Revisions Deadline ====
Stefan (Ericsson) also proposes to NOTE the CR
==== Final Comments Deadline ====
Noted
9.1.2 S2-2301101 CR Approval 23.503 CR0787R2 (Rel-18, 'B'): Exposure of satellite backhaul information CATT Rel-18 Revision of S2-2210979. r02 agreed. Revised to S2-2301762. Stefan (Ericsson) provides r01
Haris(Qualcomm) provides r02
==== Revisions Deadline ====
Stefan (Ericsson) OK with r02
Hannu (Nokia) also prefers r02
Hucheng (CATT) can live with r02.
==== Final Comments Deadline ====
Revised
9.1.2 S2-2301762 CR Approval 23.503 CR0787R3 (Rel-18, 'B'): Exposure of satellite backhaul information CATT Rel-18 Revision of S2-2301101r02. Approved Agreed
9.1.2 S2-2301025 CR Approval 23.502 CR3829 (Rel-18, 'F'): Correction on AMF Reporting Satellite Category to PCF Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.1.2 S2-2300628 CR Approval 23.502 CR3760 (Rel-18, 'B'): Procedures update to support of dynamic satellite backhaul Xiaomi Rel-18 r01 agreed. Revised to S2-2301763. Stefan (Ericsson) provides comments and r01
==== Revisions Deadline ====
Yuxin (Xiaomi) is OK with r01
==== Final Comments Deadline ====
Revised
9.1.2 S2-2301763 CR Approval 23.502 CR3760R1 (Rel-18, 'B'): Procedures update to support of dynamic satellite backhaul Xiaomi Rel-18 Revision of S2-2300628r01. Approved Agreed
9.1.2 - - - Satellite edge computing - - Docs:=4 -
9.1.2 S2-2300808 CR Approval 23.501 CR3985 (Rel-18, 'B'): Add description for PSA UPF selection China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.1.2 S2-2300811 CR Approval 23.503 CR0858 (Rel-18, 'B'): Add Satellite backhaul category information as input for PCC decisions China Telecom Rel-18 Approved Yuxin (Xiaomi) provides r01 to merge S2-2300630.
Hui(Huawei) clarification the difference between the report of satellite backhaul from AMF to PCF and existing report, and object to r01
Heng (China Telecom) share the same view with Hui(Huawei).
Yuxin (Xiaomi) replies to Hui(Huawei).
Heng (China Telecom) replies to Yuxin (Xiaomi).
Yuxin (Xiaomi) replies to Heng (China Telecom) and provides r02
==== Revisions Deadline ====
Heng (China Telecom) can live with r02
Hui(Huawei): suggests to approve r00
Hui (Huawei) replies to Yuxin(Xiaomi)
Yuxin(Xiaomi) replies to Hui (Huawei) and accept r00
==== Final Comments Deadline ====
Agreed
9.1.2 S2-2300629 CR Approval 23.502 CR3761 (Rel-18, 'B'): Procedures update to support of Satellite Edge Computing Xiaomi Rel-18 r01 agreed. Revised to S2-2301764. Stefan (Ericsson) comments
Yuxin (Xiaomi) replies to Stefan (Ericsson)
Haris(Qualcomm) comments
Hannu (Nokia) responds to previous questions and comments.
Heng (China Telecom) comments
Hannu (Nokia) shares the concern of Heng and Haris that dynamic GEO backhaul might not be practical.
Yuxin (Xiaomi) replies and provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.1.2 S2-2301764 CR Approval 23.502 CR3761R1 (Rel-18, 'B'): Procedures update to support of Satellite Edge Computing Xiaomi Rel-18 Revision of S2-2300629r01. Approved Agreed
9.1.2 - - - Local data switching - - Docs:=6 -
9.1.2 S2-2301029 CR Approval 23.503 CR0876 (Rel-18, 'B'): Indication for UE-to-UE Communication via UPF on Satellite in PCC Rule Huawei, HiSilicon Rel-18 Noted Guanglei (Huawei) provides r01 for rewording
==== Revisions Deadline ====
Hannu (Nokia) asks a question on the applicability area on r01 (possible CR to next meeting?)
Guanglei (Huawei) respones to Hannu, agree to revise the text in next meeting
Laurent (Nokia): objects to any version of 1029 (or asks to POSTPONE) as the need to update AF influence for SATBH is not settled
Stefan (Ericsson) agrees that this CR is not needed and should be noted or posponed
==== Final Comments Deadline ====
Noted
9.1.2 S2-2301028 CR Approval 23.502 CR3830 (Rel-18, 'B'): AF Provides Information for UE-to-UE Communication via UPF on Satellite Huawei, HiSilicon Rel-18 Noted Guanglei (Huawei) provides r01 for rewording
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of 1028 (or asks to POSTPONE) as the need to update AF influence for SATBH is not settled
Stefan (Ericsson) agrees that this CR is not needed and should be noted or posponed
==== Final Comments Deadline ====
Noted
9.1.2 S2-2301027 CR Approval 23.501 CR4044 (Rel-18, 'B'): AF Provides Information for UE-to-UE Communication via UPF on Satellite Huawei, HiSilicon Rel-18 Noted Guanglei (Huawei) provides r01
Haris(Qualcomm) asks question for clarification
Guanglei (Huawei) replies
Hannu (Nokia) requests the explanation from Guanglei to be shown also in the CR.
Guanglei (Huawei) replies and provides r02
Hannu (Nokia) thanks Guanglei and proposes one further change in r03.
Haris(Qualcomm) comments and asks question
Guanglei (Huawei) provides r04 to remove the typo
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of 1027 (or asks to POSTPONE) as the need to update AF influence for SATBH is not settled
Stefan (Ericsson) agrees that this CR is not needed and should be noted or postponed
==== Final Comments Deadline ====
Noted
9.1.2 S2-2300859 CR Approval 23.501 CR3999 (Rel-18, 'B'): Clarification of N19 forwarding for local switch via PSA UPF on GEO Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2301765, merging S2-2301071 Guanglei (Huawei) provides r01 to merge with 1071 and 1027.
Stefan (Ericsson) provides comments
Guanglei (Huawei) replies and provides r02
Hannu (Nokia) comments and provides r03.
Guanglei (Huawei) replies and provides r04
Stefan (Ericsson) provides r05
Guanglei (Huawei) replies and provides r06
Stefan (Ericsson) provides questions
Guanglei (Huawei) provides r07 based on r06
==== Revisions Deadline ====
Hannu (Nokia) cannot agree r07 due to the addition of bullet item 3 in clause 5.43.3.3. Can still agree r06 as the outcome of this meeting.
Hannu (Nokia) corrects his previous comment on this CR. Nokia does not agree with r06 or r07 as both contain that new bullet point 3. Can still agree r05.
Stefan (Ericsson) OK with r03 and r05
Guanglei (Huawei) can live with r05, prefer r03
==== Final Comments Deadline ====
Revised
9.1.2 S2-2301765 CR Approval 23.501 CR3999R1 (Rel-18, 'B'): Clarification of N19 forwarding for local switch via PSA UPF on GEO Huawei, HiSilicon Rel-18 Revision of S2-2300859r05, merging S2-2301071. Approved Agreed
9.1.2 S2-2301071 CR Approval 23.501 CR4052 (Rel-18, 'F'): Alignment of local switching procedures with the existing 5G VN procedures Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Merged into S2-2301765 Guanglei (Huawei) propose merge to 0859
Hannu (Nokia) can live with the merge to 0859 in order to get one document for discussion but will need further updates on the 0859.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.1.2 - - - Documents exceeding TU budget - - Docs:=7 -
9.1.2 S2-2300348 CR Approval 23.501 CR3879 (Rel-18, 'C'): Re-using existing QoS monitoring for satellite backhaul Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2300483 CR Approval 23.501 CR3915 (Rel-18, 'C'): Network exposure of backhaul information LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2301026 CR Approval 23.501 CR4043 (Rel-18, 'B'): PCF Requests QoS Monitoring for Backhaul Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2301072 CR Approval 23.501 CR4053 (Rel-18, 'F'): Removal of the EN on new QoS monitoring for backhaul only Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2300630 CR Approval 23.503 CR0842 (Rel-18, 'B'): Remove Satellite backhaul category change as a Policy Control Request Triggers relevant for AMF Xiaomi Rel-18 Not Handled Yuxin (Xiaomi) proposes this CR is merged into S2-2300811 and move discussion to 0811 thread.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2301100 CR Approval 23.502 CR3839 (Rel-18, 'B'): Support of satelltie edge computing and local data switching CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.1.2 S2-2301098 CR Approval 23.501 CR4060 (Rel-18, 'B'): Remove ENs for local data switching CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.2.1 - - - Study on satellite access Phase 2 (FS_5GSAT_Ph2) - - Docs:=0 -
9.2.2 - - - Satellite access Phase 2 (5GSAT_Ph2) - - Docs:=33 -
9.2.2 S2-2301108 CR Approval 23.401 CR3721 (Rel-18, 'B'): Support of mobility management and power saving with discontinuous coverage Huawei, HiSilicon, Thales Rel-18 Postponed Hannu (Nokia) proposes that in order to align with the 5G CR, the MME need not calculate the orbit and the terminology should be aligned with the one used in TS 23.501 and 23.502 (e.g. UE out-of-coverage period) consistently throughout the CR.
Yuxin(Xiaomi) proposes to postpone this CR until S2-2300982 is approved.
Steve (Huawei) is fine to postpone.
Stefan (Ericsson) supports to postpone
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.2.2 S2-2301105 CR Approval 23.501 CR4062 (Rel-18, 'B'): Network determines the UE discontinuous satellite coverage period CATT Rel-18 Merged into S2-2301769 Steve (Huawei) Can this be considered as merged to S2-2300982?
Jean Yves (Thales) proposes to merge this document with S2-2300982
Yingying (CATT) agrees to merge this document with S2-2300982
==== Revisions Deadline ====
Yuxin (Xiaomi) reminds this CR can be seen as merged since the CR owner is a consigner of 0982
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300934 CR Approval 23.501 CR4020 (Rel-18, 'B'): Wait range during discontinuous coverage. Samsung Rel-18 r02 agreed. Revised to S2-2301766. Stephen (Qualcomm) assumes this may have been or will be merged in to S2-2300982
Lalith(Samsung) comments S2-2300982 is handling different topic.
Hannu (Nokia) supports Lalith to keep 0934 standalone CR as it does not overlap with S2-2300982 and shares r01 suggesting that this CR can be implemented in the TS at the end of clause 5.4.x after the new clauses that are added in CR S2-2300982.
Lalith(Samsung) is OK with r01.
Stephen (Qualcomm) replies to Lalith (Samsung)
Chris (Vodafone) provides r02 to allow UE to access other RATs
Steve (Huawei) comments.
Lalith(Samsung) comments.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree and prefers the r02 (as it is more precise)
Lalith(Samsung) is OK with r02
Steve (Huawei) is fine with r02.
Jean-Yves(Thales) is OK for r02
==== Final Comments Deadline ====
Revised
9.2.2 S2-2301766 CR Approval 23.501 CR4020R1 (Rel-18, 'B'): Wait range during discontinuous coverage. Samsung Rel-18 Revision of S2-2300934r02. Approved Agreed
9.2.2 S2-2300693 CR Approval 23.501 CR3966 (Rel-18, 'B'): Paging enhancement during satellite discontinuous coverage Vivo Rel-18 Revised to S2-2301853. Stefan (Ericsson) provides comments and questions
Amy (vivo) replies to Stephen
Stephen (Qualcomm) comments to Amy (vivo)
Amy (vivo) provides r01 and replies to Stephen and Stefan
Hannu (Nokia) doesn't understand what r01 is intended to say and asks questions.
Stefan (Ericsson) provides comments and asks if the CR is needed
Amy (vivo) provides r03, replies to Stefan and Hannu and kindly asks Stephen to review whether UE out-of-coverage period situation is described correctly.
Yuxin(Xiaomi) comments for r04
Steve (Huawei) Yuxin are your questions are for r03?
Steve (Huawei) provides r04
Amy (vivo) is ok with r04 provided by Steve and replies to Yuxin
Yuxin (Xiaomi) provides r05
Stefan (Ericsson) provides r06
==== Revisions Deadline ====
Amy (vivo) is ok with r06
Chris (Vodafone) is ok with r06 but the 'clauses affected' needs correcting and MCC will need guidance on how to incorporate the CR.
Steve (Huawei) is ok with r06.
Steve (Huawei) comments.
Hannu (Nokia) agrees r06 (and the proposed clean-ups).
Amy (vivo) confirms the clean-up ; )
Jean-Yves (Thales) also agrees r06 (and the proposed clean-ups).
==== Final Comments Deadline ====
Chris (Vodafone) comments that he thinks that MCC will be grateful for the CR implementation guidance for this and the related CRs.
Revised
9.2.2 S2-2301853 CR Approval 23.501 CR3966R1 (Rel-18, 'B'): Paging enhancement during satellite discontinuous coverage Vivo Rel-18 Revision of S2-2300693. Approved Agreed
9.2.2 S2-2300647 CR Approval 23.501 CR3956 (Rel-18, 'B'): Transfer of Satellite Coverage Data to a UE and AMF Qualcomm Incorporated Rel-18 r12 agreed. Revised to S2-2301767. Stephen (Qualcomm) provides an r01 with the correct WI code on the cover sheet
Guillaume (MediaTek Inc.) provides r02
Saso (Intel) asks a question on the need for NIDD.
Stephen (Qualcomm) replies to Guillaume (MediaTek Inc.) and Saso (Intel)
Lalith(Samsung) provides comments.
Steve (Huawei) comments.
Hannu (Nokia) provides r01 to clarify that the external server is an AF and that the AMF need not be aware of satellite orbit information.
Hannu (Nokia) corrects the comment to refer to r03 and clarifies that the external server is an AF and that the AMF need not be aware of satellite orbit information.
Hannu (Nokia) comments on UE related text that still remains from earlier revisions.
Hannu (Nokia) shares r04 to align the terminology with the revision of S2-2300982r10.
Amy (vivo) provides further comments on the overlapping part with S2-2300982
Hannu (Nokia) supports the comment from Amy on the overlapping parts between S2-2300647 and S2-2300982
Stefan (Ericsson) provides comments and r05
Stephen (Qualcomm) provides comments and an r06
Stephen (Qualcomm) provides comments and an r07
Lalith(Samsung) provides r08
Yuxin(Xiaomi) comments and provides r09
Jean-Yves (Thales) comments and provides r10
Stefan (Ericsson) provides r11
Stefan (Ericsson) provides r12 since emails crossed
Chris (Vodafone) is OK with R12 for NR-5GS but 'data over NAS' shall be supported for NB-IoT-EPC in any 23.401 CR
Steve (Huawei) is ok with r12.
==== Revisions Deadline ====
Stephen (Qualcomm) can also agree the r12
Lalith(Samsung) can agree from r08 to r12 and Object other revisions
Yuxin(Xiaomi) can agree r12
Jean Yves (Thales) can agree r12
==== Final Comments Deadline ====
Revised
9.2.2 S2-2301767 CR Approval 23.501 CR3956R1 (Rel-18, 'B'): Transfer of Satellite Coverage Data to a UE and AMF Qualcomm Incorporated Rel-18 Revision of S2-2300647r12. Approved Agreed
9.2.2 S2-2300649 CR Approval 23.700-28 CR0001 (Rel-18, 'F'): Resolution of EN on transfer of satellite coverage data Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2301768. Stephen (Qualcomm) provides an r01 with the correct WI code on the cover sheet
Chris (Vodafone) provides an r02 as we need 'data over NAS' for NB-IoT
Jean-Yves (Thales) supports r02, 'data over NAS' for NB-IoT needs to be supported
Saso (Intel) comments that 'or an AF over user plane' refers to NIDD; 'over user plane' should be removed from this CR.
Yuxin(Xiaomi) replies to Saso (Intel)
Saso (Intel) provides r03.
==== Revisions Deadline ====
Stephen (Qualcomm) prefers the r03 but can also agree the r02 or r01
Lalith (Samsung) prefers r03
Yuxin (Xiaomi) is ok with r03.
Steve (Huawei) is ok with r03.
Jean-Yves (Thales) is ok with r03.
==== Final Comments Deadline ====
Revised
9.2.2 S2-2301768 CR Approval 23.700-28 CR0001R1 (Rel-18, 'F'): Resolution of EN on transfer of satellite coverage data Qualcomm Incorporated Rel-18 Revision of S2-2300649r03. Approved Agreed
9.2.2 S2-2300668 DISCUSSION Discussion Provision of Satellite Coverage Data to a UE and MME/AMF. Qualcomm Incorporated Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300982 CR Approval 23.501 CR4033 (Rel-18, 'B'): Support of discontinuous coverage Huawei, HiSilicon, Thales, Intel, Xiaomi Rel-18 r21 agreed. Revised to S2-2301769, merging S2-2301105, S2-2300940, S2-2300311, S2-2300625, S2-2300340 and S2-2300470 Stephen (Qualcomm) provides an r01 and some comments
Stefan (Ericsson) provides r02, comments and questions
Steve (Huawei) comments.
Amy (vivo) provides r03 and asks for clarification
Ellen (Google) comments and provides r04
Jaewoo (LGE) provides r05 to merge S2-2300470 into S2-2300982.
Lalith(Samsung) provides r06
Lalith(Samsung) comments.
Stephen (Qualcomm) provides comments and an r07
Jaewoo (LGE) responds to Stephen (Qualcomm).
Yuxin (Xiaomi) comments and provides r08.
Steve (Huawei) comments, provides r09
Amy (vivo) comments, provides r10
Lalith(Samsung) comments on r07
Hannu (Nokia) provides r11 and co-signs.
Lalith (Samsung) provides r12
Lalith (Samsung) comments.
Stefan (Ericsson) provides r13
Ellen (Google) provides r14
Jaewoo (LGE) provides r15.
Yuxin (Xiaomi) provides r16.
Lalith(Samsung) comments on r13
Stephen (Qualcomm) provides comments and an r17
Stephen (Qualcomm) replies to Jaewoo (LGE)
Jaewoo (LGE) replies to Stephen (Qualcomm) for clarification.
Jean-Yves (Thales) comments and provides r18 to remove an EN
Jaewoo (LGE) further replies to Stephen (Qualcomm).
Steve (Huawei) provides r19.
Stefan (Ericsson) provides r20
Yingying (CATT) provides r21 and co-sign it.
==== Revisions Deadline ====
Jaewoo (LGE) asks to add 'LG Electronics' as supporting company.
Stephen (Qualcomm) can agree the r21 (and r20, r19, r18, r17), but cannot agree any version between r00 and r16
Lalith (Samsung) can agree r21 .
Yuxin(Xiaomi) is OK with r21 .
Amy (vivo) supports r21 and ok with r17-r20.
Jean-Yves (Thales) is OK with r21 .
Steve (Huawei) is ok with r21.
==== Final Comments Deadline ====
Revised
9.2.2 S2-2301769 CR Approval 23.501 CR4033R1 (Rel-18, 'B'): Support of discontinuous coverage Huawei, HiSilicon, Thales, Intel, Xiaomi, Google Inc., Samsung, vivo, Nokia, Nokia Shanghai Bell, CATT, LG Electronics Rel-18 Revision of S2-2300982r21, merging S2-2301105, S2-2300940, S2-2300311, S2-2300625, S2-2300340 and S2-2300470. Approved Agreed
9.2.2 S2-2300940 CR Approval 23.501 CR4021 (Rel-18, 'B'): Support of discontinuous coverage Samsung Rel-18 Corrupt file in ZIP! Merged into S2-2301769 Amy (vivo) provides merge suggestions
Jean Yves (Thales) proposes to merge this document with S2-2300982
Lalith(Samsung) is OK with merge proposal of Rapporteur.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300944 DISCUSSION Discussion Unreachability period and power saving. Samsung Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300626 DISCUSSION Discussion Discussion on UE centric solution optimization. Xiaomi Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300311 CR Approval 23.501 CR3873 (Rel-18, 'B'): Mobility management and/or power saving for UE in discontinuous coverage China Mobile Rel-18 Merged into S2-2301769 Dan(China Mobile) suggest to merge S2-2300311 into S2-2300982
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300278 DISCUSSION Approval DP on articulation between network centric(s) and UE centric procedures for mobility management and/or power saving for Satellite Discontinuous Coverage. Thales Rel-18 Noted Steve (Huawei) should be noted.
==== Revisions Deadline ====
Jean Yves (Tales) agree to note, discussion was held through 982
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300624 DISCUSSION Discussion Discussion on coverage information provision in UE centric and network centric solutions. Xiaomi Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300625 CR Approval 23.501 CR3950 (Rel-18, 'B'): Optimize TR conclusion to introduce UE unreachability period information is provided to UE and AMF Xiaomi Rel-18 Merged into S2-2301769 Jean Yves (Thales) proposes to merge this document with S2-2300982
Yuxin (Xiaomi) is OK to merge into 0982
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300627 CR Approval 23.501 CR3951 (Rel-18, 'B'): Optimization on information provision to AMF by UE Xiaomi Rel-18 Postponed Jean Yves (Thales) proposes to merge this document with S2-2300982
Yuxin (Xiaomi) proposes to postpone this CR as it's a different topic to S2-2300982
Jean-Yves (Thales) is OK to postpone if too heavy for merging now
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.2.2 S2-2300340 CR Approval 23.501 CR3877 (Rel-18, 'B'): Support for discontinous coverage Ericsson Rel-18 Merged into S2-2301769 Steve (Huawei) Can this be considered as merged to S2-2300982?
Jean Yves (Thales) proposes to merge this document with S2-2300982
==== Revisions Deadline ====
Yuxin (Xiaomi) reminds this CR has been merged into S2-2300982
Steve (Huawei) believes can be marked as merged to 0982.
Stefan (Ericsson) agrees to mark it as merged into 0982
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300341 DISCUSSION Agreement Provisioning of satellite coverage information to AMF/MME . Ericsson Rel-18 Noted Steve (Huawei) should be noted.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300470 CR Approval 23.501 CR3911 (Rel-18, 'B'): Add Discontinuous Coverage back-off timer LG Electonics Rel-18 Merged into S2-2301769 Jean Yves (Thales) proposes to merge this document with S2-2300982
Jaewoo (LGE) confirms that this CR is merged into S2-2300982.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.2.2 S2-2300028 LS In Action LS from CT WG1: Reply LS on Satellite coverage data transfer to a UE using UP versus CP CT WG1 (C1-227196) Rel-18 Responses drafted in S2-2300279, S2-2300671. Noted Lalith (Samsung) proposes to NOTE this LS.
Jean-Yves (Thales) also proposes to NOTE this LS.
Noted
9.2.2 S2-2300279 LS OUT Approval [DRAFT] Reply LS on Reply LS on Satellite coverage data transfer to a UE using UP versus CP THALES Rel-18 Response to S2-2300028. Noted To be merged into S2-2300671 (Noted) Jean Yves (Thales) proposes to withdrawn this LS proposal and use S2-2300671
==== Revisions Deadline ====
Steve (Huawei) should be noted or merged to 00671
Jean-Yves (Thales) OK, this LS proposal can be considered as merged to 00671
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300671 LS OUT Approval [DRAFT] Further Reply LS on Satellite coverage data transfer to a UE using UP versus CP Qualcomm Incorporated Rel-18 Response to S2-2300028. Noted Saso (Intel) provides r01.
Stephen (Qualcomm) replies to Saso (Intel)
Hannu (Nokia) shares r02 and points out that the external server beyond N6 is only needed for the UE configuration.
Stefan (Ericsson) provides comments
Stephen (Qualcomm) provides comments and an r03
Lalith(Samsung) comments.
Stephen (Qualcomm) replies to Lalith (Samsung)
Chris (Vodafone) provides r04 to allow Data over NAS to be user to carry N6 data.
Lalith (Samsung) replies to Stephen (Qualcomm)
Yuxin (Xiaomi) comments
Jean-Yves (Thales) comments and supports r04,data over NAS is necessary for NB-IoT
Guillaume (MediaTek Inc.) provides r05
Steve (Huawei) provides r06
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r06 (and r05)
Lalith(Samsung) comments to NOTE this LS. Not OK to send this LS.
==== Final Comments Deadline ====
Noted
9.2.2 S2-2300062 LS In Action LS from SA WG1: Reply LS on Latency impact for NTN verified UE location SA WG1 (S1-223539) Rel-18 Noted Chunhui (Xiaomi) proposes to NOTE this LS. Noted
9.2.2 - - - Documents exceeding TU budget - - Docs:=5 -
9.2.2 S2-2301118 CR Approval 23.502 CR3842 (Rel-18, 'B'): Procedures for support of satellite discontinuous coverage data transfer CATT Rel-18 Not Handled Postpone to SA2#155 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.2.2 S2-2300694 CR Approval 23.502 CR3776 (Rel-18, 'B'): Paging enhancement with satellite discontinuous coverage Vivo Rel-18 Not Handled Postpone to SA2#155 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.2.2 S2-2300983 CR Approval 23.502 CR3823 (Rel-18, 'B'): Procedures for support of discontinuous coverage Huawei, HiSilicon, Thales, Intel, Xiaomi Rel-18 Not Handled Postpone to SA2#155 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.2.2 S2-2300939 CR Approval 23.502 CR3818 (Rel-18, 'B'): Wait range during discontinuous coverage. Samsung Rel-18 Not Handled Postpone to SA2#155 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.2.2 S2-2300471 CR Approval 23.502 CR3731 (Rel-18, 'B'): Procedures for discontinuous coverage back-off timer LG Electonics Rel-18 Not Handled Postpone to SA2#155 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 - - - Study on Personal IoT Networks (FS_5G_PIN) - - Docs:=26 -
9.3.1 - - - LS in/out - - Docs:=8 -
9.3.1 S2-2300015 LS In Action LS from SA WG6: LS on PIN Management SA WG6 (S6-222870) Rel-18 Revision of postponed S2-2210205 from S2#154. Responses drafted in S2-2300968, S2-2301044. Final response in S2-2301362 Replied to
9.3.1 S2-2300968 LS OUT Agreement [DRAFT] Reply to LS on PIN Management Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300015. r02 agreed. Revised to S2-2301362, merging S2-2301044 Lalith(Samsung) provides r01
Marco (Huawei) provides r02 considering SoH result
Pallab (Nokia) responds to Lalith(Samsung) and Marco (Huawei). OK with r02
Lalith(Samsung) is OK with r02
==== Revisions Deadline ====
Marco(Huawei) OK R02. Object r00-r01
Qian (Ericsson) is OK with R02.
==== Final Comments Deadline ====
Revised
9.3.1 S2-2301362 LS OUT Agreement Reply to LS on PIN Management SA WG2 Rel-18 Revision of S2-2300968r02, merging S2-2301044. Approved Approved
9.3.1 S2-2301044 LS OUT Approval [DRAFT] Reply LS on PIN Management Samsung Rel-18 Response to S2-2300015. Merged into S2-2301362 Merge into S2-2300968 Marco(Huawei) proposes to note this LS
==== Revisions Deadline ====
Lalith(Samsung) is OK to mark it merged into S2-2300968 based on rapporteur guidance.
==== Final Comments Deadline ====
Merged
9.3.1 S2-2300016 LS In Action LS from SA WG6: LS on Support PIN application architecture and interaction SA WG6 (S6-223028) Rel-18 Revision of postponed S2-2210206 from S2#154. Responses drafted in S2-2300438, S2-2300969, S2-2301206. Postponed Postponed
9.3.1 S2-2300438 LS OUT Approval [DRAFT] Reply LS on support PIN vivo Response to S2-2300016. Postponed To be merged into S2-2301206 (Postponed) Marco(Huawei) propose to Merge into S2-2301206
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.1 S2-2300969 LS OUT Agreement [DRAFT] Reply LS on Support PIN application architecture and interaction Nokia, Nokia Shanghai Bell Rel-18 Response to S2-2300016. Postponed To be merged into S2-2301206 (Postponed) Marco(Huawei) propose to Merge into S2-2301206
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.1 S2-2301206 LS OUT Approval [DRAFT] Reply LS on Support PIN application architecture and interaction InterDigital Inc. Rel-18 Response to S2-2300016. Postponed Saad (InterDigital) comments and provides r01
Marco(Huawei) provides r02
==== Revisions Deadline ====
Qian (Ericsson) provides comments and checks if it's better to postpone the LS
Pallab (Nokia) agrees that the LS Out needs more work. Also thinks it is better to POSTPONE. Cannot agree to r02
==== Final Comments Deadline ====
Postponed
9.3.1 - - - Discussion - - Docs:=1 -
9.3.1 S2-2300467 DISCUSSION Discussion Additional parameters in N3GPP QoS Assistance information. Qualcomm Incorporated Rel-18 Noted Marco(Huawei) proposed to note, since solved in SoH
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.3.1 - - - Update on TR conclusions - - Docs:=6 -
9.3.1 S2-2300227 P-CR Approval 23.700-88: KI#3, Conclusion updates . Ericsson Rel-18 r03 agreed. Revised to S2-2301363. Basis for KI#3 Zhenhua (vivo) provides r01.
Qian (Ericsson) provides r02 based on result of SoH.
Marco (Huawei) provides r03 to better reflect the SoH
==== Revisions Deadline ====
Pallab (Nokia) supports r03 as it better reflects the SoH result and proposes to approve r03
Qian (Ericsson) supports r03
Kefeng (Qualcomm) prefers r03
==== Final Comments Deadline ====
Revised
9.3.1 S2-2301363 P-CR Approval 23.700-88: KI#3, Conclusion updates . Ericsson Rel-18 Revision of S2-2300227r03. Approved Approved
9.3.1 S2-2301208 P-CR Approval 23.700-88: Solve open ENs. Huawei, Hisilicon Rel-18 r03 + change agreed. Revised to S2-2301364. Basis for KI#7 Jianning (Xiaomi) provide comment
Zhenhua (vivo) provides r01.
Zhenhua (vivo) provide r02
Marco (Huawei) provide r03
==== Revisions Deadline ====
Pallab (Nokia) points out that there is some overlap for KI#4 conclusions between this paper and 0970. Proposes to go with the updates in 0970 for KI#4
Jianning (Xiaomi) suggests to approve only content of KI#7 in this paper. leave the KI#4 part to 0970 for approval
Qian (Ericsson) supports r03 + remove the updates for KI#4 (which is covered in 0970)
Kefeng (Qualcomm) supports r03 + removal all the updates for KI#4
Marco(Huawei) OK with r03 + removal all the updates for KI#4
==== Final Comments Deadline ====
Revised
9.3.1 S2-2301364 P-CR Approval 23.700-88: Solve open ENs. Huawei, Hisilicon Rel-18 CC#4: Revision of S2-2301208r03 + change. Approved Approved
9.3.1 S2-2300970 P-CR Approval 23.700-88: 23.700-88: Conclusions update for KI#4. Nokia, Nokia Shanghai Bell Rel-18 r06 agreed. Revised to S2-2301365. CC#4: Noted. Comment from Huawei recorded Basis for KI#4 and KI#5 Kefeng Zhang(Qualcomm) provides comment that one PDU session may serve one or more PIN.
Kefeng Zhang (Qualcomm) updated Bullet 2, 3, 11 on KI#4 and provides r02.
Zhenhua (vivo) provides r01.
Jianning (Xiaomi) corrects the title and reply to Kefeng (Qualcomm)
Serge (T-Mobile USA) provides r03.
Zhenhua (vivo) provides r04.
Pallab (Nokia) provides r05.
Serge (T-Mobile USA) cannot accept r05, provides r06
==== Revisions Deadline ====
Pallab (Nokia) OK to approve r06.
Jianning (Xiaomi) is ok to approve r06
Qian (Ericsson) is ok to with r06
Kefeng (Qualcomm) objects r05, r06, OK with r04.
Pallab (Nokia) checks with Kefeng (Qualcomm) whether r06 is acceptable if changes in bullet 11) of clause 8.4 are re-instated.
Marco(Huawei) objects from R00 to R05, OK with R06. R06 Bullet 11 wording leave open to normative discussion USRP vs RSP
Kefeng (Qualcomm) is OK with r04, in addition I only accept r05, r06 with removal of any changes to bullet 11 of 8.4, and objects to all others.
Marco (Huawei) comments.
Pallab (Nokia) Objects to r01,02,03,04. Can accept r06 or r06 + re-instating changes in bullet 11). Can also consider any other alternative for bullet 11) changes on top of r06.
==== Final Comments Deadline ====
Noted
9.3.1 S2-2301365 P-CR Approval 23.700-88: 23.700-88: Conclusions update for KI#4. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300970r06. Approved. CC#4: WITHDRAWN Withdrawn
9.3.1 - - - Documents exceeding TU budget - - Docs:=11 -
9.3.1 S2-2301203 P-CR Approval 23.700-88: KI#7, Conclusion Update. InterDigital Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2301124 P-CR Approval 23.700-88: Conclusion Update for Key Issue#3. Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2301125 P-CR Approval 23.700-88: Conclusion Update for Key Issue#4. Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300971 P-CR Approval 23.700-88: 23.700-88: Conclusions update for KI#4, KI#5 to remove EN. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300230 P-CR Approval 23.700-88: KI#7, Conclusion . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300229 P-CR Approval 23.700-88: KI#5, Conclusion updates . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300435 P-CR Approval 23.700-88: Resolve EN on conclusion of KI#3. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300437 P-CR Approval 23.700-88: Resolve ENs on conclusion of KI#4 and KI#5. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300436 P-CR Approval 23.700-88: Resolve ENs on conclusion of KI#4 and KI#5. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300271 P-CR Approval 23.700-88: KI #4, Conclusion Update. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.1 S2-2300228 P-CR Approval 23.700-88: KI#4, Conclusion updates. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.3.2 - - - Personal IoT Networks (5G_PIN) - - Docs:=34 -
9.3.2 - - - CRs for 23.501 - - Docs:=20 -
9.3.2 S2-2301126 CR Approval 23.501 CR4073 (Rel-18, 'B'): PEMC-PEGC registration and authorization Xiaomi Rel-18 Postponed Qian (Ericsson) provides comments
Jianning (Xiaomi) response
Pallab (Nokia) provides comments
Kefeng (Qualcomm) provides comments
Jianning (Xiaomi) provides r01 based on SoH
==== Revisions Deadline ====
Pallab (Nokia) proposes to NOTE this paper, as in our view this 5GMM capability indication is not needed
Jianning (Xiaomi) response to Pallab (Nokia). PIN capability exchanging between UE and 5GC is necessary and needed before UE requesting to use PIN feature.
Pallab (Nokia) responds to Jianning (Xiaomi). Maintains objection.
Qian (Ericsson) supports to postpone the paper.
Jianning (Xiaomi) responses to Pallab(Nokia)
Marco(Huawei) object r00
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2301207 CR Approval 23.501 CR4092 (Rel-18, 'B'): PIN definition and architecture Huawei, Hisilicon Rel-18 r05 agreed. Revised to S2-2301366, merging S2-2300425 Jianning (Xiaomi) provide comment
Zhenhua (vivo) provides r01.
LaeYoung (LGE) comments.
Marco (Huawei) provide r02
Zhenhua (vivo) provide r03
Marco (Huawei) i'm OK with R03
Jianning (Xiaomi) is ok with r03
LaeYoung (LGE) is fine with r03.
Jianning (Xiaomi) provides comment
Zhenhua (vivo) replies
Pallab (Nokia) comments and provides r04
Zhenhua (vivo) replies to Pallab (Nokia)
Zhenhua (vivo) provides r05
==== Revisions Deadline ====
Pallab (Nokia) Objects to r05. Proposes to approve r04 with below changes:
Change the text 'Only a UE can be a PEGC' to 'Only a UE is able to act as a PEGC'
Jianning (Xiaomi) suggests to go with r05, cannot accept r04 that removes the architecture assumption, since we need to re-evaluate whether it impacts on the existing conclusions or not
Qian (Ericsson) comments and prefers to go with r04
Marco(Huawei) object r04 , OK r03 & R05. I object Pallab's proposal.
Pallab (Nokia) can accept r05 if the definition of PEMC is removed.
Pallab (Nokia) responds to Marco(Huawei)
Jianning (Xiaomi) objects to remove definition of PEMC
Pallab (Nokia) responds to Jianning (Xiaomi).
Marco (Huawei) propose way out (see email)
Jianning (Xiaomi) prefers the option 'definition of PEMC + EN'
Pallab (Nokia) thanks Marco (Huawei) for the proposal. Provides some comment. Can accept the way forward option 2) R05 without definition of PEMC + EN
==== Final Comments Deadline ====
Revised
9.3.2 S2-2301366 CR Approval 23.501 CR4092R1 (Rel-18, 'B'): PIN definition and architecture Huawei, Hisilicon Rel-18 Revision of S2-2301207r05, merging S2-2300425. Approved Agreed
9.3.2 S2-2300972 CR Approval 23.501 CR4028 (Rel-18, 'B'): Informative Annex on PIN Architecture Nokia, Nokia Shanghai Bell Rel-18 r08 agreed. Revised to S2-2301367, merging S2-2300427 Jianning (Xiaomi) provide comment
Jicheol (Samsung) provides comments.
Saad (InterDigital) comments
Kefeng Zhang (Qualcomm) comments
marco (Huawei) have a concern to have reference architecture and assumptions as informative. This shall be in clause 4.x
marco (Huawei) provide r01 moving to normative part
Qian (Ericsson) provides comments and has strong concern on introducing normative text has nothing to do with 5GS/5GC.
marco (huawei) answer to Qian (Ericsson).
Saad (InterDigital) comments on r01
Pallab (Nokia) replies. Has same concerns with r01 as raised by Ericsson. Provides r02 based on r00
Jianning (Xiaomi) provide views
Zhenhua (vivo) provides r03
Saad (InterDigital) provides r04 and more comments
Qian (Ericsson) comments and provides r05
Pallab (Nokia) comments and provides r06 based on r05
Marco (Huawei ) that I will object to any version that has the assumptions in the informative annex, since they are Normative essential statements
Jianning (Xiaomi) shares the view with Marco (Huawei)
Pallab (Nokia) provides r07 to take care of concerns from Jianning (Xiaomi) and Marco (Huawei )
Zhenhua (vivo) provides r08
==== Revisions Deadline ====
Marco(Huawei) ok with R07 & r08 object any other versions
Jianning (Xiaomi) only accept r08, and object r07
Kefeng (Qualcomm) is ok with r07 & r08.
==== Final Comments Deadline ====
Revised
9.3.2 S2-2301367 CR Approval 23.501 CR4028R1 (Rel-18, 'B'): Informative Annex on PIN Architecture Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300972r08, merging S2-2300427. Approved Agreed
9.3.2 S2-2300474 CR Approval 23.501 CR3912 (Rel-18, 'B'): Non-3GPP QoS and delay budget - 23.501 Qualcomm Incorporated Rel-18 r08 agreed. Revised to S2-2301368. Marco(Huawei) ask clarification
Kefeng (Qualcomm) replies Marco(Huawei) and provides r01.
Qian (Ericsson) provides comments.
Kefeng (Qualcomm) replies Qian (Ericsson) comments.
Qian (Ericsson) provides further comments.
Qian (Ericsson) provides comments and r02.
Kefeng (Qualcomm) replies Qian (Ericsson) comments and provides r03.
Pallab (Nokia) comments and provides r04
Kefeng (Qualcomm) is OK with r04
Qian (Ericsson) comments and provides r05
Marco(Huawei) provide r06 on top of r05
Marco(Huawei) provide r07 on top of r04
Kefeng (Qualcomm) provide r08 on top of r06
==== Revisions Deadline ====
Marco(Huawei) ok with r06, R07 & r08 . object any other versions
Kefeng (Qualcomm) only OK with r08, r03, objects all others
==== Final Comments Deadline ====
Revised
9.3.2 S2-2301368 CR Approval 23.501 CR3912R1 (Rel-18, 'B'): Non-3GPP QoS and delay budget - 23.501 Qualcomm Incorporated Rel-18 Revision of S2-2300474r08. Approved Agreed
9.3.2 S2-2300428 CR Approval 23.501 CR3904 (Rel-18, 'B'): PIN operations over application layer Vivo Rel-18 Noted Saad (InterDigital) comments
Kefeng (Qualcomm) comments
Marco(Huawei) comment to note this document since it describes aspects outside SA2 scope (app layer interaction over UP).
Qian (Ericsson) share the same view as previous comments and consider the content is not really related to SA2 specs.
Pallab (Nokia) shares same view in previous comments and proposes to NOTE the CR
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.3.2 S2-2300421 CR Approval 23.501 CR3897 (Rel-18, 'B'): PIN communication configuration Vivo Rel-18 r12 agreed. Revised to S2-2301369. Zhenhua (vivo) provides r01.
Marco(Huawei) asks clarifications. The CR shall be revised to reflect SoH result
Zhenhua (vivo) replies to Marco(Huawei)
Qian (Ericsson) provides comments
Zhenhua (vivo) replies to Qian (Ericsson) and provides r02
Kefeng (Qualcomm) comments to r02
Zhenhua (vivo) provides r03
Pallab (Nokia) provides comments on r03
Zhenhua (vivo) replies to Pallab (Nokia)
Zhenhua (vivo) provides r04
Jianning (Xiaomi) provides comments on r04
Zhenhua (vivo) replies to Jianning (Xiaomi)
Qian (Ericsson) comments and provides r05 with structure focus
Zhenhua (vivo) provides r06 to align with SoH
Zhenhua (vivo) provides r07 to merge session related text from S2-2300422
Pallab (Nokia) provides r08. Objects to all previous revisions including r00
Zhenhua (vivo) comments on r08
Zhenhua (vivo) objects r08 and provides r09
LaeYoung (LGE) comments.
Marco (Huawei) comments r08 and r09
Boren (OPPO) comments.
Jianning (Xiaomi) comments
Zhenhua (vivo) replies to Boren (OPPO).
Zhenhua (vivo) replies and provides r10
Pallab (Nokia) provides r11
Zhenhua (vivo) provides r13 based on r10 and r12
Qian (Ericsson) provides r12
Pallab (Nokia) objects to r13 for reasons already explained
Pallab (Nokia) responds to Zhenhua (vivo).
Zhenhua (vivo) replise
Jianning (Xiaomi) provide comment
==== Revisions Deadline ====
Pallab (Nokia) responds to Zhenhua (vivo). Proposes to approve r12
Kefeng (Qualcomm) proposes to approve r12 and provides comments to r13
Qian (Ericsson) proposes also to go with r12 + some change proposals as way forward
Jianning (Xiaomi) proposes to go with r12 + some change proposals as way forward
Kefeng (Qualcomm) is OK to go with r12 + some change proposals as way forward
Pallab (Nokia) also OK with r12 + some changes
Qian (Ericsson) comment that we probably can go with r12 + 2 ENs (Editor's Note: The handling of PEMC in 5GC in relation with PIN is FFS + Editor's Note: The handling of PIN deletion/deactivation/activation is FFS), as provided in r14.
==== Final Comments Deadline ====
Revised
9.3.2 S2-2301369 CR Approval 23.501 CR3897R1 (Rel-18, 'B'): PIN communication configuration Vivo Rel-18 Revision of S2-2300421r12. Approved Agreed
9.3.2 S2-2300272 CR Approval 23.501 CR3862 (Rel-18, 'B'): New Annex on PIN Session Model Samsung Rel-18 Postponed Jianning (Xiaomi) provide comment
Zhenhua (vivo) provides r01.
Jicheol (Samsung) provides comments.
Kefeng (Qualcomm) provides comments and suggest to postponed the CR.
Marco(Huawei) suggest to postpone the CR
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300231 CR Approval 23.501 CR3854 (Rel-18, 'B'): PIN support in 5GC Ericsson Rel-18 r14 + changes agreed. Revised to S2-2301370, merging S2-2300424 Zhenhua (vivo) provides r01.
Marco(Huawei) this CR needs to be revised based on SoH
Qian (Ericsson) provides comments related to the structure of the PIN support
Zhenhua (vivo) provides r02
Kefeng (Qualcomm) provides comments on r02
Zhenhua (vivo) replies to Kefeng (Qualcomm)
Pallab (Nokia) provides comments on r02. Provides r03. Needs further revision based on SoH result
Zhenhua (vivo) comments on r03
Zhenhua (vivo) provides r04
Jianning (Xiaomi) provide comment
Zhenhua (vivo) provide r05
Qian (Ericsson) provides r07 based on SoH (Please ignore r06)
Pallab (Nokia) provides r08 based on r07
LaeYoung (LGE) comments on r08.
Marco (Huawei) will not object to any version without assumptions in normative text (not in informative annex) and provider r09
Qian (Ericsson) asks questions on r09.
Pallab (Nokia) responds to LaeYoung (LGE)
LaeYoung (LGE) thanks to answers from Pallab (Nokia) and would like to clarify that Qian (Ericsson) provided r10.
Qian (Ericsson) thanks to LaeYoung (LGE) and confirms that r10 is provided. ??
Zhenhua (vivo) provides r11
Qian (vivo) provides r12
ERRATA CORRIGE: Marco (Huawei) will not object to any version without assumptions in normative text (not in informative annex) and provider r09
Jianning (Xiaomi) provide comments on r12 and provide r13
Zhenhua (vivo) provides r14
==== Revisions Deadline ====
Pallab (Nokia) is OK with r08, r10. Objects to all other revisions. As a compromise can accept r14 with below changes:

Change 1:
'A PIN includes at least one UE with PEGC and one or more UE with PEMC.'
to
'A PIN includes at least one UE with PEGC and may include one or more UE with PEMC.'

Change 2:
'The 5GC is enhanced to support the delivery of PIN related UE policy and the session policy control for PIN service, if PEGC/PEMC is registered in 5GS.'
to
'The 5GC is enhanced to support the delivery of PIN related UE policy and the session policy control for PIN service.'
Jianning (Xiaomi) suggests to go r14
Pallab (Nokia) responds to Jianning (Xiaomi)
Qian (Ericsson) comments and ask Pallab (Nokia) a question.
Pallab (Nokia) removes objection from r14 in order to allow progress
Jianning (Xiaomi) replies to Pallab (Nokia)
Kefeng (Qualcomm) objects r14, OK with r13
Jianning (Xiaomi) object r12 and any versions that to make PEMC as optional. But only can live with r12 by removing the word 'optionally' in the statement 'optionally one or more UE with PEMC'
Qian (Ericsson) comments and provides way forward (based on r14 + with changes below)
Marco (comments) that Qian (Ericsson) proposal that assumption are not present and several other issue . SO I keep my objection (note that in char note the 'not' with strikeout character is not present giving opposite reading)
Qian (Ericsson) asks Macro (Huawei) a question
Jianning (Xiaomi) asks questions for clarification to Marco (Huawei)
Qian (Ericsson) provides further proposal
Kefeng (Qualcomm) replies Qian (Ericsson) suggestion.
Pallab (Nokia) comments
marco (huawei) proposes as worst case to approve only the 1st paragraph in order to have the clause where to add the other approved CR..
Qian (Ericsson) indicates following changes on top of r14 probably can be agreed:
1. replace 'with optionally' with 'and/or' in first sentence of 2nd paragraph
2. remove 'PIN related UE policy and'
3. add 'Editor's Note: the management role between PEMC/AF is FFS.'
==== Final Comments Deadline ====
Marco (Huawei) comments that I can accept this proposal from Xiaomi, but I would say that next meeting I will propose other assumption that has been removed and I repeatedly ask to add.
Qian (Ericsson) indicates following changes on top of r14 probably can be agreed:
1. Replace 'with optional' with 'and' + add 'if AF deployed' in first sentence of 2nd paragraph
2. remove 'PIN related UE policy and'
3. add 'Editor's Note: the management role between PEMC/AF is FFS.'
Revised
9.3.2 S2-2301370 CR Approval 23.501 CR3854R1 (Rel-18, 'B'): PIN support in 5GC Ericsson Rel-18 Revision of S2-2300231r14 + changes, merging S2-2300424. CC#4: Approved Agreed
9.3.2 S2-2300424 CR Approval 23.501 CR3900 (Rel-18, 'B'): PIN subscription Vivo Rel-18 Merged into S2-2301370 Qian (Ericsson) checks if this one shall be considered as merged into 0231
Zhenhua (vivo) asks for clarification
Zhenhua (vivo) is OK to merge into S2-2300231
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.3.2 S2-2300425 CR Approval 23.501 CR3901 (Rel-18, 'B'): Terms and abbreviations for PIN Vivo Rel-18 Merged into S2-2301366 Merge into S2-2301207 Zhenhua (vivo) proposes to merge into S2-2301207
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.3.2 S2-2300423 CR Approval 23.501 CR3899 (Rel-18, 'B'): PIN identifiers Vivo Rel-18 r04 agreed. Revised to S2-2301371. Marco(Huawei) need to be revised based on SoH
Zhenhua (vivo) provides r01 to align with the SoH result and add Interdigital as co-signer
Jianning (Xiaomi) provide r02
Boren (OPPO) comments on r02.
Jianning (Xiaomi) response to Boren (OPPO)
Zhenhua (vivo) provide r03
Marco (Huawei) provide r04
Jianning (Xiaomi) provide comment
==== Revisions Deadline ====
Qian (Ericsson) is ok with r04
Kefeng (Qualcomm) is ok with r04
==== Final Comments Deadline ====
Revised
9.3.2 S2-2301371 CR Approval 23.501 CR3899R1 (Rel-18, 'B'): PIN identifiers Vivo, Interdigital Rel-18 Revision of S2-2300423r04. Approved Agreed
9.3.2 S2-2300426 CR Approval 23.501 CR3902 (Rel-18, 'B'): PIN and PIN session models Vivo Rel-18 Noted Zhenhua (vivo) provides r01.
LaeYoung (LGE) proposes to NOTE this CR.
==== Revisions Deadline ====
Qian (Ericsson) supports to NOTE this CR.
==== Final Comments Deadline ====
Noted
9.3.2 S2-2300422 CR Approval 23.501 CR3898 (Rel-18, 'B'): PIN policy configuration Vivo Rel-18 Postponed Zhenhua (vivo) provides r01.
Pallab (Nokia) provides comments.
Zhenhua (vivo) answers to Pallab (Nokia).
Qian (Ericsson) provides comments.
Zhenhua (vivo) asks Qian (Ericsson) for clarification
Kefeng Zhang (Qualcomm) provides comments.
Zhenhua (vivo) provides r02.
Pallab (Nokia) responds to Zhenhua (vivo).
Pallab (Nokia) comments on r02.
Zhenhua (vivo) replies to Pallab (Nokia) and provides r03.
Zhenhua (vivo) replies Pallab (Nokia) about PRSP and URSP.
Qian (Ericsson) comments and provides r04 with structure focus
Zhenhua (vivo) provides r05
Pallab (Nokia) comments on r05.
Zhenhua (vivo) provides r06.
Jianning (Xiaomi) comments on r06
Qian (Ericsson) provides r07
Zhenhua (vivo) provides r08
Qian (Ericsson) provides comments on r08
Yishan (Huawei) provides r10
Yishan (Huawei) provides comments
Zhenhua (vivo) replies to Yishan (Huawei)
Kefeng (Qualcomm) objects r09
Kefeng (Qualcomm) objects r10
Kefeng (Qualcomm) provides r11
==== Revisions Deadline ====
Pallab (Nokia) proposes to approve r10. Objects to all other revisions. R11 was provided after deadline.
Kefeng (Qualcomm) proposes to approve r11 (5 mins late due to mailing server processing) . Objects to all other revisions.
Just to clarify Pallab (Nokia) also objects to r11. Can go with only r10
Pallab (Nokia) is OK with the way forward propose by Qian (Ericsson)
Qian (Ericsson) comments and propose a way forward.
Jianning (Xiaomi) is ok with way forward proposed by Qian, i.e. r10 + remove '(e.g. corresponding URSP rule associated with the PIN)'
Kefeng (Qualcomm) proposes to postponed the CR.
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300427 CR Approval 23.501 CR3903 (Rel-18, 'B'): PIN architecture Vivo Rel-18 Merged into S2-2301367 Merge into S2-2300972 Zhenhua (vivo) proposes to merge into S2-2300972.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.3.2 - - - CRs for 23.502 - - Docs:=10 -
9.3.2 S2-2301127 CR Approval 23.502 CR3845 (Rel-18, 'B'): PEMC and PEGC Authorization for PIN service Xiaomi Rel-18 Postponed Zhenhua (vivo) provides r01
Pallab (Nokia) provides comments
Zhenhua (vivo) provides comments
Jianning (Xiaomi) response to Zhenhua(vivo) and Pallab (Nokia)
Marco (Huawei) ask clarification
Qian (Ericsson) provides comments
LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Jianning (Xiaomi) replies to Qian(Ericsson) and Marco (Huawei)
Pallab (Nokia) supports the suggestion to postpone all 23.502 CRs
Jianning (Xiaomi) provides view and it is to earlier to decide to postpone, we still have time after SoH to progress
LaeYoung (LGE) points out that this CR has dependency with SoH Q.
Kefeng (Qualcomm) provides comments.
Jianning (Xiaomi) provide r02 based on the SoH
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
Jicheol (Samsung) shares the same view with LGE, Nokia, Ericsson and Huawei.
Jianning (Xiaomi) is ok to postpone this paper
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2301128 CR Approval 23.502 CR3846 (Rel-18, 'B'): Support internal and external PIN identifier Xiaomi Rel-18 Postponed To be merged into S2-2300726 (Postponed) Zhenhua (vivo) proposes to merge into S2-2300726.
Jianning (Xiaomi) agrees to merge into S2-2300726.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300726 CR Approval 23.502 CR3779 (Rel-18, 'B'): Definition of PIN Group ID Huawei, HiSilicon Rel-18 Postponed Zhenhua (vivo) provides r01
Kefeng Zhang (Qualcomm) provides comments to r01.
Pallab (Nokia) provides comments.
Marco (Huawei) provides R02 where 'group' is removed.
Qian (Ericsson) provides comments related to r02.
LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
marco (Huawei) answer to Qian (Ericsson) andPallab (Nokia) and provide r03
LaeYoung (LGE) provides comment.
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300433 CR Approval 23.502 CR3723 (Rel-18, 'B'): PIN related data in UDM and UDR Vivo Rel-18 Postponed LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Jianning (Xiaomi) thinks it is too earlier to make such decide to Postpone all 502CRs
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300473 CR Approval 23.502 CR3732 (Rel-18, 'B'): PIN Route Selection Policy - 23.502 Qualcomm Incorporated Rel-18 Postponed LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
LaeYoung (LGE) sees that PRSP vs. URSP is still controversial and under discussion at S2-2300472 thread.
Marco(Huawei) proposes to postpone to wait conclusion of 501 discussion on PRSP vs. URSP
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300431 CR Approval 23.502 CR3721 (Rel-18, 'B'): PIN data configuration Vivo Rel-18 Postponed LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Marco (Huawei) propose to postpone in order to have more stable 501 text.
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300429 CR Approval 23.502 CR3719 (Rel-18, 'B'): AF influence traffic QoS and routing for PIN Vivo Rel-18 Postponed LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300430 CR Approval 23.502 CR3720 (Rel-18, 'B'): PEGC-initiated traffic QoS and routing for PIN Vivo Rel-18 Postponed Pallab (Nokia) provides comments.
Zhenhua (vivo) replies to Pallab (Nokia).
Kefeng Zhang (Qualcomm) provides comments.
Marco (Huawei) comments.
Zhenhua (vivo) replies to Kefeng Zhang (Qualcomm).
LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Qian (Ericsson) supports the proposal from LaeYoung(LGE) to postpone
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300475 CR Approval 23.502 CR3733 (Rel-18, 'B'): Non-3GPP QoS and delay budget - 23.502 Qualcomm Incorporated Rel-18 Postponed Qian (Ericsson) provides comments
LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Kefeng (Qualcomm) replies Qian (Ericsson) comments
Kefeng (Qualcomm) replies LaeYoung (LGE) and claim that the open issues for SoH have no impact on the proposed procedures.
LaeYoung (LGE) replies to Kefeng (Qualcomm) that the related 23.501 CR needs to be stabilized first.
Pallab (Nokia) comments and provides r01. r01 is provided for illustration of some comments. Does not mean we approve r01
Kefeng (Qualcomm) replies Pallab (Nokia) comments.
Marco (Huawei) provide r02.
Qian (Ericsson) comments and proposes to postpone the paper.
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
Kefeng (Qualcomm) is OK with r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300432 CR Approval 23.502 CR3722 (Rel-18, 'B'): PIN join Vivo Rel-18 Postponed Pallab (Nokia) provides comments.
Zhenhua (vivo) answers.
Pallab (Nokia) responds to Zhenhua (vivo).
Zhenhua (vivo) replies.
Zhenhua (vivo) provides r01.
LaeYoung (LGE) proposes to POSTPONE this 23.502 CR because conclusions/SoH are still under discussion.
Zhenhua (vivo) claims that the open issues for SoH have no impact on the proposed procedures.
Kefeng (Qualcomm) provides comments on r01.
Qian (Ericsson) supports the approach proposed by LaeYoung (LGE) ??.
Pallab (Nokia) also supports the approach proposed by LaeYoung (LGE).
Zhenhua (vivo) replies to Kefeng (Qualcomm)
Qian (Ericsson) provides comments and proposes to postpone the paper
Marco (Huawei) propose to postpone all 502 in order to have a consistent set of CRs to be added TS.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 - - - CRs for 23.503 - - Docs:=3 -
9.3.2 S2-2300727 CR Approval 23.503 CR0849 (Rel-18, 'B'): URSP extension for PIN Huawei, HiSilicon Rel-18 Postponed Jicheol (Samsung) proposes to note (or merge to S2-2300472).
Jianning (Xiaomi) propose to keep it open currently
Zhenhua (vivo) clarifies
Marco (Huawei) answer to Zhenhua(Vivo)
Qian (Ericsson) provides comments
Pallab (Nokia) shares the same view as Ericsson, Huawei
Kefeng (Qualcomm) provides comments.
Marco (Huawei) further comments
Marco (Huawei) provide R02 removing 'Group'
Kefeng (Qualcomm) replies Marco (Huawei) comments.
==== Revisions Deadline ====
Pallab (Nokia) proposes to POSTPONE. We have competing proposals in 0727 and 0472, both cannot be agreed. We should first agree on PRSP vs URSP and then come back on this CR
Kefeng (Qualcomm) objects any revision of this CR
Jianning (Xiaomi) also suggests to postpone this CR, until there is consensus on URSP or PRSP
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300434 CR Approval 23.503 CR0830 (Rel-18, 'B'): PIN Routing Selection Policy Vivo Rel-18 Postponed To be merged into S2-2300472 (Postponed) Zhenhua (vivo) proposes to merge into S2-2300472.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.3.2 S2-2300472 CR Approval 23.503 CR0833 (Rel-18, 'B'): PIN Route Selection Policy - 23.503 Qualcomm Incorporated Rel-18 Postponed Jicheol (Samsung) comments.
Kefeng Zhang (Qualcomm) provides r02
Zhenhua (vivo) provides r01
Zhenhua (vivo) comments on r02
Zhenhua (vivo) replies to Jicheol (Samsung).
Zhenhua (vivo) provides r03
Kefeng Zhang (Qualcomm) provides comments on r03.
Jianning (Xiaomi) provide comments
Zhenhua (vivo) provides r04
Marco (Huawei) express concern on why a route policy for PIN need to be define since it refers/endorses URSP
Kefeng (Qualcomm) replies Marco (Huawei) comments
Pallab (Nokia) comments and shares the same concerns raised by Marco (Huawei)
Qian (Ericsson) shares also the view from Pallab (Nokia) and Marco (Huawei)
Kefeng (Qualcomm) replies the comments on PRSP vs URSP.
Jianning (Xiaomi) provides view
Kefeng (Qualcomm) replies Jianning (Xiaomi) comment
Qian (Ericsson) provides comments
Kefeng (Qualcomm) replies Qian (Ericsson) comments.
Zhenhua (vivo) provides r05 and r06.
Pallab (Nokia) comments.
Marco (huawei) comments on PRSP vs URSP.
Zhenhua (vivo) replies.
Jicheol (Samsung) comments on PRSP vs. URSP.
Zhenhua (vivo) comments on PRSP vs. URSP.
Kefeng (Qualcomm) replies Marco (Huawei) comments on PRSP vs. URSP.
Kefeng (Qualcomm) is not OK with r06.
Marco (Huawei) replies on PRSP vs. URSP.
==== Revisions Deadline ====
Jianning (Xiaomi) comment URSP vs PRSP
Kefeng (Qualcomm) replies Marco.
Pallab (Nokia) proposes to POSTPONE. We have competing proposals in 0727 and 0472, both cannot be agreed. We should first agree on PRSP vs URSP and then come back on this CR
Marco (Huawei) objects any revision of this CR including r00
==== Final Comments Deadline ====
Postponed
9.3.2 - - - Documents exceeding TU budget - - Docs:=1 -
9.3.2 S2-2300476 CR Approval 23.503 CR0834 (Rel-18, 'B'): Non-3GPP delay budget - 23.503 Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.4.1 - - - Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) - - Docs:=6 -
9.4.1 S2-2300961 CR Approval 23.700-58 CR0003 (Rel-18, 'C'): KI3 Conclusion update Huawei, HiSilicon Rel-18 Noted Stefano Faccin (Qualcomm) suggested to note the CR because not aligned to TR conclusions
Runze (Huawei) replies to Stefano Faccin (Qualcomm)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.4.1 S2-2300960 CR Approval 23.700-58 CR0002 (Rel-18, 'C'): Update solution#5 that DAA payload is carried by PC5-U message Huawei, HiSilicon Rel-18 Approved Guanzhou (InterDigital) thinks the change may not be necessary. Also wonders if 9.4.1 is in agenda? Propose to discuss the necessary clarification in the thread of S2-2301306.
Runze (Huawei) replies to Guanzhou (InterDigital).
Stefano (Qualcomm) suggests we proceed with the document as is.
LaeYoung (LGE) also supports the change in this CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.4.1 S2-2300404 CR Approval 23.700-58 CR0001 (Rel-18, 'F'): Resolution of RAN dependent aspects and ENs for KI#3 LG Electronics Rel-18 r01 agreed. Revised to S2-2301770. Stefano Faccin (Qualcomm) suggested to proceed with this CR to address the pending ENs.
Shabnam (Ericsson) provides comments that if we are referring to RAN then we need to add the references to the study as well as documented normative spec(s) that describe this mechanism so suggest revising the CR to include them.
LaeYoung (LGE) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.4.1 S2-2301770 CR Approval 23.700-58 CR0001R1 (Rel-18, 'F'): Resolution of RAN dependent aspects and ENs for KI#3 LG Electronics Rel-18 Revision of S2-2300404r01. Approved Agreed
9.4.1 S2-2300403 LS OUT Approval [DRAFT] LS on PC5 based Detect and Avoid mechanism LG Electronics Rel-18 Revised to S2-2301854. Stefano Faccin (Qualcomm) strongly support sending the LS with the current content.
Shabnam (Ericsson) provides comments regarding how the issue relates to the RAN soln? See details
LaeYoung (LGE) responds to Shabnam (Ericsson).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.4.1 S2-2301854 LS OUT Approval LS on PC5 based Detect and Avoid mechanism SA WG2 Rel-18 Revision of S2-2300403. Approved Approved
9.4.2 - - - Phase 2 for UAS, UAV and UAM (UAS_Ph2) - - Docs:=11 -
9.4.2 S2-2301306 CR Approval 23.256 CR0078 (Rel-18, 'B'): Architectural enhancements for support of Detect And Avoid Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2301771. LaeYoung (LGE) provides r01.
Stefano (Qualcomm) agrees with r01.
Shabnam (Ericsson) provides comments with minor updates in r02
LaeYoung (LGE) provides r03.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.4.2 S2-2301771 CR Approval 23.256 CR0078R1 (Rel-18, 'B'): Architectural enhancements for support of Detect And Avoid Qualcomm Incorporated Rel-18 Revision of S2-2301306r03. Approved Agreed
9.4.2 S2-2301305 CR Approval 23.256 CR0077 (Rel-18, 'B'): Architectural enhancements for support of Broadcast Remote ID Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2301772. LaeYoung (LGE) provides comments.
Shabnam (Ericsson) provides comments is the intention that we shall populate with more details in future meeting? If so, an EN would be beneficial, otherwise content is not very useful.
Stefano (Qualcomm) provides R01 to address both comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.4.2 S2-2301772 CR Approval 23.256 CR0077R1 (Rel-18, 'B'): Architectural enhancements for support of Broadcast Remote ID Qualcomm Incorporated Rel-18 Revision of S2-2301305r01. Approved Agreed
9.4.2 S2-2301303 CR Approval 23.256 CR0076 (Rel-18, 'B'): Architectural enhancements for Rel. 18 UAS features Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2301773. LaeYoung (LGE) provides r01.
Stefano (Qualcomm) provides r02.
LaeYoung (LGE) is fine with r02.
Pallab (Nokia) comments and provides r03.
Stefano (Qualcomm) provides r04.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.4.2 S2-2301773 CR Approval 23.256 CR0076R1 (Rel-18, 'B'): Architectural enhancements for Rel. 18 UAS features Qualcomm Incorporated Rel-18 Revision of S2-2301303r04. Approved Agreed
9.4.2 S2-2301312 CR Approval 23.256 CR0079 (Rel-18, 'B'): Ground based DAA for an area (Sol#7) Ericsson Rel-18 Confirm Specification Number - CR states 23.xxx! Revised to S2-2301855. Stefano Faccin (Qualcomm) has comments and questions for clarifications
LaeYoung (LGE) responds to Shabnam (Ericsson).
Shabnam (Ericsson) provides comments
LaeYoung (LGE) provides r01.
Guanzhou (InterDigital) provides r02.
Stefano (Qualcomm) provides r03.
Shabnam (Ericsson) provides comments that worked on previous baseline so hopefully I have included all relevant changes into r04 since our changes were quite extensive and would be too difficult to redo.
Stefano (Qualcomm) thanks Shabnam for adopting most changes and clarifying various points.
LaeYoung (LGE) comments on r04.
Shabnam (Ericsson) provides r05, cleaning up the text and consistency.
Stefano (Qualcomm) provides r06.
LaeYoung (LGE) provides r07.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that r07 is not acceptable since LTE has been in scope in the TR as well as in the normative work and LGE has given no reason to remove LTE. r06 is fine, thanks Stefano.
Stefano (Qualcomm) also prefers R06. Support of LTE is essential and was agreed since the beginning.
LaeYoung (LGE) thinks that r06 does not work as is.
Shabnam (Ericsson) now I understand and that would have been much better update then removal ?? we can ask the chair if we can do the update or even an EN., Thanks for clarifying.
LaeYoung (LGE) supports to add text or NOTE to clarify LTE PC5.
Shabnam (Ericsson) provides r08 after revision deadline, which is r07 with addition : Both NR and LTE PC5 are supported.
NOTE: LTE PC5 can be used to broadcast DAA messages by UAVs.
LaeYoung (LGE) supports r08 suggestion from Shabnam (Ericsson), so delta from r07 is modifying ' - NR PC5 is supported.' to '- Both NR and LTE PC5 are supported.' and adding 'NOTE: LTE PC5 can be used to broadcast DAA messages by UAVs.'.
Stefano (Qualcomm) also supports r08, even though it is after revision deadline, because the change is needed and there was a miscommunication (no disagreement).
==== Final Comments Deadline ====
Revised
9.4.2 S2-2301855 CR Approval 23.256 CR0079R1 (Rel-18, 'B'): Ground based DAA for an area (Sol#7) Ericsson Rel-18 Revision of S2-2301312. Approved Agreed
9.4.2 S2-2301060 CR Approval 23.256 CR0075 (Rel-18, 'B'): Support for direct C2 communication InterDigital Rel-18 Confirm Specification Number - CR states TS 23.256! CC#4: r04 agreed. Revised to S2-2301475. Stefano Faccin (Qualcomm) has questions/comments
Guanzhou (InterDigital) responds to Stefano(Qualcomm) and provides r01.
Stefano (Qualcomm) provides comments
Stefano (Qualcomm) provides r02
Shabnam (Ericsson) provides comments that there is contradicting procedure and prefers to move PC5 aspects in the new clause, see details
Stefano (Qualcomm) supports Shabnam
Guanzhou (InterDigital) provides r03.
Stefano (Qualcomm) has concerns about the additional changes and suggests we do not include the A2X Service Type derivation from CAA-level UAV ID at this meeting.
Guanzhou (InterDigital) responds to Stefano.
Stefano (Qualcomm) provides R04 making the dynamic A2X service type derived from UAV ID FFS.
Guanzhou (InterDigital) provides r05.
Stefano (Qualcomm) prefers R04 to give room for further discussion before we add normative text.
==== Revisions Deadline ====
Guanzhou (InterDigital) proposes to go with r05.
Shabnam (Ericsson) provides comments that we need a revision as per response so propose that a revision is provided to the CC#4 for approval, current versions are not acceptable.
Stefano (Qualcomm) can only accept R04.
==== Final Comments Deadline ====
Revised
9.4.2 S2-2301475 CR Approval 23.256 CR0075R1 (Rel-18, 'B'): Support for direct C2 communication InterDigital Rel-18 Revision of S2-2301060r04. Approved Agreed
9.4.2 S2-2300959 CR Approval 23.256 CR0074 (Rel-18, 'B'): Introducing new feature: MBS-based UAV remote ID broadcasting Huawei, HiSilicon Rel-18 Noted Stefano Faccin (Qualcomm) has comments and concerns.
Stefano Faccin (Qualcomm) indicates the paper as-is without addressing the comments cannot be accepted.
==== Revisions Deadline ====
Runze (Huawei) propose to postpone the paper.
==== Final Comments Deadline ====
Noted
9.5.1 - - - Study on Ranging based services and sidelink positioning (FS_Ranging_SL) - - Docs:=57 -
9.5.1 - - - Term - - Docs:=2 -
9.5.1 S2-2301136 P-CR Approval 23.700-86: Update to Terminology. Xiaomi Rel-18 Revision of S2-2209131. r01 agreed. Revised to S2-2301774. LiMeng (Huawei) asks for clarification.
Nicole (Xiaomi) provides new version.
Nicole (Xiaomi) provides new S2-2301136r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301774 P-CR Approval 23.700-86: Update to Terminology. Xiaomi Rel-18 Revision of S2-2301136r01. Approved Approved
9.5.1 - - - Solution of KI#2 - - Docs:=1 -
9.5.1 S2-2301280 P-CR Approval 23.700-86: TR 23.700-86: Sol#30 update for privacy issue. Intel Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.1 - - - Solution of KI#4 - - Docs:=1 -
9.5.1 S2-2300556 P-CR Approval 23.700-86: KI#4, Sol#3 Update: adding RSPP procedure. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.1 - - - Solution of KI#5 - - Docs:=2 -
9.5.1 S2-2300557 P-CR Approval 23.700-86: KI#5, Sol#20 Update: adding MT-LR procedure for target UE out of coverage. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2301775. Lars (Sony) comments.
LiMeng (Huawei) responds and provides r01.
Lars (Sony) comments on r01.
LiMeng (Huawei) provides r02.
Nicole (Xiaomi) comments on r02.
==== Revisions Deadline ====
Lars (Sony) is ok with r02.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301775 P-CR Approval 23.700-86: KI#5, Sol#20 Update: adding MT-LR procedure for target UE out of coverage. Huawei, HiSilicon Rel-18 Revision of S2-2300557r02. Approved Approved
9.5.1 - - - Solution of KI#6, KI#7 - - Docs:=4 -
9.5.1 S2-2301137 P-CR Approval 23.700-86: KI#6, Solution#25: Update to consider SL Positioning Server UE. Xiaomi Rel-18 Revision of S2-2209132. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.1 S2-2300555 P-CR Approval 23.700-86: KI#6: Update of Solution 9. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301776. Hong (Qualcomm) comments.
Lars (Sony) agrees with Hong's comments and provides further comments.
Xiaoyan Shi (Intel) comments.
LiMeng (Huawei) replies and provides r01.
Lars (Sony) comments on r01.
LiMeng (Huawei) responds and provides r02.
Lars (Sony) comments on r02.
Sherry (Xiaomi) provides r03.
Lars (Sony) comments on r03.
Lars (Sony) replies.
Sherry (Xiaomi) replies.
LiMeng (Huawei) provides r04.
==== Revisions Deadline ====
Lars (Sony) is ok with r04.
Sherry (Xiaomi) prefers r03 and can live with r04.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301776 P-CR Approval 23.700-86: KI#6: Update of Solution 9. Huawei, HiSilicon Rel-18 Revision of S2-2300555r04. Approved Approved
9.5.1 S2-2301277 P-CR Approval 23.700-86: Sol#7 update: Network assisted UE Sidelink Positioning capability. Intel Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.1 - - - Others Solutions - - Docs:=2 -
9.5.1 S2-2301138 P-CR Approval 23.700-86: KI#2&3&4&5&6&7, Solution#26: Update to clarify SL Positioning Server UE functionalities. Xiaomi Rel-18 Revision of S2-2209137. r03 agreed. Revised to S2-2301777. Lars (Sony) ask for clarification.
Lars (Sony) comments on r01.
Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) replies and provides r02.
Lars (Sony) will object to all version if the Issue I highlighted is not removed from the Terms.
Sherry (Xiaomi) replies and provides r03.
==== Revisions Deadline ====
Lars (Sony) is fine with r03.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301777 P-CR Approval 23.700-86: KI#2&3&4&5&6&7, Solution#26: Update to clarify SL Positioning Server UE functionalities. Xiaomi Rel-18 Revision of S2-2301138r03. Approved Approved
9.5.1 - - - Evaluation & Conclusion for KI#1&8 - - Docs:=3 -
9.5.1 S2-2301139 P-CR Approval 23.700-86: Updates to Evaluation&Conclusions for KI#1&8. Xiaomi Rel-18 r04 agreed. Revised to S2-2301778. Wen (vivo) asks a question regarding QoS parameters for RSPP transport.
LiMeng (Huawei) agrees with the comments from Wen (vivo).
Sherry (Xiaomi) provides r01.
Jungje(Interdigital) comments r01.
LaeYoung (LGE) comments on r01.
Sherry (Xiaomi) provides r02.
Sherry (Xiaomi) provides r03.
LiMeng (Huawei) provides r04.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r04.
Sherry (Xiaomi) is fine with r03 and r04.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301778 P-CR Approval 23.700-86: Updates to Evaluation&Conclusions for KI#1&8. Xiaomi Rel-18 Revision of S2-2301139r04. Approved Approved
9.5.1 S2-2300552 P-CR Approval 23.700-86: KI#1: Deletion of EN. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.1 - - - Evaluation & Conclusion for KI#2 - - Docs:=3 -
9.5.1 S2-2300708 P-CR Approval 23.700-86: TR 23.700-86: Updates to the conclusion for KI#2. Vivo Rel-18 Merged into S2-2301779 Hong (Qualcomm) replies to Wen.
Wen (vivo) replies to Hong.
Hong (Qualcomm) comments and propose use S2-2300549 as the basis for this KI conclusion.
LiMeng (Huawei) replies to Wen (vivo) and Hong (Qualcomm).
Sherry (Xiaomi) comments.
Wen (vivo) replies.
Wen (vivo) provides r01.
Wen (vivo) doesn't mind to merge.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300549 P-CR Approval 23.700-86: KI#2 Conclusion update on EN handling. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2301779, merging S2-2300708 Sherry (Xiaomi) comments.
LiMeng (Huawei) responds.
Sherry (Xiaomi) provides r01.
Wen (vivo) provides r02 for merging the 0708.
==== Revisions Deadline ====
Sherry (Xiaomi) replies to Wen.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301779 P-CR Approval 23.700-86: KI#2 Conclusion update on EN handling. Huawei, HiSilicon Rel-18 Revision of S2-2300549r02, merging S2-2300708. Approved Approved
9.5.1 - - - Evaluation & Conclusion for KI#3 - - Docs:=2 -
9.5.1 S2-2301279 P-CR Approval 23.700-86: TR 23.700-86: KI#3 Conclusion update. Intel Rel-18 r02 agreed. Revised to S2-2301780. Hong (Qualcomm) comments and provide r01.
Xiaoyan Shi (Intel) replies and comments on r01.
Hong (Qualcomm) replies to Xiaoyan.
LiMeng (Huawei) asks for clarification.
Walter Dees (Philips) provides comments.
Xiaoyan Shi (Intel) replies and provides r02.
Hong (Qualcomm) replies to LiMeng.
LiMeng (Huawei) replies to Hong (Qualcomm).
Sherry (Xiaomi) comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301780 P-CR Approval 23.700-86: TR 23.700-86: KI#3 Conclusion update. Intel Rel-18 Revision of S2-2301279r02. Approved Approved
9.5.1 - - - Evaluation & Conclusion for KI#4 - - Docs:=8 -
9.5.1 S2-2301233 P-CR Approval 23.700-86: Update on conclusion of KI#4. Interdigital Rel-18 r01 agreed. Revised to S2-2301781. Jung Je(Interdigital) responded Hong(Qualcomm)
Wen(vivo) comments.
Hong (Qualcomm) asks a question regarding the L3 Relay use case.
Lars (Sony) comment on the new wording proposal
Sherry (Xiaomi) requests a further clarification.
Xiaoyan Shi (Intel) asks question for clarification.
Jungje(Interdigital) responded to Xioyan(Intel) and Sherry(Xiaomi)
Jungje(Interdigital) provided r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301781 P-CR Approval 23.700-86: Update on conclusion of KI#4. Interdigital Rel-18 Revision of S2-2301233r01. Approved Approved
9.5.1 S2-2301288 P-CR Approval 23.700-86: Update to conclusions for KI#4: Control of Operations for Ranging/Sidelink positioning. Qualcomm Incorporated Rel-18 r09 agreed. Revised to S2-2301782, merging S2-2300312 Sherry (Xiaomi) comments.
Sherry (Xiaomi) provides r01.
Walter (Philips) provides comments and questions.
Sherry (Xiaomi) replies to Walter (Philips).
Hong (Qualcomm) replies to Walter and provides r02.
Wen (vivo)comments and provides r03.
Walter (Philips) comments and provides r04.
LiMeng (Huawei) provides r05.
LiMeng (Huawei) provides r06 based on r05 and merging 1312.
Richard (Ericsson) provides r06 based on r05 and merging 1312. Previous same comment was from Ericsson and not from Huawei.
Walter (Philips) provides r07.
Richard (Ericsson) provides r08
Hong (Qualcomm) provides r09
==== Revisions Deadline ====
Sherry (Xiaomi) is fine with r09
LiMeng (Huawei) can live with r09
Richard (Ericsson) is fine with r09
Wen (vivo) can live with r09.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301782 P-CR Approval 23.700-86: Update to conclusions for KI#4: Control of Operations for Ranging/Sidelink positioning. Qualcomm Incorporated Rel-18 Revision of S2-2301288r09, merging S2-2300312. Approved Approved
9.5.1 S2-2300710 P-CR Approval 23.700-86: TR 23.700-86: Updates to the conclusion for KI#4. Vivo Rel-18 Noted Hong (Qualcomm) comments and cannot accept conclusions on new solutions.
Wen (vivo) replies to Hong.
Sherry (Xiaomi) comments and requests for clarifications.
Wen (vivo) replies to Sherry.
LiMeng (Huawei) responds.
Sherry (Xiaomi) responds.
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) comments.
Wen (vivo) replies.
Walter (Philips) provides comments and questions.
Wen (vivo) replies to Walter and provides r01 which focuses on the Ranging initiation procedure.
==== Revisions Deadline ====
Hong (Qualcomm) objects to all revisions of the paper.
Hong (Qualcomm) replies to Wen.
Sherry (Xiaomi) proposes to note or merge this paper into S2-2301288.
==== Final Comments Deadline ====
Noted
9.5.1 S2-2300550 P-CR Approval 23.700-86: KI#4 Conclusion update. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301783. Sherry (Xiaomi) comments.
LiMeng (Huawei) responds.
Xiaoyan Shi (Intel) asks question for clarification.
LiMeng (Huawei) responds to Xiaoyan (Intel).
Walter (Philips) provides comments
LiMeng (Huawei) provides the update.
==== Revisions Deadline ====
LiMeng (Huawei) replies to Sherry (Xiaomi).
Sherry (Xiaomi) is fine with r01.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301783 P-CR Approval 23.700-86: KI#4 Conclusion update. Huawei, HiSilicon Rel-18 Revision of S2-2300550r01. Approved Approved
9.5.1 S2-2300312 P-CR Approval 23.700-86: KI#4 Update Conclusion: Update SL Positioning server UE functionalities in case of OoO scenario. Ericsson Rel-18 Merged into S2-2301782 Hong (Qualcomm) comments.
Sherry (Xiaomi) comments.
Richard (Ericsson) answers to Hong (Qualcomm).
LiMeng (Huawei) supports Richard (Ericsson) and RAN2 LS only touch the out-of-coverage scenario.
Guillaume (MediaTek Inc.) concurs with Sherry (Xiaomi) and Hong (Qualcomm)
Lars (Sony) Comments
Xiaoyan Shi (Intel) comments.
Wen (vivo) shares the same view with Lars (Sony).
Richard (Ericsson) answers to Sherry (Xiaomi) and provides more comments
Sherry(Xiaomi) replies.
Richard (Ericsson) provides more comment
Richard (Ericsson) provides r01
Xiaoyan Shi (Intel) comments on r01
Richard (Ericsson) answers to Xiaoyan Shi (Intel) and provides r02
Walter (Philips) provides comments
Richard (Ericsson) answers to Sherry (Xiaomi) and agrees to merge this into 1288
Richard (Ericsson) answers to Walter (Philips)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 - - - Evaluation & Conclusion for KI#5 - - Docs:=9 -
9.5.1 S2-2301234 P-CR Approval 23.700-86: Update on conclusion of KI#5. Interdigital Rel-18 Revised to S2-2301856, merging S2-2301140, S2-2301302, S2-2301278, S2-2300711, S2-2300823, S2-2300748 and S2-2300551 Jung Je(interdigital) provides updates r01.
Lars (Sony) provides r02.
David (Samsung) provides r03.
Hong (Qualcomm) comments on r03.
Lars (Sony) provides r04.
Jungje(Interdigital) responded to Lars
Jungje(Interdigital) comments on r04.
Xiaoyan Shi(Intel) comments on r04.
Jungje(Interdigital) responded on Xioyan(Intel)'s comment
Wen(vivo) comments r04 and provides r05
LiMeng (Huawei) comments and provides r06
Lars (Sony) r06 is in the right direction
Jungje(Interdigital) responded to Lars(Sony)
Lars (Sony) responds to Jungje(Interdigital)
Sherry (Xiaomi) provides r07 and r08.
Lars (Sony) ask a question on the candidate Located UEs.
Hong (Qualcomm) comments.
Jungje(Interdigital) comments.
Sherry (Xiaomi) comments.
David (Samsung) comments on r07, r08
Walter (Philips) provides r09
Jungje(Interdigital) provided r10 and responded to David(Samsung)'s comment.
Xiaoyan Shi (Intel) comments and provided r11.
Lars (Sony) r11 looks ok.
LiMeng (Huawei) provides r12.
Walter (Philips) provides r13.
Jungje(Interdigital) provides r14.
David (Samsung) supports r13.
==== Revisions Deadline ====
Jungje(Interdigital) propose to agree on r14.
Xiaoyan Shi (Intel) can live with both r14 and r13.
Lars (Sony) is ok with r14.
David (Samsung) agrees to both r14 and r13.
Sherry (Xiaomi) asks for clarification.
Jungje(Interdigital) responded to Sherry(Xiaomi)
Wen(vivo) is ok with r14.
Sherry (Xiaomi) provides r15 and propose to discuss it on CC#4.
Lars (Sony) is ok with the content of r15 but you need to show the changes on top of r14 in this comment field.
Jungje(Interdigital) comments on r15.
Sherry (Xiaomi) provides r16.
Lars (Sony) propose to approve r14 + changes below.

Add:
, for MO-LR or pending MT-LR (e.g. deferred MT-LR),
after AMF in the sentence
-If Target UE cannot establish NAS connection with AMF the following procedures can be used:

Remove:
For MO-LR
in
Option a),: For MO-LR:

Remove:
For MO-LR or pending MT-LR (e.g. deferred MT-LR)
in
Option b) For MO-LR or pending MT-LR (e.g. deferred MT-LR):
Jungje(Interdigital) comments Lar's change.
Sherry(Xiaomi) proposes to approve r14 + changes below.
Add:
, for MO-LR or pending MT-LR (e.g. deferred MT-LR),
after AMF in the sentence
-If Target UE cannot establish NAS connection with AMF the following procedures can be used:

Change :
For MO-LR:
to
Option a),:

Change:
For MO-LR or pending MT-LR (e.g. deferred MT-LR)
to
Option b):
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301856 P-CR Approval 23.700-86: Update on conclusion of KI#5. Interdigital, Philips International B.V. Rel-18 Revision of S2-2301234, merging S2-2301140, S2-2301302, S2-2301278, S2-2300711, S2-2300823, S2-2300748 and S2-2300551. Approved Approved
9.5.1 S2-2301140 P-CR Approval 23.700-86: Updates to Evaluation and Conclusions for KI#5. Xiaomi Rel-18 Merged into S2-2301856 Jung Je(interdigital) suggest to merge the paper into S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2301302 P-CR Approval 23.700-86: KI#5 Conclusion Updates. Philips International B.V. Rel-18 Merged into S2-2301856 Jung Je(interdigital) suggest to merge the paper into S2-2301234.
Walter (Philips) agrees to merge.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2301278 P-CR Approval 23.700-86: TR 23.700-86: KI#5 Conclusion update. Intel Rel-18 Merged into S2-2301856 Jungje(Interdigital) propose merge S2-2301278 into S2-2301234 and make a track for discussion.
Xiaoyan Shi(Intel) thanks for Jung Je's proposal, and Intel is fine to merge S2-2301278 into S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300711 P-CR Approval 23.700-86: TR 23.700-86: Updates to the conclusion for KI#5. Vivo Rel-18 Merged into S2-2301856 Jung Je(interdigital) suggest to merge the paper into S2-2301234.
Wen(vivo) is ok to merge the paper into S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300823 P-CR Approval 23.700-86: KI#5: Conclusion Update. Sony Rel-18 Merged into S2-2301856 Jung Je(interdigital) suggest to merge the paper into S2-2301234.
Lars (Sony) is ok to merge the paper into S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300748 P-CR Approval 23.700-86: KI#5: Conclusion Update . Samsung Rel-18 Merged into S2-2301856 Jung Je(interdigital) suggest to merge the paper into S2-2301234.
David (Samsung) is OK with the merger proposal into S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300551 P-CR Approval 23.700-86: KI#5 Conclusion update. Huawei, HiSilicon Rel-18 Merged into S2-2301856 Hong (Qualcomm) comments.
Jung Je(interdigital) suggest to merge the paper into S2-2301234.
LiMeng (Huawei) is fine with the merging proposal, and we can discuss the details under the email thread of S2-2301234.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 - - - Evaluation & Conclusion for KI#6 - - Docs:=5 -
9.5.1 S2-2301141 P-CR Approval 23.700-86: Updates to Evaluation and Conclusions for KI#6. Xiaomi Rel-18 Merged into S2-2301784 Lars (Sony) propose to merge this into S2-2300828.
Sherry (Xiaomi) confirms merging this paper into S2-2300828.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300828 P-CR Approval 23.700-86: KI#6: Conclusion Update. Sony Rel-18 r08 agreed. Revised to S2-2301784, merging S2-2301141, S2-2300712 and S2-2300553 LiMeng (Huawei) provides r01.
Wen (vivo) provides r02.
Lars (Sony) provides r03.
Sherry (Xiaomi) provides r04.
Wen (vivo) comments on r04.
Sherry (Xiaomi) replies to Wen.
Lars (Sony) provides r05.
Sherry (Xiaomi) provides r06.
Lars (Sony) comments on r06.
Jungje(Interdigital) responded to Lars(Sony) and submitted r07.
Lars (Sony) responds to Jungje(Interdigital).
Jungje(Interdigital) responds to Lars(Sony)
Lars (Sony) provides r08
Sherry (Xiaomi) comments.
==== Revisions Deadline ====
Jungje(Interdigital) is OK with r08
Sherry (Xiaomi) prefers r06 and can live with r08.
LiMeng (Huawei) is fine with r08.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301784 P-CR Approval 23.700-86: KI#6: Conclusion Update. Sony Rel-18 Revision of S2-2300828r08, merging S2-2301141, S2-2300712 and S2-2300553. Approved Approved
9.5.1 S2-2300712 P-CR Approval 23.700-86: TR 23.700-86: Updates to the conclusion for KI#6. Vivo Rel-18 Merged into S2-2301784 Lars (Sony) propose to merge this into S2-2300828.
Wen (vivo) is ok to merge this paper into S2-2300828.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300553 P-CR Approval 23.700-86: KI#6: Deletion of EN. Huawei, HiSilicon Rel-18 Merged into S2-2301784 Lars (Sony) propose to merge this into S2-2300828.
LiMeng (Huawei) agrees to merge this document into S2-2300828.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 - - - Evaluation & Conclusion for KI#7 - - Docs:=4 -
9.5.1 S2-2301236 P-CR Approval 23.700-86: Update on conclusion of KI#7. Interdigital Rel-18 Merged into S2-2301785 Hong (Qualcomm) comments.
David (Samsung) suggests to merge contents into S2-2300751.
Jungje(Interdigital) responded to David(Samsung)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 S2-2300751 P-CR Approval 23.700-86: KI#7: Conclusion Update . Samsung Rel-18 r07 agreed. Revised to S2-2301785, merging S2-2301236 and S2-2300554 Lars (Sony) comments.
Xiaoyan Shi (Intel) comments.
David (Samsung) provides r01.
Lars (Sony) fine with r01.
Jungje(Interdigital) provides r02
David (Samsung) provides r03.
Walter (Philips) provides r04.
Jungje(Interdigital) comments r04.
LiMeng (Huawei) provides r05 based on r03.
David (Samsung) provides r06.
Walter (Philips) provides r07.
==== Revisions Deadline ====
Jungje(Interdigital) is OK with r05,r06 and r07. And wish to cosign.
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301785 P-CR Approval 23.700-86: KI#7: Conclusion Update . Samsung, Interdigital Rel-18 Revision of S2-2300751r07, merging S2-2301236 and S2-2300554. Approved Approved
9.5.1 S2-2300554 P-CR Approval 23.700-86: KI#7 Deletion of EN. Huawei, HiSilicon Rel-18 Merged into S2-2301785 David (Samsung) suggests to merge contents into S2-2300751, provides comment.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.5.1 - - - LS - - Docs:=9 -
9.5.1 S2-2300047 LS In Action LS from RAN WG2: Reply LS on RAN dependency for Ranging & Sidelink Positioning RAN WG2 (R2-2213131) Rel-18 Response drafted in S2-2301267. Final response in S2-2301464. Replied to
9.5.1 S2-2301267 LS OUT Approval [DRAFT] Reply LS on Reply LS on RAN dependency for Ranging/Sidelink Positioning Xiaomi Rel-18 Response to S2-2300047. CC#4: r04 agreed. Revised to S2-2301464. Sherry (Xiaomi) provides r01.
==== Revisions Deadline ====
Runze (Huawei) replies to Sherry (Xiaomi) and provides r02.
David (Samsung) comments that there does not seem to be any r02 in the server.
LiMeng (Huawei) asks to withdraw the r01 of 1267 in the folder _Post_revisions_deadline.
Sherry (Xiaomi) provides r03 and propose to discuss this issue on CC#3.
Sherry (Xiaomi) objects to r02, and proposes to discuss this issue on CC#4.
Hong (Qualcomm) prefers r03 and objects r02.
Runze (Huawei) replies to Hong (Qualcomm), only accepts r02, and objects to r01, r03.
Hong (Qualcomm) replies to Runze.
Sherry (Xiaomi) replies to Runze.
Runze replies to Sherry (Xiaomi) and Hong (QC).
Sherry (Xiaomi) clarifies that r02 is not acceptable, because the potential answer to the question added by Runze may be interpreted in different ways. It does not help for SA2, instead, it will lead to more confusions
==== Final Comments Deadline ====
Sherry (Xiaomi) provided the papers for CC#4 discussion.
Revised
9.5.1 S2-2301464 LS OUT Approval Reply LS on Reply LS on RAN dependency for Ranging/Sidelink Positioning SA WG2 Rel-18 Revision of S2-2301267r04. Approved Approved
9.5.1 S2-2300048 LS In Action LS from RAN WG2: LS on SL positioning groupcast and broadcast RAN WG2 (R2-2213142) Rel-18 Response drafted in S2-2301292. Final response in S2-2301786 Replied to
9.5.1 S2-2301292 LS OUT Approval [DRAFT] Reply LS on SL positioning groupcast and broadcast Qualcomm Incorporated Rel-18 Response to S2-2300048. r02 agreed. Revised to S2-2301786. ==== Revisions Deadline ====
LiMeng (Huawei) requests a change on the last part.
Hong (Qualcomm) provides r01 (after revision deadline) and request to handle it in CC#3.
LiMeng (Huawei) is fine with the revision provided by Hong (Qualcomm).
Sherry (Xiaomi) provides r02 (after revision deadline).
LiMeng (Huawei) asks if we can put the r01/r02 at the folder for '_Post_revisions_deadline'.
Hong (Qualcomm) is fine with r02.
Sherry (Xiaomi) provides r02 to the _Post_revisions_deadline folder
==== Final Comments Deadline ====
Revised
9.5.1 S2-2301786 LS OUT Approval Reply LS on SL positioning groupcast and broadcast SA WG2 Rel-18 Revision of S2-2301292r02. Approved Approved
9.5.1 S2-2300012 LS In Action LS from RAN WG1: Reply LS on Terminology Alignment for Ranging/Sidelink Positioning RAN WG1 (R1-2210567) Revision of postponed S2-2210187 from S2#154. Postponed Postponed
9.5.1 S2-2300013 LS In Action LS from RAN WG2: Reply LS on Terminology Alignment for Ranging/Sidelink Positioning RAN WG2 (R2-2210982) Revision of postponed S2-2210192 from S2#154. Postponed Postponed
9.5.1 S2-2300041 LS In Action LS from RAN WG1: Reply LS on RAN dependency for Ranging/Sidelink Positioning RAN WG1 (R1-2212926) Rel-18 Postponed Postponed
9.5.1 - - - Discussion - - Docs:=2 -
9.5.1 S2-2301258 DISCUSSION Agreement FS_Ranging_SL Open Issue Company Position Survey. Xiaomi (Rapporteur) Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.5.1 S2-2300709 DISCUSSION Discussion Discussion on SLPP deployed. Vivo Rel-18 Noted Hong (Qualcomm) comments and propose to NOTE.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.5.2 - - - Ranging based services and sidelink positioning (Ranging_SL) - - Docs:=9 -
9.5.2 S2-2301143 P-CR Approval 23.586: Proposed texts for terminology and general concept . Xiaomi Rel-18 Approved Lars (Sony) provides r01
Sherry (Xiaomi) comments to r01
Lars (Sony) withdraw r01, ok to go with r00.
==== Revisions Deadline ====
Lars (Sony) suggest to go with r00.
Walter (Philips) objects to r01. Proposes to go with r00.
==== Final Comments Deadline ====
Approved
9.5.2 S2-2301142 P-CR Approval 23.586: Proposed texts for clause 1 of TS 23.586. Xiaomi Rel-18 r02 agreed. Revised to S2-2301787. Hong (Qualcomm) comments.
Sherry (Xiaomi) provides r01 and r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.5.2 S2-2301787 P-CR Approval 23.586: Proposed texts for clause 1 of TS 23.586. Xiaomi Rel-18 Revision of S2-2301142r02. Approved Approved
9.5.2 S2-2301281 P-CR Approval 23.586: TS 23.586: Architectural reference model . Intel Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.2 S2-2301144 P-CR Approval 23.586: Skeleton of Ranging_SL TS 23.586. Xiaomi Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.2 S2-2300713 P-CR Approval 23.586: TS 23.586: Functional entities. Vivo Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.5.2 S2-2300595 P-CR Approval 23.586: Subscription to Ranging/SL Positioning. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301788. Hong (Qualcomm) comments.
LiMeng (Huawei) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.5.2 S2-2301788 P-CR Approval 23.586: Subscription to Ranging/SL Positioning. Huawei, HiSilicon Rel-18 Revision of S2-2300595r01. Approved Approved
9.5.2 S2-2300596 P-CR Approval 23.586: Authorisation and provisioning for Ranging/Sidelink positioning. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.6.1 - - - Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) - - Docs:=4 -
9.6.1 S2-2300039 LS In Action LS from RAN WG1: Reply LS on Positioning Reference Units RAN WG1 (R1-2212715) Rel-18 Noted Runze (Huawei) propose to note the LS in. Noted
9.6.1 S2-2300059 LS In Action LS from RAN WG3: LS on Study on expanded and improved NR positioning RAN WG3 (R3-226889) Rel-18 Noted Runze (Huawei) propose to note the LS in. Noted
9.6.1 S2-2300040 LS In Action LS from RAN WG1: Reply LS on LPHAP information delivery to RAN RAN WG1 (R1-2212725) Rel-18 Noted Runze (Huawei) propose to note the LS in. Noted
9.6.1 S2-2300051 LS In Action LS from RAN WG2: Reply LS on LPHAP information delivery to RAN RAN WG2 (R2-2213327) Rel-18 Noted Runze (Huawei) propose to note the LS in. Noted
9.6.2 - - - 5GC LoCation Services Phase 3 (eLCS_Ph3) - - Docs:=50 -
9.6.2 - - - User Plane Positioning - - Docs:=12 -
9.6.2 S2-2300314 LS OUT Approval [DRAFT] LS on LPP message over a user plane connection between UE and LMF Ericsson Rel-18 Revised to S2-2301857, merging S2-2300634 Guanglei (Huawei) provides r01
==== Revisions Deadline ====
Leo (Deutsche Telekom) comments on r01
Guanglei (Huawei) thanks Leo reminding and propose go with r01+'remove RAN3 in clasue 2'
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301857 LS OUT Approval LS on LPP message and supplementary service event report over a user plane connection between UE and LMF SA WG2 Rel-18 Revision of S2-2300314, merging S2-2300634. Approved Approved
9.6.2 S2-2300634 LS OUT Approval [DRAFT] LS on LPP message transfer over a user plane connection to LMF Qualcomm Incorporated Rel-18 Merged into S2-2301857 Guanglei (Huawei) supports Yunjing(CATT)'s suggestion.
Yunjing (CATT) proposes to merge this draft LS into S2-2300314.
Scott (Inspur) echoes the appeal proposed by the previous delegates.
Stephen (Qualcomm) agrees to merge this draft LS into S2-2300314
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.6.2 S2-2300692 LS OUT Approval [DRAFT] LS on UE event reporting over a user plane connection to LCS client or AF Qualcomm Incorporated Rel-18 Revised to S2-2301789. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301789 LS OUT Approval LS on UE event reporting over a user plane connection to LCS client or AF SA WG2 Rel-18 Revision of S2-2300692. Approved Approved
9.6.2 S2-2301261 CR Approval 23.273 CR0291 (Rel-18, 'B'): LCS User Plane Function Nokia, Nokia Shanghai Bell Rel-18 Postponed Guanglei (Huawei) comments: it is not proper to regard LMF as an EAS and lots of concepts in this CR needs SA3/CT4/CT1 decision and justification.
Stephen (Qualcomm) also has comments on the correctness, clarity and completeness of this CR
Richard (Ericsson) provides comments and concerns
Cai Simon (Nokia) provide r01
Guanglei (Huawei) provides comments on r01
Richard (Ericsson) suggests to not add AF influence on traffic routing in any UP solutions since that is independent functionality
Cai Simon (Nokia) clarifies to Guanglei (Huawei)
Cai Simon (Nokia) provide r02
==== Revisions Deadline ====
Guanglei (Huawei) provides r03
Scott(Inspur) comments.
Cai Simon (Nokia) accepts Scott(Inspur) as one of the ways forward
Runze (Huawei) proposes to postpone the paper.
==== Final Comments Deadline ====
Postponed
9.6.2 S2-2300860 CR Approval 23.273 CR0279 (Rel-18, 'B'): Procedures of positioning over the user plane connection between UE and LMF Huawei, HiSilicon, Ericsson Rel-18 Postponed Cai Simon (Nokia) provides comments
Richard (Ericsson) answers to Simon (Nokia)
Guanglei (Huawei) further replies and provides r01.
Cai Simon (Nokia) comments on r01
Richard (Ericsson) answers to Simon (Nokia) and provides r02
Cai Simon (Nokia) comments r02
==== Revisions Deadline ====
Cai Simon (Nokia) comments the answer that 2300860 needs 2301260
Richard (Ericsson) disagrees that 2301260 is needed
Cai Simon (Nokia) proposed to postpone the paper
==== Final Comments Deadline ====
Postponed
9.6.2 S2-2301260 CR Approval 23.502 CR3863 (Rel-18, 'B'): Extra UE identity to AMF from GMLC to LMF Nokia, Nokia Shanghai Bell Rel-18 Postponed Cai Simon (Nokia) clarifies to Yunjing (CATT)
Yunjing (CATT) asks a question for clarification.
Richard (Ericsson) provides comment and questions
Stephen (Qualcomm) provides comments
Cai Simon (Nokia) provides r01 and clarifies
Guanglei (Huawei) provides comments: this CR has dependency with 1261
Yunjing (CATT) provides comment
Cai Simon (Nokia) clarifies to Yunjing (CATT) and Guanglei (Huawei)
Cai Simon (Nokia) clarifies to Richard (Ericsson)
==== Revisions Deadline ====
Runze (Huawei) proposes to postpone the paper.
Richard (Ericsson) agrees to postpone
==== Final Comments Deadline ====
Postponed
9.6.2 S2-2300794 CR Approval 23.502 CR3790 (Rel-18, 'F'): Update AMF service operation to support UE user plane connection to and LCS Client or AF CATT Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.6.2 S2-2300791 CR Approval 23.273 CR0270 (Rel-18, 'F'): Add Conditions for Positioning over User Plane Connection CATT Rel-18 Noted Guanglei (Huawei) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300793 CR Approval 23.273 CR0272 (Rel-18, 'F'): Update LMF and GMLC service operations to support cumulative event report CATT Rel-18 r01 agreed. Revised to S2-2301790. Stephen (Qualcomm) provides an r01 and some comments
Yunjing (CATT) accepts r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301790 CR Approval 23.273 CR0272R1 (Rel-18, 'F'): Update LMF and GMLC service operations to support cumulative event report CATT Rel-18 Revision of S2-2300793r01. Approved Agreed
9.6.2 - - - NPN deployment - - Docs:=3 -
9.6.2 S2-2301178 CR Approval 23.273 CR0290 (Rel-18, 'F'): Clarification on Location service in PNI-NPN ZTE Rel-18 Approved Richard (Ericsson) provides comments
Runze (Huawei) agrees with Richard (Ericsson) 's comments
Cai Simon (Nokia) asks a question
Richard (Ericsson) answers to Cai Simon (Nokia)
Cai Simon (Nokia) further comment
Runze (Huawei) shares the opinion.
Richard (Ericsson) answers to Cai Simon (Nokia) and Runze (Huawei)
Yunjing (CATT) provide comment.
Yunjing (CATT) replies to Richard (Ericsson)
Richard (Ericsson) answers to Yunjing (CATT)
Richard (Ericsson) agrees with Yunjing (CATT)
==== Revisions Deadline ====
Jinguo(ZTE) suggests to approve r00
Runze (Huawei) supports r00
==== Final Comments Deadline ====
Agreed
9.6.2 S2-2300955 CR Approval 23.273 CR0284 (Rel-18, 'C'): Positioning procedure update for PNI-NPN deployment Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2301791. Richard (Ericsson) provides comments
Runze (Huawei) replies to Richard (Ericsson).
Richard (Ericsson) answers to Runze (Huawei)
Leo (Deutsche Telekom) comments on original version
Runze (Huawei) replies to Leo (Deutsche Telekom) and Richard (Ericsson) and provides r01.
Yunjing (CATT) provides r02.
Runze (Huawei) replies to Yunjing (CATT).
Richard (Ericsson) provides comment on r01 and r02
Cai Simon (Nokia) asks a question about r02
Yunjing (CATT) replies to Cai Simon (Nokia).
Cai Simon (Nokia) comments further
Cai Simon (Nokia) replies to Richard (Ericsson)
Richard (Ericsson) answers to Cai Simon (Nokia)
==== Revisions Deadline ====
Cai Simon (Nokia) clarifies to Richard (Ericsson)
Runze (Huawei) supports both r01, r02.
Richard (Ericsson) supports r01 and r02.
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301791 CR Approval 23.273 CR0284R1 (Rel-18, 'C'): Positioning procedure update for PNI-NPN deployment Huawei, HiSilicon Rel-18 Revision of S2-2300955r02. Approved Agreed
9.6.2 - - - Local Area Restriction - - Docs:=6 -
9.6.2 S2-2301179 CR Approval 23.502 CR3851 (Rel-18, 'F'): Adding LMF ID in Namf_Location_ProvidePositioningInfo ZTE Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.6.2 S2-2300958 CR Approval 23.273 CR0287 (Rel-18, 'C'): Procedure update with additional LCS NF discovery and selection method Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301792. Jinguo(ZTE) comments
Runze (Huawei) replies to Jinguo(ZTE) and provides r01.
Jinguo(ZTE) replies to Runze (Huawei)
==== Revisions Deadline ====
Runze (Huawei) propose to approve r01.
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301792 CR Approval 23.273 CR0287R1 (Rel-18, 'C'): Procedure update with additional LCS NF discovery and selection method Huawei, HiSilicon Rel-18 Revision of S2-2300958r01. Approved Agreed
9.6.2 S2-2300795 CR Approval 23.273 CR0273 (Rel-18, 'F'): Update the local area GMLC and LMF selection CATT Rel-18 Merged into S2-2301793 Jinguo(ZTE) suggests to merge this CR into 1177 since the update are similar.
Yunjing (CATT) agrees to merge this CR into 1177.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.6.2 S2-2301177 CR Approval 23.273 CR0289 (Rel-18, 'F'): Clarification on LMF Discovery and Selection ZTE Rel-18 r04 agreed. Revised to S2-2301793, merging S2-2300795 Runze (Huawei) provides comments and proposes to merge this paper into S2-2300958.
Jinguo(ZTE) thinks 958 and 1177 are not overlapping and perfers to discuss separately.
Jinguo(ZTE) provides r01
Runze (Huawei) replies to Jinguo(ZTE).
Cai Simon (Nokia) provides r02
Jinguo(ZTE) provides r03
Richard (Ericsson) provides question
Jinguo(ZTE) replies to Richard (Ericsson) and provides r03
Cai Simon (Nokia) accepts r04 from Jinguo(ZTE)
Runze (Huawei) replies to Jinguo.
Jinguo(ZTE) replies to Runze (Huawei)
==== Revisions Deadline ====
Richard (Ericsson) can accept r04 but would prefer new LCS subscriber data type.
Runze (Huawei) shares the same view as Richard (Ericsson) that a new LCS data type is needed and accepts r04.
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301793 CR Approval 23.273 CR0289R1 (Rel-18, 'F'): Clarification on LMF Discovery and Selection ZTE Rel-18 Revision of S2-2301177r04, merging S2-2300795. Approved Agreed
9.6.2 - - - NWDAF - - Docs:=3 -
9.6.2 S2-2300957 CR Approval 23.273 CR0286 (Rel-18, 'B'): Introduce new feature: NWDAF assisted positioning Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301794. Amy (vivo) provides r01 based on the rapporteur's proposal
Stephen (Qualcomm) provides an r01 and some comments
Yunjing (CATT) provides an r02.
Amy (vivo) provides comments
Amy (vivo) please ignore this comment, I put it in a wrong agenda number
Cai Simon (Nokia) provides r03
Runze (Huawei) accepts r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301794 CR Approval 23.273 CR0286R1 (Rel-18, 'B'): Introduce new feature: NWDAF assisted positioning Huawei, HiSilicon Rel-18 Revision of S2-2300957r03. Approved Agreed
9.6.2 S2-2300463 CR Approval 23.273 CR0267 (Rel-18, 'F'): Removing PLMN Operator Class related to NWDAF Inspur Rel-18 CC#4: This was postponed. Yunjing (CATT) asks questions for clarification.
Amy (vivo) provides further analytics and comments
Scott (Inspur) provides response
Yunjing(CATT) replies.
Scott(Inspur) replies.
Yunjing (CATT) replies.
Amy (vivo) provides opinions
Amy (vivo) provides r01
Scott (Inspur) comments:
Scott(Inspur) provides r02
Amy (vivo) provides comments
Leo (Deutsche Telekom) provides comments
Scott(Inspur) replies to Amy (vivo)
Amy (vivo) provides an understanding about O&M LCS client.
Scott(Inspur) replies to Amy(Vivo).
==== Revisions Deadline ====
Runze (Huawei) propose the paper for CC#4.
==== Final Comments Deadline ====
Scott(Inspur) replies to Runze(Huawei).
Postponed
9.6.2 - - - GNSS - - Docs:=4 -
9.6.2 S2-2300801 LS OUT Approval [DRAFT] LS Out on Serving Area of GNSS Assistance Data CATT Rel-18 Noted Guanglei (Huawei) comments: this Ls depends on the outcome of 0798, technically RAN impacts are not needed.
Scott (Inspur) comments.
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to note this draft LS
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300798 CR Approval 23.273 CR0275 (Rel-18, 'F'): Add the usage of serving area of GNSS assistance data CATT Rel-18 Postponed Guanglei (Huawei) provides r01, RAN impacts are not needed.
Stephen (Qualcomm) comments that the CR does not seem needed
Scott (Inspur) comments.
Yunjing (CATT) replies to Guanglei (Huawei).
Guanglei (Huawei) further comments.
Yunjing (CATT) replies to Stephen (Qualcomm).
Yunjing (CATT) replies to Scott (Inspur).
Guanglei (Huawei) further clarifies why RAN impacts are not needed.
Yunjing (CATT) replies.
Scott (Inspur) replies.
Stephen (Qualcomm) replies to Yunjing (CATT)
Yunjing (CATT) provides r01 based on comment from Stephen (Qualcomm).
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone the CR
Runze (Huawei) agrees to postpone the CR
==== Final Comments Deadline ====
Postponed
9.6.2 S2-2300461 DISCUSSION Information Discussion on content and source of positioning assistance data . Inspur Rel-18 Noted Guanglei (Huawei) comments
Scott(Inspur) comments
Guanglei (Huawei) replies
Scott (Inspur) replies
Guanglei (Huawei) further replies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300462 CR Approval 23.273 CR0266 (Rel-18, 'B'): Content, source and procedure of positioning assistance data Inspur Rel-18 Noted Guanglei (Huawei) provides comments
Scott (Inspur) provides comments
Stephen (Qualcomm) provides comments and questions
Scott (Inspur) provides response inline.
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to note this CR
Scott (Inspur) replies to Stephen(Qualcomm)
==== Final Comments Deadline ====
Noted
9.6.2 - - - Unaware Positioning - - Docs:=6 -
9.6.2 S2-2300800 LS OUT Approval [DRAFT] LS Out on UE Unaware Positioning CATT Rel-18 Noted Stephen (Qualcomm) comments that the draft LS is incorrect and may not be needed
Scott (Inspur) comments that the draft LS.
Yunjing (CATT) provides r01 and replies
Scott (Inspur) comments r1 and object it.
Yunjing (CATT) replies to Scott (Inspur).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300797 CR Approval 23.502 CR3791 (Rel-18, 'F'): Update AMF service operation to support UE unaware indication CATT Rel-18 Approved Scott (Inspur) Comments
Chris (Vodafone) comments that signalling to the RAN seems to be missing.
Yunjing (CATT) replies.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.6.2 S2-2300799 CR Approval 23.273 CR0276 (Rel-18, 'B'): Support of User Unware Positioning CATT, OTD Rel-18 r01 agreed. Revised to S2-2301795. Guanglei (Huawei) ask questions
Stephen (Qualcomm) comments that the CR does not seem needed
Scott (Inspur) comments:
Yunjing (CATT) provides r01 and replies.
Chris (Vodafone) comments that signalling to the RAN seems to be missing.
Scott (Inspur) comments.
Stephen (Qualcomm) can agree the r01
Yunjing (CATT) replies to Chris (Vodafone).
Yunjing (CATT) replies to Scott (Inspur).
Chris (Vodafone) thanks Yunjing (CATT) for the reply and highlighting S2-2210996.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301795 CR Approval 23.273 CR0276R1 (Rel-18, 'B'): Support of User Unware Positioning CATT, OTD Rel-18 Revision of S2-2300799r01. Approved Agreed
9.6.2 S2-2300796 CR Approval 23.273 CR0274 (Rel-18, 'F'): Update LMF service operation to support UE unaware indication CATT Rel-18 r01 agreed. Revised to S2-2301796. Stephen (Qualcomm) provides an r01 and some comments
Scott (Inspur) provides some comments
Yunjing (CATT) replies to Scott (Inspur).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301796 CR Approval 23.273 CR0274R1 (Rel-18, 'F'): Update LMF service operation to support UE unaware indication CATT Rel-18 Revision of S2-2300796r01. Approved Agreed
9.6.2 - - - PRU - - Docs:=5 -
9.6.2 S2-2300636 CR Approval 23.273 CR0263R4 (Rel-18, 'B'): Support of PRUs Qualcomm Incorporated, CATT, Huawei, HiSilicon Rel-18 Revision of S2-2211232. Noted Stephen (Qualcomm) provides an r01 and some comments
Scott (Inspur) some comments
Stephen (Qualcomm) replies to Scott (Inspur)
Scott (Inspur) replies to Stephen(Qualcomm)
Guanglei (Huawei) replies to Scott (Inspur)
Scott (Inspur) replies to Guanglei (Huawei)
Cai Simon (Nokia) comments r01
Stephen (Qualcomm) provides comments and an r02
Guanglei (Huawei) provides r03
Cai Simon (Nokia) comments r03
Scott (Inspur) comments r03
Cai Simon (Nokia) provides r04
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r03 (and r02) but not the r04
Stephen (Qualcomm) provides an additional comment
Cai Simon (Nokia) accepts r04, rejects other revisions
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300862 CR Approval 23.273 CR0244R3 (Rel-18, 'B'): General description to support PRUs Huawei, HiSilicon, [CATT?], [Qualcomm?] Rel-18 Revision of S2-2211233. Confirm Sources! r07 agreed. Revised to S2-2301797. Stephen (Qualcomm) provides an r01 and some comments
Guanglei (Huawei) provides an r02 to cover UDM impacts
Guanglei (Huawei) provides r03
Cai Simon (Nokia) comments r03
Cai Simon (Nokia) comments r02
Guanglei (Huawei) provides r04
Cai Simon (Nokia) comments r04
Guanglei (Huawei) replies.
Cai Simon (Nokia) clarifies the logic redundancy and provides options
Guanglei (Huawei) provides r05, replies and ask questions.
Walter Dees (Philips) requests clarification
Guanglei (Huawei) replies to Walter Dees (Philips)
Yunjing (CATT) provide comment.
Walter Dees (Philips) responds to Guanglei
Guanglei (Huawei) further replies to Walter Dees (Philips)
Cai Simon (Nokia) further comments
Scott (Inspur) comments.
Guanglei (Huawei) provides r06 and replies to Simon and Scott.
Scott(Inspur) provides response.
Guanglei (Huawei) replies to Scott
Guanglei (Huawei) provides r07 to add an EN to reflect the view from Scott.
==== Revisions Deadline ====
Cai Simon (Nokia) propose to postpone the CR
Guanglei (Huawei) proposes to go with r07, as the general description has no controversial issues now
Yunjing (CATT) can accept r07.
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301797 CR Approval 23.273 CR0244R4 (Rel-18, 'B'): General description to support PRUs Huawei, HiSilicon, CATT, Qualcomm Rel-18 Revision of S2-2300862r07. Approved Agreed
9.6.2 S2-2300313 CR Approval 23.273 CR0265 (Rel-18, 'B'): PRU verification by AMF during PRU positioning Ericsson Rel-18 r02 agreed. Revised to S2-2301798. Stephen (Qualcomm) provides an r01 and some comments
Guanglei (Huawei) shares the view with Stephen.
Scott (Inspur) provides some comments
Richard (Ericsson) answers to Scott (Inspur)
Richard (Ericsson) answers to Stephen (Qualcomm) and Guanglei (Huawei)
Guanglei (Huawei) further comments.
Scott (Inspur) answers to Richard (Ericsson)
Stephen (Qualcomm) replies to Richard (Ericsson)
Scott (Inspur) answers to Rechard (Ericsson)
Stephen (Qualcomm) provides comments and an r02
Richard (Ericsson) is fine with r02 and provides comments
==== Revisions Deadline ====
Scott (Inspur) proposes to note the CR.
Richard (Ericsson) answers all questions of Scott (Inspur) which were the reason of noting
==== Final Comments Deadline ====
Scott(Inspur) replies to Richard(Ericsson) and insist on note.
Revised
9.6.2 S2-2301798 CR Approval 23.273 CR0265R1 (Rel-18, 'B'): PRU verification by AMF during PRU positioning Ericsson Rel-18 Revision of S2-2300313r02. Approved Agreed
9.6.2 - - - Service continuity - - Docs:=2 -
9.6.2 S2-2301265 CR Approval 23.273 CR0295 (Rel-18, 'B'): Location service continuity between EPS and 5GS (bi-direction) Nokia, Nokia Shanghai Bell Rel-18 Postponed Stephen (Qualcomm) provides an r01 and some comments
Guanglei (Huawei) provides an r02 which merged some general description from 0863.
Yunjing (CATT) provide comments.
Cai Simon (Nokia) accepts r01, not r02
Guanglei (Huawei) provides r03.
Cai Simon (Nokia) replies to Guanglei (Huawei)
Guanglei (Huawei) clarifies.
Cai Simon (Nokia) 2nd replies to Guanglei (Huawei)
==== Revisions Deadline ====
Cai Simon (Nokia) provides r04
Cai Simon (Nokia) provides r05
Stephen (Qualcomm) proposes to postpone the CR
==== Final Comments Deadline ====
Postponed
9.6.2 S2-2300863 CR Approval 23.273 CR0281 (Rel-18, 'B'): Location service continuity between EPS and 5GS (bi-direction) Huawei, HiSilicon Rel-18 Postponed Stephen (Qualcomm) comments that the CR does not correspond to the conclusions in TR 23.700-71 and the procedures will not work
Guanglei (Huawei) provides r01 which only discusses the continuity procedure for deferred MT-LR request
Stephen (Qualcomm) comments that the r01 procedures do not work
Guanglei (Huawei) replies
Stephen (Qualcomm) replies to Guanglei (Huawei)
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone the CR
==== Final Comments Deadline ====
Postponed
9.6.2 - - - Satellite Access - - Docs:=2 -
9.6.2 S2-2301090 CR Approval 23.501 CR4059 (Rel-18, 'B'): TAI determination for mobility restriction with satellite access Huawei, HiSilicon Rel-18 Noted Guanglei (Huawei) replies.
Yunjing (CATT) asks a question for clarification.
Stephen (Qualcomm) agrees with Yunjing (CATT) and believes the CR is not applicable to eLCS Ph3
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to note the CR based on the previous comments
==== Final Comments Deadline ====
Noted
9.6.2 S2-2300861 CR Approval 23.273 CR0280 (Rel-18, 'B'): TAI determination for mobility restriction with satellite access Huawei, HiSilicon Rel-18 Confirm Specification Number - CR states 23.501! WITHDRAWN Guanglei (Huawei) confirms 0861 can be marked as withdraw, 1090 has the correct TS number.
Yunjing (CATT) thinks this CR is the same as S2-2301090.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Withdrawn
9.6.2 - - - Triggered Location - - Docs:=5 -
9.6.2 S2-2300792 CR Approval 23.273 CR0271 (Rel-18, 'B'): Enhance the Triggered Location for UE power saving purpose CATT Rel-18 r01 agreed. Revised to S2-2301799. Stephen (Qualcomm) provides some comments
Amy (vivo) provides suggestions
Scott (Inspur) provides some comments
Amy (vivo) please ignore this comment, I put it in a wrong agenda number.
Cai Simon (Nokia) comments
Yunjing(CATT) provides r01 and replies.
Amy (vivo) provides enhancement based on suggestion 2
Yunjing (CATT) replies to Amy (vivo).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301799 CR Approval 23.273 CR0271R1 (Rel-18, 'B'): Enhance the Triggered Location for UE power saving purpose CATT Rel-18 Revision of S2-2300792r01. Approved Agreed
9.6.2 S2-2300956 CR Approval 23.273 CR0285 (Rel-18, 'C'): Clarification on additional check for location events Huawei, HiSilicon Rel-18 Approved Scott (Inspur) comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.6.2 S2-2300697 CR Approval 23.273 CR0269 (Rel-18, 'B'): Enable additional check in target area in deferred area event Vivo Rel-18 r02 agreed. Revised to S2-2301800. Yunjing (CATT) provides r01.
Scott (Inspur) comments.
Amy (vivo) replies to Yunjing and Jiangyong
Scott (Inspur) replies to Amy
Amy (vivo) provides r02 and replies to Yunjing and Scott
Amy (vivo) replies to Scott
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.6.2 S2-2301800 CR Approval 23.273 CR0269R1 (Rel-18, 'B'): Enable additional check in target area in deferred area event Vivo Rel-18 Revision of S2-2300697r02. Approved Agreed
9.6.2 - - - LPHAP - - Docs:=2 -
9.6.2 S2-2300954 CR Approval 23.273 CR0283 (Rel-18, 'B'): Introduce new feature: support of low power and high accuracy positioning Huawei, HiSilicon Rel-18 CC#4: r02 + editor's note agreed. Revised to S2-2301476. Chunhui (Xiaomi) suggests to take the UE configuration/preference into account and provides r01.
Stephen (Qualcomm) disagrees the r01 and provides an r02
Chunhui (Xiaomi) replies the comments from Stephen(QC).
Scott (Inspur) comments.
==== Revisions Deadline ====
Chunhui (Xiaomi) objects to r02 since it does not consider the UE configuration/preference.
Stephen (Qualcomm) can agree the r02 but not r01 or r00
Runze (Huawei) propose the paper for CC#4.
==== Final Comments Deadline ====
Chunhui (Xiaomi) proposes a EN or to postpone this CR to next meeting.
Revised
9.6.2 S2-2301476 CR Approval 23.273 CR0283R1 (Rel-18, 'B'): Introduce new feature: support of low power and high accuracy positioning Huawei, HiSilicon Rel-18 Revision of S2-2300954r02 + editor's note. Approved Agreed
9.7.1 - - - Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) - - Docs:=0 -
9.7.2 - - - Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) - - Docs:=79 -
9.7.2 - - - LS in and out - - Docs:=4 -
9.7.2 S2-2300052 LS In Action LS from RAN WG2: LS on Differentiation of Layer2 ID and Coexistence of U2N/U2U RAN WG2 (R2-2213328) Rel-18 Responses drafted in S2-2300504, S2-2300605. Postponed Deng Qiang (CATT) asks to postponed this LS in. Postponed
9.7.2 S2-2300504 LS OUT Approval [DRAFT] Reply LS on Differentiation of Layer2 ID and Coexistence of U2N/U2U CATT Rel-18 Response to S2-2300052. Postponed Fei (OPPO) comments.
Steve (Huawei) comments.
Fei (OPPO) replied.
Fei (OPPO) provides r01.
Hannu (Nokia) does not oppose r01 from Fei but asks for clarification of Q3b and provides a possible clarification in r02.
Fei (OPPO) replied to Hannu and provides r03.
LaeYoung (LGE) asks a Q.
Fei (OPPO) replied to LaeYoung
LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) provided replies to LaeYoung (LGE)
Fei (OPPO) replied to LaeYoung (LGE)..
LaeYoung (LGE) responds to Fei (OPPO).
==== Revisions Deadline ====
LaeYoung (LGE) proposes to POSTPONE this LS.
Steve (Huawei) Postponing seems sensible
Deng Qiang (CATT) is fine to be Postponed.
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2300605 LS OUT Approval [DRAFT] Reply LS on Differentiation of Layer2 ID and Coexistence of U2N/U2U OPPO Rel-18 Response to S2-2300052. Noted Deng Qiang (CATT) proposed to discuss the reply LS in S2-2300504 thread.
Fei (OPPO) responds.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.7.2 S2-2300056 LS In Action LS from RAN WG3: Reply LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN RAN WG3 (R3-226822) Rel-18 Noted LaeYoung (LGE) proposes to POSTPONE this incoming LS.
Fei (OPPO) proposed to note this incoming reply LS.
LaeYoung (LGE) is fine to NOTE this LS.
Noted
9.7.2 - - - KI#1: UE-to-UE Relay - - Docs:=30 -
9.7.2 S2-2300250 CR Approval 23.304 CR0160 (Rel-18, 'B'): Update to UE-to-UE Relay Model A Discovery Ericsson Rel-18 Noted Hao (ZTE) fixes the contribution number S2-2300250, not S2-2300050.
Zhang (Ericsson) response to Jianning (Xiaomi)
Steve (Huawei) comments.
Zhang (Ericsson) response to Steve(Huawei)
Hong (Qualcomm) comments.
Jung Je (Interdigital) comments
Zhang (Ericsson) provides response
Jungje (Interdigital) comments
Zhang (Ericsson) response to Jung Je(Interdigital)
Zhang (Ericsson) response to Hong and Steve
Hannu (Nokia) is not convinced that we need all this new text in the CR.
Jungje(Interdigital) responded to Zhang(Ericsson)
Zhang (Ericsson) response to Hannu (Nokia)
Zhang (Ericsson) response to Steve (Huawei)
==== Revisions Deadline ====
Steve (Huawei) should be noted?
Hannu (Nokia) supports the proposal to note.
==== Final Comments Deadline ====
Noted
9.7.2 S2-2300251 CR Approval 23.304 CR0161 (Rel-18, 'B'): 5G ProSe Layer-3 UE-to-UE Relay Communication for Non-IP Traffic Ericsson Rel-18 r01 agreed. Revised to S2-2301562. Yali (OPPO) comments.
Steve (Huawei) comments.
Zhang (Ericsson) provides r01
==== Revisions Deadline ====
Hong (Qualcomm) comments on r01.
Zhang (Ericsson) response to Hong (Qualcomm)
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301562 CR Approval 23.304 CR0161R1 (Rel-18, 'B'): 5G ProSe Layer-3 UE-to-UE Relay Communication for Non-IP Traffic Ericsson Rel-18 Revision of S2-2300251r01. Approved Agreed
9.7.2 S2-2300385 DISCUSSION Discussion Discussion on RSC for UE-to-UE relaying. LG Electronics Rel-18 Noted Steve (Huawei) comments.
LaeYoung (LGE) proposes to NOTE this DP.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.7.2 S2-2300386 CR Approval 23.304 CR0170 (Rel-18, 'B'): RSC for UE-to-UE relaying LG Electronics Rel-18 r02 agreed. Revised to S2-2301563. LaeYoung (LGE) responds to Zhang (Ericsson).
Zhang (Ericsson) provides comments and prefer to use S2-2300387
Fei proposed another alternative.
Jianning (Xiaomi) agree with Fei (OPPO) to update 0386 to capture the content of 0387
LaeYoung (LGE) replies to Fei (OPPO) and Jianning (Xiaomi).
Steve (Huawei) comments.
LaeYoung (LGE) provides r01.
Hong (Qualcomm) comments on r01.
LaeYoung (LGE) provides r02.
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r02
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301563 CR Approval 23.304 CR0170R1 (Rel-18, 'B'): RSC for UE-to-UE relaying LG Electronics Rel-18 Revision of S2-2300386r02. Approved Agreed
9.7.2 S2-2300494 CR Approval 23.304 CR0172 (Rel-18, 'B'): Layer-2 link management for 5G ProSe UE-to-UE Relay OPPO Rel-18 Postponed. CC#4: r02 agreed. Revised to S2-2301479. Yali(OPPO) replies to Zhang (Ericsson)
Zhang (Ericsson) provides comments
Steve (Huawei) makes an observation
Jungje(Interdigital) comments
Yali(OPPO) provides r01
Steve (Huawei) comments, provides r02.
Yali(OPPO) is fine with r02, and replies to Zhang (Ericsson)
==== Revisions Deadline ====
Zhang (Ericsson) is fine with r02
Jungje(Interdigital) propose to accept r02 with deletion of the parameters 'Destination Layer-2 ID of target 5G ProSe End UE' under subclause 6.4.3.7.x(
Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay Communication with integrated Discovery)
Yali(OPPO) replies to Jungje(Interdigital) , the parameter cannot be removed, it aligns with the TR conclusion and the TS text we agreed in the last meeting.
Jungje(Interdigital) responded to Yali(OPPO)
Yali(OPPO) replies to Jungje(Interdigital).
Jungje(Interdigital) response to Yali(OPPO)
Jungje(Interdigital) can only accept r02 with deletion of the parameter 'Destination Layer-2 ID of target 5G ProSe End UE' under subclause 6.4.3.7.x(
Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay Communication with integrated Discovery)
Yali(OPPO) replies to Jungje(Interdigital), can only accept r02.
Jungje(Interdigital) propose to accept r02 with deletion of the parameter 'Destination Layer-2 ID of target 5G ProSe End UE' under subclause 6.4.3.7.x(
Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay Communication with integrated Discovery) and handle at CC#4.
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301479 CR Approval 23.304 CR0172R1 (Rel-18, 'B'): Layer-2 link management for 5G ProSe UE-to-UE Relay OPPO Rel-18 Revision of S2-2300494r02. Approved Agreed
9.7.2 S2-2300495 CR Approval 23.304 CR0173 (Rel-18, 'C'): Update for 5G ProSe UE-to-UE Relay Communication with integrated Discovery OPPO Rel-18 r02 agreed. Revised to S2-2301564. Yali(OPPO) clarifies and suggests not to merge
Zhang (Ericsson) suggest to merge the paper into S2-2301237
Steve (Huawei) comments.
Zhang (Ericsson) response to Yali (OPPO)
Yali(OPPO) provides r01
Hannu (Nokia) provides r02 to remove redundancy on integrated discovery requirements.
Yali(OPPO) is fine with r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301564 CR Approval 23.304 CR0173R1 (Rel-18, 'C'): Update for 5G ProSe UE-to-UE Relay Communication with integrated Discovery OPPO Rel-18 Revision of S2-2300495r02. Approved Agreed
9.7.2 S2-2300500 CR Approval 23.304 CR0174 (Rel-18, 'B'): Identifiers for 5G ProSe UE-to-UE Relay Discovery CATT Rel-18 r01 agreed. Revised to S2-2301565, merging S2-2301130 Fei (OPPO) comments.
Deng Qiang (CATT) provides r01.
Steve (Huawei) makes an observation
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301565 CR Approval 23.304 CR0174R1 (Rel-18, 'B'): Identifiers for 5G ProSe UE-to-UE Relay Discovery CATT Rel-18 Revision of S2-2300500r01, merging S2-2301130. Approved Agreed
9.7.2 S2-2300501 CR Approval 23.304 CR0175 (Rel-18, 'B'): Identifiers for Discovery integrated into PC5 unicast link establishment CATT Rel-18 CC#4: r02 agreed. Revised to S2-2301480. Fei (OPPO) comments and provides r01.
Steve (Huawei) comments in titles
Jungje(Interdigital) comments.
Fei (OPPO) responds to Jung Je.
Fei (OPPO) provides response.
Yali (OPPO) provides r02
==== Revisions Deadline ====
Fei (OPPO) can only accept r02.
JUngje(Interdigital) comments on r01 and propose to agree on r01 with removing the second paragraph in the change.
Jungje(Interdigital) responded to Fei(OPPO) and reconsider the position.
Fei (OPPO) Replied to Jung Je.
Jungje(Interdigital) responded to Fei(Oppo).
Fei (OPPO) Provides responses.
Jungje(Interdigital) can only accept r02 with deletion of second paragraph which starts with '5G ProSe UE-to-UE Relay may send a unicast Direct Communication Request message...'.
Jungje(Interdigital) propose to accept r02 with deletion of second paragraph which starts with '5G ProSe UE-to-UE Relay may send a unicast Direct Communication Request message...' and handled at CC#4.
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301480 CR Approval 23.304 CR0175R1 (Rel-18, 'B'): Identifiers for Discovery integrated into PC5 unicast link establishment CATT Rel-18 Revision of S2-2300501r02. Approved Agreed
9.7.2 S2-2300703 CR Approval 23.304 CR0186 (Rel-18, 'B'): Updates to U2U relay link management Vivo Rel-18 Approved Steve (Huawei) has a comment or 2.
Jungje(Interdigital) comments
Wen (vivo) replies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.7.2 S2-2300761 CR Approval 23.304 CR0190 (Rel-18, 'B'): Clarification on Messages Used in 5G ProSe Discovery Integrated into PC5 Unicast Link Establishment Procedure ZTE Rel-18 Postponed To be merged into S2-2300494 (Postponed) Yali (OPPO) suggests to merge this paper into S2-2300494.
Hao (ZTE) is OK to merge this paper into S2-2300494.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2300985 CR Approval 23.304 CR0195 (Rel-18, 'B'): Protocol Stacks for 5G ProSe UE-to-UE Relay Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301566. Zhang (Ericsson) provides comments
Steve (Huawei) provides r01
Hannu (Nokia) is concerned of SA2 specifying RAN2 protocol stacks for L2 relaying in both r00 and r01.
Steve (Huawei) comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301566 CR Approval 23.304 CR0195R1 (Rel-18, 'B'): Protocol Stacks for 5G ProSe UE-to-UE Relay Huawei, HiSilicon Rel-18 Revision of S2-2300985r01. Approved Agreed
9.7.2 S2-2300993 CR Approval 23.304 CR0201 (Rel-18, 'B'): Update on UE-to-UE Relay reselection Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301567. Jung Je (Interdigital) comments.
Jungje(Interdigital) provides r01
Steve (Huawei) comments, provides r02
Jungje(Interdigital) comments on r02.
Jungje(interdigital) provides r03.
Steve (Huawei) provides r04
==== Revisions Deadline ====
Jungje(Interdigital) is OK with r04.
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301567 CR Approval 23.304 CR0201R1 (Rel-18, 'B'): Update on UE-to-UE Relay reselection Huawei, HiSilicon Rel-18 Revision of S2-2300993r04. Approved Agreed
9.7.2 S2-2301129 CR Approval 23.304 CR0202 (Rel-18, 'B'): Support of Emergency service over UE-to-Network Relay Xiaomi Rel-18 r04 agreed. Revised to S2-2301568. Jianning (Xiaomi) provide r01 to correct the title
Steve (Huawei) comments.
Zhang (Ericsson) clarifies the relay indication
Jianning (Xiaomi) provides view and r02
Yali (OPPO) comments
Zhang (Ericsson) provides comments
Jianning (Xiaomi) provides r03
Steve (Huawei) provides r04
==== Revisions Deadline ====
Jianning (Xiaomi) is ok with r04
Zhang (Ericsson) is OK with r03 and r04
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301568 CR Approval 23.304 CR0202R1 (Rel-18, 'B'): Support of UE-to-UE Relay operation during ProSe Direct Discovery Xiaomi Rel-18 Revision of S2-2301129r04. Approved Agreed
9.7.2 S2-2301130 CR Approval 23.304 CR0203 (Rel-18, 'B'): 5.8.4.2 Common Identifiers for 5G ProSe UE-to-UE Relay Xiaomi Rel-18 Merged into S2-2301565 Steve (Huawei) comments on merging with 0500?
Jianning (Xiaomi) is ok to merge into S2-2300500
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.7.2 S2-2301237 CR Approval 23.304 CR0206 (Rel-18, 'C'): Update on UE-to-UE Relay with Integrated Discovery Interdigital Rel-18 Postponed Yali(OPPO) suggests to postpone this CR.
Zhang (Ericsson) provides comments
Jung Je (Interdigital) responded to Zhang
Jung Je(Interdigital) responded to Yali(OPPO)'s comment.
Jungje (Interdigital) provided r01
Steve (Huawei) is really uncomfortable
Yali(OPPO) still suggests to postpone this CR.
==== Revisions Deadline ====
Steve (Huawei) objects to all revisions. Could live with postpone.
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2301240 CR Approval 23.304 CR0208 (Rel-18, 'B'): Link Management over PC5 reference point for 5G ProSe UE-to-UE Relay Interdigital Rel-18 CC#4: r02 + changes agreed. Revised to S2-2301481. Zhang (Ericsson) provides comments
Jianning (Xiaomi) provide comment
Steve (Huawei) comments.
Jung Je(Interdigital) responded to Steven(Huawei), Zhang(Ericsson), and Jianning(Xiaomi).
And provided r01
Jung Je(Interdigital) provides r02
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r02
Yali(OPPO) comments and proposes to Note.
Jungje(Interdigital) proposes to go with r02 + change 'with an additional Indication sent to peer End UEs by the Layer -3 UE-to-UE Relay' to 'Layer-3 UE-to-UE Relay may send link modification update to the peer End UEs to notify it' and proposes this for CC#4
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301481 CR Approval 23.304 CR0208R1 (Rel-18, 'B'): Link Management over PC5 reference point for 5G ProSe UE-to-UE Relay Interdigital Rel-18 Revision of S2-2301240r02 + changes. Approved Agreed
9.7.2 S2-2301293 CR Approval 23.304 CR0212 (Rel-18, 'B'): IP address allocataion for communication with a 5G ProSe Layer-3 UE-to-UE Relay Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2301569. Zhang (Ericsson) provides comments
Hong (Qualcomm) provides r01.
Hong (Qualcomm) replies to Zhang.
Zhang (Ericsson) response to Hong
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301569 CR Approval 23.304 CR0212R1 (Rel-18, 'B'): IP address allocataion for communication with a 5G ProSe Layer-3 UE-to-UE Relay Qualcomm Incorporated Rel-18 Revision of S2-2301293r01. Approved Agreed
9.7.2 S2-2301320 CR Approval 23.304 CR0215 (Rel-18, 'F'): Clarification of out-of-coverage operation for U2U Relays Philips International B.V. Rel-18 r01 agreed. Revised to S2-2301570. Hong (Qualcomm) comments and suggest aligning the wording with related Rel-17 discussion.
LaeYoung (LGE) comments that ME box instead of CN box should be ticked.
Walter (Philips) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301570 CR Approval 23.304 CR0215R1 (Rel-18, 'F'): Clarification of out-of-coverage operation for U2U Relays Philips International B.V. Rel-18 Revision of S2-2301320r01. Approved Agreed
9.7.2 - - - KI#2: Path switching btw two indirect paths - - Docs:=2 -
9.7.2 S2-2300600 CR Approval 23.304 CR0180 (Rel-18, 'C'): Update on path switching between different U2N relays OPPO Rel-18 r04 agreed. Revised to S2-2301571. Steve (Huawei) asks a question
Fei (OPPO) responds and provides r01.
Steve (Huawei) provides r02
Judy (Ericsson) comments
Fei (OPPO) replied and provided r04 (please discard r03).
==== Revisions Deadline ====
Steve (Huawei) is ok with r04
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301571 CR Approval 23.304 CR0180R1 (Rel-18, 'C'): Update on path switching between different U2N relays OPPO Rel-18 Revision of S2-2300600r04. Approved Agreed
9.7.2 - - - KI#3: Direct path switching btw PC5 and Uu - - Docs:=5 -
9.7.2 S2-2300384 CR Approval 23.304 CR0169 (Rel-18, 'B'): Path switching between PC5 path and Uu path LG Electronics, MediaTek Inc. Rel-18 r07 agreed. Revised to S2-2301572, merging S2-2300707 and S2-2300763 Wen (vivo) tries to provides r01 for considering merging with 0707.
Steve (Huawei) provides r02
Jungje(Interdigital) provides r03
Hong (Qualcomm) provides r04.
Jungje(Interdigital) comments r04
Hao (ZTE) comments: this paper depends on the discussion result under thread S2-2300762(DP).
LaeYoung (LGE) provides r05.
Hong (Qualcomm) comments.
Steve (Huawei) provides r06
Jungje(Interdigital) provides r07
LaeYoung (LGE) provides r08.
Jungje(Interdigital) comments r08
==== Revisions Deadline ====
Jungje(Interdigital) propose to agree on r07
Wen(vivo) prefers r07, compared with r08.
LaeYoung (LGE) prefers r08, but can live with r07.
Jungje(Interdigital) accept r07 and objects to others.
Steve (Huawei) is ok with r06, r07 or r08, happy to cosign.
LaeYoung (LGE) thanks to Steve (Huawei) for co-sign.
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301572 CR Approval 23.304 CR0169R1 (Rel-18, 'B'): Path switching between PC5 path and Uu path LG Electronics, MediaTek Inc., Huawei, HiSilicon Rel-18 Revision of S2-2300384r07, merging S2-2300707 and S2-2300763. Approved Agreed
9.7.2 S2-2300707 CR Approval 23.304 CR0189 (Rel-18, 'B'): Negotiated path switching between PC5 and Uu Vivo Rel-18 Merged into S2-2301572 Steve (Huawei) Is this merged to 384?
LaeYoung (LGE) also proposes to merge this CR to 00384.
Wen (vivo) is ok to merge this CR to 00384.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.7.2 S2-2300762 DISCUSSION Agreement Discussion on Unified Path Permission Policy for Path Selection and Switching. ZTE Rel-18 Noted Judy (Ericsson) proposes to use thread to discuss how to handle the policy for path switching in 384, 707 and 763, and provides comments
Hao (ZTE) comments.
Fei (OPPO) commets
Wen (vivo) comments
Mehrdad (MediaTek Inc.) comments
Judy (Ericsson) asks question
LaeYoung (LGE) provides comment.
Wen (vivo) provides comment.
Mehrdad (MediaTek Inc.) can not agree with unified Path Permission Policy.
Steve (Huawei) comments.
Mehrdad (MediaTek Inc.) replies to Huawei.
Hong (Qualcomm) comments.
Mehrdad (MediaTek Inc.) replies to Qualcomm.
Fei (OPPO) provides comments.
Mehrdad (MediaTek Inc.) replies to OPPO, ZTE.
Steve (Huawei) on joined or separate policies - separate.
Judy (Ericsson) comments
Steve (Huawei) comments, is fine with the way forward in 384.
Judy (Ericsson) responds to Steve (Huawei)
LaeYoung (LGE) comments.
Mehrdad (MediaTek Inc.) replies to Qualcomm, Ericsson, LGE.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.7.2 S2-2300763 CR Approval 23.304 CR0191 (Rel-18, 'B'): Unified Path Permission Policy for Path Selection and Switching ZTE Rel-18 Merged into S2-2301572 Judy (Ericsson) comments that this CR depends on the discussion in 762 thread
LaeYoung (LGE) proposes to merge this CR to 00384.
Hao (ZTE) is OK to mark this paper as Merged into S2-2300384 or as Noted.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.7.2 - - - KI#4: Path switching btw direct path and indirect path for L2 U2N Relay - - Docs:=2 -
9.7.2 S2-2300503 CR Approval 23.304 CR0177 (Rel-18, 'B'): Path switching between direct and indirect path for Layer-2 UE-to-Network Relay CATT Rel-18 r05 agreed. Revised to S2-2301573. Fei (OPPO) comments.
Deng Qiang (CATT) provides r01.
Judy (Ericsson) comments and provides r02
Steve (Huawei) comments.
Deng Qiang (CATT) provides r03.
Fei (OPPO) comments on r03.
Steve (Huawei) predicts the future...
Fei (OPPO) replied to Steve.
Fei (OPPO) replies and provides r04.
Steve (Huawei) comments, could live with an EN.
Fei (OPPO) comments and provides r05 with EN.
Steve (Huawei) is ok with r05
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301573 CR Approval 23.304 CR0177R1 (Rel-18, 'B'): Path switching between direct and indirect path for Layer-2 UE-to-Network Relay CATT, Ericsson Rel-18 Revision of S2-2300503r05. Approved Agreed
9.7.2 - - - KI#5: Multi-path transmission - - Docs:=9 -
9.7.2 S2-2300256 CR Approval 23.502 CR3689 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#5: Authorizing multi-path transmission via direct Uu and L2 U2N Relay Ericsson Rel-18 r05 agreed. Revised to S2-2301574. Fei (OPPO) comments and provides r01.
Judy (Ericsson) thanks Fei (OPPO) for the revision and I'm fine with r01
Steve (Huawei) provides r02
Mehrdad (MediaTek Inc.) has concern on r02 wording
Steve (Huawei) provides r03
Mehrdad (MediaTek Inc.) thinks r03 is in the right direction but has one question.
Steve (Huawei) comments.
Judy (Ericsson) is fine with the direction of Steve's proposal and provides r04 with minor update
LaeYoung (LGE) asks to add 'LG Electronics' to Judy (Ericsson).
Judy (Ericsson) thanks for LaeYoung (LGE) for the support
Steve (Huawei) r04 looks good and supports the CR.
Mehrdad (MediaTek Inc.) requests to be added as a co-source based on r04.
Judy (Ericsson) provides r05 adding LG, Huawei and MediaTek as co-source.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301574 CR Approval 23.502 CR3689R1 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#5: Authorizing multi-path transmission via direct Uu and L2 U2N Relay Ericsson, LG Electronics, Huawei, HiSilicon, MediaTek Inc. Rel-18 Revision of S2-2300256r05. Approved Agreed
9.7.2 S2-2300382 CR Approval 23.304 CR0168 (Rel-18, 'B'): Authorization information about multi-path transmission for L2 Remote UE LG Electronics, MediaTek Inc. Rel-18 r06 agreed. Revised to S2-2301575. Judy (Ericsson) provides r01 and comments
Mehrdad (MediaTek Inc.) replies to Ericsson.
LaeYoung (LGE) comments on r01.
Judy (Ericsson) responds to LaeYoung (LGE) and provides r02
Mehrdad (MediaTek Inc.) comments on r02
Steve (Huawei) comments, provides r03
Mehrdad (MediaTek Inc.) has concern on r03 wording
Steve (Huawei) comments in the wording
Mehrdad (MediaTek Inc.) replies to Huawei
LaeYoung (LGE) provides r04.
Mehrdad (MediaTek Inc.) is OK with r04 wording.
Steve (Huawei) EN works for me, provides r05 for term alignment
Judy (Ericsson) provides r05
LaeYoung (LGE) comments that Judy (Ericsson) provides r06 instead of r05.
LaeYoung (LGE) replies to Judy (Ericsson).
Judy (Ericsson) thanks LaeYoung (LGE), confirms that she provided r06, and asks to add Ericsson as co-source
Steve (Huawei) r06 looks good and supports the CR.
LaeYoung (LGE) thanks to Steve (Huawei) for co-sign.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301575 CR Approval 23.304 CR0168R1 (Rel-18, 'B'): Authorization information about multi-path transmission for L2 Remote UE LG Electronics, MediaTek Inc., Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2300382r06. Approved Agreed
9.7.2 S2-2300519 CR Approval 23.503 CR0840 (Rel-18, 'B'): 5G ProSe Remote UE traffic handling for multipath transmission via UE-to-Network Relay Intel Rel-18 r01 agreed. Revised to S2-2301576, merging S2-2300987. CC#4: This was postponed. Steve (Huawei) has concerns about legacy
Changhong (Intel) replies to Steve.
Steve (Huawei) comments.
Heng (China Telecom) suggests 0519 and 0987 should be merged.
Changhong (Intel) replies to Heng Nie that 0987 has been asked to be merged into this paper.
Changhong (Intel) replies to Steve comments.
Steve (Huawei) proposes to mark this paper as merged into S2-2300987
Changhong (Intel) provides r01 to reverse the change on NOTE 4.
==== Revisions Deadline ====
Hong (Qualcomm) suggests choosing only 1 CR (between this and 0987). Otherwise, overlapping indicators would be introduced. Alternatively, both should be postponed.
Changhong (Intel) proposes to choose 0519 considering the consistency with other XXX preference (e.g. Access Type preference) in URSP rule today. Naming it with preference gives very straight meaning that it's for guidance in UE implementation.
Steve (Huawei) Let's postpone both 0519 and 0987
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2301576 CR Approval 23.503 CR0840R1 (Rel-18, 'B'): 5G ProSe Remote UE traffic handling for multipath transmission via UE-to-Network Relay Intel Rel-18 Revision of S2-2300519r01, merging S2-2300987. Approved. CC#4: This was withdrawn Withdrawn
9.7.2 S2-2300765 CR Approval 23.304 CR0193 (Rel-18, 'B'): Support of Multi-path Transmission for Layer-3 UE-to-Network Relay without N3IWF ZTE Rel-18 CC#4: This was postponed. Judy (Ericsson) checks what document structure should be used to specify multipath transmission and question the need of the flows.
Mehrdad (MediaTek Inc.) supports the views shared by Ericsson. The new message flows are not needed.
Hao (ZTE) responds.
Steve (Huawei) comments on the flows
Hong (Qualcomm) comments.
Hao (ZTE) responds and provides r01.
Mehrdad (MediaTek Inc.) requests status update on this CR after r01.
Hao (ZTE) provides r02.
Fei (OPPO) comments.
Steve (Huawei) comments.
Mehrdad (MediaTek Inc.) clarifies to OPPO that there is another SA2 meeting before next plenary so we have time to restructure.
Hao (ZTE) provides r03 as suggested by OPPO; and we can have further discussion on this.
==== Revisions Deadline ====
Hong (Qualcomm) comments that this CR has dependency on discussion of 0987 and 0519. It may need to be aligned based on the conclusion of the discussion. Otherwise, it should be postponed with the other two CRs.
Hao (ZTE) is OK to postpone the paper.
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2300986 CR Approval 23.304 CR0196 (Rel-18, 'B'): 5G ProSe Remote UE traffic handling for multipath transmission via Layer-3 UE-to-Network Relay Huawei, HiSilicon Rel-18 Approved. CC#4: This was postponed. ==== Revisions Deadline ====
Fei (OPPO) indicates that this CR has dependency on status of 0519 and 0987
==== Final Comments Deadline ====
Postponed
9.7.2 S2-2300987 CR Approval 23.503 CR0874 (Rel-18, 'B'): 5G ProSe Remote UE traffic handling for multipath transmission via Layer-3 UE-to-Network Relay Huawei, HiSilicon Rel-18 Merged into S2-2301576. CC#4: This was postponed. Changhong (Intel) proposes to mark this paper as merged into S2-2300519.
Steve (Huawei) comments on merge, S2-2300519 should be merged here.
Hannu (Nokia) hasn't done the merge yet but provides r01 to limit the RDS update to non-N3IWF case.
==== Revisions Deadline ====
Hong (Qualcomm) suggests choosing only 1 CR (between this and 0519). Otherwise, overlapping indicators would be introduced.
Steve (Huawei) Let's postpone both 0519 and 0987
==== Final Comments Deadline ====
Postponed
9.7.2 - - - KI#6: PC5 Parameter Provisioning - - Docs:=3 -
9.7.2 S2-2300518 CR Approval 23.304 CR0178 (Rel-18, 'B'): 5G ProSe UE-to-UE Relay and End UE Authorization and Provisioning to UE Intel Rel-18 Merged into S2-2301577 Tingyu (Samsung) suggests merging 0518 (from Intel) into 1173 (from Samsung).
Changhong (Intel) is OK with merging 0518 into 1173.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.7.2 S2-2301173 CR Approval 23.304 CR0205 (Rel-18, 'B'): Authorization and Provisioning for 5G ProSe UE-to-UE Relay Samsung Rel-18 r04 agreed. Revised to S2-2301577, merging S2-2300518 Tingyu (Samsung) provides r01 by merging 0518 (from Intel) into 1173 (from Samsung).
Jungje(Interdigital) provides r02.
Changhong(Intel) confirms to co-sign this paper.
Fei (OPPO) asks questions and comments.
Tingyu (Samsung) replies and provides r03
Hong (Qualcomm) comments.
Fei (OPPO) comments and provides r04.
Tingyu (Samsung) thanks Fei (OPPO) and can live with r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.7.2 S2-2301577 CR Approval 23.304 CR0205R1 (Rel-18, 'B'): Authorization and Provisioning for 5G ProSe UE-to-UE Relay Samsung, Intel Rel-18 Revision of S2-2301173r04, merging S2-2300518. Approved Agreed
9.7.2 - - - Documents exceeding TU Budget - - Docs:=24 -
9.7.2 S2-2300252 CR Approval 23.304 CR0162 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300253 CR Approval 23.501 CR3858 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300254 CR Approval 23.167 CR0369 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300375 CR Approval 23.304 CR0165 (Rel-18, 'B'): Support of Emergency service over UE-to-Network Relay MediaTek Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300599 CR Approval 23.304 CR0179 (Rel-18, 'B'): Support of emergency service over U2N relay OPPO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300704 DISCUSSION Discussion Discussion on non-eRSC usage. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300705 CR Approval 23.304 CR0187 (Rel-18, 'B'): Emergency over non-eRSC L2 U2N relay Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300706 CR Approval 23.304 CR0188 (Rel-18, 'B'): One Remote UE for emergency handling Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300990 CR Approval 23.304 CR0199 (Rel-18, 'B'): Procedure for 5G ProSe UE-to-Network Relay Discovery for emergency service Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300812 CR Approval 23.304 CR0141R1 (Rel-18, 'B'): Support of Public Warning Notification Relaying by 5G ProSe UE-to-Network Relay. Sony, LG Electronics Rel-18 Revision of S2-2210560 Not Handled Hong (Qualcomm) comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300387 CR Approval 23.304 CR0171 (Rel-18, 'B'): RSC definition update for UE-to-UE relaying LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300502 CR Approval 23.304 CR0176 (Rel-18, 'F'): Update for Discovery integrated into PC5 unicast link establishment procedure CATT Rel-18 Not Handled Zhang (Ericsson) suggest to merge this paper into S2-2301237
Deng Qiang (CATT) clarified this CR has been marked as Not Handled.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300988 CR Approval 23.304 CR0197 (Rel-18, 'B'): Authorisation for 5G ProSe UE-to-UE Relay Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300991 CR Approval 23.502 CR3824 (Rel-18, 'B'): Subscription data update for ProSe U2U Relay and ProSe multipath transmission Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300992 CR Approval 23.304 CR0200 (Rel-18, 'B'): General description of 5G ProSe UE-to-UE Relay Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2301239 CR Approval 23.304 CR0207 (Rel-18, 'F'): Updates on UE-to-UE Relay reselection Interdigital Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300764 CR Approval 23.304 CR0192 (Rel-18, 'B'): Procedures for Communication Path Switching between PC5 and Uu ZTE Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300984 CR Approval 23.304 CR0194 (Rel-18, 'B'): Communication path switching between PC5 and Uu reference points Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2301131 CR Approval 23.304 CR0204 (Rel-18, 'B'): Path switching between PC5 and Uu(i.e. not Relay) Xiaomi Rel-18 Not Handled Hannu (Nokia) asks whether it is right to assume that S2-2300384 is taken as the basis for PC5 - Uu path switch CR and this CR is not needed?
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2301241 CR Approval 23.304 CR0209 (Rel-18, 'B'): Path Switch between Uu and PC5 Interdigital Rel-18 Not Handled Hannu (Nokia) asks whether it is right to assume that S2-2300384 is taken as the basis for PC5 - Uu path switch CR and this CR is not needed?
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300255 CR Approval 23.304 CR0163 (Rel-18, 'B'): Introducing 5G ProSe ph2 function for KI#5: Authorizing multi-path transmission via direct Uu and L2 U2N Relay Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300383 CR Approval 23.502 CR3711 (Rel-18, 'B'): Subscription data about multi-path transmission for L2 Remote UE LG Electronics, MediaTek Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300989 CR Approval 23.304 CR0198 (Rel-18, 'B'): Authorisation for Multi-path transmission via UE-to-Network Relay Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.7.2 S2-2300699 CR Approval 23.503 CR0775R1 (Rel-18, 'B'): Multi-Path transmission OPPO Rel-18 Revision of S2-2210533 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.1 - - - Study on Generic group management, exposure and communication enhancements (FS_GMEC) - - Docs:=7 -
9.8.1 - - - For dynamic control of cross-UPF connectivity of KI#4 - - Docs:=3 -
9.8.1 S2-2301268 P-CR Approval 23.700-74: KI#4: Conclusion proposal. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301801 Baseline for evaluation, conclusion merges in 1190 Qianghua (Huawei) proposes to merge 01268 into 01190r01
Georgios Gkellas (Nokia, Nokia Shanghai Bell) Agrees to merge 01268 to 1190r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.8.1 S2-2301190 P-CR Approval 23.700-74: KI#4, evaluations and conclusions. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301801, merging S2-2301268 Baseline for conclusion, evaluation merges in 1268 Georgios Gkellas (Nokia, Nokia Shanghai Bell) Provides S2-2301190r01
Qianghua (Huawei) provides r02, removing some unclear evaluation parts and only keeping the conclusion for dynamic control
Sang-Jun (Samsung) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.1 S2-2301801 P-CR Approval 23.700-74: KI#4, evaluations and conclusions. Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung, Ericsson Rel-18 Revision of S2-2301190r04, merging S2-2301268. Approved Approved
9.8.1 - - - For other aspects of KI#4 - - Docs:=2 -
9.8.1 S2-2300359 P-CR Approval 23.700-74: KI#4: Conclusion proposal. Ericsson, Nokia, Nokia Shanghai Bell, Juniper, Broadcom Rel-18 r04 agreed. Revised to S2-2301802. Baseline for communication reliability, compatibility and static connectivity Qianghua (Huawei) provides r01
Sang-Jun (Samsung) provides r02
Hiroshi (NEC) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
Sang-Jun (Samsung) is OK with r04
==== Final Comments Deadline ====
Revised
9.8.1 S2-2301802 P-CR Approval 23.700-74: KI#4: Conclusion proposal. Ericsson, Nokia, Nokia Shanghai Bell, Juniper, Broadcom, Huawei, Samsung, NEC Rel-18 Revision of S2-2300359r04. Approved Approved
9.8.1 - - - Documents exceeding TU budget - - Docs:=2 -
9.8.1 S2-2300807 P-CR Approval 23.700-74: Evaluation and Conclusion for FS_GMEC KI#4. Samsung Rel-18 Not Handled Not handled, can merge into 1268, 1190 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.1 S2-2300360 P-CR Approval 23.700-74: KI#4, Sol#16: Updates to resolve editor s notes . Ericsson Rel-18 Not Handled Not handled, sol update for reference ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.2 - - - Generic group management, exposure and communication enhancements (GMEC) - - Docs:=40 -
9.8.2 - - - KI#1 - - Docs:=18 -
9.8.2 S2-2301191 CR Approval 23.501 CR4086 (Rel-18, 'B'): KI#1: Support the enhancement of group attribute management Huawei, HiSilicon, Nokia, Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2301803. Baseline for 501 structure and AF indication that group is for 5G VN group communication Qianghua (Huawei) provides r01
Stefan (Ericsson) comments and provides r02
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
Hyunsook (LGE) can live with r04.
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301803 CR Approval 23.501 CR4086R1 (Rel-18, 'B'): KI#1: Support the enhancement of group attribute management Huawei, HiSilicon, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301191r04. Approved Agreed
9.8.2 S2-2301192 CR Approval 23.502 CR3853 (Rel-18, 'B'): KI#1: Support the enhancement of group attribute management Huawei, HiSilicon, Nokia, Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2301804. Baseline for 502 structure and AF indication that group is for 5G VN group communication Qianghua (Huawei) provides r01
Georgios Gkellas (Nokia, Nokia Shanghai Bell) provides r02
Stefan (Ericsson) provides r03
Sang-Jun (Samsung) provides comments on r03
Hyunsook (LGE) suggests to use 'LADN per DNN and S-NSSAI'.
Hyunsook (LGE) provides r04.
Qianghua (Huawei) provides r05
==== Revisions Deadline ====
Hyunsook (LGE) is fine with r05 and wants to cosign.
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301804 CR Approval 23.502 CR3853R1 (Rel-18, 'B'): KI#1: Support the enhancement of group attribute management Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, LG Electronics Rel-18 Revision of S2-2301192r05. Approved Agreed
9.8.2 S2-2300482 CR Approval 23.501 CR3914 (Rel-18, 'B'): Service area provisioning and LADN aspects for enhanced group management LG Electronics Rel-18 r12 agreed. Revised to S2-2301805, merging S2-2300405 Baseline for service area aspect (501) Dan (China Mobile) provides r01 with adding the link
Stefan (Ericsson) provides comments and r02
Dan (China Mobile) provides r03
Qianghua (Huawei) provides r04
Hyunsook (LGE) comments.
Sang-Jun (Samsung) provides r05.
Dan (China Mobile) reply.
Hyunsook (LGE) provide the comments on r04/r05.
Hyunsook (LGE) asks about the study conclusion.
Sang-Jun (Samsung) responds to Hyunsook (LGE)
Hyunsook (LGE) provides r06.
Qianghua (Huawei) provides responses, OK with r05 /r06 and welcome further updates
Dan (China Mobile) provides r07
Georgios Gkellas (Nokia, Nokia Shanghai Bell) provides responses, agrees with r05/r06, considers r06 more clear
Sang-Jun (Samsung) provides comments
Hyunsook (LGE) provides comments
Dan (China Mobile) provides r08
Georgios Gkellas (Nokia, Nokia Shanghai Bell) provides r09
Qianghua (Huawei) provides r10
Stefan (Ericsson) provides r04
Qianghua (Huawei) corrects that: Stefan (Ericsson) provides r11, not r04
Hyunsook (LGE) provides r12.
==== Revisions Deadline ====
Sang-Jun (Samsung) is OK with r12
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301805 CR Approval 23.501 CR3914R1 (Rel-18, 'B'): Service area provisioning and LADN aspects for enhanced group management LG Electronics, Huawei, Samsung, China Mobile, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300482r12, merging S2-2300405. Approved Agreed
9.8.2 S2-2300405 CR Approval 23.501 CR3891 (Rel-18, 'B'): Enforcement of service area applicable to 5G VN group China Mobile Rel-18 Merged into S2-2301805 merge with 0482 (confirmed) Dan (China Mobile) this paper is merged into S2-2300482
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.8.2 S2-2300879 CR Approval 23.501 CR4010 (Rel-18, 'B'): Add the service area and the default QoS parameters for 5G VN group data CATT Rel-18 r04 agreed. Revised to S2-2301806. Baseline for QoS (501), merge service area aspect with 0482? Liping Wu (CATT) provides r01 to remove the service area part.
Qianghua (Huawei) provides r02
Hyunsook (LGE) provides comments
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
Hyunsook (LGE) can live with r04.
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301806 CR Approval 23.501 CR4010R1 (Rel-18, 'B'): Add the default QoS parameters for 5G VN group data CATT, Huawei Rel-18 Revision of S2-2300879r04. Approved Agreed
9.8.2 S2-2300353 CR Approval 23.502 CR3708 (Rel-18, 'B'): Exposure of Service Area and Default QoS for a DNN/S-NSSAI and group of UEs Ericsson Rel-18 r04 agreed. Revised to S2-2301807, merging S2-2300545 and S2-2300878 Baseline for QoS and service area (502) Qianghua (Huawei) provides r01
Liping Wu (CATT) provides r02.
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
Hyunsook (LGE) is fine with r04 and wants to cosign.
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301807 CR Approval 23.502 CR3708R1 (Rel-18, 'B'): Exposure of Service Area and Default QoS for a DNN/S-NSSAI and group of UEs Ericsson, CATT, China Telecom, Huawei, LG Electronics Rel-18 Revision of S2-2300353r04, merging S2-2300545 and S2-2300878. Approved Agreed
9.8.2 S2-2300787 CR Approval 23.501 CR3982 (Rel-18, 'B'): Group MBR Samsung Rel-18 r05 agreed. Revised to S2-2301808, merging S2-2300877 Baseline for Group-MBR (501) Liping Wu (CATT) provide r01 to merge S2-2300877 into S2-2300787.
Stefan (Ericsson) comments and provides r02
Qianghua (Huawei) provides r03
Sang-Jun (Samsung) is fine with r03.
Stefan (Ericsson) provides r04 adding an EN
Qianghua (Huawei) provides r05
==== Revisions Deadline ====
Sang-Jun (Samsung) is OK with r05
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301808 CR Approval 23.501 CR3982R1 (Rel-18, 'B'): Group MBR Samsung, Huawei Rel-18 Revision of S2-2300787r05, merging S2-2300877. Approved Agreed
9.8.2 S2-2300877 CR Approval 23.501 CR4009 (Rel-18, 'B'): Add the Group-MBR parameter for 5G VN group data CATT Rel-18 Merged into S2-2301808 Merge with 0787? Liping Wu (CATT) agrees to merge S2-2300877 into S2-2300787.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.8.2 S2-2300878 CR Approval 23.502 CR3805 (Rel-18, 'B'): Add the Group-MBR parameter for 5G VN group data CATT Rel-18 Merged into S2-2301807 Baseline for Group-MBR (502) Liping Wu (CATT) provides r01.
Qianghua (Huawei) provides comments on whether to apply group-MBR only to 5G VN group
Jun (China Telecom) provides comments on whether to apply group-MBR only to 5G VN group.
Liping Wu (CATT) agrees to merge 0878 to 0353.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.8.2 S2-2300545 CR Approval 23.502 CR3744 (Rel-18, 'B'): GMEC KI1 TS23.502 CR Update for Group MBR China Telecom Rel-18 Merged into S2-2301807 To be merged into S2-2300878 (Merged into S2-2301807) Jun (China Telecom) this paper is merged into S2-2300878
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.8.2 S2-2300586 CR Approval 23.503 CR0841 (Rel-18, 'B'): GMEC KI1 TS23.503 CR Update for Group MBR China Telecom, Huawei, CATT Rel-18 r02 agreed. Revised to S2-2301809. Baseline for Group-MBR (503) Qianghua (Huawei) provides r01, applying group-MBR for general group
Jun (China Telecom) is fine with r01.
Stefan (Ericsson) provides r02 adding an EN
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301809 CR Approval 23.503 CR0841R1 (Rel-18, 'B'): GMEC KI1 TS23.503 CR Update for Group MBR China Telecom, Huawei, CATT Rel-18 Revision of S2-2300586r02. Approved Agreed
9.8.2 - - - KI#3 - - Docs:=16 -
9.8.2 S2-2301193 CR Approval 23.501 CR4087 (Rel-18, 'B'): KI#3: provisioning of traffic characteristics and monitoring of performance characteristics Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301810. Baseline for 501 structure and using SSPP service Qianghua (Huawei) provides r01
Stefan (Ericsson) provides r02
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301810 CR Approval 23.501 CR4087R1 (Rel-18, 'B'): KI#3: provisioning of traffic characteristics and monitoring of performance characteristics Huawei, HiSilicon Rel-18 Revision of S2-2301193r04. Approved Agreed
9.8.2 S2-2300806 CR Approval 23.501 CR3984 (Rel-18, 'B'): UE-to-UE QoS for a group Samsung Rel-18 r04 agreed. Revised to S2-2301811. Baseline for UE-to-UE QoS Qianghua (Huawei) provides r01
Stefan (Ericsson) provides r02
Heng (China Telecom) provides r03
Sebastian (Qualcomm) comments
Sang-Jun (Samsung) provides r03 based on Sebastian (Qualcomm)'s comments
Sang-Jun (Samsung) provides r04 based on Sebastian (Qualcomm)'s comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301811 CR Approval 23.501 CR3984R1 (Rel-18, 'B'): UE-to-UE QoS for a group Samsung, Huawei, China Telecom Rel-18 Revision of S2-2300806r04. Approved Agreed
9.8.2 S2-2300680 CR Approval 23.501 CR3964 (Rel-18, 'B'): KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs ZTE Rel-18 r04 agreed. Revised to S2-2301812. Baseline for PDU Type change and temporal invalidity/validity condition (501) zhendong (ZTE) provides r01.
Stefan (Ericsson) provides comments and questions
zhendong (ZTE) provides response.
zhendong (ZTE) provides r02.
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301812 CR Approval 23.501 CR3964R1 (Rel-18, 'B'): KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs ZTE, Huawei Rel-18 Revision of S2-2300680r04. Approved Agreed
9.8.2 S2-2300681 CR Approval 23.502 CR3774 (Rel-18, 'B'): KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs ZTE Rel-18 r02 agreed. Revised to S2-2301813. Baseline for PDU Type change (502) zhendong (ZTE) provides r01.
Stefan (Ericsson) provides r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301813 CR Approval 23.502 CR3774R1 (Rel-18, 'B'): KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs ZTE Rel-18 Revision of S2-2300681r02. Approved Agreed
9.8.2 S2-2300355 CR Approval 23.502 CR3709 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, enhancing AF-session-with-QoS service Ericsson Rel-18 Noted Qianghua (Huawei) proposes to note this CR and uses new NEF service as in 0357, 0358 to go forward
==== Revisions Deadline ====
Stefan (Ericsson) OK to note and use 0357, 0358 instead
==== Final Comments Deadline ====
Noted
9.8.2 S2-2300356 CR Approval 23.503 CR0818 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, enhancing AF-session-with-QoS service Ericsson Rel-18 Noted Qianghua (Huawei) proposes to note this CR and uses new NEF service as in 0357, 0358 to go forward
==== Revisions Deadline ====
Stefan (Ericsson) OK to note and use 0357, 0358 instead
==== Final Comments Deadline ====
Noted
9.8.2 S2-2300357 CR Approval 23.502 CR3710 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, using new NEF service Ericsson Rel-18 r03 agreed. Revised to S2-2301814. Baseline for using new AF request QoS service (502) Qianghua (Huawei) provides r01
Stefan (Ericsson) provides r02
Qianghua (Huawei) provides r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301814 CR Approval 23.502 CR3710R1 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, using new NEF service Ericsson Rel-18 Revision of S2-2300357r03. Approved Agreed
9.8.2 S2-2300358 CR Approval 23.503 CR0819 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, using new NEF service Ericsson Rel-18 r03 agreed. Revised to S2-2301815. Baseline for using new AF request QoS service (503) Qianghua (Huawei) provides r01
Stefan (Ericsson) provides r02
Georgios Gkellas (Nokia, Nokia Shanghai Bell) Agrees with r02
Qianghua (Huawei) provides r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301815 CR Approval 23.503 CR0819R1 (Rel-18, 'B'): Exposure of traffic characteristics and performance monitoring for a group of UEs, using new NEF service Ericsson Rel-18 Revision of S2-2300358r03. Approved Agreed
9.8.2 S2-2300679 DISCUSSION Decision Discussion on the issues for the key issue#3 ZTE Rel-18 Noted Qianghua (Huawei) proposes to note the discussion contribution
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.8.2 S2-2300354 DISCUSSION Approval NEF service for KI#3 . Ericsson Rel-18 Noted Qianghua (Huawei) proposes to note the discussion contribution
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.8.2 - - - KI#5 - - Docs:=2 -
9.8.2 S2-2300809 CR Approval 23.501 CR3986 (Rel-18, 'B'): Allowing UE to simultaneously send data to different groups with different QoS policy Samsung, Huawei [Nokia, Nokia Shanghai Bell] Rel-18 r01 agreed. Revised to S2-2301816. Baseline Sebastian (Qualcomm) provides r01
==== Revisions Deadline ====
Sang-Jun (Samsung) is OK with r01
==== Final Comments Deadline ====
Revised
9.8.2 S2-2301816 CR Approval 23.501 CR3986R1 (Rel-18, 'B'): Allowing UE to simultaneously send data to different groups with different QoS policy Samsung, Huawei Rel-18 Revision of S2-2300809r01. Approved Agreed
9.8.2 - - - Documents exceeding TU budget - - Docs:=4 -
9.8.2 S2-2300880 CR Approval 23.502 CR3806 (Rel-18, 'B'): Add the service area and the default QoS parameters for 5G VN group data CATT Rel-18 Not Handled Not handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.2 S2-2300790 CR Approval 23.501 CR3983 (Rel-18, 'B'): LADN-based Service Area Restriction for a group Samsung Rel-18 Not Handled Not handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.2 S2-2300542 CR Approval 23.501 CR3931 (Rel-18, 'B'): GMEC KI1 TS23.501 CR Update for Group MBR China Telecom Rel-18 Not Handled Not handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.8.2 S2-2301194 CR Approval 23.502 CR3854 (Rel-18, 'B'): KI#3: provisioning of traffic characteristics and monitoring of performance characteristics Huawei, HiSilicon Rel-18 Not Handled Not handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.9.1 - - - Study on System Support for AI/ML-based Services (FS_AIMLsys) - - Docs:=0 -
9.9.2 - - - System Support for AI/ML-based Services (AIMLsys) - - Docs:=63 -
9.9.2 - - - LSin/out and General - - Docs:=6 -
9.9.2 S2-2300548 DISCUSSION Discussion New 5QI for AIML based services. Qualcomm Incorporated Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.9.2 S2-2300559 LS OUT Approval [DRAFT] LS about KPIs for AI/ML model transfer in 5GS QUALCOMM JAPAN LLC. Rel-18 r07 agreed. Revised to S2-2301578. Tricci <OPPO> provides revision r01 for editorial update to the LS out
LaeYoung (LGE) provides r02.
Yang (OPPO) provides r03.
Belen (Ericsson) provides comments
Juan Zhang (Qualcomm) replies to Ericsson
Tingyu (Samsung) provides r04.
Juan Zhang (Qualcomm) is OK with r04.
Yang (OPPO) provides R05 adding more questions
Tingyu (Samsung) is OK with r05.
Belen (Ericsson) provides r07,
==== Revisions Deadline ====
LaeYoung (LGE) is fine to go with r07.
Juan Zhang (Qualcomm) is fine to go with r07.
Yang (OPPO) is ok to agree r07
Tingyu (Samsung) is fine with r07.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301578 LS OUT Approval LS about KPIs for AI/ML model transfer in 5GS SA WG2 Rel-18 Revision of S2-2300559r07. Approved Approved
9.9.2 S2-2300146 CR Approval 23.501 CR3826 (Rel-18, 'B'): AIMLsys High-level Descriptions for 5GS assistance for Application AI/ML operation OPPO Rel-18 Merged into S2-2301579 Merge into S2-2300728 David (Samsung) provides comments, suggests to merge this contribution into S2-2300728.
Tricci (OPPO) thanks David (Samsung) feedback and agreed to merge the two CRs. In addition, OPPO has already provided comments to S2-2300728. Please check.
David (Samsung) thanks OPPO for clarifying their position, agrees to get further feedback from other companies.
Juan Zhang (Qualcomm) proposes to postpone the CR.
David (Samsung) wonders if this is the right thread for Qualcomm's former comment.
Juan Zhang (Qualcomm) withdraw the previous comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300728 CR Approval 23.501 CR3968 (Rel-18, 'B'): 5GS Assistance for Application AI/ML operation: General clause Samsung Rel-18 r10 agreed. Revised to S2-2301579, merging S2-2300146 and S2-2300484 Baseline for S2-2300146 Tricci <OPPO> proposes to merge OPPO's S2-2300146 into this CR S2-2300728 and provides r01 for S2-2300728 with EN.
Dongjoo <Nokia> provides comments and asks for a revision .
Belen (Ericsson) provides r02, cannot accept r01 or initial version
David (Samsung) provides r03.
Tricci (OPPO) thanks David (Samsung) and Belen (Ericsson) update and can live with the minimum descriptions. OPPO provides r04.
Juan Zhang (Qualcomm) provides comments on r04.
Dongjoo (Nokia) provides r05.
Jihoon (ETRI) asks for clarification.
David (Samsung) provides r07 (please disregard r06).
Tricci (OPPO) thanks David (Samsung) update and would like to ask for clarifications?
Tricci (OPPO) provides r08 to remove the unnecessary wordings.
Tricci (OPPO) thanks Hyunsook (LGE) update, however, OPPO cannot accept r09 at this point due to inconsistency on capturing the general descriptions of the AI/ML functionalities in this general clause.
David (Samsung) comments.
Dongjoo (Nokia) provides comments.
Tricci (OPPO) responds to both Dongjoo (Nokia) and David (Samsung) feedback and disagrees on the comments from Samsung which does not reflect the actual event. Never-the-less, the important thing for this meeting is to find a common ground for us to move forward. OPPO would like to suggest to defer the general descriptions for the AI/ML functionalities in the general clause in this meeting until the normative work is more stable.
David (Samsung) asks a question for clarification to OPPO.
Tricci (OPPO) apologizes to David (Samsung) for not being clear on OPPO's suggestion and would like to further clarify.
David (Samsung) thanks Tricci, agrees with the clarification.
Juan Zhang (Qualcomm) also supports to continue discuss based on r08.
Tricci (OPPO) provides r09 to remove the abbreviation clause like in other CR to not to repeat the AIML abbreviation. Also, to remove the highlevel descriptions of the Member Selection Functionality as we will update the general clause in the next meeting once the normative work for different application AI/ML functionalities becomes stable.
Dongjoo (Nokia) asks questions to Tricci(OPPO)
Tricci (OPPO) apologizes to Dongjoo (Nokia) for uploading the wrong version. r09 has been uploaded by LGE. Hence, I should upload r10 instead. Sorry...
Dongjoo (Nokia) is fine with r10 and would like to co-sign
Hyunsook (LGE) provides comments on r10.
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r10.
Hyunsook (LGE) can live with r10.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301579 CR Approval 23.501 CR3968R1 (Rel-18, 'B'): 5GS Assistance for Application AI/ML operation: General clause Samsung, OPPO, LG Electronics, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300728r10, merging S2-2300146 and S2-2300484. Approved Agreed
9.9.2 - - - Key Issue #1: Monitoring of network resource utilization for support of Application AI/ML operations - - Docs:=4 -
9.9.2 S2-2300121 CR Approval 23.502 CR3662 (Rel-18, 'B'): Procedure to provision and enforce Group-MBR Ericsson Rel-18 Noted Tricci <OPPO> asks for clarifications, provides comments and suggests a possible way forward for Group-MBR monitoring support.
Tricci <OPPO> has provided a list of detailed technical comments in previous email and can NOT accept this CR until all OPPO's concern are addressed.
Dongeun (Samsung) comments
Tricci (OPPO) thanks Dongeun (Samsung) good comments and to provide response.
Belen (Ericsson) answers OPPO questions. Answers Samsung´s questions, Think that Group MBR enforcement may need more discussion, that includes S2-2300148
==== Revisions Deadline ====
Tricci (OPPO) proposes to NOTED or to postpone this CR as we have no agreement on how to proceed the support for Group-MBR monitoring.
==== Final Comments Deadline ====
Noted
9.9.2 S2-2300148 CR Approval 23.502 CR3672 (Rel-18, 'B'): KI#1 23.502 Solution for 5GC assistance to support Group-MBR Monitoring via NEF Event Exposure Extensions OPPO, Oracle Rel-18 Postponed Belen (Ericsson) objects to this initial version, provides comments
Tricci (OPPO) cannot accept the objection reason from Belen (Ericsson) by suggesting the Group-MBR monitoring is to be done in another R18 WID UPEAS which does NOT support 'dynamic' group of QoS flows monitoring and it has not been examined or agreed during the AIMLsys conclusions.
Tricci (OPPO) provides r01 to fix the missing 'new' parameter, i.e. traffic filtering information, for NEF Event Exposure subscription service which is used to identify the target QoS flow to be monitored within each application for the selected UEs. The traffic filtering information is needed in order to ensure the QoS information be provided by the NEF to PCF to trigger the UPF monitoring event.
David (Samsung) requests clarification on this CR.
Tricci (OPPO) thanks David (Samsung) question and provides feedback.
Yingying (CATT) asks for clarifications for which TR conclusion and procedures that this CR is based on to propose updating QoS Monitoring PCC rules to include also the bit rate reporting for specific QoS flow. Also, the proposed change violates the agreed conclusion that How the UPF reports traffic/data volume is determined in UPEAS SID. Finally, we suggest following the agreed conclusion that Only after UPEAS study work is completed, AIMLsys will determine if the traffic/data volume is required to report from 5GC to AF. Hence, this CR should be NOTED as the way that it is defined.
Tricci (OPPO) responds to Yingying (CATT) for incorrect understanding of the TR conclusion for this CR. OPPO demands CATT to provide the actual facts and concrete proof that OPPO violates the TR conclusion for the Group-MBR monitoring support. Hoping CATT can be reasonable to respect the TR conclusion and withdraw your unjustified objection for this CR which is prepared according to the TR conclusion.
Tricci (OPPO) provides further response to Yingying (CATT) on the target UPF reporting alignment considerations.
Belen (Ericsson) objects to this CR, agrees with CATT comments and requests to postpone
Tricci (OPPO) confuse by Belen (Ericsson) comments because Ericsson's CR S2-2300121 did the same thing.
Yingying (CATT) thanks Tricci (OPPO) for further clarification and can live with the updated version since the 'Editor's Note' has been added.
David (Samsung) provides further comments
Tricci (OPPO) requests concrete technical justification from Belen (Ericsson) to explain why this CR does not work without a specific technical justifications. OPPO plans to bring this issue to SA2 CC for discussions.
Tricci (OPPO) asks Belen (Ericsson) again, please provide concrete technical justifications for objecting this CR.
Tricci (OPPO) provides feedback to David (Samsung).
Belen (Ericsson) asks Tricci to please focus on the comments to the CRs.
Belen (Ericsson) still objects to this CR
==== Revisions Deadline ====
Tricci (OPPO) proposes to NOTED or to postpone this CR as it is clear that we have no agreement on how to proceed the support for Group-MBR monitoring.
Belen (Ericsson) asks to POSTPONE, to be fair. Given that OPPO CR on the same topic is POSTPONED
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300388 CR Approval 23.503 CR0823 (Rel-18, 'B'): KI#1 23.503 Solution for 5GC assistance to support Group-MBR Monitoring via UPF Event Exposure Extensions OPPO, Oracle Rel-18 Postponed Belen (Ericsson) provides comments, asks if the CR is needed
David (Samsung) agrees this discussion conflicts with the generalization of QoS monitoring CR and doubts whether we can make any progress now
Yingying (CATT) shares the view that the discussion on a generalization of QoS Monitoring will cover this CR. Also, we suggest following the agreed conclusion that Only after UPEAS study work is completed, AIMLsys determines the UPF Event Exposure Extensions things. Hence, this CR should be NOTED as the way that it is defined.
Mehrdad (MediaTek Inc.) requests a status update for this CR.
Tricci (OPPO) responds to Mehrdad (MediaTek Inc.) and all and is okay to postpone this CR until the next meeting once we complete the QoS Monitoring alignment. Thanks.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300755 CR Approval 23.502 CR3786 (Rel-18, 'B'): NEF monitoring events for assisting AIML operation Samsung Rel-18 Postponed Tricci <OPPO> asks for clarifications on the introduction of the 'new' NEF exposure events.
Bahador <NTT DOCOMO> asks for clarifications regarding new events
Belen (Ericsson) provides comments
David (Samsung) replies to comments from OPPO and NTT DOCOMO.
David (Samsung) replies to Ericsson
Tricci (OPPO) thanks David (Samsung) for the responses, and more fundamental questions on how feasible for those events are triggered.
Jihoon (ETRI) asks a question.
Tricci (OPPO) responds to Jihoon (ETRI) question.
Mirko (Huawei) comments.
David (Samsung) answers to comments.
Tricci (OPPO) thanks David (Samsung) responses and would like to clarify OPPO's concern regarding to the new events.
David (Samsung) answers to OPPO.
Tricci (OPPO) thanks the patient from David (Samsung) to respond to OPPO, and OPPO will provide a more clarifications to David and hoping that it is more clear on explaining OPPO's concern on the new events of this CR.
Belen (Ericsson) provides comments, details are needed as explained in earlier emails
David (Samsung) provides r01, answers comments.
Tricci (OPPO) thanks David (Samsung) revision, unfortunately, OPPO still feel more concrete discussions are needed and can not accept this CR as is.
Belen (Ericsson) provides r03, is okay with r01 with some updates as proposed.
Tricci (OPPO) sustains objection against this CR and responds to David (Samsung) and would be happy to capture this for CC#3/4 discussions.
David (Samsung) finds OPPO's objection unreasonable and unacceptable, provides r02 and would like it to be open in CC#3/4 if OPPO's objection is sustained.
David (Samsung) thanks Ericsson, would be OK with both r03 and r02.
==== Revisions Deadline ====
Dongjoo (Nokia) can live with both r02 and r03.
Uri (Oracle) comments, suggests to postpone to next meeting.
David (Samsung) is OK to postpone this CR.
==== Final Comments Deadline ====
Postponed
9.9.2 - - - Key Issue #3: 5GC Information Exposure to authorized 3rd party for Application Layer AI / ML Operation - - Docs:=3 -
9.9.2 S2-2300484 CR Approval 23.501 CR3916 (Rel-18, 'B'): Network exposure for Application Layer AI/ML Operation LG Electronics Rel-18 Merged into S2-2301579 Tricci <OPPO> asks for similar clarifications from LGE colleague for the questions against S2-2300755 from Samsung.
David (Samsung) suggests to merge this contribution into S2-2300728.
Hyunsook (LGE) comments.
Dongjoo (Nokia) provides comments and suggests merging this paper into S2-2300728.
Hyunsook (LGE) is o.k. to merge this paper into S2-2300728.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300718 CR Approval 23.503 CR0846 (Rel-18, 'B'): Exposure to authorized 3rd party for AI/ML Huawei, HiSilicon Rel-18 Postponed Zhang (Ericsson) ask for clarification
Jaewoo (LGE) asks for clarifications.
Mehrdad (MediaTek Inc.) supports the view shared by Ericsson. AF can directly interact with NWDAF for QoS sustainability analytics even in past releases
Dongjoo (Nokia) shares the same view as MediaTek and Ericsson
Juan Zhang (Qualcomm) has the same comments as Ericsson and MediaTek.
Susan (Huawei) replies.
Juan Zhang (Qualcomm) replies to Susan (Huawei).
Susan (Huawei) replies to Juan Zhang (Qualcomm).
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r00.
Zhang (Ericsson) suggest to postpone the paper due it is still unclear the motivation
Dongjoo (Nokia) supports Zhang (Ericsson)'s view to postpone it.
Mehrdad (MediaTek Inc.) also suggests to postpone this.
Susan (Huawei) replies and ok to postpone the CR.
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2301205 CR Approval 23.501 CR4091 (Rel-18, 'B'): User consent checking for member selection assistance exposure Google Inc. Rel-18 Postponed Tricci <OPPO> proposes to discuss this CR under the agenda of KI#3 and not KI#7 since there is no TR conclusion related to the user consent under KI#7.
Tricci <OPPO> proposes to NOTED this CR for now and to wait for the SA3's conclusion in order to proceed any further normative work in SA2. .
Belen (Ericsson) supports OPPO view
Tingyu (Samsung) also supports OPPO's view.
Ellen (Google) feedback
Juan Zhang (Qualcomm) provides comments on r01.
Ellen (Google) feedback to Qualcomm
==== Revisions Deadline ====
Belen (Ericsson) agrees to POSTPONE this topic
Ellen (Google) agrees to POSTPONE this paper
==== Final Comments Deadline ====
Postponed
9.9.2 - - - Key Issue #4: Enhancing External Parameter Provisioning - - Docs:=4 -
9.9.2 S2-2300108 CR Approval 23.502 CR3660 (Rel-18, 'B'): Enhancing the Expected UE Behaviour parameters clause Rakuten Mobile Rel-18 Merged into S2-2301580 Merge into S2-2300731 Tricci <OPPO> proposes to merge S2-2300108 into S2-2300731 from Samsung to have single stream discussions on the same topic for KI#4.
Manmeet (Rakuten) agrees to merge S2-2300108 into S2-2300731 as suggested by the rapporteurs.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300143 CR Approval 23.502 CR3670 (Rel-18, 'B'): Confidence Level for Expected UE Behaviour Parameters NTT DOCOMO Rel-18 Merged into S2-2301580 Merge into S2-2300731 Tricci <OPPO> proposes to merge S2-2300143 into S2-2300731 from Samsung to have single stream discussions on the same topic for KI#4.
Bahador (NTT DOCOMO) agrees to merge S2-2300143 into S2-2300731 as suggested by the rapporteurs.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300731 CR Approval 23.502 CR3780 (Rel-18, 'B'): External parameter provisioning enhancements for AI/ML-based services Samsung, Rakuten Mobile Rel-18 r04 agreed. Revised to S2-2301580, merging S2-2300108 and S2-2300143 Baseline for S2-2300108, S2-2300143 Zhang (Ericsson) show concerns on this paper, and suggest to use S2-2300143 as baseline
Tricci <OPPO> proposes this tdoc S2-2300731 to be used as the baseline to merge with S2-2300108 (from Rakuten Mobile) and with S2-2300143 (from DoCoMo).
Dongjoo (Nokia) supports Ericsson's suggestion, and comments and questions.
David (Samsung) replies to comments from Ericsson and Nokia, provides r01
Zhang (Ericsson) response to David (Samsung)
Dongjoo (Nokia) responses to David (Samsung) and asks another question
David (Samsung) provides r02, replies to further comments
Dongjoo (Nokia) is fine with r02
Zhang (Ericsson) response to David and provide r03
David (Samsung) provides r04 with minor rewording in step 7
==== Revisions Deadline ====
Dongjoo (Nokia) can accept r04
Zhang (Ericsson) is OK with r04
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301580 CR Approval 23.502 CR3780R1 (Rel-18, 'B'): External parameter provisioning enhancements for AI/ML-based services Samsung, Rakuten Mobile Rel-18 Revision of S2-2300731r04, merging S2-2300108 and S2-2300143. Approved Agreed
9.9.2 - - - Key Issue #5: 5GC Enhancements to enable Application AI/ML Traffic Transport - - Docs:=10 -
9.9.2 S2-2300123 CR Approval 23.503 CR0796 (Rel-18, 'B'): PDTQ removing Editor s Notes Ericsson Rel-18 Noted Tricci <OPPO> asks for clarifications and proposes to merge this CR into S2-2300144 from DoCoMo to have a single stream of discussions for CRs which overlap the same clauses.
Tricci <OPPO> proposes to merge this CR into S2-2300144 from DoCoMo and to provide feedback on those questions that have been raised by OPPO in the previous email. Thanks. .
==== Revisions Deadline ====
Tricci <OPPO> proposed to NOTED or postpone this CR. OPPO receives no feedback for the questions asked, and receives no feedback for the proposed merge of this CR into S2-2300144 from DoCoMo.
==== Final Comments Deadline ====
Noted
9.9.2 S2-2300774 CR Approval 23.503 CR0855 (Rel-18, 'B'): Update to remove ENs related to PDTQ policy Huawei, HiSilicon Rel-18 Merged into S2-2301482 To be merged into S2-2300144 (For CC#4) Tricci <OPPO> proposes to merge this CR into S2-2300144 from DoCoMo to have a single stream of discussions on CRs which proposed changes to the common clauses.
Wang Yuan (Huawei) is ok to merge this CR into S2-2300144.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300775 CR Approval 23.288 CR0656 (Rel-18, 'B'): Update the input and output data of DN Performance Analytics Huawei, HiSilicon Rel-18 Postponed Tricci <OPPO> asks for clarifications form Huawei regarding the reason for introducing the Time Window in the DN Performance Analytics.
Bahador <NTT DOCOMO> asks for clarifications regarding the new input and output
Dongjoo <Nokia> shares the same view with NTT Docomo and OPPO
Wang Yuan (Huawei) replies to Tricci (OPPO), Bahador (NTT DOCOMO), Dongjoo (Nokia).
Bahador (NTT DOCOMO) replies to Yuan (Huawei)
Dongjoo <Nokia> asks further questions to Yuan (Huawei)
Wang Yuan (Huawei) replies to Bahador (NTT DOCOMO) and provides r02.
Wang Yuan (Huawei) replies to Dongjoo (Nokia).
David (Samsung) agrees with OPPO, Nokia, NTT DOCOMO and requests Time Window to be removed from the analytics
Bahador (NTT DOCOMO) provides comments
==== Revisions Deadline ====
Tricci (OPPO) still don't fully understand the need for additional Time Window input filter for this analytics and prefer to have further discussions on this CR.
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300144 CR Approval 23.503 CR0799 (Rel-18, 'B'): DN Performance Analytics usage in PDTQ policy NTT DOCOMO Rel-18 CC#4: r06 agreed. Revised to S2-2301482. Baseline for S2-2300123, S2-2300774 Tricci <OPPO> proposes to use this CR as the baseline to merge with S2-2300123 (from Ericsson) and S2-2300774 (from Huawei) to have the single stream of discussions for updating the common clauses in TS 23.503.
Belen (Ericsson) provides r01 and comments
Bahador (NTT DOCOMO) replies to Belen (Ericsson) and provides r02
Wang Yuan (Huawei) is ok to merge S2-2300774 into S2-2300144 and provides r03.
Tricci (OPPO) thanks Wang Yuan (Huawei) revision and would like to support the considerations from DoCoMo and Huawei. OPPO would like to cosign this latest revision of the CR. Please OPPO as the supporting company. Many thanks.
Bahador (NTT DOCOMO) replies to Yuan (Huawei) and provides r04
Mirko (Huawei) comments and provides r05.
Bahador (NTT DOCOMO) replies to Mirko (Huawei).
Belen (Ericsson) provides r06
==== Revisions Deadline ====
Tricci (OPPO) responds to Bahador (NTT DOCOMO) based on the past discussions with Belen..
Wang Yuan (Huawei) proposes to go forward with r06 with a word 'may' added and the EN removed (as in late r07), and add Huawei as a cosigner.
Tricci (OPPO) accepts Wang Yuan (Huawei) proposal to go forward with r06 with a word 'may' added and the EN removed (as in late r07).
Belen (Ericsson) is okay with r06, and objects to the proposed additions to add the word 'may' and remove the Editor´s Note.
Asks to POSTPONE the CR if no agreement is reached.
Bahador (NTT DOCOMO) is okay with r06 with a word 'may' added (and keep the Editor´s Note as it is).
Wang Yuan (Huawei) is okay with the proposal proposed by Bahador (NTT DOCOMO).
Belen (Ericsson) is not okay to add 'may' as proposed, wants to keep the EN and would like to remove 'if possible' when it comes to DN Performance
==== Final Comments Deadline ====
Wang Yuan (Huawei) can live with r06 with the proposal proposed by Belen(Ericsson), i.e., not to add 'may', keep the EN and remove 'if possible'.
Bahador (NTT DOCOMO) asks to agree Ericsson's proposal: r06 + not to add 'may', keep the EN and remove 'if possible' (for the DN Performance) in CC#4.
Revised
9.9.2 S2-2301482 CR Approval 23.503 CR0799R1 (Rel-18, 'B'): DN Performance Analytics usage in PDTQ policy NTT DOCOMO, OPPO Rel-18 Revision of S2-2300144r06. Approved Agreed
9.9.2 S2-2300122 CR Approval 23.288 CR0608 (Rel-18, 'B'): Network performance analytics Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.9.2 S2-2300389 CR Approval 23.288 CR0622 (Rel-18, 'F'): Clarification on enhanced Network Performance analytics LG Electronics Rel-18 r01 agreed. Revised to S2-2301581. LaeYoung (LGE) replies to Dongjoo (Nokia).
Dongjoo (Nokia) asks a question for clarification
Dongjoo (Nokia) asks a f/up question for further clarification
LaeYoung (LGE) answers to Dongjoo (Nokia).
Dongjoo (Nokia) provides a suggestion for a revision
LaeYoung (LGE) provides r01.
Dongjoo (Nokia) is fine with r01
Mehrdad (MediaTek Inc.) supports this CR. Please add us as a co-signer.
LaeYoung (LGE) answers to Mehrdad (MediaTek Inc.).
==== Revisions Deadline ====
Tricci (OPPO) thanks LaeYoung and support r01.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301581 CR Approval 23.288 CR0622R1 (Rel-18, 'F'): Clarification on enhanced Network Performance analytics LG Electronics, MediaTek Inc. Rel-18 Revision of S2-2300389r01. Approved Agreed
9.9.2 S2-2300150 CR Approval 23.502 CR3673 (Rel-18, 'B'): AIMLsys: KI#5 Planned Data Transfer with QoS Policy (PDTQ) Negotiation and Activation for future PDU session to support Application AI/ML data transfer OPPO, Oracle Rel-18 Confirm CR Number - CR states 0673! R07 + changes agreed. Revised to S2-2301582. LaeYoung (LGE) comments
Trici (OPPO) thanks LaeYoung (LGE) kind reminder and will provide r01 to remove the text.
LaeYoung (LGE) still sees the text to be removed in r01.
Tricci (OPPO) apologizes to LaeYoung (LGE) for repeated mistake and provides r02.
Dongeun (Samsung) comments
Wang Yuan (Huawei) comments on r02 and provides r03.
Tricci (OPPO) thanks Dongeun (Samsung) comments and provides feedback.
Tricci (OPPO) thanks Wang Yuan (Huawei) and accepts r03. OPPO would like to ask if Wang Yuan (Huawei) would like to cosign since Huawei is one of the original authors with many aspects are from Huawei.
Bahador (NTT DOCOMO) supports r03. Please add NTT DOCOMO as a supporting company.
Tricci (OPPO) responds to Dongeun (Samsung) comments
Tricci (OPPO) provides r04 to address some comments from Dongeun (Samsung) and adds Toyota and NTT DoCoMo as the supporting companies.
Mirko (Huawei) comments.
Tricci (OPPO) thanks Mirko (Huawei) comments and clarifying his concern. OPPO agrees to remove the clause for applying the PDTQ procedure in the CR and provides r05. Please check.
Tricci (OPPO) responds to Dongeun (Samsung) comments and asks Dongeun (Samsung) for clarifications from before making any further update, if needed, It is because some of the Samsung's comments are very unclear.
Tricci (OPPO) provides r06 to address some Dongeun (Samsung) comments
Belen (Ericsson) provides r07, removes those aspects that cannot be agreed, in previous revisions. Objects to previous revisions
==== Revisions Deadline ====
Dongeun (Samsung) suggest to go with r06 + update from Belen.
Tricci (OPPO) thanks Dongeun (Samsung) suggestions and would prefer to use Belen (Ericsson) r07 'minus' the step-16 PDTQ warning 'plus' EN for approval.
Belen (Ericsson) is okay with removing step 16 in PDTQ and objects to add any EN on UE involvement
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301582 CR Approval 23.502 CR3673R1 (Rel-18, 'B'): AIMLsys: KI#5 Planned Data Transfer with QoS Policy (PDTQ) Negotiation and Activation for future PDU session to support Application AI/ML data transfer OPPO, Oracle Rel-18 Revision of S2-2300150r07 + changes. Approved Agreed
9.9.2 - - - Key Issue #6: QoS and Policy enhancements - - Docs:=6 -
9.9.2 S2-2300670 CR Approval 23.501 CR3963 (Rel-18, 'C'): Introducing standard 5QIs for AI/ML Service OPPO Rel-18 Confirm Spec version used - CR states V18.0.0! Postponed To be merged into S2-2300750 (Postponed) Tricci <OPPO> proposes to merge this CR into S2-2300750 (from Samsung) to have a single stream of discussions.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300750 CR Approval 23.501 CR3976 (Rel-18, 'B'): Introducing new 5QIs for AI/ML-based Services Samsung Rel-18 Postponed Tricci <OPPO> proposes to use this CR as the baseline to merge with S2-2300670 (from OPPO) to have a single stream of discussions.
Yang (OPPO) clarifies and provides r01
Belen (Ericsson) thinks that the discussion on whether new 5Qis are needed needs SA1 feedback
Tingyu (Samsung) replies.
LaeYoung (LGE) agrees with Belen (Ericsson) that the discussion on new 5Qis needs SA1 feedback, so proposes to POSTPONE this CR.
Dongjoo (Nokia) shares the same view as Ericsson and LGE.
Juan Zhang (Qualcomm) also agrees to focus on the LS to SA1 first and proposes to postpone the new 5QI definition.
Tingyu (Samsung) is OK to wait for SA1's feedback for further discussion on 5QI
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300824 CR Approval 23.501 CR3989 (Rel-18, 'B'): Support of Group QoS request Samsung Rel-18 r01 agreed. Revised to S2-2301583. CC#4: Postponed Dongeun(Samsung) provides r01
==== Revisions Deadline ====
Tricci (OPPO) proposes to NOTED this CR since we have no agreement.
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2301583 CR Approval 23.501 CR3989R1 (Rel-18, 'B'): Support of Group QoS request Samsung Rel-18 Revision of S2-2300824r01. Approved CC#4: Withdrawn Withdrawn
9.9.2 S2-2300826 CR Approval 23.502 CR3795 (Rel-18, 'B'): Support of Group QoS request Samsung Rel-18 Postponed Tricci <OPPO> has fundamental concern on this CR of which some of the issues have been raised in last meeting and during offline discussions.
Dongeun (Samsung) provide r01 and response to Tricci (OPPO)
Tricci (OPPO) thanks Dongeun (Samsung) kind responses. However, Samsung did not really answer OPPO's questions.
Belen (Ericsson) provides comments, cannot accept r01 or initial revision
Dongeun (Samsung) replies to Belen (Ericsson) and Tricci (OPPO)
Dongeun (Samsung) provides r02
Tricci (OPPO) thanks Dongeun (Samsung) update, but with your latest changes, some technical issues still remain and the claims of the performance improvement becomes less efficient. Hence, OPPO proposes to NOTED this CR.
Dongeun (Samsung) replies to Tricci (OPPO)
Belen (Ericsson) provides comments, thinks that procedures needs more work.
==== Revisions Deadline ====
Dongeun (Samsung) suggest to postpone the CR
Tricci (OPPO) thanks Dongeun (Samsung) feedback and willingness to discuss in technical details to evaluate the technical issues.
Dongeun (Samsung) replies to Tricci(OPPO)
Tricci (OPPO) thanks Dongeun's feedback and would like to respond...
==== Final Comments Deadline ====
Tricci (OPPO) thanks again to Dongeun (Samsung) feedback and provides responses the last time
Postponed
9.9.2 S2-2300827 CR Approval 23.503 CR0861 (Rel-18, 'B'): Support of Group QoS request Samsung Rel-18 Postponed Dongeun(Samsung) provides r01
Tricci (OPPO) objects this CR as-is until the issues for the companion 23.502 CR S2-2300827 are resolved,.
==== Revisions Deadline ====
Dongeun (Samsung) suggest to postpone the CR
==== Final Comments Deadline ====
Postponed
9.9.2 - - - Key Issue #7: 5GS Assistance to Federated Learning Operation - - Docs:=0 -
9.9.2 - - - Key Issue #7: Member Selection Assistance Functionality - - Docs:=16 -
9.9.2 S2-2300149 CR Approval 23.501 CR3827 (Rel-18, 'B'): General Description of AIML Member Selection Assistant Functionality in NEF NTT DOCOMO Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci (OPPO) proposes to merge this CR to LG's S2-2300468.
Bahador (NTT DOCOMO) agrees to merge S2-2300149 to S2-2300468
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300145 CR Approval 23.502 CR3671 (Rel-18, 'B'): AI/ML Operation Member Selection Assistant Functionality NTT DOCOMO Rel-18 Postponed To be merged into S2-2300152 (Postponed) Tricci (OPPO) proposes to merge this CR into OPPO/Sony CR S2-2300152.
Bahador (NTT DOCOMO) agrees to merge S2-2300145 to S2-2300152
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300151 CR Approval 23.501 CR3828 (Rel-18, 'B'): AIMLsys: KI#7 5GC assistance to member selection functionality for application operation OPPO Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci (OPPO) proposes to merge this CR into LG's CR S2-2300468.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300152 CR Approval 23.502 CR3674 (Rel-18, 'B'): AIMLsys: KI#7 NEF services description for assistance to member selection OPPO, Sony Rel-18 Postponed Jingran <OPPO> provides r01 which merge the S2-2300145, S2-2300270, S2-2300469, S2-2300575 and S2-2301290 into S2-2300152.
Tricci <OPPO> proposes to use this CR as the baseline to merge with S2-2300145, S2-2300270, S2-2300469, S2-2300575 and S2-2301290 to have a single stream of discussions to define the Member Selection Assistance Functionality in 23.502.
Vivian <vivo> provides r02 and some comments.
Jingran(OPPO) replies to vivo.
Yingying(CATT) provides comments.
Bahador <NTT DOCOMO> provides comments about 'additional information' and asks for clarifications about clause 4.15.X.2
Dongjoo(Nokia) provides r03.
David (Samsung) provides r04.
Dongjoo (Nokia) questions on r04.
David (Samsung) replies to Nokia.
Jingran (OPPO) provides r05.
Juan Zhang (Qualcomm) provides comments on r05.
Belen (Ericsson) provides r06, objects to all revisions from r05 to initial version.
David (Samsung) provides r07 on top of r06.
Dongjoo (Nokia) provides r08 on top of r07.
David (Samsung) provides r09 on top of r08.
Jaewoo (LGE) provides r10 on top of r09.
Jingran (OPPO) provides r11.
Mehrdad (MediaTek Inc.) comments on all revisions.
Ulises (InterDigital Inc.) gives comments and provides r12
Jingran (OPPO) replies to MediaTek and InterDigital.
Aihua(CMCC) replies and provides r13.
Dongjoo (Nokia) is fine with r13 and would like to co-sign.
Vivian (vivo) provides r14.
Jingran (OPPO) provides r15.
Jaewoo (LGE) provides r16.
Mehrdad (MediaTek Inc.) requests to add MediaTek Inc. as a co-source.
Jingran (OPPO) provides r17.
Ulises Olvera (InterDigital Inc.) requests to add InterDigital Inc. as a co-source.
Belen (Ericsson) provides r18
Jingran (OPPO) provides r19
Belen (Ericsson) provides r10, objects to r19
==== Revisions Deadline ====
Tao(VC) suppose Belen means r20 instead of r10
Jingran(OPPO) confirm the latest version is r20 and is fine with r20.
Juan Zhang (Qualcomm) is fine with r20.
Bahador (NTT DOCOMO) accepts r20 only if clause '4.15.X' in this version is converted back to 'Annex X' as it was in r19; this change was happened in r19 -> r20 without discussion in the email thread.
Belen (Ericsson) cannot accept NTT DOCOMO proposal to revert it the new procedure into an Annex, Ericsson objects to such a proposal.
Jingran (OPPO) replies to NTT DOCOMO and provides r21 to the draft folder.
David (Samsung) comments on r20 and r21.
Mehrdad (MediaTek Inc.) is Ok with r20.
Jingran (OPPO) objects the r20. The control flow for AF direct communication with 5GC for member selection support is not a normative description. It is just an informative example, therefore it cannot belong to part of the normative session of the TS. This totally violates the 3GPP drafting rule. The informative example can only go to informative Annex.
Aihua(CMCC) is fine with r20.
Belen (Ericsson) corrects previous statement, we cannot accept r20, suggests r8.
Mehrdad (MediaTek Inc.) requests status update on this CR. We are also OK with r08. Is r08 agreeable by all parties?
Jaewoo (LGE) propose r21 + remove filters in the table: 'UE historical location', 'UE direction', 'UE separation distance', 'MA PDU Session'.
Mehrdad (MediaTek Inc.) clarifies to LGE there is no r21. The latest revision before deadline is r20. Any changes should be clarified based on r20 or past revisions.
Tricci (OPPO) responds to Mehrdad (MediaTek Inc.) with sincere considerations of many companies perspectives.
David (Samsung) suggests to postpone this CR.
Jaewoo (LGE) propose r20 + change '4.15.X AI/ML Member selection at the AF' to 'Annex X (Informative)' + remove filters in the table: 'UE historical location', 'UE direction', 'UE separation distance', 'MA PDU Session'.
Mehrdad (MediaTek Inc.) also suggests to postpone this CR in light of lack of agreement
Belen (Ericsson) ok to postpone.
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300269 CR Approval 23.501 CR3861 (Rel-18, 'B'): KI#7 - 23.501 CR for member selection Nokia, Nokia Shanghai Bell, SK Telecom Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci <OPPO> proposes to merge this CR into LG's S2-2300468.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300270 CR Approval 23.502 CR3693 (Rel-18, 'B'): KI#7 - 23.502 CR for member selection Nokia, Nokia Shanghai Bell, SK Telecom Rel-18 Postponed To be merged into S2-2300152 (Postponed) Tricci <OPPO> proposes to merge this CR into OPPO/Sony CR S2-2300152.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300468 CR Approval 23.501 CR3910 (Rel-18, 'B'): Assistance to Member Selection Functionality for Application Operation LG Electronics Rel-18 r15 agreed. Revised to S2-2301584, merging S2-2300149, S2-2300151, S2-2300269, S2-2300579, S2-2301201 and S2-2301287 Baseline for S2-2300149, S2-2300151, S2-2300269, S2-2300579, S2-2301201, S2-2301287 Jaewoo (LGE) provides r02 and provides comments on r01.
Dongjoo (Nokia) provides r01.
Tricci <OPPO> proposes to use this CR from LG as the baseline to merge with other similar CRs, S2-2300149, S2-2300151, S2-2300269, S2-2301201 and S3-2301287 in order to have a single stream discussions to converge the update to 23.501 to provide highlevel descriptions for the Member Selection Functionality for application operation. Thanks.
Jingran (OPPO) provides r03.
Jaewoo (LGE) provides r04.
Vivian (vivo) provides r05.
David (Samsung) provides r06.
Dongjoo (Nokia) provides r07.
David (Samsung) comments on r07.
Dongjoo (Nokia) replies to David (Samsung).
Ellen (Google) provides r08 addressing untrusted and trusted AF
Tricci (OPPO) has trouble to understand the logic from Ellen (Google) for untrusted and trusted AF and would like to ask Google for clarifications. OPPO cannot accept r08 from Google. Sorry...
Ellen (Google) replies to Tricci (OPPO) and disagree to allow AF in trusted domain for accessing NEF directly
Tricci (OPPO) thanks Ellen (Google) reply, how Google does not really answer OPPO's questions and OPPO would like to ask for further clarifications.
Dongjoo (Nokia) shares the same view as Tricci (OPPO)
Bahador (NTT DOCOMO) shares the same view as Tricci (OPPO) and Dongjoo (Nokia)
Jingran (OPPO) provides r09.
Jinsook (DISH) confirm that the trusted AF should be allowed to use NEF service. It's operator choice.
Ellen (Google) thanks feedback and clarification on trusted AF (fine for way forward)
Jianning (Xiaomi) provides questions for clarification on r09
Jingran(OPPO) replies to Xiaomi
Jaewoo (LGE) provides r10.
David (Samsung) provides r11.
Dongjoo (Nokia) can live with the proposed EN so is fine with r11.
Jingran (OPPO) is fine with r11.
Dongjoo (Nokia) also would like to co-sign.
David (Samsung) also would like to co-sign.
Bahador (NTT DOCOMO) provides comments
Jaewoo (LGE) provides r12.
Bahador (NTT DOCOMO) provides r13.
Ulises Olvera (InterDigital Inc.) provides further updates reflected in r14 that has been uploaded, and we also request to be added as a co-source company.
Jaewoo (LGE) thanks to Bahador (NTT DOCOMO) and Ulises Olvera (InterDigital Inc.) and provides r15.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301584 CR Approval 23.501 CR3910R1 (Rel-18, 'B'): Assistance to Member Selection Functionality for Application Operation LG Electronics, OPPO, Toyota, Nokia, Nokia Shanghai Bell, Samsung, InterDigital Rel-18 Revision of S2-2300468r15, merging S2-2300149, S2-2300151, S2-2300269, S2-2300579, S2-2301201 and S2-2301287. Approved Agreed
9.9.2 S2-2300469 CR Approval 23.502 CR3730 (Rel-18, 'B'): Assistance to Member Selection Functionality for Application Operation LG Electronics Rel-18 Postponed To be merged into S2-2300152 (Postponed) Tricci <OPPO> proposes to merge this CR into OPPO/Song CR S2-2300152.
==== Revisions Deadline ====
Jaewoo (LGE) confirms that this CR is merged into S2-2300152.
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300575 CR Approval 23.502 CR3752 (Rel-18, 'B'): UE selection capability supported by NEF Qualcomm Incorporated Rel-18 Postponed To be merged into S2-2300152 (Postponed) Tricci <OPPO> proposes to merge this CR into OPPO/Sony CR S2-2300152.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2300579 CR Approval 23.501 CR3941 (Rel-18, 'B'): UE selection capability supported by NEF Qualcomm Incorporated Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci <OPPO> proposes to merge this CR into LG's CR S2-2300468.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2301201 CR Approval 23.501 CR4090 (Rel-18, 'B'): 5GC support for member selection assistance functionality Google Inc. Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci <OPPO> proposes to merge this CR into LG's S2-2300468.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2301290 CR Approval 23.502 CR3867 (Rel-18, 'B'): NEF enhancement for new member Selection Functionality Xiaomi Rel-18 Postponed To be merged into S2-2300152 (Postponed) Tricci <OPPO> proposes to merge this CR into OPPO/Song CR S2-2300152.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2301287 CR Approval 23.501 CR4104 (Rel-18, 'B'): NEF enhancement for new member Selection Functionality Xiaomi Rel-18 Merged into S2-2301584 Merge into S2-2300468 Tricci <OPPO> proposes to merge this CR into LGE CR S2-2300468.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300446 CR Approval 23.288 CR0629 (Rel-18, 'B'): Procedure for direct member selection assistance to AF China Mobile, MediaTek Inc. Rel-18 Confirm Specification Number - CR states 23.502! Should be 23.502 CR3870. Postponed Wrong spec: it should be 23.502. To be merged into S2-2300152 (Postponed) Tricci (OPPO) sincerely thanks Aihua (CMCC) providing r02. OPPO proposes to merge this CR to S2-2300152 to consolidate the 23.502 descriptions for member selection assistance functionality.
Aihua(CMCC) provides r02.
Tricci (OPPO) thanks and agrees with Jaewoo (LGE) comments and hoping the new revision from CMCC for the merged proposal will come out soon. Thanks.
Tricci (OPPO) objects this CR as-is because the procedure itself has technical fundamental error and also, the rest of the procedures in the control flows can be supported today without this CR. There is no justification to introduce a 'new' for procedure that can be supported already.
Jaewoo (LGE) provides comments.
Zhang (Ericsson) provides r01 and co-sign
Vivian (vivo) provides r03 before this paper is merged with S2-2300152 .
Jingran(OPPO) replies to vivo .
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.9.2 S2-2301299 CR Approval 23.501 CR4109 (Rel-18, 'B'): FL member selection for trusted AF InterDigital, Inc. Rel-18 Noted Tricci <OPPO> proposes to note and to reject this CR because there is no agreement to leverage NWDAF to host the FL member selection functionality regardless the AF is trusted or untrusted. The only agreement of the TR conclusion is to have the NEF to host the member selection functionality. OPPO cannot accept this CR.
Dongjoo (Nokia) objects this contribution with the same view as OPPO.
Mehrdad (MediaTek Inc.) shares similar view as OPPO and Nokia
David (Samsung) agrees with raised objections.
Juan Zhang (Qualcomm) shares the same view to note the CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.9.2 - - - Key Issue #7: Network Analytics Extensions - - Docs:=13 -
9.9.2 S2-2301024 CR Approval 23.288 CR0671 (Rel-18, 'B'): Enhancement of Service Experience Analytics to assist federated learning operation ETRI Rel-18 Revised to S2-2301585. Yingying(CATT) provides comments.
Jingran(OPPO) provides comments.
Tingyu (Samsung) provides comments.
Jihoon (ETRI) replies to the comments.
Tingyu (Samsung) comments
==== Revisions Deadline ====
Jihoon (ETRI) replies to Tingyu (Samsung).
Jihoon (ETRI) asks if we can go with 'r00 + term alignment with S2-2300268'.
Tingyu (Samsung) is OK with adding 'RAN' to the names of the 3 new information elements to align the terms.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301585 CR Approval 23.288 CR0671R1 (Rel-18, 'B'): Enhancement of Service Experience Analytics to assist federated learning operation ETRI Rel-18 Revision of S2-2301024. Approved Agreed
9.9.2 S2-2300109 CR Approval 23.288 CR0555R1 (Rel-18, 'B'): Updates for DN performance Analytics of Group UEs Ericsson Rel-18 Revision of S2-2210268. r02 agreed. Revised to S2-2301586. Tricci <OPPO> suggests to add a note to the DN Service Performance statistics to indicate that such statistics output parameters are more applicable to longer group operation cycle for the given application.
Jaewook(ETRI) provides the comment.
Dongjoo (Nokia) asks a question for clarification.
Tingyu (Samsung) asks for clarification
Zhang (Ericsson) provides r01 and comment
Tingyu (Samsung) provides comments.
Zhang (Ericsson) response to Tingyu (Samsung)
Zhang (Ericsson) provides r02
Tingyu (Samsung) replies to Zhang (Ericsson)
Zhang (Ericsson) response to Tingyu (Samsung) and does not like the strategy
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301586 CR Approval 23.288 CR0555R2 (Rel-18, 'B'): Updates for DN performance Analytics of Group UEs Ericsson Rel-18 Revision of S2-2300109r02. Approved Agreed
9.9.2 S2-2300268 CR Approval 23.288 CR0616 (Rel-18, 'B'): KI#7 - 23.288 CR for adding UE Transmission Latency Performance Analytics Nokia, Nokia Shanghai Bell, OPPO, SK Telecom Rel-18 Check Affected Clauses! r14 agreed. Revised to S2-2301587, merging S2-2301045 and S2-2300752 Baseline for S2-2301045, S2-2300752 Jingran (OPPO) provides comments.
Zhang (Ericsson) ask for clarification
Dongjoo (Nokia) provides r02 for further changes.
Tingyu (Samsung) provides r01 by merging 1045 (from ETRI) and 0752 (from Samsung) into 0268 (from Nokia, OPPO, and SK Telecom).
Jingran (OPPO) reply to Ericsson
Dongjoo (Nokia) provides further feedback to Ericsson
Dongjoo (Nokia) provides more comments.
Jihoon (ETRI) provides comments.
Yingying(CATT) provides comments and provides r03 and co-sign it.
Bahador (NTT DOCOMO) provides comments.
Tingyu (Samsung) comments r04 was uploaded by mistake, please disregard
Tingyu (Samsung) provides comments and r05.
Jingran (OPPO) replies to Samsung
Jingran (OPPO) provides r06
Tingyu (Samsung) replies to OPPO and Nokia and provides r07 with minor changes.
Jihoon (ETRI) provides comments and r08.
Jingran (OPPO) replies to ETRI.
Juan Zhang (Qualcomm) provides comments on r08.
Tingyu (Samsung) replies and provides r09
Dongjoo (Nokia) thanks Tingyu(Samsung) and supports r09
Jingran (OPPO) provides comments on r09.
Tingyu (Samsung) replies to Jingran (OPPO).
Zhang (Ericsson) still have concerns to r09
Mehrdad (MediaTek Inc.) comments on all revisions.
Dongjoo (Nokia) provides feedback and r10
Juan Zhang (Qualcomm) provides r11.
Dongjoo (Nokia) provides r12.
Zhang (Ericsson) response to Dongjoo (Nokia)
Tingyu (Samsung) replies and provides r13
Jaewoo (LGE) provides comments.
Tingyu (Samsung) replies to Jaewoo (LGE)
Dongjoo (Nokia) provides r14.
Jingran (OPPO) is fine with r14.
Jaewoo (LGE) is also fine with r14.
Tingyu (Samsung) is also OK with r14
Costas (Lenovo) provides comments.
Tingyu (Samsung) replies to Zhang (Ericsson) and explains data could be collected from OAM and 5GC NFs.
Zhang (Ericsson) pointed out to have delay performance between UE and application server, NWDAF needs input from AF
==== Revisions Deadline ====
Juan Zhang (Qualcomm) can live with r14 in this meeting.
Zhang (Ericsson) can live with r14
Yingying (CATT) is OK with r14.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301587 CR Approval 23.288 CR0616R1 (Rel-18, 'B'): KI#7 - 23.288 CR for adding UE Transmission Latency Performance Analytics Nokia, Nokia Shanghai Bell, OPPO, SK Telecom, Samsung, CATT, ETRI Rel-18 Revision of S2-2300268r14, merging S2-2301045 and S2-2300752. Approved Agreed
9.9.2 S2-2301045 CR Approval 23.288 CR0672 (Rel-18, 'B'): UE latency performance analytics to assist federated learning operation ETRI Rel-18 Merged into S2-2301587 Merge into S2-2300268, Zhang (Ericsson) suggest to merge the paper into S2-2300268
Jihoon (ETRI) indicates that this CR has been already merged into S2-2300268 and discussed in the email thread.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2300752 CR Approval 23.288 CR0652 (Rel-18, 'B'): UE latency performance analytics Samsung Rel-18 Merged into S2-2301587 Merge into S2-2300268, Zhang (Ericsson) provides comments and suggest to merge the paper into S2-2300268
Tingyu (Samsung) replies and confirm to merge 0752 into S2-2300268
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.9.2 S2-2301104 CR Approval 23.288 CR0677 (Rel-18, 'B'): KI#7 23.288 CR for UE mobility analytics to assist FL operation CATT Rel-18 r05 agreed. Revised to S2-2301588. Tricci <OPPO> asks for clarifications for which TR conclusion and procedures that this CR is based on to propose updating the UE mobility analytics? Also, the proposed change violate the AIMLsys architecture principle to have 5GC aware of the application operation type, i.e. Federated Learning. Finally, there was similar analytics but with different approach adopted by eNA for the similar purpose. Hence, this CR should be NOTED as the way that it is defined.
Yingying <CATT> replies to Tricci <OPPO> and provides r01.
Jingran(OPPO) replies to CATT
Yingying <CATT> replies to OPPO.
Tingyu (Samsung) provides comments.
Jingran (OPPO) replies to Tingyu.
Jingran (OPPO) replies to Yingying.
Jihoon (ETRI) asks questions for clarification.
Juan Zhang (Qualcomm) provides comments
Yingying (CATT) replies to Tingyu (Samsung), Jingran (OPPO), Jihoon (ETRI) and provides r02.
Mehrdad (MediaTek Inc.) comments on r02 and other revisions and wonders how then 5GC is agnostic to AIML operation.
Tingyu (Samsung) comments on r02 and suggests removing 'any UE' and AIML/FL-related descriptions.
Yingying (CATT) replies to Juan(Qualcomm), Mehrdad (MediaTek Inc.) and Tingyu (Samsung) and provides r03,r04.
Jingran (OPPO) provides comments
Mehrdad (MediaTek Inc.) comments on r03 and r04
Yingying (CATT) replies to Jingran (OPPO).
Jingran (OPPO) replies to CATT.
Mehrdad (MediaTek Inc.) can not agree with r03 or r04 and provides r05
Yingying (CATT) thanks Mehrdad for the updated version and agrees with r03,r04 and r05.
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r05.
Tingyu (Samsung) is OK with r05 and would like to co-sign.
==== Final Comments Deadline ====
Revised
9.9.2 S2-2301588 CR Approval 23.288 CR0677R1 (Rel-18, 'B'): KI#7 23.288 CR for UE mobility analytics to assist FL operation CATT, Samsung Rel-18 Revision of S2-2301104r05. Approved Agreed
9.9.2 S2-2300777 CR Approval 23.501 CR3979 (Rel-18, 'B'): NWDAF supports FL member selection Huawei, HiSilicon Rel-18 Noted Tricci <OPPO> proposes to NOTED this CR since it is inconsistent with the TR conclusion which has rejected the NWDAF to host the Member Selection Assistance Functionalities. 5GC shall NOT have two different NFs to support the 'same' functionalities.
Dongjoo (Nokia) objects this contribution with the same view as OPPO.
David (Samsung) objects this contribution based on the conclusion and SoH result reached at SA2#154.
Mehrdad (MediaTek Inc.) shares similar view as OPPO, Samsung and Nokia
Wang Yuan (Huawei) thanks for all the comments and suggests to focus on the discussion in the thread of S2-2300776.
Juan Zhang (Qualcomm) shares similar view with others and proposes to note the CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.9.2 S2-2300776 CR Approval 23.288 CR0657 (Rel-18, 'B'): NWDAF supports FL member selection Huawei, HiSilicon Rel-18 Noted Tricci <OPPO> proposes to NOTED this CR during the inaccurate reason of change. The decision to select NEF to host the Member Selection Assistance functionality is independent of whether the AF is trusted or untrusted. NWDAF has been proposed to host the functionality and has been voted out. It is not acceptable to have two different 5GC NF to implement the overlapped functionalities. OPPO strongly objects this CR for any revision.
Dongjoo (Nokia) objects this contribution with the same view as OPPO.
David (Samsung) objects this contribution based on the conclusion and SoH result reached at SA2#154.
Mehrdad (MediaTek Inc.) shares similar view as OPPO, Samsung and Nokia
Wang Yuan (Huawei) replies to Tricci (OPPO), Dongjoo (Nokia), David (Samsung) and Mehrdad (MediaTek).
Bahador (NTT DOCOMO) provides comments
Mehrdad (MediaTek Inc.) comments
Juan Zhang (Qualcomm) also proposes to note the CR.
Aihua(CMCC) replies and comments.
Tricci (OPPO) confused by Aihua(CMCC) latest comments and ask for clarifications.
Dongjoo (Nokia) provides feedback on Aihua(CMCC)'s comments
==== Revisions Deadline ====
Wang Yuan (Huawei) replies to Aihua(CMCC) and Tricci(OPPO).
Juan Zhang (Qualcomm) proposes to note the CR and end the solution for Rel-18.
Wang Yuan (Huawei) is OK to note this CR.
==== Final Comments Deadline ====
Noted
9.9.2 S2-2301250 CR Approval 23.288 CR0687 (Rel-18, 'B'): FL member selection for Trusted AF InterDigital, Inc. Rel-18 Noted Tricci <OPPO> proposes to NOTED this CR during the inaccurate reason of change. The decision to select NEF to host the Member Selection Assistance functionality is independent of whether the AF is trusted or untrusted. NWDAF has been proposed to host the functionality and has been voted out. It is not acceptable to have two different 5GC NFs to implement the overlapped functionalities. OPPO strongly objects this CR for any revision.
Dongjoo (Nokia) objects this contribution with the same view as OPPO.
Tingyu (Samsung) objects to this contribution based on the conclusion and shares similar views as OPPO and Nokia.
Ulises (InterDigital Inc.) replies to Oppo (Tricci) agrees to note to avoid fruitless discussions on TR conclusion agreements, but we want to emphasize that the UE member selection functionality can only be provided by 5GC if a NEF supporting this capability is deployed, otherwise NEF changes wouldn't be warranted.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.9.2 - - - Key Issue #7: Misc - - Docs:=1 -
9.9.2 S2-2301103 CR Approval 23.503 CR0884 (Rel-18, 'B'): KI#7 Performance Monitoring Exposure CATT Rel-18 Noted Tricci (OPPO) has more fundamental question that what was asked by Jaewook(ETRI) for this CR.
Jaewook(ETRI) provides the comment.
Dongjoo (Nokia) asks further questions.
Yingying <CATT> replies to ETRI and OPPO.
Jaewook <ETRI> replies to Yingying <CATT>.
Yingying (CATT) replies to Dongjoo (Nokia) and provides r01.
Dongjoo (Nokia) asks for another revision.
Tricci (OPPO) very much confused by this CR and needs more clarifications. OPPO rejects this CR as-is.
Yingying (CATT) replies to Dongjoo (Nokia), Tricci (OPPO), Jaewook (ETRI) and provides r02.
Belen (Ericsson) provides r03, objects to r02, r01 and initial revision
Tricci (OPPO) shares the same concern as Belen and proposes to NOTED this CR after the changes from Belen (Ericsson) with r03. It is practically almost nothing left. What would be good use for this CR?
Yingying (CATT) replies to Belen (Ericsson) and Tricci (OPPO).
Tricci (OPPO) thanks Yingying (CATT) further clarification and can live with the latest update with further clean-up in the next revision. CATT needs to clean-up cover page of the CR for the reason of changes.
Yingying (CATT) replies Tricci (OPPO) and provides r04.
Jaewook (ETRI) is fine with r04 and requests the ETRI's cosign.
Tingyu (Samsung) provides r05 with minor correction
Yingying (CATT) thanks Tingyu for the updated version, welcomes ETRI to co-sign, and agrees with r05.
==== Revisions Deadline ====
Mirko (Huawei) objects to this CR as the additions are not necessary.
==== Final Comments Deadline ====
Yingying (CATT) replies to Mirko (Huawei) and requests withdrawal of the objection.
Noted
9.10.1 - - - Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) - - Docs:=0 -
9.10.2 - - - 5G multicast-broadcast services Phase 2 (5MBS_Ph2) - - Docs:=43 -
9.10.2 - - - TR conclusion update - - Docs:=2 -
9.10.2 S2-2300166 DISCUSSION Discussion UE-CN state synchronisation in RRC_INACTIVE state. Qualcomm Incorporated Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.10.2 S2-2300167 CR Approval 23.700-47 CR0001 (Rel-18, 'C'): UE-CN state synchronisation in RRC_INACTIVE state Qualcomm Incorporated Rel-18 Noted zhendong (ZTE) proposes the comments.
Judy (Ericsson) shares the view from LiMeng (Huawei).
LiMeng (Huawei) comments that this is a new solution, and it belongs to agenda 9.10.1 that is not included in the agenda in this meeting.
Haris(Qualcomm) responds
Thomas (Nokia) also suggest noting this contribution.
Xiaoyan (CATT) support discussing the issues and solutions raised in this contributions.
Fenqin (Huawei) propose to note this paper.
Judy (Ericsson) comments and also propose to note this paper.
Haris(Qualcomm) responds to comments
==== Revisions Deadline ====
Judy (Ericsson) responds to Haris(Qualcomm), and objects to this paper for the sake of chairman's note
Fenqin (Huawei) responds to Haris(Qualcomm) and propose to Note this paper
==== Final Comments Deadline ====
Noted
9.10.2 - - - General - - Docs:=1 -
9.10.2 S2-2300441 CR Approval 23.247 CR0146R3 (Rel-18, 'B'): Update the scope of TS 23.247 China Mobile, KPN Rel-18 Revision of S2-2211303. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.10.2 - - - KI#1: Reception in RRC_INACTIVE - - Docs:=22 -
9.10.2 S2-2300060 LS In Action LS from RAN WG3: Reply LS on the re-establishment of the MBS context during mobility registration update or service request procedure RAN WG3 (R3-226922) Rel-18 Noted LiMeng (Huawei) suggests that we mark this LS as noted. Noted
9.10.2 S2-2300177 CR Approval 23.247 CR0149 (Rel-18, 'B'): Support of MBS multicast reception by UEs in RRC_INACTIVE state Nokia, Nokia Shanghai-Bell Rel-18 r11 agreed. Revised to S2-2301589, merging S2-2300685 and S2-2301165 LiMeng (Huawei) suggests to use this document as the basis for recording the enhancements on the procedures. And other contents can be merged into other documents.
Haris(Qualcomm) provides r01
Fenqin (Huawei) provides comments
Thomas(Nokia) provides r02
Fenqin (Huawei) provides r03
Judy (Ericsson) provides r05 based on r03
Haris(Qualcomm) provides r06
Fenqin(Huawei) provides r07
Judy (Ericsson) provides r08
Thomas(Nokia) is fine with r07
Haris(Qualcomm) is not OK with r07 and asks question
Thomas(Nokia) provides r09
Thomas (Nokia) support the concerns oh Harris against r08
Haris(Qualcomm) asks question on UEs traffic pattern and comments
Judy (Ericsson) provides r10
zhendong (ZTE) provides r11.
Thomas(Nokia) provides r12.
==== Revisions Deadline ====
Fenqin(Huawei) provides comments.
Thomas(Nokia) replies to Fenqin.
Haris(Qualcomm) objects to r12, possibly ok with r11
Judy (Ericsson) accepts r05, r06, r08, r10 & r11, objects to other revisions (including r00)
Fenqin(Huawei) replies to Thomas.
Thomas (Nokia) suggest agreeing r11, objects to r05, r06, r08, r10
Fenqin(Huawei) accept r07,r03 and live with r11, and object to other version.
Judy (Ericsson) suggests agreeing r11
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301589 CR Approval 23.247 CR0149R1 (Rel-18, 'B'): Support of MBS multicast reception by UEs in RRC_INACTIVE state Nokia, Nokia Shanghai-Bell, Huawei, ZTE, Ericsson Rel-18 Revision of S2-2300177r11, merging S2-2300685 and S2-2301165. Approved Agreed
9.10.2 S2-2300178 CR Approval 23.502 CR3680 (Rel-18, 'B'): Support of MBS multicast reception by UEs in RRC_INACTIVE state Nokia, Nokia Shanghai-Bell Rel-18 Merged into S2-2301591 LiMeng (Huawei) suggests to use S2-2300330 as the basis for further discussion.
Thomas (Nokia) agrees to merge this CR into S2-2300330.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2300329 CR Approval 23.247 CR0159 (Rel-18, 'B'): Support RRC_INACTIVE UE receiving multicast MBS data Ericsson Rel-18 r09 agreed. Revised to S2-2301590, merging S2-2300683 and S2-2301163 Judy (Ericsson) provides r01 following the proposal from the rapporteur LiMeng (Huawei)
LiMeng (Huawei) suggests to use this document as the basis for recording the enhancements on Subscription to multicast /AF provisioning multicast MBS Session.
Thomas (Nokia) provides r02)
Judy (Ericsson) comments on r02
Thomas(Nokia) replies to Judy
zhendong (ZTE) provides r03.
Judy (Ericsson) responds and provides r04
zhendong (ZTE) provides response.
Thomas (Nokia) provides r05 and objects against r04
Haris(Qualcomm) comments on r05
zhendong (ZTE) provides comments.
Thomas(Nokia) replies to Haris(Qualcomm)
Thomas (Nokia) provides r06
Haris(Qualcomm) responds
Fenqin(Huawei) provides r07
Fenqin(Huawei) give comments
Judy (Ericsson) comments and provides r08
Fenqin (Huawei) provides feedbacks
Fenqin (Huawei) comments and provides r10
Thomas (Nokia) provides r09
==== Revisions Deadline ====
Xiaoyan (CATT) would like to co-sign.
Judy (Ericsson) thanks Xiaoyan (CATT) for support
Judy (Ericsson) accepts r01, r04 & r08, objects to other revisions (including r00)
Haris(Qualcomm) can live with r10 for this meeting but descriptions require improvements
Thomas(Nokia) objects to r01, r04 & r08 and r10
Ask Judy if r09 + ENs could be a way forward.
Fenqin(Huawei) can accept r07, r10 and object to other version.
Thomas(Nokia) suggests r9 + ENs
In Clause 6.4.2
Editor´s note: The description of UE level MBS Assistance information needs improvements.
In Clause 7.2.9a:
Editor´s note: The description of UE level MBS Assistance information needs improvements.
Thomas(Nokia) can live with r10 + ENs
In Clause 6.4.2
Editor´s note: The description of UE level MBS Assistance information needs improvements.
In Clause 7.2.9a:
Editor´s note: The description of UE list MBS Assistance information needs improvements.
Judy (Ericsson) can live with Thomas(Nokia)'s suggestion, i.e. 'r09 + ENs in clauses 6.4.2 and 7.2.9a
Editor´s note: The description of UE level MBS Assistance information needs improvements'
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301590 CR Approval 23.247 CR0159R1 (Rel-18, 'B'): Support RRC_INACTIVE UE receiving multicast MBS data Ericsson, Nokia, Nokia Shanghai-Bell, ZTE, CATT Rel-18 Revision of S2-2300329r09, merging S2-2300683 and S2-2301163. Approved Agreed
9.10.2 S2-2300330 CR Approval 23.502 CR3705 (Rel-18, 'B'): RRC_INACTIVE UE receiving multicast MBS data, provisioning UE level MBS assistance information Ericsson Rel-18 r02 agreed. Revised to S2-2301591, merging S2-2300178 Thomas (Nokia) provides r01
Judy (Ericsson) comments and provides r02
Thomas (Nokia) accepts r02
==== Revisions Deadline ====
Fenqin (Huawei) provides a comments
Haris(Qualcomm) can live with r02 for now but further work is needed before being approved by SA plenary
Judy (Ericsson) responds to Haris(Qualcomm)
Fenqin (Huawei) provides comments
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301591 CR Approval 23.502 CR3705R1 (Rel-18, 'B'): RRC_INACTIVE UE receiving multicast MBS data, provisioning UE level MBS assistance information Ericsson, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300330r02, merging S2-2300178. Approved Agreed
9.10.2 S2-2300648 CR Approval 23.247 CR0167 (Rel-18, 'B'): Mobility of multicast MBS service for the UE in RRC_INACTIVE state China Mobile Rel-18 Merged into S2-2301592 LiMeng (Huawei) asks for clarification.
Aihua (China Mobile) responds to LiMeng (Huawei).
Judy (Ericsson) comments and proposes to merge this paper to 0656
zhendong (ZTE) share the similar view.
Aihua (China Mobile) agrees to merge this paper to 0656.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2300656 CR Approval 23.247 CR0168 (Rel-18, 'B'): Support of RRC Inactive state reception for MBS session Huawei, HiSilicon Rel-18 r12 agreed. Revised to S2-2301592, merging S2-2300648 and S2-2301162 LiMeng (Huawei) suggests to use this document as the basis for the general description of RRC_INACTIVE.
Fenqin (Huawei) provides r01
Haris(Qualcomm) provides r02
Thomas(Nokia) provides r03
Fenqin(Huawei) provides feedback.
Judy (Ericsson) prefer to keep 'UE-level MBS assistance information' for now and comments that r03 announced is not available on server yet
Fenqin (Huawei) provides r04
zhendong (ZTE) provides r05.
Judy (Ericsson) comment and provides r06
Haris(Qualcomm) provides r07
Fenqin (Huawei) provides r08
Judy (Ericsson) provides r09
Fenqin (Huawei) provides r10
zhendong (ZTE) provides r11 on top of r09.
Judy (Ericsson) comments to r10
Fenqin (Huawei) provides r12
==== Revisions Deadline ====
Xiaoyan (CATT) would like to co-sign.
Judy (Ericsson) accepts r06, r07, r09& r11, objects to other revisions (including r00).
Fenqin (Huawei) suggest to go with r12 + following two changes:
1. EDITOR'S NOTE: Whether the MBS assistance information need directly mention the RRC state is FFS.
2. Replace
'The joined UEs in RRC Inactive state in cells where the MBS session is delivered allowing RRC-inactive reception is possible to remain in RRC_ INACTIVE state to receive the MBS session data'
-->' The joined UEs in RRC_INACTIVE state in the cells where the RRC_INACTIVE UE is allowed to receive MBS data may be able to stay in RRC_INACTIVE and receive MBS Session data'
Judy (Ericsson) is fine with Fenqin (Huawei)'s change
Thomas(Nokia) objects to r06, r07, r09& r11
Thomas (Nokia) is fine with agreeing r12 + changes suggested by Fenqin (Huawei)
Haris(Qualcomm) objects to r11. Can accept post-revision deadline proposal by Fenqin (r13)
zhendong (ZTE) is fine with fenqin proposal, r12 + 2 changes suggested by Fenqin
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301592 CR Approval 23.247 CR0168R1 (Rel-18, 'B'): Support of RRC Inactive state reception for MBS session Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, ZTE, CATT, Ericsson Rel-18 Revision of S2-2300656r12, merging S2-2300648 and S2-2301162. Approved Agreed
9.10.2 S2-2300682 CR Approval 23.247 CR0171 (Rel-18, 'B'): KI#1, adding RRC inactive network functionality of NF description ZTE Rel-18 r03 agreed. Revised to S2-2301593. Judy (Ericsson) provides r01
Thomas (Nokia) provides r02, objects against r01
LiMeng (Huawei) provides r03
==== Revisions Deadline ====
Judy (Ericsson) accepts r01, objects to other revisions (including r00)
Haris(Qualcomm) can live with r03 as basis for further work, but requires updates: typo (assitance->assistance), UE description looks like MBS is supported only in RRC_INACTIVE
Thomas(Nokia) objects against r01
Suggest agreeing r03 + removing changes in Clauses 5.3.2.9 and 5.3.2.8
Judy (Ericsson) can live with Thomas(Nokia)' proposal, i.e. 'r03 + removing changes in Clauses 5.3.2.9 and 5.3.2.8'
LiMeng (Huawei) is fine with the proposal 'r03 + removing changes in Clauses 5.3.2.9 and 5.3.2.8'.
zhendong (ZTE) is fine with the proposal 'r03 + removing changes in Clauses 5.3.2.9 and 5.3.2.8'
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301593 CR Approval 23.247 CR0171R1 (Rel-18, 'B'): KI#1, adding RRC inactive network functionality of NF description ZTE, Ericsson, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300682r03. Approved Agreed
9.10.2 S2-2300683 CR Approval 23.247 CR0172 (Rel-18, 'B'): KI#1, adding RRC inactive related subscription and parameters provisionning ZTE Rel-18 Merged into S2-2301590 LiMeng (Huawei) suggests to merge this document into S2-2300329.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2300684 CR Approval 23.247 CR0173 (Rel-18, 'B'): KI#1, adding session management enhancement for the RRC inactive reception ZTE Rel-18 Postponed Judy (Ericsson) comments
zhendong (ZTE) proposes the response.
LiMeng (Huawei) proposes the response.
Thomas(Nokia) suggest considering this CR merged into S2-2300177
Fenqin (Huawei) give comments
zhendong (ZTE) is fine to postpone this CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.10.2 S2-2300685 CR Approval 23.247 CR0174 (Rel-18, 'B'): KI#1, adding activation for the RRC inactive reception ZTE Rel-18 Merged into S2-2301589 LiMeng (Huawei) suggests to merge this document into S2-2300177.
zhendong (ZTE) is fine with merging proposal.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2300686 CR Approval 23.247 CR0175 (Rel-18, 'B'): KI#1, adding mobility support for the RRC inactive reception ZTE Rel-18 Merged into S2-2301594 LiMeng (Huawei) suggests to merge this document into S2-2301164.
zhendong (ZTE) is fine with merging proposal.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2301162 CR Approval 23.247 CR0177 (Rel-18, 'B'): Multicast MBS Session reception by UEs in RRC Inactive state CATT Rel-18 Merged into S2-2301592 LiMeng (Huawei) suggests to merge this document into S2-2300656.
Thomas (Nokia) comments that this document should be merged to S2-2300656 according to rapporteur proposal.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2301164 CR Approval 23.247 CR0179 (Rel-18, 'B'): Mobility procedures for UEs receiving multicast MBS session data in RRC Inactive state CATT Rel-18 r12 agreed. Revised to S2-2301594, merging S2-2300686 Thomas (Nokia) raises concerns about RAN dependencies of CR
Xiaoyan (CATT) provides r01.
Thomas(Nokia) suggest postponing the CR.
Xiaoyan (CATT) provides r02 and points out there is no justification for postponing this CR.
Judy (Ericsson) provides r03 and propose to proceed with the content that is stable.
Fenqin (Huawei) provides r04.
Haris(Qualcomm) comments
Thomas (Nokia) replies to Xiaoyan to further explain his concerns
Xiaoyan provides r05 and thanks to the supports from Judy (Ericsson) and Fenqin (Huawei).
Xiaoyan (CATT) clarifies to Thomas (Nokia).
Xiaoyan (CATT) provides r06.
Fenqin(Huawei) provides r07
Thomas(Nokia) provides r08
Xiaoyan (CATT) provides r09.
Xiaoyan (CATT) provides r10.
Judy (Ericsson) provides r11
Xiaoyan (CATT) provides comments to r11
Haris(Qualcomm) asks question on one aspect
Xiaoyan (CATT) replies to Haris(Qualcomm).
Haris(Qualcomm) cannot accept 'SMF may send the MBS assistance information in the MBS related information to the target NG-RAN via the AMF' any revisions including this text
LiMeng (Huawei) clarifies
Haris(Qualcomm) provides r12
Xiaoyan (CATT) provides further clarification to Haris.
Xiaoyan (CATT) provides r14.
Xiaoyan (CATT) provides r13.
==== Revisions Deadline ====
Xiaoyan (CATT) propose possible modification on top of r10, to address Haris' comment.
Judy (Ericsson) responds to Xiaoyan (CATT)
Xiaoyan (CATT) replies to Judy (Ericsson).
Xiaoyan (CATT) responds to Judy (Ericsson)
Haris(Qualcomm) objects to r14. Can only accept r12
Fenqin(Huawei) can live with r12 and do some further work next time
Xiaoyan (CATT) thanks the support of Fenqin(Huawei) and can live with r12.
Judy (Ericsson) responds to Xiaoyan (CATT), can accept r12, request to add Ericsson as co-source.
Xiaoyan (CATT) thanks to Judy (Ericsson) for the support.
zhendong (ZTE) can accept r12, and request to add ZTE as co-signer.
Xiaoyan (CATT) thanks zhendong (ZTE) for cosigning.
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301594 CR Approval 23.247 CR0179R1 (Rel-18, 'B'): Mobility procedures for UEs receiving multicast MBS session data in RRC Inactive state CATT, Huawei, HiSilicon, Ericsson, ZTE Rel-18 Revision of S2-2301164r12, merging S2-2300686. Approved Agreed
9.10.2 S2-2301165 CR Approval 23.247 CR0180 (Rel-18, 'B'): MBS session activation and deactivation procedures for UEs in RRC Inactive state CATT Rel-18 Merged into S2-2301589 LiMeng (Huawei) suggests to merge this document into S2-2300177.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 S2-2301163 CR Approval 23.247 CR0178 (Rel-18, 'B'): Subscription data with UE level MBS assistance information CATT Rel-18 Merged into S2-2301590 LiMeng (Huawei) suggests to merge this document into S2-2300329.
Thomas (Nokia) to merge into S2-2300329 following the rapporteur´s proposals
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.10.2 - - - KI#2: MOCN RAN sharing - - Docs:=6 -
9.10.2 S2-2300046 LS In Information LS from RAN WG2: Reply LS on resource efficiency for MBS reception in RAN sharing scenario RAN WG2 (R2-2213109) Rel-18 Noted LiMeng (Huawei) suggests to mark this document as noted.
Judy (Ericsson) supports to mark the LS as noted as there is no action expected from SA2.
Noted
9.10.2 S2-2300331 CR Approval 23.247 CR0160 (Rel-18, 'B'): Introducing functionality of resource efficiency in MOCN Network Sharing Ericsson Rel-18 r05 agreed. Revised to S2-2301453. Judy (Ericsson) provides r01 following the proposal from rapporteur LiMeng (Huawei)
LiMeng (Huawei) suggests to use this document as the basis for General parts, services, and the procedure of Broadcast MBS Session Transport in Network Sharing.
Thomas (Nokia) provides r02
Judy (Ericsson) comments and provide r03
Thomas(Nokia) provides r04
zhendong (ZTE) provides r05.
==== Revisions Deadline ====
Judy (Ericsson) accepts r01 & r03, objects to r02/r04/r05. r00 is not valid anymore after rapporter's merging proposal.
LiMeng (Huawei) can accept r03-r05.
Thomas(Nokia) objects to r00, r01 and r03
Suggest agreeing r05 + change Title of Clause 7.3.X to
Transport Change for multiple broadcast MBS Sessions via different CNs to deliver the same content during network sharing
Judy (Ericsson) responds to Thomas(Nokia)
LiMeng (Huawei) is fine with the proposal of
'agreeing r05 + change Title of Clause 7.3.X to
Transport Change for multiple broadcast MBS Sessions via different CNs to deliver the same content during network sharing'
Judy (Ericsson) agreeing r05 + change Title of Clause 7.3.X to
Transport Change for resource sharing across broadcast MBS Sessions in network sharing
Thomas (Nokia) can accept r05 + change Title of Clause 7.3.X to
Transport Change for resource sharing across broadcast MBS Sessions in network sharing
+ editors note term 'Transport Change for resource sharing across broadcast MBS Sessions in network sharing' is ffs
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301453 CR Approval 23.247 CR0160R1 (Rel-18, 'B'): Introducing functionality of resource efficiency in MOCN Network Sharing Ericsson, ZTE, Samsung Rel-18 Revision of S2-2300331r05. Approved Agreed
9.10.2 S2-2300590 CR Approval 23.247 CR0165 (Rel-18, 'B'): On resource efficiency for MBS reception in RAN sharing scenario Huawei, HiSilicon Rel-18 Postponed LiMeng (Huawei) suggests to use this document as the basis for all procedure changes except for Broadcast MBS Session Transport message.
Haris(Qualcomm) proposes r01
Thomas(Nokia) proposes r02
LiMeng (Huawei) provides r03 and thanks Haris (Qualcomm) and Thomas (Nokia) for the revision. Fine with r01 and comments to r02.
Youngkyo(Samsung) requests more clarification on MBS session establishment .
Judy (Ericsson) comments and provides r04 (updating existing clauses) and r05 (adding new clauses for enhancement to support network sharing)
Thomas Nokia provides r06 based on r03, comments against r04 and r05
Judy (Ericsson) responds to Thomas (Nokia) that r06 missed impact to a number of steps which are captured in r04 but are ignored. r06 is not agreeable to us.
Thomas(Nokia) replies to Judy
Thomas (Nokia) provides r07
Haris(Qualcomm) provides r08
Judy (Ericsson) comments that impact to steps are still missing in r06, r07 & r08 and propose to go for the approach of new sub-clause as in r05
LiMeng (Huawei) considers having a separated clause or not is a matter of taste.
Thomas (Nokia) objects against r05 and asks Judy to provide a revision if something is missing
Judy (Ericsson) comment: Thomas (Nokia) ignored the aspects in r04 when providing his r06, but now ask to make revision to add the aspects in r04 that he ignored. I find this request unfair.
Thomas(Nokia) replies that he provided r07 to incorporate r04 changes, so r04 was not ignored..
==== Revisions Deadline ====
Thomas(Nokia) objects against r04.
Judy (Ericsson) asks Thomas(Nokia) to be specific on the comments
Tao(VC) check r03 agreeable or no agreeable revision
Thomas (Nokia) replies to Judy
Suggests agreeing r08 + changes
Changes to be announced later, bur a first proposal is in late r09
Judy (Ericsson) would like to point out that Thomas (Nokia)'s comment on terminology is not based on the fact. r08 does not meet the criteria 'minor revision' for cc. Cannot agree to r08. Explained and more comments.
Judy (Ericsson) responds to LiMeng (Huawei) that having separated clauses or not is more than a matter of taste due to the level of impact
Judy (Ericsson) corrects: 'r08' in previous comment should be 'post-DL revision=r08+changes'
LiMeng (Huawei) provides r04 + changes (combines r06 and r08).
Judy (Ericsson) accepts r05, objects to other revisions (including r00), propose to postpone this paper
Thomas(Nokia) support to postpone this paper
LiMeng (Huawei) is fine with the postponing suggestion.
Haris(Qualcomm) agrees to postpone
==== Final Comments Deadline ====
Postponed
9.10.2 S2-2300687 CR Approval 23.247 CR0176 (Rel-18, 'B'): KI#2, adding MOCN network sharing for the same content ZTE Rel-18 r07 agreed. Revised to S2-2301595. LiMeng (Huawei) suggests to use this document as the basis for General Introduction, i.e., 6.X only.
zhendong (ZTE) provides r01.
Youngkyo(Samsung) asks a question.
zhendong (ZTE) provides the response.
LiMeng (Huawei) provides the response.
Judy (Ericsson) provides r02 and responds to Youngkyo(Samsung) on SSM as associated session ID
Thomas (Nokia) provides r03
Youngkyo(Samsung) provides r04
Judy (Ericsson) comments and provides r05
zhendong (ZTE) provides r06.
Thomas (Nokia) provides r07.
==== Revisions Deadline ====
Haris(Qualcomm) is ok with r07
Judy (Ericsson) accept only r05 &06, object to other revisions. Can agree r07 + change title of 6.X to 'Resource sharing across broadcast MBS Sessions in network sharing'
Thomas(Nokia) can accept r03, r04 and r07.
Suggest agreeing r07 + change title of 6.X to 'Resource sharing across broadcast MBS Sessions in network sharing'
Editor´s note: Term 'Resource sharing across broadcast MBS Sessions in network sharing' is ffs
Judy (Ericsson) can live with
agreeing r07 + change title of 6.X to 'Resource sharing across broadcast MBS Sessions in network sharing'
Editor´s note: Term 'Resource sharing across broadcast MBS Sessions in network sharing' is ffs
Thomas (Nokia) can alternatively accept r07 + change Title of Clause 6.X to
Multiple broadcast MBS Sessions via different CNs delivering the same content during network sharing
Judy (Ericsson) suggest
agreeing r07 + change title of 6.X to 'Resource sharing across broadcast MBS Sessions in network sharing'
Editor´s note: Term 'Resource sharing across broadcast MBS Sessions in network sharing' is ffs
zhendong (ZTE) provides response.
Thomas(Nokia suggests using Judy´s proposal as way forward.
LiMeng (Huawei) also fine with Judy's proposal.
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301595 CR Approval 23.247 CR0176R1 (Rel-18, 'B'): KI#2, adding MOCN network sharing for the same content ZTE, Ericsson Rel-18 Revision of S2-2300687r07. Approved Agreed
9.10.2 - - - KI#4: Group message delivery - - Docs:=4 -
9.10.2 S2-2300332 CR Approval 23.247 CR0161 (Rel-18, 'C'): Resolve ENs on Group Message Delivery and corrections Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.10.2 S2-2300333 CR Approval 23.501 CR3755R1 (Rel-18, 'C'): Group Message Delivery Ericsson Rel-18 Revision of S2-2210257. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.10.2 S2-2300588 CR Approval 23.247 CR0163 (Rel-18, 'B'): On the Update of Group Message Delivery Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301596. Judy (Ericsson) comments
Thomas (Nokia) comments
LiMeng (Huawei) provides r01.
Judy (Ericsson) comments on r01
LiMeng (Huawei) provides r02
Judy (Ericsson) provides r03
LiMeng (Huawei) is OK with r03, thanks Judy for the update.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301596 CR Approval 23.247 CR0163R1 (Rel-18, 'B'): On the Update of Group Message Delivery Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2300588r03. Approved Agreed
9.10.2 - - - KI#5: Capability-limited UEs - - Docs:=8 -
9.10.2 S2-2300169 CR Approval 23.501 CR3834 (Rel-18, 'C'): MBS service for UE using power saving functions Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2301597. LiMeng (Huawei) suggests that this documents add the reference to TS 23.247 (if necessary) as we did in Rel-17.
Judy (Ericsson) supports the proposal from LiMeng (Huawei) and provides r01
Thomas (Nokia) supports the proposal from LiMeng (Huawei) and provides r02
LiMeng (Huawei) is fine with r02 and provides r03 adding HW as a co-signer.
Judy (Ericsson) provide r04, the only change is to add Ericsson as co-source.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301597 CR Approval 23.501 CR3834R1 (Rel-18, 'B'): MBS service for UE using power saving functions Qualcomm Incorporated, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2300169r04. Approved Agreed
9.10.2 S2-2300179 CR Approval 23.247 CR0150 (Rel-18, 'B'): Coexistence with existing power saving mechanisms for capability-limited devices Nokia, Nokia Shanghai-Bell Rel-18 r07 agreed. Revised to S2-2301598. LiMeng (Huawei) suggests that we use this document as the basis for the service announcement part (i.e., 6.11).
Thomas (Nokia) provides r01 only maintaining changes for the service announcement as suggested in the merging proposals of the rapporteur
LiMeng (Huawei) provides r02 use the term 'UE applying power saving mechanism', and add Huawei, HiSilicon as the supporting company.
Judy (Ericsson) provides r03
Xiaoyan (CATT) provides comments.
Xiaoyan (CATT) raises concerns and suggests postponing this CR.
Judy (Ericsson) provides r04 adding EN for start time and/or a sequence of scheduled activation times
Thomas(Nokia) replies to Xiaoyan
Xiaoyan (CATT) provides r05.
Thomas (Nokia) provides r06.
Judy (Ericsson) comments on r06
Thomas (Nokia) provides r07.
==== Revisions Deadline ====
Judy (Ericsson) requests a revision = r07 + 'add dependent CR0164 in cover sheet' as the added reference 6.X in r07 is introduced in that CR
Thomas (Nokia) is fine with agreeing r07 + 'add dependent CR0164 for TS 23.247 in cover sheet
Haris(Qualcomm) is ok with r07+ suggestions from Judy
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301598 CR Approval 23.247 CR0150R1 (Rel-18, 'B'): Coexistence with existing power saving mechanisms for capability-limited devices Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2300179r07. Approved Agreed
9.10.2 S2-2300334 CR Approval 23.247 CR0162 (Rel-18, 'B'): Support MBS for UEs using power saving functions Ericsson Rel-18 r05 agreed. Revised to S2-2301599. Judy (Ericsson) provides r01 following LiMeng (Huawei)'s proposal and remove 'NR RedCap' from 'NR RedCap UE using power saving function'
LiMeng (Huawei) suggests that we use this document as the basis for the procedure enhancements.
Thomas (Nokia) provides r02 with wording improvements'
LiMeng (Huawei) provides r03
Thomas (Nokia) replies to LiMeng
Judy (Ericsson) provides r04, adding the EN for eDRX > 10.24s as discussed in 0589.
Haris(Qualcomm) provides r05
Judy (Ericsson) is fine with r05
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301599 CR Approval 23.247 CR0162R1 (Rel-18, 'B'): Support MBS for UEs using power saving functions Ericsson, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon Rel-18 Revision of S2-2300334r05. Approved Agreed
9.10.2 S2-2300589 CR Approval 23.247 CR0164 (Rel-18, 'B'): On Clarifying the Scenario Considering the Power Saving Mechanism Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2301600. LiMeng (Huawei) suggests to use this document as the basis for the general description part (i.e., 6.X).
Haris(Qualcomm) provides r01
Thomas(Nokia) provides r02
LiMeng (Huawei) provides r03 based on r02
Judy (Ericsson) comments and provides r04
Haris(Qualcomm) comments on r04
Judy (Ericsson) responds to Haris(Qualcomm) and provide r05 to bring back the EN for eDRX > 10.24s
Judy (Ericsson) comments that r06 does not seem available on the server
Thomas (Nokia) provide r06
==== Revisions Deadline ====
Thomas (Nokia) replies to Judy
Judy (Ericsson) responds to Thomas (Nokia)
Haris(Qualcomm) is ok with r06
Thomas(Nokia) is ok with r06, r03 and r02, objects to other revisions
Judy (Ericsson) cannot accept r06 as is, requesting a revision = r06 + replace 'previously' with 'firstly'
Thomas (Nokia) accepts r06 + replace 'previously' with 'firstly'
==== Final Comments Deadline ====
Revised
9.10.2 S2-2301600 CR Approval 23.247 CR0164R1 (Rel-18, 'B'): On Clarifying the Scenario Considering the Power Saving Mechanism Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson Rel-18 Revision of S2-2300589r06. Approved Agreed
9.11.1 - - - Study on Network Slicing Phase 3 (FS_eNS_Ph3) - - Docs:=0 -
9.11.2 - - - Network Slicing Phase 3 (eNS_Ph3) - - Docs:=65 -
9.11.2 - - - KI#1 - - Docs:=15 -
9.11.2 S2-2300996 DISCUSSION Approval KI#1: Analysis on NSSF determining the Alternative S-NSSAI . Lenovo Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.11.2 S2-2301005 DISCUSSION Agreement KI#1: Further analysis on Alternative S-NSSAI determination and provision to UE. Lenovo Rel-18 Noted Stefano Faccin (Qualcomm) has comments and questions for clarification
==== Revisions Deadline ====
George Foti (Ericsson) proposes to note the CR.
==== Final Comments Deadline ====
Noted
9.11.2 S2-2300293 CR Approval 23.501 CR3867 (Rel-18, 'B'): Change of Network Slice instance for PDU sessions Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301601. Dongeun (Samsung) provides comments
Haiyang (Huawei) provides r01
Jinguo(ZTE) comments
Jinguo(ZTE): the previous comment is for 998, sorry for confusion.
Haiyang (Huawei) comments
Jinguo(ZTE) provides r02
alessio(nokia) provides r03
George (Ericsson) asks question
==== Revisions Deadline ====
George (Ericsson) Ericsson accepts only R02
Jinguo(ZTE) propose to remove the' after indicating to the Ue to establish a new PDU session 'in r03
Myungjune (LGE) supports Jinguo(ZTE) to remove the' after indicating to the Ue to establish a new PDU session 'in r03
Haiyang (Huawei) responses to Myungjune (LGE), also suggests to go with r02
Myungjune (LGE) replies to Haiyang (Huawei)
Jinguo(ZTE) replies to Myungjune (LGE)
Alessio(Nokia) ok with r03 and removal of proposed text. . we can come bac at future meetings with improvements.
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301601 CR Approval 23.501 CR3867R1 (Rel-18, 'B'): Change of Network Slice instance for PDU sessions Huawei, HiSilicon Rel-18 Revision of S2-2300293r03. Approved Agreed
9.11.2 S2-2300997 CR Approval 23.501 CR4036 (Rel-18, 'B'): Introduction of Alternative S-NSSAI replacement determined by NSSF Lenovo Rel-18 Postponed Myungjune (LGE) asks question for clarification.
Genadi (Lenovo) responds to Myungjune (LGE).
Genadi (Lenovo) responds to Xiaowen Sun (vivo) and provides r01.
Myungjune (LGE) comments.
Xiaowen Sun (vivo) provides response and provides r02.
Jinguo(ZTE) comments
Jinguo(ZTE) replies .
Genadi (Lenovo) replies to Jinguo(ZTE) and provides r03 (on top of r02).
Genadi (Lenovo) replies to Xiaowen Sun (vivo) and is fine with r02.
Genadi (Lenovo) replies to Jinguo (ZTE) and Myungjune (LGE).
Xiaowen Sun (vivo) replies to Genadi (Lenovo) and is fine with r03.
Xiaowen Sun (vivo) replies to Genadi (Lenovo).
Dongeun (Samsung) comments
Malla (NTT DOCOMO) comments
Genadi (Lenovo) replies to Malla (NTT DOCOMO).
Peter Hedman (Ericsson) provides comments
==== Revisions Deadline ====
Genadi (Lenovo) provides r04.
Dongeun (Samsung) suggest to postpone CR (as per EN in 1182).
Alessio (Nokia) is ok with r03
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2301182 CR Approval 23.501 CR4083 (Rel-18, 'B'): Support of network slice replacement ZTE, LG Electronics Rel-18 r14 agreed. Revised to S2-2301602. Xiaowen Sun (vivo) provides comments.
Myungjune (LGE) replies to Stefano Faccin (Qualcomm)
Stefano Faccin (Qualcomm) has comments and questions for clarification
Jinguo(ZTE) provides r01
Jinguo(ZTE) replies to Xiaowen(vivo), Stefano(Qualcomm)
Yunjing (CATT) asks a question for clarification.
Iskren (NEC) comments.
George (Ericsson) provides comments
Genadi (Lenovo) responds to Yunjing (CATT).
Haiyang (Huawei) comments.
Jinguo(ZTE) replies to Haiyang (Huawei) and provides r02.
Dongeun (Samsung) comments.
Iskren (NEC)comments.
Ulises Olvera (InterDigital Inc.) has comments and question for clarification
Jinguo(ZTE) provides r03
Malla (NTT DOCOMO) provided comments
Dongeun (Samsung) provide r04
Jinguo(ZTE) replies to Malla (NTT DOCOMO)
Malla (NTT DOCOMO) provided r05
Jinguo(ZTE) provides r06
Genadi (Lenovo) provides comments to r06 and comments to Registration procedure.
Iskren (NEC) provides r07
Iskren (NEC) answers questions from Genadi.
Jinguo(ZTE) provides r08
Iskren (NEC) provides comments
Malla (NTT DOCOMO) provide comment
George (Ericsson) provides r09
Jinguo(ZTE) replies to Iskren(NEC)
Genadi (Lenovo) comments to Iskren (NEC).
Jinguo(ZTE) provides r10
George (Ericsson) provides r11
Peter Hedman (Ericsson) provides r12
Jinguo(ZTE) provides r13
Ulises Olvera (InterDigital Inc.) provides comments and request to add InterDigital as co-sourcing company
Jinguo(ZTE) provides r14
==== Revisions Deadline ====
George (Ericsson) Ericsson OK with r14
Krisztian (Apple) requests to add Apple as co-signing company.
Myungjune (LGE) is ok with r14.
Dongeun (Samsung) is ok with r14
Jinguo(ZTE) replies to Dongeun (Samsung)
Dongeun (Samsung) requests to add Samsung as co-signing company.
Alessio(Nokia) is ok with R14 and would like to be added as supporting company
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301602 CR Approval 23.501 CR4083R1 (Rel-18, 'B'): Support of network slice replacement ZTE, LG Electronics, NEC, Ericsson, Lenovo, InterDigital, Apple,Samsung, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301182r14. Approved Agreed
9.11.2 S2-2300294 CR Approval 23.502 CR3698 (Rel-18, 'B'): Change of Network Slice instance for PDU sessions Huawei, HiSilicon Rel-18 Postponed Jinguo(ZTE) comments
Haiyang (Huawei) responses
Alessio(Nokia) proposes to postpone this to think of whether to document this or just 501 is sufficient.
==== Revisions Deadline ====
George (Ericsson) proposes to postpone
Haiyang (Huawei) suggests to keep this CR.
Malla (NTT DOCOMO) proposes to postpone.
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300570 CR Approval 23.502 CR3749 (Rel-18, 'B'): Providng Alternative S-NSSAI to the UE via Registration and UCU LG Electronics, ZTE Rel-18 Postponed Myungjune (LGE) responds to Xiaowen Sun (vivo).
Xiaowen Sun (vivo) provides comments.
Stefano Faccin (Qualcomm) same comments made on 1105 and 1182 apply.
Myungjune (LGE) replies to George Foti (Ericsson).
George Foti (Ericsson) provides comments
Alessio(Nokia) proposes to postpone this Cr till 501 is stable
==== Revisions Deadline ====
George (Ericsson) proposes to postpone.
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300651 CR Approval 23.502 CR3764 (Rel-18, 'B'): 23.502 Remapping in Initial Registration to Support Network Slice Service Continuity Vivo Rel-18 Postponed Jinguo(ZTE) provides comment and propose to use 997/998 for any NSSF discussion.
Xiaowen (vivo) provides response
alessio(nokia) prop[oses to postpone 502 CRs till 501 is stable
==== Revisions Deadline ====
George (Ericsson) propose to postpone
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300905 CR Approval 23.502 CR3813 (Rel-18, 'B'): Support of slice replacement for new PDU Sessions Samsung Rel-18 Postponed George Foti (Ericsson) provides comments
Dongeun (Samsung) provides r01 and replies to George (Ericsson)
Jinguo(ZTE) comments
alessio(Nokia) asks to postpone this 502 CR
==== Revisions Deadline ====
George (Ericsson) proposes to postpone the CR
Dongeun (Samsung) is ok to postpone the CR
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300912 CR Approval 23.502 CR3814 (Rel-18, 'B'): Support of determining alternative S-NSSAI Samsung Rel-18 Postponed Jinguo(ZTE) comments
Dongeun (Samsung) replies
Malla (NTT DOCOMO) proposes to postpone 502
==== Revisions Deadline ====
George (Ericsson) proposes to postpone.
Dongeun (Samsung) is ok to postpone the CR
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300998 CR Approval 23.502 CR3825 (Rel-18, 'B'): Introduction of Alternative S-NSSAI replacement determined by NSSF Lenovo Rel-18 Postponed Jinguo(ZTE) comments
Dongeun (Samsung) comments
==== Revisions Deadline ====
Jinguo(ZTE) suggests to postpone this 502 CR
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2301183 CR Approval 23.502 CR3852 (Rel-18, 'B'): Support of network slice replacement ZTE, LG Electronics Rel-18 Postponed Dongeun (Samsung) comments
Genadi (Lenovo) provides comments.
Jinguo(ZTE) response to Genadi (Lenovo) and Dongeun (Samsung)
Genadi (Lenovo) provides comments to Jinguo (ZTE).
Jinguo(ZTE) provides r01
George (Ericsson) All 23.502 CRs have to be noted. We don't have an agreement on 23.501 yet.
Iskren (NEC) provides r02.
Malla (NTT DOCOMO) provided comment.
Jinguo(ZTE) replies to Malla (NTT DOCOMO) and Iskren (NEC)
==== Revisions Deadline ====
George (Ericsson) proposes to postpone the CR
Jinguo(ZTE) is ok to postpone all 502 CRs
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300922 CR Approval 23.503 CR0869 (Rel-18, 'B'): Support of determining alternative S-NSSAI Samsung Rel-18 Postponed Jinguo(ZTE) comments
Dongeun (Samsung) replies to Jinguo (ZTE)
==== Revisions Deadline ====
George (Ericsson) proposes to postpone the CR
Dongeun (Samsung) is ok to postpone the CR
==== Final Comments Deadline ====
Postponed
9.11.2 - - - KI#2 - - Docs:=1 -
9.11.2 S2-2301300 CR Approval 23.501 CR4110 (Rel-18, 'B'): Support of slice based SoR mechanism Apple Rel-18 Postponed Dongeun (Samsung) supports to postpone this CR.
Stefano Faccin (Qualcomm) proposes to postpone and wait for CT1 progress
Myungjune (LGE) supports to postpone this CR.
George Foti (Ericsson) would like to postpone the CR until CT1 does the work
Kundan(NEC) thinks that we should at least capture the requirement that steering of roaming based on slicing and captures the detail once CT1 concludes.
Krisztian (Apple) provides r01.
Kundan(NEC) is fine with r01.
Malla (NTT DOCOMO) provides r02 but preferred our spec changes after the CT1 work.
Alessio(nokia) provides r03 which is probably the stable state for what we will ever have in TS 23.501, cannot accept any previous revisions
George (Ericsson) Ok only with r01. Nothing is defined yet, r03 is Ok once it is defined
Stefano (Qualcomm) provides R04 with an EN.
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comments
Krisztian (Apple) is OK with r04.
Myungjune (LGE) comments
Alessio(Nokia) ok with r04 and r03 only
George (Ericsson) proposes to postpone this. No need to say anything before work id completed
Krisztian (Apple) proposes to agree r04. As pointed out by Alessio, SA2 did the study and expects CT1 to use the results as a basis for normative work in CT1 (written in the LS). I am wondering why we have doubts CT1 would ignore this request.
Jinguo(ZTE) also propose to agree r04.
George (Ericsson) proposes postponing this.
==== Final Comments Deadline ====
Postponed
9.11.2 - - - KI#3 - - Docs:=8 -
9.11.2 S2-2300855 DISCUSSION Discussion Considerations on the normative support of KI#3 and KI#5 features. Nokia, Nokia Shanghai Bell Rel-18 Noted Peter Hedman (Ericsson) provides comments on the proposals
Alession (Nokia) provides some replies to comments by Peter Hedman (Ericsson)
Peter Hedman (Ericsson) provides replies inline.
Alessio(Nokia) suggest that the CRs are discussed as I think here are inaccuracies in the comments here below (e.g. the fact we do not support per TA granularity from non-supporting UEs which is plainly NOT what we say.. but if you give per cell availability info (CLRI in our paper) then obviously the granularity for supporting UEs is sub TA and a MRU should be done when the Ue exists the support area in KI#3 context
==== Revisions Deadline ====
Myungjune (LGE) proposes to notes this DP.
==== Final Comments Deadline ====
Noted
9.11.2 S2-2300866 CR Approval 23.501 CR4000 (Rel-18, 'B'): Support of network slices with sub-TA granularity Nokia, Nokia Shanghai Bell Rel-18 Postponed Peter Hedman (Ericsson) provides comments and concerns
Jinguo(ZTE) comments and suggests to use 1151 as basis for the location validity
Ashok (Samsung) comments
Alessio(nokia) provides r01 which should address the concerns.
Stefano (Qualcomm) proposes to note the CR and devote further discussion/thought to this functionality.
Dieter (Deutsche Telekom) provides comments and concerns
==== Revisions Deadline ====
Peter Hedman (Ericsson) objects to the CR r00 and r01
Jinguo(ZTE) asks to discuss it at CC#5.
Jinguo(ZTE) asks to discuss at CC#4
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300868 CR Approval 23.501 CR4002 (Rel-18, 'B'): On non-uniform support of network slices with the RA Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301483 To be merged into S2-2300995 (For CC#4) Peter Hedman (Ericsson) proposes to use 00995 as basis
alessio(Nokia) prefers 868 documentation style not impacting other clauses so we want to keep this.
alessio(Nokia) provides r01
Jinguo(ZTE) mentioned that this CR is for KI#5 and is moved from KI#3
Peter Hedman (Ericsson) provides strong concerns and suggests to use 00995 as basis as this CR
alessio(Nokia) replies to peter.
alessio(Nokia) provides r02.
Iskren (NEC) proposes to use S2-2300995 by Lenovo as a baseline CR.
Kundan(NEC) asking question to Alessio.
==== Revisions Deadline ====
Jinguo(ZTE) suggest to merge this CR into 995
==== Final Comments Deadline ====
Merged
9.11.2 S2-2300871 CR Approval 23.501 CR4004 (Rel-18, 'B'): Optimizations for the support of time vality policies for a network slice and graceful network slice PDU sessions release. Nokia, Nokia Shanghai Bell Rel-18 Noted Ashok (Samsung) provides r01
Haiyang (Huawei) comments
Malla (NTT DOCOMO) provided r02
alessio (nokia) does not agree with Huawei comments: there is no similarity as the temporary nature of slices can apply to slices that have not yet been requested and can be provided together with the configured S-NSSAI and are irrespective of the location where the UE is. also this is a feature that is not really related to the other logically. the limited area applies also only inside the RA and is updated after MRU. this may not be updated for a long time and be associated with configured slices.
alessio(nokia) Comments and provides r03
Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides question
Peter Hedman (Ericsson) provides r04
Ashok (Samsung) comments on r04
Kundan (NEC) is fine with r04.
Malla (NTT DOCOMO) comment
alessio(nokia) cannot agree with r04 and provides r05
Peter Hedman (Ericsson) provides replies
Peter Hedman (Ericsson) objects to r05
Alessio(Nokia) comments that this r04 voids the feature. what is left?
Ashok (Samsung) propose to go with r04
Peter Hedman (Ericsson) provides comments and r07
Peter Hedman (Ericsson) provides r06 based on r04
alessio(Nokia) cannot accept r07, r06 as they are removing the main purpose of the feature. without RAN impact this is just a FYI on a time when slice ends as NO signalling is saved whatsoever (and as stated the thing does not work in r04,6,7
Haiyang (Huawei) provides questions
==== Revisions Deadline ====
Jinguo(ZTE) suggest to go with r07
alessio(nokia) suggest to go with r05 as technically endorsed as basis of further work, with this note in report: 'the aspect of how to minimize PDU session release signally are to be discussed' because the other revisions by Ericsson seem to not enable any signalling saving (which was the purpose of adding this feature not just to tell the UE when a slice will be disappearing as a FYI.
Peter Hedman (Ericsson) propose to approve r07, ok with r04, r06, r07 and OBJECTS to r00, r01, r02, r03, r05
Alessio(Nokia) then assumes this is noted. pity.
Ashok (Samsung) is fine with r07
==== Final Comments Deadline ====
Noted
9.11.2 S2-2301151 CR Approval 23.501 CR4077 (Rel-18, 'B'): Support of reduced network slice availability Ericsson Rel-18 Postponed Alessio(Nokia) has concerns with this CR as int introduces is rather complex handling of availability info and policies that is an overkill for KI#3 resolution. also the concepts are unclear
Peter Hedman (Ericsson) provides comments
Xiaowen Sun (vivo) provides comments.
Peter Hedman (Ericsson) provides r01
Ashok (Samsung) comments
Myungjune (LGE) questions on alternative QoS notification
Ashok (Samsung) provides r02
Peter Hedman (Ericsson) provides r03
Ashok (Samsung) is OK with r03
Xiaowen Sun (vivo) replies to Peter (Ericsson)
Alessio(Nokia) agrees with Xiaowen . he CR seems to land ana vaialbility polic but then is not specified how it is used by UE from our standpooitn for KI#3 the UE behaviour is clear : register whe UE enters area where the slice is marked to be not available. we therefore propose to use 866 which is very simple. we will revise it to cover some of the comments received.
Ashok (Samsung) propose to go with r03
Jinguo(ZTE) suggests to use this tdoc as basis for location validity policy.
==== Revisions Deadline ====
Dieter (Deutsche Telekom) supports this CR.
Alessio(Nokia) believes that if the behaviour is NOT registered then a registration has to be done so the network deregisters the UE from S-NSSAI in line in 871. Then the registered with no UP activated means the CN can still page and we wonder why since the UE in in area where resource is 0. Any cell where resource is >0 should be part of the validity are and by definition of GSMA AoS (area where Ue can access the network slice) is part of the AoS. so this cR is not really aligned with a sound end to end behaviour nor GSMA definition of AoS and cannot be accepted. we object to using this as basis of work. also the text on registered with no UP was for partially allowed s-NSSAIs policies (what in solution 11 was conditional S-NSSAI) it is just an accident it was left here the same as for KI#5.
Alessio(Nokia) (comments to replace the previous one) believes that if the behaviour is NOT registered then a registration has to be done so the network deregisters the UE from S-NSSAI in line in 866. Then the registered with no UP activated means the CN can still page and we wonder why since the UE in in area where resource is 0. Any cell where resource is >0 should be part of the validity are and by definition of GSMA AoS (area where Ue can access the network slice) is part of the AoS. so this cR is not really aligned with a sound end to end behaviour nor GSMA definition of AoS and cannot be accepted. we object to using this as basis of work. also the text on registered with no UP was for partially allowed s-NSSAIs policies (what in solution 11 was conditional S-NSSAI) it is just an accident it was left here the same as for KI#5.
Peter Hedman (Ericsson) propose to approve r03 (and adding co-signers)
alessio(Nokia) objects to approving any revision of this. we clarified why technically the whole week but were ignored. this CR introduces too many options for this and also is oblivious of AoS definition in GSMA.
Ashok (Samsung) also Ok with r03
Alessio(Nokia) for avoidance of doubt we object to all revisions of this document so far seen
Jinguo(ZTE) asks to discuss it at CC#5.
Jinguo(ZTE) asks to discuss at CC#4
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2301153 CR Approval 23.501 CR4078 (Rel-18, 'B'): Support of graceful/gradual termination of PDU sessions during network slice decommissioning Ericsson Rel-18 Noted Peter Hedman (Ericsson) provides r01
Malla (NTT DOCOMO) provided comment
Alessio(Nokia) agrees with Malla it is not necessary to introduce a clause on network slice management, proposes to note the paper
Peter Hedman (Ericsson) provides reply to Malla
Xiaowen Sun (vivo) provides comments.
Haiyang (Huawei) provides r02.
Alessio(nokia) asks to note r02 too which is made worse as now the URSP update to convey time limits is proposed and we do not thing this was agreed.
Peter Hedman (Ericsson) provides comments
Ashok (Samsung) comments
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides reply and suggest to approve r00
alessio (nokia) already suggested to note this CR including r00
==== Final Comments Deadline ====
Noted
9.11.2 S2-2301152 CR Approval 23.502 CR3848 (Rel-18, 'B'): Support of reduced network slice availability Ericsson Rel-18 Postponed Alessio(Nokia) proposes to postpone this document till 501 is stable
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300295 CR Approval 23.503 CR0812 (Rel-18, 'B'): Graceful termination for legacy UEs Huawei, HiSilicon, LG Electronics Rel-18 Noted Ashok (Samsung) comments
Haiyang (Huawei) responses
Peter Hedman (Ericsson) provides comments
Haiyang (Huawei) responses to Peter (Ericsson)
Ashok (Samsung) responds to Haiyang (Huawei)
Haiyang (Huawei) responses to Ashok (Samsung)
Malla (NTT DOCOMO) agrees with Ashok (Samsung) and share concern
Alessio(Nokia) shares the concerns of other companies and proposes to note this paper.
Haiyang (Huawei) responses to Malla (NTT DOCOMO)
Ashok (Samsung) clarifies to Haiyang (Huawei)
Haiyang (Huawei) provides r01
==== Revisions Deadline ====
alessio(Nokia) proposes to note this CR
Haiyang (Huawei) comments
alessio(nokia) replies
Alessio(Nokia) comments that if what Ericsson as is correct they can do it already today so no need to write this into a NORMATIVE note in a table. So again this CR is NOT needed as operators if they think this is used as described they can do it. we do not describe what operators shall or not do in the standards. we object to approving any revision of this.
==== Final Comments Deadline ====
Noted
9.11.2 - - - KI#4 - - Docs:=9 -
9.11.2 S2-2300126 CR Approval 23.501 CR3822 (Rel-18, 'B'): KI#4: Support for Centralized NSACF in a PLMN with multi-service areas Ericsson Rel-18 r06 agreed. Revised to S2-2301603. Fenqin (Huawei) provides r01
Fenqin (Huawei) provides comments.
George (Ericsson) provides comments.
Fenqin (Huawei) provides feedback.
George (Ericsson) provides response.
Dongeun (Samsung) provides comments
George (Ericsson) provides r02
Fenqin (Huawei) provides r03.
George (Ericsson) provides r04. Minor editorial changes
Jinguo(ZTE) provides comments
Fenqin(Huawei) provides r05
Fenqin(Huawei) provides r06
==== Revisions Deadline ====
George (Ericsson) Accepts r06
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301603 CR Approval 23.501 CR3822R1 (Rel-18, 'B'): KI#4: Support for Centralized NSACF in a PLMN with multi-service areas Ericsson Rel-18 Revision of S2-2300126r06. Approved Agreed
9.11.2 S2-2300128 CR Approval 23.501 CR3823 (Rel-18, 'B'): KI#4: Support for HPLMN admission mode while Roaming Ericsson Rel-18 r03 agreed. Revised to S2-2301604. Fenqin (Huawei) Provides r01
George (Ericsson) Not Ok with this revision, provides comments, and ask questions
George (Ericsson) provides r02
Fenqin (Huawei) Provides r03
==== Revisions Deadline ====
George (Ericsson) OK with r03
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301604 CR Approval 23.501 CR3823R1 (Rel-18, 'B'): KI#4: Support for HPLMN admission mode while Roaming Ericsson Rel-18 Revision of S2-2300128r03. Approved Agreed
9.11.2 S2-2300657 CR Approval 23.501 CR3959 (Rel-18, 'B'): Hierarchical NSACF architecture enhancement Huawei, HiSilicon Rel-18 r10 agreed. Revised to S2-2301605. Fenqin (Huawei) provides r02.
George Foti (Ericsson) provides r01.
Ashok (Samsung) provides r03.
Fenqin (Huawei) provides feedback to Ashok.
George (Ericsson) Ericsson accepts ONLY r01 or r02.
Ashok (Samsung) accepts only r03.
Fenqin (Huawei) provides feedback.
Jinguo(ZTE) provides comment
George (Ericsson) provides response
Ashok (Samsung) responds to George (Ericsson)
George (Ericsson) provides responses inline
Fenqin (Huawei) provides a responses to Ashok.
Ashok (Samsung) responds to George (Ericsson) and Fenqin (Huawei) and propose a way forward
Fenqin (Huawei) responds to Ashok (Samsung)
Jinguo(ZTE) provides comments
Ashok (Samsung) comments
Fenqin (Huawei) provides r04
George (Ericsson) provides r06
Iskren (NEC) expresses strong concern
George (Ericsson) provides comments
Fenqin (Huawei) give a feedback
Iskren (NEC) replies Fenqin
Fenqin(Huawei) replies Isrken,
George (Ericsson) I suggested a simpler classification hierarchal vs non-Hierarchal. That makes everyone happy. We can go for it
George (Ericsson) provides r07
Fenqin (Huawei) provides R08
George (Ericsson) provides r09
alessio(Nokia) provides r10
==== Revisions Deadline ====
George (Ericsson) OK R10
Jinguo(ZTE) is ok with r10 and would like to cosign
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301605 CR Approval 23.501 CR3959R1 (Rel-18, 'B'): Hierarchical NSACF architecture enhancement Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, ZTE Rel-18 Revision of S2-2300657r10. Approved Agreed
9.11.2 S2-2300127 CR Approval 23.502 CR3663 (Rel-18, 'B'): KI#4: Support for Centralized NSACF in multi-service PLMN in non-roaming cases. Ericsson Rel-18 Postponed Fenqin (Huawei) provides comments.
==== Revisions Deadline ====
Jinguo(ZTE) suggests to postpone all 502 CRs
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300659 CR Approval 23.502 CR3768 (Rel-18, 'B'): Hierarchical NSACF architecture enhancement Huawei, HiSilicon Rel-18 Postponed ==== Revisions Deadline ====
Jinguo(ZTE) suggests to postpone the 502 CR
Dongeun(Samsung) suggests to postpone the 502 CR and inform Tao (VC) that CR is marked as Approved in the latest Chairman's Note.
Fenqin (Huawei) we are ok to postpone
==== Final Comments Deadline ====
Postponed
9.11.2 S2-2300660 CR Approval 23.502 CR3769 (Rel-18, 'B'): Hierarchical NSACF architecture in roaming enhancement Huawei, HiSilicon Rel-18 Postponed ==== Revisions Deadline ====
Jinguo(ZTE) suggests to postpone the 502 CR
Dongeun(Samsung) suggests to postpone the 502 CR and inform Tao (VC) that CR is marked as Approved in the latest Chairman's Note.
Fenqin (Huawei) we are ok to postpone
==== Final Comments Deadline ====
Postponed
9.11.2 - - - KI#5 - - Docs:=9 -
9.11.2 S2-2301011 LS OUT Approval [DRAFT] LS on partially allowed/rejected S-NSSAI Nokia, Nokia Shanghai Bell Rel-18 CC#4: r09 agreed. Revised to S2-2301466. Peter Hedman (Ericsson) provides comments and suggests to use 01157
Genadi (Lenovo) provides comments to also include RAN2 and the topic from KI#3.
Alessio(Nokia) suggests using this one
Peter Hedman (Ericsson) provides reply that proposal is for sure going for an option that was turned down at SoH
Alessio(Nokia) provides R01 that also expands the scope of LS to ask question on the AoS smaller than TA topic which we need to be aware of.
Jinguo(ZTE) provides r03
Haiyang (Huawei) provides r02
Haiyang (Huawei) comments
Genadi (Lenovo) provides r04.
Ashok (Samsung) updated the subject title. It's about KI#3, not KI#5
==== Revisions Deadline ====
Jinguo(ZTE) is fine with r04
Haiyang (Huawei) is OK with r04
alessio provides r05 in drafts folder
Haiyang (Huawei) comments, suggests to go with r04 (not OK with r05)
Jinguo(ZTE) asks to discuss at CC#5
alessio(Nokia) can only accept r05 and explains why
Jinguo(ZTE) asks to discuss at CC#4
==== Final Comments Deadline ====
Peter Hedman (Ericsson) provides r0x
Alessio(nokia) can live with this r07 which is largely based on r06 but clarifies the meaning of zero configured resources no data can be sent/received.
Peter Hedman (Ericsson) provides comments and r08
alessio(Nokia) ok with r08
Haiyang (Huawei) provides r09. r08 is not OK.
Revised
9.11.2 S2-2301466 LS OUT Approval LS on Support of Network Slices which have Area of Service not matching deployed Tracking Areas SA WG2 Rel-18 Revision of S2-2301011r09. Approved Approved
9.11.2 S2-2301154 DISCUSSION Agreement KI#5: Proposed way forward. Ericsson Rel-18 Noted Alessio(Nokia) comments
Peter Hedman (Ericsson) provides replies
==== Revisions Deadline ====
Myungjune (LGE) proposes to notes this DP.
==== Final Comments Deadline ====
Noted
9.11.2 S2-2301157 LS OUT Approval [DRAFT] LS on Partially allowed/rejected NSSAI Ericsson Rel-18 CC#4: r11 agreed. Revised to S2-2301467. Alessio(Nokia) proposes to note this Ls and use S2-2301011
Peter Hedman (Ericsson) provides r01
Genadi (Lenovo) provides r02.
==== Revisions Deadline ====
Ashok (Samsung) comments
Genadi (Lenovo) replies to Ashok (Samsung).
Jinguo(ZTE) is fine with r02
Ashok (Samsung) clarifies to Genadi (Lenovo)
Haiyang (Huawei) provides r03: r02+'proposes->has discussed'+' optimize RRM logic -> know about it if required by the RAN.'.
Kundan(NEC)is fine with r02.
alessio(Nokia) is not ok with previous revisions and proposes r04 in drafts folder
Peter Hedman (Ericsson) propose to approve r02 or as suggested r02+'proposes->has discussed'+' optimize RRM logic -> know about it if required by the RAN.
Alessio (Nokia) replies to Peter Hedman (Ericsson) objects to r02 and its revision
Peter Hedman (Ericsson) provides reply to Alessio
Alessio(Nokia) is providing r05 in the DRAFT folder
Peter Hedman (Ericsson) provides r06 in draft folder
Ashok (Samsung) seeks clarification
Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides r07 to cater for the comments
Haiyang (Huawei) provides r08
Peter Hedman (Ericsson) provides r08 in draft folder
alessio(Nokia) provides r09 in draft folder
Jinguo(ZTE) comments
Peter Hedman (Ericsson) provides r10
Jinguo(ZTE) asks to discuss at CC#5
Jinguo(ZTE) asks to discuss at CC#4
==== Final Comments Deadline ====
Peter Hedman (Ericsson) replies
Peter Hedman (Ericsson) provides r11
Alessio(nokia) thanks peter for providing r11 which we can accept.
Revised
9.11.2 S2-2301467 LS OUT Approval LS on Partially allowed/rejected NSSAI SA WG2 Rel-18 Revision of S2-2301157r11. Approved Approved
9.11.2 S2-2300900 CR Approval 23.501 CR4014 (Rel-18, 'B'): .Support of partially supported network slice in a RA KI#5. NEC Rel-18 Merged into S2-2301483 To be merged into S2-2300995 (For CC#4) Peter Hedman (Ericsson) provides comments and prefer to make changes to other clauses as well as in 00995.
Kundan (NEC) responds to Peter.
Alessio(nokia) comments that this paper should be merged into S2-2300868 23.501 CR4002 (Rel-18, 'B'): On non-uniform support of network slices with the RA which was wrongly allocated to KI#3 . we prefer self-contained clause approach as if we start updating though ought it will be a lot of CRs and the text will become messy
Kundan (NEC) provides r01 addressing Peter's comment.
==== Revisions Deadline ====
Myungjune (LGE) proposes to merge this CR into S2-2300995
Jinguo(ZTE) proposes to merge this CR into S2-2300995
==== Final Comments Deadline ====
Merged
9.11.2 S2-2300995 CR Approval 23.501 CR4035 (Rel-18, 'B'): Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI Lenovo Rel-18 CC#4: r08 + changes agreed. Revised to S2-2301483. Peter Hedman (Ericsson) provides comments
Genadi (Lenovo) responds to Peter Hedman (Ericsson).
Xiaowen Sun (vivo) provides comments.
Ashok (Samsung) comments
Genadi (Lenovo) provides r01 mainly based on comments from Peter Hedman (Ericsson).
alessio(Nokia) has strong concerns and cannot agree with this CR
Haiyang (Huawei) suggests we can select one 501 CR as basis
Alessio(Nokia) as mentioned has concerns on the contents of this revision and has proposed 868r01 to be used as basis.
Peter Hedman (Ericsson) provides replies tpo the 'concerns' from Nokia
Peter Hedman (Ericsson) provides r02
Genadi (Lenovo) responds to Alessio(Nokia) and seeks for compromise.
alessio(nokia) replies to peter
Iskren (NEC) suggests an update to the Partially Allowed NSSAI definition
alessio(Nokia) objects to r03
Peter Hedman (Ericsson) provides r03
Iskren (NEC) comments
Genadi (Lenovo) responds to Iskren (NEC) and provides r04 (removing the objected clauses).
Iskren (NEC) comments.
alessio(Nokia) could live with r04 with the understanding it needs lots of work still
alessio(Nokia) Sorry : we mistakenly said r04 but we meant r05 which we provided ?? disregard previous comment for notes
Peter Hedman (Ericsson) provides r07
Haiyang(Huawei) provides r06
Kundan(NEC) is not fine with any version not providing partially supported TA to the NG-RAN. we see clear advantage in providing to the NG-RAN in RRM procedure.
Peter Hedman (Ericsson) provides reply
Kundan (NEC) provides R09 on top of R07.
==== Revisions Deadline ====
Genadi (Lenovo) provides reply to Kundan (NEC).
Stefano (Qualcomm) provides R08 with editorial changes for readability.
Myungjune (LGE) is ok with r08 and wants to cosign.
Haiyang (Huawei) is ok with r08.
Ashok (Samsung) ok with r08.
Kundan(NEC) provides comment on r08.
Jinguo(ZTE) is fine with r08 and would like to cosign.
Alessio (nokia) is can live with r08 and would like to suggest this is technically endorsed as basis of further work (we need lots of changes anyhow)
Genadi (Lenovo) replies to Kundan (NEC) comment on r08.
NEC(Kundan) supports Genadi proposal.
Alessio(Nokia) ok with the update.
Iskren (NEC) supports the CR and would like to co-sign.
Genadi (Lenovo) proposes to open the paper in CC#3 or CC#4 to discuss r08 + proposed changes.
Stefano (Qualcomm) supports the proposal and asks to co-sign the paper.
Peter Hedman (Ericsson) provides comments and suggests new wording
Genadi (Lenovo) is fine with the wording proposal by Peter Hedman (Ericsson).
Genadi (Lenovo) comments on a misalignment in r08 and proposes a resolution.
Genadi (Lenovo) provides r09 in the '_Post_revisions_deadline' folder.
Peter Hedman (Ericsson) provides comments and suggest to approve r08 + add 'in the whole Registration area, but the UE is allowed to activate the User Plane resources' + remove 'The AMF also provides the Partially Allowed NSSAI (without indication of the TA list where the partially allowed S-NSSAIs are supported) to the NG-RAN together with the UE's context.' + remove RAN as impacted on cover sheet
Jinguo(ZTE) asks to discuss at CC#5
Jinguo(ZTE) asks to discuss at CC#4
==== Final Comments Deadline ====
Alessio(Nokia) think the changes are too many we can only accept this change r08 + add 'in the whole Registration area, but the UE is allowed to activate the User Plane resources'
Genadi (Lenovo) supports the proposal by Peter Hedman (Ericsson).
Alessio(Nokia) reiterates the RAN impact of receiving and handling allowed NSAI shall be there. Peter just confirmed it.
Revised
9.11.2 S2-2301483 CR Approval 23.501 CR4035R1 (Rel-18, 'B'): Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI Lenovo, Ericsson, LG Electronics, Huawei, Samsung, ZTE, NEC, Qualcomm, Apple, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300995r08 + changes. Approved Agreed
9.11.2 S2-2301155 CR Approval 23.502 CR3849 (Rel-18, 'B'): Support of partly rejected/allowed S-NSSAIs Ericsson Rel-18 Postponed Alessio(Nokia) proposes to note this Cr as it is not realistic to proceed with 23.502 CR before 23.501 is stable
Peter Hedman (Ericsson) provides r01
Xiaowen Sun (vivo) provides concern on terminology
Peter Hedman (Ericsson) provides comments
==== Revisions Deadline ====
Jinguo(ZTE) proposes to postpone the 502 CR
Ashok (Samsung) comments
Peter Hedman (Ericsson) provides comments that CR r00 seems stable in relation to the 23.501 CR
Alessio(Nokia) has already asked to postpone this.
==== Final Comments Deadline ====
Postponed
9.11.2 - - - KI#6 - - Docs:=3 -
9.11.2 S2-2300573 CR Approval 23.501 CR3939 (Rel-18, 'B'): Improved network control of the UE beahviour for a network slice LG Electronics Rel-18 r16 agreed. Revised to S2-2301606. Fenqin (Huawei) provides comments
George (Ericsson) Not OK with r01. provides comments
Myungjune provides r01.
George Foti (Ericsson) provides comments
Ashok (Samsung) provides r02
George (Ericsson) Not OK with any revision including the original. Additional comments below.
Fenqin (Huawei) provides further feedbacks
Alessio(nokia) provides r03
George (Ericsson) Actually what U attached is exactly what I said. At PDU session establsihment PCF provides the info to the SMF. So UDM is not need. I maintain our objection to all revisions including original.
Ashok (Samsung) comments
Fenqin (Huawei) give a feedback on this issue.
alessio(nokia) comments
George (Ericsson) provides response. We don't.
Myungjune (LGE) provides r04.
Ashok (Samsung) responds
Ashok (Samsung) provides r05.
alessio(Nokia) clarifies the SMF cannot know whether there is another SMF for same slice so cannot decide to release the slice on behalf of AMF and AMF ahs to run the timer for release of slice not SMF.
Ashok (Samsung) clarifies that SMF is not deciding to release the slice on the behalf of AMF. It is simply indicating AMF that the slice can be deregistered because of inactivity. If AMF does not find another PDU session using the same slice then AMF can remove, otherwise not. It's the AMF who in the end decide whether to release or retain.
alessio(Nokia) comments that it makes no difference why a PDU session was released by a SMF. so not sure why the indication from SMF matters.
Iskren (NEC) comments.
Alessio(Nokia) has concerns on r05 till we can find the justification for the sending of indication to aMF. AMF should not really care why a PDU session in slice is released to run its own timers, nor be required to analyze the cause code of release from SMF (or UE)
Myungjune (LGE) replies to Iskren (NEC).
Ashok (Samsung) explains the benefit and it is to save the AMF from running the timer again to identify the slice inactivity when already SMF has identified and indicated. AMF need to use the input and take action
Iskren (NEC) provides updates in r06
George (Ericsson) Not OK with this revision. We keep discussing things unrelated to on demand slices, which are not in scope and not required. All other comments are not addressed
George (Ericsson) objects to all revision. Provides comments
Myungjune (LGE) provides r07
George (Ericsson) provides r08
Fenqin (Huawei) provides r09
Ashok (Samsung) provides r10
Jinguo(ZTE) suggest to change 'can' to 'may'
Krisztian (Apple) provides r11.
Myungjune (LGE) provides r12.
George (Ericsson) provides r13
alessio(Nokia) provides r14
Fenqin (Huawei) provides r15
George (Ericsson) provides r16. cosigned
Fenqin (Huawei) comments
Ashok (Samsung) replies
George (Ericsson) provides comments
==== Revisions Deadline ====
Iskren (NEC) provides comments
Iskren (NEC) provides r17
Tao(VC) remind that r17 provided after revision deadline. Will check r016 agreeable or not
Tao(VC) let's still check r17 since I checked r17 uploaded to the server before revision deadline.
George (Ericsson) Accepts only R16
Fenqin (Huawei) responds to Ashok
Krisztian (Apple) prefers r16.
Jinguo(ZTE) suggest to go with r16.
Myungjune (LGE) proposes to agree r16 and replies to Jinguo(ZTE)
Genadi (Lenovo) proposes to agree r16. Further work is needed in the next meeting.
==== Final Comments Deadline ====
Revised
9.11.2 S2-2301606 CR Approval 23.501 CR3939R1 (Rel-18, 'B'): Improved network control of the UE beahviour for a network slice LG Electronics, NEC, Apple, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Samsung, Huawei, HiSilicon Rel-18 Revision of S2-2300573r16. Approved Agreed
9.11.2 S2-2300574 CR Approval 23.502 CR3751 (Rel-18, 'B'): Improved network control of a network slice LG Electronics Rel-18 Postponed Myungjune (LGE) provides r01.
George Foti (Ericsson) proposes to note the CR. We need to agree on the 23.501 CR first
Iskren (NEC) supports this CR and provides r02.
George (Ericsson) objects to all 23.502 CRs for which there is an agreed upon 23.501 CR. This is completely backward
alessio(Nokia) agrees to postpone the 502 CRs
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.11.2 - - - Documents exceeding TU budget - - Docs:=20 -
9.11.2 S2-2300662 CR Approval 23.502 CR3770 (Rel-18, 'B'): Slice control based on UE inactivity Huawei, HiSilicon Rel-18 Not Handled George Foti (Ericsson) provides proposes to note the CR. We need to settle the 23.50 CR first
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300661 CR Approval 23.501 CR3961 (Rel-18, 'B'): Slice control based on UE inactivity Huawei, HiSilicon, Rel-18 Not Handled Fenqin (Huawei) proposes a feedback
George Foti (Ericsson) proposes to note the CR
George (Ericsson) Not Ok with UDM.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300872 CR Approval 23.501 CR4005 (Rel-18, 'B'): Configuration of network-controlled slice selection behavior for a UE Nokia, Nokia Shanghai Bell Rel-18 Not Handled George Foti (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301156 CR Approval 23.501 CR4079 (Rel-18, 'B'): Support of partly rejected/allowed S-NSSAIs Ericsson Rel-18 Not Handled Alessio(Nokia) proposes to merge this Cr in 868 or other paper as people will decide ... or note it.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300297 CR Approval 23.502 CR3699 (Rel-18, 'B'): Partially rejected S-NSSAI. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300296 CR Approval 23.501 CR3868 (Rel-18, 'B'): Partially rejected S-NSSAI Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300129 CR Approval 23.502 CR3664 (Rel-18, 'B'): KI#4: Support for HPLMN admission mode while Roaming Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300658 CR Approval 23.501 CR3960 (Rel-18, 'B'): Hierarchical NSACF architecture in roaming enhancement Huawei, HiSilicon Rel-18 Not Handled George Foti (Ericsson) This is merged in 129., which is fairly comprehensive and complete. We are not OK with touching the architectural figures. Not needed.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300571 CR Approval 23.501 CR3938 (Rel-18, 'B'): Non-homogenous slice support within a Registration Area LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300881 CR Approval 23.501 CR4011 (Rel-18, 'B'): .Support of Temporary network slice NEC Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300572 CR Approval 23.502 CR3750 (Rel-18, 'B'): Non-homogenous slice support within a Registration Area LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301184 CR Approval 23.503 CR0887 (Rel-18, 'B'): Support of network slice replacement ZTE Rel-18 Not Handled Dongeun (Samsung) provide comments
George Foti (Ericsson) provides comments
Jinguo(ZTE): this document is not on the list of this meeting.
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300650 CR Approval 23.501 CR3957 (Rel-18, 'B'): 23.501 Remapping in Initial Registration to Support Network Slice Service Continuity Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300652 CR Approval 23.501 CR3958 (Rel-18, 'B'): 23.501 PDU session relocation for slice service continuity Vivo Rel-18 Confirm CR Number - CR states 3957! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301009 CR Approval 23.501 CR4038 (Rel-18, 'B'): Support of network slice replacement with Altetnative S-NSSAI Lenovo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301200 CR Approval 23.502 CR3857 (Rel-18, 'B'): Alternative S-NSSAI provision to the UE NEC Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301204 CR Approval 23.502 CR3858 (Rel-18, 'B'): KI#1 New PDU Session transfer to an Alternative S-NSSAI NEC Rel-18 Not Handled Stefano Faccin (Qualcomm) same comments made on 1105 and 1182 apply.
George Foti (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300653 CR Approval 23.502 CR3765 (Rel-18, 'B'): 23.502 PDU session relocation for slice service continuity Vivo Rel-18 Not Handled George Foti (Ericsson) provides comments
alessio(Nokia) would like to postpone the 502 CRs till 501 is stable
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2300507 CR Approval 23.502 CR3739 (Rel-18, 'B'): KI#1 AMF triggered SSC mode 3 PDU Session Transfer KDDI, NEC Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.11.2 S2-2301188 CR Approval 23.501 CR4085 (Rel-18, 'B'): KI#1 Alternative S-NSSAI support NEC Rel-18 Not Handled George Foti (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.1 - - - Study on XR (Extended Reality) and media services (FS_XRM) - - Docs:=0 -
9.12.2 - - - XR (Extended Reality) and media services (XRM) - - Docs:=138 -
9.12.2 - - - General - - Docs:=12 -
9.12.2 S2-2300008 LS In Action LS from SA WG4: Reply LS on further details on XR traffic SA WG4 (S4aV220921) Revision of postponed S2-2210181 from S2#154. Noted Dan (China Mobile) suggest to NOTE this LS, this is the reply from SA4 and no action for SA2. Noted
9.12.2 S2-2300006 LS In Action LS from SA WG4: Reply LS to Follow-up LS on QoS support with Media Unit granularity SA WG4 (S4-221174) Revision of postponed S2-2210177 from S2#154. Noted Dan (China Mobile) suggest to NOTE this LS, this is the reply from SA4. Noted
9.12.2 S2-2301359 LS OUT Approval [DRAFT] LS on RAN information exposure for XRM Ericsson Rel-18 Created at CC#2. CC#4: Postponed Paul (Ericsson) provides Draft LS to RAN WG3 on on RAN information exposure for XRM.
Zhuoyun (Tencent) provides r02.
Dan(China Mobile) provides r01 with stating that these two aspects have been concluded in TR conclusion.
==== Revisions Deadline ====
Xiaowan Ke(vivo) disagree all the revisions and original version, provides comments and update(see r03 in draft folder)
Zhuoyun (Tencent) is fine with r01-r03, prefers r03, objects to r00.
Paul (Ericsson) provides r04 in DRAFTS folder and asks to discuss it in CC#3.
Chunshan (CATT) comments on the questions in the r04 LS.
Antoine (Orange): There is misalignment on the questionned WGs.
Dario (Qualcomm) support r04.
Hui(Huawei) fine with r04.
Xiaowan(vivo) disagree r04, just like feasibility question of L4S, the LS should focus on the feasibility question
Haley(Lenovo) disagree with r04 and prefer to ask whether it is feasible for RAN to support these exposure features
Paul (Ericsson) provides comments
Dario (Qualcomm) ??
==== Final Comments Deadline ====
Chunshan (CATT) provides r04v02.
Postponed
9.12.2 S2-2301462 LS OUT Approval [DRAFT] LS on RAN information exposure for XRM Ericsson Rel-18 Revision of S2-2301359. WITHDRAWN Withdrawn
9.12.2 S2-2300049 LS In Action LS from RAN WG2: Reply LS to SA WG2 on XR RAN WG2 (R2-2213226) Rel-18 Noted Hui (Huawei) proposes to note the LS In.
Xiaowan Ke(vivo) is OK to note the LS and no LS reply is expected.
Noted
9.12.2 S2-2300058 LS In Action LS from RAN WG3: Reply LS on XR and Media Services RAN WG3 (R3-226885) Rel-18 Noted Hui (Huawei) proposes to note the LS In.
Lei (Tencent) agrees with Hui and proposes to note the LS In.
Xiaowan Ke(vivo) also share the view no LS reply is expected for this LS in and it can be noted.
Noted
9.12.2 S2-2300078 LS In Information LS from SA WG4: Reply LS on Pose Information for XR SA WG4 (S4-221626) Rel-18 Noted Dan (China Mobile) suggest to NOTE this LS, since there is no action requirement for SA2. Noted
9.12.2 S2-2301211 DISCUSSION Discussion Discussion on a New SST value for Extended Reality and Media Services. InterDigital, Inc. Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.12.2 S2-2301213 LS OUT Approval [DRAFT] LS on a new SST value for Extended Reality and Media Services InterDigital Inc. Rel-18 r07 agreed. Revised to S2-2301372. LaeYoung (LGE) provides r02.
Dario (Qualcomm) comments and provides r01
Curt (Meta) comments - aren't SA2 asking GSMA to determine if there is a need or not to define a new SST for xR?
Dan(China Mobile) comments
Mike (InterDigital) replies to Curt (Meta) and Dan (China Mobile) and provides r03
Hui(Huawei) provides r04
Dan(China Mobile) provides r05
Curt (Meta) comments provides r06.
Dan (China Mobile) provide r07.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r07.
Curt (Meta) is fine with r07.
Mike (InterDigital) comments that r07 is good.
Dario (Qualcomm) is fine w/ r07
Hui (Huawei) prefers to r07, objects to r00-r03.
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301372 LS OUT Approval LS on a new SST value for Extended Reality and Media Services SA WG2 Rel-18 Revision of S2-2301213r07. Approved Approved
9.12.2 S2-2300241 CR Approval 23.501 CR3759R1 (Rel-18, 'B'): Support of XR and Media Services Tencent,Tencent Cloud, China Mobile, OPPO, Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, InteDigital Inc, Google Inc. Rel-18 Revision of S2-2210295. Confirm CR Revision - CR states 0! CC#4: r13 agreed. Revised to S2-2301469. Hyunsook (LGE) comments.
Dario (Qualcomm) comments and provides r01
Lei(Tencent) provides comments
Lei(Tencent) provides r04.
Devaki (Nokia) provides r05 (in case detailed version as in r04 is adopted). Alternatively, I would also be fine with the simplified general clause as in r01.
Xiaowan Ke(vivo) provides r06
Lei(Tencent) replies to Devaki(Nokia) and Xiaowan(vivo) and provide r07.
Hui(Huawei) provides comments on r07.
Boren (OPPO) provides r08.
Jinhua (Xiaomi) provides comments and r09.
Lei(Tencent) replies to Jinhua (Xiaomi) and provides comments and r09.
Mukesh (MediaTek) provides r10
Saso (Intel) points out that the new abbreviations in clause 3.2 are not used in the CR.
Lei(Tencent) replies to Saso (Intel) and think the new abbreviations in clause 3.2 are for whole XRM.
Jinhua (Xiaomi) replies to Mukesh, provides r11,
Mengzhen (China Telecom) comments and provides r11
Mengzhen (China Telecom) comments and provides r12
Dario (Qualcomm) comments and provides r13.
Jinhua (Xiaomi) provides comments,.
Lei(Tencent) provide r14 on top of r12. Replies to Dario (Qualcomm) and suggest to keep r13 as an option but allow more revisions on top of r14 to companies who are favor of the green texts
Hui (Huawei) provides r15.
==== Revisions Deadline ====
Devaki (Nokia) is ok with either r13 or r15 although I do prefer r13 to avoid risk of inconsistent specification due to duplication of text.
Jinhua (Xiaomi) provides comments, r15 is prefer,
Hui (Huawei) prefers to r15
Lei(Tencent) also prefers r15
Boren (OPPO) prefers r15
Mengzhen (China Telecom) prefers r15
Xiaowan is ok with r15 and r13, and prefers r15 w.r.t. people's time/energy for drafting
Dario (Qualcomm) prefers r13 and objects to others.
Lei(Tencent) thinks majority companies prefer r15 and the text related to KI#8 reflects TR conclusion.
Lei(Tencent) request to discuss in CC#4 if r15 can not be approved. Endorsing r15 is also acceptable.
==== Final Comments Deadline ====
Lei(Tencent) uploaded a revision on top of r15, add EN saying that the bullets can be updated according to progress of each KI, also remove half of a sentence referring to TS 23.503 and ask if this ok. If Dario(Qualcomm) still sustain objection, fine to approve r13 and do more work in next meeting.
Revised
9.12.2 S2-2301469 CR Approval 23.501 CR3759R2 (Rel-18, 'B'): Support of XR and Media Services Tencent,Tencent Cloud, China Mobile, OPPO, Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, InteDigital Inc, Google Inc., Huawei, vivo, Xiaomi Rel-18 Revision of S2-2300241r13. Approved Agreed
9.12.2 - - - KI#1&2 - - Docs:=8 -
9.12.2 S2-2300281 CR Approval 23.501 CR3864 (Rel-18, 'B'): Policy control enhancements to support multi-modality flows coordinated transmission China Mobile,Nokia,Nokia Shanghai Bell, Samsung, Xiaomi Rel-18 r12 agreed. Revised to S2-2301373, merging S2-2300235 and S2-2300477 Xinpeng(Huawei) provides r02.
Mike (InterDigital) comments and provides r01
Dan(China Mobile) would like to ask people's idea
Saso (Intel) replies to Dan(China Mobile) that Multimodal Service Identifier is preferable
Xinpeng(Huawei) replies.
Shabnam (Ericsson) provides comments and r03, supports by co-signing r03
Dan (China Mobile) provides r04
Dario (Qualcomm) comments.
Xinpeng(Huawei) provides r05.
Dan (China Mobile) reply.
Mengzhen (China Telecom) comments.
Jinhua (Xiaomi) provides comments, about the group change, and QoS monitoring.
Dan (China Mobile) provides reply.
Xinpeng(Huawei) provides r06.
Jinhua (Xiaomi) replies to Dan, and r07.
Dan (China Mobile) provide r08
Mike (InterDigital) comments and provides r09
Mengzhen (China Telecom) comments and provides r10
Georgios Gkellas (Nokia, Nokia Shanghai Bell) is OK with r10
Shabnam (Ericsson) provides comments and revision r11
Mengzhen (China Telecom) comments and provides r12
Mengzhen (China Telecom) comments and provides r14.
Jinhua (Xiaomi) replies to Shabnam (Ericsson), and provides r13,
Dan (China Mobile) adding r14 link.
==== Revisions Deadline ====
Xinpeng(Huawei) provides r15.
Shabnam (Ericsson) objects to all revisions excepts r11 and r12.
Xinpeng(Huawei) prefers r12.
Dan(China Mobile) prefers r12.
Dario (Qualcomm) prefers r11, is OK w/ r12 and objects to all other revisions.
Jinhua (Xiaomi) replies to Shabnam, go with r12 is OK
Youngkyo(Samsung) prefers r12.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) is OK with r11, r12, prefers r12
Dan(China Mobile) suggest to go with r12
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301373 CR Approval 23.501 CR3864R1 (Rel-18, 'B'): Policy control enhancements to support multi-modal flows China Mobile,Nokia,Nokia Shanghai Bell, Samsung, Xiaomi, Ericsson, InterDigital Inc., China Telecom Rel-18 Revision of S2-2300281r12, merging S2-2300235 and S2-2300477. Approved Agreed
9.12.2 S2-2300235 CR Approval 23.501 CR3857 (Rel-18, 'B'): Support for delivery of multimodal services Ericsson Rel-18 Merged into S2-2301373 Dan (China Mobile) suggest to merge this paper to S2-2300281 .
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300477 CR Approval 23.501 CR3913 (Rel-18, 'B'): Policy control enhancements to support multi-modal flows coordinated transmission China Telecom Rel-18 Confirm CR Number - CR states -! Merged into S2-2301373 Dan (China Mobile) suggest to merge this paper to S2-2300281 .
Mengzhen (China Telecom) agrees this paper to be merged into 0281.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300479 CR Approval 23.503 CR0835 (Rel-18, 'B'): Policy update to support policy control enhancements for multi-modality flows coordinated transmission China Telecom Rel-18 Confirm CR Number - CR states -! r16 agreed. Revised to S2-2301374. Youngkyo(Samsung) asks questions.
Mengzhen (China Telecom) provides r01 by merging the related contributions as suggested by rapporteur.
Boren(OPPO) asks questions.
Dan(China Mobile) answer some question
Haley(Lenovo) asks for clarification.
Mengzhen (China Telecom) reply to Dan (China Mobile), Boren(OPPO), Youngkyo(Samsung) and provides r02
Mengzhen (China Telecom) replies to Haley(Lenovo).
Shabnam (Ericsson) provides comments and r04, Ericsson supports the merger.
Dario (Qualcomm) provides r05 and asks question.
Mengzhen (China Telecom) replies to Dario (Qualcomm) and provides r06
Boren (OPPO) asks question and provides r07.
Xinpeng(Huawei) provides r08 based on r06.
Mengzhen (China Telecom) provides r09
Dan(China Mobile) also suggest to remove the link state, which is not clear.
Dan(China Mobile) provides r10
Xinpeng(Huawei) provides r11.
Dan(China Mobile) provides r12 to simplify the sentence.
Xinpeng(Huawei) provides r13.
Shabnam (Ericsson) provides comments and provides r14 aligned with other CRs
Mengzhen (China Telecom) provides r15
Mengzhen (China Telecom) provides r16
==== Revisions Deadline ====
Mengzhen (China Telecom) prefers r16, can live with r15/r14
Xinpeng(Huawei) prefers r16, and live with r13, objects to any other revisions.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) prefers r16, accepts r14, r15, too
Mengzhen (China Telecom) suggests to go with r16
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301374 CR Approval 23.503 CR0835R1 (Rel-18, 'B'): Policy update to support policy control enhancements for multi-modal services China Telecom, Ericsson, Huawei Rel-18 Revision of S2-2300479r16. Approved Agreed
9.12.2 S2-2300478 CR Approval 23.502 CR3734 (Rel-18, 'B'): Procedures update to support policy control enhancements for multi-modal flows coordinated transmission China Telecom, Nokia, Nokia Shanghai Bell Rel-18 Confirm CR Number - CR states -! r12 agreed. Revised to S2-2301375. Xinpeng(Huawei) provides r01.
Mengzhen (China Telecom) provides r02 by merging the related contributions.
Shabnam (Ericsson) provides comments and updated r03 and co-signs.
Dario (Qualcomm) provides r04 and asks question.
Mengzhen (China Telecom) replies to Dario (Qualcomm) and provides r05
Xinpeng(Huawei) provides r06.
Jinhua (Xiaomi) provides comments and r07.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) prefers r06
Xinpeng(Huawei) comments.
Jinhua (Xiaomi) replies to Georgios Gkellas, and provides r08.
Xinpeng(Huawei) provides r09 based on r07.
Shabnam (Ericsson) provides comments r10 aligned with changes to 23.501
Jinhua (Xiaomi) replies to Shabnam (Ericsson), and provides r11,
Mengzhen (China Telecom) provides r12
==== Revisions Deadline ====
Jinhua (Xiaomi) provides comments, r12/r11/r09 is prefer, can live with r10,
Mengzhen (China Telecom) prefers r12, can live with r11/r10/r09
Boren (OPPO) prefers r12, can live with r10.
Xinpeng(Huawei) accepts r09, r12, and objects to r10, r11.
Shabnam (Ericsson) can only accept r11, the EN added in r12 are not agreeable as open issue
Georgios Gkellas (Nokia, Nokia Shanghai Bell) prefers r10, accepts r11, r12, objects to r09
Mengzhen (China Telecom) suggest to accept r12 + remove the EN 'How to support the change of theMulti-modal Service ID is FFS'.
Xinpeng(Huawei) is ok with r12 + remove the EN 'How to support the change of theMulti-modal Service ID is FFS'.
Jinhua (Xiaomi) is OK with the proposal from Shabnam,
Mengzhen (China Telecom) suggests to go with r12 + remove the EN 'How to support the change of the Multi-modal Service ID is FFS'.
Dario (Qualcomm) can only accept r11, objects to other revisions.
==== Final Comments Deadline ====
Mengzhen (China Telecom) clarifies and requests to reconfirm in CC#4.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) Agrees with Mengzhen, i.e. R12 + remove the EN
Revised
9.12.2 S2-2301375 CR Approval 23.502 CR3734R1 (Rel-18, 'B'): Procedures update to support policy control enhancements for multi-modal flows China Telecom, Nokia, Nokia Shanghai Bell, Xiaomi, Huawei, Ericsson, Samsung Rel-18 Revision of S2-2300478r12. Approved Agreed
9.12.2 - - - KI#3 - - Docs:=17 -
9.12.2 S2-2300508 CR Approval 23.501 CR3923 (Rel-18, 'B'): Network exposure support for XR services Tencent, Tencent Cloud, Xiaomi, MediaTek, vivo Rel-18 CC#4: r24 removing bullets agreed. Revised to S2-2301376, merging S2-2300746 and S2-2300576 Youngkyo(Samsung) asks further some questions for clarification.
Lei(Tencent) /rapporteur comments that this paper should be taken as baseline for KI#3 501 general CR.
Haley (Lenovo) asks questions for clarification.
Zhuoyun (Tencent) provides r01 by merging the related contributions as suggested by rapporteur.
Yali(OPPO) provides r02
Zhuoyun (Tencent) replies.
Dario (Qualcomm) comments and provides r04.
Devaki (Nokia) provides r05.
Jinhua (Xiaomi) provides comments and r06.
Zhuoyun (Tencent) provides r08.
Youngkyo(Samsung) provides r09.
Zhuoyun (Tencent) comments.
Curt (Meta) supports Zhuoyun (Tencent) to focus this paper on API based solution.
Hui (Huawei) provides r10.
Zhuoyun (Tencent) provides r12.
Hui(Huawei) provides comments.
Dan (China Mobile) provides r14 based on r12, please ignore r13, I make a mistake.
Chunshan(CATT) provides r11.
Paul (Ericsson) provides r16. As per proposal from the pen holding company (Zhuoyun (Tencent) ) we remove all L4S aspects as 0232 is the baseline for L4S and 0508 is baseline for API/exposure.
Dan(China Mobile) comment for r16
Dan(China Mobile) reply
Zhuoyun (Tencent) provides r17.
Paul (Ericsson) provides response to Dan (China Mobile)
Paul (Ericsson) provides comments
Chunshan(CATT) provides r18.
Zhuoyun(Tencent) provides r19.
Zhuoyun(Tencent) provides r20.
Dan(China Mobile) provides r21
Hyunsook (LGE) provides the comment on r20.
Zhuoyun (Tencent) provides r22 and r23.
Paul (Ericsson) provides r24.
==== Revisions Deadline ====
Dan (China Mobile) prefer r23
Hyunsook (LGE) can live with r23.
Devaki (Nokia) comments that we cannot accept r23 (or the versions without the EN), can live with r22 or r24.
Dan(China Mobile) can live with r22.
Jinhua (Xiaomi) provide comments, proposes r24 with the last EN removing.
Curt (Meta) can live with r22/r24 but prefers r23.
Chunshan(CATT) accepts r23. For the r22/r24 is acceptable with the EN 'Editor's Note: It is for RAN3 to confirm whether providing QoS Notification Control for GBR QoS Flow and data rate information can be included in Release'18. ' is changed to ''Editor's Note: It is for RAN2 to confirm whether providing QoS Notification Control for GBR QoS Flow and data rate information can be feasible in this Release.'
Zhuoyun (Tencent) suggests to go forward with r23+' Editor's Note: It is for RAN WG to confirm whether providing QoS Notification Control for GBR QoS Flow and data rate information to the core network can be feasible in this Release.' Objects to r16. r24 was provided after the revision deadline in the ChairNotes, so it's not a valid version.
Xiaowan(vivo) confirm r24 is marked behind the revision deadline after double check.
Paul (Ericsson) can only accept r24.
Dario (Qualcomm) can only accept r24 (or r23 + changes).
Zhuoyun (Tencent) proposes to go forward with: r24+ changing the first EN to 'Editor's Note: It is for RAN WG to confirm whether providing QoS Notification Control for GBR QoS Flow and data rate information can be feasible in this Release.'
Dan (China Mobile) proposes to go forward with:r24= r23+ below changes including
1. Adding 'Editor's Note: It is for RAN WG to confirm whether providing QoS Notification Control for GBR QoS Flow and data rate information can be feasible in this Release.'
2. Adding 'Editor's Note: How the PCF correlates the QoS Monitoring measurements to provide this information is FFS.'
3. Adding 'Editor's Note: It is FFS whether all QoS monitoring requests can be addressed with the limitation of one QoS Monitoring control information per PCC'
4. Changing the first bullet about 'congestion information' to:
'For the congestion information, based on the PCC rule from PCF, the SMF requests the NG-RAN to report via GTP-U header to UPF and to PSA UPF to expose the information described in 5.37.Y.3 (this NG-RAN information can be provided to support ECN marking for L4S in PSA UPF as described in 5.37.Y.3) via Nupf_EventExposure service or via SMF/PCF/NEF as described in 5.8.2.X.'
5. Changing the bullet about 'delay difference' to :
'When PCF is requested to provide the difference between measured delays for the delay difference for two QoS Flows with different QoS requirements, the PCF enables the QoS monitoring for the different PCC rules and calculate the difference between the delays received. The AF includes in the request the neccesary information for the PCF to derive the associated QoS monitoring requirements for each PCC rule (i.e. periodicity, requested qos monitoring parameter - UL, DL, roundtrip), and is notified when the delay difference between two QoS Flows exceeds a threshold. The delay measurement for individual QoS Flow is based on QoS monitoring in clause 5.33.3. '
Dan(China Mobile) request this for CC#4
Dario (Qualcomm): in r24 also the 'delay difference' part needs to be removed.
==== Final Comments Deadline ====
Zhuoyun (Tencent) suggests to go forward with the changes captured in the latest ChairNotes with further removing the bullet about 'delay difference'.
Revised
9.12.2 S2-2301376 CR Approval 23.501 CR3923R1 (Rel-18, 'B'): Network exposure support for XR services Tencent, Tencent Cloud, Xiaomi, MediaTek, vivo, CATT, Huawei, China Mobile, Meta USA, ZTE Rel-18 Revision of S2-2300508r24 removing bullets, merging S2-2300746 and S2-2300576. Approved Agreed
9.12.2 S2-2300392 CR Approval 23.501 CR3887 (Rel-18, 'B'): Introduction of 5GS Information Exposure Vivo, China Mobile, Tencent, Tencent Cloud Rel-18 CC#4: r09 was revised to S2-2301471. Chunshan (CATT) provides r02 to merge the Averaging Window in Alternative QoS in paper 0733 and Available bit rate report in paper 0736.
Xiaowan Ke(vivo) replies to Youngkyo(Samsung)
Youngkyo(Samsung) questions.
Xiaowan Ke(vivo) provides r01 to merge the paper as requested by the rapporteur
Lei(Tencent) /rapporteur comments that this paper can be baseline for 501 CR for KI#3 covering aspects not in 0508.
Youngkyo(Samsung) replies to Xiaowan Ke(vivo)
Youngkyo(Samsung) is okay with Xiaowan's comment
Dario (Qualcomm) comments and provides r03.
Devaki (Nokia) has some fundamental concerns with some enhancements proposed in the CR and the revisions, wonders how all the CR (and the revisions) content matches to the TR conclusion. Some content such as data rate exposure from UPF, Averaging window to the NEF/PCF is all fine.
Hui(Huawei) provides comments.
Xiaowan Ke(vivo) replies to Devaki (Nokia) and Hui(Huawei) to provides r04
Chunshan(CATT) provides r05.
Xiaowan Ke(vivo) replies to Chunshan(CATT) and provides r06
Xiaowan Ke(vivo) replies to Hui(Huawei) and propose to check with r06
Chunshan(CATT) provides r07.
Mirko (Huawei) provides r08.
==== Revisions Deadline ====
Dario (Qualcomm) because of LS out 1359 objects to approving any revision; is OK with endorsing r04.
Dan (China Mobile) reply and we should ignore the LS to RAN.
Lei(Tencent) agrees with Dan (China Mobile) and think this CR can go ahead as conclusion as already been made in TR.
Xiaowan Ke(vivo) questions Dario (Qualcomm) whether OK as well about 'r04 with removal of changes(Average window) in 5.7.2.4.1a/1b/2/3'
Devaki (Nokia) comments that we would also prefer to endorse r04 (object to other revisions), r05/06 introduce these capabilities for non-GBR QoS Flow which go above and beyond TR conclusion.
Chunshan(CATT) objects r04,r05 and is OK with r06, r07, r08.
Dan(China Mobile) suggest to endorse r04
Xiaowan Ke(vivo) propose to agree/endorse r04 with addition 'The NG-RAN may be instructed to report the data rate in QoS flow level via control plane' and with removal of 'changes in 5.7.2.4.1a/1b/2/3'
Chunshan (CATT) is OK the proposal for the r04 that Xiaowan Ke(vivo) propose to agree/endorse r04 with addition 'The NG-RAN may be instructed to report the data rate in QoS flow level via control plane' and with removal of 'changes in 5.7.2.4.1a/1b/2/3'
Xiaowan Ke(vivo) uploads r04rev1(reflecting my previous proposal, which seems agreeable) in CC#3 folder for checking.
Paul (Ericsson) provide r08. There are dependencies to 0508 with same need for feedback from RAN3 as well as to the progress in 0232 concerning information provided to UPF. These are documented in this revision. We have general concerns to progress this CR in this meeting.
Dario (Qualcomm) is OK with postponing this CR.
Hui(Huawei) objects approval of any version, support to endorse r04, or r04 with change from r08.
Xiaowan Ke(vivo) propose to endorse r04 with addition 'The NG-RAN may be instructed to report the data rate in QoS flow level via control plane' and with removal of 'changes in 5.7.2.4.1a/1b/2/3'and addition of ENs: 'Editor's Note: It is for RAN3 WG to confirm whether providing QoS Notification Control for GBR QoS Flow to the CN can be feasible or not', 'Editor's Note: It is for RAN WG to confirm whether providing data rate information for QoS Flow to the CN can be feasible or not'; And if it is not endorsed, request CC#4 since it is the BL CR.
==== Final Comments Deadline ====
Xiaowan Ke(vivo) ask people to check r09 for technical endorse; and is ok to endorse r04 or r09
Revised
9.12.2 S2-2301471 CR Approval 23.501 CR3887R1 (Rel-18, 'B'): Introduction of 5GS Information Exposure Vivo, China Mobile, Tencent, Tencent Cloud Rel-18 Revision of S2-2300392r09. CC#4: Postponed and should be used as a baseline for the next meeting. Ericsson comment recorded Postponed
9.12.2 S2-2300232 CR Approval 23.501 CR3855 (Rel-18, 'B'): Introduction of support for L4S Ericsson, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Meta USA, AT&T, Charter, T-Mobile USA, Apple Rel-18 CC#4: r14 was revised to S2-2301470. Lei(Tencent)/rapporteur suggests this paper merged into 0508.
Paul (Ericsson) suggest that the L4S based option and the API based option are each based on separate baseline CR. Hence 0232 is proposed to serve as baseline for the L4S based solution. See additional explanation and r01 adding more supporting companies.
Paul (Charter) Also, agree to separate CRs for L4S congestion information exposure (based on 0232) and API based information exposure (based on 0508)
Curt (Meta) supports Paul (Ericsson) as well to have xx0232 to serve as baseline for the L4S based solution .
Dieter (Deutsche Telekom) supports Paul (Ericsson) as well to have xx0232 to serve as baseline for the L4S based solution .
Yali(OPPO) provides comments and supports the proposal of rapporteur to merge this paper into S2-2300508
Zhuoyun (Tencent) comments.
Haley(Lenovo) supports the proposal of rapporteur to merge this paper into S2-2300508
Mukesh (MediaTek) agrees with Zhuoyun (Tencent) and Yali (Oppo) to merge this paper into s2-2300508.
Jinhua (Xiaomi) provides comments, merged draft of KI#3 for further discussion is prefer, same as other KIs. Both of 0232 and 0508 could be the baseline choice.
Paul (Ericsson) replies to Yali (OPPO)
Hugh (AT&T) suggests 2300232 as the base for support of L4S and 2300508 as the base for API-based solution.
Chris Joul (T-Mobile USA) agrees with AT&T 2300232 as the base for support of L4S and 2300508 as the base for API-based solution.
Yali (OPPO) replies to Paul (Ericsson) , suggests some update of the CR content, and still suggests to merge this paper into S2-2300508
Devaki (Nokia) also prefers that this CR is used as the baseline for L4S aspects and the other CRs should focus on API based exposure method.
Youngkyo(Samsung) is okay with the separate CR for L4S marking but need refer to its clause since API based exposure method is also related to congestion reporting.
Lei(Tencent) repies to Youngkyo(Samsung) that referring to these clauses can be done in general CR for all XRM key issues 0241.
Yali (OPPO) provides r02
Youngkyo(Samsung) provide comments
Haley(Lenovo) asks for further clarification.
Hui (Huawei) provides comments
Dan(China Mobile) provides r03
Hui(Huawei) provides r04
Mukesh (MediaTek) provides r05.
Xiaowan Ke(vivo) provides r06
Paul (Ericsson) provides r07 and comments.
Saso (Intel) comments on the use of pre-configured 5QI(s).
Yali(OPPO) provides r08
Hui(Huawei) provides comments
Xiaowan Ke(vivo) comments and provides r09
Hui(Huawei) provides r10
Zhuoyun (Tencent) provides r11
Devaki (Nokia) comments.
Dieter (Deutsche Telekom) comments from operator perspective.
Chris (Vodafone) provides R13 (based on original r11 not Nokia r11)
Devaki (Nokia) provides r11 and r12.
Yali (OPPO) replies to Devaki (Nokia).
Yali(OPPO) replies to Chris (Vodafone) and provides R14 based on R13
==== Revisions Deadline ====
Devaki (Nokia) is fine with r13 as well (similar updates as in r11).
Yali(OPPO) prefer r14, ok with r08-r10, and r13, object to all other revisions. R14 is the latest version before revision deadline based on r13, just fix some terms which is not correctly used in r13.
Devaki (Nokia) comments that we can live with r14 (although I still think N4 capability indication is an overkill as well).
Paul (Ericsson) provides comments and question to Yali (OPPO).
Chris (Vodafone) replies on Paul's (Ericsson) question to Yali (OPPO).
Yali(OPPO) replies on Paul's (Ericsson).
Saso (intel) seeks clarification on 'the use of L4S on that QoS flow is controlled by RAN O&M' in r13 and r14
Yali (OPPO) comments
Paul (Ericsson) provides r15 based on r14 in DRAFTS folder and asks to discuss it in CC#3.
Yali(OPPO) is fine for r15.
Saso (Intel) replies to Yali (OPPO)
Hui(Huawei) can accept r15 only with this sentence: The assistance information carries congestion information of the QoS Flow for UPF to perform ECN marking or exposure via API.
Chunshan (CATT) replies to Yali (OPPO)
Hui(Huawei) can accept r10-r14, or r15 + 'The assistance information carries congestion information of the QoS Flow for UPF to perform ECN marking or exposure via API.', objects other revisions and original version.
Xiaowan ke(vivo) comments r15 because suddenly change the terminology name after revision deadline will cause misalignment problem. We request to keep congestion information this meeting and revisit new proposal next meeting by contribution, if needed.
Yali (OPPO) replies to Chunshan (CATT)
Paul (Ericsson) provides a compromise proposal
Hui (Huawei) replies to Paul.
Zhuoyun (Tencent) prefers r14, objects to r15. We have the similar concern as Xiaowan regards to the terminology change and prefers to keep congestion information at this meeting. The proposal from Hui could be a compromise from our side.
Xiaowan Ke(vivo) objects to r15 and versions without 'congestion information'
==== Final Comments Deadline ====
Dan(China Mobile) summarize the difference between r15 and r14, people can further consider this change, since r15 is invalide version, while r14 is the latest version. So it is needed that we provide r14+changes
Revised
9.12.2 S2-2301470 CR Approval 23.501 CR3855R1 (Rel-18, 'B'): Introduction of support for L4S Ericsson, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Meta USA, AT&T, Charter, T-Mobile USA, Apple, Verizon, BT, Telstra Rel-18 Revision of S2-2300232r14. Postponed and should be used as a baseline for the next meeting. Ericsson comment recorded Postponed
9.12.2 S2-2300233 CR Approval 23.501 CR3856 (Rel-18, 'B'): Enhancements to QoS Monitoring Ericsson Rel-18 Merged into S2-2301471 To be merged into S2-2300392 (For CC#4) Lei(Tencent)/rapporteur suggest this paper to be merged into 0392
Dario (Qualcomm) asks questions for clarification and comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300746 CR Approval 23.501 CR3974 (Rel-18, 'B'): Network exposure support for XR services Samsung Rel-18 Confirm CR Number - CR states -! Merged into S2-2301376 Lei(Tencent)/rapporteur suggests this paper to be merged into 0508.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300733 CR Approval 23.501 CR3970 (Rel-18, 'B'): Support Averaging Window in Alternative QoS CATT Rel-18 Merged into S2-2301471 To be merged into S2-2300392 (For CC#4) Lei(Tencent)/rapporteur suggests this paper to be merged into 0392.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300576 CR Approval 23.501 CR3940 (Rel-18, 'B'): Congestion information exposure for XRM services Lenovo Rel-18 Merged into S2-2301376 Lei(Tencent)/rapporteur suggests this paper to be merged into 0508.
Haley(Lenovo) agrees this paper to be merged into 0508.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300736 CR Approval 23.501 CR3971 (Rel-18, 'B'): RAN Bitrate Report via the Control Plane Path CATT, Lenovo Rel-18 Merged into S2-2301471 To be merged into S2-2300392 (For CC#4) Lei(Tencent)/rapporteur suggests this paper to be merged into 0392.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301038 CR Approval 23.503 CR0877 (Rel-18, 'B'): 5GS Information Exposure Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301377, merging S2-2300738 and S2-2300810 Lei(Tencent) /rapporteur suggest to discuss 503 CR for KI#3 in this thread.
Hui(Huawei) provides r01.
Chunshan(CATT) provides r02.
Dario (Qualcomm) provides r03.
Hui (Huawei) comments on r03.
Hui(Huawei) provides r04.
Jinhua (Xiaomi) provides comments and r05.
Xiaowan Ke(vivo) provides r06
Mukesh (MediaTek) provides r22.
Mukesh (MediaTek) apologies for the previous email which was intended for 1039 discussion.
Hui(Huawei) clarifies r06 is the latest version, and r22 should be ignored.
==== Revisions Deadline ====
Jinhua (Xiaomi) suggest to go with r06,
Zhuoyun (Tencent) prefers r06 and would like to cosign this contribution.
Chunshan(CATT) prefers r06 and asks for cosign this contribution.
Dario (Qualcomm) objects to all revisions except r03 because of 'delay difference'.
Paul (Ericsson) agrees that the 'delay difference' shall not be included and objects all revisions except r03.
==== Final Comments Deadline ====
Paul (Ericsson) objects r03 that is marked as approved and all other revisions.
Revised
9.12.2 S2-2301377 CR Approval 23.503 CR0877R1 (Rel-18, 'B'): 5GS Information Exposure Huawei, HiSilicon Rel-18 Revision of S2-2301038r03, merging S2-2300738 and S2-2300810. Approved Agreed
9.12.2 S2-2300418 CR Approval 23.503 CR0828 (Rel-18, 'B'): Update TS23.503 to reflect conclusion of KI#3 for XRM in TR23.700-60 with respect to API based exposure option Nokia, Nokia Shanghai Bell Rel-18 Check Affected Clauses! Postponed Lei(Tencent) /rapporteur suggest to discuss 503 CR for KI#3 in 1038 thread to avoid parallel discussion in multiple threads.
Devaki (Nokia) comments that this CR is actually complimentary to the CR in S2-2301038, changes proposed in this CR to 6.1.3.22 are not covered by 1038 thus this CR can be kept separate.
Lei(Tencent) asks whether Nokia want to progress this CR, if yes, there should be a revision to remove QoS monitoring section and only keep simple changes 6.1.3.22, otherwise, the CR may not be approved as it is.
==== Revisions Deadline ====
Dan(China Mobile) suggest to postponed this paper.
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300738 CR Approval 23.503 CR0851 (Rel-18, 'B'): RAN Bitrate Report via the Control Plane Path CATT, Lenovo Rel-18 Merged into S2-2301377 Lei(Tencent) /rapporteur suggest to discuss 503 CR for KI#3 in 1038 thread to avoid parallel discussion in multiple threads.
Lei(Tencent) /rapporteur suggest to mark this CR as merged into 1038.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300810 CR Approval 23.503 CR0857 (Rel-18, 'B'): Congestion information exposure for XRM services Lenovo Rel-18 Merged into S2-2301377 Lei(Tencent) /rapporteur suggest to discuss 503 CR for KI#3 in 1038 thread to avoid parallel discussion in multiple threads.
Lei(Tencent) /rapporteur suggest to mark this CR as merged into 1038.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300819 CR Approval 23.288 CR0659 (Rel-18, 'B'): NWDAF exposes the estimated bandwidth to AF Huawei, HiSilicon Rel-18 Postponed Dario (Qualcomm) asks questions for understanding and proposes to discuss this with eNA_Ph3 experts.
LaeYoung (LGE) proposes to NOTE this CR.
Xinpeng(Huawei) replies and provides r01.
Dan (China Mobile) provide comment
LaeYoung (LGE) proposes to POSTPONE this CR to discuss together with updated WID.
==== Revisions Deadline ====
Dario (Qualcomm) is OK with postponing this CR.
==== Final Comments Deadline ====
Postponed
9.12.2 - - - KI#4&5 - - Docs:=40 -
9.12.2 S2-2300095 LS In Information LS from SA WG4: Reply LS on PDU Set Handling SA WG4 (S4aR230035) Rel-18 Noted Dan (China Mobile) suggest to NOTE this LS, since there is no action requirement for SA2.
Hui (Huawei) supports to NOTE this LS
Noted
9.12.2 S2-2300053 LS In Action LS from RAN WG2: LS on PDU Set Handling RAN WG2 (R2-2213351) Rel-18 Responses drafted in S2-2300337, S2-2300400, S2-2300499, S2-2300732, S2-2300741, S2-2301013, S2-2301036, S2-2301094, S2-2301219. Final response in S2-2301378 Replied to
9.12.2 S2-2300337 LS OUT Approval [DRAFT] Reply to LS on PDU Set handling Ericsson Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300400 LS OUT Approval [DRAFT] LS reply on PDU Set Handling vivo Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300499 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling Tencent, Tencent Cloud Rel-18 Response to S2-2300053. r23 agreed. Revised to S2-2301378, merging S2-2300337, S2-2300400, S2-2300732, S2-2300741, S2-2301013, S2-2301036, S2-2301094, S2-2301219 and S2-2300371 Lei(Tencent) provides r01
Lei(Tencent) comments and based on some offline discussion, suggest to focus on discussion in 0499 to save people's effort.
Dario (Qualcomm) comments and provides r02
Lei(Tencent) provide comments and explains that choosing 0499 as baseline is supported by several companies and LS content needs to be based on multiple papers. Another revision considering multiple LS relies including 337 is being prepared.
Devaki (Nokia) provides r03, simplified version.
Lei(Tencent) agrees with Devaki (Nokia) that some text bring in r02 need to be remove, add some text from r00 to provide a better LS reply structure, provide r04.
Paul (Ericsson) provides r05 and comments.
Xiaowan Ke(vivo) provides r06
Hui(Huawei) provides r07
Xiaowan Ke(vivo) suggests Yixue(Tencent) to provide a version without change on change for easy review
Lei(Tencent) replies to Xiaowan Ke(vivo) and provides r08 without change on change for easy review.
Mukesh (MediaTek) provides v09.
Mukesh (MediaTek) provides r10
Chunshan(CATT) provides r11.
Lei(Tencent) provides comments and provide r12.
Mike (InterDigital) comments and provides r13
Saso (Intel) provides r14
Ellen (Google) comments and provides r15
Paul (Ericsson) provides comments
Chunshan(CATT) provides r16.
Lei(Tencent) provides comments and r17.
Lei(Tencent) asks to skip r17 and provide r18 for further review.
Hui(Huawei) provides r19.
Sudeep (Apple) comments on r19.
Saso (Intel) provides r20.
Paul (Ericsson) provides r21
Lei(Tencent) provides r22, fixing 'to CT3' to 'to RAN2'
Saso (Intel) provides r23.
Chunshan(CATT) provides r23.
Mike (InterDigital) comments and provides r24
==== Revisions Deadline ====
Dario (Qualcomm) can accept r21/r22/23 and objects to other revisions.
Youngkyo(Samsung) prefers r23
Devaki (Nokia) comments that we prefer r24, can live with r21, r22 (an earlier version, r03), objects to all other versions that go beyond TR conclusions.
Devaki (Nokia) comments that we can also live with r23.
Hui (Huawei) prefers r22, can live with r07/08, r23, objects to all other versions.
Saso (Intel) prefers r23, can live with r24, objects to all other versions.
Sudeep (Apple) prefers r23.
Chunshan(CATT) objects all the versions. Only after the 'PDU sets with different PDU Set QoS parameters (i.e. PSER and PSDB) are mapped to multiple QoS flows ' is removed from the r23/r24,the r23 or r24 can be accepted.
Lei(Tencent) thinks r23 is the most likely agreed revision, so may I ask if people is fine to go with r23 plus removing of 'PDU sets with different PDU Set QoS parameters (i.e. PSER and PSDB) are mapped to multiple QoS flows'. Otherwise, suggest to discuss this LS in CC#3 and CC#4.
Xiaowan Ke(vivo) is OK with r23 plus removing of 'PDU sets with different PDU Set QoS parameters (i.e. PSER and PSDB) are mapped to multiple QoS flows'.
Yali (OPPO) comments and suggests a sentence to address the concern of Chunshan.
Mukesh (MediaTek) is fine with r23 plus the removal of the multiple QoS sentence suggested by CATT.
Saso (Intel) replies to Yali (OPPO).
Lei(Tencent) uploads 'r23 plus the removal of the multiple QoS sentence' suggested by CATT as Mukesh(MediaTek) requested. Suggest to go with this if people are ok.
Yali (OPPO) replies to Saso (Intel).
Mike (InterDigital) prefers r24 and comments
Chunshan(CATT) replies to Saso (Intel).
Hui(Huawei) replies to Chunshan.
Chunshan(CATT) replies to Hui(Huawei).
Saso (Intel) replies to Chunshan; proposes to move forward with r23 as is; r24 is also fine
Paul (Ericsson) can accept r23, while we object to r24.
Chunshan(CATT) Is OK to r23 only after the deletion of the multiple QoS Flow description.
Lei(Tencent) agrees with Saso's view but for the sake of progress, is also fine to go with r23 with the sentence about multiple QoS flow deleted as uploaded in draft folder.
Lei(Tencent) requests to discuss this in CC#4 if 'r23 with the sentence about multiple QoS flow deleted as uploaded in draft folder' is not approved.
Lei(Tencent) thanks to Mike (InterDigital) 's cooperation spirit and think we can approve r23+ removing the sentence now.
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301378 LS OUT Approval Reply LS on PDU Set Handling SA WG2 Rel-18 Revision of S2-2300499r23, merging S2-2300337, S2-2300400, S2-2300732, S2-2300741, S2-2301013, S2-2301036, S2-2301094, S2-2301219 and S2-2300371. Approved Approved
9.12.2 S2-2300732 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling CATT Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300741 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling SAMSUNG Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301013 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling Apple Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
Sudeep (Apple) OK to consider this merged to 0499.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301036 LS OUT Approval [DRAFT] LS reply on PDU Set handling Huawei Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
Hui(Huawei) fine with merge into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301094 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling Intel Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301219 LS OUT Approval [DRAFT] Reply LS on PDU Set Handling InterDigital Inc. Rel-18 Response to S2-2300053. Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
Mike (InterDigital) is ok to mark this as MERGED into 0499
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300371 LS OUT Approval [DRAFT] LS on PDU Set Error Rate MediaTek Inc. Rel-18 Merged into S2-2301378 Lei(Tencent) comments and based on some offline discussion, suggest to merge this tdoc into 0499
Mukesh (MediaTek) replies to Lei (Tencent) 0371 is not a reply LS on PDU Set handling and therefore should not be merged into 0499.
Dario (Qualcomm) proposes to solve the issue in SA2.
Lei(Tencent) replies there is also related question in 1094
Devaki (Nokia) also agrees that the questions should be resolved in SA2, do not see the need to ask RAN2 regarding PSER definition. Propose to note the LS at this time, work on a resolution for the next meeting.
Hui (Huawei) supports to resolve the issue in SA2 since we defines the mechanism.
Dan (China Mobile) supports to resolve the PSER in SA2.
Saso (Intel) supports to seek feedback on PSER from RAN WGs, as proposed in 0371, but piggybacked in the general reply LS on PDU Set handling.
Mukesh (MediaTek) agrees to merge this LS into 0499.
Lei(Tencent) replies to Mukesh (MediaTek) and fine to mark this tdoc as merged into 0499. And would like to highlight that the Question can only be piggy back to 0499 as long as people agrees.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301217 DISCUSSION Discussion Discussion on Using PDU Set Importance. InterDigital, Inc Rel-18 Noted Dario (Qualcomm) comments
Mike (InterDigital) replies to Dario (Qualcomm)
Sudeep (Apple) shares the same view as Dario (Qualcomm).
John (Futurewei) has same view as Dario (Qualcomm).
Saso (Intel) supports the view from John (Futurewei) and Dario (Qualcomm).
==== Revisions Deadline ====
Saso (Intel) replies to Mike.
==== Final Comments Deadline ====
Noted
9.12.2 S2-2300962 DISCUSSION Discussion Clarification on PDU-set information marking in a QoS Flow with PDU-set QoS requirements. Lenovo Noted Dario (Qualcomm) comments
Yali(OPPO) asks question to Dario (Qualcomm)
Dimitris (Lenovo) responds to Dario (QCOM)
Hui(Huawei) provides comments
Chunshan(CATT) provides comments on Hui(Huawei).
Hui(Huawei) replies to Chunshan.
Saso (Intel) comments that handling of untagged packets should not be an issue.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.12.2 S2-2300372 DISCUSSION Discussion Discussion on PDU Set Error Rate. MediaTek Inc. Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.12.2 S2-2300419 CR Approval 23.501 CR3896 (Rel-18, 'B'): Update TS23.501 to reflect conclusion of KI#4 for XRM in TR23.700-60 Nokia, Nokia Shanghai Bell Rel-18 r21 removing EN agreed. Revised to S2-2301379, merging S2-2301242, S2-2300544 and S2-2300373. Chris Joul (T-Mobile USA) Agrees with proposal to use this doc as baseline and provides comments
Dan (China Mobile) provide guidance for KI#4&5 of TS 23.501 CR that to take S2-2300419(this paper) as baseline paper for general part description.
Zhuoyun (Tencent) asks questions for clarification.
Saso (Intel) suggests an EN for uplink handling.
Yali(OPPO) comments
Hui (Huawei) provides comments.
Paul (Ericsson) provides r01
Mukesh (MediaTek) provides r02.
Mike (InterDigital) comments and provides r03
Dario (Qualcomm) comments and provides r04.
Devaki (Nokia) provides r05 with minor updates on top of r04.
Youngkyo(Samsung) provide comments and provides r06.
Haley(Lenovo) provides r07 by merging the content of S2-2300544.
Hui(Huawei) provide r08 to avoid conflicts with 1039.
Zhuoyun (Tencent) provides r09 based on r08.
Dan(China Mobile) provides r10 based on r09.
Yali(OPPO) provides r11 based on r10.
Chunshan(CATT) provides r12 based on r11.
Haley(Lenovo) provides r13 based on r12.
Xiaowan Ke(vivo) provides r14
Mike (InterDigital) comments and provides r15
Ellen (Google) provides r16
Youngkyo(Samsung) provides r17.
Hui ((Huawei provides r18
Saso (Intel) asks a question on 'PSH-support' capability.
Haley (Lenovo) replies to Saso (Intel).
Chris(Vodafone) adds further reply to Saso (Intel).
Saso (Intel) provides r19.
Dario (Qualcomm) comments and provides r20
Chris (Vodafone) says we need to support non-homogeneous RAN - so R20 may need further work
Paul (Ericsson) provides r21
Yali (OPPO) comments on r20.
==== Revisions Deadline ====
Haley (Lenovo) also accepts r20 with EN 'Editor Note: whether and how to introduce a PDU set handling capability of RAN capability indication is FFS'.
Hui(Huawei) supports r22 or r22+EN on protocol Desc. Cannot accept r20 as it use 'PDU Set QoS Characteristics' as discussed in 1039.
Yali(OPPO) also supports r22 or r22+EN on protocol Desc. Cannot accept r20.
Zhuoyun (Tencent) prefers r22+EN on protocol Desc.
Mike (InterDigital) objects to r21, comments that no r22 seems to be available, and comments that he is ok with r21 if the EN on How PDU Set Importance is interpreted is interpreted is reinserted.
Saso (intel) replies to Mike (InterDigital).
Mike (InterDigital) thanks Devaki (Nokia) for pointing him to r22 and comments that he is ok with r22 + 'Editor's Note: Whether and how PDU Set Importance is interpreted across QoS Flows is FFS'
Mike (InterDigital) replies to Saso (Intel)
Paul (Ericsson) provides late r23.
Mike (InterDigital) provides late r24
Devaki (Nokia) provides a summary of changes on top of r21 (provided prior to revision deadline) for chair's notes:
1. Removes the capability indication paragraph.
2. Adds Editor's Note: Whether the Protocol Description belongs to the existing Flow Description or is standalone IE is FFS.
3. Adds Editor's Note: Whether and how PDU Set Importance is interpreted across QoS Flows is FFS
==== Final Comments Deadline ====
Paul (Ericsson) can't accept the addition of Editor's Note: Whether and how PDU Set Importance is interpreted across QoS Flows is FFS.
Mike (InterDigital) provides justification for the EN
Haley(Lenovo) can not accept revision without EN for PSH capability
Devaki (Nokia) comments that I agree with Saso and Mike that this is a detail which needs specification during normative phase, thus not a continuation of study IMHO.
Revised
9.12.2 S2-2301379 CR Approval 23.501 CR3896R1 (Rel-18, 'B'): Update TS23.501 to reflect conclusion of KI#4 for XRM in TR23.700-60 Nokia, Nokia Shanghai Bell, InterDigital Inc., Huawei Rel-18 Revision of S2-2300419r21 removing EN, merging S2-2301242, S2-2300544 and S2-2300373. Approved. Vodafone comment recorded Agreed
9.12.2 S2-2301039 CR Approval 23.501 CR4046 (Rel-18, 'B'): Support of PDU Set based handling Huawei, HiSilicon, China Mobile, Lenovo, KDDI Rel-18 CC#4: r30 + changes agreed. Revised to S2-2301472. Hui (Huawei) provide r01, which merged other related papers.
Dan (China Mobile) provide guidance for KI#4&5 of TS 23.501 CR that to take S2-2301039(this paper) as baseline paper for other impacted clauses.
Chunshan (CATT) provide r02.
Youngkyo(Samsung) asks questions for clarification.
Zhuoyun (Tencent) asks questions for clarification.
Hui(Huawei) asks questions on r02.
Chunshan (CATT) provides clarification to Zhuoyun (Tencent).
Haley (Lenovo) replies to Zhuoyun(Tencent)
Hui (Huawei) replies comments.
Chunshan(CATT) provides clarification to Hui(Huawei).
Hui(Huawei) replies to Chunshan and provide r03
Chunshan(CATT) replies to Hui(Huawei) .
Yali(OPPO) provides comments on r03
Curt (Meta) asks a question w.r.t when PSDB is not available. Probably this Q is for Saso (intel).
Xiaowan Ke(vivo) provides r04
Saso (Intel) replies to Curt. Also one comment on r04
Mukesh (MediaTek) seek clarification of PSDB and PSER.
Dario (Qualcomm) points out there is a lot of overlap between 1039 and 0419 and that 1039 should be merged into 0419.
Youngkyo(Samsung) provides comment.
Hui(Huawei) replies to Yali.
Hui (Huawei) provided r05 to address comments and also sync some revision in 419 on QoS parts.
Devaki (Nokia) provides r06 to remove overlaps (also removes changes copied from 419 and its revisions) with 419, cannot accept earlier revisions.
Hui (Huawei) suggest to continue with r05 since r06 didn't follow the baseline assignment. And the contents removed from r06 addressing comments on QoS profile was not copied from 419.
Chunshan(CATT) provides r07 based on r05.
Youngkyo(Samsung) provides r08.
Dan(China Mobile) provides comments.
Hui(Huawei) provides r09.
Hui(Huawei) replies to chunshan.
Yali(OPPO) provides r11.
Paul (Ericsson) provides comments and questions for clarification.
Chunshan (CATT) provides r10.
Hui(Huawei) replies to Paul and provide r12 based on r10.
Hui(Huawei) provide r13 to merge some changes from r11.
Chunshan(CATT) provide r14.
Paul (Ericsson) provides comments and questions to Hui (Huawei).
Chunshan(CATT) provides response comments to Paul (Ericsson).
Hui (Huawei) provides further replies to Paul.
Hui (Huawei) asks Chunshan for clarification on the proposal.
Xiaowan Ke(vivo) provides r15 and comment
Paul (Ericsson) provides response to Chunshan (CATT)
Mike (InterDigital) comments and provides r16
Saso (Intel) seeks clarification on the expired draft-ietf-avtext-framemarking-13: 'Frame Marking RTP Header Extension' and the related Annex X.3.
Mukesh (MediaTek) responds to Saso (Intel)
Kenichi (KDDI) provides r17
Youngkyo(Samsung) questions on update of r16 from Mike (InterDigital)
Chunshan(CATT) provides response to Paul (Ericsson).
Chunshan(CATT) provides r18 based on r17.
Yali(OPPO) comments on r18.
Hui(Huawei) asks for clarification before discuss the NOTE.
Sudeep (Apple) also has the same question on the NOTE on 'XR stream'.
Devaki (Nokia) provides r19.
Hui (Huawei) provides r20.
Xiaowan Ke(vivo) provides r21
Mukesh (MediaTek) provides r23 which replaces r22.
Mukesh (MediaTek) provides r24 which replaces r22 and r23.
Paul (Ericsson) provides r25
Mukesh (MediaTek) provides r26.
Hui (Huawei) provides r27.
Yali(OPPO) provides r28 based on r27.
Hui(Huawei) asks question to Mike.
Dario (Qualcomm) comments and provides r31
Xiaowan Ke(vivo) provides r30
Hui(Huawei) provides r29 based on r28.
Saso (Intel) provides r32 on top of r31.
Hui (Huawei) provides comments to r32 and r31.
==== Revisions Deadline ====
Yali (OPPO) comments on r32 and r31.
Dan(China Mobile)(Rapportuer ) resend: vivo provides r33 without 3GPP ack, and forwarding this email, which is within the revision deadline.
Xiaowan Ke(vivo) disagrees r25, 26, r27, r28, r29, r31, r32 and propose to agree r30 (WRT r33 is not captured in the Chairman note although it is sent on time but rejected by 3GPP server)
Dario (Qualcomm) prefers r31 but, as a compromise, can accept r32. Objects to all other revisions (including r33).
Yali (OPPO) supports r28 to r30, and r33(if it can be taken into account), objects to r26, r27, r31, r32.
Hui(Huawei) provides draft r34v1.
Devaki (Nokia) comments that we can live with r34v1 (unclear why this is v1 but that is editorial) only without the EN 'Editor's Note: The definition of AN PSDB is FFS' or it shall be amended as follows: 'Editor's Note: The need for AN PSDB and definition of AN PSDB is FFS.
Hui(Huawei) replies to Devaki.
Chunshan(CATT) a) comments that we can live with r34v1 only with changing 'Editor's Note: it is FFS how to count PSER when the a PDU Set is delayed more than PSDB with regard the maximum duration threshold is met or not. ' to 'Editor's Note: it is FFS how to count PSER when the PDU of PDU Set is delayed more than PSDB with regard the maximum duration threshold is met or not.'
Hui (Huawei) provides draft r34v2.
Mukesh (MediaTek) can live with r34r2, only with 'Editor's Note: [XRM] The definition of PSER is pending RAN feedback' reinstated. Object to all other revisions without this EN.
Saso (Intel) requests addition of an EN from r24 in draft r34v2.
Xiaowan(vivo) replies to Hui(Huawei)
Chunshan (CATT) can live with r34r2, only with 'For a QoS Flow supporting PDU Set, the QoS Profile includes the PDU Set QoS Parameters described in this clause in addition to the PDU QoS Characteristics (see clause 5.7.3.1). ' is changed to 'For a QoS Flow supporting PDU Set, the QoS Profile includes the PDU Set QoS Parameters described in this clause in addition to the PDU QoS profile (see clause 5.7.1.2).'
Hui (Huawei) provides r34r3
Chunshan (CATT) accepts the r34v3 (not r34r3) with the typo correction from 'For a QoS Flow supporting PDU Set, the QoS Profile includes the PDU Set QoS Parameters described in this clause in addition to the PDU QoS Profile (see clause 5.7.3.2)' to 'For a QoS Flow supporting PDU Set, the QoS Profile includes the PDU Set QoS Parameters described in this clause in addition to the PDU QoS Profile (see clause 5.7.1.2)''
Hui (Huawei) provides r34 and asks to discuss on CC#3.
Dario (Qualcomm) can only accept r34 w/o Annex and reference to it.
Paul (Ericsson) can accept r34v2
==== Final Comments Deadline ====
Hui (Huawei) asks people to check final r34.
Revised
9.12.2 S2-2301472 CR Approval 23.501 CR4046R1 (Rel-18, 'B'): Support of PDU Set based handling Huawei, HiSilicon, China Mobile, Lenovo, KDDI, Nokia, Nokia Shanghai Bell, OPPO, InterDigital Inc., Samsung, Tencent, Intel, ZTE Rel-18 Revision of S2-2301039r30 + changes. Approved Agreed
9.12.2 S2-2300336 CR Approval 23.501 CR3876 (Rel-18, 'B'): Introduction of support for PDU Set handling Ericsson Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper to merge 5.37.X part into 0419 and merge other impacts clause to 1039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301218 CR Approval 23.501 CR4094 (Rel-18, 'B'): Considering PDU Set Importance when Setting a Priority Level InterDigital Inc. Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper can be merged into 1039, and take the discussion in 1039 email list
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301242 CR Approval 23.501 CR4098 (Rel-18, 'B'): Support for PDU Set QoS Framework Qualcomm Incorporated Rel-18 Merged into S2-2301379 Dan (China Mobile) suggest this paper to merge general part into 0419 and merge other impacts clause to 1039.
Dario (Qualcomm) is fine with merging this contributions into 00419.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301214 CR Approval 23.501 CR4093 (Rel-18, 'B'): PDU Set handling in NG-RAN in absence of PSDB Intel Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper merged into S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301181 CR Approval 23.501 CR4082 (Rel-18, 'B'): Support of PDU Set based QoS handling ZTE Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper merged into S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301082 CR Approval 23.501 CR4055 (Rel-18, 'B'): Functional Description for PDU Set QoS Control CATT Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper merged into S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300964 CR Approval 23.501 CR4025 (Rel-18, 'B'): PDU set information marking in a QoS flow Lenovo, Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper merged into S2-2301039.
==== Revisions Deadline ====
Dimitris (Lenovo) suggests to mark this CR as postponed
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300758 CR Approval 23.501 CR3978 (Rel-18, 'B'): (KI #4&5) modification on QoS description for PDU set based mechanism Samsung Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest this paper to merge general part into 0419 and merge other impacts clause to 1039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300492 CR Approval 23.501 CR3920 (Rel-18, 'B'): Introduction of PDU Set Information identification OPPO Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest to merge this paper to S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300456 CR Approval 23.501 CR3907 (Rel-18, 'B'): PDU Set identification for different service protocol information KDDI, Huawei Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest to merge this paper to S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300544 CR Approval 23.501 CR3932 (Rel-18, 'B'): PDU set handling capability of RAN node Lenovo, CATT Rel-18 Merged into S2-2301379 Dan (China Mobile) suggest to merge this paper to S2-2300419.
Haley (Lenovo) agrees to merge this paper to S2-2300419.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300457 CR Approval 23.501 CR3908 (Rel-18, 'B'): PDU Set related information provisioning by AF KDDI Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest to merge this paper to S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300399 CR Approval 23.501 CR3890 (Rel-18, 'B'): Introduction of PDU Set QoS Vivo Rel-18 Merged into S2-2301472 To be merged into S2-2301039 (For CC#4) Dan (China Mobile) suggest to merge this paper to S2-2301039.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300373 CR Approval 23.501 CR3884 (Rel-18, 'B'): DL PDU Set Handling MediaTek Inc. Rel-18 Merged into S2-2301379 Dan (China Mobile) suggest to merge this paper to S2-2300419.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301243 CR Approval 23.503 CR0891 (Rel-18, 'B'): Support for PDU Set QoS Framework Qualcomm Incorporated Rel-18 Postponed Dan (China Mobile) suggest to use this paper as baseline for TS 23.503 CRs.
Dario (Qualcomm) comments, asks questions and provides r01
Youngkyo(Samsung) provides answer to Dario (Qualcomm)
Chunshan(CATT) provides r02 to merge paper S2-2300740.
Xiaowan(vivo) provides comments
Yali(OPPO) has the same view as Xiaowan(vivo)
Hui(Huawei) provides r03 based on r01
Sudeep (Apple) provides r04.
Dario (Qualcomm) replies to Chunshan and Youngkyo.
Chunshan (CATT) provides clarification to Dario (Qualcomm) and provides r06
Xiaowan Ke(vivo) comments r05 and provides r06. but it doesn't mean we accept r06 since my comments are not totally fixed due to deadline arrival
Chunshan(CATT) provides response to Hui(Huawei).
Hui(Huawei)asks for clarification.
Chunshan(CATT) provides r05 and provides response to Yali and Xiaowan.
Chunshan (CATT) provides clarification to Dario (Qualcomm) and provides r07 based on r06 from vivo
==== Revisions Deadline ====
Dario (Qualcomm) can accept r00/01/03/04 and objects to others.
Xiaowan Ke(vivo) disagree all the revisions and the original version
Chunshan (CATT) can accept r02, r05, r06,r07 and objects r00, r01,r03, r04.
Hui(Huawei) replies to Chunshan(CATT).
Hui (Huawei) can accept r03, r04, objects all other versions.
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300770 CR Approval 23.503 CR0854 (Rel-18, 'B'): Support for PDU Set QoS Framework Samsung Rel-18 Postponed To be merged into S2-2301243 (Postponed) Dan (China Mobile) suggest to merge this paper to S2-2301243.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300740 CR Approval 23.503 CR0852 (Rel-18, 'B'): Policy Control for PDU Set QoS Control CATT Rel-18 Postponed To be merged into S2-2301243 (Postponed) Dan (China Mobile) suggest to merge this paper to S2-2301243.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300497 CR Approval 23.502 CR3738 (Rel-18, 'B'): AF Session procedures update to support PDU Set QoS Parameters Futurewei Rel-18 r06 agreed. Revised to S2-2301380, merging S2-2300458 Dan (China Mobile) suggest to use this paper as baseline for TS 23.502 CRs.
John (Futurewei) merges updates in S2-2300458 and provides r01
Dario (Qualcomm) comments and provides r02.
John (Futurewei) agrees and provides r03.
Zhuoyun (Tencent) provides r04 and also co-sign this contribution.
Xiaowan Ke(vivo) provides comment
Hui (Huawei) provides r05.
Xiaowan Ke(vivo) provides r06
John (Futurewei) asks question to Xiaowan (Vivo)
Xiaowan Ke(vivo) replies to John (Futurewei)
John (Futurewei) provides clarification and r07.
==== Revisions Deadline ====
Dan(China Mobile) suggest to go with r06.
John (Futurewei) is ok to go with r06.
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301380 CR Approval 23.502 CR3738R1 (Rel-18, 'B'): AF Session procedures update to support PDU Set QoS Parameters Futurewei, KDDI, Tencent Rel-18 Revision of S2-2300497r06, merging S2-2300458. Approved Agreed
9.12.2 S2-2300458 CR Approval 23.502 CR3728 (Rel-18, 'B'): PDU Set related information provisioning for Nnef_AFsessionWithQoS service KDDI Rel-18 Merged into S2-2301380 Dan (China Mobile) suggest to merge this paper to S2-2300497.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 - - - KI#6 - - Docs:=9 -
9.12.2 S2-2300487 CR Approval 23.501 CR3919 (Rel-18, 'B'): Introduction of KI#6 conclusion: uplink-downlink transmission coordination OPPO, Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell Rel-18 r07 agreed. Revised to S2-2301381, merging S2-2300397 Xiaowan Ke(vivo) comment and provides r01
Lei(Tencent) /rapporteur comments that this paper can be taken as baseline for 23.501 CR of KI#6 (resend with updated AI# in e-mail title).
Lei(Tencent) /rapporteur comments that this paper can be taken as baseline for 23.501 CR of KI#6.
Boren (OPPO) replies to Xiaowan Ke (vivo)
Xiaowan Ke(vivo) replies to Boren (OPPO)
Saubhagya (Nokia) comments and provides r02.
Paul (Ericsson) provides comments and has concerns on progressing this CR in this meeting.
Saubhagya (Nokia) responds to Paul's comment.
Boren (OPPO) replies to Paul (Ericsson) and provides r03.
Boren (OPPO) provides r04.
Paul (Ericsson) provides r05.
Boren (OPPO) provides r06.
Boren (OPPO) provides r07.
==== Revisions Deadline ====
Jinhua (Xiaomi) provide comments, r04 is OK, can live with r05/07 removing the last EN.
Boren (OPPO) prefers r04. R07 removing the last EN is also OK
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301381 CR Approval 23.501 CR3919R1 (Rel-18, 'B'): Introduction of KI#6 conclusion: uplink-downlink transmission coordination OPPO, Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, vivo, Huawei, Xiaomi Rel-18 Revision of S2-2300487r07, merging S2-2300397. Approved Agreed
9.12.2 S2-2300397 CR Approval 23.501 CR3889 (Rel-18, 'B'): Introduction of Round-Trip delay requirements Vivo Rel-18 Merged into S2-2301381 Lei(Tencent) /rapporteur comments that this paper can be merged into 0487.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301040 CR Approval 23.503 CR0878 (Rel-18, 'B'): Support of UL/DL transmission coordination to meet RT latency requirements Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2301382, merging S2-2300491 and S2-2300835 Saubhagya (Nokia) comments and provides r01.
Lei(Tencent) /rapporteur comments that this paper can be taken as baseline for 23.503 CR of KI#6.
Boren (OPPO) comments and provides r02.
Dario (Qualcomm) provides r03.
Xiaowan Ke(vivo) provides r01
Xiaowan Ke(vivo) provides r04
Jinhua (Xiaomi) provides comments and r05.
Hui (Huawei) provides r06
Hui (Huawei) provides r08
Paul (Ericsson) provides r07
Boren (OPPO) provides r09
==== Revisions Deadline ====
Saubhagya (Nokia) comments.
Saubhagya (Nokia) prefers the r06 and object to all other revisions.
Jinhua (Xiaomi) provides comments,
Boren (OPPO) prefers r06.
Xiaowan(vivo) also prefers r06
Lei(Tencent) also prefers r06
==== Final Comments Deadline ====
Paul (Ericsson) we can live with r07, r08 and r09, but object to all other revisions. Please take S2-230190 to CC#4.
Revised
9.12.2 S2-2301382 CR Approval 23.503 CR0878R1 (Rel-18, 'B'): Support of UL/DL transmission coordination to meet RT latency requirements Huawei, HiSilicon,vivo, Xiaomi, OPPO, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301040r06, merging S2-2300491 and S2-2300835. Approved Agreed
9.12.2 S2-2300491 CR Approval 23.503 CR0838 (Rel-18, 'B'): Introduction of KI#6 conclusion: uplink-downlink transmission coordination OPPO Rel-18 Merged into S2-2301382 Lei(Tencent) /rapporteur comments that this paper can be merged into 1040.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300835 CR Approval 23.503 CR0863 (Rel-18, 'B'): XRM_KI#6_ RT latency of XRM service Xiaomi Rel-18 Merged into S2-2301382 Lei(Tencent) /rapporteur comments that this paper can be merged into 1040.
Jinhua (Xiaomi) replies, merged 0835 into 1040 is OK.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300488 CR Approval 23.502 CR3736 (Rel-18, 'B'): Introduction of KI#6 conclusion: uplink-downlink transmission coordination OPPO, Tencent, Tencent Cloud Rel-18 r08 agreed. Revised to S2-2301383. Lei(Tencent) /rapporteur comments that this paper can be taken as baseline for 23.502 CR of KI#6.
Dario (Qualcomm) asks question for clarification.
Boren (OPPO) replies to Dario (Qualcomm), and provides r01.
Saubhagya (Nokia) comments and provides r02.
Boren (OPPO) provides r03.
Jinhua (Xiaomi) provides comments and r04.
Saubhagya (Nokia) comments on r04.
Xiaowan Ke(vivo) provides r05
Boren (OPPO) provides r06.
Boren (OPPO) provides r08.
Lei(Tencent) comments
Paul (Ericsson) provides r07
==== Revisions Deadline ====
Boren (OPPO) prefers r06, can live with r08, object to r07.
Saubhagya (Nokia) comments; prefers r06, can live with r08, object r07.
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301383 CR Approval 23.502 CR3736R1 (Rel-18, 'B'): Introduction of KI#6 conclusion: uplink-downlink transmission coordination OPPO, Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, Xiaomi, vivo Rel-18 Revision of S2-2300488r08. Approved Agreed
9.12.2 - - - KI#7 - - Docs:=4 -
9.12.2 S2-2300283 CR Approval 23.501 CR3792R1 (Rel-18, 'B'): PCF support of 5GS jitter value monitoring based on QoS monitoring mechanism and exposed to AF China Mobile, Tencent, Samsung, Nokia Nokia Shanghai Bell Rel-18 Revision of S2-2210587. CC#4: r04 + changes agreed. Revised to S2-2301473. Dario (Qualcomm) comments.
Dan (China Mobile) provide r01 to reflect Dario's comment.
Dan (China Mobile) provide r02 to keep alignment with 503 with removing sample frequency.
Paul (Ericsson) provides comments/questions and raises concern regarding progressing that CR at this meeting.
Dan (China Mobile) provides response and provide r03
Lei(Tencent) provides comments and support Dan (China Mobile) revisions
Paul (Ericsson) provides r04
Dan(China Mobile) provides r05 with removing the EN which is not clear for me.
==== Revisions Deadline ====
Saubhagya (Nokia) prefer r03, and object to all other revision.
Dan (China Mobile) prefer r03
Dan (China Mobile) prefer r03, request to discuss this in CC#3&CC#4
Dan (China Mobile) give a suggestion that, we call the term as 'packet delay associated jitter'
Saubhagya (Nokia) Agrees with Dan's (China Mobile) suggestion.
Dan(China Mobile) provide r06 based on r05, the change is r05+ replace 'Packet Delay Variance' into 'packet delay associated jitter',please check whether this is ok
Dario (Qualcomm) can only accept r04 (objects to others)
Dan (China Mobile) check with Dario whether it is ok for r05+replace 'Packet Delay Variance' into 'packet delay associated jitter'+EN:'Editor's Note: Whether all QoS monitoring needs can be addressed with the limitation of one QoS Monitoring control information per PCC rule is FFS'
Saubhagya (Nokia) objects to r04. OK with r03
Dan (China Mobile) r07, that is r04+changing 'variance' to 'variation'+remove'RT'.Please check whether we can endorse this.
Dan (China Mobile) request this for CC#4
==== Final Comments Deadline ====
Dan (China Mobile) propose to try to approve the version of r04+changing 'variance 'to 'variation'+remove'RT'+adding 'EN:whether the round-trip delay can be used to generate Packet Delay Variation is FFS'
Saubhagya (Nokia) OK with the proposed EN by Dan (China Mobile)
Dan (China Mobile) provide r08=r04+changing 'variance 'to 'variation'+remove'RT'+adding 'EN:whether the round-trip delay can be used to generate Packet Delay Variation is FFS'
Revised
9.12.2 S2-2301473 CR Approval 23.501 CR3792R2 (Rel-18, 'B'): PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF China Mobile, Tencent, Samsung, Nokia Nokia Shanghai Bell Rel-18 Revision of S2-2300283r04 + changes. Approved Agreed
9.12.2 S2-2300284 CR Approval 23.503 CR0781R1 (Rel-18, 'B'): PCF support of 5GS jitter value monitoring based on QoS monitoring mechanism and exposed to AF China Mobile, Tencent, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2210593. CC#4: r02 + changes agreed. Revised to S2-2301474. Dario (Qualcomm) provides same comments as for 0283 plus additional ones.
Dan(China mobile) reply and provide r01
Paul (Ericsson) provides r02
==== Revisions Deadline ====
Saubhagya (Nokia) prefer r01, and object to all other revision.
Lei(Tencent) prefer r01 and can also live with r02.
Dan(China Mobile) prefer r01, request to discuss this on CC#3&CC#4
Dan(China Mobile) provide r03, that is r02+ replace 'Packet Delay Variance' into 'packet delay associated jitter',please check whether this is ok
Dario (Qualcomm) prefers r02, but points out dependency on 0283.
Dan(China Mobile) provide r04, that is r02+changing 'variance' to 'variation'+remove'RT'.Please check whether we can endorse this.
Dan(China Mobile) request for CC#4
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301474 CR Approval 23.503 CR0781R2 (Rel-18, 'B'): PCF support of 5GS Packet Delay Variation value monitoring based on QoS monitoring mechanism and exposed to AF China Mobile, Tencent, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300284r02 + changes. Approved Agreed
9.12.2 - - - KI#8 - - Docs:=15 -
9.12.2 S2-2300042 LS In Action LS from RAN WG1: Draft reply LS on XR and Media Services RAN WG1 (R1-2212994) Rel-18 Responses drafted in S2-2300391, S2-2300496, S2-2301246, S2-2300338. Final response in S2-2301384 Replied to
9.12.2 S2-2300391 LS OUT Approval [DRAFT] LS reply on reply LS on XR and Media Services vivo Response to S2-2300042. r02 agreed. Revised to S2-2301384, merging S2-2300496, S2-2301246 and S2-2300338 Xiaowan Ke(vivo) seeks clarification from Boren (OPPO)
Boren (OPPO) comments.
Xiaowan Ke(vivo) provides r01 to merge LS replies for RAN1 LS in (S2-2300042)
Boren (OPPO) replies to Xiaowan Ke(vivo)
Dario (Qualcomm) comments and provide r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301384 LS OUT Approval LS reply on reply LS on XR and Media Services SA WG2 Revision of S2-2300391r02, merging S2-2300496, S2-2301246 and S2-2300338. Approved Approved
9.12.2 S2-2300496 LS OUT Approval [DRAFT] Reply LS on XR and Media Services OPPO Response to S2-2300042. Merged into S2-2301384 Xiaowan Ke(vivo) suggests to merge this paper into S2-2300391
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301246 LS OUT Approval [DRAFT] Reply LS on XR and Media Services Qualcomm Incorporated Rel-18 Response to S2-2300042. Merged into S2-2301384 Xiaowan Ke(vivo) suggests to merge this paper into S2-2300391
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300338 LS OUT Approval [DRAFT] Reply to Draft reply LS on XR and Media Services Ericsson Rel-18 Response to S2-2300042. Merged into S2-2301384 Xiaowan Ke(vivo) suggests to merge this paper into S2-2300391
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300335 CR Approval 23.501 CR3875 (Rel-18, 'B'): Introduction of support for Jitter Measurement and End of Data Burst reporting to the NG-RAN Ericsson Rel-18 r14 agreed. Revised to S2-2301385, merging S2-2301244, S2-2301041, S2-2301269, S2-2300395, S2-2300374 and S2-2301315 Boren (OPPO) comments and provides r02
Lei(Tencent) /rapporteur comments that this paper can be baseline for 501 CR for KI#8.
Mike (InterDigital) comments and provides r01
Paul (Ericsson) provides r03
Xiaowan Ke(vivo) provides r04
zhendong (ZTE) provides r06.
Jaehyeon (Samsung) agrees with zhendong (ZTE).
Xiaowan Ke(vivo) provides r07 and comments
Dario (Qualcomm) expresses concerns with proceeding with this paper as baseline.
zhendong (ZTE) provides response to qualcomm.
Jaehyeon (Samsung) provides comment to xiaowan.
Curt (Meta) objects to AF providing Jitter value (again).
Jaehyeon (samsung) replies to Curt (Meta).
Dan (China Mobile) provide r08
Dan (China Mobile) replies to Jaehyeon and Curt.
Xiaowan (vivo) relies to Jaehyeon (Samsung) that 'AF provided jitter information' has been rule out due to official voting in 154 F2F meeting.
Chunshan (CATT) provides r09.
Paul (Ericsson) provides r10
Mike (InterDigital) comments and provides r11
Paul (Ericsson) provides comments and question for clarification.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) is OK with r10.
Mike (InterDigital) replies
Paul (Ericsson) replies to Mike (InterDigital)
Xiaowan Ke(vivo) comments and provides r12
Hui (Huawei) provides r13.
Tezcan (Samsung) replies to Paul (Ericsson) and Xiaowan (vivo), and provides r14.
Dario (Qualcomm) provides r15.
Chunshan(CATT) provides r15.
==== Revisions Deadline ====
Dario (Qualcomm) can only accept r15 (email sent before the deadline) and objects to others).
Hui (Huawei) can only accept r13,14,15 and objects other versions.
Curt (Meta) supports Qualcomm and can only accept r15.
zhendong (ZTE) can live with r15
Dario (Qualcomm) for clarity: r15 = r14 with following changes; 1) clarification that jitter = N6 jitter; 2) add 'Editor's Note: whether the Periodicity and associated N6 Jitter information is provided via TSCAI or via a new specific container for CDRX assistance information is FFS.' In 5.4.X.2; 3) removal of any reference to TSCAI/TSCAC in 5.4.X.2; 4) remove all changes in 5.27.2.1
==== Final Comments Deadline ====
Revised
9.12.2 S2-2301385 CR Approval 23.501 CR3875R1 (Rel-18, 'B'): Introduction of support for Jitter Measurement and End of Data Burst reporting to the NG-RAN Ericsson, vivo, China Mobile, ZTE Rel-18 Revision of S2-2300335r14, merging S2-2301244, S2-2301041, S2-2301269, S2-2300395, S2-2300374 and S2-2301315. Approved Agreed
9.12.2 S2-2301244 CR Approval 23.501 CR4099 (Rel-18, 'B'): Enhancements to power savings based on CDRX optimization Qualcomm Incorporated Rel-18 Merged into S2-2301385 Lei(Tencent)/rapporteur suggests this paper to be merged into 0335.
Dario (Qualcomm): before merging to 0335 issues need to be addressed.
Xiaowan(vivo) agree with to Dario (Qualcomm)
==== Revisions Deadline ====
Dario (Qualcomm) if 0335r15 is not agreed/endorsed, I propose to discuss this during CC#3 or CC#5.
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301041 CR Approval 23.501 CR4047 (Rel-18, 'B'): Support of power saving for XRM services Huawei, HiSilicon Rel-18 Merged into S2-2301385 Lei(Tencent) /rapporteur comments that this paper can be merged into 0335.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301269 CR Approval 23.501 CR4102 (Rel-18, 'B'): KI#8: TSCAI/TSCAC modifications to support enhancements to power savings for XR services Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301385 Lei(Tencent) /rapporteur comments that this paper can be merged into 0335.
Georgios Gkellas (Nokia, Nokia Shanghai Bell) Yes, agree to merge 1269 to 0335
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300395 CR Approval 23.501 CR3888 (Rel-18, 'B'): Introduction of KI#8 concl: Power Saving related Vivo Rel-18 Merged into S2-2301385 Lei(Tencent) /rapporteur comments that this paper can be merged into 0335. Would to highlight that 5.37.x in this CR look nice and encourage to merge at least this part to 0335 especially.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300374 CR Approval 23.501 CR3885 (Rel-18, 'B'): Enhancements to UE power saving for XR MediaTek Inc. Rel-18 Merged into S2-2301385 Lei(Tencent)/rapporteur suggests this paper to be merged into 0335.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2301315 CR Approval 23.501 CR4111 (Rel-18, 'B'): Introduction of Power Saving requirements for XRM service Samsung Rel-18 Merged into S2-2301385 Lei(Tencent) /rapporteur comments that this paper can be merged into 0335.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.12.2 S2-2300394 CR Approval 23.503 CR0825 (Rel-18, 'B'): Introduction of Power Saving requirements for XRM service Vivo, China Mobile Rel-18 Technically Endorsed Lei(Tencent) /rapporteur comments that this paper can be taken as baseline for KI#8 503 CR.
Dario (Qualcomm) comments that before accepting this paper as baseline, we need to solve the issue on BAT vs. N6 jitter in the TSCAI raised with 00335.
==== Revisions Deadline ====
Dan(China Mobile) suggest to postponed this paper
Xiaowan Ke(vivo) propose to technical endorse this paper. Since the original version aligns with 00335. 'The traffic characteristics information is provided by the AF to the PCF via NEF or to the PCF directly when the AF is trusted.' Also TSCAI (between SMF and RAN) has no relationship with (AF-PCF) in 503.
Xiaowan Ke(vivo) is OK to technically endorse the paper without mentioning TSCAC in the cover page as requested by Dario (Qualcomm)
Dan(China Mobile) is fine technically endorsing the CR
Dario (Qualcomm) is fine w/ technically endorsing the CR, but Cover page should be updated to remove mentioning of TSCAC.
==== Final Comments Deadline ====
Endorsed
9.12.2 - - - KI#9 - - Docs:=4 -
9.12.2 S2-2300839 CR Approval 23.501 CR3990 (Rel-18, 'B'): Add the descriptions for reference of KI#6 and KI#9 to support the XRM service. Xiaomi, InterDigital Inc. Rel-18 Postponed Jinhua (Xiaomi) provides r01.
Dan (China Mobile) comments whether this paper can be merged into S2-2300241, and suggest the common ID should be removed
Lei (Tencent) provides comments.
Jinhua (Xiaomi) replies to Lei and Dan.
Curt (Meta) - as commented in 1216, needs some more details on how this SLA before agreeing to this CR set.
Dario (Qualcomm) comments.
Jinhua (Xiaomi) replies to Curt and Dario.
Dan (China Mobile) replies.
Jinhua (Xiaomi) replies,
Jinhua (Xiaomi) provides r02,
==== Revisions Deadline ====
Curt (Meta) still prefers to postpone these set of CRs (including xx837 to 839). See thread on xx1216.
Dario (Qualcomm) supports Meta.
Jinhua (Xiaomi) replies to Dario and Curt, please check the clarification and revise proposal in thread on xx1216, thanks.
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2301216 CR Approval 23.503 CR0889 (Rel-18, 'B'): Supporting trade-off of QoE and power saving requirements Interdigital Inc. Rel-18 Postponed Jinhua (Xiaomi) provides comments, and r01,
Curt (Meta) wants to see an example on how this solution is supposed to work before documenting it with normative texts.
Mukesh (MediaTek) agrees with Curt (Meta).
Mike (InterDigital) replies to Mukesh (MediaTek) and Curt (Meta).
Mukesh (MediaTek) replies to Mike (InterDigital) and provides r02.
Dario (Qualcomm) thinks that the Media Codec information needs to be clearly specified.
Youngkyo(Samsung) has similar concern with Dario (Qualcomm).
Mike (InterDigital) is fine with r02, provides r03 to clarify a point, and replies to Dario (Qualcomm) and Youngkyo(Samsung)
Jinhua (Xiaomi) provide comments for clarification
Mukesh (MediaTek) is fine r03 provided by Mike (InterDigital)
Georgios Gkellas (Nokia, Nokia Shanghai Bell) is OK with r03
Jinhua (Xiaomi) replies to Mike, r03 is fine, Xiaomi co-sign it as 0837 merged in.
Curt (Meta) prefers to postone this set of CRs to next meeting as we need to have a better understanding on how to define this 'value representing a codec setting'.
Mike (InterDigital) replies to Curt (Meta) and provides r04 but still prefers r03
==== Revisions Deadline ====
Curt (Meta) still prefers to postpone these set of CRs (including xx837 to 839).
Dario (Qualcomm) supports Meta.
Jinhua (Xiaomi) provides comments for clarification, and revise proposal based on r04: 1) remove 'Media Codec Configuration Currently in Use', the NOTE 3 and the EN. 2) Add one EN as replace 'Editor's Note: Whether any other media codec information provided is FFS, and how to use it for the trade-off is FFS.'
Jinhua (Xiaomi) relies to Dario.
Mirko (Huawei) proposes to postpone.
Jinhua (Xiaomi) replies to Mirko,
Mike (InterDigital) replies to Mirko and Jinhua
Jinhua (Xiaomi )replies to Mike,
Mike (InterDigital) replies to Jinhua
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300837 CR Approval 23.503 CR0864 (Rel-18, 'B'): Codec Information Provision to PCF Xiaomi Rel-18 Postponed To be merged into S2-2301216 (Postponed) Dan (China Mobile) suggest to merge this paper to S2-2301216
Jinhua (Xiaomi) replies to Dan, merge 0837 into 1216 for further discussion is OK.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.12.2 S2-2300838 CR Approval 23.502 CR3798 (Rel-18, 'B'): XRM_KI#9_23.502 Codec Information Provision to PCF Xiaomi, InterDigital Inc. Rel-18 Postponed Curt (Meta) - as commented in 1216, needs some more details on how this can work with SLA before agreeing to this CR set.
Dario (Qualcomm): Media Codec Info needs to be clearly defined. Examples are not sufficient.
Jinhua (Xiaomi) replies to Dario and Curt,
Jinhua (Xiaomi) provides r01 to keep alignment,
==== Revisions Deadline ====
Curt (Meta) still prefers to postpone these set of CRs (including xx837 to 839). See thread on xx1216.
Dario (Qualcomm) supports Meta.
Jinhua (Xiaomi) replies to Dario and Curt, please check the clarification and revise proposal in thread on xx1216, thanks.
==== Final Comments Deadline ====
Postponed
9.12.2 - - - Documents exceeding TU budget - - Docs:=29 -
9.12.2 S2-2301316 CR Approval 23.502 CR3869 (Rel-18, 'B'): Procedures update to Power Saving requirements for XRM service Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301245 CR Approval 23.502 CR3862 (Rel-18, 'B'): Enhancements to power savings based on CDRX optimization Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301235 CR Approval 23.503 CR0890 (Rel-18, 'B'): 5GC provides periodicity and traffic jitter value to NG-RAN China Mobile, Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301222 CR Approval 23.502 CR3860 (Rel-18, 'B'): XRM_KI#1#2_ 23.502 Policy enhancement for multi-modality flows Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301042 CR Approval 23.502 CR3832 (Rel-18, 'B'): Support of power saving for XRM services Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301043 CR Approval 23.503 CR0879 (Rel-18, 'B'): Support of power saving for XRM services Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2301037 CR Approval 23.501 CR4045 (Rel-18, 'B'): 5GS information exposure Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300753 CR Approval 23.502 CR3785 (Rel-18, 'B'): Update TS23.502 to reflect conclusion of KI#3 for XRM in TR23.700-60 for the API based congestion exposure option Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300735 CR Approval 23.503 CR0850 (Rel-18, 'B'): Support Averaging Window in AF QoS request and Alternative QoS CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300994 CR Approval 23.501 CR4034 (Rel-18, 'B'): Introduction of a new standard SST for XRM China Mobile, Huawei, Hisilicon,Tencent Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300734 CR Approval 23.502 CR3781 (Rel-18, 'B'): Support Requested Averaging Window from AF CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300737 CR Approval 23.502 CR3782 (Rel-18, 'B'): RAN Bitrate Report via the Control Plane Path CATT, Lenovo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300822 CR Approval 23.503 CR0860 (Rel-18, 'B'): Implement the TR conclusion for KI#1, #2 in the specification and describe the required QoS enhancement. Huawei, HiSilicon Rel-18 Confirm CR Number - CR states xxxx! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300836 CR Approval 23.502 CR3797 (Rel-18, 'B'): XRM_KI#6_ 23.502 RT latency of XRM service Xiaomi, Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300821 CR Approval 23.502 CR3793 (Rel-18, 'B'): Enhance the Nnef_AFsessionWithQoS service to support the coordination of multi-modality flows in one XRM service Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300820 CR Approval 23.501 CR3988 (Rel-18, 'B'): Implement the TR conclusion for KI#1, #2 in the specification and describe the required QoS enhancement. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300493 CR Approval 23.501 CR3921 (Rel-18, 'B'): Reusing and extending TSCAI/TSCAC to support power saving optimization OPPO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300460 CR Approval 23.502 CR3729 (Rel-18, 'B'): Procedures update to support QoS monitoring to monitor jitter value requested by AF Samsung, Tencent, Tencent Cloud Rel-18 Confirm CR Revision - CR states 1! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300398 CR Approval 23.503 CR0826 (Rel-18, 'B'): Introduction of Round-Trip delay requirements Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300558 CR Approval 23.502 CR3746 (Rel-18, 'B'): PDU set handling capability of RAN node Lenovo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300578 CR Approval 23.502 CR3753 (Rel-18, 'B'): Congestion information exposure for XRM services Lenovo Rel-18 Confirm Specification Number - CR states 23.503! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300452 CR Approval 23.501 CR3906 (Rel-18, 'B'): Description about the 5GS information exposure for XR/media service China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300234 CR Approval 23.502 CR3687 (Rel-18, 'B'): Enhancements to QoS Monitoring Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300393 CR Approval 23.503 CR0824 (Rel-18, 'B'): Introduction of 5GS information exposure Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300480 CR Approval 23.503 CR0836 (Rel-18, 'B'): Policy update to enable network information exposure for XR and media services China Telecom Rel-18 Confirm CR Number - CR states -! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300236 CR Approval 23.503 CR0807 (Rel-18, 'B'): Policy control enhancements for the delivery of XR and multimodal services Ericsson, Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300396 CR Approval 23.502 CR3713 (Rel-18, 'B'): Introduction of KI#8 concl: Power Saving related Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300237 CR Approval 23.503 CR0808 (Rel-18, 'B'): Policy control enhancements for the support of PDU Set Handling Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.12.2 S2-2300417 CR Approval 23.502 CR3718 (Rel-18, 'B'): Update TS23.502 to reflect conclusion of KI#3 for XRM in TR23.700-60 for the API based congestion exposure option Nokia, Nokia Shanghai Bell Rel-18 Check Affected Clauses! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.13.1 - - - Study on RedCap Phase 2 (FS_RedCAP_Ph2) - - Docs:=0 -
9.13.2 - - - RedCap Phase 2 (NR_RedCAP_Ph2) - - Docs:=14 -
9.13.2 S2-2301180 CR Approval 23.501 CR4081 (Rel-18, 'B'): CN based MT communication capability indication ZTE Rel-18 CC#4: r03 + note agreed. Revised to S2-2301477. Steve (Huawei) comments.
Miguel (Qualcomm) comments
Miguel (Qualcomm) replies to Steve
Jinguo(ZTE) replies
Steve (Huawei) provides r01
Qian (Ericsson) provides comment on r01
Hannu (Nokia) does not see the need for this CR in the context of NR RedCap and objects to all revisions.
Jinguo(ZTE) replies to Hannu (Nokia) and provides r02
Miguel (Qualcomm) replies to Hannu
Qian (Ericsson) propose a way forward and r03
Jingo(ZTE) is fine with r03
==== Revisions Deadline ====
Qian (Ericsson) propose to go with r03
Steve (Huawei) is ok with r03.
Chris (Vodafone) is NOT ok (object) with r03. But can accept r03 provided that it is agreed to correct it in Feb. R03 allows eDRX when the AMF does not support it! Perhaps check in CC#4?
Jinguo(ZTE) propose a revision
Qian (Ericsson) provides comments.
==== Final Comments Deadline ====
Chris (Vodafone) replies. Assuming we are all agreed that eDRX>10.24 is not used in RRC Inactive unless the AMF supports it, then I'm OK with r03 as the basis for further work.
Revised
9.13.2 S2-2301477 CR Approval 23.501 CR4081R1 (Rel-18, 'B'): CN based MT communication capability indication ZTE,Ericsson Rel-18 Revision of S2-2301180r03 + note. Approved Agreed
9.13.2 S2-2301065 CR Approval 23.502 CR3834 (Rel-18, 'F'): Delayed indication of RRC-Inactive with long eDRX Nokia, Nokia Shanghai Bell Rel-18 Noted Qian (Ericsson) provides comments
Hannu (Nokia) shares r01 to avoid collision with another CR. Disagrees with the claimed uselessness of the CR as the delayed eDRX indication from NG-RAN to AMF cannot work without it.
Miguel (Qualcomm) objects to r01.
==== Revisions Deadline ====
Qian (Ericsson) propose to NOTE or Postpone this paper.
Lars (Sony) objects to all version of this paper
Hannu (Nokia) agrees that based on the discussions in the meeting, documents S2-2301064 and S2-2301065 should be NOTED.
==== Final Comments Deadline ====
Noted
9.13.2 S2-2301064 CR Approval 23.501 CR4050 (Rel-18, 'F'): Delayed indication of RRC-Inactive with long eDRX Nokia, Nokia Shanghai Bell Rel-18 Noted Qian (Ericsson) provides comments
Lars (Sony) Agrees with Qian (Ericsson) comments
Miguel (Qualcomm) agrees with Lars (Sony) Agrees with Qian (Ericsson) comments, thinks this CR is not needed.
Hannu (Nokia) cannot agree with the previous comments and explains why the remaining eDRX time is needed
Miguel (Qualcomm) responds to Hannu (Nokia)
Hannu (Nokia) thanks Miguel for explanation but requests to get a confirmation from the RAN2 since we are sending LS S2-2300932 from this meeting
==== Revisions Deadline ====
Qian (Ericsson) propose to NOTE or Postpone this paper
Lars (Sony) objects to this paper
Hannu (Nokia) agrees that based on the discussions in the meeting, documents S2-2301064 and S2-2301065 should be NOTED.
==== Final Comments Deadline ====
Noted
9.13.2 S2-2300965 CR Approval 23.501 CR4026 (Rel-18, 'C'): Overview update for triggers to send RedCap indication for CN buffering Huawei, HiSilicon Rel-18 Merged into S2-2301477 To be merged into S2-2301180 (For CC#4) Qian (Ericsson) provides comments and ask question
Steve (Huawei) comments.
Miguel (Qualcomm) has concerns with changing RAN/CN behaviour for eDRX<=10.24s
Miguel (Qualcomm) has separate question from previous comment on the second proposed change
Steve (Huawei) comments on the second change
Steve (Huawei) comments on different understandings
Hannu (Nokia) proposes not to merge and provides r01.
Miguel (Qualcomm) provides r02
Jinguo(ZTE) suggest merge into 1180
==== Revisions Deadline ====
Qian (Ericsson) propose to mark this paper as merged into 1180
Steve (Huawei) is ok to merge with 1180r03.
==== Final Comments Deadline ====
Merged
9.13.2 S2-2300966 CR Approval 23.502 CR3822 (Rel-18, 'C'): Procedure update for triggers to send RedCap indication for CN buffering Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301448. Lars (Sony) ask if this can be merged into S2-2300220
Steve (Huawei) comments on merge, it's possible, but...
Qian (Ericsson) provides comments and consider only to merge the changes of the first clause to 0221
Steve (Huawei) provides r01
Miguel (Qualcomm) asks follow-up question to Steve (Huawei)
Steve (Huawei) provides r02
Miguel(Qualcomm) provides r03 to align cover sheet with revised text
Steve (Huawei) provides r04
==== Revisions Deadline ====
Qian (Ericsson) proposes to go with r04
Lars (Sony) is ok with r04
Chris (Vodafone) supports the changes in r04 but the WI code needs to be changed from Redcap to e.g. TEI-18, and the category must be cat F
Steve (Huawei) comments.
==== Final Comments Deadline ====
Revised
9.13.2 S2-2301448 CR Approval 23.502 CR3822R1 (Rel-18, 'F'): UE Triggered Connection Resume in RRC Inactive procedure alignment with RAN Huawei, HiSilicon Rel-18 Revision of S2-2300966r04. Approved Agreed
9.13.2 S2-2300055 LS In Action LS from RAN WG3: Reply LS on long eDRX support for RRC_INACTIVE RAN WG3 (R3-226776) Rel-18 Response drafted in S2-2300932. Final response in S2-2301858 Replied to
9.13.2 S2-2300932 LS OUT Approval [DRAFT] Reply LS to provide SA WG2 agreements related eDRX handling for RRC_INACTIVE with attached CRs Ericsson Inc. Rel-18 Response to S2-2300055. Revised to S2-2301858. Steve (Huawei) provides r01
Miguel (Qualcomm) provides r02
Hannu (Nokia) provides r03 to ask for RAN groups to confirm the analysis on the eDRX sync between the NG-RAN and the AMF
Miguel (Qualcomm) still prefers r02, doesn't agree the added text in r03 would be useful.
==== Revisions Deadline ====
Qian (Ericsson) provides comments.
Qian (Ericsson) prefers r02 but can live with r03.
Lars (Sony) supports r02.
Steve (Huawei) prefers r02 but can live with r03
Qian (Ericsson) comments that after we select either r02 or r03, the attached CR number for 23.501 in the LS shall be: 4081
Hannu (Nokia) can follow the majority view and live with r02.
Qian (Ericsson) comments that we agreed to go with R02 + change attached 23.501 CR number to: 4081
==== Final Comments Deadline ====
Revised
9.13.2 S2-2301858 LS OUT Approval Reply LS on long eDRX support for RRC_INACTIVE SA WG2 Rel-18 Revision of S2-2300932. Approved Approved
9.13.2 S2-2300221 CR Approval 23.502 CR3685 (Rel-18, 'C'): Update of CN based MT handling Ericsson, ZTE Rel-18 Revised to S2-2301859, merging S2-2300439 Lars (Sony) ask a question and comments
Steve (Huawei) on RAN triggers
Qian (Ericsson) provides answers and views
Steve (Huawei) comments
Qian (Ericsson) provides comments
Steve (Huawei) provides r01
Qian (Ericsson) provides comments and r02
Hannu (Nokia) comments and intends to provide another revision soon (but it takes a bit of time to edit it)
Hannu (Nokia) provides r03.
Qian (Ericsson) provides comments on r03.
Steve (Huawei) comments - keep it simple.
Qian (Ericsson) provides comments and r04.
Miguel (Qualcomm) supports r04.
Steve (Huawei) comments.
Qian (Ericsson) provides comments and r05.
Qian (Ericsson) provides comments and r06.
Steve (Huawei) provides r07
Miguel (Qualcomm) provides r08
==== Revisions Deadline ====
Jinguo(ZTE) comments on r08 and suggests to approve r07
Qian (Ericsson) provides comments and provides r09 in draft folder
Jinguo(ZTE) is ok with the change in r09
Miguel (Qualcomm) OK with r09 with minor editorial
Qian (Ericsson) thanks all for the constructive discussion and indicates agreement is reached with following change on top of r08:
1) in step 1a, remove 'after connection release towards UE based';
2) in step 2, replace the second paragraph with 'If the NG-RAN receives DL NAS message and the UE is in RRC_INACTIVE with RRC configured eDRX cycle and is considered not reachable, NG-RAN indicates to the AMF a NAS non-delivery and then initiates for the CN to handle mobile terminated (MT) communication.'
Chris (Vodafone) is OK is r8/9/10 as basis for further work.
Qian (Ericsson) comments.
==== Final Comments Deadline ====
Revised
9.13.2 S2-2301859 CR Approval 23.502 CR3685R1 (Rel-18, 'C'): Update of CN based MT handling Ericsson, ZTE, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300221, merging S2-2300439. Approved Agreed
9.13.2 S2-2300439 CR Approval 23.502 CR3724 (Rel-18, 'B'): Clarification on RAN implementation on triggering buffering MT data in TS 23.502 China Mobile Rel-18 Merged into S2-2301859 Qian (Ericsson) proposes to merge this paper into 0221
Aihua(CMCC) agrees to merge this paper into 0221.
Hannu (Nokia) supports the merge proposed by Qian in order to get a single proposal to deal with the same clause
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.13.2 S2-2300220 CR Approval 23.501 CR3849 (Rel-18, 'F'): EDRX synchronization handling Ericsson, ZTE Rel-18 Noted Lars (Sony) ask aquestion
Qian (Ericsson) provides answer
Lars (Sony) responds to Qian.
Miguel (Qualcomm) provides comment regarding reference
Lars (Sony) propose to merge this into S2-2300965
Qian (Ericsson) provides comments
==== Revisions Deadline ====
Qian (Ericsson) proposes to mark this one as merged into 1180 or NOTED
==== Final Comments Deadline ====
Noted
9.14.1 - - - Study on evolution of IMS multimedia telephony service (FS_NG_RTC) - - Docs:=33 -
9.14.1 - - - General issues - - Docs:=4 -
9.14.1 S2-2300766 P-CR Approval 23.700-87: Modification of Terms and Abbreviations in Clause 3. ZTE Rel-18 r01 agreed. Revised to S2-2301817. Rainer (Nokia) provides r01.
==== Revisions Deadline ====
Hao (ZTE) is fine with R01.
George (Ericsson) provides comments OK with r01
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301817 P-CR Approval 23.700-87: Modification of Terms and Abbreviations in Clause 3. ZTE Rel-18 Revision of S2-2300766r01. Approved Approved
9.14.1 S2-2301761 LS OUT Approval [DRAFT] LS on PS Data Off for IMS Data Channel China Mobile - Created at CC#3. r02 agreed. Revised to S2-2301827. ==== Revisions Deadline ====
Yi (China Mobile) 1761 has been uploaded and please check.
Rainer (Nokia) provides r01.
Hao (ZTE) comments.
Leo (Deutsche Telekom) provides r02 in the _Post_revisions_deadline folder.
Rainer (Nokia) replies.
Rainer (Nokia) is ok with r02.
Revised
9.14.1 S2-2301827 LS OUT Approval LS on PS Data Off for IMS Data Channel service SA WG2 Rel-18 Revision of S2-2301761r02. Approved Approved
9.14.1 - - - KI#1: Solution updates - - Docs:=11 -
9.14.1 S2-2300130 P-CR Approval 23.700-87: KI#1, 4: Update to solution 20. Ericsson, CMCC Rel-18 r05 agreed. Revised to S2-2301818, merging S2-2300767 and S2-2300926 Hao (ZTE) provides R01.
Mu (Huawei) comments and provide r02
Rainer (Nokia) comments.
George (Ericsson) provides comments inline.
Mu (Huawei) comments inline
George (Ericsson) provides r03
Chris Joul (T-Mobile USA) Provides comments to answer Nokia Questions.
Yi (China Mobile) support HTTP proxy and ask question about how to capture NF services.
Mu (Huawei) provide r04 with text indicating 6.20.1.2.2-3 is an example.
Rainer (Nokia) replies.
Rainer (Nokia) provides r05.
==== Revisions Deadline ====
George (Ericsson) OK with r05
Chris Joul (T-Mobile USA) OK with r05
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301818 P-CR Approval 23.700-87: KI#1, 4: Update to solution 20. Ericsson, CMCC, ZTE Rel-18 Revision of S2-2300130r05, merging S2-2300767 and S2-2300926. Approved Approved
9.14.1 S2-2301074 P-CR Approval 23.700-87: KI#1, Update of solution #20. China Mobile, Huawei, Hisilicon, ZTE Rel-18 r05 agreed. Revised to S2-2301819. George Foti (Ericsson) provides r01 including several comments. The main thing is that the media resources for Mb and DCMF needs to be separated.
Rainer (Nokia) comments.
Yi (China Mobile) replies to George and Rainer. r02 is provided.
Hao (ZTE) comments.
Yi (China Mobile) provides r04 to align with 927 and accept comments from Hao.
George (Ericsson) provides r05
Yi (China Mobile) ask question.
Yi (China Mobile) provides r06 to support managing multiple media flows in a service operation.
Rainer (Nokia) asks question.
George (Ericsson) provides comments
George (Ericsson) Ericsson would like to postpone this CR and all its revisions to the next meeting. Additional comments below.
==== Revisions Deadline ====
Hao (ZTE) suggests to go with one of the versions; and we can have further discussion and update it.
George (Ericsson) We would like to postpone this as there are too many inconsistencies
Yi (China Mobile) replies to Rainer.
Yi (China Mobile) replies to George.
Rainer (Nokia) prefers to postpone.
Yi (China Mobile) propose to go with r05.
Rainer (Nokia) is ok with r05 for this meeting.
Rainer (Nokia) replies.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301819 P-CR Approval 23.700-87: KI#1, Update of solution #20. China Mobile, Huawei, Hisilicon, ZTE Rel-18 Revision of S2-2301074r05. Approved Approved
9.14.1 S2-2301056 P-CR Approval 23.700-87: KI#1, Sol#20 Update to remove MDC3. Huawei, HiSilicon Rel-18 Noted ==== Revisions Deadline ====
George Foti (Ericsson) proposes to note this one.
Rainer (Nokia) comments.
Mu (Huawei) agrees to note this pCR
==== Final Comments Deadline ====
Noted
9.14.1 S2-2300927 P-CR Approval 23.700-87: KI#1, solution #20 update: associate bootstrap DC with subscriber identity. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2301820. Chris Joul (T-Mobile USA) Agrees with Ericsson and suggests sending a LS to SA3
Yi (China Mobile) provides comments and propose to merge to 0130.
George Foti (Ericsson) provides comments. We prefer one option and that's option 1
Rainer (Nokia) replies.
James Jin (vivo) provides comments.
George (Ericsson) provides response. A redirect will lead to tearing down the session and restating a completely new session. So there are UE impacts. The correlation is required in all cases, so I don't understand the basis of your comment. U have to send s a redirect link to the UE tied to the subscriber, so U have to correlate it to the subscriber, and maintain a state. This state is also temporary and the UE may never comes ack again then U have to remove this state. That's why option 1 is the simples.
Mu (Huawei) comments
George (Ericsson) provides question
George (Ericsson) provides response and a question
Chris Joul (T-Mobile USA) Replies to question on option 1
Yi (China Mobile) comments and think option 2 is more straightforward.
Mu (Huawei) comments that option 2 does not need to have identity information in the URL
Rainer (Nokia) comments and provides r01.
Rainer (Nokia) replies to Yi on SoH.
George (Ericsson) provides comments
George (Ericsson) provides response We will only support option 2 with URL replacement; no redirect as this has issues.
Yi (China Mobile) also agree to only support option 2 with URL replacement by DCMF.
Mu (Huawei) support option 2 with URL replacement, and also support to use a subclause to capture this change.
James (vivo) support option 2 with URL replacement by DCMF.
George (Ericsson) add it to the conclusion; a new revision of 131 to capture that.
Rainer (Nokia) provides r02.
==== Revisions Deadline ====
George (Ericsson) OK with r02
Chris Joul (T-Mobile USA) OK with r02
Yi (China Mobile) is fine with r02.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301820 P-CR Approval 23.700-87: KI#1, solution #20 update: associate bootstrap DC with subscriber identity. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300927r02. Approved Approved
9.14.1 S2-2300767 P-CR Approval 23.700-87: KI #1, Sol #20, Update Procedures for P2A/A2P Scenario. ZTE Rel-18 Merged into S2-2301818 Yi (China Mobile) provides comments and propose to merge to 0130.
Hao (ZTE) is OK to merge this paper in 0130; and 0130r01 is provided to reflect the change.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.14.1 S2-2300928 P-CR Approval 23.700-87: KI#1, Sol#20 update: Providing subscriber related information from IMS AS to DCSF. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2301821. Yi (China Mobile) provides comments and propose to merge to 0130.
George Foti (Ericsson) provides comments
Mu (Huawei) comments
Yi (China Mobile) provides comments and suggest to further discuss it in thread of 0130.
Rainer (Nokia) provides r01.
George (Ericsson) ask question.
Rainer (Nokia) replies.
==== Revisions Deadline ====
George (Ericsson) Accepts r01
Yi (China Mobile) can accpet r01. Please note that step 17 has been removed in 130.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301821 P-CR Approval 23.700-87: KI#1, Sol#20 update: Providing subscriber related information from IMS AS to DCSF. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300928r01. Approved Approved
9.14.1 S2-2300926 P-CR Approval 23.700-87: KI#1, solution #20 update: services description. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301818 Chris Joul (T-Mobile USA) Provides comments and agrees this should merge with 0130 and 1074
Yi (China Mobile) provides comments and propose to merge into 0130 and 1074.
George Foti (Ericsson) provides comments .
Rainer (Nokia) is ok to mark 0926 as merged into 0130.
==== Revisions Deadline ====
George (Ericsson) proposes to note the CR as this is merged in 130.
==== Final Comments Deadline ====
Merged
9.14.1 - - - KI#2: Solution updates - - Docs:=2 -
9.14.1 S2-2300929 P-CR Approval 23.700-87: KI#2, conclusions update: remove references to sol#8 and sol#9 and add reference to sol#20. Nokia, Nokia Shanghai Bell Rel-18 Noted Yi (China Mobile) comments.
George Foti (Ericsson) provides comments
Mu (Huawei) comments and provide r01
Mu (Huawei) provide r02
Hao (ZTE) provides R03.
Rainer (Nokia) does not accept r03.
Hao (ZTE) comments.
==== Revisions Deadline ====
Hao (ZTE) can only accept R03.
George (Ericsson) Objects to all revisions including the original. We see nothing needing over what is in the TR already
Yi (China Mobile) can live with r02 and r03, or note the pCR.
Rainer (Nokia) ok to note the document.
==== Final Comments Deadline ====
Noted
9.14.1 S2-2300768 P-CR Approval 23.700-87: Resolve EN Regarding AR Media Network Rendering Process. ZTE Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.14.1 - - - KI#4: Solution updates - - Docs:=2 -
9.14.1 S2-2301073 P-CR Approval 23.700-87: KI#4: Update to solution 17. China Mobile Rel-18 r03 agreed. Revised to S2-2301822. George Foti (Ericsson) provides comments
Hao (ZTE) comments.
Yi (China Mobile) provides r02.
Yi (China Mobile) provides r03.
==== Revisions Deadline ====
George (Ericsson) Ok with r03
Rainer (Nokia) also ok with r03.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301822 P-CR Approval 23.700-87: KI#4: Update to solution 17. China Mobile Rel-18 Revision of S2-2301073r03. Approved Approved
9.14.1 - - - Evaluations and conclusions - - Docs:=14 -
9.14.1 S2-2300520 P-CR Approval 23.700-87: KI #1, Evaluation Update . Vivo, Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2301823. James Jin (vivo) replies to questions from George Foti (Ericsson).
George (Ericsson) provides additional questions
Hao (ZTE) comments.
James Jin (vivo) replies to questions from George Foti (Ericsson) and explains the evaluation is to complete the TR.
George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
James Jin (vivo) confirm r01 is OK.
==== Revisions Deadline ====
George (Ericsson) Accepts r01
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301823 P-CR Approval 23.700-87: KI #1, Evaluation Update . Vivo, Qualcomm Incorporated Rel-18 Revision of S2-2300520r01. Approved Approved
9.14.1 S2-2300464 P-CR Approval 23.700-87: KI #1, update of conclusions on DC application ID . Qualcomm Incorporated, vivo Rel-18 Revised to S2-2301860. George Foti (Ericsson) provides comments
Kefeng Zhang (Qualcomm replies George Foti (Ericsson) comments.
==== Revisions Deadline ====
George (Ericsson) proposes to postpone the pCR. It is unclear what this additional information is. SA4 is only discussing application binding. The text is not relevant for SA2.
Kefeng (Qualcomm) replies George (Ericsson) comments and ask for approval of the pCR.
Kefeng (Qualcomm) proposes to approve the pCR with following changes:
Removing the second bullet ' - When multiple Data Channels with different endpoints ...' and NOTE 4.
Rainer (Nokia) is ok with 464.
Rainer (Nokia) is ok to remove the second bullet.
George (Ericsson) provides response. If U remove this bullet I would be OK than
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301860 P-CR Approval 23.700-87: KI #1, update of conclusions on DC application ID . Qualcomm Incorporated, vivo Rel-18 Revision of S2-2300464. Approved Approved
9.14.1 S2-2300131 P-CR Approval 23.700-87: KI#1: Update to Conclusion 1. Ericsson Rel-18 r03 agreed. Revised to S2-2301824. Mu (Huawei) provide r01 to reflect the changes in 0130
Rainer (Nokia) provides r02.
James Jin (vivo) provides comments.
Mu (Huawei) replies
George (Ericsson) provides r03
Rainer (Nokia) comments.
Mu (Huawei) further replies
==== Revisions Deadline ====
George (Ericsson) Ericsson accepts only r03.
Rainer (Nokia) is ok with r03.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301824 P-CR Approval 23.700-87: KI#1: Update to Conclusion 1. Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300131r03. Approved Approved
9.14.1 S2-2300521 P-CR Approval 23.700-87: Update to resolve ENs in conclusion of KI#1. Vivo Rel-18 r02 agreed. Revised to S2-2301825. James Jin (vivo) replies to questions from George Foti (Ericsson).
George Foti (Ericsson) provides comments
James Jin (vivo) replies to questions from George Foti (Ericsson) and provide r01.
Rainer (Nokia) provides r02.
James Jin (vivo) confirm r02 is OK.
==== Revisions Deadline ====
George (Ericsson Accepts r02
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301825 P-CR Approval 23.700-87: Update to resolve ENs in conclusion of KI#1. Vivo Rel-18 Revision of S2-2300521r02. Approved Approved
9.14.1 S2-2300280 P-CR Approval 23.700-87: Update on conclusion of KI#1. Deutsche Telekom, KPN, Orange, Vodafone, KDDI Rel-18 r05 agreed. Revised to S2-2301826. Yi (China Mobile) provides r01.
Leo (Deutsche Telekom) provides r02.
Rainer (Nokia) provides r03.
Yi (China Mobile) ask question about sending LS to SA1.
Leo (Deutsche Telekom) is fine with r03 and comments.
Mu (Huawei) support sending LS to SA1
Rainer (Nokia) agrees to send an LS to SA1.
Kefeng (Qualcomm) provides comments.
Yi (China Mobile) is willing to draft a LS for review.
Leo (Deutsche Telekom) comments on drafting a LS for review.
Yi (China Mobile) replies to Leo and provides a draft LS.
Rainer (Nokia) provides r01.
Kefeng (Qualcomm) and provides r04 and comments to the daft LS.
Leo (Deutsche Telekom) comments on proposed LS and S2-2300280.
Mu (Huawei) replies.
George (Ericsson) provides comments
Rainer (Nokia) asks for clarification.
Rainer (Nokia) replies.
Hao (ZTE) comments.
Rainer (Nokia) cannot accept r04, prefers r03. Postponing would be also ok.
Leo (Deutsche Telekom) objects r04 and provides r05, can live with r03.
==== Revisions Deadline ====
Rainer (Nokia) is ok with r05.
George (Ericsson) Accepts r05
Kefeng (Qualcomm) object r05 and provides comments.
Yi (China Mobile) is fine with the proposed change on the LS from Rainer. we also agree R18 will not work on DC data off.
Yi (China Mobile) is fine with r05.
Kefeng (Qualcomm) I agree that R18 will not work on DC data off and exemption is not supported.
Ashok (Samsung) comments
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301826 P-CR Approval 23.700-87: Update on conclusion of KI#1. Deutsche Telekom, Orange, Vodafone, KDDI Rel-18 Revision of S2-2300280r05. Approved Approved
9.14.1 S2-2300465 P-CR Approval 23.700-87: KI #3, update of conclusions on Third Party ID. Qualcomm Incorporated, Samsung Rel-18 Noted George Foti (Ericsson) not ok with this revision. Additional comments below
Kefeng Zhang (Qualcomm) replies George Foti (Ericsson) comments and provides r01.
Yi (China Mobile) comments.
Ashok (Samsung) provides update on group management
George (Ericsson) provides responses. Still NOT OK with any revision
Ashok (Samsung) seeks clarification from George (Ericsson)
George (Ericsson) reply
Rainer (Nokia) comments.
Kefeng Zhang (Qualcomm) replies George (Ericsson) comments.
George (Ericsson) provides comments
Kefengf (Qualcomm) replies George (Ericsson) comments
Kefeng (Qualcomm) replies George (Ericsson) comments and provided r02
Kefeng (Qualcomm) replies Rainer (Nokia) comments.
Ashok (Samsung) responds to George (Ericsson) and Rainer (Nokia)
Rainer (Nokia) asks for clarification.
George (Ericsson) provides comments in line
Kefeng (Qualcomm) replies George (Ericsson) comments, and provides r03.
Ashok (Samsung) replies to George (Ericsson)
==== Revisions Deadline ====
George (Ericsson) We are Not OK with any revision including the original.
Kefeng (Qualcomm) asks George (Ericsson) for clarification.
Ashok (Samsung) agrees with Kefeng (Qualcomm) and don't see any technical reason to not approve it
Yi (China Mobile) ask question.
Rainer (Nokia) objects to 465.
Ashok (Samsung) responds to Rainer (Nokia)
Rainer (Nokia) replies.
Ashok (Samsung) comments
Mu (Huawei) comments and propose to approve r03
George (Ericsson) provides reasons for objecting to the CR
Ashok (Samsung) clarifies and propose to approve r03
Kefeng (Qualcomm) replies George (Ericsson).
George (Ericsson) provides comments inline
Kefeng (Qualcomm) replies Rainer (Nokia).
Kefeng (Qualcomm) replies George (Ericsson) comments.
==== Final Comments Deadline ====
Noted
9.14.1 S2-2300930 P-CR Approval 23.700-87: KI#3, conclusion update: resolving remaining editor notes. Nokia, Nokia Shanghai Bell Rel-18 Noted. CC#4: Add that KI#5 will not be progressed. Revised to S2-2301486. George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
Kefeng Zhang (Qualcomm) provides comments and suggests to merge 0930 with 0465.
George (Ericsson) proposes to keep the discussion in 465. Please note 930.
There is now a clear misalignment anyway
Rainer (Nokia) does not agree to note 0930.
George (Ericsson) I thinks that reasonable. These open issues are just now surfacing
==== Revisions Deadline ====
George (Ericsson) Ericsson OK with r01
Kefeng (Qualcomm) objects r01 and the original version.
==== Final Comments Deadline ====
Revised
9.14.1 S2-2301486 P-CR Approval 23.700-87: KI#3, conclusion update: resolving remaining editor notes. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300930. Approved Approved
9.14.1 S2-2300931 P-CR Approval 23.700-87: KI#4, conclusions update: move reference to sol#17 on DCMF services from clause 9.4 to clause 9.1. Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Approved
9.14.2 - - - Evolution of IMS multimedia telephony service (NG_RTC) - - Docs:=6 -
9.14.2 - - - CRs for 23.228 - - Docs:=5 -
9.14.2 S2-2301075 CR Approval 23.228 CR1263 (Rel-18, 'B'): Architecture of IMS supporting data channel China Mobile Rel-18 r07 agreed. Revised to S2-2301449, merging S2-2301055 Chris Joul (T-Mobile USA) Prefers to use this CR as basis for discussion, and provides comments
George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
Yi (China Mobile) provides r02.
Rainer (Nokia) provides r03.
George (Ericsson) provides r04
Rainer (Nokia) replies.
George (Ericsson) provides comments
Chris Joul (T-Mobile USA) Provides comments
Yi (China Mobile) is fine to have a sentence saying IMS AS supporting DC is collocated with TAS in this release.
Yi (China Mobile) provides r05 for further review and revision.
Rainer (Nokia) provides r06.
George (Ericsson) provides r07. Removed one occurrence of TAS
George (Ericsson) provides r08
==== Revisions Deadline ====
Yi (China Mobile) is fine with r08.
Hao (ZTE) supports r08.
Rainer (Nokia) prefers r07 and doing this correction at next meeting.
Mu (Huawei) only accept r07. Agree to merge 1055 into 1075 and please add Huawei as source company.
George (Ericsson) What inconsistency. There is already a example showing how it is used in update to solution 20. There is nothing inconsistent. U can clarify as well as the next meeting using R08. U provide no details.
Mu (Huawei) ask a question. Could you clarify where in sol#20 shows a example that DCSF using MDC2 to interact with DC AS. I don't believe such example exist.
Yi (China Mobile) propose to go with r07 including the contents we all agree and make progress.
Rainer (Nokia) agrees on the way forward as proposed by Yi.
George (Ericsson) provides response
George (Ericsson) Ericsson ONLY ENDORSES R07. Does not accept it.
George (Ericsson) look at the architecture. MDC2 terminates on DCMF. We are reflecting that.
Yi (China Mobile) ask question.
Mu (Huawei) need further clarification. Please provide complete logic, MDC2 terminate on DCMF but not DCSF so DCSF cannot interact with DC AS via MDC2. If you want to do so you are changing the architecture.
==== Final Comments Deadline ====
Revised
9.14.2 S2-2301449 CR Approval 23.228 CR1263R1 (Rel-18, 'B'): Architecture of IMS supporting data channel China Mobile, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301075r07, merging S2-2301055. Technically Endorsed Endorsed
9.14.2 S2-2301054 CR Approval 23.228 CR1259 (Rel-18, 'B'): Supporting AR Telephony Communication Huawei, HiSilicon Rel-18 Confirm CR Number - CR states ! r04 agreed. Revised to S2-2301450. Chris Joul (T-Mobile USA) Prefers to use TDOC S2-2301075 as baseline.
George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
Rainer (Nokia) comments.
Mu (Huawei) comment regarding DC4 interface
Rainer (Nokia) replies.
George (Ericsson) provides comments
Mu (Huawei) comments and provide r02.
George (Ericsson) responds. I was asking a question on MDC3, and MDC4. DC3, and DC4 are not in Release 18 scope anyway. But they belong to 3GPP otherwise how can the NEF be used.
We corrected DC4 by the way.
Yi (China Mobile) comments.
George (Ericsson) provides response. IF MDCX carry no signalling relevant for anything than I understand. Can we be clear on the description the nature of these interface so we avoid the discussion. Also that implies that the AS itself has media in it. I don't understand how this can work with the AR sending media to ARMF, and DCMF separately. This does not make sense. Please provide an update.
Mu (Huawei) replies to George
George (Ericsson) asks question.
Mu (Huawei) replies and provide r03.
Rainer (Nokia) provides r04.
George (Ericsson) asks questions. We are not OK with any revision yet.
Mu (Huawei) further replies to George
==== Revisions Deadline ====
George (Ericsson) proposes to ONY ENDORSE R04 for future work, but not to approve it at this meeting.
Rainer (Nokia) agrees to endorse r04 and come back at the next meeting.
==== Final Comments Deadline ====
Revised
9.14.2 S2-2301450 CR Approval 23.228 CR1259R1 (Rel-18, 'B'): Supporting AR Telephony Communication Huawei, HiSilicon Rel-18 Revision of S2-2301054r04. Technically Endorsed Endorsed
9.14.2 S2-2301055 CR Approval 23.228 CR1260 (Rel-18, 'B'): Support of IMS Data Channel Huawei, HiSilicon Rel-18 Confirm CR Number - CR states ! Merged into S2-2301449 Chris Joul (T-Mobile USA) Provides comments and agrees with Ericsson proposal to use S2-2301075 as baseline text
George Foti (Ericsson) provides comments
Rainer (Nokia) also prefers to use 1075 as baseline.
Mu (Huawei) agrees to use 1075 as baseline. Comment for MDC3.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.14.2 - - - CRs for 23.502 - - Docs:=1 -
9.14.2 S2-2301076 CR Approval 23.502 CR3837 (Rel-18, 'B'): Enhancements to NRF servives to support DCSF discovery and selection China Mobile Rel-18 Approved George Foti (Ericsson) provides comments
Yi (China Mobile) replies to George.
George (Ericsson) provides comments
George (Ericsson) but in this release it cant be used, or are U saying that it can be used.
==== Revisions Deadline ====
George (Ericsson) Ericsson accepts R01
Mu (Huawei) asks is there r01?
Rainer (Nokia) prefers to postpone this to next meeting.
George (Ericsson) Accepts original
Rainer (Nokia) prefers to postpone but can accept 1076 as is.
==== Final Comments Deadline ====
Agreed
9.15.1 - - - Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) - - Docs:=0 -
9.15.2 - - - Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) - - Docs:=28 -
9.15.2 S2-2301107 CR Approval 23.501 CR4064 (Rel-18, 'B'): Support of redundant traffic steering Xiaomi Rel-18 Merged into S2-2301608 Rainer (Nokia) proposes to merge into 0923.
Yuxin (Xiaomi) supports to merge this CR into 0923.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.15.2 S2-2301008 CR Approval 23.502 CR3826 (Rel-18, 'B'): Support of non-3GPP access path switching for MA PDU Session Samsung Rel-18 Merged into S2-2301615 Rainer (Nokia) proposes to merge into 0347.
Paul (Charter) agree with Nokia that 1008 can be merge into 0347.
DongYeon (Samsung) agree to merge 1008 into 0347.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300745 CR Approval 23.502 CR3784 (Rel-18, 'B'): Introduction of the MPQUIC Steering Functionality Lenovo, Broadcom Rel-18 r02 agreed. Revised to S2-2301607. Rainer (Nokia) comments.
Apostolis (Lenovo) provides r01. Only change is the addition of co-sourcing companies.
Apostolis (Lenovo) provides r02. Only change is more of co-sourcing companies.
==== Revisions Deadline ====
Krisztian (Apple) requests to add Apple as co-signing company.
Rainer (Nokia) is ok with r02.
Paul (Charter) is also ok with r02.
Omkar (CableLabs) is ok with r02.
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301607 CR Approval 23.502 CR3784R1 (Rel-18, 'B'): Introduction of the MPQUIC Steering Functionality Lenovo, Broadcom, Nokia, Nokia Shanghai Bell, Charter, Deutsche Telekom, Ericsson, Apple Rel-18 Revision of S2-2300745r02. Approved Agreed
9.15.2 S2-2300645 CR Approval 23.501 CR3955 (Rel-18, 'B'): Introduction of N3GPP access path switching on MA PDU session Huawei, HiSilicon Rel-18 Merged into S2-2301613 Paul (Charter) proposes to merge into 0346.
Rainer (Nokia) agrees to merge into 346.
==== Revisions Deadline ====
Yishan (Huawei) agrees to merge into 346 and answers to Rainer.
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300646 CR Approval 23.502 CR3763 (Rel-18, 'B'): Introduction of N3GPP access path switching on MA PDU session Huawei, HiSilicon Rel-18 Merged into S2-2301615 Yishan (Huawei) provides r01 to update the call flow which is aligned with the wording from 0347.
Myungjune (LGE) prefers to use S2-2300347 as basis.
Apostolis (Lenovo) also prefers to merge this CR into S2-2300347.
==== Revisions Deadline ====
Yishan (Huawei) is ok to merge this CR into S2-2300347.
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300643 CR Approval 23.501 CR3954 (Rel-18, 'B'): Introduction of redundant steering mode Huawei, HiSilicon Rel-18 Merged into S2-2301608 Rainer (Nokia) proposes to merge into 0923.
Yishan (Huawei) is ok to merge 0643 into 0923.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300923 CR Approval 23.501 CR4019 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics Rel-18 r08 agreed. Revised to S2-2301608, merging S2-2301107 and S2-2300643 Rainer (Nokia) provides r01.
Stefan (Ericsson) commentd and provides r02
Rainer (Nokia) is ok with r02.
Yuxin (Xiaomi) comments and provides r03
Myungjune (LGE) provides r04.
Rainer (Nokia) cannot accept r03, does not think changes are inline with the study conclusions.
Yishan (Huawei) provides r05.
Rainer (Nokia) provides r06.
Yuxin(Xiaomi) replies to Rainer (Nokia)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301608 CR Approval 23.501 CR4019R1 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics, Xiaomi, Lenovo Rel-18 Revision of S2-2300923r08, merging S2-2301107 and S2-2300643. Approved Agreed
9.15.2 S2-2300924 CR Approval 23.502 CR3816 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics Rel-18 r03 agreed. Revised to S2-2301609. Stefan (Ericsson) provides r01
Rainer (Nokia) provides r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301609 CR Approval 23.502 CR3816R1 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics, Lenovo Rel-18 Revision of S2-2300924r03. Approved Agreed
9.15.2 S2-2300725 CR Approval 23.503 CR0848 (Rel-18, 'B'): MA PDU Session between 5GC and EPC Huawei, HiSilicon Rel-18 Revised to S2-2301561. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301561 CR Approval 23.503 CR0848R1 (Rel-18, 'B'): MA PDU Session between 5GC and EPC Huawei, HiSilicon, Deutsche Telekom Rel-18 Revision of S2-2300725. Approved Agreed
9.15.2 S2-2300742 CR Approval 23.501 CR3973 (Rel-18, 'B'): Introduction of the MPQUIC Steering Functionality Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Charter, Broadcom Rel-18 r09 agreed. Revised to S2-2301610. Susan (Huawei) provides r01.
Stefan (Ericsson) comments and provides r02
Rainer (Nokia) comments.
Dieter (Deutsche Telekom) comments/asks a question.
Myungjune (LGE) comments
Apostolis (Lenovo) provides r03.
Susan (Huawei) provides r04.
Dieter (Deutsche Telekom) comments.
Apostolis (Lenovo) responds to Dieter (Deutsche Telekom).
Dario (Qualcomm) provides r05.
Apostolis (Lenovo) provides r08.
Susan (Huawei) replies to Apostolis (Lenovo).
Apostolis (Lenovo) provides r09 to include Huawei and HiSilicon in the list of sources.
==== Revisions Deadline ====
Rainer (Nokia) is ok with r09.
Paul (Charter) is also ok with r09.
Omkar (CableLabs) is ok with r09.
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301610 CR Approval 23.501 CR3973R1 (Rel-18, 'B'): Introduction of the MPQUIC Steering Functionality Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Charter, Broadcom, Apple, CableLabs, HPE, US Cellular, NICT, KPN, F5, LG Electronics, Deutsche Telekom, Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2300742r09. Approved Agreed
9.15.2 S2-2300925 CR Approval 23.503 CR0870 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics Rel-18 r09 agreed. Revised to S2-2301611, merging S2-2300644 Yishan (Huawei) asks for clarifications
Rainer (Nokia) replies.
Yishan (Huawei) replies to Rainer (Nokia)
Rainer (Nokia) provides r01.
Stefan (Ericsson) provides comments
Rainer (Nokia) provides r02.
Yishan (Huawei) provides r03.
Myungjune (LGE) comments r03.
Yishan (Huawei) provides r04 to capture comments from Myungjune (LGE).
Rainer (Nokia) comments.
Myungjune (LGE) replies to Yishan (Huawei)
Rainer (Nokia) provides r05.
Yishan (Huawei) provides r06 based on r05 to capture comments from Rainer (Nokia).
Myungjune (LGE) comments on r06.
Dario (Qualcomm) provides r07.
Yishan (Huawei) provides r08.
Rainer (Nokia) provides r09.
Myungjune (LGE) is ok with r09.
Apostolis (Lenovo) asks question.
==== Revisions Deadline ====
Yishan (Huawei) is ok with r09
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301611 CR Approval 23.503 CR0870R1 (Rel-18, 'B'): Introducing Redundant Steering Mode Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics Rel-18 Revision of S2-2300925r09, merging S2-2300644. Approved Agreed
9.15.2 S2-2300724 CR Approval 23.502 CR3778 (Rel-18, 'B'): MA PDU Session between 5GC and EPC Huawei, HiSilicon Rel-18 Merged into S2-2301614 Rainer (Nokia) asks for clarification.
Stefan (Ericsson) provides comments
Myungjune (LGE) suggests to merge this CR into S2-2300569.
Susan (Huawei) replies.
==== Revisions Deadline ====
Apostolis (Lenovo) indicates that this CR should be marked as 'Merged into 0569'.
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300723 CR Approval 23.501 CR3967 (Rel-18, 'B'): MA PDU Session between 5GC and EPC Huawei, HiSilicon Rel-18 LATE DOC: Rx 16/01, 01:20. Merged into S2-2301612 Myungjune (LGE) suggests to merge this CR into S2-2300568.
Susan (Huawei) replies to Myungjune (LGE).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300644 CR Approval 23.503 CR0844 (Rel-18, 'B'): Introduction of redundant steering mode Huawei, HiSilicon Rel-18 Merged into S2-2301611 Rainer (Nokia) proposes to merge into 0925.
Yishan (Huawei) is ok to merge 0644 with 0925.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.15.2 S2-2300568 CR Approval 23.501 CR3937 (Rel-18, 'B'): Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC LG Electronics Rel-18 r01 agreed. Revised to S2-2301612, merging S2-2300723 Myungjune (LGE) provides r01 to add supporting company.
==== Revisions Deadline ====
Rainer (Nokia) is ok with r01.
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301612 CR Approval 23.501 CR3937R1 (Rel-18, 'B'): Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC LG Electronics, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-18 Revision of S2-2300568r01, merging S2-2300723. Approved Agreed
9.15.2 S2-2300346 CR Approval 23.501 CR3878 (Rel-18, 'B'): Support for non-3GPP access path switching Ericsson, Nokia, Nokia Shanghai Bell, Charter Communications Rel-18 r04 agreed. Revised to S2-2301613, merging S2-2300645 Yishan (Huawei) asks for clarifications
Stefan (Ericsson) replies and provides r01 and r02
Rainer (Nokia) provides r03.
Stefan (Ericsson) is ok with r03
==== Revisions Deadline ====
Myungjune (LGE) is ok with r03 and wants to cosign
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301613 CR Approval 23.501 CR3878R1 (Rel-18, 'B'): Support for non-3GPP access path switching Ericsson, Nokia, Nokia Shanghai Bell, Charter Communications, Lenovo, LG Electronics Rel-18 Revision of S2-2300346r04, merging S2-2300645. Approved Agreed
9.15.2 S2-2300569 CR Approval 23.502 CR3748 (Rel-18, 'B'): Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC LG Electronics Rel-18 r02 agreed. Revised to S2-2301614, merging S2-2300724 Rainer (Nokia) comments.
Stefan (Ericsson) provides r01
Myungjune (LGE) replies to Rainer (Nokia)
Rainer (Nokia) replies.
Apostolis (Lenovo) asks question.
Myungjune (LGE) replies to Apostolis.
==== Revisions Deadline ====
Rainer (Nokia) is ok with r02.
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301614 CR Approval 23.502 CR3748R1 (Rel-18, 'B'): Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC LG Electronics, Lenovo, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-18 Revision of S2-2300569r02, merging S2-2300724. Approved Agreed
9.15.2 S2-2300347 CR Approval 23.502 CR3707 (Rel-18, 'B'): Non-3GPP access path switching Ericsson, Nokia, Nokia Shanghai Bell, Charter Communications Rel-18 r04 agreed. Revised to S2-2301615, merging S2-2301008 and S2-2300646 Myungjune (LGE) comments.
Yishan (Huawei) asks for clarifications and provides suggestions for the merging.
Stefan (Ericsson) provides replies to Myungjune and Yishan
Myungjune (LGE) responds to Stefan (Ericsson)
Rainer (Nokia) replies.
Yishan (Huawei) replies.
Stefan (Ericsson) provides r01
Paul (Charter) prefers to use S2-2300347 as basis and agree to r01.
Myungjune (LGE) provides r02 to update cover sheet and cosigned.
Yishan (Huawei) replies to Stefan (Ericsson).
DongYeon (Samsung) provides r03.
Rainer (Nokia) is ok with r01.
Apostolis (Lenovo) provides r04.
==== Revisions Deadline ====
Myungjune (LGE) replies to Apostolis (Lenovo).
Yishan (Huawei) provides comments
Paul (Charter) is ok with r04.
Yishan (Huawei) is ok with r04 and ok with the suggestions from Apostolis (Lenovo)
Stefan (Ericsson) OK with r04
Omkar (CableLabs) OK with r04
==== Final Comments Deadline ====
Revised
9.15.2 S2-2301615 CR Approval 23.502 CR3707R1 (Rel-18, 'B'): Non-3GPP access path switching Ericsson, Nokia, Nokia Shanghai Bell, Charter Communications, LG Electronics, Samsung, Lenovo Rel-18 Revision of S2-2300347r04, merging S2-2301008 and S2-2300646. Approved Agreed
9.16.1 - - - Study on UPF enhancement for Exposure And SBA (FS_UPEAS) - - Docs:=3 -
9.16.1 S2-2300577 P-CR Approval 23.700-62: Update to conclusions on KI#2. China Mobile Rel-18 Merged into S2-2301386 Yan (China Mobile) proposes to use 0612 as the baseline paper to discuss conclusion update on KI#2 and merge this 0577 into it.
==== Revisions Deadline ====
Magnus H (Ericsson) objects to this CR
Yan (China Mobile) has merged this 0577 into 0612.
==== Final Comments Deadline ====
Merged
9.16.1 S2-2300612 P-CR Approval 23.700-62: Update to Conclusion (solving an EN) . Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2301386, merging S2-2300577 Yan (China Mobile) suggests to use this 0612 as the baseline paper to discuss conclusion update on KI#2 and merge 0577.
Fenqin (Huawei) provides comments
Laurent (Nokia): answers
Fenqin (Huawei) provides further comments
Huazhang (vivo) reply to Fenqin (Huawei) and provide r01, ask Fenqin and Laurent whether it is ok to compromise that remove the DNAI based SMF discovery for single UE
Huazhang (vivo) provides r02
Fenqin (Huawei) provides r03
Huazhang (vivo) is ok for the wording in r03, thanks Fenqin
Yan (China Mobile) is ok with r03.
Laurent (Nokia): provides r04
==== Revisions Deadline ====
Fenqin (Huawei): accept r04
Huazhang (vivo) is ok with r04, thanks Fenqin, Laurent and Yan
Yan (China Mobile) suggests to go with r04.
Laurent (Nokia): objects to R03
==== Final Comments Deadline ====
Revised
9.16.1 S2-2301386 P-CR Approval 23.700-62: Update to Conclusion (solving an EN) . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300612r04, merging S2-2300577. Approved Approved
9.16.2 - - - UPF enhancement for Exposure And SBA (UPEAS) - - Docs:=33 -
9.16.2 - - - CR for 23.501 - - Docs:=14 -
9.16.2 S2-2300663 CR Approval 23.501 CR3962 (Rel-18, 'F'): Direct Exposure from UPF and UPF selection Huawei, HiSilicon, Rel-18 r05 agreed. Revised to S2-2301387. Fenqin (Huawei) proposes r01.
Laurent (Nokia): provides r02
Magnus H (Ericsson) provides r03
Fenqin (Huawei) provides r04
Kefeng (Qualcomm) provides comments.
Fenqin (Huawei) provides r05.
==== Revisions Deadline ====
Magnus H (Ericsson) objects to r00-r02 and suggests to go with r05
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301387 CR Approval 23.501 CR3962R1 (Rel-18, 'F'): Direct Exposure from UPF and UPF selection Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, Deutsche Telekom Rel-18 Revision of S2-2300663r05. Approved Agreed
9.16.2 S2-2300933 CR Approval 23.501 CR3720R1 (Rel-18, 'B'): UPF event exposure service for TSC management ETRI Rel-18 Revision of S2-2208527. r04 agreed. Revised to S2-2301388. Laurent (Nokia): provides r01
Yan (China Mobile) provides r02.
Fenqin (Huawei) provides comment
Laurent (Nokia): answers
Fenqin (Huawei) provides feedback.
Magnus H (Ericsson) provides comments
Yoohwa (ETRI) comments.
Yoohwa (ETRI) provides r03.
Kefeng Zhang (Qualcomm) provides questions and comments.
Yoohwa (ETRI) responds to Kefeng Zhang.
Fenqin (Huawei) provides comments.
Kefeng (Qualcomm) provides comments.
Yoohwa (ETRI) asks Kenny and Fenqin.
Fenqin (Huawei)give a feedback.
Yoohwa (ETRI) provides r04.
Laurent (Nokia): provides r05
==== Revisions Deadline ====
Fenqin (Huawei): suggest r05+ removing 'and indication of support of direct PMIC/UMIC notifications from UPF' in clause 5.28.3.2
Yoohwa (ETRI) responds to Fenqin.
Yoohwa (ETRI) proposes to go with r04 in this meeting.
Fenqin (Huawei): suggest to go with r04 and object other version.
Laurent (Nokia): objects to R00, I ask to add the following 'both TSCTSF AND/TSN AF and' in the last sentence of 5.8.2.11.14
Fenqin(Huawei) ask a question and insist on r04.
Magnus H (Ericsson) suggests to go with r04
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301388 CR Approval 23.501 CR3720R2 (Rel-18, 'B'): UPF event exposure service for TSC management ETRI, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300933r04. Approved Agreed
9.16.2 S2-2300621 CR Approval 23.501 CR3949 (Rel-18, 'C'): User Plane Function Selection for UPEAS Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2301389, merging S2-2300132 Yan (China Mobile) suggests to use this 0621 as the baseline paper to discuss update of clause 5.8.2.17 in clause TS 23.501 and merge 0132.
Fenqin (Huawei) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301389 CR Approval 23.501 CR3949R1 (Rel-18, 'C'): User Plane Function Selection for UPEAS Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300621r01, merging S2-2300132. Approved Agreed
9.16.2 S2-2300132 CR Approval 23.501 CR3824 (Rel-18, 'B'): Data Exposure by UPF via SBI aligned with TS 23.502 Ericsson Rel-18 Merged into S2-2301389 Yan (China Mobile) proposes to use 0621 as the baseline paper to discuss update of clause 5.8.2.17 in clause TS 23.501 and merge this 0132 into it.
==== Revisions Deadline ====
Magnus H (Ericsson) consider this CR as merged into 0621
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300485 CR Approval 23.501 CR3917 (Rel-18, 'F'): Update on the reference architecture and UPF service for network exposure LG Electronics Rel-18 Postponed Hyunsook (LGE) provides r01.
Yan (China Mobile) suggests to use this 0485 as the baseline paper to discuss update on reference architecture for UPEAS and merge 0967 and 0498.
Fenqin (Huawei) provides comment.
Laurent (Nokia): provides r02
Magnus H (Ericsson) provides comments
Mirko (Huawei) comments.
Hyunsook (LGE) comments.
Hyunsook (LGE) wants to check the group's opinion.
Hyunsook (LGE) provides r03.
Laurent (Nokia): provides r04
==== Revisions Deadline ====
Hyunsook (LGE) suggests to go with r04 in this meeting.
Mirko (Huawei) objects to all versions of this CR as the specific nature of the Nupf interface would get lost.
Laurent (Nokia): objects to R00, R01 and R03; Happy with R04 (Nupf is now more generic than Edge aspects from R17)
==== Final Comments Deadline ====
Postponed
9.16.2 S2-2300967 CR Approval 23.501 CR4027 (Rel-18, 'F'): Update the reference architecutre for UPEAS Samsung Rel-18 Postponed To be merged into S2-2300485 (Postponed) Yan (China Mobile) proposes to use 0485 as the baseline paper to discuss update on reference architecture for UPEAS and merge this 0967 into it.
Kisuk (Samsung) merges this paper into 0485.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== Final Comments Deadline ====
Postponed
9.16.2 S2-2300498 CR Approval 23.501 CR3922 (Rel-18, 'F'): Update for 5G reference architecture describtion for the Nupf interface China Telecom Rel-18 Postponed To be merged into S2-2300485 (Postponed) Yan (China Mobile) proposes to use 0485 as the baseline paper to discuss update on reference architecture for UPEAS and merge this 0498 into it.
Zhiwei (China Telecom): This paper has been merged into 0485
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.16.2 S2-2300135 CR Approval 23.501 CR3825 (Rel-18, 'B'): Support of NAT exposure in 23.501 according to the conclusion in UPEAS Ericsson, Nokia, Nokia Shanghai Bell, DISH Network Rel-18 r06 agreed. Revised to S2-2301390, merging S2-2300153 and S2-2300593 Yan (China Mobile) suggests to use this 0135 as the baseline paper to discuss how to support NAT exposure in TS 23.501 and merge 0153 and 0593.
Yan (China Mobile) provides r01 to merge 0593 in.
Fenqin (Huawei) provides r02
Laurent (Nokia): provides r03
Yan (China Mobile) provides comment.
Yan (China Mobile) provides r04.
Magnus H (Ericsson) provides comments
Saso (Intel) provides r05
Fenqin (Huawei) agree with Magnus.
Yan (China Mobile) provides r06.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301390 CR Approval 23.501 CR3825R1 (Rel-18, 'B'): Support of NAT exposure in 23.501 according to the conclusion in UPEAS Ericsson, Nokia, Nokia Shanghai Bell, DISH Network, Intel, China Mobile, Deutsche Telekom Rel-18 Revision of S2-2300135r06, merging S2-2300153 and S2-2300593. Approved Agreed
9.16.2 S2-2300153 CR Approval 23.501 CR3829 (Rel-18, 'B'): UE IP address mapping information exposure by UPF Intel Rel-18 Merged into S2-2301390 Yan (China Mobile) proposes to use 0135 as the baseline paper to discuss how to support NAT exposure in TS 23.501 and merge this 0153 into it.
Saso (Intel) is OK to consider 0153 MERGED into 0135.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300593 CR Approval 23.501 CR3945 (Rel-18, 'B'): UPF event exposure service update to support NAT exposure based on conclusions in FS_UPEAS China Mobile Rel-18 Merged into S2-2301390 Yan (China Mobile) proposes to use 0135 as the baseline paper to discuss how to support NAT exposure in TS 23.501 and merge this 0593 into it.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 - - - CR for 23.502 - - Docs:=15 -
9.16.2 S2-2300134 CR Approval 23.502 CR3665 (Rel-18, 'B'): Data Exposure by UPF via SBI aligned with TS 23.502 Ericsson Rel-18 r13 agreed. Revised to S2-2301391, merging S2-2300897, S2-2300899, S2-2300664, S2-2300622 and S2-2300587 Yan (China Mobile) suggests to use this 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge 0897, 0899, 0664, 0622, and 0587.
Huazhang (vivo) reply to Changki (ETRI)
Changki(ETRI) provides r01 by merging S2-2300587 into S2-2300134 with comments
Laurent (Nokia): provides r02
Huazhang (vivo) provides r03 based on r02, not change the content in r02
Changki(ETRI, S2-2300587) reply to Huazhang (vivo,S2-2300897) and all
Huazhang (vivo) reply to Changki (ETRI) that I provide a revision r03 to reflect the changes in 897
Laurent (Nokia): provides r04
Magnus H (Ericsson) provides r05
Fenqin (Huawei) provides r06
Changki(ETRI) provides r07 with comments
Magnus H (Ericsson) provides r08
Mirko (Huawei) comments.
Magnus H (Ericsson) answers
Fenqin (Huawei) provides r09
Huazhang (vivo) provides r10 based on r09, only add Nsmf_EventExposure Subscribe in step 3
Laurent (Nokia): provides r11
Mirko (Huawei) repeats comment and asks for an update which clarifies that QoS monitoring is not triggered by this procedure.
Magnus H (Ericsson) provides r13
==== Revisions Deadline ====
Huazhang (vivo) suggests to go with r13 that to move forward, thanks
Magnus H (Ericsson) provides comments
Changki (ETRI) also suggest to go with r13 and discuss other issues based on this revision with NOTEs.
Laurent (Nokia): objects to R00+R03+R08+R09+R10
Laurent (Nokia): thinks R13 is the best version and that any agreed version shall not have text in 4.15.4.x.3
(overlap with 0898)
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301391 CR Approval 23.502 CR3665R1 (Rel-18, 'B'): Data Exposure by UPF via SBI aligned with TS 23.502 Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300134r13, merging S2-2300897, S2-2300899, S2-2300664, S2-2300622 and S2-2300587. Approved Agreed
9.16.2 S2-2300897 CR Approval 23.502 CR3809 (Rel-18, 'B'): Indirect subscription via SMF service Vivo Rel-18 Merged into S2-2301391 Yan (China Mobile) proposes to use 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge this 0897 into it.
Huazhang (vivo) is ok to merge, thank Yan
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300899 CR Approval 23.502 CR3811 (Rel-18, 'B'): Remove ENs of condition for direct subscription and indirect subscription Vivo Rel-18 Merged into S2-2301391 Yan (China Mobile) proposes to use 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge this 0899 into it.
Huazhang (vivo) is ok to merge, thanks Yan
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300664 CR Approval 23.502 CR3771 (Rel-18, 'F'): Event exposure of UPF Huawei, HiSilicon Rel-18 Merged into S2-2301391 Yan (China Mobile) proposes to use 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge this 0664 into it.
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300622 CR Approval 23.502 CR3758 (Rel-18, 'C'): UPF event exposure service in TS 23.502 Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301391 Yan (China Mobile) proposes to use 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge this 0622 into it.
Laurent (Nokia): is OK to merge as the rapporteur suggested
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300587 CR Approval 23.502 CR3754 (Rel-18, 'B'): Support for UPF QoS monitoring event subscription via SMF ETRI Rel-18 Merged into S2-2301391 Yan (China Mobile) proposes to use 0134 as the baseline paper to discuss UPF Event Exposure for UPF Data Collection by NWDAF in TS 23.502 and merge this 0587 into it.
Laurent (Nokia): objects to any version for the sake of merging as proposed by the rapporteur
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300451 CR Approval 23.502 CR3726 (Rel-18, 'B'): UPF event exposure service to NWDAF for AoI in TS 23.502 China Mobile Rel-18 Postponed Aihua(China Mobile) provides r02.
Laurent (Nokia): I'd feel this Tdoc needs further work
Aihua(China Mobile) replies to Laurent (Nokia).
Magnus H (Ericsson) provides comments
Aihua(China Mobile) replies to Magnus H (Ericsson), please refer to r02.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version (asking to POSTPONE)
Fenqin (Huawei): provide comments
Aihua(China Mobile) replies to Laurent (Nokia) and suggests to get r02 approved.
==== Final Comments Deadline ====
Postponed
9.16.2 S2-2300898 CR Approval 23.502 CR3810 (Rel-18, 'B'): Update of Information flow for UPF event exposure service to NWDAF for any UE Vivo Rel-18 r08 agreed. Revised to S2-2301392. Huazhang (vivo) provide r01 to move the 4.15.11 to 4.15.4
Laurent (Nokia): provides r02
Yan (China Mobile) asks for clarification.
Huazhang (vivo) provide r03 based on r02, remove the first two paragraph because it has already been in the paper 2300134. To make no overlap
Yan (China Mobile) replies.
Huazhang (vivo) thanks to Yan to correct the link, thanks
Kenichi (KDDI) provides r06.
Fenqin(Huawei) provides r07.
Laurent (Nokia): provides r08
==== Revisions Deadline ====
Huazhang (vivo) is ok to go with r08, thanks Laurent
Magnus H (Ericsson) don't like 'NEF/UDR' in r08. Wants to replace it with 'NEF'.
Huazhang (vivo) prepares to go with r08 + replace the word 'NEF/UDR' in r08 to 'NEF'
This will be ok to you Magnus?
Magnus H (Ericsson) accepts and also wants the following to be added to the last sentence of step 7: 'with target of event Reporting any UE.'
Huazhang (vivo) suggests to go with r08 +
+ replace the word 'NEF/UDR' in r08 to 'NEF'
+ add 'with target of event Reporting any UE' to the last sentence of step 7 in r08
Laurent (Nokia): supports removing 'UDR' in any instance of'NEF/UDR' + following to be added to the last sentence of step 7: 'with target of event Reporting any UE.'
Laurent (Nokia): objects to R00+R01+R04+R05
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301392 CR Approval 23.502 CR3810R1 (Rel-18, 'B'): Update of Information flow for UPF event exposure service to NWDAF for any UE Vivo, Nokia , Nokia Shanghai Bell Rel-18 Revision of S2-2300898r08. Approved Agreed
9.16.2 S2-2300935 CR Approval 23.502 CR3817 (Rel-18, 'B'): Updates on Npcf_PolicyAuthorization service ETRI Rel-18 Postponed Laurent (Nokia): provides r01
Fenqin (Huawei): provides r02
Kefeng (Qualcomm) provides comments.
Yoohwa (ETRI) provides r03.
==== Revisions Deadline ====
Laurent (Nokia): objects to R00+R02+R03.
Fenqin (Huawei): suggest to go r03 and objects r00,r01.
==== Final Comments Deadline ====
Postponed
9.16.2 S2-2300136 CR Approval 23.502 CR3666 (Rel-18, 'B'): Support of NAT exposure in 23.502 according to the conclusion in UPEAS Ericsson, Nokia, Nokia Shanghai Bell, DISH Network Rel-18 r06 agreed. Revised to S2-2301393, merging S2-2300154 and S2-2300597 Yan (China Mobile) suggests to use this 0136 as the baseline paper to discuss how to support NAT exposure in TS 23.502 and merge 0154 and 0597.
Yan (China Mobile) provides r01 to merge 0597 in.
Saso (Intel) seeks clarification from the authors.
Sudeep (Apple) asks a question for clarification.
Jinsook (DISH) Replied to Sudeep
Naman (Samsung) provides comments
Fenqin (Huawei) provides r02
Saso (Intel) provides r03
Sudeep (Apple) provides r04.
Naman (Samsung) replies to Sudeep (Apple)
Saso (Intel) provides r05 to address comment from Naman (Samsung)
Yan (China Mobile) provides r06 to cosign.
==== Revisions Deadline ====
Jinsook (DISH) there are double figures for Figure 4.15.10-1
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301393 CR Approval 23.502 CR3666R1 (Rel-18, 'B'): Support of NAT exposure in 23.502 according to the conclusion in UPEAS Ericsson, Nokia, Nokia Shanghai Bell, DISH Network, Intel, China Mobile, Deutsche Telekom Rel-18 Revision of S2-2300136r06, merging S2-2300154 and S2-2300597. Approved Agreed
9.16.2 S2-2300154 CR Approval 23.502 CR3675 (Rel-18, 'B'): UE IP address mapping information exposure by UPF Intel Rel-18 Merged into S2-2301393 Yan (China Mobile) proposes to use 0136 as the baseline paper to discuss how to support NAT exposure in TS 23.502 and merge this 0154 into it.
Saso (Intel) is OK to consider 0154 MERGED into 0136.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 S2-2300597 CR Approval 23.502 CR3755 (Rel-18, 'B'): UPF event exposure service update to support NAT exposure based on conclusions in FS_UPEAS China Mobile Rel-18 Merged into S2-2301393 Yan (China Mobile) proposes to use 0136 as the baseline paper to discuss how to support NAT exposure in TS 23.502 and merge this 0597 into it.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.16.2 - - - CR for 23.503 - - Docs:=3 -
9.16.2 S2-2300937 CR Approval 23.503 CR0871 (Rel-18, 'B'): Updates on PDU session related policy information ETRI Rel-18 r03 agreed. Revised to S2-2301394. Yan (China Mobile) resends r01 provided by Laurent to correct the Tdoc number in email title.
Kefeng (Qualcomm) provides comments.
Yoohwa (ETRI) provides r03.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.16.2 S2-2301394 CR Approval 23.503 CR0871R1 (Rel-18, 'B'): Updates on PDU session related policy information ETRI Rel-18 Revision of S2-2300937r03. Approved Agreed
9.16.2 S2-2300133 CR Approval 23.503 CR0798 (Rel-18, 'B'): Policy update to enable NWDAF subscription to QoS monitoring event. Ericsson Rel-18 Postponed Laurent (Nokia): provides r01
Magnus H (Ericsson) provides r02
==== Revisions Deadline ====
Mirko (Huawei) objects to this CR and its revisions as the principles of the functionality are not fully clear yet.
Magnus H (Ericsson) proposes to postpone this CR
==== Final Comments Deadline ====
Postponed
9.16.2 - - - CR for 23.288 - - Docs:=1 -
9.16.2 S2-2301254 CR Approval 23.288 CR0688 (Rel-18, 'C'): NWDAF access to UPF information Nokia, Nokia Shanghai Bell Rel-18 Postponed Yan (China Mobile) comments.
Laurent (Nokia): provides r01
Antoine (Orange) comments on changes in 6.7.3.4.
Laurent (Nokia): answers
Laurent (Nokia): provides r02
==== Revisions Deadline ====
Antoine (Orange) objects to r00, r01 and r02; proposes to take out clause 6.7.3.4 to fix it at the next meeting.
==== Final Comments Deadline ====
Laurent (Nokia): asks Antoine if one version without changes to clause 6.7.3.4 would be ok?
Antoine (Orange) is OK to approve r02 without the changes to clause 6.7.3.4.
Laurent (Nokia): provides the link to the updated Tdoc per the proposal=R02 without the changes to clause 6.7.3.4
Postponed
9.17.1 - - - Study on Edge Computing Phase 2 (FS_EDGE_Ph2) - - Docs:=0 -
9.17.2 - - - Edge Computing Phase 2 (EDGE_Ph2) - - Docs:=84 -
9.17.2 - - - LSs and Rapporteur documents - - Docs:=2 -
9.17.2 S2-2301080 CR Approval 23.548 CR0105 (Rel-18, 'D'): EASDF functional description update Huawei (rapporteur) Rel-18 r02 agreed. Revised to S2-2301395. Magnus H (Ericsson) provides r01
Dario (Qualcomm) provides r02.
Patrice (Huawei) is OK with r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301395 CR Approval 23.548 CR0105R1 (Rel-18, 'B'): EASDF functional description update Huawei (rapporteur) Rel-18 Revision of S2-2301080r02. Approved Agreed
9.17.2 - - - KI#1 HR - - Docs:=14 -
9.17.2 S2-2300155 DISCUSSION Discussion KI #1, Technical issues on HR-SBO procedure. Samsung Rel-18 Noted Laurent (Nokia): proposes to note this discussion paper
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.17.2 S2-2300156 CR Approval 23.548 CR0084 (Rel-18, 'B'): Home Routed-Session Breakout (HR-SBO) support Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, CMCC, Sony Rel-18 r13 + changes agreed. Revised to S2-2301396, merging S2-2300749 Tianqi (China Unicom) provides r01 and comments.
Laurent (Nokia): provides r02
Hongsuk (LGE): provides r03
Tianqi (China Unicom) provides r04 based on r03 following the correct tdoc title.
Dan (China Mobile): provides comment
Hongsuk (LGE) provides comment
Tianqi (China Unicom) gives clarification.
Dan (China Mobile) reply
Laurent (Nokia): answers
Tianqi (China Unicom) replies.
Dan (China Mobile) provide r05
Dan (China Mobile) provide comment
Jicheol (Samsung) asks a question for clarification on ULCL replacement of IP address replacement.
Jicheol (Samsung) comments on 'Placeholder UE IP indication'.
Hongsuk (LGE) provides r06
Dan (China Mobile) reply.
Jicheol (Samsung) acked Dan(CMCC) response.
Xinpeng(Huawei) comments.
Dan(China Mobile) answers.
Hui(Huawei) provides comments.
Dan(China Mobile)some clarification.
Dario (Qualcomm) ask question about intermiediate UPF(s).
Dario (Qualcomm) asks question about Figure 4.2-3
Jicheol (Samsung) comments.
Hui(Huawei) provides r07
Hongsuk (LGE) provides comments
Jicheol (Samsung) provides r08.
Laurent (Nokia): provides r09
Magnus O (Ericsson) provides r10
Tianqi (China Unicom) provided r11.
Jicheol (Samsung) provides r12 (clean-up version) based on r11.
Svante (Sony) ask question to Magnus
Magnus (Ericsson) Answers Svante
Svante (Sony) Provides r13 on top of r12 based on Magnus answer
==== Revisions Deadline ====
Hongsuk (LGE) asks to add 'LG Electronics' to Jicheol (Samsung).
Dan(China Mobile) is ok for r12 and r13, prefer r13.
Hui(Huawei) asks question to r13(and earlier versions since r08).
Jicheol (Samsung) answers Hui.
Hui (Huawei) can accept r07 or r13 + 'EN: How to retrieve PCC rule from HPLMN to control local PSA is FFS', objects other versions
Hui(Huawei)replies to Dan.
Laurent (Nokia): objects to R07 and wants to reword the EN proposed by Hui into 'It is FFS how information to steer traffic offload received by H-SMF in PCC rule is transferred to the VPLMN'
Laurent (Nokia): objects to R07 and wants to reword the EN proposed by Hui into 'It is FFS whether and how information to steer traffic offload received by H-SMF in PCC rule is transferred to the VPLMN' + add in § 6.7.2.4 : the content of this clause may be subject to change
Laurent (Nokia): another possibility is to Only endorse R13
Hui (Huawei) replies to Laurent
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301396 CR Approval 23.548 CR0084R1 (Rel-18, 'B'): Home Routed-Session Breakout (HR-SBO) support Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, CMCC, Sony, LGE Rel-18 CC#4: Revision of S2-2300156r13 + change, merging S2-2300749. Approved Agreed
9.17.2 S2-2300157 CR Approval 23.502 CR3676 (Rel-18, 'B'): HR-SBO support SM subscription data and SMF services Samsung, Sony Rel-18 r02 agreed. Revised to S2-2301397. Laurent (Nokia): provides r01
Jicheol (Samsung) provide r02.
Laurent (Nokia): answers
Jicheol (Samsung) comments.
==== Revisions Deadline ====
Laurent (Nokia): objects to R00
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301397 CR Approval 23.502 CR3676R1 (Rel-18, 'B'): HR-SBO support SM subscription data and SMF services Samsung, Sony, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300157r02. Approved Agreed
9.17.2 S2-2300158 CR Approval 23.501 CR3830 (Rel-18, 'B'): The support of Home Routed PDU Session supporting Session Breakout in VPLMN (HR-SBO) Samsung, Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2301398. Dario (Qualcomm) asks questions for understanding.
Hui (Huawei) provides r01.
Jicheol (Samsung) is fine with r01.
Laurent (Nokia): provides r02
==== Revisions Deadline ====
Hui (Huawei) fine with r02
Laurent (Nokia): objects to R01
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301398 CR Approval 23.501 CR3830R1 (Rel-18, 'B'): The support of Home Routed PDU Session supporting Session Breakout in VPLMN (HR-SBO) Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon Rel-18 Revision of S2-2300158r02. Approved Agreed
9.17.2 S2-2300159 CR Approval 23.503 CR0800 (Rel-18, 'B'): VPLMN specific roaming offloading policy for HR-SBO Samsung Rel-18 Postponed Laurent (Nokia): has reservation with the Tdoc (VPLMN specific roaming offloading policy coming from UDM and not from PCF)
Dario (Qualcomm) asks questions for understanding.
Jicheol (Samsung) comments and answers.
Laurent (Nokia): objects to This paper (we have not decided upon either PCF or UDM source for Hr-SBO authorization)
Magnus (Ericsson) comment
==== Revisions Deadline ====
Jicheol (Samsung) propose to postpone.
Laurent (Nokia): supports postponing
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300534 CR Approval 23.548 CR0089 (Rel-18, 'B'): Handling AF traffic influence for HR-SBO PDU Sessions Samsung Rel-18 Postponed Laurent (Nokia): suggest to postpone once we have not decided upon 1030
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of 0534 (to make sure it is postponed) (needs more offline work and F2F meeting)
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300546 CR Approval 23.502 CR3745 (Rel-18, 'B'): Processing AF traffic influence for HR-SBO PDU Sessions Samsung Rel-18 Postponed Dario (Qualcomm) asks question for clarification.
Magnus (Ericsson) propose to postpone this doc until a decision has been made on 1030 and the related CR in 534
Hyesung (Samsung) replies.
Laurent (Nokia): let's postpone all documents related to 1030
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of 0546 (to make sure it is postponed)
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300509 CR Approval 23.548 CR0088 (Rel-18, 'B'): The EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO China Unicom Rel-18 r05 agreed. Revised to S2-2301399. Jicheol (Samsung) comments.
Tianqi (China Unicom) provides r01 and replies.
Laurent (Nokia): provides r02
Tianqi (China Unicom) provided r03 and replies.
Magnus (Ericsson) comments
Tianqi (China Unicom) replies.
Laurent (Nokia): provides r04
Tianqi (China Unicom) provided r05.
==== Revisions Deadline ====
Tianqi (China Unicom) is fine with r05.
Laurent (Nokia): objects to any version except R04 and R05.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301399 CR Approval 23.548 CR0088R1 (Rel-18, 'B'): The EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO China Unicom Rel-18 Revision of S2-2300509r05. Approved Agreed
9.17.2 S2-2300749 CR Approval 23.548 CR0091 (Rel-18, 'B'): DNS Query transmission to HPLMN for HR-SBO PDU session China Mobile, Rel-18 Merged into S2-2301396 Laurent (Nokia): provides r01, we could also POSTPONE this Tdoc
Magnus (Ericsson) Agrees with Laurent
Dan (China Mobile) suggest we can have the discussion in 2300156
Jicheol (Samsung) comments.
Dan(China Mobile) reply
Dan(China Mobile) suggest this paper merged into S2-2300156
Jicheol (Samsung) is okay to merge this to S2-2300156
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.17.2 S2-2300921 DISCUSSION Agreement Discussion of the Editor s Notes for HR-SBO scenario. Ericsson Rel-18 Noted Laurent (Nokia): proposes to note this discussion paper
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.17.2 - - - KI#1 HR edge relocation - - Docs:=3 -
9.17.2 S2-2300908 CR Approval 23.501 CR4016 (Rel-18, 'B'): Support of edge relocation for accessing EHE when roaming CATT Rel-18 Postponed Dario (Qualcomm): if 0909 and 0910 are postponed, the cover page needs to be updated.
Laurent (Nokia): objects to any version of 908 as this Tdoc is linked with 0910
Yuan Tao (CATT) replies to Laurent (Nokia)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300909 CR Approval 23.503 CR0868 (Rel-18, 'B'): Support of edge relocation for accessing EHE when roaming CATT Rel-18 Postponed Laurent (Nokia): proposes to NOTE or POSTPONE this Tdoc
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300910 CR Approval 23.548 CR0100 (Rel-18, 'B'): Support of edge relocation for accessing EHE when roaming CATT Rel-18 Postponed Yuan Tao (CATT) provides r01.
Laurent (Nokia): objects to this Tdoc : Transforming a LBO PDU session into an HR PDU Session is not part of the TR conclusions; this has very strong impacts that have not been studied
Yuan Tao (CATT) replies to Laurent (Nokia) to clarify the procedure is not to transform a LBO PDU session into an HR PDU Session, and provides r02.
Jicheol (Samsung) asks questions for clarifications on the scenario of the procedures.
Yuan Tao (CATT) replies to Jicheol (Samsung).
Dario (Qualcomm) asks questions for clarification.
Yuan Tao (CATT) replies to Dario (Qualcomm).
==== Revisions Deadline ====
Laurent (Nokia): objects to ANY version of this Tdoc (fundamental issues are not solved)
Yuan Tao (CATT) asks Laurent (Nokia) for clarification about the fundamental issues.
Dario (Qualcomm) objects to all revisions
==== Final Comments Deadline ====
Postponed
9.17.2 - - - KI#1 HR rediscovery - - Docs:=5 -
9.17.2 S2-2301030 DISCUSSION Discussion KI#1 HR Discussion on AF deployed in VPLMN triggered EAS Re-discovery via interacting with VPLMN Huawei, HiSilicon Rel-18 Noted Laurent (Nokia): comments
Hui (Huawei) replies
Magnus (Ericsson) comments
Yaxin (OPPO) comments.
Hui (Huawei) replies.
Laurent (Nokia): replies,
Hyesung (Samsung) comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.17.2 S2-2301032 CR Approval 23.548 CR0073R1 (Rel-18, 'B'): EAS Re-discovery Procedure with EASDF in HR roaming scenario Huawei, HiSilicon Rel-18 Revision of S2-2210509. r04 agreed. Revised to S2-2301400. Yuan Tao (CATT) asks for clarification.
Laurent (Nokia): provides r01
Hui (Huawei) fine with r01 and responses to Yuan.
Dario (Qualcomm) asks questions and proposes some changes.
Hui (Huawei) provides r02.
Yuan Tao (CATT) comments.
Laurent (Nokia): provides r03
Jicheol (Samsung) provides r04.
==== Revisions Deadline ====
Hui (Huawei) replies to Jicheol.
Jicheol (Samsung) comments.
Laurent (Nokia): objects to R00, R01 and R02
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301400 CR Approval 23.548 CR0073R2 (Rel-18, 'B'): EAS Re-discovery Procedure with EASDF in HR roaming scenario Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung Rel-18 Revision of S2-2301032r04. Approved Agreed
9.17.2 S2-2301033 CR Approval 23.502 CR3619R1 (Rel-18, 'B'): EAS Re-discovery with EASDF for HR PDU session Huawei, HiSilicon Rel-18 Revision of S2-2210510. r04 agreed. Revised to S2-2301401. Dario (Qualcomm) asks question on the applicability of the SM Context fields.
Hui (Huawei) provides r01.
Jicheol (Samsung) provides r02 and cosigned.
Laurent (Nokia): provides r03
Hui(Huawei) provides r04
==== Revisions Deadline ====
Laurent (Nokia): objects to R00, R01 and R02
Jicheol (Samsung) is fine with r03 and r04.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301401 CR Approval 23.502 CR3619R2 (Rel-18, 'B'): EAS Re-discovery with EASDF for HR PDU session Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2301033r04. Approved Agreed
9.17.2 - - - KI#1 EACI - - Docs:=6 -
9.17.2 S2-2300888 CR Approval 23.502 CR3808 (Rel-18, 'B'): ECS Address Configuration Information delivery in roaming Vivo, Nokia, Nokia Shanghai Bell Rel-18 Confirm CR Revision - CR states 1! r04 agreed. Revised to S2-2301402. Laurent (Nokia): provides r01
Hyesung (Samsung) comments.
Huazhang (vivo) reply to Hyesung to see the reply and revision in 889
Yaxin (OPPO) comments to r01.
Huazhang (vivo) provides r02 to add an ENs based on r01, in order to move forward. And Huazhang prefer in next meeting to solve this problem of whether introduce new service or reuse the parameter provision procedure
Yaxin (OPPO) is OK with r02.
Hyesung (Samsung) comments on r02.
Dario (Qualcomm) provides r03
Huazhang (vivo) provides r04 based on r03
==== Revisions Deadline ====
Laurent (Nokia): objects to R00,
Huazhang (vivo) prefers to go with r04
Dario (Qualcomm) is OK with r04
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301402 CR Approval 23.502 CR3808R1 (Rel-18, 'B'): ECS Address Configuration Information delivery in roaming Vivo, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300888r04. Approved Agreed
9.17.2 S2-2300889 CR Approval 23.548 CR0096 (Rel-18, 'B'): ECS Address Configuration Information delivery in roaming Vivo, Huawei, Nokia, Nokia Shanghai Bell, CMCC Rel-18 r02 agreed. Revised to S2-2301403. Hyesung (Samsung) ask a question for clarification.
Huazhang (vivo) reply to Hyesung and provide r01
Dario (Qualcomm) provides r02
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 and R01
Huazhang (vivo) is ok to go with r02
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301403 CR Approval 23.548 CR0096R1 (Rel-18, 'B'): ECS Address Configuration Information delivery in roaming Vivo, Huawei, Nokia, Nokia Shanghai Bell, CMCC Rel-18 Revision of S2-2300889r02. Approved Agreed
9.17.2 S2-2300892 LS OUT Approval [DRAFT] LS on ECS associated with multiple PLMNs vivo r03 agreed. Revised to S2-2301404. Hyesung (Samsung) comments.
Huazhang (vivo) provides r01
Dario (Qualcomm) provides r02
Huazhang (vivo) represent Dario to copy the r02 of this paper
==== Revisions Deadline ====
Laurent (Nokia): Comments (late proposal to remove 'even now the UE are not roaming in some of the PLMN IDs')
Huazhang (vivo) suggests to go with r02 + removing the words: 'even now the UE are not roaming in some of the PLMN IDs?'
Dario (Qualcomm) provides and proposes to go with r03 = r02 with removal of text required by Laurent + editorial corrections.
Huazhang (vivo) thanks Dario, that the r03 is ok to me
This is the LS, that prefer to directly approve this version 3
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301404 LS OUT Approval LS on Edge Configuration Server associated with or serves multiple PLMNs SA WG2 - Revision of S2-2300892r03. Approved Approved
9.17.2 - - - KI#3 - - Docs:=7 -
9.17.2 S2-2300913 CR Approval 23.501 CR3761R3 (Rel-18, 'C'): Introducing selection of more granular set of UEs Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2211357. r02 agreed. Revised to S2-2301405, merging S2-2301019 Xinpeng(Huawei) provides r01.
Tingfang Tang (Lenovo) asks for clarification.
Magnus H (Ericsson) provides comments
Laurent (Nokia): provides r02
Tingfang Tang (Lenovo) asks for clarification from Laurent.
Laurent (Nokia): answers
Tingfang Tang (Lenovo) replies to Laurent further.
Tingfang Tang (Lenovo) is OK with Laurent's proposal and agree with r02.
==== Revisions Deadline ====
Tingfang Tang (Lenovo) is ok with r02, objects r00, r01.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301405 CR Approval 23.501 CR3761R4 (Rel-18, 'C'): Introducing selection of more granular set of UEs Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300913r02, merging S2-2301019. Approved Agreed
9.17.2 S2-2300914 CR Approval 23.502 CR3603R3 (Rel-18, 'C'): Introducing selection of more granular set of UEs Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2211358. r03 agreed. Revised to S2-2301406, merging S2-2301020 Xinpeng(Huawei) provides r01.
Tingfang Tang (Lenovo) asks for clarification.
Magnus H (Ericsson) provides comments
Tingfang Tang (Lenovo) provides r02.
Magnus H (Ericsson) provides r03
==== Revisions Deadline ====
Tingfang Tang (Lenovo) is OK r03.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301406 CR Approval 23.502 CR3603R4 (Rel-18, 'C'): Introducing selection of more granular set of UEs Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300914r03, merging S2-2301020. Approved Agreed
9.17.2 S2-2300915 CR Approval 23.503 CR0763R3 (Rel-18, 'C'): Introducing selection of more granular set of UEs Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2211359. Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.17.2 S2-2301019 CR Approval 23.501 CR4041 (Rel-18, 'C'): Introducing selection of more granular set of UEs Lenovo, Huawei, HiSilicon Rel-18 Merged into S2-2301405 Laurent (Nokia): asks questions. Can't accept this Tdoc without having answers that can be understood
Tingfang Tang (Lenovo) replies to Laurent.
Magnus H (Ericsson) provides some more questions
Tingfang Tang (Lenovo) replies to Magnus H r2.
Laurent (Nokia): Comments, making a proposal
==== Revisions Deadline ====
Tingfang Tang (Lenovo) proposes to mark this contribution to be merged into S2-2300913.
Magnus H (Ericsson) objects to this CR, let's work on 0913
Laurent (Nokia): agrees that it should be merged in 0913
==== Final Comments Deadline ====
Merged
9.17.2 S2-2301020 CR Approval 23.502 CR3827 (Rel-18, 'C'): Introducing selection of more granular set of UEs Lenovo, Huawei, HiSilicon Rel-18 Merged into S2-2301406 Magnus H (Ericsson) provides comments
Laurent (Nokia): asks similar questions as Magnus
Tingfang Tang (Lenovo) replies to Magnus.
Tingfang Tang (Lenovo) replies to Laurent.
Tingfang Tang (Lenovo) replies to Magnus for further clarification.
Laurent (Nokia): Comments, making a proposal
Tingfang Tang (Lenovo) thanks for the proposal from Laurent and comments.
Laurent (Nokia): answers
Tingfang Tang (Lenovo) replies to Magnus r2.
Tingfang Tang (Lenovo) replies to Laurent for further clarification.
==== Revisions Deadline ====
Tingfang Tang (Lenovo) proposes to mark this contribution to be merged with S2-2300914.
Laurent (Nokia): agrees that it should be merged in 0914
==== Final Comments Deadline ====
Merged
9.17.2 - - - KI#4 - - Docs:=19 -
9.17.2 S2-2300813 CR Approval 23.501 CR3987 (Rel-18, 'B'): KI#4 23.501 AF traffic influence for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT Rel-18 r04 agreed. Revised to S2-2301407. Magnus H (Ericsson) provides comments
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Shubhranshu (Nokia) comments
Xinpeng(Huawei) replies.
Xinpeng(Huawei) provides r01.
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Tugce (NTT DOCOMO) provides r02.
Xinpeng(Huawei) provides r03.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301407 CR Approval 23.501 CR3987R1 (Rel-18, 'B'): KI#4 23.501 AF traffic influence for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT, NTT DOCOMO Rel-18 Revision of S2-2300813r04. Approved Agreed
9.17.2 S2-2300814 CR Approval 23.502 CR3792 (Rel-18, 'B'): KI#4 23.502 AF traffic influence for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT Rel-18 Revised to S2-2301408, merging S2-2300175 ==== Revisions Deadline ====
Tugce (NTT DOCOMO) requests for a change to align the text with related CR -0813 by removing: 'or PCF could get the common EAS or common DNAI from group data if dynamic group is used.'
Xinpeng(Huawei) replies.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301408 CR Approval 23.502 CR3792R1 (Rel-18, 'B'): KI#4 23.502 AF traffic influence for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT Rel-18 Revision of S2-2300814, merging S2-2300175. Approved Agreed
9.17.2 S2-2300815 CR Approval 23.503 CR0859 (Rel-18, 'B'): KI#4 23.503 PCC rule for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT Rel-18 r01 agreed. Revised to S2-2301409. Xinpeng(Huawei) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301409 CR Approval 23.503 CR0859R1 (Rel-18, 'B'): KI#4 23.503 PCC rule for common EAS, DNAI selection Huawei, HiSilicon, Lenovo, CATT Rel-18 Revision of S2-2300815r01. Approved Agreed
9.17.2 S2-2300816 CR Approval 23.548 CR0093 (Rel-18, 'B'): KI#4 23.548 common EAS enforcement for set of UEs Huawei, HiSilicon, Lenovo, CATT Rel-18 r04 agreed. Revised to S2-2301410. Shubhranshu (Nokia) asks for clarification
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) responds and asks for clarification
Xinpeng(Huawei) provides r01.
Shubhranshu (Nokia) comments
Xinpeng(Huawei) provides r02.
Magnus H (Ericsson) provides r03
Xinpeng(Huawei) provides r04.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301410 CR Approval 23.548 CR0093R1 (Rel-18, 'B'): KI#4 23.548 common EAS enforcement for set of UEs Huawei, HiSilicon, Lenovo, CATT Rel-18 Revision of S2-2300816r04. Approved Agreed
9.17.2 S2-2300175 CR Approval 23.502 CR3679 (Rel-18, 'B'): KI#4: AF traffic influence for common EAS, DNAI selection NTT DOCOMO Rel-18 Merged into S2-2301408 Xinpeng(Huawei) suggests to merge 0175 into 0814.
Tugce (NTT DOCOMO) agrees to merge.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.17.2 S2-2300176 CR Approval 23.548 CR0087 (Rel-18, 'B'): KI#4: AF traffic influence for common EAS, DNAI selection NTT DOCOMO Rel-18 r04 agreed. Revised to S2-2301411. Xinpeng(Huawei) provides r01.
Tugce (NTT DOCOMO) provides r02.
Xinpeng(Huawei) provides r03.
Xinpeng(Huawei) provides r04.
Xinpeng(Huawei) replies.
Tugce (NTT DOCOMO) comments.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301411 CR Approval 23.548 CR0087R1 (Rel-18, 'B'): KI#4: AF traffic influence for common EAS, DNAI selection NTT DOCOMO Rel-18 Revision of S2-2300176r04. Approved Agreed
9.17.2 S2-2300184 CR Approval 23.502 CR3681 (Rel-18, 'B'): A New Service for Selection of Common DNAI NTT DOCOMO Rel-18 Postponed Shubhranshu (Nokia) comments
Tugce (NTT DOCOMO) responds
Shubhranshu (Nokia) responds
==== Revisions Deadline ====
Tugce (NTT DOCOMO) comments
Tugce (NTT DOCOMO) proposes to continue with r00 by adding an Editor's Note: It is FFS how to address race conditions that may occur when multiple SMFs use Nbsf_Management_Register service and whether to use the majority of UEs when selecting the common DNAI.
Shubhranshu (Nokia) objects this paper
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300911 CR Approval 23.548 CR0101 (Rel-18, 'B'): Select common DNAI/EAS for a set of UEs CATT Rel-18 r03 agreed. Revised to S2-2301412. Xinpeng(Huawei) provides r01.
Yuan Tao (CATT) is fine with r01.
Xinpeng(Huawei) provides r02.
Yuan Tao (CATT) provide r03.
==== Revisions Deadline ====
Xinpeng(Huawei) agrees with r03, and objects to other revisions.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301412 CR Approval 23.548 CR0101R1 (Rel-18, 'B'): Select common DNAI/EAS for a set of UEs CATT Rel-18 Revision of S2-2300911r03. Approved Agreed
9.17.2 S2-2301034 CR Approval 23.501 CR3789R1 (Rel-18, 'B'): Common EAS/DNAI selection by AF Huawei, HiSilicon Rel-18 Revision of S2-2210552. Check Affected Clauses! Revised to S2-2301413. ==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301413 CR Approval 23.501 CR3789R2 (Rel-18, 'B'): Common EAS/DNAI selection by AF Huawei, HiSilicon Rel-18 Revision of S2-2301034. Approved Agreed
9.17.2 S2-2301035 CR Approval 23.502 CR3831 (Rel-18, 'B'): Common EAS/DNAI selection by AF Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.17.2 S2-2301232 CR Approval 23.502 CR3655R1 (Rel-18, 'B'): Influencing UPF and EAS (re)location for collections of UEs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2210915. Postponed Xinpeng(Huawei) comments.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) provides r01
==== Revisions Deadline ====
Tugce (NTT DOCOMO) comments
Magnus H (Ericsson) wants to postpone this CR to next meeting
Shubhranshu (Nokia) proposes to agree this paper
Tugce (NTT DOCOMO) objects
Magnus H (Ericsson) objects to this CR
Shubhranshu (Nokia) ok to postpone
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2301259 CR Approval 23.548 CR0106 (Rel-18, 'B'): Influencing UPF and EAS (re)location for collections of UEs Nokia, Nokia Shanghai Bell Rel-18 Postponed Magnus H (Ericsson) provides comments
Shubhranshu (Nokia) responds
Xinpeng(Huawei) comments.
Xinpeng(Huawei) Shubhranshu (Nokia).
==== Revisions Deadline ====
Magnus H (Ericsson) wants to postponed this CR to next meeting
Shubhranshu (Nokia) ok to postpone
==== Final Comments Deadline ====
Postponed
9.17.2 - - - KI#4 Edge relocation - - Docs:=4 -
9.17.2 S2-2301022 CR Approval 23.501 CR4042 (Rel-18, 'C'): Edge relocation with common DNAI Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.17.2 S2-2301023 CR Approval 23.502 CR3828 (Rel-18, 'C'): Edge relocation with common DNAI Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.17.2 S2-2300818 CR Approval 23.548 CR0095 (Rel-18, 'B'): Common DNAI relocation Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301414. Tingfang Tang (Lenovo) provides r01.
Tugce (NTT DOCOMO) provides r02.
Magnus H (Ericsson) provides comments
Xinpeng(Huawei) provides r03.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301414 CR Approval 23.548 CR0095R1 (Rel-18, 'B'): Common DNAI relocation Huawei, HiSilicon, Lenovo Rel-18 Revision of S2-2300818r03. Approved Agreed
9.17.2 - - - KI#5 - - Docs:=9 -
9.17.2 S2-2301238 CR Approval 23.501 CR3820R1 (Rel-18, 'B'): Edge Relocation within the same hosting PLMN's EHEs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2210918. Revised to S2-2301247 Revised
9.17.2 S2-2301247 CR Approval 23.501 CR3820R2 (Rel-18, 'B'): Edge Relocation within the same hosting PLMN's EHEs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301238. Postponed Xinpeng(Huawei) comments.
Yuan Tao (CATT) comments.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) replies.
Yuan Tao (CATT) thinks the proposed texts are quite unclear and provides further comments.
Shubhranshu (Nokia) further clarifies
Dario (Qualcomm) asks questions for clarification.
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Yuan Tao (CATT) provides further comments.
==== Revisions Deadline ====
Xinpeng(Huawei) proposes to postpone the paper.
Shubhranshu (Nokia) proposes to agree this paper
Yuan Tao (CATT) proposes to postpone this paper.
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2301251 CR Approval 23.502 CR3656R1 (Rel-18, 'B'): Edge Relocation within the same hosting PLMN's EHEs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2210919. Postponed Dario (Qualcomm) proposes to add an EN
Shubhranshu (Nokia) responds, and provides r01
Xinpeng(Huawei) comments.
Shubhranshu (Nokia) comments
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) provides r02
==== Revisions Deadline ====
Xinpeng(Huawei) proposes to postpone the paper.
Yuan Tao (CATT) proposes to postpone this paper.
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2301255 CR Approval 23.548 CR0083R1 (Rel-18, 'B'): Edge Relocation within the same hosting PLMN's EHEs Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2210920. Confirm Spec version used - CR states {{No Current version}}! Postponed Yuan Tao (CATT) comments.
Shubhranshu (Nokia) responds
Dario (Qualcomm): please see my comments for 1247
Shubhranshu (Nokia) responds, and provides r01
==== Revisions Deadline ====
Xinpeng(Huawei) proposes to postpone the paper.
Yuan Tao (CATT) proposes to postpone this paper.
==== Final Comments Deadline ====
Postponed
9.17.2 S2-2300817 CR Approval 23.548 CR0094 (Rel-18, 'B'): KI#5 EDI extension for EAS discovery for GSMA OPG scenario Huawei, HiSilicon, Lenovo Rel-18 r01 agreed. Revised to S2-2301415, merging S2-2300904 Hyesung (Samsung) provides comments.
Xinpeng(Huawei) replies and provides r01.
Tingfang Tang (Lenovo) comments.
Magnus (Ericsson) comments
Dario (Qualcomm) thinks that with the latest GSMA OPG reply this CR is not needed.
Xinpeng(Huawei) replies to Dario (Qualcomm).
==== Revisions Deadline ====
Tangqing(China Mobile) is ok with r01.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301415 CR Approval 23.548 CR0094R1 (Rel-18, 'B'): KI#5 EDI extension for EAS discovery for GSMA OPG scenario Huawei, HiSilicon, Lenovo Rel-18 Revision of S2-2300817r01, merging S2-2300904. Approved Agreed
9.17.2 S2-2300893 CR Approval 23.548 CR0098 (Rel-18, 'B'): Information sharing between PLMN to support GSMA OPG Vivo Rel-18 r07 agreed. Revised to S2-2301416. Laurent (Nokia): Comments and potential concerns with the CR
Magnus (Ericsson) I don't agree with this CR
Huazhang (vivo) provides r01
Laurent (Nokia): as I still have questions, I provide r02
Magnus O (Ericsson) support r02
Tingfang Tang (Lenovo) provides r04.
Magnus (Ericsson) is ok with r02, can live with r03 and object to r04.
Tingfang Tang (Lenovo) replies to Manus.
Huazhang (vivo) prefer to go with r03,
Magnus (Ericsson) provides further comments
Tingfang Tang (Lenovo) replies to Manus r2.
Huazhang (vivo) provides r05 and prefer to agree the minimum set
Magnus (Ericsson) Answers Tingfang
Tingfang Tang (Lenovo) replies to Manus r3.
Magnus O (Ericsson) provides r07
==== Revisions Deadline ====
Dario (Qualcomm) is OK w/ r07.
Huazhang (vivo) is ok for r07, thanks
Laurent (Nokia): objects to R00, R01, R04
Tingfang Tang (Lenovo) is OK with r07.
Xinpeng(Huawei) is ok with r07, r03, objects to all others.
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301416 CR Approval 23.548 CR0098R1 (Rel-18, 'B'): Information sharing between PLMN to support GSMA OPG Vivo Rel-18 Revision of S2-2300893r07. Approved Agreed
9.17.2 S2-2300904 CR Approval 23.548 CR0099 (Rel-18, 'B'): KI#5: Support of EAS discovery of GSMA OPG scenario China Mobile Rel-18 Merged into S2-2301415 Laurent (Nokia): comments and first level of questions
Tangqing(China Mobile) replies to Laurent.
Magnus (Ericsson) provides comments
Hyesung (Samsung) asks a question for clarification.
Tangqing(China Mobile) replies to Magnus, Hyesung and provides r01.
Hyesung (Samsung) provides comments.
Tangqing(China Mobile) provides r02.
Magnus (Ericsson) Proposes to Note this document
Tingfang Tang (Lenovo) asks clarification to Magnus O.
Magnus (Ericsson) comments
Dario (Qualcomm) supports Ericsson.
Tingfang Tang (Lenovo) further comments.
Tangqing(China Mobile) comments, this paper is merged into S2-2300817.
==== Revisions Deadline ====
Laurent (Nokia): Supports Magnus who Proposes to Note this document : objects to any version
==== Final Comments Deadline ====
Merged
9.17.2 - - - KI#7 - - Docs:=6 -
9.17.2 S2-2300783 CR Approval 23.548 CR0092 (Rel-18, 'B'): DNAI mapping based on conclusions in TR 23.700-48 China Mobile Rel-18 r08 agreed. Revised to S2-2301417. Magnus H (Ericsson) provides r01
Huazhang (vivo) provides r02 based on r01, no changes of the content in r01
Tangqing(China Mobile) provides r03.
Patrice (Huawei) provides r04, cosigns.
Dario (Qualcomm) provides r05.
Tangqing(China Mobile) reply to Dario and support for r06.
Patrice (Huawei) provides r07, objects r05.
Magnus H (Ericsson) provides r08
==== Revisions Deadline ====
Tangqing(China Mobile) is ok with r07.
Patrice (Huawei) ok with r07, not OK with r08 as it is which modifies more than just adding an EN. Alternatively, the following changes to r08 can be made : remove '[Optional]' from S-NSSAI in the table + add 'S-NSSAI/' in front of DNN 3 times in the Editor's note.
Magnus H (Ericsson) objects to all revisions except r01 and r08 and cannot accept Patrice's proposed changes on top of r08 since we see S-NSSAI as a sub Key and therefor it is optional.
Patrice (Huawei) comments. r01 and r08 not acceptable. r08 can only be acceptable with the change previously mentioned.
Tangqing(China Mobile) comments. r08 is ok with deleting table Table 6.x.1-1 and related ENs.
Tangqing(China Mobile) would like to check whether 'r08+ deleting table Table 6.x.1-1 and related ENs' is OK for Patrice and Magnus
Patrice (Huawei) accepts Tangqing (China Mobile)'s proposal.
Magnus H (Ericsson) accepts Tangqing (China Mobile)'s proposal with the addition that sentence: 'The EAS address and DNAI Mapping Information record in UDR is shown Table 6.x.1-1.' Is removed
Dan(China Mobile) provide r09: r08+removing [optional] for S-NSSAI+EN' Editor's Note: how the above parameters can be used as key/sub Key is FFS
'
Magnus H (Ericsson) accepts r09
Patrice (Huawei) is OK with r09 as described by Dan.
Dan(China Mobile) check whether r09 is ok or not?
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301417 CR Approval 23.548 CR0092R1 (Rel-18, 'B'): DNAI mapping based on conclusions in TR 23.700-48 China Mobile, Huawei Rel-18 Revision of S2-2300783r08. Approved Agreed
9.17.2 S2-2300784 CR Approval 23.502 CR3789 (Rel-18, 'B'): NEF and UDR service update to support for DNAI mapping China Mobile Rel-18 r06 agreed. Revised to S2-2301418. Magnus H (Ericsson) provides comments
Magnus H (Ericsson) provides r01
Tangqing(China Mobile) replies to Magnus.
Tangqing(China Mobile) provide r02.
Patrice (Huawei) comments to Magnus.
Dario (Qualcomm) provides r03.
Tingfang Tang (Lenovo) clarifies to Magnus.
Tangqing(China Mobile) reply to Dario, Magnus and provide r04.
Magnus H (Ericsson) ask for clarification
Huazhang (vivo) provides r05 to add the ENs to reflect the data key
Tangqing(China Mobile) reply to Magnus.
Magnus H (Ericsson) provides r06
==== Revisions Deadline ====
Tangqing(China Mobile) is ok with r05, r06.
Patrice (Huawei) will survive at the approval of r05 or r06.:)
Magnus H (Ericsson) objects to all revisions except r01 and r06
Tangqing(China Mobile) suggest to go with r06
==== Final Comments Deadline ====
Revised
9.17.2 S2-2301418 CR Approval 23.502 CR3789R1 (Rel-18, 'B'): NEF and UDR service update to support for DNAI mapping China Mobile Rel-18 Revision of S2-2300784r06. Approved Agreed
9.17.2 S2-2301081 CR Approval 23.501 CR4054 (Rel-18, 'B'): AF obtaining DNAI associated to EAS Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.17.2 S2-2300891 CR Approval 23.548 CR0097 (Rel-18, 'B'): SMF obtains DNAI from NEF/UDR to select user plane Vivo Rel-18 Noted Dario (Qualcomm) thinks this is out of scope of the SI conclusions.
Huazhang (vivo) reply to Dario
Patrice (Huawei) agrees with Dario (Qualcomm) that this is out of scope of the conclusion and should be noted. Besides, it is incorrect.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.17.2 - - - Documents exceeding TU budget - - Docs:=9 -
9.17.2 S2-2300174 CR Approval 23.501 CR3836 (Rel-18, 'B'): KI#4: AF traffic influence for common EAS, DNAI selection NTT DOCOMO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2300459 CR Approval 23.501 CR3909 (Rel-18, 'B'): KI#4 General description for Application Function influence on traffic routing NEC Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2300547 CR Approval 23.548 CR0090 (Rel-18, 'B'): HR-SBO resolving EN for when to select V-EASDF LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2300890 CR Approval 23.501 CR4013 (Rel-18, 'B'): Update supporting Edge Computing Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2300918 CR Approval 23.502 CR3815 (Rel-18, 'B'): DNAI mapping based on conclusions in TR 23.700-48 Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2300919 CR Approval 23.548 CR0102 (Rel-18, 'B'): DNAI mapping based on conclusions in TR 23.700-48 Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2301021 CR Approval 23.548 CR0103 (Rel-18, 'C'): Edge relocation with common DNAI Lenovo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2301031 CR Approval 23.501 CR3781R1 (Rel-18, 'B'): Support EC for HR PDU Session Huawei, HiSilicon Rel-18 Revision of S2-2210505 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.17.2 S2-2301061 CR Approval 23.548 CR0104 (Rel-18, 'B'): AF triggered EAS re-discovery via HR PDU session CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.1 - - - Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) - - Docs:=9 -
9.18.1 S2-2300948 CR Approval 23.700-25 CR0007 (Rel-18, 'C'): KI3 conclusion update Huawei, HiSilicon Rel-18 CC#5: Noted Sang-Jun (Samsung) supports the CR and provides r01 with a small correction and Samsung co-sign.
zhendong (ZTE) provides comments.
Runze (Huawei) replies to zhendong (ZTE).
Sebastian (Qualcomm) asks questions
zhendong (ZTE) share the view with qualcomm and provides comments.
zhendong (ZTE) provides r02.
==== Revisions Deadline ====
Runze (Huawei) is ok with r02.
Sang-Jun (Samsung) can live with r02
Devaki (Nokia) prefers r02 as it is aligned with working assumption from SA2#154 (and objects to other versions).
Jari (NTT DOCOMO) Objects all revisions and r00
zhendong (ZTE) provides two options.
Jari (NTT DOCOMO) provides r03 for CC
zhendong (ZTE) provides response.
Jari (NTT DOCOMO) responds
Sebastian (Qualcomm) objects to all versions; can be ok with r02 if all occurrences of 'AMF' in the new text are replaced by 'TSCTSF' and if this sentence 'If the parameters in the AF request exceeds the parameters in subscription, the AMF use the parameters in the subscription. ' is replaced by 'If the parameters in the AF request exceeds the parameters in subscription, the TSCTSF rejects the request. '
Shabnam (Ericsson) provides comments objects too all revisions and original, to update to this KI as we only had KI#1 and 6 open and don't see why we are changing KI#3 conclusion now? We prefer to take discussion in normative work
==== Final Comments Deadline ====
Runze (Huawei) provides r04, using Sebastian's proposal, and propose it for CC#4.
Noted
9.18.1 S2-2300414 CR Approval 23.700-25 CR0003 (Rel-18, 'C'): TR 23.700 KI#6 conclusion update Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2301419. zhendong (ZTE) provides the comments.
Sang-Jun (Samsung) supports the CR and provides r01 with a correction on the coversheet and Samsung co-sign.
Haiyang(Huawei) comments
Devaki (Nokia) comments.
Haiyang(Huawei) clarifies
zhendong (ZTE) provides response.
Haiyang(Huawei) provides r01
Devaki (Nokia) replies and provides r02.
Haiyang (Huawei) is OK with r02.
Devaki (Nokia) prefers r00.
Sebastian (Qualcomm) provides r03
Haiyang (Huawei) provides r04.
Sebastian (Qualcomm) provides r05
==== Revisions Deadline ====
Haiyang (Huawei) is OK with r05.
==== Final Comments Deadline ====
Revised
9.18.1 S2-2301419 CR Approval 23.700-25 CR0003R1 (Rel-18, 'C'): TR 23.700 KI#6 conclusion update Nokia, Nokia Shanghai Bell, Samsung Rel-18 Revision of S2-2300414r05. Approved Agreed
9.18.1 S2-2300407 CR Approval 23.700-25 CR0002 (Rel-18, 'C'): TR 23.700 KI#1 conclusion update Nokia, Nokia Shanghai Bell, Qualcomm Rel-18 CC#4: r20 was agreed and was revised to S2-2301461 Shabnam (Ericsson) provides comments that we don't believe this conclusion addresses RAN2 concerns as well as potential security concerns with SIB usage, provide detailed revision of 0319 which is NOT Handled status.
Devaki (Nokia) provides r01 for S2-2300407.
zhendong (ZTE) provides r02.
Runze (Huawei) provides r03.
Devaki (Nokia) provides r04 (sorry I created r04 without knowing about r03, will need to provide another revision to merge the updates from r03).
Jari (NTT DOCOMO) comments
Sebastian (Qualcomm) replies to Huawei
Sebastian (Qualcomm) provides r06
Shabnam (Ericsson) provides comments with r05, sorry it seems we are completely out of sync with revision number. There was no r05 so I uploaded r05. Merger and a clean version will be needed with r06 from Qualcomm
Devaki (Nokia) provides r09 (without the TSCTSF subscription for impacted UE(s)) and r10 (without the TSCTSF subscription for impacted UE(s)), considering the open discussion still based on r03. Kindly ignore r07/r08.
Runze (Huawei) replies to Jari (NTT DOCOMO).
Runze (Huawei) replies to Sebastian (Qualcomm) and provides r11(based on r09).
Sang-Jun (Samsung) provides r12
Jari (NTT DOCOMO) responds to Runze
Sebastian (Qualcomm) has the same questions as raised by Jari
Sebastian (Qualcomm) provides r13
Jari (NTT DOCOMO) provides r14
Shabnam (Ericsson) provides comments r15
Sebastian (Qualcomm) is not ok with r15
==== Revisions Deadline ====
Shabnam (Ericsson) objects to any revision that removes clockclass, as explained in the thread 0322 LS out, which we need to approve together, we believe ITU-T response includes this as one parameter so we should get RAN feedback before ruling it out.
Shabnam (Ericsson) can only accept r15, objects to other revisions, also needs to be approved together with the LS out in revision of 0322.
Devaki (Nokia) comments.
Runze (Huawei) replies to Jari (NTT DOCOM).
Runze (Huawei) provides more justification to Jari (NTT DOCOM).
Runze (Huawei) replies to Sebastian (QC) and Jari (NTT DOCOMO).
Runze (Huawei)) replies to Jari (NTT DOCOMO), and propose to add texts on top of r17 ' the option 'RAN determined impacted UE' will be continue the discuss in the normative phase.' .
Devaki (Nokia) comments that the discussion is anyhow expected to continue during normative phase, it is ok for me to add 'the option to determine impacted UE by the RAN' will continue to be discussed during the normative phase.' as part of R17 if others are ok with it as well.
Runze (Huawei) replies the Devaki (Nokia).
Shabnam (Ericsson) provides comments that we understand the revision is what we discussed at the CC#3, not sure if the version has been uploaded by Devaki yet?
Sebastian (Qualcomm) has the same comment as Shabnam
Devaki (Nokia) provides r17 as discussed during CC#3 in CC3 folder.
==== Final Comments Deadline ====
Sebastian (Qualcomm) comments that 'PTP class' should read 'PTP clockClass' in NOTE Z
Devaki (Nokia) provides r18 with the editorial fix: updated to 'clockClass' (3 times).
Runze adds one sentence in r19, on top of r18.
Shabnam (Ericsson) we are adding now feasibility into normative work and who will do this work, since it is RAN determined, RAN? Then should that not be discussed in RAN as part of input to the LS?
Runze (Huawei) replies to Shabnam (Ericsson).
Revised
9.18.1 S2-2301461 CR Approval 23.700-25 CR0002R1 (Rel-18, 'C'): TR 23.700 KI#1 conclusion update Nokia, Nokia Shanghai Bell, Qualcomm, Huawei, ZTE, Samsung Rel-18 Revision of S2-2300407r20. Approved Agreed
9.18.1 - - - Documents exceeding TU budget - - Docs:=4 -
9.18.1 S2-2301110 CR Approval 23.700-25 CR0008 (Rel-18, 'F'): KI#1, update the conclusion for the KI#1 to resovle the ENs on providing the time sync status to UE. ZTE Rel-18 Not Handled Merge with S2-2300407 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.1 S2-2300947 CR Approval 23.700-25 CR0006 (Rel-18, 'C'): KI1 conclusion update Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.1 S2-2300782 CR Approval 23.700-25 CR0004 (Rel-18, 'B'): Conclusion for FS_5TRS_URLLC KI#6 Samsung Rel-18 Not Handled Merge with S2-2300414 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.1 S2-2300319 CR Approval 23.700-25 CR0001 (Rel-18, 'B'): KI #1: Update to address ENs Ericsson Rel-18 Not Handled Merge with S2-2300407 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 - - - 5G Timing Resiliency and TSC & URLLC enhancements (5TRS_URLLC) - - Docs:=59 -
9.18.2 - - - LSs - - Docs:=7 -
9.18.2 S2-2300011 LS In Action LS from ITU-T SG15: Reply to Liaison on Monitoring of network time synchronization and relevant parameters (reply to 3GPP TSG SA2-LS3) ITU-T SG15 (SG15-LS17) Revision of postponed S2-2210185 from S2#154. Postponed Postponed
9.18.2 S2-2300043 LS In Action LS from RAN WG2: LS response on 5GS time synchronization status report towards the UE(s) RAN WG2 (R2-2213048) Rel-18 Postponed Postponed
9.18.2 S2-2300044 LS In Action LS from RAN WG2: Reply LS on UL scenario of reactive RAN feedback for burst sending time adjustment RAN WG2 (R2-2213070) Rel-18 Response drafted in S2-2300304. Final response in S2-2301420 Replied to
9.18.2 S2-2300304 LS OUT Approval [DRAFT] LS Reply on UL scenario of Reactive RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Response to S2-2300044. r02 agreed. Revised to S2-2301420. zhendong (ZTE) provides comments.
Haiyang (Huawei) provides reply.
Devaki (Nokia) provides r01.
Sebastian (Qualcomm) provides r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301420 LS OUT Approval LS Reply on UL scenario of reactive RAN feedback for burst sending time adjustment SA WG2 Rel-18 Revision of S2-2300304r02. Approved Approved
9.18.2 S2-2300322 LS OUT Approval [DRAFT] LS on proposed method for Time Synchronization status reporting to UE(s) Ericsson Rel-18 CC#4: r07 agreed. Revised to S2-2301463. Devaki (Nokia) provides r01 for DRAFT LS out to RAN2 in 322.
Sebastian (Qualcomm) provides r02
Shabnam (Ericsson) provides r03
Sebastian (Qualcomm) provides r04
Devaki (Nokia) comments.
Devaki (Nokia) provides r05.
Sebastian (Qualcomm) replies
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments and that we see the LS Out and the CR in 0407 to be approved together.
Shabnam (Ericsson) provides comments that can't accept r05 or r04, r02, r01. Only accepts r03 or r05+adding back clockclass which was removed for the question to RAN3 but not from the parameters description.
Devaki (Nokia) provides r06 to re-instate clock class on top of r05 as an option.
Sebastian (Qualcomm) cannot accept adding back clockclass unless more explanation is added what this refers to and how this can work. PTP clockClass cannot be used because it is PTP specific. PTP clockClass values refer to 'holdover specification of the applicable PTP Profile' as per IEEE 1588 clause 7.6.2.5, which has no meaning if ASTI is used; PTP clockClass will also not work if gNB uses GNSS as time source, which is what many operators use
Sebastian (Qualcomm) provides r07
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301463 LS OUT Approval Proposed method for Time Synchronization status reporting to UE(s) SA WG2 Rel-18 Revision of S2-2300322r07. Approved Approved
9.18.2 - - - CRs - - Docs:=5 -
9.18.2 S2-2300408 CR Approval 23.501 CR3892 (Rel-18, 'B'): Support for network timing synchronization status and reporting KI1 - description Nokia, Nokia Shanghai Bell, NTT DOCOMO Rel-18 r05 agreed. Revised to S2-2301421, merging S2-2301111 Shabnam (Ericsson) provides comments with r01
Sebastian (Qualcomm) provides r02
Devaki (Nokia) provides r03.
Jari (NTT DOCOMO) provides r04.
zhendong (ZTE) provides r05.
Jari (NTT DOCOMO) responds to zhendong
zhendong (ZTE) provides response.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that r05 is ok as we ack that we need to do more work after we get RAN feedback, please add Ericsson as supporting company.
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301421 CR Approval 23.501 CR3892R1 (Rel-18, 'B'): Support for network timing synchronization status and reporting KI1 - description Nokia, Nokia Shanghai Bell, NTT DOCOMO, ZTE, Ericsson Rel-18 Revision of S2-2300408r05, merging S2-2301111. Approved Agreed
9.18.2 S2-2301111 CR Approval 23.501 CR4065 (Rel-18, 'B'): KI#1, Adding the timing synchronization status reporting ZTE Rel-18 Confirm Spec version used - CR states 18.X.0! Merged into S2-2301421 Jari (NTT DOCOMO) proposes to merge with S2-2300408
Sebastian (Qualcomm) also proposes to consider this merged
zhendong (ZTE) is fine to merge proposal.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.18.2 S2-2300831 CR Approval 23.502 CR3644R1 (Rel-18, 'B'): Reporting the RAN timing synchronization status change from AMF to TSCTSF NTT DOCOMO Rel-18 Revision of S2-2210739. Postponed zhendong (ZTE) proposes to postpone this CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2300829 CR Approval 23.501 CR3807R1 (Rel-18, 'B'): Reporting the RAN timing synchronization status change from AMF to TSCTSF NTT DOCOMO Rel-18 Revision of S2-2210714. Approved zhendong (ZTE) proposes to merge with S2-2300408.
Jari (NTT DOCOMO) proposes to keep separate, as there is no overlap with -408
zhendong (ZTE) is fine to keep seperate.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.18.2 - - - Key Issue #1 - - Docs:=5 -
9.18.2 S2-2301115 CR Approval 23.502 CR3841 (Rel-18, 'B'): Clarification on registration area impacted by the requeted or subscribed coverage area. ZTE Rel-18 Postponed Sang-Jun (Samsung) comments that the CR title should be corrected.
Jari (NTT DOCOMO) comments
Devaki (Nokia) comments.
zhendong (ZTE) provides response.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that we postpone this CR and others in KI#3 and come back with common approach next time in April. Objects to all revisions just for sake of chair
zhendong (ZTE) is fine to postpone this CR for further discussion.
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2300410 CR Approval 23.501 CR3893 (Rel-18, 'C'): Corrections for the description of coverage area support for time synchronization service KI2 Nokia, Nokia Shanghai Bell Rel-18 Postponed Jari (NTT DOCOMO) comments
Qianghua (Huawei) provides comments
Devaki (Nokia) comments.
Jari (NTT DOCOMO) provides r01
==== Revisions Deadline ====
Qianghua (Huawei) provides responses to Devaki
Devaki (Nokia) replies to Qianghu. Also, r01 from Jari is fine for me.
Shabnam (Ericsson) provides comments that we postpone this CR and others in KI#3 and come back with common approach next time in April. Objects to all revisions just for sake of chair
Devaki (Nokia) comments that this CR is not related to Registration area alignment rather it is related to TSCTSF subscribing to all AMFs vs serving AMF only thus I don't understand why this needs to be postponed.
Sebastian (Qualcomm) agrees with Devaki, this CR is not related to the RA discussion
Shabnam (Ericsson) provides comments wrong comment, but we still have issues with changing to UDM as we don't believe it is needed change and adding more load to UDM is not justified. We can consider having both options but we don't agree to remove NRF option.
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2300318 CR Approval 23.502 CR3703 (Rel-18, 'F'): Ensuring that a geographical area requested for a time sync service coincides with a RA Ericsson Rel-18 Postponed Jari (NTT DOCOMO) comments
zhendong (ZTE) provides.
Sebastian (Qualcomm) comments
Shabnam (Ericsson) provides comments and r01 using option 3B
Devaki (Nokia) comments
Zhenglei (China Mobile) comments
zhendong (ZTE) similar view with nokia. proposes to move with option 2 or 4.
Shabnam (Ericsson) provides r02 for option 4, this requires update to 1113 as well.
==== Revisions Deadline ====
Devaki (Nokia) is fine with r02 (objects to earlier versions).
Sebastian (Qualcomm) proposes to postpone; objects to all versions for the record
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2301113 CR Approval 23.501 CR4066 (Rel-18, 'F'): KI#2 clarification on the UE registration area and UDM check ZTE Rel-18 Postponed Jari (NTT DOCOMO) comments
Qianghua (Huawei) provides comments that this CR overlaps with 0779
Devaki (Nokia) provides r01. This CR can be used as the baseline and 779 can be merged with this as this also does the proper reference.
Shabnam (Ericsson) provides r02 aligned with Option 4
zhendong (ZTE) provides comments.
Jari (NT DOCOMO) comments
zhendong (ZTE) provides the comments.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments to come back to this topic as it has dependency with discussion on 0318 and offline we concluded to postpone that CR for further evaluation
Sebastian (Qualcomm) proposes to postpone as discussed offline; objects to all versions
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2300779 CR Approval 23.501 CR3980 (Rel-18, 'F'): Registration Area management for time synchronization service China Mobile Rel-18 Postponed To be merged into S2-2301113 (Postponed) Jari (NTT DOCOMO) provides r01
Zhenglei (China Mobile) is fine to merge 0779 with 1113 if we use Option 2 as the way forward.
zhendong (ZTE) proposes this CR merged with 1113.
zhendong (ZTE) provides response.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.18.2 - - - Key Issue #2 - - Docs:=10 -
9.18.2 S2-2301198 CR Approval 23.501 CR4089 (Rel-18, 'F'): Charification for Controlling time synchronization service based on the Subscription Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301422. Jari (NTT DOCOMO) proposes to note
Qianghua (Huawei) provides responses to Jari and asks how to use error budget set in UDM?
Jari (NTT DOCOMO) responds
Qianghua (Huawei) provides r01, clarify 'Uu time synchronization error budge' in UE subscription and the AF request error budge are mutually exclusive
Sebastian (Qualcomm) has concerns
Qianghua (Huawei) replies to Sebastain concerns
Devaki (Nokia) comments.
zhendong (ZTE) similar comments with qualcomm and nokia.
Qianghua (Huawei) provides r02
Sebastian (Qualcomm) comments
Jari (NTT DOCOMO) provides r03
==== Revisions Deadline ====
Sebastian (Qualcomm) is ok with r03, objects to other versions
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301422 CR Approval 23.501 CR4089R1 (Rel-18, 'F'): Charification for Controlling time synchronization service based on the Subscription Huawei, HiSilicon Rel-18 Revision of S2-2301198r03. Approved Agreed
9.18.2 S2-2300413 CR Approval 23.502 CR3716 (Rel-18, 'F'): Corrections to time synchronization based on subscription KI3 Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2301423. Jari (NTT DOCOMO) comments
Sebastian (Qualcomm) raises concerns on the CR
Devaki (Nokia) provides r03 to resolve the concerns raised. Please ignore r01/r02 (which I created prior to reading all the comments).
zhendong (ZTE) provides the comments.
Devaki (Nokia) provides r04.
==== Revisions Deadline ====
Devaki (Nokia) comments
Jari (NTT DOCOMO) objects
Sebastian (Qualcomm) objects to the CR; can be ok with r04 with 'AMF should use the highest received value' replaced by 'AMF uses the value from the AM policy'
zhendong (ZTE) provides comemnts.
Sebastian (Qualcomm) replies to Zhendong (ZTE)
Jari (NTT DOCOMO) can agree r04 with 'AMF should use the highest received value' replaced by 'AMF uses the value from the AM policy'
Devaki (Nokia) is ok with r04 with 'AMF should use the highest received value' replaced by 'AMF uses the value received from the AM policy'
zhendong (ZTE) provides response to devaki.
Devaki (Nokia) replies
zhendong (ZTE) provides response to nokia.
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301423 CR Approval 23.502 CR3716R1 (Rel-18, 'F'): Corrections to time synchronization based on subscription KI3 Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300413r04. Approved Agreed
9.18.2 S2-2301199 CR Approval 23.502 CR3856 (Rel-18, 'F'): Charification for Controlling time synchronization service based on the Subscription Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2301424. Sang-Jun (Samsung) comments that the CR title and coversheet should be corrected.
Jari (NTT DOCOMO) proposes to note
Qianghua (Huawei) provides r01
Sebastian (Qualcomm) provides r02
Devaki (Nokia) provides r03.
zhendong (ZTE) ask question for clarification.
Qianghua (Huawei) replies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301424 CR Approval 23.502 CR3856R1 (Rel-18, 'F'): Charification for Controlling time synchronization service based on the Subscription Huawei, HiSilicon Rel-18 Revision of S2-2301199r03. Approved Agreed
9.18.2 S2-2300780 CR Approval 23.501 CR3981 (Rel-18, 'F'): Update for controlling time synchronization service based on Subscription China Mobile Rel-18 r04 agreed. Revised to S2-2301425. Jari (NTT DOCOMO) provides r01
Zhenglei (China Mobile) is fine with r01 and provides revision of 23.502 CR
Zhenglei (China Mobile) provides r02 of S2-2300781 and proposes to move S2-2300781 to KI#3
Devaki (Nokia) provides r03.
Zhenglei (China Mobile) clarified it should be r02 and fine with r02
zhendong (ZTE) provides comments.
Zhenglei (China Mobile) replies comments from Zhendong and provides r03
Jari (NTT DOCOMO) provides r04.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301425 CR Approval 23.501 CR3981R1 (Rel-18, 'F'): Update for controlling time synchronization service based on Subscription China Mobile Rel-18 Revision of S2-2300780r04. Approved Agreed
9.18.2 S2-2301114 CR Approval 23.501 CR4067 (Rel-18, 'F'): KI#3, resolve EN on the the subscribed covrage area ZTE Rel-18 Postponed Sang-Jun (Samsung) comments that the CR title should be corrected.
Jari (NTT DOCOMO) comments
zhendong (ZTE) provides response.
Qianghua (Huawei) provides comments that this CR overlaps with 0779
Devaki (Nokia) provides r01 (supports as we had a similar CR in 412 (not handled) to remove the EN) with minor edits proposal.
zhendong (ZTE) provides r02.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that we need to work on this further since the CR cover sheet does not explain how the EN was resolved, objects to all revisions.
==== Final Comments Deadline ====
Postponed
9.18.2 S2-2300951 CR Approval 23.501 CR4023 (Rel-18, 'B'): Adding UE subscription data related to time synchronization service Huawei, HiSilicon Rel-18 Postponed Sang-Jun (Samsung) supports the CR and provides r01 with a small correction and Samsung co-sign.
Jari (NTT DOCOMO) comments
Runze (Huawei) thanks Sang-Jun (Samsung) and supports r01.
Runze (Huawei) replies to Jari (NTT DOCOMO) and provides r02.
zhendong (ZTE) provides comments.
==== Revisions Deadline ====
Devaki (Nokia) comments that CR shall be aligned with the parallel conclusion update in 948r02, thus objects to the revisions. As of r03, the proposed NOTE is misleading, kindly produce a revision to copy paste the text from 948r02 to this CR (objects to r03 as it is not aligned with 948r02).
Shabnam (Ericsson) provides comments that r03 is not acceptable, the NOTE text is not accurate and has normative 'should', then the proposal in this CR is introducing a few function where SLA bypasses the subscription. I believe this was not something we agreed in study, we need more time for this before agreeing as normative text in other revisions. So object to this document in all revisions.
Jari (NTT DOCOMO) can agree r03. Objects all other revisions and r00
==== Final Comments Deadline ====
Runze (Huawei) provides r04 and suggest to approve this version in CC#4.
Postponed
9.18.2 - - - Key Issue #3 - - Docs:=4 -
9.18.2 S2-2300302 CR Approval 23.501 CR3870 (Rel-18, 'B'): Removing ENs for TSN TN intergation Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2301426. Sang-Jun (Samsung) comments that the CR title should be corrected.
Haiyang (Huawei) provides r01.
Jari (NTT DOCOMO) provides r02.
Haiyang (Huawei) provides r03.
Devaki (Nokia) provides r03 with some comments and updates, also propose to leave some ENs open, rationale present inline.
Haiyang (Huawei) provides r06.
==== Revisions Deadline ====
Haiyang (Huawei) prefers r03, can live with r06, objects to other versions just in case.
Devaki (Nokia) prefers r05 (objects to other versions) as MaxLatency remains unsolved also in r06, comments inline. In the earlier email announcement, I missed announcing r05 that I provided.
Haiyang (Huawei) comments and suggests to go with r07: r06 +'remove UPF Residence Time'
Devaki (Nokia) comments that we can live with r07.
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301426 CR Approval 23.501 CR3870R1 (Rel-18, 'B'): Removing ENs for TSN TN integration Huawei, HiSilicon, NTT DOCOMO, Samsung Rel-18 Revision of S2-2300302r06. Approved Agreed
9.18.2 S2-2300303 CR Approval 23.501 CR3871 (Rel-18, 'F'): Clarification on for TSN TN intergation Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301427. Sang-Jun (Samsung) comments that the CR title should be corrected.
Haiyang (Huawei) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301427 CR Approval 23.501 CR3871R1 (Rel-18, 'F'): Clarification on for TSN TN integration Huawei, HiSilicon, Samsung Rel-18 Revision of S2-2300303r01. Approved Agreed
9.18.2 - - - Key Issue #5 - - Docs:=16 -
9.18.2 S2-2301196 CR Approval 23.501 CR4088 (Rel-18, 'B'): Charify on periodicity adaption on Proactive feedback Huawei, HiSilicon Rel-18 r07 agreed. Revised to S2-2301428, merging S2-2300754 and S2-2300906 Sang-Jun (Samsung) comments that the CR title and coversheet should be corrected.
Devaki (Nokia) provides r01 (merges also 415 content to this CR as Haiyang proposed to consider this as the baseline).
Sang-Jun (Samsung) provides r02 and confirms 0754 is also merged.
Devaki (Nokia) supports based on the merge as well, provides r03.
Qianghua (Huawei) provides r04 keeping the indication for periodicity adaptation, as well as r05 removing the indication for periodicity adaptation,
Yuan Tao (CATT) merges S2-2300906 into this paper per rapporteur's suggestion, and provides r06 and r07 based on r04, r05 respectively.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301428 CR Approval 23.501 CR4088R1 (Rel-18, 'B'): Clarify on periodicity adaption on Proactive feedback Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung Rel-18 Revision of S2-2301196r07, merging S2-2300754 and S2-2300906. Approved Agreed
9.18.2 S2-2300754 CR Approval 23.501 CR3977 (Rel-18, 'B'): RAN feedback for burst sending time and periodicity adjustment Samsung Rel-18 Merged into S2-2301428 Haiyang (Huawei) suggests to merge this paper into S2-2301196
Sang-Jun (Samgung) agrees to merge 0754 into 1196.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.18.2 S2-2300906 CR Approval 23.501 CR4015 (Rel-18, 'B'): RAN feedback for Burst Arrival Time offset CATT Rel-18 Merged into S2-2301428 Devaki (Nokia) proposes to consider this merged with 305 (for UL related updates to clause 5.27.2.5.2) and with 1196 and its revisions (for periodicity feedback).
Yuan Tao (CATT) asks Devaki (Nokia) for clarification about merging.
Devaki (Nokia) replies.
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
==== Revisions Deadline ====
Yuan Tao (CATT) confirms this CR is merged into 2301196.
==== Final Comments Deadline ====
Merged
9.18.2 S2-2300757 CR Approval 23.502 CR3787 (Rel-18, 'B'): RAN feedback for burst sending time and periodicity adjustment Samsung Rel-18 Merged into S2-2301432 Sang-Jun (Samsung) agrees to merge this paper into S2-2300416
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.18.2 S2-2300769 CR Approval 23.503 CR0853 (Rel-18, 'B'): RAN feedback for burst sending time and periodicity adjustment Samsung Rel-18 r02 agreed. Revised to S2-2301429. Haiyang (Huawei) suggests to use this paper as basis for 503 on periodicity adjustment
Sang-Jun (Samsung) provides r01 merging 0420.
Qianghua (Huawei) provides r02
Sang-Jun (Samsung) provides r03
Qianghua (Huawei) explains the concerns by using a new para to describe periodicity aspects.
==== Revisions Deadline ====
Qianghua (Huawei) can only accept r02 given the explanations below (object other revisions for mark)
Sang-Jun (Samsung) can accept r02 and r03, but r02 is related with 414 r05, 1196 r07, 416 r03. However 416 r03 has obejction. So r03 needs to be accepted if 416 r03 is not accepted.
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301429 CR Approval 23.503 CR0853R1 (Rel-18, 'B'): RAN feedback for burst sending time and periodicity adjustment Samsung, Nokia, Nokia Shanghai Bell, Huawei Rel-18 Revision of S2-2300769r02. Approved Agreed
9.18.2 S2-2300781 CR Approval 23.502 CR3788 (Rel-18, 'F'): Update for controlling time synchronization service based on Subscription China Mobile Rel-18 r04 agreed. Revised to S2-2301430. Zhenglei (China Mobile) provides r02 of S2-2300781 and proposes to move S2-2300781 to KI#3
Devaki (Nokia) provides r03.
Zhenglei (China Mobile) provides r02 and proposes to move S2-2300781 to KI#3
Devaki (Nokia) provides r03 - remove reporting of subscribed coverage to the AF (not present in conclusion).
Zhenglei (China Mobile) is fine with r03
Sebastian (Qualcomm) provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301430 CR Approval 23.502 CR3788R1 (Rel-18, 'F'): Update for controlling time synchronization service based on Subscription China Mobile Rel-18 Revision of S2-2300781r04. Approved Agreed
9.18.2 S2-2300415 CR Approval 23.501 CR3895 (Rel-18, 'C'): The support for Periodicity feedback in Enablers for Time Sensitive Communications and Time Synchronization feature KI6. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2301431. Haiyang (Huawei) proposes to move the periodicity part into S2-2301196
Qianghua (Huawei) provides r01
Sebastian (Qualcomm) provides r02
==== Revisions Deadline ====
Sebastian (Qualcomm) objects to all revisions; can only accept r02 if the changes to the 'Reactive RAN feedback' clause are removed
Devaki (Nokia) comments r02 minus changes to 'Reactive RAN feedback' clause is fine for me. I uploaded this as r03 in CC#4 folder for reference
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301431 CR Approval 23.501 CR3895R1 (Rel-18, 'C'): The support for Periodicity feedback in Enablers for Time Sensitive Communications and Time Synchronization feature KI6. Nokia, Nokia Shanghai Bell, Huawei Rel-18 Revision of S2-2300415r02. Approved Agreed
9.18.2 S2-2300416 CR Approval 23.502 CR3717 (Rel-18, 'C'): RAN feedback for periodicity adjustment KI6 Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2301432, merging S2-2300757 Haiyang (Huawei) suggests to use this paper as basis for 502 on periodicity adjustment
Sang-Jun (Samsung) agrees to use this paper as basis for 502 on periodicity adjustment and provides r01
Qianghua (Huawei) provides r02 keeping the indication for periodicity adaptation, as well as r03 removing the indication for periodicity adaptation,
==== Revisions Deadline ====
Devaki (Nokia) comments r03 removes periodicity (sent to RAN) completely erroneously while Haiyang just proposed to removed the capability indication, retain periodicity range signaled to RAN as in HUA paper as well thus only r02 can be approved.
Qianghua (Huawei) asks further on Devaki comments about r03, and asks Devaki to check again on r03
Qianghua (Huawei) provides responses and proposes to go with r03 to keep aligning with the conclusion paper
Qianghua (Huawei) proposes to confirm r03 at CC#4, for safe, object r00, r01, r02
Devaki (Nokia) comments r03 is ok.
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301432 CR Approval 23.502 CR3717R1 (Rel-18, 'C'): RAN feedback for periodicity adjustment KI6 Nokia, Nokia Shanghai Bell, Samsung, Huawei Rel-18 Revision of S2-2300416r03, merging S2-2300757. Approved Agreed
9.18.2 S2-2300420 CR Approval 23.503 CR0829 (Rel-18, 'B'): Corrections for the description of coverage area support for time synchronization service KI6 Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2301433. Devaki (Nokia) proposes to keep this CR separate as this CR updates more sections while 769 updates just a single section (overlapping third change can be removed from this CR, otherwise, it requires significant effort to do the merge, not worth the effort at this time), provides r01.
Qianghua (Huawei) provides r02
György (Ericsson) prefers r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.18.2 S2-2301433 CR Approval 23.503 CR0829R1 (Rel-18, 'B'): Corrections for the description of coverage area support for time synchronization service KI6 Nokia, Nokia Shanghai Bell, Huawei, Samsung Rel-18 Revision of S2-2300420r02. Approved Agreed
9.18.2 S2-2300305 CR Approval 23.501 CR3872 (Rel-18, 'B'): Removing EN on UL scenario of Reactive RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.18.2 - - - Key Issue #6 - - Docs:=12 -
9.18.2 S2-2301197 CR Approval 23.502 CR3855 (Rel-18, 'B'): RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2301112 CR Approval 23.502 CR3840 (Rel-18, 'B'): KI#1, Adding the timing synchronization status reporting ZTE Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300950 CR Approval 23.502 CR3820 (Rel-18, 'B'): Adding 5GS network timing synchronization status reporting Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300952 CR Approval 23.502 CR3821 (Rel-18, 'B'): Adding UE subscription data related to time synchronization service Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300907 CR Approval 23.503 CR0867 (Rel-18, 'B'): RAN feedback for Burst Arrival Time offset CATT Rel-18 Not Handled Kefeng Zhang(Qualcomm) provides comment that one PDU session may serve one or more PIN.
Jianning (Xiaomi) provide comment
Jicheol (Samsung) asks a question for clarifiction to Jianning (Xiaomi).
Jianning (Xiaomi) replise to Jicheol (Samsung)
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300949 CR Approval 23.501 CR4022 (Rel-18, 'B'): Adding 5GS network timing synchronization status reporting Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300306 CR Approval 23.502 CR3700 (Rel-18, 'B'): Proactive RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300316 CR Approval 23.501 CR3874 (Rel-18, 'B'): Reporting timing synchronization status Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300317 CR Approval 23.502 CR3702 (Rel-18, 'B'): AF confirming TSCTSF s intention to deactivate the time sync service Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300412 CR Approval 23.501 CR3894 (Rel-18, 'F'): Registration Area management in presence of Time Synchronization Coverage Area KI3 Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300411 CR Approval 23.502 CR3715 (Rel-18, 'C'): Corrections for the procedures to support coverage area for time synchronization service KI2 Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 S2-2300409 CR Approval 23.502 CR3714 (Rel-18, 'B'): Support for network timing synchronization status and reporting - procedures Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.18.2 - - - Documents exceeding TU budget - - Docs:=0 -
9.19.1 - - - Study on Vehicle Mounted Relays (FS_VMR) - - Docs:=0 -
9.19.2 - - - Vehicle Mounted Relays (FS_VMR) - - Docs:=36 -
9.19.2 S2-2301282 CR Approval 23.501 CR4103 (Rel-18, 'B'): MBSR authorization update Intel Rel-18 r06 agreed. Revised to S2-2301451. Qian (Ericsson) provides comments and r01
Xiaoyan Shi (Intel) provides comments on r01 and provide r02
Lars (Sony) comment
Alessio(Nokia) provides R03
Qian (Ericsson) comments on r03
Lalith (Samsung) comments
Xiaoyan Shi (Intel) comments that 'not allowed to operate as MBSR' shall be addressed in 1015. So let us continue discussion based on r02.
Hong (Qualcomm) comments.
LiMeng (Huawei) provides r04.
Xiaoyan Shi (Intel) provides r05.
Qian (Ericsson) provides comments and r06
alessio(nokia) provides r07
Xiaoyan Shi (Intel) prefers to go with r06
Alessio(Nokia) prefers r07 and has concerns with other revisions
Xiaoyan Shi(Intel) objects r07 before receiving clear reply on when 'TS already includes sending in NAS that the MBSR behaviour is not allowed'.
==== Revisions Deadline ====
Qian (Ericsson) shares the same view as Xiaoyan (Intel) and object to r07.
LiMeng (Huawei) objects to r07, there is no need to send the MBSR authorized indication to UE.
Alessio(Nokia) asks not Xiaoyan to allow r07 since we have provided the required info
alessio (nokia) provides evidence to the comment by Xiaoyan
alessio(Nokia) believes the current spec is clear the not allowed is send to the MBSR in registration procedure. we just add the ALLOWED so the MBSR know is it allowed also
alessio(Nokia) if companies prefer we can postpone this. to us it is a no brainer to add the support indication to MBSR as we already send no support be can only accept r07
alessio(Nokia) is ok to technically endorse this as basis of further work.
Xiaoyan Shi (Intel) kindly reminds Alessio that the provided info is disused in 1015 and there is corresponding EN, and this contribution didn't touch this part. Please don't hijack a contribution by a irrelevant topic.
Xiaoyan Shi (Intel) replies.
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301451 CR Approval 23.501 CR4103R1 (Rel-18, 'B'): MBSR authorization update Intel, Ericsson Rel-18 Revision of S2-2301282r06. Technically Endorsed Endorsed
9.19.2 S2-2301295 CR Approval 23.501 CR4107 (Rel-18, 'C'): UE mobility when moving together with a MBSR cell Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2301828. LiMeng (Huawei) comments
Xiaoyan Shi (Intel) comments
Hong (Qualcomm) provides r01.
Alessio(Nokia) provides r02.
LiMeng (Huawei) provides r04.
Alessio(nokia) can live with r04
==== Revisions Deadline ====
Qian (Ericsson) is ok with r04
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301828 CR Approval 23.501 CR4107R1 (Rel-18, 'C'): UE mobility when moving together with a MBSR cell Qualcomm Incorporated Rel-18 Revision of S2-2301295r04. Approved Agreed
9.19.2 S2-2301161 CR Approval 23.273 CR0288 (Rel-18, 'B'): MT-LR procedure for when a MBSR is involved in the location of a UE. Sony Rel-18 CC#4: r07 + editor's note agreed. Revised to S2-2301478. LiMeng (Huawei) comments.
Qian (Ericsson) provides comments.
Lars (Sony) responds to LiMeng and Qian.
Lars (Sony) Merging 802 and 803 content and provides r01
Alessio(Nokia) provides R02 which we support
alessio(Nokia) agrees with Sonly answers.
Hong (Qualcomm) provides r03.
Lars (Sony) provides r04.
LiMeng (Huawei) provides r05.
Lars (Sony) provides r06
Hong (Qualcomm) comments on r04.
Lars (Sony) responds to Hong.
Hong (Qualcomm) provides r07.
alessio(nokia) provides r08.
==== Revisions Deadline ====
LiMeng (Huawei) objects to r08.
Qian (Ericsson) provides comments and prefers r07.
Lars (Sony) is ok with r07.
alessio(Nokia) comments and cannot accept r07 with the editor's note and can only accept r08
LiMeng (Huawei) disagrees with the comments from Alessio, cannot accept r08.
Lars (Sony) ask if EN can be updated.
LiMeng (Huawei) can only accept r05-r07, objects to any other revisions including r00.
Hong (Qualcomm) objects r0 to r06.
Lars (Sony) ask to be brought up in CC#4.
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301478 CR Approval 23.273 CR0288R1 (Rel-18, 'B'): MT-LR procedure for when a MBSR is involved in the location of a UE. Sony, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301161r07 + editor's note. Approved Agreed
9.19.2 S2-2301284 CR Approval 23.502 CR3866 (Rel-18, 'B'): CAG enhancement for UE access control via MBSR Intel Rel-18 r02 agreed. Revised to S2-2301829. Use as the basis for CAG control procedures. May need to be discussed w/ eNPN_Ph2 (9.24.2) papers. Qian (Ericsson) provides comments and r01
Hong (Qualcomm) comments on r01.
Xiaoyan Shi (intel) thanks Qian's r01 and reply.
LiMeng (Huawei) comments on r01.
Qian (Ericsson) provides some comments.
Josep (DT) answers Hong (Qualcomm). Comments on r01
Xiaoyan Shi (Intel) provides r02.
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) replies to Hong.
LiMeng (Huawei) comments to r02.
Xiaoyan Shi (Intel) replies to Limeng.
==== Revisions Deadline ====
LiMeng (Huawei) replies to Xiaoyan (Intel).
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301829 CR Approval 23.502 CR3866R1 (Rel-18, 'B'): CAG enhancement for UE access control via MBSR Intel Rel-18 Revision of S2-2301284r02. Approved Agreed
9.19.2 S2-2301297 CR Approval 23.501 CR4108 (Rel-18, 'B'): Configuraiton of the MBSR node Qualcomm Incorporated Rel-18 r10 agreed. Revised to S2-2301452. LiMeng (Huawei) comments.
Qian (Ericsson) provides comments.
Qian (Ericsson) provides r01 considering the content from 0223.
Xiaoyan Shi (Intel) share same view with Huawei and Ericsson and comments on r01.
Hong (Qualcomm) provide r02.
LiMeng (Huawei) comments to r02.
Alessio(Nokia) provides R03
Lars (Sony) provides r04.
Qian (Ericsson) comments and provides r05.
LiMeng (Huawei) provides r06.
Hong (Qualcomm) provides r07.
Alessio(nokia) provides r08.
Hong (Qualcomm) is fine with r08.
Qian (Ericsson) comments and provides r09.
Hong (Qualcomm) provides r10.
Alessio(nokia) provides r11 with all the necessary details
==== Revisions Deadline ====
LiMeng (Huawei) prefers r09, can live with r10 and comments to r11
Qian (Ericsson) prefers r09, can live with r10 and objects to r11
alessio(Nokia) explains that this is a MBSR not a IAB node. IAB nodes can be PRECONFIGURED with the PDU session info here we can allow a non configured UE that indicates to be MBSR to receive the necessary PDU session at bootstrap using what described in r11. not sure why R11 is not good. it is also clarified that the OAM connection is established only if the MBSR is allowed to operate as MBSR.
Hong (Qualcomm) prefers r10.
Alessio(Nokia) can compromise by updating r10 with the changes in the draft folder which now make the text read ' The serving PLMN provides an Allowed NSSAI and establishes the PDU session for the OAM server access, considering the S-NSSAI and DNN requested by MBSR and/or the default values in subscription data'
.
Hong (Qualcomm) is fine with the change proposed by Alessio. Suggests handling this in CC#4.
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301452 CR Approval 23.501 CR4108R1 (Rel-18, 'B'): Configuration of the MBSR node Qualcomm Incorporated Rel-18 Revision of S2-2301297r10. Approved Agreed
9.19.2 S2-2301298 CR Approval 23.503 CR0892 (Rel-18, 'B'): Definition of MBSR Policy Qualcomm Incorporated Rel-18 Postponed LiMeng (Huawei) comments.
Qian (Ericsson) provides comments and consider new specific container is not needed
Hong (Qualcomm) replies to Qian.
Alessio(Nokia) suggest to postpone this CR to gain a better understanding of what Ue policies exactly we need to configure. we can then have this cr submitted with updates at next meeting
==== Revisions Deadline ====
Qian (Ericsson) postpone this paper.
Hong (Qualcomm) is fine to postpone.
==== Final Comments Deadline ====
Postponed
9.19.2 S2-2301010 CR Approval 23.501 CR4039 (Rel-18, 'F'): Resolving EN on emergency services. Samsung Rel-18 r05 agreed. Revised to S2-2301830. LiMeng (Huawei) comments
Lalith(Samsung) comments
LiMeng (Huawei) prefers to not have the 'delayed' option
Qian (Ericsson) asks questions
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) comments.
Hong (Qualcomm) replies to Xiaoyan.
alessio(Nokia) provides R01
Lalith(Samsung) provides r02
Alessio(Nokia) if this is a note what is the value? seem like a potential action that may or may not happen...if so should we note the paper (that anyhow no longer addresses emergency?)
Xiaoyan Shi (Intel) comments on r02
Lalith(Samsung) provides r03
LiMeng (Huawei) provides r04
Lalith (Samsung) is OK with r04
Qian (Ericsson) provides comments and r05
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301830 CR Approval 23.501 CR4039R1 (Rel-18, 'F'): Resolving EN on emergency services. Samsung Rel-18 Revision of S2-2301010r05. Approved Agreed
9.19.2 S2-2301018 DISCUSSION Discussion Discussion on not allowed to act as MBSR handling. Samsung Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.19.2 S2-2301015 CR Approval 23.501 CR4040 (Rel-18, 'F'): Not allowed to act as MBSR handling Samsung Rel-18 r02 agreed. Revised to S2-2301831. LiMeng (Huawei) comments and considers the registration accept have some issues.
Lalith(Samsung) replies to LiMeng (Huawei)
Lars (Sony) Ask a question
LiMeng (Huawei) responds to Lars and Lalith.
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) comments.
LiMeng (Huawei) responds.
Qian (Ericsson) comments.
alessio(Nokia) proposes to note this paper and consider the text in S2-2301283r03 for discussion of this aspect.
Lalith(Samsung) comments
Lalith(Samsung) indicate 1283 and 1015 are handling two different topics.
Xiaoyan Shi (Intel) share same view with Hong and Lalith about keeping both 1015 and 1282 for different topic.
LiMeng (Huawei) provides r01.
Lalith(Samsung) seeks clarification from LiMeng (Huawei)
LiMeng (Huawei) responds to Lalith (Samsung)
Lalith (Samsung) responds to LiMeng (Huawei)
Alessio(Nokia) provides r02
Lalith(Samsung) is OK with r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Qian (Ericsson) indicates following changes on tope r02
Remove '(or UE configuration update if needed to update the authorization information)' on top of r02 + add 'Editor's Note: Whether and how (e.g. UCU or deregistration with re-registration) MBSR is informed when change in MBSR subscription is FFS.'
Revised
9.19.2 S2-2301831 CR Approval 23.501 CR4040R1 (Rel-18, 'F'): Not allowed to act as MBSR handling Samsung Rel-18 Revision of S2-2301015r02. Approved Agreed
9.19.2 S2-2300226 CR Approval 23.502 CR3686 (Rel-18, 'B'): Mobile IAB authorization and UE CAG updates Ericsson Rel-18 Postponed Josep (DT) comments, provides r01.
Lalith(Samsung) comments
Qian (Ericsson) comments and provides r02
Xiaoyan Shi (Intel) comments on r02
Qian (Ericsson) provides comments
alessio(Nokia) asks whether this will be merged in 1284 or what is the handling? we cannot go with both papers. if it refocuses on authorization I think it is best to take this discussion after we clarify the 501 aspects and we come back at next meeting (also because it is unusual to change CR title as it may need a new number ?? )
Xiaoyan Shi (Intel) comments and provides r03
LiMeng (Huawei) asks for clarification.
Qian (Ericsson) comments and provides r04.
Alessio(nokia) prefers to postpone this CR as the full picture on authorization and 1015 is not there yet.
Qian (Ericsson) comments that this paper has no direct relation with 1015.
==== Revisions Deadline ====
Xiaoyan Shi (Intel) believes this CR is independent from 1015 and r04 is fine with Intel.
LiMeng (Huawei) asks question on term alignment.
Qian (Ericsson) responds to Limeng(Huawei).
alessio(Nokia) agrees we do the work stepwise but then first we see the agreed 23.501 applicable CR(S) then we see what we do for 502. no need to overload MCC with implementing many CRs for same topic. we ask to postpone
Qian (Ericsson) indicates that this CR is in link with 1282
Qian (Ericsson) emphasise that this paper goes hand in hand with 1282. If the final fate of the 1282 is endorsement, this one can be endorsed as well
==== Final Comments Deadline ====
Postponed
9.19.2 S2-2300242 CR Approval 23.502 CR3688 (Rel-18, 'B'): MBSR Location Reporting to update Warning Area List for PWS Rakuten Mobile Rel-18 r02 agreed. Revised to S2-2301832. LiMeng (Huawei) asks for clarification
Aoken (Rakuten Mobile) responds to LiMeng (Huawei) and provides r01
Qian (Ericsson) asks further question on r01
Hong (Qualcomm) comments on r01.
Aoken (Rakuten Mobile) answers to the question Qian (Ericsson)
Aoken(Rakuten Mobile) responds to Hong (Qualcomm).
Aoken(Rakuten Mobile) provides r02
Xiaoyan Shi (Intel) asks question for clarification.
Aoken(Rakuten Mobile) responds to Xiaoyan Shi (Intel).
==== Revisions Deadline ====
Qian (Ericsson) comments.
Aoken answers to Qian (Ericsson)'s comments.
Qian (Ericsson) provides further comments.
Aoken(Rakuten Mobile) responds to Qian (Ericsson).
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301832 CR Approval 23.502 CR3688R1 (Rel-18, 'B'): MBSR Location Reporting to update Warning Area List for PWS Rakuten Mobile Rel-18 Revision of S2-2300242r02. Approved Agreed
9.19.2 S2-2300561 CR Approval 23.501 CR3933 (Rel-18, 'B'): Providing cell ID/TAC of MBSR for services LG Electronics Rel-18 r05 agreed. Revised to S2-2301833. Qian (Ericsson) provides comments
Xiaoyan Shi (Intel) comments
Hongsuk (LGE) provides r01
Lars (Sony) comments and suggest rewording
Hongsuk (LGE) provides r02
Alessio(nokia) provides r03
LiMeng (Huawei) comments r03
Alessio(nokia) provides r04
Hong (Qualcomm) comments on r04.
Xiaoyan Shi (Intel) comments on r04.
Hongsuk (LGE) provides r05 and proposes to merge this CR into S2-2301295.
LiMeng (Huawei) support to postpone this document if the changes overlap with S2-2301295.
Hongsuk (LGE) is ok to postpone this document.
Alessio(Nokia) proposes to use r05 as it removes a reference to TR and the text is not incorrect
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.19.2 S2-2301833 CR Approval 23.501 CR3933R1 (Rel-18, 'B'): Providing cell ID/TAC of MBSR for services LG Electronics Rel-18 Revision of S2-2300561r05. Approved Agreed
9.19.2 S2-2300225 CR Approval 23.501 CR3853 (Rel-18, 'F'): CAG support for mobile IAB update Ericsson Rel-18 Postponed To be merged into S2-2301294 (Postponed) Hong (Qualcomm) comments and proposes to handle this together with eNPN_Ph2 (9.24.2) contribution S2-2301294 and S2-2301229 .
Hong (Qualcomm) proposes to merge this CR into S2-2301294.
Qian (Ericsson) provides comments.
Alessio (nokia) ok with proposal by Hong (Qualcomm) to merge this CR into S2-2301294.
==== Revisions Deadline ====
Qian (Ericsson) confirms that this CR is merged into S2-2301294.
==== Final Comments Deadline ====
Postponed
9.19.2 S2-2300585 CR Approval 23.273 CR0268 (Rel-18, 'B'): Update location service involving Mobile Base Station Relay Huawei, HiSilicon Rel-18 Noted Qian (Ericsson) provides comments
LiMeng (Huawei) responds to Qian (Ericsson)
Lars (Sony) ask a question
Hong (Qualcomm) comments.
LiMeng (Huawei) replies to Hong (Qualcomm) and Lars (Sony).
LiMeng (Huawei) provides r01.
Lars (Sony) Ask a further question.
Alessio(Nokia) proposes to proceed with Sony's paper at this meeting as updated in 1161r01. there are some key FFs in this paper like how to obtain the UE ID of the MBSR that shall not Be FFS before we can agree on this. we can note this.
==== Revisions Deadline ====
Lars (Sony) Object to all versions.
==== Final Comments Deadline ====
Noted
9.19.2 S2-2300584 DISCUSSION Discussion Discussion and proposal on NRPPa procedure for MBSR location determination. Huawei, HiSilicon Rel-18 Noted Alessio(Nokia) comments
LiMeng (Huawei) replies to Alessio (Nokia)
Alessio (Nokia) replies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.19.2 S2-2300582 DISCUSSION Discussion Discussion on how to handle MBSR in case MBSR authorization fails. Huawei, HiSilicon Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.19.2 S2-2300222 CR Approval 23.501 CR3850 (Rel-18, 'F'): Update for the support of mobile IAB Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.19.2 S2-2301321 LS OUT Approval [DRAFT] LS on secured and trusted access to the serving PLMN OAM server by a MBSR Nokia Rel-18 Created at CC#1. CC#4: r09 agreed. Revised to S2-2301465. Alessio(Nokia) provides the based version r00 of the outgoing LS
LaeYoung (LGE) comments.
Alessio(nokia) provides r01 which addresses LaeYoung (LGE) comments whom he thanks.
Lars (Sony) comments.
LiMeng (Huawei) comments r01.
Qian (Huawei) comments and provide r02.
Alessio (Nokia) cannot agree to r02
alessio (nokia) replies to limeng and provides r03
Hong (Qualcomm) comments.
Qian (Ericsson) comments and provides r04.
Hong (Qualcomm) is fine with r04.
LiMeng (Huawei) provides r05.
Alessio provides r06.
==== Revisions Deadline ====
Qian (Ericsson) is ok with r05, r04, r02 and objects to all other revisions.
LiMeng (Huawei) can accept r05 and r06 only, object to other versions due to the issue of neutral wording.
Walter Dees (Philips) comments on CR number
Qian (Ericsson) comments the CR number for attached 23.501 CR shall be updated to '4108'.
alessio(Nokia) provides r07 in drafts
Qian (Ericsson) provides comments on drafted r07
LiMeng (Huawei) provides comments on drafted r07
alessio(Nokia) provides r08 in drafts
LiMeng (Huawei) requests to remove the last question
Qian (Ericsson) requests to add the CR as attachment
alessio(Nokia) suggests handling in CC#4
==== Final Comments Deadline ====
alessio(Nokia) provides r09 in drafts folder that includes attachment which would be r10+changes in drafts folder
Revised
9.19.2 S2-2301465 LS OUT Approval LS on secured and trusted access to the serving PLMN OAM server by a MBSR SA WG2 Rel-18 Revision of S2-2301321r09. Approved Approved
9.19.2 - - - Documents exceeding TU budget - - Docs:=8 -
9.19.2 S2-2301283 CR Approval 23.502 CR3865 (Rel-18, 'B'): MBSR authorization Intel Rel-18 Not Handled To be merged into 0226 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300802 CR Approval 23.273 CR0277 (Rel-18, 'F'): Update LMF function and procedure to support location service involving mobile base station relay CATT Rel-18 Not Handled To be merged into S2-2301161 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300803 CR Approval 23.273 CR0278 (Rel-18, 'F'): Remove the editor s note related to privacy check CATT Rel-18 Not Handled To be merged into S2-2301161? ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300224 CR Approval 23.501 CR3852 (Rel-18, 'F'): Mobile IAB authorization update Ericsson Rel-18 Not Handled To be merged into S2-2301015 & S2-2301282 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300223 CR Approval 23.501 CR3851 (Rel-18, 'F'): Mobile IAB configuration support Ericsson Rel-18 Not Handled To be merged into S2-2301297 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300583 CR Approval 23.501 CR3944 (Rel-18, 'B'): Update of MBSR authorization Huawei, HiSilicon Rel-18 Not Handled To merge with S2-2301015 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300581 CR Approval 23.501 CR3943 (Rel-18, 'B'): Addressing EN about UEs accessing emergency service Huawei, HiSilicon Rel-18 Not Handled To merge with S2-2301010 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.19.2 S2-2300580 CR Approval 23.501 CR3942 (Rel-18, 'B'): UE mobility when moving together with a MBSR cell Huawei, HiSilicon Rel-18 Not Handled To be merged into S2-2301295 ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 - - - Study on the support for 5WWC Phase 3 (FS_5WWC_Ph2) - - Docs:=21 -
9.20.1 S2-2300093 LS In Information LS from CableLabs: Feedbacks on solutions for 5WWC_Ph2 Key Issue 1 CableLabs (CableLabs LS Response on 3GPP Rel-18 5WWC_Ph2) Postponed Sebastian (Qualcomm) comments that LS can be noted given that we are concluding the study in this meeting based on the LS
Marco(Huawei) comments that an LS with the conclusion would be nice to inform them
Laurent (Nokia): let's keep the ls open and decide in April whether to send a LS to inform them (I think Marco has a good idea)
Postponed
9.20.1 S2-2300038 LS In Action LS from BBF: BBF answer to your liaison S2-2207761 solutions for 5WWC_Ph2 Key Issue 1 BBF (LIAISE-562-05) Postponed Sebastian (Qualcomm) comments that LS can be noted given that we are concluding the study in this meeting based on the LS
Marco(Huawei) comments that an LS with the conclusion would be nice to inform them
Laurent (Nokia): let's keep the ls open and decide in April whether to send a LS to inform them (I think Marco has a good idea)
Postponed
9.20.1 S2-2300505 P-CR Approval 23.700-17: KI#1: Solutions evaluation and conclusion. CableLabs, Charter, Comcast Rel-18 r07 + changes agreed. Revised to S2-2301834. To serve as baseline for conclusions on the support of AUN3 devices Laurent (rapporteur): provides r01 to serve as baseline for conclusions on the support of AUN3 devices
Laurent (Nokia): provides r02
Sriram(CableLabs) provides r03
Marco (Huawei) provides several questions and comments
Stefan (Ericsson) provides comments
Laurent (Nokia): provides r04
Laurent (Nokia): provides r05
Sebastian (Qualcomm) asks questions and comments
Sriram(CableLabs) provides clarifications and responds to Marco and Stefan.
Sriram(CableLabs) provides clarifications.
Sriram(CableLabs) provides r06.
Stefan (Ericsson) comments and provides r07
Dieter (Deutsche Telekom) comments.
Marco (Huawei) agree and support Stefan's (Ericsson) r07 and concern on almost all previous version.
Laurent (Nokia): provides r08
Sriram(CableLabs) responds to Stefan (Ericsson).
Sriram(CableLabs) provides r09.
Stefan (Ericsson) replies to Sriram
Sriram(CableLabs) replies to Stefan.
==== Revisions Deadline ====
Stefan (Ericsson) reponds to Sriram
Marco(Huawei) OK for r07, r08 and object r09 (NOK from r00 to r06)
Dieter (Deutsche Telekom) OK for r07, r08 and objects to all other revisions
Sriram (CableLabs) OK with r07 or r08.
Yildirim (Charter) is fine with r07 or r08.
Stefan (Ericsson) prefers r07, can live with r08 and objects r09 and r00-r06
Laurent (Nokia): Prefers R08 but can live with R07
Stefan (Ericsson) replies to Laurent
Stefan (Ericsson) comments to go for r07 or work a bit further on the additional text for BR control in r08
==== Final Comments Deadline ====
Laurent (Nokia): proposes to approve R07 + following sentence: 'The network (e.g. PCF or OAM) is able to control the aggregate traffic of all the PDU Sessions (of a 5G RG and of the AUN3 devices using the 5G RG) using a wireline access, ensuring that the sum of the MBR limits of these PDU Sessions remains below a subscribed maximum value. The mechanism is to be determined in normative phase but is not on a per packet basis for the aggregate. '
Laurent (Nokia): provides the link to the R07 + sentence in CC4 folder
Revised
9.20.1 S2-2301834 P-CR Approval 23.700-17: KI#1: Solutions evaluation and conclusion. CableLabs, Charter, Comcast, Nokia, Nokia shanghai Bell Rel-18 Revision of S2-2300505r07 + changes. Approved Approved
9.20.1 S2-2300344 P-CR Approval 23.700-17: KI#1: conclusion proposals on subscriptions and PDU sessions. Ericsson Rel-18 r06 agreed. Revised to S2-2301835. To serve as baseline for general conclusions applicable to different types of devices Laurent (rapporteur): To serve as baseline for general conclusions applicable to different types of devices
Laurent (Nokia): provides r01
Sebastian (Qualcomm) provides r02
Marco(Huawei) the addition of ARP & Periodicity depends by SoH on PIN
Marco(Huawei) question on delay budget evaluation and usage
Yubing (China Telecom): provides comments and proposes that solution#6 should be classified into the category of device with independent subscription
Stefan (Ericsson) provides comments and questions
Laurent (Nokia): provides r03
Curt (Meta) replies to Marco (Huawei)
Sebastian (Qualcomm) replies to Stefan
Sebastian (Qualcomm) replies to Marco
Sebastian (Qualcomm) replies and provides r04
Yubing (China Telecom) replies to Stefan (Ericsson) and Laurent (Nokia)
Stefan (Ericsson) provides r05
Yubing (China Telecom) replies to Stefan(Ericsson) and provides r06
Sebastian (Qualcomm) replies to Stefan and provides r07
Laurent (Nokia): provides r08
Stefan (Ericsson) provides r09
==== Revisions Deadline ====
Stefan (Ericsson) can accept r05, r06, r09. Objects to r00-r04 and r07-r08.
Marco(Huawei) OK with R05, R06, R09. Objects to R00- R04 and R07-R08.
Laurent (Nokia): objects to R00, R02, R04+R07+R08+R09
Sriram(CableLabs) is ok with r09.
Sriram(CableLabs) is can live r05 Or r06. Prefer r05.
==== Final Comments Deadline ====
Revised
9.20.1 S2-2301835 P-CR Approval 23.700-17: KI#1: conclusion proposals on subscriptions and PDU sessions. Ericsson Rel-18 Revision of S2-2300344r06. Approved Approved
9.20.1 S2-2300609 P-CR Approval 23.700-17: KI1 conclusions: NAUN3 devices . Nokia, Nokia Shanghai Bell Rel-18 CC#4: r13 with the note removed was agreed and revised in S2-2301484 To serve as baseline for conclusions on the support of NAUN3 devices Laurent (Nokia): answers with concerns on r01
Laurent (rapporteur): 0609 is To serve as baseline for discussions on conclusions on the support of NAUN3 devices
Sriram (CableLabs) provides comments and offer r01 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2300609r01.zip> .
Huan (vivo) asks for clarifications
Susan (Huawei) provides r01.
Sebastian (Qualcomm) provides r02
Yildirim (Charter) comments; and provides r03 includes Sol #21 to the conclusion.
Huan (vivo) provides r04
Sriram(CableLabs) provides r05 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/INBOX/Revisions/S2-2300609r05.zip> and provides clarifications to Laurent's question.
Susan (Huawei) provides r06.
Sriram(CableLabs) replies to Susan and provides clarification on applicability of solution to FN-RG.
Stefan (Ericsson) provides comments
Laurent (Nokia): provides r08
Sebastian (Qualcomm) provides r09
Yildirim (Charter) comments and provides r10.
Susan (Huawei) provides r11.
Susan (Huawei) clarifies that the discussion on reusing URSP or defining a new policy in PIN is still ongoing.
Stefan (Ericsson) supports the updates made by Susan
Yubing (China Telecom) provides r12
Laurent (Nokia): provides r13
Marco (Huawei) the additional policy vs URSP is NOT decided in PIN there is controversial
==== Revisions Deadline ====
Marco(Huawei) ok with R13, r12, r11 and object any other
Laurent (Nokia): can only live with R00, R08, R11 and R13; objects to any other version
Huan (vivo) is OK with r13
Yubing (China Telecom) is OK with r12
Dieter (Deutsche Telekom) prefers 13, is OK with 11, not ok with 12, 10, and other revisions
Stefan (Ericsson) ok with r13, r11, r08 and object any other
Sriram(CableLabs) ok with r13. Object to all other revisions.
Yildirim (Charter) OK with r13.
Marco(Huawei) Revised position: OK with R13, r12, r11. I can survive with r08 object any other
Sebastian (Qualcomm) can only accept r09; objects to other versions for reasons given earlier
==== Final Comments Deadline ====
Laurent (Nokia): proposes a SoH on this topic
Revised
9.20.1 S2-2301484 P-CR Approval 23.700-17: KI1 conclusions: NAUN3 devices . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300609r13 with the note removed. Approved Approved
9.20.1 S2-2301257 P-CR Approval 23.700-17: KI#1, Evaluation and Conclusion for solutions targeting UE(s) type of devices. Intel Rel-18 Revised to S2-2301861. To serve as baseline for conclusions on the support of UE(s) Laurent (rapporteur): provides r01 to serve for conclusions on the support of UE(s) (removing evaluation)
Laurent (Nokia): provides r02
Yildirim (Charter) asks Laurent (Nokia) a question on r02 for clarification.
Marco (Huawei) asks question on NSWOF
Yildirim (Charter) answers to Marko.
Marco (Huawei) answers to Yildirim (Charter)
Stefan (Ericsson) comments and provides r03
Laurent (Nokia): provides r04
Sriram (CableLabs) seeks clarification.
Sriram (CableLabs) provides r05.
Sriram (CableLabs) provides r06.
Yildirim (Charter) agrees with CableLabs on the removal of the NOTE.
Marco (Huawei) comments r06.
Laurent (Nokia): same comments than Marco/HW
==== Revisions Deadline ====
Marco(Huawei) OK with r05 and I can live with R06
Laurent (Nokia): objects to R00, R01, R05, R06 but can live with R05/R06 if we add following text: 'NOTE: FN-RG is only supported for untrusted access and with no R18 normative work (e.g. TR 23.700-17 § 6.2.2 does not apply to FN RG)'
Huan (vivo) is OK with r05/ R06 with the NOTE proposed by Nokia
Sriram(CableLabs) is OK with r05 with the NOTE proposed by Nokia.
Stefan (Ericsson) ) is OK with r05/r06 with the NOTE proposed by Nokia.
Yildirim (Charter) is OK with r05 with the NOTE proposed by Nokia.
Marco(Huawei) is OK with r05 with the NOTE proposed by Nokia.
==== Final Comments Deadline ====
Revised
9.20.1 S2-2301861 P-CR Approval 23.700-17: KI#1, Evaluation and Conclusion for solutions targeting UE(s) type of devices. Intel, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301257. Approved Approved
9.20.1 - - - Documents exceeding TU budget - - Docs:=11 -
9.20.1 S2-2301256 P-CR Approval 23.700-17: KI#1, Evaluation and Conclusion for solutions targeting AUN3 type of devices. Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300608 P-CR Approval 23.700-17: KI1 conclusions: AUN3 devices. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300611 P-CR Approval 23.700-17: TR clean up. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2301016 P-CR Approval 23.700-17: Partial conclusion for key issue 1 / handling of WiFi Alliance LS. Qualcomm Incorporated, Meta USA Rel-18 Not Handled Chunhui (Xiaomi) comments.
Sebastian (Qualcomm) replies to Chunhui
Chunhui (Xiaomi) provides further comments.
Sebastian (Qualcomm) suggests to continue the discussion in the thread for S2-2300344
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300722 P-CR Approval 23.700-17: KI#1: Conclusion on KI#1. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300642 P-CR Approval 23.700-17: KI#2, update conclusion on KI#2 about TNGF selection. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300698 P-CR Approval 23.700-17: KI#1, Partial conclusions for NAUN3 device. China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300343 P-CR Approval 23.700-17: KI#1, Partial conclusions for NAUN3 device behind 5G-RG. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300529 P-CR Approval 23.700-17: KI#1: Conclusion proposals to NAUN3 devices. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300610 P-CR Approval 23.700-17: KI1 conclusions: 3GPP UE(s) and conclusions valid for any kind of device. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.1 S2-2300345 P-CR Approval 23.700-17: KI#1: Discussion and proposal on provisioning differentiated services for home and guest UEs behind 5GRG. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 - - - Support for 5WWC Phase 3 (5WWC_Ph2) - - Docs:=19 -
9.20.2 S2-2300641 CR Approval 23.503 CR0843 (Rel-18, 'B'): ANDSP extension to support TNGF selection for S-NSSAI needed by UE Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2301836. Sebastian (Qualcomm) provides r01
==== Revisions Deadline ====
Yishan (Huawei) is ok with r01
==== Final Comments Deadline ====
Revised
9.20.2 S2-2301836 CR Approval 23.503 CR0843R1 (Rel-18, 'B'): ANDSP extension to support TNGF selection for S-NSSAI needed by UE Huawei, HiSilicon Rel-18 Revision of S2-2300641r01. Approved Agreed
9.20.2 S2-2300639 CR Approval 23.501 CR3953 (Rel-18, 'B'): TNGF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2301837. Laurent (Nokia): provides a suggested r01
Heng (China Telecom): provides a suggested r02 on r01
Yishan (Huawei) is ok with r02
==== Revisions Deadline ====
Laurent (Nokia): objects to R00
==== Final Comments Deadline ====
Revised
9.20.2 S2-2301837 CR Approval 23.501 CR3953R1 (Rel-18, 'B'): TNGF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, China Telecom Rel-18 Revision of S2-2300639r02. Approved Agreed
9.20.2 S2-2300640 CR Approval 23.502 CR3762 (Rel-18, 'B'): TNGF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2301838. Myungjune (LGE) provides r02
Laurent (Nokia): provides r01
Heng(China Telecom): provides r03 on r02
Stefan (Ericsson) comments and provides r04
Yishan (Huawei) is ok with r05
==== Revisions Deadline ====
Laurent (Nokia): objects to R02, R03, R04
==== Final Comments Deadline ====
Revised
9.20.2 S2-2301838 CR Approval 23.502 CR3762R1 (Rel-18, 'B'): TNGF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, China Telecom Rel-18 Revision of S2-2300640r05. Approved Agreed
9.20.2 S2-2300018 LS In Information LS from Wi-Fi Alliance: Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks Wi-Fi Alliance (20221202_WiFi_Alliance) Response drafted in S2-2301046. Postponed Postponed
9.20.2 S2-2301046 LS OUT Approval [DRAFT] Reply LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks Qualcomm Rel-18 Response to S2-2300018. Postponed Chunhui (Xiaomi) suggests to discuss DSCP mapping in the thread of S2-2301016 (P-CR).
marco (Huawei) propose to postpone this KLS
Laurent (Nokia): Comments
Chunhui (Xiaomi) comments.
Sebastian (Qualcomm) comments
Sebastian (Qualcomm) replies
Marco (Huawei) comments
Laurent (Nokia): the LS cannot agreed as it has 2 options
Sebastian (Qualcomm): that is true; should we postpone it?
==== Revisions Deadline ====
Chunhui (Xiaomi) supports to postpone this LS to next meeting.
Laurent (Nokia): supports to postpone this LS
Sebastian (Qualcomm) is ok to postpone
==== Final Comments Deadline ====
Postponed
9.20.2 S2-2300021 LS In Action LS from CT WG1: Reply LS on the slice-specific N3IWF prefix configuration in VPLMN CT WG1 (C1-227033) Rel-18 Response drafted in S2-2301048. Final response in S2-2301839 Replied to
9.20.2 S2-2301048 LS OUT Approval [DRAFT] Reply LS on the slice-specific N3IWF prefix configuration in VPLMN Qualcomm Rel-18 Response to S2-2300021. r01 agreed. Revised to S2-2301839. Marco(Huawei) propose to postpone or select option 2
Heng(China Telecom) provide r01
Sebastian (Qualcomm) comments that Marco's comments are presumably for a different paper.
Laurent (Nokia): suggests to go ahead with r01
Sebastian (Qualcomm) is fine with r01
Marco (Huawei) please ignore my previous comment. OK with r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.20.2 S2-2301839 LS OUT Approval Reply LS on the slice-specific N3IWF prefix configuration in VPLMN SA WG2 Rel-18 Revision of S2-2301048r01. Approved Approved
9.20.2 - - - Documents exceeding TU budget - - Docs:=8 -
9.20.2 S2-2301209 CR Approval 23.503 CR0888 (Rel-18, 'B'): Control Request Triggers relevant for AMF for N3IWF selection based on slice support Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2301047 CR Approval 23.501 CR4048 (Rel-18, 'F'): Clarifying applicability of slice-specific N3IWF prefix configuration from HPLMN Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300830 CR Approval 23.502 CR3796 (Rel-18, 'B'): Update to 4.12.2.2 to resolve ENs China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300567 CR Approval 23.502 CR3747 (Rel-18, 'F'): Update of Registration procedure for untrusted non-3GPP access to resolve editor's notes LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300566 CR Approval 23.501 CR3936 (Rel-18, 'F'): Clarification on N3IWF selection enhancement for support of S-NSSAI needed by UE LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300342 CR Approval 23.502 CR3706 (Rel-18, 'C'): Delivery of N3IWF selection policies to UE Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300832 CR Approval 23.503 CR0862 (Rel-18, 'B'): Add Configured NSSAI change as Policy Control Request Trigger China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.20.2 S2-2300638 DISCUSSION Discussion Discussion on CRs for TNGF selection. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.21 - - - Stage 2 of MPS_WLAN (MPS_WLAN) - - Docs:=9 -
9.21 S2-2301092 CR Approval 23.402 CR2998R1 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2209051. r04 agreed. Revised to S2-2301840. Shabnam (Ericsson) provides comments and requests if the CR can be updated to reflect them.
Shabnam (Ericsson) provides comments with the correct CR and requests if the CR can be updated to reflect them.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.21 S2-2301840 CR Approval 23.402 CR2998R2 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2301092r04. Approved Agreed
9.21 S2-2301095 CR Approval 23.502 CR3595R1 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2209053. r03 agreed. Revised to S2-2301841. Marco(Huawei) asks clarification
Haris(Qualcomm) comments
Shabnam (Ericsson) provides comments and requests if the CR can be updated to reflect them.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.21 S2-2301841 CR Approval 23.502 CR3595R2 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2301095r03. Approved Agreed
9.21 S2-2301096 DISCUSSION Information User plane QoS differentiation via control plane. Peraton Labs Rel-18 Revision of S2-2209054. Noted Haris(Qualcomm) comments
Yildirim(Charter) comments
Pallab (Nokia) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.21 S2-2301089 CR Approval 23.401 CR3713R1 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2209050. r04 agreed. Revised to S2-2301842. Shabnam (Ericsson) provides comments and requests update
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.21 S2-2301842 CR Approval 23.401 CR3713R2 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2301089r04. Approved Agreed
9.21 S2-2301093 CR Approval 23.501 CR3745R1 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2209052. r05 agreed. Revised to S2-2301843. Marco(Huawei) provides r01
Shabnam (Ericsson) provides comments
==== Revisions Deadline ====
Marco(Huawei) ok with r05
==== Final Comments Deadline ====
Revised
9.21 S2-2301843 CR Approval 23.501 CR3745R2 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA Rel-18 Revision of S2-2301093r05. Approved Agreed
9.22.1 - - - Study on 5G AM Policy (FS_AMP) - - Docs:=0 -
9.22.2 - - - 5G AM Policy (AMP) - - Docs:=12 -
9.22.2 - - - CR for 23.501 - - Docs:=5 -
9.22.2 S2-2300185 CR Approval 23.501 CR3837 (Rel-18, 'F'): Resolving EN on PCF s awareness of modified RFSP index indicating a change of priority from 5GC to EPC Ericsson Rel-18 r05 agreed. Revised to S2-2301844, merging S2-2300299 Haiyang (Huawei) comments to r02.
Judy (Ericsson) provides r02
Haiyang (Huawei) corrects the Agenda and provides r01.
Zhuoyi(China Telecom) suggests to use this paper as baseline to resolve the EN in 501.
Chris (Vodafone) provides r04.
Haiyang (Huawei) provides r03.
Judy (Ericsson) provides r05
Judy (Ericsson) wonders if Haiyang (Huawei)'s email is delayed as r04 is provided by Chris earlier
Haiyang (Huawei) responses to Judy (Ericsson)
Judy (Ericsson) responds to Haiyang (Huawei)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.22.2 S2-2301844 CR Approval 23.501 CR3837R1 (Rel-18, 'F'): Resolving EN on PCF s awareness of modified RFSP index indicating a change of priority from 5GC to EPC Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2300185r05, merging S2-2300299. Approved Agreed
9.22.2 S2-2300299 CR Approval 23.501 CR3869 (Rel-18, 'F'): Removing ENs on PCF awareness of IWK Huawei, HiSilicon, China Telecom Rel-18 Merged into S2-2301844 Zhuoyi(China Telecom) suggests this paper merge to S2-2300185 to resolve the EN in 501.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.22.2 S2-2300841 CR Approval 23.501 CR3991 (Rel-18, 'B'): Clarification of AMF behaviour when it receives RFSP Index in Use Validity Time from MME during UE mobility from EPS to 5GS Samsung Rel-18 r01 agreed. Revised to S2-2301845. Haiyang (Huawei) corrects the title and provides questions
Judy (Ericsson) provides r01 and responds to Haiyang (Huawei)
Ashok (Samsung) is OK with r01
Haiyang (Huawei) clarifies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.22.2 S2-2301845 CR Approval 23.501 CR3991R1 (Rel-18, 'B'): Clarification of AMF behaviour when it receives RFSP Index in Use Validity Time from MME during UE mobility from EPS to 5GS Samsung, Ericsson Rel-18 Revision of S2-2300841r01. Approved Agreed
9.22.2 - - - CR for 23.502 - - Docs:=4 -
9.22.2 S2-2300481 CR Approval 23.502 CR3735 (Rel-18, 'F'): Missing part in approved S2-2209611 from SA WG2#153E China Telecom Rel-18 Approved Ashok (Samsung) thanks Judy (Ericsson) for providing r01
Judy (Ericsson) comments and provides r01
Zhuoyi (China Telecom) points out the previous comments from Ericsson and Samsung are for another paper. No revision is provided yet.
Judy (Ericsson) thanks Zhuoyi (China Telecom) to point out my mistake. Andy, please ignore the comments before Zhuoyi including r01 which were intended for 0841, apology for the additional work on you.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.22.2 S2-2300840 CR Approval 23.502 CR3799 (Rel-18, 'F'): Clarification for the need of RFSP Index in Use Validity Time in Namf_Communication_UEContextTransfer service operation Samsung Rel-18 Corrupt file in ZIP - replaced in Docs. r01 agreed. Revised to S2-2301846. Ashok (Samsung) provides r01 by enabling the change mark for the proposed change
Judy (Ericsson) comments that there is no track change for the proposed changes
Haiyang (Huawei) comments
Haiyang (Huawei) provides comments
Ashok (Samsung) responds to Judy (Ericsson) and Haiyang (Huawei)
==== Revisions Deadline ====
Ashok (Samsung) clarifies to Judy (Ericsson)
Judy (Ericsson) responds to Ashok (Samsung)
==== Final Comments Deadline ====
Revised
9.22.2 S2-2301846 CR Approval 23.502 CR3799R1 (Rel-18, 'F'): Clarification for the need of RFSP Index in Use Validity Time in Namf_Communication_UEContextTransfer service operation Samsung Rel-18 Revision of S2-2300840r01. Approved Agreed
9.22.2 S2-2300843 CR Approval 23.502 CR3800 (Rel-18, 'B'): Clarification of AMF behaviour when it receives RFSP Index in Use Validity Time from MME during UE mobility from EPS to 5GS Samsung Rel-18 Noted Ashok (Samsung) replies
Judy (Ericsson) questions the need of this CR
Haiyang (Huawei) also fine to only have 501 CR on this topic.
==== Revisions Deadline ====
Judy (Ericsson) confirms that this CR is noted as the change in 23.501 CR is sufficient
Ashok (Samsung) agrees with Judy (Ericsson) and ready to NOTE it
==== Final Comments Deadline ====
Noted
9.22.2 - - - CR for 23.503 - - Docs:=3 -
9.22.2 S2-2300298 CR Approval 23.503 CR0813 (Rel-18, 'F'): Removing ENs on PCF awareness of IWK Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301847, merging S2-2300361 Zhuoyi (China Telecom) comments and provide r03.
Haiyang (Huawei) comments and provide r02, also add China Telecom as cosigner.
Zhuoyi(China Telecom) correct the AI#.
Judy (Ericsson) comments and provide r01
Zhuoyi(China Telecom) suggests to use this paper as baseline to resolve the EN in 503 and cosign.
Judy (Ericsson) responds and provides r04
Haiyang (Huawei) prefers r03.
==== Revisions Deadline ====
Judy (Ericsson) accepts r01/r04, objects to other revisions including r00
==== Final Comments Deadline ====
Revised
9.22.2 S2-2301847 CR Approval 23.503 CR0813R1 (Rel-18, 'F'): Removing ENs on PCF awareness of IWK Huawei, HiSilicon, China Telecom, Ericsson Rel-18 Revision of S2-2300298r04, merging S2-2300361. Approved Agreed
9.22.2 S2-2300361 CR Approval 23.503 CR0820 (Rel-18, 'F'): Resolving EN on PCF s awareness of modified RFSP index indicating a change of priority from 5GC to EPC Ericsson Rel-18 Merged into S2-2301847 Judy (Ericsson) agrees to the proposal from the rapporteur Zhuoyi(China Telecom)
Zhuoyi(China Telecom) suggests this paper merge to S2-2300298 to resolve the EN in 503.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.23.1 - - - Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) - - Docs:=0 -
9.23.2 - - - Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) - - Docs:=156 -
9.23.2 - - - Key Issue #1: How to improve correctness of NWDAF analytics - - Docs:=19 -
9.23.2 S2-2300535 DISCUSSION Information KI#1 Moderated Discussions on KI#1 skeleton and interest gathering. Vivo Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300142 DISCUSSION Endorsement Discussion on ML Model profile. Lenovo Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300106 CR Approval 23.288 CR0598 (Rel-18, 'B'): Rating untrusted AF data sources Lenovo Mobile Com. Technology Rel-18 Postponed Zhang (Ericsson) object the proposal
Akito provides r01 to align with the terminology in TS23.288.
Fabio (Nokia) provides comments.
Jungshin (Samsung) provides comments.
==== Revisions Deadline ====
Costas (Lenovo) suggest to postpone
Zhang (Ericsson) suggest to postpone
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300110 CR Approval 23.288 CR0556R1 (Rel-18, 'B'): Updates for Model Provisioning for Analytics of Group UEs Ericsson, InterDigital Inc. Rel-18 Revision of S2-2210269. r02 agreed. Revised to S2-2301457. Costas (Lenovo) provides comments
Zhang (Ericsson) response to Costas (Lenovo)
Costas (Lenovo) elaborate further
Fabio (Nokia) provides r01.
Zhang (Ericsson) provide r02
Fabio (Nokia) is OK with r02.
Costas (Lenovo) objects r02
Zhang (Ericsson) provides r03
==== Revisions Deadline ====
Fabio (Nokia) is OK with r03.
Costas (Lenovo) respond to Zhang
Fabio (Nokia) proposes to accept r02, and to replace the definition of 'requested representative ratio' with: 'Requested representative ratio: a minimum percentage of UEs in the group whose data is a non-empty set and can be used in the model training when the Target of ML Model Reporting is a group of UEs.'
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301457 CR Approval 23.288 CR0556R2 (Rel-18, 'B'): Updates for Model Provisioning for Analytics of Group UEs Ericsson, InterDigital Inc., Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300110r02. Approved Agreed
9.23.2 S2-2300111 CR Approval 23.288 CR0557R1 (Rel-18, 'B'): Monitoring of accuracy of ML models Ericsson Rel-18 Revision of S2-2210274. r07 agreed. Revised to S2-2301980. Zhang (Ericsson) provides r01
Xiaoyan (CATT) provides r02.
Dimitris (Lenovo) comments
Fabio (Nokia) provides comments to r02.
Haiyang (Huawei) provides r03.
Zhang (Ericsson) object r03 and provide comments
Dimitris (Lenovo) provides comments
Xiaobo (vivo) provides r04 with some update and clarification.
Juan Zhang (Qualcomm) provides comments.
Zhang (Ericsson) provides r05 and comments
Juan Zhang (Qualcomm) provides comments to r05.
Zhang (Ericsson) response to Juan (Qualcomm)
Dimitris (Lenovo) provides r07
Yannick (Convenor): To record that r06 was provided by Ericsson.
==== Revisions Deadline ====
Xiaoyan (CATT) would like to co-sign this CR.
Juan Zhang (Qualcomm) is OK with r07.
Zhang (Ericsson) is OK with r07
Xiaobo (vivo) would like to co-sign this CR.
Fabio (Nokia) is OK with r07.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301980 CR Approval 23.288 CR0557R2 (Rel-18, 'B'): Monitoring of accuracy of ML models Ericsson, CATT, Vivo Rel-18 Revision of S2-2300111r07. Approved Agreed
9.23.2 S2-2300309 CR Approval 23.288 CR0564R1 (Rel-18, 'B'): Adding Accuracy Checking Capability to NWDAF Architecture Huawei, HiSilicon Rel-18 Revision of S2-2210348. r07 agreed. Revised to S2-2301981. Xiaobo (vivo) clarify how to revise the baseline CR to avoid overlapping with S2-2300111 <file:///E:/3GPP%20SA/SA2/SA2%23154AH/external/SA2_154AHE/docs/Docs/S2-2300111.zip> .
Zhang (Ericsson) suggest to merge clause 6.2X in the paper into S2-2300111
Dimitris (Lenovo) comments
Fabio (Nokia) provides comments
Haiyang (Huawei) provides r01 as Xiaobo proposed. Also capture Clause 5C.3.1 in S2-2300760
Jiahui (China Telecom) provides comment.
Zhang (Ericsson) provide r02
Dimitris (Lenovo) provides r03 based on r02
Haiyang (Huawei) is OK with r03
Fabio (Nokia) provides r04.
Xiaobo (vivo) provides r05 on top of r03.
Xiaobo (vivo) provides r06 by merging r05(from xiaobo) and r04(from Fabio).
Dimitris (Lenovo) is ok with r06
Haiyang (Huawei) provides r07.
Fabio (Nokia) is OK with r07
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r07
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301981 CR Approval 23.288 CR0564R2 (Rel-18, 'B'): Adding Accuracy Checking Capability to NWDAF Architecture Huawei, HiSilicon,vivo Rel-18 Revision of S2-2300309r07. Approved Agreed
9.23.2 S2-2300536 CR Approval 23.288 CR0637 (Rel-18, 'B'): Analytics/ML Model Accuracy Monitoring Functional Description Vivo Rel-18 r05 agreed. Revised to S2-2301982. Zhang (Ericsson) provides comments
Dimitris (Lenovo) provides r01
Fabio (Nokia) provides comments to r01 and asks for confirmation.
Bahador (NTT DOCOMO) provides comments on the 'input data collection' and 'ground truth collection' steps
Xiaobo (vivo) provides r02 to address comments from Zhang(Ericsson)/Fabio(Nokia)/ Bahador(NTT DoCoMo)
Zhang (Ericsson) provides r03
Jiahui (China Telecom) provides r04
Xiaobo (vivo) provides r05 with some cleanup
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r05 and co-sign
Fabio (Nokia) is OK with r05.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301982 CR Approval 23.288 CR0637R1 (Rel-18, 'B'): Analytics/ML Model Accuracy Monitoring Functional Description Vivo, Lenovo Rel-18 Revision of S2-2300536r05. Approved Agreed
9.23.2 S2-2300541 CR Approval 23.288 CR0640 (Rel-18, 'B'): Update on Multiple ML models for an analytics ID Vivo Rel-18 r01 agreed. Revised to S2-2301983. Zhang (Ericsson) provides comments
Fabio (Nokia) provides comments to the paper
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301983 CR Approval 23.288 CR0640R1 (Rel-18, 'B'): Update on Multiple ML models for an analytics ID Vivo Rel-18 Revision of S2-2300541r01. Approved Agreed
9.23.2 S2-2300804 CR Approval 23.288 CR0658 (Rel-18, 'B'): KI#1: Update for supporting analytics feedback ETRI Rel-18 r04 agreed. Revised to S2-2301984. Zhang (Ericsson) provides comments
Antoine (Orange) makes 3 comments.
Fabio (Nokia) provides comments.
Dimitris (Lenovo) comments
Soohwan provides r01 and replies to comments.
Soohwan (ETRI) corrects the link for r01.
Antoine (Orange) comments.
Soohwan (ETRI) provides r02.
Xiaobo (vivo) provides some clarification and r03.
Antoine (Orange) comments on the changes added in r03.
Zhang (Ericsson) provides r04 and comments
Dimitris (Lenovo) comments on r04 provides r05.
Antoine (Orange) provides r06, removing the occurences of 'ground truth' and adding 's' to 'analytic'.
Zhang (Ericsson) response to Dimitris (lenovo)
==== Revisions Deadline ====
Zhang (Ericsson) only OK with r04 and object all other versions
Dimitris (Lenovo) is ok to proceed with r04
Fabio (Nokia) is OK to proceed with r04 too.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301984 CR Approval 23.288 CR0658R1 (Rel-18, 'B'): KI#1: Update for supporting analytics feedback ETRI, vivo Rel-18 Revision of S2-2300804r04. Approved Agreed
9.23.2 S2-2301049 CR Approval 23.288 CR0673 (Rel-18, 'B'): Procedure for accuracy monitoring at NWDAF containing AnLF China Telecom Rel-18 r04 agreed. Revised to S2-2301985. Jiahui (China Telecom) replys Ericsson and provides r01
Zhang (Ericsson) provides comments
Fabio (Nokia) comments on r01
Haiyang (Huawei) provides r02.
Jiahui (China Telecom) replys to Nokia and provides r03
Fabio (Nokia) provides r04.
==== Revisions Deadline ====
Jiahui (China Telecom) is ok with r04.
Zhang (Ericsson) is OK with r04
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301985 CR Approval 23.288 CR0673R1 (Rel-18, 'B'): Procedure for accuracy monitoring at NWDAF containing AnLF China Telecom Rel-18 Revision of S2-2301049r04. Approved Agreed
9.23.2 S2-2301270 CR Approval 23.288 CR0689 (Rel-18, 'B'): MTLF-based ML Model Accuracy Monitoring Nokia, Nokia Shanghai Bell Rel-18 r06 agreed. Revised to S2-2301986. Zhang (Ericsson) provide r01
Dimitris (Lenovo) provides r02
Soohwan (ETRI) provides r03 and add ETRI a co-source company.
Fabio (Nokia) provides r04.
Xiaobo (vivo) provides comments and r05.
Fabio (Nokia) is OK with r05 and provides comments.
Zhang (Ericsson) provide r06
==== Revisions Deadline ====
Fabio (Nokia) is OK with r06.
Zhang (Ericsson) co-sign the paper
Fabio (Nokia) confirms Ericsson will be added as co-signer to the last submission with the new tdoc number.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301986 CR Approval 23.288 CR0689R1 (Rel-18, 'B'): MTLF-based ML Model Accuracy Monitoring Nokia, Nokia Shanghai Bell, ETRI, vivo, Ericsson Rel-18 Revision of S2-2301270r06. Approved Agreed
9.23.2 - - - Key Issue #2: NWDAF-assisted application detection - - Docs:=6 -
9.23.2 S2-2300442 CR Approval 23.288 CR0625 (Rel-18, 'B'): KI#2 Clarification on PFD Determination Analytics in TS 23.288 China Mobile, KDDI Rel-18 r07 agreed. Revised to S2-2301987. Jungshin (Samsung) provides r01.
Aihua(CMCC) provides r02.
Kenichi (KDDI) provides r03 to merge S2-2300453 in S2-2300442, based on the rapporteurs proposal.
Jungshin (Samsung) provides comments.
Aihua(CMCC) provides r04.
Belen (Ericsson) provides r05
Kenichi (KDDI) provides r06 for correction
Aihua(CMCC) provides r07.
Jungshin (Samsung) provides r08
Belen (Ericsson) objects to r08, is okay with r07, r06 and r05
==== Revisions Deadline ====
Jungshin (Samsung) can live with r07
Kenichi (KDDI) is OK with r07.
Belen (Ericsson) is okay with r07
Kenichi (KDDI) provides comment.
Aihua(CMCC) suggests to go with r07.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301987 CR Approval 23.288 CR0625R1 (Rel-18, 'B'): KI#2 Clarification on PFD Determination Analytics in TS 23.288 China Mobile, KDDI, Samsung, SK Telecom, Ericsson Rel-18 Revision of S2-2300442r07. Approved Agreed
9.23.2 S2-2300454 CR Approval 23.502 CR3727 (Rel-18, 'B'): PFD Determination by NEF (PFDF) KDDI Rel-18 r02 agreed. Revised to S2-2301988. Kenichi (KDDI) provides r01.
Thomas(Nokia) provides r02.
Kenichi (KDDI) comments for r02.
Thomas(Nokia) replies to Kenichi , prefers r02
Kenichi (KDDI) accepts r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301988 CR Approval 23.502 CR3727R1 (Rel-18, 'B'): PFD Determination by NEF (PFDF) KDDI, China Mobile, Samsung, SK Telecom Rel-18 Revision of S2-2300454r02. Approved Agreed
9.23.2 S2-2301289 CR Approval 23.501 CR4105 (Rel-18, 'B'): Update NEF to support NWDAF-assisted application detection Samsung, SK Telecom Rel-18 r03 agreed. Revised to S2-2301989. Kenichi (KDDI) provides r01.
Jungshin (Samsung): We are ok with r01.
Belen (Ericsson) provides r02
Thomas(Nokia) provides r03
==== Revisions Deadline ====
Kenichi (KDDI) is fine with r03
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301989 CR Approval 23.501 CR4105R1 (Rel-18, 'B'): Update NEF to support NWDAF-assisted application detection Samsung, SK Telecom, KDDI, Ericsson Rel-18 Revision of S2-2301289r03. Approved Agreed
9.23.2 - - - Key Issue #3: Data and analytics exchange in roaming case - - Docs:=9 -
9.23.2 S2-2300014 LS In Action LS from SA WG3: LS on the data and analytics exchange between two NWDAFs in different PLMNs SA WG3 (S3-223020) Revision of postponed S2-2210201 from S2#154. Postponed Jungshin (Samsung) proposes to postpone the LS.
Vivian(vivo) also suggest to postpone the LS.
Postponed
9.23.2 S2-2300210 CR Approval 23.288 CR0611 (Rel-18, 'B'): Key Issue #3: Data and analytics exchange in roaming case Nokia, Nokia Shanghai-Bell Rel-18 r08 agreed. Revised to S2-2301990. Vivian (vivo) provides comments and r01.
Zhang (Ericsson) provides comments
Zhang (Ericsson) response further comment
Jungshin (Samsung) provides comments and asks for clarification.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301990 CR Approval 23.288 CR0611R1 (Rel-18, 'B'): Key Issue #3: Data and analytics exchange in roaming case Nokia, Nokia Shanghai-Bell, Samsung, CATT Rel-18 Revision of S2-2300210r08. Approved Agreed
9.23.2 S2-2300527 CR Approval 23.288 CR0636 (Rel-18, 'B'): Roaming architecture for data or analytics exchange Vivo Rel-18 r07 agreed. Revised to S2-2301991. Vivian (vivo) provides r01 based on rapporteur's assignment, merging roaming architectures from S2-2301168 <file:///D:/vivian/3GPP??/SA2??/????/11136506/Documents/vchat/ChatFiles/Docs/S2-2301168.zip> ,S2-2300631 <file:///D:/vivian/3GPP??/SA2??/????/11136506/Documents/vchat/ChatFiles/Docs/S2-2300631.zip> and S2-2300210 <file:///D:/vivian/3GPP??/SA2??/????/11136506/Documents/vchat/ChatFiles/Docs/S2-2300210.zip> into S2-2300527
Zhang (Ericsson) provides comment
Jungshin (Samsung) provides comments on r01..
Bahador (NTT DOCOMO) provides r02.
Vivian (vivo) provides r03.
Xiaoyan (CATT) provides comments.
Jungshin (Samsung) agrees to Xiaoyan (CATT) and provides comments
Vivian(vivo) replies to Jungshin (Samsung) and Xiaoyan (CATT)'s comments
Juan Zhang (Qualcomm) provides comments.
Vivian (vivo) replies to Juan Zhang's (Qualcomm) comments.
Thomas (Nokia) provides r04.
Zhang (Ericsson) provides comment to R04
Wang Yuan (Huawei) provides comments.
Vivian (vivo) replies to Thomas (Nokia) comment and cannot accept R04
Vivian (vivo) provides r06 (r05 has been occupied but not declared)
Xiaoyan (CATT) provides r07.
Zhang (Ericsson) is OK with r06
Vivian(vivo) is fine with both r06 and r07
==== Revisions Deadline ====
Thomas (Nokia) is fine with r07.
Xiaoyan (CATT) would like to co-sign this CR.
Vivian(vivo) replies to Xiaoyan (CATT), and will add CATT as co-signer.
Wang Yuan (Huawei) is ok with r07 and would like to co-sign.
Juan Zhang (Qualcomm) is ok with r07 and would like to co-sign.
Zhang (Ericsson) is OK with r07 and co-sign
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301991 CR Approval 23.288 CR0636R1 (Rel-18, 'B'): Roaming architecture for data or analytics exchange Vivo, Nokia, Nokia Shanghai-Bell, CATT,cHuawei, Ericsson, Qualcomm Rel-18 Revision of S2-2300527r07. Approved Agreed
9.23.2 S2-2301169 CR Approval 23.288 CR0683 (Rel-18, 'B'): Procedures for network data analytics in roaming CATT Rel-18 r11 agreed. Revised to S2-2301458. Zhang (Ericsson) provides comments
Xiaoyan (CATT) provides r01.
Bahador (NTT DOCOMO) provides r02 and requests for clarification.
Jungshin (Samsung) provides comments.
Vivian (vivo) provides comments.
Xiaoyan (CATT) provides r03.
Xiaoyan (CATT) replies to Vivian (vivo).
Wang Yuan (Huawei) provides comments.
Thomas (Nokia) provides r04.
Xiaoyan (CATT) objects to r04.
Thomas(Nokia) objects against r00 to r03.
Provides r05
Xiaoyan (CATT) provides r06.
Xiaoyan (CATT) objects to r05.
Xiaoyan (CATT) provides r07.
Zhang (Ericsson) provides r08 and comment
Wang Yuan (Huawei) provides comments and r09.
Vivian (vivo) provides r10.
Juan Zhang (Qualcomm) provides r11..
==== Revisions Deadline ====
Thomas(Nokia) objects against r06 to r11.
Suggest agreeing r11 with the following changes (as in late r12):
The H-NWDAF or provides V-NWDAF with roaming entry capability provides the Nnwdaf_RoamingAnalytics and Nnwdaf_RoamingData services for that purpose.
NOTE: The access to the Nwdaf_AnalyticsSubscription service, and the Nwdaf_AnalyticsInfo service is expected to be restricted by the NRF to NF service consumers within the same PLMN to prevent bypassing checks based on user consent and operator policy
Editor's note: It is FFS whether an analytics profile is required in addition to analytics.
Editor's note: It is FFS whether there is a need to restrict the parameters compared to the non-roaming case. Handling of NSSAIs is FFS. Does source or target PLMN perform a mapping, and are both mapped and original S-NSSAIs required?. It is FFS how HPLMN-ID and VPLMN ID can be provided in a safe manner. It is ffs whether an indication about inbound or outbound roaming scenario is required.
Xiaoyan (CATT) can live with agreeing r11 with the following changes (as in late r13):
The H-NWDAF or V-NWDAF with roaming entry capability provides the Nnwdaf_RoamingAnalytics and Nnwdaf_RoamingData services for that purpose.
NOTE: The access to the Nnwdaf_AnalyticsSubscription service and the Nnwdaf_AnalyticsInfo service is expected to be restricted by the NRF to NF service consumers within the same PLMN to prevent bypassing checks based on user consent and operator policy
Editor's note: It is FFS whether an analytics profile is required in addition to analytics.
Editor's note: It is FFS whether there is a need to restrict the parameters compared to the non-roaming case. Handling of NSSAIs is FFS. Does source or target PLMN perform a mapping, and are both mapped and original S-NSSAIs required?. It is FFS how HPLMN-ID and VPLMN ID can be provided in a safe manner. It is ffs whether an indication about inbound or outbound roaming scenario is required.
Yannick (Convenor) asks if r05 could be acceptable.
Juan Zhang (Qualcomm) can not agree r05 and proposed to further update based on r11.
Xiaoyan (CATT) replies to Yannick (Convenor): We sustains the objection to r05, and suggests agreeing the late r13.
Thomas (Nokia) accepts agreeing r11 with the changes of Xiaoyan (CATT) (as in late r13)
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301458 CR Approval 23.288 CR0683R1 (Rel-18, 'B'): Procedures for network data analytics in roaming CATT, Qualcomm, Nokia, Nokia-Shanghai-Bell, vivo Rel-18 Revision of S2-2301169r11. Approved Agreed
9.23.2 S2-2301171 CR Approval 23.501 CR4080 (Rel-18, 'B'): Using network analytics for roaming scenarios CATT Rel-18 r01 agreed. Revised to S2-2301992. Jungshin (Samsung) provides comments.
Xiaoyan (CATT) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301992 CR Approval 23.501 CR4080R1 (Rel-18, 'B'): Using network analytics for roaming scenarios CATT Rel-18 Revision of S2-2301171r01. Approved Agreed
9.23.2 - - - Key Issue #4: How to Enhance Data collection and Storage - - Docs:=18 -
9.23.2 S2-2300112 CR Approval 23.288 CR0600 (Rel-18, 'B'): Update ML model provisioning by leveraging ML model storage in ADRF Ericsson Rel-18 Postponed Chi (China Unicom) raises some considerations about this proposal.
Fabio (Nokia) asks questions for clarification and provides comments.
Wang Yuan (Huawei) raises comments about this proposal.
Chi (China Unicom) asks question for clarification.
Zhang (Ericsson) provide response
Chi (China Unicom) suggests to treat 'multiple ML models' as a seperated issue.
Wang Yuan (Huawei) clarify previous question.
Fabio (Nokia) prefers to postpone the paper, as suggested by contributor and other companies.
==== Revisions Deadline ====
Zhang (Ericsson) is OK to postpone the CR
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300115 CR Approval 23.288 CR0603 (Rel-18, 'C'): NWDAF relocation updates Ericsson Rel-18 Postponed Fabio (Nokia) provides r01
Wang Yuan (Huawei) provides r02.
Zhang (Ericsson) provide r03
Fabio (Nokia) can't accept all revisions except r01.
Fabio (Nokia) clarifies that the valid comment is that he can't accept all revisions except r01.
==== Revisions Deadline ====
Zhang (Ericsson) propose to postpone the CR
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300118 CR Approval 23.502 CR3661 (Rel-18, 'B'): Updates on pending notifications handling Ericsson Rel-18 Noted Fabio (Nokia) objects the paper.
==== Revisions Deadline ====
Zhang (Ericsson) is OK to NOTE the paper
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300119 CR Approval 23.288 CR0606 (Rel-18, 'B'): Updates on pending notifications handling Ericsson Rel-18 r01 agreed. Revised to S2-2301993. Antoine (Orange) comments.
Wang Yuan (Huawei) provides comments about this proposal.
Zhang (Ericsson) response to Antoine (Orange)
Fabio (Nokia) provides r01.
Fabio (Nokia) objects the paper.
Fabio (Nokia) asks to disregard the previous objection to S2-2300119, as it was referred to S2-2300118.
Antoine (Orange) comments that the corresponding functional description and procedures updates are still missing.
Zhang (Ericsson) response to Fabio (Nokia) and OK with r01
==== Revisions Deadline ====
Wang Yuan (Huawei) thanks Zhang (Ericsson) for the clarification and is OK with r01 .
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301993 CR Approval 23.288 CR0606R1 (Rel-18, 'B'): Updates on pending notifications handling Ericsson Rel-18 Revision of S2-2300119r01. Approved Agreed
9.23.2 S2-2300315 CR Approval 23.288 CR0620 (Rel-18, 'B'): Storing data source rating in ADRF Lenovo Mobile Com. Technology Rel-18 Noted Zhang (Ericsson) object the proposal
Costas (Lenovo) responds to Zhang
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300447 CR Approval 23.288 CR0630 (Rel-18, 'B'): ENA_Ph3 DCCF relocation in TS 23.288 China Mobile, Nokia, Nokia Shanghai Bell Rel-18 Postponed Zhang (Ericsson) provides r01
Fabio (Nokia) objects r01 and provides r02.
Aihua(CMCC) provides r03
Fabio (Nokia) is OK with r03.
Zhang (Ericsson) provide r04 and object r02 and r03
Fabio (Nokia) can accept r02 and r03, rejects the others.
Fabio (Nokia) objects r05 and provides r06.
Aihua(CMCC) provides r05.
==== Revisions Deadline ====
Zhang (Ericsson) propose to postpone the CR
Fabio (Nokia) is OK to postpone the paper.
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300449 CR Approval 23.502 CR3725 (Rel-18, 'B'): Enhance NRF services for DCCF relocation in TS 23.502 China Mobile Rel-18 Noted Zhang (Ericsson) object r00
Aihua(CMCC) replies to Zhang (Ericsson)
Fabio (Nokia) objects to r0.
Aihua(CMCC) replies to Fabio (Nokia)
Fabio (Nokia) replies to comments from Aihua (CMCC).
Zhang (Ericsson) response to Fabio and Aihua
Aihua(CMCC) response to Fabio(Nokia) and Zhang (Ericsson)
Fabio (Nokia) replies to comments from Aihua (CMCC) about registering the indicator.
Aihua(CMCC) replies to Fabio(Nokia)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300533 CR Approval 23.501 CR3929 (Rel-18, 'B'): Considering ML model management capability during ADRF discovery and selection China Unicom Rel-18 r04 agreed. Revised to S2-2301994. Zhang (Ericsson) provides comments and object r00
Zhang (Ericsson) object r00
Chi (China Unicom) replies to Zhang (Ericsson).
Fabio (Nokia) provides comments
Costas (Lenovo) provides comments
Fabio (Nokia) replies to comments from Costas
Fabio (Nokia) replies to questions from Costas.
Costas (Lenovo) provides further comments to Fabio's response
Megha(Intel) provides comments
Fabio (Nokia) provides clarification to comments from Costas
Chi (China Unicom) replies to Costas, Fabio, Megha and Zhang.
Chi (China Unicom) provides r01 based on the previous discussions.
Chi (China Unicom) corrects the link of r01 as it may link to another file.
Costas (Lenovo) replies to Chi.
Zhang (Ericsson) provide r03 due to r02 is occupied
Chi (China Unicom) provides r04.
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r04
Fabio (Nokia) is OK with r04.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301994 CR Approval 23.501 CR3929R1 (Rel-18, 'B'): Considering ML model management capability during ADRF discovery and selection China Unicom Rel-18 Revision of S2-2300533r04. Approved Agreed
9.23.2 S2-2300543 CR Approval 23.288 CR0641 (Rel-18, 'B'): ML model storage and retrieval via ADRF China Unicom Rel-18 r08 agreed. Revised to S2-2301995. Chi (China Unicom) provides r01 with S2-2300282 merged in, which following the rapporteur's proposal.
Bahador (NTT DOCOMO) provides comments regarding the output of Nadrf_MLModelManagement_RetrievalRequest
Chi (China Unicom) replies to Bahador (NTT DOCOMO).
Bahador (NTT DOCOMO) replies to Chi (China Unicom) and provides r02
Fabio (Nokia) provides comments about retrieving ML Models from ADRF
Megha(Intel) provides comments
Bahador (NTT DOCOMO) provides r03 and asks Fabio (Nokia) for clarification
Chi (China Unicom) provides r04 and replies to Megha (Intel), Bahador (NTT DOCOMO) and Fabio (Nokia).
Fabio (Nokia) replies to Bahador (NTT DOCOMO).
Fabio (Nokia) provides comments to r04.
Wang Yuan (Huawei) provides comments.
Bahador (NTT DOCOMO) provides comments and r05
Costas (Lenovo) provides comments to Bahador
Bahador (NTT DOCOMO) replies to Costas (Lenovo)
Chi (China Unicom) provides r06 and replies.
Bahador (NTT DOCOMO) requests for clarification.
Chi (China Unicom) replies to Bahador (NTT DOCOMO) and provides r07.
Chi (China Unicom) provides r08.
==== Revisions Deadline ====
Megha (Intel) is ok with r08.
Wang Yuan (Huawei) is OK with r08.
Zhang (Ericsson) is OK with r08
Fabio (Nokia) is OK with r08.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301995 CR Approval 23.288 CR0641R1 (Rel-18, 'B'): ML model storage and retrieval via ADRF China Unicom, Lenovo Mobile Com. Technology, Intel Rel-18 Revision of S2-2300543r08. Approved Agreed
9.23.2 S2-2300669 CR Approval 23.288 CR0645 (Rel-18, 'B'): KI#4 Optimization on the collection and reporting of network data China Mobile Rel-18 Confirm Specification Number - CR states 23.501! Noted Aihua(CMCC) provides r01.
Zhang (Ericsson) provides r02
Antoine (Orange) comments.
Aihua(CMCC) replies to Antoine (Orange) and Zhang (Ericsson) .
Antoine (Orange) comments that this feature should be better described.
Fabio (Nokia) provides r03.
Antoine (Orange): r03 does not solve my concerns. We need a clearer description for the TS. If we can't do it during this meeting I suggest postponing this CR.
Aihua(CMCC) replies to Antoine (Orange) and provides r04.
==== Revisions Deadline ====
Aihua(CMCC) replies to Antoine (Orange), suggesting to approve r04 approved.
Antoine (Orange) objects to all versions.
==== Final Comments Deadline ====
Noted
9.23.2 S2-2301001 CR Approval 23.288 CR0669 (Rel-18, 'C'): Optimizing data collection and storage by NWDAF registration in UDM for all Analytics IDs Orange Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 S2-2301271 CR Approval 23.288 CR0690 (Rel-18, 'C'): Data storage in ADRF using DataSetTag. Nokia, Nokia Shanghai Bell Rel-18 Approved Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments on r00.
Costas (Lenovo) question for clarification.
Zhang (Ericsson) comment to Fabio
Fabio (Nokia) replies to comments about multiple Tags.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 S2-2301274 CR Approval 23.288 CR0693 (Rel-18, 'C'): Data Storage Management Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2301996. Zhang (Ericsson) provides comments
Fabio (Nokia) replies to comments from Zhang (Ericsson).
Zhang (Ericsson) response to Fabio (Nokia)
Fabio (Nokia) provides r01
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r01
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301996 CR Approval 23.288 CR0693R1 (Rel-18, 'C'): Data Storage Management Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2301274r01. Approved Agreed
9.23.2 S2-2301275 CR Approval 23.502 CR3864 (Rel-18, 'C'): Managing of Event Muting Impact on NFp Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 - - - Key Issue #5: Enhance trained ML Model sharing - - Docs:=7 -
9.23.2 S2-2300114 CR Approval 23.288 CR0602 (Rel-18, 'F'): Update ML model provisioning service with Interoperability Information Ericsson Rel-18 r01 agreed. Revised to S2-2301997. Fabio (Nokia) provides editorial comments
Zhang (Ericsson) provide r01
Fabio (Nokia) is OK with r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301997 CR Approval 23.288 CR0602R1 (Rel-18, 'F'): Update ML model provisioning service with Interoperability Information Ericsson Rel-18 Revision of S2-2300114r01. Approved Agreed
9.23.2 S2-2300524 CR Approval 23.501 CR3926 (Rel-18, 'B'): TS 23.501 enhancements for model sharing. Vivo Rel-18 r01 agreed. Revised to S2-2301998. Zhang (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301998 CR Approval 23.501 CR3926R1 (Rel-18, 'B'): TS 23.501 enhancements for model sharing. Vivo Rel-18 Revision of S2-2300524r01. Approved Agreed
9.23.2 S2-2300526 CR Approval 23.288 CR0635 (Rel-18, 'B'): TS 23.288 enhancements for model sharing. Vivo Rel-18 r01 agreed. Revised to S2-2301999. Zhang (Ericsson) provides comments
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301999 CR Approval 23.288 CR0635R1 (Rel-18, 'B'): TS 23.288 enhancements for model sharing. Vivo Rel-18 Revision of S2-2300526r01. Approved Agreed
9.23.2 S2-2301132 CR Approval 23.502 CR3847 (Rel-18, 'B'): Support for ML Model Interoperability Indicator Resolve EN Intel Rel-18 Approved Fabio (Nokia) is OK with r00.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 - - - Key issue #6: NWDAF-assisted URSP - - Docs:=8 -
9.23.2 S2-2300124 CR Approval 23.288 CR0609 (Rel-18, 'B'): Service Experience Analytics ID Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 S2-2300379 CR Approval 23.288 CR0621 (Rel-18, 'B'): Add new parameters to Redundant Transmission Experience analytics Futurewei, Huawei, LG Electronics Rel-18 Postponed Jihoon (ETRI) provides comments with some question for clarification.
Belen (Ericsson) provides comments, thinks that this CR needs to reduce the scope.
Juan Zhang (Qualcomm) have strong concern of the CR.
Belen (Ericsson) agrees with QC that it needs to be clarified first whether PCF can trigger e2e redundancy
Abbas (Futurewei) responds Jihoon (ETRI) and provides r01
Abbas (Futurewei) responds Belen (Ericsson)
Abbas (Futurewei) responds Juan (Qualcomm) and Belen (Ericsson)
Thomas(Nokia) shares the concerns of Belen and Juan
Abbas (Futurewei) responds Thomas (Nokia)
Belen (Ericsson) objects to this CR, the scope is not correct.
Juan Zhang (Qualcomm) objects to this CR, it is not acceptable for the PCF to activate / deactivate the redundant PDU session.
Abbas (Futurewei) provides r02
Belen (Ericsson) responds that objections are to the CR any revision as the PCF does not instruct the UE to activate redundacy
==== Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to note the CR.
Juan Zhang (Qualcomm) proposes to postpone the CR in this meeting and try to find a compromise in next meeting after the offline discussion.
Abbas Kiani (Futurewei) is OK to postpone
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300401 CR Approval 23.503 CR0827 (Rel-18, 'F'): Correction and clarification on NWDAF assisted URSP LG Electronics Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 S2-2300895 CR Approval 23.288 CR0664 (Rel-18, 'B'): Procedures of NWDAF-assisted URSPs Vivo Rel-18 Noted Kenichi (KDDI) ask for clarification.
Jihoon (ETRI) provides comments.
Huazhang (vivo) reply to Jihoon that for now in 23.288, there is no paragraph to clearify the URSP rule assisted by NWDAF. All of the contents are seperately in other sections. It will be good to have a general words that to clarify the new features introduced in R18
Huazhang (vivo) thanks Kenichi and provide r01
Jihoon (ETRI) replies to Huazhang (vivo).
Kenichi (KDDI) fine with r01.
Belen (Ericsson) asks whether this description is not covered in 23.503.
Huazhang (vivo) reply to Belen
Jungshin (Samsung) provides comments.
Huazhang (vivo) provides r02 and reply to Jungshin
LaeYoung (LGE) does not think the addition by this CR is needed.
Huazhang (vivo) provide r03 to make the word simpler
Juan Zhang (Qualcomm) provides r04.
Thomas(Nokia) comments that CR is not required as similar information in TS 23.503 is already available and fits better in that specification.
Huazhang (vivo) provides r05 base on r04 to reduce more words that want to keep a section to declear the new features that R18 introduce
LaeYoung (LGE) still thinks this CR is NOT needed.
Belen (Ericsson) objects to this CR, asks to move the table to 23.503
==== Revisions Deadline ====
Kenichi (KDDI) has a same view LaeYoung (LGE) and Belen (Ericsson) .
==== Final Comments Deadline ====
Noted
9.23.2 S2-2301012 CR Approval 23.503 CR0875 (Rel-18, 'C'): Update on NWDAF-assisted URSP ETRI Rel-18 r03 agreed. Revised to S2-2302000. LaeYoung (LGE) comments.
Jihoon (ETRI) replies to LaeYoung (LGE).
LaeYoung (LGE) replies to Jihoon (ETRI).
Huazhang (vivo) reply to Jihoon and LaeYoung
LaeYoung (LGE) responds to Jihoon (ETRI).
LaeYoung (LGE) responds to Huazhang (vivo).
Jihoon (ETRI) replies to Huazhang (vivo) and LaeYoung (LGE).
LaeYoung (LGE) answers to Jihoon (ETRI).
Jihoon (ETRI) provides r01.
LaeYoung (LGE) comments on r01.
Jihoon (ETRI) provides r02 on top of r01 considering the received comment.
Belen (Ericsson) asks a question
LaeYoung (LGE) comments on r02.
==== Revisions Deadline ====
Jihoon (ETRI) provides r03.
LaeYoung (LGE) is fine with r03.
Jihoon (ETRI) thanks LaeYoung (LGE) for the support.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302000 CR Approval 23.503 CR0875R1 (Rel-18, 'C'): Update on NWDAF-assisted URSP ETRI Rel-18 Revision of S2-2301012r03. Approved Agreed
9.23.2 S2-2301052 CR Approval 23.503 CR0880 (Rel-18, 'B'): Remove EN about NWDAF assisted URSP in TS23.503 China Telecom Rel-18 r06 agreed. Revised to S2-2302001. Jiahui (China Telecom) provide r01
Hyunsook (LGE) provides r02.
Jihoon (ETRI) provides comments.
Susan (Huawei) replies to Hyunsook (LGE) and provides r03.
Jiahui (China Telecom) replies to Jihoon (ETRI)
Juan Zhang (Qualcomm) provides r04.
Belen (Ericsson) objects to this CR, asks to postpone the discussion.
Belen (Ericsson) withdraws objection, provides r05
Jiahui (China Telecom) provides r06
Susan (Huawei) asks Juan Zhang (Qualcomm) to explain why she removed the behavior of PCF and UE.
Juan Zhang (Qualcomm) replies to Susan (Huawei).
==== Revisions Deadline ====
Susan (Huawei) replies to Juan Zhang (Qualcomm), and objects to r04, r05, r06.
Yannick (Convenor) asks if any version from r00 to r03 could be acceptable.
Juan Zhang (Qualcomm) objects r00-r03 which includes PCF and UE behaviour.
Jiahui (China Telecom) kindly asks Susan to consider withdrawing objection to r06 .
Susan (Huawei) objects to r00 and raises concern that Juan Zhang (Qualcomm) does not respect the conclusion of the TR, and didn't provide valid argumentation for her objection, and asks discussion on CC#3 or CC#4, to move forward with r01, r02 or r03.
Juan Zhang (Qualcomm) does not agree Susan's comments that I did not provide valid argumentation.
Susan (Huawei) replies to Jiahui (China Telecom) and withdraw her objection to r06.
Jiahui (China Telecom) is ok with r06 .
Susan (Huawei) replies to Juan Zhang (Qualcomm).
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302001 CR Approval 23.503 CR0880R1 (Rel-18, 'B'): Remove EN about NWDAF assisted URSP in TS23.503 China Telecom Rel-18 Revision of S2-2301052r06. Approved Agreed
9.23.2 - - - Key Issue #7: Enhancements on QoS Sustainability analytics - - Docs:=3 -
9.23.2 S2-2300450 CR Approval 23.288 CR0631 (Rel-18, 'B'): QoS sustainability analytics with fine granularity enhancement China Mobile Rel-18 r08 agreed. Revised to S2-2301459. Aihua(CMCC) provides r01.
Fabio (Nokia) provides comments to r01
Jaewoo (LGE) provides r02.
Aihua(CMCC) provides r03
Fabio (Nokia) provides comments to r03
Aihua(CMCC) provides r04
Juan Zhang (Qualcomm) provides r05
Belen (Ericsson) provides r06, cannot accept previous revisions.
Juan Zhang (Qualcomm) provides r07.
Jaewoo (LGE) asks a question to Aihua (CMCC).
Aihua(CMCC) replies to Jaewoo (LGE).
Jaewoo (LGE) provides r08.
==== Revisions Deadline ====
Susan (Huawei) replies to Belen (Ericsson) and Juan Zhang (Qualcomm).
Juan Zhang (Qualcomm) is OK with r08.
Juan Zhang (Qualcomm) replies to Susan (Huawei).
Susan (Huawei) replies to Juan Zhang (Qualcomm).
Belen (Ericsson) asks to remove 'In such scenario, a warning message is provided in the response or notification to the NF consumer.' In r08.
Aihua(CMCC) is fine to remove it in r04, and request for CC#4.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301459 CR Approval 23.288 CR0631R1 (Rel-18, 'B'): QoS sustainability analytics with fine granularity enhancement China Mobile Rel-18 Revision of S2-2300450r08. Approved Agreed
9.23.2 S2-2300466 CR Approval 23.288 CR0633 (Rel-18, 'B'): Enhancements on QoS Sustainability analytics LG Electronics, Orange Rel-18 Postponed Aihua(CMCC) comment.
Jihoon (ETRI) provides comments.
Kenichi (KDDI) ask for clarification.
Jaewoo (LGE) responds to Aihua(CMCC).
Jaewoo (LGE) responds to Kenichi (KDDI).
Kenichi (KDDI) fine with the proposed text.
Fabio (Nokia) provides comments.
Antoine (Orange) replies to Aihua that SMF discovery is already specified in clause 6.2.2.1.
Antoine (Orange) replies to Fabio.
Jaewoo (LGE) provides r01.
Fabio (Nokia) is OK with replies from Antoine (Orange).
Aihua (CMCC) provides r02.
Mirko (Huawei) comments and asks to clarify that the additions are only applicable for the 5QIs of non-GBR resource type.
Antoine (Orange) is not fully sure that the additions are only applicable for the 5QIs of non-GBR resource type.
Jaewoo (LGE) provides r03 and r04.
==== Revisions Deadline ====
Mirko (Huawei) objects to r04 and proposes to postpone this CR.
Jaewoo (LGE) is OK to postpone this CR.
Antoine (Orange) OK to postpone.
==== Final Comments Deadline ====
Postponed
9.23.2 - - - Key Issue #8: Supporting Federated Learning in 5GC - - Docs:=13 -
9.23.2 S2-2300116 CR Approval 23.288 CR0604 (Rel-18, 'B'): Support the Maintenance of Federated Learning Process in 5GC Ericsson Rel-18 r04 agreed. Revised to S2-2302002. Yaxin (OPPO) comments.
Zhang (Ericsson) response to Yaxin (OPPO)
Costas (Lenovo) comments.
Fabio (Nokia) provides comments.
Bahador (NTT DOCOMO) provides r01.
Vivian (vivo) provides comments.
Zhang (Ericsson) provides comments and r02
Costas (Lenovo) further comments on r03 and express concerns
Bahador (NTT DOCOMO) replies to Costas (Lenovo) and provides r04
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302002 CR Approval 23.288 CR0604R1 (Rel-18, 'B'): Support the Maintenance of Federated Learning Process in 5GC Ericsson Rel-18 Revision of S2-2300116r04. Approved Agreed
9.23.2 S2-2300117 CR Approval 23.288 CR0605 (Rel-18, 'B'): Support MTLF Discovery and Model Information Exchange for Federated Learning in 5GC Ericsson Rel-18 Postponed Soohwan (ETRI) asks questions for clarification and expresses concerns.
Zhang (Ericsson) response to Soohwan (ETRI)
Fabio (Nokia) provides comments.
Zhang (Ericsson) response to Fabio (Nokia)
Soohwan (ETRI) provides further comments.
Fabio (Nokia) replies to previous comments from Zhang (Ericsson)
Zhang (Ericsson) response to Fabio (Nokia) and Soohwan (ETRI)
Yannick (Convenor): To record that r01 was provided by Ericsson.
Dimitris (Lenovo) indicates that changes clash with changes in CR S2-2300445
Zhang (Ericsson) provide r02 to merge the general procedure into S2-2300445
==== Revisions Deadline ====
Soohwan (ETRI) proposes to postpone and provides further comments.
Megha(Intel) proposes to postpone the CR
Zhang (Ericsson) response to postpone the paper or SoH of 2300117 and 2300788
Dimitris (Lenovo) suggests to postpone
Zhang (Ericsson) confirm to postpone the paper
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300445 CR Approval 23.288 CR0628 (Rel-18, 'C'): Update for Federated Learning among Multiple NWDAFs in TS 23.288 China Mobile Rel-18 r14 agreed. Revised to S2-2301460. Yaxin (OPPO) comments.
Aihua(CMCC) replies and provides .
Aihua(CMCC) replies and provides r01.
Bahador (NTT DOCOMO) comments on exchanging model metrics and clarifies DOCOMO's CR
Zhang (Ericsson) provide r01 and comments
Jaewoo (LGE) provides comments.
Hyesung (Samsung) provides comments.
Yaxin (OPPO) provides r03 and comments.
Aihua(CMCC) replies to the comments.
Vivian (vivo) provides r04 on top of r03.
Aihua(CMCC) replies and provides r05.
Bahador (NTT DOCOMO) objects r05.
Dimitris (Lenovo) comments and does not agree to define analytics accuracy procedure in the general description for FL
Zhang (Ericsson) provides comment
Hyesung (Samsung) provides comments on r05.
Aihua(CMCC) replies and provides r06.
Aihua(CMCC) replies and provides r07.
Yaxin (OPPO) comments to r07.
Vivian (vivo) provides comments.
Yaxin (OPPO) provides r08 based on r07.
Aihua(CMCC) provides r09.
Hyesung (Samsung) provides r10.
Vivian(vivo) provides r11.
Aihua(CMCC) provides r12.
Juan Zhang (Qualcomm) provides comments on r12.
Yaxin (OPPO) replies.
Bahador (NTT DOCOMO) provides comments on r12
Aihua(CMCC) replies to Juan Zhang (Qualcomm) and provides r13.
Aihua(CMCC) provides r14.
Zhang (Ericsson) provide r15 and comments
Aihua (CMCC) provide r16.
==== Revisions Deadline ====
Soohwan (ETRI) objects to r15 and r16.
Megha(Intel) can accept r14 and provides comments
Hyesung (Samsung) is fine with r14.
Yaxin (OPPO) is fine with r14.
Dimitris (Lenovo) suggest to proceed with r14 with an additional EN regarding FL client discovery/selection
Juan Zhang (Qualcomm) is OK with r14.
Vivian (vivo) is OK with r14, please add vivo as co-signer.
Aihua(CMCC) replies to Dimitris (Lenovo) , suggesting not to add new EN.
Dimitris (Lenovo) comments on the need of the additional EN
Zhang (Ericsson) response to Dimitris and ask clarification
Aihua(CMCC) can live with r14 with new EN, and request for CC#4.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2301460 CR Approval 23.288 CR0628R1 (Rel-18, 'C'): Update for Federated Learning among Multiple NWDAFs in TS 23.288 China Mobile Rel-18 Revision of S2-2300445r14. Approved Agreed
9.23.2 S2-2300522 CR Approval 23.288 CR0634 (Rel-18, 'B'): Enhance NWDAF to enable Federated Learning Vivo Rel-18 r06 agreed. Revised to S2-2302003. Vivian (vivo) provides r01, removing changes for clause 5.2 and 6.2C and merging S2-2300592 .
Yaxin (OPPO) comments.
Zhang (Ericsson) provide r02 and comment
Vivian (vivo) replies to Zhang(Ericsson)comment
Vivian (vivo) replies to Yaxin (OPPO)'s comments and provides r03.
Yaxin (OPPO) provides r04 based on r03.
Vivian(vivo) replies to Yaxin (OPPO) and is fine with r04.
Vivian(vivo) provides r05 on top of r04, only removing some wrong clause references.
Zhang (Ericsson) provides comment to r05
Vivian (vivo) replies to Zhang (Ericsson) and provides r06.
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r06.
Zhang (Ericsson) is Ok with r06
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302003 CR Approval 23.288 CR0634R1 (Rel-18, 'B'): Enhance NWDAF to enable Federated Learning Vivo Rel-18 Revision of S2-2300522r06. Approved Agreed
9.23.2 S2-2300523 CR Approval 23.501 CR3925 (Rel-18, 'B'): TS 23.501 enhancements for federated learining. Vivo Rel-18 r04 agreed. Revised to S2-2302004. Dimitris (Lenovo) provides r01
Megha(Intel) raises concern on the proposal in the CR regarding FL capability for NWDAF selection
Vivian(vivo) replies to Dimitris (Lenovo) comments and provides r02.
Dimitris (Lenovo) responds to Vivian (Vivo)
Vivian (vivo) replies to Dimitris (Lenovo)'s comment
Zhang (Ericsson) provides r03 and comments
Vivian (vivo) provides r04.
Dimitris (Lenovo) prefers r02
Vivian (vivo) is OK with both r02 and r04, and asks if Zhang(Eriksson) can live with r02
Juan Zhang (Qualcomm) prefers r04.
Dimitris (Lenovo) indicates NWDAF containing MTLF already stores Data Sources available to NRF
Zhang (Ericsson) response to Dimitris (Lenovo)
Megha(Intel) provides r05 and comments
Vivian (vivo) is OK with r05.
Vivian (vivo) thanks Megha (Intel) for providing r06, and is OK with both r04(=r05, can be ignored) and r06.
Megha (Intel) provides r06 and comments
==== Revisions Deadline ====
Megha(Intel) is ok with r04.
Zhang (Ericsson) is OK with r04 and object all other versions
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302004 CR Approval 23.501 CR3925R1 (Rel-18, 'B'): TS 23.501 enhancements for federated learining. Vivo Rel-18 Revision of S2-2300523r04. Approved Agreed
9.23.2 S2-2300788 CR Approval 23.288 CR0574R1 (Rel-18, 'B'): KI#8: Addition of Nnwdaf_MLModelTraining service ETRI Rel-18 Revision of S2-2210557. Postponed Zhang (Ericsson) provides comments
Soohwan (ETRI) provides r01.
Zhang (Ericsson) response to Soohwan (ETRI)
==== Revisions Deadline ====
Soohwan (ETRI) proposes to postpone.
Megha(Intel) supports r01 but also ok to postpone this CR for next meeting.
Zhang (Ericsson) response to postpone the paper or SoH of 2300117 and 2300788
Zhang (Ericsson) propose to postpone the paper
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300789 DISCUSSION Agreement KI#8: Discussion on services enabling FL. ETRI Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300943 CR Approval 23.288 CR0666 (Rel-18, 'B'): NWDAF discovery and selection for an NWDAF supporting MTLF with FL capability Lenovo, Rel-18 Postponed Vivian (vivo) provides r01 .
Dimitris (Lenovo) responds to Vivian (Vivo)
Zhang (Ericsson) provides comment to r01
Vivian(vivo) replies to Dimitris (Lenovo) and Zhang(Ericsson)'s comments
Dimitris (Lenovo) provides responses
Zhang (Ericsson) provide r02 and comments
Dimitris (Lenovo) objects to r02
Juan Zhang (Qualcomm) prefers r02.
Dimitris (Lenovo) comments that this definition is already in normative specs
Zhang (Ericsson) response to Dimitris (Lenovo)
Dimitris (Lenovo) responds to Zhang (Ericsson)
==== Revisions Deadline ====
Zhang (Ericsson) only accept r02 and object all other versions
Dimitris (Lenovo) objects r02
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2301120 CR Approval 23.501 CR4070 (Rel-18, 'B'): Discovery and selection of NWDAF with FL support Resolve EN Intel Rel-18 Approved Vivian (vivo) provides comments .
Yaxin (OPPO) agrees with Intel that the FL capability should be per analytics ID.
Megha(Intel) responds to the comments from Vivian(Vivo).
Vivian (vivo) replies to Megha (Intel)'s comments.
Fabio (Nokia) provides comments.
Juan Zhang (Qualcomm) provides comments.
Megha (Intel) responds to Vivian (vivo)
Vivian(vivo) is OK to go with the direction of making the FL capability per analytics ID
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 - - - Key Issue #9: Enhancement of NWDAF with finer granularity of location information - - Docs:=16 -
9.23.2 S2-2300211 CR Approval 23.288 CR0612 (Rel-18, 'B'): Key Issue #9: Analytic ID that supports location accuracy estimate Nokia, Nokia Shanghai-Bell Rel-18 Check Affected Clauses! Add revision marks! r06 agreed. Revised to S2-2302005. Dimitris (Lenovo) has concerns with including input data as part of an analytics request
Kenichi (KDDI) ask for clarification.
Amy (vivo) provides comments
Dimitris (Lenovo) suggests to take 785 as the basis for the procedure
Kenichi (KDDI) prefer to 785 as the baseline.
Thomas(Nokia) replies to comments and objects against taking 785 as basis
Dimitris (Lenovo) responds
Amy (vivo) replies to Dimitris and Thomas, and asks for a revision
Thomas(Nokia) replies to Amy and Dimitris and provides r01
Kenichi (KDDI) provides r02.
Thomas(Nokia) is fine with r02.
Wang Yuan (Huawei) provides r03.
Amy (vivo) still has concerns about how this analytics works
Dimitris (Lenovo) provides r04 objects to previous versions
Amy (vivo) provides r05 based on r04
Amy (vivo) copy paste missing comments and remind Thomas to have a look at r05, as provided based on Dimitris' r04.
Thomas(Nokia) provides r06, objects against r04 and r05
Dimitris (Lenovo) can live with r06
==== Revisions Deadline ====
Amy (vivo) can live with r06
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302005 CR Approval 23.288 CR0612R1 (Rel-18, 'B'): Key Issue #9: Analytic ID that supports location accuracy estimate Nokia, Nokia Shanghai-Bell, Lenovo Rel-18 Revision of S2-2300211r06. Approved Agreed
9.23.2 S2-2300238 CR Approval 23.228 CR1258 (Rel-18, 'B'): Support of PSAP resolution with NWDAF Rakuten Mobile Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.23.2 S2-2300239 DISCUSSION Discussion Discussion on PSAP resolution with UE mobility analytics. Rakuten Mobile Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300240 CR Approval 23.288 CR0615 (Rel-18, 'B'): UE Mobility analytics enhancement for PSAP Rakuten Mobile Rel-18 Confirm Spec version used - CR states 17.6.0! Postponed Amy (vivo) provides comments and suggestions
Antoine (Orange) comments.
Bahador (NTT DOCOMO) requests for clarification about 'current cell'
Aoken (Rakuten Mobile) responds to Amy (vivo), Antoine (Orange) and Bahador (NTT DOCOMO) and provides r01
Costas (Lenovo) comments.
Aoken responds to Costas (Lenovo) and provides r02.
Kenichi (KDDI) comments Geographical Identifier.
Aoken(Rakuten Mobile) responds to Kenichi (KDDI). Need to correct the reference spec to 23.228
Amy (vivo) provides further comments
Aoken(Rakuten Mobile) responds to Amy (vivo)
Kenichi ask for clarification.
Aoken (Rakuten Mobile ) answers to Kenichi (KDDI)
Kenichi (KDDI) responses to Aoken (Rakuten Mobile)
Thomas(Nokia) provides r03.
Aoken (Rakuten Mobile) provides r04.
Kenichi (KDDI) prefer r03 with additional comments.
Aoken (Rakuten Mobile) answers to the additional comments from Kenichi (KDDI) and provides r05
Antoine (Orange) proposes to postpone this CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.23.2 S2-2300695 CR Approval 23.288 CR0646 (Rel-18, 'B'): NWDAF data collection from LCS system Vivo Rel-18 Check Affected Clauses! r03 agreed. Revised to S2-2302006. Amy (vivo) provides r01 based on the rapporteur's proposal
Manmeet (Rakuten) agrees to merge first change of S2-2300107 into S2-2300695r01 as suggested by Vivo.
Kenichi (KDDI) comments for r01.
Amy (vivo) replies to Kenichi
Kenichi (KDDI) fine with r02.
Thomas (Nokia) provides r03.
Amy (vivo) is ok with Thomas provided r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302006 CR Approval 23.288 CR0646R1 (Rel-18, 'B'): NWDAF data collection from LCS system Vivo, Rakuten Mobile Rel-18 Revision of S2-2300695r03. Approved Agreed
9.23.2 S2-2300696 CR Approval 23.288 CR0647 (Rel-18, 'B'): KI#9 NWDAF consumer enhancement about location service Vivo, Orange Rel-18 r06 agreed. Revised to S2-2302007. Dimitris (Lenovo) starts a thread to discuss how NWDAF requests finer granularity location info
Amy (vivo) provides comments
Thomas (Nokia) provides comments
Thomas (Nokia) provides other comments that require a revision
Antoine (Orange) replies.
Wang Yuan (Huawei) provides comments.
Amy (vivo) provides r01 and replies to Thomas, and asks Dimitris to review preferred granularity of location information
Thomas (Nokia) provides r02
Dimitris (Lenovo) comments that some changes in this CR clash with 0788 i.e. clause 6.7
Amy (vivo) provides r03 to delete EN about AOI and replies to Thomas and Dimitris
Thomas (Nokia) provides r04
Dimitris (Lenovo) provides r05 removing any clashes with 778 CR
Amy (vivo) provides r06 to include the preferred orientation of location information, and spatial granularity in UE mobility analytics.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302007 CR Approval 23.288 CR0647R1 (Rel-18, 'B'): Enhancements to Analytics Reporting Information and NWDAF output Vivo, Orange, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2300696r06. Approved Agreed
9.23.2 S2-2300771 CR Approval 23.288 CR0653 (Rel-18, 'B'): UE Mobility analytics enhancement Huawei, HiSilicon, Toyota Rel-18 r01 agreed. Revised to S2-2302008. Amy (vivo) provides comments
Wang Yuan (Huawei) responds to Amy (Vivo).
Yannick (Convenor): To record that r01 was provided by Huawei.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302008 CR Approval 23.288 CR0653R1 (Rel-18, 'B'): UE Mobility analytics enhancement Huawei, HiSilicon, Toyota Rel-18 Revision of S2-2300771r01. Approved Agreed
9.23.2 S2-2300744 CR Approval 23.288 CR0651 (Rel-18, 'B'): Relative Proximity Analytics Samsung Rel-18 r03 agreed. Revised to S2-2302009. Antoine (Orange) has a bunch of comments.
Amy (vivo) asks for clarifications
David (Samsung) provides r01, replies to comments from Orange and vivo.
Juan Zhang (Qualcomm) provides comments.
David (Samsung) provides r02, replies to Qualcomm.
Antoine (Orange) has further comments/questions.
Thomas(Nokia) (suggest additional improvements:.
Amy (vivo) asks for further clarifications on r02
David (Samsung) provides r03 and answers to comments
Juan Zhang (Qualcomm) replies to David.
==== Revisions Deadline ====
Thomas (Nokia) accepts r03 and answers to comments
Amy (vivo) accepts r03 and answers to comments
Juan Zhang (Qualcomm) is OK with r03.
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302009 CR Approval 23.288 CR0651R1 (Rel-18, 'B'): Relative Proximity Analytics Samsung Rel-18 Revision of S2-2300744r03. Approved Agreed
9.23.2 S2-2301226 LS OUT Approval [DRAFT] LS on DCAF Support for Relative Proximity Analytics in NWDAF Samsung Rel-18 Noted Juan Zhang (Qualcomm) provides comments.
==== Revisions Deadline ====
David (Samsung) confirms this LS can be noted since S2-2300744r03 seems approvable.
==== Final Comments Deadline ====
Noted
9.23.2 S2-2300778 CR Approval 23.288 CR0592R1 (Rel-18, 'B'): Enhancing location analytics with finer granularity location information Lenovo, Rel-18 Revision of S2-2210824. r06 agreed. Revised to S2-2302010. Antoine (Orange) provides a bunch of changes in r01.
Amy (vivo) provides comments
Dimitris (Lenovo) responds to Amy (Vivo)
Wang Yuan (Huawei) raises comments
Dimitris (Lenovo) responds to Wang Yuan (Huawei) and provides r02
Amy (vivo) provides r03 and clarifies the concerns
Dimitris (Lenovo) indicates that r02 is based on TR conclusions provides r04 taking into account contents of r03
Amy (vivo) still believes that r03 is not acceptable, several problems still exist
Amy (vivo) provides r05 and replies to Dimitris about what GMLC will provide to NWDAF as LCS location response
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302010 CR Approval 23.288 CR0592R2 (Rel-18, 'B'): Enhancing location analytics with finer granularity location information Lenovo, Rel-18 Revision of S2-2300778r06. Approved Agreed
9.23.2 - - - Key Issue #10: how NWDAF requests analytics from MDAS/MDAF - - Docs:=3 -
9.23.2 S2-2300444 CR Approval 23.288 CR0627 (Rel-18, 'A'): KI#10 NWDAF interaction with MDAS/MDAF in TS 23.288 China Mobile Rel-18 Where is the Rel-17 CR? r03 agreed. Revised to S2-2302011. Aihua(CMCC) provides r01.
Aihua(CMCC) provides r02.
Fabio (Nokia) provides editorial comments.
Aihua(CMCC) provides r03.
Costas(Lenovo) provides comments to r03.
Aihua(CMCC) provides comments to Constas.
Aihua(CMCC) replies to Constas.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.23.2 S2-2302011 CR Approval 23.288 CR0627R1 (Rel-18, 'B'): KI#10 NWDAF interaction with MDAS/MDAF in TS 23.288 China Mobile Rel-18 Revision of S2-2300444r03. Approved Agreed
9.23.2 S2-2300772 CR Approval 23.288 CR0654 (Rel-18, 'B'): Procedure for for analytics collection from MDAF Huawei, HiSilicon Rel-18 Postponed Wang Yuan (Huawei) provides r01 to merge S2-2300105 into S2-2300772.
Belen (Ericsson) provides r02
Wang Yuan (Huawei) is OK with r02.
Costas (Lenovo) replies to Yuan.
Wang Yuan (Huawei) reply to Costas (Lenovo) and provide r04.
==== Revisions Deadline ====
Wang Yuan (Huawei) asks Costas (Lenovo) whether there are any suggestion for way forward.
Costas (Lenovo) replies to we shall postpone this for the next meeting.
==== Final Comments Deadline ====
Postponed
9.23.2 - - - Documents exceeding TU Budget - - Docs:=54 -
9.23.2 S2-2300307 CR Approval 23.501 CR3764R1 (Rel-18, 'B'): Extension of NWDAF registration information to reflect new accuracy checking capability Huawei, HiSilicon Rel-18 Revision of S2-2210346 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300308 CR Approval 23.502 CR3606R1 (Rel-18, 'B'): Extension of NRF services for NWDAF registration to reflect new accuracy checking capability Huawei, HiSilicon Rel-18 Revision of S2-2210347 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300537 CR Approval 23.501 CR3930 (Rel-18, 'B'): NWDAF discovery enhancement for Analytics Models Accuracy Monitoring Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300538 CR Approval 23.502 CR3743 (Rel-18, 'B'): NRF service enhancements for Analytics Accuracy Monitoring Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300539 CR Approval 23.288 CR0638 (Rel-18, 'B'): Analytics Accuracy Monitoring procedures Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300540 CR Approval 23.288 CR0639 (Rel-18, 'B'): ML Models Accuracy Monitoring procedures Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300756 CR Approval 23.288 CR0585R1 (Rel-18, 'B'): Supporting Analytics Accuracy at the NWDAF - General Description Lenovo, Rel-18 Revision of S2-2210783 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300759 CR Approval 23.288 CR0586R1 (Rel-18, 'B'): Supporting Analytics Accuracy at the NWDAF - MTLF Description Lenovo Rel-18 Revision of S2-2210792 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300760 CR Approval 23.288 CR0587R1 (Rel-18, 'B'): Supporting Analytics Accuracy at the NWDAF - AnLF Description Lenovo, Rel-18 Revision of S2-2210795 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300786 CR Approval 23.288 CR0573R1 (Rel-18, 'B'): KI#1: Procedures to monitor ML model accuracy ETRI Rel-18 Revision of S2-2210555 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300842 CR Approval 23.288 CR0661 (Rel-18, 'B'): AnLF Analytics Accuracy Monitoring procedure China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301050 CR Approval 23.288 CR0674 (Rel-18, 'B'): Procedure for AnLF assisted MTLF in ML model accuracy monitoring China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301051 CR Approval 23.288 CR0675 (Rel-18, 'B'): New NWDAF service supporting for AnLF assisted MTLF in accuracy monitoring China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301166 CR Approval 23.288 CR0680 (Rel-18, 'B'): Procedure for AnLF-assisted ML model monitoring for analytics accuracy CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301167 CR Approval 23.288 CR0681 (Rel-18, 'B'): Service definition for analytics accuracy monitoring CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301273 CR Approval 23.288 CR0692 (Rel-18, 'C'): Input data in ML model provision services. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300443 CR Approval 23.288 CR0626 (Rel-18, 'B'): The procedure for PFD management via NEF (PFDF) based on PFD Determination analytics in TS23.502 China Mobile Rel-18 Confirm Specification Number - CR states 23.502! Should be 23.502 CR3871 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300453 CR Approval 23.288 CR0632 (Rel-18, 'B'): Update NWDAF-assisted PFD determination KDDI, China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300455 CR Approval 23.503 CR0832 (Rel-18, 'B'): Clarification on NWDAF-assisted PFD determination in TS23.503 KDDI, China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301285 CR Approval 23.288 CR0694 (Rel-18, 'C'): Update on PFD Determination analytics Samsung, SK Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301291 CR Approval 23.502 CR3868 (Rel-18, 'B'): Update NEF to support NWDAF-assisted application detection Samsung, SK Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300113 CR Approval 23.288 CR0601 (Rel-18, 'B'): Procedure of analytics and data collection in roaming scenario Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300631 CR Approval 23.288 CR0643 (Rel-18, 'B'): Network Data Analytics Exposure architecture in roaming case Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300773 CR Approval 23.288 CR0655 (Rel-18, 'B'): Analytics Exposure in roaming case Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301168 CR Approval 23.288 CR0682 (Rel-18, 'B'): Roaming architecture CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301170 CR Approval 23.288 CR0684 (Rel-18, 'B'): NWDAF discovery in roaming scenarios CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301172 CR Approval 23.502 CR3850 (Rel-18, 'B'): Using network analytics for roaming scenarios CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300282 CR Approval 23.288 CR0619 (Rel-18, 'B'): ML Model storage and retrieval from ADRF Lenovo Mobile Com. Technology Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300448 CR Approval 23.501 CR3905 (Rel-18, 'B'): DCCF Discovery principle enhancements for DCCF relocation in TS 23.501 China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301272 CR Approval 23.288 CR0691 (Rel-18, 'B'): DCCF relocation Nokia, Nokia Shanghai Bell Rel-18 Confirm Spec version used - CR states 18.0! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300525 CR Approval 23.502 CR3741 (Rel-18, 'B'): TS 23.502 enhancements for model sharing. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301134 CR Approval 23.288 CR0678 (Rel-18, 'B'): Update NWDAF Discovery and Selection procedure resolve EN Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300125 CR Approval 23.503 CR0797 (Rel-18, 'B'): Service Experience Analytics ID Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300402 CR Approval 23.288 CR0623 (Rel-18, 'F'): Clarification on enhanced OSE analytics LG Electronics Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300720 CR Approval 23.503 CR0847 (Rel-18, 'B'): NWDAF assisted decision on E2E redundant transmission Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300894 CR Approval 23.288 CR0663 (Rel-18, 'B'): Add application descriptor and connection capability into output of OSE Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300896 CR Approval 23.503 CR0865 (Rel-18, 'B'): Removing ENs about redundent transmission and multiple analytic Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300719 CR Approval 23.288 CR0649 (Rel-18, 'B'): QoS Sustainability enhancement Huawei, HiSilicon Rel-18 Not Handled Belen (Ericsson) provides r01, cannot accept the initial version
==== Revisions Deadline ====
Susan (Huawei) replies to Belen (Ericsson)
==== Final Comments Deadline ====
-
9.23.2 S2-2300147 CR Approval 23.288 CR0610 (Rel-18, 'B'): Federate Learning Procedure Enhancement for Accuracy and Member Selection NTT DOCOMO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300274 CR Approval 23.288 CR0617 (Rel-18, 'C'): Update of Federated Learning among Multiple NWDAFs OPPO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300275 CR Approval 23.502 CR3694 (Rel-18, 'C'): Update of NRF service for Federated Learning in 5GC OPPO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300276 CR Approval 23.501 CR3863 (Rel-18, 'C'): Update of NWDAF Discovery and Selection for FL in 5GC OPPO Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300592 CR Approval 23.288 CR0642 (Rel-18, 'F'): Definition of FL capability Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300594 CR Approval 23.501 CR3946 (Rel-18, 'F'): Definition of FL capability Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300598 CR Approval 23.502 CR3756 (Rel-18, 'F'): Definition of FL capability Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300632 CR Approval 23.288 CR0644 (Rel-18, 'B'): FL client NWDAF selection Samsung, SK Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300945 CR Approval 23.288 CR0667 (Rel-18, 'B'): Clarification of Federated Learning procedure at MTLF Lenovo, Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301135 CR Approval 23.288 CR0679 (Rel-18, 'B'): Procedure updates to support FL between NWDAFs containing MTLF Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300107 CR Approval 23.288 CR0599 (Rel-18, 'B'): Enhancement of NWDAF with finer granularity of location information using the Ngmlc services. Rakuten Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300406 CR Approval 23.288 CR0624 (Rel-18, 'B'): Enhancement of NWDAF with finer granularity of location information in Observed Service Experience Analytic ID Rakuten Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300785 CR Approval 23.288 CR0593R1 (Rel-18, 'B'): Supporting Location Accuracy Analytics Lenovo, Rel-18 Revision of S2-2210825 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300857 CR Approval 23.288 CR0662 (Rel-18, 'B'): New analytics ID for traffic flow use case Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2301004 CR Approval 23.288 CR0670 (Rel-18, 'B'): Enhancement of NWDAF with finer granularity of location information in Dispersion Analytics Rakuten Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.23.2 S2-2300105 CR Approval 23.288 CR0597 (Rel-18, 'B'): Procedure for requesting and collecting analytics from MDAF Lenovo Mobile Com. Technology Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.1 - - - Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) - - Docs:=9 -
9.24.1 S2-2301091 P-CR Approval 23.700-08: KI #4: Clarify selection of SNPN as a hosting network. Qualcomm Rel-18 r01 agreed. Revised to S2-2301434. Peter Hedman (Ericsson) provides comments/questions
Saso (Intel) comments on the assumption that 'the hosting network may have a higher priority than the subscribed SNPN'.
Yishan (Huawei) provides comments.
Guanzhou (InterDigital) ask questions for clarification.
Sebastian (Qualcomm)
Sebastian (Qualcomm) replies to Peter
Guanzhou (InterDigital) responds to Sebastian (Qualcomm).
Pallab (Nokia) comments
Peter Hedman (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.24.1 S2-2301434 P-CR Approval 23.700-08: KI #4: Clarify selection of SNPN as a hosting network. Qualcomm Rel-18 Revision of S2-2301091r01. Approved Approved
9.24.1 S2-2300368 P-CR Approval 23.700-08: KI#4: Update the conclusion. MediaTek Inc. Rel-18 r02 agreed. Revised to S2-2301435. Related to open EN Peter Hedman (Ericsson) provides comments
Chia-Lin (MediaTek) responds to Peter (Ericsson) and provides r01
Sebastian (Qualcomm) provides r02
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r02
Chia-Lin (MediaTek) is ok with r02
==== Final Comments Deadline ====
Revised
9.24.1 S2-2301435 P-CR Approval 23.700-08: KI#4: Update the conclusion. MediaTek Inc. Rel-18 Revision of S2-2300368r02. Approved Approved
9.24.1 S2-2300199 P-CR Approval 23.700-08: KI #4: Resolve open issue for additional information for manual selection. Ericsson Rel-18 r01 agreed. Revised to S2-2301436. Related to open EN Huan (vivo) asks for clarifications
Pallab (Nokia) provides comments
Yishan (Huawei) provides comments
Josep (DT) comments, similar view as other companies already expressed.
Peter Hedman (Ericsson) provides replies
Josep (DT) replies to Peter (Ericsson) regarding TD in URSP rules for conveying service availability information.
Guanzhou (InterDigital) ask questions for clarification.
Pallab (Nokia) responds to Peter (Ericsson) and provides r01
Josep (DT) supports the approach in r01.
Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides reply
Guanzhou (InterDigital) responds to Peter (Ericsson).
Yishan (Huawei) is ok with r01
Peter Hedman (Ericsson) provides reply i.e. as no support we can simply remove EN as in r01
Pallab (Nokia) responds to Peter Hedman (Ericsson)
==== Revisions Deadline ====
Chia-Lin (MediaTek) is ok with r01
Huan (vivo) is ok with r01
==== Final Comments Deadline ====
Revised
9.24.1 S2-2301436 P-CR Approval 23.700-08: KI #4: Resolve open issue for additional information for manual selection. Ericsson Rel-18 Revision of S2-2300199r01. Approved Approved
9.24.1 - - - Documents exceeding TU Budget - - Docs:=3 -
9.24.1 S2-2300977 P-CR Approval 23.700-08: 23.700-08: Conclusions update for KI#4, onboarding. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Under discussion with CRs Guanzhou (InterDigital) has sympathy on the proposed change.
Pallab (Nokia) proposes to take the discussion to 0978 as 0977 was marked as 'NOT HANDLED'
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.1 S2-2300506 P-CR Approval 23.700-08: KI#2: Conclusion update. CableLabs, Charter Rel-18 Not Handled Does not change the related note, i.e. better directly handled with a CR at Feb meeting as alignment between Rel18 WIs ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.1 S2-2300201 P-CR Approval 23.700-08: KI#2: Resolve issue with same credentials for access to SNPN with NG-RAN and to WLAN Access Network. Ericsson Rel-18 Not Handled Proposes aspect out of SA2 scope, i.e. will not be part of CR, but could be addressed by the LS out below. ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.2 - - - Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) - - Docs:=49 -
9.24.2 - - - General - - Docs:=8 -
9.24.2 S2-2300026 LS In Action LS from CT WG1: Reply LS on the progress and open issues for NPN enhancements in Rel-18 CT WG1 (C1-227157) Rel-18 Noted Peter Hedman (Ericsson) proposes to note the LS Noted
9.24.2 S2-2300063 LS In Action LS from SA WG1: Reply LS on Progress and open issues for NPN enhancements in Rel-18 SA WG1 (S1-2235400) Rel-18 Postponed Postponed
9.24.2 S2-2300072 LS In Action LS from SA WG3: Reply LS on Progress and open issues for NPN enhancements in Rel-18 SA WG3 (S3-224175) Rel-18 Responses drafted in S2-2300172, S2-2300200. Postponed Postponed
9.24.2 S2-2300172 LS OUT Approval [DRAFT] Reply LS on Progress and open issues for NPN enhancements in Rel-18 Qualcomm Rel-18 Response to S2-2300072. Postponed Peter Hedman (Ericsson) provides r01
Saso (Intel) provides r02
Yishan (Huawei) comments
Rainer (Nokia) provides r03.
Haris(Qualcomm) objects to r01, r02 and r03
Saso (Intel) replies to Haris
Peter Hedman (Ericsson) provides r04
Saso (Intel) provides r05
Haris(Qualcomm) comments that r05 is not acceptable
==== Revisions Deadline ====
Haris(Qualcomm) objects to r04
Yishan (Huawei) proposes to postpone this LS
Rainer (Nokia) is ok to postpone.
Peter Hedman (Ericsson) Seems hard to find any agreeable wording i.e. postpone is ok
==== Final Comments Deadline ====
Postponed
9.24.2 S2-2300171 CR Approval 23.501 CR3835 (Rel-18, 'C'): Support for NSWO with CH Qualcomm Incorporated, Intel, Lenovo, Nokia, Nokia Shanghai Bell Rel-18 Postponed Peter Hedman (Ericsson) provides comments/questions
Haris(Qualcomm) responds
Omkar (CableLabs) supports the CR and provides r01
Yishan (Huawei) provides comments
Saso (Intel) points out that the proposed change in r01 is out of scope for this CR.
Peter Hedman (Ericsson) provides r02
Saso (Intel) comments that r02 is incomplete.
Haris(Qualcomm) objects on r02
Haris(Qualcomm) agrees to postpone the CR and LS (as commented in other thread)
Rainer (Nokia) is ok to postpone 0171.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.24.2 S2-2300200 LS OUT Approval [DRAFT] LS on UE using same credentials for access to SNPN with NG-RAN and to WLAN Access Network Ericsson Rel-18 Response to S2-2300072. Postponed To be merged into S2-2300172 (Postponed) Yishan (Huawei) prefer to take 0200 as basis for the LS reply to SA3
Haris(Qualcomm) indicates that the content of this LS is not agreeable
Peter Hedman (Ericsson) ok to use 00172 as basis
==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
9.24.2 S2-2300198 LS OUT Approval [DRAFT] LS on RAN impact for NPN enhancement in Rel-18 Ericsson Rel-18 r00 agreed. Revised to S2-2301437. ==== Revisions Deadline ====
Sebastian (Qualcomm) is ok with r00; just one editorial comment: SA2#156 meeting is now an e-meeting (not TBD)
Peter Hedman (Ericsson) provides comment that LS out needs a revised number to cleanup
Rainer (Nokia) is ok with the LS.
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301437 LS OUT Approval LS on RAN impact for NPN enhancement in Rel-18 SA WG2 Rel-18 Revision of S2-2300198r00. Approved Approved
9.24.2 - - - KI#1 - - Docs:=1 -
9.24.2 S2-2300963 CR Approval 23.501 CR4024 (Rel-18, 'F'): Equivalent SNPN support Samsung Rel-18 Noted Rainer (Nokia) asks for clarification.
Peter Hedman (Ericsson) provides r01 and comment
Haris(Qualcomm) comments
Fei (OPPO) comments.
Chia-Lin (MediaTek) provides comments
Myungjune (LGE) comments.
Peter Hedman (Ericsson) provides comments
Saso (Intel) supports the views that Equivalent (home)/(subscribed) SNPN is not part of the study conclusions. Proposes to NOTE.
Rainer (Nokia) agrees to note the CR.
Kisuk (Samsung) notes this CR.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.24.2 - - - KI#2 - - Docs:=4 -
9.24.2 S2-2300101 CR Approval 23.501 CR3821 (Rel-18, 'B'): N5CW device access to SNPN services Intel, Nokia, Nokia Shanghai Bell Rel-18 Approved Yishan (Huawei) asks for clarification
Saso (Intel) replies to Yishan (Huawei)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.24.2 S2-2300195 CR Approval 23.501 CR3841 (Rel-18, 'B'): Clarification of SNPN access mode Ericsson Rel-18 Approved Yildirim (Charter) provides questions.
Chia-Lin (MediaTek) provides comments and think we can keep re-using the existing definition of SNPN access mode
Saso (Intel) supports the contribution and comments
Peter Hedman (Ericsson) provides comments
Yildirim (Charter) provides comments
Chia-Lin (MediaTek) provides r01
Saso (Intel) objects to r01
Peter Hedman (Ericsson) provides comments that we need to maintain the per instance aspect
==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.24.2 S2-2301147 CR Approval 23.316 CR2076 (Rel-18, 'B'): Support of wireline access as access to SNPN Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2301438. Same subject as 23.501 CR, i.e. “moving” the related text Omkar (CableLabs) provides r01 and asks for clarification
Marco (Huawei) answer to Omkar (CableLabs)
Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides question
Omkar (CableLabs) responds to Marco (Huawei) and Peter (Ericsson)
Marco (Huawei) further comments
Huan (vivo) provides r02
Rainer (Nokia) provides r03.
Rainer (Nokia) replies.
Marco (Huawei) provide r04
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r04, and comments
Huan (vivo) ok with r04
Omkar (CableLabs) is ok r04.
Rainer (Nokia) is ok with r04.
Yildirim (Charter) is ok with r04.
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301438 CR Approval 23.316 CR2076R1 (Rel-18, 'B'): Support of wireline access as access to SNPN Huawei, HiSilicon Rel-18 Revision of S2-2301147r04. Approved Agreed
9.24.2 - - - WID objective 3a, 3b – Intro and OAM config - - Docs:=3 -
9.24.2 S2-2300981 CR Approval 23.501 CR4032 (Rel-18, 'F'): Update Definitions for Localized Service Samsung Rel-18 Merged into S2-2301439 CC agreed to not use hosting network… Peter Hedman (Ericsson) provides comments and propose to mark as merged into 00196.
Kisuk (Samsung) merges this CR into 00196.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300196 CR Approval 23.501 CR3842 (Rel-18, 'B'): Introduction to Localized Services Ericsson Rel-18 r03 agreed. Revised to S2-2301439, merging S2-2300981 Pallab (Nokia) comments and provides r01
Josep (DT) comments on r01 that normative text in an informative Annex is not OK.
Guanzhou (InterDigital) questions whether X.Y and X.Z should be informative.
Josep (DT) requests info regarding informative/normative for Annex X from Peter (rapporteur).
Pallab (Nokia) provides r02 to take care of the comment from Josep (DT)
Peter Hedman (Ericsson) provides r03 as to refer to other CRs in the ENs
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301439 CR Approval 23.501 CR3842R1 (Rel-18, 'B'): Introduction to Localized Services Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300196r03, merging S2-2300981. Approved Agreed
9.24.2 - - - WID objective 3c - onboarding - - Docs:=4 -
9.24.2 S2-2301121 CR Approval 23.501 CR4071 (Rel-18, 'B'): Support for using onborading for enabling access to hosting network Xiaomi Rel-18 Merged into S2-2301440 Haris(Qualcomm) provides r01
Jianning (Xiaomi) is ok with r01
Pallab (Nokia) proposes to go with the CR in tdoc 0978 and checks if this can be merged to 0978
Huan (vivo) suggests to merge 2301121 into 2300528
Jianning (Xiaomi) is ok to merge into 2300528
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300978 CR Approval 23.501 CR4029 (Rel-18, 'B'): UE onboarding using default credentials when hosting network acts as ON-SNPN Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301440 Peter Hedman (Ericsson) proposes that we use 00528
Pallab (Nokia) suggests that we do not merge this tdoc to 0528 yet. Based on the discussions in 0528, we could decide to either go with proposal in 0978 or 0528.
Haris(Qualcomm) comments on the proposal in 0978
Pallab (Nokia) responds to Haris(Qualcomm)
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300528 CR Approval 23.501 CR3927 (Rel-18, 'B'): Clarifications on Onboarding in SNPN supporting localized services Vivo, Ericsson Rel-18 r06 agreed. Revised to S2-2301440, merging S2-2301121 and S2-2300978 Pallab (Nokia) provides comments
Huan (vivo) provide feedback
Pallab (Nokia) responds to Huan (vivo)
Naman (Samsung) provides comments and r01
Pallab (Nokia) comments. Not able to open r01
Naman (Samsung) provides r02
Saso (Intel) seeks clarification on r02
Naman (Samsung) replies to Saso (Intel)
Peter Hedman (Ericsson) provides r0x
Saso (Intel) replies to Naman
Haris(Qualcomm) comments on r02
Guanzhou (InterDigital) comments.
Yishan (Huawei) provides comments.
Huan (vivo) provides r03
Pallab (Nokia) comments. Also wants to check if this can be merged to 0978
Naman (Samsung) replies and provides r04 on top of r02
Huan (vivo) comments on r04
Naman (Samsung) replies to Huan (Vivo)
Macro (Huawei) comments
Saso (Intel) replies to Haris(Qualcomm)
Peter Hedman (Ericsson) provides r05
Huan (vivo) provides r06
Guanzhou (InterDigital) questions r04/r05.
Huan (vivo) provides feedback
Guanzhou (InterDigital) responds to Huan(Vivo).
Pallab (Nokia) comments on r06.
Peter Hedman (Ericsson) provides comments
Naman (Samsung) replies to Guangzhou (Interdigital)
Haris(Qualcomm) provides comments
Peter Hedman (Ericsson) provides reply
Guanzhou (InterDigital) responds to Huan(Vivo) and proposes to postpone the CR.
==== Revisions Deadline ====
Guanzhou (InterDigital) responds to Peter (Ericsson).
Haris(Qualcomm) comments and responds to Guanzhou (Interdigital)
Guanzhou (InterDigital) asks Haris (Qualcomm) for further clarification.
Peter Hedman (Ericsson) provides comments and ok with r06.
Huan (vivo) is ok with r00, r03 and r06.
Saso (Intel) proposes to postpone.
Peter Hedman (Ericsson) provides reply to Saso
Saso (Intel) is OK with r06.
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301440 CR Approval 23.501 CR3927R1 (Rel-18, 'B'): Clarifications on Onboarding in SNPN supporting localized services Vivo, Ericsson Rel-18 Revision of S2-2300528r06, merging S2-2301121 and S2-2300978. Approved Agreed
9.24.2 - - - WID objective 3d - network selection WID objective 3e - SoR enhancements - - Docs:=19 -
9.24.2 S2-2301229 CR Approval 23.501 CR4097 (Rel-18, 'B'): UE configuration and network selection for localized service hosting network (PNI-NPN) InterDigital Rel-18 Postponed Chia-Lin (MediaTek) provides r01
Yishan (Huawei) would like to confirm whether 1229 is merged to 1294 or will be handled separately?
Sebastian (Qualcomm) provides r02
Peter Hedman (Ericsson) provides r03
Yishan (Huawei) asks for clarification.
Peter Hedman (Ericsson) provides comments
Sebastian (Qualcomm) replies and provides r04
Yishan (Huawei) provides r05
Chia-Lin (MediaTek) is ok with r05 and agreed with Yishan's suggestions
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r05
Sebastian (Qualcomm) can only accept r02 and r04; objects to other versions; can also be ok with r02 + EN 'Details of location validity are FFS'
Chia-Lin (MediaTek) can only accept r05
Peter Hedman (Ericsson) propose to agree r05 + EN 'Location validity information is FFS'
Sebastian (Qualcomm) objects to agree r05 + EN 'Location validity information is FFS'
==== Final Comments Deadline ====
Postponed
9.24.2 S2-2301294 CR Approval 23.501 CR4106 (Rel-18, 'B'): Common enhancements on Allowed CAG list for VMR and PNI-NPN Qualcomm Incorporated Rel-18 Postponed Yishan (Huawei) asks for clarifications
Chia-Lin (MediaTek) provides comments
Josep (DT) comments, has some preference for a simpler solution.
Sebastian (Qualcomm) replies to Chia-Lin
Sebastian (Qualcomm) provides r01
Peter Hedman (Ericsson) provides r02
Chia-Lin (MediaTek) provides response to Sebastian (Qualcomm)
Yishan (Huawei) provides comments
Peter Hedman (Ericsson) provides comments
Sebastian (Qualcomm) provides r03
Yishan (Huawei) provides r04
Peter Hedman (Ericsson) provides comments and r05
==== Revisions Deadline ====
Yishan (Huawei) provides comments to r05
Peter Hedman (Ericsson) propose to approve r05 + remove 'and location restriction'
Josep (DT) is OK with (a revision based on) r05. Would like to co-sign.
Yishan (Huawei) is ok with r05 + remove 'and location restriction'
Chia-Lin (MediaTek) can only accept r05
Sebastian (Qualcomm) can only accept r01 and r03; objects to other versions
Peter Hedman (Ericsson) propose to approve r05 + remove 'and location restriction', + add EN 'Details how to support location validity is FFS', +
Sebastian (Qualcomm) prefers to rediscuss the overall CR next time, objects to Peter's proposal, i.e., objects to r05 + remove 'and location restriction', + add EN 'Details how to support location validity is FFS',)
==== Final Comments Deadline ====
Postponed
9.24.2 S2-2301133 CR Approval 23.501 CR4074 (Rel-18, 'C'): Selection of SNPN as a hosting network Qualcomm Incorporated Rel-18 Merged into S2-2301443 Clause 5.30.2.3, 5.30.2.4.1, 5.30.2.4.2. NW selection lists with validity and also new selection logic, two options (i.e. one to be removed). Overlaps with 00980, 01122, 01223, 00875, 00979, 00369, 00637, 00874 Guanzhou (InterDigital) asks questions for clarification.
Sebastian (Qualcomm): can be marked merged with 0369
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2301109 DISCUSSION Information Information for automatic hosting network selection. InterDigital, Inc. Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.24.2 S2-2301223 CR Approval 23.501 CR4096 (Rel-18, 'B'): UE configuration and network selection for localized service hosting network (SNPN) InterDigital Rel-18 Merged into S2-2301443 Clause 5.30.2.3, 5.30.2.4.1, 5.30.2.4.2. . Overlaps with 00980, 01122, 01133, 00875, 00979, 00369, 00637, 00874 Pallab (Nokia) checks if this can be merged to 0369
Sebastian (Qualcomm) also suggests to merge with 0369
Guanzhou (InterDigital) don't think this should be merged.
Sebastian (Qualcomm) suggests to merge the paper into 0369 as 0369 has more details
Yishan (Huawei) provides comments
Huan (vivo) provides comments
Guanzhou (InterDigital) replies to Huan (Vivo) and Yishan (Huawei)
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2301148 LS OUT Approval [DRAFT] LS Regarding Hosting Network selection for Localized services Samsung Rel-18 r04 agreed. Revised to S2-2301441. Chia-Lin (MediaTek) considers this LS is not needed based on TR conclusion for KI#4
Yishan (Huawei) suggests to keep this LS and asks feedback from CT1
Sebastian (Qualcomm) objects to r00; needs to be updated based on meeting progress
Naman (Samsung) provides r01
Josep (DT) comments, points out that r01 was uploaded with a wrong file name.
Pallab (Nokia) comments
Naman (Samsung) provides r02
Yishan (Huawei) provides r03
Sebastian (Qualcomm) provides r04
==== Revisions Deadline ====
Naman (Samsung) comments on r03/r04; prefers r04 + 'optional validity conditions'
Yishan (Huawei) provides comments
Peter Hedman (Ericsson) ok with r04, also ok with r04 + replace 'time and location validity conditions' with 'optional validity conditions (e.g. time)', + add 'optional' twice in question
Yishan (Huawei) has concerns with r04 but is ok with r04+ wording suggestion from Peter (Ericsson)
Naman (Samsung) is ok with r04 + changes proposed by Peter (Ericsson); would prefer to have 'Steering to Hosting Networks' also added to the LS but can live without those changes
Sebastian (Qualcomm) ok with r04 + 'optional validity conditions' as proposed by Naman (Samsung); objects to proposal by Peter (objects to replace 'time and location validity conditions')
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301441 LS OUT Approval Regarding issues related to SNPN selection for Localized services SA WG2 Rel-18 Revision of S2-2301148r04. Approved Approved
9.24.2 S2-2301221 CR Approval 23.501 CR4095 (Rel-18, 'B'): SNPN broadcast system information and manual network selection for localized service InterDigital Rel-18 r04 agreed. Revised to S2-2301442. Clause 5.30.2.2, 5.30.2.4.3. LS inf in SIB (RAN impacts noted, but none?), manual selection (added sentence no change of logic…). Pallab (Nokia) provides comments
Chia-Lin (MediaTek) provides r01
Yishan (Huawei) provides comments
Saso (intel) agrees with Yishan (Huawei) that the first change is not needed (BTW it uses a 'may' in a NOTE).
Peter Hedman (Ericsson) provides r02
Yishan (Huawei) asks for clarifications
Guanzhou (InterDigital) is OK with r02.
Naman (Samsung) provides r03
Josep (DT) comments, provides r04.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r04
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301442 CR Approval 23.501 CR4095R1 (Rel-18, 'B'): SNPN broadcast system information and manual network selection for localized service InterDigital, Samsung Rel-18 Revision of S2-2301221r04. Approved Agreed
9.24.2 S2-2300875 CR Approval 23.501 CR4007 (Rel-18, 'B'): Selection of hosting network providing access to localized services CATT Rel-18 Merged into S2-2301443 Clause 5.30.2.3, 5.30.2.4.2, 5.30.2.4.3, 5.30.3.2, 5.30.3.3. Time validity info, application layer input for manual selection, …. Overlaps with 00980, 01122, 01133, 01223, 00979, 00369, 00637, 00874. Liping Wu (CATT) agrees to merge S2-2300875 into S2-2300369.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300979 CR Approval 23.501 CR4030 (Rel-18, 'B'): SNPN selection with time validity information Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301443 Clause 5.30.2.3, 5.30.2.4.2, 5.30.2.4.3. Time validity, logic for auto selection. Overlaps with 00980, 01122, 01133, 01223, 00875, 00369, 00637, 00874. Sebastian (Qualcomm) proposes to mark merged into 0369
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300369 CR Approval 23.501 CR3883 (Rel-18, 'B'): UE discover, select and access to a Hosting network for Localized services MediaTek Inc. Rel-18 r20 agreed. Revised to S2-2301443, merging S2-2301133, S2-2301223, S2-2300875, S2-2300979, S2-2300637 and S2-2300874 Clause 5.4.4a, 5.30.2.3, 5.30.2.4, 5.30.2.4.2, 5.30.2.5, 5.30.3.3. New UE capability for PNINPN, time validity, LS access mode, uses hosting nw, . Overlaps with 00980, 01133, 01223, 00875, 00979, 01122, 00637, 00874. Liping Wu (CATT) provides r01 to merge S2-2300874 and S2-2300875 into S2-2300369.
Liping Wu (CATT) provides comments and asks for clarification.
Huan (vivo) asks for clarifications
Josep (DT) comments regarding PNI-NPN.
Chia-Lin (MediaTek) responds to Huan (vivo) and Liping (CATT) and provides r02
Yishan (Huawei) provides comments
Guanzhou (InterDigital) asks question for clarification.
Chia-Lin (MediaTek) responds to Josep (DT)
Chia-Lin (MediaTek) responds to Yishan (Huawei) and Guanzhou and provides r03
Myungjune (LGE) comments.
Chia-Lin (MediaTek) responds to Myungjune (LGE) and provides r04
Pallab (Nokia) comments and provides r05
Pallab (Nokia) now provides the link to r05
Yishan (Huawei) provides comments and r06
Pallab (Nokia) provides comments. Do not agree with the change in r06
Chia-Lin (MediaTek) provides comments and r07
Yishan (Huawei) replies to Pallab (Nokia)
Sebastian (Qualcomm) replies and provide r08
Naman (Samsung) seeks clarifications
Sebastian (Qualcomm) replies to Naman
Pallab (Nokia) provides r09
Peter Hedman (Ericsson) provides r10
Chia-Lin (MediaTek) responds to Pallab (Nokia)
Guanzhou (InterDigital) provides r11 and thinks implied new access mode needs further clarification.
Amanda Xiang ( Futurewei ) provides r12
Myungjune (LGE) provides r13
Chia-Lin (MediaTek) provides r14
Naman (Samsung) provides r15
Yishan (Huawei) asks questions
Chia-Lin (MediaTek) responds to Yishan (Huawei) and provides r16
Pallab (Nokia) provides r17
Peter Hedman (Ericsson) provides r18
Guanzhou (InterDigital) provides r19 and co-signed.
Sebastian (Qualcomm) provides r20
==== Revisions Deadline ====
Naman (Samsung) asks question to Sebastian (Qualcomm) regarding the added text in r20
Pallab (Nokia) agreed with the previous comment from Naman (Samsung) Proposes to approve r20 with below change:
Change 'The UE shall check regularly if SNPNs for which a validity condition is valid become available.' To
'If the UE supports accessing an SNPN providing access for Localized services and the end user enables to access Localized services the UE shall check regularly if SNPNs for which a validity condition is valid become available.'
Peter Hedman (Ericsson) provides comments and ok with r20 + 'If the UE supports accessing an SNPN providing access for Localized services and the end user enables to access Localized services'
Chia-Lin (MediaTek) is ok with r20 and also with the additional sentence suggested by Pallab (Nokia) in r20
Yishan (Huawei) is ok with r20 + the additional sentence suggested by Pallab (Nokia) for r20
Guanzhou (InterDigital) is OK with r20.
Naman (Samsung) is OK ONLY with r20 + addition suggested by Pallab (Nokia) / Peter (Ericsson) and would request to co-sign as well
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301443 CR Approval 23.501 CR3883R1 (Rel-18, 'B'): UE discover, select and access to a Hosting network for Localized services MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson, Futurewei, LG Electronics, InterDigital Rel-18 Revision of S2-2300369r20, merging S2-2301133, S2-2301223, S2-2300875, S2-2300979, S2-2300637 and S2-2300874. Approved Agreed
9.24.2 S2-2300637 CR Approval 23.501 CR3952 (Rel-18, 'B'): Support for accessing hosting network Huawei, HiSilicon Rel-18 Merged into S2-2301443 Clause 5.30.2.4.2.X (new), 5.30.3.4. Title implies accessing LS, but more selection aspects with SNPN and CAG, uses hosting nw. Overlaps with 00980, 01133, 01223, 00875, 00979, 01122, 00369, 00874. Overlaps with 01294. Sebastian (Qualcomm) proposes to mark merged into 0369
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
Yishan (Huawei) is ok to merged 0637 to 0369
Sebastian (Qualcomm) replies
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300874 CR Approval 23.501 CR4006 (Rel-18, 'B'): Support the mechanism how localized service is accessed in hosting network CATT Rel-18 Merged into S2-2301443 Clause 5.4.4a,5.30.2.3,5.30.2.5,5.30.3.4. UE capability, and multiple SNPN IDs and CAG IDs in SIB each dedicated to LS. Overlaps with 00980, 01133, 01223, 00875, 00979, 01122, 00369, 00637. Liping Wu (CATT) agrees to merge S2-2300874 into S2-2300369.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2301123 CR Approval 23.502 CR3844 (Rel-18, 'B'): Support for SoR enhancement for enabling automatic selection of SNPN as hosting network Xiaomi Rel-18 r07 agreed. Revised to S2-2301444, merging S2-2301230 and S2-2300980 UDM SOR change with time validity…no location. Overlap with 1230 (principle same). Pallab (Nokia) provides comments
Jianning (Xiaomi) replies to Pallab (Nokia) and provide r01
Pallab (Nokia) provides comments and thinks that the CR can be NOTED
Naman (Samsung) provides r02
Jianning (Xiaomi) responses and provides r04 by merging S2-2301230
Sebastian (Qualcomm) provides r05
Pallab (Nokia) provides r06
Peter Hedman (Ericsson) provides r07
==== Revisions Deadline ====
Jianning (Xiaomi) is ok with r07
Naman (Samsung) is OK with r07 as well and would like to co-sign
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301444 CR Approval 23.502 CR3844R1 (Rel-18, 'B'): Support for SoR enhancement for enabling automatic selection of SNPN as hosting network Xiaomi, Ericsson Rel-18 Revision of S2-2301123r07, merging S2-2301230 and S2-2300980. Approved Agreed
9.24.2 S2-2301230 CR Approval 23.502 CR3861 (Rel-18, 'B'): Update of SoR information for validity conditions Samsung Rel-18 Merged into S2-2301444 New note in UDM table for SOR. Overlap with 01123 (principle same). Jianning (Xiaomi) proposes to merge this paper into S2-2301123
Sebastian (Qualcomm) suggests to mark as merged into 1123
Naman (Samsung) agrees to merge this into 1123
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300980 CR Approval 23.501 CR4031 (Rel-18, 'B'): SoR update trigger for CH controlled prioritized list of SNPN/GIN containing time validity condition Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301444 Clause 5.30.2.3. Overlaps with 01122, 01133, 01223, 00875, 00979, 00369, 00637, 00874 Sebastian (Qualcomm) proposes to mark merged into 1123
Sebastian (Qualcomm) objects to the CR to avoid that it gets approved by mistake
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 - - - WID objective 3f – accessing localized services - - Docs:=3 -
9.24.2 S2-2300367 CR Approval 23.501 CR3882 (Rel-18, 'B'): Enable the UE to access Localized services after the UE registers to a Hosting network MediaTek Inc. Rel-18 Merged into S2-2301445 Uses hosting nw. Adds new x.z clause Peter Hedman (Ericsson) proposes to mark as merged into 00844 which is used as basis
Sebastian (Qualcomm) also proposes to mark merged
Chia-Lin (MediaTek) is ok to be merged into 00844
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.24.2 S2-2300844 CR Approval 23.501 CR3992 (Rel-18, 'B'): Enabling Access to Localized Services Samsung Rel-18 Confirm Spec version used - CR states Rel 18! r09 agreed. Revised to S2-2301445, merging S2-2300367 Adds new x.z clause Yishan (Huawei) asks for clarification
Guanzhou (InterDigital) questions what conclusion is the proposed change based upon?
Ashok (Samsung) provides r01
Guanzhou (InterDigital) responds to Ashok (Samsung).
Josep (DT) comments on the normative text in the informative annex, provides r02.
Peter Hedman (Ericsson) provides r03
Chia-Lin (MediaTek) agree with Peter (Ericsson) and suggest to remove the last part
Pallab (Nokia) agrees with previous comments and would support removal of the last part
Ashok (Samsung) responds
Peter Hedman (Ericsson) provides comments and r04
Josep (DT) comments, makes some changes to cover sheet, co-signs, provides r05.
Amanda Xiang ( Futurewei ) comments, co-signed and provides r06
Myungjune (LGE) provides r07 to cosign.
Huan ( vivo ) comments to r06/r07
Huan ( vivo ) provides r08
Ashok (Samsung) comments
Yishan (Huawei) comments and provides r09
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r09
Chia-Lin (MediaTek) can only accept r08 and r09. Prefer r08
Ashok (Samsung) propose to go with r09
Huan ( vivo ) is OK to r08 and r09.
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301445 CR Approval 23.501 CR3992R1 (Rel-18, 'B'): Enabling Access to Localized Services Samsung, Ericsson, Deutsche Telekom,Futurewei, LG Electronics Rel-18 Revision of S2-2300844r09, merging S2-2300367. Approved Agreed
9.24.2 - - - WID objective 3g - Return - - Docs:=3 -
9.24.2 S2-2300876 CR Approval 23.501 CR4008 (Rel-18, 'B'): Support for leaving network providing access to localized services CATT Rel-18 Noted Pallab (Nokia) provides comments and thinks the CR is not needed
Liping Wu (CATT) provides r01 and the response to Pallab (Nokia).
Josep (DT) comments, provides r02. Sees no need for normative changes.
Peter Hedman (Ericsson) provides comments
Liping Wu (CATT) agrees to add second note raised by Ericsson.
Liping Wu (CATT) provides r03.
Prabhu (NEC) suggests a minor update and provides r04.
Yishan (Huawei) comments
Pallab (Nokia) comments and thinks this CR is not needed
Sebastian (Qualcomm) has the same view as Pallab (Nokia)
Prabhu (NEC) provides r05.
==== Revisions Deadline ====
Pallab (Nokia) proposes to NOTE the CR.
==== Final Comments Deadline ====
Noted
9.24.2 S2-2300197 CR Approval 23.501 CR3843 (Rel-18, 'B'): Support for leaving network that provides access to localized services Ericsson, LG Electronics, NEC Rel-18 r01 agreed. Revised to S2-2301446. Not overlapping Peter Hedman (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.24.2 S2-2301446 CR Approval 23.501 CR3843R1 (Rel-18, 'B'): Support for leaving network that provides access to localized services Ericsson, LG Electronics, NEC Rel-18 Revision of S2-2300197r01. Approved Agreed
9.24.2 - - - Documents exceeding TU Budget - - Docs:=4 -
9.24.2 S2-2300102 CR Approval 23.502 CR3658 (Rel-18, 'B'): N5CW device access to SNPN services Intel, Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.2 S2-2300103 CR Approval 23.503 CR0795 (Rel-18, 'B'): N5CW device access to SNPN services Intel, Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.2 S2-2301145 CR Approval 23.501 CR4075 (Rel-18, 'B'): Wireline access to SNPN Huawei, HiSilicon Rel-18 Check Affected Clauses! Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.24.2 S2-2301122 CR Approval 23.501 CR4072 (Rel-18, 'B'): Support for SoR enhancement for enabling automatic selection of SNPN as hosting network Xiaomi Rel-18 Not Handled Clause 5.30.2.4.2, 5.30.2.3. SOR update triggers will cause normative changes. Overlaps with 00980, 01133, 01223, 00875, 00979, 00369, 00637, 00874 Pallab (Nokia) checks if this is merged into 0369 as proposed by rapporteur Tdoc sorting list
==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.25.1 - - - Study on Enhancement of 5G UE Policy (FS_eUEPO) - - Docs:=23 -
9.25.1 - - - Evaluation and Conclusion for KI#1 (URSP in VPLMN) - - Docs:=5 -
9.25.1 S2-2300193 P-CR Approval 23.700-85: KI#1 Conclusions. Ericsson Rel-18 Noted Changhong (Intel) proposes to NOTE this paper based on the SoH result for KI#1.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.1 S2-2300883 P-CR Approval 23.700-85: Updating to KI#1 Conclusion. OPPO Rel-18 r06 agreed. Revised to S2-2301616, merging S2-2301266 Mike (InterDigital) comments and provides r01
Hong (Qualcomm) comments on r01.
Mike (InterDigital) replies to Hong (Qualcomm)
Krisztian (Apple) suggests to merge 1266r02 into 0883r01 (or the other way) to have a full picture of KI#1 conclusion.
Mike (InterDigital) accepts the suggestion from Krisztian (Apple) and merged 1266r02 into 0883r01. Revision r02 is provided.
Pallab (Nokia) provides comments on r02.
Jicheol (Samsung) provides r03 and cosigns the paper.
Mike (InterDigital) replies to Jicheol (Samsung) and Pallab (Nokia) and provides r04.
Dimitris (Lenovo) comments
Yang (OPPO) provides r05
Krisztian (Apple) provides r06 and co-signs.
==== Revisions Deadline ====
Yang (OPPO) is ok to go with r06
Pallab (Nokia) supports r06.
Jicheol (Samsung) is fine with r06.
Dimitris (Lenovo) supports r06
==== Final Comments Deadline ====
Revised
9.25.1 S2-2301616 P-CR Approval 23.700-85: Updating to KI#1 Conclusion. OPPO, InterDigital Inc., Lenovo, Intel, Samsung, Apple, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300883r06, merging S2-2301266. Approved Approved
9.25.1 S2-2301266 P-CR Approval 23.700-85: Key Issue #1 Conclusion Update. InterDigital, Inc., Lenovo Rel-18 Merged into S2-2301616 Mike (InterDigital) provides r01 based on the SoH on CC-1
Changhong (Intel) provides r02 and cosigns.
Mike (InterDigital) proposes to mark this document as merged into S2-2300883.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.25.1 S2-2301224 DISCUSSION Agreement Discussion on Edge Computing Scenarios and FS_eUEPO Key Issue #1 Option D. InterDigital, Inc., Lenovo Rel-18 Noted Mike (InterDigital) comments that this discussion paper can be NOTED.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.1 - - - Evaluation and Conclusion for KI#2 (5GC awareness of URSP enforcement) - - Docs:=8 -
9.25.1 S2-2300370 P-CR Approval 23.700-85: KI#2: URSP precedence as URSP rule ID. MediaTek Inc., Huawei Rel-18 Noted Krisztian (Apple) objects to the proposed conclusion.
Josep (DT) replies to Krisztian (Apple) that SA3 did not identify and privacy issue.
Pavan (Google) agrees with Apple.
Krisztian (Apple) responds to Josep (DT): a lack of SA3 reply does not mean there is no privacy issue, it just means SA3 could not find consensus yet.
Yang (OPPO) comments
Haiyang (Huawei) comments
Yang (OPPO) replies to Haiyang
Haiyang (Huawei) comments to Yang (OPPO)
Changhong (Intel) proposes to NOTE this paper based on SoH result at CC#2.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.1 S2-2300513 P-CR Approval 23.700-85: KI#2: Update on Conclusion. Intel Rel-18 r01 agreed. Revised to S2-2301617. Yang (OPPO) thinks the EN can be simply removed and provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.25.1 S2-2301617 P-CR Approval 23.700-85: KI#2: Update on Conclusion. Intel Rel-18 Revision of S2-2300513r01. Approved Approved
9.25.1 S2-2300887 P-CR Approval 23.700-85: Update of conclusion of KI#2 about UE reporting connection capabilities. Vivo Rel-18 Merged into S2-2301485 To be merged into S2-2301146 (For CC#4) Pallab (Nokia) checks if this can be considered as merged to 1146?
Huazhang (vivo) confirm the merge to 1146, that in 1146r01, I have merge content in this paper into 1146, thanks Pallab.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.25.1 S2-2301215 P-CR Approval 23.700-85: KI#2, Conclusions. Google Inc. Rel-18 Noted Krisztian (Apple) provides r01.
Josep (DT) comments. Sees this pCR as clearly part of KI#4, not KI#2
Susana (Vodafone) objects to this pCR.
Pavan (Google) responds to Apple, DT, and Vodafone, and supports r01
Hong (Qualcomm) comments.
Krisztian (Apple) comments.
Haiyang (Huawei) comments.
Pavan (Google) responds to QC and Huawei, and provides r02.
Yang (OPPO) clarifies 'Recognize' is a technical wording documented in 24526 already.
Hong (Qualcomm) replies to Yang and Pavan.
Yang (OPPO) replies to Hong and Pavan. Provide r03
Josep (DT) comments, also shares views of Hong (Qualcomm).
Masaharu (KDDI) comments that I have same views of Hong (Qualcomm).
Susana (Vodafone) comments and objects to any revision of this document.
Dimitris (Lenovo) shares the view raised by Vodafone and Qualcomm
Changhong (Intel) proposes to NOTE this paper based on SoH result at CC#2.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.1 S2-2300946 P-CR Approval 23.700-85: KI#2, Evaluation and Conclusions. Deutsche Telekom, BT, Ericsson, China Unicom, KDDI, Vodafone, Intel Rel-18 Revision of S2-2209957. Revised to S2-2301146 Revised
9.25.1 S2-2301146 P-CR Approval 23.700-85: KI#2, Evaluation and Conclusions. Deutsche Telekom, BT, Ericsson, China Unicom, KDDI, Vodafone, Intel Rel-18 Revision of S2-2300946. CC#4: r09 was agreed and was revised to S2-2301485 Krisztian (Apple) comments: 1. disagrees with the need for the UE to publish standardized traffic category, 2. NOTE 4 proposes to take SA3 feedback into account however the recent proposal is not aligned with the LS S2-2209327 we sent to SA3.
Josep (DT) replies to Krisztian (Apple).
Krisztian (Apple) responds to Josep (DT).
Josep (DT) replies to Kirsztian (Apple).
Masaharu (KDDI) comments to Krisztian (Apple)
Huazhang (vivo) provide r01 to reflect the content in 887
Josep (DT) comments on SoH, add NEC as co-signer after offline talk, provides r02.
Huazhang (vivo) have one comments
Chia-Lin (MediaTek) provides r03 based on r02
Yang (OPPO) comments to r03
Josep (DT) thanks the previous revisions, comments, replies to Yang (Oppo)
Yang (OPPO) replies to Josep and provide r04. OPPO is fine to r04
Haiyang (Huawei) provides r05
Josep (DT) provides minor clean-up in r06.
Huazhang (vivo) provides r07 based on r06
Josep (DT) comments, provides r09, please ignore r08.
Yang (OPPO) provides r08
Krisztian (Apple) provides r10.
==== Revisions Deadline ====
Haiyang (Huawei) is OK with r10.
Huazhang (vivo) is ok with r10, thanks all
Josep (DT) has a strong preference for r09.
Susana (Vodafone) disagrees with r10 and prefer r09
Dimitris (Lenovo) prefers r09
Iskren (NEC) prefers r09
Masaharu (KDDI) is ok with r09 and r10. My preference is r09.
Pavan (Google) can live with r10, has a concern with r09.
Changhong (Intel) kindly requests Krisztian to consider moving forward with r09 by removing 'Monitoring'.
Krisztian (Apple) can only accept r10.
Josep (DT) comments, would be OK with 'r09 + remove 'monitoring''.
Huazhang (vivo) r09 + removing 'monitor' is ok to me
Changhong (Intel) asks Tao to mark it for CC#4. Let's aim to approved the r09 + removing 'monitoring', if not, we can establish working agreement.
Krisztian (Apple): just to reiterate, we can only accept r10.
Krisztian (Apple) objects to 'r09 + removing 'monitoring'. We can of course discuss it in CC#4.
==== Final Comments Deadline ====
Revised
9.25.1 S2-2301485 P-CR Approval 23.700-85: KI#2, Evaluation and Conclusions. Deutsche Telekom, BT, Ericsson, China Unicom, KDDI, Vodafone, Intel, NEC, Huawei Rel-18 Revision of S2-2301146r09. Approved. Concern from Apple recorded Approved
9.25.1 - - - Evaluation and Conclusion for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=7 -
9.25.1 S2-2300885 P-CR Approval 23.700-85: Update of conclusion of KI#3 about dual-register. Vivo Rel-18 Merged into S2-2301619 DongYeon (Samsung) comments.
Huazhang (vivo) reply to DongYeon
Changhong (Intel) comments.
Huazhang (vivo) provides r01 and try to give some explaination
Changhong (Intel) proposes to use S2-2301014 as the baseline, we can mark this paper as merged into S2-2301014.
Huazhang (vivo) confirms this merge, thanks Changhong
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.25.1 S2-2300976 P-CR Approval 23.700-85: 23.700-85: Conclusions update for KI#3 to remove EN1. Nokia, Nokia Shanghai Bell Rel-18 Noted DongYeon (Samsung) comments.
Pallab (Nokia) responds to DongYeon (Samsung).
Changhong (Intel) proposes to use S2-2301014 to resolve the EN and NOTE this paper.
==== Revisions Deadline ====
DongYeon (Samsung) propose NOTE this paper.
==== Final Comments Deadline ====
Noted
9.25.1 S2-2300975 P-CR Approval 23.700-85: 23.700-85: Conclusions update for KI#3, remove 2nd EN. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2301618. Pallab (Nokia) is OK with r01
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r01.
==== Final Comments Deadline ====
Revised
9.25.1 S2-2301618 P-CR Approval 23.700-85: 23.700-85: Conclusions update for KI#3, remove 2nd EN. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2300975r01. Approved Approved
9.25.1 S2-2301003 DISCUSSION Agreement Discussion on conclusion update for KI#3. Samsung Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.1 S2-2301014 P-CR Approval 23.700-85: KI#3: Update on Conclusion. Samsung Rel-18 r02 agreed. Revised to S2-2301619, merging S2-2300885 Pallab (Nokia) provides comments.
DongYeon (Samsung) provides r01.
Changhong (Intel) comments on r01.
Huazhang (vivo) provide comments
DongYeon (Samsung) replies to Pallab, Changhong, and Huazahng.
Changhong (Intel) provides r02 to convert the EN into a NOTE.
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r02.
Pallab (Nokia) OK to approve r02. Objects to r00, r01.
==== Final Comments Deadline ====
Revised
9.25.1 S2-2301619 P-CR Approval 23.700-85: KI#3: Update on Conclusion. Samsung Rel-18 Revision of S2-2301014r02, merging S2-2300885. Approved Approved
9.25.1 - - - Documents exceeding TU Budget - - Docs:=3 -
9.25.1 S2-2300512 P-CR Approval 23.700-85: KI#1: Update on Conclusion. Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.25.1 S2-2301210 P-CR Approval 23.700-85: KI#2, Evaluation . Google Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.25.1 S2-2300514 P-CR Approval 23.700-85: KI#3: Update on Conclusion. Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Comments Deadline ====
-
9.25.2 - - - Enhancement of 5G UE Policy (eUEPO) - - Docs:=22 -
9.25.2 - - - Evaluation and Conclusion for KI#1 (URSP in VPLMN) - - Docs:=4 -
9.25.2 S2-2300194 CR Approval 23.503 CR0804 (Rel-18, 'B'): KI#1 - Provision of URSP to route traffic to the VPLMN Ericsson Rel-18 Postponed Mike (InterDigital) comments and provides r01.
Yang (OPPO) comments the second change needs to be deferred. And ask clarification for 'URSP to route to VPLMN'
Belen (Ericsson) provides r02, responds to OPPO.
Hong (Qualcomm) comments on r02.
Yang (OPPO) replies to Ericsson and provides r03
Mike (InterDigital) comments and provides r04
Yang (OPPO) provides r05
Belen (Ericsson) provides r06
==== Revisions Deadline ====
Yang (OPPO) cannot agree the CR and propose to postpone it.
Belen (Ericsson) asks OPPO, agrees to POSTPONE it if more discussion is needed
Dimitris (Lenovo) prefers to proceed with r06
Mike (InterDigital) also prefers to proceed with r06
Yang (OPPO) proposes to postpone
==== Final Comments Deadline ====
Postponed
9.25.2 S2-2300390 CR Approval 23.502 CR3712 (Rel-18, 'B'): Service Parameters for URSP in VPLMN LG Electronics, vivo Rel-18 r08 agreed. Revised to S2-2301620, merging S2-2300941 LaeYoung (LGE) provides r01.
Pallab (Nokia) provides r02.
LaeYoung (LGE) provides r03.
Dimitris (Lenovo) has a question for clarification
LaeYoung (LGE) replies to Dimitris (Lenovo).
Dimitris (Lenovo) provides r04 removing the 'any UE' restriction
Krisztian (Apple) provides r05.
LaeYoung (LGE) is fine with r05.
Pallab (Nokia) comments on r05.
Dimitris (Lenovo) responds to Pallab (Nokia)
Belen (Ericsson) provides r06
LaeYoung (LGE) provides r07.
Pallab (Nokia) provides r08
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r08.
Jicheol (Samsung) requests to cosign.
Dimitris (Lenovo) is ok with r08
LaeYoung (LGE) thanks to Dimitris (Lenovo) and Jicheol (Samsung).
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301620 CR Approval 23.502 CR3712R1 (Rel-18, 'B'): Service Parameters for URSP in VPLMN LG Electronics, vivo, Nokia, Nokia Shanghai Bell, Apple, Ericsson, Lenovo, Samsung Rel-18 Revision of S2-2300390r08, merging S2-2300941. Approved Agreed
9.25.2 S2-2300941 CR Approval 23.502 CR3819 (Rel-18, 'B'): AF providing VPLMN specific URSP rules to H-PCF Lenovo, Apple Rel-18 Merged into S2-2301620 LaeYoung (LGE) suggests to MERGE this CR into S2-2300390.
==== Revisions Deadline ====
Dimitris (Lenovo) confirms CR is merged into S2-2300390
==== Final Comments Deadline ====
Merged
9.25.2 - - - Evaluation and Conclusion for KI#2 (5GC awareness of URSP enforcement) - - Docs:=3 -
9.25.2 S2-2300277 CR Approval 23.288 CR0618 (Rel-18, 'B'): KI#2 New NWDAF analytic on URSP enforcement OPPO Rel-18 Noted To be merged into S2-2300938 (Noted) Yang (OPPO) provides r01 correcting the cover page
Dimitris (Lenovo) comments
Josep (DT) comments, asks regarding merge of 0277 and 0938.
Yang (OPPO) replies
Josep (DT) asks a question for clarification.
Changhong (Intel) proposes to merge this paper into S2-2300938.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.2 S2-2300936 DISCUSSION Discussion KI#2: Using NWDAF analytics to identify traffic which does not correspond to a URSP rule. Lenovo Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.25.2 S2-2300938 CR Approval 23.288 CR0665 (Rel-18, 'B'): NWDAF analytics to detect URSP enforcement Lenovo Rel-18 Noted Dimitris (Lenovo) provides r01 with additional clarifications
Josep (DT) comments, provides r02, asks question regarding SUPI from UPF.
Yang (OPPO) comments to the solution
Dimitris (Lenovo) responds
Belen (Ericsson) asks questions for clarification
Yang (OPPO) uploads r03
Dimitris (Lenovo) responds to Belen (Ericsson)
Josep (DT) comments, provides r04.
Belen (Ericsson) objects to r03, and still think that the CR needs more work
Yang (OPPO) asks questions to Ericsson
Belen (Ericsson) replies to OPPO
Dimitris (Lenovo) provides answers to Belen (Ericsson)
Yang (OPPO) replies
Belen (Ericsson) provides comments
Yang (OPPO) asks question to Lenovo
Yang (OPPO) replies to Ericsson
Dimitris (Lenovo) provides responses
Yang (OPPO) comments PFD derivation cannot fulfill the requirement
==== Revisions Deadline ====
Dimitris (Lenovo) provides r05 with 'potentially' acceptable wording
Yang (OPPO) objects r00 and all revisions.
Belen (Ericsson) would be okay with r05
==== Final Comments Deadline ====
Noted
9.25.2 - - - Evaluation and Conclusion for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=8 -
9.25.2 S2-2300515 CR Approval 23.501 CR3924 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 r03 agreed. Revised to S2-2301621. Yang (OPPO) provides r01 correcting the parameter name
Changhong (Intel) is fine with the term change.
Belen (Ericsson) provides r02
Changhong (Intel) provides r03.
Pallab (Nokia) provides r04.
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r03, and r04 is not preferred.
DongYeon (Samsung) is OK with r03, objects to r04.
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301621 CR Approval 23.501 CR3924R1 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 Revision of S2-2300515r03. Approved Agreed
9.25.2 S2-2300516 CR Approval 23.502 CR3740 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 r04 agreed. Revised to S2-2301622. Pallab (Nokia) provides comments.
Yang (OPPO) provides r01 correcting the indication name
Belen (Ericsson) provides r02
Changhong (Intel) comments on r02
Changhong (Intel) provides r03.
Belen (Ericsson) prefers r02 to allow for discussion
Changhong (Intel) provides r04 to include the EN proposed in r02.
==== Revisions Deadline ====
DongYeon (Samsung) prefers r03, have question on the EN included in r02 and r04.
Belen (Ericsson) is okay with r04, replies on r02 and the added EN
DongYeon (Samsung) proposes to change the EN in r04 as: 'How to handle when the UE re-enables N1 mode is FFS'.
Belen (Ericsson) asks Samsung about the proposed EN.
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301622 CR Approval 23.502 CR3740R1 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 Revision of S2-2300516r04. Approved Agreed
9.25.2 S2-2300517 CR Approval 23.503 CR0839 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 r03 agreed. Revised to S2-2301623. Pallab (Nokia) provides comments.
Belen (Ericsson) provides r01
Changhong (Intel) provides r02
Changhong (Intel) provides r03
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301623 CR Approval 23.503 CR0839R1 (Rel-18, 'B'): Support URSP provisioning in EPS Intel Rel-18 Revision of S2-2300517r03. Approved Agreed
9.25.2 S2-2300884 CR Approval 23.502 CR3807 (Rel-18, 'B'): UE policy association handling from EPS to 5GS Vivo Rel-18 r04 agreed. Revised to S2-2301624. DongYeon (Samsung) comments.
Pallab (Nokia) comments.
Huazhang (vivo) provides r01 to make the plan simpler to terminate the UE policy association in EPS
Huazhang (vivo) provide r02
Changhong (Intel) thinks this CR should be noted and we should focus on updating the TR conclusion for this EN at this meeting.
Huazhang (vivo) reply to Changhong that this paper didn't focus on the dual-registration
Belen (Ericsson) objects to r02, r01 and initial version
Changhong (Intel) replies to Huazhang.
Huazhang (vivo) provides r03
Changhong (Intel) is OK with r03.
Belen (Ericsson) provides r04 some minor rewording.
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r04, objects to r02, r01, and r00.
Huazhang (vivo) is ok with r04, thanks Belen and all
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301624 CR Approval 23.502 CR3807R1 (Rel-18, 'B'): UE policy association handling from EPS to 5GS Vivo Rel-18 Revision of S2-2300884r04. Approved Agreed
9.25.2 - - - Evaluation and Conclusion for KI#4 (Support standardized and operator-specific traffic categories in URSP) - - Docs:=7 -
9.25.2 S2-2300027 LS In Action LS from CT WG1: Reply LS on UEPO Traffic Categories CT WG1 (C1-227518) Rel-18 Responses drafted in S2-2300886, S2-2301317. Postponed Postponed
9.25.2 S2-2300886 LS OUT Approval [DRAFT] Reply LS on UEPO Traffic Categories vivo Response to S2-2300027. Postponed To be merged into S2-2301317 (Postponed) Changhong (Intel) proposes to use this paper as the baseline for LS OUT.
Hong (Qualcomm) comments and propose to wait for the LS from GSMA ENSWI.
Huazhang (vivo) reply to Hong
Krisztian (Apple) thinks S2-2301317 better reflects what we sent to CT1 previously in S2-2208461.
Huazhang (vivo) reply to Krisztian (Apple)
Haiyang (Huawei) comments
Farooq (AT&T) proposes to defer reply LS to next meeting. Also prefers response from Apple in S2-2301317
Huazhang (vivo) is ok to postpone the LS until the GSMA give the new LS, but it is not proper to don't give any value of traffic category to CT1, because that the requirements is received by SA2, and the CT1 only focus the requirement from SA2, not GSMA
Krisztian (Apple) thinks SA2 can send the info in S2-2301317 from this meeting to trigger the work in CT1 asap.
Changhong (Intel) proposes to NOTE this LS OUT and discuss the content in the thread of S2-2301317.
Huazhang (vivo) prefers to merge this into the S2-2301317, bacause all of these are the two possible way to send LS, thanks Changhong
==== Revisions Deadline ====
Susana (Vodafone) prefers to delay the reply LS to next meeting
Krisztian (Apple) prefers to send the LS to CT1 to trigger the work there. Considering eUEPO is not scheduled in Feb, sending the LS from the April meeting is a long delay.
Huazhang (vivo) feel free to send this LS to CT1, but as I said that maybe CT1 still sends LS to SA2 for the certain value of Traffic category
==== Final Comments Deadline ====
Postponed
9.25.2 S2-2301317 LS OUT Approval [DRAFT] Reply LS on UEPO Traffic Categories (response to S2-2300027) Apple Rel-18 Response to S2-2300027. Postponed Changhong (Intel) proposes to NOTE this LS OUT and discuss in the thread of S2-2300886.
Krisztian (Apple) thinks this LS OUT better reflects what we sent to CT1 previously in S2-2208461.
Changhong (Intel) proposes to use this paper as baseline for the LS OUT.
==== Revisions Deadline ====
Susana (Vodafone) prefers to delay the reply LS to next meeting
Krisztian (Apple) prefers to send the LS to CT1 to trigger the work there. Considering eUEPO is not scheduled in Feb, sending the LS from the April meeting is a long delay.
Huazhang (vivo) feel free to send this LS to CT1, but as I said that maybe CT1 still sends LS to SA2 for the certain value of Traffic category
==== Final Comments Deadline ====
Postponed
9.25.2 S2-2300300 CR Approval 23.503 CR0814 (Rel-18, 'B'): New value of Connection Capability Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2301625. DongYeon (Samsung) asks if 0300 can be merge into 1313.
Changhong (Intel) proposes to use this paper to focus on changes in clause 6.6.2 and Apple paper can focus on changes in Annex.
Krisztian (Apple) provides r01 to align with 1313.
Haiyang (Huawei) is OK with r01.
DongYeon (Samsung) provides r02.
Krisztian (Apple) provides r03.
Susana (Vodafone) comments and provides r04.
Antoine (Orange) provides r05.
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r05.
Krisztian (Apple) is OK with r05.
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301625 CR Approval 23.503 CR0814R1 (Rel-18, 'B'): New value of Connection Capability Huawei, HiSilicon, Apple, Samsung Rel-18 Revision of S2-2300300r05. Approved Agreed
9.25.2 S2-2301313 CR Approval 23.503 CR0893 (Rel-18, 'B'): Support standardized and operator-specific traffic categories in URSP Apple Rel-18 r04 agreed. Revised to S2-2301626. Changhong (Intel) proposes to use this paper to only focus on changes in Annex.
Haiyang (Huawei) provides r01 as Changhong (Intel) proposed.
Krisztian (Apple) provides r02 to update the cover page to reflect the change.
DongYeon (Samsung) provides r03.
Susana (Vodafone) asks whether the EN included in the annex should be rephrased considering the threads on the LS to CT1
Krisztian (Apple) provides r04 to implement Susana's comment.
==== Revisions Deadline ====
DongYeon (Samsung) is OK with r04.
Haiyang (Huawei) is OK with r04 and would like to cosign.
==== Final Comments Deadline ====
Revised
9.25.2 S2-2301626 CR Approval 23.503 CR0893R1 (Rel-18, 'B'): Support standardized and operator-specific traffic categories in URSP Apple, Samsung, Huawei, HiSilicon Rel-18 Revision of S2-2301313r04. Approved Agreed
9.26.1 - - - Study on System Enabler for Service Function Chaining (FS_SFC) - - Docs:=0 -
9.26.2 - - - System Enabler for Service Function Chaining (SFC) - - Docs:=20 -
9.26.2 S2-2301117 CR Approval 23.501 CR4069 (Rel-18, 'B'): Support for Service Function Chaining in 5GS Intel Rel-18 r10 agreed. Revised to S2-2301848, merging S2-2300137 Dongjoo (Nokia) provides r02 for co-signing and minor changes.
Megha (Intel) provides r01
Dimitris (Lenovo) asks to cosign
Fenqin (Huawei) provides comments
Megha (Intel) provides r03 and comments
Stefan (Ericsson) provides r04
Fenqin (Huawei) provides r05
Stefan (Ericsson) provides r06
Dongjoo (Nokia) provides r07
Fenqin (Huawei) provides r08
Megha(Intel) provides comments
Hyunsook (LGE) provides comments
Hyunsook (LGE) provides r09.
Stefan (Ericsson) provides r10
==== Revisions Deadline ====
Megha(Intel) is ok with r10.
Dongjoo (Nokia) is also ok with r10.
Hyunsook (LGE) is fine with r10.
Fenqin(Huawei) is ok with r10.
==== Final Comments Deadline ====
Revised
9.26.2 S2-2301848 CR Approval 23.501 CR4069R1 (Rel-18, 'B'): Support for Service Function Chaining in 5GS Intel, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Deutsche Telekom Rel-18 Revision of S2-2301117r10, merging S2-2300137. Approved Agreed
9.26.2 S2-2301119 CR Approval 23.502 CR3843 (Rel-18, 'B'): Procedure update to support Service Function Chaining in 5GS Intel Rel-18 Merged into S2-2301850 Megha (Intel) comments this CR can be merged with S2-2300138.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2301202 CR Approval 23.501 CR3728R2 (Rel-18, 'B'): Supporting traffic influence to service functions Lenovo, Rel-18 Revision of S2-2208701. Merged into S2-2301849 Megha (Intel) comments - Can this CR be merged with S2-2300265?
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2301212 CR Approval 23.502 CR3580R1 (Rel-18, 'B'): Supporting traffic influence to service functions Lenovo, Rel-18 Revision of S2-2208712. Merged into S2-2301850 Megha (Intel) comments - can this CR be merged with S2-2300138?
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300667 CR Approval 23.503 CR0756R1 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Revision of S2-2208901. r07 agreed. Revised to S2-2301851, merging S2-2300267 Dongjoo (Nokia) provides r01.
Megha (Intel) provides comments - to use this CR as baseline for discussion on clause 5.3.1, 6.1.3.14, 6.3.1.
Dimitris (Lenovo) provides r02
Fenqin (Huawei) provides r03
Stefan (Ericsson) comments and provides r04
Fenqin (Huawei) provides r05
Dongjoo (Nokia) provides r06 to add co-signers
Dimitris (Lenovo) provides r07 adding Lenovo
Dieter (Deutsche Telekom) asks question for clarification
Fenqin (Huawei) give a response.
==== Revisions Deadline ====
Fenqin (Huawei) feedback to Dieter.
==== Final Comments Deadline ====
Revised
9.26.2 S2-2301851 CR Approval 23.503 CR0756R2 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Deutsche Telekom Rel-18 Revision of S2-2300667r07, merging S2-2300267. Approved Agreed
9.26.2 S2-2300665 CR Approval 23.501 CR3736R1 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Revision of S2-2208899. Merged into S2-2301849 Megha (Intel) comments - Can this CR be merged with S2-2300265?
==== Revisions Deadline ====
Fenqin (Huawei) we are ok this paper to be merged with S2-2300265.
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300666 CR Approval 23.502 CR3588R1 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Revision of S2-2208900. Merged into S2-2301850 Megha (Intel) comments - Can this CR be merged with S2-2300138?
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300729 CR Approval 23.501 CR3969 (Rel-18, 'B'): Support for SFC funtionality ETRI Rel-18 Noted Yoohwa (ETRI) provides r01 which includes only clause 6.2.3 based on the Rapporteur's proposal.
Megha (Intel) provides comments - to use this CR as baseline for discussion on clause 6.2.3
Fenqin (Huawei) provides comments
Yoohwa (ETRI) responds to Fenqin.
==== Revisions Deadline ====
Fenqin (Huawei) propose to note this paper.
Stefan (Ericsson) OK to note
==== Final Comments Deadline ====
Noted
9.26.2 S2-2300714 CR Approval 23.502 CR3571R1 (Rel-18, 'B'): Enabling AF to request predefined SFC ETRI Rel-18 Revision of S2-2208526. Merged into S2-2301850 Yoohwa (ETRI) agrees to merge this CR into S2-2300138.
Megha (Intel) comments - Can this CR be merged with S2-2300138?
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300266 CR Approval 23.502 CR3692 (Rel-18, 'B'): SFC CR 23.502 Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301850 Megha (Intel) comments - Can this CR be merged with S2-2300138?
Dongjoo (Nokia) agrees to merge this contribution into S2-2300138
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300139 CR Approval 23.503 CR0740R1 (Rel-18, 'B'): Basic description of Service Function Chaining Ericsson Rel-18 Revision of S2-2208270. r02 agreed. Revised to S2-2301852. Megha (Intel) comments - to use this CR as baseline for discussion on clause 4.3.7, 5.3.10.
Stefan (Ericsson) provides r01
Fenqin (Huawei) provides r02
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.26.2 S2-2301852 CR Approval 23.503 CR0740R2 (Rel-18, 'B'): Basic description of Service Function Chaining Ericsson, Deutsche Telekom Rel-18 Revision of S2-2300139r02. Approved Agreed
9.26.2 S2-2300138 CR Approval 23.502 CR3667 (Rel-18, 'B'): Support for AF influence on Service Function Chaining Ericsson Rel-18 r08 agreed. Revised to S2-2301850, merging S2-2301119, S2-2301212, S2-2300666, S2-2300714 and S2-2300266 Dongjoo (Nokia) provides r01 for co-signing and a few of changes.
Megha (Intel) comments - to use this CR as baseline for normative changes to TS 23.502.
Fenqin (Huawei) provides r02.
Dongjoo (Nokia) asks questions on r02.
Fenqin (Huawei) provides feedback.
Stefan (Ericsson) provides r03
Dongjoo (Nokia) provides feedback and r03.
Dongjoo (Nokia) provides feedback and r04.
Fenqin (Huawei) provides feedback and r05.
Dongjoo (Nokia) is fine with r05
Megha (Intel) provides r06 and comments
Fenqin (Huawei) provides r07
Yoohwa (ETRI) provides r08 to cosign.
==== Revisions Deadline ====
Stefan (Ericsson) OK with r08
==== Final Comments Deadline ====
Revised
9.26.2 S2-2301850 CR Approval 23.502 CR3667R1 (Rel-18, 'B'): Support for AF influence on Service Function Chaining Ericsson, Nokia, Nokia Shanghi Bell, Intel, ETRI, Deutsche Telekom Rel-18 Revision of S2-2300138r08, merging S2-2301119, S2-2301212, S2-2300666, S2-2300714 and S2-2300266. Approved Agreed
9.26.2 S2-2300137 CR Approval 23.501 CR3706R1 (Rel-18, 'B'): Basic description of Service Function Chaining Ericsson Rel-18 Revision of S2-2208269. Merged into S2-2301848 Megha (Intel) comments - Can this CR be merged with S2-2301117?
==== Revisions Deadline ====
Stefan (Ericsson) OK to merge as suggested by Megha
==== Final Comments Deadline ====
Merged
9.26.2 S2-2300265 CR Approval 23.501 CR3860 (Rel-18, 'B'): SFC CR 23.501 Nokia, Nokia Shanghai Bell Rel-18 r11 agreed. Revised to S2-2301849, merging S2-2301202 and S2-2300665 Dongjoo (Nokia) provides S2-2300265r01 to correct the version of the specification and remove 5.6.X and merge some parts from other CRs as proposed by the Rapporteur.
Dimitris (Lenovo) comments
Dongjoo (Nokia) asks a question for clarification to Lenovo
Stefan (Ericsson) provides comments
Stefan (Ericsson) provides r02
Dongjoo (Nokia) provides r03
Fenqin (Huawei) provides r04
Dongjoo (Nokia) provides r05
Stefan (Ericsson) provides r06
Fenqin (Huawei) provides r08
Dongjoo (Nokia) is fine with r08
Stefan (Ericsson) provides r09
Fenqin (Huawei) suggest to go with r08.
Stefan (Ericsson) cannot agree r08, replies to Fenqin
Fenqin (Huawei) replies to Stefan
Stefan (Ericsson) replies to Fenqin
Fenqin (Huawei) replies to Stefan further and provides r10
Dongjoo (Nokia) asks a question to Stefan (Ericsson)
Stefan (Ericsson) replies to Fenqin and Dongjoo and provides r11
Dongjoo (Nokia) supports Stefan (Ericsson) and r11
Stefan (Ericsson) replies to Dongjoo
==== Revisions Deadline ====
Fenqin (Huawei) Provides r12
Stefan (Ericsson) replies to Fenqin and suggests to go with r11
Fenqin (Huawei) accept r11
==== Final Comments Deadline ====
Revised
9.26.2 S2-2301849 CR Approval 23.501 CR3860R1 (Rel-18, 'B'): SFC CR 23.501 Nokia, Nokia Shanghai Bell, Ericsson, Intel, Deutsche Telekom Rel-18 Revision of S2-2300265r11, merging S2-2301202 and S2-2300665. Approved Agreed
9.26.2 S2-2300267 CR Approval 23.503 CR0811 (Rel-18, 'B'): SFC CR 23.503 Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301851 Dongjoo (Nokia) is ok to merge this contribution into S2-2300667.
Megha (Intel) comments - Can this CR be merged with S2-2300667?
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.1 - - - Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) - - Docs:=4 -
9.27.1 S2-2300688 P-CR Approval 23.700-46: Update the TR to resolve the EN in the conclusion. ZTE Rel-18 Merged into S2-2301627 György (Ericsson) proposes consider this merged into 0204
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.1 S2-2300903 P-CR Agreement 23.700-46: Resolution of open questions in DetNet TR. Nokia Rel-18 Noted György (Ericsson) comments.
Jari (NTT DOCOMO) comments.
Saubhagya (Nokia) comments.
György (Ericsson) responds to Nokia
György (Ericsson) proposes to note the document based on SoH outcome.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
9.27.1 S2-2300204 P-CR Approval 23.700-46: Resolution of open questions in DetNet TR. Ericsson Rel-18 Revised to S2-2301627, merging S2-2300688 zhendong (ZTE) proposes the comments.
György (Ericsson) agrees and responds to ZTE.
zhendong (ZTE) provides the response.
Jari (NTT DOCOMO) comments
Saubhagya (Nokia) comments.
György (Ericsson) comments.
==== Revisions Deadline ====
zhendong (ZTE) can accept r00 + removing '3gpp define YANG extension' bulletin.
Qianghua (Huawei) agrees with Zhendong, can only accept r00+removal of '3gpp define YANG extension' bulletin
zhendong (ZTE) provides r01 in the post revision folder.
György (Ericsson) agrees with the removal of the bullet on '3gpp define YANG extension'
==== Final Comments Deadline ====
Revised
9.27.1 S2-2301627 P-CR Approval 23.700-46: Resolution of open questions in DetNet TR. Ericsson Rel-18 Revision of S2-2300204, merging S2-2300688. Approved Approved
9.27.2 - - - Extensions to the TSC Framework to support DetNet (DetNet) - - Docs:=14 -
9.27.2 S2-2300902 CR Approval 23.503 CR0866 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301628 György (Ericsson) proposes to merge into 0208
György (Ericsson) proposes to consider this merged into 0208.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300901 CR Approval 23.502 CR3812 (Rel-18, 'B'): UL Routing information exposure to DetNet Controller Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301629 Sang-Jun (Samsung) comments
György (Ericsson) proposes to consider this merged into 0207.
György (Ericsson) responds to Samsung
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300689 CR Approval 23.501 CR3965 (Rel-18, 'B'): Adding support of IETF DetNet. ZTE Rel-18 Merged into S2-2301630 György (Ericsson) proposes to merge into 0205
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300691 CR Approval 23.503 CR0845 (Rel-18, 'B'): Adding support of IETF DetNet. ZTE Rel-18 Merged into S2-2301628 György (Ericsson) proposes to merge into 0208
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300882 CR Approval 23.501 CR4012 (Rel-18, 'B'): Support of UL routing exposure for Deterministic Networking Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2301630 Sang-Jun (Samsung) comments
György (Ericsson) proposes to consider this merged into 0205.
György (Ericsson) responds.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300690 CR Approval 23.502 CR3775 (Rel-18, 'B'): Adding support of IETF DetNet. ZTE Rel-18 Merged into S2-2301629 György (Ericsson) proposes to merge into 0207
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300623 CR Approval 23.502 CR3759 (Rel-18, 'B'): Updates on Npcf_PolicyAuthorization service ETRI Rel-18 Merged into S2-2301629 György (Ericsson) proposes to consider this merged into 0207.
Yoohwa (ETRI) agrees to merge this CR into 0207.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.27.2 S2-2300208 CR Approval 23.503 CR0806 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson Rel-18 r05 agreed. Revised to S2-2301628, merging S2-2300902, S2-2300691 and S2-2300301 György (Ericsson) provides r01.
Xiaowen (vivo) asks for clarification.
Saubhagya (Nokia) comments and provides r02.
Haiyang (Huawei) provides r03.
Jari (NTT DOCOMO) comments
György (Ericsson) responds to Vivo
György (Ericsson) comments
György (Ericsson) provides r04.
Xiaowen Sun (vivo) responses to Saubhagya and György.
zhendong (ZTE) provides r05.
Haiyang (Huawei) provides comments.
==== Revisions Deadline ====
Saubhagya (Nokia) provides comment.
György (Ericsson) proposes to go with r05 and do the suggested editorial updates during cleanup.
==== Final Comments Deadline ====
Revised
9.27.2 S2-2301628 CR Approval 23.503 CR0806R1 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung Rel-18 Revision of S2-2300208r05, merging S2-2300902, S2-2300691 and S2-2300301. Approved Agreed
9.27.2 S2-2300207 CR Approval 23.502 CR3683 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson Rel-18 r02 agreed. Revised to S2-2301629, merging S2-2300901, S2-2300690 and S2-2300623 György (Ericsson) provides r01.
zhendong (ZTE) provides the r02.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.27.2 S2-2301629 CR Approval 23.502 CR3683R1 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson, ZTE, Samsung Rel-18 Revision of S2-2300207r02, merging S2-2300901, S2-2300690 and S2-2300623. Approved Agreed
9.27.2 S2-2300205 CR Approval 23.501 CR3844 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson Rel-18 r07 + Editor's note agreed. Revised to S2-2301630, merging S2-2300882 and S2-2300689 György (Ericsson) provides r01.
György (Ericsson) provides r01. Re-sent with corrected subject line.
Saubhagya (Nokia) provides r02.
Haiyang (Huawei) provides r03.
György (Ericsson) comments
Jari (NTT DOCOMO) comemnts
György (Ericsson) comemnts
Jari (NTT DOCOMO) comments
Haiyang (Huawei) comments.
György (Ericsson) provides r04.
Haiyang (Huawei) provides comments.
György (Ericsson) responds to Huawei
zhendong (ZTE) provides r05.
zhendong (ZTE) provides r06.
György (Ericsson) comments.
Haiyang (Huawei) provides r07.
==== Revisions Deadline ====
Saubhagya (Nokia) prefers the r06 and object to the r07.
Haiyang (Huawei) comments, can only live with r03 or r07.
zhendong (ZTE) proposes to move with r07.
Saubhagya (Nokia) Ok with r05.
György (Ericsson) proposes to go with r07, and requests Huawei to update the wording of the EN.
Tao(VC) check agreeable of György's proposal.
György (Ericsson) ok with r07 with Huawei's updated EN wording.
Saubhagya (Nokia) Ok with r07 with updated EN.
==== Final Comments Deadline ====
Revised
9.27.2 S2-2301630 CR Approval 23.501 CR3844R1 (Rel-18, 'B'): Support of integration with IETF Deterministic Networking Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung Rel-18 Revision of S2-2300205r07 + Editor's note, merging S2-2300882 and S2-2300689. Approved Agreed
9.27.2 S2-2300301 CR Approval 23.503 CR0815 (Rel-18, 'B'): Policy control for DetNet Huawei, HiSilicon Rel-18 Merged into S2-2301628 György (Ericsson) proposes the document to be merged into 0208
Haiyang (Huawei) is OK to merge this paper into 0208
==== Revisions Deadline ====
==== Final Comments Deadline ====
Merged
9.28.1 - - - Study on Seamless UE context recovery (FS_SUECR) - - Docs:=0 -
9.28.2 - - - Seamless UE context recovery (SUECR) - - Docs:=0 -
9.29 - - - MBS support for V2X services (TEI18_MBS4V2X) - - Docs:=3 -
9.29 S2-2300362 CR Approval 23.287 CR0187 (Rel-18, 'B'): MBS support for V2X services LG Electronics, Tencent, Tencent Cloud Rel-18 Postponed LaeYoung (LGE) provides r02.
Shabnam (Ericsson) provides comments and r01, also co-signs the revised CR
Haris(Qualcomm) provides r03
Shabnam (Ericsson) provides comments on the roaming aspect
Thomas(Nokia) provides r04
LaeYoung (LGE) provides r05.
Thomas (Nokia) provides comments against r05 and replies to LaeYoung (LGE).
LaeYoung (LGE) replies to Thomas (Nokia) and provides r06.
Thomas (Nokia) replies to LaeYoung (LGE)
LaeYoung (LGE) responds to Thomas (Nokia).
LiMeng (Huawei) provides r07.
LaeYoung (LGE) replies to LiMeng (Huawei) and provides r08 on top of r06.
LiMeng (Huawei) provides r09.
Haris(Qualcomm) asks question on EN in r08
LaeYoung (LGE) comments on r09.
LaeYoung (LGE) responds to Haris (Qualcomm).
LaeYoung (LGE) provides r10 on top of r09 only to bring 'information' back to the EN just in case. ^__^
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that there seems to be quite some mixups with MBS vs. V2X use of MBS which can also define USD etc. if needed. So I suggest that we don't approve but rather use the work to further continue offline.
LaeYoung (LGE) is fine to postpone this CR, so let's take some offline discussion before Feb meeting and online discussion there for approval.
Tao(VC) then check we prefer to postpone or agree with a version as a basis for Feb. meeting.
Thomas(Nokia) replies to Shabnam (Ericsson) regarding USD.
LaeYoung (LGE) responds to Thomas(Nokia).
Haris(Qualcomm) comments
LiMeng (Huawei) tries to provide some more information regarding USD.
LaeYoung (LGE) thanks to Haris, Shabnam, Thomas and LiMeng for all the fruitful/useful information.
==== Final Comments Deadline ====
Postponed
9.29 S2-2300363 CR Approval 23.501 CR3881 (Rel-18, 'B'): 5QI for V2X message delivery via MBS LG Electronics, Tencent, Tencent Cloud Rel-18 r02 agreed. Revised to S2-2301631. LaeYoung (LGE) provides r02.
Shabnam (Ericsson) provides comments and r01, also co-signs the revised CR
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.29 S2-2301631 CR Approval 23.501 CR3881R1 (Rel-18, 'B'): 5QI for V2X message delivery via MBS LG Electronics, Tencent, Tencent Cloud, Ericsson Rel-18 Revision of S2-2300363r02. Approved Agreed
9.30 - - - Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) - - Docs:=10 -
9.30 S2-2300721 CR Approval 23.502 CR3777 (Rel-18, 'B'): Spending Limits for AM Policies in the 5GC Huawei, Oracle, Verizon UK Ltd, Ericsson Rel-18 Confirm CR Number - CR states 0377! r02 agreed. Revised to S2-2301632. Susan (Huawei) replies to Zhuoyi(China Telecom).
Zhuoyi(China Telecom) comments.
Susan (Huawei) provides r02.
==== Revisions Deadline ====
Uri (Oracle) comments on r02 that was kindly provided by Susan (Huawei).
==== Final Comments Deadline ====
Revised
9.30 S2-2301632 CR Approval 23.502 CR3777R1 (Rel-18, 'B'): Spending Limits for AM Policies in the 5GC Huawei, Oracle, Verizon UK Ltd, Ericsson Rel-18 Revision of S2-2300721r02. Approved Agreed
9.30 S2-2300203 CR Approval 23.503 CR0805 (Rel-18, 'B'): 23.503 Spending Limits for AM and UE Policies in the 5GC Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO, DISH Network Rel-18 r05 agreed. Revised to S2-2301633. Zhuoyi(China Telecom) comments at r02.
Uri(Oracle) comments on the email from Zhuoyi(China Telecom) and provides r02.
Zhuoyi(China Telecom) provides r01 and cosign.
Uri (Oracle) reply to Zhuoyi's (China Telecom) comments about r02.
Dieter (Deutsche Telekom) comments.
Uri (Oracle) replies to comment from Dieter (Deutsche Telekom) and provides rev03.
Mirko (Huawei) comments.
Uri (Oracle) replies to comments from Mirko (Huawei) and provides rev04.
Pallab (Nokia) provides r05.
Uri (Oracle) reply to a comment from Pallab (Nokia) and agrees with r05 provided by Pallab (Nokia).
==== Revisions Deadline ====
Pallab (Nokia) responds to Uri (Oracle)
==== Final Comments Deadline ====
Revised
9.30 S2-2301633 CR Approval 23.503 CR0805R1 (Rel-18, 'B'): 23.503 Spending Limits for AM and UE Policies in the 5GC Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO, DISH Network, China Telecom Rel-18 Revision of S2-2300203r05. Approved Agreed
9.30 S2-2300380 CR Approval 23.501 CR3886 (Rel-18, 'B'): 23.501 Spending Limits for AM and UE Policies in the 5GC Verizon, Oracle Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.30 S2-2300214 LS OUT Approval [DRAFT] LS about CHF Logic Realization wrt/ Spending Limits functionality Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO, DISH Network Rel-18 r01 agreed. Revised to S2-2301634. Belen (Ericsson) provides r01.
Uri responds to a question asked by Belen (Ericsson) and agrees with r01 that was provided by Belen (Ericsson).
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.30 S2-2301634 LS OUT Approval LS about CHF Logic Realization wrt/ Spending Limits functionality SA WG2 Rel-18 Revision of S2-2300214r01. Approved Approved
9.30 S2-2300215 CR Approval 23.502 CR3684 (Rel-18, 'B'): 23.502 Spending Limits for UE Policies in the 5GC Oracle, Verizon UK Ltd, Ericsson, OPPO Rel-18 Revised in S2-2301017 Revised
9.30 S2-2301017 CR Approval 23.502 CR3684R1 (Rel-18, 'B'): 23.502 Spending Limits for UE Policies in the 5GC Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, OPPO Rel-18 Revision of S2-2300215. Confirm CR Revision - CR states 0! r01 agreed. Revised to S2-2301635. Uri(Oracle) provides r01.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.30 S2-2301635 CR Approval 23.502 CR3684R2 (Rel-18, 'B'): 23.502 Spending Limits for UE Policies in the 5GC Oracle, Verizon UK Ltd, Huawei, HiSilicon, Ericsson, OPPO Rel-18 Revision of S2-2301017r01. Approved Agreed
9.31 - - - Enhancement of application detection event exposure (TEI18_ADEE) - - Docs:=2 -
9.31 S2-2300440 CR Approval 23.503 CR0831 (Rel-18, 'B'): Adding application detection event exposure from PCF China Mobile, Asiainfo, CATT, Huawei Rel-18 r01 agreed. Revised to S2-2301636. CC#4: This was postponed Pallab (Nokia) provides comments and requests for a revision.
Jinguo(ZTE ) replies to Pallab (Nokia)
Pallab (Nokia) responds.
Jinguo(ZTE) further replies to Pallab (Nokia)
Pallab (Nokia) responds to Jinguo(ZTE).
Belen (Ericsson) also requests a revision that removes bulk subscription for now
Aihua(CMCC) provides r01.
==== Revisions Deadline ====
Pallab (Nokia) is OK with r01
Belen (Ericsson) objects to r01 and initial version
Jinguo(ZTE) replies to Belen (Ericsson) suggest to approve r01 at this meeting
==== Final Comments Deadline ====
Belen (Ericsson) replies to ZTE
Postponed
9.31 S2-2301636 CR Approval 23.503 CR0831R1 (Rel-18, 'B'): Adding application detection event exposure from PCF China Mobile, Asiainfo, CATT, Huawei Rel-18 Revision of S2-2300440r01. Approved. CC#4: Withdrawn Withdrawn
9.32 - - - General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) - - Docs:=9 -
9.32 S2-2300260 CR Approval 23.304 CR0164 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 Approved ==== Revisions Deadline ====
==== Final Comments Deadline ====
Agreed
9.32 S2-2300261 CR Approval 23.316 CR2075 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics, ZTE, Apple Rel-18 r03 agreed. Revised to S2-2301637. Yildirim (Charter) provides r01.
Judy (Ericsson) thanks Yildirim (Charter) and fine with r01
Chris (Vodafone) asks whether the change from '5G RG' to 'RG' should also be done in the last sentence of the 23.501 CR.
Judy (Ericsson) confirms that '5G RG' should be changed to 'RG' in 23.501 CR as well.
Marco(Huawei) provides r02
Yildirim (Charter) comments
Judy (Ericsson) provides r03 to re-instate the description related to subscribed size of prefix as discussed in 0257
==== Revisions Deadline ====
Yildirim (Charter) is ok with r03 with a minor editorial fix.
Judy (Ericsson) is OK with a revision = r03 + change '5GRG' to '5G-RG'
==== Final Comments Deadline ====
Revised
9.32 S2-2301637 CR Approval 23.316 CR2075R1 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics, ZTE, Apple Rel-18 Revision of S2-2300261r03. Approved Agreed
9.32 S2-2300259 CR Approval 23.503 CR0810 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 r01 agreed. Revised to S2-2301638. Chris (Vodafone) asks a question.
Judy (Ericsson) provides r01, updating cover sheet to explain why the reference to TS 23.304 is removed in session binding.
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
9.32 S2-2301638 CR Approval 23.503 CR0810R1 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 Revision of S2-2300259r01. Approved Agreed
9.32 S2-2300257 CR Approval 23.501 CR3859 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 r04 agreed. Revised to S2-2301639. Fenqin (Huawei) provides comment.
Judy (Ericsson) responds to Fenqin (Huawei)
Fenqin (Huawei) provides further comment.
Chris (Vodafone) suggests change '5G RG' to 'RG' in the last sentence (to align with S2-2300261r01).
Judy (Ericsson) provides r01 to address comment from Chris (Vodafone) and responds to Fenqin (Huawei)
Fenqin (Huawei) provides r02 to add one EN.
Judy (Ericsson) provides r03 and responds to Fenqin (Huawei)
Fenqin (Huawei) provides responds to Judy.
Judy (Ericsson) responds to Fenqin (Huawei) and provide r04. Subscribed max size of prefix is removed from 23.501CR and will be kept in 23.316CR
==== Revisions Deadline ====
Judy (Ericsson) clarifies to Tao the latest revision is r04 (but not r03 which is marked for check in chariman's notes)
Fenqin (Huawei) accept r04, r02 and object other version. .
Judy (Ericsson) proposes to go for r04
==== Final Comments Deadline ====
Suresh Srinivasan (Intel) is Ok with r05/r06 .
Revised
9.32 S2-2301639 CR Approval 23.501 CR3859R1 (Rel-18, 'B'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 Revision of S2-2300257r04. Approved Agreed
9.32 S2-2300258 CR Approval 23.502 CR3690 (Rel-18, 'F'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 r02 agreed. Revised to S2-2301640. Judy (Ericsson) provides r01 to replace the reference of 23.501 with 23.316 for the subscribed max size of prefix, see discussion in 0257
Fenqin (Huawei) provides r02
Judy (Ericsson) responds to Fenqin (Huawei) and is fine with r02
==== Revisions Deadline ====
Fenqin (Huawei) accept only r02 and object other version.
==== Final Comments Deadline ====
Revised
9.32 S2-2301640 CR Approval 23.502 CR3690R1 (Rel-18, 'F'): IPv6 prefix delegation in 5GS Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, ZTE, Apple Rel-18 Revision of S2-2300258r02. Approved Agreed
10 - - - Project Planning and Management - - Docs:=0 -
10.1 - - - Revised Rel-18 Study Items - - Docs:=1 -
10.1 S2-2301078 SID REVISED Approval Revised SID: Study on system architecture for Next Generation Real Time Communication Services (FS_NG_RTC). China Mobile Rel-18 Postponed ==== Revisions Deadline ====
Leo (Deutsche Telekom) provides comments.
==== Final Comments Deadline ====
Postponed
10.2 - - - TS/TR Cover sheets - - Docs:=7 -
10.2 S2-2301296 TS OR TR COVER Approval Cover sheet for approval of TR 23.700-17 by TSG SA#99 Nokia, Nokia Shanghai Bell Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.2 S2-2301158 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-08 to TSG SA#99 Ericsson Rel-18 Postponed ==== Revisions Deadline ====
Peter Hedman (Ericsson) provides r01 in drafts folder
==== Final Comments Deadline ====
Postponed
10.2 S2-2301077 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-87 to TSG SA#99 China Mobile Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Yi (China Mobile) provides r01 to reflect the stauts of this meeting.
Rainer (Nokia) provides r02.
Ashok (Samsung) provides r03
Rainer (Nokia) replies.
Ashok (Samsung) provides r04
Rainer (Nokia) asks for clarification.
Yi (China Mobile) replies to Rainer.
Postponed
10.2 S2-2300510 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-85 to TSG SA#99 Intel Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.2 S2-2300209 TS OR TR COVER Approval Presentation of Report to TSG: TR 23.700-46, Version 1.2.0 Ericsson Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.2 S2-2301322 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-86 to TSG SA for approval Xiaomi Rel-18 Created at meeting. Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Sherry (Xiaomi) provides r00.
Postponed
10.2 S2-2301358 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-62 to TSG SA for approval China Mobile Rel-18 Created at meeting. Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Yan (China Mobile) provides the initial draft.
Postponed
10.3 - - - New and revised Rel-18 Work Items - - Docs:=9 -
10.3 S2-2301195 WID REVISED Approval Revised WID on generic group management, exposure and communication enhancements. Huawei, HiSilicon Rel-18 Revision of SP-221339. Postponed Laurent (Nokia): objects to R00 that is not aligned with the SoH result
Georgios Gkellas (Nokia, Nokia Shanghai Bell) provides r01
Sang-Jun (Samsung) provides r02
Hiroshi (NEC) provides r03
Georgios Gkellas (Nokia, Nokia Shanghai Bell) corrects AI in the 'Subject' from AI#9.8.1 to AI#10.3
==== Revisions Deadline ====
==== Final Comments Deadline ====
Qianghua (Huawei) provides r04 in the draft folder
Sang-Jun (Samsung) is fine with r04.
Postponed
10.3 S2-2301176 WID REVISED Approval Revised WID: Enhancement of Network Slicing Phase 3 (eNS_Ph3). ZTE, LG Electronics Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2301079 WID REVISED Approval WID update: System architecture for Next Generation Real time Communication services . China Mobile Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2300865 WID REVISED Approval Revised WID: System Support for AI/ML-based Services (AIMLsys). OPPO, Samsung Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2300202 WID REVISED Approval Revised WID: Enhanced support of Non-Public Networks Phase 2 (eNPN_Ph2). Ericsson Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Peter Hedman (Ericsson) as no comments received I will upload r00 to CC#4 folder 2hrs before CC#4 starts
Peter Hedman (Ericsson) will provide r01 adding more supporting companies 2hrs before the CC#4
Peter Hedman (Ericsson) provides r01 in CC#4 folder
Rainer (Nokia) is ok with r01.
Postponed
10.3 S2-2300606 WID REVISED Approval Updated WID: Support for 5WWC, Phase 2. Nokia, Nokia Shanghai Bell Rel-18 Revision of SP-221347. Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2300635 WID REVISED Approval Revised WID: Dynamically Changing AM Policies in the 5GC Phase 2. SA WG2 Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2300273 WID REVISED Approval Revised WID: 5GC/EPC enhancement for satellite access Phase 2 (5GSAT_Ph2). Thales, Xiaomi, Novamint, TNO Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Postponed
10.3 S2-2300511 WID REVISED Approval Revised WID: Enhancement of 5G UE Policy (eUEPO). Intel (Rapporteur) Rel-18 Postponed ==== Revisions Deadline ====
==== Final Comments Deadline ====
Changhong (Intel) provides r01.
Postponed
10.4 - - - Rel-18 SID/WID Status Reports - - Docs:=33 -
10.4 S2-2301286 WI STATUS REPORT Information SUECR Status Report Samsung Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301175 WI STATUS REPORT Information Status report for eNS_Ph3 ZTE, LG Electronics Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2300607 WI STATUS REPORT Information Status report: Support for 5WWC, Phase 2 Nokia, Nokia Shanghai Bell Rel-18 Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301326 WI STATUS REPORT Information WI and SID Status Report on 5GC LoCation Services - Phase 3 CATT Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301327 WI STATUS REPORT Information WI and SID Status Report on Stage 2 for Proximity based Services Phase 2 CATT Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301328 WI STATUS REPORT Information WI and SID Status Report on 5GC enhancement for satellite access Phase 2 Thales Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301329 WI STATUS REPORT Information WI and SID Status Report on Support of Satellite Backhauling in 5GS CATT Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301330 WI STATUS REPORT Information WI and SID Status Report on architectural enhancements for 5G multicast-broadcast services Phase 2 Huawei Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301331 WI STATUS REPORT Information WI and SID Status Report on 5G Timing Resiliency and TSC&URLLC enhancements Nokia Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301332 WI STATUS REPORT Information WI and SID Status Report on support for 5WWC Phase 2 Nokia Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301333 WI STATUS REPORT Information WI and SID Status Report on 5G System Support for AI/ML-based Services OPPO Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301334 WI STATUS REPORT Information WI and SID Status Report on 5G AM Policy China Telecom Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301335 WI STATUS REPORT Information WI and SID Status Report on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301336 WI STATUS REPORT Information WI and SID Status Report on Stage 2 of Edge Computing phase 2 Huawei Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301337 WI STATUS REPORT Information WI Status Report for FS_eNA_Ph3 Vivo Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301338 WI STATUS REPORT Information WI and SID Status Report on enhanced support of Non-Public Networks phase 2 Ericsson Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301340 WI STATUS REPORT Information WI and SID Status Report on enhancement of 5G UE Policy Intel Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301341 WI STATUS REPORT Information WI and SID Status Report on generic group management, exposure and communication enhancements Huawei Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301342 WI STATUS REPORT Information WI and SID Status Report on Stage 2 of MPS_WLAN Peraton Labs Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301343 WI STATUS REPORT Information WI and SID Status Report on system architecture for next generation real time communication services China Mobile Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301344 WI STATUS REPORT Information WI and SID Status Report on Personal IoT Networks vivo Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301345 WI STATUS REPORT Information WI and SID Status Report on Ranging based services and sidelink positioning Xiaomi Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301346 WI STATUS REPORT Information WI and SID Status Report on RedCap Phase 2 Ericsson Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301347 WI STATUS REPORT Information WI and SID Status Report on System Enabler for Service Function Chaining Intel Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301350 WI STATUS REPORT Information WI and SID Status Report on Phase 2 for UAS, UAV and UAM Qualcomm Finland RFFE Oy Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301351 WI STATUS REPORT Information WI and SID Status Report on UPF enhancement for Exposure And SBA China Mobile Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301352 WI STATUS REPORT Information WI and SID Status Report on Architecture Enhancements for Vehicle Mounted Relays Qualcomm Incorporated Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301353 WI STATUS REPORT Information WI status report for FS_XRM China Mobile Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301354 WI STATUS REPORT Information WI Status Report on MBS support for V2X services (TEI18_MBS4V2X) LG Electronics Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301355 WI STATUS REPORT Information WI Status Report on Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) Oracle Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301356 WI STATUS REPORT Information WI Status Report on Enhancement of application detection event exposure (TEI18_ADEE) China Mobile Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301357 WI STATUS REPORT Information WI Status Report on General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) Ericsson Rel-18 Created at CC#1. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.4 S2-2301361 WI STATUS REPORT Information WI Status Report on Extensions to the TSC Framework to support DetNet (DetNet) Ericsson Rel-18 Created at CC#3. Noted ==== Revisions Deadline ====
==== Final Comments Deadline ====
Noted
10.5 - - - Review of the Work Plan - - Docs:=2 -
10.5 S2-2300381 WORK PLAN Endorsement SA WG2 Work Planning SA WG2 Chair Revision of S2-2210903. CC#2: February updated TU allocation was endorsed, subject to resolution of any scheduling conflicts. r04 agreed. Revised to S2-2301447. Puneet (SA2 Chair) provides r01
==== Revisions Deadline ====
==== Final Comments Deadline ====
Revised
10.5 S2-2301447 WORK PLAN Endorsement SA WG2 Work Planning SA WG2 Chair - Revision of S2-2300381r04. February TUs were endorsed. April and May TUs will be further revised based on progress at the February meeting Endorsed
10.6 - - - Planning future meetings - - Docs:=0 -
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=431 -
99 S2-2301339 WI STATUS REPORT Information Status report for FS_eNS_Ph3 ZTE Rel-18 Created at CC#1. WITHDRAWN ==== Revisions Deadline ====
==== Final Comments Deadline ====
Withdrawn
99 S2-2301348 WI STATUS REPORT Information WI Status Report on Multiple location report for MT-LR Immediate Location Request for regulatory services Ericsson Rel-18 Created at CC#1. WITHDRAWN ==== Revisions Deadline ====
==== Final Comments Deadline ====
Withdrawn
99 S2-2301349 WI STATUS REPORT Information WI and SID Status Report on Secondary DN Authentication and authorization in EPC IWK cases Nokia Rel-18 Created at CC#1. WITHDRAWN ==== Revisions Deadline ====
==== Final Comments Deadline ====
Withdrawn
99 S2-2300096 LS In Information NOT USED - Reserved for incoming LS - () WITHDRAWN Withdrawn
99 S2-2300097 LS In Information NOT USED - Reserved for incoming LS - () WITHDRAWN Withdrawn
99 S2-2300098 LS In Information NOT USED - Reserved for incoming LS - () WITHDRAWN Withdrawn
99 S2-2300099 LS In Information NOT USED - Reserved for incoming LS - () WITHDRAWN Withdrawn
99 S2-2300100 LS In Information NOT USED - Reserved for incoming LS - () WITHDRAWN Withdrawn
99 S2-2300739 CR Approval 23.501 CR3972 (Rel-18, 'B'): Functional Description for PDU Set QoS Control CATT Rel-18 Confirm Specification Number - CR states 23.503! WITHDRAWN Withdrawn
99 S2-2301059 P-CR Approval 23.700-87: KI#1, Sol#20 Update to remove MDC3 Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2301058 CR Approval 23.228 CR1262 (Rel-18, 'B'): 23.228 Support of IMS Data Channel Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2301057 CR Approval 23.228 CR1261 (Rel-18, 'B'): 23.228 Supporting AR Telephony Communication Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2300601 CR Approval 23.304 CR0181 (Rel-18, 'B'): Multi-Path transmission OPPO Rel-18 WITHDRAWN Withdrawn
99 S2-2300350 CR Approval 23.501 CR3880 (Rel-18, 'B'): QoS monitoring with satellite backhaul reporting backhaul delay only Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2300351 CR Approval 23.503 CR0817 (Rel-18, 'B'): QoS monitoring with satellite backhaul reporting backhaul delay only Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2300352 DISCUSSION Approval Way forward on option issues for QoS Monitoring Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2300320 CR Approval 23.502 CR3704 (Rel-18, 'B'): Reporting a timing synchronization status Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2301106 CR Approval 23.501 CR4063 (Rel-18, 'B'): 23.502 Procedures for support of satellite discontinuous coverage data transfer CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2301220 CR Approval 23.502 CR3859 (Rel-18, 'B'): 23.502 Update of SoR information for validity conditions Samsung Rel-18 WITHDRAWN Withdrawn
99 S2-2301006 P-CR Approval 23.700-85: KI#3: Update on Conclusion Samsung Electronics Rel-18 WITHDRAWN Withdrawn
99 S2-2300850 CR Approval 23.501 CR3997 (Rel-18, 'B'): 23.501: update for 5G VN group data for service area and QoS CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300851 CR Approval 23.502 CR3802 (Rel-18, 'B'): 23.502: update for 5G VN group data for service area and QoS CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300849 CR Approval 23.502 CR3801 (Rel-18, 'B'): 23.502: Add the Group-MBR parameter for 5G VN group data CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300848 CR Approval 23.501 CR3996 (Rel-18, 'B'): 23.501: Add the Group-MBR parameter for 5G VN group data CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300747 CR Approval 23.501 CR3975 (Rel-18, 'B'): KI#1&3 NEF monitoring events for assisting AIML operation Samsung Rel-18 WITHDRAWN Withdrawn
99 S2-2300805 CR Approval 23.503 CR0856 (Rel-18, 'B'): 23.503 Congestion information exposure for XRM services Lenovo Rel-18 WITHDRAWN Withdrawn
99 S2-2300834 CR Approval 23.700-25 CR0005 (Rel-18, 'B'): Conclusion for FS_5TRS_URLLC KI#6 Samsung Rel-18 WITHDRAWN Withdrawn
99 S2-2300845 CR Approval 23.501 CR3993 (Rel-18, 'B'): Update conclusion for how localized service is accessed in hosting network per agreed conditions CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300846 CR Approval 23.501 CR3994 (Rel-18, 'B'): Update for information for accessing the localized service CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300847 CR Approval 23.501 CR3995 (Rel-18, 'B'): Update for supporting leaving network providing access to localized services CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300186 CR Approval 23.502 CR3682 (Rel-18, 'F'): Resolving EN on PCF s awareness of modified RFSP index indicating a change of priority from 5GC to EPC Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2300486 CR Approval 23.501 CR3918 (Rel-18, 'B'): TS 23.501 Enhancing 5G VN Group Management Chine Telecom Rel-18 WITHDRAWN Withdrawn
99 S2-2300489 CR Approval 23.502 CR3737 (Rel-18, 'B'): Add the Group-MBR parameter for 5G VN group data China Telecom Rel-18 WITHDRAWN Withdrawn
99 S2-2300490 CR Approval 23.503 CR0837 (Rel-18, 'B'): TS 23.503 Enhancing 5G VN Group policy control Chine Telecom, Huawei, CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300560 CR Approval 23.503 CR0894 (Rel-18, 'B'): GMEC KI1 TS23.503 CR Update for Group MBR China Telecom, Huawei, CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2300104 CR Approval 23.502 CR3659 (Rel-18, 'B'): Confidence Level of Expected UE Behaviour Parameters NTT DOCOMO Rel-18 WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 98
Agreed: 380
Replied to LSs: 21
Noted: 225
Merged: 186
For e-mail approval: 0
Postponed: 190
Withdrawn: 261
Total documents: 1776