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-2201916 AGENDA Approval SA WG2 #150E Meeting Agenda SA WG2 Chair Approved Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
3 - - - SA2#149E Meeting report - - Docs:=1 -
3 S2-2201917 REPORT Approval Auto-Generated Report of SA WG2 meeting #149E SA WG2 Secretary Approved Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=82 -
4.1 S2-2201950 LS In Information LS from RAN WG2: Reply LS on opens issues for NB-IoT and eMTC support for NTN RAN WG2 (R2-2204108) Rel-17 Noted Leo (Deutsche Telekom) proposes to NOTE the LS, there is no action for SA2.
==== Revisions Deadline ====
Noted
4.1 S2-2201958 LS In Information LS from SA WG3: Reply LS on opens issues for NB-IoT and eMTC support for NTN SA WG3 (S3-220543) Rel-17 Noted Steve (Huawei) Proposes to note.
==== Revisions Deadline ====
Leo (Deutsche Telekom): same view as Steve, LS shall be noted, no action for SA2.
Noted
4.1 S2-2201962 LS In Information LS from ETSI ISG MEC: LS to 3GPP on MEC Federation and interest to collaborate ETSI ISG MEC (MEC(22)000127r5) Noted Hui (Huawei) proposes to note this LS.
Magnus O (Ericsson) Agree with Hui, the LS is for information and should be Noted.
==== Revisions Deadline ====
Noted
4.1 S2-2201922 LS In Information LS from GSMA: Reply LS on IMEI for Non-Public Networks/Private Networks without using USIM GSMA (TSG46_028) Revision of Postponed S2-2200040 from S2#149E. Noted Rainer (Nokia) proposes to note the LS.
Qianghua (Huawei) the tile should be S2-2201922 and agrees to note 1922.
==== Revisions Deadline ====
Noted
4.1 S2-2201929 LS In Action LS from CT WG1: LS on progress of FS_eIMS5G2 CT WG1 (C1-220734) Rel-17 Revision of Postponed S2-2200082 from S2#149E. Noted Rainer (Nokia) proposes to note the LS as CT1 has made no progress on this topic.
==== Revisions Deadline ====
Noted
4.1 S2-2201935 LS In Action LS from SA WG3: LS on full Registration Request upon AMF re-allocation SA WG3 (S3-220453) Rel-17 Revision of Postponed S2-2201519 from S2#149E. Noted Fenqin (Huawei) Propose to note this LS.
Qian (Ericsson) agrees that the LS can be noted.
==== Revisions Deadline ====
Noted
4.1 S2-2202238 DISCUSSION Discussion Discussion paper on Mapped NSSAI handling. Apple Rel-17 Noted Noted
4.1 S2-2202378 DISCUSSION Discussion Discussion on the mapped S-NSSAI in VPLMN. Qualcomm Incorporated Noted Jinguo(ZTE) comments that the observation 2 is incorrect.
Guillaume (MediaTek Inc.) recommends this paper be noted. It is also incorrect.
Jinguo(ZTE) response to Guillaume,
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2202047 CR Approval 23.501 CR3583 (Rel-17, 'F'): Clarification on Mapped NSSAI Huawei, HiSilicon Rel-17 Approved Agreed
4.1 S2-2202240 CR Approval 23.501 CR3598 (Rel-17, 'F'): Correction of description of Mapped NSSAI handling Apple Rel-17 Noted Jinguo(ZTE) correct the title since this topic is moved to 4.1
Dongeun (Samsung) objects to this CR.
Stefano (Qualcomm) objects to this CR.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2201936 LS In Action LS from CT WG1: LS on Mapped NSSAI CT WG1 (C1-222095) Rel-17 Responses drafted in S2-2202046, S2-2202239, S2-2202369, S2-2202662, S2-2202876, S2-2202576. Final response in S2-2203151 Replied to
4.1 S2-2202046 LS OUT Approval Reply LS on Mapped NSSAI Huawei, HiSilicon Rel-17 Response to S2-2201936. r07 agreed. Revised to S2-2203022 Jinguo(ZTE) suggests to use 2662 as basis
Haiyang (Huawei) suggests to use 2046 as baseline.
Robert (Apple) is asking a question for clarification on 2046 and the corresponding proposed CR in 2047.
Tao(VC) please use this thread for discussion of response of 1936, per the checking with people on CC#1.
Haiyang(Huawei) responds to Robert (Apple).
Peter Hedman (Ericsson) provides r04
Genadi (Lenovo) provides r03.
Robert (Apple) provides r02
Alessio(Nokia) provides r01
Guillaume (MediaTek Inc.) comments.
Jinguo(ZTE) asks question for clarification
Guillaume (MediaTek) objects r04, provides r05.
Peter Hedman (Ericsson) provides comments
Haiyang (Huawei) responses to Jinguo(ZTE) , provides r06 for clean up
Guillaume (MediaTek Inc.) object to r06.
Haiyang (Huawei) provides r07
Guillaume (MediaTek Inc.) thanks Haiyang (Huawei)
==== Revisions Deadline ====
alessio(nokia) provides r08 as some wording in r07 was a bit not correct (in our opinion)
Peter Hedman (Ericsson) provides question why r07 was wrong
alessio(Nokia) comments that the rejected s-NSSAI has to include the mirror of what the UE requested and the UE would request the REQUESTED NSSAI with the mapped value in scenarios where it is roaming.
Peter Hedman (Ericsson) provides reply and r08 is not aligned with SA2 specs and prefers to go with r07 + removal of text
Alessio(nokia) is ok with whatever works which is not creating further issues on thisrel-15 topic.
Haiyang (Huawei) provides r09 based on the agreement: which is r07 + removal of text 'A rejected S-NSSAI for the entire Serving PLMN is expected to be provided without a mapped HPLMN S-NSSAI value if the reason of rejection is that there is no mapping info available. However, if the reason of rejection is not due to unavailable mapping info, the Serving PLMN can provide the rejected VPLMN S-NSSAI value with the corresponding mapped HPLMN S-NSSAI value. In both cases, a new configured NSSAI is provided to the UE with the correct mapping for the S-NSSAIs the UE is expected to be able to request in the VPLMN.'
Peter Hedman (Ericsson) ok with r09
==== Comments Deadline ====
alessioi(nokia) ok with r09
Robert (Apple) is ok with r09
Revised
4.1 S2-2203022 LS OUT Approval Reply LS on Mapped NSSAI SA WG2 Rel-17 Revision of S2-2202046r07. Approved. Incorrect attachment provided. Revised to S2-2203151. Revised
4.1 S2-2203151 LS OUT Approval Reply LS on Mapped NSSAI SA WG2 Rel-17 Revision of S2-2203022 Approved
4.1 S2-2202239 LS OUT Approval [DRAFT] Reply LS on Mapped NSSAI Apple (UK) Limited Rel-17 Response to S2-2201936. Noted Jinguo(ZTE) suggest to use 2662 as basis for discussion
Jinguo(ZTE) correct the title since this topic is moved to 4.1
Dongeun (Samsung) objects to this LS response.
Stefano (Qualcomm) objects to this LS response.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2202369 LS OUT Approval [DRAFT] Reply LS on Mapped NSSAI QUALCOMM Europe Inc. - Italy Rel-17 Response to S2-2201936. Noted Jinguo(ZTE) suggests to use 2662 as basis
Apples objects to the LS, especially to the interpretation which is expressed in the answer to question 2 and described in more detail in 2378.
Haiyang (Huawei) comments, agrees with Robert (Apple) and Jinguo (ZTE).
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2202662 LS OUT Approval [DRAFT] Reply LS on Mapped NSSAI ZTE Rel-17 Response to S2-2201936. Noted Peter (Ericsson) provides comments and proposes suggested answer in the mail.
Haiyang (Huawei ) comments on r00 and thinks what Peter (Ericsson) proposes is quite aligned with S2-2202046. Thus suggests to use 2046 as baseline directly.
Guillaume (MediaTek Inc.): ok to use 2662 as placeholder for discussions.
Tao(VC) suggest to use either 2262 or 2046 as the basis. If not agreeable, use 1936 instead. Suggest to check in CC#1.
Robert (Apple): also ok to use 2662 as placeholder for discussions.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2202876 LS OUT Approval [DRAFT] Reply LS on Mapped NSSAI MediaTek Inc. Rel-17 Response to S2-2201936. Noted Jinguo(ZTE) suggest to use 2662 as basis for discussion
Jinguo(ZTE) correct the title since this topic is moved to 4.1
Stefano (Qualcomm) objects to this LS response.
Guillaume (MediaTek Inc.) respectfully disagrees with Stefano (Qualcomm) assessment.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2202576 LS OUT Approval [DRAFT] Reply LS on Mapped NSSAI Lenovo, Motorola Mobility Rel-17 Response to S2-2201936. Noted Jinguo(ZTE) suggest to use 2662 as basis for discussion
Jinguo(ZTE) correct the title since this topic is moved to 4.1
Stefano (Qualcomm) proposes to consider the LS merged into 2369.
Genadi (Lenovo) provides comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2201921 LS In Action LS from RAN WG2: LS on paging subgrouping and PEI RAN WG2 (R2-2111415) Rel-17 Revision of Postponed S2-2200032 from S2#149E. Postponed Qian (Ericsson) proposes to postpone the paper as there is no reply paper in this meeting.
==== Revisions Deadline ====
Postponed
4.1 S2-2201924 LS In Action LS on access to multiple IMS networks via a 5GC network slice CT WG1 (C1-216839) Rel-17 Revision of Postponed S2-2200042 from S2#149E. Noted Rainer (Nokia) proposes to note the LS as CT1 has made no progress on this topic.
==== Revisions Deadline ====
Noted
4.1 S2-2201925 LS In Action LS from CT WG4: Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer CT WG4 (C4-216381) Rel-17 Revision of Postponed S2-2200054 from S2#149E. Response drafted in S2-2202048. Noted Haiyang (Huawei) suggests to note this LS In.
==== Revisions Deadline ====
Noted
4.1 S2-2202048 LS OUT Approval Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer Huawei, HiSilicon Rel-17 Response to S2-2201925. Noted Hannu (Nokia) can't agree with the proposed analysis in this LS. Proposes to re-use the text from S2-2200282r01 in r01.
Haris(Qualcomm) agrees with Hannu (Nokia) analysis and supports r01, or suggests to simply note the incoming LS to not spend further time
Haiyang (Huawei) comments to r01.
Qian (Ericsson) supports r01
Hannu (Nokia) expresses his concern on SA2 working procedures when the same proposal is submitted repeatedly after clear and justified objections have been made against it.
Haiyang (Huawei) cannot accept r01; and can agree with Haris (Qualcomm) to note the incoming LS S2-2201925
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2201940 LS In Action LS from GSMA: Reply LS to 3GPP SA2 on ARP PL GSMA (NRG 012_206r3) Response drafted in S2-2202185. Final response in S2-2203023 Judy (Ericsson) comments that S2-2202170 is not a response to the LS thus to be removed.
==== Revisions Deadline ====
Replied to
4.1 S2-2202185 LS OUT Approval [DRAFT] Reply LS to GSMA NRG on ARP override and GBR alignment for VoLTE roaming Ericsson Rel-17 Response to S2-2201940 and S2-2201970. r01 agreed. Revised to S2-2203023 Judy (Ericsson) provides r01 to take out the GBR part, see discussion in 2186 thread.
==== Revisions Deadline ====
Leo (Deutsche Telekom) supports r01.
==== Comments Deadline ====
Revised
4.1 S2-2203023 LS OUT Approval Reply LS to GSMA NRG on ARP override VoLTE roaming SA WG2 Rel-17 Revision of S2-2202185r01. Approved Approved
4.1 S2-2201941 LS In Action LS from EUWENA: LS on presentation of EUWENA and involvement in 3GPP on Non Public Network EUWENA (LS EUWENA) Noted Rainer (Nokia) proposes to note the LS as there is no action to SA2.
==== Revisions Deadline ====
Noted
4.1 S2-2201951 LS In Action LS from RAN WG2: LS on EPS fallback enhancements RAN WG2 (R2-2204236) Rel-17 Responses drafted in S2-2201997 and S2-2202366. Final response in S2-2203590 Replied to
4.1 S2-2201997 LS OUT Approval Reply LS on EPS fallback enhancements Qualcomm Rel-17 Response to S2-2201951. r09 agreed. Revised to S2-2203590. George Foti (Ericsson) provides r01
Leo (Deutsche Telekom) provides r02
Genadi (Lenovo) provides r03. Prefers to take this LS reply as basis and merge S2-2202366 into this one.
Alessio(Nokia) provides r04.
Haris(Qualcomm) provides r05
Xiaobo (vivo) asks for clarification from George Foti (Ericsson).
Chris provides rev 6 to address Vivo question and clarify that network control is needed for the MO case.
Xiaobo (vivo) thanks clarification from Chris(VDF) and support that network control is needed for the MO case and reword CT1 related content and provides r07.
Wanqiang (Huawei) provides r08.
==== Revisions Deadline ====
Antoine (Orange) : Small changes needed on top of r08.
Leo (Deutsche Telekom) agrees with Orange, r08 can be the basis, but for the final version changes are necessary.
Chris (Vodafone) is OK with r08 but agrees that the Orange comments are valid. If editing, one extra typo should be fixed.
Haris(Qualcomm) provides post deadline r09 to discuss in CC
Xiaobo (vivo) is ok with r09 and thanks Haris for the update.
==== Comments Deadline ====
Revised
4.1 S2-2203590 LS OUT Approval Reply LS on EPS fallback enhancements SA WG2 Rel-17 Revision of S2-2201997r09. Approved Approved
4.1 S2-2202366 LS OUT Approval [DRAFT] Reply LS on EPS fallback enhancements Huawei, HiSilicon Rel-17 Response to S2-2201951. Noted George Foti (Ericsson) objects to the LS
Leo (Deutsche Telekom) also objects to the LS. For the reply LS SA2 should continue with S2-2201997
Jungshin (Samsung): We also object to the proposed LS.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
4.1 S2-2201960 LS In Action LS from SA WG4: LS on Traffic Identification within 5G Media Streaming SA WG4 (S4-220305) Rel-17 Response drafted in S2-2202188. This was postponed. Postponed
4.1 S2-2202188 LS OUT Approval [DRAFT] Reply LS on Traffic Identification within 5G Media Streaming Ericsson Rel-17 Response to S2-2201960. This was postponed. Pallab (Nokia) proposes to first discuss and agree on the CR proposed in 2189 before agreeing on the LS OUT
==== Revisions Deadline ====
Pallab (Nokia) proposes r01 of the LS OUT based on discussions in 2189
Judy (Ericsson) request to discuss in CC#2, see discussion in 2189 thread
==== Comments Deadline ====
Postponed
4.1 S2-2202189 CR Approval 23.502 CR3431 (Rel-17, 'F'): Traffic Identification using ToS/TC for 5G Media Streaming Ericsson Rel-17 This was postponed. Pallab (Nokia) comments and asks for clarification
Judy (Ericsson) responds to Pallab (Nokia)
Pallab (Nokia) responds to Judy (Ericsson)
Haiyang (Huawei) comments; suggests to generate a 503 CR to update description of flow description.
Haiyang (Huawei) clarifies
Judy (Ericsson) responds to Pallab (Nokia) and asks Haiyang (Huawei) for clarification
Judy (Ericsson) ask further questions
Haiyang (Huawei) further responds
Dario (Qualcomm) provides r01
Judy (Ericsson) provides r03 based on r00 and comments, please ignore r02.
Pallab (Nokia) asks if we can agree that there is no need for this CR and reply to SA4 accordingly
Dario (Qualcomm) comments.
Judy (Ericsson) propose to go with the CR proposal to support the SA4 use case.
Pallab (Nokia) proposes to NOTE the CR and respond to SA4 accordingly
==== Revisions Deadline ====
Dario (Qualcomm) is fine with noting the CR.
Judy (Ericsson) does not agree to note this CR as there is no technical argument provided, and requests we allow for services deployment support by the operators with knowledge of responsibility documented in 3GPP specs.
Pallab (Nokia) responds to Judy (Ericsson) and maintains the position to NOTE the paper. Proposes LS OUT draft revision to SA4
Judy (Ericsson) does not agree it is 3GPP scope to specify 'How the operator and the external DN (service provider) can collaborate' in the context of the discussion, and request to discuss in CC#2
==== Comments Deadline ====
Postponed
4.1 S2-2201945 LS In Action LS from RAN WG2: LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure RAN WG2 (R2-2203691) Rel-16 Response drafted in S2-2202376. Final response in S2-2203024 Replied to
4.1 S2-2202376 LS OUT Approval [DRAFT] Reply LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure CATT Rel-16 Response to S2-2201945. r00 agreed. Revised to S2-2203024 Hannu (Nokia) provides r01 to improve the wording.
Deng Qiang (CATT) comments on r01.
LaeYoung (LGE) answers to Hannu (Nokia).
Hannu (Nokia) answers to Deng Qiang
Fei (OPPO) comments
Steve (Huawei) has a preference for r00
LaeYoung (LGE) also prefers r00, so proposes to go with r00.
==== Revisions Deadline ====
Hannu (Nokia) still prefers r01 but can also live with r00.
==== Comments Deadline ====
Revised
4.1 S2-2203024 LS OUT Approval Reply LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure SA WG2 Rel-16 Revision of S2-2202376r00. Approved Approved
4.1 S2-2201964 LS In Action LS from ETSI EMTEL: LS response to 3GPP SA1 on IMS emergency communication improvement - SMS to emergency centre ETSI EMTEL (EMTEL(22)000042) Noted Vodafone proposes to note this LS. Response to EMTEL should be sent by SA1.
Leo (Deutsche Telekom) also requests to note this LS. Response to EMTEL should be sent by SA1.
Rainer (Nokia) agrees to not the LS as it is asking to add requirements to 3gpp specs.
==== Revisions Deadline ====
Noted
4.1 S2-2201970 LS In Information LS from GSMA: LS to 3GPP SA2 on VoLTE Roaming GBR Handling GSMA (NRG 13_201r2) Response drafted in S2-2202185. Postponed Judy (Ericsson) comments this LS is also responded in S2-2202185 thus to be added in 'Comments' column.
==== Revisions Deadline ====
Leo (Deutsche Telekom) proposes to POSTPONE the LS-in, VoLTE Roaming GBR Handling is proposed to be discussed at the next SA2 meeting.
Postponed
4.1 S2-2202775 LS In Action Reply LS on mandatory SSC modes supported by UE CT WG1 (C1-222033) Rel-15 Noted Hui (Huawei) proposes to note this LS.
Stefan (Ericsson) agrees that it can be noted
==== Revisions Deadline ====
Noted
4.1 S2-2202780 LS In Action LS from CT WG4: Reply-LS on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get CT WG4 (C4-221079) Rel-17 Noted Leo (Deutsche Telekom) proposes to NOTE the LS
Qian (Ericsson) supports to NOTE the LS as SA2 spec covered the aspect already.
==== Revisions Deadline ====
Noted
4.1 S2-2202781 LS In Information LS from CT WG4: Reply LS On User Consent Updating CT WG4 (C4-221413) Rel-17 Noted Leo (Deutsche Telekom) proposes to NOTE the LS, there is no action for SA2.
==== Revisions Deadline ====
Noted
4.1 S2-2202789 LS In Information LS from RAN WG3: Reply LS on paging subgrouping and PEI RAN WG3 (R3-222874) Rel-17 Noted Steve (Huawei) Proposes to note.
==== Revisions Deadline ====
Noted
4.1 S2-2202793 LS In Information LS from SA WG3: Reply LS on User Consent Updating SA WG3 (S3-220474) Rel-17 Noted Leo (Deutsche Telekom) proposes to NOTE the LS, there is no action for SA2.
==== Revisions Deadline ====
Noted
4.1 S2-2202798 LS In Information LS on Alignment concerning 5G RG requirements and its remote management TSG SA (SP-220347) Rel-18 Noted Noted
4.1 S2-2202783 LS In Information LS from BBF: 3GPP TS 29.244 BBF (LIAISE-507-02) Noted Noted
4.1 S2-2202784 LS In Information LS from BBF: ATSSS and Co-located AGF-UPF procedures BBF (LIAISE-519) Response drafted in S2-2202242. Final response in S2-2203021 Replied to
4.1 S2-2202242 LS OUT Approval [DRAFT] Reply LS on ATSSS and Co-located AGF-UPF procedures Ericsson Rel-17 Response to S2-2202784. r00 agreed. Revised to S2-2203021 Revised
4.1 S2-2203021 LS OUT Approval Reply LS on ATSSS and Co-located AGF-UPF procedures SA WG2 Rel-17 Revision of S2-2202242r00. Approved Approved
4.1 S2-2201983 CR Approval 23.316 CR2063 (Rel-17, 'F'): Generalizing NAS transport between 5G and W-AGF to accommodate latest BBF developments Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Approved Agreed
4.1 S2-2201996 CR Approval 23.501 CR3496R1 (Rel-16, 'F'): Requirement for signalling separate IMEI for each network subscription Qualcomm Incorporated Rel-16 Revision of (Postponed) S2-2200386 from S2#149E. r01 agreed. Revised to S2-2203026 Rainer (Nokia) provides comment.
Haris(Qualcomm) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
4.1 S2-2203026 CR Approval 23.501 CR3496R2 (Rel-16, 'F'): Requirement for signalling separate IMEI for each network subscription Qualcomm Incorporated Rel-16 Revision of S2-2201996r01. Approved Agreed
4.1 S2-2202171 CR Approval 23.316 CR2064 (Rel-17, 'F'): Alignment to BBF LS 512 (Frame route, BBF references) Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2203030 Stefan (Ericsson) provides r01
Laurent (Nokia): provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
4.1 S2-2203030 CR Approval 23.316 CR2064R1 (Rel-17, 'F'): Alignment to BBF LS 512 (Frame route, BBF references) Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2202171r02. Approved Agreed
4.1 S2-2202172 CR Approval 23.501 CR3591 (Rel-17, 'F'): Alignment to BBF LS 512 (Frame route, BBF references) Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2203031 Marco (Huawei) provide r01 with editorial clean up
Marco (Huawei)
Stefan (Ericsson) provides r02
==== Revisions Deadline ====
Marco (Huawei) agree r02 (reference missing in chair note)
==== Comments Deadline ====
Revised
4.1 S2-2203031 CR Approval 23.501 CR3591R1 (Rel-17, 'F'): Alignment to BBF LS 512 (Frame route, BBF references) Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2202172r02. Approved Agreed
4.1 S2-2202186 CR Approval 23.401 CR3695 (Rel-17, 'F'): Handling of ARP and GBR for IMS voice service in home routed roaming Ericsson, Deutsche Telekom Rel-17 r06 agreed. Revised to S2-2203027 Robert (Peraton Labs) provides r01
Judy (Ericsson) provides r02
Judy (Ericsson) is fine with r03 and responds to Mirko (Huawei) and Chris (Vodafone)
So far this discussion has covered both 5GC and EPC but Chris (Vodafone) suggests that Alternative QoS Profiles are used for the GBR issue on 5GC.
Mirko (Huawei) comments.
Leo (Deutsche Telekom) provides r03
Chris (Vodafone) repeats his request for an explanation of how rev 3 works. Alt QoS remains a possibility for 5GC.
Judy (Ericsson) responds to Chris (Vodafone)
Chris (Vodafone) answers on Alt QoS and requests an explanation of how rev 3 works
Judy (Ericsson) responds to Chris (Vodafone) and provides r06 taking out GBR downgrade.
==== Revisions Deadline ====
Leo (Deutsche Telekom) prefers r06, and objects to r01.
Chris (Vodafone) is OK with r06 (which solves the ARP issue). We need to work on the GBR issue at the next SA2.
==== Comments Deadline ====
Revised
4.1 S2-2203027 CR Approval 23.401 CR3695R1 (Rel-17, 'F'): Handling of ARP for IMS voice service in home routed roaming Ericsson, Deutsche Telekom Rel-17 Revision of S2-2202186r06. Approved Agreed
4.1 S2-2202187 CR Approval 23.501 CR3593 (Rel-17, 'F'): Handling of ARP and GBR for IMS voice service in home routed roaming Ericsson, Deutsche Telekom Rel-17 r07 agreed. Revised to S2-2203028 Robert (Peraton Labs) provides r01
Judy (Ericsson) provides r02
Chris (Vodafone) suggests that Alternative QoS Profiles are used for the GBR issue on 5GC.
Mirko (Huawei) comments.
Leo (Deutsche Telekom) provides r03
Judy (Ericsson) is fine with r03 and responds to Chris (Vodafone) & Mirko (Huawei).
==== Revisions Deadline ====
Chris (Vodafone) objects to all versions of this CR. This is stop misalignment with S2-2202186. We need to revisit this in the next SA2.
Leo (Deutsche Telekom) asks VF to withdraw objection for r07.
Judy (Ericsson) also ask Chris (Vodafone) to withdraw objection against r07 which is fully aligned with 2186
Chris (Vodafone) withdraws his objection and is OK with r07.
==== Comments Deadline ====
Revised
4.1 S2-2203028 CR Approval 23.501 CR3593R1 (Rel-17, 'F'): Handling of ARP for IMS voice service in home routed roaming Ericsson, Deutsche Telekom Rel-17 Revision of S2-2202187r07. Approved Agreed
4.1 S2-2202190 CR Approval 23.501 CR3594 (Rel-17, 'F'): RRC state terminology alignment Ericsson Rel-17 Postponed Hannu (Nokia) proposes to mark S2-2202190 and S2-2202191 as 'not handled' since 5GS_Ph1 is not on the agenda.
Shabnam (Ericsson) Clarifies that as other Rel-17 new spec like MBS starting to align terminology with base specs 501 and 502, we need to get agreement on this in April.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202191 CR Approval 23.502 CR3432 (Rel-17, 'F'): RRC state terminology alignment Ericsson Rel-17 Postponed Tao(VC) correct the title with correct tdoc number.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202241 CR Approval 23.316 CR2065 (Rel-17, 'F'): Additional support for selecting UPF collocated with W-AGF Ericsson Rel-17 r02 agreed. Revised to S2-2203025 Laurent (Nokia): provides r01
Stefan (Ericsson) changing to correct AI in subject. OK with r01
Marco (Huawei) question for clarification and some doubts
Stefan (Ericsson) provides replies to Marco
Marco (Huawei) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
4.1 S2-2203025 CR Approval 23.316 CR2065R1 (Rel-17, 'F'): Additional support for selecting UPF collocated with W-AGF Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202241r02. Approved Agreed
4.1 S2-2202375 DISCUSSION Discussion Discussion on Source Layer-2 ID of first PC5-S unicast message. CATT, LG Electronics, Deutsche Telekom Rel-16 Noted Noted
4.1 S2-2201937 LS In Action LS on handling of packet filters when the supported number is exceeded CT WG3 (C3-221503) Rel-17 Responses drafted in S2-2202182, S2-2202448, S2-2202825. Postponed Pallab (Nokia) also agrees to discuss the proposals in this thread. Also provides comments on the related CRs
zhendong (ZTE) agree to use this as discussion reflector
Judy (Ericsson) comments that there are 3 sets of papers with different solutions and propose to use this thread for solution discussion.
Peter (Vodafone) agrees with the text in draft LS out in S2-2202182 that the decision on packet filters for TFT is to be based on operator policy, as also proposed in S2-2202825. Vodafone also prefers the response proposed in S2-2202182 or S2-2202825 rather than the response in S2-2202448.
Mirko (Huawei) comments that the solution has to allow that more than 16 packet filters can be assigned to a PDU session eligible for EPS IWK.
Sebastian (Qualcomm) comments
Judy (Ericsson) share Mirko (Huawei)'s view, thanks Sebastian (Qualcomm)'s support for Set 1 papers and propose to continue the revisions on Set 1 (2182, 2183, 2184).
zhendong (ZTE) provides the comments
Judy (Ericsson) responds to zhendong (ZTE)
Pallab (Nokia) comments
Mirko (Huawei) responds.
zhendong (ZTE) provides the repsonse
Sebastian (Qualcomm) replies to Zhendong
Mirko (Huawei) comments.
zhendong (ZTE) ask question for clarificaiton
zhendong (ZTE) provides response to mirko
Judy (Ericsson) responds to Mirko (Huawei), zhendong (ZTE) and Pallab (Nokia)
zhendong (ZTE) provides the response to nokia
Pallab (Nokia) respond to zhendong (ZTE)
Pallab (Nokia) responds to Judy (Ericsson)
Sebastian (Qualcomm) suggests to postpone all CRs and the reply LS given that no solution seems to be agreeable this time
zhendong (ZTE) is fine to have more discussion.
Pallab (Nokia) is also OK to postpone and have more discussion.
Sebastian (Qualcomm) kindly asks authors of all related CRs and draft LSs to indicate in the respective threads that the papers should be marked postponed
Judy (Ericsson) is OK with the postponement if preferred by the majority
==== Revisions Deadline ====
Postponed
4.1 S2-2202182 LS OUT Approval [DRAFT] Reply to LS handling of packet filters when the supported number is exceeded Ericsson Rel-17 Response to S2-2201937. Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202448 LS OUT Approval [DRAFT] LS OUT on handling of packet filters when the supported number is exceeded; Response to S2-2201937 Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2201937. Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202825 LS OUT Approval [DRAFT] Reply LS On handling of packet filters when the supported number is exceeded ZTE Response to S2-2201937. Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
zhendong (ZTE) is fine to postpone
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202183 CR Approval 23.502 CR3430 (Rel-17, 'F'): Number of TFT filters exceeding allowed limit for 5GS to EPS interworking Ericsson Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
Mirko (Huawei) provides r01.
Judy (Ericsson) thanks Mirko (Huawei) for the revision and is fine with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202184 CR Approval 23.503 CR0712 (Rel-17, 'F'): Number of TFT filters exceeding allowed limit for 5GS to EPS interworking Ericsson Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
Mirko (Huawei) provides r01.
Judy (Ericsson) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202449 CR Approval 23.503 CR0713 (Rel-17, 'F'): Handling of number of supported Packet Filters for signalled QoS rules for the PDU Session with EPS IWK Nokia, Nokia Shanghai Bell Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202450 CR Approval 23.502 CR3444 (Rel-17, 'F'): Handling of number of supported Packet Filters for signalled QoS rules for the PDU Session with EPS IWK Nokia, Nokia Shanghai Bell Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202451 CR Approval 23.501 CR3608 (Rel-17, 'F'): Handling of number of supported Packet Filters for signalled QoS rules for the PDU Session with EPS IWK Nokia, Nokia Shanghai Bell Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202823 CR Approval 23.502 CR3455 (Rel-16, 'F'): Clarification on the TFT exceeding 16 for 5GS-EPS interworking ZTE Rel-16 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
zhendong (ZTE) is fine to postpone
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2202824 CR Approval 23.502 CR3456 (Rel-17, 'A'): Clarification on the TFT exceeding 16 for 5GS-EPS interworking ZTE Rel-17 Postponed Judy (Ericsson) comments the discussion is in S2-2201937 thread.
zhendong (ZTE) is fine to postpone
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
4.1 S2-2201938 LS In Information LS from BBF: EAP-5G change; Answer to S2-2109043 BBF (LIAISE-508-02) Response drafted in S2-2201984. Final response in S2-2203017 Endorsed
4.1 S2-2201984 LS OUT Approval Reply LS on EAP-5G change Ericsson Rel-17 Response to S2-2201938. r00 agreed. Revised to S2-2203017 Revised
4.1 S2-2203017 LS OUT Approval Reply LS on EAP-5G change SA WG2 Rel-17 Revision of S2-2201984r00. Approved Approved
4.1 S2-2201939 LS In Information LS from BBF: LS on 5GC Support of DHCP signaling for RG; Response to S2-2009340 BBF (LIAISE-512-on DHCP to SA-03) Response drafted in S2-2202170. Final response in S2-2203029 Replied to
4.1 S2-2202170 LS OUT Approval [DRAFT] LS on LS on 5GC Support of DHCP signaling for RG Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2201939. r01 agreed. Revised to S2-2203029 Judy (Ericsson) comments this reply is not a response to S2-2201940 but a response to S2-2009340
Judy (Ericsson) agrees with Tao.
Tao(VC) clarifies the response to 1939
Laurent (Nokia): provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
4.1 S2-2203029 LS OUT Approval LS on LS on 5GC Support of DHCP signaling for RG; SA WG2 Rel-17 Revision of S2-2202170r01. Approved Approved
4.2 - - - P-CRs/CRs related to use of inclusive language in 3GPP - - Docs:=0 -
8 - - - Pre-Rel-17 Maintenance (excluding all 5G topics) - - Docs:=0 -
8.1 - - - Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) - - Docs:=33 -
8.1 S2-2201993 CR Approval 23.288 CR0510 (Rel-17, 'F'): Clarification on historical data and analytics storage via MFAF China Telecom, Huawei, Hisilicon Rel-17 r02 agreed. Revised to S2-2203217 Zhang (Ericsson) provides comments and r01
Yannick (Nokia): Nokia provides comments on r00.
Jiahui (China Telecom) provides comments and agrees with r01
Yannick (Nokia): Nokia provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203217 CR Approval 23.288 CR0510R1 (Rel-17, 'F'): Clarification on historical data and analytics storage via MFAF China Telecom, Huawei, Hisilicon, Ericsson, Nokia Rel-17 Revision of S2-2201993r02. Approved Agreed
8.1 S2-2201994 CR Approval 23.288 CR0511 (Rel-17, 'F'): Alignment and corrections on analytics subscription procedures China Telecom, Huawei, Hisilicon Rel-17 r04 agreed. Revised to S2-2203218 Yannick (Nokia): Nokia provides comments.
Jiahui (China Telecom): China Telecom provides r01.
Yannick (Nokia): Nokia provides r02.
Kenichi (KDDI: KDDI provides comment for r02.
Yannick (Nokia): Nokia provides r03.
Kenichi (KDDI): provides r04 for adding KDDI as co-signer.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203218 CR Approval 23.288 CR0511R1 (Rel-17, 'F'): Alignment and corrections on analytics subscription procedures China Telecom, Huawei, Hisilicon, Nokia, KDDI Rel-17 Revision of S2-2201994r04. Approved Agreed
8.1 S2-2202045 CR Approval 23.288 CR0512 (Rel-17, 'F'): Inputs update for Nnwdaf Notify services for missing elements China Telecom Rel-17 r01 agreed. Revised to S2-2203219 Leo (Deutsche Telekom) provides r01.
Zhuoyi (China Telecom) accepts r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203219 CR Approval 23.288 CR0512R1 (Rel-17, 'F'): Inputs update for NWDAF Notify services for missing elements China Telecom Rel-17 Revision of S2-2202045r01. Approved Agreed
8.1 S2-2202085 CR Approval 23.502 CR3426 (Rel-17, 'F'): Correction to Naf_EventExposure service Ericsson Rel-17 r02 agreed. Revised to S2-2203220 Wang Yuan (Huawei) provides comments.
Yannick (Nokia): Nokia provides comments.
Belen (Ericsson) provides r01.
Yannick (Nokia): Nokia provides comments on r01.
Belen (Ericsson) provides r02
==== Revisions Deadline ====
Wang Yuan (Huawei) is fine with r02.
==== Comments Deadline ====
Revised
8.1 S2-2203220 CR Approval 23.502 CR3426R1 (Rel-17, 'F'): Correction to Naf_EventExposure service Ericsson Rel-17 Revision of S2-2202085r02. Approved Agreed
8.1 S2-2202086 CR Approval 23.288 CR0513 (Rel-17, 'F'): Correction to Dispersion Analytics Ericsson Rel-17 r02 agreed. Revised to S2-2203221 David (Spirent) updates Ericsson's Dispersion analytics addition of 'any UE'
Belen (Ericsson) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203221 CR Approval 23.288 CR0513R1 (Rel-17, 'F'): Correction to Dispersion Analytics Ericsson, Spirent Rel-17 Revision of S2-2202086r02. Approved Agreed
8.1 S2-2202118 CR Approval 23.288 CR0516 (Rel-17, 'F'): Clarify the data and analytics storage in ADRF Huawei, HiSilicon Rel-17 Merged into S2-2203226 Yannick (Nokia): Nokia notes there is similar proposal from Vivo in S2-2202498. Can these two contributions be merged?
Vivian(vivo) has provided a merged version using S2-2202498 as baseline, and asks for your opinion on whether agree it or not?
Wang Yuan (Huawei) is ok to merge this CR into S2-2202498.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.1 S2-2202119 DISCUSSION Agreement Discussion on the parameter 'list of analytics subsets that are requested'. Huawei, HiSilicon Rel-17 Noted Noted
8.1 S2-2202120 CR Approval 23.288 CR0517 (Rel-17, 'F'): Clarify the Analytics subset per different Analytics ID Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2203222 Yannick (Nokia): Nokia provides comments, can only accept changes in clause 6.5.3.
Belen (Ericsson) provides comments, objects to the CR in the current form
Wang Yuan (Huawei) replies to Yannick (Nokia) and Belen (Ericsson), and provides r01.
Belen (Ericsson) cannot accept r01
David (Samsung) cannot accept current changes in cl. 6.5.3 for both r00 and r01
Wang Yuan (Huawei) replies to Belen (Ericsson) and David (Samsung), and provides r02.
Yannick (Nokia): Nokia is ok with r02.
Yannick (Nokia): Nokia request that cover page is updated according to latest development for the CR.
Yannick (Nokia): Nokia is fine with r03.
Wang Yuan (Huawei) replies to Yannick (Nokia), and provides r03.
Belen (Ericsson) is okay with r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203222 CR Approval 23.288 CR0517R1 (Rel-17, 'F'): Clarify the Analytics subset per different Analytics ID Huawei, HiSilicon Rel-17 Revision of S2-2202120r03. Approved Agreed
8.1 S2-2202248 CR Approval 23.288 CR0518 (Rel-17, 'F'): Adding UE ID to the Service Data from AF related to the Observed Service Experience InterDigital Inc. Rel-17 Approved Mike (InterDigital) replies to Zhuoyi
Zhuoyi (China Telecom) provides comments
Zhuoyi (China Telecom) replies to Mike.
Belen (Ericsson) provides comments
Mike (InterDigital) replies to Belen and Zhuoyi
==== Revisions Deadline ====
==== Comments Deadline ====
Agreed
8.1 S2-2202337 CR Approval 23.502 CR3441 (Rel-17, 'F'): Add NWDAF as a consumer NF of the Nnsacf_SliceEventExposure services Huawei, HiSilicon Rel-17 Merged into S2-2203224 Wang Yuan (Huawei) proposes to merge this CR into S2-2202664 per offline discussion with Jinguo (ZTE).
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.1 S2-2202117 CR Approval 23.288 CR0515 (Rel-17, 'F'): Alignment on the data collection from NSACF Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2203223, merging S2-2202663 Yannick (Nokia): Nokia provides comments and request for clarification. Also notes that there is a similar proposal in S2-2202663 so a merge would be needed.
Wang Yuan (Huawei) replies to Yannick and provide r01 (also merge S-2202663 into this CR Per offline discussion with Jinguo (ZTE)).
Yannick (Nokia): Nokia provides r02.
Wang Yuan (Huawei) is OK with r02.
Jinguo(ZTE) is ok with r02
==== Revisions Deadline ====
Jinguo(ZTE) suggest to approve r02
Yannick (Nokia): Nokia also supports approving r02.
==== Comments Deadline ====
Revised
8.1 S2-2203223 CR Approval 23.288 CR0515R1 (Rel-17, 'F'): Alignment on the data collection from NSACF Huawei, HiSilicon, ZTE Rel-17 Revision of S2-2202117r02, merging S2-2202663. Approved Agreed
8.1 S2-2202664 CR Approval 23.502 CR3450 (Rel-17, 'F'): Adding NWDAF as service consumer of NSACF ZTE Rel-17 r01 agreed. Revised to S2-2203224, merging S2-2202337 Yannick (Nokia): Nokia provides comment. Also notes that there is similar proposal in S2-2202337.
Jinguo(ZTE) provides r01
==== Revisions Deadline ====
Wang Yuan (Huawei) ae fine with r01, thanks Jinguo.
==== Comments Deadline ====
Revised
8.1 S2-2203224 CR Approval 23.502 CR3450R1 (Rel-17, 'F'): Adding NWDAF as service consumer of NSACF ZTE,Huawei Rel-17 Revision of S2-2202664r01, merging S2-2202337. Approved Agreed
8.1 S2-2202663 CR Approval 23.288 CR0522 (Rel-17, 'F'): Adding the NSACF as NWDAF data source ZTE Rel-17 Merged into S2-2203223 Yannick (Nokia): Nokia provides comments. Also notes that there is similar proposal in S2-2202117.
Jinguo(ZTE) propose to merge this paper into 2117.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.1 S2-2202420 CR Approval 23.288 CR0488R2 (Rel-17, 'F'): Clarification of transferring ML model during analytics transfer Lenovo, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2200808. r06 agreed. Revised to S2-2203225 Xiaoyan (CATT) provides r02.
Xiaoyan (CATT) provides r01.
Dimitris (Lenovo) comments
Yannick (Nokia): Nokia provides r03 and asks Xiaoyan to not delete changes in previous versions without change marks, otherwise it is hard to get the new changes in each version.
Malla (NTT DOCOMO) asks clarification on r03.
Yannick (Nokia): Nokia replies to NTT DOCOMO.
Malla (NTT DOCOMO) replies to Nokia.
Xiaoyan (CATT) provides r04.
Malla (NTT DOCOMO) replies to Yannick (Nokia).
Yannick (Nokia): Nokia provides r05. Objects to r04.
Xiaoyan (CATT) provides r06.
Yannick (Nokia): Nokia is fine with r06.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203225 CR Approval 23.288 CR0488R3 (Rel-17, 'F'): Clarification of transferring ML model during analytics transfer Lenovo, Nokia, Nokia Shanghai Bell, CATT Rel-17 Revision of S2-2202420r06. Approved Agreed
8.1 S2-2202498 CR Approval 23.288 CR0519 (Rel-17, 'F'): Update inputs parameters for the Nadrf_DataManagement_StorageRequest service Vivo Rel-17 r01 agreed. Revised to S2-2203226, merging S2-2202118 Yannick (Nokia): Nokia notes there is similar proposal from Huawei in S2-2202118. Can these two contributions be merged?
Vivian(vivo) replies to Yannick (Nokia) comment and gives a merged version r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203226 CR Approval 23.288 CR0519R1 (Rel-17, 'F'): Update inputs parameters for the Nadrf_DataManagement_StorageRequest service Vivo Rel-17 Revision of S2-2202498r01, merging S2-2202118. Approved Agreed
8.1 S2-2202499 CR Approval 23.288 CR0520 (Rel-17, 'F'): Clarification on data collection with Event Muting Mechanism Vivo Rel-17 r01 agreed. Revised to S2-2203227 Yannick (Nokia): Nokia requests for clarification.
Vivian(vivo) replies to Yannick (Nokia)'s comments and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203227 CR Approval 23.288 CR0520R1 (Rel-17, 'F'): Clarification on data collection with Event Muting Mechanism Vivo Rel-17 Revision of S2-2202499r01. Approved Agreed
8.1 S2-2202500 CR Approval 23.288 CR0521 (Rel-17, 'F'): Update ML model to AI/ML model for AI terminology alignment Vivo Rel-17 Noted Yannick (Nokia): Nokia do not see the need for this correction in Rel-17.
Xiaobo (vivo) provides comments.
Xiaobo (vivo) provides additional comments.
Yannick (Nokia): Nokia replies to Vivo.
Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) provided comment.
David (Samsung) agrees with previous companies and would prefer to leave the terminology in R17 as it is now
Xiaobo (vivo) request Tricci(OPPO) or David(Samsung) for clarification about the meaning of AI/ML model in R18 SA2 SID FS_AIMLsys and in SA1 WID AI/ML model transfer in 5GS .
Xiaobo (vivo) provides response to Zhang(Ericsson)/Malla(NTT DoCoMo)/David(Samsung).
Yannick (Nokia): Nokia replies to Vivo. Suggest we do not discuss this in the context of Rel-17 maintenance, rather this seems more a discussion for e.g. AIMLsys work in Rel-18. We should note this Rel-17 CR.
David (Samsung) replies to Xiaobo.
Xiaobo (vivo) provides response and agree to note this CR and postpone the discussion to R18
Yannick (Nokia): Nokia thanks Vivo for agreeing to postpone this discussion.
David (Samsung) supports latest comments by Yannick (Nokia) and agrees with the way forward proposed by Xiaobo (vivo).
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.1 S2-2202678 CR Approval 23.288 CR0462R3 (Rel-17, 'F'): Clarify the Redundant Transmission Experience related analytics China Mobile, Huawei Rel-17 Revision of (Postponed) S2-2200971. r04 agreed. Revised to S2-2203228, merging S2-2202726 Juan Zhang (Qualcomm) provides comments.
Susan (Huawei) replies to Antoine (Orange).
Antoine (Orange) asks a question and indicates that this CR clashes with 2-2202726.
Susan (Huawei) replies to Juan Zhang (Qualcomm).
Yannick (Nokia): Nokia provides r01 with contents from S2-2202726.
Antoine (Orange) provides r02.
Yannick (Nokia): Nokia replies to Huawei.
Susan (Huawei) replies to Yannick (Nokia).
Yannick (Nokia): Nokia asks Huawei for further clarification.
Yannick (Nokia): Nokia asks Huawei for clarification.
Susan (Huawei) provides r03.
Susan (Huawei) provides r04.
Yannick (Nokia): Nokia is fine with r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.1 S2-2203228 CR Approval 23.288 CR0462R4 (Rel-17, 'F'): Clarify the Redundant Transmission Experience related analytics China Mobile, Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202678r04, merging S2-2202726. Approved Agreed
8.1 S2-2202726 CR Approval 23.288 CR0523 (Rel-17, 'F'): Corrections to Redundant Transmission Experience analytics Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2203228 Aihua(CMCC) provides comments.
Susan (Huawei) propose to merge this CR to S2-2202678.
Antoine (Orange) asks if one of the changes is really FASMO and indicates that this CR clashes with S2-2202678.
Yannick (Nokia): Nokia replies to Orange and Huawei.
Yannick (Nokia): Nokia asks Huawei for clarification.
Susan (Huawei) replies to Yannick.
Yannick (Nokia): Nokia request convenor to mark this CR as merged into S2-2202678.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.1 S2-2202727 CR Approval 23.502 CR3453 (Rel-17, 'F'): Corrections to Redundant Transmission Experience for SMF event exposure Nokia, Nokia Shanghai Bell Rel-17 Approved Agreed
8.1 S2-2202925 CR Approval 23.288 CR0524 (Rel-17, 'F'): Clarification for analytics subscription transfer for group of UEs and for any UE Nokia, Nokia Shanghai Bell Rel-17 Noted Zhang (Ericsson) provides comments
Antoine (Orange) proposes to make the 2nd bullet more general.
Wang Yuan (Huawei) provides comments.
Malla (NTT DOCOMO) asks for clarification.
Yannick (Nokia): Nokia provides r01, and answers to comments from Orange, NTT DOCOMO, Ericsson and Huawei.
Yingying(CATT) provides comments.
Yannick (Nokia): Nokia replies to Ericsson.
Zhang (Ericsson) response to Nokia
Yannick (Nokia): Nokia replies to Ericsson and asks Ericsson to explain the issue they see.
Zhang (Ericsson) provides r02 and co-sign the paper
Yannick (Nokia): Nokia objects to r02.
Yannick (Nokia): Nokia asks Ericsson for clarification.
Zhang (Ericsson) object r01 and the original version
Yannick (Nokia): Nokia kindly asks Zhang (Ericsson) to not use text from the CR out of the context, that can only introduce confusion. We are discussing subscription or a group of UEs, while the quoted text is for subscription for any UE.
==== Revisions Deadline ====
Yannick (Nokia): Nokia replies to Ericsson. It would be good to focus the discussion on the technical contents of the CR at stake, not on digging old emails nor on quoting text out of context.
Zhang (Ericsson) kindly ask Nokia to have clear assumption or mind before discussion
==== Comments Deadline ====
Noted
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=34 -
8.2 S2-2201918 LS In Action LS from CT WG1: LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 CT WG1 (C1-215137) Rel-16 Revision of Postponed S2-2200007 from S2#149E. Response drafted in S2-2202157. Final response in S2-2203419 Replied to
8.2 S2-2201926 LS In Action LS from SA WG1: LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 SA WG1 (S1-214234) Rel-16 Revision of Postponed S2-2200061 from S2#149E. Response drafted in S2-2202157. Final response in S2-2203419 Replied to
8.2 S2-2202157 LS OUT Approval [DRAFT] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 Ericsson Rel-16 Response to S2-2201918 and S2-2201926. r01 agreed. Revised to S2-2203419 Josep (DT) comments, provides r01.
Peter Hedman (Ericsson) provides reply
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.2 S2-2203419 LS OUT Approval Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 SA WG2 Rel-16 Revision of S2-2202157r01. Approved Approved
8.2 S2-2201920 LS In Action LS from SA WG3: LS on conclusions of authentication methods for initial access for onboarding. SA WG3 (S3-214334) Rel-17 Revision of Postponed S2-2200029 from S2#149E. Postponed Postponed
8.2 S2-2201955 LS In Action LS from SA WG3: REPLY LS on support of DCS variants in UE Onboarding Architecture SA WG3 (S3-220493) Rel-17 Noted Rainer (Nokia) proposes to note the LS.
==== Revisions Deadline ====
Noted
8.2 S2-2201961 LS In Action LS from SA WG4: LS on Media Production over 5G NPN SA WG4 (S4-220328) Rel-17 Response drafted in S2-2202639. Final response in S2-2203417 Replied to
8.2 S2-2202639 LS OUT Approval [DRAFT] Reply LS on Media Production over 5G NPN Qualcomm Rel-17 Response to S2-2201961. Revised to S2-2203417. Revised
8.2 S2-2203417 LS OUT Approval Reply LS on Media Production over 5G NPN SA WG2 Rel-17 Revision of S2-2202639. Approved Approved
8.2 S2-2202790 LS In Action LS from SA WG3: LS on conclusions of authentication methods for initial access for onboarding SA WG3 (S3-214541) Rel-17 Noted Peter (Ericsson) proposes to note the LS as it is outdated
==== Revisions Deadline ====
Noted
8.2 S2-2201998 CR Approval 23.501 CR3581 (Rel-17, 'F'): Role of Credential Holder Qualcomm Incorporated Rel-17 r03 agreed. Revised to S2-2203420 Peter (Ericsson) provides comments and r01
Josep (DT) proposes to NOTE this CR. Not FASMO
Haris(Qualcomm) replies why the CR is FASMO
Josep (DT) replies.
Haris(Qualcomm) provides comments
Josep (DT) comments, provides r02.
Peter Hedman (Ericsson) provides r03
==== Revisions Deadline ====
Josep (DT) is fine with r03, objects to r00, r01.
Rainer (Nokia) is ok with r03.
Haris(Qualcomm) is ok w r03
==== Comments Deadline ====
Revised
8.2 S2-2203420 CR Approval 23.501 CR3581R1 (Rel-17, 'F'): Role of Credential Holder Qualcomm Incorporated, Ericsson Rel-17 Revision of S2-2201998r03. Approved Agreed
8.2 S2-2202132 CR Approval 23.501 CR3588 (Rel-17, 'F'): Clarification on Remote Provisioning Huawei, HiSilicon Rel-17 Postponed Peter (Ericsson) provides comments and r01
Haris(Qualcomm) proposes to note the CR for now
Saso (Intel) proposes to postpone the CR.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
8.2 S2-2202158 CR Approval 23.501 CR3589 (Rel-17, 'F'): Network Slicing Support in SNPN Ericsson Rel-17 r01 agreed. Revised to S2-2203421 Antoine (Orange) provides r01.
Peter Hedman (Ericsson) provides reply ok to align with eNS_Ph2 conclusions
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.2 S2-2203421 CR Approval 23.501 CR3589R1 (Rel-17, 'F'): Network Slicing Support in SNPN Ericsson Rel-17 Revision of S2-2202158r01. Approved Agreed
8.2 S2-2202159 CR Approval 23.501 CR3590 (Rel-17, 'F'): SNPN onboarding correction Ericsson Rel-17 Postponed Haris(Qualcomm) asks questions
Saso (Intel) supports the CR and comments.
Haris(Qualcomm) comments
Rainer (Nokia) concurs with Haris (Qualcomm).
Qianghua (Huawei) understands a singular DNN/S-NSSAI is used for onboarding in ON-SNPN
Saso (Intel) comments that only Option 1 makes sense, but the clarification can be done in a future meeting.
Peter Hedman (Ericsson) provide replies
Ashok (Samsung) comments
Peter Hedman (Ericsson) proposes we discuss a possible update of 23.502 flow for the no DCS case at the next meeting
Saso (Intel) replies to Haris.
Peter Hedman (Ericsson) provides comments
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides reply
Haris(Qualcomm) proposes to postpone
Qianghua (Huawei) OK with the CR
==== Comments Deadline ====
Postponed
8.2 S2-2202160 CR Approval 23.503 CR0710 (Rel-17, 'F'): Corrections to URSP provisioning when UE accesses an SNPN using CH credentials Ericsson Rel-17 Merged into S2-2203425 Antoine (Orange) assumes this CR is merged into S2-2202877.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.2 S2-2202161 CR Approval 23.503 CR0711 (Rel-17, 'F'): Identification of a list of PSIs provided by an SNPN Ericsson Rel-17 Noted Josep (DT) comments, provides r01.
Qianghua (Huawei) comments that the updates are not necessary and proposes to note.
Belen (Ericsson) is okay with r01, replies to Huawei.
==== Revisions Deadline ====
Qianghua (Huawei) objects this CR (r00-r01) because of the changes are not necessary and bring backward compatibility issues
Belen (Ericsson) asks Huawei to explain which the backward compatibility issue is.
Qianghua (Huawei) replies that UE->5GC direction is already supported in CT1 spec, and backward compatibility issue is that: Rel-16 UEs/SNPNs don't support this CR enhancement while Rel-17 UEs does for the same scenario. Without enhancements in this CR, the current mechanism works well.
Belen (Ericsson) replies to Huawei
==== Comments Deadline ====
Noted
8.2 S2-2202514 CR Approval 23.501 CR3609 (Rel-17, 'F'): SMF UP remote provisioning capability Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2203422 Pengfei (vivo) provides comments
Qianghua (Huawei) replies to Pengfei (vivo)
Haris(Qualcomm) asks questions
Rainer (Nokia) comments.
Rainer (Nokia) provides r01 removing the second change.
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.2 S2-2203422 CR Approval 23.501 CR3609R1 (Rel-17, 'F'): SMF UP remote provisioning capability Huawei, HiSilicon Rel-17 Revision of S2-2202514r02. Approved Agreed
8.2 S2-2202515 CR Approval 23.502 CR3445 (Rel-17, 'F'): SMF UP remote provisioning capability Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2203423 Peter (Ericsson) provides comments and r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.2 S2-2203423 CR Approval 23.502 CR3445R1 (Rel-17, 'F'): SMF UP remote provisioning capability Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2202515r01. Approved Agreed
8.2 S2-2202516 CR Approval 23.501 CR3610 (Rel-17, 'F'): Provisioning of PVS address to UE for SNPN onboarding Huawei, HiSilicon Rel-17 Postponed Rainer (Nokia) proposes to note the CR as it is adding new functionality.
Peter Hedman (Ericsson) provides to use 2827 as basis
zhendong (ZTE) same view with ericsson and nokia
Qianghua (Huawei) still suggests to use 2516 as basis
Qianghua (Huawei) provides r01
==== Revisions Deadline ====
Qianghua (Huawei) disagrees to mark it merged with 2827, since 2827 doesn't address any technical issues for this scenario. Propose to postpone.
Haris(Qualcomm) objects to this CR
==== Comments Deadline ====
Postponed
8.2 S2-2202517 CR Approval 23.502 CR3446 (Rel-17, 'F'): Provisioning of PVS address to UE for SNPN onboarding Huawei, HiSilicon Rel-17 Postponed Rainer (Nokia) proposes to note the CR as it is adding new functionality.
Peter Hedman (Ericsson) proposes to use 2828 as basis
zhendong (ZTE) same view with ericsson and nokia
Qianghua (Huawei) still suggests to use 2517 as basis
==== Revisions Deadline ====
Qianghua (Huawei) disagrees to mark it merged with 2828, since 2828 doesn't address any technical issues for this scenario. Propose to postpone.
==== Comments Deadline ====
Postponed
8.2 S2-2202577 CR Approval 23.503 CR0715 (Rel-17, 'F'): Clarify URSP provisioning when UE accesses an SNPN using CH credentials Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2203425 Belen (Ericsson) provides comments
Antoine (Orange) points out that this CR clashes with S2-2202160.
Rainer (Nokia) proposes to mark 2577 as merged into 2877.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.2 S2-2202579 CR Approval 23.501 CR3613 (Rel-17, 'F'): DCS supporting AUSF/UDM and AAA server functionality Nokia, Nokia Shanghai Bell Rel-17 Approved Agreed
8.2 S2-2202684 CR Approval 23.503 CR0716 (Rel-17, 'F'): Clarifications for eNPN related description Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2203424 Belen (Ericsson) provides comments
Qianghua (Huawei) replies
Sebastian (Qualcomm) comments
Belen (Ericsson) provides comments.
Qianghua (Huawei) provides r01
Antoine (Orange) provides r02, removing 'accessing'.
Belen (Ericsson) provides r03, disagrees with r02,r01 and initial version
Antoine (Orange) objects to r03 because we have never studied NSSAI mapping for SNPN.
Sebastian (Qualcomm) replies
Qianghua (Huawei) provides a way forward
Qianghua (Huawei) replies and provides r04
Belen (Ericsson) asks Orange to clarify his comment.
Antoine (Orange) clarifies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.2 S2-2203424 CR Approval 23.503 CR0716R1 (Rel-17, 'F'): Clarifications for eNPN related description Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2202684r04. Approved Agreed
8.2 S2-2202826 CR Approval 23.501 CR3622 (Rel-17, 'F'): Clarification on the PVS address DCS. ZTE Rel-17 Postponed Qianghua (Huawei) provides comments
zhendong (ZTE) provides the response
Qianghua (Huawei) replies
zhendong (ZTE) comments
Saso (Intel) replies to Zhendong.
Peter Hedman (Ericsson) provides comments, and do not see the need to restrict the specs
Saso (Intel) objects to r00.
zhendong (ZTE) provides r01
Rainer (Nokia) provides r02.
Saso (Intel) is OK with r02.
Qianghua (Huawei) objects this CR
Saso (Intel) points to Qianghua that the concern 'how to ensure that the DCS knows the SO-SNPN' is not valid. The DCS may, but does not have to, know the SO-SNPN identity.
Qianghua (Huawei) asks how to make this 'if' happens at DCS?
Peter Hedman (Ericsson) provides reply and suggests to go with r02
Haris(Qualcomm) provides r03
zhendong (ZTE) similar view with saso (intel)
zhendong (ZTE) provides r03 hyperlink
==== Revisions Deadline ====
Qianghua (Huawei) suggests to postpone the CR, objects this CR (r00-r03) for NOTEs
Rainer (Nokia) is ok to note the CR.
Peter Hedman (Ericsson) ok to note the CR
==== Comments Deadline ====
Postponed
8.2 S2-2202827 CR Approval 23.501 CR3623 (Rel-17, 'F'): Clarification on the FQDN(s) and IP address(es) of PVS for remote provisionning ZTE Rel-17 This was postponed Qianghua (Huawei) provides comments and suggests to use 2516/2517 for basis
Rainer (Nokia) replies and prefers 2827 and 2828.
Peter Hedman (Ericsson) proposes to use 2827/2828 as basis and provides r01
Haris(Qualcomm) also prefer 2827/2828 technical proposal vs. what is included in 2516/2517
zhendong (ZTE) same view with Qualcomm and Nokia, prefer with 2827/2828 proposal
Jihoon (ETRI) also prefers 2827/2828 and provides r02.
Qianghua (Huawei) comments that the NOTE doesn't address the technical concerns and is not acceptable as a way forward
Haris(Qualcomm) provides r03
Qianghua (Huawei) replies
Peter Hedman (Ericsson) provides reply
zhendong (ZTE) provides the comments
zhendong (ZTE) provides the response
==== Revisions Deadline ====
Qianghua (Huawei) suggests to postpone the CR, objects this CR (r00-r03) for NOTEs
Rainer (Nokia) proposes to agree the CR.
Peter Hedman (Ericsson) proposes to agree the CR in r03
Haris(Qualcomm) proposes to agree r03 but if not possible proposes to do SoH in CC#2/3
zhendong (ZTE) agree with haris, proposes to agree r03 but if not possible proposes to do SoH
Qianghua (Huawei) OK with SoH on CR, but will still object the CR with the reasons expressed before.
zhendong (ZTE) ask to take this CR to CC#3
==== Comments Deadline ====
Postponed
8.2 S2-2202828 CR Approval 23.502 CR3457 (Rel-17, 'F'): Clarification on the FQDN(s) and IP address(es) of PVS for remote provisionning ZTE Rel-17 Postponed Qianghua (Huawei) provides comments and suggests to use 2516/2517 for basis
Rainer (Nokia) prefers 2827 and 2828.
zhendong (ZTE) also prefer 2827 amd 2828
Qianghua (Huawei) comments that the 2827 NOTE doesn't address the technical concerns and is not acceptable as a way forward
Haris(Qualcomm) provides r01
==== Revisions Deadline ====
Qianghua (Huawei) suggests to postpone the CR, objects this CR (r00-r01) for NOTEs
Rainer (Nokia) proposes to agree the CR.
Peter Hedman (Ericsson) proposes to agree r01
Haris(Qualcomm) supports approving the CR
Haris(Qualcomm) proposes to do SoH in CC#2/3
zhendong (ZTE) agree to do SoH in CC#2/3
Qianghua (Huawei) OK with SoH on CC, but will still object the CR with the reasons expressed before.
Qianghua (Huawei) replies and asks to check email history for 2827.
Qianghua (Huawei) replies: Rather than agree a CR that only captures partial clarification, I prefer not rush and come back with a full picture
zhendong (ZTE) ask to take this CR to CC#3
==== Comments Deadline ====
Postponed
8.2 S2-2202877 CR Approval 23.503 CR0719 (Rel-17, 'F'): ENPN: Correction to URSP provisioning when UE accesses an SNPN using CH credentials MediaTek Inc. Rel-17 r13 agreed. Revised to S2-2203425, merging S2-2202160 and S2-2202577 Belen (Ericsson) provides comments
Josep (DT) asks question for clarification, comments.
Pengfei (vivo) provides a revision r01.
Chia-Lin (MediaTek) provides r02 and suggests to use this CR as baseline to merge S2-2202160, S2-2202577 and S2-2202684
Belen (Ericsson) provides r03.
Qianghua (Huawei) revisions of 2877 do not contain changes of 2684 and 2684 can be handled separately
Chia-Lin (MediaTek) responds to Qianghua (Huawei)
Belen (Ericsson) objects to r04
Chia-Lin (MediaTek) provides r04
Sebastian (Qualcomm) comments
Qianghua (Huawei) provides r05
Chia-Lin (MediaTek) objects to r05 and provides r06
Antoine (Orange) provides r07.
Belen (Ericsson) provides r07.
Sebastian (Qualcomm) comments that r07 has already been provided by Antoine
Belen (Ericsson) provides r08
Antoine (Orange) comments on r08.
Belen (Ericsson) replies to Orange
Antoine (Orange) replies to Ericsson.
Chia-Lin (MediaTek) responds to Belen (Ericsson)
Chia-Lin (MediaTek) responds to Belen (Ericsson) and provides r09
Qianghua (Huawei) objects to r00-r08, except the r05
Antoine (Orange) replies to Belen: Yes.
Belen (Ericsson) replies to MediaTek
Belen (Ericsson) provides r10.
Guillaume (MediaTek Inc.) comments.
Guillaume (MediaTek inc.) responds to Belen.
Guillaume (MediaTek Inc.) provides r12 (pls. ignore r11 uploaded with a mistake)
Belen (Ericsson) replies to MediaTek, Ericsson is okay with r09.
==== Revisions Deadline ====
Qianghua (Huawei) provides r13
Chia-Lin (MediaTek) suggest to go either r09/r13 (without new sub-clauses) or r12 and suggest to discuss in CC#2 to decide to go with which revision since they are different proposals.
Qianghua (Huawei) asks what is the misleading with title 'URSP rules for an SNPN-enabled UE'
Sebastian (Qualcomm) asks a question
Belen (Ericsson) prefers r13 or r09.
Guillaume (MediaTek Inc.) responds to Qianghua (Huawei)
Qianghua (Huawei) replies to Guillaume (MediaTek Inc.)
Qianghua (Huawei) replies and asks again the invalidating, thanks
==== Comments Deadline ====
Revised
8.2 S2-2203425 CR Approval 23.503 CR0719R1 (Rel-17, 'F'): ENPN: Correction to URSP provisioning when UE accesses an SNPN using CH credentials MediaTek Inc., Ericsson Rel-17 Revision of S2-2202877r13, merging S2-2202160 and S2-2202577. Approved Agreed
8.2 S2-2202938 CR Approval 23.502 CR3463 (Rel-17, 'F'): DN-AAA server selection during UE onboarding Intel Rel-17 Postponed Peter (Ericsson) provides comments and question whether we can postpone the CR
Saso (Intel) is OK to postpone the CR.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=30 -
8.3 S2-2201930 LS In Information LS from CT WG1: LS on ECS provider identification in ECS address provisioning CT WG1 (C1-220854) Rel-17 Revision of Postponed S2-2200196 from S2#149E. Postponed Postponed
8.3 S2-2201966 LS In Information LS from SA WG6: Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) SA WG6 (S6-220265) Rel-17 Noted Hui (Huawei) proposes to note this LS.
Magnus O (Ericsson) Also propose to note this LS
==== Revisions Deadline ====
Noted
8.3 S2-2201967 LS In Information Reply LS on follow-up on EAS definition SA WG6 (S6-220351) Rel-18 Noted Hui (Huawei) proposes to note this LS.
==== Revisions Deadline ====
Noted
8.3 S2-2201969 LS In Information Reply LS on further Operator Platform Group questions following SDO Workshop SA WG6 (S6-220432) Rel-17 Noted Hui (Huawei) proposes to note this LS.
==== Revisions Deadline ====
Noted
8.3 S2-2202779 LS In Action LS on AF specific UE ID retrieval CT WG3 (C3-221735) Rel-17 Response drafted in S2-2202964. Final response in S2-2203426 Replied to
8.3 S2-2202964 LS OUT Approval [DRAFT] Reply LS on AF specific UE ID retrieval Qualcomm Incorporated, Ericsson Rel-17 Response to S2-2202779. r02 agreed. Revised to S2-2203426 Hui (Huawei) provides r01.
Shubhranshu (Nokia) comments
Magnus (Ericsson) provides r02
==== Revisions Deadline ====
Dario (Qualcomm) is OK with r02
==== Comments Deadline ====
Revised
8.3 S2-2203426 LS OUT Approval Reply LS on AF specific UE ID retrieval SA WG2 Rel-17 Revision of S2-2202964r02. Approved Approved
8.3 S2-2202796 LS In Information LS from SA WG3: Reply LS on Further Operator Platform Group questions following SDO Workshop SA WG3 (S3-220571) Noted Hui (Huawei) proposes to note this LS.
==== Revisions Deadline ====
Noted
8.3 S2-2202797 LS In Information LS from TSG SA: Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop TSG SA (SP-220346) Noted Hui (Huawei) proposes to note this LS.
==== Revisions Deadline ====
Noted
8.3 S2-2202063 CR Approval 23.502 CR3423 (Rel-17, 'F'): Outcome of UE Policies delivery procedure Samsung Rel-17 r01 agreed. Revised to S2-2203427 Hui (Huawei) asks for clarification.
Shubhranshu (Nokia) comments
Magnus (Ericsson) provides comments
Jicheol (Samsung) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.3 S2-2203427 CR Approval 23.502 CR3423R1 (Rel-17, 'F'): Outcome of UE Policies delivery procedure Samsung Rel-17 Revision of S2-2202063r01. Approved Agreed
8.3 S2-2202064 CR Approval 23.503 CR0708 (Rel-17, 'F'): Outcome of UE Policies delivery procedure Samsung Rel-17 r01 agreed. Revised to S2-2203428 Magnus O (Ericsson) provides comments
Jicheol (Samsung) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.3 S2-2203428 CR Approval 23.503 CR0708R1 (Rel-17, 'F'): Outcome of UE Policies delivery procedure Samsung Rel-17 Revision of S2-2202064r01. Approved Agreed
8.3 S2-2202089 CR Approval 23.501 CR3587 (Rel-17, 'F'): Discovery and selection Ericsson Rel-17 Postponed Shubhranshu (Nokia) comments
Hui (Huawei) comments
Magnus H (Ericsson) withdraws the CR to be postponed to next meeting
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
8.3 S2-2202090 CR Approval 23.502 CR3427 (Rel-17, 'F'): AF specific UE ID retrieval procedure correction Ericsson, Qualcomm Incorporated Rel-17 Approved Agreed
8.3 S2-2202091 CR Approval 23.548 CR0052 (Rel-17, 'F'): Correction related to EAS IP Address in EDI Ericsson Rel-17 r01 agreed. Revised to S2-2203429 Hui (Huawei) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.3 S2-2203429 CR Approval 23.548 CR0052R1 (Rel-17, 'F'): Correction related to EAS IP Address in EDI Ericsson Rel-17 Revision of S2-2202091r01. Approved Agreed
8.3 S2-2202273 CR Approval 23.548 CR0053 (Rel-17, 'F'): Corrections on enabling EAS IP Replacement procedure by AF China Unicom Rel-17 Approved Agreed
8.3 S2-2202374 CR Approval 23.548 CR0054 (Rel-17, 'F'): Correction of EAS Deployment Information Management procedures and services Tencent, Tencent Cloud Rel-17 r04 agreed. Revised to S2-2203430 Magnus (Ericsson) provides r01
Tugce (NTT DOCOMO) asks for clarification.
Zhuoyun (Tencent) provides r02.
Magnus H (Ericsson) comments
Xinpeng(Huawei) provides r03.
Zhuoyun (Tencent) provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.3 S2-2203430 CR Approval 23.548 CR0054R1 (Rel-17, 'F'): Correction of EAS Deployment Information Management procedures and services Tencent, Tencent Cloud, Ericsson, Huawei, HiSilicon Rel-17 Revision of S2-2202374r04. Approved Agreed
8.3 S2-2202397 CR Approval 23.548 CR0055 (Rel-17, 'F'): Alignment to SA WG6 on ECS Configuration Information Huawei, HiSilicon Rel-17 Postponed Shubhranshu (Nokia) comments
Dario (Qualcomm) proposes to postpone this CR.
==== Revisions Deadline ====
Hui (Huawei) agrees to postpone.
==== Comments Deadline ====
Postponed
8.3 S2-2202398 CR Approval 23.502 CR3443 (Rel-17, 'F'): Alignment to SA WG6 on ECS Configuration Information Huawei, HiSilicon Rel-17 Postponed Shubhranshu (Nokia) comments
Hui (Huawei) replies to Shubhranshu.
Shubhranshu (Nokia) responds
Dario (Qualcomm) proposes to postpone this CR.
Hui (Huawei) asks question.
Dario (Qualcomm) replies to Hui.
Hui (Huawei) replies to Dario.
==== Revisions Deadline ====
Hui (Huawei) agrees to postpone.
==== Comments Deadline ====
Postponed
8.3 S2-2202741 CR Approval 23.548 CR0056 (Rel-17, 'F'): Parameter supplement of EDI China Mobile Rel-17 r06 agreed. Revised to S2-2203602. Hui (Huawei) provides r01.
Magnus H (Ericsson) provides r02
Hui (Huawei) asks for clarification on r02
Tugce (NTT DOCOMO) provides comments.
Magnus H (Ericsson) answers Hui
Dario (Qualcomm) provides r03
Dario (Qualcomm) provides r06 based on r05 + a correction.
Magnus H (Ericsson) disagrees with r04 and provides r05 based on r03
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Xinpeng(Huawei) ask Magnus H (Ericsson) question.
Magnus H (Ericsson) answers Xinpeng
Tingfang Tang (Lenovo) comments and provide r07.
Magnus H (Ericsson) expresses concerns of r07
Tingfang Tang (Lenovo) replies to Magnus.
Magnus H (Ericsson) comments
==== Revisions Deadline ====
Dario (Qualcomm) proposes to go with r06 because does not seem agreeable.
Dan (China Mobile) also suggest to go with r06
Dario (Qualcomm) proposes to go with r06 because r07 does not seem agreeable.
Tingfang Tang (Lenovo) replies.
Tingfang Tang (Lenovo) replies to Dario and Dan.
Hui (Huawei) asks question to Magnus.
Dan(China Mobile) provide r08 based on r07 with removing the NOTE
Magnus H (Ericsson) objects to all versions of this document except r00 and r06
Tingfang Tang (Lenovo) replies to Dan and is ok with r07 with removing the NOTE, and suggests further time for discussion and discusses this CR in CC#3.
Dan (China Mobile) ask further and request to discuss this in CC#2 or CC#3
==== Comments Deadline ====
Revised
8.3 S2-2203602 CR Approval 23.548 CR0056R1 (Rel-17, 'F'): Parameter supplement of EDI China Mobile, Huawei, Ericsson Rel-17 Revision of S2-2202741r06. Approved Agreed
8.3 S2-2202845 CR Approval 23.502 CR3460 (Rel-17, 'F'): Clarification for Edge Relocation Triggered by AF Lenovo, Motorola Mobility Rel-17 r01 agreed. Revised to S2-2203431 Magnus (Ericsson) provides r01
Shubhranshu (Nokia) comments
Tugce (NTT DOCOMO) provides comments.
Tingfang Tang (Lenovo) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.3 S2-2203431 CR Approval 23.502 CR3460R1 (Rel-17, 'F'): Clarification for Edge Relocation Triggered by AF Lenovo, Motorola Mobility, Ericsson Rel-17 Revision of S2-2202845r01. Approved Agreed
8.3 S2-2202846 CR Approval 23.548 CR0057 (Rel-17, 'F'): Clarification on EAS Deployment Information Lenovo, Motorola Mobility Rel-17 Noted Magnus H (Ericsson) comments
Shubhranshu (Nokia) comments
Tugce (NTT DOCOMO) provides comments and asks for clarification.
Tingfang Tang (Lenovo) replies.
Shubhranshu (Nokia) provides r01
Magnus (Ericsson) provides r02
Tingfang Tang (Lenovo) replies to Shubhranshu .
Tingfang Tang (Lenovo) replies to Magnus.
==== Revisions Deadline ====
Magnus H (Ericsson) can only accept r02 and objects to r00 and r01
Tingfang Tang (Lenovo) replies to Shubhranshu.
Shubhranshu (Nokia) comments and does not agree to r02
Tingfang Tang (Lenovo) is OK to note this paper.
==== Comments Deadline ====
Noted
8.3 S2-2202847 CR Approval 23.502 CR3461 (Rel-17, 'F'): Clarification on EAS Deployment Information Lenovo, Motorola Mobility Rel-17 Noted Magnus H (Ericsson) comments
Tugce (NTT DOCOMO) asks for clarification.
Tingfang Tang (Lenovo) replies.
Tingfang Tang (Lenovo) proposes to withdraw 2847 based on the discussion on 2846.
==== Revisions Deadline ====
Magnus H (Ericsson) objects to this document
==== Comments Deadline ====
Noted
8.3 S2-2202851 CR Approval 23.548 CR0058 (Rel-18, 'F'): Update of EASDF functional description and clarication on scope of EAS in EAS discovey and selection procedure IIT Delhi Rel-18 Noted Hui (Huawei) provides comment.
Hyesung (Samsung) comments.
Shubhranshu (Nokia) comments
Ashish (IIT Delhi) provides r02
Magnus (Ericsson) provides comments
Dario (Qualcomm) comments
Ashish (IIT Delhi) accepts Samsung and Huawei comments.
==== Revisions Deadline ====
Dario (Qualcomm) clarifies that this paper should be note.
Hyesung (Samsung) also thinks that the status of this CR should be 'noted'.
==== Comments Deadline ====
Noted
8.3 S2-2202963 CR Approval 23.502 CR3464 (Rel-17, 'F'): Correction to the Service Specific Authorization procedure Nokia, Nokia Shanghai Bell Rel-17 Approved Agreed
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=17 -
8.4 S2-2202800 LS In Information LS from GSMA: LS on enforcement of maximum number of UEs and maximum number of PDU sessions in a network slice GSMA (ENSWI09_Doc006) Postponed Postponed
8.4 S2-2202017 CR Approval 23.501 CR3582 (Rel-17, 'F'): Removal of NSACF from HPLMN in LBO Model Ericsson Rel-17 r01 agreed. Revised to S2-2203032 alessio(nokia) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.4 S2-2203032 CR Approval 23.501 CR3582R1 (Rel-17, 'F'): Removal of NSACF from HPLMN in LBO Model Ericsson Rel-17 Revision of S2-2202017r01. Approved Agreed
8.4 S2-2202049 CR Approval 23.501 CR3584 (Rel-17, 'F'): Clarification on determination of Registration Area Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2203033 Haiyang (Huawei) responds to Stefano (Qualcomm)
Stefano (Qualcomm) proposes to note the CR because it is not FASMO, not cat. F, and technically incorrect.
Peter Hedman (Ericsson) provides r01
Dongeun (Samsung) cannot agree with r00 and can live with r01
Alessio(Nokia) the issue is that the feature requesting a specific behaviour precisely defines what to do so there is no FASMO unless one ignores doing what the specific feature requires. maintains the position on this CR
Haiyang (Huawei) is OK with r01.
Alessio(nokia) while r01 is correct in referencing a certain lause, we do not believe that it is needed as the clause that imposes a certain behaviour in connection to the support of TARGET NSSAI already describes that! we have to only approve FASMO CRs at this meeting (also the meeting agenda says that). so we also agree with those that think this CR is not meeting FASMO and shall not be approved.
Genadi (Lenovo) supports r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.4 S2-2203033 CR Approval 23.501 CR3584R1 (Rel-17, 'F'): Clarification on determination of Registration Area Huawei, HiSilicon Rel-17 Revision of S2-2202049r01. Approved Agreed
8.4 S2-2202075 CR Approval 23.502 CR3425 (Rel-17, 'F'): Providing differential NSAC BOT Samsung Rel-17 Noted Fenqin (Huawei) provide comment and consider this is an implementation issue.
Ashok (Samsung) comments
Fenqin (Huawei) provide comment.
Ashok (Samsung) responds to Fenqin (Huawei)
Jinguo(ZTE) agree with Fenqin and suggest to note this paper, not FASMO
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.4 S2-2202280 CR Approval 23.502 CR3438 (Rel-17, 'F'): NSSRG during PDN connections Samsung, Nokia, Nokia Shanghai Bell Rel-17 Noted Jinguo(ZTE) comments
Ashok (Samsung) replies to Jinguo (ZTE)
Peter Hedman (Ericsson) provides comments that it is not a FASMO issue
Patrice (Huawei) supports Peter (Ericsson) and proposes to note the CR.
Jinguo (ZTE) provides comments that it is not a FASMO issue
Ashok (Samsung) responds to Peter Hedman (Ericsson) and Patrice (Huawei)
Ashok (Samsung) responds to Jinguo (ZTE) and explains how it is FASMO
Peter Hedman (Ericsson) provides comments and objects to the CR as it is not FASMO and adding new functionality
Alessio(nokia) comments we supported this CR as it is common and frequent to establish PDU sessions in EPS so this CR ensures retaining the slice compatibility for PDU sessions that are established while in EPS.
Ashok (Samsung) responds to Peter Hedman (Ericsson): Peter, your comments seems to suggest to restrict the service to user/not giving the feature and hence eliminating problem statement to justify solution not needed
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.4 S2-2202660 CR Approval 23.502 CR3405R1 (Rel-17, 'F'): Correction on NSACF exposure ZTE, Rel-17 Revision of (Postponed) S2-2201043. r03 agreed. Revised to S2-2203034 Fenqin (Huawei) provides comment and r01.
Jinguo(ZTE) is ok with r03.
alessio(Nokia) is ok with r03.
Srisakul (NTT DOCOMO) provides comments and r03.
Jinguo(ZTE) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.4 S2-2203034 CR Approval 23.502 CR3405R2 (Rel-17, 'F'): Correction on NSACF exposure ZTE, Huawei Rel-17 Revision of S2-2202660r03. Approved Agreed
8.4 S2-2202088 CR Approval 23.503 CR0709 (Rel-17, 'F'): Corrections to the UE-Slice-MBR Ericsson Rel-17 r01 agreed. Revised to S2-2203035 Jinguo(ZTE) comments
DongEun(Samsung) propose to note the CR
Belen (Ericsson) replies to ZTE and Samsung
Jinguo(ZTE) replies to Belen (Ericsson)
Alessio(Nokia) proposes to note this paper and use option 2 of 2661
Jinguo(ZTE) proposes r01
==== Revisions Deadline ====
Jinguo(ZTE) suggest to approve r01
Dongeun (Samsung) object to r01
Alessio(nokia) justifies why cannot accept r01 either
Belen (Ericsson) asks if r01 can be agreed removing the NOTE
Jinguo(ZTE) is ok to remove the NOTE and agree r01
TAO(VC) check whether the proposed, remove the NOTE and agree r01, agreeable to everyone
Haiyang (Huawei) is ok to remove the NOTE and agree r01
==== Comments Deadline ====
Revised
8.4 S2-2203035 CR Approval 23.503 CR0709R1 (Rel-17, 'F'): Corrections to the UE-Slice-MBR Ericsson Rel-17 Revision of S2-2202088r01. Approved Agreed
8.4 S2-2202661 CR Approval 23.501 CR3616 (Rel-17, 'F'): Clarification on UE-Slice-MBR ZTE Rel-17 Postponed DongEun(Samsung) provides r01
Belen (Ericsson) objects to this CR both initial version and r01
Jinguo(ZTE) asks clarification to Belen (Ericsson).
Alessio(Nokia) proposes r02 that actually makes the 1:1 constraint for slices associated with a UE_slice_MBR normative.
==== Revisions Deadline ====
Haiyang (Huawei) suggests to postpone this paper as offline comment.
==== Comments Deadline ====
Postponed
8.4 S2-2202756 CR Approval 23.501 CR3620 (Rel-17, 'F'): UE-Slice-MBR exemption for emergency and priority services Samsung Rel-17 Noted DongEun (Samsung) provides r01 to correct cover page
Haiyang (Huawei) seeks for clarification
Belen (Ericsson) objects to this CR.
Dongeun (Samsung) replies to Haiyang (Huawei)
Dongeun (Samsung) clarifies to Belen (Ericsson)
Jinguo(ZTE) agree with Belen (Ericsson) and Haiyang(Huawie) and propose to note this CR
Dongeun (Samsung) cannot agree to Zinguo (ZTE) and clarifies
Alessio(Nokia) also objects to this CR as it is not FASMO
==== Revisions Deadline ====
Dongeun (Samsung) is OK to note the CR.
==== Comments Deadline ====
Noted
8.4 S2-2202074 CR Approval 23.502 CR3424 (Rel-17, 'F'): Clarification on storage of rejected S-NSSAI and BOT due to NSAC in UE Samsung Rel-17 Noted Stefano (Qualcomm) has questions for clarification.
Ashok (Samsung) provides clarification to Stefano (Qualcomm)
Jinguo(ZTE) believes this details are stage 3 and should be noted.
alessio(Nokia) suggest we note this paper as the FASMO issue seems to be missing.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.4 S2-2202858 CR Approval 23.501 CR3550R1 (Rel-17, 'F'): Clarification of NSAC about the Access Type Xiaomi Rel-17 Revision of S2-2200945. Noted Alessio(Nokia) supports Jinguo that there is no requirement to support quota per AT so this cannot be FASMO.
Jinguo(ZTE) comments
Jinhua(Xiaomi) replies to Jinguo and Alessio, 2858 can be noted.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.4 S2-2202859 CR Approval 23.502 CR3391R1 (Rel-17, 'F'): Clarification of NSAC about the Access Type Xiaomi Rel-17 Revision of (Noted) S2-2200946. r02 agreed. Revised to S2-2203036 Alessio(Nokia) supports Jinguo that there is no requirement to support quota per AT so this cannot be FASMO. proposed to not this and the other paper in 2858
Jinguo(ZTE) comments
Jinhua(Xiaomi) replies to Jinguo and Alessio, with r01 provided.
Fenqin(Huawei) comments and provides r02
Fenqin(Huawei) suggest to go with r02
Jinhua(Xiaomi) replies to Fenqin, r02 is fine, with r03 provided for clarification,
==== Revisions Deadline ====
Jinhua(Xiaomi) replies to Fenqin, r02 is OK with me,
==== Comments Deadline ====
Revised
8.4 S2-2203036 CR Approval 23.502 CR3391R2 (Rel-17, 'F'): Clarification of NSAC about the Access Type Xiaomi Rel-17 Revision of S2-2202859r02. Approved Agreed
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=40 -
8.5 S2-2201923 LS In Action LS from ITU-T SG15: LS/r on Time Synchronization support in 3GPP specification ITU-T SG15 (SG15-LS348) Revision of Postponed S2-2200041 from S2#149E. Response drafted in S2-2202196. Final response in S2-2203229 Shabnam (Ericsson) can be marked Noted since response has been approved. Replied to
8.5 S2-2202196 LS OUT Approval [DRAFT] Reply Time Synchronization support in 3GPP Ericsson Rel-17 Response to S2-2201923. Revised to S2-2203229. Revised
8.5 S2-2203229 LS OUT Approval Reply Time Synchronization support in 3GPP SA WG2 Rel-17 Revision of S2-2202196. Approved Approved
8.5 S2-2202192 CR Approval 23.501 CR3595 (Rel-17, 'F'): Cleaning up the description of time distribution methods and parameters Ericsson Rel-17 This was postponed Scott (Inspur) comments on this paper and propose to merge it to 2279.
Devaki (Nokia) provides r01.
Sang-Jun (Samsung) supports r01, asks to add Samsung as co-signer, and objects to merging it to 2279.
Scott (Inspur) propose the way forward.
zhendong (ZTE) provides r02
Qianghua (Huawei) provides comments
György (Ericsson) responds
Sebastian (Qualcomm) provides r03
Qianghua (Huawei) provides r04
==== Revisions Deadline ====
György (Ericsson) comments and proposes to go with r03
Qianghua (Huawei) objects r00-r03, and suggests a way forward
zhendong (ZTE) provides clarification on the dependency
Devaki (Nokia) comments.
Sang-Jun (Samsung) supports r03, and asks to add Samsung as co-signer before final upload.
Scott(Inspur) objects 00-03.
Shabnam (Ericsson) attaches the email with Ericsson responses and asks Inspur to not block progress. We understand that INSPUR joined these discussions recently. We request you reconsider your objection, as external readers found it difficult to understand the two methods so we are trying to avoid mistakes by misunderstanding.
Scott(Inspur) replies to withdraw objection.
==== Comments Deadline ====
Postponed
8.5 S2-2202193 CR Approval 23.502 CR3433 (Rel-17, 'F'): Cleaning up the time synchronization procedures Ericsson Rel-17 r02 agreed. Revised to S2-2203230 Shabnam (Ericsson) provides r01, removing overlaps with tdoc 2296 and Nokia co-signs.
Sang-Jun(Samsung) supports r01, and asks to add Samsung as co-signer.
Shabnam (Ericsson) r02, adding no technical changes, Samsung and fixing the diagrams to be editable.
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
8.5 S2-2203230 CR Approval 23.502 CR3433R1 (Rel-17, 'F'): Cleaning up the time synchronization procedures Ericsson, Nokia, Nokia Shanghai Bell, Samsung Rel-17 Revision of S2-2202193r02. Approved Agreed
8.5 S2-2202194 CR Approval 23.501 CR3485R1 (Rel-17, 'F'): Correcting the 5G AS time distribution procedure Ericsson Rel-17 Revision of (Noted) S2-2200299. r02 agreed. Revised to S2-2203231 Devaki (Nokia) supports the CR, incorporates our updates from last meeting thus wish to cosign as well.
Qianghua (Huawei) provides comments
zhendong (ZTE) provides comments
Qianghua (Huawei) provides r01 removing the new interface between TSCTSF-UDM
Shabnam (Ericsson) provides r02 and indicates to Huawei that it is from SBI perspective not new interface, but for point to point based there is no way to describe without new interface. This is the consequence of the agreement that was not completed due to many parallel CRs ongoing.
Qianghua (Huawei) replies
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203231 CR Approval 23.501 CR3485R2 (Rel-17, 'F'): Correcting the 5G AS time distribution procedure Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202194r02. Approved Agreed
8.5 S2-2202195 CR Approval 23.502 CR3434 (Rel-17, 'F'): Correcting the 5G AS time distribution procedure Ericsson Rel-17 r02 agreed. Revised to S2-2203232 Shabnam (Ericsson) provides r01, removing overlaps with tdoc 2296 and Nokia co-signs.
Qianghua (Huawei) provides comments
Sebastian (Qualcomm) comments
Jari (NTT DOCOMO) comments
zhendong (ZTE) provides the comments
Shabnam (Ericsson) r02 with editable figure, thanks for catching it.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203232 CR Approval 23.502 CR3434R1 (Rel-17, 'F'): Correcting the 5G AS time distribution procedure Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202195r02. Approved Agreed
8.5 S2-2202268 CR Approval 23.501 CR3602 (Rel-17, 'F'): Changing the TSCTSF Services Inspur Rel-17 Merged into S2-2203234 Devaki (Nokia) replies.
Scott(Inspur) agree to merge with 2295 in principle with extra comments.
Devaki (Nokia) proposes to consider this CR as merged with 2295, as that is a super set of the changes proposed in this CR.
Scott (Inspur) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.5 S2-2202279 CR Approval 23.501 CR3603 (Rel-17, 'F'): Revisions on Exposure of Time Synchronization Inspur Rel-17 This was postponed. Devaki (Nokia) responds to INSPUR.
Scott (Inspur) comments on Devaki's comments.
Devaki (Nokia) comments that the changes in this CR conflicts with 2192 (which in our view is better basis to start), conflict needs to be resolved, only one CR can be used as the basis.
Sang-Jun (samsung) has similar views as Devaki (Nokia).
György (Ericsson) agrees with Nokia and proposes to consider this merged into 2192
zhendong (ZTE) provides comment
zhendong (ZTE) provides the response
Scott(Inspur) replies to zhendong (ZTE)
==== Revisions Deadline ====
Scott(Inspur) provides the response
Devaki (Nokia) replies
Scott(Inspur) replies to Devaki
Shabnam (Ericsson) comments that changes in the first clause we do not see needed, it is just different ways of presenting the content and not FASMO. For change of clause title in your second change, I can understand your proposal is better formulated but needs consensus to change.
Also, I would like to point out that we discussed last time and agreed we should not add parameters on the title
as that restricts future use of the clause. So, we need to avoid that.
Scott(Inspur) replies to Shabnam (Ericsson).
Shabnam (Ericsson) responds in line to clarify and hope we can decouple approval of 2192 from this.
==== Comments Deadline ====
Devaki (Nokia) comments that this document should be marked as withdrawn or noted as discussed with Scott offline. Scott does not prefer this to be marked as merged with 2192.
Postponed
8.5 S2-2202293 CR Approval 23.501 CR3605 (Rel-17, 'F'): Corrections to Survival Time description Nokia, Nokia Shanghai Bell, Ericsson, Huawei Rel-17 r01 agreed. Revised to S2-2203233 Sang-Jun (Samsung) agrees on the changes of this CR, and asks to add Samsung as co-signer.
Mirko (Huawei) comments and asks whether the same reference can be used in both tables.
Devaki (Nokia) provides r01, with Samsung as cosigner, fixing SA1 spec reference to align the tables.
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
8.5 S2-2203233 CR Approval 23.501 CR3605R1 (Rel-17, 'F'): Corrections to Survival Time description Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung Rel-17 Revision of S2-2202293r01. Approved Agreed
8.5 S2-2202294 CR Approval 23.502 CR3439 (Rel-17, 'F'): Terminology Alignment for AF session with required QoS procedures Nokia, Nokia Shanghai Bell Rel-17 Approved Agreed
8.5 S2-2202295 CR Approval 23.501 CR3606 (Rel-17, 'F'): Corrections to time synchronization description Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2203234, merging S2-2202268, S2-2202518 and S2-2202590 Devaki (Nokia) provides r01 resolving the comments by INSPUR/Scott Jiang.
Qianghua (Huawei) provides comments
Qianghua (Huawei) provides r02
Devaki (Nokia) is fine with r02.
==== Revisions Deadline ====
Scott(Inspur) is fine with r02.
==== Comments Deadline ====
Revised
8.5 S2-2203234 CR Approval 23.501 CR3606R1 (Rel-17, 'F'): Corrections to time synchronization description Nokia, Nokia Shanghai Bell, Huawei, INSPUR Rel-17 Revision of S2-2202295r02, merging S2-2202268, S2-2202518 and S2-2202590. Approved Agreed
8.5 S2-2202296 CR Approval 23.502 CR3440 (Rel-17, 'F'): Corrections to time synchronization procedures Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2203235 Shabnam (Ericsson) provides r01, removing overlaps with tdoc 2193 and 2195 and Ericsson co-signs.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203235 CR Approval 23.502 CR3440R1 (Rel-17, 'F'): Corrections to time synchronization procedures Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2202296r01. Approved Agreed
8.5 S2-2202518 CR Approval 23.501 CR3611 (Rel-17, 'F'): Split TimeSynchronization service Huawei, HiSilicon Rel-17 Merged into S2-2203234 Devaki (Nokia) proposes to merge this with 2295 as it covers the changes proposed here, third change in this CR needs correction which is already corrected in 2295.
Qianghua (Huawei) OK to merge with 2295 if my comments on 2295 are addressed in the revision.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.5 S2-2202519 CR Approval 23.502 CR3447 (Rel-17, 'F'): Corrections for 5GS Bridge Information reporting and subscription Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2203236 Devaki (Nokia) provides r01.
Qianghua (Huawei) provides r02
Qianghua (Huawei) provides comments on r03
Sang-Jun (Samsung) provides r04.
Jari (NTT DOCOMO) provides r03
Qianghua (Huawei) provides r05
Jari (NTT DOCOMO) provides r06
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203236 CR Approval 23.502 CR3447R1 (Rel-17, 'F'): Corrections for 5GS Bridge Information reporting and subscription Huawei, HiSilicon Rel-17 Revision of S2-2202519r06. Approved Agreed
8.5 S2-2202520 CR Approval 23.503 CR0714 (Rel-17, 'F'): Corrections for 5GS Bridge Information reporting and subscription Huawei, HiSilicon Rel-17 Approved Agreed
8.5 S2-2202590 CR Approval 23.501 CR3614 (Rel-17, 'F'): 23.501 Term Changes for IIoT Samsung Rel-17 Merged into S2-2203234 Devaki (Nokia) proposes to merge with 2295 as it covers the Master -> Leader changes proposed in this CR.
Sang-Jun (Samsung) agrees to merge 2590 with 2295.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.5 S2-2202591 CR Approval 23.502 CR3448 (Rel-17, 'F'): 23.502 Term Changes for IIoT Samsung Rel-17 r02 agreed. Revised to S2-2203237 Devaki (Nokia) proposes to remove the note from this CR for 23.502 (to avoid duplication), instead simply refer to the Note in TS 23.501.
Sang-Jun (Samsung) provides r01, which applies Devaki (Nokia)'s proposal.
Sang-Jun (Samsung) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203237 CR Approval 23.502 CR3448R1 (Rel-17, 'F'): 23.502 Term Changes for IIoT Samsung Rel-17 Revision of S2-2202591r02. Approved Agreed
8.5 S2-2202685 CR Approval 23.503 CR0717 (Rel-17, 'F'): PCF response when rejecting an AF session with required QoS Huawei, HiSilicon Rel-17 Approved Devaki (Nokia) comments.
Gyorgy (Ericsson) comments.
Mirko (Huawei) responds to the comments.
György (Ericsson) provides r01
zhendong (ZTE) comments
György (Ericsson) responds.
Mirko (Huawei) replies to the comments.
==== Revisions Deadline ====
Mirko (Huawei) proposes to agree on the original version of the CR.
==== Comments Deadline ====
Agreed
8.5 S2-2202686 CR Approval 23.503 CR0718 (Rel-17, 'F'): Alignment of description for support of Time Sensitive Communication and Time Synchronization Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2203238 Devaki (Nokia) provides r01 (third change proposing to remove existing functionality is not acceptable for us).
zhendong (ZTE) provides comments
Mirko (Huawei) responds to comments.
Shabnam (Ericsson) provides additional comments and questions if we should really add some of the details.
Mirko (Huawei) responds to the comments.
==== Revisions Deadline ====
Mirko (Huawei) proposes to agree on the original version of the CR.
Devaki (Nokia) objects to the original version of the CR, can only accept r01.
==== Comments Deadline ====
Revised
8.5 S2-2203238 CR Approval 23.503 CR0718R1 (Rel-17, 'F'): Alignment of description for support of Time Sensitive Communication and Time Synchronization Huawei, HiSilicon Rel-17 Revision of S2-2202686r01. Approved Agreed
8.5 S2-2202719 CR Approval 23.501 CR3618 (Rel-17, 'F'): Correction the residence time for the 5G as end-to-end Transparent Clock CATT Rel-17 Noted Devaki (Nokia) comments that this CR is not a FASMO (the format in which the timer is stored is anyhow implementation specific, also we believe current text is correct).
Sang-Jun (Samsung) provids comments, and agrees with with Devaki (Nokia).
Chunshan (CATT) provides clarification.
Shabnam (Ericsson) corrects CATT misunderstanding on Ericsson comment, we don't believe it is correct to change it as you do and that other parts already also reflect same association so by just changing here does not change the function.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.5 S2-2202720 CR Approval 23.501 CR3619 (Rel-17, 'F'): NW-TT Identification and Clock Drift Report CATT Rel-17 Noted Chunshan (CATT) provides more clarification.
Jari (NT DOCOMO) responds
Chunshan (CATT) responds
Chunshan (CATT) provides clarifications
Jari (NT DOCOMO) objects
Jari (NT DOCOMO) objects, not FASMO
Chunshan (CATT) provides clarification.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.5 S2-2202721 CR Approval 23.502 CR3452 (Rel-17, 'F'): NW-TT Identification and Clock Drift Report CATT Rel-17 Noted Chunshan (CATT) provides clarifications
Jari (NT DOCOMO) objects
Jari (NT DOCOMO) objects, not FASMO
Chunshan (CATT) provides clarification.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.5 S2-2202829 CR Approval 23.501 CR3624 (Rel-17, 'F'): Clarification on how the TSFTSF assign the NW-TT port to PPT instance ZTE, Nokia, Nokia Shanghai Bell Rel-17 r00 agreed. Revised to S2-2203239 Jari (NTT DOCOMO) proposes to note
zhendong (ZTE) provides the response
==== Revisions Deadline ====
zhendong (ZTE) proposes to approve r00
==== Comments Deadline ====
Revised
8.5 S2-2203239 CR Approval 23.501 CR3624R1 (Rel-17, 'F'): Clarification on how the TSFTSF assign the NW-TT port to PPT instance ZTE, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202829r00. Approved Agreed
8.5 S2-2202830 CR Approval 23.502 CR3458 (Rel-17, 'F'): Clarification on the PCF service operation consumer ZTE Rel-17 r01 agreed. Revised to S2-2203240 Devaki (Nokia) responds to ZTE.
zhendong (ZTE) respond the CR includes other change which is not cover by 2195
Devaki (Nokia) comments that this CR is not a FASMO by itself (adding an example consumer is not normative nor FASMO) but to retain the change, propose to merge with 2195.
Mirko (Huawei) comments.
zhendong (ZTE) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.5 S2-2203240 CR Approval 23.502 CR3458R1 (Rel-17, 'F'): Clarification on the PCF service operation consumer ZTE Rel-17 Revision of S2-2202830r01. Approved Agreed
8.5 S2-2202831 CR Approval 23.501 CR3625 (Rel-17, 'F'): Clarification on 5G access stratum distribution in mobility ZTE Rel-17 Postponed zhendong (ZTE) provides r01.
Devaki (Nokia) proposes to note this CR as the proposed description is not correct nor useful (we are ok with the intention captured in the companion 23.502 CR - 2832).
Devaki (Nokia) comments that this CR is not a FASMO by itself (adding an example consumer is not normative nor FASMO) but to retain the change, propose to merge with 2195.
Qianghua (Huawei) provides comments
zhendong (ZTE) provides the response
Shabnam (Ericsson) also does not see any value to add a new subclause to refer to another spec/clause. We can add such text in one of the main clauses where related functions are described or 23.502 covers it.
zhendong (ZTE) provides r02
==== Revisions Deadline ====
Qianghua (Huawei) this CR should be marked postponed based on offline discussion (needs LS to RAN). But OK to mark this endorsed or approved in this meeting.
Jari (NTT DOCOMO) prefers to postpone
==== Comments Deadline ====
Postponed
8.5 S2-2202832 CR Approval 23.502 CR3459 (Rel-17, 'F'): Clarification on 5G access stratum distribution in mobility ZTE Rel-17 Postponed Jari (NTT DOCOMO) comments
zhendong (ZTE) provides the response
Shabnam (Ericsson) similar view as Jari, but also I would like to know what RAN has decided on this if any. It should be aligned with RAN for Xn case.
Qianghua (Huawei) comments further
Shabnam (Ericsson) thanks Zhendong for RAN3 information, comments..
==== Revisions Deadline ====
Qianghua (Huawei) this CR should be marked postponed based on offline discussion (needs LS to RAN). But OK to mark this endorsed or approved in this meeting.
Shabnam (Ericsson) prefer to postpone and discuss the new LS to RAN3 and discuss in CT#2 potentially to discuss the CR to conclude.
Jari (NTT DOCOMO) prefers to postpone
==== Comments Deadline ====
Postponed
8.5 S2-2203621 LS OUT Approval [DRAFT] LS On handover issue for 5G access stratum time distribution ZTE Created at CC#2: Related to postponed CRs S2-2202831 and S2-2202832. Revised to S2-2203596. Revised
8.5 S2-2203596 LS OUT Approval LS on handover issue for 5G access stratum time distribution SA WG2 - Revision of S2-2203621. This Approved Approved
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:=17 -
8.7 S2-2201927 LS In Action Reply LS on 3GPP SA1 clarifications on problematic UAV SA WG1 (S1-214238) Rel-17 Revision of Postponed S2-2200062 from S2#149E. Noted Stefano (Qualcomm) proposes to note, no actions required.
==== Revisions Deadline ====
Noted
8.7 S2-2201934 LS In Action LS from CT WG4: LS on SMF initiated reauthorization CT WG4 (C4-221445) Rel-17 Revision of Postponed S2-2201270 from S2#149E. Response drafted in S2-2202361, S2-2202446. Final response in S2-2203037 Replied to
8.7 S2-2202361 LS OUT Approval [DRAFT] LS Reply on SMF initiated reauthorization QUALCOMM Europe Inc. - Italy Rel-17 Response to S2-2201934. Merged into S2-2203037 Pallab (Nokia) agrees with the proposal to merge.
Stefano (Qualcomm) proposes to consider merged into S2-222446
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.7 S2-2202446 LS OUT Approval [DRAFT] LS OUT SMF initiated reauthorization; Response to S2-2201934 Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2201934. r00 agreed. Revised to S2-2203037, merging S2-2202361 Stefano (Qualcomm) proposes to take this LS as the way forward.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.7 S2-2203037 LS OUT Approval LS SMF initiated reauthorization; Response to S2-2201934 SA WG2 Rel-17 Revision of S2-2202446r00, merging S2-2202361. Approved Approved
8.7 S2-2202778 LS In Action LS from CT WG3: LS on NEF-initiated reauthorization CT WG3 (C3-221444) Rel-17 Response drafted in S2-2202367. Final response in S2-2203038 Replied to
8.7 S2-2202367 LS OUT Approval [DRAFT] LS Reply on NEF-initiated reauthorization QUALCOMM Europe Inc. - Italy Rel-17 Response to S2-2202778. r01 agreed. Revised to S2-2203038 Stefano (Qualcomm) provides R01 to align to Nokia LS reply to CT4.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.7 S2-2203038 LS OUT Approval LS Reply on NEF-initiated reauthorization SA WG2 Rel-17 Revision of S2-2202367r01. Approved Approved
8.7 S2-2202245 CR Approval 23.256 CR0059 (Rel-17, 'F'): Correcting errors for UAV-C address Ericsson Rel-17 r02 agreed. Revised to S2-2203039 Guanglei (Huawei) provides r02 to further correct step numbers.
Shabnam (Ericsson) provides r01, removing overlapped clauses with CR in 2439.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.7 S2-2203039 CR Approval 23.256 CR0059R1 (Rel-17, 'F'): Correcting errors for UAV-C address Ericsson Rel-17 Revision of S2-2202245r02. Approved Agreed
8.7 S2-2202246 CR Approval 23.256 CR0060 (Rel-17, 'F'): Correcting terminology inconsistencies Ericsson Rel-17 Merged into S2-2203040 Shabnam (Ericsson) can be considered merged into revision of 2439 revision 01 as provided, if the changes are agreeable.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.7 S2-2202362 CR Approval 23.256 CR0061 (Rel-17, 'F'): Corrections to SMF-initiated and NEF-initiated re-authorization Qualcomm Incorporated Rel-17 Merged into S2-2203041 Pallab (Nokia) agrees to merge this into S2-2202447.
Stefano (Qualcomm) proposes to consider this merged into S2-2202447.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.7 S2-2202396 CR Approval 23.256 CR0062 (Rel-17, 'F'): Corrections to Naf(Nnef)_Authentication_AuthenticateAuthorize service operation LG Electronics Rel-17 Approved Agreed
8.7 S2-2202439 CR Approval 23.256 CR0063 (Rel-17, 'F'): Clarification and Correction on C2 payload Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2203040, merging S2-2202246 Guanglei (Huawei) provides r02.
Shabnam (Ericsson) provides r01 which includes changes from 2246 and some additional improvements.
Dimitris (Lenovo) comments
Guanglei (Huawei) replies to Dimitris (Lenovo).
Hans (Ericsson) comments on r02.
Guanzhou (InterDigital) provides r03.
Stefano (Faccin) provides r04.
Shabnam (Ericsson) is OK with r04 and comments. Thanks for the updates, looks good and clear.
Guanzhou (InterDigital) is OK with r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.7 S2-2203040 CR Approval 23.256 CR0063R1 (Rel-17, 'F'): Clarification and Correction on C2 payload Huawei, HiSilicon, Ericsson Rel-17 Revision of S2-2202439r04, merging S2-2202246. Approved Agreed
8.7 S2-2202447 CR Approval 23.256 CR0064 (Rel-17, 'F'): Corrections to service operation names Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2203041, merging S2-2202362 Pallab (Nokia) provides r01 merging 2362, added Qualcomm as co-source and corrected as per comment received from Vodafone .
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.7 S2-2203041 CR Approval 23.256 CR0064R1 (Rel-17, 'F'): Corrections to service operation names Nokia, Nokia Shanghai Bell, Qualcomm Incorporated Rel-17 Revision of S2-2202447r01, merging S2-2202362. Approved Agreed
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=31 -
8.8 - - - LS on new interface btw PKMF and UDM - - Docs:=6 -
8.8 S2-2201956 LS In Action LS from SA WG3: LS on new reference point name for the interface between PKMF and UDM in 5G ProSe SA WG3 (S3-220505) Rel-17 Response drafted in S2-2202106. Final response in S2-2203018 Replied to
8.8 S2-2202106 LS OUT Approval [DRAFT] Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe Ericsson Rel-17 Response to S2-2201956.r00 agreed. Revised to S2-2203018 Revised
8.8 S2-2203018 LS OUT Approval Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe SA WG2 Rel-17 Revision of S2-2202106r00. Approved Approved
8.8 S2-2202105 CR Approval 23.304 CR0089 (Rel-17, 'F'): Adding reference point between 5G PKMF and UDM Ericsson Rel-17 r03 agreed. Revised to S2-2203042 Zhang (Ericsson) is OK with r01
Steve (Huawei) provides r01
Hannu (Nokia) provides r02.
Zhang (Ericsson) is OK with r02
Fei (OPPO) comments.
Steve (Huawei) comments
Zhang (Ericsson) provides r03
==== Revisions Deadline ====
Fei (OPPO) is fine with r03.
Steve (Huawei) is ok with r03.
==== Comments Deadline ====
Revised
8.8 S2-2203042 CR Approval 23.304 CR0089R1 (Rel-17, 'F'): Adding reference point between 5G PKMF and UDM Ericsson Rel-17 Revision of S2-2202105r03. Approved Agreed
8.8 S2-2202987 LS OUT Approval [DRAFT] LS on 5G ProSe security open items Nokia Created at CC#1. Noted Steve (Huawei) what is the different to the ENs that SA3 already have?
Hannu (Nokia) provides the initial draft of the new LS that was allocated in CC #1.
Xiaoyan Shi (Interdigital) comments.
Deng Qiang (CATT) comments.
Myungjune (LGE) provides r01.
Myungjune (LGE) responds to Steve (Huawei) and provides r03.
Steve (Huawei) comments
Deng Qiang (CATT) provides r02.
Fei (OPPO) comments.
Hannu (Nokia) replies to Steve on the LS justification.
Hannu (Nokia) replies to Fei
Hannu (Nokia) provides r04 and r05. Can live with either r04 or r05 and lets the others decide which one to send?
==== Revisions Deadline ====
Hong (Qualcomm) comments.
Myungjune (LGE) responds to Hong (Qualcomm) and Judy (Ericsson).
Judy (Ericsson) comments
Judy (Ericsson) see the need of SA2 impact and comments
Myungjune (LGE) responds to Judy (Ericsson)
Steve (Huawei) can this be sent? Perhaps note it.
Judy (Ericsson) share similar view and supports Steve (Huawei)'s proposal to note this paper.
TAO(VC) it seems we cannot converge on any revision? Or some candidate revision move forward
Hannu (Nokia) agrees to note the LS.
==== Comments Deadline ====
Noted
8.8 - - - LS for information - - Docs:=1 -
8.8 S2-2202774 LS In Information LS from CT WG1: LS on the SDU type used over user plane for NR PC5 reference point CT WG1 (C1-221835) Rel-17 Noted Fei (OPPO) proposes to note this incoming LS.
==== Revisions Deadline ====
Noted
8.8 - - - CP based security solution for UE-to-Network Relay - - Docs:=7 -
8.8 S2-2201999 DISCUSSION Endorsement Open issues for control plane authentication/authorisation and secondary authentication for L3 UE-NW Relays. Qualcomm Incorporated Noted Hannu (Nokia) proposes to address items 1 - 4 in revision of S2-2202596 and to allocate tdoc number for LS out to SA3 on items 5 - 7.
Hannu (Nokia) clarifies the proposal item by item.
Hong (Qualcomm) replies to Hannu.
Judy (Ericsson) comments
Myungjune (LGE) responds to Hong (Qualcomm).
Hong (Qualcomm) replies to Myungjune.
Myungjune (LGE) replies to Hong (Qualcomm).
Fei (OPPO) comments.
Deng Qiang (CATT) comments.
Myungjune (LGE) comments.
Hannu (Nokia) responds to comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.8 S2-2202104 CR Approval 23.304 CR0088 (Rel-17, 'F'): Clarify for security procedure for UE-to-Network Relaying Ericsson Rel-17 r04 agreed. Revised to S2-2203043 Fei (OPPO) comments and provides r03 based on r01.
Deng Qiang (CATT) comments on r01.
Fei (OPPO) comments and provides r02.
Zhang (Ericsson) provides r01
Steve (Huawei) comments, provides r04
Zhang (Ericsson) is OK with R04
Hannu (Nokia) supports r04
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.8 S2-2203043 CR Approval 23.304 CR0088R1 (Rel-17, 'F'): Clarify for security procedure for UE-to-Network Relaying Ericsson Rel-17 Revision of S2-2202104r04. Approved Agreed
8.8 S2-2202596 CR Approval 23.304 CR0102 (Rel-17, 'F'): AMF and AUSF selection for CP authentication and authorisation Nokia, Nokia Shanghai Bell, Interdigital Inc. Rel-17 r06 + changes agreed. Revised to S2-2203591. Fei (OPPO) asks questions.
Deng Qiang (CATT) asks to address the issues raised in 1999 in revisions.
Steve (Huawei) comments
Hannu (Nokia) answers the questions and provides r01.
Fei (OPPO) responds
Hong (Qualcomm) comments.
Judy (Ericsson) comments
Xiaoyan Shi (Interdigital) comments
Myungjune (LGE) provides r02
Deng Qiang (CATT) comments on r02.
Hannu (Nokia) replies to Fei
Hannu (Nokia) replies to Hong
Myungjune (LGE) provides r03
Hannu (Nokia) answers to Judy
Hannu (Nokia) replies to Steve
Hannu (Nokia) thanks Myungjune for r02, provides r03 and comments.
Hong (Qualcomm) replies to Hannu.
Steve (Huawei) comments, provides r06.
Fei (OPPO) provides comments.
Fei (OPPO) provides comments on standarized SST value.
==== Revisions Deadline ====
Fei (OPPO) comments r06 is not acceptable unless the last bullet is removed from r06.
Judy (Ericsson) comments a revision is needed to take out the per user basis authorization, and remove 'Layer-3' from cover sheet
Deng Qiang (CATT) comments on r06, it does not fully address the comments.
TAO(VC) check whether the following can be clarified and some revision based upon r06 can achieve agreement.
Hannu (Nokia) proposes after revision deadline r07 to address the comments.
==== Comments Deadline ====
Revised
8.8 S2-2203591 CR Approval 23.304 CR0102R1 (Rel-17, 'F'): AMF and AUSF selection for CP authentication and authorisation Nokia, Nokia Shanghai Bell, Interdigital Inc. Rel-17 Revision of S2-2202596r06 + changes. Approved Agreed
8.8 S2-2202597 CR Approval 23.501 CR3615 (Rel-17, 'F'): AMF and AUSF selection for CP authentication and authorisation Nokia, Nokia Shanghai Bell, Interdigital Inc. Rel-17 This was postponed. Judy (Ericsson) comments
Hannu (Nokia) does not agree to postpone as this CR addresses some of the open issues identified in S2-2201999. Provides r01.
==== Revisions Deadline ====
Deng Qiang (CATT) comments the principle on 2596 and 2597 should be aligned.
Hannu (Nokia) responds to Deng Qiang that even if the AMF and slice selection solution is removed from S2-2202596, the AUSF selection using NF profile should still be kept.
Hannu (Nokia) proposes to go ahead with r01, with one more deletion of 'Layer-3' on the cover page if requested by Ericsson.
Steve (Huawei) suggests postponing, lets sort out 2596, then align
Judy (Ericsson) supports Steve (Huawei)'s proposal to postpone it, sort out the impacted SA2 aspects first and then align.
Hannu (Nokia) accepts to leave the AMF change to later date and points out that S2-2202596r07 provided in drafts area already removes the AMF aspect completely and updates the cover page as requested. The related S2-2202597 and 2598 do not touch this AMF aspect and can be agreed with comment that the text 'Layer-3' is to be removed from the cover page.
==== Comments Deadline ====
Postponed
8.8 S2-2202598 CR Approval 23.502 CR3449 (Rel-17, 'F'): AMF and AUSF selection for CP authentication and authorisation Nokia, Nokia Shanghai Bell, Interdigital Inc. Rel-17 This was postponed. Judy (Ericsson) comments
Hannu (Nokia) does not agree to postpone as this CR addresses some of the open issues identified in S2-2201999. Provides r01.
==== Revisions Deadline ====
Deng Qiang (CATT) comments the principle on 2596 and 2598 should be aligned. Similar comments to 2597.
Hannu (Nokia) proposes to agree r01 with cover page cleanup to remove the text 'Layer-3' as suggested by Judy.
Steve (Huawei) This CR DEPENDS in S2-2202597. This can't be agreed unless is agreed.
Hannu (Nokia) accepts to leave the AMF change to later date and points out that S2-2202596r07 provided in drafts area already removes the AMF aspect completely and updates the cover page as requested. The related S2-2202597 and 2598 do not touch this AMF aspect and can be agreed with comment that the text 'Layer-3' is to be removed from the cover page.
==== Comments Deadline ====
Postponed
8.8 - - - Miscellaneous corrections and alignments - - Docs:=17 -
8.8 S2-2202247 CR Approval 23.304 CR0090 (Rel-17, 'F'): Mobility restrictions for MCX cleanup Ericsson Rel-17 r02 agreed. Revised to S2-2203044 Steve (Huawei) comments
Mehrdad (Samsung) is OK with this CR and co-signs the CR
Judy (Ericsson) provides r01 to add Samsung in co-source and responds to Steve (Huawei)
LaeYoung (LGE) comments.
Judy (Ericsson) responds to LaeYoung (LGE)
LaeYoung (LGE) answers to Judy (Ericsson).
Judy (Ericsson) provides r02, the only change is to tick the ME box in cover sheet
==== Revisions Deadline ====
Steve (Huawei) is ok with r02.
LaeYoung (LGE) is OK with r02.
Mehrdad (Samsung) is OK with r02.
==== Comments Deadline ====
Revised
8.8 S2-2203044 CR Approval 23.304 CR0090R1 (Rel-17, 'F'): Mobility restrictions for MCX cleanup Ericsson, Samsung Rel-17 Revision of S2-2202247r02. Approved Agreed
8.8 S2-2202871 CR Approval 23.304 CR0103 (Rel-17, 'F'): Clarification to mobility restrictions Samsung, Nokia, Nokia Shanghai Bell Rel-17 Noted Judy (Ericsson) comments that the change in this paper is not needed with the correction in 02247.
Hannu (Nokia) can live without this CR following the comment from Judy.
==== Revisions Deadline ====
Mehrdad (Samsung) is OK to note this CR.
==== Comments Deadline ====
Noted
8.8 S2-2202292 CR Approval 23.304 CR0093 (Rel-17, 'F'): TAI delivery OPPO Rel-17 r03 agreed. Revised to S2-2203045 Judy (Ericsson) ask questions
Fei (OPPO) responds to Judy (Ericsson)
Deng Qiang (CATT) comments.
Fei (OPPO) responds to Deng Qiang (CATT).
Steve (Huawei) comments
Fei (OPPO) responds and provides r01.
Hong (Qualcomm) comments.
Hong (Qualcomm) comments on r01.
Fei (OPPO) responds to Hong (Qualcomm) and provides r02.
Judy (Ericsson) comments
Fei (OPPO) provides r03.
==== Revisions Deadline ====
Judy (Ericsson) responds to Fei (OPPO)
Steve (Huawei) is ok with r03.
==== Comments Deadline ====
Revised
8.8 S2-2203045 CR Approval 23.304 CR0093R1 (Rel-17, 'F'): TAI delivery OPPO Rel-17 Revision of S2-2202292r03. Approved Agreed
8.8 S2-2202320 CR Approval 23.304 CR0094 (Rel-17, 'F'): Remove ENs on Security Parameters Provisioning for UE-NW Relay CATT, Ericsson Rel-17 r05 agreed. Revised to S2-2203046 Fei (OPPO) provides comments.
Steve (Huawei) provides r01
Hong (Qualcomm) comments on r01
Walter Dees (Philips) comments on r02 and provides r03.
Deng Qiang (CATT) comments on r01 and provides r02.
Hong (Qualcomm) comments on r02.
Deng Qiang (CATT) can live with r01 and comments on r03.
Walter Dees (Philips) answers to Deng Qiang (CATT).
Deng Qiang (CATT) provides r05.
==== Revisions Deadline ====
Steve (Huawei) is ok with r05.
==== Comments Deadline ====
Revised
8.8 S2-2203046 CR Approval 23.304 CR0094R1 (Rel-17, 'F'): Remove ENs on Security Parameters Provisioning for UE-NW Relay CATT, Ericsson Rel-17 Revision of S2-2202320r05. Approved Agreed
8.8 S2-2202462 CR Approval 23.304 CR0098 (Rel-17, 'F'): Miscellaneous corrections and alignments Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2203047 Zhang (Ericsson) suggest to merge the paper with S2-2202320
Steve (Huawei) part can be merged, provides r01 with remainder.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.8 S2-2203047 CR Approval 23.304 CR0098R1 (Rel-17, 'F'): Miscellaneous corrections and alignments Huawei, HiSilicon Rel-17 Revision of S2-2202462r01. Approved Agreed
8.8 S2-2202350 DISCUSSION Agreement Clarification on multiple PDU sessions during L2 U2N direct to indirect path switching. ASUSTeK Rel-17 Noted Noted
8.8 S2-2202351 CR Approval 23.304 CR0095 (Rel-17, 'F'): Clarification on multiple PDU sessions during L2 U2N direct to indirect path switching ASUSTeK Rel-17 Noted Wen (vivo) comments.
Fei (OPPO) comments.
Zhang (Ericsson) provides comments
Lider (ASUSTeK) has questions for clarification.
Fei (OPPO) provides comments.
Xiaoyan Shi (interdigital) replies to Lider.
==== Revisions Deadline ====
Fei (OPPO) supports noting the CR.
Hong (Qualcomm) propose to NOTE the CR.
==== Comments Deadline ====
Noted
8.8 S2-2202352 CR Approval 23.304 CR0096 (Rel-17, 'F'): Differ source L2ID for unstructured type PDU session ASUSTeK Rel-17 Noted Wen (vivo) comments.
Fei (OPPO) comments.
Lider (ASUSTeK) comments.
Hannu (Nokia) proposes to note the document as adding more conditions to informative note is not a FASMO change.
Mehrdad (Samsung) provides comments
Hong (Qualcomm) agrees with Mehrdad (Samsung).
==== Revisions Deadline ====
Mehrdad (Samsung) suggests to NOTE this CR.
==== Comments Deadline ====
Noted
8.8 S2-2202353 CR Approval 23.304 CR0097 (Rel-17, 'F'): Correction on layer-2 link release ASUSTeK Rel-17 Noted Steve (Huawei) Is this needed?
Lider (ASUSTeK) comments.
Mehrdad (Samsung) provides comments
Hong (Qualcomm) comments.
==== Revisions Deadline ====
Steve (Huawei) should be NOTED.
==== Comments Deadline ====
Noted
8.8 S2-2202564 CR Approval 23.304 CR0099 (Rel-17, 'F'): Modify description in clause 4.3.9.3 ZTE Rel-17 Approved Agreed
8.8 S2-2202573 CR Approval 23.304 CR0100 (Rel-17, 'F'): Clarification on DRX handling for unicast communication procedures ZTE Rel-17 r02 agreed. Revised to S2-2203048 Fei (OPPO) comments.
Steve (Huawei) comments
Mehrdad (Samsung) provides comments
Hao Dong (ZTE) responds and provides r01.
LaeYoung (LGE) comments.
Hao Dong (ZTE) responds to LaeYoung (LGE) and provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.8 S2-2203048 CR Approval 23.304 CR0100R1 (Rel-17, 'F'): Clarification on DRX handling for unicast communication procedures ZTE Rel-17 Revision of S2-2202573r02. Approved Agreed
8.8 S2-2202595 CR Approval 23.304 CR0101 (Rel-17, 'F'): Removal of non-existent reference point Nokia, Nokia Shanghai Bell Rel-17 Noted Zhang (Ericsson) provides comments
Steve (Huawei) comments
Hannu (Nokia) responds to Zhang and Steve and points out the description of this reference point is incomplete and outside of the scope of 3GPP TS.
Fei (OPPO) comments
Hannu (Nokia) thanks Steve for the way forward.
==== Revisions Deadline ====
Zhang (Ericsson) object r01 and original version
Hannu (Nokia) agrees to note the CR but points out that some other correction is still needed as Figure 4.2.7.1-2 is not aligned with TS 23.501 Figure D.3-2.
Hong (Qualcomm) comments.
==== Comments Deadline ====
Hannu (Nokia) replies to Hong.
Hong (Qualcomm) replies to Hannu.
Noted
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=53 -
8.9 - - - LSs, replies and associated CRs - - Docs:=31 -
8.9 S2-2201933 LS In Action LS from CT WG4: LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation CT WG4 (C4-221427) Rel-17 Revision of Postponed S2-2201269 from S2#149E. Response drafted in S2-2202985. Final response in S2-2203049 Replied to
8.9 S2-2202985 LS OUT Approval [DRAFT] Reply LS on LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation Nokia Rel-17 Response to S2-2201933. r02 agreed. Revised to S2-2203049 LiMeng(Huawei) provides r01.
Miguel (Qualcomm) comments that ACTIONS section in the draft LS is incorrect
Thomas(Nokia) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203049 LS OUT Approval Reply LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation SA WG2 Rel-17 Revision of S2-2202985r02. Approved Approved
8.9 S2-2201949 LS In Action LS from RAN WG2: Reply LS on maximum number of MBS sessions that can be associated to a PDU session RAN WG2 (R2-2204107) Rel-17 Response drafted in S2-2202140. Final response in S2-2203050 Replied to
8.9 S2-2201965 LS In Action LS from SA WG6: Reply LS on maximum number of MBS sessions that can be associated to a PDU session SA WG6 (S6-220262) Rel-17 Response drafted in S2-2202140. Final response in S2-2203050 Robbie (Ericsson) comments this LS is responded in S2-2202140 Replied to
8.9 S2-2202140 LS OUT Approval [DRAFT] Reply LS on maximum number of MBS sessions that can be associated to a PDU session Ericsson Rel-17 Response to S2-2201949 and S2-2201965. r03 agreed. Revised to S2-2203050 LiMeng(Huawei) provides r01.
Robbie (Ericsson) thanks LiMeng(Huawei) for r01 and comments.
Miguel (Qualcomm) provides some views, ok with either 16 or 32.
Thomas(Nokia) prefers value 16 and provides r02.
Miguel (Qualcomm) comments on Thomas argument
Robbie (Ericsson) shares Miguel's view and prefers 32 to be upper limit in protocol
Robbie (Ericsson) objects to r02, the reason is 32 is the appropriate value in protocol design, and it aligns with RAN2 and SA6 feedback as well.
Thomas (Nokia) objects to r00 and r01
Thomas (Nokia) provides r03
==== Revisions Deadline ====
LiMeng (Huawei) is OK with r03
Miguel (Qualcomm) also ok with r03
Robbie (Ericsson) prefers r01 and can live with r03
==== Comments Deadline ====
Revised
8.9 S2-2203050 LS OUT Approval Reply LS on maximum number of MBS sessions that can be associated to a PDU session SA WG2 Rel-17 Revision of S2-2202140r03. Approved Approved
8.9 S2-2201959 LS In Action LS on 5MBS User Services SA WG4 (S4-220304) Rel-17 Responses drafted in S2-2202002, S2-2202356, S2-2202141. Final response in S2-2203051 Robbie (Ericsson) provides comments
LiMeng (Huawei) provides comments
Robbie (Ericsson) replies to LiMeng (Huawei).
Haris(Qualcomm) comments
Robbie (Ericsson) replies to Haris (Qualcomm).
Haris(Qualcomm) replies
Thomas (Nokia) replies to LiMeng
Thomas (Nokia) provides comments
Thomas(Nokia) comments that the reply in S2-2202002 is fully in line with his technical understanding and suggest to use it as basis for revisions.
zhendong (ZTE) is fine with ericsson proposal
Robbie (Ericsson) responds to zhendong (ZTE)
zhendong (ZTE) respond to robbie
Robbie (Ericsson) replies to Zhendong (ZTE)
zhendong (ZTE) provides the comments
Robbie(Ericsson) asks
Thomas(Nokia) replies to Robbie(Ericsson)
LiMeng (Huawei) agrees with Robbie's view
Robbie (Ericsson) asks whether S2-2202141 or S2-2202202 should be use as a basis for further progress.
LiMeng (Huawei) suggests to use S2-2202141 as the baseline.
==== Revisions Deadline ====
Replied to
8.9 S2-2202002 LS OUT Approval Reply LS on 5MBS User Services Qualcomm Rel-17 Response to S2-2201959. Noted Robbie (Ericsson) suggests having the discussion in LS In thread (S2-2201959).
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.9 S2-2202141 LS OUT Approval [DRAFT] Reply LS on 5MBS User Services Ericsson Rel-17 r03 agreed. Revised to S2-2203051 Robbie (Ericsson) suggests having the discussion in LS In thread (S2-2201959).
Robbie (Ericsson) provides r01.
Thomas (Nokia) provides r02.
Haris(Qualcomm) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203051 LS OUT Approval Reply LS on 5MBS User Services SA WG2 Rel-17 Revision of S2-2202141r03. Approved Approved
8.9 S2-2202356 LS OUT Approval [DRAFT] Reply LS on 5MBS User Service Huawei, HiSilicon Rel-17 Response to S2-2201959. Noted Robbie (Ericsson) suggests having the discussion in LS In thread (S2-2201959).
==== Revisions Deadline ====
LiMeng (Huawei) agrees to mark this document as 'NOTED'.
==== Comments Deadline ====
Noted
8.9 S2-2201963 LS In Action LS from TSG CT: LS on parameters preconfigured in the UE to receive MBS service TSG CT (CP-220398) Rel-17 Responses drafted in S2-2202001 and S2-2202357. This was postponed. Postponed
8.9 S2-2202001 LS OUT Approval Reply LS on parameters preconfigured in the UE to receive MBS service Qualcomm Rel-17 Response to S2-2201963. Noted Thomas (Nokia) raises concerns against this LS
LiMeng (Huawei) object to this LS.
Kaixin (CBN) raises concerns
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.9 S2-2202357 LS OUT Approval [DRAFT] Reply LS on preconfigured in the UE receiving MBS Huawei, HiSilicon Rel-17 Response to S2-2201963. This was postponed. Haris(Qualcomm) objects to this LS out
Thomas (Nokia) provides r01
Haris(Qualcomm) objects to r01
Shabnam (Ericsson) provides r02, has concerns on both original and r01 versions as they attempt to add new functions into the spec that does not current exist.
Haris(Qualcomm) comment on r02 and provides r03
Thomas(Nokia) raises concerns against r03
LiMeng (Huawei) objects to r02 and 03.
Haris(Qualcomm) objects to r0 and comments
Kaixin (CBN) raises concerns
==== Revisions Deadline ====
Haris(Qualcomm) proposes post deadline r04
LiMeng (Huawei) proposes post deadline r05 on top of post deadline r04.
==== Comments Deadline ====
Thomas (Nokia) proposes post deadline r06
Haris(Qualcomm) comments
Postponed
8.9 S2-2202000 CR Approval 23.247 CR0100 (Rel-17, 'F'): Need for pre-configured USD and service announcement Qualcomm Incorporated Rel-17 Noted Youngkyo(Samsung) provides a comment.
LiMeng (Huawei) comments
Haris(Qualcomm) provides answers
Thomas (Nokia) raises concerns
Haris(Qualcomm) responds and provides r01
Shabnam (Ericsson) it is wrong to have MBMS spec referred for 5G service announcement when 5G spec is available. Comments and asks clarification
Thomas(Nokia) replies to Harris and provides r02
LiMeng (Huawei) provides r03, and objects to r00, r01, and has concern with r02.
Haris(Qualcomm) objects to r03
Xiaoyan (CATT) provides comments and supports r03.
Haris(Qualcomm) comments
Kaixin (CBN) raises concerns
zhendong (ZTE) proposes to go with r03
==== Revisions Deadline ====
Haris(Qualcomm) asks to whom it will confusion
Haris(Qualcomm) proposes post deadline r04
Shabnam (Ericsson) supports the revised versions of the CR and associated LS response provided here, comments.
LiMeng (Huawei) proposes the post deadline r05
LiMeng (Huawei) replies to Haris.
Haris(Qualcomm) comments that this is ROM and is out of scope of the WI in rel.17
Antoine (Orange) agrees with Haris that UE receiving broadcast communication service data without interaction with the network is out of Rel-17 scope and should not be introduced after the freeze.
LiMeng (Huawei) replies there is no ROM defined for NR in rel.17.
Thomas(Nokia) comments that ruling out ROM in rel.17 is not required
Haris(Qualcomm) comments that not ruling out ROM in rel.17 are absurd
Thomas(Nokia) suggest no explicit wording whether ROM mode is enabled in LS and CR.
Suggest approving r02 of CR
Suggest a post-deadline revision of related LS
==== Comments Deadline ====
James Hu (AT&T) agrees with Haris that receiving broadcast content using preconfiguration without registering in PLMN should not be introduced and is out of Rel-17 scope.
Shabnam (Ericsson) agrees with Qualcomm, AT&T, Orange that receiving broadcast content using preconfiguration without registering in PLMN is out of Rel-17 scope. This is shown via the Rel-17 and Rel-18 Study items deprioritisation of the associated work in SA plenary as indicated by Qualcomm.
Thomas(Nokia) replies to Shabnam that she is correct that no related work was performed,
but that this does not prove that ROM reception is not possible.
Suggest as compromise avoiding any explicit wording in either direction.
Noted
8.9 S2-2202801 LS In Action LS from RAN WG3: LS on further outstanding issues in TS 23.247 RAN WG3 (R3-222867) Rel-17 Response drafted in S2-2202146 and S2-2202535. Postponed Fenqin (Huawei) provides comments.
Thomas (Nokia) provides comments.
Paul (Ericsson) replies.
zhendong (ZTE) provides the comments
Thomas (Nokia) replies to Zhendong.
Thomas (Nokia) replies to Paul (Ericsson)
zhendong (ZTE) provides the response
Thomas(Nokia) replies to zhendong (ZTE)
==== Revisions Deadline ====
Postponed
8.9 S2-2202146 LS OUT Approval [DRAFT] Reply LS on further outstanding issues in TS 23.247 Ericsson Rel-17 Response to S2-2202801. Noted Fenqin (Huawei) suggest to note this paper and take 2535 as LS out base line.
Thomas (Nokia) objects against this LS
zhendong (ZTE) agree with fenqin proposal
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.9 S2-2202535 LS OUT Approval [DRAFT] Response LS on further outstanding issues in TS 23.247 Huawei, HiSilicon Rel-17 Response to S2-2202801. Noted Paul (Ericsson) proposes to note this draft LS in 2535 and take the draft LS in 2146 as a baseline.
Thomas (Nokia) objects against this LS
Thomas (Nokia) Withdraws objection
zhendong (ZTE) proposes to use this as baseline
Paul (Ericsson) objects to this LS as it neither takes the RAN3 request nor RAN3 agreements into account.
Hence the content of the LS are incorrect.
==== Revisions Deadline ====
Thomas (Nokia) provides late r01
==== Comments Deadline ====
Noted
8.9 S2-2202145 DISCUSSION Agreement Discussion of RAN WG3 LS Related Topics. Ericsson Rel-17 Noted Noted
8.9 S2-2202147 CR Approval 23.247 CR0104 (Rel-17, 'F'): Alignment with RAN WG3 and other corrections Ericsson Rel-17 r02 agreed. Revised to S2-2203052 Fenqin (Huawei) provides comment
Thomas (Nokia) provides r01
Fenqin (Huawei) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203052 CR Approval 23.247 CR0104R1 (Rel-17, 'F'): Alignment with RAN WG3 and other corrections Ericsson Rel-17 Revision of S2-2202147r02. Approved Agreed
8.9 S2-2202773 LS In Action LS from CT WG1: LS on the impact of MSK update on MBS multicast session update procedure CT WG1 (C1-221747) Rel-17 Response drafted in S2-2202984. Postponed Postponed
8.9 S2-2202984 LS OUT Approval [DRAFT] Reply LS on LS on the impact of MSK update on MBS multicast session update procedure Nokia Rel-17 Response to S2-2202773. Postponed Robbie (Ericsson) provides r01.
LiMeng (Huawei) asks question.
Robbie (Ericsson) provides r02 to include the question from LiMeng (Huawei).
Thomas (Nokia) provides r03
Robbie (Ericsson) asks Thomas (Nokia).
Thomas (Nokia) replies to Robbie (Ericsson)
Thomas (Nokia) provides r04
Thomas (Nokia) provides r07, object against r01, r02 and r06
Robbie (Ericsson) provides r06 to address his concerns and comments
Thomas (Nokia) replies to Robbie and provides r05 to address the comments
Robbie (Ericsson) provides r08.
Thomas (Nokia) objects against r08 and provides r09
Robbie (Ericsson) asks why Thomas (Nokia) can decide the MBSF/MBSTF's behavior in SA2, which is under the remits of SA3.
Robbie (Ericsson) asks Thomas (Nokia) to let SA3 do their work, and consider more energy saving option.
Thomas (Nokia) replies to Robbie.
Robbie (Ericsson) replies to Thomas (Nokia).
Thomas (Nokia) replies to Robble
Robbie (Ericsson) accepts only r01, r02, r06, r08, and objects to other revisions, no consensus can be reached, suggests to postpone this paper
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
8.9 S2-2202960 CR Approval 23.247 CR0116 (Rel-17, 'F'): Miscelaneous corrections Nokia, Nokia Shanghai Bell Rel-17 r06 agreed. Revised to S2-2203053 Robbie (Ericsson) comments this CR contains several unrelated issues. Suggest removing the security related updates which require feedback from SA3 and SA4, to align with the LS response (S2-2202984).
Youngkyo(Samsung) supports removing the security related updates.
Thomas(Nokia) replies to Robbie
Provides r01
Thomas(Nokia) provides r02 to remove security related updates as requested by Robbie
Fenqin(Huawei) provides r03
Thomas(Nokia) provides r04
Robbie (Ericsson) asks whether 'N2 MBS info change indicator' is FASMO
Thomas replies to Robbie
Robbie (Ericsson) still tries to understand whether 'N2 MBS info change indicator' is FASMO
Robbie (Ericsson) provides further comments and r05
Robbie (Ericsson) provide r06 since r05 is corrupted
==== Revisions Deadline ====
Fenqin (Huawei) is fine with r06
Robbie (Ericsson) accepts r06 only, and cannot accept other revisions.
==== Comments Deadline ====
Revised
8.9 S2-2203053 CR Approval 23.247 CR0116R1 (Rel-17, 'F'): Miscelaneous corrections Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202960r06. Approved Agreed
8.9 S2-2202782 LS In Action LS from CT WG4: LS on Traffic usage reporting on 5MBS service CT WG4 (C4-221443) Rel-17 Response drafted in S2-2202142. Final response in S2-2203019 Replied to
8.9 S2-2202142 LS OUT Approval [DRAFT] Reply LS on Traffic usage reporting on 5MBS service Ericsson Rel-17 Response to S2-2202782. r00 agreed. Revised to S2-2203019 Revised
8.9 S2-2203019 LS OUT Approval Reply LS on Traffic usage reporting on 5MBS service SA WG2 Rel-17 Revision of S2-2202142r00. Approved Approved
8.9 S2-2202785 LS In Action LS from RAN WG2: Reply LS on the Length of MBS Service Area Identity RAN WG2 (R2-2203902) Rel-17 Noted LiMeng(Huawei) suggests to note this LS, RAN2 already specified that.
==== Revisions Deadline ====
Noted
8.9 S2-2202794 LS In Action LS from SA WG3: Reply LS on Multicast paging with TMGI SA WG3 (S3-220537) Rel-17 Noted LiMeng(Huawei) suggests to note this LS.
==== Revisions Deadline ====
Noted
8.9 - - - Others - - Docs:=22 -
8.9 S2-2202044 CR Approval 23.247 CR0101 (Rel-17, 'F'): Correction on the mobility procedures for MBS Inspur Rel-17 r02 agreed. Revised to S2-2203054 Xiaohua (Inspur) provides r01 to fill CR number on the cover sheet.
Judy (Ericsson) asks to copy the complete content of 7.2.3.2 where the changes apply.
Xiaohua (Inspur) provides r02 based on Judy's comment.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203054 CR Approval 23.247 CR0101R1 (Rel-17, 'F'): Correction on the mobility procedures for MBS Inspur Rel-17 Revision of S2-2202044r02. Approved Agreed
8.9 S2-2202355 CR Approval 23.247 CR0107 (Rel-17, 'F'): Mega CR to clean up Huawei, Hisilicon, Samsung Rel-17 r02 agreed. Revised to S2-2203055 Youngkyo(Samsung) replies.
Robbie (Ericsson) raises a question.
Youngkyo(Samsung) comments.
Robbie (Ericsson) provides r01.
LiMeng(provides) r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203055 CR Approval 23.247 CR0107R1 (Rel-17, 'F'): Mega CR to clean up Huawei, Hisilicon, Samsung, Ericsson Rel-17 Revision of S2-2202355r02. Approved Agreed
8.9 S2-2202833 CR Approval 23.247 CR0113 (Rel-17, 'F'): Clarification on Activation procedure ZTE Rel-17 Approved Agreed
8.9 S2-2202834 CR Approval 23.247 CR0114 (Rel-17, 'F'): Clarificaiton on the MBS session create and start procedure ZTE Rel-17 Noted Judy (Ericsson) comments that change to 7.3.3 overlaps with 02960 and removal of ENs need some justification.
zhendong (ZTE) provides r01
Judy (Ericsson) provides r02
==== Revisions Deadline ====
Judy (Ericsson) accepts r02 and objects to r00, r01
Thomas (Nokia) object against r02
==== Comments Deadline ====
Noted
8.9 S2-2202712 CR Approval 23.247 CR0110 (Rel-17, 'F'): Clarification on MBS security function Samsung Rel-17 Approved Agreed
8.9 S2-2202143 CR Approval 23.247 CR0102 (Rel-17, 'F'): Broadcast MBS Session Release Require Procedure Ericsson Rel-17 Approved Agreed
8.9 S2-2202144 CR Approval 23.247 CR0103 (Rel-17, 'F'): MBS Service Area for MB-SMF selection in TMGI Allocation Ericsson Rel-17 r06 agreed. Revised to S2-2203056 Youngkyo(Samsung) asks a question.
Fenqin (Huawei) provides comment.
Robbie (Ericsson) replies to Fenqin (Huawei) and Youngkyo (Samsung).
Fenqin (Huawei) provides further comment.
Robbie (Ericsson) replies to Fenqin (Huawei).
Robbie (Ericsson) provides r01.
Fenqin (Huawei) provides r02.
Robbie (Ericsson) provides r03.
Youngkyo(Samsung) comments.
Robbie(Ericsson) replies and provides r04
Fenqin (Huawei) comments and provide r05
Robbie (Ericsson) comments.
Robbie (Ericsson) asks Fenqin (Huawei)
Fenqin(Huawei) responds to Robbie(Ericsson).
Robbie(Ericsson) replies to Youngkyo(Samsung) and asks Fenqin(Huawei).
Robbie(Ericsson) raises concerns on r05
Fenqin (Huawei) provides responds
Fenqin (Huawei) provides responds and r06
Robbie (Ericsson) is fine with r06
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203056 CR Approval 23.247 CR0103R1 (Rel-17, 'F'): MBS Service Area for MB-SMF selection in TMGI Allocation Ericsson Rel-17 Revision of S2-2202144r06. Approved Agreed
8.9 S2-2202148 CR Approval 23.247 CR0105 (Rel-17, 'F'): Correction to MBS Session Context and MBS Session Activation procedure Ericsson Rel-17 r03 agreed. Revised to S2-2203057 Fenqin (Huawei) provides comment and r01
Judy (Ericsson) responds to Fenqin (Huawei) that the current description does not match the condition and the change in r00 makes them consistent.
Judy (Ericsson) provides r02 based on r00
Fenqin (Huawei) provides r03
Judy (Ericsson) is fine with r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203057 CR Approval 23.247 CR0105R1 (Rel-17, 'F'): Correction to MBS Session Context and MBS Session Activation procedure Ericsson Rel-17 Revision of S2-2202148r03. Approved Agreed
8.9 S2-2202354 CR Approval 23.247 CR0106 (Rel-17, 'F'): Resolve the residual ENs and Clean-up in TS 23.247 Huawei, HiSilicon Rel-17 r09 agreed. Revised to S2-2203592. Thomas (Nokia) provides r01
Judy (Ericsson) provides r02
Thomas (Nokia) provides r03
Judy (Ericsson) does not agree with r03 and comments
Thomas (Nokia) does not agree with r02 and comments
Thomas (Nokia) provides r04 (with additional affected clause requested by Judy) and r05 (reverting the controversial changes) to choose from
LiMeng (Huawei) can accept r04.
Judy (Ericsson) provides r06 based on r04
Thomas (Nokia) provides r08 based on r06
Thomas (Nokia) objects against r04 and r06
Judy (Ericsson) provides r09
LiMeng (Huawei) comments on r09 and provides r10.
Thomas (Nokia) provides r11.
==== Revisions Deadline ====
Judy (Ericsson) accepts r02, r05, r06 & r09, objects to other revisions including r00 as the added text does not capture the implication of the removed EN and NOTE 4.
LiMeng (Huawei) can accept r00, r01, r03-05, r10 and r11, and objects to other versions of this document. Suggest to go with r05 in this meeting for the sake of progress.
Thomas (Nokia) objects against r02 and r06.
Thomas Nokia asks if Judy could accept r09 with two minor changes on top.
If so suggest bringing that version to CC
Judy (Ericsson) responds to Thomas (Nokia)
Thomas (Nokia) replies to Judy
Thomas(Nokia) can accept r09
==== Comments Deadline ====
Revised
8.9 S2-2203592 CR Approval 23.247 CR0106R1 (Rel-17, 'F'): Resolve the residual ENs and Clean-up in TS 23.247 Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2202354r09. Approved Agreed
8.9 S2-2202536 CR Approval 23.247 CR0090R1 (Rel-17, 'F'): Clarification of MBS data forwarding Huawei, HiSilicon Rel-17 Revision of S2-2200882. Noted Fenqin (Huawei) provides r02
Thomas (Nokia) provides r01
Paul (Ericsson) provides r03 and comments that RAN3 asked SA2 in their LS in 2801 to take into account their agreements and specifically referring to a solution based on NG-C/N2 signaling.
Thomas (Nokia) raises comments against r03
Fenqin (Huawei) provides r04
zhendong (ZTE) provides r05
Fenqin (Huawei) objects r03 and r06 and suggest to take r04 way forward.
==== Revisions Deadline ====
zhendong (ZTE) only accept r05
Thomas (Nokia) can accept r04 and r05
Comments that the issue was already discussed in a SA2#149e CC and the chair indicated that we could try to establish a working agreement in 150E is the same situation continues.
Suggest bringing this matter to a CC to see if a working agreement can this time be established
Paul (Ericsson) objects to all revisions except r03 and r06.
Fenqin (Huawei) object r03 and r06, and suggest to bring this to CC#2.
==== Comments Deadline ====
Noted
8.9 S2-2202687 CR Approval 23.247 CR0109 (Rel-17, 'F'): Update of PCC procedure for 5MBS Huawei, HiSilicon Rel-17 Noted Judy (Ericsson) fully supports the simplification for no NEF deployment, and proposes further simplification for the NEF deployment and makes the NEF-PCF interaction optional.
zhendong (ZTE) provides the comments
Thomas(Nokia) objects against this CR
Mirko (Huawei) responds to the comments and asks for constructive proposals for the simplification/streamlining of the PCC procedures for 5MBS.
==== Revisions Deadline ====
Judy (Ericsson) does not accept r00, asks Tao (VC) if r01 provided on April 6 can be updated in the note, if yes, propose to go for r01 for simplification, and asks Nokia&ZTE to reconsider their position as the current MBS PCC is unnecessarily complicated and very inefficient and it does not consider Energy Efficiency as guiding principle either.
Thomas(Nokia) continues to inject against all revisions (including the original).
zhendong (ZTE) object this CR.
Thomas(Nokia) continues to object against all revisions (including the original). Sorry for my typo in the previous email
==== Comments Deadline ====
Noted
8.9 S2-2202736 CR Approval 23.247 CR0111 (Rel-17, 'F'): Usage of NAS message for UE joining procedure Samsung Rel-17 r03 agreed. Revised to S2-2203058 Judy (Ericsson) provides r01
Youngkyo(Samsung) provides r02
Miguel (Qualcomm) provides r03
Youngkyo(Samsung) is okay with r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203058 CR Approval 23.247 CR0111R1 (Rel-17, 'F'): Usage of NAS message for UE joining procedure Samsung, Ericsson Rel-17 Revision of S2-2202736r03. Approved Agreed
8.9 S2-2202738 CR Approval 23.247 CR0112 (Rel-17, 'F'): Clarification on MBS session activation procedure Samsung Rel-17 Approved Agreed
8.9 S2-2202537 CR Approval 23.247 CR0108 (Rel-17, 'F'): Left issue on local MBS service Huawei, HiSilicon Rel-17 Postponed zhendong (ZTE) provides comment
Judy (Ericsson) provides r01
Fenqin (Huawei) provides response and r02
Judy (Ericsson) responds to Fenqin (Huawei)
Fenqin (Huawei) responds.
zhendong (ZTE) provides r03
==== Revisions Deadline ====
Judy (Ericsson) accepts r01, objects to other revisions including r00
zhendong (ZTE) is fine with r01
Fenqin (Huawei) object to remove the multi MB-SMF case and suggest to keep the change on resource reservation for data forwarding
Judy (Ericsson) responds to Fenqin (Huawei).
Fenqin (Huawei) responds to Judy (Ericsson).
Thomas(Nokia) objects against r01 that removes multi MB-SMF case
Judy (Ericsson) comments
==== Comments Deadline ====
Fenqin (Huawei) suggest to bring this to CC#3.
Postponed
8.9 S2-2202835 CR Approval 23.247 CR0115 (Rel-17, 'F'): Clarification on local dependent MBS session ZTE Rel-17 r02 agreed. Revised to S2-2203059 Judy (Ericsson) provides r01
Thomas (Nokia) provides r02
zhendong (ZTE) provies response
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.9 S2-2203059 CR Approval 23.247 CR0115R1 (Rel-17, 'F'): Clarification on local dependent MBS session ZTE, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2202835r02. Approved Agreed
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=3 -
8.10 S2-2202210 CR Approval 23.501 CR3596 (Rel-17, 'F'): Correction of message name for paging restriction information Ericsson Rel-17 Approved Agreed
8.10 S2-2202211 CR Approval 23.401 CR3696 (Rel-17, 'F'): Acceptance and Rejection of Paging restriction information Ericsson Rel-17 r01 agreed. Revised to S2-2203241 Steve (Huawei) provides r01
Qian (Ericsson) is ok with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.10 S2-2203241 CR Approval 23.401 CR3696R1 (Rel-17, 'F'): Acceptance and Rejection of Paging Restriction Information Ericsson Rel-17 Revision of S2-2202211r01. Approved Agreed
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=20 -
8.11 S2-2201928 LS In Action Reply LS on UE location aspects in NTN SA WG3 (S3-214360) Rel-17 Revision of Postponed S2-2200065 from S2#149E. Noted DongYeon (Samsung) proposes to postpone, becuase there's no action required from SA2 yet.
Hannu (Nokia) proposes to note as the LS is only CC to us and no response is requested.
Stefan (Ericsson) supports to note the LS
DongYeon (Samsung) supports to note the LS
==== Revisions Deadline ====
Noted
8.11 S2-2201931 LS In Action LS from RAN WG3: LS on RAN Initiated Release due to out-of-PLMN area condition RAN WG3 (R3-221379) Rel-17 Revision of Postponed S2-2200417 from S2#149E. Responses drafted in S2-2201981, S2-2202803. Final response in S2-2203242 Replied to
8.11 S2-2201943 LS In Action LS from RAN WG2: LS on UE location during initial access in NTN RAN WG2 (R2-2202057) Rel-17 Already replied to in S2-2201540. Noted Steve (Huawei) already replied to, should be noted?
Jean Yves (Thales) also proposes to note
==== Revisions Deadline ====
Noted
8.11 S2-2201953 LS In Information LS from RAN WG2: LS on UE location in connected mode in NTN RAN WG2 (R2-2204257) Rel-17 Noted DongYeon (Samsung) proposes to NOTE, because this input is information LS to SA2.
==== Revisions Deadline ====
Noted
8.11 S2-2201981 LS OUT Approval Reply LS on RAN Initiated Release due to out-of-PLMN area condition Ericsson Rel-17 Response to S2-2201931. Merged into S2-2203242 Steve (Huawei) We need to pick one of S2-2201981 or S2-2202803 to send, can't send both.
Stefan (Ericsson) OK to merge S2-2201981 into S2-2202803
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.11 S2-2202803 LS OUT Approval [DRAFT] Reply LS on RAN Initiated Release due to out-of-PLMN area condition Samsung Electronics Romania Rel-17 Response to S2-2201931. r01 agreed. Revised to S2-2203242, merging S2-2201981 Steve (Huawei) We need to pick one of S2-2201981 or S2-2202803 to send, can't send both.
Stefan (Ericsson) provides r01
Yuxin (Xiaomi) agrees the r01
Jean Yves (Thales) agrees the r01
Steve (Huawei) fine to select this one, r01 is ok.
DongYeon (Samsung) agrees to r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.11 S2-2203242 LS OUT Approval Reply LS on RAN Initiated Release due to out-of-PLMN area condition SA WG2 Rel-17 Revision of S2-2202803r01, merging S2-2201981. Approved Approved
8.11 S2-2202776 LS In Information LS from CT WG1: NR satellite RAT type in UE NAS CT WG1 (C1-222098) Rel-17 Noted Noted
8.11 S2-2201980 CR Approval 23.502 CR3420 (Rel-17, 'F'): RAN indication that UE has moved out of PLMN serving area Ericsson Rel-17 Approved, merging S2-2202805 Agreed
8.11 S2-2202235 CR Approval 23.501 CR3597 (Rel-17, 'F'): Correction of last visited TAI requirement Apple Rel-17 Postponed DongYeon (Samsung) comments.
Stephen (Qualcomm) comments
Yuxin (Xiaomi) has the same comment.
Hannu (Nokia) supports the comment from Stephen and Yuxin and provides r01.
Robert (Apple) responds to Hannu's comment. r01 is not acceptable.
Robert (Apple) responds to Stephen (Qualcomm) and provides r02.
Scott (Inspur) comments.
Robert (Apple) responds to Scott's (Inspur) comment.
Stephen (Qualcomm) comments on the r01 and r02
Robert (Apple) responds to Stephen's (Qualcomm) comments and provides r04.
Stefan (Ericsson) comments and provides r03
Chris (Vodafone) provides r05.
Robert (Apple) responds to Chris (Vodafone) and provides r08.
Stephen (Qualcomm) can accept r03 but has reservations for other rev.s
Hannu (Nokia) provides r09.
Stefan (Ericsson) provides r10
Robert (Apple) provides r11
Scott(Inspur) comments.
Chris (Vodafone) provides r12.
Robert (Apple) responds to Scott (?) and Chris (Vodafone) and provides r13.
Chris (Vodafone) believes R13 is wrong (and R12 is correct).
Robert (Apple) comments on Chris's (Vodafone) believe.
Steve (Huawei) comments
==== Revisions Deadline ====
Robert (Apple): r14 is OK for Apple
Stefan (Ericsson) provides r14
Stephen (Qualcomm) can agree r03 only and no other rev.
Hucheng (CATT) proposes to postpone the discussion as there is no perfect version.
Stefan (Ericsson) comments that r14 was uploaded before deadline but email announcing it was delayed due to altospam.
Leo (Deutsche Telekom) agrees with CATT, CR shall be postponed to the next SA2 meeting.
Jean Yves (Thales) is in favor to postponed to the next SA2 meeting.
DongYeon (Samsung) agrees with Hucheng (CATT), it needs to be postponed to the next meeting.
==== Comments Deadline ====
Postponed
8.11 S2-2202236 CR Approval 23.502 CR3436 (Rel-17, 'F'): Correction of last visited TAI requirement Apple Rel-17 r02 agreed. Revised to S2-2203243 DongYeon (Samsung) comments.
Stephen (Qualcomm) comments
Yuxin (Xiaomi) has the same comment.
Hannu (Nokia) comments.
Scott (Inspur) comments.
Hannu (Nokia) asks for clarification to understand the non-FASMO comment?
Scott (Inspur) responds to Hannu and clarifies the FASMO problem.
Robert (Apple) replies to Stephen (Qualcomm) and provides r01.
Stephen (Qualcomm) comments on the r01
Robert (Apple) responds to Stephen's (Qualcomm) comments and provides r02
Stephen (Qualcomm) can agree the r02
Hannu (Nokia) supports r02 as the only possible solution, i.e. we need to update the incorrect note.
Stefan (Ericsson) also agrees with r02
==== Revisions Deadline ====
DongYeon (Samsung) also agree with r02.
==== Comments Deadline ====
Revised
8.11 S2-2203243 CR Approval 23.502 CR3436R1 (Rel-17, 'F'): Correction of last visited TAI requirement Apple Rel-17 Revision of S2-2202236r02. Approved Agreed
8.11 S2-2202281 CR Approval 23.501 CR3604 (Rel-17, 'F'): Criterion of Verification of UE location for UE registering via 5G Satellite Access Inspur Rel-17 r01 agreed. Revised to S2-2203244 Hannu (Nokia) proposes r01 to avoid re-use of reserved word 'country' in different meaning.
Stephen (Qualcomm) comments on the r00 and r01
Scott (Inspur) replies Hannu and Stephen.
Stefan (Ericsson) comments
Chris (Vodafone) objects to r00, but r01 seems OK.
Guillaume (MediaTek Inc.) comments
Runze (Huawei) comments.
Stephen (Qualcomm) comments again on the r00 versus r01
DongYeon (Samsung) objects to r00, but r01 is OK.
Scott(Inspur) replies to Chris.
Scott(Inspur) relies to Stephen (Qualcomm)'s comments
Scott(Inspur) replies to DongYeon (Samsung) and all.
Hannu (Nokia) replies to Scott
Jean Yves (Thales) comments
Scott (Inspur) comments
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01
Scott(Inspur) provides the r02
Hannu (Nokia) supports r02 and thanks Scott for cleaning up the revision.
Stefan (Ericsson) agrees with r02 (and r01)
==== Comments Deadline ====
Hannu (Nokia) comments that r02 is a cleaned up version of r01 to remove changes on changes. Since r02 was provided after the revision deadline, it should go to CC #3 but I support r02 as r01 would need the same cleanup anyway.
Revised
8.11 S2-2203244 CR Approval 23.501 CR3604R1 (Rel-17, 'F'): Criterion of Verification of UE location for UE registering via 5G Satellite Access Inspur Rel-17 Revision of S2-2202281r01. Approved Agreed
8.11 S2-2202329 CR Approval 23.501 CR3607 (Rel-17, 'F'): Clarification on AMF obtaining the satellite-related information Inspur Rel-17 r03 agreed. Revised to S2-2203245 DongYeon (Samsung) comments.
Stefan (Ericsson) agrees with DongYeon that this CR is not needed
Hannu (Nokia) proposes to note this CR for the reasons mentioned by DongYeong and Stefan.
Xiaohua (Inspur) replies and provides r01.
Yuxin (Xiaomi) comments
Xiaohua (Inspur) replies to Yuxin
DongYeon (Samsung) comments, and provides r02.
Hannu (Nokia) provides r03 and comments.
Xiaohua (Inspur) replies to DongYeon and Hannu.
==== Revisions Deadline ====
Yuxin (Xiaomi) can live with r03
Xiaohua (Inspur) accepts r03 and comments.
DongYeon (Samsung) is Okay with r03 and r02 (prefers r03), objects to any other versions.
Jean Yves (Thales) is ok with r03
==== Comments Deadline ====
Revised
8.11 S2-2203245 CR Approval 23.501 CR3607R1 (Rel-17, 'F'): Clarification on AMF obtaining the satellite-related information Inspur Rel-17 Revision of S2-2202329r03. Approved Agreed
8.11 S2-2202380 CR Approval 23.502 CR3442 (Rel-17, 'F'): TAIs reporting corresponding to the Selected PLMN OPPO Rel-17 Approved Agreed
8.11 S2-2202804 CR Approval 23.501 CR3621 (Rel-17, 'F'): RAN Initiated UE Context Release for UE using NR satellite access Samsung Rel-17 r02 agreed. Revised to S2-2203246 Stephen (Qualcomm) comments that the wrong clause is being changed
Scott (Inspur) comments that we support the paper, but it is subject to change.
Hucheng (CATT) has similar understanding as Stephen (Qualcomm).
Yuxin (Xiaomi) provides r02.
DongYeon (Samsung) replies to Scott (Inspur).
DongYeon (Samsung) replies to Stephen (Qualcomm) and Hucheng (CATT), and provides r01.
Stephen (Qualcomm) comments that the r02 is acceptable
Scott (Inspur) replies to DongYeon (Samsung).
Scott (Inspur) comments and propose the way forward.
DongYeon (Samsung) responds to Scott (Inspur), and provides r03.
Scott (Inspur) responds to DongYeon (Samsung), and comment on r03.
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r03
Yuxin (Xiaomi) can accept the r03
Hucheng (CATT) prefers r02, but objects r00 and r03.
DongYeon (Samsung) is Okay with r02 and r03.
Yuxin(Xiaomi) withdraw supporting r03, can live with r02
Hucheng (CATT) clarifies to DongYeon (Samsung).
DongYeon (Samsung) asks everyone if r02 is acceptable.
Jean Yves (Thales) is ok with r02 and comments
==== Comments Deadline ====
Revised
8.11 S2-2203246 CR Approval 23.501 CR3621R1 (Rel-17, 'F'): RAN Initiated UE Context Release for UE using NR satellite access Samsung Rel-17 Revision of S2-2202804r02. Approved Agreed
8.11 S2-2202805 CR Approval 23.502 CR3454 (Rel-17, 'F'): RAN Initiated UE Context Release for UE using NR satellite access Samsung Rel-17 Merged into S2-2201980 Stefan (Ericsson) comments and proposes to merge into S2-2201980
Steve (Huawei) merging into 1980 looks sensible.
DongYeon (Samsung) agrees to MERGE S2-2202805 into S2-2201980.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=15 -
8.12 S2-2201946 LS In Action LS from RAN WG2: LS on Tx Profile RAN WG2 (R2-2203693) Rel-17 Responses drafted in S2-2202283, S2-2202287, S2-2202681. Final response in S2-2203595 Replied to
8.12 S2-2202283 LS OUT Approval [DRAFT] Reply LS on Tx Profile LG Electronics Rel-17 Response to S2-2201946. r08 agreed. Revised to S2-2203595, merging S2-2202681 and S2-2202287. LaeYoung (LGE) provides r01.
Fei (OPPO) comments on r01.
LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) provides response.
LaeYoung (LGE) provides answers to Mehrdad (Samsung).
Mehrdad (Samsung) comments and requests clarification and changes.
LaeYoung (LGE) provides r02.
Fei (OPPO) provides further comments.
Mehrdad (Samsung) provides r03 and also adds further comments
LaeYoung (LGE) provides r04.
Hong (Qualcomm) provides r05.
LaeYoung (LGE) provides r06 with further clean-ups and editorial/minor changes.
Fei (OPPO) provides r07.
LaeYoung (LGE) responds to Fei (OPPO).
Fei (OPPO) responds
==== Revisions Deadline ====
Hong (Qualcomm) cannot accept r07 and prefer r06.
LaeYoung (LGE) is fine with wording suggestion from Fei (OPPO) with small editorial changes.
Fei (OPPO) provides response to LaeYoung (LG).
LaeYoung (LGE) proposes to add 'that seems not controllable by 3GPP standardization' to r07 to move forward.
Fei (OPPO) can only accept r07 and object r00 to r06.
LaeYoung (LGE) is OK to go with r06, and also fine with either option suggested by Hong (Qualcomm).
LaeYoung (LGE) is also fine with wording suggestion from Hong (Qualcomm).
Fei (OPPO) asks clarification on the new wording from Hong (Qualcomm)
Hong (Qualcomm) comments and suggest new wording.
Hong (Qualcomm) replies to Fei.
LaeYoung (LGE) proposes to discuss this LS at CC#2 in order to add the agreeable text to the latest version, r07.
Fei (OPPO) replies to LaeYoung (LGE)
Hong (Qualcomm) replies to Laeyoung.
LaeYoung (LGE) suggests wording on top of wording from Hong (Qualcomm).
LaeYoung (LGE) uploaded r08 adding the agreeable text on top of r07 (latest version before revision deadline) to Revisions folder as well as CC#2 folder for discussion at CC#2.
==== Comments Deadline ====
Revised
8.12 S2-2203595 LS OUT Approval Reply LS on Tx Profile SA WG2 Rel-17 Revision of S2-2202283r08, merging S2-2202681 and S2-2202287. Approved Approved
8.12 S2-2202681 LS OUT Approval [DRAFT] Response LS on Tx Profile Huawei, HiSilicon Rel-17 Response to S2-2201946. Merged into S2-2203595 LiMeng (Huawei) corrects the previous comment.
LiMeng (Huawei) replies.
LaeYoung (LGE) provides comment.
LaeYoung (LGE) responds to LiMeng (Huawei).
Mehrdad (Samsung) suggests to use 2283 as the discussion thread and to finalize the LS
LiMeng (Huawei) is fine to use 2283 as the one to further discuss the issue.
LaeYoung (LGE) proposes to merge this LS into 2283 or get this LS NOTED.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.12 S2-2202287 LS OUT Approval [DRAFT] Reply LS on Tx Profile OPPO Response to S2-2201946. Merged into S2-2203595 LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) responds to LaeYoung (LGE).
LaeYoung (LGE) provides comment.
Mehrdad (Samsung) suggests to use 2283 as the discussion thread and to finalize the LS
LaeYoung (LGE) proposes to merge this LS into 2283 or get this LS NOTED.
Fei (OPPO) responds.
Mehrdad (Samsung) apologies for confusion. 2283 is the thread to merge all the LSs. We follow the discussions in 2283.
LaeYoung (LGE) will reply to Mehrdad (Samsung) on 2283 thread because we agreed to use 2283 thread for further discussion.
Mehrdad (Samsung) comments and requests clarification and changes.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.12 S2-2202284 CR Approval 23.287 CR0177 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, CATT Rel-17 r05 agreed. Revised to S2-2203247, merging S2-2202290 Fei (OPPO) comments on r01 and proposes to focus on reply LS first.
LaeYoung (LGE) provides r01.
Mehrdad (Samsung) suggests to adopt either 2284 or 2290 for the DRX changes of V2X
LaeYoung (LGE) provides r02.
Fei (OPPO) comments on r02.
LaeYoung (LGE) provides r03.
Hong (Qualcomm) comments.
LaeYoung (LGE) replies to Hong (Qualcomm).
Shabnam (Ericsson) provides r04 to make it clearer on the mapping when Tx profile not available and co-signs.
LaeYoung (LGE) thanks to Shabnam (Ericsson) for wording improvement and co-sign.
Mehrdad (Samsung) asks a question for clarification.
LaeYoung (LGE) answers to Mehrdad (Samsung).
Mehrdad (Samsung) replies to LGE.
LaeYoung (LGE) provides r05.
==== Revisions Deadline ====
Fei (OPPO) is fine with r05.
Mehrdad (Samsung) is OK with r05 and would like to co-source this CR based on r05.
LaeYoung (LGE) will add Samsung to the final version.
==== Comments Deadline ====
Revised
8.12 S2-2203247 CR Approval 23.287 CR0177R1 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, CATT, Ericsson, Samsung, OPPO Rel-17 Revision of S2-2202284r05, merging S2-2202290. Approved Agreed
8.12 S2-2202285 CR Approval 23.304 CR0091 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, CATT Rel-17 r04 agreed. Revised to S2-2203248, merging S2-2202289 LaeYoung (LGE) answers to Fei (OPPO).
Fei (OPPO) comments and proposes to focus on reply LS first.
LaeYoung (LGE) provides r01.
Mehrdad (Samsung) suggests to adopt either 2285 or 2289 for the DRX changes of ProSe
LaeYoung (LGE) provides r02.
Fei (OPPO) comments on r02.
LaeYoung (LGE) provides r03.
LaeYoung (LGE) provides r04.
==== Revisions Deadline ====
Fei (OPPO) is fine with r04.
Mehrdad (Samsung) is OK with r04 and would like to co-source this CR based on r04.
LaeYoung (LGE) will add Samsung to the final version.
==== Comments Deadline ====
Revised
8.12 S2-2203248 CR Approval 23.304 CR0091R1 (Rel-17, 'F'): Clarifications on PC5 DRX operations LG Electronics, CATT, Ericsson, Samsung, OPPO Rel-17 Revision of S2-2202285r04, merging S2-2202289. Approved Agreed
8.12 S2-2202288 DISCUSSION Discussion Tx profile. OPPO Rel-17 Noted Noted
8.12 S2-2202289 CR Approval 23.304 CR0092 (Rel-17, 'F'): DRX operations OPPO Rel-17 Merged into S2-2203248 Mehrdad (Samsung) suggests to adopt either 2285 or 2289 for the DRX changes of ProSe
LaeYoung (LGE) proposes to merge this CR into S2-2202285 (LGE, CATT).
==== Revisions Deadline ====
Fei (OPPO) is ok to mark merged or noted.
==== Comments Deadline ====
Merged
8.12 S2-2202290 CR Approval 23.287 CR0178 (Rel-17, 'F'): DRX operations OPPO Rel-17 Merged into S2-2203247 Mehrdad (Samsung) suggests to adopt either 2284 or 2290 for the DRX changes of V2X
LaeYoung (LGE) proposes to merge this CR into S2-2202284 (LGE, CATT).
==== Revisions Deadline ====
Fei (OPPO) is ok to mark merged or noted.
==== Comments Deadline ====
Merged
8.12 S2-2202680 CR Approval 23.287 CR0179 (Rel-17, 'F'): SL DRX update considering new QoS parameters Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2203249 Cai Simon (Nokia) provides comments
LaeYoung (LGE) provides r01.
LaeYoung (LGE) provides r02.
Cai Simon (Nokia) supports r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.12 S2-2203249 CR Approval 23.287 CR0179R1 (Rel-17, 'F'): SL DRX update considering new QoS parameters Huawei, HiSilicon, Tencent Rel-17 Revision of S2-2202680r02. Approved Agreed
8.12 S2-2202704 CR Approval 23.285 CR0064 (Rel-17, 'F'): Clarification on parameter for NR Tx Profile selection LG Electronics Rel-17 Approved Agreed
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:=9 -
8.14 S2-2201942 LS In Information LS from RAN WG1: Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance RAN WG1 (R1-2202912) Rel-17 Noted Yunjing (CATT) proposes to note the LS.
==== Revisions Deadline ====
Noted
8.14 S2-2201948 LS In Action LS from RAN WG2: LS on Positioning in RRC_INACTIVE State RAN WG2 (R2-2203949) Rel-17 Responses drafted in S2-2202915, S2-2202974. Final response in S2-2203250 Replied to
8.14 S2-2202915 LS OUT Approval [DRAFT] Reply LS on Positioning in RRC_INACTIVE State Huawei, HiSilicon Rel-17 Response to S2-2201948. Revised to S2-2203250, merging S2-2202974 Revised
8.14 S2-2203250 LS OUT Approval Reply LS on Positioning in RRC_INACTIVE State SA WG2 Rel-17 Revision of S2-2202915, merging S2-2202974. Approved Approved
8.14 S2-2202974 LS OUT Approval [DRAFT] LS Response to LS on Positioning in RRC_INACTIVE State Qualcomm Incorporated Rel-17 Response to S2-2201948. Merged into S2-2203250 Runze (Huawei) propose to merge the paper into S2-2202915
Stephen (Qualcomm) agrees merger of S2-2202974 into S2-2202915.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.14 S2-2202916 CR Approval 23.273 CR0226 (Rel-17, 'B'): Adding procedures to support UE positioning in RRC inactive state Huawei, HiSilicon Rel-17 Merged into S2-2203251 Stephen (Qualcomm) comments
==== Revisions Deadline ====
Stephen (Qualcomm) proposes that S2-2202916 be merged into S2-2202973
==== Comments Deadline ====
Merged
8.14 S2-2202971 CR Approval 23.273 CR0227 (Rel-17, 'B'): Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state Qualcomm Incorporated Rel-17 Noted Stephen (Qualcomm) proposes to note this CR
==== Comments Deadline ====
Noted
8.14 S2-2202973 CR Approval 23.273 CR0228 (Rel-17, 'B'): Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state Qualcomm Incorporated Rel-17 r01 agreed. Revised to S2-2203251, merging S2-2202916 Yunjing (CATT) provides comments.
Yunjing (CATT) provides comment.
Stephen (Qualcomm) provides an r01 and responds to comments from Yunjing (CATT)
Runze (Huawei) comments.
Stephen (Qualcomm) replies to Runze (Huawei)
Cai Simon (Nokia) provides comments
==== Revisions Deadline ====
Stephen (Qualcomm) replies to Cai Simon (Nokia)
==== Comments Deadline ====
Revised
8.14 S2-2203251 CR Approval 23.273 CR0228R1 (Rel-17, 'B'): Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state Qualcomm Incorporated Rel-17 Revision of S2-2202973r01, merging S2-2202916. Approved 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:=2 -
8.21 S2-2202688 CR Approval 23.502 CR3451 (Rel-17, 'F'): Alignment of terminology for PCF related procedures Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2203432 Belen (Ericsson) provides comments
Mirko (Huawei) responds.
Mirko (Huawei) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.21 S2-2203432 CR Approval 23.502 CR3451R1 (Rel-17, 'F'): Alignment of terminology for PCF related procedures Huawei, HiSilicon Rel-17 Revision of S2-2202688r01. Approved Agreed
8.22 - - - IP address pool information from UDM (TEI17_IPU) - - Docs:=0 -
8.23 - - - Same PCF selection for AMF and SMF (TEI17-SPSFAS) - - Docs:=0 -
8.24 - - - Support of different slices over different Non-3GPP access (TEI17_N3SLICE) - - Docs:=0 -
8.25 - - - Minimization of Service Interruption (MINT) - - Docs:=16 -
8.25 S2-2201957 LS In Action LS from SA WG3: Reply LS on Reply LS on MINT functionality for Disaster Roaming SA WG3 (S3-220518) Rel-17 Noted Hyunsook (LGE) proposes to note this LS.
Lalith(Samsung) also proposes to note this LS.
==== Revisions Deadline ====
Noted
8.25 S2-2202051 CR Approval 23.501 CR3585 (Rel-17, 'F'): Disaster Roaming for Short Message Service Huawei, HiSilicon Rel-17 Postponed Qian (Ericsson) asks question
Haiyang (Huawei) responds to Qian (Ericsson)
Qian (Ericsson) comments and provide r01
Haris(Qualcomm) comments
Haiyang (Huawei) is OK with r01
Haris(Qualcomm) asks question
Hyunsook (LGE) comments
Lalith(Samsung) comments.
Haiyang (Huawei) provides r02
Haris(Qualcomm) comments on r02
Haiyang (Huawei) clarifies to Haris(Qualcomm)
==== Revisions Deadline ====
Haris(Qualcomm) proposes to postpone, no revision is acceptable
==== Comments Deadline ====
Postponed
8.25 S2-2202208 CR Approval 23.501 CR3580R1 (Rel-17, 'F'): Disaster roaming service indication Ericsson Rel-17 Revision of (Endorsed) S2-2201832. Endorsed Qian (Ericsson) responds to Haiyang (Huawei)
Haiyang (Huawei) provides a question
==== Revisions Deadline ====
Hyunsook (LGE) proposes to mark it as 'POSTPONED'
Lalith(Samsung) is OK with 'POSTPONED' or 'ENDORSED'
Qian (Ericsson) comments and consider the paper shall be 'ENDORSED' as the outcome from last SA2 meeting, if we did not get reply from SA5 in time.
Hyunsook (LGE) can agree to mark it as 'ENDORSED'
==== Comments Deadline ====
Endorsed
8.25 S2-2202209 CR Approval 23.502 CR3147R3 (Rel-17, 'F'): Session procedure improvement for MINT Ericsson Rel-17 Revision of (Endorsed) S2-2201833. Endorsed Haiyang (Huawei) provides a question
Qian (Ericsson) responds
==== Revisions Deadline ====
Hyunsook (LGE) proposes to mark it as 'POSTPONED'
Lalith(Samsung) is OK with 'POSTPONED' or 'ENDORSED'
Qian (Ericsson) comments and consider the paper shall be 'ENDORSED' as the outcome from last SA2 meeting, if we did not get reply from SA5 in time.
Hyunsook (LGE) can agree to mark it as 'ENDORSED'
==== Comments Deadline ====
Endorsed
8.25 S2-2202259 CR Approval 23.501 CR3599 (Rel-17, 'F'): Session related subscription infomation LG Electronics Rel-17 r01 agreed. Revised to S2-2203060 Hyunsook (LGE) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.25 S2-2203060 CR Approval 23.501 CR3599R1 (Rel-17, 'F'): Session related subscription information LG Electronics Rel-17 Revision of S2-2202259r01. Approved Agreed
8.25 S2-2202260 CR Approval 23.502 CR3437 (Rel-17, 'F'): Session related subscription infomation LG Electronics Rel-17 r01 agreed. Revised to S2-2203061 Hyunsook (LGE) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.25 S2-2203061 CR Approval 23.502 CR3437R1 (Rel-17, 'F'): Session related subscription information LG Electronics Rel-17 Revision of S2-2202260r01. Approved Agreed
8.25 S2-2202261 CR Approval 23.501 CR3600 (Rel-17, 'F'): Clarification on UE 5GMM Capability LG Electronics Rel-17 Approved Agreed
8.25 S2-2202262 CR Approval 23.501 CR3601 (Rel-17, 'F'): Removing the editor's note related to CT WG1 LG Electronics Rel-17 Approved, merging S2-2202912 Agreed
8.25 S2-2202912 CR Approval 23.501 CR3627 (Rel-17, 'F'): Resolving the EN. Samsung Rel-17 Merged into S2-2202262 Hyunsook (LGE) proposes to mark it as 'merged into 2262'
Lalith(Samsung) agrees to merge into 2262
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.25 S2-2202903 CR Approval 23.501 CR3626 (Rel-17, 'F'): End of disaster condition Samsung Rel-17 Approved Agreed
8.25 S2-2202911 CR Approval 23.502 CR3462 (Rel-17, 'F'): Clarification on MINT support and end of disaster Samsung Rel-17 r02 agreed. Revised to S2-2203062 Haiyang (Huawei) provides r01
Hyunsook (LGE) provides r02
==== Revisions Deadline ====
Lalith(Samsung) is OK r02
==== Comments Deadline ====
Revised
8.25 S2-2203062 CR Approval 23.502 CR3462R1 (Rel-17, 'F'): Clarification on MINT support and end of disaster Samsung Rel-17 Revision of S2-2202911r02. Approved Agreed
8.25 S2-2202050 CR Approval 23.502 CR3421 (Rel-17, 'F'): Network-initiated Deregistration if disaster condition is no longer being applicable Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2203063 Lalith(Samsung) comments
Qian (Ericsson) comments and provides r01
Hyunsook (LGE) provides r02
Haiyang (Huawei) is OK with r02
==== Revisions Deadline ====
Lalith(Samsung) is OK with r02
Qian (Ericsson) is ok with r02
==== Comments Deadline ====
Revised
8.25 S2-2203063 CR Approval 23.502 CR3421R1 (Rel-17, 'F'): Network-initiated Deregistration if disaster condition is no longer being applicable Huawei, HiSilicon Rel-17 Revision of S2-2202050r02. Approved Agreed
8.26 - - - Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) - - Docs:=1 -
8.26 S2-2202544 CR Approval 23.501 CR3612 (Rel-17, 'F'): AMF selection to support HLcom feaure for RedCap using power saving function Sony Rel-17 Postponed Antoine (Orange) asks a question and comments.
Lars (Sony) responds to Antoine.
Antoine (Orange) provides r01.
Lars (Sony) is ok with r01 provided by Antoine.
Steve (Huawei) comments
Qian (Ericsson) provides comments.
Lars (Sony) responds to Steve
Lars (Sony) responds to Qian
Qian (Ericsson) provides further comments.
Qian (Ericsson) responds to Lars (Sony)
Steve (Huawei) thanks Lars for the reference.
Hannu (Nokia) supports Qian (Ericsson) and comments.
Hannu (Nokia) provides r03.
Lars (Sony) thanks Qian for r02
Qian (Ericsson) comments and provides r02
Steve (Huawei) a bit more checking would be a good thing.
==== Revisions Deadline ====
Lars (Sony) ask what to at this meeting?
Steve (Huawei) lets postpone and come back.
==== Comments Deadline ====
Postponed
8.27 - - - Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) - - Docs:=15 -
8.27 S2-2201932 LS In Action LS from RAN WG3: LS on opens issues for NB-IoT and eMTC support for NTN RAN WG3 (R3-221406) Rel-17 Revision of Postponed S2-2200418 from S2#149E. Response drafted in S2-2202006, S2-2202875. Final response in S2-2203064 Replied to
8.27 S2-2202875 LS OUT Approval [DRAFT] Reply LS on open issues for NB-IoT and eMTC support for NTN MediaTek Inc. Rel-17 Response to S2-2201932. Merged into S2-2203064 Guillaume (MediaTek Inc.) proposes to merge 2875 with 2006.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.27 S2-2202006 LS OUT Approval Reply LS on opens issues for NB-IoT and eMTC support for NTN Qualcomm Rel-17 Response to S2-2201932. r02 agreed. Revised to S2-2203064, merging S2-2202875 Guillaume (MediaTek Inc.) provides r01.
Stefan (Ericsson) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.27 S2-2203064 LS OUT Approval Reply LS on opens issues for NB-IoT and eMTC support for NTN SA WG2 Rel-17 Revision of S2-2202006r02, merging S2-2202875. Approved Approved
8.27 S2-2202005 LS OUT Approval NB-IoT Control Plane Relocation procedure upon NTN to TN mobility Qualcomm Rel-17 Noted Steve (Huawei) comments, related to CR in S2-2202004. Needs to wait for fate of 2004.
Haris(Qualcomm) provides r01
Stefan (Ericsson) asks for clarification
Haris(Qualcomm) comments and provides r02
Steve (Huawei) why is this needed?
Stefan (Ericsson) also not clear why it is needed, but provides r03 just in case
==== Revisions Deadline ====
Steve (Huawei) objects to all revisions (r00, r01, r02, r03).
==== Comments Deadline ====
Noted
8.27 S2-2202777 LS In Action LS from CT WG1: Reply LS on UE providing Location Information for NB-IoT CT WG1 (C1-222100) Rel-17 Noted Stefan (Ericsson) proposes to note this LS
==== Revisions Deadline ====
Noted
8.27 S2-2202787 LS In Action LS from RAN WG3: Reply LS on UE providing Location Information for NB-IoT RAN WG3 (R3-222858) Rel-17 Noted Guillaume (MediaTek Inc.) proposes to note the LS. No response needed.
==== Revisions Deadline ====
Noted
8.27 S2-2202788 LS In Information LS from RAN WG3: Reply LS on UE location during initial access in NTN RAN WG3 (R3-222861) Rel-17 Noted Steve (Huawei) Proposes to note.
==== Revisions Deadline ====
Noted
8.27 S2-2202795 LS In Information LS from SA WG3: Reply LS on security concerns for UE providing Location Information for NB-IoT SA WG3 (S3-220544) Rel-17 Noted Steve (Huawei) Proposes to note.
==== Revisions Deadline ====
Noted
8.27 S2-2202003 DISCUSSION Approval TN-NTN NB-IoT mobility for CP-CIoT Qualcomm Rel-17 Noted Noted
8.27 S2-2202004 CR Endorsement 23.401 CR3693 (Rel-17, 'C'): NB-IOT TN-NTN mobility for CP-CIoT Qualcomm Incorporated Rel-17 Postponed Hannu (Nokia) asks for clarification as revision might be needed?
Hannu (Nokia) asks for clarification as revision might be needed? (re-sending to correct the AI)
Haris(Qualcomm) answers
Steve (Huawei) comments
Stefan (Ericsson) provides comments
Haris(Qualcomm) comments
Guillaume (MediaTek Inc.) provides comments and r01.
Haris(Qualcomm) comments on r01
Hannu (Nokia) is open to either endorsing the CR or sending LS, but points out that neither r00 nor r01 really solve the problem so more revisions would be needed?
==== Revisions Deadline ====
Haris(Qualcomm) agrees with Hannu and proposes to postpone
Steve (Huawei) objects to r00, is ok with r01. Postponing is not acceptable.
Stefan (Ericsson) OK to note the CR
==== Comments Deadline ====
Postponed
8.27 S2-2202007 CR Approval 23.401 CR3694 (Rel-17, 'F'): Removal of unecessary LTE-M satellite Indication in S1-AP Qualcomm Incorporated Rel-17 r03 agreed. Revised to S2-2203065 Guillaume (MediaTek Inc.) comments and provides r01.
Haris(Qualcomm) comments
Guillaume (MediaTek Inc.) replies to Haris (Qualcomm)
Steve (Huawei) thanks Haris
Stefan (Ericsson) provides r02
Haris(Qualcomm) replies
Steve (Huawei) comments
Steve (Huawei) provides r03
==== Revisions Deadline ====
Steve (Huawei) is ok with r03, except the spec on the coversheet is wrong (should be 23.401 not 23.501).
Haris(Qualcomm) will correct the coverheet indicated spec to TS 23.401 in final version
==== Comments Deadline ====
Revised
8.27 S2-2203065 CR Approval 23.401 CR3694R1 (Rel-17, 'F'): Removal of unecessary LTE-M satellite Indication in S1-AP Qualcomm Incorporated Rel-17 Revision of S2-2202007r03. Approved Agreed
8.27 S2-2202237 CR Approval 23.401 CR3697 (Rel-17, 'F'): IoT NTN: Correction of last visited TAI requirement Apple Rel-17 Postponed Hannu (Nokia) provides r01.
Hannu (Nokia) provides r01. (re-sending to correct the wrong AI in the previous email)
Robert (Apple) replies to Hannu's (Nokia) comments and provides r02.
Hannu (Nokia) supports r02
Haris(Qualcomm) provides r03
Stefan (Ericsson) provides r04
Hannu (Nokia) provides r05
Robert (Apple) responds to Hannu (Nokia).
Chris (Vodafone) provides rev 7.
==== Revisions Deadline ====
Robert (Apple) requests to postpone this CR.
Chris (Vodafone) agrees to postpone this CR. We should come up with a common text for 5GC-NR-NTN and EPC-IoT -NTN
==== Comments Deadline ====
Postponed
8.27 S2-2202395 CR Approval 23.401 CR3698 (Rel-17, 'F'): IoT NTN: Alignment of TA handling for moving cells with NR NTN OPPO Rel-17 Approved Agreed
8.28 - - - Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups - - Docs:=36 -
8.28 S2-2201952 LS In Information LS from RAN WG2: LS out on PEI and UE Subgrouping RAN WG2 (R2-2204240) Rel-17 Response drafted in S2-2202900. Final response in S2-2203252 Replied to
8.28 S2-2202900 LS OUT Approval [DRAFT] LS out on PEI and UE Subgrouping Qualcomm Europe Inc. Sweden Rel-17 Response to S2-2201952. r04 agreed. Revised to S2-2203252 Qian (Ericsson) provides r01
Miguel (Qualcomm) ok with r01
Qian (Ericsson) asks a further question
Steve (Huawei) comments, provides r02
Steve (Huawei) provides r04
Miguel (Qualcomm) responds to Qian, Steve provides r03
==== Revisions Deadline ====
Qian (Ericsson) supports r04
==== Comments Deadline ====
Revised
8.28 S2-2203252 LS OUT Approval Reply LS out on PEI and UE Subgrouping SA WG2 Rel-17 Revision of S2-2202900r04. Approved Approved
8.28 S2-2201944 LS In Information LS from RAN WG2: Reply LS on LTE User Plane Integrity Protection RAN WG2 (R2-2203663) Rel-17 Noted Tim (Vodafone) believes this LS can be noted by SA2 and treated by SA3.
==== Revisions Deadline ====
Noted
8.28 S2-2201947 LS In Action LS from RAN WG2: Reply LS on Slice list and priority information for cell reselection RAN WG2 (R2-2203807) Rel-17 Response drafted in S2-2202658. Final response in S2-2203597 Replied to
8.28 S2-2202658 LS OUT Approval [DRAFT] Reply LS on Slice list and priority information for cell reselection ZTE Rel-17 Response to S2-2201947. r17 + changes agreed. Revised to S2-2203597, merging S2-2202228. Jinguo(ZTE) provides r01
alessio(nokia) provides r02
Peter Hedman (Ericsson) provides r03
alessio (nokia) cannot agree with r03
Peter Hedman (Ericsson) provides reply and cannot accept r02
Jinguo(ZTE) provides r04
Haiyang (Huawei) provides r05
Peter Hedman (Ericsson) provides r06
Jinguo(ZTE) provides r07
Haiyang (Huawei) provides response to Peter(Ericsson) and r08
alessio (nokia) provides r09 cannot agree with any other revision.
Peter Hedman (Ericsson) objects to r09, instead provides r10
alessio (nokia) objects to r10
==== Revisions Deadline ====
Jinguo(ZTE) suggest to keep it open and discuss it during CC#2 or CC#3
==== Comments Deadline ====
Jinguo(ZTE) provides r11
Peter Hedman (Ericsson) provides comments
Tricci So (OPPO) provides r13 for couple editorial changes.
Alessio(nokia) provides r14
Jinguo(ZTE) provides r16 and ask to ignore r15.
Alessio(nokia) provides r17
Jinguo(ZTE) is fine with r17
Peter Hedman (Ericsson) provides comments that R17 endanger other WGs to finalize the work in Q2
Revised
8.28 S2-2203597 LS OUT Approval Reply LS on Slice list and priority information for cell reselection SA WG2 Rel-17 Revision of S2-2202658r17 + changes, merging S2-2202228. Approved Approved
8.28 S2-2202052 CR Approval 23.501 CR3586 (Rel-17, 'B'): Enabling Network Slice Access Stratum groups Huawei, HiSilicon Rel-17 Merged into S2-2203618 Jinguo(ZTE) suggests to merge into 2706 to use single thread for further discussion.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202053 CR Approval 23.502 CR3422 (Rel-17, 'B'): Enabling Network Slice Access Stratum groups Huawei, HiSilicon Rel-17 Merged into S2-2203619 Jinguo(ZTE) suggests to merge into 2711 and use single thread for futher discussion
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202176 CR Approval 23.501 CR3592 (Rel-17, 'F'): Updates to support 5G NSWO Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2203254 Laurent (Nokia): suggests to merge his own 23.501 CR (2176) into 2677
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202177 CR Approval 23.502 CR3429 (Rel-17, 'F'): Updates to support 5G NSWO Nokia, Nokia Shanghai Bell Rel-17 Noted Apostolis (Lenovo) proposes to Note this CR.
Laurent (Nokia): provides r01
Apostolis (Lenovo) cannot accept r01.
Marco (Huawei) comment.
==== Revisions Deadline ====
Apostolis (Lenovo) objects to r00 and r01.
==== Comments Deadline ====
Noted
8.28 S2-2202178 LS OUT Approval [DRAFT] LS on 5G NSWO roaming aspects Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2203253 Laurent (Nokia): provides r01
Marco (Huawei): provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
8.28 S2-2203253 LS OUT Approval LS on 5G NSWO roaming aspects SA WG2 Rel-17 Revision of S2-2202178r02. Approved Approved
8.28 S2-2202223 DISCUSSION Agreement Discussion on Slice list and priority information for cell reselection. Ericsson Noted Noted
8.28 S2-2202224 CR Approval 23.501 CR3317R5 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes Ericsson Rel-17 Revision of SP-220319. Revised to S2-2203620, merging S2-2202702 and S2-2202225 Peter (Ericsson) provides comments and r01 as per CC#1 working assumption
alessio(Nokia) is ok with this revision r01, Nokia, Nokia Shanghai Bell can be added as supporting company.
Jinguo(ZTE) supports this paper and can be added as supporting company, and provide additional comment
Peter Hedman (Ericsson) provides reply
Jinguo(ZTE) corrects the title (which miss an 'S').
Peter Hedman (Ericsson) provides r04
Haiyang (Huawei) provides r05
Peter Hedman (Ericsson) provides comment that r05 leaves the option for NSAG priorities to the UE implementation, i.e. r06 clarifies that intention but Ericsson got concerns with leaving this to UE implementation.
Jinguo(ZTE) provides r07
Haiyang (Huawei) responds to Peter (Ericsson)
alessio(nokia) can only accept r03
Peter Hedman (Ericsson) provides reply and cannot accept r03
==== Revisions Deadline ====
Jinguo(ZTE) propose a way forward
Dan(China Mobile) provide r10 and suggest to endorse r10 in this emeeting
Haiyang (Huawei) comments. Suggest to endorse r05.
==== Comments Deadline ====
Haiyang(Huawei) suggests one more EN on Jinguo (ZTE)'s proposal: 'When there is TAC in the NSAG information, whether the priority is valid within a TA or among different TAs (i.e. unique per PLMN/larger area) is FFS'
Revised
8.28 S2-2203620 CR Approval 23.501 CR3317R7 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes Ericsson, ZTE, AT&T, China Mobile, OPPO Rel-17 Revision of S2-2202224, merging S2-2202702 and S2-2202225. This CR was agreed Agreed
8.28 S2-2202225 CR Approval 23.502 CR3435 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes Ericsson Rel-17 Merged into S2-2203620 Jinguo(ZTE) suggests to merge into 2711 and use single thread for futher discussion
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202226 CR Approval 23.501 CR3482R2 (Rel-17, 'B'): Enabling Network Slice Access Stratum groups Ericsson Rel-17 Revision of SP-220317. Merged into S2-2203618 Jinguo(ZTE) suggests to merge into 2706 to use single thread for further discussion.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202227 CR Approval 23.502 CR3334R2 (Rel-17, 'B'): Enabling Network Slice Acess stratum group Ericsson Rel-17 Revision of SP-220318. Merged into S2-2203619 Jinguo(ZTE) suggests to merge into 2711 and use single thread for futher discussion
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202228 LS OUT Approval [DRAFT] LS on enabling support for Slice Groups and Slice priorities for RAN Slicing Ericsson Rel-17 Merged into S2-2203597 Jinguo(ZTE) suggests to merge into 2658
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202655 DISCUSSION Agreement NSWO and N3GPP access support. Huawei, HiSilicon Rel-17 Noted Apostolis (Lenovo) provides comments and does not agree with conclusion #2.
Laurent (Nokia): objects to any version of this Tdoc (to discuss only the CR)
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
8.28 S2-2202659 CR Approval 23.501 CR3539R2 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups ZTE, China Mobile Rel-17 Revision of SP-220303. Merged into S2-2203618 Jinguo(ZTE) suggests to merge into 2706 and use single thread for futher discussion
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202676 DISCUSSION Discussion Proposal on slice priority and slice group China Mobile Rel-17 Noted Noted
8.28 S2-2202677 CR Approval 23.501 CR3617 (Rel-17, 'F'): 23.501: NSWO and N3GPP access support Huawei Rel-17 r05 agreed. Revised to S2-2203254, merging S2-2202176 Laurent (Nokia): provides r01
Apostolis (Lenovo) asks questions and proposes changes.
Stefan (Ericsson) provides r02
Haris(Qualcomm) provides r03
Marco (Huawei) answers to Apostolis (Lenovo) .
Marco(Huawei) provides r04
Stefan (Ericsson) provides r05
Walter Dees (Philips) agrees with Laurent (Nokia).
Marco (Huawei) comments on SNPN.
Laurent (Nokia): provides r06
Haris(Qualcomm) comments on r06 and suggests to not consider SNPN case in rel.17
Laurent (Nokia): answers
Stefan (Ericsson) provides r07
Laurent (Nokia): provides r08
Marco (huawei) objects to any CR version including support in SNPN in R17
==== Revisions Deadline ====
Laurent (Nokia): objects to R00; order of preference is R08 preferred then R07 then R06
Josep (DT) objects to r08, r07, r06. Shares Marco's (Huawei) and Haris' (Qualcomm) view.
Marco (huawei): objects to r06, r07 r08 for SNPN part. Agreed with r05, however It is ok to add revisions to SBA roaming description of r07 in r05.
Stefan (Ericsson) OK with r05 but there are remaining errors in the SBA figures that were fixed in r07
==== Comments Deadline ====
Revised
8.28 S2-2203254 CR Approval 23.501 CR3617R1 (Rel-17, 'F'): 23.501: NSWO and N3GPP access support Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2202677r05, merging S2-2202176. Approved Agreed
8.28 S2-2202702 CR Approval 23.501 CR3317R6 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung Rel-17 Revision of S2-2200508. Merged into S2-2203620 Alessio(Nokia) provides r01
Peter Hedman (Ericsson) provides comment that RAN is in a better position to know how to limit the number of re-directs which is the main goal.
Jinguo(ZTE) suggests to merge into 2224 and use single thread for futher discussion
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
8.28 S2-2202706 CR Approval 23.501 CR3539R3 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd, ZTE, InterDigital, Xiaomi, LGE, Samsung Rel-17 Revision of S2-2200847. Revised to S2-2203618, merging S2-2202052, S2-2202226 and S2-2202659 Alessio(Nokia) provides r01
Atsushi(NTT DOCOMO) provides comments.
Jinguo(ZTE) response to Atsushi(NTT DOCOMO)
Atsushi(NTT DOCOMO) response to Jinguo(NTT DOCOMO)
Atsushi(NTT DOCOMO) corrects the comments; it's Jinguo (ZTE) very sorry
Haiyang (Huawei) provides r02
Peter Hedman (Ericsson) provides comments
Guillaume (MediaTek Inc.) provides r03.
Alessio(Nokia) provides r04
Peter Hedman (Ericsson) provides reply and r05
Alessio(Nokia) provides reply and r06
Haiyang (Huawei) comments on r05/ r06
Peter Hedman (Ericsson) provides questions and r07
Haiyang(Huawei) provides r08
Peter Hedman (Ericsson) provides r09
alessio(Nokia) replies to comments by Haiyang (Huawei) on r05/ r06
Alessio(nokia) cannot agree with r08 as, as we already clarifies) the fact a NSAG is unique per PLMN does not eliminate its association to a TA needs to be known unless these are supported in all the cells of the PLMN.
alessio(nokia) cannot agree to r09 as the EN introduces an issue that does not exist if we allow the addition of TAC to NSAG (as this allows including also NSAGs that are reused). It is because of revisions not by source companies that this EN becomes necessary.
Alessio(nokia) can accept r07
Guillaume (MediaTek Inc.) provides r10
alessio(nokia) provides r11
==== Revisions Deadline ====
Jinguo(ZTE) suggest to use r11 as basis
Dongeun (Samsung) supports r11 which aligns with the WA at CC#1.
?
Haiyang (Huawei) suggest to add one more EN
Peter Hedman (Ericsson) provides comments and propose that r11 needs more work, i.e. objects to r11.
alessio(nokia) ok to use r11 as basis but I wonder why from SA2 perspective it would be acceptable to restrict the RA formation to enable cell reselection just to not include a TAC in a configuration passed via NAS, when we already can pass up to 16 TAIs (incl. PLMN Id) in the RA. At least nokia does not like the idea this feature would introduce constraints to RA formation (i.e. potentially make RA smaller than needed).
Alessio(Nokia) accepts ontly to include this EN: 'Editor's Note: TAC information iclusion in in NSAG information depends on enabling TAC advertisement in 38.331 SIB format
alessio (Nokia) considers the objections by erisson not valid and explains why
Dieter (Deutsche Telekom) objects to any revision including editor's note. Stage 3 work groups need to be able to finish the work in this quarter.
Jinguo(ZTE) suggest to update the following on top of r11 and approve/technique endorse r11
Peter Hedman (Ericsson) provides reply to Nokia
Guillaume (MediaTek Inc.) objects to r11 and responds to Peter (Ericsson), Alessio (Nokia).
Jinguo(ZTE) asks question to Guillaume (MediaTek Inc.)
Peter Hedman (Ericsson) provides reply to Guillaume
Haiyang (Huawei) is OK with the EN proposed by Alessio(Nokia): 'Editor's Note: TAC information iclusion in in NSAG information depends on enabling TAC advertisement in 38.331 SIB format' with considering the open issue on priority will be added as EN in 2224
==== Comments Deadline ====
Revised
8.28 S2-2203618 CR Approval 23.501 CR3539R4 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd, ZTE, InterDigital, Xiaomi, LGE, Samsung, AT&T, Oppo, Huawei Rel-17 Revision of S2-2202706, merging S2-2202052, S2-2202226 and S2-2202659. This CR was agreed Agreed
8.28 S2-2202711 CR Approval 23.502 CR3300R3 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung Rel-17 Revision of S2-2200918. Revised to S2-2203619, merging S2-2202053 and S2-2202227 Peter (Ericsson) provides comments and questions
Alessio(nokia) replies. and provides r01
Peter Hedman (Ericsson) provides explanation why Service accept need also the priority information
Peter Hedman (Ericsson) provides r02
Peter Hedman (Ericsson) it is not acceptable to have the feature cause more redirections between frequencies than with legacy logic i.e. we object to r01 and r00 as we need the AMF to be able to send the NSAG priorities in the Service Accept.
Alessio(nokia) comments that the AMF may chose to not store the NSAGs for slices it does not support and rely on NSSF to provide the right NSAG configuration for all subscribed slices. this is why the 'GET' operation is needed (to outsource the NSAG configuration to be valid beyond the supported slices by the AMF). we do not see the Service accept need as the NSAG configuration should be from the same AMF as before and for same RA. we do not accept r02 as it seems still not justified and it seems the RAN now reshuffles the priorities of the groups! RAN can still cause stickiness to a band using dedicated signalling per UE.
alessio(nokia) cannot accept the change of slice priorities as by product or dependent variable of RRM as NOKIA has proven the RAN can do RRM as it likes and cause the UE to camp on the band it likes at any time using dedicated signalling irrespective of the group priorities. so we insist on not including the SR aspect as the RAN will decide whether to pin the UE to current band for up to T320.
Peter Hedman (Ericsson) provides reply that it is not acceptable to suddenly disable the feature just because Nokia proposal does not work
Alessio(nokia) replies to Ericsson
==== Revisions Deadline ====
Jinguo(ZTE) comments and propose a way forward, suggest to technique endorse r01
Peter Hedman (Ericsson) provides comments and object to approve r01, but conditionally ok to technically endorse the r01 as basis for work at the next meeting.
alessio(Nokia) agrees to proceed with r01 as the service accept proposal by ericsson is new and not enough motivation has been provided given that the RAN can already steer the UE to a certain band using UE specific policies, if so desired, not impacting the NSAG priorities that should be based on service level criteria set by HPLMN.
Alessio(nokia) comments that if there is no agreement then the feature is postponed so Peter Hedman (Ericsson) is asking to postpone the feature if he wants to make the acceptance conditional to adding something people do not agree with as not needed. we should have a working agreement
Dieter (Deutsche Telekom) comments.
Jinguo(ZTE) replies
==== Comments Deadline ====
Revised
8.28 S2-2203619 CR Approval 23.502 CR3300R4 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung, AT&T, Oppo, Huawei Rel-17 Revision of S2-2202711, merging S2-2202053 and S2-2202227. This CR was agreed Agreed
8.28 S2-2202725 DISCUSSION Discussion Discussion on Slice list and priority information for cell reselection. Nokia, Nokia Shanghai Bell, InterDigital, NEC Rel-17 Noted Noted
8.28 S2-2202739 CR Approval 23.502 CR3102R3 (Rel-17, 'F'): AMF relocation in connected state NEC Rel-17 Revision of S2-2201165. r02 + changes agreed. Revised to S2-2203598 (New CR number 3465 allocated as this one was already TSG SA approved). Jinguo(ZTE) propose to note this paper
Fenqin(Huawei) share the view as Jinguo
Jinguo(ZTE) replies to Kundan(NEC)
Alessio(Nokia) requests to just remove the editor's note and approve r01
Kundan(NEC) addresses Jinguo and Fenqin concern.
Peter Hedman (Ericsson) provides r02
Jinguo(ZTE) is ok with r02
Fenqin (Huawei) is also ok with r02
==== Revisions Deadline ====
alessio(Nokia) would suggest to update to r03 in draft folder in CC#2/3 as there is a coversheet error in r02 and also the note can be made a little bit more clear with the addition of an if (as we update the coversheet it is worth it)
Kundan(NEC) is fine with r02. don't think r03 is needed.
==== Comments Deadline ====
Revised
8.28 S2-2203598 CR Approval 23.502 CR3465 (Rel-17, 'F'): AMF relocation in connected state NEC, Nokia; Nokia Shanghai Bell., Ericsson Rel-17 Revision of S2-2202739r02 + changes. Approved Agreed
8.28 S2-2202786 LS In Information LS from RAN WG3: Reply LS on User Plane Integrity Protection for eUTRA connected to EPC RAN WG3 (R3-222610) Noted Noted
8.28 S2-2202791 LS In Action LS on 5G NSWO roaming aspects SA WG3 (S3-220446) Rel-17 Postponed Postponed
8.28 S2-2202792 LS In Action LS from SA WG3: Reply LS on LTE User Plane Integrity Protection SA WG3 (S3-220464) Rel-17 Noted Haiyang (Huawei) suggests to note this LS as no action is needed for SA2
==== Revisions Deadline ====
Noted
9 - - - Rel-18 SIDs - - Docs:=0 -
9.1 - - - Study on System Enabler for Service Function Chaining (FS_SFC) - - Docs:=19 -
9.1 - - - General - - Docs:=1 -
9.1 S2-2202651 P-CR Approval 23.700-18: Updating Annex A. ETRI Rel-18 Approved Approved
9.1 - - - Key issues - - Docs:=2 -
9.1 S2-2202650 P-CR Approval 23.700-18: Updating KIs. ETRI Rel-18 r04 agreed. Revised to S2-2203433 Megha(Intel) provides comments
Fenqin (Huawei) agree with the view from Intel
Stefan (Ericsson) agrees with Huawei and Intel
Yoohwa (ETRI) responds to Megha (Intel)
Megha (Intel) provides r01 and comments
Yoohwa (ETRI) agrees to r01 from Megha.
Fenqin (Huawei) provides r02
Laurent (Nokia): provides r03
Stefan (Ericsson) provides questions and r04
==== Revisions Deadline ====
Laurent (Nokia): objects to any version except R03 and R04
Stefan (Ericsson) objects to any revision except r04
Yoohwa (ETRI) is ok with r04.
==== Comments Deadline ====
Revised
9.1 S2-2203433 P-CR Approval 23.700-18: Updating KIs. ETRI Rel-18 Revision of S2-2202650r04. Approved Approved
9.1 - - - Solutions - - Docs:=16 -
9.1 S2-2201978 P-CR Approval 23.700-18: Solution for Key Issue #1 for Traffic Steering Policy and SFC Enhancements. Ericsson Rel-18 r03 agreed. Revised to S2-2203434 Megha (Intel) provides comments
Stefan (Ericsson) replies and provides r01
Megha (Intel) provides r02 and comments
Stefan (Ericsson) provides r03
==== Revisions Deadline ====
Megha(Intel) is ok with r02, r03
Stefan (Ericsson) cannot accept r02. OK with r03.
==== Comments Deadline ====
Revised
9.1 S2-2203434 P-CR Approval 23.700-18: Solution for Key Issue #1 for Traffic Steering Policy and SFC Enhancements. Ericsson Rel-18 Revision of S2-2201978r03. Approved Approved
9.1 S2-2201979 P-CR Approval 23.700-18: Solution for Key Issue #2 for Exposure to enable AF to request predefined SFC for traffic flow(s) related with target UE(s). Ericsson Rel-18 r03 agreed. Revised to S2-2203435 Megha(Intel) asks question for clarification
Fenqin(Huawei) asks one question for clarification
Megha(Intel) provides comments
Stefan (Ericsson) replies to Megha and provides r01
Stefan (Ericsson) replies to Fenqin
Fenqin (Huawei) replies to Stefan
Megha (Intel) provides r02 and comments
Stefan (Ericsson) provides r03
==== Revisions Deadline ====
Megha(Intel) is ok with r02, r03
Stefan (Ericsson) cannot accept r02. OK with r03.
==== Comments Deadline ====
Revised
9.1 S2-2203435 P-CR Approval 23.700-18: Solution for Key Issue #2 for Exposure to enable AF to request predefined SFC for traffic flow(s) related with target UE(s). Ericsson Rel-18 Revision of S2-2201979r03. Approved Approved
9.1 S2-2202206 P-CR Approval 23.700-18: New Solution: AF influencing Service Function Chaining support by 5GC. Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2203436 Laurent (Nokia): provides r01
Megha(Intel) provides comments and questions for clarification
Stefan (Ericsson) provides comments and questions
Fenqin (Huawei) provides comments and questions
Megha (Intel) provides more comments
Laurent (Nokia): provides r02
Stefan (Ericsson) adds one question
Fenqin (Huawei) agree the view on the exposure issue as Stefan mentioned and provides r03
Laurent (Nokia): provides r04
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.1 S2-2203436 P-CR Approval 23.700-18: New Solution: AF influencing Service Function Chaining support by 5GC . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202206r04. Approved Approved
9.1 S2-2202231 P-CR Approval 23.700-18: KI 1 and KI 2: New Solution for traffic steering control and SFC enhancements. Intel Rel-18 r04 agreed. Revised to S2-2203437 Laurent (Nokia): Comments/ questions
Stefan (Ericsson) provides comments/questions
Fenqin (Huawei) share the similar view.
Megha (Intel) provides r01 and further clarification.
Stefan (Ericsson) provides additional comments
Fenqin (Huawei) provides comment.
Megha(Intel) provides r02 and some further comments
Laurent (Nokia): provides r03
Megha (Intel) provides r04 and some comments
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 + R01 + R02
==== Comments Deadline ====
Revised
9.1 S2-2203437 P-CR Approval 23.700-18: KI 1 and KI 2: New Solution for traffic steering control and SFC enhancements. Intel Rel-18 Revision of S2-2202231r04. Approved Approved
9.1 S2-2202319 P-CR Approval 23.700-18: Solution for KI #1: UPF enhancement with SFC capability. ETRI Rel-18 r01 agreed. Revised to S2-2203438 Stefan (Ericsson) provides comments/questions
Fenqin (Huawei) provides comments/questions
Yoohwa (ETRI) provides r01.
==== Revisions Deadline ====
Laurent (Nokia): objects to R00
==== Comments Deadline ====
Revised
9.1 S2-2203438 P-CR Approval 23.700-18: Solution for KI #1: UPF enhancement with SFC capability. ETRI Rel-18 Revision of S2-2202319r01. Approved Approved
9.1 S2-2202336 P-CR Approval 23.700-18: Solution for KI#2: Service Function Chaining exposure. ETRI Rel-18 r01 agreed. Revised to S2-2203439 Megha(Intel) provides comments and questions for clarification.
Laurent (Nokia): Comments that clarifications are required in the Tdoc
Stefan (Ericsson) provides comments/questions
Stefan (Ericsson) replies to Jaewook
Jaewook (ETRI) answers to Laurent (Nokia) and ask for clarification
Jaewook (ETRI) answers to Stefan (Ericsson) and ask for clarification
Jaewook (ETRI) answers to Megha(Intel) and ask for clarification
Fenqin (Huawei) provides comments/questions
Megha (Intel) responds to Jaewook (ETRI)
Jaewook (ETRI) answer Fenqin (Huawei) and provides r01.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version BUT as he does not want to block the solution can live with R01 with the addition of an EN just above 6.X.2: EN: the content of the classification rule referred to in Table 6.x.1-4 as well as its usage in 5GC is FFS.
Jaewook (ETRI) to Laurent (Nokia) and all: Jaewook (ETRI) is ok with R01 with the addition of an EN for approval.
Megha(Intel) objects to the r00 (original), ok with r01
==== Comments Deadline ====
Revised
9.1 S2-2203439 P-CR Approval 23.700-18: Solution for KI#2: Service Function Chaining exposure. ETRI Rel-18 Revision of S2-2202336r01. Approved Approved
9.1 S2-2202483 P-CR Approval 23.700-18: Solution for KI#2: Enhancing Application Function influence on traffic routing to an N6-LAN based on pre-defined SFC policies. Lenovo Rel-18 r03 agreed. Revised to S2-2203440 Megha(Intel) provides comments and proposes merging this document with S2-2202206 (Nokia) and S2-2201979 (Ericsson)
Laurent (Nokia): Comments asking clarifications (changes) within the tdoc
Dimitris (Lenovo) provides r01 to address comments
Fenqin (Huawei) provides comments
Dimitris (Lenovo) responds to Fenqin (Huawei)
Fenqin (Huawei) ask two question.
Megha (Intel) provides some comments
Dimitris (Lenovo) provides r02 responds to Megha and Fenqin
Fenqin (Huawei) provides r03
Stefan (Ericsson) supports adding this EN
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 and R01
Fenqin (Huawei) only accept r03
Megha(Intel) is ok with r03, r04
==== Comments Deadline ====
Revised
9.1 S2-2203440 P-CR Approval 23.700-18: Solution for KI#2: Enhancing Application Function influence on traffic routing to an N6-LAN based on pre-defined SFC policies. Lenovo Rel-18 Revision of S2-2202483r03. Approved Approved
9.1 S2-2202538 P-CR Approval 23.700-18: KI#1/KI#2, AF request predefined SFC for traffic flow(s) related with target UE(s). Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203441 Fenqin (Huawei) provides responds
Stefan (Ericsson) provides questions and comments
Megha (Intel) provides comments
Fenqin (Huawei) provides feedback and provides r01
Laurent (Nokia): provides r02
Fenqin (Huawei) provides r03
==== Revisions Deadline ====
Megha(Intel) is ok with r03
==== Comments Deadline ====
Revised
9.1 S2-2203441 P-CR Approval 23.700-18: KI#1/KI#2, AF request predefined SFC for traffic flow(s) related with target UE(s). Huawei, HiSilicon Rel-18 Revision of S2-2202538r03. Approved Approved
9.2 - - - Study on Generic group management, exposure and communication enhancements (FS_GMEC) - - Docs:=43 -
9.2 - - - Definitions, Architectural assumptions - - Docs:=3 -
9.2 S2-2202521 P-CR Approval 23.700-74: Definition and assumption for the group in GMEC study. Huawei, HiSilicon Rel-18 Merged into S2-2203255 Sang-Jun (Samsung) provides comments for clarification.
Qianghua (Huawei) provides r01.
Laurent (Nokia): in order to keep a single thread objects to any version of this TDOC (let's discuss only 2836)
==== Revisions Deadline ====
Qianghua (Huawei) OK for merge with 2836
Sang-Jun (Samsung) proposes to consider it merged to 2836.
==== Comments Deadline ====
Merged
9.2 S2-2202836 P-CR Approval 23.700-74: Adding the group description to the Terms definition. ZTE Rel-18 r04 agreed. Revised to S2-2203255, merging S2-2202521 Laurent (Nokia): Comments (concern on having 5G group definition, better just have a Note: the solutions for this study will describe what kind of group the solution they are targeting)
Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) supports Nokia proposal
Qianghua (Huawei) provides comments and proposes to use 2521 as the basis
Tugce (NTT DOCOMO) provides comments.
zhendong (ZTE) provides the response
zhendong (ZTE) provides r01
Laurent (Nokia): provides r02. objects to R00
Qianghua (Huawei) provides r03 and comments
Laurent (Nokia): provides r04
Qianghua (Huawei) provides r05
==== Revisions Deadline ====
Samsung is fine with r05.
Stefan (Ericsson) can only accept r04, objects to other revisions.
Laurent (Nokia): can only live with r04; objects to any other version
Sang-Jun (Samsung) can live with r04.
==== Comments Deadline ====
Revised
9.2 S2-2203255 P-CR Approval 23.700-74: Adding the group description to the Terms definition. ZTE, Huawei Rel-18 Revision of S2-2202836r04, merging S2-2202521. Approved Approved
9.2 - - - New KIs - - Docs:=2 -
9.2 S2-2202814 P-CR Approval 23.700-74: New Key Issue: Efficient N19 tunnel management for VN group communication. China Mobile, China Southern Power Grid Rel-18 Noted Laurent (Nokia): Objects to any version of this Tdoc that goes beyond the scope of the approved SID
Sang-Jun (Samsung) provides comments for clarification.
Qianghua (Huawei) provides comments and wonders whether this can be a update for KI#4
Laurent (Nokia): Comments. but no need to update KI#4
Yue (China Telecom) propose this KI as an update for KI#4.
Qianghua (Huawei) proposes a way forward, provides r01
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Noted
9.2 S2-2202815 P-CR Approval 23.700-74: New Key Issue: Enhancement on UPF to support diverse terminal access. China Mobile, China Southern Power Grid Rel-18 Noted Laurent (Nokia): Objects to any version of this Tdoc that goes beyond the scope of the approved SID
Sang-Jun (Samsung) provides comments for clarification.
Josep (DT) asks question for clarification.
==== Revisions Deadline ====
Sang-Jun (Samsung) proposes to note the paper.
==== Comments Deadline ====
Noted
9.2 - - - new Sol, rev Sol, rev KI PCRs for KI#1 - - Docs:=13 -
9.2 S2-2201988 P-CR Approval 23.700-74: New solution for KI#1 based on 5G VN group management APIs. Ericsson Rel-18 r01 agreed. Revised to S2-2203256 Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) replies to Sang-Jun
Tugce (NTT DOCOMO) provides comments.
Qianghua (Huawei) provides comments
Stefan (Ericsson) replies to Qianghua
Stefan (Ericsson) replies to Tugce
Qianghua (Huawei) provides r01
Stefan (Ericsson) provides comments
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.2 S2-2203256 P-CR Approval 23.700-74: New solution for KI#1 based on 5G VN group management APIs. Ericsson Rel-18 Revision of S2-2201988r01. Approved Approved
9.2 S2-2201989 P-CR Approval 23.700-74: New solution for KI#1 based on NEF Parameter Provision and Service Parameter services. Ericsson Rel-18 r02 agreed. Revised to S2-2203257 Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) replies to Sang-Jun
Tugce (NTT DOCOMO) provides comments.
Qianghua (Huawei) provides comments.
Stefan (Ericsson) replies to Tugce and Qianghua
Qianghua (Huawei) provides r01
Stefan (Ericsson) replies and provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203257 P-CR Approval 23.700-74: New solution for KI#1 based on NEF Parameter Provision and Service Parameter services. Ericsson Rel-18 Revision of S2-2201989r02. Approved Approved
9.2 S2-2202377 P-CR Approval 23.700-74: Solution on supporting 5G VN group service area with LADN mechanism. China Mobile Rel-18 r01 agreed. Revised to S2-2203258 Dan(China Mobile) provides response
Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) provides questions
Dan (China Mobile) provides r01
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.2 S2-2203258 P-CR Approval 23.700-74: Solution on supporting 5G VN group service area with LADN mechanism China Mobile Rel-18 Revision of S2-2202377r01. Approved Approved
9.2 S2-2202522 P-CR Approval 23.700-74: Split Sol1 and address the related ENs. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203259 Sang-Jun (Samsung) provides comments.
Stefan (Ericsson) provides questions/comments
Qianghua (Huawei) provides r01 and responses
Stefan (Ericsson) provides comments
Qianghua (Huawei) provides responses
Stefan (Ericsson) provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203259 P-CR Approval 23.700-74: Split Sol1 and address the related ENs. Huawei, HiSilicon Rel-18 Revision of S2-2202522r02. Approved Approved
9.2 S2-2202653 P-CR Approval 23.700-74: Solution on support 5G VN service area restriction with SMF service area. China Mobile Rel-18 r01 agreed. Revised to S2-2203260 Dan (China Mobile) provides response.
Sang-Jun (Samsung) provides comments for clarification.
Tugce (NTT DOCOMO) provides comments.
Dan(China Mobile) provides r01 to reflect Tugce (NTT DOCOMO)'s comment
Qianghua (Huawei) comments
Dan (China Mobile) reply
Qianghua (Huawei) replies
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.2 S2-2203260 P-CR Approval 23.700-74: Solution on support 5G VN service area restriction with SMF service area . China Mobile Rel-18 Revision of S2-2202653r01. Approved Approved
9.2 S2-2202961 P-CR Approval 23.700-74: New Solution to Key Issue #1 of FS_GMEC WT#1.1. Nokia, Nokia Shanghai Bell Rel-18 r06 agreed. Revised to S2-2203261 Sang-Jun (Samsung) provides comments for clarification.
Shubhranshu (Nokia) responds
Qianghua (Huawei) provides comments
Tugce (NTT DOCOMO) provides comments.
Stefan (Ericsson) provides questions
Shubhranshu (Nokia) responds and provides r01
Qianghua (Huawei) provides r02
Shubhranshu (Nokia) responds and provides r03
Stefan (Ericsson) provides r04
Sebastian (Qualcomm) provides r05
Qianghua (Huawei) provides r06
Shubhranshu (Nokia) asks for clarification
==== Revisions Deadline ====
Qianghua (Huawei) replies
Sang-Jun (Samsung) is fine with r06.
Sebastian (Qualcomm) is fine with r06 and r05 and objects to other versions
==== Comments Deadline ====
Revised
9.2 S2-2203261 P-CR Approval 23.700-74: New Solution to Key Issue #1 of FS_GMEC WT#1.1. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202961r06. Approved Approved
9.2 S2-2202578 P-CR Approval 23.700-74: Update KI#1 with new solution: Support for attribute of maximum number of users for a 5G VN group. China Telecom Rel-18 Noted Sang-Jun (Samsung) provides comments for clarification.
Haoquan(China Telecom) provides example usages.
Stefan (Ericsson) provides comments
Shubhranshu (Nokia) comments
Stefan (Ericsson) objects to expanding the scope of the KI and thus to this pCR
Qianghua (Huawei) same rules should apply to other PCRs that are expanding the scope, to be fair
==== Revisions Deadline ====
Sang-Jun (Samsung) proposes to note the PCR.
==== Comments Deadline ====
Noted
9.2 - - - new Sol for KI#2 - - Docs:=4 -
9.2 S2-2201990 P-CR Approval 23.700-74: New solution for KI#2 on group status event reporting. Ericsson Rel-18 r02 agreed. Revised to S2-2203262 Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) replies to question and provides r01
Qianghua (Huawei) provides comments
Stefan (Ericsson) replies to Qianghua
Qianghua (Huawei) replies
Stefan (Ericsson) provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203262 P-CR Approval 23.700-74: New solution for KI#2 on group status event reporting. Ericsson Rel-18 Revision of S2-2201990r02. Approved Approved
9.2 S2-2202612 P-CR Approval 23.700-74: New Solution for KI#2: Enhance group status event reporting. NTT DOCOMO Rel-18 r01 agreed. Revised to S2-2203263 Sang-Jun (Samsung) provides comments for clarification.
Tugce (NTT DOCOMO) responds.
Qianghua (Huawei) provides comments
Stefan (Ericsson) provides questions
Tugce (NTT DOCOMO) responds to Qianghua (Huawei).
Qianghua (Huawei) replies and proposes a way forward
Tugce (NTT DOCOMO) agrees to add an EN and provides r01.
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.2 S2-2203263 P-CR Approval 23.700-74: New Solution for KI#2: Enhance group status event reporting. NTT DOCOMO Rel-18 Revision of S2-2202612r01. Approved Approved
9.2 - - - rev Sol for KI#3 - - Docs:=3 -
9.2 S2-2202523 P-CR Approval 23.700-74: Sol2 update to investigate some specific parameters. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203264 Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) provides comments and questions
Qianghua (Huawei) provides r01 and responses
Shubhranshu (Nokia) comments
Qianghua (Huawei) provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203264 P-CR Approval 23.700-74: Sol2 update to investigate some specific parameters. Huawei, HiSilicon Rel-18 Revision of S2-2202523r02. Approved Approved
9.2 S2-2202614 P-CR Approval 23.700-74: Revision of Solution #2 NEF service for connection management for a group for KI#3. Samsung Rel-18 Postponed Shubhranshu (Nokia) comments
==== Revisions Deadline ====
Sang-Jun (Samsung) accepts Shubhranshu (Nokia) proposal to postpone the PCR so that tne EN will be clarified during next meeting.
==== Comments Deadline ====
Postponed
9.2 - - - new Sol, rev Sol, rev KI for KI#4 - - Docs:=12 -
9.2 S2-2201991 P-CR Approval 23.700-74: New solution for KI#4 to support multiple SMFs per 5G VN. Ericsson Rel-18 r03 + changes agreed. Revised to S2-2203265 Sang-Jun (Samsung) provides comments for clarification.
Stefan (Ericsson) provides replies and r01
Qianghua (Huawei) provides comments
Laurent (Nokia): provides r02
Stefan (Ericsson) replies to Qianghua
Qianghua (Huawei) provides r03
Stefan (Ericsson) provides r04
Qianghua (Huawei) comments
==== Revisions Deadline ====
Qianghua (Huawei) objects to r00, r01, r02, r04. OK with r03
Sang-Jun (Samsung) proposes to go with r03 and continue discussions next meeting.
Laurent (Nokia): Proposes to go with R04 which is a good compromise.
==== Comments Deadline ====
Revised
9.2 S2-2203265 P-CR Approval 23.700-74: New solution for KI#4 to support multiple SMFs per 5G VN. Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2201991r03 + changes. Approved Approved
9.2 S2-2202174 P-CR Approval 23.700-74: Solution #3 update. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203266 Sang-Jun (Samsung) provides comments for clarification.
Qianghua (Huawei) provides comments.
Laurent (Nokia): provides r01
Qianghua (Huawei) provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203266 P-CR Approval 23.700-74: Solution #3 update. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202174r02. Approved Approved
9.2 S2-2202524 P-CR Approval 23.700-74: Update Solution 5 to complete the procedure. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203267 Sang-Jun (Samsung) provides comments for clarification.
Laurent (Nokia): Comments
Stefan (Ericsson) provides comments
Qianghua (Huawei) provides r01 and responses
Laurent (Nokia): provides r02 and objects to any previous version
Qianghua (Huawei) provides r03
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r03.
==== Comments Deadline ====
Revised
9.2 S2-2203267 P-CR Approval 23.700-74: Update Solution 5 to complete the procedure. Huawei, HiSilicon Rel-18 Revision of S2-2202524r03. Approved Approved
9.2 S2-2202611 P-CR Approval 23.700-74: Revision of Solution #5 Multiple SMFs involved 5G VN group communication for KI#4. Samsung Rel-18 r04 agreed. Revised to S2-2203268 Laurent (Nokia): Comments
Stefan (Ericsson) provides comments
Sang-Jun (Samsung) provides r01.
Laurent (Nokia): provides r02. Objects to any previous version (un clear)
Stefan (Ericsson) provides r03
Sang-Jun (Samsung) provides r04.
Stefan (Ericsson) prefers r00/r03/r04
Qianghua (Huawei) prefers r00/r03/r04
==== Revisions Deadline ====
Sang-Jun (Samsung) prefers r04.
Laurent (Nokia): (repats) objects to R00+R01
==== Comments Deadline ====
Revised
9.2 S2-2203268 P-CR Approval 23.700-74: Revision of Solution #5 Multiple SMFs involved 5G VN group communication for KI#4. Samsung Rel-18 Revision of S2-2202611r04. Approved Approved
9.2 S2-2202837 P-CR Approval 23.700-74: KI#4, update to the sol#4 Multiple SMFs for VN group communication. ZTE Rel-18 r02 agreed. Revised to S2-2203269 Sang-Jun (Samsung) provides comments for clarification.
Laurent (Nokia): Comments
Stefan (Ericsson) comments
Laurent (Nokia): provides r01 and objects to any previous version
zhendong (ZTE) provides the response
zhendong (ZTE) propvides response
zhendong (ZTE) provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.2 S2-2203269 P-CR Approval 23.700-74: KI#4, update to the sol#4 Multiple SMFs for VN group communication. ZTE Rel-18 Revision of S2-2202837r02. Approved Approved
9.2 S2-2202817 P-CR Approval 23.700-74: Update to Key Issue#4 on session management efficiency of multiple SMFs. China Mobile Com. Corporation, China Southern Power Grid Rel-18 r01 agreed. Revised to S2-2203270 Sang-Jun (Samsung) provides comments for clarification.
Laurent (Nokia): I don't think we need this update of KI#4
Qianghua (Huawei) provides r01
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.2 S2-2203270 P-CR Approval 23.700-74: Update to Key Issue#4 on session management efficiency of multiple SMFs. China Mobile Com. Corporation, China Southern Power Grid Rel-18 Revision of S2-2202817r01. Approved Approved
9.2 - - - new Sol, rev Sol, rev KI for KI#5 - - Docs:=6 -
9.2 S2-2202175 P-CR Approval 23.700-74: Solution #6 update. Nokia, Nokia Shanghai Bell Rel-18 Approved Sang-Jun (Samsung) provides comments for clarification.
Laurent (Nokia): answers
Sang-Jun (Samsung) provides comments.
==== Revisions Deadline ====
Sang-Jun (Samsung) thanks to Laurent (Nokia) for answers and agrees to approve r00.
==== Comments Deadline ====
Approved
9.2 S2-2202525 P-CR Approval 23.700-74: New solution to address key issue 5. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203271 Sang-Jun (Samsung) provides comments for clarification.
Laurent (Nokia): Comments
Qianghua (Huawei) provides r01 and responses
Stefan (Ericsson) provides comments
Laurent (Nokia): provides r02 and objects to any previous version
Qianghua (Huawei) provides r03
==== Revisions Deadline ====
Sang-Jun (Samsung) supports r03.
==== Comments Deadline ====
Revised
9.2 S2-2203271 P-CR Approval 23.700-74: New solution to address key issue 5. Huawei, HiSilicon Rel-18 Revision of S2-2202525r03. Approved Approved
9.2 S2-2202609 P-CR Approval 23.700-74: Revision of Solution #7 a PDU Session with multiple groups for KI#5. Samsung Rel-18 r05 agreed. Revised to S2-2203272 Laurent (Nokia): requests to have Mandatory clarifications added
Sang-Jun (Samsung) responses to Laurent (Nokia) and and provides r01.
Qianghua (Huawei) provides comments
Sang-Jun (Samsung) repies to Qianghua (Huawei).
Stefan (Ericsson) provides comments and questions
Sang-Jun (Samsung) replies to Stefan (Ericsson).
Laurent (Nokia): provides r02, OBJECTS to any previous version
Sang-Jun (Samsung) provides r03 on top of r02.
Qianghua (Huawei) provides r04
Stefan (Ericsson) provides r05
==== Revisions Deadline ====
Sang-Jun (Samsung) accepts r05.
==== Comments Deadline ====
Revised
9.2 S2-2203272 P-CR Approval 23.700-74: Revision of Solution #7 a PDU Session with multiple groups for KI#5. Samsung Rel-18 Revision of S2-2202609r05. Approved Approved
9.2 S2-2202818 P-CR Approval 23.700-74: Update to Key Issue#5. China Mobile Com. Corporation, China Southern Power Grid Rel-18 This was postponed. Sang-Jun (Samsung) provides comments for clarification.
Qianghua (Huawei) supports the updates
==== Revisions Deadline ====
Yi (CMCC) provides r01 in the GMEC draft folder for your information.
Qianghua (Huawei) OK with either r00 or r01
Sang-Jun (Samsung) is fine with r01, and asks to add Samsung as co-signer.
==== Comments Deadline ====
Postponed
9.3 - - - Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) - - Docs:=30 -
9.3 - - - Solutions for KI#2 - - Docs:=10 -
9.3 S2-2202728 P-CR Approval 23.700-53: New Solution to KI#2: Re-ordering Modes and Features. Deutsche Telekom AG Rel-18 Noted Apostolis (Lenovo) asks questions for clarification.
Markus (Deutsche Telekom) reply
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.3 S2-2202734 P-CR Approval 23.700-53: Update of Solution 3 MP-DCCP-LL based ATSSS steering functionality Deutsche Telekom AG Rel-18 r03 agreed. Revised to S2-2203066 Apostolis (Lenovo) suggests changes.
Dieter (Deutsche Telekom) provides r01 addressing comments from Apostolis..
Dario (Qualcomm) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203066 P-CR Approval 23.700-53: Update of Solution 3 MP-DCCP-LL based ATSSS steering functionality . Deutsche Telekom AG Rel-18 Revision of S2-2202734r03. Approved Approved
9.3 S2-2202742 P-CR Approval 23.700-53: Solution #X: MPQUIC steering functionality using UDP proxying over HTTP Lenovo, Motorola Mobility, ZTE, Broadcom, Ericsson, LGE, Nokia, Nokia Shanghai Bell, Charter Communications Rel-18 r03 agreed. Revised to S2-2203067 Dieter (Deutsche Telekom) asks questions, comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203067 P-CR Approval 23.700-53: Solution #X: MPQUIC steering functionality using UDP proxying over HTTP. Lenovo, Motorola Mobility, ZTE, Broadcom, Ericsson, LGE, Nokia, Nokia Shanghai Bell, Charter Communications, Apple Rel-18 Revision of S2-2202742r03. Approved Approved
9.3 S2-2202745 P-CR Approval 23.700-53: Solution #X: MPQUIC steering functionality using IP proxying over HTTP Lenovo, Motorola Mobility, Broadcom Rel-18 r02 agreed. Revised to S2-2203068 Dieter (Deutsche Telekom) asks questions, comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203068 P-CR Approval 23.700-53: Solution #X: MPQUIC steering functionality using IP proxying over HTTP. Lenovo, Motorola Mobility, Broadcom Rel-18 Revision of S2-2202745r02. Approved Approved
9.3 S2-2202863 DISCUSSION Agreement Discussion on Key Issue #2: Per-Packet Overhead of QUIC/DCCP-based Steering Functionalities. InterDigital Inc. Rel-18 Noted Noted
9.3 S2-2202866 P-CR Approval 23.700-53: New Solution: Limiting MA-PDU Per-Packet Overhead. InterDigital Inc. Rel-18 r03 agreed. Revised to S2-2203069 Apostolis (Lenovo) provides comments and questions.
Guanzhou (InterDigital) responds to Apostolis' comments and provides r01.
Dario (Qualcomm) comments and asks questions.
Guanzhou (InterDigital) responds to Dario's comments and provides r02.
Rainer (Nokia) comments.
Guanzhou (InterDigital) provides r03.
Rainer (Nokia) is ok with r03.
==== Revisions Deadline ====
Dario (Qualcomm) is OK with r03 but points out inconsistency to be solved at the next meeting.
Apostolis (Lenovo) is also fine with r03.
==== Comments Deadline ====
Revised
9.3 S2-2203069 P-CR Approval 23.700-53: New Solution: Limiting MA-PDU Per-Packet Overhead. InterDigital Inc. Rel-18 Revision of S2-2202866r03. Approved Approved
9.3 - - - Solutions for KI#3 - - Docs:=10 -
9.3 S2-2202134 P-CR Approval 23.700-53: New solution on redundant traffic steering triggered by AF. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203070 Rainer (Nokia) replies.
Yishan (Huawei) answers to Rainer (Nokia).
Rainer (Nokia) asks for clarification.
Dario (Qualcomm) comments.
Yishan (Huawei) answers to Dario (Qualcomm).
Apostolis (Lenovo) comments.
Yishan (Huawei) answers to Apostolis (Lenovo) and provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203070 P-CR Approval 23.700-53: New solution on redundant traffic steering triggered by AF. Huawei, HiSilicon Rel-18 Revision of S2-2202134r02. Approved Approved
9.3 S2-2202551 P-CR Approval 23.700-53: Update solution for redundancy steering mode. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203071 Guanzhou (InterDigital) has concerns on removing the EN.
Rainer (Nokia) comments.
Myungjune (LGE) comments.
Susan (Huawei) replies and provides r01.
Dario (Qualcomm) comments.
Susan (Huawei) replies and provides r02.
Stefan (Ericsson) provides r03
Susan (Huawei) is ok with r03.
==== Revisions Deadline ====
Dario (Qualcomm) is OK with r03.
Guanzhou (InterDigital) is OK with r03.
Rainer (Nokia) is also ok with r03.
==== Comments Deadline ====
Revised
9.3 S2-2203071 P-CR Approval 23.700-53: Update solution for redundancy steering mode. Huawei, HiSilicon Rel-18 Revision of S2-2202551r03. Approved Approved
9.3 S2-2202583 P-CR Approval 23.700-53: Solution for support of redundant traffic steering. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203072 Guanzhou (InterDigital) comments and asks for clarification.
Rainer (Nokia) replies to Guanzhou (InterDigital).
Susan (Huawei) provides comments.
Myungjune (LGE) provides comments.
Rainer (Nokia) replies.
Rainer (Nokia) replies to Susan (Huawei).
Stefan (Ericsson) provides questions
Dario (Qualcomm) comments and asks questions
Guanzhou (InterDigital) comments and provides r01.
Rainer (Nokia) is ok with r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203072 P-CR Approval 23.700-53: Solution for support of redundant traffic steering. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202583r03. Approved Approved
9.3 S2-2202862 P-CR Approval 23.700-53: Solutions for KI#3 Redundant Traffic Steering Mode. InterDigital Inc. Rel-18 r02 agreed. Revised to S2-2203073 Rainer (Nokia) asks for clarification.
Guanzhou (InterDigital) responds to Rainer and provides r01.
Stefan (Ericsson) comments
Rainer (Nokia) is ok to add the EN.
Guanzhou (InterDigital) provides r02.
Dario (Qualcomm) comments and asks questions.
Guanzhou (InterDigital) responds to Dario's comments.
==== Revisions Deadline ====
Dario (Qualcomm) replies to Guanzhou.
==== Comments Deadline ====
Revised
9.3 S2-2203073 P-CR Approval 23.700-53: Solutions for KI#3 Redundant Traffic Steering Mode. InterDigital Inc. Rel-18 Revision of S2-2202862r02. Approved Approved
9.3 S2-2202965 P-CR Approval 23.700-53: KI#3: Solution for redundant steering mode with duplication information and trigger mechanisms. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2203074 Stefan (Ericsson) provides questions
Guanzhou (InterDigital) comments.
Susan (Huawei) provides comments.
Myungjune (LGE) provides comments.
Rainer (Nokia) comments.
Dario (Qualcomm) replies and provides r01.
Rainer (Nokia) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203074 P-CR Approval 23.700-53: KI#3: Solution for redundant steering mode with duplication information and trigger mechanisms. Qualcomm Incorporated Rel-18 Revision of S2-2202965r01. Approved Approved
9.3 - - - Solutions for KI#5 - - Docs:=8 -
9.3 S2-2202133 P-CR Approval 23.700-53: Solution for supporting traffic switching between two N3GPP paths. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203075 Stefan (Ericsson) provides comments and questions
Yishan (Huawei) answers to Stefan (Ericsson).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203075 P-CR Approval 23.700-53: Solution for supporting traffic switching between two N3GPP paths. Huawei, HiSilicon Rel-18 Revision of S2-2202133r02. Approved Approved
9.3 S2-2202275 P-CR Approval 23.700-53: KI #5, New Sol: Delaying UDM Registration until non-3GPP access switching completes. LG Electronics Rel-18 r02 agreed. Revised to S2-2203076 Marco (huawei) asks questions
Myungjune (LGE) responds to Marco (Huawei)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203076 P-CR Approval 23.700-53: KI #5, New Sol: Delaying UDM Registration until non-3GPP access switching completes. LG Electronics Rel-18 Revision of S2-2202275r02. Approved Approved
9.3 S2-2202948 P-CR Approval 23.700-53: Solution #X: KI#5 - Path switching between Non-3GPP accesses. Charter Communications, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, CableLabs, Apple, Comcast Rel-18 r01 agreed. Revised to S2-2203077 DongYeon (Samsung) comments, and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203077 P-CR Approval 23.700-53: Solution #X: KI#5 - Path switching between Non-3GPP accesses. Charter Communications, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, CableLabs, Apple, Comcast Rel-18 Revision of S2-2202948r01. Approved Approved
9.3 S2-2202807 P-CR Approval 23.700-53: Solution for KI#5 Switching traffic of an MA PDU Session between two non-3GPP access paths. Samsung Rel-18 r03 agreed. Revised to S2-2203078 Marco (Huawei) provides comments and questions.
Myungjune (LGE) comments.
Rainer (Nokia) comments.
DongYeon (Samsung) replies to Marco (Huawei) and Myungjune (LGE), and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203078 P-CR Approval 23.700-53: Solution for KI#5 Switching traffic of an MA PDU Session between two non-3GPP access paths. Samsung Rel-18 Revision of S2-2202807r03. Approved Approved
9.3 - - - Solutions for KI#6 - - Docs:=2 -
9.3 S2-2202552 P-CR Approval 23.700-53: Update solution for Multi-access between EPC and 5GC. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203079 Stefan (Ericsson) provides comments and questions
Myungjune (LGE) comments
Myungjune (LGE) replies to Susan (Huawei)
Susan (Huawei) replies to Stefan (Ericsson) and Myungjune (LGE), and provides r01.
Stefan (Ericsson) comments
Susan (Huawei) replies.
Susan (Huawei) provides r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.3 S2-2203079 P-CR Approval 23.700-53: Update solution for Multi-access between EPC and 5GC . Huawei, HiSilicon Rel-18 Revision of S2-2202552r03. Approved Approved
9.4 - - - Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) - - Docs:=68 -
9.4 - - - General - - Docs:=4 -
9.4 S2-2202581 LS OUT Approval [DRAFT] LS on eNPN Control Plane remote provisioning Lenovo, Motorola Mobility, Samsung Rel-18 Noted Saso (Intel) seeks clarification on the SA2's commitment.
Rainer (Nokia) objects to the LS.
Genadi (Lenovo) replies to Saso (Intel) and Rainer (Nokia).
Rainer (Nokia) replies.
Peter Hedman (Ericsson) provides comments and suggestion for way forward.
Qianghua (Huawei) agrees views from Kisuk, and can accept the outgoing LS
Haris(Qualcomm) objects to the LS
Genadi (Lenovo) replies to Josep (DT) and Rainer (Nokia).
Kisuk (Samsung) comments
Josep (DT) agrees with Saso's (Intel) and Rainer's (Nokia) view.
Fei (OPPO) comments.
Kisuk (Samsung) provides comment.
Walter Dees (Philips) supports sending the LS.
Huan (vivo) agrees to send out the LS
Kisuk (Samsung) agrees to send out the LS
Saso (Intel) asking for revision.
Haris(Qualcomm) objects to the LS again
==== Revisions Deadline ====
Genadi (Lenovo) requests to capture in the minutes the following statement as proposed by the rapporteur 'The reason why CP provisioning could not be part of Rel-17 was that SA3 could not agree on the security functionality. It is up to SA3 whether and how to progress CP provisioning in Rel-18.'
==== Comments Deadline ====
Noted
9.4 S2-2202166 P-CR Approval 23.700-08: Terminology and definition for localized service. Ericsson Rel-18 r03 agreed. Revised to S2-2203442 Jianning (Xiaomi) provides comment
Walter Dees (Philips) provides comment.
Antoine (Orange) provides r01.
Miguel (Qualcomm) provides r02
Walter (Philips) comments that r02 is empty
Peter Hedman (Ericsson) ok with r01 while r02 is empty?
Miguel (Qualcomm) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203442 P-CR Approval 23.700-08: Terminology and definition for localized service. Ericsson Rel-18 Revision of S2-2202166r03. Approved Approved
9.4 S2-2202888 P-CR Approval 23.700-08: FS_eNPN_Ph2: architecture assumption. Xiaomi Rel-18 Noted Pallab (Nokia) comments and questions the need for the pCR
Josep (DT) objects to r00.
Jianning (Xiaomi) response to Peter (Ericsson)
Peter Hedman (Ericsson) provides comments and wonder if S2-2202642 is enough?
Jianning (Xiaomi) replies to Josep (DT) and Pallab (Nokia)
Antoine (Orange): The proposed addition is not readable and not needed.
Marco (Huawei) share others view that it is not required
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.4 - - - New Key issues - - Docs:=3 -
9.4 S2-2202496 P-CR Approval 23.700-08: Key issue #2: Support of Non-3GPP access for SNPN. Lenovo, Motorola Mobility, Broadcom, Charter Communications, CableLabs, Intel, Ericsson, Nokia, Nokia Shanghai Bell Rel-18 r07 agreed. Revised to S2-2203443 Marco (Huawei) comments and provide r01
Josep (DT) is fine with how the note in r03 reads.
Genadi (Lenovo) provides r03.
Peter Hedman (Ericsson) provides question
Josep (DT) objects to r01. Provides r02
Marco (Huawei) provide r03 with change in Note 1.
Antoine (Orange) provides r05.
Marco (Huawei) provide r06.
Josep (DT) disagrees with the addition in r06.
Antoine (Orange) provide r07.
==== Revisions Deadline ====
Josep (DT) is OK with r07, objects to r06, r04, r01, r00.
Rainer (Nokia) is ok with r07.
Genadi (Lenovo) can live with r07.
Peter Hedman (Ericsson) ok with r07
Marco (Huawei) for progressing we can accept r07
Yi (China Mobile) provides r08 after revision deadline based on discussions on S2-2202813.
==== Comments Deadline ====
Haris(Qualcomm) that r08 is not acceptable without additional explanation
Yi (China Mobile) replies to Haris.
Peter Hedman (Ericsson) provides comments
Saso (Intel) agrees with the Rapporter's proposal for adding a NOTE (but not extending the KI scope); provides comments
Yi (China Mobile) replies.
Saso (Intel) replies to Yi.
Yi (China Mobile) replies to Saso.
Revised
9.4 S2-2203443 P-CR Approval 23.700-08: Key issue #2: Support of Non-3GPP access for SNPN. Lenovo, Motorola Mobility, Broadcom, Charter Communications, CableLabs, Intel, Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202496r07. Approved Approved
9.4 S2-2202813 P-CR Approval 23.700-08: KI for simultaneous access to multiple NPNs and services. China Mobile Rel-18 Noted Saso (Intel) comments that the proposed KI is not in the SID scope and proposes to NOTE the document.
Josep (DT) also proposes to NOTE this document.
Genadi (Lenovo) provides comments and linkage to the r03 of S2-2202496.
Peter Hedman (Ericsson) provides comments
Haris(Qualcomm) objects to the pCR
Josep (DT) comments that this new, unrelated KI wold require a re-evaluation & agreement of the TUs stated in the SID (new WT).
Yi (China Mobile) responds.
Antoine (Orange) asks clarification on Yi's proposal.
==== Revisions Deadline ====
Yi (China Mobile) confirms Antoine's understanding is correct.
Josep (DT) is OK to add a NOTE to 2496 but has to object to this pCR (new KI).
Peter Hedman (Ericsson) provides question
Yi (China Mobile) propose to try to add note to 2496 at CC this meeting.
Genadi (Lenovo) proposes slight re-wording to the NOTE to 2496.
Yi (China Mobile) is fine with the rewording.
==== Comments Deadline ====
Haris(Qualcomm) comments
Yi (China Mobile) replies to Haris.
Noted
9.4 - - - Update of Key issues - - Docs:=6 -
9.4 S2-2202642 P-CR Approval 23.700-08: KI#3 updates. Ericsson Rel-18 r02 agreed. Revised to S2-2203444 Marco (Huawei) provides r01
Peter Hedman (Ericsson) provides comments, ok with r02
Josep (DT) comments, provides r02.
marco (Huawei) ok with r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203444 P-CR Approval 23.700-08: KI#3 updates. Ericsson Rel-18 Revision of S2-2202642r02. Approved Approved
9.4 S2-2202643 P-CR Approval 23.700-08: KI#4: adding key issue description. Ericsson, InterDigital, Futurewei, Vivo Rel-18 r06 agreed. Revised to S2-2203445 Yishan (Huawei) provides r01
Josep (DT) finds that the changes in r01 make the text less clear.
Yishan (Huawei) answers to Josep (DT)
Josep (DT) replies to Yishan (Huawei).
Peter Hedman (Ericsson) provides comments and a question
Josep (DT) answers to Yishan (Huawei), provides r02.
Walter Dees (Philips) provides comments and revision r03
Antoine (Orange) objects to r03, OK with r02.
Walter Dees (Philips) comments to Antoine (Orange).
Josep (DT) find the changes in r03 unclear.
Miguel (Qualcomm) provides r04
Walter Dees (Philips) can live with r02.
Peter Hedman (Ericsson) provides r05 on changing the note (but not yet checked what r04 changed)
Walter (Philips) provides r06 given that r05 did not include the requested changes by Peter (Ericsson)
==== Revisions Deadline ====
Josep (DT) in Ok with the change in the note in r06.
Peter Hedman (Ericsson) ok with r06
Yishan (Huawei) is ok with r06 and objects to r03
Guanzhou (InterDigital) is OK to r06 AND objects r03.
Ashok (Samsung) comments
Antoine (Orange) is fine with the clarification that Ashok proposes to add.
==== Comments Deadline ====
Josep (DT) asks for clarification.
Ashok (Samsung) is fine Josep (DT)'s suggestion.
Revised
9.4 S2-2203445 P-CR Approval 23.700-08: KI#4: adding key issue description . Ericsson, InterDigital, Futurewei, Vivo Rel-18 Revision of S2-2202643r06. Approved Approved
9.4 S2-2202679 P-CR Approval 23.700-08: FS_eNPN_Ph2 Update of Key Issue #6. Vivo Rel-18 r02 agreed. Revised to S2-2203446 Josep (DT) comments, provides r01.
Peter Hedman (Ericsson) provides r02
Huan (vivo) is OK to r02
==== Revisions Deadline ====
Josep (DT) is also OK with r02.
==== Comments Deadline ====
Revised
9.4 S2-2203446 P-CR Approval 23.700-08: FS_eNPN_Ph2 Update of Key Issue #6. Vivo Rel-18 Revision of S2-2202679r02. Approved Approved
9.4 - - - Update of solutions - - Docs:=6 -
9.4 - - - For KI#1 - - Docs:=4 -
9.4 S2-2202162 P-CR Approval 23.700-08: Solution Equivalent SNPN solution#1 update. Ericsson Rel-18 r02 agreed. Revised to S2-2203447 Jihoon (ETRI) asks questions.
Peter Hedman (Ericsson) provides reply
Jihoon (ETRI) replies to Peter (Ericsson) with r01.
Jihoon (ETRI) thanks Peter (Ericsson), and provides r02 with a minor correction.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r02
==== Comments Deadline ====
Revised
9.4 S2-2203447 P-CR Approval 23.700-08: Solution Equivalent SNPN solution#1 update. Ericsson, ETRI Rel-18 Revision of S2-2202162r02. Approved Approved
9.4 S2-2202582 P-CR Approval 23.700-08: Enhancements to Solution #1 Enable efficient mobility via equivalent SNPNs. Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2203448 Rainer (Nokia) replies.
Guanzhou (InterDigital) asks a question.
Guanzhou (InterDigital) responds to Rainer.
Rainer (Nokia) replies to Guanzhou (InterDigital).
Fei (OPPO) comments.
Guanzhou (InterDigital) comments and provides r01.
Rainer (Nokia) provides r02.
Peter Hedman (Ericsson) provides r03
Rainer (Nokia) is ok with r03.
Fei (OPPO) comments on the order.
Fei (OPPO) provides r04
Rainer (Nokia) provides r05.
Guanzhou (InterDigital) replies to Fei (Oppo)'s comment.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r05
Fei (OPPO) is ok with r05.
Guanzhou (InterDigital) is OK with r05.
==== Comments Deadline ====
Revised
9.4 S2-2203448 P-CR Approval 23.700-08: Enhancements to Solution #1 Enable efficient mobility via equivalent SNPNs. Nokia, Nokia Shanghai Bell, InterDigital, Ericsson, OPPO Rel-18 Revision of S2-2202582r05. Approved Approved
9.4 - - - For KI#2 - - Docs:=4 -
9.4 S2-2202935 P-CR Approval 23.700-08: Sol#3 update: Removal of Editor's notes. Intel Rel-18 r03 agreed. Revised to S2-2203449 Genadi (Lenovo) provides r01.
Myungjune (LGE) provides comments.
Saso (Intel) is OK with r01.
Peter Hedman (Ericsson) provides r02
Myungjune (LGE) is ok with r02
Huan (vivo) provides r03
Saso (Intel) is OK with r03.
Genadi (Lenovo) is fine with r03.
Peter Hedman (Ericsson) provides reminder on not using shall in TR
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r03
Rainer (Nokia) is ok with r03.
==== Comments Deadline ====
Revised
9.4 S2-2203449 P-CR Approval 23.700-08: Sol#3 update: Removal of Editor's notes. Intel, Lenovo, Motorola Mobility, Ericsson, vivo Rel-18 Revision of S2-2202935r03. Approved Approved
9.4 S2-2202936 P-CR Approval 23.700-08: Sol#2 update: Removal of Editor's notes. Intel Rel-18 r05 agreed. Revised to S2-2203450 Ashok (Samsung) comments and provides r01
Huan (vivo) comments
Saso (Intel) does not agree r01.
Ashok (Samsung) does not agree with r00 and don't see anything technical wrong in r01.
Peter Hedman (Ericsson) provides r02 an comments
Ashok (Samsung) is fine with r02
Saso (Intel) provides r03
Ashok (Samsung) provides r04
Saso (Intel) comments that r04 does not read well.
Ashok (Samsung) comments and request for a revision
Saso (Intel) provides r05.
Yishan (Huawei) questions
Marco (Huawei) replies to Saso (Intel).
Saso (Intel) replies to Yishan.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r05
Yishan (Huawei) can live with r05, but with the intention to clarify the assumption of solution on PVS access in next meeting
Saso (Intel) replies to Yishan that it is OK to clarify the assumption of solution on PVS access in next meeting.
Ashok (Samsung) is Ok with r05
==== Comments Deadline ====
Revised
9.4 S2-2203450 P-CR Approval 23.700-08: Sol#2 update: Removal of Editor's notes. Intel, Ericsson Rel-18 Revision of S2-2202936r05. Approved Approved
9.4 - - - New solutions - - Docs:=3 -
9.4 - - - New solutions for KI#1 - - Docs:=1 -
9.4 S2-2202257 P-CR Approval 23.700-08: Solution (WT#1): Support service continuity between equivalent SNPNs. NEC Rel-18 Noted Huan (vivo) asks for clarifications
Peter Hedman (Ericsson) provides comments
Rainer (Nokia) comments.
Hiroshi (NEC) provides r1
Josep (DT) objects to this solution. Also comments that 'r1' file should be disregarded, should be 'r01'.
Antoine (Orange) objects to r00 and r01 because this solution is not in the scope of KI#1.
==== Revisions Deadline ====
Hiroshi Dempo (NEC) replies to Peter's comments
Hiroshi (NEC) replied to Josep
Hiroshi (NEC) replied to Antoine
==== Comments Deadline ====
Noted
9.4 - - - New solutions for KI#2 - - Docs:=9 -
9.4 S2-2202009 P-CR Approval 23.700-08: Solution for access to SNPN with NG-RAN and to WLAN Access Network using the same credentials. Qualcomm Incorporated Rel-18 Revision of (Noted) S2-2201193 from S2#149E. r07 agreed. Revised to S2-2203451 Josep (DT) comments, proposes r02.
Marco (Huawei) comments and merge 2146 with r01 . Resend with correct subject
Marco (Huawei) proposes r03 merging the part from 2146.
Haris(Qualcomm) comments and provides r04
Saso (Intel) comments that Huawei's solution (2156) is on the 'Not handled' list and should not be merged on 2009, all the more so that it goes against the spirit of 2009.
Marco (Huawei ) rapporteur in its suggestion proposed to merge 'Seems to cover S2-2202156?'. I disagree that is in different sprit
Saso (Intel) provides r05, removing content from 2156; objects to r04.
Marco (Huawei) object to r05.
Rainer (Nokia) comments.
Genadi (Lenovo) provides r06 with an EN about the role of the CH.
Saso (Intel) replies to Rainer and Genadi.
Rainer (Nokia) provides r07.
Saso (Intel) replies to Marco.
==== Revisions Deadline ====
Josep (DT) objects to r00, r01, r03, r04.
Haris(Qualcomm) is ok with r07
Marco (Huawei) we can accept r06 and r07 with the understanding that the similar solution in 2156 will be handled in next meeting.
Peter Hedman (Ericsson) ok with r07 and provides clarifications
==== Comments Deadline ====
Revised
9.4 S2-2203451 P-CR Approval 23.700-08: Solution for access to SNPN with NG-RAN and to WLAN Access Network using the same credentials. Qualcomm Incorporated Rel-18 Revision of S2-2202009r07. Approved Approved
9.4 S2-2202010 P-CR Approval 23.700-08: Solution for using ePDG for access to SNPN over non-3GPP access. Qualcomm Incorporated Rel-18 Noted Josep (DT) questions whether adding SNPN support to EPC is in scope of this SID.
Rainer (Nokia) agrees with Josep (DT).
Guanzhou (InterDigital) shares similar concern on assuming ePDG in SNPN.
Haris(Qualcomm) comments
Josep (DT) comments, disagrees with Haris (Qualcomm).
Haris(Qualcomm) replies
Marco (Huawei) shares the concern of DT & Nokia
==== Revisions Deadline ====
Josep (DT) objects to this pCR.
==== Comments Deadline ====
Noted
9.4 S2-2202135 P-CR Approval 23.700-08: Solution on support of onboarding over untrusted non-3GPP access in SNPN. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203452 Saso (Intel) questions the need for support of UE onboarding in the Untrusted non-3GPP access architecture.
Rainer (Nokia) replies.
Josep (DT) asks a question for clarification. Questions whether the solution as proposed fits any of the KIs
Yishan (Huawei) replies.
Josep (DT) comments that the default credentials have nothing to do with the SNPN, rather with the DCS.
Guanzhou (InterDigital) thinks this is not related to KI#2 or in SID scope.
Haris(Qualcomm) comments
Rainer (Nokia) comments.
Saso (Intel) replying to Yishan. Proposes to NOTE the document.
Marco (Huawei) answers to comments and disagree with Saso (intel).
Saso (Intel) replies to Marco.
Marco (Huawei) answer to Saso (Intel)
Saso (Intel) answer to Marco
Haris(Qualcomm) provides r01
==== Revisions Deadline ====
Saso (Intel) is OK with the additions in r01
Yishan (Huawei) is OK with r01
==== Comments Deadline ====
Revised
9.4 S2-2203452 P-CR Approval 23.700-08: Solution on support of onboarding over untrusted non-3GPP access in SNPN. Huawei, HiSilicon Rel-18 Revision of S2-2202135r01. Approved Approved
9.4 S2-2202137 P-CR Approval 23.700-08: New solution on support of Credentials Holder scenarios over untrusted non-3GPP access in SNPN. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2203453 Haris(Qualcomm) comments
Josep (DT) comments on SNPN ID in FQDN. I am also not aware of a SNPN N3IWF FQDN in the specs.
Rainer (Nokia) asks for clarification.
Yishan (Huawei) provides r01.
Josep (DT) asks question for clarification.
Saso (Intel) comments
Yishan (Huawei) answers and provides r02
Rainer (Nokia) replies.
Yishan (Huawei) replies to Rainer (Nokia)
Yishan (Huawei) replies.
Yishan (Huawei) updates r03
Haris(Qualcomm) provides r04
==== Revisions Deadline ====
Yishan (Huawei) is ok for r04
==== Comments Deadline ====
Revised
9.4 S2-2203453 P-CR Approval 23.700-08: New solution on support of Credentials Holder scenarios over untrusted non-3GPP access in SNPN. Huawei, HiSilicon Rel-18 Revision of S2-2202137r04. Approved Approved
9.4 S2-2202258 P-CR Approval 23.700-08: Solution for access to SNPN services via wireline access network. CableLabs, Charter Rel-18 Approved Approved
9.4 S2-2202528 P-CR Approval 23.700-08: New solution for enabling the SNPN to identify non-3GPP access type. Huawei, HiSilicon Rel-18 Noted Genadi (Lenovo) provides r01.
Saso (Intel) seeks clarification on the justification.
Rainer (Nokia) comments.
Josep (DT) comments, agrees with Rainer (Nokia).
Qianghua (Huawei) replies and provides r02
Saso (Intel) replies to Qianghua
==== Revisions Deadline ====
Qianghua (Huawei) proposes to go with r02 + EN from Saso: Editor's note: The motivation for the SNPN 5GC to be able to discriminate between 'untrusted access via WLAN' vs 'untrusted access via PLMN' is FFS and needs to be described. Can confirm this at next CC.
Josep (DT) objects to this pCR.
==== Comments Deadline ====
Noted
9.4 - - - New solutions for KI#3-6 - - Docs:=21 -
9.4 S2-2202163 P-CR Approval 23.700-08: Solution High level flow for localized service support. Ericsson Rel-18 r02 agreed. Revised to S2-2203454 Josep (DT) comments that this 'solution' is rather architectural requirements/assumptions.
Saso (Intel) supports the proposal and thinks it is a good idea to have an 'umbrella' solution that presumably can serve as a common framework for other solutions.
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
Jianning (Xiaomi) provides comment
Josep (DT) comments, objects to r00.
Peter Hedman (Ericsson) provides reply
==== Comments Deadline ====
Revised
9.4 S2-2203454 P-CR Approval 23.700-08: Solution High level flow for localized service support. Ericsson Rel-18 Revision of S2-2202163r02. Approved Approved
9.4 S2-2202167 P-CR Approval 23.700-08: Return to home network. Ericsson Rel-18 r02 agreed. Revised to S2-2203455 Josep (DT) comments, provides r01 with ENs.
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203455 P-CR Approval 23.700-08: Return to home network. Ericsson Rel-18 Revision of S2-2202167r02. Approved Approved
9.4 S2-2202457 P-CR Approval 23.700-08: 23.700-08: Solution on KI#6; Support for returning to home network. Nokia, Nokia Shanghai Bell Rel-18 Approved Approved
9.4 S2-2202932 P-CR Approval 23.700-08: Solution for overload control caused by a high number of UEs returning to home network. InterDigital Rel-18 r02 agreed. Revised to S2-2203456 Pallab (Nokia) comments and requests for clarification
Guanzhou (InterDigital) replies to Pallab (Nokia) and provides r01.
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203456 P-CR Approval 23.700-08: Solution for overload control caused by a high number of UEs returning to home network. InterDigital Rel-18 Revision of S2-2202932r02. Approved Approved
9.4 S2-2202870 P-CR Approval 23.700-16: Solution to Key issues #4 and #6: Automatic selection for SNPN and PNI-NPN cases and leave. Qualcomm Inc. Rel-17 r01 agreed. Revised to S2-2203457 Josep (DT) asks questions for clarification.
Miguel (Qualcomm) responds to Josep (DT) and provide r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203457 P-CR Approval 23.700-16: Solution to Key issues #4 and #6: Automatic selection for SNPN and PNI-NPN cases and leave. Qualcomm Inc. Rel-17 Revision of S2-2202870r01. Approved Approved
9.4 S2-2202274 P-CR Approval 23.700-08: KI #5, New Sol: Access to localized service by using roaming architecture. LG Electronics Rel-18 r03 agreed. Revised to S2-2203458 Pallab (Nokia) asks questions
Guanzhou (InterDigital) comments.
Myungjune (LGE) responds to Guanzhou (InterDigital)
Myungjune (LGE) responds to Pallab (Nokia)
Myungjune (LGE) provides r01.
Pallab (Nokia) asks for further clarification
Myungjune (LGE) responds to Pallab (Nokia) and provides r02.
Josep (DT) makes a minor correction, provides r03.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r03.
Guanzhou (InterDigital) is Ok with r03.
==== Comments Deadline ====
Revised
9.4 S2-2203458 P-CR Approval 23.700-08: KI #5, New Sol: Access to localized service by using roaming architecture. LG Electronics Rel-18 Revision of S2-2202274r03. Approved Approved
9.4 S2-2202309 P-CR Approval 23.700-08: 23.700-08: Solution to KI#3_Hosting network provides localized service when UE does not have prior subscription. Samsung Rel-18 Noted Pallab (Nokia) asks questions
Saso (Intel) seeks clarification.
Ashok (Samsung) replies.
Guanzhou (InterDigital) comments.
Pallab (Nokia) asks further questions
Ashok (Samsung) replies to Pallab (Nokia)
Pallab (Nokia) requests for a revision with below updates
Ashok (Samsung) provides r01
Pallab (Nokia) comments
Pallab (Nokia) provides further comments
Josep (DT) proposes to NOTE.
Ashok (Samsung) provides r02.
Josep (DT) comments.
Ashok (Samsung) responds to Josep
Pallab (Nokia) comments and agrees with DT that the solution is vague
Ashok (Samsung) responds to Pallab (Nokia)
==== Revisions Deadline ====
Josep (DT) objects to this pCR.
Ashok (Samsung) does not agree with Josep (DT)
Ashok (Samsung) responds : Josep , I think you only checked the 6.41.2.4 but forgot to see the 6.41.2.5. Please see where SA1 requirement mentions clearly the word 'prior subscription'
Ashok (Samsung) responds to Pallab (Nokia) and suggest to carefully read SA1 requirement TS 22.261
Pallab (Nokia) responds to Ashok (Samsung)
Ashok (Samsung) comments and propose to go with r02
Antoine (Orange) objects to r00, r01 and r02; agrees that UE with no subscription is not in scope.
Ashok (Samsung) request clarification from Antoine (Orange)
==== Comments Deadline ====
Noted
9.4 S2-2202458 P-CR Approval 23.700-08: 23.700-08: Solution to KI#4; Discovering services offered by SNPN while camping in a serving network. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203459 Guanzhou (InterDigital) comments and asks for clarification.
Yishan (Huawei) asks for clarification.
Pallab (Nokia) responds to Huawei, Oppo and InterDigital and provides r01
Fei (OPPO) comments.
Peter Hedman (Ericsson) provides r02
Josep (DT) comments, provides r03.
Pallab (Nokia) comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203459 P-CR Approval 23.700-08: 23.700-08: Solution to KI#4; Discovering services offered by SNPN while camping in a serving network. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202458r03. Approved Approved
9.4 S2-2202526 P-CR Approval 23.700-08: New solution to address PALS key issues. Huawei, HiSilicon Rel-18 Approved Approved
9.4 S2-2202562 P-CR Approval 23.700-08: FS_eNPN_Ph2 Solution of WT#5 - hosting network selection. Vivo Rel-18 r01 agreed. Revised to S2-2203460 Pallab (Nokia) requests for clarification
Saso (Intel) proposes to MERGE 2562 into 2870
Huan (vivo) provides feedback and r01
Josep (DT) comments.
Huan (vivo) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203460 P-CR Approval 23.700-08: FS_eNPN_Ph2 Solution of WT#5 - hosting network selection. Vivo Rel-18 Revision of S2-2202562r01. Approved Approved
9.4 S2-2202724 P-CR Approval 23.700-08: Solution (KI#5): Steering of UE to a specific hosting network for localized service(s) with consideration of location, times, and coverage of the hosting network. Futurewei Rel-18 Postponed Pallab (Nokia) requests for clarification
Amanda ( Futurewei ) responses to Nokia
Josep (DT) does not agree that this solution is in SID scope.
Josep (DT) comments.
Guanzhou (InterDigital) comments and asks questions.
Amanda ( Futurewei ) responses to DT and clarify that this solution is in the SID scope, provide r01
Amanda ( Futurewei ) responses to DT
Amanda ( Futurewei ) answers questions from Interdigital
==== Revisions Deadline ====
Josep (DT) objects to this pCR.
Due to miss the revision submission deadline, Amanda ( Futurewei ) like to withdraw this contribution and will re-submit in next meeting
==== Comments Deadline ====
Postponed
9.4 S2-2202930 P-CR Approval 23.700-08: Solution for Steering UE to select hosting network for obtaining localized services. InterDigital Rel-18 r02 agreed. Revised to S2-2203461 Peter (Ericsson) provides comments and r01
Guanzhou (InterDigital) responds to Peter(Ericsson).
Josep (DT) comments, provides r02 with EN.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.4 S2-2203461 P-CR Approval 23.700-08: Solution for Steering UE to select hosting network for obtaining localized services. InterDigital Rel-18 Revision of S2-2202930r02. Approved Approved
9.4 S2-2202931 P-CR Approval 23.700-08: New Solution: Local service provisioning via PLMN. InterDigital Rel-18 Approved Approved
9.4 - - - Documents exceeding TU Budget - - Docs:=16 -
9.4 S2-2202008 P-CR Approval 23.700-08: Key issue on Support of non-3GPP accesses for SNPN services. Qualcomm Incorporated Rel-18 Not Handled Not Handled
9.4 S2-2202527 P-CR Approval 23.700-08: Key issue for enabling non-3GPP access for SNPN. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.4 S2-2202705 P-CR Approval 23.700-08: KI related with FS_eNPN_ph2 WT2. Samsung Rel-18 Not Handled Marco (Huawei) proposes to merge to 2008
Kisuk (Samsung) agrees to merge to 2008
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.4 S2-2202867 P-CR Approval 23.700-08: Key issue #4 content proposal based on WT#5.b text. Qualcomm Inc. Rel-18 Not Handled Not Handled
9.4 S2-2202164 P-CR Approval 23.700-08: Solution Selected NID for non-3GPP access. Ericsson Rel-18 Not Handled Not Handled
9.4 S2-2202165 P-CR Approval 23.700-08: Solution Selection mechanism in non-3GPP access network. Ericsson Rel-18 Not Handled Not Handled
9.4 S2-2202561 P-CR Approval 23.700-08: FS_eNPN_Ph2 Update Solution 2 with access network selection for UE onboarding. Vivo Rel-18 Not Handled Not Handled
9.4 S2-2202649 P-CR Approval 23.700-08: Update to solution #3: for Access Network Selection. Lenovo, Motorola Mobility Rel-18 Not Handled Not Handled
9.4 S2-2202580 P-CR Approval 23.700-08: Supported NID assignment model for access to SNPN services via trusted non-3GPP access network. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not Handled
9.4 S2-2202071 P-CR Approval 23.700-08: 23.700-08: Solution to KI#2_N3IWF selection for Onboarding UEs for SNPN. Samsung Rel-18 Not Handled Not Handled
9.4 S2-2202136 P-CR Approval 23.700-08: New solution on support of onboarding over trusted non-3GPP access in SNPN. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.4 S2-2202138 P-CR Approval 23.700-08: New solution on support of Credentials Holder scenarios over trusted non-3GPP in SNPN. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.4 S2-2202156 P-CR Approval 23.700-08: New Solution for NSWO access to SNPN. Huawei, HiSilicon Rel-18 Not Handled Josep (DT) overlooked that the document is marked as NOT HANDLED. Please ignore my last comment.
Josep (DT) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.4 S2-2202168 P-CR Approval 23.700-08: Temporary network reselection for localized service support. Ericsson Rel-18 Not Handled Not Handled
9.4 S2-2202648 P-CR Approval 23.700-08: Solution to KI#4: discovery and selection of hosting network based on URSP rules and configuration information. Lenovo, Motorola Mobility Rel-18 Not Handled Not Handled
9.4 S2-2202889 P-CR Approval 23.700-08: FS_eNPN_Ph2: solution for KI#4: network selection for accessing to a hosting network. Xiaomi Rel-18 Not Handled Not Handled
9.5 - - - Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) - - Docs:=10 -
9.5 S2-2202379 P-CR Approval 23.700-58: New solution for KI#2 and KI#3: U2X for support of Broadcast Remote ID and direct DAA via PC5. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203273 LaeYoung (LGE) provides r01.
Guanzhou (InterDigital) asks questions for clarification.
Stefano (Qualcomm) replies and provides R02.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r02.
Guanzhou (InterDigital) is OK with r02.
==== Comments Deadline ====
Revised
9.5 S2-2203273 P-CR Approval 23.700-58: New solution for KI#2 and KI#3: U2X for support of Broadcast Remote ID and direct DAA via PC5. Qualcomm Incorporated Rel-18 Revision of S2-2202379r02. Approved Approved
9.5 S2-2202455 P-CR Approval 23.700-58: 23.700-58: (New) Solution for KI#1; C2 communication over PC5. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203274 Stefano (Qualcomm) has questions for clarifications
Pallab (Nokia) responds to Stefano (Qualcomm) and provides r01
Shabnam (Ericsson) asks if the solution assumes that the UE supports ProSe or does it intend to mean that UAV supports PC5 and associated procedures for ProSe/V2X as applicable for UAV?
Pallab (Nokia) responds to Ericsson and provides r03. Please ignore r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.5 S2-2203274 P-CR Approval 23.700-58: 23.700-58: (New) Solution for KI#1; C2 communication over PC5. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202455r03. Approved Approved
9.5 S2-2202732 P-CR Approval 23.700-58: Solution for network-assisted DAA. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203275 Stefano (Qualcomm) has questions for clarification.
Guanzhou (InterDigital) asks questions for clarification.
Runze (Huawei) replies to Stefano (Qualcomm) and Guanzhou (Interdigital), and provides r01.
Stefano (Qualcomm) asks further questions.
Guanzhou (InterDigital) comments.
Runze (Huawei) replies to Guanzhou (InterDigital).
Runze (Huawei) replies to Stefano (Qualcomm) and provides r02.
Stefano (Qualcomm) provides R03.
==== Revisions Deadline ====
Runze (Huawei) accepts R03.
==== Comments Deadline ====
Revised
9.5 S2-2203275 P-CR Approval 23.700-58: Solution for network-assisted DAA. Huawei, HiSilicon Rel-18 Revision of S2-2202732r03. Approved Approved
9.5 S2-2202928 P-CR Approval 23.700-58: MBS-based UAV remote ID broadcast. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203276 Stefano (Qualcomm) has questions for clarification, provides R01.
Runze (Huawei) replies to Stefano (Qualcomm) and provides r02.
Stefano (Qualcomm) requests further changes on top of R02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.5 S2-2203276 P-CR Approval 23.700-58: MBS-based UAV remote ID broadcast. Huawei, HiSilicon Rel-18 Revision of S2-2202928r03. Approved Approved
9.5 S2-2202929 P-CR Approval 23.700-58: New Solution: Direct C2 communication over PC5. InterDigital Rel-18 r03 agreed. Revised to S2-2203277 Stefano (Qualcomm) has questions for clarification.
Guanzhou (InterDigital) provides responses.
LaeYoung (LGE) questions for clarification.
Guanzhou (InterDigital) provides r01 to address Stefano and LaeYoung's comments.
Stefano (Qualcomm) comments.
Guanzhou (InterDigital) responds to Stefano.
Stefano (Qualcomm) responds to Guanzhou and provides R02.
Guanzhou (InterDigital) provides r03.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r03.
==== Comments Deadline ====
Revised
9.5 S2-2203277 P-CR Approval 23.700-58: New Solution: Direct C2 communication over PC5 . InterDigital Rel-18 Revision of S2-2202929r03. Approved Approved
9.6 - - - Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) - - Docs:=2 -
9.6 S2-2202029 P-CR Approval 23.700-46: Candidate Solution for 5GS DetNet node reporting. China Telecom Rel-18 Not Handled Not Handled
9.6 S2-2202030 P-CR Approval 23.700-46: Candidate Solution for provisioning DetNet configuration from the DetNet controller to 5GS. China Telecom Rel-18 Not Handled Not Handled
9.7 - - - Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) - - Docs:=47 -
9.7 - - - Solutions for Key issue #1 - - Docs:=13 -
9.7 S2-2202128 P-CR Approval 23.700-25: Solution for reporting 5GS network timing synchronization status. Huawei, HiSilicon Rel-18 Merged into S2-2203465 Devaki (Nokia) comments.
Sang-Jun (Samsung) asks for clarification.
Sebastian (Qualcomm) provides r01
Runze (Huawei) replies to Sang-Jun (Samsung).
Runze (Huawei) replies to Sebastian (Qualcomm).
Runze (Huawei) replies to Devaki (Nokia), and propose to merge the paper into S2-2202299.
Shabnam (Ericsson) shares same view as Nokia, as 2299 combines multiple alternative variants into single pCR, can Huawei clarify what the differences are? Otherwise we should consider this merged.
Devaki (Nokia) proposes to consider this merged with 2299 (based on confirmation by Huawei/Runze: 'Since we propose to merge the paper into S2-2202299, your comments (added EN) will be considered in that paper together.'
==== Revisions Deadline ====
Sang-Jun (Samsung) thanks Runze (Huawei) for replies.
==== Comments Deadline ====
Merged
9.7 S2-2202530 P-CR Approval 23.700-25: New Solution for timing synchronization status reporting. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203462 Devaki (Nokia) comments.
Sang-Jun (Samsung) asks for clarification.
Sebastian (Qualcomm) comments
Qianghua (Huawei) replies.
Qianghua (Huawei) provides r01 and responses.
==== Revisions Deadline ====
Sang-Jun (Samsung) thanks Qianghua (Huawei) for replies, and is fine with r01.
==== Comments Deadline ====
Revised
9.7 S2-2203462 P-CR Approval 23.700-25: New Solution for timing synchronization status reporting. Huawei, HiSilicon Rel-18 Revision of S2-2202530r01. Approved Approved
9.7 S2-2202198 P-CR Approval 23.700-25: Update to Solution #1. Ericsson Rel-18 r02 agreed. Revised to S2-2203463 Shabnam (Ericsson) provides r01 based on offline merging into 2636 and moving relevant content to clause 4.
Sebastian (Qualcomm) comments
Shabnam (Ericsson) responds to Qualcomm and provides r02 along the line of suggested proposal.
==== Revisions Deadline ====
Sebastian (Qualcomm) replies
Devaki (Nokia) also supports to remove EN (which requires some analysis and further discussion). Propose to go forward with r02 minus newly added EN.
Shabnam (Ericsson) the feedback I got from internal experts is that GNSS and other types of clocks used, some can change often. OK to go with r02 minus EN (the EN is not newly added was there in original submission pCR, it was revised based on Sebastian comment hoping to clarify).
Sebastian (Qualcomm) ok to go with r02 minus EN
Shabnam (Ericsson) provides r03 post revision deadline removing the EN, also fixed an editorial where an extra 's' remained.
==== Comments Deadline ====
Revised
9.7 S2-2203463 P-CR Approval 23.700-25: Update to Solution #1. Ericsson Rel-18 Revision of S2-2202198r02. Approved Approved
9.7 S2-2202570 P-CR Approval 23.700-25: KI#1, Update solution #1. CATT Rel-18 Merged into S2-2203464 Shabnam (Ericsson) this pCR has been merged into 2636
==== Revisions Deadline ====
Yuan Tao (CATT) confirms 2570 is merged into 2636.
==== Comments Deadline ====
Merged
9.7 S2-2202636 P-CR Approval 23.700-25: Addressing Editor's notes for solution 1. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203464, merging S2-2202570 and S2-2202629 Jari (NTT DOCOMO) comments
Sebastian (Qualcomm) provides r01
Sebastian (Qualcomm) replies to Jari and provides r02
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r02.
==== Comments Deadline ====
Revised
9.7 S2-2203464 P-CR Approval 23.700-25: Addressing Editor's notes for solution 1. Qualcomm Incorporated, Samsung Rel-18 Revision of S2-2202636r02, merging S2-2202570 and S2-2202629. Approved Approved
9.7 S2-2202629 P-CR Approval 23.700-25: Revision of Solution #1 Inform UE and AF about network timing synchronization status for KI#1. Samsung Rel-18 Merged into S2-2203464 Shabnam (Ericsson) proposes to NOTE the pCR as it does not address and EN nor does it clarify how the conclusion is reached, based on what information.
Sang-Jun (Samsung) informs that 2629 is merged into 2636 via offline discussion.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 S2-2202299 P-CR Approval 23.700-25: KI#1 Solution proposal 5GS network timing synchronization status and reporting - Solution proposal. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203465, merging S2-2202128 Sang-Jun (Samsung) asks for clarification.
Sebastian (Qualcomm) provides r01
Devaki (Nokia) replies.
Runze (Huawei) provides r02.
Shabnam (Ericsson) provides r03, removing parameter details as it is too early and can depend on type of clock etc.
Devaki (Nokia) provides r04.
==== Revisions Deadline ====
Devaki (Nokia) proposes to go with r03 in the interest of progress.
Shabnam (Ericsson) Ericsson is not ok to include the parameters etc. of original, r01, r02, r04, as already commented in r03 version. Our preference is that a solution framework should be agreed first and then companies can provide parameters aspect instead of having this approach.
Sang-Jun (Samsung) thanks Devaki (Nokia) for replies and supports going with r03 in the interest of progress.
==== Comments Deadline ====
Revised
9.7 S2-2203465 P-CR Approval 23.700-25: KI#1 Solution proposal 5GS network timing synchronization status and reporting - Solution proposal. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202299r03, merging S2-2202128. Approved Approved
9.7 S2-2202838 P-CR Approval 23.700-25: KI#1, adding a solution on 5GS network timing synchronization status reporting. ZTE Rel-18 r03 agreed. Revised to S2-2203466 Sebastian (Qualcomm) provides r01
Shabnam (Ericsson) asks if this solution is one of the alternatives in Nokia paper 2299? If so, we can consider this merged? Provides comments
zhendong (ZTE) provides r02 and prefer to keep seperately.
Shabnam (Ericsson) provides r03 with some additional corrections.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203466 P-CR Approval 23.700-25: KI#1, adding a solution on 5GS network timing synchronization status reporting. ZTE Rel-18 Revision of S2-2202838r03. Approved Approved
9.7 - - - Solutions for Key issue #2 - - Docs:=9 -
9.7 S2-2202129 P-CR Approval 23.700-25: Solution for Supporting for 5G timing exposure enhancement. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203467 Sebastian (Qualcomm) comments
Devaki (Nokia) comments.
Runze (Huawei) replies to Devaki(Nokia) and Sebastian (Qualcomm).
Shabnam (Ericsson) Please see some comments, I hope you can provide a revision accordingly.
Runze (Huawei) replies to Shabnam (Ericsson) and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203467 P-CR Approval 23.700-25: Solution for Supporting for 5G timing exposure enhancement. Huawei, HiSilicon Rel-18 Revision of S2-2202129r01. Approved Approved
9.7 S2-2202199 P-CR Approval 23.700-25: Enabling time synchronization service in a specific coverage area, KI#2. Ericsson Rel-18 Merged into S2-2203468 Devaki (Nokia) proposes that this paper is considered merged with 2300r02 which was cosigned by Ericsson.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 S2-2202300 P-CR Approval 23.700-25: KI#2 Solution proposal Time synchronization service enhancements - Solution proposal. Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2203468, merging S2-2202199, S2-2202571, S2-2202617, S2-2202689 and S2-2202839 Devaki (Nokia) provides r02 (please ignore r01), cosigned by Ericsson, ZTE, Samsung, CATT.
Jari (NT DOCOMO) comments
Yuan Tao (CATT) asks for clarification.
Devaki (Nokia) replies.
Jari (NTT DOCOMO) provides r03
Yuan Tao (CATT) provides r04.
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r04.
==== Comments Deadline ====
Revised
9.7 S2-2203468 P-CR Approval 23.700-25: KI#2 Solution proposal Time synchronization service enhancements - Solution proposal. Nokia, Nokia Shanghai Bell, CATT, Samsung, ZTE, Ericsson, NTT DOCOMO Rel-18 Revision of S2-2202300r04, merging S2-2202199, S2-2202571, S2-2202617, S2-2202689 and S2-22028 Approved
9.7 S2-2202617 P-CR Approval 23.700-25: Solution #X: Synchronization with Coverage. Samsung Rel-18 Merged into S2-2203468 Josep (DT) asks question for clarification.
Devaki (Nokia) proposes to consider this solution merged with 2300r01.
Sang-Jun (Samsung) informs that 2617 is merged into 2300r01.
Sang-Jun (Samsung) agrees to merge 2617 into 2300r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 S2-2202839 P-CR Approval 23.700-25: KI#2, a solution to restrict time synchronization service in a specific coverage area. ZTE Rel-18 Merged into S2-2203468 zhendong (ZTE) this paper is merged into S2-2202300
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 S2-2202571 P-CR Approval 23.700-25: KI#2, New solution - AF requests time synchronization service in a specific coverage area. CATT Rel-18 Merged into S2-2203468 Devaki (Nokia) proposes to consider this solution merged with 2300r01.
==== Revisions Deadline ====
Yuan Tao (CATT) confirms 2571 is merged into 2300.
==== Comments Deadline ====
Merged
9.7 S2-2202689 P-CR Approval 23.700-25: New Solution on AF request for time synchronization in a target area. China Mobile Rel-18 Merged into S2-2203468 Sebastian (Qualcomm) suggests to add Editor's notes
Aihua(CMCC) proposes that this paper merges to 2300r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 - - - Solutions for Key issue #3 - - Docs:=4 -
9.7 S2-2202130 P-CR Approval 23.700-25: Solution for controlling 5G time synchronization service based on subscription. Huawei, HiSilicon Rel-18 Postponed Devaki (Nokia) comments.
Josep (DT) comments.
Sebastian (Qualcomm) provides r01
Sang-Jun (Samsung) asks for clarification.
Runze (Huawei) replies and provides r02.
Shabnam (Ericsson) has concerns with this paper where the subscription aspects are extended into new NAS procedures rather than having network control and does not believe this is in scope of the KI.
Shabnam (Ericsson) We need more time on the proposal outside of our understanding of the KI scope it addresses, so I propose we postpone/note this now and take some offline discussion on this first together with 2303.
Devaki (Nokia) comments that the proposal to postpone/note all the solutions proposing proper procedures kind of blocks / derails one KI completely.
Runze (Huawei) replies to Shabnam, and propose r03.
Runze (Huawei) replies to Shabnam (Ericsson).
Runze (Huawei) supports Devaki (Nokia).
Shabnam (Ericsson) asks to postpone this pCR, needs some time to understand this issue, as our understanding of KI is different and absence of restriction does not make it same as developing different solutions. As explained in 2303 thread, and comments.
Shabnam (Ericsson) as discussed with Devaki offline, we are fine to postpone all the pCRs on this topic from this meeting. If you prefer then I will object to the pCR, rather was avoiding that path really since I want to work offline to better understand and find common way forward.
Runze (Huawei) propose r04 and suggest to move forward.
==== Revisions Deadline ====
Runze (Huawei) is ok to postpone the solution.
==== Comments Deadline ====
Postponed
9.7 S2-2202200 P-CR Approval 23.700-25: Enabling time synchronization service via subscription. Ericsson Rel-18 Postponed Devaki (Nokia) comments.
Shabnam (Ericsson) provides r01 according to the comments.
Shabnam (Ericsson) responds to comments and provides r03 on top of r02 provided by ZTE.
zhendong (ZTE) provides r02.
Devaki (Nokia) proposes that this paper should be postponed, as discussed offline with Shabnam (as it is missing the procedure and the details for the impacted procedures, thus unclear which procedure the new principles apply for, also the expected impact).
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.7 S2-2202303 P-CR Approval 23.700-25: KI#3 Solution proposal Controlling 5G time synchronization service based on subscription - Solution proposal. Nokia, Nokia Shanghai Bell Rel-18 Postponed Jari (NTT DOCOMO) comments
Sebastian (Qualcomm) comments
Devaki (Nokia) replies and provides r01.
Sebastian (Qualcomm) comments and provides r02
Devaki (Nokia) is fine with r02, replies.
Shabnam (Ericsson) couldn't find 2303r02 and has concerns on original and r01, see comments.
Shabnam (Ericsson) seems documents 2301 and 2303 titles etc. got mixed up along the way, so reposting my connect on the right thread. Ericsson has concerns on the overall approach and its relation to actual KI itself and its scope, comments
Devaki (Nokia) replies, sorry it seems there may be some misunderstanding e.g. comments refer to TSN AF, there is no occurrence of TSN AF in the solution. Comments refer to 'many aspects', 'aspects' but not saying what? what are the 'aspects'? Unless the comment is technically clear, it is impossible to address.
Shabnam (Ericsson) responds that TSN AF comes from your reference to Rel-16 specs, that is the only time sync supported in Rel-16 and it is without an AF and continuing on Rel-17, same aspect. As the tdoc number is of the wrong document, I hope the thread is correct.
Jari (NTT DOCOMO) provides r02
Shabnam (Ericsson) proposes to postpone this paper as this KI needs further discussion on the scope etc. along with 2130 as commented already.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.7 S2-2202840 P-CR Approval 23.700-25: KI#3, A new solution on 5G time synchronization service based on subscription. ZTE Rel-18 Postponed Shabnam (Ericsson) comments that very similar to 2200 and if can be considered merged.
zhendong (ZTE) is fine to merge.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.7 - - - Solutions for Key issue #4 - - Docs:=8 -
9.7 S2-2202302 P-CR Approval 23.700-25: KI#4: Solution proposal AF to explicitly provide PER. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203469 Sebastian (Qualcomm) raises concerns on the redundant user-plane part of the solution
Haiyang (Huawei) provides questions
György (Ericsson) agrees with Qualcomm
Devaki (Nokia) replies.
Devaki (Nokia) provides r01.
György (Ericsson) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203469 P-CR Approval 23.700-25: KI#4: Solution proposal AF to explicitly provide PER. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202302r01. Approved Approved
9.7 S2-2202057 P-CR Approval 23.700-25: New Solution for KI#5: Interworking with TSN network deployed in the transport network. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203470 zhendong (ZTE) change the tile for the email
Devaki (Nokia) provides r01.
György (Ericsson) comments.
Haiyang (Huawei) clarifies.
Devaki (Nokia) replies.
Haiyang (Huawei) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203470 P-CR Approval 23.700-25: New Solution for KI#5: Interworking with TSN network deployed in the transport network. Huawei, HiSilicon Rel-18 Revision of S2-2202057r02. Approved Approved
9.7 S2-2202695 P-CR Approval 23.700-25: New solution for Key Issue#5: 5GC acting as a CUC for CNC in TN. NTT DOCOMO Rel-18 r03 agreed. Revised to S2-2203471 Devaki (Nokia) provides r01.
Jari (NTT DOCOMO) provides r02.
Sebastian (Qualcomm) comments
Jari (NTT DOCOMO) responds to Sebastian
Sebastian (Qualcomm) replies
Jari (NTT DOCOMO) responds to Haiyang
Haiyang (Huawei) provides questions
Jari (NTT DOCOMO) provides r03
Haiyang (Huawei) provides responses
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203471 P-CR Approval 23.700-25: New solution for Key Issue#5: 5GC acting as a CUC for CNC in TN . NTT DOCOMO Rel-18 Revision of S2-2202695r03. Approved Approved
9.7 S2-2202841 P-CR Approval 23.700-25: KI#5, adding a new solution on the Interworking with TSN network deployed in N3. ZTE Rel-18 r03 agreed. Revised to S2-2203472 Sebastian (Qualcomm) provides r01
Haiyang (Huawei) provides questions
zhendong (ZTE) provides the response
zhendong (ZTE) provides the r02
Haiyang (Huawei) further comments
Haiyang (Huawei) comments
Haiyang (Huawei) provides response; also suggests to merge this paper into 2057
Haiyang (Huawei) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203472 P-CR Approval 23.700-25: KI#5, adding a new solution on the Interworking with TSN network deployed in N3. ZTE Rel-18 Revision of S2-2202841r03. Approved Approved
9.7 - - - Solutions for Key issue #6 - - Docs:=13 -
9.7 S2-2202059 P-CR Approval 23.700-25: New Solution for KI#6: Cross layer scheduling optimization. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203473 Devaki (Nokia) comments.
Sebastian (Qualcomm) provides r01 with ENs
György (Ericsson) raises questions.
Haiyang (Huawei) replies and provides r02
Qianghua (Huawei) withdraws my previous replies, that is supposed to reply for another doc, my apologies
Qianghua (Huawei) replies
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203473 P-CR Approval 23.700-25: New Solution for KI#6: Cross layer scheduling optimization. Huawei, HiSilicon Rel-18 Revision of S2-2202059r02. Approved Approved
9.7 S2-2202301 P-CR Approval 23.700-25: KI#6 Solution proposal Pro-active RAN burst timing preference provision. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203474 Sebastian (Qualcomm) comments
György (Ericsson) comments
Devaki (Nokia) replies and provides r01.
Devaki (Nokia) replies.
Devaki (Nokia) comments that Ericsson comments seem to be applying for a different P-CR / not this email thread, kindly re-check and re-post in the right email thread.
Devaki (Nokia) replies, sorry it seems there may be some misunderstanding e.g. comments refer to TSN AF, there is no occurrence of TSN AF in the solution. Comments refer to 'many aspects', 'aspects' but not saying what? what are the 'aspects'? Unless the comment is technically clear, it is impossible to address.
Shabnam (Ericsson) Devaki, as the proposal encompasses everything end to end, it is very hard to comment other than to remove everything not related to subscription itself for now. But I believe that is captured in 2200 which you also mentioned. We need more time on the rest of the proposal so I propose we postpone/note this now and take some offline discussion on this first.
Devaki (Nokia) respectfully disagrees with the proposed way forward.
Shabnam (Ericsson) responds that TSN AF comes from your reference to Rel-16 specs, that is the only time sync supported in Rel-16 and it is without an AF and continuing on Rel-17, same aspect. As the tdoc number is of the wrong document, I hope the thread is correct.
György (Ericsson) responds.
Devaki (Nokia) comments.
Devaki (Nokia) provides r03 with an EN to address E/// last comment.
==== Revisions Deadline ====
György (Ericsson) ok with r03
==== Comments Deadline ====
Revised
9.7 S2-2203474 P-CR Approval 23.700-25: KI#6 Solution proposal Pro-active RAN burst timing preference provision . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202301r03. Approved Approved
9.7 S2-2202197 P-CR Approval 23.700-25: Assisted Timing Support. Ericsson Rel-18 r02 agreed. Revised to S2-2203475 Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
Sebastian (Qualcomm) comments
Shabnam (Ericsson) provides r01 and responds to comments from Qualcomm, Nokia and NTT-DoCoMo.
Jari (NTT DOCOMO) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203475 P-CR Approval 23.700-25: Assisted Timing Support. Ericsson Rel-18 Revision of S2-2202197r02. Approved Approved
9.7 S2-2202529 P-CR Approval 23.700-25: Solution2 Update for UL scheduling. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203476 Devaki (Nokia) comments that the solution is partly out of scope of the KI#6.
Sebastian (Qualcomm) suggests to document these changes as new solution, provides r01
Qianghua (Huawei) provides r02
Sebastian (Qualcomm) comments
Qianghua (Huawei) replies
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203476 P-CR Approval 23.700-25: Solution2 Update for UL scheduling. Huawei, HiSilicon Rel-18 Revision of S2-2202529r02. Approved Approved
9.7 S2-2202619 P-CR Approval 23.700-25: Revision of Solution #2 Burst arrival time adaptation for KI#6. Samsung Rel-18 Merged into S2-2203477 Sebastian (Qualcomm) suggests to merge paper into 2637
Sang-Jun (Samsung) accepts Sebastian (Qualcomm)'s suggestion to merge paper into 2637.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.7 S2-2202637 P-CR Approval 23.700-25: Addressing Editor's notes for solution 2. Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2203477, merging S2-2202619 Devaki (Nokia) comments.
Sebastian (Qualcomm) replies to Nokia
György (Ericsson) comments
Sebastian (Qualcomm) replies and provides r01
Sebastian (Qualcomm) replies and provides r02
Qianghua (Huawei) provides comments on r01
Sebastian (Qualcomm) replies and provides r03
György (Ericsson) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.7 S2-2203477 P-CR Approval 23.700-25: Addressing Editor's notes for solution 2. Qualcomm Incorporated Rel-18 Revision of S2-2202637r03, merging S2-2202619. Approved Approved
9.7 S2-2202697 P-CR Approval 23.700-25: New solution for Key Issue#6: BAT adjustment during a QoS Flow setup or modification. NTT DOCOMO Rel-18 r01 agreed. Revised to S2-2203478 Sang-Jun (Samsung) asks for clarification.
Sebastian (Qualcomm) provides r01
Jari (NTT DOCOMO) responds to Sang-Jun
==== Revisions Deadline ====
Sang-Jun (Samsung) is fine with r01.
==== Comments Deadline ====
Revised
9.7 S2-2203478 P-CR Approval 23.700-25: New solution for Key Issue#6: BAT adjustment during a QoS Flow setup or modification. NTT DOCOMO Rel-18 Revision of S2-2202697r01. Approved Approved
9.7 - - - Documents exceeding TU Budget - - Docs:=3 -
9.8 - - - Study on RedCap Phase 2 (FS_RedCAP_Ph2) - - Docs:=16 -
9.8 - - - Architectural Assumptions and Requirements - - Docs:=1 -
9.8 S2-2202512 P-CR Approval 23.700-68: Support of HLcom features for NR RedCap devices. Sony Rel-18 Postponed Qian (Ericsson) provides comments and r01
Lars (Sony) responds to Qian and is not ok with r01
Steve (Huawei) comments
Miguel (Qualcomm) comments
Qian (Ericsson) comments
Lars (Sony) comments
Qian (Ericsson) asks question.
Lars (Sony) as an author suggests to postpone paper
==== Revisions Deadline ====
Qian (Ericsson) thanks Lars (Sony) for the proposal and comments
==== Comments Deadline ====
Postponed
9.8 - - - Solution Updates for KI#1 - - Docs:=7 -
9.8 S2-2202212 P-CR Approval 23.700-68: Solution #1 updates. Ericsson Rel-18 r02 agreed. Revised to S2-2203278 Lars (Sony) provides r01
Miguel (Qualcomm) comments
Hannu (Nokia) supports the comment from Miguel (Qualcomm)
Qian (Ericsson) comments and provides r02
==== Revisions Deadline ====
Qian (Ericsson) proposes to agree on r02
Lars (Sony) is fine with r02
==== Comments Deadline ====
Revised
9.8 S2-2203278 P-CR Approval 23.700-68: Solution #1 updates . Ericsson Rel-18 Revision of S2-2202212r02. Approved Approved
9.8 S2-2202425 P-CR Approval 23.700-68: Update of Solution#3: Resolution of ENs and clarifications on AMF behaviour. Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2203279, merging S2-2202620 Lars (Sony) provides r01 to suggest further updates
Hannu (Nokia) provides r02 and comments.
Steve (Huawei) provides r03
Jinguo(ZTE) provides r04
Steve (Huawei) provides r05
Steve (Huawei) provides r06.
Hannu (Nokia) responds to Steve
==== Revisions Deadline ====
Qian (Ericsson) proposes to go with r06.
Lars (Sony) is ok with r06.
==== Comments Deadline ====
Revised
9.8 S2-2203279 P-CR Approval 23.700-68: Update of Solution#3: Resolution of ENs and clarifications on AMF behaviour . Huawei, HiSilicon Rel-18 Revision of S2-2202425r06, merging S2-2202620. Approved Approved
9.8 S2-2202532 P-CR Approval 23.700-68: Update Solution 2. Sony, Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203280 Qian (Ericsson) provides comments and asks questions
Lars (Sony) provides r01 based on Qian comments
Steve (Huawei) asks about paging in the wider area
Lars (Sony) responds to Steve
Steve (Huawei) replies to Lars
Steve (Huawei) thanks understand.
==== Revisions Deadline ====
Lars (Sony) proposes to go with r01
Qian (Ericsson) comments and suggests to go with r01
Steve (Huawei) is ok with r01
==== Comments Deadline ====
Revised
9.8 S2-2203280 P-CR Approval 23.700-68: Update Solution 2. Sony, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202532r01. Approved Approved
9.8 S2-2202620 P-CR Approval 23.700-68: EN clarification on solution#3 for no Xn interface case. China Mobile Rel-18 Merged into S2-2203279 Qian (Ericsson) propose to merge this paper into 2425
Aihua(CMCC) agrees to merge 2620 into 2425
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.8 - - - New Solutions for KI#1 - - Docs:=4 -
9.8 S2-2202671 P-CR Approval 23.700-68: New solution to KI#1: Enabling UPF buffering per NG-RAN request for UE in RRC_Inactive state with long eDRX cycle. ZTE Rel-18 r03 agreed. Revised to S2-2203281 Qian (Ericsson) asks questions
Jinguo(ZTE) response to Qian (Ericsson) and provides r01
Jinguo(ZTE) provides r02 to address the question from Hannu (Nokia)
Hannu (Nokia) asks questions on the AMF CM-state.
Qian (Ericsson) provides further comments.
Jinguo(ZTE) provides r03
==== Revisions Deadline ====
Qian (Ericsson) comments and considers it's ok to go with r03
Jinguo(ZTE) thanks Qian (Ericsson)
==== Comments Deadline ====
Revised
9.8 S2-2203281 P-CR Approval 23.700-68: New solution to KI#1: Enabling UPF buffering per NG-RAN request for UE in RRC_Inactive state with long eDRX cycle. ZTE Rel-18 Revision of S2-2202671r03. Approved Approved
9.8 S2-2202882 P-CR Approval 23.700-68: Converged Solution proposal between Solutions #1, #3, and #4. Qualcomm Inc Rel-18 r03 + changes agreed. Revised to S2-2203599. Lars (Sony) provides r01
Qian (Ericsson) provides r02
Hannu (Nokia) provides r03 and comments that not all network vendors support the violation of the AMF CM-CONNECTED state.
==== Revisions Deadline ====
Qian (Ericsson) is ok with either r02 or r03, though prefer r02.
Lars (Sony) surprised that sourcing company has not addressed comments in the solution.
Qian (Ericsson) comments and asks Lars (Sony) to check if r02 (or r03) can be agreed in this meeting.
Lars (Sony) Not sure what to do with this one, r02 and r03 still have comments and things that should be address in my view.
Miguel (Qualcomm) ok with r02 or r03, missed there were pending comments in the revisions, propose to agree either r02 or r03. But provides answers, and we could reopen in CC#3 to make those (small) changes.
Lars (Sony) there was one more change to the figure.
Qian (Ericsson) proposes to add the following 3 changes on top of r03: 1) add 'except paging procedure,' in clause 6.x.2; 2) update step 4 in figure 6.x.3.3-1 to synch the procedure name with clause 6.x.3.2; 3) update step 5b in figure 6.x.3.3-1 to start the arrow from AMF.
Miguel (Qualcomm) proposes to use r03 with changes to be copy pasted in chat window in CC#3, as described in content of this email.
==== Comments Deadline ====
Miguel (Qualcomm) ok with Qian proposal
Revised
9.8 S2-2203599 P-CR Approval 23.700-68: Converged Solution proposal between Solutions #1, #3, and #4. Qualcomm Inc Rel-18 Revision of S2-2202882r03 + changes. Approved Approved
9.8 - - - Evaluation of solutions for KI#1 - - Docs:=4 -
9.8 S2-2202213 P-CR Approval 23.700-68: Solution Evaluation for KI#1. Ericsson Rel-18 Merged into S2-2203282 Qian (Ericsson) provides comments and propose to use this paper as the base for evaluation
Hannu (Nokia) asks Qian whether it is OK to merge this paper to S2-2202534 and use the merged paper as the basis for evaluation?
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.8 S2-2202426 P-CR Approval 23.700-68: Initial evaluations for KI#1 solutions. Huawei, HiSilicon Rel-18 Merged into S2-2203282 Qian (Ericsson) proposes to merge this paper into 2534 as commented on that thread.
Hannu (Nokia) supports the proposal from Qian.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.8 S2-2202534 P-CR Approval 23.700-68: Initial Evaluation. Sony, Nokia, Nokia Shanghai Bell Rel-18 r07 agreed. Revised to S2-2203282, merging S2-2202213 and S2-2202426 Lars (Sony) provides r01 as a merge of S2-2202213 and S2-2202426
Qian (Ericsson) provides comments and propose to use this paper as the base for evaluation
Lars (Sony) provides r03
Qian (Ericsson) provides r02
Hannu (Nokia) prefers r03 and comments.
Steve (Huawei) provides r04
Lars (Sony) provides r05
Steve (Huawei) comments
Lars (Sony) responds to Steve
Steve (Huawei) how to capture these aspects?
Lars (Sony) think is already captured
Steve (Huawei) only partially captured
Lars (Sony) responds and suggest wording
Lars (Sony) provides r06
Steve (Huawei) provides r07
==== Revisions Deadline ====
Lars (Sony) agrees to r07
Qian (Ericsson) comments and proposes to go with r07
Steve (Huawei) is ok with r07
==== Comments Deadline ====
Revised
9.8 S2-2203282 P-CR Approval 23.700-68: Initial Evaluation. Sony, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2202534r07, merging S2-2202213 and S2-2202426. Approved Approved
9.9 - - - Study on Vehicle Mounted Relays (FS_VMR) - - Docs:=23 -
9.9 - - - Incoming LS's - - Docs:=1 -
9.9 S2-2201954 LS In Action LS from TSG RAN: Reply LS to SA2 on IAB support of NR satellite access TSG RAN (RP-220963) Rel-18 Noted Hong (Qualcomm) propose to NOTE, pending on approval of revision of S2-2202317. Noted
9.9 - - - Arch Assumptions - - Docs:=2 -
9.9 S2-2202317 P-CR Approval 23.700-05: Architecture Assumption: VMR not applicable to NR satellite access. Rakuten Mobile Rel-18 r01 agreed. Revised to S2-2203283 LiMeng (Huawei) provides r01.
Aoken (Rakuten Mobile) fine with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.9 S2-2203283 P-CR Approval 23.700-05: Architecture Assumption: VMR not applicable to NR satellite access . Rakuten Mobile Rel-18 Revision of S2-2202317r01. Approved Approved
9.9 - - - New/updated KI's - - Docs:=3 -
9.9 S2-2202510 P-CR Approval 23.700-05: KI#5: Update KI5. Sony Rel-18 Noted Zhenhua (vivo) comments
Lars (Sony) responds to Zhenhua
Hong (Qualcomm) comments.
Lars (Sony) comments.
Alessio(Nokia) comments and proposes to note
==== Revisions Deadline ====
Lars (Sony) As an author, I am ok to NOTED the paper
==== Comments Deadline ====
Noted
9.9 S2-2202214 P-CR Approval 23.700-05: Terminology updates. Ericsson Rel-18 Approved Approved
9.9 S2-2202765 P-CR Approval 23.700-05: TR 23.700-05: new KI on UE permission and policies for accessing VMR. Qualcomm Incorporated Rel-18 This was postponed. LiMeng (Huawei) provides comment
Lars (Sony) provides comment
Qian (Ericsson) provides comments and r01
Hong (Qualcomm) provides r02.
Hong (Qualcomm) replies to Lars.
Lars (Sony replies to Hong.
Mehrdad (Samsung) comments
Hong (Qualcomm) provides r03.
LiMeng (Huawei) provides r04.
LiMeng (Huawei) provides r05, and asks to withdrawn r04.
alessio(nokia) can accept r03 but not subsequent r05 (assuming r04 is withdrawn)
LiMeng (Huawei) cannot accept r03.
Hong (Qualcomm) comments.
Hong (Qualcomm) provides r06
LiMeng (Huawei) replies, objects r04 and asks Alessio to re-consider his objection to r05.
==== Revisions Deadline ====
Hong (Qualcomm) replies to LiMeng and suggest to consider r06.
LiMeng (Huawei) replies to Hong, objects to r00-r04 and r06.
LiMeng (Huawei) comments.
Hong (Qualcomm) replies to LiMeng.
Hong (Qualcomm) provide r07 in draft folder.
alessio (nokia) is ok with r07
==== Comments Deadline ====
LiMeng (Huawei) provides r08 in the draft folder.
Postponed
9.9 - - - New solutions - - Docs:=0 -
9.9 - - - KI#1 - - Docs:=5 -
9.9 S2-2202033 P-CR Approval 23.700-05: Solution for KI#1: Mobile base station relay operation authorization using Forbidden Areas. Huawei, HiSilicon Rel-18 Merged into S2-2203284 LiMeng (Huawei) agrees to merge this document into S2-2202215, as per the suggestion from Rapporteur.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.9 S2-2202215 P-CR Approval 23.700-05: Solution for configuration. Ericsson Rel-18 r03 + removing 'in SA5' in the EN revised to S2-2203284, merging S2-2202033 LiMeng (Huawei) provides r01, merge S2-2202033.
Qian (Ericsson) comments and r02.
Hong (Qualcomm) comments.
Qian (Ericsson) comments and provides r03.
LiMeng (Huawei) doesn't think the added EN is necessary and provides r04.
==== Revisions Deadline ====
Hong (Qualcomm) replies to LiMeng and comments on r04, and suggest to keep the EN in r03 (with potential removal of SA5).
Qian (Ericsson) comments and consider it's ok to go with r04, or go with the proposal from Hong by removing 'in SA5' in the EN on top of r03.
==== Comments Deadline ====
Revised
9.9 S2-2203284 P-CR Approval 23.700-05: Solution for configuration . Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2202215r03 + changes, merging S2-2202033. Approved Approved
9.9 S2-2202761 P-CR Approval 23.700-05: TR 23.700-05: KI#1, new solution proposal on provisioning and policy control for FS_VMR. Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2203285 LiMeng (Huawei) provides comment
LaeYoung (LGE) comments.
Hong (Qualcomm) provides r01.
Mehrdad (Samsung) comments
Hong (Qualcomm) replies to Mehrdad.
LiMeng (Huawei) provides r02.
Alessio(nokia) has fundamental issues with the proposal and cannot accept it as such.
Hong (Qualcomm) replies to Alessio.
==== Revisions Deadline ====
Alessio(Nokia ) comments the note in r03 does not read right and proposes a new note
==== Comments Deadline ====
Revised
9.9 S2-2203285 P-CR Approval 23.700-05: TR 23.700-05: KI#1, new solution proposal on provisioning and policy control for FS_VMR. Qualcomm Incorporated Rel-18 Revision of S2-2202761r03. Approved Approved
9.9 - - - KI#2 - - Docs:=3 -
9.9 S2-2202032 P-CR Approval 23.700-05: Solution for KI#2: Reusing existing procedures for UE mobility. Huawei, HiSilicon Rel-18 Approved Approved
9.9 S2-2202478 P-CR Approval 23.700-05: New Solution: Mobility procedures. Vivo Rel-18 r05 agreed. Revised to S2-2203286 LiMeng (Huawei) asks for clarification.
Zhenhua (vivo) replies to LiMeng (Huawei) and provides r01.
Lars (Sony) as for a clarification.
Zhenhua (vivo) replies to Lars (Sony).
Qian (Ericsson) provides comments and asks questions.
Hong (Qualcomm) asks for clarifications.
Zhenhua (vivo) replies and provides r02
Hong (Qualcomm) replies to Zhenhua.
Zhenhua (vivo) responds to Hong (Qualcomm) and provides r03
Zhenhua (vivo) provides r04 to correct the impact on AMF.
Alessio(Nokia) asks this paper to be laser focused on the new ides of link ID: show WHY it is needed (i.e. its role and why we cannot do without it), define it in detail, and show the purpose is each intended use at high level. if you want to show one example or two procedures fine. but as is I have a hard time to accept this paper.
Zhenhua (vivo) replies to Alessio(Nokia).
Zhenhua (vivo) provides r05
==== Revisions Deadline ====
alessio(nokia) iif this means there is a proxy request of mobility I think this needs SA3 to look into this link ID.... byut this is an evaluation comment. we can let this solution be documented.
==== Comments Deadline ====
Revised
9.9 S2-2203286 P-CR Approval 23.700-05: New Solution: Mobility procedures. Vivo Rel-18 Revision of S2-2202478r05. Approved Approved
9.9 - - - KI#3 - - Docs:=1 -
9.9 S2-2202216 P-CR Approval 23.700-05: Solution for mobility. Ericsson Rel-18 Noted Zhenhua (vivo) ask questions for clarification
Qian (Ericsson) responds to Zhenhua (vivo)
Hong (Qualcomm) asks questions and comments.
Qian (Ericsson) responds to Hong (Qualcomm) and provide r01.
LiMeng (Huawei) provides r02.
alessio(nokia) proposes to note this paper and come back at next meeting
Qian (Ericsson) indicates that a solution with ENs/NOTEs is normal process for the first meeting allowing solution contribution. Don't see a clear reason why it shall be postponed. Considering the limited meeting time, we shall progress with the proposed solution.
Qian (Ericsson) provides r03 to address the technical concern.
==== Revisions Deadline ====
alessio(nokia) our problem is that this seems a solution that is unreal as to be useful it has to assume many things that need to exist maybe is a lab under a controlled environment but not in the real world. proposed still to not then we can discuss offline the merits of this.
Qian (Ericsson) comments that concerns raised seem related to evaluation of the solution.
alessio(nokia) our problem is that this seems a solution that is unreal as to be useful it has to assume many things that need to exist maybe is a lab under a controlled environment but not in the real world. proposed still to not approve then we can discuss offline the merits of this.
==== Comments Deadline ====
Noted
9.9 - - - KI#4 - - Docs:=2 -
9.9 S2-2202768 P-CR Approval 23.700-05: TR 23.700-05: KI#4, new solution on support of roaming of mobile base station relays. Qualcomm Incorporated Rel-18 r02 + clause 6.x.3.3 deleted revised to S2-2203287 LiMeng (Huawei) provides comment
Qian (Ericsson) provides comments and asks questions
Hong (Qualcomm) replies to Qian and LiMeng.
Wanqiang (Huawei) replies and has fundamental concern regarding the concept of the paper
Alessio(nokia) requests to update the document to clarify that the HPLMN must share the same MCC as the VPLMN at least.
Hong (Qualcomm) replies to Wanqiang, and provides r01.
Hong (Qualcomm) provides r02.
==== Revisions Deadline ====
Wanqiang (Huawei) objects any version of the paper and has fundamental issue with the concept.
Hong (Qualcomm) replies to Wanqiang.
Wanqiang (Huawei) replies and maintains the position.
Hong (Qualcomm) provides r03 in draft folder, removing the corresponding clause.
==== Comments Deadline ====
Revised
9.9 S2-2203287 P-CR Approval 23.700-05: TR 23.700-05: KI#4, new solution on support of roaming of mobile base station relays . Qualcomm Incorporated Rel-18 Revision of S2-2202768r02 + changes. Approved Approved
9.9 - - - KI#5 - - Docs:=4 -
9.9 S2-2202511 P-CR Approval 23.700-05: KI#5: Solution Network based Positioning of VMR for location services. Sony Rel-18 r02 agreed. Revised to S2-2203288 Yunjing (CATT) provides comments.
Lars (Sony) responds to Yunjing and provides r01.
Yunjing (CATT) replies to Lars (Sony).
Lars (Sony) responds to Yunjing.
LiMeng (Huawei) provides r02.
Lars (Sony) responds Yunjing.
Lars (Sony) is ok with r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.9 S2-2203288 P-CR Approval 23.700-05: KI#5: Solution Network based Positioning of VMR for location services. Sony Rel-18 Revision of S2-2202511r02. Approved Approved
9.9 S2-2202628 P-CR Approval 23.700-05: KI#5, New Sol: Support of positioning for UE accessing via mobile base station relay. CATT Rel-18 r04 agreed. Revised to S2-2203289 Lars (Sony) ask question on the solution.
Yunjing (CATT) replies to Lars (Sony).
Lars (sony) responds and asks for a r01 with ENs.
Yunjing (CATT) provides r01.
Lars (Sony) provides r02.
LiMeng (Huawei) provides r03.
Yunjing (CATT) replies to LiMeng (Huawei) and provides r04.
==== Revisions Deadline ====
Lars (Sony) is ok with r04.
==== Comments Deadline ====
Revised
9.9 S2-2203289 P-CR Approval 23.700-05: KI#5, New Sol: Support of positioning for UE accessing via mobile base station relay. CATT Rel-18 Revision of S2-2202628r04. Approved Approved
9.9 - - - KI#6 - - Docs:=2 -
9.9 S2-2202217 P-CR Approval 23.700-05: Solution for user location. Ericsson Rel-18 r01 agreed. Revised to S2-2203290 LiMeng (Huawei) provides r01.
==== Revisions Deadline ====
Qian (Ericsson) is ok with r01.
==== Comments Deadline ====
Revised
9.9 S2-2203290 P-CR Approval 23.700-05: Solution for user location. Ericsson Rel-18 Revision of S2-2202217r01. Approved Approved
9.10 - - - Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) - - Docs:=44 -
9.10 - - - Updates to Section 4 - - Docs:=1 -
9.10 S2-2202709 P-CR Approval 23.700-71: Update LCS Architectural Assumptions and Requirements. Deutsche Telekom Rel-18 Approved Approved
9.10 - - - New KI's - - Docs:=6 -
9.10 S2-2202976 P-CR Approval 23.700-71: Key Issue: Support of Reduced UE Power Consumption. Qualcomm Incorporated Rel-18 Merged into S2-2203292 Ming (CATT) suggests merge S2-2202976 and S2-2202920.
Runze (Huawei) agrees with Ming (CATT), and propose to take S2-2202920 as baseline.
Stephen (Qualcomm) replies to Runze (Huawei) and Ming (CATT)
==== Revisions Deadline ====
Stephen (Qualcomm) now agrees to merge S2-2202976 into S2-2202920
==== Comments Deadline ====
Merged
9.10 S2-2202977 P-CR Approval 23.700-71: Key Issue: Support of Reduced Latency. Qualcomm Incorporated Rel-18 Approved Runze (Huawei) asks a question.
Stephen (Qualcomm) replies to Runze (Huawei)
Runze (Huawei) replies to Stephen (Qualcomm).
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.10 S2-2202764 P-CR Approval 23.700-41: New key issue for WT#3.3: Triggered Location for UE power saving purpose. Orange Rel-18 r03 agreed. Revised to S2-2203291 Ming (CATT) asks questions.
Runze (Huawei) asks a question for clarification.
Antoine (Orange) replies.
Hank (vivo) has some interest in this KI and provides some opinions.
Ming (CATT) provies r01.
Hank (vivo) asks a question on the r01.
Antoine (Orange) provides r02.
Hank (vivo) provides r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.10 S2-2203291 P-CR Approval 23.700-41: New key issue for WT#3.3: Triggered Location for UE power saving purpose . Orange, CATT Rel-18 Revision of S2-2202764r03. Approved Approved
9.10 S2-2202920 P-CR Approval 23.700-71: Key issue proposal on LPHAP UE identification. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2203292, merging S2-2202976 Ming (CATT) suggests merge S2-2202976 and S2-2202920.
Runze (Huawei) propose r01, merging S2-2202976.
Hank (vivo) has some comments on this KI.
Stephen (Qualcomm) provides an r02
Leo (Deutsche Telekom) provides r03.
Antoine (Orange) provides r04, removing 'LPHP UE'.
==== Revisions Deadline ====
Stephen (Qualcomm) prefers the r04 (but the r02 and r03 are okay)
Runze (Huawei) can live with r04.
==== Comments Deadline ====
Revised
9.10 S2-2203292 P-CR Approval 23.700-71: Key issue proposal on LPHAP UE identification. Huawei, HiSilicon Rel-18 Revision of S2-2202920r04, merging S2-2202976. Approved Approved
9.10 - - - Updated KI's - - Docs:=2 -
9.10 S2-2202621 P-CR Approval 23.700-71: KI #4: Update KI#4 to add a question related to privacy check. CATT Rel-18 r01 agreed. Revised to S2-2203293 Hank (vivo) provides r01.
Yunjing (CATT) is fine with r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.10 S2-2203293 P-CR Approval 23.700-71: KI #4: Update KI#4 to add a question related to privacy check. CATT Rel-18 Revision of S2-2202621r01. Approved Approved
9.10 - - - KI#1 solutions - - Docs:=6 -
9.10 S2-2201975 P-CR Approval 23.700-71: Solution LPP transport via user plane. Ericsson Rel-18 r01 agreed. Revised to S2-2203294 Guanglei (Huawei) ask questions
Yunjing (CATT) asks questions for clarification
Scott (Inspur) reply to Rechard
Richard (Ericsson) reply to comments and providing r01
Scott (Inspur) asks to add FFSs
Richard (Ericsson) reply to Scott
Cai Simon (Nokia) provides comments
Scott(Inspur) reply to Richard (Ericsson)
Stephen (Qualcomm) comments
Richard (Ericsson) reply to Stephen
Richard (Ericsson) reply to Simon
Cai Simon (Nokia) clarifies questions that may be misinterpreted
==== Revisions Deadline ====
Cai Simon (Nokia) further comments
Richard (Ericsson) reply to Simon (resent due to server problem)
Cai Simon (Nokia) provides the combined comments
==== Comments Deadline ====
Revised
9.10 S2-2203294 P-CR Approval 23.700-71: Solution LPP transport via user plane. Ericsson Rel-18 Revision of S2-2201975r01. Approved Approved
9.10 S2-2202933 P-CR Approval 23.700-71: FS_eLCS_Ph3 TR Solution to KI#1. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203295 Richard (Ericsson) comments
Cai Simon (Nokia) clarifies to Richard (Ericsson)
Cai Simon (Nokia) provides r01
Stephen (Qualcomm) comments
Richard (Ericsson) provides additional comments
Cai Simon (Nokia) clarifies to Stephen (Qualcomm)
==== Revisions Deadline ====
Cai Simon (Nokia) clarifies and provides r02
Cai Simon (Nokia) clarifies to Andy (Samsung)
Richard (Ericsson) replies to Simon
Cai Simon (Nokia) further clarifies based on the reply in 2201975
Richard (Ericsson) has concern on r00,r01,r02 and proposes to postpone or note the paper.
Guanglei (Huawei) suggest approve r02, as all UP related solutions in this meeting needs further discussion
==== Comments Deadline ====
Revised
9.10 S2-2203295 P-CR Approval 23.700-71: FS_eLCS_Ph3 TR Solution to KI#1. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202933r02. Approved Approved
9.10 S2-2202436 P-CR Approval 23.700-71: Solution for KI#1: Architectural Enhancement to support User Plane positioning. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203296 Stephen (Qualcomm) comments
Guanglei (Huawei) replies to Stephen (Qualcomm) and provides r01.
Richard (Ericsson) comments
Guanglei (Huawei) replies and provides r02.
Cai Simon (Nokia) asks questions
Cai Simon (Nokia) provides comments
Richard (Ericsson) replies to Huawei and propose merging
Cai Simon (Nokia) provides more comments besides pending question
Guanglei (Huawei) provides r04 and thinks it would be too early to consider merge
Guanglei (Huawei) replies and corrects that the latest revision number is r03
Stephen (Qualcomm) comments again
Cai Simon (Nokia) clarifies to Stephen (Qualcomm)
Cai Simon (Nokia) clarifies and provides r01
Richard (Ericsson) provides additional comments
Guanglei (Huawei) replies to Richard (Ericsson)
Guanglei (Huawei) replies to Simon
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r03
Cai Simon (Nokia) provide combined comments
Cai Simon (Nokia) agrees to 'further discuss and evaluate this later'
Richard (Ericsson) has concern on r00,r01,02,03 and proposes to postpone the paper.
Guanglei (Huawei) replies to Richard (Ericsson) and suggest approve, as all UP related solutions in this meeting needs further discussion
Guanglei (Huawei) replies to Richard (Ericsson) and suggest approve r03, as all UP related solutions in this meeting needs further discussion
Guanglei (Huawei) ask for CC#3
==== Comments Deadline ====
Revised
9.10 S2-2203296 P-CR Approval 23.700-71: Solution for KI#1: Architectural Enhancement to support User Plane positioning. Huawei, HiSilicon Rel-18 Revision of S2-2202436r03. Approved Approved
9.10 - - - KI#2 solutions - - Docs:=4 -
9.10 S2-2202673 P-CR Approval 23.700-71: FS_eLCS_Ph3 New Solution to KI#2. ZTE Rel-18 r02 + changes agreed. Revised to S2-2203600. Hank (vivo) asks several questions about this solution.
Richard (Ericsson) providing comments and questions
Jinguo(ZTE) replies to Richard (Ericsson) and Hank (vivo) and provides r01
Runze (Huawei) comments.
Jinguo(ZTE) replies to Runze (Huawei)
Stephen (Qualcomm) comments
Jinguo(ZTE) provides r02
Hank (vivo) comments on r02.
==== Revisions Deadline ====
Jinguo(ZTE) replies to Hank (vivo)
Stephen (Qualcomm) can agree the r02
Richard (Ericsson) object to r00,r01,r02
Jinguo(ZTE) asks Richard (Ericsson) to withdraw your objection which is evaluation comment and just before the revision deadline. Ask for CC#3.
==== Comments Deadline ====
Jinguo(ZTE) provides r04 in CC#3 folder
Jinguo(ZTE) provides another FFS
Revised
9.10 S2-2203600 P-CR Approval 23.700-71: FS_eLCS_Ph3 New Solution to KI#2. ZTE Rel-18 Revision of S2-2202673r02 + changes. Approved Approved
9.10 S2-2202917 P-CR Approval 23.700-71: Solution on LCS architecture enhancement for PNI-NPN. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203297 Jinguo(ZTE) comments and provide r01
Stephen (Qualcomm) has a few questions
Runze (Huawei) replies to Stephen(Qualcomm), and propose r02.
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r02
Richard (Ericsson) agree on r02
==== Comments Deadline ====
Revised
9.10 S2-2203297 P-CR Approval 23.700-71: Solution on LCS architecture enhancement for PNI-NPN. Huawei, HiSilicon Rel-18 Revision of S2-2202917r02. Approved Approved
9.10 - - - KI#3 solutions - - Docs:=6 -
9.10 S2-2202674 P-CR Approval 23.700-71: FS_eLCS_Ph3 New Solution to KI#3. ZTE Rel-18 Approved Hank (vivo) asks for clarifications.
Jinguo(ZTE) replies to Hank (vivo)
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.10 S2-2202635 P-CR Approval 23.700-71: New solution on LMF selection based on client or AF identifier. China Mobile Rel-18 r01 agreed. Revised to S2-2203298 Stephen (Qualcomm) comments that most of the solution is not new
Aihua(CMCC) provides r01.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01
==== Comments Deadline ====
Revised
9.10 S2-2203298 P-CR Approval 23.700-71: New solution on LMF selection based on client or AF identifier. China Mobile Rel-18 Revision of S2-2202635r01. Approved Approved
9.10 S2-2202622 P-CR Approval 23.700-71: KI#3, New Sol: LMF selection based on GMLC service area. CATT Rel-18 r01 agreed. Revised to S2-2203299 Stephen (Qualcomm) provides an r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.10 S2-2203299 P-CR Approval 23.700-71: KI#3, New Sol: LMF selection based on GMLC service area. CATT Rel-18 Revision of S2-2202622r01. Approved Approved
9.10 S2-2202918 P-CR Approval 23.700-71: Solution on local LMF and GMLC selection. Huawei, HiSilicon Rel-18 Approved Approved
9.10 - - - KI#4 solutions - - Docs:=8 -
9.10 S2-2202623 P-CR Approval 23.700-71: KI#4, New Sol: Interaction between location service and NWDAF based on existing architecture. CATT Rel-18 r02 agreed. Revised to S2-2203300 Dimitris (Lenovo) has a question for clarification
Yunjing (CATT) replies to Dimitris (Lenovo).
Hank (vivo) asks for clarifications.
Hank (vivo) can live with r01.
Yunjing (CATT) provides r01.
Stephen (Qualcomm) comments
Yunjing (CATT) provides r02.
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r02
==== Comments Deadline ====
Revised
9.10 S2-2203300 P-CR Approval 23.700-71: KI#4, New Sol: Interaction between location service and NWDAF based on existing architecture. CATT Rel-18 Revision of S2-2202623r02. Approved Approved
9.10 S2-2202934 P-CR Approval 23.700-71: FS_eLCS_Ph3 TR Solution to KI#4. Nokia, Nokia Shanghai Bell Rel-18 r02 + EN proposed by Samsung: Editor's Note: Whether to use new Analytics ID or reuse existing one is FFS and may need to be decided in coordination with eNA_ph3 revised to S2-2203301 Dimitris (Lenovo) has questions for clarification
Cai Simon (Nokia) clarifies to Dimitris (Lenovo)
Dimitris (Lenovo) provides additional comments
Hank (vivo) asks for a clarification.
David (Samsung) expresses concern with this proposal.
Cai Simon (Nokia) clarifies to Hank (vivo)
Stephen (Qualcomm) comments
Cai Simon (Nokia) clarifies and provides r01
David (Samsung) reiterates concerns since I don't see any comments addressed in r01 and they haven't been replied to.
Hank (vivo) asks one question on r01.
Cai Simon (Nokia) provides r02
==== Revisions Deadline ====
Stephen (Qualcomm) replies to Cai Simon (Nokia)
Cai Simon (Nokia) clarifies the comments
Cai Simon (Nokia) clarifies further comments
David (Samsung) requests an EN to cover the strong dependencies with eNA_ph3.
Cai Simon (Nokia) confirms the EN already covers the comment
David (Samsung) does not think the existing EN addresses the comment.
Cai Simon (Nokia) agrees with the new EN text
==== Comments Deadline ====
Revised
9.10 S2-2203301 P-CR Approval 23.700-71: FS_eLCS_Ph3 TR Solution to KI#4. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202934r02 + changes. Approved Approved
9.10 S2-2202441 P-CR Approval 23.700-71: Solution for KI#4: Supporting analytics for location accuracy. Lenovo Rel-18 r01 agreed. Revised to S2-2203302 Yunjing (CATT) comments
Stephen (Qualcomm) comments
Dimitris (Lenovo) responds
Cai Simon (Nokia) asks questions
Dimitris (Lenovo) responds to Hank (Vivo)
Hank (vivo) has a concern about this solution.
Dimitris (Lenovo) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.10 S2-2203302 P-CR Approval 23.700-71: Solution for KI#4: Supporting analytics for location accuracy. Lenovo Rel-18 Revision of S2-2202441r01. Approved Approved
9.10 S2-2202613 P-CR Approval 23.700-71: New Solution for KI#4: Architecture enhancement for the interaction between LCS and NWDAF. Vivo Rel-18 r01 agreed. Revised to S2-2203303 Stephen (Qualcomm) comments
Hank (vivo) replies to Stephen (Qualcomm) and provides r01.
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r01
==== Comments Deadline ====
Revised
9.10 S2-2203303 P-CR Approval 23.700-71: New Solution for KI#4: Architecture enhancement for the interaction between LCS and NWDAF . Vivo Rel-18 Revision of S2-2202613r01. Approved Approved
9.10 - - - KI#5 solutions - - Docs:=1 -
9.10 S2-2202437 P-CR Approval 23.700-71: Solution for KI#5: Assistance data provisioning for low power high accuracy GNSS positioning. Huawei, HiSilicon Rel-18 This was postponed. Richard (Ericsson) object to the pCR
Guanglei (Huawei) replies to Richard (Ericsson) and provides r01
==== Revisions Deadline ====
Richard (Ericsson) object to r00 and r01
Guanglei (Huawei) replies to Richard (Ericsson), this solution has impacts on both RAN and SA2, an EN is added to clarify it is RAN to decide whether to support this solution, why it cannot be approved in the TR phase?
Richard (Ericsson) answering to Guanglei (Huawei)
Guanglei (Huawei) asking Richard (Ericsson), do you mean if a solution has impacts on LMF or other 5GC functionality, but if it re-uses existing procedures, then we can say there are no SA2 impacts?
Guanglei (Huawei) ask for CC#3
==== Comments Deadline ====
Postponed
9.10 - - - KI#6 solutions - - Docs:=2 -
9.10 S2-2202624 P-CR Approval 23.700-71: KI#6, New Sol: Unawareness positioning. CATT Rel-18 r01 agreed. Revised to S2-2203304 Stephen (Qualcomm) comments that the solution needs more work and development
Yunjing (CATT) replies to Stephen (Qualcomm).
Stephen (Qualcomm) replies to Yunjing (CATT)
Yunjing (CATT) replies to Stephen (Qualcomm) and provides r01
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r01
==== Comments Deadline ====
Revised
9.10 S2-2203304 P-CR Approval 23.700-71: KI#6, New Sol: Unawareness positioning. CATT Rel-18 Revision of S2-2202624r01. Approved Approved
9.10 - - - KI#7 solutions - - Docs:=5 -
9.10 S2-2202730 P-CR Approval 23.700-71: Solution for KI#7: Support of Positioning Reference Units and Reference UEs. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203305 Yunjing (CATT) provides questions for clarification.
Cai Simon (Nokia) provides comments
Runze (Huawei) replied to Yunjing (CATT).
Runze (Huawei) thanks Simon for the clarification.
David (Samsung) provides comments raised in S2-2202180 by companies which, if enforced, may be applicable to S2-2202730.
Runze (Huawei) proposes r01
==== Revisions Deadline ====
David (Samsung) comments on r01.
Runze (Huawei) replies to David (Samsung).
Cai Simon (Nokia) agrees with Runze's proposal to remove 'reference UE' from the TR key issue description.
David (Samsung) shares views with Runze (Huawei).
==== Comments Deadline ====
Revised
9.10 S2-2203305 P-CR Approval 23.700-71: Solution for KI#7: Support of Positioning Reference Units and Reference UEs. Huawei, HiSilicon Rel-18 Revision of S2-2202730r01. Approved Approved
9.10 S2-2202625 P-CR Approval 23.700-71: KI#7, New Sol: solution to support PRU registration and utilization. CATT Rel-18 Approved Approved
9.10 S2-2202180 P-CR Approval 23.700-71: KI#7: New Solution on Support for 5GS Localization via Reference UE. Samsung Rel-18 r01 agreed. Revised to S2-2203306 Stephen (Qualcomm) comments
David (Samsung) replies to Qualcomm.
Yunjing (CATT) provides comments.
Cai Simon (Nokia) supports Stephen (Qualcomm)
David (Samsung) replies to CATT and provides r01.
David (Samsung) replies to Nokia.
Stephen (Qualcomm) comments again that this seems a solution applicable to agenda item 9.20
Cai Simon (Nokia) clarifies to David (Samsung)
David (Samsung) replies to Nokia, Qualcomm.
==== Revisions Deadline ====
Stephen (Qualcomm) reiterates that this is a solution applicable to agenda item 9.20
David (Samsung) replies to Stephen, suggests to add an EN for this meeting.
Runze (Huawei) shares the same view as Stephen (Qualcomm).
==== Comments Deadline ====
Revised
9.10 S2-2203306 P-CR Approval 23.700-71: KI#7: New Solution on Support for 5GS Localization via Reference UE. Samsung Rel-18 Revision of S2-2202180r01. Approved Approved
9.10 - - - KI#8 solutions - - Docs:=1 -
9.10 S2-2202919 P-CR Approval 23.700-71: Solution on local LMF and GMLC selection. Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
9.10 - - - KI#9 solutions - - Docs:=2 -
9.10 S2-2202181 P-CR Approval 23.700-71: KI#9, 4: New Solution on Location Verification for Satellite Access assisted by NWDAF analytics. Samsung Rel-18 r00 + changes agreed. Revised to S2-2203601. Runze (Huawei) corrected the mail subject to S2-2202181
David (Samsung) replies to Huawei
Stephen (Qualcomm) comments
David (Samsung) replies to Qualcomm
==== Revisions Deadline ====
Runze (Huawei) replies to David (Samsung), and suggest to include an EN reflecting the comment from Qualcomm and Huawei
==== Comments Deadline ====
Revised
9.10 S2-2203601 P-CR Approval 23.700-71: KI#9, 4: New Solution on Location Verification for Satellite Access assisted by NWDAF analytics. Samsung Rel-18 Revision of S2-2202181r00 + changes. Approved Approved
9.11 - - - Study on Edge Computing Phase 2 (FS_EDGE_Ph2) - - Docs:=78 -
9.11 S2-2202799 LS In Action LS from 5GAA WG4: LS on UPF selection based on DNAI 5GAA WG4 (5GAA_S-220022) Rel-18 Postponed Patrice (Huawei, rapporteur) proposes to postpone this LS, as it has action for SA2, but no reply yet.
==== Revisions Deadline ====
Postponed
9.11 - - - KI#1 LS - - Docs:=4 -
9.11 S2-2201968 LS In Action LS on FS_eEDGEAPP Solution for Support of Roaming UEs SA WG6 (S6-220429) Rel-18 Responses drafted in S2-2202869, S2-2202884. Final response in S2-2203479 Replied to
9.11 S2-2202869 LS OUT Approval [DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of Roaming UEs China Mobile Rel-18 Response to S2-2201968. Merged into S2-2203479 Mike (InterDigital) proposes that this paper be marked as merged into S2-2202884
Dan (China Mobile) is OK for merge
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.11 S2-2202884 LS OUT Approval [DRAFT] Reply LS on FS_eEDGEAPP Solution for Support of Roaming UEs InterDigital Inc. Rel-18 Response to S2-2201968. r01 agreed. Revised to S2-2203479, merging S2-2202869 Laurent (Nokia): provides r01
Mike (InterDigital) is ok with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203479 LS OUT Approval Reply LS on FS_eEDGEAPP Solution for Support of Roaming UEs SA WG2 Rel-18 Revision of S2-2202884r01, merging S2-2202869. Approved Approved
9.11 - - - KI#1 solutions (HR) - - Docs:=10 -
9.11 S2-2202082 P-CR Approval 23.700-48: KI#1: Solution for EAS discovery in a VPLMN when roaming. China Mobile Rel-18 r02 agreed. Revised to S2-2203480 Magnus H (Ericsson) ask some questions
Laurent (Nokia): Comments
Laurent (Nokia): answers
Laurent (Nokia): my previous Comments REQUIRE change to the Tdoc
Dario (Qualcomm) asks questions for clarification
Dan (China Mobile) reply the comment
Dan(China Mobile) reply
Dan(China Mobile) provide r01 to reflect the previous comment
Laurent (Nokia): provides r02 and objects to any previous version (MUST have EN )
Dan (China Mobile) ok with r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203480 P-CR Approval 23.700-48: KI#1: Solution for EAS discovery in a VPLMN when roaming. China Mobile Rel-18 Revision of S2-2202082r02. Approved Approved
9.11 S2-2202266 P-CR Approval 23.700-48: Solution for Key Issue #1: Home Routed Session Breakout in VPLMN. Samsung Rel-18 r03 agreed. Revised to S2-2203481 Hui (Huawei) asks for clarification
Jicheol (Samsung) responses.
Hui (Huawei) clarify the question
Laurent (Nokia): Comments requiring EN
Jicheol provides r01.
Tingfang Tang (Lenovo) comments.
Laurent (Nokia): provides r02 and objects to any previous version (MUST have EN )
Jicheol (Samsung) provides r03. (with accepting all the Nokia EN's)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203481 P-CR Approval 23.700-48: Solution for Key Issue #1: Home Routed Session Breakout in VPLMN. Samsung Rel-18 Revision of S2-2202266r03. Approved Approved
9.11 S2-2202276 P-CR Approval 23.700-48: KI #1, Solution: EAS (re)discovery procedure in roaming scenario. China Unicom Rel-18 r05 agreed. Revised to S2-2203482 Magnus H (Ericsson) asks some questions
Laurent (Nokia): Comments requiring EN to be added
Tianqi (China Unicom) replies to Magnus H (Ericsson).
Dario (Qualcomm) asks question
Tianqi (China Unicom) replies to Laurent (Nokia) and provides r01.
Tianqi (China Unicom) replies to Dario (Qualcomm).
Tianqi (China Unicom) replies to Tingfang Tang (Lenovo).
Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson) wants an EN
Laurent (Nokia): provides r02 and objects to any previous version (MUST have EN)
Tianqi (China Unicom) replies to Laurent (Nokia).
Tianqi (China Unicom) provides r03 based on r02 with some editorial changes.
Tianqi (China Unicom) replies to Laurent (Nokia) and provides r01. This email is resent because of incorrect title.
Tingfang Tang (Lenovo) comments and provides r01.
Tingfang Tang (Lenovo) comments and provides r04.
Tianqi (China Unicom) replies to Tingfang Tang (Lenovo) and provides r05 based on r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203482 P-CR Approval 23.700-48: KI #1, Solution: EAS (re)discovery procedure in roaming scenario. China Unicom Rel-18 Revision of S2-2202276r05. Approved Approved
9.11 S2-2202402 P-CR Approval 23.700-48: Solution for KI#1: EAS discovery in VPLMN via HR PDU Session. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203483 Magnus H (Ericsson) comments and asks questions.
Laurent (Nokia): Comments requiring EN (Editor's Note)
Dario (Qualcomm) asks questions for clarification.
Hui (Huawei) replies to Magnus H (Ericsson).
Tingfang Tang (Lenovo) comments.
Hui (Huawei) replies to Dario.
Hui (Huawei) provides r01 and replies to Laurent.
Hui (Huawei) replies to Tingfang and explain the basic idea of the solution.
Laurent (Nokia): provides r02
Hui (Huawei)asks for clarification
Hui (Huawei) provides r03
==== Revisions Deadline ====
Laurent (Nokia): objects to R00+R01. OK to have R03 with EN rewritten to Editor's Note: it is FFS whether procedures defined for I-SMF may be used for this call flow e.g. in step 15
Hui (Huawei) is fine with Laurent's proposal on 'r03 + EN in 6.X.2 rewritten to 'Editor's Note: it is FFS whether procedures defined for I-SMF may be used for this call flow e.g. in step 15'
==== Comments Deadline ====
Revised
9.11 S2-2203483 P-CR Approval 23.700-48: Solution for KI#1: EAS discovery in VPLMN via HR PDU Session. Huawei, HiSilicon Rel-18 Revision of S2-2202402r03. Approved Approved
9.11 S2-2202566 P-CR Approval 23.700-48: KI#1, New solution - Accessing V-EHE via HR PDU session. CATT Rel-18 r03 agreed. Revised to S2-2203484 Dario (Qualcomm) asks about difference w/ 2266 and potential merge.
Yuan Tao (CATT) responds to Dario (Qualcomm) and provides r01.
Magnus H (Ericsson) comments
Tingfang Tang (Lenovo) comments.
Yuan Tao (CATT) replies.
Yuan Tao (CATT) provides r02.
Yuan Tao (CATT) provides r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203484 P-CR Approval 23.700-48: KI#1, New solution - Accessing V-EHE via HR PDU session . CATT Rel-18 Revision of S2-2202566r03. Approved Approved
9.11 - - - KI#1 solutions (LBO) - - Docs:=10 -
9.11 S2-2202204 P-CR Approval 23.700-48: New solution for WT1: URSP solution to support roamers access to EHE in a VPLMN. Nokia, Nokia Shanghai Bell Rel-18 Revision of (Postponed) S2-2201084. r04 agreed. Revised to S2-2203603. Mike (InterDigital) comments
Magnus H (Ericsson) comments
Laurent (Nokia): provides r01
Mike (InterDigital) comments and questions
Dario (Qualcomm) comments that this type of proposal should be discussed in FS_eUEPO
Mike (InterDigital) comments that this solutions address an Edge KI and should be discussed within FS_EDGE_Ph2.
Patrice (Huawei) comments.
Laurent (Nokia): provides r02
Patrice (Huawei) comments further.
Changhong (Intel) asks to note this paper and discuss this solution in AI#9.22 at next meeting.
Yang (OPPO) supports to note it or move it to eUEPO TR.
Laurent (Nokia): provides R03
Mike (InterDigital) comments and is ok with r03.
Patrice (Huawei) confirms that this is in the scope of FS_EDGE_Ph2 to discuss this, and requests a minor change to r03.
Dario (Qualcomm) is not OK to capture this solution in this TR at this stage due to the ongoing UEPO work.
Laurent (Nokia): provides r04
Patrice (Huawei) thanks Laurent (Nokia), is fine with r04.
Tingfang Tang (Lenovo) supports discuss the URSP related solution for KI#1 for FS_EDGE_Ph2 .
==== Revisions Deadline ====
Changhong (Intel) further comments and objects to document this solution in FS_EDGE_Ph2 TR.
Dario (Qualcomm) explains why we should discuss this in UEPO first.
Changhong (Intel) clarifies that the same solution in S2-2202454 from Nokia was submitted to FS_eUEPO, we should discuss the URSP aspect for roaming support in FS_eUEPO not here since this solution is not specific to edge computing.
Patrice (Huawei, rapporteur) objects to Changhong's (INTEL) procedural objection. FS_UEPO cannot resolve the issues specific to FS_EDGE_Ph2. Worse, forcing to move these solutions to UEPO will pollute UEPO precious few TUs with EDGE-related discussions, especially in F2F meetings. Solution evaluation and conclusion will not be possible for delegates that are not able to follow UEPO discussions, esp. in F2F meetings, when they are focused on EDGE related topics.
==== Comments Deadline ====
Jicheol (Samsung) shares a view from Intel and others.
Hui(Huawei) proposes a way forward for the open solutions in EC.
Changhong (Intel) proposes a new NOTE proposal based on r04.
Hui (Huawei) fine with the NOTE with an editorial change..
Revised
9.11 S2-2203603 P-CR Approval 23.700-48: New solution for WT1: URSP solution to support roamers access to EHE in a VPLMN. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202204r04. Approved Approved
9.11 S2-2202252 P-CR Approval 23.700-48: KI#1: New Solution - Using URSP Rules to Establish an LBO PDU Session. InterDigital Inc. Rel-18 r02 + changes agreed. Revised to S2-2203604. Hui (Huawei) provides comments
Laurent (Nokia): same Comment as Hui
Mike (InterDigital) replies to Hui and Laurent and provides r01
Dario (Qualcomm) comments that this type of solutions should be discussed in FS_eUEPO
Mike (InterDigital) comments that this solutions address an Edge KI and should be discussed within FS_EDGE_Ph2.
Magnus H (Ericsson) asks some questions
Huazhang(vivo) ask some questions to Mike (InterDigital)
Mike (InterDigital) replies and provides r02
Changhong (Intel) asks to note this paper and discuss this solution in AI#9.22 at next meeting.
Yang (OPPO) raise comments and suggest to add an EN
Mike (InterDigital) responds and comments that 'these late proposals to note papers and resubmit them under different AI's at the next meeting is an inefficient use of TUs' and provides r03
Yang (OPPO) comments
Dario (Qualcomm) is not OK to capture this solution in this TR at this stage due to the ongoing UEPO work.
Patrice (Huawei) would appreciate if procedural objections could be lifted, as the scope of KI#1 of FS_EDGE_Ph2 is not the same as the scope of KI#1 of FS_UEPO, therefore UEPO TR is not appropriate to discuss content targetting FS_EDGE_Ph2 study.
Mike (InterDigital) proposes to address this issue on CC#2 and asks Dario (Qualcomm) to clarify his position
==== Revisions Deadline ====
Mike (InterDigital) replies that we need guidance on how to handle this issue moving forward
Changhong (Intel) replies to Michael.
Mike (InterDigital) replies to Changhong (Intel) and asks questions
Changhong (Intel) insists that we should discuss the URSP aspect for roaming support in FS_eUEPO not here since this solution is not specific to edge computing.
Dario (Qualcomm) replies to Mike.
Mike (InterDigital) replies to Dario
Hui (Huawei) provides concerns on pending the EC solution to UEPO key issue.
Yang (OPPO) comments to the overlap of URSP work
Patrice (Huawei, rapporteur) objects to Changhong's (INTEL) et al procedural objection. FS_UEPO cannot resolve the issues specific to FS_EDGE_Ph2. Worse, forcing to move these solutions to UEPO will pollute UEPO precious few TUs with EDGE-related discussions, especially in F2F meetings. Solution evaluation and conclusion will not be possible for delegates that are not able to follow UEPO discussions, esp. in F2F meetings, when they are focused on EDGE related topics.
Mike (InterDigital) asks if companies can re-consider their positions given that no one has argued that this solution does not address Edge Key Issue #1 and asks if we can we agree to r03.
==== Comments Deadline ====
Changhong (Intel) proposes a new NOTE based on r03.
Mike (InterDigital) is fine with the note. Proposes to agree to r03 with the following change: the existing note is change to say 'NOTE: Before concluding this solution for normative work, alignment check with FS_eUEPO shall be done in order to avoid any conflict with the conclusion of KI#1 in TR 23.785[xx]. Final decision on generic URSP enhancement for supporting LBO roaming case should be made within FS_eUEPO study.'.
Hui (Huawei) fine with the NOTE with an editorial change..
Revised
9.11 S2-2203604 P-CR Approval 23.700-48: KI#1: New Solution - Using URSP Rules to Establish an LBO PDU Session. InterDigital Inc. Rel-18 Revision of S2-2202252r02 + changes. Approved Approved
9.11 S2-2202253 P-CR Approval 23.700-48: KI#1: New Solution - V-ECS Discovery during Steering of Roaming. InterDigital Inc. Rel-18 r02 agreed. Revised to S2-2203485 Laurent (Nokia): Comments
Mike (InterDigital) provides r01
Dario (Qualcomm) comments.
Mike (InterDigital) replies
Hyesung (Samsung) asks questions.
Magnus H (Ericsson) comments
Hui (Huawei) share same comment in previous emails.
Huazhang (vivo) replies to Mike
Mike (InterDigital) replies to Magnus and Laurent.
Mike (InterDigital) replies and provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203485 P-CR Approval 23.700-48: KI#1: New Solution - V-ECS Discovery during Steering of Roaming. InterDigital Inc. Rel-18 Revision of S2-2202253r02. Approved Approved
9.11 S2-2202256 P-CR Approval 23.700-48: KI#1 PDU Session configuration from EASDF. Sony Rel-18 r04 agreed. Revised to S2-2203486 Hui (Huawei) asks for clarification
Mike (InterDigital) asks a question
Svante (Sony) provides answer to question
Hyesung (Samsung) asks questions.
Svante (Sony) provides answer to questions
Laurent (Nokia): Comments requiring updates
Magnus (Ericsson) provides comments
Dario (Qualcomm) provides questions/comments that require a pCR update.
Tingfang Tang (Lenovo) comments.
Svante (Sony) provides r01 and answers to questions.
Hyesung (Samsung) asks clarification.
Svante (Sony) respond to question..
Svante (Sony) provide comments and answers.
Laurent (Nokia): provides r02 and objects to any previous version
Svante (Sony) provide r03.
Tingfang Tang (Lenovo) comments and provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203486 P-CR Approval 23.700-48: KI#1 PDU Session configuration from EASDF. Sony Rel-18 Revision of S2-2202256r04. Approved Approved
9.11 S2-2202401 P-CR Approval 23.700-48: Solution on KI#1: Accessing EHE in VPLMN via LBO PDU Session. Huawei, HiSilicon Rel-18 r01 + changes agreed. Revised to S2-2203605. Hui (Huawei) replies
Mike (InterDigital) comments
Mike (InterDigital) replies
Dario (Qualcomm) comments that this type of solutions should be discussed in FS_eUEPO
Mike (InterDigital) comments that this solutions address an Edge KI and should be discussed within FS_EDGE_Ph2.
Hui(Huawei) supports Mike's view and believe this solution should be discussed in EC.
Laurent (Nokia): supports Hui(Huawei) and Mike's view and believe this solution should be discussed in EC.
Changhong (Intel) asks to note this paper and discuss this solution in AI#9.22 at next meeting.
Hui (Huawei) provides r01 to address Yang's concern.
Hui (Huawei) replies to Yang
Yang (OPPO) replies to Hui
Hui (Huawei) disagree with only discussing this solution in AI#9.22.
Yang (OPPO) supports Intel's proposal to note it
Dario (Qualcomm) is not OK to capture this solution in this TR at this stage due to the ongoing UEPO work.
Hui (Huawei) don't think the solution can be purely reused.
Tingfang Tang (Lenovo) supports discuss the URSP related solution for KI#1 for FS_EDGE_Ph2 .
Patrice (Huawei, rapporteur) would appreciate if procedural objections could be lifted, as the scope of KI#1 of FS_EDGE_Ph2 is not the same as the scope of KI#1 of FS_UEPO, therefore UEPO TR is not appropriate to discuss content targetting FS_EDGE_Ph2 study.
==== Revisions Deadline ====
Changhong (Intel) clarifies that the same solution in S2-2202557 from Huawei was submitted to FS_eUEPO, we should discuss the URSP aspect for roaming support in FS_eUEPO not here since this solution is not specific to edge computing.
Hui (Huawei) clarifies that the solution in S2-2202557 is different.
Patrice (Huawei, rapporteur) objects to Changhong's (INTEL) procedural objection. FS_UEPO cannot resolve the issues specific to FS_EDGE_Ph2. Worse, forcing to move these solutions to UEPO will pollute UEPO precious few TUs with EDGE-related discussions, especially in F2F meetings. Solution evaluation and conclusion will not be possible for delegates that are not able to follow UEPO discussions, esp. in F2F meetings, when they are focused on EDGE related topics.
==== Comments Deadline ====
Changhong (Intel) proposes a new NOTE proposal based on r01.
Hui (Huawei) fine with r01+ the NOTE with an editorial change..
Yang (OPPO) is fine to agree it with the Note
Revised
9.11 S2-2203605 P-CR Approval 23.700-48: Solution on KI#1: Accessing EHE in VPLMN via LBO PDU Session. Huawei, HiSilicon Rel-18 Revision of S2-2202401r01 + changes. Approved Approved
9.11 - - - KI#2 KI update - - Docs:=3 -
9.11 S2-2202403 P-CR Approval 23.700-48: Update on KI#2: Add Use Cases, Scenarios and Assumptions. Huawei, HiSilicon Rel-18 r10 agreed. Revised to S2-2203487, merging S2-2202097 Magnus O (Ericsson) asks a couple of questions
Dario (Qualcomm) asks question on justification of use case.
Hui (Huawei) provides r01 and replies to Dario and Magnus
Magnus (Ericsson) provides follow up comments
Hui(Huawei) replies to Magnus and provides r02
Magnus (Ericsson) provides further comments
Hui (Huawei) proposes a change
Magnus (Ericsson) provides r03
Huawei (Huawei) asks question on the comments.
Magnus (Ericsson) provides more comments
Shubhranshu (Nokia) comments and provides r05
Magnus (Ericsson) provides r06
Hui (Huawei) provides r07
Magnus (Ericsson) provides r08
Hui (Huawei) proposes r09
Magnus (Ericsson) provides r10
Dan (China Mobile) suggest to consider r09 as a compromized way
Hui (Huawei) fine with both r09 and r10
==== Revisions Deadline ====
Magnus (Ericsson)is ok with r10 and objects to earlier revisions of the doc.
==== Comments Deadline ====
Revised
9.11 S2-2203487 P-CR Approval 23.700-48: Update on KI#2: Add Use Cases, Scenarios and Assumptions. Huawei, HiSilicon Rel-18 Revision of S2-2202403r10, merging S2-2202097. Approved Approved
9.11 S2-2202097 P-CR Approval 23.700-48: Use Cases for to KI#2. Ericsson Rel-18 Merged into S2-2203487 Patrice (Huawei) agrees with Shubhranshu (Nokia) and wonders if this is really relevant for EC work, proposes to note.
Hui (Huawei) comments
Shubhranshu (Nokia) comments
Magnus H (Ericsson) answers
Hui (Huawei) proposes to merge 'rate adaptation' part into S2-2202403.
Magnus H (Ericsson) comments
Shubhranshu (Nokia) asks for clarificaiton
==== Revisions Deadline ====
Hui (Huawei) suggests to consider this paper as merged into S2-2202403.
==== Comments Deadline ====
Merged
9.11 - - - KI#2 solutions - - Docs:=8 -
9.11 S2-2202083 P-CR Approval 23.700-48: KI#2: solution for efficient network exposure of RAN related information. China Mobile Rel-18 Merged into S2-2203488 Hui (Huawei) suggests to merge this paper into S2-2202404.
Dan (China Mobile) suggest this paper is merged into S2-2202404
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.11 S2-2202404 P-CR Approval 23.700-48: Solution for KI#2: Exposure of network congestion information. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2203488, merging S2-2202083 and S2-2202414 Magnus H (Ericsson) asks some questions
Hui (Huawei) provides r01 and response to Magnus
Dario (Qualcomm) asks questions.
Hui (Huawei) provides r02 and replies.
Hui (Huawei) asks for clarification on the EN
Magnus H (Ericsson) wants an EN
Hui (Huawei) provides r03.
Hui (Huawei) replies to Magnus H (Ericsson).
Magnus H (Ericsson) wants an EN.
Magnus H (Ericsson) comments
Hui (Huawei) provides r04.
Shubhranshu (Nokia) asks for clarification
Hui (Huawei) provides r05
==== Revisions Deadline ====
Magnus (Ericsson) has a problem with r05 (also included in r02-r04). Propose to go with r05 and removing the second sentence in NOTE 1.
Hui (Huawei) fine with Magnus' proposal and asks to discuss in CC#2.
Magnus (Ericsson) object to all revisions but is ok with r05 with the removal of the last sentence in NOTE 1 in section 6.x.0.
Hui (Huawei) fine with Magnus's proposal on 'r05 with the removal of the last sentence in NOTE 1 in section 6.x.0.'
==== Comments Deadline ====
Revised
9.11 S2-2203488 P-CR Approval 23.700-48: Solution for KI#2: Exposure of network congestion information. Huawei, HiSilicon, Intel, China Mobile, vivo Rel-18 Revision of S2-2202404r05, merging S2-2202083 and S2-2202414. Approved Approved
9.11 S2-2202414 P-CR Approval 23.700-48: KI#2, New Solution: Network Information Provisioning from NG-RAN to 5GC via User Plane Intel Rel-18 Merged into S2-2203488 Hui (Huawei) suggests to merge this paper into S2-2202404.
Changhong (Intel) is fine to merge.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.11 S2-2202707 P-CR Approval 23.700-48: Solution for KI#2: efficient exposure of RAN information. Vivo Rel-18 r01 agreed. Revised to S2-2203489 Magnus H (Ericsson) ask some questions
Dario (Qualcomm) asks question and provides comment.
Xiaowan (vivo) replies to the questions from Magnus H (Ericsson) Dario (Qualcomm)
Magnus H (Ericsson) comments and to add EN or merge with 2404
Xiaowan(vivo) replies to Magnus H (Ericsson) and provide r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203489 P-CR Approval 23.700-48: Solution for KI#2: efficient exposure of RAN information. Vivo Rel-18 Revision of S2-2202707r01. Approved Approved
9.11 S2-2202982 P-CR Approval 23.700-48: Solution to KI#2: Fast and efficient network exposure improvements. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203490 Hui (Huawei) asks for questions
Shubhranshu (Nokia) responds
Dario (Qualcomm) asks question
Dan (China Mobile) provides comments
Hui (Huawei) shares same comments of Magnus
Magnus (Ericsson) provides comments
Shubhranshu (Nokia) provides r01
Magnus (Ericsson) comments
Shubhranshu (Nokia) responds and provides r02
Hui(Huawei) requests a revision before accept the paper.
Magnus (Ericsson) provides additional comments
Shubhranshu (Nokia) responds and provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203490 P-CR Approval 23.700-48: Solution to KI#2: Fast and efficient network exposure improvements. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202982r03. Approved Approved
9.11 - - - KI#4 KI update - - Docs:=1 -
9.11 S2-2202078 P-CR Approval 23.700-48: Update KI#4 Influencing UPF and EAS (re)location for collections of UEs. NTT DOCOMO Rel-18 Approved Shubhranshu (Nokia) asks for clarification
Tugce (NTT DOCOMO) responds.
Xinpeng(Huawei) ask question for clarification.
Tugce (NTT DOCOMO) responds to Xinpeng(Huawei).
Shubhranshu (Nokia) comments
==== Revisions Deadline ====
Tugce (NTT DOCOMO) responds to Shubhranshu (Nokia).
==== Comments Deadline ====
Approved
9.11 - - - KI#4 solutions - - Docs:=12 -
9.11 S2-2202076 P-CR Approval 23.700-48: New Solution FS_EDGE KI#4 Group Management. NTT DOCOMO Rel-18 r03 agreed. Revised to S2-2203491 Tingfang Tang (Lenovo) comments.
Jari (NTT DOCOMO) responds to Tingfang Tang
Xinpeng(Huawei) comments.
Jari (NTT DOCOMO) responds to Xinpeng
Jari (NTT DOCOMO) provides r01
Xinpeng(Huawei) provides r02.
Jari (NTT DOCOMO) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203491 P-CR Approval 23.700-48: New Solution FS_EDGE KI#4 Group Management. NTT DOCOMO Rel-18 Revision of S2-2202076r03. Approved Approved
9.11 S2-2202077 P-CR Approval 23.700-48: New Solution FS_EDGE KI#4 Selection of Common DNAI. NTT DOCOMO Rel-18 r04 agreed. Revised to S2-2203492 Tingfang Tang (Lenovo) comments.
Jari (NTT DOCOMO) responds to Tingfang Tang
Xinpeng(Huawei) comments.
Jari (NTT DOCOMO) responds to Magnus H
Magnus H (Ericsson) ask some questions
Patrice (Huawei) asks for clarification.
Jari (NTT DOCOMO) responds to Patrice
Patrice (Huawei) thanks Jari for his answers, and would kindly request an update with these clarifications.
Xinpeng(Huawei) provides r01 and comments.
Jari (NTT DOCOMO) provides r03
Xinpeng(Huawei) is ok with r03.
Tingfang Tang (Lenovo) comments and provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203492 P-CR Approval 23.700-48: New Solution FS_EDGE KI#4 Selection of Common DNAI. NTT DOCOMO Rel-18 Revision of S2-2202077r04. Approved Approved
9.11 S2-2202373 P-CR Approval 23.700-48: Solution for Selecting the same EAS/DNAI for collection of UEs KI#4. Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2203493 Jari (NTT DOCOMO) comments
Yuan Tao (CATT) asks for clarification
Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson) ask questions
Xinpeng(Huawei) replies to Tingfang Tang (Lenovo) .
Xinpeng(Huawei) replies to Yuan Tao (CATT).
Xinpeng(Huawei) replies Jari (NTT DOCOMO) .
Xinpeng(Huawei) replies to Magnus H (Ericsson).
Jari (NTT DOCOMO) provides r01
Yuan Tao (CATT) responds to Xinpeng(Huawei) .
Magnus H (Ericsson) wants updates and ask question
Xinpeng(Huawei) provides r02.
Jari (NTT DOCOMO) provides r03
Xinpeng(Huawei) provides r04, and disagree with r03.
Xinpeng(Huawei) replies to Jari (NTT DOCOMO) and provides r05.
Tingfang Tang (Lenovo) comments and provides r06.
==== Revisions Deadline ====
Xinpeng(Huawei) replies to jari(NTT DOCOMO)
Xinpeng(Huawei) replies to Jari(NTT DOCOMO).
==== Comments Deadline ====
Revised
9.11 S2-2203493 P-CR Approval 23.700-48: Solution for Selecting the same EAS/DNAI for collection of UEs KI#4. Huawei, HiSilicon Rel-18 Revision of S2-2202373r06. Approved Approved
9.11 S2-2202405 P-CR Approval 23.700-48: Solution for KI#4: Application layer EAS selection for collections of UEs. Huawei, HiSilicon Rel-18 Approved Tingfang Tang (Lenovo) comments.
Hui (Huawei) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.11 S2-2202473 P-CR Approval 23.700-48: Solution for the KI#4: Discovery of the same EAS for collections of UEs. Vivo Rel-18 r08 agreed. Revised to S2-2203494, merging S2-2202568 Jari (NTT DOCOMO) comments
Huazhang(vivo) replies to Jari (NTT DOCOMO)
Tingfang Tang (Lenovo) comments.
Huazhang(vivo) replies to Tingfang Tang (Lenovo)
Yuan Tao (CATT) merges S2-2202568 into 2202473 based on offline discussion, and provides r01.
Magnus H (Ericsson) ask some questions
Yuan Tao (CATT) responds to Magnus H (Ericsson)
Huazhang(vivo) replies to Magnus H (Ericsson)
Huazhang(vivo) provides r02 to add ENs to express the opinion from Magnus and Tingfang
Xinpeng(Huawei) comments.
Huazhang(vivo) provides r05 and reply Xinpeng(Huawei) and Magnus.
Xinpeng(Huawei) replies to Huazhang(vivo).
Magnus H (Ericsson) comments
Huazhang(vivo) provides r04 to reflect Tao Yuan (CATT) 's suggestions.
Yuan Tao (CATT) comments.
Huazhang (vivo) replies to Xinpeng(Huawei) , and provides r03
Patrice (Huawei) asks for revision marks in the next revision.
Huazhang(vivo) provides r06 and replies to Tingfang Tang (Lenovo) comments and Patrice(Huawei)
Xinpeng(Huawei) provides r07.
Huazhang(vivo) provides r08 based on Xinpeng(Huawei) 's r07 version, that only split the first changes of 6.X and second changes
==== Revisions Deadline ====
Yuan Tao (CATT) is ok with r08.
==== Comments Deadline ====
Revised
9.11 S2-2203494 P-CR Approval 23.700-48: Solution for the KI#4: Discovery of the same EAS for collections of UEs. Vivo, CATT Rel-18 Revision of S2-2202473r08, merging S2-2202568. Approved Approved
9.11 S2-2202568 P-CR Approval 23.700-48: KI#4, New solution - EAS discovery for a dynamic group. CATT Rel-18 Merged into S2-2203494 Patrice (Huawei, rapporteur) asks for confirmation that 2568 is merged in 2473.
Yuan Tao (CATT) confirms that 2568 is merged in 2473.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.11 S2-2202975 P-CR Approval 23.700-48: Solution to KI#4. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203495 Tingfang Tang (Lenovo) comments.
Magnus H (Ericsson) ask questions
Jari (NTT DOCOMO) proposes to merge with S2-2202076, comments.
Yuan Tao (CATT) comments.
Shubhranshu (Nokia) responds
Xinpeng(Huawei) comments.
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Magnus H (Ericsson) comments
Jari (NTT DOCOMO) comments
Xinpeng(Huawei) provides r01.
Xinpeng(Huawei) is fine with r02.
Shubhranshu (Nokia) comments
Shubhranshu (Nokia) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203495 P-CR Approval 23.700-48: Solution to KI#4. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202975r02. Approved Approved
9.11 - - - KI#5 KI update - - Docs:=2 -
9.11 S2-2202966 P-CR Approval 23.700-48: KI#5: Scenario for GSMA OPs federation. Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2203496 Magnus O (Ericsson) provides r01
Patrice (Huawei) comments, asks for update.
Dario (Qualcomm) provides r03 with co-signers
Dario (Qualcomm) provides r02
Magnus (Ericsson) asks a question
Patrice (Huawei) thanks Dario (Qualcomm) for the update.
Dario (Qualcomm) replies to Magnus.
Shubhranshu (Nokia) comments and provides r04
==== Revisions Deadline ====
Dario (Qualcomm) is OK with r04.
==== Comments Deadline ====
Revised
9.11 S2-2203496 P-CR Approval 23.700-48: KI#5: Scenario for GSMA OPs federation. Qualcomm Incorporated, Charter Communications, AT&T Rel-18 Revision of S2-2202966r04. Approved Approved
9.11 - - - KI#5 solutions - - Docs:=8 -
9.11 S2-2202255 P-CR Approval 23.700-48: KI#5 Solution with Global EASDF. Sony Rel-18 r01 agreed. Revised to S2-2203497 Dario (Qualcomm) ask question for clarification.
Svante (Sony) provide comment/answers.
Xinpeng(Huawei) ask question for clarification.
Shubhranshu (Nokia) comments
Svante (Sony) provides r01 and clarifications.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203497 P-CR Approval 23.700-48: KI#5 Solution with Global EASDF. Sony Rel-18 Revision of S2-2202255r01. Approved Approved
9.11 S2-2202406 P-CR Approval 23.700-48: Solution for KI #5: EAS discovery with different OPs. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203498 Dario (Qualcomm) asks clarification.
Hui (Huawei) replies and provides r01.
Magnus (Ericsson) comments
Shubhranshu (Nokia) comments
Hui (Huawei) replies to Shubhranshu
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203498 P-CR Approval 23.700-48: Solution for KI #5: EAS discovery with different OPs. Huawei, HiSilicon Rel-18 Revision of S2-2202406r01. Approved Approved
9.11 S2-2202967 P-CR Approval 23.700-48: KI#5: solutions for supporting federated Operator Platforms. Qualcomm Incorporated, Charter Communications Rel-18 Revision of S2-2201247. r03 agreed. Revised to S2-2203499 Dan(China Mobile) provide r01
Xinpeng(Huawei) asks for clarification.
Dario (Qualcomm) replies to Dan and Xinpeng and provides r02.
Xinpeng(Huawei) provides r03.
Dario (Qualcomm) is OK with r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203499 P-CR Approval 23.700-48: KI#5: solutions for supporting federated Operator Platforms . Qualcomm Incorporated, Charter Communications, AT&T Rel-18 Revision of S2-2202967r03. Approved Approved
9.11 S2-2202972 P-CR Approval 23.700-48: Solution to KI#5. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203500 Hyesung (Samsung) provides comments.
Dario (Qualcomm) asks a question for clarification.
Shubhranshu (Nokia) responds and provides r01
Xinpeng(Huawei) asks a question for clarification.
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Hyesung (Samsung) comments.
Dario (Qualcomm) provides r02
Shubhranshu (Nokia) comment
Xinpeng(Huawei) ask question for clarification.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.11 S2-2203500 P-CR Approval 23.700-48: Solution to KI#5. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202972r02. Approved Approved
9.11 - - - Documents exceeding TU Budget - - Docs:=19 -
9.11 S2-2202093 P-CR Approval 23.700-48: Solution to KI#3: Use of Internal Group ID and constrains in EDI. Ericsson Rel-18 Not Handled Not Handled
9.11 S2-2202205 P-CR Approval 23.700-48: New solution (WT5) for supporting offload policies to match more granular sets of UE(s). Nokia, Nokia Shanghai Bell Rel-18 Revision of (Postponed) S2-2201083. Not Handled Not Handled
9.11 S2-2202372 P-CR Approval 23.700-48: Solution for offload policy for finer granular set of UEs KI#3. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.11 S2-2202567 P-CR Approval 23.700-48: KI#3, New solution - AF requests offload policy for sets of UEs. CATT Rel-18 Not Handled Not Handled
9.11 S2-2202848 P-CR Approval 23.700-48: Solution for KI#3. Lenovo, Motorola Mobility Rel-18 Not Handled Not Handled
9.11 S2-2202092 P-CR Approval 23.700-48: Solution to KI#6: Controlling non-3GPP access of EC traffic via URSP and ATSSS. Ericsson Rel-18 Not Handled Not Handled
9.11 S2-2202096 P-CR Approval 23.700-48: Solution to KI#6: SMF indication of EC-related functionality. Ericsson Rel-18 Not Handled Not Handled
9.11 S2-2202250 P-CR Approval 23.700-48: KI#6: New Solution - Avoiding Switch Away Based on an Indication in the URSP. InterDigital Inc. Rel-18 Not Handled Not Handled
9.11 S2-2202251 P-CR Approval 23.700-48: KI#6: New Solution - Avoiding Switch Away Based on an SMF Indication. InterDigital Inc. Rel-18 Not Handled Not Handled
9.11 S2-2202254 P-CR Approval 23.700-48: KI#6 Solution with Application selected PDU Session Sony Rel-18 Not Handled Not Handled
9.11 S2-2202413 P-CR Approval 23.700-48: Solution for KI#6: EAS traffic switching away avoidance. Samsung Rel-18 Not Handled Not Handled
9.11 S2-2202472 P-CR Approval 23.700-48: Solution for the KI#6: Network based solutions for keeping EC traffic on 3GPP Access. Vivo Rel-18 Not Handled Not Handled
9.11 S2-2202493 P-CR Approval 23.700-48: Solution for KI#6: Avoid UE switching EC traffic away from 3GPP access. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.11 S2-2202501 P-CR Approval 23.700-48: KI#6: New Solution: Network guided EC traffic switching. Apple Rel-18 Not Handled Not Handled
9.11 S2-2202094 P-CR Approval 23.700-48: Solution to KI#7: EDI holding the IP address to DNAI mapping. Ericsson Rel-18 Not Handled Not Handled
9.11 S2-2202370 P-CR Approval 23.700-48: Solution for obtain and maintain mapping table between IP address/IP range with DNAI China Mobile Rel-18 Not Handled Not Handled
9.11 S2-2202407 P-CR Approval 23.700-48: Solution for KI#7: AF obtaining target DNAI. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.11 S2-2202471 P-CR Approval 23.700-48: Solution for the KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI. Vivo Rel-18 Not Handled Not Handled
9.11 S2-2202569 P-CR Approval 23.700-48: KI#7, New solution - Obtain and maintain DNAI information using AF influence. CATT Rel-18 Not Handled Not Handled
9.12 - - - Study on 5G System with Satellite Backhaul (FS_5GSATB) - - Docs:=17 -
9.12 - - - New/updated KI's - - Docs:=2 -
9.12 S2-2202433 P-CR Approval 23.700-27: Update KI#1 to cover packet out-of-sequence problems Huawei, HiSilicon, CATT Rel-18 r02 agreed. Revised to S2-2203307 Guanglei (Huawei) is fine with r01
Hannu (Nokia) provides r01 reducing the text to requirement.
Stefan (Ericsson) provides r02
Relja (TNO) is fine with both r02 and r01. Relja asks Stefan for some clarification on r02.
Stefan (Ericsson) replies to Relja
Hannu (Nokia) supports r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.12 S2-2203307 P-CR Approval 23.700-27: Update KI#1 to cover packet out-of-sequence problems. Huawei, HiSilicon, CATT Rel-18 Revision of S2-2202433r02. Approved Approved
9.12 - - - KI#1 solutions - - Docs:=7 -
9.12 S2-2202399 P-CR Approval 23.700-27: Update on Solution#1 to support multiple satellite backhaul. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203308 Hucheng (CATT) comments.
Stefan (Ericsson) provides comments
Hui (Huawei) provides r01
Hannu (Nokia) provides r02 in order to merge the substance of S2-2202593 into clause 6.1.1.
Hannu (Nokia) supports the updates in r01 but asks whether one instance was forgotten?
Hui (Huawei) fine with r02.
Hucheng (CATT) comments to r02.
Hui (Huawei) replies to Hucheng.
Relja (TNO) provides r03 with further refinement of Hannu's r02.
Hui (Huawei) fine with r03.
Hannu (Nokia) thanks Relja and supports r03.
==== Revisions Deadline ====
Jean Yves (Thales) supports r03.
Stefan (Ericsson) OK with r03
==== Comments Deadline ====
Revised
9.12 S2-2203308 P-CR Approval 23.700-27: Update on Solution#1 to support multiple satellite backhaul. Huawei, HiSilicon Rel-18 Revision of S2-2202399r03. Approved Approved
9.12 S2-2202434 P-CR Approval 23.700-27: Solution for Key Issue #1: Information of satellite constellation and change of backhaul delay exposed to PCF/AF. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2203309 Hucheng (CATT) asks for clarifications.
DongYeon (Samsung) asks for clarificaiton.
Guanglei (Huawei) provides r01.
Guanglei (Huawei) replies and provides r02.
Stefan (Ericsson) provides questions
Haris(Qualcomm) comments
Guanglei (Huawei) replies to Haris(Qualcomm),Stefan (Ericsson) and provides r03
Guanglei (Huawei) replies to Hannu (Nokia) and provides r04
Hannu (Nokia) asks for details of the proposed delay reporting procedures.
==== Revisions Deadline ====
Hucheng (CATT) is fine with r04.
==== Comments Deadline ====
Revised
9.12 S2-2203309 P-CR Approval 23.700-27: Solution for Key Issue #1: Information of satellite constellation and change of backhaul delay exposed to PCF/AF. Huawei, HiSilicon Rel-18 Revision of S2-2202434r04. Approved Approved
9.12 S2-2202586 P-CR Approval 23.700-27: Solution for KI#1: QoS control enhancements for dynamic satellite backhauling. CATT Rel-18 Approved Haris(Qualcomm) provides comments
Hannu (Nokia) asks whether the multi-path backhaul is in the scope of dynamic delay backhaul study?
Hucheng (CATT) responds to Haris(Qualcomm).
Haris(Qualcomm) comments
Hucheng(CATT) clarifies to Hannu (Nokia).
Relja (TNO) asks Hucheng/Hannu for clarification.
Hannu (Nokia) responds to Hucheng
==== Revisions Deadline ====
Hucheng (CATT) clarifies to Relja (TNO).
==== Comments Deadline ====
Approved
9.12 S2-2202593 P-CR Approval 23.700-27: Dynamic delay solution enhancement. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203310 Hucheng (CATT) proposes to merge the EN solving part into S2-2202399.
Hannu (Nokia) agrees with Hucheng and provides r01 to allow partial merger of this CR to S2-2202399 in the area of clause 6.1.1.
==== Revisions Deadline ====
Hucheng (CATT) is fine with r01.
==== Comments Deadline ====
Revised
9.12 S2-2203310 P-CR Approval 23.700-27: Dynamic delay solution enhancement. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202593r01. Approved Approved
9.12 - - - KI#2 solutions - - Docs:=4 -
9.12 S2-2202400 P-CR Approval 23.700-27: Solution for KI#2 and KI#3: Enable Satellite Edge Computing or Local Data Switching via on-board UPF acting as ULCL/BP and local PSA. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203311 Hucheng (CATT) comments.
Stefan (Ericsson) provides questions
Hui (Huawei) provides replies
Stefan (Ericsson) provides comments
Hui (Huawei) responses to Stefan.
Stefan (Ericsson) provides r02
Hui (Huawei) fine with r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.12 S2-2203311 P-CR Approval 23.700-27: Solution for KI#2 and KI#3: Enable Satellite Edge Computing or Local Data Switching via on-board UPF acting as ULCL/BP and local PSA. Huawei, HiSilicon Rel-18 Revision of S2-2202400r02. Approved Approved
9.12 S2-2202587 P-CR Approval 23.700-27: Solution for KI#2: Support of Satellite Edge Computing via UPF on board. CATT Rel-18 r01 agreed. Revised to S2-2203312 Haris(Qualcomm) provides comments
Hucheng (CATT) responds to Haris(Qualcomm) and provides r01.
Stefan (Ericsson) provides comments
==== Revisions Deadline ====
Hucheng (CATT) replies to Stefan (Ericsson).
Hucheng (CATT) asks if we can agree r01 and solve the FFS in the next meeting.
Stefan (Ericsson) OK to agree r01
==== Comments Deadline ====
Revised
9.12 S2-2203312 P-CR Approval 23.700-27: Solution for KI#2: Support of Satellite Edge Computing via UPF on board. CATT Rel-18 Revision of S2-2202587r01. Approved Approved
9.12 - - - KI#3 solutions - - Docs:=4 -
9.12 S2-2202435 P-CR Approval 23.700-27: Solution for Key Issue #3: Enable on-board local data switch based on UPF-level N4 sessions. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203313 Stefan (Ericsson) provides questions
Guanglei (Huawei) replies and provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.12 S2-2203313 P-CR Approval 23.700-27: Solution for Key Issue #3: Enable on-board local data switch based on UPF-level N4 sessions. Huawei, HiSilicon Rel-18 Revision of S2-2202435r01. Approved Approved
9.12 S2-2202588 P-CR Approval 23.700-27: Solution for KI#3: Support of Local Data Switching via UPF on-board. CATT Rel-18 r01 agreed. Revised to S2-2203314 Stefan (Ericsson) provides comments and questions
Hucheng (CATT) responds to Stefan (Ericsson).
Stefan (Ericsson) provides replies
Hucheng (CATT) responds to Stefan (Ericsson) and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.12 S2-2203314 P-CR Approval 23.700-27: Solution for KI#3: Support of Local Data Switching via UPF on-board. CATT Rel-18 Revision of S2-2202588r01. Approved Approved
9.13 - - - Study on the support for 5WWC Phase 3 (FS_5WWC_Ph2) - - Docs:=36 -
9.13 - - - KI 1 new solutions - - Docs:=13 -
9.13 S2-2201987 P-CR Approval 23.700-17: New solution for KI#1: Non-3GPP device behind 5G-RG based on 5GS exposure. Ericsson Rel-18 r02 agreed. Revised to S2-2203501 Laurent (Nokia): Comments
Huan (vivo): ask questions for clarifications or adding ENs
Marco (Huawei): Comments
Sebastian (Qualcomm) provides r01
Stefan (Ericsson) provides r02 and replies to Sebastian and Marco
Stefan (Ericsson) replies to Huan and Laurent
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.13 S2-2203501 P-CR Approval 23.700-17: New solution for KI#1: Non-3GPP device behind 5G-RG based on 5GS exposure. Ericsson Rel-18 Revision of S2-2201987r02. Approved Approved
9.13 S2-2202079 P-CR Approval 23.700-17: Solution for differentiated QoS for non-3GPP devices behind a 5G RG. CableLabs, Charter Rel-18 r03 agreed. Revised to S2-2203502 Laurent (Nokia): Comments, suggests 2 updates
Myungjune (LGE) asks question for clarification.
Huan (vivo) asks question for clarification.
Sriram(CableLabs) provides clarification to Huan (vivo).
Sriram(CableLabs) provides clarifications and r03
Sriram(CableLabs) provides clarifications to Yishan (Huawei)
Sriram(CableLabs) provides r02
Sriram(CableLabs) provides r01
Sriram(CableLabs) replies to Myungjune (LGE) providing clarification.
Huan (vivo) asks for clarifications
Yishan (Huawei) asks for clarifications
==== Revisions Deadline ====
Sriram(CableLabs) provides clarification to Yishan (Huawei).
Sebastian (Qualcomm) is ok with r03
==== Comments Deadline ====
Revised
9.13 S2-2203502 P-CR Approval 23.700-17: Solution for differentiated QoS for non-3GPP devices behind a 5G RG. CableLabs, Charter Rel-18 Revision of S2-2202079r03. Approved Approved
9.13 S2-2202201 P-CR Approval 23.700-17: New solution for KI1: Support of 'combo Ethernet + IP' service. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203503 Huan (vivo): Comments
Stefan (Ericsson) provides comments
Marco (huawei) provides comments
Marco (Huawei) comments
Sebastian (Qualcomm) comments
Laurent (Nokia): provides r01
Sebastian (Qualcomm) provides r02
Laurent (Nokia): answers
==== Revisions Deadline ====
Sebastian (Qualcomm) objects to r00 and r01 and is fine with r02
Marco (huawei) objects to r00 and r01 and accept r02
==== Comments Deadline ====
Revised
9.13 S2-2203503 P-CR Approval 23.700-17: New solution for KI1: Support of 'combo Ethernet + IP' service. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202201r02. Approved Approved
9.13 S2-2202234 P-CR Approval 23.700-17: Solution for differentiated QoS for non-3GPP devices behind a 5G RG. CableLabs Rel-18 Approved Laurent (Nokia): Comments, how is solution in S2-2202234 different from solution 1 in the TR?
Sriram(CableLabs) replies to Laurent.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.13 S2-2202751 P-CR Approval 23.700-17: Solution #X: Support differentiated QoS for AUN3 devices. Lenovo, Motorola Mobility, Broadcom Rel-18 r04 agreed. Revised to S2-2203504 Laurent (Nokia): Comments
Myungjune (LGE) asks question for clarification.
Apostolis (Lenovo) responds to Laurent's (Nokia) questions.
Marco (Huawei) comments.
Huan (vivo) asks for clarifications
Stefan (Ericsson) provides comments
Myungjune (LGE) responds to Apostolis (Lenovo).
Laurent (Nokia): Comments, need of a revision
Sriram(CableLabs) comments and seeks clarifications.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.13 S2-2203504 P-CR Approval 23.700-17: Solution #X: Support differentiated QoS for AUN3 devices. Lenovo, Motorola Mobility, Broadcom Rel-18 Revision of S2-2202751r04. Approved Approved
9.13 S2-2202575 P-CR Approval 23.700-17: FS_5WWC_Ph2 new Solution for KI#1. China Telecom Rel-18 r01 agreed. Revised to S2-2203505 Laurent (Nokia): Comments requesting clarifications in the solutiuon
Huan(vivo): asks for clarifications
Jing (China Telecom): answers and provides r01 to clarify § 6.X.2.2
==== Revisions Deadline ====
Laurent (Nokia): objects to R00
==== Comments Deadline ====
Revised
9.13 S2-2203505 P-CR Approval 23.700-17: FS_5WWC_Ph2 new Solution for KI#1. China Telecom Rel-18 Revision of S2-2202575r01. Approved Approved
9.13 S2-2202634 P-CR Approval 23.700-17: New solution for KI1: Delay budget for non-3GPP devices behind 5G-RG. Qualcomm Rel-18 r02 agreed. Revised to S2-2203506 Huan (vivo): asks for clarifications
Sebastian (Qualcomm) replies
Sebastian (Qualcomm) replies to Marco and provides r02
Marco (Huawei) comments and express concern
Sebastian (Qualcomm) provides r01 and replies
Laurent (Nokia): Comments requiring a solution update
Marco (answer) to Sebastian (Qualcomm)
==== Revisions Deadline ====
Marco (Huawei) ok with r02 and object r00 & r01
==== Comments Deadline ====
Revised
9.13 S2-2203506 P-CR Approval 23.700-17: New solution for KI1: Delay budget for non-3GPP devices behind 5G-RG. Qualcomm Rel-18 Revision of S2-2202634r02. Approved Approved
9.13 - - - KI 2 new solutions - - Docs:=10 -
9.13 S2-2202243 P-CR Approval 23.700-17: New solution for KI#2: Non-3GPP Access with N3IWF/TNGF Relocation due to network slicing. Ericsson Rel-18 r05 agreed. Revised to S2-2203507 Laurent (Nokia): Comments/questions AND suggestion to merge the [second] option of 2139 within 2243
Sebastian (Qualcomm) provides r01
Stefan (Ericsson) provides r02 and replies to Laurent
Marco (Huawei) comments and ask clarification
Laurent (Nokia): provides r03
Stefan (Ericsson) replies to Marco and provides r04
Myungjune (LGE) asks questions.
Stefan (Ericsson) replies and provides r05
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 + R01 + R02
Marco (Huawei): objects to r00, r01, r02,r03, prefer r05
==== Comments Deadline ====
Revised
9.13 S2-2203507 P-CR Approval 23.700-17: New solution for KI#2: Non-3GPP Access with N3IWF/TNGF Relocation due to network slicing. Ericsson Rel-18 Revision of S2-2202243r05. Approved Approved
9.13 S2-2202328 P-CR Approval 23.700-17: New solution to Key Issue 2. China Telecom Rel-18 r02 agreed. Revised to S2-2203508 Heng (China Telecom) provide r01 to remove N3IWF selection part
Laurent (Nokia): Comments asking to merge the [first] option of 2139 within the 2328
Heng (China Telecom) provide r01 to remove the first part(N3IWF selection)
Laurent (Nokia): provides r02
Heng (China Telecom): I am ok with r02
==== Revisions Deadline ====
Laurent (Nokia): objects to R00+R01; happy to agree R02
==== Comments Deadline ====
Revised
9.13 S2-2203508 P-CR Approval 23.700-17: New solution to Key Issue 2. China Telecom Rel-18 Revision of S2-2202328r02. Approved Approved
9.13 S2-2202139 P-CR Approval 23.700-17: Solution on selecting N3IWF supporting the S-NSSAI needed by UE. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203509 Yishan (Huawei) would like to merge partial solution of S2-2202328 from China Telecom and make S2-2202328 mainly focus on TNGF selection.
Laurent (Nokia): Comments
Ashok (Samsung)comments
Yishan (Huawei) has concerns about splitting 2139 for the merge.
Myungjune (LGE) provides comments.
Yishan (Huawei) answers
Sebastian (Qualcomm) provides r02
Ashok (Samsung) ask a question
Laurent (Nokia): provides r03
Yishan (Huawei) is ok with r02
Yishan (Huawei) is ok with r03
==== Revisions Deadline ====
Laurent (Nokia): objects to R0 + R01 + R02. happy to agree R03
==== Comments Deadline ====
Revised
9.13 S2-2203509 P-CR Approval 23.700-17: Solution on selecting N3IWF supporting the S-NSSAI needed by UE. Huawei, HiSilicon, China Telecom Rel-18 Revision of S2-2202139r03. Approved Approved
9.13 S2-2202202 P-CR Approval 23.700-17: New solutions for KI2: UE determination of the N3IWF that supports the slices targeted by the UE. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203510 Jaewoo (LGE) provides comment.
Sebastian (Qualcomm) provides r01 and asks authors about the two solutions in the tdoc
Sebastian (Qualcomm) comments
Laurent (Nokia): provides r02
Marco (Huawei) comments and ask clarification
Yishan (Huawei) asks for clarifications
==== Revisions Deadline ====
Marco (Huawei) object r00 & r01
==== Comments Deadline ====
Revised
9.13 S2-2203510 P-CR Approval 23.700-17: New solutions for KI2: UE determination of the N3IWF that supports the slices targeted by the UE. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202202r02. Approved Approved
9.13 S2-2202700 P-CR Approval 23.700-17: N3IWF selection based on slicing information. Qualcomm Rel-18 r01 agreed. Revised to S2-2203511 Laurent (Nokia): Comments (adding an EN)
Sebastian (Qualcomm) replies
Marco (Huawei) asks clarification
Sebastian (Qualcomm) provides r01
Heng (China Telecom) ask question about TA FQDN format
==== Revisions Deadline ====
Laurent (Nokia): objects to R00; happy to agree with R01
==== Comments Deadline ====
Revised
9.13 S2-2203511 P-CR Approval 23.700-17: N3IWF selection based on slicing information. Qualcomm Rel-18 Revision of S2-2202700r01. Approved Approved
9.13 - - - KI 1 updated solutions - - Docs:=4 -
9.13 S2-2202553 P-CR Approval 23.700-17: Update solution for remote UE accessing 5GC. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203512 Huan (vivo): asks for clarifications
Sebastian (Qualcomm) provides r01
Stefan (Ericsson) provides questions
Susan (Huawei) replies and provides r01.
Susan (Huawei) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.13 S2-2203512 P-CR Approval 23.700-17: Update solution for remote UE accessing 5GC. Huawei, HiSilicon Rel-18 Revision of S2-2202553r02. Approved Approved
9.13 S2-2202563 P-CR Approval 23.700-17: FS_5WWC_Ph2 Update of Solution 4 for providing differentiated service for non-3GPP devices connected behind a 5G-RG. Vivo Rel-18 r04 agreed. Revised to S2-2203513 Laurent (Nokia): Comments asking EN addition
Huan (vivo): provides feedback to Laurent and upload r01
Stefan (Ericsson) provides comments
Marco (Huawei) comments
Laurent (Nokia): provides r03
Huan (vivo) provides feedback to Stefan and r02
Huan (vivo) provides feedback and upload r04
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 + R01 + R03. Much prefers R03 but can live with r04
==== Comments Deadline ====
Revised
9.13 S2-2203513 P-CR Approval 23.700-17: FS_5WWC_Ph2 Update of Solution 4 for providing differentiated service for non-3GPP devices connected behind a 5G-RG. Vivo Rel-18 Revision of S2-2202563r04. Approved Approved
9.13 - - - KI 2 updated solutions - - Docs:=2 -
9.13 S2-2202939 P-CR Approval 23.700-17: Additions to Solution 12: Slice related TNGF selection for WLAN access. Lenovo, Motorola Mobility Rel-18 r01 agreed. Revised to S2-2203514 Laurent (Nokia): Comments asking to change text (adding an EN)
Apostolis (Lenovo) responds to Laurent's (Nokia).
Apostolis (Lenovo) provides r01.
==== Revisions Deadline ====
Laurent (Nokia): objects to R00.
==== Comments Deadline ====
Revised
9.13 S2-2203514 P-CR Approval 23.700-17: Additions to Solution 12: Slice related TNGF selection for WLAN access. Lenovo, Motorola Mobility Rel-18 Revision of S2-2202939r01. Approved Approved
9.13 - - - Rapporteur's input (out of FS_5WWC_Ph2 quota) - - Docs:=1 -
9.13 S2-2202173 LS OUT Approval [DRAFT] LS on FS_5WWC_Ph2 R18 study Nokia, Nokia Shanghai Bell Rel-18 Noted Sebastian (Qualcomm) suggests to postpone the LS
Laurent (Nokia): unfortunately our august meeting is our deadline decision meeting and we need input from BBF / Cable Labs for this as an input
Sebastian (Qualcomm) objects to the LS
Laurent (Nokia): answers: I do not plan to send the TR for information at this meeting (there was not input Tdoc for this anyhow), I'll have to submit in May a SID change to shift the deadline to December, as we haven't got 5WWC slot to progress the solutions at the May meeting and we need external feedback. we don't let Cable and BBF folks much time to answer between end of august and October
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.13 - - - Documents exceeding TU Budget - - Docs:=6 -
9.13 S2-2201985 P-CR Approval 23.700-17: Solution updates to Solution #2 to e.g. resolve ENs. Ericsson Rel-18 Not Handled Not Handled
9.13 S2-2201986 P-CR Approval 23.700-17: Updates to solution #1 to resolve Editor's Notes. Ericsson Rel-18 Not Handled Not Handled
9.13 S2-2202495 P-CR Approval 23.700-17: Update to Solution#6 on FS_5WWC_Ph2. China Telecom Rel-18 Not Handled Sebastian (Qualcomm) provides r01
Marco (Huawei) comments and has a technical concern
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.13 S2-2202632 P-CR Approval 23.700-17: Addressing Editor's notes for solution 7. Qualcomm Incorporated Rel-18 Not Handled Not Handled
9.13 S2-2202203 P-CR Approval 23.700-17: Update to solution 12. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not Handled
9.13 S2-2202244 P-CR Approval 23.700-17: New solution for KI#2: N3IWF selection by UE taking supported slices into account. Ericsson Rel-18 Not Handled Not Handled
9.14 - - - Study on Network Slicing Phase 3 (FS_eNS_Ph3) - - Docs:=59 -
9.14 - - - Key Issue - - Docs:=2 -
9.14 - - - WT#2 Rejected S-NSSAI - - Docs:=2 -
9.14 S2-2202221 P-CR Approval 23.700-41: Key issue for Handling Rejected S-NSSAIs in some TAs of RA. Ericsson, Nokia, Nokia shanghai Bell, Samsung, InterDigital Inc., DISH Network, ZTE, Qualcomm Inc, Apple, Huawei, LG Electronics, NEC Rel-18 Revision of (Noted) S2-2200190. r04 agreed. Revised to S2-2203080 Antoine (Orange) proposes a rewording.
Antoine (Orange) provides r01, merging S2-2202763.
Peter Hedman (Ericsson) provides r02
Alessio(nokia) is ok with r02
Jinguo(ZTE) provides r03
Ashok (Samsung) agrees with r03
Peter Hedman (Ericsson) provides r04
alessio(Nokia) agrees also with r04.
Serge (T-Mobile USA) provides r05 with a small clarification.
Antoine (Orange): OK with r04, not with r05 .
Jinguo(ZTE) agrees that r04 is better
Kundan(NEC) is not fine with r01-05. the original version has be captured after lot of discussion to not narrow down the scope of the solution.
Antoine (Orange) is not fine with r00.
Kundan(NEC) provides r06.
Peter Hedman (Ericsson) provides comments
==== Revisions Deadline ====
Haiyang(Huawei) suggests to go with r04
Ashok (Samsung) shares same view as Haiyang and agrees to r04
Peter Hedman (Ericsson) ok with r04 and r06
Alessio (nokia) Supports r04
Kundan (NEC) supports r04 and r06 but prefers r06.
==== Comments Deadline ====
Revised
9.14 S2-2203080 P-CR Approval 23.700-41: Key issue for Handling Rejected S-NSSAIs in some TAs of RA . Ericsson, Nokia, Nokia shanghai Bell, Samsung, InterDigital Inc., DISH Network, ZTE, Qualcomm Inc, Apple, Huawei, LG Electronics, NEC, Orange Rel-18 Revision of S2-2202221r04. Approved Approved
9.14 - - - WT#4: NW Control - - Docs:=2 -
9.14 S2-2202737 P-CR Approval 23.700-41: New key issue: KI for objective #4 -Improved Network control of the UE behaviour Nokia, Nokia Shanghai Bell, Ericsson, Samsung, Verizon UK Ltd Rel-18 r08 agreed. Revised to S2-2203081 Stefano (Qualcomm) provides questions
Fenqin (Huawei) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203081 P-CR Approval 23.700-41: New key issue: KI for objective #4 -Improved Network control of the UE behaviour . Nokia, Nokia Shanghai Bell, Ericsson, Samsung, Verizon UK Ltd Rel-18 Revision of S2-2202737r08. Approved Approved
9.14 - - - WT#7: NSAC - - Docs:=1 -
9.14 S2-2202018 P-CR Approval 23.700-41: New Key issue for WTI#7: Handling of Number of Registered UEs, and number PDU Sessions while roaming.. Ericsson Rel-18 Noted Fenqin (Huawei) provides comments
George (Ericsson) provides comments
Alessio(nokia) provides r01 that aligns to the NG.116 the existing KI, rather than creating a new KI
George (Ericsson) provides r02
George (Ericsson) provides response
George (Ericsson) NOT Ok with r01.
alessio does not think R02 shall be approved. we need to stick to r01
==== Revisions Deadline ====
George (Ericsson) Ericsson only OK with r02, or original.
alessio(nokia) politely asks why r01 is not ok...
Alessio(nokia) comments the coexistence is a non-issue as each slice is configured with ONE behaviour but since this is a KI we can live with r02 . objects to r00
George (Ericsson) provides comments. The co-existence cannot be pre-configured, and this is what r02 proposes. This has to be dynamic and should be under HPLMN control; no configuration is needed in the VPLMN. This is what r01 tries to achieve.
==== Comments Deadline ====
Noted
9.14 - - - Solution for KI#1 (Service Continuity) - - Docs:=13 -
9.14 S2-2202054 P-CR Approval 23.700-41: New solution for KI#1: Support of Network Slice Service continuity. Huawei, HiSilicon Rel-18 Noted Alessio(Nokia) comments on the specific use case and believes this is non-existent. proposes to note the paper. objects to it being approved and proposes r01 to remove the use case
Haiyang (Huawei) objects r01, provides r02
==== Revisions Deadline ====
Alessio(Nokia) after clarification insists even more to approve r01 objects to r02 and r00
Haiyang (Huawei) comments
Alessio(Nokia) replies that we cannot assume the overload is caused by one UE alone.
Haiyang(Huawei) replies to Alessio(Nokia), doubting the value of this KI.
==== Comments Deadline ====
Noted
9.14 S2-2202267 P-CR Approval 23.700-41: Solution for the KI#1: Network Slice Switch for Ensuring Service Continuity. Alibaba Group Rel-18 Noted Dongeun (Samsung) provides comments
Stefano (Qualcomm) proposes to note the paper since it is not related to the key issue
Xiaobo Yu (Alibaba) provides r01 and replies to the comments from Qualcomm
Xiaobo Yu (Alibaba) replies to the comments from Samsung
Patrice (Huawei) proposes to note.
Xiaobo Yu (Alibaba) provides r02 and replies to comments from Huawei
Patrice (Huawei) is still not convinced of the validity of the proposed scenario.
Stefano (Qualcomm) is also not convinced of the validity of the proposed scenario and proposes to note.
Xiaobo Yu (Alibaba) provides r03 and replies to the comments from Huawei and Qualcomm.
==== Revisions Deadline ====
Stefano (Qualcomm) asks once again to note the paper.
Xiaobo Yu (Alibaba) replies to the comments from Qualcomm and propose to discussion r03 in CC#2.
==== Comments Deadline ====
Xiaobo Yu (Alibaba) proposes to add EN and wording changes based on r03 and have it reviewed in CC#3.
Noted
9.14 S2-2202668 P-CR Approval 23.700-41: FS_eNS_Ph3 New Solution to KI#1. ZTE Rel-18 r05 agreed. Revised to S2-2203082 Jinguo(ZTE) response to Myungjune(LGE)
Myungjune(LGE) asks question for clarification
Dongeun (Samsung) ask for clarification.
Dongeun (Samsung) ask again for clarification.
Jinguo(ZTE) provides r02 and response to Dongeun (Samsung)
Iskren (NEC) asks questions
Jinguo(ZTE) replies to Iskren (NEC) and provides r03
Patrice (Huawei) comments, proposes to clarify the purpose of the solution, or note for now.
Jinguo(ZTE) replies to Patrice (Huawei)
Patrice (Huawei) comments Jinguo (ZTE)'s answers, and requests further update.
Jinguo(ZTE) provides r04.
Patrice (Huawei) thanks Jinguo (ZTE) for the update, provides r05 (objects r04 and earlier revisions).
Iskren (NEC) comments.
Iskren (NEC) provides r06 based on r01.
Patrice (Huawei) objects r06, which takes away all the clarifications that have been added during the week.
Jinguo(ZTE) is fine with r05
Iskren (NEC) provides r07 based on r05 with 'instance' removed and added NE
==== Revisions Deadline ====
Jinguo(ZTE) provides r08
Iskren (NEC) comments on r08
Dongeun (Samsung) provides late revision r09 and propose to either postpone this paper or approve r09 in CC#2
Patrice (Huawei) objects r07, r08, r09 (unless the editor's note on associating a slice instance with S-NSSAI is removed). Therefore, I propose to go with r05, or with r05 with the following additional Editor's Note at the bottom of 6.X.1: 'Editor's note: It is FFS whether and how the PDU Session can be associated with more than one S-NSSAI within a PLMN'.
Jinguo(ZTE) agree with Patrice (Huawei), propose to approve r05 with the editor note
Editor's note: It is FFS whether and how the PDU Session can be associated with more than one S-NSSAI within a PLMN'
Dongeun (Samsung) is ok with r05 + Editor's note: It is FFS whether and how the PDU Session can be associated with more than one S-NSSAI within a PLMN'
==== Comments Deadline ====
Revised
9.14 S2-2203082 P-CR Approval 23.700-41: FS_eNS_Ph3 New Solution to KI#1. ZTE Rel-18 Revision of S2-2202668r05. Approved Approved
9.14 S2-2202757 P-CR Approval 23.700-41: A New Solution for KI#1: Support of Network Slice Service Continuity. Samsung Rel-18 r04 agreed. Revised to S2-2203083 Myungjune(LGE) asks question for clarification.
Dongeun (Samsung) replies to Myungjune(LGE)
Myungjune(LGE) requests to update procedure and impact.
Jinguo(ZTE) agree with Myungjune(LGE)
Iskren (NEC) asks question
Dongeun (Samsung) replies to Iskren (NEC)
Dongeun (Samsung) replies to Myungjune(LGE) and Zinguo (ZTE) and provides r01
Patrice (Huawei) comments
Dongeun (Samsung) replies to Patrice (Hauwei) and provides r02.
Alessio(nokia) comments that the solution seems needing more updates
Dongeun (Samsung) provides r03
Patrice (Huawei) thanks Dongeun for the update, but has more comments and requests an update with additional ENs.
Dongeun (Samsung) provides r04
==== Revisions Deadline ====
Patrice (Huawei) cannot accept r04 (or previous versions) as it is. But I can accept r04 + changing the Editor's note in 6.X.2 to ' EN: 'The specific scenarios that this solution is intending to resolve are FFS.'
Dongeun (Samsung) is ok with the proposal by Patrice (Hauwei) and propose to approve r05 that is provided after deadline (i.e., r04 + 'Editor's note: The specific scenarios that this solution is intending to resolve are FFS.')
Dongeun (Samsung) propose to approve r04 + 'Editor's note: The specific scenarios that this solution is intending to resolve are FFS.' in CC#2
==== Comments Deadline ====
Revised
9.14 S2-2203083 P-CR Approval 23.700-41: A New Solution for KI#1: Support of Network Slice Service Continuity. Samsung Rel-18 Revision of S2-2202757r04. Approved Approved
9.14 S2-2202766 P-CR Approval 23.700-41: 23.700-41: Solution for KI#1; Support of Network Slice Service continuity using SSC mode 3. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203084 Myungjune(LGE) asks question for clarification.
Alessio(Nokia) replies to LGE question.
Myungjune (LGE) responds to Alessio (Nokia).
Patrice (Huawei) asks for clarification and update.
Patrice (Huawei) provides r02 in a hurry before deadline.
Alessio(Nokia) clarifies what was asked in r01
==== Revisions Deadline ====
Alessio(nokia) is ok with r02
Patrice (Huawei) clarifies the additions in r02, and that only r02 is acceptable (object r00, r01).
==== Comments Deadline ====
Revised
9.14 S2-2203084 P-CR Approval 23.700-41: 23.700-41: Solution for KI#1; Support of Network Slice Service continuity using SSC mode 3. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202766r02. Approved Approved
9.14 S2-2202850 P-CR Approval 23.700-41: KI#1 new Solution X: PDU Session on compatible network slice. NEC Rel-18 r03 agreed. Revised to S2-2203085 Myungjune(LGE) asks question for clarification.
Stefano (Qualcomm) asks questions for clarification
Iskren (NEC) answers question from Stefano (Qualcomm)
Iskren (NEC) answers Myungjune(LGE)
Jinguo(ZTE) comments
Iskren (NEC) answers comments from Jinguo (ZTE)
Myungjune(LGE) clarifies question.
Iskren (NEC) answers comments from Myungjune(LGE).
Myungjune(LGE) responds to Iskren (NEC)
Iskren (NEC) provides updates in r01 based on comments from Stefano (Qualcomm), Jinguo (ZTE) and Myungjune(LGE)
Patrice (Huawei) comments, asks for update
Iskren (NEC) replies to Patrice (Huawei) and provides updates in r02
Alessio(Nokia) requests to note version of this paper where NSAC is mentioned. For r02 as it is not approvable till it is clear how the slice that is compatible is in the allowed NSSAI.
Iskren (NEC) answers Alessio(Nokia) and provides r03 with the requested update.
Patrice (Huawei) thanks Iskren for the update. r03 is OK for me.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203085 P-CR Approval 23.700-41: KI#1 new Solution X: PDU Session on compatible network slice . NEC Rel-18 Revision of S2-2202850r03. Approved Approved
9.14 S2-2202853 P-CR Approval 23.700-41: KI#1 new Solution Y: PDU session handover to a target RAN with an alternative S-NSSAI support. NEC Rel-18 Merged into S2-2203086 Jinguo(ZTE) comments that this solution may be out scope of KI#1
Myungjune(LGE) comments.
Patrice (Huawei) comments that this is out of scope and should be noted.
Alessio(Nokia) assumes 2a,2b are not our of scope and we need to further study if they are indeed out of scope based on the KI EN. comments on this solution that now it is same as 850 largely. Allowed NSSAI considerations missing
Iskren (NEC) agrees for this pCR to be noted
==== Revisions Deadline ====
Iskren (NEC) - actually this pCR is better be marked as merged to 2854
==== Comments Deadline ====
Merged
9.14 S2-2202854 P-CR Approval 23.700-41: KI#1 new Solution Z: PDU session handover to a target CN with an alternative S-NSSAI support. NEC Rel-18 r04 agreed. Revised to S2-2203086, merging S2-2202853 Myungjune(LGE) asks question for clarification.
Jinguo(ZTE) comments that this solution should further clarified otherwise can be noted
Iskren (NEC) answers comments from Jinguo(ZTE) and Myungjune (LGE) and provides revision 01
Myungjune (LGE) comments on r01
Iskren (NEC) answers comment from Myungjune (LGE) and provides revision 02
Patrice (Huawei) updates his comment: provides a comment and propose to note unless clarify how this solve the scenario 2d.
Patrice (Huawei) .....
Iskren (NEC) answers Patrice (Huawei)
Myungjune (LGE) comments on revision 02.
Alessio(nokia) proposes this is merged in 853 and 850 to be one solution. Technically this does not work as the RAN is the one that triggers the HO to a target RAN node and the RAN has to pichk acell where the target alternative S-NSSAI works so the RAN must be aware of the alternative S-NSSAI and when the target RAN node cannot support the primary one because it is in an area where the CN is not working for the slice.
Iskren (NEC) addresses comments from Alessio (Nokia) and Patrice (Huawei) and provides r03
Patrice (Huawei) thanks Iskren (NEC) for the update, requires 3 more additional changes as described.
Iskren (NEC) addresses comments from Patrice (Huawei) and provides r04
Patrice (Huawei) thanks Iskren (NEC) and is OK with r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203086 P-CR Approval 23.700-41: KI#1 new Solution Z: PDU session handover to a target CN with an alternative S-NSSAI support . NEC Rel-18 Revision of S2-2202854r04, merging S2-2202853. Approved Approved
9.14 - - - Solution for KI#2 (VPLMN selection) - - Docs:=11 -
9.14 S2-2202021 P-CR Approval 23.700-41: Key issue 2: Extended SoR VPLMN Slice Information transfer to UEs. Ericsson Rel-18 r05 agreed. Revised to S2-2203087, merging S2-2202819 and S2-2202897 Myungjune (LGE) asks question for clarification
DongEun (Samsung) asks for clarificaiton.
Kundan(NEC) asks questions.
Haiyang (Huawei) comments.
George (Ericsson) provides comments
George (Ericsson) provides r0. Removed the simultaneous access to VPLMNs
Krisztian (Apple) supports r01 and provides r02 to indicate the merge with S2-2202897.
George (Ericsson) provides response
Haiyang (Huawei) asks question for clarification
Jinguo(ZTE) asks question for clarification
Genadi (Lenovo) is OK to merge S2-2202819 into the provided r03.
Genadi (Lenovo) replies to Jinguo(ZTE) and Haiyang (Huawei).
George (Ericsson) provides r04. Just a couple of typos; s in slice got chopped off in few locations.
George (Ericsson) please look at rev 03. It has Lenovo and Apple merged in. It should answer those questions. Some answers in line
Ulises Olvera (InterDigital Inc.) provides comments or r01.
Ulises Olvera (InterDigital Inc.) provides comments or r04.
Genadi (Lenovo) provides comments to Ulises Olvera (InterDigital Inc.).
Genadi (Lenovo) provides r05.
George (Ericsson) asks a question
Genadi (Lenovo) replies to George (Ericsson).
George (Ericsson) provides answers
==== Revisions Deadline ====
George (Ericsson) Prefer R04s but can accept r05. l
Haiyang (Huawei) is OK with r05, but objects to other versions.
Ulises Olvera (InterDigital Inc.) can accept r05.
==== Comments Deadline ====
Revised
9.14 S2-2203087 P-CR Approval 23.700-41: Key issue 2: Extended SoR VPLMN Slice Information transfer to UEs. Ericsson, Apple, Lenovo, Motorola Mobility Rel-18 Revision of S2-2202021r05, merging S2-2202819 and S2-2202897. Approved Approved
9.14 S2-2202056 P-CR Approval 23.700-41: New Solution for KI#2: VPLMN Selection following existing SoR information. Huawei, HiSilicon Rel-18 Noted Myungjune (LGE) asks question for clarification
George Foti (Ericsson) proposes to merge this in 2021
Haiyang (Huawei) clarifies, prefer to keep this solution independent
Genadi (Lenovo) asks questions for clarification.
George (Ericsson) provides comments
Haiyang (Huawei) provides r01
Alessio(nokia) comments that this solution is not meeting the stage one and is largely not changing what is done today already. proposes to note
Haiyang (Huawei) comments to Alessio(nokia) , provides r02
==== Revisions Deadline ====
Alessio(nokia) replies, cannot live with r02
Haiyang (Huawei) comments, still suggests to go with r02
==== Comments Deadline ====
Noted
9.14 S2-2202277 P-CR Approval 23.700-41: KI #2, New Sol: VPLMN selection by using Operator Controlled PLMN Selector with Slice information. LG Electronics Rel-18 Noted Myungjune (LGE) responds to Jinguo (ZTE)
Jinguo(ZTE) comments
Myungjune (LGE) responds to George Foti (Ericsson) and provides r01
George Foti (Ericsson) provides comments
Jinguo(ZTE) responds to Myungjune (LGE)
Myungjune (LGE) responds to Jinguo(ZTE).
George (Ericsson) provides comments
Myungjune (LGE) replies to George (Ericsson) and Srisakul (NTT DOCOMO) and provides r02.
Srisakul (NTT DOCOMO) agrees to add EN on SOR-AF related aspect.
George (Ericsson) ask question
Dongeun (Samsung) comments
Myungjune (LGE) responds to Dongeun (Samsung)
Alessio(nokia) comments that this solution should be noted
Myungjune (LGE) responds to Alessio (Nokia) and don't agree to note.
Myungjune (LGE) responds to Genadi (Lenovo).
Genadi (Lenovo) comments with an example.
Myungjune (LGE) replies to George (Ericsson).
Myungjune (LGE) responds to George (Ericsson)
==== Revisions Deadline ====
George (Ericsson) Can accept r02
TAO(VC) let's check r02 agreeable or not
alessio(nokia) proposes to note r02
Myungjune (LGE) replies to Alessio (Nokia) and proposes to agree r02
==== Comments Deadline ====
Noted
9.14 S2-2202666 P-CR Approval 23.700-41: Solution for KI#2: enhancement of SOR mechanism. ZTE Rel-18 Noted DongEun (Samsung) comments
Myungjune (LGE) asks question for clarification.
Jinguo(ZTE) replies to DongEun (Samsung)
DongEun (Samsung) ask questions
George Foti (Ericsson) proposes to merge this in 2021 which is more complete.
Haiyang (Huawei) asks question for clarification.
Jinguo(ZTE) response to Myungjune (LGE) and DongEun (Samsung) and provides r01.
George (Ericsson) provides comments. R01 has the wrong attachment
Jinguo(ZTE) response to Haiyang (Huawei) and provides r02
George (Ericsson) asks question
Jinguo(ZTE) answer to George (Ericsson)
George (Ericsson) asks additional questions.
Jinguo(ZTE) response to George (Ericsson)
George (Ericsson) please provide a link to the updated solution
Alessio(Nokia) proposes to note this solution as it does not work and also not address the stage 1
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.14 S2-2202749 P-CR Approval 23.700-41: Solution for KI#2 Support of providing VPLMN network slice information to a roaming UE. NEC Rel-18 Noted Kundan (NEC) disagrees with George (Ericsson) analysis and responds to George.
DongEun (Samsung) ask questions
George Foti (Ericsson) provides comments
Myungjune (LGE) asks question for clarification
Genadi (Lenovo) asks question for clarification.
George (Ericsson) provides comments
Kundan (NEC) responds to Genadi.
Kundan(NEC) provides response to Myungjune (LGE).
Kundan (NEC) provides r01.
Haiyang (Huawei) provides comments
Kundan (NEC) responds to Haiyang.
Kundan(NEC) provides r02 incorporating George comments.
alessio (Nokia) requests to note this paper as it does not work and a monolithic SoR info should not be used to satisfy the stage 1.
Kundan(NEC) clarifies to Genadi.
Genadi (Lenovo) comment to Kundan (NEC) regarding the rejected cause provided to the UDM.
Kundan(NEC) provides r04 addressing Alessio comments. Kundan thinks the solution can work very efficiently.
==== Revisions Deadline ====
alessio(Nokia) is still unclear this is a working solution as it is monodimensional SoR (like today) and also because the trigger of rejected NSSAI happens only due to misconfiguration of supported slices in the past but this is resolved by updating the UE configuration not SoR. proposes to note and discuss offline till we have a clear solution for next meeting . cannot agree any revisions at this meeting byt happy to work offline till next meeting to understand this paper proposal better.
Kundan(NEC) thinks Nokia is confused and overlooking the fact that the NSSAI can be rejected due to other factor than misconfiguration e.g. requested S-NSSAI not supported in the current RA or no. of UE reached for the S-NSSAI . we propose to agree this solution and discuss further in next meeting. I don't see any harm in including the new solution in the TR and come back in the next meeting.
Alessio(Nokia) believes SoR should not be activated when a UE enters or exists a RA... this would be too much.
Alessio (Nokia) has wrong observation, the solution doesn't mention the HPLMN will trigger SoR every now and then. He is talking about evaluation phase which has yet not come. even we have a note in our solution.
==== Comments Deadline ====
Noted
9.14 S2-2202819 P-CR Approval 23.700-41: Solution for KI#2: providing Network Slice based SoR information to the UE. Lenovo, Motorola Mobility Rel-18 Merged into S2-2203087 George Foti (Ericsson) proposes to merge this pCR int 2021, as it is fully covered there.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.14 S2-2202820 P-CR Approval 23.700-41: 23.700-41: Solution for KI#3; configuring the UE with per network slice preferred PLMNs. Nokia, Nokia Shanghai Bell Rel-18 Noted George Foti (Ericsson) provides comments
Myungjune (LGE) asks question for clarification.
Alessio(nokia) replies and provides r01 aligning to the existing TR skeleton and Solutions description format and also take comments into account
Genadi (Lenovo) seeks clarification for the 'weight' in the table.
Kundan(NEC) proposes to note the paper as many steps can not be implementable and ambiguous.
Genadi (Lenovo) proposes r02 as a merger with S2-2202819.
Alessio(nokia) points out SoR uses a transparent container so NEC comment is invalid. the procedure indeed will be updated to include the new info in the transparent container obviously ??.
Genadi (Lenovo) proposes r03
==== Revisions Deadline ====
George (Ericsson) can accept r01.
Genadi (Lenovo) is fine with r03. We cannot agree r01 as it is missing the concept from the merged S2-2202819 where the UE can also internally determine the preferred S-NSSAIs. To correct the notes: r03 was provided by Alessio (Nokia); Genadi provided r02.
Tao(VC) check whether we can go with r03
alessio is ok with r03 and r01
Kundan(NEC) is not fine with original version and any revisions. reasons are same as explained in my previous mail.
alessio(nokia) claims NEC is taking the PCR ransom to get theirs approved. Asks if NEC will let this approved if we let thought theirs (which is not descending into ridicule)
Alessio(Nokia) proposes to go to CC#2/3 to verify the issue.
NEC(Kundan) disagrees with Alessio (Nokia) observations. We are not fine with the Nokia proposed approach basically this is his approach of working. we already provided our technical comments to his paper.
Alessio(Nokia) asks the P-CR to be approved at CC#3 as NEC concern is based on our comments on their CR 'You keep changing your goal post. I clarified each and every comments. When you didn't find any further issue you are raising questions which are part of the evaluation.'
==== Comments Deadline ====
Noted
9.14 S2-2202897 P-CR Approval 23.700-41: New Sol for KI#2: Support of slice aware PLMN selection in roaming scenarios. Apple Rel-18 Merged into S2-2203087 George Foti (Ericsson) proposes to merge this with the UE initiated approach in 2021
Myungjune (LGE) asks question for clarification.
George (Ericsson) provides comments
Myungjune (LGE) provides comments.
Krisztian (Apple) confirms the UE initiated procedure in 2021 is along the same lines as this solution. We are OK with the merge.
George (Ericsson) provides comments. 2021 clearly shows this as a UE behavior,
Myungjune (LGE) replies to Krisztian (Apple).
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.14 S2-2202943 P-CR Approval 23.700-41: New Solution to KI#2: Enabling awareness of Network Slice availability in VPLMNs. InterDigital Inc. Rel-18 r03 agreed. Revised to S2-2203088 George Foti (Ericsson) provides comments
Myungjune (LGE) asks question for clarification.
Genadi (Lenovo) asks questions for clarification.
Ulises Olvera (InterDigital Inc.) replies to Myungjune (LGE)'s comments.
Ulises Olvera (InterDigital Inc) provides replies to George's comments, and it provides r01
Ulises Olvera (InterDigital Inc) provides replies to Genadi's comments, and it provides r01
George (Ericsson) provides comments
Haiyang (Huawei) provides questions
Ulises Olvera (InterDigital Inc) provides replies to Haiyang (Huawei), and provides r02
alessio(nokia) comments and requests to remove option 2 from the solution a sit seems to be not working
Ulises Olvera (InterDigital Inc) provides replies to Alessio (Nokia), and provides r03
==== Revisions Deadline ====
George (Ericsson) can accept r03
==== Comments Deadline ====
Revised
9.14 S2-2203088 P-CR Approval 23.700-41: New Solution to KI#2: Enabling awareness of Network Slice availability in VPLMNs. InterDigital Inc. Rel-18 Revision of S2-2202943r03. Approved Approved
9.14 - - - Solution for KI#3 (Service area and lifetime) - - Docs:=10 -
9.14 S2-2202601 P-CR Approval 23.700-41: New solution for avoiding service disruption due to slice termination in key issue#3. NTT DOCOMO Rel-18 r04 agreed. Revised to S2-2203089 George Foti (Ericsson) provides comments
Kundan(NEC) supports the solution.
Stefano (Qualcomm) expresses concerns and proposes to note the proposal
Srisakul (NTT DOCOMO) provides r02 by adding NEC, which I forgot to add in r01. Sorry.
Srisakul (NTT DOCOMO) provides r01 and responds to comments raised by George (E//), Kundan (NEC) and Stefano (Qualcomm). Do not think that we should stop documenting a solution that does not have a UE impact at this stage. We can compare all proposed solutions during the evaluation period, but not now.
Patrice (Huawei) comments, proposes ways for improvement.
Srisakul (NTT DOCOMO) provides r03 and responds to Patrice (Huawei).
alessio(Nokia) comments
Patrice (Huawei) thanks Srisakul (NTT Docomo) for the update, and replies.
Srisakul (NTT DOCOMO) provides r04. Response to Alessio (NOKIA) and Patrice (Huawei)
Patrice (Huawei) thanks Srisakul (NTT Docomo) for the update, is OK with r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203089 P-CR Approval 23.700-41: New solution for avoiding service disruption due to slice termination in key issue#3. NTT DOCOMO, NEC Rel-18 Revision of S2-2202601r04. Approved Approved
9.14 S2-2202626 P-CR Approval 23.700-41: KI #3, New Sol: Support of Area of Service and lifetime of the network slice. CATT Rel-18 Noted George Foti (Ericsson) proposes to note the paper. Please see additional comments
Yunjing (CATT) replies to George Foti (Ericsson).
George (Ericsson) provides comments
Yunjing(CATT) provides r01.
Patrice (Huawei) comments.
Yunjing (CATT) replies to George (Ericsson)
Jinguo(ZTE) asks the author to pick one solution in this paper
Yunjing (CATT) replies to Patrice (Huawei) and provides r02.
Patrice (Huawei) has further comments, requests further update.
alessio(nokia) cannot accept r03 as the concept of AoS is left undefined (how is it communicated to the UE, in which way)
Alessio(Nokia) comments that this paper solution 1 cannot be accepted as the concept of AoS provided to the Ue is undefined. Solution 2 should be merged with the docomo solution somehow. but if CATT wants to retain as independent we can live with that.
Yunjing (CATT) provides r03 to remove solution Y based comment from Jinguo(ZTE)
Yunjing (CATT) provides r04.
Yunjing (CATT) provides r04 to address alessio(nokia)'s comment.
Patrice (Huawei) thanks Yunjing (CATT) for the update in r04, which is acceptable.
==== Revisions Deadline ====
alessio(nokia) cannot accept this solution as the AoS parameters has not been made concrete (is it a TA, is it a cell?)
==== Comments Deadline ====
Noted
9.14 S2-2202822 P-CR Approval 23.700-41: 23.700-41: Solution for KI#5; support of a Network Slice with an Area of Service not matching existing TA boundaries. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203090 Patrice (Huawei) comments, requires update.
alessio(nokia) provides update in r01
Patrice (Huawei) thanks Alessio (Nokia) for the update, can accept it for now.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203090 P-CR Approval 23.700-41: 23.700-41: Solution for KI#5; support of a Network Slice with an Area of Service not matching existing TA boundaries. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202822r01. Approved Approved
9.14 S2-2202902 P-CR Approval 23.700-41: Solution: KI#3: Network Slice Area of Service for services not mapping to existing TAs boundaries. NEC Rel-18 Postponed Patrice (Huawei) comments that this seems to be misplaced and to be a solution to the non-yet approved KI for WT#2. This should be noted.
Kundan(NEC) clarifies that this is for KI#3 to handle - 'The support of services over network slices when the services have Area of Service not matching the existing deployed TA boundaries'.
alessio(nokia) comments this cannot meet KI#3 as it does not show how a S-NSSAI does not match a deployed TA. it may meet KI#2 but so it should be noted in both cases at this meeting.
Patrice (Huawei) proposes to postpone.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.14 S2-2202921 P-CR Approval 23.700-41: Solution: KI#3 Key Issue #3: Temporary network slices. NEC Rel-18 r03 agreed. Revised to S2-2203091 George Foti (Ericsson) provides comments
Kundan(NEC) mentions that George has wrong understanding of KI and further clarifies to him.
George (Ericsson) provides comments
Jinguo(ZTE) comments.
Ashok (Samsung) comments
Kundan(NEC) responds to Jinguo.
Jinguo(ZTE) comments that the impacts on UDM should be added
Kundan(NEC) provides r01.
Kundan(NEC) agrees with Ashok and will add EN in the revision.
Patrice (Huawei) comments, requests update.
Kundan (NEC) provides revision addressing Patrice (Huawei) comments.
Patrice (Huawei) thanks Kundan (NEC) for the update.
Kundan (NEC) provides r03 incorporating further comment from Patrice.
Patrice (Huawei) thanks Kundan (NEC) for the update, and is OK with r03.
==== Revisions Deadline ====
George (Ericsson) can accept r03
Ashok (Samsung) is fine with r03 but need one small clarification
Kundan(NEC) provides clarification to Ashok.
Patrice (Huawei) clarifies his comment.
==== Comments Deadline ====
Revised
9.14 S2-2203091 P-CR Approval 23.700-41: Solution: KI#3 Key Issue #3: Temporary network slices. NEC , NTT DOCOMO Rel-18 Revision of S2-2202921r03. Approved Approved
9.14 S2-2202349 P-CR Approval 23.700-41: New solution on Key issue for WT#2 for Handling Rejected S-NSSAIs in some TAs of RA. Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2203092 Srisakul (NTT DOCOMO) asks a few questions on the solutions, and comments that solution is not clear on how it works, as there is no procedure described.
Stefano (Qualcomm) provides R01.
Patrice (Huawei) comments, would kindly request an update accordingly.
Stefano (Qualcomm) provides r02.
Patrice (Huawei) thanks Stefano for the r02 update, which is OK.
alessio(nokia) comments on r02 ans asks for a small update.
Stefano (Qualcomm) thanks Patrice and Alessio, provides r03.
Patrice (Huawei) thanks Stefano (Qualcomm) for the update, is OK with r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.14 S2-2203092 P-CR Approval 23.700-41: New solution on Key issue for WT#2 for Handling Rejected S-NSSAIs in some TAs of RA . Qualcomm Incorporated Rel-18 Revision of S2-2202349r03. Approved Approved
9.14 - - - Solution for KI#4 (NSAC) - - Docs:=7 -
9.14 S2-2202019 P-CR Approval 23.700-41: Solution for KI 4: Centralized Counting for Multi Service Areas and 5GS-EPS Interworking. Ericsson Rel-18 r01 agreed. Revised to S2-2203093 Fenqin (Huawei) provides comments
George (Ericsson) provides response
George (Ericsson) provides answers. Please see inline. Please note the subject for standardization her is the central node.
Fenqin (Huawei) provides comments and r01
George (Ericsson) provides a quick reply. See comments below
George (Ericsson) provides comments
Dongeun (Samsung) provides comments.
==== Revisions Deadline ====
George (Ericsson) can accept r01
==== Comments Deadline ====
Revised
9.14 S2-2203093 P-CR Approval 23.700-41: Solution for KI 4: Centralized Counting for Multi Service Areas and 5GS-EPS Interworking. Ericsson Rel-18 Revision of S2-2202019r01. Approved Approved
9.14 S2-2202540 P-CR Approval 23.700-41: KI#4: Hierarchical NSACF Architecture for maximum UE/PDU Session number control. Huawei, HiSilicon, China Mobile Rel-18 r03 agreed. Revised to S2-2203094 Fenqin (Huawei) provides feedback and r01
George Foti (Ericsson) provides comments
George (Ericsson) provides comments inline. I would also add that the distribution aspects are not part of this KI.
Fenqin (Huawei) provides response.
Chi (China Unicom) provides r02 with co-signing this p-CR.
George (Ericsson) provides response.
Fenqin (Huawei) provides feedback and r03
==== Revisions Deadline ====
George (Ericsson) can accept r03
==== Comments Deadline ====
Revised
9.14 S2-2203094 P-CR Approval 23.700-41: KI#4: Hierarchical NSACF Architecture for maximum UE/PDU Session number control. Huawei, HiSilicon, China Mobile, China Unicom Rel-18 Revision of S2-2202540r03. Approved Approved
9.14 S2-2202667 P-CR Approval 23.700-41: Solution for KI#4: Maximum Number Distribution in multiple NSACFs. ZTE Rel-18 r02 agreed. Revised to S2-2203095 George Foti (Ericsson) provides comments
Jinguo(ZTE) replies to Georg (Ericsson)
George (Ericsson) provides comments
Jinguo(ZTE) replies to George (Ericsson)
Jinguo(ZTE) replies to George (Ericsson) and provides r01
George (Ericsson) r01 is OK with the EN
Dongeu (Samsung) comments
Jinguo(ZTE) replies to Dongeu (Samsung)
Dongeun (Samsung) provides r02 and comments.
Jinguo(ZTE) is ok with r02
==== Revisions Deadline ====
George (Ericsson) would like this noted. It does not solve the problem
Jinguo(ZTE) replies to George (Ericsson) and suggests to approve r02.
Alessio(Nokia) supports documenting r02
George (Ericsson) provides comments. This can be added to 2540 at the next meeting. As I said, and U confirmed this does not solve the main issue here.
Jinguo(ZTE) suggust to approve r02 with adding an editor note
==== Comments Deadline ====
Revised
9.14 S2-2203095 P-CR Approval 23.700-41: Solution for KI#4: Maximum Number Distribution in multiple NSACFs. ZTE Rel-18 Revision of S2-2202667r02. Approved Approved
9.14 S2-2202759 P-CR Approval 23.700-41: A New Solution for KI#4: Support of Service Continuity in Multiple NSACF environment. Samsung Rel-18 Noted George Foti (Ericsson) provides comments
Iskren (NEC) comments
Jinguo(ZTE) comments
Jinguo(ZTE) comments that r01 doesnt work
Dongeun (Samsung) clarifies to Ericsson, NEC, and ZTE
Fenqin(Huawei) share the same view as Jinguo
Dongeun (Samsung) provides r02
Jinguo(ZTE) replies to Dongeun (Samsung)
Fenqin(Huawei) comments and still think the update solution not work.
Dongeun (Samsung) replies and provides r03.
George (Ericsson) asks question.
Dongeun (Samsung) replies to George (Ericsson)
Jinguo(ZTE) insists that the SMF part should be removed.
Dongeun (Samsung) provides r04
Fenqin(Huawei) comments and think the issue still not resolved.
Dongeun (Samsung) replies to Fenqin(Huawei)
George (Ericsson) provides comments
Alessio(nokia) comments ad requests to note
==== Revisions Deadline ====
George (Ericsson) would like this noted as it does not solve the problem.
==== Comments Deadline ====
Noted
9.14 - - - Documents exceeding TU Budget - - Docs:=13 -
9.14 S2-2202669 P-CR Approval 23.700-41: FS_eNS_Ph3: requirement on Allowed NSSAI. ZTE Rel-18 Not Handled Not Handled
9.14 S2-2202763 P-CR Approval 23.700-41: New key issue for objective #2: Improved support of RAs including TAs supporting Rejected S-NSSAIs. Orange Rel-18 Not Handled Not Handled
9.14 S2-2202541 P-CR Approval 23.700-41: New Key issue for WT#4: Actual Activity or Usage-based Slice Admission control. Huawei, HiSilicon Rel-18 Not Handled Alessio(nokia) proposes to note this paper with some motivations
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.14 S2-2202539 P-CR Approval 23.700-41: Remove the EN on KI#4. Huawei, HiSilicon Rel-18 Not Handled alessio(Nokia) provides r01
Jinguo(ZTE) points this paper is out of quota ..
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.14 S2-2202055 P-CR Approval 23.700-41: New Solution for Objective: 2: Handling Rejected S-NSSAIs in some TAs of RA. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.14 S2-2202073 P-CR Approval 23.700-41: 23.700-41: Solution to WT#2_Updating UE's behaviour of rejected slice due to not supported in RA. Samsung Rel-18 Not Handled Not Handled
9.14 S2-2202754 P-CR Approval 23.700-41: Solution: KI#X Improved support of RAs including TAs supporting Rejected S-NSSAIs. NEC Rel-18 Not Handled Not Handled
9.14 S2-2202861 P-CR Approval 23.700-41: Solution for WT#2: providing UE with partially available S-NSSAI per TA. Lenovo, Motorola Mobility Rel-18 Not Handled Not Handled
9.14 S2-2202914 P-CR Approval 23.700-41: New Sol for KI#X: Support of network slices with TA granularity within a RA. Apple Rel-18 Not Handled Not Handled
9.14 S2-2202945 P-CR Approval 23.700-41: TR Objective: #2: New Solution: Enabling Flexible RAs with Slice Service Area. InterDigital Inc. Rel-18 Not Handled Not Handled
9.14 S2-2202020 P-CR Approval 23.700-41: Solution KI for WT#4: Network Control for UE Slice Use. Ericsson Rel-18 Not Handled Not Handled
9.14 S2-2202072 P-CR Approval 23.700-41: 23.700-41: Solution to WT#4_Controlling network slice based on UE's actual usage. Samsung Rel-18 Not Handled Not Handled
9.14 S2-2202904 P-CR Approval 23.700-41: New Sol for KI#X: Slice-specific implicit deactivation timers. Apple Rel-18 Not Handled Not Handled
9.15 - - - Study on 5G AM Policy (FS_AMP) - - Docs:=16 -
9.15 S2-2201972 P-CR Approval 23.700-89: New Solution to KI#1: Enforcing RFSP index authorized by PCF in EPC via N26. Ericsson Rel-18 r02 agreed. Revised to S2-2203315 Haiyang (Huawei) provides r01 to merge 2061 into this pCR and co-signs.
Judy (Ericsson) thanks Haiyang (Huawei) and is fine with r01
Vivian (vivo) provides comments on original version and r01.
Zhuoyi (China Telecom) provides comments.
Judy (Ericsson) responds to Zhuoyi (China Telecom)
Zhuoyi (China Telecom) replies to Ericsson.
Judy (Ericsson) ask Zhuoyi (China Telecom) a question
Vivian (vivo) asks Judy (Ericsson) to response to my comments below.
Judy (Ericsson) responds to Vivian (vivo), apologize for the delay and provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.15 S2-2203315 P-CR Approval 23.700-89: New Solution to KI#1: Enforcing RFSP index authorized by PCF in EPC via N26. Ericsson, Huawei Rel-18 Revision of S2-2201972r02. Approved Approved
9.15 S2-2201973 P-CR Approval 23.700-89: New solution to KI#1, Enforcing RFSP index authorized by PCF in EPC without N26 interface. Ericsson Rel-18 r01 agreed. Revised to S2-2203316 Haiyang (Huawei) proposes to merge this pCR into S2-2202061.
Judy (Ericsson) responds to Haiyang (Huawei) that the key interaction between AMF with UDM is different in 1973 and 2061, thus I prefer to keep them separate, explained
Haiyang (Huawei) comments.
Zhuoyi (China Telecom) comments.
Judy (Ericsson) responds to Zhuoyi (China Telecom)
Judy (Ericsson) provides r01 and responds to Zhuoyi (China Telecom)
Zhuoyi (China Telecom) responds to Judy.
Judy (Ericsson) respond and ask question
==== Revisions Deadline ====
Zhuoyi (China Telecom) asks Judy (Ericsson) for further clarification.
Zhuoyi (China Telecom) replies.
Ashok (Samsung) comments
Judy (Ericsson) responds to Ashok (Samsung)
==== Comments Deadline ====
Revised
9.15 S2-2203316 P-CR Approval 23.700-89: New solution to KI#1, Enforcing RFSP index authorized by PCF in EPC without N26 interface . Ericsson Rel-18 Revision of S2-2201973r01. Approved Approved
9.15 S2-2202036 P-CR Approval 23.700-89: Solution for KI#1: Direct interface between PCF and MME. Qualcomm Incorporated Rel-18 Noted Pallab (Nokia) comments and thinks that the proposed solution is not within the scope of the Study
Zhuoyi (China Telecom) provides comments
Belen (Ericsson) provides comments
Pallab (Nokia) objects to the solution as it is clearly not in the scope of the agreed SID
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.15 S2-2202043 P-CR Approval 23.700-89: Update on TR23700-89 Solution #1. China Telecom Rel-18 r01 agreed. Revised to S2-2203317 Belen (Ericsson) provides comments
Zhuoyi (China Telecom) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.15 S2-2203317 P-CR Approval 23.700-89: Update on TR23700-89 Solution #1. China Telecom Rel-18 Revision of S2-2202043r01. Approved Approved
9.15 S2-2202061 P-CR Approval 23.700-89: New Solution for Key Issue#1: Authorized RFSP index provisioning from 5GC to MME. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203318 Judy (Ericsson) proposes to merge the solution for N26 to 01972, i.e. this paper keeps only the solution for no N26 deployment.
Haiyang (Huawei) agrees to Judy (Ericsson) to merge the N26 based solution into S2-2201972 and provides r01. And suggests to merge S2-2201973 into this one.
Zhuoyi (China Telecom) provides comments.
==== Revisions Deadline ====
Haiyang (Huawei) suggests to go with r01.
==== Comments Deadline ====
Revised
9.15 S2-2203318 P-CR Approval 23.700-89: New Solution for Key Issue#1: Authorized RFSP index provisioning from 5GC to MME . Huawei, HiSilicon Rel-18 Revision of S2-2202061r01. Approved Approved
9.15 S2-2202069 P-CR Approval 23.700-89: 23.700-89: Updated RFSP when UE is already moved to EPS with N26 interface. Samsung Rel-18 r03 agreed. Revised to S2-2203319 Belen (Ericsson) provides comments
Ashok (Samsung) replies to Belen (Ericsson)
Haiyang (Huawei) provides a question
Vivian (vivo) provides comments
Ashok (Samsung) replies to Haiyang(Huawei) and Vivian (vivo)
Ashok (Samsung) responds to Belen (Ericsson) and provides r01
Belen (Ericsson) asks to update the solution to address our comments.
Belen (Ericsson) provides comments.
Ashok (Samsung) provides r03
Ashok (Samsung) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.15 S2-2203319 P-CR Approval 23.700-89: 23.700-89: Updated RFSP when UE is already moved to EPS with N26 interface. Samsung Rel-18 Revision of S2-2202069r03. Approved Approved
9.15 S2-2202070 P-CR Approval 23.700-89: 23.700-89: Updated RFSP when UE is already moved to EPS without N26 interface. Samsung Rel-18 Approved Vivian (vivo) provides comments
Ashok (Samsung) replies to Vivian (vivo)
Zhuoyi (China Telecom) ask for further clarification.
Belen (Ericsson) provides comments.
Ashok (Samsung) responds to Belen (Ericsson)
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.15 S2-2202342 P-CR Approval 23.700-89: New solution for KI#1 in TR23700-89 for without N26 interworking. China Telecom Rel-18 Approved Belen (Ericsson) provides comments
Zhuoyi (China Telecom) replies to Ericsson's questions.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.15 S2-2202394 P-CR Approval 23.700-89: FS_AMP, KI#1, New solution for KI#1. Vivo Rel-18 r01 agreed. Revised to S2-2203320 Belen (Ericsson) provides comments
Vivian (vivo) replies to Belen (Ericsson)'s comments.
Belen (Ericsson) replies to Vivo, objects to r01 and initial version.
Vivian(vivo) replies to Belen (Ericsson)'s comments and provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.15 S2-2203320 P-CR Approval 23.700-89: FS_AMP, KI#1, New solution for KI#1. Vivo Rel-18 Revision of S2-2202394r01. Approved Approved
9.15 S2-2202456 P-CR Approval 23.700-89: 23.700-89: Solution for KI#1; Provide RFSP Index via N26 interface when the UE moves from 5GC to EPC. Nokia, Nokia Shanghai Bell Rel-18 Approved Approved
9.16 - - - Study on Personal IoT Networks (FS_PIN) - - Docs:=43 -
9.16 - - - New KI and solutions for Identification - - Docs:=2 -
9.16 S2-2202481 P-CR Approval 23.700-88: New KI and Solution: Identification assignment for PIN Elements. Vivo Rel-18 r03 agreed. Revised to S2-2203515 Marco (Huawei) asks questions
Zhenhua (vivo) replies to Marco (Huawei)
Jianning (Xiaomi) provides comments
Marco (Huawei) comment that KI Zhenhua (vivo) replies
LaeYoung (LGE) comments.
Zhenhua (vivo) replies to Qian (Ericsson)
Qian (Ericsson) provides comments
Zhenhua (vivo) provides r01
LaeYoung (LGE) provides further comment.
Zhenhua (vivo) provides r02
Jianning (Xiaomi) provide comments and provide r03
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r03.
Marco (Huawei) ok with r03 and objects to r00, r01, r02.
==== Comments Deadline ====
Revised
9.16 S2-2203515 P-CR Approval 23.700-88: New KI and Solution: Identification assignment for PIN Elements. Vivo Rel-18 Revision of S2-2202481r03. Approved Approved
9.16 - - - New Solution for KI#2 (Discovery) - - Docs:=9 -
9.16 S2-2202461 P-CR Approval 23.700-88: 23.700-88: Solution for KI#2; PIN elements Discovery within PIN using PC5 interface.. Nokia, Nokia Shanghai Bell Rel-18 Noted Zhenhua (vivo) ask Q for clarification
Marco (Huawei) asks questions
LaeYoung (LGE) thinks that the proposed solution is not scope of this study, so proposes to NOTE this paper.
Jianning (Xiaomi) provide comments
Xiaoyan Shi (interdigital) share same view with LaeYoung and proposes to NOTE this paper.
Pallab (Nokia) responds to interdigital, Xiaomi, LGE, Huawei.
Suresh Srinivasan (Intel) provides comments and questions
Jianning (Xiaomi) responses to Pallab (Nokia)
Pallab (Nokia) responds to Jianning (Xiaomi).
Pallab (Nokia) responds to Suresh Srinivasan (Intel).
marco (huawei) share view that is not in the scope as proposed.
Pallab (Nokia) responds to marco (huawei).
Pallab (Nokia) provides r01
LaeYoung (LGE) comments.
Pallab (Nokia) responds to LaeYoung (LGE)
Pallab (Nokia) provides r02 with EN as proposed
LaeYoung (LGE) replies to Pallab (Nokia).
LaeYoung (LGE) answers to Pallab (Nokia).
LaeYoung (LGE) proposes to NOTE this pCR.
==== Revisions Deadline ====
Marco (Huawei) agree to NOTE .
==== Comments Deadline ====
Noted
9.16 S2-2202506 P-CR Approval 23.700-88: KI#2: New Solution: PIN and PIN element discovery and selection. Apple Rel-18 r02 agreed. Revised to S2-2203516 Zhenhua (vivo) ask Q for clarification
Jianning (Xiaomi) provides questions for clarification
LaeYoung (LGE) comments.
Sudeep (Apple) provides r01 and responds to comments from vivo, Xiaomi and LGE.
Xiaoyan Shi (Interdigital) comments on Non-PINE.
Zhenhua (vivo) comments.
Suresh Srinivasan (Intel) provides comments and questions
marco (Huawei) provides comments
Jianning (Xiaomi) provides comments
Qian (Ericsson) provides comments
Sudeep (Apple) provides r02 and responds to comments from Huawei, Ericsson, Intel.
Sudeep (Apple) responds to Jianning (Xiaomi).
Jianning (Xiaomi) provide comment
Sudeep (Apple) responds.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r02.
==== Comments Deadline ====
Revised
9.16 S2-2203516 P-CR Approval 23.700-88: KI#2: New Solution: PIN and PIN element discovery and selection. Apple Rel-18 Revision of S2-2202506r02. Approved Approved
9.16 S2-2202874 P-CR Approval 23.700-88: KI#2: New solution for PIN and PIN element discovery and selection. Intel Rel-18 r02 agreed. Revised to S2-2203517 Marco (Huawei) asks questions and comments
Jianning (Xiaomi) provides comments
Suresh Srinivasan (Intel) replies to Jianning's (Xiaomi) comments
Suresh Srinivasan (Intel) replies to Marco's (Huawei) questions and comments
Suresh Srinivasan (Intel) provides r01.
Marco (Huawei) comment.
Jianning (Xiaomi) provide further questions for clarification
Pallab (Nokia) comments.
Suresh Srinivasan (Intel) answers Jianning's questions
Suresh Srinivasan (Intel) replies to marco's comment.
Suresh Srinivasan (Intel) Provides r02
Suresh Srinivasan (Intel) reply to Pallab's comments.
Jianning (Xiaomi) provide comment
==== Revisions Deadline ====
Suresh Srinivasan (Intel) replies to Jianning comment
==== Comments Deadline ====
Revised
9.16 S2-2203517 P-CR Approval 23.700-88: KI#2: New solution for PIN and PIN element discovery and selection. Intel Rel-18 Revision of S2-2202874r02. Approved Approved
9.16 S2-2202927 P-CR Approval 23.700-88: (KI#2) Solution for PIN and PIN Elements discovery and selection. Samsung Rel-18 r01 agreed. Revised to S2-2203518 Suresh Srinivasan (Intel) provides comments and questions
Lalith(Samsung) comments.
Pallab (Nokia) provides comments and questions
Lalith(Samsung) replies to Pallab (Nokia)
Lalith(Samsung) provides r01.
Pallab (Nokia) responds to Lalith(Samsung)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203518 P-CR Approval 23.700-88: (KI#2) Solution for PIN and PIN Elements discovery and selection. Samsung Rel-18 Revision of S2-2202927r01. Approved Approved
9.16 S2-2202951 P-CR Approval 23.700-88: Solution for KI#2: PIN and PIN Element discovery. Interdigital Rel-18 r01 agreed. Revised to S2-2203519 Zhenhua (vivo) ask Q for clarification
Marco (Huawei) asks question
Xiaoyan Shi (Interdigital) replies to Vivo and Huawei.
Suresh Srinivasan (Intel) provides comments and questions
Zhenhua (vivo) propose to merge S2-2202952 into this
Jianning (Xiaomi) provides comments
Marco (Huawei) comments.
Xiaoyan Shi (Interdigital) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203519 P-CR Approval 23.700-88: Solution for KI#2: PIN and PIN Element discovery. Interdigital Rel-18 Revision of S2-2202951r01. Approved Approved
9.16 - - - New Solution for KI#3 (Management) - - Docs:=12 -
9.16 S2-2202028 P-CR Approval 23.700-88: Solution of authorization and management of PIN and PIN Elements. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203520 Suresh Srinivasan (Intel) provides comments and questions
Marco (Huawei) provides comments and questions
Kefeng Zhang (Qualcomm) answers Qian (Ericsson), and provides r02.
Kefeng Zhang (Qualcomm) replies to Marco (Huawei) and Suresh (Intel), and provides r01.
Qian (Ericsson) provides comments and questions
Marco (Huawei) comments.
Kefeng Zhang (Qualcomm) replies to Marco (Huawei).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203520 P-CR Approval 23.700-88: Solution of authorization and management of PIN and PIN Elements. Qualcomm Incorporated Rel-18 Revision of S2-2202028r02. Approved Approved
9.16 S2-2202131 P-CR Approval 23.700-88: Solution for KI #3 Management of PIN and PIN Elements. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203521 Zhenhua (vivo) ask Q for clarification
Jianning (Xiaomi) asks questions for clarification
Marco (Huawei) answer to Jianning (Xiaomi)
Marco (Huawei) answer to Zhenhua (vivo)
Xiaoyan Shi (Interdigital) comments.
Zhenhua (vivo) comments
Suresh Srinivasan (Intel) Provides comments and question.
Qian (Ericsson) provides comments and questions
marco (huawei) provides r01
Marco (Huawei) answers to Suresh Srinivasan (Intel)
Marco (Huawei) answers to Zhenhua (vivo)
Marco (Huawei) answers Xiaoyan Shi (Interdigital)
Marco (Huawei)answer to Qian (Ericsson) and provide r
Kefeng Zhang (Qualcomm) asks questions for clarification.
Marco (Huawei) answer to Kefeng Zhang (Qualcomm)
Jianning (Xiaomi) provide comment
Marco (Huawei) agree to exclude roaming scenario support (i.e. roaming UE) from PIN study and to capture in assumption in next meeting
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203521 P-CR Approval 23.700-88: Solution for KI #3 Management of PIN and PIN Elements. Huawei, HiSilicon Rel-18 Revision of S2-2202131r01. Approved Approved
9.16 S2-2202460 P-CR Approval 23.700-88: 23.700-88: Solution for KI#3; PIN Management by 5GS. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203522 Zhenhua (vivo) ask Q for clarification
Jianning (Xiaomi) provides comments
Xiaoyan Shi (interdigital) provides comments
Suresh Srinivasan (Intel) provides comments and questions
Marco (Huawei) provides comments and questions
Pallab (Nokia) provides responses to all comments and uploads r01
Pallab (Nokia) responds to Marco (Huawei) and provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203522 P-CR Approval 23.700-88: 23.700-88: Solution for KI#3; PIN Management by 5GS. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202460r02. Approved Approved
9.16 S2-2202479 P-CR Approval 23.700-88: New Solution: Management PIN and PIN Elements. Vivo Rel-18 r04 agreed. Revised to S2-2203523 Suresh Srinivasan (Intel) provides comments and questions
Zhenhua (vivo) replies to Suresh Srinivasan (Intel)
Myungjune (LGE) asks question for clarification.
Qian (Ericsson) provides comments.
Jianning (Xiaomi) provides comment
Marco (Huawei) ask questions.
Myungjune (LGE) replies Zhenhua (vivo).
Zhenhua (vivo) replies to Myungjune (LGE)
Zhenhua (vivo) provides r02.
Zhenhua (vivo) replies to Qian (Ericsson)
Zhenhua (vivo) replies to Jianning (Xiaomi)
Zhenhua (vivo) replies to Marco (Huawei)
marco (huawei) answer to Jianning (Xiaomi)
Zhenhua (vivo) provides r03
Zhenhua (vivo) provides r04
Jianning (Xiaomi) provide comment
==== Revisions Deadline ====
Jianning (Xiaomi) is ok with r04
==== Comments Deadline ====
Revised
9.16 S2-2203523 P-CR Approval 23.700-88: New Solution: Management PIN and PIN Elements. Vivo Rel-18 Revision of S2-2202479r04. Approved Approved
9.16 S2-2202890 P-CR Approval 23.700-88: Solution for KI#3: one authorized UE creates a PIN. Xiaomi Rel-18 r05 agreed. Revised to S2-2203524 Jianning (Xiaomi) merges S2-2202893 into S2-2202890, and provide S2-2202890r01
Zhenhua (vivo) comments
Jianning (Xiaomi) replies to Zhenhua (vivo)
Jianning (Xiaomi) provides updated r03
Marco (huawei) asks questions and comments
Jianning (Xiaomi) response to Marco (Huawei)
Xiaoyan Shi (Interdigital) comments.
Suresh Srinivasan (Intel) provides comments and questions
Qian (Ericsson) provides comments
Jianning (Xiaomi) replies to Xiaoyan (Interdigital) and Suresh (Intel) and provide r04
Marco (Huawei) provides comments
Jianning (Xiaomi) response to Marco(Huawei) and Qian (Ericsson), and provide r05
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203524 P-CR Approval 23.700-88: Solution for KI#3: PIN management and PINE management. Xiaomi Rel-18 Revision of S2-2202890r05. Approved Approved
9.16 S2-2202895 P-CR Approval 23.700-88: KI#3: New solution for Management of PIN and PIN Elements. Intel Rel-18 r02 agreed. Revised to S2-2203525 Marco (huawei) asks questions and comments
Suresh Srinivasan (Intel) replies to Marco's questions and comments
Suresh Srinivasan (Intel) provides r01.
Zhenhua (vivo) ask Q for clarification
Suresh Srinivasan (Intel) answers Zhenhua Q
LaeYoung (LGE) asks a Q.
Zhenhua (vivo) suggest to add clause of impacts
Marco (Huawei) asks a Q.
Suresh Srinivasan (Intel) replies to LaeYoung's Q.
Suresh Srinivasan (Intel) replies to Marco's Q.
Suresh Srinivasan (Intel) Provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203525 P-CR Approval 23.700-88: KI#3: New solution for Management of PIN and PIN Elements. Intel Rel-18 Revision of S2-2202895r02. Approved Approved
9.16 - - - New Solution for KI#4 (Communication) - - Docs:=6 -
9.16 S2-2202026 P-CR Approval 23.700-88: Solutions for QoS control between PINE and 5GS when a PEGC is used for the relay. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203526 Marco (Huawei) asks question and comment
Jianning (Xiaomi) provide comments
Kefeng Zhang (Qualcomm) answers Marco (Huawei)
Kefeng Zhang (Qualcomm) answers Jianning (Xiaomi)
LaeYoung (LGE) comments.
Kefeng Zhang (Qualcomm) answers LaeYoung (LGE), and provides r01.
Suresh Srinivasan (Intel) provides comments and questions
Marco (Huawei) further comments
Kefeng Zhang (Qualcomm) replies Marco (Huawei) and provides r02.
Kefeng Zhang (Qualcomm) answers Suresh Srinivasan (Intel)
Pallab (Nokia) has a follow up question.
Kefeng Zhang (Qualcomm) answers Pallab (Nokia).
Jianning (Xiaomi) provides further comment
Kefeng Zhang (Qualcomm) replies Jianning (Xiaomi) .
==== Revisions Deadline ====
LaeYoung (LGE) thinks that r02 should be checked for approval instead of r00.
Jianning (Xiaomi) can live with r02.
Marco (Huawei) can accept r02 and object r00 & r01.
==== Comments Deadline ====
Revised
9.16 S2-2203526 P-CR Approval 23.700-88: Solution for QoS control between PINE and 5GS when a PEGC is used for the relay. Qualcomm Incorporated Rel-18 Revision of S2-2202026r02. Approved Approved
9.16 S2-2202480 P-CR Approval 23.700-88: New Solution: Communication of PIN. Vivo Rel-18 r04 agreed. Revised to S2-2203527 Marco (Huawei) asks questions
Zhenhua (vivo) replies to Marco (Huawei) and provides r01
Suresh Srinivasan (Intel) provides comments and questions
Myungjune (LGE) requests to update terminology
Jianning (Xiaomi) provide questions for clarification
Myungjune (LGE) replies to Zhenhua (vivo)
Zhenhua (vivo) replies to Myungjune (LGE)
Zhenhua (vivo) replies to Suresh Srinivasan (Intel) and provides r02
Zhenhua (vivo) provides r03
Qian (Ericsson) provides comments
Zhenhua (vivo) replies to Jianning (Xiaomi)
Zhenhua (vivo) provides r04
Jianning (Xiaomi) provide comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.16 S2-2203527 P-CR Approval 23.700-88: New Solution: Communication of PIN. Vivo Rel-18 Revision of S2-2202480r04. Approved Approved
9.16 S2-2202896 P-CR Approval 23.700-88: KI#4: New solution for communication of PIN. Intel Rel-18 r03 agreed. Revised to S2-2203528 Zhenhua (vivo) ask Q for clarification
Marco (Huawei) asks questions
Suresh Srinivasan (Intel) replies to Marco's (Huawei) questions
Suresh Srinivasan (Intel) clarifies Zhenhua's (vivo) Question
Suresh Srinivasan (Intel) provides r01.
Zhenhua (vivo) suggests to add clause of impacts
Marco (Huawei) comments and provide r02
Suresh Srinivasan (Intel) replies to Marco's comments and provides r03
Suresh Srinivasan (Intel) adds clause of impacts in r03
==== Revisions Deadline ====
Marco (Huawei) ok with r03
==== Comments Deadline ====
Revised
9.16 S2-2203528 P-CR Approval 23.700-88: KI#4: New solution for communication of PIN. Intel Rel-18 Revision of S2-2202896r03. Approved Approved
9.16 - - - Documents exceeding TU Budget - - Docs:=14 -
9.16 S2-2202952 P-CR Approval 23.700-88: Solution for KI#2: PIN Elements with Gateway Capabilities (PEGC) discovery and selection. InterDigital Rel-18 Not Handled Not Handled
9.16 S2-2202893 P-CR Approval 23.700-88: Solution for KI#3 a device joins a PIN. Xiaomi Rel-18 Not Handled Not Handled
9.16 S2-2202027 P-CR Approval 23.700-88: Solution of Personal IoT Networks Architecture in 5GS. Qualcomm Incorporated Rel-18 Not Handled Not Handled
9.16 S2-2202482 P-CR Approval 23.700-88: New Solution: Architecture alternative for PIN. Vivo Rel-18 Not Handled Not Handled
9.16 S2-2202898 P-CR Approval 23.700-88: KI#1: New solution for 5GC architecture enhancements to support PIN. Intel Rel-18 Not Handled Not Handled
9.16 S2-2202459 P-CR Approval 23.700-88: 23.700-88: KI on Identification of PIN and PIN elements. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not Handled
9.16 S2-2202901 P-CR Approval 23.700-88: KI#5: New solution for PIN Authorization. Intel Rel-18 Not Handled Not Handled
9.16 S2-2202507 P-CR Approval 23.700-88: KI#6: New Solution: Policy and parameter provisioning framework for PIN. Apple Rel-18 Not Handled Not Handled
9.16 S2-2202899 P-CR Approval 23.700-88: KI#6: New solution for Policy and Parameters Provisioning for PIN. Intel Rel-18 Not Handled Not Handled
9.16 S2-2202926 P-CR Approval 23.700-88: (KI#6) Solution for provisioning in PEGC/PEMC. Samsung Rel-18 Not Handled Not Handled
9.16 S2-2202950 P-CR Approval 23.700-88: Solution for KI#6: PIN policy and parameters provisioning. Interdigital Rel-18 Not Handled Not Handled
9.16 S2-2202533 P-CR Approval 23.700-88: Correction on TR 23.700-88 KI#2. China Telecom Rel-18 Not Handled Not Handled
9.16 S2-2202891 P-CR Approval 23.700-88: Update the definition of PIN. Xiaomi Rel-18 Not Handled Not Handled
9.16 S2-2202892 P-CR Approval 23.700-88: Architecture Assumption. Xiaomi Rel-18 Not Handled Not Handled
9.17 - - - Study on evolution of IMS multimedia telephony service (FS_NG_RTC) - - Docs:=42 -
9.17 - - - Architectural assumptions - - Docs:=3 -
9.17 S2-2202015 P-CR Approval 23.700-78: Architectural Assumptions. Ericsson Rel-18 Merged into S2-2203336 Hao Dong (ZTE) comments.
Mu (Huawei) proposes to merge this doc into 2016.
George (Ericsson) provides r02. Please see responses in line
Rainer (Nokia) comments.
George (Ericsson) provides r01
Hao Dong (ZTE) comments: we prefer putting the proposed architecture within the solution one by one; it will be more convenient for readers to connect the procedures with architecture. So it is suggested to merge this paper into the solution paper. Thanks.
Yi (China Mobile) comments that architectural assumption clause should not contain solution option.
George (Ericsson) provides comments. We can consider this merged in 2016
Leo (Deutsche Telekom) agrees with China Mobile and ZTE, this text should be merged with / included in solution description
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.17 S2-2202513 P-CR Approval 23.700-87: Clarification on Architecture Assumptions and Principles. ZTE Rel-18 r01 agreed. Revised to S2-2203321 Hao Dong (ZTE) responds to George (Ericsson).
George Foti (Ericsson) provides comments
Antoine (Orange) provides r01.
Hao Dong (ZTE) is fine with r01.
==== Revisions Deadline ====
George (Ericsson) can accept r01.
Leo (Deutsche Telekom) supports r01.
==== Comments Deadline ====
Revised
9.17 S2-2203321 P-CR Approval 23.700-87: Clarification on Architecture Assumptions and Principles. ZTE Rel-18 Revision of S2-2202513r01. Approved Approved
9.17 - - - New/updated KI's - - Docs:=8 -
9.17 S2-2202014 P-CR Approval 23.700-78: TR 23.700-87: KI on service based architecture for IMS media control. Ericsson, T-Mobile USA Rel-18 r06 agreed. Revised to S2-2203322, merging S2-2202767 Yi (China Mobile) provides r04
Mu (Huawei) propose r03
George (Ericsson) provides r02
Hao Dong (ZTE) reminds George Foti (Ericsson).
George Foti (Ericsson) provides r01
George (Ericsson) provides r06. Added a note on IMS DC being the priority
Rainer (Nokia) asks for clarification.
Mu Li (Huawei) replies
George (Ericsson) provides comments. I am trying to progress this KI. I can return it. I tried to cover this aspect in the modified bullet 2.
Yi (China Mobile) comments.
Mu (Huawei) is ok with r06
Chris Joul (T-Mobile USA) is ok with r06
Ashok (Samsung) is ok with r06
==== Revisions Deadline ====
Yi (China Mobile) is fine with r06.
Leo (Deutsche Telekom) supports r06.
Rainer (Nokia) is ok with r06.
==== Comments Deadline ====
Revised
9.17 S2-2203322 P-CR Approval 23.700-78: TR 23.700-87: KI on service based architecture for IMS media control. Ericsson, T-Mobile USA Rel-18 Revision of S2-2202014r06, merging S2-2202767. Approved Approved
9.17 S2-2202767 P-CR Approval 23.700-87: Key Issue: service based architecture for IMS media control. Huawei, HiSilicon Rel-18 Merged into S2-2203322 George Foti (Ericsson) proposes to consider this merged into 2014r01
==== Revisions Deadline ====
Mu(Huawei) agrees to consider this merged into 2014r06
==== Comments Deadline ====
Merged
9.17 S2-2202022 P-CR Approval 23.700-87: Update of KI #1 to study policy control and charging of Data Channel. Qualcomm Incorporated Rel-18 Approved Yi (China Mobile) ask questions for clarification
Kefeng Zhang (Qualcomm) answers Yi (China Mobile)
Rainer (Nokia) asks for clarification.
Kefeng Zhang (Qualcomm) answers Rainer (Nokia)
==== Revisions Deadline ====
George (Ericsson) can accept the original.
Yi (China Mobile) can not accept the KI before it is clear what to do.
Kefeng Zhang (Qualcomm) replies to Yi (China Mobile).
Yi (China Mobile) responds.
==== Comments Deadline ====
Approved
9.17 S2-2202393 P-CR Approval 23.700-87: FS_MMTELin5G, KI#1, Update KI on Data Channel. Vivo Rel-18 Merged into S2-2202810 Yi (China Mobile) propose to merge 2393 into 2810.
Xiaobo (vivo) replies to Ji(China Mobile) and OK to merge 2393 into 2810 .
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.17 S2-2202810 P-CR Approval 23.700-87: Update on the NOTE of KI for Data Channel usage in IMS network. China Mobile Rel-18 Approved, merging S2-2202393 Yi (China Mobile) clarifies this is a different KI with 2014.
George Foti (Ericsson) proposes to consider this merged into 2014r01
Rainer (Nokia) comments.
Yi (China Mobile) responds to Rainer.
==== Revisions Deadline ====
George (Ericsson) accepts the original.
==== Comments Deadline ====
Approved
9.17 S2-2202264 P-CR Approval 23.700-87: New Solution for new key issue - IMS MRF Discovery and Selection using 5G-SBA NRF. T-Mobile USA Rel-18 r01 agreed. Revised to S2-2203323 George Foti (Ericsson) provides comments
Chris Joul (T-Mobile USA) Replies to Ericsson comments
Rainer (Nokia) comments.
Yi (China Mobile) comments.
Mu (Huawei) comments.
George (Ericsson) provides comments to Chris
Chris Joul (T-Mobile USA) Provides r01 and answers questions on the solution.
==== Revisions Deadline ====
George (Ericsson) can accept r01.
Yi (China Mobile) is fine with r01.
Mu (Huawei) is ok with r01
Rainer (Nokia) is ok with r01.
==== Comments Deadline ====
Revised
9.17 S2-2203323 P-CR Approval 23.700-87: New Solution for new key issue - IMS MRF Discovery and Selection using 5G-SBA NRF. T-Mobile USA Rel-18 Revision of S2-2202264r01. Approved Approved
9.17 - - - KI#1 solutions - - Docs:=13 -
9.17 S2-2202531 P-CR Approval 23.700-87: Solution of Data Channel Usage for A2P Scenario. ZTE Rel-18 r03 agreed. Revised to S2-2203324 Hao Dong (ZTE) responds to George (Ericsson) and provides r01.
George Foti (Ericsson) provides comments
George (Ericsson) provides comments. The solution still needs clarification. Please see below
Rainer (Nokia) comments.
Hao Dong (ZTE) responds to George (Ericsson) and Rainer (Nokia), and provides r02.
Hao Dong (ZTE) responds to George (Ericsson).
George (Ericsson) provides comments. NG.129 is a white paper and has no bearing on the discussion. We know that any AS can handle a session. This is a basic assumption that cant change. So U have to explain how this will work. The EN is fine. We will look at the details when available. We did also consider that but ruled it, as it can break how things work today.
Hao Dong (ZTE) responds to George (Ericsson) and provides r03.
George (Ericsson) provides response
==== Revisions Deadline ====
George (Ericsson) accepts r03.
==== Comments Deadline ====
Revised
9.17 S2-2203324 P-CR Approval 23.700-87: Solution of Data Channel Usage for A2P Scenario. ZTE Rel-18 Revision of S2-2202531r03. Approved Approved
9.17 S2-2202023 P-CR Approval 23.700-87: Solution of Data Channel usage in IMS network. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203325 Kefeng Zhang (Qualcomm) replies George Foti (Ericsson) and provides r01.
George Foti (Ericsson) provides comments
George (Ericsson) please see answers inline.
Kefeng Zhang (Qualcomm) replies George (Ericsson) inline.
George (Ericsson) provides comments inline.
Kefeng Zhang (Qualcomm) replies George (Ericsson), and provides r02.
Kefeng Zhang (Qualcomm) answers Xiaobo (vivo) and Hao Dong (ZTE).
Hao Dong (ZTE) comments.
Xiaobo (vivo) comments
==== Revisions Deadline ====
George (Ericsson) can accept r02.
==== Comments Deadline ====
Revised
9.17 S2-2203325 P-CR Approval 23.700-87: Solution of Data Channel usage in IMS network. Qualcomm Incorporated Rel-18 Revision of S2-2202023r02. Approved Approved
9.17 S2-2202605 P-CR Approval 23.700-87: Solution to IMS Data Channel Architecture and Procedures. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203608. George Foti (Ericsson) provides comments. Too many issues with this solution to be accepted. We need to agree on the principles first.
Rainer (Nokia) comments and asks for clarification.
Xiaobo (vivo) asks a question for clarification.
Mu (Huawei) replies
George (Ericsson) provides comments. Still missing updates.
Mu (Huawei) replies and provide r01
George (Ericsson) provides answers and ask another question.
Kefeng Zhang (Qualcomm) provides comments
George (Ericsson) ask questions and provides comment..
==== Revisions Deadline ====
George (Ericsson) can accept r01.
Kefeng Zhang (Qualcomm) is OK with r01.
Rainer (Nokia) also ok with r01.
==== Comments Deadline ====
Revised
9.17 S2-2203608 P-CR Approval 23.700-87: Solution to IMS Data Channel Architecture and Procedures. Huawei, HiSilicon Rel-18 Revision of S2-2202605r01. Approved Approved
9.17 S2-2202604 P-CR Approval 23.700-87: Solution to IMS Data Channel Capability Discovery. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203326 George Foti (Ericsson) provides comments
Mu (Huawei) provides r01 based on the comments
Xiaobo (vivo) asks a question for clarification .
Huawei(Mu) replies
George (Ericsson) provides comments
Mu (Huawei) replies
Ashok (Samsung) request for a clarification from Mu (Huawei)
George (Ericsson) provides comment.
Mu (Huawei) asks for clarification
George (Ericsson) provides response
Mu (Huawei) provide r02 based on comments
Ashok (Samsung) comments
Mu (Huawei) clarifies and provide r03
==== Revisions Deadline ====
George (Ericsson) can accept r03.
==== Comments Deadline ====
Revised
9.17 S2-2203326 P-CR Approval 23.700-87: Solution to IMS Data Channel Capability Discovery. Huawei, HiSilicon Rel-18 Revision of S2-2202604r03. Approved Approved
9.17 S2-2202606 DISCUSSION Discussion Discussion on interworking between a DCMTSI client in terminal and an MTSI client in terminal. Huawei, HiSilicon Rel-18 Noted George Foti (Ericsson) provides comments
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.17 S2-2202811 P-CR Approval 23.700-87: Solution of IMS DC capability negotiation. China Mobile Rel-18 r02 + EN: Whether the UE need to report DC capability list in registration request is FFS revised to S2-2203327 George Foti (Ericsson) provides comments
Rainer (Nokia) asks for clarification.
Yi (China Mobile) responds and provides r01.
Xiaobo (vivo) asks for question for clarification .
George (Ericsson) provides comments
Yi (China Mobile) responds to Kenny.
Yi (China Mobile) responds to Xiaobo.
Kefeng Zhang (Qualcomm) provides comments on DC capabilities.
Yi (China Mobile) responds to George and provides r02.
==== Revisions Deadline ====
George (Ericsson) can accept r02.
Kefeng Zhang (Qualcomm) provides comments.
Rainer (Nokia) agrees with Kenny (Qualcomm).
Yi (China Mobile) responds.
Rainer (Nokia) clarifies that he does not object to the PCR.
Kefeng Zhang (Qualcomm) objects any revisions of this pCR,
As an alternative, we can live with adding an EN to r02 as following:
'Whether the UE need to report DC capability list in registration request is FFS.'
Rainer (Nokia) supports Kenny's (Qualcomm) proposal.
==== Comments Deadline ====
Yi (China Mobile) responds and ask for clarification from Qualcomm.
Revised
9.17 S2-2203327 P-CR Approval 23.700-87: Solution of IMS DC capability negotiation. China Mobile Rel-18 Revision of S2-2202811r02 + changes. Approved Approved
9.17 S2-2202812 P-CR Approval 23.700-87: Solution on IMS network architecture enhancements to support functionalities associated with Data Channel. China Mobile Rel-18 r01 agreed. Revised to S2-2203328 George Foti (Ericsson) provides comments
Chris Joul (T-Mobile USA) provides comments
Xiaobo (vivo) provides comments and suggestions.
Rainer (Nokia) comments.
Yi (China Mobile) responds and provides r01.
George (Ericsson) provides comment.
==== Revisions Deadline ====
George (Ericsson) can accept r01
==== Comments Deadline ====
Revised
9.17 S2-2203328 P-CR Approval 23.700-87: Solution on IMS network architecture enhancements to support functionalities associated with Data Channel. China Mobile Rel-18 Revision of S2-2202812r01. Approved Approved
9.17 - - - KI#2 solutions - - Docs:=4 -
9.17 S2-2202546 P-CR Approval 23.700-87: Solution of AR Telephony Communication Based on Data Channel. ZTE Rel-18 r03 agreed. Revised to S2-2203329 George Foti (Ericsson) provides comments
Hao Dong (ZTE) responds to George (Ericsson) and provides r01.
Mu (Huawei) asks for clarification.
Hao Dong (ZTE) responds to Mu (Huawei).
Hao Dong (ZTE) responds to Rainer (Nokia).
Rainer (Nokia) asks for clarification.
George (Ericsson) provides comments. We are not agreeing to the event notification as proposed as the IMSA AS is not known ahead of time. Hence this cant work. I also think U need to add assumptions on the UEs. I don't still understand the role of the DC server here. What can be bootstrapped. WE need to at minimum add EN for these issues.
Hao Dong (ZTE) responds to George (Ericsson) and provides r03.
==== Revisions Deadline ====
George (Ericsson) can accept r03.
==== Comments Deadline ====
Revised
9.17 S2-2203329 P-CR Approval 23.700-87: Solution of AR Telephony Communication Based on Data Channel. ZTE Rel-18 Revision of S2-2202546r03. Approved Approved
9.17 S2-2202602 P-CR Approval 23.700-87: Solution: Supporting AR Communication Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2203330 George Foti (Ericsson) proposes not to include the solution in its current state. Please see additional comments
Chris Joul (T-Mobile USA) Adds further comments
Mu replies and provide r01 based on the comments
Chris Joul (T-Mobile USA) provides further comments
Xiaobo (vivo) provides comments on AR-M .
Mu (Huawei) provides r02
George (Ericsson) asks question.
Mu (Huawei) replies
George (Ericsson) provides comments,
Rainer (Nokia) comments.
Mu (Huawei) comments and provide r04 based on comments
George (Ericsson) provides a question
Mu (Huawei) replies and provide r05
== Revisions Deadline ==
George (Ericsson) can accept r05.
== Comments Deadline ==
Revised
9.17 S2-2203330 P-CR Approval 23.700-87: Solution: Supporting AR Communication. Huawei, HiSilicon Rel-18 Revision of S2-2202602r05. Approved Approved
9.17 - - - KI#3 solutions - - Docs:=8 -
9.17 S2-2202584 P-CR Approval 23.700-87: KI#3: Solution for third party specific user identities. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203331 George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
Mu (Huawei) asks for clarification
Rainer (Nokia) replies.
Mu (Huawei) comments
Mu (Huawei) replies to Rainer.
Ashok (Samsung) requests for clarification from Rainer (Nokia)
Rainer (Nokia) replies to Mu (Huawei).
Ashok (Samsung) comments
==== Revisions Deadline ====
George (Ericsson) can accept r01.
==== Comments Deadline ====
Revised
9.17 S2-2203331 P-CR Approval 23.700-87: KI#3: Solution for third party specific user identities. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202584r01. Approved Approved
9.17 S2-2202068 P-CR Approval 23.700-87: 23.700-87: Solution to KI#3_Verification of calling party when using third party specific identity. Samsung Rel-18 r02 agreed. Revised to S2-2203332 George Foti (Ericsson) provides comments
Ashok (Samsung) replies to George (Ericsson) and provides r01
Mu (Huawei) asks for clarifications
Rainer (Nokia) replies.
Ashok (Samsung) replies to Rainer (Nokia) and Mu (Huawei)
Ashok (Samsung) replies to Mu (Huawei)
Mu (Huawei) ask for clarification
Ashok (Samsung) responds to Rainer (Nokia)
George (Ericsson) asks a question
George (Ericsson) replies
George (Ericsson) provides comment
Ashok (Samsung) provides r02
George (Ericsson) asks a question.
George (Ericsson) replies.
Ashok (Samsung) replies.
==== Revisions Deadline ====
George (Ericsson) can accept r02.
==== Comments Deadline ====
Revised
9.17 S2-2203332 P-CR Approval 23.700-87: 23.700-87: Solution to KI#3_Verification of calling party when using third party specific identity. Samsung Rel-18 Revision of S2-2202068r02. Approved Approved
9.17 S2-2202024 P-CR Approval 23.700-87: Solution of SHAKEN based third-party specific user identities. Qualcomm Incorporated Rel-18 r05 agreed. Revised to S2-2203333 Kefeng Zhang (Qualcomm), replies to George Foti (Ericsson), and provides r01.
Mu (Huawei) comments
George Foti (Ericsson) provides comments
Kefeng Zhang (Qualcomm) replies to Mu (Huawei)
Rainer (Nokia) comments.
Kefeng Zhang (Qualcomm) replies to Rainer (Nokia)
Kefeng Zhang (Qualcomm) provides r02.
George (Ericsson) provides comments
Xiaobo (vivo) asks a question for clarification in terms of UE impacts.
Kefeng Zhang (Qualcomm) replies comments and provides r03.
Rainer (Nokia) asks for clarification.
Leo (Deutsche Telekom) provides comments.
Kefeng Zhang (Qualcomm) answers Rainer (Nokia).
Kefeng Zhang (Qualcomm) provides r04.
George (Ericsson) asks a question
Kefeng Zhang (Qualcomm) answers George (Ericsson) .
Rainer (Nokia) provides r05.
George (Ericsson) asks question.
Kefeng Zhang (Qualcomm) is OK with r05.
Kefeng Zhang (Qualcomm) replies George (Ericsson).
==== Revisions Deadline ====
George (Ericsson) can accept r04.
Leo (Deutsche Telekom) prefers r05.
Mu (Huawei) prefers r05, can accept r04.
Ashok (Samsung) comments: Where is r05 and who has provided it ?
Leo (Deutsche Telekom) replies to Ashok (Samsung): It was provided by Nokia, you find it in the revisions folder?
Ashok (Samsung) thanks Leo (Deutsche Telekom) and fine with r05
==== Comments Deadline ====
George (Ericsson) Ok with r05
Revised
9.17 S2-2203333 P-CR Approval 23.700-87: Solution of SHAKEN based third-party specific user identities. Qualcomm Incorporated Rel-18 Revision of S2-2202024r05. Approved Approved
9.17 S2-2202603 P-CR Approval 23.700-87: Solution: Supporting Third Party ID Access in IMS. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203334 George Foti (Ericsson) provides comments
Mu (Huawei) replies
Rainer (Nokia) comments.
Chris Joul (T-Mobile USA) Supplies comments
Mu (Huawei) replies and provide r01 to reflect previous comments
George (Ericsson) provides comments
Mu(Huawei) makes clarification
Ashok (Samsung) have some concerns on the solution
Ashok (Samsung) comments
Rainer (Nokia) replies.
George (Ericsson) provides reply
Mu (Huawei) replies, and provide r02
==== Revisions Deadline ====
George (Ericsson) can accept r02.
==== Comments Deadline ====
Revised
9.17 S2-2203334 P-CR Approval 23.700-87: Solution: Supporting Third Party ID Access in IMS. Huawei, HiSilicon Rel-18 Revision of S2-2202603r02. Approved Approved
9.17 - - - KI#4 solutions - - Docs:=1 -
9.17 S2-2202924 P-CR Approval 23.700-87: KI#4: Reference architecture to support Data Channel usage in IMS. Nokia, Nokia Shanghai Bell Rel-18 Approved George Foti (Ericsson) provides comments
Chris Joul (T-Mobile USA) suggests merging this paper with S2-2202015
Mu (Huawei) comments. Just to clarify DCS-M is not an MRF as we think the function of DCS-M is very much different from MRF.
George (Ericsson) provides comments. The DCS-M is the NEW MRF in the HWA solution. They don't want to enhance the MRF
Rainer (Nokia) replies.
Chris Joul (T-Mobile USA) Provides comments
George (Ericsson) provides comments. I don't see the difference. The triggers or interfaces are the only difference that I can tell.
Ashok (Samsung) comments
Rainer (Nokia) comments.
==== Revisions Deadline ====
Rainer (Nokia) don't accept merging 2924 into 2015 at this meeting.
==== Comments Deadline ====
Approved
9.17 - - - SBA KI solutions - - Docs:=5 -
9.17 S2-2202607 DISCUSSION Discussion Discussion on media plane SBI benefits. Huawei, HiSilicon Rel-18 Noted Mu (Huawei) replies.
George Foti (Ericsson) provides comments
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.17 S2-2202608 P-CR Approval 23.700-87: Solution: Applying service based principles to IMS media control interfaces for existing capabilities. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203335 George Foti (Ericsson) proposes to note the pCR. Please see additional comments
Mu (Huawei) replies
Rainer (Nokia) comments.
George (Ericsson) provides comments
Chris Joul (T-Mobile USA) Provides comments
Mu (Huawei) replies, I don't see how this will rewrite 23.228, if we only define service, it requires a few pages max.
George (Ericsson) we are not OK including this. It requires rewriting 23.228 to show how to use this Numf.
Mu (Huawei) provides r01
George (Ericsson) asks a question.
==== Revisions Deadline ====
Mu (Huawei) wants to verify whether the objection still hold after explanation.
==== Comments Deadline ====
Revised
9.17 S2-2203335 P-CR Approval 23.700-87: Solution: Applying service based principles to IMS media control interfaces for existing capabilities. Huawei, HiSilicon Rel-18 Revision of S2-2202608r01. Approved Approved
9.17 S2-2202016 P-CR Approval 23.700-78: WT #5: solution for IMS Media Support for DC Server. Ericsson Rel-18 r01 agreed. Revised to S2-2203336, merging S2-2202015 Mu (Huawei) asks for clarification
Kefeng Zhang (Qualcomm) asks for clarification.
George (Ericsson) provides comments, please see inline
George (Ericsson) provides response. U need a termination point for SDP for security purpose.. NO entity can just access the IMS AGW directly.
Kefeng Zhang (Qualcomm) asks more question for clarification.
George (Ericsson) provides comments. Bootstrapping is always needed according to TS 26.114.
Rainer (Nokia) replies.
George (Ericsson) provides answers
Rainer (Nokia) comments.
George (Ericsson) provides r0. It includes 2015. More responses
Mu (Huawei) comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.17 S2-2203336 P-CR Approval 23.700-78: WT #5: solution for IMS Media Support for DC Server. Ericsson Rel-18 Revision of S2-2202016r01, merging S2-2202015. Approved Approved
9.18 - - - Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) - - Docs:=47 -
9.18 - - - LSs - - Docs:=2 -
9.18 S2-2202013 LS OUT Approval UE capabilities for MBS Qualcomm Rel-18 r00 agreed. Revised to S2-2203020 Revised
9.18 S2-2203020 LS OUT Approval UE capabilities for MBS SA WG2 Rel-18 Revision of S2-2202013r00. Approved Approved
9.18 - - - KI update - - Docs:=1 -
9.18 S2-2202816 P-CR Approval 23.700-74: Update to Key Issue#4 on supporting MBS. China Mobile, China Southern Power Grid Rel-18 Noted Youngkyo(Samsung) questions.
Antoine (Orange) comments.
Josep (DT) comments, disagrees with the addition of this KI.
Thomas(Nokia) supports the concerns of Youngkyo, Antoine, and Josep.
Suggests noting this contribution
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.18 - - - General update - - Docs:=2 -
9.18 S2-2202865 P-CR Approval 23.700-47: Generic approach to supporting large number of Public Safety UEs in a cell. AT&T, FirstNet, Nokia, Nokia Shanghai-Bell Rel-18 r06 agreed. Revised to S2-2203096 Haris(Qualcomm) provides comments and revision r01
Shabnam (Ericsson) provides r02 for further inclusion of text, as the use case information is good to capture in an Annex.
Thomas(Nokia) supports the approach suggested by Shabnam (Ericsson)
Provides r03.
LiMeng (Huawei) provides r04 and asks question.
Haris(Qualcomm) provides r05
Shabnam (Ericsson) provides r06, consistent with Qualcomm comment I add an e.g., in front of RRC_INACTIVE since we should not force this already in the architectural assumptions and Ericsson cosigns the paper.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203096 P-CR Approval 23.700-47: Generic approach to supporting large number of Public Safety UEs in a cell. AT&T, FirstNet, Nokia, Nokia Shanghai-Bell, Ericsson Rel-18 Revision of S2-2202865r06. Approved Approved
9.18 - - - New Key Issue and related documents - - Docs:=5 -
9.18 S2-2202149 P-CR Approval 23.700-47: New Key Issue: Improvement on performance issues for public safety UEs. Ericsson Rel-18 r03 agreed. Revised to S2-2203097, merging S2-2202821 and S2-2202842 Thomas (Nokia) comments
LiMeng(Huawei) corrects the title of the email.
Robbie (Ericsson) provides r01.
Thomas (Nokia) provides r02.
Ihab Guirguis (FirstNet): We support r02 and we are OK with r01. Please add FirstNet as cosigner for r02.
LiMeng (Huawei) provides r03.
Thomas(Nokia) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203097 P-CR Approval 23.700-47: New Key Issue: Improvement on performance issues for public safety UEs. Ericsson, Nokia, Nokia Shanghai-Bell, FirstNet, Huawei, HiSilicon, ZTE Rel-18 Revision of S2-2202149r03, merging S2-2202821 and S2-2202842. Approved Approved
9.18 S2-2202348 DISCUSSION Discussion Enabling adoption of 5MBS for Public Safety in Rel-18. AT&T, FirstNet Rel-18 Noted Noted
9.18 S2-2202821 P-CR Approval 23.700-47: Key issue for high number of Public safety UEs (WT#5). Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2203097 Robbie (Ericsson) asks whether it is fine to accept a general statement in KI description as S2-2202149
Thomas(Nokia) replies to Robbie
Robbie (Ericsson) proposes to merge this paper to S2-2202149
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.18 S2-2202842 P-CR Approval 23.700-47: New KI#X on performance issues for high number of public safety UE. ZTE Rel-18 Merged into S2-2203097 Robbie (Ericsson) asks whether it is fine to accept a general statement in KI description as S2-2202149
Robbie (Ericsson) proposes to merge this paper to S2-2202149
LiMeng (Huawei) comments on the way forward.
Thomas(Nokia) replies to LiMeng (Huawei)
LiMeng (Huawei) replies to Thomas.
zhendong (ZTE) provides the response
==== Revisions Deadline ====
LiMeng (Huawei) suggests to merge this document into S2-2202149
zhendong (ZTE) is fine with the merge proposal
==== Comments Deadline ====
Merged
9.18 - - - Solutions of KI#1 - - Docs:=13 -
9.18 S2-2202154 P-CR Approval 23.700-47: New Solution for KI#1: AF providing assistance information. Ericsson Rel-18 r00 + changes agreed. Revised to S2-2203593. Xiaoyan (CATT) provides comments.
Judy (Ericsson) responds to Xiaoyan (CATT)
Youngkyo(Samsung) provides comments.
Thomas (Nokia) comments
Judy (Ericsson) responds to Thomas (Nokia)
Judy (Ericsson) responds to Youngkyo(Samsung)
==== Revisions Deadline ====
Thomas/Nokia) objects against r00,
suggest agreeing r00 with one additional change (for CC3)
Judy (Ericsson) provides post-dealine revision r01 to address Thomas (Nokia)'s comment
==== Comments Deadline ====
Revised
9.18 S2-2203593 P-CR Approval 23.700-47: New Solution for KI#1: AF providing assistance information . Ericsson Rel-18 Revision of S2-2202154r00 + changes.Approved Approved
9.18 S2-2202312 P-CR Approval 23.700-47: Solution for KI#1: MM procedure enhancements for multicast reception. CATT Rel-18 Noted Judy (Ericsson) comments
Xiaoyan (CATT) provides r01.
LiMeng (Huawei) asks question.
Xiaoyan (CATT) replies to LiMeng (Huawei).
zhendong (ZTE) comments
Thomas (Nokia) also questions that this relates to key issue 1
Xiaoyan (CATT) asks for clarifications from Thomas (Nokia) and zhendong (ZTE).
Thomas(Nokia) replies and provides r02 where he retains only aspects that relate to key issue 1
Object against r00 and r01
==== Revisions Deadline ====
zhendong (ZTE) responds to judy (ericsson)
zhendong (ZTE) is fine with r02
LiMeng (Huawei) is fine with r02 also.
Thomas (Nokia) objects against r02 because the remaining parts of the solution are also covered by solution 1
==== Comments Deadline ====
Noted
9.18 S2-2202542 P-CR Approval 23.700-47: KI#1: MBS session management for RRC Inactive state MBS data receiving UE. Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2203098 Xiaoyan (CATT) asks for clarification.
Haris(Qualcomm) provides comments
Fenqin(Huawei) provides responds.
Fenqin (Huawei) responds and provides r01.
Thomas (Nokia) and provides r02.
Judy (Ericsson) provides r03
Haris(Qualcomm) comments
Fenqin(Huawei) provides feedback and r04
Thomas(Nokia) provides r05
Fenqin(Huawei) provides feedback and r06
Thomas(Nokia) replies to Fenqin and provides r07
Fenqin(Huawei) provides feedback and suggest to go with r06.
Thomas(Nokia) is fine with r06.
==== Revisions Deadline ====
Val (AT&T) comments.
Fenqin (Huawei) responds to Val(AT&T).
Val(AT&T) responds to Fenqin (Huawei).
==== Comments Deadline ====
Revised
9.18 S2-2203098 P-CR Approval 23.700-47: KI#1: MBS session management for RRC Inactive state MBS data receiving UE. Huawei, HiSilicon Rel-18 Revision of S2-2202542r06. Approved Approved
9.18 S2-2202543 P-CR Approval 23.700-47: KI#1: Mobility Procedures for UE supporting RRC Inactive MBS data reception. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203099 Judy (Ericsson) comments
Fenqin (Huawei) provides response to Judy(Ericsson).
Judy (Ericsson) provides r01
Judy (Ericsson) provide r02 (due to corrupted r01)
Thomas(Nokia) comments that zipped file in r01 seems broken.
Asks Judy to provide a r02 with same content
Fenqin (Huawei) provides r03.
==== Revisions Deadline ====
Judy (Ericsson) is fine with r03, objects to r00
==== Comments Deadline ====
Revised
9.18 S2-2203099 P-CR Approval 23.700-47: KI#1: Mobility Procedures for UE supporting RRC Inactive MBS data reception. Huawei, HiSilicon Rel-18 Revision of S2-2202543r03. Approved Approved
9.18 S2-2202843 P-CR Approval 23.700-47: KI#1, adding a new solution on Multicast MBS data reception in RRC Inactive state. ZTE Rel-18 r02 agreed. Revised to S2-2203100 Judy (Ericsson) provides r01
LiMeng (Huawei) provides r02
==== Revisions Deadline ====
Judy (Ericsson) accetps r01, r02, does not agree r00.
==== Comments Deadline ====
Revised
9.18 S2-2203100 P-CR Approval 23.700-47: KI#1, adding a new solution on Multicast MBS data reception in RRC Inactive state. ZTE Rel-18 Revision of S2-2202843r02. Approved Approved
9.18 S2-2202864 P-CR Approval 23.700-47: Solution proposal for key issue 1 (inactive reception). Nokia, Nokia Shanghai Bell Rel-18 Noted Thomas (Nokia) provides r01
Judy (Ericsson) comments
Thomas (Nokia) replies to Judy
Fenqin (Huawei) provides comment and r02
Judy (Ericsson) provides r03
Xiaoyan (CATT) provides comments and questions the need of this solution.
Thomas(Nokia) replies to Xiaoyan and explains SA2 impacts of the solution.
Xiaoyan (CATT) provides r04.
==== Revisions Deadline ====
Judy (Ericsson) accepts r03, r04, objects to other revisions including r00
Xiaoyan (CATT) objects to all the revisions (including r00) of this pCR.
Thomas Nokia suggest agreeing r04 provided by Xiaoyan (CATT)
Asks Xiaoyan if he rejects his own revision?
Thomas(Nokia) suggest bringing this to CC if there is no timely response by Xiaoyan
Xiaoyan (CATT) confirms her objection also to r04.
Thomas (Nokia) replies to Xiaoyan
Comments that proposing an acceptable revision before the deadline and rejecting it afterwards is quite unfair.
Asks for CC3 treatment
TAO(VC) clarifies Xiaoyan whether also object r04 provided by Xiaoyan herself.
Xiaoyan (CATT) confirms also objection to r04.
==== Comments Deadline ====
Noted
9.18 S2-2202311 P-CR Approval 23.700-47: Update to Solution 1 for KI#1 multicast reception in RRC INACTIVE state. CATT Rel-18 Merged into S2-2203101 Haris(Qualcomm) provides comments
Thomas(Nokia) comments that there are overlaps and conflicts with S2-2202358 and that a merger might be advisable. Raises doubt regarding some proposed parameters
Judy (Ericsson) share similar view as Haris and comments
Xiaoyan (CATT) replies to the comments and is fine with merging into S2-2202358.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.18 S2-2202358 P-CR Approval 23.700-47: Solution update for RRC inactive MBS data reception. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203101, merging S2-2202311 Thomas (Nokia) provides r01
Judy (Ericsson) provides r02
Xiaoyan (CATT) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203101 P-CR Approval 23.700-47: Solution update for RRC inactive MBS data reception. Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CATT Rel-18 Revision of S2-2202358r03, merging S2-2202311. Approved Approved
9.18 - - - Solutions of KI#2 - - Docs:=10 -
9.18 S2-2202152 P-CR Approval 23.700-47: KI#2: New Solution: MOCN RAN Sharing. Ericsson Rel-18 r03 agreed. Revised to S2-2203102 Haris(Qualcomm) provides comments
Robbie (Ericsson) provides r01.
Youngkyo(Samsung) provides questions.
Robbie(Ericsson) replies to Youngkyo(Samsung)
Robbie(Ericsson) provides r02 and replies to Youngkyo(Samsung)
Youngkyo(Samsung) provides a comment.
Robbie (Ericsson) replies to LiMeng (Huawei).
LiMeng (Huawei) asks question.
Robbie(Ericsson) provides r03 and replies to Youngkyo(Samsung)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203102 P-CR Approval 23.700-47: KI#2: New Solution: MOCN RAN Sharing. Ericsson Rel-18 Revision of S2-2202152r03. Approved Approved
9.18 S2-2202558 P-CR Approval 23.700-47: KI#2, New Sol: Allocating and using MOCN TMGI. LG Electronics Rel-18 r03 agreed. Revised to S2-2203103 Haris(Qualcomm) provides comments
Youngkyo(Samsung) comments
Robbie (Ericsson) asks a question.
LaeYoung (LGE) provides r01.
LaeYoung (LGE) responds to Robbie (Ericsson).
Haris(Qualcomm) comments and provides r02
LaeYoung (LGE) provides r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203103 P-CR Approval 23.700-47: KI#2, New Sol: Allocating and using MOCN TMGI. LG Electronics Rel-18 Revision of S2-2202558r03. Approved Approved
9.18 S2-2202743 P-CR Approval 23.700-47: Solution on 5MBS MOCN Network Sharing (Key issue #2) Samsung Rel-18 r01 agreed. Revised to S2-2203104 Robbie (Ericsson) asks questions
Youngkyo(Samsung) replies
Youngkyo(Samsung) replies and provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203104 P-CR Approval 23.700-47: Solution on 5MBS MOCN Network Sharing (Key issue #2). Samsung Rel-18 Revision of S2-2202743r01. Approved Approved
9.18 S2-2202151 P-CR Approval 23.700-47: KI#2: Update Solution#2: Procedures for MOCN network sharing. Ericsson Rel-18 r02 agreed. Revised to S2-2203105, merging S2-2202565 Robbie (Ericsson) provides r01.
Robbie (Ericsson) is fine with r02.
LiMeng (Huawei) answers and provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203105 P-CR Approval 23.700-47: KI#2: Update Solution#2: Procedures for MOCN network sharing. Ericsson, LG Electronics Rel-18 Revision of S2-2202151r02, merging S2-2202565. Approved Approved
9.18 S2-2202565 P-CR Approval 23.700-47: KI#2, Sol#2: Update to add EN. LG Electronics Rel-18 Merged into S2-2203105 Robbie (Ericsson) proposes to merge this paper to S2-2202151
LaeYoung (LGE) is fine to merge this pCR to S2-2202151 (Ericsson).
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.18 S2-2202359 P-CR Approval 23.700-47: Solution update of MOCN broadcasting. Huawei, HiSilicon Rel-18 Approved Approved
9.18 - - - Solutions of KI#3 - - Docs:=4 -
9.18 S2-2202477 P-CR Approval 23.700-47: New Solution: AF triggered MBS session management. Vivo Rel-18 r06 agreed. Revised to S2-2203106 Judy (Ericsson) ask questions
Zhenhua (vivo) responds to Judy (Ericsson)
Haris(Qualcomm) provides comments
Zhenhua (vivo) replies to Haris(Qualcomm) and provide r01
Judy (Ericsson) responds to Zhenhua (vivo)
Thomas(Nokia) provides r02
Zhenhua (vivo) provides r03 to address comments from Judy and Thomas
Zhenhua (vivo) provides r06 and ask to ignore r05
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203106 P-CR Approval 23.700-47: New Solution: AF triggered MBS session management. Vivo Rel-18 Revision of S2-2202477r06. Approved Approved
9.18 S2-2202630 P-CR Approval 23.700-47: Solution on enabling the on-demand multicast MBS session management. China Mobile, CATT Rel-18 r01 agreed. Revised to S2-2203107 Judy (Ericsson) asks questions and comments.
Haris(Qualcomm) provides comments
Xiaoyan (CATT) provides r01 to address the comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203107 P-CR Approval 23.700-47: Solution on enabling the on-demand multicast MBS session management. China Mobile, CATT Rel-18 Revision of S2-2202630r01. Approved Approved
9.18 - - - Solutions of KI#4 - - Docs:=4 -
9.18 S2-2202150 P-CR Approval 23.700-47: KI#4: New Solution: Group Message Delivery. Ericsson Rel-18 r01 agreed. Revised to S2-2203108 Haris(Qualcomm) provides r01
Robbie(Ericsson) is fine with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203108 P-CR Approval 23.700-47: KI#4: New Solution: Group Message Delivery. Ericsson Rel-18 Revision of S2-2202150r01. Approved Approved
9.18 S2-2202360 P-CR Approval 23.700-47: New solution for MBS group message delivery. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203109 Robbie (Ericsson) asks a question
Robbie (Ericsson) re-send with fixed AI#9.18
Haris(Qualcomm) comments
Thomas (Nokia) provides r01
Robbie (Ericsson) provides r02.
LiMeng (Huawei) accepts r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203109 P-CR Approval 23.700-47: New solution for MBS group message delivery. Huawei, HiSilicon Rel-18 Revision of S2-2202360r02. Approved Approved
9.18 - - - Solutions of KI#5 - - Docs:=2 -
9.18 S2-2202012 P-CR Approval 23.700-47: Solution for Key Issue#5 (MBS coexistence with power saving mechanisms). Qualcomm Incorporated Rel-18 Approved Approved
9.18 S2-2202155 P-CR Approval 23.700-47: KI#5: New Solution to Coexistence with existing power saving mechanisms for capability-limited devices. Ericsson Rel-18 Approved Approved
9.18 - - - Solutions of new key issue - - Docs:=4 -
9.18 S2-2202011 P-CR Approval 23.700-47: WT5: Solution for handling large number of devices in a specific area for public safety. Qualcomm Inc. Rel-18 Revision of (Postponed) S2-2201212 from S2#149E. r02 agreed. Revised to S2-2203110 Robbie (Ericsson) asks
Robbie(Ericsson) comments.
Haris(Qualcomm) replies
Robbie (Ericsson) asks one more question
Thomas(Nokia) provides r01.
Haris(Qualcomm) responds
Robbie(Ericsson) provides suggestions.
Haris(Qualcomm) provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203110 P-CR Approval 23.700-47: WT5: Solution for handling large number of devices in a specific area for public safety. Qualcomm Inc. Rel-18 Revision of S2-2202011r02. Approved Approved
9.18 S2-2202153 P-CR Approval 23.700-47: New Solution to new KI: Performance Improvement for Public Safety. Ericsson Rel-18 r06 agreed. Revised to S2-2203111 Thomas (Nokia) provides r01, raises concerns that part of the suggested solution are beyond the scope of the Rel-18 study
Robbie (Ericsson) provides r02 and clarifies to Thomas (Nokia)
Thomas(Nokia) objects against r02 and replies to Robbie
Fenqin (Huawei) ask a question for clarification
Haris(Qualcomm) comments
Robbie (Ericsson) provides r03.
Val (AT&T) comments
Fenqin (Huawei) provides r04.
Thomas (Nokia) provides r05. Objects aqainst earlier revisions
Robbie (Ericsson) provides r06.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.18 S2-2203111 P-CR Approval 23.700-47: New Solution to new KI: Performance Improvement for Public Safety. Ericsson Rel-18 Revision of S2-2202153r06. Approved Approved
9.19 - - - Study on XR (Extended Reality) and media services (FS_XRM) - - Docs:=86 -
9.19 - - - Architectural Assumption, new and updates Key issue - - Docs:=6 -
9.19 S2-2202878 P-CR Approval 23.700-60: PCR 23.700-60: Architectural assumption on the PDU Session for XRM services. MediaTek Inc. Rel-18 This was postponed Youngkyo(Samsung) comments.
Xiaowan (vivo) comments on r00 and r01
Youngkyo(Samsung) provide a revision.
Hui(Huawei) provides r01.
Dan(China Mobile) agree with r01
Yali (OPPO) indicates r01 is from Samsung.
Chia-Lin (MediaTek) provides r02
Hui (Huawei) provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.19 S2-2202855 P-CR Approval 23.700-60: Tactile Internet definition introduction. China Mobile Rel-18 Approved Approved
9.19 S2-2202713 P-CR Approval 23.700-60: Key Issue #7 Update: Clarifying that KI should also consider how to minimize jitter. InterDigital Inc. Rel-18 Noted Dario (Qualcomm) is not OK with this proposal because it extends the scope of the KI beyond the scope of the related WT.
Mike (InterDigital) disagrees with Dario (Qualcomm) and explains why
Devaki (Nokia) comments.
Devaki (Nokia) replies.
Dario (Qualcomm) replies to Devaki and Mike.
Shabnam (Ericsson) agrees with Qualcomm view, the added aspects are not needed. As the KI currently states, the scope is to define requirements for AF towards PCF and for PCF to see if enhancements can be made to address minimisation of jitter. It is up to the solutions to provide how and if that is achievable.
Saso (Intel) agrees with Ericsson and Qualcomm and proposes to NOTE the document. Similar discussion already took place in SA#94E during the prioritization exercise.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.19 S2-2202330 P-CR Approval 23.700-60: KI #4 update to clarify PDU set. Tencent, Tencent Cloud Rel-18 r05 agreed. Revised to S2-2203529 Xiaowan (vivo) provides comments
Youngkyo(Samsung) share the view from Mike.
Mike (InterDigital) expresses concerns about the update
Zhuoyun (Tencent) provides r01.
Hui (Huawei) provides comment.
Dan (China Mobile) provides comment.
Chris Joul (T-Mobile USA) Provides comments
Mike (InterDigital) comments
Dario (Qualcomm) provides comment.
Zhuoyun (Tencent) replies.
Devaki (Nokia) fine with r01.
Chunshan (CATT) provides r02.
Mike (InterDigital) provides r03
Dario (Qualcomm) provides r04
Shabnam (Ericsson) provides comments regarding some wrong wording changes that is being proposed and should be updated.
Zhuoyun (Tencent) provides r05 and r06.
Mike (InterDigital) is ok with r03, r04, and r05. Has concerns with r06. Provides r07
==== Revisions Deadline ====
Hui (Huawei) prefers to r05. Fine with r06.
Zhuoyun (Tencent) prefers to r06, r07 and r05.
Dario (Qualcomm) is OK w/ r05 and objects to r06 and r07
==== Comments Deadline ====
Revised
9.19 S2-2203529 P-CR Approval 23.700-60: KI #4 update to clarify PDU set. Tencent, Tencent Cloud Rel-18 Revision of S2-2202330r05. Approved Approved
9.19 S2-2202879 P-CR Approval 23.700-60: PCR 23.700-60: New KI and Solution for Usage of PDU Set feature in 5GS. MediaTek Inc. Rel-18 Noted Xiaowan (vivo) provides comments on KI part
Hui (Huawei) provides comments
Dan (China Mobile) provides comments
Chia-Lin (MediaTek) respond to Dan (China Mobile)
Chia-Lin (MediaTek) respond to Hui (Huawei)
Hui (Huawei) responses
Chunshan (CATT) thinks the proposed KI to be included in the KI#4.
Dario (Qualcomm) does not agree with this KI proposal.
Chia-Lin (MediaTek) responds to Dario (Qualcomm)
Devaki (Nokia) comments that we do not see the need for the newly proposed KI but ok with documenting the solution for KI#4/5.
Dario (Qualcomm) comments.
Shabnam (Ericsson) share same view as others that a new KI is not needed and the solution is not really a solution. I would think the usage of PDU set by network (different entities) and UE would be described as part of impacts to interfaces, UEs, NFs etc. would it not?
Chia-Lin (MediaTek) responds to Dario (Qualcomm), Shabnam (Ericsson), and Hui (Huawei) and provides r01
==== Revisions Deadline ====
Dario (Qualcomm) objects all versions of this paper.
Chia-Lin (MediaTek) disagrees the objection and responds to Dario (Qualcomm)
==== Comments Deadline ====
Noted
9.19 - - - Solutions for KI#1&2 - - Docs:=17 -
9.19 S2-2202084 P-CR Approval 23.700-60: Solutions for Key1: Tactile and multi-modality traffic flows coordination transmission for one UE. China Mobile Rel-18 r02 agreed. Revised to S2-2203530 Boren (OPPO) comments.
Dario (Qualcomm) comments.
Dan (China Mobile) reply
Devaki (Nokia) comments that there seems to be a wrong assumption that a QoS parameter such as delay exists.
Dan (China Mobile) reply and provide r01
Devaki (Nokia) replies.
Dan (China Mobile) provide r02 with adding the suggested sentence for this solution
==== Revisions Deadline ====
Dario (Qualcomm) is OK with r02 with the clarification that it does not impact RAN-CN signaling.
==== Comments Deadline ====
Revised
9.19 S2-2203530 P-CR Approval 23.700-60: Solutions for Key1: Tactile and multi-modality traffic flows coordination transmission for one UE . China Mobile Rel-18 Revision of S2-2202084r02. Approved Approved
9.19 S2-2202107 P-CR Approval 23.700-60: Solution for KI#1 handling multiple QoS flows of one UE together. Vivo Rel-18 This was postponed Xinpeng(Huawei) comments.
Dan(China Mobile) comments.
Xiaowan (vivo) provides r01
Youngkyo(Samsung) comments
Xiaowan (vivo) replies to Youngkyo(Samsung)
Dario (Qualcomm) explains why this proposal is out of scope of the KI.
Xiaowan(vivo) replies Dario (Qualcomm) that handling the QoS flow together belongs to policy control to support QoS policy coordination between multiple QoS flows
Dan(China Mobile) replies Dario and think the policy control related functionaliy in SMF,UPF,RAN is in the scope of this KI
Jinhua(Xiaomi) provides comments, with r03,
Jinhua(Xiaomi) provides r04
==== Revisions Deadline ====
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Dan (China Mobile) states that this solution is within the scope of this KI
Mike (InterDigital) agrees with Dan and points out that the SID (SP-211646) says that WT#1 may have RAN impact.
Xiaowan(vivo) seconds Dan (China Mobile) and Mike (InterDigital) that the solution is in the scope and asks for CC#3. Furthermore, KI#1&KI#2 are from WT#1.1, possible impacts on AF, PCF, RAN are not excluded and the NFs between RAN and PCF may be impacted as well. The same reply is applied to 'out of scope' comments on S2-2202750/S2-2202746/S2-2202714/S2-2202371/S2-2202305/S2-2202269/S2-2202107.
==== Comments Deadline ====
Postponed
9.19 S2-2202269 P-CR Approval 23.700-60: Solution for KI#1,2 on multi-modality flows coordinated transmission. OPPO Rel-18 This was postponed. Dan (China Mobile) asks a question.
Boren (OPPO) replies to Dan (China Mobile) and provides r01.
Xinpeng(Huawei) ask questions for clarification.
Xinpeng(Huawei) ask to add an EN.
Boren (OPPO) replies to Xinpeng (Huawei) and provides r02.
Dario (Qualcomm)
Boren (OPPO) replies to Xinpeng (Huawei).
Boren (OPPO) replies to Dario (Qualcomm), and provides r03.
Dan (China Mobile ) replies to Dario (Qualcomm). and clearly say this impact for SMF/UPF/RAN is in the KI scope
==== Revisions Deadline ====
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Boren (OPPO) disagrees with Dario (Qualcomm), since the SMF/UPF/RAN impacts are not excluded by the KI nor the WT. Believes that this paper and other papers received similar objections are within scope.
Dan (China Mobile) states that this solution is within the scope of this KI
Yali (OPPO) asks to discuss this paper on CC#3.
==== Comments Deadline ====
Postponed
9.19 S2-2202305 P-CR Approval 23.700-60: KI#1, KI#2 Solution proposal: Policy Control enhancements for multi-modal traffic. Nokia, Nokia Shanghai Bell Rel-18 This was postponed. Saso (Intel) seeks clarification.
Devaki (Nokia) replies.
Chris Joul (T-Mobile USA) provides comments
Youngkyo(Samsung) comments.
Saso (Intel) provides r01.
Boren (OPPO) comments.
Devaki (Nokia) comments.
Devaki (Nokia) is fine with r01 and replies to Boren.
Dario (Qualcomm) believes the solution is out of scope of the KI because it impacts more than just policies/policy control.
Devaki (Nokia) replies that there is a misunderstanding with QCOM's comment related to the scope of the WT and KI. Policy enhancements does not preclude RAN impact (in fact, one fundamental policy is about 5QI for which RAN is the key consumer).
Boren (OPPO) provides r02.
Dan (China Mobile ) replies to Dario (Qualcomm). and clearly say this impact for SMF/UPF/RAN is in the KI scope
==== Revisions Deadline ====
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Dan (China Mobile) states that this solution is within the scope of this KI
==== Comments Deadline ====
Postponed
9.19 S2-2202371 P-CR Approval 23.700-60: Solution: QoS enhancement to support synchronized delivery of multiple QoS flows. Huawei, HiSilicon Rel-18 This was postponed. Youngkyo(Samsung) ask a question.
Boren (OPPO) asks for clarification
Xinpeng(Huawei) Replies to Youngkyo(Samsung).
Saso (Intel) seeks clarification.
Boren (OPPO) comments.
Xinpeng(Huawei) replies to Boren (OPPO).
Saso (Intel) provides r02.
Xinpeng(Huawei) replies to Saso (Intel).
Xinpeng(Huawei) replies to Boren (OPPO) .
Dario (Qualcomm) believes the second part of this solution is out of scope of this KI.
Devaki (Nokia) comments that Qualcomm comment continues to have a misunderstanding of the KI scope. KI never stated it is limited to AF-PCF impact, in fact, QCOM comment renders the whole KI useless. Rapporteur should raise this in CC#2 if the KI is stalled due to this.
Mike (InterDigital) agrees with Devaki (Nokia)
Dan(China Mobile) support Devaki and agree that the policy control related functionaliy in SMF,UPF,RAN is in the scope of this KI#1&KI#2
Xinpeng(Huawei) share the same view with Dan(China Mobile), Devaki(Nokia) and Mike(InterDigital).
Youngkyo(Samsung) shares the same view with Dan(China Mobile), Devaki(Nokia), Xinpeng(Huawei) and Mike(InterDigital).
Xinpeng(Huawei) is fine with r02 and provides r03 with KT as cosigner.
==== Revisions Deadline ====
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Shabnam (Ericsson) we share Qualcomm view, the SA discussion was extensive and our understanding is that the scope is AF to PCF policy influence for application behaviour, rest of the system would be transparent.
Xinpeng(Huawei) ask to discuss this paper on CC#2 or CC#3.
Xinpeng(Huawei) replies to Dario.
Dan (China Mobile) states that this solution is within the scope of this KI
==== Comments Deadline ====
Postponed
9.19 S2-2202714 P-CR Approval 23.700-60: Key Issue #1 and Key Issue #2: New solution, Flow Association with a Session Identifier. InterDigital Inc. Rel-18 This was postponed. Xiaowan (vivo) provides comments
Mike (InterDigital) replies and provides r01.
dan (China Mobile) comment
Devaki (Nokia) comments that QCOM has a misunderstanding of KI#1/#2 (and the corresponding WT in SID).
Dario (Qualcomm) comments.
Mike (InterDigital) agrees with Devaki (Nokia) and replies to Dario (Qualcomm)
Dan (China Mobile ) replies to Dario (Qualcomm). and clearly say the impact for policy control(impact for SMF,UPF,RAN, UE etc) is in the KI scope
==== Revisions Deadline ====
Shabnam (Ericsson) supports Qualcomm. We had extensive discussion in SA on this and the scope is AF/PCF, via policy one can influence end to end behaviour but not impact additional entities as we do for other features without impacting entities or changing PCC impacted NFs/entities.
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Mike (InterDigital) points out that the SID (SP-211646) says that WT#1 may have RAN impact. Believes that this paper and the other papers the received similar objections are within scope. Proposes to discuss on CC#3.
Dan (China Mobile) states that this solution is within the scope of this KI
==== Comments Deadline ====
Postponed
9.19 S2-2202747 P-CR Approval 23.700-60: Solution on KI#1 and KI#2 for XR and media services KT Corp. Rel-18 To be Merged into S2-2202371 (Postponed). Postponed Xiaowan (vivo) provides comments
Youngkyo(Samsung) adds comments& questions.
Sungpyo(KT) provides a revision r01.
Dan(China Mobile) suggest this merged into S2-2202371
Dario (Qualcomm) asks questions for clarification
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.19 S2-2202746 P-CR Approval 23.700-60: Solution on multi-modality support for single UE (Key issue #1) Samsung Rel-18 This was postponed. Xiaowan (vivo) provides comments
Youngkyo(Samsung) provide a revision r01
Xinpeng(Huawei) comments.
Youngkyo(Samsung) replies to Xinpeng and provide r02..
Xinpeng(Huawei) replies to Youngkyo(Samsung).
Dan (China Mobile) comments.
Boren (OPPO) comments.
Dario (Qualcomm) believes this solution goes beyond the scope of the KI.
Mike (InterDigital) believes that this solution is well within the scope of the Key Issue.
Youngkyo(Samsung) replies and provide r03.
Dan (China Mobile ) replies to Dario (Qualcomm). and clearly say the impact for policy control(impact for SMF,UPF,RAN, UE etc) is in the KI scope
Xinpeng(Huawei) provides r04.
Youngkyo(Samsung) is okay to add the EN as r04 for now.
==== Revisions Deadline ====
Shabnam (Ericsson) Ericsson agrees with Qualcomm & we had extensive discussion at SA on scoping this down. AF and PCF in scope and influence towards rest of the system is to be transparent/reuse so we do not see that as impacts.
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Dan (China Mobile) states that this solution is within the scope of this KI
==== Comments Deadline ====
Postponed
9.19 S2-2202750 P-CR Approval 23.700-60: Solution on multi-modality support among multiple UEs (Key issue #2). Samsung Rel-18 This was postponed. Xiaowan (vivo) provides comments
Youngkyo(Samsung) provides some answer and a revision r01
Xinpeng(Huawei) comments.
Youngkyo(Samsung) replies to Xinpeng and provides r02..
Dan(LGE) comments.
LaeYoung (LGE) comments.
Youngkyo(Samsung) replies and provides r03.
Dario (Qualcomm) believes this solution goes beyond the scope of the KI.
Mike (InterDigital) believes that this solution is well within the scope of the Key Issue.
Dan (China Mobile) believes that this solution is well within the scope of the Key Issue.
Xinpeng(Huawei) provides r04.
Youngkyo(Samsung) is okay to add the EN as r04 for now.
==== Revisions Deadline ====
Dario (Qualcomm) objects to any version of this document because out of scope of the KI. Proposes to discuss this in CC#2/3.
Dan (China Mobile) states that this solution is within the scope of this KI
==== Comments Deadline ====
Postponed
9.19 S2-2202970 P-CR Approval 23.700-60: KI#1 and KI#2: Solution for application-layer based media-synchronization for multi-modality services. Qualcomm Incorporated Rel-18 This was postponed. Youngkyo(Samsung) comments.
Boren (OPPO) comments.
Dario (Qualcomm) replies to Boren and Youngkyo.
Boren (OPPO) comments..
dan(China Mobile) comment and provie r01
Youngkyo(Samsung) share the view from Boren
dan(China Mobile) reply
Yali (OPPO) replies to Dario (Qualcomm)
Devaki (Nokia) proposes to note this paper as there is really no need to study this solution in Rel-18 and/or in 3GPP. If the claim is that there is no solution needed, just propose a conclusion paper proposing to conclude the KI without any normative work, no need to document this solution.
Dario (Qualcomm) replies and provides r02
==== Revisions Deadline ====
Devaki (Nokia) objects to the solution as it simply references current specifications which needs no study, also unclear why and how this solves the problem statement proposed by the KI.
Xiaowan(vivo) replies to Dario (Qualcomm) that the solution shall be noted since it is not in the your scope principle as you repeated in 2202750/S2-2202746/S2-2202714/S2-2202371/S2-220230/S2-2202305/S2-2202269/S2-2202107
Saso (Intel) disagrees with Devaki. A solution with no normative impact is still a valid solution and should be documented if it addresses the KI; specific to this solution, it addresses the coordinated transmission of multi-modality flows (KI#1 and KI#2).
Xinpeng(Huawei) share the same view as Devaki(Nokia) and propose to note this paper.
Dan(China Mobile) share the same view as others and propose to note this paper.
==== Comments Deadline ====
Dario (Qualcomm) points out that the solution is in scope of the KI and asks to discuss this in CC#3.
Postponed
9.19 S2-2202856 P-CR Approval 23.700-60: Solution of KI#2 on Group policy for Multi-modal Traffic among Multiple UEs. Xiaomi Rel-18 r02 agreed. Revised to S2-2203531 Xiaowan (vivo) provides comments
Xinpeng(Huawei) comments.
Jinhua(Xiaomi) replies to Xiaowan with r01,
Dan(China Mobile) comments.
Jinhua(Xiaomi) replies to Xinpeng,
Jinhua(Xiaomi) replies to Dan,
Dario (Qualcomm) questions the baseline assumption for this scenario and solution.
Jinhua(Xiaomi) replies to Dario,
Dan(China Mobile) provide some thinking and maybe one PCF set can be used for multi-modality service
Jinhua(Xiaomi) replies to Dan, with r02 provided.
Dan(China Mobile) replies
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203531 P-CR Approval 23.700-60: Solution of KI#2 on Group policy for Multi-modal Traffic among Multiple UEs. Xiaomi Rel-18 Revision of S2-2202856r02. Approved Approved
9.19 S2-2202857 P-CR Approval 23.700-60: Solution of KI#2 on same PCF selection for Multiple UEs with XRM services. Xiaomi Rel-18 r01 agreed. Revised to S2-2203532 Xinpeng(Huawei) comments.
dan(China Mobile) comments.
Jinhua(Xiaomi) replies to Xinpeng,
Jinhua(Xiaomi) replies to Dan, with r01 provided,
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203532 P-CR Approval 23.700-60: Solution of KI#2 on same PCF selection for Multiple UEs with XRM services. Xiaomi Rel-18 Revision of S2-2202857r01. Approved Approved
9.19 S2-2202108 P-CR Approval 23.700-60: Solution for KI#2: QoS policy coordination for multiple UEs' QoS flows. Vivo Rel-18 r02 agreed. Revised to S2-2203533 Xinpeng(Huawei) comments.
Huazhang(vivo) replies to Xinpeng(Huawei)
Dan(China Mobile) provide comment
Youngkyo(Samsung) comments.
Xinpeng(Huawei) replies to Huazhang(vivo).
Huazhang(vivo) provides r01 and response to Youngkyo(Samsung) and Dan
Dario (Qualcomm) questions the scenario of the solution.
Huazhang (vivo) provides r02 and replies to Dario (Qualcomm) and Xinpeng(Huawei)
==== Revisions Deadline ====
Dario (Qualcomm) asks to add the same EN added n 2856 because we should discuss if the multiple PCFs scenario is valid or not.
Huazhang (vivo) thanks Dario(Qualcomm), and to prefer to agree r02, and adding the editor's note below in r02:
'Editor's Note: the details if multiple PCF instance selected from one PCF set for the PDU session related to XRM services of the group UEs is FFS'
==== Comments Deadline ====
Revised
9.19 S2-2203533 P-CR Approval 23.700-60: Solution for the KI#2: QoS policy coordination for multiple UEs' QoS flows. Vivo Rel-18 Revision of S2-2202108r02. Approved Approved
9.19 - - - Solutions for KI#3 - - Docs:=6 -
9.19 S2-2202109 P-CR Approval 23.700-60: Solution for KI#3: Exposure of the UE data rate and normal data transmission interruption event. Vivo Rel-18 r02 agreed. Revised to S2-2203534, merging S2-2202332 Mirko (Huawei) comments.
Xiaowan(vivo) replies to Mirko (Huawei)
Zhuoyun (Tencent) provides r01.
Zhuoyun (Tencent) provides the link for r01.
Xiaowan (vivo) provides r02 to fix the comments
Mirko (Huawei) comments and asks for adding a clarification about how the RAN notifies the UPF when there is no UL traffic.
Mirko (Huawei) is fine with r02.
==== Revisions Deadline ====
Zhuoyun (Tencent) is fine with r02.
==== Comments Deadline ====
Revised
9.19 S2-2203534 P-CR Approval 23.700-60: Solution for KI#3: Exposure of the UE data rate and normal data transmission interruption event. Vivo, Tencent, Tencent Cloud Rel-18 Revision of S2-2202109r02, merging S2-2202332. Approved Approved
9.19 S2-2202218 P-CR Approval 23.700-60: New solution for KI#3: 5GS information exposure on XR/media Enhancements. Ericsson, Deutsche Telekom, AT&T, Charter Communications Inc., MediaTek Inc., TMO USA Inc., Telstra, Apple Rel-18 This was postponed. Youngkyo(Samsung) ask a question.
Yali (OPPO) comments.
Paul (Ericsson) replies to Yali (OPPO).
John (Futurewei) asks question.
Devaki (Nokia) provides r01.
Paul (Ericsson) replies to Zhuoyun (Tencent).
Paul (Ericsson) replies to John (Futurewei).
Paul (Ericsson) asks Devaki (Nokia) question for clarification.
Zhuoyun (Tencent) comments.
Yali (OPPO) provides r02.
Hui (Huawei) provides comments.
Paul (Ericsson) replies to Hui (Huawei).
John (Futurewei) clarifies re: IETF arch.
Devaki (Nokia) replies.
Youngkyo(Samsung) comments.
Dan(China Mobile) comments.
Hui (Huawei) replies to Paul (Ericsson).
Paul (Ericsson) replies to Devaki (Nokia) and provides r03.
Paul (Ericsson) replies and asks Hui (Huawei) for clarification.
Devaki (Nokia) comments that it is simply NOT acceptable to us to document simulation results in the TR anywhere (solution, annex or anywhere).
Paul (Ericsson) provides r04.
Yali (OPPO) only accepts r02.
Jinsook (DISH Network) Comment
Hui (Huawei) replies.
Paul (Ericsson) provides r05.
==== Revisions Deadline ====
Paul (Ericsson) provides response to Hui (Huawei). The aspects you refer to are part of IETF work where they address all scenarios/use cases not just what applies to 3GPP, we are applying L4S within 3GPP context as we do with any IETF framework usage in IMS, Security etc. In addition, the nature of the comments is more evaluation, if applicable so we can take the discussion if such input is provided. See detailed comments below.
Ellen (Google) supports this contribution
Hui (Huawei) asks to postpone this paper. The deployment concerns are not only IETF work since the proposed solution in 3GPP fully depends on the maturity of wider domain than 3GPP.
Stephen (BT) supports this contribution
Paul (Ericsson) replies to Hui (Huawei) and asks to discuss this paper during CC#2. We do not see any justification to further delay inclusion of L4S as one solution to this study.
Sriram(CableLabs) supports this contribution
Hui (Huawei) insists on postponing the paper.
==== Comments Deadline ====
Paul (Ericsson) replies to Hui (Huawei) and asks questions for clarification.
Hui(Huawei) replies to Paul (Ericsson).
Saso (Intel) comments that there is no reason for not including a candidate solution in the TR if it: 1) fits within the scope of the study, 2) fits (at least partly) within the remit of SA2 WG, and 3) is sufficiently clearly described. Is there any guidance from the Rapporteur?
Dieter (Deutsche Telekom) fully agrees with Saso. There is no there is no reason for not including this candidate solution in the TR.?
Dan (China Mobile) reply to saso
Hui (Huawei) replies to Saso that the postpone proposal is based on technical reasons that cannot be resolved during this meeting.
Saso (Intel) replies to Hui.
Hui(Huawei) replies to Saso.
Devaki (Nokia) also supports including the solution in the TR as it is a technically viable solution (market adoption etc, one could consider during evaluation phase).
Paul (Ericsson) thanks Saso for taking it up. Indeed, as we also replied earlier, we work in the studies on solns using ENs. We want to be constructive and are adding (see below) ENs to the solution. R07 is uploaded to CC#3 folder.
Hui (Huawei) suggests Paul to check Ericsson's comments on S2-2202130, while Ericsson requested to postpone the paper, instead of adding ENs.
Postponed
9.19 S2-2202332 P-CR Approval 23.700-60: KI #3, New Sol: Network Information Exposure to Support XR/Media enhancements. Tencent, Tencent Cloud Rel-18 Merged into S2-2203534 Mirko (Huawei) comments and suggests to merge this document into S2-2202109.
Zhuoyun (Tencent) is fine with merging this contribution into S2-2202109.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.19 S2-2202717 P-CR Approval 23.700-60: New Solution for KI#3: Non-GBR QoS Notification Control Report. CATT Rel-18 r05 agreed. Revised to S2-2203535 Dan(China Mobile) comment and provie r01
Mirko (Huawei) comments.
Chunshan (CATT) provides r02.
Mirko (Huawei) provides r03.
Chunshan (CATT) provides r04.
Chunshan (CATT) provides clarification
Mirko (Huawei) responds and provide r05.
Chunshan (CATT) responds and provide r06.
Mirko (Huawei) comments and prefers r05.
Mirko (Huawei) responds.
Chunshan (CATT) provides further clarification.
Chunshan (CATT) provides the clarification.
==== Revisions Deadline ====
Chunshan (CATT) responds and asks to go with the r06.
Mirko (Huawei) can only accept r03 or r05 and objects to all other versions.
Chunshan (CATT) prefers the r06 and r05 is also OK.
==== Comments Deadline ====
Revised
9.19 S2-2203535 P-CR Approval 23.700-60: New Solution for KI#3: Non-GBR QoS Notification Control Report. CATT Rel-18 Revision of S2-2202717r05. Approved Approved
9.19 - - - Solutions for KI#4&5 - - Docs:=35 -
9.19 S2-2202080 P-CR Approval 23.700-60: New solution for KI#4,5: Identification and importance of packets in PDU sets. Futurewei Rel-18 r05 agreed. Revised to S2-2203536 Xiaowan (vivo) seek clarification
John (Futurewei) replies, provides r01.
Guillaume (MediaTek Inc.) comments.
Saso (Intel) comments.
John (Futurewei) responds to Guillaume (Mediatek) and Saso (Intel), provides r02.
Dario (Qualcomm) provides r03
Xinpeng(Huawei) ask questions for clarification.
John (Futurewei) responds to Xinpeng (Huawei).
Xinpeng(Huawei) replies to John (Futurewei).
Guillaume (MediaTek Inc.): happy with r02
John (Futurewei) responds to Xinpeng, Dario, provides r04.
Xinpeng(Huawei) provides r05.
John (Futurewei) is OK with r05.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203536 P-CR Approval 23.700-60: New solution for KI#4,5: Identification and importance of packets in PDU sets. Futurewei Rel-18 Revision of S2-2202080r05. Approved Approved
9.19 S2-2202219 P-CR Approval 23.700-60: Solution for KI#4: Introduction of PDU Set information and QoS parameters. Ericsson Rel-18 r04 agreed. Revised to S2-2203537 John (Futurewei) has questions.
Paul (Ericsson) replies to John (Futurewei) and provides r01.
Yali (OPPO) asks a question.
Saso (Intel) seeks clarification.
Xiaowan (vivo) seek calrifications
Paul (Ericsson) replies to Yali (OPPO) on PSDB/PSER issue and to Saso (Intel).
Yali (OPPO) comments PSDB/PSER issue is not special for this solution, S2-2202872/S2-2202408/S2-2202968 also affected.
Saso (Intel) follows up on Paul's reply.
Saso (Intel) follows up on Paul's reply; makes text proposals.
Dario (Qualcomm) provides r02 and asks question.
Paul (Ericsson) replies and provides r03.
Saso (Intel) provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203537 P-CR Approval 23.700-60: Solution for KI#4: Introduction of PDU Set information and QoS parameters. Ericsson Rel-18 Revision of S2-2202219r04. Approved Approved
9.19 S2-2202872 P-CR Approval 23.700-60: Solution for KI#4 (PDU Set integrated packet handling) by sending PDU Set sequence number in a GTP-U extension header. Vodafone Rel-18 r01 agreed. Revised to S2-2203538 John (Futurewei) asks question for clarification.
Mike (InterDigital) comments
Chris (Vodafone) replies to the Futurewei and Interdigital questions
Mike (InterDigital) replies
Sudeep (Apple) has questions for clarification.
Chris (Vodafone) replies to Apple and Interdigital.
Chris (Vodafone) provides rev 01 to address Interdigital's comment.
Mike (InterDigital) is ok with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203538 P-CR Approval 23.700-60: Solution for KI#4 (PDU Set integrated packet handling) by sending PDU Set sequence number in a GTP-U extension header . Vodafone Rel-18 Revision of S2-2202872r01. Approved Approved
9.19 S2-2202110 P-CR Approval 23.700-60: Solution for KI#4&5 different bearers for PDUs with different importance levels. Vivo Rel-18 r01 agreed. Revised to S2-2203539 Xiaowan(vivo) replies to Hui (Huawei)
Hui (Huawei) asks for clarification.
Jinguo(ZTE) comments that this solution is not based on existing QoS mechanism.
Xiaowan(vivo) replies to Jinguo(ZTE) there is likely a misunderstanding
Youngkyo(Samsung) shares the view from Jinguo(ZTE).
Xiaowan (vivo) replies to comments and provides r01
==== Revisions Deadline ====
Jinguo(ZTE) suggests to approve r01
Devaki (Nokia) proposes to go with r01. (Chair's note asks for r00 to be approved).
==== Comments Deadline ====
Revised
9.19 S2-2203539 P-CR Approval 23.700-60: Solution for KI#4&5 different bearers for PDUs with different importance levels. Vivo Rel-18 Revision of S2-2202110r01. Approved Approved
9.19 S2-2202111 P-CR Approval 23.700-60: Solution for KI#4&5 handling PDU Set within QoS flow. Vivo Rel-18 Approved Youngkyo(Samsung) asks a question
Mike (InterDigital) asks a question
Yali (OPPO) asks a question
Xiaowan(vivo) replies to Mike (InterDigital) and Youngkyo(Samsung)
Dario (Qualcomm) asks question for clarification
Xiaowan (vivo) replies to the questions from Dario(Qualcomm) and Yali (OPPO)
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.19 S2-2202408 P-CR Approval 23.700-60: KI#4: Solution for PDU Set integrated QoS handling. Huawei, HiSilicon, KDDI Rel-18 r04 agreed. Revised to S2-2203540 Dario (Qualcomm) provides r01
Hui(Huawei) provides r02
Saso (Intel) provides r03
Hui (Huawei) replies to Saso.
Saso (Intel) is OK with r04.
Hui (Huawei) provides r04
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203540 P-CR Approval 23.700-60: KI#4: Solution for PDU Set integrated QoS handling. Huawei, HiSilicon, KDDI Rel-18 Revision of S2-2202408r04. Approved Approved
9.19 S2-2202112 P-CR Approval 23.700-60: Solution for KI#5 DL data handling. Vivo Rel-18 r02 agreed. Revised to S2-2203541 Guillaume (MediaTek Inc.) comments.
Dario (Qualcomm) comments.
Xiaowan (vivo) replies to Dario (Qualcomm) and Guillaume (MediaTek Inc.) and provides r02
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203541 P-CR Approval 23.700-60: Solution for KI#5 DL data handling. Vivo Rel-18 Revision of S2-2202112r02. Approved Approved
9.19 S2-2202113 P-CR Approval 23.700-60: Solution for KI#5 UL data handling. Vivo Rel-18 Noted Guillaume (MediaTek Inc.) comments: this is a RAN2 proposal
Saso (Intel) agrees with Guillaume: this is a RAN2 proposal. The tdoc should be NOTED.
Dario (Qualcomm) comments.
Xiaowan(vivo) replies to Saso (Intel) Guillaume(MediaTek Inc.) SA2 is E2E arch certainly can discuss RAN based solution. And you two proposes RAN solution(e.g. solution#22 in 23761) in SA2 before. Let's have a consistent principle and focus on the technical discussion.
Guillaume (MediaTek Inc.) responds to Xiaowan (vivo), and insists the proposal is RAN2-only so should be noted.
Saso (Intel) proposes again to NOTE the document as the solution is mostly in RAN2 scope, or to re-write it by focusing only on the NAS-AS interactions.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.19 S2-2202304 P-CR Approval 23.700-60: KI#4: Solution proposal PDU Set integrated packet handling. Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2203542 John (Futurewei) asks question for clarification.
Devaki (Nokia) replies.
Sudeep (Apple) comments.
Zhuoyun (Tencent) comments.
Dario (Qualcomm) asks question for clarification.
Chia-Lin (MediaTek) ask for clarification on the solution
Devaki (Nokia) provides r01 and replies.
Saso (Intel) provides r02.
Chris (Vodafone) provides r03.
==== Revisions Deadline ====
Chia-Lin (MediaTek) are ok with r02 and r03
Zhuoyun (Tencent) is ok with r02 and r03
==== Comments Deadline ====
Revised
9.19 S2-2203542 P-CR Approval 23.700-60: KI#4: Solution proposal PDU Set integrated packet handling. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202304r03. Approved Approved
9.19 S2-2202270 P-CR Approval 23.700-60: New solution: Leverage RTP layer info for PDU Set handling. OPPO Rel-18 r01 agreed. Revised to S2-2203543 Mike (InterDigital) comments
Yali (OPPO) provides r01.
Mike (InterDigital) is ok with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203543 P-CR Approval 23.700-60: New solution: Leverage RTP layer info for PDU Set handling . OPPO Rel-18 Revision of S2-2202270r01. Approved Approved
9.19 S2-2202503 P-CR Approval 23.700-60: KI#4, KI#5: New Solution: PDU Set identification. Apple Rel-18 r02 agreed. Revised to S2-2203544 Dario (Qualcomm) provides r01
Saso (Intel) comments and questions.
Sudeep (Apple) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203544 P-CR Approval 23.700-60: KI#4, KI#5: New Solution: PDU Set identification . Apple Rel-18 Revision of S2-2202503r02. Approved Approved
9.19 S2-2202715 P-CR Approval 23.700-60: New Solution for KI#4/5: Sub-QoS Flow based QoS Architecture and Policy Control. CATT Rel-18 Approved Chunshan (CATT) responds.
Hui(Huawei) asks question.
Dario (Qualcomm) asks clarification
==== Revisions Deadline ====
Dario (Qualcomm) comments.
Devaki (Nokia) comments.
Chunshan (CATT) comments.
==== Comments Deadline ====
Approved
9.19 S2-2202716 P-CR Approval 23.700-60: New Solution for KI#4/5: PDU Set Identification and Marking. CATT Rel-18 Approved Dario (Qualcomm) proposes r01
Chunshan (CATT) responds to Dario that you provide other paper's r01 to my paper.
==== Revisions Deadline ====
Chunshan (CATT) proposes to go with r00, since the r01 is for another paper.
Dario (Qualcomm) acknlowedges the issue w/ r1 and is OK to go with the original version.
Chunshan (CATT) comments.
==== Comments Deadline ====
Approved
9.19 S2-2202752 P-CR Approval 23.700-60: Solution on Application-aware QoS (Key issue #4 and #5). Samsung Rel-18 Approved Approved
9.19 S2-2202969 P-CR Approval 23.700-60: KI#4 and KI#5: Solution for UPF based PDU Set identification. Qualcomm Incorporated Rel-18 r07 agreed. Revised to S2-2203545 John (Futurewei) requests clarification.
Mike (InterDigital) comments and questions
Chris Joul (T-Mobile USA) comments
Dario (Qualcomm) replies to InterDigital, Futurewei and T-Mobile USA
Dario (Qualcomm) provides a missing answer for Futurewei.
Mike (InterDigital) replies
Chris Joul (T-Mobile USA) provides comments to Dario
Zhuoyun (Tencent) comments.
John (Futurewei) comments.
Youngkyo(Samsung) ask a question.
Saso (Intel) comments and questions
Hui (Huawei) comments.
Dario (Qualcomm) replies and provides r01
Dario (Qualcomm) provides r02
Saso (Intel) provides r03
Chris (Vodafone) supports Intel on the need for some solutions to consider PDU encryption
Yali (OPPO) provides r04
Guillaume (MediaTek Inc.) comments and provides r05.
Guillaume (MediaTek Inc.) provides r07 (on top of r06, to address empty r05)
Dario (Qualcomm) replies and provides r06.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203545 P-CR Approval 23.700-60: KI#4 and KI#5: Solution for UPF based PDU Set identification. Qualcomm Incorporated Rel-18 Revision of S2-2202969r07. Approved Approved
9.19 S2-2202672 P-CR Approval 23.700-60: FS_XRM new solution to KI#4: PDU Set ID in the GTP-U header. ZTE Rel-18 Approved Dario (Qualcomm) asks clarification
Jinguo(ZTE) replies to Dario (Qualcomm)
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.19 S2-2202937 P-CR Approval 23.700-60: KI#4, KI#5, New Sol: N6 tunnelling-based solution. Intel Rel-18 r04 agreed. Revised to S2-2203546 Youngkyo(Samsung) comments.
John (Futurewei) asks question.
Mike (InterDigital) asks a question
Saso (Intel) provides r01.
Mike (InterDigital) is ok with r01
Dario (Qualcomm) asks question for clarification.
Sudeep (Apple) has questions for clarification.
Saso (Intel) provides r02.
Hui(Huawei) asks question.
Youngkyo(Samsung) replies.
Saso (Intel) provides r03.
Dario (Qualcomm) replies to Saso
Saso (Intel) provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203546 P-CR Approval 23.700-60: KI#4, KI#5, New Sol: N6 tunnelling-based solution. Intel Rel-18 Revision of S2-2202937r04. Approved Approved
9.19 S2-2202331 P-CR Approval 23.700-60: KI #4, New Sol: PDU set related packet handling enhancements. Tencent, Tencent Cloud Rel-18 Approved Approved
9.19 S2-2202409 P-CR Approval 23.700-60: KI#5: Solution for differentiated QoS handling for different PDU Sets. Huawei, HiSilicon, KDDI Rel-18 Approved Approved
9.19 S2-2202968 P-CR Approval 23.700-60: KI#4 and KI#5: Solution for PDU Set control QoS framework. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203547 Youngkyo(Samsung) ask a question
Mike (InterDigital) ask questions
Dario (Qualcomm) replies to Youngkyo and Mike.
Youngkyo(Samsung) provides comments further.
Saso (Intel) comments.
Dario (Qualcomm) replies to Sašo and Youngkyo and provides r01.
Saso (Intel) provides r02.
==== Revisions Deadline ====
Saso (Intel) replies to Dario.
==== Comments Deadline ====
Revised
9.19 S2-2203547 P-CR Approval 23.700-60: KI#4 and KI#5: Solution for PDU Set control QoS framework. Qualcomm Incorporated Rel-18 Revision of S2-2202968r02. Approved Approved
9.19 S2-2202656 P-CR Approval 23.700-60: Differentiated QoS handling for XR and media service. Lenovo Rel-18 r02 agreed. Revised to S2-2203548 Dario (Qualcomm) provides r01
Youngkyo(Samsung) provide comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203548 P-CR Approval 23.700-60: Differentiated QoS handling for XR and media service. Lenovo Rel-18 Revision of S2-2202656r02. Approved Approved
9.19 S2-2202682 DISCUSSION Agreement PDU set integrated packet handling for XR and media service. Lenovo Rel-18 Noted Noted
9.19 - - - Solutions for KI#6 - - Docs:=7 -
9.19 S2-2202031 P-CR Approval 23.700-60: KI#6, New Sol: QoS enhancements to Meet RTT Requirement for XR and Media Services. Tencent, Tencent Cloud Rel-18 Covered by S2-2202114. Noted Xiaowan (vivo) proposes to merge this paper into S2-2202114
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.19 S2-2202114 P-CR Approval 23.700-60: Solution for KI#6 RT latency split for two QoS flows used for UL and DL respectively. Vivo Rel-18 Approved with the understanding that updates can be made at a later time. Xiaowan(vivo) suggests to agree r01
Hui(Huawei) repost r01 link, and support Xiaowan r01 is the agreeable one.
==== Comments Deadline ====
Approved
9.19 S2-2202115 P-CR Approval 23.700-60: Solution for KI#6 RT latency handling for single QoS flow. Vivo Rel-18 r03 agreed. Revised to S2-2203549, merging S2-2202271 Xiaowan (vivo) replies to hui(Huawei)
Hui(Huawei) asks an EN.
Boren (OPPO) provides r02.
Hui(Huawei) provides further comment.
Chunshan(CATT) questions for clarification.
Mike (InterDigital) comments
Xiaowan (vivo) replies comments and provides r03
Boren (OPPO) is fine with r03.
Devaki (Nokia) comments.
Xiaowan (vivo) replies to Devaki (Nokia)
Hui (Huawei) asks another question.
Xiaowan(vivo) replies to Hui (Huawei)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203549 P-CR Approval 23.700-60: Solution for KI#6 RT latency handling for single QoS flow . Vivo, OPPO Rel-18 Revision of S2-2202115r03, merging S2-2202271. Approved Approved
9.19 S2-2202271 P-CR Approval 23.700-60: Solution for KI#6 on uplink-downlink transmission coordination to meet Round-Trip latency requirements. OPPO Rel-18 Merged into S2-2203549 Boren (OPPO) replies to Hui(Huawei).
Hui(Huawei) asks an EN and whether this can be merged with S2-2202115.
Boren (OPPO) confirms that this paper has been merged into S2-2202115.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.19 S2-2202410 P-CR Approval 23.700-60: Solution for KI#6: Support for Round-Trip latency requirement. Huawei, HiSilicon Rel-18 Covered by S2-2202114. Noted Hui(Huawei) agrees to merge
Xiaowan (vivo) proposes to merge this paper into S2-2202114
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.19 S2-2202306 P-CR Approval 23.700-60: KI#6 Solution proposal: Two Way Delay Budget. Nokia, Nokia Shanghai Bell Rel-18 Approved Devaki (Nokia) replies.
Xiaowan (vivo) questions
Hui(Huawei) asks questions.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.19 - - - Solutions for KI#7 - - Docs:=6 -
9.19 S2-2202065 P-CR Approval 23.700-60: KI#6, New Sol: Policy enhancements to minimize jitter for XR and Media Services. Tencent, Tencent Cloud Rel-18 r04 agreed. Revised to S2-2203550 Mike (InterDigital) asks a question
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203550 P-CR Approval 23.700-60: KI#6, New Sol: Policy enhancements to minimize jitter for XR and Media Services. Tencent, Tencent Cloud Rel-18 Revision of S2-2202065r04. Approved Approved
9.19 S2-2202852 P-CR Approval 23.700-60: Solution about policy enhancements to minimize the jitter. China Mobile Rel-18 r01 + changes agreed. Revised to S2-2203606. Devaki (Nokia) provides r01.
Youngkyo(Samsung) ask a question.
Dan(China Mobile) reply, and if you think the below need to be provided in the paper, I can update it.
Dario (Qualcomm) comments that this solution is not in scope of the KI.
Dan (China Mobile) reply and provide r01
==== Revisions Deadline ====
Dan (China Mobile) reply and provide r02
Devaki (Nokia) comments that r02 does not address all the comments provided regarding the procedure in r01 but in the interest of progress, ok to move forward with r02 for now under the assumption that these will be addressed during next meeting.
Dan (China Mobile) thanks devaki, and I will address these comments in next meeting.
Dario (Qualcomm) objects to this proposal because it goes beyond the scope of the KI.
Dan (China Mobile) provide r03 with removing some sentence in r02
Dan (China Mobile) request to discuss this paper in CC#3
Devaki (Nokia) comments.
Dan (China Mobile) reply with correct the previous email
==== Comments Deadline ====
Revised
9.19 S2-2203606 P-CR Approval 23.700-60: Solution about policy enhancements to minimize the jitter . China Mobile Rel-18 Revision of S2-2202852r01 + changes. Approved Approved
9.19 S2-2202718 P-CR Approval 23.700-60: New Solution for KI#7: Periodicity and Periodicity Jitter Control. CATT Rel-18 r02 + changes agreed. Revised to S2-2203607. Mike (InterDigital) asks a question
Chunshan (CATT) provides clarification to Mike (InterDigital).
Chunshan (CATT) provides clarification.
Dario (Qualcomm) comments that this solution is out of scope of the KI.
Shabnam (Ericsson) if CATT can then revise the paper to only include the relevant parts as commented and move rest of the information into Annex or background info? Why does RAN need to enforce and why not the AF adjustment of, e.g. CODEC etc. sufficient handling?
Chunshan (CATT) provides r01.
Chunshan (CATT) provides r02.
==== Revisions Deadline ====
Dario (Qualcomm) objects to any revision of this paper.
Chunshan (CATT) thinks the objection are unreasonable and proposes to discuss in CC#3
==== Comments Deadline ====
Revised
9.19 S2-2203607 P-CR Approval 23.700-60: New Solution for KI#7: Periodicity and Periodicity Jitter Control. CATT Rel-18 Revision of S2-2202718r02 + changes. Approved Approved
9.19 - - - Solutions for KI#8 - - Docs:=6 -
9.19 S2-2202307 LS OUT Approval [DRAFT] LS on UE Power Saving for XR and Media Services Nokia, Nokia Shanghai Bell Rel-18 Revised to S2-2203418. Devaki (Nokia) comments that this LS out should have been marked approved in Chair's notes as per e-meeting rules (as it received zero comments prior to revision deadline). Chair's notes posted after revision deadline includes no comments or decision for this LS out.
Hui(Huawei) provides comments
==== Comments Deadline ====
Revised
9.19 S2-2203418 LS OUT Approval LS on UE Power Saving for XR and Media Services SA WG2 Rel-18 Revision of S2-2202307. Approved Approved
9.19 S2-2202220 P-CR Approval 23.700-60: Solution for KI#8 Enhancements to power savings for XR. Ericsson Rel-18 This was postponed. Dario (Qualcomm) comments and asks clarification.
Paul (Ericsson) replies to Dario (Qualcomm) and Saso (Intel).
Saso (Intel) seeks clarification.
Saso (Intel) proposes r01.
Paul (Ericsson) replies to Saso (Intel) and asks for clarification.
Dario (Qualcomm) replies to Paul and provides r02
Saso (Intel) replies to Paul.
Paul (Ericsson) replies to Saso (Intel) and Dario (Qualcomm) and provides r03.
Saso (Intel) provides r04.
Saso (Intel) replies to Paul and asks for clarification.
==== Revisions Deadline ====
Paul (Ericsson) comments and asks Saso (Intel) question for clarification.
Dario (Qualcomm) can only accept r02 and objects other versions
Paul (Ericsson) replies to Dario (Qualcomm), and asks question for clarification. R02 is not acceptable.
Paul (Ericsson) proposes to discuss this document at CC#3.
==== Comments Deadline ====
Postponed
9.19 S2-2202411 P-CR Approval 23.700-60: Solution for KI#8: support of CDRX enhancement for power saving handling. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203551 Mike (InterDigital) asks a question
Paul (Ericsson) asks question for clarification.
Saso (Intel) seeks clarification.
Hui (Huawei) provides r01 and replies.
Saso (Intel) proposes an EN.
Dario (Qualcomm) asks questions for clarification
Hui (Huawei) replies to Dario.
Hui (Huawei) replies to Saso.
Saso (Intel) provides r02.
Hui (Huawei) fine with r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203551 P-CR Approval 23.700-60: Solution for KI#8: support of CDRX enhancement for power saving handling . Huawei, HiSilicon Rel-18 Revision of S2-2202411r02. Approved Approved
9.19 S2-2202723 P-CR Approval 23.700-60: Key Issue #8 and Key Issue #9: New solution: 5GC and UE Assistance to RAN for CDRX Optimization. InterDigital Inc. Rel-18 Approved Dario (Qualcomm) asks questions for clarification
Mike (InterDigital) replies
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.19 - - - Solutions for KI#9 - - Docs:=2 -
9.19 S2-2202272 P-CR Approval 23.700-60: New solution: Provision of conditional QoS profile(s). OPPO Rel-18 r03 agreed. Revised to S2-2203552 Mike (InterDigital) comments
Yali (OPPO) provides r01
Yali (OPPO) replies to LaeYoung (LGE) and provides r02.
LaeYoung (LGE) comments.
Dario (Qualcomm) asks questions for clarification
Yali (OPPO) provides r03 and replies to Mike (InterDigital) &Dario (Qualcomm).
Mike (InterDigital) is ok with r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.19 S2-2203552 P-CR Approval 23.700-60: New solution: Provision of conditional QoS profile(s). OPPO Rel-18 Revision of S2-2202272r03. Approved Approved
9.19 - - - Others - - Docs:=1 -
9.19 S2-2202654 DISCUSSION Agreement PDU set integrated packet handling for XR and media service Lenovo Information Technology Rel-18 WITHDRAWN Hui(Huawei) asks whether this paper has been withdrawn.
==== Revisions Deadline ====
==== Comments Deadline ====
Withdrawn
9.20 - - - Study on Ranging based services and sidelink positioning (FS_Ranging_SL) - - Docs:=34 -
9.20 - - - New KI - - Docs:=2 -
9.20 S2-2202907 P-CR Approval 23.700-86: Proposed new KI on Service Authorization to NG-RAN. Xiaomi Rel-18 r01 agreed. Revised to S2-2203337 Saad (Interdigital) comments
Sherry (Xiaomi) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203337 P-CR Approval 23.700-86: Proposed new KI on Service Authorization to NG-RAN. Xiaomi Rel-18 Revision of S2-2202907r01. Approved Approved
9.20 - - - Solution of KI#1 - - Docs:=4 -
9.20 S2-2202345 P-CR Approval 23.700-86: Solution for KI#1 on authorization and policy and parameter provisioning for ranging services. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2203338 Sherry (Xiaomi) comments.
Cai Simon (Nokia) asks questions
Fei (OPPO) asks questions.
LiMeng (Huawei) responds.
LiMeng (Huawei) provides r01.
Cai Simon (Nokia) re-iterates the question not clarified
Hong (Qualcomm) comments.
LiMeng (Huawei) replies and provides r02.
LiMeng (Huawei) further clarifies.
LiMeng (Huawei) replies.
Sherry (Xiaomi) replies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203338 P-CR Approval 23.700-86: Solution for KI#1 on authorization and policy and parameter provisioning for Ranging/SL positioning services. Huawei, HiSilicon Rel-18 Revision of S2-2202345r04. Approved Approved
9.20 S2-2202908 P-CR Approval 23.700-86: Proposed new solution on authorization and policy/parameter provisioning to UE. Xiaomi Rel-18 r03 agreed. Revised to S2-2203339 LaeYoung (LGE) asks a Q.
Sherry (Xiaomi) provides r01.
Walter Dees (Philips) provides comments
Hong (Qualcomm) comments.
LiMeng (Huawei) provides r02.
LaeYoung (LGE) provides comment.
Sherry (Xiaomi) provides r03.
Walter Dees (Philips) is ok with r03
==== Revisions Deadline ====
LiMeng (Huawei) is OK with r03.
==== Comments Deadline ====
Revised
9.20 S2-2203339 P-CR Approval 23.700-86: Proposed new solution on authorization and policy/parameter provisioning to UE. Xiaomi Rel-18 Revision of S2-2202908r03. Approved Approved
9.20 - - - Solution of KI#3&4 - - Docs:=6 -
9.20 S2-2202344 P-CR Approval 23.700-86: Solution for KI#4 on direct ranging operation. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2203340 Sherry (Xiaomi) comments.
LiMeng (Huawei) responds.
Deng Qiang (CATT) comments.
Sherry (Xiaomi) asks a question and provides r01.
Saad (Interdigital) asks a question
Hong (Qualcomm) comments.
LiMeng (Huawei) responds and provides r02.
Deng Qiang (CATT) comments on r02.
Sherry (Xiaomi) provides r03.
==== Revisions Deadline ====
Hong (Qualcomm) prefers r03.
LiMeng (Huawei) replies to Deng Qiang (CATT) and prefers to r02.
Sherry (Xiaomi) provides r04, both r02&r03&r04 are acceptable to us.
==== Comments Deadline ====
Revised
9.20 S2-2203340 P-CR Approval 23.700-86: Solution for KI#4 on direct ranging operation. Huawei, HiSilicon Rel-18 Revision of S2-2202344r03. Approved Approved
9.20 S2-2202489 P-CR Approval 23.700-86: TR 23.700-86: New solution for Ranging devices discovery and ranging procedure. Vivo Rel-18 r06 agreed. Revised to S2-2203341 Sherry (Xiaomi) comments.
LiMeng (Huawei) asks questions.
Saad (Interdigital) asks question
Wen (vivo) responds to Saad, LiMeng and Sherry.
Sherry (Xiaomi) provides r04.
LiMeng (Huawei) provides r03.
Wen (vivo) replies to Fei.
Fei (OPPO) comments.
Hong (Qualcomm) provides r05.
Wen (vivo) replies.
Sherry (Xiaomi) provides r06.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203341 P-CR Approval 23.700-86: TR 23.700-86: New solution for Ranging devices discovery and ranging procedure . Vivo Rel-18 Revision of S2-2202489r06. Approved Approved
9.20 S2-2202627 P-CR Approval 23.700-86: KI#3, KI#4, New Sol: Solution to support ranging/sidelink positioning. CATT Rel-18 r04 agreed. Revised to S2-2203342 Sherry (Xiaomi) comments.
LiMeng (Huawei) asks questions regarding the reference UE.
Cai Simon (Nokia) asks questions
Wen (vivo) comments
Fei (OPPO) asks questions
Walter Dees (Philips) comments
Yunjing (CATT) replies and provides r01.
LiMeng (Huawei) provides r02 and asks questions.
Yunjing (CATT) replies to LiMeng (Huawei).
Walter (Philips) replies to Yunjing (CATT).
Yunjing (CATT) replies to Walter (Philips) and provides r03.
Sherry (Xiaomi) provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203342 P-CR Approval 23.700-86: KI#3, KI#4, New Sol: Solution to support ranging/sidelink positioning. CATT Rel-18 Revision of S2-2202627r04. Approved Approved
9.20 - - - Solution of KI#5 - - Docs:=6 -
9.20 S2-2202490 P-CR Approval 23.700-86: TR 23.700-86: Network assisted Ranging and Sidelink Positioning. Vivo Rel-18 r04 agreed. Revised to S2-2203343 Sherry (Xiaomi) comments.
Lars (Sony) comments.
LiMeng (Huawei) comments.
Saad (Interdigital) comments.
Wen (vivo) responds to Saad, LiMeng, Lars and Sherry.
Lars (Sony) provides r02.
Wen (vivo) replies.
Hong (Qualcomm) comments.
Wen (vivo) responds and provides r03.
Sherry (Xiaomi) replies.
Sherry (Xiaomi) provides r04.
==== Revisions Deadline ====
Sherry (Xiaomi) is fine to agree r04 expecting more updates in the next meeting.
Wen (vivo) is ok with r03 and acknowledges there will be further discussion of the questions in r04 at the next meeting.
==== Comments Deadline ====
Revised
9.20 S2-2203343 P-CR Approval 23.700-86: TR 23.700-86: Network assisted Ranging and Sidelink Positioning . Vivo Rel-18 Revision of S2-2202490r04. Approved Approved
9.20 S2-2202509 P-CR Approval 23.700-86: KI#5: Solution for Network assisted SL positioning. Sony Rel-18 r03 agreed. Revised to S2-2203344 Sherry (Xiaomi) comments.
Lars (Sony) is fine with r03.
Sherry (Xiaomi) provides r03.
Lars (Sony) is ok with r02
LiMeng (Huawei) provides r02
Lars (Sony) responds to Sherry and provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203344 P-CR Approval 23.700-86: KI#5: Solution for Network assisted SL positioning. Sony Rel-18 Revision of S2-2202509r03. Approved Approved
9.20 S2-2202731 P-CR Approval 23.700-86: Solution for KI#5: Network assisted Sidelink Positioning for In Network Coverage and Partial Network Coverage. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203345 Lars (Sony) comments.
Sherry (Xiaomi) comments.
Runze (Huawei) replies to Sherry.
Walter Dees (Philips) comments
Sherry (Xiaomi) replies to Runze.
Leo (Deutsche Telekom) comments that r01 was provided by Runze (Huawei).
Hong (Qualcomm) comments.
Lars (Sony) comments on r01.
Walter Dees (Philips) requests Editors Note to be added
Runze (Huawei) replies to Walter Dees (Philips), Lars (Sony), Hong (Qualcomm) and Sherry (Xiaomi), and propose r02.
==== Revisions Deadline ====
Sherry (Xiaomi) can live with r02 for this meeting, however, many issues are expected to be further clarified for this solution.
==== Comments Deadline ====
Revised
9.20 S2-2203345 P-CR Approval 23.700-86: Solution for KI#5: Network assisted Sidelink Positioning for In Network Coverage and Partial Network Coverage. Huawei, HiSilicon Rel-18 Revision of S2-2202731r02. Approved Approved
9.20 - - - Solution of KI#6 - - Docs:=6 -
9.20 S2-2202346 P-CR Approval 23.700-86: Solution for KI#6 on ranging and sidelink positioning service exposure to UE. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2203346 Lars (Sony) comments.
Sherry (Xiaomi) comments.
Lars (Sony) comments on r01.
Sherry (Xiaomi) withdraws this thread and continue the discussion under the thread initiated by Lars.
LiMeng (Huawei) provides r01.
Lars (Sony) provides r02.
Sherry (Xiaomi) provides r03 on top of r02.
Hong (Qualcomm) comments.
LiMeng (Huawei) provides r04.
Sherry (Xiaomi) provides r05.
==== Revisions Deadline ====
Hong (Qualcomm) is fine with r04.
Sherry (Xiaomi) is fine with r04 & r05, and prefers to agree r05, which reduced some editorial problems.
==== Comments Deadline ====
Revised
9.20 S2-2203346 P-CR Approval 23.700-86: Solution for KI#6 on ranging and sidelink positioning service exposure to UE. Huawei, HiSilicon Rel-18 Revision of S2-2202346r05. Approved Approved
9.20 S2-2202491 P-CR Approval 23.700-86: TR 23.700-86: New solution for Ranging service exposure to UE. Vivo Rel-18 r01 agreed. Revised to S2-2203347 Sherry (Xiaomi) comments.
Wen (vivo) responds.
Wen (vivo) replies to Sherry.
Sherry (vivo) replies to Wen.
Wen (vivo) responds to Sherry.
Sherry (Xiaomi) asks questions.
Wen (vivo) provides r01 based on previous comments and comments from other thread.
==== Revisions Deadline ====
Sherry (Xiaomi) has concern on r01 and r00, and proposes to postpone or note the paper.
Wen (vivo) has concerns on the comments from Xiaomi.
Sherry (Xiaomi) propose to work on it further in the next meeting.
==== Comments Deadline ====
Revised
9.20 S2-2203347 P-CR Approval 23.700-86: TR 23.700-86: New solution for Ranging service exposure to UE . Vivo Rel-18 Revision of S2-2202491r01. Approved Approved
9.20 S2-2202508 P-CR Approval 23.700-86: KI#6: Solution for UE using exposure API. Sony Rel-18 r01 agreed. Revised to S2-2203348 LiMeng (Huawei) asks whether this solution is specific to Ranging only.
Lars (Sony) responds to LiMeng
Sherry (Xiaomi) comments.
Sherry (Xiaomi) replies to Lars.
Lars (Sony) provides r01.
Sherry (Xiaomi) withdraws this thread and continue the discussion under the thread initiated by Li Meng.
Lars (Sony) responds to Sherry.
LiMeng (Huawei) asks for clarification.
Lars (Sony) responds to LiMeng question
LiMeng (Huawei) thanks Lars for the answer.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.20 S2-2203348 P-CR Approval 23.700-86: KI#6: Solution for UE using exposure API. Sony Rel-18 Revision of S2-2202508r01. Approved Approved
9.20 - - - Solution of KI#7 - - Docs:=4 -
9.20 S2-2202368 P-CR Approval 23.700-86: KI#7: New Solution on Ranging Service Exposure towards AF. Samsung Rel-18 r02 agreed. Revised to S2-2203349 LiMeng (Huawei) comments.
Sherry (Xiaomi) comments.
Saad (Interdigital) comments
David (Samsung) replies to Huawei, Interdigital, Xiaomi and provides r01.
Sherry (Xiaomi) withdraws this thread and continue the discussion under the thread initiated by Li Meng.
Sherry (Xiaomi) proposes to withdraw this thread and continue the discussion under the thread initiated by Li Meng.
Sherry (Xiaomi) combines the comments to this TDoc from the other 2 threads.
Sherry (Xiaomi) comments to r01.
David (Samsung) provides r02.
==== Revisions Deadline ====
Sherry (Xiaomi) is fine with r02.
==== Comments Deadline ====
Revised
9.20 S2-2203349 P-CR Approval 23.700-86: KI#7: New Solution on Ranging Service Exposure towards AF. Samsung Rel-18 Revision of S2-2202368r02. Approved Approved
9.20 S2-2202909 P-CR Approval 23.700-86: Proposed new solution on service initiated by Application server or 5GC NF. Xiaomi Rel-18 r04 agreed. Revised to S2-2203350 David (Samsung) provides comments.
Sherry (Xiaomi) provides r01.
Hong (Qualcomm) comments.
LiMeng (Huawei) provides r02.
Sherry (Xiaomi) provides r03.
David (Samsung) suggests an EN on top of r03, as done in S2-2202368.
David (Samsung) accepts r04.
Sherry (Xiaomi) provides r04.
==== Revisions Deadline ====
LiMeng (Huawei) is OK with r04.
==== Comments Deadline ====
Revised
9.20 S2-2203350 P-CR Approval 23.700-86: Proposed new solution on service initiated by Application server or 5GC NF. Xiaomi Rel-18 Revision of S2-2202909r04. Approved Approved
9.20 - - - Others - - Docs:=2 -
9.20 S2-2202769 P-CR Approval 23.700-86: TR 23.700-86: New Solution on reference architecture for Sidelink Positioning and Ranging services. Qualcomm Incorporated Rel-18 r06 + rename the SLPP to SPRF, in both the text and the figure revised to S2-2203351 LiMeng (Huawei) asks for clarifications for SR5.
Sherry (Xiaomi) asks if we can define a reference architecture as assumption rather than an architecture solution?
Deng Qiang (CATT) comments.
Walter Dees (Philips) comments.
Hong (Qualcomm) replies, and provides r01 (documented as a solution) and r02 (documented as arch assumptions).
Sherry (Xiaomi) provides r03.
Hong (Qualcomm) replies to Sherry.
Sherry (Xiaomi) replies to Hong.
Deng Qiang (CATT) asks further clarifications.
Sherry (Xiaomi) comments.
David (Samsung) comments, requests an EN.
Walter Dees (Philips) cannot agree r02 and r03.
Hong (Qualcomm) provides r04.
David (Samsung) provides r06 on top of r05 with the requested EN on LCS NF impact.
David (Samsung) reiterates the need for an EN.
Walter Dees (Philips) can also not agree r04, and provides r05.
==== Revisions Deadline ====
Hong (Qualcomm) is fine with r06.
Hong (Qualcomm) comments.
Sherry (Xiaomi) is fine with r06 to document it as a solution for this meeting and further work on it in the next meeting to see whether we can define it as the architecture assumption.
Richard (Ericsson) gives comments
Hong (Qualcomm) replies to Richard.
Sherry (Xiaomi) suggest to try resolving this on CC#3, but if we don't get a chance in CC#3, we agree r06.
Hong (Qualcomm) provides r07 for CC#3 in draft folder. Agree that we should approve r06 if we don't get chance in CC#3.
==== Comments Deadline ====
Revised
9.20 S2-2203351 P-CR Approval 23.700-86: TR 23.700-86: New Solution on reference architecture for Sidelink Positioning and Ranging services. Qualcomm Incorporated Rel-18 Revision of S2-2202769r06 + changes. Approved Approved
9.20 - - - Documents exceeding TU Budget - - Docs:=4 -
9.20 S2-2202347 P-CR Approval 23.700-86: Solution for KI#7 on ranging and sidelink positioning service exposure to AF. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.20 S2-2202492 P-CR Approval 23.700-86: TR 23.700-86: New solution for Ranging service exposure to server. Vivo Rel-18 Not Handled Not Handled
9.20 S2-2202906 P-CR Approval 23.700-86: Change term Observer UE to Reference UE. Xiaomi Rel-18 Not Handled Not Handled
9.20 S2-2202910 P-CR Approval 23.700-86: Proposed new solution on service initiated by UE. Xiaomi Rel-18 Not Handled Lars (Sony) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.21 - - - Study on System Support for AI/ML-based Services (FS_AIMLsys) - - Docs:=70 -
9.21 - - - Key Issue#1: Monitoring of Network Resource Utilization for support of Application AI/ML operations - - Docs:=2 -
9.21 S2-2202169 P-CR Approval 23.700-80: KI#1, 6: New Solution on 5GS Monitoring Capabilities for AI/ML-based Services. Samsung Rel-18 r02 agreed. Revised to S2-2203553 Yannick (Nokia): Nokia requests for clarification.
Belen (Ericsson) provides comments
David (Samsung) replies to Nokia
Malla (NTT DOCOMO) provided comment
David (Samsung) provides r01
David (Samsung) provides r02 with the EN requested by Ericsson
Belen (Ericsson) asks to add an EN to explain why these new parameters need to be monitored
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203553 P-CR Approval 23.700-80: KI#1, 6: New Solution on 5GS Monitoring Capabilities for AI/ML-based Services. Samsung Rel-18 Revision of S2-2202169r02. Approved Approved
9.21 - - - Key Issue#2: 5GC Information Exposure to UE - - Docs:=9 -
9.21 S2-2202038 P-CR Approval 23.700-80: Solution for KI#2: User Plane solution for 5GC information exposure to UE. Qualcomm Incorporated Rel-18 r09 agreed. Revised to S2-2203554, merging S2-2202391 Zhang (Ericsson) provides comments
Soohwan (ETRI) provides comments
Jungshin (Samsung) provides comments
Malla (NTT DOCOMO) provides comments
Jiahui (China Telecom) provides comments.
Vivian(vivo) provides the r02 again due to the email crossing.
Tricci (OPPO) thanks Juan Zhang (Qualcomm) for the kind acceptance to merge with OPPO S2-2202034 with S2-2202391 as the base. OPPO provides r01.
Jungshin (Samsung) provides further comments
Vivian(vivo) provides r02 based on OPPO's r01, trying to merge with S2-2202391.
Yannick (Nokia): Nokia provides comments. Without clear understanding of how the UE can use the analytics it is difficult to proceed with the solution.
Juan Zhang (Qualcomm) replies to Soohwan
Juan Zhang (Qualcomm) replies to Jungshin
Yannick (Nokia): Nokia provides comments on r02. Without clear understanding of how the UE can use the analytics it is difficult to proceed with the solution.
Juan Zhang (Qualcomm) provides r03 and replies to Nokia, China Telecom Samsung and vivo.
Tricci (OPPO) apologizes to Vivian(vivo) for the cross over email and thanks for r02 revision. OPPO is okay with r02 and hoping that it is okay for Qualcomm.
Soohwan (ETRI) request to add ETRI as co-source company.
Vivian (vivo) provides comments and r04.
Malla (NTT DOCOMO) provided r05.
Juan Zhang (Qualcomm) replies to Vivian.
Juan Zhang (Qualcomm) replies to Soohwan.
Juan Zhang (Qualcomm) replies to Malla.
Juan Zhang (Qualcomm) replies to Jungshin.
Tricci (OPPO) thanks for all the good discussions and provides r07 with minor editorial clean up.
Yannick (Nokia): Nokia provides r08.
Malla (NTT DOCOMO) provided r09.
Juan Zhang (Qualcomm) replies to Yannick.
Juan Zhang (Qualcomm) replies to Zhang
==== Revisions Deadline ====
Farooq (AT&T) asks a question.
Vivian(vivo) replies to Farooq (AT&T)'s question.
Vivian (vivo ) replies to Juan Zhang (Qualcomm).
Vivian (vivo ) is OK with the latest r09.
Juan Zhang (Qualcomm) replies to vivian (vivo).
Juan Zhang (Qualcomm) replies to Farooq.
Farooq (AT&T) responds to Vivian(vivo).
Farooq (AT&T) responds to Juan Zhang (Qualcomm).
Zhang (Ericsson) is OK with r09 and co-sign the paper
==== Comments Deadline ====
Revised
9.21 S2-2203554 P-CR Approval 23.700-80: Solution for KI#2: User Plane solution for 5GC information exposure to UE. Qualcomm Incorporated, Toyota Motor Corporation, OPPO, vivo, Samsung, Ericsson, ETRI Rel-18 Revision of S2-2202038r09, merging S2-2202391. Approved Approved
9.21 S2-2202391 P-CR Approval 23.700-80: FS_AIMLsys, KI#2, New solution for 5GC exposuring network data analytics to UE. Vivo Rel-18 Merged into S2-2203554 Zhang (Ericsson) provides comments
Soohwan (ETRI) provides comments.
Vivian(vivo) replies to Zhang (Ericsson)'s comments
Jungshin (Samsung) proposes the merge of S2-2202038 and S2-2202391.
Malla (NTT DOCOMO) proposed to merge and the changes can be easily implemented.
Tricci (OPPO) thanks Yannick (Nokia) caught the mistakes and will repost the PCR to the proper email thread for S2-2202038.
Yannick (Nokia): Nokia asks if revision provided by OPPO for S2-2202038 was recorded as part of the email thread for S2-2202038.
Tricci (OPPO) thanks Juan Zhang (Qualcomm) for the kind acceptance to merge with OPPO S2-2202034 with S2-2202391 as the base. OPPO provides r01.
Vivian (vivo) replies to Juan Zhang (Qualcomm) and Malla (NTT DOCOMO) comments.
Juan Zhang (Qualcomm) replies to Vivian.
==== Revisions Deadline ====
Farooq(AT&T) provides comment.
Vivian (vivo) replies to Farooq(AT&T)'s comment.
Vivian (vivo) clarifies this paper has been merged with S2-2202038.
==== Comments Deadline ====
Merged
9.21 S2-2202572 P-CR Approval 23.700-80: KI#2, New Sol: 5GC information exposure to UE by SMF. LG Electronics Rel-18 r06 agreed. Revised to S2-2203555 Zhang (Ericsson) provides comments
LaeYoung (LGE) answers to Zhang (Ericsson) and provides r01.
Soohwan (ETRI) asks questions.
Jungshin (Samsung): provides comments
LaeYoung (LGE) provides r02.
Huazhang (vivo) replies to LaeYoung (LGE) for some comments
Yannick (Nokia): Nokia requests that information on which data the UE can retrieve and how these data can be used for AIML operations are described in the solution. Without clear understanding of how the UE can use the data it is difficult to proceed with the solution.
Jungshin (Samsung) provides further comments
Juan Zhang (Qualcomm) provides comments
LaeYoung (LGE) provides r03 with answers.
Jianning (Xiaomi) provides questions for clarification
LaeYoung (LGE) provides r04 with answers.
Juan Zhang (Qualcomm) provides further comments
LaeYoung (LGE) provides r05 with answers.
Yannick (Nokia): Nokia provides r06.
LaeYoung (LGE) responds to Yannick (Nokia).
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r06.
==== Comments Deadline ====
Revised
9.21 S2-2203555 P-CR Approval 23.700-80: KI#2, New Sol: 5GC information exposure to UE by SMF. LG Electronics Rel-18 Revision of S2-2202572r06. Approved Approved
9.21 S2-2202641 P-CR Approval 23.700-80: New Solution on 5GC information exposure to UE. China Mobile Rel-18 r04 agreed. Revised to S2-2203556 Tricci (OPPO) shares the similar concern as Ericsson.
Zhang (Ericsson) provides comments
Soohwan (ETRI) asks questions.
Jungshin (Samsung): Samsung provide comments.
Yannick (Nokia): Nokia requests that information on which data the UE can retrieve and how these data can be used for AIML operations are described in the solution. Without clear understanding of how the UE can use the data it is difficult to proceed with the solution.
Aihua(CMCC) replies the comments ant provides r01.
Aihua(CMCC) replies the comments ant provides r02.
Aihua(CMCC) provides r03.
Yannick (Nokia): Nokia provides r04.
==== Revisions Deadline ====
Farooq(AT&T) comments.
Aihua(CMCC) replies to comment from Farooq(AT&T).
Jungshin (Samsung): We can live with r04
Juan Zhang (Qualcomm) provides comments
Aihua(CMCC) replies to comment from Juan Zhang (Qualcomm).
Juan Zhang (Qualcomm) is OK with r04.
==== Comments Deadline ====
Revised
9.21 S2-2203556 P-CR Approval 23.700-80: New Solution on 5GC information exposure to UE. China Mobile Rel-18 Revision of S2-2202641r04. Approved Approved
9.21 S2-2202959 P-CR Approval 23.700-80: New Solution: Information Exposure to UE. InterDigital Rel-18 r04 agreed. Revised to S2-2203557 Huazhang(vivo) have some comments
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) provides comments
Huazhang (vivo) replies to Juan Zhang (Qualcomm)
Ulises Olvera (InterDigital Inc.) replies to Huazhang (Vivo) and Juan (Qualcomm) and provides r01 .
LaeYoung (LGE) provides comment.
Juan Zhang (Qualcomm) replies to Huazhang
Juan Zhang (Qualcomm) provides further comments
Yannick (Nokia): Nokia provides r02.
Ulises Olvera (InterDigital Inc.) thanks Huazhang (Vivo) for his support and replies to Juan (Qualcomm), to LaeYoung(LGE) and Yannick(Nokia) and provides r03 .
==== Revisions Deadline ====
Ulises Olvera (InterDigital Inc.) addressing Juan's concern in r04.
Farooq (AT&T) comments.
Juan Zhang (Qualcomm) is OK with r04.
==== Comments Deadline ====
Revised
9.21 S2-2203557 P-CR Approval 23.700-80: New Solution: Information Exposure to UE. InterDigital Rel-18 Revision of S2-2202959r04. Approved Approved
9.21 - - - Key Issue#3: 5GC Information Exposure to Authorized 3rd Party for Application AI/ML operation - - Docs:=7 -
9.21 S2-2202363 P-CR Approval 23.700-80: KI #7 & #3, New Solution: Federated learning analytics as assistance to AI/ML application server. Nokia, Nokia Shanghai Bell Rel-18 r05 agreed. Revised to S2-2203558 Soohwan (ETRI) provides comments.
Juan Zhang (Qualcomm) provides comments.
Yannick (Nokia): Nokia replies to ETRI.
Jihoon (ETRI) asks questions with some comments.
Yannick (Nokia): Nokia provides r02.
Malla (NTT DOCOMO) asks clarification.
Yannick (Nokia): Nokia replies to Ericsson.
Zhang (Ericsson) ask for clarification for r02
Soohwan (ETRI) asks clarification
Yingying(CATT) provides comments and r03.
Jianning (Xiaomi) provide question for clarification
Juan Zhang (Qualcomm) provides further comments
Yingying(CATT) provides r04 and co-sign it.
Yannick (Nokia): Nokia provides r05.
==== Revisions Deadline ====
Yingying(CATT) provides r06.
==== Comments Deadline ====
Revised
9.21 S2-2203558 P-CR Approval 23.700-80: KI #7 & #3, New Solution: Federated learning analytics as assistance to AI/ML application server. Nokia, Nokia Shanghai Bell, CATT Rel-18 Revision of S2-2202363r05. Approved Approved
9.21 S2-2202657 P-CR Approval 23.700-80: 5GS information exposure for AI/ML operation. Lenovo Rel-18 r01 agreed. Revised to S2-2203559 Belen (Ericsson) asks more questions.
Belen (Ericsson) provides comments
Jungshin (Samsung): asks for clarification
Tricci (OPPO) has more fundamental questions and comments and asks for clarifications.
Jianning (Xiaomi) provide comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203559 P-CR Approval 23.700-80: 5GS information exposure for AI/ML operation . Lenovo Rel-18 Revision of S2-2202657r01. Approved Approved
9.21 S2-2202880 P-CR Approval 23.700-80: PCR 23.700-80: KI#3: User consent for UE-related information. MediaTek Inc. Rel-18 Approved Approved
9.21 S2-2202554 P-CR Approval 23.700-80: New Solution to KI#2 and KI#3 of FS_AIMLsys. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203560 Yannick (Nokia): Nokia requests that information on which data the UE can retrieve and how these data can be used for AIML operations are described in the solution. Without clear understanding of how the UE can use the data it is difficult to proceed with the solution.
Susan (Huawei) replies to Juan Zhang (Qualcomm) and Zhang (Ericsson).
Jungshin (Samsung) provides comments
Zhang (Ericsson) provides comments
Juan Zhang (Qualcomm) provides comments.
Juan Zhang (Qualcomm) provides further comments
Susan (Huawei) replies to Yannick (Nokia) and Jungshin (Samsung), and provides r01.
Susan (Huawei) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203560 P-CR Approval 23.700-80: New Solution to KI#2 and KI#3 of FS_AIMLsys. Huawei, HiSilicon, CATT Rel-18 Revision of S2-2202554r02. Approved Approved
9.21 - - - Key Issue#4: Enhancing External Parameter Provisioning - - Docs:=2 -
9.21 S2-2202424 P-CR Approval 23.700-80: New solution for KI#4: AF influence on customized AI/ML service policies China Telecommunications Rel-18 r03 agreed. Revised to S2-2203561 Zhang (Ericsson) ask for clarification
Menghan(China Telecom) replies to Zhang(Ericsson).
Mehrdad (Samsung) provides comments
Menghan(China Telecom) replies to Soohwan(ETRI)
Soohwan (ETRI) provides comments.
Menghan(China Telecom) provides r01
Juan Zhang (Qualcomm) provides comments
Zhang (Ericsson) provides comments
Menghan(China Telecom) replies to Juan(Qualcomm)
Menghan(China Telecom) provides r02
Juan Zhang (Qualcomm) further comments
Menghan(China Telecom) provides r03 and replies to Juan(Qualcomm)
Juan Zhang (Qualcomm) provides further comments
==== Revisions Deadline ====
Menghan(China Telecom) replies to Juan(Qualcomm) and Zhang(Ericsson)
JuanZhang (Qualcomm) replies to Menghan
Menghan(China Telecom) provides r04 and replies to Juan(Qualcomm) and Zhang(Ericsson)
==== Comments Deadline ====
Revised
9.21 S2-2203561 P-CR Approval 23.700-80: AF influence on customized AI/ML service policies. China Telecom Rel-18 Revision of S2-2202424r03. Approved Approved
9.21 - - - Key Issue#5: 5GC Enhancements to enable Application AI/ML Traffic Transport - - Docs:=8 -
9.21 S2-2201971 P-CR Approval 23.700-80: TR 23.700-80: KI#5 - BDT Extensions to support non-real-time Application AI/ML traffic transport. Oracle, Toyota, OPPO Rel-18 r06 agreed. Revised to S2-2203562 Mehrdad (Samsung) comments
Belen (Ericsson) provides comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203562 P-CR Approval 23.700-80: TR 23.700-80: KI#5 - BDT Extensions to support non-real-time Application AI/ML traffic transport. Oracle, Toyota, OPPO Rel-18 Revision of S2-2201971r06. Approved Approved
9.21 S2-2202547 P-CR Approval 23.700-80: Solution for KI#5: Traffic routing enhancements for Application AIML Traffic Transport. CATT, Ericsson Rel-18 r02 agreed. Revised to S2-2203563 Tricci (OPPO) provides comments and asks for clarifications.
Megha(Intel) provides comments
Malla (NTT DOCOMO) provides comments and asks for clarifications.
Mehrdad (Samsung) provides comments
Xiaoyan (CATT) provides r01.
Tricci (OPPO) thanks Xiaoyan (CATT) provides r01 and still don't quite understand what's new proposed by this PCR?
Yannick (Nokia): Nokia provides comments.
Xiaoyan (CATT) provides clarification to Yannick (Nokia).
Xiaoyan (CATT) clarifies to Tricci (OPPO).
Huazhang(vivo) replies to Xiaoyan (CATT) for some questions
Xiaoyan (CATT) replies to Huazhang(vivo).
Tricci (OPPO) thanks Xiaoyan (CATT) feedback and provides further comments.
Xiaoyan (CATT) provides r02.
Tricci (OPPO) thanks Xiaoyan (CATT) update.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203563 P-CR Approval 23.700-80: Solution for KI#5: Traffic routing enhancements for Application AIML Traffic Transport. CATT, Ericsson Rel-18 Revision of S2-2202547r02. Approved Approved
9.21 S2-2202548 P-CR Approval 23.700-80: Solution for KI#5: Charging for Application AI/ML Traffic. CATT Rel-18 r02 agreed. Revised to S2-2203564 Mehrdad (Samsung) provides comments
Belen (Ericsson) provides comments, objects to the solution in the current form
Xiaoyan (CATT) provides r01.
Xiaoyan (CATT) provides r02
Xiaoyan (CATT) replies to Belen (Ericsson).
Belen (Ericsson) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203564 P-CR Approval 23.700-80: Solution for KI#5: Charging for Application AI/ML Traffic. CATT Rel-18 Revision of S2-2202548r02. Approved Approved
9.21 S2-2202615 P-CR Approval 23.700-80: KI#5, New Sol: Support Application AI/ML Traffic Transport. Samsung Rel-18 r06 agreed. Revised to S2-2203565 Tricci (OPPO) shares exactly same concern as Zhang (Ericsson), and more...
Tricci (OPPO) asks additional question.
Jaewoo (LGE) provides comment.
Zhang (Ericsson) provides comments
Megha(Intel) provides comments
Malla (NTT DOCOMO) asks for clarification
Mehrdad (Samsung) replies to Intel, Ericsson, LGE, OPPO and NTT DOCOMO.
Tricci (OPPO) thanks Mehrdad (Samsung) for a super efficient responses to many of us, but still have fundamental questions to ask.
Mehrdad (Samsung) replies to OPP and provides r01.
Mehrdad (Samsung) replies to Qualcomm.
Juan Zhang (Qualcomm) provides comments
Yannick (Nokia): Nokia provides comments.
Mehrdad (Samsung) replies to Nokia and provides r02.
Yannick (Nokia): Nokia asks same question on r02.
Mehrdad (Samsung) replies to Nokia and provides r03.
Huazhang (vivo) replies to Mehrdad (Samsung) to request to change the ENs below:
Editor's note: whether and what parameters from the AI/ML transport configuration information can be shared to the UE via 5GC is FFS.
Mehrdad (Samsung) provides r04
Tricci (OPPO) suggests minor editorial correction to the EN below.
Mehrdad (Samsung) replies to Qualcomm and provides r06
Juan Zhang (Qualcomm) provides further comments
Mehrdad (Samsung) provides r05.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203565 P-CR Approval 23.700-80: KI#5, New Sol: Support Application AI/ML Traffic Transport. Samsung Rel-18 Revision of S2-2202615r06. Approved Approved
9.21 - - - Key Issue#6: QoS and Policy Enhancement - - Docs:=8 -
9.21 S2-2202881 P-CR Approval 23.700-80: PCR 23.700-80: KI#6: Network Conditions. MediaTek Inc. Rel-18 r01 agreed. Revised to S2-2203566 Guillaume (MediaTek Inc.): r01 is good.
Belen (Ericsson) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203566 P-CR Approval 23.700-80: PCR 23.700-80: KI#6: Network Conditions. MediaTek Inc., Ericsson Rel-18 Revision of S2-2202881r01. Approved Approved
9.21 S2-2202440 P-CR Approval 23.700-80: Solution on Flock QoS based Federated Learning Operation. NTT DOCOMO Rel-18 r04 agreed. Revised to S2-2203567 Megha(Intel) provides comments
Tricci (OPPO) provides comments
Megha (Intel) responds to Tricci(OPPO)
Tricci (OPPO) responds to Megha (Intel) feedback.
Malla (NTT DOCOMO) provided clarification to Oppo and Intel and provided r01.
Megha (Intel) provides further comments
Tricci (OPPO) provides further comments to this PCR.
Malla (NTT DOCOMO) replies to Belen (Ericsson)
Tricci (OPPO) thanks Malla (NTT DOCOMO) updates and provides further comments.
Belen (Ericsson) asks a question to DOCOMO
Malla (NTT DOCOMO) provided r03, please discard r02.
Belen (Ericsson) objects to r01 and initial version
Yannick (Nokia): Nokia provides questions/comments.
Tricci (OPPO) thanks Dongeun (Samsung) comments and provides feedback.
Juan Zhang (Qualcomm) provides comments
Belen (Ericsson) asks Malla again.
Malla (NTT DOCOMO) replies to Belen (Ericsson).
Belen (Ericsson) replies to Malla (DOCOMO)
Malla (NTT DOCOMO) provided r04
Dongeun (Samsung) comments again.
Malla (NTT DOCOMO) replied to Dongeun (Samsung).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203567 P-CR Approval 23.700-80: Solution on Flock QoS based Federated Learning Operation. NTT DOCOMO Rel-18 Revision of S2-2202440r04. Approved Approved
9.21 S2-2202947 P-CR Approval 23.700-80: New Solution: QoS monitoring for AIML application. InterDigital Rel-18 r04 agreed. Revised to S2-2203568 Violeta (Verizon) asks questions.
Belen (Ericsson) provides comments.
Juan Zhang (Qualcomm) provides comments.
Ulises Olvera (InterDigital Inc.) replies to Verizon, Qualcomm and Ericsson, and provides r01 .
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203568 P-CR Approval 23.700-80: New Solution: QoS monitoring for AIML application . InterDigital Rel-18 Revision of S2-2202947r04. Approved Approved
9.21 S2-2201995 P-CR Approval 23.700-80: TR 23.700-80: KI#2 - Solution for supporting the aggregated QoS parameters based on the Group-MBR. Oracle, Toyota, OPPO Rel-18 r04 agreed. Revised to S2-2203569 Zhang (Ericsson) ask questions
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203569 P-CR Approval 23.700-80: TR 23.700-80: KI#2 - Solution for supporting the aggregated QoS parameters based on the Group-MBR . Oracle, Toyota, OPPO Rel-18 Revision of S2-2201995r04. Approved Approved
9.21 - - - Key Issue#7: 5GS Assistance to Federated Learning Operation - - Docs:=22 -
9.21 S2-2202035 P-CR Approval 23.700-80: TR 23.700-80: KI#7 - 5GS assistance for FL member selection using QoS monitoring. OPPO Rel-18 r02 agreed. Revised to S2-2203570 Tricci (OPPO) thanks Megha(Intel) comments and provides feedback.
Megha(Intel) provides comments and questions for clarification on the solution proposal.
Yannick (Nokia): Nokia provides comments.
Megha (Intel) provides further comments.
Tricci (OPPO) thanks Megha(Intel) further comments and provides r01 to address the last two emails comments from Intel.
Tricci (OPPO) thanks Yannick (Nokia) comments and provides r02
Yannick (Nokia): Nokia comments on r02.
Zhang (Ericsson) ask questions
Tricci (OPPO) apologizes for the late response to Zhang (Ericsson) and would like to borrow HW's simulation result to explain my feedback.
==== Revisions Deadline ====
Megha(Intel) is ok with r02
==== Comments Deadline ====
Revised
9.21 S2-2203570 P-CR Approval 23.700-80: TR 23.700-80: KI#7 - 5GS assistance for FL member selection using QoS monitoring. OPPO Rel-18 Revision of S2-2202035r02. Approved Approved
9.21 S2-2202037 P-CR Approval 23.700-80: TR 23.700-80: KI#7 - 5GS assistance for FL member selection based on UE historical nomadic area info. OPPO Rel-18 r03 agreed. Revised to S2-2203571 Megha(Intel) provides comments and questions for clarification on the solution proposal.
Tricci (OPPO) thanks Megha(Intel) comments and provides feedback.
Jihoon (ETRI) provides comments and questions.
Megha (Intel) responds to Tricci (OPPO) provides further comments.
Tricci (OPPO) thanks Jihoon (ETRI) comments and provides feedback.
Tricci (OPPO) thanks Megha(Intel) new comments and provides feedback as well as r01.
Tricci (OPPO) thanks Yannick (Nokia) and David (Samsung) comments and provides feedback, and provides r02.
Tricci (OPPO) thanks Zhang (Ericsson) comments and provides feedback.
David (Samsung) provides comments.
Yannick (Nokia): Nokia provides comments.
Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia comments on r02.
Tricci (OPPO) thanks Yannick (Nokia) and apologizes for the missing update. OPPO provides r03 for the additional update.
Yannick (Nokia): Nokia thanks for r03 and is fine with it.
Tricci (OPPO) responds to Zhang (Ericsson)
==== Revisions Deadline ====
Zhang (Ericsson) thanks Tricci for the comments and OK with r03
Megha(Intel) is ok with r03
==== Comments Deadline ====
Revised
9.21 S2-2203571 P-CR Approval 23.700-80: TR 23.700-80: KI#7 - 5GS assistance for FL member selection based on UE historical nomadic area info. OPPO Rel-18 Revision of S2-2202037r03. Approved Approved
9.21 S2-2202040 P-CR Approval 23.700-80: Solution for KI#7: 5GS assisted FL member selection. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203572 Megha(Intel) asks questions for clarification on the solution proposal.
Dongeun (Samsung) ask for clarification.
Ulises Olvera (InterDigital) requests comments for clarification as described below.
Juan Zhang (Qualcomm) replies to Intel, Samsung, Ericsson and Nokia
Yannick (Nokia): Nokia provides comments.
Zhang (Ericsson) share the views of Samsung
Juan Zhang (Qualcomm) provides r01.
Jaewoo (LGE) provides comments.
Juan Zhang (Qualcomm) provides r02.
==== Revisions Deadline ====
Megha(Intel) is ok with r02
==== Comments Deadline ====
Revised
9.21 S2-2203572 P-CR Approval 23.700-80: Solution for KI#7: 5GS assisted FL member selection. Qualcomm Incorporated Rel-18 Revision of S2-2202040r02. Approved Approved
9.21 S2-2202127 P-CR Approval 23.700-80: New solution for KI#7: 5GS assistance to reduce the latency divergence. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203573 Wang Yuan (Huawei) replies to Zhang and Yannick, and provides r01.
Yannick (Nokia): Nokia provides comments.
Zhang (Ericsson) provides comments
Yannick (Nokia): Nokia provides comments on r01.
Wang Yuan (Huawei) replies to Yannick and provides r02.
Tricci (OPPO) thanks Wang Yuan (Huawei) for the beautiful simulation diagrams in the PCR and would like to ask for clarifications.
Wang Yuan (Huawei) replies to Tricci.
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r04 and co-sign the paper
Wang Yuan (Huawei) thanks for the co-sign.
Zhang (Ericsson) is OK with r02 and co-sign the paper
==== Comments Deadline ====
Revised
9.21 S2-2203573 P-CR Approval 23.700-80: New solution for KI#7: 5GS assistance to reduce the latency divergence. Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2202127r02. Approved Approved
9.21 S2-2202334 P-CR Approval 23.700-80: Solution for KI #7: 5GC Exposure of UE performance or group of UEs performance. ETRI Rel-18 r03 agreed. Revised to S2-2203574 Megha(Intel) provides comments and questions for clarification on the solution proposal.
Tricci (OPPO) has similar view as Megha(Intel) on the responsibility of the group management except that, it should not be limited to Federated Learning only.
Dongeun (Samsung) ask again for clarification.
Jaewook (ETRI) answers to Megha(Intel) and Tricci (OPPO).
Vivian (vivo) provides comments on r01.
Wang Yuan (Huawei) provides comments on r01.
Tricci (OPPO) thanks Vivian (vivo) kind suggestion to have this PCR to be merged into S2-2202035. Unfortunately, this will not work since two PCRs are very different.
Jaewook(ETRI) answers Vivian (vivo) and Wang Yuan (Huawei) .
Yannick (Nokia): Nokia notes that the link provided in previous email is incorrect.
Jaewook (ETRI) answers Dongeun (Samsung).
Jaewook (ETRI) sorry for incorrect link and provide correct link
Wang Yuan (Huawei) thanks for your reply and provides further comments on r02.
Jaewook (ETRI) thanks for Wang Yuan (Huawei) comments on r02 and provides r03.
Malla (NTT DOCOMO) asks clarification.
Jaewook (ETRI) answers to Malla (NTT DOCOMO).
==== Revisions Deadline ====
Wang Yuan (Huawei) is fine with r03.
==== Comments Deadline ====
Revised
9.21 S2-2203574 P-CR Approval 23.700-80: Solution for KI #7: 5GC Exposure of UE performance or group of UEs performance. ETRI Rel-18 Revision of S2-2202334r03. Approved Approved
9.21 S2-2202343 P-CR Approval 23.700-80: New solution for KI#7: 5GC-assisted federated learning over 5G VN group China Telecommunications Rel-18 r04 agreed. Revised to S2-2203575 Menghan(China Telecom) replies to Megha(Intel).
Megha(Intel) provides comments
Wang Yuan (Huawei) has concerns on this contribution.
Jihoon (ETRI) asks questions.
David (Samsung) shares concerns raised by other companies on this contribution.
Menghan(China Telecom) ask questions
Menghan(China Telecom) replies to David(Samsung)
Menghan(China Telecom) replies to Yuan(Huawei), David(Samsung), Zhang(Ericsson) and Jihoon(ETRI)
David (Samsung) replies
Zhang (Ericsson) provides comments
Wang Yuan (Huawei) provides further comments.
Jihoon (ETRI) asks further questions with some comments.
Menghan(China Telecom) provides r02
Jihoon (ETRI) provides comments with additional questions.
Menghan(China Telecom) provides r03 and relies to Jihoon(ETRI)
Jihoon (ETRI) replies to Menghan(China Telecom).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203575 P-CR Approval 23.700-80: 5GC-assisted Federated Learning over 5G VN group. China Telecom Rel-18 Revision of S2-2202343r04. Approved Approved
9.21 S2-2202364 P-CR Approval 23.700-80: KI #7 & #3, New Solution: Federated Learning Server assisting on federated learning members selection. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203576 Jungshin (Samsung) provides comments
Juan Zhang (Qualcomm) provides comments
Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) provides comments
Tricci (OPPO) requests Nokia to please respond to the previous question on the target domain (i.e. part of AF vs. 5GC) of the proposed new function (i.e. FL Server) n in this PCR because it affects the follow-up questions from many companies. Without understand better for the design intent, it is difficult to allow this PCR to progress.
Tricci (OPPO) apologizes the previous misleading email for the target domain of the FL Server, and would like to ask for more clarifications of this PCR.
David (Samsung) provides comments
Tricci (OPPO) thanks Yannick (Nokia) for the update and would like to follow up for one missing responses and one further clarifications.
Yannick (Nokia): Nokia provides r01.
Yannick (Nokia): Nokia provides r02.
Tricci (OPPO) thanks Yannick (Nokia) always being so kind to address my question... r02 works for me.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203576 P-CR Approval 23.700-80: KI #7 & #3, New Solution: Federated Learning Server assisting on federated learning members selection. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202364r02. Approved Approved
9.21 S2-2202392 P-CR Approval 23.700-80: FS_AIMLsys, KI#7, New solution for 5GS Assistance to Federated Learning. Vivo Rel-18 r02 agreed. Revised to S2-2203577 Jihoon (ETRI) asks questions.
Vivian(vivo) replies to Jihoon (ETRI)'s questions and provides r01.
Vivian (vivo) replies to Yannick (Nokia) comments and provides r02.
Yannick (Nokia): Nokia provides comments on r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203577 P-CR Approval 23.700-80: FS_AIMLsys, KI#7, New solution for 5GS Assistance to Federated Learning. Vivo Rel-18 Revision of S2-2202392r02. Approved Approved
9.21 S2-2202412 P-CR Approval 23.700-80: KI#7, New Sol: Providing 5GS Assistance information to AF for Federated Learning Operation. LG Electronics Rel-18 r05 agreed. Revised to S2-2203578 Tricci (OPPO) asks for clarifications of this PCR.
Jaewoo (LGE) responds to Megha (Intel) and provides r01.
Megha(Intel) provides comments
Jaewoo (LGE) responds to Tricci (OPPO) and provides r02.
David (Samsung) provides comments.
Megha (Intel) provides further comments and express concern on the assumption in this solution.
Jaewoo (LGE) responds to David (Samsung).
Jaewoo (LGE) responds to Megha (Intel) and provides r03.
Wang Yuan (Huawei) has concerns on this contribution.
Jaewoo (LGE) responds to Wang Yuan (Huawei) and Yannick (Nokia).
Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) thanks for the response and provides suggestions on r03.
Tricci (OPPO) would like to suggest LG to clarify one fundamental aspect of the AIML NF.
Jaewoo (LGE) responds to Wang Yuan (Huawei) and Tricci (OPPO), and provides r04.
Tricci (OPPO) thanks Jaewoo ( LG) for the update.
Jaewoo (LGE) thanks David (Samsung) for the revision and is fine with r05.
David (Samsung) thanks Jaewoo (LGE) and provides r05.
==== Revisions Deadline ====
Wang Yuan (Huawei) is fine with r05..
Megha(Intel) is ok with r05
==== Comments Deadline ====
Revised
9.21 S2-2203578 P-CR Approval 23.700-80: KI#7, New Sol: Providing 5GS Assistance information to AF for Federated Learning Operation. LG Electronics Rel-18 Revision of S2-2202412r05. Approved Approved
9.21 S2-2202443 P-CR Approval 23.700-80: Solution for FL operation with 5GS coordination for UE selection. NTT DOCOMO Rel-18 r04 agreed. Revised to S2-2203579 Jihoon (ETRI) provides comments.
Juan Zhang (Qualcomm) provides comments
Yannick (Nokia): Nokia provides comments.
Malla (NTT DOCOMO) provided r01.
Jihoon (ETRI) asks further questions for clarification.
Malla (NTT DOCOMO) replies to Jihoon (ETRI) and provided r02.
Jihoon (ETRI) provides minor comments.
Malla (NTT DOCOMO) provided r03.
Malla (NTT DOCOMO) provided r04.
Jihoon (ETRI) replies to Malla (NTT DOCOMO).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.21 S2-2203579 P-CR Approval 23.700-80: Solution for FL operation with 5GS coordination for UE selection. NTT DOCOMO Rel-18 Revision of S2-2202443r04. Approved Approved
9.21 S2-2202729 P-CR Approval 23.700-80: Solution (KI#7): 5GS assistance to selection of UEs for federated learning operation. ETRI Rel-18 r01 agreed. Revised to S2-2203580 Yannick (Nokia): Nokia provides comments.
Zhang (Ericsson) provides comments
Jihoon (ETRI) replies to Zhang (Ericsson) and Yannick (Nokia), providing r01.
==== Revisions Deadline ====
Zhang (Ericsson) is OK r01
==== Comments Deadline ====
Revised
9.21 S2-2203580 P-CR Approval 23.700-80: Solution (KI#7): 5GS assistance to selection of UEs for federated learning operation. ETRI Rel-18 Revision of S2-2202729r01. Approved Approved
9.21 - - - Documents exceeding TU Budget - - Docs:=12 -
9.21 S2-2202675 DISCUSSION Agreement QoS and Policy enhancement for AI/ML service. Lenovo Rel-18 Not Handled Not Handled
9.21 S2-2202696 DISCUSSION Agreement Location based FL member selection. TOYOTA MOTOR CORPORATION Rel-18 Not Handled Not Handled
9.21 S2-2202958 P-CR Approval 23.700-80: Update: Update on Architectural Assumptions related to Application AI/ML operation within a single slice. InterDigital Rel-18 Not Handled Not Handled
9.21 S2-2202034 P-CR Approval 23.700-80: TR 23.700-80: KI#2 - Network Analytic Data Exposure to UE via DCAF. OPPO Rel-18 Not Handled Not Handled
9.21 S2-2202755 P-CR Approval 23.700-80: A New Solution for KI#7: Support of group QoS for Federated Learning. Samsung Rel-18 Not Handled Not Handled
9.21 S2-2202126 P-CR Approval 23.700-80: New solution for KI#7: 5GS assistance to FL member selection. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.21 S2-2202421 P-CR Approval 23.700-80: Update KI#7: Adding central server to member selection section China Telecommunications Rel-18 Not Handled Not Handled
9.21 S2-2202555 P-CR Approval 23.700-80: Solution to KI#4 of FS_AIMLsys. Huawei, HiSilicon Rel-18 Not Handled Tricci (OPPO) clarifies that this PCR has been moved to agenda item 'NOT HANDLE' and we should not spend time to comment on it.
Zhang (Ericsson) provides comments
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.21 S2-2202589 P-CR Approval 23.700-80: Solution for KI#3: Expose AI/ML traffic transmission status to the authorized 3rd party for Application Layer AI/ML Operation. CATT Rel-18 Not Handled Not Handled
9.21 S2-2202390 P-CR Approval 23.700-80: FS_AIMLsys, KI#2, New solution for the UE Optimizes AIML operations by analytics from NWDAF. Vivo Rel-18 Not Handled Not Handled
9.21 S2-2202445 P-CR Approval 23.700-80: KI#2: New solution for UP-based 5GC information exposure to UE. ETRI Rel-18 Not Handled Not Handled
9.21 S2-2202949 P-CR Approval 23.700-80: New Solution: Information Exposure to authorized 3rd parties. InterDigital Rel-18 Not Handled Not Handled
9.22 - - - Study on Enhancement of 5G UE Policy (FS_eUEPO) - - Docs:=51 -
9.22 - - - New Solutions for KI#1 (URSP in VPLMN) - - Docs:=12 -
9.22 S2-2202066 P-CR Approval 23.700-85: Solution for Key Issue#1: Provisioning V-URSP rules for roaming scenario. Samsung Rel-18 Noted Belen (Ericsson) provides comments
Dimitris (Lenovo) provides comments
Pallab (Nokia) raises concern with the solution and points that the solution is going against the agreed scope of the study
Wen (vivo) share same concerns that the solution is going against the agreed scope of the study
Belen (Ericsson) thinks that the solution is in the scope of the study.
Jicheol (Samsung) answers.
Belen (Ericsson) asks for a new revision including answered comments.
Pallab (Nokia) responds to Jicheol (Samsung) and concern about this solution being out of scope of the study is still maintained.
Belen (Ericsson) asks to Nokia a question
Pallab (Nokia) responds to Belen (Ericsson).
Krisztian (Apple) shares the concerns this solution is not aligned with the Key Issue statement 'backward compatibility with the existing framework of policy control based on HPLMN shall be maintained'.
Jicheol (Samsung) clarifies this solution complies with 'backward compatibility with the existing framework of policy control based on HPLMN shall be maintained'.
Changhong (Intel) comments.
Yang (OPPO) comments.
Pallab (Nokia) comments on r01.
Wen (vivo) comments.
Jicheol (Samsung) asks for clarification on the comment.
Belen (Ericsson) provides comments.
Pallab (Nokia) objects to this solution unless it is clearly specified how the HPLMN controls the URSP determination or an EN is added as proposed to address this in next meeting
Hong (Qualcomm) comments.
Krisztian (Apple) comments.
Jicheol (Samsung) comments.
Jicheol (Samsung) provides r02 (added ENs to capture the concerns)
Pallab (Nokia) proposes a different EN text to move forward. r02 is not agreeable
Belen (Ericsson) proposes an EN.
==== Revisions Deadline ====
Jicheol (Samsung) is asking whether the lastest EN provided by Erisson is accepable to everyone.
If so, the proposal is to replace the last Editor's Note of the clause 6.X.1 with following statement on top of S2-2202066r02:
'Editor's Note: How the HPLMN remains in control of the URSP Rules provided to the UE by the VPLMN is FFS'
Pallab (Nokia) proposes to NOTE the paper. There is no point in adding a solution into the TR that is clearly not in scope with an EN to study how to comply to the SID scope.
Jicheol (Samsung) disagree with Nokia way forward proposal.
Pallab (Nokia) responds to Jicheol (Samsung).
Belen (Ericsson) supports Samsung proposal to add an EN on top of r02
==== Comments Deadline ====
Noted
9.22 S2-2202454 P-CR Approval 23.700-85: 23.700-85: Solution for KI#1; URSP provisioning when a UE is not served by its home operator. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2203610. Dimitris (Lenovo) proposes to merge to S2-2202469
Yang (OPPO) comments
Pallab (Nokia) responds to Dimitris (Lenovo)
Belen (Ericsson) provides comments
Changhong (Intel) comments and propose not to merge this solution and keep it as standalone.
Pallab (Nokia) responds Belen (Ericsson)
Belen (Ericsson) provides comments.
Dimitris (Lenovo) comments
Changhong (Intel) replies to DK.
Yang (OPPO) shares the similar comment as Intel
Pallab (Nokia) responds to Oppo, Intel, Ericsson, Lenovo and provided r01. Proposes no to merge with S2-2202469
Pallab (Nokia) responds to Jicheol (Samsung)
Jicheol (Samsung) ask a question.
Jicheol (Samsung) comments.
Pallab (Nokia) responds to Jicheol (Samsung) and provides r02
==== Revisions Deadline ====
Dieter (Deutsche Telekom) objects to all revisions that include CH and SNPN as out of scope - (CH and SNPN can still be removed and the a rev approved at CC#2 or 3) .
Pallab (Nokia) requests to discuss this at CC#2.
Proposes to agree r02 with following changes to address the concern from DT: 'remove any reference to SNPN and CH from the solution.'
Antoine (Orange) objects to r00, r01 and r02. r03 does not seem to qualify as a simple change that can be approved during the CC.
Pallab (Nokia) responds to Antoine (Orange) and highlights that if concerns related to SNPN+CH were raised before revision deadline a revision could have been provided.
Also, the changes proposed are simple, 'remove SNPN and CH references from the solution and impacts'.
Antoine (Orange): This contribution should not have been submitted with text assuming that SNPN+CH is roaming. This has been written in the spec and should not have to be repeated at every meeting.
==== Comments Deadline ====
Revised
9.22 S2-2203610 P-CR Approval 23.700-85: 23.700-85: Solution for KI#1; URSP provisioning when a UE is not served by its home operator. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202454r02. Approved Approved
9.22 S2-2202469 P-CR Approval 23.700-85: Solution for KI#1: VPLMN influencing URSP rules creation in an HPLMN. Lenovo Rel-18 r04 agreed. Revised to S2-2203609. Yang (OPPO) raise questions to the solution
Dimitris (Lenovo) provides r01 to potentially merge with S2-2202454 and others. Addresses comments from Yang (Oppo)
Krisztian (Apple) supports r01 and provides r02 to indicate the merge with S2-2202887.
Changhong (Intel) comments and has concern with VPLMN validity in TD.
Changhong (Intel) comments and asks not to merge 2454 since this solution is different.
Dimitris (Lenovo) responds to Changhong indicates the PLMN ID is added within the RSD component not TD
Dimitris (Lenovo) further responds to Changhong
Pallab (Nokia) comments and also asks not to merge 2454 at this stage.
Belen (Ericsson) provides comments.
Dimitris (Lenovo) responds to Belen (Ericsson)
Yang (OPPO) further comments
Yang (OPPO) raises a technical concern
Dimitris (Lenovo) does not see an issue on the concern raised
Dimitris (Lenovo) responds to Yang (Oppo)
Yang (OPPO) thanks Dimitris reply and provides answers
Dimitris (Lenovo) provides r03
Yang (OPPO) asks to add a EN
Yang (OPPO) provides r04
Dimitris (Lenovo) comments on r04
==== Revisions Deadline ====
Yang (OPPO) replies to Dimitris
Dimitris (Lenovo) replies to Yang (Oppo) propose to proceed with r02 or r04 depending on the discussion
Yang (OPPO) responds to Dimitris (Lenovo) and prefer to go with r04 in this meeting.
Dieter (Deutsche Telekom) objects to all revisions that include CH and SNPN as out of scope - (CH and SNPN can still be removed and the a rev approved at CC#2 or 3) .
Dimitris (Lenovo) is OK to proceed with r04
Dimitris (Lenovo) propose to discuss at CC#2/CC#3
Proposes to agree r04 with following changes to address the concern from DT: 'remove any reference to SNPN and CH from the solution.'
Antoine (Orange) objects to r01, r02, r03 and r04 for the same reason as Dieter.
Dimitris (Lenovo) provides proposed r04 amendment in drafts folder for CC#3
==== Comments Deadline ====
Revised
9.22 S2-2203609 P-CR Approval 23.700-85: Solution for KI#1: VPLMN influencing URSP rules creation in an HPLMN . Lenovo, Apple Rel-18 Revision of S2-2202469r04. Approved Approved
9.22 S2-2202476 P-CR Approval 23.700-85: TR 23.700-85: New solution for URSP provisioning and updating in roaming. Vivo Rel-18 Approved Dimitris (Lenovo) has concerns adding PLMN id in the traffic descriptor
Wen (vivo) replies to Dimitris
Pallab (Nokia) requests for clarification
Wen (vivo) responds
Pallab (Nokia) responds to Wen (vivo)
Changhong (Intel) comments
Wen (vivo) responds to Pallab (Nokia)
Krisztian (Apple) shares the concerns about adding PLMN ID in the traffic descriptor.
Wen (vivo) responds to Krisztian (Apple).
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.22 S2-2202557 P-CR Approval 23.700-85: Solution for URSP in VPLMN. Huawei, HiSilicon Rel-18 Approved Susan (Huawei) replies to Dimitris (Lenovo).
Dimitris (Lenovo) further responds to Susan (Huawei)
Dimitris (Lenovo) has a question
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.22 S2-2202574 P-CR Approval 23.700-85: KI#1, New Sol: URSP determination based on service parameter obtained from VPLMN. LG Electronics Rel-18 r03 agreed. Revised to S2-2203112 Dimitris (Lenovo) proposes to merge to S2-2202469
LaeYoung (LGE) replies to Dimitris (Lenovo) that she does not think this solution can be merged with 2469 due to their differences.
Dimitris (Lenovo) provides further question
LaeYoung (LGE) replies to Dimitris (Lenovo).
Dimitris (Lenovo) asks further question
LaeYoung (LGE) responds to Dimitris (Lenovo).
LaeYoung (LGE) responds to Belen (Ericsson).
Belen (Ericsson) objects to this contribution.
LaeYoung (LGE) provides r01.
Dimitris (Lenovo) comments on r01
Dimitris (Lenovo) responds to LaeYoung (LGE)
LaeYoung (LGE) provides r02.
Belen (Ericsson) responds to LGE, provides comments.
Belen (Ericsson) comments
LaeYoung (LGE) provides r03 with answer.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203112 P-CR Approval 23.700-85: KI#1, New Sol: URSP determination based on service parameter obtained from VPLMN. LG Electronics Rel-18 Revision of S2-2202574r03. Approved Approved
9.22 S2-2202771 P-CR Approval 23.700-85: TR 23.700-85: KI#1, new solution proposal on URSP in VPLMN. Qualcomm Incorporated, Intel Rel-18 r01 + changes agreed. Revised to S2-2203594. Dimitris (Lenovo) does not see how this solution is backwards compatible
Belen (Ericsson) provides comments
Jicheol (Samsung) comments.
Hong (Qualcomm) provides r01.
Belen (Ericsson) provides comments.
Hong (Qualcomm) replies to Belen.
Belen (Ericsson) objects to the solution.
==== Revisions Deadline ====
Hong (Qualcomm) replies to Belen that the previous Ericsson comment does not reflect the paper's content.
Yang (OPPO) supports to agree this solution with r01. And also agree it is technically correct
Changhong (Intel) proposes to agree r01.
Tao(VC) please check r01 agreeable or not.
Belen (Ericsson) objects to r01 as already stated. Proposes an EN
Hong (Qualcomm) replies to Belen, and suggest to handle in CC#3 if any new EN needs to be added as in r02 (in draft folder).
Belen (Ericsson) replies to QC.
Hong (Qualcomm) provides r03 in draft folder for CC#3.
Belen (Ericsson) is okay with r03
==== Comments Deadline ====
Revised
9.22 S2-2203594 P-CR Approval 23.700-85: TR 23.700-85: KI#1, new solution proposal on URSP in VPLMN. Qualcomm Incorporated, Intel Rel-18 Revision of S2-2202771r01 + changes. Approved Approved
9.22 S2-2202887 P-CR Approval 23.700-85: New Sol for KI#1: Influencing the determination of USRP rules with VPLMN URSP Guidance. Apple Rel-18 Merged into S2-2202469 (noted). Noted Yang (OPPO) raise concern to the solution
Dimitris (Lenovo) proposes to merge
Krisztian (Apple) is OK to merge with S2-2202469r02.
==== Revisions Deadline ====
Dieter (Deutsche Telekom) objects to all revisions that include CH and SNPN as out of scope - (CH and SNPN can still be removed and the a rev approved at CC#2 or 3) .
==== Comments Deadline ====
Noted
9.22 - - - New Solutions for KI#2 (5GC awareness of URSP enforcement) - - Docs:=17 -
9.22 S2-2202067 P-CR Approval 23.700-85: Solution for Key Issue #2: URSP compliance verification. Samsung Rel-18 r02 agreed. Revised to S2-2203113 Krisztian (Apple) objects to this solution.
Jicheol (Samsung) responses.
Belen (Ericsson) provides comments.
Huazhang (vivo) comments
Changhong (Intel) asks to clearly state the impact to UE and network function.
Chi (China Unicom) asks questions for clarification.
Jicheol (Samsung) provides r01.
Krisztian (Apple) responds to Jicheol.
Dimitris (Lenovo) comments on r01
Jicheol (Samsung) answers Dimitris questions.
Krisztian (Apple) provides r02 including an EN about user consent (similar to 2265r02).
==== Revisions Deadline ====
Jicheol ask a question for added EN.
==== Comments Deadline ====
Revised
9.22 S2-2203113 P-CR Approval 23.700-85: Solution for Key Issue #2: URSP compliance verification. Samsung Rel-18 Revision of S2-2202067r02. Approved Approved
9.22 S2-2202265 P-CR Approval 23.700-85: Solution for KI#2: PSI reporting for awareness of URSP enforcement. China Unicom Rel-18 r02 agreed. Revised to S2-2203114 Krisztian (Apple) objects to this solution.
Belen (Ericsson) provides comments
Huazhang (vivo) provides comments
Chi (China Unicom) replies to Huazhang (vivo) and provides r01.
Chi (China Unicom) replies to Belen (Ericsson).
Chi (China Unicom) replies to Krisztian (Apple).
Krisztian (Apple) responds to Chi.
Chi (China Unicom) replies to Krisztian (Apple) and provides r02.
==== Revisions Deadline ====
Hong (Qualcomm) comments.
==== Comments Deadline ====
Revised
9.22 S2-2203114 P-CR Approval 23.700-85: Solution for KI#2: PSI reporting for awareness of URSP enforcement. China Unicom Rel-18 Revision of S2-2202265r02. Approved Approved
9.22 S2-2202467 P-CR Approval 23.700-85: Solution for KI#2: Per-PDU session awareness of URSP enforcement. Lenovo Rel-18 r02 agreed. Revised to S2-2203115 Krisztian (Apple) objects to this solution.
Dimitris (Lenovo) requests clarification form Krisztian (Apple)
Yang (OPPO) asks a question.
Dimitris (Lenovo) responds to Yang (Oppo)
Dimitris (Lenovo) provides r01
Krisztian (Apple) responds to Dimitris.
Pallab (Nokia) asks further questions
Dimitris (Lenovo) responds to Pallab (Nokia)
Pallab (Nokia) comments on r01 and asks for clarification in the pCR how the solution works.
Pallab (Nokia) responds to Dimitris
Dimitris (Lenovo) provides r02 and comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203115 P-CR Approval 23.700-85: Solution for KI#2: Per-PDU session awareness of URSP enforcement . Lenovo Rel-18 Revision of S2-2202467r02. Approved Approved
9.22 S2-2202475 P-CR Approval 23.700-85: Solution for the KI#2: Network based URSP rules enforcement feedback. Vivo Rel-18 Approved Huazhang(vivo) replies to Krisztian (Apple)
Krisztian (Apple) comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.22 S2-2202549 P-CR Approval 23.700-85: Solution for KI#2 5GC awareness of URSP enforcement. OPPO Rel-18 r01 agreed. Revised to S2-2203116 Krisztian (Apple) comments.
Yang (OPPO) answers.
Yang (OPPO) responds to Dimitris
Dimitris (Lenovo) comments
Yang (OPPO) replies to Changhong and provides r01.
Changhong (Intel) comments.
Krisztian (Apple) responds to Yang.
Zhuoyi (China Telecom) comments.
Yang (OPPO) replies to Apple.
Yang (OPPO) responds to CTC
Hong (Qualcomm) comments.
Yang (OPPO) replies to Hong
Yang (OPPO) provides a question to CTC
Zhuoyi (China Telecom) replies to OPPO
Jicheol (Samsung) comments.
Yang (OPPO) replies to CTC
==== Revisions Deadline ====
==== Comments Deadline ====
Yang (OPPO) replies to Jicheol.
Revised
9.22 S2-2203116 P-CR Approval 23.700-85: Solution for KI#2 5GC awareness of URSP enforcement. OPPO Rel-18 Revision of S2-2202549r01. Approved Approved
9.22 S2-2202556 P-CR Approval 23.700-85: Solution for 5GC awareness of URSP enforcement. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2203117 Krisztian (Apple) objects to this solution.
Yang (OPPO) comments.
Huazhang (vivo) has concerns of UPF drop the packets
Laurent (Nokia): Comments requiring EN
Laurent (Nokia): Comments requiring updates
Haiyang (Huawei) response
Haiyang (Huawei) provides r02 (please ignore r01)
Krisztian (Apple) provides r04 including an EN about user consent (similar to 2265r02). Please ignore r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203117 P-CR Approval 23.700-85: Solution for 5GC awareness of URSP enforcement. Huawei, HiSilicon Rel-18 Revision of S2-2202556r04. Approved Approved
9.22 S2-2202699 P-CR Approval 23.700-85: EUEPO solution for Key Issue 2. China Telecom Rel-18 r03 agreed. Revised to S2-2203118 Krisztian (Apple) objects to this solution.
Yang (OPPO) comments to the solution.
Pinghui (China Telecom) responses and provide r01
Dimitris (Lenovo) has a question
Pinghui (China Telecom) provides r02
Iskren (NEC) comments
Pinghui (China Telecom) replies to Dimitris(Lenovo)
Pallab (Nokia) asks questions
Antoine (Orange) replies to Pallab.
Krisztian (Apple) provides r03 including an EN about user consent (similar to 2265r02).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203118 P-CR Approval 23.700-85: EUEPO solution for Key Issue 2 . China Telecom Rel-18 Revision of S2-2202699r03. Approved Approved
9.22 S2-2202762 P-CR Approval 23.700-85: KI#2, New Sol: 5GC awareness of URSP rule evaluation and verification of network slice usage. Orange Rel-18 r02 agreed. Revised to S2-2203119 Krisztian (Apple) objects to this solution.
Susana (Vodafone) supports this proposal and comments.
Huazhang(vivo) comments
Dimitris (Lenovo) asks a question
Changhong (Intel) comments.
Antoine (Orange) provide r01 addressing the comments.
Antoine (Orange) provides r03.
Krisztian (Apple) provides r02 extending the EN about user privacy (EN matches 2265r02).
==== Revisions Deadline ====
Krisztian (Apple) supports r02 but cannot live with r03.
Antoine (Orange) can consent to r02.
==== Comments Deadline ====
Revised
9.22 S2-2203119 P-CR Approval 23.700-85: KI#2, New Sol: 5GC awareness of URSP rule evaluation and verification of network slice usage. Orange Rel-18 Revision of S2-2202762r02. Approved Approved
9.22 S2-2202860 P-CR Approval 23.700-85: KI#2 new Solution X: UE URSP enforcement validation by the network. NEC Rel-18 r04 agreed. Revised to S2-2203120 Krisztian (Apple) objects to this solution.
Huazhang(vivo) have some comments
Changhong (Intel) comments
Iskren (NEC) replies to comments from Kris (Apple), Huazhang(vivo) and Changhong (Intel) and provides updates in r01
Huazhang(vivo) reply to Iskren (NEC)
Krisztian (Apple) has a concern on the new NOTE and maintains objection.
Iskren (NEC) answers Huazhang(vivo)
Hong (Qualcomm) comments.
Iskren (NEC) provides r02. I have removed the Note and added an EN on the App ID. I hope it is acceptable. It will allow us to further discuss and clarify any potential privacy issues.
Pallab (Nokia) provides comments on r02.
Iskren (NEC) adds the requested EN by Pallab (Nokia) and provides r03.
Krisztian (Apple) provides r04 re-formulating the EN about user privacy to match with 2265r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203120 P-CR Approval 23.700-85: KI#2 new Solution X: UE URSP enforcement validation by the network . NEC Rel-18 Revision of S2-2202860r04. Approved Approved
9.22 - - - New Solutions for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=11 -
9.22 S2-2201974 P-CR Approval 23.700-85: New Solution to KI#3: URSPs into PCO for EPC. Ericsson Rel-18 r01 agreed. Revised to S2-2203121 Susan (Huawei) raises question for clarification.
Changhong (Intel) comments.
Belen (Ericsson) replies to Intel and Huawei
Changhong (Intel) replies to Belen.
Belen (Ericsson) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203121 P-CR Approval 23.700-85: New Solution to KI#3: URSPs into PCO for EPC. Ericsson Rel-18 Revision of S2-2201974r01. Approved Approved
9.22 S2-2202452 P-CR Approval 23.700-85: 23.700-85: Solution for KI#3; Indication of applicability of URSP to UE in EPS. Nokia, Nokia Shanghai Bell Rel-18 Approved Susan (Huawei) don't think the indication proposed in this paper is needed.
Yang (OPPO) asks a question.
Pallab (Nokia) responds to Susan (Huawei).
Pallab (Nokia) responds to Yang (OPPO).
Changhong (Intel) comments.
Yang (OPPO) replies
Yang (OPPO) further comments
Pallab (Nokia) responds to Yang (OPPO) and Changhong (Intel).
Belen (Ericsson) provides some comments.
Pallab (Nokia) responds to Belen (Ericsson)
Belen (Ericsson) provides comments.
Hong (Qualcomm) comments.
Yang (OPPO) comments
Pallab (Nokia) responds to Yang (OPPO) and Hong (Qualcomm).
Belen (Ericsson) asks to Nokia.
Pallab (Nokia) responds Belen.
Belen (Ericsson) replies to Pallb (Nokia)
==== Revisions Deadline ====
Pallab (Nokia) responds to Hong (Qualcomm)
==== Comments Deadline ====
Approved
9.22 S2-2202415 P-CR Approval 23.700-33: KI#3, New Solution: Provisioning consistent URSP to UE across 5GS and EPS for Single PCF Deployment Intel Rel-18 r03 agreed. Revised to S2-2203122, merging S2-2202545 and S2-2202941 Belen (Ericsson) provides comments
Susan (Huawei) provides comments.
Changhong (Intel) provides r01.
Yang (OPPO) provides r02 merging 2941 and 2545.
Belen (Ericsson) asks one question on r02.
Changhong (Intel) replies to Belen and provides r03.
Belen (Ericsson) replies to Intel, it is okay with r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203122 P-CR Approval 23.700-33: KI#3, New Solution: Provisioning consistent URSP to UE across 5GS and EPS for Single PCF Deployment. Intel, Apple, OPPO Rel-18 Revision of S2-2202415r03, merging S2-2202545 and S2-2202941. Approved Approved
9.22 S2-2202545 P-CR Approval 23.700-85: Solution for KI#3 consistent URSP provisioning to UE across 5GS and EPS. OPPO Rel-18 Merged into S2-2203122 Changhong (Intel) proposes to merge it into S2-2202415.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.22 S2-2202744 P-CR Approval 23.700-85: Solution: KI#3 Provision consistent URSP to UE across 5GS and EPS NEC Rel-18 r02 agreed. Revised to S2-2203123 Susan (Huawei) provides comments.
Kundan (NEC) provides response to Susan(Huawei).
Belen (Ericsson) asks questions
Kundan(NEC) responds to Belen.
Kundan(NEC) provides r01 addressing Susan comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203123 P-CR Approval 23.700-85: Solution: KI#3 Provision consistent URSP to UE across 5GS and EPS. NEC Rel-18 Revision of S2-2202744r02. Approved Approved
9.22 S2-2202808 P-CR Approval 23.700-85: Solution for KI#3: Provision consistent URSP to UE across 5GS and EPS. Samsung Rel-18 r03 agreed. Revised to S2-2203124 Susan (Huawei) provides comment.
DongYeon (Samsung) responds to Susan (Huawei), and provides r01.
DongYeon (Samsung) replies to Zhuoyi (China Telecom).
DongYeon (Samsung) provides r02.
Zhuoyi (China Telecom) ask for clarification.
Belen (Ericsson) provides comments.
Zhuoyi (China Telecom) asks further questions.
DongYeon (Samsung) replies to Zhuoyi (China Telecom), Belen (Ericsson), and provides r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203124 P-CR Approval 23.700-85: Solution for KI#3: Provision consistent URSP to UE across 5GS and EPS. Samsung Rel-18 Revision of S2-2202808r03. Approved Approved
9.22 S2-2202941 P-CR Approval 23.700-85: 23.700-85: Solution for KI #3 URSP in EPS. Apple Rel-18 Merged into S2-2203122 Belen (Ericsson) provides comments
Changhong (Intel) proposes to merge it into S2-2202415.
Susan (Huawei) provides comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.22 - - - New Solutions for KI#4 (Support standardized and operator-specific traffic categories in URSP) - - Docs:=11 -
9.22 S2-2202060 P-CR Approval 23.700-85: New Solution on KI#6: Traffic Category with existing mechanism. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203125 Dimitris (Lenovo) has questions for clarification
Haiyang (Huawei) responds to Dimitris (Lenovo)
Dimitris (Lenovo) responds
Huazhang (vivo) comments
Krisztian (Apple) comments.
Susana (Vodafone) has concerns with this proposal and cannot accept it
Yang (OPPO) considers it is feasible by using DNN since the DNN in TD and RSD can be decoupled
Susana (Vodafone) still disagrees with this proposal and comments
Haiyang (Huawei) seeks clarifications from Susana (Vodafone)
Haiyang (Huawei) provides r01
==== Revisions Deadline ====
Hong (Qualcomm) comments.
==== Comments Deadline ====
Revised
9.22 S2-2203125 P-CR Approval 23.700-85: New Solution on KI#6: Traffic Category with existing mechanism. Huawei, HiSilicon Rel-18 Revision of S2-2202060r01. Approved Approved
9.22 S2-2202444 P-CR Approval 23.700-85: Solution for KI#4: UE provisioned/configured with a mapping of application traffic to traffic categories. Lenovo Rel-18 r01 agreed. Revised to S2-2203126 Haiyang (Huawei) suggests to merge this paper into 2474
Dimitris (Lenovo) responds and suggests to have separate solutions
Pallab (Nokia) requests for clarification
Dimitris (Lenovo) provides r01
Pallab (Nokia) is OK with r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.22 S2-2203126 P-CR Approval 23.700-85: Solution for KI#4: UE provisioned/configured with a mapping of application traffic to traffic categories . Lenovo Rel-18 Revision of S2-2202444r01. Approved Approved
9.22 S2-2202453 P-CR Approval 23.700-85: 23.700-85: Solution for KI#4; Support standardized and operator-specific traffic categories in URSP. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203127 Huazhang (vivo) provides the comments
Pallab (Nokia) responds to Huazhang (vivo)
Dimitris (Lenovo) comments
Pallab (Nokia) responds to Dimitris (Lenovo)
Huazhang (vivo) replies to Pallab
Dimitris (Lenovo) responds
Farooq(AT&T) as a question on the solution.
Changhong (Intel) asks not to evaluate solutions at current stage if it works.
Huazhang (vivo) replies to Pallab (Nokia)
Pallab (Nokia) replies to Huazhang (vivo)
Dimitris (Lenovo) provides additional comments
Pallab (Nokia) responds Farooq(AT&T)
Farooq (AT&T) responds to Pallab(Nokia)
Huazhang(vivo) replies to Farooq (AT&T) and Pallab(Nokia), to ask a ENs: How to the UE authorize the application's request of traffic category is FFS
Huazhang (vivo) replies to Pallab(Nokia) , the ENs is needed.
Pallab(Nokia) responds to Farooq (AT&T), Huazhang(vivo)
Pallab(Nokia) responds to Huazhang(vivo)
Pallab(Nokia) responds Farooq (AT&T)
Hong (Qualcomm) comments.
Pallab (Nokia) responds to Hong (Qualcomm).
Pallab (Nokia) provides r01 with EN to capture comments from Qualcomm, AT&T, vivo.
Susana (Vodafone) comments
Farooq(AT&T) responds to Pallab(Nokia)
==== Revisions Deadline ====
Masaharu (KDDI) comments
==== Comments Deadline ====
Revised
9.22 S2-2203127 P-CR Approval 23.700-85: 23.700-85: Solution for KI#4; Support standardized and operator-specific traffic categories in URSP. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202453r01. Approved Approved
9.22 S2-2202474 P-CR Approval 23.700-85: Solution for the KI#4: Introduction of Traffic Category into URSP rules. Vivo Rel-18 r05 agreed. Revised to S2-2203128 Huazhang (vivo) provides r01 to merge the S2-2202444, S2-2202474 and S2-2202940 into S2-2202474
Haiyang (Huawei) provides concerns on the duplicate mapping
Pallab (Nokia) requests for clarification
Dimitris (Lenovo) disagrees with r01
Huazhang(vivo) replies to Pallab (Nokia)
Huazhang(vivo) replies to Haiyang (Huawei)
Haiyang (Huawei) comments
Haiyang (Huawei) further comments
Masaharu (KDDI) requests for clarification.
Pallab (Nokia) comments
Pallab (Nokia) responds to Huazhang(vivo)
Huazhang (vivo) responds to Pallab (Nokia) and Haiyang
Dimitris (Lenovo) comments
Huazhang (vivo) replies to Pallab (Nokia)
Krisztian (Apple) shares the concerns on the additional level of mapping the solution introduces, and also disagrees with r01 since the fundamental principles of the solutions are different and there's no need to merge them.
Huazhang (vivo) response to Krisztian
Huazhang(vivo) responses to Masaharu (KDDI) and provides the revision 2
Huazhang (vivo) provides r04 (please ignore the r03) and reply to Pallab (Nokia) , and reflect the suggestions from Dimitris (Lenovo)
Pallab (Nokia) responds to Huazhang(vivo) and has concerns whether the proposed solution addresses the KI or some other problem
Dimitris (Lenovo) comments. Indicates most comments are evaluation points
Huazhang(vivo) provides R05 and replies to Pallab (Nokia)
Hong (Qualcomm) comments.
Huazhang (vivo) replies to Hong (Qualcomm)
==== Revisions Deadline ====
Masaharu (KDDI) thanks to Huazhang(vivo) for clarification
==== Comments Deadline ====
Revised
9.22 S2-2203128 P-CR Approval 23.700-85: Solution for the KI#4: Introduction of Traffic Category into URSP rules. Vivo Rel-18 Revision of S2-2202474r05. Approved Approved
9.22 S2-2202701 P-CR Approval 23.700-85: KI#4, New Sol: Support standardized and operator-specific traffic categories in URSP. China Telecom Rel-18 Approved Approved
9.22 S2-2202940 P-CR Approval 23.700-85: 23.700-85: Solution for KI #4 Traffic categories based on 5G QoS characteristics. Apple Rel-18 r02 agreed. Revised to S2-2203129 Belen (Ericsson) provides comments
Pallab (Nokia) requests for clarification
Yang (OPPO) comments and asks questions
Farooq (AT&T) suggests to simplify the solution proposal.
Susana (Vodafone) requests clarification on the changes in rev01 and on the 'Needs to be managed' column in the table in 6.X.1.2.
Dimitris (Lenovo) requests clarification
Pallab (Nokia) requests clarification
Krisztian (Apple) provides r02 and addresses the comments.
Krisztian (Apple) responds to Farooq.
Yang (OPPO) asks a question
Haiyang (Huawei) has similar feeling as Yang (OPPO)
Susana (Vodafone) proposes text to be included in the clause 6.X.1.2 due to problems with editing the pCR and uploading to the server.
Krisztian (Apple) responds to Yang and Haiyang.
==== Revisions Deadline ====
Krisztian (Apple): I can add this EN in the final version.
==== Comments Deadline ====
Revised
9.22 S2-2203129 P-CR Approval 23.700-85: 23.700-85: Solution for KI #4 Traffic categories based on 5G QoS characteristics. Apple Rel-18 Revision of S2-2202940r02. Approved Approved
9.23 - - - Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) - - Docs:=83 -
9.23 - - - General - - Docs:=2 -
9.23 S2-2202121 P-CR Approval 23.700-81: Architecture assumption update for FS_eNA_Ph3. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203352 Xiaobo (vivo) comments and provide r01.
==== Revisions Deadline ====
Wang Yuan (Huawei) can live with r01.
==== Comments Deadline ====
Revised
9.23 S2-2203352 P-CR Approval 23.700-81: Architecture assumption update for FS_eNA_Ph3. Huawei, HiSilicon Rel-18 Revision of S2-2202121r01. Approved Approved
9.23 - - - New key issues - - Docs:=2 -
9.23 S2-2202883 P-CR Approval 23.700-81: KI proposal: KI for WT#3.4. Nokia, Nokia Shanghai Bell Rel-18 r04 + updates proposed by Huawei revised to S2-2203353 Wang Yuan (Huawei) provides comments.
Jungshin (Samsung): provides comments
Jungshin (Samsung): provides r02
Belen (Ericsson) provides r01
Fabio (Nokia) agrees to r02.
Xiaobo (vivo) comments and provide r03.
Wang Yuan (Huawei) provides r04.
Jungshin (Samsung): requests for clarification on changes in r04.
Malla (NTT DOCOMO) we support the KI.
Wang Yuan (Huawei) replies to Jungshin (Samsung).
==== Revisions Deadline ====
Aihua (CMCC) supports the KI, please add as a supporting company in next revision.
Jungshin (Samsung): provides comments on Yuan (Huawei) reply
Wang Yuan (Huawei) replies to Jungshin(Samsung) and propose a way forward.
Jungshin (Samsung): thanks Yuan (Huawei) and agrees to the proposed way forward
Belen (Ericsson) is okay with r02, and asks about the NOTE to be added to Huawei and Samsung
Wang Yuan (Huawei) provides r05 for CC.
Belen (Ericsson) asks Huawei on r05
Wang Yuan (Huawei) can accept r04 (which before the revision deadline) with the following two changes:
1. Restore 'and how' for first two bullets.
2. adding a new Note saying: Studying the MDAS/MDAF output is out scope of this KI.
==== Comments Deadline ====
Revised
9.23 S2-2203353 P-CR Approval 23.700-81: KI proposal: KI for WT#3.4. Nokia, Nokia Shanghai Bell, Ericsson, Samsung, China Mobile, Huawei Rel-18 Revision of S2-2202883r04 + changes. Approved Approved
9.23 - - - Key Issue #1: How to improve correctness of NWDAF analytics - - Docs:=14 -
9.23 S2-2202099 P-CR Approval 23.700-81: KI#1: New Solution for Improving Correctness of Analytics Based on the Use of Multiple ML Models. Ericsson Rel-18 r02 agreed. Revised to S2-2203354 Megha(Intel) provides comments and questions for clarification
Soohwan (ETRI) asks some questions for clarification.
Zhang (Ericsson) provides responses
Vivian (vivo) provides comments
Megha(Intel) responds to Zhang (Ericsson)
Zhang (Ericsson) provides response and r01
Malla (NTT DOCOMO) provided comments.
Vivian(vivo) provides comments and r02.
Zhang (Ericsson) is Ok with r02
==== Revisions Deadline ====
Megha(Intel) is ok with r02
==== Comments Deadline ====
Revised
9.23 S2-2203354 P-CR Approval 23.700-81: KI#1: New Solution for Improving Correctness of Analytics Based on the Use of Multiple ML Models. Ericsson Rel-18 Revision of S2-2202099r02. Approved Approved
9.23 S2-2202249 P-CR Approval 23.700-81: KI#1: New Solution - Improving the Correctness of Service Experience Predictions with Contribution Weights. InterDigital Inc. Rel-18 r04 agreed. Revised to S2-2203355 Mike (InterDigital) replies
Megha(Intel) provides comments
Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) asks for clarification.
Mike (InterDigital) replies and provides r01
Megha (Intel) provides further comments
Mike (InterDigital) replies and provides r02
Haiyang (Huawei) comments, provides r03
Mike (InterDigital) replies and provides r04
==== Revisions Deadline ====
Haiyang (Huawei) comments, can live with r04
Megha(Intel) is ok with r04
==== Comments Deadline ====
Revised
9.23 S2-2203355 P-CR Approval 23.700-81: KI#1: New Solution - Improving the Correctness of Service Experience Predictions with Contribution Weights. InterDigital Inc. Rel-18 Revision of S2-2202249r04. Approved Approved
9.23 S2-2202383 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#1, New solution for improving NWDAF correctness. Vivo Rel-18 r01 agreed. Revised to S2-2203356 Xiaoyan (CATT) provides comment.
Megha(Intel) provides comments
Soohwan (ETRI) asks a question for clarification.
Fabio (Nokia) provides comments.
Zhang (Ericsson) provides comments
Xiaobo (vivo) provides clarification.
Xiaobo (vivo) provides further clarification to Fabio(Nokia) and Soohwan(ETRI).
Xiaobo (vivo) provides further clarification to Zhang(Ericsson) and r01 trying to address the comments received so far.
Xiaoyan (CATT) provides r02.
Soohwan (ETRI) asks questions on r02.
Xiaoyan (CATT) clarifies to Soohwan (ETRI) and provides r03.
Soohwan (ETRI) asks further question on r02.
Xiaoyan (CATT) replies to Soohwan (ETRI).
==== Revisions Deadline ====
Soohwan (ETRI) prefers to go with r01.
Xiaobo (vivo) propose to go with r01 to make progress and CATT kindly bring a paper to update step 12 next meeting .
Xiaoyan (CATT) is fine with going with r01.
==== Comments Deadline ====
Revised
9.23 S2-2203356 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#1, New solution for improving NWDAF correctness. Vivo Rel-18 Revision of S2-2202383r01. Approved Approved
9.23 S2-2202438 P-CR Approval 23.700-81: Solution for KI#1: Determining ML model drift for improving analytics accuracy. Lenovo Rel-18 r03 agreed. Revised to S2-2203357 Megha(Intel) provides comments
Soohwan (ETRI) asks questions for clarification.
Zhang (Ericsson) provides comments
Fabio (Nokia) provides comments.
Dimitris (Lenovo) responds to comments provides r01
Juan Zhang (Qualcomm) provides comments
Dimitris (Lenovo) responds to Juan
Dimitris (Lenovo) provides r02
Fabio (Nokia) provides comments on r02
Dimitris (Lenovo) provides r03
==== Revisions Deadline ====
Megha(Intel) is ok with r03
==== Comments Deadline ====
Revised
9.23 S2-2203357 P-CR Approval 23.700-81: Solution for KI#1: Determining ML model drift for improving analytics accuracy. Lenovo Rel-18 Revision of S2-2202438r03. Approved Approved
9.23 S2-2202442 P-CR Approval 23.700-81: KI#1: New solution for improving NWDAF correctness. ETRI Rel-18 r02 agreed. Revised to S2-2203358 Xiaoyan (CATT) provides comment.
Zhang (Ericsson) provides comments
Fabio (Nokia) provides comments.
Dimitris (Lenovo) comments
Soohwan (ETRI) replies all the comments with r01.
Soohwan (ETRI) provides r02.
Xiaoyan (CATT) provides r03.
Soohwan (ETRI) provides comments on r03.
Soohwan (ETRI) asks to Xiaoyan (CATT) to bring a new solution with new service proposed in r02 in next meeting.
Xiaoyan (CATT) clarifies to Soohwan (ETRI) and provides r04.
LaeYoung (LGE) supports comment from Soohwan (ETRI) to ask to Xiaoyan (CATT) to bring a new solution with new service proposed in r02 in next meeting.
==== Revisions Deadline ====
Hyesung (Samsung) prefers r02.
==== Comments Deadline ====
Revised
9.23 S2-2203358 P-CR Approval 23.700-81: KI#1: New solution for improving NWDAF correctness. ETRI Rel-18 Revision of S2-2202442r02. Approved Approved
9.23 S2-2202693 P-CR Approval 23.700-81: New Solution on correctness improvement by determining ML model performance. China Mobile Rel-18 r02 agreed. Revised to S2-2203359 Megha(Intel) provides comments
Antoine (Orange) comments and proposes a change.
Fabio (Nokia) provides comments.
Zhang (Ericsson) ask for clarification
Aihua(Ericsson) replies and provides r01
Dimitris (Lenovo) includes a question on the MTLF action to retrain an ML model
Aihua (CMCC) replies to Dimitris (Lenovo).
Aihua (CMCC) replies to Fabio (Nokia) and provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.23 S2-2203359 P-CR Approval 23.700-81: New Solution on correctness improvement by determining ML model performance. China Mobile Rel-18 Revision of S2-2202693r02. Approved Approved
9.23 S2-2202886 P-CR Approval 23.700-81: Solution proposals: KI#1 How to improve correctness of NWDAF analytics. Nokia, Nokia Shanghai Bell Rel-18 r03 + EN’s proposed by Ericsson revised to S2-2203360 Xiaoyan (CATT) provides comment.
Soohwan (ETRI) asks questions for clarification.
Megha (Intel) provides some comments/ questions .
Zhang (Ericsson) provides comments
Fabio (Nokia) provides r01 and replies to comments.
Zhang (Ericsson) object r01 and the original
Malla (NTT DOCOMO) asks for clarification.
Fabio (Nokia) comments on Ericsson's objection to r01 and original
Fabio (Nokia) replies to comments from Docomo
Xiaobo (vivo) comments and is interested in sub-area concept .
Malla (NTT DOCOMO) thanks for the clarification.
Xiaobo (vivo) comments.
Fabio (Nokia) provides r03.
==== Revisions Deadline ====
Zhang (Ericsson) thanks Nokia for the revision, but r03 cannot be accepted as it is, unless the following ENs are added. And Zhang object all versions before r03
Fabio (Nokia) replies to Zhang (Ericsson) on r03
Zhang (Ericsson) can accept r03 with additional ENs:
Editor's note: It is FFS how to rate the ML model and analytics.
Editor's note: It is FFS how to prevent unfair and biased rating from different vendors, or from the competitors of the vendor of the ML model.
Editor's note: It is FFS how to trust the TRLF, which vendor should implement TRLF?
Fabio (Nokia) provides r05 implementing the ENs agreed with Ericsson.
Fabio (Nokia) warns that previous message was sent to wrong email thread.
Fabio provides r04 implementing the changes and EN agreed with Ericsson.
Zhang (Ericsson) is OK with r04
==== Comments Deadline ====
Revised
9.23 S2-2203360 P-CR Approval 23.700-81: Solution proposal: KI#1 How to improve correctness of NWDAF analytics. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202886r03 + changes. Approved Approved
9.23 - - - Key Issue #2: NWDAF-assisted application detection - - Docs:=5 -
9.23 S2-2202123 P-CR Approval 23.700-81: New Solution for KI#2: NWDAF-assisted application detection. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2203361 Belen (Ericsson) provides comments
Wang Yuan (Huawei) replies to Belen (Ericsson) and provide r01.
Belen (Ericsson) objects to r01 and initial version
Wang Yuan (Huawei) replies to Belen (Ericsson) and provide r02.
Yifan (China Telecom) comments.
Jungshin (Samsung): request clarification on how to use Service Type
Wang Yuan (Huawei) replies to Jungshin (Samsung) and Yifan (China Telecom) and provide r03.
Thomas Nokia provides r04.
Jungshin (Samsung): Provides r05
==== Revisions Deadline ====
Wang Yuan (Huawei) is OK with r05.
==== Comments Deadline ====
Revised
9.23 S2-2203361 P-CR Approval 23.700-81: New Solution for KI#2: NWDAF-assisted application detection. Huawei, HiSilicon Rel-18 Revision of S2-2202123r05. Approved Approved
9.23 S2-2202308 P-CR Approval 23.700-81: New Solution on NWDAF-assisted application detection. Samsung Rel-18 Merged into S2-2203362 Wang Yuan (Huawei) provides comments.
Belen (Ericsson) proposes to merge this solution and the one in S2-2202638.
Belen (Ericsson) provides comments.
Jungshin (Samsung): provides clarification in response to Belen (Ericsson) and r01
Jungshin (Samsung) provides clarification
Xiaobo (vivo) comments .
==== Revisions Deadline ====
Jungshin (Samsung): agrees to merge the pCR to S2-2202638
==== Comments Deadline ====
Merged
9.23 S2-2202638 P-CR Approval 23.700-81: New Solution on NWDAF-assisted application detection. China Mobile Rel-18 r04 agreed. Revised to S2-2203362, merging S2-2202308 Belen (Ericsson) provides comments
Belen (Ericsson) proposes to merge this solution and the one in S2-2202308.
Aihua(Ericsson) replies to Belen (Ericsson) and provides r01, and asks for merging S2-2202308 into this pCR.
Aihua(CMCC) replies to Belen (Ericsson) and provides r01, and asks for merging S2-2202308 into this pCR.
Belen (Ericsson) provides r02
Jungshin (Samsung): provides r02 to merge with S2-2202308
Jungshin (Samsung): corrected that Samsung provided r03, not r02
Thomas (Nokia): providers r04
==== Revisions Deadline ====
Jungshin (Samsung): We are ok with r03 and r04.
Belen (Ericsson) is okay with r04, can accept r03,r02. Objects to initial version and r01
==== Comments Deadline ====
Revised
9.23 S2-2203362 P-CR Approval 23.700-81: New Solution on NWDAF-assisted application detection. China Mobile, Samsung Rel-18 Revision of S2-2202638r04, merging S2-2202308. Approved Approved
9.23 - - - Key Issue #3: Data and analytics exchange in roaming case - - Docs:=3 -
9.23 S2-2202100 P-CR Approval 23.700-81: KI#3: New Solution for Data and Analytics Exchange in Roaming Case. Ericsson Rel-18 r04 agreed. Revised to S2-2203363 Wang Yuan (Huawei) has concerns on this contributions.
Zhang (Ericsson) provides response
Vivian(vivo) provides comments
Malla (NTT DOCOMO) provides comments
Juan Zhang (Qualcomm) provides comments
Jungshin (Samsung): provides comments
Thomas (Nokia) provides r01
Jinguo(ZTE) comments
Vivian(vivo) provides comments and r02.
Zhang (Ericsson) provides comments and r03
Jungshin (Samsung): provides r04
==== Revisions Deadline ====
Wang Yuan (Huawei) cannot accept all revisions but provides r05 for CC#3.
Xiaobo (vivo) tend to support to agree r04 or any revision before revision deadline to make progress.
Zhang (Ericsson) is OK with r05 and r04. We can agree on r05 and no need to go to CC
Wang Yuan (Huawei) can live with r04 (which is the latest revision before the deadline) as it is.
==== Comments Deadline ====
Revised
9.23 S2-2203363 P-CR Approval 23.700-81: KI#3: New Solution for Data and Analytics Exchange in Roaming Case. Ericsson, Samsung Rel-18 Revision of S2-2202100r04. Approved Approved
9.23 S2-2202314 P-CR Approval 23.700-81: Solution for KI#3: PDU session management in roaming scenarios using network analytics. CATT Rel-18 Approved Approved
9.23 - - - Key Issue #4: How to Enhance Data collection and Storage - - Docs:=2 -
9.23 S2-2202873 P-CR Approval 23.700-81: Solution proposal: KI#4: Data Collection and Storage Enhancements. Nokia, Nokia Shanghai Bell Rel-18 r04 + EN’s proposed by Ericsson revised to S2-2203364 Xiaoyan (CATT) provides comment.
Vivian(vivo) provides comment.
Antoine (Orange): a definition of Storage Approach is missing.
Fabio (Nokia) provides r01 and replies to comments.
Zhang (Ericsson) object r01 and the original version
Juan Zhang (Qualcomm) shares the same concern about the merge.
Fabio (Nokia) replies to Ericsson's and Qualcomm's comments.
Fabio (Nokia) provides comments and r03
Zhang (Ericsson) object r02 and r03
Fabio (Nokia) provides r04.
==== Revisions Deadline ====
Zhang (Ericsson) thanks for the revision, but r04 cannot be accepted as it is now, unless the following ENs are added. Zhang object all versions before r04
Zhang (Ericsson) can accept r04 with additional ENs:
Editor's note: it is FFS how to do data collection transfer for the case of group UEs or any UE
Editor's note: it is FFS whether and how to transfer the data subscription between DCCF and the data sources.
Fabio (Nokia) is OK with the changes proposed by Ericsson on r04.
Fabio (Nokia) provides r05 implementing the ENs agreed with Ericsson.
Zhang (Ericsson) is OK with r05
==== Comments Deadline ====
Revised
9.23 S2-2203364 P-CR Approval 23.700-81: Solution proposal: KI#4: Data Collection and Storage Enhancements. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202873r04 + changes. Approved Approved
9.23 - - - Key Issue #5: Enhance trained ML Model sharing - - Docs:=6 -
9.23 S2-2202233 P-CR Approval 23.700-81: KI5: Solution - NWDAF MTLF and NWDAF AnLF interoperability support for registration and discovery in 5GC. Intel Rel-18 r01 agreed. Revised to S2-2203365 Xiaoyan (CATT) asks a question for clarification.
Wang Yuan (Huawei) has concerns for the contribution.
Zhang (Ericsson) provides comments
Megha (Intel) provides clarification and r01.
Wang Yuan (Huawei) provides further comment on r01 and also notice that S2-2202385 and S2-2202233 are proposing similar ideas, can these two contributions be merged?
Malla (NTT DOCOMO) asks for clarification.
Megha (Intel) responds to Malla (NTT DOCOMO) and provides r02.
Megha (Intel) responds to Wang Yuan (Huawei).
==== Revisions Deadline ====
Wang Yuan (Huawei) objects to r02 as it is, can live with r01 or re-phasing the EN in r02.
Megha (Intel) is ok with r01.
==== Comments Deadline ====
Revised
9.23 S2-2203365 P-CR Approval 23.700-81: KI5: Solution - NWDAF MTLF and NWDAF AnLF interoperability support for registration and discovery in 5GC. Intel Rel-18 Revision of S2-2202233r01. Approved Approved
9.23 S2-2202385 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#5, New solution for model sharing. Vivo Rel-18 r05 agreed. Revised to S2-2203366 Wang Yuan (Huawei) has concerns for this contribution.
Wang Yuan (Huawei) provide revision to address the concerns from Yuan(Huawei).
Xiaobo (vivo) provides clarification and corrects the TYPO.
Wang Yuan (Huawei) replies to Xiaobo (vivo) and provides further comments. Also notice that S2-2202385 and S2-2202233 are proposing similar ideas, can these two contributions be merged?
Xiaobo (vivo) replies to Zhang(Ericsson) and provide r03.
Xiaobo (vivo) replies to Malla(NTT DoCoMo) and provide r03.
Zhang (Ericsson) propose to add EN about model metadata
Malla (NTT DOCOMO) asks for clarification.
Xiaobo (vivo) provide r02 to the comments from Yuan(Huawei) and prefer to keep S2-2202385/S2-2202233 separate due to some difference but is happy to hold a pen to merge if majority insist on a merge.
Malla (NTT DOCOMO) provide r04.
Zhang (Ericsson) provides comments
Xiaobo (vivo) is ok with Malla(NTT DoCoMo)'s proposal and provides r05 to address the comment from Zhang(Ericsson).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.23 S2-2203366 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#5, New solution for model sharing. Vivo Rel-18 Revision of S2-2202385r05. Approved Approved
9.23 S2-2202468 P-CR Approval 23.700-81: Solution for ML model sharing with different service provider's AnLF. NTT DOCOMO Rel-18 r02 agreed. Revised to S2-2203367 Megha(Intel) provides comments
Vivian (vivo) provides comments.
Xiaoyan (CATT) asks for clarification.
Zhang (Ericsson) ask for clarification
Fabio (Nokia) provides comments.
Malla (NTT DOCOMO) replies to Xiaoyan (CATT).
Malla (NTT DOCOMO) provided response.
Megha (Intel) provides more comments.
Malla (NTT DOCOMO) replied to Intel and Vivo.
Malla (NTT DOCOMO) replies to Megha (Intel).
Megha (Intel) responds to Malla (NTT DOCOMO)
Malla (NTT DOCOMO) replied to Megha (Intel) and provided r01
Vivian(vivo) provides comments and corresponding r02
Malla (NTT DOCOMO) asks question to Vivian(vivo).
Vivian(vivo) replies to Malla (NTT DOCOMO)'s question.
==== Revisions Deadline ====
Megha (Intel) is ok with r02.
==== Comments Deadline ====
Revised
9.23 S2-2203367 P-CR Approval 23.700-81: Solution for ML model sharing with different service provider's AnLF. NTT DOCOMO Rel-18 Revision of S2-2202468r02. Approved Approved
9.23 - - - Key issue #6: NWDAF-assisted URSP - - Docs:=5 -
9.23 S2-2201992 P-CR Approval 23.700-81: New solution for NWDAF assisted URSP determination. China Telecom, Ericsson Rel-18 r02 + EN proposed by Ericsson revised to S2-2203368 Rainer (Nokia) proposes to note the LS.
Mehrdad (Samsung) provides r01 and co-signs the PCR.
Yang (OPPO) comments this solution missed an important assumption
Jiahui (China Telecom) replys to OPPO.
Wang Yuan (Huawei) asks for clarification.
Jiahui (China Telecom) replys Samsung and Huawei.
==== Revisions Deadline ====
Belen (Ericsson) asks Samsung on r01 and same text in r02
Mehrdad (Samsung) replies to Ericsson
Belen (Ericsson) proposes to add extend the EN on top of r02
Belen (Ericsson) proposes to add extend the EN on top of r02.
Belen (Ericsson) corrects the proposed EN.
Mehrdad (Samsung) objects to the original version of this PCR but we can live with r02 + the revised Editor's note suggested by Ericsson. We suggest to add this PCR change for CC#2 or CC#3 for final approval.
Jiahui (China Telecom) is fine with Samsung's proposal to go with r02 + the revised Editor's note suggested by Ericsson.
==== Comments Deadline ====
Revised
9.23 S2-2203368 P-CR Approval 23.700-81: New solution for NWDAF assisted URSP determination. China Telecom, Ericsson, Samsung Rel-18 Revision of S2-2201992r02 + changes. Approved Approved
9.23 S2-2202315 P-CR Approval 23.700-81: Solution for KI#3#6: NSSP in roaming scenarios using network analytics. CATT Rel-18 r02 agreed. Revised to S2-2203369 Thomas (Nokia) provides r01
Mehrdad (Samsung) provides comments
Xiaoyan (CATT) replies to Mehrdad (Samsung).
Jungshin (Samsung) provides further comments
Xiaoyan (CATT) replies to Jungshin (Samsung).
Xiaoyan clarifies to Jungshin (Samsung) and provides r02.
==== Revisions Deadline ====
Jungshin (Samsung): can live with r02 for this meeting, and propose to resolve the issue in the next meeting.
==== Comments Deadline ====
Revised
9.23 S2-2203369 P-CR Approval 23.700-81: Solution for KI#3#6: NSSP in roaming scenarios using network analytics. CATT Rel-18 Revision of S2-2202315r02. Approved Approved
9.23 S2-2202559 P-CR Approval 23.700-81: Solution for NWDAF assisted URSP enforcement analytics. OPPO Rel-18 Noted Dimitris (Lenovo) includes a question for clarification
Mehrdad (Samsung) provides comments
Yang (OPPO) replies to Mehrdad
Yang (OPPO) replies to Dimitris
Antoine (Orange) comments.
Thomas(Nokia) comments
Huazhang (vivo) replies to Yang(OPPO), and in order to save time and response to other company's view, prefer a ENs:
Editor's note: The details of URSP rules enforcement data collection and usage of this information should be updated.
Juan Zhang (Qualcomm) provides comments
Wang Yuan (Huawei) asks for clarification.
Wang Yuan (Huawei) withdraws previous comments as it is not for this doc. .
Yang (OPPO) replies and provides r01
==== Revisions Deadline ====
Antoine (Orange) objects to r00 and r01.
==== Comments Deadline ====
Noted
9.23 - - - Key Issue #7: Enhancements on QoS Sustainability analytics - - Docs:=9 -
9.23 S2-2201919 LS In Action LS from 5GAA: LS on Enhancements on QoS Sustainability analytics in the context of the Study on Enablers for Network Automation for 5G - phase 3 (FS_eNA_Ph3) 5GAA (5GAA_S-210186) Revision of Postponed S2-2200016 from S2#149E. Response drafted in S2-2202122. Final response in S2-2203370 Replied to
9.23 S2-2202122 LS OUT Approval [DRAFT] Reply LS on Enhancements on QoS Sustainability analytics Huawei, HiSilicon Rel-18 Response to S2-2201919. r01 agreed. Revised to S2-2203370 Mehrdad (Samsung) provides comments
LaeYoung (LGE) replies to Mehrdad (Samsung).
Wang Yuan (Huawei) replies to Mehrdad (Samsung) and LaeYoung (LGE), and provides r01.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r01.
Wang Yuan (Huawei) replies to LaeYoung (LGE).
Mehrdad (Samsung) prefers r01 and is OK with r01.
==== Comments Deadline ====
Revised
9.23 S2-2203370 LS OUT Approval Reply LS on Enhancements on QoS Sustainability analytics in the context of the Study on Enablers for Network Automation for 5G - phase 3 (FS_eNA_Ph3) SA WG2 Rel-18 Revision of S2-2202122r01. Approved Approved
9.23 S2-2202338 LS OUT Approval [DRAFT] LS on Location Granularity of RAN inputs to OAM and NWDAF Huawei, HiSilicon Rel-18 Postponed Mehrdad (Samsung) provides comments
Juan Zhang (Qualcomm) provides comments
Thomas (Nokia) has concerns that LS is premature
Wang Yuan (Huawei) can accept the suggestions to postpone this LS OUT until the solution is stable.
==== Revisions Deadline ====
==== Comments Deadline ====
Postponed
9.23 S2-2202025 P-CR Approval 23.700-81: KI#7, New Sol: Enhanced QoS Sustainability Analytics. Tencent, Tencent Cloud Rel-18 r01 agreed. Revised to S2-2203371 Mehrdad (Samsung) provides comments
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.23 S2-2203371 P-CR Approval 23.700-81: KI#7, New Sol: Enhanced QoS Sustainability Analytics. Tencent, Tencent Cloud Rel-18 Revision of S2-2202025r01. Approved Approved
9.23 S2-2202125 P-CR Approval 23.700-81: Solution on KI#7: Enhanced QoS Sustainability Analytics. Huawei, HiSilicon Rel-18 r05 + EN proposed by Huawei revised to S2-2203372 Mehrdad (Samsung) provides comments
LaeYoung (LGE) provides comment.
Jihoon (ETRI) asks for clarification.
Wang Yuan (Huawei) replies to Mehrdad (Samsung), LaeYoung (LGE) and Jihoon (ETRI) , and provides r01.
Juan Zhang (Qualcomm) provides comments.
Belen (Ericsson) provides comments.
Thomas (Nokia) has concerns that LS is premature
Wang Yuan (Huawei) replies to Juan Zhang (Qualcomm), Belen (Ericsson) and Thomas (Nokia), and provides r02.
LaeYoung (LGE) comments.
Aihua(CMCC) provides r03.
Thomas (Nokia) apologizes that his comment was in the wrong email thread
Wang Yuan (Huawei) replies to LaeYoung (LGE), Aihua (CMCC) and Juan (Qualcomm), and provides r04.
LaeYoung (LGE) further comments.
Wang Yuan (Huawei) replies to LaeYoung (LGE), and provides r05.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r05.
Belen (Ericsson) objects to this contribution all revisions and initial version.
Belen (Ericsson) can accept r05 with an EN to state that it FFS how the SMF/PCF knows whether PER, PDB or GFBR cannot be fulfilled.
Juan Zhang (Qualcomm) is fine with r05.
Wang Yuan (Huawei) agrees Belen (Ericsson)'s suggestion, and provides r06 for CC#3/CC#4.
Wang Yuan (Huawei) suggests to agree r05 with adding the following EN:
Editor's note: It is FFS how the SMF/PCF knows whether PER, PDB or GFBR cannot be fulfilled from the QNC/AQP='GFBR can no longer be guaranteed' event.
==== Comments Deadline ====
Revised
9.23 S2-2203372 P-CR Approval 23.700-81: Solution on KI#7: Enhanced QoS Sustainability Analytics. Huawei, HiSilicon Rel-18 Revision of S2-2202125r05 + changes. Approved Approved
9.23 S2-2202983 P-CR Approval 23.700-81: KI#7, New Sol: QoS Sustainability analytics enhanced with additional input data for UL/DL throughput KPI. Orange Rel-18 Approved Approved
9.23 - - - Key Issue #8: Supporting Federated Learning in 5GC - - Docs:=8 -
9.23 S2-2202041 P-CR Approval 23.700-81: Solution for KI#8 to support Federated Learning between NWDAFs. Qualcomm Incorporated Rel-18 r05 agreed. Revised to S2-2203373 Megha(Intel) provides r01 and comments
Malla (NTT DOCOMO) provided comments
Zhang (Ericsson) provides comments
Hyesung (Samsung) provides comments
Vivian(vivo) provides comments
Juan Zhang (Qualcomm) replies to Zhang.
Megha (Intel) replies to Juan (Qualcomm)
Juan Zhang (Qualcomm) replies to Malla.
Juan Zhang (Qualcomm) relies to Intel
Juan Zhang (Qualcomm) replies to Hyesung.
Juan Zhang (Qualcomm) replies to vivo
Juan Zhang (Qualcomm) provides r02.
Soohwan (ETRI) asks questions for clarification.
Soohwan (ETRI) asks one more question.
Wang Yuan (Huawei) provides comments on r02.
Juan Zhang (Qualcomm) replies to HW.
Juan Zhang (Qualcomm) replies to Soohwan
Vivian(vivo) provides comment and r03.
Wang Yuan (Huawei) replies to Juan (Qualcomm).
Juan Zhang (Qualcomm) provides r04.
Juan Zhang (Qualcomm) provides r05.
==== Revisions Deadline ====
Megha(Intel) is ok with r05
Vivian (vivo) is ok with r05
Juan Zhang (Qualcomm) replies to Vivian (vivo)
Soohwan (ETRI) okay with r05.
Vivian (vivo) replies to Juan Zhang (Qualcomm)
Juan Zhang (Qualcomm) replies to Vivian.
Vivian(vivo) replies to Juan Zhang (Qualcomm) and thanks for explanation.
==== Comments Deadline ====
Revised
9.23 S2-2203373 P-CR Approval 23.700-81: Solution for KI#8 to support Federated Learning between NWDAFs . Qualcomm Incorporated, Intel Rel-18 Revision of S2-2202041r05. Approved Approved
9.23 S2-2202318 P-CR Approval 23.700-81: Solution for KI #8: Federated Learning Group creation. Samsung Rel-18 r03 agreed. Revised to S2-2203374 Megha(Intel) provides r01 , comments and questions for clarification
Xiaoyan (CATT) provides comments.
Soohwan (ETRI) asks questions for clarification.
Zhang (Ericsson) provides comments
Vivian (vivo) provides comments
Juan Zhang (Qualcomm) provides comments
Hyesung (Samsung) replies and provides r02
Soohwan (ETRI) provides comments.
Hyesung (Samsung) replies to Soohwan and provides r03.
==== Revisions Deadline ====
Xiaoyan (CATT) is fine with r03 and would like to co-sign.
Soohwan (ETRI) okay with r03.
Juan Zhang (Qualcomm) is okay with r03.
==== Comments Deadline ====
Revised
9.23 S2-2203374 P-CR Approval 23.700-81: Solution for KI #8: Federated Learning Group creation. Samsung, CATT Rel-18 Revision of S2-2202318r03. Approved Approved
9.23 S2-2202427 P-CR Approval 23.700-81: Solution for KI#8: Support of federated learning for model training. Lenovo Rel-18 r05 agreed. Revised to S2-2203375 Megha(Intel) provides r01 and comments
Soohwan (ETRI) asks questions for clarification.
Xiaoyan (CATT) asks for clarification.
Hyesung (Samsung) provides comments.
Dimitris (Lenovo) responds to questions raised provides r02 on top of r01
Malla (NTT DOCOMO) provided comments.
Dimitris (Lenovo) responds to Malla (NTT DOCOMO)
Zhang (Ericsson) provides comments for r02
Dimitris (Lenovo) provides r03
Soohwan (ETRI) asks further clarifications.
Dimitris (Lenovo) provides r05 (ignore r04)
==== Revisions Deadline ====
Megha(Intel) is ok with r05
==== Comments Deadline ====
Revised
9.23 S2-2203375 P-CR Approval 23.700-81: Solution for KI#8: Support of federated learning for model training. Lenovo, Intel Rel-18 Revision of S2-2202427r05. Approved Approved
9.23 S2-2202633 P-CR Approval 23.700-81: New Solution on Horizontal Federated Learning among Multiple NWDAFs Instances. China Mobile Rel-18 r01 agreed. Revised to S2-2203376 Megha(Intel) provides comments and questions for clarification
Antoine (Orange): Why is FL different for the case of abnormal behaviour?
Soohwan (ETRI) asks questions for clarification.
Zhang (Ericsson) ask for clarification
Aihua(CMCC) replies to Antoine (Orange).
Aihua(CMCC) replies to the comments and provides r01
==== Revisions Deadline ====
Megha(Intel) is ok with r01
==== Comments Deadline ====
Revised
9.23 S2-2203376 P-CR Approval 23.700-81: New Solution on Horizontal Federated Learning among Multiple NWDAFs Instances. China Mobile Rel-18 Revision of S2-2202633r01. Approved Approved
9.23 - - - Key Issue #9: Enhancement of NWDAF with finer granularity of location information - - Docs:=6 -
9.23 S2-2202388 P-CR Approval 23.700-81: KI#9, New Sol: Outdoors Advertisement use case with finer granularity location information. Vivo Rel-18 r01 agreed. Revised to S2-2203377 Xiaoyan (CATT) provides comment.
Hank (vivo) responses to Xiaoyan (CATT).
Zhang (Ericsson) provides comments
David (Samsung) provides comments
Malla (NTT DOCOMO) provides comments
Juan Zhang (Qualcomm) provides comments.
Hank (vivo) provides r01.
Hank (vivo) responses to all.
Dimitris (Lenovo) comments
Hank (vivo) replies to Dimitris (Lenovo).
Hank (vivo) replies to Juan Zhang (Qualcomm).
==== Revisions Deadline ====
Hank (vivo) proposes to agree r01.
Hank (vivo) has a further clarification on r01 to Dimitris (Lenovo) and proposes to agree on r01.
==== Comments Deadline ====
Revised
9.23 S2-2203377 P-CR Approval 23.700-81: KI#9, New Sol: Outdoors Advertisement use case with finer granularity location information. Vivo Rel-18 Revision of S2-2202388r01. Approved Approved
9.23 S2-2202694 P-CR Approval 23.700-81: TR 23.700-81: KI#9 - Solution for finer granularity of location information. TOYOTA MOTOR CORPORATION Rel-18 r04 agreed. Revised to S2-2203378 Hank (vivo) asks for clarifications.
Wang Yuan (Huawei) provides comments.
Xiao (Toyota) replies to Hank.
Xiao (Toyota) replies to Yuan (Huawei).
Xiao (Toyota) thank Hank (vivo) for further clarification.
Hank (vivo) replies to Xiao (Toyota) and feels fine with the proposal.
Kenichi (KDDI) provides r01.
Xiao (Toyota) is fine with the revision from Kenichi (KDDI).
Dimitris (Lenovo) supports the proposal and requests to cosign
Wang Yuan (Huawei) replies to Xiao (Toyota), provides r02 and cosigns this pCR.
Hank (vivo) provides r03 and co-signs this pCR.
Kenichi (KDDI) provides r04 for adding Lenovo as co-signer.
Xiao (Toyota) is fine with r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.23 S2-2203378 P-CR Approval 23.700-81: TR 23.700-81: KI#9 - Solution for finer granularity of location information. TOYOTA MOTOR CORPORATION, KDDI, Lenovo, Huawei, vivo, Rel-18 Revision of S2-2202694r04. Approved Approved
9.23 S2-2202179 P-CR Approval 23.700-81: KI#9: New solution on relative proximity analytics. Samsung Rel-18 r04 agreed. Revised to S2-2203379 Zhang (Ericsson) ask for clarification
David (Samsung) replies to Ericsson and provides r01
Hank (vivo) asks for clarifications.
Juan Zhang (Qualcomm) provides comments
Zhang (Ericsson) provides comments
Wang Yuan (Huawei) provides comments.
David (Samsung) provides r02 and replies to comments
Xiaobo (vivo) comments.
Juan Zhang (Qualcomm) provides further comments.
David (Samsung) provides r03 and comments.
Juan Zhang (Qualcomm) provides comment.
David (Samsung) replies to Qualcomm.
Juan Zhang (Qualcomm) replies to David
David (Samsung) provides r04 with the EN requested by Juan (Qualcomm)
==== Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r04.
==== Comments Deadline ====
Revised
9.23 S2-2203379 P-CR Approval 23.700-81: KI#9: New solution on relative proximity analytics. Samsung Rel-18 Revision of S2-2202179r04. Approved Approved
9.23 - - - Documents exceeding TU Budget - - Docs:=21 -
9.23 S2-2202087 P-CR Approval 23.700-81: New Key Issue on Study Whether and How Interactions between NWDAF can Leverage MDAS/MDAF Functionality for Analytics. Ericsson Rel-18 Not Handled Not Handled
9.23 S2-2202640 P-CR Approval 23.700-81: New KI: Interactions between NWDAF and MDAF for data collection and analytics. China Mobile Rel-18 Not Handled Not Handled
9.23 S2-2202062 P-CR Approval 23.700-81: New Solution on KI#1: Detect and Improve correctness of NWDAF analytics. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.23 S2-2202313 P-CR Approval 23.700-81: Solution for KI#1: Enhanced ML model provisioning. CATT Rel-18 Not Handled Not Handled
9.23 S2-2202124 P-CR Approval 23.700-81: New Solution for KI#3: Data collection and analytics by H-NWDAF in roaming case. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.23 S2-2202316 P-CR Approval 23.700-81: Solution for KI#3: Architecture for network analytics in roaming scenarios. CATT Rel-18 Not Handled Not Handled
9.23 S2-2202384 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#3, New solution for data or analytics exchange in roaming scenario. Vivo Rel-18 Not Handled Not Handled
9.23 S2-2202665 P-CR Approval 23.700-81: FS_eNA_Ph3 New Solution to KI#3. ZTE Rel-18 Not Handled Laurent (Nokia): 'objects' to the paper (just for the sake that we discuss just in the thread of 2677 HW CR)
Jinguo(ZTE) points that Laurent(Nokia) objection is to 2655, not to 2665.
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.23 S2-2202683 P-CR Approval 23.700-81: New Solution on ML Model storage in ADRF. China Mobile Rel-18 Not Handled Not Handled
9.23 S2-2202690 P-CR Approval 23.700-81: New Solution on DCCF relocation. China Mobile Rel-18 Not Handled Not Handled
9.23 S2-2202387 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#6, New solution for PCF re-evaluates the URSP rules according to NWDAF's analytics. Vivo Rel-18 Not Handled Not Handled
9.23 S2-2202646 P-CR Approval 23.700-81: New Solution on enhancements on QoS Sustainability analytics. China Mobile Rel-18 Not Handled Jihoon (ETRI) provides comments.
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.23 S2-2202386 P-CR Approval 23.700-81: FS_eNA_Ph3, KI#8, New solution for Federal ML. Vivo Rel-18 Not Handled Not Handled
9.23 S2-2202042 P-CR Approval 23.700-81: Solution for KI#9: Support to collect finer granularity of Location Information to NWDAF. Qualcomm Incorporated Rel-18 Not Handled Not Handled
9.23 S2-2202098 P-CR Approval 23.700-81: KI#1: New Solution for Detection of ML Model Degradation. Ericsson Rel-18 Not Handled Not Handled
9.23 S2-2202722 P-CR Approval 23.700-81: Solution for KI#9: Supporting UE mobility analytics with finer granularity than TA/cell. Lenovo Rel-18 Not Handled Not Handled
9.23 S2-2202806 P-CR Approval 23.700-81: KI #3 solution proposal. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not Handled
9.23 S2-2202310 P-CR Approval 23.700-81: New Solution on data and analytics exchange for roaming UEs. Samsung Rel-18 Not Handled Not Handled
9.23 S2-2202616 P-CR Approval 23.700-81: KI#6, New Sol: Support NWDAF-assisted URSP. Samsung Rel-18 Not Handled Not Handled
9.23 S2-2202232 P-CR Approval 23.700-81: KI 4: Solution -Trained ML models storage and retrieval from ADRF. Intel Rel-18 Not Handled Not Handled
9.23 S2-2202470 P-CR Approval 23.700-81: Solution on finer granular location information based on LCS input data. NTT DOCOMO Rel-18 Not Handled Not Handled
9.24 - - - Study on satellite access Phase 2 (FS_5GSAT_Ph2) - - Docs:=25 -
9.24 S2-2202229 P-CR Approval 23.700-28: Solution for predictive Power Saving Mode. Thales r03 agreed. Revised to S2-2203380 Haris(Qualcomm) provides comments
Steve (Huawei) asks some questions.
Stefan (Ericsson) asks questions
Hannu (Nokia) asks questions and comments on GPRS Timer 3.
Jean Yves (Thales) responds to questions and provides r01
Haris(Qualcomm) provides r02
Jean Yves (Thales) answers to Haris and provides r03
Haris(Qualcomm) is ok with r03 and comments
==== Revisions Deadline ====
Steve (Huawei) is ok with r03
==== Comments Deadline ====
Revised
9.24 S2-2203380 P-CR Approval 23.700-28: Solution for predictive Power Saving Mode . Thales, Eutelsat - Revision of S2-2202229r03. Approved Approved
9.24 S2-2201982 P-CR Approval 23.700-28: New solution for KI#2 on Power Saving mechanisms in case of discontinuous coverage. Ericsson Rel-18 r01 agreed. Revised to S2-2203381 Haris(Qualcomm) provides comments
Steve (Huawei) comments
Stefan (Ericsson) provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.24 S2-2203381 P-CR Approval 23.700-28: New solution for KI#2 on Power Saving mechanisms in case of discontinuous coverage. Ericsson Rel-18 Revision of S2-2201982r01. Approved Approved
9.24 S2-2202339 P-CR Approval 23.700-28: New key issues on Mobility Management enhancement with discontinuous satellite coverage. Xiaomi Rel-18 Noted Haris(Qualcomm) provides comments
Steve (Huawei) comments
Stefan (Ericsson) provides comments
Hannu (Nokia) comments and suggests way forward.
Lalith (Samsung) comments.
Yuxin (Xiaomi) replies to Lalith (Samsung)
Yuxin (Xiaomi) replies to Stefan (Ericsson)
Yuxin (Xiaomi) replies to Haris(Qualcomm)
Yuxin (Xiaomi) provides r01 based on the comments from all of you
Yuxin(Xiaomi) replies to Steve (Huawei)
Haris(Qualcomm) comments that all revisions remain unacceptable
Yuxin(Xiaomi) replies and provides r04
Hannu (Nokia) comments on service continuity which seems odd. Not convinced that this PCR is needed?
==== Revisions Deadline ====
Yuxin (Xiaomi) replies to Hannu and Haris
Stefan (Ericsson) agrees with Hannu and is also not convinced this update is needed
==== Comments Deadline ====
Noted
9.24 S2-2202340 P-CR Approval 23.700-28: Solution on Mobility Management enhancement with discontinuous satellite coverage. Xiaomi Rel-18 Noted Haris(Qualcomm) provides comments
Steve (Huawei) comments
Hannu (Nokia) comments.
Yuxin (Xiaomi) comments
Yuxin(Xiaomi) replies to Haris (Qualcomm)
Jean Yves (Thales) comments and ask question to Haris
Yuxin (Xiaomi) comments to clarification
Yuxin (Xiaomi) provides r01.
Yuxin (Xiaomi) provides r02.
Yuxin (Xiaomi) provides r03.
Haris(Qualcomm) comments on r02
Stefan (Ericsson) provides comments
Yuxin (Xiaomi) replies and provides r04
==== Revisions Deadline ====
Haris(Qualcomm) comments that r04 continues to be based on incorrect assumptions
==== Comments Deadline ====
Noted
9.24 S2-2202381 P-CR Approval 23.700-28: Solution for Mobility Management enhancement based on coverage information and UE location. Vivo Rel-18 r03 agreed. Revised to S2-2203382 Haris(Qualcomm) provides comments
Stefan (Ericsson) provides comments
Hannu (Nokia) shares the concern against specifying paging strategies that was indicated by Stefan.
Lufeng(vivo) feedback to Stefan (Ericsson) and provides rev02.
Lufeng(vivo) feedback to Haris(Qualcomm) and provides rev01.
Jean Yves (Thales) comments.
Lufeng(vivo) feedback to Hannu (Nokia).
Lufeng(vivo) feedback to Jean Yves (Thales) and provide revision r03.
Steve (Huawei) comments
Yingying(CATT) provides comments.
==== Revisions Deadline ====
Lufeng(vivo) respond to Yingying(CATT).
Lufeng(vivo) respond to Steve (Huawei).
Yingying(CATT) is OK with r03.
==== Comments Deadline ====
Revised
9.24 S2-2203382 P-CR Approval 23.700-28: Solution for Mobility Management enhancement based on coverage information and UE location . Vivo Rel-18 Revision of S2-2202381r03. Approved Approved
9.24 S2-2202382 P-CR Approval 23.700-28: Solution for KI#2 Power Saving based on updating parameters before releasing signalling connection. Vivo Rel-18 r03 agreed. Revised to S2-2203383 Steve (Huawei)
Stefan (Ericsson) provides questions
Lufeng(vivo) feedback to Stefan (Ericsson) and provides rev01.
Lufeng(vivo) feedback to Steve (Huawei).
Stephen (Qualcomm) comments
Jean Yves (Thales) comments
Lufeng(vivo) feedback to Jean Yves (Thales) and provide revision r02;
Lufeng(vivo) feedback to Stephen (Qualcomm).
Jean Yves (Thales) responds to Lufeng and ask question
Lufeng(vivo) responds to Jean Yves (Thales) and provide rev03.
==== Revisions Deadline ====
Stephen (Qualcomm) points out defects but is okay to agree the P-CR
==== Comments Deadline ====
Revised
9.24 S2-2203383 P-CR Approval 23.700-28: Solution for KI#2 Power Saving based on updating parameters before releasing signalling connection . Vivo Rel-18 Revision of S2-2202382r03. Approved Approved
9.24 S2-2202422 P-CR Approval 23.700-28: KI#2 Update for CN awareness of coverage information. Huawei, HiSilicon Rel-18 Noted DongYeon (Samsung) asks questions.
Steve (Huawei) comments
Stefan (Ericsson) has concerns with this KI update since it is solution oriented
Jean Yves (Thales) comments
Stefan (Ericsson) replies to Jean Yves
Jean Yves (Thales) replies to Stefan
==== Revisions Deadline ====
Stefan (Ericsson) objects to the pCR
==== Comments Deadline ====
Noted
9.24 S2-2202423 P-CR Approval 23.700-28: Solution#1 Update for Power Saving based on AMF awareness of coverage information. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2203384 DongYeon (Samsung) asks question for clarification.
Steve (Huawei) replies to the question
Stefan (Ericsson) provides questions and comments
Steve (Huawei) replies and provides r01.
Stefan (Ericsson) provides r02
Steve (Huawei) thanks for the update, r02 is ok for me.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.24 S2-2203384 P-CR Approval 23.700-28: Solution#1 Update for Power Saving based on AMF awareness of coverage information. Huawei, HiSilicon Rel-18 Revision of S2-2202423r02. Approved Approved
9.24 S2-2202594 P-CR Approval 23.700-28: Solution discontinuous coverage architecture. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203385 Jaewoo (LGE) asks question for clarification.
Steve (Huawei) Is there AN impacts?
Stefan (Ericsson) asks questions
Yuxin (Xiaomi) asks question
Jean Yves (Thales) comments and supports
Hannu (Nokia) answers questions and provides r01.
Stephen (Qualcomm) comments
jean Yves (Thales) responds to Hannu.
Hannu (Nokia) responds to Jean Yves.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01
Jaewoo (LGE) is fine with r01.
==== Comments Deadline ====
Revised
9.24 S2-2203385 P-CR Approval 23.700-28: Solution discontinuous coverage architecture. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202594r01. Approved Approved
9.24 S2-2202809 P-CR Approval 23.700-28: Updates to KI#2: Power saving enhancement for UE in discontinuous coverage. Samsung Rel-18 Noted Steve (Huawei) comments, not clear what the aim is.
Stefan (Ericsson) provides similar comments
Yuxin (Xiaomi) comments
Hannu (Nokia) asks further question to understand the use case?
Lufeng(vivo) comments, question for clarification
==== Revisions Deadline ====
DongYeon (Samsung) replies.
Steve (Huawei) proposed to note
DongYeon (Samsung) agree to NOTE this paper.
==== Comments Deadline ====
Noted
9.24 S2-2202913 P-CR Approval 23.700-28: Updates to KI#1 on MM enhancement with discontinuous satellite coverage. Samsung Rel-18 r04 agreed. Revised to S2-2203386 Steve (Huawei) comments
Lalith(Samsung) provides r01
Hannu (Nokia) answers to Lufeng and Lalith.
Lalith(Samsung) replies to Lufeng(vivo)
Lufeng(vivo) comment: question for clarification.
Lalith(Samsung) comments
Stefan (Ericsson) provides comments
Lalith(Samsung) provides r02
Haris(Qualcomm) provides r03
Lalith(Samsung) provides r04
Hannu (Nokia) has concerns on the scope of the proposed KI update.
Lalith(Samsung) replies to Hannu (Nokia)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.24 S2-2203386 P-CR Approval 23.700-28: Updates to KI#1 on MM enhancement with discontinuous satellite coverage. Samsung Rel-18 Revision of S2-2202913r04. Approved Approved
9.24 S2-2202923 P-CR Approval 23.700-86: An update to Architecture assumptions and Principles. Xiaomi Rel-18 Noted Lalith(Samsung) seeks clarification.
Jean Yves (Thales) comments an supports adding the note.
Haris(Qualcomm) proposes to note
Steve (Huawei) comments
Lalith(Samsung) comments.
Sherry (Xiaomi) provides r01
Haris(Qualcomm) asks questions on r01
Sherry(Xiaomi) replies to Haris.
Haris(Qualcomm) comments
Sherry (Xiaomi) provides r02.
Stefan (Ericsson) provides comments
==== Revisions Deadline ====
Sherry (Xiaomi) comments.
==== Comments Deadline ====
Noted
9.24 S2-2202978 P-CR Approval 23.700-28: Key Issue: Support of 5GS Aspects of Discontinuous Coverage. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2203387 Lalith (Samsung) seeks clarification.
Steve (Huawei) comments
Stephen (Qualcomm) replies to comments from Steve (Huawei) and Lalith (Samsung)
Jean Yves (Thales) comments
Hannu (Nokia) objects to creation of new key issue with strong commonalities to the existing one. If this can be revised to propose a revision of the existing KI, then we can discuss it.
Stephen (Qualcomm) provides an r01 and responds to comments
Jean Yves (Thales) responds to Stephen
Hannu (Nokia) supports r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.24 S2-2203387 P-CR Approval 23.700-28: Key Issue: Support of 5GS Aspects of Discontinuous Coverage. Qualcomm Incorporated Rel-18 Revision of S2-2202978r01. Approved Approved
9.24 S2-2202980 P-CR Approval 23.700-28: Key Issue: Coverage by Multiple Satellite Operators. Qualcomm Incorporated Rel-18 Noted Lalith (Samsung) seeks clarification.
Steve (Huawei) comments
Hannu (Nokia) is not convinced on the need of this new KI.
Stephen (Qualcomm) replies to comments from Steve (Huawei) and Lalith (Samsung)
Stephen (Qualcomm) replies to comments from Hannu (Nokia)
Hannu (Nokia) thanks Stephen for explanation of the intended work.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
9.24 S2-2202981 P-CR Approval 23.700-28: Key Issue: Coverage using Alternative RATs. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203388 Lalith(Samsung) comments.
Jean Yves (Thales) comments on possible merge
Hannu (Nokia) agrees on the proposed merge but comments on the contents.
Stephen (Qualcomm) replies to comments from Lalith (Samsung) and Jean Yves (Thales)
Stephen (Qualcomm) provides an r01 and r02 (with correction) and responds to comments
Hannu (Nokia) still doesn't like the initial version but can live with r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.24 S2-2203388 P-CR Approval 23.700-28: Key Issue: Coverage using Alternative RATs. Qualcomm Incorporated Rel-18 Revision of S2-2202981r02. Approved Approved
9.24 - - - Documents exceeding TU Budget - - Docs:=1 -
9.24 S2-2202341 P-CR Approval 23.700-28: Solution on power saving determination based on discontinuous coverage information. Xiaomi Rel-18 Not Handled Haris(Qualcomm) provides comments
Steve (Huawei) this document exceeds TU budget and there is not handled?
Andy (VC, Samsung): Yes, this tdoc is marked as not handled.
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.25 - - - Study on UPF enhancement for Exposure And SBA (FS_UPEAS) - - Docs:=25 -
9.25 - - - New and updated Key issue - - Docs:=4 -
9.25 S2-2202758 P-CR Approval 23.700-62: Revision of Key issue #1 in TR 23.700-62 v0.1.0. China Mobile Rel-18 Approved Approved
9.25 S2-2202708 P-CR Approval 23.700-62: Update Key Issue #2: Support UPF expose information to other NFs. Samsung Rel-18 r01 agreed. Revised to S2-2203581 Yan (China Mobile) comments
Laurent (Nokia): provides r01
Kisuk (Samsung) replies.
Kisuk (Samsung) is ok with r01
==== Revisions Deadline ====
Yan (China Mobile) comments to ask the necessity of the update
Yan (China Mobile) suggests to go with r01
==== Comments Deadline ====
Revised
9.25 S2-2203581 P-CR Approval 23.700-62: Update Key Issue #2: Support UPF expose information to other NFs. Samsung Rel-18 Revision of S2-2202708r01. Approved Approved
9.25 S2-2202710 P-CR Approval 23.700-62: KI related with new UPF event exposure service(s). Samsung Rel-18 Noted Laurent (Nokia): Comments, not sure this new KI is needed (same as Magnus)
Magnus H (Ericsson) comments
Yan (China Mobile) provides r01
Yan (China Mobile) corrects the link
Laurent (Nokia): I am less and less convinced
Magnus H (Ericsson) same comment as Fenqin (Huawei)
Fenqin (Huawei) provides comments
Kisuk (Samsung) is ok with r01.
Kisuk (Samsung) replies
Kisuk (Samsung) provides comments.
Yan (China Mobile) comments
Fenqin (Huawei) Object this paper and its revision
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of this Tdoc
==== Comments Deadline ====
Kisuk (Samsung) notes this Tdoc.
Noted
9.25 - - - New and updated Solution - - Docs:=19 -
9.25 S2-2202770 P-CR Approval 23.700-62: Revision of Solution#1 in TR 23.700-62 v0.1.0. China Mobile Rel-18 r04 agreed. Revised to S2-2203582 Yan (China Mobile) provides r01 to correct the mistake
Megha(Intel) provides comments
Laurent (Nokia): Comments needing solution updates
Magnus H (Ericsson) provides r02
Fenqin (Huawei) provides r03
Magnus H (Ericsson) resending with correct link to r02
Yan (China Mobile) provides r04 for editorial update
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 + R01
Yan (China Mobile) suggests to go with r04
Magnus H (Ericsson) objects to r00 and r01, suggest r04
==== Comments Deadline ====
Revised
9.25 S2-2203582 P-CR Approval 23.700-62: Revision of Solution#1 in TR 23.700-62 v0.1.0. China Mobile, Ericsson Rel-18 Revision of S2-2202770r04. Approved Approved
9.25 S2-2202207 P-CR Approval 23.700-62: New solution: using the proper subscription mechanism depending on the event targeted by the UPF event consumer. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2203583 Magnus H (Ericsson): This pCR contains several solutions, which should be avoided.
Laurent (Nokia): all 'solutions' are linked with each other, especially one 'solution' has no procedure as the procedures are described in other 'solutions'; the chairman also said we need to allow multiple solutions when it Really makes sense
Yan (China Mobile) comments requesting a small change
Yan (China Mobile) is agree with Magnus and suggest to merge some of solutions with 1976/2389/2733
Fenqin (Huawei) ask some question
Magnus H (Ericsson) is ok with multiple solutions in a single pCR for this case.
Laurent (Nokia): provides r01
==== Revisions Deadline ====
Yan (China Mobile) suggests to go with r01
==== Comments Deadline ====
Revised
9.25 S2-2203583 P-CR Approval 23.700-62: New solution: using the proper subscription mechanism depending on the event targeted by the UPF event consumer. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-220Revision of S2-2207r01. Approved Approved
9.25 S2-2202585 P-CR Approval 23.700-62: New solution for KI#2: Support UPF expose information to other NFs (SMF). China Telecom Rel-18 Noted Magnus H (Ericsson) comments
Yan (China Mobile) comments
Fenqin (Huawei) comments
Zhiwei Mo (China Telecom) responds
Zhiwei (China Telecom) responds and provides r01
Fenqin (Huawei) suggest to note this paper and its revision.
==== Revisions Deadline ====
Magnus H (Ericsson) suggests to note this document
==== Comments Deadline ====
Noted
9.25 S2-2202652 P-CR Approval 23.700-62: Solution for KI #2: UPF event exposure service for TSC management. ETRI Rel-18 Approved Approved
9.25 S2-2202740 P-CR Approval 23.700-62: New Solution: Support Direct PFD Provisioning to UPF China Mobile Rel-18 Noted Magnus H (Ericsson) comments
Magnus H (Ericsson) objects to this pCR, since it is out of scope
Yan (China Mobile) provides r01
Laurent (Nokia): We support Magnus's understanding and objection to the PCR
Yan (China Mobile) explains that the provision service should be considered as UPF enhancement
Yan (China Mobile) provides r02 to add an EN
==== Revisions Deadline ====
Serge (T-Mobile USA) agrees with Ericsson and Nokia and objects to all revisions
Laurent (Nokia): agrees with Serge and objects to any version of this Tdoc
==== Comments Deadline ====
Noted
9.25 S2-2202748 P-CR Approval 23.700-62: New Solution: Support QoS Profile exposure by UPF. China Mobile Rel-18 Postponed Magnus H (Ericsson) comments
Yan (China Mobile) responds
Laurent (Nokia): expresses concerns (objects to) with the solution
Yan (China Mobile) provides r01 to add EN to move foward
Fenqin (Huawei) suggest to postpone this paper
==== Revisions Deadline ====
Yan (China Mobile) is OK to postpone this paper
Magnus H (Ericsson) supports postponing this paper
Laurent (Nokia): supports postponing, otherwise would object to any version
==== Comments Deadline ====
Postponed
9.25 S2-2202753 P-CR Approval 23.700-62: New Solution: Support Direct Traffic Steering Policy ID Provisioning to UPF. China Mobile Rel-18 Noted Laurent (Nokia): expresses concerns
Magnus H (Ericsson) objects to this pCR, since it is out of scope
==== Revisions Deadline ====
Serge (T-Mobile USA) agrees with Ericsson and Nokia and objects to this pCR
Laurent (Nokia): Agrees with Serge and objects to any version of this document
Yan (China Mobile) agrees to object this pCR
==== Comments Deadline ====
Noted
9.25 S2-2201976 P-CR Approval 23.700-62: Solution for Key Issue #2 for exposure to NWDAF of Data Usage Measurements PDU Session as needed for R16-R17 data analytics. Ericsson Rel-18 r02 agreed. Revised to S2-2203584 Laurent (Nokia): Comments (asking EN)
Magnus (Ericsson) provides r02
Fenqin (Huawei) provides comment
Magnus (Ericsson) provides r01 with an EN in the spirit of Laurent's suggestion
Yan (China Mobile) comments
==== Revisions Deadline ====
Magnus H (Ericsson) comments
Laurent (Nokia): objects to R00
Yan (China Mobile) suggests to go with r02
==== Comments Deadline ====
Revised
9.25 S2-2203584 P-CR Approval 23.700-62: Solution for Key Issue #2 for exposure to NWDAF of Data Usage Measurements PDU Session as needed for R16-R17 data analytics. Ericsson Rel-18 Revision of S2-2201976r02. Approved Approved
9.25 S2-2201977 P-CR Approval 23.700-62: Solution for Key Issue #2 for exposing to NWDAF QoS Flow level measurements for existing (Rel16-Rel17) data analytics. Ericsson Rel-18 r01 agreed. Revised to S2-2203585 Laurent (Nokia): Comments (requesting an EN)
Magnus (Ericsson) provides r01
Fenqin (Huawei) ask one question
Magnus H (Ericsson) question the need for the EN
==== Revisions Deadline ====
Laurent (Nokia): can live with any version only IF following EN is added: it is FFS how the solution works when NWDAF requests reporting filtered based on whether the UE is an AoI
Magnus H (Ericsson) ask question to Laurent
==== Comments Deadline ====
Revised
9.25 S2-2203585 P-CR Approval 23.700-62: Solution for Key Issue #2 for exposing to NWDAF QoS Flow level measurements for existing (Rel16-Rel17) data analytics. Ericsson Rel-18 Revision of S2-2201977r01. Approved Approved
9.25 S2-2202389 P-CR Approval 23.700-62: FS_UPEAS, KI# 2, New solution for NWDAF collecting information from UPF by event exposure. Vivo Rel-18 r02 agreed. Revised to S2-2203586 Huazhang (vivo) provides r01 to reply to Fenqin
Fenqin (Huawei) provides comments
Yan (China Mobile) asks a question
Huazhang (vivo) provides r02 and replies to Yan (China Mobile) the question
Yan (China Mobile) is ok with r02
==== Revisions Deadline ====
Yan (China Mobile) suggests to go with r02
==== Comments Deadline ====
Revised
9.25 S2-2203586 P-CR Approval 23.700-62: FS_UPEAS, KI# 2, New solution for NWDAF collecting information from UPF by event exposure. Vivo Rel-18 Revision of S2-2202389r02. Approved Approved
9.25 S2-2202647 P-CR Approval 23.700-62: New Solution on UPF event exposure to NWDAF. China Mobile Rel-18 r01 agreed. Revised to S2-2203587 Aihua(CMCC): replies to the comments from Laurent (Nokia) and provides r01.
Laurent (Nokia): (my previous comment was) Comments requesting EN
Laurent (Nokia): Comments
==== Revisions Deadline ====
Laurent (Nokia): can only live with r01 provided that following EN is added: ': it is FFS how the solution can deal with analytics targeting an AoI where target UE are located'
Aihua (CMCC) agrees to add EN, and provides r02 for CC#2/CC#3.
==== Comments Deadline ====
Revised
9.25 S2-2203587 P-CR Approval 23.700-62: New Solution on UPF event exposure to NWDAF. China Mobile Rel-18 Revision of S2-2202647r01. Approved Approved
9.25 S2-2202733 P-CR Approval 23.700-62: New Solution: Support UPF event exposure service to NWDAF China Mobile Rel-18 r03 agreed. Revised to S2-2203588 Fenqin (Huawei) provides comments
Yan (China Mobile) provides r01
Laurent (Nokia): Comments requesting a small change
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.25 S2-2203588 P-CR Approval 23.700-62: New Solution: Support UPF event exposure service to NWDAF. China Mobile Rel-18 Revision of S2-2202733r03. Approved Approved
9.25 - - - Documents exceeding TU Budget - - Docs:=2 -
9.25 S2-2202692 P-CR Approval 23.700-62: Revision of Annex A in TR 23.700-62 v0.1.0. China Mobile Rel-18 Not Handled Not Handled
9.25 S2-2202735 P-CR Approval 23.700-62: New Solution: Support QoS Monitoring results exposure by UPF China Mobile Rel-18 Not Handled Not Handled
9.26 - - - Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) - - Docs:=63 -
9.26 - - - New KI and KI update - - Docs:=3 -
9.26 S2-2202644 P-CR Approval 23.700-33: New Key Issue on Support of Emergency Services for UE to Network Relaying. Ericsson, AT&T, Apple, [vivo], Samsung, [Nokia, Nokia Shanghai Bell, OPPO] Rel-18 r04 agreed. Revised to S2-2203131 Fei (OPPO) comments.
Judy (Ericsson) responds to Fei (OPPO).
Mehrdad (Samsung) asks a clarification from Ericsson
Steve (Huawei) comments
Sudeep (Apple) comments.
Wen (vivo) comments
Judy (Ericsson) provides r01
Hannu (Nokia) responds to Judy (Ericsson) and Fei (OPPO).
Hannu (Nokia) comments and provides r02.
Mehrdad (Samsung) comments
Hong (Qualcomm) comments.
Judy (Ericsson) provides r03
Fei (OPPO) provides comments.
Wen (vivo) confirms that square bracket can be removed .
Sudeep (Apple) has comments on r03
Sudeep (Apple) answers.
Judy (Ericsson) provides r04
==== Revisions Deadline ====
Mehrdad (Samsung) is OK with r04 with the assumption that LS S2-2202986r02 will be agreed and sent to SA1.
==== Comments Deadline ====
Hannu (Nokia) supports r04 but points out that the EN on emergency call in the same PLMN has become redundant in the latest revisions.
Revised
9.26 S2-2203131 P-CR Approval 23.700-33: New Key Issue on Support of Emergency Services for UE to Network Relaying. Ericsson, AT&T, Apple, vivo, Samsung, Nokia, Nokia Shanghai Bell, OPPO Rel-18 Revision of S2-2202644r04. Approved Approved
9.26 S2-2202463 P-CR Approval 23.700-33: KI#6 Update: Addition of path switching policy. Huawei, HiSilicon Rel-18 Approved Fei (OPPO) comments that the change is not needed.
Steve (Huawei) comments, it is already happening.
Fei (OPPO) thanks for the clarification and can live with this update.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.26 - - - New solutions for KI#1 (UE-UE Relay) - - Docs:=16 -
9.26 S2-2202323 P-CR Approval 23.700-33: Moving UE-to-UE Relay solutions from TR 23.752 into TR 23.700-33. CATT, OPPO, Intel, Huawei, HiSilicon Rel-18 Approved Approved
9.26 S2-2202102 P-CR Approval 23.700-33: KI#1: New Solution for UE-to-UE relay discovery. Ericsson Rel-18 r03 agreed. Revised to S2-2203132 Yali (OPPO) comments.
Deng Qiang (CATT) asks questions for clarifications.
Zhang (Ericsson) provides response
Yali (OPPO) replies to Zhang (Ericsson)
Steve (Huawei) comments
Mehrdad (Samsung) asks whether there is a plan to merge this solution into 2323
Zhang (Ericsson) provides comments and r01
Mehrdad (Samsung) comments
Zhang (Ericsson) provides r02
Steve (Huawei) provides r03
==== Revisions Deadline ====
Zhang (Ericsson) prefer r02, but can live with r03
==== Comments Deadline ====
Revised
9.26 S2-2203132 P-CR Approval 23.700-33: KI#1: New Solution for UE-to-UE relay discovery. Ericsson Rel-18 Revision of S2-2202102r03. Approved Approved
9.26 S2-2202333 P-CR Approval 23.700-33: Consolidated solution for UE-to-UE Relay discovery and selection based on Model A and Model B discovery. OPPO, Ericsson Rel-18 Revision of S2-2200624. r02 agreed. Revised to S2-2203133 Deng Qiang (CATT) comments.
Yali (OPPO) provides r01.
Mehrdad (Samsung) asks a question for clarification
Yali (OPPO) replies to Mehrdad (Samsung).
Mehrdad (Samsung) comments
Yali (OPPO) provides r02 and replies to Mehrdad (Samsung).
Zhang (Ericsson) provides comments
Yali (OPPO) replies to Zhang (Ericsson).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203133 P-CR Approval 23.700-33: Consolidated solution for UE-to-UE Relay discovery and selection based on Model A and Model B discovery. OPPO, Ericsson Rel-18 Revision of S2-2202333r02. Approved Approved
9.26 S2-2202335 P-CR Approval 23.700-33: Consolidated solution for L3 UE-to-UE Relay communication setup after Model A and Model B discovery. OPPO, Ericsson Rel-18 Revision of (Postponed) S2-2200625. r01 agreed. Revised to S2-2203134 Mehrdad (Samsung) comments
Yali (OPPO) replies to Mehrdad (Samsung)
Yali (OPPO) indicates r01 is provided.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203134 P-CR Approval 23.700-33: Consolidated solution for L3 UE-to-UE Relay communication setup after Model A and Model B discovery. OPPO, Ericsson Rel-18 Revision of S2-2202335r01. Approved Approved
9.26 S2-2202324 P-CR Approval 23.700-33: Solution for Layer-3 UE-to-UE Relay. CATT Rel-18 r04 agreed. Revised to S2-2203135 Yali (OPPO) comments
Zhang (Ericsson) ask clarification
Deng Qiang (CATT) responds and provides r01.
Zhang (Ericsson) ask for clarification
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) comments and provides r02
Yali (OPPO) objects r02, and indicates r01 need further clarification.
Deng Qiang (CATT) provides r03 based on r01.
Deng Qiang (CATT) clarifies and provides r04.
Zhang (Ericsson) provides comments
Deng Qiang (CATT) responds to Zhang (Ericsson).
==== Revisions Deadline ====
Yali (OPPO) suggests to go with r04, not r00.
Tao(VC) PLEASE CHECK R04 agreeable or not
Steve (Huawei) suggests going with r04.
Michelle Perras (Interdigital). Prefer r02 but can accept r04.
==== Comments Deadline ====
Revised
9.26 S2-2203135 P-CR Approval 23.700-33: Solution for Layer-3 UE-to-UE Relay. CATT Rel-18 Revision of S2-2202324r04. Approved Approved
9.26 S2-2202956 P-CR Approval 23.700-33: Solution: Layer-3 UE-to-UE Relay based on IP routing. Interdigital Rel-18 Noted Yali (OPPO) comments.
Wen (vivo) comments.
Deng Qiang (CATT) comments.
Zhang (Ericsson) ask for clarification
Steve (Huawei) comments
Hannu (Nokia) asks if 'solution Y' is documented in this meeting or is it yet to be seen?
Xiaoyan Shi (Interdigital) replies and provides r01.
Deng Qiang (CATT) comments on r01.
Zhang (Ericsson) suggest to not pursue this paper
==== Revisions Deadline ====
Yali (OPPO) also suggests to not pursue this paper
Michelle Perras (Interdigital) suggests going with r01.
==== Comments Deadline ====
Noted
9.26 S2-2202325 P-CR Approval 23.700-33: Solution for Layer-2 UE-to-UE Relay. CATT Rel-18 Noted Yali (OPPO) provides comments
Zhang (Ericsson) provides comments
Deng Qiang (CATT) provides r01.
Deng Qiang (CATT) provides r03 reverted changes in step 4.
Deng Qiang (CATT) provides r02.
Xiaoyan Shi (Interdigital) comments and provides r04.
Deng Qiang (CATT) can't accept r04 and provides r05.
==== Revisions Deadline ====
Michelle Perras on behalf of Xiaoyan Shi (Interdigital) replies to Deng.
Yali (OPPO) comments
Deng Qiang (CATT) responds.
Michelle Perras (Interdigital) has concerns with most revisions and can only accept r04.
==== Comments Deadline ====
Noted
9.26 S2-2202955 P-CR Approval 23.700-33: Solution: Link Establishment procedure via Layer-2 UE-to-UE Relay. Interdigital Rel-18 CC#2: r03 agreed. r03 agreed. Revised to S2-2203150 Wen (vivo) comments.
Deng Qiang (CATT) comments.
Zhang (Ericsson) ask clarification
Yali (OPPO) comments.
Xiaoyan Shi (Interdigital) replies and provides r01
Yali (OPPO) replies to Xiaoyan Shi (Interdigital).
Xiaoyan Shi (Interdigital) replies to Yali and provides r02.
Deng Qiang (CATT) comments on r02.
==== Revisions Deadline ====
Michelle Perras on behalf of Xiaoyan Shi (Interdigital) replies to Yali and Deng.
Deng Qiang (CATT) can live with late r03, and it needs to be discussed at CC#2.
Yali (OPPO) is ok with r03 in the draft folder, cannot accept other versions.
==== Comments Deadline ====
Revised
9.26 S2-2203150 P-CR Approval 23.700-33: Solution: Link Establishment procedure via Layer-2 UE-to-UE Relay . Interdigital Rel-18 Revision of S2-2202955r03. Approved Approved
9.26 S2-2202954 P-CR Approval 23.700-33: Solution: Link Identifier Update procedure when using UE-to-UE Relay. Interdigital Rel-18 Postponed Deng Qiang (CATT) comments.
Zhang (Ericsson) ask for clarification
Xiaoyan Shi (Interdigital) replies and provides r01
Zhang (Ericsson) provides comments
Xiaoyan Shi (Interdigital) provides r02
Deng Qiang (CATT) asks to postponed this paper.
==== Revisions Deadline ====
Michelle Perras (Interdigital) no reason to postpone since 2955r03 is stable. Suggest to accept r02.
==== Comments Deadline ====
Postponed
9.26 S2-2202986 LS OUT Approval [DRAFT] LS out on service requirements for emergency service support over ProSe Relays Qualcomm Created at CC#1. r02 agreed. Revised to S2-2203130 Hong (Qualcomm) provide r0 of the LS Out draft.
Shabnam (Ericsson) Thanks Qualcomm for the first version of the LS, adds some more questions and clarifications.
Deng Qiang (CATT) asks about the work plan for this KI.
Fei (OPPO) comments.
Sudeep (Apple) comments.
Shabnam (Ericsson) responds to Oppo and CATT.
Steve (Huawei) comments
Hong (Qualcomm) provides r02.
==== Revisions Deadline ====
Fei (OPPO) is ok with r02.
Shabnam (Ericsson) ok with r02, though we need to approve the associated pCR as referenced by the LS.
Deng Qiang (CATT) is ok with r02 and thanks Shabnam (Ericsson) clarifications.
Mehrdad (Samsung) is OK with r02 with the assumption that S2-2202644r04 will be agreed.
==== Comments Deadline ====
Revised
9.26 S2-2203130 LS OUT Approval LS on service requirements for emergency service support over ProSe Relays SA WG2 - Revision of S2-2202986r02. Approved Approved
9.26 - - - New solutions for KI#2 (path switching btw two indirect paths) - - Docs:=4 -
9.26 S2-2202486 P-CR Approval 23.700-33: TR 23.700-33: Criteria for two indirect network paths switching. Vivo Rel-18 r03 agreed. Revised to S2-2203136 Wen (vivo) responds to Qiang.
Deng Qiang (CATT) comments.
Fei (OPPO) comments.
Wen (vivo) replies.
Steve (Huawei) comments
Wen (vivo) responds and provides r01
Judy (Ericsson) comments
Wen (vivo) replies and provides r02
Wen (vivo) replies and provides r03
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203136 P-CR Approval 23.700-33: TR 23.700-33: Criteria for two indirect network paths switching. Vivo Rel-18 Revision of S2-2202486r03. Approved Approved
9.26 S2-2202772 P-CR Approval 23.700-33: TR 23.700-33: KI#2, new solutions for path switching between two indirect paths. Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2203137 Fei (OPPO) comments.
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) comments
Deng Qiang (CATT) asks questions for clarifications.
Judy (Ericsson) asks questions
Judy (Ericsson) provides r02
Hong (Qualcomm) provides r02, and clarifies that Judy provided r01.
Judy (Ericsson) thanks Hong (Qualcomm) for correction (i.e. Judy provided r01)
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203137 P-CR Approval 23.700-33: TR 23.700-33: KI#2, new solutions for path switching between two indirect paths. Qualcomm Incorporated Rel-18 Revision of S2-2202772r02. Approved Approved
9.26 - - - New solutions for KI#3 (direct path switching) - - Docs:=13 -
9.26 S2-2202326 P-CR Approval 23.700-33: New solution on direct communication path switching between PC5 and Uu reference points. CATT Rel-18 Approved Steve (Huawei) asks a question
Mehrdad (Samsung) comments
Deng Qiang (CATT) responds.
Judy (Ericsson) comments
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.26 S2-2202465 P-CR Approval 23.700-33: KI#3 Solution: Path switching from PC5 path to Uu path. Huawei, HiSilicon Rel-18 Revision of (Postponed) S2-2200934. r03 agreed. Revised to S2-2203138 Deng Qiang (CATT) comments.
Fei (OPPO) asks questions.
Wen (vivo) comments.
Steve (Huawei) comments, provides r01.
Xiaoyan Shi (Interdigital) comments.
Steve (Huawei) comments, provides r02
Steve (Huawei) provides r03
Zhang (Ericsson) provides comments
Steve (Huawei) thanks Zhang for the clarification.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203138 P-CR Approval 23.700-33: KI#3 Solution: Path switching from PC5 path to Uu path . Huawei, HiSilicon Rel-18 Revision of S2-2202465r03. Approved Approved
9.26 S2-2202484 P-CR Approval 23.700-33: TR 23.700-33: New solution for UE Negotiation-based path switching from PC5 to Uu. Vivo Rel-18 r02 agreed. Revised to S2-2203139 Wen (vivo) provides r01 based on Rapporteur suggestion of merging 2485 to 2484.
Deng Qiang (CATT) comments.
Wen (vivo) responds.
Fei (OPPO) comments.
Wen (vivo) responds to Fei.
Fei (OPPO) provides comments.
Mehrdad (Samsung) comments
Wen(vivo) responds
Deng Qiang (CATT) requests revisions based on the comments.
Wen (vivo) responds to Qiang and provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203139 P-CR Approval 23.700-33: TR 23.700-33: New solution for UE Negotiation-based path switching from PC5 to Uu. Vivo Rel-18 Revision of S2-2202484r02. Approved Approved
9.26 S2-2202497 P-CR Approval 23.700-33: Solution for Path Switching between PC5 and Uu Based on Path Preference Policy. ZTE Rel-18 r03 agreed. Revised to S2-2203140 Deng Qiang (CATT) comments.
Wen (vivo) comments.
Hao Dong (ZTE) responds to Deng Qiang (CATT).
Hao Dong (ZTE) responds to Wen (vivo) and provides r01.
Fei (OPPO) comments.
Hao Dong (ZTE) responds to Fei (OPPO).
Steve (Huawei) comments
Hao Dong (ZTE) responds to Steve (Huawei) and provides r02.
Fei (OPPO) comments on r02.
Hao Dong (ZTE) responds to Fei (OPPO) and provides r03.
Mehrdad (Samsung) comments
Hao Dong (ZTE) responds to Mehrdad (Samsung).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203140 P-CR Approval 23.700-33: Solution for Path Switching between PC5 and Uu Based on Path Preference Policy. ZTE Rel-18 Revision of S2-2202497r03. Approved Approved
9.26 S2-2202550 P-CR Approval 23.700-33: KI#3, New Sol: Switching back to PC5 path. LG Electronics Rel-18 r01 agreed. Revised to S2-2203141 Deng Qiang (CATT) comments.
Fei (OPPO) comments.
Steve (Huawei) comments
LaeYoung (LGE) provides r01.
Hannu (Nokia) asks a question on r01.
Mehrdad (Samsung) comments
LaeYoung (LGE) responds Hannu (Nokia) and Mehrdad (Samsung).
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203141 P-CR Approval 23.700-33: KI#3, New Sol: Switching back to PC5 path. LG Electronics Rel-18 Revision of S2-2202550r01. Approved Approved
9.26 S2-2202618 P-CR Approval 23.700-33: KI#3, New Sol: Support direct communication path switching between PC5 and Uu. Samsung Rel-18 r03 agreed. Revised to S2-2203142 Zhang (Ericsson) ask for clarification
Deng Qiang (CATT) comments.
Fei (OPPO) comments and asks questions.
Wen (vivo) comments.
Mehrdad (Samsung) replies to Ericsson, CATT, OPPO and Vivo.
Zhang (Ericsson) provides comments
Mehrdad (Samsung) replies to Ericsson.
Steve (Huawei) comments
LaeYoung (LGE) comments.
Mehrdad (Samsung) replies to Ericsson, Huawei and LGE and provides r01 and r02. Please ignore r01.
LaeYoung (LGE) asks a Q.
Mehrdad (Samsung) replies to LGE and provides r03.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r03.
==== Comments Deadline ====
Revised
9.26 S2-2203142 P-CR Approval 23.700-33: KI#3, New Sol: Support direct communication path switching between PC5 and Uu. Samsung Rel-18 Revision of S2-2202618r03. Approved Approved
9.26 S2-2202957 P-CR Approval 23.700-33: Solution for KI#3: Direct Path Switching between PC5 and Uu (non- relay). Interdigital Rel-18 r02 agreed. Revised to S2-2203143 Deng Qiang (CATT) comments.
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) replies to CATT and Huawei and provides r01
LaeYoung (LGE) comments.
Hannu (Nokia) supports the comment from LaeYoung (LGE).
Mehrdad (Samsung) comments
Xiaoyan Shi (Interdigital) replies and provides r02
Deng Qiang (CATT) comments on r02.
==== Revisions Deadline ====
Michelle Perras (Interdigital). Prefer r02, can accept all versions.
==== Comments Deadline ====
Revised
9.26 S2-2203143 P-CR Approval 23.700-33: Solution for KI#3: Direct Path Switching between PC5 and Uu (non- relay). Interdigital Rel-18 Revision of S2-2202957r02. Approved Approved
9.26 - - - New solutions for KI#4 (path switching for L2 Relay) - - Docs:=4 -
9.26 S2-2202291 P-CR Approval 23.700-33: Solution for KI# 4: path switching for Layer-2 UE-to-Network Relay with session continuity. OPPO Rel-18 r02 agreed. Revised to S2-2203144 Wen (vivo) comments.
Steve (Huawei) comments
Steve (Huawei) asks a couple more questions
Fei (OPPO) responds and provides r01.
Fei (OPPO) provides response to Steve (Huawei)
Steve (Huawei) provides r02
==== Revisions Deadline ====
Fei (OPPO) is ok with r02.
==== Comments Deadline ====
Revised
9.26 S2-2203144 P-CR Approval 23.700-33: Solution for KI# 4: path switching for Layer-2 UE-to-Network Relay with session continuity. OPPO Rel-18 Revision of S2-2202291r02. Approved Approved
9.26 S2-2202844 P-CR Approval 23.700-33: TR 23.700-33: KI#4, new solutions for path switching between direct and indirect paths. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2203145 Fei (OPPO) comments and proposes to merge the content into S2-2202291.
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) asks question for clarification on RRC inactive.
Hong (Qualcomm) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203145 P-CR Approval 23.700-33: TR 23.700-33: KI#4, new solutions for path switching between direct and indirect paths. Qualcomm Incorporated Rel-18 Revision of S2-2202844r01. Approved Approved
9.26 - - - New solutions for KI#5 (multi-path transmission) - - Docs:=12 -
9.26 S2-2202416 P-CR Approval 23.700-85: KI#3, New Solution: Provisioning consistent URSP to UE across 5GS and EPS for Single PCF Deployment Intel Rel-18 Approved Deng Qiang (CATT) the title in chairnote is not correct.
Deng Qiang (CATT) corrected the subject.
Steve (Huawei)
Changhong (Intel) replies to Steve
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.26 S2-2202466 P-CR Approval 23.700-33: KI#5 Solution: Multi-path transmission via Layer-2 U2N Relay. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2203146 Deng Qiang (CATT) comments.
Fei (OPPO) comments.
Steve (Huawei) comments, provides r01
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203146 P-CR Approval 23.700-33: KI#5 Solution: Multi-path transmission via Layer-2 U2N Relay. Huawei, HiSilicon Rel-18 Revision of S2-2202466r01. Approved Approved
9.26 S2-2202502 P-CR Approval 23.700-33: Solution for Multi-path transmission for Layer-2 UE-to-Network Relay. ZTE Rel-18 Postponed Fei (OPPO) asks questions.
Heng (China Telecom) asks question.
LaeYoung (LGE) comments.
Hao Dong (ZTE) responds to Fei (OPPO) and Heng (China Telecom).
Hao Dong (ZTE) responds to LaeYoung (LGE).
LaeYoung (LGE) asks a Q.
Steve (Huawei) comments
Fei (OPPO) provides further comments.
Hao Dong (ZTE) answers LaeYoung (LGE).
Hao Dong (ZTE) responds to Fei (OPPO) and Steve (Huawei), and provides r01.
Hao Dong (ZTE) responds to Steve (Huawei).
Judy (Ericsson) provides r02
Deng Qiang (CATT) comments this solution enlarges RAN WI scope.
LaeYoung (LGE) has problem to understand what this solution tries to solve/achieve.
Fei (OPPO) provides comments.
Hao Dong (ZTE) responds and provides r03.
LaeYoung (LGE) replies to Fei (OPPO) and Hao Dong (ZTE).
Steve (Huawei) comments, suggesting noting.
Hao Dong (ZTE) uploads r04 with single NG-RAN node as requested by some companies; please check whether we can go with this.
==== Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this pCR because which operation is needed in NG-RAN is not clear.
Hao Dong (ZTE) suggests to POSTPONE the paper; as some clarification and further discussion are needed.
LaeYoung (LGE) is fine to mark this pCR as POSTPONED.
Steve (Huawei) let's NOTE for now.
Hao Dong (ZTE) prefers to mark the paper as postponed since there are already some comments, discussions and corresponding modifications on it.
==== Comments Deadline ====
Postponed
9.26 S2-2202487 P-CR Approval 23.700-33: TR 23.700-33: Solution for Multi-Path with Layer-3 relay without N3IWF. Vivo Rel-18 r04 agreed. Revised to S2-2203147 Deng Qiang (CATT) comments.
Wen (vivo) responds.
Fei (OPPO) asks questions.
Steve (Huawei) comments
Wen (vivo) responds and provides r01
Heng (China Telecom) ask question.
Hannu (Nokia) replies to Wen.
Wen(vivo) replies and provides r02.
Fei (OPPO) provides comments.
Wen(vivo) replies and provides r03.
Wen (vivo) replies and provides r04.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.26 S2-2203147 P-CR Approval 23.700-33: TR 23.700-33: Solution for Remote UE traffic handling for Multi-Path with Layer-3 relay without N3IWF. Vivo Rel-18 Revision of S2-2202487r04. Approved Approved
9.26 S2-2202600 P-CR Approval 23.700-33: Solution for multi-path support in case of L3 U2N relay with N3IWF. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2203148 Deng Qiang (CATT) proposed this paper merged into S2-2202849.
Hannu (Nokia) agrees the proposed merge of this document to S2-2202849.
==== Revisions Deadline ====
==== Comments Deadline ====
Merged
9.26 S2-2202849 P-CR Approval 23.700-33: TR 23.700-33: KI#5, new solution for multi-path transmission for UE-to-Network Relay. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2203148, merging S2-2202600 Hannu (Nokia) provides r01 and co-signs to acknowledge the merge of S2-2202600 to this document.
==== Revisions Deadline ====
Hong (Qualcomm) is fine with r01.
==== Comments Deadline ====
Revised
9.26 S2-2203148 P-CR Approval 23.700-33: TR 23.700-33: KI#5, new solution for multi-path transmission for UE-to-Network Relay. Qualcomm Incorporated, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2202849r01, merging S2-2202600. Approved Approved
9.26 S2-2202703 P-CR Approval 23.700-33: New solution for KI#5 on multi-path to improve reliability or data rates. China Telecom Rel-18 Postponed Steve (Huawei) comments
Heng (China Telecom) reply to Steve
LaeYoung (LGE) comments.
Heng(China Telecom) reply to LaeYoung
LaeYoung (LGE) further comments.
LaeYoung (LGE) responds to Heng (China Telecom).
==== Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this pCR due to no clear description on redundancy handling by NG-RAN.
Heng (China Telecom) dose not agree to LaeYoung (LGE)'s proposal.
Fei (OPPO) propsoes adding EN on top of r02.
LaeYoung (LGE) does not think that adding the EN suggested by Fei (OPPO) work.
Heng (China Telecom) propose adding EN.
Deng Qiang (CATT) suggests to move forward with an appropriate EN on RAN impacts.
LaeYoung (LGE) cannot accept any version. Marking as POSTPONED instead of NOTED is fine.
==== Comments Deadline ====
Postponed
9.26 S2-2202894 P-CR Approval 23.700-33: Solution for KI#5 multi-path transmission for UE-to-Network Relay. Xiaomi Rel-18 r01 agreed. Revised to S2-2203149 Steve (Huawei) comments
Judy (Ericsson) comments
Jianning (Xiaomi) response Steven (Huawei) and Judy (Ericsson)
==== Revisions Deadline ====
Judy (Ericsson) comments that there is r01 provided by Jianning (Xiaomi), asks Tao to check r01
Steve (Huawei) objects to r00, and not very keen on r01 either
==== Comments Deadline ====
Revised
9.26 S2-2203149 P-CR Approval 23.700-33: Solution for KI#5 multi-path transmission for UE-to-Network Relay. Xiaomi Rel-18 Revision of S2-2202894r01. Approved Approved
9.26 - - - Documents exceeding TU Budget - - Docs:=11 -
9.26 S2-2202488 P-CR Approval 23.700-33: TR 23.700-33: New solution for emergency service support. Vivo Rel-18 Not Handled Not Handled
9.26 S2-2202504 P-CR Approval 23.700-33: New Solution for emergency services over U2N Relay. Apple Rel-18 Not Handled Not Handled
9.26 S2-2202505 P-CR Approval 23.700-33: Solution for supporting emergency services for 5G ProSe Layer-3 UE-to-Network Relay. ZTE Rel-18 Not Handled Not Handled
9.26 S2-2202599 P-CR Approval 23.700-33: New solution: Emergency call via 5G ProSe Layer-3 UE-to-Network Relay. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Not Handled
9.26 S2-2202645 P-CR Approval 23.700-33: New solution to KI of Emergency Services for UE-to-Network Relaying. Ericsson Rel-18 Not Handled Not Handled
9.26 S2-2202868 P-CR Approval 23.700-33: New Sol: Emergency support via 5G ProSe Layer-3 UE-to-Network Relay. Samsung Rel-18 Not Handled Not Handled
9.26 S2-2202103 P-CR Approval 23.700-33: Resolving EN for terms for UE-to-UE Relaying. Ericsson Rel-18 Not Handled Not Handled
9.26 S2-2202464 P-CR Approval 23.700-33: KI#1 Solution: Determination of U2U Relay type using RSC and Policy. Huawei, HiSilicon Rel-18 Not Handled Not Handled
9.26 S2-2202485 P-CR Approval 23.700-33: TR 23.700-33: New solution for UE Negotiation-based path switching from Uu to PC5. Vivo Rel-18 Not Handled Not Handled
9.26 S2-2202592 P-CR Approval 23.700-33: Solution for switching between two indirect L3 UE-to-Network Relay paths using N3IWF. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2201007. Not Handled Not Handled
9.26 S2-2202953 P-CR Approval 23.700-33: Solution: UE-to-UE Relay Reselection. Interdigital Rel-18 Not Handled Yali (OPPO) comments this paper is already marked as 'not handled' in chairman note.
Zhang (Ericsson) ask for clarification
Zhang (Ericsson) withdraw the comment
==== Revisions Deadline ====
==== Comments Deadline ====
Not Handled
9.27 - - - Study on Seamless UE context recovery (FS_SUECR) - - Docs:=10 -
9.27 S2-2202278 P-CR Approval 23.700-61: KI 1, New Sol: Exposing UE provided unavailability period via Loss of Connectivity event subscription. LG Electronics Rel-18 r01 agreed. Revised to S2-2203389 Yannick (Nokia): Nokia provides comments.
Myungjune (LGE) responds to Yannick (Nokia) and provides r01.
Yannick (Nokia): Nokia thanks LGE, r01 clarifies.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.27 S2-2203389 P-CR Approval 23.700-61: KI 1, New Sol: Exposing UE provided unavailability period via Loss of Connectivity event subscription. LG Electronics Rel-18 Revision of S2-2202278r01. Approved Approved
9.27 S2-2202365 P-CR Approval 23.700-61: KI #1, New Solution: Usage of MICO mode for UE unavailability period management. Nokia, Nokia Shanghai Bell Rel-18 Approved Lalith (Samsung) provides r01
Yannick (Nokia): Nokia does not understand the need for the EN as proposed by Samsung, believes Samsung's comments are more related to the evaluation of the solution. Cannot accept r01.
Lalith(Samsung) replies to Yannick (Nokia)
Yannick (Nokia): Nokia replies to Samsung.
Lalith(Samsung) is OK with r00.
Yannick (Nokia): Nokia asks Samsung if they are fine with r00.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.27 S2-2202560 P-CR Approval 23.700-61: FS_SUECR Solution for Determination of unavailability period in 5GS for a specific UE. Vivo Rel-18 r02 agreed. Revised to S2-2203390 Lalith (Samsung) comments.
Yannick (Nokia): Nokia requests for clarification on the solution.
Qian (Ericsson)provides comments.
Lalith(Samsung) provides r01.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.27 S2-2203390 P-CR Approval 23.700-61: FS_SUECR Solution for Determination of unavailability period in 5GS for a specific UE. Vivo Rel-18 Revision of S2-2202560r02. Approved Approved
9.27 S2-2202885 P-CR Approval 23.700-61: Solution to KI#1: UE provided Unavailability Period. Qualcomm Inc Rel-18 Approved Lalith (Samsung) provides r01
Yannick (Nokia): Nokia does not understand the need for the EN as proposed by Samsung, believes Samsung's comments are more related to the evaluation of the solution.
Lalith(Samsung) comments
Miguel (Qualcomm) comments to not proceed with r01 and go with r00
Lalith(Samsung) is OK with r00
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.27 S2-2202942 P-CR Approval 23.700-61: 23.700-61: Solution for KI #1 Determination of unavailability period in 5GS. Apple Rel-18 Approved Lalith (Samsung) comments.
Krisztian (Apple) responds.
Lalith(Samsung) comments.
Qian (Ericsson) provides comments.
Krisztian (Apple) responds to Qian.
==== Revisions Deadline ====
==== Comments Deadline ====
Approved
9.27 S2-2202944 P-CR Approval 23.700-61: Determination of unavailability period in 5GS for a specific UE. Samsung Rel-18 r03 agreed. Revised to S2-2203391 Hiroaki (KDDI) asks some comments for clarification.
Lalith(Samsung) replies to Hiroaki (KDDI)
Yannick (Nokia): Nokia provides comments.
Lalith(Samsung) replies to Yannick (Nokia) and provides r01.
Qian (Ericsson) comments and asks question
Lalith(Samsung) replies to Qian (Ericsson)
Hiroaki (KDDI) understood comments and ask to add KDDI as co-signer.
Lalith(Samsung) thanks KDDI and add KDDI as co-signer in r03.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
9.27 S2-2203391 P-CR Approval 23.700-61: Determination of unavailability period in 5GS for a specific UE. Samsung, KDDI Rel-18 Revision of S2-2202944r03. Approved Approved
9.27 S2-2202946 P-CR Approval 23.700-61: Solution for unavailability period using NAS MO. Samsung Rel-18 Noted Yannick (Nokia): Nokia provides comments.
Lalith(Samsung) comments.
Qian (Ericsson) provides comments.
Lalith(Samsung) proposes to NOTE this paper.
==== Revisions Deadline ====
==== Comments Deadline ====
Noted
10 - - - Project Planning and Management - - Docs:=0 -
10.1 - - - New and Revised Work Items, TS/TR Cover sheets - - Docs:=6 -
10.1 S2-2202230 SID REVISED Approval Revised SID: Study on System Enabler for Service Function Chaining. Intel Rel-18 Approved Approved
10.1 S2-2202282 SID REVISED Approval New SID on Study on architecture enhancement for XR and media services. China Mobile, Huawei, HiSilicon, Tencent, Xiaomi Rel-18 Revision of SP-211646. r02 agreed. Revised to S2-2203589 Dan (China Mobile) provides r01.
Dan (China Mobile) provides r02.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
10.1 S2-2203589 SID REVISED Approval New SID on Study on architecture enhancement for XR and media services . China Mobile, Huawei, HiSilicon, Tencent, Xiaomi Rel-18 Revision of S2-2202282r02. Approved Approved
10.1 S2-2202417 SID REVISED Approval SID Revised: FS_eUEPO Intel (Rapporteur) Rel-18 Approved Approved
10.1 S2-2202691 SID REVISED Approval Revised SID on Study on UPF enhancement for Exposure And SBA. China Mobile Rel-18 Revision of SP-211652. Approved Approved
10.1 S2-2202760 SID NEW Approval New SID on Rel-18 study consolidation. LG Electronics Rel-18 Enjoyed and Noted Noted
10.2 - - - Rel-18 SID/WID Status Reports - - Docs:=43 -
10.2 S2-2202327 WI STATUS REPORT Information FS_5G_ProSe_Ph2 Status Report CATT, OPPO Rel-18 Revised in S2-2203013 Revised
10.2 S2-2203013 WI STATUS REPORT Information WI Status Report: Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) Rapporteur Created at CC#1. Revision of S2-2202327. Noted Noted
10.2 S2-2203011 WI STATUS REPORT Information WI Status Report: Study on satellite access Phase 2 (FS_5GSAT_Ph2) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202999 WI STATUS REPORT Information WI Status Report: Study on 5G System with Satellite Backhaul (FS_5GSATB) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202610 WI STATUS REPORT Information FS_5MBS_Ph2 status report Huawei (rapporteur) Rel-18 Revised in S2-2203005 Revised
10.2 S2-2203005 WI STATUS REPORT Information WI Status Report: Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) Rapporteur Created at CC#1. Revision of S2-2202610. Noted Noted
10.2 S2-2202298 WI STATUS REPORT Information FS_5TRS_URLLC status report Nokia, Nokia Shanghai Bell (Rapporteur) Rel-18 Revised in S2-2202994 Revised
10.2 S2-2202994 WI STATUS REPORT Information WI Status Report: Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) Rapporteur Created at CC#1. Revision of S2-2202298. Noted Noted
10.2 S2-2203000 WI STATUS REPORT Information WI Status Report: Study on the support for 5WWC Phase 2 (FS_5WWC_Ph2) Rapporteur Created at CC#1. Noted Laurent (Nokia): provides r00 (FS_5WWC_Ph2 status report)
==== Revisions Deadline ====
==== Comments Deadline ====
Laurent (Nokia): provides r01
Sebastian (Qualcomm) comments
Laurent (Nokia): provides r02
Sebastian (Qualcomm) provides r03
Noted
10.2 S2-2202922 WI STATUS REPORT Information FS_AIMLsys Status Report OPPO, Samsung Rel-18 Revised in S2-2203008 Revised
10.2 S2-2203008 WI STATUS REPORT Information WI Status Report: Study on System Support for AI/ML-based Services (FS_AIMLsys) Rapporteur Created at CC#1. Revision of S2-2202922. Noted Noted
10.2 S2-2203002 WI STATUS REPORT Information WI Status Report: Study on 5G AM Policy (FS_AMP) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202990 WI STATUS REPORT Information WI Status Report: Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202993 WI STATUS REPORT Information WI Status Report: Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) Rapporteur Created at CC#1. WITHDRAWN Withdrawn
10.2 S2-2202494 WI STATUS REPORT Information FS_EDGE_Ph2 status report Huawei (Rapporteur) Rel-18 Revised in S2-2202998 Noted
10.2 S2-2202998 WI STATUS REPORT Information WI Status Report: Study on Edge Computing Phase 2 (FS_EDGE_Ph2) Rapporteur Created at CC#1. Revision of S2-2202494. Noted Noted
10.2 S2-2202997 WI STATUS REPORT Information WI Status Report: Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202698 WI STATUS REPORT Information FS_eNA_Ph3 statuts report China Mobile M2M Company Ltd. Rel-18 Revised in S2-2203010 Revised
10.2 S2-2203010 WI STATUS REPORT Information WI Status Report: Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) Rapporteur Created at CC#1. Revision of S2-2202698. Noted Noted
10.2 S2-2202222 WI STATUS REPORT Information FS_eNPN_Ph2 Status Report Ericsson (rapporteur) Revised in S2-2202991 Revised
10.2 S2-2202991 WI STATUS REPORT Information WI Status Report: Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) Rapporteur Created at CC#1. Revision of S2-2202222. Noted Noted
10.2 S2-2202670 WI STATUS REPORT Information Status report for FS_eNS_Ph3 ZTE Rel-18 Revised in S2-2203001 Revised
10.2 S2-2203001 WI STATUS REPORT Information WI Status Report: Study on Network Slicing Phase 3 (FS_eNS_Ph3) Rapporteur Created at CC#1. Revision of S2-2202670. Noted Noted
10.2 S2-2202418 WI STATUS REPORT Information Status Report for FS_eUEPO Intel (Rapporteur) Revised in S2-2203009 Revised
10.2 S2-2203009 WI STATUS REPORT Information WI Status Report: Study on Enhancement of 5G UE Policy (FS_eUEPO) Rapporteur Created at CC#1. Revision of S2-2202418. Noted Noted
10.2 S2-2202989 WI STATUS REPORT Information WI Status Report: Study on Generic group management, exposure and communication enhancements (FS_GMEC) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2203004 WI STATUS REPORT Information WI Status Report: Study on evolution of IMS multimedia telephony service (FS_NG_RTC) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2203003 WI STATUS REPORT Information WI Status Report: Study on Personal IoT Networks (FS_PIN) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202905 WI STATUS REPORT Information FS_Ranging_SL Status Report Xiaomi Rel-18 Revised in S2-2203007 Revised
10.2 S2-2203007 WI STATUS REPORT Information WI Status Report: Study on Ranging based services and sidelink positioning (FS_Ranging_SL) Rapporteur Created at CC#1. Revision of S2-2202905. Noted Noted
10.2 S2-2202995 WI STATUS REPORT Information WI Status Report: Study on RedCap Phase 2 (FS_RedCAP_Ph2) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202988 WI STATUS REPORT Information WI Status Report: Study on System Enabler for Service Function Chaining (FS_SFC) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202979 WI STATUS REPORT Information FS_SUECR Status Report Samsung Rel-18 Revised in S2-2203014 Revised
10.2 S2-2203014 WI STATUS REPORT Information WI Status Report: Study on Seamless UE context recovery (FS_SUECR) Rapporteur Created at CC#1. Revision of S2-2202979. Noted Noted
10.2 S2-2202992 WI STATUS REPORT Information WI Status Report: Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2203012 WI STATUS REPORT Information WI Status Report: Study on UPF enhancement for Exposure And SBA (FS_UPEAS) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202996 WI STATUS REPORT Information WI Status Report: Study on Vehicle Mounted Relays (FS_VMR) Rapporteur Created at CC#1. Noted Noted
10.2 S2-2202419 WI STATUS REPORT Information FS_XRM status report China Mobile(rapporteur) Rel-18 Revised in S2-2203006 Revised
10.2 S2-2203006 WI STATUS REPORT Information WI Status Report: Study on XR (Extended Reality) and media services (FS_XRM) Rapporteur Created at CC#1. Revision of S2-2202419. Noted Noted
10.2 S2-2202297 WI STATUS REPORT Information IIoT status report Nokia, Nokia Shanghai Bell (Rapporteur) Rel-17 Noted Noted
10.2 S2-2203016 WI STATUS REPORT Information WI Status Report: IIoT Rapporteur Created at CC#1. WITHDRAWN Withdrawn
10.2 S2-2202263 WI STATUS REPORT Information MINT Status Report LG Electronics Rel-17 Noted Noted
10.2 S2-2203015 WI STATUS REPORT Information WI Status Report: MINT Rapporteur Created at CC#1. WITHDRAWN Withdrawn
10.3 - - - Review of the Work Plan - - Docs:=0 -
10.4 - - - Planning future meetings - - Docs:=2 -
10.4 S2-2202962 OTHER Endorsement SA WG2 meeting calendar for year 2024 SA WG2 Chair Revised to S2-2203617. Patrice (Huawei) proposes to move Jan SA2-AH one week earlier, and July SA2-AH one or two weeks earlier.
Puneet (SA2 Chair) responds to Patrice.
Patrice (Huawei) responds to Puneet, and has to insist that the January ad-hoc placeholder is shifted one week earlier. Provides r01 accordingly.
Puneet (SA2 Chair) responds to Patrice, makes some suggestions, and proposes to have further discussion over CC#2.
==== Revisions Deadline ====
==== Comments Deadline ====
Revised
10.4 S2-2203617 OTHER Endorsement SA WG2 meeting calendar for year 2024 SA WG2 Chair Revision of S2-2202962. CC#2: Endorsed Endorsed
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=112 -
99 S2-2202116 CR Approval 23.288 CR0514 (Rel-17, 'F'): Add NWDAF as a consumer NF of the Nnsacf_SliceEventExposure services Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2202802 OTHER Information Reserved for incoming LS MCC Withdrawn (Not Used) Withdrawn
99 S2-2202095 P-CR Approval 23.700-48: Scenarios and assumptions for KI#5 GSMA OPG impacts and improvements for EHE operated by separate party Ericsson Rel-18 WITHDRAWN Withdrawn
99 S2-2202039 P-CR Approval 23.700-80: 23.700-80: KI#4 - User consent to enable 5GC Assistance to support Application AI.ML Operation OPPO Rel-18 WITHDRAWN Withdrawn
99 S2-2202286 P-CR Approval 23.700-80: New solution on 5GC information exposure to UE Samsung Electronics France SA Rel-18 WITHDRAWN Withdrawn
99 S2-2202101 CR Approval 23.502 CR3428 (Rel-17, 'F'): Correction to Naf_EventExposure service Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2202081 P-CR Approval 23.700-48: EAS discovery for federated OPs China Mobile Rel-18 WITHDRAWN Withdrawn
99 S2-2202322 LS OUT Approval [DRAFT] Reply LS on how to receive the first PC5-S unicast message during PC5-S connection setup procedure CATT Rel-17 Response to S2-2201945. WITHDRAWN Withdrawn
99 S2-2202321 DISCUSSION Discussion Discussion on Source Layer-2 ID of first PC5-S unicast message CATT, LG Electronics, Deutsche Telekom Rel-17 WITHDRAWN Withdrawn
99 S2-2202428 P-CR Approval 23.700-27: Update KI#1 to cover packet out-of-sequence problems Huawei, HiSilicon, CATT Rel-18 WITHDRAWN Withdrawn
99 S2-2202429 P-CR Approval 23.700-27: Solution for Key Issue #1: Information of satellite constellation and change of backhaul delay exposed to PCF/AF Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2202430 P-CR Approval 23.700-27: Enable on-board local data switch based on UPF-level N4 session Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2202431 P-CR Approval 23.700-71: Solution for Key Issue #1:Architectural Enhancement to support User Plane positioning Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2202432 P-CR Approval 23.700-71: Solution for KI#5: Assistance data provisioning for low power high accuracy GNSS positioning Huawei, HiSilicon Rel-18 WITHDRAWN Withdrawn
99 S2-2202631 P-CR Approval 23.700-81: New Solution on enhancements on QoS Sustainability analytics v1.1 China Mobile M2M Company Ltd. Rel-18 WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 483
Agreed: 111
Replied to LSs: 27
Noted: 180
Merged: 68
For e-mail approval: 0
Postponed: 80
Withdrawn: 141
Total documents: 1609