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-2208100 Agenda Approval SA WG2 #153E Meeting Agenda SA WG2 Chair - Approved ==== Final Deadline ==== Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
3 - - - SA2#152E Meeting report - - Docs:=1 -
3 S2-2208101 Report Approval Auto-Generated Report of SA WG2 meeting #152E SA WG2 Secretary - Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=50 -
4.1 - - - LS In for Info or potential action - - Docs:=11 -
4.1 S2-2208114 LS In Information Reply LS to CT WG3 on Data Reporting API SA WG4 (S4-221118) Rel-17 Revision of Postponed S2-2208095 from S2#152-e. Noted Yannick (Nokia): Nokia suggests to note this LS since there is no action for SA2. Noted
4.1 S2-2208118 LS In Information LS from CT WG4: Reply LS on PLMN ID used in Roaming Scenarios CT WG4 (C4-224444) Rel-17 Revision of Postponed S2-2208099 from S2#152-e. Noted Noted
4.1 S2-2208119 LS In Information LS from GSMA DESS: LS to 3GPP - Hosted SEPP GSMA DESS (GSMA DESS LS to 3GPP SA3) Noted Peter Hedman (Ericsson) propose to note Noted
4.1 S2-2208120 LS In Information LS from : LS reply to 3GPP SA6 on Clarification of Edge Node Sharing GSMA OPG (OPG_103_Doc_03) Noted Magnus O (Ericsson) proposes to Note this LS Noted
4.1 S2-2208149 LS In Information LS from RAN WG3: LS on NCR Solutions RAN WG3 (R3-225253) Rel-18 Noted Wanqiang (Huawei): proposes to note this LS as there is no action for SA2.
Qian (Ericsson) agrees to NOTE the LS.
Noted
4.1 S2-2208166 LS In Information LS from ETSI ISG MEC: LS reply to GSMA OPAG on E/WBI ETSI ISG MEC (MEC(22)000430r2) Noted Magnus O (Ericsson) proposes to Note this LS Noted
4.1 S2-2208169 LS In Information LS from IETF LPWAN WG: Liaison statement from the IETF LPWAN WG to 3GPP IETF LPWAN WG (LS_from_IETF_1796) Noted Hannu (Nokia) proposes to note this LS as there is no action for SA2 right now. Noted
4.1 S2-2208154 LS In Action LS from SA WG3-LI: Identifier availability for Lawful Interception during Inter-PLMN handover SA WG3-LI (S3i220485) Rel-18 Response drafted in S2-2209207. Final response in S2-2209262 Laurent (Nokia): Comments
Chris (Vodafone) replies to Nokia. Draft LS response will be in S2-2209207.
Chris (Vodafone) provides the draft LS response in S2-2209207.
Replied to
4.1 S2-2209207 LS OUT Approval [DRAFT] Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover Vodafone Rel-18 Created at CC#1. Response to S2-2208154. r00 agreed. Revised to S2-2209262. Chris (Vodafone) provides the draft LS response in S2-2209207.
==== Revisions Deadline ====
Leo (Deutsche Telekom) supports to send the LS.
==== Final Deadline ====
Revised
4.1 S2-2209262 LS OUT Approval Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover SA WG2 Rel-18 Revision of S2-2209207r00. Approved Approved
4.1 S2-2208155 LS In Action LS from SA WG4: Reply LS to SA2 on EVEX SA WG4 (S4-221122) Rel-17 Noted Yannick (Nokia): Nokia suggests to note this LS since there is no action for SA2. Noted
4.1 - - - Reply LS or CRs - - Docs:=35 -
4.1 S2-2208123 LS In Action LS from CT WG1: LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP accesses CT WG1 (C1-225230) Rel-18 Response drafted in S2-2208376. Final response in S2-2209263 Replied to
4.1 S2-2208376 LS OUT Approval [DRAFT] Reply LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP Access Type Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2208123. r00 agreed. Revised to S2-2209263. Fei (OPPO) comments and provides r01 to drafts/revisions.
Hannu (Nokia) cannot accept r01 as it is not available '403 forbidden: Access denied'. We need to see any revision that is proposed for the meeting.
Fei (OPPO) provides links in revisions.
Hannu (Nokia) thanks Fei for the link to r01 but can't agree the contents. Considering discussion on the related CRs (8377 - 8378), the original version is more correct.
==== Revisions Deadline ====
Fei (OPPO) indicates that the reply LS is linked to status of S2-2208377.
==== Final Deadline ====
Hannu (Nokia) agrees with Fei and Qianghua that the LS must reflect what was agreed in this meeting, so only agreed CRs can be attached.
Revised
4.1 S2-2209263 LS OUT Approval Reply LS on handling of PDU sessions for emergency services when registering via both 3GPP and non-3GPP accesses SA WG2 Rel-17 Revision of S2-2208376r00. Approved Approved
4.1 S2-2208377 CR Approval 23.501 CR3711 (Rel-17, 'F'): Emergency PDU session transfer Nokia, Nokia Shanghai Bell, MediaTek, Google Inc., Ericsson Rel-17 r08 agreed. Revised to S2-2209264. Jinguo(ZTE) provides r01
Fei (OPPO) comments and the CR is not needed.
Hannu (Nokia) comments to Fei (OPPO) that CR on TS 23.501 is needed for sure, as the present SA2 text mandates rejecting completely valid emergency calls!
Hannu (Nokia) agrees the comment from Jinguo and provides r02 with editorial change only.
Haris(Qualcomm) asks questions for clarification
Hannu (Nokia) answers to Haris and asks for clarification on the emergency call back requirements?
Shabnam (Ericsson) provides comments to Qualcomm question
Hannu (Nokia) responds to Shabnam
Fei (OPPO) responds to Hannu (Nokia)
Kundan (NEC) provides comments.
Hannu (Nokia) provides r03 and replies to Fei and Kundan. Can also live with r02 which is also correct.
Kundan (NEC) provides response to Hannu (Nokia).
Fei (OPPO) comments and provides r04
Hannu (Nokia) answers to Kundan
Kundan (NEC) responds to Hannu.
Hannu (Nokia) provides r05 with the minimum change. UE impact cannot be avoided due to incorrect condition in the second paragraph.
Fei (OPPO) provides comments.
Hannu (Nokia) comments that both the general rule in clause 5.16.4.1 and its implementation in clause 5.16.4.9 are needed.
Fei (OPPO) provides replies
Qianghua (Huawei) comments
Shabnam (Ericsson) CT1 is wrong and they are not stage 2 responsible and we must also align with 4G, CT4 etc. I understand you want to consider this for Rel-18, but we cannot accept messing up normal emergency calls being messed up for a corner case CT1 found. Simple soln follow existing principles.
Jinguo(ZTE) comment
Kundan (NEC) answers to Hannu
Kundan (NEC) agrees with Huawei to keep both action. both actions are handling different situations. I explained the reason in my previous mail.
Hannu (Nokia) provides r06 and answers the questions.
Haris(Qualcomm) indicates that r06 is not acceptable
Hannu (Nokia) agrees with Haris and provides hopefully less weird r07.
Fei (OPPO) requests to untick the ME box.
Kundan(NEC) provides the reference. states the abnormal case is well discussed in CT1 from Rel-9.
==== Revisions Deadline ====
Shabnam (Ericsson) prefers r03, can accept r00 and r07 and objects to other revisions.
Fei (OPPO) can only accept r03 and objects to other revisions including r00.
Hannu (Nokia) can also accept r03.
Fei (OPPO) can only accept r04 and objects to other revisions including r00. Please ignore the previous incorrect version.
Hannu (Nokia) asks Fei whether the UE that has got emergency PDU Session in one Access Type is allowed to request another emergency PDU session in the same Access Type. Yes or no?
Shabnam (Ericsson) believes that the UE impact from stage 2 specification is unavoidable since we have conflicting text for 5G, which one UE should be compliant with if they are conflicting?
Qianghua (Huawei) can live with r07. Prefer to untick the ME impacts.
Hannu (Nokia) proposes to take this CR to CC in order to check which revision can be agreed.
Fei (OPPO) replies to Hannu and can live with r08 which is based on r04 plus additional changes in the 2nd paragraph.
Hannu (Nokia) thanks Fei.
Kundan(NEC) can live with r08.
Qianghua (Huawei) can also live with r08 if majority can accept
Hannu (Nokia) thanks for supports and provides a copy of r08 in 'revisions' folder as suggested in CC #2
==== Final Deadline ====
Revised
4.1 S2-2209264 CR Approval 23.501 CR3711R1 (Rel-17, 'F'): Emergency PDU session transfer Nokia, Nokia Shanghai Bell, MediaTek, Google Inc., Ericsson Rel-17 Revision of S2-2208377r08. Approved Agreed
4.1 S2-2208378 CR Approval 23.502 CR3561 (Rel-17, 'F'): Emergency PDU session transfer Nokia, Nokia Shanghai Bell, MediaTek, Google Inc. Rel-17 Noted Fei (OPPO) comments
Jinguo(ZTE) comments and the CR is not needed.
Hannu (Nokia) thanks Fei (OPPO) for good comment and explains to Jinguo why the CR is needed and provides r01.
Judy (Ericsson) asks how the CR is relevant to the emergency PDU Session transfer
Hannu (Nokia) replies to Judy and provides r02
Qianghua (Huawei) shares the same views and provides more reasons why this CR is not needed
Judy (Ericsson) checks if the intention is to align with stage 3 regarding deregistration notify due to duplicated PDU Session detected in UDM
Hannu (Nokia) responds to comments and proposes to choose between the original version and r02.
Judy (Ericsson) provides r03 to make an alignment with stage 3
Qianghua (Huawei) sustains the view
==== Revisions Deadline ====
Judy (Ericsson) propose to go with r03 which is pure stage 3 alignment not specific to emergency PDU Session, objects to other revisions (r00 included) due to incorrect reason for change.
Hannu (Nokia) answers to Qianghua's question even though this discussion becomes irrelevant after r03 that aligns SA2 text with the one in 29.503.
Hannu (Nokia) thanks Judy for good compromise and supports r03.
Qianghua (Huawei) objects all revs including the original
Judy (Ericsson) comments
Jinguo(ZTE) comments that r03 has issues and is not agreeable. ask to postpone
Hannu (Nokia) supports Judy and points out that all emergency PDU session aspects have been removed in r03 making it pure alignment with the existing stage 3 requirements.
Hannu (Nokia) proposes to solve the editorial issues in r03 by re-using CR text from the original r00 and proposes the CR for CC. Late revision r04 shows the changes over r03.
Qianghua (Huawei) sustains the objection, sorry to say that concerns are still not addressed
Hannu (Nokia) answers to Qianghua and provides r05 to fully align with TS 29.503 hoping that such alignment is acceptable?
==== Final Deadline ====
Qianghua (Huawei) still objects given the reasons explained online and offline, sorry
Hannu (Nokia) understand that the discussion with Qianghua is a wording issue and uses the wording from Qianghua in r06
Noted
4.1 S2-2208125 LS In Action LS from CT WG1: LS on starting a timer in RRC-inactive state CT WG1 (C1-225319) Rel-18 Responses drafted in S2-2208305, S2-2208838. Final response in S2-2209265 Replied to
4.1 S2-2208305 LS OUT Approval [DRAFT] Reply LS on starting a timer in RRC-inactive state Huawei, HiSilicon Rel-18 Response to S2-2208125. r01 agreed. Revised to S2-2209265, merging S2-2208838 Hannu (Nokia) has got no strong view on which LS to take as template (8305 or 8838) but suggests to attach CR 8837 and to shorten the LS.
Haris(Qualcomm) provides r01
==== Revisions Deadline ====
Hannu (Nokia) supports r01 but points out that this LS still depends on the approval of the CR in S2-2208837 (which is hopefully approved in this meeting)
==== Final Deadline ====
Revised
4.1 S2-2209265 LS OUT Approval Reply LS on starting a timer in RRC-inactive state SA WG2 Rel-18 Revision of S2-2208305r01, merging S2-2208838. Approved Approved
4.1 S2-2208838 LS OUT Approval [DRAFT] Reply LS on starting a timer in RRC-inactive state Qualcomm Rel-18 Response to S2-2208125. Merged into S2-2209265 LiMeng (Huawei) suggests to merge into S2-2208305
Hannu (Nokia) has got no strong view on which LS to take as template but shows the way forward in r01.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
4.1 S2-2208837 CR Approval 23.501 CR3733 (Rel-18, 'F'): De-activation timer for eCall only mode UE in RRC_INACTIVE Qualcomm Incorporated Rel-18 Approved LiMeng (Huawei) has a question on the WID code.
Haris(Qualcomm) responds to LiMeng re the WI code
Hannu (Nokia) supports the principle but asks about the second change in the CR?
==== Revisions Deadline ====
==== Final Deadline ====
Agreed
4.1 S2-2208134 LS In Action LS from CT WG4: LS on service operation used in AMF relocation in Inter PLMN handover procedure CT WG4 (C4-224408) Rel-17 Noted Hannu (Nokia) proposes to note the LS, assuming the CR related CR in S2-2208896 that carries out the SA2 action can be agreed.
Qian (Ericsson) agrees to NOTE the LS.
Noted
4.1 S2-2208253 CR Approval 23.502 CR3554 (Rel-17, 'F'): N2 HO service operation update Ericsson Rel-17 Merged into S2-2209266 Fenqin (Huawei) suggest to merge this paper to 8896.
Qian (Ericsson) is ok to merge.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
4.1 S2-2208896 CR Approval 23.502 CR3587 (Rel-17, 'F'): Update service operation used in AMF relocation in Inter PLMN handover procedure Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2209266, merging S2-2208253 Fenqin (Huawei) provides r01.
Qian (Ericsson) provides r02.
Jinguo(ZTE) provides r03.
Hannu (Nokia) provides r04 to clean up the cover page.
Fenqin (Huawei) provides r06 and ask ignore r05.
==== Revisions Deadline ====
Qian (Ericsson) is ok with r06.
Hannu (Nokia) supports r06.
==== Final Deadline ====
Revised
4.1 S2-2209266 CR Approval 23.502 CR3587R1 (Rel-17, 'F'): Update service operation used in AMF relocation in Inter PLMN handover procedure Huawei, HiSilicon, Ericsson, ZTE Rel-17 Revision of S2-2208896r06, merging S2-2208253. Approved Agreed
4.1 S2-2208130 LS In Action LS from CT WG3: Reply LS on Traffic Identification within 5G Media Streaming CT WG3 (C3-224556) Rel-17 Response drafted in S2-2208353. Postponed Postponed
4.1 S2-2208353 LS OUT Approval [DRAFT] Reply LS on Traffic Identification within 5G Media Streaming Ericsson Rel-17 Response to S2-2208130. r00 agreed. Revised to S2-2209258. Postponed ==== Revisions Deadline ====
Mirko (Huawei) proposes to postpone the LS response.
==== Final Deadline ====
Postponed
4.1 S2-2209258 LS OUT Approval [DRAFT] Reply LS on Traffic Identification within 5G Media Streaming Ericsson Rel-17 Revision of S2-2208353r00. WITHDRAWN Withdrawn
4.1 S2-2208354 CR Approval 23.502 CR3431R2 (Rel-17, 'F'): Traffic Identification using ToS/TC for 5G Media Streaming Ericsson Rel-17 Revision of (Postponed) S2-2203843 from S2#151E. r03 agreed. Revised to S2-2209267. Postponed Judy (Ericsson) responds to Dan(China Mobile)
Dan(China Mobile) provide suggestion for updating the NOTE
Dan(China Mobile) reply suggestion
Mirko (Huawei) comments.
Judy (Ericsson) provides r01 and responds
Dan (China Mobile) ok for r01 NOTE update
Pallab (Nokia) shares the view with Mirko (Huawei) and questions whether we need to duplicate the information in TS 23.502
Judy (Ericsson) responds to Pallab (Nokia) and Mirko (Huawei).
Mirko (Huawei) responds.
Judy (Ericsson) responds to Mirko (Huawei) and provide r02
Pallab (Nokia) NOT OK with r02
Dario (Qualcomm) is not OK with r02 and provides r03.
Judy (Ericsson) is fine with r03 and responds
==== Revisions Deadline ====
Mirko (Huawei) objects to the original version and all revisions and suggests to instead clarify those issues in 23.503 clause 6.1.3.6.
==== Final Deadline ====
Postponed
4.1 S2-2209267 CR Approval 23.502 CR3431R3 (Rel-17, 'F'): Traffic Identification using ToS/TC for 5G Media Streaming Ericsson Rel-17 Revision of S2-2208354r03. WITHDRAWN Withdrawn
4.1 S2-2208133 LS In Action LS from CT WG4: Reply to LS on VoLTE Roaming GBR Handling CT WG4 (C4-224401) Rel-17 This LS was postponed Postponed
4.1 S2-2208158 LS In Action LS from SA WG4: DRAFT Reply LS to 3GPP SA2 on VoLTE Roaming GBR Handling SA WG4 (S4-221192) Rel-17 This LS was postponed Postponed
4.1 S2-2208504 DISCUSSION Discussion Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming . Vivo Rel-17 Noted Judy (Ericsson) proposes to have the discussion in 9115 thread
==== Revisions Deadline ====
==== Final Deadline ====
Noted
4.1 S2-2208606 DISCUSSION Discussion Discussion paper for VoLTE GBR handling in roaming case OPPO Rel-17 Noted Judy (Ericsson) proposes to have the discussion in 9115 thread
==== Revisions Deadline ====
==== Final Deadline ====
Noted
4.1 S2-2209115 DISCUSSION Decision Avoiding a HPLMN request for a GBR greater than the VPLMN s value for IMS voice in home routed roaming. Vodafone Rel-17 Noted Judy (Ericsson) proposes to use this paper for further discussion for 9115, 8502, 8504 and 8606.
Haris(Qualcomm) provides comments to the indicated papers
Yang (OPPO) provides comments
Rainer (Nokia) comments.
Judy (Ericsson) comment
Xiaobo (vivo) asks questions for clarification
Chris (Vodafone) replies
Xiaobo (vivo) asks further questions for clarification
Chris (Vodafone) responds to Vivo's questions
Xiaobo (vivo) provides some clarification and share understanding
Chris (Vodafone) responds and suggests an outline for an LS to GSMA
Leo (Deutsche Telekom) agrees with the proposal and the LS to be sent to GSMA
Xiaobo (vivo) agrees with proposal from Chris (Vodafone) and supports to send LS to GSMA.
Rainer (Nokia) is ok with a LS to GSMA.
Yang (OPPO) is supportive of sending the LS to GSMA. And suggest to ask GSMA if they can define a recommended GBR value for the roaming case
Chris (Vodafone) replies an comments EPS fallback and on the difficulty of a common value for TN and NTN
Judy (Ericsson) is OK with LS to GSMA
Haris(Qualcomm) is ok to send LS to GSMA but asks one question
Rainer (Nokia) replies to Haris (Qualcomm).
Haris(Qualcomm) responds
==== Revisions Deadline ====
Tao(VC) check the status of the proposed LS out to GSMA
Chris (Vodafone) provides the draft LS in the drafts folder.
Judy (Ericsson) provides an update to the draft LS in the drafts folder
Rainer (Nokia) provides an update.
Chris (Vodafone) replies.
Chris (Vodafone) provides an updated draft.
Chris (Vodafone) uploads that draft into inbox/revisions as S2-2210158.
==== Final Deadline ====
Haris(Qualcomm) provides r01
Chris (Vodafone) is OK with r01
Noted
4.1 S2-2210158 LS OUT Approval [DRAFT] Response to 'LS to 3GPP SA WG2 on VoLTE Roaming GBR Handling' Vodafone CC#4: r01 agreed. Revised to S2-2209969. Chris (Vodafone) is OK with r01
Judy (Ericsson) provides r02
Rainer (Nokia) comments.
Chris (Vodafone) does not agree with r02.
Chris (Vodafone) puts a copy of 10158r01 into the CC#4 folder.
Revised
4.1 S2-2209969 LS OUT Approval Response to LS to SA WG2 on VoLTE Roaming GBR Handling SA WG2 - Revision of S2-2210158r01. Approved Approved
4.1 S2-2208502 CR Approval 23.501 CR3718 (Rel-17, 'F'): Handling of HPLMN request for GBR greater than VPLMN value for IMS voice service in home routed roaming Vivo Rel-17 Noted Judy (Ericsson) proposes to have the discussion in 9115 thread
Rainer (Nokia) proposes to note 8502 at this meeting.
Xiaobo (vivo) replies to questions from Rainer (Nokia) and propose to postpone this.
==== Revisions Deadline ====
Leo (Deutsche Telekom) proposes to NOTE the CR.
Xiaobo (vivo) is ok to note the CR.
==== Final Deadline ====
Noted
4.1 S2-2209140 CR Approval 23.228 CR1257 (Rel-18, 'F'): IMS cross border mobility with Home routed IMS calls Vodafone (S2-2205903 was Ericsson, Vodafone?, AT&T) Rel-18 Confirm Sources!. Affected clauses under revision history! r06 agreed. Revised to S2-2209268. Rainer (Nokia) provides r01.
Magnus H (Ericsson) provides r02
Rainer (Nokia) provides r03.
Chris (Vodafone) provides r04.
Rainer (Nokia) replies.
Magnus H (Ericsson) comments.
Leo (Deutsche Telekom) comments.
Haris(Qualcomm) comments
Chris (Vodafone) replies to Qualcomm
Rainer (Nokia) comments.
Rainer (Nokia) provides r05.
Shabnam (Ericsson) provides comments that I don't believe this is Category F CR but rather Category C. So I propose to change to a Cat C please.
Rainer (Nokia) provides r06.
==== Revisions Deadline ====
Antoine (Orange) comments that the WI code should be 'V8, TEI18', and asks why the 2 new procedures are specific to voice whereas the LS from SA3-LI did not mention voice.
Chris (Vodafone) replies to Orange and Ericsson. To help MCC, he will change the WID name from S8HR to V8 during the CR clean up (3GU did not allow a search for 2 letter WID codes).
==== Final Deadline ====
Revised
4.1 S2-2209268 CR Approval 23.228 CR1257R1 (Rel-18, 'F'): IMS cross border mobility with Home routed IMS calls Vodafone, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2209140r06. Approved Agreed
4.1 S2-2208159 LS In Action LS from SA WG5: LS on Reference point allocation to support charging services SA WG5 (S5-225775) Rel-18 Response drafted in S2-2209199. Final response in S2-2209259 Replied to
4.1 S2-2209199 LS OUT Approval [DRAFT] LS reply on Reference point allocation to support charging services MATRIXX Software Rel-18 Response to S2-2208159. r00 agreed. Revised to S2-2209259. ==== Revisions Deadline ====
==== Final Deadline ====
Revised
4.1 S2-2209259 LS OUT Approval LS reply on Reference point allocation to support charging services SA WG2 Rel-18 Revision of S2-2209199r00. Approved Approved
4.1 S2-2209200 CR Approval 23.501 CR3752 (Rel-18, 'B'): Reference point numbers for charging MATRIXX Software Rel-18 r01 agreed. Revised to S2-2209347. Antoine (Orange) comments that the WI code should be MMS_CH_SBI, and wonders whether it's worth spending efforts allocating RP numbers...
Gerald (MATRIXX Software) followed the given guidance and provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
4.1 S2-2209347 CR Approval 23.501 CR3752R1 (Rel-18, 'B'): Reference point numbers for charging MATRIXX Software Rel-18 Revision of S2-2209200r01. Approved Agreed
4.1 - - - Common issue CRs - - Docs:=4 -
4.1 S2-2208396 CR Approval 23.502 CR3562 (Rel-17, 'F'): Release of emergency PDU Session without data transfer for a period Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
4.1 S2-2209065 CR Approval 23.501 CR3748 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints Peraton Labs, CISA ECD, AT&T, Verizon Rel-17 Noted Antoine (Orange) comments that the WI code should be 'TEI17, 5GS_Ph1' like the CR that introduced this clause (CR#3507).
Judy (Ericsson) questions FASMO aspect
Laurent (Nokia): would a way forward be that this CR (and its companion) are agreed as R18 CR(s)
==== Revisions Deadline ====
Tao(VC) I see change proposal and way forward by Laurent. Any update/view from the author or co-source company on the way forward?
==== Final Deadline ====
Noted
4.1 S2-2209067 CR Approval 23.503 CR0757 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints Peraton Labs, CISA ECD, AT&T, Verizon Rel-17 Noted Antoine (Orange) comments on WI code and wording.
Judy (Ericsson) proposes to discuss in 9065 thread
Laurent (Nokia): would a way forward be that this CR (and its companion) are agreed as R18 CR(s)
==== Revisions Deadline ====
Tao(VC) I see change proposal and way forward by Laurent. Any update from the author or co-source company on the way forward view?
Laurent (Nokia): ok for me for R18
Judy (Ericsson) objects to this paper, and any enhancement in Rel-18 needs to be justified as commented previously in 9065 thread.
==== Final Deadline ====
Noted
4.1 S2-2209191 CR Approval 23.502 CR3601 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints Peraton Labs, CISA ECD, AT&T, Verizon Rel-17 Noted Antoine (Orange) comments that the WI code should be 'TEI17, 5GS_Ph1'.
Judy (Ericsson) proposes to discuss in 9065 thread
Jinguo(ZTE) fixes the title and provides comment
Mirko (Huawei) provides r01.
==== Revisions Deadline ====
Judy (Ericsson) objects to this paper, and any enhancement in Rel-18 needs to be justified as commented previously in 9065 thread.
==== Final Deadline ====
Noted
4.2 - - - P-CRs/CRs related to use of inclusive language in 3GPP - - Docs:=0 -
5 - - - Pre-Rel-17 Maintenance (excluding all 5G topics) - - Docs:=0 -
5.1 - - - 3GPP Packet Access Maintenance - - Docs:=0 -
5.2 - - - QoS and PCC Maintenance - - Docs:=0 -
5.3 - - - Non-3GPP Access Maintenance - - Docs:=0 -
5.4 - - - IMS and IMS-Related Maintenance - - Docs:=0 -
6 - - - Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) - - Docs:=0 -
6.1 - - - General aspects, concepts and reference models - - Docs:=7 -
6.1 S2-2208408 CR Approval 23.501 CR3583R3 (Rel-17, 'F'): Clarification on Mapped NSSAI Huawei, HiSilicon Rel-17 Revision of (agreed, but noted by TSG SA) S2-2202047 from S2#150E. Should be a revision of (Postponed) S2-2205700. r06 agreed. Revised to S2-2209558. Josep (DT) asks for clarification why roaming mention in normative text is removed.
Haiyang (Huawei) responds to Josep (DT).
Genadi (Lenovo) provides question for clarification.
Haris(Qualcomm) provides r01
Peter Hedman (Ericsson) provides r02
Alessio(Nokia) comments
Alessio(Nokia) provides r03
Krisztian (Apple) provides r05.
Genadi (Lenovo) provides r04.
Peter Hedman (Ericsson) provides comments
Alessio(Nokia) is ok with r05.
Guillaume (MediaTek Inc.) provides r06
Alessio(Nokia) prefers r05 but can live with r06
Haiyang (Huawei) is ok with r06.
Genadi (Lenovo) is fine with r06, but we prefer r05 to avoid repetition of Requested NSSAI.
Peter Hedman (Ericsson) ok with r06 and r05 as they have at the end the same meaning
==== Revisions Deadline ====
==== Final Deadline ====
Revised
6.1 S2-2209558 CR Approval 23.501 CR3583R4 (Rel-17, 'F'): Clarification on Mapped NSSAI Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Apple Rel-17 Revision of S2-2208408r06. Approved Agreed
6.1 S2-2208762 CR Approval 23.501 CR3729 (Rel-17, 'F'): Mapped NSSAI when UE is roaming Ericsson, Qualcomm Incorporated Rel-17 Postponed Haiyang (Huawei) provides r01
Peter Hedman (Ericsson) provides reply
alessio(Nokia) provides r02
Krisztian (Apple) provides r03.
Jinguo(ZTE) provides r04
Myungjune (LGE) provides r05.
Peter Hedman (Ericsson) provides comments and r06
alessio(Nokia) is ok with r03.
alessio(Nokia) objects to r05 and r04
alessio(Nokia) objects to r06
Guillaume (MediaTek Inc.) supports r06
Peter Hedman (Ericsson) provides comments and suggests to postpne the CR due to one company objection
Alessio(nokia) rather suggests to approve r03
Peter Hedman (Ericsson) provides comments that r03 is not agreeble before CT1 provided feedback
alessio(nokia) so really the reason why this is not approved is Ericsson objection to r03 technical content.
==== Revisions Deadline ====
Haris(Qualcomm) indicates that r03 is useless to solve the issue in reason for change
Jinguo(ZTE) suggest to approve r06
Peter Hedman (Ericsson) ok with r06 or to postpone
Alessio(Nokia) comments that r03 is the only version that we accept in line with existing CT1 text (so it does align with CT1 text). Nokia objects to changing existing clear specification unless there is a FSMO reason DUE to the specifications.
==== Final Deadline ====
Postponed
6.1 S2-2208763 LS OUT Approval [DRAFT] LS on Alignments related to usage of mapped S-NSSAi Ericsson Rel-17 r05 agreed. Revised to S2-2209559. Peter Hedman (Ericsson) provides r02 adding a statement about possibly doing CRs from Rel-15 at the next meeting.
Alessio(Nokia) does not agree we need to state a speculative statement as in r02... if we agree to go to rel-15 at this meeting we just say so. if not we say there was no agreement to go back to rel-15 in which case it is inconsistent spec set (really? do we want that?). we shall take the decision at this meeting. in fact we should ask a number on Thursday to get the job done really...(not sure there is value to postpone?)
Peter Hedman (Ericsson) provides comment that time passed for getting new tdoc numbers, as explained by chair att CC-1
Peter Hedman (Ericsson) provides r03
Alessio(Nokia) believes there is nothing preventing the allocation of new tdoc numbers if this is needed and there is consensus. I missed the statement new tdoc numbers are forbidden even if they are needed. asks Ericsson if they would object to allocation of tdoc numbers if we all agree to that.
Haris(Qualcomm) comment that CR numbers need to be completed in the LS
Peter Hedman (Ericsson) provides r04
alessi(Nokia) provides r05
==== Revisions Deadline ====
Peter Hedman (Ericsson) propose to approve r05 as r06 simply tries to hide the debate.
Peter Hedman (Ericsson) sorry, r05 hides the mapping issue for roaming i.e. we really prefer to be clear and instead approve r04. If Nokia objects to r04 as they want to hide it, we are ok with r05.
alessio(Nokia) can only accept r05
==== Final Deadline ====
Revised
6.1 S2-2209559 LS OUT Approval Alignments related to usage of mapped S-NSSAI SA WG2 Rel-17 Revision of S2-2208763r05. Approved Approved
6.1 S2-2208834 CR Approval 23.501 CR3673R1 (Rel-17, 'F'): Mapped NSSAI alignment with stage-3 Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2205753 from S2#152E. r03 agreed. Revised to S2-2209560. Alessio(Nokia) comments on the release of this CR and asks why it is not rel-15 if this is aligning with stage 3 sing rel-15
Haris(Qualcomm) responds that we are ok to bring the same CR to rel.15/16 at next meeting
Krisztian (Apple) provides r01.
Peter Hedman (Ericsson) provides r02
Alessio(Nokia) ok with r01.
Guillaume (MediaTek Inc.) agrees with r01 (and certainly r02)
alessio(nokia) Provides r03
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r03
==== Final Deadline ====
Revised
6.1 S2-2209560 CR Approval 23.501 CR3673R2 (Rel-17, 'F'): Mapped NSSAI alignment with stage-3 Qualcomm Incorporated, Apple, MediaTek Inc Rel-17 Revision of S2-2208834r03. Approved Agreed
6.2 - - - Common Access Control, RM and CM functions and procedure flows - - Docs:=0 -
6.3 - - - Session management and continuity functions and flows - - Docs:=4 -
6.3 S2-2208351 CR Approval 23.502 CR3559 (Rel-16, 'F'): 3GPP PS Data Off status in PDU Session Establishment Ericsson Rel-16 r01 agreed. Revised to S2-2209561. Laurent (Nokia): Comments and suggests to only consider this for R17
Judy (Ericsson) responds to Laurent (Nokia) and prefer to have the correction in Rel-16 as well.
Mirko (Huawei) comments.
Judy (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
6.3 S2-2209561 CR Approval 23.502 CR3559R1 (Rel-16, 'F'): 3GPP PS Data Off status in PDU Session Establishment Ericsson Rel-16 Revision of S2-2208351r01. Approved Agreed
6.3 S2-2208352 CR Approval 23.502 CR3560 (Rel-17, 'F'): 3GPP PS Data Off status in PDU Session Establishment Ericsson Rel-17 r00 agreed. Revised to S2-2209562. ==== Revisions Deadline ====
==== Final Deadline ====
Revised
6.3 S2-2209562 CR Approval 23.502 CR3560R1 (Rel-17, 'F'): 3GPP PS Data Off status in PDU Session Establishment Ericsson Rel-17 Revision of S2-2208352r00. Approved Agreed
6.4 - - - Security related functions and flows - - Docs:=0 -
6.5 - - - QoS concept and functionality - - Docs:=2 -
6.5 S2-2209058 CR Approval 23.501 CR3747 (Rel-17, 'F'): Correction on conditions for using SPI for UE derived QoS rules Qualcomm Incorporated Rel-17 r02 agreed. Revised to S2-2209563. Stefan (Ericsson) provides r01
Mirko (Huawei) comments.
Hong (Qualcomm) provides r02.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
6.5 S2-2209563 CR Approval 23.501 CR3747R1 (Rel-17, 'F'): Correction on conditions for using SPI for UE derived QoS rules Qualcomm Incorporated Rel-17 Revision of S2-2209058r02. Approved Agreed
6.6 - - - Policy and charging control - - Docs:=9 -
6.6 S2-2208132 LS In Action LS from CT WG3: UE Policy Control with PCF re-selection during AMF relocation CT WG3 (C3-224697) Rel-17 Responses drafted in S2-2208348, S2-2208859, S2-2209089. Postponed Haiyang (Huawei) proposes to use this thread to discuss the LS 8132
Belen (Ericsson) provides comments
Jinguo(ZTE) provides comments
Belen (Ericsson) asks ZTE
DongYeon (Samsung) comments.
Uri(Oracle) provides comments
Haiyang (Huawei) comments
Jinguo(ZTE) replies to Belen (Ericsson)
Huazhang (vivo) have some observation and join the discussion
Yue (China Telecom) provides comment.
Belen (Ericsson) replies to the discussion on the PCF needs to know if it is an initial registration or a mobility case
Pallab (Nokia) provides views
Uri (Oracle) responds to Haiyang
Haiyang (Huawei) responds to Uri (Oracle), Ok to postpone the LS discussion
Belen (Ericsson) is okay to postpone the LS.
DongYeon (Samsung) agrees to postpone this LS.
Postponed
6.6 S2-2208348 LS OUT Approval [DRAFT] Reply LS on UE Policy Control with PCF re-selection during AMF relocation Ericsson Rel-17 Response to S2-2208132. Postponed Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) agrees to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2208859 LS OUT Approval [DRAFT] LS on UE Policy Control with PCF re-selection during AMF relocation Huawei, HiSilicon Rel-17 Response to S2-2208132. Postponed Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) agrees to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2209089 LS OUT Approval [DRAFT] Reply LS on UE Policy Control with PCF re-selection during AMF relocation Samsung Electronics Romania Rel-17 Response to S2-2208132. Postponed Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) agrees to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2209091 DISCUSSION Decision UE Policy Association Establishment when AMF relocation with PCF change. Samsung Rel-17 Noted ==== Revisions Deadline ====
DongYeon (Samsung) suggests to note this discussion paper.
==== Final Deadline ====
Noted
6.6 S2-2209093 CR Approval 23.502 CR3597 (Rel-17, 'F'): UE Policy Association Establishment when AMF relocation with PCF change Samsung Rel-17 Postponed Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly.
Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) agrees to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2209095 CR Approval 23.503 CR0758 (Rel-17, 'F'): UE Policy Association Establishment when AMF relocation with PCF change Samsung Rel-17 Postponed Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly.
Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) agrees to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2208349 CR Approval 23.502 CR3558 (Rel-17, 'F'): UE Policy determination at AMF relocation with PCF change Ericsson Rel-17 Postponed DongYeon (Samsung) asks a question.
Belen (Ericsson) asks if questions below are replied in S2-2208132
Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly.
Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) proposes to postpone this paper.
==== Final Deadline ====
Postponed
6.6 S2-2208350 CR Approval 23.503 CR0742 (Rel-17, 'F'): UE Policy determination at AMF relocation with PCF change Ericsson Rel-17 Postponed Jinguo(ZTE) suggests to use 8132 as thread for discussion, and update the CR accordingly.
Haiyang (Huawei) suggests to postpone the paper as per discussion in 8132.
==== Revisions Deadline ====
DongYeon (Samsung) proposes to postpone this paper.
==== Final Deadline ====
Postponed
6.7 - - - 3GPP access specific functionality and flows - - Docs:=3 -
6.7 S2-2208252 CR Approval 23.501 CR3703 (Rel-17, 'F'): PScell handling in 5GS Ericsson Rel-17 Noted Hannu (Nokia) proposes to note this CR as it is attempting to extend the agreed scope of Rel-17 feature.
Qian (Ericsson) provides comments.
Wanqiang (Huawei) has concern and proposes to note this CR.
Qian (Ericsson) responds.
Hannu (Nokia) replies to Qian.
Chris (Vodafone) thinks that the Ericsson CR is logical.
Hannu (Nokia) comments that this CR is not what we agreed when introducing this feature and that the justification for this 5GS change is derived from EPS.
==== Revisions Deadline ====
Qian (Ericsson) responds to Hannu(Nokia) and propose to approve original revision.
Wanqiang (Huawei) is not Ok with original revision as it is not a correction CR.
==== Final Deadline ====
Noted
6.7 S2-2209002 CR Approval 23.501 CR3742 (Rel-17, 'F'): Correction of reference for RedCap indication from UE Qualcomm Inc. Rel-17 Bad WI code. CR Number incorrect XXX! Should be 3742 (in revision number cell). r02 agreed. Revised to S2-2209564. Hannu (Nokia) provides r01.
Miguel (Qualcomm) ok with r01.
Steve (Huawei) comments on the record rev number and CR number.
Miguel (Qualcomm) provides r02 correcting CR number and Rev number
==== Revisions Deadline ====
Qian (Ericsson) is ok with r02
Steve (Huawei) is ok with r02
==== Final Deadline ====
Revised
6.7 S2-2209564 CR Approval 23.501 CR3742R1 (Rel-17, 'F'): Correction of reference for RedCap indication from UE Qualcomm Inc. Rel-17 Revision of S2-2209002r02. Approved Agreed
6.8 - - - Specific services support - - Docs:=0 -
6.9 - - - Interworking and Migration - - Docs:=2 -
6.9 S2-2208382 CR Approval 23.501 CR3712 (Rel-17, 'F'): Monitoring event in 5GS to EPS mobility Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2209565. Fenqin (Huawei): Comments and provides r01
Qian (Ericsson) asks questions
Hannu (Nokia) asks questions and comments that some changes in r01 are not correct.
Fenqin (Huawei) provides a feedback to Hannu
Qian (Ericsson) provides comments.
Hannu (Nokia) answers to Fenqin.
Hannu (Nokia) asks follow-up questions
Fenqin (Huawei) answers to Hannu.
Hannu (Nokia) provides r02
==== Revisions Deadline ====
Fenqin (Huawei) is fine with r02
Fenqin (Huawei) provides response to Qian
Qian (Ericsson) provides further comments.
Hannu (Nokia) proposes to agree r02.
Fenqin (Huawei) we are fine to go with r02.
==== Final Deadline ====
Revised
6.9 S2-2209565 CR Approval 23.501 CR3712R1 (Rel-17, 'F'): Monitoring event in 5GS to EPS mobility Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2208382r02. Approved Agreed
6.10 - - - Non-3GPP access specific functionality and flows - - Docs:=0 -
6.11 - - - Framework functions - - Docs:=0 -
7 - - - Rel-16 Maintenance for 5G (excluding 5GS_Ph1) - - Docs:=0 -
7.1 - - - Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) - - Docs:=2 -
7.1 S2-2208174 CR Approval 23.287 CR0184 (Rel-17, 'F'): Removal of V2X policy request during registration procedure LG Electronics, Ericsson, CATT, Huawei, ZTE Rel-17 Postponed LaeYoung (LGE) thinks that result for this CR should be same to result of S2-2208356/8357 in AI#8.8 for consistent handling of same topic (i.e. approved or postponed).
==== Revisions Deadline ====
LaeYoung (LGE) proposes to get this CR POSTPONED as well because the result of S2-2208356/8357 in AI#8.8 covering same topic is Postponed.
==== Final Deadline ====
Postponed
7.1 S2-2208175 CR Approval 23.503 CR0738 (Rel-17, 'F'): Removal of V2X policy request during registration procedure LG Electronics, Ericsson, CATT, Huawei, ZTE Rel-17 Postponed LaeYoung (LGE) thinks that result for this CR should be same to result of S2-2208356/8357 in AI#8.8 for consistent handling of same topic (i.e. approved or postponed).
==== Revisions Deadline ====
LaeYoung (LGE) proposes to get this CR POSTPONED as well because the result of S2-2208356/8357 in AI#8.8 covering same topic is Postponed.
==== Final Deadline ====
Postponed
7.2 - - - Wireless and Wireline Convergence for the 5G system architecture (5WWC) - - Docs:=4 -
7.2 S2-2208180 CR Approval 23.316 CR2072 (Rel-17, 'F'): Change the direction of the arrow in figure IPLOOK Rel-17 Spec version incorrect - V17.3.0! r02 agreed. Revised to S2-2209670. Laurent (Nokia): Comments, shall provide revision marks
Weizhi Wu(IPLOOK) provides r01
Weizhi Wu(IPLOOK) provides r02
Stefan (Ericsson) comments on the revision marks
==== Revisions Deadline ====
Weizhi Wu(IPLOOK) provides r03
Stefan (Ericsson) suggest to agree r03
Laurent (Nokia): suggests to agree R03 for the same reason than Stefan
Marco (Huawei) ok with r03 since agrees with Stefan (Ericsson) and Laurent (Nokia)
==== Final Deadline ====
Revised
7.2 S2-2209670 CR Approval 23.316 CR2072R1 (Rel-17, 'F'): Change the direction of the arrow in figure IPLOOK Rel-17 Revision of S2-2208180r02. Approved Agreed
7.2 S2-2208323 CR Approval 23.501 CR3708 (Rel-16, 'F'): R16 Correction on TNGF functionality Huawei, HiSilicon Rel-16 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
7.2 S2-2208324 CR Approval 23.501 CR3709 (Rel-17, 'A'): R17 Correction on TNGF functionality Huawei, HiSilicon Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
7.3 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) - - Docs:=0 -
7.4 - - - Cellular IoT support and evolution for the 5G System (5G_CIoT) - - Docs:=0 -
7.5 - - - Enablers for Network Automation for 5G (eNA) - - Docs:=0 -
7.6 - - - Enhancement to the 5GC Location Services (5G_eLCS) - - Docs:=0 -
7.7 - - - 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) - - Docs:=0 -
7.8 - - - Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - - Docs:=0 -
7.9 - - - Architecture enhancements for the support of Integrated access and backhaul (IABARC) - - Docs:=0 -
7.10 - - - Enhancement of URLLC supporting in 5GC (5G_URLLC) - - Docs:=5 -
7.10 S2-2208138 LS In Action LS from CT WG4: LS on Packet Delay Failure Threshold CT WG4 (C4-224636) Rel-17 Postponed Postponed
7.10 S2-2208572 CR Approval 23.503 CR0750 (Rel-16, 'F'): Clarifications for QoS monitoring control Huawei, HiSilicon Rel-16 Postponed Shabnam (Ericsson) provides detailed comments and objects to the CR as not FASMO and adds new functions not in scope.
Mirko (Huawei) replies to Shabnam's comments.
Devaki (Nokia) comments. We also believe the CR changes must be limited to FASMO changes and new enhancements must be removed.
Mirko (Huawei) responds to Devaki's questions.
==== Revisions Deadline ====
Shabnam (Ericsson) proposes to note the CR and work offline towards a resolution at the next meeting.
Devaki (Nokia) proposes to postpone the paper.
==== Final Deadline ====
Postponed
7.10 S2-2208573 CR Approval 23.503 CR0751 (Rel-17, 'A'): Clarifications for QoS monitoring control Huawei, HiSilicon Rel-17 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
7.10 S2-2208574 CR Approval 23.501 CR3721 (Rel-16, 'F'): Clarifications for QoS monitoring control Huawei, HiSilicon Rel-16 Noted Shabnam (Ericsson) provides technical comments and objects to the CR as this is not FASMO and changing functions that are stable since Rel-16.
Genadi (Lenovo) provides a question for clarification.
Mirko (Huawei) responds to Genadi's question.
Mirko (Huawei) replies to Shabnam's comments.
Genadi (Lenovo) replies to Mirko (Huawei).
Mirko (Huawei) comments.
Shabnam (Ericsson) provides comments in line and notes that Lenovo has created a separate thread after Ericsson email thread was established...
Mirko (Huawei) responds.
==== Revisions Deadline ====
Shabnam (Ericsson) provides comments that since we have not created any revision but good discussion, propose to note now and work offline until next meeting.
==== Final Deadline ====
Noted
7.10 S2-2208575 CR Approval 23.501 CR3722 (Rel-17, 'A'): Clarifications for QoS monitoring control Huawei, HiSilicon Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
7.11 - - - Enhancement of Network Slicing (eNS) - - Docs:=0 -
7.12 - - - Optimisations on UE radio capability signalling (RACS) - - Docs:=0 -
7.13 - - - Enhanced IMS to 5GC Integration (eIMS5G_SBA) - - Docs:=0 -
7.14 - - - User Data Interworking and Coexistence (UDICoM) - - Docs:=1 -
7.14 S2-2208186 CR Approval 23.502 CR3551 (Rel-17, 'F'): Alignment of TS 23.502 with SBI-based SMS Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
7.15 - - - Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) - - Docs:=0 -
7.16 - - - 5GS Transfer of Policies for Background Data Transfer (xBDT) - - Docs:=0 -
7.17 - - - Single radio voice continuity from 5GS to 3G (5G_SRVCC) - - Docs:=0 -
8 - - - Rel-17 WIDs - - Docs:=0 -
8.1 - - - Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) - - Docs:=16 -
8.1 - - - 5GS information exposure - - Docs:=9 -
8.1 S2-2208167 LS In Action LS from CT WG3: LS on Issues on exposing 5GS information to an untrusted AF CT WG3 (C3-224688) Rel-17 Responses drafted in S2-2208705, S2-2208992. Final response in S2-2209566 Replied to
8.1 S2-2208705 LS OUT Approval [DRAFT] LS reply on Issues on exposing 5GS information to an untrusted AF Huawei, HiSilicon Rel-17 Response to S2-2208167. Merged into S2-2209566 Josep (DT) would like to point out that A1 is not an answer to Q1.
Belen (Ericsson) provides comments
Wang Yuan (Huawei) replies to Belen (Ericsson) and Josep(DT), and provides r01.
==== Revisions Deadline ====
Yannick (Nokia): Nokia suggests to merge this into S2-2208992. r01 for this draft LS out is not aligned with further changes made to related CR in S2-2208991.
Wang Yuan (Huawei) is OK to merge this into S2-2208992.
==== Final Deadline ====
Merged
8.1 S2-2208992 LS OUT Approval [DRAFT] Reply LS on Issues on exposing 5GS information to an untrusted AF Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2208167. r01 agreed. Revised to S2-2209566, merging S2-2208705 Belen (Ericsson) provides comments
Yannick (Nokia): Nokia provides r01 which aligns with S2-2208991r03.
==== Revisions Deadline ====
Leo (Deutsche Telekom) supports r01
==== Final Deadline ====
Revised
8.1 S2-2209566 LS OUT Approval Reply LS on Issues on exposing 5GS information to an untrusted AF SA WG2 Rel-17 Revision of S2-2208992r01, merging S2-2208705. Approved Approved
8.1 S2-2208704 CR Approval 23.288 CR0549 (Rel-17, 'F'): Clarification on exposing 5GS information to an untrusted AF Huawei, HiSilicon Rel-17 Merged into S2-2209671 Antoine (Orange) asks a fundamental question.
Wang Yuan (Huawei) propose to merge this CR into S2-2208991.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.1 S2-2208991 CR Approval 23.288 CR0553 (Rel-17, 'F'): Corrections on exposing 5GS information to untrusted AF Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2209671, merging S2-2208704 Antoine (Orange) asks a fundamental question.
Belen (Ericsson) provides comments.
Malla (NTT DOCOMO) provides comments.
Yannick (Nokia): Nokia provides r01.
Wang Yuan (Huawei) thanks r01 for merging the 'NSI ID' proposal from 8704 and asks question on r01.
Yannick (Nokia): Nokia replies to Huawei.
Malla (NTT DOCOMO) provided r02.
Yannick (Nokia): Nokia requests clarification to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) replies to Yannick (Nokia).
Belen (Ericsson) cannot agree with the proposed updates in this CR
Yannick (Nokia): Nokia asks if comment from Ericsson applies to all revisions that have been provided so far.
Yannick (Nokia): Nokia provides r03 and asks if this could be a way forward.
Malla (NTT DOCOMO) asks for clarification.
Yannick (Nokia): Nokia answers that this revision should be read together with the LS out draft reply in S2-2208992r01.
Yannick (Nokia): Nokia provides r04, with same text proposal as r03, but with cover page changes.
==== Revisions Deadline ====
Wang Yuan (Huawei) supports r04 and would like to co-sign.
Belen (Ericsson) asks to remove in r04
NOTE 1: Dispersion analytics bound by slice are not provided to untrusted AF.
Yannick (Nokia): Nokia agrees with proposal from Ericsson. We suggest to go with 'r04 + removal of NOTE 1 in 6.10.1'.
==== Final Deadline ====
Revised
8.1 S2-2209671 CR Approval 23.288 CR0553R1 (Rel-17, 'F'): Corrections on exposing 5GS information to untrusted AF Nokia, Nokia Shanghai Bell, Huawei Rel-17 Revision of S2-2208991r04, merging S2-2208704. Approved Agreed
8.1 S2-2208990 LS OUT Approval [DRAFT] Reply LS on eNA_Ph2 issues Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2205413 (Replied to at S2#151E). r00 agreed. Revised to S2-2209567 ==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.1 S2-2209567 LS OUT Approval Reply LS on eNA_Ph2 issues SA WG2 Rel-17 Revision of S2-2208990r00. Approved Approved
8.1 - - - Other - - Docs:=7 -
8.1 S2-2208824 CR Approval 23.288 CR0550 (Rel-17, 'F'): Formatting and Processing Instructions related correction to Nadrf_DataManagement service ZTE Rel-17 r03 agreed. Revised to S2-2209672. Yannick (Nokia): Nokia cannot accept initial version of the CR for Rel-17. Formatting and processing instructions have not been discussed in the context of ADRF, adding this at this stage of Rel-17 is not appropriate. Provides r01.
Jinguo(ZTE) provides r02
Yannick (Nokia): Nokia replies to ZTE and provides r03.
==== Revisions Deadline ====
Yannick (Nokia): Nokia comments that if r03 is acceptable some changes to coversheet would be needed.
Jinguo(ZTE) is ok with r03 + coversheet change, and thanks Yannick for good suggestion
==== Final Deadline ====
Revised
8.1 S2-2209672 CR Approval 23.288 CR0550R1 (Rel-17, 'F'): Formatting and Processing Instructions related correction to Nadrf_DataManagement service ZTE, Nokia Rel-17 Revision of S2-2208824r03. Approved Agreed
8.1 S2-2208989 CR Approval 23.288 CR0552 (Rel-17, 'F'): Corrections for time window in ADRF Nadrf_DataManagement service Nokia, Nokia Shanghai Bell Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.1 S2-2208247 CR Approval 23.288 CR0545 (Rel-17, 'F'): Granularity of time and location for NWDAF analytics results Ericsson Rel-17 Postponed Wang Yuan (Huawei) raises concerns on r00.
Belen (Ericsson) replies to Huawei concerns and asks if those are resolved
==== Revisions Deadline ====
Belen (Ericsson) asks Huawei if their comments were addressed, no response was received.
Wang Yuan (Huawei) thanks for the clarification and in principle ok with this idea but still suggests to postpones the CR for next meeting since the changes still needs some further considerations.
==== Final Deadline ====
Postponed
8.1 S2-2208591 CR Approval 23.288 CR0547 (Rel-17, 'F'): Remove the Editor s Note related to EVEX in SA WG4 Qualcomm Incorporated Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.1 S2-2208173 CR Approval 23.288 CR0544 (Rel-17, 'F'): Correction on SMCCE Analytics LG Electronics, Ericsson Rel-17 Postponed LaeYoung (LGE) comments that the change in this CR conflicts with the change in 8247 (clause 6.12.3).
Belen (Ericsson) agrees that this one is not needed if we go with the change in 8247 (clause 6.12.3).
==== Revisions Deadline ====
LaeYoung (LGE) thinks that this CR can be Approved because 8247 is expected to be Noted.
Belen (Ericsson) asks to check S2-2208247 first, given that Huawei did not reply.
LaeYoung (LGE) proposes to POSTPONE this CR as 8247 is expected to be postponed for further discussion.
Belen (Ericsson) is okay to POSTPONE
==== Final Deadline ====
Postponed
8.1 S2-2208248 CR Approval 23.288 CR0546 (Rel-17, 'F'): Corrections to Slice Load level Analytics ID Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=9 -
8.2 S2-2208139 LS In Information LS from CT WG6: Reply LS on Facilitating roaming adoption across 3GPP NPN deployments CT WG6 (C6-220475) Rel-17 Noted Peter Hedman (Ericsson) provides comments and propose to note the LS Noted
8.2 S2-2208766 CR Approval 23.503 CR0753 (Rel-17, 'F'): The list of PSIs associated to an SNPN Ericsson Rel-17 r04 agreed. Revised to S2-2209568. Josep (DT) comments, provides r01.
Mirko (Huawei) comments.
Josep (DT) tries, provides r03, please disregard r02. Requets to pelase re-check r03.
Josep (DT) provides r04.
Belen (Ericsson) is okay with r04.
Josep (DT) is happy to co-sign.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.2 S2-2209568 CR Approval 23.503 CR0753R1 (Rel-17, 'F'): The list of PSIs associated to an SNPN Ericsson, Deutsche Telekom Rel-17 Revision of S2-2208766r04. Approved Agreed
8.2 S2-2208768 DISCUSSION Decision Differentiation of subscribed/non-subscribed SNPN in CH architecture. Ericsson Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.2 S2-2208769 CR Approval 23.501 CR3731 (Rel-17, 'F'): Clarification when access SNPN using CH with AAA-S Ericsson Rel-17 r03 agreed. CC#3: r03 + changes agreed. Revised to S2-2209673. Josep (DT) is not sure whether introducing new terminology (subscribed/non-subscribed) improves clarity.
Rainer (Nokia) agrees with Josep (DT).
Peter Hedman (Ericsson) provides reply
Haris(Qualcomm) comments that the CR is not FASMO but if the majority prefer to do this clarification only option 2 is acceptable without the sentence: 'This is, the AUSF, UDM and NSSAAF in Figure 5.30.2.9.2-1 belong to the subscribed SNPN of the UE.' In NOTE 2
Josep (DT) is OK to add as many clarification NOTEs but not to change normative text.
Qianghua (Huawei) comments that the introduction of non-subscribed/subscribed SNPN in CH AAA-S case makes it hard to understand the architecture and doesn't see any benefits or necessities to do so
Chia-Lin (MediaTek) provides the comments and considers this is not a FASMO CR
Peter Hedman (Ericsson) provides r01
Saso (Intel) provides r02
Peter Hedman (Ericsson) ok with r02
Qianghua (Huawei) the terms 'subscribed/non-subscribed' still confuse me and doesn't match with the network selection logic, miss one case in the NOTE
Peter Hedman (Ericsson) provides comments and r03
==== Revisions Deadline ====
Qianghua (Huawei) asks further clarification.
Haris(Qualcomm) proposes changes on top of r03 to add next to SUPI privacy settings 'SUPI privacy settings (when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])'
Qianghua (Huawei) replies and can not live the NOTE as it is
Peter Hedman (Ericsson) provides replies and ok with QC suggestion i.e. r03 + '(when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])'
Qianghua (Huawei) that normative text applies for both 'subscribed SNPN' and 'non-subscribed SNPN' case.
==== Final Deadline ====
Qianghua (Huawei) proposes to make additional changes on the NOTE after offline discussion with Peter, i.e. r03 + '(when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29])' + 'same as corresponding NFs in the subscribed SNPN'
Antoine (Orange): The green addition is not clear.
Peter Hedman (Ericsson) provides reply to Antoine
Revised
8.2 S2-2209673 CR Approval 23.501 CR3731R1 (Rel-17, 'F'): Clarification when access SNPN using CH with AAA-S Ericsson Rel-17 Revision of S2-2208769r03 + changes. Approved Agreed
8.2 S2-2208839 CR Approval 23.501 CR3675R1 (Rel-17, 'F'): Alignment with SA WG3 agreement on usage of SUCI when CH is legacy AAA Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2205756 from S2#152E. CC#3: r05 agreed. Revised to S2-2209947. Peter Hedman (Ericsson) provides comments
Fei (OPPO) comments
Haris(Qualcomm) provides r01
Haris(Qualcomm) responds
Genadi (Lenovo) comments to r01.
Genadi (Lenovo) responds to Haris (Qualcomm).
Qianghua (Huawei) comments on the same point with Genadi
Genadi (Lenovo) agrees with the proposal by Qianghua (Huawei).
Chia-Lin (MediaTek) provides the comments on r01 and suggest to remove the change from clause 5.30.2.4.2
Peter Hedman (Ericsson) provides r02
Haris(Qualcomm) asks questions on r02
Haris(Qualcomm) provides r03
Fei (OPPO) comments and provides r04.
Chia-Lin (MediaTek) provides r05
Haris(Qualcomm) indicates that r05 is not acceptable
Peter Hedman (Ericsson) provides reply
Peter Hedman (Ericsson) provides reply and r05 is ok
Haris(Qualcomm) responds to Peter
==== Revisions Deadline ====
Haris(Qualcomm) can only accept r04, r03. Objects to r05, r02. R00 and R01 contain incorrect text
Chia-Lin (MediaTek) can only accept r05 and object all other versions including the original one
Fei (OPPO) can accept r04, r02, r05 and objects other revisions including r00.
Haris(Qualcomm) asks Chia-Lin (Mediatek) to clarify the objection to r04
Qianghua (Huawei) OK with r01, r02, r03, r04, r05. But not the original
Peter Hedman (Ericsson) provides reply that the note in 08769 clarifies that UDM handles the privacy as well i.e. the note is not needed in this CR
Chia-Lin (MediaTek) responds to Haris (Qualcomm)
==== Final Deadline ====
Revised
8.2 S2-2209947 CR Approval 23.501 CR3675R2 (Rel-17, 'F'): Alignment with SA WG3 agreement on usage of SUCI when CH is legacy AAA Qualcomm Incorporated Rel-17 Revision of S2-2208839r05. Approved Agreed
8.2 S2-2208935 CR Approval 23.501 CR3738 (Rel-17, 'F'): Clarification of SUPI for SNPN Huawei, HiSilicon Rel-17 Merged into (Covered by) S2-2208839 Peter Hedman (Ericsson) provides comments that changes looks ok, but we can only agree this or 08839.
Haris(Qualcomm) suggests to focus the discussion on S2-2208839
Qianghua (Huawei) OK to merge this into S2-2208839
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=18 -
8.3 S2-2208102 LS In Action LS from CT WG3: LS on handling of FQDN ranges in AF influence on traffic routing procedures CT WG3 (C3-222419) Rel-17 Revision of Postponed S2-2205396 from S2#152-e. Response drafted in S2-2208372. Final response in S2-2209269 Replied to
8.3 S2-2208372 LS OUT Approval [DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures Ericsson [to be SA2] Rel-17 Response to S2-2208102. r02 agreed. Revised to S2-2209269. Xinpeng(Huawei) replies to Yuan Tao (CATT).
Yuan Tao (CATT) asks Xinpeng(Huawei) for clarification on r01.
Xinpeng(Huawei) provides r01.
Yuan Tao (CATT) replies to Xinpeng(Huawei).
Shubhranshu (Nokia) comments
Jari (NTT DOCOMO) comments
Xinpeng(Huawei) replies to Jari (NTT DOCOMO).
Jari (NTT DOCOMO) replies to Xinpeng
Jari (NTT DOCOMO) responds to Xinpeng
Magnus H (Ericsson) comments.
Shubhranshu (Nokia) responds
Jari (NTT DOCOMO) prefers r01
Jari (NTT DOCOMO) responds to Magnus H
Shubhranshu (Nokia) proposes to agree r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.3 S2-2209269 LS OUT Approval Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures SA WG2 Rel-17 Revision of S2-2208372r02. Approved Approved
8.3 S2-2208160 LS In Information LS from SA WG6: Reply LS to OPAG_34_Doc_07_OPAG_LS ETSI-3GPP-Network integration SA WG6 (S6-222337) Rel-18 Noted Magnus O (Ericsson) proposes to Note this LS Noted
8.3 S2-2208162 LS In Action LS from SA WG6: Forward on S6-222332, LS on Network federation interface for Telco edge consideration SA WG6 (S6-222543) Rel-18 Postponed Magnus O (Ericsson) proposes to postpone this LS to the November meeting Postponed
8.3 S2-2208163 LS In Information LS from SA WG6: Reply LS on user’s consent for EDGEAPP SA WG6 (S6-222555) Rel-17 Response drafted in S2-2208373. Final response in S2-2209270 Replied to
8.3 S2-2208373 LS OUT Approval [DRAFT] Response LS on Clarifications for AF specific UE ID retrieval Ericsson [to be SA2] Rel-17 Response to S2-2208163. r00 agreed. Revised to S2-2209270. Jinsook (DISH) Question for clarification
Magnus (Ericsson) Provides answers
==== Revisions Deadline ====
Jinsook (DISH) Thanks for the clarification, further comment
==== Final Deadline ====
Revised
8.3 S2-2209270 LS OUT Approval Response LS on Clarifications for AF specific UE ID retrieval SA WG2 Rel-17 Revision of S2-2208373r00. Approved Approved
8.3 S2-2208164 LS In Information LS from SA WG6: Reply LS to Network federation interface for Telco edge consideration SA WG6 (S6-222557) Rel-18 Noted Noted
8.3 S2-2208368 CR Approval 23.501 CR3663R1 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Revision of (Postponed) S2-2205633 from S2#152E. r04 agreed. Revised to S2-2209271. Xinpeng(Huawei) provides r01.
Magnus H (Ericsson) comments and provides r02
Xinpeng(Huawei) provides r03.
Shubhranshu (Nokia) asks for clarification
Magnus H (Ericsson) this document should be under AI#6.6, could we please move. Sorry for the inconvenience.
Shubhranshu (Nokia) comments
Magnus H (Ericsson) comments.
Jari (NT DOCOMO) provides r04
Shubhranshu (Nokia) responds
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.3 S2-2209271 CR Approval 23.501 CR3663R2 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Revision of S2-2208368r04. Approved Agreed
8.3 S2-2208369 CR Approval 23.503 CR0732R1 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Revision of (Postponed) S2-2205635 from S2#152E. r01 agreed. Revised to S2-2209272. Xinpeng(Huawei) comments.
Magnus H (Ericsson) provides r01.
Shubhranshu (Nokia) comments
Magnus H (Ericsson) this document should be under AI#6.6, could we please move. Sorry for the inconvenience.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.3 S2-2209272 CR Approval 23.503 CR0732R2 (Rel-17, 'F'): Correction related to traffic correlation in PCC rule Ericsson Rel-17 Revision of S2-2208369r01. Approved Agreed
8.3 S2-2208370 CR Approval 23.501 CR3634R2 (Rel-17, 'F'): Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF Ericsson Rel-17 Revision of (Postponed) S2-2205629 from S2#152E. Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.3 S2-2208371 DISCUSSION Decision DP on role of PCC in authorization of EAS Discovery procedure with EASDF. Ericsson Rel-17 Noted Xinpeng(Huawei) proposes to note this DP paper.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.3 S2-2208576 CR Approval 23.548 CR0063 (Rel-17, 'F'): Clarifications for local event notification control Huawei, HiSilicon Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.3 S2-2209171 CR Approval 23.501 CR3751 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request Nokia, Nokia Shanghai Bell Rel-17 Postponed Tugce (NTT DOCOMO) comments and provides r01.
Jari (NTT DOCOMO) provides r02.
Xinpeng(Huawei) proposes merge 9171 into 8370.
Magnus H (Ericsson) agrees with Xinpeng that we should merge 9171 into 8370
Shubhranshu (Nokia) responds
Shubhranshu (Nokia) proposes NOT to merge
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Xinpeng(Huawei) responds to Shubhranshu (Nokia).
==== Revisions Deadline ====
Xinpeng(Huawei) proposes to note this paper.
Shubhranshu (Nokia) proposes to postpone this paper
Xinpeng(Huawei) is fine to postpone.
==== Final Deadline ====
Postponed
8.3 S2-2209172 CR Approval 23.503 CR0759 (Rel-17, 'F'): Correction to clarify uses of FQDN Range in the AF request Nokia, Nokia Shanghai Bell Rel-17 Postponed Xinpeng(Huawei): the result of 9172 depends on the discussion of 9171.
Jari (NTT DOCOMO) proposes to postpone
Shubhranshu (Nokia) OK to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=25 -
8.4 S2-2208116 LS In Information Reply LS on Support for managing slice for trusted third-party owned application SA WG1 (S1-222262) Rel-18 Revision of Postponed S2-2208097 from S2#152-e. Noted Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 Noted
8.4 S2-2208151 LS In Information LS from SA WG1: Reply LS on Support for managing slice for trusted third-party owned application SA WG1 (S1-222267) Rel-18 Noted Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 Noted
8.4 S2-2208161 LS In Information LS from SA WG6: Reply LS on Reply LS on Support for managing slice for trusted third-party owned application SA WG6 (S6-222340) Rel-18 Noted Jinguo(ZTE) proposes to note this LS in since there is no action for SA2 Noted
8.4 S2-2208107 LS In Action LS from SA WG3: LS on EAC Mode for NSAC SA WG3 (S3-221164) Rel-17 Revision of Postponed S2-2205437 from S2#152-e. Response drafted in S2-2208415. Final response in S2-2209260 Replied to
8.4 S2-2208415 LS OUT Approval [DRAFT] Reply LS on EAC Mode for NSAC Huawei, HiSilicon Rel-17 Response to S2-2208107. r00 agreed. Revised to S2-2209260. ==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.4 S2-2209260 LS OUT Approval LS Reply on EAC Mode for NSAC SA WG2 Rel-17 Revision of S2-2208415r00. Approved Approved
8.4 S2-2208416 CR Approval 23.502 CR3563 (Rel-17, 'F'): Clarification on EAC Mode for NSAC Huawei, HiSilicon, ZTE Rel-17 r02 agreed. Revised to S2-2209273. Haiyang (Huawei) provides r01
George Foti (Ericsson) provides comments
Stefano Faccin (Qualcomm) provides comments
Haiyang (Huawei) provides clarification
Dongeun (Samsung) comments
Haiyang (Huawei) provides clarification to Dongeun (Samsung)
alessio(Nokia) supports the comment(s) by Stefano. proposes to note this CR also at this meeting as it is not helping to address a FASMO issue so we cannot agree to it. SA3 can put a note in their specs if they see a need and can find consensus in SA3 on a logic to set a proper value that is secure.
Haiyang (Huawei) provides comments to Alessio (Nokia)
Haiyang (Huawei) provides r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.4 S2-2209273 CR Approval 23.502 CR3563R1 (Rel-17, 'F'): Clarification on EAC Mode for NSAC Huawei, HiSilicon, ZTE Rel-17 Revision of S2-2208416r02. Approved Agreed
8.4 S2-2209003 CR Approval 23.502 CR3592 (Rel-17, 'F'): Update in EAC mode procedure Samsung Rel-17 Noted Fenqin (Huawei) provides comments
George Foti (Ericsson) proposes to note the CR. Please see comments below.
Ashok (Samsung) responds to George (Ericsson) and Fenqin (Huawei)
George (Ericsson) provides answer. EAC follow the quota. This case is for 3GPP, then that's what it is applied for.
Ashok (Samsung) comments
Fenqin (Huawei) provides response
Ashok (Samsung) provides comments
Iskren (NEC) this CR should be noted as the quota is per UE, not per AT
Ashok (Samsung) responds to Iskren (NEC)
Fenqin (Huawei) reply to Ashok
Ashok (Samsung) clarifies to Fenqin
Jinguo(ZTE) comments
Fenqin (Huawei) provides a further comments
Ashok (Samsung) responds to Fenqin , Jinguo
alessio(Nokia) also agrees there is no FASMO. the worst case EAC is not activated for both access types.
Ashok (Samsung) ask a question to Alessio(Nokia)
Iskren (NEC) comments.
Ashok (Samsung) explains to Iskren
Alessio(Nokia) replies
Ashok (Samsung) responds to Alessio(Nokia)
George (Ericsson) provides response
George (Ericsson) The issue is understood and no action is required.
Ashok (Samsung) replies to Iskren
Ashok (Samsung) seeks a clarification from George
Ashok (Samsung) provides response to George (Ericsson)
Ashok (Samsung) comments to George
Iskren (NEC) answers Ashok (Samsung) replies to Iskren
Ashok (Samsung) replies to Iskren (NEC)
Iskren (NEC) replies to Ashok (Samsung)
==== Revisions Deadline ====
Fenqin (Huawei) suggest to note this paper.
Ashok (Samsung) agrees to NOTE the paper
==== Final Deadline ====
Noted
8.4 S2-2208103 LS In Action LS from CT WG1: LS on NSSRG restriction on pending NSSAI CT WG1 (C1-224073) Rel-17 Revision of Postponed S2-2205406 from S2#152-e. This LS was postponed Postponed
8.4 S2-2209037 LS OUT Approval [DRAFT] LS on NSSRG restriction on pending NSSAI NEC Rel-17 CC#3: r03 agreed. Revised to S2-2209944. Alessio(Nokia) provides r01 so it can be used in association with Nokia CRs.
Alessio(Nokia) provides r01 so it can be used in association with Nokia CRs. (sending zip file)
Alessio(Nokia) provides r01 clarifying that when NSSRG Info applies the Pending NSSAI cannot be blindly added to the Requested as (you may imagine) the requested and pending need not be compatible a priory.
Kundan (NEC) objects to r01. Nokia has wrong understanding of pending NSSAI. Pending NSSAI is implicit requested NSSAI according to CT1. If the UE is interested in the pending NSSAI but can't send it as a part of requested NSSAI due to CT1 design doesn't mean it is not requested NSSAI.
Ashok (Samsung) provides r02
Kundan(NEC) : r02 is very confusing and contradictory
alessio(nokia) comments CT1 has not a common understanding that is why they asked the question. even if they had the understanding the pending is always part of requested this is not correct as it violates the NSSRG feature when there is incompatibility with pending. it would be like mandating the allowed or rejected is always part of requested... (given that a pending S-NSSAI can be ultimately allowed or rejected).
Alessio(Nokia) also prefers to postpone to next meeting and have a call to discuss this important topi. r02 is to us going in the right direction logically but we need to create the right CR backing it so CT1 eventually does the right thing. And also we need to tell CT1 they have to remove in NSSRG context (i.e. for UEs for which NSSRG applies) the assumption that the pending is virtually part of requested as obviously when the Ue requests incompatible slices with a pending S-NSSAI this cannot be part of the requested.
==== Revisions Deadline ====
Kundan(NEC) provides r03 which is very much aligned with stage 2 and stage3.
Xiaowen(vivo) is ok to r03 and propose to go with r03, can live with r02.
Tao(VC) remind r03 is provided after revision deadline. Further check whether any version agreeable.
r03 is uploaded on the server within the time period. this is before 10/12 16:00 UTC.
alessio(nokia) suggest to note the LS as we will postpone the issue
nokia is not happy to send any LS till we have a stable state in SA2. this will not be till next meeting.
Peter Hedman (Ericsson) propose to send LS as delaying to next meeting means we probably delay the resolution in stage 3 to Q1 2023
Alessio(Nokia) LSs are sent when there is a clear way forward.
==== Final Deadline ====
Revised
8.4 S2-2209944 LS OUT Approval LS out on NSSRG restriction on pending NSSAI SA WG2 Rel-17 Revision of S2-2209037r03. Approved Approved
8.4 S2-2209038 LS OUT Approval [DRAFT] LS on NSSRG Restrictions on Pending NSSAI vivo Rel-17 Merged into (Covered by) S2-2209037 Haiyang (Huawei) suggests to discuss in 9037 thread
Jinguo(ZTE) suggest to merge this LS to 9037
Xiaowen (vivo) agrees to merge into 9037.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.4 S2-2209039 CR Approval 23.501 CR3744 (Rel-17, 'F'): NSSRG restriction on Pending NSSAI Vivo Rel-17 Noted Jinguo(ZTE) think this CR is not needed
Genadi (Lenovo) has concerns with the proposal.
Alessio(Nokia) also believes this is not the way forward to resolve the issue.
Peter Hedman (Ericsson) provides comments that a way forward without need for any indication is preferred
Xiaowen (vivo) provides responses.
Jinguo(ZTE) agree with others view
==== Revisions Deadline ====
Stefano (Qualcomm) assumes that based on the previous comments, this CR will be noted.
Peter Hedman (Ericsson) agree that CR should be noted
vivo confirm this CR can be noted.
==== Final Deadline ====
Noted
8.4 S2-2209040 CR Approval 23.502 CR3594 (Rel-17, 'F'): NSSRG restriction on Pending NSSAI Vivo Rel-17 Noted Jinguo(ZTE) think this CR is not needed
Alessio(Nokia) believes this is not the way forward to resolve the issue.
==== Revisions Deadline ====
Stefano (Qualcomm) assumes that based on the previous comments, this CR will be noted.
we should note this CR. as we don't need a separate indicator.
Peter Hedman (Ericsson) agree that CR should be noted
vivo confirm this CR can be noted.
==== Final Deadline ====
Noted
8.4 S2-2209201 CR Approval 23.501 CR3684R1 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2206152 from S2#152E. LATE DOC: Rx 03/10, 10:50. Postponed Peter Hedman (Ericsson) provides question if the late CR is part of the meeting?
Kundan (NEC) has same response as Peter. After the document submission deadline it was not in the tdoc list.
Kundan(NEC) also proposes to note this paper.
alessio(nokia) ... we believe that our CRs are consistent with current UE behaviour in NSSRG handling which is the same as if the S-NSSAI was allowed instead of pending. if we can request one S-NSSAI set incompatible with allowed NSSAI, we surely can request one S-NSSAI incompatible with a pending NSSAI. it is the network then that needs to check the compatibility of the pending with the allowed at time of NSSAA completion.
Kundan (NEC) pending NSSAI is considered as part of the requested NSSAI. so Nokia CR is against the current NSSRG principle.
Kundan(NEC): Nokia CR has a big drawback, it is always rejecting the pending NSSAI. what is the logic?
Alessio(Nokia) clarifies Kundan's doubt
alessio(Nokia) clarifies this was a network side behaviour predating the NSSRG introduction. this is no longer valid thereafter.
Kundan(NEC) further clarifies Alessio. According to stage 3, receiving incompatible slices at the network side is abnormal case.
Alessio(Nokia)replies that consistently with that the requested NSSAI is always made of compatible S-NSSAIs as we say.
Haiyang (Huawei) comments.
Kundan (NEC) has same understanding as Huawei that pending NSSAI is part of requested NSSAI should be compatible. we have reiterated earlier this also.
Kundan(NEC) indicates that the UE can still be interested in the pending NSSAI and an additional slice then the pending slice and new additional must be compatible.
Peter Hedman (Ericsson) provides comments and propose we move forward with CR in 09004
Ashok (Samsung) suggests a way forward
This CR suffers same issue Genadi raised. AMF will deny the service of most preferred slice for the UE.
Alessio(Nokia) comments
alessio(nokia) clarifies we are addressing the case here where the UE is no more interested in the pending NSSAI (as the whole discussion is what to do when the Pending s-NSSAI is incompatible with requested)
alessio(Nokia) is not in tune with the way forward proposed by Ashok(Samsung) as this is exactly the issue this CR wants to avoid (any blocking factor to requesting service)
alessio(Nokia) cannot see any relationship with the access type issue.
Kundan (NEC) commented that Nokia CR does not have statement that the UE is no more interested then ignore the pending NSSAI and send the new requested NSSAI. it has very generic statement to send the incompatible requested NSSAI even though the UE is interested. can you show me where it is mentioned that the UE is not interested pending NSSAI statement??
Stefano (Qualcomm) believes the original question has not been answered: this is a LATE CR and as such should not be discussed. If we allow it, then anyone under any WID will start injecting late CRs. This is not acceptable, sorry.
Alessio(Nokia) replies to Stefano (Qualcomm)
==== Revisions Deadline ====
Kundan (NEC) CR won't work when the UE is pending over one AMF and UE tries to register on another AMF and ignoring the pending NSSAI and sends the incompatible slices. how the two AMF can co-operate after NSSAA procedure is finished on one AMF? This solution doesn't work in many cases in addition to the case when the UE is registering over two AMFs.

I agree with Stefano this this CR shouldn't be treated at all due to late submission.
Kundan (NEC) indicates this CR won't work when the UE is pending over one AMF and UE tries to register on another AMF and ignoring the pending NSSAI and sends the incompatible slices. how the two AMF can co-operate after NSSAA procedure is finished on one AMF? This solution doesn't work in many cases in addition to the case when the UE is registering over two AMFs.

I agree with Stefano this this CR shouldn't be treated at all due to late submission.
alessio(Nokia) the statements below need to be discussed further in a DP as they are not clear. if the UE requests compatible slices set on both accesses both AMFs will react to pending consistently. so the issue is not clear and needs to be discussed
but I see ultimately the only argument left is the procedural one so let's postpone the issue
Peter Hedman (Ericsson) agree that CR should be noted and we can focus on NEC CR
Kundan (NEC) provides list of drawbacks of this solution.
alessio (Nokia) the issue is postponed then.
==== Final Deadline ====
Postponed
8.4 S2-2209202 CR Approval 23.502 CR3529R1 (Rel-17, 'F'): Clarification on Interaction between NSSAA and NSSRG Nokia, Nokia Shanghai Bell Rel-17 Revision of (Noted) S2-2206159 from S2#152E. LATE DOC: Rx 03/10, 10:50. Noted Peter Hedman (Ericsson) provides comments that we should move forward with CR in 9004 i.e. this CR can be noted.
==== Revisions Deadline ====
Kundan(NEC): this document should be noted. reasons are provided in 09201 thread.
==== Final Deadline ====
Noted
8.4 S2-2209004 CR Approval 23.501 CR3693R1 (Rel-17, 'F'): Pending NSSAI and NSSRG NEC, Ericsson, Huawei, HiSilicon, ZTE Rel-17 Revision of (Postponed) S2-2206644 from S2#152E. CC#3: r02 agreed. Revised to S2-2209943. Agree r02? Genadi (Lenovo) asks a question for clarification.
Alessio(Nokia) comments and asks this paper to be noted
Ashok (Samsung) comments
Peter Hedman (Ericsson) provides comments
Kundan(NEC) responds to Genadi.
Kundan (NEC) comments
Kundan(NEC) asks question to Genadi.
Haiyang (Huawei) provides r01
Genadi (Lenovo) comments to Kundan(NEC).
Genadi (Lenovo) replies to Kundan(NEC) that the NSSRG applies to Allowed NSSAI and the UE may have one Allowed NSSAI for AT1 and another Allowed NSSAI for AT2.
Kundan (NEC) the current specification 23.501 and 24.501 don't allow what you are saying. Please below in details.
Genadi (Lenovo) replies to Kundan (NEC).
Jinguo(ZTE) provides comment
Kundan (NEC) responds to Ashok.
Peter Hedman (Ericsson) provides comments and propose we move forward with this CR
Ashok (Samsung) suggests a way forward
Myungjune comments on way forward proposed by Ashok (Samsung)
Ashok (Samsung) responds to Myungjune
Alessio(Nokia) cannot accept any revision of this document where there is a concept the Ue needs to wait for NSSAA completion before requesting a new set of slices. we can only accept 9201 approach that is consistent with the behavior when the same S-NSSAI is allowed rather than pending...
alessio(Nokia) objects to the approach in this CR as it causes blocking obtaining service.
Alessio(Nokia) has problems with this paper being the basis as it is against established 3GPP principle to not delay or potentially block service as already stated, cannot live with this approach.
Alessio(Nokia) suggests to keep the discussion focused and not introduce AT distractions... the requested NSSAI is what matters and this is to be irrespective of the Pending NSSAI or allowed NSSAI.
Ulises Olvera (InterDigital Inc.) provides comments
Jinguo(ZTE) propose a compromise for R17
alessio(nokia) agrees with Ulises(Interdigital) that the only restriction is to ensure the requested NSSAI is made of mutually compatible S-NSSAIs ad we will object to this cR.
Peter Hedman (Ericsson) provides reply
Peter Hedman (Ericsson) provides reply to Nokia that we should maintain a consistent logic for NSSRG
Kundan (NEC) nothing against the 3GPP principle this is following 3GPP specification and GSMA requirement of NSSRG. aligned with stage 3 specification. Mutually exclusive services cannot be attained at the same time. one needs to be dropped.
Alessio(Nokia) UE requests compatible slices between themselves at all times. the AMF can allow a pending if compatible with allowed when NSSAA successfully completed, else it will remove from pending the S-NSSAI (if NSSAA does not fails otherwise it rejects the S-NSSAI). there is nothing to add. we have the CR that does this. I stop commenting on this subject as w already said the same thing too many times.
Nokia CRs has many issues already highlighted in that thread.
Ulises Olvera (InterDigital Inc.) provides reply
==== Revisions Deadline ====
Xiaowen (vivo) provides comments.
Kundan(NEC) provides r02. In this revision we have added a condition that UE shall apply the NSSRG rules with respect to pending NSSAI if the UE is interested which is very much aligned with CT1 specification.
Kundan(NEC) ask questions to Ulises to understand his comment further.
Ulises Olvera (InterDigital Inc.) provides answers to Kundan
Kundan (NEC) responds to Xiaowen.
Xiaowen (vivo) responds to Kundan.
Alessio(Nokia) comment: the fact stage 3 forgot to update this quoted text by kundan on Pnding NSSAI when NSSRG was introduced is undeniable. like we did forget to update our specs. so not sure we can refer to not updated text of CT1 after NSSRG was introduced to resolve this. SA2 anc TCT1 need to resolve the NSSAA and NSSRG feature interaction. we want to do it In a way that des NOT block the Ue to request new services like when the same S-NSSAI is allowed.
==== Final Deadline ====
Revised
8.4 S2-2209943 CR Approval 23.501 CR3693R2 (Rel-17, 'F'): Pending NSSAI and NSSRG NEC, Ericsson, Huawei, HiSilicon, ZTE Rel-17 Revision of S2-2209004r02. Approved Agreed
8.4 S2-2209022 CR Approval 23.501 CR3694R1 (Rel-17, 'F'): Pending NSSAI and AMF Relocation in Connected mode 23.501. NEC, Ericsson Rel-17 Revision of (Postponed) S2-2206652 from S2#152E. Approved. CC#3: This was postponed. ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
8.4 S2-2208545 CR Approval 23.501 CR3682R1 (Rel-17, 'F'): UE-Slice-MBR exemption for priority services Samsung Rel-17 Revision of (Postponed) S2-2206034 from S2#152E. CC#3: Postponed Belen (Ericsson) provides r01
Jinguo(ZTE) provides comment
Dongeun (Samsung) replies to Jinguo (ZTE)
Dongeun (Samsung) replies to Belen (Ericsson)
Haiyang (Huawei) suggests to note this paper
Dongeun (Samsung) disagrees to Haiyang (Huawei)
Haiyang (Huawei) provides feedback
Jinguo(ZTE) replies to Dongeun
Dongeun (Samsung) replies to Haiyang (Huawei) and Jinguo (ZTE)
Belen (Ericsson) provides comments
Dongeun (Samsung) provides r02
alessio(Nokia) comments
Belen (Ericsson) provides comments, replies to Samsung as well.
Dongeun (Samsung) replies to Belen (Ericsson) and provide r04
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
8.4 - - - Documents exceeding TU Budget - - Docs:=4 -
8.4 S2-2208470 CR Approval 23.501 CR3717 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area NEC Rel-17 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
8.4 S2-2208471 CR Approval 23.502 CR3568 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area NEC Rel-17 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
8.4 S2-2208521 CR Approval 23.503 CR0748 (Rel-17, 'F'): AMF provides Target NSSAIs for all TAI in the Registration Area NEC Rel-17 Not Handled Mirko (Huawei) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
8.4 S2-2208969 CR Approval 23.501 CR3741 (Rel-17, 'F'): Correction to the Target NSSAI feature in RRC redirection NEC Rel-17 Not Handled Jinguo(ZTE) comments this CR is not handled.
Stefano Faccin (Qualcomm) has questions for clarification and concerns
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=7 -
8.5 S2-2208553 CR Approval 23.502 CR3573 (Rel-17, 'F'): Clarification on time synchronization error budget provisioning and ASTI management Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2209569. Shabnam (Ericsson) provides comments regarding if this is FASMO, if we are to proceed the following comments apply
Devaki (Nokia) provides r01 - believes it is a FASMO as current stage 2 has some inconsistencies resulting in ambiguity for stage 3 and implementation.
Shabnam (Ericsson) provides comments to remove RAN impacts on cover sheet as there is none, if others don't have any issue on FASMO, I can live with the CR ??
==== Revisions Deadline ====
Devaki (Nokia) comments that we will remove the RAN impacts from cover page of the final uploaded version of the CR. Thanks!
==== Final Deadline ====
Revised
8.5 S2-2209569 CR Approval 23.502 CR3573R1 (Rel-17, 'F'): Clarification on time synchronization error budget provisioning and ASTI management Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2208553r01. Approved Agreed
8.5 S2-2208578 CR Approval 23.502 CR3527R1 (Rel-17, 'F'): Alignment of IIoT related parameter description Huawei, HiSilicon Rel-17 Revision of (Noted) S2-2206052 from S2#152E. r01 agreed. Revised to S2-2209570, merging S2-2208947 Jari (NTT DOCOMO) comments
Mirko (Huawei) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.5 S2-2209570 CR Approval 23.502 CR3527R2 (Rel-17, 'F'): Alignment of IIoT related parameter description Huawei, HiSilicon, ZTE, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2208578r01, merging S2-2208947. Approved Agreed
8.5 S2-2208936 CR Approval 23.502 CR3589 (Rel-17, 'F'): Adding SUPI in BSF-DISCOVER output Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Approved Saso (Intel) provides r01 and cosigns.
Devaki (Nokia) comments on r01 (moving all Mandatory parameters to be optional would have backward compatibility issues?)
Qianghua (Huawei) provides comments
Qianghua (Huawei) provides r02
Shabnam (Ericsson) provides comments isn't this approach too drastic and contradictory to what we usually do?
Qianghua (Huawei) agrees with Shabnam and prefers the original.
Saso (Intel) withdraws r01; ok with r00.
==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.5 S2-2208522 CR Approval 23.502 CR3570 (Rel-17, 'F'): Correction to BSF service description Samsung Rel-17 Merged into (Covered by) S2-2208936 Shabnam (Ericsson) proposes to take 8936 as the basis and consider this merged.
Sang-Jun (Samsung) confirms 8522 is merged into 8936.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.5 S2-2208947 CR Approval 23.502 CR3590 (Rel-17, 'F'): Clarification on the AF request Qos procedure. ZTE Rel-17 Merged into S2-2209570 Mirko (Huawei) suggests to merge this CR into S2-2208578r01.
zhendong (ZTE) confirm the merge proposal
==== Revisions Deadline ====
==== Final Deadline ====
Merged
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:=9 -
8.7 S2-2208104 LS In Action LS from CT WG4: LS on UAV authorization container CT WG4 (C4-223513) Rel-17 Revision of Postponed S2-2205417 from S2#152-e. Response drafted in S2-2208295. Final response in S2-2209274 Replied to
8.7 S2-2208295 LS OUT Approval [DRAFT] Reply LS on UAV authorization container Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2208104. r07 agreed. Revised to S2-2209274. Stefano Faccin (Qualcomm) expresses concerns and proposes R01
Pallab (Nokia) comments on R01
Ashok (Samsung) comments
Stefano Faccin (Qualcomm) disagrees
Shabnam (Ericsson) provides comments
Stefano Faccin (Qualcomm) comments
Guanglei (Huawei) provides comments and r02 based on r01
Ashok (Samsung) seeks clarification
Pallab (Nokia) comments and provides R03
Guanzhou (InterDigital) can't accept r03.
Stefano Faccin (Qualcomm) provides R04
Shabnam (Ericsson) provides comments on the wording see below
Pallab (Nokia) responds to Stefano Faccin (Qualcomm)
Pallab (Nokia) responds to Shabnam (Ericsson)
Shabnam (Ericsson) provides r05
Stefano (Qualcomm) agrees and provides R06 to improve readability.
Shabnam (Ericsson) provides comments that maybe there is misunderstanding I understood that payload availability is NOT up to stage 3 since it will be part of the function of the USS/UAS NF and will be forwarded, the only aspect left is payload type is needed or not and that we leave to stage 3. Did I misunderstand that?
Stefano (Qualcomm) agrees and provides R07.
Pallab (Nokia) is OK with r07
Ashok (Samsung) also fine with r07
Guanzhou (InterDigital) is OK with r07.
==== Revisions Deadline ====
Guanglei (Huawei) is Ok with r07
==== Final Deadline ====
Revised
8.7 S2-2209274 LS OUT Approval Reply LS on UAV authorization container SA WG2 Rel-17 Revision of S2-2208295r07. Approved Approved
8.7 S2-2208137 LS In Action LS from CT WG4: LS on Indication of Network Assisted Positioning method CT WG4 (C4-224626) Rel-17 Postponed Guanglei (Huawei) comments the corresponding Ls reply is 8744, discussed in 8.14 Postponed
8.7 S2-2208296 CR Approval 23.256 CR0068 (Rel-17, 'F'): Corrections to functionality and procedure at UAS NF for C2 authorization Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Postponed Guanglei (Huawei) comments.
Guanzhou (InterDigital) comments and provides r01
Stefano Faccin (Qualcomm) expresses concerns
Pallab (Nokia) comments and provide r02
Guanzhou (InterDigital) responds to Pallab (Nokia) and can't accept r02.
Pallab (Nokia) comments and provide r03 and r04. Prefers r04
Guanzhou (InterDigital) provides r05.
Shabnam (Ericsson) provides comments that we can not accept r05 and comments on proposal
Guanzhou (InterDigital) responds to Shabnam (Ericsson).
Shabnam (Ericsson) provides comments that the case we are trying to address and CT1 spec in our view needs to be updated and aligned with stage 2 and CT4 discussion.
Pallab (Nokia) responds to Guanzhou (InterDigital)
Stefano (Qualcomm) asks for clarification on what revision might be acceptable. We see technical concerns with all.
Pallab (Nokia) is OK to postpone the CR if there is no agreeable revision
Guanzhou (InterDigital) also thinks the CR should be postponed.
Shabnam (Ericsson) ok to postpone but we need to come back to this and correct stage 2 consistency, we don't want Rel-18 to be built on misleading text.
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
8.7 S2-2208843 CR Approval 23.256 CR0070 (Rel-17, 'F'): Aerial Subscription Update Samsung Rel-17 r03 agreed. Revised to S2-2209275. Guanglei (Huawei) comments.
Shabnam (Ericsson) provides comments regarding potential alternative solns and Objects to current approach in these CRs as not suitable for the subscription handling.
Ashok (Samsung) comments.
Ashok (Samsung) provides r01.
Dimitris (Lenovo) has a question for clarification
Ashok (Samsung) responds to Dimitris (Lenovo)
Stefano (Qualcomm) responds to Ashok (Samsung)
Stefano (Qualcomm) asks question for clarification.
Ashok (Samsung) agrees to Stefano (Qualcomm) comment and removed the NOTE and provides r02
Ashok (Samsung) provides r03
Shabnam (Ericsson) provides comments , thanks we would be ok and please also update 23.502 and correct one UCU left
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.7 S2-2209275 CR Approval 23.256 CR0070R1 (Rel-17, 'F'): Aerial Subscription Update Samsung Rel-17 Revision of S2-2208843r03. Approved Agreed
8.7 S2-2208866 CR Approval 23.502 CR3586 (Rel-17, 'F'): Aerial Subscription Update Samsung Rel-17 r01 agreed. Revised to S2-2209276. Shabnam (Ericsson) provides comments to follow potential soln option as indicated in the thread of document 8843 and objects to the soln in this CR
Ashok (Samsung) provides r01 which is inline with 8843 paper discussion
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.7 S2-2209276 CR Approval 23.502 CR3586R1 (Rel-17, 'F'): Aerial Subscription Update Samsung Rel-17 Revision of S2-2208866r01. Approved Agreed
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=27 -
8.8 - - - Discovery message cast type - - Docs:=6 -
8.8 S2-2208106 LS In Action LS from RAN WG2: LS on Cast Type for Discovery message RAN WG2 (R2-2206391) Rel-17 Revision of Postponed S2-2205424 from S2#152-e. Responses drafted in S2-2208515, S2-2209064. Final response in S2-2209277 Replied to
8.8 S2-2208515 LS OUT Approval [DRAFT] Reply LS on Cast Type for Discovery message OPPO Rel-17 Revision of (Noted) S2-2205994 from S2#152E. Response to S2-2208106. Noted Hannu (Nokia) proposes to note this LS and to proceed as suggested in S2-2209064 which is better aligned with the existing SA2 specifications.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 S2-2209064 LS OUT Approval [DRAFT] Reply LS on Cast Type for Discovery message Qualcomm Incorporated Rel-17 Response to S2-2208106. r03 agreed. Revised to S2-2209277. Fei (OPPO) comments and provides r01.
Hannu (Nokia) provides r02.
Fei (OPPO) comments and provides r03.
==== Revisions Deadline ====
Hannu (Nokia) thanks Fei for the update and supports r03.
==== Final Deadline ====
Revised
8.8 S2-2209277 LS OUT Approval Reply LS on Cast Type for Discovery message SA WG2 Rel-17 Revision of S2-2209064r03. Approved Approved
8.8 S2-2208513 DISCUSSION Discussion Cast type for direct discovery. OPPO Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 S2-2208514 CR Approval 23.304 CR0108R1 (Rel-17, 'F'): Cast Type for Discovery message OPPO Rel-17 Revision of (Noted) S2-2205993 from S2#152E. Noted Hannu (Nokia) proposes to note the document as there is neither requirement nor criteria for the upper layers to determine the cast type.
Fei (OPPO) responds to Hannu (Nokia)
Hong (Qualcomm) proposes to NOTE the CR.
Hannu (Nokia) shares the view of Hong that SA2 hasn't got any requirement but only a question from RAN2 in their LS and we need to reply based on our specifications.
Sudeep (Apple) agrees with Hannu (Nokia) and Hong (Qualcomm) and proposes to NOTE this CR.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 - - - 5G DDNMF discovery - - Docs:=4 -
8.8 S2-2208122 LS In Action LS from CT WG1: LS on 5G DDNMF discovery CT WG1 (C1-225229) Rel-17 Response drafted in S2-2208600. Final response in S2-2209261 Replied to
8.8 S2-2208600 LS OUT Approval [DRAFT] Reply LS on 5G DDNMF Discovery ZTE Rel-17 Response to S2-2208122. r00 agreed. Revised to S2-2209261. ==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.8 S2-2209261 LS OUT Approval Reply LS on 5G DDNMF Discovery SA WG2 Rel-17 Revision of S2-2208600r00. Approved Approved
8.8 S2-2208599 CR Approval 23.304 CR0119 (Rel-17, 'F'): Add 5G DDNMF Address in Parameter Provisioning for 5G ProSe Direct Discovery ZTE, Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.8 - - - Policy request during registration procedure - - Docs:=7 -
8.8 S2-2208128 LS In Action LS from CT WG1: LS on V2X policy or ProSe policy request during registration procedure CT WG1 (C1-225451) Rel-17 Responses drafted in S2-2208355, S2-2208700. Postponed Postponed
8.8 S2-2208355 LS OUT Approval [DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure LG Electronics Rel-17 Response to S2-2208128. Noted Susan (Huawei) proposes to either merge this draft LS to S2-2208700 or note this paper .
Hong (Qualcomm) replies to Susan.
Susan (Huawei) replies to Hong (Qualcomm).
Hannu (Nokia) asks whether we are discussing the removal of the Rel-17 requirement or including it in Rel-18?
==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 S2-2208700 LS OUT Approval [DRAFT] Reply LS on V2X policy or ProSe policy request during registration procedure Huawei, HiSilicon Response to S2-2208128. Noted LaeYoung (LGE) thinks that this LS may be not needed depending on the discussion outcome for 8356/8357.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 S2-2208356 CR Approval 23.503 CR0743 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE Rel-17 Postponed Susan (Huawei) provides r01.
Hannu (Nokia) supports r01. The cover page update is needed as in the absence of any Rel-18 TS version, we can only decide on Rel-17 in this meeting.
Judy (Ericsson) responds to Hannu (Nokia) and Susan (Huawei) and provides r02.
Hong (Qualcomm) objects r01.
Judy (Ericsson) provides r03 (please ignore r02)
Sherry (Xiaomi) comments.
Hannu (Nokia) asks whether we can postpone this Rel-17 proposal until Rel-18 TS version exists?
==== Revisions Deadline ====
LaeYoung (LGE) proposes to get this CR POSTPONED because 8357 covering same topic (so coupled together) is postponed.
Judy (Ericsson) agrees to postpone this CR until TS spec for Rel-18 is available
Hannu (Nokia) adds the comment for the minutes that SA2 did not challenge the applicability of this CR to Rel-17. The CR is postponed to allow us apply it only on Rel-17 without impacting Rel-18.
==== Final Deadline ====
Postponed
8.8 S2-2208357 CR Approval 23.304 CR0115 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure Ericsson, LG Electronics, CATT, Huawei, ZTE Rel-17 Postponed Susan (Huawei) provides r01.
Hannu (Nokia) supports r01 as in the absence of any Rel-18 TS, we can't decide on Rel-18 yet.
Hong (Qualcomm) objects to r01.
Judy (Ericsson) provides r02 to allow the work to be continued in Rel-18
Hong (Qualcomm) is fine with r02.
Hannu (Nokia) proposes to postpone the CR on the grounds explained in S2-2208356 discussion thread.
Judy (Ericsson) responds to Hannu (Nokia) and OK to postpone
==== Revisions Deadline ====
Hannu (Nokia) adds the comment for the minutes that SA2 did not challenge the applicability of this CR to Rel-17. The CR is postponed to allow us apply it only on Rel-17 without impacting Rel-18.
==== Final Deadline ====
Postponed
8.8 S2-2208482 CR Approval 23.304 CR0116 (Rel-17, 'F'): Removal of ProSe policy request during registration procedure CATT Rel-17 Merged into (Covered by) S2-2208357 Deng Qiang (CATT) this paper can be merged into S2-2208357.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.8 S2-2208483 CR Approval 23.503 CR0747 (Rel-17, 'F'): Removal of V2X/ProSe policy request during registration procedure CATT Rel-17 Merged into (Covered by) S2-2208356 Deng Qiang (CATT) this paper can be merged into S2-2208356.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.8 - - - RRC estbl cause - - Docs:=1 -
8.8 S2-2208129 LS In Information LS from CT WG1: LS on setting RRC establishment cause value when relay UE has its own service CT WG1 (C1-225453) Rel-17 Noted Deng Qiang (CATT) this LS In is for information and can be noted. Noted
8.8 - - - Secondary authentication - - Docs:=3 -
8.8 S2-2208153 LS In Information LS from SA WG3: LS Reply on Reply LS on 5G ProSe security open items SA WG3 (S3-222434) Rel-17 Response drafted in S2-2208359. Postponed Postponed
8.8 S2-2208359 LS OUT Approval [DRAFT] Reply to 5G ProSe security open items Ericsson Rel-17 Response to S2-2208153. Noted Hannu (Nokia) has got concerns on SA2 telling SA3 what kind of security work they can do. Asking technical questions is of course fine.
Judy (Ericsson) provides r01
Steve (Huawei) comments
Jungje (Interdigital) comments
Judy (Ericsson) responds to Steve (Huawei) and Jungje (Interdigital)
Jungje(Interdigital) comments Judy (Ericsson)
Hannu (Nokia) is concerned that the LS is not asking SA3 guidance on SA2 specifications but micro-managing SA3 work from SA2.
Judy (Ericsson) responds to Jungje(Interdigital) that SA2 is in To but not CCed, and responds to Hannu (Nokia) that inclusion of the draft CR in SA3 LS is for feedback if any and as such no micro managing other WGs work
Hong (Qualcomm) comments.
Jungje(Interdigital) responds to Judy (Ericsson)
Fei (OPPO) comments and provides r02.
Judy (Ericsson) provides r03 with wording update
Jungje(Interdigital) responds Judy(Ericsson)
==== Revisions Deadline ====
Jungje (Interdigital) responds to Judy(Ericsson) and propose to note. Oppose to original and any version.
Judy (Ericsson) responds to Jungje (Interdigital)
==== Final Deadline ====
Noted
8.8 S2-2208358 DISCUSSION Decision Discussion of 5G ProSe security open item for L3 Remote UE's secondary AA. Ericsson Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.8 - - - Corrections - - Docs:=6 -
8.8 S2-2208516 CR Approval 23.304 CR0117 (Rel-17, 'F'): Clarification on DCR message for DRX OPPO Rel-17 Merged into S2-2209279 LaeYoung (LGE) replies to Fei (OPPO).
Fei (OPPO) responds to LaeYoung (LGE)
LaeYoung (LGE) comments and proposes to MERGE this CR to S2-2208581.
Hong (Qualcomm) comments and also thinks separate TX Profile for DCR is not needed.
Hannu (Nokia) supports the proposed merging of this document to S2-2208581.
Fei (OPPO) responds and fine to NOTE/merge this CR.
LaeYoung (LGE) replies to Fei (OPPO), Hannu (Nokia) and Hong (Qualcomm).
Wen (vivo) replies.
Hong (Qualcomm) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.8 S2-2208581 CR Approval 23.304 CR0118 (Rel-17, 'F'): Clarifications on PC5 DRX operations Vivo, LG Electronics Rel-17 r01 agreed. Revised to S2-2209279, merging S2-2208516 Fei (OPPO) provides r01
LaeYoung (LGE) is OK with r01.
Hannu (Nokia) supports r01 and considers it reasonable to call the other paper as merged to this one.
==== Revisions Deadline ====
Wen (vivo) is OK with r01.
==== Final Deadline ====
Revised
8.8 S2-2209279 CR Approval 23.304 CR0118R1 (Rel-17, 'F'): Clarifications on PC5 DRX operations Vivo, LG Electronics Rel-17 Revision of S2-2208581r01, merging S2-2208516. Approved Agreed
8.8 S2-2208908 CR Approval 23.304 CR0120 (Rel-17, 'F'): Correction on PC5 link release indication Huawei, HiSilicon, vivo Rel-17 r01 agreed. Revised to S2-2209280. Judy (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.8 S2-2209280 CR Approval 23.304 CR0120R1 (Rel-17, 'F'): Correction on PC5 link release indication Huawei, HiSilicon, vivo Rel-17 Revision of S2-2208908r01. Approved Agreed
8.8 S2-2209138 CR Approval 23.304 CR0121 (Rel-18, 'F'): Updates to Control Plane based security procedures for 5G ProSe UE-to-Network Relay Xiaomi Rel-18 CR Number missing! Noted Judy (Ericsson) comments
Judy (Ericsson) provides r01
Fei (OPPO) comments.
Steve (Huawei) Some small hiccup, the comment from Judy is not about S2-2209138.
Steve (Huawei) comments
Judy (Ericsson) thanks Steve (Huawei) and corrects that no revison is provided to 9138.
Sherry (Xiaomi) replies, and proposes to send a LS to SA3 to confirm whether both user plane based solution and control based solution are supported for 5G ProSe discovery.
Sherry (Xiaomi) proposes to send a LS to SA3 to confirm whether 5G ProSe relay discovery security have two options of user plane based solution and control based solution.
Deng Qiang (CATT) comments.
Fei (OPPO) provides comments.
==== Revisions Deadline ====
Deng Qiang (CATT) think this CR should be NOTED.
==== Final Deadline ====
Noted
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=40 -
8.9 - - - 5MBS User Services - - Docs:=9 -
8.9 S2-2208108 LS In Action LS from SA WG4: Reply LS on 5MBS User Services SA WG4 (S4-220828) Rel-17 Revision of Postponed S2-2205450 from S2#152-e. Responses drafted in S2-2208329, S2-2208720. Final response in S2-2209281 Replied to
8.9 S2-2208329 LS OUT Approval [DRAFT] Reply LS on 5MBS User Services Ericsson, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2208108. r02 agreed. Revised to S2-2209281, merging S2-2208720 Robbie (Ericsson) clarifies to LiMeng (Huawei).
LiMeng (Huawei) comments and provides r01
Miguel (Qualcomm) comments
Robbie (Ericsson) provides r02.
Peng Tan (TELUS) request clarification and put further comments on r02
Robbie (Ericsson) replies to Peng Tan (TELUS).
==== Revisions Deadline ====
Peng Tan (TELUS) provides further comments
Peng (TELUS) replies to Robbie (Ericsson)
==== Final Deadline ====
Revised
8.9 S2-2209281 LS OUT Approval Reply LS on 5MBS User Services SA WG2 Rel-17 Revision of S2-2208329r02, merging S2-2208720. Approved Approved
8.9 S2-2208951 CR Approval 23.247 CR0129R1 (Rel-17, 'F'): Clarification on the traffic handling in MBSTF for interworking ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm Rel-17 Revision of (Postponed) S2-2206206 from S2#152E. CR Revision incorrect: -1! r04 agreed. Revised to S2-2209282. LiMeng (Huawei) provides r01
Miguel (Qualcomm) responds to LiMeng (Huawei) finds no merit for r01, supports r00
Thomas(Nokia) raises concerns against r01
zhendong (ZTE) share the similar view with qualcomm and nokia
Robbie (Ericsson) prefers r00.
LiMeng (Huawei) responds and provides r02.
zhendong (ZTE) provides r03
Robbie (Ericsson) provides r04.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209282 CR Approval 23.247 CR0129R2 (Rel-17, 'F'): Clarification on the traffic handling in MBSTF for interworking ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm Rel-17 Revision of S2-2208951r04. Approved Agreed
8.9 S2-2208720 LS OUT Approval [DRAFT] Reply LS on MBS user service Huawei, HiSilicon Rel-17 Response to S2-2208108. Merged into S2-2209281 LiMeng (Huawei) is fine use the email thread of S2-2208329 for discussions
Thomas (Nokia) suggest to use S2-2208329 as basis for discussions
Robbie (Ericsson) suggests marking it as merged into S2-2208329
LiMeng (Huawei) agrees to merge this document into S2-2208329
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 S2-2208718 DISCUSSION Discussion Discussion on MBS user service. Huawei, HiSilicon Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.9 S2-2208115 LS In Information LS on modifications to MBS User Services architecture SA WG4 (S4-221119) Rel-17 Revision of Postponed S2-2208096 from S2#152-e. Noted Robbie (Ericsson) suggests marking it as NOTED Noted
8.9 S2-2208131 LS In Information LS from CT WG3: Reply LS on 5MBS User Services CT WG3 (C3-224655) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED Noted
8.9 - - - Multicast MBS session Deactivation and Reactivation - - Docs:=8 -
8.9 S2-2208136 LS In Action LS from CT WG4: LS on Multicast MBS session Deactivation and Reactivation CT WG4 (C4-224417) Rel-17 Responses drafted in S2-2208201, S2-2208328, S2-2208897. Final response in S2-2209283 Robbie (Ericsson) provides comments
Fenqin (Huawei) provides comments
Thomas (Nokia) suggest this thread as basis for discussions
Thomas (Nokia) replies to Fenqin
Fenqin (Huawei) provides feedback
Thomas(Nokia) replies to Fenqin
Fenqin (Huawei) replies to Thomas
Fenqin (Huawei) further replies to Thomas
Thomas(Nokia) replies to Robbie
Robbie (Ericsson) replies to Thomas(Nokia)
Fenqin (Huawei) replies to Thomas(Nokia)
Replied to
8.9 S2-2208201 LS OUT Approval [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation Nokia, Nokia Shanghai-Bell Rel-17 Response to S2-2208136. Merged into S2-2209283 Fenqin (Huawei) suggest to merge this LS to 8897 and take 8897 as base line.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 S2-2208328 LS OUT Approval [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation Ericsson Rel-17 Response to S2-2208136. Merged into S2-2209283 Fenqin (Huawei) suggest to merge this LS to 8897 and take 8897 as base line.
Robbie (Ericsson) confirms it is merged into 8897.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 S2-2208897 LS OUT Approval [DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation Huawei, HiSilicon Rel-17 Response to S2-2208136. r04 agreed. Revised to S2-2209283, merging S2-2208201 and S2-2208328 Fenqin (Huawei) provides r01
Thomas (Nokia) provides r02
Fenqin (Huawei) provides r03
Robbie (Ericsson) provides r04
Fenqin (Huawei) is fine with r04
Thomas (Nokia) is fine with r04
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209283 LS OUT Approval Reply LS on Multicast MBS session Deactivation and Reactivation SA WG2 Rel-17 Revision of S2-2208897r04, merging S2-2208201 and S2-2208328. Approved Approved
8.9 S2-2208200 CR Approval 23.247 CR0134 (Rel-17, 'F'): Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation Nokia, Nokia Shanghai-Bell Rel-17 r07 agreed. Revised to S2-2209284, merging S2-2208331 Thomas (Nokia) provides r01 to capture results of offline discussions
Robbie (Ericsson) provides r02, merge in S2-2208331
Thomas (Nokia) provides r03
Fenqin (Huawei) provides r04
Robbie (Ericsson) provides r05
Thomas (Nokia) is fine with r04
zhendong (ZTE) is fine with r04
Fenqin (Huawei) is not ok with r05 and provide r06.
Youngkyo(Samsung) provides a comment.
Robbie (Ericsson) provides r07, including the comments from Youngkyo(Samsung).
Fenqin (Huawei) provide response to Youngkyo.
Robbie (Ericsson) replies to Fenqin (Huawei).
Thomas (Nokia) can accept r07
==== Revisions Deadline ====
Fenqin (Huawei) we are fine with r07
==== Final Deadline ====
Revised
8.9 S2-2209284 CR Approval 23.247 CR0134R1 (Rel-17, 'F'): Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation Nokia, Nokia Shanghai-Bell, Ericsson, Huawei Rel-17 Revision of S2-2208200r07, merging S2-2208331. Approved Agreed
8.9 S2-2208331 CR Approval 23.247 CR0136 (Rel-17, 'F'): Clarification on MBS session activation and deactivation Ericsson Rel-17 Merged into S2-2209284 Thomas (Nokia) suggest to consider this CR as merged into S2-2208200
Robbie (Ericsson) confirms this CR is merged into S2-2208200
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 - - - shared NG-U Termination among gNBs - - Docs:=8 -
8.9 S2-2208148 LS In Information LS from RAN WG3: LS on shared NG-U Termination among gNBs RAN WG3 (R3-225247) Rel-17 Responses drafted in S2-2208722, S2-2208950. Final response in S2-2209285 Replied to
8.9 S2-2208722 LS OUT Approval [DRAFT] Reply LS on Common CU-UP Huawei, HiSilicon Rel-17 Response to S2-2208148. Merged into S2-2209285 Thomas (Nokia) suggest to merge into S2-2208950
LiMeng (Huawei) is fine with the merging proposal.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 S2-2208950 LS OUT Approval [DRAFT] Reply LS on shared NG-U Termination among gNBs ZTE Rel-17 Response to S2-2208148. r03 agreed. Revised to S2-2209285, merging S2-2208722 Fenqin (Huawei) provides the r01
zhendong (ZTE) provides r02
Robbie (Ericsson) provides r03
zhendong (ZTE) provides the response
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209285 LS OUT Approval Reply LS on shared NG-U Termination among gNBs SA WG2 Rel-17 Revision of S2-2208950r03, merging S2-2208722. Approved Approved
8.9 S2-2208721 DISCUSSION Discussion Discussion on the issue of shared NG-U Termination among gNBs. Huawei, HiSilicon Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.9 S2-2208948 DISCUSSION Discussion Discussion on the common UP issue raised by RAN WG3 for shared delivery establishment management. ZTE Rel-17 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
8.9 S2-2208949 CR Approval 23.247 CR0141 (Rel-17, 'F'): Clarification on the shared delivery tunnel management for common gNB UP case ZTE Rel-17 r10 agreed. Revised to S2-2209286. zhendong (ZTE) provides the response
zhendong (ZTE) comments
Robbie (Ericsson) provides r02
Thomas (Nokia) provides r01
Fenqin (Huawei) provides the comment and r03
Thomas (Nokia) provides r04 and raises concerns against r03
Thomas (Nokia) provides r05 as alternative to r04
Prefers r04 but can also accept r05
Fenqin(Huawei) provides r06
zhendong (ZTE) provides r07
Robbie (Ericsson) provides r08.
Fenqin(Huawei) is fine with r08
zhendong (ZTE) reply to robbie(Ericsson)
Robbie (Ericsson) replies to zhendong (ZTE)
Thomas (Nokia) provides r09, raises concerns about r08
Robbie (Ericsson) provides r10
Thomas (Nokia) is fine with r10
Fenqin(Huawei) is fine with r10
zhendong (ZTE) is fine with r10
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209286 CR Approval 23.247 CR0141R1 (Rel-17, 'F'): Clarification on the shared delivery tunnel management for common gNB UP case ZTE, Nokia, Nokia Shanghai-Bell, Ericsson, Huawei Rel-17 Revision of S2-2208949r10. Approved Agreed
8.9 - - - Other LSs - - Docs:=6 -
8.9 S2-2208152 LS In Action LS from SA WG3: Reply LS on the impact of MSK update on MBS multicast session update procedure SA WG3 (S3-222391) Rel-17 Response drafted in S2-2208327. Final response in S2-2209287 Replied to
8.9 S2-2208327 LS OUT Approval [DRAFT] Reply LS on the impact of MSK update on MBS multicast session update procedure Ericsson Rel-17 Response to S2-2208152. r01 agreed. Revised to S2-2209287. Fenqin (Huawei) provides r01
Robbie (Ericsson) is fine with r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209287 LS OUT Approval Reply LS on the impact of MSK update on MBS multicast session update procedure SA WG2 Rel-17 Revision of S2-2208327r01. Approved Approved
8.9 S2-2208124 LS In Information LS from CT WG1: Reply LS on AS-NAS layer interactions for MBS CT WG1 (C1-225249) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED Noted
8.9 S2-2208141 LS In Information LS from RAN WG2: Reply LS on the MBS broadcast service continuity and MBS session identification RAN WG2 (R2-2208885) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED Noted
8.9 S2-2208146 LS In Information LS from RAN WG3: Response LS on Support of Broadcast and Multicast MBS sessions with AMF Set RAN WG3 (R3-225165) Rel-17 Noted Robbie (Ericsson) suggests marking it as NOTED Noted
8.9 - - - CRs - - Docs:=8 -
8.9 S2-2208330 CR Approval 23.247 CR0135 (Rel-17, 'F'): Missing NID in output parameters to AF for SNPN Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.9 S2-2208577 CR Approval 23.247 CR0137 (Rel-17, 'F'): Clean-up of PCC procedures for 5MBS Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2209288. Judy (Ericsson) provides r01
Thomas(Nokia) comments
Judy (Ericsson) responds to Thomas(Nokia)
Thomas(Nokia) provides r02
==== Revisions Deadline ====
Judy (Ericsson) is fine with r02
==== Final Deadline ====
Revised
8.9 S2-2209288 CR Approval 23.247 CR0137R1 (Rel-17, 'F'): Clean-up of PCC procedures for 5MBS Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2208577r02. Approved Agreed
8.9 S2-2208723 CR Approval 23.247 CR0139 (Rel-17, 'F'): CR on MTK or MSK processing Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2209289. Robbie (Ericsson) asks for clarification
LiMeng (Huawei) thanks for r01, but it seems that the link is broken.
Thomas (Nokia) provides r01
Thomas(Nokia) replies that link now works.
Thomas (Nokia) replies to Robbie
LiMeng (Huawei) replies to Thomas and Robbie.
Robbie (Ericsson) provides r02 and replies to LiMeng (Huawei) and Thomas (Nokia)
LiMeng (Huawei) asks questions
Robbie (Ericsson) replies to LiMeng (Huawei)
Thomas (Nokia) is fine with r02 and replies to LiMeng and Robbie
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.9 S2-2209289 CR Approval 23.247 CR0139R1 (Rel-17, 'F'): CR on MTK or MSK processing Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson Rel-17 Revision of S2-2208723r02. Approved Agreed
8.9 S2-2208170 CR Approval 23.247 CR0133R1 (Rel-17, 'F'): Alignment with SA WG4 work on MBS service announcements Nokia, Nokia Shanghai-Bell Rel-17 Revision of (postponed) S2-2207689 from S2-152E. CC#3: Postponed to CC#4. CC#4: No consensus. Noted Robbie (Ericsson) comments that S2-2208170 and S2-2208840 are competing, and we need to find a way forward.
==== Revisions Deadline ====
Haris(Qualcomm) proposes to NOTE S2-2208170 and move ahead with S2-2208840
Youngkyo(Samsung) shares the view with Haris(Qualcomm).
Robbie (Ericsson) supports Haris(Qualcomm) to note this CR and move ahead with S2-2208840
Thomas(Nokia) suggest bringing both S2-2208170 and S2-2208840 to CC2 as they are competing proposals
==== Final Deadline ====
Thomas(Nokia) provides late r01
Noted
8.9 S2-2208840 CR Approval 23.247 CR0140 (Rel-17, 'F'): Alignment with stage-3 for USD and service announcement Qualcomm Incorporated Rel-17 CC#3: Postponed to CC#4. CC#4: No consensus. Noted Robbie (Ericsson) supports this CR, and adds Ericsson as co-source in r01.
LiMeng (Huawei) objects to the proposal.
Youngkyo(Samsung) supports wayforward of this CR and provide r02.
Leo (Deutsche Telekom) proposes to NOTE this LS, and use S2-2208812
Haris(Qualcomm) responds to LiMeng (Huawei)
Haris(Qualcomm) provides r03
==== Revisions Deadline ====
Wanqiang(Huawei) objects the proposal (any revision).
Kaixin (CBN) objects to the proposal.
Zhendong (ZTE) agrees with Wanqiang (Huawei), proposes to Note this CR.
Haris(Qualcomm) suggests to discuss in CC#2
Antoine (Orange) supports r03.
==== Final Deadline ====
Noted
8.9 S2-2209198 CR Approval 23.247 CR0142 (Rel-17, 'F'): Update on service announcement/pre-configuration description Samsung Rel-17 Merged into (Covered by) S2-2208840 Robbie (Ericsson) suggests merging it to S2-2208840
Thomas (Nokia) suggest to consider this CR covered by S2-2208840or S2-2208170
Youngkyo(Samsung) is okay to handle this issue S2-2208840 instead of me to be continued from the previous meeting.
Youngkyo(Samsung) is okay with merging it to S2-2208840
Thomas (Nokia) suggest to consider this CR covered by S2-2208840 or S2-2208170
==== Revisions Deadline ====
==== Final Deadline ====
Merged
8.9 - - - Documents exceeding TU Budget - - Docs:=1 -
8.9 S2-2208719 CR Approval 23.247 CR0138 (Rel-17, 'F'): CR on MBS user service Huawei, HiSilicon Rel-17 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=0 -
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=2 -
8.11 S2-2208121 LS In Action LS from CT WG1: LS on UE selecting a non-allowed TAI in satellite access broadcasting multiple TACs per cell CT WG1 (C1-225160) Rel-17 Noted Steve (Huawei) comments
Jean Yves (Thales) comments
Stefan (Ericsson) provides comments
Hannu (Nokia) proposes to note the LS and agrees the interpretation suggested by Jean Yves and Stefan.
Yuxin (Xiaomi) supports to note the LS and provides comments.
Chris (Vodafone) is also Ok to note the LS. The example looks like network misconfiguration.
Noted
8.11 S2-2208135 LS In Information LS from CT WG4: Reply LS on Nudm_UEContextManagement service for satellite NG-RAN CT WG4 (C4-224409) Rel-17 Noted Jean-Yves (Thales) proposes to note this LS which is for information
Steve (Huawei) agrees about noting. We can note it.
Noted
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=4 -
8.12 S2-2208165 LS In Information LS from RAN WG2: LS on TX profile RAN WG2 (R2-2208853) Rel-17 Noted LaeYoung (LGE) proposes to NOTE this LS because this LS is for Information thus no action is needed in SA2. Noted
8.12 S2-2208306 CR Approval 23.287 CR0185 (Rel-17, 'F'): Clarification on the PC5 DRX operation for Groupcast Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2209571. LaeYoung (LGE) provides r02.
LaeYoung (LGE) provides r01, and replies to Wen (vivo) and Fei (OPPO).
Fei (OPPO) comments on r01.
Wen(vivo) comments.
LaeYoung (LGE) provides r01.
LiMeng (Huawei) is fine with r02.
LaeYoung (LGE) thanks to LiMeng (Huawei) for checking and confirming r02. :)
==== Revisions Deadline ====
Fei (OPPO) is fine with r02.
==== Final Deadline ====
Revised
8.12 S2-2209571 CR Approval 23.287 CR0185R1 (Rel-17, 'F'): Clarification on the PC5 DRX operation for Groupcast Huawei, HiSilicon Rel-17 Revision of S2-2208306r02. Approved Agreed
8.12 S2-2208481 CR Approval 23.287 CR0186 (Rel-17, 'F'): Removal of V2X policy request during registration procedure CATT Rel-17 Postponed LaeYoung (LGE) thanks to Deng Qiang (CATT) and let's merge this CR to S2-2208174.
Deng Qiang (CATT) is fine to discuss this issue under AI#7.1, and this paper can be merged into S2-2208174.
LaeYoung (LGE) suggests to discuss this issue under AI#7.1 (with S2-2208174).
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
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:=8 -
8.14 S2-2208743 CR Approval 23.273 CR0234 (Rel-17, 'F'): Support an indication of reliable UE location information requirement Huawei, HiSilicon Rel-17 Bad WI Code! Noted Stephen (Qualcomm) provides an r01
Guanglei (Huawei) provides r02 to correct WI code.
Stephen (Qualcomm) flags the r01 with the correct agenda item in the subject line
Ming (CATT) comments and provides r03.
Stephen (Qualcomm) provides comments and an r04
Guanglei (Huawei) can live with r04
==== Revisions Deadline ====
Stephen (Qualcomm) can agree r01, r02 or r04 but not r00 or r03
Ming (CATT) comments, can only accept r03 for this meeting.
Suggests that SA2 checks SA3 on whether the measurement from UE is trusted or not, and align SA2 spec accordingly in future meeting, if necessary.
Guanglei (Huawei) understand the concern from Ming(CATT), supports r03 for the sake of future proof. If the discussion on NTN has conclusion that the UE-based measurement is also trusted, we can further revise SA2/SA3 UAS/LCS specifications.
Leo (Deutsche Telekom) supports r03 and considers UE provided information as not reliable.
==== Final Deadline ====
Noted
8.14 S2-2208742 CR Approval 23.256 CR0069 (Rel-17, 'F'): Indication of Network Assisted Positioning method for UAV positioning Huawei, HiSilicon Rel-17 Bad WI Code! r01 agreed. Revised to S2-2209572. Guanglei (Huawei) provides r01 to correct WI code.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
8.14 S2-2209572 CR Approval 23.256 CR0069R1 (Rel-17, 'F'): Indication of Network Assisted Positioning method for UAV positioning Huawei, HiSilicon Rel-17 Revision of S2-2208742r01. Approved Agreed
8.14 S2-2208744 LS OUT Approval [DRAFT] LS reply on Indication of Network Assisted Positioning method Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2209573. CC#3: This LS was postponed and S2-2209573 was withdrawn Leo (Deutsche Telekom) provides r01 and comments that incoming LS S2-2208137 is in AI#8.7
Leo (Deutsche Telekom) provides link to r01
==== Revisions Deadline ====
Guanglei (Huawei) is fine with r01
==== Final Deadline ====
Postponed
8.14 S2-2209573 LS OUT Approval [DRAFT] LS reply on Indication of Network Assisted Positioning method Huawei, HiSilicon Rel-17 Revision of S2-2208744r01. CC#3: WITHDRAWN Withdrawn
8.14 S2-2209074 CR Approval 23.273 CR0235 (Rel-17, 'F'): Update of GNSS integrity requirement provisioing Huawei, HiSilicon Rel-17 Postponed Cai Simon (Nokia) provides comments
Stephen (Qualcomm) provides comments
Runze (Huawei) replies to Stephen (Qualcomm).
Runze (Huawei) replies to Simon (Nokia).
Cai Simon (Nokia) replies to Runze (Huawei)
Runze (Huawei) agrees with Cai Simon (Nokia) and provides r01.
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to postpone the CR and agrees with Runze (Huawei) to consult RAN2
==== Final Deadline ====
Postponed
8.14 S2-2210162 LS OUT Approval [DRAFT] LS on GNSS integrity requirement provisioning Huawei CC#4: r00 agreed. Revised to S2-2209966. Runze (Huawei) provides r00 of S2-2210162 in the revision folder. Revised
8.14 S2-2209966 LS OUT Approval LS on GNSS integrity requirement provisioning SA WG2 - Revision of S2-2210162r00. Approved Approved
8.15 - - - Multimedia Priority Service (MPS) Phase 2 (MPS2) - - Docs:=0 -
8.16 - - - Dynamic management of group-based event monitoring (TEI17_GEM) - - Docs:=0 -
8.17 - - - N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) - - Docs:=0 -
8.18 - - - System enhancement for Redundant PDU Session (TEI17_SE_RPS) - - Docs:=0 -
8.19 - - - IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) - - Docs:=0 -
8.20 - - - Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) - - Docs:=0 -
8.21 - - - Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) - - Docs:=0 -
8.22 - - - IP address pool information from UDM (TEI17_IPU) - - Docs:=0 -
8.23 - - - Same PCF selection for AMF and SMF (TEI17-SPSFAS) - - Docs:=0 -
8.24 - - - Support of different slices over different Non-3GPP access (TEI17_N3SLICE) - - Docs:=3 -
8.24 S2-2208254 CR Approval 23.501 CR3704 (Rel-17, 'F'): ULI with TAI for non-3GPP access Ericsson Rel-17 r03 agreed. Revised to S2-2209290. Laurent (Nokia): provides r01
Stefan (Ericsson) replies
Stefan (Ericsson) provides r02
Marco (Huawei) provide r03
==== Revisions Deadline ====
Laurent (Nokia): objects to R00 and R02
==== Final Deadline ====
Revised
8.24 S2-2209290 CR Approval 23.501 CR3704R1 (Rel-17, 'F'): ULI with TAI for non-3GPP access Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2208254r03. Approved Agreed
8.24 S2-2208255 CR Approval 23.316 CR2073 (Rel-17, 'F'): ULI with TAI for wireline access Ericsson Rel-17 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
8.25 - - - Minimization of Service Interruption (MINT) - - Docs:=3 -
8.25 S2-2208126 LS In Information LS from CT WG1: Reply LS on system information extensions for minimization of service interruption (MINT) CT WG1 (C1-225386) Rel-17 Noted Hyunsook (LGE) proposes to note the LS. Noted
8.25 S2-2209166 CR Approval 23.502 CR3600 (Rel-17, 'F'): PLMN with disaster condition Samsung Rel-17 r02 agreed. Revised to S2-2209291. Hyunsook (LGE) provides a comment and r01.
Haiyang (Huawei) provides a question.
Lalith(Samsung) replies
Haiyang (Huawei) further provides a question.
Lalith(Samsung) replies to Haiyang (Huawei)
Haris(Qualcomm) provides r02
Lalith(Samsung) is OK with r02
==== Revisions Deadline ====
Haiyang (Huawei) is OK with r02.
Hyunsook (LGE) is OK with r02.
Qian (Ericsson) is OK with r02.
==== Final Deadline ====
Revised
8.25 S2-2209291 CR Approval 23.502 CR3600R1 (Rel-17, 'F'): PLMN with disaster condition Samsung Rel-17 Revision of S2-2209166r02. Approved Agreed
8.26 - - - Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) - - Docs:=1 -
8.26 S2-2208127 LS In Information LS from CT WG1: Reply LS on the maximum PTW length of IDLE eDRX CT WG1 (C1-225450) Rel-17 Noted Steve (Huawei) proposes to note
Chris (Vodafone) comments that when using eDRX, DRX should be short and hence large PTW is not needed. It might be good to inform R2 and C1 about that.
Noted
8.27 - - - Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) - - Docs:=0 -
8.28 - - - Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups - - Docs:=4 -
8.28 S2-2208188 CR Approval 23.502 CR3552 (Rel-17, 'F'): Correction to Nnef_UEId_Get and Nbsf_Management_Discovery definition Intel Rel-17 r02 agreed. Revised to S2-2209574. Saso (Intel) provides r01 by removing the second change (which is merged in 8936).
Dario (Qualcomm) provides r02
Saso(Intel) is ok with r02
==== Revisions Deadline ====
Laurent (Nokia): objects to R00, R01; Supports R02
==== Final Deadline ====
Revised
8.28 S2-2209574 CR Approval 23.502 CR3552R1 (Rel-17, 'F'): Correction to Nnef_UEId_Get Intel Rel-17 Revision of S2-2208188r02. Approved Agreed
8.28 S2-2208469 CR Approval 23.501 CR3668R1 (Rel-17, 'F'): NSAG for TA(s) just outside of the RA has a specific association to those TA(s) NEC Rel-17 Revision of (Postponed) S2-2205672 from S2#152E. Noted Genadi (Lenovo) asks a question for clarification.
Peter Hedman (Ericsson) provides comments that current text is good enough i.e. propose to note the CR
Tamura (NEC) responds to Genadi.
Genadi (Lenovo) is fine with the clarification by Tamura (NEC).
Jinguo(ZTE) shares the same view as Peter Hedman (Ericsson)
Tamura (NEC) provides r01.
Tamura (NEC) replies to Jinguo (ZTE).
Peter Hedman (Ericsson) provides comments and still do not see the need for the CR
Alessio(Nokia) shares the view of Ericsson. the operator can configure NSAGs for TAs outside RA already so there is no FASMO. FASMO does not apply to configuration related issues that can be set in a way that does not cause the misoperation.
Jinguo(ZTE) is fine with Tamura (NEC) response
Haiyang (Huawei) comments
Tamura (NEC) provides r02 reflecting given comments from Jinguo (ZTE) and Sunhaiyang (Huawei) but not seeking approval any more in this meeting.
As two companies don't qualify it as FASMO, no point to propose it as release 17. As Peter (Ericsson) proposed in his Email, we are happy to work on it as Release 18.
==== Revisions Deadline ====
Andy is right. r02 can be noted. I was not clear. Sorry about it.
==== Final Deadline ====
Noted
8.28 S2-2209204 LS In Action LS from SA WG3: LS reply on 5G NSWO roaming aspects SA WG3 (S3-222397) Rel-17 Noted Laurent (Nokia): Proposes to NOTE the LS
Stefan (Ericsson) agrees to NOTE
Noted
9 - - - Rel-18 SIDs - - Docs:=0 -
9.1.1 - - - Study on System Enabler for Service Function Chaining (FS_SFC) - - Docs:=5 -
9.1.1 S2-2208268 P-CR Approval 23.700-18: KI#1, Basic conclusions . Ericsson Rel-18 Merged into S2-2209858 Megha(Intel) comments - can this pCR be marked as merged with S2-2209113?
==== Revisions Deadline ====
Megha(Intel) comments -this pCR is to be marked as merged with S2-2209113
==== Final Deadline ====
Merged
9.1.1 S2-2208685 P-CR Approval 23.700-18: Conclusions for FS_SFC. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209858 Dongjoo(Nokia) responds to Megha
Megha(Intel) comments - can this pCR be marked as merged with S2-2209113?
==== Revisions Deadline ====
Dongjoo(Nokia) confirms this document can be marked as merged into S2-2209113.
==== Final Deadline ====
Merged
9.1.1 S2-2208898 P-CR Approval 23.700-18: KI#1, Conclusion for KI#1. Huawei, HiSilicon Rel-18 Merged into S2-2209858 Megha(Intel) comments - can this pCR be marked as merged with S2-2209113?
==== Revisions Deadline ====
Megha(Intel) comments - this pCR is to be marked merged with S2-2209113.
==== Final Deadline ====
Merged
9.1.1 S2-2209113 P-CR Approval 23.700-18: KI#1: Conclusion. Intel, AT&T, Interdigital, Microsoft, Sandvine, Deutsche Telekom, DISH network, Charter Communications Rel-18 CC#4: r09 agreed. Revised to S2-2209858, merging S2-2208268, S2-2208685 and S2-2208898 Jinguo(ZTE) shares the same view as others
Dongjoo(Nokia) responds to Megha
Fenqin (Huawei) proposes comments.
Megha(Intel) proposes to use this pCR as baseline for all discussions related to KI#1 conclusion.
Stefan (Ericsson) also shares the same views
Megha(Intel) provides r01 and comments
Megha (Intel) provides response to Jinguo (ZTE)
Jinguo(ZTE) replies to Megha (Intel)
Fenqin (Huawei) provides further comments.
Dongjoo(Nokia) asks questions to Jinguo(ZTE)
Stefan (Ericsson) replies to Megha
Jinguo(ZTE) replies to Dongjoo(Nokia)
Megha (Intel) replies to Stefan and provides r02
Dongjoo(Nokia) replies and asks a further question to Jinguo(ZTE)
Fenqin (Huawei) provides r03
Dongjoo(Nokia) asks a clarification question to Fenqin(Huawei)
Fenqin (Huawei) provides response to Dongjoo.
Dongjoo(Nokia) replies to Fenqin(Huawei) and provides r04
Stefan (Ericsson) provides r06
Jinguo(ZTE) provides r07, and points that that Stefan(Ericsson) provides r05 instead of r06,
Megha(Intel) provides r08
==== Revisions Deadline ====
Megha (Intel) provides comments
Fenqin (Huawei) provides comments
Dongjoo (Nokia) provides feedback to Fenqin (Huawei)
Megha (Intel) provides reply to Fenqin(Huawei)
Dongjoo (Nokia) supports the response from Megha (Intel)
Megha (Intel) provides comment that based on the result of the SoH r05 will be used for KI#1 agreement.
Megha (Intel) is ok with r05 with the added underlined text to bullet point 2 - PCF checks whether the indicated SFC policy IDs and Metadata correspond to an authorized SFC policy for the AF.
==== Final Deadline ====
Megha (Intel) proposes to check this pCR in CC#4 to update the approved r05 with the addition of text 'and Metadata' and remove text 'for the AF' in bullet point 2.
Revised
9.1.1 S2-2209858 P-CR Approval 23.700-18: KI#1: Conclusion. Intel, AT&T, Interdigital, Microsoft, Sandvine, Deutsche Telekom, DISH network, Charter Communications, KPN Rel-18 Revision of S2-2209113r09, merging S2-2208268, S2-2208685 and S2-2208898. Approved Approved
9.1.2 - - - System Enabler for Service Function Chaining (SFC) - - Docs:=16 -
9.1.2 S2-2208269 CR Approval 23.501 CR3706 (Rel-18, 'C'): Basic description of Service Function Chaining Ericsson Rel-18 Postponed Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments proposes to postpone the CR.
==== Final Deadline ====
Postponed
9.1.2 S2-2208455 CR Approval 23.501 CR3716 (Rel-18, 'B'): Support for Service Function Chaining in 5GS Intel Rel-18 Noted Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments that based on the outcome of SoH , this CR is to be NOTED.
==== Final Deadline ====
Noted
9.1.2 S2-2208525 CR Approval 23.501 CR3719 (Rel-18, 'C'): SMF/UPF functionalities for SFC support (based on option 1 for KI#1 Conclusion) LG Electronics Rel-18 Postponed Dongjoo(Nokia) ask a question
Hyunsook (LGE) clarifies.
Dongjoo(Nokia) replies to Hyunsook(LGE)
Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments to postpone the CR to next meeting.
==== Final Deadline ====
Postponed
9.1.2 S2-2208526 CR Approval 23.502 CR3571 (Rel-18, 'B'): Enabling AF to request predefined SFC ETRI Rel-18 Postponed Stefan (Ericsson) provides comments
Yoohwa (ETRI) responds to Stefan (Ericsson).
==== Revisions Deadline ====
==== Final Deadline ====
Fenqin (Huawei) ask to postpone this paper
Megha(Intel) comments - For CC#4 as this CR needs to be marked as postponed.
Postponed
9.1.2 S2-2208689 CR Approval 23.501 CR3727 (Rel-18, 'B'): Adding a clause for the description of SFC Nokia, Nokia Shanghai Bell Rel-18 Postponed Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments to postpone the CR to next meeting.
==== Final Deadline ====
Postponed
9.1.2 S2-2208701 CR Approval 23.501 CR3728 (Rel-18, 'B'): Supporting traffic influence to service functions Lenovo, Rel-18 r01 agreed. Revised to S2-2209859. Postponed Megha(Intel) provides r01 and comments
==== Revisions Deadline ====
==== Final Deadline ====
Fenqin (Huawei) ask to postpone this paper
Dimitris (Lenovo) is ok to postpone
Megha(Intel) comments - For CC#4 this CR needs to be marked as postponed.
Postponed
9.1.2 S2-2209859 CR Approval 23.501 CR3728R1 (Rel-18, 'B'): Supporting traffic influence to service functions Lenovo, Rel-18 Revision of S2-2208701r01. WITHDRAWN Withdrawn
9.1.2 S2-2208712 CR Approval 23.502 CR3580 (Rel-18, 'B'): Supporting traffic influence to service functions Lenovo, Rel-18 Postponed Fenqin (Huawei) provides comments
Dimitris (Lenovo) responds
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.1.2 S2-2208899 CR Approval 23.501 CR3736 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Postponed Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments to postpone the CR to next meeting.
==== Final Deadline ====
Postponed
9.1.2 S2-2208456 CR Approval 23.502 CR3567 (Rel-18, 'B'): Procedure update to support Service Function Chaining in 5GS Intel Rel-18 Noted Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments that based on the outcome of SoH , this CR is to be NOTED.
==== Final Deadline ====
Noted
9.1.2 S2-2208691 CR Approval 23.502 CR3579 (Rel-18, 'B'): Procedure update for SFC support Nokia, Nokia Shanghai Bell Rel-18 CR Number missing! Postponed Dongjoo(Nokia) provides r02
Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
Stefan (Ericsson) provides comments
Dongjoo (Nokia) provides r03 accepting the comments from Stefan (Ericsson)
==== Revisions Deadline ====
Megha(Intel) comments to postpone this CR for next meeting
==== Final Deadline ====
Postponed
9.1.2 S2-2208900 CR Approval 23.502 CR3588 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Postponed Megha(Intel) comments the decision to endorse/postpone this CR depends on the KI#1 conclusion in AI 9.1.1.
==== Revisions Deadline ====
Megha(Intel) comments to postpone this CR for next meeting
==== Final Deadline ====
Postponed
9.1.2 - - - Documents exceeding TU Budget - - Docs:=4 -
9.1.2 S2-2208270 CR Approval 23.503 CR0740 (Rel-18, 'C'): Basic description of Service Function Chaining Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.1.2 S2-2208457 CR Approval 23.503 CR0746 (Rel-18, 'B'): Policy update to support Service Function Chaining in 5GS Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.1.2 S2-2208702 CR Approval 23.503 CR0752 (Rel-18, 'B'): SFC Support Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.1.2 S2-2208901 CR Approval 23.503 CR0756 (Rel-18, 'B'): Application Function influence SFC support Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 - - - Study on Generic group management, exposure and communication enhancements (FS_GMEC) - - Docs:=28 -
9.2.1 - - - KI#1 - group service area, group MBR, group QoS - - Docs:=7 -
9.2.1 S2-2208524 P-CR Approval 23.700-74: KI#1: Conclusion update on service area enforcement. LG Electronics Rel-18 r01 agreed. Revised to S2-2209575. Qianghua (Huawei) provides r01 to capture the assumption to use LADN-based approach
Sang-Jun (Samsung) comments.
==== Revisions Deadline ====
Hyunsook (LGE) is OK with r01.
==== Final Deadline ====
Revised
9.2.1 S2-2209575 P-CR Approval 23.700-74: KI#1: Conclusion update on service area enforcement. LG Electronics Rel-18 Revision of S2-2208524r01. Approved Approved
9.2.1 S2-2208607 P-CR Approval 23.700-74: Conclusion update for KI#1 for SMF service area control. China Mobile Rel-18 Noted Sebastian (Qualcomm) objects to the pCR
Dan (China Mobile) reply
Shubhranshu (Nokia) comments
Qianghua (Huawei) provides comments and suggests a way forward
Qianghua (Huawei) provides r01, this is an attempt to make a way forward as proposed below
==== Revisions Deadline ====
Shubhranshu (Nokia) concerns to r01
Stefan (Ericsson) shares same concern as Shubhranshu
Sebastian (Qualcomm) objects also to r01 for the reasons given by Shubhranshu and Stefan
==== Final Deadline ====
Noted
9.2.1 S2-2208594 P-CR Approval 23.700-74: KI#1: Update for Group-MBR conclusion. CATT Rel-18 r01 agreed. Revised to S2-2209576. Shubhranshu (Nokia) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.2.1 S2-2209576 P-CR Approval 23.700-74: KI#1: Update for Group-MBR conclusion. CATT Rel-18 Revision of S2-2208594r01. Approved Approved
9.2.1 S2-2208714 P-CR Approval 23.700-74: KI#1_Conclusion update for QoS provision for KI#5 muticast group. China Telecom Rel-18 CC#3: r03 agreed. Revised to S2-2209948. Stefan (Ericsson) provides comments
Qianghua (Huawei) also suggests to consider this as part of KI#3, but with different views on how to use such QoS
Heng (China Telecom) reply
Sebastian (Qualcomm) comments
Stefan (Ericsson) comments
Sang-Jun (Samsung) comments.
Heng (China Telecom) provide r01.
Heng (China Telecm) provides r02
Shubhranshu (Nokia) asks for clarification
Heng (China Telecom) reply to Shubhranshu and provide r03 to correct the mistake.
==== Revisions Deadline ====
Heng (China Telecom) reply to Shubhranshu (Nokia)
Sebastian (Qualcomm) objects to the PCR (all versions)
Heng (China Telecom) reply to Sebastian (Qualcomm)
Sang-Jun (Samsung) proposes to go with r03.
Qianghua (Huawei) proposes to go with r03.
==== Final Deadline ====
Revised
9.2.1 S2-2209948 P-CR Approval 23.700-74: KI#3_Conclusion update for QoS provision for KI#5 muticast group. China Telecom Rel-18 Revision of S2-2208714r03. Approved Approved
9.2.1 - - - KI#3 - conclusion updates - - Docs:=3 -
9.2.1 S2-2208280 P-CR Approval 23.700-74: KI#3: Conclusion updates . Ericsson Rel-18 r05 agreed. Revised to S2-2209674. Qianghua (Huawei) provides comments
Sebastian (Qualcomm) comments
Stefan (Ericsson) provides comments
Sebastian (Qualcomm) provides r01
Qianghua (Huawei) provides r02
Stefan (Ericsson) provides r03
Qianghua (Huawei) provides r04
Stefan (Ericsson) provides r05
Shubhranshu (Nokia) objects r04
Qianghua (Huawei) replies and also asks Sebastian to reconsider again
==== Revisions Deadline ====
Sebastian (Qualcomm) is ok with r01; objects to other versions; can be ok with r05 if this text ('The following example or NOTE may however be added to e.g. TS 23.501 or 23.502) to clarify how the AF does this.') and the two sub-bullets are removed and replaced by 'How the AF does this is not to be standardized (An example or NOTE may however be added to e.g. TS 23.501 or 23.502).'
Stefan (Ericsson) OK with r00, r01, r03, r05. Objects to r02, r04
Sebastian (Qualcomm) replies to Stefan
Qianghua (Huawei) OK to go with r05+ removal of ('The following example or NOTE may however be added to e.g. TS 23.501 or 23.502) to clarify how the AF does this.') and the two sub-bullets, + addition of 'How the AF does this is not to be standardized in SA2 specifications (A NOTE may however be added to e.g. TS 23.501 or 23.502' + removal of the EN about CSR/CSA
Qianghua (Huawei) cannot accept R0, R01, r03, for records
==== Final Deadline ====
Shubhranshu (Nokia) agrees and proposes to capture this in Chair's Note: 'Revision of S2-2208280r05 + changes proposed by Huawei', instead of current Chair's Note which says: 'Revision of S2-2208280r05 + changes proposed by Qualcomm'
Antoine (Orange): I don't understand 'removal of the EN about CSR/CSA' because there's no EN and nothing about CSR/CSA in r05.
Sebastian (Qualcomm) is ok with the proposal by Shubhranshu (Nokia)
Revised
9.2.1 S2-2209674 P-CR Approval 23.700-74: KI#3: Conclusion updates . Ericsson Rel-18 Revision of S2-2208280r05. Approved Approved
9.2.1 S2-2208503 P-CR Approval 23.700-74: Update to conclusion of KI#3. Siemens Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.2.1 - - - KI#4- Rapp Blank Conclusion - - Docs:=1 -
9.2.1 S2-2208646 P-CR Approval 23.700-74: Merged Conclusion for FS_GMEC KI#4. Samsung (Rapp), Huawei (Rapp) Rel-18 CC#3: Postponed to CC#4. CC#4: Noted Qianghua (Huawei) provides r01
Laurent (Nokia): provides r02
Qianghua (Huawei) provides r03
==== Revisions Deadline ====
Stefan (Ericsson) objects to r01-r03 (r00 is empty)
Qianghua (Huawei), based on offline discussion, proposes to go with r03 + the following changes:
Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism'
Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose'
Laurent (Nokia): objects to R00-R03
Sang-Jun (Samsung) also supports going with r03 + the following changes:
Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism'
Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose'
Zhendong (ZTE) is fine with qianghua proposal
Stefan (Ericsson) cannot accept Qianghua proposal
Qianghua (Huawei), based on offline discussion, proposes to go with r03 + the following changes:
Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism'
Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose'
+ confirm whether to keep the Ens at CC#3
==== Final Deadline ====
Laurent (Nokia): my request is to have a written text in front of me at the CC3. Especially I require to SEE where such NOTE would be 'No standard impacts are expected for this purpose'
Qianghua (Huawei) provides r04 at CC#3, need to check whether to keep the ENs or not at CC#3, besides the following changes over r03 seem agreeable:
- Move sentence 'Implementation dependent signaling ... is based on implementation choice.' to the NOTE, and change 'signaling' to 'mechanism'
- Add 'except a NOTE such as' after 'No standard impacts are expected for this purpose'
Noted
9.2.1 - - - KI#4-contributions from company - - Docs:=3 -
9.2.1 S2-2208283 P-CR Approval 23.700-74: KI#4: Conclusion proposal. Ericsson, Nokia, Nokia Shanghai Bell Rel-18 Noted Qianghua (Huawei) disagrees some observations and thus cannot agree the conclusions pointing to specific solutions.
Sang-Jun (Samsung) shares the same veiws as Qianghua.
Stefan (Ericsson) provides replies
Laurent (Nokia): answers
Qianghua (Huawei) provides responses to the comments
==== Revisions Deadline ====
Qianghua (Huawei) agrees to note or merge, discussion already under 08646. Otherwise object for record.
==== Final Deadline ====
Noted
9.2.1 S2-2208939 P-CR Approval 23.700-74: KI#4, evaluations and conclusions. Huawei, HiSilicon Rel-18 Noted Stefan (Ericsson) cannotagree to the conclusions
Laurent (Nokia): We cannot also agree to the conclusions, support Stefan's view as we expressed also in 8283 thread
Qianghua (Huawei) provides responses to the comments
==== Revisions Deadline ====
Laurent (Nokia): objects to any version (anyhow we are discussing 8646 now)
Qianghua (Huawei) OK to note
==== Final Deadline ====
Noted
9.2.1 S2-2208954 P-CR Approval 23.700-74: KI#4, adding the evaluation and conclusion for KI#4. ZTE Rel-18 Noted Stefan (Ericsson) has similar concerns
==== Revisions Deadline ====
Laurent (Nokia): objects to any version (anyhow we are discussing 8646 now)
==== Final Deadline ====
Noted
9.2.1 - - - KI#5-conclusion updates - - Docs:=1 -
9.2.1 S2-2208615 P-CR Approval 23.700-74: Conclusion for FS_GMEC KI#5. Samsung Rel-18 Approved Sebastian (Qualcomm) suggests to note the paper
Sang-Jun (Samsung) repiles to Sebastian (Qualcomm).
==== Revisions Deadline ====
Sang-Jun (Samsung) proposes to go with r00 as the NOTEs should be added even before the conclusion for KI1/2/3 are being undated.
==== Final Deadline ====
Approved
9.2.1 - - - Documents exceeding TU Budget - - Docs:=13 -
9.2.1 S2-2208279 P-CR Approval 23.700-74: KI#1: Update to conclusions . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208592 P-CR Approval 23.700-74: Update of Solution #12: Support 5G VN service area restriction with SMF service area. China Mobile Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208953 P-CR Approval 23.700-74: KI#1, update the solution 18. ZTE Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208952 P-CR Approval 23.700-74: KI#1, conclusion update. ZTE Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208937 P-CR Approval 23.700-74: KI#1: Update conclusions to address Editor's notes. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208394 P-CR Approval 23.700-74: Update of Solution #21 for FS_GMEC KI#1. China Telecom Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208281 P-CR Approval 23.700-74: KI#3, Sol#22: Solution updates to address ENs and clarify solution. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208938 P-CR Approval 23.700-74: KI#3: Update conclusions to address the ENs. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2209162 P-CR Approval 23.700-74: KI# 3 Conclusion updates. Nokia, Nokia Shanghai bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208223 P-CR Approval 23.700-74: Update to solution 16 ( 6.16.2.5). Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208282 P-CR Approval 23.700-74: KI#4, Sol#16: Updates to resolve editor s notes . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.1 S2-2208613 P-CR Approval 23.700-74: Conclusion for FS_GMEC KI#4. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
Laurent (Nokia): Objects to any version (rapporteur said not handled anyhow)
==== Final Deadline ====
Not Handled
9.2.1 S2-2208618 P-CR Approval 23.700-74: Evaluation for FS_GMEC KI#4. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
Laurent (Nokia): Objects to any version (rapporteur said not handled anyhow)
==== Final Deadline ====
Not Handled
9.2.2 - - - Generic group management, exposure and communication enhancements (GMEC) - - Docs:=11 -
9.2.2 - - - KI#2- CRs - - Docs:=6 -
9.2.2 S2-2208428 CR Approval 23.501 CR3715 (Rel-18, 'B'): TS 23.501 Enhancing External Exposure of Network Capability NTT DOCOMO, Huawei Rel-18 CR Number missing! r03 agreed. Revised to S2-2209577, merging S2-2208941 Tugce (NTT DOCOMO) provides r01.
Stefan (Ericsson) provides comments
Tugce (NTT DOCOMO) responds.
Shubhranshu (Nokia) comments
Qianghua (Huawei) comments
Stefan (Ericsson) comments
Stefan (Ericsson) replies to Tugce
Qianghua (Huawei) provides r02, merging 2208941
Stefan (Ericsson) provides r03
==== Revisions Deadline ====
Qianghua (Huawei) OK with r03, prefer r02
Stefan (Ericsson) proposes to go with r03
==== Final Deadline ====
Revised
9.2.2 S2-2209577 CR Approval 23.501 CR3715R1 (Rel-18, 'B'): TS 23.501 Enhancing External Exposure of Network Capability NTT DOCOMO, Huawei Rel-18 Revision of S2-2208428r03, merging S2-2208941. Approved Agreed
9.2.2 S2-2208432 CR Approval 23.502 CR3566 (Rel-18, 'B'): TS 23.502 Enhancing parameter provisioning services NTT DOCOMO, Huawei Rel-18 CR Number missing! Merged into S2-2209578 Tugce (NTT DOCOMO) provides r01.
Qianghua (Huawei) proposes to mark this CR postponed or merged into 08595
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.2.2 S2-2208595 CR Approval 23.502 CR3575 (Rel-18, 'B'): Enhance group status event reporting CATT Rel-18 r02 agreed. Revised to S2-2209578, merging S2-2208432 Stefan (Ericsson) comments and provides r01 and r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.2.2 S2-2209578 CR Approval 23.502 CR3575R1 (Rel-18, 'B'): Enhance group status event reporting CATT Rel-18 Revision of S2-2208595r02, merging S2-2208432. Approved Agreed
9.2.2 S2-2208941 CR Approval 23.501 CR3739 (Rel-18, 'B'): Support the enhance group status event reporting Huawei, HiSilicon Rel-18 Merged into S2-2209577 Qianghua (Huawei) agrees to merge this in S2-2208428
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.2.2 - - - KI#5- CRs - - Docs:=1 -
9.2.2 S2-2208643 CR Approval 23.501 CR3725 (Rel-18, 'C'): Allowing UE to simultaneously send data to different groups with different QoS policy Samsung, Huawei, Nokia, Nokia Shanghai Bell Rel-18 Postponed Sebastian (Qualcomm) objects to r00 and in general suggests to postpone the CR
Sang-Jun (Samsung) replies to Sebastian (Qualcomm). This is regarding the principle agreed for KI#5 and need to be captured even before the conclusion for KI1/2/3 are being undated.
Qianghua (Huawei) provides r01 and asks for clarification from Sebastian
Sebastian (Qualcomm) replies and proposes to postpone
==== Revisions Deadline ====
Sang-Jun (Samsung) replies to Sebastian (Qualcomm) and propses to go with r01.
Sebastian (Qualcomm) prefers to postpone; (objects to r00 and r01)
==== Final Deadline ====
Postponed
9.2.2 - - - Documents exceeding TU Budget - - Docs:=4 -
9.2.2 S2-2208596 DRAFTCR Information Update for 5G VN group data CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.2 S2-2208597 DRAFTCR Information Update paramaters for 5G VN group data CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.2 S2-2208940 DRAFTCR Information KI#1: Support the enhancement of group attribute management Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.2.2 S2-2208942 DRAFTCR Information KI#3: provisioning of traffic characteristics and monitoring of performance characteristics Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.3 - - - Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) - - Docs:=32 -
9.3 - - - Liaisons - - Docs:=1 -
9.3 S2-2208111 LS In Action LS from BBF: BBF 5G-RG requirements for 3GPP Rel.18/ATSSS (Enhanced Hybrid Access) BBF (LIAISE-542-5G-RG-Hybrid-Access-Requirements-00) Revision of Postponed S2-2205467 from S2#152-e. This LS was postponed Postponed
9.3 - - - KI#2 - Solution updates - - Docs:=5 -
9.3 S2-2209195 P-CR Approval 23.700-53: KI#2: Sol.2.1 Update. Deutsche Telekom Rel-18 r01 agreed. Revised to S2-2209278. Apostolis (Lenovo) provides comments and questions.
==== Revisions Deadline ====
Dieter (Deutsche Telekom) provides r01.
Tao(VC) still check r00 since r01 is provided after revision deadline and no explict objection to r00 for see.
==== Final Deadline ====
Revised
9.3 S2-2209278 P-CR Approval 23.700-53: KI#2: Sol.2.1 Update. Deutsche Telekom Rel-18 Revision of S2-2209195r01. Approved Approved
9.3 S2-2209087 P-CR Approval 23.700-53: Updates to solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, Charter Communications Rel-18 r03 agreed. Revised to S2-2209292. Dieter (Deutsche Telekom) provides comments, questions and suggestions to the solution update.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.3 S2-2209292 P-CR Approval 23.700-53: Updates to solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, Charter Communications Rel-18 Revision of S2-2209087r03. Approved Approved
9.3 S2-2209090 P-CR Approval 23.700-53: Updates to solution #2.3: MPQUIC steering functionality using IP proxying over HTTP. Lenovo, Broadcom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.3 - - - KI#3 - Solution updates - - Docs:=5 -
9.3 S2-2208801 DISCUSSION Discussion DP on the effectiveness of asynchronous redundant steering mode Alibaba Group Rel-18 Noted ==== Revisions Deadline ====
Rainer (Nokia) proposes to note the DP in 8801.
==== Final Deadline ====
Noted
9.3 S2-2208796 P-CR Approval 23.700-53: New solution on asynchronous redundant traffic steering mode. Alibaba Group Rel-18 Revision of (Noted) S2-2205560 from S2#152E. Noted Dario (Qualcomm) comments
Rainer (Nokia) comments.
==== Revisions Deadline ====
Guanzhou (InterDigital) assumes that no new solution is allowed at this meeting and this should be Noted.
Rainer (Nokia) agrees to note the paper.
==== Final Deadline ====
Noted
9.3 S2-2209032 P-CR Approval 23.700-53: Updates to solution #3.7: Suspending the Redundancy Steering Mode. China Telecom Rel-18 r01 agreed. Revised to S2-2209293. Rainer (Nokia) provides r01.
Yubing (China Telecom) is ok with r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.3 S2-2209293 P-CR Approval 23.700-53: Updates to solution #3.7: Suspending the Redundancy Steering Mode. China Telecom Rel-18 Revision of S2-2209032r01. Approved Approved
9.3 S2-2209034 P-CR Approval 23.700-53: Updates to solution #3.1: Deactivate the RSM during the redundant transmission. China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.3 - - - KI#5 - Solution updates - - Docs:=1 -
9.3 S2-2208326 P-CR Approval 23.700-53: KI#5, update Sol#5.6. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.3 - - - KI#2 - Evaluation and Conclusions - - Docs:=5 -
9.3 S2-2209092 P-CR Approval 23.700-53: Evaluation for KI#2. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent Rel-18 r04 agreed. Revised to S2-2209294. Dieter (Deutsche Telekom) comments and provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.3 S2-2209294 P-CR Approval 23.700-53: Evaluation for KI#2. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent Rel-18 Revision of S2-2209092r04. Approved Approved
9.3 S2-2209094 P-CR Approval 23.700-53: Conclusions for KI#2. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, US Cellular, China Mobile, Qualcomm Incorporated, Charter Communications, AT&T, Samsung, Cisco, HP Rel-18 CC#3: Postponed to CC#4. CC#4: r06 + changes agreed. Revised to S2-2209955. Apostolis (Lenovo) provides r01.
Dieter (Deutsche Telekom) provides r02.
==== Revisions Deadline ====
==== Final Deadline ====
Apostolis (Lenovo) responds to Susan (Huawei) and requests this document to be discussed in CC#3.
Revised
9.3 S2-2209955 P-CR Approval 23.700-53: Conclusions for KI#2. Lenovo, Motorola Mobility, Apple, Broadcom, Tencent, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CableLabs, LG Electronics, Tejas Networks, Meta USA, Google, US Cellular, China Mobile, Qualcomm Incorporated, Charter Communications, AT&T, Samsung, Cisco, HPE, NICT, KPN, F5, DISH Network, Intel, Tessares, Microsoft, CATT, ETRI Rel-18 Revision of S2-2209094r06 + changes. Approved Approved
9.3 S2-2209196 P-CR Approval 23.700-53: Evaluation and Conclusions for KI#2. Deutsche Telekom Rel-18 Noted Dieter (Deutsche Telekom) provides r01.
Dieter (Deutsche Telekom) comments that we could try to merge the evaluation part with 9092 and the conclusion part with 9094.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.3 - - - KI#3 - Evaluation and Conclusions - - Docs:=10 -
9.3 S2-2208278 P-CR Approval 23.700-53: KI#3: Updates to conclusion . Ericsson Rel-18 CC#3: Postponed to CC#4. CC#4: r10 agreed. Revised to S2-2209956. Dario (Qualcomm) comments.
==== Revisions Deadline ====
Stefan (Ericsson) comments on slides
==== Final Deadline ====
Apostolis (Lenovo) provides r02 as a possible compromise to be discussed in CC#3.
Revised
9.3 S2-2209956 P-CR Approval 23.700-53: KI#3: Updates to conclusion . Ericsson Rel-18 Revision of S2-2208278r10. Approved Approved
9.3 S2-2208439 P-CR Approval 23.700-53: KI#3: Evaluation/conclusions update on suspending the redundant steering mode. Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2209295. Stefan (Ericsson) provides comments
Rainer (Nokia) replies.
Myungjune (LGE) comments
Myungjune (LGE) replies to Rainer (Nokia)
Myungjune (LGE) replies to Rainer (Nokia).
Rainer (Nokia) provides r01.
Stefan (Ericsson) provides r02
Rainer (Nokia) is ok with r02.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r02.
==== Final Deadline ====
Revised
9.3 S2-2209295 P-CR Approval 23.700-53: KI#3: Evaluation/conclusions update on suspending the redundant steering mode. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208439r02. Approved Approved
9.3 S2-2208987 P-CR Approval 23.700-53: KI#3: Conclusion update for KI#3 . InterDigital Inc. Rel-18 Merged into S2-2209296 Dario (Qualcomm) asks questions for clarifications.
Rainer (Nokia) proposes to merge 8987 into 9096.
Guanzhou (InterDigital) agrees to merge this with S2-2209096 and responds to Dario (Qualcomm)'s questions.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.3 S2-2209035 P-CR Approval 23.700-53: Updates to the Conclusion for KI #3. China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.3 S2-2209096 P-CR Approval 23.700-53: Conclusions for KI#3: RTT Thresholds. Lenovo Rel-18 r06 agreed. Revised to S2-2209296, merging S2-2208987 Dario (Qualcomm) asks questions for clarification.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.3 S2-2209296 P-CR Approval 23.700-53: Conclusions for KI#3: RTT Thresholds. Lenovo, Nokia, Nokia Shanghai Bell, InterDigital Rel-18 Revision of S2-2209096r06, merging S2-2208987. Approved Approved
9.3 S2-2209098 P-CR Approval 23.700-53: Conclusions for KI#3: RSM with ATSSS-LL. Lenovo Rel-18 WITHDRAWN Jinguo(ZTE) asks questions for clarification.
==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
9.3 S2-2209152 P-CR Approval 23.700-53: KI#3: Removal of EN on duplication factor in evaluation and conclusions. Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Charter Communications, Broadcom Rel-18 Noted Myungjune (LGE) provides comments.
Stefan (Ericsson) have similar comments as LGE
Rainer (Nokia) replies.
Jinguo(ZTE) shares same concerns as Ericsson and LGE
Susan (Huawei) shares the similar view as Ericsson, LGE, ZTE.
Dario (Qualcomm) replies and provides r01
==== Revisions Deadline ====
Myungjune (LGE) comments.
Susan (Huawei) objects to all versions of the paper, i.e. r00 and r01.
Susan (Huawei) replies to Rainer (Nokia).
Stefan (Ericsson) also objects to all versions of the paper, i.e. r00 and r01.
==== Final Deadline ====
Noted
9.3 - - - KI#5 - Evaluation and Conclusions - - Docs:=5 -
9.3 S2-2208276 P-CR Approval 23.700-53: KI#5: Updates to conclusions to resolve Editor s note 1. Ericsson Rel-18 Merged into S2-2209297 Myungjune (LGE) proposes to merge this pCR into S2-2208460 / S2-2208500.
Rainer (Nokia) agrees to merge and asks for clarification.
Stefan (Ericsson) replies to Rainer
Stefan (Ericsson) OK to consider it merged into S2-2208500
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.3 S2-2208277 P-CR Approval 23.700-53: KI#5: Updates to conclusions to resolve Editor s note 2. Ericsson Rel-18 Merged into S2-2209297 Myungjune (LGE) proposes to merge this pCR into S2-2208460 / S2-2208500.
==== Revisions Deadline ====
Stefan (Ericsson) OK to consider it merged into S2-2208500
Marco (Huawei) as per Stefan's comment. Yes consider merged into 8500.
==== Final Deadline ====
Merged
9.3 S2-2208460 P-CR Approval 23.700-53: KI#5 Conclusion (clause 8.3), addressing the 1st EN in clause 8.3. Charter Communications, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Broadcom, Apple, CableLabs Rel-18 Merged into S2-2209297 Myungjune (LGE) provides r01.
Marco (Huawei) comments
Paul R (Charter) comments
Marco (Huawei) consider merged into 8500 as per 8500r06
Paul R (Charter) confirms that S2-2208460r01 has been merged into S2-2208500 during the meeting
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.3 S2-2208500 P-CR Approval 23.700-53: Conclusion for KI#5. LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell Rel-18 r11 agreed. Revised to S2-2209297, merging S2-2208276, S2-2208277 and S2-2208460 Myungjune (LGE) replies to Jinguo (ZTE)
Jinguo(ZTE) asks questions for clarification.
Myungjune (LGE) provides r01.
Jinguo(ZTE) asks one question
Myungjune (LGE) replies Jinguo (ZTE).
Marco (Huawei) ask clarification and comments
Stefan (Ericsson) comments and provides r02
Paul R. (Charter) comments and provides r03
Myungjune (LGE) provides r04.
Myungjune (LGE) replies to Marco (Huawei)
Marco (Huawei) agrees with Paul (charter) to remove of Wireline support . Support R02 NOT r03 & r04
Myungjune (LGE) clarifies that r04 is aligned with r02.
Stefan (Ericsson) replies to Paul and Myungjune
Myungjune (LGE) replies to Stefan (Ericsson).
Paul R. (Charter) provides r06 which merges S2-2208460r01 pCR, because S2-2208500r05 addresses the 1st EN in step 6.
Myungjune (LGE) replies to Paul R. (Charter)
Stefan (Ericsson) replies and provides r08
DongYeon (Samsung) provides r09.
Marco (Huawei) provide r10 without option 'without interruption'
Paul R (Charter) agrees to r09 but not r10
Myungjune (LGE) replies to Marco (Huawei) .
Stefan (Ericsson) comments to Myungjune and provides r11
==== Revisions Deadline ====
Paul R (Charter) supports r11 as it improves r09
Rainer (Nokia) is ok with r11.
Stefan (Ericsson) responds to Myungjune
Marco (Huawei) can live with r11 and object any version from 00 to 09
==== Final Deadline ====
Revised
9.3 S2-2209297 P-CR Approval 23.700-53: Conclusion for KI#5. LG Electronics, Lenovo, Nokia, Nokia Shanghai Bell, Charter Communications Rel-18 Revision of S2-2208500r11, merging S2-2208276, S2-2208277 and S2-2208460. Approved Approved
9.4.1 - - - Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) - - Docs:=56 -
9.4.1 - - - General - - Docs:=3 -
9.4.1 S2-2208776 LS OUT Approval [DRAFT] LS on Progress and open issues for NPN enhancements in Rel-18 Ericsson Rel-18 r01 agreed. Revised to S2-2209860. Peter Hedman (Ericsson) provides r01
Guanzhou (InterDigital) has some suggestion on Q1
Rainer (Nokia) comments.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r01 but also ok to add the proposals suggested and that is done in r02, i.e. r01+
Add 'and whether it is necessary that the UE needs to use any of these modes to select an SNPN over non-3GPP access' to question 4.
Add ', and does it depend on whose credentials the UE uses to access the hosting network' to question 1
Remove '' from question 2
Rainer (Nokia) is ok with r01 or r02.
Saso (Intel) prefers r01 wording for Q4.
Peter Hedman (Ericsson) asks if we then can agree r01 or r01+
Add ', and does it depend on whose credentials the UE uses to access the hosting network' to question 1
Remove '' from question 2
Rainer (Nokia) is ok to remove yellow text.
Guanzhou (InterDigital) is OK with r02 and is also OK with r01+changes Peter(Ericsson) mentioned below
==== Final Deadline ====
Revised
9.4.1 S2-2209860 LS OUT Approval Progress and open issues for NPN enhancements in Rel-18 SA WG2 Rel-18 Revision of S2-2208776r01. Approved Approved
9.4.1 S2-2208770 P-CR Approval 23.700-08: Correction of Mapping Solutions to Key Issues. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.4.1 - - - KI#2 - - Docs:=3 -
9.4.1 S2-2208438 P-CR Approval 23.700-08: KI#2 on Support of Non-3GPP access for SNPN: Conclusion update. Nokia, Nokia Shanghai Bell, Intel, Qualcomm Incorporated, Ericsson Rel-18 Approved Huan (vivo) asks questions for clarifications
Rainer (Nokia) replies.
Huan (vivo) comments
Saso (Intel) replies to Huan.
Marco (Huawei) comments
Rainer (Nokia) comments.
Huan(vivo) comments.
Saso (Intel) replies to Huan(vivo).
Yishan (Huawei) provides comments
Saso (Intel) replies to Yishan (Huawei)
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.4.1 S2-2208945 P-CR Approval 23.700-08: KI#2 Conclusions update to resolve the EN on NSWO enhancements. Lenovo Rel-18 r02 agreed. Revised to S2-2209861. Peter Hedman (Ericsson) provides comments
Saso (Intel) provides comments
Rainer (Nokia) comments.
Marco (Huawei) shares previous emails' views and concerns
Genadi (Lenovo) provides r01 and replies to Peter (Ericsson), Saso (Intel), Rainer (Nokia) and Marco (Huawei).
Genadi (Lenovo) replies to Saso (Intel).
Marco (Huawei) further comments
Genadi (Lenovo) replies to Marco (Huawei).
Saso (Intel) comments.
Marco (Huawei) can accept Saso's (Intel) proposal to consider for a note in future normative work.
Saso (Intel) provides r02 to keep the discussion ongoing.
Rainer (Nokia) is ok with r02.
==== Revisions Deadline ====
Peter Hedman (Ericsson) ok with r02
Marco (Huawei) ok with r02
==== Final Deadline ====
Revised
9.4.1 S2-2209861 P-CR Approval 23.700-08: KI#2 Conclusions update to resolve the EN on NSWO enhancements. Lenovo Rel-18 Revision of S2-2208945r02. Approved Approved
9.4.1 - - - KI#3 - - Docs:=8 -
9.4.1 S2-2208313 P-CR Approval 23.700-08: KI#3, Update evaluation on KI#3. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209862, merging S2-2208734 Marco (Huawei) provide r01 as merging of S2-228734/8775
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.4.1 S2-2209862 P-CR Approval 23.700-08: KI#3, Update evaluation on KI#3. Huawei, HiSilicon Rel-18 Revision of S2-2208313r01, merging S2-2208734. Approved Approved
9.4.1 S2-2208316 P-CR Approval 23.700-08: KI#3, Update conclusion on KI#3. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209863. Peter Hedman (Ericsson) provides comments and questions
Yishan (Huawei) answers to Peter Hedman (Ericsson) and provides r01 accordingly
Peter Hedman (Ericsson) provides r02, and ok to keep the content of agreement in this paper
==== Revisions Deadline ====
Yishan (Huawei) is ok with r02
==== Final Deadline ====
Revised
9.4.1 S2-2209863 P-CR Approval 23.700-08: KI#3, Update conclusion on KI#3. Huawei, HiSilicon Rel-18 Revision of S2-2208316r02. Approved Approved
9.4.1 S2-2208734 P-CR Approval 23.700-08: KI#3: Update evaluation of solutions for KI#3. CATT Rel-18 Merged into S2-2209862 Peter Hedman (Ericsson) provides comments, and suggests to mark the paper as merged into 08313.
Liping Wu (CATT) agrees to mark the paper as merged into 08313.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208775 P-CR Approval 23.700-08: KI#3: Evaluation and conclusion for Key Issue #3. Ericsson, Qualcomm Rel-18 r02 agreed. Revised to S2-2209864. Peter Hedman (Ericsson) provides r01 and suggests to merge in evaluation into 08313, tbd what tdoc to use for conclusions
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.4.1 S2-2209864 P-CR Approval 23.700-08: KI#3: Evaluation and conclusion for Key Issue #3. Ericsson, Qualcomm Rel-18 Revision of S2-2208775r02. Approved Approved
9.4.1 S2-2209173 P-CR Approval 23.700-08: Update evaluation and solution#22 for key issue#3/4. Xiaomi Rel-18 Noted Peter Hedman (Ericsson) provides comments
Jianning (Xiaomi) replies to Peter (Ericsson)
Marco (Huawei) provide r01 and comment
Josep (DT) agrees with Peter (Ericsson) does not find unsecured connection to the hosting network acceptable.
Ashok (Samsung) comments
Huan (vivo) comments
Jianning (Xiaomi) replies to Josep (DT)
Jianning (Xiaomi) replies to Huan(vivo)
Josep (DT) replies to Jianning (Xiaomi) and expresses big security concerns with this pCR.
==== Revisions Deadline ====
Josep (DT) objects to this pCR.
==== Final Deadline ====
Noted
9.4.1 - - - KI#4 - - Docs:=17 -
9.4.1 S2-2208291 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4 PNI-NPN. Vivo, China Telecom Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) assumes this will be considered merged into S2-2208774.
==== Revisions Deadline ====
Huan (vivo) confirms this contribution is considered merged into S2-2208774.
==== Final Deadline ====
Merged
9.4.1 S2-2208293 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4 SNPN - content of the hosting network selection information. Vivo, China Telecom Rel-18 Merged into S2-2209865 ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged into other tdocs?
Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774
Huan (vivo) confirms this contribution can be considered the evaluation part is merged into 2208444 and conclusion part into S2-2208774.
==== Final Deadline ====
Merged
9.4.1 S2-2208294 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4 SNPN - where and how a UE obtains hosting network selection information. Vivo, China Telecom Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) assumes this will be considered merged into S2-2208774.
==== Revisions Deadline ====
Huan (vivo) confirms this contribution can be considered as merged into S2-2208774.
==== Final Deadline ====
Merged
9.4.1 S2-2208297 P-CR Approval 23.700-08: 23.700-08: Conclusions for KI#4. Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) provides an initial bunch of comments and questions.
Josep (DT) additionally comments. Finds the conclusion too inconclusive
Pallab (Nokia) responds to Josep (DT)
Pallab (Nokia) responds to Antoine (Orange)
==== Revisions Deadline ====
Myungjune (LGE) proposes to merge this to S2-2208774.
Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774
Peter Hedman (Ericsson) provides comments and suggests to mark 'Merged into S2-2208774'
Pallab (Nokia) confirms Merging into S2-2208774
==== Final Deadline ====
Merged
9.4.1 S2-2208317 P-CR Approval 23.700-08: KI#4, Update conclusion on KI#4. Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) raises an ambiguous sentence.
Yishan (Huawei) answers to Antoine (Orange) and provides r01.
Guanzhou (InterDigital) points out revisions of S2-2208774 try to merge 8317 and other KI#4 conclusion proposals.
==== Revisions Deadline ====
Guanzhou (InterDigital) considers this is merged in 8774. Otherwise we object to all versions of this.
==== Final Deadline ====
Merged
9.4.1 S2-2208444 P-CR Approval 23.700-08: KI#4: Evaluation and interim conclusions on automatic Hosting network selection. MediaTek Inc. Rel-18 r04 agreed. Revised to S2-2209865, merging S2-2208293, S2-2208541 and S2-2208773 Peter Hedman (Ericsson) provides r03 based on r01, now I need to re-implement based on r02.
Peter Hedman (Ericsson) provides r04
==== Revisions Deadline ====
Josep (DT) objects to r00.
Huan (vivo) is OK to r04
==== Final Deadline ====
Revised
9.4.1 S2-2209865 P-CR Approval 23.700-08: KI#4: Evaluation and interim conclusions on automatic Hosting network selection. MediaTek Inc., Futurewei, vivo, Ericsson Rel-18 Revision of S2-2208444r04, merging S2-2208293, S2-2208541 and S2-2208773. Approved Approved
9.4.1 S2-2208541 P-CR Approval 23.700-08: KI#4, evaluation update on 7.4.2. Futurewei Rel-18 Merged into S2-2209865 ==== Revisions Deadline ====
Peter Hedman (Ericsson) propose to mark it as 'merged into the revision of S2-2208444'
==== Final Deadline ====
Merged
9.4.1 S2-2208737 P-CR Approval 23.700-08: KI#4, #5, Sol#13: Update to add one precondition for procedure 6.13.3.1. CATT Rel-18 Approved ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged?
==== Final Deadline ====
Liping Wu (CATT) provides comments and ask for approval for this pCR.
Approved
9.4.1 S2-2208773 P-CR Approval 23.700-08: KI #4: Update evaluation of Key Issue #4. Ericsson Rel-18 Merged into S2-2209865 ==== Revisions Deadline ====
Peter Hedman (Ericsson) been merged to 08444
==== Final Deadline ====
Merged
9.4.1 S2-2208774 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4. Ericsson, LG Electronics Rel-18 CC#4: r25 agreed. Revised to S2-2209976. Peter Hedman (Ericsson) provides r01
Saso (Intel) comments on localized service information advertised via SIB
Josep (DT) comments, comments that only S2-2209005 captured automatic/manual selection aspects.
Yishan (Huawei) provides comments and agree with comments from Josep (DT) and Saso (Intel)
Guanzhou (InterDigital) comments and provides r02.
Yishan (Huawei) comments and provides r03.
Guanzhou (InterDigital) responds to Yishan (Huawei).
Peter Hedman (Ericsson) provides r04
Amanda Xiang ( Futurewei ) provides comments and r04
Amanda Xiang ( Futurewei ) provides r05 on top of Ericsson's r04
Antoine (Orange) comments on r05.
Chia-Lin (MediaTek) provides the comments on r05
Josep (DT) comments on r05.
Yishan (Huawei) provides the comments on r05
Pallab (Nokia) provides comments on r05 and has concerns with many conclusions
Huan (vivo) provides comments on r05
Saso (Intel) provides r06 removing the SIB option
Gerald (MATRIXX Software) with comment.
Peter Hedman (Ericsson) provides comments and question on the business relationships possible
Pallab (Nokia) provides r07 based on comments provided earlier
Antoine (Orange) asks Peter why he is discussing roaming interfaces; this is not in the scope of this Study.
Peter Hedman (Ericsson) provides reply to Antoine
Josep (DT) agrees to Peter (Ericsson's proposal) to clearly separate SNPN and PLMN cases.
Huan (vivo) comments
Antoine (Orange) Replies to Huan.
Amanda Xiang ( Futurewei ) provides responses some questions on r05 and provides r08
Genadi (Lenovo) provides comments and r09.
Antoine (Orange) replies to Amanda.
Antoine (Orange) agrees with Genadi.
Guanzhou (InterDigital) can't accept 7c.
Yishan (Huawei) has concerns about 7c and 7d and provides r10.
Chia-Lin (MediaTek) provides r11 based on r10
Peter Hedman (Ericsson) provides r12
Peter Hedman (Ericsson) provides some replies
Antoine (Orange) provides r13.
Chia-Lin (MediaTek) provides r14 based on r13
Huan(vivo) provides r15
Josep (DT) comments on r15, cannot accept point 4 in 8.4.3.
Yishan (Huawei) provides r16 to capture comments from Josep (DT)
Genadi (Lenovo) comments to Chia-Lin (MediaTek) and provides r17.
Miguel (Qualcomm) provides r18
Pallab (Nokia) provides r19
Peter Hedman (Ericsson) provides reply to Josep
Josep (DT) replies to Peter (Ericsson).
Guanzhou (InterDigital) asks Peter (Ericsson) a question
Amanda Xiang ( Futurewei ) provides r20
Peter Hedman (Ericsson) provides r21
Josep (DT) comments.
Naman (Samsung) provides r22 on top of r21
Yishan (Huawei) provides r23
Chia-Lin (MediaTek) provides r24 based on r23
==== Revisions Deadline ====
Josep (DT) asks Rapporteur what the proposed way forward regarding revisions is.
Amanda Xiang ( Futurewei ) prefer to approve r23 as we don't agree with the deletion of some text in r24.
Guanzhou (InterDigital) provides comments on revisions
Josep (DT) is OK to go forward with >=r20, provides some overview of changes in the last five revisions.
Peter Hedman (Ericsson) provides comments, and suggests to approve r24 and only do changes on top if really necessary
Chia-Lin (MediaTek) also suggests to go with r24
Yishan (Huawei) also suggests to go with r24 or r23
Huan (vivo) is OK to r24
Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions.
1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3
2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.'
Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions.
1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3
2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.'
Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions.
1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3
2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.'
Genadi (Lenovo) can only accept r22. Alternatively, we are OK to r24 + reverting 7d with the accompanying EN.
Peter Hedman (Ericsson) suggests r24, or r24 +
'EN: It is FFS whether, e.g. home network, may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting ' +
'EN: (Complementary to Alt.1 in clause 8.4.2 also) It is FFS whether , in case of SNPN as hosting network, the hosting network may broadcast the supported localized service information (e.g. service identifiers and/or human readable service information, such as name, cost, service description) to help UEs discover the service and the hosting network. The localized service identifier may be pre-configured in the UE as per clause 8.4.2. The human readable service information is used for manual hosting network selection. UE may acquire this information from hosting network also via on-demand SIB while UE is RRC_IDLE or RRC_INACTIVE state in serving network.
==== Final Deadline ====
Pallab (Nokia) is OK to agree r24 with below changes. Can also accept r19, objects to all other revisions.
1. Change 'via new UE policy' to 'e.g. via new UE policy' in clause 8.4.3
2. add this in clause 8.4.3 --> '7c. The serving network may broadcast in a SIB an indication that localised service(s) are available in the geographic locality of the cell that is broadcasting.'
Pallab (Nokia) is not OK with updates and requests to have conclusion text as proposed earlier.
Peter Hedman (Ericsson) provides comments with proposal to go for r24 or r24 + changes
Antoine (Orange) comments.
Pallab (Nokia) responds to Peter Hedman (Ericsson)
Peter Hedman (Ericsson) provides updated proposal as per comments
Revised
9.4.1 S2-2209976 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4. Ericsson, LG Electronics, Futurewei Rel-18 Revision of S2-2208774r25. Approved Approved
9.4.1 S2-2208973 P-CR Approval 23.700-08: KI#4: Conclusion for KI#4. InterDigital Rel-18 Merged into (Covered by) S2-2208774 ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged?
Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774
Guanzhou (InterDigital) confirms this is merged into 8774.
==== Final Deadline ====
Merged
9.4.1 S2-2209005 P-CR Approval 23.700-08: KI #4: Conclusion of Key Issue #4. Qualcomm Inc Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) assumes this will be considered merged into S2-2208774.
Miguel (Qualcomm) author confirms this is can be considered merged into S2-2208774 as suggested
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2209167 P-CR Approval 23.700-08: KI #4: Evaluation and Conclusions update. Samsung Rel-18 Merged into (Covered by) S2-2208774 ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged?
Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8774
==== Final Deadline ====
Merged
9.4.1 S2-2209168 P-CR Approval 23.700-08: KI#4: Update Sol#41 and remove ENs. Samsung Rel-18 Approved ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged?
Naman (Samsung) proposes to approve r00
==== Final Deadline ====
Peter Hedman (Ericsson) agree to approve r00.
Approved
9.4.1 S2-2209175 P-CR Approval 23.700-08: Conclusion for key issue#4. Xiaomi Rel-18 Merged into (Covered by) S2-2208774 Antoine (Orange) assumes this will be considered merged into S2-2208774.
Jianning (Xiaomi) is ok to merge this paper into 8774
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 - - - KI#5 - - Docs:=10 -
9.4.1 S2-2208292 P-CR Approval 23.700-08: KI #5: Update of Evaluation and Conclusion of Key Issue #5 PNI-NPN. Vivo, China Telecom Rel-18 Merged into S2-2209867 and S2-2209866 Peter Hedman (Ericsson) provides comments and suggests to merge in evaluation into 08735 and conclusion to 08298
Huan (vivo) agrees to be merged as suggested and is OK with the revision proposal from Peter
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208298 P-CR Approval 23.700-08: 23.700-08: Updates to conclusions for KI#5. Nokia, Nokia Shanghai Bell Rel-18 r10 agreed. Revised to S2-2209866, merging S2-2208318, S2-2208445 and S2-2209006 Antoine (Orange) asks (1) what are the use cases and service requirements for accessing localized services via another network used as underlay and (2) which solution of the TR details how home network services can be accessed using a hosting network as overlay.
Guanzhou (InterDigital) can't accept removing validity info from SoR.
Peter Hedman (Ericsson) provides comments
Pallab (Nokia) responds to Antoine (Orange).
Pallab (Nokia) responds to Guanzhou (InterDigital).
Pallab (Nokia) responds to Peter Hedman (Ericsson)
Pallab(Nokia) provides r01 merging S2-2208318, S2-2208445, S2-2208772, to be taken as the basis for further discussion
Yishan (Huawei) provides r02 to polish the conclusion
Huan (vivo) comments
Peter Hedman (Ericsson) provides r03
Josep (DT) comments.
Antoine (Orange) provides r05.
Guanzhou (InterDigital) comments and provides r04.
Pallab (Nokia) provides r06
Antoine (Orange) provides r07.
Myungjune (LGE) provides r08.
Pallab (Nokia) is OK with r08.
Josep (DT) does not agree r08 is correct. Provides r09
Miguel (Qualcomm) provides r10
==== Revisions Deadline ====
Myungjune (LGE) is ok with r09, r010
Josep (DT) objects to r05-r08. Is OK with 09, r10
Huan (vivo) is ok with r10
Yishan (Huawei) is ok with r10
Pallab (Nokia) proposes to approve r10
Peter Hedman (Ericsson) ok with r10
Chia-Lin (MediaTek) can only accept r10
Guanzhou (InterDigital) is OK with r09/r10.
Miguel (Qualcomm) can only accept r10
Amanda (Futurewei) prefer to approve r10, but can live with r09
==== Final Deadline ====
Revised
9.4.1 S2-2209866 P-CR Approval 23.700-08: 23.700-08: Updates to conclusions for KI#5. Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics Rel-18 Revision of S2-2208298r10, merging S2-2208318, S2-2208445 and S2-2209006. Approved Approved
9.4.1 S2-2208318 P-CR Approval 23.700-08: KI#5, Update conclusion on KI#5. Huawei, HiSilicon Rel-18 Merged into S2-2209866 Peter Hedman (Ericsson) provides comments and suggests we merge in conclusion to 08298
Pallab (Nokia) comments that a revision r01 has been provided in 08298 merging the conclusion content from 08318
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208445 P-CR Approval 23.700-08: KI#5: Evaluation and interim conclusions on UE for accessing the localized services in a registered Hosting network. MediaTek Inc. Rel-18 Merged into S2-2209866 Peter Hedman (Ericsson) provides comments and suggests to merge in evaluation to 08735 and conclusion to 08298
Pallab (Nokia) comments that a revision r01 has been provided in 08298 merging the conclusion content from 8445
Chia-Lin (MediaTek) is ok to merge the pCR to S2-2208298
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208542 P-CR Approval 23.700-08: KI#5, evaluation and conclusion update . Futurewei Rel-18 Noted Guillaume (MediaTek Inc.) comments that the subject of this discussion is wrong (8542): it is commenting on 8452 instead .
Guanzhou (InterDigital) asks questions.
Amanda Xiang ( Futurewei ) replies to InterDigital
Myungjune (LGE) provides comments.
Josep (DT) comments on adding 'if UE is in good coverage of the hosting network' as condition
Pallab (Nokia) provides comments and concurs with concerns raised by other companies
Amanda Xiang ( Futurewei ) provides responses to Nokia, DT and LGE and provide r02
Josep (DT) comments that the issue of coverage is a bit different to that of QoS/QoE.
Amanda Xiang ( Futurewei ) response to DT's comment and provides r03
Myungjune (LGE) comments.
Josep (DT) comments.
Pallab (Nokia) objects to r00-r02
Amanda Xiang ( Futurewei ) provides r04
==== Revisions Deadline ====
Josep (DT) is fine with r04.
Pallab (Nokia) objects to all revisions and proposes to NOTE
Guanzhou (InterDigital) objects to all versions.
Amanda Xiang ( Futurewei ) responses to Nokia and InterDigital
Guanzhou (InterDigital) responds to Amanda (Futurewei).
==== Final Deadline ====
Noted
9.4.1 S2-2208735 P-CR Approval 23.700-08: KI#5: Update evaluation of solutions for KI#5. CATT Rel-18 r04 agreed. Revised to S2-2209867, merging S2-2208292 and S2-2208772 Liping Wu (CATT) provides r01
Amanda Xiang ( Futurewei ) provides r02
Peter Hedman (Ericsson) looks ok and happy to support
Liping Wu (CATT ) provides comments and ask Amanda to align the content between evaluation and conclusion paper.
Amanda Xiang ( Futurewei ) provides r03 to align with the conclusion and evaluation.
Peter Hedman (Ericsson) provides r04
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.4.1 S2-2209867 P-CR Approval 23.700-08: KI#5: Update evaluation of solutions for KI#5. CATT, Futurewei, Ericsson Rel-18 Revision of S2-2208735r04, merging S2-2208292 and S2-2208772. Approved Approved
9.4.1 S2-2208772 P-CR Approval 23.700-08: KI#5: Evaluation and conclusion for Key Issue #5. Ericsson Rel-18 Merged into S2-2209867 and S2-2209866 Pallab (Nokia) proposes to merge the conclusions into 08298 and provides r01 removing the conclusions part. A revision of S2-2208298r01 is provided including the conclusions from this paper.
Peter Hedman (Ericsson) propose to mark the P-CR as merged into 08735 (evaluation) and 08298 (conclusion)
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2209006 P-CR Approval 23.700-08: KI #5: Conclusion of Key Issue #5. Qualcomm Inc. Rel-18 Merged into S2-2209866 Pallab (Nokia) comments and thinks that some of the conclusions are not clear
Josep (DT) comments on hosting network ID.
Peter Hedman (Ericsson) provides comments
Josep (DT) finds Peter's proposal regarding network identifiers OK.
Guanzhou (InterDigital) asks can we assume this is merged in 8298
Pallab (Nokia) proposes to consider this as merged to 8298
==== Revisions Deadline ====
Josep (DT) objects to this pCR.
Guanzhou (InterDigital) considers this is merged in 8298. Otherwise we object to this tdoc.
==== Final Deadline ====
Merged
9.4.1 - - - KI#6 - - Docs:=11 -
9.4.1 S2-2208314 P-CR Approval 23.700-08: KI#6, Update evaluation on KI#6. Huawei, HiSilicon Rel-18 Merged into S2-2209868 Peter Hedman (Ericsson) proposes to merge this into 09073.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208315 P-CR Approval 23.700-08: KI#6, Update conclusion on KI#6. Huawei, HiSilicon Rel-18 Noted Peter Hedman (Ericsson) provides question
Pallab (Nokia) shares the same view as Ericsson
Chia-Lin (MediaTek) shares the same view as Nokia and Ericsson
==== Revisions Deadline ====
Josep (DT) objects to this pCR. Overlapping with main discussion thread in 8771.
Pallab (Nokia) also proposes to NOTE the pCR
==== Final Deadline ====
Noted
9.4.1 S2-2208446 P-CR Approval 23.700-08: KI#6: Evaluation and interim conclusion on the existing mechanism reused for UE returning from Hosting network. MediaTek Inc. Rel-18 Merged into (Covered by) S2-2208771 Peter Hedman (Ericsson) provides comments and propose to mark P-CR as merged into other tdocs
Chia-Lin (MediaTek) is ok to merge to S2-2208771
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208520 P-CR Approval 23.700-08: Conclusion on KI#6. LG Electronics Rel-18 Merged into (Covered by) S2-2208771 Guanzhou (InterDigital) assumes this is merged in S2-2208771?.
Myungjune (LGE) is ok to merge this into S2-2208871.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.4.1 S2-2208736 P-CR Approval 23.700-08: KI#6: Update evaluation for KI#6. CATT Rel-18 Merged into (Covered by) S2-2208771 ==== Revisions Deadline ====
Peter Hedman (Ericsson) I assume this has been merged?
Josep (DT) objects to this pCR because it did not merge a suggested. The discussion is clearly on 8771
==== Final Deadline ====
Liping Wu (CATT) provides comments and ask for marking the pCR 'merged into 2208771'.
Merged
9.4.1 S2-2208771 P-CR Approval 23.700-08: KI#6: Evaluation and conclusion of Key Issue #6. Ericsson, Qualcomm Rel-18 CC#3: r08 agreed. Revised to S2-2209936. Myungjune (LGE) provides r01.
Pallab (Nokia) provides comments on r01.
Myungjune (LGE) replies to Pallab (Nokia).
Peter Hedman (Ericsson) provides r02
Huan (vivo) comments
Guanzhou (InterDigital) provides r03.
Guanzhou (InterDigital) provides r04. And please ignore r03.
Prabhu (NEC) responds to Huan (vivo) and Peter (Ericsson), and provides r05.
Pallab (Nokia) objects to all revisions from r00-r05. Provides r06
Miguel (Qualcomm) responds to Pallab (Nokia), believes informative annex may be overkill
Peter Hedman (Ericsson) provides question why Nokia objects to r00, and provides r07
Guanzhou (InterDigital) provides r08.
Miguel (Qualcomm) still prefers r00 over r06 and r07.
Prabhu (NEC) clarifies a need for new mechanism to address the requirements of KI #6 and provides r09.
Ashok (Samsung) is fine with r08. Not Ok with r09
==== Revisions Deadline ====
Guanzhou (InterDigital) suggests to go with r08.
Myungjune (LGE) support objects r09 and ok with r06 r07, r08.
Pallab (Nokia) responds to Peter Hedman (Ericsson). OK with r06, r07. Objects to all other revisions
Huan (vivo) prefers r08, is ok to r07.
Prabhu (NEC) responds to Ashok (Samsung).
Peter Hedman (Ericsson) ok with r08, r07, r06, r02, r00
Prabhu (NEC) responds to Myungjune (LGE).
Ashok (Samsung) clarifies to Prabhu (NEC)
Chia-Lin (MediaTek) is ok with r07 or r08.
Guanzhou (InterDigital) only accepts r08 and points out other versions have evaluation text which is supposed to be merged with 9073
Miguel (Qualcomm) prefers r00, but can live with r08
Genadi (Lenovo) prefers r08 or r07.
==== Final Deadline ====
Pallab (Nokia) OK with r08.
Revised
9.4.1 S2-2209936 P-CR Approval 23.700-08: KI#6: Evaluation and conclusion of Key Issue #6. Ericsson, Qualcomm, LG Electronics Rel-18 Revision of S2-2208771r08. Approved Approved
9.4.1 S2-2208971 P-CR Approval 23.700-08: KI#6: Update of the evaluation. InterDigital Rel-18 Merged into S2-2209868 Peter Hedman (Ericsson) provides question if we can mark the paper as merged into 09073?
==== Revisions Deadline ====
Guanzhou (InterDigital) confirms this is merged into 9073.
==== Final Deadline ====
Merged
9.4.1 S2-2209073 P-CR Approval 23.700-08: KI#6: Evaluation and conclusion for KI#6. NEC Rel-18 r02 agreed. Revised to S2-2209868, merging S2-2208314 and S2-2208971 Guanzhou (InterDigital) propose r01 that merges S2-2208971. (resent to correct the wrong meeting number in the subject line)
Peter Hedman (Ericsson) provides r02
==== Revisions Deadline ====
Guanzhou (InterDigital) is OK with r02.
==== Final Deadline ====
Revised
9.4.1 S2-2209868 P-CR Approval 23.700-08: KI#6: Evaluation and conclusion for KI#6. NEC, InterDigital Rel-18 Revision of S2-2209073r02, merging S2-2208314 and S2-2208971. Approved Approved
9.4.1 S2-2209139 P-CR Approval 23.700-08: KI#6: Update of the conclusions. InterDigital Rel-18 Noted Prabhu (NEC) provides r01.
Pallab (Nokia) provides comments and raises concerns with the proposal. Proposes to NOTE.
Myungjune (LGE) provides comments.
Chia-Lin (MediaTek) shares the same view as LGE and Nokia
Ashok (Samsung ) comments
Josep (DT) also agrees with others, comments that the approach in this pCR would be difficult to deploy.
Guanzhou (InterDigital) comments.
Prabhu (NEC) responds Josep (DT) and Ashok (Samsung).
==== Revisions Deadline ====
Josep (DT) objects to this pCR. Content is already included in discussion 8771, where the bulk of the discussion happened (e.g. r09 can be considered a merger as it includes avoidance-based)
==== Final Deadline ====
Noted
9.4.1 - - - Documents exceeding TU Budget - - Docs:=4 -
9.4.1 S2-2208312 P-CR Approval 23.700-08: KI#5, Update evaluation on KI#5. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.4.1 S2-2208311 P-CR Approval 23.700-08: KI#4, Update evaluation on KI#4. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.4.1 S2-2208459 P-CR Approval 23.700-08: KI#2: Additional conclusion on SNPN access mode. Intel Rel-18 Not Handled Rainer (Nokia) asks for clarification.
Saso (Intel) replies to Rainer (Nokia).
Rainer (Nokia) replies and is ok with 8459 as is..
Yishan (Huawei) comments
Rainer (Nokia) replies.
Saso (Intel) replies to Yishan.
==== Revisions Deadline ====
Yishan (Huawei) replies.
==== Final Deadline ====
Not Handled
9.4.1 S2-2209174 P-CR Approval 23.700-08: Conclusion for key issue#3. Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.4.2 - - - Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) - - Docs:=8 -
9.4.2 S2-2208426 CR Approval 23.501 CR3714 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 r05 agreed. Revised to S2-2209869. Omkar (CableLabs) provides r01 and comments
Saso (Intel) provides r02 and comments
Ashok (Samsung) comments
Omkar (CableLabs) provides r03 and comments
Saso (Intel) replies to Ashok
Ashok (Samsung) responds to Saso
Saso (Intel) comments on r03 and proposes to focus on r02
Peter Hedman (Ericsson) provides comments/questions
Saso (Intel) replies to Peter
Yishan (Huawei) provides r04
Saso (Intel) provides r05
Peter Hedman (Ericsson) provides reply
==== Revisions Deadline ====
Yishan (Huawei) is ok with r05 and object to r00~r04
Rainer (Nokia) is ok with r05.
Peter Hedman (Ericsson) provides comments that some content is dependent on feedback from CT1
Saso (Intel) proposes to agree the CRs with a note in the official meeting report.
Omkar (CableLabs) is ok with r05, objects to r00.
==== Final Deadline ====
Saso (Intel) checks with the Rapporteur whether this CR (currently marked as approved) needs to be reopened.
Revised
9.4.2 S2-2209869 CR Approval 23.501 CR3714R1 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 Revision of S2-2208426r05. Approved (Some content is dependent on feedback from CT WG1) Agreed
9.4.2 S2-2208427 CR Approval 23.502 CR3565 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
9.4.2 S2-2208512 CR Approval 23.502 CR3569 (Rel-18, 'B'): Equivalent SNPN support OPPO, Ericsson, Nokia, Nokia Shanghai Bell, Mediatek Inc., LG Electronics Rel-18 Approved Marco (Huawei) comments that the CR to 23.502 needs to be aligned to 23.501 on UE capability
==== Revisions Deadline ====
Myungjune (LGE) proposes to approve r00.
Fei (OPPO) replies.
Peter Hedman (Ericsson) agree that it make sense to agree r00
Peter Hedman (Ericsson) agree to approve r00
==== Final Deadline ====
Agreed
9.4.2 S2-2208767 CR Approval 23.501 CR3730 (Rel-18, 'B'): Equivalent SNPN support Ericsson, OPPO, LG Electronics, Nokia, Nokia Shanghai Bell, MediaTek Inc. Rel-18 Approved Yishan (Huawei) asks for clarification
Fei (OPPO) responds to Yishan (Huawei).
Yishan (Huawei) responds to Fei (OPPO) and provides r01.
Myungjune (LGE) replies to Yishan (Huawei)
Fei (OPPO) agree with Myungjune
Yishan (Huawei) asks questions
Fei (OPPO) provided response to Yishan
Peter Hedman (Ericsson) provides reply
Yishan (Huawei) replies to Peter Hedman (Ericsson) and Fei (OPPO) and agree to send the LS to CT1
Myungjune (LGE) replies to Yishan (Huawei).
Yishan (Huawei) answers.
Peter Hedman (Ericsson) provides question
Yishan (Huawei) answers to Peter Hedman (Ericsson)
==== Revisions Deadline ====
Myungjune (LGE) objects r01 and proposes to approve r00.
Rainer (Nokia) supports r00.
Fei (OPPO) supports r00
==== Final Deadline ====
Agreed
9.4.2 S2-2208429 CR Approval 23.503 CR0745 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 r03 agreed. Revised to S2-2209870. Peter Hedman (Ericsson) provides questions
Saso (Intel) replies to Peter; provides r01
Marco (Huawei) provide r02
Saso (Intel) is OK with r02
Josep (DT) comments, provides r03.
Saso (Intel) is OK with r03
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comments, and CR depends on CT1 feedback
Saso (Intel) replies to Peter Hedman (Ericsson) that there is no intent to introduce SNPN access mode to EPS/EPC.
==== Final Deadline ====
Revised
9.4.2 S2-2209870 CR Approval 23.503 CR0745R1 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 Revision of S2-2208429r03. Approved Agreed
9.4.2 S2-2208434 CR Approval 23.402 CR2997 (Rel-18, 'B'): Support of Non-3GPP access for SNPN Intel, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo Rel-18 Approved ==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comment that usage of SNPN access mode depends on CT1 feedback, and assume we do not propose to introduce SNPN access mode to EPS/EPC.
Saso (Intel) replies to Peter Hedman (Ericsson) that there is no intent to introduce SNPN access mode to EPS/EPC.
==== Final Deadline ====
Agreed
9.5 - - - Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) - - Docs:=16 -
9.5 - - - LS’s in - - Docs:=1 -
9.5 S2-2208168 LS In Action LS from MITRE Engenuity Open Generation 5G Consortium: MITRE Engenuity Open Generation 5G Consortium (S2-2208168) Postponed Stefano Faccin (Qualcomm) proposes to postpone answering to this LS Postponed
9.5 - - - KI#1 - - Docs:=4 -
9.5 S2-2208983 P-CR Approval 23.700-58: KI#1: Solution #4 update. InterDigital Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.5 S2-2208975 P-CR Approval 23.700-58: KI#1: Update to evaluation. InterDigital Rel-18 Approved Pallab (Nokia) comments and requests for clarification
Guanzhou (InterDigital) responds to Pallab (Nokia).
Pallab (Nokia) responds to Guanzhou (InterDigital)
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.5 S2-2208301 P-CR Approval 23.700-58: 23.700-58: Updates to conclusions for KI#1. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2209579. Guanzhou (InterDigital) comments and provides r01
Pallab (Nokia) responds to Guanzhou (InterDigital)
Guanzhou (InterDigital) responds to Pallab (Nokia).
Ashok (Samsung) need clarification
Shabnam (Ericsson) provides comments
Ashok (Samsung) responds to Shabnam (Ericsson)
Guanzhou (InterDigital) responds to Shabnam(Ericsson)
==== Revisions Deadline ====
Shabnam (Ericsson) thanks for the clarification, I wonder do you plan to address this with soln in future or should we change the EN to a NOTE stating restricted discovery is not supported? Do you believe existing ProSe mechanism can't be reused, I thought that can be reused in cases as described when under MNO.
Guanzhou (InterDigital) accepts only r01 and objects to other versions.
==== Final Deadline ====
Revised
9.5 S2-2209579 P-CR Approval 23.700-58: 23.700-58: Updates to conclusions for KI#1. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208301r01. Approved Approved
9.5 - - - KI#2 - - Docs:=3 -
9.5 S2-2209122 P-CR Approval 23.700-58: TR 23.700-58 Conclusions Key Issue #2. Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2209580, merging S2-2209079 Guanzhou (InterDigital) provides r01.
Antoine (Orange) comments on the 1st bullet.
Stefano (Qualcomm) provides R02.
Runze (Huawei) provides R03.
Runze (Huawei) provides URL of R03.
==== Revisions Deadline ====
Runze (Huawei) supports R03 only, but no other versions.
==== Final Deadline ====
Revised
9.5 S2-2209580 P-CR Approval 23.700-58: TR 23.700-58 Conclusions Key Issue #2. Qualcomm Incorporated, Huawei Rel-18 Revision of S2-2209122r03, merging S2-2209079. Approved Approved
9.5 S2-2209079 P-CR Approval 23.700-58: Conclusion of Key Issue 2. Huawei, HiSilicon Rel-18 Merged into S2-2209580 Guanzhou (InterDigital) suggests this is merged in 9122.
Runze (Huawei) is fine to merge this paper into 2209122
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.5 - - - KI#3 - - Docs:=8 -
9.5 S2-2208780 P-CR Approval 23.700-58: KI#3, Sol#7 Clarifications & address eNs. Ericsson Rel-18 Approved Guanzhou (InterDigital) comments and asks for clarifications.
Shabnam (Ericsson) provides comments sorry I seems I have missed a few emails including this one ?? bad macros
==== Revisions Deadline ====
Guanzhou (InterDigital) comments.
==== Final Deadline ====
Approved
9.5 S2-2208299 P-CR Approval 23.700-58: 23.700-58: Updates to evaluation for KI#3. Nokia, Nokia Shanghai Bell, InterDigital Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.5 S2-2209082 P-CR Approval 23.700-58: KI#3: Evaluation update. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209581. Guanzhou (InterDigital) comments and provides r01.
Runze (Huawei) accepts r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.5 S2-2209581 P-CR Approval 23.700-58: KI#3: Evaluation update. Huawei, HiSilicon Rel-18 Revision of S2-2209082r01. Approved Approved
9.5 S2-2209083 P-CR Approval 23.700-58: KI#3: interim Conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209582 Pallab (Nokia) proposes to NOTE this paper. As discussed in the evaluation paper S2-2208299, we believe the network based DAA mechanism does not work in practical cases. So we do not agree to take Sol#2 into normative phase.
Runze (Huawei) proposed to merge the paper into 2209129.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.5 S2-2208300 P-CR Approval 23.700-58: 23.700-58: Conclusion for KI#3. Nokia, Nokia Shanghai Bell, InterDigital Rel-18 Merged into S2-2209582 Stefano Faccin (Qualcomm) proposes to merge into 9129
Pallab (Nokia) agrees to merge into 9129
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.5 S2-2209129 P-CR Approval 23.700-58: TR 23.700-58 Conclusions Key Issue #3. Qualcomm Incorporated Rel-18 r05 agreed. Revised to S2-2209582, merging S2-2208300 and S2-2209083 Guanzhou (InterDigital) propose r01.
Guanzhou (InterDigital) propose r01. (resent to correct the wrong meeting number in the subject line)
Shabnam (Ericsson) provides comments and r02 to include area specific DAA
Shabnam (Ericsson) provides r03 adding Ericsson as supporting company and clarify soln# which was missed.
Stefano Faccin (Qualcomm) comments and is supportive
Runze (Huawei) provides r04.
Guanzhou (InterDigital) provides r05
==== Revisions Deadline ====
Guanzhou (InterDigital) accepts r05 and r01 and objects to other versions.
Runze (Huawei) supports r04 and r05, objects to other versions.
==== Final Deadline ====
Revised
9.5 S2-2209582 P-CR Approval 23.700-58: TR 23.700-58 Conclusions Key Issue #3. Qualcomm Incorporated, Ericsson, InterDigital Rel-18 Revision of S2-2209129r05, merging S2-2208300 and S2-2209083. Approved Approved
9.6 - - - Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) - - Docs:=0 -
9.7.1 - - - Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) - - Docs:=48 -
9.7.1 - - - Key Issue #1 - - Docs:=19 -
9.7.1 S2-2208398 P-CR Approval 23.700-25: KI #1, Sol #14: Update to address ENs. Ericsson Rel-18 Noted Sebastian (Qualcomm) objects to the PCR
Shabnam (Ericsson) provides comments with r01, as noted we may not choose taking this on board in Rel-18, we would like to update the solution to correct and answer questions for completeness. The EN is still there.
Sebastian (Qualcomm) replies
Shabnam (Ericsson) and we are providing updates to soln already in the TR to address your comments right and we have not removed the EN which says whether it is in scope is FFS, so no contradiction here other than cleanup of the TR.
==== Revisions Deadline ====
Sebastian (Qualcomm) objects to r01
==== Final Deadline ====
Noted
9.7.1 S2-2208399 LS OUT Approval [DRAFT] LS on 5G Timing Resiliency Ericsson Rel-18 Noted Shabnam (Ericsson) provides r01 as discussed in offline call
Sebastian (Qualcomm) objects to the LS for the same reasons as given for S2-2208398
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.7.1 S2-2208400 DISCUSSION Decision FS_5TRS_URLLC, KI #1: 5GS network timing synchronization status and reporting Ericsson Rel-18 Noted Sebastian (Qualcomm) comments
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.7.1 S2-2208403 P-CR Approval 23.700-25: KI #1, Annex A: An alternative to report a time synchronization status to UEs. Ericsson Rel-18 r03 agreed. Revised to S2-2209871. Rapporteur: Handle independently Sebastian (Qualcomm) comments
Shabnam (Ericsson) provides comments and r02, please ignore r01 as I missed one comment from Qualcomm in that revision.
Sebastian (Qualcomm) provides r03
==== Revisions Deadline ====
Sebastian (Qualcomm) is fine with r03, objects to other versions.
==== Final Deadline ====
Revised
9.7.1 S2-2209871 P-CR Approval 23.700-25: KI #1, Annex A: An alternative to report a time synchronization status to UEs. Ericsson Rel-18 Revision of S2-2208403r03. Approved Approved
9.7.1 S2-2208554 P-CR Approval 23.700-25: Conclusion for key issue 1. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209875 Rapporteur: Merge into S2-2209101 Shabnam (Ericsson) provides comments that we would not like to include any conclusion on SIB without RAN consultation. Issues we see are described in 8400, will take the discussion under 9101 as proposed by rapporteur.
Devaki (Nokia) proposes that this is merged with 9103.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208555 P-CR Approval 23.700-25: Annex to capture methods to notify UE regarding RAN time sync for KI#1 . Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2209872. Rapporteur: Handle independently Shabnam (Ericsson) provides comments ok with the proposal but we also added a general EN on our Annex submission for RAN dependency, additional question
Devaki (Nokia) replies to Shabnam.
Sebastian (Qualcomm) comments
zhendong (ZTE) comments
Devaki (Nokia) provides r01.
Sebastian (Qualcomm) provides r02
==== Revisions Deadline ====
Sebastian (Qualcomm) is fine with r02 if the figure is aligned with the text (remove step 2; replace steps 8-10 by one step 'UE enters RRC_Connected', renumber figure and text); objects to other versions
Devaki (Nokia) uploaded r03 before the deadline (with fix for the figure) but the email was not sent to the reflector by mistake.
==== Final Deadline ====
Revised
9.7.1 S2-2209872 P-CR Approval 23.700-25: Annex to capture methods to notify UE regarding RAN time sync for KI#1 . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208555r03. Approved Approved
9.7.1 S2-2208609 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#1. Samsung Rel-18 Merged into S2-2209875 Rapporteur: Merge into S2-2209101 Devaki (Nokia) proposes that this is merged with 9103.
Sang-Jun (Samsung) agrees that this is merged with 9103.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208626 P-CR Approval 23.700-25: KI#1: Conclusion proposal. Huawei, HiSilicon Rel-18 Merged into S2-2209875 Rapporteur: Merge into S2-2209101 Devaki (Nokia) proposes that this is merged with 9103.
Runze (Huawei) agrees to merge this paper into 9103.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208955 P-CR Approval 23.700-25: KI#1 adding the notifying UE time sync status method to Annex. ZTE Rel-18 r01 agreed. Revised to S2-2209873. Rapporteur: Handle independently Shabnam (Ericsson) provides comments that the proposal is similar to Ericsson one in 8403, whether ZTE sees opportunity to merge?
zhendong (ZTE) provides the response
Sebastian (Qualcomm) comments
zhendong (ZTE) provides r01
==== Revisions Deadline ====
Runze (Huawei) comments on r01
Zhendong (ZTE) provides the response to runze (huawei)
Sebastian (Qualcomm) supports Zhendong
==== Final Deadline ====
Revised
9.7.1 S2-2209873 P-CR Approval 23.700-25: KI#1 adding the notifying UE time sync status method to Annex. ZTE Rel-18 Revision of S2-2208955r01. Approved Approved
9.7.1 S2-2209101 P-CR Approval 23.700-25: KI#1: Update solution 1 to clarify SIB aspects and add details in annex on ciphering of time synchronization status in SIB. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2209874. Rapporteur: Handle independently (solution update not needed) Josep (DT) supports this approach, would like to co-sign.
Shabnam (Ericsson) provides comments as depending on responses and potential merger revision may be provided later.
Shabnam (Ericsson) provides comments for additional update as per offline discussion
Sebastian (Qualcomm) provides r01
Sebastian (Qualcomm) replies to Josep
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.7.1 S2-2209874 P-CR Approval 23.700-25: KI#1: Update solution 1 to clarify SIB aspects and add details in annex on ciphering of time synchronization status in SIB. Qualcomm Incorporated, Deutsche Telekom Rel-18 Revision of S2-2209101r01. Approved Approved
9.7.1 S2-2209103 P-CR Approval 23.700-25: Conclusion for key issue 1. Qualcomm Rel-18 r07 agreed. Revised to S2-2209875, merging S2-2208554, S2-2208609 and S2-2208626 Rapporteur: Handle independently. (isolated issue on information reported) Jari (NTT DOCOMO) comments
Devaki (Nokia) provides r01 and comments.
Shabnam (Ericsson) provides comments and r02, clarifying some aspects and adding EN on RAN dependency and co-signs
Sebastian (Qualcomm) replies to Jari
Jari (NTT DOCOMO) responds to Sebastian
Sebastian (Qualcomm) provides r03
Runze (Huawei) provides r04.
Shabnam (Ericsson) provides comments and r05
Sebastian (Qualcomm) provides r06
Shabnam (Ericsson) provides comments that the updated text is not making sense see below, provides r07
Runze (Huawei) replies to Sebastian (Qualcomm).
==== Revisions Deadline ====
Runze (Huawei) supports r04, r06, r07, and objects to other versions.
==== Final Deadline ====
Revised
9.7.1 S2-2209875 P-CR Approval 23.700-25: Conclusion for key issue 1. Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, AT&T, Verizon, Huawei Rel-18 Revision of S2-2209103r07, merging S2-2208554, S2-2208609 and S2-2208626. Approved Approved
9.7.1 S2-2209118 P-CR Approval 23.700-25: Conclusions based on the reply from ITU-T SG15 Q13/Q15 on monitoring of time synchronization and relevant parameters. Qualcomm Incorporated Rel-18 Postponed Shabnam (Ericsson) provides comments and r01 on Ericsson view and analysis for the LS response, though it is not yet available for 3GPP.
==== Revisions Deadline ====
Shabnam (Ericsson) comments that to be fair since 3GPP/SA2 has not yet officially received any response and we are creating Annex to capture different options, we should note this paper. though I would encourage companies to review the r01 and consider their responses so we have a common view to work from next meeting.
Devaki (Nokia) proposes to postpone this paper as we are waiting for the LS response officially (we cannot accept r01 however).
Sebastian (Qualcomm) objects to r01; disagrees with most of the observations in r01 as they go beyond what is contained in the ITU-T LS; r01 also mistakenly assumes that the network would need to calculate the end-to-end accuracy and provide it to the UE but that has not been proposed; Sebastian (Qualcomm) is ok to postpone the paper; suggests to have an offline call soon after this meeting to try to converge on the open points (see email for details)
==== Final Deadline ====
Postponed
9.7.1 S2-2209169 LS OUT Approval [DRAFT] LS on Time Synchronization Status notification towards UE(s) Nokia, Nokia Shanghai Bell Rel-18 r03 agreed. Revised to S2-2209876. Rapporteur: Use this as the baseline for time sync status notification Shabnam (Ericsson) provides r01
Sebastian (Qualcomm) provides r02
Devaki (Nokia) provides r03.
==== Revisions Deadline ====
Sebastian (Qualcomm) is ok with r03 and r02; objects to other versions.
Runze (Huawei) prefers rev03.
==== Final Deadline ====
Revised
9.7.1 S2-2209876 LS OUT Approval LS on Time Synchronization Status notification towards UE(s) SA WG2 Rel-18 Revision of S2-2209169r03. Approved Approved
9.7.1 - - - Key Issue #2 - - Docs:=9 -
9.7.1 S2-2208401 P-CR Approval 23.700-25: KI#2, Sol#7: Evaluation of the deferred 5GC-MT-LR-based approach. Ericsson Rel-18 Noted Scott (Inspur) objects the paper.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.7.1 S2-2208477 P-CR Approval 23.700-25: TR 23.700-25-040: Updates to the solutions of Key Issue #2 . Inspur Rel-18 Merged into S2-2209877 Rapporteur: 5GC-MT-LR-based approach – variant #2 Shabnam (Ericsson) provides comments that no budget for soln update as per workplan, Objects proposal to change/revise the solution at this point.
Devaki (Nokia) proposes to merge (and discuss) the conclusion aspects (not related to MT-LR) under 8556.
Scott(Inspur) replies.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208478 P-CR Approval 23.700-25: TR 23.700-25-040: Updates to the conclusion of Key Issue #2 . Inspur Rel-18 Noted Shabnam (Ericsson) provides comments as explained in 8401 and as we see no need to have multiple solns for the same issue & as we are only focusing on TA level and homogeneous TA status across RA as Qualcomm is proposing no need for additional complexity of this mechanism, we Object inclusion of this approach.
Sebastian (Qualcomm) supports the comments provided by Ericsson and objects to the pCR
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.7.1 S2-2208556 P-CR Approval 23.700-25: Conclusion for key issue 2 update to address the EN. Nokia, Nokia Shanghai Bell, Ericsson Rel-18 r03 agreed. Revised to S2-2209877, merging S2-2208477, S2-2208791, S2-2209116 and S2-2208627 Rapporteur: Can we this as the baseline for conclusion to capture the way forward regarding cell level granularity for coverage? Variant #1 Jari (NTT DOCOMO) comments
Devaki (Nokia) comments
Devaki (Nokia) provides r01.
Jari (NTT DOCOMO) provides r02
Sebastian (Qualcomm) provides r03
Devaki (Nokia) provides r04 for consideration.
Jari (NTT DOCOMO) responds to Devaki
==== Revisions Deadline ====
Devaki (Nokia) comments.
Sebastian (Qualcomm) can only accept r03; objects to other versions
Runze (Huawei) proposes to agree r03, but keep the last EN (Editor's note: How ASTI service activation/deactivation is impacted by TA or Cell level Requested Coverage Area is FFS.) in r03.
Sebastian (Qualcomm) objects to proposal by Runze to keep the last EN in r03; we can only accept r03 as-is and object to other versions.
Shabnam (Ericsson) proposes to go with r03, we concluded we will only use TA level for this release and if any Interactions with ASTI arises for TA then we will need to address that as part of the process?
==== Final Deadline ====
Runze (Huawei) can live with r03 as is.
Revised
9.7.1 S2-2209877 P-CR Approval 23.700-25: Conclusion for key issue 2 update to address the EN. Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2208556r03, merging S2-2208477, S2-2208791, S2-2209116 and S2-2208627. Approved Approved
9.7.1 S2-2208627 P-CR Approval 23.700-25: KI#2: Update of conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209877 Merged into S2-2208556? Devaki (Nokia) proposes that this is merged with 8556.
Sebastian (Qualcomm) objects to the PCR
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208791 P-CR Approval 23.700-25: KI#2: Update conclusion for time synchronization service enhancements. CATT Rel-18 Merged into S2-2209877 Rapporteur: Handle independently Devaki (Nokia) proposes that this is merged with 8556.
Yuan Tao (CATT) confirms this paper is merged with 8556.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208956 P-CR Approval 23.700-25: KI#2, update the conclusion for the kI#2. ZTE Rel-18 Noted Sebastian (Qualcomm) objects to the PCR
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.7.1 S2-2209116 P-CR Approval 23.700-25: Removing Editor's note on cell level granularity for coverage area. Qualcomm Incorporated Rel-18 Merged into S2-2209877 Rapporteur: Cell level coverage area - Variant #2 Devaki (Nokia) proposes that this is merged with 8556.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 - - - Key Issue #3 - - Docs:=2 -
9.7.1 S2-2208557 P-CR Approval 23.700-25: Conclusions for KI#3 . Nokia, Nokia Shanghai Bell, NTT DOCOMO, Ericsson, ZTE Rel-18 r04 agreed. Revised to S2-2209878. Rapporteur: Use this as the baseline. Devaki (Nokia) provides r01 as per offline discussion to allow the option to restrict coverage area and/or allow any coverage area in the subscription.
Sang-Jun (Samsung) provides r02 with a small editorial change and adding Samsung as co-signer.
Runze (Huawei) provides r03.
Sebastian (Qualcomm) provides r04
Runze (Huawei) replies to Sebastian (Qualcomm), and provides r05.
Sebastian (Qualcomm) replies
==== Revisions Deadline ====
Runze (Huawei) replied to Sebastian (Qualcomm).
Devaki (Nokia) comments.
Shabnam (Ericsson) provides comments and supports Nokia analysis but prefers to go with r04, can also accept r00. Revisions r01, r02, r03, r05 not acceptable as they either introduces wrong concept or ambiguity.
Devaki (Nokia) proposes that we go with original version and work on the newly added bullet for next meeting. R04 is fine as well; r04+ '(optionally) an indication to allow AF requested Uu time synchronization error budget, start/stop time and/or Coverage Area always accepted' is also fine.
Sebastian (Qualcomm) is ok with r00 and r04; objects to other versions; proposes to go for r04 with additional EN: 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'
Runze (Huawei) agrees with Sebastian (Qualcomm)'s proposal that go for r04 with additional EN: 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'.
Runze (Huawei) objects to r00-r04 (without the EN)
Devaki (Nokia) comments that r04 + proposed EN is fine.
Shabnam (Ericsson) can accept r04 + proposed EN but wonders if the EN should start with 'Whether and then how...' .
Sebastian (Qualcomm) supports Shabnam's (Ericsson) proposal. Also ok to start with 'Whether and then how...'
Runze (Huawei) don't agree the EN start with 'Whether and then how...', insist the previous wording.
==== Final Deadline ====
Devaki (Nokia) comments that we should stick with 'Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'.
Devaki (Nokia) proposes to go with r03 with 'enabling an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS' as discussed.
Runze (Huawei)agrees with Devaki (Nokia)'s proposal to go with r03 with 'enabling an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS'.
Runze (Huawei) provides r06 in the revision and CC#4 folder as final revision, per chair's guidance.
Devaki (Nokia) agrees with r06, reflects the proposal also from QCOM and E///.
Revised
9.7.1 S2-2209878 P-CR Approval 23.700-25: Conclusions for KI#3 . Nokia, Nokia Shanghai Bell, NTT DOCOMO, Ericsson, ZTE, Samsung, Huawei Rel-18 Revision of S2-2208557r04. Approved Approved
9.7.1 - - - Key Issue #5 - - Docs:=2 -
9.7.1 S2-2208957 P-CR Approval 23.700-25: KI#5, update the conclusion for the KI#5. ZTE Rel-18 Merged into (Covered by) S2-2208187 Devaki (Nokia) proposes that this is merged with 8187.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208187 P-CR Approval 23.700-25: Update on conclusions for KI#5. NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei, Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.7.1 - - - Key Issue #6 - - Docs:=12 -
9.7.1 S2-2208424 LS OUT Approval [DRAFT] LS OUT on UL scenario of reactive RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2209879. Rapporteur: Merge this into S2-2208612? György (Ericsson) provides r01.
Haiyang (Huawei) provides r02.
György (Ericsson) comments.
Haiyang (Huawei) provides reply to György (Ericsson).
zhendong (ZTE) provides r03
==== Revisions Deadline ====
Sebastian (Qualcomm) can only accept r00; objects to other versions; can accept r03 with the following changes: remove 'The mechanism allows the RAN to provide feedback to the AF to change the burst sending time based on the RAN TDD pattern.', remove '. SA2 kindly asks RAN2 to provide feedback on the proposal'; replace 'SA2 asks RAN2 group to kindly provide the feedback' by 'SA2 asks RAN2 group to inform SA2 if RAN2 considers it feasible to extend the reactive adaptation mechanism also to the UL case based on UE feedback to RAN using RRC signalling.'
Haiyang (Huawei) provides r04 as an Alt: which is r03+ removing 'The mechanism allows the RAN to provide feedback to the AF to change the burst sending time based on the RAN TDD pattern.' and '. SA2 kindly asks RAN2 to provide feedback on the proposal'+ Replacing 'SA2 asks RAN2 group to kindly provide the feedback' by 'SA2 asks RAN2 group to inform SA2 if RAN2 considers it feasible to extend the reactive adaptation mechanism also to the UL case based on UE feedback to RAN using RRC signalling.'
==== Final Deadline ====
Revised
9.7.1 S2-2209879 LS OUT Approval LS on UL scenario of reactive RAN feedback for burst sending time adjustment SA WG2 Rel-18 Revision of S2-2208424r04. Approved Approved
9.7.1 S2-2208142 LS In Action LS from RAN WG2: Reply LS on RAN feedback for low latency RAN WG2 (R2-2208913) Rel-18 Noted Sebastian (Qualcomm) proposes to note the LS Noted
9.7.1 S2-2210161 LS OUT Approval [DRAFT] LS on low latency communication applications to use RAN feedback on periodicity for scheduling Samsung Rel-18 CC#4: r00 agreed. Revised to S2-2209964. Sang-Jun (Samsung) provides r00 of S2-2210161 in the revision folder. Revised
9.7.1 S2-2209964 LS OUT Approval LS on low latency communication applications to use RAN feedback on periodicity for scheduling SA WG2 Rel-18 Revision of S2-2210161r00. Approved Approved
9.7.1 S2-2208425 P-CR Approval 23.700-25: Discussion on periodicity provisioning and update conclusion of KI#6. Huawei, HiSilicon, Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209880 Rapporteur: Merge this into S2-2208612? György (Ericsson) comments.
Devaki (Nokia) proposes that this is merged with 8612 as discussed.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208562 P-CR Approval 23.700-25: Conclusion for key issue 6 update to address the ENs and some clarifications. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209880 Rapporteur: Merge this into S2-2208612? György (Ericsson) comments.
Devaki (Nokia) proposes that this is merged with 8612 as discussed.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.1 S2-2208612 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#6. Samsung Rel-18 r06 agreed. Revised to S2-2209880, merging S2-2208425 and S2-2208562 Rapporteur: Can we use this as a baseline for KI#6 conclusion updates? György (Ericsson) comments.
Devaki (Nokia) comments.
Sang-Jun (Samsung) provides r01.
Sang-Jun (Samsung) replies to György (Ericsson).
Jari (NTT DOCOMO) comments.
Sang-Jun (Samsung) provides r02.
Haiyang (Huawei) provides r03.
Sang-Jun (Samsung) provides r04.
György (Ericsson) provides r05.
Sang-Jun (Samsung) replies to György (Ericsson) and proposes to go with r04 as discussed offline.
Devaki (Nokia) comments that the newly proposed EN in r04 is strange (states the obvious that SA1 has to provide requirements which they do already.
Sang-Jun (Samsung) provides r06 based on Devaki (Nokia)'s comments.
==== Revisions Deadline ====
Devaki (Nokia) objects to r05, ok with other versions.
Sebastian (Qualcomm) objects to r05; proposes to go with r04 but replace 'EN: The above industrial applications behaviours regarding periodicity need to be confirmed by SA1.' by 'EN: Whether periodicity values are provided will be determined in a future meeting based on SA1 feedback'
Sang-Jun (Samsung) proposes to go with r06 which is the same as Sebastian (Qualcomm)proposed. That is r04 but replace 'EN: The above industrial applications behaviours regarding periodicity need to be confirmed by SA1.' by 'EN: Whether periodicity values are provided will be determined in a future meeting based on SA1 feedback'
==== Final Deadline ====
Revised
9.7.1 S2-2209880 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#6. Samsung Rel-18 Revision of S2-2208612r06, merging S2-2208425 and S2-2208562. Approved Approved
9.7.1 S2-2208860 P-CR Approval 23.700-25: KI#6: Conclusion update. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209881. Rapporteur: Merge this into S2-2208612? Devaki (Nokia) proposes that this is merged with 8612 as discussed.
Haiyang (Huawei) suggests to keep this paper separately.
Devaki (Nokia) comments that it is fine to treat this paper independently.
György (Ericsson) comments.
Haiyang (Huawei) provides r01.
Haiyang (Huawei) provides r02.
Jari (NTT DOCOMO) comments
Haiyang (Huawei) provides reply to Jari (NTT DOCOMO).
Sebastian (Qualcomm) provides r03
==== Revisions Deadline ====
Sebastian (Qualcomm) is ok with r03, objects to other versions
==== Final Deadline ====
Revised
9.7.1 S2-2209881 P-CR Approval 23.700-25: KI#6: Conclusion update. Huawei, HiSilicon Rel-18 Revision of S2-2208860r03. Approved Approved
9.7.1 S2-2208958 P-CR Approval 23.700-25: KI#6, update the conclusion for the KI#6. ZTE Rel-18 Noted Sebastian (Qualcomm) provides r01
Haiyang(Huawei) checks whether this paper has been merged already
Zhendong (ZTE) provides the response
==== Revisions Deadline ====
Devaki (Nokia) objects to r01, ok with the original version.
Jari (NTTT DOCOMO) objects original and all revisions
Zhendong (ZTE) explains the change, and asks Jari to reconsider
Jari (NTTT DOCOMO) responds to zhendong
==== Final Deadline ====
Noted
9.7.1 - - - Documents exceeding TU Budget - - Docs:=4 -
9.7.1 S2-2208610 P-CR Approval 23.700-25: Conclusion for FS_5TRS_URLLC KI#3. Samsung Rel-18 Not Handled Rapporteur: Merge this with S2-2208557 Devaki (Nokia) proposes that this is merged with 8557.
Sang-Jun (Samsung) agrees that this is merged with 8557.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.7.1 S2-2208628 P-CR Approval 23.700-25: KI#3: Update of conclusion. Huawei, HiSilicon Rel-18 Not Handled Rapporteur: Merge this with S2-2208557 Devaki (Nokia) proposes that this is merged with 8557.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.7.1 S2-2208402 P-CR Approval 23.700-25: KI #2, Conclusion: Update to address the EN. Ericsson Rel-18 Not Handled Rapporteur: Merge this into S2-2208556 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.7.1 S2-2208976 P-CR Approval 23.700-25: KI#5, Update of Solution #9. NTT DOCOMO Rel-18 Not Handled Rapporteur: ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.7.2 - - - 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) - - Docs:=19 -
9.7.2 S2-2208171 DRAFTCR Approval Interworking with TSN network deployed in the transport network NTT DOCOMO Rel-18 Postponed Jari (NTT DOCOMO) provides r01
==== Revisions Deadline ====
zhendong (ZTE) proposes to postpone
==== Final Deadline ====
Postponed
9.7.2 S2-2208558 CR Approval 23.502 CR3574 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2209882, merging S2-2208794 György (Ericsson) comments.
Mirko (Huawei) provides r01.
Devaki (Nokia) comments.
Yuan Tao (CATT) comments.
Mirko (Huawei) responds.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.7.2 S2-2209882 CR Approval 23.502 CR3574R1 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208558r01, merging S2-2208794. Approved Agreed
9.7.2 S2-2208559 CR Approval 23.503 CR0749 (Rel-18, 'B'): AF provides PER to NEF/PCF (as concluded for 23.700-25, KI#4) Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209883 ==== Revisions Deadline ====
Devaki (Nokia) comments that this CR should be unapproved as it was merged with 8795r02 (which must be approved). Sorry, we forgot to mention in this thread earlier.
==== Final Deadline ====
Merged
9.7.2 S2-2208560 DRAFTCR Information TSN support in TN Nokia, Nokia Shanghai Bell Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208561 DRAFTCR Information RAN_BATFeedback_For_ AF_Adaptation Nokia, Nokia Shanghai Bell Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208792 CR Approval 23.501 CR3732 (Rel-18, 'B'): Exposure time synchronization services for requested coverage area CATT Rel-18 Postponed Jari (NTT DOCOMO) comments
Yuan Tao (CATT) provides r01.
zhendong (ZTE) proposes to postpone
Sebastian (Qualcomm) objects to the CR (conclusions are not table yet)
Yuan Tao (CATT) is ok to postpone the CR as offline discussion
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208793 CR Approval 23.502 CR3581 (Rel-18, 'B'): Exposure time synchronization services for requested coverage area CATT Rel-18 Postponed zhendong (ZTE) proposes to postpone
Sebastian (Qualcomm) objects to the CR (conclusions are not table yet)
Yuan Tao (CATT) is ok to postpone the CR as offline discussion
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208794 CR Approval 23.502 CR3582 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS CATT Rel-18 Merged into S2-2209882 Yuan Tao (CATT) confirms this paper is merged into 2208558.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.7.2 S2-2208795 CR Approval 23.503 CR0754 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS CATT Rel-18 r02 agreed. Revised to S2-2209883, merging S2-2208559 Yuan Tao (CATT) provides r01, which merges with 2208559.
Devaki (Nokia) comments that r01 is not accessible (seems to have been uploaded to a wrong revisions folder - DRAFT/REVISIONS.
Yuan Tao (CATT) updates link for r01.
Mirko (Huawei) provides r02.
==== Revisions Deadline ====
Yuan Tao (CATT) is ok with r02.
==== Final Deadline ====
Revised
9.7.2 S2-2209883 CR Approval 23.503 CR0754R1 (Rel-18, 'B'): Support AF Request of PER for QoS and Alt-QoS CATT, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208795r02, merging S2-2208559. Approved Agreed
9.7.2 S2-2208861 CR Approval 23.501 CR3734 (Rel-18, 'B'): RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Postponed zhendong (ZTE) proposes to postpone
Sebastian (Qualcomm) objects to the CR (conclusions are not stable yet)
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208862 CR Approval 23.503 CR0755 (Rel-18, 'B'): Pro-active RAN feedback for burst sending time adjustment Huawei, HiSilicon Rel-18 Postponed zhendong (ZTE) proposes to postpone
Sebastian (Qualcomm) objects to the CR (conclusions are not stable yet)
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208863 CR Approval 23.502 CR3584 (Rel-18, 'B'): CR 23.502 RAN feedback for adaption Huawei, HiSilicon Rel-18 Postponed Haiyang (Huawei) proposes to postpone
Sebastian (Qualcomm) objects to the CR (conclusions are not stable yet)
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208864 CR Approval 23.501 CR3735 (Rel-18, 'B'): Interaction with TSN TN Huawei, HiSilicon Rel-18 Postponed Jari (NTT DOCOMO) proposes to merge with S2-2208171
Haiyang (Huawei) proposes to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208865 CR Approval 23.502 CR3585 (Rel-18, 'B'): Interaction with TSN TN Huawei, HiSilicon Rel-18 Postponed Jari (NTT DOCOMO) proposes to merge with S2-2208972
Haiyang (Huawei) proposes to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208959 CR Approval 23.501 CR3740 (Rel-18, 'B'): Adding time synchronization service area restriction ZTE Rel-18 Postponed zhendong (ZTE) proposes to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208960 CR Approval 23.502 CR3591 (Rel-18, 'B'): Adding time synchronization service area restriction ZTE Rel-18 Postponed zhendong (ZTE) proposes to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.7.2 S2-2208972 DRAFTCR Approval Interworking with TSN network deployed in the transport network NTT DOCOMO Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.8.1 - - - Study on RedCap Phase 2 (FS_RedCAP_Ph2) - - Docs:=0 -
9.8.2 - - - RedCap Phase 2 (NR_RedCAP_Ph2) - - Docs:=14 -
9.8.2 S2-2208117 LS In Action LS from RAN WG3: Reply LS on FS_REDCAP_Ph2 option feasibility RAN WG3 (R3-225119) Rel-18 Revision of Postponed S2-2208098 from S2#152-e. Response drafted in S2-2208655. Noted Qian (Ericsson) proposes to NOTE the LS Noted
9.8.2 S2-2208145 LS In Action LS from RAN WG2: Reply LS on FS_REDCAP_Ph2 option feasibility RAN WG2 (S2-2204989) Rel-18 Noted Steve (Huawei) can be noted Noted
9.8.2 S2-2208655 LS OUT Approval [DRAFT] LS on conclusion of FS_REDCAP_Ph2 Huawei, HiSilicon Rel-18 Response to S2-2208117. Merged into (Covered by) S2-2208258 Steve (Huawei) can be merged to S2-2208258
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.8.2 S2-2208258 LS OUT Approval [DRAFT] LS on long eDRX support for RRC_INACTIVE Ericsson Rel-18 CC#4: r06 agreed. Revised to S2-2209958. Qian (Ericsson) proposes to use this paper as baseline paper for 23.502 CR.
Steve (Huawei) comments, I guess you meant 8527 for the 502 CR?
Qian (Ericsson) withdraw the previous comment since it's meant for 8257.
Qian (Ericsson) provides r01 to merge in the content from 8655
Lars (Sony) we should add RAN2.
Qian (Ericsson) provides r02.
Steve (Huawei) comments on 2 LSs out.
Hannu (Nokia) provides r03.
Steve (Huawei) comments and provides r04
Lars (Sony) should the new paging msg from AMF be included in the list?
Qian (Ericsson) provides comments
Steve (Huawei) comments on still discussing
==== Revisions Deadline ====
Jinguo(ZTE) prefers r03, but we can also live with r02 or r04
Qian (Ericsson) proposes to go with r02, though can live with r03/r04 as well
Qian (Ericsson) comments and provides r06
Lars (Sony) comments
Lars (Sony) is ok with r06
Steve (Huawei) Just the polite indication is all that is required.
Steve (Huawei) is ok with r06
Qian (Ericsson) indicates that r06 is agreeable on top of r02 with updating the 2rd/3rd bullets to below text(highlighted ones are updated):
- The gNB sends an indication to the CN to handle MT communication while the UE is in RRC_INACTIVE state and provides unreachability information (e.g., eDRX values negotiated between UE and gNB for RRC_INACTIVE state). This allows the CN to apply the HLcom functionality (e.g. data buffering, notifications to other network and application functions etc) based on the unreachability information the gNB provided (as described in CR3705 and CR3555).
- If the gNB has indicated the UE has entered RRC_INACTIVE to the CN, the gNB also notifies the CN about the RRC State transition back to RRC_CONNECTED (as described in CR3555).
==== Final Deadline ====
Revised
9.8.2 S2-2209958 LS OUT Approval LS On long eDRX support for RRC_INACTIVE SA WG2 Rel-18 Revision of S2-2208258r06. Approved Approved
9.8.2 S2-2209020 CR Approval 23.501 CR3743 (Rel-18, 'B'): Support of RRC_INACTIVE with eDRX cycle length of more than 10.24s Qualcomm Inc Rel-18 Merged into S2-2209583 Qian (Ericsson) proposes to consider this paper is merged into 8256 or NOTED.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.8.2 S2-2209023 CR Approval 23.502 CR3593 (Rel-18, 'B'): Support of RRC_INACTIVE with eDRX cycle length greater than 10.24s Qualcomm Inc Rel-18 Merged into S2-2209675 Qian (Ericsson) proposes to consider this paper is merged into 8257 or NOTED.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.8.2 S2-2209025 CR Approval 23.700-68 CR0002 (Rel-18, 'F'): Remove editor s note in Conclusion Qualcomm Inc. Rel-18 Merged into (Covered by) S2-2208654 Qian (Ericsson) proposes to consider this paper is merged into 8654 or NOTED.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.8.2 S2-2208256 CR Approval 23.501 CR3705 (Rel-18, 'B'): Support of RRC_INACTIVE with long eDRX Ericsson, Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2209583, merging S2-2209020 Base for normative 23.501 CR. Qian (Ericsson) proposes to use this paper as baseline paper for 23.501 CR.
Lars (Sony) provides r01 and ask about NOTE4.
Jinguo(ZTE) provides r02
Lars (Sony) responds to Jinguo(ZTE)
Qian (Ericsson) provides comments.
Steve (Huawei) comments and provides r03.
Jinguo(ZTE) comments and provides r04
Lars (Sony) does not agree with r04 and r00.
Jinguo(ZTE) replies to Lars (Sony)
Lars (Sony) replies to Jinguo
Qian (Ericsson) comments
Lars (Sony) comments
Steve (Huawei) comments on r04.
Guillaume (MediaTek Inc.) provides r05
Lars (Sony) provides r06
==== Revisions Deadline ====
Qian (Ericsson) proposes to go with r06.
Jinguo(ZTE) is ok with r06.
Steve (Huawei) is ok with r06.
==== Final Deadline ====
Revised
9.8.2 S2-2209583 CR Approval 23.501 CR3705R1 (Rel-18, 'B'): Support of RRC_INACTIVE with long eDRX Ericsson, Huawei, HiSilicon, MediaTek Inc. Rel-18 Revision of S2-2208256r06, merging S2-2209020. Approved Agreed
9.8.2 S2-2208257 CR Approval 23.502 CR3555 (Rel-18, 'B'): Support of RRC_INACTIVE with long eDRX Ericsson, Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2209675, merging S2-2209023 Base for normative 23.502 CR. Qian (Ericsson) proposes to use this paper as baseline paper for 23.502 CR.
Lars (Sony) provides r01.
Qian (Ericsson) comments on r01.
Lars (Sony) responds to Qian (Ericsson).
Steve (Huawei) provides r02
Jinguo(ZTE) provides r03
Lars (Sony) cannot agree on r03
Jinguo(ZTE) comments
Lars (Sony) replies to Jinguo(ZTE)
Qian (Ericsson) comments and provides r04
Chris (Vodafone) provides comment
Hannu (Nokia) provides r05
Jinguo(ZTE) replies to Lars (Sony)
Lars (Sony replies to Jinguo(ZTE)
Steve (Huawei) comments on <10.24
Lars (Sony) responds to Steve that it would not be power efficient an sustainable.
==== Revisions Deadline ====
Qian (Ericsson) provides comments
Qian (Ericsson) proposes to go with r05.
Lars (Sony) is ok with r05.
Jinguo(ZTE) insists to go with r04.
Qian (Ericsson) provides comments.
Jinguo(ZTE) suggests to approve r03. Sorry for confusion.
Steve (Huawei) is ok with r05.
Lars (Sony) as mentioned before we objects to r03.
Qian (Ericsson) asks Jinguo (ZTE) to see if there is a comprised way forward on top of r05.
Jinguo(ZTE) objects to r00, r04, r05, is ok with r03, or r05 + following sentence in step 7 of 4.8.1.1a 'Based on NG-RAN configuration this step may be triggered after step 1'.
Lars (Sony) Are not ok with the additional sentence as proposed.
Qian (Ericsson) provides a comprised way in r06 by adding an EN on top of r05.
Lars (Sony) is ok with the EN in r06 i.e. r05+EN
Steve (Huawei) can live with the EN for the sake of progress.
Jinguo(ZTE) can live with r06
Qian (Ericsson) thanks Jinguo and indicates that it's agreed to add following EN on top of r05 (submitted before revision deadline).
Editor's note: It's FFS on the handling of NG-RAN indication after entering RRC_INACTIVE.
==== Final Deadline ====
Revised
9.8.2 S2-2209675 CR Approval 23.502 CR3555R1 (Rel-18, 'B'): Support of RRC_INACTIVE with long eDRX Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2208257r05, merging S2-2209023. Approved Agreed
9.8.2 S2-2208654 CR Approval 23.700-68 CR0001 (Rel-18, 'F'): Conclusion update for KI#1 Huawei, HiSilicon Rel-18 Approved Qian (Ericsson) proposes to use this paper as baseline paper for 23.700-68 CR.
==== Revisions Deadline ====
==== Final Deadline ====
Agreed
9.8.2 S2-2208760 DISCUSSION Discussion Discussion related to the EN in the TR Conclusion. Sony Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.9 - - - Study on Vehicle Mounted Relays (FS_VMR) - - Docs:=30 -
9.9 - - - Solution Updates - - Docs:=6 -
9.9 S2-2208384 P-CR Approval 23.700-05: KI#3: Update of Solution#17. Huawei, HiSilicon Rel-18 Approved Hong (Qualcomm) asks for clarifications.
LiMeng (Huawei) responds to Hong (Qualcomm).
Hong (Qualcomm) replies to LiMeng.
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.9 S2-2208889 P-CR Approval 23.700-05: KI#4, Solution#6 Update to remove EN. LG Electronics Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.9 S2-2208385 P-CR Approval 23.700-05: KI#5: update of Solution#7. Huawei, HiSilicon Rel-18 Noted Hong (Qualcomm) asks for clarifications.
Alessio(Nokia) comments this solution update is not needed as we already say OAM will provide trigger ot TRP info exchange and this will be when the new cell Id is assigned At integration etc). once this is assigned the LMF knows the MBSR UEID for the cell ID and the cell ID is mobile. the assumption is the cell Id assignment is an OAM event that is therefore usable to trigger TRP exchange from donor gNB.
Alessio(Nokia) cannot accept approving this document (for the record)
LiMeng (Huawei) replies to Hong and Alessio.
==== Revisions Deadline ====
LiMeng (Huawei) replies to Alessio and ask for re-considering his objection.
==== Final Deadline ====
Noted
9.9 S2-2208816 P-CR Approval 23.700-05: KI #5, Sol #19: Update solution #19. CATT Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.9 S2-2208259 P-CR Approval 23.700-05: KI#7, Sol#20, Update to remove ENs . Ericsson Rel-18 r03 agreed. Revised to S2-2209584. Used as the basis for merging in contents from S2-2208386 (Huawei). Qian (Ericsson) provides r01 to consider content from 8386
Hong (Qualcomm) provides comments on r01.
Qian (Ericsson) provides r02
Alessio(Nokia) has some questions:
Qian (Ericsson) responds.
Alessio(nokia) replies
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.9 S2-2209584 P-CR Approval 23.700-05: KI#7, Sol#20, Update to remove ENs . Ericsson Rel-18 Revision of S2-2208259r03. Approved Approved
9.9 - - - Evaluation and conclusions - - Docs:=12 -
9.9 - - - KI#1 - - Docs:=2 -
9.9 S2-2209085 P-CR Approval 23.700-05: TR 23.700-05: KI#1 evaluation and conclusion updates. Qualcomm Incorporated Rel-18 CC#4: r04 agreed. Revised to S2-2209967. Qian (Ericsson) asks questions
LiMeng (Huawei) asks questions
Lars (Sony) as a question
Hong (Qualcomm) replies to Qian, LiMeng, and Lars.
alessio(Nokia)
alessio(Nokia) comments for the aspect of PLMNs where the UE can operate: cannot we use the preferred PLMN list + forbidden PLMNs list mechanisms?
Hong (Qualcomm) replies to Alessio.
Qian (Ericsson) provides further comments.
Hong (Qualcomm) comments.
Qian (Ericsson) provides comments and r01.
alessio(nokia) comments a slice is always need it is a matter of WHICH.
alessio(Nokia) provides r02
Hong (Qualcomm) provides r03.
==== Revisions Deadline ====
LiMeng (Huawei) considers this issue is related to our discussion in KI#4, thus cannot accept all revisions including the original version. Proposes a way forward based on r03.
Hong (Qualcomm) replies to LiMeng.
==== Final Deadline ====
Revised
9.9 S2-2209967 P-CR Approval 23.700-05: TR 23.700-05: KI#1 evaluation and conclusion updates. Qualcomm Incorporated Rel-18 Revision of S2-2209085r04. Approved Approved
9.9 - - - KI#2, 3 - - Docs:=4 -
9.9 S2-2208388 P-CR Approval 23.700-05: KI#2 and KI#3: Evaluation and Conclusion. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209676. Used as the basis for KI#3 (clause 7.3 and 8.3), merging in contents of S2-2208741 (Sony). LiMeng (Huawei) provides r02 with merging the content of S2-2208741, and asks to ignore r01.
Lars (Sony) comments and ask question.
Hong (Qualcomm) comments.
Alessio(Nokia) provides r03 to allow the stable TAC option. of course RAN3 feedback can be taken into account if it is negative
Lars (Sony) disagree with dedicated TAC option.
LiMeng (Huawei) comments on r03.
Alessio(Nokia) comments that a dedicated TAC can be allowed at least within a donor control... change of TAC can be based on change of donor if needed. but this is not really something we should rule out right away as e.g. parial migration based options are still possible.
alessio(Nokia) thinks the donor gNB is in control of the policy of TAC broadcasting so the text we proposed is consistent with that. whether we proceed with one of the options or both we can discuss after we get the feedback from RAN. for now all options should be on equal footing.
Lars (Sony) comments.
alessio(Nokia) ok to consider all the conclusion under a EN.
Lars (Sony) responds to Alessio
==== Revisions Deadline ====
Lars (Sony) objects to r03 at this meeting and propose to go with r02.
alessio(nokia) cannot live with r02. as a compromise we should add an EN to r03 to say that 'both options, stable tA and TA equal to the TA of the donor, require further study'. the truth is that eventually RAN decides what we can do in this space.
Lars (Sony) responds to Alessio.
Hong (Qualcomm) asks if EN + r02 works for Alessio.
Alessio (nokia) r02 works with this note 'Editor's note: the alternatives assuming MBSR operates with dedicated TAC(s) or TAC from Donor are subject to the feedback of RAN WGs'
Qian (Ericsson) supports to extend r02 with an EN.
Lars (Sony) is ok with r02 + EN suggested by Alessio
==== Final Deadline ====
alessio(Nokia) is ok if the note applies to both options... both are subject to RAN evaluations I guess as maybe RAN can have some comment son it as well EN: 'Editor's note the above approach based on using same TA as Donor cell and the approach of using a stable TA rare to be further evaluated jointly with RAN WGs'
Revised
9.9 S2-2209676 P-CR Approval 23.700-05: KI#3: Evaluation and Conclusion. Huawei, HiSilicon, Sony Rel-18 Revision of S2-2208388r02. Approved Approved
9.9 S2-2208733 P-CR Approval 23.700-05: KI#2: Conclusions. Sony, Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2209585. Used as basis for KI#2 (clause 7.2 and 8.2), merging in contents of S2-2208260 (Ericsson) and partial contents of S2-2208388 (Huawei). Qian (Ericsson) provides r01.
Lars (Sony) thanks Qian for the support and is ok with r01.
LiMeng (Huawei) supports the document in general, has a question for the 3rd bullet.
Lars (Sony) responds to LiMeng (Huawei).
LiMeng (Huawei) responds to Lars.
Lars (Sony) responds to LiMeng.
LiMeng (Huawei) provides r02.
Lars (Sony) comments.
==== Revisions Deadline ====
Lars (Sony) is ok with either r01 or r02.
Lars (Sony) is ok with either r02 or r01.
==== Final Deadline ====
Revised
9.9 S2-2209585 P-CR Approval 23.700-05: KI#2: Conclusions. Sony, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2208733r02. Approved Approved
9.9 - - - KI#4 - - Docs:=2 -
9.9 S2-2209086 P-CR Approval 23.700-05: TR 23.700-05: KI#4 evaluation and conclusion updates. Qualcomm Incorporated Rel-18 CC#4: r08 agreed. Revised to S2-2209968. This is to be used as the basis for merging in contents of S2-2209170 (Samsung). Approve r07 + NOTE : Which NAS messageS(registration accept, registration reject or/and deregistration request) is used by the AMF of the MBSR for indicating to the MBSR that it is not allowed to act as MBSR will be determined during normative phase Li Meng (Huawei) asks if we need to provide a revision on this.
Lalith(Samsung) comments.
Alessio(Nokia) provides an updated version in r01
Qian (Ericsson) provides r02
Hong (Qualcomm) comments.
Lalith(Samsung) provides r03
Qian (Ericsson) responds
LiMeng (Huawei) provides r04.
Lalith (Samsung) provides r05.
alessio(nokia) provides r06
Lalith(Samsung) provides r07
Hong (Qualcomm) replies to Qian.
==== Revisions Deadline ====
Lalith(Samsung) objects r02,r04. OK with any other revision. Prefer r07.
Request source company to add 'Samsung' as co-signer.
LiMeng (Huawei) agrees with Qian regarding the issue if MBSR can be the normal UE, therefore objects with all revisions except for r04, propose a way forward.
alessio(Nokia) can only accept r06, r07
Hong (Qualcomm) comments, and accepts r06 or r07.
Hong (Qualcomm) replies to LiMeng.
Lalith(Samsung) proposes to agree r07.
With additional below NOTE.
'NOTE : Which NAS message(registration accept, registration reject or/and deregistration request) is used by the AMF of the MBSR for indicating to the MBSR that it is not allowed to act as MBSR will be determined during normative phase'
Hong (Qualcomm) agrees with Lalith's proposal.
ok r07.
With additional below NOTE.
'NOTE : Which NAS messageS(registration accept, registration reject or/and deregistration request) is used by the AMF of the MBSR for indicating to the MBSR that it is not allowed to act as MBSR will be determined during normative phase'
==== Final Deadline ====
Revised
9.9 S2-2209968 P-CR Approval 23.700-05: TR 23.700-05: KI#4 evaluation and conclusion updates. Qualcomm Incorporated, Samsung Rel-18 Revision of S2-2209086r08. Approved Approved
9.9 - - - KI#5 - - Docs:=3 -
9.9 S2-2208387 P-CR Approval 23.700-05: KI#5: Update of evaluation and conclusion. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2209586. This is to be used as the basis for merging in contents of S2-2208261 (Ericsson). LiMeng (Huawei) provides r01.
Lars (Sony) ask a question to LiMeng (Huawei).
Hong (Qualcomm) comments and provides r02.
Lars (Sony) provides r03.
LiMeng (Huawei) comments.
Lars (Sony) responds to LiMeng.
alessio(Nokia) provides r04
Hong (Qualcomm) responds to LiMeng.
LiMeng (Huawei) r provides r05.
==== Revisions Deadline ====
Lars (Sony) is ok with r05.
alessio(Nokia) can live with r05
Qian (Ericsson) is ok with r05
==== Final Deadline ====
Revised
9.9 S2-2209586 P-CR Approval 23.700-05: KI#5: Update of evaluation and conclusion. Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2208387r05. Approved Approved
9.9 S2-2208815 P-CR Approval 23.700-05: KI #5: Update conclusion of KI#5. CATT Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.9 - - - KI#6 - - Docs:=1 -
9.9 S2-2208529 P-CR Approval 23.700-05: KI#6 Conclusion Update . Rakuten Mobile Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.9 - - - KI#7 - - Docs:=4 -
9.9 S2-2208262 P-CR Approval 23.700-05: KI#7, Evaluation and Conclusion. Ericsson Rel-18 r08 agreed. Revised to S2-2209587. This is to be used as the basis for clause 8.7, merging in contents of S2-2208179 (IPLOOK), S2-2208389 (Huawei), S2-2209084 (Qualcomm) and S2-2209151 (Intel). Qian (Ericsson) provides r01 considering the content from 8179/8389/9084/9151
Lalith(Samsung) request for clarification on r01.
Qian (Ericsson) responds.
Lalith (Samsung) responds.
Hong (Qualcomm) comments.
Qian (Ericsson) provides comments.
alessio(Nokia) comments
Lalith (Samsung) provides r03.
Kindly skip r02 there were some errors.
Lalith(Samsung) comments
alessio(Nokia0 provides r04
Qian (Ericsson) provides comments and r05
Aoken (Rakuten Mobile) provides comments and r06
LiMeng (Huawei) comments and provides r07.
Lalith(Samsung) comments.
Xiaoyan Shi (Intel) comments.
alessio(nokia) having read the comments by Lalit on energy efficiency I update the paper to r08
==== Revisions Deadline ====
Qian (Ericsson) is ok with r08
Lalith(Samsung) is ok with r08. I request source company to add 'Samsung' as co-signer before upload.
Xiaoyan Shi(Intel) is ok with r08. Question mark on Intel in the co-sign company can be removed.
Hong (Qualcomm) is fine with r08.
==== Final Deadline ====
Revised
9.9 S2-2209587 P-CR Approval 23.700-05: KI#7, Evaluation and Conclusion. Ericsson, Huawei, HiSilicon, Qualcomm, Intel, Samsung, IPLOOK, Rakuten Mobile Rel-18 Revision of S2-2208262r08. Approved Approved
9.9 S2-2209084 P-CR Approval 23.700-05: TR 23.700-05: KI#7 evaluation and conclusion. Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2209588. This is to be used as the basis for clause 7.7, merging in contents of S2-2208179 (IPLOOK), S2-2208389 (Huawei), S2-2208262 (Ericsson) and S2-2209151 (Intel). LiMeng (Huawei) wonders if we shall provide the revision.
Qian (Ericsson) comments.
Hong (Qualcomm) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.9 S2-2209588 P-CR Approval 23.700-05: TR 23.700-05: KI#7 evaluation and conclusion. Qualcomm Incorporated Rel-18 Revision of S2-2209084r01. Approved Approved
9.9 - - - Documents exceeding TU Budget - - Docs:=8 -
9.9 S2-2208386 P-CR Approval 23.700-05: KI#7: update of Solution#20. Huawei, HiSilicon Rel-18 Not Handled Contents to be merged into S2-2208259 (Ericsson). Incorrect clause number for 6.20.2.2. ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2208260 P-CR Approval 23.700-05: KI#2, Evaluation updates and Conclusion. Ericsson Rel-18 Not Handled Contents to be merged into S2-2208733 (Sony, Nokia). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2208741 P-CR Approval 23.700-05: KI#3: Conclusions. Sony Rel-18 Not Handled Contents to be merged into S2-2208388 (Huawei). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2208261 P-CR Approval 23.700-05: KI#5, Evaluation and Conclusion updates. Ericsson Rel-18 Not Handled Contents to be merged into S2-2208387 (Huawei). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2208179 P-CR Approval 23.700-05: KI#7: Evaluation of Solution for KI#7. IPLOOK Rel-18 Not Handled Contents to be merged into S2-2208262 (Ericsson) and S2-2209084 (Qualcomm). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2208389 P-CR Approval 23.700-05: KI#7:Evaluation and Conclusion. Huawei, HiSilicon Rel-18 Not Handled Contents to be merged into S2-2208262 (Ericsson) and S2-2209084 (Qualcomm). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2209151 P-CR Approval 23.700-05: TR 23.700-05: KI#7 Evaluation and conclusion. Intel Rel-18 Not Handled Contents to be merged into S2-2208262 (Ericsson) and S2-2209084 (Qualcomm). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.9 S2-2209170 P-CR Approval 23.700-05: KI #4, Update to conclusions. Samsung Rel-18 Not Handled Contents to be merged into S2-2209086 (Qualcomm). ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.10 - - - Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) - - Docs:=59 -
9.10 - - - LS In and Response - - Docs:=5 -
9.10 S2-2208140 LS In Action LS from RAN WG2: LS on LCS framework for Network verified UE location (NTN) RAN WG2 (R2-2208779) Rel-18 Responses drafted in S2-2208440, S2-2208812, S2-2208878. Final response in S2-2209589 Replied to
9.10 S2-2208440 LS OUT Approval [DRAFT] Reply LS on LCS framework for Network verified UE location (NTN) Samsung Rel-18 Response to S2-2208140. Merged into S2-2209589 Leo (Deutsche Telekom) proposes to NOTE this LS, and use S2-2208812
Yunjing (CATT) proposes to merge this paper into S2-2208812.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.10 S2-2208812 LS OUT Approval [DRAFT] Response LS on LCS framework for Network verified UE location (NTN) CATT Rel-18 Response to S2-2208140. r03 agreed. Revised to S2-2209589, merging S2-2208440 David (Samsung) provides r01.
Yunjing (CATT) provides r02 and r03.
==== Revisions Deadline ====
Stephen (Qualcomm) is okay with r03, r02, r00 but not r01 - and suggests to agree r03
Yunjing (CATT) suggests to agree r03 based on progress on S2-2208437 thread
Leo (Deutsche Telekom) prefers r03
David (Samsung) supports r03.
Guanglei (Huawei) supports r03
==== Final Deadline ====
Revised
9.10 S2-2209589 LS OUT Approval Response LS on LCS framework for Network verified UE location (NTN) SA WG2 Rel-18 Revision of S2-2208812r03, merging S2-2208440. Approved Approved
9.10 S2-2208878 LS OUT Approval [DRAFT] Reply LS on LCS framework for Network verified UE location (NTN) Xiaomi Rel-18 Response to S2-2208140. Noted Leo (Deutsche Telekom) proposes to NOTE this LS, and use S2-2208812
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.10 - - - LS out - - Docs:=5 -
9.10 S2-2208813 LS OUT Approval [DRAFT] LS on Positioning Reference Units CATT Rel-18 r01 agreed. Revised to S2-2209590. Stephen (Qualcomm) provides an r01
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 but not r00
==== Final Deadline ====
Revised
9.10 S2-2209590 LS OUT Approval LS Out on Positioning Reference Units SA WG2 Rel-18 Revision of S2-2208813r01. Approved Approved
9.10 S2-2208753 LS OUT Approval [DRAFT] LS on positioning information exchange between NG-RAN nodes Huawei, HiSilicon Rel-18 Noted Stephen (Qualcomm) provides comments
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to note the draft LS
Guanglei (Huawei) confirms this draft LS can be noted
==== Final Deadline ====
Noted
9.10 S2-2209078 LS OUT Approval [DRAFT] LS on LPHAP information delivery to RAN Huawei, HiSilicon Rel-18 r00 agreed. Revised to S2-2209591 ==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.10 S2-2209591 LS OUT Approval LS on LPHAP information delivery to RAN SA WG2 Rel-18 Revision of S2-2209078r00. Approved Approved
9.10 - - - Solution updates - - Docs:=10 -
9.10 S2-2209124 P-CR Approval 23.700-71: KI#1 Solution #2 Update. Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2208476 P-CR Approval 23.700-71: TR 23.700-71-040: Sol#3_Updates to clause 6.3.3.5 . Inspur, Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2208716 P-CR Approval 23.700-71: KI#4: Update of Solution 12 to include LOS/NLOS analytics. Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2208811 P-CR Approval 23.700-71: KI#7: update solution #25. CATT Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2208808 P-CR Approval 23.700-71: KI#7: Update Solution #28. CATT Rel-18 r01 agreed. Revised to S2-2209592. Stephen (Qualcomm) provides an r01
Cai Simon (Nokia) comments r01
Stephen (Qualcomm) replies to Cai Simon (Nokia)
Cai Simon (Nokia) clarifies to Stephen (Qualcomm)
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 but not r00
==== Final Deadline ====
Revised
9.10 S2-2209592 P-CR Approval 23.700-71: KI#7: Update Solution #28. CATT Rel-18 Revision of S2-2208808r01. Approved Approved
9.10 S2-2208748 P-CR Approval 23.700-71: KI#8, Sol#31, Update of Sol#31 . Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2209127 P-CR Approval 23.700-71: KI#8 Update to Solution #33: Support of LCS continuity when UE moves between 5GS and EPS. Nokia, Nokia Shanghai Bell Rel-18 Approved Guanglei (Huawei) has technical concerns on the principle of this solution.
Cai Simon (Nokia) clarifies Guanglei (Huawei)
Stephen (Qualcomm) provides comments
Guanglei (Huawei) further comments.
==== Revisions Deadline ====
Yunjing (CATT) can accept r0.
Guanglei (Huawei) can accept the r0
==== Final Deadline ====
Approved
9.10 S2-2208749 P-CR Approval 23.700-71: KI#9, update solution#34 to clarify impacts on service, entities and interfaces. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209593. Yunjing (CATT) provides comments.
Guanglei (Huawei) replies to Yunjing (CATT).
Leo (Deutsche Telekom) provides r01.
==== Revisions Deadline ====
Guanglei (Huawei) is fine with r01, thanks Leo (Deutsche Telekom) supporting
==== Final Deadline ====
Revised
9.10 S2-2209593 P-CR Approval 23.700-71: KI#9, update solution#34 to clarify impacts on service, entities and interfaces. Huawei, HiSilicon Rel-18 Revision of S2-2208749r01. Approved Approved
9.10 - - - Evaluation and Conclusions To - - Docs:=15 -
9.10 - - - KI#1, to support User Plane positioning - - Docs:=2 -
9.10 S2-2208533 P-CR Approval 23.700-71: KI#1: Conclusions. Qualcomm Incorporated Rel-18 CC#4: r09 agreed. Revised to S2-2209594, merging S2-2209123 Guanglei (Huawei) comments for KI#1 papers, I propose to use 8533 for conclusion discussion, 8751 for evaluation.
Cai Simon (Nokia) objects to the proposal
Stephen (Qualcomm) agrees with the proposal to use 8533 for conclusion discussion and 8751 for evaluation.
Guanglei (Huawei) replies and provides r01
Cai Simon (Nokia) provides r02 and objects to r00 and r01
Stephen (Qualcomm) provides an r03
Richard (Ericsson) supports r01 and object r02 and r03
Yunjing (CATT) provides r04.
Cai Simon (Nokia) accepts r04
Guanglei (Huawei) provides r05 for further discussion/revision
Cai Simon (Nokia) accepts r05
Guanglei (Huawei) provides r06 based on r03 to avoid overlap with KI#10
Richard (Ericsson) provides an r07
Cai Simon (Nokia) provides r08
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r00 and r03 but no other version
Guanglei (Huawei) comments on the AF/Client bullet
Yunjing (CATT) suggests to approve r08.
Guanglei (Huawei) thanks Yunjing(CATT) and can live with r08
Cai Simon (Nokia) thanks Yunjing(CATT) and supports r08 as well
Richard (Ericsson) can live with r08 and proposal from Yunjing(CATT)
==== Final Deadline ====
Cai Simon (Nokia) supports Stephen that 'take the r08 and restore the last paragraph which is shown as deleted'
Runze (Huawei) provides r09 in both revision and CC#4 folder.
Revised
9.10 S2-2209594 P-CR Approval 23.700-71: KI#1: Conclusions. Qualcomm Incorporated Rel-18 CC#4: Revision of S2-2208533r09, merging S2-2209123. Approved Approved
9.10 - - - KI#2, for NPN deployment - - Docs:=2 -
9.10 S2-2208820 P-CR Approval 23.700-71: Update of Key issue #2 conclusion. ZTE Rel-18 CC#4: Noted Yunjing (CATT) provides comments.
Runze (Huawei) comments.
Jinguo(ZTE) replies
Jinguo(ZTE) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.10 S2-2209075 P-CR Approval 23.700-71: Update of Key issue #2 conclusion. Huawei, HiSilicon Rel-18 CC#4: Approved Jinguo(ZTE) suggests to use 8820 thread for discussion
Runze (Huawei) considers a potential SoH in the next CC.
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 - - - Ki#3 , Local Area Restriction for an LMF and GMLC - - Docs:=17 -
9.10 - - - KI#4, Interaction between Location Service and NWDAF - - Docs:=3 -
9.10 S2-2208924 P-CR Approval 23.700-71: KI#4: update to evaluation and conclusion update for KI#4. Vivo Rel-18 r03 agreed. Revised to S2-2209595. Stephen (Qualcomm) comments and provides an r01
Vivian(vivo) replies to Stephen (Qualcomm) comments and provides r02
Cai Simon (Nokia) provides r03
==== Revisions Deadline ====
Stephen (Qualcomm) can accept the r03 but points out that usage of the term 'LCS System' in the Conclusions is ambiguous, and may lead to different interpretations and different solution proposals in a normative phase
Vivian(vivo) thanks for Stephen's (Qualcomm) agreement and replies to his comments
==== Final Deadline ====
Revised
9.10 S2-2209595 P-CR Approval 23.700-71: KI#4: update to evaluation and conclusion update for KI#4. Vivo Rel-18 Revision of S2-2208924r03. Approved Approved
9.10 S2-2208968 P-CR Approval 23.700-71: KI#4: Conclusions update for location accuracy analytics. Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 - - - KI#7, Positioning Reference Units and Reference UEs - - Docs:=10 -
9.10 S2-2208805 P-CR Approval 23.700-71: KI#7: Update Conclusion for PRU. CATT Rel-18 r02 agreed. Revised to S2-2209596. Stephen (Qualcomm) provides an r01
Yunjing (CATT) provides an r02.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r02
==== Final Deadline ====
Revised
9.10 S2-2209596 P-CR Approval 23.700-71: KI#7: Update Conclusion for PRU. CATT Rel-18 Revision of S2-2208805r02. Approved Approved
9.10 S2-2208806 P-CR Approval 23.700-71: KI#7: Update Solution Evaluation for PRU. CATT Rel-18 r01 agreed. Revised to S2-2209597. Stephen (Qualcomm) provides an r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.10 S2-2209597 P-CR Approval 23.700-71: KI#7: Update Solution Evaluation for PRU. CATT Rel-18 Revision of S2-2208806r01. Approved Approved
9.10 S2-2208807 P-CR Approval 23.700-71: KI#7: Add solution evaluation and conclusion for reference UE in key issue#7. CATT Rel-18 r01 agreed. Revised to S2-2209598. Stephen (Qualcomm) agrees with and supports this evaluation and conclusion
David (Samsung) provides r01
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01
Yunjing (CATT) can agree the r01
==== Final Deadline ====
Revised
9.10 S2-2209598 P-CR Approval 23.700-71: KI#7: Add solution evaluation and conclusion for reference UE in key issue#7. CATT Rel-18 Revision of S2-2208807r01. Approved Approved
9.10 S2-2209126 P-CR Approval 23.700-71: Updates to KI #7 Evaluation and conclusion. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2209599. Yunjing (CATT) provides comments and r01.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 but not the r00
==== Final Deadline ====
Revised
9.10 S2-2209599 P-CR Approval 23.700-71: Updates to KI #7 Evaluation and conclusion. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2209126r01. Approved Approved
9.10 S2-2209081 P-CR Approval 23.700-71: KI#7, conclusion update . Huawei, HiSilicon Rel-18 CC#4: r04 agreed. Revised to S2-2209970. Stephen (Qualcomm) provides an r01
Cai Simon (Nokia) comments r01
Runze (Huawei) replies to Stephen(QC) and provides r02.
Cai Simon (Nokia) provides r03
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 but not any other version
Runze (Huawei) replies to Stephen (Qualcomm) and proposes the paper for CC#3.
Runze (Huawei) only accepts r00, r02, r03, not r01.
Runze (Huawei) can live with r01 with a revision that replacing 'may include a UE subscription indication indicating whether this is a PRU' with 'may include a UE verification indication indicating whether this UE can serve as a PRU'
==== Final Deadline ====
Runze (Huawei) provides r04, both in the revision and CC#4 folder.
Revised
9.10 S2-2209970 P-CR Approval 23.700-71: KI#7, conclusion update . Huawei, HiSilicon Rel-18 Revision of S2-2209081r04. Approved Approved
9.10 - - - KI#8,location service continuity - - Docs:=3 -
9.10 S2-2208747 P-CR Approval 23.700-71: KI#8, Evaluation and conclusion of KI#8 . Huawei, HiSilicon Rel-18 Merged into S2-2209600 Guanglei (Huawei) provides r01, proposes to use 8747 for EPC/5GC handover case discussion
Stephen (Qualcomm) provides comments
Guanglei (Huawei) provides r02
==== Revisions Deadline ====
Yunjing (CATT) proposes to merge this pCR into S2-2209125
Guanglei (Huawei) confirms this pCR merged to 9125r05
==== Final Deadline ====
Merged
9.10 S2-2209125 P-CR Approval 23.700-71: Analysis and Conclusion KI #8: support of location service continuity in case of UE mobility. Nokia, Nokia Shanghai Bell Rel-18 r04 agreed. Revised to S2-2209600, merging S2-2208747 Stephen (Qualcomm) provides an r01
Guanglei (Huawei) provides r02, proposes to use 9125 as baseline for intra-5GC handover case
Cai Simon (Nokia) provides r04
Guanglei (Huawei) provides r05
Cai Simon (Nokia) accepts r05
==== Revisions Deadline ====
Stephen (Qualcomm) can agree r01, r03 or r04 only and not other versions
Guanglei (Huawei) can live with r04, prefer r05, agree that RAN requirement is needed in R18
Cai Simon (Nokia) supports r04 as well
==== Final Deadline ====
Revised
9.10 S2-2209600 P-CR Approval 23.700-71: Analysis and Conclusion KI #8: support of location service continuity in case of UE mobility. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2209125r04, merging S2-2208747. Approved Approved
9.10 - - - KI#9,Related to Satellite Access - - Docs:=7 -
9.10 S2-2208872 P-CR Approval 23.700-71: KI#9: Solution Evaluation. Xiaomi Rel-18 r05 agreed. Revised to S2-2209601. Stephen (Qualcomm) provides an r01
Yunjing (CATT) provides comments.
Yuxin (Xiaomi) provides r02.
David (Samsung) provides r03
Yuxin (Xiaomi) provides r04 merging evaluation part of 8750 following rapporteur's proposal
Stephen (Qualcomm) provides an r05
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.10 S2-2209601 P-CR Approval 23.700-71: KI#9: Solution Evaluation. Xiaomi, Huawei, HiSilicon Rel-18 Revision of S2-2208872r05. Approved Approved
9.10 S2-2208750 P-CR Approval 23.700-71: KI#9, update evaluation and conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209602 Leo (Deutsche Telekom) proposes to mark this document as MERGED with S2-2208437.
==== Revisions Deadline ====
Guanglei (Huawei) confirms this pCR merged to 8437r08
==== Final Deadline ====
Merged
9.10 S2-2208437 P-CR Approval 23.700-71: KI#9 conclusion. Samsung Rel-18 r08 agreed. Revised to S2-2209602, merging S2-2208750, S2-2208809 and S2-2208873 David (Samsung) provides r01 merging 8750, 8809 and 8873 following rapporteur's proposal
Yuxin (Xiaomi) provides r02
Yunjing(CATT) asks questions for clarification.
Stephen (Qualcomm) provides comments and an r03
Chunhui (Xiaomi) replies Stephen(QC) and provides r04.
Yunjing (CATT) provides comments.
Leo (Deutsche Telekom) provides comments.
Yuxin (Xiaomi) replies to Leo (Deutsche Telekom) and Yunjing (CATT)
Yunjing (CATT) replies to Yuxin (Xiaomi).
Yunjing (CATT) provides r05.
David (Samsung) provides r06.
Stephen (Qualcomm) provides an r07
Guanglei (Huawei) provides r08 based on r07.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r08
Jean-Yves (Thales) agrees the r08
David (Samsung) supports r08, would like to confirm if companies that merged their tdocs would like to co-sign
Yunjing (CATT) confirms to co-sign.
Guanglei (Huawei) confirms to co-sign.
==== Final Deadline ====
Revised
9.10 S2-2209602 P-CR Approval 23.700-71: KI#9 conclusion. Samsung, CATT, Huawei Rel-18 Revision of S2-2208437r08, merging S2-2208750, S2-2208809 and S2-2208873. Approved Approved
9.10 S2-2208809 P-CR Approval 23.700-71: KI#9: Add conclusion for key issue #9. CATT Rel-18 Merged into S2-2209602 Jean-Yves (Thales) comments and asks question
Yunjing (CATT) replies to Jean-Yves (Thales).
Leo (Deutsche Telekom) proposes to mark this document as MERGED with S2-2208437.
Yunjing (CATT) confirms that this document can be MERGED with S2-2208437.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.10 S2-2208873 P-CR Approval 23.700-71: KI#9: Solution Conclusion. Xiaomi Rel-18 Merged into S2-2209602 Leo (Deutsche Telekom) proposes to mark this document as MERGED with S2-2208437.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.10 - - - KI#10, Reduced Latency - - Docs:=2 -
9.10 S2-2208752 P-CR Approval 23.700-71: KI#10, evaluation and conclusion. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209603. Stephen (Qualcomm) provides an r01
Guanglei (Huawei) provides r02 based on r01.
Stephen (Qualcomm) replies to Guanglei (Huawei)
Guanglei (Huawei) replies to Stephen(Qualcomm)
==== Revisions Deadline ====
Guanglei (Huawei) still has technical concerns on r01
Stephen (Qualcomm) can agree the r01 but not other versions
Guanglei (Huawei) replies to Stephen (Qualcomm)
Yunjing (CATT) can accept r01.
Guanglei (Huawei) thanks Yunjing(CATT) and can live with r01
Richard (Ericsson) supports r01
==== Final Deadline ====
Revised
9.10 S2-2209603 P-CR Approval 23.700-71: KI#10, evaluation and conclusion. Huawei, HiSilicon Rel-18 Revision of S2-2208752r01. Approved Approved
9.10 - - - KI#11, Triggered Location for UE power saving - - Docs:=5 -
9.10 S2-2208925 P-CR Approval 23.700-71: KI#11: evaluations of KI#11. Vivo Rel-18 r01 agreed. Revised to S2-2209604. Amy (vivo) provides r01, merge the evaluation as mentioned in S2-2208810r02.
==== Revisions Deadline ====
Stephen (Qualcomm) agrees the r01 with the merger
==== Final Deadline ====
Revised
9.10 S2-2209604 P-CR Approval 23.700-71: KI#11: evaluations of KI#11. Vivo, CATT Rel-18 Revision of S2-2208925r01. Approved Approved
9.10 S2-2208926 P-CR Approval 23.700-71: KI#11: conclusions for KI#11. Vivo Rel-18 Merged into S2-2209605 Yunjing (CATT) proposes to merge this pCR into S2-2208810.
==== Revisions Deadline ====
Amy (vivo) confirms to merge this pCR into S2-2208810.
==== Final Deadline ====
Merged
9.10 S2-2208810 P-CR Approval 23.700-71: KI#11: Add evaluation and conclusion for key issue#11. CATT Rel-18 r03 agreed. Revised to S2-2209605, merging S2-2208926 Stephen (Qualcomm) provides an r01
Yunjing (CATT) provides an r02.
Amy (vivo) provides r03, keep the conclusion and merges evaluation to S2-2208925r01
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r03 - given the evaluation merger to S2-2208925r01
==== Final Deadline ====
Revised
9.10 S2-2209605 P-CR Approval 23.700-71: KI#11: Add evaluation and conclusion for key issue#11. CATT Rel-18 Revision of S2-2208810r03, merging S2-2208926. Approved Approved
9.10 - - - KI#12, low power and/or high accuracy positioning - - Docs:=4 -
9.10 S2-2209077 P-CR Approval 23.700-71: Key issue#12 conclusion. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 S2-2208751 P-CR Approval 23.700-71: KI#1, update evaluation and conclusion. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209606. Guanglei (Huawei) comments for KI#1 papers, I propose to use 8533 for conclusion discussion, 8751 for evaluation.
Cai Simon (Nokia) provides comments
Guanglei (Huawei) replies and provides r01 for evaluation
Cai Simon (Nokia) replies to Guanglei (Huawei)
Yunjing (CATT) provides r02.
Cai Simon (Nokia) accepts r02
Guanglei (Huawei) further replies
Cai Simon (Nokia) clarifies to Guanglei (Huawei)
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.10 S2-2209606 P-CR Approval 23.700-71: KI#1, update evaluation . Huawei, HiSilicon Rel-18 Revision of S2-2208751r02. Approved Approved
9.10 S2-2209123 P-CR Approval 23.700-71: KI#1 Evaluation and Conclusion Update. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209594 Guanglei (Huawei) comments for KI#1 papers, I propose to use 8533 for conclusion discussion, 8751 for evaluation.
Cai Simon (Nokia) objects to the proposal
Guanglei (Huawei) proposes to merge to 8533, as the merging discussion is happening there
==== Revisions Deadline ====
Stephen (Qualcomm) also proposed to merge this or note this if merging is not acceptable
Cai Simon (Nokia) agrees to use 2208533 r08
==== Final Deadline ====
Merged
9.10 - - - KI#2, for NPN deployment - - Docs:=5 -
9.10 - - - Ki#3 , Local Area Restriction for an LMF and GMLC - - Docs:=1 -
9.10 S2-2209076 P-CR Approval 23.700-71: Update of key issue#3 conclusion. Huawei, HiSilicon, Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.10 - - - KI#4, Interaction between Location Service and NWDAF - - Docs:=2 -
9.11 - - - Study on Edge Computing Phase 2 (FS_EDGE_Ph2) - - Docs:=50 -
9.11 - - - LS IN/OUT - - Docs:=4 -
9.11 S2-2208112 LS In Action LS from GSMA OPAG: Network federation interface for Telco edge consideration GSMA OPAG (OPAG_34_Doc_06) Revision of Postponed S2-2206963 from S2#152-e. Noted Patrice (Huawei, rapporteur) proposes to note. Noted
9.11 S2-2208113 LS In Action LS from GSMA OPAG: Network integration interface for Telco edge consideration GSMA OPAG (OPAG_34_Doc_07) Revision of Postponed S2-2206964 from S2#152-e. Noted Patrice (Huawei, rapporteur) proposes to note. Noted
9.11 S2-2209155 LS OUT Approval [DRAFT] LS on shared EHE and HR PDU session with SBO in V-PLMN Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2209884. Yuan Tao (CATT) provides comments.
Tangqing (China Mobile) provides comments.
Dario (Qualcomm) replies to Tangqing and Yun Tao.
Shubhranshu (Nokia) comments
Hyesung (Samsung) provides comments.
Tangqing (China Mobile) provides r01.
Dario (Qualcomm) replies and provides r02.
Hyesung (Samsung) provides r03.
Dario (Qualcomm) is OK w/ r03 and replies.
==== Revisions Deadline ====
Tangqing (China Mobile) provides r03_v1.
Yuan Tao (CATT) provides comments on r03_v1.
Patrice (Huawei, rapporteur) asks whether r03_v1 is acceptable to all?
Yuan Tao (CATT) can accept r03_v1.
Dario (Qualcomm) uploaded r04 = r03_v1
==== Final Deadline ====
Tangqing (China Mobile) reply to Yuan.
Revised
9.11 S2-2209884 LS OUT Approval LS on shared EHE and HR PDU session with SBO in V-PLMN SA WG2 Rel-18 Revision of S2-2209155r04. Approved Approved
9.11 - - - Rapporteur editorial pCR - - Docs:=1 -
9.11 S2-2208800 P-CR Approval 23.700-48: Editorial clean-up of TR23.700-48 . Huawei (Rapporteur) Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.11 - - - KI#1 LBO - - Docs:=4 -
9.11 S2-2208198 P-CR Approval 23.700-48: KI #1, Conclusion and Evaluation Update for LBO Scenarios. InterDigital Inc. Rel-18 r01 agreed. Revised to S2-2209885. Huazhang (vivo) comments and don't understand that if we support in HR session with ULCL, why we still need this design. And the usrp rules of EAS can be used for UE to create session without any new design. Dynamic design has already been covered by ULCL + URSP rules. And if release the HR session, the traffic in the HR session will be impact.
Laurent (Nokia): provides r01
Magnus O (Ericsson) provides r02
Laurent (Nokia): answers: I stop on this thread for a while to avoid 'Magnus adding and Laurent removing solution 27'
Huazhang (vivo) comments and doubt that whether the dynamic design is needed.
Mike (InterDigital) replies to Huazhang (vivo)
Patrice (Huawei, rapporteur) comments, trying to find an actionable question for CC.
Magnus (Ericsson) is fine to go with SoH with r00 vs r01
Huazhang (vivo) is ok for this SoH, thanks Patrice
Mike (InterDigital) is also ok with the SoH proposal
==== Revisions Deadline ====
Dario (Qualcomm) comments and he is OK with the SoH
Magnus (Ericsson) Asks if Dario comments on the right thread
Patrice (Huawei,rapporteur) confirms based on CC#2 that r01 should be approved.
==== Final Deadline ====
Revised
9.11 S2-2209885 P-CR Approval 23.700-48: KI #1, Conclusion and Evaluation Update for LBO Scenarios. InterDigital Inc. Rel-18 Revision of S2-2208198r01. Approved Approved
9.11 S2-2208363 P-CR Approval 23.700-48: Solution 27 update. Ericsson Rel-18 r01 agreed. Revised to S2-2209886. Patrice (Huawei) provides r01 with minor editorial corrections.
Magnus (Ericsson) is fine with r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.11 S2-2209886 P-CR Approval 23.700-48: Solution 27 update. Ericsson Rel-18 Revision of S2-2208363r01. Approved Approved
9.11 - - - KI#1 HR - - Docs:=7 -
9.11 S2-2208978 P-CR Approval 23.700-48: KI #1, Conclusion and Evaluation Update for HR Scenarios. Samsung Rel-18 r17 agreed. Revised to S2-2209887, merging S2-2208290 and S2-2208563 Jicheol (Samsung) provides r01.
This version collidates the conclusions update on KI#1 HR and also proposed to merge S2-2208290, S2-2208563, S2-2208630 for the same clauses.
Yuan Tao (CATT) provides r02.
Laurent (Nokia): provides r03
Dan (China Mobile) support r03
Laurent (Nokia): Comments
Hui (Huawei): comments
Magnus (Ericsson) provides comments
Yuan Tao (CATT) provides r04.
Jicheol (Samsung) ask a question for the indication from H-PCF.
Yuan Tao (CATT) replies to Jicheol (Samsung).
Dario (Qualcomm) comments and provides r05.
Hui (Huawei) provides r06.
Jicheol replies to Yuan Tao (CATT).
Tianqi (China Unicom) provides r07
Jicheol (Samsung) comments.
Tangqing (China Mobile) provides r08.
Jicheol (Samsung) provides r09 including EN for SOH question for authorization indication.
Hui (Huawei) comments on r08.
Tangqing (China Mobile) provides r10 and reply to Hui.
Magnus O (Ericsson) provides r11
Jicheol (Samsung) provides r12, r13, r14 on top of r11 to reflect SoH question on authorization indication .
r12 (Option A. UDM->AMF-VSMF), r13 (Option B. UDM->VSMF->HSMF) r14 (Option C. HPCF->HSMF->VSMF)
Jicheol (Samsung) provides r12, r13, r14 on top of r11 to reflect SoH question on authorization indication .
r12 (Option A. UDM->AMF-VSMF), r13 (Option B. UDM->VSMF->HSMF) r14 (Option C. HPCF->HSMF->VSMF)
Yuan Tao (CATT) provides r15
Dan(China Mobile) provide a compromise way, and please Jicheol can find a version to put it?
Hui(Huawei) supports Dan's proposal.
Laurent (Nokia): Comments asking for changes
Laurent (Nokia): provides r16
Magnus (Ericsson) comments
Hui (Huawei) provides r17
==== Revisions Deadline ====
Yuan Tao (CATT) requests a change on r17.
Hui (Huawei) supports Jicheol's comments.
Jicheol comments.
Patrice (Huawei, rapporteur) comments on the way forward.
Laurent (Nokia): answers
Hui (Huawei): replies
Jicheol (Samsung) is checking the final proposal from offline discussion.
Jicheol (Samsung) proposes the final resolution for this paper as follows:
Accept r17 with the following changes in the clause 8.1.2:
1. Replace the description for 'AF triggered EAS Re-discovery for an AF interaction with VPLMN' of the bullet 4 with the following NOTE:
'NOTE: The baseline procedure for AF triggered EAS Re-discovery for an AF interacting with VPLMN will be determined in normative phase.'
2. Add 'and H-SMF' after V-SMF in the bullet 5.
3. Remove the following sentense from the bullet 1.
'During PDU session establishment/modification, AMF sends the indication to V-SMF, V-SMF selects and configures V-EASDF considering this indication'
4. Add CATT as co-signer.
==== Final Deadline ====
Revised
9.11 S2-2209887 P-CR Approval 23.700-48: KI #1, Conclusion and Evaluation Update for HR Scenarios . Samsung, Huawei, HiSilicon, China Unicom, vivo, CATT Rel-18 Revision of S2-2208978r17, merging S2-2208290 and S2-2208563. Approved Approved
9.11 S2-2208290 P-CR Approval 23.700-48: KI #1: update the solution evaluation and interim conclusion of scenario 2. China Unicom Rel-18 Merged into S2-2209887 Laurent (Nokia): objects to any version of this Tdoc for the sake of having an unique thread (Rapporteur's penholder)
Tianqi (China Unicom) confirms that 8290 is merged into 8978.
Patrice (Huawei, rapporteur) proposes to merge to 8978.
Laurent (Nokia): OK to consider this as merged (and not objected by me)
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208563 P-CR Approval 23.700-48: KI#1: Update Evaluation and Conclusion for HR case. Huawei, HiSilicon Rel-18 Merged into S2-2209887 Laurent (Nokia): objects to any version of this Tdoc for the sake of having an unique thread (Rapporteur's penholder)
Laurent (Nokia): if:as the paper is merged, please consider I have not objected
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208630 P-CR Approval 23.700-48: Evaluation and conclusion update of solution 53 for KI#1. Vivo Rel-18 Merged into (Covered by) S2-2208979 Laurent (Nokia): objects to any version of this Tdoc for the sake of having an unique thread (Rapporteur's penholder)
Huazhang (vivo) confirms this paper has already been merged to S2-2208978
Laurent (Nokia): if:as the paper is merged, please consider I have not objected
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208464 P-CR Approval 23.700-48: Optimizing UPF selection to meet QoS requirements in Home Routed PDU sessions . Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2209888. Magnus O (Ericsson) provides comments
Laurent (Nokia): provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.11 S2-2209888 P-CR Approval 23.700-48: Optimizing UPF selection to meet QoS requirements in Home Routed PDU sessions . Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208464r01. Approved Approved
9.11 - - - KI#1 EACI - - Docs:=2 -
9.11 S2-2208565 P-CR Approval 23.700-48: KI#1: Update Conclusion for EACI delivery. Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2209889. Laurent (Nokia): provides r01 and R02
Hui (Huawei) provides r03
Magnus O (Ericsson) provides r04
Laurent (Nokia): provides r05
Dario (Qualcomm) provides r06
Hui (Huawei) fine with r06
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.11 S2-2209889 P-CR Approval 23.700-48: KI#1: Update Conclusion for EACI delivery. Huawei, HiSilicon Rel-18 Revision of S2-2208565r06. Approved Approved
9.11 - - - KI#2 - - Docs:=4 -
9.11 S2-2208566 P-CR Approval 23.700-48: KI#2: Conclusion for Exposure. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2209890, merging S2-2208364 and S2-2208890 Hui(Huawei) provides r01.
Changhong (Intel) replies to Hui.
Magnus (Ericsson) proposes to use 8364 as the baseline for KI#2 conclusions
Patrice (Huawei,rapporteur) comments that the study needs to have its own proper conclusion and explains why.
Changhong (Intel) comments and provides r02.
Hui (Huawei) comments to Changhong.
Magnus (Ericsson) is not ok with r00-r03
Hui (Huawei) provide r03
Hui (Huawei) responses to Magnus.
Shubhranshu (Nokia) comments
Magnus (Ericsson) Answers Hui
Dario (Qualcomm) is OK only w/ r02 or with 8364
Hyunsook (LGE) provides a comment.
Magnus O (Ericsson) provides r04, not ok with r00-r03
Hui (Huawei) can live with r04 for the sake of progress.
Shubhranshu (Nokia) OK with r04
Ouerdia (Orange) provides a comment.
Patrice (Huawei) asks for clarification.
==== Revisions Deadline ====
Hui(Huawei) replies to Ouerdia (Orange)
==== Final Deadline ====
Revised
9.11 S2-2209890 P-CR Approval 23.700-48: KI#2: Conclusion for Exposure. Huawei, HiSilicon Rel-18 Revision of S2-2208566r04, merging S2-2208364 and S2-2208890. Approved Approved
9.11 S2-2208364 P-CR Approval 23.700-48: KI#2: Conclusion. Ericsson Rel-18 Merged into S2-2209890 Patrice (Huawei, rapporteur) objects to a conclusion that does not explicitly conclude the study work, and refers blindly to another study with different objectives, therefore has to object to r00.
Patrice (Huawei, rapporteur) indicates to merge to 8566.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208890 P-CR Approval 23.700-48: KI#2: Conclusion on NG-RAN exposed QoS information. Intel Rel-18 Merged into S2-2209890 Hui(Huawei) provides r01.
Hui(Huawei) suggest to merge this paper into S2-2208566.
Changhong (Intel) replies to Hui.
Magnus (Ericsson) proposes to use 8364 as the baseline for KI#2 conclusions
Patrice (Huawei, rapporteur) requests to use 8566 as baseline for KI#2.
Shubhranshu (Nokia) ok to 8364 as baseline
Patrice (Huawei, rapporteur) indicates to merge to 8566.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 - - - KI#3 - - Docs:=3 -
9.11 S2-2208679 P-CR Approval 23.700-48: Conclusions for KI#3: Policies for finer granular sets of UEs. Nokia, Nokia Shanghai Bell Rel-18 r06 agreed. Revised to S2-2209891, merging S2-2208365 Xinpeng(Huawei) provides r01.
Magnus H (Ericsson) provides r02
Xinpeng(Huawei) provides r03.
Magnus H (Ericsson) comments.
Laurent (Nokia): provides r04
Xinpeng(Huawei) provides r05.
Xinpeng(Huawei) replies and provides r06.
Magnus H (Ericsson) please ignore r07
==== Revisions Deadline ====
Laurent (Nokia): objects to R02, R03, R07
Xinpeng(Huawei) suggest to go with r06.
==== Final Deadline ====
Revised
9.11 S2-2209891 P-CR Approval 23.700-48: Conclusions for KI#3: Policies for finer granular sets of UEs. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208679r06, merging S2-2208365. Approved Approved
9.11 S2-2208365 P-CR Approval 23.700-48: KI #3, Discussion, Evaluation and conclusion . Ericsson Rel-18 Merged into S2-2209891 Patrice (Huawei, rapporteur) proposes to merge to 8679.
Laurent (Nokia): considers that discussion takes place only in the thread of 8679
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
Patrice (Huawei,rapporteur) confirms it is merged to 8679.
==== Final Deadline ====
Merged
9.11 - - - KI#4 - - Docs:=7 -
9.11 S2-2208888 P-CR Approval 23.700-48: Update Conclusions for KI#4: Influencing UPF and EAS (re)location for collections of UEs. Lenovo, NTT DOCOMO, Huawei, CATT Rel-18 r15 agreed. Revised to S2-2209892, merging S2-2208757, S2-2208789 and S2-2209187 Xinpeng(Huawei) provides r01.
Tingfang Tang (Lenovo) starts the discussion for KI#4 conclusion update
Shubhranshu (Nokia) provides r02
Huazhang (vivo) provides r03 based on r02
Xinpeng(Huawei) comments.
Xinpeng(Huawei) replies to Huazhang (vivo).
Huazhang (vivo) reply to Xinpeng(Huawei)
Tingfang Tang (Lenovo) clarifies for r02 and Xinpeng's reply.
Tingfang Tang (Lenovo) replies to Huazhang.
Yuan Tao (CATT) merges S2-2208789 into this paper per rapporteur's suggestion and provides r04.
Tingfang Tang (Lenovo) replies to Yuan.
Yuan Tao (CATT) replies.
Yuan Tao (CATT) replies to Xinpeng(Huawei).
Xinpeng(Huawei) replies to Yuan Tao (CATT).
Tingfang Tang (Lenovo) follow-on reply to Yuan for the new timer
Tugce (NTT DOCOMO) comments
Shubhranshu (Nokia) responds
Shubhranshu (Nokia) comments
Tingfang Tang (Lenovo) asks clarification from Shubhranshu.
Tingfang Tang (Lenovo) replies.
Shubhranshu (Nokia) responds, and asks for clarification
Shubhranshu (Nokia) comments and provides r05
Yuan Tao (CATT) comments and provides r06.
Magnus H (Ericsson) ask questions
Xinpeng(Huawei) provides r07.
Shubhranshu (Nokia) asks for clarification
Tingfang Tang (Lenovo) replies and provides r07.
Tingfang Tang (Lenovo) provides r08 based covering update in r07.
Magnus H (Ericsson) comments.
Tingfang Tang (Lenovo) replies to Shubhranshu.
Magnus H (Ericsson) provides r09
Shubhranshu (Nokia) provides r10
Xinpeng(Huawei) provides r11.
Tingfang Tang (Lenovo) asks question to Magnus.H.
Huazhang (vivo) want to ask, what does this sentence mean ' For common EAS, SMF may initiate EAS re-discovery if the UE has traffic to another EAS' in r11
Tingfang Tang (Lenovo) replies and comments on r11 and provides r12.
Huazhang (vivo) thanks Tingfang, but this sentence needs polish as that, if the common EAS is changed for collection of UEs, that the EAS relocation is enforced.
Tingfang Tang (Lenovo) comments and provides r13.
Tugce (NTT DOCOMO) asks for clarification
Tingfang Tang (Lenovo) asks clarification to Magnus H.
Xinpeng(Huawei) replies.
Tugce (NTT DOCOMO) provides r14 based on r13
Xinpeng(Huawei) provides r15 based on r13.
==== Revisions Deadline ====
Tingfang Tang (Lenovo) confirms to agree with r15.
Shubhranshu (Nokia) asks for clarification to r15
Xinpeng(Huawei) replies to Shubhranshu (Nokia).
Tingfang Tang (Lenovo) proposes to go with r15 with one update, to change 'applies' to 'may apply' in the first sentence of 'UE collection definition' part, based on further discussion.
==== Final Deadline ====
Revised
9.11 S2-2209892 P-CR Approval 23.700-48: Update Conclusions for KI#4: Influencing UPF and EAS (re)location for collections of UEs. Lenovo, NTT DOCOMO, Huawei, CATT, Ericsson, Nokia Rel-18 Revision of S2-2208888r15, merging S2-2208757, S2-2208789 and S2-2209187. Approved Approved
9.11 S2-2208757 P-CR Approval 23.700-48: KI#4 Conclusion Update. Huawei, HiSilicon Rel-18 Merged into S2-2209892 Patrice (Huawei, rapporteur) proposes to merge to 8888.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208789 P-CR Approval 23.700-48: KI#4: Update conclusion for influencing UPF and EAS (re)location for collections of UEs. CATT, vivo Rel-18 Merged into S2-2209892 Patrice (Huawei, rapporteur) proposes to merge to 8888.
Yuan Tao (CATT) agrees to merge this paper into 8888 per rapporteur's suggestion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2209187 P-CR Approval 23.700-48: Updates to KI#4 Conclusions. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209892 Patrice (Huawei, rapporteur) proposes to merge to 8888.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208788 P-CR Approval 23.700-48: KI #4, Sol #18: solution update. CATT, vivo Rel-18 r01 agreed. Revised to S2-2209893. Tingfang Tang (Lenovo) clarifies
Yuan Tao (CATT) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.11 S2-2209893 P-CR Approval 23.700-48: KI #4, Sol #18: solution update. CATT, vivo Rel-18 Revision of S2-2208788r01. Approved Approved
9.11 - - - KI#5 - - Docs:=9 -
9.11 S2-2209154 P-CR Approval 23.700-48: KI#5: Conclusion update to address EAS discovery. Qualcomm Incorporated, Charter Communications, AT&T Rel-18 r13 agreed. Revised to S2-2209894, merging S2-2208758, S2-2208580 and S2-2208631 Hyesung (Samsung) asks a question.
Xinpeng(Huawei) provides r01.
Dario (Qualcomm) comments and provides r02.
Dario (Qualcomm) replies to Hyesung
Magnus (Ericsson) comments
Tangqing(China Mobile) provides r03.
Huazhang (vivo) provide comments and also, that the revision 3 I can't open
Magnus O (Ericsson) provides r04
Hiroshi (NEC) provides a comment for r04
Dario (Qualcomm) replies, provides r06 and asks to ingore r05.
Dario (Qualcomm) provides r07 based on r06.
Xinpeng(Huawei) provides r08.
Huazhang (vivo) add the evaluation of solution 55 into r08, and create r09
Magnus O (Ericsson) provides r10
Shubhranshu (Nokia) provides r11
Patrice (Huawei, rapporteur) comments that r11 removes the Edge Relocation paragraph altogether from the TR, which seems not to be the intention. It is better to keep that text unchanged, as in r10.
Dario (Qualcomm) comments and provides r12
Shubhranshu (Nokia) responds
Magnus O (Ericsson) is not ok with r12, provides r13
==== Revisions Deadline ====
Tangqing (China Mobile) is ok with r12 and r13
Dario (Qualcomm) accepts r13.
==== Final Deadline ====
Revised
9.11 S2-2209894 P-CR Approval 23.700-48: KI#5: Conclusion update to address EAS discovery. Qualcomm Incorporated, Charter Communications, AT&T Rel-18 Revision of S2-2209154r13, merging S2-2208758, S2-2208580 and S2-2208631. Approved Approved
9.11 S2-2208579 P-CR Approval 23.700-48: KI#5: conclusion for support of edge relocation based on GSMA OPG impacts and improvements. China Mobile Rel-18 r05 agreed. Revised to S2-2209895, merging S2-2208790 Patrice (Huawei), rapporteur) proposes to merge to 9154.
Shubhranshu (Nokia) provides r01
Tangqing (China Mobile) is ok with that take 8579 as baseline.
Tangqing (China Mobile) provide r02.
Shubhranshu (Nokia) provides r03
Yuan Tao (CATT) can only accept r01, object r00, r02 and r03.
Patrice (Huawei, rapporteur) is forced to object to r01-r03 as they are badly formatted and would remove text that should be left untouched by this contribution. Proper updates are required instead.
Xinpeng(Huawei) provides r04 based on r02.
Yuan Tao (CATT) provides r05 based on r04
Patrice (Huawei, rapporteur) clarifies that contrary to my original statement, 8579 is not to be merged to another document, but treated separately.
Shubhranshu (Nokia) provides r06
==== Revisions Deadline ====
Yuan Tao (CATT) only accepts r05, objects other revisions.
Shubhranshu (Nokia) is OK to r05
==== Final Deadline ====
Revised
9.11 S2-2209895 P-CR Approval 23.700-48: KI#5: conclusion for support of edge relocation based on GSMA OPG impacts and improvements. China Mobile Rel-18 Revision of S2-2208579r05, merging S2-2208790. Approved Approved
9.11 S2-2208580 P-CR Approval 23.700-48: Conclusion update for KI#5 of EAS discovery. China Mobile Rel-18 Merged into S2-2209894 Patrice (Huawei, rapporteur) proposes to merge to 9154.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208631 P-CR Approval 23.700-48: Evaluation and conclusion update for KI#5. Vivo Rel-18 Merged into S2-2209894 Patrice (Huawei, rapporteur) proposes to merge to 9154.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208758 P-CR Approval 23.700-48: KI#5 update evaluation and conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209894 Patrice (Huawei, rapporteur) proposes to merge to 9154.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208790 P-CR Approval 23.700-48: KI#5: conclusion for edge relocation based on GSMA OPG impacts and improvements. CATT, Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209895 Patrice (Huawei, rapporteur) proposes to merge to 9154.
Yuan Tao (CATT) asks Patrice (Huawei, rapporteur)if keep the conclusions for EAS discovery and EAS relocation separately as we agreed in offline discussion.
Shubhranshu (Nokia) asks for clarification
Patrice (Huawei, rapporteur) confirms Yuan (CATT) and Shubhranshu (Nokia) statements, and propose to indeed use a separate paper. Proposes 8579, but open for suggestion, as long as it properly integrates with the current section 8.5.
Shubhranshu (Nokia) is OK to take 8579 as baseline and merge this tdoc into 8579
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2209153 P-CR Approval 23.700-48: KI#5: Update of Sol. 22 to address pre-configured use case. Qualcomm Incorporated, Charter Communications, AT&T Rel-18 Approved Xinpeng(Huawei) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.11 - - - KI#6 - - Docs:=6 -
9.11 S2-2208366 P-CR Approval 23.700-48: KI #6, Conclusions. Ericsson Rel-18 CC#3: Postponed Sudeep (Apple) provides r01.
Hyesung (Samsung) provides r02.
Huazhang (vivo) comments that how to move forward that for KI6, we have a totally different view compared with 8632.
Shubhranshu (Nokia) comments
Huazhang (vivo) reply to Shubhranshu (Nokia), and no ok to directly go with current way forward and object r00 - r02
Shubhranshu (Nokia) provides r03
Svante (Sony) replies to comments on the edge indication
Patrice (Huawei) proposes r04.
Mehrdad (Mediatek Inc.) comments
Shubhranshu (Nokia) provides r05, objects to r04
Dario (Qualcomm) comments and provides r06
Mike (InterDigital) is ok with r05 and objects to r06
Huazhang (vivo) only accept r06, object any other version
Sudeep (Apple) agrees with Patrice's comments.
Mehrdad (Mediatek Inc.) is OK with r06. We object to the rest of revisions as we see very little value in it.
Magnus (Ericsson) is ok with r05 or r04 not ok with r06
Svante (Sony) ask question for clarification of r04 & r05
Dario (Qualcomm) replies.
Mike (InterDigital) replies
Svante (Sony) provide r07 based on r06 with Sony as supporting company
Mike (InterDigital) objects to r07 and replies to Svante (Sony)
==== Revisions Deadline ====
Hyesung (Samsung) is fine with r05, but not ok with r06 and r07
Huazhang (vivo) only agree with r06 and r07, object any other version.
And the design of indication doesn't bring any benefit to UE, and no normative work should do.
Shubhranshu (Nokia) prefers r05
Magnus (Ericsson) ok with SoH
Patrice (Huawei, rapporteur) comments on the SoH for KI#6.
Patrice (Huawei, rapporteur) tries to see how we can work further to address the concerns based on r04.
Svante (Sony) prefers r07 but will not object to r04/r05
==== Final Deadline ====
Mehrdad (Mediatek Inc.) replies to Huawei, rapporteur.
Sudeep (Apple) adds comments.
Postponed
9.11 S2-2208632 P-CR Approval 23.700-48: KI#6 Evaluation and Conclusion for keeping EC traffic on 5GS. Vivo, OPPO, Xiaomi Rel-18 Merged into (Covered by) S2-2208366 Patrice (Huawei, rapporteur) proposes to merge to 8366.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.11 S2-2208799 P-CR Approval 23.700-48: KI#6: Evaluation and Conclusion . Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209896. Patrice (Huawei, rapporteur) proposes to merge to 8366.
Magnus O (Ericsson) provides r01
Shubhranshu (Nokia) responds
Huazhang (vivo) provides r02
Magnus O (Ericsson) provides r03
Patrice (Huawei, rapporteur) clarifies that contrary to my original statement, 8799 is not to be merged to another document, but treated separately.
==== Revisions Deadline ====
Huazhang (vivo) ok to move forward r03
==== Final Deadline ====
Revised
9.11 S2-2209896 P-CR Approval 23.700-48: KI#6: Evaluation and Conclusion . Huawei, HiSilicon Rel-18 Revision of S2-2208799r03. Approved Approved
9.11 S2-2208979 P-CR Approval 23.700-48: KI#6, Sol#47: Update for AF influenced traffic switching guidance . Apple, Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.11 S2-2209182 P-CR Approval 23.700-48: Updates to Sol#49. Nokia, Nokia Shanghai bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.11 - - - Documents exceeding TU Budget - - Docs:=3 -
9.11 S2-2208564 P-CR Approval 23.700-48: KI#1: Update on Conclusion for LBO case. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.11 S2-2208984 P-CR Approval 23.700-48: KI #1, solution #2 update for clarification. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.11 S2-2208367 P-CR Approval 23.700-48: KI #6, Solution evaluation . Ericsson, InterDigital Inc., Nokia, Nokia Shanghai Bell, Apple Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.12 - - - Study on 5G System with Satellite Backhaul (FS_5GSATB) - - Docs:=13 -
9.12 S2-2208374 LS OUT Approval [DRAFT] LS on reporting dynamic satellite backhaul parameters to CHF Nokia, Nokia Shanghai Bell Rel-18 r02 agreed. Revised to S2-2209607. Hucheng(CATT) provides r01.
DongYeon (Samsung) comments.
Stefan (Ericsson) comments
Gerald (MATRIXX Software) supports the involvement of SA5 CH group in sending this LS.
Hucheng (CATT) shares same understanding as Gerald (MATRIXX Software) .
Stefan (Ericsson) replies to Hucheng and Gerald and provides r02
Chunhui(Xiaomi) shares the concern from Stefan(Ericsson) that the LS is not needed.
Hannu (Nokia) comments that the LS is needed for the sake of conditional conclusion in clause 8.1 but agrees to take out the bulleted list of questions in r03
Gerald (MATRIXX Software) with comments and the support of r02.
Hucheng (CATT) replies to Stefan (Ericsson).
Gerald (MATRIXX Software) with comment to Hucheng/Stefan and suggest to move on with r03.
Hannu (Nokia) prefers r03 but can also live with r02.
==== Revisions Deadline ====
Hucheng (CATT) prefers r04, can live with r02 and r03, objects r00, and points out that there is another thread for this LS and some comments in that thread are not captured in the chair's notes.
Guanglei (Huawei) can support r04
Stefan (Ericsson) can only accept r02. Object to other revisions.
Hannu (Nokia) supports r04. Can also live with r02 or r03.
==== Final Deadline ====
Revised
9.12 S2-2209607 LS OUT Approval LS on reporting dynamic satellite backhaul parameters to CHF SA WG2 Rel-18 Revision of S2-2208374r02. Approved Approved
9.12 S2-2208380 P-CR Approval 23.700-27: Update of KI#3 conclusions. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209610 Hucheng(CATT) comments.
Guanglei (Huawei) comments and proposes to merge to 8746.
Stefan (Ericsson) provides comments
Guanglei (Huawei) further comments
Hannu (Nokia) agrees to merge this paper to S2-2208746 and believes that both main proposals in this paper are applicable on the merged document.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.12 S2-2208745 P-CR Approval 23.700-27: KI#1, update evaluation and conclusion of KI#1 to cover in sequence delivery. Huawei, HiSilicon, China Telecom, CATT Rel-18 CC#4: Noted Stefan (Ericsson) provides comments
Haris(Qualcomm) provides r01
Hucheng (CATT) proposes to capture satellite backhaul case as an example.
Hannu (Nokia) shares the concern of Stefan on N3 sequence numbering.
DongYeon (Samsung) cannot agree on expanding to all kind of backhaul network, and provides r02.
Guanglei (Huawei) prefers r02
Antoine (Orange) supports and provides r03.
Guanglei (Huawei) thanks Antoine (Orange) supporting and is fine with r03
Heng (China Telecom) provide r04
Haris(Qualcomm) comments on r03
Hucheng (CATT) replies to Haris(Qualcomm).
Haris(Qualcomm) responds
Stefan (Ericsson) maintains concerns
==== Revisions Deadline ====
Hucheng (CATT) proposes to focus on dynamical satellite backhaul case now and see whether this solution can be applied to wider scope later if necessary.
Haris(Qualcomm) is ok with r01 since he sees no reason to restrict the already existing configuration for GTP-U SN to dynamic backhaul
Stefan (Ericsson) comments that this use of SN is not existing functionality
Stefan (Ericsson) objects to all revisions r00-r04
Guanglei (Huawei) asks for CC#3 or CC#4
==== Final Deadline ====
Hucheng (CATT) supports Guanglei (Huawei) to wait for SoH in CC#3 or CC#4
Heng(China Telecom) propose go with case B for SOH
Noted
9.12 S2-2208746 P-CR Approval 23.700-27: KI#3 Conclusion update. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2209610, merging S2-2208380 and S2-2208846 Stefan (Ericsson) provides questions for clarification
Guanglei (Huawei) replies to Stefan (Ericsson) and provides r01
Stefan (Ericsson) replies to Guanglei
Guanglei (Huawei) thanks Stefan (Ericsson) comments and provides r02
Hannu (Nokia) provides r03 to merge S2-2208380 to this document.
Hucheng (CATT) provides r04 for enhancement and merging S2-2208846 into it.
Stefan (Ericsson) provides r05
Hucheng (CAT) provides response to Stefan (Ericsson).
==== Revisions Deadline ====
Hucheng (CAT) prefers r04, can live with r05, and can not accept other versions.
Stefan (Ericsson) can accept r03 and r05. Objects to other versions.
Hucheng (CATT) asks clarifications from Stefan (Ericsson).
Stefan (Ericsson) replies to Hucheng
Hannu (Nokia) supports r05.
Relja (TNO) supports r05.
==== Final Deadline ====
Revised
9.12 S2-2209610 P-CR Approval 23.700-27: KI#3 Conclusion update. Huawei, HiSilicon, CATT Rel-18 Revision of S2-2208746r05, merging S2-2208380 and S2-2208846. Approved Approved
9.12 S2-2208755 P-CR Approval 23.700-27: KI#1: Evaluation and conclusion updates . Ericsson Rel-18 CC#4: Noted Depends on 8745 outcome Hucheng(CATT) comments.
Guanglei (Huawei) provides comments.
Heng(China Telecom) comments.
Stefan (Ericsson) replies
DongYeon (Samsung) comments.
Hannu (Nokia) shares Stefan's concerns and is not convinced of the merits of the sequence numbering at N3.
==== Revisions Deadline ====
Guanglei (Huawei) not agree the pCR, the result depends on the 8745 outcome
==== Final Deadline ====
Noted
9.12 S2-2208845 P-CR Approval 23.700-27: KI#1: Update evaluation and conclusion. CATT Rel-18 r02 agreed. Revised to S2-2209608. Haris(Qualcomm) comments
Hucheng (CATT) responds to Haris(Qualcomm)'s comments.
Stefan (Ericsson) provides r01
Hannu (Nokia) supports Stefan and provides r02
DongYeon (Samsung) comments.
Hucheng (CATT) relies to commnets.
==== Revisions Deadline ====
Hucheng (CATT) is OK with r02
Haris(Qualcomm) is ok with r02
==== Final Deadline ====
Revised
9.12 S2-2209608 P-CR Approval 23.700-27: KI#1: Update evaluation and conclusion. CATT Rel-18 Revision of S2-2208845r02. Approved Approved
9.12 S2-2208846 P-CR Approval 23.700-27: KI#3: Update evaluation and conclusion. CATT Rel-18 Merged into S2-2209610 Stefan (Ericsson) provides comments
Hucheng (CATT) replies to Stefan (Ericsson)
==== Revisions Deadline ====
Hucheng (CATT) thinks this paper can be marked as merged into S2-2208746.
Stefan (Ericsson) supports to mark this as merged into S2-2208746
==== Final Deadline ====
Merged
9.12 S2-2209193 P-CR Approval 23.700-27: KI#2: Update to Solution#10: Enable Satellite EAS re-discovery and re-allocation by means of local DNS. TNO Rel-18 Approved Hucheng(CATT) points out that no new or updated solution is allowed in this meeting according to the work plan.
Relja (TNO) responds to Hucheng.
==== Revisions Deadline ====
Hucheng (CATT) is OK to include this paper into the TR if no other objection.
==== Final Deadline ====
Approved
9.12 S2-2209194 P-CR Approval 23.700-27: Evaluation update of Solution#10 and addition of conclusions for Solution#10. TNO Rel-18 r01 agreed. Revised to S2-2209609. Stefan (Ericsson) comments and provides r01
==== Revisions Deadline ====
Hucheng (CATT) is OK with r01
Relja (TNO) is OK with r01 and thanks Stefan for providing it.
==== Final Deadline ====
Revised
9.12 S2-2209609 P-CR Approval 23.700-27: Evaluation update of Solution#10 and addition of conclusions for Solution#10. TNO Rel-18 Revision of S2-2209194r01. Approved. Not provided. WITHDRAWN Withdrawn
9.13.1 - - - Study on the support for 5WWC Phase 2 (FS_5WWC_Ph2) - - Docs:=15 -
9.13.1 - - - KI#2 conclusions - - Docs:=3 -
9.13.1 S2-2208226 P-CR Approval 23.700-17: Update to conclusions for KI2. Nokia, Nokia Shanghai Bell Rel-18 r07 agreed. Revised to S2-2209897. Laurent (Nokia): (rapporteur) It is proposed to discuss only one Update to conclusions for KI2 within the thread of S2-2208226, merging 8325 into 8226
Sebastian (Qualcomm) provides r01
Laurent (Nokia): reasking my question
Marco (Huawei) provides r02 removing the new solution and related conclusion since per plan agreed in SA2 the last opportunity was in Aug meeting for KI#2
Marco (Huawei) provide r02 since I forgot to merge text from 8325
Marco (Huawei) Errata corrige - provide r03 since I forgot to merge text from 8325
Heng (China Telecom) comment on r03
Yishan (Huawei) provides r04 to capture the comments from Heng (China Telecom)
Laurent (Nokia): provides r05
Laurent (Nokia): provides r07, R06 skipped
==== Revisions Deadline ====
Laurent (Nokia): objects to R02, R03, R04
Yishan (Huawei) answers to Laurent (Nokia)
Marco (Huawei) object to r05, and r07 since include the bullet 3 where TNGF send slice supported per SSID.
Sebastian (Qualcomm) objects to r00
Marco (Huawei) object to r05, and r07: I can accept r07 without bullet 3.
==== Final Deadline ====
Revised
9.13.1 S2-2209897 P-CR Approval 23.700-17: Update to conclusions for KI2. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208226r07. Approved Approved
9.13.1 S2-2208463 P-CR Approval 23.700-17: KI#2: Updating solution 15 . Nokia, Nokia Shanghai Bell Rel-18 Approved Heng(China Telecom) comments.
Laurent (Nokia): answers
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.13.1 - - - KI#1 solution updates - - Docs:=10 -
9.13.1 S2-2208274 P-CR Approval 23.700-17: KI#1, Sol#1: Update to address RG configuration and differentiated charging. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.13.1 S2-2208275 P-CR Approval 23.700-17: KI#1, Sol#2: Update to resolve ENs and address per RG differentiation . Ericsson Rel-18 r03 agreed. Revised to S2-2209898, merging S2-2208322 Marco (Huawei) provides r02
Huan(vivo) comments
Huan(vivo) provides additional comments
Stefan (Ericsson) replies and provides r03
==== Revisions Deadline ====
Huan(vivo) comments that an existing paragraph in the TR is not included in the contribution and hope the rapporteur can fix it :)
Yishan (Huawei) answers the questions from Huan (vivo)
==== Final Deadline ====
Revised
9.13.1 S2-2209898 P-CR Approval 23.700-17: KI#1, Sol#2: Update to resolve ENs and address per RG differentiation . Ericsson, Intel Rel-18 Revision of S2-2208275r03, merging S2-2208322. Approved Approved
9.13.1 S2-2208322 P-CR Approval 23.700-17: KI#1, update Sol#2. Huawei, HiSilicon Rel-18 Merged into S2-2209898 Stefan (Ericsson) provides comments and asks about merging into 8275
Yishan (Huawei) answers to Stefan (Ericsson)
==== Revisions Deadline ====
Stefan (Ericsson) proposes to consider it merged into S2-2208275
==== Final Deadline ====
Merged
9.13.1 S2-2208781 P-CR Approval 23.700-17: KI #1, Sol #20: update to enhance the primary mechanism . China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.13.1 S2-2209024 P-CR Approval 23.700-17: KI#1: Update to Solution#6 on FS_5WWC_Ph2. China Telecom Rel-18 r01 agreed. Revised to S2-2209899. Stefan (Ericsson) provides questions for clarification
Yubing (China Telecom) replies to Stefan (Ericsson) and provides clarification
Stefan (Ericsson) replies to Yubing
Laurent (Nokia): Comments
Yubing (China Telecom) replies to Stefan(Ericsson) and Laurent (Nokia), and provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.13.1 S2-2209899 P-CR Approval 23.700-17: KI#1: Update to Solution#6 on FS_5WWC_Ph2. China Telecom Rel-18 Revision of S2-2209024r01. Approved Approved
9.13.1 S2-2209143 P-CR Approval 23.700-17: KI#1: 802.11e s user priority mapping with 5G QoS. Meta USA, CableLabs, Charter Communications, Broadcom Rel-18 Postponed Stefan (Ericsson) comments
Sebastian (Qualcomm) proposes to postpone
Marco (Huawei) comments
Curt (Meta) replies to Marco/Sebatian/Stefan...and provides r01.
Sebastian (Qualcomm) still prefers to postpone
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.13.1 S2-2209144 P-CR Approval 23.700-17: KI#1: Update to solution 3 Resolving EN(s). Intel Rel-18 r01 agreed. Revised to S2-2209900. Laurent (Nokia): Comments
Suresh Srinivasan (Intel) replies to Laurent's (Nokia) comments and propose S2-2209144r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.13.1 S2-2209900 P-CR Approval 23.700-17: KI#1: Update to solution 3 Resolving EN(s). Intel Rel-18 Revision of S2-2209144r01. Approved Approved
9.13.1 - - - Documents exceeding TU Budget - - Docs:=2 -
9.13.1 S2-2209141 P-CR Approval 23.700-17: KI#1: Update to solution 2 Resolving EN(s). Intel Rel-18 Not Handled Stefan (Ericsson) provides comments and asks about merging into 8275
Suresh Srinivasan (Intel) relies to Stefan's(Ericsson) queries
Suresh Srinivasan (Intel) propose S2-2208275r01
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Not Handled
9.13.1 S2-2208325 P-CR Approval 23.700-17: KI#2, Update conclusion on KI#2 Huawei, HiSilicon Rel-18 Not Handled Merge into S2-2208226 Laurent (Nokia): (rapporteur) It is proposed to discuss only one Update to conclusions for KI2 within the thread of S2-2208226, merging 8325 into 8226
Heng(China Telecom) comments.
Heng(China Telecom) please ignor my previous email which is in a wrong thread.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Not Handled
9.13.2 - - - Support for WWC Phase 2 (5WWC_Ph2) - - Docs:=7 -
9.13.2 S2-2208319 CR Approval 23.501 CR3707 (Rel-18, 'B'): N3IWF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Qualcomm, China Telecom Rel-18 r07 agreed. Revised to S2-2209901, merging S2-2208227 Laurent (Nokia): (rapporteur) It is proposed to discuss only one 23.501 CR within the thread of 8319, merging 8227 into 8319
Laurent (Nokia): provides r01
Myungjune (LGE) provides r02.
Yishan (Huawei) provides r03.
Myungjune (LGE) comments on r03.
Yishan (Huawei) answers to Myungjune (LGE)
Sebastian (Qualcomm) provides r04
Laurent (Nokia): provides r05
Marco (Huawei) provide r06 with editorial revisions
Sebastian (Qualcomm) provides r07 with minor editorial fixes
==== Revisions Deadline ====
Laurent (Nokia): objects to R00, R03, R04
Marco (Huawei) support r07
==== Final Deadline ====
Revised
9.13.2 S2-2209901 CR Approval 23.501 CR3707R1 (Rel-18, 'B'): N3IWF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Qualcomm, China Telecom, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208319r07, merging S2-2208227. Approved Agreed
9.13.2 S2-2208684 CR Approval 23.502 CR3578 (Rel-18, 'B'): Introduction to N3IWF selection to support the slices needed by the UE Nokia, Nokia Shanghai Bell Rel-18 r11 agreed. Revised to S2-2209902, merging S2-2208320 Laurent (Nokia): provides r01
Laurent (Nokia): (rapporteur) It is proposed to discuss only one 23.502 CR within the thread of 8684, merging 8320 into 8684
Laurent (Nokia): provides r01
Myungjune (LGE) provides comments.
Stefan (Ericsson) provides comments
Yishan (Huawei) asks for clarification
Heng (China Telecom) share the same concern with Yishan
Sebastian (Qualcomm) replies and provides r02
Laurent (Nokia): answers and provides r03
Myungjune (LGE) provides r04.
Yishan (Huawei) provides r05.
Sebastian (Qualcomm) provides r06
Laurent (Nokia): provides r07
Ashok (Samsung) need clarifications
Marco (Huawei) replies to Laurent (Nokia)
Sebastian (Qualcomm) provides r08
Ashok (Samsung) agrees with Sebastian
Heng (China Telecom) agrees with Ashok
Sebastian (Qualcomm) replies to Ashok
Heng (China Telecom) provides r09 on top of r08
Ashok (Samsung) thanks Sebastian
Sebastian (Qualcomm) comments; has concerns with r09
Heng (China Telecom) comments and think the issue may need FFS
Marco (Huawei) provides r10
Ashok (Samsung) provides r11
==== Revisions Deadline ====
Laurent (Nokia): objects to R09
Sebastian (Qualcomm) prefers r11; also ok with r02, r06, r08, r10; objects to other versions
Marco (Huawei) ok with r11 & r10, objects any other versions
Ashok (Samsung) OK with r11
==== Final Deadline ====
Revised
9.13.2 S2-2209902 CR Approval 23.502 CR3578R1 (Rel-18, 'B'): Introduction to N3IWF selection to support the slices needed by the UE Nokia, Nokia Shanghai Bell, Qualcomm Huawei, HiSilicon, China Telecom Rel-18 Revision of S2-2208684r11, merging S2-2208320. Approved Agreed
9.13.2 S2-2208320 CR Approval 23.502 CR3556 (Rel-18, 'B'): N3IWF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Qualcomm, China Telecom Rel-18 Merged into S2-2209902 Merge into S2-2208684 Laurent (Nokia): (rapporteur) It is proposed to discuss only one 23.502 CR within the thread of 8684, merging 8320 into 8684
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Merged
9.13.2 S2-2208321 CR Approval 23.503 CR0741 (Rel-18, 'B'): N3IWF selection enhancement for support of S-NSSAI needed by UE Huawei, HiSilicon, Qualcomm, China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Agreed
9.13.2 S2-2208227 CR Approval 23.501 CR3702 (Rel-18, 'B'): Introduction to N3IWF selection to support the slices needed by the UE Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209901 Marco (Huawei) this is merged into 8319
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 - - - Study on Network Slicing Phase 3 (FS_eNS_Ph3) - - Docs:=43 -
9.14 - - - Evaluation + Conclusion for all KIs - - Docs:=1 -
9.14 S2-2208946 DISCUSSION Discussion Nokia comments on proposals for Conclusions . Nokia, Nokia Shanghai Bell Rel-18 Noted Jinguo(ZTE) suggests to note this paper. The content is for discussion and will be considered during the discussion of each key issue
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.14 - - - Evaluation + Conclusion for KI#1 - - Docs:=7 -
9.14 S2-2208944 P-CR Approval 23.700-41: KI#1 Evaluation and Conclusions. Lenovo, ZTE, NEC, Apple, Ericsson Rel-18 CC#4: r17 agreed. Revised to S2-2209298, merging S2-2208409, S2-2208980 and S2-2209028 Myungjune (LGE) provides comments.
Dongeun(Samsung) provides r01
Haiyang (Huawei) provides r02
Peter Hedman (Ericsson) provides comments
Jinguo(ZTE) provides r03
Dongeun (Samsung) replies to Peter (Ericsson)
Genadi (Lenovo) replies to some comments by Myungjune (LGE).
Genadi (Lenovo) provides r04 and further comments to Dongeun (Samsung) and Haiyang (Huawei).
Myungjune (LGE) replies to Genadi (Lenovo) and cannot accept r03/r04.
Xiaowen (vivo) provides comments.
Haiyang (Huawei) replies to Genadi (Lenovo).
Jinguo(ZTE) replies to Myungjune (LGE).
Ulises (InterDigital) agrees with Myungjune (LGE) regarding (1) re-evaluation of the URSP rule and (2) reverting changes to EN underneath bullet (3), and provides r05 to reflect this
Stefano (Qualcomm) provides R06 to address concerns due to unnecessary updates to URSP rules.
Krisztian (Apple) supports r06 and shares the concerns on unnecessarily updating URSP rules based on temporary network conditions.
Xiaowen (vivo) provides comments which has been ignored in the email thread.
Dongeun (Samsung) comments
Genadi (Lenovo) replies to Dongeun (Samsung) on updating the URSP rules.
Yi (China Mobile) comments.
Haiyang (Huawei) provides r07 based on r06
Genadi (Lenovo) replies to Xiaowen (Vivo) and Yi (China Mobile). Further, r08 is provided.
Dongeun (Samsung) cannot accept r02 r03 r05 r07
alessio(Nokia) provides r09
Haiyang (Huawei) comments to Dongeun (Samsung)
Xiaowen (vivo) response to Genadi.
Peter Hedman (Ericsson) provides r10
Haiyang (Huawei) provides r11
Jinguo(ZTE) provides r12
Dongeun (Samsung) replies to Haiyang (Huawei)
Myungjune (LGE) provides r13.
Dongeun (Samsung) provides r14
Genadi (Lenovo) comments to r14.
==== Revisions Deadline ====
Genadi (Lenovo) provides further comments to Dongeun (Samsung).
Genadi (Lenovo) proposes to agree r13.
Alessio(Nokia) can live with revisions up to 11. can accept r16 only if it minuted or added as EN that' it is FFS whether we need solutions where there is no change of IP address (i.e SMF/UP do not change) and also that the NSI change option is needed only for UP overload that is unforeseen (CP load is not mitigated by this solution rather is made worse)'
Peter Hedman (Ericsson) ok with r16 + removal of 'The PCF notification can be triggered via the QoE improvement indication from AF.'
Jinguo(ZTE) suggest to go with r16 + removal of 'The PCF notification can be triggered via the QoE improvement indication from AF.' +
Dongeun (Samsung) also suggeset to go with r16 + removal of 'The PCF notification can be triggered via the QoE improvement indication from AF.'
Iskren (NEC) we also want to go with r16 with removed 'The PCF notification can be triggered via the QoE improvement indication from AF'
Haiyang (Huawei) also OK to go with r16 + removal of 'The PCF notification can be triggered via the QoE improvement indication from AF.'
Alessio replies to jinguo (ZTE) that I can also accept just reinstating in r16 in EN for bullet 3 this sentence: 'it is FFS whether the same cannot be achieved by repartitioning resources where needed hence this solution may not be needed in normative phase'
==== Final Deadline ====
Revised
9.14 S2-2209298 P-CR Approval 23.700-41: KI#1 Evaluation and Conclusions. Lenovo, ZTE, NEC, Apple, Ericsson, Huawei Rel-18 CC#4: Revision of S2-2208944r17, merging S2-2208409, S2-2208980 and S2-2209028. Approved Approved
9.14 S2-2208409 P-CR Approval 23.700-41: Evaluation and conclusion for KI#1: Support of Network Slice Service continuity. Huawei, HiSilicon Rel-18 Merged into S2-2209298 Jinguo(ZTE) suggests to merge this P-CR in 8944
Alessio(Nokia) considers this paper status noted for the rest of the discussion and will only comment on 8944 . we ask to mark this paper noted.
==== Revisions Deadline ====
Haiyang(Huawei) is ok to merge this P-CR in 8944
==== Final Deadline ====
Merged
9.14 S2-2208980 P-CR Approval 23.700-41: KI#1 Evaluation and Conclusions. Samsung Rel-18 Merged into S2-2209298 Jinguo(ZTE) suggests to merge this P-CR in 8944
Alessio(Nokia) considers this paper status noted for the rest of the discussion and will only comment on 8944 . we ask to mark this paper noted.
Dongeun(Samsung) is ok to be merged into 8944
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2209028 P-CR Approval 23.700-41: Solution Evaluation and Conclusions for KI #1. Vivo Rel-18 Merged into S2-2209298 Jinguo(ZTE) suggests to merge this P-CR in 8944
Xiaowen (vivo) agrees to merge.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2209047 P-CR Approval 23.700-41: Conclusion on KI#1. China Mobile Rel-18 Noted Jinguo(ZTE) suggests to merge this P-CR in 8944
Alessio(Nokia) considers this paper status noted for the rest of the discussion and will only comment on 8944 . we kindly ask to mark this paper noted.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.14 S2-2209108 P-CR Approval 23.700-41: KI#1 Discussion and proposals on open issues. Lenovo Rel-18 Noted Jinguo(ZTE) suggests to note this paper. The content is for discussion and will be considered during the discussion of 8944
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.14 - - - Evaluation + Conclusion for KI#2 - - Docs:=8 -
9.14 S2-2209000 P-CR Approval 23.700-41: KI#2: Conclusions. NEC, LGE, Lenovo, Nokia, Rel-18 CC#4: r18 agreed. Revised to S2-2209299, merging S2-2208412 Myungjune (LGE) provides r01.
George (Ericsson) provides r02. The inclusion if assistance information is a CT1 discussion and we should let them decide.
Genadi (Lenovo) provides r03.
George (Ericsson) provides r04. Minor editorial in cyan.
Dongeun (Samsung) provides r05.
George (Ericsson) provides comments. U delete via UDM completely, SO the statement below ius incorrect. Can U please correct this or we have use r04
Dongeun (Samsung) comments
Kundan (NEC) provides comments.
Kundan (NEC) provides r06.
George (Ericsson) provides comments. U forgot to restore via UDM in bullet 5.
Myungjune (LGE) provides comments.
Myungjune (LGE) provides r07.
George (Ericsson) asks question
Myungjune (LGE) replies to George (Ericsson)
Myungjune (LGE) replies to Dongeun (Samsung).
Haiyang (Huawei) provides r08
Myungjune (LGE) provides r09.
Dongeun (Samsung) provides r10.
Haiyang (Huawei) provides comments
George (Ericsson) provides response
George (Ericsson) provides r11. Ericsson objects any mention of legacy UEs. CT1 will discuss that
Srisakul (NTT DOCOMO) provides r12 (mainly editorial and add EN). Ask question for clarification.
Haiyang (Huawei) cannot accept to conclude explicit UE capability in SA2. Ask questions
Myungjune (LGE) replies to Srisakul (NTT DOCOMO).
Krisztian (Apple) provides r13
Haiyang (Huawei) objects r10~r13, provides r14
Dongeun (Samsung) provide comment to Haiyaing (Huawei)
Haiyang (Huawei) comments to Dongeun (Samsung)
George (Ericsson) provides r15
alessio(Nokia) provides r16 for approval and asks to note earlier revisions.
Myungjune comments on r16.
Haiyang (Huawei) agrees with Myungjune and provides r17
==== Revisions Deadline ====
George (Ericsson) can accept only r15, r16 or r17
Kundan (NEC) are fine with only r15, r16 or r17 but prefers r17.
Dongeun (Samsung) provide comments on r17
Haiyang (Huawei) can accept only r08, r09, r14 and r17
Alessio(Nokia) prefers R16 but can live with r17 with the understanding the any SA3 evaluation is not used to block any solution or progress of normative work. existing SoR info already today can take into account what slices a VPLMN supports because it is known by roaming agreements and so much so the subscribed s-NSSAIs sent to the VPLMN are per VPLMN. there is some assumption in rev17 text that this cannot be done already using rel-15 specs and it is incorrect (e.g. a HPLMN can in principle exclude or down prioritize a PLMN because it supports a reduced set of slices for the UE than other PLMNs in the visited country).
Genadi (Lenovo) can prefers r17 and can accept r16.
Alessio(Nokia) if r17 was pursue we want this to be minuted 'SA3 evaluation is not used to block any solution or progress of normative work. I.e. a WID can be agreed and SA3 work will occur normally if needed'
Dongeun(Samsung) suggest to go with r16
Haiyang (Huawei) has a question on the minutes.
Peter Hedman (Ericsson) provides comments that SA2 cannot overrule SA3
Alessio(Nokia) replies to peter that nokia did not certainly mean what peter easy. to simplify we want to ask to remove this note from relp-17 then '34NOTE x: SA3 has to investigate whether the above principles present potential security risks and if so whether SA3 can resolve them. . Any SA3 feedback will be taken into account during the normative phase'
==== Final Deadline ====
Haiyang (Huawei) provides r18 which is: 'R17+ 1. change the NOTE 1: from 'Container' to 'mechanism' +2. delete the last NOTE.
Peter Hedman (Ericsson) provides question whether removing the note means that SA3 are assumed to not perform a security evaluation of the whole solution/principles?
Haiyang (Huawei) clarify that R17 is still preferred by us
Jinguo(ZTE) replies
Revised
9.14 S2-2209299 P-CR Approval 23.700-41: KI#2: Conclusions. NEC, LGE, Lenovo, Nokia, Nokia shanghai Bell, Huawei, ZTE Rel-18 Revision of S2-2209000r18 (CC#4), merging S2-2208412. Approved. CC#3: Postponed to CC#4. CC#4: S2-2209000r18 agreed. Approved Approved
9.14 S2-2208183 P-CR Approval 23.700-41: KI 2: Proposal for Conclusion on KI #2. Ericsson, Apple Rel-18 r03 agreed. Revised to S2-2209300. Jinguo(ZTE) propose to use this paper as basis for evaluation part. The conclusion part can use 9000 as basis
Myungjune (LGE) proposes to merge this pCR into S2-2209000.
Kundan (NEC) agrees with Jinguo to use this paper as evaluation document and use 9000 as conclusion document.
alessio (nokia) agrees with Jinguo
Jinguo(ZTE) provides r01 to remove the conclusion part.
alessio(Nokia) provides r02 to correctly evaluate the KI at least for some solutions (did not spend time on some solutions George bundled together in the evaluation so the companies that care about those solutions should take care of those)
Haiyang (Huawei) provides r03.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.14 S2-2209300 P-CR Approval 23.700-41: KI 2: Proposal for Conclusion on KI #2. Ericsson, Apple Rel-18 Revision of S2-2208183r03. Approved Approved
9.14 S2-2208412 P-CR Approval 23.700-41: Evaluation and conclusion of KI#2. Huawei, HiSilicon Rel-18 Merged into S2-2209299 Myungjune (LGE) proposes to merge this pCR into S2-2209000.
Dongeun (Samsung) comments
George Foti (Ericsson) proposes to note the pCR. Please see additional comments
Kundan (NEC) proposes to merge this in 9000 and further asking quesition.
Haiyang (Huawei) provides feedback to Myungjune (LGE) and Kundan (NEC).
Kundan(NEC) responds to Haiyang.
Haiyang (Huawei) comments.
Haiyang (Huawei) comments to Kundan (NEC).
alessio(Nokia) also proposes to note this paper and use S2-2209000.
==== Revisions Deadline ====
Dongeun (Samsung) suggest to merge this into 9000 as the same topic is being discussed in 9000
Haiyang (Huawei) is OK to merge to 9000.
==== Final Deadline ====
Merged
9.14 S2-2208414 LS OUT Approval [DRAFT] LS on slice SoR security Huawei, HiSilicon Rel-18 Noted George Foti (Ericsson) provides comments
Stefano Faccin (Qualcomm) provides concerns
Haiyang (Huawei) provides r01
alessio(Nokia) cannot accept this LS unless Huawei can provide a view on the identified security risks on which there can be shared agreement these are real. this is more transferring to SA3 the evaluation of the study which to us is not right.
Haiyang (Huawei) comments to Alessio (Nokia)
alessio(Nokia) comments SA3 will open a WID on a contribution driven manner if some companies identify a security risk. we should send a LS to SA3 if a company has security risks they have identified that they want SA3 to assess... what security risk do you identify?
Haiyang (Huawei) responds to Alessio (Nokia), provides r02
==== Revisions Deadline ====
alessio(Nokia) requests to NOTE any version of this LS as CT1 will own the normative work and then interact with SA3 as needed.
Haiyang (Huawei) proposes to use the LS to trigger the discussion in SA3
==== Final Deadline ====
Noted
9.14 S2-2208782 LS OUT Approval [DRAFT] LS on Slice based Steering of Roaming NTT DOCOMO Rel-18 Postponed alessio(Nokia) proposes to note this LS.
Srisakul (NTT DOCOMO) provides r01 and comments to Alessio (NOKIA).
alessio(Nokia) thanks Srisakul for the clarification. I am ok to send a LS to cT1 to get them started but let's wait to send it till we have a conclusion to share ... so let's check whether we can send a LS already to cT1 at this meeting or postpone this to next meeting
==== Revisions Deadline ====
Alessio Nokia) asks to postpone this till we have a way forwards by a WID normative text that CT1 can consider our input.
Jinguo(ZTE) support to send this LS to CT1. The WID in SA2 will not touch too much details on SoR since most of the work will be done at CT1. This LS is good chance to trigger the CT1 discussion?
Srisakul (NTT DOCOMO) agrees with Jinguo (ZTE) that this LS can be sent from this meeting to trigger CT1 discussion considering that SA2 seems to agree on some solution principles for KI#2 in this meeting.
==== Final Deadline ====
Alessio(Nokia) thinks that it is more appropriate to have a discussion at next meeting on the work split on this KI and Send to CT1 a proposal of work split. so we thank docomo for starting this useful discussion but we believe we should send one LS where we also say we encourage CT1 to do normative work based on the outcomes... in any event they will not work on this next meeting as they need a WID discussion.
Srisakul (NTT DOCOMO) responded to Alessio (NOKIA). Please note that texts in the drafted LS OUT already stated that 'SA2 would like to request CT1 to consider the conclusion for this key issue#2 for normative work to be handled by CT1.' So it is fully aligned to what you are asking for. Could you please clarify what are your concerns and what work split do you have in mind? If no strong concern, we would appreciate to re-consider to send this LS OUT.
Postponed
9.14 S2-2209001 DISCUSSION Information KI#2: Input from companies on basic procedures of slice based SoR. NEC Rel-18 Noted Jinguo(ZTE) proposes to note this discussion paper, and thanks Kundan(NEC) for the polling work.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.14 - - - Evaluation + Conclusion for KI#3 - - Docs:=5 -
9.14 S2-2208802 P-CR Approval 23.700-41: Way forward proposal for Conclusions and Evaluations. Nokia, Nokia Shanghai Bell, Docomo Rel-18 r07 + changes agreed. Revised to S2-2209301, merging S2-2208413 and S2-2208764 Haiyang (Huawei) comments
Ashok (Samsung) comments that URSP solution does not work for termination of temporary slice
Peter Hedman (Ericsson) provides comments, and propose to move forward with 08764
Jinguo(ZTE) suggest that this paper can focus on different TAs per cell and new time information to the UE.
Srisakul (NTT DOCOMO) provides comments and agrees with Ashok (Samsung). Suggest to keep slice termination aspect (graceful termination and gradual termination) and temporary slice aspect in this paper. Dividing different aspects on KI#3 in different tdocs would be difficult to follow. It is better to have a single Email thread to handle KI#3 and try to reach compromise.
Jinguo(ZTE) replies to Srisakul (NTT DOCOMO)
Srisakul (NTT DOCOMO) responds to Jinguo (ZTE).
Jinguo(ZTE) suggest to use 8802 as basis for evaluation discussion
Alessio(Nokia) will object to any URSP based solutions as they solve none of the issues at hand (e.g. time based slice is still allowed even after it dies but if you say that the AMF can remove it with UCU then why to use your URSP rules at all?) while still requiring update of UE behaviour. the idea was to improve the system not to show the inefficient or non-suitable solutions one can use today. requests one signle document is updated per KI to avoid too many threads.
alessio(Nokia) cannot agree to any of 8764 and we should proceed with this apper as baseline and people can comment on they as they see fit.
alessio(nokia) proposes that we use this as baseline then if some other company has an alternative to baseline they cannot convince others to accept we can go to a resolution but please let us stick to one document per KI as we discussed ...
Peter Hedman (Ericsson) same as Alessio cannot agree anything of 8764 I cannot see what is worth to progress in this paper that is not also in 8764 i.e. baseline would then be minimal common denominator?
Stefano (Qualcomm) indicates that 8802 is surely not optimal, but it is a preferrable way forward than 8802.
Kundan (NEC) suggests to use one document for all conclusions.
Jinguo(ZTE) provides r01
Kundan (NEC) asks question, can we document something in conclusion which is pending to another group response.
Alessio(Nokia) provides r02
Peter Hedman (Ericsson) provides r03
alessio(Nokia) objects to r03 because it redefines the concept of time availability of a slice (it says slice is still there but not for the UE - this was not what the KI was about, it was about temporary slices) also it introduces a strange reconfiguration of TA concept that was never discussed (new TAs configured but other TAs still support the slices?). we did not remove options in r02 we just removed those that are not technically agreeable like use of existing URSP.
Haiyang (Huawei) objects r02
alessio(nokia) clarifies that we kept (despite not agreeing with it) in r02 the description of the option to use 'updated URSPs ' but removed the option to use EXISTING URSPS unchanged. so asks Huawei to clarify whether they still keep the objection.
Stefano (Qualcomm) expresses concerns and will object to solutions that mandate constant re-evaluation of URSP rules at every cell change.
Haiyang (Huawei) provides r04
Jinguo(ZTE) provides r05
Haiyang (Huawei) provides r06
Srisakul (NTT DOCOMO) provides r07
Peter Hedman (Ericsson) provides r07
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides question
Haiyang (Huawei) can only accept r04 r06, and r07
Srisakul (NTT DOCOMO) ask question to Peter (Ericsson).
alessio(Nokia) can only accept r02 or r04.r05 and beyond modify the evaluation in unacceptable ways.
Peter Hedman (Ericsson) provides reply to Srisakul
Peter Hedman (Ericsson) provides questin to Alessio on what are the unacceptable changes in r05 (and beyond)
Peter Hedman (Ericsson) Prefer r06 over r07, but both 'ok' with the understanding that we will not have any final conclusions at this meeting
Iskren (NEC) objects to r00 to r04. We can only accept r05 or r06 or r07
Jinguo(ZTE) suggests to go with r07. This the baseline for further discussion. There is no final conclusion on each bullet.
Srisakul (NTT DOCOMO) provides comment to Peter's clarification.
Alessio(Nokia) can ONLY accept r02, r04 and can live with r07 ONLY and ONLY if the evaluations are removed.
Peter Hedman (Ericsson) objects also r02 and r04, as stated before 'ok' with r07 (with or without evaluation)
Srisakul (NTT DOCOMO) OK with r01, r02, r04 and r07. Object to r03, r05, r06.
Alessio(Nokia) can then live with r07 WITHOUT evaluation text.
Kundan(NEC) is fine with r07.
Haiyang (Huawei) can also live with r07 with or without evaluation text.
Jinguo(ZTE) suggests to go with r07+ remove evaluation text
==== Final Deadline ====
Revised
9.14 S2-2209301 P-CR Approval 23.700-41: Way forward proposal for Conclusions and Evaluations. Nokia, Nokia Shanghai Bell, Docomo, NEC Rel-18 Revision of S2-2208802r07 + changes, merging S2-2208413 and S2-2208764. Approved Approved
9.14 S2-2208413 P-CR Approval 23.700-41: Evaluation and conclusion of KI#3. Huawei, HiSilicon Rel-18 Merged into S2-2209301 Srisakul (NTT DOCOMO) comments. Suggest to use 8802 as a basis. Perhaps, if conclusion part is controversial, we may think of dropping conclusion part in this meeting, and mainly focus on the evaluation part in 8802.
alessio(Nokia) like docomo, we Suggest to use 8802 as a basis. we kindly ask this paper to be marked as we will only comment on 8802 for this KI from now on.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2208764 P-CR Approval 23.700-41: KI#3: Proposal for Evaluation and Conclusion for KI#3. Ericsson Rel-18 Merged into S2-2209301 Haiyang (Huawei) suggests to merge this paper into 8413
Ashok (Samsung) comments URSP solution does not work for temporary slice as proposed in 8764 and 8413 paper
Jinguo(ZTE) suggest that this paper can focus on temporary network slice part, mainly on the URSP extension with a new indication.
Srisakul (NTT DOCOMO) comments. Updating URSP for slice decommissioning is also quite complex and might not be backward-compatible with existing mechanisms/logics of other 5GC NF.
Peter Hedman (Ericsson) provides reply to Srisakul
Peter Hedman (Ericsson) provides reply to Haiyang
Stefano (Qualcomm) expresses concerns on the solution and cannot accept the conclusions of forcing a UE to re-evaluate URSP rules for existing PDU sessions. Suggests to use 8802 as the basis.
Alessio(Nokia) proposes that this is noted and 8802 is used as basis.
Peter Hedman (Ericsson) provides reply to QC and r01 to address QC comment.
alessio(Nokia) comments that we no longer want to discuss this paper based on Jinguo direction but the new added text in r01 is implying the RAN has to become aware if the UE supports the URSP enhancement. we do not understand why we need to go down this route that also requires anyhow UE vendors to implement the URSP enhancements . the text is unclear as it does not explain which node releases the session...so we do not accept this r01 also for this reason -please kleep discussion in one document.
==== Revisions Deadline ====
Peter Hedman (Ericsson) provides comments that RAN does not know whether there is any PDU Session established, but only if there is UP i.e. read again
Peter Hedman (Ericsson) content was merged into 08802
==== Final Deadline ====
Merged
9.14 S2-2208970 P-CR Approval 23.700-41: ENS_Ph3 KI#3 Evaluation and Conclusion for the network slice patchy support requirement part only. NEC Rel-18 CC#4: Merged into S2-2209302 Jinguo(ZTE) comments
Iskren (NEC) responds to comments from Jinguo (ZTE)
Haiyang (Huawei) comments
Alessio(Nokia) also agrees with Jinguo this paper is not suitable for KI#3 discussion and more focused on KI#5. of course this concept can be ancillary to solution like the one proposing smaller TAs are secondary TAs (a bit like sol 29,11 etc.). so it can be folded into KI#3 evaluation in the same bucket as the KI#5 solutions which enable the RA be linked to supporting uniformly the Allowed NSSAI only (i.e. to enable flexible RA allocation when e.g. smaller secondary Ras are supported.
Iskren (NEC) provides r01 with added conclusion for KI#5
==== Revisions Deadline ====
alessio(Nokia) believes we already have papers for KI#3/5 and so this is not needed. asks to not the paper as it is difficult to see how this can fit. (i.e. we cannot agree to approve this)
==== Final Deadline ====
Iskren (NEC) Tao, please mark this as merged to S2-2208802
Merged
9.14 - - - Evaluation + Conclusion for KI#4 - - Docs:=3 -
9.14 S2-2208184 P-CR Approval 23.700-41: KI#4: Proposal for Evaluation Conclusion on KI #4. Ericsson Rel-18 Merged into S2-2209302 Dongeun (Samsung) provides comments
Fenqin (Huawei) suggest to merge this paper to 8902
Alessio(Nokia) askes then to mark this as noted. Nokia will only comment to 8902 from now onwards.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2208902 P-CR Approval 23.700-41: KI#4: Evaluation and Conclusion for KI#4. Huawei, HiSilicon, Nokia, ZTE Rel-18 r02 agreed. Revised to S2-2209302, merging S2-2208184 and S2-2208970 Fenqin(Huawei) provides r01
George (Ericsson) provides r02. Removed change on change. Added Ericsson as co-signer
Fenqin (Huawei) provides r03 to clarify the roaming case.
George (Ericsson) provides response, I don't understand what the not means.
Fenqin (Huawei) replies to George.
George (Ericsson) provides response. I want that postponed for next meeting or normative phase. SO we are not Ok with r03.
==== Revisions Deadline ====
George (Ericsson) Ericsson OK only with r02
alessio(Nokia) notwithstanding the Ericsson position on this thread: the primary NSACF is used in roaming too. so this should be clear. So the normative work shall proceed for both roaming and non roaming . I hope Ericsson agrees.
George (Ericsson) responds
Jinguo(ZTE) suggests to go with r02, and leave the roaming aspect for next meeting.
==== Final Deadline ====
Revised
9.14 S2-2209302 P-CR Approval 23.700-41: KI#4: Evaluation and Conclusion for KI#4. Huawei, HiSilicon, Nokia, ZTE, Ericsson Rel-18 Revision of S2-2208902r02, merging S2-2208184 and S2-2208970. Approved Approved
9.14 - - - Evaluation + Conclusion for KI#5 - - Docs:=6 -
9.14 S2-2208411 P-CR Approval 23.700-41: Evaluation and conclusion for KI#5 . Huawei, HiSilicon Rel-18 r04 + changes agreed. Revised to S2-2209303, merging S2-2208881 and S2-2209114 Jinguo(ZTE) propose to use this paer for conclusion of partially rejected NSSAI
Haiyang (Huawei) is OK to use this paper for conclusion of partially rejected NSSAI
Peter Hedman (Ericsson) provides comments
Jinguo(ZTE) suggest to use 8765 as basis for evaluation part.
Haiyang (Huawei) thinks 8411 has a better structure for evaluation.
Jinguo(ZTE) is also fine to take 8411 as basis for evaluation
Kundan(NEC) suggests to use one paper for all conclusions and provides further comments.
Haiyang (Huawei) is also fine to take 8411 as basis for whole KI#5
Peter Hedman (Ericsson) provides r01
Alessio(nokia) provides r02
Haiyang (Huawei) provides r03
Genadi (Lenovo) provides r04.
Peter Hedman (Ericsson) provides r05
==== Revisions Deadline ====
Myungjune (LGE) (LGE) objects r01, r02, 03, 04. Can accept r00, r05.
Krisztian (Apple) can accept r05. We also object to r01-r04 due to RAN impacts. r00 is incomplete.
Tao(VC) ask to list the modification on top of r04 to reflect r05.
Haiyang (Huawei) indicates r05 is : r04+ removing 'The connected mode behaviour can be based on sol.29 principle'+ add 'The S-NSSAIs of the Partially Allowed S-NSSAI are provided to the NG-RAN as part of Allowed NSSAI assuming there is no impact to the NG-RAN.'
Genadi (Lenovo) prefers r05.
alessio(Nokia) can live with r05 only if this is removed
'The S-NSSAIs of the Partially Allowed S-NSSAI are provided to the NG-RAN as part of Allowed NSSAI assuming there is no impact to the NG-RAN.'

as in no solution this was proposed. the RAN impact if any can be judged when we have RAN feedback by the way we thing the text above has RAN impact as now we allow some S-NSSAIs where the S-NSSAI is not supported so the rAN may even enter error conditions and if it does note we also expect new behaviour (basically now we say a certain S_NSSAI si allowed but in reality it is not in a TA so the RAN can get confused!). At least solution 29 hadd a reasoned behaviour here it is totally open and not documented.
alessio(Nokia) by the way r05 is after submission. so in principle we prefer r02/3/4
Myungjune (LGE) proposes to agree r00
Peter Hedman (Ericsson) propose to agree r05 + moving the sentence 'The S-NSSAIs of the Partially Allowed S-NSSAI are provided to the NG-RAN as part of Allowed NSSAI assuming there is no impact to the NG-RAN' to an EN. Objects to r02-r04 and r00 is incomplete.
Jinguo(ZTE) propose to agree r04+ removing 'The connected mode behaviour can be based on sol.29 principle'+ add EN: it is FFS whether the S-NSSAIs of the Partially Allowed S-NSSAI provided to the NG-RAN as part of Allowed NSSAI has any impact to the NG-RAN.'
Alessio(Nokia) ok also to update r04+ removing 'The connected mode behaviour can be based on sol.29 principle' no need to add more EN or text that is probably not going to see much agreement.
Jinguo(ZTE)suggest to go r04+ removing 'The connected mode behaviour can be based on sol.29 principle'
==== Final Deadline ====
Peter Hedman (Ericsson) provides comments and not really happy with the approved revision, and suggest to add 'EN: it is FFS whether S-NSSAIs of the Partially Allowed S-NSSAI can be provided to the NG-RAN as part of Allowed NSSAI assuming there is no impact to the NG-RAN'
Revised
9.14 S2-2209303 P-CR Approval 23.700-41: Evaluation and conclusion for KI#5 . Huawei, HiSilicon Rel-18 Revision of S2-2208411r04 + changes, merging S2-2208881 and S2-2209114. Approved Approved
9.14 S2-2208765 P-CR Approval 23.700-41: KI#5: Proposal for Evaluation and Conclusion for KI#5. Ericsson Rel-18 Noted Jinguo(ZTE) propose to use this paer for conclusion of partially rejected NSSAI
Haiyang (Huawei) thinks Jinguo(ZTE) meant to use this paper for conclusion of partially Allowed NSSAI
Haiyang (Huawei) comments
Myungjune (LGE) has concern on RAN impact.
Ashok (Samsung) comments
Peter Hedman (Ericsson) provides comments and r01
alessio(Nokia) cannot agree to use this paper as basis for partially allowed NSSAI as there is no pointer to any solution describing the handling of the connected mode for these s-NSSAI. for the rejected S-NSSAI there is the apple paper, our paper or Huawei paper. my suggestion is to use the Huawei paper as overall baseline and we see how we can add the partially allowed concept but in a complete manner including the connected mode mobility etc. the nokia paper is to use appropriate to handle the partially allowed (if anything because it posits to the solution defining how it actually works). Also the issue of overlapping TAs is not addressed and we need to cover that(see sol 29 update)
Peter Hedman (Ericsson) provides reply to Nokia
Kundan(NEC) requests to use only one paper for all conclusions. otherwise it will be difficult to track the conclusions.
alessio(nokia) assumes the discussion is not based on 8411 and asks to mark this as noted.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.14 S2-2208821 P-CR Approval 23.700-41: Conclusion on KI#5. ZTE Rel-18 Noted Haiyang (Huawei) comments
Myungjune (LGE) comments
Ashok (Samsung) comments
Jinguo(ZTE) replies
Myungjune (LGE) replies to Jinguo(ZTE)
Haiyang (Huawei) ask a question
Jinguo(ZTE) replies to Myungjune (LGE)
alessio(Nokia) proposes this is noted if agreeable the way forward of this paper added to 8411. we also note the discussion on whether this is in scope.
==== Revisions Deadline ====
Myungjune (LGE) proposes to NOTE.
==== Final Deadline ====
Noted
9.14 S2-2208881 P-CR Approval 23.700-41: Evaluation and conclusion for KI#5: Improved support of RAs including TAs supporting Rejected S-NSSAIs . Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209303 Jinguo(ZTE) propose to use 8411 for discussion on partially rejected NSSAI and 8765 for discussion on partially allowed NSSAI
Myungjune (LGE) has concern on RAN impact.
Alessio(Nokia) does not agree to split the conclusion on KI#5 over two threads. So either we use this paper or we use 8411 that was the baseline... up to you...
Peter Hedman (Ericsson) provides comments and concerns.
Alessio(Nokia) ok to merge this into 8411
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2209114 P-CR Approval 23.700-41: KI#5: Evaluation and interim conclusion. Apple Rel-18 Merged into S2-2209303 Jinguo(ZTE) suggest to merge this paper into 8411
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 - - - Evaluation + Conclusion for KI#6 - - Docs:=5 -
9.14 S2-2208871 P-CR Approval 23.700-41: KI#6: Evaluation and conclusion. Samsung Rel-18 CC#3: r13 + changes agreed. Revised to S2-2209945. Myungjune (LGE) provides r02.
George (Ericsson) provides r03 and comments below
Myungjune (LGE) replies to George (Ericsson).
Ashok (Samsung) provides comments
Genadi (Lenovo) comments on the inactivity timer for PDU Session release and S-NSSAI deregistration.
George (Ericsson) provides responses
Genadi (Lenovo) comments on the implicit/explicit deregistration of S-NSSAI in AMF and UE.
Iskren (NEC) expresses provides comments
George (Ericsson) provides r04
Fenqin (Huawei) provides r05
George (Ericsson) Ericsson not OK with rev 05. The case for AF is very fluffy and is unclear. Questions asked not addressed at all.
Fenqin (Huawei) responds to George
George (Ericsson) asks. What do U mean by NSAC is to be controlled. And by who ? NSAC is an operator NF.
U need to provide clarity how this works and why needed.
Fenqin (Huawei) provides further responds to George
Ashok (Samsung) comments
Ashok (Samsung) clarifies to Genadi (Lenovo)
Fenqin (Huawei) provides response to Ashok
Myungjune (LGE) provides r06.
George (Ericsson) provides r07
Fenqin (Huawei) provides r08.
George (Ericsson) Not OK with this revision, I already indicated that this is already covered. NSAC is not an authorized AF. It belongs to the PLMN, so the wording is wrong. If it is an external server then definitely we are against that. If it is NSAC then this is not an AFG.
SO which one is it./
U can add at most a NOTE stating that Ur case over r07. The note can say: this covers the case of NSAC......
Fenqin(Huawei) we are not ok with r07.
George (Ericsson) provides response. This is not described in any of the solutions.
Fenqin(Huawei) provides response to George.
Fenqin(Huawei) ask one question to George.
Fenqin(Huawei) give feedback to George.
Ashok (Samsung) agrees with George (Ericsson)
George (Ericsson) provides text inline
George (Ericsson) provided what Ericsson will accept in a previosu email Ashok is correct. This cant be open ended as it is now. It is up to Fenqin now.
Fenqin (Huawei) provides r09
George (Ericsson) provides r10
George (Ericsson) provides r11
George (Ericsson) provides r12
Ashok (Samsung) provides r13
George (Ericsson) provides comments
Ashok (Samsung) provides reply
George (Ericsson) responds
Ashok (Samsung) replies
==== Revisions Deadline ====
George (Ericsson) Ericsson accepts only r12 or r13
Myungjune (LGE) supports r13.
Krisztian (Apple) supports r13 and objects to r12, r11.
Fenqin (Huawei) support to go with r13.
alessio(Nokia) provides r11
Genadi (Lenovo) is fine with r13, although it is not clear why the description of AF initiated inactivity timer configuration is described twice.
alessio(Nokia) can only accept r12, r11
alessio(Nokia) replies to KKISS(Apple) the explicit release timer in supporting UE only causes an explicit release from UE not from network!! the non-supporting UE release if FROM the network with timers running in network. I hope this explains the difference.
Ashok (Samsung) explains to Alessio(Nokia) and propose to agree r13
Jinguo(ZTE) supports to go with r13
Ashok (Samsung) not ok with r12, r11, propose to go with r13
George (Ericsson) Indeed this is not my revision. Alessio thinks too much about me so he added my name to his revision ??
Alessio(Nokia) replies to Ashok (Samsung) there is no duplication as the role is different and also the impact is different (in UE and especially in network). we object to moving forward without adding this options 2 as it mean the network ALWAYS has to run timers . so we only accept r12 or r11.
Alessio(Unfortunately has to object to rel-13. we want an option where the network has not to run timers.
Ashok (Samsung) comments that network cannot avoid the scenario of not running timer because it has to support non-supporting UE as well.
Iskren (NEC) suggests to go with r13. We cannot accept versions with timers in the UE only.
George (Ericsson) responds. So if the network does not enforce policies will the network really trusts all UEs. I mean it is incomprehensible that this will be acceptable.
alessio(Nokia) if this is a matter of trusting the UE then we cannot really trust the UE either to have release the slice locally 9or to do anything really)... the UE behaviour is conformance tested... and the whole point to do this KI was to program the UE really. but maybe Krisztian can tell us if UEs can be trusted.
George (Ericsson) responds No they cant be trusted. U can go to the GSMA and look at misbehaving UEs. Then U can understand why no operator will buy into Ur argument.
alessio( Nokia) we can live with 13 keeping the explicit release of PDU sessions with the hysteresis timer. (the explicit release timer running in UE only to decide when to release a session after the last app is detected to not use the session anymore.). otherwise 12 or 11
Ashok (Samsung) provides reply.
Jinguo(ZTE) asks for CC#3.
alessio replies to jinguo: yes we want to reinstate this bullet: I ndication of the time after which a PDU session is explicitly released after no application is detected to need it at the UE (timer running at UE only). The timer is provided by HPLMN or VPLMN of HPLMN allows any existing methods for UE configuration. After the timer expiry UE explicitly update SMF about PDU release.
==== Final Deadline ====
Revised
9.14 S2-2209945 P-CR Approval 23.700-41: KI#6: Evaluation and conclusion. Samsung, NEC Rel-18 Revision of S2-2208871r13 + changes. Approved Approved
9.14 S2-2208185 P-CR Approval 23.700-41: KI 1: Proposal for Evaluation and Conclusion on KI #6. Ericsson Rel-18 Merged into (Covered by) S2-2208871 Jinguo(ZTE) suggest to use 8871 as basis for KI#6 discussion
Fenqin (Huawei) also suggest to discuss in 8871.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2208903 P-CR Approval 23.700-41: KI#6, Evaluation and conclusion of Solutions of KI#6. Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208871 Jinguo(ZTE) suggest to use 8871 as basis for KI#6 discussion
George Foti (Ericsson) provides comments
George (Ericsson) provides r01. OK to use 8871 as a basis.
alessio(Nokia) agrees with Jinguo and also there are some inaccurate evaluations in places as e.g. solution 38 is only considered to be PCF based. so we would ask to note this and use the Samsung paper 8871
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 S2-2209029 P-CR Approval 23.700-41: KI #6, Solution Evaluation and conclusions . Vivo Rel-18 Merged into (Covered by) S2-2208871 Jinguo(ZTE) suggest to use 8871 as basis for KI#6 discussion
George Foti (Ericsson) proposes to consider the pCR merged in 8871.
Xiaowen (vivo) agrees to merge.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.14 - - - Solution update - - Docs:=8 -
9.14 S2-2209033 P-CR Approval 23.700-41: Update to Sol#43. Vivo Rel-18 r02 agreed. Revised to S2-2209304. Jinguo(ZTE) believes this P-CR is not needed, i.e. can be noted.
Xiaowen responses to Jinguo
Xiaowen(vivo) provides r1.
Jinguo(ZTE) comments that the figure is not updated. 3b) does not exist now.
Xiaowen(vivo) provides r02 and updates the figure according to Jinguo's comments.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.14 S2-2209304 P-CR Approval 23.700-41: Update to Sol#43. Vivo Rel-18 Revision of S2-2209033r02. Approved Approved
9.14 S2-2208410 P-CR Approval 23.700-41: KI#3, Sol#21 update to remove EN. Huawei, HiSilicon Rel-18 Noted alessio(Nokia) provides r01
Haiyang (Huawei) comments to r01
==== Revisions Deadline ====
Haiyang (Huawei) objects r01
alessio(Nokia) objects to r00 as the EN resolution is partial and does not address the issue of implementation based behaviour. we do not believe that this solution has been fully specified as it uses existing URSPs but they do not support what is claimed. can you comment on the eN content?
==== Final Deadline ====
Noted
9.14 S2-2208467 P-CR Approval 23.700-41: KI#6, Sol #32: Update to allow the PCF initiate the move of a PDU session from one slice to another . Verizon Rel-18 Approved Jinguo(ZTE) provides r01
Fenqin (Huawei) provides r02
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.14 S2-2208786 P-CR Approval 23.700-41: KI#1, Sol#40: Update to enable input of QoE Improvement indication from AF Alibaba Group, China Mobile Rel-18 Merged into S2-2209305 Jinguo(ZTE) suggest to merge this paper into 9046 since both papers are updating same figure in solution 40
==== Revisions Deadline ====
Xiaobo Yu (Alibaba) agrees to merge 8786 into 9046.
==== Final Deadline ====
Merged
9.14 S2-2208835 P-CR Approval 23.700-41: KI#3, Updated Solution 29: Editor's Note resolution and small optimization for MO interactions. Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.14 S2-2209046 P-CR Approval 23.700-41: Resolving ENs of solution #40. China Mobile Rel-18 r02 agreed. Revised to S2-2209305, merging S2-2208786 Jinguo(ZTE) comments
Yi (China Mobile) provides r01 to resolve comment from ZTE.
Genadi (Lenovo) comments that one Ed.Note seems not resolved.
Xiaobo Yu (Alibaba) agree to merge 8786 into 9046 and provides r02.
==== Revisions Deadline ====
==== Final Deadline ====
Xiaobo Yu (Alibaba) requests to cosign this contribution.
Revised
9.14 S2-2209305 P-CR Approval 23.700-41: Resolving ENs of solution #40. China Mobile, Alibaba Rel-18 Revision of S2-2209046r02, merging S2-2208786. Approved Approved
9.15.1 - - - Study on 5G AM Policy (FS_AMP) - - Docs:=0 -
9.15.2 - - - 5G AM Policy (AMP) - - Docs:=12 -
9.15.2 S2-2208176 CR Approval 23.503 CR0739 (Rel-18, 'B'): New timer from PCF along with RFSP Index to direct a UE to 4G China Telecom, Ericsson Rel-18 r06 agreed. Revised to S2-2209677, merging S2-2208422 Haiyang (Huawei) provides comments
Zhuoyi (China Telecom) suppose to unify the name as 'Validity time for RFSP Index in use' for the new timer and apply it to other CRs in 9.15.2.
Judy (Ericsson) responds to Haiyang (Huawei)
Haiyang (Huawei) comments
Zhuoyi (China Telecom) responds to Haiyang (Huawei)
Judy (Ericsson) comments
Zhuoyi (China Telecom) provides r01.
Haiyang (Huawei) provides r02
Judy (Ericsson) provides r03
Zhuoyi (China Telecom) prefers r03.
Haiyang (Huawei) provides r04
Pallab comments on r04.
Haiyang (Huawei) provides reply to Pallab (Nokia)
Zhuoyi (China Telecom) respondes to Pallab.
Zhuoyi (China Telecom) provides r05.
Judy (Ericsson) provides r06
Pallab responds to Zhuoyi (China Telecom)
Zhuoyi (China Telecom) responds to Pallab.
==== Revisions Deadline ====
Judy (Ericsson) prefer r06, objects to r02/r04/r05
Pallab (Nokia) also proposes to approve r06. Would like to co-sign
Zhuoyi (China Telecom) replies to Nokia.
Haiyang (Huawei) proposes to approve r06 + 'Editor's Note: Whether PCF needs to be aware the modified RFSP index indicates a change of priority from 5GC to EPC is FFS.' As per discussion in 8343 thread
==== Final Deadline ====
Revised
9.15.2 S2-2209677 CR Approval 23.503 CR0739R1 (Rel-18, 'B'): New timer from PCF along with RFSP Index to direct a UE to 4G China Telecom, Ericsson, Huawei, HiSilicon, Nokia Rel-18 Revision of S2-2208176r06, merging S2-2208422. Approved Agreed
9.15.2 S2-2208343 CR Approval 23.501 CR3710 (Rel-18, 'C'): RFSP index in use at 5GS to EPS mobility Ericsson, China Telecom Rel-18 r09 agreed. Revised to S2-2209678. Haiyang (Huawei) comments
Ashok (Samsung) comments and provides r01
Pallab (Nokia) comments and provides r02
Judy (Ericsson) provides r03
Haiyang (Huawei) provides r04
Judy (Ericsson) comments that r04 removes the high level description of the AMP function which should be added back and provides r05
Judy (Ericsson) provides r06, changing '4G access' to 'EPC/EUTRAN access'
Pallab (Nokia) asks what is 'EPC/EUTRAN access'
Judy (Ericsson) responds to Pallab (Nokia) that 'EUTRAN access' seems to be a better wording
Judy (Ericsson) provides r07, removing 'EPC' from 'EPC/UETRAN access'
Haiyang (Huawei) can only accept r04
Pallab (Nokia) provides r09 based on r07. Would like to co-sign. Please ignore r08
Judy (Ericsson) thanks Pallab (Nokia) for the support
==== Revisions Deadline ====
Judy (Ericsson) objects to r04, prefers r09
Pallab (Nokia) proposes to approve r09
Haiyang (Huawei) proposes to postpone
Judy (Ericsson) responds to Haiyang (Huawei)
Zhuoyi (China Telecom) responds to Judy (Ericsson)
Haiyang (Huawei) responds
Haiyang (Huawei) is OK with r09 + 'Editor's Note: Whether PCF needs to be aware the modified RFSP index indicates a change of priority from 5GC to EPC is FFS.'
Judy (Ericsson) provides postDL revision r10=r09 + 'Editor's Note: Whether PCF needs to be aware the modified RFSP index indicates a change of priority from 5GC to EPC is FFS'
==== Final Deadline ====
Revised
9.15.2 S2-2209678 CR Approval 23.501 CR3710R1 (Rel-18, 'C'): RFSP index in use at 5GS to EPS mobility Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-18 Revision of S2-2208343r09. Approved Agreed
9.15.2 S2-2208344 CR Approval 23.502 CR3557 (Rel-18, 'C'): RFSP index in use at 5GS to EPS mobility Ericsson, China Telecom Rel-18 r04 agreed. Revised to S2-2209611, merging S2-2208421 Judy (Ericsson) responds to Haiyang (Huawei)
Haiyang (Huawei) provides comments
Haiyang (Huawei) comments
Pallab (Nokia) provides comments
Judy (Ericsson) provides r01
Haiyang (Huawei) provides r02
Judy (Ericsson) provides r04 (please ignore r03)
Haiyang (Huawei) objects r04
==== Revisions Deadline ====
Pallab (Nokia) OK to approve r04. Would like to co-sign
Judy (Ericsson) thanks Pallab (Nokia) for your support, and expect Huawei to withdraw objection to r04 per guidance from rapporteurs of 23.401/501/502.
Haiyang (Huawei) comments and can accept r04 with expecting we will have clean up on AM Policy parameters in the future
==== Final Deadline ====
Revised
9.15.2 S2-2209611 CR Approval 23.502 CR3557R1 (Rel-18, 'C'): RFSP index in use at 5GS to EPS mobility Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-18 Revision of S2-2208344r04, merging S2-2208421. Approved Agreed
9.15.2 S2-2208420 CR Approval 23.501 CR3713 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon Rel-18 r06 agreed. Revised to S2-2209612. Haiyang (Huawei) comments
Judy (Ericsson) comments that clause 5.3.4.3 is for 5GS thus should not be updated for EPS-5GS interworking
Haiyang (Huawei) comments and thinks this paper should be handled separately
Judy (Ericsson) proposes to merge this paper to 8343 and comment
Ashok (Samsung) comments
Zhuoyi (China Telecom) agrees with Ashok and Haiyang.
Pallab (Nokia) agrees with Zhuoyi (China Telecom), Ashok (Samsung), Haiyang (Huawei) and proposes to keep this CR
Judy (Ericsson) provides r01 and comments
Haiyang (Huawei) provides r02
Haiyang (Huawei) provides comments
Pallab (Nokia) has the same comment: what is 'EPC/EUTRAN access'? Can we change it to 'E-UTRAN access' or may be 'LTE access'?
Judy (Ericsson) responds to Pallab (Nokia) that 'E-UTRAN access' seems to be a better wording, and comment on r02
Haiyang (Huawei) provides r03
Judy (Ericsson) provides r05 based on r01 (please ignore r04), changing '5GS' to '5G access', and 'EPS' to 'EUTRAN access'
Zhuoyi (China Telecom) comments.
Pallab (Nokia) comments
Judy (Ericsson) provides r06, changing 'EUTRAN' to 'E-UTRAN'
==== Revisions Deadline ====
Judy (Ericsson) can accept r01/r05/r06, objects to other revisions (including r00)
Haiyang (Huawei) proposes to postpone
Haiyang (Huawei) is OK with r06 now as per discussion in 8343
==== Final Deadline ====
Revised
9.15.2 S2-2209612 CR Approval 23.501 CR3713R1 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2208420r06. Approved Agreed
9.15.2 S2-2208421 CR Approval 23.401 CR3712 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon Rel-18 Merged into S2-2209611 Judy (Ericsson) comment this paper is not needed as the impact to EPS due to 5GS interworking should be captured in 23.502 instead of 23.401.
Ashok (Samsung) comments
Haiyang (Huawei) provides feedback.
Juan Zhang (Qualcomm) provides comments
Judy (Ericsson) comments
Ashok (Samsung) completely agrees with Judy (Ericsson)
Haiyang (Huawei) provides r01.
Zhuoyi (China Telecom) can live with r01.
==== Revisions Deadline ====
Judy (Ericsson): this paper can be marked as merged to 8344 based on offline discussion.
Pallab (Nokia) wants to check if this CR be considered as merged to 8344r04
Haiyang (Huawei) is OK to merge this paper to 8344r04 based on offline discussion
==== Final Deadline ====
Merged
9.15.2 S2-2208422 CR Approval 23.503 CR0744 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon Rel-18 Merged into S2-2209677 ==== Revisions Deadline ====
Judy (Ericsson): Andy, this paper has been merged to 8176 based on discussion in 8176 thread
==== Final Deadline ====
Merged
9.15.2 S2-2208423 CR Approval 23.502 CR3564 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2209679. Haiyang (Huawei) thinks this paper can be handled separately as suggested by the Rapporteur
Judy (Ericsson) proposes to merge this paper to 8344
Haiyang (Huawei) provides r01 (just to align the term)
Judy (Ericsson) asks question about Rapporteur's proposal
Zhuoyi (China Telecom) responses to Judy and provides r02.
Judy (Ericsson) comment
Haiyang (Huawei) provides r03 as an Alt
Pallab (Nokia) comments on r03
Haiyang (Huawei) provides reply to Pallab (Nokia)
Judy (Ericsson) comments that the change in r03 is not related to AMP
Haiyang (Huawei) provides reply to Judy
Zhuoyi (China Telecom) comments and provides r04.
Judy (Ericsson) comment that r04 does not include any change to TS23.502, and propose to either NOTE this paper or merge to 8344
Zhuoyi (China Telecom) replies to Ericsson.
Judy (Ericsson) responds to Zhuoyi (China Telecom)
Haiyang (Huawei) comments
==== Revisions Deadline ====
Zhuoyi (China Telecom) suggests to approve r04.
Judy (Ericsson) does not agree to this paper as is, as the update is not aligned with 23.503 update. If the author really wants to keep this CR, adding a reference to 23.503 is acceptable.
Pallab (Nokia) proposes to go with r02
Haiyang (Huawei) provides r05 as an Alt: which is r04+removing the exact values but add the reference to TS 23.503
Pallab (Nokia) is OK with r05 (which is r04+ removing the exact values but add the reference to TS 23.503)
Judy (Ericsson) proposes an after-revision update
Zhuoyi (China Telecom) is OK with r05 and I think it need to bring up to CC#?
Haiyang (Huawei) provides r06: which is r04+removing the exact values but add the reference to clauses of TS 23.503 + add Ericsson as cosigner
Ashok (Samsung) Ok with the proposal in r06
Zhuoyi (China Teleom) proposes to approve r04 + removing the exact values of 'AM Policy Information' but add the reference to clauses of TS 23.503 in Table 5.2.2.2.2-1 + add Ericsson as cosigner
==== Final Deadline ====
Revised
9.15.2 S2-2209679 CR Approval 23.502 CR3564R1 (Rel-18, 'B'): RFSP index during interworking Huawei, HiSilicon, Ericsson Rel-18 Revision of S2-2208423r04. Approved Agreed
9.16 - - - Study on Personal IoT Networks (5G_PIN) - - Docs:=39 -
9.16 S2-2208263 P-CR Approval 23.700-88: KI#1, Conclusion updates . Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Rel-18 Merged into (Covered by) S2-2208688 Marco (Huawei) proposes to merge in S2-2208688
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208264 P-CR Approval 23.700-88: KI#3, Conclusion updates . Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Rel-18 Merged into S2-2209903 Marco (Huawei) proposes to merge into 8997
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208265 P-CR Approval 23.700-88: KI#5, Conclusion updates . Ericsson Rel-18 r07 agreed. Revised to S2-2209937, merging S2-2208462. R05? Revise based on SoH Zhenhua (vivo) provides r01.
Pallab (Nokia) comments on r01.
Qian (Ericsson) provides r02 and comments.
Zhenhua (vivo) replies to Pallab (Nokia)
Jianning (Xiaomi) provide comment
Marco (Huawei) provide r03
Serge (T-Mobile USA) objects to r02 and r03, accepts r01
Zhenhua (vivo) provides r04 to reinstate bullet 3
Pallab (Nokia) objects r04.
Serge (T-Mobile USA) is ok with rev04
Zhenhua (vivo) asks question to Pallab (Nokia) and Serge (T-Mobile USA) and provide r05.
Pallab (Nokia) is OK to keep only PEGC as proposed in r05.
Marco (Huawei) r05 may be fine. Ask clarification
Zhenhua (vivo) replies to Marco (Huawei)
Marco (Huawei) replies
Qian (Ericsson) provides comments
==== Revisions Deadline ====
Jianning (Xiaomi) provide commemt
Marco (Huawei) r05 should be revised based on SoH
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r05 based on discussions in SoH of CC#2 for further consideration and agreement
Saad (interdigital) replies to Nokia
Pallab (Nokia) responds to Saad (interdigital). Proposes to approve r05+ NOTE below
NOTE: Whether PEMC UE needs a specific 5G subscription will be decided during normative phase
Pallab (Nokia) responds to Saad (interdigital). Proposes to approve r05+ NOTE below
NOTE: Whether PEMC UE needs a specific 5G subscription will be decided during normative phase
Pallab (Nokia) responds to Saad (interdigital). Proposes to approve r05+ NOTE below
NOTE: Whether PEMC UE needs a specific 5G subscription will be decided during normative phase
Boren (OPPO) asks for clarification on the NOTE proposed by Pallab (Nokia)
Marco (Huawei) asks also clarification on the NOTE proposed by Pallab (Nokia)
Marco (Huawei) comments
Pallab (Nokia) responds Marco (Huawei) and OK with the revised NOTE
Boren (OPPO) comments
Kefeng (Qualcomm) is OK to add the NOTE
Qian (Qualcomm) provides m02 to reflect the proposed EN.
Zhenhua (vivo) provides r06.
Qian (Ericsson) provides r07
Revised
9.16 S2-2209937 P-CR Approval 23.700-88: KI#5, Conclusion updates Ericsson Rel-18 Revision of S2-2208265r07, merging S2-2208462. Approved Approved
9.16 S2-2208266 P-CR Approval 23.700-88: KI#6, Conclusion updates . Ericsson Rel-18 Merged into (Covered by) S2-2208302 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208302
Zhenhua (vivo) agree the merge into S2-2208302
Jianning (Xiaomi) noticed that 8266 was approved without any comments in the ChairNotes. In fact 8266 was agreed to be merged into S2-2208302
==== Final Deadline ====
Merged
9.16 S2-2208267 P-CR Approval 23.700-88: KI#7, Conclusion . Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2208629 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208629
Zhenhua (vivo) agree the merge into S2-2208629
Jianning (Xiaomi) noticed that 8267 was approved without any comments in the ChairNotes. In fact 8267 was agreed to be merged into S2-2208629
==== Final Deadline ====
Merged
9.16 S2-2208302 P-CR Approval 23.700-88: 23.700-88: KI #6, Conclusions for KI#6. Nokia, Nokia Shanghai Bell Rel-18 CC#4: r07 agreed. Revised to S2-2209949. R06? Revise based on SoH Zhenhua (vivo) provides r01.
Kefeng Zhang (Qualcomm) provides comments.
Zhenhua (vivo) responds to Kefeng Zhang (Qualcomm).
Pallab (Nokia) comments and provides r02
Marco (Huawei) comments r02
Kefeng (Qualcomm) comments r02
Zhenhua (vivo) provides r03 according to offline CC
Suresh Srinivasan (Intel) objects to all versions of S2-2208302
Pallab (Nokia) responds to Marco (Huawei)
Pallab (Nokia) responds to Kefeng (Qualcomm)
Zhenhua (vivo) provides r04
Marco (Huawei) provides r06 on top of r04
Kefeng (Qualcomm) provides r05.
Marco (Huawei) objects to r05.
==== Revisions Deadline ====
Suresh Srinivasan (Intel) comments on r06
Kefeng (Qualcomm) proposes to reinstate following text on top of r06:
c) Non-3GPP QoS assistance information
Marco (Huawei) agree to reinstate the N3GPP QoS on top of R06. Object r05. Furthermore r06 needs to be revised based on SoH
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r06 based on discussions in SoH of CC#2 for further consideration and agreement
Zhenhua (vivo) provides r07
Revised
9.16 S2-2209949 P-CR Approval 23.700-88: 23.700-88: KI #6, Conclusions for KI#6. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208302r07. Approved Approved
9.16 S2-2208462 P-CR Approval 23.700-88: KI #5, Interim conclusions update. T-Mobile USA Rel-18 Merged into S2-2209937 Merged into S2-2208265? Zhenhua (vivo) proposes merge into S2-2208265
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208465 P-CR Approval 23.700-88: KI#3, Conclusion Update. InterDigital Inc. Rel-18 Merged into S2-2209953 Merged into S2-2209178? Zhenhua (vivo) proposes merge into S2-2209178
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208466 P-CR Approval 23.700-88: KI#7, New Conclusion . InterDigital Inc. Rel-18 Merged into S2-2209950 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208629
Zhenhua (vivo) agree the merge into S2-2208629
Jianning (Xiaomi) noticed that 8466 was approved without any comments in the ChairNotes. In fact 8466 was agreed to be merged into S2-2208629
==== Final Deadline ====
Merged
9.16 S2-2208499 P-CR Approval 23.700-88: 23.700-88: KI #4, update conclusion on KI#4 . Qualcomm Incorporated Rel-18 Merge into S2-2209952 Marco (Huawei) proposes to considered merged into S2-2209013
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208501 P-CR Approval 23.700-88: KI#4 & KI #6: update conclusion on KI #4 & KI#6 for PIN Route Selection Policy. Qualcomm Incorporated Rel-18 Merge into S2-2209952 Zhenhua (vivo) proposes to merge into S2-2209013
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208629 P-CR Approval 23.700-88: KI#1-7: Update of conclusions. Huawei, HiSilicon Rel-18 CC#4: r06 agreed. Revised to S2-2209950, merging S2-2208466. R04? Revise based on SoH Zhenhua (vivo) provides r01.
Marco (Huawei) proposes to consider as basis for KI #7 (other KIs will be removed)
Marco (Huawei) provides version r02
Zhenhua (vivo) provides r03 according to offline CC
Saad (Interdigital) provides r04
==== Revisions Deadline ====
Marco (Huawei) r04 shall to be revised based on SoH results
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r04 based on discussions in SoH of CC#2 for further consideration and agreement
Zhenhua (vivo) provides r05
Qian (Ericsson) provides r06
Revised
9.16 S2-2209950 P-CR Approval 23.700-88: KI#1-7: Update of conclusions. Huawei, HiSilicon Rel-18 Revision of S2-2208629r06, merging S2-2208466. Approved Approved
9.16 S2-2208688 P-CR Approval 23.700-88: KI#1, Conclusion Update. OPPO Rel-18 CC#4: r11 agreed. Revised to S2-2209951. R10? Revise based on SoH Zhenhua (vivo) provides r01.
Kefeng Zhang (Qualcomm) provides r02.
Zhenhua (vivo) asks questions to r02
Boren (OPPO) asks questions.
Zhenhua (vivo) provides r03.
Kefeng Zhang (Qualcomm) replies Zhenhua (vivo) and Boren (OPPO) on r02.
Pallab (Nokia) provides r04 based on r03.
Marco (Huawei) provides to r05 on top of r04
Kefeng Zhang (Qualcomm) provides comments on r04.
Zhenhua (vivo) comments on r03.
Zhenhua (vivo) provides r06
Pallab (Nokia) responds to Kefeng Zhang (Qualcomm)
Pallab (Nokia) responds to Zhenhua (vivo).
Zhenhua (vivo) replies to Pallab (Nokia)
Zhenhua (vivo) provides r07
Intel Objects to S2-2208688r07
Interdigital (Saad) also object to r07
Qian (Ericsson) provides comments
Marco (Huawei) comments on r03.
Marco (Huawei) provides comments
Marco (Huawei) reply to couple of comments
Suresh Srinivasan (Intel) relies to Qian (Ericson) and Marco (Hauwei)
Jianning (Xiaomi) provide comment
Zhenhua (vivo) replies to Marco (Huawei) on PIN signalling
Kefeng (Qualcomm) provides comments.
Zhenhua (vivo) replies to Kefeng (Qualcomm)
Jianning (Xiaomi) provide comment to Zhuanhua (vivo) and Kefeng (Qualcomm)
Jianning (Xiaomi) provide comment on agenda of the CC
Marco (Huawei) reply to Suresh Srinivasan (Intel)
Marco (Huawei) answer to Jianning (Xiaomi)
Marco (Huawei) replies to Zhenhua (vivo) on PIN signalling
Marco (Huawei) answer to Zhenhua (vivo)
Suresh Srinivasan (Objects) to all version of S2-2208688 and propose S2-2208688r08
Zhenhua (vivo) provides r09 to remove all AF/no-AF staffs according to offline CC
Suresh Srinivasan (Intel) Objects to S2-2208688r09
Zhenhua (vivo) provides r10
Pallab (Nokia) shares the same view as Qualcomm, Ericsson, Huawei that 5GC NF is not responsible for management of PIN
Zhenhua (vivo) responds to Pallab (Nokia)
Marco (Huawei) comments that some issues (AF vs NF and the consequent conclusion) will be solved only via SoH result ( Hopefully)
Qian (Ericsson) shares the view from Macro and provides further comments
Boren (OPPO) shares the same view as Zhenhua (vivo)
==== Revisions Deadline ====
Suresh Srinivasan (Intel) comments on r10
Marco (Huawei) r10 should be revised based on SoH result. Object any other versions
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r10 based on discussions in SoH of CC#2 for further consideration and agreement
Zhenhua (vivo) provides r11
Revised
9.16 S2-2209951 P-CR Approval 23.700-88: KI#1, Conclusion Update. OPPO Rel-18 Revision of S2-2208688r11. Approved Approved
9.16 S2-2208692 P-CR Approval 23.700-88: KI#4, Conclusion Update. OPPO Rel-18 Merged into (Covered by) S2-2209013 Marco (Huawei) proposes to considered merged into S2-2209013
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2208996 P-CR Approval 23.700-88: KI #4, new Annex to describe PIN Session Model. Samsung Rel-18 Merged into S2-2209903 Pallab (Nokia) provides comments
==== Revisions Deadline ====
Zhenhua (vivo) propose to merge into S2-2208997
==== Final Deadline ====
Merged
9.16 S2-2208997 P-CR Approval 23.700-88: KI #4, evaluation and conclusion update. Samsung Rel-18 r05 agreed. Revised to S2-2209903, merging S2-2208264 and S2-2208996 Zhenhua (vivo) provides r01.
Boren (OPPO) comments.
Zhenhua (vivo) comments and provides r02.
Pallab (Nokia) comments.
Jianning (Xiaomi) provide comment on r02
Marco (Huawei) provides r04 to remove conclusion part (skipped r03 due to error)
Zhenhua (vivo) replies to Jianning (Xiaomi)
Jicheol (Samsung) provides r03 to correct the figure and texts based on the discussion
Jicheol (Samsung) clarified to Marco that all the versions do NOT include conclusion part.
Jicheol (Samsung) provides r05 to make sure to remove the conclusion part from this paper.
==== Revisions Deadline ====
Marco (Huawei) oj with r05, object any other versions
==== Final Deadline ====
Revised
9.16 S2-2209903 P-CR Approval 23.700-88: KI #4, evaluation update. Samsung Rel-18 Revision of S2-2208997r05, merging S2-2208264 and S2-2208996. Approved Approved
9.16 S2-2209007 DISCUSSION Information Discussion on PIN issues and proposals vivo Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.16 S2-2209008 DISCUSSION Information Consolidated solution proposal for PIN vivo Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.16 S2-2209009 P-CR Approval 23.700-88: Consolidated solution. Vivo Rel-18 Noted Marco (Huawei) the consolidated solution must be aligned to final agreed KI conclusion
Zhenhua (vivo) replies
Qian (Ericsson) comments
Marco (Huawei) considering current discussion and SoH, I propose to note the pCR
==== Revisions Deadline ====
Kefeng (Qualcomm) propose to note the pCR.
==== Final Deadline ====
Noted
9.16 S2-2209010 P-CR Approval 23.700-88: Update interim conclusions on KI#1. Vivo Rel-18 Merged into (Covered by) S2-2208688 Marco (Huawei) proposes to considered merged into S2-2208688
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2209011 P-CR Approval 23.700-88: Editorial modification on interim conclusions of KI#2. Vivo Rel-18 r01 agreed. Revised to S2-2209904. Zhenhua (vivo) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.16 S2-2209904 P-CR Approval 23.700-88: Editorial modification on interim conclusions of KI#2. Vivo Rel-18 Revision of S2-2209011r01. Approved Approved
9.16 S2-2209012 P-CR Approval 23.700-88: Update interim conclusions on KI#3. Vivo Rel-18 Merge into S2-2209953 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2209178
Zhenhua (vivo) agree the merge into S2-2209178
Jianning (Xiaomi) noticed that 9012 was approved without any comments in the ChairNote. In fact 9012 was agreed to be merged into S2-2209178, but the ChairNote didn't capture that information
==== Final Deadline ====
Merged
9.16 S2-2209013 P-CR Approval 23.700-88: Update interim conclusions on KI#4. Vivo, Inspur Rel-18 CC#4: r17 agreed. Revised to S2-2209952, merging S2-2208499 and S2-2208501. R14? Revise based on SoH Zhenhua (vivo) provides r01.
Kefeng Zhang (Qualcomm) provides r02.
Boren (OPPO) comments.
Zhenhua (vivo) comments on r02.
Kefeng (Qualcomm) replies Zhenhua (vivo) comments on r02.
Zhenhua (vivo) answers to Kefeng (Qualcomm).
Pallab (Nokia) provides r03 based on r02.
Zhenhua (vivo) provides r04.
Kefeng (Qualcomm) provides r05.
Jianning (Xiaomi) provide comment on r05
Interdigital (Saad) asks question for clarification
Qian (Ericsson) asks also for clarification
Kefeng Zhang replies Jianning (Xiaomi) on Q2.
Kefeng (Qualcomm) replies Qian (Ericsson) comments on Bullet 1.
Zhenhua (vivo) replies and provide r06
Yang (OPPO) provides comment
Zhenhua (vivo) provides r07 according to offline CC
Qian (Ericsson) provides comments and r08
Kefeng (Qualcomm) comments r08.
Zhenhua (vivo) comments.
Kefeng (Qualcomm) provides comments to r07.
Zhenhua (vivo) replies to Kefeng (Qualcomm).
Zhenhua (vivo) provides r09.
Kefeng (Qualcomm) replies Zhenhua (vivo).
Zhenhua (vivo) replies Kefeng (Qualcomm).
Pallab (Nokia) provides comments.
Pallab (Nokia) provides further comments.
Zhenhua (vivo) replies to Pallab (Nokia)
Zhenhua (vivo) replies to Pallab (Nokia).
Pallab (Nokia) responds to Zhenhua (vivo)
Pallab (Nokia) responds to Zhenhua (vivo).
Zhenhua (vivo) replies to Pallab (Nokia) and provides r10
Zhenhua (vivo) answers to Pallab (Nokia)
Zhenhua (vivo) answers to Pallab (Nokia).
Jicheol (Samsung) provides r11.
Jianning (Xiaomi) provide view
Marco (Huawei) provide r12 on top of r10
Qian (Ericsson) asks questions on r10
Zhenhua (vivo) answers to Qian (Ericsson) and provide r13
Walter Dees (Philips) requests clarification on x4
Zhenhua (vivo) replies to Walter Dees (Philips)
Jianning (Xiaomi) provide r15 on top of r13
Michele Zarri (Huawei) provides revision 14
==== Revisions Deadline ====
Jianning (Xiaomi) provides comment
Pallab (Nokia) comments that r14 shall be revised based on SoH result in CC#2
Marco (Huawei) R14 should be revised based on SoH. Object any version from 00 to r12.
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r14 based on discussions in SoH of CC#2 for further consideration and agreement
Pallab (Nokia) objects to revision R14-m01 as concerns raised in earlier revisions have not been addressed. Also proposes clean-up of the conclusions in a new revision
Zhenhua (vivo) provides r16
Qian (Ericsson) provides r17
Revised
9.16 S2-2209952 P-CR Approval 23.700-88: Update interim conclusions on KI#4. Vivo, Inspur Rel-18 Revision of S2-2209013r17, merging S2-2208499 and S2-2208501. Approved Approved
9.16 S2-2209014 P-CR Approval 23.700-88: Update interim conclusions on KI#5. Vivo Rel-18 Merged into (Covered by) S2-2208265 Zhenhua (vivo) proposes to merge into S2-2208265
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2209015 P-CR Approval 23.700-88: Update interim conclusions on KI#6. Vivo Rel-18 Merged into (Covered by) S2-2208302 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208302
Zhenhua (vivo) agree the merge into S2-2208302
Jianning (Xiaomi) noticed that 9015 was approved without any comments in the ChairNotes. In fact 9015 was agreed to be merged into S2-2208302, but the ChairNotes didn't capture that information
==== Final Deadline ====
Merged
9.16 S2-2209016 P-CR Approval 23.700-88: Add interim conclusions on KI#7. Vivo Rel-18 Merged into (Covered by) S2-2208629 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208629
Zhenhua (vivo) agree the merge into S2-2208629
Jianning (Xiaomi) noticed that 9016 was approved without any comments in the ChairNotes. In fact 9016 was agreed to be merged into S2-2208629, but the ChairNotes didn't capture that information
==== Final Deadline ====
Merged
9.16 S2-2209145 P-CR Approval 23.700-88: KI#1: Update to Conclusion on Key Issue#1 Resolving EN(s). Intel Rel-18 Merged into (Covered by) S2-2208688 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208688.
Zhenhua (vivo) agree the merge into S2-2208688.
Jianning (Xiaomi) noticed that 9145 was approved without any comments in the ChairNotes. In fact 9145 was agreed to be merged into S2-2208688, but the ChairNotes didn't capture that information
==== Final Deadline ====
Merged
9.16 S2-2209146 P-CR Approval 23.700-88: KI#6: Update to Conclusion on key Issue#6. Intel Rel-18 Merged into (Covered by) S2-2208302 Zhenhua (vivo) proposes merge into S2-2208302
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2209176 P-CR Approval 23.700-88: Update conclusion for KI#1 . Xiaomi Rel-18 Merged into (Covered by) S2-2208688 Marco (Huawei) proposes to consider this merged into S2-2208688
Jianning (Xiaomi) is ok to merge into 8688
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.16 S2-2209177 P-CR Approval 23.700-88: Update conclusion for Key Issue#7 . Xiaomi Rel-18 Merged into (Covered by) S2-2208629 ==== Revisions Deadline ====
Kefeng (Qualcomm) proposes to merge into S2-2208629.
Zhenhua (vivo) agree the merge into S2-2208629.
Jianning (Xiaomi) noticed that 9177 was approved without any comments in the ChairNotes. In fact 9177 was agreed to be merged into S2-2208629, but the ChairNotes didn't capture that information
==== Final Deadline ====
Merged
9.16 S2-2209178 P-CR Approval 23.700-88: Update conclusion for Key Issue#3 . Xiaomi Rel-18 CC#4: r06 agreed. Revised to S2-2209953, merging S2-2208465 and S2-2209012. R03? Revise based on SoH Zhenhua (vivo) provides r01.
Qian (Ericsson) provides r02.
Zhenhua (vivo) provides r03 according to offline CC.
Jianning (Xiaomi) provide r04 to try to capture the both NF and AF based option
Zhenhua (vivo) comments on r04
Marco (Huawei) objects to r04 since the intention of have both options for SoH is not clearly reflected
==== Revisions Deadline ====
Marco (Huawei) which revision is most suitable for revision to match SoH needs to be determined.
Zhenhua (vivo) is OK to use r03 recorded in Chair note as basis for SOH.
Jianning (Xiaomi) is ok for either r03 or r04 for furtuer revision based on SoH
==== Final Deadline ====
Pallab (Nokia) requests rapporteur to provide revision of r03 based on discussions in SoH of CC#2 for further consideration and agreement
Saad (interdigital) replies to Nokia
Marco (Huawei) objects to r03-m3
Pallab (Nokia) NOT OK with r03-m3.
OK with r03-m2
Qian (Ericsson) shares the same view that r03-m2 is ok, but is not ok with r03-m3
Kefeng (Qualcomm) is not OK with r03-m3., which is not align with the result of SOH.
OK with r03-m2.
Jianning (Xiaomi) provide comment on r03-m2
Qian (Ericsson) provides comments
Marco (Huawei) provides comments
Pallab (Nokia) comments
Jianning (Xiaomi) comment and suggest to go r03-m2 with NOTE as 'NOTE: whether and how to support the validity duration and time validity of a PIN will determine in normative phase.'
Zhenhua (vivo) provides r05
Qian (Ericsson) provides r06
Revised
9.16 S2-2209953 P-CR Approval 23.700-88: Update conclusion for Key Issue#3 . Xiaomi Rel-18 Revision of S2-2209178r06, merging S2-2208465 and S2-2209012. Approved Approved
9.17.1 - - - Study on evolution of IMS multimedia telephony service (FS_NG_RTC) - - Docs:=27 -
9.17.1 - - - General issues - - Docs:=1 -
9.17.1 S2-2208530 DISCUSSION Discussion Discussion related to IMS Data Channel and 3GPP PS Data Off. Deutsche Telekom Rel-18 Noted Hao (ZTE) comments.
Yi (China Mobile) comments.
Rainer (Nokia) agrees with Yi (China Mobile).
Kefeng Zhang (Qualcomm) provides comments.
Leo (Deutsche Telekom) replies to Kenny, Yi, Rainer.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.17.1 - - - KI#1: Solution updates - - Docs:=15 -
9.17.1 S2-2208181 P-CR Approval 23.700-87: KI#1, 4: Update to solution 20. Ericsson Rel-18 Postponed Mu (Huawei) comments
Yi (China Mobile) comments.
Kefeng (Qualcomm) comments.
James Jin(vivo) provides comments
George (Ericsson) provides response.
George (Ericsson) provides answer
Kefeng (Qualcomm) provides further comments.
George (Ericsson) provides More responses inline to Y, and more to Kenny
Hao (ZTE) comments.
George (Ericsson) provides responses in line
George (Ericsson) provides r01. Removed the extra sequence diagram.
Rainer (Nokia) asks for clarification.
George (Ericsson) provides comments inline, and r02
Kefeng (Qualcomm) provides comments.
George (Ericsson) provides r03
Rainer (Nokia) is ok to add the EN.
George (Ericsson) provides response. Good question and I don't now the answer, I already asked Yi. He wanted a SOH and I don't think we are ready or this is needed. We need more discussion after this. May be can be captured.
Rainer (Nokia) replies.
==== Revisions Deadline ====
Yi (China Mobile) ask to postpone this contribution to next meeting.
Rainer (Nokia) is ok to postpone 8181 and 9041.
==== Final Deadline ====
Postponed
9.17.1 S2-2208442 P-CR Approval 23.700-87: KI#1: Sol#20 update of architecture figures. Nokia, Nokia Shanghai Bell Rel-18 Approved George Foti (Ericsson) proposes to note the pCR and considers this merged into 8181 as it addressed the same thing.
Rainer (Nokia) is ok to mark 8442 merged into 8181.
==== Revisions Deadline ====
Rainer (Nokia) asks to agree on 8442.
Hao (ZTE) supports approving this paper.
==== Final Deadline ====
Approved
9.17.1 S2-2209041 P-CR Approval 23.700-87: KI#1, Update of solution #20. China Mobile, Huawei, Hisilicon, ZTE Rel-18 Postponed George Foti (Ericsson) provides comments
Mu (Huawei) comments
Yi (China Mobile) replies to Mu and George. R01 is provided.
George (Ericsson) provides response. There are fundamental functional differences that needs to be resolve for the 2 updated solutions 20.
Rainer (Nokia) comments.
Hao (ZTE) responds.
Yi (China Mobile) replies and provides r02.
==== Revisions Deadline ====
George (Ericsson) Ericsson not Ok with any revision including the original. We prefer to use 8181 as a basis for discussion as it has a lot more description and clarification.
Hao (ZTE) proposes to POSTPONE this paper.
Rainer (Nokia) agrees to postpone 9041.
==== Final Deadline ====
Postponed
9.17.1 S2-2208506 P-CR Approval 23.700-87: KI#1, Update solution #20 to merge with existing solution #18. Vivo Rel-18 r02 agreed. Revised to S2-2209613. James Jin (vivo) replies to questions from George Foti (Ericsson) and explains that it is a separate problem different from 8181.
George Foti (Ericsson) proposes to note the pCR. This can be incorporated in existing updates to solution 20 such as 8181
Yi (China Mobile) ask a question.
James Jin (vivo) replies to questions from Yi (China Mobile).
Kefeng (Qualcomm) provides r01.
James Jin (vivo) replies to Kefeng (Qualcomm), I am ok with r01.
George (Ericsson) provides response
Rainer (Nokia) provides r02.
James Jin (vivo) replies to Rainer (Nokia), Ok with r02
==== Revisions Deadline ====
George (Ericsson) OK with rev 02
==== Final Deadline ====
Revised
9.17.1 S2-2209613 P-CR Approval 23.700-87: KI#1, Update solution #20 to merge with existing solution #18. Vivo Rel-18 Revision of S2-2208506r02. Approved Approved
9.17.1 S2-2208182 P-CR Approval 23.700-87: KI#1, 4: Update to solution 5. Ericsson Rel-18 r02 agreed. Revised to S2-2209614. Yi (China Mobile) provides r01.
George Foti (Ericsson) provides r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.17.1 S2-2209614 P-CR Approval 23.700-87: KI#1, 4: Update to solution 5. Ericsson Rel-18 Revision of S2-2208182r02. Approved Approved
9.17.1 S2-2208496 P-CR Approval 23.700-87: KI #1, update Sol #22. Qualcomm Incorporated, vivo Rel-18 Approved Kefeng Zhang (Qualcomm) replies Hao (ZTE) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.17.1 S2-2208498 P-CR Approval 23.700-87: KI #1, new solution: UE capabilities detection for IMS DC applications. Qualcomm Incorporated, vivo Rel-18 Revision of (Noted) S2-2206002 from S2#152E. r02 agreed. Revised to S2-2209615. Kefeng Zhang (Qualcomm) replies Hao (ZTE) comments and provides r01.
Hao (ZTE) responds.
Kefeng Zhang (Qualcomm) replies Hao (ZTE) comments.
Kefeng Zhang (Qualcomm) clarified this is a re-submission of S2-2206002r01 in SA2 #152e, which was not correctly concluded in Chairman's note.
George Foti (Ericsson) proposes to note the CR.
Rainer (Nokia) agrees to note the CR.
Kefeng (Qualcomm) replies Rainer (Nokia) comments.
Rainer (Nokia) replies.
Kefeng (Qualcomm) replies Rainer (Nokia) .
George (Ericsson) provides response. This is more suitable for a GSM spec. Does not belong to 3GPP stage 2 specs.
Kefeng (Qualcomm) replies George (Ericsson) .
George (Ericsson) provides response, I am not necessarily against it. But U have broken the rules and others can complain
Kefeng (Qualcomm) provides r02.
Rainer (Nokia) is ok with r02.
==== Revisions Deadline ====
George (Ericsson) Ok with r02
==== Final Deadline ====
Revised
9.17.1 S2-2209615 P-CR Approval 23.700-87: KI #1, new solution: UE capabilities detection for IMS DC applications. Qualcomm Incorporated, vivo Rel-18 Revision of S2-2208498r02. Approved Approved
9.17.1 S2-2208601 P-CR Approval 23.700-87: KI #1, Sol #6, Update Procedures. ZTE Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.17.1 S2-2208602 P-CR Approval 23.700-87: KI #1, Sol #17, Update to Resolve ENs. ZTE Rel-18 r02 agreed. Revised to S2-2209616. George Foti (Ericsson) provides comments
Kefeng (Qualcomm) provides comments
Hao (ZTE) responds and provides r01.
George (Ericsson) provides response
George (Ericsson) provides response. I prefer we simply add a note that the profile will align with solution 20, and we leave it there.
Hao (ZTE) responds to George (Ericsson) and provides r02.
==== Revisions Deadline ====
George (Ericsson) OK with r02
Rainer (Nokia) is ok with r02.
==== Final Deadline ====
Revised
9.17.1 S2-2209616 P-CR Approval 23.700-87: KI #1, Sol #17, Update to Resolve ENs. ZTE Rel-18 Revision of S2-2208602r02. Approved Approved
9.17.1 S2-2208495 LS OUT Approval [DRAFT] LS on the usage of DC application identifier in SDP Qualcomm Rel-18 r00 agreed. Revised to S2-2209617 ==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.17.1 S2-2209617 LS OUT Approval LS on the usage of DC application identifier in SDP SA WG2 Rel-18 Revision of S2-2208495r00. Approved Approved
9.17.1 - - - KI#2: Solution updates - - Docs:=1 -
9.17.1 S2-2208608 P-CR Approval 23.700-87: KI#2, Sol#9 Update Supporting AR Communication. Huawei, HiSilicon Rel-18 Noted Mu (Huawei) replies
George Foti (Ericsson) provides comments
George (Ericsson) provides response
Mu (Huawei) replies and provide r01.
George (Ericsson) provides comments. Not Ok with this revision.
Mu (Huawei) replies and provide r02.
George (Ericsson) provides comments on r02.
==== Revisions Deadline ====
George (Ericsson) NOT OK with any revisions including the original
==== Final Deadline ====
Noted
9.17.1 - - - Evaluations and conclusions - - Docs:=10 -
9.17.1 S2-2208497 P-CR Approval 23.700-87: KI #1, update evaluation and conclusion on DC application ID . Qualcomm Incorporated, vivo Rel-18 r02 agreed. Revised to S2-2209618. George Foti (Ericsson) proposes to note the pCR. We send an LS on this issue. We should wait for their response
George Foti (Ericsson) proposes to note the CR. We sent an LS to SA4 and we should wait for their answer.
Rainer (Nokia) comments.
Kefeng (Qualcomm) replies George Foti (Ericsson) & Rainer (Nokia) comments.
Kefeng (Qualcomm) provides r01.
Rainer (Nokia) provides r02.
Kefeng (Qualcomm) is OK with r02.
==== Revisions Deadline ====
George (Ericsson) Ericsson Ok with rev. 02
==== Final Deadline ====
Revised
9.17.1 S2-2209618 P-CR Approval 23.700-87: KI #1, update evaluation and conclusion on DC application ID . Qualcomm Incorporated, vivo Rel-18 Revision of S2-2208497r02. Approved Approved
9.17.1 S2-2208603 P-CR Approval 23.700-87: KI #1, Evaluation Update. ZTE Rel-18 r01 agreed. Revised to S2-2209619. Kefeng Zhang (Qualcomm) proposes to merge evaluation of Sol #22 into S2-2208497 and provides r01.
==== Revisions Deadline ====
Hao (ZTE) is fine with r01.
Rainer (Nokia) is ok with r01.
==== Final Deadline ====
Revised
9.17.1 S2-2209619 P-CR Approval 23.700-87: KI #1, Evaluation Update. ZTE Rel-18 Revision of S2-2208603r01. Approved Approved
9.17.1 S2-2209042 P-CR Approval 23.700-87: Update on conclusion of KI#1. China Mobile, Huawei, Hisilicon, ZTE Rel-18 r04 agreed. Revised to S2-2209620. Mu (Huawei) comments
George Foti (Ericsson) provides comments
Rainer (Nokia) comments.
George (Ericsson) provides response
Mu (Huawei) replies to George
Yi (China Mobile) replies to George and Rainer. R01 is provided.
Rainer (Nokia) provides r02.
George (Ericsson) provides r03
George (Ericsson) provides r04. Responses
Mu (Huawei) replies to Rainer
Rainer (Nokia) replies to Mu (Huawei).
Yi (China Mobile) comments.
George (Ericsson) provides responds
==== Revisions Deadline ====
Yi (China Mobile) responds to George and can live with r04.
Rainer (Nokia) is ok with r04.
==== Final Deadline ====
Revised
9.17.1 S2-2209620 P-CR Approval 23.700-87: Update on conclusion of KI#1. China Mobile, Huawei, Hisilicon, ZTE Rel-18 Revision of S2-2209042r04. Approved Approved
9.17.1 S2-2208441 P-CR Approval 23.700-87: KI#3: Conclusions for support of Third Party specific user IDs. Nokia, Nokia Shanghai Bell, Samsung Rel-18 r01 agreed. Revised to S2-2209621. George Foti (Ericsson) provides comments
Rainer (Nokia) provides r01.
Mu (Huawei) comments
Rainer (Nokia) replies.
Mu (Huawei) provides r02, adding CRS as alternative.
Rainer (Nokia) cannot accept r02.
Mu (Huawei) replies to Rainer
==== Revisions Deadline ====
George (Ericsson) OK with rev. 01
Kefeng (Qualcomm) OK with r01.
Ashok (Samsung) OK with r01.
==== Final Deadline ====
Revised
9.17.1 S2-2209621 P-CR Approval 23.700-87: KI#3: Conclusions for support of Third Party specific user IDs. Nokia, Nokia Shanghai Bell, Samsung Rel-18 Revision of S2-2208441r01. Approved Approved
9.17.1 S2-2209043 P-CR Approval 23.700-87: Evaluation and conclusion of KI#4. China Mobile Rel-18 r01 agreed. Revised to S2-2209622. Hao (ZTE) comments.
George Foti (Ericsson) provides comments
Yi (China Mobile) replies to George.
George (Ericsson) provides response
Rainer (Nokia) provides r01.
Yi (China Mobile) comments.
==== Revisions Deadline ====
Yi (China Mobile) are fine with r00 and r01.
Rainer (Nokia) is only ok with r01.
==== Final Deadline ====
Revised
9.17.1 S2-2209622 P-CR Approval 23.700-87: Evaluation and conclusion of KI#4. China Mobile Rel-18 Revision of S2-2209043r01. Approved Approved
9.17.2 - - - Evolution of IMS multimedia telephony service (NG_RTC) - - Docs:=0 -
9.18 - - - Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) - - Docs:=69 -
9.18 - - - Resource efficiency for MBS reception in RAN sharing scenario (LSs) - - Docs:=13 -
9.18 S2-2208147 LS In Information LS from RAN WG3: LS on the scope of resource efficiency for MBS reception in RAN sharing scenario RAN WG3 (R3-225229) Rel-18 Responses drafted in S2-2208341, S2-2208730. Postponed Postponed
9.18 S2-2208150 LS In Action LS from TSG RAN: Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario TSG RAN (RP-222678) Rel-18 Responses drafted in S2-2208285, S2-2208341, S2-2208851, S2-2208966. Final response in S2-2209306. Postponed Postponed
9.18 S2-2208851 LS OUT Approval [DRAFT] Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario CATT Rel-18 Response to S2-2208150. r01 agreed. Revised to S2-2209306, merging S2-2208285, S2-2208341, S2-2208713, S2-2208730, S2-2208869 and S2-2208966. Noted zhendong (ZTE) agree with thomas
LaeYoung (LGE) is OK to handle/cover broadcast only for KI#2 (i.e. RAN sharing scenario) in Rel-18.
Thomas (Nokia) provides r01
Youngkyo(Samsung) agrees that it is too late to extend the scope of our study.
Haris(Qualcomm) r01 is aligned with our view
LiMeng (Huawei) prefers to not check this issue in the study phase, but considers the possibility in normative work.
zhendong (ZTE) provides the response
Youngkyo(Samsung) questions TU budget change for normative phase.
LiMeng (Huawei) responds to Youngkyo (Samsung) and Zhendong (ZTE)
Shabnam (Ericsson) provides comments as indicated in our input paper (8340), we can take some TU time if companies agree otherwise as we have done for many WIs that are RAN led (e.g. eDRX, REDCap, NR_Slice, IoT_SAT_ARCH_EPS... to name a few), we will then use the alignment TU budget SA2 reserves for such purposes.
Shabnam (Ericsson) provides r02 according to comments below.
Haris(Qualcomm) indicates why r02 is not acceptable
Thomas (Nokia) does not agree to do normative work on MOCN MBS multicast session sharing without prior SA2 study or as RAN3 alignment, as fundamental technical issues need to be studied before by SA2.
Thomas(Nokia) objects against r02
Youngkyo(Samsung) share the view with Thomas(Nokia) and Haris(Qulacomm) as r02 is not acceptable.
Shabnam (Ericsson) comments it is quite premature for SA2 to assume RAN is not capable without seeing their outcome and we should follow normal procedure and let RAN work on this and let us know what they have achieved, objects to original and all revisions except r02.
==== Revisions Deadline ====
LaeYoung (LGE) suggests to check r01 to move forward.
Tao(VC) Let's further check r01 agreeable or not
Haris(Qualcomm) is ok with r01 and supports approving the LS response at this meeting
Zhendong (ZTE) proposes to move with r01
==== Final Deadline ====
Shabnam (Ericsson) provides comments that Ericsson did not withdraw their objection to r01, we can only accept r02 and object to all other revisions as stated already.
Noted
9.18 S2-2209306 LS OUT Approval [DRAFT] Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario CATT Rel-18 Revision of S2-2208851r01, merging S2-2208285, S2-2208341, S2-2208713, S2-2208730, S2-2208869 and S2-2208966. WITHDRAWN Withdrawn
9.18 S2-2208713 LS OUT Approval [DRAFT] Reply LS on Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario SAMSUNG Rel-18 Response to S2-2208150. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
Youngkyo(Samsung) is okay to merge it.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208341 LS OUT Approval [DRAFT] Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario Ericsson Rel-18 Response to S2-2208147 and S2-2208150. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208730 LS OUT Approval [DRAFT] Reply LS on MOCN multicast Huawei, HiSilicon Rel-18 Response to S2-2208147. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208869 LS OUT Approval [DRAFT] Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario Qualcomm Rel-18 Response to S2-2208147 and S2-2208150. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208966 LS OUT Approval [DRAFT] Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario ZTE Rel-18 Response to S2-2208150. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208285 LS OUT Approval [DRAFT] Reply LS on on the scope of resource efficiency for MBS reception in RAN sharing scenario Nokia, Nokia Shanghai-Bell Rel-18 Response to S2-2208150. Merged into S2-2209306 LiMeng (Huawei) suggests to merge this document into S2-2208851.
Thomas (Nokia) agrees to merge this document into S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208286 DISCUSSION Discussion Scope of resource efficiency for MBS reception in RAN sharing scenario. Nokia, Nokia Shanghai-Bell Rel-18 Noted zhendong (ZTE) proposes to Note this DP, and discusses this in 8851 thread.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.18 S2-2208340 DISCUSSION Decision Discussion & Way Forward on Resource Efficiency for Multicast MBS reception of RAN Sharing Ericsson, FirstNet Rel-18 Noted zhendong (ZTE) proposes to Note this DP, and discusses this in 8851 thread.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.18 S2-2208731 DISCUSSION Discussion Discussion on MOCN Multicast issue. Huawei, HiSilicon Rel-18 Noted zhendong (ZTE) proposes to Note this DP, and discusses this in 8851 thread.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.18 - - - Resource efficiency for MBS reception in RAN sharing scenario (CR) - - Docs:=1 -
9.18 S2-2208965 P-CR Approval 23.700-47: KI2#, discussion and proposal for the LS on the MOCN scope. ZTE Rel-18 Noted Robbie (Ericsson) comments it needs to be decided together with the reply LS S2-2208851.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.18 - - - Other LSs - - Docs:=3 -
9.18 S2-2208879 LS OUT Approval [DRAFT] Reply LS on UE capabilities for MBS Qualcomm Rel-18 Response to S2-2205431 (noted at S2#152E). Noted LiMeng (Huawei) comments.
Haris(Qualcomm) responds
Judy (Ericsson) comment
LaeYoung (LGE) comments.
Haris(Qualcomm) provides r01
Thomas(Nokia) provides comments
Wanqiang(Huawei) provides comments and proposes to note the paper.
Haris(Qualcomm) responds to Wanqiang (Huawei)
Wanqiang(Huawei) responds to Haris (Qualcomm)
==== Revisions Deadline ====
Haris(Qualcomm) asks to approve r01
Tao(VC) further check whether r01 agreeable or not
Wanqiang(Huawei) objects the LS as RAN1 already gave the feedback.
==== Final Deadline ====
Noted
9.18 S2-2210160 LS OUT Approval [DRAFT] LS on re-establishment of the MBS context during mobility registration update or service request procedure CATT CC#4: r07 agreed. Revised to S2-2209965. Revised
9.18 S2-2209965 LS OUT Approval LS on re-establishment of the MBS context during mobility registration update or service request procedure SA WG2 - Revision of S2-2210160r07. Approved Approved
9.18 - - - KI#1: Solution update - - Docs:=10 -
9.18 S2-2208288 P-CR Approval 23.700-47: KI#1 and KI#6, Sol#26 Update to address ENs. Nokia, Nokia Shanghai-Bell Rel-18 r04 agreed. Revised to S2-2209307. Thomas (Nokia) provides r01
Fenqin (Huawei) provides comments
Judy (Ericsson) asks question
Thomas (Nokia) replies to Fenqin and provides r02
Fenqin (Huawei) provides r03
Xiaoyan (CATT) provides r04
==== Revisions Deadline ====
Xiaoyan (CATT) only accepts r04 and objects to other revisions (including r00).
Thomas (Nokia) replies to Xiaoyoan
Ask her to reconsider objection
==== Final Deadline ====
Revised
9.18 S2-2209307 P-CR Approval 23.700-47: KI#1 and KI#6, Sol#26 Update to address ENs. Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2208288r04. Approved Approved
9.18 S2-2208332 P-CR Approval 23.700-47: KI#1, Sol#18: update to resolve ENs. Ericsson Rel-18 r03 agreed. Revised to S2-2209308. Fenqin (Huawei) provide comments and provide r01
Haris(Qualcomm) comments that removing the EN 'It is FFS whether there is a need for the UE to become aware the group paging is the CN initiated paging, and if yes how.' is not acceptable without feedback from RAN2
Judy (Ericsson) responds and provide r02
Thomas (Nokia) provides r03
==== Revisions Deadline ====
Judy (Ericsson) is fine with r03
==== Final Deadline ====
Revised
9.18 S2-2209308 P-CR Approval 23.700-47: KI#1, Sol#18: update to resolve ENs. Ericsson Rel-18 Revision of S2-2208332r03. Approved Approved
9.18 S2-2208333 P-CR Approval 23.700-47: KI#1, Sol#27: update to resolve ENs. Ericsson Rel-18 r06 agreed. Revised to S2-2209309. Fenqin (Huawei) provide comments and r01
Aihua(CMCC) provide comments.
Judy (Ericsson) responds to Aihua (CMCC)
Thomas (Nokia) provide r02
Judy (Ericsson) provides r03
Thomas(Nokia) raises concerns against r03
Provides r04
Judy (Ericsson) responds to Thomas(Nokia), and provide r05
Thomas(Nokia) and provides r06
Judy (Ericsson) responds to Aihua(CMCC)
==== Revisions Deadline ====
Aihua(CMCC) disagrees with the EN removal, suggesting to keep EN as it was.
Judy (Ericsson): Aihua(CMCC) please explain what is your real concern if an SMF gets UE's GPSI as part of the MBS Session context but the UE may not have joined or may have joined in different SMF. It does not help if you ignore the analysis and repeat the same comment.
==== Final Deadline ====
Revised
9.18 S2-2209309 P-CR Approval 23.700-47: KI#1, Sol#27: update to resolve ENs. Ericsson Rel-18 Revision of S2-2208333r06. Approved Approved
9.18 S2-2208852 P-CR Approval 23.700-47: KI#1 Sol#20 update: resolving Editor's notes. CATT Rel-18 Noted Thomas (Nokia) provides r01
==== Revisions Deadline ====
Xiaoyan (CATT) objects to r01
Thomas (Nokia) objects to r00
==== Final Deadline ====
Noted
9.18 S2-2208963 P-CR Approval 23.700-47: KI#1, update the solution 6. ZTE Rel-18 r02 agreed. Revised to S2-2209310. Judy (Ericsson) comment
zhendong (ZTE) provides the response
Thomas(Nokia) comments that some justification for EN removal should be provided
zhendong (ZTE) provides r01
Fenqin(Huawei) comments
zhendong (ZTE) provides r02
==== Revisions Deadline ====
Fenqin(Huawei) is fine with r02
==== Final Deadline ====
Revised
9.18 S2-2209310 P-CR Approval 23.700-47: KI#1, update the solution 6. ZTE Rel-18 Revision of S2-2208963r02. Approved Approved
9.18 S2-2208964 P-CR Approval 23.700-47: KI#1, update the solution 28. ZTE Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.18 - - - KI#1: Evaluation and conclusion - - Docs:=8 -
9.18 S2-2208473 P-CR Approval 23.700-47: Evaluation for key issue 1 . Nokia, Nokia Shanghai Bell, Rel-18 r06 agreed. Revised to S2-2209311. Fenqin (Huawei) provides comment and r01.
Thomas (Nokia) provides r02.
zhendong (ZTE) provides r03
Judy (Ericsson) provides r04
Xiaoyan (CATT) provides r05
Fenqin (Huawei) provides r06
==== Revisions Deadline ====
Haris(Qualcomm) is ok with r06, indicates that contains typo 'to enable inavtive MBS reception' that needs to be corrected in final version
==== Final Deadline ====
Revised
9.18 S2-2209311 P-CR Approval 23.700-47: Evaluation for key issue 1 . Nokia, Nokia Shanghai Bell, Ericsson, Huawei Rel-18 Revision of S2-2208473r06. Approved Approved
9.18 S2-2208904 P-CR Approval 23.700-47: KI#1: Further evaluation and conclusion update. Huawei, HiSilicon Rel-18 r10 agreed. Revised to S2-2209312, merging S2-2208334, S2-2208472, S2-2208853 and S2-2208962 Fenqin (Huawei) provides r01
Haris(Qualcomm) provides r02
Fenqin (Huawei) provides feedback and r03
Haris(Qualcomm) responds that r03 is not acceptable
Fenqin (Huawei) responds to Haris
Xiaoyan (CATT) provides r04
zhendong (ZTE) provides r05
Fenqin (Huawei) provides r06
Haris(Qualcomm) comments on r04's changes on how to re-establish the MBS context from CM-IDLE
Haris(Qualcomm) responds that r06 is not acceptable
Judy (Ericsson) provides r07 to allow further discussion which solution to adopt for SMF to get UE priority info if the requirement is confirmed by NG-RAN.
Thomas (Nokia) provides r08
Xiaoyan(CATT) replies to Haris(Qualcomm)
Xiaoyan (CATT) provides r09
Haris(Qualcomm) provides r10
==== Revisions Deadline ====
Judy (Ericsson) objects to r01, r03~r06, cannot accept r09/r10 as is, request to remove 'service request'
Haris(Qualcomm) can only accept r02 and r10. Objects to other revisions.
Thomas (Nokia) can agree r10 + remove 'service request'
Fenqin (Huawei) Provides r11==r10+ removing the 'service request' from the indicated paragraph
Xiaoyan (CATT) objects to r11 (i.e. r10 + remove 'service request') and also requests to add a NOTE in r10.
Fenqin (Huawei) suggest to go with r10
Judy (Ericsson) thanks to Xiaoyan's info and can live with r10.
Thomas(Nokia) can live with r10.
zhendong (ZTE) is fine with r10
==== Final Deadline ====
Revised
9.18 S2-2209312 P-CR Approval 23.700-47: KI#1: Further evaluation and conclusion update. Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, CATT, Ericsson Rel-18 Revision of S2-2208904r10, merging S2-2208334, S2-2208472, S2-2208853 and S2-2208962. Approved Approved
9.18 S2-2208334 P-CR Approval 23.700-47: KI#1, Update to Evaluation and Interim Conclusion . Ericsson Rel-18 Merged into S2-2209312 Judy (Ericsson) is OK with the rapporteur's merging proposal.
LiMeng (Huawei) suggests to merge this document into S2-2208904.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208472 P-CR Approval 23.700-47: KI#1, Interim conclusion updates . Nokia, Nokia Shanghai-Bell, Rel-18 Merged into S2-2209312 LiMeng (Huawei) suggests to merge this document into S2-2208904.
Thomas (Nokia) accepts to merge this document into S2-2208904.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208853 P-CR Approval 23.700-47: KI#1 conclusions update. CATT Rel-18 Merged into S2-2209312 LiMeng (Huawei) suggests to merge this document into S2-2208904.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208962 P-CR Approval 23.700-47: KI#1, update the conclusion of Key issue#1. ZTE Rel-18 Merged into S2-2209312 LiMeng (Huawei) suggests to merge this document into S2-2208904.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 - - - KI#2 - - Docs:=7 -
9.18 S2-2208335 P-CR Approval 23.700-47: KI#2, Sol#7: update to MOCN RAN Sharing for TMGI Option. Ericsson Rel-18 r01 agreed. Revised to S2-2209313. LaeYoung (LGE) comments that Robbie (Ericsson) and LaeYoung (LGE) exchanged several emails such as questions from herself and answers from Robbie (Ericsson), but used wrong end tag (i.e. >).
Robbie (Ericsson) provides r01 based on the comments from LaeYoung (LGE).
LaeYoung (LGE) is fine with the text updates in r01 and provides comment.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.18 S2-2209313 P-CR Approval 23.700-47: KI#2, Sol#7: update to MOCN RAN Sharing for TMGI Option. Ericsson Rel-18 Revision of S2-2208335r01. Approved Approved
9.18 S2-2208395 P-CR Approval 23.700-47: KI#2, Evaluation Update. Ericsson, Huawei, HiSilicon Rel-18 r09 agreed. Revised to S2-2209314. Haris(Qualcomm) comments
Robbie (Ericsson) replies to Haris(Qualcomm), provides r01
Haris(Qualcomm) asks question for clarification
LaeYoung (LGE) comments.
Robbie (Ericsson) provides r02 and replies to LaeYoung(LGE)
LaeYoung (LGE) replies to Robbie (Ericsson).
Robbie (Ericsson) provides r03 and replies to LaeYoung (LGE).
Thomas (Nokia) provides r04.
LaeYoung (LGE) provides r05.
Robbie (Ericsson) provides r06.
LiMeng (Huawei) provides r07 based on r05 but can accept r06.
Thomas (Nokia) provides r08
Robbie (Ericsson) provides r09
Haris(Qualcomm) comments on r07
Robbie (Ericsson) asks clarification on the comments from Haris(Qualcomm)
Haris(Qualcomm) responds
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r09.
==== Final Deadline ====
Revised
9.18 S2-2209314 P-CR Approval 23.700-47: KI#2, Evaluation Update. Ericsson, Huawei, HiSilicon, LG Electronics, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2208395r09. Approved Approved
9.18 S2-2208732 P-CR Approval 23.700-47: Conclusion update on KI #2(MOCN network sharing). Samsung Rel-18 Noted Robbie (Ericsson) asks for clarification
Youngkyo(Samsung) replies.
Robbie (Ericsson) asks for clarification again.
LiMeng (Huawei) asks for clarification.
LaeYoung (LGE) does not prefer to update KI#2 conclusion in this meeting without feedback from RAN2 and RAN3.
Youngkyo(Samsung) replies to LaeYoung and provides r01.
Robbie (Ericsson) provides comments.
zhendong (ZTE) comments
Robbie (Ericsson) replies to zhendong (ZTE)
Thomas (Nokia) provides r02
Robbie (Ericsson) objects to r02, provides r03.
LiMeng (Huawei) agrees with Robbie that it is not possible to conclude to use common TMGI as the identifier.
LaeYoung (LGE) proposes to NOTE this pCR because it is considered not much meaningful to update KI#2 conclusion in this meeting w/o RAN2/3.
Thomas (Nokia) provides r04 and objects to r03
asks Robbie to explain his objection to r02
Robbie (Ericsson) explains the reasons to Thomas (Nokia)
Thomas (Nokia) provides r05 and replies to Robbie
Robbie (Ericsson) thanks Thomas (Nokia) and provides comments
zhendong (ZTE) provides the r06
Thomas (Nokia) provides r06 based on the proposal of Robbie
Thomas Nokia provides r07
Clarifies that r06 was in fact provided by zhendong (ZTE)
Haris(Qualcomm) asks question
Haris(Qualcomm) provides r08
LaeYoung (LGE) cannot accept all versions.
LiMeng (Huawei) comments on the last bullet .
==== Revisions Deadline ====
Thomas(Nokia) replies to LaeYoung
LaeYoung (LGE) responds to Thomas (Nokia).
Thomas (Nokia) responds to LaeYoung (LGE)
LaeYoung (LGE) replies to Thomas (Nokia).
==== Final Deadline ====
Noted
9.18 S2-2208725 P-CR Approval 23.700-47: KI#2: Update the conclusions. Huawei, HiSilicon, Ericsson Rel-18 Merged into (Covered by) S2-2208732 LiMeng (Huawei) suggests to merge this document into S2-2208732.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.18 S2-2208844 P-CR Approval 23.700-47: Conclusions for KI#2. Qualcomm Incorporated Rel-18 Noted LiMeng (Huawei) comments.
==== Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this pCR or mark as MERGED into 8732.
Haris(Qualcomm) agrees with LaeYoung. It should be marked noted or merged
==== Final Deadline ====
Noted
9.18 - - - KI#3 - - Docs:=7 -
9.18 S2-2208287 P-CR Approval 23.700-47: KI#3, Sol#30 Update to address ENs. Nokia, Nokia Shanghai-Bell Rel-18 r02 agreed. Revised to S2-2209315. Judy (Ericsson) comments
Thomas (Nokia ) replies to Judy
Fenqin (Huawei) comments
Thomas(Nokia) replies to Fenqin
Fenqin (Huawei) replies to Thomas
Thomas (Nokia) replies to Judy
Thomas(Nokia) provides r01 and replies to Fenqin (Huawei)
Fenqin (Huawei) further replies to Thomas
Xiaoyan (CATT) provides r03
==== Revisions Deadline ====
Thomas (Nokia) comments that r03 disregards the previous revisions and suggest using r02 instead.
Judy (Ericsson) can accept r02/r03, object to r00/r01 which removes EN withotu resolution
Xiaoyan (CATT) prefers r03, can live with r02, and objects to r00/r01
Thomas (Nokia) still prefers r02.
==== Final Deadline ====
Revised
9.18 S2-2209315 P-CR Approval 23.700-47: KI#3, Sol#30 Update to address ENs. Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2208287r02. Approved Approved
9.18 S2-2208657 P-CR Approval 23.700-47: FS_5MBS_Ph2 KI#3, Sol#11 Update for making clarification. China Mobile, CATT, vivo Rel-18 r01 agreed. Revised to S2-2209316. Aihua (CMCC) provides r01.
Judy (Ericsson) asks question
Aihua (CMCC) replies.
==== Revisions Deadline ====
Judy (Ericsson) comment
==== Final Deadline ====
Revised
9.18 S2-2209316 P-CR Approval 23.700-47: FS_5MBS_Ph2 KI#3, Sol#11 Update for making clarification. China Mobile, CATT, vivo Rel-18 Revision of S2-2208657r01. Approved Approved
9.18 S2-2208660 P-CR Approval 23.700-47: KI#3 Update to evaluation and conclusion. China Mobile Rel-18 Postponed Aihua (CMCC) provides r01
Judy (Ericsson) provides r02
Thomas(Nokia) provides r03 and raises concerns against r02
Aihua (CMCC) replies and provides r03.
Thomas(Nokia) provides r04
Clarifies that r03 was provided by Aihua (CMCC)
and raises concerns against r02 and r03
Aihua (CMCC) objects r04 and provides r05.
Xiaoyan (CATT) provides r06.
==== Revisions Deadline ====
Thomas (Nokia) objects against r02, r03 and r06.
Haris(Qualcomm) proposes to postpone conclusions
Judy (Ericsson) accepts only r02 and objects to other revisions (r00 included).
Thomas (Nokia) objects against r02 and r03
==== Final Deadline ====
Postponed
9.18 S2-2209190 P-CR Approval 23.700-47: KI#3 evaluation updates . Nokia, Nokia Shanghai Bell, Rel-18 r02 agreed. Revised to S2-2209317. Judy (Ericsson) provides r01
Thomas (Nokia) provides r02, raises concerns against r01
==== Revisions Deadline ====
Judy (Ericsson) prefers r01, can live with r02 and objects to r00
Thomas (Nokia) objects against r01
==== Final Deadline ====
Revised
9.18 S2-2209317 P-CR Approval 23.700-47: KI#3 evaluation updates . Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2209190r02. Approved Approved
9.18 - - - KI#4 - - Docs:=2 -
9.18 S2-2208724 P-CR Approval 23.700-47: KI#4, Sol#13: Update and clarification. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.18 S2-2208337 P-CR Approval 23.700-47: KI#4, Evaluation and Conclusion Update. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.18 - - - KI#5 - - Docs:=3 -
9.18 S2-2208868 P-CR Approval 23.700-47: Conclusions for KI#5. Qualcomm Incorporated Rel-18 Noted LiMeng (Huawei) asks questions regarding the deferred activation.
Thomas (Nokia) provides r01
Haris(Qualcomm) comments
Thomas(Nokia) replies to Haris
Judy (Ericsson) comments and provides r02 based on r00, only change is to add Ericsson as co-source
Haris(Qualcomm) responds to Thomas (Nokia)
Thomas(Nokia) replies to LiMeng
Thomas(Nokia) objects against r00 and r02.
Provides r03
replies to Judy and Harris.
==== Revisions Deadline ====
Haris(Qualcomm) can only accept r0 and r02. Objects to other revisions
Judy (Ericsson) accept r00 and r02, objects to other revisions
==== Final Deadline ====
Noted
9.18 S2-2208726 P-CR Approval 23.700-47: KI#5: Evaluation and Conclusion on broadcast MBS session. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209318. LiMeng (Huawei) provides r01
Judy (Ericsson) provides r02
Thomas (Nokia) provides r03
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.18 S2-2209318 P-CR Approval 23.700-47: KI#5: Update to Evaluation on MBS session. Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2208726r03. Approved Approved
9.18 - - - KI#6 - - Docs:=6 -
9.18 S2-2208727 P-CR Approval 23.700-47: KI#6, Sol#31: Update and clarification. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209319. Robbie (Ericsson) provides comments
Thomas (Nokia) provides r01
Robbie (Ericsson) provides r02
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.18 S2-2209319 P-CR Approval 23.700-47: KI#6, Sol#31: Update and clarification. Huawei, HiSilicon Rel-18 Revision of S2-2208727r02. Approved Approved
9.18 S2-2208339 P-CR Approval 23.700-47: KI#6, Evaluation Update and Conclusion. Ericsson Rel-18 CC#3: Postponed to CC#4. CC#4: r09 agreed. Revised to S2-2209980. Robbie (Ericsson) provides r01.
Haris(Qualcomm) provides r02
Fenqin (Huawei) provides comment.
Haris(Qualcomm) responds
Xiaoyan (CATT) provides r03
Robbie (Ericsson) supports Fenqin(Huawei) and raise concerns against r02, r03
Haris(Qualcomm) responds to Robbie (Ericsson)
Thomas (Nokia) provides r04 and supports the concerns against r02, r03
Robbie (Ericsson) replies to Haris(Qualcomm)
Haris(Qualcomm) comments that without explicit acknowledgment from SA2 that this scenario is possible SA6 cannot do the job
Robbie(Ericsson) comments that SA6 can utilize both MBS broadcast and MBS multicast without further standardization in SA2
Fenqin (Huawei) share the same view as Robbie
Haris(Qualcomm) provides r05
Fenqin (Huawei) provides r06
Robbie (Ericsson) provides r07
Haris(Qualcomm) indicates that neither r06 or r07 are acceptable
Robbie (Ericsson) provides r08
==== Revisions Deadline ====
Thomas (Nokia) objects against r07 and r08
Robbie (Ericsson) asks Thomas (Nokia) to explain why the evaluation of not relevant KIs need to be recorded in this KI
Tao(VC) further check whether r05 agreeable or not
Robbie(Ericsson) asks Thomas (Nokia) to withdraw his objection on r08
Fenqin (Huawei) is ok with r05 or r08. The NOTE should not impact the KI#6 conclusion.
Thomas(Nokia) can agree r04 and r06. Object to other revisions.
suggest agreeing r06 + remove 'simultaneously '
Haris(Qualcomm) is ok with r08 or r05. Objects to other revisions.
Robbie (Ericsson) accepts r08, r07, r01 and objects to other revisions.
LiMeng (Huawei) asks if the following can be acceptable.
Robbie (Ericsson) agrees with the suggestion from LiMeng (Huawei).
Thomas(Nokia) has concerns with the proposals of LiMeng
LiMeng (Huawei) proposes the way forward.
==== Final Deadline ====
Haris(Qualcomm) is ok with the WF proposal from LiMeng
Robbie(Ericsson) is ok with the WF proposal from LiMeng
Revised
9.18 S2-2209980 P-CR Approval 23.700-47: KI#6, Evaluation Update and Conclusion. Ericsson, Nokia, Nokia Shanghai-Bell Rel-18 Revision of S2-2208339r09. Approved Approved
9.18 S2-2208854 P-CR Approval 23.700-47: KI#6 evaluation update. CATT Rel-18 r04 agreed. Revised to S2-2209320. Robbie (Ericsson) asks for clarification
Xiaoyan (CATT) clarifies to Robbie (Ericsson)
Robbie (Ericsson) replies to Xiaoyan (CATT)
Robbie (Ericsson) asks for further clarification.
Robbie (Ericsson) provides r01.
Xiaoyan (CATT) provides r02.
Xiaoyan (CATT) provides further clarifications to Robbie (Ericsson)
Robbie (Ericsson) provides comments.
Robbie (Ericsson) provides r03.
Xiaoyan (CATT) provides r04
==== Revisions Deadline ====
Robbie (Ericsson) is fine with r04.
==== Final Deadline ====
Revised
9.18 S2-2209320 P-CR Approval 23.700-47: KI#6 evaluation update. CATT, Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2208854r04. Approved Approved
9.18 - - - Documents exceeding TU Budget - - Docs:=9 -
9.18 S2-2208961 P-CR Approval 23.700-47: KI#1, update the evaluation of Key issue#1. ZTE Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208474 P-CR Approval 23.700-47: KI#2, Interim conclusion updates. Nokia, Nokia Shanghai Bell Rel-18 Not Handled LaeYoung (LGE) proposes to MERGE this pCR to 8732.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208967 P-CR Approval 23.700-47: KI#2, update the evaluation and conclusion for the Key issue#2. ZTE Rel-18 Not Handled LaeYoung (LGE) proposes to MERGE this pCR to 8395 for evaluation and to 8732 for conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208336 P-CR Approval 23.700-47: KI#3, Evaluation update . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208338 P-CR Approval 23.700-47: KI#5, Evaluation update and Conclusion . Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208475 P-CR Approval 23.700-47: KI#5, conclusions. Nokia, Nokia Shanghai Bell Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208728 P-CR Approval 23.700-47: KI#6: Evaluation and conclusion. Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208855 P-CR Approval 23.700-47: KI#6 conclusions. CATT Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.18 S2-2208867 P-CR Approval 23.700-47: Conclusions for KI#6. Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 - - - Study on XR (Extended Reality) and media services (FS_XRM) - - Docs:=96 -
9.19 - - - LS & TR clean up - - Docs:=16 -
9.19 S2-2208143 LS In Information LS from RAN WG2: LS on Pose Information for XR RAN WG2 (R2-2209213) Rel-18 Noted Noted
9.19 S2-2208144 LS In Action LS from RAN WG2: LS on XR-awareness in RAN RAN WG2 (R2-2209215) Rel-18 Responses drafted in S2-2209107, S2-2209157. Final response in S2-2209979 Replied to
9.19 S2-2208157 LS In Action LS from SA WG4: Reply LS to Follow-up LS on QoS support with Media Unit granularity SA WG4 (S4-221174) Rel-18 This was Postponed Postponed
9.19 S2-2208105 LS In Action LS from RAN WG1: Reply LS on UE Power Saving for XR and Media Services RAN WG1 (R1-2205531) Rel-18 Revision of Postponed S2-2205421 from S2#152-e. Responses drafted in S2-2208197, S2-2208392. Final response in S2-2209979 Replied to
9.19 S2-2209257 LS In Action LS from SA WG4: Reply LS on further details on XR traffic SA WG4 (S4aV220921) Rel-18 Postponed Not in Chair notes Postponed
9.19 S2-2208392 LS OUT Approval [DRAFT] LS on XR and Media Services Ericsson Response to S2-2208105. Merged into (Covered by) S2-2208209 Dan (China Mobile) proposes to merge this LS to S2-2208209 and we only need one LS to RAN WGs.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208197 LS OUT Approval [DRAFT] Reply LS on UE Power Saving for XR and Media Services InterDigital Inc. Rel-18 Response to S2-2208105. Merged into (Covered by) S2-2208209 Dan (China Mobile) proposes to merge this LS to S2-2208209 and we only need one LS to RAN WGs.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209107 LS OUT Approval [DRAFT] Reply LS on XR-awareness in RAN Intel Rel-18 Response to S2-2208144. Merged into (Covered by) S2-2208209 Dan (China Mobile) proposes to merge this LS to S2-2208209 and we only need one LS to RAN WGs.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209157 LS OUT Approval [DRAFT] Reply LS on XR-awareness in RAN Qualcomm Incorporated Rel-18 Response to S2-2208144. Merged into (Covered by) S2-2208209 Dan (China Mobile) proposes to merge this LS to S2-2208209 and we only need one LS to RAN WGs.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208209 LS OUT Approval [DRAFT] LS on XR and Media Services vivo Response to S2-2208105 and S2-2208144. CC#4: r26 agreed. Revised to S2-2209979, merging S2-2208779. Xiaowan Ke(vivo) provides r01 to merge LSs to RAN
Paul (Ericsson) provides r02.
Xiaowan Ke(vivo) provides r03
Lei(Tencent) provides comments.
Xiaowan Ke(vivo) replies to Lei(Tencent) and seek clarification from proponent for the question in KI#8; If no clarification, it is proposed to remove it in later revision.
Devaki (Nokia) comments that it is better to wait for conclusions to be stable to discuss the LS. Also, for KI#8 specifically, we already have significant input in the LS from RAN1.
Xiaowan(vivo) relies to Devaki (Nokia) and provide r04.
Mukesh (MediaTek) and provides r05.
Mike (InterDigital) comments and provides r06 and points out that this is a reply LS to R1-2205531/S2-2208105.
Chunshan(CATT) provides r07.
Dario (Qualcomm) comments and provides r08
Zhuoyun (Tencent) comments and provides r09.
Xiaowan Ke(vivo) provides r10
Hui (Huawei) provides r11.
Mike (InterDigital) comments and provides r12
Mukesh (MediaTek) objects to r12.
Mukesh (MediaTek) no longer objects to r12.
Curt (Meta) comments.. provided r13 (based on r12).
Xiaowan Ke(vivo) replies to Curt (Meta) and provides r14
Lei(Tencent) provide comments and r15.
Dario (Qualcomm) comments and provides r16.
Xinpeng(Huawei) replies to Dario (Qualcomm).
Hui (Huawei) objects to r16.
Saso (Intel) seeks clarification on 'per-RAN node congestion' and the relevance of 'per-DRB congestion'.
Xiaowan(vivo) replies to Saso (Intel) on 'per-RAN node congestion' and the relevance of 'per-DRB congestion'.
Curt (Meta) replies Xiaowan
Saso (Intel) replies to Xiaowan.
Paul (Ericsson) provides r17.
Xiaowan Ke(vivo) provides 18
Paul (Ericsson) asks Xiaowan question for clarification.
Xiaowan(vivo) replies to Paul (Ericsson)
Mukesh (MediaTek) agree with Paul (Ericsson)
Xiaowan(vivo) replies to Mukesh (MediaTek) and Paul (Ericsson) and provide 19
Xiaowan(vivo) provide r19
Paul (Ericsson) provides r20 to find a compromise text.
==== Revisions Deadline ====
Devaki (Nokia) cannot accept the text regarding Uplink for KI#4/5 in the LS as it is technically incorrect. I have indicated # of times, SA2 specified reflective QoS framework also addresses UL.
Xiaowan(vivo) replies to Devaki (Nokia)
Hui(Huawei) clarify that we have definition for 'congestion level info' then Q0 is not needed.
Xiaowan Ke(vivo) proposes to agree r20 with addition of agreed pCR 2208536rZZ for KI#3 and removal of 'SA2 understands the uplink PDU Set handling is closely related to the interaction between the UE and RAN. Hence, SA2 decides to focus on the downlink PDU Set handling and to align with RAN's progress and decision for uplink, if any. '
Paul (Ericsson) provides r21.
Hui (Huawei) provide r22 and r23, objects other versions.
Devaki (Nokia) agrees with r20 with addition of agreed pCR 2208536rZZ for KI#3 and removal of 'SA2 understands the uplink PDU Set handling is closely related to the interaction between the UE and RAN. Hence, SA2 decides to focus on the downlink PDU Set handling and to align with RAN's progress and decision for uplink, if any. '
Hui (Huawei) asks to pending the LS until the comments from Ericsson and Qualcomm on 'congestion level info' is resolved in S2-2208673.
Xiaowan Ke(vivo) agrees with option1 and option1_plus and prefers option1; Option1: r20 with addition of agreed pCR 2208536rZZ for KI#3 and removal of 'SA2 understands the uplink PDU Set handling is closely related to the interaction between the UE and RAN. Hence, SA2 decides to focus on the downlink PDU Set handling and to align with RAN's progress and decision for uplink, if any. ' and removal of 'SA2 is also considering per QoS flow congestion information exposure on N2 as well as on N3 for which SA2 seeks RAN WGs feedback.'. Option1_plus: further remove all the questions for KI#3 based on Option1
Hui (Huawei) can accept option 1 only after we agreed on a definition on 'congestion level info' in S2-2208673 since the question use it but some companies challenge the definition.
Xiaowan Ke(vivo) ask for CC#3 if it is not agreed
Dan(China Mobile) ask for CC#3 and suggest to send the LS out to RAN in this meeting.
==== Final Deadline ====
Dario (Qualcomm) proposes to attach to r23 the agreed 8673rXX and add:
'Q3: whether it is feasible for NG-RAN to provide the congestion level to 5GC at QoS flow level'
Hui (Huawei) proposes to attach to r23 the agreed 8673rXX and add:
'Q3: whether it is feasible for NG-RAN to provide the above congestion level to 5GC at QoS flow level'
And change 'congestion' in Q1 and Q2 to 'congestion level'
Xiaowan Ke(vivo) provides r24 on top of r20 and ask people to check
Saso (Intel) proposes (again) to remove 'per-DRB' from Q1 and Q2.
Paul (Ericsson) asks Xiaowan (vivo) to clarify what 'without UE involvement' in context of this LS means.
Paul (Ericsson) replies to Xiaowan) and asks for further clarification.
Paul (Ericsson) can't accept stage 3 like statements in this LS and provides an alternative wording in r25.
Hui (Huawei) asks why congestion level info is stage 3 statements.
Hui (Huawei) insist on asking 'per-DRB' congestion.
Hui (Huawei) asks to remove Q3 assume the definition is clear.
Xiaowan Ke(vivo) uploads r24 in CC#3 folder
Xiaowan Ke(vivo) provides r25 for CC#4 based on offline consensus
Curt (Meta) provides r26 which removes 'UE involvement...'from 2ndQ.
Dan (China Mobile) suggest that r25 can be approved
Revised
9.19 S2-2209979 LS OUT Approval LS on XR and Media Services SA WG2 - Revision of S2-2208209r26, merging S2-2208779. Approved Approved
9.19 S2-2208779 LS OUT Approval [DRAFT] LS on Use of advanced jitter statistics for XR service power saving Huawei, HiSilicon Rel-18 Merged into S2-2209979 Dan (China Mobile) proposes to merge this LS to S2-2208209 and we only need one LS to RAN WGs.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209158 LS OUT Approval [DRAFT] LS on N6 PDU Set identification and marking Qualcomm Incorporated Rel-18 r11 agreed. Revised to S2-2209905. Mike (InterDigital) comments and provides r01
Dario (Qualcomm) replies to Mike and provides r02.
Dan (China Mobile) comments and this LS is not needed
Lei (Tencent) shares the concern of Dan.
Boren (OPPO) shares the same view as Dan.
Xiaowan Ke(vivo) shares the view with Dan and Yixue. The necessity for this LS is not confirmed
Mike (InterDigital) responds to Dario and is ok to send the LS
Youngkyo(Samsung) is okay to send an LS excluding traffic classification topic( see the revision r03).
Hui (Huawei) provides r04
Chunshan(CATT) provides r05.
Kenichi (KDDI) provides r06.
Mike (InterDigital) provides r07
Hui (Huawei) comments on r07
Mike (InterDigital) provides r08 in reply to Hui (Huawei)
Lei (Tencent) provide comments and also r09. Can not accept only ask whether will specify but without timeline information.
==== Revisions Deadline ====
Paul (Ericsson) provides responses to Dario and Mike and r10.
Dario (Qualcomm) OK with removing 'Late PDU set delivery indication' from example.
Lei (Tencent) prefers r09, objects r00-r08.
Lei (Tencent) provides comments
Paul (Ericsson) we are ok to remove'Late PDU set delivery indication' from example.
Dario (Qualcomm) provides r11 = r10 - 'Late PDU set delivery indication'.
Xiaowan Ke(vivo) comments r10 an its plus
Dario (Qualcomm) I am fine with r09, r08, r07.
==== Final Deadline ====
Revised
9.19 S2-2209905 LS OUT Approval LS on N6 PDU Set identification SA WG2 Rel-18 Revision of S2-2209158r11. Approved Approved
9.19 S2-2208674 P-CR Approval 23.700-60: Clean up for TR 23.700-60. China Mobile, Tencent Rel-18 r01 agreed. Revised to S2-2209906. Dario (Qualcomm) provides r01
==== Revisions Deadline ====
Dan (China Mobile) accept r01
==== Final Deadline ====
Revised
9.19 S2-2209906 P-CR Approval 23.700-60: Clean up for TR 23.700-60. China Mobile, Tencent, Huawei Rel-18 Revision of S2-2208674r01. Approved Approved
9.19 - - - KI1&2 evaluation & conclusion - - Docs:=16 -
9.19 S2-2208189 P-CR Approval 23.700-60: KI #1 and KI#2, New Evaluation: Overall Evaluation for Key Issues #1 and #2. InterDigital Inc. Rel-18 Merged into S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 and S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208190 P-CR Approval 23.700-60: KI #1, New Conclusion: Overall Conclusion for Key Issue. InterDigital Inc. Rel-18 Merged into S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208191 P-CR Approval 23.700-60: KI #2, New Conclusion: Overall Conclusion for Key Issue. InterDigital Inc. Rel-18 Merged into S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208210 P-CR Approval 23.700-60: KI#1&2, Conclusions. Vivo Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 for KI#1 and S2-2208390 for KI#2
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208390 P-CR Approval 23.700-60: KI#1 and KI#2, Solutions evaluation and conclusion. Ericsson, Deutsche Telekom, Meta, Apple, Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2209907, merging S2-2208189, S2-2208190, S2-2208191 and S2-2208667 Dan(China Mobile) provide r01 to show the update version
Dan(China Mobile) suggest to use this paper for KI#2 evaluation and conclusion discussion. And all the other related KI#2 conclusion paper should be merged into this one in order to reduce the parallel discussion.
Jinhua (Xiaomi) provides comments, about MMCI
Saso (Intel) comments on r01 and why it is not acceptable
Youngkyo(Samsung) provide comments.
Mengzhen (China Telecom) comments.
Saso (Intel) replies to Youngkyo
Markus (Nokia) comments.
Saso (Intel) replies to Markus
Markus (Nokia) provides r02 which builds on top of KI#1 conclusions.
Shabnam (Ericsson) provides comments that it will be difficult to converge so many various solns and also majority proposed KI 1 & 2 conclusion together. And updates are not acceptable since removes simple soln possible already.
Curt (Meta) supports Ericsson's view. KI 1&2 conclusion should be dealt with together to get a holistic view.
Dan(China Mobile) suggest if company suggest to have single paper for KI1&2, this paper is suggested to be merged into 8662, I will provide a update for 8662, the first step is to generate the version which we can converged,
Xinpeng(Huawei) supports to merge 8390 into 8662.
Dan(China Mobile) provide information
Jinhua (Xiaomi) provided comments, merged both KIs can live with me. Muti-modality Communication Group Identifier (MMCGI) is proposed to combined the Group ID and MMCI.
Shabnam (Ericsson) provides comments and r03
Dan (China Mobile) provides r04, and this paper is individually to be handled, not merged.
Shabnam (Ericsson) provides comments that I see on the other thread we added only for Multiple UEs, I think we are now working in tandem difficult to work through.
Dan (China Mobile) reply that separate the paper is ok, since we are ok with the content of r04 in this paper.
==== Revisions Deadline ====
Dario (Qualcomm) is OK only w/ r0 and r03. Other revisions are NOT OK.
Dan (China Mobile) request Dario to double check the r04. The conclusion part of r04 is the same as r03, the only difference is r04 without the evaluation part.So I hope you can accept r04.
Dan(China Mobile) suggest to go with r04.
Xinpeng(Huawei) suggests to go with r04.
Dan(China Mobile) object r03 and support r04.
Jinhua (Xiaomi) provides comments, suggest to go with r04, which achieved all of the concern, with same conclusion with r03 and better evaluation process.
Lei (Tencent) is fine to go with r04
Dan(China Mobile) object to r03 and suggestion to go with r04
Dario (Qualcomm) is OK w/ r04 (please ignore my previous comment).
==== Final Deadline ====
Revised
9.19 S2-2209907 P-CR Approval 23.700-60: KI#1 and KI#2, Solutions evaluation and conclusion. Ericsson, Deutsche Telekom, Meta, Apple, Qualcomm Incorporated Rel-18 Revision of S2-2208390r04, merging S2-2208189, S2-2208190, S2-2208191 and S2-2208667. Approved Approved
9.19 S2-2208532 P-CR Approval 23.700-60: KI#1, Conclusion. OPPO Rel-18 Merged into S2-2209908 Dan(China Mobile) propose to merge this paper into S2-2208662
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208546 P-CR Approval 23.700-60: KI #1,2: Evaluation and Conclusion. China Telecom Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 for KI#1 and S2-2208390 for KI#2
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208547 P-CR Approval 23.700-60: KI#1 and KI#2, Solutions evaluation. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 and S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208548 P-CR Approval 23.700-60: KI#1 and KI#2, Conclusions . Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 and S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208662 P-CR Approval 23.700-60: Evaluation and conclusion for KI1. China Mobile, Huawei, HiSilicon Rel-18 r20 agreed. Revised to S2-2209908, merging S2-2208210, S2-2208532, S2-2208546, S2-2208547, S2-2208548, S2-2208687, S2-2208759 and S2-2208803 Dan(China Mobile) provide r01. And suggest to use this paper for KI#1 evaluation and conclusion discussion. And all the other related KI#1 conclusion paper should be merged into this one in order to reduce the parallel discussion.
Markus (Nokia) provides r02 and explains the updates from r01 to r02.
Boren (OPPO) provides r03.
Saso (Intel) seeks clarification on the feasibility of 'The maximum 5GS delay difference threshold for the group of flows'.
Boren (OPPO) provides comments.
Markus (Nokia) reponds to Boren (OPPO) and Saso (Intel) comments on joint resource allocation/admission control.
Xiaowan(vivo) replies to Boren (OPPO)
Lei (Tencent) provides comments.
Xinpeng(Huawei) comments.
Mengzhen (China Telecom) comments.
Xiaowan Ke(vivo) provides r04
Dan(China Mobile)reply to Saso
Dan(China Mobile)provide r05
Mike (InterDigital) provides r06
Dario (Qualcomm) comments and proposes to take 8390 as baseline also for KI#1.
Mengzhen (China Telecom) comments and provide r07.
Dan(China Mobile) comments and cannot accept to 8390 as baseline for KI#1.
Xinpeng(Huawei) replies to Dario (Qualcomm).
Jinhua (Xiaomi) provides comments, separate the discussion into 8662 and 8390 is prefer, and proposals with clarification.
Saso (Intel) replies to Xinpeng(Huawei).
Xinpeng(Huawei) replies to Saso (Intel).
Markus (Nokia) provides r08.
Shabnam (Ericsson) provides comments that it seems majority of proposals used KI 1/2 together so seems we are artificially separating the conclusion to a certain extent. We propose the simple approach be used as baseline first as in 8390.
Jinhua(Xiaomi) provides comments, keep the conclusion of KI#1 and #2 separately as it is now is prefer. Mixed the different issues with no consensus achieved together at the DDL day of revisions, that has no help for progress.
Mengzhen (China Telecom) shares the same view with Jinhua.
Dan(China Mobile) provide a merged paper with include 8390 into 8662, please check it
Mike (InterDigital) provides r10
Markus (Nokia) comments.
Jinhua(Xiaomi) provides comments, and r11
Jinhua (Xiaomi) replies to Markus,
Dan(China Mobile) provides r12
Youngkyo(Samsung) provides comment.
Dan(China Mobile) provides r13.
Jinhua(Xiaomi) replies to Dan, can live with r12
Xiaowan Ke(vivo) provides r14
Saso (Intel) comments on r13
Markus (Nokia) provides r15.
Dan (China Mobile) provides r16.
Shabnam (Ericsson) provides comments that we can not accept this version as from our perspective we need to include the baseline that we can support this without such changes. r17 provides baseline and an FFS of if any other impacts are needed.
Sudeep (Apple) comments that r17 still has references to KI#2 (multiple UE case).
Xinpeng(Huawei) objects to r17, and disagree r17 is baseline.
Mengzhen (China Telecom) is OK with r16, and objects to r17.
Dan (China Mobile) not ok with r17 and provide r18 based on r17. This paper is changed to support Ki#1
Saso (Intel) prefers the approach in r17.
Markus (Nokia) provides r19.
Shabnam (Ericsson) provides comments that the concept of group we still are not convinced so take that off until further work, r20 provided
==== Revisions Deadline ====
Dario (Qualcomm) seeks clarification on r20.
Dan (China Mobile) response
Dan (China Mobile) is ok with r20, suggest to go with r20
Shabnam (Ericsson) agrees that r20 has inconsistencies which can be clarified with simple post revision update, provides a revision in the Drafts folder as r20_ER. We can't accept any revision with assumption that we need to have this group concept to make the soln work.
Dan (China Mobile) summary some udpate based on r20:
1) adding'any additional' in bullet:Normative impact to AF and NEF/PCF
2) change'PCF enforces the flow admission.' into'PCF performs the flow authorization .'
3) change'PCF enforces QoS fulfilment i.e. updates one flow policy with considering other multi-modality flows policies. ' into 'PCF provisions QoS information considering the requirements provided by the AF for all data flows associated to a multi-modal (XRM) application.'
4) Update the last EN into 'Editor's Note: Whether the PCF sends the policy information to SMF/NG-RAN, and Whether the NG-RAN should support the additional policies and how NG-RAN uses them is FFS.'
Markus (Nokia) asks for clarification and about potential inconsistencies still in r20_ER. Proposes to add 'alternative service requirements' to the list of information AF can provide.
Shabnam (Ericsson) thanks Nokia and comments in line
Dan (China Mobile) suggest to go with r20+ following changes:
1) adding'any additional','alternative service requirements' in bullet:Normative impact to AF and NEF/PCF
2) change'PCF enforces the flow admission.' into'PCF performs the flow authorization .'
3) change'PCF enforces QoS fulfilment i.e. updates one flow policy with considering other multi-modality flows policies. ' into 'PCF provisions QoS information considering the requirements provided by the AF for all data flows associated to a multi-modal (XRM) application.'
4) remove 'group level ' in 'PCF enforces the group level policy for the use of Alternative QoS parameters.'
5) change last EN into 'Editor's Note: Whether the PCF sends the policy information to SMF/NG-RAN, and Whether the NG-RAN should support the additional policies and how NG-RAN uses them is FFS.'
Jinhua (Xiaomi) supports the proposal from Dan,
==== Final Deadline ====
Shabnam (Ericsson) ok with the proposed way forward by CMCC/Rapporteur.
Dario (Qualcomm) is OK with Dan's proposal except for bullet 1). The change vs. r20 needs to be
1) remove 'and requirements' in bullet: Normative impact to AF and NEF/PCF
Dan (China Mobile) is OK with this proposal from Dario, and I suppose this is editorial correction, if chairman have time, we can open discussion in CC#3,
Xinpeng(Huawei) proposes to chang 'Normative impact to AF and NEF/PCF: extend the existing Nnef_AFsessionWithQoS service to allow the AF to provide, at the same time, service requirements, a common ID and requirements for multiple IP data flows associated to a multi-modal (XRM) application.' INTO 'Normative impact to AF and NEF/PCF: extend the existing Nnef_AFsessionWithQoS service to allow the AF to provide, at the same time, a common ID and service requirements for multiple IP data flows associated to a multi-modal (XRM) application.' for better readbility.
'
Revised
9.19 S2-2209908 P-CR Approval 23.700-60: Evaluation and conclusion for KI1. China Mobile, Huawei, HiSilicon, China Telecom, InterDigital, Nokia, OPPO,Samsung, vivo, Ericsson, ZTE Rel-18 Revision of S2-2208662r20, merging S2-2208210, S2-2208532, S2-2208546, S2-2208547, S2-2208548, S2-2208687, S2-2208759 and S2-2208803. Approved Approved
9.19 S2-2208667 P-CR Approval 23.700-60: Evaluation and conclusion for KI#2. China Mobile Rel-18 Merged into S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208687 P-CR Approval 23.700-60: Conclusion on KI #1 and #2. Samsung Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 and S2-2208390
Youngkyo(Samsung) propose to have one paper between KI#1 and #2
Dan(China Mobile) answer the comment
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208759 P-CR Approval 23.700-60: Evaluation and conclusion of KI #1/2 Policy control enhancement and QoS policy coordination for multi-modal traffic for single. Huawei, HiSilicon Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) propose to merge this paper into S2-2208662 and S2-2208390
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208803 P-CR Approval 23.700-60: KI#1, KI#2: Conclusion. Intel Rel-18 Merged into S2-2209908 and S2-2209907 Dan(China Mobile) provide comment for this paper, also suggest to merge into S2-2208662 and S2-2208390 to avoid parallel discussion
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 - - - KI3 evaluation & conclusion - - Docs:=14 -
9.19 S2-2208211 P-CR Approval 23.700-60: KI#3, Conclusion update for normal data interruption event. Vivo, Meta, China Mobile, China Telecom, MediaTek, OPPO, Xiaomi, Apple, Tencent Rel-18 CC#3: This was postponed. Devaki (Nokia) raises question regarding the proposal
Xiaowan Ke(vivo) replies to Devaki (Nokia)
Xiaowan Ke(vivo) replies to Paul (Ericsson): we have studies it half year and you didn't attend before. We also take long time offline + CC with you. You can object but you cannot judge it 'not been sufficiently studied'. It is totally untechnical and unfair comment. I encourage technical comment
Ellen (Google) supports this document with the clarification on exposure of mobility event
Xiaowan Ke(vivo) provides r01
Devaki (Nokia) comments.
Hui (Huawei) share concerns as other companies.
Xiaowan(vivo) replies to Devaki (Nokia) and hui(Huawei) and provide r02
Paul (Ericsson) objects to r0, r01 and r02 and that proposal in general, i.e. all revisions. This has not been studied enough and thus too many aspects are unclear to make any conclusions.
Xiaowan Ke(vivo) request a show hand for this item
Curt (Meta) supports Vivo's view.
Hui (Huawei) asks question.
Saso (Intel) seeks clarification from Xiaowan Ke(vivo)
Xiaowan Ke(vivo) to Hui (Huawei)
==== Revisions Deadline ====
Dan(China Mobile) provide a document for SoH for CC#2
==== Final Deadline ====
Postponed
9.19 S2-2208212 P-CR Approval 23.700-60: KI#3, Conclusions update for L4S, etc. Vivo Rel-18 Merged into (Covered by) S2-2208536 Dan (China Mobile) suggest to merge this paper to S2-2208536
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208393 P-CR Approval 23.700-60: KI#3, Update to conclusions. Ericsson Rel-18 Noted Xiaowan Ke(vivo) objects to this paper
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.19 S2-2208449 P-CR Approval 23.700-60: KI#3: Exposure information via QNC Notification: Evaluation and Conclusion. MediaTek Inc., vivo Rel-18 Noted Hui (Huawei) comments
Mukesh (MediaTek) responds to Hui (Huawei)
Hui (Huawei) provides further comments
Devaki (Nokia) comments.
Hui (Huawei) provide r03
Mukesh (MediaTek) provides r04
Mukesh (MediaTek) provides r05
Yali (OPPO) comments
==== Revisions Deadline ====
Devaki (Nokia) comments that r04 is misleading and wrong.
Devaki (Nokia) proposes to NOTE the CR and its revisions as existing conclusion already includes data rate anyway.
Mukesh (MediaTek) replied to Devaki (Nokia)
==== Final Deadline ====
Noted
9.19 S2-2208536 P-CR Approval 23.700-60: KI#3: Conclusion update about L4S enabling. OPPO Rel-18 CC#4: r24 agreed. Revised to S2-2209977. Yali (OPPO) provides r02
Hui (Huawei) provides r01
Hui (Huawei) provides r03 and comments
Xiaowan replies to HW (Huawei) and provider04
Hui (Huawei) replies to Xiaowan.
Zhuoyun (Tencent) provides r05.
Chunshan (CATT) comments.
Hui (Huawei) replies to Zhuoyun.
Hui (Huawei) response to Chunshan.
Yali (OPPO) provides r06.
Chunshan (CATT) response to Hui.
Devaki (Nokia) comments that it is important to clarify that the alt.1/alt.2 being added on-the-fly applies only to Method 2.
Dario (Qualcomm) questions the need for two alternatives to perform ECN marking in the UPF.
Chunshan (CATT) response to Hui and provides r08.
Hui (Huawei) provides r09.
Yali (OPPO) provides r10
Xiaowan(vivo) objects to r09.
Dan (China Mobile) reply to Dario, as the operator view, and support to introduce two options for L4S
Hui(Huawei) replies.
Xiaowan(vivo) replies Hui(Huawei).
Saso (Intel) supports Qualcomm's view and provide r11 removing Method 2.
Hui(Huawei) objects to r11 and explain.
Yali (OPPO) cannot accept r11.
Mukesh (MediaTek) also objects to r11 and provides r12 based on r10
Paul (Ericsson) clarifies that r07 was uploaded yesterday evening by mistake, but we are ok with as it has come into the revisions stream.
Xiaowan Ke(vivo) provides r13
Mukesh (MediaTek) objects to r13. UPF is not required to store information related to congestion in L4S.
Jaehyeon (Samsung) objects to r13. UPF is not required to store information related to congestion and 'if L4S traffic detection is used to trigger a L4S dedicated QoS flow establishment' is not clear.
Chunshan (CATT) provides r14.
Xiaowan(vivo) replies to Chunshan (CATT), Mukesh (MediaTek) and Jaehyeon (Samsung) and provides r15.
Yali (OPPO) provides r16.
Hui (Huawei) provides r17.
Xiaowan Ke(vivo) replies Hui (Huawei) and Yali (OPPO) and provide r18
Paul (Ericsson) provides r19 and objects to r18, r17, r16, r15, r14, r13, r12, r10, r6, r5, r4, r3, r2, r1, r0.
Saso (Intel) provides r20 (on top of r19).
Dan (China Mobile) provides r21 (on top of r20).
Hui (Huawei) provides r22.
Xiaowan Ke(vivo) provides r23
==== Revisions Deadline ====
Dario (Qualcomm) can accept r19-r23 only if LS Out 8209 includes question on semantic and definition of 'congestion level information'.
Devaki (Nokia) cannot accept the CR / any of the revision unless it is clearly clarified that the two new alternatives are applicable only for Method 2.
Yali(OPPO) clarifies to Devaki (Nokia), there's no alternative2, and the alternative1 is clearly stated only for Method2.
Yali (OPPO) proposes to approve r23 or r23 with removing the sentence which Dario has concern.
Hui(Huawei) can accept r22, r23, and object any other versions.
Xiaowan(vivo) replies to Yali (OPPO)
Yali (OPPO) proposes to approve r23 as the term is not introduced by this paper, it's already in the existing TR conclusion. I can also live with r23 with removing 'when the UL/DL congestion level information changes (e.g. UL/DL congestion start, degree of UL/DL congestion, UL/DL congestion end) , NG-RAN reports the latest UL/DL congestion level information to PSA UPF via GTP-U header of UL packet.'.
Dan (China Mobile) support OPPO's suggested way forward: r23+removing the sentence
==== Final Deadline ====
Dario (Qualcomm) is OK with CMCC and OPPO's proposal provided that 8673 has a clear defintion of 'congestion level'.
Yali (OPPO) provides r24 based on r23, with following changes:
1. Remove 'In this method, when the UL/DL congestion level information changes (e.g. UL/DL congestion start, degree of UL/DL congestion, UL/DL congestion end), NG-RAN reports the latest UL/DL congestion level information to PSA UPF via GTP-U header of UL packet.'
2. Add 'In Method2'
3. Replace 'generates' by 'may generate'
Yali (OPPO) provides r24 based on r23, with following changes:
1. Remove 'In this method, when the UL/DL congestion level information changes (e.g. UL/DL congestion start, degree of UL/DL congestion, UL/DL congestion end), NG-RAN reports the latest UL/DL congestion level information to PSA UPF via GTP-U header of UL packet.'
2. Add 'In Method2'
3. Replace 'generates' by 'may generate'
Revised
9.19 S2-2209977 P-CR Approval 23.700-60: KI#3: Conclusion update about L4S enabling. OPPO, vivo, Huawei Rel-18 Revision of S2-2208536r24. Approved Approved
9.19 S2-2208567 P-CR Approval 23.700-60: KI#3: Update conclusion for network exposure. Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208673 Dan (China Mobile) suggest to merge this paper to S2-2208673
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208658 P-CR Approval 23.700-60: Update conclusions for Key Issue#3. China Mobile Rel-18 Merged into (Covered by) S2-2208673 Dan(China Mobile) merge this paper into S2-2208673.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208663 P-CR Approval 23.700-60: KI#3, Evaluation. Tencent, Tencent Cloud Rel-18 Merged into (Covered by) S2-2208673 Dan (China Mobile) suggest to merge this paper to S2-2208673
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208673 P-CR Approval 23.700-60: KI#3, conclusion update. Tencent, Tencent Cloud, Xiaomi Rel-18 CC#4: r24 + changes (r25) agreed. Revised to S2-2209978, merging S2-2208823 and S2-2208999. Zhuoyun (Tencent) provides r01 by merging S2-2208567, S2-2208658, S2-2208663, S2-2208823 and S2-2208999 as suggested by rapporteur.
Xiaowan Ke(vivo) provides r02
Dan(China Mobile) provides r03
Mukesh (MediaTek) provides r04
Zhuoyun (Tencent) suggests to follow the suggestion of rapporteur that 8449 and 8211 are handled individually, so there is no need to add the revisions from 8449 and 8211 into this contribution.
Dan (China Mobile) suggests to avoid such merging. So MTK's requirement of parameter exposure should not be discussed in this paper.
Hui(Huawei) provides r05
Mukesh (MediaTek) responds to Dan (China Mobile)
Xiaowan Ke(vivo) provides r06
Paul (Ericsson) provides r07 based on r05.
Zhuoyun (Tencent) comments.
Chunshan(CATT) comments.
Xiaowan Ke(vivo) object to r07 and replies Zhuoyun (Tencent)
Zhuoyun (Tencent) provides r08 based on r07 to solve the concern on the Note from Xiaowan.
Xiaowan Ke(vivo) provides r09
Hui (Huawei) provides r10.
Paul (Ericsson) asks question for clarification.
Devaki (Nokia) provides r13.
Hui (Huawei) replies.
Zhuoyun (Tencent) provides r11 and r12.
Zhuoyun (Tencent) provides r14, r15 and r16.
Hui (Huawei) provides r17.
Xiaowan Ke(vivo) replies to Zhuoyun (Tencent)
Saso (Intel) seeks clarification on 'delay difference'.
Paul (Ericsson) asks for clarification on what interfaces RAN/CN QNC and congestion level is intended to be exposed.
Paul (Ericsson) replies to Hui.
Zhuoyun (Tencent) clarifies.
Saso (Intel) proposes r18 with a clarification on 'delay difference'.
Hui (Huawei) replies to Paul.
Zhuoyun (Tencent) is fine with r18.
Hui(Huawei) provides r19.
Zhuoyun (Tencent) replies.
Mukesh (MediaTek) provides r20.
==== Revisions Deadline ====
Chunshan (CATT) replies to Hui (Huawei).
Mukesh (MediaTek) supports r20 and objects to all other revisions.
Hui (Huawei) replies to Chunshan.
Hui (Huawei) asks question on the new sentence in r20.
Mukesh (MediaTek) responds to Hui (Huawei)
Paul (Ericsson) can only accept r0.
Dan (China Mobile) ask further
Dan(China Mobile) propose a way forward. r20+ remove
'Congestion level information: values denoting the following: the degree of current congestion, no congestion/congestion end, congestion start, directions.. A lower value means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.
'
Mukesh (MediaTek) replies to Dan (China Mobile)
Paul (Ericsson) objects to all revisions except r0.
Zhuoyun (Tencent) proposes to go forward with the suggestion by Paul: r20 with removing the following text:
'Congestion level information: values denoting the following: the degree of current congestion, no congestion/congestion end, congestion start, directions.. A lower value means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.'
Hui (Huawei) propose r20 + changes.
Dan(China Mobile) reply and request Paul to find other version which we can work on besides r0
Chunshan (CATT) supports r20.
>Hui (Huawei) propose r20 + changes.
>
Dario (Qualcomm): definition of congestion level and instructions to RAN need to be clearer.
Zhuoyun (Tencent) proposes to go with r20 with the following changes:
'Congestion level information: E.g., values denoting the following: including a value to denote the degree of current congestion level, no congestion/congestion end, congestion start, and directions on which congestion happens. A lower value degree means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.'
==== Final Deadline ====
Dario (Qualcomm) propose to include in r20:
Congestion level = a value denoting the level of congestion in the RAN. The lower the value, the lower the level of congestion.
Congestion level information: congestion level, and indication of the direction(s) in which the congestion happens.
NOTE: The coding of congestion level and related range, whether congestion start/end indications can be denoted by specific level values or need separated IEs is up to Stage 3.
Dario (Qualcomm) propose to include in r20:
Congestion level = a value denoting the level of congestion in the RAN. The lower the value, the lower the level of congestion.
Congestion level information: congestion level, and indication of the direction(s) in which the congestion happens.
NOTE: The coding of congestion level and related range, whether congestion start/end indications can be denoted by specific level values or need separated IEs is up to Stage 3.
Zhuoyun (Tencent) provides r24 for CC#4 based on offline consensus.
r24 is r20 plus following changes:
(1) changing
'Congestion level information: values denoting the following: the degree of current congestion, no congestion/congestion end, congestion start, directions.. A lower value means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.'
to 'RAN provides the congestion information enabling PSA UPF to perform API exposure towards the AF and ECN marking for L4S;'
(2) for Note 3, move '(e.g. per QoS flow congestion level)' to the end of the sentence.
Chunshan (CATT) provides r25 based on r24.

r25 is r20 plus following changes:
(1) changing
'Congestion level information: values denoting the following: the degree of current congestion, no congestion/congestion end, congestion start, directions.. A lower value means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.'
to 'RAN provides the congestion information to PSA UPF enabling PSA UPF to perform API exposure towards the AF and ECN marking for L4S;'
(2) for Note 3, move '(e.g. per QoS flow congestion level)' to the end of the sentence.
Chunshan (CATT) provides r25 based on r24.

r25 is r20 plus following changes:
(1) changing
'Congestion level information: values denoting the following: the degree of current congestion, no congestion/congestion end, congestion start, directions.. A lower value means less congestion is experienced.
NOTE: Whether congestion start/end can be denoted by specific level values or need separated IEs is up to Stage 3.'
to 'RAN provides the congestion information to PSA UPF enabling PSA UPF to perform API exposure towards the AF and ECN marking for L4S;'
(2) for Note 3, move '(e.g. per QoS flow congestion level)' to the end of the sentence.
Revised
9.19 S2-2209978 P-CR Approval 23.700-60: KI#3, conclusion update. Tencent, Tencent Cloud, Xiaomi, China Mobile, Huawei, Vivo, ZTE, CATT Rel-18 Revision of S2-2208673r24 + changes, merging S2-2208823 and S2-2208999. Approved Approved
9.19 S2-2208823 P-CR Approval 23.700-60: Update Conclusion for KI#3. ZTE Rel-18 Merged into S2-2209978 Dan(China Mobile) suggest this paper merged into S2-2208673
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208999 P-CR Approval 23.700-60: KI #3, conclusion update for clarification. Samsung Rel-18 Merged into S2-2209978 Dan(China Mobile) suggest this paper merged into S2-2208673
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209068 P-CR Approval 23.700-60: KI#3: update conclusion for support of 5GS information exposure. CATT Rel-18 Noted Chunshan (CATT) provides r01.
Dario (Qualcomm) comments.
Chunshan (CATT) response to Dario (Qualcomm).
Chunshan (CATT) provides r02.
Devaki (Nokia) comments that it is unclear whether these enhancements are actually necessary for non-GBR. We object to the RAN exposing data rate for non-GBR (first bullet added). Can live without the additions but if it remains, our revision in r03.
Chunshan (CATT) provides r04.
Devaki (Nokia) comments.
Chunshan(CATT) provides r05.
Paul (Ericsson) provides comments and expresses concerns on inclusion of this solution in the conclusions.
Chunshan(CATT) response to Paul (Ericsson) .
Hui (Huawei) provides r06.
Chunshan(CATT) objects r06 since it is not the target of the paper.
==== Revisions Deadline ====
Dario (Qualcomm) objects to every revision of this paper.
Chunshan (CATT) proposes to go with r03, since the bitrate for non-GBR notification is deleted.
Devaki (Nokia) objects to the paper and its revisions.
Chunshan responses to Devaki (Nokia) , you have provided r03, propose to go with r03 which delete the QNC for non-GBR QoS Flow.
==== Final Deadline ====
Noted
9.19 - - - KI4&5 evaluation & conclusion - - Docs:=19 -
9.19 S2-2208213 DISCUSSION Discussion Discussion on open issues on KI#4&5 vivo Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.19 S2-2208450 DISCUSSION Decision KI#4 & KI#5: Email discussion. MediaTek Inc. Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.19 S2-2208192 P-CR Approval 23.700-60: KI #4 and 5, New Eval: Key Issue #4 and #5 Evaluation Text for Solution 55. InterDigital Inc. Rel-18 Revision of (postponed) S2-2205912 from S2-152E. Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208214 P-CR Approval 23.700-60: KI#4&5, Conclusions . Vivo Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208228 P-CR Approval 23.700-60: KI #4 and 5: New Evaluation and Conclusion. Futurewei Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
John (Futurewei) is OK to merge into S2-2208568
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208391 P-CR Approval 23.700-60: KI#4 and KI#5: Solutions evaluation and conclusions. Ericsson Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208480 P-CR Approval 23.700-60: Key Issues #4 and #5: evaluation and conclusion. Lenovo Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208538 P-CR Approval 23.700-60: KI#4: Conclusion for the PDU Set Info over N3. OPPO Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208549 P-CR Approval 23.700-60: KI#4 & 5 Conclusion. Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208568 P-CR Approval 23.700-60: KI#4&5: Evaluation and Conclusion. Huawei, HiSilicon, China Mobile, KDDI, Lenovo Rel-18 CC#3: r34 + changes agreed. Revised to S2-2209938. Hui (Huawei) provides r01, merged parts of evaluation/conclusion proposals from other papers.
Jinhua (Xiaomi) provides r02,
Xiaowan Ke(vivo) provides r03 and comments
Kenichi (KDDI) comments on r03.
Xiaowan(vivo) replies to Kenichi (KDDI) and seek justification
John (Futurewei) provides 04 and comments.
Paul (Ericsson) provides comments and r05.
Mike (InterDigital) provides r06
Devaki (Nokia) provides r07, proposes to focus only on conclusion and not evaluation (which is unnecessary at this time for KI#4/5 when the study is almost start of the year).
Dario (Qualcomm) provides r08, but he is fine with focusing on the conclusions only.
Jaehyeon (Samsung) provides comments and r09.
Yali (OPPO) provides r10.
Xiaowan Ke(vivo) provides r11
Haley(Lenovo) replies to Paul (Ericsson) and provides r12.
Hui(Huawei) provides r13
Hui (Huawei) comments
Zhuoyun (Tencent) provides r14.
Hui (Huawei) provides r15.
Kenichi (KDDI) replies to Xiaowan(vivo).
Paul (Ericsson) replies to Haley (Lenovo).
Xinpeng(Huawei) provides r16.
Hui (Huawei) provide r17 to merge some changes from Nokia
Paul (Ericsson) provide r18 and comments.
Xinpeng(Huawei) replies to Paul (Ericsson).
Saso (Intel) provide r19 on top of r17.
Chunhui (Xiaomi) provides a NOTE suggestion about charging.
Paul (Ericsson) replies to Saso (Intel).
Saso (Intel) replies to Paul.
John (Futurewei) replies to Paul.
Svante (Sony) provide r20 based on r19.
Paul (Ericsson) provides r21 based on r17.
Xiaowan Ke(vivo) provides r22
Mukesh (MediaTek) ask Paul (Ericsson) to clarify why UPF dropping is removed when in RAN2 Ericsson is in favour?
Paul (Ericsson) replies to John (Futurewei) and Saso (Intel).
Paul (Ericsson) clarifies that R2-22100867 does not propose dropping by UPF. This contributions has a proposal that enables signaling of information to RAN to create app awareness etc (as it says).
Saso (Intel) replies to Paul (Ericsson).
Saso (Intel) provides additional reply to Paul (Ericsson).
John (Futurewei) responds to Paul (Ericsson)
Curt (Meta) comments...to Saso and Paul
John (Futurewei) comments, responds to Paul (Ericsson)
Devaki (Nokia) provides r23.
Chunhui (Xiaomi) provides r24.
Chunshan(CATT) provides r25.
Hui(Huawei) provides r26.
Xiaowan Ke(vivo) provides r27
Dario (Qualcomm) provides r28 and comments.
Svante (Sony) provides r29 that add content from r20
Chunhui (Xiaomi) provides r30 based on r28.
Paul (Ericsson) provides comments.
Svante (Sony) provides r32 based on r31 and missing sentence from r29
Hui (Huawei) asks for clarification on r32
Svante (Sony) respond to question and provide r33 with clarification.
Hui (Huawei) comments to r33.
Curt (Meta) comments to Svante (Sony)...
Svante (Sony) respond to Hui (Huawei) on r33.
Xiaowan Ke(vivo) replies to Svante (Sony) and provides r34
Svante (Sony) responds to Curt (Meta) and Xiaowan Ke(vivo)
Dario (Qualcomm) provides r35
Hui (Huawei) comments on r35
==== Revisions Deadline ====
Dario (Qualcomm) thanks Hui, asks to ignore r35 and is fine w/ r34.
Devaki (Nokia) comments that r34 is ok.
John (Futurewei) is OK with revisions r26 - r34.
Chunhui (Xiaomi) is fine with r34.
Youngkyo(Samsung) questions what PDU Set Identifier implies.
Devaki (Nokia) cannot accept any version up to and including r21. r34 is fine.
Hui (Huawei) proposes to go with r34.
Saso (Intel) points out that the intended use of PDU Set Importance is not defined in r34.
Hui (Huawei) replies to Saso.
Saso (Intel) replies to Hui (Huawei).
Paul (Ericsson) we object to all revisions except r05, r18 and r21.
Hui (Huawei) asks Paul to indicate what part is not acceptable in r34.
Xiaowan(vivo) support to go r34; alternatively, can go with r21 with removal of 'except for 'PDU Set Importance'' in 8.X.2.3
Devaki (Nokia) cannot accept r21 with the removal of 'except for 'PDU Set Importance'' in 8.X.2.3
Saso (Intel) is OK to keep PDU Set Importance, even though its intended use is not defined; but in that case we cannot accept to further work on Q2 on SoH in this meeting.
Paul (Ericsson) replies to Hui.
Svante (Sony) prefer r33 and accept any version after r21
Saso (Intel) points out that the EN on PDU Set dependency can be removed.
Yali (OPPO) cannot accept any version with PDU Set size as mandatory parameter, optional is ok but relies on the SA4 design.
Hui (Huawei) support to remove the EN on PDU Set dependency based on the working assumption.
==== Final Deadline ====
Paul (Ericsson) asks Yali (OPPO) to clarify why PDU Set size, as requested by RAN1 is not acceptable?
Saso (Intel) agrees with Yali (OPPO) on the 'number of PDUs in the PDU Set' parameter and proposes to remove it based on SA4 reply LS (9257).
Hui (Huawei) provides draft r36 as way forward and asks to discuss in CC#3. R36 is based on r34 with the following changes.
Hui (Huawei) provides r37 as way forward and asks to discuss in CC#3. R37 is based on r34 with the following 6 changes.
Hui (Huawei) provides r38. R38 is based on r34 with the following 6 changes.
Chunshan (CATT) provides the link of r38.
Saso (intel) asks why 'PDU Set Size in Bytes' was added back in r38, given that SA4 reply LS (S2-2209257) clarified that such information is not available.
Saso (Intel) replies that even though RAN1 have indicated that 'PDU set size (number of bits) or number of PDUs in a PDU set' may be helpful, SA4 replied that it is not possible to provide it.
Paul (Ericsson) asks to clarify what is the reasoning to designate some PDU Set info as optional and provides r39.
Devaki (Nokia) comments that we can still accept only r34, cannot accept r35-r38.
Saso (Intel) supports Nokia's proposal to move forward with r34 + one proposed change.
Xiaowan Ke(vivo) also propose to agree r34 or r34 minus
Yali (OPPO) agree the NOTE from Xiaowan, cannot accept Saso's NOTE
Paul (Ericsson) replies to Saso that SA4 LS was referring to Data Burst size and not PDU Set size.
Hui (Huawei) proposes to put a FFS for PDU Set Size.
Saso (Intel) is OK with the latest r34+ summary from Hui (Huawei).
Saso (Intel) replies to Paul (Ericsson) that SA4 LS also states that the size of the video slice/frame is 'not explicitely signalled in the bitstream'.
Devaki (Nokia) comments that we can live with r39 for now.
Hui (Huawei) replies to Paul.
Paul (Ericsson) the 'remove all' is preferred.
Paul (Ericsson) clarifies that it means that the size is known to the encoder / server today, but the server does not write the size explicitly into the stream. Of course, the existence of the PDU Set concept is currently limited to the FS_XRM TR.
Revised
9.19 S2-2209938 P-CR Approval 23.700-60: KI#4&5: Evaluation and Conclusion. Huawei, HiSilicon, China Mobile, KDDI, Lenovo, Nokia, Nokia Shanghai Bell, Xiaomi, vivo, Sony, ZTE, Tencent, CATT, Futurewei, Samsung, Ericsson, Intel Rel-18 Revision of S2-2208568r34 + changes. Approved Approved
9.19 S2-2208681 P-CR Approval 23.700-60: KI#4 and KI#5, Conclusions. Tencent, Tencent Cloud Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208690 P-CR Approval 23.700-60: Conclusions on KI #4 and #5. Samsung Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
Youngkyo(Samsung) is okay to merge this paper into baseline Tdoc S2-2208568.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208822 P-CR Approval 23.700-60: Conclusion for KI#4&5. ZTE Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208923 P-CR Approval 23.700-60: KI#4 and 5 evaluation of solution #50 and #70. Sony Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209069 P-CR Approval 23.700-60: KI#4/5: Sub-QoS Flow for PDU Set and Conclusion. CATT Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209071 P-CR Approval 23.700-60: KI#4, KI#5: Additional conclusion on PDU Set Information identification. Intel Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209072 P-CR Approval 23.700-60: KI#4, KI#5: Conclusion on PDU Set Importance. Intel Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209156 P-CR Approval 23.700-60: Key Issues #4 and #5: Conclusion principles. Qualcomm Incorporated Rel-18 Merged into (Covered by) S2-2208568 Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 - - - KI6 evaluation & conclusion - - Docs:=6 -
9.19 S2-2208215 P-CR Approval 23.700-60: KI#6, Overall evaluation and conclusion update. Vivo, China Mobile Rel-18 Merged into S2-2209909 Hui (Huawei) suggests to merge this paper into S2-2208550 and take S2-2208550 as baseline for KI6 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208535 P-CR Approval 23.700-60: KI#6, Conclusion Update. OPPO Rel-18 Merged into S2-2209909 Hui (Huawei) suggests to merge this paper into S2-2208550 and take S2-2208550 as baseline for KI6 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208543 P-CR Approval 23.700-60: KI#6: Conclusion Update. Tencent, Tencent Cloud Rel-18 Merged into S2-2209909 Hui (Huawei) suggests to merge this paper into S2-2208550 and take S2-2208550 as baseline for KI6 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208550 P-CR Approval 23.700-60: KI#6 Conclusion updates. Nokia, Nokia Shanghai Bell Rel-18 r08 agreed. Revised to S2-2209909, merging S2-2208215, S2-2208535, S2-2208543 and S2-2208569 Hui (Huawei) suggests to take this paper as baseline for KI6 evaluation/conclusion.
Saubhagya (Nokia) proposes S2-2208550r01 as baseline, (merges S2-2208215, S2-2208535, S2-2208543 & S2-2208569)
Hui (Huawei) proposes r02
Hui (Huawei) provides further comments
Saubhagya (Nokia) responds to comments. Proposes r03
Hui (Huawei) provides comments for r03
Saubhagya (Nokia) responds to comments on r03. Proposes r04
Boren (OPPO) provides comments and r05.
Dario (Qualcomm) provides r06 and asks question about r04.
Saubhagya (Nokia) responding to questions on r04. Adds questions and comments on r05. Provides r07
Xiaowan Ke(vivo) provides r08
Boren (OPPO) responds to Saubhagya (Nokia) and provides r09
Lei (Tencent) provides comments.
Boren (OPPO) comments.
Lei (Tencent) provides r10.
==== Revisions Deadline ====
Dario (Qualcomm) proposes to go with r07, r06 or r08. R10 and r09 are not OK.
Boren (OPPO) can live with r08.
Chunshan(CATT) comments and r06,r07,r 08 is ok.
Lei (Tencent) confirms that r06, r07, r08 are ok.
Xiaowan Ke(vivo) propose to agree r08
==== Final Deadline ====
Revised
9.19 S2-2209909 P-CR Approval 23.700-60: KI#6 Conclusion updates. Nokia, Nokia Shanghai Bell, OPPO, Tencent, Tencent Cloud, Huawei, Hisilicon, vivo Rel-18 Revision of S2-2208550r08, merging S2-2208215, S2-2208535, S2-2208543 and S2-2208569. Approved Approved
9.19 S2-2208569 P-CR Approval 23.700-60: Conclusion update for KI#6. Huawei, HiSilicon Rel-18 Merged into S2-2209909 Hui (Huawei) suggests to merge this paper into S2-2208550 and take S2-2208550 as baseline for KI6 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 - - - KI8 evaluation & conclusion - - Docs:=7 -
9.19 S2-2208194 P-CR Approval 23.700-60: KI #8, New Conclusion: Key Issue #8 Conclusion . InterDigital Inc. Rel-18 Merged into (Covered by) S2-2209159 Hui (Huawei) suggests to merge this paper into S2-2209159 and take S2-2209159 as baseline for KI8 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208216 P-CR Approval 23.700-60: KI#8, Conclusions . Vivo Rel-18 Merged into (Covered by) S2-2209159 Hui (Huawei) suggests to merge this paper into S2-2209159 and take S2-2209159 as baseline for KI8 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208451 P-CR Approval 23.700-60: KI#8: Evaluation and Conclusion . MediaTek Inc. Rel-18 Merged into (Covered by) S2-2209159 Hui (Huawei) suggests to merge this paper into S2-2209159 and take S2-2209159 as baseline for KI8 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208551 P-CR Approval 23.700-60: KI#8 Conclusion. Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2209159 Hui (Huawei) suggests to merge this paper into S2-2209159 and take S2-2209159 as baseline for KI8 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208778 P-CR Approval 23.700-60: Conclusion for KI#8. Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2209159 Hui (Huawei) suggests to merge this paper into S2-2209159 and take S2-2209159 as baseline for KI8 evaluation/conclusion.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2209159 P-CR Approval 23.700-60: Key Issue #8: Evaluation and conclusion. Qualcomm Incorporated Rel-18 CC#3: r27 + changes agreed. Revised to S2-2209939. Hui (Huawei) suggests to take this paper as baseline for KI8 evaluation/conclusion.
Dan (China Mobile) provide comment
Xiaowan Ke(vivo) shares comments of Dan (China Mobile and provides r01
Dario (Qualcomm) replies to Xiaowan and Dan and provides r02.
Hui (Huawei) provide r03
Xiaowan Ke(vivo) provides r04
Mukesh (MediaTek) proposes the removal of NOTE X and provides r05
Saso (Intel) comments on Option 1 and provides r06.
Xiaowan Ke(vivo) provides r07 and replies to Saso (Intel)
Mike (InterDigital) provides r08
Paul (Ericsson) object to any revision where UPF performs data buffering, i.e. r07, r05, r04, r03, r02.
Curt (Meta) can't accept AF providing 'Traffic Jitter range' is a done deal from S2 side.
Curt (Meta) provides r09.
Devaki (Nokia) provides r10 and supports.
Lei (Tencent) provides r11 and supports.
Chunshan (CATT) provides r12.
Hui (Huawei) replies to Chunshan.
Chunshan (CATT) responds to Hui.
Dario (Qualcomm) replies and provides r13 and r14.
Chunshan (CATT) provides r15.
jaehyeon (samsung) provides comments.
Chunshan (CATT) provides r16 .
Boren (OPPO) comments
Lei(Tencent) comments
Xiaowan Ke(vivo) object from r13 tor18 provides r19 based on r18
Chunshan (CATT) provides r20 and r21.
Chunshan (CATT) response to jaehyeon (samsung).
Xiaowan Ke(vivo) replies to Chunshan (CATT) : we OK with r20, object : r21, r13-r18.
Michele Zarri (Huawei) provides revision 22 (based on r21)
Xiaowan Ke(vivo) provides r23
Lei(Tencent) provides comments
Curt (Meta) has different views w.r.t jitter range interpretation from SA4.
Saso (Intel) comments on r23 and the need for further changes
Xiaowan(vivo) replies to Saso (Intel)
Xiaowan(vivo) provides r24 and replies to Saso (Intel)
Saso (Intel) provides r25
Curt (Meta) provides r26
Curt (Meta) asks Xiaowan (vivo) to clarify - what is one media unit?
Hui (Huawei) replies to Boren.
Xiaowan(vivo) replies to Curt (Meta)
Chunshan(CATT) comments to Hui (Huawei) .
Hui(Huawei) replies to Chunshan.
Curt (Meta) provides r27
Lei(Tencent) provides comments to Curt (Meta) and think an editorial correct to r27 is needed.
Saso (Intel) comments to Hui (Huawei) .
Lei(Tencent) provide r28 to correct the issue of r27
Hui (Huawei) replies to Saso .
Dario (Qualcomm) provides r30 based on r28 and asks to ignore r29.
Xiaowan Ke(vivo) provides comments and provides r31
Xiaowan Ke(vivo) provides r31 and object r30
==== Revisions Deadline ====
Curt (Meta) r27 needs to be opened with mac and not PC to see the right formatting. We can't accept any version that requires the AF to provide Traffic Jitter information.
Dario (Qualcomm) provides, after offline discussions, r32 that is r27 plus the deletion of the UPF implementation based example and no NOTE 4. Proposes to select this revision.
Paul (Ericsson) objects to all revisions provided before deadline except r0, r06, r21, r22, r30.
Curt (Meta) supports this version (r32) from Dario (QCOM).
Dario (Qualcomm) if no agreement, asks to take this in CC#3.
Hui (Huawei) supports r32
==== Final Deadline ====
Xiaowan Ke(vivo) provides r33 based on r32, since original assistance information for EOB from AF in r32 is misleading,update it and clear changes on changes
request to agree r33 in CC#4, i.e. with changes on top of R27:
1) remove the 'word' of 'Note4' (i.e. not the whole sentence)
2) remove: implementation method
3) add assistance information for EOB from AF
Lei(Tencent) can accept r32, also fine with r33.
Devaki (Nokia) comments
Xiaowan (vivo) replies to Devaki (Nokia)
Chunshan (CATT) comments that AS needs to be changed to AF.
>Devaki (Nokia) comments
>
Revised
9.19 S2-2209939 P-CR Approval 23.700-60: Key Issue #8: Evaluation and conclusion. Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, Tencent, Tencent Cloud, Vivo Rel-18 Revision of S2-2209159r27 + changes. Approved Approved
9.19 - - - KI9 evaluation & conclusion - - Docs:=7 -
9.19 S2-2208196 P-CR Approval 23.700-60: KI #9, New Conclusion: Key Issue #9 Conclusion. InterDigital Inc. Rel-18 Merged into (Covered by) S2-2208539 Boren (OPPO) provides comments that this paper has been suggested to be merged into S2-2208539 as suggested by rapporteur.
==== Revisions Deadline ====
Devaki (Nokia) comments that this paper shall be marked as NOTED or merged into 8539 as per rapporteur proposal. We have objection to this proposal as RAN2 has analyzed this approach provides no benefit.
Hui(Huawei) confirms this paper was merged into S2-2208539.
==== Final Deadline ====
Merged
9.19 S2-2208452 P-CR Approval 23.700-60: KI#9: Evaluation and Conclusion . MediaTek Inc., Apple Rel-18 Merged into (Covered by) S2-2208539 Guillaume (MediaTek Inc.) comments that the subject of this discussion is wrong (8542): it is commenting on 8452 instead .
LaeYoung (LGE) thinks that this pCR needs to be MERGED into 8539.
Hui (Huawei) agree with LaeYoung that this pCR is merged into 8539.
Jinhua (Xiaomi) provide comments, and 8542r01 (was not capture in the notes because of the wrong tdoc number)
Hui(Huawei) replies.
Dan (China Mobile) suggest to keep this paper merged into 8539
Jinhua(Xiaomi) replies to Dan, merged it into 8539 is OK.
Jinhua replies to Hui, merge is confirmed, thanks.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208539 P-CR Approval 23.700-60: KI#9, Evaluation and Conclusion. OPPO Rel-18 CC#3: r08 agreed. Revised to S2-2209940. Jinhua (Xiaomi) provides comments, and r01,
Guillaume (MediaTek Inc.) provides r02 (waiting for r01)
Dan (China Mobile) comment
Guillaume (MediaTek Inc.) comments
Jinhua (Xiaomi) provide the comments,
Dario (Qualcomm) comments and provides r03.
Dario (Qualcomm) provides r04 and asks to ignore r03.
Devaki (Nokia) supports r04 (this reflects our original version in 8552).
Jinhua (Xiaomi) replies to Devaki,
Jinhua (Xiaomi) replies to Dario,
Boren (OPPO) comments.
Hui (Huawei) asks whether SoH is needed.
Paul (Ericsson) objects to r0, r01, r02.
Boren (OPPO) replies to Hui (Huawei) and Guillaume (MediaTek Inc.) and provides r05.
Jinhua (Xiaomi) provides comments, and r06, to capture the compromise achieved ever.
Guillaume (MediaTek Inc.) ok with r06 - not r05.
Jinhua (Xiaomi) replies to Paul (Ericsson), and provides r07, to capture the suggestion.
Boren (OPPO) replies to Guillaume (MediaTek Inc.)
Dario (Qualcomm) is NOT OK with r06/07 an provides r08
Paul (Ericsson) provides comments and object to r07.
Guillaume (MediaTek Inc.) responds
Boren (OPPO) provides r09.
==== Revisions Deadline ====
Curt (Meta) can only accept r04 or no conclusion in this meeting.
Devaki (Nokia) shares the same view as Curt. We cannot accept any revision (or original version) except r04. We can accept only r04.
Dario (Qualcomm) can accepts r04 or r08. Others are not OK.
LaeYoung (LGE) can only accept r04 and objects to all other versions.
Jinhua (Xiaomi) replies to Paul (Ericsson), and provides r10, update to state that no new procedures or impacts on RAN.
Jinhua (Xiaomi) replies to Curt (Meta),
Jinhua (Xiaomi) replies to LaeYoung, pending or postpone the conclusion of KI#8 and KI#9, and find agreed content next meeting as your proposal, is fine for me. I'm neutral for combined the KIs discussion.
Jinhua (Xiaomi) replies to Devaki, postpone the conclusion of KI#8 and KI#9 is fine for me. I'm neutral for combined the KIs discussion.
Boren (OPPO) objects to r04.
Jinhua (Xiaomi) replies to Dario, suggest to go with r08+ one EN, 'Editor's Note: Other conclusions are FFS.', to move forward
Dan(China Mobile) object to r04 since this contain 'Refer to clause 8.y about conclusions for KI#8 for assistance parameters to be sent to NG-RAN for power savings.
' and put some observation for this KI discussion
Hui(Huawei) supports Dan.
Boren (OPPO) agree with Hui(Huawei)'s suggestion to approve evaluation part first, and proposes to go with r0+removing conclusion part.
Jinhua (Xiaomi) request this paper for CC#3,
Check if can go with r08+ one EN, 'Editor's Note: Other conclusions are FFS.', to move forward
Jinhua (Xiaomi) request this paper for CC#3,
Check if can go with r08+ one EN, 'Editor's Note: Other aspects are FFS.', to move forward
==== Final Deadline ====
Revised
9.19 S2-2209940 P-CR Approval 23.700-60: KI#9, Evaluation and Conclusion. OPPO, Xiaomi, China Mobile, Tencent Rel-18 Revision of S2-2208539r08. Approved Approved
9.19 S2-2208552 P-CR Approval 23.700-60: KI#9 Conclusion. Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2209159 Jinhua (Xiaomi) provides comments, all the comments were not captured in the ChairNotes, because of One '<' was missing. Confirm that 8552 is merged into 8539 for the discussion.
Dan(China Mobile) provides comments, this paper should be merged into 8539
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208831 P-CR Approval 23.700-60: Conclusion for KI#9. Xiaomi, China Mobile Rel-18 Merged into (Covered by) S2-2209159 Jinhua (Xiaomi) provides comments, merged 8831 into 8539 is OK,
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 S2-2208832 P-CR Approval 23.700-60: Evaluation for KI#9. Xiaomi, China Mobile Rel-18 Merged into (Covered by) S2-2209159 Jinhua (Xiaomi) provides comments, merged 8832 into 8539 is OK,
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.19 - - - Documents exceeding TU Budget - - Docs:=11 -
9.19 S2-2208195 P-CR Approval 23.700-60: KI #9, New Eval: Key Issue #9 Evaluation . InterDigital Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208193 P-CR Approval 23.700-60: KI #8, New Eval: Key Issue #8 Evaluation . InterDigital Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208217 P-CR Approval 23.700-60: Update according to the response SA WG4 LS. Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208682 P-CR Approval 23.700-60: Fix on solution #66 multi-modality support (KI #1 and #2). Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208826 P-CR Approval 23.700-60: XRM_KI#2Sol#2 Remove the ENs. Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208827 P-CR Approval 23.700-60: XRM_KI#2Sol#3 Remove the ENs . Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208828 P-CR Approval 23.700-60: XRM_KI#2Sol#66 Remove the ENs . Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208829 P-CR Approval 23.700-60: XRM_KI#3Sol#47 the Update of Measurement Description. Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208830 P-CR Approval 23.700-60: XRM_KI#4Sol#52 Remove the ENs . Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208833 P-CR Approval 23.700-60: XRM_KI#9Sol#75 Update the PCC Rules as Exist Mechanism . Xiaomi Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.19 S2-2208998 P-CR Approval 23.700-60: KI #3, Solution #43 update for clarification. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 - - - Study on Ranging based services and sidelink positioning (FS_Ranging_SL) - - Docs:=46 -
9.20 - - - Terminology - - Docs:=1 -
9.20 S2-2208250 P-CR Approval 23.700-86: Update terminology: Remove SL Positioning Server UE. Ericsson, Huawei, HiSilicon Rel-18 Noted Guillaume (MediaTek Inc.) proposes to note this document.
Richard (Ericsson) answering to MediaTek Inc.
Sherry (Xiaomi) comments and provides r01.
Xiaoyan Shi (Intel) comments on the SL Positioning Server UE's new function and has concerns on r01.
Sherry replies to Xiaoyan.
Richard (Ericsson) answering to Xiaomi and not support r01
Guillaume (MediaTek Inc.) responds to Xiaoyan
Guillaume (MediaTek Inc.) responds to Richard (Ericsson)
Sherry (Xiaomi) replies.
Richard (Ericsson) answering to Xiaomi and MediaTek Inc.
LiMeng (Huawei) replies and supports Richard (Ericsson).
LiMeng (Huawei) correct the wording in the last email.
Sherry (Xiaomi) replies to LM and Richard.
Sherry (Xiaomi) comments.
Richard (Ericsson) providing comments
Guillaume (MediaTek inc.) comments
==== Revisions Deadline ====
Sherry (Xiaomi) objects r00 and support r01.
Runze (Huawei) objects r01 and supports r00.
==== Final Deadline ====
Noted
9.20 - - - Solution of KI#2 - - Docs:=1 -
9.20 S2-2208205 P-CR Approval 23.700-86: KI#2 Update of Sol#29 to address the EN. Huawei, HiSilicon Rel-18 Not Handled LiMeng (Huawei) proposes to swap this document with S2-2208204, i.e., 8204 will be handled instead of 8205.
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 - - - Solution of KI#5 - - Docs:=5 -
9.20 S2-2208985 P-CR Approval 23.700-86: Update on Sol#31. Interdigital Rel-18 r03 agreed. Revised to S2-2209623. Lars (Sony) provides r01.
Jungje(Interdigital) respond to Lars(Sony)
Xiaoyan Shi (Intel) comments.
Walter Dees (Philips) provides comments
Jungje(Interdigital) responded to Xiaoyan(Intel) and provided r03
Xiaoyan Shi(Intel) comments.
Jungje(Interdigital) comments.
Xiaoyan Shi(Intel) is fine with r03.
==== Revisions Deadline ====
Jungje (Interdigital) responds to Walter(Philips)
Walter (Philips) responds to Jungje (Interdigital)
==== Final Deadline ====
Revised
9.20 S2-2209623 P-CR Approval 23.700-86: Update on Sol#31. Interdigital Rel-18 Revision of S2-2208985r03. Approved Approved
9.20 S2-2209110 P-CR Approval 23.700-86: KI#4 KI#5, Update of Solution #32 . Philips International B.V. Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.20 S2-2209149 P-CR Approval 23.700-86: TR 23.700-86: KI#5 Sol#6 update. Intel Rel-18 r01 agreed. Revised to S2-2209624. Walter Dees (Philips) provides comments
Xiaoyan Shi (Intel) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.20 S2-2209624 P-CR Approval 23.700-86: TR 23.700-86: KI#5 Sol#6 update. Intel Rel-18 Revision of S2-2209149r01. Approved Approved
9.20 - - - Solution of KI#6, KI#7 - - Docs:=3 -
9.20 S2-2208586 P-CR Approval 23.700-86: KI#2&6, Sol#10_Update the Ranging service exposure to UE over PC5. Vivo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.20 S2-2208453 P-CR Approval 23.700-86: KI#2 KI#6: MT-LR and MO-LR signalling for peer-to-peer SL Positioning and Ranging. MediaTek Inc. Rel-18 r02 agreed. Revised to S2-2209626. New solution has to be deprioritized Sherry (Xiaomi) provides r01
Walter Dees (Philips) provides r02
Guillaume (MediaTek Inc.) r02 ok
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.20 S2-2209626 P-CR Approval 23.700-86: KI#2 KI#6: MT-LR and MO-LR signalling for peer-to-peer SL Positioning and Ranging. MediaTek Inc. Rel-18 Revision of S2-2208453r02. Approved Approved
9.20 - - - Others Solutions - - Docs:=2 -
9.20 S2-2209088 P-CR Approval 23.700-86: Revision of Solution #19 for Addition of LMF Positioning Support . Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2209627. Sherry (Xiaomi) comments.
Hong (Qualcomm) replies to Sherry and provide r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.20 S2-2209627 P-CR Approval 23.700-86: Revision of Solution #19 for Addition of LMF Positioning Support . Qualcomm Incorporated Rel-18 Revision of S2-2209088r01. Approved Approved
9.20 - - - Evaluation & Conclusion - - Docs:=14 -
9.20 S2-2208207 P-CR Approval 23.700-86: KI#1 and KI#8: Evaluation and conclusion. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2209628. Deng Qiang (CATT) asks questions for clarifications.
Fei (OPPO) asks questions.
LiMeng (Huawei) responds and provides r01.
Walter Dees (Philips) comments.
Xiaoyan Shi (Intel) provides r02.
Deng Qiang (CATT) comments on Ranging QoS.
LiMeng (Huawei) replies to Deng Qiang (CATT).
Sherry (Xiaomi) provides r04. (r03 is also provided, but pls ignore r03)
Sherry (Xiaomi) replies to DQ.
==== Revisions Deadline ====
Jungje(Interdigital) comments.
Deng Qiang (CATT) accepts r04.
LiMeng (Huawei) is fine with r04 and replies to Jung Je (InterDigital).
==== Final Deadline ====
Revised
9.20 S2-2209628 P-CR Approval 23.700-86: KI#1 and KI#8: Evaluation and conclusion. Huawei, HiSilicon, Xiaomi Rel-18 Revision of S2-2208207r04. Approved Approved
9.20 S2-2208443 P-CR Approval 23.700-86: KI#7: Evaluation and conclusion . Samsung Rel-18 r06 agreed. Revised to S2-2209629. Lars (Sony) provides r01.
Hong (Qualcomm) asks for some clarifications.
LiMeng (Huawei) comments on r01.
Lars (Sony) responds.
David (Samsung) provides r02.
Lars (Sony) ask David to explain more.
David (Samsung) replies to Sony.
Sherry (Xiaomi) provides r03.
Hong (Qualcomm) comments.
Wen (vivo) comments.
Lars (Sony) comments.
Walter Dees (Philips) requests clarification.
Sherry (Xiaomi) provides r06.
==== Revisions Deadline ====
Lars (Sony) is ok with either r05 or r06, but prefer r05.
David (Samsung) prefers r06.
Sherry (Xiaomi) can only accept r06.
Lars (Sony) as said before it is fine to go with r06.
Wen (vivo) is fine to go with r06.
==== Final Deadline ====
Revised
9.20 S2-2209629 P-CR Approval 23.700-86: KI#7: Evaluation and conclusion . Samsung Rel-18 Revision of S2-2208443r06. Approved Approved
9.20 S2-2208484 P-CR Approval 23.700-86: KI#3: Overall Evaluation and Conclusions. CATT Rel-18 r05 agreed. Revised to S2-2209630. Wen (vivo) comments
Deng Qiang (CATT) provides r01.
Fei (OPPO) asks questions on r01.
Hong (Qualcomm) provides r02.
Deng Qiang (CATT) provides r03.
LiMeng (Huawei) provides r04.
Hong (Qualcomm) provides r05.
Xiaoyan Shi (Intel) comments.
Hong (Qualcomm) replies to Xiaoyan.
Deng Qiang (CATT) provides r06 and comments.
Fei (OPPO) comments on r06.
Hong (Qualcomm) replies to Deng Qiang.
==== Revisions Deadline ====
Hong (Qualcomm) replies to Fei.
Fei (OPPO) is ok with r06.
LiMeng (Huawei) prefers r05.
Deng Qiang (CATT) is fine with either r05 or r06.
Xiaoyan Shi (Intel) prefers r05.
==== Final Deadline ====
Revised
9.20 S2-2209630 P-CR Approval 23.700-86: KI#3: Overall Evaluation and Conclusion. CATT, Xiaomi Rel-18 Revision of S2-2208484r05. Approved Approved
9.20 S2-2208587 P-CR Approval 23.700-86: TR 23.700-86: Evaluation and conclusion on KI#6. Vivo, Sony Rel-18 r08 agreed. Revised to S2-2209631. LiMeng (Huawei) provides r01.
Lars (Sony) comment on r01.
Hong (Qualcomm) comment.
Lars (Sony) just to be clear we cannot agree on r01.
Wen (vivo) replies.
LiMeng (Huawei) replies.
Walter Dees (Philips) provides comments.
Wen (vivo) replies to Walter Dees (Philips) and provides r02.
Walter Dees (Philips) responds to Wen (Vivo).
Wen (vivo) responds to Walter Dees (Philips) and provides the r03.
Walter (Philips) responds to Wen (Vivo).
Lars (Sony) provides r04.
Walter (Philips) comments on r04.
Wen (vivo) provides r05 on top r03.
Lars (Sony) responds to Walter.
Lars (Sony) provides r06.
LiMeng (Huawei) provides r07 and comment on r06.
Lars (Sony) comments on r07.
LiMeng (Huawei) provides r08.
==== Revisions Deadline ====
Lars (Sony) is ok with r08.
Walter (Philips) can live with r08 under the assumption that this conclusion can be updated with additional scenarios in a next meeting.
Wen (vivo) can live with r08 as well.
==== Final Deadline ====
Revised
9.20 S2-2209631 P-CR Approval 23.700-86: TR 23.700-86: Evaluation and conclusion on KI#6. Vivo, Sony Rel-18 Revision of S2-2208587r08. Approved Approved
9.20 S2-2208715 P-CR Approval 23.700-86: KI#5: Evaluation and Conclusion. Sony Rel-18 r21 agreed. Revised to S2-2209680. Wen (vivo) provides r02.
Hong (Qualcomm) provides r01.
Lars (Sony) replies to Hong and Wen (vivo) and provides r03.
LiMeng (Huawei) provides r04.
Lars (Sony) provides r05.
David (Samsung) provides r06.
Lars (Sony) provides r07.
Jungje(Interdigital) provides r08.
Xiaoyan Shi (Intel) provides r09.
Wen (vivo) provides r10.
Lars (Sony) provides r11.
LiMeng (Huawei) provides r12.
Lars (Sony) provides r13.
Sherry (Xiaomi) provides r14.
Lars (Sony) responds to Sherry (Xiaomi) on r14 and provides r15.
Hong (Qualcomm) comments on r15.
Walter Dees (Philips) provides r16.
Wen (vivo) provides r17.
LiMeng (Huawei) replies to Hong.
Hong (Qualcomm) replies to LiMeng.
Lars (Sony) ask Wen (vivo) to provide r18 with change marks.
Wen (vivo) replies and provides r18 on top of R16.
Lars (Sony) comments and provides r19.
LiMeng (Huawei) provides r20.
LiMeng (Huawei) provides r21.
==== Revisions Deadline ====
Sherry (Xiaomi) responds Lars.
Sherry (Xiaomi) objects to all revisions except r14 and provides r22 in the draft folder.
Wen (vivo) objects to r22, r14 and any versions that removes the case where If Target UE is not in network coverage and does not have NAS connection with AMF, can accept r21 in the chairman note
Jungje(Interdigital) comments LiMeng(Huawei) on r21.
Lars (Sony) comments on r21.
Sherry replies to Wen (vivo).
LiMeng replies to Jung Je (InterDigital).
Lars (Sony) ask Sherry to re-check r21.
Wen (vivo) replies to Sherry.
Sherry (Xiaomi) replies to Lars (Sony).
Sherry (Xiaomi) replies to Wen.
Wen (vivo) replies to Sherry and keeps the original view that vivo objects to r22, r14 and any versions that removes the part where If Target UE is not in network coverage and does not have NAS connection with AMF, can accept r21.
Lars (Sony) replies to Sherry (Xiaomi).
Sherry objects any revision except r22 and r14 but may agree a new revision if the concern is removed.
Lars (Sony) remind Sherry that r22 was not submitted before revision deadline.
Sherry (Xiaomi) provides r23.
Sherry (Xiaomi) replies that r23 is provided on top of r21, with some small changes.
Wen (vivo) is ok with r23.
Lars (Sony) I can't agree to r23.
Sherry (Xiaomi) replies.
Lars (Sony) replies.
Sherry replies to Lars (Sony).
Lars (Sony) propose a WF
Wen (vivo) replies to Lars (Sony)
Sherry (Xiaomi) is fine with the texts proposed by Lars and the way forward.
Lars (Sony) let me study r23 one more time.
Lars (Sony) let's go with the following.
Wen (vivo) is ok with the process provided by Lars (Sony).
Sherry (Xiaomi) is fine with the texts provided by Lars (Sony).
Lars (Sony) WF: based on r21+ add In the third bullet from the end ',MO-LR,' + add in the last EN 'MT-LR'.
==== Final Deadline ====
Revised
9.20 S2-2209680 P-CR Approval 23.700-86: KI#5: Evaluation and Conclusion. Sony, Vivo Rel-18 Revision of S2-2208715r21. Approved Approved
9.20 S2-2209130 P-CR Approval 23.700-86: Evaluation and Conclusion for KI#4. Xiaomi Rel-18 CC#4: r10 agreed. Revised to S2-2209959. Hong (Qualcomm) provides r01.
LiMeng (Huawei) comments.
Wen (vivo) comments.
Lars (Sony) provides r02.
Jungje(Interdigital) comments Lars(Sony)
LaeYoung (LGE) comments.
Jingran (OPPO) provides comments.
Dimitris (Lenovo) requests clarification for the EN on the Ranging/Positioning Layer
Guillaume (MediaTek Inc.) provides r03
Sherry (Xiaomi) provides r04.
Walter (Philips) provides r05.
Runze (Huawei) provides r06.
Guillaume (MediaTek Inc.) provides r07 - r06 is not ok.
Sherry (Xiaomi) provides r08.
==== Revisions Deadline ====
LiMeng (Huawei) objects to r07 and r08, but is fine if we remove 'and will be aligned with RAN WGs' from EN in r08.
Guillaume (MediaTek Inc.) comments: r08 with LiMeng (Huawei) suggestion wrt EN: OK!
Sherry (Xiaomi) provides r09.
Guillaume (MediaTek Inc.): ok with r09!
Runze (Huawei) comments on r09, only accept if removing 'SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or' in the bullet 'A SL Positioning Server UE can be discovered and selected for SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or result calculation for the case of partial coverage and out of coverage'
Guillaume (MediaTek Inc.) recommends to agree with Andy (Vice-Chair) summary as proposed by Huawei: r08 + change EN to 'Editor's Note: Whether the SL Positioning Server functionalities can be provided by a stand-alone SL Positioning Server UE is FFS'
==== Final Deadline ====
Sherry (Xiaomi) recommends to agree with Andy (Vice-Chair) summary as proposed by Huawei: r08 + change EN to 'Editor's Note: Whether the SL Positioning Server functionalities can be provided by a stand-alone SL Positioning Server UE is FFS'
Runze (Huawei) replies to Sherry (Xiaomi).
Runze (Huawei) can only agree r08 + change EN to 'Editor's Note: Whether the SL Positioning Server functionalities can be provided by a stand-alone SL Positioning Server UE is FFS' + removing 'SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or'.
Sherry (Xiaomi) propose to agree r08 + change EN to 'Whether the SL Positioning Server functionalities can support more functionalities, e.g. SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling, in addition to result calculation if FFS.' + removing 'SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or'.
Sherry (Xiaomi) propose to agree r08 + change EN to 'Whether the SL Positioning Server functionalities can support more functionalities, e.g. SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling, in addition to result calculation is FFS.' + removing 'SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or'.
Runze (Huawei) supports Sherry (Xiaomi)'s proposal to agree r08 + change EN to 'Whether the SL Positioning Server functionalities can support more functionalities, e.g. SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling, in addition to result calculation is FFS.' + removing 'SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling and/or'.
Guillaume (MediaTek Inc.) thanks Runze (Huawei) and Sherry (Xiaomi) - we support Sherry proposal as well.
Sherry (Xiaomi) provides r10.
Revised
9.20 S2-2209959 P-CR Approval 23.700-86: Evaluation and Conclusion for KI#4. Xiaomi Rel-18 Revision of S2-2209130r10. Approved Approved
9.20 S2-2209148 P-CR Approval 23.700-86: TR 23.700-86: KI#2 Evaluation and conclusion. Intel Rel-18 CC#4: r08 agreed. Revised to S2-2209960. Deng Qiang (CATT) asks questions for clarifications.
Fei (OPPO) comments.
Lars (Sony) comments.
Hong (Qualcomm) comments.
Xiaoyan Shi (Intel) provides R01.
Wen (vivo) provides R02.
LiMeng (Huawei) provides R03.
Sherry (Xiaomi) provides r04.
Xiaoyan Shi (Intel) provides r05.
LiMeng (Huawei) provides r06.
Limeng (Huawei) provides r07.
==== Revisions Deadline ====
Jungje(Interdigital) comments on r07
Runze (Huawei) replies to Jungje(Interdigital).
Jungje(Interdigital) responds to Runze(Hauwei)
Sherry (Xiaomi) comments.
Sherry (Xiaomi) objects to r06 and r07, and proposes a way fwd.
Xiaoyan Shi (Intel) replies to Sherry (Xiaomi).
Runze (Huawei) supports Xiaoyan Shi (Intel)'s view, suggest to agree r06.
==== Final Deadline ====
Runze (Huawei) agrees to approve r07+combine the 3rd bullet of the last paragraph into the first bullet (i.e. remove 'Otherwise, existing Assistant UE continues to be used' and add the 'existing Assistant UE continues to be used' after 'If the assistant UE is still required' + remove 'by the Target UE' of the 1st bullet
Sherry (Xiaomi) thanks Runze for the compromise.
Sherry (Xiaomi) provides r08 based on the agreement.
Revised
9.20 S2-2209960 P-CR Approval 23.700-86: TR 23.700-86: KI#2 Evaluation and conclusion. Intel Rel-18 Revision of S2-2209148r08. Approved Approved
9.20 - - - LS Out - - Docs:=3 -
9.20 S2-2208487 LS OUT Approval [DRAFT] LS on transport of RSPP CATT Rel-18 Merged into (Covered by) S2-2209134 Guillaume (MediaTek Inc.) proposes to merge 8487 with 9134
Hong (Qualcomm) objects to this LS draft.
Sherry (Xiaomi) proposes to merge this paper into 9134.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.20 S2-2209134 LS OUT Approval [DRAFT] LS on RAN dependency for Ranging/Sidelink Positioning Xiaomi Rel-18 CC#4: r18 agreed. Revised at CC#4 to S2-2209961. Guillaume (MediaTek Inc.) provides r01
Sherry (Xiaomi) provides r02.
Hong (Qualcomm) provides r03.
Wen (vivo) comments.
Hong (Qualcomm) replies to Wen.
Lars (Sony) provides r04.
Deng Qiang (CATT) comments.
Sherry (Xiaomi) replies to Wen.
Sherry (Xiaomi) replies.
Xiaoyan Shi (Intel) comments.
Sherry (Xiaomi) provides r05.
Lars (Sony) responds to Sherry and does not agree to r05.
Sherry (Xiaomi) replies to Lars.
Sherry (Xiaomi) provides r06.
Leo (Deutsche Telekom) provides r07.
Walter (Philips) provides r08
Sherry (Xiaomi) is fine with the rewording in r07.
Hong (Qualcomm) provides r09.
Sherry (Xiaomi) provides r10.
Xiaoyan Shi (Intel) provides r11.
Walter (Philips) responds to Hong (Qualcomm) and provides r12.
==== Revisions Deadline ====
Hong (Qualcomm) comments.
Runze (Huawei) provides r13, and objects to all other versions.
Sherry objects r13 provided by Runze (Huawei), and expects Huawei to be reasonable for the issue of SL Positioning Sever UE, which is already defined and described in several solutions and in the architecture assumptions.
Hong (Qualcomm) provides r14.
Guillaume (MediaTek Inc.) objects to r13
Guillaume (MediaTek Inc.) objects to r14 (which is based on r13), and to r15 in the rev folder. Supports R16 is ok (still waiting for the email though...)
(r16 contains Hong (Qualcomm) changes from r14)
Guillaume (MediaTek Inc.) provides ref to r15 and r16 (neither are from us) on the server (but missing the emails).
==== Final Deadline ====
Sherry (Xiaomi) provides both r15 and r16, and prefers r16.
Sherry (Xiaomi) provides r17.
Runze (Huawei) provides r18, reword the Q7 to: A SL Positioning Server UE can be discovered and selected for result calculation for the case of partial coverage and out of coverage, in case a constrained UE is not able to support all SL Positioning/Ranging features. Whether the SL Positioning Server functionalities can support more functionalities, e.g. SL Positioning/Ranging method determination, operation coordination, resource coordination and scheduling, in addition to result calculation is FFS. SA2 would like to understand whether this is reasonable from RAN perspective.
Sherry (Xiaomi) is fine with r18.
Revised
9.20 S2-2209961 LS OUT Approval LS on RAN dependency for Ranging/Sidelink Positioning SA WG2 Rel-18 Revision of S2-2209134r18. Approved Approved
9.20 - - - Discussion - - Docs:=1 -
9.20 S2-2208486 DISCUSSION Discussion Way-forward proposal on transport of RSPP. CATT Rel-18 Noted Guillaume (MediaTek Inc.) comments
Sherry (Xiaomi) comments.
Hong (Qualcomm) comments and does not agree with the statements of the discussion paper.
Wen (vivo) comments.
Hong (Qualcomm) comments.
Deng Qiang (CATT) comments.
Jingran(OPPO) provides comments.
LiMeng (Huawei) agrees with Jingran(OPPO), and suggests to move forward with PC5-S.
Sherry(Xiaomi) comments.
Walter Dees (Philips) comments to Hong (Qualcomm)
Walter (Philips) responds to Hong (Qualcomm)
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.20 - - - Documents exceeding TU Budget - - Docs:=16 -
9.20 S2-2208485 P-CR Approval 23.700-86: KI#4: Overall Evaluation and Conclusions. CATT Rel-18 Not Handled Can be merged into S2-2209130 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208588 P-CR Approval 23.700-86: TR 23.700-86: Evaluation and conclusion on KI#2. Vivo Rel-18 Not Handled Can be merged into S2-2209148 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208589 P-CR Approval 23.700-86: TR 23.700-86: Evaluation and conclusion on KI#5. Vivo Rel-18 Not Handled Can be merged into S2-2208715 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208590 P-CR Approval 23.700-86: TR 23.700-86: Evaluation and conclusion on KI#7. Vivo Rel-18 Not Handled Can be merged into S2-2208443 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209080 P-CR Approval 23.700-86: KI#5: Evaluation and Conclusion for KI#5. Huawei, HiSilicon Rel-18 Not Handled Can be merged into S2-2208715 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208454 P-CR Approval 23.700-86: Correction to the definition of SL Positioning Server UE. MediaTek Inc. Rel-18 Not Handled Guillaume (MediaTek Inc.) provides r01 (merger of 8454, 9131, 9137)
Sherry (Xiaomi) clarifies that this paper is one of the unhandled papers. :)
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208204 P-CR Approval 23.700-86: KI#5, Sol#20_Update to support multiple Located UEs case, partial network coverage and located UE discovery for specific coordinate systems . Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209625. Can be swapped with any Huawei terminology & Solution update paper that is to be handled LiMeng (Huawei) proposes to swap this document with S2-2208205, i.e., 8204 will be handled instead of 8205.
Sherry (Xiaomi) is fine to handle this Tdoc instead of S2-2208205, but we need to check with Chairman's view.
Lars (Sony) comments on r00.
Xiaoyan Shi (Intel) asks question for clarification.
Runze (Huawei) replied to Xiaoyan Shi (Intel) and Lars (Sony), provides r01.
==== Revisions Deadline ====
Xiaoyan Shi (Intel) replied to Runze.
==== Final Deadline ====
Revised
9.20 S2-2209625 P-CR Approval 23.700-86: KI#5, Sol#20_Update to support multiple Located UEs case, partial network coverage and located UE discovery for specific coordinate systems . Huawei, HiSilicon Rel-18 Revision of S2-2208204r01. Approved Approved
9.20 S2-2209150 P-CR Approval 23.700-86: Sol#7 update: Network assisted UE Sidelink Positioning capability. Intel Rel-18 Not Handled Can be swapped with any Intel terminology & Solution update paper that is to be handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208251 P-CR Approval 23.700-86: KI#5, Sol#27: Update to add LMF reselection factors. Ericsson Rel-18 Not Handled Can be swapped with any Ericsson terminology & Solution update paper that is to be handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2208208 P-CR Approval 23.700-86: KI#4, Sol#3 Update: adding RSPP procedure. Huawei, HiSilicon Rel-18 Not Handled Can be swapped with any Huawei terminology & Solution update paper that is to be handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209099 P-CR Approval 23.700-86: Sol#12: Update to address EN . Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209137 P-CR Approval 23.700-86: KI#2&3&4&5&6&7, Solution#26: Update to clarify SL Positioning Server UE functionalities. Xiaomi Rel-18 Not Handled Can be merged into S2-2208454 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209132 P-CR Approval 23.700-86: KI#6, Solution#25: Update to consider SL Positioning Server UE. Xiaomi Rel-18 Not Handled Can be merged into S2-2209088 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209133 P-CR Approval 23.700-86: KI#2, Solution#16&Solution#29: Update to clarify the impact to RAN. Xiaomi Rel-18 Not Handled Can be merged into S2-2208205 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.20 S2-2209131 P-CR Approval 23.700-86: Update to Terminology. Xiaomi Rel-18 Not Handled Can be merged into S2-2208454 ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 - - - Study on System Support for AI/ML-based Services (FS_AIMLsys) - - Docs:=78 -
9.21 - - - Incoming LSs - - Docs:=5 -
9.21 S2-2208109 LS In Action LS from SA WG4: LS on User plane solution for 5GC information exposure to UE SA WG4 (S4-220846) Rel-18 Revision of Postponed S2-2205451 from S2#152-e. Response drafted in S2-2209206. Final response in S2-2209910 Zhang (Ericsson) suggest to send a LS back to SA4
Yannick (Nokia): Nokia notes there are two incoming LSs from SA4 on the same topic of 5GC information exposure to UE, S2-2208109 and S2-2208156. We could note S2-2208156 and keep S2-2208109 open for any reply we may wish to provide to SA4 on the status for KI#2 conclusions.
Jungshin (Samsung) supports to send an LS to SA4 and SA3 replying to S2-2208109, and suggests to note other related LSs, S2-2208110 and S2-2208156.
Malla (NTT DOCOMO) We agree to send a LS with KI#2 status, rapporteur can request the LS_reply number in CC#1.
Mehrdad (Mediatek Inc.) also agrees with the suggestion that one LS to stay open for a possible reply but to note the rest.
LaeYoung (LGE) also supports to send reply LS to SA4 and SA3 to let them know KI#2 study outcome.
Jingran (OPPO) provides a draft LS reply to the 2208109
Yannick (Nokia): Nokia provides a few revisions suggestions to the draft LS out.
LaeYoung (LGE) comments to draft version of 9206 (Reply LS).
Malla (NTT DOCOMO) provided comment.
Jingran(OPPO) replies to the comments.
Replied to
9.21 S2-2209206 LS OUT Approval [DRAFT] Reply LS on User plane solution for 5GC information exposure to UE OPPO Rel-18 Created at CC#1. Response to S2-2208109. r02 agreed. Revised to S2-2209910. Jingran(OPPO) provides r01 and put r00 and r01 in the revision folder.
Mehrdad (Mediatek Inc.) is fine with r01
==== Revisions Deadline ====
LaeYoung (LGE) is also OK with r01.
Jungshin (Samsung) is ok with r01.
Malla (NTT DOCOMO) agrees with r01, and we suggest also attaching S2-2208659 pCR.
Yannick (Nokia): Nokia supports the proposal from NTT DOCOMO to attach conclusion related pCR to the LS.
LaeYoung (LGE) provides r02 mentioning the KI#2 conclusion pCR.
Mehrdad (Mediatek Inc.) is ok either with r02 suggested by LGE or with r01 + final version of S2-2208659 attached.
LaeYoung (LGE) answers to Mehrdad (Mediatek Inc.) that revision of LS Out is allowed after revision deadline according to guidance from SA2 leadership.
Jingran(OPPO) agree the r02
==== Final Deadline ====
Revised
9.21 S2-2209910 LS OUT Approval Reply LS on User plane solution for 5GC information exposure to UE SA WG2 Rel-18 Revision of S2-2209206r02. Approved Approved
9.21 S2-2208110 LS In Action LS from SA WG3: LS reply on 5GC information exposure to UE SA WG3 (S3-221621) Rel-18 Revision of Postponed S2-2205455 from S2#152-e. Noted Zhang (Ericsson) suggest to NOTE the LS
Jungshin (Samsung) supports to note the LS.
Juan Zhang (Qualcomm) supports to note the LS as well.
Noted
9.21 S2-2208156 LS In Action LS from SA WG4: Reply LS to SA2 on 5G Core Information Exposure to UE via DCAF Solution SA WG4 (S4-221123) Rel-17 Noted Yannick (Nokia): Nokia notes there are two incoming LSs from SA4 on the same topic of 5GC information exposure to UE, S2-2208109 and S2-2208156. We suggest to note S2-2208156 and keep S2-2208109 open for any reply we may wish to provide to SA4 on the status for KI#2 conclusions.
Jungshin (Samsung) supports to note the LS.
Juan Zhang (Qualcomm) also supports to note the LS.
Mehrdad (Mediatek Inc.) also agrees with the suggestion that one LS to stay open for a possible reply but to note the rest.
Noted
9.21 - - - General Architecture Principles - - Docs:=1 -
9.21 S2-2208570 P-CR Approval 23.700-80: Conclusion for the General Architecture Principles . Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson Rel-18 CC#3: Noted Basis evaluation/conclusion document. R14? Tricci (OPPO) proposed r03 for OPPO's comment on the General Architecture Principles to limit the new NF for FL operation only.
Tricci (OPPO) moves BOTH r01 (Ericsson) and r02 (OPPO) into the draft/revision folder per SA2 chair's instructions
Tricci (OPPO) clarifies the rapporteur proposed merge revision is r02 for tdocs 8233 (from Ericsson), 8430 (from Samsung), 9188 (from OPPO, Oracle), 9183 (from InterDigital) to be merged into this 8570 (from QC et al)
Tricci (OPPO) submits the merged revision for tdocs 8233 (from Ericsson), 8430 (from Samsung), 9188 (from OPPO, Oracle), 9183 (from InterDigital) to be merged into this 8570 (from QC et al)
Zhang (Ericsson) provides r01
Yannick (Nokia): Nokia provides comments and r04.
David (Samsung) comments on Nokia's proposal
Tricci (OPPO) thanks Yannick (Nokia) feedback and provide r06. OPPO cannot accept r04. Please ignore r05 uploaded by OPPO by mistake.
Juan Zhang (Qualcomm) provides comments
Yannick (Nokia): Nokia replies to Samsung.
David (Samsung) replies to Nokia
Malla (NTT DOCOMO) provided comments.
Tricci (OPPO) would like to respond to Juan (Qualcomm) inline below.
Tricci (OPPO) responds to Malla (NTT DOCOMO) for his question for the justification of new NF for this feature.
Tricci (OPPO) would like to respond to Nokia's questions what are the major significant architecture impacts towards NWDAF if extending NWDAF as the anchor NF to assist member selections for AI/ML operation.
David (Samsung) wonders if Nokia is planning to address Samsung's arguments against NWDAF as NF to provide assistance for FL by means other than statistics/predictions on this thread, shared almost 24h ago.
Juan Zhang (Qualcomm) provides comments on other aspects than 'dedicated NF'.
Zhang (Ericsson) provides comment
Malla (NTT DOCOMO) comments on aspects rather than 'Dedicated new NF'
Tricci (OPPO) responds to Malla (NTT DOCOMO) comments
David (Samsung) replies to Ericsson
Juan Zhang (Qualcomm) provides r07.
Yannick (Nokia): Nokia comments on r07.
David (Samsung) provides comments on r07.
Yannick (Nokia): Nokia comments on Samsung's point regarding principle and dedicated NF discussion.
Tricci (OPPO) would like to comments on r07 and responds to Yannick (Nokia) and Juan (Qualcomm)
Zhang (Ericsson) response to David (Samsung)
Zhang (Ericsson) provides r08
Tricci (OPPO) has fundamental questions to Zhang (Ericsson)
Tricci (OPPO) responds to Zhang (Ericsson) and would like to keep AP#4.
Yannick (Nokia): Nokia comments on principles #4 and #7. In their current form, they are not acceptable to us.
Tricci (OPPO) responds to Yannick (Nokia).
David (Samsung) replies back to Ericsson
Juan Zhang (Qualcomm) provides comments on principle #4.
Tricci (OPPO) thanks Juan Zhang (Qualcomm) for the kind acceptance of the motivation of AP#4. OPPO provides r09 with an other suggested wordings. In addition, OPPO restore AP#6 with revised descriptions for the support for dedicated NF for the AIML assistance operation.
Yannick (Nokia): Nokia replies to OPPO.
Tricci (OPPO) thanks Yannick (Nokia) provides responses.
Tricci (OPPO) would like to respond to Yannick (Nokia) question.
Zhang (Ericsson) provide r10
Tricci (OPPO) thanks Zhang (Ericsson) for r10 and happily support this.
Yannick (Nokia): Nokia provides r11.
Tricci (OPPO) thanks Yannick (Nokia) for the rewordings for AP#4 and AP#7. But OPPO was not part of the 'we' that Nokia has referred.
David (Samsung) provides r12
Juan Zhang (Qualcomm) provides r13.
David (Samsung) provides r14.
==== Revisions Deadline ====
Mehrdad (Mediatek Inc.) comments on r14
David (Samsung) confirms the r14 zipped file was corrupt; re-uploads it in the drafts folder.
Zhang (Ericsson) propose to go for r11, but can live with r13 and r14, object all the other revisions
Wang Yuan (Huawei) accepts r13, objects r14.
Yannick (Nokia): Nokia supports going forward with r11. We cannot accept r14 nor r12.
Juan Zhang (Qualcomm) replies to Yannick (Nokia)
Juan Zhang (Qualcomm) objects r12 and r14, we can support r11, or r13, r15 is also OK which uploaded in draft folder based on r13.
David (Samsung) can live with r13 only if there's a minor wording change as a compromise, see r15
David (Samsung) objects to r11 and late r15 as provided by Qualcomm. We provide r16 with one word on top of r15
Juan Zhang (Qualcomm) objects r16.
David (Samsung) replies to Qualcomm.
Juan Zhang (Qualcomm) replies to David (Samsung).
==== Final Deadline ====
Juan Zhang (Qualcomm) provides r17 and askes feedback.
David (Samsung) thanks Qualcomm and confirms r17 is OK for us.
Noted
9.21 - - - KI#1: Monitoring of network resource utilization for support of Application AI/ML operations - - Docs:=2 -
9.21 S2-2208671 P-CR Approval 23.700-80: TR 23.700-80 KI#1: Updated evaluation and conclusion for KI#1. OPPO, Samsung, CATT Rel-18 r11 agreed. Revised to S2-2209911. Basis evaluation/conclusion document Tricci (OPPO) moves r01 of 8671 (from OPPO, Samsung, CATT) rapporteur proposed revision merger with Qualcomm to draft/revision folder per SA2 Chair instructions
Tricci (OPPO) provides rapporteur merged r01 to merge 8571 (from Qualcomm) into this 8671 (from OPPO, Samsung, CATT).
Yannick (Nokia): Nokia provides r02.
Tricci (OPPO) thanks Yannick (Nokia) kind checking and provides r03 to add the missing text from Qualcomm's 8571.
David (Samsung) provides r04.
Juan Zhang (Qualcomm) provides r05.
Belen (Ericsson) provides r06
David (Samsung) provides r07
Tricci (OPPO) request clarifications from Belen (Ericsson) to justify the removal of the service trigger of Group-MBR monitoring via Nnef_AFInfluenceTrafficRouting.
Juan Zhang (Qualcomm) can not agree with r07.
David (Samsung) provides r08, objects to r05 and r06.
Juan Zhang (Qualcomm) provides r09.
David (Samsung) can live with r09.
Yannick (Nokia): Nokia provides r10.
David (Samsung) is OK with r10, provides comments to Nokia.
Belen (Ericsson) is okay with r10, replies to OPPO again, same view as in previous meetings
Tricci (OPPO) would like to assure to Belen (Ericsson) and promises to work together with Ericsson during the normative phase to determine the proper AF service trigger for the Group MBR
Yannick (Nokia): Nokia provides r11.
David (Samsung) can live with r11, comments.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209911 P-CR Approval 23.700-80: TR 23.700-80 KI#1: Updated evaluation and conclusion for KI#1. OPPO, Samsung, CATT Rel-18 Revision of S2-2208671r11. Approved Approved
9.21 - - - KI#2: 5GC Information Exposure to UE - - Docs:=16 -
9.21 S2-2208659 P-CR Approval 23.700-80: TR 23.700-80: Conclusion for KI#2. OPPO, LG Electronics, Ericsson, MediaTek, Samsung Rel-18 r03 agreed. Revised to S2-2209912, merging S2-2209181 Basis conclusion document Yannick (Nokia): Nokia provides r01.
Juan Zhang (Qualcomm) provides r02.
Malla (NTT DOCOMO) provides r03.
Juan Zhang (Qualcomm) is OK with r03.
Susan (Huawei) provides r04.
LaeYoung (LGE) objects to r04 and proposes to go with r03.
Malla (NTT DOCOMO) objects to r04 and proposes to go with r03.
Zhang (Ericsson) propose to go with r03
Susan (Huawei) replies and is ok to go with r03 for this meeting.
Mehrdad (Mediatek Inc.) is OK with r03 but objects to r04
==== Revisions Deadline ====
Jungshin (Samsung) is ok with r03 and object to r04.
Yannick (Nokia): Nokia supports going forward with r03.
==== Final Deadline ====
Revised
9.21 S2-2209912 P-CR Approval 23.700-80: TR 23.700-80: Conclusion for KI#2. OPPO, LG Electronics, Ericsson, MediaTek, Samsung Rel-18 Revision of S2-2208659r03, merging S2-2209181. Approved Approved
9.21 S2-2208614 P-CR Approval 23.700-88: TR 23.700-80: Evaluation updated for KI#2. OPPO Rel-18 Merged into S2-2209913 LaeYoung (LGE) comments that this pCR can be marked as MERGED into 9097.
Jungshin (Samsung) supports the MERGE into 9097.
Jingran(OPPO) agree and confirm this pCR has already merged into 9097.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2209097 P-CR Approval 23.700-80: Update on evaluation of KI#2. Samsung Rel-18 r04 agreed. Revised to S2-2209913, merging S2-2208614 Basis evaluation document Yannick (Nokia): Nokia provides comments. Also can we assume this contribution will take onboard changes from S2-2208614?
Jingran(OPPO) provides r01 to merge 8614 into the 9097
Jungshin (Samsung) provides r02.
Susan (Huawei) provides r03.
Mehrdad (Mediatek Inc.) provides r04.
==== Revisions Deadline ====
Jungshin (Samsung) is ok with r04.
==== Final Deadline ====
Revised
9.21 S2-2209913 P-CR Approval 23.700-80: Update on evaluation of KI#2. Samsung, OPPO Rel-18 Revision of S2-2209097r04, merging S2-2208614. Approved Approved
9.21 S2-2209181 P-CR Approval 23.700-80: Conclusion for key issue#2. Xiaomi Rel-18 Merged into S2-2209912 LaeYoung (LGE) proposes to MERGE this pCR to S2-2208659.
Jungshin (Samsung) proposes to merge the pCR with S2-2208659.
Malla (NTT DOCOMO) objects r00 and proposes to MERGE this pCR to S2-2208659.
Jianning (Xiaomi) is ok to merge into 8659 as suggested
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208240 P-CR Approval 23.700-80: KI#2, Sol#30: Update: AI/ML Translator (AI/ML-T) for 5GC Information Exposure to UE. Ericsson Rel-18 r03 agreed. Revised to S2-2209914. Yannick (Nokia): Nokia provides comments.
Jungshin (Samsung) provides comments
Mehrdad (Mediatek Inc.) asks for a few clarifications.
Zhang (Ericsson) provide r01
Mehrdad (Mediatek Inc.) provides r02.
Zhang (Ericsson) provides r03
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209914 P-CR Approval 23.700-80: KI#2, Sol#30: Update: AI/ML Translator (AI/ML-T) for 5GC Information Exposure to UE. Ericsson Rel-18 Revision of S2-2208240r03. Approved Approved
9.21 S2-2208447 P-CR Approval 23.700-80: KI#2, Sol#2 Update: User Plane solution for 5GC information exposure to UE. MediaTek Inc. Rel-18 Merged into S2-2209915 Wang Yuan (Huawei) provides comments.
Yannick (Nokia): Nokia provides comments.
Jungshin (Samsung) provides comments
Juan Zhang (Qualcomm) provides comments
Mehrdad (Mediatek Inc.) suggests either 08447 or 08593 threads to be used as the baseline for further discussions and replies to Huawei, Nokia, Samsung, Qulacomm.
Ulises Olvera (InterDigital Inc.) provides comments.
Jingran(OPPO) provides comments.
Mehrdad (Mediatek Inc.) replies to Qualcomm.
Mehrdad (Mediatek Inc.) replies to InterDigital and OPPO.
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek Inc.).
Mehrdad (Mediatek Inc.) replies to InterDigital.
Jingran(OPPO) comments.
Jungshin (Samsung) provides comments.
Mehrdad (Mediatek Inc.) replies to Samsung.
Jungshin (Samsung) thanks Mehrdad (MediaTek) for clarification and asks further questions.
Mehrdad (Mediatek Inc.) proposes to mark this PCR as merged into 8593r03.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208593 P-CR Approval 23.700-80: KI#2: Clean up of solution#2. Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2209915, merging S2-2208447 and S2-2209186 Mehrdad (Mediatek Inc.) suggests either 08447 or 08593 threads to be used as the baseline for further discussions and requests some clarifications on 08593
Juan Zhang (Qualcomm) replies to Mehrdad (Mediatek.Inc)
Mehrdad (Mediatek Inc.) provides r01.
Juan Zhang (Qualcomm) provides r02.
Juan Zhang (Qualcomm) provides r03
Mehrdad (Mediatek Inc.) clarifies that r03 provided by MediaTek Inc. not Qualcomm.
Juan Zhang (Qualcomm) is OK with r03.
==== Revisions Deadline ====
Jungshin (Samsung) can live with r03.
Mehrdad (Mediatek Inc.) is ok with r03 and r01 but objects to the rest of revisions and original version.
Ulises Olvera (InterDigital Inc.) agrees to proceed with 8593r03, and notes that there's still some work to be done. E.g., further details of how the AIML policy is used by the DEC
==== Final Deadline ====
Revised
9.21 S2-2209915 P-CR Approval 23.700-80: KI#2: Clean up of solution#2. Qualcomm Incorporated, MediaTek Inc., InterDigital Inc. Rel-18 Revision of S2-2208593r03, merging S2-2208447 and S2-2209186. Approved Approved
9.21 S2-2208694 P-CR Approval 23.700-80: Update of Solution #8. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.21 S2-2208710 P-CR Approval 23.700-80: KI#2, Sol#2: Updates of network consent. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209916. Jungshin (Samsung) provides comments
Juan Zhang (Qualcomm) provides comments
Mehrdad (Mediatek Inc.) wonders what is the role of DCAF here. At least, this should be changed to IEAF to align with the rest of solution #2.
Wang Yuan (Huawei) replies to Jungshin (Samsung), Juan Zhang (Qualcomm) and Mehrdad (Mediatek Inc.), and provides r01.
Mehrdad (Mediatek Inc.) provides r02.
Wang Yuan (Huawei) replies to Mehrdad (Mediatek Inc.) and provides r03.
==== Revisions Deadline ====
Jungshin (Samsung) is ok with r03
Mehrdad (Mediatek Inc.) is ok with r03 and r02 but objects to the rest of revisions and original version.
==== Final Deadline ====
Revised
9.21 S2-2209916 P-CR Approval 23.700-80: KI#2, Sol#2: Updates of network consent. Huawei, HiSilicon Rel-18 Revision of S2-2208710r03. Approved Approved
9.21 S2-2209102 P-CR Approval 23.700-80: Update on Solution #31. Samsung Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.21 S2-2209186 P-CR Approval 23.700-80: KI#2, Sol#2: Update: User Plane solution for 5GC information exposure to UE. InterDigital Inc. Rel-18 Merged into S2-2209915 Jungshin (Samsung) provides comments
Mehrdad (Mediatek Inc.) requests several clarifications and suggests either 08447 or 08593 threads to be used as the baseline for further discussions.
Ulises Olvera (InterDigital Inc.) replies to Jungshin (Samsung) and provides r01 to address his comments.
Ulises Olvera (InterDigital Inc.) replies to Mehrdad (Media Tek Inc.) and provides to r02 to address his comments.
Mehrdad (Media Tek Inc.) can not agree with original version, r01 or r02.
Juan Zhang (Qualcomm) provides comments.
Ulises Olvera (InterDigital Inc.) replies to Juan (Qualcomm)
Jungshin (Samsung) asks for clarification
Mehrdad (Mediatek Inc.) requests to mark this PCR as merged into 8593r03 or noted.
==== Revisions Deadline ====
Jungshin (Samsung) thanks Ulises (InterDigital) for the clarification and is ok with r03.
Ulises Olvera (InterDigital Inc.) agrees with the proposal to merge onto 8593r03, and notes that there's still some work to be done in 8593r03. E.g., further details of how the AIML policy is used by the DEC
==== Final Deadline ====
Merged
9.21 - - - KI#3: 5GC Information Exposure to authorized 3rd party for Application Layer AI/ML Operation - - Docs:=9 -
9.21 S2-2208406 P-CR Approval 23.700-80: KI#3, Updates to evaluation and conclusions. Samsung, OPPO, CATT Rel-18 r17 agreed. Revised to S2-2209917, merging S2-2208241, S2-2208307, S2-2208619, S2-2208693, S2-2209021 and S2-2208709 Basis evaluation/conclusion document Wang Yuan (Huawei) found that the evaluations of Solution#8 is omitted thus provides r01.
Tingyu (Samsung) provides r02 by merging 8241, 8307, 8619, 8693 and 9021 with 8406 according to the chair's notes, and suggests using this email thread to discuss the evaluations and conclusions of KI#3.
Wang Yuan (Huawei) objects to the principle in r02 that RAN node provides available UL/DL data rate to the AF, and provides r03.
Zhang (Ericsson) raise concerns for the paper
Yannick (Nokia): Nokia provides r04.
Vivian(vivo) provides r05 and adds vivo as co-signer.
Juan Zhang (Qualcomm) provides comments
Malla (NTT DOCOMO) provides comments
Tingyu (Samsung) replies and provides r06.
Yannick (Nokia): Nokia replies to Samsung.
Mehrdad (Mediatek Inc.) comments
Zhang (Ericsson) provide comment to r06
Wang Yuan (Huawei) proposes to merge user consent part of S2-2208709 into S2-2208406, provides r07 and cosigns this pCR.
Ellen (Google) provides r08 to merge 9021 and cosigns this pCR.
Zhang (Ericsson) provide r09 and co-sign
Tingyu (Samsung) can live with r09.
Vivian(vivo) provides r10 on top of r09.
Malla (NTT DOCOMO) objects r10.
Juan Zhang (Qualcomm) provides r11.
Yannick (Nokia): Nokia provides r12.
Yingying(CATT) provides r13.
Wang Yuan (Huawei) replies to Malla (NTT DOCOMO) and Juan (Qualcomm), and provides r14.
Vivian(vivo) replies to Malla (NTT DOCOMO) comments and provides r15 on top of r14.
Ellen (Google) provides r16 or can live with r13 with the sentence about purpose removed.
Juan Zhang (Qualcomm) provides r17 and r18.
Malla (NTT DOCOMO) prefers r17.
Tingyu (Samsung) can live with both r17 and r18.
Zhang (Ericsson) provide r20
==== Revisions Deadline ====
Wang Yuan (Huawei) can live with both r17 and r18.
Malla (NTT DOCOMO) accepts only r17 and object r20.
Vivian(vivo) prefers r18 and r20, can live with r17 to make progress.
Yannick (Nokia): Nokia supports going forward with r17 or r18.
Tingyu (Samsung) is also OK with r20.
Juan Zhang (Qualcomm) prefers 17, but can live with r18 and r20.
Zhang (Ericsson) response to Yannick (Nokia)
Yingying(CATT) agrees with r13, r17,r18 and r20.
Ellen (Google) supports r17, r20.
==== Final Deadline ====
Revised
9.21 S2-2209917 P-CR Approval 23.700-80: KI#3, Updates to evaluation and conclusions. Samsung, OPPO, CATT, vivo, Huawei, HiSilicon, Google Inc., Ericsson Rel-18 Revision of S2-2208406r17, merging S2-2208241, S2-2208307, S2-2208619, S2-2208693, S2-2209021 and S2-2208709. Approved Approved
9.21 S2-2208241 P-CR Approval 23.700-80: KI#3: Update: Evaluation and Conclusions. Ericsson Rel-18 Merged into S2-2209917 Wang Yuan (Huawei) provides comments for the initial version.
Yannick (Nokia): Nokia also asks for clarification on initial version.
Zhang (Ericsson) confirm the paper is merged into S2-2208406
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208307 P-CR Approval 23.700-80: KI#3: Update of conclusion . Lenovo Rel-18 Merged into S2-2209917 Wang Yuan (Huawei) objects to the proposal of RAN providing UL/DL data rate to the AF.
Malla (NTT DOCOMO) objects r00.
Tingyu (Samsung) comments and proposes to discuss the evaluations and conclusions for KI#3 based on 8406r02, according to the chair's notes.
Mehrdad (Mediatek Inc.) comments
Tricci (OPPO) shares the same concern as Yuan (Huawei) and would like to ask for further clarification.
Haley (Lenovo) replies.
Tricci (OPPO) thanks Haley (Lenovo) response and would like to answer question from Lenovo.
Haley(Lenovo) replies.
LaeYoung (LGE) ask a Q.
LaeYoung (LGE) replies to Haley(Lenovo) and thinks that this pCR can be MERGED to 8406.
Wang Yuan (Huawei) replies to Haley (Lenovo) and still have concern about RAN provides UL/DL data rate to the AF.
Haley(Lenovo) replies to Mehrdad (Mediatek Inc.) and Wangyuan (Huawei).
==== Revisions Deadline ====
Malla (NTT DOCOMO) asked the Chair to change the status of the report to NOTED, not merged.
Wang Yuan (Huawei) agrees with Malla (NTT DOCOMO) and suggests the status of this doc should be NOTED.
==== Final Deadline ====
Merged
9.21 S2-2208619 P-CR Approval 23.700-80: KI#3, Update conclusion. Vivo Rel-18 Merged into S2-2209917 Juan Zhang (Qualcomm) provides comments
Vivian(vivo) replies to Juan Zhang (Qualcomm) comments and provides r01.
Tingyu (Samsung) proposes to merge this with 8406r02, according to the chair's notes.
==== Revisions Deadline ====
Vivian(vivo) agrees to merge this paper to S2-2208406
==== Final Deadline ====
Merged
9.21 S2-2208693 P-CR Approval 23.700-80: Evaluation and Conclusions for KI#2 and KI#3. Huawei, HiSilicon Rel-18 Merged into S2-2209917 Juan Zhang (Qualcomm) provides comments
LaeYoung (LGE) proposes to MERGE KI#2 parts and KI#3 parts to 8659 and 8406, respectively, per rapporteur's recommendation.
Tingyu (Samsung) proposes to merge this Tdoc with 8406, according to the chair's notes.
Mehrdad (Mediatek Inc.) comments and suggests to remove KI#2 conclusion.
Susan (Huawei) replies and provides r01.
David (Samsung) kindly asks Huawei to merge KI2 evaluation into basis document S2-2209097.
==== Revisions Deadline ====
Mehrdad (Mediatek Inc.) requests to mark this PCR as merged or noted.
==== Final Deadline ====
Merged
9.21 S2-2209021 P-CR Approval 23.700-60: KI#3 Evaluation and Conclusion to enhance user consent checking. Google Inc. Rel-18 Merged into S2-2209917 Wang Yuan (Huawei) provides comments for the initial version and r01.
Tricci (OPPO) supports Yuan(Huawei) r01. OPPO has the same opinion.
Malla (NTT DOCOMO) provided comments.
Yannick (Nokia): Nokia comments on r00 and r01.
Wang Yuan (Huawei) replies to Tricci (OPPO), Malla (NTT DOCOMO) and Yannick (Nokia), and provides r02.
Yannick (Nokia): Nokia provides r03.
Vivian (vivo) suggests to merge this paper to S2-2208406 following rapporteurs' guideline, in order to avoid duplications and conflicts .
Ellen (Google) agree r03 provided by Yuan (Huawei) and ask for Rapporteur's guidance on how to handle user consent aspects
Tingyu (Samsung) proposes to merge this paper into S2-2208406, according to the chair's notes.
Ellen (Google) agrees to merge 9021 into 8406r08.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208611 P-CR Approval 23.700-80: KI#3, Update Sol#6: User consent enhancement for AIML operation. Vivo Rel-18 r01 agreed. Revised to S2-2209918. Yannick (Nokia): Nokia provides r01.
Vivian(vivo) replies to Yannick (Nokia) comment and accepts r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209918 P-CR Approval 23.700-80: KI#3, Update Sol#6: User consent enhancement for AIML operation. Vivo Rel-18 Revision of S2-2208611r01. Approved Approved
9.21 - - - KI#4: Enhancing External Parameter Provisioning - - Docs:=4 -
9.21 S2-2208433 P-CR Approval 23.700-80: KI#4: Updated evaluation and conclusion. Samsung Rel-18 r06 agreed. Revised to S2-2209919. Basis evaluation/conclusion document Zhang (Ericsson) provides comments and suggest to remove CP UP related text
Malla (NTT DOCOMO) asks for clarification
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) provides comments
David (Samsung) provides r01 and replies to some of the comments
Yannick (Nokia): Nokia provides r02.
David (Samsung) is OK with r02, provides r03
Yannick (Nokia): Nokia comments on accuracy level.
David (Samsung) responds to Nokia
Malla (NTT DOCOMO) requests clarification.
David (Samsung) replies to Docomo, provides r04
Yannick (Nokia): Nokia provides r05.
David (Samsung) thanks Nokia, provides r06
Yannick (Nokia): Nokia is ok with r06.
==== Revisions Deadline ====
Zhang (Ericsson) is OK with r06
Malla (NTT DOCOMO) is OK with r06
Juan Zhang (Qualcomm) is OK with r06.
==== Final Deadline ====
Revised
9.21 S2-2209919 P-CR Approval 23.700-80: KI#4: Updated evaluation and conclusion. Samsung Rel-18 Revision of S2-2208433r06. Approved Approved
9.21 S2-2208435 P-CR Approval 23.700-80: KI#4: Sol#36 updates to address remaining EN. Samsung Rel-18 r00 agreed. Revised to S2-2209920. Zhang (Ericsson) provides comments
Tricci (OPPO) also would like to ask for clarifications for such CP-UP switching support and wonder how would this functionality benefit Application AI/ML data transfer?
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) provides comments
David (Samsung) replies to comments.
==== Revisions Deadline ====
Zhang (Ericsson) propose to add an NOTE to the paper to address people concerns 'NOTE: whether CP/UP related information is useful or not will be determined in the conclusion clause'
David (Samsung) accepts Ericsson's proposal
Yannick (Nokia): Nokia is fine with r00 + NOTE as suggested by Ericsson.
==== Final Deadline ====
Revised
9.21 S2-2209920 P-CR Approval 23.700-80: KI#4: Sol#36 updates to address remaining EN. Samsung Rel-18 Revision of S2-2208435r00. Approved Approved
9.21 - - - KI#5: 5GC Enhancement to enable Application AI/ML Traffic Transport - - Docs:=5 -
9.21 S2-2208777 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Conclusion. NTT DOCOMO, Oppo, Huawei, Oracle, Toyota Rel-18 CC#3: r09 + EN agreed. Revised to S2-2209941. Basis conclusion document. R10? Belen (Ericsson) provides r01, objects to initial revision
Tricci (OPPO) thanks Belen (Ericsson) detailed update. OPPO provides r03 to correct some mistakes. OPPO cannot accept r02.
Malla (NTT DOCOMO) provides r03. For chair's note, Oppo provided r02, not r03. In this case, Oppo's objection should be for r01.
Wang Yuan (Huawei) replies to Belen (Ericsson) and provides r04.
Belen (Ericsson) objects to r02, r03 and r04. Cannot accept referring to solution#10 as we think it is wrong.
It can accept specific parts as per principles
Tricci (OPPO) thanks Belen (Ericsson) detailed feedback, however, Ericsson still does not explain clearly what exactly wrong with Solution#10, is it just because missing parameters that you would like to be included or just because of the name of the service, i.e. ADT vs, AAMDT? OPPO cannot accept the Ericsson's r01 for rejecting the multiple companies joint Solution#10 as the baseline without fundamental technical justifications.
Wang Yuan (Huawei) thinks there may be some misunderstandings and provide further clarification for Sol#10.
Wang Yuan (Huawei) further complete the clarification to Belen (Ericsson).
David (Samsung) provides r05 and co-signs.
Tricci (OPPO) thanks David (Samsung) for the update, however, the update should be related to transport routing configuration and NOT all transport configurations because Solution#10 itself also includes the transport configuration such as the PCC rules and transmission time windows etc. OPPO provides r06 to clarify the changes from Samsung.
David (Samsung) confirms r06 is OK.
Belen (Ericsson) provides r07, objects to r06, r05
David (Samsung) provides r08
Tricci (OPPO) thanks Belen (Ericsson) revision r07.
Malla (NTT DOCOMO) provided r09 and r10.
==== Revisions Deadline ====
Wang Yuan (Huawei) is ok with r07, r09 or r10.
David (Samsung) supports going with r10, objects to r07 and r09
Belen (Ericsson) can accept r09 and objects to r10,r08
Malla (NTT DOCOMO) asks whether David (Samsung) can live with r09 + an EN
Belen (Ericsson) can live with an EN as suggested by DOCOMO, assuming that this is resolved in the study phase
David (Samsung) replies with a modified proposal
Belen (Ericsson) provides comments to the modified proposal. Thinks that this is a study topic.
==== Final Deadline ====
Revised
9.21 S2-2209941 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Conclusion. NTT DOCOMO, Oppo, Huawei, Oracle, Toyota, Samsung Rel-18 Revision of S2-2208777r09 + EN. Approved Approved
9.21 S2-2208244 P-CR Approval 23.700-80: KI#5 Conclusions. Ericsson Rel-18 Noted Tricci (OPPO) provided r01 to update the baseline evaluation tdoc for KI#5 from Ericsson, S2-2208244 to reflect the latest Solution#10 status.
Belen (Ericsson) provides r02, cannot accept r01.
David (Samsung) corrects the subject of the email thread with the right contribution title.
Tricci (OPPO) is very much confused with Belen (Ericsson) argument for objecting r01 from OPPO for updating the evaluation against Solution#10 to make it more accurate, and would like to ask for clarifications from Ericsson.
Belen (Ericsson) provides replies to OPPO
Tricci (OPPO) thanks Belen (Ericsson) response, and would like to provide further clarifications.
==== Revisions Deadline ====
Malla (NTT DOCOMO) pointed that conclusion is overlap with 08777, only support on agreeing without the conclusion, or else we object r00 and any revision with conclusion.
Tricci (OPPO) responds to Malla (NTT DoCoMo) with clarifications.
Belen (Ericsson) cannot accept r01, it is okay to NOTE this contribution .
==== Final Deadline ====
Noted
9.21 S2-2208479 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Solution#10 Update for BDT Extensions. Oracle, Toyota, NTT DoCoMo, Huawei, OPPO Rel-18 r01 agreed. Revised to S2-2209921. Belen (Ericsson) provides comments, cannot agree with initial revision.
Tricci (OPPO) thanks Belen (Ericsson) comments and please kindly provide your feedback so that I can update the Solution#10 accordingly. Thanks.
Tricci (OPPO) provides r01 based on the comments from Ericsson.
==== Revisions Deadline ====
Tricci (OPPO) supports all revisions.
==== Final Deadline ====
Revised
9.21 S2-2209921 P-CR Approval 23.700-80: TR 23.700-80: KI#5 Solution#10 Update for BDT Extensions. Oracle, Toyota, NTT DoCoMo, Huawei, OPPO Rel-18 Revision of S2-2208479r01. Approved Approved
9.21 - - - KI#6: QoS and Policy Enhancement - - Docs:=10 -
9.21 S2-2208617 P-CR Approval 23.700-80: TR 23.700-80: Comments for Evaluation Descriptions in Clause 7 on KI#6. OPPO, Oracle Rel-18 Merged into S2-2209922 and S2-2209923 Tricci (OPPO) merges the conclusion part of 8617 into 8695, and the evaluation part of 8617 into 8245.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208695 P-CR Approval 23.700-80: KI#6: Update Evaluation and Conclusions. Huawei, HiSilicon Rel-18 r09 agreed. Revised to S2-2209922, merging S2-2208405 and S2-2208617 Basis conclusion document Susan (Huawei) provides r01.
Tingyu (Samsung) proposes r02 with minor changes and confirms co-sourcing.
Yannick (Nokia): Nokia provides r03.
Belen (Ericsson) provides r04, objects to r03, r02 and r01. It accepts also initial version (not merged)
Yannick (Nokia): Nokia requests clarification on r04.
Tingyu (Samsung) replies to Ericsson and provides r05.
Tricci (OPPO) provides r06 to update the conclusion that no new Group QoS parameter is introduced for this study.
Tricci (OPPO) merges 8617 into 8695.
Yannick (Nokia): Nokia requests clarification on r06.
Tingyu (Samsung) replies Nokia.
Belen (Ericsson) provides r07, replies to Nokia and Samsung.
Yannick (Nokia): Nokia provides r08.
Tingyu (Samsung) provides r09 with minor changes.
Yannick (Nokia): Nokia thanks Samsung for the changes in r09.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209922 P-CR Approval 23.700-80: KI#6: Update Evaluation and Conclusions. Huawei, HiSilicon, OPPO, Oracle, Ericsson, Samsung, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208695r09, merging S2-2208405 and S2-2208617. Approved Approved
9.21 S2-2208245 P-CR Approval 23.700-80: KI#6 Evaluation and Conclusions. Ericsson Rel-18 r02 agreed. Revised to S2-2209923. Basis evaluation document Dongeun (Samsung) provides comments and provides r01.
Tricci (OPPO) merges 8617 into 8245.
Belen (Ericsson) provides r02, removing conclusions.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209923 P-CR Approval 23.700-80: KI#6 Evaluation and Conclusions. Ericsson Rel-18 Revision of S2-2208245r02. Approved Approved
9.21 S2-2208405 P-CR Approval 23.700-80: KI#6: Updates to evaluation and conclusion. Samsung Rel-18 Merged into S2-2209922 Tingyu (Samsung) merged 8405 with 8695.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208993 P-CR Approval 23.700-80: Solution #38 evaluation and conclusions for key issue #6. Nokia, Nokia Shanghai Bell Rel-18 Noted. CC#4: r01 agreed. Revised to S2-2209983. Belen (Ericsson) objects to this contribution.
Yannick (Nokia): Nokia provides r01, focusing on evaluation for solution #38 and removing conclusion part.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209983 P-CR Approval 23.700-80: Solution #38 evaluation and conclusions for key issue #6. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208993r01. Approved Approved
9.21 S2-2208308 P-CR Approval 23.700-80: KI#3&KI#6: Update of solution#7. Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.21 S2-2209192 P-CR Approval 23.700-80: KI#6: Sol#15: Update: QoS monitoring for AIML application. InterDigital Rel-18 Approved Belen (Ericsson) provides comments
Mehrdad (Media Tek Inc.) comments.
Ulises Olvera (InterDigital Inc.) replies to Belen (Ericsson) and (Mehrdad).
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.21 - - - KI#7: 5GS Assistance to Federated Learning Operation - - Docs:=17 -
9.21 S2-2208509 P-CR Approval 23.700-80: KI#7: Evaluation and conclusion. LG Electronics Rel-18 Merged into (Covered by) S2-2208651 Dongjoo(Nokia) asks a question
Malla (NTT DOCOMO) merged into S2-2208651
Tricci (OPPO) provided response to Dongjoo (Nokia) and believes NWDAF is the worst choice of NF in 5GC to be the anchor function to assist the member selection for the AF.
Dongjoo(Nokia) replies to Tricci (OPPO)
Jaewoo (LGE) replies to Dongjoo(Nokia) and Malla (NTT DOCOMO).
Dongjoo(Nokia) comments
David (Samsung) supports to mark this document as merged and continue the discussion in the relevant threads.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208651 P-CR Approval 23.700-80: TR 23.700-80: Evaluation and conclusion for Member Selection KI#7. OPPO, Oracle Rel-18 - Option-1 - NEF:
- Option-2 - NWDAF:
- Option-3 - New NF:
NOTE: Option-3 does not preclude the New NF to be co-located with other 5GC NF and will be determined during the normative phase
Regardless of the SoH result, S2-2208651 will be noted and the following EN added to cl. 8.7:
Editor's note: Conclusions to KI7 need to be finalized in SA2#154 based on SoH result at SA2#153E

Show of Hands:
Qn-1: Should the FL Member Selection Assistance Functionality be supported in R18?
Yes: 25 Samsung, OPPO, Tencent, China Telecom, Toyota, Oracle, InterDigital, LGE, ETRI, vivo, AT&T, China Unicom, CableLabs, Charter, MediaTek Inc., Intel , ZTE, LG Uplus, Google, Huawei, Alibaba, Xiaomi, DISH, Lenovo, CATT
No: 6 Nokia, Ericsson, NTT DOCOMO, Deutsche Telekom, Apple, CMCC
Way Forward: This will be further worked on at the next meeting. Progress should continue with the assumption that FL Member Selection Assistance Functionality will be supported in Rel-18.

Qn-2: If the decision for Qn-1 is "Yes", which of the following 5GC NF is best suited to provide the FL Member Selection Assistance Functionality:
- Option-1 - NEF:
Yes: 8 Ericsson, NTT DOCOMO, Xiaomi, Nokia, vivo, T-Mobile USA, Lenovo, Intel
- Option-2 - NWDAF:
Yes: 14 CMCC, Nokia, Qualcomm, AT&T, Ericsson, China Telecom, CATT, CableLabs, vivo, T-Mobile USA, Charter, Huawei, ZTE, Lenovo
- Option-3 - New NF:
Yes: 16 Samsung , InterDigital, MediaTek Inc. , OPPO, Oracle, LGE, LG Uplus, ETRI, Toyota, China Unicom, Orange, DISH, Alibaba , Huawei , Intel, Xiaomi
Samsung asked that the result of the show of hands should be captured in the conclusions in an editor's note. This was not considered necessary. S2-2208651 was postponed.">CC#4: Postponed Basis conclusion clause document (8.7.X): member selection. R08?
Tricci (OPPO) provides r01 to merge OPPO's 8644 into 8651 per rapporteur proposed agenda plan.
Dongjoo(Nokia) comments
Tricci (OPPO) thanks Dongjoo (Nokia) feedback and would like to provide responses.
Zhang (Ericsson) object r00 and r01, provides r02
David (Samsung) provides r03
Tricci (OPPO) accepts r03 as the starting point to discuss the conclusions of member selection for KI#7
Tricci (OPPO) would like to request Zhang (Ericsson) to examine the technical justifications for dedicated 5GC NF in other email thread for S2-2208570 before deciding that there is no strong technical justification on this new NF. Thanks.
Dongjoo(Nokia) provides further feedback to Tricci(OPPO)
Jaewoo (LGE) provides r04 to merge 8509 into 8651.
Tricci (OPPO) thanks Dongjoo (Nokia) feedback. OPPO prepared r05 to suggest a way forward towards conclusion on the member selection aspect for KI#7.
Dongjoo(Nokia) responds to Tricci(OPPO)
Aihua(CMCC) comments.
Tricci (OPPO) responds to Dongjoo(Nokia) and requests Nokia to provide clarifications.
Tricci (OPPO) thanks Aihua(CMCC) kind confirmation for the importance to specify the member selection criteria. OPPO has further question to CMCC and Nokia on the feasibility to leverage NWDAF to generate the candidate member list.
Malla (NTT DOCOMO) provided r06.
Malla (NTT DOCOMO) replies to Samsung and Oppo.
Tricci (OPPO) thanks Malla (NTT DOCOMO) explanations, however, OPPO object r06 without any further clarifications from DoCoMo
David (Samsung) provides r07, cannot accept r06
Tricci (OPPO) would like to further respond to Malla (DoCoMo).
Dongjoo(Nokia) responds to Tricci(OPPO) and asks a question
Zhang (Ericsson) provide comment to Dongjoo(Nokia) and Malla (Docomo)
David (Samsung) provides views on Dongjoo's questions
Malla (NTT DOCOMO) replies to Tricci (OPPO).
Tricci (OPPO) thanks Malla (NTT DOCOMO) responses. OPPO asks for further clarifications.
David (Samsung) comments on Docomo's views.
Dongjoo(Nokia) responds to David(Samsung)
Wang Yuan (Huawei) is ok with r06 and r07, and proposes to merge FL member selection part of S2-2208709 into S2-2208651, provides r08 and cosigns this pCR.
Dongjoo(Nokia) provides r09
David (Samsung) objects to r09 and co-signs r08
Dongjoo(Nokia) responses to David (Samsung)
David (Samsung) replies to Dongjoo
Aihua(CMCC) provides r10.
Vivian(vivo) raises a concern about whether NWDAF analytics should be added as another criteria for FL member selection
David (Samsung) can accept r10, asks CMCC if they'd be willing to merge their evaluation content into this paper.
Menghan(China Telecom) comments on other than the controversial issue and provides r11 (based on r10)
Tricci (OPPO) thanks Menghan(China Telecom) clarifications and update, and asks for more clarifications.
Malla (NTT DOCOMO) replies to Tricci (OPPO) and David (Samsung).
Belen (Ericsson) provides comments, ask not to include QoS information that is discussed in KI#6
Jihoon (ETRI) asks David (Samsung) about AI/ML session identifier (AMSID) for clarification.
Aihua(CMCC) replies to David (Samsung): it looks not necessary to merge 8886 into this paper.
Tricci (OPPO) thanks Malla (NTT DOCOMO) kind responses.
Zhang (Ericsson) object all version from r08
Menghan(China Telecom) replies to Tricci(OPPO)
Aihua(CMCC) replies to Belen (Ericsson) that QoS information is helpful for the AF to select the FL member, asking to keep in list.
Dongjoo (Nokia) comments.
Belen (Ericsson) replies to CMCC that the AF can use Analytics on QoS Sustainability
Tricci (OPPO) responds to Dongjoo (Nokia) comments.
David (Samsung) replies to Ericsson
Zhang (Ericsson) response to David (Samsung)
==== Revisions Deadline ====
Jihoon (ETRI) replies to David (Samsung).
Tricci (OPPO) responds also to Jihoon (ETRI) on clarifying the use of the AMSID
Zhang (Ericsson) provides comments and thanks Tricci's comment
Tricci (OPPO) would like to build common understandings on what exactly we are disagreeing before we can discuss how to move forward.
Zhang (Ericsson) response to Tricci (OPPO) and provides r12 after revision deadline. Pointed out that the following sentence is not correct and all the version with the sentence should be objected.
'The criteria below provided by the AF is used for candidate UE list selected by 5GC NF for member selection.'
Malla (NTT DOCOMO) only accept r09 (from Nokia) and can live with r12 (provided after deadline), and object all revisions.
Tricci (OPPO) thanks Zhang (Ericsson) feedback and would like to provide some clarifications.
Dongjoo (Nokia) also accepts r09 and can live with r12 (but further changes are required in the evaluation part from both r09 and r12), and objects all other revisions.
Dongjoo (Nokia) response to Tricci (OPPO) on the 'fundamental disagreement on the requirements'
Tricci (OPPO) thanks Dongjoo (Nokia) feedback for his clarifications, however, OPPO respectfully confused by Nokia's response because it is contradiction of itself.
Tricci (OPPO) can live with r08. OPPO can NOT accept any version that exclude the support for Dedicated NF.
Dongjoo (Nokia) answers to Tricci (OPPO)'s question.
David (Samsung) agrees to r11, r10, r08; objects to r09 and late r12; agrees with OPPO a SoH is needed for this aspect
==== Final Deadline ====
Postponed
9.21 S2-2208676 P-CR Approval 23.700-80: KI#7: Proposal for Conclusion for KI#7. Samsung Rel-18 Noted Belen (Ericsson) provides r01
Malla (NTT DOCOMO) provides r02
Tricci (OPPO) asks for clarifications regarding the 'new QoS mechanism' in conclusion for KI#7.
David (Samsung) provides r03, objects to r02
Dongjoo (Nokia) asks questions for clarification
David (Samsung) replies to Nokia
Dongjoo (Nokia) provides further feedback to David(Samsung) and asks a question.
Zhang (Ericsson) share the same view as Nokia
David (Samsung) replies to Nokia and Ericsson, agrees to discuss dedicated NF on S2-2208651
Jihoon (ETRI) asks questions other than the controversial issue on the necessity of a dedicated NF.
Wang Yuan (Huawei) proposes to merge FL performance part of S2-2208709 into S2-2208676, provides r04 and cosigns this pCR.
Jihoon (ETRI) asks Wang Yuan (Huawei) about the FL performance part.
Wang Yuan (Huawei) replies to Jihoon (ETRI).
Tricci (OPPO) provides r06 to update the conclusion that no new Group QoS parameter is introduced for this study.
David (Samsung) raises the issue that the latest revision by OPPO has been shared in the wrong thread
Tricci (OPPO) thanks David (Samsung) catching OPPO's mistake and please remove r06 on this email thread.
David (Samsung) proposes to mark this document as merged into S2-2208651
Jihoon (ETRI) replies to Wang Yuan (Huawei).
Zhang (Ericsson) also propose to merge the paper into S2-2208651
Zhang (Ericsson) response to r05 just in case the paper is not merged
==== Revisions Deadline ====
Menghan(China Telecom) asks a question
Wang Yuan (Huawei) is ok with either r04 or r05, and thinks it's no need to merge into 8651, and proposes to add the following NOTE in r04 or r05 to address the concern raised by Jihoon (ETRI). NOTE: It does not limit that FL performance can be only assisted by DN Performance Analytics. Additional analytics other than DN Performance Analytics may need to be extended to assist with other aspects of FL performance, if any.
Tricci (OPPO) supports Yuan (Huawei) and would like to keep the conclusion captured in this tdoc.
Menghan(China Telecom) also supports Yuan (Huawei) and would like to keep the conclusion captured in this tdoc.
Zhang (Ericsson) is OK with r02 and r05, object all other versions
Malla (NTT DOCOMO) is OK with r02 and r05, object all other revisions
Jihoon (ETRI) supports Yuan (Huawei)'s proposal to add the suggested NOTE in r05.
David (Samsung) clarifies this document should be marked as merged into S2-2208651. Whether any late version of S2-2208651 can be agreed is still to be seen
In addition: David (Samsung) objects to r02 and r05
David (Samsung) replies to China Telecom; this document can stay un-merged but there is no agreeable revision
Zhang (Ericsson) suggest to change the NOTE to an EN
==== Final Deadline ====
Wang Yuan (Huawei) suggests a final try at CC#3 and proposes to go forward with r05 + two Editor's note.
Zhang (Ericsson) is OK with Yuan's proposal + remove the EN about new NF
Noted
9.21 S2-2208709 P-CR Approval 23.700-80: Conclusion of KI #7. Huawei, HiSilicon Rel-18 Merged into S2-2209917 Merged into multiple TDs? David (Samsung) comments that this document should be marked as merged.
Wang Yuan (Huawei) thanks David (Samsung) for the reminder, and proposes to merge FL member selection part of S2-2208709 into S2-2208651, merge Performance monitoring/exposure part of S2-2208709 into S2-2208842, merge FL performance part of S2-2208709 into S2-2208676, and merge user consent part of S2-2208709 into S2-2208406.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208783 P-CR Approval 23.700-80: TR 23.700-80: KI#7 Conclusion. NTT DOCOMO Rel-18 Merged into (Covered by) S2-2208651 David (Samsung) comments that this document should be marked as merged.
Malla (NTT DOCOMO) agrees to mark this pCR as merged with S2-2208651/S2-2208842.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 S2-2208842 P-CR Approval 23.700-80: KI #7, Evaluation and Conclusion for Performance Monitoring Exposure. ETRI Rel-18 Noted Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) provides comments
David (Samsung) comments on Docomo's proposal
Yannick (Nokia): Nokia requests for clarification.
Belen (Ericsson) asks where to discuss Group MBR monitoring.
Tricci (OPPO) responds to Yannick (Nokia).
Tricci (OPPO) agrees with Belen (Ericsson), Solution#37 should be discussed in KI#1 as we have agree in last SA2#153E.
Jaewook (ETRI) provides r01 and replies to Zhang (Ericsson).
Jaewook (ETRI) replies to Malla (NTT DOCOMO) and David (Samsung).
Jaewook (ETRI) provides r02 and replies to Yannick (Nokia) and Tricci (OPPO).
Jaewook (ETRI) provides r03 and replies to Belen (Ericsson) and Tricci (OPPO).
Zhang (Ericsson) provide r04 and co-sign
Jaewook (ETRI) is fine with r04 and thanks for co-sign.
Wang Yuan (Huawei) proposes to merge Performance monitoring/exposure part of S2-2208709 into S2-2208842, provides r05 and cosigns this pCR.
Jaewook (ETRI) thanks for co-sign and comments on r05.
Tricci (OPPO) provides r06 to clarify the list of aggregate monitoring parameters are analytics outputs and not 'new' QoS parameters.
David (Samsung) provides r07 and co-signs.
Wang Yuan (Huawei) replies to Jaewook (ETRI) and David (Samsung), and provides r08.
David (Samsung) provides r09.
Wang Yuan (Huawei) thanks David (Samsung) for clarification and can accept r09.
Yannick (Nokia): Nokia comments on r09. Cannot accept r09 and provides r10.
Zhang (Ericsson) promote r10
Wang Yuan (Huawei) provides r11.
Tricci (OPPO) provides r13, sorry for skipping r12 by mistake.
==== Revisions Deadline ====
Wang Yuan (Huawei) can accept r13.
Tricci (OPPO) thanks Yuan (Huawei) to accept r13. OPPO accepts ONLY r13.
Zhang (Ericsson) is OK with r13, object all other versions
Malla (NTT DOCOMO) is OK with r13.
Yannick (Nokia): Nokia objects to r13 and r11. Suggest to go with r10 in this meeting and come back to the debated sentence in next meeting.
Zhang (Ericsson) is also OK with r10
Tricci (OPPO) responds to Yannick (Nokia), provides OPPO's perspective and asks for clarification from Nokia.
Tricci (OPPO) supports ONLY r13. Sorry...
==== Final Deadline ====
Jaewook (ETRI) suggests to move forward with r10 + the editor's note.
Noted
9.21 S2-2208994 P-CR Approval 23.700-80: Evaluations and conclusions for KI#7. Nokia, Nokia Shanghai Bell Rel-18 r01 agreed. Revised to S2-2209924. Merged into S2-2208651 (Postponed at CC#4). Postponed Dongjoo(Nokia) provides r01
David (Samsung) comments that this document should be marked as merged.
Dongjoo (Nokia) replies to David (Samsung)
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.21 S2-2209924 P-CR Approval 23.700-80: Evaluations and conclusions for KI#7. Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208994r01. WITHDRAWN Withdrawn
9.21 S2-2208995 P-CR Approval 23.700-80: Evaluation for analytics enhancements and new analytics, and conclusions for Key Issue #7. Nokia, Nokia Shanghai Bell Rel-18 Noted Jingran(OPPO) moves r01 to draft/revision folder per SA2 Chair instructions
Jingran (OPPO) provides r01
Zhang (Ericsson) provides comments
Malla (NTT DOCOMO) provides comments
Jihoon (ETRI) provides r02 with some comments and cosigns this pCR.
Jingran(OPPO) provides comments.
Menghan(China Telecom) provides r03 with some comments.
Jihoon (ETRI) replies to Jingran(OPPO).
Jingran (OPPO) provides r04.
Zhang (Ericsson) provide r05 and co-sign
David (Samsung) provides r06
Yannick (Nokia): Nokia provides r07.
Jingran (OPPO) provides comments.
Jingran (OPPO) provides r08.
David (Samsung) provides r10
Yannick (Nokia): Nokia asks Samsung for clarification.
David (Samsung) replies to Nokia
Yannick (Nokia): Nokia replies to Samsung.
Menghan (China Telecom) provides r11(based on r10)
==== Revisions Deadline ====
Yannick (Nokia): Nokia objects to r11 and r10. Supports r07 and r08.
David (Samsung) objects to r07 and r08, can agree to a modified version of Nokia's proposal based on r10
==== Final Deadline ====
Yannick (Nokia): Nokia suggests to go forward with r10 + editor's note.
Menghan (China Telecom) objects to r10, can agree with r11+EN
Yannick (Nokia): Nokia suggests to go forward with r10 + editor's note. Cannot agree to go with r11 + editor's note.
Noted
9.21 S2-2208886 P-CR Approval 23.700-80: KI#7 Update to Evaluation and Conclusion. China Mobile Rel-18 r02 agreed. Revised to S2-2209925. Basis general evaluation document Megha(Intel) provides r01
David (Samsung) provides r02.
Malla (NTT DOCOMO) provided comments
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209925 P-CR Approval 23.700-80: KI#7 Update to Evaluation and Conclusion. China Mobile Rel-18 Revision of S2-2208886r02. Approved Approved
9.21 S2-2208234 P-CR Approval 23.700-80: KI#7, Updates to Solution#41. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.21 S2-2208510 P-CR Approval 23.700-80: KI#7, Sol#40 update UE-initiated request to join an AI/ML session for FL. LG Electronics Rel-18 r01 agreed. Revised to S2-2209926. Mehrdad (Mediatek Inc.) comments
David (Samsung) provides r01 and co-signs
Jaewoo (LGE) replies to David (Samsung) and OK with r01.
Zhang (Ericsson) ask question
Jaewoo (LGE) replies to Zhang (Ericsson).
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209926 P-CR Approval 23.700-80: KI#7, Sol#40 update UE-initiated request to join an AI/ML session for FL. LG Electronics, Samsung Rel-18 Revision of S2-2208510r01. Approved Approved
9.21 S2-2208711 P-CR Approval 23.700-80: KI#7, Sol#39: Update to remove ENs. Huawei, HiSilicon Rel-18 r05 agreed. Revised to S2-2209927, merging S2-2209019 Zhang (Ericsson) provides comments
Dongeun (Samsung) provides comments
Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) replies to Zhang (Ericsson), Dongeun (Samsung) and Yannick (Nokia), and provides r01.
Malla (NTT DOCOMO) Changes overlap with S2-2209019, could Huawei and Google work and confirm the group for comments
Wang Yuan (Huawei) replies to Dongeun (Samsung) and provides r02.
Wang Yuan (Huawei) proposes to merge S2-2209019 into S2-2208711, and provides r03.
Ellen (Google) provides r04 for S2-2208711
Dongeun (Samsung) provides r05
Wang Yuan (Huawei) can accept r05, and proposes to continue the discuss of 'AF purpose' in thread 8406.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.21 S2-2209927 P-CR Approval 23.700-80: KI#7, Sol#39: Update to remove ENs. Huawei, HiSilicon, Google Inc. Rel-18 Revision of S2-2208711r05, merging S2-2209019. Approved Approved
9.21 S2-2209019 P-CR Approval 23.700-80: Resolve Editor s Note for user consent handling in Sol#39 . Google Inc. Rel-18 Merged into S2-2209927 Zhang (Ericsson) suggest merge the paper into S2-2208711
Wang Yuan (Huawei) also propose to merge S2-2209019 into S2-2208711.
Ellen (Google) agree to merge merge S2-2209019 into S2-2208711 and move the discussion in 8711 thread.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.21 - - - Documents exceeding TU Budget - - Docs:=9 -
9.21 S2-2208233 P-CR Approval 23.700-80: General: Updates to General Architecture Principles. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2208430 P-CR Approval 23.700-80: Updates to General Architecture Principles. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2209188 P-CR Approval 23.700-80: TR 23.700-80: Proposal for Conclusions for General Architecture Principles . OPPO, Oracle Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2209183 P-CR Approval 23.700-80: TR 23.700-80: Evaluation of General Architecture Principles, Principle #2. InterDigital Inc. Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2208571 P-CR Approval 23.700-80: KI#1: Conclusion for KI#1. Qualcomm Incorporated Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2209100 P-CR Approval 23.700-80: Update on Conclusion for KI#2. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2208644 P-CR Approval 23.700-80: TR 23.700-80: Evaluations and conclusions for KI#7. OPPO, Oracle Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2208683 P-CR Approval 23.700-80: KI#7: Proposal for Evaluation for KI#7. Samsung Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.21 S2-2209119 P-CR Approval 23.700-80: KI#7: Evaluation update. Intel Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.22 - - - Study on Enhancement of 5G UE Policy (FS_eUEPO) - - Docs:=41 -
9.22 - - - Solution Update for KI#1 (URSP in VPLMN) - - Docs:=2 -
9.22 S2-2208647 P-CR Approval 23.700-85: KI#1, updates to solution#2 and solution#6 in TR23700-85. OPPO Rel-18 r03 agreed. Revised to S2-2209321. Mike (InterDigital) asks a question
Yang (OPPO) replies to Mike
Mike (InterDigital) replies to Yang (OPPO)
Hong (Qualcomm) replies to Mike.
Changhong (Intel) comments.
Mike (InterDigital) replies and provides r01
Dimitris (Lenovo) comments on r01
Yang (OPPO) provides r02
Dimitris (Lenovo) provides r03. Objects to other versions
Yang (OPPO): r03 is the version I can live with
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.22 S2-2209321 P-CR Approval 23.700-85: KI#1, updates to solution#2 and solution#6 in TR23700-85. OPPO Rel-18 Revision of S2-2208647r03. Approved Approved
9.22 - - - Evaluation and Conclusion for KI#1 (URSP in VPLMN) - - Docs:=11 -
9.22 S2-2208199 P-CR Approval 23.700-85: KI #1, Conclusion Update on Re-evaluation Triggers. InterDigital Inc., Intel Rel-18 r03 agreed. Revised to S2-2209322. Changhong (Intel) proposes to use this paper as baseline for URSP re-evaluation trigger with PLMN change.
Chia-Lin (MediaTek) provides the comments as raised during CC and offline discussions.
Changhong (Intel) replies to Chia-Lin's comments.
Mike (InterDigital) replies to Chia-Lin (MediaTek)
Pallab (Nokia) comments
Chia-Lin (MediaTek) provides response to Pallab (Nokia)
Pallab (Nokia) comments and provides r01
Chia-Lin (MediaTek) provides r02 based on r01
Changhong (Intel) is OK with r02 and thanks Chia-Lin for compromising.
Hong (Qualcomm) comments.
Changhong (Intel) provides r03 with deleting the misleading discussion part based on Hong's comment.
==== Revisions Deadline ====
Pallab (Nokia) is OK to approve r03
Chia-Lin (MediaTek) is ok with r03
==== Final Deadline ====
Revised
9.22 S2-2209322 P-CR Approval 23.700-85: KI #1, Conclusion Update on Re-evaluation Triggers. InterDigital Inc., Intel Rel-18 Revision of S2-2208199r03. Approved Approved
9.22 S2-2208345 P-CR Approval 23.700-85: KI#1, Conclusions: Proposal to remove Editor s Notes . Ericsson Rel-18 r04 agreed. Revised to S2-2209323. Changhong (Intel) proposes to use this paper as baseline for clause 8.1.1.
Susan (Huawei) provides comments to the paper.
Changhong (Intel) asks Susan on how to move forward with this paper.
Belen (Ericsson) provides r01
Susan (Huawei) provides r02.
Dimitris (Lenovo) comments
Mike (InterDigital) provides r03
LaeYoung (LGE) replies to Dimitris (Lenovo).
Changhong (Intel) provides r04 to remove the whole second change part for clause 8.1.2.
Belen (Ericsson) provides is okay with r04, also replies to Lenovo.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.22 S2-2209323 P-CR Approval 23.700-85: KI#1, Conclusions: Proposal to remove Editor s Notes . Ericsson Rel-18 Revision of S2-2208345r04. Approved Approved
9.22 S2-2208598 P-CR Approval 23.700-85: KI#1, Conclusion update: EN resolution. LG Electronics, Ericsson, Huawei, Intel, vivo, Qualcomm Incorporated Rel-18 r01 agreed. Revised to S2-2209324, merging S2-2208986 Changhong (Intel) proposes to use this paper as baseline for clause 8.1.3.
LaeYoung (LGE) would like to seek how to move forward on the aspect about who provides Service Parameters to H-PCF.
Dimitris (Lenovo) questions how the solution will work given that there is no procedure for the UE to identify VPLMN rules
Belen (Ericsson) provides comments
Mike (InterDigital) agrees with Dimitris (Lenovo)
Susan (Huawei) shares the same view as Belen (Ericsson).
LaeYoung (LGE) shares the same view with Susan (Huawei) and Belen (Ericsson).
Changhong (Intel) kindly asks DK and Mike to compromise as the rapporteur.
Wen (vivo) comments.
Pallab (Nokia) provides comments and has some concerns with the conclusions
Dimitris (Lenovo) provides r01 as a compromise
LaeYoung (LGE) replies to Pallab (Nokia) and Dimitris (Lenovo) and is fine with r01.
Belen (Ericsson) thinks that we need to reach some compromise, can live with r01
==== Revisions Deadline ====
Pallab (Nokia) is also OK with the compromise proposal in r01
==== Final Deadline ====
Revised
9.22 S2-2209324 P-CR Approval 23.700-85: KI#1, Conclusion update: EN resolution. LG Electronics, Ericsson, Huawei, Intel, vivo, Qualcomm Incorporated Rel-18 Revision of S2-2208598r01, merging S2-2208986. Approved Approved
9.22 S2-2208650 P-CR Approval 23.700-85: KI#1, updates to clause 8.1.2 how to identify PLMN specific URSP Rules . OPPO Rel-18 Noted Changhong (Intel) proposes to use this paper as baseline for clause 8.1.2.
Mike (InterDigital) expresses concerns
Changhong (Intel) provides r01 as the rapporteur.
Hong (Qualcomm) objects r01.
Changhong (Intel) kindly ask Hong (Qualcomm) to compromise as the rapporteur.
Hong (Qualcomm) replies and maintains the objection.
Belen (Ericsson) provides comments, ask QC.
Dimitris (Lenovo) provides a further compromise proposal
Hong (Qualcomm) replies to Belen.
Dimitris (Lenovo) comments
==== Revisions Deadline ====
Chia-Lin (MediaTek) share the same view with Hong (Qualcomm)
==== Final Deadline ====
Noted
9.22 S2-2208656 P-CR Approval 23.700-85: KI#1, updates to the clause 7.1.1 evaluation and clause 8.1.1 general conclusion in TR 23.700-85. OPPO Rel-18 r01 agreed. Revised to S2-2209325. Changhong (Intel) proposes to merge this paper into S2-2208345.
Yang (OPPO) provides r01 and suggests to keep the pCR with r01 which has removed the overlapped part to 8345
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.22 S2-2209325 P-CR Approval 23.700-85: KI#1, updates to the clause 7.1.1 evaluation and clause 8.1.1 general conclusion in TR 23.700-85. OPPO Rel-18 Revision of S2-2208656r01. Approved Approved
9.22 S2-2208756 P-CR Approval 23.700-85: KI#1: Conclusions for provisioning and identifying VPLMN specific URSP rules. Lenovo, Apple Rel-18 Merged into (Covered by) S2-2208650 Changhong (Intel) proposes to merge this paper into S2-2208650 (clause 8.1.2) and S2-2208598 (clause 8.1.3).
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208986 P-CR Approval 23.700-85: KI #1, conclusion update to reflect the SA WG2#152e decision. Samsung Rel-18 Merged into S2-2209324 Changhong (Intel) proposes to merge this paper into S2-2208598.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 - - - Solution Update for KI#2 (5GC awareness of URSP enforcement) - - Docs:=2 -
9.22 S2-2208648 P-CR Approval 23.700-85: Solution#11 Update: 5GC awareness of URSP recognition. Google Inc., OPPO, Apple Rel-18 r06 agreed. Revised to S2-2209326. Josep (DT) comments, provides r01. Wonders whether the solution is changes too much to be considered the same solution.
Dimitris (Lenovo) request to clarify further 'unsupported URSP rule'
Hong (Qualcomm) asks for clarifications on the use of the report.
Haiyang (Huawei) comments
Krisztian (Apple) provides r02.
Ellen (Google) is fine with r02 provided by Krisztian (Apple) and feedback to Josep (DT), Hong (QC), Dimitris (Lenovo), Haiyang (HW)
Haiyang (Huawei) further comments
Yang (OPPO) disagree with HW's comment
Elmira (Vodafone) disagrees with the current versions, comments and provides r03
Belen (Ericsson) provides r04
Ellen (Google) provides r05 and prefer r02
Josep (DT) comments on the terminology. TS 24.526 uses 'unrecognized' and not 'unsupported'
Elmira (Vodafone) considers PCF should not blindly remove unrecognized components from URSP rules but act as per local policies. R06 is provided on the top of r04 from Ericsson. R05 is not acceptable for us.
Hong (Qualcomm) comments.
Ellen (Google) feedback to Hong (Qualcomm)
Antoine (Orange) replies to Hong and Ellen.
==== Revisions Deadline ====
Ellen (Google) replies to Antoine.
Josep (DT) objects to r00, r01, r02 r05. Strongly prefers r06
Ellen (Google) prefers r05 and can live with r06 (stage 3 can work on the details)
==== Final Deadline ====
Revised
9.22 S2-2209326 P-CR Approval 23.700-85: Solution#11 Update: 5GC awareness of URSP recognition. Google Inc., OPPO, Apple Rel-18 Revision of S2-2208648r06. Approved Approved
9.22 - - - Evaluation and Conclusion for KI#2 (5GC awareness of URSP enforcement) - - Docs:=13 -
9.22 S2-2208206 P-CR Approval 23.700-85: 23.700-85: KI#2: Evaluation of need of UE assistance and interim conclusion. Deutsche Telekom, Orange, Vodafone, Telef nica Rel-18 Merged into (Covered by) S2-2208346 Changhong (Intel) proposes to use this paper as baseline for UE reporting information during PDU Session Establishment.
Josep (DT) asks questions for clarification to Iskren (NEC), can ultimately merge with S2-2208346.
Krisztian (Apple) provides comments to Iskren (NEC).
Iskren (NEC) answers comments from Krisztian (Apple)
Josep (DT) replies to Iskren (NEC).
Changhong (Intel) asks to merge this paper into S2-2208346 and focus on one thread discussion there.
Josep (DT) is OK with the merge. 8346 is OK as way forward.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208346 P-CR Approval 23.700-85: KI#2, Evaluation and Conclusions. Ericsson Rel-18 CC#3: Postponed to CC#4. CC#4: r27 received support in SoH. Revised to S2-2209957. Changhong (Intel) proposes to use this paper as baseline for UE reporting information during PDU Session Establishment and out of PDU Session.
Josep (DT) comments, provides r01, supports this compromise approach, co-signs.
Hong (Qualcomm) provide r02.
Yang (OPPO) comments to r02.
Huazhang (vivo) answer a question about APP ID? Is the APP ID is the application on UE that identified, or the application identifier (APP ID)?
Hong (Qualcomm) replies to Huazhang, and Yang.
Krisztian (Apple) cannot accept r02, r01 or r00 (and other revisions) that describe the UE reporting an App ID in PDU Session Establishment or Modification.
Josep (DT) comments, provides r03.
Haiyang (Huawei) comments.
Belen (Ericsson) replies to questions from vivo and comments
Iskren (NEC) comments
Josep (DT) comments, provides r04.
Hong (Qualcomm) comments, provides r05.
Krisztian (Apple) provides r06. We can only accept r06.
Josep (DT) comments, provides r07, would like to provide Rapporteur outline for possible SoH.
Pallab (Nokia) provides views. Can only accept r06
Changhong (Intel) provides r08 reflecting the solution without UE assistance.
Iskren (NEC) provides comments
Iskren (NEC) answers Pallab (Nokia)
Pallab (Nokia) responds to Iskren (NEC)
Josep (DT) replies to Pallab.
Haiyang (Huawei) provides r09 (based on r08), r10 (based on r07), and r11 (based on r05) to merge 8891
Masaharu (KDDI) provides comments
Belen (Ericsson) provides r12
Belen (Ericsson) provides r12 on top of r11.
Changhong (Intel) provides SoH slides for KI#2.
Yang (OPPO) supports the SoH slides proposed by Rapporteur
Pallab (Nokia) responds to Josep (DT)
Changhong (Intel) asks Haiyang to provide a non-corrupted revision for r09.
Josep (DT) replies.
Haiyang (Huawei) provides r13 (correction of r09)
Huazhang (vivo) reply to Changhong, that for the option B, whether the report via registration NAS or session related NAS is not determined now, so I prefer we have a general description:
Option B: UE reports URSP rule to network at during NAS procedure? (S2-2208346r05)
Josep (DT) replies to Pallab (Nokia).
Josep (DT) comments, provides r14, r15.
==== Revisions Deadline ====
Pavan (Google) provides some comments based on Josep (DT)'s updates
Changhong (Intel) replies to Huazhang and is surprised with your comments.
Changhong (Intel) updated the SoH slides to v3.
Pallab (Nokia) is OK to go with r11 as a way forward based on the SoH in CC#2, only if it is further revised to include a NOTE with warning on possible signaling load implications due to UE reporting at PDU Session Establishment/Modification. I will provide an acceptable NOTE text soon.
Masaharu (KDDI) supports to move forward with r11 and KDDI co-signs r11.
Chia-Lin (MediaTek) cannot accept r11 (from SoH) as way forward
Yang (OPPO) provides one comments in r11, r15.
Changhong (Intel) replies to Pallab and Intel cosigns r11.
Changhong (Intel) replies to Chia-Lin.
Haiyang (Huawei) clarifies to Yang (OPPO).
Hong (Qualcomm) comments.
Pallab (Nokia) responds to Changhong (Intel)
Krisztian (Apple) sustains objection to r11 as a way forward based on the SoH in CC#2 due to reasons discussed in-depth earlier in this mail thread and previous meetings.
Yang (OPPO) replies to Haiyang
Changhong (Intel) asks to polish the r11 and upload it to draft folder of FS_eUEPO.
==== Final Deadline ====
Krisztian (Apple) comments.
Josep (DT) comments, tries to summarize.
Pavan (Google) objects to r11
Krisztian (Apple) provides comments on Josep's summary.
Josep (DT) comments, provides draft r16 based on r11. Pending NOTE 2 to be provided.
Pallab (Nokia) provides the pending NOTE 2 text to be added on top of r16

NOTE 2: UE reporting the enforced URSP rule information in PDU Session Establishment/Modification can significantly increase the amount of signalling in the network. Care should be taken to ensure that such UE reporting is enabled for limited number UEs and limited number of applications.
Haiyang (Huawei) provides r17 based on r16
Josep (DT) provides some formatting clean-up and correction on cover sheet in r18.
Chia-Lin (MediaTek) provides r19 based on r18
Yang (OPPO) provides r19. Cannot agree the 'UPF based detection' related description.
Pallab (Nokia) provides r20 based on r19
Josep (DT) provides r21 trying to accommodate comments from r19 (MediaTek), lost r19 (Oppo) and r20 (Nokia).
Josep (DT) replies to Pallab (Nokia). Provides r22 on top of r21
Pallab (Nokia) responds to Josep (DT) and OK with r22
Dimitris (Lenovo) comments on the UPF-based detection description. Does not agree with r22
Pallab (Nokia) ask questions to Dimitris (Lenovo)
Haiyang (Huawei) provides r23 based on r22
Haiyang (Huawei) responds to Yang (OPPO)
Josep (DT) comments on Haiyang's (Huawei) and Dimitri's (Lenovo) comment.
Haiyang (Huawei) responds to Josep (DT)
Dimitris (Lenovo) ok with r23
Antoine (Orange) provides r24 to fix an accidental deletion of 'and'.
Krisztian (Apple) objects to r25.
Haiyang (Huawei) provides r25
Krisztian (Apple) objects to r24 and previous revisions.
Josep (DT) replies to Krzistian, provides r26.
Belen (Ericsson) asks Josep (DT) to present changes on top of r23 on CC#4.
Antoine (Orange) provides r27 as an alternative to r26 but also accept r26.
Josep (DT) replies to Belén (Ericsson): OK to present the changes. Uploaded revisions to CC#4 folder.
Revised
9.22 S2-2209957 P-CR Approval 23.700-85: KI#2, Evaluation and Conclusions. Ericsson, Deutsche Telekom, Orange, Vodafone, Telef nica, KDDI, Intel, NEC Rel-18 Revision of S2-2208346r27. CC#4: No consensus. Noted Noted
9.22 S2-2210163 LS OUT Approval [DRAFT] LS on Introduction of URSP Rule ID Deutsche Telekom Created at CC#3. Postponed to CC#4. CC#4: No consensus. Noted Josep (DT) provides first draft of the LS requested at CC#3.
Hong (Qualcomm) comments.
Antoine (Orange) provides r01 with the change proposed by Hong.
Pavan (Google) agrees with Hong (Qualcomm) and wonders if it is premature to send the LS now.
Antoine (Orange) replies that this LS is not tasking CT1 to do any work but just asking questions.
Huazhang (vivo) provides r02 that the URSP rule ID is equal to TD precedence + RSD precedence, so this question should be delivered to CT1, and for last sentence, I use () to include the option A and B to make this clear to reading.
Haiyang (Huawei) agrees with Yang (OPPO) and provides r03.
Yang (OPPO) comments
Josep (DT) cleans up a bit, adds comment from Yang (Oppo), provides r04.
Belen (Ericsson) provides comments
Antoine (Orange) comments.
Josep (DT) cleaned-up, added further input, provides r06, please disregard r05.
Belen (Ericsson) ok with r06
Yang (OPPO) is fine to r04, but concern to r05 and r06 due to too much subjective assesment
Josep (DT) tries to apply suggested changes, provides r08, may have uploaded r07 by mistake.
Belen (Ericsson) replies to OPPO
Antoine (Orange) provides r09; also accepts r08.
Belen (Ericsson) prefers r08 but it is okay with r09
Belen (Ericsson) prefers r09, not okay with r08
Thanks for the updating. OPPO is fine to r09
Noted
9.22 S2-2208634 LS OUT Approval [DRAFT] LS on impact of URSP rule enforcement report to 5GC vivo Rel-18 r04 agreed. Revised to S2-2209327. Josep (DT) comments, provides r01.
Haiyang (Huawei) supports to remove SA1 part and comments.
Huazhang (vivo) provide r02 based on r01
Josep (DT) comments, provides r03.
Huazhang (vivo) comments to URSP rule ID
Josep (DT) comments, provides r04.
Huazhang (vivo) thanks Josep, and this version is ok and see other's suggestions
==== Revisions Deadline ====
Huazhang (vivo) is ok with r04 and propose to go with r04, thanks for your help Josep
==== Final Deadline ====
Revised
9.22 S2-2209327 LS OUT Approval LS on impact of URSP rule enforcement report to 5GC SA WG2 Rel-18 Revision of S2-2208634r04. Approved Approved
9.22 S2-2208787 P-CR Approval 23.700-85: KI#2, Evaluation and way forward proposal . China Telecom Rel-18 Merged into (Covered by) S2-2208206 Changhong (Intel) proposes to merge this paper into S2-2208206.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208804 P-CR Approval 23.700-85: KI#2 Conclusions: Supporting URSP enforcement for well known app traffic to specific S-NSSAI/DNN. Lenovo Rel-18 r07 agreed. Revised to S2-2209328. Changhong (Intel) proposes to use this paper as baseline for UPF reporting to NWDAF for analytics.
Yang (OPPO) comments to the new NWDAF analytics
Dimitris (Lenovo) responds
Josep (DT) disagrees with Yang (OPPO).
Yang (OPPO) comments and concerns
Yang (OPPO) replies why the solution doe not work
Josep (DT) provides an example.
Haiyang (Huawei) comments
Yang (OPPO) provides comments.
Dimitris (Lenovo) does not understand Oppo's concerns
Yang (OPPO) further replies to Dimitris
Dimitris (Lenovo) provides additional responses
Belen (Ericsson) provides r01
Dimitris (Lenovo) provides responses
Yang (OPPO) responds to Dimirtris
Dimitris (Lenovo) provides r02 and responds
Haiyang (Huawei) have comments
Yang (OPPO) cannot agree r00-r02
Pallab (Nokia) shares the same view as Yang (OPPO)
Dimitris (Lenovo) responds and provides r03
Dimitris (Lenovo) provides r04
Yang (OPPO) provides r05 and can only accept r05
Dimitris (Lenovo) provides r06 to align with KI objectives
Yang (OPPO) provides r07 based on r06
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.22 S2-2209328 P-CR Approval 23.700-85: KI#2 Conclusions: Supporting URSP enforcement for well known app traffic to specific S-NSSAI/DNN. Lenovo Rel-18 Revision of S2-2208804r07. Approved Approved
9.22 S2-2208891 P-CR Approval 23.700-85: KI#2 Evaluation and Conclusion. Intel, Lenovo, Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208346 Antoine (Orange) comments that the conclusion text does not clearly indicate what normative changes are recommended (if any).
Changhong (Intel) proposes to use this paper as baseline for UPF detection based solution without UE reporting.
Haiyang (Huawei) responds to Antoine (Orange)
Belen (Ericsson) objects to this contribution
Haiyang (Huawei) responds to Belen (Ericsson)
Changhong (Intel) replies to Belen (Ericsson) and asks to merge this paper into S2-2208346.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208974 P-CR Approval 23.700-85: EUEPO KI#2 Evaluation and Conclusion for KI#2. NEC Rel-18 Revision of (Noted) S2-2206404 from S2#152E. Merged into (Covered by) S2-2208206 Changhong (Intel) proposes to merge this paper into S2-2208206.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208988 P-CR Approval 23.700-85: KI #2, conclusion. Samsung Rel-18 Merged into (Covered by) S2-2208206 Changhong (Intel) proposes to merge this paper into S2-2208206.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2209112 P-CR Approval 23.700-85: Evaluation and conclusion for KI#2. Apple, Google, Nokia, Nokia Shanghai Bell, Oppo Rel-18 Noted Changhong (Intel) proposes to use this paper as baseline for UE reporting information out of PDU Session.
Haiyang (Huawei) comments that we should first focus on the discussion on 8648.
Belen (Ericsson) provides comments.
Krisztian (Apple) provides r01.
Changhong (Intel) asks to merge this paper into S2-2208346.
Hong (Qualcomm) also requests to merge this to 8364.
Belen (Ericsson) provides comments that 8364 does not include any of this conclusions so far.
==== Revisions Deadline ====
Krisztian (Apple) responds to Belen (Ericsson)
Josep (DT) objects to this pCR. SoH is based on 8364.
==== Final Deadline ====
Noted
9.22 - - - Evaluation and Conclusion for KI#3 (Provision consistent URSP to UE across 5GS and EPS) - - Docs:=6 -
9.22 S2-2208303 P-CR Approval 23.700-85: 23.700-85: Evaluation and Conclusions update for KI#3. Nokia, Nokia Shanghai Bell, KDDi Rel-18 CC#3: This was noted. Changhong (Intel) proposes to use this paper as baseline removing the second EN.
Yang (OPPO) comments
Pallab (Nokia) responds to Yang (OPPO)
Hong (Qualcomm) comments and cannot agree with the proposal.
Huazhang (vivo) comments
Pallab (Nokia) responds to Hong (Qualcomm) and Huazhang (vivo).
DongYeon (Samsung) comments.
Changhong (Intel) provides SoH slides for KI#3.
Pallab (Nokia) responds to DongYeon (Samsung)
==== Revisions Deadline ====
Pallab (Nokia) responds to Changhong (Intel) and requests to change the description for SoH on KI#3
DongYeon (Samsung) proposes change text on KI#3 SoH Slide, and replies to Pallab.
Pallab (Nokia) responds to DongYeon (Samsung). Cannot accept the proposed SoH text.
DongYeon (Samsung) replies to Pallab.
DongYeon (Samsung) provides SoH slide in CC#2 folder containing preferred text on KI#3.
Changhong (Intel) uploads v4 with removing all evaluation statement in slide #2.
==== Final Deadline ====
Noted
9.22 S2-2208304 DISCUSSION Discussion 23.700-85: Discussion on Evaluation and Conclusions update for KI#3. Nokia, Nokia Shanghai Bell Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.22 S2-2208347 P-CR Approval 23.700-85: KI#3: Update to conclusion solving EN. Ericsson Rel-18 CC#3: r03 + changes agreed. Revised to S2-2209946. Changhong (Intel) proposes to use this paper as baseline removing the third EN.
Huazhang (vivo) comments
DongYeon (Samsung) comments.
Belen (Ericsson) replies to comments and questions.
Changhong (Intel) asks for clarification.
Belen (Ericsson) replies to Intel
Yang (OPPO) provides a question
Changhong (Intel) replies to Belen.
Huazhang (vivo) provides a way forward to remove the UE impact in this paper.
DongYeon (Samsung) provides r01.
Belen (Ericsson) replies to OPPO
Belen (Ericsson) provides r02
DongYeon (Samsung) provides r03.
==== Revisions Deadline ====
Changhong (Intel) objects to r01, r02 and r03 and provides a draft r04 for CC#2 or 3 discussion.
==== Final Deadline ====
DongYeon (Samsung) is OK with draft-r04 provided by Changhong.
Huazhang (vivo) agree with DongYeon and ok to move forward with r04
Revised
9.22 S2-2209946 P-CR Approval 23.700-85: KI#3: Update to conclusion solving EN. Ericsson Rel-18 Revision of S2-2208347r03 + changes. Approved Approved
9.22 S2-2208633 P-CR Approval 23.700-85: KI#3: Evaluation and Conclusion update. Vivo Rel-18 Merged into (Covered by) S2-2208892 DongYeon (Samsung) comments, and provides r01.
Belen (Ericsson) objects to r00 and r01, provides comments.
Huazhang (vivo) ask to clarify, how to understand 'the (H-)PCF in roaming and the PCF in non-roaming may register to the BSF (not shall or must) as the PCF serving this UE'
Belen (Ericsson) replies to vivo again that the BSF is conditional (and not optional)
Huazhang (vivo) reply to Belen
Changhong (Intel) agrees with Belen that BSF should be deployed as conditional to make the feature work.
Changhong (Intel) provides r02.
Belen (Ericsson) is okay with r02
Pallab (Nokia) comments on r02.
Pallab (Nokia) provides r03.
Belen (Ericsson) objects to r03
Huazhang (vivo) provides r04
==== Revisions Deadline ====
Changhong (Intel) proposes to approve r02.
Pallab (Nokia) proposes to approve r03. Objects to all other revisions including r00
DongYeon (Samsung) supports r02. r03 is conditionally OK when 1) change 'AMF shall use the Nbsf_Management discovery service' to 'AMF queries BSF'.
Belen (Ericsson) can accept r02, objects to r01,r01 and initial version.
Changhong (Intel) propose to NOTE this paper and use the thread of S2-2208892 for discussion in order to avoid cross checking.
Huazhang (vivo) ask whether whether we can approve r02, to change the note as below:

NOTE: BSF needs to be deployed in order to ensure a single UE-PCF is selected for a UE in both EPS and 5GS. Whether AMF queries BSF to discover the PCF and PCF set that may be already serving a UE policy association for the UE in EPS should be re-evaluate in normative phase.
Huazhang (vivo) is ok to keep one discussion and suggest to merge this paper to S2-2208892
Belen (Ericsson) can accept the initial revision, and objects to all other revisions
Belen (Ericsson) can accept r02, objects to r01,r03 and initial version.
Huazhang (vivo) provides r04 and whether we can move forward of this.
NOTE: Whether BSF is involved in order to ensure a single UE-PCF is selected for a UE in both EPS and 5GS should be re-evaluate during normative phase.
==== Final Deadline ====
Merged
9.22 S2-2208892 P-CR Approval 23.700-85: KI#3: Update on Conclusion. Intel, OPPO, Qualcomm Rel-18 Noted Changhong (Intel) proposes to use this paper as baseline removing the first EN.
Pallab (Nokia) comments for clarification and further discussion.
Changhong (Intel) replies to Pallab and provides r02.
Pallab (Nokia) provides comments on r02.
Changhong (Intel) replies to Pallab.
Pallab (Nokia) responds to Changhong (Intel).
DongYeon (Samsung) comments. Note that there's no r02 yet. The previous comments must be for r01.
Pallab (Nokia) responds to Changhong (Intel) and provides r03.
Pallab (Nokia) responds to DongYeon (Samsung).
Belen (Ericsson) provides comments
Changhong (Intel) replies to Pallab and clarifies that r02 was not provided, it was a typo.
Changhong (Intel) comments on r03.
Huazhang (vivo) don't understand why UE should give the indication to 5GC, does the 5GC didn't know to use which association to deliver policy to UE?
The 5GC or EPS can well solved the problem of multiple UE policy association, and also, 5GC and EPS can know where the UE is.
Huazhang (vivo) can't accept r03
Pallab (Nokia) responds to Changhong (Intel) provides r04 that only removes the EN (no other text added in conclusion).
Pallab (Nokia) responds to Huazhang (vivo).
Pallab (Nokia) provides r05.
Huazhang (vivo) reply to Pallab
Huazhang (vivo) thanks Pallab, that maybe the BSF is the only way forward to reduce the impact, thanks. Let me check further.
Pallab (Nokia) responds to Changhong (Intel) and provides r06. Which revision is agreed for this pCR is dependent on the decision of tdoc S2-2208633
==== Revisions Deadline ====
Changhong (Intel) proposes to approve r05.
Huazhang (vivo) only agree with r05 and object any other version
Pallab (Nokia) proposes to approve r06. Objects to all other revisions.
Can accept r04 only if S2-2208633r03 is approved.
DongYeon (Samsung) supports r02, objects to r03 and r04. r05 is conditionally OK when 1) change 'AMF shall use the Nbsf_Management discovery service' to 'AMF queries BSF' + add 'NOTE: BSF needs to be deployed in order to ensure a single UE-PCF is selected for a UE in both EPS and 5GS.'
Changhong (Intel) provides draft r07.
Huazhang (vivo) can accept r07, the only way forward.
Pallab (Nokia) comments that bringing this discussion in this thread will cause more confusion and I do not see Ericsson participating in this thread and they were objecting to the changes proposed in r07 in 8633.
Belen (Ericsson) objects to r07 as well, it cannot accept a solution that is not discussed.
Changhong (Intel) comments.
==== Final Deadline ====
Noted
9.22 - - - Evaluation and Conclusion for KI#4 (Support standardized and operator-specific traffic categories in URSP) - - Docs:=6 -
9.22 S2-2208172 P-CR Approval 23.700-85: KI#4, Update to Note in Conclusions . AT&T, Meta USA, T Mobile USA, Orange Rel-18 Approved Belen (Ericsson) provides r01
Farooq(AT&T) expresses concern on r1
Haiyang (Huawei) also think CT1 is better to handle the work
==== Revisions Deadline ====
Farooq (AT&T) can accept only r00.
Dieter (Deutsche Telekom) also can only accept r00.
==== Final Deadline ====
Approved
9.22 S2-2208419 LS OUT Approval [DRAFT] LS OUT on supporting Traffic Categories Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208461 Changhong (Intel) proposes to merge this paper into S2-2208461.
Serge (T-Mobile USA) agrees to merge this paper into S2-2208461.
Haiyang (Huawei) is OK to merge this paper into S2-2208461.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.22 S2-2208461 LS OUT Approval [DRAFT] LS On UEPO Traffic Categories T-Mobile USA Inc. Rel-18 Approved. Revised by MCC to remove 'draft' in S2-2209348 Changhong (Intel) proposes to use this paper as baseline for the LS OUT to GSMA on Traffic Categories.
Serge (T-Mobile USA) proposes to merge 2208419 into this paper.
Dieter (Deutsche Telekom) prefers to keep the LS answer to GSMA in S2-2209036 separate from the information to CT1.
Changhong (Intel) is fine with keeping this paper and S2-2209036 separate.
Belen (Ericsson) provides r01
Farooq(AT&T) expresses concern on r01.
Haiyang (Huawei) also think CT1 is better to handle the work
Hong (Qualcomm) also supports leaving the definitions to CT1.
Serge (T-Mobile USA) comments and prefers r00.
Belen (Ericsson) provides comments
==== Revisions Deadline ====
Farooq (AT&T) can only accept r00.
Dieter (Deutsche Telekom) also can only accept r00.
==== Final Deadline ====
Revised
9.22 S2-2209348 LS OUT Approval LS on UEPO Traffic Categories SA WG2 Rel-18 Revision of S2-2208461. Approved Approved
9.22 S2-2209036 LS OUT Approval [DRAFT] LS on Traffic Categories Deutsche Telekom Rel-18 Revision of S2-2209027. Response to S2-2203657 (Replied to at S2#151E). r03 agreed. Revised to S2-2209329. Changhong (Intel) proposes to merge this paper into S2-2208461.
Dieter (Deutsche Telekom) prefers to keep the LS answer to GSMA in S2-2209036 separate from the information to CT1.
Farooq (AT&T) would like to keep the content of the GSMA LS aligned with the conclusions of the TR as was done in CT LS even if it is sent as a separate LS to GSMA
Hong (Qualcomm) provide r01.
Farooq(AT&T) provides r02.
Changhong (Intel) provide r02.
Changhong (Intel) asks Farooq to provide r03.
Haiyang(Huawei) provides r03.
Belen (Ericsson) provides r04
Farooq(AT&T) expresses concern on r04.
Haiyang (Huawei) also think CT1 is better to handle the work
Curt (Meta) shares the same view as Farooq (ATT).
==== Revisions Deadline ====
Farooq (AT&T) can accept only r03.
Dieter (Deutsche Telekom) also can only accept r03.
==== Final Deadline ====
Revised
9.22 S2-2209329 LS OUT Approval LS on Traffic Categories SA WG2 Rel-18 Revision of S2-2209036r03. Approved Approved
9.22 - - - Documents exceeding TU Budget - - Docs:=1 -
9.22 S2-2208418 DRAFTCR Endorsement New value of Connection Capability Huawei, HiSilicon Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.23 - - - Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) - - Docs:=104 -
9.23 - - - Key Issue #1: How to improve correctness of NWDAF analytics - - Docs:=8 -
9.23 - - - Solution updates - - Docs:=7 -
9.23 S2-2208230 P-CR Approval 23.700-81: KI#1, Sol#1: Update to remove ENs. Ericsson Rel-18 r01 agreed. Revised to S2-2209632. Xiaobo (vivo) provides r01, clarifying how MTLF provide Multiple Models.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209632 P-CR Approval 23.700-81: KI#1, Sol#1: Update to remove ENs. Ericsson, vivo Rel-18 Revision of S2-2208230r01. Approved Approved
9.23 S2-2208243 P-CR Approval 23.700-81: KI#1: Terminology updates to Sol #29. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208309 P-CR Approval 23.700-81: Update to solution#61 to remove EN China Telecom Rel-18 r01 agreed. Revised to S2-2209633. Zhang (Ericsson) ask for clarification
Menghan(China Telecom) replies to Zhang(Ericsson).
Menghan(China Telecom) provides r01
Zhang (Ericsson) OK with r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209633 P-CR Approval 23.700-81: Update to solution#61 to remove EN. China Telecom Rel-18 Revision of S2-2208309r01. Approved Approved
9.23 S2-2208620 P-CR Approval 23.700-81: KI#1, Sol#3: Sol Update: Accuracy based NWDAF Analytics Correctness Improvement . Vivo Rel-18 r01 agreed. Revised to S2-2209634. Costas (Lenovo) provides an editorial suggestion and asks for clarification
Xiaobo (vivo) provides r01 and provide clarification to Costas (Lenovo)
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209634 P-CR Approval 23.700-81: KI#1, Sol#3: Sol Update: Accuracy based NWDAF Analytics Correctness Improvement . Vivo Rel-18 Revision of S2-2208620r01. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=11 -
9.23 S2-2208232 P-CR Approval 23.700-81: KI#1: Updates to Conclusions for KI#1. Ericsson Rel-18 Merged into (Covered by) S2-2208621 Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208621 .
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208236 P-CR Approval 23.700-81: KI#1: Updates to Overall Evaluation for KI#1. Ericsson Rel-18 r06 agreed. Revised to S2-2209635, merging S2-2208417, S2-2208887 and S2-2209060 Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for evaluation.
Antoine (Orange) provides r01, merging in S2-2208887.
Antoine (Orange) provides r04, updating the evaluation of Sol#62.
Fabio (Nokia) provides r05.
Dimitris (Lenovo) provides r06
Zhang (Ericsson) is OK with r05 and r06
==== Revisions Deadline ====
Dimitris (Lenovo) is only ok with r06
==== Final Deadline ====
Revised
9.23 S2-2209635 P-CR Approval 23.700-81: KI#1: Updates to Overall Evaluation for KI#1. Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ETRI, Orange, China Mobile M2M Company Ltd. Rel-18 Revision of S2-2208236r06, merging S2-2208417, S2-2208887 and S2-2209060. Approved Approved
9.23 S2-2208417 P-CR Approval 23.700-81: KI#1: Updating Evaluation and conclusion on KI#1. Huawei, HiSilicon Rel-18 Merged into S2-2209635 Xiaobo (vivo) on behalf of rapporteur proposes to merge this into S2-2208236 (evaluation part) and S2-2208621(conclusion part), respectively.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208468 P-CR Approval 23.700-81: KI#1: Update of KI#1 conclusion . ETRI Rel-18 Revised to S2-2208887 Revised
9.23 S2-2208887 P-CR Approval 23.700-81: KI#1: Update of KI#1 evaluation and conclusion . ETRI, Orange Rel-18 Revision of S2-2208468. Merged into S2-2209635 Xiaobo (vivo) on behalf of rapporteur proposes to merge this into S2-2208236 (evaluation part) and S2-2208621(conclusion part), respectively.
Antoine (Orange) can consider this pCR merged into S2-2208236r01 but would like to keep S2-2208887 open in case no agreement is found on S2-2208236.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208544 P-CR Approval 23.700-81: KI#1, conclusion update: expand the scope of Accuracy information by adding updated analytics. China Telecom vivo Rel-18 Merged into (Covered by) S2-2208621 Jiahui (China Telecom) agrees this paper to be merged into S2-2208621.
Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208621 .
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208621 P-CR Approval 23.700-81: KI#1, conclusion Update . Vivo, China Telecom Rel-18 CC#4: r16 agreed. Revised to S2-2209971. Xiaobo (vivo) provides r01 by taking into account the content from S2-2208232 / S2-2208887 / S2-2208544 / S2-2208880 / S2-2209060 / S2-2208417 .
Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for conclusion.
Dimitris (Lenovo) provides initial comments
Zhang (Ericsson) object r00 and r01, provides r02
Haiyang (Huawei) provides r03
Fabio (Nokia) replies to comments from Zhang (Ericsson) and Dimitris (Lenovo)
Antoine (Orange) provides r04.
Soohwan (ETRI) provides r05.
Dimitris (Lenovo) provides r06
Xiaobo (vivo) provides r07 with clean revision.
Zhang (Ericsson) response to Fabio (Nokia)
Fabio (Nokia) answers to comments from Zhang (Ericsson)
Zhang (Ericsson) provides r08
Haiyang (Huawei) comments to r08
Haiyang (Huawei) provides r09
Xiaobo (vivo) provides r10 with sort of summary as well as further clean-up.
Haiyang (Huawei) objects r10.
Dimitris (Lenovo) provides r11
Haiyang (Huawei) provides r12.
Zhang (Ericsson) response to Haiyang (Huawei)
Haiyang (Huawei) response to Zhang (Ericsson)
Aihua(CMCC) suggests to make partial conclusion in this meeting.
Fabio (Nokia) provides r13 and comments
Xiaobo (vivo) provides r14 and comments.
==== Revisions Deadline ====
Haiyang (Huawei) can only accept r03~r07, r09, r12 and r13. Objects to others.
Dimitris (Lenovo) is ok with r14 but can live with r13 as a compromise
Xiaobo (vivo) support to go with r13 as a compromise to make progress.
Zhang (Ericsson) can ONLY accept r08, r10, r11, object all the other revision
Xiaobo (vivo) ask whether Zhang(Ericsson) could live with r14 and if yes, then propose to go with r14.
Zhang (Ericsson) can go with r14 with the EN Xiaobo proposed, also there are two bullets need to be deleted from r14
'Consumers of AnLF and MTLF services may be capable of checking the performance of analytics IDs and/or ML models and accordingly to generate performance information. Such performance information can be stored in such a way that other service consumers can retrieve it.'
'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request additional parameters related to input data and their granularity to assist MTLF in the ML model selection. When notifying the AnLF about a trained ML Model, the MTLF can include in the notification additional parameters related to input data and their granularity.'
Haiyang (Huawei) can live with r14 + replacing 'Editor's Note: Additional feedback information from an analytics consumer is FFS.'
To
' The analytics consumer NF making some decision may change the trend indicated by the prediction output, the analytics consumer NF may provide a unified feedback related to the effect of an analytics on the changes in network status after the consumption of analytics and how to define unified feedback and based on which logic is FFS '
Xiaobo (vivo) thanks Zhang(Ericsson) for the compromise and corporation and propose go with r14 with the updated EN + two bullets deleted from r14 proposed by Zhang(Ericsson).

Editor's Note: The analytics consumer NF making some decision may change the trend indicated by the prediction output, the analytics consumer NF may provide a unified feedback related to the effect of an analytics on the changes in network status after the consumption of analytics and how to define unified feedback and based on which logic is FFS '

Two bullets to be removed:

'Consumers of AnLF and MTLF services may be capable of checking the performance of analytics IDs and/or ML models and accordingly to generate performance information. Such performance information can be stored in such a way that other service consumers can retrieve it.'

'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request additional parameters related to input data and their granularity to assist MTLF in the ML model selection. When notifying the AnLF about a trained ML Model, the MTLF can include in the notification additional parameters related to input data and their granularity.'
Xiaobo (vivo) thanks Haiyang(Huawei) for the compromise and corporation and agree r14 as baseline to make progress this meeting.
Xiaobo (vivo) thanks Haiyang(Huawei) for the clarification and adds Huawei as co-signer and thanks Haiyang(Huawei) for the support.
Dimitris (Lenovo) supports the proposal to include the text suggested by Haiyang (Huawei)
Fabio (Nokia) is OK with r14 plus changes proposed by Haiyang (Huawei).
Fabio (Nokia) is not OK with the removal of the bullets as suggested by Zhang (Nokia) and suggests turning them into the following:

'- Consumers of AnLF and MTLF services may be capable of checking the performance of analytics IDs and/or ML models and accordingly to generate performance information. Such performance information can be stored in such a way that other service consumers can retrieve it.' Becomes the following EN:
'Editor's note: It is FFS if consumers of AnLF and MTLF services can generate and request storage of performance information in such a way that other service consumers can retrieve it.' And

'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request additional parameters related to input data and their granularity to assist MTLF in the ML model selection. When notifying the AnLF about a trained ML Model, the MTLF can include in the notification additional parameters related to input data and their granularity.'

Becomes :
'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request additional parameters related to input data to assist MTLF in the ML model selection. When notifying the AnLF about a trained ML Model, the MTLF can include in the notification additional parameters related to input data'
'Editor's Note: It is FFS if input data parameter should include data granularity'
==== Final Deadline ====
Zhang (Ericsson) propose modifications on the proposal from Fabio (Nokia)
Xiaobo (vivo) thanks all for the contributions and summarize the all agreed changes on top of r14.

r14 + updated Editor's Note + two modified bullets

1. replaced 'Editor's Note: Additional feedback information from an analytics consumer is FFS.' with ' The analytics consumer NF making some decision may change the trend indicated by the prediction output, the analytics consumer NF may provide a unified feedback related to the effect of an analytics on the changes in network status after the consumption of analytics and how to define unified feedback and based on which logic is FFS '

2. replaced '- Consumers of AnLF and MTLF services may be capable of checking the performance of analytics IDs and/or ML models and accordingly to generate performance information. Such performance information can be stored in such a way that other service consumers can retrieve it ' with 'Editor's note: It is FFS if consumers of AnLF and MTLF services can generate and request storage of performance information in such a way that other service consumers can retrieve it.'

3. replaced

'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request additional parameters related to input data and their granularity to assist MTLF in the ML model selection. When notifying the AnLF about a trained ML Model, the MTLF can include in the notification additional parameters related to input data and their granularity.'

with

'- When requesting an ML model via the MLModelProvision service, the AnLF can specify in the request the information about input data type to assist MTLF in the ML model selection'
'Editor's Note: It is FFS if data granularity also included in the request'
Fabio (Nokia) thanks Xiaobo (Vivo) for the summary and is OK with it.
Antoine (Orange) provides r15 = r14 + updated Editor's Note + two modified bullets.
Revised
9.23 S2-2209971 P-CR Approval 23.700-81: KI#1, conclusion Update . Vivo, China Telecom, China Mobile, Ericsson, Huawei, Orange, ETRI, Lenovo, Nokia,CATT Rel-18 Revision of S2-2208621r16. Approved Approved
9.23 S2-2208880 P-CR Approval 23.700-81: KI#1 Update the Evaluation and Conclusion. China Mobile Rel-18 Merged into (Covered by) S2-2208621 Zhang (Ericsson) indicate the evaluation part is merged into S2-2208236, the conclusion updates are merged into S2-2208621
Aihua (CMCC) confirms this paper can be merged into S2-2208621.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2209060 P-CR Approval 23.700-81: KI#1: Updates of Evaluation and Conclusions. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209635 Xiaobo (vivo) on behalf of rapporteur proposes to merge this into S2-2208236 (evaluation part) and S2-2208621(conclusion part), respectively.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 - - - Key Issue #2: NWDAF-assisted application detection - - Docs:=27 -
9.23 - - - Solution updates - - Docs:=3 -
9.23 S2-2208666 P-CR Approval 23.700-81: KI #2, Sol #9: Update to make clarification on ENs . China Mobile, Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208670 P-CR Approval 23.700-81: KI#1, updates to solution#9 in TR23.700-81. OPPO Rel-18 r01 agreed. Revised to S2-2209636. Thomas (Nokia) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209636 P-CR Approval 23.700-81: KI#1, updates to solution#9 in TR23.700-81. OPPO Rel-18 Revision of S2-2208670r01. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=7 -
9.23 S2-2208431 P-CR Approval 23.700-81: KI#2 Conclusion Updates to reduce network load. Nokia, Nokia Shanghai Bell Rel-18 CC#4: r04 agreed. Revised to S2-2209972. Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for conclusion.
Thomas (Nokia) provides r01 to perform merge suggested by rapporteur
Belen (Ericsson) provides r02
Yang (OPPO) is okay with r01 but not ok with r02
Belen (Ericsson) provides comments
Yang (OPPO) replies and provides r03
Malla (NTT DOCOMO) replies to Yang (OPPO)
Yang (OPPO) replies to Malla (DOCOMO)
==== Revisions Deadline ====
Wang Yuan (Huawei) suggests a way forward to use r03 as basis and remove the last sentence in Note 3
Belen (Ericsson) objects to r03, ok with r02
Belen (Ericsson) objects to r01
Thomas(Nokia) suggest agreeing r00
Aihua(CMCC) suggests to go with r02, with one LS sending out to check user consent with SA3.
Yang (OPPO) asks question to Ericsson
Lei(Tencent) agrees with Yang that user consent is needed thus object r02.
==== Final Deadline ====
Yang (OPPO) privides drat LS to SA3 about the user consent.
Wang Yuan (Huawei) is OK to agree r00 at this meeting if r02 or all other revisions cannot be agreed..
Aihua(CMCC) prefer r02, but can live with r00.
Thomas(Nokia) uploaded late r04 as possible compromise
Belen (Ericsson) is okay with r04 as compromise, then wait for SA3 feedback
Yang (OPPO) is fine to 'r04+LSout'.
Aihua(CMCC) is fine to r04+SA3 LS as a way forward.
Wang Yuan (Huawei) is also fine with r04 + SA3 LS as way forward
Revised
9.23 S2-2209972 P-CR Approval 23.700-81: KI#2 Conclusion Updates. Nokia, Nokia Shanghai Bell, Ericsson, Oppo Rel-18 Revision of S2-2208431r04. Approved Approved
9.23 S2-2210159 LS OUT Approval [DRAFT] LS_out_to SA WG3_for_user_consent_for_appliaction_detection China Mobile CC#4: r01 agreed (The LS title should be corrected). Revised to S2-2209973. Yang (OPPO) provides drat LS to SA3 about the user consent.
Thomas (Nokia) provides r01
Revised
9.23 S2-2209973 LS OUT Approval LS on User consent for Application Detection SA WG2 - Revision of S2-2210159r01. Approved Approved
9.23 S2-2208672 P-CR Approval 23.700-81: Evaluation and Conclusion for KI#2. China Mobile, Ericsson Rel-18 r01 agreed. Revised to S2-2209637. Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for evaluation and merge its conclusion part into S2-2208431 .
Thomas (Nokia) provides r01 to remove conclusion part as suggested by rapporteur
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209637 P-CR Approval 23.700-81: Evaluation and Conclusion for KI#2. China Mobile, Ericsson Rel-18 Revision of S2-2208672r01. Approved Approved
9.23 S2-2208686 P-CR Approval 23.700-81: Updates to conclusion for KI#2 in TR23.700-81. OPPO Rel-18 Merged into (Covered by) S2-2208431 Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208431 .
Thomas (Nokia) suggest to merge this PCR into S2-2208431 as suggested by rapporteur
Yang (OPPO) agree to merge 8686 to 8431
Belen (Ericsson) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 - - - Key Issue #3: Data and analytics exchange in roaming case - - Docs:=18 -
9.23 - - - Solution updates - - Docs:=6 -
9.23 S2-2208622 P-CR Approval 23.700-81: KI#3, Sol#37, #38, #39, #40: Sol Update to extend user consent information for roaming cases. Vivo Rel-18 r02 agreed. Revised to S2-2209638. Thomas (Nokia) provides r01
Jungshin (Samsung) provides r02
Vivian(vivo) thanks Thomas (Nokia) and Jungshin (Samsung) for providing wording improvements, and is fine with r02.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209638 P-CR Approval 23.700-81: KI#3, Sol#37, #38, #39, #40: Sol Update to extend user consent information for roaming cases. Vivo Rel-18 Revision of S2-2208622r02. Approved Approved
9.23 S2-2208623 P-CR Approval 23.700-81: KI #3, Sol#39 Update . Vivo Rel-18 Revision of (Unhandled) S2-2206418 from S2#152E. r03 agreed. Revised to S2-2209639. Thomas (Nokia) raises concerns
Juan Zhang (Qualcomm) provides comments
Vivian(vivo) replies to Juan Zhang (Qualcomm) and Thomas(Nokia)'s comments and provides r01.
Juan Zhang (Qualcomm) replies to Vivian (vivo).
Vivian(vivo) replies to Juan Zhang (Qualcomm)'s comment and provides r02.
Juan Zhang (Qualcomm) is OK with r02.
Thomas(Nokia) provides r03.
Vivian(vivo) replies to Thomas(Nokia) and can live with r03.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209639 P-CR Approval 23.700-81: KI #3, Sol#39 Update . Vivo Rel-18 Revision of S2-2208623r03. Approved Approved
9.23 S2-2209106 P-CR Approval 23.700-81: Update on Solution #40. Samsung Rel-18 r01 agreed. Revised to S2-2209640. Thomas (Nokia) raises concerns
Vivian(vivo) provides comments
Jungshin (Samsung) provides clarification and r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209640 P-CR Approval 23.700-81: Update on Solution #40. Samsung Rel-18 Revision of S2-2209106r01. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=6 -
9.23 S2-2208397 P-CR Approval 23.700-81: KI#3 Conclusion Update to resolve editor s notes. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209681 Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208856 .
Thomas (Nokia) agrees to merge this PCR to S2-2208856 .
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208708 P-CR Approval 23.700-81: Update the conclusion for KI#3. Huawei, HiSilicon Rel-18 Merged into S2-2209681 Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208856 .
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208856 P-CR Approval 23.700-81: KI#3 conclusions update. CATT Rel-18 CC#4: r10 + existing Editor's note agreed. Revised to S2-2209681, merging S2-2208397, S2-2208708 and S2-2209105 Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for conclusion.
Thomas (Nokia) provides r01
Zhang (Ericsson) provide comments
Xiaoyan (CATT) provides r02.
Jungshin (Samsung) provides comments on r02.
Vivian(vivo) provides comments and r03.
Malla (NTT DOCOMO) provides comments.
Zhang (Ericsson) provide r04
Vivian(vivo) provides comment and is fine with r04
Jungshin (Samsung) can accept r03 but cannot agree to r04.
Xiaoyan (CATT) replies to Jungshin (Samsung).
Juan Zhang (Qualcomm) provides r05.
Jungshin (Samsung) provides r06.
Vivian(vivo) replies to Juan Zhang (Qualcomm) and provides r07 based on r06.
Malla (NTT DOCOMO) objects r07.
Juan Zhang (Qualcomm) proposes the comments on r07.
Vivian (vivo) replies to Juan(Qualcomm) and Malla (NTT DOCOMO)'s comment
Thomas(Nokia) provides r08
Xiaoyan (CATT) objects to r08.
Thomas (Nokia) Provides r09.
Objects against r06
Zhang (Ericsson) provides r10
==== Revisions Deadline ====
Jungshin (Samsung) objects to r10, and can accept r08 and r09.
Vivian (vivo) can accept r08 and r09, and suggests to go with r09.
Wang Yuan (Huawei) support r10 and cannot agree with r09 and the comments from Jungshin (Samsung).
Zhang (Ericsson) can only accept r10, object all other revision
Vivian(vivo) can live with current r10, but still suggests to add r10 with an EN: whether other NF can also be the central NF is FFS.
Aihua(CMCC) agrees with the suggestion from Vivian, going with r10 with newly added EN.
Wang Yuan (Huawei) is OK with the suggestion from Vivian (Vivo), i.e., r10 with newly added EN to make progress.
Zhang (Ericsson) is OK with EN added on top of r10 'EN: whether other NF can also be the central NF is FFS.'
Thomas (Nokia) accepts r10 + 'EN: whether other NF can also be the central NF is FFS.'
Thomas(Nokia) objects against r02 to r07
==== Final Deadline ====
Jungshin (Samsung) propose to add an additional EN on top of r10.
'EN: Whether other NF can also be the central NF is FFS. Whether an NWDAF can be used to forward collected data to another PLMN is FFS.
Jungshin (Samsung) replies to Yuan (Huawei).
Wang Yuan (Huawei) thanks for the clarification and is OK with the way forward.
Jungshin (Samsung) objects to r10 +'EN: whether other NF can also be the central NF is FFS.', without additional note: Whether an NWDAF can be used to forward collected data to another PLMN is FFS.
Xiaobo(vivo) can understood Jungshin (Samsung) and is ok to add additional part if it is allowed by chair in CC#4 but would kindly request Jungshin (Samsung) to indicate its objection in time before final comments deadline.
Revised
9.23 S2-2209681 P-CR Approval 23.700-81: KI#3 conclusions update. CATT, Nokia, Nokia Shanghai-Bell, vivo Rel-18 Revision of S2-2208856r10 + existing Editor's note, merging S2-2208397, S2-2208708 and S2-2209105. Approved Approved
9.23 S2-2209104 P-CR Approval 23.700-81: Update on evaluation of KI#3. Samsung Rel-18 r01 agreed. Revised to S2-2209642. Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for evaluation.
Thomas (Nokia) comments that PCR assumes that changes in S2-2209106 are agreed
Jungshin (Samsung) provides clarification and r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209642 P-CR Approval 23.700-81: Update on evaluation of KI#3. Samsung Rel-18 Revision of S2-2209104r01. Approved Approved
9.23 - - - Key Issue #4: How to Enhance Data collection and Storage - - Docs:=35 -
9.23 - - - Solution updates - - Docs:=2 -
9.23 S2-2208882 P-CR Approval 23.700-81: KI#4 Update to Sol#64 and evaluation and conclusion. China Mobile Rel-18 r01 agreed. Revised to S2-2209643. Aihua (CMCC) provides r01 and comments
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209643 P-CR Approval 23.700-81: KI#4 Update to Sol#64 and evaluation and conclusion. China Mobile Rel-18 Revision of S2-2208882r01. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=7 -
9.23 S2-2208238 P-CR Approval 23.700-81: KI#4: Update to conclusion and solving EN. Ericsson Rel-18 r07 agreed. Revised to S2-2209644. Zhang (Ericsson) provides r01 by merging text from S2-2208707
Fabio (Nokia) provides comments and suggests including an EN about security.
Aihua (CMCC) provides r02
Malla (NTT DOCOMO) provides r03
Megha(Intel) provides comments
Aihua (CMCC) provides r04
Fabio (Nokia) provides comments to r04.
Wang Yuan (Huawei) objects to r03 and r04 for MTLF directly sending ML model to ADRF.
Malla (NTT DOCOMO) replies to Wang Yuan (Huawei).
Zhang (Ericsson) provides r05
Aihua (CMCC) provides r06
Zhang (Ericsson) is OK with r06
Zhang (Ericsson) objects r05 and r06
Wang Yuan (Huawei) replies to Malla (DOCOMO)
Aihua(CMCC) suggests making a partial conclusion in this meeting and provides r07.
Zhang (Ericsson) is OK with r07
==== Revisions Deadline ====
Wang Yuan (Huawei) is also OK with r07
Malla (NTT DOCOMO) previous objections to r05 and r06 is from NTT DOCOMO, not Ericsson. I forgot to update the name and affiliation, my apologies mainly to Zhang (Ericsson).
Malla (NTT DOCOMO) replies to Wang Yuan (Huawei) and can live with r07.
Megha (Intel) is ok with r07.
==== Final Deadline ====
Revised
9.23 S2-2209644 P-CR Approval 23.700-81: KI#4: Update to conclusion and solving EN. Ericsson, Huawei, HiSilicon Rel-18 Revision of S2-2208238r07. Approved Approved
9.23 S2-2208870 P-CR Approval 23.700-81: KI#4 Update the Evaluation and Conclusion. China Mobile Rel-18 CC#4: r07 agreed. Revised to S2-2209974. Approve r05 + changes? Aihua (CMCC) provides r02 as baseline for evaluation.
Aihua (CMCC) provides r01 and comments
Xiaobo (vivo) on behalf of rapporteur proposes to select this as baseline for evaluation and merge its conclusion part into S2-2209061 .
Fabio (Nokia) provides comments to Aihua and r03.
Zhang (Ericsson) object r00, r01, r02, r03, provides r04
Aihua (CMCC) provides clarification to Zhang (Ericsson)
Fabio (Nokia) objects to r04 and replies to comments from Zhang (Ericsson).
Zhang (Ericsson) response to Aihua (CMCC) and Fabio (Nokia)
Aihua (CMCC) clarify to Zhang (Ericsson)
Aihua (CMCC) replies to Zhang (Ericsson)
==== Revisions Deadline ====
==== Final Deadline ====
Fabio (Nokia) provides further arguments to support that text should be removed.
Revised
9.23 S2-2209974 P-CR Approval 23.700-81: KI#4 Update the Evaluation and Conclusion. China Mobile, Ericsson Rel-18 Revision of S2-2208870r07. Approved Approved
9.23 S2-2209061 P-CR Approval 23.700-81: KI#4: Evaluation and Conclusion for DCCF / MFAF relocation. Nokia, Nokia Shanghai Bell Rel-18 Noted Xiaobo (vivo) on behalf of rapporteur proposes this paper mainly focuses on conclusion for DCCF / MFAF relocation.
Zhang (Ericsson) provides r01
Aihua (CMCC) provides r02.
Zhang (Ericsson) response to Aihua (CMCC) and object r02
Aihua (CMCC) clarify to Zhang (Ericsson) and provides r03
Zhang (Ericsson) provides r04
Fabio (Nokia) prefers r03 and objects to r04. Comments are also provided.
Zhang (Ericsson) response to Fabio (Nokia)
==== Revisions Deadline ====
Zhang (Ericsson) can accept r01 and r04, object all the other versions
Aihua(CMCC) can't accept r01, prefer r03 and can live with r04.
Fabio (Nokia) suggests to replace the following sentence from r04 'For data consumer or central DCCF reselecting target DCCF , Solution 44 and 66 is the baseline for normative work' with 'When a DCCF is no longer able to serve a data consumer, procedures for DCCF re-selection and DCCF re-location are supported.'
Zhang (Ericsson) cannot accept what Nokia propose
==== Final Deadline ====
Noted
9.23 S2-2209062 P-CR Approval 23.700-81: KI#4: Evaluation and Conclusion for ADRF/NWDAF data management. Nokia, Nokia Shanghai Bell Rel-18 r07 agreed. Revised to S2-2209645. Xiaobo (vivo) on behalf of rapporteur proposes this paper mainly focuses conclusion on ADRF/NWDAF data management and its evaluation part merged into S2-2208870.
Fabio (Nokia) provides r01
Zhang (Ericsson) object r00 and r01, provide r02
Antoine (Orange) provides r03.
Aihua(CMCC) provides r04.
Zhang (Ericsson) provide r05
Fabio (Nokia) objects to r05 and provides r06.
Zhang (Ericsson) provide r07
==== Revisions Deadline ====
Fabio (Nokia) is OK with r07
==== Final Deadline ====
Revised
9.23 S2-2209645 P-CR Approval 23.700-81: KI#4: Evaluation and Conclusion for ADRF/NWDAF data management. Nokia, Nokia Shanghai Bell, Ericsson Rel-18 Revision of S2-2209062r07. Approved Approved
9.23 - - - Key Issue #5: Enhance trained ML Model sharing - - Docs:=2 -
9.23 - - - Solution updates - - Docs:=1 -
9.23 S2-2208235 P-CR Approval 23.700-81: KI#5, Sol#47: Clarify the relationship between Interoperability token and container. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 - - - Evaluations and conclusions - - Docs:=2 -
9.23 S2-2208239 P-CR Approval 23.700-81: KI#5: Update conclusion and solving EN. Ericsson Rel-18 r07 agreed. Revised to S2-2209646. Vivian (vivo) provides comments and suggests to add Interoperability token into conclusion.
Megha (Intel) provides comments/questions
Wang Yuan (Huawei) raises concerns on 'Representative Ratio' part
Malla (NTT DOCOMO) asks for clarification
Zhang (Ericsson) provide comment
Megha(Intel) provides further comments and raises concern on Representative Ratio parameter
Wang Yuan (Huawei) shares the same concerns with Megha (Intel) on the Representative Ratio parameter and suggest to remove it from the conclusion of KI#5
Zhang (Ericsson) response to Yuan (Huawei) and Megha (Intel)
Megha(Intel) responds to Zhang (Ericsson) and provides r02.
Vivian (vivo) provides r03 based on r02, adding Interoperability token into conclusion.
Soohwan (ETRI) provides r04 to align with KI#8 discussion.
Wang Yuan (Huawei) provides comment on adding interoperability token into conclusion in r03 and r04 and question what will be the normative work for this interoperability token.
Zhang (Ericsson) response to Yuan (Huawei) and Megha (Intel) and provide r05
Fabio (Nokia) asks a question to Zhang (Ericsson) for clarification
Zhang (Ericsson) response to Fabio (Nokia)
Fabio (Nokia) provides further comments to Zhang (Ericsson).
Wang Yuan (Huawei) objects r05 since the texts captured in the conclusion doesn't reflect what has been clarified for interoperability token.
Wang Yuan (Huawei) objects previous version as they didn't solve the concern regarding to interoperability token and provide r06.
Megha(Intel) provides r07 and comments
==== Revisions Deadline ====
Megha(Intel) is ok with r02 and r07 only, objects to all other revisions.
Wang Yuan (Huawei) is OK with r07.
Vivian (vivo) is OK with r06 and r07.
Zhang (Ericsson) is OK with r07
Fabio (Nokia) is OK with r07.
==== Final Deadline ====
Revised
9.23 S2-2209646 P-CR Approval 23.700-81: KI#5: Update conclusion and solving EN. Ericsson, vivo Rel-18 Revision of S2-2208239r07. Approved Approved
9.23 - - - Key issue #6: NWDAF-assisted URSP - - Docs:=4 -
9.23 - - - Solution updates - - Docs:=2 -
9.23 S2-2208641 P-CR Approval 23.700-81: KI#6, Update Solution#16: NWDAF supports to provide combination of RSCs performance. Vivo, China Telecom Rel-18 r04 agreed. Revised to S2-2209647. Huazhang (vivo) reply to Thomas(Nokia)
Thomas (Nokia) raises questions
Wang Yuan (Huawei) shares the same concerns with Thomas (Nokia) and still confused for the explanations.
Jihoon (ETRI) asks questions.
Thomas(Nokia) replies to Huazhang
Belen (Ericsson) provides comments.
Huazhang (vivo) reply to Jihoon (ETRI)
Huazhang (vivo) reply to Wang Yuan (Huawei)
Huazhang (vivo) reply to Thomas (Nokia)
Huazhang (vivo) provide r01 to reply the comments
Jihoon (ETRI) provides r02 with some comments.
Thomas (Nokia) replies to Huazhang
Huazhang (vivo) thanks Thomas's guidance
Huazhang (vivo) provides r03 based on r02 to reflect Thomas's suggestion, and thanks to Jihoon's revision and support
Belen (Ericsson) provides comments to r03, still asks how it is proposed to enhanced the NWDAF subscribe or request.
Huazhang (vivo) reply to Belen
Huazhang (vivo) provides r04 based on r03 to state clearly that what is new in the input. Including SSC mode, PDU session type
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209647 P-CR Approval 23.700-81: KI#6, Update Solution#16: NWDAF supports to provide combination of RSCs performance. Vivo, China Telecom, ETRI Rel-18 Revision of S2-2208641r04. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=7 -
9.23 S2-2208246 P-CR Approval 23.700-81: KI#6: Update to conclusion Solving EN. Ericsson Rel-18 WITHDRAWN Thomas (Nokia) provides r01
Abbas (Futurewei) provides r02
Belen (Ericsson) provides r03
Abbas (Futurewei) disagrees r03
Belen (Ericsson) provides comments
Abbas (Futurewei) replies Belen (Ericsson)
==== Revisions Deadline ====
Belen (Ericsson) objects to r02, can only accept r03.
Abbas (Futurewei) objects to r03, can only accept r02 or r03 with the addition that the parameters from enhanced 'Redundant Transmission Experience' are included.
==== Final Deadline ====
Withdrawn
9.23 S2-2208404 P-CR Approval 23.700-81: KI#6 Conclusion Updates to reduce network load. Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208640 P-CR Approval 23.700-81: Update evaluation and conclusion of KI#6. Vivo, China Telecom Rel-18 r04 agreed. Revised to S2-2209648. Thomas (Nokia) comments that this PCR relies S2-2208641 being agreed.
Belen (Ericsson) provides comments
Huazhang (vivo) reply to Belen
Huazhang (vivo) provides r01 to reflect the concerns
Jihoon (ETRI) provides r02 with some comments.
Huazhang (vivo) provides r03 based on r02, and thanks for Jihoon's support
Huazhang (vivo) provides R04 based on R03 to reflect what is the enhancement in input of analytic request
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209648 P-CR Approval 23.700-81: Update evaluation and conclusion of KI#6. Vivo, China Telecom, ETRI Rel-18 Revision of S2-2208640r04. Approved Approved
9.23 S2-2208699 P-CR Approval 23.700-81: Update evaluation and conclusions for KI#6. Huawei, HiSilicon Rel-18 Noted. CC#4: r05 agreed. Revised to S2-2209982. Huazhang (vivo) have comments
Thomas (Nokia) raises concerns
Yang (OPPO) comments and check if any new UE impact is there
Juan Zhang (Qualcomm) provides comments
Belen (Ericsson) provides comments, has concerns on this contribution.
Susan (Huawei) replies and provides r01.
Juan Zhang (Qualcomm) provides comments on r01.
Belen (Ericsson) still has concerns with r01
Susan (Huawei) replies to Juan (Qualcomm) and Belen (Ericsson), and provides r02.
Thomas(Nokia) comments that his concerns about new procedures for redundant transmission being out of scope have not been resolved in any revision
==== Revisions Deadline ====
Susan (Huawei) replies to Thomas (Nokia), and provides r03, and asks for CC#3 decision.
Thomas (Nokia) also has concerns with late r03.
==== Final Deadline ====
Susan (Huawei) replies to Thomas (Nokia) and provides r04.
Revised
9.23 S2-2209982 P-CR Approval 23.700-81: Update evaluation and conclusions for KI#6. Huawei, HiSilicon Rel-18 Revision of S2-2208699r05. Approved Approved
9.23 S2-2209203 P-CR Approval 23.700-81: KI#6, evaluation and conclusions update Futurewei Rel-18 LATE DOC: Rx 10/03 14:30. Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.23 - - - Key Issue #7: Enhancements on QoS Sustainability analytics - - Docs:=1 -
9.23 - - - Solution updates - - Docs:=1 -
9.23 S2-2208697 P-CR Approval 23.700-81: Clarifications on Solution #19 Alt#2. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 - - - Evaluations and conclusions - - Docs:=4 -
9.23 S2-2208696 P-CR Approval 23.700-81: Clarification on Evaluation and Conclusions for KI#7. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209649. Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208696 as baseline for evaluation.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209649 P-CR Approval 23.700-81: Clarification on Evaluation and Conclusions for KI#7. Huawei, HiSilicon Rel-18 Revision of S2-2208696r01. Approved Approved
9.23 S2-2208883 P-CR Approval 23.700-81: KI#7 Update to Conclusion. China Mobile Rel-18 r03 agreed. Revised to S2-2209650. Aihua (CMCC) provides r01 as the baseline for conclusion.
Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208883 as baseline for conclusion.
Lei (Tencent) provides comments and also r02 .
Fabio (Nokia) provides some comments
Susan (Huawei) replies and provides r03.
Lei(Tencent) provides some comments and correct the name within macro.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209650 P-CR Approval 23.700-81: KI#7 Update to Conclusion. China Mobile, Huawei, HiSilicon Rel-18 Revision of S2-2208883r03. Approved Approved
9.23 - - - Key Issue #8: Supporting Federated Learning in 5GC - - Docs:=0 -
9.23 - - - Solution updates - - Docs:=2 -
9.23 S2-2208231 P-CR Approval 23.700-81: KI#8, Sol#24: Update: Horizontal Federated Learning among Multiple NWDAFs. Ericsson Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208817 P-CR Approval 23.700-81: KI #8, Sol #24: Update to add the Service Area as one parameter. China Mobile Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 - - - Evaluations and conclusions - - Docs:=8 -
9.23 S2-2208242 P-CR Approval 23.700-81: KI#8: Update: Evaluation and Conclusions. Ericsson, Vivo Rel-18 r01 agreed. Revised to S2-2209651. Aihua(CMCC) on behalf of rapporteur proposes to merge conclusion part into S2-2208797.
Zhang (Ericsson) provide r01 based on rapporteur suggestion
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209651 P-CR Approval 23.700-81: KI#8: Update: Evaluation and Conclusions. Ericsson, Vivo Rel-18 Revision of S2-2208242r01. Approved Approved
9.23 S2-2208625 P-CR Approval 23.700-81: KI#8, conclusion Update . Vivo Ericsson Rel-18 Merged into (Covered by) S2-2208797 Aihua(CMCC) on behalf of rapporteur proposes to merge into S2-2208797.
==== Revisions Deadline ====
Vivian(vivo) agrees to merge this paper into S2-2208797.
==== Final Deadline ====
Merged
9.23 S2-2208642 P-CR Approval 23.700-81: KI#8, Conclusion update. Samsung Rel-18 Merged into (Covered by) S2-2208797 Aihua(CMCC) on behalf of rapporteur proposes to merge into S2-2208797.
==== Revisions Deadline ====
Hyesung (Samsung) confirms to merge this into S2-2208797.
==== Final Deadline ====
Merged
9.23 S2-2208698 P-CR Approval 23.700-81: KI#8: Update Evaluation and Conclusions. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209652. Aihua(CMCC) on behalf of rapporteur proposes to merge conclusion part into S2-2208797.
Zhang (Ericsson) provides comment
Susan (Huawei) replies to Zhang (Ericsson).
Yang (OPPO) provides r01 and think the situation in Sol#69 is just one use case
Zhang (Ericsson) object r01 and provide r02, since the paper is only focus on evaluation as suggested by rapporteur
Susan (Huawei) replies to Yang (OPPO) and Zhang (Ericsson)
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209652 P-CR Approval 23.700-81: KI#8: Update Evaluation and Conclusions. Huawei, HiSilicon Rel-18 Revision of S2-2208698r02. Approved Approved
9.23 S2-2208797 P-CR Approval 23.700-81: KI#8 Update to conclusion. China Mobile Rel-18 CC#4: r09 agreed. Revised to S2-2209975. Approve r08 + changes? Aihua (CMCC) provides r01.
Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208797 as baseline for conclusion.
Yang (OPPO) comments to r01
Dimitris (Lenovo) comments
Vivian (vivo) provides comments and r02
Megha(Intel) provides r03 and comments
Zhang (Ericsson) provides comments to r03
Xiaoyan (CATT) provides r04
Juan Zhang (Qualcomm) provides comments.
Dimitris (Lenovo) requests more clarifications
Aihua(CMCC) provides r05.
Vivian (vivo) replies to Dimitris (Lenovo) and Juan(Qualcomm)'s question
Yang (OPPO) suggest to clarify the principle#8 or reword the sentence
Fabio (Nokia) provides comments.
Zhang (Ericsson) provides r06
Hyesung (Samsung) provides clarification
Xiaoyan (CATT) provides r07
Susan (Huawei) replies and provides r08.
Zhang (Ericsson) ask for clarification
Susan (Huawei) replies to Zhang (Ericsson) and Dimitris (Lenovo).
Zhang (Ericsson) response to Susan (Huawei)
Susan (Huawei) replies to Zhang (Ericsson).
==== Revisions Deadline ====
Susan (Huawei) replies Zhang (Ericsson).
Dimitris (Lenovo) prefers r07. R08 can be accepted with a few modifications
Susan (Huawei) provides r09.
Susan (Huawei) asks for CC#2 discussion on r09.
Aihua(CMCC) is fine with r09.
Dimitris (Lenovo) is ok with the proposed changes on top of r08
Zhang (Ericsson) is OK with r09
Vivian(vivo) is OK with r09 and confirms to be as a co-author
Hyesung (Samsung) is fine with r09
==== Final Deadline ====
Revised
9.23 S2-2209975 P-CR Approval 23.700-81: KI#8 Update to conclusion. China Mobile, Huawei, CATT Rel-18 Revision of S2-2208797r09. Approved Approved
9.23 - - - Key Issue #9: Enhancement of NWDAF with finer granularity of location information - - Docs:=0 -
9.23 - - - Solution updates - - Docs:=4 -
9.23 S2-2208310 P-CR Approval 23.700-81: KI#9 Solution #59 updates to address editor s notes. Nokia, Nokia Shanghai Bell Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208761 P-CR Approval 23.700-81: KI#9: Solution 58 update addressing ENs. Lenovo Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.23 S2-2208930 P-CR Approval 23.700-81: KI#9, Sol #57: Update to resolve the EN related to the area defined with the finer granularity. Vivo Rel-18 r01 agreed. Revised to S2-2209653. Thomas (Nokia) provides r01
==== Revisions Deadline ====
Amy (vivo) agrees with r01
==== Final Deadline ====
Revised
9.23 S2-2209653 P-CR Approval 23.700-81: KI#9, Sol #57: Update to resolve the EN related to the area defined with the finer granularity. Vivo Rel-18 Revision of S2-2208930r01. Approved Approved
9.23 - - - Evaluations and conclusions - - Docs:=11 -
9.23 S2-2208342 P-CR Approval 23.700-81: KI#9 Location Accuracy Enhancements & Evaluation/Conclusion . Nokia, Nokia Shanghai Bell Rel-18 r06 agreed. Revised to S2-2209654, merging S2-2208857 and S2-2208928 Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208342 as baseline for evaluation.
Thomas (Nokia) provides r01
Xiao (Toyota) answers the questions for Solution #26 in this contribution.
Amy (vivo) provides r02, merges the S2-2208928 evaluation into 8342r02
Antoine (Orange) asks why Sol #26 and #70 are classified under Aspect 2 rather than Aspect 1.
Dimitris (Lenovo) provides r03 with clarifications for Sol#58
Xiao (Toyota) comments on r02. (No questions for the part added in r03)
Thomas(Nokia) questions whether 'aspects' added in r02 are helpful.
Amy (vivo) provides r04 and replies to Thomas, Antoine
Xiao (Toyota) provides r05
Thomas (Nokia) provides r06
Amy (vivo) replies to Thomas (Nokia)
Xiao (Toyota) is fine with r06.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209654 P-CR Approval 23.700-81: KI#9 Location Accuracy Enhancements Evaluation. Nokia, Nokia Shanghai Bell, vivo Rel-18 Revision of S2-2208342r06, merging S2-2208857 and S2-2208928. Approved Approved
9.23 S2-2208653 P-CR Approval 23.700-81: KI#9 Conclusion . Samsung, Orange Rel-18 r07 agreed. Revised to S2-2209655. Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208653 as baseline for Conclusion and focus on use cases..
Thomas (Nokia) provides r01
Xiao (Toyota) provides r02
Dimitris (Lenovo) comments
Zhang (Ericsson) provides comments to r01 and r02
Thomas (Nokia) prides r03
replies to Zhang (Ericsson)
Xiao (Toyota) is fine with r03
David (Samsung) is OK with r03
Amy (vivo) provides r05, to make this consistent with 8929
Thomas(Nokia) questions a change in r06
Zhang (Ericsson) provides comment to r06
Aoken (Rakuten Mobile) provides r06
David (Samsung) replies to Lenovo
Amy (vivo) provides r06, and answers to Thomas, Zhang
Amy (vivo) provides r07, to correct the name and copy the answers to Thomas and Zhang
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209655 P-CR Approval 23.700-81: KI#9 Conclusion . Samsung, Orange, Nokia, Nokia Shanghai-Bell, vivo Rel-18 Revision of S2-2208653r07. Approved Approved
9.23 S2-2208857 P-CR Approval 23.700-81: KI#9 Evaluation. CATT Rel-18 Merged into S2-2209654 Aihua(CMCC) on behalf of rapporteur proposes to merge into S2-2208342.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208858 P-CR Approval 23.700-81: KI#9 conclusions. CATT Rel-18 Merged into S2-2209685 Aihua(CMCC) on behalf of rapporteur proposes to merge into S2-2208929.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208928 P-CR Approval 23.700-81: KI #9, Evaluation for KI#9 Vivo Rel-18 Merged into S2-2209654 Aihua(CMCC) on behalf of rapporteur proposes to merge into S2-2208342.
Amy (vivo) merges 8928 into 8342
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208927 LS OUT Approval [DRAFT] LS on possibility of providing per UE speed and orientation on FS_eNA_Ph3 Vivo Rel-18 r01 agreed. Revised to S2-2209656. David (Samsung) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209656 LS OUT Approval LS on possibility of providing per UE speed and orientation on FS_eNA_Ph3 SA WG2 Rel-18 Revision of S2-2208927r01. Approved Approved
9.23 S2-2208929 P-CR Approval 23.700-81: KI #9, Conclusion for KI#9. Vivo Rel-18 r08 agreed. Revised to S2-2209685, merging S2-2208858 Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208929 as baseline for conclusion and focus on general principles.
Thomas (Nokia) provides r01
Amy (vivo) provides r02, a merged version based on rapporteur proposal
Dimitris (Lenovo) provides r03 suggesting additional conclusion text
Malla (NTT DOCOMO) asks for clarification
Xiao (Toyota) provides r04.
Amy (vivo) provides r05, and answers to Xiao, Malla and Thomas
David (Samsung) provides r06
Amy (vivo) provides r07
Thomas(Nokia) provides r08
==== Revisions Deadline ====
Amy (vivo) agrees with r08
Antoine (Orange) proposes to approve r08 with replacement of 'Analytics Filter Information' and ' analytics filter' by 'Analytics Reporting Information'.
Amy (vivo) proposes to agree with r08 with adding a NOTE to capture what Antoine means.
Thomas (Nokia) can agree r08 + NOTE: Where to include the preferred granularity of location information, e.g. 'Analytics Filter Information' or 'Analytics Reporting Information', is to be determined in the normative phase.
Antoine (Orange) also agrees to r08 + this Note.
==== Final Deadline ====
Revised
9.23 S2-2209685 P-CR Approval 23.700-81: KI #9, Conclusion for KI#9. Vivo, Nokia, Nokia Shanghai-Bell, Samsung, Orange, CATT, Toyota, NTT DOCOMO Rel-18 Revision of S2-2208929r08, merging S2-2208858. Approved Approved
9.23 - - - Key Issue #10: how NWDAF requests analytics from MDAS/MDAF - - Docs:=2 -
9.23 - - - Solution updates - - Docs:=3 -
9.23 S2-2208229 P-CR Approval 23.700-81: KI#3, Sol#10: Resolving remaining ENs. Ericsson Rel-18 r01 agreed. Revised to S2-2209641. Thomas (Nokia) raises concerns
Wang Yuan (Huawei) shares the same concerns with Thomas (Nokia) and don't think a standalone NF is needed.
Malla (NTT DOCOMO) agrees with Huawei and Nokia.
Jinsook (DISH) seeks for clarification
Jungshin (Samsung): We have the similar view as other companies, and do not agree to the proposed changes.
Zhang (Ericsson) provide response and surprise on the comments from other companies. Ericsson is just provide its view on its solution, Ericsson does not provide a conclusion or evaluation in this pCR
Malla (NTT DOCOMO) provided response.
Zhang (Ericsson) thanks Malla for the clarification
Thomas replies to Zhang
Zhang (Ericsson) provide r01
==== Revisions Deadline ====
Jinsook (DISH) anybody can clarify me?
==== Final Deadline ====
Revised
9.23 S2-2209641 P-CR Approval 23.700-81: KI#3, Sol#10: Resolving remaining ENs. Ericsson Rel-18 Revision of S2-2208229r01. Approved Approved
9.23 S2-2208982 P-CR Approval 23.700-81: KI#10: Enhancing solution #74 for supporting NWDAF interaction with MDAF . Lenovo Rel-18 Noted Belen (Ericsson) prefers that conclusions take relevant parts of solution#73 and #74
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.23 - - - Evaluations and conclusions - - Docs:=4 -
9.23 S2-2208785 P-CR Approval 23.700-81: KI#10: Evaluation and interim conclusions . Lenovo Rel-18 r01 agreed. Revised to S2-2209657. Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208785 as baseline for evaluation.
Dimitris (Lenovo) provides r01 as suggested by rapporteur
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209657 P-CR Approval 23.700-81: KI#10: Evaluation and interim conclusions . Lenovo Rel-18 Revision of S2-2208785r01. Approved Approved
9.23 S2-2208884 P-CR Approval 23.700-81: KI#10 Evaluation and Conclusion. China Mobile Rel-18 r04 agreed. Revised to S2-2209658. Aihua (CMCC) provides r01 as the baseline for conclusion.
Aihua(CMCC) on behalf of rapporteur proposes to use S2-2208884 as baseline for Conclusion.
Dimitris (Lenovo) provides r02
Wang Yuan (Huawei) raises concerns on r02.
Belen (Ericsson) provides r03, has concerns with previous revisions.
Dimitris (Lenovo) comments
Aihua (CMCC) provides r04.
Wang Yuan (Huawei) thanks Aihua (CMCC) for providing r04 and would like co-sign r04.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.23 S2-2209658 P-CR Approval 23.700-81: KI#10 Evaluation and Conclusion. China Mobile Rel-18 Revision of S2-2208884r04. Approved Approved
9.23 - - - Documents exceeding TU Budget - - Docs:=6 -
9.23 S2-2208706 DISCUSSION Discussion Discussion on the information exchange architecture between two PLMNs Huawei, HiSilicon Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.23 S2-2209063 P-CR Approval 23.700-81: KI#8: Updates to Evaluation and Conclusions. Nokia, Nokia Shanghai Bell Rel-18 Not Handled Zhang (Ericsson) ask if the paper is merged into S2-2208797
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.23 S2-2208624 P-CR Approval 23.700-81: KI#3, conclusion Update . Vivo Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.23 S2-2209105 P-CR Approval 23.700-81: Update on Conclusion for KI#3. Samsung Rel-18 Merged into S2-2209681 Xiaobo (vivo) on behalf of rapporteur proposes to merge this to S2-2208856 .
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.23 S2-2208707 P-CR Approval 23.700-81: Update the conclusion for KI#4. Huawei, HiSilicon Rel-18 Not Handled Zhang (Ericsson) indicate the paper is merged into S2-2208238
Wang Yuan (Huawei) confirms this paper is merged into S2-2208238
==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.23 S2-2208237 P-CR Approval 23.700-81: KI#10: Evaluation and Conclusion. Ericsson Rel-18 Not Handled ==== Revisions Deadline ====
==== Final Deadline ====
Not Handled
9.24 - - - Study on satellite access Phase 2 (FS_5GSAT_Ph2) - - Docs:=40 -
9.24 S2-2208284 P-CR Approval 23.700-28: KI#1/KI#2: Proposal towards conclusions. Ericsson Rel-18 Merged into (Covered by) S2-2208784 Stephen (Qualcomm) provides comments
Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208379 P-CR Approval 23.700-28: Preconditions of KI#1 and KI#2 conclusion. Nokia, Nokia Shanghai Bell Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208511 P-CR Approval 23.700-28: Update Evaluation & Conclusion. LG Electronics Rel-18 r02 agreed. Revised to S2-2209659. Yingying(CATT) provides comments.
Stephen (Qualcomm) provides comments
Jaewoo (LGE) replies to Yingying(CATT).
Jaewoo (LGE) replies to Stephen (Qualcomm).
Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
Jean Yves (Thales) comments
Jaewoo (LGE) responds to Jean Yves (Thales) and provides r01.
Stephen (Qualcomm) provides comments and an r02
Jean-Yves (Thales) comments
Jaewoo (LGE) responds to Stephen (Qualcomm) and provides comments.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r02 but not other versions
==== Final Deadline ====
Revised
9.24 S2-2209659 P-CR Approval 23.700-28: Update Evaluation & Conclusion. LG Electronics Rel-18 Revision of S2-2208511r02. Approved Approved
9.24 S2-2208531 P-CR Approval 23.700-28: KI#1 Sol#23 Update to apply Coverage Information Provisioning. Rakuten Mobile Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.24 S2-2208537 P-CR Approval 23.700-28: KI#1, KI#2: Evaluation. Qualcomm Incorporated Rel-18 r04 agreed. Revised to S2-2209660, merging S2-2208876 Jean-Yves (Thales) comments
Stephen (Qualcomm) replies to Jean-Yves (Thales)
Jean-Yves (Thales) replies to Stephen (Qualcomm)
Steve (Huawei) comments on how to merge - see first email on 8668
Stephen (Qualcomm) provides comments and an r01
DongYeon (Samsung) provides r02, and both of the latest version of 8668 and 8537 can go into the TR.
Jean-Yves (Thales) comments.
Jean-Yves (Thales) provides r03.
Jaewoo (LGE) provides r04.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r04 (as well as other versions)
==== Final Deadline ====
Revised
9.24 S2-2209660 P-CR Approval 23.700-28: KI#1, KI#2: Evaluation. Qualcomm Incorporated Rel-18 Revision of S2-2208537r04, merging S2-2208876. Approved Approved
9.24 S2-2208540 P-CR Approval 23.700-28: KI#1, KI#2: Conclusions. Qualcomm Incorporated Rel-18 Merged into (Covered by) S2-2208784 Yingying(CATT) provides comments.
Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
Stephen (Qualcomm) agrees the merger into S2-2208784 proposed by the rapporteur
==== Final Deadline ====
Merged
9.24 S2-2208668 P-CR Approval 23.700-28: Evaluation Update. Huawei, HiSilicon Rel-18 r04 agreed. Revised to S2-2209682, merging S2-2208848 Steve (Huawei) comments on how to merge.
Stephen (Qualcomm) provides comments and an r01
Yuxin (Xiaomi) replies to Steve(Huawei)
Yingying(CATT) provides r02.
Lalith(Samsung) provides r03.
Amy (vivo) provides r04.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree r04 (and r01, r02, r03) but not r00
Jean-Yves (Thales) cannot agree any revision until the question of §7.4.2 is solved (see mail on 9026 thread)
Steve (Huawei) is ok with r04 and 'With changes removed from this pCR for clauses 7.4.2 and 7.5.3 (i.e. no changes in 7.4.2 and 7.5.3 compared to the TR in this pCR).'
Jean Yves (Thales) is ok with r04 with below explanations (clause 7.4.2 in TR will come from 9026r02)
Yingying(CATT) agrees with r02, r03 and r04.
==== Final Deadline ====
Revised
9.24 S2-2209682 P-CR Approval 23.700-28: Evaluation Update. Huawei, HiSilicon Rel-18 Revision of S2-2208668r04, merging S2-2208848. Approved Approved
9.24 S2-2208669 P-CR Approval 23.700-28: Conclusion. Huawei, HiSilicon Rel-18 Merged into (Covered by) S2-2208784 Stephen (Qualcomm) provides comments
Steve (Huawei) comments
Stephen (Qualcomm) replies to Steve (Huawei)
Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
Steve (Huawei) is ok to MERGE to 8784.
==== Final Deadline ====
Merged
9.24 S2-2208677 P-CR Approval 23.700-28: Update Evaluation and Conclusion for KI#1 and KI#2. Google Inc. Rel-18 r01 agreed. Revised to S2-2209661. Jean-Yves (Thales) As per discussed way forward, proposes to merge this document into S2-2209184
Ellen (Google) agree to merged the second change (conclusion part) into S2-2209184 and propose to handle the first change (evaluation) in this 8677
Steve (Huawei) thinks we should consider the evaluation part merged to 8847?
Ellen (Google) clarify: 8847 and 8677r01 cover different aspects in Solution#13.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.24 S2-2209661 P-CR Approval 23.700-28: Update Evaluation and Conclusion for KI#1 and KI#2. Google Inc. Rel-18 Revision of S2-2208677r01. Approved Approved
9.24 S2-2208740 P-CR Approval 23.700-28: Evaluation update for coverage information provisioning to core network. Thales Rel-18 Noted Steve (Huawei) comments on how to merge - see first email on 8668
==== Revisions Deadline ====
Jean-Yves (Thales) proposes to note the document
==== Final Deadline ====
Noted
9.24 S2-2208754 P-CR Approval 23.700-28: Clarification on UE initiated Power Saving Mechanisms for Solution#21. Google Inc. Rel-18 r01 agreed. Revised to S2-2209662. Steve (Huawei) comments
Ellen (Google) feedbacks Steve (Huawei) comments
Yuxin(Xiaomi) comments
Stefan (Ericsson) comments
Jean-Yves (Thales) comments
Ellen (Google) thanks for the good comments and propose a way forward
Ellen (Google) provided r01 to capture comments from companies
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.24 S2-2209662 P-CR Approval 23.700-28: Clarification on UE initiated Power Saving Mechanisms for Solution#21. Google Inc. Rel-18 Revision of S2-2208754r01. Approved Approved
9.24 S2-2208784 P-CR Approval 23.700-28: Conclusions proposal for TR23.700-28. Thales Rel-18 CC#4: r22 agreed. Revised at CC#4 to S2-2209962. Jean-Yves (Thales) (rapporteur) provides a revision capturing a synthesis of Tdocs for conclusions and proposes it as single document to elaborate further conclusion on R1, R2, R5, R6
Steve (Huawei) comments
Stephen (Qualcomm) provides comments
Yingying(CATT) provides comments.
Jean-Yves (Thales) answers Stephen and clarifies the rapporteur proposal (if necessary)
Lalith (Samsung) provides r02
Yuxin (Xiaomi) replies to Lalith (Samsung) that r02 may have something wrong and cannot be opened
Jean-Yves (Thales) comment that r02 has word issue, and answer Yingying questions
Lalith (Samsung) provides r03
Yuxin (Xiaomi) provides r04
Stefan (Ericsson) provides r05
Lalith (Samsung) provides r06
Jaewoo (LGE) provides r07.
Hannu (Nokia) provides r08.
Steve (Huawei) comments and provides r10.
Steve (Huawei) provided r09, but there was a zipping error so please ignore it.
Ellen (Google) provides r011.
Stephen (Qualcomm) provides an r12
Jaewoo (LGE) replies to Ellen (Google) and provides comment.
Yingying(CATT) provides r13.
Amy (vivo) provides r14, adds info on paging enhancement
DongYeon (Samsung) comments: The EN regarding LS sending to CT1 regarding UP/CP based solution needs to be align with the result of S2-2209197.
Stefan (Ericsson) provides questions
Yuxin (Xiaomi) provides r15 to recover clause 8.3
Jaewoo (LGE) responds to Stefan (Ericsson).
Amy (vivo) provides r16
Lalith(Samsung) comments.
Steve (Huawei) provides r17
Jaewoo (LGE) replies to Lalith (Samsung) for clarification.
Jean-Yves (Thales) comments on r17 and provides r18, asks also clarification on one sentence.
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r12 and no other revision or version
Jean-Yves (Tales) responds to Stephen and requests to clarify a sentence
Yingying (CATT) replies to Stephen and can accept r13 and revisions after r13.
Steve (Huawei) comments in proposed change.
Stefan (Ericsson) comments
Steve (Huawei) comments on potential differences
Stefan (Ericsson) provides on potential differences
Hannu (Nokia) supports the latest version in r18.
Steve (Huawei) confirms it was about the bullet about RAN broadcasts
Amy (vivo) supports the latest version in r18.
Steve (Huawei) proposed to agree r18 the following change: The bullet 'Following Rel-17, the UE has UE unreachability information from RAN broadcasts.' Is changed to 'Following Rel-17, the UE has satellite assistance information for predication of discontinuous coverage from RAN broadcasts.'
Jean-Yves (Thales) cannot accepted r18 as is
==== Final Deadline ====
Yingying(CATT) agrees with the proposal.
Steve (Huawei) comments, suggested bullet rewording, and only 3rd bullet for UE needs to change.
Lockheed Martin would like to co-sign.
Thanks & KR
Prasad Chandratre (LMCO)
Revised
9.24 S2-2209962 P-CR Approval 23.700-28: Conclusions proposal for TR23.700-28. Thales, Huawei, Samsung, Lockheed Martin, Xiaomi, CATT Rel-18 Revision of S2-2208784r22. Approved Approved
9.24 S2-2208841 P-CR Approval 23.700-28: KI#1, Evaluation and conclusions for KI#1 R3 RAT/PLMN selection. Spreadtrum Communications Rel-18 Merge into S2-2209184 (Noted at CC#4). Noted Jean-Yves (Thales) As per discussed way forward, proposes to merge this document into S2-2209184
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.24 S2-2208847 P-CR Approval 23.700-28: KI#1: Evaluation of solutions. CATT Rel-18 r01 agreed. Revised to S2-2209663, merging S2-2208874 and S2-2209185 Steve (Huawei) comments on how to merge - see first email on 8668
Yuxin (Xiaomi) provides r01
==== Revisions Deadline ====
Jean-Yves (Thales) is OK with r01
Yingying(CATT) agrees with r01.
==== Final Deadline ====
Revised
9.24 S2-2209663 P-CR Approval 23.700-28: KI#1: Evaluation of solutions for alternative RAT/PLMN selection. CATT, Xiaomi Rel-18 Revision of S2-2208847r01, merging S2-2208874 and S2-2209185. Approved Approved
9.24 S2-2208848 P-CR Approval 23.700-28: KI#2: Evaluation of solutions. CATT Rel-18 Merged into S2-2209682 Steve (Huawei) comments on how to merge - see first email on 8668
Yingying(CATT) agrees to merge into S2-2208668 as a proposal.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208849 P-CR Approval 23.700-28: KI#1, Conclusion. CATT Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
Steve (Huawei) comments on how to merge - see first email on 8668
Steve (Huawei) Ignore the suggestion to merge from me, it should be merged to 8784.
Yingying(CATT) agrees to merge this T-doc into S2-2208784.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208850 P-CR Approval 23.700-28: KI#2, Conclusion. CATT Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
Yingying(CATT) agrees to merge this T-doc into S2-2208784.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208874 P-CR Approval 23.700-28: KI#1 solution evaluation. Xiaomi Rel-18 Merged into S2-2209663 Stephen (Qualcomm) provides comments
Yuxin(Xiaomi) provides r01
Steve (Huawei) comments on how to merge - see first email on 8668
Yuxin (Xiaomi) comments this p-CR is merged into S2-2208847 as per proposed
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208875 P-CR Approval 23.700-28: KI#1 solution conclusion . Xiaomi Rel-18 Merge into S2-2209184 (Noted at CC#4). Noted Jean-Yves (Thales) As per discussed way forward, proposes to merge this document into S2-2209184
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.24 S2-2208876 P-CR Approval 23.700-28: KI#1&KI#2: Evaluation of satellite coverage information provision. Xiaomi Rel-18 Merged into S2-2209660 Stephen (Qualcomm) provides comments
Steve (Huawei) comments on how to merge - see first email on 8668
==== Revisions Deadline ====
Stephen (Qualcomm) proposes to merge this into S2-2208537
Yuxin (Xiaomi) is fine to merge this into S2-2208537
Yuxin(Xiaomi) informs this p-CR has been merged into S2-2208537
==== Final Deadline ====
Merged
9.24 S2-2208877 P-CR Approval 23.700-28: KI#1&KI#2: Conclusion on satellite coverage information provision. Xiaomi Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208931 P-CR Approval 23.700-28: Conclusion of Key Issue #1 Paging enhancement aspect. Vivo Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208932 P-CR Approval 23.700-28: Conclusion of Key Issue #2. Vivo Rel-18 Merged into (Covered by) S2-2208784 Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2208933 P-CR Approval 23.700-28: Evaluation of signalling overload on target RAT/PLMN. Vivo Rel-18 r03 agreed. Revised to S2-2209664. Stephen (Qualcomm) provides an r01
Steve (Huawei) comments on how to merge - see first email on 8668
Amy (vivo) provides r02
Amy (vivo) provides r03
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r03
Jean-Yves (Thales) can agree the r03
==== Final Deadline ====
Revised
9.24 S2-2209664 P-CR Approval 23.700-28: Evaluation of signalling overload on target RAT/PLMN. Vivo Rel-18 Revision of S2-2208933r03. Approved Approved
9.24 S2-2208934 P-CR Approval 23.700-28: Conclusion of Key Issue #1 signalling overload aspect. Vivo Rel-18 r14 agreed. Revised to S2-2209665. Stephen (Qualcomm) provides comments
Jean-Yves (Thales) As per discussed way forward, proposes this document to continue further discussions on R4 (signalling overload), including some parts of S2-2209184 (second part)
Amy (vivo) provides merged version for discussion on signalling overload
Amy (vivo) answers Stephen (Qualcomm) and copy paste Stephen's comments to avoid branching
Steve (Huawei) comments, provides r02
Lalith(Samsung) provides r03
Stephen (Qualcomm) provides an r04
Amy (vivo) comments on r02, and provides r05
Lalith(Samsung) provides r06
Amy (vivo) replies to Lalith
Lalith(Samsung) replise
Stefan (Ericsson) comments and provides r07
Steve (Huawei) comments, provides r08
Lalith(Samsung) provides r09
Amy (vivo) asks who provides r09, replies to Steve and Lalith, and provides r10.
Lalith(Samsung) provides r11.
Steve (Huawei) comments on setting the timer.
Lalith(Samsung) provides r12
Stefan (Ericsson) replies to Lalith and provides r13
Lalith(Samsung) is OK with r13
Amy (vivo) is OK with r13
Steve (Huawei) comments on calculation
Amy (vivo) provide r14 to capture the calculation in case people like this info
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r14
Steve (Huawei) is ok with r14
Jean-Yves (Thales) is ok with r14
==== Final Deadline ====
Revised
9.24 S2-2209665 P-CR Approval 23.700-28: Conclusion of Key Issue #1 signalling overload aspect. Vivo, Samsung Rel-18 Revision of S2-2208934r14. Approved Approved
9.24 S2-2209026 P-CR Approval 23.700-28: Evaluation and Conclusion Update on Coverage Information Provisioning. Google Inc. Rel-18 r02 agreed. Revised to S2-2209683. Jean-Yves (Thales) proposes to note the document as merged with 8784, like all conclusion based documents for R1,R2,R5,R6 and refers to 8784 for details
SangMin (Google) replied to Jean-Yves, and provided r01.
Jean-Yves (Thales) replied to SangMin
Stephen (Qualcomm) provides an r02
==== Revisions Deadline ====
Stephen (Qualcomm) can agree the r02 but not other versions
Jean-Yves (Thales) notices that r02 (and other revs) proposes different evaluation texts than S2-2208668 (r04 latest) and proposes this S2-2209026 as reference for §7.4.2
Steve (Huawei) is ok with r02
Jean-Yves (Thales) is ok with r02
SangMin (Google) is okay with r02
DongYeon (Samsung) is conditionally okay with r02 when adding 'Solution #22 proposes authentication procedure performed by external server to ensure that only the allwed UE receives the coverage data.' next to 'These solutions with communicating external server may have potential issues in terms of privacy and security.'
==== Final Deadline ====
Revised
9.24 S2-2209683 P-CR Approval 23.700-28: Evaluation and Conclusion Update on Coverage Information Provisioning. Google Inc. Rel-18 Revision of S2-2209026r02. Approved Approved
9.24 S2-2209184 P-CR Approval 23.700-28: KI #1, conclusions. Samsung Rel-18 CC#4: Noted Lalith(Samsung) provides r01
Stephen (Qualcomm) provides comments
Lalith(Samsung) comments
Yuxin(Xiaomi) comments and provides r02 merging 8841, 8875 and 8677 following rapporteur's proposal
Lufeng(Spreadtrum) comments and share the view that more information are valuable when deciding RAT/PLMN selection.
Hannu (Nokia) clarifies his comment and r03 that PLMN selection stage 1 is owned by SA1 and stage 2 is owned by CT1, so SA2 cannot change those without the requirements from SA1 and architecture work by CT1.
Hannu (Nokia) agrees that the UE can change RAT or PLMN due to lack of coverage but proposes to re-use the existing procedures in r03.
Ellen (Google) provides r04 on top of r03 provided by Hannu (Nokia)
Steve (Huawei) provides r05
Stephen (Qualcomm) provides comments and cannot agree with any of the versions
Lalith(Samsung) replies to Stephen (Qualcomm)
Yuxin(Xiaomi) comments and provides r06
==== Revisions Deadline ====
Stephen (Qualcomm) cannot agree the r06 or other versions
Hannu (Nokia) believes the CR can be noted.
Jean-Yves (Thales) comments
Stephen (Qualcomm) provides more comments
==== Final Deadline ====
Noted
9.24 S2-2209185 P-CR Approval 23.700-28: KI #1, Evaluations. Samsung Rel-18 Merged into S2-2209663 Steve (Huawei) comments on how to merge - see first email on 8668
Lalith(Samsung) is OK to mark merged into 8847.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.24 S2-2209197 LS OUT Approval [DRAFT] LS on Satellite coverage data transfer to a UE using UP versus CP Qualcomm Incorporated Rel-18 r02 agreed. Revised to S2-2209684. Lalith (Samsung) comments.
Stefan (Ericsson) provides comments
Hannu (Nokia) provides r01.
Stephen (Qualcomm) provides comments
DongYeon (Samsung) comments.
Jean-Yves (Thales) comments
==== Revisions Deadline ====
Stephen (Qualcomm) prefers r01 but can accept r02
Jean-Yves (Thales) is ok for r02
DongYeon (Samsung) supports r02, and agree to maintain the EN discussed in 8784.
==== Final Deadline ====
Revised
9.24 S2-2209684 LS OUT Approval LS on Satellite coverage data transfer to a UE using UP versus CP SA WG2 Rel-18 Revision of S2-2209197r02. Approved Approved
9.25.1 - - - Study on UPF enhancement for Exposure And SBA (FS_UPEAS) - - Docs:=23 -
9.25.1 - - - KI#1 - solution updates and conclusion updates - - Docs:=6 -
9.25.1 S2-2208508 P-CR Approval 23.700-62: KI #1, Sol #1: Update to add input of UPF registration in NRF. China Mobile Rel-18 Noted Laurent (Nokia): provides r01
Fenqin (Huawei): provides comments
Yan (China Mobile) comments.
Fenqin (Huawei): provides further comments.
==== Revisions Deadline ====
Fenqin (Huawei) suggest to note this paper.
==== Final Deadline ====
Noted
9.25.1 S2-2208219 P-CR Approval 23.700-62: Update to conclusions on KI1. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209928 Yan (China Mobile) proposes to use 8905 as the baseline paper for KI#1 evaluation&conclusion and merge this 8219 into it.
Laurent (Nokia): OK to merge as requested by the rapporteur
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208505 P-CR Approval 23.700-62: Update to evaluations and conclusions on KI#1. China Mobile Rel-18 Merged into S2-2209928 Yan (China Mobile) proposes to use 8905 as the baseline paper for KI#1 evaluation&conclusion and merge this 8505 into it.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208905 P-CR Approval 23.700-62: KI#1, Further evaluation and conclusion of KI#1. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209928, merging S2-2208219, S2-2208505 and S2-2209161 Yan (China Mobile) suggests to use this 8905 as the baseline paper to discuss evaluation and conclusion for KI#1.
Yan (China Mobile) provides r01 by merging 8505 into it.
Magnus H (Ericsson) provides r02
Laurent (Nokia): provides r03
==== Revisions Deadline ====
Yan (China Mobile) suggests to go with r03.
Laurent (Nokia): objects to R02 whose text, sorry, looks unclaer to mle
Fenqin (Huawei) is fine to go with r03.
==== Final Deadline ====
Revised
9.25.1 S2-2209928 P-CR Approval 23.700-62: KI#1, Further evaluation and conclusion of KI#1. Huawei, HiSilicon, Nokia Rel-18 Revision of S2-2208905r03, merging S2-2208219, S2-2208505 and S2-2209161. Approved Approved
9.25.1 S2-2209161 P-CR Approval 23.700-62: KI #1: Conclusion Update. Samsung Rel-18 Merged into S2-2209928 Laurent (Nokia): has concerns with this tDoc which is not aligned with what we agreed at last meeting
Yan (China Mobile) proposes to use 8905 as the baseline paper for KI#1 evaluation&conclusion and merge this 9161 into it.
Kisuk (Samsung) merges it into 8905.
Kisuk (Samsung): comments.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 - - - KI#2 - solution updates and conclusion updates - - Docs:=17 -
9.25.1 S2-2208222 P-CR Approval 23.700-62: Update to the solution 20 (UE IP address mapping information exposure by UPF) . Nokia, Nokia Shanghai Bell Rel-18 CC#4: r08 received goos support in SoH. R08 + changes agreed. Revised to S2-2209954. Yan (China Mobile) suggests to use this 8222 as the baseline paper to discuss solution 20 and then determine the conclusions of exposure of NAT information in 8221 based on this paper.
Yan (China Mobile) has concerns on requesting public IP address via the BSF.
Fenqin (Huawei) provides comment
Magnus H (Ericsson) provides comment
Laurent (Nokia): answers
Fenqin (Huawei) provides feedback
Saso (Intel) comments on the proposed IPFix alternative
Jinsook (DISH) Questionable about the IPFix proposal
Yan (China Mobile) comments.
Magnus H (Ericsson) comments.
Saso (Intel) replies to Magnus
Jinsook (DISH) Asking for a clarification to Magnus
Rohit(AT&T) comments.
Jinsook (DISH) comments.
Jinsook (DISH) comments on the BSF interaction.
Jinsook (DISH) sorry, clarifying my previous comment.
Kisuk (Samsung) comments.
Yan (China Mobile) provides r01.
Laurent (Nokia): provides r02
Magnus H (Ericsson) dislikes any solution where BSF is in charge of finding the NATed address
Magnus H (Ericsson) comments and point to DP 8273
Magnus H (Ericsson) provides r03.
Jinsook (DISH) provides r04.
Fenqin (Huawei) provides r05.
Laurent (Nokia): provides r06,objects to R03 and R05
==== Revisions Deadline ====
Jinsook (DISH): comments and objects to R03 and R05
Kisuk (Samsung): is ok with R04 but objects to R03 and R05
Rohit (AT&T) provides comments
Rohit(AT&T) is ok with r04 only if it is explicitly mentioned in the conclusion that it is an optional feature.
Yan (China Mobile) is ok with r04 and r06 and objects r03 and r05.
Magnus H (Ericsson) can only accept r03, r05 and r06 and objects to all other revisions.
Yan (China Mobile) objects r06 and can only accept r04.
Fenqin (Huawei) prefer r05, r03 and live with r06. Object other version.
Jinsook (DISH) can we go with r04?
Magnus H (Ericsson) comments and sustains the objection, and clarifies that we are not suggesting to remove solution 20. In r06 it should be clear that only second change should be left in the pCR, rest removed.
Laurent (Nokia): I object to R03 and R05 ; I am asking a Show of hand on this topic whether to accept R04
==== Final Deadline ====
Yan (China Mobile) supports to bring it to CC#3 whether to accept r04.
Revised
9.25.1 S2-2209954 P-CR Approval 23.700-62: Update to the solution 20 (UE IP address mapping information exposure by UPF) . Nokia, Nokia Shanghai Bell, DISH Network Rel-18 Revision of S2-2208222r08 + changes. Approved Approved
9.25.1 S2-2208635 P-CR Approval 23.700-62: KI#2, Sol #9: Update to clarify how to NWDAF obtain DNAI according to application server IP address/FQDN. Vivo, ETRI, KDDI Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.25.1 S2-2208220 P-CR Approval 23.700-62: Update to conclusions on KI2: usage of SBA versus usage PFCP for SMF 3rd party subscription onto UPF. Nokia, Nokia Shanghai Bell, Deutsche Telekom, DISH Network Rel-18 Merged into S2-2209929 Fenqin (Huawei) suggest to merge this paper to 8271
==== Revisions Deadline ====
==== Final Deadline ====
Laurent (Nokia): agree to merge in 8271, sorry I forgot to mention
Merged
9.25.1 S2-2208221 P-CR Approval 23.700-62: Update to conclusions on KI2 except for usage of SBA versus usage PFCP for SMF 3rd party subscription onto UPF. Nokia, Nokia Shanghai Bell Rel-18 CC#3: r14 + changes agreed. Revised to S2-2209942. Laurent (Nokia): provides r01
Huazhang (vivo) reply to Laurent (Nokia) on revision 1
Fenqin (Huawei): provides comments
Huazhang (vivo) provides r02
Zhiwei (China Telecom) replies to Laurent (Nokia) and provides r03
Fenqin (Huawei): provides r04
Hyunsook (LGE) provides a comment on r04.
Yan (China Mobile) provides r05.
Josep (DT) includes some editorials + co-sign. Provides r06.
Magnus H (Ericsson) provides r07
Hyunsook (LGE) provides r08
Yan (China Mobile) provides r09 on top of r08.
Fenqin (Huawei) provides r10
Hyunsook (LGE) provides r11
Laurent (Nokia): provides r12
Fenqin (Huawei) ask a question for clarification from Hyunsook
Huazhang (vivo) ask question to Laurent, that I find the specification support to discovery of SMF by UE location, it might be the same as the AoI? Because the AoI is just the UE location or area of interest of UE location?
Yan (China Mobile) replies to Laurent (Nokia).
Magnus H (Ericsson) provides r13
Fenqin (Huawei) provides r14
Hyunsook (LGE) responses to Fenqin.
Fenqin (Huawei) replies to Hyunsook(LGE)
Yoohwa (ETRI) provides r15.
Fenqin (Huawei) is not ok with r15
==== Revisions Deadline ====
Yoohwa (ETRI) is fine with r15 not being accepted.
Huazhang (vivo) prefers we go with r14. This is the only choice to move forward.
Thanks for your hard work.
Magnus H (Ericsson) suggests to go with r14
Aihua(CMCC) provides r16 based on r14, with leftover copied from 8885, and request to discuss in CC#2 or #CC3.
Fenqin (Huawei) suggest to go with r14.
Laurent (Nokia): objects to any version apart R12, R01, R00
I could live with R03, R04, R05,R06,R13 , R14, R15 provided that we add an EN (see below)
Huazhang (vivo) ask a question about this ENs, because in eNA, that request for a certain application's analytic is defined in 6.4.4 of TS 23.288, so DNN and S-NSSAI can be optional, not madatory.
Fenqin (Huawei) ask a question for clarification.
==== Final Deadline ====
Magnus H (Ericsson) disagrees with the proposed EN by Laurent, for the simple reason that the study is not dealing with what consumers to NWDAF use.
Revised
9.25.1 S2-2209942 P-CR Approval 23.700-62: Update to conclusions on KI2 except for usage of SBA versus usage PFCP for SMF 3rd party subscription onto UPF. Nokia, Nokia Shanghai Bell, LG Electronics, China Mobile, Deutsche Telekom, Ericsson Rel-18 Revision of S2-2208221r14 + changes. Approved Approved
9.25.1 S2-2208271 P-CR Approval 23.700-62: KI #2, conclusion update for removal of ENs. Ericsson Rel-18 r01 agreed. Revised to S2-2209929, merging S2-2208220. Laurent (Nokia): has concerns with this Tdoc for the reasons expressed in 8220
Yan (China Mobile) has concerns on requesting public IP address via the BSF.
Yan (China Mobile) recalls the last comments by mistake.
Yan (China Mobile) proposes to make an agreement on whether SBI and/or PFCP is used for interaction with UPF for SMF 3rd party subscription onto UPF.
Magnus H (Ericsson) provides comment
Fenqin (Huawei) provides comments
Laurent (Nokia): answers
Yan (China Mobile) comments.
Laurent (Nokia): provides r01
Magnus H (Ericsson) comments.
Fenqin (Huawei) provides r02
==== Revisions Deadline ====
Yan (China Mobile) suggests to go with r01.
Magnus H (Ericsson) supports Yan to go with r01
Fenqin (Huawei) suggest to bring this to CC#2
Laurent (Nokia): objects to R00
Laurent (Nokia): objects to R00 and R02 (replaces me previous mail)
==== Final Deadline ====
Fenqin (Huawei) only accept r02 and suggest to bring this to CC#3
Revised
9.25.1 S2-2209929 P-CR Approval 23.700-62: KI #2, conclusion update for removal of ENs. Ericsson Rel-18 Revision of S2-2208271r01, merging S2-2208220. Approved Approved
9.25.1 S2-2208272 P-CR Approval 23.700-62: KI#2: Conclusion update and solution 2 correction and evaluation. Ericsson Rel-18 r03 agreed. Revised to S2-2209930. Yoohwa (ETRI) provides r01.
Magnus H (Ericsson) provides r02.
Yoohwa (ETRI) provides r03.
Fenqin (Huawei) ask a question for clarification.
Yoohwa (ETRI) responds to Fenqin (Huawei).
==== Revisions Deadline ====
Yoohwa (ETRI) accepts r01 and r03 but objects r00 and r02.
==== Final Deadline ====
Revised
9.25.1 S2-2209930 P-CR Approval 23.700-62: KI#2: Conclusion update and solution 2 correction and evaluation. Ericsson Rel-18 Revision of S2-2208272r03. Approved Approved
9.25.1 S2-2208273 P-CR Approval 23.700-62: KI #2, Discussion, evaluation, and conclusion regarding exposure of NAT information. Ericsson, Huawei Rel-18 Merged into (Covered by) S2-2208221 Yan (China Mobile) suggests to discuss solution 20 under the 8222 thread firstly before merging the conclusion in this 8273 into 8221.
Saso (Intel) seeks clarification on IPFix.
Jinsook (DISH) Comment & Propose to note this paper
Magnus H (Ericsson) comments.
Laurent (Nokia): objects to any version of this Tdoc; Let's discuss in 8222 (one single thread as proposed by the rapporteur)
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208507 P-CR Approval 23.700-62: Update to evaluations and conclusions on KI#2. China Mobile Rel-18 Merged into (Covered by) S2-2208221 Laurent (Nokia): Comments/concerns with some part
Yan (China Mobile) replies to Laurent (Nokia) and merges this 8507 into 8221.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208519 P-CR Approval 23.700-62: Update to conclusions on KI #2 to resolve ENs. China Telecom Rel-18 Merged into (Covered by) S2-2208221 Zhiwei (China Telecom) has merged this paper into 8221.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208523 P-CR Approval 23.700-62: KI#2: Conclusion update on UPF data reporting. LG Electronics Rel-18 Merged into (Covered by) S2-2208221 Fenqin (Huawei) suggest to merge this paper to 8221
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208636 P-CR Approval 23.700-62: KI#2 conclusions update. Vivo, ETRI, KDDI Rel-18 Merged into (Covered by) S2-2208221 Fenqin (Huawei) suggest to merge this paper to 8221
Huazhang (vivo) agree to merge, thanks Yan and Fenqin
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.1 S2-2208885 P-CR Approval 23.700-62: KI#2 Update to Conclusion. China Mobile Rel-18 Merged into (Covered by) S2-2208221 Fenqin (Huawei) suggest to merge this paper to 8221
==== Revisions Deadline ====
Aihua(CMCC) suggests not to merge and keep it as it was.
Fenqin (Huawei) suggest to mark this paper as merge to 8221.
==== Final Deadline ====
Merged
9.25.1 S2-2208906 P-CR Approval 23.700-62: KI#2, Further update Evaluation and conclusion of KI#2. Huawei, HiSilicon Rel-18 Noted Laurent (Nokia): has concerns with this Tdoc for the reasons expressed in 8220
==== Revisions Deadline ====
Laurent (Nokia): objects to any version of this tdoc (technical and to be merged in
==== Final Deadline ====
Noted
9.25.2 - - - UPF enhancement for Exposure And SBA (UPEAS) - - Docs:=17 -
9.25.2 S2-2208527 CR Approval 23.501 CR3720 (Rel-18, 'B'): UPF event exposure service for TSC management ETRI Rel-18 Postponed Yan (China Mobile) suggests to only discuss TSC management related description in this 8527 and merge other general descriptions to the baseline papers.
Kefeng Zhang (Qualcomm) proposes to remove 'Indication of event notification'.
Yoohwa (ETRI) responds to Kefeng Zhang (Qualcomm)
Laurent (Nokia): suggests to postpone this paper. we first need to understand the overall service/capability before dealing with extra work for TSC aspects
==== Revisions Deadline ====
Yoohwa (ETRI) is fine with postponing this paper.
Laurent (Nokia): Thanks Yoohwa
==== Final Deadline ====
Postponed
9.25.2 S2-2208528 CR Approval 23.502 CR3572 (Rel-18, 'B'): UPF event exposure service ETRI Rel-18 Merged into S2-2209932 Yan (China Mobile) proposes to use 8638 as the baseline paper for UPF service update in 23.502 and merge this 8528 into it.
==== Revisions Deadline ====
Yoohwa (ETRI) is okay with merging 8528.
==== Final Deadline ====
Merged
9.25.2 S2-2208616 CR Approval 23.501 CR3723 (Rel-18, 'B'): Update for UPF registration and event exposure related context concluded in FS_UPEAS China Mobile Rel-18 r06 agreed. Revised to S2-2209931, merging S2-2208637 and S2-2209165 Laurent (Nokia): provides r01
Yan (China Mobile) suggests to use this 8616 as the baseline paper to discuss UPF service update in 23.501.
Yan (China Mobile) provides r02.
Magnus H (Ericsson) provides r03
Laurent (Nokia): provides r04
Fenqin (Huawei) provides r05
Yoohwa (ETRI) provides r06 and cosign it.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.25.2 S2-2209931 CR Approval 23.501 CR3723R1 (Rel-18, 'B'): Update for UPF registration and event exposure related context concluded in FS_UPEAS China Mobile, Nokia, Nokia shanghai Bell, ETRI Rel-18 Revision of S2-2208616r06, merging S2-2208637 and S2-2209165. Approved Agreed
9.25.2 S2-2208637 CR Approval 23.501 CR3724 (Rel-18, 'B'): UPF services update in 23.501 according to the conclusion in UPEAS Vivo Rel-18 Merged into S2-2209931 Yan (China Mobile) proposes to use 8616 as the baseline paper for UPF service update in 23.501 and merge this 8637 into it.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Merged
9.25.2 S2-2208638 CR Approval 23.502 CR3576 (Rel-18, 'B'): UPF service update in 23.502 according to the conclusion in UPEAS Vivo Rel-18 r05 agreed. Revised to S2-2209932, merging S2-2208528, S2-2208645 and S2-2209164 Yan (China Mobile) suggests to use this 8638 as the baseline paper to discuss UPF service update in 23.502.
Huazhang (vivo) provides r01 to merge 8528, 8645 and 9164
Yan (China Mobile) suggests to update this CR further based on the conclusions in 8221.
Fenqin (Huawei) provides r02
Yan (China Mobile) comments.
Yoohwa (ETRI) supports the merged version from Vivo.
Huazhang (vivo) reply to Yoohwa(ETRI)
Magnus H (Ericsson) provides r03
Laurent (Nokia): provides r04
Yoohwa (ETRI) provides r05.
==== Revisions Deadline ====
Huazhang (vivo) prefer to go with r05, and can live with r01, r02, r03, r04
Thanks for your support.
Yoohwa (ETRI) objects r04, but accepts any version.
Laurent (Nokia): objects to any version except R04 and R05
==== Final Deadline ====
Revised
9.25.2 S2-2209932 CR Approval 23.502 CR3576R1 (Rel-18, 'B'): UPF service update in 23.502 according to the conclusion in UPEAS Vivo, ETRI, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208638r05, merging S2-2208528, S2-2208645 and S2-2209164. Approved Agreed
9.25.2 S2-2208639 CR Approval 23.288 CR0548 (Rel-18, 'B'): NWDAF collects data from UPF via service based procedure. Vivo Rel-18 Merged into S2-2209933 Yan (China Mobile) proposes to use 8825 as the baseline paper for alignment for UPF service to NWDAF in 23.288 and merge this 8639 into it.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Merged
9.25.2 S2-2208645 CR Approval 23.502 CR3577 (Rel-18, 'B'): UPF registration and event exposure service update based on conclusions in FS_UPEAS China Mobile Rel-18 Merged into S2-2209932 Yan (China Mobile) proposes to use 8638 as the baseline paper for UPF service update in 23.502 and merge this 8645 into it.
==== Revisions Deadline ====
Laurent (Nokia): objects to any version for the sake of merging
==== Final Deadline ====
Merged
9.25.2 S2-2208825 CR Approval 23.288 CR0551 (Rel-18, 'B'): Alignment for UPF event exposure service to NWDAF via the SMF in TS 23.288 China Mobile Rel-18 r02 agreed. Revised to S2-2209933, merging S2-2208639 Yan (China Mobile) suggests to use this 8825 as the baseline paper to discuss alignment for UPF service to NWDAF in 23.288.
Laurent (Nokia): provides r01
Laurent (Nokia): provides r02
==== Revisions Deadline ====
Laurent (Nokia): objects to R00
==== Final Deadline ====
Revised
9.25.2 S2-2209933 CR Approval 23.288 CR0551R1 (Rel-18, 'B'): Alignment for UPF event exposure service to NWDAF via the SMF in TS 23.288 China Mobile, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208825r02, merging S2-2208639. Approved Agreed
9.25.2 S2-2208836 CR Approval 23.502 CR3583 (Rel-18, 'B'): UPF event exposure service to NWDAF via the SMF in TS 23.502 China Mobile Rel-18 r04 agreed. Revised to S2-2209934. Fenqin (Huawei) provides comments
Aihua(CMCC) provides r01.
Magnus H (Ericsson) provides r02
Huazhang (vivo) ask a question
Aihua(CMCC) provides r03.
Laurent (Nokia): provides r04
==== Revisions Deadline ====
Laurent (Nokia): objects to R00, R01, R02, R03
in R04 there is a typo to correct in § § 4.15.X.3: change '6' to '5'
==== Final Deadline ====
Laurent (Nokia): objects to R00, R01, R02, R03
in R04 there is a typo to correct in § § 4.15.X.3: change '6' to '5'
Revised
9.25.2 S2-2209934 CR Approval 23.502 CR3583R1 (Rel-18, 'B'): UPF event exposure service to NWDAF via the SMF in TS 23.502 China Mobile Rel-18 Revision of S2-2208836r04. Approved Agreed
9.25.2 S2-2208907 CR Approval 23.501 CR3737 (Rel-18, 'B'): Introduction of UPEAS Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209935. Laurent (Nokia): provides r01
Yan (China Mobile) suggests to use this 8907 as the baseline paper to discuss new functions provided by UPF and UPF selection in 23.501.
Fenqin (Huawei): provides r02
Magnus H (Ericsson) ask for some coherency in our specifications
Fenqin (Huawei) provides a response to Magnus
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.25.2 S2-2209935 CR Approval 23.501 CR3737R1 (Rel-18, 'B'): Introduction of UPEAS Huawei, HiSilicon, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208907r02. Approved Agreed
9.25.2 S2-2209164 CR Approval 23.502 CR3599 (Rel-18, 'B'): Update UPF Event Exposure service Samsung Rel-18 Merged into S2-2209932 Yan (China Mobile) proposes to use 8638 as the baseline paper for UPF service update in 23.502 and merge this 9164 into it.
Kisuk (Samsung) merges this paper into 8638.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.25.2 S2-2209165 CR Approval 23.501 CR3750 (Rel-18, 'B'): Update UPF Event Exposure service Samsung Rel-18 Merged into S2-2209931 Yan (China Mobile) proposes to use 8616 as the baseline paper for UPF service update in 23.501 and merge this 9165 into it.
Kisuk (Samsung) merges this paper into 8616.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 - - - Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) - - Docs:=66 -
9.26 - - - KI#1 (UE-UE Relay) - - Docs:=20 -
9.26 S2-2208383 P-CR Approval 23.700-33: KI#1: resolve EN in conclusions. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209332 Yali (OPPO) proposes to merge this paper into S2-2208534
Wen (vivo) seeks the same clarification as asked by Zhang (Ericsson)
Zhang (Ericsson) ask for clarification
Hannu (Nokia) agrees to merge to S2-2208534 and replies to Zhang
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208488 P-CR Approval 23.700-33: KI#1: Conclusions on per-hop link establishment of UE-to-UE Relay. CATT Rel-18 r08 agreed. Revised to S2-2209330. Wen (vivo) comments
Deng Qiang (CATT) replies to Wen (vivo) and provides r01.
Steve (Huawei) comments
Deng Qiang (CATT) provides r02.
Yali (OPPO) comments and provides r03.
Zhang (Ericsson) support OPPO view
Deng Qiang (CATT) comments on r03.
Steve (Huawei) comments and provides r04.
Hong (Qualcomm) comments and provides r05.
Yali (OPPO) replies to Hong (Qualcomm), comments on r05, provides r06.
Wen (vivo) comments.
Yali (OPPO) agree with Wen(vivo).
Deng Qiang (CATT) provides r07.
Steve (Huawei) provides r08
==== Revisions Deadline ====
Deng Qiang (CATT) is fine with r08.
Hong (Qualcomm) accepts r08.
==== Final Deadline ====
Revised
9.26 S2-2209330 P-CR Approval 23.700-33: KI#1: Conclusions on per-hop link establishment of UE-to-UE Relay. CATT Rel-18 Revision of S2-2208488r08. Approved Approved
9.26 S2-2208489 P-CR Approval 23.700-33: KI#1: Conclusion on Identifiers for UE-to-UE Relay discovery. CATT Rel-18 r08 agreed. Revised to S2-2209331, merging S2-2209180 Wen (vivo) comments
Deng Qiang (CATT) replies to Wen (vivo).
Jianning (Xiaomi) provide r01 by merging 9180
Jianning (Xiaomi) provides comment
Steve (Huawei) comments about the sharing of User Info ID, r01 is not good.
Hong (Qualcomm) comments.
Deng Qiang (CATT) clarifies.
Deng Qiang (CATT) replies to Hong (Qualcomm).
Deng Qiang (CATT) provides r03, and please ignore r02.
Yali (OPPO) provides r04.
Jianning (Xiaomi) replies to Steve (Huawei)
Jianning (Xiaomi) replies to Hong (Qualcomm)
Jianning (Xiaomi) replies to Qiang (CATT)
Jianning (Xiaomi) provide r05 on top of r04
Deng Qiang (CATT) responds to Jianning (Xiaomi).
Hong (Qualcomm) is fine with r03, and objects r04.
Deng Qiang (CATT) replies.
Yali (OPPO) comments and provides r06.
Hong (Qualcomm) replies.
Deng Qiang (CATT) replies and provides r07.
Wen (vivo) comments.
Jianning (Xiaomi) replies to Qiang(CATT), Hong(Qualcomm) and Steve (Huawei)
Wen (vivo) replies to Qiang.
Yali (OPPO) shares the view from Wen (vivo).
Jianning (Xiaomi) replies to Wen (vivo) and Yali (OPPO)
Steve (Huawei) provides r08
Wen (vivo) replies to Jianning.
Jianning (Xiaomi) comments
==== Revisions Deadline ====
Deng Qiang (CATT) is fine with r08.
==== Final Deadline ====
Revised
9.26 S2-2209331 P-CR Approval 23.700-33: KI#1: Conclusion on Identifiers for UE-to-UE Relay discovery. CATT Rel-18 Revision of S2-2208489r08, merging S2-2209180. Approved Approved
9.26 S2-2208534 P-CR Approval 23.700-33: KI#1: Conclusion update. OPPO Rel-18 r11 agreed. Revised to S2-2209332, merging S2-2208383 and S2-2208977 Deng Qiang (CATT) proposed to discuss the resolution of ENs about integrated discovery and relay selection by target UE in this email thread.
Yali (OPPO) provides r01 to merge S2-2208383/S2-2208911/S2-2208977.
Steve (Huawei) comments
Hong (Qualcomm) provides r02.
Jungje (Interdigital) provides r03.
Deng Qiang (CATT) comments on r03.
Zhang (Ericsson) object r03
Yali(OPPO) is fine with r02 and object r03.
Jungje(Interdigital) responded Den (CATT)
Steve (Huawei) comments, provides r04.
Jungje(Interdigital) responded to Zhang(Ericsson).
Jungje(Interdigital) comments on r04 and provides r05.
Hong (Qualcomm) comments.
Jungje(Interdigital) responds to Hong(Qualcomm)
Hannu (Nokia) provides r06
Yali(OPPO) provides r07
Jungje(Interdigital) comments Yali(OPPO)
Hannu (Nokia) provides r08 to correct the condition for the UE to not respond.
Jungje(Interdigital) provides r09.
Yali(OPPO) provides r10 based on r09.
Steve (Huawei) comments on parts of, provides r11.
Yali(OPPO) is fine with r11.
==== Revisions Deadline ====
==== Final Deadline ====
Hannu (Nokia) supports r11.
Revised
9.26 S2-2209332 P-CR Approval 23.700-33: KI#1: Conclusion update. OPPO Rel-18 Revision of S2-2208534r11, merging S2-2208383 and S2-2208977. Approved Approved
9.26 S2-2208909 P-CR Approval 23.700-33: Terms update for U2U Relay. Huawei, HiSilicon Rel-18 r02 agreed. Revised to S2-2209333. LaeYoung (LGE) provides comment.
Hao (ZTE) comments.
Zhang (Ericsson) provides comments
Jianning (Xiaomi) provide comment
Steve (Huawei) comments
Zhang (Ericsson) provide comment
LaeYoung (LGE) comments.
LaeYoung (LGE) replies to Steve (Huawei).
Jungje(Interdigital) comments
Steve (Huawei) changes peer to end and provides r01.
Hong (Qualcomm) comments.
LaeYoung (LGE) provides r02.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.26 S2-2209333 P-CR Approval 23.700-33: Terms update for U2U Relay. Huawei, HiSilicon Rel-18 Revision of S2-2208909r02. Approved Approved
9.26 S2-2208910 P-CR Approval 23.700-33: KI#1 Sol#7 Update: Add new option for L2 U2U Relay. Huawei, HiSilicon Rel-18 r03 agreed. Revised to S2-2209334, merging S2-2209031 Zhang (Ericsson) ask for clarification
Jungje(Interdigital) comments and provides r01.
Steve (Huawei) provides r02
Jungje(Interdigital) comments and provides r03
==== Revisions Deadline ====
Jungje (Interdigital) accepts only r03.
Steve (Huawei) can live with r03.
==== Final Deadline ====
Revised
9.26 S2-2209334 P-CR Approval 23.700-33: KI#1 Sol#7 Update: Add new option for L2 U2U Relay. Huawei, HiSilicon Rel-18 Revision of S2-2208910r03, merging S2-2209031. Approved Approved
9.26 S2-2208911 P-CR Approval 23.700-33: KI#1: Conclusion update. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209335. Yali (OPPO) proposes to merge this paper into S2-2208534 and S2-2209111
Steve (Huawei) provides r01, removing parts merged elsewhere.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.26 S2-2209335 P-CR Approval 23.700-33: KI#1: Conclusion update. Huawei, HiSilicon Rel-18 Revision of S2-2208911r01. Approved Approved
9.26 S2-2208977 P-CR Approval 23.700-33: KI #1: Conclusion Update . Interdigital Rel-18 Merged into S2-2209332 Zhang (Ericsson) provides comments and ask for clarification
Yali (OPPO) proposes to merge this paper into S2-2208534
Jianning (Xiaomi) provide comment
==== Revisions Deadline ====
Steve (Huawei) Should be merged to 8534
==== Final Deadline ====
Merged
9.26 S2-2209031 P-CR Approval 23.700-33: Updates on Solution #7 . Interdigital Rel-18 Merged into S2-2209334 Steve (Huawei) comments
Jungje(Interdigital) comments
==== Revisions Deadline ====
Yali(OPPO) think this paper has been merged into S2-2208910, as Jungje(Interdigital) mentioned in the previous email.
Steve (Huawei) has been merged with 9310
==== Final Deadline ====
Merged
9.26 S2-2209109 P-CR Approval 23.700-33: Update to EN in conclusions for KI#1: Support of UE-to-UE relay . Qualcomm Incorporated Rel-18 r03 agreed. Revised to S2-2209336. Wen (vivo) comments.
Deng Qiang (CATT) asks for clarifications on the 'additional UE-to-UE relay discovery information'.
Yali (OPPO) comments and proposes to merge this paper into S2-2208489.
Jianning (Xiaomi) provide comment
Hong (Qualcomm) replies to Deng Qiang (CATT).
Steve (Huawei) supports r00.
Hong (Qualcomm) replies to Yali, Jianning, and Wen.
Deng Qiang (CATT) further comments.
Hong (Qualcomm) replies to Deng Qiang.
Deng Qiang (CATT) provides r01.
Yali(OPPO) replies to Hong (Qualcomm).
Hong (Qualcomm) replies to Yali, and DengQiang, and provide r02.
Deng Qiang (CATT) is fine with r02.
Yali(OPPO) replies to Hong (Qualcomm) and provides r03.
==== Revisions Deadline ====
Steve (Huawei) is ok with r03
==== Final Deadline ====
Revised
9.26 S2-2209336 P-CR Approval 23.700-33: Update to EN in conclusions for KI#1: Support of UE-to-UE relay . Qualcomm Incorporated Rel-18 Revision of S2-2209109r03. Approved Approved
9.26 S2-2209111 P-CR Approval 23.700-33: Update to conclusions for KI#1: Support of UE-to-UE relay . Qualcomm Incorporated Rel-18 r03+ changes agreed. Revised to S2-2209337 Deng Qiang (CATT) asks for clarifications on the 'E2E links'.
Wen (vivo) comments for clarification.
Yali (OPPO) comments.
Hong (Qualcomm) provides r01.
Steve (Huawei)
Yali replies to Steve (Huawei)
Steve (Huawei) comments
Deng Qiang (CATT) comments.
Jungje(Interdigital) comments.
Jungje(Interdigital) respond to Steve(Huawei).
Jungje(Interdigital) responded to Steve(Huawei).
Jungje(Interdigital) provides r02
Hong (Qualcomm) provides r03.
Jungje(Interdigital) comments to r03.
Deng Qiang (CATT) replies to Jungje (Interdigital).
Jungje (Interdigital) responds to Deng(CATT)
Deng Qiang (CATT) responds to Jungje (Interdigital).
Hong (Qualcomm) comments.
Steve (Huawei) comments on individually
Jungje(Interdigital) responds to Hong(Qualcomm)
Jungje(Interdigital) provides r04.
Yali(OPPO) objects r04.
Jungje(Interdigital) responds to Yali(OPPO).
Jungje(Interdigital) responds to Hong(Qualcomm).
==== Revisions Deadline ====
Deng Qiang (CATT) supports r03 and objects r04.
Hong (Qualcomm) replies to JungJe, and can only accept r03.
Hong (Qualcomm) replies to JungJe.
Jungje(Interdigital) respons to Hong(Qualcomm)
Steve (Huawei) only supports r03, objects to all other revisions (r00, r01, r02, r04).
Jungje(Interdigital) oppose to r03 but can accept r03 with following NOTE added.
NOTE : If source UE or target UE has multiple application layer IDs (user info), it would be treated as different UEs per application layer ID and separate PC5 link between UE(source UE or target UE) and Relay UE shall be setup.
This will be confirmed by RAN during normative phase.
Deng Qiang (CATT) comments on the proposed NOTE.
Jungje(Interdigital) responds to Deng(CATT)
Hong (Qualcomm) comments: although we believe the NOTE is not needed technically, but can live with it w/ r03.
==== Final Deadline ====
Revised
9.26 S2-2209337 P-CR Approval 23.700-33: Update to conclusions for KI#1: Support of UE-to-UE relay . Qualcomm Incorporated Rel-18 Revision of S2-2209111r03 + changes. Approved Approved
9.26 S2-2209180 P-CR Approval 23.700-33: Update conclusion#1 to remove the EN. Xiaomi Rel-18 Merged into S2-2209331 Deng Qiang (CATT) comments and proposes to discuss discovery parameters in S2-2208489.
Jianning (Xiaomi) replies to Deng Qiang(CATT)
Deng Qiang(CATT) comments.
Wen (vivo) comments
Jianning (Xiaomi) is ok to merge into 8489 to focus on discovery parameters discussion
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 - - - KI#2 (path switching btw two indirect paths) - - Docs:=1 -
9.26 S2-2208912 P-CR Approval 23.700-33: KI#2: Conclusion update on rule priority. Huawei, HiSilicon Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 - - - KI#3 (path switching btw PC5 and Uu) - - Docs:=11 -
9.26 S2-2208604 P-CR Approval 23.700-33: KI#3, Sol#19 Update. ZTE Rel-18 r02 agreed. Revised to S2-2209338. LaeYoung (LGE) asks a Q.
Hao (ZTE) responds.
LaeYoung (LGE) replies to Hao (ZTE).
Hao (ZTE) responds and provides r01.
LaeYoung (LGE) comments on r01.
Hao (ZTE) responds to LaeYoung (LGE) and provides r02.
LaeYoung (LGE) is fine with r02.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.26 S2-2209338 P-CR Approval 23.700-33: KI#3, Sol#19 Update. ZTE Rel-18 Revision of S2-2208604r02. Approved Approved
9.26 S2-2208605 P-CR Approval 23.700-33: KI#3, Sol#22 Clarification on UE Address. ZTE Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 S2-2208661 P-CR Approval 23.700-33: TR 23.700-33: Update on KI #3 conclusions. China Telecom Rel-18 Merged into S2-2209339 Zhang (Ericsson) provides comments
LaeYoung (LGE) provides comments.
Wen (vivo) comments.
Changzheng (China Telecom) replies to Zhang, LaeYoung, Wen.
Jungje (Interdigital) comments.
Changzheng (China Telecom) replies to Jung Je.
LaeYoung (LGE) proposes to NOTE or MERGE this pCR to other KI#3 conclusion update pCR (e.g. 8981, 8914) and to discuss this aspect there.
LaeYoung (LGE) proposes to MERGE this pCR to 8914.
Mehrdad (Mediatek Inc.) also suggests to mark this PCR as either noted or merged into 8914.
==== Revisions Deadline ====
Steve (Huawei) Should be marked as MERGED to 8914
==== Final Deadline ====
Merged
9.26 S2-2208717 P-CR Approval 23.700-33: KI #3, Sol #22: update to remove the EN . China Telecom Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 S2-2208739 P-CR Approval 23.700-33: TR 23.700-33: Update on KI #3 conclusions. China Telecom Rel-18 Merged into S2-2209339 LaeYoung (LGE) proposes to MERGE this pCR to 8914.
Heng (China Telecom) reply.
Mehrdad (Mediatek Inc.) also suggests to mark this PCR as merged into 8914.
==== Revisions Deadline ====
Heng (China Telecom) agree to mark this PCR as merged into 8914.
Steve (Huawei) Should be marked as MERGED to 8914
==== Final Deadline ====
Merged
9.26 S2-2208913 P-CR Approval 23.700-33: KI#3 Sol#17 Update: Support of Multiple Services . Huawei, HiSilicon Rel-18 Approved Hao (ZTE) comments.
Wen (vivo) tries to reply to Hao (ZTE) .
Steve (Huawei) comments
Mehrdad (Mediatek Inc.) comments
Steve (Huawei) comments on cases
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 S2-2208914 P-CR Approval 23.700-33: KI#3: Evaluation and Conclusion Update. Huawei, HiSilicon Rel-18 r10 agreed. Revised to S2-2209339, merging S2-2208661, S2-2208739, S2-2208981 and S2-2209179 Deng Qiang (CATT) proposes to discuss the EN resolution in this email thread.
Jianning (Xiaomi) provide r01 by merging the content from 9179 as suggested by Rapporteur.
Steve (Huawei) comments on the merge
Jungje(Interdigital) provide r02
Steve (Huawei) comments, r02 is not a good merge either.
Jungje(Interdigital) provides r02
Hao (ZTE) comments.
Jianning (Xiaomi) replies to Steve (Huawei)
Jianning (Xiaomi) replies to Hao (ZTE) and provide r03
Heng (China Telecom) provide r04 to merge 8739 to r03.
Jungje(Interdigital) respond Steve(Huawei) and provided r05
Steve (Huawei) provides r06
Mehrdad (Mediatek Inc.) comments on latest revision, r06.
Jungje(Interdigital) comments Steve(Huawei) and provides r07.
Steve (Huawei) comments on doubling the negotiation
Jungje(Interdigital) responds to Steve (Huawei).
Hao (ZTE) asks for clarification.
LaeYoung (LGE) provides r08 on top of r06 from Steve (Huawei).
Heng (China Telecom) clarify to LaeYoung and Mehrdad
Changzheng (China Telecom) provides r09 to merge 8661 to r08.
LaeYoung (LGE) replies to Heng (China Telecom).
LaeYoung (LGE) responds to Jungje (Interdigital) and Changzheng (China Telecom).
Heng (China Telecom) replies to LaeYoung (LGE).
Hannu (Nokia) provides r10.
Jungje(Interdigital) responds to Laeyoung(LGE)
Heng (China Telecom) provides r11 on top of r10 to keep the removed two bullets.
LaeYoung (LGE) replies to Jungje (Interdigital).
LaeYoung (LGE) cannot accept r11 and answers to Heng (China Telecom).
LaeYoung (LGE) answers to Jungje (Interdigital).
Jungje(Intedigital) responds to LaeYoung(LGE) and provides r12.
Jungje(Interdigital) responds Heng(China Telecom)'s proposal
Jungje(Interdigital) provides r14.
==== Revisions Deadline ====
LaeYoung (LGE) accepts only r10, r09, r08 and objects to other versions. So, proposes to go with r10.
Jungje(Interdigital) responds LaeYoung (LGE).
Heng(China Telecom) reply to Jungje and Laeyoung
Heng (China Telecom) reply to LaeYoung (LGE)
Steve (Huawei) r10 looks like the baseline according to the comments. Supports r10.
Heng (China Telecom) propose add the non IP case in r10
==== Final Deadline ====
Revised
9.26 S2-2209339 P-CR Approval 23.700-33: KI#3: Evaluation and Conclusion Update. Huawei, HiSilicon Rel-18 Revision of S2-2208914r10, merging S2-2208661, S2-2208739, S2-2208981 and S2-2209179. Approved Approved
9.26 S2-2208981 P-CR Approval 23.700-33: KI #3: Conclusion Update . Interdigital Rel-18 Merged into S2-2209339 LaeYoung (LGE) proposes to MERGE this pCR to 8914.
Changzheng(China Telecom) replies to LaeYoung(LGE) and provide r01 to merge 8661 to 8981.
LaeYoung (LGE) proposes to MERGE this pCR to 8914 and to discuss KI#3 conclusion updates there.
Hannu (Nokia) supports the proposal from LaeYoung to merge in order to discuss each KI in single document, please. So this tdoc won't be needed as any agreeable contents should go to a revision of the merged document.
==== Revisions Deadline ====
Steve (Huawei) Should be marked as MERGED to 8914
==== Final Deadline ====
Merged
9.26 S2-2209179 P-CR Approval 23.700-33: Update conclusion#3 to remove the EN. Xiaomi Rel-18 Merged into S2-2209339 Hao (ZTE) comments.
Jianning (Xiaomi) provide comment
Hao (ZTE) responds.
Jianning (Xiaomi) replies to Hao (ZTE), and merge this paper into 8914
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 - - - KI#4 (path switching for L2 Relay) - - Docs:=1 -
9.26 S2-2208492 P-CR Approval 23.700-33: KI#4: Remove RAN dependency ENs in KI#4 Conclusions. CATT Rel-18 Approved Hannu (Nokia) comments that this P-CR does not remove the RAN dependency but only pushes it to normative phase.
==== Revisions Deadline ====
Deng Qiang (CATT) replies to Hannu (Nokia).
Steve (Huawei) is ok with r00
==== Final Deadline ====
Approved
9.26 - - - KI#5 (multi-path transmission) - - Docs:=11 -
9.26 S2-2208381 P-CR Approval 23.700-33: KI#5: Re-use of Rel-18 ATSSS study conclusions. Nokia, Nokia Shanghai Bell Rel-18 Merged into S2-2209340 Deng Qiang (CATT) proposes this paper be merged into S2-2208490.
Changhong (Intel) replies to Qiang and OK with using S2-2208490 for the second EN resolution.
Steve (Huawei) comments
Hannu (Nokia) agrees to merge to 8490.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208490 P-CR Approval 23.700-33: KI#5: Remove EN in KI#5 Conclusions. CATT Rel-18 r01 agreed. Revised to S2-2209340, merging S2-2208381 Hannu (Nokia) provides r01 to merge S2-2208381 into this document and co-signs.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.26 S2-2209340 P-CR Approval 23.700-33: KI#5: Remove EN in KI#5 Conclusions. CATT, Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208490r01, merging S2-2208381. Approved Approved
9.26 S2-2208517 P-CR Approval 23.700-33: KI#5, Conclusion update: Resolve EN for multi-path. OPPO Rel-18 Merged into (Covered by) S2-2208893 Changhong (Intel) proposes to discuss the first EN resolution in the thread of S2-2208893.
Hannu (Nokia) agrees to merge this to 8893 but points out that the proposed change needs modification.
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208652 P-CR Approval 23.700-33: TR 23.700-33: KI #5 conclusion: Update on MA-PDU Session Establishment. China Telecom Rel-18 Merged into (Covered by) S2-2208893 Wen (vivo) comments.
Fei (OPPO) comments and does not see any need to this new access type.
Changzheng (China Telecom) replies.
Changhong (Intel) supports the proposal and proposes to merge it into S2-2208893.
==== Revisions Deadline ====
Changzheng (China Telecom) confirms to merge S2-2208652 to S2-2208893 and accept r00, r02.
==== Final Deadline ====
Merged
9.26 S2-2208893 P-CR Approval 23.700-33: KI#5: Conclusion Update. Intel Rel-18 Noted. CC#4: r04 agreed. Revised to S2-2209981. Fei (OPPO) comments.
Wen (vivo) comments.
Changhong (Intel) replies to Wen and Fei's comments.
Wen (vivo) replies to Changhong.
Steve (Huawei) comments
Changhong (Intel) replies to Steve.
Hannu (Nokia) provides r01.
Changhong (Intel) replies to Hannu's comment and provides r02.
Steve (Huawei) provides r03
==== Revisions Deadline ====
Changhong (Intel) objects to r03, r01 and can only accept r00, r02.
Changzheng (China Telecom) supports r02 and objects r03.
Fei (OPPO) can only accept r03.
Wen (vivo) shares the same view with Fei and can only accept r03.
Steve (Huawei) only accepts r03, objects to all other revisions
Changhong (Intel) provides a draft r04 as way forward to resolve the EN in the conclusion for KI#3.
Changhong (Intel) provides a draft r04 as way forward to resolve the EN in the conclusion for KI#5, sorry for typo.
==== Final Deadline ====
Fei (OPPO) is ok with draft r04 which is based on r03 plus one note (note1). Propose it can be discussed at CC#3 or CC#4.
Hannu (Nokia) prefers r02 or r04. Can also live with r03.
Steve (Huawei) proposes a clarified note: NOTE 1: For policy authorization for multi-path transmission via direct Uu path and Layer 3 U2N Relay UE with N3IWF, whether the current Access Type preference in URSP needs to be updated will be investigated in the normative phase.
Changhong (Intel) clarifies that draft r04 reverse the removal of 'with an' in first bullet and add the 'NOTE: For policy authorization for multi-path transmission via direct Uu path and Layer 3 U2N Relay UE with N3IWF, whether the current Access Type preference in URSP needs to be updated will be investigated in the normative phase' on top of r03.
Revised
9.26 S2-2209981 P-CR Approval 23.700-33: KI#5: Conclusion Update. Intel Rel-18 Revision of S2-2208893r04. Approved Approved
9.26 S2-2208915 P-CR Approval 23.700-33: KI#5 Sol#29 Update: Policy and Authorization for Multi-path Transmission. Huawei, HiSilicon Rel-18 Approved Changhong (Intel) comments and don't think a solution can be updated to be same with an existing solution.
Hao (ZTE) comments.
Steve (Huawei) comments, not redundant, avoids backwards compatibility, it's a clarification.
Changhong (Intel) thinks the updated Sol#29 becomes a new solution and asks Rapporteurs to clarify whether new solution is allowed at this meeting.
Fei (OPPO) comments.
Changhong (Intel) proposes to NOTE this paper since new solution is not allowed at this meeting.
Steve (Huawei) it's not new and the clarifications have been seen before, provides r01.
Changhong (Intel) replies to Steve.
Changhong (Intel) prefers to agree r00 based on clarification from Steve.
==== Revisions Deadline ====
Steve (Huawei) is fine with r00
==== Final Deadline ====
Approved
9.26 S2-2208916 P-CR Approval 23.700-33: KI#5: Evaluation update. Huawei, HiSilicon Rel-18 r01 agreed. Revised to S2-2209341. Changhong (Intel) comments.
Steve (Huawei) comments
Changhong (Intel) provides r01.
==== Revisions Deadline ====
Steve (Huawei) is ok with r01.
==== Final Deadline ====
Revised
9.26 S2-2209341 P-CR Approval 23.700-33: KI#5: Evaluation update. Huawei, HiSilicon Rel-18 Revision of S2-2208916r01. Approved Approved
9.26 S2-2208917 P-CR Approval 23.700-33: KI#5 Conclusion Update for Sol#27. Huawei, HiSilicon Rel-18 Noted Fei (OPPO) comments and objects to this conclusion update.
Deng Qiang (CATT) shares the similar view with Fei (OPPO), and proposes to NOTED this paper.
Hannu (Nokia) shares the view of Fei and Deng Qiang
==== Revisions Deadline ====
Judy (Ericsson) shares the view of Fei, Deng Qiang and Hannu
==== Final Deadline ====
Noted
9.26 - - - KI#6: PC5 Parameter Provisioning - - Docs:=4 -
9.26 S2-2208491 P-CR Approval 23.700-33: KI#6: Overall Evaluation and Conclusions. CATT, LG Electronics, Intel Rel-18 r03 agreed. Revised to S2-2209342, merging S2-2208918 and S2-2208919 Steve (Huawei) provides r01
LaeYoung (LGE) comments on r01.
Deng Qiang (CATT) provides r02 to shorten the description and avoid duplication.
Steve (Huawei) comments and provides r03.
==== Revisions Deadline ====
LaeYoung (LGE) is fine with r03.
Deng Qiang (CATT) is fine with r03.
Steve (Huawei) is ok with r03
==== Final Deadline ====
Revised
9.26 S2-2209342 P-CR Approval 23.700-33: KI#6: Overall Evaluation and Conclusions. CATT, LG Electronics, Intel Rel-18 Revision of S2-2208491r03, merging S2-2208918 and S2-2208919. Approved Approved
9.26 S2-2208918 P-CR Approval 23.700-33: KI#6: Evaluation. Huawei, HiSilicon Rel-18 Merged into S2-2209342 Deng Qiang (CATT) proposes this paper be merged into S2-2208491.
==== Revisions Deadline ====
Steve (Huawei) is ok to MERGE with 8491
==== Final Deadline ====
Merged
9.26 S2-2208919 P-CR Approval 23.700-33: KI#6: Conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209342 Deng Qiang (CATT) proposes this paper be merged into S2-2208491.
==== Revisions Deadline ====
Steve (Huawei) is ok to MERGE with 8491
==== Final Deadline ====
Merged
9.26 - - - KI#7 (Emergency service) - - Docs:=18 -
9.26 S2-2208584 LS OUT Approval [DRAFT] LS on the feasibility of NG-RAN providing emergency indication vivo Rel-18 Postponed Judy (Ericsson) comments
==== Revisions Deadline ====
Wen (vivo) : it is ok that this paper can be postponed.
Judy (Ericsson): this paper should be either postponed or noted as the solution is still under discussion as previously commented.
==== Final Deadline ====
Postponed
9.26 S2-2208360 P-CR Approval 23.700-33: KI#7, Sol#42: update to resolve ENs. Ericsson Rel-18 r04 agreed. Revised to S2-2209343, merging S2-2208448, S2-2208585 and S2-2208920 Deng Qiang (CATT) proposes to discuss sol#42 update in this email thread.
Steve (Huawei) comments on merge potential / how to discuss.
Mehrdad (Mediatek Inc.) is happy to use either 8920 or 8360 as the baseline and merge 8448 into the baseline paper.
Judy (Ericsson) comments and provides r01
Mehrdad (Mediatek Inc.) asks a clarification based on evaluation in 8361
Steve (Huawei) provides r02
Judy (Ericsson) provides r03
Steve (Huawei) provides r04
==== Revisions Deadline ====
Judy (Ericsson) is fine with r04
Mehrdad (Mediatek Inc.) requests to mark 8448 marked as merged into 8360r04 and co-signs 8360r04.
Judy (Ericsson) responds to Mehrdad (Mediatek Inc.)
==== Final Deadline ====
Revised
9.26 S2-2209343 P-CR Approval 23.700-33: KI#7, Sol#42: update to resolve ENs. Ericsson, Mediatek Inc., vivo, Huawei, HiSilicon Rel-18 Revision of S2-2208360r04, merging S2-2208448, S2-2208585 and S2-2208920. Approved Approved
9.26 S2-2208361 P-CR Approval 23.700-33: KI#7, Evaluation on Emergency Services for UE to Network Relaying. Ericsson, Nokia, Nokia Shanghai Bell, Apple Rel-18 Revision of (Unhandled) S2-2205810 from S2#152E. r05 agreed. Revised to S2-2209344, merging S2-2208583 and S2-2208921 Deng Qiang (CATT) proposes to discuss KI#7 Evaluation in this email thread.
Wen (vivo) provides r01.
Mehrdad (Mediatek Inc.) comments on r01
Wen (vivo) replies to Mehrdad (Mediatek Inc.)
Judy (Ericsson) provides r02
Hannu (Nokia) provides r03
Mehrdad (Mediatek Inc.) provides r04
Tingyu (Samsung) provides r05.
Judy (Ericsson) provides r06 adding EN to allow to check whether L2 Relay UE should also prioritize its own emergency service
Steve (Huawei) comments on L2 handling EN, does not agree with it.
==== Revisions Deadline ====
Steve (Huawei) can live with r05, objects to r06.
Mehrdad (Mediatek Inc.) is OK with r05 and r04 but we objects to the rest of revision and original version.
==== Final Deadline ====
Revised
9.26 S2-2209344 P-CR Approval 23.700-33: KI#7, Evaluation on Emergency Services for UE to Network Relaying. Ericsson, Nokia, Nokia Shanghai Bell, Apple Rel-18 Revision of S2-2208361r05, merging S2-2208583 and S2-2208921. Approved Approved
9.26 S2-2208362 P-CR Approval 23.700-33: KI#7, Conclusion on Emergency Services for UE to Network Relaying. Ericsson, Nokia, Nokia Shanghai Bell, Apple Rel-18 Revision of (Unhandled) S2-2205811 from S2#152E. r14 agreed. Revised to S2-2209345, merging S2-2208518 and S2-2208922 Deng Qiang (CATT) proposes to discuss KI#7 Conclusions in this email thread.
Steve (Huawei) provides r01
Wen (vivo) provides r02
Fei (OPPO) provides r03 and comments.
Wen (vivo) replies to Fei.
Steve (Huawei) comments, provides r04
Mehrdad (Mediatek Inc.) comments on r04
Hong (Qualcomm) provide r05.
Wen (vivo) replies to Steve (Huawei)
Wen (vivo) replies to Hong and comments on r05.
Hong (Qualcomm) comments.
Wen (vivo) replies.
Judy (Ericsson) provides r06
Wen (vivo) comments.
Wen (vivo) provides r07
Fei (OPPO) provides responses inline
Hannu (Nokia) provides r08.
Judy (Ericsson) provides r09 adding EN whether limited service state applies to L3 remote UE is FFS
Fei (OPPO) provides views on L3 remote UE.
Hannu answers to Judy, Fei and Steve and provides r10.
Fei (OPPO) replies.
Steve (Huawei) comments and provides r11
Wen (vivo) provides r12
Steve (Huawei) comments on by implementation
Hong (Qualcomm) replies to Wen.
Wen (vivo) replies to Hong (Qualcomm).
Fei (OPPO) provides comments to Wen
Judy (Ericsson) provides r13
Tingyu (Samsung) comments.
Steve (Huawei) provides r14
Wen (vivo) repines to Judy about the RRC messaged encrypted
==== Revisions Deadline ====
Fei (OPPO) is fine with r14.
Steve (Huawei) is ok with r14.
Mehrdad (Mediatek Inc.) can live with r14
==== Final Deadline ====
Revised
9.26 S2-2209345 P-CR Approval 23.700-33: KI#7, Conclusion on Emergency Services for UE to Network Relaying. Ericsson, Nokia, Nokia Shanghai Bell, Apple, OPPO Rel-18 Revision of S2-2208362r14, merging S2-2208518 and S2-2208922. Approved Approved
9.26 S2-2208375 P-CR Approval 23.700-33: KI#7 emergency: Update of solution #47. Nokia, Nokia Shanghai Bell Rel-18 Approved Judy (Ericsson) asks question
Hong (Qualcomm) asks questions.
Hannu (Nokia) answers to Hong
==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 S2-2208407 P-CR Approval 23.700-33: KI#7: Updates to Solution #48. Samsung Rel-18 Approved ==== Revisions Deadline ====
==== Final Deadline ====
Approved
9.26 S2-2208448 P-CR Approval 23.700-33: KI#7, Sol#42 Update: Emergency Services for UE to Network Relaying. MediaTek Inc. Rel-18 Merged into S2-2209343 Judy (Ericsson) assumes this paper is merged to 8362
Judy (Ericsson) corrects: this paper is assumed to be merged to 8360
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208518 P-CR Approval 23.700-33: KI#7, Conclusion on emergency service on U2N relay for access type. OPPO Rel-18 Merged into S2-2209345 Judy (Ericsson) assumes this paper is merged into 8362
Fei (OPPO) comfirms it should be marked as merged or noted
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208582 P-CR Approval 23.700-33: KI#7,Sol#45,Update to emergency indication from NG-RAN. Vivo Rel-18 r01 agreed. Revised to S2-2209346. Hannu (Nokia) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Revised
9.26 S2-2209346 P-CR Approval 23.700-33: KI#7,Sol#45,Update to emergency indication from NG-RAN. Vivo Rel-18 Revision of S2-2208582r01. Approved Approved
9.26 S2-2208583 P-CR Approval 23.700-33: KI#7_Sol#45_Evaluation and Conclusion. Vivo Rel-18 Merged into S2-2209344 Judy (Ericsson) assumes this paper merged into 8361 or 8362
==== Revisions Deadline ====
Wen(vivo): this paper is ok to be merged into 8361 or 8362
==== Final Deadline ====
Merged
9.26 S2-2208585 P-CR Approval 23.700-33: KI#7, Sol#42, Update: EN removal about mobility restriction. Vivo Rel-18 Merged into S2-2209343 Judy (Ericsson) assumes this paper is merged to 8362
Judy (Ericsson) corrects: this paper is assumed to be merged to 8360
==== Revisions Deadline ====
Wen (vivo): this paper is ok to be merged to 8360
==== Final Deadline ====
Merged
9.26 S2-2208920 P-CR Approval 23.700-33: KI#7 Sol#42 Update: EN removal and solution clarification. Huawei, HiSilicon Rel-18 Merged into S2-2209343 Judy (Ericsson) comments that the related discussion is in 8360 thread
==== Revisions Deadline ====
Steve (Huawei) is ok to MERGE to 8360.
==== Final Deadline ====
Merged
9.26 S2-2208921 P-CR Approval 23.700-33: KI#7: Evaluation. Huawei, HiSilicon, MediaTek Inc. Rel-18 Merged into S2-2209344 Judy (Ericsson) assumes this paper is merged into 8361
==== Revisions Deadline ====
==== Final Deadline ====
Merged
9.26 S2-2208922 P-CR Approval 23.700-33: KI#7: Conclusion. Huawei, HiSilicon Rel-18 Merged into S2-2209345 Judy (Ericsson) comments the related discussion is in 8362 thread
==== Revisions Deadline ====
Steve (Huawei) is ok to MERGE to 8362
==== Final Deadline ====
Merged
9.27.1 - - - Study on Seamless UE context recovery (FS_SUECR) - - Docs:=0 -
9.27.2 - - - Seamless UE context recovery (SUECR) - - Docs:=4 -
9.27.2 S2-2209160 CR Approval 23.501 CR3749 (Rel-18, 'B'): Support of unavailability period Samsung, Qualcomm, LG Electronics, Apple Rel-18 r05 agreed. Revised to S2-2209666. Hannu (Nokia): shares r01 on behalf of drafting group last week.
Fei (OPPO) comments.
Steve (Huawei) provides r02
Lalith(Samsung) is fine with r02 and replies.
Fei (OPPO) provides r03.
Qian (Ericsson) provides r04.
Lalith (Samsung) provides r05.
==== Revisions Deadline ====
Myungjune (LGE) is ok with r05.
Steve (Huawei) is ok with r05
==== Final Deadline ====
Revised
9.27.2 S2-2209666 CR Approval 23.501 CR3749R1 (Rel-18, 'B'): Support of unavailability period Samsung, Qualcomm, LG Electronics, Apple, Nokia, Nokia Shanghai Bell, KDDI Rel-18 Revision of S2-2209160r05. Approved Agreed
9.27.2 S2-2209163 CR Approval 23.502 CR3598 (Rel-18, 'B'): Support of unavailability period Samsung, Qualcomm, LG Electronics, Apple Rel-18 r02 agreed. Revised to S2-2209667. Hannu (Nokia): shares r01 corresponding to the updates that were proposed in S2-2209160r01.
Hannu (Nokia): corrects the AI from 9.27 to 9.27.2
Fei (OPPO) comments
Steve (Huawei) provides r02
Lalith(Samsung) comments.
Fei (OPPO) provides comments.
Steve (Huawei) clarifies comment on service operations and storing times in context.
Fei (OPPO) responds.
Lalith(Samsung) replies to Steve (Huawei)
Lalith (Samsung) comments.
Fei (OPPO) provides response to Lalith
Qian (Ericsson) asks a question for clarification
Qian (Ericsson) provides further comments
Lalith(Samsung) replies to Qian (Ericsson)
==== Revisions Deadline ====
Myungjune (LGE) ok with r02.
Steve (Huawei) is ok with r02
==== Final Deadline ====
Revised
9.27.2 S2-2209667 CR Approval 23.502 CR3598R1 (Rel-18, 'B'): Support of unavailability period Samsung, Qualcomm, LG Electronics, Apple, Nokia, Nokia Shanghai Bell, KDDI Rel-18 Revision of S2-2209163r02. Approved Agreed
9.28 - - - Stage 2 of MPS_WLAN (MPS_WLAN) - - Docs:=10 -
9.28 S2-2209049 DISCUSSION Information MPS when access to EPC/5GC is WLAN. Peraton Labs Rel-18 Noted Robert (Peraton Labs) suggests for now to continue the discussion for this DP and related CRs on this thread.
Laurent (Nokia): answers
Shabnam (Ericsson) provides comments that Nokia input covers most of our views as well on this thread, see below
Robert (Peraton Labs) responds to Laurent/Nokia.
Robert (Peraton Labs) provides updated CRs based on the discussion so far.
Haris(Qualcomm) proposes to revise the DP listing the open issues identified in this thread instead of revising the CRs
Robert (Peraton Labs) provides a rev of the discussion paper
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.28 S2-2209050 CR Approval 23.401 CR3713 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Shabnam (Ericsson) provides comments that the CR is to be postponed allowing overall agreement and solution scope under the Discussion document thread.
Pallab (Nokia) also proposed to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.28 S2-2209051 CR Approval 23.402 CR2998 (Rel-18, 'B'): MPS when access to EPC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Shabnam (Ericsson) provides comments that we see no reason to update PMIP support and we should also have a discussion on the Trusted WLAN case.
Pallab (Nokia) provides comments
Pallab (Nokia) proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.28 S2-2209052 CR Approval 23.501 CR3745 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Shabnam (Ericsson) provides comments to decide in CC#1 if the DP should be used as basis for discussion and other associated CRs (for DP 9049) need to be aligned with potential way forward.
Pallab (Nokia) also proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.28 S2-2209053 CR Approval 23.502 CR3595 (Rel-18, 'B'): MPS when access to 5GC is WLAN Peraton Labs, CISA ECD AT&T, Verizon Rel-18 Postponed Shabnam (Ericsson) provides comments to postpone the CR until discussion is completed on the overall solution scope.
Pallab (Nokia) also proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.28 S2-2209054 DISCUSSION Information User plane QoS differentiation via control plane. Peraton Labs Rel-18 Noted Laurent (Nokia): Comments
Shabnam (Ericsson) provides comments and expresses concerns on the proposal overall, don't believe it is needed and complex for actual usefulness purposes
Shabnam (Ericsson) resending comments of Nokia & Ericsson using correct email header, first email was missing agenda item on the Subject field, expresses concerns on the proposal overall, don't believe it is needed and complex for actual usefulness purposes
Marco (Huawei) comments and expresses concern on adding an SBI interface to an Access node and this interface is a second one from a CN NF which is against the principle to have all control via N2 only.
==== Revisions Deadline ====
==== Final Deadline ====
Noted
9.28 S2-2209055 CR Approval 23.401 CR3714 (Rel-18, 'B'): User plane QoS differentation via control plane Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Shabnam (Ericsson) provides comments that the CR is to be postponed until we can sort out the need for this additional feature.
Pallab (Nokia) also proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
Marco (Huawei) neutral on noted or posteponed, but next time the technical proposal should be different.
==== Final Deadline ====
Postponed
9.28 S2-2209056 CR Approval 23.402 CR2999 (Rel-18, 'B'): User plane QoS differentiation via control plane Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Marco (Huawei) object
Pallab (Nokia) proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
Marco (Huawei) Marco (Huawei) neutral on noted or posteponed, but next time the technical proposal should be different.

==== Final Deadline ====
Postponed
9.28 S2-2209057 CR Approval 23.501 CR3746 (Rel-18, 'B'): User plane QoS differentiation via control plane Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Marco (Huawei) object since the proposal add an SBI interface to an Access node and this interface is a second one from a CN NF which is against the principle to have all control via N2 only.
Pallab (Nokia) proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
Marco (Huawei) neutral on noted or posteponed, but next time the technical proposal should be different.

==== Final Deadline ====
Postponed
9.28 S2-2209059 CR Approval 23.502 CR3596 (Rel-18, 'B'): User plane QoS differentation via control plane Peraton Labs, CISA ECD, AT&T, Verizon Rel-18 Postponed Marco (Huawei) object since the proposal add an SBI interface to an Access node and this interface is a second one from a CN NF which is against the principle to have all control via N2 only.
Pallab (Nokia) proposes to postpone the CR as discussed in CC#1 and use the discussion papers for agreeing on the overall scope and impacts
==== Revisions Deadline ====
Marco (Huawei) neutral on noted or postponed, but next time the technical proposal should be different.
==== Final Deadline ====
Postponed
9.29 - - - Multiple location report for MT-LR Immediate Location Request for the regulatory service (TEI18_MLR) - - Docs:=2 -
9.29 S2-2208249 CR Approval 23.273 CR0233 (Rel-18, 'B'): Multiple location report for MT-LR Immediate Location Request for the regulatory service Ericsson, T-Mobile USA Rel-18 CC#4: This was postponed. A revision of 8249 or 9128 acceptable? Stephen (Qualcomm) provides an r01
Cai Simon (Nokia) comments r00 and r01
Richard (Ericsson) response to Nokia and Qualcomm
Cai Simon (Nokia) comments further
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.29 S2-2209128 CR Approval 23.273 CR0236 (Rel-18, 'B'): Multiple location report for MT-LR Immediate Location Request for the regulatory service Nokia, Nokia Shanghai Bell Rel-18 CC#4: This was postponed. A revision of 8249 or 9128 acceptable? Cai Simon (Nokia) provides r01
Richard (Ericsson) provides comments
Cai Simon (Nokia) clarifies to Richard (Ericsson)
Richard (Ericsson) answering to Simon (Nokia)
Cai Simon (Nokia) provides r02
Shabnam (Ericsson) provides comments that we cannot have same topic 2 CRs and it would have been appreciated if Nokia provided their view offline when we shared our CR well in advance. We object to original and all revisions and propose to combine efforts into one document 8249 to find common ground.
Cai Simon (Nokia) clarifies to Shabnam (Ericsson)
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
9.30 - - - Secondary DN Authentication and authorization in EPC IWK cases (TEI18_SDNAEPC) - - Docs:=4 -
9.30 S2-2208224 CR Approval 23.501 CR3701 (Rel-18, 'B'): Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell Rel-18 Revision of (noted) S2-2205472 from S2-152E. r02 agreed. Revised to S2-2209668. Fei (OPPO) comments.
Chris (Vodafone) provides r01.
Fei (OPPO) provides r02.
==== Revisions Deadline ====
Ashok (Samsung) comments
Fei (OPPO) replies.
Fenqin (Huawei) provides comments.
Fei (OPPO) provides replies and indicates that the first bullet should be updated to add one missing word-support.
Ashok (Samsung) seeks a clarification from Fei (OPPO)
Laurent (Nokia): answers, agrees with R01 (better)
Fei (OPPO) can only accept r02.
Fei (OPPO) replies to Ashok
==== Final Deadline ====
Revised
9.30 S2-2209668 CR Approval 23.501 CR3701R1 (Rel-18, 'B'): Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell Rel-18 Revision of S2-2208224r02. Approved Agreed
9.30 S2-2208225 CR Approval 23.502 CR3553 (Rel-18, 'B'): Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell Rel-18 Revision of (noted) S2-2205473 from S2-152E. r08 agreed. Revised to S2-2209669. Myungjune (LGE) provides comments.
Laurent (Nokia): provides r01
Ashok (Samsung) comments.
Stefan (Ericsson) provides comments
Laurent (Nokia): Comments
Laurent (Nokia): provides r02
Laurent (Nokia): provides r03
Fenqin (Huawei): ask a question for clarification
Laurent (Nokia): provides r04
Fenqin (Huawei): provide comments and r05
Stefan (Ericsson) provides r06
Fenqin (Huawei) ask a question for clarification
Stefan (Ericsson) replies to Fenqin
Chris (Vodafone) provides r07
Ashok (Samsung) provides r08
==== Revisions Deadline ====
Myungjune (LGE) asks question whether there is impact to DN-AAA.
Fenqin (Huawei) provides comments
Chris (Vodafone) answers LGE.
Ashok (Samsung) proposes to go with r08
Chris (Vodafone) supports r08. Can fine tune in next meeting.
==== Final Deadline ====
Revised
9.30 S2-2209669 CR Approval 23.502 CR3553R1 (Rel-18, 'B'): Secondary DN authentication and authorization in EPS IWK case Nokia, Nokia Shanghai Bell, Ericsson, Samsung Rel-18 Revision of S2-2208225r08. Approved Agreed
10 - - - Project Planning and Management - - Docs:=0 -
10.1 - - - Revised Rel-18 Study Items - - Docs:=3 -
10.1 S2-2208218 SID REVISED Approval Revised SID: Study on the support for 5WWC, Phase 2 Nokia, Nokia Shanghai Bell Rel-18 Update to SP-220419 (TSG SA-96). CC#4: This was postponed. ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.1 S2-2209044 SID REVISED Approval Revised SID: Study on system architecture for Next Generation Real Time Communication Services (FS_NG_RTC) China Mobile Rel-18 CC#4: This was postponed. Antoine (Orange) comments that the 'Total TU' figures do not correspond to the sum of TU per WT.
Rainer (Nokia) comments on no of TU for normative phase.
Yi (China Mobile) thanks Antoine and Rainer for pointing out the mistake. R01 and r02 are provided.
Rainer (Nokia) replies.
Yi (China Mobile) replies and prefer r02 as well.
Rainer (Nokia) provides r03.
==== Revisions Deadline ====
Yi (China Mobile) comments and still prefer r02.
Rainer (Nokia) is ok with r02 or r03.
Mu (Huawei) is ok with r02
Leo (Deutsche Telekom) supports r02.
==== Final Deadline ====
Rainer (Nokia) comments.
Postponed
10.1 S2-2209136 SID REVISED Approval Revised SID on Study on Architecture Enhancement to support Ranging based services and sidelink positioning. Xiaomi Rel-18 CC#4: This was postponed. ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.2 - - - TS/TR Cover sheets - - Docs:=6 -
10.2 S2-2208494 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-33 to TSG SA#98E for approval CATT, OPPO Rel-18 Postponed ==== Revisions Deadline ====
Deng Qiang (CATT) this cover sheet should be postponed.
==== Final Deadline ====
Postponed
10.2 S2-2208738 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-62 to TSG SA for approval China Mobile Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.2 S2-2208894 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-85 to TSG SA#98E Intel (Rapporteur) Rel-18 Postponed LaeYoung (LGE) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.2 S2-2209018 TS OR TR COVER Approval Cover sheet for presentation of TR 23.700-88 (FS_PIN) to SA#98 vivo Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.2 S2-2209045 P-CR Approval 23.700-87: Cover sheet for presentation of TR 23.700-87 to TSG SA#97. China Mobile Rel-18 Postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.2 S2-2209121 TS OR TR COVER Approval Presentation of Report to TSG: TR 23.700-58 Qualcomm Finland RFFE Oy Rel-18 Postponed. Not provided. WITHDRAWN ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.3 - - - New and revised Rel-18 Work Items - - Docs:=27 -
10.3 - - - Revised Rel-18 WIDs - - Docs:=14 -
10.3 S2-2208943 WID REVISED Approval Revised WID on generic group management, exposure and communication enhancements Huawei, HiSilicon, Samsung Rel-18 Update of SP-220959. CC#4: This was postponed. Laurent (Nokia): Concerns with some text of R00 that cannot be approved as is
Gerald (MATRIXX Software) supports this WID.
Qianghua (Huawei) provides r01
==== Revisions Deadline ====
==== Final Deadline ====
Qianghua (Huawei) provides r02 at draft folder
Laurent (Nokia): objects to R00 and R01
Postponed
10.3 S2-2208289 WID REVISED Approval Revise WID on 5G AM Policy (AMP) SA WG2 Rel-18 Update to SP-220807 (TSG SA#97E). CC#4: r03 agreed. Revised to S2-2209984. Shabnam (Ericsson) provides comments that SA#99 is not planned to be Electronic as per 3gpp portal so the E should be removed from #99.
Zhuoyi (China Telecom) provides r01 according to Ericsson's comment.
==== Revisions Deadline ====
==== Final Deadline ====
Zhuoyi (China Telecom) provides r02 according to approved CRs at this meeting.
Haris(Qualcomm) comments on r02
Zhuoyi(China Telecom) replies to Haris.
Zhuoyi(China Telecom) provides r03 removing 'specific clause description'.
Revised
10.3 S2-2209984 WID REVISED Approval Revised WID on 5G AM Policy. China Telecom Rel-18 Revision of S2-2208289r03. Approved Approved
10.3 S2-2208458 WID REVISED Approval Revised WID: 5G System Enabler for Service Function Chaining Intel Rel-18 Revision of (Approved) S2-2207866 from S2#152E. CC#4: r01 agreed. Revised to S2-2209985. ==== Revisions Deadline ====
==== Final Deadline ====
Revised
10.3 S2-2209985 WID REVISED Approval Revised WID: 5G System Enabler for Service Function Chaining. Intel Rel-18 Revision of S2-2208458r01. Approved Approved
10.3 S2-2208493 WID REVISED Approval Revised WID on Proximity-based Services in 5GS Phase 2 CATT, OPPO Rel-18 Update to SP-220806 (TSG SA#97E). CC#4: This was approved. ==== Revisions Deadline ====
==== Final Deadline ====
Approved
10.3 S2-2208678 WID REVISED Approval Revised WID: Support for 5WWC, Phase 2 Nokia, Nokia Shanghai Bell Rel-18 Update of SP-220800. CC#4: This was postponed. ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.3 S2-2208798 WID REVISED Approval Revised WID: Edge Computing Phase 2 Huawei, HiSilicon Rel-18 Update of SP-220987. CC#4: r01 agreed. Revised to S2-2209986. Gerald (MATRIXX Software) supports this WID.
Patrice (Huawei) thanks Gerald (Matrixx Software) for his support, and will provide an r01 once the conclusions for the study are stable.
==== Revisions Deadline ====
Mehrdad (Mediatek Inc.) comments on all revisions of the WID.
Patrice (Huawei) replies.
==== Final Deadline ====
Revised
10.3 S2-2209986 WID REVISED Approval Revised WID: Edge Computing Phase 2. Huawei, HiSilicon Rel-18 Revision of S2-2208798r01. Approved Approved
10.3 S2-2208814 WID REVISED Approval Revised WID on Enhancement to the 5GC LoCation Services Phase 3 CATT, Huawei Rel-18 CC#4: r01 agreed. Revised to S2-2209987. Gerald (MATRIXX Software) supports this WID.
==== Revisions Deadline ====
==== Final Deadline ====
Gerald (MATRIXX Software) with comment on rapporteurship.
Runze (Huawei) supports r01.
Revised
10.3 S2-2209987 WID REVISED Approval Revised WID on Enhancement to the 5GC LoCation Services Phase 3. CATT, Huawei Rel-18 Revision of S2-2208814r01. Approved Approved
10.3 S2-2208895 WID REVISED Approval Revised WID: Enhancement of 5G UE Policy Intel (Rapporteur) Rel-18 CC#4: This was postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.3 S2-2209142 WID REVISED Approval Revised WID: Timing Resiliency and URLLC enhancements. SA WG2 Rel-18 CC#4: This was postponed ==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.3 S2-2209205 WID REVISED Approval Revised WID on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. Lenovo Rel-18 Approved ==== Revisions Deadline ====
Apostolis (Lenovo) provides the revised WID on ATSSS_ph3 with a new objective to define a steering functionality based on the conclusions of KI#2.
Rainer (Nokia) supports this update.
==== Final Deadline ====
Approved
10.3 - - - New Rel-18 WIDs - - Docs:=13 -
10.3 S2-2208436 WID NEW Approval New WID on System support for AI/ML-based Services OPPO, Samsung Rel-18 CC#4: This was postponed Malla (NTT DOCOMO) provided comment
David (Samsung) replies to Docomo
LaeYoung (LGE) comments.
==== Revisions Deadline ====
Belen (Ericsson) objects to the current version of this WID.
Tricci (OPPO) responds to LaeYoung (LGE) comments.
Tricci (OPPO) would like to Belen (Ericsson) the current version of the WID is just a place holder for now until the ongoing discussions are concluded.
David (Samsung) comments and provides r01
Yannick (Nokia): Nokia provides comments to the WID and on ongoing discussion points.
Belen (Ericsson) replies to OPPO that it is a place holder with some assumptions we cannot agree at the moment
Belen (Ericsson) objects to r01
Mehrdad (Mediatek Inc.) comments on original version and revision 01
==== Final Deadline ====
Juan Zhang (Qualcomm) provides comments
David (Samsung) provides r03 (you may disregard r02)
Belen (Ericsson) objects to r03.
David (Samsung) provides r04.
Postponed
10.3 S2-2208649 WID NEW Approval New WID on Enablers for Network Automation for 5G - phase 3 China Mobile M2M Company Ltd. Rel-18 CC#4: This was postponed Hui (Huawei) proposes to merge this paper into S2-2208568, and take S2-2208568 as baseline for evaluation/conclusion of KI4 and 5.
Hui (Huawei) withdraws the previous comment to S2-2208649. Wrong tdoc number was used.
Thomas (Nokia) suggests to remove last objective
Comments that objectives need to be checked against conclusions achieved at the end of this meeting
David (Samsung) concurs with Thomas (Nokia) and requests the last objective to be removed
Jinsook (DISH) The list of supporting companies are different from SID
Aihua(CMCC) provides r01.
Gerald (MATRIXX Software) supports this WID.
Aihua(CMCC) provides r02, adding MATRIXX Software as supporting company.
Abbas (Futurewei) asks to add Futurewei as a supporting company
==== Revisions Deadline ====
Belen (Ericsson) asks to add Ericsson as supporting company, asks questions
Aihua(CMCC) provides r03.
Thomas(Nokia) provides comments
==== Final Deadline ====
Aihua(CMCC) replies.
Xiaobo(Nokia) provides clarification.
Thomas(Nokia) replies to Aihua
Juan Zhang (Qualcomm) provides comments.
Aihua(CMCC) replies to Juan Zhang (Qualcomm) there is no impact on UE for FS_eNA_Ph3. And will remove UE impact in the revision.
Postponed
10.3 S2-2208665 WID NEW Approval New WID: 5GC/EPC enhancement for satellite access Phase 2 THALES Rel-18 CC#4: This was postponed Hannu (Nokia): comments that this WID needs to be aligned with the conclusions by the end of this meeting.
Jean-Yves (Thales): answers to hannu's comment
Gerald (MATRIXX Software) supports this WID.
Yuxin(Xiaomi) adds MATRIXX Software as support company as Gerald (MATRIXX Software) proposed.
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.3 S2-2208703 WID NEW Approval New WID: Architecture Enhancements for XR and media services China Mobile, Tencent, Tencent Cloud, Huawei, HiSilicon Rel-18 CC#4: This was postponed Dan (China Mobile) provides r01.
Gerald (MATRIXX Software) with comment on charging.
Lei(Tencent) provides comments to Gerald(MATRIXX Software).
Dan (China Mobile) provide r02 with adding SA5 for charging.
==== Revisions Deadline ====
==== Final Deadline ====
Shabnam (Ericsson) provides comments that the WI needs to reflect agreement and which items are actually ready for normative work. Currently it is missing any details.
Dan (China Mobile) ask
Dan (China Mobile) provide r03
Lei (Tencent) provides comments. Fine with r02 as there are still ENs in some KIs conclusion papers. One typo need to be corrected 'KIKI#9'
Haris(Qualcomm) comments on r03
Dan(China Mobile) reply
Saso (Intel) proposes for this meeting to refocus the WID only on KIs that have reached sufficient level of conclusion.
Dan(China Mobile) provide r04
Saso (Intel) comments that r04 needs to be beefed up.
Dan (China Mobile) comments
Lei(Tencent) provides comments to Saso(Intel)
Dan(China Mobile) provides r05
Postponed
10.3 S2-2208729 WID NEW Approval New WID on Architectural enhancements for 5G multicast-broadcast services Phase 2 (5MBS_Ph2) Huawei, HiSilicon Rel-18 CC#4: r01 agreed. Revised to S2-2209988. Robbie (Ericsson) comments that the WID needs to be updated based on the conclusions agreed in this meeting.
Thomas (Nokia) suggests improvement of bullet c
==== Revisions Deadline ====
==== Final Deadline ====
Revised
10.3 S2-2209988 WID NEW Approval New WID on Architectural enhancements for 5G multicast-broadcast services Phase 2 (5MBS_Ph2). Huawei, CBN Rel-18 Revision of S2-2208729r01. Approved Approved
10.3 S2-2208819 WID NEW Approval New WID: Enhancement of Network Slicing Phase 3 ZTE, LG Electronic Rel-18 CC#4: This was postponed Gerald (MATRIXX Software) supports this WID.
==== Revisions Deadline ====
Jinguo(ZTE) provides r01 in the draft folder
Myungjune (LGE) provides r02 in the draft folder
==== Final Deadline ====
Fenqin (Huawei) provides r03 in the CC#4 folder
Haiyang (Huawei) provides r04 in the CC#4 folder
Kundan (NEC) comments. Let's not partially allowed NSSAI yet until we receive RAN3 response. so we suggest to not remove partially allowed NSSAI at this moment.
Haiyang (Huawei) provides reply to Kundan (NEC)
Kundan (NEC) further clarifies with Haiyang.
Peter Hedman (Ericsson) propose to either postpone the WID to the November meeting or only include objectives for KIs without any EN in the conclusion.
George (Ericsson) provides comment. We would like KI4 not to go to the WID yet as we have to address roaming. So please remove it
Fenqin(Huawei) would like to keep KI#4 in the objective and update the objective to include the roaming part at the next meeting
George (Ericsson) provides response. We need to state that roaming is not in the WID, and still part of the study. Please make sure this is clear
Fenqin (Huawei) provides response.
George (Ericsson) provides response. I prefer that we not include the KI4 in the WID at this meeting. We can update next mtg.
alessio( nokia) suggests to keep this in the WID (which anyhow is not approved by SA yet) and say 'NOTE: the work on Partially allowed NSSAI can start once the RAN evaluation of feasibility is received and indicates feasibility'
Fenqin (Huawei) How about we add a NOTE like this, Note: roaming part is to be started after it is concluded.
George Foti (Ericsson) The note should say: roaming part is to be started after it is concluded in the SID.
Jinguo(ZTE) provides r05
Postponed
10.3 S2-2209017 WID NEW Approval New WID: Personal IoT Networks vivo Rel-18 CC#4: r05 agreed. Revised to S2-2209989. ==== Revisions Deadline ====
==== Final Deadline ====
Pallab (Nokia) provides comments and uploaded r01
Haris(Qualcomm) comments on r01
Pallab (Nokia) replies
Qian (Ericsson) provides comments
Zhenhua (vivo) provides r01
Zhenhua (vivo) actually provides r02 but wrongly indicates r01
Zhenhua (vivo) provides r03 to add more supporting companies
Kefeng (Qualcomm) provides r05 to add one more bullet: 5GC architecture enhancements to support PIN
Revised
10.3 S2-2209989 WID NEW Approval New WID: Personal IoT Networks. vivo Rel-18 Revision of S2-2209017r05. Approved Approved
10.3 S2-2209070 WID NEW Approval New WID on Architecture Enhancements for Vehicle Mounted Relays Qualcomm Incorporated, Sony, InterDigital Inc., AT&T, ZTE Corporation, vivo Mobile Communications Ltd, Philips International B.V., Xiaomi, FirstNet, LG Electronics, Apple, Nokia, Nokia Shanghai Bell, Intel, Deutsche Telekom Rel-18 CC#4: This was postponed LiMeng (Huawei) comments on the second bullet of the objective.
Gerald (MATRIXX Software) supports this WID.
Hong (Qualcomm) provides r01.
==== Revisions Deadline ====
==== Final Deadline ====
Hong (Qualcomm) provides r02.
Hong (Qualcomm) provides r03.
Postponed
10.3 S2-2209117 WID NEW Approval New WID on Further Architecture Enhancement for UAV and UAM Qualcomm Incorporated CC#4: r01 + Supporting Companies agreed. Revised to S2-2209990. LaeYoung (LGE) comments.
==== Revisions Deadline ====
==== Final Deadline ====
Revised
10.3 S2-2209990 WID NEW Approval New WID on Further Architecture Enhancement for UAV and UAM. Qualcomm Incorporated - Revision of S2-2209117r01 + Supporting Companies. Approved Approved
10.3 S2-2209135 WID NEW Approval New WID on Architecture Enhancement to support Ranging based services and sidelink positioning Xiaomi Rel-18 CC#4: This was postponed Gerald (MATRIXX Software) supports this WID.
Walter Dees (Philips) suggests some changes.
Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) thanks Gerald (MATRIXX Software) for supporting this WID.
Walter (Philips) agrees with r01
==== Revisions Deadline ====
==== Final Deadline ====
Postponed
10.4 - - - Rel-18 SID/WID Status Reports - - Docs:=52 -
10.4 S2-2208818 WI STATUS REPORT Endorsement Status report for FS_eNS_Ph3 ZTE Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209120 WI STATUS REPORT Endorsement WI Status Report: Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) Qualcomm Finland RFFE Oy Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209208 WI STATUS REPORT Endorsement Status Report: Study on Stage 2 for Proximity based Services Phase 2 CATT Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209209 WI STATUS REPORT Endorsement Status Report: Study on 5GC enhancement for satellite access Phase 2 Thales Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209210 WI STATUS REPORT Endorsement Status Report: Study on Support of Satellite Backhauling in 5GS CATT Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209211 WI STATUS REPORT Endorsement Status Report: Study on architectural enhancements for 5G multicast-broadcast services Phase 2 Huawei Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209212 WI STATUS REPORT Endorsement Status Report: Study on 5G Timing Resiliency and TSC&URLLC enhancements Nokia Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209213 WI STATUS REPORT Endorsement Status Report: Study on the support for 5WWC Phase 2 Nokia Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209214 WI STATUS REPORT Endorsement Status Report: Study on 5G System Support for AI/ML-based Services OPPO Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209215 WI STATUS REPORT Endorsement Status Report: Study on 5G AM Policy China Telecom Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209216 WI STATUS REPORT Endorsement Status Report: Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209217 WI STATUS REPORT Endorsement Status Report: Study on Extensions to the TSC Framework to support Deterministic Networking (DetNet) Ericsson Rel-18 WITHDRAWN Withdrawn
10.4 S2-2209218 WI STATUS REPORT Endorsement Status Report: Study on Stage 2 of Edge Computing phase 2 Huawei Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209219 WI STATUS REPORT Endorsement Status Report: Study on Enhancement to the 5GC LoCation Services-Phase 3 CATT Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209220 WI STATUS REPORT Endorsement Status Report: Study on Enablers for Network Automation for 5G - phase 3 China Mobile Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209221 WI STATUS REPORT Endorsement Status Report: Study on enhanced support of Non-Public Networks phase 2 Ericsson Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209222 WI STATUS REPORT Huawei Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209223 WI STATUS REPORT Endorsement Status Report: Study on generic group management, exposure and communication enhancements Huawei Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209224 WI STATUS REPORT Endorsement Status Report: Study on system architecture for next generation real time communication services China Mobile Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209225 WI STATUS REPORT Endorsement Status Report: Study on Personal IoT Networks vivo Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209226 WI STATUS REPORT Endorsement Status Report: Study on Ranging based services and sidelink positioning Xiaomi Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209227 WI STATUS REPORT Endorsement Status Report: Study on RedCap Phase 2 Ericsson Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209228 WI STATUS REPORT Endorsement Status Report: Study on System Enabler for Service Function Chaining Intel Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209229 WI STATUS REPORT Endorsement Status Report: Study on Seamless UE context recovery Samsung Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209230 WI STATUS REPORT Endorsement Status Report: Study on UPF enhancement for Exposure And SBA China Mobile Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209231 WI STATUS REPORT Endorsement Status Report: Study on Architecture Enhancements for Vehicle Mounted Relays Qualcomm Incorporated Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209232 WI STATUS REPORT Endorsement Status Report: Study on architecture enhancement for XR and media services China Mobile Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209189 WI STATUS REPORT Endorsement SUECR Status Report Samsung Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209233 WI STATUS REPORT Endorsement Status Report: 5GC LoCation Services - Phase 3 CATT Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209234 WI STATUS REPORT Endorsement Status Report: Stage 2 of 5GSATB CATT Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209235 WI STATUS REPORT Endorsement Status Report: Support for Wireless and Wireline Convergence Phase 2 Nokia Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209236 WI STATUS REPORT Endorsement Status Report: 5G AM Policy China Telecom Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209237 WI STATUS REPORT Endorsement Status Report: Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 3 Lenovo Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209238 WI STATUS REPORT Endorsement Status Report: Extensions to the TSC Framework to support DetNet Ericsson Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209239 WI STATUS REPORT Endorsement Status Report: Edge Computing Phase 2 Huawei Technologies Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209240 WI STATUS REPORT Endorsement Status Report: Stage 2 of Non-Public Networks Phase 2 Ericsson Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209241 WI STATUS REPORT Endorsement Status Report: Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection ZTE Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209242 WI STATUS REPORT Endorsement Status Report: Enhancement of 5G UE Policy Intel Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209243 WI STATUS REPORT Endorsement Status Report: Generic group management, exposure and communication enhancements Huawei Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Qianghua (Huawei) provides r01 at draft folder
Withdrawn
10.4 S2-2209244 WI STATUS REPORT Endorsement Status Report: Stage 2 of MPS_WLAN Peraton Labs Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209245 WI STATUS REPORT Endorsement Status Report: System architecture for Next Generation Real time Communication services China Mobile Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209246 WI STATUS REPORT Endorsement Status Report: NR RedCap UE with long eDRX for RRC_INACTIVE State Ericsson Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209247 WI STATUS REPORT Endorsement Status Report: 5G System Enabler for Service Function Chaining Intel Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209248 WI STATUS REPORT Endorsement Status Report: TEI18 on Enhancement of Application Detection Event Exposure China Mobile Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209249 WI STATUS REPORT Endorsement Status Report: Dynamically Changing AM Policies in the 5GC Phase 2 China Telecom Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209250 WI STATUS REPORT Endorsement Status Report: General Support of IPv6 Prefix Delegation in 5GS Ericsson Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209251 WI STATUS REPORT Endorsement Status Report: MBS support for V2X services LG Electronics Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209252 WI STATUS REPORT Endorsement Status Report: Multiple location report for MT-LR Immediate Location Request for regulatory services T-Mobile USA Rel-18 Noted. Not provided. WITHDRAWN ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209253 WI STATUS REPORT Endorsement Status Report: Secondary DN Authentication and authorization in EPC IWK cases Nokia Rel-18 Noted ==== Revisions Deadline ====
==== Final Deadline ====
Noted
10.4 S2-2209254 WI STATUS REPORT Endorsement Status Report: Spending Limits for AM and UE Policies in the 5GC Oracle Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209255 WI STATUS REPORT Endorsement Status Report: Stage 2 of Timing Resiliency and URLLC enhancements Nokia Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.4 S2-2209256 WI STATUS REPORT Endorsement Status Report: UPF enhancement for Exposure and SBA China Mobile Rel-18 Withdrawn ==== Revisions Deadline ====
==== Final Deadline ====
Withdrawn
10.5 - - - Review of the Work Plan - - Docs:=0 -
10.6 - - - Planning future meetings - - Docs:=0 -
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=561 -
99 S2-2208680 CR Approval 23.501 CR3726 (Rel-18, 'B'): Introduction to N3IWF selection to support the slices needed by the UE Nokia, Nokia Shanghai Bell Rel-18 WITHDRAWN Withdrawn
99 S2-2209048 DISCUSSION Information KI#2: Discussion paper on outstanding issues NEC Rel-18 WITHDRAWN Withdrawn
99 S2-2209027 LS OUT Approval [DRAFT] LS on Traffic Categories Deutsche Telekom (to be: SA2) Rel-18 Revised to S2-2209036. WITHDRAWN Withdrawn
99 S2-2209066 CR Approval 23.502 CR3519R1 (Rel-17, 'F'): Support for 5QI Priority Level in QoS constraints Peraton Labs, CISA ECD, AT&T, Verizon Rel-17 WITHDRAWN Withdrawn
99 S2-2209147 P-CR Approval 23.700-08: KI#4: Update Sol#42 and remove ENs. Samsung Rel-18 WITHDRAWN Withdrawn
99 S2-2208675 P-CR Approval 23.700-28: Update Evolution and Conclusion for KI#1 and KI#2 Google Inc. Rel-18 WITHDRAWN Withdrawn
99 S2-2209030 P-CR Approval 23.700-41: Update to Sol#43 vivo Rel-18 WITHDRAWN Withdrawn
99 S2-2208664 P-CR Approval 23.700-80: FS_AIMLsys KI#7, Evaluation and Conclusion China Mobile M2M Company Ltd. Rel-18 WITHDRAWN Withdrawn
99 S2-2208177 CR Approval 23.502 CR3550 (Rel-18, 'B'): CR_23502_New timer for RFSP Index validity when mobility from 5G to 4G via N26 China Telecom Corporation Ltd. Rel-18 WITHDRAWN Withdrawn
99 S2-2208178 CR Approval 23.316 CR2071 (Rel-17, 'F'): Change the direction of the arrow in figure IPLOOK Rel-17 WITHDRAWN Withdrawn
99 S2-2208202 P-CR Approval 23.700-80: Sample 1 MediaTek Inc. Rel-18 WITHDRAWN Withdrawn
99 S2-2208203 P-CR Approval 23.700-80: Sample 3 MediaTek Inc. Rel-18 WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 359
Agreed: 81
Replied to LSs: 19
Noted: 179
Merged: 281
For e-mail approval: 0
Postponed: 107
Withdrawn: 143
Total documents: 1515