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-2103714 AGENDA Approval SA WG2 #145E Meeting Agenda SA WG2 Chair CC#5: Approved Approved
2.1 - - - IPR Call and Antitrust Reminder - - Docs:=0 -
2.2 - - - SA WG2 Elections - - Docs:=0 -
3 - - - SA2#144E Meeting report - - Docs:=2 -
3 S2-2103715 REPORT Approval Auto-Generated Report of SA WG2 meeting #144E SA WG2 Secretary Approved Approved
3 S2-2104788 OTHER Presentation SA WG2 Excellence Award SA WG2 Noted Noted
4 - - - General - - Docs:=0 -
4.1 - - - Common issues and Incoming LSs - - Docs:=37 -
4.1 - - - LS in for Information - - Docs:=8 -
4.1 S2-2103729 LS In Information LS from WBA 5G Work Group: Liaison Statement on 5G & Wi-Fi RAN Convergence WBA 5G Work Group (WBA LS on 5G Wi-Fi RAN Convergence) Revision of Postponed S2-2102130 from S2#144E. Postponed Postponed
4.1 S2-2103732 LS In Information LS from GSMA NG NRG: LS to 3GPP SA2 on ARP PL GSMA NG NRG (NRG 009_201 - LS to 3GPP SA2 CT3 ARP) Postponed Thomas (Nokia) proposes to postpone the LS
Judy (Ericsson) support the propsoal from Thomas (Nokia) to postpone this LS
Postponed
4.1 S2-2103733 LS In Information LS from ITU-T FG-VM: LS on the latest results on the Vehicular Multimedia deliverables from ITU FG-VM ITU-T FG-VM (FGVM-LS51) Noted Leo (Deutsche Telekom) propose to NOTE this LS, it is for information and no action to SA2.
LaeYoung (LGE) seconds Leo (Deutsche Telekom), so this LS can be NOTED
Noted
4.1 S2-2103734 LS In Information Reply LS on User Plane Integrity Protection for eUTRA connected to EPC RAN WG2 (R2-2104349) Rel-17 Noted Wanqiang (Huawei) proposes to NOTE this LS, it is for information and no action to SA2 Noted
4.1 S2-2103741 LS In Information LS from SA WG4: LS on Media-Related Services and Requirements SA WG4 (S4-210680) Rel-18 Noted Wanqiang (Huawei) proposes to NOTE this LS, it is for information and no action to SA2 Noted
4.1 S2-2103763 LS In Information Reply LS on Server Domain Name Usage for Application Traffic Detection CT WG3 (C3-212404) Rel-16 Noted Noted
4.1 S2-2103772 LS In Information LS from RAN WG2: LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism RAN WG2 (R2-2104654) Rel-17 Noted Shabnam (Ericsson) proposes to NOTE the LS as no action needed from SA2.
Fei (OPPO) proposed to NOTE this LS
Noted
4.1 S2-2103775 LS In Information LS from RAN WG2: LS to CT WG1 on Small data transmission RAN WG2 (R2-2104644) Rel-17 Noted Wanqiang (Huawei) proposes to NOTE this LS, it is for information and no action to SA2 Noted
4.1 - - - LS in for Action (no response) - - Docs:=3 -
4.1 S2-2103745 LS In Action LS from SA WG6: Reply LS on IP address to GPSI translation SA WG6 (S6-211082) Rel-17 Postponed Laurent (Nokia): suggests to postpone the LS waiting for SA3 answer to our LS on the topic
Magnus (Ericsson): Agrees with Laurent, the LS should be postponed and handled together the SA3 answer on the same topic.
Hui(Huawei): support to postpone the LS
Dieter (Deutsche Telekom): also supports postponing the LS
Postponed
4.1 S2-2103718 LS In Action LS on stage 3 aspects for Reliable Data Service Serialization Indication CT WG1 (C1-207769) Revision of Postponed S2-2102086 from S2#144E. Postponed Mike (Convida Wireless) asks to POSTPONE this document. We will bring CRs and an LS response to SA2 #146e to address this after the Rel-17 version of TS 23.682 is created.
Hannu (Nokia) supports the proposal from Mike (Convida Wireless) to POSTPONE. The matter is not controversial, but we agreed to wait for Rel-17 TS version.
Steve (Huawei) same view about postponing.
Hannu (Nokia) agrees the intention of Steve (Huawei).
Mike (Convida Wireless) agree with Steve (Huawei) and Hannu (Nokia)
Postponed
4.1 S2-2103774 LS In Action LS from GSMA 5GJA: LS to 3GPP SA2 on URSP Traffic Descriptor GSMA 5GJA (5GJA16_109r2) Rel-17 Postponed Hoyeon (Samsung) proposes to postpone the LS
Dimitris (Lenovo) agrees with Hoyeon (Samsung) and propose to postpone.
Dieter (Deutsche Telekom): also proposes to postpone the LS...
alessio(Nokia) supports Dieter (DT), Hoyeon(Samsung)
Farooq (AT&T) supports postponing of handling the LS to the next meeting so that required CR is created.
Haris(Qualcomm) suggests to postpone the LS
Krisztian (Apple) also asks to postpone the LS.
Mike (Convida Wireless) comments
Postponed
4.1 - - - Session Management Policy per PLMN - - Docs:=1 -
4.1 S2-2104140 LS OUT Approval LS Reply on Session Management Policy Data per PLMN Huawei, HiSilicon Rel-17 Response to S2-2103722. Merged into S2-2104002 (Postponed) Laurent (Nokia): suggest to take S2-2104002 (the other LS out) to be the final LS as well as the thread to discuss the topic
Dieter (Deutsche Telekom): proposes to discuss the issue in one thread only and mark this LS answer proposal as merged into S2-2104002.
Haiyang(Huawei) is ok to mark this LS answer proposal as merged into S2-2104002.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
4.1 - - - 5G capabilities exposure - - Docs:=4 -
4.1 S2-2103727 LS In Action LS from 5G-ACIA: 5G capabilities exposure for factories of the future - revised 5G-ACIA (5G-ACIA_LS_3GPP_Exposure_18032021) Revision of Postponed S2-2102128 from S2#144E. Coordination response to 3GPP groups in S2-2104794. Postponed for feedback from TSG SA Qianghua (Huawei) invites anyone interested on this LS to have a look for S2-2104189
Laurent (Nokia): proposes to postpone again the LS. August meeting should be a better time to decide what to do with the LS
Dieter (Deutsche Telekom): comments that SA plenary should coordinate any potential LS answer to ACIA and proposes that SA2 should sent such request to plenary.
laurent (Nokia): 1) agrees that SA plenary should coordinate any potential LS answer to ACIA : SA2 should sent a LS immediately to SA1, SA5, SA6 and SA for this purpose AND 2) proposes that SA2 feedbacks technically to SA plenary in August : Proposes also to postpone the LS.
Sang-Jun (Samsung) also agrees that SA plenary should coordinate any potential LS answer to ACIA and proposes to postpone the LS.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): suggests to keep the LS in open as long as we haven't provided our feedback to TSG SA
Postponed
4.1 S2-2104787 LS OUT Approval [DRAFT] LS on 5G capabilities exposure for factories of the future Nokia - Related to S2-2103727. r03 agreed. Revised to S2-2104794. Laurent (Nokia): provides r00
Qianghua (Huawei) provides r01
Laurent (Nokia): provides r02
Peter Hedman (Ericsson) provides r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): supports R03 (supports any version but R01) but would like to add SA5, CT3 in CC of the LS
Dieter (Deutsche Telekom): agrees with Nokia, i.e. supports r03 with addition of SA5 and CT3.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2104794 LS OUT Approval LS on 5G capabilities exposure for factories of the future SA WG2 - Revision of S2-2104787r03. Approved Approved
4.1 S2-2104189 DISCUSSION Discussion Work analytics on 5G capabilities for factories of the future requested by 5G-ACIA. Huawei, HiSilicon Rel-17 Noted Laurent (Nokia): suggests to postpone
Qianghua (Huawei) invites anyone interested to provide their thoughts for information, not close the door at the beginning of this meeting
Laurent (Nokia): answers
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.2 - - - P-CRs/CRs related to use of inclusive language in 3GPP - - Docs:=0 -
4.1 - - - RedCap - - Docs:=8 -
4.1 S2-2103769 LS In Action LS from RAN WG2: LS on introducing extended DRX for RedCap UEs RAN WG2 (R2-2104374) Rel-17 Responses drafted in S2-2103796, S2-2103902 and S2-2104343 (Postponed). Postponed Postponed
4.1 S2-2103796 LS OUT Approval [DRAFT] Reply LS on introducing extended DRX for RedCap UEs Qualcomm Technologies Int Rel-17 Response to S2-2103769. Postponed Paul (Ericsson) provides r01 of S2-2103796 with S2-2104343 being merged in. Ericsson object to r0 of S2-2103796.
Hannu (Nokia) provides r02.
Paul (Ericsson) provides r03 and a response to Hannu (Nokia). We object r02 as it contains incorrect information on SA2 work plan and information that is not in scope of the related RAN work item.
Miguel (Qualcomm) disagrees with any LS version that indicates SA2 will study solutions for RRC inactive eDRX > 10.24s, so all versions so far. It is also false that a feasible solution was documented in 5G CIoT TR.
Hannu (Nokia) provides r04 and reminds Paul (Ericsson) that TS 23.501 requirements for AMF serving the UE over different RATs means that the consideration of interaction with other RAT Types is not incorrect but essential aspect.
Sherry (Xiaomi) comments and provides r05.
Chris (Vodafone) comments that CT 4 need to be involved on the feasibility of long eDRX in Inactive. See their LS in S2-2103765.
Paul (Ericsson) replies to Miguel (Qualcomm) that at no time SA2 considered the solution documented in the Rel-16 CIoT TR as not being feasible.
Miguel (Qualcomm) asks Paul to point where in TR 23.724 Conclusions section (8.4) it says that the solution is feasible. That was your claim, but it is false, there was no such agreement. There was company provided solution that was not agreed.
Guillaume (MediaTek) comments.
Wanqiang (Huawei) comments and provides r06.
Aihua (China Mobile) comments.
Dieter (Deutsche Telekom): fully agrees with MediaTek and the view expressed by Ericsson.
Paul (Ericsson) provides r07.
Miguel (Qualcomm) cannot agree to r07 and provides r08. Also comments if no CR is agreed at this meeting, the LS cannot be sent
Hannu (Nokia) supports r08. Can't agree r07 or any revision that promises to extend RRC Inactive eDRX cycle in Rel-17.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Paul (Ericsson) replies, we can live with r08.
Wanqiang (Huawei) OK with r08.
Dieter (Deutsche Telekom): we can also live with r08.
Guillaume (MediaTek) is ok with r08 as well.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
China Mobile(Aihua) is fine with r08.
Sherry (Xiaomi) is fine with r08, which is more neutral and reflects our current status.
Miguel (Qualcomm) supports r08 conditional to approval of CR in S2-2103798, but asks to be NOTED if CR is not approved.
Postponed
4.1 S2-2103902 LS OUT Approval [DRAFT] Reply LS on introducing extended DRX for RedCap UEs Ericsson Rel-17 Response to S2-2103769. Noted Miguel (Qualcomm) proposes NOTE this LS and use S2-2103796 instead
Wanqiang (Huawei) agree to use S2-2103796 or S2-2104343 instead.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2104343 LS OUT Approval [DRAFT] Reply LS on introducing extended DRX for RedCap UEs China Mobile Rel-17 Response to S2-2103769. Merged into S2-2103796 (Postponed) Miguel (Qualcomm) proposes to merge this draft LS with S2-2103796
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Aihua (China Mobile) agrees to merge. .
Postponed
4.1 S2-2103798 CR Approval 23.501 CR2857 (Rel-17, 'B'): Extended DRX for NR (RedCap) Qualcomm Inc. Rel-17 Postponed Antoine (Orange) provides r01 removing the e.g. on heterogeneous support this this example no longer applies.
Hannu (Nokia) co-signs the CR and explains the reasons on the cover page.
Paul (Ericsson) proposes to note this CR.
Miguel (Qualcomm) exlains Ericsson's argument is false and insists on proceeding with this CR as basis
Hannu (Nokia) supports this CR and points out it's a logical extension of what we have got already in 5G CIoT specifications.
Sherry (Xiaomi) agrees to start from extending the existing texts, but still has some concerns.
Paul (Ericsson) proposes to postpone this CR at this meeting.
Miguel (Qualcomm) provides r03 to address Sherry's (Xiaomi) comment and insists to proceed with this alignment CR
Hannu (Nokia) asks Paul (Ericsson) to identify the issues that this alignment CR brings along to justify postponing?
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Sherry (Xiaomi) replies to Miguel.
Miguel (Qualcomm) replies to Sherry eDRX is negotiated in NAS for NR.
Antoine (Orange) supports approving this CR (r03) at this meeting.
Sherry (Xiaomi) replies to Miguel (Qualcomm) and can live with r02 as the baseline with the assumption of further updates to address the open issues.
Antoine (Orange): The typo of 'NW' instead of 'NR' has to be fixed as part of CR clean-up.
Miguel (Qualcomm) agrees with Antoine
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Paul (Ericsson) replies to Miguel (Qualcomm).
Miguel (Qualcomm) replies to Paul (Ericsson)
Guillaume (MediaTek) comments.
Tricci (OPPO) thanks Guillaume (MediaTek) the excellent summary and supports Guillaume's proposal.
Paul (Ericsson) also supports Guillaume's (MediaTek) proposal on the way forward.
Dieter (Deutsche Telekom) also supports Guillaume's (MediaTek) proposal on the way forward.
Hannu (Nokia) comments on the delta approach in 3903.
Postponed
4.1 S2-2103903 CR Approval 23.501 CR2869 (Rel-17, 'B'): Support for RedCap UE indication and eDRX Ericsson, MediaTek Inc. Rel-17 Noted Chris (Vodafone): we need to decide on eDRX of > 10.24s for Inactive. NOT add an FFS !
Miguel (Qualcomm) proposes NOTE this CR and use S2-2103798 instead
Wanqiang (Huawei) comment and ask more discussions on the RRC inactive handling.
Paul (Ericsson) provides r01.
Sherry (Xiaomi) requests for clarification.
Miguel (Qualcomm) insists on using S2-2103798 instead as basis
Hannu (Nokia) supports Miguel's proposal to work this out via 3798 and points out that the EN in clause 5.x.2.3 hides a new study item.
Paul (Ericsson) proposes to postpone this CR at this meeting.
Guillaume (MediaTek) supports postponing this and proposes some min. working assumption.
Hannu (Nokia) supports the proposal from Guillaume (MediaTek) to identify minimum working assumption.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Tricci (OPPO) thanks Guillaume (MediaTek) suggestion and supports the minimum working assumptions as proposed by MediaTek.
Dieter (Deutsche Telekom): supports the minimum working assumptions as proposed by MediaTek including the agreement to work on eDRX cycle > 10.24s in later meeting.
Paul (Ericsson) provides comments, Ericsson also supports the working assumptions as proposed by Guillaume (MediaTek).
Guillaume (MediaTek) clarifies the proposed working assumption is for Rel-17.
Dieter (Deutsche Telekom): yes, of course for Rel-17, thank you Guillaume! We also agree that with this assumption there is no urgency to agree CRs at this meeting.
Hannu (Nokia) still supports the proposal from Guillaume, but asks why the first steps can't be agreed already in this meeting where we have the CRs available?
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Miguel (Qualcomm) objects to this CR.
Aihua (China Mobile) suggests to include extending eDRX cycles to beyond 10.24s as the package of the R17 WID.
Noted
4.1 S2-2104329 DISCUSSION Discussion Discussion on architecture impact for REDCAP. China Mobile Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2104358 DISCUSSION Agreement Discussion on long eDRX value system impact to support RedCap. Ericsson Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 - - - Asynchronous Type Communication - - Docs:=8 -
4.1 S2-2103765 LS In Action LS from CT WG4: LS on Support of Asynchronous Type Communication in N1N2MessageTransfer CT WG4 (C4-212401) Rel-17 Response drafted in S2-2103895. Postponed Postponed
4.1 S2-2103895 LS OUT Approval [DRAFT] Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer Ericsson Rel-17 Response to S2-2103765. Postponed Chunshan (Tencent) provides r01.
Haiyang (Huawei) share similar view with Chunshan (Tencent) and provides r02.
Qian (Ericsson) comments and points out that we shall have a way forward to guide the stage 3 design.
Haiyang (Huawei) comments.
Qian (Ericsson) responses to Haiyang (Huawei).
Hannu (Nokia) supports the original version of 3895 but can't agree with the revisions that are not aligned with the reasoning given to justify these updates.
Haiyang (Huawei) replies.
Hannu (Nokia) asks for the corresponding CRs related with the proposed interpretation (2)?
Qian (Ericsson) provides further comments and indicating there seems still no use case identified.
Hannu (Nokia) supports Qian (Ericsson) and proposes to go for ATC removal unless a valid use case can be shown.
Jicheol (Samsung) share the view with Nokia and Ericsson.
Qian (Ericsson) responds.
Haiyang (Huawei) provides comments.
Qian (Ericsson) gives further comments.
Haiyang (Huawei) provides response.
Qian (Ericsson) replies.
Chunshan (Tencent) replies.
Hannu (Nokia) answers to Haiyang (Huawei).
Hannu (Nokia) replies to Chunshan (Tencent).
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Haiyang (Huawei) replies and cannot accept the original version.
Qian (Ericsson) comments and suggests this to be discussion in CC#2.
Hannu (Nokia) supports the proposal to bring this to CC#2.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
4.1 S2-2103896 CR Approval 23.501 CR2866 (Rel-15, 'F'): Removal of ATC Ericsson Rel-15 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2103897 CR Approval 23.501 CR2867 (Rel-16, 'A'): Removal of ATC Ericsson Rel-16 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
Hannu (Nokia) warns that noting this CR leaves the whole decision open in this meeting as this is the only practical solution we have got.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2103898 CR Approval 23.501 CR2868 (Rel-17, 'A'): Removal of ATC Ericsson Rel-17 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
Hannu (Nokia) warns that noting this CR leaves the whole decision open in this meeting as this is the only practical solution we have got.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2103899 CR Approval 23.502 CR2746 (Rel-15, 'F'): Removal of ATC Ericsson Rel-15 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
Qian (Ericsson) provides r01.
Hannu (Nokia) supports r01.
Chunshan (Tencent) provides clarification and objects r01.
Qian (Ericsson) provides comments.
Hannu (Nokia) challenges the comment that valid ATC use cases would exist.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2103900 CR Approval 23.502 CR2747 (Rel-16, 'A'): Removal of ATC Ericsson Rel-16 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 S2-2103901 CR Approval 23.502 CR2748 (Rel-17, 'A'): Removal of ATC Ericsson Rel-17 CC#2: Noted Haiyang (Huawei) suggests to note this CR.
Chunshan (Tencent) suggests to note this CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 - - - MINT - - Docs:=4 -
4.1 S2-2103748 LS In Action LS from CT WG1: LS on the conclusion of FS_MINT-CT CT WG1 (C1-212598) Rel-17 Response drafted in S2-2104043. Final response in S2-2104994 Replied to
4.1 S2-2104043 LS OUT Approval [DRAFT] Reply LS on the conclusion of FS_MINT-CT LG Electronics Rel-17 Response to S2-2103748. CC#2: r02, moving TSG SA from the CC: list to the TO: list agreed. Revised to S2-2104994. Qian Chen (Ericsson) provides comments and considers it's better to send the Reply LS in later SA2 meeting
Hyunsook (LGE) suggests to provide the potential SA2 plan to CT1 and SA, because Rel17 stage 2 freezing target is June, 2021.
Alessio(Nokia) supports Ericsson, we should postpone the LS.
Haris(Qualcomm) comments
Fenqin (Huawei) comments
Hyunsook (LGE) has comments and provides r01.
Jinguo(ZTE) suggest to postpone this LS
For the smooth progress in CT1 and SA, Hyunsook(LGE) suggests to send the simple reply (such as r01 without SA2 analysis)
Dieter (Deutsche Telekom): proposes to postpone this LS
Qian (Ericsson): comments and provide r02
alessio(Nokia) is ok with r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Jinguo(ZTE) comments that r02 the action is still to CT1, not to SA, further update is needed.
LG Uplus agrees with LGE.
Hyunsook (LGE) is ok with r02, and proposes to change the action target to 'CT1 and SA' based on Jinguo's comment.
Hoyeon (Samsung) supports to approve r02 with the changes suggestied by Hyunsook (LGE).
Jinguo(ZTE) is ok with r02 plus the changes suggestied by Hyunsook (LGE). suggest for CC#2.
Dieter (Deutsche Telekom): would be ok with r02 + proposed change for action.
Qian (Ericsson) is ok with r02 + proposed changes.
Andy (VC, Samsung): The after-deadline changes look necessary so I have added this for CC#2.
Hyunsook (LGE) put the last revision (S2-2104043r02+after deadline) into CC#2 folder.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
4.1 S2-2104994 LS OUT Approval Reply LS on the conclusion of FS_MINT-CT SA WG2 Rel-17 Revision of S2-2104043r02 + changes. Approved Approved
4.1 S2-2104046 DISCUSSION Discussion SA WG2 specification impact on FS_MINT-CT . LG Electronics, KT Corp., LG Uplus, SK Telecom Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
4.1 - - - Other - - Docs:=1 -
4.1 S2-2104617 CR Approval 23.502 CR2848 (Rel-17, 'B'): Updates of Processing AF requests to influence AM policies procedure China Mobile Rel-17 Confirm Spec version used - CR states 17.1.0! Not Handled -
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:=14 -
6.1 S2-2103991 CR Approval 23.501 CR2874 (Rel-17, 'F'): Correction to the reference document for charging related reference points Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2104795. Stefan (Ericsson) comments
Laurent (Nokia): provides r01
Gerald (Matrixx) support r01 as cosigner and with comment
Mirko (Huawei) provides r02.
Gerald (Matrixx) improved the collection on RP based on the approval in SA5 in r03.
Dieter (Deutsche Telekom): comments r03.
Gerald (Matrixx) provides r04 as suggested.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Mirko (Huawei) comments and suggests to move forward with r02.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2104795 CR Approval 23.501 CR2874R1 (Rel-17, 'F'): Correction to the reference document for charging related reference points Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103991r02. Approved Agreed
6.1 S2-2104138 DISCUSSION Discussion Discussion on determination of Registration Area. Huawei, HiSilicon Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2104139 CR Approval 23.501 CR2898 (Rel-17, 'F'): Correction on determination of Registration Area Huawei, HiSilicon Rel-17 Noted Alessio(Nokia) thinks this CR is not needed. propose to note it but to study the related issue in rel-18
Chris (Vodafone) thinks this CR is useful and provides r01.
Jinguo(ZTE) agree with Alessio(Nokia)
Malla (NTT DOCOMO) agrees with Alessio(Nokia) and CR is not needed, propose to note.
Haris(Qualcomm) comments on r01
Hoyeon (Samsung) suggest to note the CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Haiyang (Huawei) prefers to state the non-UE-impact solution in R17, and study the others in R18. So r01 is ok for us.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2104433 CR Approval 23.501 CR2779R1 (Rel-15, 'F'): Correct NOTE 1 for N6 China Mobile Rel-15 Revision of (unhandled) S2-2102543. CC#2: Noted Mirko (Huawei) comments and provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): objects to r01 , provides a r02 post deadline
Dan(China Mobile): OK for r01, and r02, and request this for CC#2
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2104444 CR Approval 23.501 CR2782R1 (Rel-16, 'F'): (Mirror)Correct the NOTE for N6 China Mobile Rel-16 Revision of (Unhandled) S2-2102551. Is this a mirror CR? Not Cat A, where is base CR? CC#2: Noted Mirko (Huawei) comments and provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.1 S2-2104454 CR Approval 23.501 CR2783R1 (Rel-17, 'F'): (Mirror)Correct the NOTE for N6 China Mobile Rel-17 Revision of (Unhandled) S2-2102552. Confirm Spec version used - CR states 17.1.0! CC#2: r02 + Changes agreed. Revised to S2-2104995. Mirko (Huawei) comments and provides r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Dan(China Mobile) provides r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2104995 CR Approval 23.501 CR2783R2 (Rel-17, 'F'): (Mirror)Correct the NOTE for N6 China Mobile Rel-17 Revision of S2-2104454r02 + Changes. Approved Agreed
6.1 S2-2104562 CR Approval 23.501 CR2945 (Rel-17, 'F'): Clarification on the number of Subscribed S-NSSAIs Nokia, Nokia Shanghai Bell, Samsung Rel-17 r03 agreed. Revised to S2-2104796. Peter Hedman (Ericsson) provides questions.
Alessio(Nokia) responds
Hoyeon (Samsung) responds
Jinguo(ZTE) comments
Peter Hedman (Ericsson) provides reply
alessio(Nokia) replies
alessio(Nokia) replies.
Patrice (Huawei) supports Ericsson's proposal to do the limitation at what the UDM sends. r00 is therefore not agreeable.
Peter Hedman (Ericsson) provides r01
Alessio(Nokia) Can live with r01.
Hoyeon (Samsung) can live with r01.
Patrice (Huawei) supports the changes in r01 from Ericsson, updates the cover sheet and cosigns in r02.
Alessio(Nokia) provides r03 which tidies up the coversheet
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Hoyeon (Samsung) is OK with r03.
Peter Hedman (Ericsson) provides comments while ok with r03
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2104796 CR Approval 23.501 CR2945R1 (Rel-17, 'F'): Clarification on the number of Subscribed S-NSSAIs Nokia, Nokia Shanghai Bell, Samsung Rel-17 Revision of S2-2104562r03. Approved Agreed
6.1 S2-2104610 CR Approval 23.501 CR2953 (Rel-17, 'F'): Clarification on the Standardized SST values Nokia, Nokia Shanghai Bell, Qualcomm Inc. Rel-17 r05 agreed. Revised to S2-2104797. Hoyeon (Samsung) asks a question for clarification
Peter Hedman (Ericsson) provides r01
Alessio(Nokia) provides r02 just adding Samsung as supporting company
Patrice (Huawei) provides r03, turning the note to informative, based on the outcome in SA plenary. The analysis and endorsement of performance requirements is within the scope of SA1, not SA2. Question also: can AI#6.x be used for Rel-17 maintenance work in this meeting?
Alessio(Nokia) is aware of no SA outcome on this subject. R03 is not the right way to proceed
Haris(Qualcomm) comments on r03
Patrice (Huawei) clarifies his objection to r00-r02, and any revision which adds a normative reference to NG.116 regarding the SST values.
Tricci (OPPO) asks for clarification from Huawei
alessio(Nokia) can only work with a normative approach to Standardized SST values. informative is not enough.
Dieter (Deutsche Telekom): provides r04.
Patrice (Huawei) answers Tricci (Oppo).
Patrice (Huawei) can only work with an informative reference to NG.116 regarding performance requirements for standardised SST values. Normative is too much.
Alessio(Nokia) responds
Dieter (Deutsche Telekom): comments.
Peter Hedman (Ericsson) provides r05
Alessio(Nokia) provides r06
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r06 or r05
Patrice (Huawei) is OK with r03, r05, and objects r00, r01, r02, r04, r06.
Haris(Qualcomm) indicates preference to r06, and r02, r0 also ok
Haris(Qualcomm) corrects typo: Haris(Qualcomm) indicates preference to r06, and r03, r0 also ok
alessio(Nokia) of course we stand for r06 and the normative approach. if we have to go non normative then r03 is a more agreeable text but we need to discuss then how to have normative SSTs (as standardized SST values needs a commonly understood NEST to map to normatively.)
Dieter (Deutsche Telekom): suggest to go with r05.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.1 S2-2104797 CR Approval 23.501 CR2953R1 (Rel-17, 'F'): Clarification on the Standardized SST values Nokia, Nokia Shanghai Bell, Qualcomm Inc. Rel-17 Revision of S2-2104610r05. Approved Agreed
6.1 S2-2104766 CR Approval 23.501 CR2987 (Rel-17, 'F'): Correction of 5G System architecture missing CHF for charging services Matrixx Rel-17 Merged into S2-2105129 Stefan (Ericsson) has concerns with this CR and proposes to note it (see comments in email)
Gerald (Matrixx) with clarification to support the addition of CHF
Dan (China Mobile) concern with this paper and ask whether there is criteria for updating the SBA architecture in TS 23.501
Josep (DT) comments, proposes to merge with S2-2103799.
Hoyeon (Samsung) shares the concerns from Stefan (Ericsson) and Dan (China Mobile), and proposes to note the CR.
Gerald (Matrixx) is supporting the DT proposal to merge and with generic clarification.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Gerald (Matrixx) proposes to set the status as merged into S2-2103799
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
6.1 S2-2104767 CR Approval 23.501 CR2988 (Rel-17, 'F'): Correction on Charging services Matrixx Rel-17 Noted Stefan (Ericsson) provides r01
Hoyeon (Samsung) provides r02 and asks if the CHF is only option for 5G charging.
Gerald (Matrixx) objects r02 and provides an improved r03 based on r01.
Antoine (Orange) comments on 'Support of CHF services' in r03.
Stefan (Ericsson) agrees with Antoine and prefers r01 or r02.
Hoyeon (Samsung) agrees with Antoine (Orange) and Stefan (Ericsson), and provides comments.
Gerald (Matrixx) provides r04 to remove the concerns.
Hoyeon (Samsung) is OK with r04.
Dieter (Deutsche Telekom): comments.
Antoine (Orange) is fine with r04 and with the wording improvements proposed by Dieter.
Gerald (Matrixx) provides r05 for final view.
Mirko (Huawei) asks for a clean-up and additional changes.
Gerald (Matrixx) provides r06 as requested.
Mirko (Huawei) comments and provides r07.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): objects to any version but R07: the RAN box shall not be ticked.
Gerald (Matrixx) the re-addition in r07 makes the objective of the CR waste, strong object to r07 and recommend to go with r06.
Mirko (Huawei) suggests to move forward with r07.
Gerald (Matrixx) encouraged to go with r06.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.2 - - - Common Access Control, RM and CM functions and procedure flows - - Docs:=7 -
6.2 S2-2103893 CR Approval 23.502 CR2744 (Rel-16, 'F'): Group event clarification and event transfer between AMFs Ericsson Rel-16 CC#2: r03 + changes agreed. Revised to S2-2104996. Steve (Huawei) provides r01.
Jinguo(ZTE) provides comment
Qian (Ericsson) responds to Jinguo (ZTE).
Hannu (Nokia) provides r02 proposing an answer to Jinguo's question and co-signs.
Steve (Huawei) comments
Hannu (Nokia) agrees with the interpretation from Steve (Huawei) and answers.
Jinguo(ZTE) has no further comments.
Qian (Ericsson) comments and provide r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Hannu (Nokia) still prefers r02 but admits it's not perfect.
Qian (Ericsson) comments and proposes a way forward based on r03, and also requests to include the proposal in CC #2.
Steve (Huawei) It seems we have a simple change to make, let's go to CC#2 get it done.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2104996 CR Approval 23.502 CR2744R1 (Rel-16, 'F'): Group event clarification and event transfer between AMFs Ericsson Rel-16 Revision of S2-2103893r03 + changes. Approved Agreed
6.2 S2-2103894 CR Approval 23.502 CR2745 (Rel-17, 'A'): Group event clarification and event transfer between AMFs Ericsson Rel-17 Confirm CR Number - CR states 2945! CC#2: r01 + changes agreed. Revised to S2-2104997. Steve (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Steve (Huawei) there is a simple change being suggested for 3893 (which this is a mirror of) which looks like it needs CC#2. We should wait for that and then ensure this mirror has the same final treatment.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.2 S2-2104997 CR Approval 23.502 CR2745R1 (Rel-17, 'A'): Group event clarification and event transfer between AMFs Ericsson Rel-17 Revision of S2-2103894r01 + changes. Approved Agreed
6.2 S2-2104731 DISCUSSION Endorsement On allowing UE Radio Capability change in CM-CONNECTED mode. Apple Rel-17 Noted Fenqin (Huawei) comment and suggest to postpone this paper
Qian Chen (Ericsson) agrees with Fenqin (Huawei)
Fei (OPPO) comments
Haris(Qualcomm) comments that this change cannot start from SA2
Genadi (Lenovo) agrees with previous comments (Fenqin (Huawei) and Haris (Qualcomm)) and provides additional comments.
Hannu (Nokia) proposes that SA2 is not the right place to start this work.
Krisztian (Apple) responds to comments.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.2 S2-2104750 CR Approval 23.501 CR2985 (Rel-16, 'F'): Avoiding RAT-specific TAI list considering RRC Inactive state Apple Rel-16 Noted Fenqin (Huawei) comment
Qian Chen (Ericsson) comments
Fei (OPPO) asks for clarification.
Haris(Qualcomm) proposes to note
Hannu (Nokia) agrees with the previous speakers and shares especially Fenqin's concern that the AMF need not be aware of RRC-Inactive state.
Krisztian (Apple) responds to comments.
Antoine (Orange) comments that this CR makes no sense.
Krisztian (Apple) responds to Antoine (Orange).
Fenqin (Huawei) comments.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Hannu (Nokia) objects to the principle that the AMF would need to be aware of RRC Inactive.
Antoine (Orange) objects the CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.2 S2-2104751 CR Approval 23.501 CR2986 (Rel-17, 'A'): Avoiding RAT-specific TAI list considering RRC Inactive state Apple Rel-17 Noted Antoine (Orange) comments that this CR should suffer the same fate as S2-2104750.
Krisztian (Apple) responds to Antoine (Orange).
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.3 - - - Session management and continuity functions and flows - - Docs:=7 -
6.3 S2-2103764 LS In Action LS from CT WG3: Reply LS on the support of L2TP with CUPS CT WG3 (C3-212569) Rel-17 Noted Laurent (Nokia): proposes to Note the Ls as there is no real action for us (the actual technical discussion is between CT3 and CT4)
Stefan (Ericsson) agrees to NOTE
Noted
6.3 S2-2104707 CR Approval 23.501 CR2973 (Rel-17, 'B'): L2TP information provision China Telecom Rel-17 r04 agreed. Revised to S2-2104798. Laurent (Nokia): asks a question
Heng (China Telecom) provide clarification.
Heng (China Telecom) provide r01.
Stefan (Ericsson) provides r02
Laurent (Nokia): provides r03
Josep (DT) provides r04 with co-sign.
Runze (Huawei) supports r04.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.3 S2-2104798 CR Approval 23.501 CR2973R1 (Rel-17, 'B'): L2TP information provision China Telecom Rel-17 Revision of S2-2104707r04. Approved Agreed
6.3 S2-2103766 LS In Action LS from CT WG4: LS on UPF support for multiple network slices CT WG4 (C4-212560) Rel-17 Responses drafted in S2-2103873 and S2-2104157. Postponed Postponed
6.3 S2-2103873 LS OUT Approval [DRAFT] Reply LS on UPF support for multiple network slices Ericsson Rel-17 Response to S2-2103766. Postponed Josep (DT) proposes to merge with S2-2104157 and continue the discussion there.
Runze (Huawei) agrees with DT and suggests to use S2-2104757 as discussion baseline.
Laurent (Nokia): agrees with DT and suggests to use S2-2104757 as discussion baseline.
Yifan (China Telecom) agrees with DT and suggests to use S2-2104157 as discussion baseline.
Jinguo (ZTE) agrees with DT and suggests to use S2-2104157 as discussion baseline.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): objects to any version of the LS (goal is to postpone the topic and have a proper spec in august)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.3 S2-2104157 LS OUT Approval [DRAFT] Reply LS on UPF support for multiple network slices China Telecommunications Rel-17 Response to S2-2103766. Postponed Stefan (Ericsson) cannot accept r00, provides comments and r01
Josep (DT) asks for further clarification.
Stefan (Ericsson) replies
Yifan (China Telecom) cannot accept r01, provides comments.
Runze (Huawei) responds to Stefan.
Yifan (China Telecom) provides r02.
Stefan (Ericsson) asks what the benefit of solution 2 is
Dieter (Deutsche Telekom): asks basic question.
Runze (Huawei) responds to Stefan (Ericsson).
Jinguo(ZTE) response .
Yifan (China Telecom) responds to Stefan.
Dieter (Deutsche Telekom): continues with basic question.
Jinguo(ZTE) response to Dieter (Deutsche Telekom)
Josep (DT) proposes a re-think and a way forward by not choosing any solution.
Laurent (Nokia): Comments and asks to postpone the topic
Josep (DT) supports Nokia's proposal to postpone.
Stefan (Ericsson) replies to Jinguo
Jinguo(ZTE) replies to Stefan (Ericsson)
Antoine (Orange) also supports Nokia's proposal to postpone.
Dieter (Deutsche Telekom): supports to postpone this LS.
Yifan (China Telecom) responds.
Runze (Huawei) suggests to progress in this meeting.
Laurent (Nokia): answers
Stefan (Ericsson) replies to Runze
Runze (Huawei) replies to Laurent (Nokia)
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Runze (Huawei) replies to Stefan (Ericsson).
Jinguo(ZTE) suggests to go with r02
Yifan (China Telecom) agrees with ZTE and suggests to go with r02.
Runze (Huawei) suggests to approve r02.
Laurent (Nokia): objects to any version of the LS (goal is to postpone the topic and have a proper spec in august)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.3 S2-2103872 DISCUSSION Agreement Analysis of CT WG4's options to support multiple slices in UPF . Ericsson Noted Josep (DT) proposes to note this discussion paper.
Stefan (Ericsson) replies to Josep
Josep (DT) answers to Stefan (Ericsson), provides further clarification.
Stefan (Ericsson) answers Josep
Yifan (China Telecom) agrees with DT and provides comments.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.4 - - - Security related functions and flows - - Docs:=4 -
6.4 S2-2104468 CR Approval 23.501 CR2929 (Rel-16, 'F'): Support for UPIP for other than NR Qualcomm,.. Rel-16 r04 agreed. Revised to S2-2104799. Wanqiang(Huawei) comment.
Stefan (Ericsson) provides questions
Haris(Qualcomm) comments inline
Stefan (Ericsson) provides replies
Haris(Qualcomm) responds
Laurent (Nokia): Comments
Josep (DT) comments.
Stefan (Ericsson) provides r01
Chris (Vodafone) comments and provides rev 2.
Chris (Vodafone) replies
Haris(Qualcomm) proposes r03
Chris (Vodafone) thinks that r03 is probably OK.
Antoine (Orange) provides r04.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): prefers R04 then R03 Then R02
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.4 S2-2104799 CR Approval 23.501 CR2929R1 (Rel-16, 'F'): Support for UPIP for other than NR Qualcomm,.. Rel-16 Revision of S2-2104468r04. Approved Agreed
6.4 S2-2104485 CR Approval 23.501 CR2931 (Rel-17, 'A'): Support for UPIP for other than NR Qualcomm,.. Rel-17 r00 agreed. Revised to S2-2104800.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.4 S2-2104800 CR Approval 23.501 CR2931R1 (Rel-17, 'A'): Support for UPIP for other than NR Qualcomm,.. Rel-17 Revision of S2-2104485. Approved Agreed
6.5 - - - QoS concept and functionality - - Docs:=0 -
6.6 - - - Policy and charging control - - Docs:=14 -
6.6 S2-2103809 CR Approval 23.503 CR0570 (Rel-15, 'F'): Application Identifier in the PCC Rule Ericsson Rel-15 r01 agreed. Revised to S2-2104801 Pallab (Nokia) asks for clarification
Belen (Ericsson) replies to Nokia
Pallab (Nokia) replies to Belen (Ericsson)
Haiyang (Huawei) suggests to only go with R17 CR this meeting to avoid misalignment of the terms
Belen (Ericsson) provides r01
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Pallab (Nokia) is OK with r01
Belen (Ericsson) proposes to approve r01 and then S2-2103810 and S2-2103811 as mirrors
Haiyang (Huawei) is ok with what Belen (Ericsson) proposed ( to approve r01 and then S2-2103810 and S2-2103811 as mirrors)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104801 CR Approval 23.503 CR0570R1 (Rel-15, 'F'): Application Identifier in the PCC Rule Ericsson Rel-15 Revision of S2-2103809r01. Approved Agreed
6.6 S2-2103810 CR Approval 23.503 CR0571 (Rel-16, 'A'): Application Identifier in the PCC Rule Ericsson Rel-16 r00 agreed. Revised to S2-2104802. Haiyang (Huawei) suggests to only go with R17 CR this meeting
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104802 CR Approval 23.503 CR0571R1 (Rel-16, 'A'): Application Identifier in the PCC Rule Ericsson Rel-16 Revision of S2-2103810. Approved Agreed
6.6 S2-2103811 CR Approval 23.503 CR0572 (Rel-17, 'A'): Application Identifier in the PCC Rule Ericsson Rel-17 r00 agreed. Revised to S2-2104803. Haiyang (Huawei) provides r01
Pallab (Nokia) responds to Haiyang (Huawei) and points out that revision has been provided on a mirror CR
Haiyang (Huawei) replies
Belen (Ericsson) replies that the proposed changes applies since Rel-15
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104803 CR Approval 23.503 CR0572R1 (Rel-17, 'A'): Application Identifier in the PCC Rule Ericsson Rel-17 Revision of S2-2103811. Approved Agreed
6.6 S2-2104136 CR Approval 23.502 CR2776 (Rel-17, 'F'): Clean-up for AF related identifier Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104804. Belen (Ericsson) provides r01 and objects to initial version.
Haiyang (Huawei) provides response and questions.
Belen (Ericsson) replies to Haiyang
Pallab (Nokia) provides r02
Haiyang (Huawei) provides r03.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Pallab (Nokia) OK with r03.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104804 CR Approval 23.502 CR2776R1 (Rel-17, 'F'): Clean-up for AF related identifier Huawei, HiSilicon Rel-17 Revision of S2-2104136r03. Approved Agreed
6.6 S2-2104137 CR Approval 23.503 CR0586 (Rel-17, 'F'): Clean-up for AF related identifier Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104805. Belen (Ericsson) objects to initial version and provides r01
Haiyang (Huawei) is ok with r01 and provides r02 as a merger with 3811 just in case
Belen (Ericsson) objects to r02
Belen (Ericsson) provides r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104805 CR Approval 23.503 CR0586R1 (Rel-17, 'F'): Clean-up for AF related identifier Huawei, HiSilicon Rel-17 Revision of S2-2104137r03. Approved Agreed
6.6 S2-2104576 CR Approval 23.503 CR0596 (Rel-17, 'F'): Clarification on handling of URSP Traffic Descriptor Component 'Domain Descriptors' Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2104806. Belen (Ericsson) provides a revision.
Guillaume (MediaTek) provides r02.
Alessio(Nokia) can live with r01. asks questions about r02
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Farooq (AT&T) prefers r02
Hoyeon (Samsung) provides comments, and should be OK with r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104806 CR Approval 23.503 CR0596R1 (Rel-17, 'F'): Clarification on handling of URSP Traffic Descriptor Component 'Domain Descriptors' Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104576r01. Approved Agreed
6.6 S2-2104620 CR Approval 23.503 CR0600 (Rel-17, 'F'): Clarification on association of applications to PDU sessions Nokia, Nokia Shanghai Bell, Apple Rel-17 CC#2: r01 + changes agreed. Revised to S2-2104998. Belen (Ericsson) provides comments.
alessio(Nokia) responds
Belen (Ericsson) asks questions on the CR.
Alessio(Nokia) replies
Belen (Ericsson) sends a response
Alessio(Nokia) Our intent is precisely to clarify this support of multiple PDU sessions per APP is supported as there is no way this can be stopped in the UE and in the network.
Krisztian (Apple) comments and provides r01.
Haiyang (Huawei) provides comments.
Dimitris (Lenovo) provides comments and r02
Hoyeon (Samsung) provides comments.
Haiyang (Huawei) cannot accept revisions with 'traffic' and provides r03.
Jinguo(ZTE) comments
Haiyang (Huawei) replies.
Belen (Ericsson) provides r05, is okay with r04 and objects to previous revisions (and initial version)
Belen (Ericsson) provides r04, is okay with r03 and objects to previous revisions (and initial version)
alessio(Nokia) provides response
Alessio(nokia) provides r05 that treasures from the work done by Kriztian Kiss (apple) and the further comments by Dimitrios
Belen (Ericsson) objects to r06.
Belen (Ericsson) objects to r05 (there is no r06 at this point in time)
Alessio(Nokia) asks whether then Ericsson thinks that the changes by Kriztian are really wrong....
Susana (Vodafone) objects to r05, and all revisions except r04.
Farooq(AT&T) agrees with Vodafone. r04 seems to be the only acceptable version.
Alessio(Nokia) provides r07 and will not accept r03,r04
Hong (Qualcomm) provides r08.
Alessio(Nokia) cannot accept r08 as it is de facto not clarifying the simultaneous association to multiple PDU sessions is possible.
Belen (Ericsson) is okay with r08 and objects to r07
Alessio(Nokia) asks the reason for objection to r07 as this is saying what r04 says but normatively.
Belen (Ericsson) replies to Nokia-
Guillaume (MediaTek): the spec is fine as is. No CR needed.
alessio(Nokia) thinks a CR is needed
Haiyang (Huawei) provides r09.
Belen (Ericsson) still prefers r08.
Alessio(Nokia) provides r11
Yang(OPPO) thinks r08 is the most suitable version and propose to agree r08
alessio(Nokia) complains that r08 is low quality text and provides r12 but still prefers r11 .
Hong (Qualcomm) comments on r12.
Hong (Qualcomm) provides r15 that replaces r12. still prefers r11 but can live with r15
Alessio(Nokia) submits r16 also for consideration
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Krisztian (Apple) suggests to move forward with r15.
Hoyeon (Samsung) would prefer an approach having an NOTE as proposed in r08 or r15.
Dieter (Deutsche Telekom): wording in both r08 and r15 can be improved.
Alessio(Nokia) we are ok also with R15 but we may want to take a good look at the normative text collectively and see if it ingenerates confusion (it seems there is given the varied views we had this week) and if so fix them in the future.
alessio(Nokia) comments r15 is ok as is
Dieter (Deutsche Telekom) comments
Haiyang (Huawei): R11 is not OK. R15 is generally fine.
Belen (Ericsson) also thinks that 'handle' is too open, so either DT or Huawei proposal are better option on top of rel 15. R08 is okay.
Alessio(nokia) objects to r08 and can only accept r15
Hong (Qualcomm) suggests to go with either r08 or the Huawei proposal on top of r15.
Dieter (Deutsche Telekom): We prefer HW proposed change on top of r015.
Belen (Ericsson) shares DT view: We prefer HW proposed change on top of r015.
Farooq (AT&T) comments - R15 with suggested addition also OK for me.
Dimitris (Lenovo) is OK with going with R15 with the HW addition
Guillaume (MediaTek): same view as expressed below. R15+Huawei's addition is ok.
alessio (nokia) OK with R15+Huawei's addition is ok.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.6 S2-2104998 CR Approval 23.503 CR0600R1 (Rel-17, 'F'): Clarification on association of applications to PDU sessions Nokia, Nokia Shanghai Bell, Apple Rel-17 Revision of S2-2104620r01 + changes. Approved Agreed
6.7 - - - 3GPP access specific functionality and flows - - Docs:=5 -
6.7 S2-2103890 CR Approval 23.501 CR2863 (Rel-15, 'F'): UE radio capability clarification Ericsson Rel-15 Noted Wanqiang(Huawei) comment that the change on R15 is not necessary.
Qian (Ericsson) provides comments.
Wanqiang (Huawei) provides comments and only ok with R17 as clarification.
Hannu (Nokia) proposes r01 for possible compromise.
Haris(Qualcomm) ok with either r0 or r1 but this text in consequences if not approved of r1 needs to be modified as proposed here: 'If the AMF implementation does not delete the old UE radio capability and replace it by new UE radio capability during UE re-registration for UE radio capability update, it leads to mismatch of UE radio capabilities between the UE and **RAN**
Hannu (Nokia) revises to r02 following a comment from Haris(Qualcomm)
Qian (Ericsson) provides comments and r03
Wanqiang (Huawei) replies and proposes to go with R16 and R17 (No R15).
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Wanqiang (Huawei) proposes to note R15 CR.
Hannu (Nokia) supports the proposal from Wanqiang (Huawei) to note R15 CR and shares r04 to document a proposal to update Rel-16 and Rel-17 cover page to say 'This CR is technically compatible with Rel-15'.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.7 S2-2103891 CR Approval 23.501 CR2864 (Rel-16, 'A'): UE radio capability clarification Ericsson Rel-16 CC#2: r01 + changes agreed. Revised to S2-2104999. Wanqiang (Huawei) provides comments and only ok with R17 as clarification.
Qian (Ericsson) responds to Wanqiang (Huawei).
Wanqiang (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Chris (Vodafone) says check that this is a real mirror CR
Qian (Ericsson) is ok with r01
Hannu (Nokia) proposes to use the agreed text from the latest revision of S2-2103890 and to add on cover page the text 'This CR is technically compatible with Rel-15'
Hannu (Nokia) updates the document reference in his previous comment and proposes the latest revision of S2-2103891 with cover page text 'This CR is technically compatible with Rel-15'
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.7 S2-2104999 CR Approval 23.501 CR2864R1 (Rel-16, 'A'): UE radio capability clarification Ericsson Rel-16 Revision of S2-2103891r01 + changes. Approved Agreed
6.7 S2-2103892 CR Approval 23.501 CR2865 (Rel-17, 'A'): UE radio capability clarification Ericsson Rel-17 CC#2: r01 + changes agreed. Revised to S2-2105000. Wanqiang (Huawei) provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.7 S2-2105000 CR Approval 23.501 CR2865R1 (Rel-17, 'A'): UE radio capability clarification Ericsson Rel-17 Revision of S2-2103892r01 + changes. Approved Agreed
6.8 - - - Specific services support - - Docs:=16 -
6.8 S2-2104158 LS OUT Approval [DRAFT] LS on voice centric UE impact due to S1 mode disable China Telecommunications Rel-16 Noted George (Ericsson) proposed to note the LS. Please see 4214.
Leo (Deutsche Telekom) proposes to note the LS.
Haris (Qualcomm) object to sending LS to CT1
Jungshin (Samsung) supports to note the CR.
Heng (China Telecom) provide comment to Haris.
Haris(Qualcomm) comments
Thomas(Nokia) comments
Heng(China Telecom) provide r01
Ouyang(Huawei) replies to Haris(Qualcomm)
Thomas(Nokia) comments against r01
Ouyang(Huawei) replies to Thomas(Nokia) and provide r02
Haris(Qualcomm) comments that the text in LS makes incorrect assumptions
Heng(China Telecom) provide clarification
Heng(China Telecom) provide explain
Ouyang(Huawei) replies to Haris(Qualcomm) and provide r03
Haris(Qualcomm) comments that the proposal does not work
George(Ericsson) provides a comment. We have the same view. The core issue is LTE coverage. Nothing will work as long as this condition prevails. The LS adds no value. C1 can discuss the issue without any LS. The SA2 specs are correct.
Guillaume (MediaTek) agrees with the observation from Haris (Qualcomm).
Ouyang(Huawei) clarifies to Haris(Qualcomm) about their misunderstanding.
Heng(China Telecom) clarifies the LTE coverage issue.
Thomas(Nokia) comments on coverage issue.
Ouyang(Huawei) clarifies.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104214 CR Approval 23.501 CR2907 (Rel-16, 'B'): Accelerate IMS voice when S1 is disabled China Telecom, China Unicom, Huawei, HiSilicon, Rel-16 Noted George (Ericsson) proposes to note the CR. Please see additional comments.
Leo (Deutsche Telekom) also requests to note the CR.
Haris(Qualcomm) objects to the CR
Jungshin (Samsung) proposes to note the CR.
Ouyang(Huawei) seeks clarification from George (Ericsson).
Ouyang(Huawei) responses to Leo(DT)
Ouyang(Huawei) seeks clarification from Jungshin (Samsung).
Leo (Deutsche Telekom) responds to Ouyang(Huawei)
Thomas (Nokia) objects a Rel-17 change
Thomas (Nokia) correct himself and objects a Rel-16 change
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Leo (Deutsche Telekom) also objects this Rel-16 CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104451 CR Approval 23.502 CR2821 (Rel-16, 'B'): Accelerate IMS voice when S1 is disabled China Telecom, China Unicom, Huawei, HiSilicon, Rel-16 Noted George (Ericsson) proposes to note the CR. Please see 4214.
Leo (Deutsche Telekom) also proposes to note the CR.
Thomas (Nokia) also proposes to note the CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104484 CR Approval 23.501 CR2930 (Rel-17, 'A'): Accelerate IMS voice when S1 is disabled China Telecom, China Unicom, Huawei, HiSilicon, Rel-17 Noted George (Ericsson) proposes to note the CR. Please see comments on 4214
Leo (Deutsche Telekom) also proposes to note the CR and considers these changes as not needed.
Ouyang(Huawei) provides r01
Haris(Qualcomm) comments that the CR is still incomplete since it does not define what the UE does with this new indicator and see my response in the thread of S2-2104158 On why the proposal does not work considering the NAS details
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104580 CR Approval 23.502 CR2840 (Rel-17, 'A'): Accelerate IMS voice when S1 is disabled China Telecom, China Unicom, Huawei, HiSilicon, Rel-17 Noted George (Ericsson) proposes to note the CR. Please see 4214.
Leo (Deutsche Telekom) also proposes to note the CR.
Thomas (Nokia) comments.
Ouyang(Huawei) replies to Thomas (Nokia)
Ouyang(Huawei) seeks clarification from Leo(Deutsche Telekom)
Leo (Deutsche Telekom) provides answers to Ouyang(Huawei)
Thomas (Nokia) replies to Ouyang(Huawei)
Haris(Qualcomm) objects to the CR as is technically incomplete
Ouyang(Huawei) provides r01 , replies to Haris(Qualcomm) and Thomas (Nokia)
Haris(Qualcomm) see my response in the thread of S2-2104158 with my analysis on why the proposal does not work
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Antoine (Orange) questions the use case for a Rel-17 Cat B CR adressing a scenario without VoNR deployed.
Ouyang(Huawei) points out that Antoine (Orange)'s questions is invalid.
Heng (China Telecom) reply. Please ingore my last email with copy&past problem.
Antoine (Orange) replies to Ouyang and Heng.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Heng (China Telecom) reply to Antoine.
Noted
6.8 S2-2104372 DISCUSSION Agreement Recovery of IMS voice service after S1 mode is disabled Huawei, HiSilicon Rel-16 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104732 CR Approval 23.501 CR2979 (Rel-16, 'F'): AMF to consider S1 mode capability into account when setting EMF and EMC Apple Rel-16 r01 agreed. Revised to S2-2104807. George (Ericsson) provides a comment.
Hannu (Nokia) shares the concern of George (Ericsson) on normative text and asks a question.
Krisztian (Apple) responds to George (Ericsson).
Krisztian (Apple) responds to Hannu (Nokia).
George (Ericsson) OK with r01. .
Hannu (Nokia) repeats the question.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Leo (Deutsche Telekom) supports to approve r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2104807 CR Approval 23.501 CR2979R1 (Rel-16, 'F'): AMF to consider S1 mode capability into account when setting EMF and EMC Apple Rel-16 Revision of S2-2104732r01. Approved Agreed
6.8 S2-2104741 CR Approval 23.501 CR2982 (Rel-17, 'A'): AMF to consider S1 mode capability into account when setting EMF and EMC Apple Rel-17 r00 agreed. Revised to S2-2104808. George (Ericsson) provides comment.
Krisztian (Apple) responds to George (Ericsson).
Haris(Qualcomm) comments on the CR and asks question on the reason for change
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Krisztian (Apple) responds to Haris (Qualcomm).
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2104808 CR Approval 23.501 CR2982R1 (Rel-17, 'A'): AMF to consider S1 mode capability into account when setting EMF and EMC Apple Rel-17 Revision of S2-2104741. Approved Agreed
6.8 S2-2104378 CR Approval 23.502 CR2808 (Rel-16, 'F'): EPS fallback due to connection lost Huawei, HiSilicon Rel-16 Noted Haris(Qualcomm) proposes to note
Leo (Deutsche Telekom) provides comments.
Fenqin (Huawei) responds.
Haris(Qualcomm) comments
Fenqin (Huawei) responds and provides r01.
Leo (Deutsche Telekom) comments on r01.
Thomas (Nokia) comments against r01 and original.
Fenqin (Huawei) responds and provides r02
zhendong (ZTE) proviIsdes the comments.
Yang (OPPO) asks questions
Thomas(Nokia) comments that r02 does not address his concerns.
Yi (China Mobile) asks questions for clarification.
zhendong (ZTE) provides the comments.
Haris(Qualcomm) comments that the trigger for EPS/RAT fallback rejecting the entire PDU session is already documented in TS 23.502 also
Yang (OPPO) responds and further comments.
Fenqin (Huawei) provides r01
Fenqin (Huawei) provides r03
Thomas(Nokia) requests to note this CR
Thomas (Nokia) responds to Fenqin
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104379 CR Approval 23.502 CR2809 (Rel-17, 'A'): EPS fallback due to connection lost Huawei, HiSilicon Rel-17 Noted Haris(Qualcomm) proposes to note
Leo (Deutsche Telekom) provides comments.
Thomas (Nokia) provides comments.
Thomas (Nokia) correct his comments.
Fenqin (Huawei) responds.
Fenqin (Huawei) provides r01 and suggest the update from R17.
Thomas (Nokia) comments that this is not a CAT F CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.8 S2-2104551 CR Approval 23.167 CR0362 (Rel-16, 'F'): NG eCall domain selection corrections Qualcomm Rel-16 Confirm CR Number - CR states 0352! r01 agreed. Revised to S2-2104809. Ouyang(Huawei) has concerns on this CR.
Haris(Qualcomm) responds and explains why it is FASMO: If we do nothing in the situation of row 'A' the UE will have to perform eCall in CS in 2nd attempt but in rel.16 we introduced support for NG eCall over NR and there is already support for NG eCall over LTE (both for EPS and 5GS). This will possibly eliminate the probability for finding appropriate RAT (if e.g. there is no support for eCall in CS but there is in LTE)
Leo (Deutsche Telekom) supports the CR, also for Rel-16, and sees this as FASMO correction.
Chris (Vodafone) thinks that r01 is OK (and for Rel-16).
George (Ericsson) supports r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Antoine (Orange) supports r01 provided by Haris (Qualcomm) and confirms that this is FASMO.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2104809 CR Approval 23.167 CR0362R1 (Rel-16, 'F'): NG eCall domain selection corrections Qualcomm Rel-16 Revision of S2-2104551r01. Approved Agreed
6.8 S2-2104570 CR Approval 23.167 CR0364 (Rel-17, 'A'): NG eCall domain selection corrections Qualcomm Rel-17 r00 agreed. Revised to S2-2104810. Ouyang(Huawei) shows concerns on this CR.
Haris(Qualcomm) responds inline
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Antoine (Orange) Asks Ouyang why the UE behaviour should be different in Rel-16 and Rel-17.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.8 S2-2104810 CR Approval 23.167 CR0364R1 (Rel-17, 'A'): NG eCall domain selection corrections Qualcomm Rel-17 Revision of S2-2104570. Approved Agreed
6.9 - - - Interworking and Migration - - Docs:=20 -
6.9 S2-2103717 LS In Action LS from CT WG1: LS on interworking to 5GS with N26 due to UE’s N1 mode capability disabling/enabling CT WG1 (C1-207531) Revision of Postponed S2-2102085 from S2#144E. Response drafted in S2-2103992. Final response in S2-2105003 Replied to
6.9 S2-2104223 CR Approval 23.502 CR2465R3 (Rel-16, 'F'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-16 Revision of (Endorsed) S2-2103058. CC#2: r01 agreed. Revised to S2-2105004. Judy (Ericsson) provide r01 based on offline discussion.
Ouyang(Huawei) objects to this CR
Antoine (Orange) supports r01 and doesn't understand Huawei's objection.
Since we have technically endorsed this CR at SA2#143e, a working agreement needs to be made if the single objection is sustained.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Ouyang(Huawei) sustains our objection to r16 changes. The incoming LS is for R17, not r16. Not FASMO.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2105004 CR Approval 23.502 CR2465R4 (Rel-16, 'F'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-16 Revision of S2-2104223r01. Approved Agreed
6.9 S2-2104446 CR Approval 23.501 CR2814R2 (Rel-17, 'F'): The impact of UE N1 mode change in EPS ZTE, Nokia, NokiaShanghai Bell, Ericsson, Samsung Rel-17 Revision of (Endorsed) S2-2103060. Huawei agreed to withdraw their objection if their concern is recorded in the meeting report. r02 was then agreed. Revised to S2-2105001. Ouyang(Huawei) objects the original version of the CR and provide the r01.
zhendong (ZTE) object r01 and provides r02.
Ouyang(Huawei) objects r02
zhendong (ZTE) comments, how r01 works.
Ouyang(Huawei) responses to Zhendong(ZTE), point him to S2-2100131.
zhendong (ZTE) responds.
Laurent (Nokia):objects to r01
Laurent (Nokia): asks this topic to be (again) put to CC2 agenda
Antoine (Orange) supports r00.
Since we have technically endorsed this CR at SA2#143e, a working agreement needs to be made if the single objection is sustained.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====

Ouyang(Huawei):
To permit progress, Huawei will not sustain our objection but we don't agree with the contents of this CR..
We would like Maurice to record our objection in the meeting report as follows:
'Huawei objects to the contents of this CR as it breaks a basic principle by forcing the UE to handle 5G QoS related parameters when N1 mode is disabled.'.

==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2105001 CR Approval 23.501 CR2814R3 (Rel-17, 'F'): The impact of UE N1 mode change in EPS ZTE, Nokia, NokiaShanghai Bell, Ericsson, Samsung Rel-17 Revision of S2-2104446r02. Approved Agreed
6.9 S2-2104004 CR Approval 23.502 CR2603R3 (Rel-17, 'B'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of (Endorsed) S2-2103059. Huawei agreed to withdraw their objection if their concern is recorded in the meeting report. r01 was then agreed. Revised to S2-2105002, merging S2-2104532 Judy (Ericsson) provide r01, merging 4532 into 4004 per offline discussion.
Ouyang(Huawei) objects to this CR.
Laurent (Nokia): asks this topic to be (again) put to CC2 agenda
Antoine (Orange) supports r01 and doesn't understand Huawei's objection.
Since we have technically endorsed this CR at SA2#143e, a working agreement needs to be made if the single objection is sustained.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Ouyang(Huawei):
To permit progress, Huawei will not sustain our objection but we don't agree with the contents of this CR..
We would like Maurice to record our objection in the meeting report as follows:
'Huawei objects to the contents of this CR as it breaks a basic principle by forcing the UE to handle 5G QoS related parameters when N1 mode is disabled.'.
Antoine (Orange) asks Huawei to clarify whether they object or not.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2105002 CR Approval 23.502 CR2603R4 (Rel-17, 'B'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2104004r01, merging S2-2104532. Approved Agreed
6.9 S2-2103992 LS OUT Approval [DRAFT] LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2103717. CC#2: r04 + changes agreed. Revised to S2-2105003. Ouyang(Huawei) objects to the LS
Laurent (Nokia): asks this topic to be (again) put to CC2 agenda
Antoine (Orange) supports the LS and doesn't understand Huawei's objection.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Ouyang(Huawei) provide r01 in CC#2 draft folder.
Laurent (Nokia): provides r02 (an even slimmer version)
Ouyang(Huawei) see no reason to remove the description of the basic idea of this solution .
Provide r03 in CC#2 draft folder.
Laurent (Nokia): provides r04
Ouyang(Huawei) provide r05 in CC#2
Revised
6.9 S2-2105003 LS OUT Approval LS on interworking to 5GS with N26 due to UE's N1 mode capability disabling/enabling SA WG2 Rel-17 Revision of S2-2103992r04 + changes. Approved Approved
6.9 S2-2104532 CR Approval 23.502 CR2836 (Rel-17, 'C'): EPC interworking to support UE capability change Samsung Rel-17 Confirm Spec version used - CR states 17.1.0! Merged into S2-2105002 Judy (Ericsson) proposes to merge 4532 into 4004 per offline discussion.
Jungshin (Samsung) agrees to the proposal of merging 4532 to the revision of 4004.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Merged
6.9 S2-2104101 DISCUSSION Agreement Discussion on subscription data updates for EPS/5GS interworking. Samsung, AT&T, T-Mobile USA, KT Corp., LG Uplus Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2104078 CR Approval 23.501 CR2887 (Rel-16, 'F'): Subscription data updates for EPS/5GS interworking Samsung, AT&T, T-Mobile USA, KT Corp., LG Uplus Rel-16 r06 agreed. Revised to S2-2104811. Laurent (Nokia): provides r01
Hyunsook (LGE) provides comments.
Laurent (Nokia): answers
Fenqin (Huawei) provides comments.
DongYeon (Samsung) replies and provides r02.
DongYeon (Samsung) replies to Fenqin.
Qian Chen (Ericsson) comments.
zhendong (ZTE) prvodes the comments.
DongYeon (Samsung) replies to Qian (Ericsson), Zhendong (ZTE), and Fenqin (Huawei).
Fenqin (Huawei) provides comments and r03.
DongYeon (Samsung) replies and provides r04.
zhendong (ZTE) ask question for clarification.
Sebastian (Qualcomm) provides r05
Laurent (Nokia): provides r06
DongYeon (Samsung) replies.
zhendong (ZTE) provides the response.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Hyunsook (LGE) is o.k. with r06..
DongYeon (Samsung) is ok with r06 as Rel-16 CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2104811 CR Approval 23.501 CR2887R1 (Rel-16, 'F'): Subscription data updates for EPS/5GS interworking Samsung, AT&T, T-Mobile USA, KT Corp., LG Uplus Rel-16 Revision of S2-2104078r06. Approved Agreed
6.9 S2-2104079 CR Approval 23.501 CR2888 (Rel-17, 'A'): Subscription data updates for EPS/5GS interworking Samsung, AT&T, T-Mobile USA, KT Corp., LG Uplus Rel-17 r00 agreed. Revised to S2-2104812.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.9 S2-2104812 CR Approval 23.501 CR2888R1 (Rel-17, 'A'): Subscription data updates for EPS/5GS interworking Samsung, AT&T, T-Mobile USA, KT Corp., LG Uplus Rel-17 Revision of S2-2104079. Approved Agreed
6.9 S2-2103969 CR Approval 23.502 CR2755 (Rel-15, 'F'): Correction to EPS bearer ID transfer Ericsson Rel-15 Postponed Laurent (Nokia): provides r01
Judy (Ericsson) comments
Laurent (Nokia): provides r02
Judy (Ericsson) prefer r00
Fenqin (Huawei) propose to postpone this issue.
Laurent (Nokia): OK to postpone
Judy (Ericsson) responds to Fenqin (Huawei) and Laurent (Nokia) that the proposed change is aligned with stage 3 (29.502) and sees no reason to postpone.
zhendong (ZTE) provides the clarification .
Judy (Ericsson) responds to zhendong (ZTE) and provide r03 (based on r00) (r02 seems taken but I haven't seen it announced)
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Judy (Ericsson) corrects comment that r02 is actually announced.
zhendong (ZTE) provides the response.
Judy (Ericsson) responds to zhendong (ZTE).
Fenqin (Huawei) suggest to postpone this issue.
Judy (Ericsson) is OK to postpone
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.9 S2-2103943 CR Approval 23.502 CR2751 (Rel-16, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-16 Postponed
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.9 S2-2103944 CR Approval 23.502 CR2752 (Rel-17, 'A'): Correction to EPS bearer ID transfer Ericsson Rel-17 Postponed
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
6.9 S2-2104723 CR Approval 23.501 CR2978 (Rel-17, 'F'): Providing alternative S-NSSAI(s) to the UE in EPC to 5GC interworking Apple Rel-17 Noted Laurent (Nokia): questions the Cat 'F' and claims this should be a candidate TEI18 feature
Qian Chen (Ericsson) agrees with Nokia and proposes to note the paper
Jungshin (Samsung) concurs with Nokia and Ericsson, and propose to note the CR.
Sebastian (Qualcomm) objects to the CR for the same reasons as state by Nokia and Ericsson
zhendong (ZTE) proposes to note this CR.
Hyunsook (LGE) has comments.
Laurent (Nokia): objects to the CR for the reason already stated
Krisztian (Apple) responds to comments.
Krisztian (Apple) responds to Jungshin (Samsung).
Krisztian (Apple) responds to Qian (Ericsson).
Dieter (Deutsche Telekom): agrees previous comments and also propose to note the CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Antoine (Orange): This is not a Cat. F CR.
Jungshin (Samsung) resplies to Krisztian (Apple) and propose to note the CR.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.9 S2-2104727 CR Approval 23.502 CR2869 (Rel-17, 'F'): Providing alternative S-NSSAI(s) to the UE in EPC to 5GC interworking Apple Rel-17 Confirm Specification Number - CR states 23.501! Noted Laurent (Nokia): questions the Cat 'F' and claims this should be a candidate TEI18 feature
Sebastian (Qualcomm) objects to the CR for the same reason as stated by Nokia
Laurent (Nokia): objects to the CR for the reason already stated
Qian (Ericsson) agrees with others and suggests to NOTE the paper.
Krisztian (Apple) provides r01. Please see responses on the S2-2104723 thread.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): objects to any revision
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
6.10 - - - Non-3GPP access specific functionality and flows - - Docs:=5 -
6.10 S2-2103725 LS In Action LS from CT WG4: LS on N3IWF FQDN for emergency service CT WG4 (C4-211521) Revision of Postponed S2-2102109 from S2#144E. Response drafted in S2-2104625. Final response in S2-2104813 Sebastian (Qualcomm) proposes to note the LS assuming that S2-2104548 (CR) and S2-2104625 (Reply LS) will be agreed.
Andy (Samsung, VC) indicates that if the Reply LS is approved then it will be marked as 'replied to'
Replied to
6.10 S2-2104625 LS OUT Approval [DRAFT] Reply LS on N3IWF FQDN for emergency service QUALCOMM Rel-17 Response to S2-2103725. r00 agreed. Revised to S2-2104813.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.10 S2-2104813 LS OUT Approval Reply LS on N3IWF FQDN for emergency service SA WG2 Rel-17 Revision of S2-2104625. Approved Approved
6.10 S2-2104548 CR Approval 23.501 CR2848R1 (Rel-17, 'F'): FQDNs for N3IWF selection for emergency services Qualcomm, ZTE, Nokia, Nokai Shanghai Bell, Ericsson Rel-17 Revision of (Postponed) S2-2102924. Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
6.10 S2-2103723 LS In Action LS from CT WG1#128e: LS on mandate to provide any PLMN entry in the non-3GPP access node selection information in Rel-16 CT WG1 (C1-211203) Revision of Postponed S2-2102104 from S2#144E. Noted Laurent (Nokia): suggests to Note this LS
John-Luc (BlackBerry): supports the suggestion to Note this LS
Noted
6.11 - - - Framework functions - - Docs:=5 -
6.11 S2-2103726 LS In Action LS from CT WG4: LS on update a Binding Indication for multiple contexts CT WG4 (C4-211709) Revision of Postponed S2-2102111 from S2#144E. Postponed Thomas (Nokia) proposes to postpone this LS (again)
Fenqin (Huawei) also propose to postpone this LS .
Magnus (Ericsson) also think we should postpone this LS .
Josep (DT) points out that the attachment is missing, proposes to note this LS.
Thomas(Nokia) replies to Josep that probably some stage 2 alignments should be done
Postponed
6.11 S2-2104089 CR Approval 23.502 CR2768 (Rel-16, 'F'): CHF discovery via NRF Huawei, HiSilicon Rel-16 r01 agreed. Revised to S2-2104814. Thomas (Nokia) comments and provides r01
Susan (Huawei) is ok with r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.11 S2-2104814 CR Approval 23.502 CR2768R1 (Rel-16, 'F'): CHF discovery via NRF Huawei, HiSilicon Rel-16 Revision of S2-2104089r01. Approved Agreed
6.11 S2-2104090 CR Approval 23.502 CR2769 (Rel-17, 'A'): CHF discovery via NRF Huawei, HiSilicon Rel-17 r00 agreed. Revised to S2-2104815. Thomas (Nokia) provides comments
Susan (Huawei) provides r01.
Thomas (Nokia) is fine with r01 and comments that TS 23.501 changes will also be required
Susan (Huawei) agrees with Thomas a CR to 23.501 is needed for next meeting.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
6.11 S2-2104815 CR Approval 23.502 CR2769R1 (Rel-17, 'A'): CHF discovery via NRF Huawei, HiSilicon Rel-17 Revision of S2-2104090. Approved Agreed
7 - - - Rel-16 Maintenance for 5G (excluding 5GS_Ph1) - - Docs:=0 -
7.1 - - - Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) - - Docs:=0 -
7.2 - - - Wireless and Wireline Convergence for the 5G system architecture (5WWC) - - Docs:=14 -
7.2 S2-2104068 CR Approval 23.502 CR2763 (Rel-16, 'F'): Removal of Notification Control from the Additional QoS Information LG Electronics Rel-16 r01 agreed. Revised to S2-2104816. Dario S. Tonesi (Qualcomm) asks a question.
Myungjune (LGE) answers to Dario (Qualcomm).
Hualin(Huawei) comments on this paper.
Myungjune (LGE) replies to Hualin (Huawei).
Jinguo(ZTE) comments
Myungjune (LGE) replies to Jinguo (ZTE).
Jinguo (ZTE) replies to Myungjune (LGE).
Hualin(Huawei) replied Myungjune (LGE).
Myungjune (LGE) replies to Jinguo (ZTE) and clarifies that Notification control is used only in NG-RAN.
Myungjune (LGE) answers to Hualin (Huawei).
Laurent (Nokia): we support this paper
Jinguo(ZTE) ask question for clarification
Myungjune (LGE) answers to Jinguo (ZTE).
Jinguo(ZTE) suggest to note this paper (not fasmo) and go with Rel-17
Myungjune (LGE) suggests to have Rel-16 CR and provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.2 S2-2104816 CR Approval 23.502 CR2763R1 (Rel-16, 'F'): Removal of Notification Control from the Additional QoS Information LG Electronics Rel-16 Revision of S2-2104068r01. Approved Agreed
7.2 S2-2104069 CR Approval 23.502 CR2764 (Rel-17, 'A'): Removal of Notification Control from the Additional QoS Information LG Electronics Rel-17 r00 agreed. Revised to S2-2104817. Jinguo(ZTE) provides r01
Dario S. Tonesi (Qualcomm) supports r01 because clearer.
Myungjune (LGE) suggests to have Rel-16 CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm): if 4068r01 is approved, then 4069r01 needs to be updated to be Cat-A.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.2 S2-2104817 CR Approval 23.502 CR2764R1 (Rel-17, 'A'): Removal of Notification Control from the Additional QoS Information LG Electronics Rel-17 Revision of S2-2104069. Approved Agreed
7.2 S2-2104629 CR Approval 23.502 CR2852 (Rel-16, 'F'): Adding reference to different non-3GPP accesses Huawei, Hisilicon Rel-16 Noted Laurent (Nokia): this does not look like a FASMO
Stefan (Ericsson) agrees that FASMO is questionable. In addition a rel-17 mirror is missing
Marco (Huawei) answer. R17 mirror should be generated if we agree the CR
Andy (VC, Samsung) offers an opinion on what constitutes FASMO.
Marco (Huawei) if this R16 CR is not agreeable, we will submit a R17 CR cat 'F' in August meeting .
Laurent (Nokia): objects to this CR
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.2 S2-2104630 CR Approval 23.501 CR2958 (Rel-16, 'F'): Correction on non-3GPP access type Huawei, Hisilicon Rel-16 Approved Dario S. Tonesi (Qualcomm) comments.
Marco (Huawei) if this CR is approved, than a R17 mirror shall be generated since not submitted.
Laurent (Nokia): asks a question
Laurent (Nokia): I withdraw the question of the mail below (sent to a wrong thread)
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2104818 CR Approval 23.501 CR2990 (Rel-17, 'A'): Correction on non-3GPP access type Huawei, Hisilicon Rel-17 23.501 CR2990: Approved Agreed
7.2 S2-2104631 CR Approval 23.502 CR2853 (Rel-16, 'F'): Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access in deployments topologies with specific SMF Service Areas Huawei, Hisilicon Rel-16 r01 agreed. Revised to S2-2104819. Laurent (Nokia): provides r01+ comments
Marco (Huawei): reply to Nokia : yes a R17 mirror is needed and it should be generated if we are going to approve this CR
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.2 S2-2104819 CR Approval 23.502 CR2853R1 (Rel-16, 'F'): Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access in deployments topologies with specific SMF Service Areas Huawei, Hisilicon Rel-16 Revision of S2-2104631r01. Approved Agreed
7.2 S2-2104820 CR Approval 23.502 CR2879 (Rel-17, 'A'): Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access in deployments topologies with specific SMF Service Areas Huawei, Hisilicon Rel-17 23.502 CR2879: Approved Agreed
7.2 S2-2104472 CR Approval 23.502 CR2825 (Rel-16, 'F'): Add NG-RAN N3 Tunnel information in SM context ZTE, Ericsson, Huawei, CATT Rel-16 Approved Laurent (Nokia): comments and provides r01
Stefan (Ericsson) comments on r01 and prefers r00
Fenqin (Huawei) also prefer r00
Jinguo(ZTE) also prefer r00
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2104473 CR Approval 23.502 CR2826 (Rel-17, 'A'): Add NG-RAN N3 Tunnel information in SM context ZTE, Ericsson, Huawei , CATT Rel-17 r00 agreed. Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.2 S2-2104821 OTHER Approval Add NG-RAN N3 Tunnel information in SM context ZTE, Ericsson, Huawei , CATT Rel-17 WITHDRAWN Withdrawn
7.2 S2-2104476 DISCUSSION Agreement Discussion on N3 tunnel information transmission between I-SMF. ZTE Rel-16 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.3 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) - - Docs:=2 -
7.3 S2-2104070 CR Approval 23.501 CR2884 (Rel-16, 'F'): Clarification on how the UPF gets PMF address of the UE LG Electronics Rel-16 Noted Dario S. Tonesi (Qualcomm) asks question for clarification about the need of this CR
Myungjune (LGE) answers to Dario (Qualcomm).
Hualin(Huawei) request to add the corresponding CT1 texts to the reason for change.
Yannick (Nokia): Nokia provides comments.
Dario S. Tonesi (Qualcomm) replies to Myungjune.
Myungjune (LGE) is ok to NOTE this CR and mirror.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.3 S2-2104071 CR Approval 23.501 CR2885 (Rel-17, 'A'): Clarification on how the UPF gets PMF address of the UE LG Electronics Rel-17 Noted
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.4 - - - Cellular IoT support and evolution for the 5G System (5G_CIoT) + RAN Rel-16 alignment - MT-EDT - - Docs:=8 -
7.4 S2-2104556 CR Approval 23.501 CR2943 (Rel-16, 'F'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-16 Confirm CR Number - CR Number and CR Revision reversed ! Agreed. Revised to S2-2104822
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.4 S2-2104822 CR Approval 23.501 CR2943R1 (Rel-16, 'F'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2104556. Approved Agreed
7.4 S2-2104589 CR Approval 23.501 CR2947 (Rel-17, 'A'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-17 Confirm CR Number - CR Number and CR Revision reversed ! r00 agreed. Revised to S2-2104823.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.4 S2-2104823 CR Approval 23.501 CR2947R1 (Rel-17, 'A'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104589. Approved Agreed
7.4 S2-2104590 CR Approval 23.502 CR2842 (Rel-16, 'F'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-16 Confirm CR Number - CR Number and CR Revision reversed ! r01 agreed. Revised to S2-2104824. Steve (Huawei) provides r01
Hannu (Nokia) thanks Steve (Huawei) for good correction and supports r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.4 S2-2104824 CR Approval 23.502 CR2842R1 (Rel-16, 'F'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2104590r01. Approved Agreed
7.4 S2-2104591 CR Approval 23.502 CR2843 (Rel-17, 'A'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-17 Confirm CR Number - CR Number and CR Revision reversed ! r00 agreed. Revised to S2-2104825.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.4 S2-2104825 CR Approval 23.502 CR2843R1 (Rel-17, 'A'): NIDD configuration correction Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104591. Approved Agreed
7.5 - - - Enablers for Network Automation for 5G (eNA) - - Docs:=12 -
7.5 S2-2103812 CR Approval 23.288 CR0333 (Rel-16, 'F'): Clarification on output parameters in OSE Ericsson Rel-16 Confirm Spec version used - CR states 17.0.0! r03 agreed. Revised to S2-2104826. Belen (Ericsson) provides r01, fixing the specification release.
Yannick (Nokia): Nokia comments on r00 and r01.
David (Samsung) provides questions on the motivation for this CR and its mirror S2-2103813.
Belen (Ericsson) replies to Nokia and Samsung
David (Samsung) provides further comments.
Belen (Ericsson) provides r02.
Belen (Ericsson) asks Samsung and Nokia if their comments are addressed
David (Samsung) is OK with r02.
Yannick (Nokia): Nokia provides r03.
Belen (Ericsson) is okay with r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104826 CR Approval 23.288 CR0333R1 (Rel-16, 'F'): Clarification on output parameters in OSE Ericsson Rel-16 Revision of S2-2103812r03. Approved Agreed
7.5 S2-2103813 CR Approval 23.288 CR0334 (Rel-17, 'A'): Clarification on output parameters in OSE Ericsson Rel-17 r02 agreed. Revised to S2-2104827. Yannick (Nokia): Nokia provides r01.
Leo (Deutsche Telekom) provides comment on r00 and r01.
David (Samsung) provides comments.
Yannick (Nokia): Nokia agrees with Samsung and Deutsche Telekom that this CR should be revised to be a mirror of the corresponding Rel-16 CR. The CR should not contain changes related to ongoing Rel-17 eNA_Ph2 discussions.
Belen (Ericsson) provides r02.
David (Samsung) is OK with r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104827 CR Approval 23.288 CR0334R1 (Rel-17, 'A'): Clarification on output parameters in OSE Ericsson Rel-17 Revision of S2-2103813r02. Approved Agreed
7.5 S2-2104248 CR Approval 23.502 CR2792 (Rel-16, 'F'): Clarify the BDT warning procedure with degraded Network performance Huawei, HiSilicon Rel-16 r02 agreed. Revised to S2-2104828. Belen (Ericsson) asks about the reason for change and the motivation for this CR.
Mirko (Huawei) responds to Belen.
Belen (Ericsson) is okay with this CR.
Yannick (Nokia): Nokia comments on original version.
Mirko (Huawei) responds to Yannick.
Yannick (Nokia): Nokia provides r01.
Mirko (Huawei) responds to Yannick and provides r02.
Yannick (Nokia): Nokia is fine with r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104828 CR Approval 23.502 CR2792R1 (Rel-16, 'F'): Clarify the BDT warning procedure with degraded Network performance Huawei, HiSilicon Rel-16 Revision of S2-2104248r02. Approved Agreed
7.5 S2-2104249 CR Approval 23.502 CR2793 (Rel-17, 'A'): Clarify the BDT warning procedure with degraded Network performance Huawei, HiSilicon Rel-17 r00 agreed. Revised to S2-2104829.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104829 CR Approval 23.502 CR2793R1 (Rel-17, 'A'): Clarify the BDT warning procedure with degraded Network performance Huawei, HiSilicon Rel-17 Revision of S2-2104249. Approved Agreed
7.5 S2-2104250 CR Approval 23.503 CR0588 (Rel-16, 'F'): Clarify the BDT warning description with degraded Network performance Huawei, HiSilicon Rel-16 Confirm Spec version used - CR states 17.0.0! r03 agreed. Revised to S2-2104830. Belen (Ericsson) asks about the reason for change and the motivation for this CR.
Mirko (Huawei) responds to Belen.
Belen (Ericsson) is okay with this CR.
Leo (Deutsche Telekom) provides r01
Yannick (Nokia): Nokia provides r02.
Mirko (Huawei) responds and provides r03.
Leo (Deutsche Telekom) is fine with r03.
Yannick (Nokia): Nokia is also fine with r03.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104830 CR Approval 23.503 CR0588R1 (Rel-16, 'F'): Clarify the BDT warning description with degraded Network performance Huawei, HiSilicon Rel-16 Revision of S2-2104250r03. Approved Agreed
7.5 S2-2104251 CR Approval 23.503 CR0589 (Rel-17, 'A'): Clarify the BDT warning description with degraded Network performance Huawei, HiSilicon Rel-17 Confirm Spec version used - CR states 16.8.0! r00 agreed. Revised to S2-2104831. Mirko (Huawei) provides r01 to have a correct cover page.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.5 S2-2104831 CR Approval 23.503 CR0589R1 (Rel-17, 'A'): Clarify the BDT warning description with degraded Network performance Huawei, HiSilicon Rel-17 Revision of S2-2104251. Approved Agreed
7.6 - - - Enhancement to the 5GC Location Services (5G_eLCS) - - Docs:=4 -
7.6 S2-2104012 CR Approval 23.273 CR0173 (Rel-16, 'F'): Assistance Data Delivery in 5G-MO-LR Nokia, Nokia Shanghai Bell Rel-16 Confirm CR Number - CR states ! r01 agreed. Revised to S2-2104832. Leo (Deutsche Telekom) provides r01.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.6 S2-2104832 CR Approval 23.273 CR0173R1 (Rel-16, 'F'): Assistance Data Delivery in 5G-MO-LR Nokia, Nokia Shanghai Bell Rel-16 Revision of S2-2104012r01. Approved Agreed
7.6 S2-2104461 CR Approval 23.273 CR0178 (Rel-16, 'F'): Update of LCS exposure via NEF Huawei Rel-16 r01 agreed. Revised to S2-2104833. Leo (Deutsche Telekom) provides r01.
Åke (Ericsson) Comments that CR include text that overlaps and contradicts agreed CR168 rev1 (S2-2103234).
Runze (Huawei) agrees with Ake's view on the implementation, and proposed to agree r01 .
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.6 S2-2104833 CR Approval 23.273 CR0178R1 (Rel-16, 'F'): Update of LCS exposure via NEF Huawei Rel-16 Revision of S2-2104461r01. Approved Agreed
7.7 - - - 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) - - Docs:=0 -
7.7.1 - - - 5GS Enhanced support of Vertical and LAN Services - 5G-LAN aspects - - Docs:=1 -
7.7.1 S2-2103724 LS In Action LS from CT WG4: Reply LS on Additional Clarifications on LI requirements applicable to SNPNs CT WG4 (C4-211519) Revision of Postponed S2-2102108 from S2#144E. Noted Sebastian (Qualcomm) proposes to note the LS assuming that S2-2103750 and S2-2104643 will be approved, which address the action in this LS Noted
7.7.2 - - - 5GS Enhanced support of Vertical and LAN Services - TSN aspects - - Docs:=2 -
7.7.2 S2-2104230 CR Approval 23.502 CR2791 (Rel-16, 'F'): Correction of reference for TSN AF parameters Samsung Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.7.2 S2-2104257 CR Approval 23.502 CR2794 (Rel-17, 'A'): Correction of reference for TSN AF parameters Samsung Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.7.3 - - - 5GS Enhanced support of Vertical and LAN Services - Type a/b aspects - - Docs:=7 -
7.7.3 S2-2104172 CR Approval 23.501 CR2901 (Rel-16, 'F'): EPS<->5GS HO considering CAG Huawei, HiSilicon Rel-16 Postponed Fei (OPPO) comments
Qianghua (Huawei) replies
Fei (OPPO) responds
Qianghua (Huawei) provides r01
Josep (DT) asks a question for clarification in understanding what this CR aims to achieve.
Josep (DT) comments.
Peter Hedman (Ericsson) provides comments and a simple option is to not enable EPS for PNI-NPN subscriptions with CAG restrictions.
Josep (DT) proposes r02 based on Ericsson's suggestion.
Qianghua (Huawei) provides r03
Peter Hedman (Ericsson) provides r04
Devaki (Nokia) comments that the note does not sound right in r04, r05. Stating that the deployments should disable EPS for the sake of single UE is strange.
Sebastian (Qualcomm) proposes to postpone the CR
Devaki (Nokia) supports the proposal to postpone the CR.
Qianghua (Huawei) provides r05 if we finally decide to not support interworking with EPS for PNI-NPN
Qianghua (Huawei) provides r06 if we decide to postpone EPS->5GS HO, but the remaining updates still bring value, it clarifies that the MRL is considered by NG-RAN only for HO within 5GS, and addresses the conflicts for description of some bullets
Devaki (Nokia) proposes to postpone, addition to other bullets are not really FASMO.
Sebastian (Qualcomm) shares the view expressed by Devaki (Nokia)
Peter Hedman (Ericsson) provides reply
Sebastian (Qualcomm) asks a question
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Josep (DT) also proposes to postpone, send an LS before continuing.
Qianghua (Huawei) asks a question
Sebastian (Qualcomm) replies to Peter
Josep (DT) objects to r05, r01, r00.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
7.7.3 S2-2104173 CR Approval 23.502 CR2786 (Rel-16, 'F'): Registration with AMF relocation considering CAG Huawei, HiSilicon Rel-16 CC#2: r01 + changes agreed. Revised to S2-2105006. Peter Hedman (Ericsson) provides reply and asks if possible to make minor revision
Qianghua (Huawei) provides r01 in draft/revision folder and asks if this needs to be confirmed at CC#2
Andy (VC, Samsung) indicates that as the disposition wasn't clear we should open this in CC#2 to discuss the revision.
Peter Hedman (Ericsson) is ok with r01.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.3 S2-2105006 CR Approval 23.502 CR2786R1 (Rel-16, 'F'): Registration with AMF relocation considering CAG Huawei, HiSilicon Rel-16 Revision of S2-2104173r01 + changes. Approved Agreed
7.7.3 S2-2103750 CR Approval 23.501 CR2849R1 (Rel-16, 'F'): Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs Qualcomm Rel-16 Revision of (Postponed) S2-2102927. r03 agreed. Revised to S2-2104834. George (Ericsson) provides r01. Just added Ericsson as co-signer. We support this proposal
Devaki (Nokia) provides r02.
Sebastian (Qualcomm) provides r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.3 S2-2104834 CR Approval 23.501 CR2849R2 (Rel-16, 'F'): Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs Qualcomm Rel-16 Revision of S2-2103750r03. Approved Agreed
7.7.3 S2-2104643 CR Approval 23.501 CR2963 (Rel-17, 'A'): Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs Qualcomm Rel-17 r00 agreed. Revised to S2-2104835. Sebastian (Qualcomm) provides r01
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.7.3 S2-2104835 CR Approval 23.501 CR2963R1 (Rel-17, 'A'): Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs Qualcomm Rel-17 Revision of S2-2104643. Approved Agreed
7.8 - - - Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - - Docs:=3 -
7.8 S2-2104164 CR Approval 23.502 CR2784 (Rel-16, 'F'): SM policy control update due to SMF relocation Samsung Rel-16 Noted Fenqin (Huawei) ask question for clarification
Thomas (Nokia) comments that CR is not required.
Youngkyo(Samsung) replies to Fenqin (Huawei) and Thomas (Nokia). Okay to note this rel 16 CR but propose to keep rel 17.
Fenqin (Huawei) responds
Youngkyo(Samsung) replies to Fenqin (Huawei).
Thomas (Nokia) replies to Youngkyo(Samsung)
Youngkyo(Samsung) replies to Thomas (Nokia).
Thomas (Nokia) makes a text proposal
Youngkyo(Samsung) thanks for the text proposals, which will be implemented in the rel 17 CR
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.8 S2-2104166 CR Approval 23.502 CR2785 (Rel-17, 'A'): SM policy control update due to SMF relocation Samsung Rel-17 CC#2: All changes to be replaced by a note. Revised to S2-2105007. Youngkyo(Samsung) provide revision r01 with changing CR category 'F' from 'A'
Youngkyo(Samsung) privides revision r02
Thomas(Nokia) comments against revision r02
Thomas(Nokia) adds further explanation why CR is not required
Fenqin (Huawei) comment
Thomas(Nokia) replies to Fenqin
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Youngkyo(Samsung) replies to Thomas(Nokia)
Thomas(Nokia) replies to Youngkyo(Samsung)
Fenqin (Huawei) provides comment
Thomas (Nokia) replies to Fenqin
Youngkyo(Samsung) replies to Thomas and Fenqin
Youngkyo(Samsung) requests their view on the text proposal.
Fenqin (Huawei) responds.
Youngkyo(Samsung) responds.
Thomas(Nokia) accept latest proposal of Youngkyo
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.8 S2-2105007 CR Approval 23.502 CR2785R1 (Rel-17, 'A'): SM policy control update due to SMF relocation Samsung Rel-17 Revision of S2-2104166 (All changes to be replaced by a note). Approved Agreed
7.9 - - - Architecture enhancements for the support of Integrated access and backhaul (IABARC) - - Docs:=0 -
7.10 - - - Other Rel-16 WIDs - - Docs:=0 -
7.10.1 - - - Enhancement of URLLC supporting in 5GC (5G_URLLC) - - Docs:=7 -
7.10.1 S2-2104085 CR Approval 23.501 CR2889 (Rel-17, 'A'): Updates on PCC rule triggered GTP-U Path Monitoring Huawei, HiSilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.1 S2-2104086 CR Approval 23.503 CR0582 (Rel-17, 'A'): Updates to Support QoS Monitoring Control for Service Data Flows Huawei, HiSilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.1 S2-2104087 CR Approval 23.502 CR2766 (Rel-16, 'F'): N9 forwarding tunnel between source and target ULCL Huawei, HiSilicon Rel-16 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.1 S2-2104088 CR Approval 23.502 CR2767 (Rel-17, 'A'): N9 forwarding tunnel between source and target ULCL Huawei, HiSilicon Rel-17 Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.1 S2-2104112 CR Approval 23.501 CR2891 (Rel-17, 'F'): URLLC redundant session Nokia, Nokia Shanghai Bell Rel-17 Noted Shabnam (Ericsson) proposed to NOTE this CR since there is no formal relation between the two different approaches of the redundant end to end solutions and as such no need to couple them.
Devaki (Nokia) replies to Ericsson.
Devaki (Nokia) provides r01.
Jinguo (ZTE) comments
Hui (Huawei) proposed to NOTE this CR.
Devaki (Nokia) replies.
Devaki (Nokia) comments and requests Hui to check r01.
Hui(Huawei) responses.
Devaki (Nokia) comments.
Devaki (Nokia) provides r02.
Shabnam (Ericsson) does not believe r01 or r02 addresses the concern, this Annex is for single device/two UEs scenario, so the moment it is single UE then we are no longer belong to this Annex & adding the note misleading.
Yang (OPPO) agrees Huawei's comment that switching decision is made in application layer which is out of SA2 scope. Also propose to note this CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.10.1 S2-2104714 CR Approval 23.502 CR2643R2 (Rel-16, 'F'): Support of AF change CATT, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson Rel-16 Revision of (Agreed) S2-2103222. Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.1 S2-2104724 CR Approval 23.502 CR2667R2 (Rel-17, 'A'): Support of AF change Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of (Agreed) S2-2103221. Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.2 - - - Enhancement of Network Slicing (eNS) - - Docs:=10 -
7.10.2 S2-2103828 CR Approval 23.502 CR2738 (Rel-17, 'A'): NSSAA procedures for the UE when it is served by two different AMFs Samsung Rel-17 r03 agreed. Revised to S2-2104836. alessio(Nokia) provides r01
Ashok (Samsung) replies to alessio(Nokia)
Peter Hedman (Ericsson) provides comments that proposal does not work.
Peter Hedman (Ericsson) provides reply to Nokia
Genadi (Lenovo) comments on the parallel EAP authentication triggered by 2 different AMFs.
Jinguo(ZTE) agree with Genadi (Lenovo)
Alessio (Nokia) asks Genady/Peter to explain how the contexts are unreliable and also why a NSSAAF cannot handle two EACP sessions in parallel since EACH has its context.
Ashok (Samsung) also agrees with Jinguo(ZTE) and Genadi (Lenovo) and replies to Peter (Ericsson) & Alessio (Nokia)
Genadi (Lenovo) responds to Alessio (Nokia) regarding the context reliability and parallel EAP authentication.
Peter Hedman (Ericsson) provides r02
Ashok (Samsung) is OK with r02
Alessio(nokia) comments that r02 is acceptable
Jinguo(ZTE) is OK with r02
Patrice (Huawei) is OK with r02. It is expected that CR category will be changed as part of the clean-up.
Ashok (Samsung) provides r03 (just changing Cat 'A' to 'F')
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.2 S2-2104836 CR Approval 23.502 CR2738R1 (Rel-17, 'A'): NSSAA procedures for the UE when it is served by two different AMFs Samsung Rel-17 Revision of S2-2103828r03. Approved Agreed
7.10.2 S2-2103829 CR Approval 23.502 CR2739 (Rel-16, 'F'): NSSAA procedures for the UE when it is served by two different AMFs Samsung Rel-16 Noted Peter Hedman (Ericsson) provides r01
Ashok (Samsung) replies to Peter Hedman (Ericsson)
alessio (Nokia) comments this is not a FASMO issue as the NSSAAF can apply local logic to select whether to restrict execution to one AMF only for reauth, and of course revocation has to apply for all applicable AMFs... but we can accept discussing this in rekl-17 context only.
Patrice (Huawei) comments that the issue could exist, and that the fact that Allowed NSSAI is separate for each access means that it has to be done as described in r01.
Ashok (Samsung) replies to Patrice (Huawei), Peter (Ericsson), Alessio (Nokia)
Peter Hedman (Ericsson) provides comments.
Peter Hedman (Ericsson) proposes to note the CR as not FASMO and focus on Rel-17 CR.
Ashok (Samsung) OK to note the CR
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.10.2 S2-2104369 CR Approval 23.501 CR2922 (Rel-16, 'F'): Allowed NSSAI when NSSAA fails Samsung Rel-16 Noted Peter Hedman (Ericsson) proposes to note the CR as logic is already described.
Hoyeon (Samsung) replies to Peter Hedman (Ericsson).
Peter Hedman (Ericsson) proposes to note the CR as not FASMO
Hoyeon (Samsung) is OK to note the CR.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.10.2 S2-2104373 CR Approval 23.501 CR2923 (Rel-17, 'A'): Allowed NSSAI when NSSAA fails Samsung Rel-17 r02 agreed. Revised to S2-2104837. Hoyeon (Samsung) provides r01.
Peter Hedman (Ericsson) provides r02
Hoyeon (Samsung) is OK with r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.2 S2-2104837 CR Approval 23.501 CR2923R1 (Rel-17, 'A'): Allowed NSSAI when NSSAA fails Samsung Rel-17 Revision of S2-2104373r02. Approved Agreed
7.10.2 S2-2104374 CR Approval 23.502 CR2806 (Rel-16, 'F'): Allowed NSSAI when NSSAA fails Samsung Rel-16 Noted Peter Hedman (Ericsson) propose to note the CR as the CR is not FASMO
Hoyeon (Samsung) is OK to note the CR and to proceed the Rel-17 CR only.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Noted
7.10.2 S2-2104376 CR Approval 23.502 CR2807 (Rel-17, 'A'): Allowed NSSAI when NSSAA fails Samsung Rel-17 r03 agreed. Revised to S2-2104838. Peter Hedman (Ericsson) provides r01
Hoyeon (Samsung) is OK with r01
Hoyeon (Samsung) provides r02 (just changing Cat 'A' to 'F')
Alessio(Nokia) provides r03
Jinguo(ZTE) provides r04
Alessio(Nokia) thinks that r04 is not correct.
Jinguo(ZTE) replies to Alessio(Nokia).
Jinguo(ZTE) can live with r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Hoyeon (Samsung) proposes to approve r03.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.2 S2-2104838 CR Approval 23.502 CR2807R1 (Rel-17, 'A'): Allowed NSSAI when NSSAA fails Samsung Rel-17 Revision of S2-2104376r03. Approved Agreed
7.10.2 S2-2104455 CR Approval 23.502 CR2722R2 (Rel-17, 'A'): New service operation of Namf_Communication_CancelRelocateUEContext ZTE Rel-17 Revision of (Agreed) S2-2103215. Approved
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Agreed
7.10.3 - - - Optimisations on UE radio capability signalling (RACS) - - Docs:=8 -
7.10.3 S2-2104726 CR Approval 23.502 CR2868 (Rel-16, 'F'): Handling of UTRAN UE radio capabilities Vodafone Rel-16 WI Code SAE should be SAES. r02 agreed. Revised to S2-2104839. Qian (Ericsson) provides comments and r01.
Chris (Vodafone) provides r02.
Chris (Vodafone) prefers r02.
Wanqiang (Huawei) prefers r02.
Lalith(Samsung) shares view of Wanqiang(Huawei) and prefers r02.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Qian (Ericsson) is ok with r02.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2104839 CR Approval 23.502 CR2868R1 (Rel-16, 'F'): Handling of UTRAN UE radio capabilities Vodafone Rel-16 Revision of S2-2104726r02. Approved Agreed
7.10.3 S2-2104728 CR Approval 23.502 CR2870 (Rel-17, 'A'): Handling of UTRAN UE radio capabilities Vodafone Rel-17 r00 agreed. Revised to S2-2104840.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2104840 CR Approval 23.502 CR2870R1 (Rel-17, 'A'): Handling of UTRAN UE radio capabilities Vodafone Rel-17 Revision of S2-2104728. Approved Agreed
7.10.3 S2-2104747 CR Approval 23.501 CR2983 (Rel-16, 'F'): Correction to trigger for UE Radio Capability Update procedure Apple Rel-16 r04 agreed. Revised to S2-2104841. Haris(Qualcomm) provides r01 or he is ok to note
Wanqiang(Huawei) comment that the current text is correct.
Lalith(Samsung) supports r01
alessio(Nokia) agrees R01 is acceptable.
Krisztian (Apple) responds to Haris (Qualcomm) and Wanqiang (Huawei) and provides r02.
Wanqiang(Huawei) is ok with r02.
Alessio(nokia) provides r03 simplifying the text and adding supporting companies
Krisztian (Apple) provides r04.
alessio(Nokia)OK with r04.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2104841 CR Approval 23.501 CR2983R1 (Rel-16, 'F'): Correction to trigger for UE Radio Capability Update procedure Apple Rel-16 Revision of S2-2104747r04. Approved Agreed
7.10.3 S2-2104748 CR Approval 23.501 CR2984 (Rel-17, 'A'): Correction to trigger for UE Radio Capability Update procedure Apple Rel-17 r00 agreed. Revised to S2-2104842. Haris(Qualcomm) comments as per S2-2104747 apply, it needs to be updated accordingly
Krisztian (Apple) provides r01 aligned with S2-2104747r02.
Alessio (Nokia) provides r02 aligned with S2-2104747r03.
Krisztian (Apple) provides r03 aligned with S2-2104747r04.
alessio(nokia) ok with r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.3 S2-2104842 CR Approval 23.501 CR2984R1 (Rel-17, 'A'): Correction to trigger for UE Radio Capability Update procedure Apple Rel-17 Revision of S2-2104748. Approved Agreed
7.10.4 - - - Enhanced IMS to 5GC Integration (eIMS5G_SBA) - - Docs:=0 -
7.10.5 - - - User Data Interworking and Coexistence (UDICoM) - - Docs:=0 -
7.10.6 - - - Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) - - Docs:=6 -
7.10.6 S2-2104380 CR Approval 23.502 CR2810 (Rel-16, 'F'): Simultaneous change of ULCL/BP and PSA Huawei, HiSilicon Rel-16 r03 agreed. Revised to S2-2104843. Laurent (Nokia): provides r01
Fenqin (Huawei): responds and provides r02
Stefan (Ericsson) provides r03
Fenqin (Huawei) accept r03
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2104843 CR Approval 23.502 CR2810R1 (Rel-16, 'F'): Simultaneous change of ULCL/BP and PSA Huawei, HiSilicon Rel-16 Revision of S2-2104380r03. Approved Agreed
7.10.6 S2-2104381 CR Approval 23.502 CR2811 (Rel-17, 'A'): Simultaneous change of ULCL/BP and PSA Huawei, HiSilicon Rel-17 r00 agreed. Revised to S2-2104844.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Revised
7.10.6 S2-2104844 CR Approval 23.502 CR2811R1 (Rel-17, 'A'): Simultaneous change of ULCL/BP and PSA Huawei, HiSilicon Rel-17 Revision of S2-2104381. Approved Agreed
7.10.6 S2-2104382 CR Approval 23.502 CR2812 (Rel-16, 'F'): L-PSA release during mobiity procedure with I-SMF removal Huawei, HiSilicon Rel-16 Postponed Stefan (Ericsson) asks question
Laurent (Nokia): provides r01
Stefan (Ericsson) provides comments
Fenqin (Huawei) responds and provides r02
Stefan (Ericsson) provides additional comments
Laurent (Nokia): Comments
Stefan (Ericsson) comments
Laurent (Nokia): answers and provides r03
Jinguo(ZTE) comments
Fenqin (Huawei) responds and provide r04
Laurent (Nokia): provides r05
Stefan (Ericsson) provides questions
Fenqin (Huawei): responds
Laurent (Nokia): asks to postpone this CR
Stefan (Ericsson) OK to postpone
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Fenqin (Huawei) propose to go with r04 at this meeting
Laurent (Nokia): objects to R00, R02 and R04 and thinks it is better to postpone
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
7.10.6 S2-2104383 CR Approval 23.502 CR2813 (Rel-17, 'A'): L-PSA release during mobility procedure with I-SMF removal Huawei, HiSilicon Rel-17 Postponed
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Postponed
7.10.7 - - - 5GS Transfer of Policies for Background Data Transfer (xBDT) - - Docs:=0 -
7.10.8 - - - Single radio voice continuity from 5GS to 3G (5G_SRVCC) - - Docs:=0 -
8 - - - Rel-17 WID - - Docs:=0 -
8.1 - - - Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) - - Docs:=152 -
8.1 - - - General - - Docs:=6 -
8.1 S2-2103942 CR Approval 23.288 CR0304R2 (Rel-17, 'F'): Miscellaneous correction(s) vivo Rel-17 Revision of (Agreed) S2-2103238. Revised to S2-2103961 Revised
8.1 S2-2103961 CR Approval 23.288 CR0304R3 (Rel-17, 'F'): Miscellaneous correction(s) vivo Rel-17 Revision of S2-2103942 (revision of (Agreed) S2-2103238). r01 agreed. Revised to S2-2104845, merging S2-2104027 Xiaobo (vivo) propose r01 by incorporating the proposed changes from 2-2104027 into S2-2103961.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104845 CR Approval 23.288 CR0304R5 (Rel-17, 'F'): Miscellaneous correction(s) vivo Rel-17 Revision of S2-2103961r01, merging S2-2104027. Approved Agreed
8.1 S2-2103962 DISCUSSION Information Editor's Notes summary for eNA_ph2. Vivo, China Mobile Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104027 CR Approval 23.288 CR0304R4 (Rel-17, 'F'): Miscellaneous correction(s) ETRI, vivo (?) Rel-17 Revision of (Agreed) S2-2103238. Confirm Sources!. Confirm CR Revision - CR states 2! Merged into S2-2104845 Xiaobo (vivo) propose to merge S2-2104027 into S2-2103961.
Soohwan (ETRI) is okay to merge.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104321 CR Approval 23.503 CR0593 (Rel-17, 'B'): ENA_ Update of Slice Data Rate Analytics Xiaomi Rel-17 Confirm Specification Number - CR states 23.288! Should be 23.288 CR0354. Noted David (Samsung) provides comments.
Yannick (Nokia): Nokia provides comments.
Peretz (Spirent) provides similar/related comments.
Jinhua(Xiaomi) response to David (Samsung) about analytics support KI#5 of eNS_ph2.
Jinhua(Xiaomi) response to Yannick (Nokia) for output clarification.
Jinhua(Xiaomi) response to Peretz (Spirent)
Yannick (Nokia): Nokia requests for clarification.
Jinhua(Xiaomi) response to Yannick (Nokia) about analytics reusing.
Yannick (Nokia): Nokia suggests to note this proposal.
David (Samsung) also supports noting this proposal.
Jinhua(Xiaomi) response to Yannick (Nokia) and David (Samsung) , noted is OK and support updating existing analytics in 4084.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 - - - KI#1 - - Docs:=5 -
8.1 S2-2104450 CR Approval 23.288 CR0355 (Rel-17, 'B'): Clarification on the NWDAF decomposition NTT DOCOMO, Orange, Deutsche Telekom, AT&T, China Mobile, Verizon, T-Mobile USA, Telecom Italia, Rakuten Mobile, China Unicom Rel-17 CC#5: r09 + changes agreed. Revised to S2-2105194. Malla (NTT DOCOMO) provided r01
Megha(Intel) asks a question for clarification.
Soohwan (ETRI) asks questions for clarification.
Malla (NTT DOCOMO) replies to Soohwan (ETRI) and Megha(Intel).
Gerald (Nokia): Nokia asks for clarification
Wang Yuan (Huawei) provides r02
Xiaobo (vivo) provides r03 considering that we will further study this issue in R18
Malla (NTT DOCOMO) replies to Gerald (Nokia).
Dimitris (Lenovo) requests clarifications provides r04
Miguel (Ericsson) provides r05
Gerald (Nokia): Nokia comments on the discussion
David (Samsung) comments
Dimitris (Lenovo) comments
Malla (NTT DOCOMO) comments
Miguel (Ericsson) agrees with r04
Farooq (AT&T) between r04 and r05 prefers r05 with a minor change of 'is' to 'can be' in the last sentence of the note
David (Samsung) supports the comment from AT&T, provides r06
Malla (NTT DOCOMO) provides r07
Leo (Deutsche Telekom) supports the proposed changes in r07
Dimitris (Lenovo) request clarification on the usage of ModelID/VendorID proposed in some revisions
Wang Yuan (Huawei) share similar comment with Lenovo on Model ID/Vendor ID
Gerald (Nokia): Nokia assumes enhancements to NWDAF registration, discovery and selection are required. Asks for clarification on ModelID.
Malla (NTT DOCOMO) provides r08 for the discussion.
Miguel (Ericsson) are leaning towards version r07
Gerald (Nokia): Nokia prefers opt#1 with a comment, disagrees with opt#2, provides r09
David (Samsung) supports r09
==== 8.X, 9.X Revisions Deadline ====
Xiaobo (vivo) is ok with either r08 or r09 and prefer r09
Wang Yuan (Huawei) asks for clarification on r09 and suggest to discuss on CC#4 for potential revision
Gerald (Nokia): Nokia prefers r09
Dimitris (Lenovo) supports r09 as a good compromise.
Xiaoyan (CATT) provides a comment.
Wang Yuan (Huawei) share the same comment with CATT and provides further comments.
Malla (NTT DOCOMO) provided comment.
Xiaoyan (CATT) replies to Malla (NTT DOCOMO).
Gerald (Nokia): Nokia comments on the proposal
XIaoyan (CATT) provides further suggestion.
==== 8.X, 9.X Final Deadline ====
Gerald (Nokia): Nokia provides comment
Xiaobo(vivo) provides response to Gerald(Nokia) and reword the NOTE to address the concern from Gerald(Nokia) and also the comments from Xiaoyan(CATT).
Gerald (Nokia): Nokia responds to latest proposal
Xiaobo(vivo) is ok with the proposal from Gerald(Nokia) and no strong view to use 'may'.
Revised
8.1 S2-2105194 CR Approval 23.288 CR0355R1 (Rel-17, 'B'): Clarification on the NWDAF decomposition NTT DOCOMO, Orange, Deutsche Telekom, AT&T, China Mobile, Verizon, T-Mobile USA, Telecom Italia, Rakuten Mobile, China Unicom Rel-17 Revision of S2-2104450r09 + changes. Approved Agreed
8.1 S2-2104704 CR Approval 23.501 CR2972 (Rel-17, 'B'): NWDAF discovery update Nokia, Nokia Shanghai Bell Rel-17 Noted Dimitris (Lenovo) provides questions
Gerald (Nokia): Nokia responds to Lenovo
Malla (NTT DOCOMO) objects r00 and propose to note the CR.
Leo (Deutsche Telekom) shares the view of Malla (NTT DOCOMO) and objects r00.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104705 CR Approval 23.502 CR2863 (Rel-17, 'B'): NWDAF discovery update Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) object r00 and propose to note the CR.
Leo (Deutsche Telekom) objects r00
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104706 LS OUT Approval [DRAFT] LS on model sharing among trusted vendors Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) object to send the LS.
Leo (Deutsche Telekom) objects r00 of the LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 - - - KI#2 - - Docs:=36 -
8.1 S2-2103830 CR Approval 23.288 CR0298R1 (Rel-17, 'F'): Resolve ENs for clause 5.2 CATT Rel-17 Revision of (Postponed) S2-2102545. Merged into S2-2104846 Miguel (Ericsson) provides comments and suggests merging with S2-2103882
Mehrdad (Samsung) suggests to merge 3830, 3882, 4571 together and adopt one as the baseline.
Miguel (Ericsson) provides S2-2103882r01 merging S2-2103830, S2-2103882 and S2-2104571
==== 8.X, 9.X Revisions Deadline ====
Hucheng(CATT) is OK with merging this paper into 3882.
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2103876 CR Approval 23.288 CR0259R1 (Rel-17, 'B'): NWDAF registering into UDM Ericsson, Deutsche Telekom Rel-17 Revision of (Postponed) S2-2102179. r01 agreed. Revised to S2-2104847. Gerald (Nokia): Nokia comments on original
Miguel (Ericsson) replies to Gerald
Miguel (Ericsson) provides r01
Leo (Deutsche Telekom) is fine with r01, thanks.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia can live with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104847 CR Approval 23.288 CR0259R2 (Rel-17, 'B'): NWDAF registering into UDM Ericsson, Deutsche Telekom Rel-17 Revision of S2-2103876r01. Approved Agreed
8.1 S2-2103877 CR Approval 23.501 CR2702R2 (Rel-17, 'B'): Discover NWDAF for UE related Analytics using UDM Ericsson Rel-17 Revision of (Agreed) S2-2103244. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2103878 CR Approval 23.288 CR0299R2 (Rel-17, 'F'): Resolve ENs for clause 6.1A.3.2 CATT, Ericsson Rel-17 Revision of (Agreed) S2-2103250. r05 agreed. Revised to S2-2104848, merging S2-2104031 Gerald (Nokia): Nokia asks for clarification
Miguel (Ericsson) replies to Gerald
Gerald (Nokia): Nokia responds to Ericsson
Miguel (Ericsson) responds to Nokia
Gerald (Nokia): Nokia replies to Ericsson
Miguel (Ericsson) provides r01 merging S2-2104031 into it
Gerald (Nokia): Nokia asks for clarification on r01
Miguel (Ericsson) answers to Gerald about r01
Hucheng (CATT) is fine with having a merger, but have a similar concern as Nokia, and then proposes r02.
Miguel (Ericsson) replies to Hucheng and r02
Hucheng (CATT) provides r03 to reflect the request from Miguel (Ericsson).
Miguel (Ericsson) provides r04
Gerald (Nokia): Nokia comments on r04
Miguel (Ericsson) agrees with version r05
Hucheng(CATT) is also fine with r05.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104848 CR Approval 23.288 CR0299R4 (Rel-17, 'F'): Resolve ENs for clause 6.1A.3.2 CATT, Ericsson Rel-17 Revision of S2-2103878r05, merging S2-2104031. Approved Agreed
8.1 S2-2103880 CR Approval 23.502 CR2606R1 (Rel-17, 'B'): Updates to Selection of NWDAF at change of AMF Ericsson Rel-17 Revision of (Postponed) S2-2102186. r02 agreed. Revised to S2-2104849, merging S2-2104519 Malla (NTT DOCOMO) asks for clarification.
Miguel (Ericsson) provides r01 merging S2-2103884
Miguel (Ericsson) corrects previous comment. Miguel (Ericsson) provides r01 merging S2-2104519
Miguel (Ericsson) provides r02
Jungshin (Samsung) is ok with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104849 CR Approval 23.502 CR2606R2 (Rel-17, 'B'): Updates to Selection of NWDAF at change of AMF Ericsson Rel-17 Revision of S2-2103880r02, merging S2-2104519. Approved Agreed
8.1 S2-2103883 CR Approval 23.288 CR0339 (Rel-17, 'B'): NWDAF re-selection for Multiple NWDAF deployments - procedures -update Ericsson Rel-17 Noted Gerald (Nokia): Nokia has comments and proposes to partially merge S2-2104550 and S2-2104275 into this CR. R01 provided.
Xiaoyan (CATT) provides r02.
Malla (NTT DOCOMO) provides comment.
Miguel (Ericsson) provides r03
Gerald (Nokia): Nokia disagrees with r03
Miguel (Ericsson) provides r04
Gerald (Nokia): Nokia disagrees with r04
Miguel (Ericsson) disagrees with r05
Jungshin (Samsung) provides comments and r06.
Gerald (Nokia): Nokia asks for clarification on r09.
Jungshin (Samsung) clarifies to Gerald (Nokia) comments.
Gerald (Nokia): Nokia responds to Samsung
Miguel (Ericsson) disagrees with r05, therefore it also disagrees to r06 which is based on r05.
Jungshin (Samsung) provides clarification.
Jungshin (Samsung) provides r07.
Gerald (Nokia): Nokia clarifies that questions had been against r06 (not r09)
Miguel (Ericsson) provides comments, especially to r07
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r05 and r07; objects all other revisions.
Miguel (Ericsson) objects to r01, r05, r06 and r07
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2103884 CR Approval 23.288 CR0261R1 (Rel-17, 'B'): NWDAF Selection and re-selection for Multiple NWDAF deployments - procedures Ericsson, NTT DOCOMO Rel-17 Revision of (Postponed) S2-2102185. Noted Gerald (Nokia): Nokia disagrees with r00 and proposes to merge the contribution into S2-2104275.
Miguel (Ericsson) responds to Gerald (Nokia) and provides r01
Gerald (Nokia): Nokia responds to Miguel and comments on r01.
Miguel (Ericsson) provides r02
Malla (NTT DOCOMO) provided comment.
Gerald (Nokia): Nokia provides response to Ericsson and DOCOMO
Miguel (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia objects to r03 and earlier versions
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104020 CR Approval 23.288 CR0343 (Rel-17, 'B'): Addition of sets of NWDAF identifiers involved in analytics aggregation InterDigital Rel-17 r02 agreed. Revised to S2-2104850. Miguel (Ericsson) questions the motivation for this CR
Guanzhou (InterDigital) responds to Miguel (Ericsson) comments.
Malla (NTT DOCOMO) provided a comment.
Guanzhou (InterDigital) responds to Malla (NTT DOCOMO) comments.
Gerald (Nokia): Nokia has comments on r00 and provides r01
Leo (Deutsche Telekom) has comments on r01
Gerald (Nokia): Nokia provides r02
Leo (Deutsche Telekom) is fine with r02
==== 8.X, 9.X Revisions Deadline ====
Guanzhou (InterDigital) is fine with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104850 CR Approval 23.288 CR0343R1 (Rel-17, 'B'): Addition of sets of NWDAF identifiers involved in analytics aggregation InterDigital Rel-17 Revision of S2-2104020r02. Approved Agreed
8.1 S2-2104021 CR Approval 23.288 CR0344 (Rel-17, 'B'): Extension of Nnwdaf_AnalyticsSubscription_Transfer service operation for partial transfer InterDigital Rel-17 Noted Miguel (Ericsson) asks questions
Malla (NTT DOCOMO) asks questions
Guanzhou (InterDigital) responds to Miguel(Ericsson) and Malla(NTT DOCOMO)'s comments.
Miguel (Ericsson) has further questions
Malla (NTT DOCOMO) propose to note the CR.
Gerald (Nokia): Nokia shares concerns
Guanzhou (InterDigital) makes further clarification.
Juan Zhang (Qualcomm) shares same concern raised by Ericsson, NTT Docomo and Nokia.
Malla (NTT DOCOMO) objects r00 and propose to note
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia proposes to note
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104031 CR Approval 23.288 CR0299R3 (Rel-17, 'F'): Resolve ENs for clause 6.1A.3.2 CATT Rel-17 Revision of (Agreed) S2-2103250. Confirm CR Revision - CR states 1! Merged into S2-2104848 Miguel (Ericsson) provides comments and proposes merging with S2-2103878
Mehrdad (Samsung) feels this CR is already addressed in S2-2103878 and suggests to merge this into that CR.
Malla (NTT DOCOMO) agree with Mehrdad (Samsung) and Miguel (Ericsson) that this CR overlapped with S2-2103878.
Miguel (Ericsson) provides S2-2103878r01 merging S2-2104031
==== 8.X, 9.X Revisions Deadline ====
Hucheng (CATT) agrees to merge this paper into S2-2103878
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104211 CR Approval 23.288 CR0243R4 (Rel-17, 'B'): Exposing UE mobility analytics for multiple NWDAFs case China Mobile Rel-17 Revision of (Postponed) S2-2102662. Confirm CR Revision - CR states 0! r03 agreed. Revised to S2-2104851. Gerald (Nokia): Nokia comments on original
Aihua (China Mobile) replies and provides r01.
Gerald (Nokia): Nokia comments on r01
Aihua (China Mobile) replies and provides r02.
Leo (Deutsche Telekom) provides comments on r02.
Aihua (China Mobile) replies to Leo (Deutsche Telekom) and provides r03.
Leo (Deutsche Telekom) is fine with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104851 CR Approval 23.288 CR0243R5 (Rel-17, 'B'): Exposing UE mobility analytics for multiple NWDAFs case China Mobile Rel-17 Revision of S2-2104211r03. Approved Agreed
8.1 S2-2104256 CR Approval 23.288 CR0351 (Rel-17, 'B'): Removal of FFS Clause 6.2.2.1 on determining data sources in area of interest Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104852. Miguel (Ericsson) provides comments and asks a question
WangYuan (Huawei) provides clarifications to Ericsson and revision r01.
Malla (NTT DOCOMO) provided comment on r01
WangYuan (Huawei) provides clarifications to DCM and revision r02.
Yannick (Nokia): Nokia provides comments.
Miguel (Ericsson) replies to Yannick (Nokia)
Yannick (Nokia): Nokia provides r03.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) is fine with r03.
Miguel (Ericsson) agrees with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104852 CR Approval 23.288 CR0351R1 (Rel-17, 'B'): Removal of FFS Clause 6.2.2.1 on determining data sources in area of interest Huawei, HiSilicon Rel-17 Revision of S2-2104256r03. Approved Agreed
8.1 S2-2104259 CR Approval 23.288 CR0280R2 (Rel-17, 'F'): Resolving EN on analytics metadata request CATT Rel-17 Revision of (Agreed) S2-2103246. Confirm CR Revision - CR states 0! r01 agreed. Revised to S2-2104853. Gerald (Nokia): Nokia has comments on original
Xiaoyan (CATT) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104853 CR Approval 23.288 CR0280R3 (Rel-17, 'F'): Resolving EN on analytics metadata request CATT Rel-17 Revision of S2-2104259r01. Approved Agreed
8.1 S2-2104275 CR Approval 23.288 CR0281R1 (Rel-17, 'F'): Analytics Subscription Transfer when analytics consumer changes CATT Rel-17 Revision of (Postponed) S2-2102445. Confirm CR Revision - CR states 0! Noted Miguel (Ericsson) provides comments and proposes to merge S2-2104550 into this
Xiaoyan (CATT) provides r01.
Malla (NTT DOCOMO) changes are overlapped with S2-2104550. Ask the authors to work together and propose a merge CR. It is difficult to task multiple overlapping CRs.
Gerald (Nokia): Nokia proposes to merge changes on clause 6.1B into S2-2103883. This is not a complete merge.
Xiaoyan (CATT) provides r02.
Xiaoyan (CATT) provides r03.
Malla (NTT DOCOMO) provides r04.
Xiaoyan (CATT) provides r05.
Miguel (Ericsson) provides r06
Gerald (Nokia): Nokia provides r07
Malla (NTT DOCOMO) comment on r07
Miguel (Ericsson) provides r08
Gerald (Nokia): Nokia comments on r08.
Miguel (Ericsson) replies to Gerald about r08 and provides r09
Gerald (Nokia): Nokia responds to E// and comments on r09.
Miguel (Ericsson) provides r10 and comments
Malla (NTT DOCOMO) provided comments.
Gerald (Nokia): Nokia asks for clarification as both E// and CATT claim to have submitted r10
Jungshin (Samsung) provides comments on changes in r09 and r10.
Gerald (Nokia): Nokia responds to Ericsson and DOCOMO
Xiaoyan (CATT) confirms that r10 is from CATT.
Malla (NTT DOCOMO) responds to Nokia
Gerald (Nokia): Nokia responds to DOCOMO
Gerald (Nokia): Nokia responds to Samsung
Miguel (Ericsson) provides r11
Gerald (Nokia): Nokia comments on r11.
Miguel (Ericsson) replies to Nokia about r011
Gerald (Nokia): Nokia comments on r11 and provides r12
Xiaoyan (CATT) asks for clarification on r12.
Miguel (Ericsson) provides r13
Miguel (Ericsson) replies to Xiaoyan (CATT)
==== 8.X, 9.X Revisions Deadline ====
Miguel (Ericsson) prefers r13, can also live with r06, r08, r09, and r11, and objects to all other versions and the original
Gerald (Nokia): Nokia is okay with r12, can live with r07, objects to original and other revisions. Okay to postpone.
Xiaoyan (CATT) asks Miguel (Ericsson) if it is possible to reconsider r12.
Miguel (Ericsson) requests further explanation on the reasons for objecting to r13
Xiaoyan (CATT) clarifies on 'reselection'/'(re-)selection'.
Gerald (Nokia): Nokia provides further explanation for the objection to r013
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104286 CR Approval 23.288 CR0353 (Rel-17, 'F'): Analytics Subscription Transfer for aggregator NWDAF CATT Rel-17 r07 agreed. Revised to S2-2104854. Gerald (Nokia): Nokia asks for clarification
Xiaoyan (CATT) clarifies and provides r01.
Malla (NTT DOCOMO) provided comment .
Xiaoyan (CATT) replies to Malla (NTT DOCOMO).
Gerald (Nokia): Nokia responds to CATT
Xiaoyan (CATT) provides r02.
Gerald (Nokia): Nokia comments on r02 and provides r03.
Xiaoyan (CATT) provides r04.
Xiaoyan (CATT) provides r05.
Gerald (Nokia): Nokia provides r06.
Xiaoyan (CATT) provides r07.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r07 and likes to co-sign.
Xiaoyan (CATT) thanks Gerald (Nokia) for the support.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104854 CR Approval 23.288 CR0353R1 (Rel-17, 'F'): Analytics Subscription Transfer for aggregator NWDAF CATT Rel-17 Revision of S2-2104286r07. Approved Agreed
8.1 S2-2104287 CR Approval 23.501 CR2912 (Rel-17, 'F'): Clarification on NWDAF serving area CATT Rel-17 Noted Mehrdad (Samsung) comments on the original version
Miguel (Ericsson) provides comments and questions the need of this CR.
Yannick (Nokia): Nokia provides comments, believes the problem is already solved differently at stage 3.
Xiaoyan (CATT) replies to the comments.
Malla (NTT DOCOMO) propose to note.
Yannick (Nokia): Nokia does not see the need for this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104487 CR Approval 23.502 CR2828 (Rel-17, 'F'): NWDAF information for Namf CreateUEContext service Samsung Rel-17 Confirm Spec version used - CR states 17.1.0! Noted Miguel (Ericsson) provides comments and observes the incorrect design base specification
Gerald (Nokia): Nokia points out wrong baseline used for this CR
Gerald (Nokia): Nokia responds to Ericsson's comment
Miguel (Ericsson) provides r01 and replies to Nokia
Gerald (Nokia): Nokia agrees on CR being implemented on wrong baseline version and disagrees with r01
Jungshin (Samsung) agrees to the proposed changes from Gerald (Nokia).
Miguel (Ericsson) indicates that the changes proposed by this CR have been already agreed by CRs 2701 and 2708 (see interim version of 23.502). Therefore, this CR is not needed.
Jungshin (Samsung) requests Miguel (Ericsson) to check again.
Jungshin (Samsung) provides r01.
Gerald (Nokia): Nokia asks for clarification. Was expecting r02.
Jungshin (Samsung) corrects the revision number and provides r02.
==== 8.X, 9.X Revisions Deadline ====
Miguel (Ericsson) proposes to note this CR
==== 8.X, 9.X Final Deadline ====
Jungshin (Samsung) propose to postpone the CR rather than mark it as noted.
Miguel (Ericsson) accepts marking the CR as postponed
Noted
8.1 S2-2104519 CR Approval 23.502 CR2833 (Rel-17, 'C'): NWDAF association information for AMF relocation Samsung Rel-17 Confirm Spec version used - CR states 17.1.0! Merged into S2-2104849 Gerald (Nokia): Nokia has comments and asks for clarification on original
Malla (NTT DOCOMO) changes are overlapped with S2-2103880, propose to merge into S2-2103880.
Miguel (Ericsson) provides a merge of S2-2104519 into S2-2103880r01
Jungshin (Samsung) is ok for the merge.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104550 CR Approval 23.288 CR0358 (Rel-17, 'C'): Analytics subscription transfer when consumer NF changes Samsung Rel-17 Confirm Spec version used - CR states 17.1.0! Merged into S2-2103883 (Noted) and S2-2104275 (Noted) Miguel (Ericsson) provides comments and proposes to merge it into S2-2104275
Gerald (Nokia): Nokia proposes to merge changes on clause 6.1B into S2-2103883. This is not a complete merge.
Antoine (Orange) prefers the approach in S2-2104275 instead of 6.1B.2.2 of this CR.
Gerald (Nokia): Nokia asks for status of this CR
Miguel's (Ericsson) understanding is that the contents of this CR are now merged into S2-2103883 and S2-2104275. Please confirm
Jungshin (Samsung) confirms that the CR is merged to S2-2103883 and S2-2104275.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104552 CR Approval 23.288 CR0359 (Rel-17, 'B'): Update to Contents of Analytics Exposure Samsung, KDDI, AT&T Rel-17 Approved Gerald (Nokia): Nokia comments on original
Mehrdad (Samsung) replies to Nokia
Gerald (Nokia): Nokia responds to Samsung. Can live with r00.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104571 CR Approval 23.288 CR0271R1 (Rel-17, 'B'): Clarification on NWDAF selection without AoI NTT DOCOMO Rel-17 Revision of (Postponed) S2-2102300. Merged into S2-2104846 Mehrdad (Samsung) suggests to merge 3830, 3882, 4571 together and adopt one as the baseline.
Miguel (Ericsson) provides comments and suggests to merge S2-2103830, S2-21-3882, and S2-2104571
Miguel (Ericsson) provides S2-2103882r01 merging S2-2104571, S2-2103830 and S2-2103882
Malla (NTT DOCOMO) is fine to merge into S2-2103882, discussing on single CR can save our time.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104627 CR Approval 23.502 CR2851 (Rel-17, 'B'): Update to NRF service - NWDAF registration and discovery Intel Rel-17 CC#5: r03 + changes agreed. Revised to S2-2105195, merging S2-2103243, S2-2103274 and S2-2104627. Gerald (Nokia): Nokia has comments on original
WangYuan (Huawei): Huawei has further comments.
Megha(Intel) provides r01 and comments.
Gerald (Nokia): Nokia has comments on r00 and r01
Megha(Intel) provides r02.
Gerald (Nokia): Nokia provides r03
Malla (NTT DOCOMO) provided comments
Gerald (Nokia): Nokia replies to DOCOMO
Gerald (Nokia): Nokia provides r04
Leo (Deutsche Telekom) proposes a correction
Gerald (Nokia): Nokia provides r05 correcting a typo
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is fine with r05.
Miguel (Ericsson) objects to revisions r04 and r05
Gerald (Nokia): Nokia is okay to go with r03 and resolve the other issues in next meeting. Revision is required as indicated by Maurice.
Megha (Intel) is okay to go with r03.
Leo (Deutsche Telekom) comments on r03.
Megha (Intel) provides post deadline r06 for CC#4
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2105195 CR Approval 23.502 CR2851R1 (Rel-17, 'B'): Update to NRF service - NWDAF registration and discovery Intel Rel-17 Revision of S2-2104627r03 + changes, merging S2-2103243, S2-2103274 and S2-2104696. Approved Agreed
8.1 S2-2104696 CR Approval 23.288 CR0367 (Rel-17, 'B'): Analytics aggregation - resolve EN Nokia, Nokia Shanghai Bell Rel-17 Confirm Specification Number - CR states 23.502! Merged into S2-2105195 Megha(Intel) proposes to merge this document with S2-2104627.
Gerald (Nokia): Nokia is okay to mark this document merged into S2-2104627
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104699 CR Approval 23.288 CR0320R1 (Rel-17, 'C'): Correlation ID for transfer of analytics subscription Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2102802. WITHDRAWN Gerald (Nokia): Nokia withdraws 4699; we don't see the need to change agreed S2-2102802.
==== 8.X, 9.X Revisions Deadline ====
Withdrawn
8.1 S2-2104700 CR Approval 23.288 CR0300R2 (Rel-17, 'F'): Data collection within AoI for specific UEs CATT, Nokia Rel-17 Revision of (Agreed) S2-2103251. r01 agreed. Revised to S2-2104856. Miguel (Ericsson) asks questions and provides comments
Gerald (Nokia): Nokia responds to Ericsson.
Malla (NTT DOCOMO) asks for clarification.
Hucheng (CATT) replies to the comments on query UDM with group ID.
Miguel (Ericsson) provides r01
Hucheng (CATT) comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104856 CR Approval 23.288 CR0300R3 (Rel-17, 'F'): Data collection within AoI for specific UEs CATT, Nokia Rel-17 Revision of S2-2104700r01. Approved Agreed
8.1 S2-2104769 CR Approval 23.288 CR0376 (Rel-17, 'F'): Subscription ID alignment Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Gerald (Nokia): Nokia withdraws 4769.
==== 8.X, 9.X Revisions Deadline ====
Withdrawn
8.1 - - - KI#4 - - Docs:=4 -
8.1 S2-2104170 CR Approval 23.288 CR0348 (Rel-17, 'F'): Update to slice load analytics procedure Samsung Rel-17 r03 agreed. Revised to S2-2104857. Belen (Ericsson) provides comments.
David (Samsung) provides r01.
Malla (NTT DOCOMO) asks for clarification.
David (Samsung) replies to NTT DOCOMO.
Yannick (Nokia): Nokia provides r02 and a question or clarification.
David (Samsung) replies to Nokia.
Yannick (Nokia): Nokia thanks Samsung for the clarification and request a revision.
David (Samsung) provides r03.
Yannick (Nokia): Nokia is fine with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104857 CR Approval 23.288 CR0348R1 (Rel-17, 'F'): Update to slice load analytics procedure Samsung Rel-17 Revision of S2-2104170r03. Approved Agreed
8.1 S2-2104213 CR Approval 23.288 CR0349 (Rel-17, 'C'): SMF event exposure updates Samsung Rel-17 Confirm Specification Number - CR states 23.502! r01 agreed. Revised (as CR to 23.502) to S2-2104858. Belen (Ericsson) asks questions
David (Samsung) replies to Ericsson.
Yannick (Nokia): Nokia requests for clarification.
David (Samsung) replies to Nokia.
Malla (NTT DOCOMO) agrees with Nokia's proposal.
David (Samsung) provides r01.
Yannick (Nokia): Nokia is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104858 CR Approval 23.502 CR2880 (Rel-17, 'C'): SMF event exposure updates Samsung Rel-17 Revision of S2-2104213r01. Approved Agreed
8.1 - - - KI#7 - - Docs:=2 -
8.1 S2-2104697 CR Approval 23.288 CR0326R2 (Rel-17, 'B'): User Data Congestion Analytics Update Nokia Rel-17 Revision of (Agreed) S2-2103260. r04 agreed. Revised to S2-2104859. Malla (NTT DOCOMO) asks for clarification.
Gerald (Nokia): Nokia responds to NTT DOCOMO
Malla (NTT DOCOMO) is fine with r00
Belen (Ericsson) provides r01, and adds Ericsson as source, since it is a revision of Ericsson CR
Gerald (Nokia): Nokia responds to Ericsson and provides r02
Belen (Ericsson) apologies for the mistake and provide r03
Zhuoyi (China Telecom) provide comments.
Gerald (Nokia): Nokia responds to Ericsson and China Telecom
Gerald (Nokia): Nokia provides r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104859 CR Approval 23.288 CR0326R3 (Rel-17, 'B'): User Data Congestion Analytics Update Nokia Rel-17 Revision of S2-2104697r04. Approved Agreed
8.1 - - - KI#8 - - Docs:=25 -
8.1 S2-2103815 CR Approval 23.288 CR0336 (Rel-17, 'B'): Data collection from UE Application Ericsson Rel-17 Confirm CR Number - CR states 0335! r05 agreed. Revised to S2-2104860. Juan Zhang (Qualcomm) provides comments
Yannick (Nokia): Nokia provides comments.
Belen (Ericsson) replies to Nokia and QC
Juan Zhang (Qualcomm) provides r01
Belen (Ericsson) provides r02.
Yannick (Nokia): Nokia provides r03.
Mehrdad (Samsung) provides r04
Belen (Ericsson) provides r05
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104860 CR Approval 23.288 CR0336R1 (Rel-17, 'B'): Data collection from UE Application Ericsson Rel-17 Revision of S2-2103815r05. Approved Agreed
8.1 S2-2103816 CR Approval 23.288 CR0337 (Rel-17, 'B'): Mapping UE IP address and GPSI Ericsson Rel-17 r09 agreed. Revised to S2-2104861. Juan Zhang (Qualcomm) provides comments
Yannick (Nokia): Nokia provides comments.
Wang Yuan (Huawei) asks for clarifications on providing multiple IP addresses to untrusted AF.
Belen (Ericsson) provides r01
Yannick (Nokia): Nokia replies to Ericsson.
Juan Zhang (Qualcomm) provides r02
Yannick (Nokia): Nokia provides r02 and asks to clarify text added by Qualcomm on how to to determine the PDU session for data collection.
Andy (VC, Samsung) comments that Yannick provided r03, not r02.
Yang (OPPO) raises a question of condition to trigger NWDAF or AF based mapping procedure, and also question for r2/3.
Juan Zhang (Qualcomm) replies comments to Nokia and OPPO.
Yang (OPPO) also think the sentence is unclear and provides r04.
Juan Zhang (Qualcomm) replies to Yannick
Juan Zhang (Qualcomm) provides r05 and replies to Yang (OPPO)
Yan (OPPO) replies to Juan
Yannick (Nokia): Nokia requests for clarification.
Belen (Ericsson) provides r06.
Belen (Ericsson) asks for clarifications
Juan Zhang (Qualcomm) replies to Belen.
Yang Xu (OPPO) tend to agree with Juan to add an EN based on r06
Belen (Ericsson) provides r07
Juan Zhang (Qualcomm) provides r08.
Yannick (Nokia): Nokia provides r09.
Yang (OPPO) provides r09
Yannick (Nokia): Nokia confirms that r09 was already provided by Nokia.
Yang (OPPO) confirms this coincidence and ok to r09
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r09.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104861 CR Approval 23.288 CR0337R1 (Rel-17, 'B'): Mapping UE IP address and GPSI Ericsson Rel-17 Revision of S2-2103816r09. Approved Agreed
8.1 S2-2104023 CR Approval 23.501 CR2881 (Rel-17, 'B'): KI#8 - AF discovery and selection Ericsson Rel-17 r02 agreed. Revised to S2-2104862. Mehrdad (Samsung) provides r01
Yannick (Nokia): Nokia provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104862 CR Approval 23.501 CR2881R1 (Rel-17, 'B'): KI#8 - AF discovery and selection Ericsson Rel-17 Revision of S2-2104023r02. Approved Agreed
8.1 S2-2104168 CR Approval 23.288 CR0318R2 (Rel-17, 'B'): Update to NF Load Analytics Samsung Rel-17 Revision of (Agreed) S2-2103266. r04 agreed. Revised to S2-2104863, merging S2-2104524 Yannick (Nokia): Nokia provides suggestion for rewording. Also notices that there is an alternative proposal on the same text for event filter information for data processing, from Qualcomm, in S2-2104524.
Mehrdad (Samsung) replies to Nokia.
Juan Zhang (Qualcomm) provides comments
Mehrdad (Samsung) provides r01 based on the agreed wording for this CR and merges 4524 into this CR.
Juan Zhang (Qualcomm) provides r02.
Yannick (Nokia): Nokia requests for clarification.
Juan Zhang (Qualcomm) askes for clarification.
Mehrdad (Samsung) replies to Qualcomm.
Juan Zhang (Qualcomm) replies to Samsung.
Yannick (Nokia): Nokia is fine with Samsung's proposal for NOTE 4 amendments.
Mehrdad (Samsung) provides r03 based on the agreed wording for NOTE 4.
Yannick (Nokia): Nokia provides r04.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) supports r04.
Mehrdad (Samsung) is OK with r04
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104863 CR Approval 23.288 CR0318R4 (Rel-17, 'B'): Update to NF Load Analytics Samsung Rel-17 Revision of S2-2104168r04, merging S2-2104524. Approved Agreed
8.1 S2-2104370 CR Approval 23.288 CR0330R2 (Rel-17, 'B'): Extension of Naf_EventExposure for observed service experience data collection from UEs InterDigital Rel-17 Revision of (Agreed) S2-2103267. Noted Guanzhou (InterDigital) provides r01 to incorporate the changes proposed in 4496, and indicate that 4496 should be kept open for separate discussion.
Yannick (Nokia): Nokia requests for clarification.
Juan Zhang (Qualcomm) provides comments
Guanzhou (InterDigital) responds to Yannick(Nokia) and Juan(Qualcomm)'s comments.
Guanzhou (InterDigital) responds to Juan(Qualcomm)'s comments.
Belen (Ericsson) provides comments
Guanzhou (InterDigital) responds to Yannick's questions.
Guanzhou (InterDigital) responds to Belen (Ericsson) comments.
Zhuoyi (China Telecom) provides comments.
Yannick (Nokia): Nokia requests further clarifications.
Juan Zhang (Qualcomm) shares same view with Yannick.
==== 8.X, 9.X Revisions Deadline ====
Guanzhou (InterDigital) responds comments.
Juan Zhang (Qualcomm) proposes to note the CR
Yannick (Nokia): Nokia prefers to note this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104495 LS OUT Approval [DRAFT] Reply LS to SA WG4 on UE Data Collection Qualcomm CDMA Technologies Rel-17 Response to S2-2103740. r08 agreed. Revised to S2-2104864. Wang Yuan (Huawei) provides r01.
Yannick (Nokia): Nokia provides r02.
Juan Zhang (Qualcomm) provides r03.
Mehrdad (Samsung) provides r04.
Wang Yuan (Huawei) provides r05.
Juan Zhang (Qualcomm) provides r06
Belen (Ericsson) provides r07.
Wang Yuan (Huawei) can accept r06, but cannot agree r07.
Mehrdad (Samsung) clarifies for Huawei
Belen (Ericsson) objects to r06.
Juan Zhang (Qualcomm) support Samsung and Ericsson's comments
Wang Yuan (Huawei) provides r08.
Belen (Ericsson) objects to r08 and r06, it is okay with other revisions.
Juan Zhang (Qualcomm) provides to go with r07.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) cannot agree with r07 and suggests to discuss this on CC#4.
Mehrdad (Samsung) clarifies to Huawei that nothing has changed regarding the scope of the study in SA2.
Juan Zhang (Qualcomm) replies to HW.
Wang Yuan (Huawei) is still not convinced. We don't understand why it is essential to keep this LS secret from SA6 .
Belen (Ericsson) replies to Huawei that LSs, and CRs are public documents.
Propose to add in the LS the statement proposed by QC: 'SA4 focus on the protocol between UE and AF for data collection' that can be used to collect any 3GPP or non 3GPP application data
Juan Zhang (Qualcomm) replies to Wang Yuan (Huawei)
Wang Yuan (Huawei) replies to Ericsson.
Juan Zhang (Qualcomm) replies to Huawei
Belen (Ericsson) asks Huawei if he would be okay with proposed text?
Wang Yuan (Huawei) maintains the objections to all the revision without SA6 in CC and would like to raise this to CC#4
Juan Zhang (Qualcomm): as a compromise, we propose to approve R08.
Belen (Ericsson) is okay with the compromise proposal to approve r08.
Xiaobo(vivo) propose to go with r08 as compromise and make progress.
Wang Yuan (Huawei) confirms that r08 is fine.
Mehrdad (Samsung) can also live with r08 as a compromise.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104864 LS OUT Approval Reply LS to SA WG4 on UE Data Collection SA WG2 Rel-17 Revision of S2-2104495r08. Approved Approved
8.1 S2-2104496 CR Approval 23.288 CR0330R3 (Rel-17, 'B'): Extension of Naf_EventExposure for observed service experience data collection from UEs Qualcomm Incorporated Rel-17 Revision of (Agreed) S2-2103267. Approved Yannick (Nokia): Nokia notes this proposal overlaps with other proposal in S2-2104370.
Juan Zhang (Qualcomm) replies to Yannick.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r00.
Yannick (Nokia): Nokia is fine with r00.
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104524 CR Approval 23.288 CR0318R3 (Rel-17, 'B'): Update to NF Load Analytics Qualcomm Incorporated Rel-17 Revision of (Agreed) S2-2103266. Merged into S2-2104863 Yannick (Nokia): Nokia requests for clarification. Also notices that there is an alternative proposal on the same text for event filter information for data processing, from Samsung, in S2-2104168.
Mehrdad (Samsung) suggests to mark this PCR merged into S2-2104168 and clarify the rest in S2-2104577.
Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) replies to Yannick
Juan Zhang (Qualcomm) replies to Mehrdad (Samsung)
Mehrdad (Samsung) replies to Qualcomm and proposes a way forward
Mehrdad (Samsung) clarifies on the suggested wording.
Juan Zhang (Qualcomm) is fine with Samsung's way forward.
Yannick (Nokia): Nokia is fine with way forward proposal from Samsung.
Mehrdad (Samsung) requests to mark this CR as merged into S2-2104168r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104529 CR Approval 23.288 CR0356 (Rel-17, 'B'): Analytics request to collect data from UE for 'any UE' Qualcomm Incorporated Rel-17 r04 agreed. Revised to S2-2104865. Yannick (Nokia): Nokia provides comments.
Juan Zhang (Qualcomm) replies to Yannick
Yannick (Nokia): Nokia replies to Qualcomm.
Mehrdad (Samsung) provides r01
Mehrdad (Samsung) provides r02.
Antoine (Orange) provides r03.
Juan Zhang (Qualcomm) is fine with r02.
Juan Zhang (Qualcomm) replies to Antoine (Orange) and objects r03.
Belen (Ericsson) provides r04, similar view as Orange too.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r04.
Mehrdad (Samsung) also supports r04 and requests to co-sign the PCR.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104865 CR Approval 23.288 CR0356R1 (Rel-17, 'B'): Analytics request to collect data from UE for 'any UE' Qualcomm Incorporated Rel-17 Revision of S2-2104529r04. Approved Agreed
8.1 S2-2104534 CR Approval 23.288 CR0258R2 (Rel-17, 'B'): KI#8 - Resolving Editor´s note on mapping UE IP address and SUPI or GPSI Qualcomm Incorporated Rel-17 Revision of (Agreed) S2-2103261. r07 agreed. Revised to S2-2104866, merging S2-2104744 Yang (OPPO) provides comments and suggestions
Juan Zhang (Qualcomm) replies to Yang and provides r01.
Yang (OPPO) asks a question for alrification
Yang (OPPO) asks a question for clarification
Belen (Ericsson) provides r02 and comments that this is a revision of an Ericsson CR.
Juan Zhang (Qualcomm) replies to OPPO
Juan Zhang (Qualcomm) replies to Belen (Ericsson)
Yang (OPPO) concerns r1 and r2 as my previous comments and provides r03
Juan Zhang (Qualcomm) provides r04
Belen (Ericsson) asks to align both this CR and S2-2103816 given that it is a similar solution
Juan Zhang (Qualcomm) uploads r05.
Yannick (Nokia): Nokia provides r06.
Juan Zhang (Qualcomm) is fine with r06 and thanks for the co-source.
Yang (OPPO) comments and provides r07.
Juan Zhang (Qualcomm) is OK with r07.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r07 which is the latest version.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104866 CR Approval 23.288 CR0258R3 (Rel-17, 'B'): KI#8 - Resolving Editor´s note on mapping UE IP address and SUPI or GPSI Qualcomm Incorporated Rel-17 Revision of S2-2104534r07, merging S2-2104744. Approved Agreed
8.1 S2-2104560 CR Approval 23.288 CR0360 (Rel-17, 'B'): Update to NF Load Analytics Output data Samsung Rel-17 r01 agreed. Revised to S2-2104867. Antoine (Orange) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104867 CR Approval 23.288 CR0360R1 (Rel-17, 'B'): Update to NF Load Analytics Output data Samsung Rel-17 Revision of S2-2104560r01. Approved Agreed
8.1 S2-2104577 CR Approval 23.288 CR0361 (Rel-17, 'B'): Update to UE Data Collection Samsung Rel-17 r03 agreed. Revised to S2-2104868. Yang (OPPO) provides questions for clarification
Mehrdad (Samsung) replies to OPPO
Yannick (Nokia): Nokia provides r01.
Juan Zhang (Qualcomm) provides comments
Mehrdad (Samsung) replies to Nokia.
Mehrdad (Samsung) clarifies on the suggested wording.
Juan Zhang (Qualcomm) is fine with the following proposal
Mehrdad (Samsung) provides r01 based on the agreed wording for this CR.
Mehrdad (Samsung) provides r02 based on the agreed wording for this CR.
Belen (Ericsson) asks to upate the cover page too.
Mehrdad (Samsung) provides r03 and replies to Ericsson.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104868 CR Approval 23.288 CR0361R1 (Rel-17, 'B'): Update to UE Data Collection Samsung Rel-17 Revision of S2-2104577r03. Approved Agreed
8.1 S2-2104744 CR Approval 23.288 CR0373 (Rel-17, 'B'): Procedure for NWDAF collecting mapping information Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2104866 Yannick (Nokia): Our proposal is also covered by Qualcomm in S2- S2-2104534 with procedure for NWDAF correlates UE data collection and NWDAF request. We suggest to focus discussion on Qualcomm CR in S2-2104534 and we are fine to merge our S2-2104744 into S2-2104534.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104745 CR Approval 23.502 CR2874 (Rel-17, 'B'): UE IP address usage in Naf_EventExposure service Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2104869. Belen (Ericsson) provides r01
Yannick (Nokia): Nokia agrees with Ericsson and is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104869 CR Approval 23.502 CR2874R1 (Rel-17, 'B'): UE IP address usage in Naf_EventExposure service Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104745r01. Approved Agreed
8.1 S2-2103740 LS In Action LS from SA WG4: Reply LS to SA2 on UE Data Collection SA WG4 (S4-210644) Response drafted in S2-2104495. Final response in S2-2104864 Juan Zhang (Qualcomm) proposes to note the incoming LS.
Yannick (Nokia): Nokia understands disposition for this incoming LS is dependent on disposition of draft reply in S2-2104495
Replied to
8.1 - - - KI#9 - - Docs:=7 -
8.1 S2-2103925 CR Approval 23.288 CR0342 (Rel-17, 'B'): Dispersion Analytics and DN Performance Analytics to Table 7.1-2 LG Electronics, Ericsson, Lenovo, Motorola Mobility, Spirent, Samsung, vivo Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104075 CR Approval 23.288 CR0345 (Rel-17, 'F'): Dispersion Analytics: Various corrections and clarifications Spirent Communications Rel-17 Confirm Spec version used - CR states 17.1.0! Merged into S2-2104870 David (Samsung) provides a comment.
Gerald (Nokia): Nokia proposes to merge S2-2104075 into S2-2104698
Peretz (Spirent) agrees to Nokia's proposal to merge S2-2104075 (Spirent's paper) and S2-2104084 (Huawei's paper) into S2-2104698 (Nokia's paper).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104076 CR Approval 23.288 CR0346 (Rel-17, 'B'): Correlation of information between AMF and UPF Spirent Rel-17 Confirm Spec version used - CR states 17.1.0! Noted Peretz (Spirent) provides r01.
Gerald (Nokia): Nokia asks for clarification
Belen (Ericsson) asks the same question
Peretz (Spirent) answers Gerald
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia comments that Spirent preferred to withdraw/note the CR.
Peretz (Spirent) confirms Gerald's (Nokia) note.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104084 CR Approval 23.288 CR0293R2 (Rel-17, 'B'): Add bandwidth into Dispersion analytics per slice Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103271. CC#5: r15 + changes agreed. Revised to S2-2105196. Gerald (Nokia): Nokia has comments and proposes to merge this CR into S2-2104698
Susan (Huawei) replies to Gerald and provides r01.
Gerald (Nokia): Nokia responds to Huawei
Belen (Ericsson) comments.
Peretz (Spirent) object to S2-2104084r01 and provides a merged paper adding the bandwidth analytics content from 2104084.
Susan (Huawei) responds.
Susan (Huawei) provides r02.
Jinhua(Xiaomi) provide comments and r03.
Belen (Ericsson) aks a question on the need for the Applixatin Id
Susan replies to Belen (Ericsson) and provides r04.
Peretz (Spirent) provides r02, a merged paper adding the bandwidth analytics content from 2104084.
Peretz (Spirent) asks the same question. No need for the Application Id
Peretz (Spirent) asking Xiaomi to clarify
Jinhua(Xiaomi) response to Peretz (Spirent)
Peretz (Spirent) provides S2-2104698r02, an alternate merged paper adding the bandwidth analytics content of 2104084.
Gerald (Nokia): Nokia provides r05
Gerald (Nokia): Nokia provides r06. R06 is complementing S2-2104698r04 or is an alternative to S2-2104698r03.
Peretz (Spirent) provides r06
Gerald (Nokia): Nokia provides r07
Peretz (Spirent) asking Gerald for clarifications
Peretz (Spirent) provides r08
Gerald (Nokia): Nokia comments on r08.
Susan (Huawei) replies to Peretz and Gerald, and provides r09.
Jinhua(Xiaomi) replies to Susan(Huawei), with r10 provided.
Belen (Ericsson) provides r11.
Gerald (Nokia): Nokia comments on 4084 and/or 4698 and provides comments on r09
Jinhua(Xiaomi) response to Gerald (Nokia)
Jinhua(Xiaomi) response to Belen (Ericsson) , fine with r11.
Gerald (Nokia): Nokia provides r12
Gerald (Nokia): Nokia comments on 4084r12
Belen (Ericsson) prefers r12
Peretz (Spirent) is fine with r10.
Susan (Huawei) provides r14.
Peretz (Spirent) replies to Gerald
Jinhua(Xiaomi) provides r15.
Gerald (Nokia): Nokia comments on r14/r15
Gerald (Nokia): Nokia replies to Spirent
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) replies to Gerald (Nokia) and provides r16.
Susan (Huawei) provides r17 and asks for CC#4 discussion.
Gerald (Nokia): Nokia is okay with r05, r07, r12, r13. Okay with draft r16/r17 (after deadline).
Peretz (Spirent): Spirent is okay with draft r17 (after deadline).
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2105196 CR Approval 23.288 CR0293R4 (Rel-17, 'B'): Add bandwidth into Dispersion analytics per slice Huawei, HiSilicon Rel-17 Revision of S2-2104084r15 + changes. Approved Agreed
8.1 S2-2104698 CR Approval 23.288 CR0368 (Rel-17, 'F'): Dispersion analytics update Nokia, Nokia Shanghai Bell Rel-17 r07 agreed. Revised to S2-2104870, merging S2-2104075 Susan (Huawei) raises comments regarding removal of any UE and provides r01.
Gerald (Nokia): Nokia responds to Huawei
Susan (Huawei) responds to Gerald.
Peretz (Spirent) provides r01
Gerald (Nokia): Nokia comments on r01
Peretz (Spirent) replies to Gerald
Peretz (Spirent) replies to Gerald with S2-2104698r02
Gerald (Nokia): Nokia provides r03 (alternative to S2-2104084) and r04 (complementing to S2-2104084)
Peretz (Spirent) provides 2104698r05
Peretz (Spirent) replies to Gerald. We can accept 4698r03 with (0..max) applied to Application ID
Gerald (Nokia): Nokia comments on r05 and asks for clarification
Susan (Huawei) provides r06.
Gerald (Nokia): Nokia comments on r05/r06 and provides r07
Susan (Huawei) replies to Gerald.
Peretz (Spirent) provides r08
Gerald (Nokia): Nokia comments on r08
==== 8.X, 9.X Revisions Deadline ====
Peretz (Spirent) provides r09
Gerald (Nokia): Nokia is okay with r00, r04, r07 (r07 is preferred), objects to other revisions.
Peretz (Spirent): Spirent is okay with r07.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104870 CR Approval 23.288 CR0368R1 (Rel-17, 'F'): Dispersion analytics update Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104698r07, merging S2-2104075. Approved Agreed
8.1 - - - KI#10 - - Docs:=2 -
8.1 S2-2104633 CR Approval 23.288 CR0366 (Rel-17, 'F'): Correction to UE communication analytics for PDU session inactivity timer Intel Rel-17 r01 agreed. Revised to S2-2104871. Yannick (Nokia): Nokia agrees with the change, requests that the CR is limited to the only clause which is modified.
Megha(Intel) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104871 CR Approval 23.288 CR0366R1 (Rel-17, 'F'): Correction to UE communication analytics for PDU session inactivity timer Intel Rel-17 Revision of S2-2104633r01. Approved Agreed
8.1 - - - KI#11 - - Docs:=25 -
8.1 S2-2103874 CR Approval 23.501 CR2703R1 (Rel-17, 'B'): NWDAF and DCCF Discovery based on NF ID Ericsson, ETRI Rel-17 Revision of (Merged into S2-2103065, agreed) S2-2102182. Noted Yannick (Nokia): Nokia provides comments and expresses concerns on the proposal.
Yannick (Nokia): Nokia cannot accept the proposal.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2103875 CR Approval 23.288 CR0289R2 (Rel-17, 'B'): Removal of EN related to network slice association information in TS 23.288. Huawei, HiSilicon, Ericsson Rel-17 Revision of (Agreed) S2-2103063. Approved Yannick (Nokia): Nokia provides r01.
Wang Yuan (Huawei) rejects r01 and provides explanations and revision r02.
==== 8.X, 9.X Revisions Deadline ====
Yannick (Nokia): Nokia objects to r02.
Wang Yuan (Huawei) provides clarifications.
Yannick (Nokia): Nokia suggests to approve r00 in this meeting.
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2103882 CR Approval 23.288 CR0260R1 (Rel-17, 'B'): Updating clause 5.2 for the discovery of NWDAFs Ericsson Rel-17 Revision of (Postponed) S2-2102184. r12 agreed. Revised to S2-2104846, merging S2-2103830 and S2-2104571 Mehrdad (Samsung) suggests to merge 3830, 3882, 4571 together and adopt one as the baseline.
Miguel (Ericsson) provides S2-2103882r01 merging S2-2103882, S2-2104571 and S2-2103830,
Malla (NTT DOCOMO) provides r02,
Miguel (Ericsson) replies to Malla (NTT DOCOMO)
Hucheng (CATT) comments and provides r03.
Miguel (Ericsson) replies to Hucheng (CATT) and Malla (NTT DOCOMO) and provides r04
Hucheng (CATT) provides r05 and adds CATT as a supporting company.
Malla (NTT DOCOMO) provides r06.
Miguel (Ericsson) provides comments to r05/r06
Gerald (Nokia): Nokia comments on r06 and provides r07
Miguel (Ericsson) provides r08
Gerald (Nokia): Nokia provides r09
Miguel (Ericsson) provides r10
Gerald (Nokia): Nokia comments on r10 and provides r11
Miguel (Ericsson) provides r12
==== 8.X, 9.X Revisions Deadline ====
Hucheng (CATT) supports r12
Gerald (Nokia): Nokia can live with r12
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104846 CR Approval 23.288 CR0260R2 (Rel-17, 'B'): Updating clause 5.2 for the discovery of NWDAFs Ericsson Rel-17 Revision of S2-2103882r12, merging S2-2103830, merging S2-2103830 and S2-2104571. Approved Agreed
8.1 S2-2103914 CR Approval 23.288 CR0340 (Rel-17, 'B'): Different deployment options for NWDAFs Ericsson, NTT DOCOMO Rel-17 Noted Aihua (China Mobile) suggests to postpone the discussion on NWDAF deployment options to R18.
Miguel (Ericsson) replies to China Mobile
Gerald (Nokia): Nokia comments on original and supports to postpone.
Miguel (Ericsson) provides initial comments to Gerald
Malla (NTT DOCOMO) support the CR to document in Annex
Miguel (Ericsson) responds to Gerald and Malla and provides r01
Xiaobo (vivo) suggests way forward and proposes to continue discussion in R17 and further study it in R18.
Miguel (Ericsson) agrees with Xiaobo (vivo) on the proposed way forward
Gerald (Nokia): Nokia provides r02
Miguel (Ericsson) provides r03
Gerald (Nokia): Nokia comments on r03 and responds to Miguel (Ericsson).
Miguel (Ericsson) provides r04
Gerald (Nokia): Nokia responds to Ericsson, comments on r04, and has sustained concerns with the CR.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia proposes to NOTE and postpone discussion to Rel-18.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104077 CR Approval 23.288 CR0347 (Rel-17, 'D'): Historical Data and Analytics storage text improvement Spirent Rel-17 Confirm Spec version used - CR states 17.1.0! Merged into S2-2104876 Peretz (Spirent) provides r01.
Aihua (China Mobile) proposes to merge S2-2104077 into S2-2104740.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104165 CR Approval 23.288 CR0314R2 (Rel-17, 'B'): Historical Data and Analytics storage China Mobile Rel-17 Revision of (Agreed) S2-2103286. Confirm CR Revision - CR states -1! Merged into S2-2104876 Yannick (Nokia): Nokia provides comments on original version. Nokia sees some aspects from the proposal could be merged with Nokia proposal in S2-2104740.
Malla (NTT DOCOMO) asks for clarification.
Aihua (China Mobile): China Mobile provides r01 and replies comments.
Yannick (Nokia): Nokia replies to China Mobile.
Aihua (China Mobile): China Mobile provides r02 and replies comments.
Malla (NTT DOCOMO) comment on r02.
Aihua (China Mobile): China Mobile replies comments and provides r03.
Yannick (Nokia): Nokia comments on r03.
Antoine (Orange) questions how this increases the efficiency of data collection, and whether this is based on the TR conclusion.
Aihua (China Mobile): China Mobile replies to Nokia.
Peretz (Spirent) asking Nokia for clarification.
Yannick (Nokia): Nokia replies to Spirent.
Peretz (Spirent) accepts Yannick's explanation.
Zhuoyi (China Telecom): China Telecom provides comments.
Aihua (China Mobile): China Mobile suggests to merge S2-2104165 into S2-2104740.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.1 S2-2104167 CR Approval 23.288 CR0308R2 (Rel-17, 'B'): DCCF services definition Nokia, Nokia Shanghai Bell, [China Mobile] Rel-17 Revision of (Agreed) S2-2103284. Confirm CR Revision - CR states -1! r01 agreed. Revised to S2-2104872. Yannick (Nokia): Nokia is fine with the CR, but requests that a revision is provided with rev number being 2 on the coversheet.
Aihua (China Mobile) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104872 CR Approval 23.288 CR0308R3 (Rel-17, 'B'): DCCF services definition Nokia, Nokia Shanghai Bell, [China Mobile] Rel-17 Revision of S2-2104167r01. Approved Agreed
8.1 S2-2104285 CR Approval 23.288 CR0352 (Rel-17, 'F'): Clarification on data storage in ADRF CATT Rel-17 r01 agreed. Revised to S2-2104873. Yannick (Nokia): Nokia provides r01.
Miguel (Ericsson) ask a question about r01
Xiaoyan (CATT) replies to Miguel (Ericsson).
Yannick (Nokia): Nokia replies to Ericsson, agrees with CATT.
Miguel (Ericsson) acknowledges Xiaoyan (CATT)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104873 CR Approval 23.288 CR0352R1 (Rel-17, 'F'): Clarification on data storage in ADRF CATT Rel-17 Revision of S2-2104285r01. Approved Agreed
8.1 S2-2104419 CR Approval 23.288 CR0286R3 (Rel-17, 'F'): Removing EN on bulked data definitions and procedures. Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103278. r04 agreed. Revised to S2-2104874. WangYuan (Huawei) provides revision r01 with minor editorial changes.
Yannick (Nokia): Nokia provides r02.
WangYuan (Huawei) provides revision r03.
Yannick (Nokia): Nokia replies to Huawei.
WangYuan (Huawei) provides revision r04 to address Nokia's comments.
WangYuan (Huawei) provides another possibility for way forward with revision r05.
==== 8.X, 9.X Revisions Deadline ====
Yannick (Nokia): Nokia prefers to go with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104874 CR Approval 23.288 CR0286R4 (Rel-17, 'F'): Removing EN on bulked data definitions and procedures. Huawei, HiSilicon Rel-17 Revision of S2-2104419r04. Approved Agreed
8.1 S2-2104735 CR Approval 23.501 CR2981 (Rel-17, 'B'): Data collection domain for DCCF and NWDAF Nokia, Nokia Shanghai Bell Rel-17 Noted Miguel (Ericsson) asks questions
Malla (NTT DOCOMO) asks questions
Antoine (Orange) expresses concerns with the concept of data collection domain.
Yannick (Nokia): Nokia replies to Orange, NTT DOCOMO and Ericsson.
Miguel (Ericsson) agrees with Orange and coincides with the concerns with the concept of data collection domain
Wang Yuan (Huawei) shares the same concern regarding to the concept of data collection domain and suggests to further study it in R18
==== 8.X, 9.X Revisions Deadline ====
Yannick (Nokia): Nokia replies to Ericsson and Huawei.
Miguel (Ericsson) proposes to note this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104736 CR Approval 23.502 CR2872 (Rel-17, 'B'): Data collection domain for DCCF and NWDAF Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) asks questions
Yannick (Nokia): Nokia replies to NTT DOCOMO.
==== 8.X, 9.X Revisions Deadline ====
Malla (NTT DOCOMO) pointed that this CR is depends on the outcome of the S2-2104735. Nevertheless, as concern to adopt the data collection domain for R-17.
Yannick (Nokia): Nokia confirms this CR is linked with S2-2104735.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104737 CR Approval 23.288 CR0369 (Rel-17, 'B'): Processing and Processing Instructions Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2104875. Miguel (Ericsson) asks questions and provide comments
Yannick (Nokia): Nokia replies to Ericsson.
Miguel (Ericsson) requires further clarifications and provides comments
Yannick (Nokia): Nokia provides r01.
Miguel (Ericsson) indicates that revision r01 addresses the previous comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104875 CR Approval 23.288 CR0369R1 (Rel-17, 'B'): Processing and Processing Instructions Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104737r01. Approved Agreed
8.1 S2-2104738 CR Approval 23.502 CR2873 (Rel-17, 'F'): Corrections to UE behaviour trends Nokia, Nokia Shanghai Bell, Orange Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104739 CR Approval 23.288 CR0306R2 (Rel-17, 'B'): ADRF functional description Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103283. Approved Miguel (Ericsson) asks questions
Yannick (Nokia): Nokia replies to Ericsson.
Antoine (Orange) questions data collection by ADRF.
Yannick (Nokia): Nokia replies to Orange.
Dimitris (Lenovo) shares the same view with Yannick (Nokia)
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) asks how to ensure that subscriptions made by ADRF to collect data will not continue indefinitely e.g. if the NF that triggered this subscription is taken out of service.
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104740 CR Approval 23.288 CR0370 (Rel-17, 'B'): Analytics Data Repository procedures and Historical Data Handling procedure Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2104876, merging S2-2104077 and S2-2104165 Aihua (China Mobile): China Mobile suggests to merge S2-2104165 and S2-2104077 into this CR(S2-2104740) and provides r01.
Yannick (Nokia): Nokia replies to China Mobile, provides r02 and asks for clarification.
Yannick (Nokia): Nokia provides r03.
Aihua (China Mobile) accepts with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104876 CR Approval 23.288 CR0370R1 (Rel-17, 'B'): Analytics Data Repository procedures and Historical Data Handling procedure Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104740r03, merging S2-2104077 and S2-2104165. Approved. S2-2103286 from S2-144E was marked as revised Agreed
8.1 S2-2104742 CR Approval 23.288 CR0371 (Rel-17, 'B'): Procedure for data removal from ADRF Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104743 CR Approval 23.288 CR0372 (Rel-17, 'F'): Alignment with ADRF functional description and ADRF service operations Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.1 S2-2104746 CR Approval 23.288 CR0374 (Rel-17, 'B'): Procedure for Historical Data and Analytics Storage via Notifications Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2104877. Aihua (China Mobile): China Mobile provides comments and provides r01 .
Yannick (Nokia): Nokia provides r02.
Aihua (China Mobile): China Mobile replies to Nokia.
Aihua (China Mobile) accepts r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104877 CR Approval 23.288 CR0374R1 (Rel-17, 'B'): Procedure for Historical Data and Analytics Storage via Notifications Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104746r02. Approved Agreed
8.1 - - - KI#12 - - Docs:=4 -
8.1 S2-2103819 CR Approval 23.288 CR0276R2 (Rel-17, 'B'): Service Experience Analytics outputs RAT Type and Frequency information China Telecom, Ericsson Rel-17 Revision of (Agreed) S2-2103290. WITHDRAWN Yannick (Nokia): Nokia requests for clarification on whether this CR is same as CR from China Telecom in S2-2103937. If so, can we focus on just one CR? Also, Nokia requests for clarification on the change related to local configuration on supported frequencies per cell.
Belen (Ericsson) replies to Nokia
Yannick (Nokia): Nokia replies to Ericsson.
Belen (Ericsson) withdraw this contribution, and discuss S2-2103937 instead
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Withdrawn
8.1 S2-2103879 CR Approval 23.503 CR0576 (Rel-17, 'B'): Providing information on NWDAF for UE related Analytics to PCF Ericsson Rel-17 r03 agreed. Revised to S2-2104878. Yannick (Nokia): Nokia is fine with the CR, but provides r01 to clarify that this is about NWDAF IDs or Analytics IDs used for the UE.
Belen (Ericsson) provides r02
Yannick (Nokia): Nokia provides one editorial fix in r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104878 CR Approval 23.503 CR0576R1 (Rel-17, 'B'): Providing information on NWDAF for UE related Analytics to PCF Ericsson Rel-17 Revision of S2-2103879r03. Approved Agreed
8.1 S2-2103937 CR Approval 23.288 CR0276R3 (Rel-17, 'B'): Service Experience Analytics outputs RAT Type and Frequency information China Telecom, Ericsson, vivo, Huawei Rel-17 Revision of (Agreed) S2-2103290. Noted Yannick (Nokia): Nokia requests for clarification on whether this CR is same as CR from Ericsson in S2-2103819. If so, can we focus on just one CR? Also, Nokia requests for clarification on the change related to local configuration on supported frequencies per cell.
Zhuoyi (China Telecom): This CR is a revision of CR S2-2103819 with editorial update.
Yannick (Nokia): Nokia replies to China Telecom.
Belen (Ericsson) agrees with Nokia´s view
Zhuoyi (China Telecom) replies to Ericsson and Nokia, and asks for opinion.
Zhuoyi (China Telecom): China Telecom replies to Nokia.
Zhuoyi (China Telecom): China Telecom provides r01.
Yannick (Nokia): Nokia comments on r01.
Zhuoyi (China Telecom): Replies to Nokia.
Belen (Ericsson) comments to r01, proposes eitehr to keep Editor´s note on how the Frequency where the UE is located is obtained, and ask RAN via LS or Conclude that the NWDAF is configuerd with the frequencies per cell, and that the OSE is provides per RAT and candidate frequencies.
Zhuoyi (China Telecom) replies to Ericsson.
Belen (Ericsson) provides r02
Zhuoyi (China Telecom) comments on r02
==== 8.X, 9.X Revisions Deadline ====
Belen (Ericsson) replies to qusetions
Yannick (Nokia): Nokia propose to note this proposal. None of the available version provides full solution.
Belen (Ericsson) is okay to note the CR, and discuss it further
==== 8.X, 9.X Final Deadline ====
Zhuoyi (China Telecom) provides clarification.
Noted
8.1 - - - KI#13 - - Docs:=2 -
8.1 S2-2103930 DISCUSSION Discussion Discussion on NWDAF analytics in AMF Selection for load balancing consideration. China Telecom Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2103933 CR Approval 23.501 CR2871 (Rel-17, 'B'): NWDAF output for AMF (Re)selection China Telecom Rel-17 Noted Yannick (Nokia): Nokia provides comments.
Miguel (Ericsson) provides comments
Mehrdad (Samsung) provides comments
Zhuoyi (China Telecom) replies to previous comments.
Yannick (Nokia): Nokia agrees that Rel-17 is not right time to introduce such functionality which has not been investigated during study phase. We suggest to note the CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 - - - KI#15 - - Docs:=10 -
8.1 S2-2103719 LS In Action LS from SA WG3: Reply-LS on Reply-LS on user consent requirements for analytics SA WG3 (S3-210689) Revision of Postponed S2-2102097 from S2#144E. Response drafted in S2-2104703. CC#5: This was postponed. Postponed
8.1 S2-2104703 LS OUT Approval [DRAFT] Reply-LS on user consent requirements for analytics Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2102829. Response to S2-2103719. CC#5: This was noted. Malla (NTT DOCOMO) commented that LS out depends on the outcome of the CRs
Gerald (Nokia): Nokia agrees that the LS has to be revised depending on outcome of the CRs. Prefer to send an LS.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Malla (NTT DOCOMO) propose to note
Noted
8.1 S2-2103817 CR Approval 23.288 CR0338 (Rel-17, 'B'): User consent to data collection and analytics Ericsson Rel-17 Confirm CR Number - CR states 0388! CC#5: r02 agreed. Revised to S2-2105199. Malla (NTT DOCOMO) pointed that this topic is required coordination with SA3, because in SA3 there is a study to do user consent for data collection. Therefore, we cannot carry out redundant work on the same topic in SA2 and SA3.
Belen (Ericsson) provides r01.
Gerald (Nokia): Nokia comments on r01
Malla (NTT DOCOMO) provides r02, but also fine with r01
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia suggests to POSTPONE
Belen (Ericsson) supports Note, rather than postpone.
We cannot predict what SA3 will do in the future.
Belen (Ericsson) corrects its previous comment. OK with r01 or r02.
Don't see a reason to postpone
==== 8.X, 9.X Final Deadline ====
Gerald (Nokia): Nokia can live with r02. Propose this to CC#4.
Belen (Ericsson) explains that the discssion on whether there is a need for an exception or not cannot be bound to the approval or rejection of this document
I did not ask to open the document in CC#4 either, you are of course welcome to do as you think your prefered option is.
Gerald (Nokia): Nokia clarifies that we did not ask to bind the approval/rejection of this document with an exception for KI#15.
Proposes this CR for CC#4. Okay with r02.
Belen (Ericsson) thanks Gerard for clarifying this.
Revised
8.1 S2-2105199 CR Approval 23.288 CR0338R1 (Rel-17, 'B'): User consent to data collection and analytics Ericsson Rel-17 Revision of S2-2103817r02. Approved Agreed
8.1 S2-2103818 CR Approval 23.502 CR2733 (Rel-17, 'B'): User consent to data collection Ericsson Rel-17 Noted Malla (NTT DOCOMO) pointed that this topic is required coordination with SA3, because in SA3 there is a study to do user consent for data collection. Therefore, we cannot carry out redundant work on the same topic in SA2 and SA3.
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104254 CR Approval 23.288 CR0350 (Rel-17, 'B'): User consent for UE data colletion Huawei Rel-17 Noted Malla (NTT DOCOMO) pointed that this topic is required coordination with SA3, because in SA3 there is a study to do user consent for data collection. Therefore, we cannot carry out redundant work on the same topic in SA2 and SA3.
Belen (Ericsson) prefers option#1 stated by DoCoMO, and shares DoCoMO view
Belen (Ericsson) prefers option#1 stated by DoCoMO, and shares DoCoMO view.
Ericsson objects to this CR in the current form.
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104616 CR Approval 23.502 CR2847 (Rel-17, 'B'): TS23.502 KI#15 User consent for UE data collection NEC Rel-17 Noted Malla (NTT DOCOMO) propose to merge the CR into S2-2103818/S2-2104702
Iskren (NEC) answers Malla (NTT DOCOMO) and suggest a merge is not needed.
Malla (NTT DOCOMO) propose to note the CR.
Iskren (NEC) responds to Malla (NTT DOCOMO) to address his concerns.
Belen (Ericsson) also proposes to NOTE this CR
Gerald (Nokia): Nokia has comments
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104618 CR Approval 23.288 CR0365 (Rel-17, 'B'): TS23.288 KI#15 User consent for UE data collection NEC Rel-17 Noted Malla (NTT DOCOMO) propose to merge the CR into S2-2103817/S2-2104701
Iskren (NEC) answers Malla (NTT DOCOMO) and suggest a merge is not needed.
Malla (NTT DOCOMO) propose to note the CR.
Iskren (NEC) responds to Malla (NTT DOCOMO) to address his concerns.
Gerald (Nokia): Nokia has comments
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104701 CR Approval 23.288 CR0325R1 (Rel-17, 'B'): User consent revocation Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2102828. Noted Malla (NTT DOCOMO) pointed that this topic is required coordination with SA3, because in SA3 there is a study to do user consent for data collection. Therefore, we cannot carry out redundant work on the same topic in SA2 and SA3.
Belen (Ericsson) prefers option#1 stated by DoCoMO, and shares DoCoMO view.
Ericsson objects to this CR in the current form.
Gerald (Nokia): Nokia prefers option#2 and provides r01
Belen (Ericsson) objects to r02. It is not an implementation of option#2
Belen (Ericsson) objects to r01. It is not an implementation of option#2
Gerald (Nokia): Nokia provides r02
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia suggests to POSTPONE
Belen (Ericsson) supports Note, rather than postpone.
We cannot predict what SA3 will do in the future.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104702 CR Approval 23.502 CR2862 (Rel-17, 'B'): User consent Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) pointed that this topic is required coordination with SA3, because in SA3 there is a study to do user consent for data collection. Therefore, we cannot carry out redundant work on the same topic in SA2 and SA3.
Belen (Ericsson) prefers option#1 stated by DoCoMO, and shares DoCoMO view.
Ericsson objects to this CR in the current form.
Gerald (Nokia): Nokia provides r01
Mehrdad (Samsung) assumes option one is already adopted as proposed by Docomo to be followed as outlined in 3817r01 and 3817r02
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia suggests to POSTPONE
Belen (Ericsson) supports Note, rather than postpone.
We cannot predict what SA3 will do in the future.
==== 8.X, 9.X Final Deadline ====
Noted
8.1 - - - KI#16 - - Docs:=10 -
8.1 S2-2103720 LS In Action LS from SA WG5: LS on providing cell energySaving Status information to NWDAF SA WG5 (S5-211438) Revision of Postponed S2-2102099 from S2#144E. Noted Gerald (Nokia): Nokia proposes to NOTE this LS In Noted
8.1 S2-2103721 LS In Action LS from SA WG5: Reply LS on network data analysis energy saving SA WG5 (S5-211478) Revision of Postponed S2-2102101 from S2#144E. Noted Gerald (Nokia): Nokia proposes to NOTE this LS In Noted
8.1 S2-2104521 CR Approval 23.502 CR2834 (Rel-17, 'C'): NWDAF assisted DNAI selection at SMF Samsung Rel-17 Confirm Spec version used - CR states 17.1.0! r03 agreed. Revised to S2-2104879. Gerald (Nokia): Nokia asks for clarification
Jungshin (Samsung) responds to Gerald (Nokia) and provides r01.
Gerald (Nokia): Nokia comments on r01 asking for clarification
Dimitris (Lenovo) provides r02
Jungshin (Samsung) provides comments on r02.
Jungshin (Samsung) provides r03.
Gerald (Nokia): Nokia comments on r03
Jungshin (Samsung) responds to Gerald (Nokia) and ask clarification.
Gerald (Nokia): Nokia responds to Samsung
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104879 CR Approval 23.502 CR2834R1 (Rel-17, 'C'): NWDAF assisted DNAI selection at SMF Samsung Rel-17 Revision of S2-2104521r03. Approved Agreed
8.1 S2-2104527 CR Approval 23.501 CR2938 (Rel-17, 'C'): NWDAF assisted DNAI and UPF selection at SMF Samsung Rel-17 r01 agreed. Revised to S2-2104880. Gerald (Nokia): Nokia questions reason for change
Gerald (Nokia): Nokia asks status of this CR
Jungshin (Samsung) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Nokia): Nokia is okay with r01
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104880 CR Approval 23.501 CR2938R1 (Rel-17, 'C'): NWDAF assisted DNAI and UPF selection at SMF Samsung Rel-17 Revision of S2-2104527r01. Approved Agreed
8.1 S2-2104588 CR Approval 23.288 CR0363 (Rel-17, 'F'): Clarification of Application Server address within Analytics Filter information in DN Performance Analytics Lenovo, Motorola Mobility Rel-17 r01 agreed. Revised to S2-2104881. Gerald (Nokia): Nokia has comments on original
Dimitris (Lenovo) responds
Gerald (Nokia): Nokia responds to Lenovo
Dimitris (Lenovo) responds to Gerald (Nokia)
Gerald (Nokia): Nokia responds to Dimitris (Lenovo)
Dimitris (Lenovo) provides r01
Gerald (Nokia): Nokia replies to Lenovo
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104881 CR Approval 23.288 CR0363R1 (Rel-17, 'F'): Clarification of Application Server address within Analytics Filter information in DN Performance Analytics Lenovo, Motorola Mobility Rel-17 Revision of S2-2104588r01. Approved Agreed
8.1 S2-2104596 CR Approval 23.288 CR0364 (Rel-17, 'F'): Clarification of Application Server address within Analytics Filter information in Service Experience Analytics Lenovo, Motorola Mobility Rel-17 r01 agreed. Revised to S2-2104882. Gerald (Nokia): Nokia has comments on original
Dimitris (Lenovo) responds
Dimitris (Lenovo) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104882 CR Approval 23.288 CR0364R1 (Rel-17, 'F'): Clarification of Application Server address within Analytics Filter information in Service Experience Analytics Lenovo, Motorola Mobility Rel-17 Revision of S2-2104596r01. Approved Agreed
8.1 - - - KI#18 - - Docs:=2 -
8.1 S2-2103924 CR Approval 23.288 CR0341 (Rel-17, 'F'): Adding clarifications related to the Supported Analytic Delay China Telecom Rel-17 r01 agreed. Revised to S2-2104883. Gerald (Nokia): Nokia asks for clarification
Song (China Telecom): China Telecom provides reply to Nokia's question and provides r01.
Gerald (Nokia): Nokia is okay with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104883 CR Approval 23.288 CR0341R1 (Rel-17, 'F'): Adding clarifications related to the Supported Analytic Delay China Telecom Rel-17 Revision of S2-2103924r01. Approved Agreed
8.1 - - - KI#19 - - Docs:=12 -
8.1 S2-2104025 CR Approval 23.288 CR0262R1 (Rel-17, 'B'): CR to update MTLF services to resolve ENs ETRI Rel-17 Revision of (Postponed) S2-2102212. r04 agreed. Revised to S2-2104884. Miguel (Ericsson) provides comments
Malla (NTT DOCOMO) provides comments
Yannick (Nokia): Nokia provides comments and requests for clarification.
David (Samsung) provides comments/questions.
Soohwan (ETRI) replies to all the comments and questions so far and provides r01.
Yannick (Nokia): Nokia requests for clarification.
Soohwan (ETRI) replies to Nokia.
Yannick (Nokia): Nokia thanks ETRI for the explanation.
Yannick (Nokia): Nokia provides r02.
Soohwan (ETRI) is okay with r02.
Wang Yuan (Huawei) provides comments on r02.
Malla (NTT DOCOMO) provided r03 contains aspects of S2-2104578.
Yannick (Nokia): Nokia provides r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104884 CR Approval 23.288 CR0262R2 (Rel-17, 'B'): CR to update MTLF services to resolve ENs ETRI Rel-17 Revision of S2-2104025r04. Approved Agreed
8.1 S2-2104026 CR Approval 23.288 CR0305R2 (Rel-17, 'B'): Definition of Nnwdaf_MLModelInfo_Request procedure and services ETRI, China Mobile(?) Rel-17 Revision of (Agreed) S2-2103298. Confirm Sources! r03 agreed. Revised to S2-2104885. Malla (NTT DOCOMO) noted that the proposed changes depend on the outcome of S2-2104025. We need to revisit this CR after the agreement of S2-2104025..
David (Samsung) provides questions and comments.
Yannick (Nokia): Nokia has same comments and requests for clarification as for S2-2104025.
Soohwan (ETRI) replies to all the comments and provides r01.
Yannick (Nokia): Nokia provides r02.
Soohwan (ETRI) provides r03 to confirm co-source company.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104885 CR Approval 23.288 CR0305R3 (Rel-17, 'B'): Definition of Nnwdaf_MLModelInfo_Request procedure and services ETRI, China Mobile(?) Rel-17 Revision of S2-2104026r03. Approved Agreed
8.1 S2-2104417 CR Approval 23.288 CR0291R3 (Rel-17, 'B'): NWDAF discovery and selection based on ML model information Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103241. r02 agreed. Revised to S2-2104886. Megha(Intel) asks question for clarification.
Wang Yuan (Huawei) replies to Megha (Intel).
Yannick (Nokia): Nokia provides r01.
Gerald (Nokia): Nokia provides r02
Wang Yuan (Huawei) accepts r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104886 CR Approval 23.288 CR0291R4 (Rel-17, 'B'): NWDAF discovery and selection based on ML model information Huawei, HiSilicon Rel-17 Revision of S2-2104417r02. Approved Agreed
8.1 S2-2104418 CR Approval 23.501 CR2761R3 (Rel-17, 'B'): Update the NWDAF profile for ML Model Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103242. r01 agreed. Revised to S2-2104887. Yannick (Nokia): Nokia provides r01.
Soohwan (ETRI) asks to align this CR with the results of S2-2104417.
Soohwan (ETRI) reverts the comments.
==== 8.X, 9.X Revisions Deadline ====
Wang Yuan (Huawei) accepts r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104887 CR Approval 23.501 CR2761R4 (Rel-17, 'B'): Update the NWDAF profile for ML Model Huawei, HiSilicon Rel-17 Revision of S2-2104418r01. Approved Agreed
8.1 S2-2104578 CR Approval 23.288 CR0362 (Rel-17, 'B'): ML Model Provisioning filter information NTT DOCOMO Rel-17 r03 agreed. Revised to S2-2104888. Miguel (Ericsson) ask a question
David (Samsung) provides questions and comments.
Malla (NTT DOCOMO) replies to David (Samsung).
Yannick (Nokia): Nokia provides r01.
Malla (NTT DOCOMO) provides r02.
David (Samsung) provides comments, suggests to merge with S2-2104025.
Yannick (Nokia): Nokia supports the proposal from Samsung to merge with S2-2104025.
Malla (NTT DOCOMO) provided r03.
David (Samsung) thanks NTT DOCOMO, is OK with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.1 S2-2104888 CR Approval 23.288 CR0362R1 (Rel-17, 'B'): ML Model Provisioning filter information NTT DOCOMO Rel-17 Revision of S2-2104578r03. Approved Agreed
8.1 S2-2104624 CR Approval 23.501 CR2956 (Rel-17, 'F'): NWDAF discovery and selection - ML model provisioning Intel Rel-17 Noted Malla (NTT DOCOMO) questions the need of this CR
Megha (Intel) responds to Malla (NTT DOCOMO).
Malla (NTT DOCOMO) responds to Megha (Intel).
Megha (Intel) is fine to NOTE this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.1 S2-2104752 CR Approval 23.288 CR0375 (Rel-17, 'B'): NWDAF discovery update to support model sharing among trusted vendors Nokia, Nokia Shanghai Bell Rel-17 Noted Malla (NTT DOCOMO) propose to merge into S2-2104450.
Dimitris (Lenovo) also suggests to merge into S2-2104450
Wang Yuan (Huawei) also suggests to merge this into S2-2104450
==== 8.X, 9.X Revisions Deadline ====
Malla (NTT DOCOMO) asks the Nokia to confirm the merge or else we propose to note the CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 - - - Enhanced support of Non-Public Networks (eNPN) - - Docs:=99 -
8.2 - - - General - - Docs:=9 -
8.2 S2-2104730 DISCUSSION Information ENPN work plan. Ericsson (rapporteur) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2103736 LS In Information Reply LS on support of PWS over SNPN RAN WG2 (R2-2104640) Rel-17 Noted Peter Hedman (Ericsson) proposes to note the LS as SA2 replied already. Noted
8.2 S2-2103760 LS In Action LS from CT WG1: Reply LS on UE capabilities indication in UPU CT WG1 (C1-212599) Rel-17 Responses drafted in S2-2104336, S2-2104584 and S2-2104602. Postponed Postponed
8.2 S2-2104336 LS OUT Approval [DRAFT] Reply LS on UE capabilities indication in UPU Ericsson Rel-17 Response to S2-2103760. Merged into S2-2104602 (Postponed) Qianghua (Huawei) suggest to merge this into S2-2104602
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104584 LS OUT Approval [DRAFT] Reply LS on UE capabilities indication in UPU Qualcomm Rel-17 Response to S2-2103760. Merged into S2-2104602 (Postponed) Jianning (Xiaomi) seeks clarification
Peter Hedman (Ericsson) provides reply
Qianghua (Huawei) suggests to merge this into S2-2104602
Jianning (Xiaomi) replise to Peter (Ericsson)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104602 LS OUT Approval [DRAFT] Reply LS on UE capabilities indication in UPU MediaTek Inc. Rel-17 Response to S2-2103760. Postponed Qianghua (Huawei) provides comments
Xiaowan (vivo) supports Alt2 and comments on Alt1
Josep (DT) comments, supports Alt1
Haris(Qualcomm) comments
Chia-Lin(MediaTek) responds to Haris (Qualcomm)
Jianning (Xiaomi) seeks clarification
Rainer (Nokia) replies.
Peter Hedman (Ericsson) provides comments and propose to go with LS out in 04584 or 04336.
Peter Hedman (Ericsson) provides r01
Jianning (Xiaomi) provides view
Fei (OPPO) provides r02.
Rainer (Nokia) provides r03.
Chia-Lin (MediaTek) provides r04
Haris(Qualcomm) comments that r04 makes the SA2 response unecessary
Jianning (Xiaomi) provides comments
==== 8.X, 9.X Revisions Deadline ====
Jianning (Xiaomi) replies
Josep (DT) objects to r00, finds r02, r03 very confusing.
Haris(Qualcomm) objects to r04, r02, r0 and can accept r01, r03
Chia-Lin (MediaTek) is only ok with original version and r04. If not agreeable, propose to postpone the LS
Rainer (Nokia) prefers r03 but also ok to postpone the LS.
Jianning (Xiaomi) objects all the versions, suggest to postpone this LS. Based on current UPU parameters, we don't have such issue that assumed in this LS.
xiaowan (vivo) is OK to postpone
Amanda Xiang ( Futurewei ) is also fine to postpone this LS
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104603 CR Approval 23.501 CR2949 (Rel-17, 'B'): The supported parameters set type indication for UPU MediaTek Inc. Rel-17 Noted Rainer (Nokia) provides r01.
xiaowan (vivo) provides suggestions.
Josep (DT) asks questions for clarification.
Haris(Qualcomm) indicates that the CR does not solve the problem in the 'reason for change'
Jianning (Xiaomi) shares the same concens with Josep (DT)
Jianning (Xiaomi) replies
Chia-Lin (MediaTek) responds
Peter Hedman (Ericsson) provides comments and propose to focus on the LS out for this meeting.
Fei (OPPO) comments.
Chia-Lin (MediaTek) responds to Peter (Ericsson)
Rainer (Nokia) comments.
Jianning (Xiaomi) replies to Chia-Lin (MediaTek)
Peter Hedman (Ericsson) proposes to note the CR based on CC#3 discussions.
Jianning (Xiaomi) supports Peter (Ericsson), to focus on the LS reply
Haris(Qualcomm) proposes to note the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104359 CR Approval 23.502 CR2804 (Rel-17, 'B'): NF Management for SNPN Ericsson Rel-17 r03 agreed. Revised to S2-2105009. Josep (DT) proposes to note this CR.
Devaki (Nokia) proposes to note the CR.
Peter Hedman (Ericsson) provides r01
Antoine (Orange) provides r02.
Peter Hedman (Ericsson) provides reply to Orange
Peter Hedman (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105009 CR Approval 23.502 CR2804R1 (Rel-17, 'B'): NF Management for SNPN Ericsson Rel-17 Revision of S2-2104359r03. Approved Agreed
8.2 - - - KI#1 related - - Docs:=42 -
8.2 S2-2104537 CR Approval 23.501 CR2939 (Rel-17, 'B'): Correction to scenarios of external authentication Huawei, Hisilicon Rel-17 CC#5: r03 + changes agreed. Revised to S2-2105209. Peter Hedman (Ericsson) provides r01
Devaki (Nokia) believes r01 is incorrect, can live with original version if anything is needed at all.
Hualin(Huawei) also think r01 is not correct.
Peter Hedman (Ericsson) provides r02, removing 'SMF'
Hualin(Huawei) replied to Peter Hedman (Ericsson).
Devaki (Nokia) also prefers original version, objects to r01/02.
Peter Hedman (Ericsson) provides r03
Hualin(Huawei) prefer the original version and can live with r03.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) cannot accept r03 as it removes the subscription retrieval by AMF/SMF for CH=AAA architecture.
Hualin(Huawei) suggest to go with the original version and can accept r03 from our perspective.
Peter Hedman (Ericsson) provides reply and can accept r03, r02, r01 and cannot accept r00.
Hualin(Huawei) suggest to go with r02, since there is no technical argument on this version.
==== 8.X, 9.X Final Deadline ====
Hualin(Huawei) suggest to discuss it in CC#4, since a small change may resolve the problem.
Hualin(Huawei) provide r04 in draft folder to discuss it in CC#4, after offline discussion with Nokia and Ericsson.
Peter Hedman (Ericsson) confirming that r04 is ok for
Hualin(Huawei) is ok with that.
Revised
8.2 S2-2105209 CR Approval 23.501 CR2939R1 (Rel-17, 'B'): Correction to scenarios of external authentication Huawei, Hisilicon Rel-17 Revision of S2-2104537r03 + changes. Approved Agreed
8.2 S2-2104442 CR Approval 23.501 CR2926 (Rel-17, 'C'): Interaction between AUSF and AAA Server CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-17 r06 agreed. Revised to S2-2105010. Yunjing (CATT) provides r01 based on the way forward in the notes for eNPN CC.
Peter Hedman (Ericsson) provides comments.
Marco (Huawei) provides comments.
Yunjing (CATT) replies to comments.
Peter Hedman (Ericsson) provides reply
Devaki (Nokia) supports the approach 're-name of NSSAAF to Network System Specific Authentication and Authorization Function'.
Dieter (Deutsche Telekom): we do not support this approach forward.
Yunjing (CATT) replies to Dieter (Deutsche Telekom).
Dieter (Deutsche Telekom) proposes alternative if some re-naming is still preferred.
Devaki (Nokia) prefers (and supports) the alternative: NSSAAF - Network Slice-specific and SNPN Authentication and Authorization Function
Yunjing(CATT) provides r02 based on comments received.
Qianghua (Huawei) provides r03
Peter Hedman (Ericsson) provides comments and r04
Peter Hedman (Ericsson) provides comment that we can inore r04.
Marco (Huawei) provides r05.
Dieter (Deutsche Telekom) comments.
Marco (Huawei) answers to Dieter (Deutsche Telekom) and provides r06
==== 8.X, 9.X Revisions Deadline ====
Dieter (Deutsche Telekom) is ok with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105010 CR Approval 23.501 CR2926R1 (Rel-17, 'C'): Interaction between AUSF and AAA Server CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104442r06. Approved Agreed
8.2 S2-2104443 CR Approval 23.502 CR2820 (Rel-17, 'C'): Add a new NSSAAF service to support interaction between AUSF and AAA Server CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2105011. Yunjing (CATT) provides r01 based on the way forward in the notes for eNPN CC.
Peter Hedman (Ericsson) provides comments.
Marco (Huawei) provides comments.
Yunjing (CATT) replies to comments.
Devaki (Nokia) supports the approach 're-name of NSSAAF to Network System Specific Authentication and Authorization Function'.
Dieter (Deutsche Telekom): we do not support this approach forward.
Dieter (Deutsche Telekom) proposes alternative if some re-naming is still preferred.
Devaki (Nokia) prefers (and supports) the alternative: NSSAAF - Network Slice-specific and SNPN Authentication and Authorization Function
Yunjing(CATT) provides r02 based on comments received.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105011 CR Approval 23.502 CR2820R1 (Rel-17, 'C'): Add a new NSSAAF service to support interaction between AUSF and AAA Server CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104443r02. Approved Agreed
8.2 S2-2104608 CR Approval 23.501 CR2952 (Rel-17, 'B'): HRNN in manual network selection for SNPNs MediaTek Inc. Rel-17 r01 agreed. Revised to S2-2105012. Peter Hedman (Ericsson) provides r01
Chia-Lin (MediaTek) is ok with r01
Devaki (Nokia) proposes to note the CR as existing text already covers HRNN for available SNPNs.
Chia-Lin (MediaTek) responds
Fei (OPPO) comments and considers the clarification is required
Peter Hedman (Ericsson) provides reply
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) can live with r01 although I still do not see the need for it.
Peter Hedman (Ericsson) provides reply to Nokia
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105012 CR Approval 23.501 CR2952R1 (Rel-17, 'B'): HRNN in manual network selection for SNPNs MediaTek Inc. Rel-17 Revision of S2-2104608r01. Approved Agreed
8.2 S2-2103747 LS In Action Reply LS on updating the Credentials Holder controlled lists for SNPN selection CT WG1 (C1-212419) Rel-17 CC#4: This LS was postponed. Postponed
8.2 S2-2104176 CR Approval 23.501 CR2754R1 (Rel-17, 'F'): Update of CH controlled prioritized list of preferred SNPNs and GINs Huawei, HiSilicon Rel-17 Revision of (Noted) S2-2102415. r08 agreed. Revised to S2-2105013, merging S2-2104356 and S2-2104606 Peter Hedman (Ericsson) provides r01
Sebastian (Qualcomm) provides r02
Josep (DT) disagrees with the UPU approach, propose to bring this issue to the CC, provides r03.
Devaki (Nokia) provides r04 to reflect the way forward (SoR for PLMN, UPU for SNPN) proposed during CC#3.
Jianning (Xiaomi) shares the view with Josep (DT), don't see the value to split the solutisons for PLMN case and SNPN case, seek for more clarification
Qianghua (Huawei) provides r05
Jianning (Xiaomi) provides r06 on top of r03, propose to progress SoR for both PLMN/SNPN case.
Antoine (Orange) provides r07, based on r06.
Haris(Qualcomm) provides r08
Jianning (Xiaomi) replies to Haris (Qualcomm)
Haris(Qualcomm) comments
Jianning (Xiaomi) replise
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides support for r08 which is inline with CC#3 discussions.
Josep (DT) asks questions regarding the proposed r08 'mix'.
Jianning (Xiaomi) shares with Josep (DT) and provide comments
Chia-Lin (MediaTek) would like to ask for clarification from Xiaomi
Dieter (Deutsche Telekom) comments.
Dieter (Deutsche Telekom) r08 is not acceptable with current text, we propose to go with r07.
Jianning (Xiaomi) replies to Chia-Lin (MediaTek)
Jianning (Xiaomi) also suggests to go with r07, cannot live with r08.
Amanda Xiang ( Futurewei ) comments
Xiaowan(vivo) is OK to go with r07.
Antoine (Orange) objects to r08.
==== 8.X, 9.X Final Deadline ====
Haris(Qualcomm) comments that discussion needs to happen in CC#4. Objects to r07
Revised
8.2 S2-2105013 CR Approval 23.501 CR2754R2 (Rel-17, 'F'): Update of CH controlled prioritized list of preferred SNPNs and GINs Huawei, HiSilicon Rel-17 Revision of S2-2104176r08, merging S2-2104356 and S2-2104606. CC#4: Postponed Postponed
8.2 S2-2104215 CR Approval 23.502 CR2789 (Rel-17, 'F'): Update of prioritized list of preferred SNPNs and Group IDs to the UE Huawei, HiSilicon Rel-17 Merged into S2-2104338 (Posponed at CC#4) Wen (vivo) provides comments and r01.
Peter Hedman (Ericsson) provides comments and propose to use 04338 instead.
Qianghua (Huawei) agrees to merge into 04338
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104352 DISCUSSION Discussion Discussion for updating the preferred list. Xiaomi Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104353 CR Approval 23.502 CR2717R1 (Rel-17, 'B'): Support for update of Credentials Holder controlled prioritized list of preferred SNPNs Xiaomi Rel-17 Revision of (Postponed) S2-2102874. Merged into S2-2104338 (Postponed) Peter Hedman (Ericsson) provides comments and proposes to move forward with using UPU
Jianning (Xiaomi) replies and comment, several things needs clarification before moving forward with UPU or SoR
Fei (OPPO) comments and also support to merge it to S2-2104338
Dieter (Deutsche Telekom) supports go forward with this CR for the case of using SoR for updating those lists.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Jianning (Xiaomi) proposes to bring this doc for CC#4
Postponed
8.2 S2-2104356 CR Approval 23.501 CR2839R1 (Rel-17, 'B'): Support for update of Credentials Holder controlled prioritized list of preferred SNPNs Xiaomi Rel-17 Revision of (Postponed) S2-2102873. Merged into S2-2105013 Sebastian (Qualcomm) proposed to merge with S2-2104338
Jianning (Xiaomi) replies Sebastian (Qualcomm), currently it is better to discuss separately untill we make final decision to use UPU
Dieter (Deutsche Telekom) supports this CR, i.e. to use SoR as the only mechnism for updating such lists.
Devaki (Nokia) comments that 4176r04 documents the way forward proposal discussed during CC#3. Proposes to consider this merged with 4176.
Qianghua (Huawei) proposes to consider this merged with 4176
Jianning (Xiaomi) is ok to merge with 4176
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104338 CR Approval 23.502 CR2801 (Rel-17, 'B'): Additional parameters using UE Parameters Update via UDM Control Plane Procedure Ericsson Rel-17 CC#4: This was postponed. Jihoon (ETRI) provides r01.
Youngkyo(Samsung) provides r02.
Hualin(Huawei) ask for clarification.
Peter Hedman (Ericsson) provides reply
Fei (OPPO) comments.
Jianning (Xiaomi) seeks clarification from Peter (Ericsson)
Peter Hedman (Ericsson) provides r03
Fei (OPPO) comments and provides r04.
Qianghua (Huawei) provides r05
Sebastian (Qualcomm) provides r06
Fei (OPPO) asks clarification
Sebastian (Qualcomm) replies to Fei
Amanda Xiang ( Futurewei ) asks question for clarification.
Josep (DT) comments, provides r07. Disagrees to include UPU for preferred network list.
Jianning (Xiaomi) replies to Peter (Ericsson),
Devaki (Nokia) comments.
Jihoon (ETRI) replies to Devaki (Nokia).
Jianning (Xiaomi) shares the view with Josep (DT). SNPN has to support two mechanism to update the netwrok preferred list for PLMN UE and SNPN UE respectively, we don't see the value to develop another parallel way.
Peter Hedman (Ericsson) provides r08
Jianning (Xiaomi) provides further comment
Xiaowan(vivo) shows concerns about 'If the credential holder is PLMN, then SoR is used and if the credential holder is SNPN, then UPU s used (i.e. having both options specified).'
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides reply to Xiaomi
Jianning (Xiaomi) replise to Peter (Ericsson)
Dieter (Deutsche Telekom) questions whether this CR can be agreed as is as it is not clear whether UPU for the lists for SNPN selection is agreed.
Jianning (Xiaomi) cannot live with all the versions, propose to send LS to SA3 to confirm/evaluate whether UPU is a secure way to deliver the credentials first, then we can decide whether to progress further.
Antoine (Orange) proposes to postpone this CR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104606 CR Approval 23.501 CR2951 (Rel-17, 'B'): Updating the Credentials Holder controlled lists for SNPN selection MediaTek Inc. Rel-17 Merged into S2-2105013 Qianghua (Huawei) asks whether we can merge this with S2-2104176
Sebastian (Qualcomm) proposes to merge with S2-2104176
Chia-Lin (MediaTek) is ok to be merged with S2-2104176
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104607 CR Approval 23.502 CR2846 (Rel-17, 'B'): Updating the Credentials Holder controlled lists for SNPN selection MediaTek Inc. Rel-17 Merged into S2-2104338 (Posponed at CC#4) Qianghua (Huawei) suggests to merge this into S2-2104338
Chia-Lin (MediaTek) is ok to be merged with S2-2104338
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2103978 DISCUSSION Agreement Discussion on the format of SUPI/SUCI used to access to a SNPN vivo Rel-17 Noted Dieter (Deutsche Telekom) disagrees with proposal in this discussion paper and proposes to note it.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2103979 CR Approval 23.501 CR2830R1 (Rel-17, 'B'): Handling of SUPI/SUCI format of a UE from credentials holder when accessing to a SNPN vivo Rel-17 Revision of (Postponed) S2-2102836. Noted Hualin(Huawei) comments.
Xiaowan(vivo) replies to Hualin(Huawei)
Devaki (Nokia) comments.
Sebastian (Qualcomm) objects to the CR
Hualin(Huawei) agree with Devaki (Nokia).
Josep (DT) object to this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104332 CR Approval 23.501 CR2919 (Rel-17, 'B'): KI#1 T3: Handling of SUPI/SUCI format when accessing to a SNPN Ericsson Rel-17 CC#4: This was postponed. Sebastian (Qualcomm) provides r01
Devaki (Nokia) comments.
Qianghua (Huawei) prefers option 1
Saso (Intel) comments.
Chia-Lin (MediaTek) provides the comments
Xiaowan (vivo) comments.
Peter Hedman (Ericsson) provides reply
Sebastian (Qualcomm) replies
Fei (OPPO) comments
Peter Hedman (Ericsson) provides comments and suggest we decide between option 1 and option 2+3
Xiaowan (vivo) replies to Peter Hedman (Ericsson) and suggests to add another alternative Option3 only
Dieter (Deutsche Telekom) sees option 3 as the only way as proposed r01.
Devaki (Nokia) proposes that we remove option 2 as per CC#3.
Antoine (Orange) provides r02 to fix the wording in the first bullet.
Peter Hedman (Ericsson) provides r03
Dieter (Deutsche Telekom) comments r03.
Peter Hedman (Ericsson) provides r04
xiaowan (vivo) provides comments and r05
Peter Hedman (Ericsson) provides reply and comments that r05 does not cover all the scenarios
==== 8.X, 9.X Revisions Deadline ====
Xiaowan(vivo) replies Peter Hedman (Ericsson)
Josep (DT) additionally objects to revisions including 'the NID of the SUPI'. This includes r03, r04, r05
Peter Hedman (Ericsson) provides reply to Josep for understanding the nature of the objection i.e. wording or the functionality proposed.
Josep (DT) answers that 'the NID of the SNPN associated to the SUPI' would be fine.
Xiaowan(vivo) replies to Josep (DT)
Haris(Qualcomm) asks question
Saso (Intel) seeks clarification
Peter Hedman (Ericsson) asks if we can agree r04 + proposal from Josep
Haris(Qualcomm) answers
Chia-Lin (MediaTek) is ok with r06 provided by Peter (Ericsson)
Saso (Intel) seeks clarification on r06 provided by Peter (Ericsson)
Haris(Qualcomm) comments on r06
Dieter (Deutsche Telekom) prefers to postpone the CR and discuss until next meeting...
Xiaowan (vivo) provides reply
==== 8.X, 9.X Final Deadline ====
Saso (Intel) replies to Peter
Postponed
8.2 S2-2104333 CR Approval 23.501 CR2920 (Rel-17, 'B'): KI#1 T4: SNPN with self-assigned NID Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2105015 Sebastian (Qualcomm) raises concerns with the CR and asks a question
Hualin(Huawei) propose to merge this paper to S2-2104539.
Sebastian (Qualcomm) also proposes to merge with S2-2104539
Peter Hedman (Ericsson) provides reply and ok to merge.
Sebastian (Qualcomm) replies to Peter
Dieter (Deutsche Telekom) proposes to keep the self-assigned NIDs for standalone non-public network SNPNs which are really standalone.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104538 CR Approval 23.501 CR2801R1 (Rel-17, 'B'): Correction to UE identifier sent to AMF by UE Huawei, Hisilicon Rel-17 Revision of (Noted) S2-2102641. r03 agreed. Revised to S2-2105014. Peter Hedman (Ericsson) provides r01
Hualin(Huawei) comments on r01.
Devaki (Nokia) also prefers r00, cannot accept r01 as it is not backward compatible.
Antoine (Orange): A sentence in r00 is not readable.
Hualin(Huawei) replied to Antoine (Orange) and provide r02.
Peter Hedman (Ericsson) provides reply.
Hualin(Huawei) replied to Peter Hedman (Ericsson) and provide r03.
==== 8.X, 9.X Revisions Deadline ====
Josep (DT) knows it is too late anyway but proposes a new text anyway. All versions (including the original) are quite convoluted.
Haris(Qualcomm) comments that the CR is NOT Cat.D it should be Cat.F
Peter Hedman (Ericsson) ok with r03 while cover sheet can be updated.
Antoine (Orange): OK with the changes in r03 but not clear whether the updated text is informative or normative.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105014 CR Approval 23.501 CR2801R2 (Rel-17, 'B'): Correction to UE identifier sent to AMF by UE Huawei, Hisilicon Rel-17 Revision of S2-2104538r03. Approved Agreed
8.2 S2-2104539 CR Approval 23.501 CR2940 (Rel-17, 'F'): Clarification on NID Huawei, Hisilicon Rel-17 r08 agreed. Revised to S2-2105015, merging S2-2104333 Sebastian (Qualcomm) objects to the CR
Hualin(Huawei) replies and provide r01.
Sebastian (Qualcomm) provides r03; please ignore r02 which had a typo
Devaki (Nokia) objects to original and the revisions of the CRs as there is no need to mandate NID is unique for SNPN with CH arch.
Hualin(Huawei) provide r04 and reply to Devaki(Nokia).
Peter Hedman (Ericsson) provides r05 and comments
Josep (DT) objects to r00, r01, comments on r05.
Devaki (Nokia) comments.
Peter Hedman (Ericsson) provides reply
Sebastian (Qualcomm) has concerns with r05
Hualin(Huawei) replied to Peter Hedman (Ericsson).
Peter Hedman (Ericsson) provides reply.
Peter Hedman (Ericsson) provides some questions
Josep (DT) comments provides r06.
Hualin(Huawei) ask question on r06 and provides r07.
Devaki (Nokia) comments and provides r08.
Josep (DT) comments.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r08 and r07.
Dieter (Deutsche Telekom) is ok with r08.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105015 CR Approval 23.501 CR2940R1 (Rel-17, 'F'): Clarification on NID Huawei, Hisilicon Rel-17 Revision of S2-2104539r08, merging S2-2104333. Approved Agreed
8.2 S2-2104115 CR Approval 23.501 CR2894 (Rel-17, 'F'): SNPN GIN Encoding Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2105016. Sebastian (Qualcomm) provides r01
Devaki (Nokia) provides r02.
Qianghua (Huawei) provides comments
Devaki (Nokia) replies to Qianghua (Huawei).
Peter Hedman (Ericsson) provides r03
Dieter (Deutsche Telekom) asks question for clarification.
Devaki (Nokia) comments and provides r04
Dieter (Deutsche Telekom) asks question for clarification r04.
Devaki (Nokia) replies to Dieter (Deutsche Telekom).
Devaki (Nokia) provides r05.
Haris(Qualcomm) prefers r04
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) fine with r04 or r05.
Haris(Qualcomm) is not ok with r05, suggest to approve r04
Dieter (Deutsche Telekom) is ok with approving r04.
Peter Hedman (Ericsson) prefer r03 as to limit the size of the GIN
Chia-Lin (MediaTek) is ok with r04 or r05.
Dieter (Deutsche Telekom) agrees with Peter (Ericsson) and prefers r03 as well for that reason.
Amanda Xiang ( Futurewei) also prefer r03 to limit the size of GIN.
Devaki (Nokia) fine with either r03 or r04.
Antoine (Orange) objects to r04 and r05, fine with r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105016 CR Approval 23.501 CR2894R1 (Rel-17, 'F'): SNPN GIN Encoding Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104115r03. Approved Agreed
8.2 S2-2104113 CR Approval 23.501 CR2892 (Rel-17, 'F'): SNPN UE configuration and subscription aspects Nokia, Nokia Shanghai Bell, Ericsson, Huawei Rel-17 r01 agreed. Revised to S2-2105017. Sebastian (Qualcomm) asks a question
Devaki (Nokia) replies.
Sebastian (Qualcomm) provides r01
Devaki (Nokia) fine with r01.
Qianghua (Huawei) OK with r01
Dieter (Deutsche Telekom): asks questions for clarification.
Qianghua (Huawei) replies
Dieter (Deutsche Telekom): comments.
Sebastian (Qualcomm) replies to Dieter
Dieter (Deutsche Telekom) replies to Sebastian.
Devaki (Nokia) comments.
==== 8.X, 9.X Revisions Deadline ====
Dieter (Deutsche Telekom): is ok with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105017 CR Approval 23.501 CR2892R1 (Rel-17, 'F'): SNPN UE configuration and subscription aspects Nokia, Nokia Shanghai Bell, Ericsson, Huawei Rel-17 Revision of S2-2104113r01. Approved Agreed
8.2 S2-2104175 CR Approval 23.502 CR2787 (Rel-17, 'F'): Network access control by Credential Holder Huawei, HiSilicon Rel-17 Noted Devaki (Nokia) comments.
Qianghua (Huawei) replies
Peter Hedman (Ericsson) provides commenst and question why we need to add these error description in the procedures.
Sebastian (Qualcomm) has similar concerns as Peter (Ericsson); not sure these aspects need to be captured as they are not captured for PLMNs either
Qianghua (Huawei) provides r01
Josep (DT) also has concerns.
Haris(Qualcomm) reiterates previous comment and objects to all revisions
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104540 CR Approval 23.501 CR2941 (Rel-17, 'F'): Clarification for selection of AUSF in CH Huawei, Hisilicon Rel-17 CC#4: This was discussed off-line and noted. Devaki (Nokia) provides r01, can only accept the 3rd bullet, first two bullets are not correct nor needed.
Hualin(Huawei) clarify the first two bullets are just clarification and we can live without them.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides comments that the CR is not needed, can give the wrong understanding and propose to note the CR.
Hualin(Huawei) propose to bring it to CC#4 for a new revision, since we may solve it with a small change.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104114 CR Approval 23.501 CR2893 (Rel-17, 'B'): SNPN - SNPN Mobility - AMF selection impacts Nokia, Nokia Shanghai Bell, Ericsson Rel-17 r05 agreed. Revised to S2-2105018. Wen (vivo) provides comments.
Devaki (Nokia) replies to Vivo.
Youngkyo(Samsung) provides question and comment.
Devaki (Nokia) replies to Samsung.
Youngkyo(Samsung) replies to Devaki and provides r01.
Peter Hedman (Ericsson) provides comments
Youngkyo(Samsung) replies to peter.
Devaki (Nokia) comments.
Youngkyo(Samsung) replies to Devaki.
Josep (DT) comments, provides r02.
Devaki (Nokia) proposes to go with r02 for now.
Youngkyo(Samsung) is okay with r02.
Qianghua (Huawei) provides r03
Devaki (Nokia) comments that r03 is not technically correct as it removes the reference to 'NID owner'. Provides r04 reinstating that part.
Qianghua (Huawei) replies and provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105018 CR Approval 23.501 CR2893R1 (Rel-17, 'B'): SNPN - SNPN Mobility - AMF selection impacts Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2104114r05. Approved Agreed
8.2 S2-2104218 CR Approval 23.501 CR2815R2 (Rel-17, 'B'): KI#1 - T5, Enable mobility between networks [ZTE, OPPO,] Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell, Ericsson] Rel-17 Revision of (Agreed) S2-2103075. CC#4: r08 + changes agreed. Revised to S2-2105143. Wen (vivo) provides comments and r01.
Fei (OPPO) provides r02.
Qianghua (Huawei) comments
Wen (vivo) responds.
Tyler (OTD) provides comment.
Fei (OPPO) responds
Sebastian (Qualcomm) provides r03
zhendong (ZTE) provides the r04.
Qianghua (Huawei) replies
Fei (OPPO) responds.
Devaki (Nokia) requests that the authors should consult 'original source companies' prior to submitting a revision of an approved paper (guidance also from SA2 chair).
Qianghua (Huawei) provides r05
Fei (OPPO) asks clarification for r05.
Fei (OPPO) responds to Qianghua.
Fei (OPPO) responds and is Ok with r05.
Peter Hedman (Ericsson) provides a question
Youngkyo(Samsung) provides comment and further question.
Qianghua (Huawei) replies.
Youngkyo(Samsung) replies to Qianghua and provide r06.
Fei (OPPO) comments.
Qianghua (Huawei) provides r07
Dieter (Deutsche Telekom) do not see much value in adding such a note, i.e. proposes to keep original CR agreed in last meeting.
Antoine (Orange) also don't see the value of this CR, as it is always up the the UE to establish a PDU Session.
Youngkyo(Samsung) provides r08
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) still belives this CR is useless.
==== 8.X, 9.X Final Deadline ====
Peter Hedman (Ericsson) provides comments and propose to slightly update the note
Qianghua (Huawei) the proposal works for me
Revised
8.2 S2-2105143 CR Approval 23.501 CR2815R3 (Rel-17, 'B'): KI#1 - T5, Enable mobility between networks [ZTE, OPPO,] Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell, Ericsson] Rel-17 Revision of S2-2104218r08 + changes. This CR was agreed Agreed
8.2 S2-2104219 CR Approval 23.502 CR2641R2 (Rel-17, 'B'): SNPN - SNPN Mobility and Registration procedure [Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, Mediatek,] Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2102967. Noted Sebastian (Qualcomm) objects to the CR
Devaki (Nokia) is fine with the update.
Devaki (Nokia) provides r01. Merge S2-2104729 with this.
Sebastian (Qualcomm) objects to r01
Qianghua (Huawei) this depends on discussion on S2-2104333, S2-2104539; if self-assignment mode is finally agreed, this CR should be reconsidered in the end
Peter Hedman (Ericsson) provides comment and support to use NIDs in coordinated assignment model when UE can select other SNPNs than its Subscribed SNPN.
Devaki (Nokia) comments.
Antoine (Orange) objects to r00 and r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104160 CR Approval 23.502 CR2781 (Rel-17, 'B'): UE mobility support considering SNPN involved. samsung Rel-17 Noted Wen (vivo) provides comments.
Youngkyo(Samsung) reply to Wen (vivo)
Chia-Lin (MediaTek) provides comments.
Youngkyo(Samsung) reply to Chia-Lin (MediaTek)
Fei (OPPO) comments
Youngkyo(Samsung) replies to Chia-Lin (MediaTek) and Fei(OPPO)
Devaki (Nokia) comments.
Sebastian (Qualcomm) objects to the CR
Youngkyo(Samsung) replies to Devaki (Nokia)
Youngkyo(Samsung) replies to Sebastian
Sebastian (Qualcomm) replies
Dieter (Deutsche Telekom): comments
Antoine (Orange) replies.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104729 CR Approval 23.502 CR2641R3 (Rel-17, 'B'): SNPN - SNPN Mobility and Registration procedure Ericsson, [Nokia, Nokia Shanghai Bell, Qualcomm, Mediatek] Rel-17 Revision of (Agreed) S2-2102967. Noted Sebastian (Qualcomm) objects to the tdoc
Devaki (Nokia) objects to the document, proposes to merge with 4729.
Peter Hedman (Ericsson) ok to mark it merged into 4729, but also the content depends on 04332 outcome.
Dieter (Deutsche Telekom) assumes the CR is merged into 4219 and comments.
Devaki (Nokia) proposes that this CR should be considered as merged into 4729 (as it is a revision of a CR approved from SA2#144E).
Dieter (Deutsche Telekom) comments 4729 cannot be merged into itself.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104163 CR Approval 23.502 CR2783 (Rel-17, 'B'): UE context retrieval during registration procedure considering SNPN involved. samsung Rel-17 r10 agreed. Revised to S2-2105019, merging S2-2104716 Wen (vivo) provides comments.
Youngkyo(Samsung) reply to Wen (vivo)
Qianghua (Huawei) provides comments
Youngkyo(Samsung) replies to Qianghua (Huawei)
Qianghua (Huawei) provides r01
Youngkyo(Samsung) replies to Qianghua (Huawei) and provide r02.
Qianghua (Huawei) replies
Youngkyo(Samsung) provides r03
Devaki (Nokia) provides r04.
Qianghua (Huawei) provides r05
Youngkyo(Samsung) replies to Devaki and Qianghua, and provides r06.
Devaki (Nokia) replies, has objections with r06 to re-instate the SM parts. Proposes to go with r05.
Youngkyo(Samsung) provides a comment and a question
Peter Hedman (Ericsson) provides r07, using r05 as basis
Youngkyo(Samsung) provides r08 and questions to Peter.
Josep (DT) comments, provides r09.
Devaki (Nokia) comments and provides r10.
Youngkyo(Samsung) replies.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r10
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105019 CR Approval 23.502 CR2783R1 (Rel-17, 'B'): UE context retrieval during registration procedure considering SNPN involved. samsung Rel-17 Revision of S2-2104163r10, merging S2-2104716. Approved Agreed
8.2 S2-2104716 CR Approval 23.502 CR2867 (Rel-17, 'B'): Clarify the target AMF find the source AMF in the SNPN mobility ZTE Rel-17 Merged into S2-2105019 Qianghua (Huawei) comments if this can merge into S2-2104163
Devaki (Nokia) proposes to consider this CR as merged with 4163.
zhendong (ZTE) is fine with me to merge.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 - - - KI#2 related - - Docs:=8 -
8.2 S2-2104024 CR Approval 23.501 CR2564R1 (Rel-17, 'B'): Informative guideline on using existing mechanism for QoS Notification between SNPN and PLMN when using N3IWF Futurewei, ETRI Rel-17 Revision of (Postponed at S2#143E) S2-2100368. Merged into S2-2104331 (Noted) Sebastian (Qualcomm) proposes to merge into S2-2104331
Amanda Xiang ( Futurewei) agrees to merge this into S2-2104331
Jihoon (ETRI) indicates that this CR (S2-2104024) was merged into S2-2104331 and the discussion is in progress in the email thread of the merged CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104331 CR Approval 23.501 CR2918 (Rel-17, 'B'): KI#2 T1: Informative guideline for QoS Notification between overlay network and underlay network Ericsson Rel-17 CC#5: r12 + changes agreed. Revised to S2-2105213. Peter Hedman (Ericsson) provides r01, attempt to merge in content from 4024.
Peter Hedman (Ericsson) re-sending with correct link to r01.
Jihoon (ETRI) replies to Peter (Ericsson).
Belen (Ericsson) provides a response to ETRI
Devaki (Nokia) comments.
Amanda Xiang ( Futurewei ) provides r02
Devaki (Nokia) provides r03.
Jihoon (ETRI) replies to Belen (Ericsson), Devaki (Nokia), and Amanda (Futurewei). In addition, I provide r04.
Jihoon (ETRI) provide r05 with minor changes.
Belen (Ericsson) provides r06.
Hualin (Huawei) comments.
Belen (Ericsson) provides r07.
Hualin(Huawei) provide r08 to clarify 'lower the service requirement'.
Belen (Ericsson) provides r09
Jihoon (ETRI) asks Belen (Ericsson) for clarification.
Belen (Ericsson) replies to ETRI
Devaki (Nokia) objects to original and all revisions other than r03, generalizing it. We can also live without this CR, NEF API is already specified for any AF to use.
Jihoon (ETRI) replies to Belen (Ericsson).
Belen (Ericsson) provides r10, aiming to cover ETRI comments and Nokia concerns
Hualin(Huawei) question why the change in r08 is removed and provide r11.
Belen (Ericsson) provides r12 and asks Huawei if it addresses concerns
==== 8.X, 9.X Revisions Deadline ====
Amanda Xiang ( Futurewei) is fine with r12
Devaki (Nokia) can accept only r03 for this meeting. Objects to the original and other revisions.
Belen(Ericsson) objects to r03.
Belen (Ericsson) asks Nokia why they did not provide comments from r03 to r12 but wait until the very last moment.
==== 8.X, 9.X Final Deadline ====
Devaki (Nokia) recommends that Belen looks in the email thread to see the comments provided early on (starting 19th) and the revision provided early, thus not last minute by any means. In any case, generic paragraph from latest revision is also fine for us but if there are objections to do that, we can live without the CR.
Belen (Ericsson) still thinks that to make this informative annex valuable, it needs to be specific about exposure capabilities, cosigners may have a view.
Then, we propose to agree on the first paragraph in r12, and then add an Editor´s note 'how to use existing QoS notification mechanism between SNPN and PLMN is FFS'.

This Editor´s note is based on the conclusion on the TR: 'Informative guideline on how to use existing QoS notification mechanism between SNPN and PLMN can be provided during the normative phase as informative annex.'
Belen (Ericsson) asks to add this CR for CC#4.
I stored a r13 including an Editor´s note
Amanda Xiang ( Futurewei ) supports Ericsson's proposal.
Jihoon (ETRI) also supports Ericsson's proposal.
Revised
8.2 S2-2105213 CR Approval 23.501 CR2918R1 (Rel-17, 'B'): KI#2 T1: Informative guideline for QoS Notification between overlay network and underlay network Ericsson Rel-17 Revision of S2-2104331r12 + changes. Approved Agreed
8.2 S2-2104216 CR Approval 23.501 CR2718R2 (Rel-17, 'B'): KI#2 T2: Informative guideline for mapping QoS parameters and DSCP marking [Ericsson, Nokia, Nokia Shanghai Bell,] Huawei Rel-17 Revision of (Agreed) S2-2102969. Noted Sebastian (Qualcomm) objects to the CR
Qianghua (Huawei) replies
Peter Hedman (Ericsson) provides questions
Peter Hedman (Ericsson) provides comments
Peter Hedman (Ericsson) provides question whether the proposal requires extensions.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides reply that the logic seems to require normative changes.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104330 CR Approval 23.501 CR2718R3 (Rel-17, 'B'): KI#2 T2: Informative guideline for mapping QoS parameters and DSCP marking Ericsson, [Nokia, Nokia Shanghai Bell] Rel-17 Revision of (Agreed) S2-2102969. r04 agreed. Revised to S2-2105020. Marco (Huawei) ask question for clarifications .
Saso (Intel) provides r01.
Peter Hedman (Ericsson) provides reply
Saso (Intel) replies to Peter.
Devaki (Nokia) shares the same view as Saso (Intel). UE specific SLA and/or configuration in the SMF/PCF as such simply sounds unrealistic and not acceptable.
Saso (Intel) replies to Peter Hedman (Ericsson)
Marco (Huawei) support Saso (Intel) & Devaki (Nokia) and replies to Peter Hedman (Ericsson)
Peter Hedman (Ericsson) provides r02
Saso (Intel) provides r03
Marco (Huawei) commented
Devaki (Nokia) provides r04 to add S-NSSAI to the example.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105020 CR Approval 23.501 CR2718R4 (Rel-17, 'B'): KI#2 T2: Informative guideline for mapping QoS parameters and DSCP marking Ericsson, [Nokia, Nokia Shanghai Bell] Rel-17 Revision of S2-2104330r04. Approved Agreed
8.2 S2-2104174 CR Approval 23.501 CR2902 (Rel-17, 'F'): Simultaneous data service from PNI-NPN and PLMN Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2105021. Peter Hedman (Ericsson) provides r01
Devaki (Nokia) comments.
Sebastian (Qualcomm) provides r02
Peter Hedman (Ericsson) provides r0x
Qianghua (Huawei) provides r04
Josep (DT) comments, provides r05, co-signs.
Haris(Qualcomm) provides r06 that corrects coversheet
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105021 CR Approval 23.501 CR2902R1 (Rel-17, 'F'): Simultaneous data service from PNI-NPN and PLMN Huawei, HiSilicon Rel-17 Revision of S2-2104174r06. Approved Agreed
8.2 - - - KI#3 related - - Docs:=9 -
8.2 S2-2103762 LS In Information LS on limited service availability of an SNPN CT WG1 (C1-212601) Rel-17 CC#5: This was postponed. Postponed
8.2 S2-2103808 CR Approval 23.167 CR0360R3 (Rel-17, 'B'): KI#3: Support for IMS emergency over SNPN Ericsson, Qualcomm Incorprorated, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2102971. CC#5: r01 agreed. Revised to S2-2105205. Dieter (Deutsche Telekom) provides r01.
Hualin(Huawei) object the original version and r01 and provides r02.
Antoine (Orange) is fine with r01 and cannot accept r02.
Rainer (Nokia) replies.
Hualin(Huawei) replied to Rainer (Nokia).
==== 8.X, 9.X Revisions Deadline ====
Dieter (Deutsche Telekom) asks a question for clarification.
Haris(Qualcomm) comments
Hualin(Huawei) is ok with Haris(Qualcomm) proposal.
Rainer (Nokia) is ok with the proposal.
Dieter (Deutsche Telekom) would be ok with such proposal as long as this does not require any additional normative changes .
Haris(Qualcomm) proposes post-deadline r03 for CC#4
Antoine (Orange) does not agree with Haris's proposal because this is late input to the meeting.
==== 8.X, 9.X Final Deadline ====
Haris(Qualcomm) is ok with any revision
Revised
8.2 S2-2105205 CR Approval 23.167 CR0360R4 (Rel-17, 'B'): KI#3: Support for IMS emergency over SNPN Ericsson, Qualcomm Incorprorated, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103808r01. Approved Agreed
8.2 S2-2104579 CR Approval 23.501 CR2649R3 (Rel-17, 'C'): Support for IMS emergency services over SNPN Qualcomm Incorprorated, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2102973. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.2 S2-2104541 CR Approval 23.228 CR1243R2 (Rel-17, 'B'): KI#3: IMS Support for SNPN Ericsson, Nokia, Nokia Shanghai Bell, Intel, China Mobile, Huawei Rel-17 Revision of (Agreed) S2-2102970. r02 agreed. Revised to S2-2105022. Haris(Qualcomm) comments that adding the multiple IMS providers for the SNPN requires that the SNPN knows that the ISH that provides IMS service to the UE, which needs to be indicated in signalling and therefore requires normative changes
Rainer (Nokia) comments.
George (Ericsson) proposes to note the CR, and provides a comment.
Hualin(Huawei) replied to the comments.
Saso (Intel) asks Hualin(Huawei) for clarification.
Hualin(Huawei) replied to Saso (Intel).
Hualin(Huawei) replied to the companies.
Saso (Intel) replies to Hualin(Huawei).
Dieter (Deutsche Telekom) proposes to keep the 1:1 relationship and note this CR .
Hualin(Huawei) replied to Dieter (Deutsche Telekom) and provide r01.
Haris(Qualcomm) comments that Credentials Holder (CH) is not the right term to be used in IMS context
Dieter (Deutsche Telekom) comments
Hualin(Huawei) replied to Dieter (Deutsche Telekom) and provide r02.
==== 8.X, 9.X Revisions Deadline ====
Dieter (Deutsche Telekom) can live with r02...
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105022 CR Approval 23.228 CR1243R3 (Rel-17, 'F'): KI#3: IMS Support for SNPN Ericsson, Nokia, Nokia Shanghai Bell, Intel, China Mobile, Huawei Rel-17 Revision of S2-2104541r02. Approved Agreed
8.2 S2-2104182 DISCUSSION Discussion Discussion for IMS voice over Overlay network. Huawei, HiSilicon Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104183 CR Approval 23.501 CR2903 (Rel-17, 'C'): IMS voice over overlay network Huawei, HiSilicon Rel-17 r10 agreed. Revised to S2-2105023. George (Ericsson) objects to the CR. Please see additional comments
Haris (Qualcomm) agrees that large part of the CR is not needed
Qianghua (Huawei) replies
Rainer (Nokia) comments and proposes way forward.
Saso (Intel) repeats comment from previous meeting (S2-2102251) and proposes to NOTE or re-purpose the CR.
Qianghua (Huawei) provides r01
Rainer (Nokia) replies.
Saso (Intel) thinks there is a misunderstanding.
Saso (Intel) replies to Qianghua.
Qianghua (Huawei) replies and provides r02
Rainer (Nokia) provides r03.
Saso (Intel) seeks further clarification.
Saso (Intel) replies to Qianghua (Huawei)
Saso (Intel) replies to Rainer.
Rainer (Nokia) replies to Saso (Intel).
Qianghua (Huawei) provides r04
Saso (Intel) provides r05
Haris(Qualcomm) provides r06
Qianghua (Huawei) provides r07
Haris(Qualcomm) provides r08 which perform editorial changes in the coversheet
Dieter (Deutsche Telekom) we propose to note this CR.
Qianghua (Huawei) provides r09
Saso (Intel) notes that the CR category should now be 'D' or 'F', instead of 'C'
Qianghua (Huawei) provides r10
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. This is no longer a FASMO CR.
Qianghua (Huawei) responds to George (Ericsson), this is Rel-17 CR, 'FASMO' not apply
Antoine (Orange) r10 is a correct Cat. F CR and it should be approved.
Dieter (Deutsche Telekom) can only accept r10.
Rainer (Nokia) is fine with r10.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105023 CR Approval 23.501 CR2903R1 (Rel-17, 'C'): IMS voice over overlay network Huawei, HiSilicon Rel-17 Revision of S2-2104183r10. Approved Agreed
8.2 - - - KI#4 related - - Docs:=31 -
8.2 S2-2104678 CR Approval 23.501 CR2969 (Rel-17, 'B'): Definition of SNPN-related terms Orange Rel-17 r05 agreed. Revised to S2-2105024. Rainer (Nokia) provides r01.
xiaowan (vivo) provides r02
Rainer (Nokia) replies.
Antoine (Orange) provides r03.
Rainer (Nokia) provides r04.
Xiaowan (vivo) replies.
Peter Hedman (Ericsson) provides r05
==== 8.X, 9.X Revisions Deadline ====
Xiaowan(vivo) is OK with r05
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105024 CR Approval 23.501 CR2969R1 (Rel-17, 'B'): Definition of SNPN-related terms Orange Rel-17 Revision of S2-2104678r05. Approved Agreed
8.2 S2-2104028 CR Approval 23.501 CR2562R3 (Rel-17, 'B'): UE onboarding Ericsson, Qualcomm, MediaTek Inc., Nokia, Nokia Shanghai Bell, Futurewei, Convida Wireless, Intel, InterDigital, OPPO, CATT, Samsung, ETRI Rel-17 Revision of (Agreed) S2-2102974. Merged into S2-2105025 Megha(Intel) provides comments.
Rainer (Nokia) agrees with Megha (Intel) and proposes to merge parts of 4028 with 4334.
Jihoon (ETRI) replies to Rainer (Nokia) and Megha (Intel).
Hualin(Huawei) comments.
xiaowan (vivo) provides comments
Peter Hedman (Ericsson) provides comments and propose to mark the CR as merged into 04334.
Jihoon (ETRI) replies to Hualin (Huawei), Peter (Ericsson), and Xiaowan (Vivo).
Jihoon (ETRI) indicates that this CR (S2-2104028) was merged into S2-2104334 and the further discussion is in progress in the email thread of the merged CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104217 CR Approval 23.501 CR2562R4 (Rel-17, 'B'): UE onboarding [Ericsson, Qualcomm, MediaTek Inc., Nokia, Nokia Shanghai Bell, Futurewei, Convida Wireless, Intel, InterDigital, OPPO, CATT, Samsung,] Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2102974. Merged into S2-2105025 Wen (vivo) provides comments and r01.
Rainer (Nokia) provides r02.
Megha(Intel) provides r03.
Peter Hedman (Ericsson) proposes to merge r03 into 04334 and mark this as merged into 04334
Qianghua (Huawei) OK to merge this merged into 04334
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104334 CR Approval 23.501 CR2562R5 (Rel-17, 'B'): UE onboarding Ericsson, Qualcomm, MediaTek Inc., Nokia, Nokia Shanghai Bell, Futurewei, Convida Wireless, Intel, InterDigital, OPPO, CATT, Samsung, ZTE Rel-17 Revision of (Agreed) S2-2102974. r09 agreed. Revised to S2-2105025, merging S2-2104028, S2-2104217 and S2-2104431 Jihoon (ETRI) provides r01.
Qianghua (Huawei) provides r02, merging S2-2104229r03
Jihoon (ETRI) replies to Qianghua, Hualin (Huawei), Peter (Ericsson), and Xiaowan (Vivo). In addition, I provide r03.
Qianghua (Huawei) replies, asks to correct my previous comments: 'provides r02, merging S2-2104229r03' to 'provides r02, merging S2-2104217r03'
Yunjing (CATT) provides r04 to merge the first change in S2-2104431r01.
Antoine (Orange) provides r05.
Peter Hedman (Ericsson) provides r06
Hualin(Huawei) comments on r06 and provide r07.
Jihoon (ETRI) asks for clarification.
Antoine (Orange) provides r11.
Peter Hedman (Ericsson) provides reply
Peter Hedman (Ericsson) provides reply.
Hualin (Huawei) provides r09
==== 8.X, 9.X Revisions Deadline ====
Jihoon (ETRI) replies to Peter (Ericsson).
==== 8.X, 9.X Final Deadline ====
Jarmo (KPN) provides reply
Revised
8.2 S2-2105025 CR Approval 23.501 CR2562R7 (Rel-17, 'B'): UE onboarding Ericsson, Qualcomm, MediaTek Inc., Nokia, Nokia Shanghai Bell, Futurewei, Convida Wireless, Intel, InterDigital, OPPO, CATT, Samsung, ZTE Rel-17 Revision of S2-2104334r09, merging S2-2104028, merging S2-2104028, S2-2104217 and S2-2104431. Approved Agreed
8.2 S2-2104431 CR Approval 23.501 CR2562R6 (Rel-17, 'B'): UE onboarding CATT Rel-17 Revision of (Agreed) S2-2102974. Merged into S2-2105025 Wen (vivo) provides comments.
Rainer (Nokia) proposes to note 4431.
Yunjing (CATT) replies to comments.
Rainer (Nokia) replies.
Peter Hedman (Ericsson) provides comment and ask for conclusion before merging into 04334.
Fei (OPPO) comments
Yunjing (CATT) replies to comments and provides r01.
Hualin(Huawei) cannot accept r01.
Xiaowan (vivo) replies to Hualin(Huawei)
Rainer (Nokia) proposes to remove second change in 5.30.2.X.4.3 and merge rest with 4334.
Yunjing (CATT) replies to Hualin(Huawei).
Yunjing (CATT) is fine to merge this CR into 4334.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.2 S2-2104335 CR Approval 23.501 CR2921 (Rel-17, 'B'): UE onboarding architecture Ericsson, Rel-17 Noted Megha(Intel) asks question for clarification.
Peter Hedman (Ericsson) provides reply and ask for more opinions on the proposed architecture changes as to decide whether it can be merged into 04334.
Megha(Intel) provides comments and questions if option 2 is a viable option.
Haris(Qualcomm) comments that option 2 is the most viable of the two options based on existing products and deployments
Megha(Intel) provides comments.
Peter Hedman (Ericsson) provides reply and asks again if we can merge in changes to 04434.
Hualin(Huawei) support the architecture and co-sign this paper in r01.
Haris(Qualcomm) answers
Saso (Intel) asks further clarification from Haris(Qualcomm)
Peter Hedman (Ericsson) provides a question.
Saso (Intel) replies to Haris(Qualcomm)
Saso (Intel) provides r02.
Chris (Vodafone) asks how the user plane is enabled without a UDM/N8 in option 1.
Rainer (Nokia) prefers r01.
Walter (Philips) has comment
Saso (Intel) provides r03.
Saso (Intel) replies to Chris (Vodafone).
Antoine (Orange) prefers r03 (i.e. option 1).
Haris(Qualcomm) objects to r02 and r03
==== 8.X, 9.X Revisions Deadline ====
Saso (Intel) objects to r00 and r01
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104613 CR Approval 23.501 CR2955 (Rel-17, 'B'): AMF selection to support UE onboarding SNPN Intel Rel-17 r01 agreed. Revised to S2-2105026. Peter Hedman (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105026 CR Approval 23.501 CR2955R1 (Rel-17, 'B'): AMF selection to support UE onboarding SNPN Intel Rel-17 Revision of S2-2104613r01. Approved Agreed
8.2 S2-2104651 CR Approval 23.501 CR2965 (Rel-17, 'C'): AUSF selection for an Onboarding UE Vivo, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2105027. Qianghua (Huawei) asks if this CR can be merged with S2-2104542
Xiaowan(vivo) replies Qianghua (Huawei) S2-2104651 and S2-2104542 discuss different detail and are not suitable to be merged.
Josep (DT) objects to this CR.
Rainer (Nokia) provides r01.
Josep (DT) can live with r01.
Qianghua (Huawei) provides comments
Xiaowan(vivo) replies to Josep (DT)
Josep (DT) apologizes for the confusion. Retracts objection, still prefers r01
Rainer (Nokia) replies.
Josep (DT) comments on r00 being not clear.
Qianghua (Huawei) provides r02
Rainer (Nokia) provides r03.
Peter Hedman (Ericsson) provides r04
Rainer (Nokia) is ok with r04.
Xiaowan(vivo) comments and provides r05
Rainer (Nokia) provides r06.
==== 8.X, 9.X Revisions Deadline ====
Qianghua (Huawei) accepts r04, r03, r02; objects r00, r01, r05, r06
Xiaowan(vivo) is OK with r04.
Peter Hedman (Ericsson) ok with r04
Megha (Intel) is ok with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105027 CR Approval 23.501 CR2965R1 (Rel-17, 'C'): AUSF selection for an Onboarding UE Vivo, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104651r04. Approved Agreed
8.2 S2-2104229 CR Approval 23.502 CR2632R2 (Rel-17, 'B'): Registration Procedure for UE Onboarding [Intel, Ericsson, MediaTek Inc.], Huawei Rel-17 Revision of (Agreed) S2-2102975. r06 agreed. Revised to S2-2105028. Megha(Intel) provides r01, comments and proposes to merge parts of this contribution(Registration procedure) to S2-2104622.
Wen (vivo) provides comments and r02.
Rainer (Nokia) provides r03.
Haris(Qualcomm) objects to all revisions (r0-r03)
Qianghua (Huawei) replies and provides r04
Antoine (Orange) provides r05 (only fixing the cover sheet of the CR agreed at SA2#144e).
Qianghua (Huawei) provides r06
Josep (DT) also sees only necessary to update 4.2.2.2.1, other changes seen as not required.
Malla (NTT DOCOMO) indicated that unaffected clauses should be removed from the CR.
==== 8.X, 9.X Revisions Deadline ====
Rainer (Nokia) replies.
Qianghua (Huawei) responds to Haris(Qualcomm), the change in 4.2.2.2.1 is exactly the same with S2-2102975 (which is approved in last meeting), the latest revision only corrects the cover page and add new 'co-signing' company
Antoine (Orange) is OK with r06, which is only fixing the cover sheet of the CR agreed at SA2#144e and adding supporting companies.
Megha (Intel) is ok with r06.
Haris(Qualcomm) is ok with r06 (pls ignore my previous message)
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105028 CR Approval 23.502 CR2632R3 (Rel-17, 'B'): Registration Procedure for UE Onboarding [Intel, Ericsson, MediaTek Inc.], Huawei Rel-17 Revision of S2-2104229r06. Approved Agreed
8.2 S2-2104622 CR Approval 23.502 CR2849 (Rel-17, 'B'): Registration procedure for UE onboarding SNPN Intel, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 r12 agreed. Revised to S2-2105029. Megha(Intel) provides r01.
Wen (vivo) provides comments and r02.
Qianghua (Huawei) provides r03
Rainer (Nokia) provides r04.
Fei (OPPO) provides r05.
Qianghua (Huawei) provides r06
Youngkyo(Samsung) provides a comment.
Rainer (Nokia) replies.
Qianghua (Huawei) replies
Rainer (Nokia) is ok with the proposed text.
Qianghua (Huawei) provides r08
Rainer (Nokia) is ok with r08.
Haris(Qualcomm) asks question for clarification
Peter Hedman (Ericsson) provides r09
Haris(Qualcomm) provides r10
Antoine (Orange) asks why EIR check is skipped.
Megha(Intel) responds to the question from Antoine (Intel).
Haris(Qualcomm) comments
Megha(Intel) responds to the question from Antoine (Orange).
Megha (Intel) provides r11 and some comments.
Peter Hedman (Ericsson) provides r12
==== 8.X, 9.X Revisions Deadline ====
Megha (Intel) is fine with r12.
Rainer (Nokia) is ok with r12.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105029 CR Approval 23.502 CR2849R1 (Rel-17, 'B'): Registration procedure for UE onboarding SNPN Intel, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2104622r12. Approved Agreed
8.2 S2-2104692 CR Approval 23.502 CR2860 (Rel-17, 'B'): Onboarding Indication in RRC Connection Establishment Samsung Rel-17 Noted Rainer (Nokia) proposes to note 4692.
Kisuk (Samsung) notes 4692.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2103974 CR Approval 23.501 CR2832R2 (Rel-17, 'B'): UE configuration for remote provisioning Vivo?, Nokia, Nokia Shanghai Bell, ETRI?, Intel?, ZTE?, Ericsson? Rel-17 Revision of (Agreed) S2-2102980. Confirm Sources! Merged into S2-2103980 (Noted at CC#4) Jihoon (ETRI) provides comments.
Rainer (Nokia) replies.
Hualin(Huawei) don't understand the paper and comments.
xiaowan (vivo) provides r01
Rainer (Nokia) provides r02.
Hualin(Huawei) replies to Rainer (Nokia).
Jianning (Xiaomi) provides comment
Rainer (Nokia) replies to Hualin (Huawei).
Xiaowan(vivo) replies to Rainer (Nokia) and requests to merge S2-2103974 into S2-2103980
Rainer (Nokia) replies to Jianning (XIAOMI).
Rainer (Nokia) replies to Xiaowan (vivo).
Rainer (Nokia) proposes to mark 3974 as merged into 3980.
Hualin(Huawei) replied to Rainer (Nokia).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2103980 CR Approval 23.501 CR2832R3 (Rel-17, 'B'): UE configuration for remote provisioning Vivo, Nokia, Nokia Shanghai Bell, ETRI, Intel, ZTE, Ericsson Rel-17 Revision of (Agreed) S2-2102980. CC#4: Noted Jihoon (ETRI) asks a question on what has been changed.
xiaowan (vivo) replies to Jihoon (ETRI)
xiaowan (vivo) provides r01
Hualin(Huawei) propose to note this paper.
Jihoon (ETRI) replies to Hualin (Huawei).
Jihoon (ETRI) provides comments.
Rainer (Nokia) replies.
Jihoon (ETRI) replies to Rainer (Nokia) and provides r02.
Peter Hedman (Ericsson) provides reply.
Hualin(Huawei) provides reply and r03.
Jihoon (ETRI) replies to Peter (Nokia).
Rainer (Nokia) asks for clarification.
Peter Hedman (Ericsson) provides comments and question.
Rainer (Nokia) comments.
Hualin(Huawei) replied to Rainer (Nokia).
Hualin(Huawei) replied to Peter Hedman (Ericsson).
Rainer (Nokia) replies to Hualin (Huawei).
Xiaowan(vivo) comments
Haris(Qualcomm) comments
Genadi (Lenovo) provides comments.
Hualin(Huawei) replied to Genadi (Lenovo).
Hualin(Huawei) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Haris(Qualcomm) prefers r01, if not agreeable, better to 'fallback' to what is agreed in SA2#144: S2-2102980
Peter Hedman (Ericsson) also prefer r01 and if not agreeable we propose to NOTE the CR and fallback to what was approved at SA2#144E
Xiaowan(vivo) is OK with r01, 02, 03 and 04
Rainer (Nokia) is ok with r01 and r02.
Hualin (Huawei) can only accept r03 and r04.
Another way is to bring it to CC#4 and add an EN 'in case DCS provide the address, whether the application layer based solution is proper to assist the UE to identify the PVS Server in case multiple PVS Servers exist is FFS ' based on r01.
Megha (Intel) prefers r01.
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104546 CR Approval 23.501 CR2832R4 (Rel-17, 'B'): UE configuration for remote provisioning Vivo, Nokia, Nokia Shanghai Bell, ETRI, Intel, ZTE, Ericsson, [Huawei] Rel-17 Revision of (Agreed) S2-2102980. 23.501 CR2992 allocated for revision of this CR. r08 agreed. Revised to S2-2105030. Megha(Intel) provides comments.
Hualin(Huawei) replies to Megha(Intel).
Rainer (Nokia) provides r01.
xiaowan (vivo) provides comments
Rainer (Nokia) prefers r01.
Megha(Intel) provides some comments.
Haris(Qualcomm) provides comments
Xiaowan provides comments and r03
Hualin(Huawei) reply.
Hualin(Huawei) replied to Rainer (Nokia).
Hualin(Huawei) replied to Haris(Qualcomm) and Megha(Intel)
Peter Hedman (Ericsson) provides comments and asks if the CR can be considered merged into 03980?
Haris(Qualcomm) supports to note this CR and focus on 03980 since content is overlapping
Hualin(Huawei) is ok to merge the change in first paragraph into 03980. But not other changes, since current 03980 doesn't cover other changes in 4546.
xiaowan (vivo) replies to Hualin(Huawei)
Hualin(Huawei) ask whether a new number should be allocated or not?
Jihoon (ETRI) makes a correction on Tdoc number in the Hualin (Huawei)'s comment.
Hualin(Huawei) disagree to note this paper and replied to Haris(Qualcomm)
Antoine (Orange): provides r05 to make it a new CR.
Rainer (Nokia) asks for clarification.
Hualin(Huawei) replied to Rainer (Nokia) that we are requesting new CR number for this paper from Maurice or Puneet.
Maurice (MCC) Allocates 23.501 CR2992 for this new CR.
Hualin(Huawei) provide r06 with the new CR number from Maurice.
Rainer (Nokia) provides r07.
Hualin(Huawei) thanks for the support and ok with r07.
Haris(Qualcomm) comments on r07
Peter Hedman (Ericsson) provides r08
Hualin(Huawei) replied to Peter Hedman (Ericsson) and Haris(Qualcomm).
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) provides reply
Hualin(Huawei) replied to Peter Hedman (Ericsson).
==== 8.X, 9.X Final Deadline ====
Hualin(Huawei) suggest to bring this paper to CC#4 to correct the source companies in the chairman notes.
The source companies should be 'Huawei, Nokia, Nokia Shanghai Bell', but not 'Vivo, Nokia, Nokia Shanghai Bell, ETRI, Intel, ZTE, Ericsson, [Huawei]'.
Because we have requested a new CR number for this paper and this paper is not rely on the agreed paper in last meeting anymore.
Peter Hedman (Ericsson) provides question
Hualin(Huawei) replied. Yes, it is also to get CR number correct in the chair notes.
Revised
8.2 S2-2105030 CR Approval 23.501 CR2992 (Rel-17, 'B'): UE configuration for remote provisioning Vivo, Nokia, Nokia Shanghai Bell, ETRI, Intel, ZTE, Ericsson, [Huawei] Rel-17 Revision of S2-2104546r08 (CR number changed to 2992). Approved Agreed
8.2 S2-2103973 CR Approval 23.503 CR0565R2 (Rel-17, 'B'): KI#4-T3, Enabling restricted PDU Session for remote provisioning of UE using User Plane ZTE, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2102979. r01 agreed. Revised to S2-2105031. Mirko (Huawei) proposes r01.
Rainer (Nokia) is fine with 01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105031 CR Approval 23.503 CR0565R3 (Rel-17, 'B'): KI#4-T3, Enabling restricted PDU Session for remote provisioning of UE using User Plane ZTE, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103973r01. Approved Agreed
8.2 S2-2104184 CR Approval 23.501 CR2755R2 (Rel-17, 'B'): De-registration for onboarding registered UE Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2102976. r12 agreed. Revised to S2-2105032. Rainer (Nokia) provides r01.
Haris(Qualcomm) objects to r0, comments on r01
Rainer (Nokia) provides r02.
Qianghua (Huawei) provides r03
Youngkyo(Samsung) provides r04
Rainer (Nokia) is ok with r03.
Xiaowan (vivo) comments and provides r05.
Qianghua (Huawei) replies
Youngkyo(Samsung) provides comments.
Fei (OPPO) comments on r04.
Fei (OPPO) asks for clarification.
Qianghua (Huawei) provides r06
Youngkyo(Samsung) replies.
Xiaowan(vivo) replies to Qianghua (Huawei)
xiaowan (vivo) replies to Qianghua (Huawei) and provides r07
Josep (DT) also supports to have 'deregistration of ON-PLMN' as a NOTE.
Qianghua (Huawei) provides r09
Peter Hedman (Ericsson) provides r10
Antoine (Orange) provides r11.
Amanda Xiang (Futurewei) provides r12
Amanda Xiang (Futurewei) provides r12.
==== 8.X, 9.X Revisions Deadline ====
Haris(Qualcomm) comments that Antoine is right and AMF relocation needs to be considered
Qianghua (Huawei) agrees the question from Haris(Qualcomm), we are either OK to add the EN or bring proposal for this directly next meeting
Antoine (Orange) objects to r12 and proposes to add an EN to make it acceptable.
Qianghua (Huawei) OK with the EN, proposes to confirm this at CC#4 if required, and provides r13 based on r12, adding the EN 'Whether AMF re-allocation is supported for a UE registered for the purpose of onboarding and how the deregistration timer is handled in this case is FFS.'
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105032 CR Approval 23.501 CR2755R3 (Rel-17, 'B'): De-registration for onboarding registered UE Huawei, HiSilicon Rel-17 Revision of S2-2104184r12. Approved Agreed
8.2 S2-2104690 CR Approval 23.502 CR2859 (Rel-17, 'B'): Update Deregistration procedure for UE Onboarding Samsung Rel-17 Noted Rainer (Nokia) provides r01.
Haris(Qualcomm) objects to the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104542 CR Approval 23.501 CR2942 (Rel-17, 'F'): Onboarding SUCI and SUPI Huawei, Hisilicon Rel-17 Noted Wen (vivo) provides comments.
Hualin(Huawei) replied to Wen (vivo).
Rainer (Nokia) provides r01.
Megha(Intel) questions the need for this CR.
Hualin (Huawei) is ok with r01.
Peter Hedman (Ericsson) also question the need for the CR
Hualin(Huawei) replied to Peter Hedman (Ericsson) and provide r02.
Malla (NTT DOCOMO) agrees with Ericsson and Intel, and also question the need for the CR
Dieter (Deutsche Telekom) agrees with NTT DOCOMO, Ericsson and Intel, and also question the need for the CR.
Hualin(Huawei) replied to Dieter (Deutsche Telekom), Malla(NTT DOCOMO).
Antoine (Orange) proposes to Note this CR.
Josep (DT) objects to this CR.
Hualin(Huawei) is ok to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104604 CR Approval 23.501 CR2950 (Rel-17, 'B'): UE supported NPN credentials provisioned using UPU MediaTek Inc. Rel-17 Noted Jianning (Xiaomi) provides comments
Chia-Lin (MediaTek) provides r01
Youngkyo(Samsung) provides the revision r02
Rainer (Nokia) proposes to note the paper.
Chia-Lin (MediaTek) provides response
Rainer (Nokia) replies.
Qianghua (Huawei) replies
Chia-Lin (MediaTek) ask for the clarification
Jianning (Xiaomi) provides comment and seek for clarification
Xiaowan(vivo) share the view with Rainer (Nokia)
Haris(Qualcomm) proposes to note the CR
Jianning (Xiaomi) replies
Jianning (Xiaomi) seeks clarification
Rainer (Nokia) sees no justification for 4604 and proposes to note it.
Peter Hedman (Ericsson) provides comments
Jianning (Xiaomi) replies to Qianghua (Huawei)
Jianning (Xiaomi) shares the view with Peter (Ericsson)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.2 S2-2104605 CR Approval 23.502 CR2845 (Rel-17, 'B'): UE supported NPN credentials provisioned using UPU MediaTek Inc. Rel-17 Merged into S2-2104338 (Posponed at CC#4) Hualin(Huawei) ask for clarification.
Rainer (Nokia) proposes to remove SNPN credentials and merge the rest with 4338.
xiaowan (vivo) provides comments
Chia-Lin (MediaTek) provides response
Chia-Lin (MediaTek) provides r01 based on the comments
Youngkyo(Samsung) suggest merging with S2-2104338
Rainer (Nokia) agrees that 4605r1 should be merged with 4338.
Haris(Qualcomm) provides comment
Amanda Xiang (Futurewei) support to merge this with S2-2104338
Hualin(Huawei) replied to Chia-Lin (MediaTek)
Rainer (Nokia) asks for clarification.
Hualin(Huawei) replied to Rainer (Nokia).
Peter Hedman (Ericsson) provides comments and hope we can consider CR merged with 04338
Chia-Lin (MediaTek) is ok to be merged with S2-2104338
Rainer (Nokia) replies.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.2 S2-2104658 CR Approval 23.501 CR2714R2 (Rel-17, 'B'): Remote provisioning of credentials for NSSAA or secondary authentication/authorisation China Mobile, OPPO, Huawei, HiSilcon, Ericsson, Lenovo, Motorola Mobility Rel-17 Revision of (Agreed) S2-2102981. r10 agreed. Revised to S2-2105033. Rainer (Nokia) provides r01.
Genadi (Lenovo) provides comments to Rainer (Nokia).
Rainer (Nokia) replies.
Yi (China Mobile) comments and provides r02.
Genadi (Lenovo) replies to Rainer (Nokia) and Yi (CMCC) and provides r03.
Fei (OPPO) provides r04.
Genadi (Lenovo) is OK with r04.
Haris(Qualcomm) provides r06
Hualin (Huawei) have comments on r04 and provide r05.
xiaowan (vivo) provides r07
Peter Hedman (Ericsson) provides r08
Malla (NTT DOCOMO) provides comment
Genadi (Lenovo) provides comments to the revisions and will provide a revision depending on the replies.
Haris(Qualcomm) responds
Genadi (Lenovo) provides further comments.
Hualin(Huawei) replied to Genadi (Lenovo).
Genadi (Lenovo) provides r09 to implement the recent discussions.
Rainer (Nokia) comments.
Hualin(Huawei) replied and provide r10.
Genadi (Lenovo) provides reply to Rainer.
Genadi (Lenovo) is OK with r10.
Rainer (Nokia) is ok with r10.
==== 8.X, 9.X Revisions Deadline ====
Peter Hedman (Ericsson) ok with r10 and provides some comments
Genadi (Lenovo) provides comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.2 S2-2105033 CR Approval 23.501 CR2714R3 (Rel-17, 'B'): Remote provisioning of credentials for NSSAA or secondary authentication/authorisation China Mobile, OPPO, Huawei, HiSilcon, Ericsson, Lenovo, Motorola Mobility Rel-17 Revision of S2-2104658r10. Approved Agreed
8.3 - - - Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) - - Docs:=177 -
8.3 - - - General - - Docs:=15 -
8.3 S2-2103728 LS In Information LS from GSMA Operator Platform Group on edge computing definition and integration GSMA OPG (OPG_52_Doc_03) Revision of Postponed S2-2102129 from S2#144E. Response drafted in S2-2103864 and S2-2104612. Postponed Postponed
8.3 S2-2103746 LS In Information LS from ETSI ISG MEC: LS reply to GSMA Operator Platform Group on edge computing definition and integration ETSI ISG MEC (MEC(21)000164r3) Noted Hui (Huawei) proposes to note this LS as this is sent to SA2 for information.
Magnus (Ericsson) also proposes to note this LS
Noted
8.3 S2-2103743 LS In Information LS from SA WG6: Reply LS on Edge computing definition and integration SA WG6 (S6-210976) Rel-17 Noted Hui (Huawei) proposes to note this LS as this is sent to SA2 for information Noted
8.3 S2-2103744 LS In Action LS from SA WG6: 3GPP Edge Computing coordination SA WG6 (S6-2109783) Rel-17 Response drafted in S2-2103865. Final response in S2-2105034 Replied to
8.3 S2-2103865 LS OUT Approval [DRAFT] LS on 3GPP Edge Computing coordination Ericsson Rel-17 Response to S2-2103728 and S2-2103744. Merged into S2-2105034 Jicheol (Samsung) comments and proposes to merge this paper to S2-2104612 (Samsung proposal for LS response).
Magnus (Ericsson) I don't mind to much which version we use as a base but I think we should include a description/pointers to the SA2 edge work as well as all the interfaces in the GSMA OPG LS as in the Ericsson proposed LS.
Jicheol (Samsung) thanks Magnus and propose to move this thread to S2-2104612.
Magnus (Ericsson) we can consider this doc merged into 4612..
Jicheol (Samsung) agree with Magnus(Ericsson). we can mark this doc merged into S2-2104612.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2103864 LS OUT Approval [DRAFT] Reply LS on edge computing definition and integration. Ericsson Rel-17 Response to S2-2103728. Merged into S2-2105034 Jicheol (Samsung) proposes to note (or postpone) LS response to GSMA Operator Platform Group.
Dario S. Tonesi (Qualcomm) supports noting any reply LS to GSMA (it's better to liaise SA plenary instead).
Hui (Huawei) proposes to postpone the LS reply to GSMA.
Magnus (Ericsson) provides some answers.
Dario S. Tonesi (Qualcomm) replies to Magnus.
Laurent (Nokia): Comments /question
Magnus (Ericsson): It's fine to Note or consider this merged into 4612.
Jicheol (Samsung) agrees with Magnus(Ericsson). we can mark this doc merged into S2-2104612.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104612 LS OUT Approval [DRAFT] LS reply to SA on GSMA 3GPP Edge Computing coordination Samsung Rel-17 Response to S2-2103728. r12 agreed. Revised to S2-2105034, merging S2-2103864, S2-2103865 and S2-2104481 Dan (China Mobile) comments
Hui (Huawei) provides r01
Jicheol (Samsung) is fine with r01 and provides r02 for further update to capture Dan and Ericssons' comments (to capture SA2 edge work).
Dan(China Mobile) provides r03 with editorial update for SA2 EC work part
Magnus (Ericsson) provides r04.
Dario S. Tonesi (Qualcomm) provides r05
Tingfang (Lenovo) provides r06
Laurent (Nokia): provides r07
Magnus (Ericsson): provides r08
Jicheol (Samsung) provides r09.
Hui (Huawei): provides r09
Hui (Huawei) provides r10.
Laurent (Nokia): provides r11
Magnus O (Ericsson): Objects to r11 and provides r12
Susana (Vodafone) asks whether there is any action to SA5 and SA6
Jicheol answers.
==== 8.X, 9.X Revisions Deadline ====
Jicheol (Samsung) also objects to r11 and agrees with r12.
Dario S. Tonesi (Qualcomm) is fine with r12, but SA5/6 should be in CC
Hui (Huawei) is fine with r12, but SA5/6 should be in CC
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105034 LS OUT Approval LS reply to SA on GSMA 3GPP Edge Computing coordination SA WG2 Rel-17 Revision of S2-2104612r12, merging S2-2103864, merging S2-2103864 and S2-2103865, merging S2-2103864, S2-2103865 and S2-2104481. Approved Approved
8.3 S2-2104481 LS OUT Approval [DRAFT] LS on edge computing definition and integration Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2105034 Jicheol (Samsung) proposes to note this LS response to GSMA Operator Platform Group.
(And discuss the issues in the context of S2-2103864 - Ericsson LS response to GSMA OPG).
Dario S. Tonesi (Qualcomm) supports noting this LS and focusing on liaising SA pleanry instead.
Laurent (Nokia): Comments: I don't mind to much which version we use as a base, so OK to merge 4481 in 4612
Jicheol (Samsung) is okay this doc merged into S2-2104612.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104001 P-CR Approval 23.548: 23.548 should be equally applicable to PLMN(s) and to SNPN(s). Nokia, Nokia Shanghai Bell Rel-17 Postponed Hui (Huawei) provides r01.
Dan(China Mobile) provides r02.
Laurent (Nokia): provides r03
Dieter (Deutsche Telekom) comments.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): answers
Hui (Huawei) objects to rev with EN.
Dieter (Deutsche Telekom) proposes to postpone this paper.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2104038 P-CR Agreement 23.548: General aspects for ECS procedure. Xiaomi Rel-17 r05 agreed. Revised to S2-2105035. Laurent (Nokia): Provides r01
Hui (Huawei): Provides r02
Dong (Xiaomi): Provide comments.
Magnus (Ericsson): Provides r03
Dong (Xiaomi): Provide r04.
Dario S. Tonesi (Qualcomm) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105035 P-CR Agreement 23.548: General aspects for ECS procedure. Xiaomi Rel-17 Revision of S2-2104038r05. Approved Approved
8.3 S2-2104169 P-CR Approval 23.548: Considerations for UE's with WLAN access not connected to 5GS . Sony Rel-17 Noted Laurent (Nokia): Asks questions and indicates that to accept this Tdoc he expects answers to these questions
Svante (Sony): Provides clarifications on questions.
Hui (Huawei) provides r01.
Jicheol (Samsung) do not understand the intention of this paper also do not agree some statements.
Huazhang (vivo) technique discussion to Svante
Laurent (Nokia): Comments
Svante (Sony): adds clarifications
Jicheol (Samsung) objects to pCR including incorrect statements.
Magnus (Ericsson) comments.
Svante (Sony) provides r02 and comments
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version of this Tdoc
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104502 P-CR Approval 23.548: TS clean up. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2105036. Dong (Xiaomi) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105036 P-CR Approval 23.548: TS clean up. Huawei, HiSilicon Rel-17 Revision of S2-2104502r01. Approved Approved
8.3 - - - EAS discovery - - Docs:=54 -
8.3 S2-2103742 LS In Action LS from SA WG4: LS on App ID Usage in NEF Related Service API in Rel 17 SA WG4 (S4-210681) Rel-17 Noted Hui (Huawei) proposes to note this LS as this issue has been already resolved and replied in S2-2103228.
Pallab (Nokia) supports the view from Hui (Huawei) also proposes to note this LS
Noted
8.3 S2-2104503 P-CR Approval 23.548: Remove ENs in clause 6.2.3. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2105037. Laurent (Nokia): provides r01
Hui(Huawei) fine with r01
Dario S. Tonesi (Qualcomm) provides r02
Hui (Huawei) fine with r02 as well.
Laurent (Nokia): provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105037 P-CR Approval 23.548: Remove ENs in clause 6.2.3. Huawei, HiSilicon Rel-17 Revision of S2-2104503r03. Approved Approved
8.3 S2-2103852 CR Approval 23.501 CR2862 (Rel-17, 'B'): EASDF functional description Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2103853 P-CR Approval 23.548: Removing EN in 6.2.3.2.2. related to Session Breakout with EASDF Ericsson Rel-17 Postponed Laurent (Nokia): comments (negative)
Marisa (ericsson): replies
Marisa (ericsson): comments (again)
Tingfang (Lenovo) comments.
Fenqin (Huawei) comments.
Tingfang (Lenovo) replies to Fenqin.
Laurent (Nokia): provides r01
Fenqin (Huawei): provides comment.
Laurent (Nokia): answers
Tingfang (Lenovo) provides r02 based on r01, and r03 based on r00, and ask clarifications on the solution for multiple ECS option for one FQDN.
Marisa (ericsson): comments.
Laurent (Nokia): answers and provides R04
Tingfang (Lenovo) comments on r04.
Fenqin (Huawei): Comments
Zhuoyun (Tencent) comments.
Tingfang (Lenovo) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) say r05 has been provided by Tingfang (Lenovo), and suggest to go with r05
Tingfang (Lenovo) Thanks Jinguo for correcting, yes it should be r05 not r04.
Laurent (Nokia): objects to R00 and R03; Happy to agree R05 (latest version) or to other non objected versions
Hui (Huawei) object to R00-R05, but the objection can be removed by making the procedure optional.
Marisa (ericsson) asks to postpone.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2103856 P-CR Approval 23.548: Flow consistency in 23.548 clause 6.2.3.2.2 Ericsson Rel-17 Postponed Jicheol (Samsung) provides r01 (with objection to r00 i.e. a new EASDF's service operation such as DNSsend).
Magnus H (Ericsson) comments.
Laurent (Nokia): objects to r00, R01
Tingfang (Lenovo) comments and propose to note this paper
Magnus H (Ericsson) answers
Fenqin (Huawei) comments
Tingfang (Lenovo) replies to Magnus
Magnus H (Ericsson) comments regarding CRUD
Magnus H (Ericsson) answers Lenovo
Laurent (Nokia): provides r02
Zhuoyun (Tencent) comments.
Magnus H (Ericsson) provides r03
Hui (Huawei) objects r03 and propose to postpone this paper.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): repeats objection to R00 and R01. Supports postponing this paper.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2103857 P-CR Approval 23.548: Use of UE address in UL by EASDF Ericsson Rel-17 Noted Dan (China Mobile) ask question about this paper
Hui (Huawei) doubts whether the change is needed.
Magnus H (Ericsson) answers
Magnus H (Ericsson) answers question
Dan(China Mobile) suggest this paper has been merged into S2-2104044 r01
Laurent (Nokia) 1) doubts whether the change is needed and 2) thinks it makes the networking more complex
Hui (Huawei) is still not convinced on this idea.
Tingfang (Lenovo) comments and doubts on the idea too.
Magnus H (Ericsson) answers.
Zhuoyun (Tencent) comments.
Magnus H (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) propose to merge to 4044
Laurent (Nokia): objects to any version of this Tdoc and suggests to discuss as part of 4044 only
Magnus H (Ericsson) 4044 does not capture the essence of this pCR. I suggest people objecting to reconsider.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2103858 P-CR Approval 23.548: All DNS handling in EASDF provided by SMF Ericsson Rel-17 Noted Jicheol (Samsung) proposes to note this pCR.
Magnus H (Ericsson) answers
Zhuoyun (Tencent) comments.
Magnus H (Ericsson) answers.
Magnus H (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
Jicheol (Samsung) objects r00 and r01.
Magnus H (Ericsson) comments
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104044 P-CR Approval 23.548: DNS message transfer between EASDF and DNS server (located in DN) through PSA UPF. China Mobile Rel-17 CC#4: r09 agreed. Revised to S2-2105144. Dan (China Mobile) provide r01 with merge S2-2103857
Dario S. Tonesi (Qualcomm) asks question on DoS attack and comments on figure.
Dan (China Mobile) response to Dario's question
Hui (Huawei) provides r01
Dan (China Mobile) provides r02
Hui (Huawei) provides r03
Magnus H (Ericsson) provides r04
Dan (China Mobile) ask question for r03 and r04
Hui (Huawei) provides r05
Laurent (Nokia): Comments and potential concerns
Tingfang (Lenovo) provides r06.
Hui (Huawei) replies to Laurent.
Dan(China Mobile) provide r07 to reflect Laurent's comment.
Magnus H (Ericsson) comments
Laurent (Nokia): answers and provides r08
Dan(China Mobile) provide comments and reply.
Hui (Huawei) responses.
Hui(Huawei) comments.
Dan(China Mobile) provide r09
Laurent (Nokia): provides r10
Dan(China Mobile): provide r11
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) asks question on r11.
Laurent (Nokia): objects to any version before and including R07. This topic deserves more work but Ok to go to R11;
Tingfang (Lenovo) asks to go with r09 and objects r10 and r11 as the clarification on multiple UPFs is unclear and further work is needed.
Hui (Huawei): Ok to go to R11;
Tingfang (Lenovo) responses and still asks to go with r09 and objects r10 and r11.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105144 P-CR Approval 23.548: DNS message transfer between EASDF and DNS server (located in DN) through PSA UPF. China Mobile Rel-17 Revision of S2-2104044r09. Approved Approved
8.3 S2-2104384 P-CR Approval 23.548: Clarification on EAS discovery via EASDF. Huawei, HiSilicon Rel-17 CC#4: r09 + changes agreed. Revised to S2-2105145, merging S2-2104470. Fenqin (Huawei) provides r01
Riccardo (NTT DOCOMO) asks a clarification on r01
Fenqin (Huawei) responds
Jicheol (Samsung) provides r03 with comments.
(Please ignore r02 that is superceded by r03)
Magnus H (Ericsson) ask comments
Magnus H (Ericsson) disagrees and objects to the use of DNAI in EASDF
Fenqin (Huawei) comments
Magnus H (Ericsson) comments
Laurent (Nokia): provides r04
Tingfang (Lenovo) provides r04.
Fenqin (Huawei) responds and provides r06
Magnus H (Ericsson) comments and objects to the use of DNAIs in DNS handling rules.
Fenqin (Huawei) responds and provides r07
Tingfang (Lenovo) comments.
Fenqin (Huawei) responds.
Magnus H (Ericsson) comments.
Tingfang (Lenovo) replies to Fenqin and provides r08.
Fenqin (Huawei) responds and provides r09
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) is OK with r08 or r09.
Magnus H objects to this pCR.
Fenqin(Huawei) ask question for clarification
Laurent (Nokia): objects to any version but could live with R09 + A Note '1bis' (to be put below the NOTE 1 in § 6.2.3.2.2): EASDF actions 'based on EAS deployment information pertaining to UE location' refer to EASDF using rules received as part of Neasdf_NodeLeveDNSHandlingRules (EASDF is meant to get the relevant information from SMF)' AND removal of the EN in step 10
Fenqin (Huawei) we can work offline and bring this to CC#4.
==== 8.X, 9.X Final Deadline ====
Fenqin (Huawei) provides r11.
Jicheol (Samsung) comments with a proposal.
-
Add the following sentense at the end of the sentense - 'Report DNS message content to SMF. '
The EASDF may report the DNS message once if the reporting condition is met.
Revised
8.3 S2-2105145 P-CR Approval 23.548: Clarification on EAS discovery via EASDF. Huawei, HiSilicon Rel-17 Revision of S2-2104384r09 + changes, merging S2-2104470. Approved Approved
8.3 S2-2104470 P-CR Approval 23.548: Stop reporting the DNS response to SMF. ZTE Rel-17 Merged into S2-2105145 Fenqin (Huawei) propose to merge into 4384
Jinguo(ZTE) is fine to merge into 4384
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104050 P-CR Approval 23.548: Denial of Service Attack Issues of EASDF Discovery. Tencent, China Mobile Rel-17 Revision of (Postponed) S2-2102721. r05 agreed. Revised to S2-2105038. Hui (Huawei) provides r01.
Chunshan (Tencent) provides r02.
Dario S. Tonesi (Qualcomm) comments that the issue needs to first be acknowledged by SA3 (as already commented in SA2#144E).
Dan (China Mobile) comments to Dario's comment
Hui (Huawei) comments.
Chunshan (Tencent) comments to Dario's comment
Chunshan (Tencent) provides r03.
Tingfang (Lenovo) clarifies and comments
Chunshan (Tencent) provides clarification to Tingfang (Lenovo).
Laurent (Nokia): provides r04
Chunshan (Tencent) asks for clarification.
Dario S. Tonesi (Qualcomm) provides r05
Hui (Huawei): provides r06, also fine with r05.
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) objects to r06 and suggest to go with r05
Laurent (Nokia): objects to any version between (and including) R00 and R03
Dario S. Tonesi (Qualcomm) objects to r06 and suggest to go with r05
Chunshan (Tencent) is fine with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105038 P-CR Approval 23.548: Denial of Service Attack Issues of EASDF Discovery. Tencent, China Mobile Rel-17 Revision of S2-2104050r05. Approved Approved
8.3 S2-2104051 P-CR Approval 23.548: DoS Attack and Access Control to EASDF Tencent, Nokia, Nokia Shanghai Bell Rel-17 CC#5: Replace note. Revised to S2-2105211. Dario S. Tonesi (Qualcomm) comments that the issue needs to first be acknowledged by SA3.
Laurent (Nokia): Comments
Chunshan (Tencent) provides clarification.
Hui (Huawei) comments.
Dario S. Tonesi (Qualcomm) objects any revision asks to bring the issue to SA3.
Chunshan (Tencent) responses that the CR proposes the similar texts been documented in TS 23.501.
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) suggest reformulation
Chunshan (Tencent) proposes the reformulation.
Chunshan (Tencent) proposes the reformulation and discuss in CC#4.
Chunshan (Tencent) updates the reformulation and discuss in CC#4.
Chunshan (Tencent) responses.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105211 P-CR Approval 23.548: DoS Attack and Access Control to EASDF Tencent, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104051. This Approved Approved
8.3 S2-2104483 P-CR Approval 23.548: Multiple ECS options in clause 6.2.3.2.2 (EAS discovery procedure with EASDF) . Nokia, Nokia Shanghai Bell Rel-17 Noted Hui (Huawei) objects to this paper and suggest to discuss this EN in S2-2103853.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104493 P-CR Approval 23.548: Reducing interaction frequency for serve discovery-23.548. Lenovo, Motorola Mobility Rel-17 CC#4: r05 + changes agreed. Revised to S2-2105146, merging S2-2104531. Fenqin (Huawei) remove step 10 and provides r01.
Magnus H (Ericsson) ask question.
Jicheol (Samsung) proposed to discuss three alternatives to solve this issue.
Laurent (Nokia): asks a question,
Laurent (Nokia): comments (valid also for 4351),
Marisa (Ericsson): comments (related also to 4351, and 4491 & 4492, and 4733 & 4734)
Hui (Huawei) comments.
Tingfang (Lenovo) replies.
Jicheol (Samsung) comments and questions.
Tingfang (Lenovo) replies to Jicheol and Laurent.
Tingfang (Lenovo) replies to Jicheol.
Xinpeng (Huawei) provides comments.
Magnus H (Ericsson) comments.
Marisa (Ericsson) comments
Laurent (Nokia): answers
Jicheol (Samsung) replies to Marisa (Ericsson).
Tingfang (Lenovo) replies to Laurent.
Tingfang (Lenovo) suggests to move forward with node-level provisioning using the mechanism similar to that of PFDF
Tingfang (Lenovo) provides r02
Hui (Huawei) provides r03
Jicheol (Samsung) provides follow-up questions to Tingfang (Lenovo) on this solution.
Marisa (Ericsson) comments.
Tingfang (Lenovo) replies to Jicheol and provides r04
Tingfang (Lenovo) replies to Marisa and provides r05
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version; asks this Tdoc to be part of CC#4 as he could live with R05 provided that an EN is added in § 6.2.3.x.1 : it is FFS whether the interaction between SMF and UDR needs to go via NEF
Tingfang (Lenovo) is OK with r05+EN proposed by Laurent (EN is added in § 6.2.3.x.1 : it is FFS whether the interaction between SMF and UDR needs to go via NEF)
Jicheol (Samsung) proposes to postpone this pCR.
Hui (Huawei) prefer to agree the CR with ENs for progress.
Jicheol (Samsung) comments.
Hui (Huawei) responses.
Marisa (Ericsson) asks to postpone this pCR
Tingfang (Lenovo) replies and proposes to go with r05+EN proposed by Laurent as baseline for work next meeting
Tingfang (Lenovo) shares the same response of Hui to Jicheol's comments and proposes to go with r05+EN proposed by Laurent as baseline of the work next meeting.
Hui (Huawei) support to agree this as baseline with EN for next meeting.
* Marisa (ericsson) has asked to postpone; but asks this Tdoc to be part of CC#4 as Ericsson could live with R05 provided that ENs are added including Laurent's proposed EN plus: EN1 (clause: 6.2.3.2.2): The procedure for AF provisioning of the EAS Deployment information is FFS ; EN2 (clause 6y.2.3.x.1.): If both modes push and pull are needed is FFS
* Marisa (ericsson) has asked to postpone; but asks this Tdoc to be part of CC#4 a's Ericsson could live with R05 provided that ENs are added including Laurent's proposed EN plus: EN1 'The procedure for AF provisioning of the EAS Deployment information is FFS ; EN2: 'If both modes push and pull are needed is FFS'
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105146 P-CR Approval 23.548: Reducing interaction frequency for serve discovery-23.548. Lenovo, Motorola Mobility Rel-17 Revision of S2-2104493r05 + changes, merging S2-2104531. Approved Approved
8.3 S2-2104506 P-CR Approval 23.548: DNS context removal. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2105039. Huazhang (vivo) ask a question.
Hui (Huawei) replies and provides r01.
Magnus H (Ericsson) comments.
Hui (Huawei) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105039 P-CR Approval 23.548: DNS context removal. Huawei, HiSilicon Rel-17 Revision of S2-2104506r02. Approved Approved
8.3 S2-2104491 CR Approval 23.501 CR2932 (Rel-17, 'F'): DNS configuration to SMF Lenovo, Motorola Mobility, Huawei, Futurewei Rel-17 Postponed Tingfang (Lenovo) Discusses how to organize the EAS deployment information merging S2-2104733 into S2-2104491.
Marisa (ericsson) comments
John (Futurewei) asks Marisa a question.
==== 8.X, 9.X Revisions Deadline ====
Marisa (ericsson) answers.
Marisa (Ericsson) asks to postpone this CR
Tingfang (Lenovo) agrees to postpone the pCR and comes back next meeting considering node level and/or session-level provisioning
Laurent (Nokia): postponing is the best .
Hui (Huawei) fine to postpone.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2104492 CR Approval 23.503 CR0594 (Rel-17, 'F'): DNS configuration to SMF Lenovo, Motorola Mobility, Huawei, HiSilicon Rel-17 Postponed Marisa (Ericsson) requests to postpone
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version (does not seem aligned with 4493R05)
Tingfang (Lenovo) agrees to postpone the CR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2104531 P-CR Approval 23.548: Provisioning non-UE specific EAS domain configuration. Samsung Rel-17 Merged into S2-2105146 Hui (Huawei) asks why do we need an interface between UDR and EASDF.
Jicheol (Samsung) provides an answer.
Laurent (Nokia): please see my Comments to 4493
==== 8.X, 9.X Revisions Deadline ====
Hui(Huawei) proposes to note this paper or consider it as merged into S2-2104493.
Laurent (Nokia): proposes to note this paper (object to it) or consider it as merged into S2-2104493.
Marisa (ericsson): proposes to note this paper (object to it) or consider it as merged into S2-2104493.
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104733 CR Approval 23.501 CR2980 (Rel-17, 'B'): SMF configuration related with EASDF Nokia, Nokia Shanghai Bell Rel-17 Postponed Tingfang (Lenovo) agrees with Hui to discuss the SMF configuration related with EASDF in one thread of S2-2104491.
Laurent (Nokia): answers and provides r01
Tingfang (Lenovo) comments and suggests to merge 4473 into 4991 as suggested by Hui.
Tingfang (Lenovo) replies to Laurent.
Hui(Huawei) provides comments.
Tingfang (Lenovo) comments.
Marisa (Ericsson) comments.
Tingfang (Lenovo) replies to Marisa.
==== 8.X, 9.X Revisions Deadline ====
Marisa(ericsson) replies a.
Tingfang (Lenovo) asks Marisa for further clarification
Marisa (ericsson) replies
Tingfang (Lenovo) asks to note or postpone this CR for the same reason discussed in the 4491 thread.
Laurent (Nokia): agrees: postponing is the best considering 4491 is postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2104734 CR Approval 23.502 CR2871 (Rel-17, 'B'): SMF configuration related with EASDF Nokia, Nokia Shanghai Bell Rel-17 Postponed Dario S. Tonesi (Qualcomm) provides r01 (w/o impacts on ME)
Tingfang (Lenovo) comments.
Hui (Huawei) suggest to note or postpone this paper.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): withdraws / accepts-asks to postpone as we need to first clarify 23.5021 at this meeting
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2104363 P-CR Approval 23.548: Behaviour of NWDAF for optimization in eEDGE. vivo Rel-17 CC#4: Noted Huazhang (vivo) provides r01 and merge S2-2104614 to 4363.
Dimitris (Lenovo) comments
Dario S. Tonesi (Qualcomm) proposes NOT to merge 4614 into 4363 and asks to clarify the scenario for 4363.
Huazhang (vivo) comments to Dario, both of the decription and flow is needed.
Dario S. Tonesi (Qualcomm) asks question for clarification
Huazhang (vivo) replys to Dimitrios
Huazhang (vivo) response to Dario
Dario S. Tonesi (Qualcomm) asks questions for clarificaiton
Dimitris (Lenovo) responds to Huazhang (Vivo)
Huazhang (vivo) replys to Dimitrios and provides r02
Jicheol (Samsung) ask a question whether it is within the scope of this WID and suggest to postpone to Rel-18.
Huazhang (vivo) reply to Jicheol
Jicheol (Samsung) replies to Huazhan (Vivo).
Huazhang (vivo) replies to Jicheol (Samsung).
Dario S. Tonesi (Qualcomm) replies to Huazhang and asks to clarify what is missing in 288 to support provision of Observed Service Experience Info of EAS.
Huazhang (vivo) replies to Dario and explain that this can be edge specific in experience
Jicheol (Samsung) asks a question.
Jicheol (Samsung) provides r03.
Huazhang (vivo) replys to Jicheol and agree to r03
Jicheol withdraw r03, instead provides r04.
Huazhang(vivo)ask Jicheol that the link of r04 is wrong, it is r03
Dario S. Tonesi (Qualcomm) comments that this pCR does not seem to be edge specific and should not be captured in 548.
Jicheol (Samsung) provides the correct reference for r04.
Jicheol (Samsung) comments and okay to postpone or note this pCR.
Huazhang (vivo) replys to Dario and provides r05 based on r04
Shubhranshu (Nokia) supports to note this paper
Huazhang (vivo) replys to Shubhranshu,Dario and Jicheol, and provides general description in r06
Magnus H (Ericsson) comments
Magnus H (Ericsson) provides r07
==== 8.X, 9.X Revisions Deadline ====
Dimitris (Lenovo) ok with r07 with a small modification
Huazhang (vivo) ok with r07 + Dimitrios's changes
Huazhang (vivo) provides r08 based on r07 and Dimitris's changes, prefer to go with r08
Shubhranshu (Nokia) comments and still prefers to note this paper
Huazhang (vivo) replys to Shubhranshu that all these contents is in KI#16 of eNA that eNA enhancement of edge computing
Shubhranshu (Nokia) responds
Huazhang (vivo) responds
Shubhranshu (Nokia) responds and based on all the discussions so far suggest to note this paper
Huazhang (vivo) replys to Shubhranshu (Nokia) that I want to declear these content in eNA is focus on eEDGE, not for general circumstance, and the content has already written in TS 23.288
Dimitris (Lenovo) asks Nokia if they are willing to go with S2-2104614 where a specific use case is described that the SMF can be a consumer of analytics
Dario S. Tonesi (Qualcomm) if OK with Dimitris' proposal
Huazhang (vivo) responds to Shubhranshu and how about move the text to clause 6, provide r09
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104614 P-CR Approval 23.548: SMF selecting an EAS application server by taking into account NWDAF analytics. Lenovo, Motorola Mobility Rel-17 r03 agreed. Revised to S2-2105040. Dimitris (Lenovo) requests to handle S2-2104614 separately.
Dario S. Tonesi (Qualcomm) supports handling 4614 separately.
Jicheol (Samsung) objects the concept of SMF selecting EAS server among multiple EAS servers.
Huazhang (vivo) comments
Dimitris (Lenovo) requests clarification to the objection from Jicheol (Samsung)
Dimitris (Lenovo) provides r01 includes aspects of 4363.
Magnus H (Ericsson) objects to the concept of SMF selecting EAS
Dimitris (Lenovo) provides r02 with an alternative proposal on how the SMF can be a consumer for NWDAF analytics
Hui (Huawei) suggest to postpone whether/how NWDAF can support EAS selection to Rel-18.
Dimitris (Lenovo) clarifies to Hui (Huawei) that revisions do not propose EAS selection
Hui (Huawei) responses to Dimitris (Lenovo)
Dimitris (Lenovo) provides r03
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) is ok with r03 if 4363r07 is not agreed.
Shubhranshu (Nokia) responds
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105040 P-CR Approval 23.548: SMF selecting an EAS application server by taking into account NWDAF analytics. Lenovo, Motorola Mobility Rel-17 Revision of S2-2104614r03. Approved Approved
8.3 S2-2104000 P-CR Approval 23.548: EPS Interworking Considerations / traffic offload. Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Lenovo, Motorola Mobility Rel-17 r01 agreed. Revised to S2-2105041. Dario S. Tonesi (Qualcomm) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105041 P-CR Approval 23.548: EPS Interworking Considerations / traffic offload. Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, Lenovo, Motorola Mobility Rel-17 Revision of S2-2104000r01. Approved Approved
8.3 S2-2103855 P-CR Approval 23.548: L-DNS Selection for Session Breakout Option C Ericsson Rel-17 Merged into S2-2105042 Marisa (Ericsson) agrees to merge this paper into S2-2104385.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104385 P-CR Approval 23.548: Local DNS Server Configuration to UE. Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2105042, merging S2-2103855 John (Futurewei) comments, provides R01.
Marisa (Ericsson) comments and provides r02.
John (Futurewei) is fine with r02.
Laurent (Nokia): provides r03
Fenqin (Huawei): provides comments
Laurent (Nokia): answers
Fenqin (Huawei): answers
John (Futurewei) comments.
Fenqin (Huawei): provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105042 P-CR Approval 23.548: Local DNS Server Configuration to UE. Huawei, HiSilicon Rel-17 Revision of S2-2104385r04, merging S2-2103855. Approved Approved
8.3 S2-2104365 P-CR Approval 23.548: DNS behaviour in changing of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session. vivo Rel-17 Merged into S2-2105043 Hui (Huawei) confirms this paper was merged into S2-2104386.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104386 P-CR Approval 23.548: Upates to EAS Re-discovery Procedure at Edge Relocation. Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2105043, merging S2-2104365 and S2-2104145 Xinpeng (Huawei) provides r01.
Xinpeng (Huawei) resubmit for r01.
Huazhang (vivo) provides comments
Xinpeng (Huawei) replies.
Marisa (Ericsson) provides comments
Huazhang (vivo) replies to Xinpeng
Xinpeng (Huawei) replies to Huazhang and Marisa.
Tingfang (Lenovo) comments that
Marisa (Ericsson) provides r02
Xinpeng (Huawei) provides r03.
Xinpeng (Huawei) provides r04 correcting company name.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105043 P-CR Approval 23.548: Upates to EAS Re-discovery Procedure at Edge Relocation. Huawei, HiSilicon Rel-17 Revision of S2-2104386r04, merging S2-2104365, merging S2-2104365 and S2-2104145. Approved Approved
8.3 S2-2104488 P-CR Approval 23.548: EAS Rediscovery at Edge Relocation triggered by AF-23.548. Lenovo, Motorola Mobility Rel-17 Approved Marisa (ericsson) comments
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) responds
Tingfang (Lenovo) responds and proposes to agree this pCR
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2104517 CR Approval 23.501 CR2935 (Rel-17, 'F'): AF Influence enhancement for EAS Rediscovery at Edge Relocation Lenovo, Motorola Mobility Rel-17 r01 agreed. Revised to S2-2105044. Yuan (CATT) suggests to merge this paper into S2-2104288.
Tingfang (Lenovo) replies that the two papers touches different points and they is no need to merge them.
Fenqin (Huawei) comments
Laurent (Nokia): asks a question
Fenqin (Huawei) correct the meeting number.
Tingfang (Lenovo) replies to Laurent
Tingfang (Lenovo) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) proposes to agree this pCR
Changhong (Intel) proposes to approve r01.
Shubhranshu (Nokia) responds
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105044 CR Approval 23.501 CR2935R1 (Rel-17, 'F'): AF Influence enhancement for EAS Rediscovery at Edge Relocation Lenovo, Motorola Mobility Rel-17 Revision of S2-2104517r01. Approved Agreed
8.3 S2-2104518 CR Approval 23.502 CR2832 (Rel-17, 'F'): AF Influence enhancement for EAS Rediscovery at Edge Relocation Lenovo, Motorola Mobility Rel-17 Postponed Tingfang (Lenovo) replies
Laurent (Nokia): Comments
Tingfang (Lenovo) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) replies to Marisa.
Fenqin (Huawei) propose to postpone this paper.
Marisa (ericsson): objects to this paper
Tingfang (Lenovo) agree to postpone this CR
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 S2-2103860 P-CR Approval 23.548: ENs in Procedure for EAS Discovery with Dynamic PSA Distribution . Ericsson, vivo Rel-17 Merged into S2-2105045 Hui (Huawei) objects to this paper since it should be considered as merged into S2-2103866.
Laurent (Nokia):objects to this paper since it should be considered as merged into S2-2103866.
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2103866 P-CR Approval 23.548: Procedure for EAS Discovery with Dynamic PSA Distribution in SSC mode 3. Ericsson, vivo, Nokia, Nokia Shanghai Bell Rel-17 r09 agreed. Revised to S2-2105045, merging S2-2103860 Marisa (Ericsson) provides revision r02, asks to ignore r01.
Hui (Huawei) provides r03, and asks for question.
Dario S. Tonesi (Qualcomm) asks question for clarification on the wording 'further out'
Marisa (Ericsson) provides revision r04 and comments
Hui(Huawei) provides revision r05
Laurent (Nokia): provides r06
Marisa (ericsson): provides r07 and replies
Hui (Huawei): provides comments.
Marisa (ericsson) replies
Hui (Huawei) provides r09
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105045 P-CR Approval 23.548: Procedure for EAS Discovery with Dynamic PSA Distribution in SSC mode 3. Ericsson, vivo, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103866r09, merging S2-2103860. Approved Approved
8.3 S2-2104145 P-CR Approval 23.548: Update the EAS discovery over Distributed Anchor connectivity model. Tencent Rel-17 Merged into S2-2105043 Xinpeng (Huawei) suggest to merge this paper into S2-2104386.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104147 P-CR Approval 23.548: EASDF services update. Tencent Rel-17 r01 agreed. Revised to S2-2105046. Marisa (Ericsson) comments and provides revision r01
Zhuoyun Zhang (Tencent) provides r02.
Hui (Huawei) prefer to r01.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): prefers also r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105046 P-CR Approval 23.548: EASDF services update. Tencent Rel-17 Revision of S2-2104147r01. CC#4: Confirmed Approved Approved
8.3 S2-2104387 CR Approval 23.502 CR2814 (Rel-17, 'B'): UE capability to support EAS rediscovry Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2105047. Jicheol (Samsung) provides a revision (r01).
Dario S. Tonesi (Qualcomm) asks questions for clarification.
Fenqin (Huawei) Responds
Marisa (Ericsson) provides revision r02
Jicheol (Samsung) is fine with r02.
Fenqin (Huawei) Responds and provides r03
Marisa (Ericsson) comments
Dario S. Tonesi (Qualcomm) provides r04
Laurent (Nokia): Comments: r02.zip contains a r01.doc. This is confusing
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105047 CR Approval 23.502 CR2814R1 (Rel-17, 'B'): UE capability to support EAS rediscovry Huawei, HiSilicon Rel-17 Revision of S2-2104387r04. Approved Agreed
8.3 S2-2104471 CR Approval 23.502 CR2824 (Rel-17, 'B'): Target DNAI selection by AF ZTE Rel-17 Noted Marisa (Ericsson) objects to this proposal
Jinguo(ZTE) asks Marisa (Ericsson) to exlain the run time coordination between SMF and applications.
Jinguo(ZTE) provides r01
Shubhranshu (Nokia) asks for clarification
Marisa (Ericsson) answers and commentd
Jinguo(ZTE) response to Shubhranshu (Nokia)
Shubhranshu (Nokia) responds
Jinguo(ZTE) provides r02 to update the cover sheet
==== 8.X, 9.X Revisions Deadline ====
Marisa (ericsson): objects to any revision of this paper.
Jinguo(ZTE) reply to Marisa. The objection is no base.
==== 8.X, 9.X Final Deadline ====
Marisa (ericsson) replies.
Noted
8.3 S2-2104507 P-CR Approval 23.548: Clarification on UE indicating support for refreshing cached EAS information. Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2105048. Jicheol (Samsung) provides a revision (r01).
Ulises Olvera (InterDigital Inc.) provides r02 with additional editorial updates.
Jicheol (Samsung) is okay with r02.
Hui (Huawei) provides r03.
Hui (Huawei) provides r04.
Dario S. Tonesi (Qualcomm) provides r05
==== 8.X, 9.X Revisions Deadline ====
Hui(Huawei) fine with r05
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105048 P-CR Approval 23.548: Clarification on UE indicating support for refreshing cached EAS information. Huawei, HiSilicon Rel-17 Revision of S2-2104507r05. Approved Approved
8.3 S2-2104666 P-CR Approval 23.548: EAS rediscovery: corrections related to DNS cache handling. Qualcomm Incorporated, Futurewei Rel-17 Noted Magnus (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) cannot accept (i.e., he objects) r01 and proposes to go with r00.
Magnus (Ericsson) objects to r00.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - UE don't use MNO DNS - - Docs:=8 -
8.3 S2-2104504 DISCUSSION Discussion Way forwards on 'UE don't use MNO DNS configuration'. Huawei (Rapporteur) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104505 P-CR Approval 23.548: Remove EN on UE using MNO DNS configuration. Huawei Rel-17 Noted Jicheol (Samsung) provides a revision (r01).
Dan (China Mobile) provides a revision r02.
Dario S. Tonesi (Qualcomm) explains that r00, r01 and r02 describe behaviors that are not testable and hence he cannot accept them.
Jicheol (Samsung) objects r00 and r02. Only accept r01. But can live with noting this paper.
Hui (Huawei) provides r03.
Dan(China Mobile) comments
Changhong (Intel) provides r04 and strongly objects to r00 to r03.
Hui (Huawei) provides r05.
Hui (Huawei) replies to Dario.
Riccardo (NTT DOCOMO) asks clarifications on r04 and r05.
Changhong (Intel) replies to Riccardo.
Sudeep (Apple) comments.
Xiaobo Yu (Alibaba) provides r06, and can accept r05 and r06.
Hui (Huawei) comments.
Xiaobo Yu (Alibaba) replies to Hui.
Dario S. Tonesi (Qualcomm) replies to Ni Hui and explains why he cannot accept any revision up to r06
==== 8.X, 9.X Revisions Deadline ====
Riccardo (NTT DOCOMO) suggests to focus on the acceptability of r03
Hui (Huawei) supports Riccardo and ask for feedbacks.
Xiaobo Yu (Alibaba) supports r03, with some suggestion from thread 4482.
Tingfang (Lenovo) can live with moving forward with existing r03, but it is better to replace note 2 with the note suggested in thread 4482 to cover the concern for detecting.
Dario S. Tonesi (Qualcomm) objects to any revision of this paper.
Tingfang (Lenovo) comments.
Zhuoyun (Tencent) agrees with r03.
John (Futurewei) supports moving forward with r03.
Susana (Vodafone) objects to any revision of this tdoc.
Gerry (Verizon) objects to any revision of this TDoc
Huazhang (vivo) supports moving forward with r04 - r06, but r03 is also reasonable to me
Laurent (Nokia): objects to any version of this paper
==== 8.X, 9.X Final Deadline ====
Hui(Huawei) asks for a SoH on CC#4.
Xiaobo Yu(Alibaba) provides r01 for SoH slides.
Noted
8.3 S2-2104675 P-CR Approval 23.548: EAS rediscovery: DNS setting enforcement and notification of change of DNS settings. Qualcomm Incorporated, Verizon, Vodafone, AT&T Rel-17 Noted Zhuoyun Zhang (Tencent) proposes to note this contribution.
Jicheol (Samsung) agrees to note this contribution.
Xiaobo Yu (Alibaba) objects to this contribution.
Dario S. Tonesi (Qualcomm) provides r01
Riccardo (NTT DOCOMO) comments on r01
Huazhang (vivo) objects r01 and r00 and any versions
Hui (Huawei) ask questions.
Zhuoyun (Tencent) objects r00 and r01.
Susana (Vodafone) comments and provides r02
==== 8.X, 9.X Revisions Deadline ====
Xiaobo Yu (Alibaba) objects to r01 and r02.
Tingfang (Lenovo) objects all the revisions on board. The indication can be accepted but it is already covered in 4505, the 5GC detecting of not using MNO DNS is covered in 4482 in 5GC.
Jicheol (Samsung) proposes to postpone (or note) all pCRs in this subtopic.
Zhuoyun Zhang (Tencent) objects to any revision of this paper .
Laurent (Nokia): strongly suggests to postpone the topic and to organize a dedicated CC in June
Huazhang (vivo) agree with Zhuoyun and Xiaobo, objects to any revision of this paper, go for 4505 is ok
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104128 P-CR Approval 23.548: Resolve the editor's note about the DNS configuration. Tencent, ZTE, Vivo, Spreadtrum, OPPO, Lenovo, Motorola Mobility, Alibaba Rel-17 Noted Dario S. Tonesi (Qualcomm) cannot accept r0.
Zhuoyun Zhang (Tencent) replies.
Hui (Huawei) suggest merge this paper into S2-2104505.
Dario S. Tonesi (Qualcomm) objects to move the discussion to 4505
Susana (Vodafone) provides r01, objects to original version and to moving this discussion to 4505
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104361 P-CR Approval 23.548: Issues on UE don't use DNS configuration from 5GC. vivo, Sony, OPPO, ZTE, Tencent, Alibaba, Spreadtrum Rel-17 Noted Dario S. Tonesi (Qualcomm) objects to this proposal
Jicheol (Samsung) agrees with the intention of the paper, but NOTEs are not necessary.
Huazhang (vivo) response to Jicheol
Zhuoyun Zhang (Tencent) comments.
Hui (Huawei) suggest merge this paper into S2-2104505.
Dario S. Tonesi (Qualcomm) objects this paper to move the discussion to 4505
Susana (Vodafone) objects to this document and any moving of this discussion to 4505
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2103859 P-CR Approval 23.548: DNS Settings handling by application under SLA. Ericsson Rel-17 Noted Susana (Vodafone) proposes rev01
Dario S. Tonesi (Qualcomm) comments
Hui (Huawei) suggest merge this paper into S2-2104505.
Dario S. Tonesi (Qualcomm) objects to move the discussion to 4505.
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) clarifies: he objects to this paper.
Zhuoyun (Tencent) agrees with Hui to merge this paper to 4505.
Huazhang (vivo) suggest merge this paper to 4505
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104364 P-CR Approval 23.548: Principle of EAS Discovery in edge APP and non-edge APP. vivo Rel-17 Noted Changhong (Intel) proposes to note it.
Huazhang (vivo) replies
Changhong (Intel) replies to Huazhang.
Huazhang (vivo) replies to Changhong.
Hui (Huawei) asks question.
Huazhang (vivo) response to merge this paper to 4505
Changhong (Intel) objects to this paper, let's mark it as NOTED not merged.
Huazhang (vivo) replys to Changhong
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104482 P-CR Approval 23.548: Network action related with the UE not using the EASDF's IP address for its DNS Query. Nokia, Nokia Shanghai Bell Rel-17 Noted Zhuoyun Zhang (Tencent) proposes to note this contribution.
Laurent (Nokia): provides r01
Dan(China Mobile) provide our consideration
Laurent (Nokia): answers
Tingfang (Lenovo) supports Dan's proposal to have the UPF detection part only for statistics or monitoring, but not include the change of the path of the DNS message and involve further action on EASDF.
Zhuoyun Zhang (Tencent) comments.
Laurent (Nokia): provides r02
Huazhang (vivo): provides comments
Laurent (Nokia): provides r03
Magnus H (Ericsson) comments
Tingfang (Lenovo) comments that the change of the path of the DNS message and involve further action on EASDF is not convincible.
Zhuoyun (Tencent) comments.
Hui (Huawei) suggest to go with S2-2104505.
Dario S. Tonesi (Qualcomm) provides r04
Dan (China Mobile) provides r05 and suggest whether we can go with this r05
Dario S. Tonesi (Qualcomm) provides r06
Magnus H (Ericsson) comments.
laurent (Nokia) comments.
Hui(Huawei) comments.
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) can only live with r05, or accept to note this paper but add the related note in 4505.
Xiaobo Yu (Alibaba) objects to all versions of this contribution, and suggest to merge this paper into 4505.
Dan (China Mobile) suggest we go with r05
Laurent (Nokia): can live with R05
Dario S. Tonesi (Qualcomm) can only accept r06 (he objects to other revisions)
Xiaobo Yu (Alibaba) replies to Laurent regarding r05
Zhuoyun Zhang (Tencent) objects to all versions of this contribution and prefer the way forward in 4505.
Magnus H (Ericsson) objects to all versions of this contribution and prefer the way forward in 4505.
Susana (Vodafone) supports r06 and can accept r05 as long as it moves forward together with tdoc 4675r02
Huazhang (vivo) objects to all versions of this contribution and prefer the way forward in 4505.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - EAS relocation - - Docs:=4 -
8.3 S2-2103825 P-CR Approval 23.548: Correction on the procedure for EAS Relocation on Simultaneous Connectivity over Source and Target PSA. China Unicom Rel-17 r01 agreed. Revised to S2-2105049. Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105049 P-CR Approval 23.548: Correction on the procedure for EAS Relocation on Simultaneous Connectivity over Source and Target PSA. China Unicom Rel-17 Revision of S2-2103825r01. Approved Approved
8.3 S2-2104424 P-CR Approval 23.548: EAS Relocation on Simultaneous Connectivity over Source and Target PSA . NTT DOCOMO Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2104453 CR Approval 23.502 CR2720R1 (Rel-17, 'B'): KI#2 AF triggered EAS relocation ZTE, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Noted) S2-2102904. CC#4: Postponed Marisa (Ericsson) ask question and provides revision r01
Jinguo(ZTE) is fine with r01
Tingfang (Lenovo) provides comments
Xinpeng (Huawei) ask questions for clarification.
Marisa (Ericsson) comments
Shubhranshu (Nokia) responds
Tingfang (Lenovo) comments
Jinguo (ZTE) responds
Fenqin (Huawei) comments
Fenqin (Huawei) responds
Jinguo(ZTE) provides r02
Shubhranshu (Nokia) comments and provides r03
Tingfang (Lenovo) provides r04
Marisa (ericsson) ask questios
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) replies to Marisa (ericsson)
Marisa (ericsson) objects
==== 8.X, 9.X Final Deadline ====
Postponed
8.3 - - - Split UE - - Docs:=8 -
8.3 S2-2104048 P-CR Approval 23.548: EASDF Discovery via DHCP. Tencent, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2102718. r04 agreed. Revised to S2-2105050. Marisa (Ericsson) provides r01
John (Futurewei) provides r02.
Chunshan (Tencent) responses.
Jicheol (Samsung) provides r03
Chunshan (Tencent) provides clarification and there are a lot of problems in r04.
Jicheol (Samsung) comments.
Chunshan (Tencent) provides clarification.
Dario S. Tonesi (Qualcomm) asks why this pCR is needed since we already have annex C.5
Chunshan (Tencent) responses that Annex C is informative.
Hui(Huawei) responses.
Dario S. Tonesi (Qualcomm) provides r04 and asks to ignore r05.
==== 8.X, 9.X Revisions Deadline ====
John (Futurewei) is fine with either r04 or r05.
Chunshan (Tencent) is fine with r04 or r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105050 P-CR Approval 23.548: EASDF Discovery via DHCP. Tencent, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104048r04. Approved Approved
8.3 S2-2104049 P-CR Approval 23.548: EAS Re-discovery Procedure at Edge Relocation. Tencent Rel-17 Revision of (Postponed) S2-2102719. r03 agreed. Revised to S2-2105051. John (Futurewei) comments, provides R01.
Chunshan (Tencent) provides clarification.
Marisa (Ericsson) provides r02.
Laurent (Nokia): provides r03
Dario S. Tonesi (Qualcomm): unclear why we need to do anything.
Chunshan (Tencent) responses that Annex C is informative.
==== 8.X, 9.X Revisions Deadline ====
John (Futurewei) is fine with r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105051 P-CR Approval 23.548: EAS Re-discovery Procedure at Edge Relocation. Tencent Rel-17 Revision of S2-2104049r03. Approved Approved
8.3 S2-2104052 P-CR Approval 23.548: Local DNS Server Discovery via DHCP. Tencent Rel-17 r01 agreed. Revised to S2-2105052. John (Futurewei) requests clarification
Chunshan (Tencent) provides clarification.
John (Futurewei) replies.
Chunshan (Tencent) replies.
Marisa (ericsson) asks a question
John (Futurewei) provides r02.
Chunshan (Tencent) clarifies that the r02 is for another paper and is not for this paper.
Dario S. Tonesi (Qualcomm) does see the need for this pCR.
Chunshan (Tencent) responses that Annex C is informative.
Dario S. Tonesi (Qualcomm) corrects a mistake in his previous statement: he does NOT see the need for this pCR
Fenqin (Huawei) provides comments and provides r01
==== 8.X, 9.X Revisions Deadline ====
John (Futurewei) can only accept r01.
Chunshan (Tencent) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105052 P-CR Approval 23.548: Local DNS Server Discovery via DHCP. Tencent Rel-17 Revision of S2-2104052r01. Approved Approved
8.3 S2-2104053 P-CR Approval 23.548: UE Consideration for EAS (re)Discovery. Tencent Rel-17 r03 agreed. Revised to S2-2105053. John (Futurewei) comments, provides R01.
John (Futurewei) provides R02.
John (Futurewei) provides updates in r03.
Chunshan (Tencent) responses.
==== 8.X, 9.X Revisions Deadline ====
John (Futurewei) suggests to accept r03.
Chunshan (Tencent) also supports r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105053 P-CR Approval 23.548: UE Consideration for EAS (re)Discovery. Tencent Rel-17 Revision of S2-2104053r03. Approved Approved
8.3 - - - AF Guidance to URSP - - Docs:=6 -
8.3 S2-2103851 CR Approval 23.502 CR2609R1 (Rel-17, 'B'): Support for Service Specific Authorization Ericsson, AT&T Rel-17 Revision of (Postponed) S2-2102193. r01 agreed. Revised to S2-2105054. Hui (Huawei) asks questions.
Magnus (Ericsson) replies.
Hui (Huawei) requests a revision reflecting the discussion result otherwise object to the paper.
Laurent (Nokia): Comments and suggests to postpone the aspect related with multiple UE's.
Hui (Huawei): support to postpone the paper.
Magnus (Huawei): provides r01.
Farooq (AT&T) agrees with E/// on this way forward and not to delay it further as it was already postponed once in the last meeting.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105054 CR Approval 23.502 CR2609R2 (Rel-17, 'B'): Support for Service Specific Authorization Ericsson, AT&T Rel-17 Revision of S2-2103851r01. Approved Agreed
8.3 S2-2103854 CR Approval 23.502 CR2740 (Rel-17, 'B'): Spatial Validity Conditions in AF Guidance to URSP Rules Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2103862 CR Approval 23.502 CR2741 (Rel-17, 'B'): Notification on the outcome of UE Policies delivery due to service specific parameter provisioning Ericsson Rel-17 Approved Jicheol (Samsung) ask clarification questions.
Magnus (Ericsson) provide answers.
Jicheol (Samsung) thanks Magnus (Ericsson) for kind and clear answers.
Magnus (Ericsson) provides further answers.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2103863 CR Approval 23.503 CR0575 (Rel-17, 'B'): Notification on the outcome of UE Policies delivery due to service specific parameter provisioning Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2104494 P-CR Approval 23.548: Update AF Guidance to PCF Determination of URSP Rules -23.548. Lenovo, Motorola Mobility Rel-17 CC#4: Approved Shubhranshu (Nokia) comments and provides r01
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) replies to Shubhranshu, and disagrees with r01 and proposes to go with r00
==== 8.X, 9.X Final Deadline ====
Approved
8.3 - - - ECS address provisioning - - Docs:=21 -
8.3 S2-2103861 P-CR Approval 23.548: ECS Address provision clarification. Ericsson, Huawei Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2103998 CR Approval 23.502 CR2716R1 (Rel-17, 'C'): ECS Address Configuration in UDM Nokia, Nokia Shanghai Bell Rel-17 Revision of (Postponed) S2-2102869. CC#5: r07 + changes agreed. Revised to S2-2105208. Huazhang (vivo) provides R01
Laurent (Nokia): answers
Hyesung (Samsung) provides R02
Dario S. Tonesi (Qualcomm) asks question on implication of using validity conditions.
Magnus O (Ericsson) provides r03.
Ulises Olvera (InterDigital): provides r03, to address Rapporteur's suggestion.
Ulises Olvera (InterDigital): provides r04, to address Rapporteur's suggestion, and to correct previous email with wrong revision.
Laurent (Nokia): answers and provides r05
Hyesung (Samsung) provides r06 with a minor editorial change and co-signed.
Dario S. Tonesi (Qualcomm) provides r07 and repeats his question.
Ulises Olvera (InterDigital Inc.) replies to Dario and provides r08.
==== 8.X, 9.X Revisions Deadline ====
Huazhang (vivo) wants to go with r07
Magnus (Ericsson) propose to go with r06 or r07. Object to r00-r02, r04 and r08.
Ulises Olvera (InterDigital Inc.) replies to Vivo (Huazhang)
Dario S. Tonesi (Qualcomm) can accept only r00, r01 and r08.
Dario S. Tonesi (Qualcomm) is fine also with r07
Laurent (Nokia): objects to R04 and R08; proposes to go with R06 + EN 'it is FFS whether DNN and S-NSSAI are part of AF provided ECS Address Configuration Information3 + Removing the two bullets 3) in the cover sheet
Dario S. Tonesi (Qualcomm) replies to Laurent and proposes to go w/ r07 + EN 'it is FFS whether DNN and S-NSSAI are part of AF provided ECS Address Configuration Information + Removing the two bullets 3) in the cover sheet.
Ulises Olvera (InterDigital Inc.) objects to the rational used to agree to some revisions and not others and can only accept r08
==== 8.X, 9.X Final Deadline ====
Laurent (Nokia): answers he is OK to go with r07 + EN 'it is FFS whether DNN and S-NSSAI are part of AF provided ECS Address Configuration Information + Removing the two bullets 3) in the cover sheet.
Hui (Huawei) asks to discuss this on CC#4.
Laurent (Nokia): let's try to make progress on this, having at least some agreed baseline text.
Ulises Olvera (InterDigital Inc.) InterDigital has an objection that is being completely ignored. It is not clear how the new information derived by the NEF included in the table, is used by the 5GC. In addition, sending all possible ECS Provider IDs is not acceptable to us.
Laurent (Nokia): OK with / supports the EN that Ulises wants to add
proposal is
{r07 + EN 'it is FFS whether DNN and S-NSSAI are part of AF provided ECS Address Configuration Information + Removing the two bullets 3 in the cover sheet +EN 'how the 5GC Derives the ECS Configuration Information, considering the Spatial Validity Condition, is FFS' }
Dario S. Tonesi (Qualcomm) is OK with Ulises's proposal
Revised
8.3 S2-2105208 CR Approval 23.502 CR2716R2 (Rel-17, 'C'): ECS Address Configuration in UDM Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103998r07 + changes. Approved Agreed
8.3 S2-2103909 P-CR Approval 23.548: ECS Address Provisioning in Interworking Scenarios . Convida Wireless LLC, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, AT&T, LG Electronics Rel-17 r01 agreed. Revised to S2-2105055. Dan (China Mobile) provide a comment
Mike (Convida Wireless) provides r01 which moves the text into a separate interworking clause as suggested by Dan (China Mobile)
Dan (China Mobile) OK with r01
Fenqin (Huawei) ask question for clarification
Dario S. Tonesi (Qualcomm) replies to Fenqin
Mike (Convida Wireless) replies
Fenqin (Huawei) replies
==== 8.X, 9.X Revisions Deadline ====
Huazhang (vivo) technique discusstion to Mike
Fenqin (Huawei) responds
Dario S. Tonesi (Qualcomm) comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105055 P-CR Approval 23.548: ECS Address Provisioning in Interworking Scenarios . Convida Wireless LLC, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, AT&T, LG Electronics Rel-17 Revision of S2-2103909r01. Approved Approved
8.3 S2-2103910 CR Approval 23.502 CR2635R2 (Rel-17, 'F'): ECS Address Provisioning in Interworking Scenarios Convida Wireless LLC, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, AT&T, LG Electronics Rel-17 Revision of (Revised into S2-2103012, agreed) S2-2102329. Approved Fenqin (Huawei) same comment as 3909
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) comments.
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2103912 P-CR Approval 23.548: Using the UE Location to Decide what ECS Addresses are Sent . Convida Wireless LLC, Lenovo, Motorola Mobility Rel-17 Merged into S2-2105056 Hui(Huawei) questions whether ECS has service area.
Mike (Convida Wireless) replies to Hui (Huawei)
Huazhang (vivo) have some technique discussion to Mike
Dan(China Mobile) support this paper
Mike (Convida Wireless) replies to Huazhang (vivo)
Hui(Huawei) replies.
Tingfang (Lenovo) replies
Dario S. Tonesi (Qualcomm) supports Ni Hui that the concept of ECS service area has not been defined.
Mike (Convida Wireless) replies and provides r01
Hui (Huawei) clarifies that this paper is conflicting with S2-2103999.
Hui (Huawei) suggest to merge this paper into S2-2103999.
Mike (Convida Wireless) agrees to mark this paper as merged with S2-2103999
Laurent (Nokia): provides r02
Laurent (Nokia): please disregard r02 and my latest sending. I missed a few mails
Hui (Huawei) confirms that this paper is merged into S2-2103999.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2103913 CR Approval 23.502 CR2749 (Rel-17, 'C'): Using the UE Location to Decide what ECS Addresses are Sent Convida Wireless LLC, Lenovo, Motorola Mobility Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2103999 P-CR Approval 23.548: ECS Address Configuration . Nokia, Nokia Shanghai Bell Rel-17 r05 agreed. Revised to S2-2105056, merging S2-2103912 Dan (China Mobile) suggest this paper's part can be merged with S2-2103912 so that we can have one paper in TS23.548 for changing ECS address configuration
Huazhang (vivo) provides R01 and object to delete ECS ID
Dario S. Tonesi (Qualcomm) objects to r01.
Magnus O (Ericsson) provides r02.
Huazhang (vivo) replies to Dario
Hui (Huawei) clarifies that this paper is conflicting with S2-2103912.
Hui(Huawei) provides r03
Dan(China Mobile) provides r04
Mike (Convida Wireless) provides r05 which merges in S2-2103912 and adds Convida Wireless as a co-signer
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105056 P-CR Approval 23.548: ECS Address Configuration . Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103999r05, merging S2-2103912. Approved Approved
8.3 S2-2104041 DISCUSSION Agreement Discussion ECS Address Configuration Information for multiple EECs. InterDigital Inc. Rel-17 Noted Magnus O (Ericsson): This is a discussion document and it should be Noted
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104045 CR Approval 23.502 CR2760 (Rel-17, 'C'): ECS Address Configuration Information for multiple EECs InterDigital, Europe, Ltd. Rel-17 Noted Dario S. Tonesi (Qualcomm) objects to this paper to move the discussion to 3998.
Ulises Olvera (InterDigital): replies to Dario (Qualcomm)
Dario S. Tonesi (Qualcomm) replies.
Ulises Olvera (InterDigital) agrees with Dario's suggestion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104058 P-CR Approval 23.548: ECS Address Configuration Information for multiple EECs . InterDigital Inc Rel-17 Noted Magnus O (Ericsson) I think this paper should be Noted.
Ulises Olvera (InterDigital) requests Magnus (Ericsson) to provide the technical reasons why the paper should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104042 P-CR Approval 23.548: Update NOTE on roaming scenario for ECS Address Provisioning . LG Electronics Rel-17 r03 agreed. Revised to S2-2105057. Changhong (Intel) provides r01.
Hui (Huawei) provides r02.
Dario S. Tonesi (Qualcomm) provides r03
Hyunsook (LGE) provides a comment and can live with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105057 P-CR Approval 23.548: Update NOTE on roaming scenario for ECS Address Provisioning . LG Electronics Rel-17 Revision of S2-2104042r03. Approved Approved
8.3 S2-2104066 P-CR Approval 23.548: Update on ECS Address Configuration information provisioning. Samsung Rel-17 Noted Dario S. Tonesi (Qualcomm) objects to this paper and proposes to take 3999 as baseline.
Hyesung (Samsung) replies.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104155 CR Approval 23.502 CR2780 (Rel-17, 'C'): Update on ECS Address Configuration Information Parameters Samsung Rel-17 Merged into S2-2103998 (Noted) Hyesung (Samsung) agrees on the suggestion to merge this CR into S2-2103998.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104366 CR Approval 23.502 CR2805 (Rel-17, 'B'): Update of ECS address configuration parameters vivo Rel-17 Noted Dario S. Tonesi (Qualcomm) objects to this paper to move the discussion to 3998.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104360 P-CR Approval 23.548: A UE capability to deliver the ECS address to dedicated EEC. vivo Rel-17 Noted Hyesung (Samsung) asks a question for clarification.
Huazhang (vivo) replies to Hyesung
Magnus (Ericsson) comments
huazhang (vivo) reply to Magnus
Tingfang (Lenovo) comments.
Huazhang (vivo) replys to Tingfang
Dario S. Tonesi (Qualcomm) objects to this paper and proposes to take 3999 as baseline for discussion
Huazhang (vivo) ask for technique discussion to Dario
Huazhang (vivo) ask for technique discussion and provides r01
Laurent (Nokia): Comments
Dario S. Tonesi (Qualcomm) replies
Huazhang (vivo): replys to Dario and Laurent, and provides r01
Ulises Olvera (InterDigital Inc.) suggest to merge this paper in S2-2103998.
Huazhang (vivo) replys to Ulises and want to keep this paper discussion alone.
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) comments.
Huazhang (vivo) replys to Hui
Dario S. Tonesi (Qualcomm) objects to r01
Huazhang (vivo) reply to Dario, Misunderstand the content,
Ulises Olvera (InterDigital Inc.) objects to any version of this paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104362 P-CR Approval 23.548: Methods of AF get GPSI and 5GC configures ECS address for any UEs. vivo, Convida Wireless LLC Rel-17 CC#5: r05 + changes agreed. Revised to S2-2105210. Huazhang (vivo) suggests use this paper as baseline to resolve the ENs: AF get GPSI in ECS address provision
Dan (China Mobile) comments for the any UE and provide r01
Tingfang (Lenovo) provides r02.
Laurent (Nokia): provides r03
Magnus (Ericsson): provides r04
Dan (China Mobile): provides r05
==== 8.X, 9.X Revisions Deadline ====
Tingfang (Lenovo) proposes to go with r04, objects r00,r01 and r05.
Magnus (Ericsson) proposes to go with r04, objects r00-r03.
Dan(China Mobile) object to r04,r03,r02, can accept r01 and r05.
Laurent (Nokia): objects to R01 and R05
Laurent (Nokia): suggests that we concentrate our effort in progressing 3998 at this meeting
Huazhang (vivo): how about go for r05 + ENs about any UE
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105210 P-CR Approval 23.548: Methods of AF get GPSI and 5GC configures ECS address for any UEs. vivo, Convida Wireless LLC Rel-17 Revision of S2-2104362r05 + changes. Approved Approved
8.3 - - - Local network exposure - - Docs:=19 -
8.3 S2-2103997 CR Approval 23.501 CR2856R1 (Rel-17, 'B'): Newly added parameters for Local NEF discovery Vivo, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103016. Merged into S2-2105058 Laurent (Nokia): provides r01
Huazhang (vivo) objects any version of this paper and propose to merge this paper to 4400
Laurent (Nokia): accepts 3997 to be merged in 4400
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104400 CR Approval 23.501 CR2856R2 (Rel-17, 'B'): Newly added parameters for Local NEF discovery vivo, InterDigital Inc Rel-17 Revision of (Agreed) S2-2103016. r10 agreed. Revised to S2-2105058, merging S2-2103997 Laurent (Nokia): asks a question and comments
Huazhang (vivo): answers to Laurent and use this paper as baseline, merge 3999 into 4400
Huazhang (vivo): provides r01 and merge 3997 into r01
Laurent (Nokia): provides r02
Huazhang (vivo): provides r03
Ulises Olvera (InterDigital): provides answers on top of Huazhang's reply. Answers are reflected in r04 also provided
Huazhang (vivo): is ok for the r04
Xinpeng (Huawei): questions for clarification.
huazhang (vivo): replys to xinpeng
Marisa (Ericsson) asks question
Dario S. Tonesi (Qualcomm) asks question
Huazhang (vivo) response to Marisa
Huazhang (vivo) replys to Dario
Huazhang (vivo) provides r05 based on r04, modify the possibly to optionally
Ulises Olvera (InterDigital Inc.) replies to quesitons from Ericsson, Huawei and Qualcomm and provides r06
Laurent (Nokia): provides r07
Huazhang (vivo): don't agree to remove DNAI and note 2 in R07, and provides r08
Ulises Olvera (InterDigital): Replies to Laurent's comments on r06, adds additional comments to r07, and provides r09
Marisa (ericsson) provides r10
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R00, R01, R03, R04, R05, R06, R08. Laurent prefers R09
Huazhang (vivo): let's go with R09
Huazhang (vivo) can go both r09 or r10, and I find laurent don't object r10, so r10 is ok
Ulises Olvera (InterDigital Inc.) can agree to r09 or r10.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105058 CR Approval 23.501 CR2856R3 (Rel-17, 'B'): Newly added parameters for Local NEF discovery vivo, InterDigital Inc Rel-17 Revision of S2-2104400r10, merging S2-2103997. Approved Agreed
8.3 S2-2104142 CR Approval 23.501 CR2899 (Rel-17, 'B'): N4 interface enhancement for local notification Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2105059. Laurent (Nokia): provides r01
Haiyang(Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R00
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105059 CR Approval 23.501 CR2899R1 (Rel-17, 'B'): N4 interface enhancement for local notification Huawei, HiSilicon Rel-17 Revision of S2-2104142r02. Approved Agreed
8.3 S2-2104143 CR Approval 23.503 CR0587 (Rel-17, 'B'): Policy control enhancement for local notification Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2105060. Laurent (Nokia): provides r01
Marisa (Ericsson) comments and provides r02
Haiyang (Huawei) provides r03
Haiyang (Huawei) provides r04 and withdraw r03
Mirko (Huawei) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R00
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105060 CR Approval 23.503 CR0587R1 (Rel-17, 'B'): Policy control enhancement for local notification Huawei, HiSilicon Rel-17 Revision of S2-2104143r05. Approved Agreed
8.3 S2-2104150 CR Approval 23.501 CR2900 (Rel-17, 'B'): UPF function update to support network information exposure Tencent Rel-17 r01 agreed. Revised to S2-2105061. Laurent (Nokia): provides R01
Zhuoyun Zhang (Tencent) is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R00
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105061 CR Approval 23.501 CR2900R1 (Rel-17, 'B'): UPF function update to support network information exposure Tencent Rel-17 Revision of S2-2104150r01. Approved Agreed
8.3 S2-2104367 P-CR Approval 23.548: Remove EN on duplicated notification. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2105062. Laurent (Nokia): provides r01
Marisa (Ericsson) asks question
Haiyang (Huawei) replies.
Marisa (ericsson) comments
Haiyang (Huawei) provides response
Marisa (Ericsson) replies
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R00
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105062 P-CR Approval 23.548: Remove EN on duplicated notification. Huawei, HiSilicon Rel-17 Revision of S2-2104367r01. Approved Approved
8.3 S2-2104404 P-CR Approval 23.548: Network exposure through SBA interface between UPF and local NEF. China Mobile Rel-17 Revision of (Postponed) S2-2102659. r05 agreed. Revised to S2-2105063. Laurent (Nokia): provides r01
Ulises Olvera (InterDigital Inc.): provides r02, with additional editorial updates
Dan (China Mobile): provides r03 based on r02 with adding Samsung and Intel as supporting company
Haiyang(Huawei) indicates some change marks are missing in r02 and r03, and provides r04
Laurent (Nokia): provides r05
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version except R05
Dan(China Mobile) OK with R05
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105063 P-CR Approval 23.548: Network exposure through SBA interface between UPF and local NEF. China Mobile Rel-17 Revision of S2-2104404r05. Approved Approved
8.3 S2-2104409 CR Approval 23.502 CR2687R1 (Rel-17, 'B'): The introduction of UPF Service China Mobile Rel-17 Revision of (Postponed) S2-2102687. Confirm Spec version used - CR states 17.1.0! r02 agreed. Revised to S2-2105064. Haiyang (Huawei) provides r01
Laurent (Nokia): provides r02
Laurent (Nokia): comment
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to any version except R02
Dan (China Mobile) OK with R02
Marisa (ericsson) asks to postpone
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105064 CR Approval 23.502 CR2687R2 (Rel-17, 'B'): The introduction of UPF Service China Mobile Rel-17 Revision of S2-2104409r02. Approved Agreed
8.3 S2-2104695 CR Approval 23.502 CR2861 (Rel-17, 'B'): Monitoring QoS Flow for exposure of QoS monitoring event Samsung Rel-17 Noted Haiyang (Huawei) provides comments.
Kisuk (Samsung) replies to Huawei.
Haiyang (Huawei) comments.
Haiyang (Huawei) suggests to note this paper as 4711r04 is enough.
==== 8.X, 9.X Revisions Deadline ====
Haiyang (Huawei) asks questions.
Kisuk (Samsung) replies.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104709 CR Approval 23.502 CR2864 (Rel-17, 'B'): Supporting exposure of QoS monitoring event Samsung Rel-17 Noted Laurent (Nokia): provides r01
Susana (Vodafone) provides r02
Haiyang (Huawei) has concerns
Kisuk (Samsung) is ok with r02
Haiyang (Huawei) cannot accept r00, r01 and r02, suggest to note this paper
==== 8.X, 9.X Revisions Deadline ====
Kisuk (Samsung) replies to Huawei.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104710 CR Approval 23.502 CR2865 (Rel-17, 'B'): Procedure for low latency exposure of QoS monitoring via NEF Samsung Rel-17 Noted Laurent (Nokia): comments and suggests to 'merge' in S2-2104404
Kisuk (Samsung): merge into S2-2104404
Haiyang (Huawei) indicates this paper should 'merge' to S2-2104409(502 CR) but not S2-2104404 (548 pCR)
Kisuk (Samsung) replies to Huawei.
Haiyang (Huawei) clarifies.
Laurent (Nokia): objects to any version of this Tdoc
==== 8.X, 9.X Revisions Deadline ====
Kisuk (Samsung) replies to Nokia.
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104711 CR Approval 23.502 CR2866 (Rel-17, 'B'): Update the NF services for low latency exposure of QoS monitoring via NEF Samsung Rel-17 Noted Laurent (Nokia): comments and provides r01
Haiyang (Huawei) comments
Marisa (ericsson) provides revision
Haiyang (Huawei) further comments and cannot accept r00, r01 and r02
Kisuk (Samsung) is Ok with r2.
Haiyang (Huawei) provides r03
Laurent (Nokia): answers
==== 8.X, 9.X Revisions Deadline ====
Kisuk (Samsung) accepts r01 and r02 but cannot accept r03.
Kisuk (Samsung) comments
Haiyang (Huawei) provides comments
==== 8.X, 9.X Final Deadline ====
Noted
8.3 - - - EAS IP replacement - - Docs:=11 -
8.3 S2-2104032 CR Approval 23.501 CR2757R2 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Intel, Lenovo, Tencent, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103009. r02 agreed. Revised to S2-2105065, merging S2-2104510 Hui (Huawei) proposes r01.
Shubhranshu (Nokia) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105065 CR Approval 23.501 CR2757R4 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Intel, Lenovo, Tencent, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of S2-2104032r02, merging S2-2104510. Approved Agreed
8.3 S2-2104033 CR Approval 23.502 CR2648R2 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Intel, Lenovo, Tencent, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103010. r01 agreed. Revised to S2-2105066. Shubhranshu (Nokia) asks for clarification and provides r01
Hui (Huawei) responses to Nokia.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) replies to Shubhranshu (Nokia).
Shubhranshu (Nokia) responds
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105066 CR Approval 23.502 CR2648R3 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Intel, Lenovo, Tencent, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of S2-2104033r01. Approved Agreed
8.3 S2-2104034 P-CR Approval 23.548: Update Clause 6.3.3 on EAS IP Replacement in 5GC. Intel, Lenovo, Motorola Mobility, Tencent, Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2105067. Dario S. Tonesi (Qualcomm) comments that only one option should be captured.
Changhong replies to Dario S. Tonesi (Qualcomm) comments.
Dario S. Tonesi (Qualcomm) providers r01
Dario S. Tonesi (Qualcomm) provides r02 and r03 and asks to ignore r01.
Shubhranshu (Nokia) comments and asks for clarification
Changhong replies to Shubhranshu and provides r04.
Shubhranshu (Nokia) provides r05
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) proposes to go with r05.
Hui (Huawei) is fine with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105067 P-CR Approval 23.548: Update Clause 6.3.3 on EAS IP Replacement in 5GC. Intel, Lenovo, Motorola Mobility, Tencent, Huawei, HiSilicon Rel-17 Revision of S2-2104034r05. Approved Approved
8.3 S2-2104047 P-CR Approval 23.548: Update of Edge Relocation Using EAS IP Replacement . Tencent, Intel Rel-17 Revision of (Noted) S2-2102717. r05 agreed. Revised to S2-2105068. Dario S. Tonesi (Qualcomm) think that this contribution is not needed.
Shubhranshu (Nokia) also thinks this is not needed and thus Note this paper
Magnus (Ericsson) share the views from Qualcomm and Nokia and thinks the contribution should be Noted
Chunshan (Tencent) provides r01.
Shubhranshu (Nokia) responds
Chunshan (Tencent) responds .
Shubhranshu (Nokia) comments to note this paper
Chunshan (Tencent) provides r02.
Hui (Huawei) provide r03
Shubhranshu (Nokia) provides r04
Chunshan (Tencent) clarifies that r04 is no change .
Shubhranshu (Nokia) comments and provides r05
==== 8.X, 9.X Revisions Deadline ====
Chunshan (Tencent) responses.
Chunshan (Tencent) comments.
Magnus (Ericsson) proposes to Note the document or go with r05.
Chunshan (Tencent) can accept r05.
Hui (Huawei) fine with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105068 P-CR Approval 23.548: Update of Edge Relocation Using EAS IP Replacement . Tencent, Intel Rel-17 Revision of S2-2104047r05. Approved Approved
8.3 S2-2104509 P-CR Approval 23.548: Update on EAS IP replacement procedures. Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.3 S2-2104510 CR Approval 23.501 CR2757R3 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Huawei, Hisilicon, [Intel, Lenovo, Tencent, Motorola Mobility] Rel-17 Revision of (Agreed) S2-2103009. Merged into S2-2105065 Changhong (Intel) proposes to merge it into S2-2104032.
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) confirm this paper was merged into S2-2104032.
==== 8.X, 9.X Final Deadline ====
Merged
8.3 S2-2104511 CR Approval 23.503 CR0553R2 (Rel-17, 'B'): AF Influence enhancement for EAS IP replacement Huawei, HiSilicon, [Intel, Lenovo, Tencent, Motorola Mobility] Rel-17 Revision of (Agreed) S2-2103011. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 - - - AF relocation - - Docs:=6 -
8.3 S2-2104288 CR Approval 23.501 CR2913 (Rel-17, 'B'): Updates to AF requests to influence traffic routing CATT, Nokia, Nokia Shanghai Bell Rel-17 CC#4: r01 + changes agreed. Revised to S2-2105147. Marisa (Ericsson) provides r01 and comments.
Yuan (CATT) replies to Marisa (Ericsson).
Fenqin (Huawei) provides comment.
Yuan (CATT) provides comment.
Yuan (CATT) provides r02.
Marisa (ericsson) replies
==== 8.X, 9.X Revisions Deadline ====
Shubhranshu (Nokia) comments and is OK to r02
Yuan (CATT) suggests we go with r02
Marisa (ericsson) can only accept r01
Fenqin (Huawei) propose to postpone this paper or solve it offline.
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105147 CR Approval 23.501 CR2913R1 (Rel-17, 'B'): Updates to AF requests to influence traffic routing CATT, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104288r01 + changes. Approved Agreed
8.3 S2-2104289 CR Approval 23.502 CR2795 (Rel-17, 'B'): Updates to AF requests to influence traffic routing CATT, Nokia, Nokia Shanghai Bell Rel-17 r08 agreed. Revised to S2-2105069. Yuan (CATT) provides r01.
Marisa (Ericsson) provides r02.
Yuan (CATT) provides r03.
Shubhranshu (Nokia) provides r04
Fenqin (Huawei) provides r05
Yuan (CATT) replies to Fenqin (Huawei).
Shubhranshu (Nokia) responds and provides r06
Yuan (CATT) replies to Shubhranshu (Nokia)
Fenqin (Huawei) responds
Marisa (Ericsson) provides r07.
Yuan (CATT) provides r08.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) comments on r08.
Yuan (CATT) replies to Changhong (Intel).
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105069 CR Approval 23.502 CR2795R1 (Rel-17, 'B'): Updates to AF requests to influence traffic routing CATT, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104289r08. Approved Agreed
8.3 S2-2104457 P-CR Approval 23.548: Edge Relocation Involving AF change. NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 r03 agreed. Revised to S2-2105070. Fenqin (Huawei) comments and provides r01.
Yuan (CATT) provides r02.
Higo (NTT DOCOMO) provides r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105070 P-CR Approval 23.548: Edge Relocation Involving AF change. NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104457r03. Approved Approved
8.3 - - - DNAI based (I-)SMF selection - - Docs:=7 -
8.3 S2-2104290 CR Approval 23.501 CR2914 (Rel-17, 'F'): Update on I-SMF selection per DNAI CATT, ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.3 S2-2104291 CR Approval 23.502 CR2796 (Rel-17, 'B'): I-SMF selection for subsequent PDU session CATT, ZTE Rel-17 r02 agreed. Revised to S2-2105071. Shubhranshu (Nokia) comments and provides r01
Yuan (CATT) responds to Shubhranshu (Nokia).
Fenqin (Huawei) comment and provide r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105071 CR Approval 23.502 CR2796R1 (Rel-17, 'B'): I-SMF selection for subsequent PDU session CATT, ZTE Rel-17 Revision of S2-2104291r02. Approved Agreed
8.3 S2-2104474 CR Approval 23.502 CR2827 (Rel-17, 'F'): Add N3 tunnel information in SM context for I-SMF reselection per DNAI ZTE, Ericsson, Huawei, CATT Rel-17 r01 agreed. Revised to S2-2105072. Dario S. Tonesi (Qualcomm) asks questions for clarification.
Jinguo(ZTE) response to Dario S. Tonesi (Qualcomm) and provide r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105072 CR Approval 23.502 CR2827R1 (Rel-17, 'F'): Add N3 tunnel information in SM context for I-SMF reselection per DNAI ZTE, Ericsson, Huawei, CATT Rel-17 Revision of S2-2104474r01. Approved Agreed
8.3 S2-2104508 CR Approval 23.502 CR2830 (Rel-17, 'B'): Clarification on target DNAI Information stored in AMF Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2105073. Changhong (Intel) comments.
Hui (Huawei) replies.
Shubhranshu (Nokia) responds
Yuan (CATT) responds.
Changhong (Intel) asks to update the 'reason for change' part to explain why target DNAI information should be used.
Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105073 CR Approval 23.502 CR2830R1 (Rel-17, 'B'): Clarification on target DNAI Information stored in AMF Huawei, HiSilicon Rel-17 Revision of S2-2104508r01. Approved Agreed
8.3 - - - UL buffering - - Docs:=8 -
8.3 S2-2104399 CR Approval 23.502 CR2650R1 (Rel-17, 'B'): EC KI2 Target PSA buffering for SSC mode 3 NTT DOCOMO Rel-17 Revision of (Agreed) S2-2102453. r02 agreed. Revised to S2-2105074. Shubhranshu (Nokia) asks for clarification and provides r01
Riccardo (NTT DOCOMO) replies to Shubhranshu and provides r02
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) provides comments
Riccardo (NTT DOCOMO) replies to Jinguo
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105074 CR Approval 23.502 CR2650R2 (Rel-17, 'B'): EC KI2 Target PSA buffering for SSC mode 3 NTT DOCOMO Rel-17 Revision of S2-2104399r02. Approved Agreed
8.3 S2-2104512 P-CR Approval 23.548: Updates to remove the ENs in Packet Buffering for Low Packet Loss. Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2105075. Marisa (Ericsson) comments and provides revision
Hui (Huawei) provides r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105075 P-CR Approval 23.548: Updates to remove the ENs in Packet Buffering for Low Packet Loss. Huawei, HiSilicon Rel-17 Revision of S2-2104512r02. Approved Approved
8.3 S2-2104513 CR Approval 23.501 CR2934 (Rel-17, 'F'): Update on uplink traffic buffering Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2105076. Dario S. Tonesi (Qualcomm) provides r01 and comments.
Hui (Huawei) fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105076 CR Approval 23.501 CR2934R1 (Rel-17, 'F'): Update on uplink traffic buffering Huawei, HiSilicon Rel-17 Revision of S2-2104513r01. Approved Agreed
8.3 S2-2104514 CR Approval 23.502 CR2831 (Rel-17, 'F'): Updates on uplink traffic buffering Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2105077. Marisa (ericsson) comments
Hui (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105077 CR Approval 23.502 CR2831R1 (Rel-17, 'F'): Updates on uplink traffic buffering Huawei, HiSilicon Rel-17 Revision of S2-2104514r01. Approved Agreed
8.3 - - - UP latency requirement - - Docs:=10 -
8.3 S2-2104554 P-CR Approval 23.548: Clarification on User Plane Latency Requirement. Samsung Rel-17 r03 agreed. Revised to S2-2105078, merging S2-2104749 Shubhranshu (Nokia) responds
Jicheol clarify the usage case again to help Shbubranshu avoid the confusion.
Dario S. Tonesi (Qualcomm) asks question for clarification.
Jicheol (Samsung) answers the question for Dario (Qualcomm).
Jicheol (Samsung) thanks Shubranshu for its suggestions and clarifies them.
Jicheol (Samsung) thank Shubhranshu (Nokia) for redirect Magnus H (Ericsson)'s comment to this pCR.
Jicheol (Samsung) provides r01 based on Shubranshu (Nokia)'s suggestion.
Magnus H (Ericsson) comments
Jicheol (Samsung) answers to Magnus (Ericsson)'s question.
Shubhranshu (Nokia) comments and provides r02
Hui(Huawei) provides r03
Shubhranshu (Nokia) is OK to r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105078 P-CR Approval 23.548: Clarification on User Plane Latency Requirement. Samsung Rel-17 Revision of S2-2104554r03, merging S2-2104749. Approved Approved
8.3 S2-2104561 P-CR Approval 23.548: Authorization of User Plane Latency Requirements. Samsung Rel-17 r01 agreed. Revised to S2-2105079. Shubhranshu (Nokia) comments and provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105079 P-CR Approval 23.548: Authorization of User Plane Latency Requirements. Samsung Rel-17 Revision of S2-2104561r01. Approved Approved
8.3 S2-2104575 CR Approval 23.501 CR2804R2 (Rel-17, 'B'): Edge relocation considering user plane lantecy requirement Samsung Rel-17 Revision of (Agreed) S2-2103007. r01 agreed. Revised to S2-2105080. Shubhranshu (Nokia) comments and provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105080 CR Approval 23.501 CR2804R3 (Rel-17, 'B'): Edge relocation considering user plane lantecy requirement Samsung Rel-17 Revision of S2-2104575r01. Approved Agreed
8.3 S2-2104585 CR Approval 23.502 CR2841 (Rel-17, 'B'): Clarifications on User Plane Latency Requirement Samsung Rel-17 r01 agreed. Revised to S2-2105081. Shubhranshu (Nokia) comments and provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.3 S2-2105081 CR Approval 23.502 CR2841R1 (Rel-17, 'B'): Clarifications on User Plane Latency Requirement Samsung Rel-17 Revision of S2-2104585r01. Approved Agreed
8.3 S2-2104598 CR Approval 23.503 CR0598 (Rel-17, 'B'): Clarifications on User Plane Latency Requirement Samsung Rel-17 Noted Magnus H (Ericsson) ask question
Shubhranshu (Nokia) responds and provides r01
Jicheol (Samsung) responds.
Jicheol (Samsung) provides r02.
Magnus H (Ericsson) comments and suggests to note this CR.
Jicheol clarified that Magnus H (Ericsson)'s comments is not related with this CR.
Hui (Huawei) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Magnus H (Ericsson) objects to this CR
==== 8.X, 9.X Final Deadline ====
Noted
8.3 S2-2104749 P-CR Approval 23.548: Edge Relocation Considering User Plane Latency Requirement . Nokia, Nokia Shanghai Bell Rel-17 Revision of (Noted) S2-2102948. Merged into S2-2105078 Jicheol (Samsung) proposes to note this pCR. (please see S2-2104554 for the clarification)
Shubhranshu (Nokia) replies and asks for clarification
Jicheol (Samsung) answers.
Hui (Huawei) comments.
Jicheol (Samsung) comments.
==== 8.X, 9.X Revisions Deadline ====
Hui (Huawei) confirms that this paper is merged into S2-2104554.
==== 8.X, 9.X Final Deadline ====
Merged
8.4 - - - Enhancement of Network Slicing Phase 2 (eNS_Ph2) - - Docs:=89 -
8.4 S2-2104523 CR Approval 23.501 CR2937 (Rel-17, 'B'): NSAC with consideration of access type Samsung Rel-17 r06 agreed. Revised to S2-2104896. George (Ericsson) proposes to note the CR. Please see additional comments
Hoyeon (Samsung) replies to George (Ericsson)
George (Ericsson) provides a response. I am Ok with this. I have some more addition to the 23.50 one. Please see 4528.
Hoyeon (Samsung) provides r01.
George (Ericsson) provides a response. I did not see this one when I res[ponded on the 23.502 equivalent. This is much better. However, do we really want the operator policy still if the slice applies to both access types ?
Jinguo(ZTE) provides r02
George (Ericsson) Is OK with this, but please fix the note syntax.
Yunjing (CATT) asks question for clarification.
Hoyeon (Samsung) provides r03 (clean version, no additional change), provides comments on both access case, and replies to Yunjing (CATT).
George (Ericsson) provides r04, Co-signed.
Fenqin (Huawei) provides r05 and co-signed
Jinguo(ZTE) response to Fenqin (Huawei)
Fenqin (Huawei) provides r06
Hoyeon (Samsung) is OK with r06.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104896 CR Approval 23.501 CR2937R1 (Rel-17, 'B'): NSAC with consideration of access type Samsung Rel-17 Revision of S2-2104523r06. Approved Agreed
8.4 S2-2104528 CR Approval 23.502 CR2835 (Rel-17, 'B'): NSAC with consideration of access type Samsung Rel-17 r01 agreed. Revised to S2-2104897. George (Ericsson) proposes to note the CR. Please see comments in 4523
Hoyeon (Samsung) replies to George (Ericsson). Please see our response in 4523
George (Ericsson) provides a response. Can U elaborate a bit on how the NSCAF considers the access type. This needs more clarification. The direction is Ok but we need more clarity.
Hoyeon (Samsung) provides r01.
George (Ericsson) provides comment. Its OK for now. 23.501 is thin as well. But this can be improved
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104897 CR Approval 23.502 CR2835R1 (Rel-17, 'B'): NSAC with consideration of access type Samsung Rel-17 Revision of S2-2104528r01. Approved Agreed
8.4 S2-2104406 CR Approval 23.501 CR2837R2 (Rel-17, 'B'): Support of Emergency and Priority Services in Network Slice Admission Control CATT Rel-17 Revision of (Agreed) S2-2103463. r03 agreed. Revised to S2-2104898. Patrice (Huawei) comments that the CR does not answer the question from the EN, therefore the EN cannot be removed.
Yunjing(CATT) replies to Patrice (Huawei) and provides r01.
Patrice (Huawei) is OK with the direction of the update and provides r02 that cleans up and corrects the terminology.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104898 CR Approval 23.501 CR2837R3 (Rel-17, 'B'): Support of Emergency and Priority Services in Network Slice Admission Control CATT Rel-17 Revision of S2-2104406r03. Approved Agreed
8.4 S2-2104408 CR Approval 23.501 CR2924 (Rel-17, 'B'): Network Slice Admission Control in EPC Samsung, Apple, LG Electronics, China Mobile, Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO, ZTE Rel-17 r04 agreed. Revised to S2-2104899. Jinguo(ZTE) provides r01
Fenqin (Huawei) comment and provides r02
Hoyeon (Samsung) provides comments.
Fenqin (Huawei) provides comments.
Hyunsook (LGE) provides a comment.
Jinguo(ZTE) response
Hoyeon (Samsung) provides r03.
George (Ericsson) provides a comment.
Hoyeon (Samsung) replies, and submits r04 for consideration.
==== 8.X, 9.X Revisions Deadline ====
Jinguo (ZTE) is ok with r04. More work on this issue is expected.
Hoyeon (Samsung) agrees with Jinguo (ZTE) that further work on this issue is expected after this meeting.
Hyunsook (LGE) can live with r04 in this meeting.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104899 CR Approval 23.501 CR2924R1 (Rel-17, 'B'): Network Slice Admission Control in EPC Samsung, Apple, LG Electronics, China Mobile, Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO, ZTE Rel-17 Revision of S2-2104408r04. Approved Agreed
8.4 S2-2104261 CR Approval 23.501 CR2909 (Rel-17, 'B'): Support multiple NSACFs for one S-NSSAI during UE mobility China Mobile Rel-17 Confirm Spec version used - CR states 17.1.0! CC#4: r01 agreed. CC#4: r01 + changes agreed. Revised to S2-2105155. George (Ericsson) proposes to note the CR. Please see 3802. The notion of instances is deployment specific. U can have a front end and have as many instances as U want behind it transparent to the AMF.
Genadi (Lenovo) provides comments for clarification.
Fenqin (Huawei) provides comments.
Iskren (NEC)) provides comments.
George (Ericsson) provides comment.
Fenqin (Huawei) provides comment.
Dan (China Mobile) provides response and the consideration
Jinguo(ZTE) supports multiple NSACFs
George (Ericsson) provides response.
Iskren (NEC) provides response.
Dan (China Mobile) do not agree with Ericsson and NEC's comment and I think your reason is not valid
Heng (China Telecom) supports multiple NSACFs
George (Ericsson) What will not work if you have a single front end one NSCAF, used by everyone, and U have used various instances in the background; the front end NSCAF redirects the request to the instance handling the request, based on the UE for example. What do we need to standardize here. This is called communication proxy.
Iskren(NEC) explains why multiple NSACFs per slice support by standardisation is not needed.
George (Ericsson) And there is a way to support that through a communication proxy front end, without standardization.
Ashok (Samsung) provides comments
Fenqin (Huawei) Comments.
Ashok (Samsung) needs clarification
Patrice (Huawei) comments regarding proposals to resolve this in a proprietary manner.
George (Ericsson) Supporting proxy communication, by one NSCAF to multiple NSCAF instance requires only the NSCAF to support that capability; transparent to all NFs. HSS works that way today.
Dan (China Mobile) provide our consideration and explanation, and we think George's proposal can not support our requirement
Dan (China Mobile) provide r01
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) would like to note the CR until we agree on 3802.Then we can revisit this at the next meeting so everything is aligned
Fenqin (Huawei) support r01
Ashok (Samsung) ask question to Dan (China Mobile)
Jinguo(ZTE) response to Ashok (Samsung) and suggest to go with r01
Dan(China Mobile) say Ashok's question is not related with this paper. And suggest we go for r01
Dan (China Mobile) would like to check with George's concern
Srisakul (NTT DOCOMO) provides comment.
Dan(NTT DOCOMO) provides comment.
Dan(China Mobile) provides r02 to clarify the NOTE
Dan(China Mobile) request this paper be handled on CC#3, because this paper is aligned with current agreement.
Dan(China Mobile) provides suggestion text
George (Ericsson) provides a response. Interaction between NSCAF is a solution to a problem. We need to first agree on what is the problem that we now have to address given what we have in 3802 if that progresses.
Dan (China Mobile) provides a update NOTE and also would like check with George
Dan (China Mobile) provides a update sentence and NOTE based on offline discussion
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2105155 CR Approval 23.501 CR2909R1 (Rel-17, 'B'): Support multiple NSACFs for one S-NSSAI during UE mobility China Mobile Rel-17 Revision of S2-2104261r01 + changes. Approved Agreed
8.4 S2-2104345 CR Approval 23.502 CR2802 (Rel-17, 'B'): Updates of Registration Procedure and Handover Procedure to support multiple NSACFs for one S-NSSAI China Mobile Rel-17 Confirm Spec version used - CR states 17.1.0! Noted George (Ericsson) propose to note the CR. Please see additional comments.
Dan (China Mobile) reply to Ericsson and this CR is try to solve multiple NSACF for one network slice, your proposal and comment is not related with this part, so please consider to withdraw your NOTE
Jinguo(ZTE) support this paper
Genadi (Lenovo) provided comments for clarification to S2-2104261, which also apply to S2-2104345.
George(Ericsson) provides a response.
Fenqin(Huawei) provides a comment.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. We fully addressed this in 4648.
Dan (China Mobile) OK to note this paper
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104391 CR Approval 23.502 CR2816 (Rel-17, 'B'): Event Exposure for multiple NSACF instances Huawei, HiSilicon Rel-17 Noted George (Ericsson) proposes to note the CR. Please see additional comments.
Dan (China Mobile) support this paper
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. 3802 provides sufficient support to eliminate the need for this.
Fenqin (Huawei) responds
Dan(China Mobile) support this paper and suggest we can go with r00
Iskren (NEC) comments
Fenqin (Huawei) comments
Iskren (NEC) answers Fenqin (Huawei) comments
Kaisu (Nokia) proposes to note this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104522 CR Approval 23.501 CR2936 (Rel-17, 'B'): Support of multiple NSACF Huawei, HiSilicon Rel-17 Noted George (Ericsson) proposes to note the CR. Please see additional comments
Fenqin (Huawei) responds
Iskren (NEC) provides comment
Dan (China Mobile) support this paper
George (Ericsson) provides a response. Clearly we won't settle this is in Release 17 as several don't agree with that.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. 3802 addresses this.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104460 CR Approval 23.501 CR2727R2 (Rel-17, 'B'): NSACF functional descriptions NTT DOCOMO Rel-17 Revision of (Agreed) S2-2103465. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2104776 CR Approval 23.502 CR2876 (Rel-17, 'B'): AMF - NSACF discovery via NRF Apple Rel-17 Noted George (Ericsson) proposes to note the CR. There is a much simpler proposal in 8302 providing all the needed flexibility
Dan (China Mobile) suggest this paper can be merged into S2-2104456 since both papers are updating the NRF service
Krisztian (Apple) responds to George (Ericsson) .
Krisztian (Apple) responds to Dan (China Mobile). Please see my response to George. S2-2104776 includes changes not covered in S2-2104456.
Fenqin (Huawei) comments
George (Ericsson) provides a comment.
Srisakul (NTT DOCOMO) agrees not merge overlapping part into S2-2104456 and provides r01. NOTE 13 may subject to be removed depending on the clarification provided.
Srisakul (NTT DOCOMO) correct previous comment. We agree to merge overlapping part into S2-2104456 and provides r01. NOTE 13 may subject to be removed depending on the clarification provided.
George (Ericsson)_ provides a comment. The second change is meaningless. Also the first change does not explain how this is resolved. SO we are against all revisions of the CR.
Krisztian (Apple) comments and provides r02.
Srisakul (NTT DOCOMO) provides r03 and comments that solution in r02/r03 is solving the same issue that S2-2104148r01 proposed. We need to discuss whether both tdocs (4776 and 4148) are needed.
George (Ericsson) objects to 4776 and all revisions
Srisakul (NTT DOCOMO) ask George (Ericsson) on the reason for objecting r03.
George (Ericsson) provides a response.
Srisakul (NTT DOCOMO) asks George (Ericsson) further question for clarification.
George (Ericsson) provides a response. I want the piggyback approach. That's all what is needed to control the flag and both nodes are 100% synchronized at all times. The O&M approach was simply saying that the SUB/NOT can be replaced with a much simpler O&M approach.
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. 3805, describing the piggyback solution, fulfills all the needed functionality.
Krisztian (Apple) suggests that SA2 specifies a complete & working feature. I understand that George (Ericsson) prefers the 'piggyback solution' described in 3805 (on which I indicated support from the last meeting onwards), however, if there's no consensus in SA2, 3805 will likely to be NOTED per the rules. I don't think the 'my way or no way' mindset will bring us forward. In 4776, I am just trying to make the existing feature work. I think 4776 completes the existing feature, hence we need it. There's no alternative offered in this meeting including the O&M approach that only exists in this email.
George (Ericsson) responds. It's not my way or no way. There are 2 proposals neither of them are complete for the subscribe Notify. In addition, there is not enough support for either solution; piyggback or SUB/NOT. So how can it be justified that one solution should be completed while the other should stop. This is basically what U are asking for. We approved something that does not work to progress, and now the solution looks more and more rather inappropriate; and it still not completely or accurately documented in Ur CR nor the other CR. Call back URI is s stage 3 term, so we can all be in the same wave length. Ur CR has gaps as well.
Krisztian (Apple) prefers the wording in r02. I can live with r03 but I propose to proceed with r02.
Jinguo(ZTE) support to go with 4776. NRF is the simple way and straight forward
Jinguo(ZTE) prefer r03
Genadi (Lenovo) prefers r03.
George (Ericsson) objects to the original CR and all revisions.
Kaisu (Nokia) provides a comment and proposes to note the CR.
George (Ericsson) provides a comment. And the solution ignores service areas completely. This is like building a double decker plane to carry a bicycle. The bicycle is the EAC flag that will be set once in a blue moon.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2103802 CR Approval 23.501 CR2728R2 (Rel-17, 'B'): Updates of NSACF discovery and selection NTT DOCOMO, Ericsson Rel-17 Revision of (Agreed) S2-2103466. r09 agreed. Revised to S2-2104900, merging S2-2104411 Jinhua (Xiaomi) provides comments for clarification.
Hyunsook (LGE) provides comments.
Dan (China Mobile) provides comments and object this paper's new part which is highlted in yellow.
George (Ericsson) provides comments.
Fenqin (Huawei) provides comments.
George (Ericsson) provides r1
Dan (China Mobile) provides comments and think the r01 is not useful and object this version
Jinguo(ZTE) provides r02 to add the definition. Also update the cover page
Hyunsook (LGE) ask a Q for the clarification.
George (Ericsson ) objects to r02, and provides comment.
Jinguo(ZTE) replies to George (Ericsson ) and Hyunsook (LGE)
George (Ericsson) provides response. I did have an EN in r02, that reads. That's what U are saying. So U can agree with r02.
NOTE: stage 3 will define the Serving Area information. Each Serving Area is unique and unambiguously identifed.
Fenqin (Huawei ) provides comment.
George (Ericsson) provides a response.
Srisakul (NTT DOCOMO) provides comment.
Iskren (NEC) provides comments
Yunjing(CATT) provides comments
Dan(China Mobile) provides comments
Hyunsook (LGE) provides a comment.
George (Ericsson) provides r03. Tightened the spec on TAI, and that every TAI can be served by only a single NSCAF.
Iskren (NEC) expresses concern.
Jinhua (Xiaomi) provide comments and r04
George (Ericsson) provides a response. Actually this is not explicitly addressed. We need to add something there. I guess we need to have a stable base.
Jinhua (Xiaomi) reply to George (Ericsson)
Srisakul (NTT DOCOMO) provides comments and support r03/r04 to move forward.
Jinhua(Xiaomi) reply to Srisakul (NTT DOCOMO), fine to keep NSACF capability open.
Kaisu (Nokia) provides a comment.
George (Ericsson) provides a comment.
Jinguo(ZTE) response
Jinguo(ZTE) suggest to just remove the editor note and let stage 3 to define serving area. and provide r05
George (Ericsson) provides a response. My question was not answered. The question is : If I am an AMF, and I receive back 4 NSCAFs with different service area info, whether there is a different TA, scalar, text representing the service area, which one should I use ?. How does the AMF decide which one to use.
George (Ericsson) provides a response. Then we should add that the AMF selects the NSCAF whose service area matches the area configured in the AMF. There can also be no overlapping service areas between NSCAFs, there must be a service area that is default in case there is no match (that why scalar is not error prone vs text). Lots of details are missing. No TAs either.
Fenqin (Huawei) comment and provides r06.
Hoyeon (Samsung) asks a question on the approach in r05 and r06.
Srisakul (NTT DOCOMO) responds to Hoyeon's questions.
Iskren answers Srisakul (NTT DOCOMO).
Dan (China Mobile) do not agree to leave this to R18, if we can not solve this problem, this means the NSACF mechanism can not be used at all
George (Ericsson) provides a comment and response.
Fenqin (Huawei) provides a comment and response.
Jinguo(ZTE) provides r07
George (Ericsson) asks a question. We don't have a notion of NSCAF set. Please remove the word set..
Fenqin (Huawei) responds
George (Ericsson) responds. It is introduced for SMF, etc. I can't agree to use the term set here. This is the first occurrence of it. So we object to r08
George (Ericsson) responds. We have not endorsed instances for NSCAF in Release 17.
Fenqin (Huawei) so what does it mean? Do you think NSACF is not a NF instance or what others?
George (Ericsson) responds. We have not endorsed instances for NSCAF in Release 17. U are bringing in now the distribution architecture discussion in this CR.
Fenqin (Huawei) responds. If the NSACF is not deployed as NF instance, how it is deployed at the network ?
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) Check with George whether he can live with r08
George (Ericsson) accepts r07 only.
Fenqin (Huawei) accept only r06/r08
Jinguo(ZTE) suggest to go with r07 with removing 'stage 3 will define the Serving Area information' in the NOTE. provide r09
George (Ericsson) accepts r09.
TAO(VC) can we go with Jinguo's proposal
Fenqin (Huawei) accept r09
Srisakul (NTT DOCOMO) ok with r09.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104900 CR Approval 23.501 CR2728R4 (Rel-17, 'B'): Updates of NSACF discovery and selection NTT DOCOMO, Ericsson Rel-17 Revision of S2-2103802r09, merging S2-2104411. Approved Agreed
8.4 S2-2104411 CR Approval 23.501 CR2728R3 (Rel-17, 'B'): Updates of NSACF discovery and selection CATT Rel-17 Revision of (Agreed) S2-2103466. Merged into S2-2104900 George (Ericsson) proposes to note the CR. We have a simpler solution per region. Please see 3802
Yunjing(CATT) replies to George (Ericsson).
George (Ericsson) provides a response.
Srisakul (NTT DOCOMO) provides comment and agrees with George's comment.
Yunjing(CATT) replies.
Heng(China Telecom) comment to Yunjing.
Yunjing (CATT) provides r01 based on comment from Heng(China Telecom).
George (Ericsson) asks a question. Please explain how the UE location is used.
Jinhua(Xiaomi) provide comments, propose to merge 4411 into 3802
Srisakul (NTT DOCOMO) provide comments, agree with Jinhua (Xiaomi) to merge this paper into 3802.
Yunjing (CATT) is ok to merge this CR into 3802.
Hoyeon (Samsung) provides comments.
George (Ericsson) provides comment. We won't include UE location before we understand why it is needed and the use case for it.
Jinguo(ZTE) shares same view, UE location is irrelevant here.
Srisakul (NTT DOCOMO) provides comment.
Yunjing (CATT) replies to comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104456 CR Approval 23.502 CR2633R1 (Rel-17, 'B'): NSACF discovery and selection NTT DOCOMO Rel-17 Revision of (Postponed) S2-2102324. r02 agreed. Revised to S2-2104901.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104901 CR Approval 23.502 CR2633R2 (Rel-17, 'B'): NSACF discovery and selection NTT DOCOMO Rel-17 Revision of S2-2104456r02. Approved Agreed
8.4 S2-2103803 CR Approval 23.501 CR2789R2 (Rel-17, 'B'): Roaming support for NSAC Ericsson, (Huawei, HiSilicon) Rel-17 Revision of (Agreed) S2-2103066. Merged into S2-2104902 Fenqin (Huawei) suggest to merge this paper to 4388
George (Ericsson) provides a response.
Fenqin (Huawei) provides a response.
Jinguo(ZTE) suggest to merge this paper into 4388
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104388 CR Approval 23.501 CR2789R3 (Rel-17, 'B'): Roaming support for NSAC Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103066. r12 agreed. Revised to S2-2104902, merging S2-2103803 and S2-2104778 George (Ericsson) proposes to note the CR.
Fenqin (Huawei) responds.
George (Ericsson) responds.
Jinguo(ZTE) provides r01 to merge some text from 3803
George (Ericsson) provides r02. Also see comments.
Kaisu(Nokia) posts a comment on the home routed case.
George (Ericsson) asks a question.
Fenqin (Huawei) responds and provides r03.
George (Ericsson) provides r04. Added Ericsson, one minor editorial, and removed the editors note. I don't understand the justification for it. We need to wrap up, not add more EN without clear justification.
Kaisu (Nokia) provides a comment.
George (Ericsson) provides a response.
Hoyeon (Samsung) provides a comment.
Krisztian (Apple) provides r05 that fixes many terminology issues and adds Apple support.
George (Ericsson) asks a questions.
Krisztian (Apple) responds to George (Ericsson): Both changes are fine with me.
George (Ericsson) responds. So I will do an updated revision next week.
Iskren (NEC) added NEC as a supporting company.
George (Ericsson) provides r07. Minor edirotail changes discussed below.
Jinguo(ZTE) comments
Fenqin(Huawei) responds
Gerald (Matrixx) with suggestion of chapter 5.15.11.x structure.
Hoyeon (Samsung) provides comments, and r08
Gerald (Matrixx) with more clarification.
George (Ericsson) asks a question on r08
Fenqin (Huawei) also ask a question for r08
Fenqin (Huawei) some more clarification
Hoyeon (Samsung) replies.
Hoyeon (Samsung) replies to Fenqin (Huawei)
Jinguo(ZTE) provides r09
Kaisu (Nokia) repeats the question on HPLMN and provides r10.
Iskren (NEC) supports the proposal by Kaisu (Nokia)
Jinguo (ZTE) ask question on the new EN
Hoyeon (Samsung) supports the proposal by Kaisu (Nokia), and provides r11.
George (Ericsson) provides a comment.
Hoyeon (Samsung) replies to George (Ericsson).
George (Ericsson) asks a question, Can U please highlight the problematic text in the CR.
Kaisu (Nokia) replies to Jinguo (ZTE)
Fenqin (Huawei) responds and provides r12.
Verizon prefers r10.
==== 8.X, 9.X Revisions Deadline ====
Jinguo(ZTE) suggest to go with r12
Hoyeon (Samsung) is OK with r09 (if the new bullet means VPLMN S-NSSAI configuration in AMF and SMF), and also OK with r10 onward.
Tao(VC) it seem r10 got more preference? Please indicate clearly in your email if you have strong view between r10 and r12.
Fenqin (Huawei) propose to go with r12.
Hoyeon (Samsung) replies to Tao(VC), and suggests to go with r12.
Hoyeon (Samsung) replies to Jinguo(ZTE).
Srisakul (NTT DOCOMO) provides comment on texts in EN of r12.
Kaisu (Nokia) indicates that Nokia is ok with both r10 and r12.
Srisakul (NTT DOCOMO) comments.
Srisakul (NTT DOCOMO) comments and ok with r12.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104902 CR Approval 23.501 CR2789R5 (Rel-17, 'B'): Roaming support for NSAC Huawei, HiSilicon Rel-17 Revision of S2-2104388r12, merging S2-2103803, merging S2-2103803 and S2-2104778. Approved Agreed
8.4 S2-2104778 CR Approval 23.501 CR2789R4 (Rel-17, 'B'): Roaming support for NSAC Apple, [Huawei], [HiSilicon] Rel-17 Revision of (Agreed) S2-2103066. Merged into S2-2104902 George (Ericsson) provides a comment. This CR overlaps with 8303 and can be merged in there.
George (Ericsson) provides a comment. This overlaps with 8304 and can be merged there.
Jinguo(ZTE) suggest to merge with 4388
Krisztian (Apple) is OK to merge with 4388.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2103804 CR Approval 23.502 CR2669R2 (Rel-17, 'B'): Service operations of NSAC for Roaming UEs (Huawei, HiSilicon,ZTE, NEC), Ericsson Rel-17 Revision of (Agreed) S2-2103067. Merged into S2-2104903 Heng (China Telecom) provides a comment on deleting mapped S-NSSAI in hPLMN information.
Fenqin (Huawei) comments
Jinguo(ZTE) suggest to merge with 4389
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104389 CR Approval 23.502 CR2669R3 (Rel-17, 'B'): Service Operations of NSAC for Roaming UEs Huawei, HiSilicon, [ZTE?, NEC?, Ericsson?] Rel-17 Revision of (Agreed) S2-2103067. Confirm Sources! r10 agreed. Revised to S2-2104903, merging S2-2103804 and S2-2104779 George (Ericsson) proposes to note the CR Please 4388.
Fenqin (Huawei) responds
George (Ericsson) provides r01 which aligns this with 4388r04.
Fenqin (Huawei) responds and provides r02
George (Ericsson) provides r03. Minor editorial, and co-signed.
Krisztian (Apple) provides r04 that aligns with S2-2104388r05 and adds Apple support.
Ashok (Samsung) provides r05 with small change and co-signed and ask question to George (Ericsson)
George (Ericsson) provides a response. And/or works for me. We can do that
Iskren (NEC) confirms the NEC support and provides r06
Jinguo(ZTE) confirm the support and provide r07
Ashok (Samsung) provide r08
Kaisu (Nokia) provides r09
Fenqin (Huawei) provides r10
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104903 CR Approval 23.502 CR2669R5 (Rel-17, 'B'): Service Operations of NSAC for Roaming UEs Huawei, HiSilicon, [ZTE?, NEC?, Ericsson?] Rel-17 Revision of S2-2104389r10, merging S2-2103804, merging S2-2103804 and S2-2104779. Approved Agreed
8.4 S2-2104779 CR Approval 23.502 CR2669R4 (Rel-17, 'B'): Service operations of NSAC for Roaming UEs Apple, [Huawei], [HiSilicon], [ZTE], [NEC], [Ericsson] Rel-17 Revision of (Agreed) S2-2103067. Merged into S2-2104903 Jinguo(ZTE) suggest to merge with 4389, working in single thread.
Krisztian (Apple) is OK to merge with 4389.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104646 DISCUSSION Information Support for PDU Session Counting in EPS and for Roaming UEs. Nokia, Nokia Shanghai Bell Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2103806 CR Approval 23.502 CR2732 (Rel-17, 'F'): Correction of the 'Number of UEs per network slice availability check and update' procedure Ericsson, Apple, NEC Rel-17 Approved Jinhua (Xiaomi) provide comments to remove the EN.
George (Ericsson)provides a response. This CR is simply trying to describe the success case first followed by the failure case for better readability. It was not addressing any Editor's note. This is why the EN was left as is. It may actually not be needed at all.
==== 8.X, 9.X Revisions Deadline ====
Jinhua(Xiaomi) response to George (Ericsson), fine with 3806, r00 is proposed for approve.
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2104441 CR Approval 23.502 CR2819 (Rel-17, 'C'): Add a new trigger for NSAC procedure CATT Rel-17 Noted George (Ericsson) proposes to note the CR. Please see 4411.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2103805 CR Approval 23.502 CR2612R1 (Rel-17, 'B'): TS23.502 KI#1 Network Slice Admission Control Function (NSACF) - Result Update Ericsson, (NEC, Apple, Nokia, Nokia Shanghai Bell) Rel-17 Revision of (Noted) S2-2102209. Noted Ashok (Samsung) provides comments
Dan (China Mobile ) provides r01
==== 8.X, 9.X Revisions Deadline ====
TAO(VC) change the status to check as 'NOTED?' due to two proposal to NOTE
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2103827 CR Approval 23.502 CR2737 (Rel-17, 'B'): KI#1 Update to Solution & Removal of Editor-Note Samsung Rel-17 Noted George (Ericsson) proposes to note this CR. There is no justification for all of what is being proposed. Also we are not in agreement to use the SUBSCRIBE/NOTIFY procedure, let alone for what is being proposed in the CR. Please see proposal in 4648.
Jinhua (Xiaomi) provide comments for clarification
Ashok (Samsung) replies to George (Ericsson)
Ashok (Samsung) replies Jinhua (Xiaomi)
Jinguo(ZTE) comment that the baseline is incorrect and provide technique comments.
Dan (China Mobile) provide comment to this paper, but we support this method
Ashok (Samsung) replies to Jinguo(ZTE)
George (Ericsson) provides a response.
Ashok (Samsung) clarifies to George (Ericsson)
Fenqin (Huawei) ask a question for clarification
Iskren (NEC) provides comment.
George (Ericsson) provides comment. I think this is a reasonable compromise when there is no inter-PLMN mobility or inter-region mobility. The old-AMF and the new AMFs won't be able to know if they belong to different regions though.
Genadi (Lenovo) provides comment.
Jinguo (ZTE) replies to Ashok (Samsung)
Ashok (Samsung) replies to Jinguo (ZTE) replies
Ashok (Samsung) comments
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. This is already addressed in 4648.
Ashok (Samsung) is OK to Note the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104469 CR Approval 23.502 CR2823 (Rel-17, 'B'): Additional NSAC information from NSACF ZTE Rel-17 Confirm Specification Number - CR states 23.501! Merged into S2-2105156 George (Ericsson) provides a comment.
Iskren (NEC) provides a comment.
Jinguo (ZTE) replies to Iskren (NEC)
Ashok (Samsung) provides comments that the proposed solution may not work
Jinguo(ZTE) replies to Ashok (Samsung)
Ashok (Samsung) clarifies to Jinguo(ZTE)
Iskren (NEC) replies to Jinguo (ZTE)
Iskren (NEC) I repeat my previous e-mail so that I do not break the chain.
Jinguo(ZTE) replies to Ashok(Samsung) and Iskren (NEC) and suggest to merge this with 4648
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104648 CR Approval 23.502 CR2856 (Rel-17, 'B'): NSACF update in case of inter-AMF mobility with no UE context transfer Lenovo, Motorola Mobility Rel-17 CC#4: r08 + changes agreed. Revised to S2-2105156, merging S2-2104469. George (Ericsson) provides comment.
Jinguo (ZTE) answer
Genadi (Lenovo) provides comments to the scenarios introduced by George (Ericsson).
Iskren (NEC) provides comments
Genadi (Lenovo) provides comments to Iskren (NEC).
George (Ericsson) provides a response.
Ashok (Samsung) replies to George (Ericsson)
Iskren (NEC) comments
George Provides a comment. I would agree that passing the AMF-ID is sufficient to address all AMF mobility issues. The NSCAF has all the info to fully understand all the scenarios and the error cases, etc...
Ashok (Samsung) comments
Jinguo (ZTE) comments that keeping AMF ID in the NSACF is not enough.
Ashok (Samsung) replies to Jinguo (ZTE)
Jinguo(ZTE) provides comment to Genadi(Lenovo)
Iskren (NEC) answers Jingo ((ZTE)
Iskren (NEC)) provides comments
Jinguo(ZTE) asks question
George (Ericsson) asks a question Can U please explain fully the scenario U have in mind, using the 4 scenarios as a base line. I don't fully understand the case
George (Ericsson) provides additional comments.
George (Ericsson) asks a question. How can the NSCAF update the stored new AMF-ID for 3a?
George (Ericsson) provides a response. I am putting all the cases down with no consideration of what is or is not handled in existing TS. Existing text have not considered the AMF-ID is being stored. So this is new and what is being written have to be revisited to take that into account. Please see inline
Iskren (NEC) proposes a simplified solution.
Iskren (NEC) responds to George (Ericsson)
Genadi (Lenovo) comments on the proposal by Iskren (NEC).
Iskren (NEC) responds to Genadi (Lenovo).
Genadi (Lenovo) provides further comments.
George (Ericsson) provides a comment. I asked the question about where 3a/3b are covered as I indeed have the same view as Genadi stated below. But wanted to read what is written first in case I forgot with all these emails. This can be resolved with a configurable timer started for the old entry when the new entry is created. I think we can cover all cases without the AMF-ID.
Genadi (Lenovo) provides revision r01.
Fenqin (Huawei) provides comment.
Genadi (Lenovo) provides revision r02 where the case of mobility and NSACF change is supported. r02 keeps the concept of minimizing the signalling from AMFs to NSACF.
Genadi (Lenovo) provides revision r03 where the case of mobility and NSACF change is supported. r03 introduces the concept of sending updates from AMFs to NSACF during each AMF change.
George (Ericsson) provides r04., and a comment. R04 eliminate the need for CR 3469 approved at the last meeting
Genadi (Lenovo) comments that r04 changes r02 to become similar r03. Please comment on r02 or r03.
Ashok (Samsung) provides r05 on top of r02
George (Ericsson) provides r06 on top of r04. Just removed the first Editors note.
Iskren (NEC) provides comment on r05
Dan(China Mobile) object to r00,r01 r02, r05, we can accept r03, r04, r06. And we prefer r06.
Jinguo(ZTE) provides r07 based on r06
Genadi (Lenovo) provides r08 to add clarification to step 1.
==== 8.X, 9.X Revisions Deadline ====
Ashok (Samsung) feels the proposed solution without AMF-ID will not work in all scenario and hence object tor 07, r08
Jinguo(ZTE) replies to Ashok (Samsung)
Ashok (Samsung) provides comments
Ashok (George) does not agree with George (Ericsson) and continue its objection to r07, r08
Ashok (Samsung) replies to George (Ericsson) . Need the CR reference which mentions of storing the PDU session ID
Ashok (Samsung) explain the reason behind objection on r07 and r08
Jinguo(ZTE) ask why we have to agree AMF ID in this meeting
George (Ericsson). Ur example below has nothing to do with AMF-ID. It does not apply to PDU sessions. The SMF handles PDU sessions. Its apples and Oranges.
Jinguo(ZTE) propose to remove the timer so the issue doesn't exist. Ask to discuss this paper at CC#4.
Kaisu (Nokia ) supports Rev7 and Rev8
Ashok (Samsung) ask Jinguo (ZTE) whether r09 need to be created for CC#4 discussion?
Jinguo(ZTE) provides r09, the main change is to remove 'either autonomously after internally configured time expries or'
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2105156 CR Approval 23.502 CR2856R1 (Rel-17, 'B'): NSACF update in case of inter-AMF mobility with no UE context transfer Lenovo, Motorola Mobility Rel-17 Revision of S2-2104648r08 + changes, merging S2-2104469. CC#4: Approved Agreed
8.4 S2-2104148 CR Approval 23.502 CR2778 (Rel-17, 'B'): Clarification on NSAC in case of inter PLMN mobility Huawei, HiSilicon Rel-17 Noted George (Ericsson) proposes to note the CR.
Fenqin (Huawei) responds
Krisztian (Apple) comments.
Fenqin (Huawei) responds and provides r01
Srisakul (NTT DOCOMO) provides comment.
Srisakul (NTT DOCOMO) provides comment that solution in r01 is solving the same issue that S2-2104776 is trying to solve. We need to discuss which one to have in the spec.
Jinguo(ZTE) agree with Srisakul (NTT DOCOMO). There is overlapping. We should have one solution.
George (Ericsson) object to the CR, and provides a comment. How can the AMF know that the NSCAF wants to send something to it to send call back URI to it in the first place. This brings impacts to the AMF that are uncalled for.
Iskren (NEC) does not see the need from this CR.
==== 8.X, 9.X Revisions Deadline ====
Krisztian (Apple) thinks the solution is not complete, hence we should NOTE this CR.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104344 DISCUSSION Agreement NSAC and signalling restriction from AMF. Lenovo, Motorola Mobility, NTT DOCOMO Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104347 CR Approval 23.502 CR2803 (Rel-17, 'B'): Signalling restriction from AMF Lenovo, Motorola Mobility, NTT DOCOMO Rel-17 CC#4: Postponed George (Ericsson) proposes to note the CR. Please see additional comments.
Fenqin (Huawei) comments
George (Ericsson) responds.
Dan (China Mobile) provide some comment
George (Ericsson) would like to postpone this topic from Release 17. It is not an issue that we see urgent nor critical.
Genadi (Lenovo) provides responses comments.
George (Ericsson) Provides a response
Dan (China Mobile) Provides a response and suggestion
Genadi (Lenovo) provides r01.
George (Ericsson) provides a response. We ned to treat all analytics with a consistent approach. I don't think that NSCAF is the place for that
Srisakul (NTT DOCOMO) asks George whether removing the word 'internal analytics' would resolve the issue.
George (Ericsson) provides a response. Not really, we have an architecture where NWDAF collects information on behalf of consumers to take some action. So I think we need to consider this in our proposals.
Fenqin (Huawei) provide a comment
Kaisu (Nokia) provides a comment
==== 8.X, 9.X Revisions Deadline ====
George (Ericsson) proposes to note the CR. We don t see the need for this function at least at this stage.
Jinguo(ZTE) suggest to remove the Editor note and undo all other changes.
Genadi (Lenovo) is OK with the suggestion by the rapporteur Jinguo (ZTE). We need to open the paper during the CC#4 confirm a new revision which only removes the Editor note.
==== 8.X, 9.X Final Deadline ====
Postponed
8.4 S2-2104039 CR Approval 23.501 CR2680R2 (Rel-17, 'B'): TS23.501 KI#2 Network Slice Admission Control Function (NSACF) definition NEC, Apple, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics Rel-17 Revision of (Agreed) S2-2102856. r04 agreed. Revised to S2-2104904. Dan (China Mobile) Provides r01 with adding an EN
George (Ericsson) provides a response. There is no support for SCC mode. So this not going anywhere.
Hyunsook (LGE) provides a comment.
Srisakul (NTT DOCOMO) agrees with George (Ericsson) and Hyunsook (LGE). Let's not add SSC consideration into this CR, which was not the intention of the CR submitted to this meeting.
Dan(China Mobile) provide r02 with removing SSC mode2 and SSC mode 3 but keep the EN for ETSUN
George (Ericsson) objects to all revisions. We are hijacking the CR and others for the same issue.
Iskren (NEC) comments
Dan (China Mobile) think the EN is necessary and this EN is obviously for SMFs and NSACFs during ETSUN scenario, not related with other same issue.
Dan(China Mobile) would like Iskren to clarify his comments
George (Ericsson) provides a response. There is no intention nor need to do that. Any for SMF or AMF will have to only deal with the NSCAF located in their province. This is a corner stone for any mobility solution.
Dan (China Mobile) reply to George and mobility is not corner case. If we skip UE mobility, the value of NSACF is reduced.
George (Ericsson) provides a response. Only Anchor SMFs should communicate with NSCAF for NSAC enforcement. I-SMF and other types of SMFs will not communicate with the NSCAF. We need to add that to the CR. That takes care of the issue.
Iskren (NEC) responds to Dan (China Mobile)
Dan (China Mobile) accept this way forward, and let's focus on updating this part.
George (Ericsson) provides r03 to address issue below. Changes highlighted in yellow
Hyunsook (LGE) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Tao(VC) can we go with r04 or not?
Jinguo(ZTE) is fine to go with r04
Srisakul (NTT DOCOMO) is fine with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104904 CR Approval 23.501 CR2680R3 (Rel-17, 'B'): TS23.501 KI#2 Network Slice Admission Control Function (NSACF) definition NEC, Apple, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics Rel-17 Revision of S2-2104039r04. Approved Agreed
8.4 S2-2104082 CR Approval 23.502 CR2591R3 (Rel-17, 'B'): TS23.502 KI#2 Network Slice Admission Control Function (NSACF) services and procedures [NEC, Apple, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics], Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103472. Noted George (Ericsson) provides comments.
Hyunsook (LGE) provides a comment.
George (Ericsson) provides response.
Iskren (NEC) provides a comment.
Kaisu (Nokia) provides a comment.
Susan (Huawei) provides response to George.
Susan (Huawei) provides response to Hyunsook.
Susan (Huawei) provides response to Kaisu and Iskren.
Jinguo(ZTE) comment
Hoyeon (Samsung) provides comments.
Susan (Huawei) responds to Hoyeon and George.
Hyunsook (LGE) comments.
George (Ericsson) provides comment. Rev 01 still has the SSC mode. The UE ID and SMF Id are needed to handle changes of SMF, and ensuring accurate count.
Susan (Huawei) responds to George and Hyunsook.
Hoyeon (Samsung) replies to Susan (Huawei).
Hoyeon (Samsung) provides r02.
Susan (Huawei) objects to r02.
Srisakul (NTT DOCOMO) provides comment.
Susan (Huawei) replies to Hoyeon.
Susan (Huawei) replies to Srisakul (NTT DOCOMO).
George (Ericsson) provides a comment. It is clear for Release 17 there is no support for SCC mode. We can consider for Release 18. R02 is a good base for moving forward.
Susan (Huawei) keep objection to r02.
==== 8.X, 9.X Revisions Deadline ====
Hoyeon (Samsung) proposes to note the CR as there is no agreeable version.
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104422 CR Approval 23.502 CR2591R5 (Rel-17, 'B'): TS23.502 KI#2 Network Slice Admission Control Function (NSACF) services and procedures CATT Rel-17 Revision of (Agreed) S2-2103472. Noted George (Ericsson) proposes to note the CR. Please see comments on 4411
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104574 CR Approval 23.502 CR2676R2 (Rel-17, 'B'): PDU Session establishment and modification admission control based on network Slice maximum data rate [CATT, Xiaomi,] Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103481. CC#5: Revised to clean up editorially to S2-2105203
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2105203 CR Approval 23.502 CR2676R3 (Rel-17, 'B'): PDU Session establishment and modification admission control based on network Slice maximum data rate [CATT, Xiaomi,] Huawei, HiSilicon Rel-17 Revision of S2-2104574. Approved Agreed
8.4 S2-2103822 CR Approval 23.503 CR0574 (Rel-17, 'B'): Retrieval of Subscribed UE-Slice-MBR to the PCF Ericsson Rel-17 r05 agreed. Revised to S2-2104905. Haiyang (Huawei) provides r01.
Belen (Ericsson) is okay with r01
Heng (China Telecom) comment
Haiyang (Huawei) clarifies.
Belen (Ericsson) replies
Haiyang (Huawei) provides r02.
Heng (China Telecom) provide r03.
Belen (Ericsson) provides r04.
Heng (China Telecom) is ok with r04.
Haiyang (Huawei) is ok with r04.
Jinhua(Xiaomi) provides r05, and cosign to support both data set stored.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104905 CR Approval 23.503 CR0574R1 (Rel-17, 'B'): Retrieval of Subscribed UE-Slice-MBR to the PCF Ericsson Rel-17 Revision of S2-2103822r05. Approved Agreed
8.4 S2-2104131 CR Approval 23.503 CR0544R2 (Rel-17, 'B'): KI#3 - Slice Maximum Bit Rate (Slice-MBR) Ericsson, [Xiaomi, Nokia, Nokia Shanghai Bell, Samsung], Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103473. r04 agreed. Revised to S2-2104906, merging S2-2104452 Jinhua (Xiaomi) provide comments
Belen (Ericsson) provides comments
Haiyang(Huawei) provide r01
Jinhua(Xiaomi) reply to Haiyang(Huawei) , fine with r01
Jinhua(Xiaomi) reply to Haiyang(Huawei) , and provide r02.
Jinhua(Xiaomi) reply to Haiyang(Huawei) , fine with r02 and maybe we can mergeS2-2104452 ZTE paper into it?
Haiyang(Huawei) is ok to merge S2-2104452 into this paper and provides r03
Jinhua(Xiaomi) response to Haiyang(Huawei) , r04 is provided
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104906 CR Approval 23.503 CR0544R4 (Rel-17, 'B'): KI#3 - Slice Maximum Bit Rate (Slice-MBR) Ericsson, [Xiaomi, Nokia, Nokia Shanghai Bell, Samsung], Huawei, HiSilicon Rel-17 Revision of S2-2104131r04, merging S2-2104452. Approved Agreed
8.4 S2-2104452 CR Approval 23.503 CR0544R3 (Rel-17, 'B'): KI#3 - Slice Maximum Bit Rate (Slice-MBR) Ericsson?, Xiaomi?, Nokia?, Nokia Shanghai Bell?, Samsung?,ZTE Rel-17 Revision of (Agreed) S2-2103473. Confirm Sources! Merged into S2-2104906 Haiyang (Huawei) asks questions on how to handle the same CR.
alessio (Nokia) comments that we are ok also with this an wish we merge in one thread today at the latest ??
Haiyang (Huawei) indicates 4131r03 has captured the update of this paper thus suggest to merge this paper into 4131.
Jinhua(Xiaomi) response to Jinguo(ZTE) and Haiyang(Huawei) , 4131r04 is provided with 4452 merged in
Jinguo(ZTE) is ok with the merge in 4131
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104132 CR Approval 23.501 CR2706R2 (Rel-17, 'B'): Support for UE-Slice-MBR Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell, ZTE, Apple, Samsung] Rel-17 Revision of (Agreed) S2-2103474. r02 agreed. Revised to S2-2104907. Alessio(Nokia) supports this paper and provides r01
Jinguo(ZTE) is fine with the change and ask the author to add ZTE support.
Hoyeon (Samsung) confirms our support.
Haiyang (Huawei) provides r02.
Krisztian (Apple) confirms our support for 4132r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104907 CR Approval 23.501 CR2706R3 (Rel-17, 'B'): Support for UE-Slice-MBR Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell, ZTE, Apple, Samsung] Rel-17 Revision of S2-2104132r02. Approved Agreed
8.4 S2-2104133 CR Approval 23.502 CR2614R2 (Rel-17, 'B'): Support for UE-Slice-MBR Huawei, HiSilicon, [Xiaomi, Nokia, Nokia shanghai Bell, Samsung] Rel-17 Revision of (Agreed) S2-2103475. r05 agreed. Revised to S2-2104908. Jinhua (Xiaomi) provide comments
Paul (Ericsson) provides r01.
Haiyang(Huawei) provides r02.
Paul (Ericsson) provides r03.
Alessio(Nokia) ok with r03.
Hoyeon (Samsung) asks a question for clarification.
Haiyang(Huawei) provides r04.
Haiyang(Huawei) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Jinhua(Xiaomi) response to Haiyang(Huawei) , fine with r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104908 CR Approval 23.502 CR2614R3 (Rel-17, 'B'): Support for UE-Slice-MBR Huawei, HiSilicon, [Xiaomi, Nokia, Nokia shanghai Bell, Samsung] Rel-17 Revision of S2-2104133r05. Approved Agreed
8.4 S2-2104134 CR Approval 23.502 CR2683R2 (Rel-17, 'B'): ENS_502_KI#3_Update of Registration Procedures Xiaomi, Samsung, Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103476. r03 agreed. Revised to S2-2104909. Jinhua (Xiaomi) provide comments and r01.
Alessio(Nokia) provides r02
Belen (Ericsson) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104909 CR Approval 23.502 CR2683R3 (Rel-17, 'B'): ENS_502_KI#3_Update of Registration Procedures Xiaomi, Samsung, Huawei, HiSilicon Rel-17 Revision of S2-2104134r03. Approved Agreed
8.4 S2-2104449 CR Approval 23.501 CR2822R3 (Rel-17, 'B'): Introduction of support of GSMA NG.116 attributes 'Maximum DL/UL throughput per slice/UE' Nokia?, Nokia Shanghai Bell?, ZTE, Spirent?, Huawei?, Apple?, Samsung? Rel-17 Revision of (Agreed) S2-2103477. Confirm Sources! Merged into S2-2104910 Haiyang (Huawei) suggests to merge this paper into S2-2104135.
Jinguo (ZTE) is fine with the merge in 4135.
Alessio(Nokia) is it possible to merge this into S2-2104135? also this is intoducing a detail that should be already in the storage info table?
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104135 CR Approval 23.501 CR2822R2 (Rel-17, 'B'): Introduction of support of GSMA NG.116 attributes 'Maximum DL/UL throughput per slice/UE' [Nokia, Nokia Shanghai Bell, ZTE, Spirent], Huawei, HiSilicon, [Apple, Samsung] Rel-17 Revision of (Agreed) S2-2103477. r05 agreed. Revised to S2-2104910, merging S2-2104449 Jinhua (Xiaomi) provide comments and r01.
Alessio(Nokia) provides r02
Jinguo(ZTE) provides r03 to include the change in 4449
Belen (Ericsson) provides r03.
Belen (Ericsson) provides r04
Alessio(nokia) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104910 CR Approval 23.501 CR2822R4 (Rel-17, 'B'): Introduction of support of GSMA NG.116 attributes 'Maximum DL/UL throughput per slice/UE' [Nokia, Nokia Shanghai Bell, ZTE, Spirent], Huawei, HiSilicon, [Apple, Samsung] Rel-17 Revision of S2-2104135r05, merging S2-2104449. Approved Agreed
8.4 S2-2104626 CR Approval 23.502 CR2850 (Rel-17, 'B'): TS23.502 KI#4 NSACF status notification on request NEC Rel-17 Approved George (Ericsson) provides a comment.
Iskren (NEC) answers George (Ericsson).
George (Ericsson) provides a comment. My question was if there is a need to issue a separate request per S-NSSAI, or there is ability to have a single request for a group of slices or all slices.
Iskren (NEC) answers question from George (Ericsson)
==== 8.X, 9.X Revisions Deadline ====
Fenqin (Huawei) ask question for clarification
Iskren (NEC) answers Fenqin (Huawei)
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2104040 CR Approval 23.501 CR2838R2 (Rel-17, 'B'): TS23.501 KI#4 NSACF event notification definition NEC, Apple, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung Rel-17 Revision of (Agreed) S2-2103478. Approved Jinhua (Xiaomi) provide comments
Hyunsook (LGE) provides a comment.
==== 8.X, 9.X Revisions Deadline ====
Hyunsook (LGE) thinks we can approve r00.
Jinhua(Xiaomi) response to Hyunsook (LGE), fine with r00.
==== 8.X, 9.X Final Deadline ====
Agreed
8.4 S2-2104318 CR Approval 23.288 CR0354 (Rel-17, 'B'): KI#5 - Total bandwidth per S-NSSAI and SliceMBR Update with Analytics Ericsson?, KPN?, Nokia?, Nokia Shanghai Bell?, Xiaomi Rel-17 Confirm Sources!. Confirm Specification Number - CR states 23.503! Should be 23.503 CR0593. Merged into S2-2104573 (Noted) Alessio(Nokia) requests to postpone this CR as there are ongoing discussion on this in ENA.
Jinhua(Xiaomi) response to Alessio(Nokia), r01 is provided with reusing.
Belen (Ericsson) provides r02.
Jinhua(Xiaomi) response to Belen (Ericsson) , with achieved link of r02.
Mirko (Huawei) proposes to note this CR.
Jinhua(Xiaomi) response to Mirko (Huawei) , comments cannot be accepted, please see the detail clarification.
Mirko (Huawei) proposes to merge this CR into S2-2104573.
Jinhua(Xiaomi) response to Mirko (Huawei), agree to merge 4318r02 into 4573.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104319 CR Approval 23.502 CR2800 (Rel-17, 'B'): ENS_502_KI#5_Update of PDU Session Procedures Xiaomi Rel-17 Noted Susan (Huawei) provides comments.
Jinhua(Xiaomi) response to Susan (Huawei), procedures update is necessary.
Susan (Huawei) replies to Jinhua.
Jinhua(Xiaomi) replies to Susan (Huawei).
Belen (Ericsson) is okay not to change the procedures.
Jinhua(Xiaomi) response to Belen (Ericsson) and Susan(Huawei), noted is fine, update in 23.503 instead if needed.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104320 CR Approval 23.503 CR0592 (Rel-17, 'B'): ENS_ 503_ KI#5_ Update of Network Analytics Xiaomi Rel-17 r04 agreed. Revised to S2-2104911. Susan (Huawei) provides r01.
Jinhua(Xiaomi) response to Susan (Huawei) r01 is OK for us, and ask to approve.
Belen (Ericsson) asks questions.
alessio(nokia) requests to postpone this CR.
Jinhua(Xiaomi) response to Alessio(Nokia) ,
Hoyeon (Samsung) shares the view as Nokia and proposes to postpone it. We can comeback once the discussion/agreement in eNA is stable.
Belen (Ericsson) propose not to postpone yet, but check S2-2104084 in eNA, and possibilily 'conditionally agree' this CR linked to S2-2104084 approval including bandwitdh per slice.
Jinhua(Xiaomi) response to Hoyeon (Samsung).
Jinhua(Xiaomi) response to Belen (Ericsson), with r02 provided.
Alessio(Nokia) provides r03
Jinhua(Xiaomi) response to Alessio(Nokia), fine with r03.
Mirko (Huawei) provides r04.
Jinhua(Xiaomi) response to Mirko (Huawei), fine with r04.
==== 8.X, 9.X Revisions Deadline ====
Hoyeon (Samsung) is OK with r04.
Jinhua(Xiaomi) response to Hoyeon (Samsung), propose 4320r04 for approve
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104911 CR Approval 23.503 CR0592R1 (Rel-17, 'B'): ENS_ 503_ KI#5_ Update of Network Analytics Xiaomi Rel-17 Revision of S2-2104320r04. Approved Agreed
8.4 S2-2104659 CR Approval 23.503 CR0552R2 (Rel-17, 'B'): Policy control of data rate per network slice Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell] Rel-17 Revision of (Agreed) S2-2103068. r06 agreed. Revised to S2-2104912. Belen (Ericsson) asks questions and comments that overlaps with CR 543r1 (approved)
Susan (Huawei) replies to Belen and provides r01.
Alessio(Nokia) proposes to note this paper
Susan (Huawei) responds to Alessio.
Alessio(nokia) responds to Susan (Huawei): need to explain the case of multiple PCFs and also the frequency of info required.
Belen (Ericsson) provides r02
Alessio(Nokia) provides r03
Alessio(Nokia) cannot live with other versions that r03 because they are not specific for what we expect from eNA and too open ended.
Susan (Huawei) replies to Belen and Alessio, is ok with r02 but can live with r03 for this meeting.
Alessio(Nokia) suggests to proceed with r03 for this meeting, we need to come back to provide the necessary details at the next meeting (I do not think this will need an exception as these are mostly corrections)
Belen (Ericsson) provides r04.
Jinhua(Xiaomi) provides r05, align with the definition update.
Peretz (Spirent) provides r06.
Jinhua(Xiaomi) response to Peretz (Spirent) , fine with r06.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) is fine with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104912 CR Approval 23.503 CR0552R3 (Rel-17, 'B'): Policy control of data rate per network slice Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell] Rel-17 Revision of S2-2104659r06. Approved Agreed
8.4 S2-2104573 CR Approval 23.503 CR0543R2 (Rel-17, 'B'): KI#5 - Total bandwidth per S-NSSAI [Ericsson, KPN, Nokia, Nokia Shanghai Bell, Xiaomi,] Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103480. CC#5: Revised to clean up editorially to S2-2105202. Alessio(Nokia) provides r01
Mirko (Huawei) provides r02
Jinhua(Xiaomi) response to Mirko (Huawei) with merge 4318 into, and r03 is provided.
Mirko (Huawei) comments.
Jinhua(Xiaomi) response to Mirko (Huawei) for clarification.
Mirko (Huawei) responds.
Jinhua(Xiaomi) response to Mirko (Huawei), r03 is prefer, but can live with r02.
==== 8.X, 9.X Revisions Deadline ====
Mirko (Huawei) is only ok with r02 and objects to r03.
Jinhua(Xiaomi) response to Mirko (Huawei) , live with r02, as clarified.
Alessio(Nokia) believes that the remaining data rate must be managed per PCF as otherwise different PCFs may update the value inconsistently... for this meeting let's go with r01 then we come back at next meeting if we see some issue.
alessio (nokia) can not accdept r02 and r03
TAO(VC) let's check r01 agreeable or not
Mirko (Huawei) responds and suggests to move forward with either r00 or r02.
Alessio(nokia) repeats the problem description: PCF A gest remaining rate 100, PCF B also gets remainignrate 100. PCF A updates with remaining rate 90 and PCF B updated later with remaining rate 95 but in reality it should be 85 if PCF b know of the remaining rate was updated to 190 by PCF A.
Alessio(nokia) repeats the problem description (fixing typos): PCF A gest remaining rate 100, PCF B also gets remaining rate 100. PCF A updates with remaining rate 90 and PCF B updated later with remaining rate 95 but in reality it should be 85 if PCF B knew of the remaining rate was updated to 90 by PCF A.
Belen (Ericsson) cannot accept r01, r00 or r02 okay.
Belen (Ericsson) clarifies that both r00, r02 are okay. R01 is not okay for us.
Alessio(Nokia) comments that the UDM can manage the remaining rate per PCF (allocate a slice of rate per PCF)
Mirko (Huawei) responds to Alessio and questions that the UDR could do this.
Alessio(Nokia) comments that the fragmentation over various PCFs (they should be not many really) may just follow the logic that anyhow justifies the existence of multiple PCFs and needs not an algorithm in UDM: just provisioning of the respective values.. this is static information... the other option is we just use on PCF for this feature if we do not like fragmentation.
TAO(VC) can we live with r02, since r00 and r02 got more support.
Alessio(Nokia) comments that r01 works and in a particular case allows what r02 wants by sharing a single value in UDM and configuring to use the feature as per r02...
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2105202 CR Approval 23.503 CR0543R3 (Rel-17, 'B'): KI#5 - Total bandwidth per S-NSSAI [Ericsson, KPN, Nokia, Nokia Shanghai Bell, Xiaomi,] Huawei, HiSilicon Rel-17 Revision of S2-2104573. Approved Agreed
8.4 S2-2104639 DISCUSSION Endorsement KI#6: Regarding the handling of UEs not supporting Simultaneous Network Slice Registration Groups. Huawei, HiSilicon Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104641 CR Approval 23.502 CR2855 (Rel-17, 'B'): Introduction of subscription-based restriction to simultaneous use of network slices Huawei, HiSilicon Rel-17 CC#4: Status changed from approved to merged into S2-2105157 Alessio(Nokia) asks to correct the notes as we did not discuss this at all during the meeting as after at CC#1 we focused on the CR related to multi-company papers only. this should be marked as merged into 4640
Patrice (Huawei) comments that this CR did get approved according to the meeting rules, one of 3 proposals on a topic involving at least 16 companies, including major senior delegates, receiving no concern after 9 working days of discussion time. Huawei really much wants a CR approved on this topic after 3 years of discussion. We are not willing yet to merge to a document that might not get approved. As this CR is linked to S2-2104644, its status should be the same.
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104644 CR Approval 23.501 CR2964 (Rel-17, 'B'): Introduction of subscription-based restriction to simultaneous use of network slices Huawei, HiSilicon Rel-17 CC#4: Status changed from approved to merged into S2-2104913 Alessio(Nokia) asks to correct the notes as we did not discuss this at all during the meeting as after at CC#1 we focused on the CR related to multi-company papers only. this should be marked as merged into 4642
Patrice (Huawei) comments that this CR did get approved according to the meeting rules, one of 3 proposals on a topic involving at least 16 companies, including major senior delegates, receiving no concern after 9 working days of discussion time. Huawei really much wants a CR approved on this topic after 3 years of discussion. We are not willing yet to merge to a document that might not get approved. Let's approve S2-2104640r15 first before considering changing the status of this document.
Alessio(Nokia) requests this to be merged as Nokia has already agreed to r15 generated by Huawei and Huawei is happy with r15.
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104654 DISCUSSION Information KI#6: example of SRG information. Nokia, Nokia Shanghai Bell Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104655 DISCUSSION Agreement KI#6 discussion and way forward. Nokia, Nokia Shanghai bell, Convida wireless, Telecom Italia Rel-17 Noted Patrice (Huawei) comments that the assumptions of this contribution are without merit and naïve, and should be dismissed in the further discussion as irrealistic. The discussion paper should be noted without further consideration.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2103807 CR Approval 23.501 CR2813R2 (Rel-17, 'B'): Introduction of support of NG.116 attribute 'Simultaneous Use of a Network Slice' Ericsson, (Nokia, Nokia Shanghai Bell, Telecom Italia, Convida Wireless, T-Mobile, Apple, Verizon UK ltd., NEC) Rel-17 Revision of (Endorsed) S2-2103069. Merged into S2-2104913 Alessio(Nokia) proposes this is noted/merged in 4640
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104640 CR Approval 23.501 CR2813R3 (Rel-17, 'B'): Introduction of support of NG.116 attribute 'Simultaneous Use of a Network Slice' Nokia, Nokia Shanghai Bell, Telecom Italia, Convida Wireless, T-Mobile, Apple, Verizon UK ltd., NEC, Samsung, Broadcom, InterDigital Inc., ZTE, Xiaomi, Qualcomm Inc., China Telecom Rel-17 Revision of (Endorsed) S2-2103069. r15 agreed. Revised to S2-2104913, merging S2-2103807 and S2-2104644 Alessio(Nokia) provides a revision r01
George (Ericsson) provides a revision r02
==== 8.X, 9.X Revisions Deadline ====
TAO(VC) it seem r15 ok to people. Can we Approve r15 then
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104913 CR Approval 23.501 CR2813R4 (Rel-17, 'B'): Introduction of support of NG.116 attribute 'Simultaneous Use of a Network Slice' Nokia, Nokia Shanghai Bell, Telecom Italia, Convida Wireless, T-Mobile, Apple, Verizon UK ltd., NEC, Samsung, Broadcom, InterDigital Inc., ZTE, Xiaomi, Qualcomm Inc., China Telecom Rel-17 Revision of S2-2104640r15, merging S2-2103807 and S2-2104644. Approved Agreed
8.4 S2-2104642 CR Approval 23.502 CR2706R1 (Rel-17, 'B'): Introduction of support of NG.116 attribute 'Simultaneous Use of a Network Slice' Nokia, Nokia Shanghai Bell, Telecom Italia, Convida Wireless, T-Mobile, Apple, Verizon UK ltd, NEC, Samsung, Broadcom, InterDigital Inc, ZTE, Xiaomi, Qualcomm Inc., China Telecom Rel-17 Revision of (Postponed) S2-2102800. CC#4: r01 + changes agreed. Revised to S2-2105157, merging S2-2104641. Patrice (Huawei) comments that S2-2104642 is not aligned with the status of S2-2104640, for which discussion is still very much not resolved, and should be noted for this meeting.
alessio (Nokia) provides r01 aligned with 4640 latest versions
==== 8.X, 9.X Revisions Deadline ====
Patrice (Huawei) comments that this CR needs more work. It is not fully in line with S2-2104640r15. r01 in its current form cannot be approved. At least, in the change in step 1 (just above step 2) of 4.2.2.2.2, the 'shall' shall be changed to a 'may' before this can be approved (to be checked at CC#4). The other changes are less important and could wait for a clean-up CR next meeting. Even with the change, its approval should be conditional to the approval of S2-2104640r15.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2105157 CR Approval 23.502 CR2706R2 (Rel-17, 'B'): Introduction of support of NG.116 attribute 'Simultaneous Use of a Network Slice' Nokia, Nokia Shanghai Bell, Telecom Italia, Convida Wireless, T-Mobile, Apple, Verizon UK ltd, NEC, Samsung, Broadcom, InterDigital Inc, ZTE, Xiaomi, Qualcomm Inc., China Telecom Rel-17 Revision of S2-2104642r01 + changes, merging S2-2104641. CC#4: Approved Agreed
8.4 S2-2104649 CR Approval 23.502 CR2857 (Rel-17, 'B'): Support of 5GC assisted cell reselection and redirection to access a network slice Nokia, Nokia Shanghai Bell, Convida Wireless, Verizon UK ltd. Rel-17 Merged into S2-2104915 Peter Hedman (Ericsson) proposes to note the CR as merged into S2-2104341
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104652 CR Approval 23.501 CR2966 (Rel-17, 'B'): Support of 5GC assisted cell reselection and redirection to access network slice Nokia, Nokia shanghai Bell, Convida Wireless, Verizon UK ltd. Rel-17 Merged into S2-2104914 Peter Hedman (Ericsson) proposes to note the CR as merged into S2-2104340
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.4 S2-2104653 DISCUSSION Agreement KI#7 discussion and way forward proposal. Nokia, Nokia Shanghai bell, Convida Wireless, Verizon UK ltd. Rel-17 Noted Peter Hedman (Ericsson) provides comments and propose to note the DP and continue the discussions as part of the CRs
alessio(Nokia) ok to note (which is the destiny of all DPs ?? )
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.4 S2-2104340 CR Approval 23.501 CR2719R1 (Rel-17, 'B'): Support of 5GC assisted cell selection to access network slice Ericsson, NEC, Qualcomm, Samsung, ZTE, Lenovo, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of (Noted) S2-2102276. r13 agreed. Revised to S2-2104914, merging S2-2104652 Peter Hedman (Ericsson) provides r01
Alessio (nokia) provides r02 with the changes we propose based on details provided in email sent to the meeting list.
Peter Hedman (Ericsson) provides reply to Nokia and r02 cannot be accepted i.e. more discussions are needed
Alessio (nokia) can live with R02 with the changes we propose but not previous versions. encourages further discussion to converge on something acceptable.
Peter Hedman (Ericsson) provides r03 and r02 is not acceptable
Alessio(Nokia) r03 is not acceptable, provides r04
Peter Hedman (Ericsson) provides r05 and objects to r04
Alessio(Nokia) objects to r05 and provides r06
Mike (Convida Wireless) comments and expresses support for including the Configured NSSAI
Peter Hedman (Ericsson) objects to r06 and provides r07
Hoyeon (Samsung) provides comments
Hoyeon (Samsung) supports r07 and suggestion from Peter.
alessio (Nokia) objects to r07 can only live with r06
alessio (Nokia) provides r08 further improving r06 and also including the expected Target NSSAI
Jinguo(ZTE) comments on r06/r08
Peter Hedman (Ericsson) provides comment and suggest that Configured NSSAI relevance to be discussed at CC.
alessio(Nokia) would not accept discussing a component of the solution in isolation that was part of conclusion of TR, unless a concrete discussion paper or slide set with the identified issue is provided to dismiss the benefit and highlight the issue with the text in the CR.
Susan (Huawei) objects to r02, r04, r06 and r08.
Alessio(Nokia) provides reply to Ericsson reply
Alessio(Nokia) can only accept r08, as previous version have incorrect text in the last clause in addition to not providing the Configured NSSAI to rAN.
Peter Hedman (Ericsson) provides r09 based on outcome of CC#3
Alessio(Nokia) provides some improved text in some places, and inclusion of a EN on the topic pending RAN feedback.
Peter Hedman (Ericsson) provides r11
Alessio (Nokia) does not agree on rewording of EN as it changes the meaning of it . Also the RAN has visibility on the allowed NSSAI so it can determine these S-NSSAIs in the Target NSSAI that therefore the RAN should attempt to prioritize these S-NSSAIs over the rejected S-NSSAI (so not sure about the comment by Ericsson on what does it mean as some N3 bearers may not be established for some PDU sessions of the S-NSSAIs in allowed NSSAI so the text change they introduced (ericsson) requires now this extra text). Nokia provides r12 that also completes the missing text (sorry not sure what happened)
Peter Hedman (Ericsson) provides r13
Alessio(Nokia) can live with r13
==== 8.X, 9.X Revisions Deadline ====
Alessio(Nokia) clarifies that can live with r13 but we assumed this part of the bargain was held also 'In fact, you have the LS out open in which you anyway are covering that specific aspect while there may be more or other info RAN wants i.e. EN is kept generic.' asks this to be discussed in CC#4 if there is no agreement on a CR + sensible Ls package before then.
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104914 CR Approval 23.501 CR2719R2 (Rel-17, 'B'): Support of 5GC assisted cell selection to access network slice Ericsson, NEC, Qualcomm, Samsung, ZTE, Lenovo, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of S2-2104340r13, merging S2-2104652. Approved Agreed
8.4 S2-2104341 CR Approval 23.502 CR2626R1 (Rel-17, 'B'): Support of 5GC assisted cell selection to access network slice Ericsson, Samsung, NEC, Qualcomm, ZTE, Lenovo, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of (Postponed) S2-2102277. r01 agreed. Revised to S2-2104915, merging S2-2104649 Peter Hedman (Ericsson) provides r01, changes referenced clause
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.4 S2-2104915 CR Approval 23.502 CR2626R2 (Rel-17, 'B'): Support of 5GC assisted cell selection to access network slice Ericsson, Samsung, NEC, Qualcomm, ZTE, Lenovo, Motorola Mobility, Huawei, HiSilicon Rel-17 Revision of S2-2104341r01, merging S2-2104649. Approved Agreed
8.4 S2-2105008 LS OUT Approval LS on Cell reselection with band-specific network slices SA WG2 - Created at CC#3. CC#4: r01 agreed. Revised to S2-2105158. Alessio(Nokia) provides the first S2-2105008
Peter Hedman (Ericsson) as stated during CC#3 we doubt any LS out is needed as Nokia can make proposals in RAN WGs directly; propose an r01 meanwhile even if we have not decided whether to agree on sending the LS or not.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) also doubted if any LS is needed to RAN, and RAN should work on themselves without the LS from SA2. But still provides r02 in case the LS is really needed.
Alessio(Nokia) assumes that sending a sensible LS is part of the Agreement package... of course r02 is not acceptable (aside form being a revision past deadline)
Alessio(nokia) can live with r01 but considers sending a sensible LS part of the package. asks this to be discussed n CC#4.
Susan (Huawei) objects to r00 and r01 of the LS.
Alessio(Nokia) comments ' I also agree there is no agreement to agree on anything a priori but this is why we meet to agree on something not to disagree on everything. the CR +LS package is a sensible compromise.'
Mike (Convida Wireless) supports sending r00 or r01.
Verizon supports sending r00 or r01.
Jinguo(ZTE) propose to go with r01 and suggest to discuss at CC#4.
Antoine (Orange) Supports r00 and r01 and argues that sending this LS is needed since 4340r13 is up for approval and contains a related EN creating a dependency to RAN feedback.
Susan (Huawei) provides r03.
Tao(VC) Unless we get positive feedback from Susan on r01, Otherwise, we need to discuss at CC#4
Alessio(Nokia) comments r03 is not good enough as companies against the Nokia et. al. text were saying this was causing RAN issues, so that text needs to be seen by rAN sot hey can confirm this causes issues that outweigh the benefits. we still want to send r00 or r01
Susan (Huawei) replies to Alessio.
Alessio(Nokia) does not understand why we should not disclose to RAN the text that Huawei thinks had RAN issues
==== 8.X, 9.X Final Deadline ====
Peter Hedman (Ericsson) provides comments, prefers r03 but ok with r01
Nokia can only live with r01 as it will avoid some needless discussions in RAN WGs on what was the actual issue discussed in SA2 in detail. company papers do not carry the same weight as a LS to describe an issue.
Susan (Huawei) prefers r03 but can live with r01, to move forward.
Revised
8.4 S2-2105158 LS OUT Approval LS on Cell reselection with band-specific network slices SA WG2 - Revision of S2-2105008r01. CC#4: Approved Approved
8.4 S2-2105095 LS In Action LS from SA WG1: LS Response on hold and forward buffer support for VIAPA services SA WG1 (S1-211324) Rel-17 Postponed Postponed
8.5 - - - Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) - - Docs:=66 -
8.5 S2-2103738 LS In Action LS from SA WG4: Reply LS to SA2 on hold and forward buffer support for VIAPA services SA WG4 (S4-210619) Postponed Postponed
8.5 S2-2104786 LS In Information LS from SMPTE: Response To 3GPP enquiry re. SMPTE PTP profile SMPTE (3gpp02-smpte-to-3gpp-1588-update) Response to Q3 of S2-2103021. Noted Shabnam (Ericsson) proposes to NOTE the LS response, since only Q3 was responded to, we can assume SA2 approach with explanation is sufficient from SMPTE org perspective. Noted
8.5 S2-2104791 LS In Information LS from SMPTE 32NF Technology Committee: PTP device monitoring Public Committee Draft SMPTE 32NF Technology Committee (SLC04-smpte-to-3GPP-PCD-RP2059-15-2021-04-2) Postponed Postponed
8.5 S2-2103916 CR Approval 23.503 CR0563R2 (Rel-17, 'F'): TSC Assistance Container Determination by the PCF in the trusted domain Tencent, CATT, Ericsson Rel-17 Revision of (Agreed) S2-2103056. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2103917 CR Approval 23.501 CR2769R2 (Rel-17, 'B'): Correction for Survival Time Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103053. Confirm CR Revision - CR states 0! Approved Chunshan (Tencent) provides r01.
Shabnam (Ericsson) disagrees with r01 and provides comments.
Sang-Jun (Samsung) agrees with Shabnam (Ericsson).
Devaki (Nokia) also believes r01 is not correct.
Chunshan (Tencent) responses.
Shabnam (Ericsson) provides response in line and proposes to accept the original CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2103963 CR Approval 23.501 CR2872 (Rel-17, 'C'): TSC assistance container constructed by AF Ericsson Rel-17 Merged into S2-2105082 Qianghua (Huawei) proposes to note this CR or merge with S2-2104721
Devaki (Nokia) objects to the CR as it removes the need for NEF API completely.
Jari (NTT DOCOMO) responds to Devaki
Huazhang (vivo) response to Jari, Devaki
György (Ericsson) comments that Nokia probably misunderstood the proposal.
zhendong (ZTE) provides the comments.
György (Ericsson) comments.
Sang-Jun (Samsung) ask György (Ericsson) for clarificaions.
György (Ericsson) responds to Samsung.
Jari (NTT DOCOMO) comments
Jari (NTT DOCOMO) responds to zhendong
Qianghua (Huawei) replies
Devaki (Nokia) comments.
Jari (NTT DOCOMO) proposes to continue discussing the proposal for 'new NF' under S2-2103981.
zhendong (ZTE) provides the response.
Sebastian (Qualcomm) comments
Devaki (Nokia) proposes to note or consider this merged with 3981 revision.
György (Ericsson) agrees to consider this merged into 3981 if we can get agreement in that discussion.
zhendong (ZTE) also agree to merge this to 3981.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2103964 CR Approval 23.502 CR2753 (Rel-17, 'C'): TSC assistance container constructed by AF Ericsson Rel-17 Noted Jari (NTT DOCOMO) provides r01
Chunshan (Tencent) propose this paper to be merged into paper S2-2104062.
Qianghua (Huawei) proposes to note this CR
György (Ericsson) provides r02 and responds to Jari
György (Ericsson) responds to Tencent
György (Ericsson) responds to Huawei.
zhendong (ZTE) provides the comments.
Devaki (Nokia) objects to the CR for the same reason as S2-2103963, NEF API cannot be removed completely.
György (Ericsson) responds to Nokia.
György (Ericsson) comments to ZTE.
zhendong (ZTE) dont agree with György comments.
György (Ericsson) responds to ZTE.
zhendong (ZTE) respond to György.
György (Ericsson) respond to ZTE.
Devaki (Nokia) proposes to note or consider this merged with 3981 revision.
György (Ericsson) agrees to consider this merged into 3981 if that document is agreeable.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) corrects earlier proposal. Formally, 3981 is a document for 501 however this is a 502 CR thus it cannot be considered merged directly. it could be stated that the problem is resolved by 3981.
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2103965 CR Approval 23.501 CR2873 (Rel-17, 'C'): TSC handling of containers Ericsson Rel-17 Noted Jari (NTT DOCOMO) objects
Devaki (Nokia) objects to the CR as there is no need to split and/or differentiate the containers.
Qianghua (Huawei) proposes to note this CR and use S2-2104638 or S2-2104720 to address the EN
György (Ericsson) comments that if the new NF discussion under 3981 is successful, then this CR can be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2103966 CR Approval 23.502 CR2754 (Rel-17, 'C'): TSC handling of containers Ericsson Rel-17 Noted Jari (NTT DOCOMO) objects
Devaki (Nokia) objects to the CR, same reason as for 3965.
Qianghua (Huawei) proposes to note
György (Ericsson) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2103967 CR Approval 23.503 CR0577 (Rel-17, 'C'): TSC handling of containers Ericsson Rel-17 Noted Jari (NTT DOCOMO) objects
Devaki (Nokia) objects to the CR, same reason as for 3965.
Qianghua (Huawei) proposes to note
György (Ericsson) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2103981 CR Approval 23.501 CR2833R1 (Rel-17, 'B'): Introduction of architecture for AF requested support of Time Sensitive Communication and Time Synchronization vivo Rel-17 Revision of (Noted) S2-2102843. r17 agreed. Revised to S2-2105082, merging S2-2103963 and S2-2104499 Jari (NTT DOCOMO) provides r01
Qianghua (Huawei) provides comments on r01
Jari (NTT DOCOMO) responds to Qianghua
György (Ericsson) comments.
Qianghua (Huawei) replies
Devaki (Nokia) cannot accept r01 as new TimeSync (only) NF destabilizes the feature, also too narrow and not future proof.
Provides r02.
Chunshan (Tencent) comments.
Devaki (Nokia) comments.
Sebastian (Qualcomm) objects to r00 and r02 and is ok with r01
Devaki (Nokia) comments that r02 reflects QCOM offline comment.
Jari (NTT DOCOMO) provides r03, comments
Sebastian (Qualcomm) comments that it seems Devaki (Nokia) may have misunderstood offline comments
Devaki (Nokia) comments that there is a change of view here by QCOM and some others, not misunderstanding.
Saso (Intel) supports the idea of hijacking the vivo paper for the purpose of exploring the NTT DOCOMO's idea of defining a new NF for time synchronization, as discussed offline and as proposed in r01.
Jari (NTT DOCOMO) provides r04
Qianghua (Huawei) provides r05
Jari (NTT DOCOMO) comments.
Sebastian (Qualcomm) objects to r05
Devaki (Nokia) comments that the revisions of this CR introducing figures (except for r02 with no figure) are against drafting rules.
Devaki (Nokia) provides r06 (no updates to figure, request that figure owners share the editable version).
Sebastian (Qualcomm) provides r07
Devaki (Nokia) responds to Sebastian (Qualcomm).
zhendong (ZTE) provides r08.
Qianghua (Huawei) provides r09
Jari (NTT DOCOMO) provides r10
Chunshan (Tencent) provides r11.
zhendong (ZTE) provides the comments to r11.
zhendong (ZTE) ask whether can move with this approach.
Chunshan (Tencent) responses.
zhendong (ZTE) provides the response.
Chunshan (Tencent) provides r12.
Devaki (Nokia) provides r13.
zhendong (ZTE) provdies r14.
Sang-Jun (Samsung) provides r15.
zhendong (ZTE) clarify 4721 will only focus on the 5.27.2.1 to avoid the overlap.
Jari (NTT DOCOMO) provides r16
Sebastian (Qualcomm) provides r17
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105082 CR Approval 23.501 CR2833R2 (Rel-17, 'B'): Introduction of architecture for AF requested support of Time Sensitive Communication and Time Synchronization vivo Rel-17 Revision of S2-2103981r17, merging S2-2103963, merging S2-2103963 and S2-2104499. Approved Agreed
8.5 S2-2104059 CR Approval 23.501 CR2882 (Rel-17, 'F'): PMIC and BMIC in PCF Tencent Rel-17 Noted Jari (NTT DOCOMO) objects
Devaki (Nokia) objects, agrees with Jari. In addition, it should be possible to activate Time sync service even without a PDU Session.
zhendong (ZTE) similar view with nokia.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2104060 CR Approval 23.502 CR2761 (Rel-17, 'F'): PMIC and BMIC in PCF Tencent Rel-17 r11 agreed. Revised to S2-2105083. Jari (NTT DOCOMO) objects
Jari (NTT DOCOMO) provides r01
Devaki (Nokia) objects for the same reason as for 4059.
Chunshan (Tencent) provides r02.
Qianghua (Huawei) provides r03
Jari (NTT DOCOMO) provider r04
zhendong (ZTE) provides the r05.
Chunshan (Tencent) provides the r06.
Devaki(Nokia) comments on r05, latest version.
Chunshan (Tencent) provides r07.
Jari (NTT DOCOMO) does not agree with r07
Chunshan (Tencent) provides r08.
Chunshan (Tencent) provides r09 with TSCTS.
Chunshan (Tencent) provides r10 with TSCTSF.
Jari (NTT DOCOMO) provides r11
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105083 CR Approval 23.502 CR2761R1 (Rel-17, 'F'): PMIC and BMIC in PCF Tencent Rel-17 Revision of S2-2104060r11. Approved Agreed
8.5 S2-2104061 CR Approval 23.501 CR2883 (Rel-17, 'F'): TSC Assistance Container Determination by AF Tencent, CATT Rel-17 Merged into S2-2105115 Jari (NTT DOCOMO) proposes to merge with S2-2103963
Qianghua (Huawei) proposes to note this CR or merge with S2-2104721
zhendong (ZTE) this CR can be merged to 3963 or 4721.
Chunshan (Tencent) agrees this CR to be merged with 4721.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104062 CR Approval 23.502 CR2762 (Rel-17, 'B'): AF Session Setup and Update with Required QoS Procedure for Trusted Domain Tencent, CATT Rel-17 r11 agreed. Revised to S2-2105084, merging S2-2104549 Qianghua (Huawei) proposes to note this CR
Jari (NTT DOCOMO) responds to Qianghua
Chunshan (Tencent) provides r01.
Jari (NTT DOCOMO) provides r02.
Qianghua (Huawei) provides r03
Chunshan (Tencent) provides r04.
Devaki (Nokia) wonders what 'priority' refers to in the revised versions.
Qianghua (Huawei) replies
Chunshan (Tencent) provides r05 based on the new TSCTS NF.
Chunshan (Tencent) provides r06.
Qianghua (Huawei) provides r07
Jari (NTT DOCONO) comments
Chunshan (Tencent) comments on r07.
Chunshan (Tencent) response to Jari.
Chunshan (Tencent) provides r08.
Jari (NTT DOCOMO) provides r09
Devaki (Nokia) provides r10.
Chunshan (Tencent) provides r11.
==== 8.X, 9.X Revisions Deadline ====
Qianghua (Huawei) comments that re-numbering of steps in the call flow 4.15.6.6 and 4.15.6.6a brings conflicts with other CRs: S2-2104572, S2-2103055, and possibly other specifications that have references to these clauses, so we propose that we either endorse this CR this meeting or allow revision at SA Plenary to address the re-numbering issue.
Chunshan (Tencent) responses.
Qianghua (Huawei) proposes this for CC#4 to let Puneet/Maurice be aware of those issues, and propose to record in notes that: 'numbering needs to be fixed back before it gets approved in TSG, CR is in a separate package to SA, and companies are committing to bring a properly numbered CR to plenary'
Chunshan (Tencent) questions to add note.
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105084 CR Approval 23.502 CR2762R1 (Rel-17, 'B'): AF Session Setup and Update with Required QoS Procedure for Trusted Domain Tencent, CATT Rel-17 Revision of S2-2104062r11, merging S2-2104549. Approved Agreed
8.5 S2-2104063 CR Approval 23.503 CR0580 (Rel-17, 'F'): TSC Assistance Container Determination in the trusted domain Tencent, CATT Rel-17 Merged into S2-2105112 Qianghua (Huawei) proposes to note this CR or merge with S2-2104722
Chunshan (Tencent) provides r01.
Devaki (Nokia) proposes to consider this CR as merged with 4600 (reflecting CC#3 way forward proposal)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104118 CR Approval 23.501 CR2690R2 (Rel-17, 'B'): Support for IEEE 1588 Boundary Clocks in time synchronization service NTT DOCOMO, Ericsson, Huawei, ZTE, ETRI, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103020. r02 agreed. Revised to S2-2105085. Devaki (Nokia) provides r01.
Shabnam (Ericsson) provides r02, complying with MCC instructions on not referencing NOTE as numbers cannot be maintained.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105085 CR Approval 23.501 CR2690R3 (Rel-17, 'B'): Support for IEEE 1588 Boundary Clocks in time synchronization service NTT DOCOMO, Ericsson, Huawei, ZTE, ETRI, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104118r02. Approved Agreed
8.5 S2-2104119 CR Approval 23.501 CR2896 (Rel-17, 'C'): Exposure of Time synchronization as a service - description Nokia, Nokia Shangai Bell Rel-17 r02 agreed. Revised to S2-2105086. Jari (NTT DOCOMO) proposes to merge with S2-2104635
Devaki (Nokia) does not agree that this paper to be merged as 4735 does not cover the content, rather they are complimentary. Provides r01.
Jari (NTT DOCOMO) responds to Devaki
Jari (NTT DOCOMO) provides r02
Shabnam (Ericsson) asks clarification on what the term ' (g)PTP grandmaster capable, 5G Clock quality.' means and what does this apply to? Since we already refer to the IEEE specs for (g)PTP.
Devaki (Nokia) replies to Ericsson.
Devaki (Nokia) responds to Jari.
Jari (NTT DOCOMO) objects r00 and r01
Shabnam (Ericsson) my concern is that we will keep updating both 23.501 and 23.502 to align parameters? Or should we add a reference to 23.502 where the list of parameters should reside?
Devaki (Nokia) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105086 CR Approval 23.501 CR2896R1 (Rel-17, 'C'): Exposure of Time synchronization as a service - description Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2104119r02. Approved Agreed
8.5 S2-2104120 CR Approval 23.502 CR2774 (Rel-17, 'C'): Exposure of Time synchronization as a service - procedure Nokia, Nokia Shangai Bell Rel-17 Merged into S2-2105201 Jari (NTT DOCOMO) proposes to merge with S2-2104637
Devaki (Nokia) ok to merge with S2-2104637 as per offline discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104121 CR Approval 23.503 CR0585 (Rel-17, 'C'): Exposure of Time synchronization as a service - policy Nokia, Nokia Shangai Bell Rel-17 r01 agreed. Revised to S2-2105087. Qianghua (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105087 CR Approval 23.503 CR0585R1 (Rel-17, 'C'): Exposure of Time synchronization as a service - policy Nokia, Nokia Shangai Bell Rel-17 Revision of S2-2104121r01. Approved Agreed
8.5 S2-2104122 CR Approval 23.501 CR2897 (Rel-17, 'C'): Time synchronization accuracy - description Nokia, Nokia Shangai Bell Rel-17 Postponed Jari (NTT DOCOMO provides r01
Qianghua (Huawei) provides comments
Sebastian (Qualcomm) proposes to postpone the CR
Shabnam (Ericsson) supports to postpone the CR as well, need RAN response and also need to understand better what can be provided from CN with RAN input.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2104123 CR Approval 23.502 CR2775 (Rel-17, 'C'): Time synchronization accuracy - procedure Nokia, Nokia Shangai Bell Rel-17 Postponed Jari (NTT DOCOMO) proposes to merge with S2-2104637
Sebastian (Qualcomm) proposes to postpone the CR
Shabnam (Ericsson) supports to postpone the CR as well, need RAN response and also need to understand better what can be provided from CN with RAN input.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2104151 CR Approval 23.502 CR2779 (Rel-17, 'C'): Handling the time synchronization information provided by the AF ETRI Rel-17 Merged into S2-2105201 Jari (NTT DOCOMO) proposes to note, or merge with S2-2104637
Devaki (Nokia) agrees with Jari (NTT DOCOMO), proposes to consider this as merged with 4637.
Yoohwa (ETRI) is fine with this merges into 4637.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104186 CR Approval 23.501 CR2904 (Rel-17, 'F'): KI#3A Support QoS mapping based on priority for TSC exposure Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2105088. Devaki (Nokia) comments.
Qianghua (Huawei) provides r01
Sebastian (Qualcomm) objects to the CR (incl. revisions)
Qianghua (Huawei) replies
Jari (NTT DOCOMO) comments
Jari (NTT DOCOMO) responds to Qianghua
Shabnam (Ericsson) cannot accept this CR as it is not part of the conclusion nor part of the scope of IIoT. Only aspect that can be acceptable would be to use current Alt QoS as is.
Qianghua (Huawei) provides r02
Devaki (Nokia) comments and has concerns regarding r02.
Qianghua (Huawei) provides r03
Jari (NTT DOCOMO) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105088 CR Approval 23.501 CR2904R1 (Rel-17, 'F'): KI#3A Support QoS mapping based on priority for TSC exposure Huawei, HiSilicon Rel-17 Revision of S2-2104186r04. Approved Agreed
8.5 S2-2104187 CR Approval 23.501 CR2905 (Rel-17, 'F'): Clarification on support of PTP GM function in TT Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2105089. Jari (NTT DOCOMO) provides r01
Devaki (Nokia) provides r02.
Sebastian (Qualcomm) provides r03
Qianghua (Huawei) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105089 CR Approval 23.501 CR2905R1 (Rel-17, 'F'): Clarification on support of PTP GM function in TT Huawei, HiSilicon Rel-17 Revision of S2-2104187r04. Approved Agreed
8.5 S2-2104188 CR Approval 23.502 CR2788 (Rel-17, 'F'): Clarification on support of PTP GM function in TT Huawei, HiSilicon Rel-17 Confirm Specification Number - CR states 23.501! r04 agreed. Revised to S2-2105090. Jari (NTT DOCOMO) provides r01, comments
Qianghua (Huawei) replies
Qianghua (Huawei) replies again
Jari (NTT DOCOMO) comments
Devaki (Nokia) provides r02.
Jari (NTT DOCOMO) provides r03
Qianghua (Huawei) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105090 CR Approval 23.502 CR2788R1 (Rel-17, 'F'): Clarification on support of PTP GM function in TT Huawei, HiSilicon Rel-17 Revision of S2-2104188r04. Approved Agreed
8.5 S2-2104260 CR Approval 23.501 CR2908 (Rel-17, 'C'): Resolving EN for Hold and Forward mechanism Samsung Rel-17 r02 agreed. Revised to S2-2105091, merging S2-2104636 and S2-2104719 Shabnam (Ericsson) proposes to consider this CR merged with CR in document 04636 which has Cat F, which is more accurate considering we are neither adding nor modifying feature but removing EN.
zhendong (ZTE) proposes both 4636 and 4719 are merged into this CR.
Sang-Jun (Samsung) proposes to mege 4636 and 4719 into 4260, as discussed offlie CC. It is decision on whether Rel-16 feature is modifed to support a case in Rel-17 or not, so Cat C is more accurate.
Qianghua (Huawei) provides r01
Shabnam (Ericsson) objects to r00 and r01, it is not a new feature to remove EN and we do not agree to add any text on H&F and for Ethernet it is as Rel-16 so no clarification needed.
Devaki (Nokia) wonders if a CR can be objected by companies just for CR CATegory when the content is identical?!
Sang-Jun (Samsung) provides r02, which is CR category F.
Qianghua (Huawei) provides r03
Sebastian (Qualcomm) objects to r03
Shabnam (Ericsson) comments to Nokia that she fails to understand why when there is a CR with Cat F, we note that CR and use another CR that requires change of Cat but content is identical?
Devaki (Nokia) comments that companies (e.g. HUA) proposed revision to the text. Otherwise, it does not matter from my perspective.
Shabnam (Ericsson) responds to Huawei proposal and objects to adding the NOTE.
Haris(Qualcomm) reiterates earlier comment and indicate that will object to any revision that contains NOTE as in r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105091 CR Approval 23.501 CR2908R1 (Rel-17, 'C'): Resolving EN for Hold and Forward mechanism Samsung Rel-17 Revision of S2-2104260r02, merging S2-2104636, merging S2-2104636 and S2-2104719. Approved Agreed
8.5 S2-2104278 CR Approval 23.501 CR2911 (Rel-17, 'B'): KI#3B, Temporal Validity Condition Description Samsung Rel-17 CC#4: This was left for CC#5. CC#5: r10 + changes agreed. Revised to S2-2105200. Devaki (Nokia) comments and objects to original version.
Sang-Jun (Samsung) provides r01 and responses to Devaki (Nokia).
Jari (NTT DOCOMO) provides r02
Devaki (Nokia) comments.
Sang-Jun (Samsung) provides r03, and responds to Jari (NTT DOCOMO) and Devaki (Nokia).
Jari (NTT DOCOMO) responds to Sang-Jun
Sang-Jun (Samsung) provides r04 and responds to Jari (NTT DOCOMO).
Jari (NTT DOCOMO) responds to Devaki
Devaki (Nokia) replies to Jari.
Sang-Jun (Samsung) provides r05.
Jari (NTT DOCOMO) provides r06.
Shabnam (Ericsson) asks for some clarification and comments.
Devaki (Nokia) provide r07.
Sang-Jun (Samsung) provides r08 and responses to Jari, Devaki, Shabnam.
Jari (NTT DOCOMO) does not agree with r08
Sang-Jun (Samsung) is ok with r07.
Shabnam (Ericsson) still not convinced of the time in future, so how would that be communicated that it is in future? When does the future arrive, is it absolute time of in 2 hours or does the external AF and XYZ be in same time zone?
Sang-Jun (Samsung) provides r09 and responds to Shabnam (Ericsson).
Shabnam (Ericsson) provides r10, comments.
Jari (NTT DOCOMO) comments.
Devaki (Nokia) provides r11.
==== 8.X, 9.X Revisions Deadline ====
Shabnam (Ericsson) agrees with NTT DoCoMo and also confirms that for 23.502 CR we agree with QC to remove the 5G clock aspects at this time. Nokia update in r11 aligns with future 23.502 updates potential.
Sang-Jun (Samsung) prefers r09 or r11 but can live with r10, and proposes to add a NOTE: Expiry of validity condition shall not apply for UE(s) in idle mode.
Jari (NTT DOCOMO) can agree r09, r10, r11
Shabnam (Ericsson) can agree with r10, objects to other revisions.
r11 clause for 23.502 may not be there so I would suggest not to use r11 for now.
Devaki (Nokia) comments that r10 is incorrect as it does not address IDLE UE case; Also reference to TS 23.502 or 501 section where the method is described is essential.
Sang-Jun (Samsung) will provide a revision based on r10 addressing idle UE case and addressing the reference to the section where the 5G reference timing distrbution.
==== 8.X, 9.X Final Deadline ====
Sang-Jun (Samsung) provides r12 based on r10 addressing idle UE case and addressing the reference to the section where the 5G reference timing distribution is described in 23.501.
Revised
8.5 S2-2105200 CR Approval 23.501 CR2911R1 (Rel-17, 'B'): KI#3B, Temporal Validity Condition Description Samsung Rel-17 Revision of S2-2104278r10 + changes. Approved Agreed
8.5 S2-2104292 CR Approval 23.501 CR2915 (Rel-17, 'F'): Updates initialization of PTP instance CATT Rel-17 Postponed Shabnam (Ericsson) provides r01 and comments that our understanding is that the management is handled via CP in 5GS and as such the changes are not applicable.
Yuan (CATT) replies to Shabnam (Ericsson).
Jari (NTT DOCOMO) supports r00, comments
Yuan (CATT) agrees with Jari (NTT DOCOMO) and supports original version r00.
Shabnam (Ericsson) provides details for the concerns in comments.
Devaki (Nokia) also prefers original version based on our understanding of PTP specs.
Shabnam (Ericsson) proposes to postpone this CR and provides further comment.
==== 8.X, 9.X Revisions Deadline ====
Yuan (CATT) replies to Shabnam (Ericsson) and suggests to approve r00 to correct the initialization description in this meeting.
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2104293 CR Approval 23.502 CR2797 (Rel-17, 'B'): KI#3B, Temporal Validity Condition Procedure Samsung Rel-17 Confirm CR Number - CR states 2792! Postponed Devaki (Nokia) comments and objects to original version (same as 4278).
Sang-Jun (Samsung) provides r01 and responses to Devaki (Nokia).
Jari (NTT DOCOMO) proposes to note
Sang-Jun (Samsung) provides r02 and responds to Jari (NTT DOCOMO).
Devaki (Nokia) proposes to postpone this CR and focus on progressing 4278 in this meeting for validity timer. We need to first agree on the concept prior to adding just the parameter.
==== 8.X, 9.X Revisions Deadline ====
Sang-Jun (Samsung) agrees to postpone this CR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.5 S2-2104368 CR Approval 23.501 CR2773R2 (Rel-17, 'B'): Update for PTP in time synchronization service and BMCA Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103024. r01 agreed. Revised to S2-2105092. Devaki (Nokia) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105092 CR Approval 23.501 CR2773R3 (Rel-17, 'B'): Update for PTP in time synchronization service and BMCA Huawei, HiSilicon Rel-17 Revision of S2-2104368r01. Approved Agreed
8.5 S2-2104499 CR Approval 23.501 CR2933 (Rel-17, 'F'): Update TT to support non-TSN time synchronization Huawei, HiSilicon Rel-17 Merged into S2-2105082 Devaki (Nokia) proposes to merge this with 3981.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104533 CR Approval 23.502 CR2837 (Rel-17, 'F'): Updating time synchronization parameters ETRI Rel-17 Merged into S2-2105201 Devaki (Nokia) comments.
Jari (NTT DOCOMO) proposes to merge with S2-2104637
Yoohwa (ETRI) is fine with merging with 4637.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104549 CR Approval 23.502 CR2838 (Rel-17, 'C'): Requested 5GS delay and UE-DS-TT residence time NTT DOCOMO, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Merged into S2-2105084 Chunshan (Tencent) propose this paper to be merged into paper S2-2104062.
Qianghua (Huawei) asks if this is merged into 4062?
zhendong (ZTE) proposes this CR is merged into 4062..
Chunshan (Tencent) asks to confirm this paper to be merged into 4062 or be noted.
Jari (NTT DOCOMO) agrees to merge with 4062
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104572 CR Approval 23.502 CR2839 (Rel-17, 'C'): Alt-QoS for TSC NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 r07 agreed. Revised to S2-2105093. Chunshan (Tencent) provides r01
Devaki (Nokia) provides r02.
Chunshan (Tencent) provides clarification and objects r02.
Qianghua (Huawei) provides r03
zhendong (ZTE) provides the comments.
Sebastian (Qualcomm) asks questions
Shabnam (Ericsson) cannot find this as part of the conclusion of IIoT and as such do not agree to adding any additional parameters than what is already available in Rel-16.
Devaki (Nokia) provides r04 clarifying that it is based on Alt. QoS specified in Rel-16.
Qianghua (Huawei) replies
Shabnam (Ericsson) objects to original and so far all revisions since the proposal adds extra parameters. This was not part of the original WI scope and we do not agree to this addition. Provides potential text in comments.
Devaki (Nokia) states that R04 refers to the parameters in Alt QoS clause (PDB, PER, GBR); if you don't believe so, kindly requests Ericsson to provide a technical revision (like others do) as email comments/objections are not constructive unfortunately. Also, provides r05.
Devaki (Nokia) replies.
Shabnam (Ericsson) provides r06, still has some hesitancy on this but provides a revision before deadline to continue the work.
Devaki (Nokia) is fine with r06.
Devaki (Nokia) provides r07 just to add new TSCTSF on top of r06.
==== 8.X, 9.X Revisions Deadline ====
Qianghua (Huawei) comments that this CR updates on the same clause with S2-2104062, which will cause conflicts when implementing in the TS, proposes this for CC#4
Jari (NTT DOCOMO) does not agree with the conflict
Devaki (Nokia) comments that merge of multiple CRs will have to be done by the Editor/MCC eventually.
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105093 CR Approval 23.502 CR2839R1 (Rel-17, 'C'): Alt-QoS for TSC NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104572r07. Approved Agreed
8.5 S2-2104581 CR Approval 23.501 CR2946 (Rel-17, 'C'): Definition of the UE-DS-TT residence time NTT DOCOMO, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2104600 CR Approval 23.503 CR0599 (Rel-17, 'C'): Requested 5GS delay and UE-DS-TT residence time NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 r07 agreed. Revised to S2-2105112, merging S2-2104722 and S2-2104063 Chunshan (Tencent) provides r01
Chunshan (Tencent) provides clarification.
Devaki (Nokia) replies to Chunshan (Tencent).
Chunshan (Tencent) provides clarification .
Jari (NTT DOCOMO) provides r02
Qianghua (Huawei) objects r00-r02
zhendong (ZTE) object this CR.
Jari (NTT DOCOMO) provides r03
Qianghua (Huawei) provides r04
Jari (NTT DOCOMO) comments
Qianghua (Huawei) replies
Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
Jari (NTT DOCOMO) provides r05
Qianghua (Huawei) provides r06
Haris(Qualcomm) provides r07
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105112 CR Approval 23.503 CR0599R1 (Rel-17, 'C'): Requested 5GS delay and UE-DS-TT residence time NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104600r07, merging S2-2104722, merging S2-2104722 and S2-2104063. Approved Agreed
8.5 S2-2104632 CR Approval 23.501 CR2959 (Rel-17, 'F'): Grandmaster candidate enabled management information per PTP instance Qualcomm Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.5 S2-2104635 CR Approval 23.501 CR2960 (Rel-17, 'C'): Time Synchronization service exposure NTT DOCOMO Rel-17 r05 agreed. Revised to S2-2105113. Devaki (Nokia) provides r01.
Jari (NTT DOCOMO) responds to Devaki
Sang-Jun (Samsung) provides r02.
Devaki (Nokia) just noticed that this paper deletes the bullets for time sync methods with the concept behind (original version + all revisions), this is not acceptable. Provides r03.
Yoohwa (ETRI) asks a question for clarification.
Jari (NTT DOCOMO) responds to Yoohwa
Devaki (Nokia) provides r04 with minor correction and cleanup.
Jari (NTT DOCOMO) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105113 CR Approval 23.501 CR2960R1 (Rel-17, 'C'): Time Synchronization service exposure NTT DOCOMO Rel-17 Revision of S2-2104635r05. Approved Agreed
8.5 S2-2104636 CR Approval 23.501 CR2961 (Rel-17, 'F'): Clarification of hold/forward buffer support in 5GS Qualcomm, Ericsson Rel-17 Confirm CR Number - CR states ! Merged into S2-2105091 zhendong (ZTE) proposes this CR is merged into S2-2104260.
Sang-Jun (Samsung) proposes to mege 4636 and 4719 into 4260, as discussed offlie CC. It is decision on whether Rel-16 feature is modifed to support a case in Rel-17 or not, so Cat C is more accurate.
Haris(Qualcomm) agrees to mark as merged with S2-2104260
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104637 CR Approval 23.502 CR2854 (Rel-17, 'C'): Time synchronization service exposure NTT DOCOMO Rel-17 CC#4: This was left for CC#5. CC#5: r18 + changes agreed. Revised to S2-2105201, merging S2-2104120, S2-2104151 and S2-2104533. Jari (NTT DOCOMO) provides r01
Chunshan(Tencent) provides r02.
Chunshan(Tencent) provides r03.
Devaki (Nokia) provides r04.
Chunshan (Tencent) provides r05.
Jari (NTT DOCOMO) responds to Chunshan.
Chunshan(Tencent) provides clarification.
Chunshan (Tencent) provides clarification.
Chunshan (Tencent) responds to Jari.
Jari (NTT DOCOMO) provides r06
Chunshan(Tencent) responds to Jari and provides r07.
Jari (NTT DOCOMO) provides r08
Chunshan(Tencent) requests for clarification.
Yoohwa (ETRI) provides r09 to merge with 4151.
Jari (NTT DOCOMO) responds to Yoohwa
Qianghua (Huawei) provides comments
Qianghua (Huawei) replies
Jari (NTT DOCOMO) responds to Qianghua
Sang-Jun (Samsung) provides r10.
Jari (NTT DOCONO) provides r11.
Yoohwa (ETRI) responds to Jari.
Sebastian (Qualcomm) provides r12
Devaki (Nokia) has strong concerns with r12 as it removes support for 5G clock based time sync completely. There was no question on whether 5G clock sync can be supported in RAN2 LS, this was never an open question thus cannot accept removal of this.
Jari (NTT DOCOMO) provides r13
Jari (NTT DOCOMO) provides r14.
Jari (NTT DOCOMO) provides r15. (r14 was from Chunshan)
Qianghua (Huawei) provides r16
Devaki (Nokia) provides r17.
zhendong (ZTE) provides r18.
==== 8.X, 9.X Revisions Deadline ====
Haris(Qualcomm) comments and indicates that r13-r18 are not acceptable
Shabnam (Ericsson) shares Qualcomm concerns and agrees we need to wait until next meeting on 5G clock aspects.
Devaki (Nokia) comments.
Sang-Jun (Samsung) shares similar view as Nokia, as RAN2 already decided positive answer to SA2's LS.
Shabnam (Ericsson) repeats that we need sometime to understand the implications. RAN2 indicated it is beneficial, nothing more. So our objection remains.
Devaki (Nokia) objects to r12 as it goes backward (reasons stated earlier) by undoing the agreements.
Shabnam (Ericsson) objects to all revisions except r12, we have strong concerns to now impact AMF as well as UDR in the AM policy for PCF. We are ok to prepare an additional revision on top to include the new entity.
Jari (NTT DOCOMO) comments, proposes a new revision
Jari (NTT DOCOMO) provides r19 for CC#4
Haris(Qualcomm) objects to r18
Haris(Qualcomm) is ok with r19
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105201 CR Approval 23.502 CR2854R1 (Rel-17, 'C'): Time synchronization service exposure NTT DOCOMO Rel-17 Revision of S2-2104637r18 + changes, merging S2-2104120, S2-2104151 and S2-2104533. Approved Agreed
8.5 S2-2104638 CR Approval 23.501 CR2962 (Rel-17, 'F'): Clarification of applicability of port/bridge management information Qualcomm Rel-17 Confirm CR Number - CR states ! r02 agreed. Revised to S2-2105114, merging S2-2104720 Jari (NTT DOCOMO) comments
Devaki (Nokia) objects to the CR as it is going in the wrong direction - limitation is not on the network side rather the limitation is on the DS-TT side.
Sebastian (Qualcomm) provides r01
Devaki (Nokia) proposes that the limitation related to Time Sync is documented as part of 4720.
zhendong (ZTE) is agree with devaki, and propose this CR is merged into 4720.
György (Ericsson) comments that it is important to document explicitly which parameters are supported, hence supports Qualcomm to proceed with this CR.
Devaki (Nokia) comments.
György (Ericsson) responds to Nokia and provides r02.
György (Ericsson) responds to DOCOMO.
==== 8.X, 9.X Revisions Deadline ====
György (Ericsson) comments.
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105114 CR Approval 23.501 CR2962R1 (Rel-17, 'F'): Clarification of applicability of port/bridge management information Qualcomm Rel-17 Revision of S2-2104638r02, merging S2-2104720. Approved Agreed
8.5 S2-2104717 CR Approval 23.501 CR2974 (Rel-17, 'B'): KI#3B, Clarification on the PTP instance type ZTE Rel-17 Noted Shabnam (Ericsson) provides r01 to add the same reference in the Table as well.
Devaki (Nokia) comments.
Jari (NTT DOCOMO) comments.
zhendong (ZTE) provides the r02.
zhendong (ZTE) provides r03.
Qianghua (Huawei) provides comments
Sebastian (Qualcomm) objects to the CR (incl. revisions)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2104718 CR Approval 23.503 CR0603 (Rel-17, 'B'): KI#3A, TSC communication other than TSN impacts to 23.503 ZTE Rel-17 Noted Devaki (Nokia) provides r01.
Qianghua (Huawei) provides r02 and co-signs
Jari (NTT DOCOMO)objects
Sebastian (Qualcomm) objects to the CR (incl. revisions)
zhendong (ZTE) provdies the r03 to remove the new clause.
Qianghua (Huawei) provides r04
==== 8.X, 9.X Revisions Deadline ====
zhendong (ZTE) is fine with r04.
Jari (NTT DOCOMO) can agree r04
Haris(Qualcomm) objects to r04 since it still mentions TSC QoS
==== 8.X, 9.X Final Deadline ====
Noted
8.5 S2-2104719 CR Approval 23.501 CR2975 (Rel-17, 'B'): KI#3A, Clarification on the EN on the hold and buffer ZTE Rel-17 Merged into S2-2105091 Shabnam (Ericsson) proposes to consider this CR merged with CR in document 04636 which has Cat F, which is more accurate considering we are neither adding nor modifying feature but removing EN.
zhendong (ZTE) agree to merge this CR into SA2-2104260.
Shabnam (Ericsson) yes but then I checked the 3 and I think Cat F is the correct interpretation since we are only removing an EN and not changing any feature or adding/removing any and thus Cat C and B are not accurate?
zhendong (ZTE) agree that the 'F' is correct.
Sang-Jun (Samsung) proposes to mege 4636 and 4719 into 4260, as discussed offlie CC. It is decision on whether Rel-16 feature is modifed to support a case in Rel-17 or not, so Cat C is more accurate.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104720 CR Approval 23.501 CR2976 (Rel-17, 'B'): Fix EN on info exchanged between NEF and DS-TT,NW-TT ZTE Rel-17 Merged into S2-2105114 Devaki (Nokia) supports the principle of the CR but comments to remove the added new text.
Sebastian (Qualcomm) disagrees with proposal from Nokia
Devaki (Nokia) comments that the note should reflect this is for the new NF (if that is agreed).
György (Ericsson) comments that we should use 4638 to address the editor's note.
zhendong (ZTE) is ok to add a new column for the new NF in 4638
Sebastian (Qualcomm) proposes to merge with 4638; and objects to this CR to avoid approval as we get closer to the deadline
zhendong (ZTE) it is fine for me to merge this CR into 4638.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.5 S2-2104721 CR Approval 23.501 CR2977 (Rel-17, 'B'): Clarification on TSCAI for the non TSC service ZTE Rel-17 r08 agreed. Revised to S2-2105115, merging S2-2104061 Qianghua (Huawei) agree the concept in this CR, propose to merge other related CRs into this
Jari (NTT DOCOMO) comments
zhendong (ZTE) provides the response.
Sang-Jun (Samsung) agrees with Zhendong (ZTE) and Qianghua (Huawei).
Devaki (Nokia) provides r01.
Qianghua (Huawei) provides r02
Jari (NTT DOCOMO) provides r03
György (Ericsson) comments.
zhendong (ZTE) provides the comments .
Jari (NTT DOCONO) responds to zhendong
Yuan (CATT) comments.
Devaki (Nokia) comments that this CR should be updated to reflect that the TSC assistance container is created by the new NF.
zhendong (ZTE) provdies r04.
zhendong (ZTE) provides r05.
Qianghua (Huawei) provides r06
zhendong (ZTE) provides r07.
zhendong (ZTE) provides r08.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.5 S2-2105115 CR Approval 23.501 CR2977R1 (Rel-17, 'B'): Clarification on TSCAI for the non TSC service ZTE Rel-17 Revision of S2-2104721r08, merging S2-2104061. Approved Agreed
8.5 S2-2104722 CR Approval 23.503 CR0604 (Rel-17, 'B'): The impacts of non-TSC service with periodicity requirement ZTE Rel-17 Merged into S2-2105112 Chunshan (Tencent) provides r01
Chunshan (Tencent) provides wrong tdoc number. Please ignore this email.
Chunshan (Tencent) provides clarification.
Jari (NTT DOCOMO) comments
zhendong (ZTE) provides the response.
Qianghua (Huawei) proposes to note this CR or merge this with S2-2104600, based on working assumption
zhendong (ZTE) is ok to merge this into S2-2104600.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.6 - - - Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) - - Docs:=23 -
8.6 - - - QoS flow performance measurement - - Docs:=11 -
8.6 S2-2103970 CR Approval 23.501 CR2721R2 (Rel-17, 'B'): Send PMF messages to a target QoS flow Lenovo?, Motorola Mobility?, LG Electronics?, Broadcom?, ZTE?, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103303. Confirm Sources! ATSSS_Ph2 not eATSSS_Ph2. CC#5: This was noted. Myungjune (LGE) provides comments.
Rainer (Nokia) replies.
Myungjune (LGE) replies to Rainer (Nokia).
Apostolis (Lenovo) comments that if the proposal in S2-2104526 is agreed (i.e. to use different ports for different QoS flows), then measurements per QoS flow can also be supported over EPS and this CR is not needed.
Rainer (Nokia) replies to Apostolis (Lenovo).
==== 8.X, 9.X Revisions Deadline ====
Apostolis (Lenovo) comments that some clarifications may be needed on how the UE performs measurements per QoS over EPS.
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104072 DISCUSSION Discussion Discussion on how to send a PMF message over a target QoS Flow. LG Electronics Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104645 CR Approval 23.501 CR2721R4 (Rel-17, 'B'): Send PMF messages to a target QoS flow Lenovo?, Motorola Mobility?, LG Electronics?, Broadcom?, ZTE Rel-17 Revision of (Agreed) S2-2103303. Confirm Sources! Merged into S2-2105197 Rainer (Nokia) asks for clarification and proposes to merge with 4526.
Jinguo(ZTE) replies to Rainer (Nokia) and agree to merge with 4526.
Apostolis (Lenovo) comments.
Jinguo(ZTE) response
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.6 S2-2104525 DISCUSSION Discussion Discussion on sending PMF messages to a specific (target) QoS flow. Lenovo, Motorola Mobility, LG Electronics, Broadcom Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104526 CR Approval 23.501 CR2721R3 (Rel-17, 'B'): Send PMF messages to a target QoS flow Lenovo, Motorola Mobility, LG Electronics, Broadcom, ZTE Rel-17 Revision of (Agreed) S2-2103303. CC#5: r01 agreed. Revised to S2-2105197, merging S2-2104645. Dario S. Tonesi (Qualcomm) asks question for clarification
DongYeon (Samsung) asks a question for clarification.
Apostolis (Lenovo) responds to Dario's (Qualcomm) questions.
Apostolis (Lenovo) provides r01.
Dario S. Tonesi (Qualcomm) provides r02
Apostolis (Lenovo) responds to Dario (Qualcomm).
Apostolis (Lenovo) suggests that S2-2104526 should be discussed in CC#4 together with S2-2104081 , which proposes an alternative solution to the same issue.
We can decide which of these two documents to approve with a SoH.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2105197 CR Approval 23.501 CR2721R5 (Rel-17, 'B'): Send PMF messages to a target QoS flow Lenovo, Motorola Mobility, LG Electronics, Broadcom, ZTE Rel-17 Revision of S2-2104526r01, merging S2-2104645. Approved Agreed
8.6 S2-2104647 DISCUSSION Agreement Discussion on Packet Loss Rate Measurements per QoS flow. ZTE Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104081 CR Approval 23.502 CR2571R2 (Rel-17, 'B'): PMF enhancement per QoS flow Huawei, HiSilicon Rel-17 Revision of (Postponed) S2-2102378. CC#5: Noted Stefan (Ericsson) provides
Susan (Huawei) responds to Stefan.
Stefan (Ericsson) provides r01
Myungjune (LGE) provides r02.
Susan (Huawei) is fine with r01.
Apostolis (Lenovo) suggests that S2-2104081 should be discussed in CC#4 together with S2-2104526 , which proposes an alternative solution to the same issue.
We can decide which of these two documents to approve with a SoH.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104326 CR Approval 23.501 CR2917 (Rel-17, 'B'): Access performance measurement reuse for other target QoS flows Samsung Rel-17 Noted Rainer (Nokia) comments.
Myungjune (LGE) provides comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2103871 CR Approval 23.501 CR2746R2 (Rel-17, 'B'): QoS Flow recognition for per QoS Flow measurements Ericsson, LG Electronics, Lenovo, Motorola Mobility Rel-17 Revision of (Agreed) S2-2103304. r01 agreed. Revised to S2-2104889. Myungjune (LGE) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Apostolis (Lenovo) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2104889 CR Approval 23.501 CR2746R3 (Rel-17, 'B'): QoS Flow recognition for per QoS Flow measurements Ericsson, LG Electronics, Lenovo, Motorola Mobility Rel-17 Revision of S2-2103871r01. Approved Agreed
8.6 - - - UE assistance data/operation - - Docs:=5 -
8.6 S2-2103870 CR Approval 23.501 CR2647R3 (Rel-17, 'B'): PMF extensions for sending UE-assistance data to UPF Ericsson, Lenovo, Motorola Mobility, LG Electronics Rel-17 Revision of (Agreed) S2-2103309. CC#5: This was postponed. Rainer (Nokia) asks for clarification.
Stefan (Ericsson) replies to Rainer and provides r01
Rainer (Nokia) is ok with r01.
Susan (Huawei) raises comments.
Stefan (Ericsson) replies to Susan and provides r02
Stefan (Ericsson) provides r03
Spencer (Tencent) replies to Stefan and Susan and requests to cosign r02.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) responds to Spencer and asks some questions to Stefan.
Stefan (Ericsson) replies to Susan and asks questions
Dario S. Tonesi (Qualcomm) raises questions due to discussion in CT1 that proposes to introduce ATSSS Rule ID in Rel-16. Ask if we should discuss this in CC#4.
Apostolis (Lenovo) responds to Dario.
Rainer (Nokia) comments.
Susan (Huawei) responds to Stefan, and cannot agree with all versions of this CR, and asks to postpone it to next meeting.
Stefan (Ericsson) provides addiitonal replies to Susan
==== 8.X, 9.X Final Deadline ====
Postponed
8.6 S2-2104414 DISCUSSION Agreement Identification of impacted steering decision in UPF for UE-assistance operation. Ericsson Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.6 S2-2104080 CR Approval 23.501 CR2647R4 (Rel-17, 'B'): PMF extensions for sending UE-assistance data to UPF [Lenovo, Motorola Mobility], Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103309. Postponed Stefan (Ericsson) provides comments and questions
Rainer (Nokia) agrees with Ericsson and comments.
DongYeon (Samsung) comments.
Susan (Huawei) responds to Stefan.
Susan (Huawei) responds to Rainer.
Susan (Huawei) replies to DongYeon.
Stefan (Ericsson) replies to Susan
Susan (Huawei) replies to Stefan.
Myungjune (LGE) asks question.
Susan (Huawei) replies to Myungjune and provides r01.
Stefan (Ericsson) comments
Apostolis (Lenovo) supports Stefan's (Ericsson) comments and concerns.
Dario S. Tonesi (Qualcomm) provides r02 and r03
Susan (Huawei) replies to Stefan and Apostolis.
Apostolis (Lenovo) clarifies his previous concern.
==== 8.X, 9.X Revisions Deadline ====
Susan (Huawei) replies to Apostolis.
Apostolis (Lenovo) responds to Susan (Huawei) and asks further questions.
Apostolis (Lenovo) asks further questions to Susan (Huawei).
Stefan (Ericsson) comments on Susan's replies
Susan responds to Apostolis (Lenovo).
Susan (Huawei) replies to Dario.
Stefan (Ericsson) objects to all revisions
Apostolis (Lenovo) responds to Susan (Huawei).
Susan (Huawei) responds to Apostolis.
Dario S. Tonesi (Qualcomm) replies to Susan.
==== 8.X, 9.X Final Deadline ====
Postponed
8.6 S2-2103971 CR Approval 23.501 CR2743R2 (Rel-17, 'B'): Introduction of UE-assistance operation Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103308. r02 agreed. Revised to S2-2104890. Apostolis (Lenovo) provides r01.
Rainer (Nokia) is fine with r01.
Susan (Huawei) cannot accept r01 and provides r02.
==== 8.X, 9.X Revisions Deadline ====
Apostolis (Lenovo) can live with r02 (although he prefers r01).
Rainer (Nokia) is ok with r02.
Susan (Huawei) responds to Apostolis.
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2104890 CR Approval 23.501 CR2743R3 (Rel-17, 'B'): Introduction of UE-assistance operation Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103971r02. Approved Agreed
8.6 - - - Threshold for priority-based steering mode - - Docs:=2 -
8.6 S2-2103972 CR Approval 23.501 CR2811R2 (Rel-17, 'C'): Introducing threshold conditions for priority-based steering mode in TS 23.501 Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Motorola Mobility Rel-17 Revision of (Agreed) S2-2103300. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.6 S2-2104543 CR Approval 23.501 CR2811R3 (Rel-17, 'B'): Introducing threshold conditions for priority-based steering mode in TS 23.501 Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Motorola Mobility, [Huawei, Hisilicon] Rel-17 Revision of (Agreed) S2-2103300. Noted Rainer (Nokia) comments.
Myungjune (LGE) comments.
Hualin(Huawei) replied to Rainer (Nokia).
Hualin(Huawei) replied to Myungjune (LGE).
Myungjune (LGE) replies to Hualin (Huawei).
DongYeon (Samsung) comments.
Stefan (Ericsson) shares the concern of previous comments
Hualin(Huawei) provide r01 based on the comments.
==== 8.X, 9.X Revisions Deadline ====
Myungjune (LGE) provides further comments.
Myungjune(LGE) responses to Hualin (Huawei).
Apostolis (Lenovo) comments.
Rainer (Nokia) proposes to note 4543.
Spencer (Tencent) comments about the redefinition of active-standby for Rel-17.
Myungjune (LGE) replies and proposes to note this paper.
Stefan (Ericsson) also proposes to note
==== 8.X, 9.X Final Deadline ====
Noted
8.6 - - - Partial ATSSS rule update - - Docs:=4 -
8.6 S2-2104073 CR Approval 23.501 CR2886 (Rel-17, 'B'): Partial ATSSS rule update by using ATSSS rule ID LG Electronics Rel-17 CC#5: r07 agreed. Revised to S2-2105198. Rainer (Nokia) asks for clarification.
Myungjune (LGE) replies to Rainer (Nokia).
Rainer (Nokia) replies.
Myungjune (LGE) replies to Rainer (Nokia) and provides r01.
Rainer (Nokia) replies to Apostolis (Lenovo).
Apostolis (Lenovo) provides more comments.
Hualin(Huawei) comments.
Myungjune (LGE) replies to Hualin (Huawei).
Stefan (Ericsson) provides comments and r02
Apostolis (Lenovo) supports r02 and wants to co-sign r02.
Rainer (Nokia) provides r04.
Apostolis (Lenovo) provides r05.
Spencer (Tencent) would like to co-sign S2-2104073r05, and asks a question.
Myungjune (LGE) replies to Spencer (Tencent).
DongYeon (Samsung) provides r06 and comments.
Myungjune (LGE) provides r07.
Hualin(Huawei) replied to Myungjune (LGE)
Spencer (Tencent) replies to Myungjune (LGE) and confirms desire to cosign.
Dario S. Tonesi (Qualcomm) ask questions for clarification
==== 8.X, 9.X Revisions Deadline ====
Myungjune (LGE) replies to Dario S. Tonesi (Qualcomm).
Dario S. Tonesi (Qualcomm) raises questions due to discussion in CT1 that proposes to introduce ATSSS Rule ID in Rel-16. Ask if we should discuss this in CC#4.
DongYeon (Samsung) supports r07.
Apostolis (Lenovo) supports r07.
Hualin(Huawei) object to this paper and propose to note.
Apostolis (Lenovo) proposes to mark this 'for CC#4'.
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2105198 CR Approval 23.501 CR2886R1 (Rel-17, 'B'): Partial ATSSS rule update by using ATSSS rule ID LG Electronics Rel-17 Revision of S2-2104073r07. Approved Agreed
8.6 S2-2104074 CR Approval 23.502 CR2765 (Rel-17, 'B'): Partial ATSSS rule update capability LG Electronics Rel-17 r03 agreed. Revised to S2-2105132. Myungjune (LGE) provides r01.
DongYeon (Samsung) provides r02.
Myungjune (LGE) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) raises questions due to discussion in CT1 that proposes to introduce ATSSS Rule ID in Rel-16. Ask if we should discuss this in CC#4.
DongYeon (Samsung) supports r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.6 S2-2105132 CR Approval 23.502 CR2765R1 (Rel-17, 'B'): Partial ATSSS rule update capability LG Electronics Rel-17 Revision of S2-2104074r03. Approved Agreed
8.6 - - - Support for MA PDU sessions with 3GPP access leg over EPC and a non-3GPP access leg over 5GC - - Docs:=1 -
8.6 S2-2104005 CR Approval 23.316 CR2056R1 (Rel-17, 'B'): MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC Nokia, Nokia Shanghai Bell, Bell, Deutsche Telekom, Ericsson, InterDigital, Rel-17 Revision of (Endorsed at S2#143E) S2-2100076. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.7 - - - Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) - - Docs:=57 -
8.7 S2-2103730 LS In Action LS from GSMA-ACJA: Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM GSMA-ACJA (GSMA-ACJA LS 3GPP SA2 Authentication) Response drafted in S2-2103781. Final response in S2-2104895 Replied to
8.7 S2-2103784 LS OUT Approval [DRAFT] Reply LS on Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM Qualcomm Technologies Ireland Rel-17 Response to S2-2103730. Revised to S2-2104895.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104895 LS OUT Approval Reply LS on Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM SA WG2 Rel-17 Revision of S2-2103784. Approved Approved
8.7 S2-2103731 LS In Information LS from GSMA-ACJA: 3GPP SA1 clarifications on problematic UAV GSMA-ACJA (GSMA-ACJA LS 3GPP SA2 S1-210359) Response drafted in S2-2103782. Postponed Postponed
8.7 S2-2103783 LS OUT Approval [DRAFT] Reply LS to GSMA-ACJA and SA WG1. Clarifications on problematic UAV Qualcomm Technologies Ireland Rel-17 Response to S2-2103731. r02 agreed. Revised to S2-2104916. Pallab (Nokia) comments
Stefano (Qualcomm) provides R01 based on Pallab's comments.
Pallab (Nokia) provides r02 with corrected SA2 meeting dates
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104916 LS OUT Approval Reply LS to GSMA-ACJA: 3GPP SA WG1 clarifications on problematic UAV SA WG2 Rel-17 Revision of S2-2103783r02. Approved Approved
8.7 S2-2103776 P-CR Approval 23.256: TS 23.256: General ENs Cleanup. Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2103777 P-CR Approval 23.256: TS 23.256: General Clarifications and Alignments. Qualcomm Incorporated Rel-17 r03 agreed. Revised to S2-2104917. Tricci (OPPO) provides minor editorial comment and adds OPPO as the supporting company in r01.
Shabnam (Ericsson) provides r02 and prefer more the positive wording of what is supported and also prefers this as a NOTE.
Stefano (Qualcomm) thanks Ericsson for r02 and provides r03 to correct left over text.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104917 P-CR Approval 23.256: TS 23.256: General Clarifications and Alignments. Qualcomm Incorporated Rel-17 Revision of S2-2103777r03. Approved Approved
8.7 S2-2103778 P-CR Approval 23.256: TS 23.256: Clarifications on reference points. Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2103779 P-CR Approval 23.256: TS 23.256: UUAA-MM Clarifications. Qualcomm Incorporated Rel-17 r06 agreed. Revised to S2-2104918, merging S2-2103923 Tricci (OPPO) asks for clarifications for 3779 and then we can decide how to merge with 3923.
Stefano (Qualcomm) welcomes a merger and replies.
Tricci (OPPO) thanks Stefano (Qualcomm) for his clarifications and proposed to merge OPPO's 3923 into QC's 3779 with changes highlighted in yellow.
DongYeon (Samsung) provides r02 which corrects a typo.
Pallab (Nokia) provides r03.
Guanzhou (InterDigital) points out previous revisions are incorrect to put UUAA result inside transparent UUAA auth payload. And provide r04.
Stefano (Qualcomm) provides r05, indicating the result needs to be in the payload and, as IDCC states, also outside.
Guanzhou (InterDigital) provides r06 to remove one change in r04 to avoid clashes with 4110.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) OK with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104918 P-CR Approval 23.256: TS 23.256: UUAA-MM Clarifications. Qualcomm Incorporated Rel-17 Revision of S2-2103779r06, merging S2-2103923. Approved Approved
8.7 S2-2103780 P-CR Approval 23.256: TS 23.256: UUAA-SM Clarifications. Qualcomm Incorporated Rel-17 Merged into S2-2105159 Pallab (Nokia) request to merge the changes proposed in this paper with 4110
Stefano (Qualcomm) suggests to consider 3780 merged in 4110r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2103781 P-CR Approval 23.256: TS 23.256: C2 Authorization Clarifications. Qualcomm Incorporated Rel-17 r02 agreed. Revised to S2-2104919. Guanzhou (InterDigital) provides r01.
Stefano (Qualcomm) asks for clarifications.
Weijun (Huawei) provides r02.
Guanzhou (InterDigital) responds to Stefano's (Qualcomm) comments.
Stefano (Qualcomm) cannot accept the revision maintaining the security information until questions are answered.
Guanzhou (InterDigital) further comments.
Stefano (Qualcomm) replies to comments, states we cannot accept r01 or r02, and provides r03 to adopt Huawei's changes in R02.
==== 8.X, 9.X Revisions Deadline ====
Stefano (Qualcomm) states we are amenable to accept r02 for the sake of progress, even if technically it makes no sense to have completely undefined (with neither examples nor requirements from the aviation industry) information carried in the IEs.
==== 8.X, 9.X Final Deadline ====
Guanzhou (InterDigital) asks Stefano(Qualcomm) to clarify the position.
Stefano (Qualcomm) replies.
Guanzhou (InterDigital) replies.
Weijun (Huawei) clarifies that r02 was revised based on r00.
Revised
8.7 S2-2104919 P-CR Approval 23.256: TS 23.256: C2 Authorization Clarifications. Qualcomm Incorporated Rel-17 Revision of S2-2103781r02. Approved Approved
8.7 S2-2103795 P-CR Approval 23.256: TS 23.256: Correction to Unknown UAV Tracking . Qualcomm Incorporated Rel-17 r03 agreed. Revised to S2-2104920. Tricci (OPPO) provides r01 to remove the EN and adds OPPO as the supporting company.
Guanzhou (InterDigital) would like to co-sign and provides r02.
Pallab (Nokia) provides r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104920 P-CR Approval 23.256: TS 23.256: Correction to Unknown UAV Tracking . Qualcomm Incorporated Rel-17 Revision of S2-2103795r03. Approved Approved
8.7 S2-2103797 P-CR Approval 23.256: TS 23.256: UAV-UE terminology clarification. Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2103867 P-CR Approval 23.256: Resolving ENs in clause 5.2.3. Ericsson Rel-17 Merged into S2-2105159 Stefano (Qualcomm) suggests to consider 3867 merged into 4110r02, thanking Ericsson for the merger.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2103868 P-CR Approval 23.256: USS initiated C2 Authorization. Ericsson Rel-17 CC#4: This was left for CC#5. CC#5: This was postponed. Tricci (OPPO) asks for clarifications.
Shabnam (Ericsson) provides response as well as r01.
Tricci (OPPO) thanks Shabnam (Ericsson) for her clarifications and providing r01, OPPO also agrees with Ericsson that, there would be an common issue for UUAA-MM scenario when USS assigns 'new' CAA-Level UAV ID during the PDU Session Establishment/Modification after successful UUAA-MM.
Dimitris (Lenovo) includes questions for clarification
Shabnam (Ericsson) responds in line.
Dimitris (Lenovo) provides additional comments
Pallab (Nokia) requests for clarification
Guanzhou (InterDigital) questions the necessity of USS-initiated C2 authorization and the technical feasibility of using Nnef_AFsessionWithQoS_Create for this purpose.
Shabnam (Ericsson) provides response as well as r02.
Pallab (Nokia) provides r03.
Shabnam (Ericsson) thanks Pallab for good updates and accepts r03.
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange): There's something that looks inconsistent in the flows.
Guanzhou (InterDigital) reiterates that an alternative procedure is not needed and objects to all versions of 3868.
Shabnam (Ericsson) proposes to discuss in CC#4 a revision to address the inconsistencies and errors found and proposal from Nokia below.
Guanzhou (InterDigital) asks Stefano why this forces exception?
==== 8.X, 9.X Final Deadline ====
Postponed
8.7 S2-2103869 P-CR Approval 23.256: PDU Session Establishment/Modification use for authorization. Ericsson Rel-17 CC#4: This was left for CC#5. CC#5: Postponed Guanzhou (InterDigital) asks for clarification.
Shabnam (Ericsson) provides response in line.
Guanzhou (InterDigital) responds to Shabnam(Ericsson) comment.
Pallab (Nokia) agrees with Guanzhou (InterDigital) and proposes to NOTE the paper
Shabnam (Ericsson) responds to Nokia and Interdigital comments
Pallab (Nokia) replies to Shabnam (Ericsson)
Shabnam (Ericsson) provides r01, instead of EN now provides the actual procedure update so please check.
Pallab (Nokia) provides r02.
Dimitris (Lenovo) provides r03 and comments
Stefano (QUalcomm) provides r04 to improve readability and align the proposed text with the explanation in the introduction.
Guanzhou (InterDigital) has concerns on the new changes.
Shabnam (Ericsson) it is addressing an issue and from that soln we see we can address common procedures.
Guanzhou (InterDigital) further comments.
Pallab (Nokia) provides r05.
Weijun (Huawei) proposes to NOTE this pCR.
Shabnam (Ericsson) agrees with r05 and provides response to Interdigital comments and request Huawei and Interdigital to reconsider based on the issues we are facing.
Stefano (Qualcomm) supports r05 and request Huawei and Interdigital to reconsider since the technical issues raised are valid.
Guanzhou (InterDigital) asks again what technical issues are valid.
Shabnam (Ericsson) does not see any issues that are stopping the proposal being valid? Comments
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) provides some text from the TR conclusion, since we have been referring to it. Believes the proposal in 3869 was also agreed in study phase as an option.
Guanzhou (InterDigital) responds to comments and points out the additional issues of the proposed procedure. And objects to all versions of 3869.
Shabnam (Ericsson) provides feedback, acknowledges requires some correction/clarification, proposes to take it at CC#4 with revision addressing comments.
Guanzhou (InterDigital) comments.
Shabnam (Ericsson) responds, also see revisions.
Weijun (Huawei) shares Guanzhou (InterDigital)'s view to postpone or note this pCR.
==== 8.X, 9.X Final Deadline ====
Postponed
8.7 S2-2103915 CR Approval 23.501 CR2870 (Rel-17, 'B'): UAV support feature inclusion Ericsson Rel-17 r03 agreed. Revised to S2-2104921. Runze (Huawei) provides r01.
Shabnam (Ericsson) provides r02 cleaning up the text proposal and changing UAS AF to UAS NF.
Runze (Huawei ) identified a typo in r02 and provides r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104921 CR Approval 23.501 CR2870R1 (Rel-17, 'B'): UAV support feature inclusion Ericsson Rel-17 Revision of S2-2103915r03. Approved Agreed
8.7 S2-2103918 DISCUSSION Agreement Proposal for generic handling of UAS status coordination between AMF & UAS NF. OPPO Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2103919 P-CR Approval 23.256: TS 23.256: Generic handling of UAS status alignment between AMF and UAS NF. OPPO Rel-17 Noted Stefano (Qualcomm) proposes removing changes to UE/UAV terminology to allow those to be in 3797 and asks a clarification
Tricci (OPPO) agrees with Stefano (Qualcomm) to clean up the UE/UAV terminology in 3919, and responds to QC's question.
Pallab (Nokia) requests for clarification
Guanzhou (InterDigital) comments and proposes to merge with 4407.
Tricci (OPPO) responds to Pallab (Nokia) questions.
Tricci (OPPO) responds to Guanzhou (InterDigital) comments and would like to ask for clarifications.
Pallab (Nokia) comments and requests for further clarification
Tricci (OPPO) thanks to Pallab (Nokia) for the detailed feedback and provides further responses.
Pallab (Nokia) asks further questions and feels that the proposed solution is not needed
Shabnam (Ericsson) comments and also does not agree to the proposal.
Tricci (OPPO) thanks to Pallab (Nokia) and Shadnam (Ericsson) feedbacks and asks for more careful considerations.
Pallab (Nokia) clarifies further on the reason for not needing a solution here.
Tricci (OPPO) responds to Pallab (Nokia) and has trouble to understand Nokia's comments, hence, would like to ask for clarifications.
Pallab (Nokia) responds to Tricci (OPPO)
Tricci (OPPO) responds to Pallab (Nokia) proposes to note 3919 and 4407 for this meeting and to address the EN in the next Aug. SA2#146E meeting.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2103920 CR Approval 23.502 CR2750 (Rel-17, 'B'): Extension to AMF EventExposure for Service Access Status Update for UAS OPPO Rel-17 Noted Pallab (Nokia) objects this CR. This new event monitoring is not needed as discussed in 3919
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2103921 P-CR Approval 23.256: TS 23.256: ENs clean up for clauses 5.2.2.1 and 5.2.2.2. OPPO, Qualcomm Rel-17 r01 agreed. Revised to S2-2104922. Shabnam (Ericsson) questions the use of UAV vs UE in this pCR, in our view the NAS procedures of 3GPP is UE function and not UAV, r01 provided with some updates highlighted in Green.
Tricci (OPPO) thanks Shabnam (Ericsson) for the clean up and accept r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104922 P-CR Approval 23.256: TS 23.256: ENs clean up for clauses 5.2.2.1 and 5.2.2.2. OPPO, Qualcomm Rel-17 Revision of S2-2103921r01. Approved Approved
8.7 S2-2103922 P-CR Approval 23.256: TS 23.256: AMF Mobility Event Exposure support for UAS . OPPO, Qualcomm, InterDigital Rel-17 r02 agreed. Revised to S2-2104923. Stefano (Qualcomm) suggests a way forward to reconcile with Nokia's 4105 and indicates no conflict with 3779 and 3780
Pallab (Nokia) responds to Stefano (Qualcomm) and requests for clarification.
Stefano (Qualcomm) replies to Nokia
Tricci (OPPO) responds Pallab (Nokia) and provides r01 to clarify the AMF Mobility Exposure Event with Reachability Filter Event ID.
Pallab (Nokia) clarifies to Stefano (Qualcomm).
Stefano (Qualcomm) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104923 P-CR Approval 23.256: TS 23.256: AMF Mobility Event Exposure support for UAS . OPPO, Qualcomm, InterDigital Rel-17 Revision of S2-2103922r02. Approved Approved
8.7 S2-2103923 P-CR Approval 23.256: TS 23.256: Clarification for UUAA Aviation Payload and UUAA Authorization Payload. OPPO Rel-17 Merged into S2-2104918 Pallab (Nokia) points out that this pCR needs to be aligned with the latest revision of 4110
Tricci (OPPO) responds to Pallab (Nokia) that this PCR is actually overlapped with QC's 3779 and 3923 has been merged into 3779. Please check.
Pallab (Nokia) thanks Tricci (OPPO) for confirming the merge of this pCR into 3779
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2104104 P-CR Approval 23.256: TS 23.256: Updates to procedure for UAV location reporting. Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.7 S2-2104105 P-CR Approval 23.256: TS 23.256: Updates to UUAA-MM and UUAA-SM procedure. Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2104924. Stefano (Qualcomm) suggests a way forward to reconcile with Oppo's 3922 and indicates no conflict with 3779 and 3780
Tricci (OPPO) asks for clarifications.
Tricci (OPPO) provides r01 to suggest clarifications and adds OPPO as the supporting company.
Pallab (Nokia) is OK with r01 and thanks Tricci (OPPO) for supporting.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) proposes to approve r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104924 P-CR Approval 23.256: TS 23.256: Updates to UUAA-MM and UUAA-SM procedure. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104105r01. Approved Approved
8.7 S2-2104110 P-CR Approval 23.256: TS 23.256: Generic IE names for UUAA-SM. Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated Rel-17 CC#4: r02 agreed. Revised to S2-2105159, merging S2-2103780 and S2-2103867. Stefano (Qualcomm) provides r01 merging in 3780.
Shabnam (Ericsson) provides r02 merging in 3867, adding missing function in consultation with Qualcomm and Nokia.
==== 8.X, 9.X Revisions Deadline ====
Pallab (Nokia) thanks Stefano (Qualcomm) and Shabnam (Ericsson) for the merger and proposes to approve r02.
Shabnam (Ericsson) asks to take it to CC#4 as a minor mistake on step numbering was found.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2105159 P-CR Approval 23.256: TS 23.256: Generic IE names for UUAA-SM. Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated Rel-17 Revision of S2-2104110r02, merging S2-2103780 and S2-2103867. CC#4: Approved Approved
8.7 S2-2104111 P-CR Approval 23.256: TS 23.256: Updates to presence monitoring procedure. Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2104925. DongYeon (Samsung) provides r01.
Pallab (Nokia) responds to DongYeon (Samsung) and provides r02
DongYeon (Samsung) is fine with r02, and asks a question.
DongYeon (Samsung) is fine with r02.
Pallab (Nokia) tries to clarify.
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) replies, continues to agree to r02.
Pallab (Nokia) thanks DongYeon (Samsung) for confirming and proposes to approve r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104925 P-CR Approval 23.256: TS 23.256: Updates to presence monitoring procedure. Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104111r02. Approved Approved
8.7 S2-2104161 P-CR Approval 23.256: Clarifications on one EN and one NOTE in the TS 23.256. China Mobile Rel-17 r01 agreed. Revised to S2-2104926. Shabnam (Ericsson) first change is already covered in merged 4110 and prefer that change, so removed that change. r01 provided.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104926 P-CR Approval 23.256: Clarifications on one EN and one NOTE in the TS 23.256. China Mobile Rel-17 Revision of S2-2104161r01. Approved Approved
8.7 S2-2104201 P-CR Approval 23.256: TS23.256: Updates to UUAA-MM with EN resolve. vivo Rel-17 r01 agreed. Revised to S2-2104927. Stefano (Qualcomm) proposes r01 due to conflict with 3779 (both r00 and r05).
==== 8.X, 9.X Revisions Deadline ====
Wen(vivo) responds to Stefano (Qualcomm) and can live with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104927 P-CR Approval 23.256: TS23.256: Updates to UUAA-MM with EN resolve. vivo Rel-17 Revision of S2-2104201r01. Approved Approved
8.7 S2-2104401 P-CR Approval 23.256: TS 23.256: UAV Controller Replacement. InterDigital, Orange, Nokia, Nokia Shanghai Bell Rel-17 Noted Dimitris (Lenovo) points that there is an alternative proposal in S2-2104568. Requests clarifications
Guanzhou (InterDigital) replies Dimitris(Lenovo)'s questions.
Shabnam (Ericsson) prefers 4568 from Lenovo, proposes to take 4568 as the baseline.
Stefano (Qualcomm) also suggests to take the revised version of 4568 as the baseline.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2104402 P-CR Approval 23.256: TS2 3.256: Using C2 communication indication for C2 authorization. InterDigital Rel-17 Merged into S2-2105160 Pallab (Nokia) gives same comments as in 4530. Please check the comments in 4530
Stefano (Qualcomm) cannot accept r0 of 4402 and prefer to use 4530 as the baseline.
Guanzhou (InterDigital) kindly asks Stefano (Qualcomm) to explain the concern.
Shabnam (Ericsson) proposes this pCR to be merged with 4530 which includes corrections that are more precise and includes more updates.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.7 S2-2104407 P-CR Approval 23.256: TS 23.256: Service Availability Event exposure to USS. InterDigital Rel-17 Noted Guanzhou (InterDigital) provides r01
Pallab (Nokia) provides similar comments as 3919 and requests for clarification.
Guanzhou (InterDigital) responds to Pallab (Nokia)'s comments.
Tricci (OPPO) asks for clarifications.
Pallab (Nokia) comments and seeks further clarification.
Shabnam (Ericsson) has same concerns as for tdoc 3919 and objects to this pCR, we can continue further discussion under 3919 if desired.
Pallab (Nokia) responds to Guanzhou (InterDigital) and also suggests to NOTE the paper
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2104410 CR Approval 23.502 CR2817 (Rel-17, 'B'): Service Availability event InterDigital Rel-17 Noted Shabnam (Ericsson) objects to adding new service availability events not related to this work as these were not part of the study conclusion nor needed. Reuse existing handling.
Pallab (Nokia) also objects to this pCR as per discussion in 3919, 4407
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.7 S2-2104435 P-CR Approval 23.256: NF service and service operations for UAS. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2104928. Pallab (Nokia) provides r01
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) supports r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104928 P-CR Approval 23.256: NF service and service operations for UAS. Huawei, HiSilicon Rel-17 Revision of S2-2104435r01. Approved Approved
8.7 S2-2104436 P-CR Approval 23.256: Clarification on terms related to UAV communication. Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2104929. Stefano (Qualcomm) suggests to note the paper or to accept the suggested change due to a deviation from TR assumptions and conclusions.
Weijun Xing (Huawei) responds to Stefano (Qualcomm).
Tricci (OPPO) asks for clarification.
Weijun Xing (Huawei) responds to Tricci (OPPO).
Tricci (OPPO) thanks Weijun (Huawei) clarification.
Weijun Xing (Huawei) responds to Tricci (OPPO) and provides r02.
Tricci (OPPO) thanks Weijun (Huawei) update.
Pallab (Nokia) feels that the paper is causing more confusion than to clarify. Supports the view from Stefano (Qualcomm) to NOTE the paper.
Weijun Xing (Huawei) responds to Pallab (Nokia).
Pallab (Nokia) responds to Weijun.
Weijun (Huawei) accepts Pallab's (Nokia) suggestion and provides r03.
Pallab (Nokia) provides further comments.
Stefano (Qualcomm) provides r04.
Weijun (Huawei) is fine with r04.
Pallab (Nokia) responds to Stefano (Qualcomm) and provides r05
Tricci (OPPO) thanks Stefano to summarize the issues and would prefer option 3).
Guanzhou (InterDigital) comments on Stefano's question and proposed options.
Stefano (Qualcomm) provides r06.
Stefano (Qualcomm) replies to Huawei.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104929 P-CR Approval 23.256: Clarification on terms related to UAV communication. Huawei, HiSilicon Rel-17 Revision of S2-2104436r06. Approved Approved
8.7 S2-2104437 P-CR Approval 23.256: UUAA procedure with network provided UAV location. Huawei, HiSilicon Rel-17 r06 agreed. Revised to S2-2104930. Pallab (Nokia) objects to original version of the Tdoc and provides r01.
DongYeon (Samsung) asks a question and comment.
Pallab (Nokia) provides r02.
Runze (Huawei) provides r03.
Pallab (Nokia) OK with r03.
DongYeon (Samsung) provides r04.
Guanzhou (InterDigital) supports the change and thinks it should cover C2 auth procedure for completeness. R06 is provided with co-signing.
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) supports r06.
DongYeon (Samsung) supports r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104930 P-CR Approval 23.256: UUAA procedure with network provided UAV location. Huawei, HiSilicon Rel-17 Revision of S2-2104437r06. Approved Approved
8.7 S2-2104445 P-CR Approval 23.256: Clarification on UAV establishing a normal PDU session. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104931. Pallab (Nokia) provides comments and requests for clarification.
Runze (Huawei) replies to Pallab, and provides r01.
Pallab (Nokia) responds to Runze (Huawei) and provides r02.
Shabnam (Ericsson) provides r03, removing/rephrasing normative text in a NOTE.
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) supports r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.7 S2-2104931 P-CR Approval 23.256: Clarification on UAV establishing a normal PDU session. Huawei, HiSilicon Rel-17 Revision of S2-2104445r03. Approved Approved
8.7 S2-2104530 P-CR Approval 23.256: C2 authorization clarifications. Lenovo, Motorola Mobility, Qualcomm Incorporated Rel-17 CC#4: r03 with changes agreed. Revised to S2-2105160, merging S2-2104402. Pallab (Nokia) comments.
Dimitris (Lenovo) provides responses.
Guanzhou (InterDigital) comments.
Dimitris (Lenovo) responds to Guanzhou (InterDigital)
Pallab (Nokia) provides further comments
Dimitris (Lenovo) responds to Pallab (Nokia)
Guanzhou (InterDigital) shares the concerns raised by Pallab(Nokia) and repeats that pairing info configuration at UAV is not mandatory.
Pallab (Nokia) responds to Dimitris (Lenovo).
Dimitris (Lenovo) provides r01
Guanzhou (InterDigital) proposes to merge this into 4402.
Guanzhou (InterDigital) comments on Pallab (Nokia) question.
Pallab (Nokia) responds to Guanzhou (InterDigital)comments
Guanzhou (InterDigital) responds to Pallab (Nokia) comment.
Guanzhou (InterDigital) provides additional comments to Pallab (Nokia).
Pallab (Nokia) responds to Guanzhou (InterDigital).
Pallab (Nokia) points out that changes proposed in this pCR needs alignment with changes proposed in 3869
Dimitris (Lenovo) provides r02
Shabnam (Ericsson) comments and asks for clarification.
Dimitris (Lenovo) responds to Shabnam (Ericsson)
Stefano (Qualcomm) asks Lenovo to submit another revision addressing the clash highlighted by Nokia and addressing Ericsson's comment.
Dimitris (Lenovo) provides r03
Guanzhou (InterDigital) resends r04.
==== 8.X, 9.X Revisions Deadline ====
Guanzhou (InterDigital) resends r04 again and asks to consider it valid.
Stefano (Qualcomm) after further review, cannot accept r04 due to mistakes in correcting non-existing conflicts.
Stefano (Qualcomm) expresses concerns that r04 is not based on r03.
Guanzhou (InterDigital) provides r04.
Weijun (Huawei) asks for clarification.
Guanzhou(InterDigital) thanks Stefano(Qualcomm) for willing to consider r04 and responds to comments.
Stefano (Qualcomm) replies to Weijun (Huawei), admitting there is an issue with text version, but no issue in the end..
Dimitris (Lenovo) responds to Weijun (Huawei)
Guanzhou(InterDigital) shares r05 in ./inbox/drafts folder.
Dimitris (Lenovo) makes a variation of r05 proposal
Guanzhou(InterDigital) responds to Dimitris(Lenovo).
==== 8.X, 9.X Final Deadline ====
Guanzhou(InterDigital) asks to take this to CC#4 to see if late r05 can be accepted.
Revised
8.7 S2-2105160 P-CR Approval 23.256: C2 authorization clarifications. Lenovo, Motorola Mobility, Qualcomm Incorporated Rel-17 Revision of S2-2104530r03 with changes, merging S2-2104402. CC#4: Approved Approved
8.7 S2-2104568 P-CR Approval 23.256: UAV-C replacement procedure. Lenovo, Motorola Mobility Rel-17 CC#4: This was left for CC#5. CC#5: This was postponed. Guanzhou (InterDigital) asks for clarification.
Dimitris (Lenovo) responds
Weijun (Huawei) asks for clarification.
Pallab (Nokia) provides comments
Dimitris (Lenovo) provides r01 which is based in principle on the USS-initiated PDU session modification proposal in 3869
Guanzhou (InterDigital) objects to all versions of 4568.
Stefano (Qualcomm) clarifies this will cause an exception most probably and disagree with technical comment.
Pallab (Nokia) comments and provides r02
Weijun (Huawei) provides r03
Pallab (Nokia) raises concern with r03 and requests for clarification
Dimitris (Lenovo) comments on r02
Pallab (Nokia) responds to Dimitris (Lenovo)
Shabnam (Ericsson) shares Nokia view as well, r02 approach provides more graceful handling than revoke.
Dimitris (Lenovo) is OK with r02
Antoine (Orange) provides a question and comments on r02.
Pallab (Nokia) responds to Antoine (Orange).
Guanzhou (InterDigital) responds to (Qualcomm) comment
==== 8.X, 9.X Revisions Deadline ====
Antoine (Orange) replies to Pallab.
Guanzhou (InterDigital) reiterates objection to all versions of 4568.
Dimtiris (Lenovo) responds to the objections of InterDigital does not see issues
Antoine (Orange) can agree to r02 with the understanding that the useless condition 'If the PCF determines that the SMF needs updated policy information' in step 4 will be removed at the next meeting.
Pallab (Nokia) points out that 4568-r02 is aligned with the proposals in 3868 and 3869, and hence shall be agreed only if the related papers are agreed in CC#4. Proposes to mark this also for CC#4 and provide a revision (based on r02) in CC#4 to cover comment from Antoine (Orange). We object to r00, r01 and r03.
Dimitris (Lenovo) includes an additional revision in the drafts folder for consideration in CC#4
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 - - - System enhancement for Proximity based Services in 5GS (5G_ProSe) - - Docs:=118 -
8.8 S2-2104102 WORK PLAN Information 5G_ProSe work plan CATT (Rapporteur) Rel-17 Noted Deng Qiang (CATT) the work plan is for information and can be marked as NOTED.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - LS IN - - Docs:=1 -
8.8 S2-2103771 LS In Action LS from RAN WG2: LS on discovery and relay (re)selection RAN WG2 (R2-2104649) Rel-17 Response drafted in S2-2104479. Postponed Fei (OPPO) comments
Deng Qiang (CATT) comments.
Fei (OPPO) reponds to Deng Qiang (CATT).
Judy (Ericsson) comments
Wen (vivo) comments
Hong (Qualcomm) comments.
Xiaoyan Shi (Interdigital) comments.
Fei (OPPO) comments.
Fei (OPPO) responds to Wen (vivo) and Judy (Ericsson)
Wen (vivo) responds to Fei (OPPO)
Fei (OPPO) responds to Wen (vivo).
Judy (Ericsson) responds
Postponed
8.8 - - - LS OUT - - Docs:=4 -
8.8 S2-2104479 LS OUT Approval [DRAFT] Reply LS on discovery and relay (re)selection OPPO Rel-17 Response to S2-2103771. Noted Sherry (Xiaomi) provides r01.
Sherry (Xiaomi) asked a further question.
Fei (OPPO) responds to Sherry (Xiaomi)
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) reminds this LS depends on outcome of related papers.
Deng Qiang (CATT) asks to NOTED this LS.
Sherry (Xiaomi) can accept r01, but if the related CRs are not approved, it can be postponed.
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104103 LS OUT Approval LS on RAN dependency issues for 5G ProSe CATT Rel-17 r02 agreed. Revised to S2-2104932. Steve (Huawei) asks for clarifications
Deng Qiang (CATT) replies to Steve (Huawei).
Fei (OPPO) comments.
Deng Qiang (CATT) provides r01 by adding some background information.
Fei (OPPO) provides r02.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is fine with r02.
Steve (Huawei) thanks for the clarifications, I am ok with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104932 LS OUT Approval LS on RAN dependency issues for 5G ProSe SA WG2 Rel-17 Revision of S2-2104103r02. Approved Approved
8.8 S2-2104564 LS OUT Approval [DRAFT] LS out on 5G ProSe security procedures Nokia, Nokia Shanghai Bell Rel-17 Noted Steve (Huawei) waiting for SA3 is fine as for S2-2104563 on which it depends.
Deng Qiang (CATT) shares the same view with Steve (Huawei) and proposed to NOTED this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - ProSe service identifier - - Docs:=4 -
8.8 S2-2104205 P-CR Approval 23.304: TS 23.304: EN resolve of how to identify ProSe services. vivo Rel-17 Merged into S2-2104555 (Postponed) Deng Qiang (CATT) proposed this paper to be merged into S2-2104555 per offline discussion.
Wen (vivo) confirms this paper is merged into S2-2104555.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104555 P-CR Approval 23.304: Identification of ProSe service for Path Selection. Apple Rel-17 Postponed Sherry (Xiaomi) comments.
Judy (Ericsson) comments
Sudeep (Apple) responds.
Mehrdad (Samsung) cannot agree with option 1.
Changhong (Intel) doesn't think we are ready to solve the issue at this meeting and asks to postpone this paper before we have a clear idea.
Deng Qiang (CATT) comments and prefers option 2.
Mehrdad (Samsung) comments.
Sudeep (Apple) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) asks to postpone the paper.
Mehrdad (Samsung) is OK to postpone this paper.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104583 P-CR Approval 23.304: Clarification on ProSe Service Type. Samsung Rel-17 Postponed Changhong (Intel) comments.
Judy (Ericsson) comments
Mehrdad (Samsung) replies to Ericsson and Intel
Changhong (Intel) replies to Mehrdad (Samsung).
Mehrdad (Samsung) clarifies to Changhong (Intel) that the current wording of the spec is not correct.
Sudeep (Apple) provides r01.
Deng Qiang (CATT) r01 looks fine at this stage.
Sherry (Xiaomi) comments.
Mehrdad (Samsung) clarifies for Xiaomi and provides r02.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) asks to postpone the paper.
Mehrdad (Samsung) is OK to postpone this paper.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104668 P-CR Approval 23.304: TS 23.304: Identification of ProSe service for path selection. Xiaomi Rel-17 Merged into S2-2104555 (Postponed) Deng Qiang (CATT) proposed this paper to be merged into S2-2104555 per offline discussion.
Sherry (Xiaomi) agrees that this paper is merged into S2-2104555 per offline discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 - - - ProSe UE capabilities - - Docs:=5 -
8.8 S2-2103753 P-CR Approval 23.304: Capability for L3 U2N relay with N3IWF and UE capability to PCF. OPPO Rel-17 Merged into S2-2104933 Fei (OPPO) provides r01.
Steve (Huawei) comments
Hong (Qualcomm) comments.
Hong (Qualcomm) response to Steve.
Fei (OPPO) responds to Steve (Huawei).
Changhong (Intel) comments and especially disagrees with the first change.
Fei (OPPO) responds to ChangHong (Intel) on the first change.
Changhong (Intel) objects to r01 and r00, and provides r02.
Changhong (Intel) proposes to merge this paper into S2-2104106.
Deng Qiang (CATT) asks whether this paper can be merged into S2-2104106r02.
Fei (OPPO) responds and OK to merge it into S2-2104106
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104035 P-CR Approval 23.304: 5G ProSe Capability Usage by PCF. Intel Rel-17 Approved LaeYoung (LGE) thinks that adding '5G' makes wording mis-alignment with terms in clause 3.1 as well as with other parts in the TS.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) clarifies that she commented just about terminologies, so, is fine to approve this pCR.
Fei (OPPO) responds to LaeYoung and '5G' in this PCR will not be implemented to the TS.
LaeYoung (LGE) is fine with suggestion from Fei (OPPO). Anyhow, '5G ProSe Capability' is fine because this term is already in the TS. :)
Tao(VC): Let's Check whether r00 can be agreed then. If r00 approved, the '5G' will not implemented to the TS.
Changhong (Intel) replies and asks Tao a question.
LaeYoung (LGE) replies to Changhong (Intel).
Changhong (Intel) replies to LaeYoung.
LaeYoung (LGE) responds to Changhong (Intel).
Fei (OPPO) responds to LaeYoung and Changhong,
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104106 P-CR Approval 23.304: TS 23.304: Clarifications on UE capabilities. CATT Rel-17 r03 agreed. Revised to S2-2104933, merging S2-2103753 and S2-2104203 Changhong (Intel) comments and provides r01.
Wen (vivo) comments on r01.
Changhong replies to Wen.
Deng Qiang (CATT) replies to Changhong (Intel).
Deng Qiang (CATT) provides r02.
Fei (OPPO) provides r03.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is ok with r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104933 P-CR Approval 23.304: TS 23.304: Clarifications on UE capabilities. CATT Rel-17 Revision of S2-2104106r03, merging S2-2103753 and S2-2104203. Approved Approved
8.8 S2-2104203 P-CR Approval 23.304: TS 23.304: EN resolve for L3 relay capability with N3IWF. vivo Rel-17 Merged into S2-2104933 Fei (OPPO) proposes to merge S2-2104203 into S2-2103753
Wen (vivo) is ok to merge.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 - - - Identifiers for Direct Discovery - - Docs:=21 -
8.8 S2-2103755 P-CR Approval 23.304: Additional IDs in discovery message for relay. OPPO Rel-17 Postponed Deng Qiang (CATT) comments.
Fei (OPPO) responds.
Judy (Ericsson) comments this paper seems to be overlapping with the update in 4202.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) suggests to POSTPONED this paper and other related papers.
Fei (OPPO) responds to Deng Qiang and Judy.
Deng Qiang (CATT) replies to Fei (OPPO).
Steve (Huawei) supports approving this pCR
Judy (Ericsson) supports DengQiang's proposal to postpone the paper, similar reasoning as DengQiang summarized.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2103847 P-CR Approval 23.304: Resolve EN about Relay Service Code for Layer-2 UE-to-Network Relay in clause 5.9.3.2 in TS 23.304 v0.2.0. Ericsson Rel-17 Postponed Fei (OPPO) raised concen on this proposal and proposed to note this PCR.
Steve (Huawei) also has concerns on this approach. This pCR should be noted.
Hong (Qualcomm) comments.
Judy (Ericsson) responds
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) suggests to POSTPONED this paper and other related papers.
Steve (Huawei) objects to all revisions (for clarity). Postpone could be ok, but prefers noted.
Judy (Ericsson) is OK to postpone
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104202 P-CR Approval 23.304: TS 23.304: Clause 5.9.3.3 EN remove. vivo Rel-17 Postponed Changhong (Intel) provides r01.
Mehrdad(Samsung) comments and asks for clarification regarding mobility restrictions.
Wen (vivo) responds to Mehrdad(Samsung) and provides r02.
Fei (OPPO) asks for clarification.
Wen (vivo) responds to Fei (OPPO).
Steve (Huawei) comments
Mehrdad (Samsung) provides r03
Fei (OPPO) comments on r03.
Wen (vivo) replies and provides r04.
Steve (Huawei) objects to r03 and r04, provides r05.
Mehrdad (Samsung) objects to revision 5 and any revisions without mobility restriction EN.
Deng Qiang (CATT) comments on Relay TAI for L2 Relay selection.
Wen (vivo) responds to Deng Qiang (CATT).
Fei (OPPO) comments.
Wen (vivo) replies and provides r06.
Mehrdad (Samsung) provides r07
Steve (Huawei) r06 is ok, objects to r07
Judy (Ericsson) ask question
Wen (vivo) responds to Judy (Ericsson)
Judy (Ericsson) ask further question
Xiaoyan Shi (Interdigital) prefers r06.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) suggests to POSTPONED this paper and other related papers.
Steve (Huawei) supports r06. Objects to r03, r04, r07.
Mehrdad (Samsung) is OK with r07 but objects to all other revisions and original version.
Judy (Ericsson) support Deng Qiang's proposal to postpone this paper
Wen (vivo) replies and accepts the postponed
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104266 P-CR Approval 23.304: Identifiers for Layer-2 UE-to-Network Relay. Huawei, HiSilicon Rel-17 Postponed Steve (Huawei) provides r01 to avoid overlap with 3755
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) suggests to POSTPONED this paper and other related papers.
Steve (Huawei) if 3755 is approved then this should be. I support it being approved.
Judy (Ericsson) supports DengQiang's proposal to postpone the paper and the related papers (3755, 3847 & 4202)
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2103846 P-CR Approval 23.304: Resolving EN regarding User Info ID in clause 5.9.3.1. Ericsson Rel-17 Noted Deng Qiang (CATT) comments.
Mehrdad (Samsung) comments.
Steve (Huawei) comments
Xiaoyan Shi(Interdigital) comments
Judy (Ericsson) responds
Fei (OPPO) comments
Hao Dong (ZTE) comments.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) thinks that this pCR can be NOTED because 4587r03 can resolve the issue about User Info ID.
Steve (Huawei) agrees with LaeYoung (LGE) and the reason to note.
Mehrdad (Samsung) agrees with LGE and Huawei and suggests to NOTE this PCR.
Judy (Ericsson) is OK to note the paper if that's the majority view.
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2103848 P-CR Approval 23.304: Replacing 'Discovery Group ID' with 'Application Layer Group ID'. Ericsson Rel-17 r02 agreed. Revised to S2-2104935, merging S2-2104339 Mehrdad (Samsung) comments on original version
Hao Dong (ZTE) comments.
Wen (vivo) comments on r01
Judy (Ericsson) respond and provide r02 based on r00.
Mehrdad (Samsung) also prefers to keep Application Layer Group ID as the identifier
Hao Dong (ZTE) provides r03.
Mehrdad (Samsung) prefers r02 and has concern over r03.
Hao Dong (ZTE) responds to Mehrdad (Samsung).
==== 8.X, 9.X Revisions Deadline ====
Hao Dong (ZTE) prefers r03.
Mehrdad (Samsung) suggests to go with r02 and objects to r03.
Hao Dong (ZTE) can live with r02 and responds to Mehrdad (Samsung).
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104935 P-CR Approval 23.304: Replacing 'Discovery Group ID' with 'Application Layer Group ID'. Ericsson Rel-17 Revision of S2-2103848r02, merging S2-2104339. Approved Approved
8.8 S2-2104339 P-CR Approval 23.304: Clause 5.1.2.1 Clarification on ProSe Layer-2 Group ID Parameter for Group Member Discover. ZTE Rel-17 Merged into S2-2104935 Mehrdad (Samsung) comments on original version
Hao Dong (ZTE) responds to Mehrdad (Samsung).
Changhong (Intel) comments.
Hao Dong (ZTE) responds to Changhong (Intel).
Mehrdad (Samsung) suggests to mark this PCR merged into S2-2103848r02
Hao Dong (ZTE) responds to Mehrdad (Samsung) and agrees to merge this paper into S2-2103848.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2103929 P-CR Approval 23.304: L2 ID determination for U2N relay discovery. LG Electronics Rel-17 Merged into S2-2104936 Deng Qiang (CATT) proposes this paper be merged into S2-2104270.
LaeYoung (LGE) is fine to merge this pCR into S2-2104270 (Huawei).
Steve (Huawei) agrees
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104270 P-CR Approval 23.304: Clarifications on Layer-2 ID for UE-to-Network Relay discovery. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104936, merging S2-2103929 LaeYoung (LGE) provides comment.
Wen (vivo) comments.
LaeYoung (LGE) replies to Wen (vivo).
Steve (Huawei) comments
Hao Dong (ZTE) comments.
Fei (OPPO) provides r01.
Steve (Huawei) r01 looks good
Hao Dong (ZTE) provides r02.
Walter (Philips) provides r03
Steve (Huawei) r03 looks ok.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104936 P-CR Approval 23.304: Clarifications on Layer-2 ID for UE-to-Network Relay discovery. Huawei, HiSilicon Rel-17 Revision of S2-2104270r03, merging S2-2103929. Approved Approved
8.8 S2-2104207 P-CR Approval 23.304: TS 23.304: Layer 2 ID for group member discovery. vivo Rel-17 r01 agreed. Revised to S2-2104937. Deng Qiang (CATT) comments.
Hao Dong (ZTE) shares the view from DengQiang (CATT).
Wen (vivo) responds and provides r01.
Mehrdad (Samsung) comment on original version and r01.
Wen (vivo) responds to Mehrdad.
==== 8.X, 9.X Revisions Deadline ====
Wen (vivo) thinks this paper should be agreed with r01 as seeming nobody has further comments after my reply.
Mehrdad (Samsung) can live with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104937 P-CR Approval 23.304: TS 23.304: Layer 2 ID for group member discovery. vivo Rel-17 Revision of S2-2104207r01. Approved Approved
8.8 S2-2104262 P-CR Approval 23.304: Parameters used for ProSe Direct Discovery. Huawei, HiSilicon, Samsung, OPPO Rel-17 Approved Sherry (Xiaomi) comments.
Steve (Huawei) comments
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104267 P-CR Approval 23.304: Update on L3 UE-to-Network Relay discovery for slicing. Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2104938. Deng Qiang (CATT) proposes to NOTED this paper.
Fei (OPPO) provides r01.
Hao Dong (ZTE) comments.
Steve (Huawei) comments
Xiaoyan Shi (Interdigital) support the proposal and provides r02.
Wen (vivo) comments on the need of changes.
Fei (OPPO) comments.
Xiaoyan Shi (Interdigital) shares same view with Steve
Wen (vivo) responds
Deng Qiang (CATT) comments.
Steve (Huawei) provides r03 and comments
Xiaoyan Shi (Interdigital) is fine with r03.
Fei (OPPO) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) r04 looks good, thank you for the update.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104938 P-CR Approval 23.304: Update on L3 UE-to-Network Relay discovery for slicing. Huawei, HiSilicon Rel-17 Revision of S2-2104267r04. Approved Approved
8.8 S2-2104587 P-CR Approval 23.304: Clarification on identifiers for group member discovery. Samsung, Huawei, HiSilicon, LG Electronics, OPPO Rel-17 r03 agreed. Revised to S2-2104939. Judy (Ericsson) comments
Changhong (Intel) comments and asks to postpone this paper.
Mehrdad (Samsung) clarifies that there is no agreement on 3846 and this CR stays open
Mehrdad (Samsung) replies to Ericsson.
Mehrdad (Samsung) provides r01.
LaeYoung (LGE) comments on r01.
Mehrdad (Samsung) provides r02 and r03 on LG's request.
Judy (Ericsson) ask questions
LaeYoung (LGE) replies to Judy (Ericsson).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104939 P-CR Approval 23.304: Clarification on identifiers for group member discovery. Samsung, Huawei, HiSilicon, LG Electronics, OPPO Rel-17 Revision of S2-2104587r03. Approved Approved
8.8 S2-2104753 P-CR Approval 23.304: Resolve EN about RSC under clause 5.4.1.2 of TS 23.304. Qualcomm Incorporated Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104764 P-CR Approval 23.304: TS 23.304: Removing Application IDs from Section 6.3.2. Philips International B.V. Rel-17 r01 agreed. Revised to S2-2104940. Fei (OPPO) comments and provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104940 P-CR Approval 23.304: TS 23.304: Removing Application IDs from Section 6.3.2. Philips International B.V. Rel-17 Revision of S2-2104764r01. Approved Approved
8.8 - - - Identifiers for Direct Communication - - Docs:=2 -
8.8 S2-2103926 P-CR Approval 23.304: Clause 5.9.2.3: Update to ID for groupcast. LG Electronics, ZTE, CATT, OPPO, Samsung Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104351 P-CR Approval 23.304: Clause 5.1.3.1, 5.9.2.4 Clarification on Identifiers update for Unicast Mode ProSe Direct Communication. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 - - - Parameters provisioning - - Docs:=6 -
8.8 S2-2103927 P-CR Approval 23.304: Clarification on priority of group related parameters from Application Server. LG Electronics, Samsung, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104208 P-CR Approval 23.304: TS 23.304: Principles for applying parameters for ProSe UE-to-Network Relay. vivo Rel-17 CC#4: r04 with changes agreed. Revised to S2-2105161, merging S2-2104465. Deng Qiang (CATT) comments.
Wen (vivo) replies to Deng Qiang (CATT).
Fei (OPPO) comments.
Wen (vivo) responds to Fei (OPPO) .
Hao Dong (ZTE) comments.
Wen (vivo) responds to Hao Dong (ZTE).
Mehrdad(Samsung) comments and asks for clarification regarding mobility restrictions.
Wen(vivo) responds to Mehrdad(Samsung).
Fei (OPPO) responds to Wen and Mehrdad.
Mehrdad (Samsung) replies to OPPO and requests addition of a new clause.
Walter (Philips) proposed to change or remove NOTE 4
Hong (Qualcomm) comments.
Fei (OPPO) responds to Mehrdad (Samsung).
Wen (vivo) responds and provides r01.
LaeYoung (LGE) comments.
Fei (OPPO) responds to LaeYoung.
Wen (vivo) replies to LaeYoung (LGE) and provides r02.
Steve (Huawei) objects to r01 and r02, provides r03.
Mehrdad (Samsung) objects to revision 3 and any revisions without mobility restriction EN.
Steve (Huawei) comments
Wen (vivo) replies and provides r04
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) objects to r01 and r02. Prefers r03. Can just about live with r04.
Mehrdad (Samsung) is OK with r04 and objects to all other revisions and original version.
Wen (vivo) replies and supports r04 .
Hong (Qualcomm) comments on all revisions and asks to remove one of the bullet.
Fei (OPPO) responds to Hong (Qualcomm)
Hong (Qualcomm) replies to Fei.
Changhong (Intel) replies to Hong.
Hong (Qualcomm) replies to Changhong (Intel).
Wen (vivo) replies to Hong (Qualcomm) and suggests to remove all related descriptions next meeting.
Hong (Qualcomm) provides r05 for CC#4.
==== 8.X, 9.X Final Deadline ====
Wen (vivo) replies to Hong (Qualcomm) and is ok to CC#4.
Hong (Qualcomm) replies to Wen.
Hannu (Nokia) comments on r05 and the EN on Mobility Restrictions.
Mehrdad (Samsung) comments on r05.
Revised
8.8 S2-2105161 P-CR Approval 23.304: TS 23.304: Principles for applying parameters for ProSe UE-to-Network Relay. vivo Rel-17 Revision of S2-2104208r04 with changes, merging S2-2104465. CC#4: Approved Approved
8.8 S2-2104465 P-CR Approval 23.304: Principle for applying parameters for U2N relay. OPPO Rel-17 Merged into S2-2105161 Deng Qiang (CATT) asks question for clarification.
Fei (OPPO) responds to Deng Qiang (CATT)
Changhong (Intel) comments.
Fei (OPPO) responds and provides r01.
Wen (vivo) responds to Fei and suggest to merge 4465r01 into 4208.
Mehrdad(Samsung) comments and asks for clarification regarding mobility restrictions.
Fei (OPPO) responds to Mehrdad and is fine to merge this PCR to S2-2104208.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104209 P-CR Approval 23.304: TS 23.304: Updates to Policy/Parameter provisioning for ProSe UE-to-Network Relay. vivo Rel-17 r03 agreed. Revised to S2-2104941. Mehrdad (Samsung) comment on original version
Wen (vivo) replies to Mehrdad (Samsung)
Changhong (Intel) is fine with removing this indication.
Sherry (Xiaomi) comments.
Wen (vivo) responds to Sherry (Xiaomi) .
Fei (OPPO) comments and provides r01.
Steve (Huawei) provides r02
Changhong (Intel) objects to r01 and r02 and proposes to go with r00.
Steve (Huawei) provides r03
Sherry (Xiaomi) replies.
==== 8.X, 9.X Revisions Deadline ====
Wen (vivo) responds to Sherry (Xiaomi).
Changhong (Intel) is fine with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104941 P-CR Approval 23.304: TS 23.304: Updates to Policy/Parameter provisioning for ProSe UE-to-Network Relay. vivo Rel-17 Revision of S2-2104209r03. Approved Approved
8.8 - - - PDU ID management - - Docs:=9 -
8.8 S2-2103820 CR Approval 23.503 CR0573 (Rel-17, 'B'): Reporting Change of PDUID by the PCF Ericsson Rel-17 r02 agreed. Revised to S2-2104942. LaeYoung (LGE) provides r01.
Mirko (Huawei) provides r02.
Belen (Ericsson) is okay with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104942 CR Approval 23.503 CR0573R1 (Rel-17, 'B'): Reporting Change of PDUID by the PCF Ericsson Rel-17 Revision of S2-2103820r02. Approved Agreed
8.8 S2-2103821 CR Approval 23.502 CR2734 (Rel-17, 'B'): Reporting Change of PDUID by the PCF Ericsson Rel-17 r01 agreed. Revised to S2-2104943. Mirko (Huawei) provides r01.
Belen (Ericsson) is oka with r01.
Mirko (Huawei) responds.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104943 CR Approval 23.502 CR2734R1 (Rel-17, 'B'): Reporting Change of PDUID by the PCF Ericsson Rel-17 Revision of S2-2103821r01. Approved Agreed
8.8 S2-2103843 P-CR Approval 23.304: Clarification of PDUID provisioning. Ericsson Rel-17 r02 agreed. Revised to S2-2104944. Steve (Huawei) provides r01
Hong (Qualcomm) comments.
Steve (Huawei) comments
Judy (Ericsson) provides r02
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) r02 looks good.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104944 P-CR Approval 23.304: Clarification of PDUID provisioning. Ericsson Rel-17 Revision of S2-2103843r02. Approved Approved
8.8 S2-2103849 P-CR Approval 23.304: [4.2] Update Architecture to add reference point between PCF and DDNMF. Ericsson Rel-17 Merged into S2-2104945 Steve (Huawei) comments on overlap with 4269 and wonders about merge.
Judy (Ericsson) is fine merging 3849 with 4269
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104269 P-CR Approval 23.304: Update for PDUID allocation by the PCF . Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104945, merging S2-2103849 Steve (Huawei) provides r01, bring in figure 4.2.1-1 from S2-2103849
Judy (Ericsson) is fine with merging 3849 into 4269 and provide r02.
Sherry (Xiaomi) requests for clarification on the inter- 5G DDNMF interface.
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104945 P-CR Approval 23.304: Update for PDUID allocation by the PCF . Huawei, HiSilicon Rel-17 Revision of S2-2104269r03, merging S2-2103849. Approved Approved
8.8 - - - QoS handling for UE-NW Relay - - Docs:=11 -
8.8 S2-2103844 P-CR Approval 23.304: Clarify QoS Handling for Layer-3 UE-to-Network Relay in clause 5.7.2.1 in TS 23.304 v0.2.0. Ericsson Rel-17 Postponed Hannu (Nokia) shares r01.
Steve (Huawei) asks for clarification
Yali (OPPO) proposes to NOTED this paper.
Judy (Ericsson) wonders if there is misunderstanding of the proposal and provide r02.
Yali (OPPO) replies to Judy and is fine with r01 and r02.
Steve (Huawei) provide r03
Judy (Ericsson) comments that r03 changes the intention of this paper and does not provide the necessary clarification
Steve (Huawei) asks a question
Judy (Ericsson) responds to Steve
Steve (Huawei) comments
Yali (OPPO) comments.
LaeYoung (LGE) comments.
Mehrdad (Samsung) is OK with r02 but cannot agree with r03
Steve (Huawei) provides r04 and comments
Mehrdad (Samsung) is OK with both r02 and r04.
Yali (OPPO) provides r05.
LaeYoung (LGE) is fine with r04 and r05.
Wen (vivo) prefers r05.
Mehrdad (Samsung) objects to r05 but is ok with r02 or r04
Yali (OPPO) asks a question to Mehrdad, and prefers r05, can live with r02, objects to r04.
Steve (Huawei) comments on r05
Yali (OPPO) replies to Steve and provides r06.
Steve (Huawei) r06 is clear, thank you.
Mehrdad (Samsung) cannot agree with r05, or r06 and provides r07.
Yali (OPPO) asks a question to Mehrdad about r07.
Mehrdad (Samsung) replies to OPPO.
LaeYoung (LGE) comments that r07 is not correct.
Mehrdad replies to LG.
Mehrdad (Samsung) replies to LG.
LaeYoung (LGE) replies to Mehrdad (Samsung).
==== 8.X, 9.X Revisions Deadline ====
Yali (OPPO) proposes to go with r06 or postpone.
LaeYoung (LGE) is fine to go with r06.
Tao(VC) Let's double check whether Mehrdad can live with r06
Mehrdad (Samsung) suggests to go with r02 or otherwise to postpone this to the next meeting. Samsung objects to r05, r06.
Judy (Ericsson) thanks everyone for your effort to improve the paper. I hope we can move forward with r02 and make improvement next meeting.
Yali (OPPO) proposes to postpone.
Yali (OPPO) replies to Judy and proposes to postpone if r06 is not acceptable.
Steve (Huawei) is ok with r02 or r06 or postponing.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2103845 P-CR Approval 23.304: Update for Reflective QoS Handling for L3 UE-to-Network Relay. Ericsson Rel-17 r04 agreed. Revised to S2-2104946. Yali (OPPO) prefers option2.
Judy (Ericsson) responds to Yali (OPPO)
Myungjune (LGE) provides comments.
Yali (OPPO) comments.
Judy (Ericsson) comments.
Hong (Qualcomm) comments and propose to NOTE.
Myungjune (LGE) replies to Judy (Ericsson), Hong (Qualcomm) and Yali (OPPO).
Yali (OPPO) replies to Myungjune (LGE).
Myungjune (LGE) replies to Yali (OPPO).
Yali (OPPO) provides r01.
Hong (Qualcomm) responds to Judy.
Yali (OPPO) replies to Hong.
Myungjune (LGE) provides r02.
Hong (Qualcomm) replies to Yali.
Judy (Ericsson) responds and provide r03
Yali (OPPO) replies to Hong and Judy.
Myungjune (LGE) agrees with Yali (OPPO).
Hong (Qualcomm) comments.
Mehrdad (Samsung) cannot agree with original version, r01 and r03.
Myungjune (LGE) replies to Hong (Qualcomm).
Yali (OPPO) prefers r02.
Changhong (Intel) comments and proposes to NOTE this paper.
Yali (OPPO) asks a question to Changhong.
Judy (Ericsson) comment.
Yali (OPPO) proposes to go with r02.
Weijun (Huawei) asks for clarification.
Yali (OPPO) replies to Weijun.
Weijun (Huawei) responds to Yali (OPPO).
Wen (vivo) comments.
Yali (OPPO) replies to Weijun and Wen.
Weijun (Huawei) thanks for Yali 's(OPPO) clarification and provides r04.
Philips provides revision r05
Yali (OPPO) comments on r05.
Mehrdad (Samsung) objects to r05.
Walter (Philips) asks question to Mehrdad (Samsung)
Walter (Philips) provides revisions r06 and r07. Prefers r06, but can live with r07.
==== 8.X, 9.X Revisions Deadline ====
Yali (OPPO) prefers r02 or r04, can live with r07, objects to other versions.
Myungjune (LGE) prefers r04 but can live with r07.
Walter (Philips) is ok with r04 if companies don't want to make exception for reflective QoS with QFI=5QI as in r05 and r06. We can ignore r07.
Yali (OPPO) proposes to go with r04 according to the discussion.
Mehrdad (Samsung) suggests to move forward with r04. Samsung Objects to other revisions.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104946 P-CR Approval 23.304: Update for Reflective QoS Handling for L3 UE-to-Network Relay. Ericsson Rel-17 Revision of S2-2103845r04. Approved Approved
8.8 S2-2104130 P-CR Approval 23.304: TS 23.304: Resolving EN about the granularity of QoS mapping rule. OPPO Rel-17 Merged into S2-2104947 LaeYoung (LGE) proposes to mark this pCR merged into S2-2104754 (Qualcomm).
Yali (OPPO) confirms this pCR merged into S2-2104754.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104754 P-CR Approval 23.304: TS 23.304 clause 5.7.2.1: Clarification of QoS mapping rules for Layer-3 UE-to-Network Relay. Qualcomm Incorporated Rel-17 r08 agreed. Revised to S2-2104947, merging S2-2104130 Yali (OPPO) provides r01.
Hong (Qualcomm) comments on r01.
Xiaoyan Shi (Interdigital) comments on both r00 and r01.
Hong (Qualcomm) response to Xiaoyan.
Yali (OPPO) comments.
Hong (Qualcomm) responds to Yali.
Yali (OPPO) is fine with the original version.
LaeYoung (LGE) comments.
Yali (OPPO) replies to LaeYoung.
LaeYoung (LGE) replies to Yali (OPPO).
Yali (OPPO) provides r02.
LaeYoung (LGE) provides r03.
Yali (OPPO) comments on r03.
LaeYoung (LGE) answers to Yali (OPPO).
Yali (OPPO) replies to LaeYoung (LGE).
Hao Dong (ZTE) comments.
Judy (Ericsson) comments and provide r04.
Mehrdad (Samsung) requests clarification on r04.
Steve (Huawei) comments
Hong (Qualcomm) replies.
Hong (Qualcomm) replies to Steve.
Judy (Ericsson) responds to Mehrdad (Samsung) and provide r05
Yali (OPPO) provides r06.
Changhong (Intel) asks Yali questions on IP 3-tuple.
Yali (OPPO) replies to Changhong.
Judy (Ericsson) ask Q for clarification
Yali (OPPO) replies to Judy.
Changhong (Intel) replies to Yali and proposes to go with r02, objects to other revisions.
Mehrdad (Samsung) provides r07 based on r05.
Yali (OPPO) comments on r07, provides r08, and is also fine to go with r02.
Steve (Huawei) asks about RAN knowledge of the adjustment factor (again).
==== 8.X, 9.X Revisions Deadline ====
Mehrdad (Samsung) is supportive of both r07 and r08 and would like to co-sign the PCR based on either versions.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104947 P-CR Approval 23.304: TS 23.304 clause 5.7.2.1: Clarification of QoS mapping rules for Layer-3 UE-to-Network Relay. Qualcomm Incorporated Rel-17 Revision of S2-2104754r08, merging S2-2104130. Approved Approved
8.8 S2-2104146 P-CR Approval 23.304: TS 23.304: Packet filter used for the L3 U2N Relay QoS handling. OPPO Rel-17 r03 agreed. Revised to S2-2104948. LaeYoung (LGE) provides r01.
Wen (vivo) comments on r01.
LaeYoung (LGE) replies to Wen (vivo).
Steve (Huawei) comments
Hong (Qualcomm) comments.
Xiaoyan Shi (Interdigital) asks question for clarification.
Yali (OPPO) provides r02.
LaeYoung (LGE) asks a Q.
Yali (OPPO) replies to LaeYoung.
Mehrdad (Samsung) comments and original version, r01 and r02.
Yali (OPPO) replies and indicates r03 has been provided.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104948 P-CR Approval 23.304: TS 23.304: Packet filter used for the L3 U2N Relay QoS handling. OPPO Rel-17 Revision of S2-2104146r03. Approved Approved
8.8 S2-2104149 P-CR Approval 23.304: TS 23.304: L3 U2N ProSe Communication procedure. OPPO Rel-17 Merged into S2-2104949 Deng Qiang (CATT) thinks this paper can be marked as merged into S2-2104107r05.
Yali (OPPO) is fine to merge into S2-2104107.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104268 P-CR Approval 23.304: Clarification on QoS handling for L2 and L3 Relay operations. Huawei, HiSilicon Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104354 P-CR Approval 23.304: Clause 5.7.2.1 Clarification on QoS Handling for Layer-3 UE-to-Network Relay without N3IWF. ZTE Rel-17 Noted Yali (OPPO) comments.
LaeYoung (LGE) proposes to NOTE this paper.
Hao Dong (ZTE) responds to LaeYoung (LGE) and Yali (OPPP), and provides r01.
LaeYoung (LGE) provides comment and is not fine with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - UE-NW Relay procedures - - Docs:=9 -
8.8 S2-2104107 P-CR Approval 23.304: TS 23.304: Procedure on Layer-3 UE-to-Network Relay without N3IWF. CATT, LG Electronics Rel-17 r12 agreed. Revised to S2-2104949, merging S2-2104149 and S2-2104634 Judy (Ericsson) provides r01
Yali (OPPO) provides comment.
Hong (Qualcomm) comments.
Xiaoyan Shi (Interdigital) comments on r01.
LaeYoung (LGE) provides r02.
Yali (OPPO) comments.
LaeYoung (LGE) replies to Yali (OPPO).
Steve (Huawei) comments
Hong (Qualcomm) provides some comments.
Xiaoyan Shi (Interdigital) comments on SMF change.
Yali (OPPO) provides r03.
Deng Qiang (CATT) replies and provides r03.
Yali (OPPO) replies to Deng Qiang.
Deng Qiang (CATT) provides r04.
Yali (OPPO) comments on r04.
LaeYoung (LGE) provides r05.
Yali (OPPO) is fine with r05.
Xiaoyan Shi (Interdigital) provides r06 by removing paragraph on SMF change
Deng Qiang (CATT) provides r07.
LaeYoung (LGE) provides r08.
Mehrdad (Samsung) requests clarification on why the possibility to connect to EPC was removed.
LaeYoung (LGE) replies to Mehrdad (Samsung).
Hannu (Nokia) shares r09.
Steve (Huawei) thanks LaeYoung (LGE) for taking my comments on-board and asks for clarification on r09
Mehrdad (Samsung) provides r10 and co-signs the PCR
Steve (Huawei) objects to r10
Yali (OPPO) cannot accept r10.
Deng Qiang (CATT) suggests go with r08.
LaeYoung (LGE) provides r11 on top of r09 from Hannu (Nokia) and answers to Steve (Huawei).
Steve (Huawei) r11 looks fine, r08 is also fine for me.
Xiaoyan Shi (Interdigital) can live with r08 or r11
Hannu (Nokia) supports r11
LaeYoung (LGE) provides r12.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) is fine with either r08 or r12, and thanks LaeYoung (LGE) for the revisions.
Steve (Huawei) is ok with r12.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104949 P-CR Approval 23.304: TS 23.304: Procedure on Layer-3 UE-to-Network Relay without N3IWF. CATT, LG Electronics Rel-17 Revision of S2-2104107r12, merging S2-2104149, merging S2-2104149 and S2-2104634. Approved Approved
8.8 S2-2104272 P-CR Approval 23.304: Layer-2 link establishment for UE-to-Network Relaying. Huawei, HiSilicon, Philips International B.V. Rel-17 r09 agreed. Revised to S2-2104950. Fei (OPPO) comments
Hao Dong (ZTE) comments.
Judy (Ericsson) comments
Hong (Qualcomm) responds to Judy.
Weijun Xing (Huawei) responds.
Fei (OPPO) responds.
Hao Dong (ZTE) responds to Weijun (Huawei).
Weijun (Huawei) provides r02.
Hao Dong (ZTE) comments on new version.
Weijun (Huawei) responds to Hao Dong (ZTE) and provides r02. The previous version should be r01. Sorry for that.
Fei (OPPO) provides r03.
Xiaoyan Shi (Interdigital) provides comments.
Hong (Qualcomm) comments.
Fei (OPPO) responds to Xiaoyan (Inderdigital).
Wen(vivo) comments and provides r04.
Changhong(Intel) asks a question on the NOTE X.
Weijun (Huawei) responds to Changhong (Intel).
Walter (Philips) provides r05
Hong (Qualcomm) provides r06.
Weijun (Huawei) is fine with r05 and r06.
Fei (OPPO) provides r07.
Wen (vivo) provides r08.
Walter (Philips) provides r09
Wen (vivo) comments on r09
Walter (Philips) responds to Wen's question
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) is ok with r09
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104950 P-CR Approval 23.304: Layer-2 link establishment for UE-to-Network Relaying. Huawei, HiSilicon, Philips International B.V. Rel-17 Revision of S2-2104272r09. Approved Approved
8.8 S2-2104563 P-CR Approval 23.304: UE-to-network L3 relay call flow. Nokia, Nokia Shanghai Bell Rel-17 Noted Deng Qiang (CATT) proposes to NOTED this paper and wait for SA3 conclusion.
Judy (Ericsson) shares CATT's view and supports the proposal to note this paper.
Xiaoyan Shi (Interdigital) would suggest SA2 moving forward with this proposal.
Steve (Huawei) waiting for SA3 is fine.
Hannu (Nokia) proposes to treat all security procedures the same way in this meeting.
Jicheol (Samsung) supports Hannu(Nokia)'s view.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104594 P-CR Approval 23.304: L3 UE-to-Network relay mobility. Nokia, Nokia Shanghai Bell Rel-17 Noted Deng Qiang (CATT) proposes to NOTED this pCR.
Hannu (Nokia) agrees to work on L3 relay mobility via S2-2104755.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104634 P-CR Approval 23.304: L3 UE-to-network relay establishment call flow. Nokia, Nokia Shanghai Bell Rel-17 Merged into S2-2104949 Deng Qiang (CATT) proposes this pCR to be merged into S2-2104107 and S2-2104755.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104755 P-CR Approval 23.304: TS 23.304: 6.5.1.x ProSe Direct Communication via Layer-3 UE-to-Network Relay . Qualcomm Incorporated Rel-17 r04 agreed. Revised to S2-2104951. Hannu (Nokia) asks what are the Layer-3 UE-to-Network Relay capabilities to support N3IWF and how does it show in the PDU session for relaying?
Hong (Qualcomm) replies to Hannu.
Hannu (Nokia) replies to Hong (Qualcomm) and provides r01.
Steve (Huawei) provides r02
Hong (Qualcomm) provides r03.
LaeYoung (LGE) provides r04.
Hannu (Nokia) supports r04 and answers to Steve and Hong.
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) r04 is ok
==== 8.X, 9.X Final Deadline ====
Hannu (Nokia) volunteers to bring a CR to the next meeting to solve the EN that I added in clause 6.5.1.x.3. Mobility between two different indirect paths can be solved using the same procedure as mobility from direct to indirect communication path and I can bring a CR to say it next time.
Revised
8.8 S2-2104951 P-CR Approval 23.304: TS 23.304: 6.5.1.x ProSe Direct Communication via Layer-3 UE-to-Network Relay . Qualcomm Incorporated Rel-17 Revision of S2-2104755r04. Approved Approved
8.8 - - - Remote UE traffic handling - - Docs:=8 -
8.8 S2-2104273 P-CR Approval 23.304: Remote UE traffic routing via different UE-to-Network Relay types. Huawei, HiSilicon Rel-17 Noted Hong (Qualcomm) comments and propose to follow principles in S2-2104756 instead.
Steve (Huawei) comments
Hong (Qualcomm) replies to Steve.
Hong (Qualcomm) comments.
Deng Qiang (CATT) comments and suggests using the principle in S2-2104756 as basis for further discussion.
Changhong (Intel) asks to note this paper and discuss in the thread of S2-2104756.
Sherry (Xiaomi) also supports to follow principles in S2-2104756, and to discuss under the thread of 4756.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104274 CR Approval 23.503 CR0590 (Rel-17, 'B'): URSP enhancement for 5G ProSe Remote UE traffic handling Huawei, HiSilicon Rel-17 Noted Hong (Qualcomm) comments and propose to follow principles in S2-2104757 instead.
Steve (Huawei) comments
Changhong (Intel) asks to note this paper and discuss in the thread of S2-2104757.
Sherry (Xiaomi) shares the view to follow principles in S2-2104757.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104558 DISCUSSION Discussion Discussion on Relay Service Code in URSP rules. Apple Noted Deng Qiang (CATT) this DP can be marked as NOTED.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104586 CR Approval 23.503 CR0597 (Rel-17, 'B'): Adding RSC to URSP rules Apple Rel-17 Noted LaeYoung (LGE) proposes to NOTE this CR.
Hong (Qualcomm) comments and agrees with Laeyoung.
Sherry (Xiaomi) comments.
Hong (Qualcomm) responses to Sherry.
Changhong (Intel) proposes to note this paper and use S2-2104757 as the working baseline.
Sudeep (Apple) responds to Hong.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104756 P-CR Approval 23.304: TS 23.304 clause 6.5.x on URSP handling for UE-to-Network Relay support. Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2102884. r01 agreed. Revised to S2-2104952. Judy (Ericsson) comments
Changhong (Intel) comments
Steve (Huawei) asks a question
Hong (Qualcomm) replies to Judy and Steve.
Steve (Huawei) comments
Steve (Huawei) A small correction to my comment.
Steve (Huawei) comments revisions are need.
Hong (Qualcomm) replies and would create revisions based on discussion of 4757.
Steve (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
Sherry (Xiaomi) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104952 P-CR Approval 23.304: TS 23.304 clause 6.5.x on URSP handling for UE-to-Network Relay support. Qualcomm Incorporated Rel-17 Revision of S2-2104756r01. Approved Approved
8.8 S2-2104757 CR Approval 23.503 CR0569R1 (Rel-17, 'B'): URSP enhancement for the 5G ProSe UE-to-Network Relay support Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2102883. r06 agreed. Revised to S2-2104953. Judy (Ericsson): please see comments on new access type and non-seamless offload indication in 4756
Changhong (Intel) comments
Steve (Huawei) provides r01
Hong (Qualcomm) provides r02.
Steve (Huawei) provides r03 and comments.
Hong (Qualcomm) provides replies to questions from Steve, and provide r04.
Steve (Huawei) provides r05
Hong (Qualcomm) provides r06.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) comments on r06.
Steve (Huawei) is ok with r06
Hong (Qualcomm) replies.
Sherry (Xiaomi) is fine with r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104953 CR Approval 23.503 CR0569R2 (Rel-17, 'B'): URSP enhancement for the 5G ProSe UE-to-Network Relay support Qualcomm Incorporated Rel-17 Revision of S2-2104757r06. Approved Agreed
8.8 - - - L2 vs. L3 UE-NW Relay co-existence - - Docs:=2 -
8.8 S2-2103754 P-CR Approval 23.304: Co-existence on the L2 and L3 U2N relay. OPPO Rel-17 Noted Sherry (Xiaomi) requests for clarification.
Fei (OPPO) responds to Sherry (Xiaomi) and provides r01.
LaeYoung (LGE) provides r02.
Wen (vivo) comments.
LaeYoung (LGE) replies to Wen (vivo).
Wen (vivo) replies to LaeYoung (LGE).
Steve (Huawei) comments
Hong (Qualcomm) comments and prefers explicit indicator.
Fei (OPPO) responds to Wen (vivo).
Wen (vivo) responds and comments on r02.
Xiaoyan Shi (Interdigital) comments.
Fei (OPPO) responds to Xiaoyan (Interdigital) and Wen (vivo)
Wen (vivo) responds to Fei (OPPO)
LaeYoung (LGE) comments.
Fei (OPPO) responds and provides r03.
Sherry (Xiaomi) comments.
Hong (Qualcomm) comments.
Xiaoyan Shi (Interdigital) replies to Sherry.
Deng Qiang (CATT) comments.
Fei (OPPO) responds to Deng Qiang (CATT).
Changhong (Intel) objects to this paper and any revision. S2-2104209 has solved the issue, this paper can be merged into S2-2104209.
Fei (OPPO) responds to Changhong .
Changhong (Intel) replies to Fei.
Fei (OPPO) responds to Changhong and provides r04.
Changhong (Intel) replies to Fei and objects to r04.
Fei (OPPO) responds to Changhong.
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) replies to Sherry (Xiaomi).
Changhong (Intel) replies to Fei (OPPO).
==== 8.X, 9.X Final Deadline ====
Sherry (Xiaomi) can accept r03 and r04.
Noted
8.8 S2-2104206 P-CR Approval 23.304: Handling of L2 and L3 relay co-existence. vivo Rel-17 Merged into S2-2103754 (Noted) Changhong (Intel) comments and proposes to merge it into S2-2103754.
Wen (vivo) responds to Changhong and accept the proposal of merging.
Changhong (Intel) proposes to mark it NOTED since co-existence issue will not be addressed in Rel-17.
Hannu (Nokia) supports the proposal to note.
Mehrdad (Samsung) raises concern on this PCR.
Wen (vivo) responds to Mehrdad (Samsung).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - UE-UE Relay - - Docs:=2 -
8.8 S2-2104758 P-CR Approval 23.304: Support of the Layer-3 UE-to-UE Relay based on Layer-3 UE-to-Network Relay. Qualcomm Incorporated, Ericsson Rel-17 Noted Lars (Sony) proposes to NOTE this document
Hong (Qualcomm) replies to Lars and suggest the rapporteur to develop a WF paper.
Steve (Huawei) Proposes to note this paper.
Xiaoyan Shi (Interdigital) proposes to note this paper.
Deng Qiang (CATT) drafted a WF paper in S2-2104894.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104894 DISCUSSION Endorsement Way forward on UE-to-UE Relay for Rel-17 5G_ProSe CATT (rapporteur) - Generated during email discussion. CC#4: Noted Deng Qiang (CATT) shared a WF paper on Layer-3 UE-to-UE Relay.
Guillaume (MediaTek): The proposal is ok for us.
Ihab Guirguis (FirstNet) We believe that the proposal from Qualcomm (S2-2104758) should be considered in Release 17 to support Public Safety needs until full solution for UE-to-UE relay in release 18.
Xiaoyan Shi (Interdigital) supports the proposal 'Layer-3 UE-to-UE Relay is not pursed in Rel-17 5G ProSe work item'.
Lars (Sony) supports the proposal 'Layer-3 UE-to-UE Relay is not pursed in Rel-17 5G ProSe work item'.
James Hu (AT&T) provides comments: We also support the proposal from Qualcomm (S2-2104758) which shows that the layer-3 UE-to-Network relay solution can be used to support public safety needs in release 17.
==== 8.X, 9.X Revisions Deadline ====
Deng Qiang (CATT) responds to Ihab Guirguis (FirstNet) and James Hu (AT&T).
Hong (Qualcomm) replies to Deng Qiang.
==== 8.X, 9.X Final Deadline ====
Noted
8.8 - - - Miscellaneous corrections and additions - - Docs:=33 -
8.8 S2-2103756 P-CR Approval 23.304: Cleanup for U2U relay. OPPO Rel-17 CC#4: Approved. The rapporteur was asked to carefully renumber clauses and references to them Changhong (Intel) asks to unapproved this paper and mark it as POSTPONED.
Fei (OPPO) responds to ChangHong and provides r00+ for CC#4.
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2103757 P-CR Approval 23.304: TS 23.304: NAS level congestion control for UE-to-Network Relay. OPPO, Interdigital Inc., vivo Rel-17 r05 agreed. Revised to S2-2104954. Changhong (Intel) comments.
Yali (OPPO) replies to Changhong.
Steve (Huawei) comments
Yali (OPPO) provides r01.
Hong (Qualcomm) comments on r01.
Xiaoyan Shi (Interdigital) provides r02.
Yali (OPPO) provides r03.
LaeYoung (LGE) has concern with texts related to L3 U2N relay.
Deng Qiang (CATT) we hadn't discussed this during study phase and proposed to NOTED this paper.
Wen (vivo) comments.
Yali OPPO) provides r04.
Deng Qiang (CATT) comments and objects any version including L3 Relay.
Xiaoyan Shi (Interdigital) is fine with r04.
Wen (vivo) share same view with Xiaoyan (Interdigital) and can live with r04.
Steve (Huawei) provides r05
Xiaoyan Shi (Interdigital) is fine with r05
Yali OPPO) asks a question to Steve.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104954 P-CR Approval 23.304: TS 23.304: NAS level congestion control for UE-to-Network Relay. OPPO, Interdigital Inc., vivo Rel-17 Revision of S2-2103757r05. Approved Approved
8.8 S2-2103788 P-CR Approval 23.304: PCR for Supporting Many Remote UE during UE-to-Network Relay. Panasonic Corporation, DENSO CORPORATION Rel-17 Noted LaeYoung (LGE) proposes to NOTE this paper.
Hao Dong (ZTE) comments.
Xiaoyan Shi (Interdigtial) proposes r01.
Hong (Qualcomm) comments.
Fei (OPPO) comments.
Steve (Huawei) this should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2103789 DISCUSSION Agreement Discussion on Many Remote UE . Panasonic Corporation, DENSO CORPORATION Rel-17 Noted LaeYoung (LGE) proposes to NOTE this DP because this DP is just for discussion.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2103850 CR Approval 23.501 CR2861 (Rel-17, 'B'): ProSe related functional description Ericsson, LG Electronics Rel-17 r02 agreed. Revised to S2-2104955. Fei (OPPO) provides r01.
Shabnam (Ericsson) provides r02, r01 is not acceptable as it does not conform to the common structure of introducing new entities from other specifications.
Fei (OPPO) responds and is fine with r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104955 CR Approval 23.501 CR2861R1 (Rel-17, 'B'): ProSe related functional description Ericsson, LG Electronics Rel-17 Revision of S2-2103850r02. Approved Agreed
8.8 S2-2103928 P-CR Approval 23.304: Clause 5.6: Adding U2N relay aspect. LG Electronics Rel-17 r01 agreed. Revised to S2-2104956. Steve (Huawei) asks a question for clarification
Hong (Qualcomm) comments.
LaeYoung (LGE) provides r01.
Steve (Huawei) r01 looks good
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104956 P-CR Approval 23.304: Clause 5.6: Adding U2N relay aspect. LG Electronics Rel-17 Revision of S2-2103928r01. Approved Approved
8.8 S2-2104036 P-CR Approval 23.304: Update Delivery of PC5 QoS parameters to NG-RAN. Intel Rel-17 Approved Steve (Huawei) asks for clarification
==== 8.X, 9.X Revisions Deadline ====
Changhong (Intel) replies to Steve (Huawei).
Steve (Huawei) thanks Changhong (Intel) for the clarification.
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104108 P-CR Approval 23.304: TS 23.304: Resolution of several ENs. CATT Rel-17 r02 agreed. Revised to S2-2104957, merging S2-2104204 Steve (Huawei) comments on overlap with Relay ID aspects discussed in 4270/3929.
Deng Qiang (CATT) provides r01.
Fei (OPPO) comments on r00 and r01.
Mehrdad (Samsung) objects to original version and r01
Steve (Huawei) comments on the first change.
Deng Qiang (CATT) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104957 P-CR Approval 23.304: TS 23.304: Resolution of several ENs. CATT Rel-17 Revision of S2-2104108r02, merging S2-2104204. Approved Approved
8.8 S2-2104204 P-CR Approval 23.304: TS 23.304: EN resolve for integrated 5G DDNMF. vivo Rel-17 Merged into S2-2104957 Judy (Ericsson) comments and provide r01
Steve (Huawei) suggests considering this merged to S2-2104108.
Wen (vivo) is ok to merge this paper to S2-2104108.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104263 P-CR Approval 23.304: Additions and updates to UE-UE protocol stacks. Huawei, HiSilicon, OPPO Rel-17 Approved Deng Qiang (CATT) comments.
Fei (OPPO) responds.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104264 P-CR Approval 23.304: Functionality of Layer-2 UE-to-Network Relay. Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2104958, merging S2-2104349 Steve (Huawei) provides r01, merging QoS from S2-2104349
Jianning (Xiaomi) agrees to merge 4349 into 4264, and provides r02 with Xiaomi as co-sourse.
Changhong (Intel) provides r03.
Lars (Sony) comments.
Wen (vivo) comments.
Steve (Huawei) provides r04
Lars (Sony) provides r05
Walter (Philips) provides r06
==== 8.X, 9.X Revisions Deadline ====
Hong (Qualcomm) comments and objects r06.
Steve (Huawei) we are ok with r05. Thank you all.
Lars (Sony) support r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104958 P-CR Approval 23.304: Functionality of Layer-2 UE-to-Network Relay. Huawei, HiSilicon Rel-17 Revision of S2-2104264r05, merging S2-2104349. Approved Approved
8.8 S2-2104349 P-CR Approval 23.304: 4.3.9.2 Layer-2 UE-to-Network Relay . Xiaomi Rel-17 Merged into S2-2104958 Steve (Huawei) Suggests marking S2-2104349 as merged into S2-2104264
Jianning (Xiaomi) agrees to merge into 4264.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.8 S2-2104265 P-CR Approval 23.304: Update on ProSe Subscription. Huawei, HiSilicon Rel-17 r03 agreed. Revised to S2-2104959. Mehrdad (Samsung) comment on original version
Steve (Huawei) comments
Mehrdad (Samsung) comments
Steve (Huawei) provides r01
Judy (Ericsson) provide r02
Fei (OPPO) comments.
Sherry (Xiaomi) comments and prefers r01.
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104959 P-CR Approval 23.304: Update on ProSe Subscription. Huawei, HiSilicon Rel-17 Revision of S2-2104265r03. Approved Approved
8.8 S2-2104271 CR Approval 23.501 CR2910 (Rel-17, 'B'): Update of reference points for 5G ProSe Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2104960. Judy (Ericsson) comments and proposes to merge 4271 to 3850.
Steve (Huawei) comments
Judy (Ericsson) responds to Steve (Huawei)
Fei (OPPO) comments.
Steve (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104960 CR Approval 23.501 CR2910R1 (Rel-17, 'B'): Update of reference points for 5G ProSe Huawei, HiSilicon Rel-17 Revision of S2-2104271r01. Approved Agreed
8.8 S2-2104325 P-CR Approval 23.304: Clause 3.1 Remove Unused Network Communication related Terms. ZTE Rel-17 Postponed Sherry (Xiaomi) has concern on this paper.
Hao Dong (ZTE) responds to Sherry (Xiaomi).
Wen (vivo) shares same concerns with Sherry (Xiaomi).
Hao Dong (ZTE) responds to Wen (Vivo).
Fei (OPPO) comments.
Hao Dong (ZTE) proposes to postpone the paper.
Steve (Huawei) supports postponing, don't think we are quite there yet.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104328 P-CR Approval 23.304: Clause 4.2.6 Modify Nudm Provided Services. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104348 P-CR Approval 23.304: Clause 5.1.2.2 Remove Duplicated Description of Parameters Provision. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104355 P-CR Approval 23.304: Clause 6.4 Fix Wrong and Inaccurate Reference Clause Number and Term 'ProSe Data'. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.8 S2-2104464 P-CR Approval 23.304: SMF discovery. OPPO Rel-17 Noted Weijun Xing (Huawei) comments.
Fei (OPPO) responds and provide r01.
Xiaoyan Shi (Interdigital) asks question for clarification on r01.
Fei (OPPO) responds to Xiaoyan (Inderdigital)
Wen (vivo) comments on r01
Weijun Xing responds to Fei (OPPO).
Fei (OPPO) responds to Weijun (Huawei) and Wen (vivo).
Wen (vivo) responds to Fei (OPPO).
Fei (OPPO) responds to Wen (vivo),
Xiaoyan Shi (Interdigital) would suggest to go back to original version r00,
Wen (vivo) replies to Fei (OPPO),
Weijun Xing(Huawei) comments.
Fei (OPPO) rep
Fei (OPPO) responds to Weijun (Huawei), Wen (vivo) and Xiaoyan (Interdigital)
Weijun (Huawei) asks Fei (OPPO) for clarification.
Fei (OPPO) responds,
Deng Qiang (CATT) comments and proposed to NOTED this pCR.
Fei (OPPO) responds.
Changhong (Intel) proposes to note this paper.
Weijun (Huawei) responds to Fei (OPPO).
Changhong (Intel) replies to Fei and Weijun.
Mehrdad (Samsung) agrees with Intel and has concern on original version and all revisions of this PCR.
Fei (OPPO) responds and is fine to postpone or NOTE this PCR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104466 CR Approval 23.501 CR2928 (Rel-17, 'B'): NRF for DDNMF discovery OPPO Rel-17 Noted Judy (Ericsson) comments description of NRF enhancement for DDNMF discovery should be captured in 23.304.
Fei (OPPO) replies to Judy (Ericsson).
Steve (Huawei) comments on relationship with 4467 and differences from the general case.
Fei (OPPO) responds to Steve (Huawei) and is ok to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104467 CR Approval 23.502 CR2822 (Rel-17, 'B'): NRF for DDNMF discovery OPPO Rel-17 Noted Judy (Ericsson) comments the message flow of NRF for DDNMF discovery should be described in 23.304 if needed and propose to NOTE this paper.
Changhong (Intel) shares same view with Judy and also proposes to NOTE this paper.
Steve (Huawei) proposes to NOTE
Fei (OPPO) responds and is ok to NOTE
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.8 S2-2104565 P-CR Approval 23.304: PC5 link in CM-IDLE in L2 UE-to-Network relay. Nokia, Nokia Shanghai Bell Rel-17 Postponed Yali (OPPO) provides r01.
Wen (vivo) comments on r01 and r00.
Yali (OPPO) replies to Wen.
Wen (vivo) replies to Yali (OPPO).
Yali (OPPO) replies to Wen and provides r02, and indicates r00 is not acceptable.
LaeYoung (LGE) provides r03 and is not fine with r00, r01, r02.
Steve (Huawei) comments
Yali (OPPO) provides r04.
Steve (Huawei) provides r05
Yali (OPPO) comments on r05.
Wen (vivo) comments.
LaeYoung (LGE) provides r06.
Hannu (Nokia) supports comments from Steve (Huawei)
Hannu (Nokia) provides r07.
Yali (OPPO) comments on r07.
Xiaoyan Shi (Interdigital) comments on r07.
Xiaoyan Shi (Interdigital) asks question for clarification.
Hong (Qualcomm) provides r08.
Yali (OPPO) comments on r08.
Hong (Qualcomm) comments.
LaeYoung (LGE) prefers r06 and also postponing this pCR is fine.
Steve (Huawei) postpone seems like a good idea
Xiaoyan Shi (Interdigital) also thinks postpone is good idea.
Hannu (Nokia) proposes minimalistic approach in r09.
Xiaoyan Shi (Interdigital) can live with r09.
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) is fine only with r03 and r06. If there is no agreeable version, we can postpone this pCR.
Steve (Huawei) Objects to all revisions. Ok to postpone is that is preferred.
==== 8.X, 9.X Final Deadline ====
Postponed
8.8 S2-2104667 CR Approval 23.503 CR0567R2 (Rel-17, 'C'): UE policy control to support ProSe U2N relay Xiaomi, LG Electronics Rel-17 Revision of (Agreed) S2-2103522. Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.8 S2-2104669 P-CR Approval 23.304: TS 23.304: Triggers of communication path selection policy evaluation at UE. Xiaomi Rel-17 r07 agreed. Revised to S2-2104961. LaeYoung (LGE) proposes to NOTE this paper.
Sherry (Xiaomi) provides r01.
LaeYoung (LGE) provides comment that the path selection policy does not apply to UE-to-NW relaying, so r01 is not correct.
Sherry (Xiaomi) provides r02.
Hong (Qualcomm) comments.
LaeYoung (LGE) is not fine with all versions.
Mehrdad (Samsung) cannot agree with original version or any revisions of this PCR
Sherry (Xiaomi) replies.
Sherry (Xiaomi) replies to Mehrdad and provides r03.
Sherry (Xiaomi) replies to Hong.
Hong (Qualcomm) replies to Sherry.
LaeYoung (LGE) provides r04. BTW, Sherry (Xiaomi) provides r03 but seems she missed to mention it in the tag.
Steve (Huawei) comments
Mehrdad (Samsung) provides r05
LaeYoung (LGE) asks a Q on r05.
Mehrdad (Samsung) replies to LG
LaeYoung (LGE) asks a Q to Mehrdad (Samsung).
Sherry (Xiaomi) has the same question that LaeYoung asks.
Mehrdad replies to LG and Xiaomi.
LaeYoung (LGE) proposes to go with r04.
Hong (Qualcomm) provides r06.
LaeYoung (LGE) provides r07 on top of r04 by taking the changes in r06.
==== 8.X, 9.X Revisions Deadline ====
Sherry (Xiaomi) is fine with r07 and thanks LaeYoung and Hong for the further efforts to improve the texts.
Mehrdad (Samsung) is OK with r07.
==== 8.X, 9.X Final Deadline ====
Revised
8.8 S2-2104961 P-CR Approval 23.304: TS 23.304: Triggers of communication path selection policy evaluation at UE. Xiaomi Rel-17 Revision of S2-2104669r07. Approved Approved
8.8 S2-2104683 P-CR Approval 23.304: TS 23.304: 5.1.4.1 Remove Editor's Note. Interdigital Inc. Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 - - - Architectural enhancements for 5G multicast-broadcast services (5MBS) - - Docs:=170 -
8.9 - - - General - - Docs:=10 -
8.9 S2-2103739 LS In Action LS from SA WG4: LS on work split for MBSF and MBSTF definition SA WG4 (S4-210632) Rel-17 Response drafted in Ss2-2103959. Final response in S2-2104962 Replied to
8.9 S2-2103959 LS OUT Approval [DRAFT] Reply LS on work split for MBSF and MBSTF definition Ericsson Rel-17 Response to S2-2103739. r02 agreed. Revised to S2-2104962. LiMeng (Huawei) provides r01.
Judy (Ericsson) provides r02
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) is OK with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104962 LS OUT Approval Reply LS on work split for MBSF and MBSTF definition SA WG2 Rel-17 Revision of S2-2103959r02. Approved Approved
8.9 S2-2103773 LS In Action LS from RAN WG2: Reply LS on 5MBS progress and issues to address RAN WG2 (R2-2104655) Rel-17 Noted Judy (Ericsson) proposes to note this paper as no action is needed
LiMeng (Huawei) agrees to note this paper as Judy suggested
Noted
8.9 S2-2103787 DISCUSSION Agreement Discussion of UE Authorization of 5MBS Session . Panasonic Corporation, DENSO CORPORATION Rel-17 Noted LiMeng (Huawei) suggests to note this document.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2103837 DISCUSSION Information Shared delivery establishment and subsequent signalling Nokia, Nokia Shanghai Bell Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2103838 DISCUSSION Information PCF authorizing MBS Session policy Nokia, Nokia Shanghai Bell Noted Judy (Ericsson) comments the description of Option-1 is not based on fact and provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2103840 DISCUSSION Discussion MBS session Information in NRF, UDM and UDR Nokia, Nokia Shanghai Bell Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104232 DISCUSSION Discussion Discussion on options for session join. vivo Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104258 DISCUSSION Discussion Discussion on activation and deactivation procedures. vivo Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.9 - - - 23.501/502/503 - - Docs:=17 -
8.9 S2-2103907 CR Approval 23.501 CR2696R2 (Rel-17, 'B'): N4 extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103528. CC#4: r01 agreed. Revised to S2-2105177, merging S2-2103946. LiMeng (Huawei) asks to discuss S2-2103907 and S2-2103951 together.
Judy (Ericsson) provides r01, merging 3946 into this one (i.e. 3907) following rapporteur's merging proposal
zhendong (ZTE) provides r02.
Thomas (Nokia) raises concerns against r01.
Thomas (Nokia) comments against r01 and r02 and prefers r00.
zhendong (ZTE) provides the reponse to thomas.
Thomas (Nokia) replies to Zhendong.
zhendong (ZTE) provides the response.
Thomas(Nokia) replies to Zhendong
Judy (Ericsson) responds.
Thomas replies to zhendong
Thomas provides r03
LiMeng (Huawei) suggests we could work out an agreeable version.
zhendong (ZTE) provides the response on one step and two-steps approach.
Thomas(Nokia) comments that r03 is already doing what is proposed by Limeng.
Judy (Ericsson) does not agree to describe the MBS specific function in 23.501.
==== 8.X, 9.X Revisions Deadline ====
Thomas (Nokia) objects against r01 and r02
Judy (Ericsson) propose to bring the discussion to CC#4 together with 3951
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105177 CR Approval 23.501 CR2696R4 (Rel-17, 'B'): N4 extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103907r01, merging S2-2103946. CC#4: Approved Agreed
8.9 S2-2103945 CR Approval 23.501 CR2689R1 (Rel-17, 'B'): 5MBS architecture Nokia (?), Nokia Shanghai Bell (?), Ericsson, LG Electronics Rel-17 Revision of (Agreed) S2-2102126. Confirm Sources! r01 agreed. Revised to S2-2104963. Judy (Ericsson) provide r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104963 CR Approval 23.501 CR2689R2 (Rel-17, 'B'): 5MBS architecture Nokia (?), Nokia Shanghai Bell (?), Ericsson, LG Electronics Rel-17 Revision of S2-2103945r01. Approved Agreed
8.9 S2-2103946 CR Approval 23.501 CR2696R3 (Rel-17, 'B'): N4 extensions for 5MBS Nokia (?), Nokia Shanghai Bell (?), Ericsson Rel-17 Revision of (Agreed) S2-2103528. Confirm Sources! Merged into S2-2105177 LiMeng (Huawei) suggests to merge this one into S2-2103907.
Judy (Ericsson) is OK to merge 3946 to 3907
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104003 CR Approval 23.501 CR2877 (Rel-17, 'B'): NRF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Noted LiMeng (Huawei) provides r01, due to the on-going discussion with on SMF selection issue.
Judy (Ericsson) corrects the subject, and comment
LiMeng (Huawei) agrees the subject is incorrect and thanks Judy for the correction.
Thomas (Nokia) replies to Judy
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comments that the enhancement to NRF is already captured in self-contained spec 23.247 and should not be repeated in 23.501, thus does not agree to this paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104008 CR Approval 23.501 CR2878 (Rel-17, 'B'): UDM extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Noted Judy (Ericsson) comments that UDM enhancement should not be repeated in 23.501, as the enhancement is already specified in the self-contained spec 23.247.
LiMeng (Huawei) suggests to document 502 counterpart (i.e., S2-2104784).
Thomas (Nokia) accepts to note S2-2104008
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104016 CR Approval 23.501 CR2880 (Rel-17, 'B'): PCF impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 r02 agreed. Revised to S2-2104964. Judy (Ericsson) provides r01
LaeYoung (LGE) provides r02.
Thomas(Nokia) accepts r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104964 CR Approval 23.501 CR2880R1 (Rel-17, 'B'): PCF impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104016r02. Approved Agreed
8.9 S2-2104193 CR Approval 23.501 CR2906 (Rel-17, 'B'): Clarify SMF discovery and selection for MBS. And adding MB-SMF, MB-UPF discovery and selection ZTE Rel-17 Noted LiMeng (Huawei) provides r01.
Thomas (Nokia) suggest to note this contribution
Judy (Ericsson) comments that the MBS specific function should be captured in the self-contained spec 23.247 without repeating it in 23.501.
zhendong (ZTE) provides r02.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comments that enhancement in SMF discovery (if needed) should be captured in the self-contained spec 23.247 and should not be repeated in 23.501, thus does not agree to this paper.
zhendong (ZTE) provides the response to judy for further thinking.
Judy (Ericsson) responds to Zhendong.
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104007 CR Approval 23.502 CR2756 (Rel-17, 'B'): NRF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 r01 agreed. Revised to S2-2104965. LiMeng (Huawei) provides r01, due to the on-going discussion with on SMF selection issue.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104965 CR Approval 23.502 CR2756R1 (Rel-17, 'B'): NRF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104007r01. Approved Agreed
8.9 S2-2104010 CR Approval 23.502 CR2758 (Rel-17, 'B'): SMF discovery for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Postponed LiMeng (Huawei) comments that S2-2104003, S2-2104193, S2-2104007, S2-2104010, S2-2104784, S2-2104322, S2-2104300 are related to AMF finding MBS capable SMF, therefore the result should be aligned.
Thomas(Nokia) suggest postponing the issue, have some editor´s notes in 23.247 but remove remaining changes.
Request to postpone S2-2104010
==== 8.X, 9.X Revisions Deadline ====
LiMeng (Huawei) is OK to postpone this document.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104782 CR Approval 23.502 CR2877 (Rel-17, 'B'): UDR extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Postponed Judy (Ericsson) comments that this paper depends the ongoing PCF discussion.
Thomas(Nokia) provides r01 and suggest to wait if related 23.247 CRs are agreed before postponing.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) propose to postpone this paper to next meeting when we have more stable input of PCC solution.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104784 CR Approval 23.502 CR2757R2 (Rel-17, 'B'): UDM extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (withdrawn) S2-2104009. Confirm CR Revision - CR states 1! Postponed LiMeng (Huawei) provides r01, due to the on-going discussion with on SMF selection issue.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comment that there is no agreement on proposal to introduce MBS Session subscription data, therefore does not agree to this paper and propose to note or postpone.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104785 CR Approval 23.502 CR2878 (Rel-17, 'B'): BSF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Postponed LiMeng (Huawei) provides r01.
Judy (Ericsson) comments this paper depends on ongoing PCF discussion
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) proposes to postpone this paper as there is discussion whether BSF registration/discovery is really needed.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104017 CR Approval 23.503 CR0579 (Rel-17, 'B'): PCC impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Postponed LiMeng (Huawei) suggests to postpone this document.
Thomas (Nokia) agrees to postpone this document, bur requests that issue is mentioned in the exception sheet,
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - Architectural, functionalities and principles - - Docs:=40 -
8.9 S2-2104200 P-CR Approval 23.247: Clean up on the 5MBS terminology. ZTE Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2103947 P-CR Approval 23.247: Update [4.1] Potential issue of Individual MBS traffic delivery and its Mitigation Ericsson Rel-17 Noted LiMeng (Huawei) doubts the necessity of this document.
Judy (Ericsson) believes this paper is necessary to give some warning to the operator regarding the possible consequence to apply indvidual delivery
Zhenhua (vivo) have similar concern with Meng (Huawei)
Thomas (Nokia) have similar concern with Meng (Huawei)
Judy (Ericsson) does not understand the concern expressed by companies on a NOTE that makes the possible consequence of individual delivery visible and gives guideline to operator for their deployment choice.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104056 P-CR Approval 23.247: Clause 4.1: Clarification on Individual delivery. LG Electronics Rel-17 r03 agreed. Revised to S2-2104966. Judy (Ericsson) comments
LaeYoung (LGE) provides r01.
Zhenhua (vivo) ask Q for r01.
LaeYoung (LGE) provides r02.
Thomas (Nokia) provides r03.
LaeYoung (LGE) is fine with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104966 P-CR Approval 23.247: Clause 4.1: Clarification on Individual delivery. LG Electronics Rel-17 Revision of S2-2104056r03. Approved Approved
8.9 S2-2104233 P-CR Approval 23.247: Update on principles. vivo Rel-17 r04 agreed. Revised to S2-2104967. Judy (Ericsson) comments
Zhenhua (vivo) replies Judy (Ericsson) and provides r01
Judy (Ericsson) responds to Zhenhua
Zhenhua (vivo) replies to Judy (Ericsson)
Judy (Ericsson) responds to Zhenhua and provide r02
LiMeng (Huawei) provides r03
Youngkyo(Samsung) provide r04
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) is OK with r02, r03 & r04, and does not accept r01
LiMeng (Huawei) is OK with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104967 P-CR Approval 23.247: Update on principles. vivo Rel-17 Revision of S2-2104233r04. Approved Approved
8.9 S2-2104234 P-CR Approval 23.247: Update on multicast data provisioning. vivo Rel-17 r03 agreed. Revised to S2-2104968. Judy (Ericsson) comments
Youngkyo(Samsung) provides comment
Zhenhua (vivo) replise and provide r01
Thomas (Nokia) comments
Zhenhua (vivo) replise to Thomas (Nokia) and provides r02
Judy (Ericsson) provide r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104968 P-CR Approval 23.247: Update on multicast data provisioning. vivo Rel-17 Revision of S2-2104234r03. Approved Approved
8.9 S2-2104235 P-CR Approval 23.247: Update on broadcast data provisioning. vivo Rel-17 Postponed Judy (Ericsson) comment that the change in this paper is not correct as the state model is not applicable for broadcast communication, and propose to note this paper.
Zhenhua (vivo) replise to Judy (Ericsson) and propose to postpone this paper
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2103786 P-CR Approval 23.247: TS 23.247: Authorization alignment of 5MBS Session . Panasonic Corporation, DENSO CORPORATION, Huawei Rel-17 r01 agreed. Revised to S2-2104969. Judy (Ericsson) ask question
LiMeng (Huawei) provides r01.
LiuWei (Panasonic) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104969 P-CR Approval 23.247: TS 23.247: Authorization alignment of 5MBS Session . Panasonic Corporation, DENSO CORPORATION, Huawei Rel-17 Revision of S2-2103786r01. Approved Approved
8.9 S2-2104237 P-CR Approval 23.247: Update UE authorization for multicast. vivo Rel-17 Revision of (Noted) S2-2102667. Noted Judy (Ericsson) comments this paper depends on the discussion in 4240 regarding whether it is needed and how the solution can work
LaeYoung (LGE) comments that she believes that 4242 instead of 4240 is related to this pCR, so we need to see the outcome of 4242.
Judy (Ericsson) thanks LaeYoung for fixing the subject, and comment that this paper depends on the discussion in 4240 regarding whether it is needed and how the solution can work.
LaeYoung (LGE) comments that this paper looks related to both 4240 and 4242.
Zhenhua (vivo) replise to Judy (Ericsson) and LaeYoung (LGE)
LaeYoung (LGE) got the point and agrees that this pCR is related only to 4240.
Thomas (Nokia) comments against justification of PCR.
Zhenhua (vivo) replise to Thomas (Nokia).
Thomas (Nokia) asks what the justification of the CR is
Zhenhua (vivo) reponse to Thomas (Nokia)
Thomas (Nokia) replies to Zhenhua
Zhenhua (vivo) answers to Thomas (Nokia)
Thomas (Nokia) replies to Zhenhua (vivo)
Zhenhua (vivo) replies
Zhenhua (vivo) replies to Thomas (Nokia)
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) proposes to NOTE this pCR because the related pCR, 4240 is expected to be NOTED.
Thomas (Nokia) supports noting the PCR
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2103948 P-CR Approval 23.247: Update [5.3.1] Reference Point to Resolve EN. Ericsson Rel-17 Merged into S2-2104970 LiMeng (Huawei) suggests to merge this document into S2-2104310.
Judy (Ericsson) agrees to merge 3948 into 4310
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104298 P-CR Approval 23.247: MBS Functional Entities Clarification. Tencent Rel-17 Merged into S2-2104970 LiMeng (Huawei) suggests to merge this document into S2-2104310.
Judy (Ericsson) agrees to merge 4298 to 4310.
Judy (Ericsson) corrects that 4298 is meant to be 3948 which should be in another thread and request to ignore the previous comment.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104310 P-CR Approval 23.247: TS 23.247: Clarification on description of the NFs. Huawei, HiSilicon, CBN Rel-17 r01 agreed. Revised to S2-2104970, merging S2-2103948 and S2-2104298 Judy (Ericsson) provide r01 merging 3948 into this one (i.e. 4310)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104970 P-CR Approval 23.247: TS 23.247: Clarification on description of the NFs. Huawei, HiSilicon, CBN Rel-17 Revision of S2-2104310r01, merging S2-2103948, merging S2-2103948 and S2-2104298. Approved Approved
8.9 S2-2103949 P-CR Approval 23.247: Update [5.1][5.3] Architecture and Reference Point. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2103951 P-CR Approval 23.247: Update [6.7] User Plane Management. Ericsson Rel-17 CC#4: r01 with changes agreed. Revised to S2-2105176. LiMeng (Huawei) asks to discuss S2-2103907 and S2-2103951 together and comments.
Judy (Ericsson) is fine with LiMeng' proposal and suggest to add also 3946 (i.e. 3951, 3907 and 3946 are discussed together)
LiMeng (Huawei) agrees with Judy to discuss the related documents (3951, 3907 and 3946) together.
Judy (Ericsson) provides r01
Thomas (Nokia) raises concerns against r00 and r01 and provides r02
Judy (Ericsson) does not agree to r02 which removes the MBS specific UP management function, and moved it to 23.501.
Thomas(Nokia) suggest postponing the CR
Judy (Ericsson) proposes to progress 3951 (on 23.247) to avoid introducing a new clause in 23.501 in one meeting, and void it in the next meeting
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) proposes to bring the discussion to CC#4.
Thomas (Nokia) agrees to bring the discussion to CC#4.
Idea is to document the current solution completely in 23.247, see late rev3 based on rev1
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105176 P-CR Approval 23.247: Update [6.7] User Plane Management. Ericsson Rel-17 Revision of S2-2103951r01 with changes. CC#4: Approved Approved
8.9 S2-2104430 P-CR Approval 23.247: User plane management. Tencent Rel-17 r04 agreed. Revised to S2-2104971. Judy (Ericsson) ask questions.
LiMeng (Huawei) replies to Judy.
Judy (Ericsson) comments
LiMeng (Huawei) is fine with the wording proposed by Judy.
Thomas (Nokia) provides r01.
Chunshan (Tencent) provides r02.
Youngkyo(Samsung) provides comment
Judy (Ericsson) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104971 P-CR Approval 23.247: User plane management. Tencent Rel-17 Revision of S2-2104430r04. Approved Approved
8.9 S2-2103950 P-CR Approval 23.247: Update to [6.6] QoS handling. Ericsson Rel-17 Postponed Fenqin (Huawei) comment
Judy (Ericsson) responds to Fenqin
Fenqin (Huawei) responds and provides r01
Judy (Ericsson) comments that the added text in r01 may change the behavior specified 23.503 and provides r02.
Thomas (Nokia) raises concerns against the CR
Judy (Ericsson) responds and wonders if there is a misunderstanding.
Thomas(Nokia) replies to Judy
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) responds to Thomas
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104054 P-CR Approval 23.247: Requested MBS QoS and Dynamic PCC. Tencent Rel-17 Revision of (Postponed) S2-2102724. r03 agreed. Revised to S2-2104972. Haris(Qualcomm) provides r01
Chunshan (Tencent) is OK with r01
Thomas (Nokia) provides r02
Fenqin (Huawei) comments
Thomas (Nokia) replies to Fenqin
Judy (Ericsson) provide r03
Judy (Ericsson) responds
Chunshan (Tencent) response.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) accepts r03, objects to other revisions.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104972 P-CR Approval 23.247: Requested MBS QoS and Dynamic PCC. Tencent Rel-17 Revision of S2-2104054r03. Approved Approved
8.9 S2-2104055 P-CR Approval 23.247: MBS Session-AMBR. Tencent Rel-17 Revision of (Postponed) S2-2102725. r02 agreed. Revised to S2-2104973. Haris(Qualcomm) provides comments
Judy (Ericsson) comments and provide r01
Thomas (Nokia) comments and provide r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104973 P-CR Approval 23.247: MBS Session-AMBR. Tencent Rel-17 Revision of S2-2104055r02. Approved Approved
8.9 S2-2104057 P-CR Approval 23.247: Clause 5.3.2.2: TMGI allocation by MB-SMF. LG Electronics Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2104199 P-CR Approval 23.247: Adding clause 8, Protocol stack description. ZTE Rel-17 CC#5: r01 + changes agreed. Revised to S2-2105212. Judy (Ericsson) comments
LiMeng (Huawei) provides r01.
zhendong (ZTE) is fine with r01.
==== 8.X, 9.X Revisions Deadline ====
Thomas (Nokia) proposes to postpone the contribution
zhendong (ZTE) provides the response, and hope we can move with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105212 P-CR Approval 23.247: Adding clause 8, Protocol stack description. ZTE Rel-17 Revision of S2-2104199r01 + changes. Approved Approved
8.9 S2-2104308 P-CR Approval 23.247: TS 23.247: Clarification on Architecture parts in Annex A. Huawei, HiSilicon, CBN Rel-17 r01 agreed. Revised to S2-2104974. Judy (Ericsson) comment that this paper has a dependency with proposed change in 3949
LiMeng (Huawei) agrees names in 3949 and 4308 should be aligned.
LiMeng (Huawei) provides r01 to align 3949.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104974 P-CR Approval 23.247: TS 23.247: Clarification on Architecture parts in Annex A. Huawei, HiSilicon, CBN Rel-17 Revision of S2-2104308r01. Approved Approved
8.9 S2-2104427 P-CR Approval 23.247: MBS Session Policy Binding. Tencent Rel-17 r01 agreed. Revised to S2-2104975. Judy (Ericsson) comments this paper depends on the discussion of PCF interaction, and ask question.
Chunshan (Tencent) responses.
Thomas (Nokia) provides r01.
Chunshan (Tencent) response.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104975 P-CR Approval 23.247: MBS Session Policy Binding. Tencent Rel-17 Revision of S2-2104427r01. Approved Approved
8.9 S2-2104429 P-CR Approval 23.247: Source Special IP Multicast Address. Tencent Rel-17 r02 agreed. Revised to S2-2104976. Judy (Ericsson) provide r01
Chunshan (Tencent) responses.
Thomas (Nokia) provide r02
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104976 P-CR Approval 23.247: Source Special IP Multicast Address. Tencent Rel-17 Revision of S2-2104429r02. Approved Approved
8.9 S2-2103953 P-CR Approval 23.247: Update to [7.1.2] MB-SMF Discovery. Ericsson Rel-17 r04 agreed. Revised to S2-2104977. Xiaoyan (CATT) provides r01.
Judy (Ericsson) responds to Xiaoyan and provide r02
Thomas(Nokia) provide r03
Thomas(Nokia) provide r04.
Judy (Ericsson) comments
Thomas(Nokia) corrects that Xiaoyan(CATT) provided r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104977 P-CR Approval 23.247: Update to [7.1.2] MB-SMF Discovery. Ericsson Rel-17 Revision of S2-2103953r04. Approved Approved
8.9 S2-2104192 P-CR Approval 23.247: Update clause 7.1.2 MB-SMF discovery and selection and adding new clause on MB-UPF discovery and selection. ZTE Rel-17 r01 agreed. Revised to S2-2104978. Judy (Ericsson) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104978 P-CR Approval 23.247: Update clause 7.1.2 MB-SMF discovery and selection and adding new clause on MB-UPF discovery and selection. ZTE Rel-17 Revision of S2-2104192r01. Approved Approved
8.9 S2-2104346 P-CR Approval 23.247: Corrections to Clause 7.1.2 MB-SMF selection. Nokia, Nokia Shanghai-Bell Rel-17 Postponed Xiaoyan (CATT) provides comments and disagrees with the approach proposed by the pCR.
Judy (Ericsson) has a major concern on the proposal.
Thomas (Nokia) replies to Judy and Xiaoyan
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comments there is no procedure clarifying how the proposal works therefore does not agree to this paper, and propose to postpone.
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - RAN capability related - - Docs:=12 -
8.9 S2-2104179 P-CR Approval 23.247: Discussion and proposal on the awareness of NG-RAN MBS capability in the AMF. ZTE Rel-17 Approved Fenqin (Huawei) propose to note this paper.
zhendong (ZTE) provides the response.
==== 8.X, 9.X Revisions Deadline ====
zhendong (ZTE) clarify this paper can be agreed.
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2104185 P-CR Approval 23.247: Discussion and proposal on the SMF awareness of the NG-RAN MBS capability. ZTE Rel-17 Noted Fenqin (Huawei) propose to note this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104238 P-CR Approval 23.247: TS 23.247: MBS Session Join and Establishment. vivo Rel-17 Merged into S2-2104984 Zhenhua (vivo) propose to merge this document into S2-2104284.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104394 P-CR Approval 23.247: NG-RAN 5MBS Capability awareness. Huawei, HiSilicon Rel-17 r01 agreed. Revised to S2-2104979. Paul (Ericsson) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104979 P-CR Approval 23.247: NG-RAN 5MBS Capability awareness. Huawei, HiSilicon Rel-17 Revision of S2-2104394r01. Approved Approved
8.9 S2-2104423 P-CR Approval 23.247: MBS Session Join and Establishment. SAMSUNG Rel-17 Merged into S2-2104984 Fenqin (Huawei) propose to merge this paper with 4284
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104197 P-CR Approval 23.247: Modification on the mobility clause 6.3.1 and 7.2.3. ZTE Rel-17 r06 agreed. Revised to S2-2104980, merging S2-2104432 Paul (Ericsson) provides r01.
zhendong (ZTE) provides the response.
Zhenhua (vivo) provides r02.
Fenqin (Huawei) provides r03.
Thomas (Nokia) provides r04.
Paul (Ericsson) provides r05.
Fenqin (Huawei) ask same question .
Paul (Ericsson) replies to Fenqin (Huawei).
Fenqin (Huawei) provides r06.
zhendong (ZTE) has the same question with fenqin.
Fenqin (Huawei) replies to Paul (Ericsson).
zhendong (ZTE) propose moving with fenqin proposal.
Thomas (Nokia) provides r07.
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) objects to r07.
TAO(VC) let's check r06 then, or other version agreeable please indicate clearly
Thomas(Nokia) can agree r06
Paul (Ericsson), we prefer r05 but can accept r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104980 P-CR Approval 23.247: Modification on the mobility clause 6.3.1 and 7.2.3. ZTE Rel-17 Revision of S2-2104197r06, merging S2-2104432. Approved Approved
8.9 S2-2104239 P-CR Approval 23.247: Update on mobility procedures. vivo Rel-17 Noted Fenqin (Huawei) propose to note this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104398 P-CR Approval 23.247: Xn/N2 based handover from non-MBS supporting NG-RAN. Huawei, HiSilicon Rel-17 r10 agreed. Revised to S2-2104981. Paul (Ericsson) provides r01.
Fenqin (Huawei) provides r02.
Zhenhua (vivo) provides r03.
zhendong (ZTE) provides the comments.
Fenqin (Huawei) responds.
Paul (Ericsson) provides r04.
Fenqin (Huawei) ask question for clarification .
Paul (Ericsson) replies to Fenqin's (Huawei) question.
Fenqin (Huawei) do some cleanup and provides r05
Miguel (Qualcomm) can't see either how configuration would work in Xn handover, and asks for clarification
Thomas(Nokia) shares the concerns of Miguel and raises additional concerns for N2 based handover
Fenqin (Huawei) provides r06
zhendong (ZTE) provides r07.
Thomas (Nokia) is fine with r06
Paul (Ericsson) provides r08.
zhendong (ZTE) provides r09.
Fenqin (Huawei) provides r10.
==== 8.X, 9.X Revisions Deadline ====
zhendong (ZTE) is fine go with r10.
Paul (Ericsson) can accept r10.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104981 P-CR Approval 23.247: Xn/N2 based handover from non-MBS supporting NG-RAN. Huawei, HiSilicon Rel-17 Revision of S2-2104398r10. Approved Approved
8.9 S2-2104432 P-CR Approval 23.247: Handover procedures for multicast MBS Session. SAMSUNG Rel-17 Merged into S2-2104980 Fenqin (Huawei) propose to merge this paper with 4197
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - General Join/leave and establishment/release - - Docs:=19 -
8.9 S2-2103958 P-CR Approval 23.247: New [7.2.2.X] SMF Removing Joined UEs from MBS Session. Ericsson Rel-17 r03 agreed. Revised to S2-2104982, merging S2-2104396 Judy (Ericsson) provides r01, taking group paging handling from 4396 into consideration
Fenqin (Huawei) comments and provides r02.
Judy (Ericsson) provide r03
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104982 P-CR Approval 23.247: New [7.2.2.X] SMF Removing Joined UEs from MBS Session. Ericsson Rel-17 Revision of S2-2103958r03, merging S2-2104396. Approved Approved
8.9 S2-2104018 P-CR Approval 23.247: Shared delivery establishment and support of subsequent signalling from MB-SMF. Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-17 Revision of (Postponed) S2-2102941. r04 agreed. Revised to S2-2104983, merging S2-2104194 zhendong (ZTE) provides r01 .
Judy (Ericsson) provide r02 updating the comparison in Discussion.
Zhenhua (vivo) provide r03.
zhendong (ZTE) provides r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104983 P-CR Approval 23.247: Shared delivery establishment and support of subsequent signalling from MB-SMF. Nokia, Nokia Shanghai Bell, Huawei, HiSilicon Rel-17 Revision of S2-2104018r04, merging S2-2104194. Approved Approved
8.9 S2-2104194 P-CR Approval 23.247: Adding clause 7.2.5 on the shared delivery tunnel handling. ZTE Rel-17 Merged into S2-2104983 LiMeng (Huawei) suggests to merge this document into S2-2104018.
zhendong (ZTE) is fine with the merge proposal.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104196 P-CR Approval 23.247: Removing clause 7.2.1.4, MBS join and Session establishment procedure involving MBSF. ZTE Rel-17 Merged into S2-2104984 LiMeng (Huawei) suggests to merge this document into S2-2104284.
zhendong (ZTE) is fine with rapporteur proposal .
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104240 P-CR Approval 23.247: UE authorization procedure. vivo Rel-17 Revision of (Noted) S2-2102677. Noted LaeYoung (LGE) does not think that the procedure in this pCR needs to be captured separately, so proposes to NOTE this pCR.
Judy (Ericsson) share similar view as LaeYoung and additional comments
Zhenhua (vivo) replies
LaeYoung (LGE) provides comment.
Zhenhua (vivo) replies.
LaeYoung (LGE) replies to Zhenhua (vivo).
Fenqin (Huawei) ask question for clarification
Zhenhua (vivo) replies to Fenqin (Huawei)
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) cannot accept a new procedure represented by a text box, thus does not agree with this paper
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104284 P-CR Approval 23.247: Updates to MBS Session Join procedure. CATT Rel-17 Revision of (Endorsed) S2-2103074. r10 agreed. Revised to S2-2104984, merging S2-2104196, S2-2104238, S2-2104301, S2-2104307, S2-2104311, S2-2104322, S2-2104327 and S2-2104423 Xiaoyan (CATT) provides S2-2104284r01, merging S2-2104196/4307/4311/4327/4301.
LaeYoung (LGE) asks some questions for clarification.
Xiaoyan (CATT) provides r02.
Youngkyo(Samsung) ask a question
LiMeng (Huawei) replies.
Zhenhua (vivo) provides r03.
Fenqin (Huawei) provides r04.
LaeYoung (LGE) provides r05.
Thomas (Nokia) provides r06.
Miguel (Qualcomm) provides r07
Judy (Ericsson) provide r08
Xiaoyan (CATT) provide r09.
Judy (Ericsson) provide r10.
Xiaoyan (CATT) provide r11.
zhendong (ZTE) provides r12.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) prefer r10, does not accept r11/r12 as is, and object to other revisions.
Xiaoyan (CATT) can live with r10.
zhendong (ZTE) provdies the r13, it will be discussed in the CC#3.
LiMeng (Huawei) prefers to use the current provided version (e.g., r10/r12) rather than generating a new version adding the two ENs.
LiMeng (Huawei) suggests we go with r10 and cannot accept the 2nd EN of r13. This document doesn't need to appear in CC#4.
Thomas(Nokia) can accept r10.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104984 P-CR Approval 23.247: Updates to MBS Session Join procedure. CATT Rel-17 Revision of S2-2104284r10, merging S2-2104196, merging S2-2104196 and S2-2104238, merging S2-2104196, S2-2104238 and S2-2104301, merging S2-2104196, S2-2104238, S2-2104301 and S2-2104307, merging S2-2104196, S2-2104238, S2-2104301, S2-2104307 and S2-21043 Approved
8.9 S2-2104301 P-CR Approval 23.247: MBS Join and Session Establishment Procedure Clarification. Tencent Rel-17 Merged into S2-2104984 LiMeng (Huawei) suggests to merge this document into S2-2104284.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104307 P-CR Approval 23.247: TS 23.247: MBS Session Join and Establishment. Huawei, HiSilicon, CBN Rel-17 Merged into S2-2104984 LiMeng (Huawei) suggests to merge this document into S2-2104284.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104395 P-CR Approval 23.247: MBS session leave correction. Huawei, HiSilicon Rel-17 r05 agreed. Revised to S2-2104985. Judy (Ericsson) provides r01
Youngkyo(Samsung) provides r02
Zhenhua (vivo) provides r03
Fenqin (Huawei) provides r04
Zhenhua (vivo) provides r05
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104985 P-CR Approval 23.247: MBS session leave correction. Huawei, HiSilicon Rel-17 Revision of S2-2104395r05. Approved Approved
8.9 S2-2104396 P-CR Approval 23.247: MBS session release. Huawei, HiSilicon Rel-17 Merged into S2-2104982 Judy (Ericsson) propose to merge 4396 into 3958 which has been updated to consider the group paging in 4396.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104311 P-CR Approval 23.247: TS 23.247: on MB-UPF joining the multicast tree. Huawei, HiSilicon Rel-17 Merged into S2-2104984 LiMeng (Huawei) suggests to merge this document into S2-2104284.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104322 P-CR Approval 23.247: 5MBS Information in UDM. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2104984 Xiaoyan (CATT) proposes to merge S2-2104322 into S2-2104284.
Thomas (Nokia) accepts the merge proposal.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104327 P-CR Approval 23.247: Corrections to Clause 7.2.1.3 to allow a simultaneous join for several multicast sessions. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2104984 LiMeng (Huawei) suggests to merge this document into S2-2104284.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104760 P-CR Approval 23.247: Determining the DNN and/or S-NSSAI for the associated PDU session of a Multicast session. Qualcomm Rel-17 Postponed LiMeng (Huawei) asks question.
Judy (Ericsson) ask questions
Miguel (Qualcomm) replies to LiMeng and Judy
LiMeng (Huawei) replies to Miguel
Thomas (Nokia) provides additional comments
Zhenhua (vivo) has simiar concern as Thomas (Nokia)
Miguel (Qualcomm) volunteers to postpone this contribution
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104763 P-CR Approval 23.247: Corrections to Clause 7.2.1.3 to address PCF interactions. Nokia, Nokia Shanghai-Bell Rel-17 Postponed LiMeng (Huawei) suggests to postpone this document.
Thomas (Nokia) accepts to postpone this document but requests an editor´s note
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - Session states and Activation/Deactivation - - Docs:=10 -
8.9 S2-2103954 P-CR Approval 23.247: New [7.2.x] MBS Session Activate and Deactivate. Ericsson Rel-17 Merged into S2-2105191 LiMeng (Huawei) suggests to merge this document into S2-2104306.
Judy (Ericsson) agrees to merge 3954 to 4306
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104241 P-CR Approval 23.247: Activation and deactivation procedures. vivo Rel-17 Merged into S2-2105191 LiMeng (Huawei) suggests to merge this document into S2-2104306.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104306 P-CR Approval 23.247: TS 23.247: Session activation/deactivation for MBS. Huawei, HiSilicon, CBN Rel-17 CC#5: r06 + changes agreed. Revised to S2-2105191, merging S2-2103954, S2-2104241 and S2-2104413. LiMeng (Huawei) provides r01.
Zhenhua (vivo) provides r02.
Judy (Ericsson) provides r03
Judy (Ericsson) provide r04
Thomas (Nokia) provide r05
LiMeng (Huawei) provides r06
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) is fine with r03/r04/r05, does not accept r06 as is and request to remove 'may' in step 2 of 7.2.5.3, object to other revisions.
LiMeng (Huawei) proposes to bring the discussion to CC#4.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105191 P-CR Approval 23.247: TS 23.247: Session activation/deactivation for MBS. Huawei, HiSilicon, CBN Rel-17 Revision of S2-2104306r06 + changes, merging S2-2103954, S2-2104241 and S2-2104413. Approved Approved
8.9 S2-2104413 P-CR Approval 23.247: Multicast session start/stop/update&activation/de-activation/modification procedures. SAMSUNG Rel-17 Merged into S2-2105191 LiMeng (Huawei) suggests to merge this document into S2-2104306.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104236 P-CR Approval 23.247: Update on state model. vivo Rel-17 Merged into S2-2104986 LiMeng (Huawei) suggests to merge this document into S2-2104281.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104281 P-CR Approval 23.247: MBS Session state model. CATT Rel-17 r08 agreed. Revised to S2-2104986, merging S2-2104236 Zhenhua (vivo) provides r01 to merge 4236.
LiMeng (Huawei) comments on r01.
Xiaoyan (CATT) provides r02.
Zhenhua (vivo) replies.
Zhenhua (vivo) comments on r02.
Thomas (Nokia) provides r03.
Judy (Ericsson) comments
Xiaoyan (CATT) replies to Judy (Ericsson).
Thomas (Nokia) replies to Judy
LiMeng (Huawei) tries to clarify the multicast session release procedure.
LiMeng (Huawei) provides r04 to separate the discussion of AF-triggered option.
Judy (Ericsson) comments and provide r05 and responds
Xiaoyan (CATT) provides r06.
Youngkyo(Samsung) asks a question.
Xiaoyan (CATT) replies to Youngkyo (Samsung).
Zhenhua (vivo) asks a question.
Zhenhua (vivo) replise to Xiaoyan (CATT).
Zhenhua (vivo) provides r07.
Judy (Ericsson) provide r08
Xiaoyan (CATT) provides r08.
Xiaoyan (CATT) clarifies that CATT provides r09 instead of r08.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) prefers r05/r08, does not accept r09 as is (except with two ENs) and objects to other revisions.
Tao(VC) let's check r08 then
Xiaoyan (CATT) can live with r08.
Thomas(Nokia) accepts r08
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104986 P-CR Approval 23.247: MBS Session state model. CATT Rel-17 Revision of S2-2104281r08, merging S2-2104236. Approved Approved
8.9 S2-2104279 P-CR Approval 23.247: Clarification on notification of multicast session activation. CATT Rel-17 r02 agreed. Revised to S2-2104987. LiMeng (Huawei) provides r01.
Xiaoyan (CATT) provides r02.
Zhenhua (vivo) questions on r02 and prefer r01.
Xiaoyan (CATT) asks Zhenhua (vivo) for clarification.
Zhenhua (vivo) replies.
Xiaoyan (CATT) clarifies to Zhenhua (vivo).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104987 P-CR Approval 23.247: Clarification on notification of multicast session activation. CATT Rel-17 Revision of S2-2104279r02. Approved Approved
8.9 - - - AF-triggered UE join procedure - - Docs:=3 -
8.9 S2-2103977 P-CR Approval 23.247: AF-triggered join/leave for multicast sessions. Juniper Networks Rel-17 Revision of (Postponed) S2-2102310. Merged into S2-2104242 (Postponed) LiMeng (Huawei) comments and suggests to merge this document into S2-2104242.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104242 P-CR Approval 23.247: AF requested multicast session management procedure. vivo Rel-17 Revision of (Postponed) S2-2102678. CC#5: This was postponed. LiMeng (Huawei) provides r01 and asks for clarification.
LaeYoung (LGE) does not think the proposed procedure works.
Jeffrey (Juniper) provides comments and r02
LiMeng (Huawei) comments.
Zhenhua (vivo) provides r03 based on r01.
Judy (Ericsson) comments
Zhenhua (vivo) replies to Judy (Ericsson) and provides r04.
Thomas (Nokia) comments
LaeYoung (LGE) asks a Q.
Zhenhua (vivo) replies to Thomas (Nokia)
Zhenhua (vivo) provides r05 and replise to LaeYoung (LGE).
Haris(Qualcomm) suggests to note the paper
Zhenhua (vivo) replies to Thomas (Nokia) and Harisz (Qualcomm) and provides r06
Zhenhua (vivo) asks Haris(Qualcomm) to reconsider the position
Jeffrey (Juniper) asks Haris(Qualcomm) to reconsider the position
Aihua(China Mobile) replies and asks Haris(Qualcomm) to reconsider the position
Zhenhua (vivo) provides r07 according to comments from Aihua(China Mobile)
Haris(Qualcomm) comments
Zhenhua (vivo) ask Q to Haris(Qualcomm)
==== 8.X, 9.X Revisions Deadline ====
Thomas(Nokia) proposes to note the contribution
Zhenhua (vivo) asks Q for Thomas(Nokia)
Zhenhua (vivo) replise to Haris(Qualcomm)
Jeffrey (Juniper) follows up on Zhenhua (vivo) replise to Haris(Qualcomm) and Thomas.
Jeffrey (Juniper) requests Thomas (Nokia) to reconsider his 'note' proposal.
Zhenhua (vivo) follows up Jeffrey (Juniper) to ask Thomas (Nokia) whether OK to have the EN added.
Aihua(China Mobile) replies Thomas (Nokia).
Zhenhua (vivo) propose to bring this to CC#4
Thomas(Nokia) replies to Jeffrey
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104227 P-CR Approval 23.247: 5MBS dynamic multicast transmission triggered by AF. China Mobile, vivo Rel-17 Merged into S2-2104242 (Postponed) LiMeng (Huawei) suggests to merge this document into S2-2104242.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 - - - Local Multicast/Broadcast services - - Docs:=11 -
8.9 S2-2103975 P-CR Approval 23.247: Update [6.2] Local MBS. Ericsson Rel-17 Merged into S2-2104990 LiMeng (Huawei) suggests to merge this document into S2-2104299.
Robbie (Ericsson) agrees to merge 3975 to 4299.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104064 P-CR Approval 23.247: Clause 7.2.4.3.2: MBS service area in Join Accept for local multicast. LG Electronics Rel-17 r04 agreed. Revised to S2-2104988, merging S2-2104283 LaeYoung (LGE) provides r01 that covers clauses 7.2.4.1, 7.2.4.3.1 and 7.2.4.3.2.
Xiaoyan (CATT) asks for clarification.
LaeYoung (LGE) provides r02.
Xiaoyan (CATT) provides r03.
LaeYoung (LGE) is fine with r03.
Youngkyo(Samsung) asks a question
LaeYoung (LGE) replies to Youngkyo(Samsung).
Youngkyo(Samsung) replies to LaeYoung
LaeYoung (LGE) answers to Youngkyo(Samsung).
Zhenhua (vivo) replies to Youngkyo(Samsung).
zhendong (ZTE) provides the comments.
Judy (Ericsson) provides r04
LaeYoung (LGE) is fine with r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104988 P-CR Approval 23.247: Clause 7.2.4.3.2: MBS service area in Join Accept for local multicast. LG Electronics Rel-17 Revision of S2-2104064r04, merging S2-2104283. Approved Approved
8.9 S2-2104195 P-CR Approval 23.247: Modification clause 7.2.4 on the local multicast MBS procedure. ZTE Rel-17 r13 agreed. Revised to S2-2104989, merging S2-2104323 LiMeng (Huawei) provides r01 and suggests to further discuss the details based on r01.
LaeYoung (LGE) provides r02.
Xiaoyan (CATT) provides r03.
Haris(Qualcomm) provides r04
Zhenhua (vivo) provides r05
Thomas (Nokia) provides r06
LiMeng (Huawei) provides r07.
zhendong (ZTE) provides r08.
Thomas (Nokia) accepts r07.
Paul (Ericsson) provides r09.
Thomas(Nokia) objects against r09
Fenqin (Huawei) provides r10
Paul (Ericsson) provides a response and questions for clarification.
Fenqin (Huawei) provides a response.
Paul (Ericsson) replies to Fenqin (Huawei) and objects to r10.
Fenqin (Huawei) provides a response and provides r12.
zhendong (ZTE) provides the response.
==== 8.X, 9.X Revisions Deadline ====
Xiaoyan (CATT) suggests to agree r13 provided by Zhendong (ZTE) before revision deadline.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104989 P-CR Approval 23.247: Modification clause 7.2.4 on the local multicast MBS procedure. ZTE Rel-17 Revision of S2-2104195r13, merging S2-2104323. Approved Approved
8.9 S2-2104283 P-CR Approval 23.247: Update of local MBS service procedures. CATT Rel-17 Merged into S2-2104988 LiMeng (Huawei) suggests to merge this document into S2-2104064.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104299 P-CR Approval 23.247: Clarification of Local MBS Services. Tencent Rel-17 r01 agreed. Revised to S2-2104990, merging S2-2103975 Robbie (Ericsson) provides r01 merging 3975 into this one (i.e. 4299)
Lei (Tencent) is ok with r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104990 P-CR Approval 23.247: Clarification of Local MBS Services. Tencent Rel-17 Revision of S2-2104299r01, merging S2-2103975. Approved Approved
8.9 S2-2104323 P-CR Approval 23.247: Corrections to Clause 7.2.4 on Local Multicast services. Nokia, Nokia Shanghai-Bell Rel-17 Merged into S2-2104989 LiMeng (Huawei) suggests to merge this document into S2-2104195.
Thomas(Nokia) agrees with merger
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104397 P-CR Approval 23.247: Support of Local MBS. Huawei, HiSilicon Rel-17 r04 agreed. Revised to S2-2104991. Fenqin (Huawei) provides r01.
Zhenhua (vivo) provides r02.
Paul (Ericsson) provides r03.
Fenqin (Huawei) provides r04.
==== 8.X, 9.X Revisions Deadline ====
Paul (Ericsson) accepts r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104991 P-CR Approval 23.247: Support of Local MBS. Huawei, HiSilicon Rel-17 Revision of S2-2104397r04. Approved Approved
8.9 - - - Common procedures/Broadcast management - - Docs:=27 -
8.9 S2-2103976 P-CR Approval 23.247: Update [7.1] Common Procedures initiated by AF . Ericsson Rel-17 r05 agreed. Revised to S2-2104992. LiMeng (Huawei) provides r01 removing 7.1.1.X to avoid overlapping changes.
Judy (Ericsson) provides r02 proposing separate procedures without PCC and with PCC.
Thomas(Nokia) is raising concerns about separate procedures with and without PCC, huge overlap with S2-2104190, and terminology issues
Thomas(Nokia) provides r03
LiMeng (Huawei) is fine with Thomas's proposal.
Judy (Ericsson) prefers to keep PCC and no PCC separate for this meeting for all procedures (initial/update/removal) instead of having PCC and no PCC for update/removal but not for initial, considering that the PCC discussion is still ongoing.
LiMeng (Huawei) prefers to have a single initial procedure.
LiMeng (Huawei) provides r04 based on r00. For an easy merging with the agreed version of 4190.
Thomas(Nokia) provides r05 with separate PCC procedures but prefers r03
Judy (Ericsson) provide r05
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) comment that r05 is provided by Thomas (Nokia)
Judy (Ericsson) accept only r00/r02, objects to other revisions.
LiMeng (Huawei) provides a solution.
Judy (Ericsson) responds to LiMeng
LiMeng (Huawei) responds to Judy
Thomas objects against r00/r01/r02 and r04, explains r05 to Judy and makes a solution proposal
Thomas asks Judy if she withdraws her objection against r05 after offline discussion
Otherwise suggest bringing this to CC4
Judy (Ericsson) can live with r05 after offline discussion
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104992 P-CR Approval 23.247: Update [7.1] Common Procedures initiated by AF . Ericsson Rel-17 Revision of S2-2103976r05. Approved Approved
8.9 S2-2104019 P-CR Approval 23.247: NEF PCF interactions. Nokia, Nokia Shanghai-Bell, Tencent Rel-17 Revision of (Postponed) S2-2102947. Merged into S2-2104993 LiMeng (Huawei) suggests to merge this document into S2-2104190.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104190 P-CR Approval 23.247: Discussion and proposal on the PCC part of configuration procedure in clause 7.1.1. ZTE Rel-17 r08 agreed. Revised to S2-2104993, merging S2-2104019, S2-2104210, S2-2104222 and S2-2104305 LiMeng (Huawei) provides r01.
Thomas (Nokia) provides r02 merging S2-2104019.
Judy (Ericsson) provide r03
LiMeng (Huawei) provide r04
LiMeng (Huawei) provide r05
zhendong (ZTE) provides r06.
Thomas (Nokia) provides r07.
Judy (Ericsson) provides r08
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2104993 P-CR Approval 23.247: Discussion and proposal on the PCC part of configuration procedure in clause 7.1.1. ZTE Rel-17 Revision of S2-2104190r08, merging S2-2104019, merging S2-2104019 and S2-2104210, merging S2-2104019, S2-2104210 and S2-2104222, merging S2-2104019, S2-2104210, S2-2104222 and S2-2104305. Approved Approved
8.9 S2-2104222 P-CR Approval 23.247: Update on initial MBS session configuration. Samsung Rel-17 Merged into S2-2104993 LiMeng (Huawei) suggests to merge this document into S2-2104190.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104305 P-CR Approval 23.247: TS 23.247: Initial MBS session configuration. Huawei, HiSilicon Rel-17 Merged into S2-2104993 LiMeng (Huawei) suggests to merge this document into S2-2104190.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104191 P-CR Approval 23.247: Update the clause 7.1.1.2 to remove the ENs. ZTE Rel-17 Merged into S2-2105162 LiMeng (Huawei) suggests to merge this document into S2-2104228.
zhendong (ZTE) is ok to merge this into S2-2104228.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104228 P-CR Approval 23.247: Update on removal of MBS session configuration. Samsung Rel-17 r02 agreed. Revised to S2-2105162, merging S2-2104191 Judy (Ericsson) comments and provides r01
Youngkyo(Samsung) is okay with r01.
zhendong (ZTE) provides r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105162 P-CR Approval 23.247: Update on removal of MBS session configuration. Samsung Rel-17 Revision of S2-2104228r02, merging S2-2104191. Approved Approved
8.9 S2-2104210 P-CR Approval 23.247: Update of MBS session configuration. SAMSUNG Rel-17 Merged into S2-2104993 LiMeng (Huawei) suggests to merge this document into S2-2104190.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2103955 P-CR Approval 23.247: Update [7.3.3] Broadcast Session Update for Service Requirement Change. Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 S2-2104309 P-CR Approval 23.247: TS 23.247: Session Update Procedures. Huawei, HiSilicon Rel-17 CC#5: r01 + changes agreed. Revised to S2-2105192. LiMeng (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) requests to add an EN to r01 that updating the associated PDU Session's QoS based on the update of MBS Session QoS by NG-RAN requires RAN collaboration.
LiMeng (Huawei) is OK to add the EN to collaborate with RAN, therefore it is suggested to check in CC#4 to confirm the proposed changes.
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105192 P-CR Approval 23.247: TS 23.247: Session Update Procedures. Huawei, HiSilicon Rel-17 Revision of S2-2104309r01 + changes. Approved Approved
8.9 S2-2103956 P-CR Approval 23.247: Update [7.3] Broadcast to Align with Common Procedures. Ericsson Rel-17 r04 agreed. Revised to S2-2105163, merging S2-2104243 and S2-2104416 Robbie (Ericsson) provides r01 with 4243 and 4416 merged
Zhenhua (vivo) provides r02
Youngkyo(Samsung) provides r03
Thomas(Nokia) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105163 P-CR Approval 23.247: Update [7.3] Broadcast to Align with Common Procedures. Ericsson Rel-17 Revision of S2-2103956r04, merging S2-2104243, merging S2-2104243 and S2-2104416. Approved Approved
8.9 S2-2103957 P-CR Approval 23.247: Update [7.3] Broadcast to Resolve ENs about AMF involvement. Ericsson Rel-17 Merged into S2-2105193 LiMeng (Huawei) suggests to merge this document into S2-2104181
Robbie (Ericsson) is OK to merge 3957 to 4181
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104181 P-CR Approval 23.247: Modification clause 7.3 on the Broadcast session management. ZTE Rel-17 CC#4: r03 + changes agreed. Revised to S2-2105193, merging S2-2103957 and S2-2104676. Robbie (Ericsson) provides r01, merging 3957 into this one (i.e. 4181) following rapporteur's merging proposal
zhendong (ZTE) is fine with this.
Thomas (Nokia) provides r02
LiMeng (Huawei) uploads r02 again since the original version is named incorrectly.
Robbie(Ericsson) provides r03, asks for justification in r02 and questions why to stop the progress on broadcast
==== 8.X, 9.X Revisions Deadline ====
Thomas(Nokia) objects against r03, r01 and r00 and replies to Robbie
TAO(VC) let's check r02 agreeable or not
Robbie (Ericsson) proposes to bring the discussion to CC#4.
Thomas (Nokia) agrees to bring the discussion to CC#4.
There is a late rev4 based on rev3
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105193 P-CR Approval 23.247: Modification clause 7.3 on the Broadcast session management. ZTE Rel-17 Revision of S2-2104181r03 + changes, merging S2-2103957 and S2-2104676. Approved Approved
8.9 S2-2104243 P-CR Approval 23.247: Update on broadcast session establishment. vivo Rel-17 Merged into S2-2105163 LiMeng (Huawei) suggests to merge this document into S2-2103956.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104416 P-CR Approval 23.247: Update on MBS Session Establishment for Broadcast. SAMSUNG Rel-17 Merged into S2-2105163 LiMeng (Huawei) suggests to merge this document into S2-2103956.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104244 P-CR Approval 23.247: Update on broadcast session release. vivo Rel-17 r04 agreed. Revised to S2-2105164, merging S2-2104420 Zhenhua (vivo) provides r01 to merge S2-2104420.
Robbie (Ericsson) provides r02 with 3956 merged.
Youngkyo(Samsung) ask a comment/question.
Robbie (Ericsson) provides r03 and responds Youngkyo(Samsung)
Youngkyo(Samsung) replies to Robbie.
Thomas (Nokia) provides r04
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105164 P-CR Approval 23.247: Update on broadcast session release. vivo Rel-17 Revision of S2-2104244r04, merging S2-2104420. Approved Approved
8.9 S2-2104420 P-CR Approval 23.247: Update on MBS Session release for Broadcast. SAMSUNG Rel-17 Merged into S2-2105164 LiMeng (Huawei) suggests to merge this document into S2-2104244.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104421 P-CR Approval 23.247: Update on MBS Session update for Broadcast. SAMSUNG Rel-17 r02 agreed. Revised to S2-2105165. Robbie (Ericsson) provides r01.
Youngkyo(Samsung) provides r02.
Robbie(Ericsson) comments on r02.
Youngkyo(Samsung) replies to Robbie(Ericsson)
Robbie(Ericsson) replies to Youngkyo(Samsung)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105165 P-CR Approval 23.247: Update on MBS Session update for Broadcast. SAMSUNG Rel-17 Revision of S2-2104421r02. Approved Approved
8.9 S2-2104426 P-CR Approval 23.247: PCF Functionality. Tencent Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Approved
8.9 - - - Service announcement - - Docs:=4 -
8.9 S2-2103952 P-CR Approval 23.247: Update [6.11] Service Announcement. Ericsson Rel-17 r14 agreed. Revised to S2-2105166, merging S2-2104392 and S2-2104428 Chunshan (Tencent) provides r01 .
Youngkyo(Samsung) provides r02.
Judy (Ericsson) has similar doubt as Youngkyo whether SA2 need describe how to get MBS service announcement.
Fenqin (Huawei) add a NOTE related to when the service announcement is provided and provides r03.
Judy (Ericsson) asks question
Fenqin (Huawei) responds
Judy (Ericsson) ask further question
Chunshan (Tencent) provides r04.
Judy (Ericsson) provides r05 and comment
Zhenhua (vivo) provides r06
Judy (Ericsson) comment
Zhenhua (vivo) replies
Thomas (Nokia) provides r07
Zhenhua (vivo) provides r08 basd on r07
Miguel (Qualcomm) asks a question regarding the optional DNN/S-NSSAI provisioning
Fenqin (Huawei) responds and provides r09.
Thomas (Nokia) replies to Miguel
Miguel (Qualcomm) thanks Thomas for the response but still has questions for clarification
Thomas (Nokia) provides r10
Thomas(Nokia) replies to Miguel
Robbie(Ericsson) provides r11 and asks Thomas(Nokia)
Thomas(Nokia) objects against r11 and answers to Robbie
Zhenhua (vivo) mostly agree with Thomas(Nokia) and provides r12 based on r10
Robbie (Ericsson) provides r13.
Fenqin (Huawei) provides comment.
Miguel (Qualcomm) provides r14
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105166 P-CR Approval 23.247: Update [6.11] Service Announcement. Ericsson Rel-17 Revision of S2-2103952r14, merging S2-2104392, merging S2-2104392 and S2-2104428. Approved Approved
8.9 S2-2104392 P-CR Approval 23.247: Clarification of the Service Announcement. Huawei, HiSilicon Rel-17 Merged into S2-2105166 LiMeng (Huawei) suggests to merge this document into S2-2103952.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104428 P-CR Approval 23.247: Service Announce. Tencent Rel-17 Merged into S2-2105166 LiMeng (Huawei) suggests to merge this document into S2-2103952.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 - - - Session Context and Storage information - - Docs:=5 -
8.9 S2-2104180 P-CR Approval 23.247: Update the clause 6.9.1 MBS Session/Service Context. ZTE Rel-17 r11 agreed. Revised to S2-2105167, merging S2-2104280 Xiaoyan (CATT) provides r01.
Youngkyo (Samsung) provides r03.
LiMeng (Huawei) comments.
Zhenhua (vivo) provides r04.
zhendong (ZTE) provides r05.
Thomas (Nokia) provides r06.
zhendong (ZTE) provides r07.
Thomas (Nokia) comments against r07.
zhendong (ZTE) provides the r08.
LiMeng (Huawei) provides r09.
Zhenhua (vivo) provides r10.
Xiaoyan (vivo) provides r11.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105167 P-CR Approval 23.247: Update the clause 6.9.1 MBS Session/Service Context. ZTE Rel-17 Revision of S2-2104180r11, merging S2-2104280. Approved Approved
8.9 S2-2104280 P-CR Approval 23.247: MBS Session and Service Context. CATT Rel-17 Merged into S2-2105167 LiMeng (Huawei) suggests to merge this document into S2-2104180
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.9 S2-2104300 P-CR Approval 23.247: 5MBS Information in UDM. Nokia, Nokia Shanghai-Bell Rel-17 Postponed LiMeng (Huawei) provides r01.
Judy (Ericsson) comments and propose to postpone this paper.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) cannot accept this paper based on previously given comment and propose to postpone
==== 8.X, 9.X Final Deadline ====
Postponed
8.9 S2-2104313 P-CR Approval 23.247: 5MBS Information in UDR. Nokia, Nokia Shanghai-Bell Rel-17 Postponed Xiaoyan (CATT) asks for clarification.
Thomas(Nokia) replies to Xiaoyan and provides r01.
LiMeng (Huawei) provides r01 and informs Thomas that there is no r01 in the server before Huawei submitting the revision.
Judy (Ericsson) asks which procedure support the UDR interaction proposed in this paper.
Thomas (Nokia) apologizes for uploading original r01 and provides r02
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) seeks for answers to the questions previously asked.
Thomas(Nokia) replies to Judy (Ericsson)
XIaoyan (CATT) objects to r02, and requests to remove '(e.g. to the subscriber category part)' in r01.
Judy (Ericsson) propose to postpone this paper to next meeting when we have a more stable PCC solution.
==== 8.X, 9.X Final Deadline ====
Thomas (Nokia) accepts r01.
Postponed
8.9 - - - Inter system mobility/IWK - - Docs:=4 -
8.9 S2-2104198 P-CR Approval 23.247: Adding clause 7.4.2, MBMS interworking when the same service is not provided via eMBMS and 5MBS. ZTE Rel-17 Noted Dario S. Tonesi (Qualcomm) proposes to note this paper.
zhendong (ZTE) proposes to note this CR.
LaeYoung (LGE) comments that MBMS interworking aspect needs to be captured in the exception sheet.
zhendong (ZTE) agree this shall be incldued in the exception sheet.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104393 P-CR Approval 23.247: MBS procedures for inter System Mobility. Huawei, HiSilicon, LG Electronics Rel-17 Noted Dario S. Tonesi (Qualcomm) proposes to note this paper.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) assumes all IWK related papers are NOTED.
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104664 P-CR Approval 23.247: 5MBS interworking with eMBMS. Qualcomm, Ericsson, LG Electronics, AT&T Rel-17 Revision of (Postponed) S2-2102682. Noted LiMeng (Huawei) provides r01.
Fenqin (Huawei) propose to note this paper.
zhendong (ZTE) proposes to note this CR.
Thomas (Nokia) provides comment against r01.
Fenqin (Huawei) provides responds
==== 8.X, 9.X Revisions Deadline ====
LaeYoung (LGE) thinks that there seems no agreeable version to be honest, so can be marked as NOTED. ^__^
==== 8.X, 9.X Final Deadline ====
Noted
8.9 S2-2104665 P-CR Approval 23.247: 5MBS interworking with eMBMS at transport layer. Qualcomm Incorporated, Ericsson Rel-17 Noted Fenqin (Huawei) propose to note this paper
zhendong (ZTE) proposes to note this CR.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.9 - - - NF Services - - Docs:=8 -
8.9 S2-2103908 P-CR Approval 23.247: MB-SM Services . Nokia, Nokia Shanghai-Bell Rel-17 Revision of (Postponed) S2-2102949. r05 agreed. Revised to S2-2105168. Xiaoyan (CATT) provides r01 so that S2-2104282 and S2-2103908 address different MB-SMF services.
Xiaoyan (CATT) provides r02.
Judy (Ericsson) provide r03
Thomas (Nokia) provide r04
Xiaoyan (CATT) provide r05.
==== 8.X, 9.X Revisions Deadline ====
Judy (Ericsson) responds to Xiaoyan
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105168 P-CR Approval 23.247: MB-SM Services . Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2103908r05. Approved Approved
8.9 S2-2104282 P-CR Approval 23.247: MB-SMF services. CATT Rel-17 r04 agreed. Revised to S2-2105169. Xiaoyan (CATT) provides r01 so that S2-2104282 and S2-2103908 address different MB-SMF services.
Thomas (Nokia) provides r02 removing further overlaps.
Judy (Ericsson) provide r03
Xiaoyan (CATT) provides r04.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105169 P-CR Approval 23.247: MB-SMF services. CATT Rel-17 Revision of S2-2104282r04. Approved Approved
8.9 S2-2103911 P-CR Approval 23.247: PCF service for Interactions between MB-SMF and PCF. Nokia, Nokia Shanghai-Bell Rel-17 Revision of (Postponed) S2-2102946. r01 agreed. Revised to S2-2105170. LiMeng (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105170 P-CR Approval 23.247: PCF service for Interactions between MB-SMF and PCF. Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2103911r01. Approved Approved
8.9 S2-2104022 P-CR Approval 23.247: PCF service towards NEF. Nokia, Nokia Shanghai-Bell Rel-17 r01 agreed. Revised to S2-2105171. LiMeng (Huawei) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.9 S2-2105171 P-CR Approval 23.247: PCF service towards NEF. Nokia, Nokia Shanghai-Bell Rel-17 Revision of S2-2104022r01. Approved Approved
8.10 - - - System enablers for multi-USIM devices (MUSIM) - - Docs:=49 -
8.10 - - - General - - Docs:=2 -
8.10 S2-2103794 REPORT Information MUSIM work plan Intel (rapporteur) Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103793 REPORT Information Meeting minutes from MUSIM conference call Intel (rapporteur) Rel-17 Noted Steve (Huawei) should be noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 - - - Functional description - - Docs:=8 -
8.10 S2-2104771 DISCUSSION Endorsement On homogeneous network support of selected MUSIM capabilities. Intel Rel-17 Noted Lalith(Samsung) comments.
Saso (Intel) is OK with Samsung's proposal.
Steve (Huawei) comments
Saso (Intel) proposes to NOTE this document as the proposal was merged on the 3886/3887 threads.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103886 CR Approval 23.401 CR3622R4 (Rel-17, 'B'): Function Description for Multi-USIM devices Ericsson, LG Electronics, Huawei, China Telecom, Charter, MediaTek, Intel, Vodafone, Spreadtrum, Sony, Apple, Samsung, Nokia, Nokia Shanghai Bell, Vivo Rel-17 Revision of (Endorsed) S2-2103057. CC#4: r08 agreed with working agreement set. Revised to S2-2105148. Lalith (Samsung) seeks clarification.
Qian (Ericsson) provides comments and r01.
alessio(Nokia) upgrades to r02 to align with the capability negotiation text
xiaowan (vivo) provides r03
Qian(Ericsson) provides comments on the way forward for the function description papers
Lalith(Samsung) responds to Qian (Ericsson)
Qian(Ericsson) provides r04 with mainly editorial updates on top of r03
Saso (Intel) supports r04 and points to editorials.
Steve (Huawei) provides r05
Jianning (Xiaomi) provides r06, by removing PDN level PR due to our concerns are not solved.
Qian (Ericsson) provides r07 on top of R05 with only further editorial updates
Saso (Rapporteur) replies to Jianning (Xiaomi).
Guillaume (MediaTek) supports the Rapporteur's reply and provide comments.
Saso (Intel) provides r08 to include the NOTE on no PLMN-wide support of Connection Release discussed on the 4771 thread
alessio(nokia) provides r09 introducing MUSIM mode in EPS too
Saso (Intel) provides r10 to fix the clause in the MUSIM Mode definition.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r10.
Qian (Ericsson) proposes to go with R10.
Lars (Sony) is OK with r10.
Jianning (Xiaomi) replies to Saso (Intel), and object any version including PDU/PDN level PR, due to we don't see how this paging restriction can exactly serve the user experience as we repeat many times.
Jianning (Xiaomi) replies to Guillaume (MediaTek)
Saso (Rapporteur) asks for establishment of a Working Agreement in CC#4 using S2-2103886r10 as the basis.
xiaowan (vivo) is OK with r10
Guillaume (MediaTek) supports r10.
Xiaowan(vivo) revoke the last email and can be OK with r10 as long as 'MUSIM mode: A Multi-USIM UE is in MUSIM mode in a PLMN if it operates two or more USIMs and is using one or more of the enhancements described in clause 4.3.x in this PLMN' is applied
Alessio (nokia) would like to proceed with R10 and encourage companies to work on any necessary CR for next meeting
xiaowan (vivo) replies: the removal of definition of'MUSIM mode'can also make me live with r10. Otherwise, I cannot accept any revision with the incorrect definition of 'MUSIM mode'.
Steve (Huawei) MUSIM Mode is the only difference between r08 and r10 a the revision is available. Taking r08 and coming back is ok.
Saso (Intel) agrees with Steve (Huawei). Let's agree r08.
Qian (Ericsson) is also ok with r08.
Lars (Sony) is also ok with r08.
Guillaume (MediaTek) recommends going with r10.
Xiaowan(vivo) replies to Guillaume (MediaTek) and cannot go with r9/r10 as it is
==== 8.X, 9.X Final Deadline ====
Jianning (Xiaomi) provides r11 based on r08 just removing the PDN level PR.
Guillaume (MediaTek) objects to r11.
Revised
8.10 S2-2105148 CR Approval 23.401 CR3622R5 (Rel-17, 'B'): Function Description for Multi-USIM devices Ericsson, LG Electronics, Huawei, China Telecom, Charter, MediaTek, Intel, Vodafone, Spreadtrum, Sony, Apple, Samsung, Nokia, Nokia Shanghai Bell, Vivo Rel-17 Revision of S2-2103886r08r08 with working agreement set. CC#4: Approved and a working agreement was set for S2-2105148 and S2-2105149. Conditionally agreed
8.10 S2-2103887 CR Approval 23.501 CR2553R3 (Rel-17, 'B'): Function Description for Multi-SIM devices Ericsson, LG Electronics, Huawei, China Telecom, Charter, MediaTek, Intel, Vodafone, Spreadtrum, Sony, Samsung Rel-17 Revision of (Endorsed) S2-2103027. CC#4: r08 agreed with working agreement set. Revised to S2-2105149, merging S2-2103983 and S2-2104677. Lalith (Samsung) seeks clarification.
Juan Zhang (Qualcomm) provides comments
Qian (Ericsson) replies to Juan (Qualcomm) and Lalith (Samsung) and provide r01
alessio(Nokia) upgrades to r02 to align with the capability negotiation text
Qian (Ericsson) update the Subject with the correct title of the paper, though the tdoc is correct
xiaowan (vivo) provides r03
Qian (Ericsson) provides r04 with mainly editorial updates on top of r03
Saso (Intel) supports r04 and points to editorials.
Steve (Huawei) comments
Steve (Huawei) I provided r05
Jianning (Xiaomi) provides r06 with removal the PDU level PR due to our concerns are not solved
Qian (Ericsson) provides r07 on top of R05 with only further editorial updates
Saso (Rapporteur) replies to Jianning (Xiaomi).
Guillaume (MediaTek) supports the Rapporteur's reply and provide comments.
Saso (Intel) provides r08 to include the NOTE on no PLMN-wide support of Connection Release discussed on the 4771 thread
alessio(nokia) provides r09 with MUSIM mode and lots more support.
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson) propose to go with r09.
Lars (Sony) supports r09.
Saso (Intel) supports r09.
Xiaowan(vivo) can be OK with r09 as long as 'MUSIM mode: A Multi-USIM UE is in MUSIM mode in a PLMN if it operates two or more USIMs and is using one or more of the enhancements described in clause 4.3.x in this PLMN' is applied
xiaowan (vivo) replies: the removal of definition of'MUSIM mode'can also make me live with r09. Otherwise, I cannot accept any revision with the incorrect definition of 'MUSIM mode'.
Steve (Huawei) MUSIM Mode is the only difference between r08 and r09. So the revision is available. Taking r08 and coming back is ok.
Saso (Intel) is also fine with removal of MUSIM mode definition from r09. Proposes to agree r08.
Qian (Ericsson) is also fine with r08.
Lars (Sony) is also fine with r08.
Jianning (Xiaomi) cannot live r07, r08, r09, ok with r06, and object any versions with PDU/PDN level PR, due to PDU/PDN level PR may bring confusing to user and cannot exactly serve the user experience as other PRs.
Saso (Rapporteur) proposes to make a Working Agreement in CC#4 based on S2-2103887r08.
==== 8.X, 9.X Final Deadline ====
Curt (Charter) is fine with r08.
Antoine (Orange) does not understand the grounds for Xiaomi's objection.
Jianning (Xiaomi) replies to Antoine (Orange)
Jianning (Xiaomi) provides r10 based on r08 just removing the PDU level PR.
Guillaume (MediaTek) objects to r10.
Revised
8.10 S2-2105149 CR Approval 23.501 CR2553R5 (Rel-17, 'B'): Function Description for Multi-SIM devices Ericsson, LG Electronics, Huawei, China Telecom, Charter, MediaTek, Intel, Vodafone, Spreadtrum, Sony, Samsung Rel-17 Revision of S2-2103887r08, merging S2-2103983 and S2-2104677, with working agreement set. CC#4: Approved and a working agreement was set for S2-2105148 and S2-2105149. Conditionally agreed
8.10 S2-2103983 CR Approval 23.501 CR2553R4 (Rel-17, 'B'): Function Description for Multi-SIM devices Vivo (based on Tdoc from Ericsson, LG Electronics, Huawei, China Telecom, Charter, MediaTek, Intel, Vodafone, Spreadtrum, Sony, Samsung) Rel-17 Revision of (Endorsed) S2-2103027. Merged into S2-2105149 Saso (Intel) proposes to NOTE this document or MERGE it in S2-2103887.
Xiaowan(vivo) confirm the CR is merged into S2-2103887.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2104676 CR Approval 23.401 CR3641 (Rel-17, 'B'): IMEI requirement for Multi-USIM UE Orange, Deutsche Telekom Rel-17 Merged into S2-2105193 Saso (Intel) proposes to MERGE this document into S2-2103886.
Lalith (Samsung) supports to MERGE this document into S2-2103886.
Jianning (Xiaomi) provides comment and support to merge
Saso (Intel) comments that NOTEs in the Definitions clause are rarely used. Prefers keeping the text in the Functional description clause, as proposed in S2-2103886.
Antoine (Orange) agrees to merge in S2-2103886.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2104677 CR Approval 23.501 CR2968 (Rel-17, 'B'): PEI requirement for Multi-USIM UE Orange, Deutsche Telekom Rel-17 Merged into S2-2105149 Saso (Intel) proposes to MERGE this document into S2-2103887.
Lalith (Samsung) supports to MERGE this document into S2-2103887
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 - - - Capability exchange - - Docs:=10 -
8.10 S2-2103986 DISCUSSION Agreement Discussion on the complexity for the MUSIM capabilities negotiation. Vivo, Xiaomi, OPPO Rel-17 Noted Saso (Intel) seeks clarifications.
Xiaowan(vivo) replies to Saso (Intel)
Juan Zhang (Qualcomm) provides comments
Xiaowan(vivo) replies to Juan Zhang (Qualcomm)
Saso (Intel) replies to Xiaowan (vivo) that 5GMM capability already includes parameters that can be dynamically changed e.g. S1 mode.
Guillaume (MediaTek) questions the analysis of the paper.
Juan Zhang (Qualcomm) replies to Xiaowan (vivo)
Wanqiang (Huawei) replies and see the value of the paper/discussion.
Guillaume (MediaTek) responds to Wanqiang
Saso (Intel) replies to Wanqiang
Wanqiang (Intel) replies to Saso and Guillaume
Lalith(Samsung) seeks clarification fom Wanqiang
Juan Zhang (Qualcomm) replies to Xiaowan(vivo)
Juan Zhang (Qualcomm) replies to Wanqiang
Jianning (Xiaomi) asks questions for clarification to Saso (Intel) and Lalith(Samsung)
Lalith(Samsung) replies to Jianning (Xiaomi)
Jianning (Xiaomi) provides further comment
Jianning (Xiaomi) replies to Lalith(Samsung)
Juan Zhang (Qualcomm) replies to Jianning (Xiaomi)
Jianning (Xiaomi) replies to Juan (Qualcomm)
Xiaowan comments the questions in the slides for the CC#2
Saso (Rapporteur) replies to Xiaowan.
Jianning (Xiaomi) asks question for clarification from Saso (Intel)
Juan Zhang (Qualcomm) askes Jianning (Xiaomi) for clarification
Guillaume (MediaTek) supports the version from Saso (Rapporteur).
Saso (Intel) comments.
Wanqiang(Huawei) agree with Xiaowan and propose to make the question clear for SoH.
Saso (Intel) asks Wanqiang (Huawei) to clarify what exactly is unclear.
Guillaume (MediaTek): the questions are clear: proceed with a set of CRs or another set of CRs. The CRs are known.
Xiaowan(vivo) replies to Saso (Rapporteur).
Saso (Intel) replies to Xiaowan(vivo).
Jianning (Xiaomi) seeks further clarification
Guillaume (MediaTek) comments.
Saso (Intel) agrees with Guillaume and replies to Jianning (Xiaomi) and seeks clarification from Xiaowan.
Jianning (Xiaomi) replies to Saso (Intel) and Guillaume (MediaTek)
Saso (Intel) thinks that now we can NOTE this document.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104601 DISCUSSION Endorsement MUSIM: Handling of MUSIM capabilities. MediaTek Inc., Intel, LG Electronics, Qualcomm Incorporated, Samsung Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103987 CR Approval 23.401 CR3630R2 (Rel-17, 'B'): Introduction of MUSIM capability exchange Vivo, Xiaomi, OPPO (based on Tdoc from Qualcomm Incorporated, Samsung, Oppo, Intel, Apple, Huawei, Charter, Lenovo, Motorola Mobility,vivo) Rel-17 Revision of (Postponed) S2-2102342. Noted Saso (Intel) proposes to NOTE this document and progress S2-2104486, based on the SoH on CC#2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104486 CR Approval 23.401 CR3630R3 (Rel-17, 'B'): Introduction of MUSIM capability exchange Qualcomm Incorporated, Samsung, Intel, Lenovo, Motorola Mobility, MediaTek Inc., LG Electronics; Nokia, Nokia Shanghai Bell, Apple, Spreadtrum Rel-17 Revision of (Postponed) S2-2102342. r09 agreed. Revised to S2-2105116. Xiaowan(vivo) provides comments and r01
Juan Zhang (Qualcomm) provides r02.
Xiaowan (vivo) comments r02.
Juan Zhang (Qualcomm) replies to vivo.
Xiaowan(vivo) replies to Juan Zhang (Qualcomm) and provides r03
Juan Zhang (Qualcomm) replies to Xiaowan (vivo) and provides r04.
Juan Zhang (Qualcomm) provides r05.
Guillaume (MediaTek) agrees with Juan (Qualcomm) and supports r04.
Juan Zhang (Qualcomm) provides r06.
Alessio(Nokia) provides r06.
xiaowan (vivo) provides r07
Juan Zhang (Qualcomm) supports r06
Xiaowan(vivo) replies to Juan Zhang (Qualcomm) and provide r08
Juan Zhang (Qualcomm) provides r09.
Chris (Vodafone) one typo for clean up: PLMH->PLMN
==== 8.X, 9.X Revisions Deadline ====
Myungjune (LGE) is ok with r09 but it requires editorial work.
Juan Zhang (Qualcomm) proposes to approve r09 with a further typo update: 'PLMH->PLMN' in clause 5.11.3.
xiaowan (vivo) is OK with r09
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105116 CR Approval 23.401 CR3630R4 (Rel-17, 'B'): Introduction of MUSIM capability exchange Qualcomm Incorporated, Samsung, Intel, Lenovo, Motorola Mobility, MediaTek Inc., LG Electronics; Nokia, Nokia Shanghai Bell, Apple, Spreadtrum Rel-17 Revision of S2-2104486r09. Approved Agreed
8.10 S2-2104463 CR Approval 23.501 CR2927 (Rel-17, 'B'): Introduction of MUSIM capability exchage Qualcomm Incorporated, LG Electronics, Nokis, Nokia Shanghai Bell, Intel, Samsung, Apple, Spreadtrum Rel-17 r12 agreed. Revised to S2-2105117. Xiaowan(vivo) provides comments and r01
Juan Zhang (Qualcomm) provides r02.
Guillaume (MediaTek) provides r03.
Xiaowan comments r02 and r03.
Juan Zhang (Qualcomm) replies to xiaowan
Wanqiang (Huawei) replies and ask question for clarification.
Saso (Intel) replies to Wanqiang (Huawei).
Wanqiang (Huawei) replies to Saso(Intel) and proposes to update the paper with making it clear like r04.
Guillaume (MediaTek) agrees with Saso.
Juan Zhang (Qualcomm) agrees with Guillaume (MediaTek) and Saso.
Curt (Charter) also agrees with Saso.
alessio(Nokia) provides r05 which implements exactly what Juan says.
Juan Zhang (Qualcomm) is fine with r05.
xiaowan (vivo) provides r06
Jianning (Xiaomi) provides comment and r07
Guillaume (MediaTek) provides r08.
Yang (OPPO) concerns r08 will have mis-understanding and propose to use r06 as baseline. Provides r09.
Juan Zhang (Qualcomm) supports r05 and object r06 to r09.
Xiaowan(vivo) replies to Juan Zhang (Qualcomm); object to r05 and r08; provide r10
Guillaume (MediaTek) objects to r6, r7, r9, r10. Provides r11 on top of r8.
Juan Zhang (Qualcomm) thinks r11 is a good shape.
Yang (OPPO) comments as long as the UE without MUSIM capability does not send the MUSIM features, we will be fine with the revision.
Xiaowan(vivo) replies to Guillaume (MediaTek) and provides r12
Guillaume (MediaTek) replies to Xiaowan (vivo)
Jianning (Xiaomi) asks a quick question for clarification.
Guillaume (MediaTek) replies to Jianning (Xiaomi)
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r12.
Saso (Intel) supports approval of r12.
Guillaume (MediaTek) ok with both r11/r12.
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105117 CR Approval 23.501 CR2927R1 (Rel-17, 'B'): Introduction of MUSIM capability exchage Qualcomm Incorporated, LG Electronics, Nokis, Nokia Shanghai Bell, Intel, Samsung, Apple, Spreadtrum Rel-17 Revision of S2-2104463r12. Approved Agreed
8.10 S2-2103988 CR Approval 23.502 CR2568R2 (Rel-17, 'B'): Introduction of MUSIM capability exchange Vivo, Xiaomi, OPPO (based on Tdoc from Qualcomm Incorporated, Samsung, Huawei, Oppo, Intel, Apple, Charter, Lenovo, Motorola Mobility) Rel-17 Revision of (Postponed) S2-2102346. Noted Saso (Intel) proposes to NOTE this document and progress S2-2104480, based on the SoH on CC#2.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104480 CR Approval 23.502 CR2568R4 (Rel-17, 'B'): Introduction of MUSIM capability exchage Qualcomm Incorporated, Samsung, Intel, Apple, Lenovo, Motorola Mobility, MediaTek Inc., LG Electronics, Nokia, Nokia Shanghai Bell, Spreadtrum Rel-17 Revision of (Postponed) S2-2102346. r03 agreed. Revised to S2-2105118. Xiaowan(vivo) provides comments and r01
Juan Zhang (Qualcomm) provides r02.
Guillaume (MediaTek) provides r03.
xiaowan (vivo) comments r02 and r03
Juan Zhang (Qualcomm) replies to Xiaowan
Saso (Intel) replies to Xiaowan
Jianning (Xiaomi) provide comment
Guillaume (MediaTek) disagrees with the claim from Jianning (Xiaomi).
Saso (Rapporteur) announces that this topic has been included in the MUSIM questions for CC#2.
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) proposes to approve r03.
Saso (Intel) supports r03.
Guillaume (MediaTek) supports r03.
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105118 CR Approval 23.502 CR2568R5 (Rel-17, 'B'): Introduction of MUSIM capability exchage Qualcomm Incorporated, Samsung, Intel, Apple, Lenovo, Motorola Mobility, MediaTek Inc., LG Electronics, Nokia, Nokia Shanghai Bell, Spreadtrum Rel-17 Revision of S2-2104480r03. Approved Agreed
8.10 - - - KI#1 – Paging Cause - - Docs:=7 -
8.10 S2-2104375 DISCUSSION Agreement Voice service indication in NOTIFICATION message. Samsung, InterDigital, LG Electronics Rel-17 Noted Saso (Intel) proposes to endorse Proposal 2.
Jianning (Xiaomi) asks question for clarification
Lalith(Samsung) clarifies and comments.
Juan Zhang (Qualcomm) provides comments.
Ouyang(Huawei) comments
Lalith(Samsung) responds to Ouyang(Huawei)
Curt (Charter) prefers option 1 and noticed that the previous objections were not based on technical ground. Are there any companies objecting to go with option 1??
Krisztian (Apple) prefers Proposal-1. I also don't recall any technical reasons why Proposal-1 does not work.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103984 CR Approval 23.401 CR3634R2 (Rel-17, 'B'): Introduction of Paging Cause feature Vivo, Intel, LGE, Qualcomm, Xiaomi, Samsung, Huawei, Charter, MediaTek, OPPO, Apple, Nokia, Lenovo, China Telecom, NEC, Spreadtrum Rel-17 Revision of (Agreed) S2-2103028. r03 agreed. Revised to S2-2105119, merging S2-2104712 Saso (Intel) proposes to NOTE this document or MERGE it in S2-2104712.
xiaowan (vivo) replies to Saso(Intel) and provides r01
Saso (Intel) provides r02.
Steve (Huawei) provides r03
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r03.
xiaowan (vivo) is OK with r03
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105119 CR Approval 23.401 CR3634R4 (Rel-17, 'B'): Introduction of Paging Cause feature Vivo, Intel, LGE, Qualcomm, Xiaomi, Samsung, Huawei, Charter, MediaTek, OPPO, Apple, Nokia, Lenovo, China Telecom, NEC, Spreadtrum Rel-17 Revision of S2-2103984r03, merging S2-2104712. Approved Agreed
8.10 S2-2104712 CR Approval 23.401 CR3634R3 (Rel-17, 'B'): Introduction of Paging Cause feature Intel, [vivo], [LGE], [Qualcomm], [Xiaomi], [Samsung], [Huawei], [Charter], [MediaTek], [OPPO], [Apple], [Nokia], [Lenovo], [China Telecom], [NEC], [Spreadtrum] Rel-17 Revision of (Agreed) S2-2103028. Merged into S2-2105119 xiaowan (vivo) proposes to merge S2-2104712 into S2-2103984r01
Saso (Intel) confirms that S2-2104712 is MERGED into S2-2103984
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 S2-2103985 CR Approval 23.502 CR2502R3 (Rel-17, 'B'): Introduction of Paging Cause feature Vivo, Intel, LGE, Qualcomm, Xiaomi, Samsung, Huawei, Charter, MediaTek, OPPO, Apple, Nokia, Lenovo, China Telecom, NEC, Spreadtrum Rel-17 Revision of (Postponed) S2-2102317. r07 agreed. Revised to S2-2105120, merging S2-2104713 Lalith(Samsung) provides r01
Lalith(Samsung) provides r02
xiaowan (vivo) provides r03
Saso (Intel) proposes to NOTE this document or MERGE it in S2-2104713.
xiaowan (vivo) provides r04
Saso (Intel) provides r05.
Steve (Huawei) provides r06
xiaowan (vivo) provides r07 with typo fixed
==== 8.X, 9.X Revisions Deadline ====
Steve (Huawei) is ok with r07
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105120 CR Approval 23.502 CR2502R5 (Rel-17, 'B'): Introduction of Paging Cause feature Vivo, Intel, LGE, Qualcomm, Xiaomi, Samsung, Huawei, Charter, MediaTek, OPPO, Apple, Nokia, Lenovo, China Telecom, NEC, Spreadtrum Rel-17 Revision of S2-2103985r07, merging S2-2104713. Approved Agreed
8.10 S2-2104713 CR Approval 23.502 CR2502R4 (Rel-17, 'B'): Introduction of Paging Cause feature Intel, [vivo], [LGE], [Qualcomm], [Xiaomi], [Samsung], [Huawei], [Charter], [MediaTek], [OPPO], [Apple], [Nokia], [Lenovo], [China Telecom], [NEC], [Spreadtrum] Rel-17 Revision of (Postponed) S2-2102317. Merged into S2-2105120 Lalith(Samsung) provides r01
Saso (Intel) provides r02.
Juan Zhang (Qualcomm) provides r03
Lalith(Samsung) provides r04
xiaowan (vivo) proposes to note or merge S2-2104713 into S2-2103985
Saso (Intel) confirms that S2-2104713 is merged into S2-2103985
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.10 - - - KI#1 – Reject Paging (Busy) indication - - Docs:=8 -
8.10 S2-2103768 LS In Action LS from RAN WG2: LS on NAS-based busy indication RAN WG2 (R2-2104354) Rel-17 Responses drafted in S2-2103792, S2-2103982 and S2-2104153. Final response in S2-2105150 Replied to
8.10 S2-2103792 LS OUT Approval [DRAFT] Reply LS on NAS-based busy indication Intel Rel-17 Response to S2-2103768. CC#4: r36 agreed. Revised to S2-2105150. alessio (nokia) proposes to note this draft reply and focus on S2-2104153
Saso (Intel) disagrees with Alessio's proposal.
Saso (Intel) provides r01 based on the discussion on CC#3.
Lars (Sony) provides r02.
Curt (Charter) asks OEM vendors a question.
Juan Zhang (Qualcomm) replies to Curt (Charter)
Lars (Sony) provides r03
xiaowan (vivo) provides comments and r04
Lars (Sony) asks xiaowan (vivo) for clarification
Saso (Intel) provides r05
Lars (Sony) provides r06
alessio(Nokia) provides a simpler r07 (with remarks removed for legibility)
Xiaowan(vivo) replies to Saso (Intel) and Lars (Sony)
Lars (Sony) comments
Antoine (Orange): Shouldn't bullet A2 be updated accordingly?
Lars (Sony) provides r08 based r07.
Lars (Sony) provides r09 based r06.
Ouyang(Huawei) provides r10. Ouyang(Huawei) can't accept the original version and r0-r09 of this LS.
Lars (Sony) provides r11.
Steve (Huawei) provides r12
Lars (Sony) can agree on most changes in r12, but disagree that this is a scenario. It is further impact as per RAN2 Q2. Provides r13
Saso (Intel) provides r14 on top of r11.
Steve (Huawei) provides r15
Lars (Sony) provides r16
Saso (Intel) provides r17 on top of r09.
Guillaume (MediaTek) provide r18. Way too many revisions in 2min...
==== 8.X, 9.X Revisions Deadline ====
Saso (Intel) proposes to agree r16, r17 or r18.
Ouyang(Huawei) replies to Saso(Intel) about removing the second part of the LS
Krisztian (Apple) prefers the wording in r18.
Ouyang(Huawei) creates r19 in draft folder on top r15.
Can't accept r16, r17 and r18
Guillaume (MediaTek) objects to r19.
Ouyang(Huawei) comments.
Lars(Sony) responds to Ouyang
Jianning (Xiaomi) has concerns on the part of 'network switching'.
Ouyang(Huawei) replies to Lars(Sony)
Saso (Intel) replies to Ouyang(Huawei) and Jianning regarding the second part of the LS
Saso (Intel) provides r21 in the DRAFTS folder based on r18.
alessio(Nokia) supports r18... let's just send the Ls based on that, it is the most balanced probably.
Lars (Sony) comments on r21.
Lars (Sony) I can live with r18.
Lars (Sony) is ok with r22.
alessio(Nokia) can live with r22 but of course fallback to r18 if others have issue..
Ouyang(Huawei) objects r18 and r22. Provides r23 on top of r21
Lars (Sony) comments on r23 and objects to r23
Saso (Intel) is overall ok with r23. Proposes minor wording adjustments in r24.
Lars (Sony) provides r25.
Ouyang(Huawei) can't accept r25. Provide r26 and try to avoid postponing this LS to next meeting
Saso (Intel) notes that both r25 and r26 are very similar. Both are acceptable to Intel.
Lars (Sony) provides r27 and try to avoid postponing this LS to next meeting.
Xiaowan(vivo) is also ok to take r23/r24 as basis
Ouyang(Huawei) comments on the 'accounting issue' in r27 all of the sudden.
Ouyang(Huawei) responds to Ouyang.
Guillaume (MediaTek) cannot accept r26/r27 and provides r28.
Lars (Sony thanks Guillaume (MediaTek) for r28 and can accept r28.
Ouyang(Huawei) can't accept r28.
Saso (Intel) is also fine with r28.
Lars (Sony) disagree with comment on accounting issue
Saso (Intel) replies to Ouyang (Huawei).
Guillaume (MediaTek) proposes to discuss r28 in CC#4..
Lars(Sony) responds to Ouyang.
Ouyang(Huawei) is OK to discuss this LS in CC#4. Huawei considers the r26 is the right one to be selected as basis.
Lars (Sony) can also accept r29
Saso (Intel) replies to Ouyang(Huawei); also seeks opinion from Lars; provides r30
Lars (Sony) Agrees with Guillaume.
Lars (Sony) replies to Saso on r30
==== 8.X, 9.X Final Deadline ====
alessio (nokia) can accept r28.
Ouyang(Huawei) disagree the accounting is an issue, without even a proper paper to explain what the issue is.
Ouyang(Huawei) objects r30. Provides r31.
Guillaume (MediaTek) responds to Ouyang (Huawei): no proper paper exists explaining the concerns do not exist. We object to r31
Lars (Sony) We object to r31, provides r32
Guillaume (MediaTek) ok with r32 (provides r33 just in case).
Ouyang(Huawei) objects r32 andr r33.
Ouyang(Huawei) responds to Guillaume (MediaTek): what is the accounting issue?
Saso (Intel) provides r34
Xiaowan(vivo) suggests Ouyang to reconsider R33 with the removal of 'The received packets will create accounting issues.'
Xiaowan(vivo) replies Guillaume (MediaTek) that R33 seems acceptable if 'The received packets will create accounting issues.' is removed.
Lars (Sony) the proposal from Xiaowan is not a way forward, and we can't accept r34 from Saso.
Jianning (Xiaomi) has concens on the statements in r34 which are not in SA2 scope and are based on assupmption. Provide r35
Saso (Intel) provides r36
Lars (Sony) does not accept r36
Xiaowan(vivo) replies to Lars (Sony)
Ouyang(Huawei) consider this LS should not be sent if 'accounting issue' is written in any form.
Saso (Intel) comments. Proposes to agree r36.
Lars (Sony) responds to Ouyang(Huawei).
Jianning (Xiaomi) provides comment
Jianning (Xiaomi) provides comments on r36
Lars (Sony) to make progress we can live with r36.
Saso (Intel) thanks the participants for the discussion and willingness to compromise. Uploads r36 in the CC#4 folder.
Revised
8.10 S2-2105150 LS OUT Approval Reply LS on NAS-based busy indication SA WG2 Rel-17 Revision of S2-2103792r36. CC#4: Approved Approved
8.10 S2-2104153 LS OUT Approval Reply LS on NAS-based busy indication Sony Rel-17 Response to S2-2103768. Noted Steve (Huawei) proposes to note LS out and concentrate on 3792.
Lars (Sony) as the LS out is drafted in 3792, I can confirm it is ok to NOTE this LS out version.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104152 DISCUSSION Endorsement NAS based Busy Indication from RRC_Inactive state Sony, LG Electronics, Samsung Rel-17 Noted Saso (Intel) comments. Proposes to NOTE the document and use S2-2103790 as the basis for further updates.
Lars (Sony) responds to Saso and think it is too early to NOTE the document.
Myungjune (LGE) supports Lars (Sony) and replies to Saso (Intel).
Xiaowan(vivo) comments
Lalith(Samsung) comments
Lars (Sony) asks a question on the received data handling
Saso (Intel) replies to Lalith and Lars.
Ouyang(Huawei) replies to Lars(Sony), and consider the NAS based solution is sufficient.
xiaowan (vivo) provides comments
Krisztian (Apple) comments
alessio(Nokia) Nokia agrees with the issues identified by Sony
Steve (Huawei) comments
alessio(nokia) responds
Saso (Rapporteur) announces that this topic has been included in the MUSIM questions for CC#2.
Lars (Sony) Question #3 (reject paging) discuss two options, but only one option is asked to proceed with Y/N. This is not acceptable.
Saso (Rapporteur) replies to Lars (Sony.
Lars (Sony) responds to Saso.
Alessio (Nokia) proposes a different text for questions
Qian (Ericsson) provides comments
Myungjune (LGE) replies to Qian
Lars (Sony) the impact is on NG-AP.
Saso (Intel) replies to Myungjune (LGE) and Qian
Myungjune (LGE) replies to Saso (Intel)
Saso (Intel) proposes to NOTE this document.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103790 CR Approval 23.502 CR2558R3 (Rel-17, 'B'): Introduction of Reject Paging Indication response to paging using SR Intel, Qualcomm, MediaTek, Apple, Lenovo, Motorola Mobility, [Sony], [vivo], [Xiaomi], [Samsung], [China Telecom], [Oppo], [Convida Wireless], [LG Electronics] Rel-17 Revision of (Endorsed) S2-2103030. CC#4: r15 agreed. CC#5: r15 + changes agreed. Revised to S2-2105151. Saso (Intel) provides r01 based on the discussion on CC#3.
Saso (Intel) provides r02.
Myungjune (LGE) clarifies that r02 was provided by Lars (Sony) and provides r03.
Lalith (Samsung) provides r04
Lars (Sony) provides r05
Lars (Sony) provides r06
Juan Zhang (Qualcomm) provides r07
Lars (Sony) provides r08
Saso (Intel) comments and replies to Lars (Sony)
Lalith(Samsung) provides r09
Lars (Sony) comments on r09
Saso (Intel) provides r10
Lars (Sony) comments on r10
Lalith(Samsung) replies to Lars (Sony)
Alessio (Nokia) provides r11 with several changes
Guillaume (MediaTek) provides r12.
Saso (Intel) provides r13.
Lalith(Samsung) provides r14.
Guillaume (MediaTek) agrees with Saso
Steve (Huawei) comments
Lars (Sony) agrees with Steve (Huawei) on the rephrasing
Saso (Intel) replies to Steve and Alessio
Guillaume (MediaTek) replies to Steve (Huawei) and Saso (Intel). Provides r14
Guillaume (MediaTek) replies to Alessio (Nokia) re: MUSIM mode
Lars (Sony) prefers the last one of the wording proposals and provides r15
alessio(Nokia) indeed this would be goo for a 23.501 definitions clause and similar text for 23.401.
Guillaume (MediaTek) thanks Lars (Sony) for r15
==== 8.X, 9.X Revisions Deadline ====
Juan Zhang (Qualcomm) is OK with r15.
Lars (Sony) WF of CC#3 was to add an EN and send an LS to RAN2. If the LS in 3792 is not sent, then we object to all versions of this CR.
Lalith (Samsung) Object -> r11, r12, r13. OK with other revision. Prefers r15
WF of CC#3 was to add an EN and send an LS to RAN2. If the LS in 3792 is not sent, then we object to all versions of this CR.
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105151 CR Approval 23.502 CR2558R5 (Rel-17, 'B'): Introduction of Reject Paging Indication response to paging using SR Intel, Qualcomm, MediaTek, Apple, Lenovo, Motorola Mobility, [Sony], [vivo], [Xiaomi], [Samsung], [China Telecom], [Oppo], [Convida Wireless], [LG Electronics] Rel-17 Revision of S2-2103790r15 + changes. CC#5: Approved Agreed
8.10 S2-2104154 CR Approval 23.502 CR2558R4 (Rel-17, 'B'): Introduction of Reject Paging Indication response to paging using SR Sony, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Endorsed) S2-2103030. Noted Steve (Huawei) this CR should be noted as the discussion is in 3790.
Lars (Sony) agrees to NOTE this tdoc as a result of the Way forward in CC#3.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 - - - KI#2 – pCRs - - Docs:=1 -
8.10 S2-2104156 P-CR Approval 23.761: KI #2, Conclusion enabling paging reception in 5GS. Sony, Nokia, Convida Wireless, NEC, Samsung, Interdigital Rel-17 Revision of (Noted at S2#143E) S2-2100863. Postponed xiaowan (vivo) propose to postpone this paper
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 - - - KI#2 - - Docs:=2 -
8.10 S2-2104159 CR Approval 23.502 CR2631R1 (Rel-17, 'B'): Introduction of enabling paging reception Sony, Nokia, Nokia Shanghai Bell, NEC, Convida Wireless, Interdigital, [Intel] Rel-17 Revision of (Noted) S2-2102305. Postponed Saso (Intel) points out that there thus far was no RAN2 feedback on the usefulness of the GUTI assignment assistance information. Proposes to NOTE the document and use S2-2104686 as the basis for further updates.
Lars (Sony) We are not against having an EN (as in 4686 but may need some tweaking) let's see what other co-signing companies think.
Ouyang(Huawei) objects to this CR
Lars (Sony) ask a question
Ouyang(Huawei) replies to Lars(Sony)
Lars (Sony) replies to Ouyang(Huawei)
Jianning (Xiaomi) provides clarification and comment to Lars (Sony)
Lars (Sony) responds to Jianning
Jianning (Xiaomi) provides comment
Guillaume (MediaTek) agrees with Jianning (Xiaomi): MRU is sufficient (w/o assistance info)
Lars (Sony) responds to Guillaume
Guillaume (MediaTek) replies to Lars (Sony).
xiaowan (vivo) proposes to postpone this paper
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.10 S2-2104686 CR Approval 23.502 CR2631R2 (Rel-17, 'B'): Introduction of enabling paging reception Intel Rel-17 Revision of (Noted) S2-2102305. Postponed xiaowan (vivo) requests to postpone this paper
Saso (Intel) disagrees with xiaowan's (vivo) requests to postpone this paper
Lars (Sony) provides r01
Xiaowan(vivo) object to the CR (inc. revisions)
Saso (Intel) proposes to keep this document (all revisions) open for discussion given that the related RAN2 discussion summary will be published by Wed 12:00 UTC i.e. before the SA2 final comments deadline (Wed 16:00 UTC).
Steve (Huawei) this CR just commits us to another CR in the future, let's not do that. See no value in it.
Saso (Intel) provides r02. Replies to Steve.
==== 8.X, 9.X Revisions Deadline ====
Myungjune (LGE) points out that Tdoc number in coversheet is wrong.
Lars (Sony) We propose to postpone the CR.
Alessio(Nokia) is also ok to postpone. let's see what RAN has done and align at next meeting.
Xiaowan(vivo) disagrees r02 and is also ok to postpone.
Saso (Intel) points to the RAN2 MUSIM Rapporteur's conclusion that was published earlier today on the RAN2 reflector. Proposes to agree r02 because it is in line with the RAN2 MUSIM Rapporteur's conclusion.
Steve (Huawei) also suggests postponing
Guillaume (MediaTek) - the proposal from SA2 Rapporteur aka Saso is reasonable.
==== 8.X, 9.X Final Deadline ====
alessio(Nokia) received comments the meeting in rAN2 is not over...
Lars (Sony) we have been waiting for RAN2, so I guess we should continue to wait. This feature becomes an exception for Q3.
Saso (Intel) thinks there is no need for an exception for Q3.
Saso (Intel) uploads a draft Exception sheet for MUSIM in the DRAFTS folder focusing on the enabling of paging reception for 5GS.
Postponed
8.10 - - - KI#3 – pCRs - - Docs:=4 -
8.10 S2-2103885 P-CR Approval 23.761: KI#3, updates to conclusions for KI#3. Ericsson, Charter, Sony, Lenovo, Motorola Mobility, Intel Rel-17 r11 agreed. Revised to S2-2105121. Xiaowan(vivo) provides comments and r01
Lars (Sony) provides comments
Ouyang(Huawei) provide r02.
Lars (Sony) provides r03
Saso (Intel) comments
Lalith(Samsung) comments on r03
Lars (Sony) responds to Lalith and provides r04.
Lars (Sony) provides r05.
Qian (Ericsson) provides r05 (Not Lars (Sony)).
Steve (Huawei) comments that r04 onwards is not looking acceptable.
Juan Zhang (Qualcomm) provides r06.
Lars (Sony) support the direction of r06.
Saso (Intel) support the direction of r06 and provides an editorial in r07.
Alessio(nokia) provides r08.
Steve (Huawei) provides r09
alessio(nokia) cannot accept r09
Saso (Intel) supports r09
Curt (Charter) agrees with Intel to send this TR for approval with r09.
Jianning (Xiaomi) supports Saso (Intel) to go with r09, focusing the details in the related normative CRs.
alessio(Nokia) cannot accept r09 and is also ok to note this P-CR if the focus has to be the CRs and the TR is not important anymore.
Saso (Intel) replies to Alessio
Saso (Intel) provides r10
Alessio(Nokia) can only go with r08 for uniformity with the approach used for the other ENs.
Steve (Huawei) I can't agree with r04, r05, r06, r07, r08.
Juan Zhang (Qualcomm) is also fine with r02 or r03.
Qian (Ericsson) provides r11 based on r08/r09/r10.
alessio(Nokia) proposes we note this paper as we are so advanced on normative phase this retrospective work on tR makes little sense.
alessio(Nokia) can live with R11.
Saso (Rapporteur) supports approving r11.
==== 8.X, 9.X Revisions Deadline ====
Lars (Sony) are ok with r11.
Curt (Charter) supports r11.
Steve (Huawei) can live with r11, as the note documents something that has already happened.
==== 8.X, 9.X Final Deadline ====
Revised
8.10 S2-2105121 P-CR Approval 23.761: KI#3, updates to conclusions for KI#3. Ericsson, Charter, Sony, Lenovo, Motorola Mobility, Intel Rel-17 Revision of S2-2103885r11. Approved Approved
8.10 S2-2103990 P-CR Approval 23.761: KI#3: Conclusions update. Vivo, Charter, OPPO, Xiaomi Rel-17 Noted Saso (Intel) proposes to MERGE this document into S2-2103885.
Xiaowan (vivo) replies to Saso(Intel).
Saso (Intel) proposes to NOTE this document.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Xiaowan(vivo) see '?' for the CR in the status of the Chairman note and confirm partial of the proposal is merged into S1-2103885.
Noted
8.10 S2-2104682 DISCUSSION Agreement Discussion for paging restriction on PDU/PDN level . Xiaomi Rel-17 Noted Saso (Intel) notes that this is a pCR (rather than DP) and proposes to NOTE it.
Jianning (Xiaomi) replies to Saso (Intel), this DP brings new additional and important observation for further discussion, we think it is a good way to have further discuss on it first rather than NOTEing it at the very beginning.
Saso (Intel) replies to Xiaomi.
Curt (Charter) supports Saso (intel) to note this pCR.
Jianning (Xiaomi) replies to Curt (Charter) and Saso (Intel), seeks for further clarification before NOTE
Qian (Ericsson) supports Intel and Charter and provides comments
Jianning (Xiaomi) replies to Qian (Ericssion)
Saso (Intel) replies to Jianning (Xiaomi)
Juan Zhang (Qualcomm) supports comments by Saso and proposes to note the paper.
Jianning (Xiaomi) replies to Saso (Intel) and Juan (Qualcomm)
Qian (Ericsson) provides further comments
Jianning (Xiaomi) replies to Saso (Intel) and Qian (Ericsson)
Alessio(Nokia) proposes to note the paper.
Guillaume (MediaTek) supports noting the paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 - - - KI#3 - - Docs:=6 -
8.10 S2-2103989 DISCUSSION Agreement Discussion on how to perform paging restriction for a UE in RRC_Inactive. Vivo, Charter, Samsung, OPPO, Xiaomi Rel-17 Noted Saso (Intel) comments and proposes to NOTE this document.
Qian (Ericsson) provides comments.
Saso (Intel) replies to Qian (Ericsson).
Myungjune (LGE) comments.
Lars (Sony) agree that PR handling in the UPF when UE is in CM-Connected state is not good.
Juan Zhang (Qualcomm) objects any proposal that CN buffers/filters paging for UE in RRC_Inactive mode.
Curt (Charter) comments that no one size fits all and this is a good trade-off.
Juan Zhang (Qualcomm) replies to Curt (charter)
Lars (Sony) replies to Curt (charter)
Ouyang(Huawei) objects that the PR is sent to either UPF or RAN
Lalith(Samsung) shares the view of Curt (Charter) and Qian(Ericsson)
xiaowan (vivo) provides comments
Curt (Charter) comments...
Krisztian (Apple) agrees with the concerns that DL buffering/paging filtering in CN for a UE in RRC Inactive is not a good design.
Saso (Intel) proposes to NOTE the document based on the discussion on CC#3.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104067 DISCUSSION Discussion Discussion on leaving and charging issue. LG Electronics Rel-17 Noted Gerald (Matrixx) supports proposal 1&2a.
Saso (Intel) proposes to NOTE this document.
==== 8.X, 9.X Revisions Deadline ====
Gerald (Matrixx) share the view with a question.
Myungjune (LGE) is ok to NOTE this paper.
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2104276 DISCUSSION Agreement 5GS Leaving procedure for 5GC/NR and Busy indication from RRC_Inactive Intel Rel-17 Noted Saso (Intel) proposes to NOTE this document as the proposals in it have been progressed in the normative CRs in 3790/3791.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.10 S2-2103791 CR Approval 23.502 CR2724R2 (Rel-17, 'B'): Introduction of Leaving procedure - 5GS Intel, Lenovo, Motorola Mobility, MediaTek, Apple, Ericsson, [Samsung], [LG Electronics], [Qualcomm], [Xiaomi], [China Telcom], [Charter], [Oppo], [Vodafone], [Spreadtrum], [Matrixx] Rel-17 Revision of (Endorsed) S2-2103033. CC#4: r05 + changes agreed. Revised to S2-2105152, merging S2-2104065. Curt (Charter) provides r01.
Myungjune (LGE) provides r02.
Qian (Ericsson) provides comments.
Saso (Intel) prefers not to go in the direction of r02; open about the direction of r01.
Steve (Huawei) provides r03, comments on direction
Saso (Intel) provides r04.
Curt (Charter) provides r05.
Juan Zhang (Qualcomm) requests for clarification
Myungjune (LGE) replies to Juan Zhang (Qualcomm)
Juan Zhang (Qualcomm) replies to Myungjune.
Juan Zhang (Qualcomm) provides r06.
Myungjune(LGE) replies to Juan Zhang (Qualcomm)
==== 8.X, 9.X Revisions Deadline ====
Myungjune(LGE) prefers r02/03, can live with r01/r05, objects r00/r04/r06.
Gerald (Matrixx) supports the approval of r03.
Qian (Ericsson) proposes to go with r05.
Pinghui (China Telecom) share the same view with Qian, and comment.
Saso (Intel) proposes to agree r05. Replies to Pinghui (China Telecom).
Juan Zhang (Qualcomm) can compromise to r05 with a NOTE.
Curt (Charter) can live with r05 but prefers r02/03.
Alessio(Nokia) can only accept r06 and no description of accounting issues as this is not the sole accounting issues we may have (and the most important one is the NAS paging reject in RRC-Inactive which has 100% likelihood to happen all the time)
Curt (Charter) objects R06.
Alessio(Nokia) objects to r05.
Saso (Intel) proposes a modified NOTE in r05.
Qian (Ericsson) supports Saso (Intel) and consider it's important to have base agreed in this meeting.
Myungjune (LGE) proposes another update for NOTE.
Alessio is ok with r03 indeed... why did we need more than r03?
Alessio( nokia) does not see the purpose of the note... there are many other issues where data cannot be delivered or is lost in the system... and this is one of the least likely in general.
Steve (Huawei) Objects to r00, r01, r02. R03 is not useful. Prefers r06/r04. Can live with r05. Updating note in r05 is ok.
Myungjune (LGE) proposes to agree r03.
Saso (Intel) points out that r03 requires special handling for MUSIM during AN Release.
Steve (Huawei) objects to r03.
alessio (nokia) is happy with r06.
Qian (Ericsson) prefers R05, R05 with NOTE update, but also ok to live with R06/R04.
Curt (Charter) supports Saso (Intel) with a modified NOTE based on r5.
Saso (Intel) proposes to check the status on CC#4. One possibility is to agree r05 with a shortened NOTE: NOTE W: If AMF does not perform steps 5-7 before step 2 then there might be some DL data not able to be deliveredy to the UE (e.g, may result in accounting discrepancy).
==== 8.X, 9.X Final Deadline ====
alessio(nokia) ok with R05 with the modified note but r06 as fallback. Nokia is concerned we need to add notes as condition for approval.
Omkar (CableLabs) supports R05 with the modified NOTE.
Revised
8.10 S2-2105152 CR Approval 23.502 CR2724R4 (Rel-17, 'B'): Introduction of Leaving procedure - 5GS Intel, Lenovo, Motorola Mobility, MediaTek, Apple, Ericsson, [Samsung], [LG Electronics], [Qualcomm], [Xiaomi], [China Telcom], [Charter], [Oppo], [Vodafone], [Spreadtrum], [Matrixx] Rel-17 Revision of S2-2103791r05 + changes, merging S2-2104065. CC#4: Approved. CC#5: Confirmed approved Agreed
8.10 S2-2104065 CR Approval 23.502 CR2724R3 (Rel-17, 'B'): Introduction of Leaving procedure - 5GS LG Electronics Rel-17 Revision of (Endorsed) S2-2103033. Merged into S2-2105152 Xiaowan(vivo) provides comments
Ouyang(Huawei) objects to this CR.
Saso (Intel) provides r01.
Curt (Charter) seeks clarifications from Ouyang and Xiaowan.
Myungjune (LGE) replies to Xiaowan (vivo) and Ouyang (Huawei).
Lars (Sony) comments
Myungjune (LGE) responses to Lars (Sony).
Myungjune (LGE) provides r02.
Saso (Intel) seeks clarification from Myungjune (LGE).
Steve (Huawei) comments
Myungjune (LGE) replies to Saso (Intel).
Guillaume (MediaTek) expresses concerns with NAS leaving to RRC Inactive.
Saso (Intel) replying to Myungjune and Steve.
Lars (Sony) comments to all.
Saso (Intel) replies to Lars (Sony).
Saso (Intel) replies to Steve.
Lars (Sony) responds to Steve (Huawei)
Curt (Charter) comments...why should we want have two different access release procedures for end-state = RRC-IDLE?
Myungjune (LGE) provides r03.
Qian (Ericsson) asks a question
Saso (Rapporteur) announces that this topic has been included in the MUSIM questions for CC#2.
Curt (Charter) replies to Qian
Qian (Ericsson) provides further comments
Myungjune (LGE) replies to Qian (Ericsson)
Qian (Ericsson) gives further comments
Qian (Ericsson) asks questions
Myungjune (LGE) responds to Qian (Ericsson)
Saso (Intel) proposes to NOTE the CR based on the discussion on CC#3.
Qian (Ericsson) provides r04 in case this paper can be discussed further.
Qian (Ericsson) provides r05.
Saso (Intel) proposes to NOTE this document or consider it MERGED in S2-2103791.
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson) provides comments.
Curt (Charter) supports Qian that the use of RRC Inactive is not 'incapacitated' because of MUSIM. Holistic view with RAN input is needed.
Saso (Intel) seeks clarifications from Curt and Qian.
Qian (Ericsson) replies to Saso (Intel).
Myungjune (LGE) is ok to NOTE CR.
==== 8.X, 9.X Final Deadline ====
Merged
8.11 - - - Architecture aspects for using satellite access in 5G (5GSAT_ARCH) - - Docs:=30 -
8.11 - - - LSs - - Docs:=30 -
8.11 S2-2103770 LS In Action LS on multiple TACs per PLMN RAN WG2 (R2-2104377) Rel-17 Response drafted in S2-2104780. Final response in S2-2104891 Replied to
8.11 S2-2104780 LS OUT Approval [DRAFT] LS Response to LS on multiple TACs per PLMN Qualcomm Incorporated Rel-17 r09 agreed. Revised to S2-2104891. Stefan (Ericsson) comments and provides r01
DongYeon (Samsung) agrees with Stefan, and provides r02.
Yuxin(Xiaomi) agree with Stefan and DongYeon. Provide r03.
Stephen (Qualcomm) comments on r01, r02 and r03
Jean Yves (Thales) agrees with Stephen and provides r04
Stephen (Qualcomm) provides r05
Sherry (Xiaomi) provides r06.
DongYeon (Samsung) provides r07 and comments.
DongYeon (Samsung) corrects missing word in previous comment.
Stephen (Qualcomm) clarifies the previous comments were for r06 and r07 (not r05)
Stephen (Qualcomm) provides r08
DongYeon (Samsung) provides r09.
Hannu (Nokia) prefers r09 which is more precise.
Wanqiang (Huawei) is OK with r09.
Stefan (Ericsson) is OK with r09
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) also agrees r09
Jean Yves (Thales) is ok for r09
Sherry (Xiaomi) is fine with r09
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2104891 LS OUT Approval LS Response to LS on multiple TACs per PLMN SA WG2 Rel-17 Revision of S2-2104780r09. Approved Approved
8.11 S2-2103716 LS In Action LS from RAN WG2: LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G RAN WG2 (R2-2008229) Revision of Postponed S2-2102081 from S2#144E. Postponed DongYeon (Samsung) proposes to postpone this LS because corresponding document has not been submitted in this meeting Postponed
8.11 S2-2103737 LS In Information LS from SA WG3-LI: Reply LS on UE location aspects in NTN SA WG3-LI (S3i210282) Rel-17 Noted Noted
8.11 S2-2103749 LS In Information LS to ITU-T on extraterritorial use of MCC+MNC for satellite networks CT WG1 (C1-212539) Rel-17 Noted DongYeon (Samsung) proposes to NOTE this LS, it is for information to SA2 and no action needed Noted
8.11 S2-2103761 LS In Information LS on selecting a PLMN not allowed in the country where a UE is physically located CT WG1 (C1-212600) Rel-17 Noted DongYeon (Samsung) proposes to NOTE this LS, it is for information to SA2 and no action needed Noted
8.11 S2-2105096 LS In Information LS from SA WG1: Reply LS on selecting a PLMN not allowed in the country where a UE is physically located SA WG1 (S1-211503) Rel-17 Postponed Postponed
8.11 S2-2104793 LS In Information LS from SA WG1: Reply LS on selecting a PLMN not allowed in the country where a UE is physically located SA WG1 (S1-211319) Rel-17 Noted Hannu (Nokia) proposes to note the LS as SA2 is only CC'd and there is no action for us. Noted
8.11 S2-2103823 CR Approval 23.501 CR2859 (Rel-17, 'B'): RAT fallback and Emergency Service fallback to NR Satellite Access Rakuten Mobile Rel-17 Noted Yuxin (Xiaomi) provides r01
Stephen (Qualcomm) comments that this is out of scope of Rel-17 and deals with an extremely unlikely scenario
Stefan (Ericsson) agrees with Stephen and proposes to note the paper
Tyler (OTD) agrees with Stephen and Stefan that this paper should be noted due to similar reasons.
Hannu (Nokia) supports the proposal to note.
Aoken (Rakuten Mobile) comments that there can be the use case.
Jean Yves (Thales) proposes to add the topic as candidate feature to rel18 Sat SID
Wanqiang (Huawei) agrees to note the paper as not in the SID scope.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2103824 CR Approval 23.502 CR2735 (Rel-17, 'B'): RAT fallback and Emergency Service fallback to NR Satellite Access Rakuten Mobile Rel-17 Noted Yuxin (Xiaomi) provides r01
Stephen (Qualcomm) objects to this CR
Stefan (Ericsson) agrees with Stephen and proposes to note the paper
Hannu (Nokia) supports Stefan and Stephen.
Jean Yves (Thales) proposes to add the topic as candidate feature to rel18 Sat SID
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2103831 CR Approval 23.501 CR2860 (Rel-17, 'F'): Clarifications to satellite backhaul CATT Rel-17 Merged into S2-2104893 Haris(Qualcomm) proposes to mark it merged in S2-2104592
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.11 S2-2104277 CR Approval 23.503 CR0554R2 (Rel-17, 'F'): Corrections and clarification on satellite backhaul CATT Rel-17 Revision of (Agreed) S2-2103554. Confirm CR Revision - CR states 0! Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.11 S2-2104412 CR Approval 23.501 CR2925 (Rel-17, 'F'): Alternative QoS profile for satellite backhaul Samsung Rel-17 Noted Stefan (Ericsson) questions the use of alternative QoS for satellite backhaul
Hannu (Nokia) questions whether we need any note in TS 23.501 at all, assuming the normative requirements are in place in TS 23.503.
DongYeon (Samsung) replies.
Hucheng(CATT) tends to agree with Stefan (Ericsson).
Jean Yves (Thales) comments
Stefan (Ericsson) agrees with Hucheng and replies to DongYeon
Sherry (Xiaomi) comments.
DongYeon (Samsung) replies with correction.
Jean Yves (Thales) proposes to note the CR.
==== 8.X, 9.X Revisions Deadline ====
Stefan (Ericsson) objects to the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2104490 CR Approval 23.502 CR2829 (Rel-17, 'B'): SMF reports satellite backhaul information to PCF during the PDU session establishment procedure Huawei, HiSilicon Rel-17 Revised to S2-2104892, merging S2-2104316. Yuxin (Xiaomi) proposes this CR to be merged into S2-2104316
Wanqiang (Huawei) comments that as the S2-2104316 revision going to the same as 4490, then proposes to approve the 4490 original version.
==== 8.X, 9.X Revisions Deadline ====
Jean Yves (Thales) proposes to note the CR
Wanqiang (Huawei) proposes to agree 4490 as the merge is not needed finally.
Wanqiang (Huawei) disagree with the process argument to note 4490.
Yuxin (Xiaomi) proposes to merge S2-2104490r00 with S2-2104316r03.
Wanqiang (Huawei) proposes to agree 4490.
Jean Yves (Thales) comments.
Andy (VC, Samsung) suggests going with 04490r00.
Jean Yves (Thales) cancels previous proposal to Note and is ok to follow Mr VC recommendations.
Wanqiang (Huawei) comments.
Sherry (Xiaomi) is fine to agree 4490 and asks if possible to add Xiaomi as co-sourcing company.
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2104892 CR Approval 23.502 CR2829R1 (Rel-17, 'B'): SMF reports satellite backhaul information to PCF during the PDU session establishment procedure Huawei, HiSilicon Rel-17 Revision of S2-2104490, merging S2-2104316. Approved Agreed
8.11 S2-2104592 CR Approval 23.501 CR2948 (Rel-17, 'C'): Removal of UPF indication of backhaul QoS to SMF Nokia, Nokia Shanghai Bell, Xiaomi Rel-17 r07 agreed. Revised to S2-2104893, merging S2-2103831 Haris(Qualcomm) provides comments to the AMF detection of satellite backhaul
Hannu (Nokia) questions how realistic is the CU/DU split in Rel-17?
Haris(Qualcomm) comments
Hucheng(CATT) has a similar question as Hannu, and points out to focus on basic scenarios of using satellite backhaul in release 17.
Yuxin (Xiaomi) provides comments
Saso (Intel) comments and proposes to delete the NOTE.
Wanqiang (Huawei) comments and proposes to focus on the basic scenario.
Saso (Intel) replies to Wanqiang (Huawei).
Haris(Qualcomm) suggests to replace the NOTE instead of removing it
Saso (Intel) provides r01.
Hannu (Nokia) supports r01.
Wanqiang (Huawei) replies to Saso (Intel).
Jean Yves (Thales) supports r01.
Stefan (Ericsson) provides r02
Hucheng (CATT) provide r03 and proposes to merge S2-2103831 into this paper.
Haris(Qualcomm) comments that r03 is incorrect
Hucheng(CATT) think the case mentioned by Haris(Qualcomm) makes the solution complex, and should not be considered in Rel17, in contrast, r03 gives a most easy way to move forward.
Hucheng (CATT) comments and ask the questions.
Sherry (Xiaomi) provides r04.
Hucheng (CATT) comments and provides r05.
Jean Yves (Thales) comments
Stefan (Ericsson) comments and prefers r02
Saso (Intel) comments and prefers r02
Hucheng(CATT) can not accept r02.
Hannu (Nokia) shares r06 and comments that r02 says what Hucheng(CATT) says. Nokia can live with r05 or r06 but prefers r02 for its simplicity.
Sherry (Xiaomi) replies and provides r07.
Sherry (Xiaomi) comments.
Hannu (Nokia) responds to Sherry (Xiaomi) and proposes the meeting to choose between r02 and r06.
Hannu (Nokia) can agree also r07. Proposes to choose among r02, r06 and r07.
Saso (Intel) is ok with both r06 and r07. Replies to Hucheng.
Wanqiang (Huawei) object r06 and any other version stating the user plane and control plane differently.
Hannu (Nokia) proposes to go back to r02 which is the bare minimum version that says what needs to be said an nothing more.
Hucheng(CATT) clarifies the assumption to make the AMF configuration work, and provides r08.
==== 8.X, 9.X Revisions Deadline ====
Saso (Intel) is ok with r02, r06, r07 and r08.
Haris(Qualcomm) supports r02
Hannu (Nokia) can agree r02, r06, r07 or r08.
DongYeon (Samsung) objects to r06.
Wanqiang (Huawei) is ok with r08.
Sherry (Xiaomi) can agree r02, r06, r07 or r08.
Jean Yves (Thales) can agree r02, r06, r07 or r08.
Haris(Qualcomm) objects to r08
Stefan (Ericsson) agrees with Haris regarding r08 and proposes to use r02 or r07.
==== 8.X, 9.X Final Deadline ====
Relja (TNO) supports r02 or r07.
Revised
8.11 S2-2104893 CR Approval 23.501 CR2948R1 (Rel-17, 'C'): Removal of UPF indication of backhaul QoS to SMF Nokia, Nokia Shanghai Bell, Xiaomi Rel-17 Revision of S2-2104592r07, merging S2-2103831. Approved Agreed
8.11 S2-2104670 CR Approval 23.503 CR0601 (Rel-17, 'C'): Determination of 5QI for satellite backhaul Xiaomi Rel-17 r02 agreed. Revised to S2-2104855. DongYeon (Samsung) comments.
Stefan (Ericsson) comments, and questions the need for the CR
Haris(Qualcomm) proposes to note the CR
Sherry(Xiaomi) requests Haris to clarify why it is not need.
Haris(Qualcomm) responds
Sherry(Xiaomi) provides r01.
Sherry (Xiaomi) replies.
Stefan (Ericsson) proposes to note the CR
DongYeon (Samsung) proposes to note the CR.
Stefan (Ericsson) comments and provides r02
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) can only accept r02.
Sherry (Xiaomi) is fine with r02.
Jean Yves (Thales) is ok with r02.
Haris(Qualcomm) ok with r02
Relja (TNO) is ok with r02.
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2104855 CR Approval 23.503 CR0601R1 (Rel-17, 'C'): Determination of 5QI for satellite backhaul Xiaomi Rel-17 Revision of S2-2104670r02. Approved Agreed
8.11 S2-2104316 CR Approval 23.502 CR2799 (Rel-17, 'C'): Satellite backhaul with long delay notification to the PCF xiaomi Rel-17 Merged into S2-2104892 Stefan (Ericsson) provides r01
Mirko (Huawei) comments.
Stefan (Ericsson) agrees with Mirko and provides r02
DongYeon (Samsung) provides r03.
DongYeon (Samsung) objects to r00.
Yuxin (Xiaomi) agrees with the changes
Hannu (Nokia) supports r03.
Yuxin (Xiaomi) supports r03.
Wanqiang (Huawei) comments that as the change now going to the same one as 4490, then propose to use 4490.
==== 8.X, 9.X Revisions Deadline ====
Jean Yves (Thales) supports r03.
==== 8.X, 9.X Final Deadline ====
Merged
8.11 S2-2104593 CR Approval 23.502 CR2844 (Rel-17, 'C'): Satellite backhaul with long delay notification to the SMF Xiaomi, Nokia, Nokia Shanghai Bell Rel-17 r04 agreed. Revised to S2-2105133. Stefan (Ericsson) provides r01
Haris(Qualcomm) provides r02
Hannu (Nokia) supports r02
DongYeon (Samsung) provides r03 with updated cover page and co-signed.
Hannu (Nokia) agrees r03 and thanks DongYeon (Samsung) for support.
Sherry (Xiaomi) provides r04 with editorial change (totally removing the 3rd change in r03).
Hannu (Nokia) agrees r04 but points out that clause 5.2.2.3.1 must be removed also from the cover page in the final version.
==== 8.X, 9.X Revisions Deadline ====
DongYeon (Samsung) agree with r04 (remove clause 5.2.2.3.1 from coversheet).
Sherry (Xiaomi) agrees to remove clause 5.2.2.3.1 from coversheet, and it is already removed with revision mark in r04.
Hucheng (CATT) is OK with r04.
Jean Yves (Thales) is OK with r04.
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2105133 CR Approval 23.502 CR2844R1 (Rel-17, 'C'): Satellite backhaul with long delay notification to the SMF Xiaomi, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104593r04. Approved Agreed
8.11 S2-2104317 CR Approval 23.503 CR0591 (Rel-17, 'B'): Policy Control Request Trigger condition and Eventing report modification Xiaomi Rel-17 Noted Stefan (Ericsson) provides comments
Hannu (Nokia) suspects that this might be outside of 5GSAT_ARCH scope.
Yuxin (Xiaomi) agree with comments
Jean Yves (Thales) proposes to note the CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2104314 CR Approval 23.501 CR2916 (Rel-17, 'B'): UPF selection based on the UPF ability to support satellite connection xiaomi Rel-17 Noted Stefan (Ericsson) provides questions
Hannu (Nokia) has concerns on this CR.
Yuxin (Xiaomi) answer question.
Hannu (Nokia) asks for further clarification.
Stefan (Ericsson) asks follow-up question
Yuxin (Xiaomi) give clarification
Stefan (Ericsson) replies to Yuxin
Yuxin (Xiaomi) requests clarification
Hannu (Nokia) proposes to NOTE the CR as the required behaviour does not require any change.
Stefan (Ericsson) replies and proposes to note the CR
Yuxin (Xiaomi) replies and postpone to next release
Yuxin (Xiaomi) provides r01 based on comments
Hannu (Nokia) agrees with the intention of Yuxin (Xiaomi) but provides r02 to improve the wording.
Yuxin (Xiaomi) comments and provide r03
Stefan (Ericsson) proposes to note the CR
==== 8.X, 9.X Revisions Deadline ====
Stefan (Ericsson) objects to the CR
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2104315 CR Approval 23.502 CR2798 (Rel-17, 'C'): PDU session establishment handling in SMF based on satellite information xiaomi Rel-17 Noted Hannu (Nokia) asks whether this CR is a partial duplicate and if it can be merged to S2-2104593?
Yuxin (Xiaomi) provides comments
DongYeon (Samsung) comments and asks questions.
Yuxin (Xiaomi) give answers to DongYeon(Samsung).
Hannu (Nokia) withdraws his earlier proposal to merge and expresses concerns on S2-2104315.
Stefan (Ericsson) expresses similar concerns as Hannu
Haris(Qualcomm) proposes to note
Jean Yves (Thales) proposes to note also
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.11 S2-2104774 CR Approval 23.502 CR2875 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 Postponed Stefan (Ericsson) comments and suggest to postpone the CR to take also CT1 feedback into account
DongYeon (Samsung) suggests to postpone the CR.
Yuxin (Xiaomi) suggest to postpone until LS feedback from CT1.
Jean Yves (Thales) proposes also to postpone as Opt2 requires CT1 feedback
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees with postponement for this meeting
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2104777 CR Approval 23.501 CR2748R1 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 Revision of (withdrawn) S2-2102402. Postponed Stefan (Ericsson) comments and suggest to postpone the CR to take also CT1 feedback into account
DongYeon (Samsung) suggests to postpone the CR.
Yuxin (Xiaomi) suggest to postpone until LS feedback from CT1.
Jean Yves (Thales) proposes also to postpone as Opt2 requires CT1 feedback / same as S2-2104774
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees with postponement - for this meeting
==== 8.X, 9.X Final Deadline ====
Postponed
8.11 S2-2104781 CR Approval 23.167 CR0361R1 (Rel-17, 'B'): Support of IMS Emergency Calls over NR Satellite Access Qualcomm Incorporated Rel-17 Revision of (Postponed) S2-2102395. r07 agreed. Revised to S2-2105134. Stephen (Qualcomm) provides r01
Yuxin (Xiaomi) provides r02
Chris (Vodafone) provides r03
Hannu (Nokia) provides r04
Yuxin (Xiaomi) ask a question
Chris (Vodafone) answers Xiaomi. The Nokia r04 is OK.
Yuxin (Xiaomi) provides r05 .
Hannu (Nokia) provides r06.
Chris (Vodafone) provides r07.
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) slightly prefers r06 followed by r07 and then r05
Hannu (Nokia) prefers r07. Can also agree r06.
==== 8.X, 9.X Final Deadline ====
Revised
8.11 S2-2105134 CR Approval 23.167 CR0361R2 (Rel-17, 'B'): Support of IMS Emergency Calls over NR Satellite Access Qualcomm Incorporated Rel-17 Revision of S2-2104781r07. Approved Agreed
8.12 - - - Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) - - Docs:=6 -
8.12 S2-2103931 CR Approval 23.287 CR0154 (Rel-17, 'B'): Support of QoS aware NR PC5 power efficiency for P-UEs LG Electronics, Deutsche Telekom, ZTE, Lenovo, Motorola Mobility, Tencent, Intel, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 r06 agreed. Revised to S2-2105135, merging S2-2104296 Ouyang(Huawei) provides r01
LaeYoung (LGE) provides r02.
Hong (Qualcomm) provides r03.
shabnam (Ericsson) provides r04, adding the Layer 2 ID aspect that got missed in the new text.
Hao Dong (ZTE) reminds Shabnam (Ericsson).
Ouyang(Huawei) provides r05.
LaeYoung (LGE) provides r06.
Ouyang(Huawei) is OK with r06.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.12 S2-2105135 CR Approval 23.287 CR0154R1 (Rel-17, 'B'): Support of QoS aware NR PC5 power efficiency for P-UEs LG Electronics, Deutsche Telekom, ZTE, Lenovo, Motorola Mobility, Tencent, Intel, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of S2-2103931r06, merging S2-2104296. Approved Agreed
8.12 S2-2103932 CR Approval 23.287 CR0155 (Rel-17, 'B'): PC5 QoS parameters from V2X layer to AS layer of Rx UE for broadcast and groupcast LG Electronics, Deutsche Telekom, ZTE, Lenovo, Motorola Mobility, Tencent, Intel, Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Approved
==== 8.X, 9.X Final Deadline ====
Agreed
8.12 S2-2104294 CR Approval 23.287 CR0156 (Rel-17, 'B'): PC5 DRX parameters determination Huawei, HiSilicon Rel-17 r02 agreed. Revised to S2-2105136. Antoine (Orange) provides r01 with some rewording.
LaeYoung (LGE) provides r02.
Antoine (Orange) asks a question on r00 and r02.
LaeYoung (LGE) replies to Antoine (Orange).
Antoine (Orange) replies to LaeYoung (LGE).
LaeYoung (LGE) answers to Antoine (Orange).
Ouyang(Huawei) replies to LaeYoung (LGE)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.12 S2-2105136 CR Approval 23.287 CR0156R1 (Rel-17, 'B'): PC5 DRX parameters determination Huawei, HiSilicon Rel-17 Revision of S2-2104294r02. Approved Agreed
8.12 S2-2104296 CR Approval 23.287 CR0157 (Rel-17, 'B'): PC5 DRX parameters provision Huawei, HiSilicon Rel-17 Merged into S2-2105135 LaeYoung (LGE) proposes to MERGE this CR to S2-2103931.
Hong (Qualcomm) also thinks it should be merged into 3931.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.13 - - - 5G System Enhancement for Advanced Interactive Services (5G_AIS) - - Docs:=7 -
8.13 S2-2103767 LS In Action LS from RAN WG1: LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) RAN WG1 (R1-2104117) Rel-17 Noted Dario S. Tonesi (Qualcomm) supports Lei's proposal to note the LS Noted
8.13 S2-2103905 CR Approval 23.501 CR2701R1 (Rel-17, 'B'): New 5QI values to support Advance Interactive Services (AIS) in 5G Ericsson, Verizon, Qualcomm Incorporated, AT&T, Sony, MediaTek Inc., Tencent, LG Electronics, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Endorsed) S2-2102178. r03 agreed. Revised to S2-2105137. Dario S. Tonesi (Qualcomm) provides r01
Lei (Tencent) agree with Dario(Qualcomm) proposal. Ok with approving r00 if the agreed LS was not received or approve r01 if received.
==== 8.X, 9.X Revisions Deadline ====
Dario S. Tonesi (Qualcomm) supports Lars' proposal to go with r03
Lei(Tencent) agree with Dario and Lars' proposal to go with r03 considering the latest status.
==== 8.X, 9.X Final Deadline ====
Revised
8.13 S2-2105137 CR Approval 23.501 CR2701R2 (Rel-17, 'B'): New 5QI values to support Advance Interactive Services (AIS) in 5G Ericsson, Verizon, Qualcomm Incorporated, AT&T, Sony, MediaTek Inc., Tencent, LG Electronics, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2103905r03. Approved Agreed
8.13 S2-2103906 CR Approval 23.501 CR2638R4 (Rel-17, 'B'): New standardized 5QI values for Advanced Interactive Services Ericsson Rel-17 Revision of (Postponed) S2-2102177. Confirm CR Number - CR states 2701! Merged into S2-2105138 Lei (Tencent) propose to go ahead with S2-2104116, marked this CR as merged or noted.
Devaki (Nokia) supports Lei's proposal. Proposes to consider this CR as merged or noted.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.13 S2-2104116 CR Approval 23.501 CR2740R1 (Rel-17, 'B'): New standardized 5QI values for Advanced Interactive Services Nokia, Nokia Shanghai Bell, Tencent, AT&T, Qualcomm Incorporated, MediaTek Inc. Rel-17 Revision of (Endorsed) S2-2102370. r02 agreed. Revised to S2-2105138, merging S2-2103906 Mirko (Huawei) proposed r01.
==== 8.X, 9.X Revisions Deadline ====
Devaki (Nokia) provides r02 just to add DT as cosigning company.
Lei (Tencent) is ok with r00, r01 and r02.
Lei (Tencent) ok with r00, r01.
Lars (Sony) supports r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.13 S2-2105138 CR Approval 23.501 CR2740R2 (Rel-17, 'B'): New standardized 5QI values for Advanced Interactive Services Nokia, Nokia Shanghai Bell, Tencent, AT&T, Qualcomm Incorporated, MediaTek Inc. Rel-17 Revision of S2-2104116r02, merging S2-2103906. Approved Agreed
8.13 S2-2104663 CR Approval 23.501 CR2967 (Rel-17, 'F'): Applicability of PER Qualcomm Incorporated, Vodafone Rel-17 Noted Devaki (Nokia) comments and raises a question for clarification.
Devaki (Nokia) provides r01.
Paul (Ericsson) provides question for clarification.
Chris (Vodafone) replies and says that r01 is not useful.
Chris (Vodafone) provides r02.
Paul (Ericsson) provides comments and proposes to note this CR.
Dario S. Tonesi (Qualcomm) proposes to note this paper.
Devaki (Nokia) agrees with Paul (Ericsson), proposes to note the paper.
Dario S. Tonesi (Qualcomm) asks to ignore his previous comment that was to the wrong email thread.
Dario S. Tonesi (Qualcomm) provides r03
==== 8.X, 9.X Revisions Deadline ====
Chris (Vodafone) accepts r03, but the main problem still needs to be treated.
Lars (Sony) agrees with Paul and propose to Note the CR.
Paul (Ericsson) objects to that CR in all revisions.
==== 8.X, 9.X Final Deadline ====
Noted
8.14 - - - Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) - - Docs:=28 -
8.14 S2-2103735 LS In Action LS from RAN WG2: Response LS on Scheduling Location in Advance to reduce Latency RAN WG2 (R2-2104420) Rel-17 Responses drafted in S2-2104247, S2-2104438, S2-2104459 and S2-2104773. Final response in S2-2105122 Replied to
8.14 S2-2104247 LS OUT Approval [DRAFT] Reply LS on Scheduling Location in Advance to reduce Latency vivo Rel-17 Response to S2-2103735. Merged into S2-2105122 Zhenhua (vivo) proposes merging 4247 (vivo) into 4459 (Huawei), and discuss in that thread.
Åke (Ericsson) propose to merge to S2-2104438 per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) also proposes to merge this into S2-2104438 which now appears the most likely version of the draft LS to achieve a consensus
==== 8.X, 9.X Final Deadline ====
Merged
8.14 S2-2104438 LS OUT Approval [DRAFT] Response LS on Scheduling Location in Advance to reduce Latency CATT Rel-17 Response to S2-2103735. r08 agreed. Revised to S2-2105122, merging S2-2104247, S2-2104459 and S2-2104773 Zhenhua (vivo) proposes merging 4438 (CATT) into 4459 (Huawei), and discuss in that thread.
Yunjing (CATT) provides r01 based on offline discussion and agreements in CC#3.
Runze (Huawei) provides r02.
Stephen (Qualcomm) provides r03
Zhenhua (vivo) provides r04
Runze (Huawei) supports r04
Åke (Ericsson) provides r05
Zhenhua (vivo) provides r07
Åke (Ericsson) provides r08
==== 8.X, 9.X Revisions Deadline ====
Yunjing(CATT) is ok with r08.
Runze (Huawei) supports r07
Yunjing (CATT) provides r09 and r10 to move forward.
Zhenhua (vivo) is fine with r08.
Stephen (Qualcomm) is also fine with r08
Åke (Ericsson) Clarifies on comment from Zhenhua.
Leo (Deutsche Telekom) prefers r08, and objects to r09 and r10 provided after revision deadline.
Yunjing (CATT) is ok with r08.
Sherry (Xiaomi) prefers r01 and can accept r08 to progress the work.
Åke (Ericsson) Accept r08 and no other revisions
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105122 LS OUT Approval Response LS on Scheduling Location in Advance to reduce Latency SA WG2 Rel-17 Revision of S2-2104438r08, merging S2-2104247, merging S2-2104247 and S2-2104459, merging S2-2104247, S2-2104459 and S2-2104773. Approved Approved
8.14 S2-2104459 LS OUT Approval [DRAFT] LS response on scheduled location time Huawei Rel-17 Response to S2-2103735. Merged into S2-2105122 Zhenhua (vivo) proposes merging 4247 (vivo), 4438 (CATT), and 4773 (Qualcomm) into 4459 (Huawei), and discuss in this thread.
Åke (Ericsson) propose to merge to S2-2104438 per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) also proposes to merge this into S2-2104438 per CC#3
==== 8.X, 9.X Final Deadline ====
Merged
8.14 S2-2104773 LS OUT Approval [DRAFT] Response LS on Scheduling Location in Advance to reduce Latency Qualcomm Incorporated Rel-17 Response to S2-2103735. Merged into S2-2105122 Zhenhua (vivo) proposes merging 4773 (Qualcomm) into 4459 (Huawei), and discuss in that thread.
Åke (Ericsson) propose to merge to S2-2104438 per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees to the merger
==== 8.X, 9.X Final Deadline ====
Merged
8.14 S2-2103800 LS OUT Approval [DRAFT] LS on determination of location estimates in local co-ordinates Ericsson r01 agreed. Revised to S2-2105124, merging S2-2104434 Stephen (Qualcomm) supports the LS but believes it should be sent TO: RAN1, RAN2 and RAN3
Åke (Ericsson) Agree sending to RAN1, RAN2 and RAN3. Provides r01
==== 8.X, 9.X Revisions Deadline ====
Leo (Deutsche Telekom) supports r01 but requests one additional change in 'actions'
Åke (Ericsson) Suggest comment from Leo to be resolved as editorial clean up
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105124 LS OUT Approval LS on determination of location estimates in local co-ordinates SA WG2 - Revision of S2-2103800r01, merging S2-2104434. Approved Approved
8.14 S2-2103801 CR Approval 23.273 CR0147R2 (Rel-17, 'C'): Add time of position determination to Deferred MT-LR periodic Ericsson Rel-17 Revision of (Endorsed) S2-2102046. Postponed Åke (Ericsson) propose to postpone per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2103836 CR Approval 23.273 CR0150R3 (Rel-17, 'C'): Support for Multiple QoS Class in deferred location requests Samsung, Ericsson Rel-17 Revision of (Agreed) S2-2103085. r05 agreed. Revised to S2-2105125, merging S2-2104478 Stephen (Qualcomm) maintains that the CR is not justified
Tyler (OTD) provides comment
David (Samsung) provides r01 merging S2-2104478, replies to Qualcomm and OTD
Stephen (Qualcomm) provides r02 to support Minimum Accuracy
David (Samsung) provides questions on r02, cannot see the benefits.
Stephen (Qualcomm) provides answers to David (Samsung) on r02
David (Samsung) provides comments.
Stephen (Qualcomm) provides more comments
Runze (Huawei) provides r03.
Stephen (Qualcomm) comments on the r03
David (Samsung) provides r04, anticipates objection to revisions not respecting Multiple QoS Class agreed at SA2#144E.
Tyler (OTD) provides question on r04.
David (Samsung) replies to OTD.
Stephen (Qualcomm) comments on the r04
David (Samsung) provides r05.
==== 8.X, 9.X Revisions Deadline ====
Runze (Huawei) supports r05.
Leo (Deutsche Telekom) supports r05, but requests a correction on cover sheet.
Stephen (Qualcomm) clarifies that while the CR is not preferred (except for r02), there is no objection
David (Samsung) thanks companies for support, checks need to open CR at CC#4 for cover sheet correction.
Tyler (OTD) provides comment on r05, prefers r02, but will not object to r05.
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105125 CR Approval 23.273 CR0150R4 (Rel-17, 'C'): Support for Multiple QoS Class in deferred location requests Samsung, Ericsson Rel-17 Revision of S2-2103836r05, merging S2-2104478. Approved Agreed
8.14 S2-2104013 CR Approval 23.273 CR0174 (Rel-17, 'C'): LMF Parameters Support for non-3GPP Access Nokia, Nokia Shanghai Bell Rel-17 Confirm CR Number - CR states ! r01 agreed. Revised to S2-2105126. Stephen (Qualcomm) asks two questions
Yunjing (CATT) provides comment.
Åke (Ericsson) Provides r01 and justify use of TNAP/TWAP Id
Yunjing (CATT) asks questions for clarification
Åke (Ericsson) Provides clarification to Yunjing
Simon Cai (Nokia) replies to Stephen
Simon Cai (Nokia) replies to Yunjing
Simon Cai (Nokia) agrees with r01
Yunjing (CATT) replies to Åke
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 but not the r00
Leo (Deutsche Telekom) objects r00, supports r01 and requests to correct the cover sheet.
Cai Simon (Nokia) clarifies to Leo (Deutsche Telekom)
Åke (Ericsson) point out r01 don't change clause 2
Leo (Deutsche Telekom) is fine with clarification
Yunjing (CATT) can agree the r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105126 CR Approval 23.273 CR0174R1 (Rel-17, 'C'): LMF Parameters Support for non-3GPP Access Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104013r01. Approved Agreed
8.14 S2-2104014 CR Approval 23.273 CR0175 (Rel-17, 'C'): Support for Area Decision of Satellite Access Nokia, Nokia Shanghai Bell Rel-17 Confirm CR Number - CR states ! r01 agreed. Revised to S2-2105127. Stephen (Qualcomm) supports the intent of the CR but not the solution
Cai Simon(Nokia) clarifies to Stephen (Qualcomm)
Yunjing (CATT) provides comment
Stephen (Qualcomm) provides r01 (changes in green)
Cai Simon (Nokia) clarifies to Yunjing (CATT)
Yunjing (CATT) provides comment.
Tyler (OTD) provides comment on QC proposed r1
Cai Simon (Nokia) accepts the pre-configuration and provides r02
Stephen (Qualcomm) comments on the r02
Yunjing (CATT) asks question for clarification on r01.
Yunjing (CATT) replies to Cai Simon (Nokia).
Cai Simon (Nokia) clarifies each concern in r02
Yunjing (CATT) clarifies
Simon Cai (Nokia) agree with clarification
Stephen (Qualcomm) comments again
Sherry (Xiaomi) comments.
==== 8.X, 9.X Revisions Deadline ====
Simon Cai (Nokia) provides r03 based on Qualcomm input
Simon Cai (Nokia) clarifies to Sherry
Stephen (Qualcomm) can agree r01 but not other revisions
Cai Simon (Nokia) clarifies to Stephen
Åke (Ericsson) can agree r01 but no other revisions
Simon Cai (Nokia) accepts r01
Sherry (Xiaomi) prefers r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105127 CR Approval 23.273 CR0175R1 (Rel-17, 'C'): Support for Area Decision of Satellite Access Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104014r01. Approved Agreed
8.14 S2-2104245 DISCUSSION Discussion Discussion on scheduled location time. vivo Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.14 S2-2104246 DRAFTCR Agreement Addition of a Scheduled Location Time vivo Rel-17 Revision of (Endorsed at S2#143E) S2-2102047. Why a DRAFT CR ? Postponed Stephen (Qualcomm) comments that the CR is not against the latest version of TS 23.273 and contains unjustified changes
Åke (Ericsson) propose to postpone per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees with Ericsson to postpone, per CC#3
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2104403 CR Approval 23.273 CR0151R2 (Rel-17, 'B'): Addition of a Scheduled Location Time CATT Rel-17 Revision of (Endorsed) S2-2102047. Postponed Stephen (Qualcomm) comments that the CR is not against the latest version of TS 23.273 and contains unjustified changes
Åke (Ericsson) propose to postpone per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees with the proposal from Ericsson to postpone this, per CC#3
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2104434 LS OUT Approval [DRAFT] LS on local co-ordinates applied positioning methods CATT Rel-17 Merged into S2-2105124 Åke (Ericsson) Suggest to merge S2-2104434 into S2-2103800
Yunjing (CATT) is fine to merge S2-2104434 into S2-2103800
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Merged
8.14 S2-2104439 CR Approval 23.273 CR0176 (Rel-17, 'B'): UE positioning capability storage CATT Rel-17 r03 agreed. Revised to S2-2105123. Yunjing (CATT) proposes to merge this CR into S2-2104768.
Ouyang(Huawei) provides r01. Suggest to use this CR as baseline
Yunjing (CATT) is ok with r01 and provides right link for r01.
Stephen (Qualcomm) proposes to merge this into S2-2104768
Ouyang(Huawei) can't understand Stephen (Qualcomm)'s comments.
Yunjing (CATT) provides r02.
Ouyang(Huawei) suggests to create an LS to RAN2 about the variable/non-variable UE position capability.
Ouyang(Huawei) provides r04 with ENs
Yunjing (CATT) provides r03 based on comments from Ouyang(Huawei).
==== 8.X, 9.X Revisions Deadline ====
Ouyang(Huawei) suggests to go with r04, as the LS is sent to RAN2 for clarification.
Yunjing(CATT) can accept r04.
Stephen (Qualcomm) can accept r02 or r03 but not other versions
Ouyang(Huawei) can live with r03, but not r02.
Leo (Deutsche Telekom) prefers r03, but the cover sheet needs to be updated (Clauses affected).
Åke (Ericsson) can agree r03 but no other revisions
Yunjing (CATT) will update the cover sheet if r03 is approved.
Tyler (OTD) indicates support for r03
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105123 CR Approval 23.273 CR0176R1 (Rel-17, 'B'): UE positioning capability storage CATT Rel-17 Revision of S2-2104439r03. Approved Agreed
8.14 S2-2104440 CR Approval 23.502 CR2818 (Rel-17, 'B'): UE positioning capability storage in AMF CATT Rel-17 Approved Stephen (Qualcomm) supports this CR
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Agreed
8.14 S2-2104458 CR Approval 23.273 CR0177 (Rel-17, 'F'): Addition of a Scheduled Location Time Huawei, [Qualcomm Incorporated]? Rel-17 Confirm Sources! Postponed Stephen (Qualcomm) comments that the CR is not against the latest version of TS 23.273 and contains unjustified changes
Runze (Huawei) replied to Stephen.
Stephen (Qualcomm) replies to Runze (Huawei)
Runze (Huawei) replies to Stephen.
Åke (Ericsson) propose to postpone per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) also proposes to postpone per CC#3
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2104478 CR Approval 23.273 CR0179 (Rel-17, 'F'): Update of Multiple QoS Class in deferred location requests Huawei, HiSilicon Rel-17 Merged into S2-2105125 David (Samsung) provides comments, suggests to merge into S2-2103836
==== 8.X, 9.X Revisions Deadline ====
Åke (Ericsson) Support merge into S2-2103836
==== 8.X, 9.X Final Deadline ====
Merged
8.14 S2-2104768 CR Approval 23.273 CR0180 (Rel-17, 'B'): Storage of UE Positioning Capabilities by 5GCN Qualcomm Incorporated Rel-17 Postponed Ouyang(Huawei) has concern on this paper
Stephen (Qualcomm) provides responses to concerns from Ouyang (Huawei)
Ouyang(Huawei) doesn't consider a dedicated call flow is needed.
Yunjing (CATT) provides r01 and comments.
Ouyang(Huawei) proposes to note this paper, as this paper trying to address the variable positioning capabilities , which can't be determined or evaluated in SA2.
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) can agree the r01 and prefers this to the CR in S2-2104439
Ouyang(Huawei) considers postponing this contribution is the right way to go.
==== 8.X, 9.X Final Deadline ====
Postponed
8.14 S2-2104770 LS OUT Approval [DRAFT] LS on storage of UE Positioning Capabilities Qualcomm Incorporated Rel-17 CC#4: r02 agreed. Revised to S2-2105153. Ouyang(Huawei) comments that this LS depends on the outcome of other CRs discussion.
Ouyang(Huawei) provides r01, based on the discussion in S2-2104439.
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) comments that the revised LS assumes that the CR in S2-2104439 will be agreed rather than the CR originally referenced in S2-2104768. Thus, we can only agree the r01 if it will reference and attach whichever CR is finally agreed or technically endorsed.
Yunjing (CATT) provides comment.
Leo (Deutsche Telekom) objects to r00 and r01.
Yunjing (CATT) proposes the way forward.
Leo (Deutsche Telekom) agrees to the way forward.
==== 8.X, 9.X Final Deadline ====
Revised
8.14 S2-2105153 LS OUT Approval LS on storage of UE Positioning Capabilities SA WG2 Rel-17 Revision of S2-2104770r02. CC#4: Approved Approved
8.14 S2-2104772 CR Approval 23.273 CR0151R3 (Rel-17, 'B'): Addition of a Scheduled Location Time Qualcomm Incorporated Rel-17 Revision of (Endorsed) S2-2102047. Postponed Zhenhua (vivo) provides r01
Stephen (Qualcomm) comments on the r01
Cai Simon (Nokia) asks questions about the paper
David (Samsung) provides comments/question
Runze (Huawei) supports the view from (Zhenhua) vivo.
Stephen (Qualcomm) replies to comments
Sherry (Xiaomi) comments.
Åke (Ericsson) propose to postpone per agreement at CC#3
==== 8.X, 9.X Revisions Deadline ====
Stephen (Qualcomm) agrees to postponement
Simon Cai (Nokia) agrees to postponement
==== 8.X, 9.X Final Deadline ====
Postponed
8.15 - - - Multimedia Priority Service (MPS) Phase 2 (MPS2) - - Docs:=9 -
8.15 S2-2104691 CR Approval 23.401 CR3642 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 r01 agreed. Revised to S2-2105139. Robert (Perspecta Labs) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.15 S2-2105139 CR Approval 23.401 CR3642R1 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 Revision of S2-2104691r01. Approved Agreed
8.15 S2-2104693 CR Approval 23.203 CR1135 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 r03 agreed. Revised to S2-2105140. Belen (Ericsson) provies comments and asks questions
Belen (Ericsson) add some clarifications
Thomas(Nokia) comments that a number of emails with wrong subject were exchanged and forwards them to correct thread.
Mirko (Huawei) comments.
Mirko (Huawei) provides r02.
Mirko (Huawei) is ok with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.15 S2-2105140 CR Approval 23.203 CR1135R1 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 Revision of S2-2104693r03. Approved Agreed
8.15 S2-2104694 CR Approval 23.501 CR2971 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 r01 agreed. Revised to S2-2105141. Robert (Perspecta Labs) provides r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.15 S2-2105141 CR Approval 23.501 CR2971R1 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 Revision of S2-2104694r01. Approved Agreed
8.15 S2-2104708 CR Approval 23.503 CR0602 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 r03 agreed. Revised to S2-2105142. Thomas (Nokia) comments
Mirko (Huawei) comments.
Mirko (Huawei) is ok with r03.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.15 S2-2105142 CR Approval 23.503 CR0602R1 (Rel-17, 'B'): Additional authorization functionality in support of MPS for Data Transport Service Perspecta Labs, CISA ECD, T-Mobile USA INC Rel-17 Revision of S2-2104708r03. Approved Agreed
8.15 S2-2104759 DISCUSSION Information Discussion on additional authorization functionality in support of MPS for Data Transport Service. Perspecta Labs Rel-17 Noted
==== 8.X, 9.X Final Deadline ====
Noted
8.16 - - - Dynamic management of group-based event monitoring (TEI17_GEM) - - Docs:=3 -
8.16 S2-2103888 CR Approval 23.502 CR2743 (Rel-17, 'B'): Dynamic management of group based event monitoring Ericsson, Convida Wireless LLC, AT&T, Huawei Rel-17 r02 agreed. Revised to S2-2105172. Hannu (Nokia) proposes a revision in r01.
Qianghua (Huawei) provides r02, attempt to align part of the terms
Hannu (Nokia) supports r02.
Qian (Ericsson) supports also r02.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
8.16 S2-2105172 CR Approval 23.502 CR2743R1 (Rel-17, 'B'): Dynamic management of group based event monitoring Ericsson, Convida Wireless LLC, AT&T, Huawei Rel-17 Revision of S2-2103888r02. Approved Agreed
8.16 S2-2104615 CR Approval 23.682 CR0477R2 (Rel-17, 'B'): Dynamic management of group based event monitoring Ericsson, Convida Wireless LLC, AT&T, Huawei, Nokia, Nokia Shanghai Bell Rel-17 Revision of (Agreed) S2-2103043. Approved Marco (Huawei) comments and asks clarifications.
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson) comments that HW's comments/clarifications are for paper 4715, not 4615 (the tdoc in subject should be 4715).
==== 8.X, 9.X Final Deadline ====
Agreed
8.17 - - - N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) - - Docs:=0 -
8.18 - - - System enhancement for Redundant PDU Session (TEI17_SE_RPS) - - Docs:=8 -
8.18 S2-2103841 CR Approval 23.501 CR2736R2 (Rel-17, 'B'): 5G URLLC Handling redundant PDU Sessions (Nokia, Nokia Shanghai Bell, Convida Wireless, Verizon, Qualcomm,) Ericsson, (Huawei, Hisilicon, LG Electronics, ZTE) Rel-17 Revision of (Endorsed) S2-2103047. Noted Devaki (Nokia) proposes to consider this as merged with 4689 or note the paper (revision proposed by the source companies, also revisions are being proposed under 4689).
György (Ericsson) disagrees with merging the paper into 4689 due to the disagreement about URSP extension.
Devaki (Nokia) proposes to note this paper, the other paper has been progressed. If any revision is needed, propose revision to 4689.
Juan Zhang (Qualcomm) supports Nokia's comments and proposes to focus on the progress on 4689.
Juan Zhang (Qualcomm) proposes to focus on the progress on 4689, 3841 is can be noted or merged into 4689.
Hui (Huawei) objects to any revision of this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.18 S2-2103842 CR Approval 23.502 CR2658R2 (Rel-17, 'B'): PDU Session Pair Information provisioning to RAN (Huawei, HiSilicon), Ericsson Rel-17 Revision of (Endorsed) S2-2103048. Noted Devaki (Nokia) proposes to consider this as merged with 4500 or note the paper (revision by original source companies, provide revisions for 4500).
György (Ericsson) could be ok to merge 4500 into this paper including the RSN as well, but that is probably not what Nokia meant.
Yang (OPPO) considers this CR aligns with the principle in 2104689r03 (which is including both RSN and Pair ID). Support to merge it to 4500 for moving forward
György (Ericsson) proposes to use this CR to go forward and consider 4500 to be merged into this one.
Hui (Huawei) objects to any revision of the paper unless 501 issue is resolved.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
8.18 S2-2104500 CR Approval 23.502 CR2658R3 (Rel-17, 'B'): UE providing PDU Session Pair ID based on URSP rules Huawei, HiSilicon, Qualcomm Rel-17 Revision of (Endorsed) S2-2103048. r01 agreed. Revised to S2-2105173. György (Ericsson) proposes to use 3842 instead, and consider this CR to be merged into that one.
Hui (Huawei) propose to not approve 502 CR before 501 issue is resolved.
Hui (Huawei) provides r01.
==== 8.X, 9.X Revisions Deadline ====
György (Ericsson) is fine with r01.
==== 8.X, 9.X Final Deadline ====
Revised
8.18 S2-2105173 CR Approval 23.502 CR2658R4 (Rel-17, 'B'): UE providing PDU Session Pair ID based on URSP rules Huawei, HiSilicon, Qualcomm Rel-17 Revision of S2-2104500r01. Approved Agreed
8.18 S2-2104501 CR Approval 23.503 CR0595 (Rel-17, 'B'): UE providing PDU Session Pair ID based on URSP rules Huawei, HiSilicon, LG Electronics, Qualcomm Rel-17 r08 agreed. Revised to S2-2105174. Yang (OPPO) asks a question to Pair ID in URSP rule
Seokjung(LGE) replies.
Yang (OPPO) replies.
György (Ericsson) provides r01.
Yang (OPPO) provides r02.
György (Ericsson) objects to r00, r02.
Mike (Convida Wireless) provides r03
György (Ericsson) objects to r03.
Mike (Convida Wireless) replies to György and provides r04
György (Ericsson) objects to r04
Mike (Convida Wireless) provides r05
György (Ericsson) provides r06
Mike (Convida Wireless) provides r07 which is the same as r06 except I removed section 3.1 from the cover page and the CR since it is not impacted.
Hui (Huawei) provides r07
Hui (Huawei) provides r08
György (Ericsson) objects to r08.
György (Ericsson) ok with r07 provided by Mike.
==== 8.X, 9.X Revisions Deadline ====
Seokjung(LGE) is OK with r07 proposed by Mike.
Hui(Huawei) can live with r00, r02-r05, r08. Objects to all other revisions.
TAO(VC) can we go with r05 then.
Hui(Huawei) proposes to go with r08.
György (Ericsson) can also go with r08 if we can get agreement on 4689 as well.
Devaki (Nokia) supports and proposes to go with r08 (as we are reaching consensus with r11 of 4689).
Seokjung(LGE) is also OK with r08
==== 8.X, 9.X Final Deadline ====
Revised
8.18 S2-2105174 CR Approval 23.503 CR0595R1 (Rel-17, 'B'): UE providing PDU Session Pair ID based on URSP rules Huawei, HiSilicon, LG Electronics, Qualcomm Rel-17 Revision of S2-2104501r08. Approved Agreed
8.18 S2-2104689 CR Approval 23.501 CR2736R3 (Rel-17, 'B'): Clarification on UE provides PDU Session Pair ID based on URSP rules Nokia, Nokia Shanghai Bell, Convida Wireless, Verizon, Qualcomm, [Ericsson], Huawei, Hisilicon, LG Electronics, ZTE Rel-17 Revision of (Endorsed) S2-2103047. r11 agreed. Revised to S2-2105175. György (Ericsson) responds to Huawei's example.
Hui (Huawei) replies to György (Ericsson).
György (Ericsson) responds to Huawei.
Hui (Huawei) replies.
György (Ericsson) replies to Huawei.
Mike (Convida Wireless) comments.
Devaki (Nokia) shares the same view as Mike (Convida Wireless).
György (Ericsson) responds to Convida Wireless.
György (Ericsson) does not understand the comments from Nokia.
Saso (Intel) comments that URSP is not needed 'to hide 3GPP details to applications' given that the main 'application' that makes use of the redundant PDU Sessions is IEEE FRER.
Devaki (Nokia) replies to Ericsson, cannot help if the comment is misunderstood or disregarded.
György (Ericsson) replies to Nokia that the question about inconsistent parameter handling is relevant.
György (Ericsson) replies to Nokia.
Mike (Convida Wireless) provides r01 and comments
Hui (Huawei) provides r02
György (Ericsson) responds to Huawei and Convida Wireless
Devaki (Nokia) comments that Ericsson shows no willingness to compromise despite SoH outcome with majority supporting URSP.
György (Ericsson) responds to Devaki and points out that progress requires a technical understanding of the solutions that are proposed.
Hui (Huawei) replies to György.
Mike (Convida Wireless) replies to György
György (Ericsson) replies to Mike.
Mike (Convida Wireless) replies to György.
Juan Zhang (Qualcomm) comments and provides r03.
György (Ericsson) responds to Juan.
Devaki (Nokia) comments.
György (Ericsson) responds to Nokia.
Antoine (Orange) asks how the two copies of duplicated traffic can be matched by different URSP rules.
Hui (Huawei) responds to Antoine.
Hui (Huawei) responds to György.
Yang (OPPO) supports to incorporate both RSN and pair ID
György (Ericsson) provides r04.
Yang (OPPO) comments and provides r05
György (Ericsson) responds to Oppo, objects to r00-r03, r05
Mike (Convida Wireless) provides r06
Juan Zhang (Qualcomm) supports r06 as a good compromise.
György (Ericsson) objects to r06.
Mike (Convida Wireless) replies that he provided an r04 of S2-2104501 to address György comment on r06 of this paper and would like to see if the combination of S2-2104501r04 and S2-2104689r06 are acceptable
Yang (OPPO) is supportive to r06
György (Ericsson) responds to Mike
György (Ericsson) replies and provides r07
Yang (OPPO) responds to György and provides r07
Hui (Huawei) provides r08
György (Ericsson) responds to Yang, objects to r07
Devaki (Nokia) provides r09
==== 8.X, 9.X Revisions Deadline ====
György (Ericsson) objects to r08.
György (Ericsson) objects to r09 unless the term FRER is replaced with a general wording in normative text.
Devaki (Nokia) proposes that we discuss this paper during CC#4 to get operator perspective.
Devaki (Nokia) ok with any version in the interest of progress.
Hui(Huawei) can live with r00-r03, r05, r06, r08. objects to all other revisions.
Hui (Huawei) responds.
Yang (OPPO) comments and share the concern from Huawei
György (Ericsson) responds to Yang.
Devaki (Nokia) provides r10 to resolve the concerns raised by Gyorgy, Hui et al.
György (Ericsson) provides r11 with small rewording.
Hui (Huawei) fine with r10 or r11.
Devaki (Nokia) is also fine with r10 or r11. Let us go with r11 if it is preferred.
Seokjung(LGE) is OK with r10 or r11
Yang (OPPO) can live with r11
==== 8.X, 9.X Final Deadline ====
Revised
8.18 S2-2105175 CR Approval 23.501 CR2736R4 (Rel-17, 'B'): Clarification on UE provides PDU Session Pair ID based on URSP rules Nokia, Nokia Shanghai Bell, Convida Wireless, Verizon, Qualcomm, [Ericsson], Huawei, Hisilicon, LG Electronics, ZTE Rel-17 Revision of S2-2104689r11. Approved Agreed
9 - - - Project Planning and Management - - Docs:=0 -
9.1 - - - New and Revised Work Items, TS/TR Cover sheets, Exception Sheets - - Docs:=0 -
9.1.1 - - - Rel-17 new and revised work Items - - Docs:=3 -
9.1.1 S2-2103889 WID REVISED Approval Revised WID on Dynamic management of group-based event monitoring. Ericsson Rel-17 r01 agreed. Revised to S2-2105128. Hannu (Nokia) proposes r01 to mark 'no other impacts' in clause 1.
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson) supports r01.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.1 S2-2105128 WID REVISED Approval Revised WID on Dynamic management of group-based event monitoring. Ericsson Rel-17 Revision of S2-2103889r01. Approved Approved
9.1.1 S2-2104324 WID NEW Approval New WID: 5G System Enhancements for Reduced Capability NR Devices. China Mobile Rel-17 Regarding the WID scope:
Stable objectives
Support Extended DRX for RRC Inactive and Idle with eDRX cycles up to 10.24 s, without using PTW and PH
Specify extended DRX up to 10485.76 s for RRC_IDLE.
Support RedCap UE type identification and other adaptation.
Controversial aspect
Specify to support Extended DRX >10.24 s for RRC_INACTIVE
Question: Should R17 WID include the study of Extended DRX >10.24 s for RRC_INACTIVE?
Yes (S2-2104324r05)
No (S2-2104324r04)
The SA WG2 Chair clarified that there should be no study Phase in a WID. Ericsson commented that there have been many WID produced without having a preliminary Study.
Support for S2-2104324r05: 6
Support for S2-2104324r04: 18
r04 had more support and objections to this were polled:
Object to S2-2104324r04: 2
S2-2104324 was then noted">CC#4: This was left for CC#5. CC#5: Noted
Haris(Qualcomm) comments and provides r01
Wanqiang(Huawei) support the idea to create a new WI to manage our SA2 normative work as alignment and ok with r01.
Sherry (Xiaomi) supports the WID for RAN alignment without 'extending eDRX cycles to beyond 10.24s for CM-Connected with RRC inactive'.
Tricci (OPPO) thanks Sherry (Xiaomi) for the suggestion to have a separate Rel17 WID to support RAN alignment for 'extending eDRX cycles to beyond 10.24s for CM-Connected with RRC inactive'.
Paul (Ericsson) provides comments and objects to r01 and separation of the eDRX >10.24 for RRC Inactive from the WID objectives.
Aihua (China Mobile) comments and provides r02.
Tricci (OPPO) supports Aihua (China Mobile) latest revision r02.
Sherry (Xiaomi) supports the WID, but whether it is appropriate to include the study on the support of Extended DRX >10.24 s for RRC_INACTIVE in the WID is to be further discussed.
Hannu (Nokia) supports the proposal from Haris (Qualcomm) to split the alignment of NR with the already existing 5G CIoT work from the study of extending RRC Inactive eDRX cycle beyond 10.24 seconds. Supporting r01 which is the best revision
Haris(Qualcomm) objects to r02
Guillaume (MediaTek) comments.
Sherry (Xiaomi) asks if we can include a small TR phase within the R17 WID.
Haris(Qualcomm) comments that there is guidance from SA#66 to not do feature WI with study phase that require TR
Aihua (China Mobile) provides r03 and r04.
==== 8.X, 9.X Revisions Deadline ====
Chris (Vodafone) is not sure of the WID process for inter-TSG alignment, but r04 (no long eDRX for Inactive) looks feasible for R17.
Paul (Ericsson) provides comments and r05. We can live with the original revision but object to all other revisions.
==== 8.X, 9.X Final Deadline ====
Hannu (Nokia) replies to Sherry (Xiaomi) and supports r04. Objects to r05.
Sherry (Xiaomi) replies to Hannu and comments.
Noted
9.1.2 - - - TS/TR Cover sheets - - Docs:=9 -
9.1.2 S2-2104304 TS OR TR COVER Approval Cover page of TS 23.247 to TSG Huawei (rapporteur) Rel-17 CC#5: r01 + changes agreed. Revised to S2-2105206.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2105206 TS OR TR COVER Approval Cover page of TS 23.247 SA for information Huawei (rapporteur) Rel-17 Revision of S2-2104304r01 + changes. Approved Approved
9.1.2 S2-2104489 TS OR TR COVER Approval Cover sheet for TS 23.304 (to TSG SA for information) OPPO Rel-17 CC#5: r03 agreed. Revised to S2-2105189
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2105189 TS OR TR COVER Approval Cover sheet for TS 23.304 (to TSG SA for information) OPPO Rel-17 Revision of S2-2104489r03. Approved Approved
9.1.2 S2-2104515 TS OR TR COVER Approval TS coverpage of 23.548 for approval Huawei Rel-17 CC#4: Revised to send for information to TSG SA in S2-2105187
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2105187 TS OR TR COVER Approval TS coverpage of 23.548 for information Huawei Rel-17 Revision of S2-2104515. CC#5: Approved Approved
9.1.2 S2-2105188 TS OR TR COVER Approval Draft TS 23.256 cover sheet to send to TSG SA for approval Qualcomm Rel-17 CC#5: Approved Approved
9.1.2 S2-2104679 TS OR TR COVER Approval Presentation of TR 23.761 for approval to TSG Intel Rel-17 CC#5: r01 agreed. Revised to S2-2105207.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.2 S2-2105207 TS OR TR COVER Approval Presentation of TR 23.761 for approval to TSG Intel Rel-17 Revision of S2-2104679r01. Approved Approved
9.1.3 - - - Exception Sheets for Rel-17 work items - - Docs:=13 -
9.1.3 S2-2103934 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for eV2XARC_Ph2 LG Electronics Rel-17 CC#5: This was approved.
==== 8.X, 9.X Final Deadline ====
Approved
9.1.3 S2-2104303 WI EXCEPTION REQUEST Approval 5MBS WI Exception Huawei (rapporteur) Rel-17 CC#5: r02 agreed. Revised to S2-2105204.
==== 8.X, 9.X Final Deadline ====
Revised
9.1.3 S2-2105204 WI EXCEPTION REQUEST Approval 5MBS WI Exception Huawei (rapporteur) Rel-17 Revision of S2-2104303r02. Approved Approved
9.1.3 S2-2105098 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for eNPN Ericsson (eNPN rapporteur) Rel-17 CC#5: Approved Dieter (Deutsche Telekom) comments and proposes changes.
Haris(Qualcomm) supports the comments from Dieter
Approved
9.1.3 S2-2105178 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for MUSIM intel (MUSIM rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105179 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for IIoT Nokia (IIoT rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105180 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for eEDGE_5GC Huawei (eEDGE_5GC rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105181 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for eNS_Ph2 ZTE (eNS_Ph2 rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105182 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for 5G_ProSe CATT (5G_ProSe rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105183 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for 5G_eLCS_ph2 CATT (5G_eLCS_ph2 rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105184 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for eNA_Ph2 Vivo (eNA_Ph2 rapporteur) Rel-17 CC#5: Approved Approved
9.1.3 S2-2105185 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for 5GSAT_ARCH Thales (5GSAT_ARCH rapporteur) Rel-17 CC#5: Approved Hannu (Nokia) provides r01 to clarify the impact area of the identified open item.
Jean Yves (Thales) comments.
Approved
9.1.3 S2-2105186 WI EXCEPTION REQUEST Approval Rel-17 Work Item Exception for ID_UAS Qualcomm (ID_UAS rapporteur) Rel-17 CC#5: Approved Approved
9.1.4 - - - Rel-18 new Study Items/Work Items proposal - - Docs:=68 -
9.1.4 S2-2104475 SID NEW Information New SID: Feasibility on Network Slicing Phase 3. ZTE Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103751 SID NEW Information New SID on enhancement for ProSe in 5G. OPPO Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103752 DISCUSSION Information Motivations for eProSe R18 OPPO Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103758 SID NEW Information New SID on 5GS Assisted AI/ML Services and Transmissions. OPPO Rel-18 Noted Changhong (Intel) comments.
Tricci (OPPO) provides r01 with additional supporting companies - Matrixx as well as some changes proposed by Matrixx to the SID.
Guillaume (MediaTek) provides comments.
David (Samsung) provides comments.
==== 8.X, 9.X Revisions Deadline ====
Guillaume (MediaTek) thanks Guillaume (MediaTek) and David (Samsung) for your comments and would like to suggest to use this email thread to consolidate the objectives and requirements for Rel18 SA2 5G-AIML study.
Tricci (OPPO) thanks Guillaume (MediaTek) and David (Samsung) for your comments and would like to suggest to use this email thread to consolidate the objectives and requirements for Rel18 SA2 5G-AIML study.
==== 8.X, 9.X Final Deadline ====
Aihua (China Mobile) provides comments.
Tricci (OPPO) thanks Aihua (China Mobile) comments and afraid that CMCC has incorrect understanding towards the objectives in OPPO's SID.
Noted
9.1.4 S2-2103759 DISCUSSION Information Discussion on 5GS support for vertical layer AIML analytics for R18 OPPO Rel-18 Noted Tricci (OPPO) provides r01 with additional background info update to the presentation.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103785 SID NEW Information New SID on Study of Further Architecture Enhancement for UAV and UAM. Qualcomm Incorporated Rel-18 Noted Runze (Huawei) comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103832 DISCUSSION Discussion Discussion on Support of Satellite Backhaul in 5GS CATT Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103833 SID NEW Information New SID on Study on Support of Satellite Backhauling in 5GS. CATT, Thales Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103834 SID NEW Information New SID on Enhancement to the 5GC LoCation Services Phase 3. CATT, Huawei Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103835 DISCUSSION Information DP of the New SID on Enhancement to the 5GC LoCation Services Phase 3 CATT,Huawei Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103904 DISCUSSION Agreement Use of L4S in 5GS Ericsson, Deutsche Telekom, AT&T, Verizon, Apple, T-Mobile USA Inc. Rel-18 Noted Laurent (Nokia): objects to this Tdoc as no R18 WID was to be submitted for Approval at this meeting
Assumes this is a TEI-18 proposal for information/discussion; that can be discussed during this meeting.
Above comment is from Antoine (Orange).
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103936 DISCUSSION Discussion Discussion on PCF providing RFSP Index to MME/RAN . China Telecom Rel-18 Revision of (Unhandled) S2-2102535. Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103939 DISCUSSION Discussion DP on New SID on QoS Enhancements on High Data Rate and Low Latency Services Tencent Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103940 SID NEW Information New SID on QoS Enhancements on High Data Rate and Low Latency Services . Tencent Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103941 SID NEW Information New SID on Study on Tracking Internet of Things (TIoT) in the 5G System (5GS). Spreadtrum Communications Rel-18 Noted Hualin(Huawei) provide r01 in the draft folder.
Chunhui(Spreadtrum) responses to the comments from Huawei.
Guillaume (MediaTek) asks for clarification.
==== 8.X, 9.X Revisions Deadline ====
Chunhui (Spreadtrum) replies the comments from MediaTek.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103968 WID NEW Information New WID: Extensions to the TSC Framework to support DetNet (DetNet) Ericsson Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103995 WID NEW Information New Study on enhancement of support for 5WWC in 5GC. Nokia Noted Hualin(Huawei) provide comments on the proposal.
Gerald (Matrixx) with comment.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2103996 WID NEW Information New Study on enhancement of support for Edge Computing in 5GC. Nokia, Nokia Shanghai Bell Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104029 SID NEW Information New SID: Study on System improvement for Enhanced Access to and Support of Network Slice. LG Electronics, KT Corp., LG Uplus, SK Telecom Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104030 DISCUSSION Discussion Discussion on Study on System improvement for Enhanced Access to and Support of Network Slice LG Electronics Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104037 SID NEW Information New SID: Study on enhancement of 5G UE Policy. Intel, Qualcomm Incorporated Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104124 DISCUSSION Information Study on 5G Timing Resiliency and TSC enhancements for IP and ETH applications Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104125 SID NEW Information New SID: Study on 5G Timing Resiliency and TSC enhancements. Nokia, Nokia Shanghai Bell, Verizon, AT&T Rel-18 Noted Tobias (Siemens AG) supports the SID and co-signs.
Devaki (Nokia) provides r01 with additional supporting companies - Siemens, Sennheiser.
Tricci (OPPO) would like to verify for AI#9.1.4 agenda which is for information ONLY according to SA2 chair's instructions
Devaki (Nokia) comments that it is for information only, revisions are not prohibited (hopefully clear to you by now).
Gerald (Matrixx) with support of the SID.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104126 DISCUSSION Information Dual Registration between two networks. Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104144 DISCUSSION Discussion Discussion on enhancement for URLLC and deterministic network. Huawei, HiSilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104178 SID NEW Information New SID on Study on Proximity based Services in 5GS - Phase 2. CATT Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104226 SID NEW Information New Study on Service-based N2. Intel, Cisco, Verizon UK Ltd, Qualcomm Incorporated, AT&T Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104231 SID NEW Information Study on Enablers for Network Automation for 5G - phase 3. China Mobile, vivo Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104297 SID NEW Information New SID on 5G System Support for Future Factory . Samsung, LG Uplus,SK Telecom Rel-18 Noted Marco (Huawei) provide comments regarding a too broad scope of the SID.
Sang-Jun (Samsung) provides r01 with additional supporting companies - Sennheiser, KT Corp.
Sang-Jun (Samsung) responds to Marco (Huawei) that a holistic view is needed to support future factory.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104312 SID NEW Information New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2. Huawei Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104337 SID NEW Information New SID: Study on enhanced support of Non-Public Networks phase 2. Ericsson, Futurewei, Convida Wireless, Charter, China Unicom, ETRI; Cisco, China Mobile, Lenovo, Motorola Mobility, Qualcomm, ZTE Rel-18 Noted Hualin(Huawei) provides comments on the paper.
DongYeon (Samsung) comments and asks questions.
DongYeon (Samsung) withdraw her previous comment, it was for the other paper.
Peter Hedman (Ericsson) provides reply to Huawei
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104357 SID NEW Information New SID: Study on UPF enhancement for control and SBA . China Mobile, AT&T, Vodafone, CATT, Tencent, Deutsche Telekom, SK Telecom, Sandvine Rel-18 Noted Gerald (Matrixx) supports the SID and with comment.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104371 SID NEW Information New SID: Study on architecture enhancement support for coordinated communication of multiple UEs . Xiaomi, Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104405 DISCUSSION Information Study on the impact on SM and upper layers due to MM events. Samsung Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104415 SID NEW Information New SID on Smarter use of Network Slices. Samsung, SK Telecom, KT Corp. Verizon UK Ltd, NEC, ETRI Rel-18 Noted Srisakul (NTT DOCOMO) provides comments and supports the proposed SID.
Tricci (OPPO) responds to Srisakul (DoCoMo) comments on this agenda for new SID/WID for information only and not for any revision.
Srisakul (DoCoMo) agrees with Tricci (OPPO) and Hoyeon (Samsung).
Tricci (OPPO) apologizes to Srisakul (DoCoMo) that, I have missed the latest version of the SA2's chair agenda. Apparently, the rules has been updated for agenda 9.1.4.
Hoyeon (Samsung) provides r01 with additional supporting company - NTT DOCOMO, and address a comment from Srisakul.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104425 DISCUSSION Discussion Analytics based on more precise UE location information NTT DOCOMO Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104448 SID NEW Information New SID: Study on enhancement of 5G AM Policy. China Telecom Rel-18 Noted Belen (Ericsson) provides comments.
Dan (China Mobile) provides response to Belen
==== 8.X, 9.X Revisions Deadline ====
Zhuoyi (China Telecom) provides response to Belen.
Belen (Ericsson) replies to China Telecom
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104462 DISCUSSION Agreement Discussion on enhancement for 5G LAN-type service. Huawei, HiSilicon Rel-18 Noted Laurent (Nokia): objects to this Tdoc as no WID was to be submitted for Approval at this meeting
Jeffrey (Juniper) provides comments and r1
Tricci (OPPO) would like to verify for AI#9.1.4 agenda which is for information ONLY according to SA2 chair's instructions
Tricci (OPPO) apologizes for not reading the official version of the meeting agenda from SA2 chair and missed the revision rules for AI#9.1.4.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104497 SID NEW Information New SID on network enhancements for 5G broadband media services . Huawei, Hisilicon, vivo, CATT, Toyota, China Mobile Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104498 SID NEW Information New SID on Enhancement of support for Edge Computing in 5G Core network - phase 2. Huawei, HiSilicon Rel-18 Noted Jeffrey (Juniper) suggests one additional issue to study in r1
Hui (Huawei) provides comments on Jeffery.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104520 DISCUSSION Discussion Discussion on new SID proposal on Network Enhancements for 5G Broadband Media Services Huawei, HiSilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104544 DISCUSSION Discussion Discussion on 5WWC phase2. Huawei Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104545 DISCUSSION Discussion Discussion on NPN study for Release 18 . Huawei, Hisilicon Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104553 SID NEW Information New SID on 5G System Evolution for AI/ML-based Services. Samsung Rel-18 Noted Xiaobo Yu (Alibaba) asks for clarifications.
==== 8.X, 9.X Final Deadline ====
David (Samsung) replies to Alibaba.
Noted
9.1.4 S2-2104569 DISCUSSION Discussion Discussion on new SID on 5G System Evolution for AI/ML-based Services Samsung Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104582 DISCUSSION Discussion Discussion on ATSSS Enhancements Lenovo, Motorola Mobility Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104597 DISCUSSION Decision Discussion about eNA work in R18 vivo, China Mobile Rel-18 Noted Laurent (Nokia): objects to this Tdoc as no WID was to be submitted for Approval at this meeting
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104599 SID NEW Information New SID: Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. Lenovo, Motorola Mobility Noted DongYeon (Samsung) comments and asks questions.
Apostolis (Lenovo) responds to DongYeon (Samsung).
Susan (Huawei) provides some questions and comments.
Apostolis (Lenovo) responds to Susan (Huawei).
DongYeon (Samsung) comments.
==== 8.X, 9.X Revisions Deadline ====
Spencer (Tencent) responds to Apostolis and DongYeon
Spencer (Tencent) requests to confirm that Tencent is a supporting company for this SID, and suggests another topic for discussion after SA2#145-e.
Apostolis (Lenovo) responds to Spencer (Tencent).
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104619 WID NEW Information Discussion on supporting authentication and authorization for each application in the same network slice. China Telecom Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104621 WID NEW Information New WID on Supporting Authentication and Authorization of Network Slice per Application. China Telecom Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104623 SID NEW Information New SID: Study on architecture enhancement for tactile and multi-modality communication services . China Mobile, Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104650 DISCUSSION Discussion Initial views on Rel-18 (SA2) MediaTek Inc. Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104656 DISCUSSION Information Some Network slicing topics proposals for rel-18. Nokia, Nokia Shanghai Bell Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104657 SID NEW Information New SID: Study on System Enabler for Service Function Chaining. Intel, Telecom Italia, Spreadtrum, Sandvine, Convida Wireless, KPN, InterDigital, Microsoft, Matrixx, KDDI, AT&T Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104660 SID NEW Information Discussion on new SID - System Enabler for Service Function Chaining Intel Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104661 DISCUSSION Information New SID on further enhancements for XR services Qualcomm Incorporated Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104662 SID NEW Information New SID on further enhancements for XR services. Qualcomm Incorporated Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104671 DISCUSSION Information Study on Integration of satellite components in the 5G architecture Phase II Xiaomi Rel-18 Noted Sherry (Xiaomi) provides r01 with the similar change in S2-2104672r01.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104672 SID NEW Information New SID on Study on Integration of satellite components in the 5G architecture Phase II. Xiaomi Rel-18 Noted DongYeon (Samsung) asks questions.
Hannu (Nokia) asks about the foreseen MIoT requirements?
Sherry (Xiaomi) replies to DongYeon.
Jean Yves (Thales) comments about Rel18 SIDs in that meeting
Jean Yves (Thales) completes after asking to Mr Chairman in CC#2
Sherry (Xiaomi) replies to Hannu.
Sherry (Xiaomi) provides r01 to add a new objective and the supporting company and update to the existing objectives.
Guillaume (MediaTek) provides comments.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Sherry (Xiaomi) replies to Guillaume.
Noted
9.1.4 S2-2104673 DISCUSSION Information Study on Architecture Enhancement to support Ranging-based services and relative positioning Xiaomi Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104674 SID NEW Information New SID on Study on Ranging based services and relative positioning. Xiaomi Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104685 SID NEW Information New SID Study on enhancement to the integration of satellite systems in the 5G architecture. . THALES Rel-18 Noted Jean Yves (Thales) provides r01 to include Rakuten Mobile proposed use case on SAT RAT fallback for study
Hannu (Nokia) proposes that we should not commit to any Rel-18 work in this meeting yet. Collecting comments on draft documents that are intended to be re-submitted later on is fine.
Jean Yves (Thales) responds to Hannu: yes, my understanding is that Rel18 SIDs for SA2#e145 are proposed for information and need to be re-submitted in next meeting(s)
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104687 SID NEW Information New SID on Centralised Network Automation. Lenovo, Motorola Mobility Rel-18 Noted Zhuoyi (China Telecom): ask for clarification.
Belen (Ericsson) also ask about the problem to solve and simialr comments as China Telecom
==== 8.X, 9.X Revisions Deadline ====
Dimitris (Lenovo) provides responses
Belen (Ericsson) replies to Lenovo
==== 8.X, 9.X Final Deadline ====
Dimitris (Lenovo) replies
Xiaobo(vivo) provides late comments.
Noted
9.1.4 S2-2104688 DISCUSSION Information Motivation for SID on Centralised Network Automation Lenovo, Motorola Mobility Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104715 SID NEW Information New SID on Network of Networks architecture. Vivo Mobile Communications Ltd, China Telecom, Convida Wireless, Oppo, InterDigital, Tencent, T-Mobile USA, Xiaomi Rel-18 Noted Marco (Huawei) comments and asks clarifications.
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104725 DISCUSSION Discussion Motivation for New SID on Network of Networks architecture vivo Communication Technology Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104761 SID NEW Information New SID on Study of Architecture Enhancement for Vehicle Mounted Relays. Qualcomm Incorporated Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.1.4 S2-2104762 DISCUSSION Information Motivation for Study of Architecture Enhancements for Vehicle Mounted Relays (FS_VMR_ARC) Qualcomm Incorporated Rel-18 Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 - - - Review of the Work Plan, Rel-17 WID Status Reports - - Docs:=19 -
9.2 S2-2103935 WI STATUS REPORT Information EV2XARC_Ph2 status report LG Electronics Rel-17 Revised to S2-2105190.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2105190 WI STATUS REPORT Information EV2XARC_Ph2 status report LG Electronics Rel-17 Revision of S2-2103935. CC#5: Noted Noted
9.2 S2-2103960 WI STATUS REPORT Information ENA_Ph2 Status Report vivo CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104109 WI STATUS REPORT Information 5G_ProSe Status Report CATT (Rapporteur) Rel-17 Revised to S2-2105215.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2105215 WI STATUS REPORT Information 5G_ProSe Status Report CATT (Rapporteur) Rel-17 Revision of S2-2104109. CC#5: Noted Noted
9.2 S2-2104127 WI STATUS REPORT Information IIoT status report Nokia, Nokia Shanghai Bell Rel-17 CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104295 WI STATUS REPORT Information SA WG2 Status report for LCS_Ph2 CATT Rel-17 CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104302 WI STATUS REPORT Information 5MBS Status Report Huawei (rapporteur) Rel-17 Revised to S2-2105214.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2105214 WI STATUS REPORT Information 5MBS Status Report Huawei (rapporteur) Rel-17 Revision of S2-2104302. CC#5: Noted Noted
9.2 S2-2104342 WI STATUS REPORT Information ENPN Status Report Ericsson (rapporteur) Rel-17 CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104516 WI STATUS REPORT Information Status report for eEdge_5GC Huawei Rel-17 Revised to S2-2105217.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2105217 WI STATUS REPORT Information Status report for eEdge_5GC Huawei Rel-17 Revision of S2-2104516. CC#5: Noted Noted
9.2 S2-2104566 WI STATUS REPORT Information ATSSS_Ph2 Status Report Lenovo, Motorola Mobility Rel-17 Revised to S2-2105216.
==== 8.X, 9.X Final Deadline ====
Revised
9.2 S2-2105216 WI STATUS REPORT Information ATSSS_Ph2 Status Report Lenovo, Motorola Mobility Rel-17 Revision of S2-2104566. CC#5: Noted Noted
9.2 S2-2104220 WI STATUS REPORT Information SA WG2 Status report for MUSIM Intel CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104789 WI STATUS REPORT Information eNS_Ph2 Status Report ZTE (Rapporteur) CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2104790 WI STATUS REPORT Information ID_UAS Status Report Qualcomm (Rapporteur) CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2105094 WI STATUS REPORT Information MPS2 Status Report Perspecta Labs (Rapporteur) CC#5: Noted
==== 8.X, 9.X Final Deadline ====
Noted
9.2 S2-2105097 WI STATUS REPORT Information 5G_AIS Status Report Tencent (Rapporteur) Rel-17 CC#5: Noted Noted
9.3 - - - Planning future meetings - - Docs:=2 -
9.3 S2-2103839 WORK PLAN Information Work_plan_3gpp_210409_Filtered_SA WG2 MCC CC#4: This was provided for information and was noted.
==== 8.X, 9.X Final Deadline ====
Noted
9.3 S2-2104765 WORK PLAN Endorsement SA2 work planning for Q3/Q4, 2021 SA WG2 Chair CC#5: This was endorsed.
==== 8.X, 9.X Final Deadline ====
Endorsed
9.4 - - - Holder for left-overs from Deadline 1 - - Docs:=14 -
9.4 S2-2103722 LS In Action LS from CT WG3: LS on Session Management Policy Data per PLMN CT WG3 (C3-211469) Revision of Postponed S2-2102103 from S2#144E. Responses drafted in S2-2104002 and S2-2104140. CC#2: Moved to agenda item 9.4. Postponed Postponed
9.4 S2-2104002 LS OUT Approval [DRAFT] LS on Session Management Policy Data per PLMN Nokia, Nokia Shanghai Bell Rel-17 Response to S2-2103722. CC#2: Moved to 9.4. Postponed Haiyang (Huawei) provides r01.
Laurent (Nokia): answers and is asking this topic to be discussed as part of SA2 CC2
Stefano (Qualcomm): supports Nokia comments and indicates that r01 is not acceptable. R00 is fine
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Haiyang (Huawei) provides comments and is not ok with the original version.
Haiyang (Huawei) provides update slides for CC#2.
Laurent (Nokia): provides r03 of the slides
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Laurent (Nokia): provides r02 of 4006 to align with the proposal in the slides
==== 8.X, 9.X Revisions Deadline ====
Haiyang (Huawei) indicates there are only r00 and r01 of the LS OUT, suggests to postpone
Laurent (Nokia): objects to R01
Belen (Ericsson) supports to potspone this LS. No r03 either.
==== 8.X, 9.X Final Deadline ====
Postponed
9.4 S2-2104006 CR Approval 23.503 CR0578 (Rel-17, 'F'): Session Management Policy Data per PLMN for LBO case Nokia, Nokia Shanghai Bell Rel-17 CC#2: Moved to 9.4. Noted Laurent (Nokia): Provides r01
Belen (Ericsson) send comments and objects to this contribution
Haiyang(Huawei) agrees with Belen (Ericsson)
Laurent (Nokia): answers and is asking this topic to be discussed as part of SA2 CC2
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Dieter (Deutsche Telekom): comments.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Laurent (Nokia): provides r02 of 4006 (post deadline) to align with the proposal in the slides
Laurent (Nokia): provides r03
Belen (Ericsson) provides r04, objects to initial versios, r01, r02 and r03
Biao (China Telecom) supports r04.
==== 8.X, 9.X Revisions Deadline ====
Laurent (Nokia): objects to R04
==== 8.X, 9.X Final Deadline ====
Noted
9.4 S2-2104224 CR Approval 23.502 CR2790 (Rel-17, 'F'): Session Management Policy Data per PLMN for LBO case Nokia, Nokia Shanghai Bell Rel-17 CC#2: Moved to 9.4. Noted Belen (Ericsson) send comments and objects to this contribution
Haiyang(Huawei) agrees with Belen (Ericsson)
Laurent (Nokia): answers and is asking this topic to be discussed as part of SA2 CC2
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.4 S2-2104141 CR Approval 23.502 CR2777 (Rel-17, 'F'): Clarification on Session Management Policy Data per PLMN Huawei, HiSilicon Rel-17 CC#2: Moved to 9.4. Noted Laurent (Nokia): does not support the approach in S2-2104141 and comments why
Belen (Ericsson) supports this contribution.
Haiyang (Huawei) replies to Laurent (Nokia).
Laurent (Nokia): answers and is asking this topic to be discussed as part of SA2 CC2
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Dieter (Deutsche Telekom): asks questions for clarification.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Laurent (Nokia): answers and objects to 4141
Haiyang (Huawei) asks questions to Laurent (Nokia).
Biao (China Telecom): comments and supports this paper.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Noted
9.4 S2-2103799 CR Approval 23.501 CR2858 (Rel-17, 'F'): Consistent handling of NF documentation Ericsson Rel-17 CC#2: Moved to AI 9.4. r06 agreed. Revised to S2-2105129, merging S2-2104766. Gerald (Matrixx) with comments on charging
Magnus (Ericsson) responds to Gerald
Gerald (Matrixx) with progress in r01 to merge topic of S2-2104766
Magnus (Ericsson) provides r02
Gerald (Matrixx) provides r03 as suggested with question
Magnus (Ericsson) provides r04
Gerald (Matrixx) with comment to r04 to remove charging function reference in 6.1.
Magnus (Ericsson) provides r05
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Gerald (Matrixx) supports r05.
Devaki (Nokia) objects to the CR and the revisions or requests that the CR is postponed, CR is not fixing any flaw as such, but lowering scope of section 4 of 501.
Gerald (Matrixx) with request to Nokia to point out which part needs to be removed from this CR
Devaki (Nokia) replies to Gerald.
Magnus (Ericsson) responds to Nokia and asks for this doc to be brought up on CC#2.
Magnus (Ericsson) replies further.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Devaki (Nokia) comments.
Magnus (Ericsson) comments.
Magnus (Ericsson) provides r06.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2105129 CR Approval 23.501 CR2858R1 (Rel-17, 'F'): Consistent handling of NF documentation Ericsson Rel-17 Revision of S2-2103799r06, merging S2-2104766. Approved Agreed
9.4 S2-2104681 CR Approval 23.501 CR2970 (Rel-17, 'B'): 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage Vodafone, Qualcomm Rel-17 CC#2: Moved to 9.4. CC#4: r37 + changes agreed. Revised to S2-2105154. Qian Chen (Ericsson) provides comments and proposes to start a Rel+18 SID on this 2G/3G mobility via 4G scenario
Ouyang(Huawei) comments
Chris (Vodafone) responds that this is an Rel 15 correction and doing a SID in Rel 18 is completely inappropriate. Given that S10 works, what else besides TI needs to be transferred on N26?
Ouyang(Huawei) replies to Chris (Vodafone)
Qian Chen (Ericsson) responses to Chris (Vodafone)
Chris (Vodafone) provides technical answers to questions from Ericsson and Huawei
Haris(Qualcomm) supports the CR
Qian Chen (Ericsson) provides further responses to Chris (Vodafone)
Qian (Ericsson) provides comments.
Chris (Vodafone) provides r01.
Ouyang(Huawei) provide r02
Qian Chen (Ericsson) responds to Chris (Vodafone)
Chris (Vodafone) responds to Ericsson that this is an R15 error that needs correcting, not something for R18 study!
Chris (Vodafone) provides r03 based on r02 but does not necessarily support it
Guillaume (MediaTek) expresses concerns with original/r01.
Haris(Qualcomm) comments on r02/r03
Laurent (Nokia): provides r04
Ouyang(Huawei) suggests Laurent (Nokia) to work on top of r03.
Qian (Ericsson) comments and provides r05 based on r03
Laurent (Nokia): provides Ro6
Laurent (Nokia): provides R06 and comments
Laurent (Nokia): provides R07
zhendong (ZTE) provides r08.
zhendong (ZTE) provdies the response.
Laurent (Nokia): answers
Qian (Ericsson) responds to Zhendong (ZTE).
Chris (Vodafone) provides r09 based on r07
Haris(Qualcomm) provides r09
Haris(Qualcomm) proposes r10
Laurent (Nokia): Comments: can you please generate a new revision with aligned numbers
Chris (Vodafone) provides r11
zhendong (ZTE) provides r12.
Haris(Qualcomm) comments on r11
Qian (Ericsson) comments and provides r13 on top of r12.
Fenqin (Huawei) comments and provides r14.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Chris (Vodafone) replies to Qualcomm, Ericsson and Huawei.
Qian (Ericsson) response to Chris (Vodafone).
Chris (Vodafone) replies that he believes Ericsson's response is incorrect.
Qian (Ericsson) replies and indicates that UE network capability is not the same as 5GS capability/N1 Mode support capability.
Chris(Vodafone) disagrees with (Ericsson). Let's try not modify Note 5 to another wrong wording! Please suggest simple updates to r12 for agreement prior to CC#2
Chris (Vodafone) replies to new response from Qualcomm.
The following change could be made to rev 12:
Upon mobility from GERAN/UTRAN to EPS, the UE may release the current PDN connection(s) for which it has not yet attempted to negotiate (successfully or unsuccessfully) a PDU Session ID with the EPC network and re-establish these PDN connection(s) as specified in clause 4.11.1.5.4.1 of TS 23.502 [3] so that they support interworking to 5GS
Chris(Vodafone) provides comments and proposal base on r13.
Chris (Vodafone) believes that R12 is the correct version to try and approve or suggest minor changes to
Chris(Vodafone) Qian (Ericsson) provides comments and proposal base on r13.
Qian (Ericsson): provides comments and ask questions
Chris (Vodafone) prefers R12 and suggests an alternative update of Note 5.
Qian (Ericsson) expresses views and also propose an alternative on top of r13 or r14. He also expresses other concerns.
Antoine (Orange) comments on Qian's alternative proposal for Note 5.
Qian (Ericsson) fixes an important typo in previous response.
Haris(Qualcomm) cannot accept the option of release and re-establishment of PDN connection, therefore objects to all options that contains this option as normative text
Laurent (Nokia): objects to R00, R01, R05,R06, R08, R09, R10, R13 and R14 and to the NOTE proposed by Qian in the mail below,. Laurent (Nokia): descending order of preference with R07 first then R12 ,R11, R03- R04;
Guillaume (MediaTek) objects to: original, r01, r03, r04, r06 to r14
Ouyang(Huawei) considers r12 can be selected as the baseline. Invite Guillaume (MediaTek) to take another look.
Guillaume (MediaTek) responds to Ouyang (Huawei)
Chris (Vodafone) replies to 'old' unanswered comment from Qian (Ericsson)
Chris (Vodafone) replies to Haris (Qualcomm) suggesting that this is documented as an optional UE behaviour.
Ouyang(Huawei) comments that the current text is optional for the UE.
Chris (Vodafone) provides R15 based on R12.
Antoine (Orange) comments.
Qian (Ericsson) give a technical comment on r15.
Chris (Vodafone) says he can update to align with Ericsson's technical comment on r15.
Chris (Vodafone) provides r16 to address Ericsson and Orange (but not Nokia comments)
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Qian (Ericsson) provides some comments
Guillaume (MediaTek) provides fixes to r18 post-deadline: r19.
Haris(Qualcomm) comments on r19 and proposes to postpone the discussion
Guillaume (MediaTek) responds.
Chris (Vodafone) provides r21 as basis for next updates
Qian (Ericsson) provides r22 with minor changes
Chris (Vodafone) is OK with R22 from Ericsson, and provides support to latest comment from Huawei.
Haris(Qualcomm) provides r23 to clarify the UE behaviour
Laurent (Nokia): provides r24
Qian (Ericsson)ask for clarifications for r24
Fenqin (Huawei) Provide comments
Qian (Ericsson) replies to Fenqin (Huawei)
Chris (Vodafone) provides r25
Guillaume (MediaTek) provides r26.
Chris (Vodafone) thinks that r26 is OK.
Laurent (Nokia): answers and provides r27
Qian (Ericsson) comments and provides r30 (Please ignore r28 and r29 which is uploaded wrongly)
Qian (Ericsson): provides comments and strong concerns on r31
Chris (Vodafone) queries whether Ericsson and Nokia are arguing over something that is not relevant.
Qian (Ericsson) replies to Chris (Vodafone) that both options proposed by Chris are ok.
Chris (Vodafone) provides R32.
Chris (Vodafone) provides R33 as clean CR equal to R32.
Qian (Ericsson) provides R34 and comments.
Fenqin (Huawei) ask question for clarification
Chris (Vodafone) provides r20 with changes highlighted from R12 as basis for CC#2
Qian (Ericsson): replies
Chris (Vodafone) proposes a short telco
Chris (Vodafone) provides R35 as a proposal for compromise.
Qian (Ericsson): provides r36
Chris (Vodafone) is Ok with r36.
Qian (Ericsson) comments.
Chris (Vodafone) provides clean CR in r37.
Laurent (Nokia): provides r38
Laurent (Nokia): provides r40
Chris (Vodafone): provides r39
==== 8.X, 9.X Revisions Deadline ====
Qian (Ericsson): considers r39 and r40 has logic issues and shall go with r37
Gerald (Matrixx) is supporting r37.
Chris (Vodafone) asks for this to be handled in CC#4. Rev 41 should be agreeable. Rev 41 is Rev 37 (sent before deadline) BUT with NOTE 2 in 5.17.2.4 modified as highlighted below:

NOTE 2: For the use of N7 or N40 interfaces while the UE is in GERAN/UTRAN access, the SMF+PGW-C selected by the MME (using the existing selection procedures described in clause 4.11.0a of TS 23.502 [3] and clause 4.3.8 of TS 23.401[26]) needs to support the functionality (e.g. signalling of GERAN/UTRAN cell identification over N7) specified in Annex X for 'Support of GERAN/UTRAN access' if interactions via N7 or N40 interfaces are needed for GERAN/UTRAN access.
Gerald (Matrixx) supports r41.
==== 8.X, 9.X Final Deadline ====
Chris (Vodafone) says that these report Macros do not handle formatted (strikethrough) text well. In Rev 41, the final text is:

NOTE 2: For the use of N7 or N40 interfaces while the UE is in GERAN/UTRAN access, the SMF+PGW-C selected by the MME (using the existing selection procedures described in clause 4.11.0a of TS 23.502 [3] and clause 4.3.8 of TS 23.401[26]) needs to support functionality (e.g. signalling of GERAN/UTRAN cell identification over N7) specified in Annex X for 'Support of GERAN/UTRAN access'.
Revised
9.4 S2-2105154 CR Approval 23.501 CR2970R1 (Rel-17, 'B'): 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage Vodafone, Qualcomm Rel-17 Revision of S2-2104681r37 + changes. CC#4: Approved Agreed
9.4 S2-2104684 CR Approval 23.502 CR2858 (Rel-17, 'B'): 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage Vodafone (Based on S2-2103059 from Nokia, Nokia Shanghai Bell, Ericsson) Rel-17 CC#2: Moved to 9.4. Postponed Fenqin (Huawei) proposes to postpone this issue to Rel-18.
Chris (Vodafone) disagrees with Huawei. R15 should support quality mobility between 4G and 5GC and it will not!
But let's focus the 'issue' discussion on the 4681 thread.
Laurent (Nokia): strongly suggest to postpone this TDOC
Laurent (Nokia): provides r01
Chris (Vodafone): provides r02
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Qian (Ericsson): provides r04, please ignore r03
Chris (Vodafone) says that the cover sheet changes in r04 seem OK.
Laurent (Nokia): objects to R00 and R03.
In R01-R02 and R04 the cover sheet is slightly wrong
Andy (VC, Samsung) suggests that if the only changes are to correct the coversheet an r05 could be uploaded and we can very briefly open this in CC#2 .
Laurent (Nokia): provides r05 (in CC2 folder) post deadline that just removes text within the cover sheet
Qian (Ericsson) comments that the fate of this CR seems linked to the fate of 04681.
Chris (Vodafone) accepts r05 is OK. Agrees linkage with 4681.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Qian (Ericsson) says this paper is not needed based on the possible outcome of 4681.
Fenqin (Huawei) comments.
laurent(Nokia) comments: one way forward is to skip the 502 CR at this meeting and check for potential 502 changes at next meeting
Chris (Vodafone) is OK to postpone to next meeting.
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Postponed
9.4 S2-2104628 CR Approval 23.501 CR2957 (Rel-16, 'F'): Adding protocol stacks for trusted WLAN access for N5CW device Huawei, Hisilicon Rel-16 CC#2: Moved to 9.4. r13 agreed. Revised to S2-2105130. Laurent (Nokia): asks a question (this CR shall not be automatically agreed as long as the question is not settled)
Stefan (Ericsson) provides additional questions
Marco (Huawei) answers the questions and provide r01
Stefan (Ericsson) provides r02
Marco (Huawei) provides r03
Marco (Huawei): answer to Laurent (Nokia)
Laurent (Nokia): provides r04
Laurent (Nokia) answer to Marco (Huawei)
Stefan (Ericsson) comments
Marco (Huawei) provide r06
Dieter (Deutsche Telekom): does not believe this CR is FASMO.
Laurent (Nokia): answers
Dieter (Deutsche Telekom): it is not FASMO, i.e. we are not ok with a rel16 CR.
Laurent (Nokia): provides r07
Laurent (Nokia): provides r08
Marco (Huawei): The misoperation is to start an ethernet PDU session in TWIF. The coversheet updated. Provided r07
Marco (Huawei): r08 is R17 version, so if approved as R17 , then a new the CR number shall be assigned and new Tdoc number generated and R16 CR shall be noted. I provide R09 on top of R08
Marco (Huawei): provides r10 as R16 version of r10
Dieter (Deutsche Telekom): comments that for Rel16 only first change may possibly be considered FASMO.
Marco (Huawei): provides r011 with Rel16 and only first change.
==== 4.X, 5.X, 6.X, 7.X Revisions Deadline ====
Laurent (Nokia): objects to any version within R00-R03; suggests R09 for 3GPP R17 and R11 for 3GPP R16; (so not mirrors)
Marco (Huawei): I'm OK. A new tdoc and CR number shall be assigned for R09 for 3GPP R17 . To be added in CC#2?
Dieter (Deutsche Telekom): is OK with r11 for Rel16 and could live with a Rel-17 CR based on r09.
==== 4.X, 5.X, 6.X, 7.X Final Deadline ====
Marco (Huawei): provide R012 as CR for R16. The title changed 'Limitation to PDU session type IP for N5CW'
Dario S. Tonesi (Qualcomm) provides r13
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2105130 CR Approval 23.501 CR2957R1 (Rel-16, 'F'): Adding protocol stacks for trusted WLAN access for N5CW device Huawei, Hisilicon Rel-16 Revision of S2-2104628r13. Approved Agreed
9.4 S2-2105005 CR Approval 23.501 CR2991 (Rel-17, 'F'): Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Created at CC#2: Mirror CR to S2-2104628. Cat F ? r01 agreed. Revised to S2-2105131. Marco (Huawei): provide the r00 based on the Friday call. This is R17 generated from 4628 discussion. This is based on R09 where the coversheet has been fixed. The title has been changed to 'Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device'
Dario S. Tonesi (Qualcomm) provides r01
==== 8.X, 9.X Revisions Deadline ====
==== 8.X, 9.X Final Deadline ====
Revised
9.4 S2-2105131 CR Approval 23.501 CR2991R1 (Rel-17, 'F'): Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2105005r01. Approved Agreed
11 - - - Close of e-meeting - - Docs:=0 -
99 - - - Withdrawn and Reserved documents - - Docs:=64 -
99 S2-2104557 CR Approval 23.167 CR0363 (Rel-17, 'A'): NG eCall domain selection corrections Qualcomm Rel-17 WITHDRAWN Withdrawn
99 S2-2104083 CR Approval 23.503 CR0581 (Rel-17, 'B'): Maximum data rate control per S-NSSAI with assistance from the NWDAF Huawei, HiSilicon Rel-17 WITHDRAWN Belen (Ericsson) asks questions and comments that overlaps with CR 543r1 (approved)
Jinhua(Xiaomi) response to Belen (Ericsson)
Belen (Ericsson) will send comments to S2-2104659
Withdrawn
99 S2-2104117 CR Approval 23.501 CR2895 (Rel-17, 'B'): Clarification on UE provides PDU Session Pair ID based on URSP rules Nokia, Nokia Shanghai Bell, Convida Wireless, Verizon, Qualcomm, Ericsson, Huawei, Hisilicon, LG Electronics, ZTE Rel-17 WITHDRAWN Withdrawn
99 S2-2104171 CR Approval 23.288 CR0243R2 (Rel-17, 'B'): Exposing UE mobility analytics for multiple NWDAFs case China Mobile Rel-17 Revision of (Postponed) S2-2102662. WITHDRAWN Withdrawn
99 S2-2104177 CR Approval 23.288 CR0243R3 (Rel-17, 'B'): Exposing UE mobility analytics for multiple NWDAFs case China Mobile Rel-17 Revision of (Postponed) S2-2102662. WITHDRAWN Withdrawn
99 S2-2104255 CR Approval 23.288 CR0286R2 (Rel-17, 'F'): Alignment Changes on NWDAF Data Management Services Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103278. WITHDRAWN Withdrawn
99 S2-2104536 CR Approval 23.288 CR0357 (Rel-17, 'C'): Analytics subscription transfer when consumer NF changes Samsung Rel-17 WITHDRAWN Withdrawn
99 S2-2104680 DISCUSSION Agreement discussion for paging restriction on PDU/PDN level Beijing Xiaomi Software Tech Rel-17 WITHDRAWN Withdrawn
99 S2-2104609 LS OUT Approval [DRAFT] LS reply to SA on GSMA 3GPP Edge Computing coordination Samsung Rel-17 Response to S2-2103728. WITHDRAWN Withdrawn
99 S2-2104535 P-CR Approval 23.548: PCR 23.548 Clarification on User Plane Latency Requirement Samsung Rel-17 WITHDRAWN Withdrawn
99 S2-2104547 P-CR Approval 23.548: PCR 23.548 Clarification on User Plane Latency Requirement Samsung Rel-17 WITHDRAWN Withdrawn
99 S2-2104212 P-CR Approval 23.247: 5MBS dynamic multicast transmission triggered by AF China Mobile M2M Company Ltd. Rel-17 WITHDRAWN Withdrawn
99 S2-2104221 P-CR Approval 23.247: 5MBS dynamic multicast transmission triggered by AF China Mobile M2M Company Ltd. Rel-17 WITHDRAWN Withdrawn
99 S2-2104225 P-CR Approval 23.247: 5MBS dynamic multicast transmission triggered by AF China Mobile M2M Company Ltd. Rel-17 WITHDRAWN Withdrawn
99 S2-2103814 CR Approval 23.288 CR0335 (Rel-17, 'B'): AF discovery and selection Ericsson Rel-17 WITHDRAWN Withdrawn
99 S2-2104252 CR Approval 23.288 CR0291R2 (Rel-17, 'B'): Clarify the Analytics Filter and the Target of Analytics Reporting for the trained model Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103241. WITHDRAWN Withdrawn
99 S2-2104253 CR Approval 23.501 CR2761R2 (Rel-17, 'B'): Add the reference for the Analytics Filter and the Target of Analytics Reporting of the trained model Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103242. WITHDRAWN Withdrawn
99 S2-2104390 CR Approval 23.502 CR2815 (Rel-17, 'B'): Support of multiple NSACF Huawei,HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2103782 LS OUT Approval [DRAFT] Reply LS to GSMA-ACJA: SA WG1 clarifications on problematic UAV Qualcomm Technologies Ireland Rel-17 Response to S2-2103731. WITHDRAWN Withdrawn
99 S2-2104477 CR Approval 23.502 CR2568R3 (Rel-17, 'B'): Introduction of MUSIM capability exchage Qualcomm Incorporated, Samsung, Intel, Apple, Lenovo, Motorola Mobility, MediaTek Inc., LG Electronics, Nokia, Nokia Shanghai Bell, Spreadtrum Rel-17 Revision of (Postponed) S2-2102346. WITHDRAWN Withdrawn
99 S2-2104377 SID NEW Information New SID: Study on architecture enhancement for tactile and multi-modality communication services . China Mobile, Rel-18 WITHDRAWN Withdrawn
99 S2-2104783 CR Approval 23.502 CR2757R1 (Rel-17, 'B'): BSF extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of (withdrawn) S2-2104009. WITHDRAWN Withdrawn
99 S2-2104775 CR Approval 23.501 CR2989 (Rel-17, 'C'): Support of Mobility Registration Update for 5G Satellite Access Qualcomm Incorporated Rel-17 WITHDRAWN Withdrawn
99 S2-2104009 CR Approval 23.502 CR2757 (Rel-17, 'B'): UDM extensions for 5MBS Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN, merging S2-2104780 Withdrawn
99 S2-2104011 CR Approval 23.502 CR2759 (Rel-17, 'B'): PCC impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revised to (withdrawn) S2-2104015. WITHDRAWN Withdrawn
99 S2-2103938 SID NEW Information New SID: Study on enhancement of 5G AM Policy. China Telecom Rel-18 WITHDRAWN Withdrawn
99 S2-2104350 DISCUSSION Endorsement Discussion on long eDRX value system impact to support REDCAP Ericsson Inc. Rel-17 WITHDRAWN Withdrawn
99 S2-2103993 CR Approval 23.501 CR2875 (Rel-16, 'F'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-16 Revision of (Endorsed) S2-2103058. WITHDRAWN Withdrawn
99 S2-2103994 CR Approval 23.501 CR2876 (Rel-17, 'B'): Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling/enabling Nokia, Nokia Shanghai Bell, Ericsson Rel-17 Revision of (Endorsed) S2-2103059. WITHDRAWN Withdrawn
99 S2-2104162 CR Approval 23.502 CR2782 (Rel-17, 'B'): UE context retrieval during registration procedure considering SNPN involved samsung Rel-17 WITHDRAWN Withdrawn
99 S2-2103881 CR Approval 23.502 CR2742 (Rel-17, 'B'): Different deployment options for NWDAFs Ericsson, NTT DOCOMO Rel-17 WITHDRAWN Withdrawn
99 S2-2104015 CR Approval 23.501 CR2879 (Rel-17, 'B'): PCC impacts of 5MBS Nokia, Nokia Shanghai Bell Rel-17 Revision of S2-2104011. WITHDRAWN Withdrawn
99 S2-2103826 CR Approval 23.502 CR2736 (Rel-17, 'B'): NSSAA procedures for the UE when it is served by two different AMFs Samsung Rel-17 WITHDRAWN Withdrawn
99 S2-2104091 CR Approval 23.502 CR2571R3 (Rel-17, 'B'): PMF measurements per QoS Flow Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2102378. WITHDRAWN Withdrawn
99 S2-2104092 CR Approval 23.502 CR2591R4 (Rel-17, 'B'): TS23.502 KI#2 Network Slice Admission Control Function (NSACF) services and procedures Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103472. WITHDRAWN Withdrawn
99 S2-2104093 CR Approval 23.503 CR0583 (Rel-17, 'B'): Maximum data rate control per S-NSSAI with assistance from the NWDAF Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2104094 CR Approval 23.288 CR0293R3 (Rel-17, 'B'): Add bandwidth into Dispersion analytics per slice Huawei, HiSilicon Rel-17 Revision of (Agreed) S2-2103271. WITHDRAWN Withdrawn
99 S2-2104095 CR Approval 23.501 CR2890 (Rel-17, 'A'): Updates on PCC rule triggered GTP-U Path Monitoring Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2104096 CR Approval 23.503 CR0584 (Rel-17, 'A'): Updates to Support QoS Monitoring Control for Service Data Flows Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2104097 CR Approval 23.502 CR2770 (Rel-16, 'F'): N9 forwarding tunnel between source and target ULCL Huawei, HiSilicon Rel-16 WITHDRAWN Withdrawn
99 S2-2104098 CR Approval 23.502 CR2771 (Rel-17, 'A'): N9 forwarding tunnel between source and target ULCL Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2104099 CR Approval 23.502 CR2772 (Rel-16, 'F'): CHF discovery via NRF Huawei, HiSilicon Rel-16 WITHDRAWN Withdrawn
99 S2-2104100 CR Approval 23.502 CR2773 (Rel-17, 'A'): CHF discovery via NRF Huawei, HiSilicon Rel-17 WITHDRAWN Withdrawn
99 S2-2104129 P-CR Approval 23.548: Resolve the editor's note about the DNS configuration Tencent, ZTE, Vivo, Spreadtrum, OPPO, Lenovo, Motorola Mobility, Alibaba Rel-17 WITHDRAWN Withdrawn
99 S2-2104447 P-CR Approval 23.548: Edge Relocation Involving AF change. NTT DOCOMO, Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2104559 CR Approval 23.501 CR2944 (Rel-17, 'A'): R17 23502 CR Accelerate IMS voice when S1 is disabled China Telecommunications Rel-17 WITHDRAWN Withdrawn
99 S2-2104567 CR Approval 23.502 CR2629R1 (Rel-17, 'B'): Addressing EN on re-selection of NWDAF at change of AMF NTT DOCOMO Rel-17 Revision of (Postponed) S2-2102297. WITHDRAWN Withdrawn
99 S2-2104595 CR Approval 23.682 CR0479 (Rel-17, 'B'): Dynamic management of group based event monitoring Ericsson, Convida Wireless LLC, AT&T, Huawei, Nokia, Nokia Shanghai Bell Rel-17 WITHDRAWN Withdrawn
99 S2-2104611 CR Approval 23.501 CR2954 (Rel-17, 'F'): Clarification on the Standardized SST values Nokia, Nokia Shanghai Bell, Qualcomm Inc Rel-17 WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 0
Parallel Agreed: 0
Approved/Endorsed: 183
Replied to LSs: 10
Noted: 333
Merged: 122
For e-mail approval: 0
Postponed: 104
Withdrawn: 54
Total documents: 1488