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:
|
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/SWG meeting including the Chair and Vice Chairs. 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/SWG meetings is important to allow for full and fair consideration of such matters. |
| 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:=2 | - | |
| 2 | S2-2500001 | AGENDA | Approval | SA2#166 Ad Hoc-e meeting Agenda | SA WG2 Chair | CC#1: This AGENDA was approved | Approved | ||
| 2 | S2-2500002 | AGENDA | Information | SA WG2#166 Ad Hoc-e meeting conference Call planning | SA WG2 Chair | CC#1: Left open for update during meeting. Noted | Noted | ||
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#166 Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2500003 | REPORT | Approval | Draft Report of SA WG2 meeting #166 | SA WG2 Secretary | CC#1: This REPORT was approved | Approved | ||
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=21 | - | |
| 4.1 | - | - | - | LS in for information - propose to note | - | - | Docs:=6 | - | |
| 4.1 | S2-2500059 | LS In | Information | LS from SA WG1: Reply LS on UAV regulation | SA WG1 (S1-244759) | Rel-19 | Noted in e-mail session | LaeYoung (LGE) proposes to NOTE this LS because no action is needed in SA2. | Noted |
| 4.1 | S2-2500030 | LS In | Information | LS from ITU-D SG2: Liaison statement from ITU-D Study Group 2 Question 4/2 to IEEE, ISO, IEC, ETSI, 3GPP, GSMA, IETF, Wi-Fi Alliance, International Laboratory Accreditation Cooperation, and International Accreditation Forum on draft final report of ITU-D | ITU-D SG2 (D22-SG02-C-0342) | Noted in e-mail session | Laurent (Nokia): Suggests to Note this LS for Information | Noted | |
| 4.1 | S2-2500073 | LS In | Information | LS from SA WG6: Reply LS on clarifications on consent management | SA WG6 (S6-245716) | Rel-18 | Noted in e-mail session | Laurent (Nokia): Suggests to Note this LS for Information | Noted |
| 4.1 | S2-2500075 | LS In | Information | LS from TSG SA: Reply LS on clarifications on consent management. | TSG SA (SP-241934) | Rel-18 | Noted in e-mail session | Laurent (Nokia): Suggests to Note this LS for Information | Noted |
| 4.1 | S2-2500029 | LS In | Information | LS from 5G-ACIA: 5G-ACIA LS on Enhancements for 5G System Operating as Logical (TSN) Bridge(s) in Integrated IEEE/3GPP Networks | 5G-ACIA (5G-ACIA-LS-2024-008) | Noted in e-mail session | Srinivas (Nokia) thanks ACIA for the LS and proposes to Note the LS Qianghua (Huawei) agrees with Srini to note the LS | Noted | |
| 4.1 | S2-2500076 | LS In | Information | LS from ETSI TC CYBER: Update on ETSI TC Cyber middlebox work | ETSI TC CYBER (CYBER(24)39d006r1) | Noted in e-mail session | Laurent (Nokia): Suggests to Note this LS for Information | Noted | |
| 4.1 | - | - | - | LS on CENs requirements for eCall over IMS | - | - | Docs:=2 | - | |
| 4.1 | S2-2500033 | LS In | Action | LS from CT WG1: Reply to Reply LS on CENs requirements for eCall over IMS | CT WG1 (C1-246950) | Rel-19 | Noted in e-mail session | Pallab (Nokia) proposes to NOTE the LS, as no action needed from SA2 side. | Noted |
| 4.1 | S2-2500057 | LS In | Action | LS from SA WG1: Reply LS on CEN requirements for eCall over IMS | SA WG1 (S1-244755) | Rel-19 | Noted in e-mail session | Pallab (Nokia) proposes to NOTE the LS as no action needed Chris (Vodafone) asks whether we should suggest to SA1, SA3 and/or CT1 that a maximum timer for the test ecall callback is also specified? Leo (Deutsche Telekom) replies to Chris Stephen (Qualcomm) comments and adds some information | Noted |
| 4.1 | - | - | - | LS on Clarification request on usage and control of UE Local Configuration | - | - | Docs:=6 | - | |
| 4.1 | S2-2500034 | LS In | Action | LS from CT WG1: Reply LS on Clarification request on usage and control of UE Local Configuration | CT WG1 (C1-247121) | Rel-19 | Responses drafted in S2-2500219, S2-2500519, S2-2500778, S2-2501027. FInal response in S2-2501276 | Srinivas (Nokia) proposes to use S2-2500219 as baseline for the LS reply Michele Zarri [Huawei] agrees to use S2-2500219 as baseline for the LS reply, however for Q3 Huawei prefers Qualcomm's proposed reply in S2-2500519 Belen [Ericsson] agrees to use S2-2500219 as baseline for the LS reply, Q1 while Q2 and Q3 we prefer Qualcomm's proposed reply in S2-2500519 Srinivas (Nokia) asks for clarification Hong (Qualcomm) provides S2-2500219r01, by incorporating contents from S2-2500519 for Q2 and Q3. Hong (Qualcomm) replies to Srinivas (Nokia). Hong (Qualcomm) comments. Pavan (Google) responds to Hong (Qualcomm) and Krisztian (Apple) Krisztian (Apple) responds to Hong (Qualcomm). Hong (Qualcomm) comments and provides a r04. Krisztian (Apple) provides 219r03. Pavan(Google) provides some comments and r02 Belen (Ericsson) provides r05 Srinivas (Nokia) comments on r04 and r05 Belen (Ericsson) provides r06 fixing some typos Pavan (Google) provides r07. Hong (Qualcomm) comments on r07. Pavan(Google) really provides r07 this time. Krisztian (Apple) is OK with r07. Srinivas (Nokia) is Ok with R07. | Replied to |
| 4.1 | S2-2500219 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Nokia | Rel-19 | Response to S2-2500034. r07 agreed. Revised in e-mail session to S2-2501276, merging S2-2500519, S2-2500778 and S2-2501027 | Hong (Qualcomm) provides r01, according to comments in thread of S2-2500034. Hong (Qualcomm) provides r04, according to comments in thread of S2-2500034. Krisztian (Apple) provides r03 according to comments in the thread of S2-2500034. ==== General Revisions Deadline ==== Srinivas (Nokia) is Ok with R07 as discussed in S2-2500034 Hong (Qualcomm) is fine with r07. ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2501276 | LS OUT | Approval | Reply LS on Clarification request on usage and control of UE Local Configuration | SA WG2 | Rel-19 | Revision of S2-2500219r07, merging S2-2500519, S2-2500778 and S2-2501027. Approved | Approved | |
| 4.1 | S2-2500519 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Qualcomm Incorporated | Rel-15 | Response to S2-2500034. Merged into S2-2501276 | Merged | |
| 4.1 | S2-2500778 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Samsung | Response to S2-2500034. Merged into S2-2501276 | Merged | ||
| 4.1 | S2-2501027 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Rel-19 | Response to S2-2500034. Merged into S2-2501276 | Merged | ||
| 4.1 | - | - | - | LS on support of multiple access technologies based on the IMS service type | - | - | Docs:=4 | - | |
| 4.1 | S2-2500060 | LS In | Action | LS from SA WG1: Reply LS on support of multiple access technologies based on the IMS service type | SA WG1 (S1-244916) | Rel-20 | Responses drafted in S2-2500786, S2-2500943. FInal response in S2-2501277 | Replied to | |
| 4.1 | S2-2500786 | LS OUT | Approval | [DRAFT] Reply LS on support of multiple access technologies based on the IMS service type | China Telecom | Rel-20 | Response to S2-2500060. Merged into S2-2501277 | Merged | |
| 4.1 | S2-2500943 | LS OUT | Approval | [DRAFT] Reply LS on support of multiple access technologies based on the IMS service type | Samsung | Rel-20 | Response to S2-2500060. r04 agreed. Revised in e-mail session to S2-2501277, merging S2-2500786 | Kenny (Qualcomm) proposed to take this paper as baseline for LS OUT, with merging the justification from S2-2500786. Yan Li (China Telecom) is OK with QC's propoal to take Samsung's paper (S2-2500943) as baseline with merging the justification from CT's paper (S2-2500786). Rainer (Nokia) asks for clarification Ashok (Samsung) provides response Michele Zarri [Huawei] agrees to use S2-2500943 as baseline for the reply which however should be sent to TSG SA Rainer (Nokia) provides r02 Kenny (Qualcomm) is not OK with r02 and prefer to provide clear message to SA1. Ashok (Samsung) provides response to Rainer Rainer (Nokia) replies Krisztian (Apple) supports the direction of r02 and not OK with previous versions. Yan Li (China Telecom) provides comments and annouces r01 provided before. Kenny (Qualcomm) provides r03, which proposes an editorial change upon r02. Rainer (Nokia) is ok with r03 Yan Li (China Telecom) can live with r03, and provides r04 with adding SA to action part. Rainer (Nokia) is ok with r04 Ashok (Samsung) is ok with r04 ==== General Revisions Deadline ==== Kenny (Qualcomm) is OK with r04. Krisztian (Apple) is ok with r04. Mu (Huawei) is ok with r04 ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2501277 | LS OUT | Approval | Reply LS on support of multiple access technologies based on the IMS service type | SA WG2 | Rel-20 | Revision of S2-2500943r04, merging S2-2500786. Approved | Approved | |
| 4.1 | - | - | - | LS on Usage of Charging Characteristics and CHF Group ID | - | - | Docs:=1 | - | |
| 4.1 | S2-2500067 | LS In | Action | LS from SA WG5: LS on Usage of Charging Characteristics and CHF Group ID | SA WG5 (S5-246956) | Rel-19 | Postponed in e-mail session | Shabnam (Ericsson) proposes to postpone the LS, Ericsson plans to contribute at the next meeting for this. | Postponed |
| 4.1 | - | - | - | LS from GSMA TSGNS: OSAppID usage by AppToken use case | - | - | Docs:=2 | - | |
| 4.1 | S2-2500077 | LS In | Information | LS from GSMA TSGNS: OSAppID usage by AppToken use case | GSMA TSGNS (TSGNS44_003v6) | Response drafted in S2-2500962. Postponed in e-mail session | Stefano (Qualcomm) proposes to postpone to SA2#167 for in depth discussion. Michele Zarri [Huawei] agrees to postpone the reply to this LS to SA2#167 Pavan [Google] also agrees to postpone the reply to SA2#167. Masaharu [KDDI] also agrees to postpone the reply to SA2#167. Krisztian (Apple) supports postponing this LS to the February F2F meeting. Srinivas (Nokia) thanks for the discussion, and is fine with the proposal to postpone. | Postponed | |
| 4.1 | S2-2500962 | LS OUT | Approval | [DRAFT] Reply LS for OSAppID usage by AppToken use case | China Mobile | Rel-19 | Response to S2-2500077. Postponed in e-mail session | Srinivas (Nokia) provides comments on the direction of LS response Stefano (Qualcomm) proposes to postpone to SA2#167 for in depth discussion. Huazhang (China Mobile) reply to Srinivas (Nokia) Belen (Ericsson) would prefer to focus the LS reply on the questions from GSMA that are in the scope of SA2. Huazhang (CMCC) reply to Stefano (Qualcomm) Stefano (Qualcomm) reconfirms that we should wait for a F2F discussion in February, there is no urgency since GSMA meets in March. Susana (Vodafone) agrees with Ericsson that reply to LS from SA2 needs to remain within SA2 responsibility and adds some comments. Susana (Vodafone) replies to Srinivas Srinivas (Nokia) provides clarification to Susana Jicheol (Samsung) agrees to postpone the respons LS. Krisztian (Apple) supports postponing the LS response to the February F2F meeting. Huazhang (China Mobile) agree to postpone the LS, but I agree with Susana that SA2 can answer the question that GSMA ask, If GSMA doesn't have clear understanding of URSP, we can correct that, and whether this GSMA solution feasible or not is in GSMA scope. We can have further discussion in Athens Srinivas (Nokia) thanks for the discussion, and is fine with the proposal to postpone. Huazhang (CMCC) agree to postpone this to next meeting, but I find we have two direction, we need more discussion ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=0 | - | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=0 | - | |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=0 | - | |
| 5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | Docs:=0 | - | |
| 5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | Docs:=0 | - | |
| 6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Docs:=0 | - | |
| 6.1 | - | - | - | General aspects, concepts and reference models | - | - | Docs:=4 | - | |
| 6.1 | S2-2500038 | LS In | Action | LS from CT WG4: Reply LS on slice mapping between the HPLMN and EHPLMN | CT WG4 (C4-245430) | Rel-18 | Responses drafted in S2-2500605, S2-2500867. FInal response in S2-2501076 | Replied to | |
| 6.1 | S2-2500605 | LS OUT | Approval | [DRAFT] Response LS on slice mapping between the HPLMN and EHPLMN | Huawei, HiSilicon | Rel-18 | Response to S2-2500038. Merged into S2-2501076 | Jinguo(ZTE) suggests to merge 605 into 867. ==== General Revisions Deadline ==== Fenqin (Huawei) agree to merge 605 into 867. ==== Comments Deadline ==== | Merged |
| 6.1 | S2-2500867 | LS OUT | Approval | [DRAFT] LS Response on slice mapping between the HPLMN and EHPLMN | ZTE | Rel-18 | Response to S2-2500038. r04 agreed. Revised in e-mail session to S2-2501076, merging S2-2500605 | Ashok (Samsung) proposed to take this paper as baseline for LS OUT. Fenqin (Huawei) provides comment. Jinguo(ZTE) provides r01 Jinguo(ZTE) provides response to Fenqin Jinguo(ZTE) provides r04 Fenqin (Huawei) provides r03 Jinguo(ZTE) provides r02 ==== General Revisions Deadline ==== Fenqin (Huawei) is ok with r04 Qian (Ericsson) is ok with r04 ==== Comments Deadline ==== | Revised |
| 6.1 | S2-2501076 | LS OUT | Approval | LS Response on slice mapping between the HPLMN and EHPLMN | SA WG2 | Rel-18 | Revision of S2-2500867r04, merging S2-2500605. Approved | Approved | |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=3 | - | |
| 6.2 | S2-2500404 | CR | Approval | 23.502 CR5241 (Rel-19, 'F'): NSSAI update with RA change | Ericsson, AT&T | Rel-19 | Noted in e-mail session | Myungjune (LGE) provides comments. LiMeng (Huawei) asks for clarification. Qian (Ericsson) provides clarifications. Jinguo (ZTE) ask whether this CR is FASMO Alessio ( Nokia) asks a question for clarification Fenqin (Huawei) asks a question for clarification Myungjune (LGE) responses to Qian (Ericsson). Qian (Ericsson) provides comments to Fenqin (Huawei) and Alessio (Nokia) Qian (Ericsson) provides comments to Jinguo (ZTE). Fenqin (Huawei) responses to Qian (Ericsson). Alessio(Nokia agrees with the comments by Fenqin (Huawei to Qian (Ericsson).and adds that if the problem exists then it should apply even more so for the MRU procedure where the RA is definitely going to change at least when mobility happens. Alessio replies to Qian (Ericsson) and provides comments ==== General Revisions Deadline ==== Qian (Ericsson) proposes to NOTE the paper. ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2500875 | CR | Approval | 23.501 CR6022 (Rel-19, 'A'): Clarification on NSAC for EHPLMN case | ZTE | Rel-19 | Noted in e-mail session | Qian (Ericsson) indicates that it's the mirror CR of 0918 and the final content shall be synched. Jinguo(ZTE) suggest to note this mirror CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2500918 | CR | Approval | 23.501 CR6037 (Rel-18, 'F'): Clarification on NSAC for EHPLMN case | ZTE | Rel-18 | Noted in e-mail session | Qian (Ericsson) provides comments Fenqin (Huawei) provides comments Jinguo(ZTE) provides response to Fenqin and Qian, provides r01 Jinguo(ZTE) suggest to note this CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=0 | - | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=4 | - | |
| 6.5 | S2-2500360 | CR | Approval | 23.501 CR5931 (Rel-18, 'F'): VPLMN QoS constraint clarification | Ericsson | Rel-18 | r01 agreedrevised in e-mail session to S2-2501077. | Srinivas (Nokia) provides asks clarification Hong (Qualcomm) comments and expresses concerns on the changes. Srinivas (Nokia) asks for clarification Qian (Ericsson) provides clarification to Hong (Qualcomm). Qian (Ericsson) provides clarifications. Fenqin (Huawei) ask question for clarification . Srinivas (Nokia) updates on the email chain Hong (Qualcomm) replies to Qian (Ericsson). Fenqin (Huawei) provides comments Srinivas (Nokia) provides comments Qian (Ericsson) provides further response to Hong (Qualcomm) and Fenqin (Huawei). Qian (Ericsson) provides further comments and provides r01 ==== General Revisions Deadline ==== Qian (Ericsson) propose to go with r01 ==== Comments Deadline ==== | Revised |
| 6.5 | S2-2501077 | CR | Approval | 23.501 CR5931R1 (Rel-18, 'F'): VPLMN QoS constraint clarification | Ericsson | Rel-18 | Revision of S2-2500360r01. Approved | Agreed | |
| 6.5 | S2-2500361 | CR | Approval | 23.501 CR5932 (Rel-19, 'A'): VPLMN QoS contranit clarification | Ericsson | Rel-19 | r00 agreedrevised in e-mail session to S2-2501078. | Revised | |
| 6.5 | S2-2501078 | CR | Approval | 23.501 CR5932R1 (Rel-19, 'A'): VPLMN QoS constraint clarification | Ericsson | Rel-19 | Revision of S2-2500361. Approved | Agreed | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=5 | - | |
| 6.6 | S2-2500258 | CR | Approval | 23.502 CR5223 (Rel-19, 'F'): Reporting PCF authorization failure to the AF | Ericsson, AT&T | Rel-19 | r01 agreedrevised in e-mail session to S2-2501079. | Hong (Qualcomm) comments and suggests changes. Belen (Ericsson) provides r01 to address QC comments. Jicheol (Samsung) comments. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.6 | S2-2501079 | CR | Approval | 23.502 CR5223R1 (Rel-19, 'F'): Reporting PCF authorization failure to the AF | Ericsson, AT&T | Rel-19 | Revision of S2-2500258r01. Approved | Agreed | |
| 6.6 | S2-2500259 | CR | Approval | 23.503 CR1463 (Rel-19, 'F'): Reporting PCF authorization failure to the AF | Ericsson, AT&T | Rel-19 | Approved | Jicheol (Samsung) comments. Belen (Ericsson) provides a response from Samsung Belen (Ericsson) replies ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 6.6 | S2-2500260 | CR | Approval | 23.502 CR5224 (Rel-19, 'F'): Removing URSP rules upon UDR Policy Data removal | Ericsson, AT&T | Rel-19 | r01 agreedrevised in e-mail session to S2-2501080. | Haiyang (Huawei) comments. Haiyang (Huawei) is OK with r01. Belen (Ericsson) provides r01 to address Huawei comments. ==== General Revisions Deadline ==== Srinivas (Nokia) is Ok with r01 ==== Comments Deadline ==== | Revised |
| 6.6 | S2-2501080 | CR | Approval | 23.502 CR5224R1 (Rel-19, 'F'): Removing URSP rules upon UDR Policy Data removal | Ericsson, AT&T | Rel-19 | Revision of S2-2500260r01. Approved | Agreed | |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=0 | - | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=6 | - | |
| 6.9 | S2-2500606 | CR | Approval | 23.502 CR5262 (Rel-17, 'F'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-17 | r00 agreedrevised in e-mail session to S2-2501081. | Haris(Qualcomm) indicates no technical concerns with the CR but typos in the coversheet need to be corrected ==== Comments Deadline ==== | Revised |
| 6.9 | S2-2501081 | CR | Approval | 23.502 CR5262R1 (Rel-17, 'F'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-17 | Revision of S2-2500606. Approved | Agreed | |
| 6.9 | S2-2500607 | CR | Approval | 23.502 CR5263 (Rel-18, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-18 | r00 agreedrevised in e-mail session to S2-2501082. | Revised | |
| 6.9 | S2-2501082 | CR | Approval | 23.502 CR5263R1 (Rel-18, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-18 | Revision of S2-2500607. Approved | Agreed | |
| 6.9 | S2-2500608 | CR | Approval | 23.502 CR5264 (Rel-19, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-19 | r00 agreedrevised in e-mail session to S2-2501083. | Revised | |
| 6.9 | S2-2501083 | CR | Approval | 23.502 CR5264R1 (Rel-19, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-19 | Revision of S2-2500608. Approved | Agreed | |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=2 | - | |
| 6.11 | S2-2500168 | CR | Approval | 23.501 CR5820R1 (Rel-19, 'F'): Correction on network function service framework | China Mobile | Rel-19 | Revision of S2-2411419. r01 agreed. Revised in e-mail session to S2-2501084. | Josep (Deutsche Telekom) would like to co-sign. Huazhang (CMCC) provides r01 and reply to Josep (Deutsche Telekom) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.11 | S2-2501084 | CR | Approval | 23.501 CR5820R2 (Rel-19, 'F'): Correction on network function service framework | China Mobile, Deutsche Telekom | Rel-19 | Revision of S2-2500168r01. 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:=2 | - | |
| 7.1 | S2-2500257 | CR | Approval | 23.502 CR5222 (Rel-19, 'F'): Correcting service specific parameter provisioning | Ericsson, AT&T | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501278. | LaeYoung (LGE) proposes to take eV2XARC out from WI code in the coverpage. Magnus (Ericsson) understands that clause 4.15.6.7.2 was introduced by eV2XARC, but changes may be due to 5WWC_Ph2, eEDGE_5GC this is in r01. LaeYoung (LGE) thanks to Magnus (Ericsson) for r01 and is fine with r01. Laurent (Nokia): How come that a CR for WID 5WWC_Ph2, eEDGE_5GC, TEI19 ends up in V2X session???? ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.1 | S2-2501278 | CR | Approval | 23.502 CR5222R1 (Rel-19, 'F'): Correcting service specific parameter provisioning | Ericsson | Rel-19 | Revision of S2-2500257r01. Approved | Agreed | |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=0 | - | |
| 7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | Docs:=0 | - | |
| 7.4 | - | - | - | Cellular IoT support and evolution for the 5G System (5G_CIoT) | - | - | Docs:=0 | - | |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=0 | - | |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=14 | - | |
| 7.7 | S2-2500416 | DISCUSSION | Discussion | Discussion paper on missing Optional LLDP TLVs . | Nokia | Noted in e-mail session | Noted | ||
| 7.7 | S2-2500417 | CR | Approval | 23.501 CR5945 (Rel-16, 'F'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-16 | Noted in e-mail session | Srinivas (Nokia) provides clarification to Zhendong and Haiyang Zhendong (ZTE) provides comments. Haiyang (Huawei) seeks for clarification. Haiyang (Huawei) is OK with the proposal from Stefan (Ericsson) Stefan (Ericsson) provides comments whether we need to go back to previous releases, suggests to work on the rel-19 CR instead Srinivas (Nokia) proposes to Note based on the below discussion Srinivas (Nokia) provides comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2500418 | CR | Approval | 23.501 CR5946 (Rel-17, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-17 | Noted in e-mail session | Srinivas (Nokia) proposes to Note based on the discussion in S2-2500417 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2500419 | CR | Approval | 23.501 CR5947 (Rel-18, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-18 | r02 agreed. Revised in e-mail session to S2-2501279. | Srinivas (Nokia) provides r01 based on the discussion in S2-2500417 Stefan (Ericsson) provides r02 Srinivas (Nokia) agrees to the changes proposed by Stefan ==== General Revisions Deadline ==== Srinivas (Nokia) is OK with r02 ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2501279 | CR | Approval | 23.501 CR5947R1 (Rel-18, 'F'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-18 | Revision of S2-2500419r02. Approved | Agreed | |
| 7.7 | S2-2500420 | CR | Approval | 23.501 CR5948 (Rel-19, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501280. | Stefan (Ericsson) provides r01 Srinivas (Nokia) provides r02 based on the discussion in S2-2500417 Srinivas (Nokia) provides r03 based on the discussion in S2-2500419 ==== General Revisions Deadline ==== Srinivas (Nokia) is Ok with r03 ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2501280 | CR | Approval | 23.501 CR5948R1 (Rel-19, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-19 | Revision of S2-2500420r03. Approved | Agreed | |
| 7.7 | S2-2500766 | DISCUSSION | Discussion | PDU Session Modification for Port Management Information. | Samsung | Noted in e-mail session | Noted | ||
| 7.7 | S2-2500770 | CR | Approval | 23.502 CR5281 (Rel-16, 'F'): PDU Session Modification for Port Management Information | Samsung | Rel-16 | Noted in e-mail session | Shabnam (Ericsson) provides comments whether we need to go back to Rel-16, agrees that the change is valid. Haiyang (Huawei) provides a suggestion. Sang-Jun (Samsung) replies to Shabnam (Ericsson). Shabnam (Ericsson) provides comments that we don't see FASMO applies to deeply frozen Rel-16/Rel-17, additional suggestion provided Sang-Jun (Samsung) accepts suggestions from Shabnam (Ericsson) and Haiyang (Huawei), with noting R16/17 (0770,0773) and updating R18/19 (0774,0777) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2500773 | CR | Approval | 23.502 CR5282 (Rel-17, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-17 | Noted in e-mail session | Sang-Jun (Samsung) proposes to note the paper as discussed in 0770 mail thread. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2500774 | CR | Approval | 23.502 CR5283 (Rel-18, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-18 | r01 agreed. Revised in e-mail session to S2-2501281. | Sang-Jun (Samsung) provides r01 as discussed in 0770 mail thread. Qianghua (Huawei) asks a revision ==== General Revisions Deadline ==== Srinivas (Nokia) is Ok with r01, with the movement of the text to 'Other comments' as commented by Haiyang Sang-Jun (Samsung) accepts the suggestions to go with r01 + changes asked by Haiyang and Qianghua (Huawei). - Revision number 0 to 1 - mobing Added text to coversheet Haiyang (Huawei) suggest to go with r01 with moving ''This applies to earlier Releases (R16 and R17) as well.'' From the text to the cover sheet 'other comments', ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2501281 | CR | Approval | 23.502 CR5283R1 (Rel-18, 'F'): PDU Session Modification for Port Management Information | Samsung | Rel-18 | Revision of S2-2500774r01. Approved | Agreed | |
| 7.7 | S2-2500777 | CR | Approval | 23.502 CR5285 (Rel-19, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-19 | Revised in e-mail session to S2-2501282. | Revised | |
| 7.7 | S2-2501282 | CR | Approval | 23.502 CR5285R1 (Rel-19, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-19 | Revision of S2-2500777. Approved | Agreed | |
| 7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | Docs:=0 | - | |
| 7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | Docs:=0 | - | |
| 7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | Docs:=0 | - | |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=0 | - | |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=0 | - | |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=0 | - | |
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=0 | - | |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=0 | - | |
| 7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | Docs:=0 | - | |
| 7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | Docs:=0 | - | |
| 8 | - | - | - | Rel-17 Maintenance | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=2 | - | |
| 8.1 | S2-2500095 | CR | Approval | 23.288 CR1311 (Rel-19, 'F'): Correction on MFAF related service | ZTE | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501283. | Zhang (Huawei) provide comments Yuang(ZTE) replies Zhang (Huawei) Yuang(ZTE) replies to Zhang (Huawei) and provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2501283 | CR | Approval | 23.288 CR1311R1 (Rel-19, 'F'): Correction on MFAF related service | ZTE | Rel-19 | Revision of S2-2500095r01. Approved | Agreed | |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=0 | - | |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=0 | - | |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=0 | - | |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=0 | - | |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=4 | - | |
| 8.6 | S2-2500381 | CR | Approval | 23.501 CR5936 (Rel-17, 'F'): Correction to specify UE and Network behaviour when steering capability do not match for a UE requested MA PDU Session | Nokia | Rel-17 | Noted in e-mail session | Stefan (Ericsson) provides concerns Pallab (Nokia) responds to Stefan (Ericsson) Yishan (Huawei) provides comments Yishan (Huawei) answers to Pallab (Nokia) Stefan (Ericsson) replies to Pallab ==== General Revisions Deadline ==== Yishan (Huawei) thanks Pallab (Nokia) for the clarification and also suggests to postpone the discussion in future meeting Stefan (Ericsson) objects and proposes to note the CR ==== Comments Deadline ==== | Noted |
| 8.6 | S2-2500382 | CR | Approval | 23.501 CR5937 (Rel-18, 'A'): Correction to specify UE and Network behaviour when steering capability do not match for a UE requested MA PDU Session | Nokia | Rel-18 | Noted in e-mail session | Yishan (Huawei) suggests to postpone this mirror CR as discussed in S2-2500381 Stefan (Ericsson) proposes that mirror should be noted based on discussion for S2-2500381 ==== Comments Deadline ==== | Noted |
| 8.6 | S2-2500383 | CR | Approval | 23.503 CR1468 (Rel-17, 'F'): Clarification on PCC Rule for 'match all' traffic when the MA PDU Session supports ATSSS-LL | Nokia | Rel-17 | Noted in e-mail session | Stefan (Ericsson) provides simmilar concerns as for S2-2500381 Yishan (Huawei) provides similar comments as for S2-2500381 ==== General Revisions Deadline ==== Yishan (Huawei) proposes to postpone the discussion in future meeting Stefan (Ericsson) objects and proposes to note the CR ==== Comments Deadline ==== | Noted |
| 8.6 | S2-2500384 | CR | Approval | 23.503 CR1469 (Rel-18, 'A'): Clarification on PCC Rule for 'match all' traffic when the MA PDU Session supports ATSSS-LL | Nokia | Rel-18 | Noted in e-mail session | Yishan (Huawei) suggests to postpone this mirror CR as discussed in S2-2500383 Stefan (Ericsson) proposes that mirror should be noted based on discussion for S2-2500383 ==== Comments Deadline ==== | Noted |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=17 | - | |
| 8.7 | S2-2500039 | LS In | Action | LS from CT WG4: LS on UUAA Unsubscribe procedure | CT WG4 (C4-245436) | Rel-17 | Responses drafted in S2-2500437, S2-2500509, S2-2500602, S2-2500941. Postponed in e-mail session | Yunjing (CATT) proposed to postpone the LS based on offline discussion. | Postponed |
| 8.7 | S2-2500437 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Ericsson | Rel-17 | Response to S2-2500039. Postponed in e-mail session | Yunjing (CATT) provides comments. Pallab (Nokia) agrees with the comments from Yunjing (CATT) Jaewoo (LGE) provides comments. Yunjing (CATT) replies to Jaewoo (LGE). Ashok (Samsung) provides comments and suggests to keep it simple with a new Unsubscribe service operation Jaewoo (LGE) further replies to Yunjing (CATT). Shabnam (Ericsson) provides comments that we need to consider option where we align with implicit procedure, lack of mentioning explicitly 'implicit' should not require new SBI. Yunjing (CATT) proposes to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500509 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | CATT | Rel-17 | Response to S2-2500039. Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500602 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Nokia | Rel-17 | Response to S2-2500039. Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500941 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Samsung | Rel-17 | Response to S2-2500039. Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500392 | CR | Approval | 23.256 CR0157 (Rel-17, 'D'): Removing ENs for clean-up | LG Electronics | Rel-17 | Approved | Agreed | |
| 8.7 | S2-2500393 | CR | Approval | 23.256 CR0158 (Rel-18, 'A'): Removing ENs for clean-up | LG Electronics | Rel-18 | Approved | Agreed | |
| 8.7 | S2-2500394 | CR | Approval | 23.256 CR0159 (Rel-19, 'A'): Removing ENs for clean-up | LG Electronics | Rel-19 | Approved | Agreed | |
| 8.7 | S2-2500510 | CR | Approval | 23.256 CR0168 (Rel-17, 'F'): UUAA Unsubscribe | CATT | Rel-17 | Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500511 | CR | Approval | 23.256 CR0169 (Rel-18, 'A'): UUAA Unsubscribe | CATT | Rel-18 | Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500512 | CR | Approval | 23.256 CR0170 (Rel-19, 'A'): UUAA Unsubscribe | CATT | Rel-19 | Postponed in e-mail session | Yunjing (CATT) proposed to postpone the document based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500599 | CR | Approval | 23.256 CR0172 (Rel-17, 'F'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-17 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500510. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500600 | CR | Approval | 23.256 CR0173 (Rel-18, 'A'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-18 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500511. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500601 | CR | Approval | 23.256 CR0174 (Rel-19, 'A'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-19 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500512. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500917 | CR | Approval | 23.256 CR0179 (Rel-17, 'F'): Unsubscribe service operation with UAS NF | Samsung | Rel-17 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500510. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500919 | CR | Approval | 23.256 CR0180 (Rel-18, 'A'): Unsubscribe service operation with UAS NF | Samsung | Rel-18 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500511. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2500921 | CR | Approval | 23.256 CR0181 (Rel-19, 'A'): Unsubscribe service operation with UAS NF | Samsung | Rel-19 | Postponed in e-mail session | Yunjing (CATT) suggests to merge the CR into S2-2500512. Yunjing (CATT) proposes to postpone the CR based on offline discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=0 | - | |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=7 | - | |
| 8.9 | S2-2500249 | CR | Approval | 23.247 CR0378 (Rel-17, 'F'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-17 | Approved | Agreed | |
| 8.9 | S2-2500250 | CR | Approval | 23.247 CR0379 (Rel-18, 'A'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-18 | Approved | Agreed | |
| 8.9 | S2-2500251 | CR | Approval | 23.247 CR0380 (Rel-19, 'A'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-19 | Approved | Agreed | |
| 8.9 | S2-2500571 | CR | Approval | 23.247 CR0381 (Rel-17, 'F'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-17 | Noted in e-mail session | Thomas (Nokia) comments that intention of CR overlaps with S2-2500988 and only one should be pursued. Suggests to use S2-2500988 and consider the Rel-19 version of S2-2500571 as merged. Changes to earlier Releases should be noted as changes are not FASMO enough. LiMeng (Huawei) prefer to use this document as the basis, OK to only go with Rel-19. R01 is provided. Thomas(Nokia) raises concerns against r00 and r01 and provides r02. Can live with merging S2-2500988 into Rel-19 version of S2-2500571 Prefers to change Rel-19 only. ==== General Revisions Deadline ==== Robbie (Ericsson) replies to LiMeng (Huawei). LiMeng (Huawei) is OK for the postponing. Thomas's provided r02 is OK. Robbie (Ericsson) suggests marking it as Postponed Haris(Qualcomm) prefers to agree rel.19 version ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2500572 | CR | Approval | 23.247 CR0382 (Rel-18, 'A'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-18 | Noted in e-mail session | LiMeng (Huawei) can accept to continue the discussion in Athens meeting. Robbie (Ericsson) suggests marking it as Postponed Thomas(Nokia) comments that we now have an agreement to go for Rel-19 only and suggest agreeing in this meeting ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2500573 | CR | Approval | 23.247 CR0383 (Rel-19, 'A'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-19 | Not handled at CC#4. Postponed | LiMeng (Huawei) is OK for the postponing. Robbie (Ericsson) suggests marking it as Postponed Thomas (Nokia) clarifies that discussions focused on Rel-17 version of CR in S2-2500573, but agreement was to go for Rel-19 only. Thus S2-2500573 should be agreed with same changes as in S2-2500573r02, plus converting to CAF F, plus adding TEI-19 as WI code. Robbie (Ericsson) comments we don't have a good discussion on 'agreement was to go for Rel-19 only' Thomas (Nokia) corrects himself: clarifies that discussions focused on Rel-17 version of CR in S2-2500571, but agreement was to go for Rel-19 only. Thus S2-2500573 should be agreed with same changes as in S2-2500571r02, plus converting to CAF F, plus adding TEI-19 as WI code. Thomas(Nokia) prefers Rel-19 only, but can also live with changes from Rel-17 onwards Robbie (Ericsson) prefers changes from Rel-17 onwards, but can also live with Rel-19 only LiMeng (Huawei) is OK to have it only in rel-19. Robbie (Ericsson) comments: it seems majority view is to have it only in rel-19. Thomas (Nokia) suggest to go for Rel-19 only: Thus S2-2500573 should be agreed with same changes as in S2-2500571r02, plus converting to CAF F, plus adding TEI-19 as WI code. Robbie (Ericsson) agrees with Thomas (Nokia) on the way forward Thomas(Nokia) comments we now have agreement to go for REl-19 only. LiMeng (Huawei) appreciates the efforts and comments from the involved companies. LiMeng (Huawei) asks the efforts and comments from the involved companies. ==== Comments Deadline ==== LiMeng (Huawei) provides the revision of S2-2500573 to the draft/after revision deadline folder. | Postponed |
| 8.9 | S2-2500988 | CR | Approval | 23.247 CR0386 (Rel-19, 'F'): Clarification about MBS service area encoding | Nokia | Rel-19 | Postponed in e-mail session | Robbie (Ericsson) suggests merging it to S2-2500573. Thomas (Nokia) rather suggests using this CR as basis and go for Rel-19 only. Thomas(Nokia) accepts merging into Rel-19 version of S2-2500573. ==== General Revisions Deadline ==== Robbie (Ericsson) suggests marking it as Postponed ==== Comments Deadline ==== | Postponed |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=0 | - | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=0 | - | |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=0 | - | |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=0 | - | |
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=0 | - | |
| 8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | Docs:=0 | - | |
| 8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | Docs:=0 | - | |
| 8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | Docs:=0 | - | |
| 8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | Docs:=0 | - | |
| 8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | Docs:=0 | - | |
| 8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | Docs:=8 | - | |
| 8.21 | S2-2500666 | CR | Approval | 23.503 CR1374R2 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon | Rel-18 | Revision of S2-2410723. r03 agreed. Revised in e-mail session to S2-2501284. | Srinivas (Nokia) provides comments to align with stage 3 spec. Haiyang (Huawei) provides r01 with minor wording update. Haiyang (Huawei) provides r02. Belen (Ericsson) supports this CR Srinivas (Nokia) provides r03 to align with stage 3 as discussed ==== General Revisions Deadline ==== Haiyang (Huawei) is OK with r03. Srinivas (Nokia) is Ok with only r03. ==== Comments Deadline ==== | Revised |
| 8.21 | S2-2501284 | CR | Approval | 23.503 CR1374R3 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon, Ericsson, Nokia | Rel-18 | Revision of S2-2500666r03. Approved | Agreed | |
| 8.21 | S2-2500667 | CR | Approval | 23.503 CR1375R2 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2410724. Revised in e-mail session to S2-2501285. | Revised | |
| 8.21 | S2-2501285 | CR | Approval | 23.503 CR1375R3 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2500667. Approved | Agreed | |
| 8.21 | S2-2500668 | CR | Approval | 23.502 CR5020R2 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon | Rel-18 | Revision of S2-2410725. r03 agreed. Revised in e-mail session to S2-2501286. | Haiyang (Huawei) provides r01 with minor wording update. Belen (Ericsson) provides r02 with impacts on a new clause and updates to the service description. Haiyang (Huawei) answers the question from Belen, OK with r02. Belen (Ericsson) provides r03 now that Huawei provides more explanation ==== General Revisions Deadline ==== Haiyang (Huawei) OK with r03. Srinivas (Nokia) is Ok with r03 ==== Comments Deadline ==== | Revised |
| 8.21 | S2-2501286 | CR | Approval | 23.502 CR5020R3 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2500668r03. Approved | Agreed | |
| 8.21 | S2-2500669 | CR | Approval | 23.502 CR5021R2 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2410726. Revised in e-mail session to S2-2501287. | Revised | |
| 8.21 | S2-2501287 | CR | Approval | 23.502 CR5021R3 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2500669. Approved | Agreed | |
| 8.22 | - | - | - | IP address pool information from UDM (TEI17_IPU) | - | - | Docs:=0 | - | |
| 8.23 | - | - | - | Same PCF selection for AMF and SMF (TEI17-SPSFAS) | - | - | Docs:=0 | - | |
| 8.24 | - | - | - | Support of different slices over different Non-3GPP access (TEI17_N3SLICE) | - | - | Docs:=0 | - | |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=0 | - | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=0 | - | |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=0 | - | |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=0 | - | |
| 9 | - | - | - | Rel-18 WIDs | - | - | Docs:=0 | - | |
| 9.1.2 | - | - | - | 5G System with Satellite Backhaul (5GSATB) | - | - | Docs:=0 | - | |
| 9.2.2 | - | - | - | Satellite access Phase 2 (5GSAT_Ph2) | - | - | Docs:=0 | - | |
| 9.3.2 | - | - | - | Personal IoT Networks (5G_PIN) | - | - | Docs:=2 | - | |
| 9.3.2 | S2-2500472 | CR | Approval | 23.501 CR5961 (Rel-18, 'F'): Fix on N3QAI | Samsung | Rel-18 | Noted in e-mail session | LaeYoung (LGE) agrees with Pallab (Nokia) and proposes to NOTE this CR. Pallab (Nokia) provides comments Qian (Ericsson) shares the same view as LaeYoung(LGE) and Pallab (Nokia). ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.3.2 | S2-2500474 | CR | Approval | 23.501 CR5962 (Rel-19, 'A'): Fix on N3QAI | Samsung | Rel-19 | Noted in e-mail session | LaeYoung (LGE) proposes to NOTE this CR. Pallab (Nokia) provides comments: This is a mirror and depends on the outcome of S2-2500472, ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.4.2 | - | - | - | Phase 2 for UAS, UAV and UAM (UAS_Ph2) | - | - | Docs:=3 | - | |
| 9.4.2 | S2-2500056 | DISCUSSION | Discussion | Integration of Lifi Features in UAS for IoT Application | IIT, Kharagpur | Noted in e-mail session | Stefano (Qualcomm) proposes to note ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 9.4.2 | S2-2500396 | CR | Approval | 23.256 CR0160 (Rel-18, 'D'): Cleaning-up EN | LG Electronics | Rel-18 | Approved | Agreed | |
| 9.4.2 | S2-2500397 | CR | Approval | 23.256 CR0161 (Rel-19, 'A'): Cleaning-up EN | LG Electronics | Rel-19 | Approved | Agreed | |
| 9.5.2 | - | - | - | Ranging based services and sidelink positioning (Ranging_SL) | - | - | Docs:=6 | - | |
| 9.5.2 | S2-2500068 | LS In | Action | LS from SA WG5: Reply LS on Ranging/Sidelink Positioning Charging | SA WG5 (S5-247001) | Rel-19 | Noted in e-mail session | LiMeng (Huawei) prefer to note this document. | Noted |
| 9.5.2 | S2-2500569 | CR | Approval | 23.273 CR0648 (Rel-18, 'F'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-18 | WI Code should be Ranging_SL! r01 agreed. Revised in e-mail session to S2-2501176. | LiMeng (Huawei) provides r01 to correct the work item code. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.5.2 | S2-2501176 | CR | Approval | 23.273 CR0648R1 (Rel-18, 'F'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-18 | Revision of S2-2500569r01. Approved | Agreed | |
| 9.5.2 | S2-2500570 | CR | Approval | 23.273 CR0649 (Rel-19, 'A'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-19 | WI Code should be Ranging_SL! r00 agreed. Revised in e-mail session to S2-2501177. | Revised | |
| 9.5.2 | S2-2501177 | CR | Approval | 23.273 CR0649R1 (Rel-19, 'A'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-19 | Revision of S2-2500570r00. Approved | Agreed | |
| 9.5.2 | S2-2500732 | CR | Approval | 23.586 CR0156 (Rel-18, 'F'): Correction to V2X discovery for Ranging | Vivo | Rel-18 | Approved | Agreed | |
| 9.6.2 | - | - | - | 5GC LoCation Services Phase 3 (eLCS_Ph3) | - | - | Docs:=16 | - | |
| 9.6.2 | - | - | - | LS in | - | - | Docs:=4 | - | |
| 9.6.2 | S2-2500035 | LS In | Information | LS from CT WG1: LS on Requesting allocation of new TCP port for Location Services User Plane Protocol (LCS-UPP) | CT WG1 (C1-247157) | Rel-18 | Noted in e-mail session | Yunjing (CATT) proposes to note the LS. | Noted |
| 9.6.2 | S2-2500010 | LS In | Action | LS from CT WG1: LS on UEs user plane availability status for LCS-UPP | CT WG1 (C1-246023) | Rel-19 | Response drafted in S2-2500733. FInal response in S2-2501178 | Replied to | |
| 9.6.2 | S2-2500733 | LS OUT | Approval | [DRAFT] Reply LS on UE's user plane availability status for LCS-UPP | vivo | Rel-19 | Response to S2-2500010. r00 agreed. Revised in e-mail session to S2-2501178. | Revised | |
| 9.6.2 | S2-2501178 | LS OUT | Approval | Reply LS on UE's user plane availability status for LCS-UPP | SA WG2 | Rel-19 | Revision of S2-2500733r00. Approved | Approved | |
| 9.6.2 | - | - | - | User plane positioning - LMF re-selection | - | - | Docs:=2 | - | |
| 9.6.2 | S2-2500859 | CR | Approval | 23.273 CR0661 (Rel-18, 'F'): Clarification on LMF re-selection of LCS UP positioning | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.6.2 | S2-2500860 | CR | Approval | 23.273 CR0662 (Rel-19, 'A'): Clarification on LMF re-selection of LCS UP positioning | Huawei, HiSilicon | Rel-19 | Approved | Agreed | |
| 9.6.2 | - | - | - | User plane positioning - number of LCS-UPP connections | - | - | Docs:=3 | - | |
| 9.6.2 | S2-2500370 | DISCUSSION | Discussion | Analysis on the number of LCS-UPP connections. | Ericsson | Rel-18 | Noted in e-mail session | Richard (Ericsson) wants to get views of other companies related to rel18. ==== General Revisions Deadline ==== Guanglei (Huawei) provides views ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2500372 | CR | Approval | 23.273 CR0646 (Rel-19, 'F'): Clarify number of user plane connections for user plane positioning | Ericsson | Rel-19 | WI Code should be 5G_eLCS_Ph3! Postponed in e-mail session | Yunjing (CATT) provides comments and r01. Wen (vivo) provides comments on multiple LCS-UPP connections. Guanglei (Huawei) agrees it is meaningful to support multiple LCS UP connections, but asks more questions on r01. Yunjing (CATT) replies to Guanglei (Huawei). Guanglei (Huawei) further asks for clarification. Richard (Ericsson) comments on Yunjing (CATT) principles Guanglei (Huawei) tries to understand the intention and gives a clean solution. Hong (Qualcomm) comments and asks for clarification of the scope of the proposal. Guanglei (Huawei) replies to Yunjing (CATT). Yunjing (CATT) replies to Richard (Ericsson). Richard (Ericsson) is responding to Wen, Wen (vivo) responses to Richard (Ericsson) and asks for clarifications on LCS-UPP connection. Richard (Ericsson) responses to Wen (vivo) and to Hong (Qualcomm) Yaxin (OPPO) provides comments on scenario differentiation. Wen (vivo) provides further comments based on Richard's reply. Richard (Ericsson) responses to Yaxin (OPPO) Richard (Ericsson) replies to Yunjing (CATT) and commenting on r01. Hong (Qualcomm) proposes to postpone the CR to Feb meeting. Richard (Ericsson) replies to Hong (Qualcomm) that on Feb meeting only LS related issues can be handled Hong (Qualcomm) comments that more UE side impacts need to be analyzed. ==== General Revisions Deadline ==== Yunjing (CATT) replies and is fine with r0. Guanglei (Huawei) suggest postpone, although I think it is meaningful to support multiple connections. Richard (Ericsson) proposes to accept r0 if everybody agrees that LCS reallocation issue is independent from multiple connection handling Guanglei (Huawei) replies, not ok with r01, but can live with r0 as I did not find new other impacts at this moment if leave the issue raised by CATT alone. Richard (Ericsson) would like to bring this up on CC#3 since companies started to accept r0 version. Hong (Qualcomm) comments and thinks that more time is needed. Hong (Qualcomm) replies to Richard. Yaxin (OPPO) proposes to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2500371 | CR | Approval | 23.273 CR0645 (Rel-18, 'F'): Clarify number of user plane connections for user plane positioning | Ericsson | Rel-18 | LATE DOC: Not provided. WITHDRAWN | Guanglei (Huawei) proposes to postpone ==== Comments Deadline ==== | Withdrawn |
| 9.6.2 | - | - | - | User plane positioning - paging | - | - | Docs:=1 | - | |
| 9.6.2 | S2-2500694 | CR | Approval | 23.273 CR0655 (Rel-18, 'B'): Supporting of Paging Policy Differentiation for Positioning Service | China Telecom | Rel-18 | WI Code should be 5G_eLCS_Ph3! Noted in e-mail session | Guanglei (Huawei) asks a question Hong (Qualcomm) comments and raises concern on introducing new features for Rel-18. Leo (Deutsche Telekom) objects to this CR. It is not FASMO, and Cat-B CR for R18 is not acceptable. Shabnam (Ericsson) also objects to the CR(s) and indicates that this feature was originally and mainly intended for IMS voice, but general text was used to describe the feature. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.6.2 | - | - | - | User plane positioning - charging | - | - | Docs:=3 | - | |
| 9.6.2 | S2-2500856 | CR | Approval | 23.273 CR0659 (Rel-18, 'F'): Clarification on charging aspects for LCS UP positioning | Huawei, HiSilicon | Rel-18 | Postponed in e-mail session | Hong (Qualcomm) comments and suggests confirming with SA5 first before adding features to SA2. Richard (Ericsson) is sharing Qualcomm's view Stephen (Qualcomm) comments Guanglei (Huawei) Ok to postpone this CR and asks a question Leo (Deutsche Telekom) objects the CR Guanglei (Huawei) replies and ok to Postpone this CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2500857 | CR | Approval | 23.273 CR0660 (Rel-19, 'A'): Clarification on charging aspects for LCS UP positioning | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Leo (Deutsche Telekom) objects the CR Guanglei (Huawei) replies and ok to Postpone this mirror CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2500858 | LS OUT | Approval | [DRAFT] LS on Support of charing for LCS UP positioning | Huawei, HiSilicon | Postponed in e-mail session | Hong (Qualcomm) comments and suggests changes. Leo (Deutsche Telekom) comments and proposes to update the LS. Guanglei (Huawei) postpones this LS and may leave SA5 to discuss. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed | |
| 9.6.2 | - | - | - | Reference and editorial change | - | - | Docs:=3 | - | |
| 9.6.2 | S2-2500373 | CR | Approval | 23.273 CR0647 (Rel-19, 'F'): Move NOTE 2 back to the user plane positioning text | Ericsson | Rel-19 | Approved | Agreed | |
| 9.6.2 | S2-2500974 | CR | Approval | 23.273 CR0663 (Rel-18, 'F'): Emergency SUPL Reference Alignment with 23.271 | Nokia, Nokia Shanghai Bell | Rel-18 | Noted in e-mail session | Guanglei (Huawei) asks a question Stephen (Qualcomm) comments ==== General Revisions Deadline ==== Guanglei (Huawei) agrees with Stephen (Qualcomm) and Not Ok with this CR ==== Comments Deadline ==== | Noted |
| 9.6.2 | S2-2500975 | CR | Approval | 23.273 CR0664 (Rel-19, 'A'): Emergency SUPL Reference Alignment with 23.271 | Nokia, Nokia Shanghai Bell | Rel-19 | Noted in e-mail session | Noted | |
| 9.7.2 | - | - | - | Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | - | - | Docs:=4 | - | |
| 9.7.2 | S2-2500100 | CR | Approval | 23.304 CR0521 (Rel-19, 'A'): Clarification on DNS query during Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay | Huawei, HiSilicon | Rel-19 | Approved | Paul (Ericsson) provides r02. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.7.2 | S2-2500108 | CR | Approval | 23.304 CR0526 (Rel-18, 'F'): Clarification on DNS query during Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.7.2 | S2-2500977 | CR | Approval | 23.304 CR0541 (Rel-18, 'F'): Remote UE emergency location fallback | Nokia, Nokia Shanghai Bell | Rel-18 | Noted in e-mail session | Hong (Qualcomm) comments and OBJECTS the CR. Shabnam (Ericsson) agrees with Qualcomm analysis of the background for the specification as described now. Walter (Philips) supports Simon (Nokia) ==== General Revisions Deadline ==== Hong (Qualcomm) replies to Walter. Walter (Philips) replies to Hong (Qualcomm) ==== Comments Deadline ==== | Noted |
| 9.7.2 | S2-2500978 | CR | Approval | 23.304 CR0542 (Rel-19, 'A'): Remote UE emergency location fallback | Nokia, Nokia Shanghai Bell | Rel-19 | Noted in e-mail session | Hong (Qualcomm) comments and OBJECTS the CR. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.8.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | Docs:=2 | - | |
| 9.8.2 | S2-2500954 | CR | Approval | 23.502 CR5306 (Rel-19, 'F'): Fix wrong implementation of approved TDoc S2-2301807 | Nokia, Huawei, HiSilicon, Ericsson | Rel-19 | Approved | Agreed | |
| 9.8.2 | S2-2500955 | CR | Approval | 23.502 CR5307 (Rel-18, 'F'): Fix wrong implementation of approved TDoc S2-2301807 | Nokia, Huawei, HiSilicon, Ericsson | Rel-18 | Approved | Agreed | |
| 9.9.2 | - | - | - | System Support for AI/ML-based Services (AIMLsys) | - | - | Docs:=0 | - | |
| 9.10.2 | - | - | - | 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | - | - | Docs:=4 | - | |
| 9.10.2 | S2-2500574 | CR | Approval | 23.247 CR0384 (Rel-18, 'F'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised in e-mail session to S2-2501179. | Robbie (Ericsson) is fine with r02 LiMeng (Huawei) provides r02 Robbie (Ericsson) provides r01 Thomas(Nokia) provides r03 Robbie (Ericsson) is fine with r03. LiMeng (Huawei) is fine with r03. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2501179 | CR | Approval | 23.247 CR0384R1 (Rel-18, 'F'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon, Ericsson, Nokia | Rel-18 | Revision of S2-2500574r03. Approved | Agreed | |
| 9.10.2 | S2-2500575 | CR | Approval | 23.247 CR0385 (Rel-19, 'A'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon | Rel-19 | r00 agreed. Revised in e-mail session to S2-2501180. | Robbie (Ericsson) mentions the same changes in 0574 are needed for this mirror CR ==== Comments Deadline ==== | Revised |
| 9.10.2 | S2-2501180 | CR | Approval | 23.247 CR0385R1 (Rel-19, 'A'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon, Ericsson, Nokia | Rel-19 | Revision of S2-2500575r00. Approved | Agreed | |
| 9.11.2 | - | - | - | Network Slicing Phase 3 (eNS_Ph3) | - | - | Docs:=17 | - | |
| 9.11.2 | S2-2500156 | CR | Approval | 23.502 CR5201 (Rel-18, 'F'): Allow NSSF to provide slice validity time during slice selection | Oracle, Verizon | Rel-18 | Postponed in e-mail session | Uri (Oracle) responds to comments from Myungjune (LGE). Myungjune (LGE) provides comments. Jinguo(ZTE) comments Alessio(Nokia) asks question for clarification and comments this may not be FASMO Fenqin(Huawei) agree that this is not a FASMO Iskren (NEC) comments Uri (Oracle) responds to Myungjune (LGE) and shows why the CR is FASMO. Uri (Oracle) responds to Alessio(Nokia) et al showing why the CR should be FASMO Ashok (Samsung) comments on r01 and feels the original approach was better Myungjune (LGE) is ok with r01. Uri (Oracle) replies positively to Myungjune (LGE) and provides r01. Myungjune (LGE) replies to Uri (Oracle). Qian (Ericsson) provides comments Alessio(Nokia) believes the CR does not meet FASMO criteria and either is noted or postponed (postponed if the authors believe we misunderstand the issue as already commented earlier in the thread) Fenqin (Huawei) Provides comments ==== General Revisions Deadline ==== Uri (Oracle) further responds to Fenqin (Huawei) and Qian (Ericsson) Uri (Oracle) responds to Alessio(Nokia), believes at least some of the companies may have misunderstood the issue, and there is a need to postpone the paper. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500157 | CR | Approval | 23.502 CR5202 (Rel-19, 'A'): Allow NSSF to provide slice validity time during slice selection | Oracle, Verizon | Rel-19 | Postponed in e-mail session | Uri (Oracle) provides r01 also for the R19 mirror CR based on r01 of the R18 CR. Alessio(Nokia) believes the CR does not meet FASMO criteria and either is noted or postponed (postponed if the authors believe we misunderstand the issue as already commented earlier in the thread) Uri (Oracle) responds to Alessio(Nokia) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500172 | CR | Approval | 23.501 CR5895 (Rel-18, 'F'): Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon | Rel-18 | Postponed in e-mail session | Uri (Oracle) responds to comments from Myungjune (LGE) and provides r01. Myungjune (LGE) provides comments. Alessio(Nokia) provides comments and proposes rewording as alternative to noting the CR Uri (Oracle) responds to comments from Alessio(Nokia) and provides r02. Fenqin (Huawei) also prefers r01. Myungjune (LGE) prefers r01. Alessio(Nokia) comments that in roaming the slice validity time is set by HPLMN not VPLMN Uri (Oracle) responds to Alessio(Nokia) and Fenqin (Huawei) and June (LG). Provides r03. Uri responds to Qian (Ericsson). Agrees to r04. Qian (Ericsson) provides r04 Alessio(Nokia) cannot agree to r04 as it is confusing to state the AMF determines 'at least one'. We still believe the AMF will receive only one source of info but if we think it is >1 the AMF shall chose at most one ??. The multiple source of info debate should take place .. so we probably need to postpone this. Uri (Oracle) responds to Alessio(Nokia) and Qian (Ericsson) and all. Provides r05. ==== General Revisions Deadline ==== Uri responds to Myungjune (LGE) and agrees to postpone the CR. Myungjune (LGE) proposes to postpone CR. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500180 | CR | Approval | 23.501 CR5899 (Rel-19, 'A'): Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon | Rel-19 | Postponed in e-mail session | Uri (Oracle) provides r01 for the R19 mirror CR based on r04 of the R18 CR (was kindly provided earlier by Qian). Alessio(nokia) cannot agree to r04 CAT-F hence this revision r01 cannot be acceptable ==== General Revisions Deadline ==== Uri (Oracle) responds to Alessio(Nokia) and Qian (Ericsson) and all. OK to postpone ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500665 | DISCUSSION | Endorsement | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia | Rel-18 | Noted in e-mail session | Noted | |
| 9.11.2 | S2-2500686 | CR | Approval | 23.501 CR5987 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia | Rel-18 | Postponed in e-mail session | Myungjune (LGE) provides comments. Qian (Ericsson) provides comments. Jinguo(ZTE) has same view as Qian(Ericsson) Alessio (Nokia) provides replies to comments by Ericsson and LG, stating that we should be able to support always N also when the rel-18 features are introduced, i.e. also for slices that are subject to area restrictions Alessio(Nokia) we do not agree that the concept of Always-on PDU sessions cannot be supported for slices that are supported only in a TA subset of a RA or in area smaller than a TA. We need to resolve the issue. Fenqin (Huawei) also think that if one slice is not supported but we still keep the UP at NG-RAN seems some big change to NG-RAN. Malla (NTT DOCOMO) agrees with Nokia Jinguo(ZTE) provides a solution Qian (Ericsson) provides information related to AMF event subscription from SMF Ashok (Samsung) provides comments Alessio(nokia) comments that based on specs we have the RAN releases the resources when UE exists NS-AoS of slice and askes the network to also release them so the rAN impact is unavolidable to keep the always on session activated. Alessio(nokia) replies to Qian (Ericsson) that the action the SMF takes it to deactivate instead of releasing the PDU session Alessio(nokia) replies to Ashok (Samsung) Ashok (Samsung) clarifies to Alessio(nokia) Jinguo(ZTE) prefer not to impact the RAN at this stage and suggest to postpone. ==== General Revisions Deadline ==== Malla (NTT DOCOMO) agrees with Nokia. Jinguo(ZTE) response to Malla(NTT Docomo) Fenqin (Huawei) also proposes to Postpone or NOTE CR. Myungjune (LGE) proposes to NOTE or postpone CR. Qian (Ericsson) proposes to NOTE the paper. Alessio(Nokia) suggests to postpone and to have offline discussion to resolve the issue while keeping the behavior of always on. Meanwhile CT1 should not proceed to align existing text which is subject to this ongoing discussion ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500687 | CR | Approval | 23.501 CR5988 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT Docomo, Nokia | Rel-19 | Postponed in e-mail session | Qian (Ericsson) indicates this mirror CR and shall be handled the same as 0687 ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500689 | CR | Approval | 23.502 CR5273 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia. | Rel-18 | Postponed in e-mail session | Qian (Ericsson) indicates that comments in 0686 thread are valid for this one as well Alessio indicates to Qian (Ericsson) et all that replies to comments in 0686 thread are valid for this one as well ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500690 | CR | Approval | 23.502 CR5274 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia | Rel-19 | Postponed in e-mail session | Postponed | |
| 9.11.2 | S2-2500868 | CR | Approval | 23.501 CR6018 (Rel-18, 'F'): Clarification on the removal of S-NSSAI from the Configured NSSAI | ZTE, Nokia | Rel-18 | Postponed in e-mail session | Myungjune (LGE) provides comments. Qian (Ericsson) asks for clarification Jinguo(ZTE) response to Qian(Ericsson), Myungjune(LGE), and provide r01 Ashok (Samsung) is not ok with the CR. Does not see the need for the design change to Rel 18 feature and agree with Myungjune (LGE) to continue with existing design Alessio(Nokia) is not ok with the Samsung proposal to store in UDM state about the configured NSSAI as this means storing potentially state for all roaming partners. Alessio (Nokia) replies to Qian (Ericsson) Alessio(Nokia) replies to LGE comments. Myungjune (LGE) replies to Alessio (Nokia). Jinguo(ZTE) asks question for clarification on the UDM solution Ashok (Samsung) provides response to Jinguo(ZTE) Fenqin (Huawei) provides comment Jinguo(ZTE) think the UDM solution doesn't work Qian (Ericsson) asks further questions Ashok (Samsung) responds to Jinguo(ZTE) that for AF triggered slice replacement the solution is UDR based as proposed in 953. The UDM solution is for temporary slice and NS-AoS as no PCF involvement is needed here Ashok (Samsung) provides further comments. Jinguo(ZTE) response to Qian, Jinguo(ZTE) response to Ashok Jinguo(ZTE) asks one question to Myungjune, Alessio(nokia) agrees with Jinguo(ZTE) and clarifies that LG assumption is ' it works in most cases if the serving network still has Context for the UE' . this would not be really acceptable to us especially as we proposed a simple solution that works all the time Alessio(Nokia) would not agree to a solution impacting the UDM if we can have one without any stage three impacts nor impact to UDM like the one ZTE and nokia propose. Myungjune (LGE) replies to Jinguo (ZTE). Alessio(Nokia) simplifies the discussion of this paper based on simple consideration that rel-18 changes stage 3 are needed by UDM based solution keeping configured NSSAI approach in stage two, and Nokia will object this stage 3 change as it would be not a FASMO issue but a new feature proposed by samsing to keep configured NSSAI context in VPLMN in HPLMN UDM. The FASMO issue is solved at stage two level by this CR without need of a new stage three change. Alessio(Nokia) comments that network vendors can remove the context of deregistered UEs based on non-specified policies hence the solution by LG assumes specific context retention policies that are not specified. This does not work all the time and does not work systematically for long term deregistrations. Ashok (Samsung) propose to NOTE this paper and feels there is a need for small WID to address the UE deregistration scenario which affects multiple feature as the proposed solution here is not efficient. Jinguo(ZTE) answers to Myungjune(LGE) Myungjune(LGE) answers to Jinguo(ZTE) Jinguo(ZTE) response to Myungjune(LGE) Myungjune (LGE) comments that using Rejected NSSAI increases signaling. Alessio(Nokia) rejects the notion that CAT-F CR needs a TEI work or even a study. We (ZTE and Nokia) proposed a simple non stage three impacting solution which works, and we will never ever agree to fix this via stage three impacting solution for rel-18 instead. So Samsung excuse they cannot accept a CAT-F that works because they want to submit a different stage three impacting approach which requires a CAT-B CR (otherwise why would Samsung want a WID?) is not viable. We urge SA2 to adopt the ZTE and nokia proposal. Myungjune(LGE) answers to Jinguo(ZTE). Myungjune(LGE) answers to Jinguo (ZTE) Qian (Ericsson) provides comments and suggests to postpone this paper. Alessio(Nokia) disagrees Myungjune (LGE) comments that using Rejected NSSAI increases signaling. Alessio(nokia) reminds Jinguo(ZTE) that we are not discussing AF-requested slice replacement Fenqin (Huawei) provides comments ==== General Revisions Deadline ==== Myungjune (LGE) proposes to NOTE CR. Qian (Ericsson) proposes to postpone the paper. ==== Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2500869 | CR | Approval | 23.501 CR6019 (Rel-19, 'A'): Clarification on the removal of S-NSSAI from the Configured NSSAI | ZTE, Nokia | Rel-19 | Postponed in e-mail session | Postponed | |
| 9.11.2 | S2-2500896 | CR | Approval | 23.501 CR6032 (Rel-18, 'F'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-18 | r03 agreed. Revised in e-mail session to S2-2501181. | Myungjune (LGE) provides comments. Qian (Ericsson) provides comments. Jinguo(ZTE) provides comments and don't see the necessary for this CR. Alessio(Nokia) supports Jinguo(ZTE)'s view Ashok (Samsung) provides response and r01 Jinguo(ZTE) provides comment and suggest a revision Fenqin(Huawei) ask a question for clarification Qian (Ericsson) provides further comments Ashok (Samsung) provides r02 Jinguo(ZTE) provides r03 to remove the first two changes Myungjune (LGE) comments on r03. Ashok (Samsung) requests for clarification from Jinguo(ZTE) on r03 and suggests to proceed with r02 Alessio(Nokia) r03 could be acceptable but we need to fix the text as some lower case allowed NSSAI is there. Ashok (Samsung) ask for clarification. ==== General Revisions Deadline ==== Jinguo(ZTE) responses to Ashok(Samsung) Ashok (Samsung) replies to Jinguo(ZTE) and Alessio (Nokia) Jinguo(ZTE) suggest to agree r03, but the cover page needs to be updated accordingly Jinguo(ZTE) replies to Ashok(Samsung) Qian (Ericsson) prefers to NOTE the paper, but can live with the simple synch with CT1 part which is reflected in r03 Alessio(Nokia) can live with r03 Ashok (Samsung) can live with r03 as majority prefers r03 ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2501181 | CR | Approval | 23.501 CR6032R1 (Rel-18, 'F'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-18 | Revision of S2-2500896r03. Approved | Agreed | |
| 9.11.2 | S2-2500897 | CR | Approval | 23.501 CR6033 (Rel-19, 'A'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-19 | r00 agreed. Revised in e-mail session to S2-2501182. | Ashok (Samsung) provides r01. This is mapping Rel19 CR for 896 Ashok (Samsung) provides r01. This is mapping Rel19 CR for 896 with correct subject line Alessio(Nokia) asks r01 to be noted we can agree only to something aligned withr03 of 896 ==== General Revisions Deadline ==== Ashok (Samsung) comments that it is the mirror CR of 896 and can be approved by aligning r03 of 896. ==== Comments Deadline ==== | Revised |
| 9.11.2 | S2-2501182 | CR | Approval | 23.501 CR6033R1 (Rel-19, 'A'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-19 | Revision of S2-2500897r00. Approved | Agreed | |
| 9.11.2 | S2-2500914 | CR | Approval | 23.502 CR5303 (Rel-18, 'F'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-18 | Noted in e-mail session | Qian (Ericsson) indicates that the comments and discussion in 0896 thread is related to this paper as well Ashok (Samsung) provides r01. This is 23.502 paper in line with the comment on 23.501 paper Alessio(Nokia) sees the CR now is not needed as the alternative slice is in allowed NSSAI as any other slice so no need to single it out. Prefers to note this paper as it is not FASMO ==== General Revisions Deadline ==== Qian (Ericsson) indicates that this paper needs to be NOTED based on the progress in 0896 ==== Comments Deadline ==== | Noted |
| 9.11.2 | S2-2500915 | CR | Approval | 23.502 CR5304 (Rel-19, 'A'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-19 | Noted in e-mail session | Noted | |
| 9.12.2 | - | - | - | XR (Extended Reality) and media services (XRM) | - | - | Docs:=18 | - | |
| 9.12.2 | S2-2500089 | CR | Approval | 23.503 CR1451 (Rel-18, 'F'): Clarification on multi-modal service | ZTE | Rel-18 | Approved | Agreed | |
| 9.12.2 | S2-2500090 | CR | Approval | 23.503 CR1452 (Rel-19, 'A'): Clarification on multi-modal service | ZTE | Rel-19 | Approved | Agreed | |
| 9.12.2 | S2-2500411 | CR | Approval | 23.501 CR5943 (Rel-18, 'F'): Terminology corrections for the support of multimodal services | Ericsson | Rel-18 | Noted in e-mail session | Mike (InterDigital) comments and provides r01 Paul (Ericsson) provides comments and questions. Mike (InterDigital) comments and is ok with r00. Dan(China Mobile) object r00 and r01. Paul (Ericsson) ask for clarification. Dan(China Mobile) not ok with the media terminology. ==== General Revisions Deadline ==== Dan(China Mobile) suggest to note this CR. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2500412 | CR | Approval | 23.501 CR5944 (Rel-19, 'A'): Terminology corrections for the support of multimodal services | Ericsson | Rel-19 | Noted in e-mail session | Mike (InterDigital) suggests discussing this in the 0411 thread and provides r01 Mike (InterDigital) comments that he is ok with r00 based on the discussion in the 0411 thread. Dan (China Mobile) object r00 and r01. ==== General Revisions Deadline ==== Dan (China Mobile) suggest to NOTE this CR. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2500413 | CR | Approval | 23.503 CR1471 (Rel-18, 'F'): Terminology corrections for the support of multimodal services | Ericsson | Rel-18 | Noted in e-mail session | Dan (China Mobile) object r00 . ==== General Revisions Deadline ==== Dan (China Mobile) object this paper . ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2500414 | CR | Approval | 23.503 CR1472 (Rel-19, 'A'): Terminology corrections for the support of multimodal services | Ericsson | Rel-19 | Noted in e-mail session | Dan (China Mobile) object r00 . ==== General Revisions Deadline ==== Dan (China Mobile) object this paper . ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2500483 | CR | Approval | 23.502 CR5246 (Rel-18, 'F'): UL Protocol Description provisioning to SMF from PCF | Samsung | Rel-18 | Approved | Agreed | |
| 9.12.2 | S2-2500484 | CR | Approval | 23.502 CR5247 (Rel-19, 'A'): UL Protocol Description provisioning to SMF from PCF | Samsung | Rel-19 | Approved | Agreed | |
| 9.12.2 | S2-2500707 | CR | Approval | 23.503 CR1280R3 (Rel-18, 'F'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-18 | Revision of S2-2411984. r01 agreed. Revised in e-mail session to S2-2501183. | Mirko (Huawei) provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2501183 | CR | Approval | 23.503 CR1280R4 (Rel-18, 'F'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-18 | Revision of S2-2500707r01. Approved | Agreed | |
| 9.12.2 | S2-2500708 | CR | Approval | 23.503 CR1440R1 (Rel-19, 'A'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-19 | Revision of S2-2411985. r00 agreed. Revised in e-mail session to S2-2501184. | Chunshan(CATT) creates the mirror version r01 for the R19 based on Mirko (Huawei) provided r01 for R18. Georgios (Nokia) OK with r01 but many instances of the word 'optionally' must be removed Chunshan(CATT) will create the new mirror version based on the agreed R18 r01, and this r01 will be dropped. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2501184 | CR | Approval | 23.503 CR1440R2 (Rel-19, 'A'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-19 | Revision of S2-2500708r00. Approved | Agreed | |
| 9.12.2 | S2-2500910 | CR | Approval | 23.503 CR1499 (Rel-18, 'F'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised in e-mail session to S2-2501185. | Mirko (Huawei) provides r01. Dan(China Mobile) provides r03. Uri (Oracle) provides r02. Mirko (Huawei) provides r04. Paul (Ericsson) provides r05. ==== General Revisions Deadline ==== Uri responds to Paul (Ericsson) and agrees to r05. Mirko (Huawei) replies to the comments and suggests to move on with r04. R05 is not acceptable to us. Georgios (Nokia) prefers r04 and proposes to stay with r04. If not possible r05 needs modification as below Georgios (Nokia): Sorry mixed the revisions in my previous email. Prefer r05 and proposes to stay with r05. If not possible r04 needs modifications as below Paul (Ericsson) we prefer r05 and object to r00, r01, r02, r03 ,r04. Paul (Ericsson) replies to Uri. ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2501185 | CR | Approval | 23.503 CR1499R1 (Rel-18, 'F'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon, Oracle | Rel-18 | Revision of S2-2500910r05. Approved | Agreed | |
| 9.12.2 | S2-2500911 | CR | Approval | 23.503 CR1500 (Rel-19, 'A'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon | Rel-19 | r00 agreed. Revised in e-mail session to S2-2501186. | Dan(China Mobile) suggest Mirko to provide a new version based on the discussion in 0910. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.12.2 | S2-2501186 | CR | Approval | 23.503 CR1500R1 (Rel-19, 'A'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon | Rel-19 | Revision of S2-2500911r00. Approved | Agreed | |
| 9.12.2 | S2-2500912 | CR | Approval | 23.501 CR5587R4 (Rel-18, 'F'): Correction on MDBV | Huawei, HiSilicon, Nokia | Rel-18 | Revision of S2-2410787. Noted in e-mail session | Mukesh (MediaTek) supports R01 provided by Paul (Ericsson). ==== General Revisions Deadline ==== Mirko (Huawei) replies to the comments and cannot accept r01. Paul (Ericsson) objects to r00. ==== Comments Deadline ==== | Noted |
| 9.12.2 | S2-2500913 | CR | Approval | 23.501 CR6036 (Rel-19, 'A'): Correction on MDBV | Huawei, HiSilicon, Nokia | Rel-19 | Revision of S2-2410788. Confirm CR Number - CR states 5588! Confirm CR Revision - CR states 3! Noted in e-mail session | Paul (Ericsson) object to this CR in all revisions. ==== Comments Deadline ==== | Noted |
| 9.13.2 | - | - | - | RedCap Phase 2 (NR_RedCAP_Ph2) | - | - | Docs:=0 | - | |
| 9.14.2 | - | - | - | Evolution of IMS multimedia telephony service (NG_RTC) | - | - | Docs:=11 | - | |
| 9.14.2 | S2-2500063 | LS In | Information | LS from SA WG4: Reply LS on request for IMS Data Channel related clarifications | SA WG4 (S4-242073) | Rel-18 | Noted in e-mail session | Leo (Deutsche Telekom) proposes to NOTE the LS, there is no action for SA2 | Noted |
| 9.14.2 | S2-2500064 | LS In | Action | LS from SA WG4: Reply LS on Binding Information | SA WG4 (S4-242110) | Rel-18 | Postponed in e-mail session | Postponed | |
| 9.14.2 | S2-2500640 | CR | Approval | 23.228 CR1559 (Rel-18, 'F'): Clarification on ADC Setup Procedure | ZTE | Rel-18 | WI Code should be NG_RTC! r01 agreed. Revised in e-mail session to S2-2501187. | DongYeon (Samsung) provides comments. Hao (ZTE) provides r01 with the only change of WI code in coversheet. ==== General Revisions Deadline ==== DongYeon (Samsung) is ok with r01. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2501187 | CR | Approval | 23.228 CR1559R1 (Rel-18, 'F'): Clarification on ADC Setup Procedure | ZTE | Rel-18 | Revision of S2-2500640r01. Approved | Agreed | |
| 9.14.2 | S2-2500641 | CR | Approval | 23.228 CR1560 (Rel-19, 'A'): Clarification on ADC Setup Procedure | ZTE | Rel-19 | WI Code should be NG_RTC! r01 agreed. Revised in e-mail session to S2-2501188. | Hao (ZTE) provides r01 with the only change of WI code in coversheet. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2501188 | CR | Approval | 23.228 CR1560R1 (Rel-19, 'A'): Clarification on ADC Setup Procedure | ZTE | Rel-19 | Revision of S2-2500641r01. Approved | Agreed | |
| 9.14.2 | S2-2500792 | DISCUSSION | Discussion | Discussion on DC Application Information mismatches. | Samsung | Rel-19 | Noted in e-mail session | Noted | |
| 9.14.2 | S2-2500980 | CR | Approval | 23.228 CR1394R4 (Rel-18, 'F'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-18 | Revision of S2-2410688. r01 agreed. Revised in e-mail session to S2-2501189. | DongYeon (Samsung) provides comments. Jari (NTT DOCOMO) responds. Rainer (Nokia) proposes changes Jari (NTT DOCOMO) provides r01 Rainer (Nokia) comments ==== General Revisions Deadline ==== DongYeon (Samsung) comments. ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2501189 | CR | Approval | 23.228 CR1394R5 (Rel-18, 'F'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-18 | Revision of S2-2500980r01. Approved | Agreed | |
| 9.14.2 | S2-2500985 | CR | Approval | 23.228 CR1501R2 (Rel-19, 'A'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-19 | Revision of S2-2410689. r01 agreed. Revised in e-mail session to S2-2501190. | Jari (NTT DOCOMO) provides r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.14.2 | S2-2501190 | CR | Approval | 23.228 CR1501R3 (Rel-19, 'A'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-19 | Revision of S2-2500985r01. Approved | Agreed | |
| 9.15.2 | - | - | - | Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | - | - | Docs:=0 | - | |
| 9.16.2 | - | - | - | UPF enhancement for Exposure And SBA (UPEAS) | - | - | Docs:=20 | - | |
| 9.16.2 | S2-2500036 | LS In | Action | LS from CT WG3: LS on handling of Nsmf events targeting anyUe for I-SMF | CT WG3 (C3-246487) | Rel-18 | Responses drafted in S2-2500609, S2-2500866, S2-2500992, S2-2501052. FInal response in S2-2501191 | Laurent (Nokia): provides technical Comments | Replied to |
| 9.16.2 | S2-2500866 | LS OUT | Approval | [DRAFT] LS Response on handling of Nsmf events targeting anyUe for I-SMF | ZTE | Rel-18 | Baseline? Response to S2-2500036. r02 agreed. Revised in e-mail session to S2-2501191. | Yan (China Mobile) proposes to use S2-2500866 as the baseline paper for LS reply and merge S2-2500609, S2-2500992 and S2-2501052 Magnus (Ericsson) proposes to use this as basis for LS reply Laurent (Nokia): does NOT agree with the technical content of this proposed LS out Laurent (Nokia): does NOT agree with the technical content of this proposed LS out. Let's discuss the technical direction (and then which LS to take as a basis) in the thread of 0036 Naman (Samsung) provides comments Jinguo(ZTE) provides response Laurent (Nokia): answers ; Where is it specified that for SMF events we have subscription via UDM only?? Fenqin (Huawei): ask question for clarification Jinguo(ZTE) replies and provide r01 Laurent (Nokia): provides r02 ==== General Revisions Deadline ==== Fenqin (Huawei): is ok with r02 ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501191 | LS OUT | Approval | LS Response on handling of Nsmf events targeting anyUe for I-SMF | SA WG2 | Rel-18 | Revision of S2-2500866r02. Approved | Approved | |
| 9.16.2 | S2-2500609 | LS OUT | Approval | [DRAFT] Response LS on handling of Nsmf events targeting anyUe for I-SMF | Huawei, HiSilicon | Rel-18 | Response to S2-2500036. Noted in e-mail session | Yan (China Mobile) proposes to merge this paper into S2-2500866 Laurent (Nokia): does NOT agree with the technical content of this proposed LS out. let's discuss the technical direction (and then which LS to take as a basis) in the thread of 0036 Fenqin (Huawei) ask Laurent(Nokia) Huazhang(CMCC) provides two options of way forward Fenqin(Huawei) give a feedback Jinguo(ZTE) suggests to use 866 as basis for LS out and Nokia CR 1010 for technique discussion Laurent (Nokia): supports using 0866 as baseline for LS. Answers to Fenqin ==== General Revisions Deadline ==== Fenqin (Huawei): feedback to Laurent(Nokia) Laurent (Nokia): objects to any version of this Tdoc (we consider only 0866 for the LS and 1010 for the CR) ==== Comments Deadline ==== | Noted |
| 9.16.2 | S2-2500992 | LS OUT | Approval | [DRAFT] LS on handling of Nsmf events targeting anyUe for I-SMF | Nokia | Rel-18 | Response to S2-2500036. Noted in e-mail session | Yan (China Mobile) proposes to merge this paper into S2-2500866 ==== General Revisions Deadline ==== Laurent (Nokia): OK to merge ==== Comments Deadline ==== | Noted |
| 9.16.2 | S2-2501052 | LS OUT | Approval | [DRAFT] Reply LS on handling of Nsmf events targeting anyUe for I-SMF | Samsung | Response to S2-2500036. Noted in e-mail session | Yan (China Mobile) proposes to merge this paper into S2-2500866 ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc (we consider only 0866 for the LS and 1010 for the CR) ==== Comments Deadline ==== | Noted | |
| 9.16.2 | S2-2500280 | CR | Approval | 23.502 CR5231 (Rel-18, 'F'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-18 | Confirm Specification Number - CR states 23.501! r01 agreed. Revised in e-mail session to S2-2501192. | Huazhang (China Mobile) ask guidence about how to handle the wrong CR number Maurice Pope (MCC) replies: Please use the normal revisions process, here are new CR numbers: S2-2500281r01: 23.501 CR 6062 S2-2500281r01: 23.501 CR 6063 Huazhang (China Mobile) thank Maurice's help Huazhang (China Mobile) provides r01 to correct the CR number Laurent (Nokia): let's agree on the direction to take in the thread of 0036 first before discussing the CR(s) Jinguo(ZTE) suggest to discuss separately. This CR is not related with the CT3 LS. Huazhang (CMCC) reply to Jinguo Jinguo(ZTE) response to Huazhang ==== General Revisions Deadline ==== Jinguo(ZTE) is ok with r01 and propose that the UPF event exposure service is changed to SMF event exposure service. Huazhang (CMCC) thanks jinguo's understanding, and prefer to go with r01 with changes in newly added wording with: change 'In the case of UPF' to 'In the case of SMF'. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501192 | CR | Approval | 23.501 CR6062 (Rel-18, 'F'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-18 | Revision of S2-2500280r01. Approved | Agreed | |
| 9.16.2 | S2-2500281 | CR | Approval | 23.502 CR5232 (Rel-19, 'A'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-19 | Confirm Specification Number - CR states 23.501! Confirm CR Number - CR states 5231! r02 agreed. Revised in e-mail session to S2-2501193. | Maurice Pope (MCC): Please use the normal revisions process, here are new CR numbers: S2-2500281r01: 23.501 CR 6062 S2-2500281r01: 23.501 CR 6063 Note that the Rel-19 CR should probably be Category A. Huazhang (China Mobile) provides r01 to fix the CR number Yan (China Mobile) provides comment: This is a mirror and depends on the outcome of S2-2500280 Laurent (Nokia): let's agree on the direction to take in the thread of 0036 first before discussing the CR(s); the zip is r01 but the word Tdoc Nr contains r02 Huazhang (cmcc) provides r02, that r01 contains the wrong tdoc ==== General Revisions Deadline ==== Huazhang (CMCC) make alignment of changes in 280 (R18 CRs), and to go with r02 with changes in newly added wording with: change 'In the case of UPF' to 'In the case of SMF'. See the suggestion in 281 provided by jinguo (ZTE) ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501193 | CR | Approval | 23.501 CR6063 (Rel-19, 'A'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-19 | Revision of S2-2500281r02. Approved | Agreed | |
| 9.16.2 | S2-2500594 | CR | Approval | 23.502 CR5258 (Rel-18, 'F'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised in e-mail session to S2-2501194. | Yan (China Mobile) provides comments Zhao (Huawei) replies to Yan (China Mobile). Laurent (Nokia): this CR does not seem to be needed as we specified that the handling Groups of UE is done by the final consumer Naman (Samsung) shares similar view with Nokia Zhao (Huawei) replies to Laurent (Nokia) and Naman (Samsung). Magnus (Ericsson) provides r01 Zhao (Huawei) can also accept r01 and provides r02 with minor cover page change based on r01. ==== General Revisions Deadline ==== Yan (China Mobile) suggests to go with r02 Laurent (Nokia): objects to r00 ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501194 | CR | Approval | 23.502 CR5258R1 (Rel-18, 'F'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-18 | Revision of S2-2500594r02. Approved | Agreed | |
| 9.16.2 | S2-2500595 | CR | Approval | 23.502 CR5259 (Rel-19, 'A'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501195. | Yan (China Mobile) provides comment: This is a mirror and depends on the outcome of S2-2500594 Magnus (Ericsson) provides r01 ==== General Revisions Deadline ==== Yan (China Mobile) suggests to correct the 'clauses affected' in cover paper same with 0594r02 for this mirror CR Zhao (Huawei) can accept r01, which already corrects the 'clause affected' in the cover page. ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501195 | CR | Approval | 23.502 CR5259R1 (Rel-19, 'A'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-19 | Revision of S2-2500595r01. Approved | Agreed | |
| 9.16.2 | S2-2500878 | CR | Approval | 23.502 CR5297 (Rel-18, 'F'): Clarification on subscription of UPF event via I-SMF | ZTE | Rel-18 | Noted in e-mail session | Yan (China Mobile) provides comments Jinguo(ZTE) provides answer to Yan Fenqin (Huawei) provides comments Jinguo(ZTE) replies to Fenqin Yan (China Mobile) replies to Jinguo(ZTE) Jinguo(ZTE) answer to Yan(China Mobile) Laurent (Nokia): provides r01 Jinguo(ZTE) response to Laurent and can't agree r01 Fenqin(Huawei) provides comments. Jinguo(ZTE) answer to Fenqin(Huawei), and provide r02 ==== General Revisions Deadline ==== Fenqin (Huawei) provides further comment. Magnus (Ericsson) objects to this CR Laurent (Nokia): objects to R00 and R02 ==== Comments Deadline ==== | Noted |
| 9.16.2 | S2-2500879 | CR | Approval | 23.502 CR5298 (Rel-19, 'A'): Clarification on subscription of UPF event via I-SMF | ZTE | Rel-19 | Noted in e-mail session | Yan (China Mobile) provides comment: This is a mirror and depends on the outcome of S2-2500878 Magnus (Ericsson) provides comments Jinguo(ZTE) response to Magnus(Ericsson) ==== General Revisions Deadline ==== Magnus (Ericsson) objects to this CR Laurent (Nokia): Shall the same fate as 0878 (mirror) ==== Comments Deadline ==== | Noted |
| 9.16.2 | S2-2501010 | CR | Approval | 23.502 CR5313 (Rel-18, 'F'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-18 | r01 agreed. Revised in e-mail session to S2-2501196. | Jinguo(ZTE) provides comment Fenqin (Huawei) provides comment Jinguo(ZTE) response to Fenqin Yan(China Mobile) suggests to handle this CR depending on the LS out S2-2500866 Laurent (Nokia): answers Fenqin (Huawei): provides r01 ==== General Revisions Deadline ==== Laurent (Nokia): Ok with R00 and R01 Naman (Samsung): Prefers R01 Fenqin (Huawei): let us go r01, and object r00 ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501196 | CR | Approval | 23.502 CR5313R1 (Rel-18, 'F'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-18 | Revision of S2-2501010r01. Approved | Agreed | |
| 9.16.2 | S2-2501011 | CR | Approval | 23.502 CR5314 (Rel-19, 'A'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-19 | Confirm Spec version used - CR states {18.8.0}! Check TEI19 WI Code, if a mirror CR! r01 agreed. Revised in e-mail session to S2-2501197. | Magnus H (Ericsson) provides comments Yan (China Mobile) provides comments: This is a mirror and depends on the outcome of S2-2501011 Yan (China Mobile) provides comments: This is a mirror and depends on the outcome of S2-2501010 Laurent (Nokia): provides r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.16.2 | S2-2501197 | CR | Approval | 23.502 CR5314R1 (Rel-19, 'A'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-19 | Revision of S2-2501011r01. Approved | Agreed | |
| 9.17.2 | - | - | - | Edge Computing Phase 2 (EDGE_Ph2) | - | - | Docs:=18 | - | |
| 9.17.2 | S2-2500225 | CR | Approval | 23.548 CR0272 (Rel-18, 'F'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised in e-mail session to S2-2501198. | Tezcan (Nokia) is not OK with moving NOTE 2 and provides comments. Xinpeng(Huawei) provides r01 and replies to Tezcan (Nokia). Xinpeng(Huawei) responses to Tezcan (Nokia) and provides r02. Tezcan (Nokia) responds to Xinpeng (Huawei). Tezcan (Nokia) provides comments. ==== General Revisions Deadline ==== Xinpeng(Huawei) provides r03. Tezcan (Nokia) can only accept r03 with the following modifications: * Cover page/Reason for change: Remove 'based on SLA with HPLMN. For example, default QoS Flow, and the V-SMF is aware the default QoS flow per TS 29.502' Xinpeng(Huawei) proposes to go with r03. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2501198 | CR | Approval | 23.548 CR0272R1 (Rel-18, 'F'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-18 | Revision of S2-2500225r03. Approved | Agreed | |
| 9.17.2 | S2-2500226 | CR | Approval | 23.548 CR0273 (Rel-19, 'A'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501199. | Xinpeng(Huawei) provides r01. ==== General Revisions Deadline ==== Xinpeng(Huawei) provides r02. Tezcan (Nokia) is OK with r02 with the same proposed modifications on the cover page of the main tdoc 0225r03+. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2501199 | CR | Approval | 23.548 CR0273R1 (Rel-19, 'A'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-19 | Revision of S2-2500226r02. Approved | Agreed | |
| 9.17.2 | S2-2500273 | CR | Approval | 23.548 CR0276 (Rel-18, 'F'): Correction of DNS message handling rule | China Mobile | Rel-18 | Approved | Agreed | |
| 9.17.2 | S2-2500274 | CR | Approval | 23.548 CR0277 (Rel-19, 'A'): Correction of DNS message handling rule | China Mobile | Rel-19 | Approved | Agreed | |
| 9.17.2 | S2-2500496 | CR | Approval | 23.548 CR0285 (Rel-18, 'F'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-18 | Postponed in e-mail session | Haiyang (Huawei) seeks for clarification . Hyesung (Samsung) provides response. Tezcan (Nokia) asks clarification. Huazhang (CMCC) asks clarification. Haiyang (Huawei) provides comments. Hyesung (Samsung) provides responses. Tezcan (Nokia) asks further clarification Hyesung (Samsung) replies to Tezcan Tezcan (Nokia) still has questions on the need Hyesung (Samsung ) replies Hyesung (Samsung ) replies further Tezcan (Nokia) responds ==== General Revisions Deadline ==== Fenqin (Huawei) suggest to postpone this paper. ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2500497 | CR | Approval | 23.548 CR0286 (Rel-19, 'A'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-19 | Postponed in e-mail session | Postponed | |
| 9.17.2 | S2-2500498 | CR | Approval | 23.501 CR5965 (Rel-18, 'F'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-18 | Postponed in e-mail session | Haiyang (Huawei) comments. Tezcan (Nokia) provides similar comments to 0496. Magnus (Ericsson) provides comments Hyesung (Samsung) is fine with Ericsson's suggestion and accordingly provides r01 Tezcan (Nokia) comments as part of 0496 ==== General Revisions Deadline ==== Fenqin (Huawei) suggest to postpone this paper ==== Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2500499 | CR | Approval | 23.501 CR5966 (Rel-19, 'A'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-19 | Postponed in e-mail session | Postponed | |
| 9.17.2 | S2-2500678 | CR | Approval | 23.548 CR0291 (Rel-18, 'F'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-18 | r00 agreed. Revised in e-mail session to S2-2501200. | Haiyang (Huawei) provides clarification. Tezcan (Nokia) provides comments and asks for clarification. Haiyang (Huawei) provides further clarification. Tezcan (Nokia) asks further clarification Tezcan (Nokia) provides further comments Haiyang (Huawei) provides response. ==== General Revisions Deadline ==== Tezcan (Nokia) responds Haiyang (Huawei). Tezcan (Nokia) only accepts the change 'This may trigger step 2 of Figure 6.2.3.3-1.' in r00. Otherwise, objects this CR. ==== Comments Deadline ==== | Revised |
| 9.17.2 | S2-2501200 | CR | Approval | 23.548 CR0291R1 (Rel-18, 'F'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-18 | Revision of S2-2500678r00. Approved | Agreed | |
| 9.17.2 | S2-2500679 | CR | Approval | 23.548 CR0292 (Rel-19, 'A'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-19 | r00 agreed. Revised in e-mail session to S2-2501201. | Revised | |
| 9.17.2 | S2-2501201 | CR | Approval | 23.548 CR0292R1 (Rel-19, 'A'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-19 | Revision of S2-2500679r00. Approved | Agreed | |
| 9.17.2 | S2-2500680 | CR | Approval | 23.502 CR5269 (Rel-18, 'F'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-18 | Noted in e-mail session | Tezcan (Nokia) provides similar comments to 0496. ==== General Revisions Deadline ==== Tezcan (Nokia) objects to this CR (r00) based on the clarification provided for 0678. ==== Comments Deadline ==== | Noted |
| 9.17.2 | S2-2500681 | CR | Approval | 23.502 CR5270 (Rel-19, 'A'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 9.17.2 | S2-2501053 | CR | Approval | 23.502 CR5326 (Rel-18, 'F'): Correction on HR-SBO allowed indication and AF TI container transfer | Nokia | Rel-18 | Approved | Haiyang (Huawei) comments. Hyesung (Samsung) comments to Haiyang's comment. Haiyang (Huawei) further comments. Hyesung (Samsung) asks further question. Tezcan (Nokia) replies to Huawei and Samsung. Haiyang (Huawei) replies. ==== General Revisions Deadline ==== Hyesung (Samsung) is ok to go with r00. ==== Comments Deadline ==== | Agreed |
| 9.17.2 | S2-2501054 | CR | Approval | 23.502 CR5327 (Rel-19, 'A'): Correction on HR-SBO allowed indication and AF TI container transfer | Nokia | Rel-19 | Approved | Agreed | |
| 9.18.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | Docs:=0 | - | |
| 9.19.2 | - | - | - | Vehicle Mounted Relays (VMR) | - | - | Docs:=0 | - | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) | - | - | Docs:=4 | - | |
| 9.20.2 | S2-2500740 | CR | Approval | 23.316 CR2147 (Rel-18, 'F'): R18 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised in e-mail session to S2-2501202. | Laurent (Nokia): provides r01 Yishan (Huawei) responds to Laurent (Nokia) Laurent (Nokia): answers Yishan (Huawei) responds to Laurent (Nokia) and is ok with r01 Myungjune (LGE) comments. Yishan (Huawei) is ok with r02 Laurent (Nokia): provides r02 Stefan (Ericsson) provides r03 ==== General Revisions Deadline ==== Laurent (Nokia): has a strong preference for R02/R03 Yishan (Huawei) proposes to agree R03. ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2501202 | CR | Approval | 23.316 CR2147R1 (Rel-18, 'F'): R18 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon, Nokia, Ericsson | Rel-18 | Revision of S2-2500740r03. Approved | Agreed | |
| 9.20.2 | S2-2500741 | CR | Approval | 23.316 CR2148 (Rel-19, 'F'): R19 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501203. | Laurent (Nokia): provides r01 Yishan (Huawei) responds to Laurent (Nokia) Laurent (Nokia): answers Yishan (Huawei) responds to Laurent (Nokia) and provides r02 Laurent (Nokia): Lazy Laurent thanks Yishan for the R02, I am ok with it. Stefan (Ericsson) comments Yishan (Huawei) is ok with r03 Laurent (Nokia): provides r03 ==== General Revisions Deadline ==== Laurent (Nokia): has a strong preference for R03 Yishan (Huawei) proposes to agree R03 ==== Comments Deadline ==== | Revised |
| 9.20.2 | S2-2501203 | CR | Approval | 23.316 CR2148R1 (Rel-19, 'F'): R19 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon, Nokia, Ericsson | Rel-19 | Revision of S2-2500741r03. Approved | Agreed | |
| 9.21 | - | - | - | Stage 2 of MPS_WLAN (MPS_WLAN) | - | - | Docs:=0 | - | |
| 9.22.2 | - | - | - | 5G AM Policy (AMP) | - | - | Docs:=0 | - | |
| 9.23.2 | - | - | - | Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | - | - | Docs:=4 | - | |
| 9.23.2 | S2-2500091 | CR | Approval | 23.288 CR1307 (Rel-18, 'F'): Correction on ML Model monitoring service operation | ZTE | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2500092 | CR | Approval | 23.288 CR1308 (Rel-19, 'A'): Correction on ML Model monitoring service operation | ZTE | Rel-19 | Approved | Agreed | |
| 9.23.2 | S2-2500093 | CR | Approval | 23.288 CR1309 (Rel-18, 'F'): Implement agreed ML Model update parameter | ZTE | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2500094 | CR | Approval | 23.288 CR1310 (Rel-19, 'A'): Implement agreed ML Model update parameter | ZTE | Rel-19 | Approved | Agreed | |
| 9.24.2 | - | - | - | Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | - | - | Docs:=0 | - | |
| 9.25.2 | - | - | - | Enhancement of 5G UE Policy (eUEPO) | - | - | Docs:=11 | - | |
| 9.25.2 | S2-2500181 | CR | Approval | 23.503 CR1314R3 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson | Rel-18 | Revision of S2-2409501. r01 agreed. Revised in e-mail session to S2-2501204. | Josep (Deutsche Telekom) co-signs (the mirror as well) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2501204 | CR | Approval | 23.503 CR1314R4 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson, Deutsche Telekom | Rel-18 | Revision of S2-2500181r01. Approved | Agreed | |
| 9.25.2 | S2-2500184 | CR | Approval | 23.503 CR1315R2 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson | Rel-19 | Revision of S2-2408923. r01 agreed. Revised in e-mail session to S2-2501205. | Uri (Oracle) clarifies to Wanqiang (VC) that r01 was uploaded on the first day of the meeting. Uri (Oracle) clarifies to Wanqiang (VC) (this time with the proper AI - thanks Alessio..) that r01 was uploaded on the first day of the meeting. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2501205 | CR | Approval | 23.503 CR1315R3 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson, Deutsche Telekom | Rel-19 | Revision of S2-2500184r01. Approved | Agreed | |
| 9.25.2 | S2-2500234 | CR | Approval | 23.502 CR5214 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-18 | r01 agreed. Revised in e-mail session to S2-2501206. | Josep (Deutsche Telekom) co-signs (the mirror as well) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2501206 | CR | Approval | 23.502 CR5214R1 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson, Deutsche Telekom | Rel-18 | Revision of S2-2500234r01. Approved | Agreed | |
| 9.25.2 | S2-2500235 | CR | Approval | 23.502 CR5215 (Rel-19, 'F'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-19 | Revised to S2-2500415 | Revised | |
| 9.25.2 | S2-2500415 | CR | Approval | 23.502 CR5215R1 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-19 | Revision of S2-2500235. r01 agreed. Revised in e-mail session to S2-2501207. | Uri (Oracle) clarifies to Wanqiang (VC) that r01 was uploaded on the first day of the meeting. Uri (Oracle) clarifies to Wanqiang (VC) (this time with the proper AI - thanks Alessio..) that r01 was uploaded on the first day of the meeting. ==== Comments Deadline ==== | Revised |
| 9.25.2 | S2-2501207 | CR | Approval | 23.502 CR5215R2 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson, Deutsche Telekom | Rel-19 | Revision of S2-2500415r01. Approved | Agreed | |
| 9.25.2 | S2-2500562 | CR | Approval | 23.503 CR1481 (Rel-18, 'F'): URSP Guidelines updates of GSMA | Nokia | Rel-18 | Approved | Haiyang (Huawei) seeks for clarification. Srinivas (Nokia) provides clarification Haiyang (Huawei) comments that NG.135 has already referred to NG.141. Srinivas (Nokia) clarifies to Haiyang indicating that the GSMA decided not to discuss TC in 135, but in 141 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 9.25.2 | S2-2500584 | CR | Approval | 23.503 CR1484 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | Approved | Agreed | |
| 9.26.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | Docs:=0 | - | |
| 9.27.2 | - | - | - | Extensions to the TSC Framework to support DetNet (DetNet) | - | - | Docs:=4 | - | |
| 9.27.2 | S2-2500421 | CR | Approval | 23.501 CR5949 (Rel-18, 'F'): Updated reference for DetNet RFC | Ericsson | Rel-18 | Approved | Agreed | |
| 9.27.2 | S2-2500422 | CR | Approval | 23.501 CR5950 (Rel-19, 'A'): Updated reference for DetNet RFC | Ericsson | Rel-19 | Approved | Agreed | |
| 9.27.2 | S2-2500423 | CR | Approval | 23.503 CR1473 (Rel-18, 'F'): Updated reference for DetNet RFC | Ericsson | Rel-18 | Approved | Agreed | |
| 9.27.2 | S2-2500424 | CR | Approval | 23.503 CR1474 (Rel-19, 'A'): Updated reference for DetNet RFC | Ericsson | Rel-19 | Approved | Agreed | |
| 9.28.2 | - | - | - | Seamless UE context recovery (SUECR) | - | - | Docs:=0 | - | |
| 9.29 | - | - | - | Multiple location report for MT-LR Immediate Location Request for regulatory services (TEI18_MLR) | - | - | Docs:=0 | - | |
| 9.30 | - | - | - | Secondary DN Authentication and authorization in EPC IWK cases (TEI18_SDNAEPC) | - | - | Docs:=0 | - | |
| 9.31 | - | - | - | MBS support for V2X services (TEI18_MBS4V2X) | - | - | Docs:=0 | - | |
| 9.32 | - | - | - | Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) | - | - | Docs:=0 | - | |
| 9.33 | - | - | - | Enhancement of application detection event exposure (TEI18_ADEE) | - | - | Docs:=0 | - | |
| 9.34 | - | - | - | General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) | - | - | Docs:=0 | - | |
| 9.35 | - | - | - | New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18_DCAMP_Ph2) | - | - | Docs:=0 | - | |
| 9.36 | - | - | - | Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | - | - | Docs:=0 | - | |
| 9.37 | - | - | - | Generic Rel-18 LSs | - | - | Docs:=0 | - | |
| 9.38 | - | - | - | Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=0 | - | |
| 19 | - | - | - | Rel-19 SIDs and WIDs | - | - | Docs:=0 | - | |
| 19.1.1 | - | - | - | Study on Integration of satellite components in the 5G architecture Phase III (FS_5GSAT_Ph3_ARCH) | - | - | Docs:=0 | - | |
| 19.1.2 | - | - | - | Integration of satellite components in the 5G architecture Phase III (5GSAT_Ph3-ARC) | - | - | Docs:=91 | - | |
| 19.1.2 | - | - | - | KI#2 Support of S&F satellite operation | - | - | Docs:=0 | - | |
| 19.1.2 | - | - | - | General LS | - | - | Docs:=7 | - | |
| 19.1.2 | S2-2500062 | LS In | Action | LS from SA WG3-LI: Reply LS on FS_5GSAT_Ph3_ARCH conclusions | SA WG3-LI (S3i240703) | Rel-19 | Response drafted in S2-2500760. Copy of S2-2500019. WITHDRAWN | Withdrawn | |
| 19.1.2 | S2-2500019 | LS In | Action | LS from SA WG3-LI: Reply LS on FS_5GSAT_Ph3_ARCH conclusions | SA WG3-LI (S3i240703) | Rel-19 | Responses drafted in S2-2500506, S2-2500760, S2-2501033. FInal response in S2-2501085 | Replied to | |
| 19.1.2 | S2-2500760 | LS OUT | Approval | [DRAFT] Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | China Telecommunications | Rel-19 | Response to S2-2500019. r03 agreed. Revised in e-mail session to S2-2501085, merging S2-2500506 and S2-2501033 | Haris(Qualcomm) comments Yuxin(Xiaomi) comments Lalith(Samsung) comments Lalith (Samsung) is Ok with Hucheng(CATT) proposal Hucheng (CATT) comments Heng(China Telecom) agree Lalith(Samsung) comments Haris(Qualcomm) provides r01 Heng(China Telecom) provides r02 on r01 Stefan (Ericsson) provides r03 ==== General Revisions Deadline ==== Heng (China Telecom) is ok with r03 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501085 | LS OUT | Approval | Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | SA WG2 | Rel-19 | Revision of S2-2500760r03, merging S2-2500506 and S2-2501033. Approved | Approved | |
| 19.1.2 | S2-2500506 | LS OUT | Approval | [DRAFT] Reply LS to s3i240703 | Xiaomi | Rel-19 | Merge into S2-2500760? Response to S2-2500019. Merged into S2-2501085 | Haris(Qualcomm) suggests to merge in S2-2500760 and handle the response under one thread ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2501033 | LS OUT | Approval | [DRAFT] Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | Samsung | Rel-19 | Merge into S2-2500760? Revision of S2-2412294. Response to S2-2500019. Merged into S2-2501085 | Haris(Qualcomm) suggests to merge in S2-2500760 and handle the response under one thread Lalith(Samsung) agrees to merge in S2-2500760 and handle the response under one thread ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500761 | CR | Approval | 23.401 CR3865 (Rel-19, 'B'): New features in Split MME architecture to support requirement of SA WG3_LI | China Telecom | Rel-19 | Noted in e-mail session | Haris(Qualcomm) objects to the CR Heng(China Telecom) think the CR is needed Stefan (Ericsson) agrees with Haris (Qualcomm) that this CR is not needed Yuxin (Xiaomi) comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.1.2 | - | - | - | Issue#2a: List of satellite ID and S&F monitoring list | - | - | Docs:=23 | - | |
| 19.1.2 | S2-2500979 | DISCUSSION | Discussion | On the purpose and criticality of the List of Satellite IDs and S&F Monitored List and proposal to specify separate lists. . | Sateliot, Thales, Novamint | Rel-19 | Noted in e-mail session | Noted | |
| 19.1.2 | S2-2500780 | DISCUSSION | Approval | S&F Monitoring List and transition between S&F mode and normal mode | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 19.1.2 | S2-2501025 | DISCUSSION | Discussion | Discussion on List of satelliteID(s). | Samsung | Rel-19 | Noted in e-mail session | Noted | |
| 19.1.2 | S2-2500136 | DISCUSSION | Approval | On the use of monitoring list and wait time for S&F. | Qualcomm Incorporated | Rel-19 | Noted in e-mail session | Noted | |
| 19.1.2 | S2-2500972 | CR | Approval | 23.401 CR3874 (Rel-19, 'B'): Support for S&F Serving Satellite List and S&F Monitoring Satellite List | Sateliot, Novamint, Thales | Rel-19 | Noted in e-mail session | Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500782 | CR | Approval | 23.401 CR3867 (Rel-19, 'B'): Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon | Rel-19 | Option B baseline? Part on issue#2b, to be merged into S2-2501041? WI Code should be 5GSAT_Ph3-ARC! CC#4: r16 + changes agreed. Revised in e-mail session to S2-2501339, merging S2-2500179, S2-2500321, S2-2500525, S2-2500548, S2-2500619, S2-2500688, S2-2500723, S2-2500728, S2-2500779 and S2-2501028 | Steve (Huawei) provides r01 Lalith (Samsung) comments on r01 Haris(Qualcomm) provides r02 Wen(vivo) provides comment and r03. Kundan(NEC) provides comment. Carlson (MediaTek) comments and provides r04. Boren (OPPO) comments. Ramon (Sateliot) comments and provides r05. Lalith (Samsung) comments on deviating from r01. Steve (Huawei) provides a list of small aspects to be resolved Ramon (Sateliot) concurs with Lalith's (Samsung) view. Haris(Qualcomm) comments on r05 Haris(Qualcomm) responds that r01 is not acceptable Ramon (Sateliot) replies to Haris(Qualcomm). OPPO (Boren) provides comment. Hucheng (CATT) comments Yuxin (Xiaomi) comments to r07 Baixiao (CATT) comments. Wen (vivo) provides r07 Steve (Huawei) provides r06 Lalith(Samsung) provides r08 and r09. Boren (OPPO) provides comments on r08, 09. Ramon (Sateliot) comments on r08 and r09 and proposes to complement the description of the S&F Monitoring List from NW side. Lalith(Samsung) clarifies to Boren (OPPO) I can live with r08 Haris(Qualcomm) objects to r08, r09 Carlson (MediaTek) comments on r08 and r09 Stefan (Ericsson) comments on r08 and r09 Wen (vivo) comments on r08 and r09 Steve (Huawei) provides r10 Lalith(Samsung) replies to Ramon (Sateliot) Lalith(Samsung) replies to Kudan. Haris(Qualcomm) asks question on the NOTE B Lalith(Samsung) replies to Carlson (MediaTek) Steve (Huawei) replies about note B Saubhagya (Nokia) not convinced with the note and asks for clarification Lalith(Samsung) replies to Stefan (Ericsson) Lalith(Samsung) provides r11 Saubhagya (Nokia) questions on r11 Ramon(Sateliot) replies to Lalith(Samsung) Steve (Huawei) comments on shortening the note Haris(Qualcomm) comments that does not see value in NOTE B after the explanation Ramon (Sateliot) replies about note B Lalith(Samsung) replies questions on r11 Lalith(Samsung) replies to Ramon. Yuxin(Xiaomi) comments NOTE B is not needed Saubhagya (Nokia) asks further questions on MME behaviour during integrity failure Lalith (Samsung) comments. Lalith(Samsung) replies to questions on MME behaviour during integrity failure Saubhagya (Nokia) points out the existing normative text will suffice Steve (Huawei) comments on the reasons for the note Carlson (MediaTek) comments and provide r12 based on r10 Lalith(Samsung) clarifies again to Carlson (MediaTek) Carlson (MediaTek ) responds to Lalith (Samsung), provides r13 based on r11 Haris(Qualcomm) proposes text for a NOTE B Steve (Huawei) provides r14 Lalith (Samsung) replies to Carlson (MediaTek ) Stefan (Ericsson) provides r15 Haris(Qualcomm) asks question on r14/r15 ==== General Revisions Deadline ==== Carlson (MediaTek ) thinks Lalith (Samsung) explaination clarify the doubt. Lalith(Samsung) can live with NOTE. Carlson (MediaTek) is okay with Wen (vivo) proposal: keep original positive way texts & add new negative way texts. Wen (vivo) proposes go with r15+undo change for S&F wait timer on original text Boren (OPPO) is ok with r15+undo change for S&F wait timer on original text Ramon (Sateliot) comments on NOTE B and makes further proposal. Carlson (MediaTek) comments to Ramon (Sateliot) further proposal and suggest to postpone this CR. Haris(Qualcomm) suggests also to postpone the CR Haris(Qualcomm) is ok with r15+undo change for S&F wait timer on original text Ramon (Sateliot) fixes an error in the text of previous proposal Steve (Huawei) we should not postpone, is ok with r15 + reverting changes to the paragraph below note 3 (aka undo change for S&F wait timer on original text) Lalith(Samsung) suggests also to postpone the CR Steve (Huawei) comments that Lalith(Samsung) is commenting on problems with the Split MME in general and not this CR. Lalith(Samsung) clarifies to Steve (Huawei). Ramon(Sateliot) replies to Steve (Huawei). Carlson (MediaTek) try to clarify why postpone is needed Lalith(Samsung) agrees with explanation from Carlson (MediaTek) Steve (Huawei) The issue described is not related to the CR, it occurs with or without it. Thierry (Novamint) share the same views of Ramon (Sateliot) and supports to adopt one of the 3 proposals brought by Ramon (Sateliot) Carlson (MediaTek) thinks the issue described is related to S&F List decision SoH result To have progress, Carlson (MediaTek) can barely live with (1) r15 + (2) undo change for S&F wait timer on original text + (3) an EN as proposed by Ramon (Sateliot) proposal 3. Steve (Huawei) will live with r15 + reverting changes to the paragraph below note 3 (aka undo change for S&F wait timer on original text) + and the EN 'It is for further consideration whether specific UE behaviour or clarification in a NOTE needs to be added to prevent the UE from accessing satellites where the NW is not expected to keep a UE context.' ==== Comments Deadline ==== Lalith(Samsung) insists to postpone. Clearly we need more time to work on this text. Haris(Qualcomm) proposes to agree r15 + reverting changes to the paragraph below note 3 (aka undo change for S&F wait timer on original text) + and the EN 'It is for further consideration whether specific UE behaviour or clarification in a NOTE needs to be added to prevent the UE from accessing satellites where the NW is not expected to keep a UE context. | Revised |
| 19.1.2 | S2-2501339 | CR | Approval | 23.401 CR3867R1 (Rel-19, 'B'): Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon, Samsung | Rel-19 | Revision of S2-2500782r16 + changes, merging S2-2500179, S2-2500321, S2-2500525, S2-2500548, S2-2500619, S2-2500688, S2-2500723, S2-2500728, S2-2500779 and S2-2501028. This CR was agreed | Agreed | |
| 19.1.2 | S2-2500525 | CR | Approval | 23.401 CR3852 (Rel-19, 'B'): Support of S&F Monitoring List | Nokia | Rel-19 | Option B: merge into 00782 directly? Merged into S2-2501339 | Hucheng (CATT) proposes to mark this paper as merged into 0782, and then NOTE this paper ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500548 | CR | Approval | 23.401 CR3853 (Rel-19, 'B'): Resolving an EN about List of satelliteID(s) and S&F Monitoring List | LG Electronics | Rel-19 | Option B: merge into 00782 directly? Merged into S2-2501339 | Hucheng (CATT) proposes to mark this paper as merged into 0782, and then NOTE this paper ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500723 | CR | Approval | 23.401 CR3858 (Rel-19, 'B'): S&F list handling for EN resolving | Vivo | Rel-19 | Option B: merge into 00782 directly? WI Code should be 5GSAT_Ph3-ARC! Merged into S2-2501339 | Hucheng (CATT) proposes to mark this paper as merged into 0782, and then NOTE this paper ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500179 | CR | Approval | 23.401 CR3845 (Rel-19, 'B'): Update Introduction of Store and Forward feature in EPC | China Mobile | Rel-19 | Option B: focus on what S&F Wait Timer is WI Code should be 5GSAT_Ph3-ARC! Merged into S2-2501339 | Dan(China Mobile) would like to merge this paper into S2-2500782. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500619 | CR | Approval | 23.401 CR3856 (Rel-19, 'B'): Support of S&F Monitoring list and S&F Wait Timer | OPPO | Rel-19 | Option B: focus on how to use S&F Wait timer Merged into S2-2501339 | Steve (Huawei) comments on handling Boren (OPPO) proposes to merge this into 0782. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500688 | CR | Approval | 23.401 CR3857 (Rel-19, 'B'): S&F monitoring list | Xiaomi | Rel-19 | Option B: focus on how to use S&F Wait timer WI Code should be 5GSAT_Ph3-ARC! Merged into S2-2501339 | Steve (Huawei) Should this be merged with 0782? ==== General Revisions Deadline ==== Carlson (MediaTek) also think this CR to be merged to 0782 ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500779 | CR | Approval | 23.401 CR3866 (Rel-19, 'B'): Handling of List of Satellite IDs for S&F satellite operation | CATT | Rel-19 | Option B: focus valid time for the S&F satellite list. Merge procedure part merged into S2-2500726? Merged into S2-2501339 | Carlson (MediaTek) comments Baixiao (CATT) provides clarification. Wen (vivo) comments. Baixiao (CATT) provides clarification on the valid time of the list of satellite IDs. Steve (Huawei) We can assume the MME is able to manage timers, PSM and the S&F monitoring list. Baixiao (CATT) replies to Steve. Carlson (MediaTek) responds to Baixiao (CATT)'s clarification. Baixiao (CATT) proposes to merge this CR into 0782. Haris(Qualcomm) suggest this should be merged in 0782. It is not agreeable in present form ==== General Revisions Deadline ==== Carlson (MediaTek) suggest this should be merged in 0782. ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2501028 | CR | Approval | 23.401 CR3877 (Rel-19, 'B'): Handling list of satellite IDs (Opt-2) | Samsung | Rel-19 | Option B: focus on proposal for UE initiated service request and MME initiated Detach procedures Merged into S2-2501339 | Steve (Huawei) comments Kundan (NEC) asks question. Kundan (NEC) clarifies that NEC question was meant for S2-2500782. Wrongly sent on this. Stephen (Qualcomm) comments Lalith (Samsung) replies to Kundan(NEC) Ramon (Sateliot) comments Kundan (NEC) replies to Lalith(Samsung) Lalith(Samsung) replies to Kundan (NEC) Lalith (Samsung) accepts that this can be considered merged to 0782. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500728 | CR | Approval | 23.401 CR3863 (Rel-19, 'B'): Some clarifications on S&F timer and S&F list usage | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Merged into S2-2501339 | Steve (Huawei) How to handle this CR? Wen (vivo) replies and is ok to merge to 0782 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2501026 | CR | Approval | 23.401 CR3876 (Rel-19, 'B'): Handling list of satellite IDs (Opt-1) | Samsung | Rel-19 | Noted in e-mail session | Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500137 | CR | Approval | 23.401 CR3844 (Rel-19, 'B'): Support for S&F Monitoring List and Wait Timer | Qualcomm Incorporated | Rel-19 | Confirm CR Number - CR states 3804! Noted in e-mail session | Carlson (MediaTek) comments Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500726 | CR | Approval | 23.401 CR3861 (Rel-19, 'B'): Procedure updates for S&F | Vivo | Rel-19 | Baseline for introducing S&F monitoring list in procedures WI Code should be 5GSAT_Ph3-ARC! CC#4: r03 agreed. Revised in CC#4 to S2-2501340, merging S2-2500783 | Wen (vivo) provides an r01 as baseline to merge S2-2500783 and S2-2500779 Steve (Huawei) is ok with r01 Leo (Deutsche Telekom) comments that also in r1 the cover sheet still has the wrong Work Item code. It should be 5GSAT_Ph3-ARC Wen (vivo) provides r02 and r03, r02 just correct the WI code to 5GSAT_Ph3-ARC, r03 remove the changes in clause 5.3.4B.2 as it is conflict with S2-2500947 and correct the WI code to 5GSAT_Ph3-ARC, we can further discuss it in S2-2500947 for final revision selection. Haris(Qualcomm) comments that this CR has dependency on 0782 and should only be agreed if agreed description of S&F Monitoring Lists is agreed through some 0782 revision Lalith(Samsung) agrees that this CR has dependency on 0782 and should only be agreed if agreed description of S&F Monitoring Lists is agreed through some 0782 revision ==== General Revisions Deadline ==== Saubhagya (Nokia) OK with R03 Wen (vivo) proposes to go with r03 (i.e., exclude the changes in 5.3.4B.2 as there is concerns in 0947 ) if 0872 is agreed, but also ok with r02 Leo (Deutsche Telekom) is OK with R03 Chris (Vodafone) says in clean up of R03, REMOVE rather than delete sections that are not meant to be changed, please! Steve (Huawei) prefers r02, but is ok with r03. Stefan (Ericsson) proposes to go with r03 (if a revision of 0782 is agreed) ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501340 | CR | Approval | 23.401 CR3861R1 (Rel-19, 'B'): Procedure updates for S&F | Vivo, Huawei, HiSilicon | Rel-19 | Revision of S2-2500726r03, merging S2-2500783. This CR was agreed | Agreed | |
| 19.1.2 | S2-2500783 | CR | Approval | 23.401 CR3868 (Rel-19, 'B'): Procedure updates to support S&F Monitoring List | Huawei, HiSilicon | Rel-19 | Merge into S2-2500726? Merged into S2-2501340 | Wen (vivo) comments: as Rapporteur suggested in the agenda, this paper can be merged into S2-2500726 Steve (Huawei) is ok with the merge to S2-2500726 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500047 | LS In | Action | LS from RAN WG2: LS on Satellite IDs for store-and-forward operation | RAN WG2 (R2-2411197) | Rel-19 | Responses drafted in S2-2500138, S2-2500505, S2-2500538, S2-2500549, S2-2500634, S2-2500729, S2-2500781, S2-2500790, S2-2501035. CC#4: Postponed | Postponed | |
| 19.1.2 | S2-2500790 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | CATT | Rel-19 | Baseline Response to S2-2500047. CC#4: Postponed | Dario (Session Chair): this LS will be updated to align with the way forward decided in CC#1 Yingying Liu(CATT) provides r02 Leo (Deutsche Telekom) asks Yingying Liu to provide a new revision with the correct Work Item code, which is 5GSAT_Ph3-ARC Haris(Qualcomm) provides r03 Saubhagya (Nokia) agrees with r03 Lalith (Samsung) provides r05. Boren (OPPO) is OK with r04. Wen (vivo) agrees with Qualcomm's text (in r03 and r04). Jaewoo (LGE) provides r04. Stefan (Ericsson) provides r06 Saubhagya (Nokia) agrees with r06 Haris(Qualcomm) can be ok with r06 but misses the UE behaviour Stefan (Ericsson) replies to Haris Lalith(Samsung) comments Stefan (Ericsson) replies to Lalith Lalith(Samsung) replies to Stefan (Ericsson) ==== General Revisions Deadline ==== Lalith(Samsung) is also ok with r06. But note that this tdoc should be approved only if revision of S2-2500782 is agreed - as this is attached in the LS. If no revision of 0782 is agreed this tdoc should be noted. Wen(vivo) is ok with r06 Saubhagya (Nokia) OK with R06 and this LS can be sent only if 0782 is agreed Boren (OPPO) is also ok with r06. Yingying (CATT) is OK with r06. Leo (Deutsche Telekom) is OK with r06. Steve (Huawei) is ok with r06. Yingying (CATT) is OK with r06. If the revision of 0782 is agreed, this t-doc can be sent. If the revision of 0782 is postponed, this t-doc can also be postponed. ==== Comments Deadline ==== | Postponed |
| 19.1.2 | - | - | - | Issue#2b: Expected UE and network behaviour for mode transition | - | - | Docs:=6 | - | |
| 19.1.2 | S2-2501041 | CR | Approval | 23.401 CR3881 (Rel-19, 'C'): Transition between S&F Mode and Normal Mode | Qualcomm Incorporated | Rel-19 | Baseline WI Code should be 5GSAT_Ph3-ARC! Not handled at CC#4. Postponed | Saubhagya (Nokia) provides comments Carlson (MediaTek) comments Ellen (Google) provides comments Wen (vivo) provides comments Stephen (Qualcomm) replies to comments Hucheng (CATT) comments Steve (Huawei) We need to decide how much detail we want overall. The current form of the CR contains unacceptable content (as discussed many times before in previous meetings) that needs to be removed. Stefan (Ericsson) provides comments Yuxin (Xiaomi) provides comments Saubhagya (Nokia) disagree with simultaneous mode Carlson (MediaTek) disagree to define 'UE in S&F mode', provides comments, and provides an r02. Jaewoo (LGE) provides comments and shares similar view with Wen (vivo). Wen (vivo) comments and requests clarification Stephen (Qualcomm) provides an r01 Ellen (Google) provides all cases for discussion Kundan(NEC) provides comment. Lalith(Samsung) comments on r02. Steve (Huawei) comments that attach is the best option, lets keep the wording aligned with what we already have. Lalith (Samsung) comments - I can also live with attach proposal. Wen (vivo) provides r05 Lalith (Samsung) provides r04 Jaewoo (LGE) provides comments on r02, r03 and S2-2500780. Stephen (Qualcomm) provides r03 Ellen (Google) also agree attach is a cleaner approach when the UE accesses to a satellite operated in different modes from the previously attached one Jaewoo (LGE) provides r06 based on r05. Stephen (Qualcomm) comments on the r04, r05 and r06 Stephen (Qualcomm) comments again Jaewoo (LGE) further replies to comments from Stephen (Qualcomm). Carlson (MediaTek) agrees analysis from Jaewoo (LGE) and objects to texts specify ATTACH/TAU during mode change. Kundan (NECk) fine with r06. Steve (Huawei) provides r07 Jaewoo (LGE) responds to Steve (Huawei) and Kundan (NEC). Stefan (Ericsson) respondes to Jaewoo Jaewoo (LGE) further replies to Kundan (NEC). Lalith(Samsung) agrees with Stefan (Ericsson) Saubhagya (Nokia) agrees with Stefan (Ericsson) Jaewoo (LGE) responds to Stefan (Ericsson). Stefan (Ericsson) replies to Jaewoo Kundan (NEC) responds to Jaewoo. ==== General Revisions Deadline ==== Jaewoo (LGE) further responds to Stefan (Ericsson). Saubhagya (Nokia) proposing to agree with R07 with TAU instead of Attach Carlson (MediaTek) objects to all revisions of this CR, due to technically un-implementable. Lalith(Samsung) objects r00 to r03 and can accept other revisions. Stephen (Qualcomm) can accept the r07 and r03 to r05 but not other revs. Carlson (MediaTek) thinks Nokia proposal is not implementable. Chris (Vodafone) thinks that the analysis in e.g. 0780 might be inexact. Attach will be done with the old-GUTI, and unless MME can contact old MME (and if it can then TAU would succeed and not be rejected) the MME has to request the IMSI and then progress the registration. I'd probably go for a USIM file to choose between Attach and TAU - similar to the M2M 'attach with IMSI at PLMN change' field. Steve (Huawei) is ok with r07 - wording can be fixed by corrections Kundan (NEC) is ok with r07. Wording can be improved. Stefan (Ericsson) also OK with r07 Carlson (MediaTek) can only accept r07 by deleting 'If the UE is registered state with a satellite operating in S&F mode, the UE shall perform the attach procedure if it access an eNodeB that is not operating in S&F mode (either TN or NTN eNodeB) and vice versa'. ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500446 | CR | Approval | 23.401 CR3831R2 (Rel-19, 'B'): UE determination for S&F mode operation or power saving | Rel-19 | Revision of S2-2412317. Noted in e-mail session | Stephen (Qualcomm) comments Carlson (MediaTek) comments Wen (vivo) comments Steve (Huawei) comments Lalith (Samsung) comments Carlson (MediaTek) comments on r01 Ellen (Google) replies comments and provides r01 Steve (Huawei) comments on r01 Lalith (Samsung) comments on r02 Wen (vivo) comments on r02 Ellen (Google) replies comments from MediaTek, Vivo, Huawei and provides r02 Ellen (Google) replies to vivo and Samsung and provides r03 Wen (vivo)comments r03 Ellen (Google) replies to Wen (vivo) Carlson (MediaTek) ask question about why UE needs to know when and where with/without feeder link Wen (vivo) replies Ellen (Google) replies to MTK/vivo and provides r04 Wen (vivo) provides r05 ==== General Revisions Deadline ==== Haris(Qualcomm) comments that r05 is incorrect Ellen (Google) prefers r04 and replies to Qualcomm. Stephen (Qualcomm) cannot agree any revision (r00 to r05) Wen(vivo) comments that the issue' How can the UE know what is happening on the feeder of the satellite (i.e., 'If the UE determines an ongoing/upcoming loss of feeder link [...]...' )' exists also in r04. Carlson (MediaTek) cannot agree original version, r01, r04 and r05, because they are not implementable. Steve (Huawei) CR is NOT required and does not work. ==== Comments Deadline ==== | Noted | |
| 19.1.2 | S2-2500321 | CR | Approval | 23.401 CR3847 (Rel-19, 'B'): Applicability of the S&F Wait Timer | MediaTek Inc. | Rel-19 | No S&F mode for UE WI Code should be 5GSAT_Ph3-ARC! Merged into S2-2501339 | Ramon (Sateliot) comments. Carlson (MediaTek) (tdoc author) agrees with Ramon (Sateliot) comments, and is okay to merge to 0782 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.1.2 | S2-2500322 | CR | Approval | 23.401 CR3848 (Rel-19, 'B'): No Necessity to define UE in S&F mode | MediaTek Inc. | Rel-19 | Noted in e-mail session | Stephen (Qualcomm) comments Steve (Huawei) comments Stephen (Qualcomm) comments and provides an r01 Ramon (Sateliot) comments Carlson (MediaTek) responds to Ramon. Carlson (MediaTek) comments on r01 Kundan (NEC) prefers r0 over r1. Agree with MTK that there is no UE S&F mode. Boren (OPPO) also prefers no UE S&F mode and tries to avoid ambiguous wording. ==== General Revisions Deadline ==== Stephen (Qualcomm) can only agree the r01 Wen (vivo) is ok without UE S&F mode, and think the r0 is more clear . Carlson (MediaTek) objects the r01 and can only agree the current 23.401 or r00, and replies to Stephen and Boren Steve (Huawei) is ok with r00 Boren (OPPO) is ok with r00 Jaewoo (LGE) supports r00. Heng(China Telecom) is ok with r00. Thierry (Novamint) does not support r1. ok with r00 - Agree with many comments that there is no UE S&F mode. ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500559 | CR | Approval | 23.401 CR3855 (Rel-19, 'F'): Transitioning between operation in S&F mode and normal mode | LG Electronics | Rel-19 | Noted in e-mail session | Stephen (Qualcomm) comments Jaewoo (LGE) replies to Stephen (Qualcomm). Heng(China Telecom) comment Jaewoo (LGE) replies to Heng(China Telecom). Carlson (MediaTek) comments. Lalith (Samsung) comments. Jaewoo (LGE) replies to Lalith (Samsung). Steve (Huawei) we should not have multiple CRs for this. Jaewoo (LGE) responds to Stephen (Qualcomm) and provides r03 based on r01. Stephen (Qualcomm) comments on the r01 and r02 Jaewoo (LGE) responds to Wen (vivo) and provides r02. Wen (vivo) comments. Jaewoo (LGE) responds to Steve (Huawei) and provides r01. Lalith(Samsung) provides r04 Also notes only one of the S2-2500559 or S2-2501041 should be agreed at the end. Because those are contradictory Jaewoo (LGE) responds to Lalith (Samsung) and can live with r04. Carlson (MediaTek)'s view is that S2-2500559r04 and S2-2501041 can coexist. Lalith(Samsung) comments. ==== General Revisions Deadline ==== Stephen (Qualcomm) cannot agree any revision (r00 to r04) Steve (Huawei) comments, ask a question Jaewoo (LGE) replies to Steve (Huawei) and propose postpone. Stefan (Ericsson) cannot agree any revision and supports to postpone ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500724 | CR | Approval | 23.401 CR3859 (Rel-19, 'B'): UE and NW behaviour transition between SF and normal | Vivo | Rel-19 | Merge into S2-2501041? WI Code should be 5GSAT_Ph3-ARC! Proposed merged with S2-2501041 (postponed). Postponed | Saubhagya (Nokia) provides comments Carlson (MediaTek) comments Stephen (Qualcomm) comments Wen (vivo) replies and provides r01 Heng(China Telecom) Stefan (Ericsson) provides r01 Steve (Huawei) comments Stefan (Ericsson) did _NOT_ provide r01, only commented Lalith (Samsung) comments on r01 Carlson (MediaTek) disagree to discuss UE in/out S&F mode and/or NW in/out S&F mode unless we have consensus about the clear definition of these terminologies. Wen (vivo) replies and provide r02 Boren (OPPO) comments on the definition of UE in S&F mode. Steve (Huawei) What is the relationship with S2-2501041 Wen (vivo) decides to merge this paper to S2-2501041 or S2-2500559 according to their revisions ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | - | - | - | Issue#2c: Support of Attach with PDN connection for Split MME option | - | - | Docs:=7 | - | |
| 19.1.2 | S2-2500551 | CR | Approval | 23.401 CR3854 (Rel-19, 'B'): Support of Attach with PDN connection for split MME architecture | LG Electronics | Rel-19 | Baseline for implementation based simplified description? Not handled at CC#4. Postponed | Yingying (CATT) comments Jaewoo (LGE) responds to Yingying (CATT) and provides r01. Saubhagya (Nokia) suggest to remove the example from the note and refer to S&F clause Kundan (NEC) provides comment Jaewoo (LGE) provides r02. Haris(Qualcomm) provides r03 Jaewoo (LGE) provides r06 to simplify the texts. Saubhagya (Nokia) provides r05 mentioning CIOT with ESM container specific case Jaewoo (LGE) is OK with r03. Kundan (NEC) provides r04. r04 = r03+option of S2-2500944 and S2-2500982 Lalith(Samsung) provides r07 Kundan (NEC) fine with r06. Kundan(NEC) fine with r07. Haris(Qualcomm) r07 not going in right direction Stefan (Ericsson) comments on ESM container Jaewoo (LGE) provides r08. Saubhagya (Nokia) comments and can only agree with r05-r07 Kundan(NEC) provides r09 addressing Haris comments. Saubhagya (Nokia) provides ans on ESM container Haris(Qualcomm) responds Steve (Huawei) comments, we can make it simpler as it is all implementation and we are not trying to provide a full normative description. Saubhagya (Nokia) provide further response Jaewoo (LGE) provides r10. Kundan (NEC) provides r11 o top of r10. Kundan (NEC) provides comments on r11. Jaewoo (LGE) provides r12. ==== General Revisions Deadline ==== Wen (vivo) is ok with r12 and would like to co-sign this paper, thanks. Saubhagya (Nokia) can only agree to R07 object to all other revision Kundan (NEC) responds to Saubhagya Jaewo(LGE) suggest r12 + Change 'Attach with PDN Connection' to 'During attach procedure, if a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour, and the UE included the ESM message container, it'. Kundan (NEC) fine with r13. Saubhagya (Nokia) OK with R13 proposed by Jaewoo(LGE) Jaewoo (LGE) responds to Kundan (NEC) about r12 + changes. Haris(Qualcomm) is ok with r12 but requires editorial cleanup Jaewoo (LGE) asks Haris(Qualcomm) about changes r12 + Change 'Attach with PDN Connection' to 'During attach procedure, if a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour, and the UE included the ESM message container, it'. Steve (Huawei) is ok with r12 + changes suggested. Haris(Qualcomm) is ok r12 + changes suggested from Jaewoo but prefers r12 ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500944 | CR | Approval | 23.401 CR3870 (Rel-19, 'F'): Support of attach with PDN connection in S&F mode of operation-option 1 | NEC | Rel-19 | Baseline for detailed description? Proposed merged with S2-2500551 (postponed). Postponed | Saubhagya (Nokia) asks for calrification Kundan (NEC) clarifies to Saubhagya(Nokia) Saubhagya (Nokia) asks Kundan (NEC) to specify the restrictions about user plane data Stefan (Ericsson) provides comments Kundan (NEC) responds to Saubhagya Saubhagya (Nokia) comments Kundan(NEC) responds to Saubhagya (Nokia) Steve (Huawei) we don't need 2 CRs for this. Haris(Qualcomm) agrees with comments from Steven and suggests also to focus on 0551 Kundan(NEC) fine to merge the procedure mentioned in this document to 0551 as an implementation option. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500982 | CR | Approval | 23.401 CR3875 (Rel-19, 'B'): Description of procedures for split-MME architecture in informative annex | Sateliot, Novamint, Thales | Rel-19 | Proposed merged with S2-2500551 (postponed). Postponed | Stephen (Qualcomm) comments Stefan (Ericsson) provides comments Steve (Huawei) we don't need multiple CRs for this. Stefan (Ericsson) agrees with Steven and also suggests to focus on the CR in 0551 Ramon (Sateliot) agrees on focusing on the CR in 0551 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500248 | CR | Approval | 23.401 CR3846 (Rel-19, 'B'): Split MME handling of UE attach with PDN connection | Ericsson | Rel-19 | Merge into S2-2500551? Proposed merged with S2-2500551 (postponed). Postponed | Stefan (Ericsson) proposes to consider this merged into 0551 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500784 | CR | Approval | 23.401 CR3869 (Rel-19, 'B'): Information about ESM procedures in Split MME S&F Example | Huawei, HiSilicon | Rel-19 | Merge into S2-2500551? Proposed merged with S2-2500551 (postponed). Postponed | Stephen (Qualcomm) comments Steve (Huawei) should be merged into 0551. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500945 | CR | Approval | 23.401 CR3871 (Rel-19, 'F'): Support of attach with PDN connection in S&F mode of operation-option 2 | NEC | Rel-19 | Subset of option 1: merge into S2-2500944? Proposed merged with S2-2500551 (postponed). Postponed | Steve (Huawei) we don't need multiple CRs for this. Kundan (NEC) fine to merge this CR in 0551 . ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2500725 | CR | Approval | 23.401 CR3860 (Rel-19, 'B'): PDN connection handling under S&F mode | Vivo | Rel-19 | Merge into S2-2500944? WI Code should be 5GSAT_Ph3-ARC! Proposed merged with S2-2500551 (postponed). Postponed | Wen (vivo) provides r01 which only keeps clarification that no PDN connection is setup during the attach Steve (Huawei) do we need both this and 0551? Wen (vivo) is ok to discuss this paper in 0551 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.1.2 | - | - | - | Others | - | - | Docs:=11 | - | |
| 19.1.2 | S2-2500403 | CR | Approval | 23.401 CR3849 (Rel-19, 'F'): Terminology correction and clarification for Store and Forward Satellite Operation | Ericsson | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501086. | Stefan (Ericsson) provides r01 to rmeove overlap with 1038 Lalith(Samsung) Ok with r01 ==== General Revisions Deadline ==== Lalith(Samsung) objects r00 and is OK with R01 Saubhagya (Nokia) supports R01 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501086 | CR | Approval | 23.401 CR3849R1 (Rel-19, 'F'): Terminology correction and clarification for Store and Forward Satellite Operation | Ericsson | Rel-19 | Revision of S2-2500403r01. Approved | Agreed | |
| 19.1.2 | S2-2500758 | CR | Approval | 23.401 CR3864 (Rel-19, 'B'): Update on S&F Satellite Operation for UE and MME | China Telecom | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Saubhagya (Nokia) provides comments Carlson (MediaTek) comments Stephen (Qualcomm) comments Heng(China Telecom) reply to Saubhagya (Nokia) Hucheng(CATT) comments Stefan (Ericsson) comments Steve (Huawei) comments Heng (China Telecom) Reply Lalith (Samsung) comments Heng (China Telecom) provides r01 Heng (China Telecom) replies to Lalith (Samsung) comments Carlson (MediaTek) comments on r01 Steve (Huawei) clarifies about use together Heng(China Telecom) reply to Steve (Huawei) Lalith(Samsung) replies to Heng (China Telecom) Stephen (Qualcomm) comments on the r01 Heng(China Telecom) replied to Lalith(Samsung) Heng(China Telecom) reply to Lalith(Samsung) and Stephen (Qualcomm) Lalith(Samsung) replies to Heng(China Telecom) Heng(China Telecom) relpies to Carlson (MediaTek) comments and provides r03 Heng(China Telecom) replies to Lalith(Samsung) Lalith(Samsung) comments. ==== General Revisions Deadline ==== Saubhagya (Nokia) object to all versions Stephen (Qualcomm) cannot agree any version of this CR (r00 to r03) Heng(China Telecom) reply to Saubhagya (Nokia) and don't agree objection Heng(China Telecom) reply to Stephen (Qualcomm) and don't agree objection ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2501031 | CR | Approval | 23.401 CR3878 (Rel-19, 'F'): Location determination for S&F | Samsung | Rel-19 | Postponed in e-mail session | Saubhagya (Nokia) provide comments Haris(Qualcomm) comments Lalith(Samsung) comments Lalith (Samsung) comments and provides r01. Saubhagya (Nokia) have concerns with r01 as well Stefan (Ericsson) provides comments Lalith(Samsung) replies to Stefan (Ericsson) Haris(Qualcomm) provides r02 Stefan (Ericsson) replies to Lalith and prefers to let SA3-LI discuss first Lalith(Samsung) comments. Lalith(Samsung) is OK with r02 Hucheng (CATT) proposes to have a common understanding to reply LS from SA3-LI Stefan (Ericsson) proposes to focus on the reply to SA3-LI and that we do not need this CR ==== General Revisions Deadline ==== Lalith(Samsung) agrees to postpone the CR and wait for reply to SA3-LI Stefan (Ericsson) supports to postpone the CR ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2501038 | CR | Approval | 23.401 CR3879 (Rel-19, 'F'): Clarifications related to S&F aspects | Samsung | Rel-19 | Not handled at CC#4. Postponed | Saubhagya (Nokia) provide comments Boren (OPPO) provides comments Steve (Huawei) comments Haris(Qualcomm) provides comments Wen (vivo) comments Lalith (Samsung) comments and provides r01 Stefan (Ericsson) provides comments Steve (Huawei) provides r02, please ignore it. Steve (Huawei) provides r03 Lalith(Samsung) is OK with r03 Haris(Qualcomm) provides r04 Lalith(Samsung) comments on r04 Haris(Qualcomm) responds ==== General Revisions Deadline ==== Saubhagya (Nokia) agree to keep only the last change on the HSS timestamp in R04 Lalith(Samsung) replies to Saubhagya (Nokia) Saubhagya (Nokia) cannot agree to any revision Lalith (Samsung) agree to keep only the last change on the HSS timestamp in R04. i.e. only changes available in clause '5.7.1 HSS' Stefan (Ericsson) supports to keep only the last change on the HSS timestamp (clause 5.7.1) in R04, also since the similar correction was removed from another CR to avoid overlap. Steve (Huawei) is ok with r04 with and only keeping the change for the HSS in clause 5.7.1 (i.e. remove changes from clauses 4.3.12.1 & 4.13.19.1). ==== Comments Deadline ==== | Postponed |
| 19.1.2 | S2-2501040 | CR | Approval | 23.401 CR3880 (Rel-19, 'F'): UE Detach for S&F Mode Access | Qualcomm Incorporated | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Saubhagya (Nokia) provides comments Carlson (MediaTek) comments Jaewoo (LGE) provides comments. Stephen (Qualcomm) comments Wen (vivo) comments Boren (OPPO) comments. Heng (China Telecom) comments Steve (Huawei) comments Lalith (Samsung) comments Stephen (Qualcomm) provides an r01 Carlson (MediaTek) comments on r01 Stephen (Qualcomm) provides an r02 and replies to comments Lalith (Samsung) provides r03 Carlson (MediaTek) provides r05 ==== General Revisions Deadline ==== Saubhagya (Nokia) can only agree to R03 Jaewoo (LGE) prefers r05 and also OK with r03. Lalith (Samsung) objects r00 to r02. OK with r03 or r05. Wen (vivo) prefers the r05, as it is full CN on board case and depends on UE implementation aspects, then it would be better to describe in Annex O.3 . Stephen (Qualcomm) prefers the r02 but can agree the r03 or r05. Wen (vivo) is also ok with r03. Boren (OPPO) is ok with r03, r05. Carlson (MediaTek) is only okay with r05 because r03 has technical flaw Carlson (MediaTek) agrees with Boren (OPPO)'s reading on r05. Stefan (Ericsson) can agree r03 or r05 Saubhagya (Nokia) object to all versions ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500507 | CR | Approval | 23.401 CR3850 (Rel-19, 'F'): Clarification on timestamp processing and editoral modification | Xiaomi | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Stephen (Qualcomm) comments Saubhagya (Nokia) provide comments Stefan (Ericsson) coments Steve (Huawei) comments Yuxin (Xiaomi) replies and asks for clarification ==== General Revisions Deadline ==== Saubhagya (Nokia) propose to note the CR Stephen (Qualcomm) proposes the CR be noted Stefan (Ericsson) supports to note Steve (Huawei) objects to all revisions ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500947 | CR | Approval | 23.401 CR3872 (Rel-19, 'F'): Correction to the S&F procedure | NEC | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Steve (Huawei) comments it is possible for the MME to reject a UE and know it supports S&F. Haris(Qualcomm) comments Kundan (NEC) comments that 5.3.4b.2 is related to EDT and no control plane NAS message is sent how to reject EDT with NAS reject. ==== General Revisions Deadline ==== Haris(Qualcomm) objects to r0 and suggests revision Carlson (MediaTek) asks questions regarding Qcom proposed change ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500508 | CR | Approval | 23.401 CR3851 (Rel-19, 'B'): Procedure update for Store and Forward operations | Xiaomi | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Steve (Huawei) comments Haris(Qualcomm) objects to the CR Saubhagya (Nokia) same comment as provided for S2-2500507 Stefan (Ericsson) provides concerns ==== General Revisions Deadline ==== Saubhagya (Nokia) objects to the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500727 | CR | Approval | 23.401 CR3862 (Rel-19, 'B'): Service request procedure update for S&F | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Saubhagya (Nokia) asks for clarification Steve (Huawei) comments Haris (Qualcomm) comments that the CR is not needed Wen (vivo) is ok that this CR is not needed ==== General Revisions Deadline ==== Saubhagya (Nokia) objects to the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500759 | CR | Approval | 23.401 CR3843R1 (Rel-19, 'B'): Update on procedures of PDN connection to support S&F Satellite Operation | China Telecom | Rel-19 | Revision of S2-2412239. WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | Stephen (Qualcomm) comments Heng(China Telecom) reply to Stephen (Qualcomm) Stefan (Ericsson) provides comments Saubhagya (Nokia) supports Ericsson and Qualcomm view Steve (Huawei) comments Heng(China Telecom) reply and provide r01 Leo (Deutsche Telekom) comments that the cover page of r01 still uses the wrong Work Item code. It should be 5GSAT_Ph3-ARC Stephen (Qualcomm) comments that previous comments apply also to the r01 Heng(China Telecom) reply to Stephen (Qualcomm) comments ==== General Revisions Deadline ==== Saubhagya (Nokia) do not agree to any version propose to note the CR Stephen (Qualcomm) cannot agree any version (r00 to r02) for reasons already given Stefan (Ericsson) supports to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | - | - | - | KI#3 Support of UE-satellite-UE communication | - | - | Docs:=0 | - | |
| 19.1.2 | - | - | - | Mobility support - IMS layer | - | - | Docs:=11 | - | |
| 19.1.2 | S2-2500718 | CR | Approval | 23.228 CR1561 (Rel-19, 'B'): Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia | Rel-19 | r01 agreedrevised in e-mail session to S2-2501087. | George (Ericsson) provides comments Atsushi (NTT DOCOMO) provides r01 according to George (Ericsson)'s comment ==== General Revisions Deadline ==== Saubhagya (Nokia) supports R01 George (Ericsson) OK R01 George (Ericsson) Ok with R01 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501087 | CR | Approval | 23.228 CR1561R1 (Rel-19, 'B'): Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia, China Telecom | Rel-19 | Revision of S2-2500718r01. Approved | Agreed | |
| 19.1.2 | S2-2500716 | CR | Approval | 23.228 CR1521R6 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon | Rel-19 | IMS-AS based solution Revision of S2-2412672. r01 agreed. Revised in e-mail session to S2-2501088. | George (Ericsson) provides comments George (Ericsson) provides r01. Haris(Qualcomm) comments on r01 Saubhagya (Nokia) provides some clarification George (Ericsson) provides response Haris(Qualcomm) is ok with SIP MESSAGE if everyone else is fine with it Atsushi (NTT DOCOMO) agrees with r01. George (Ericsson) provides an answer ==== General Revisions Deadline ==== Saubhagya (Nokia) supports R01 Guanglei (Huawei) Supports R01 George (Ericsson) OK R01 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501088 | CR | Approval | 23.228 CR1521R8 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom | Rel-19 | Revision of S2-2500716r01. Approved | Agreed | |
| 19.1.2 | S2-2500717 | CR | Approval | 23.228 CR1522R6 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon | Rel-19 | IMS-AS based solution Revision of S2-2412673. r01 agreed. Revised in e-mail session to S2-2501089. | George (Ericsson) provides comments George (Ericsson) provides r01 Haris(Qualcomm) comments on r01 Saubhagya (Nokia) provides some clarification Atsushi (NTT DOCOMO) agrees with r01. ==== General Revisions Deadline ==== Saubhagya (Nokia) Supports R01 Guanglei (Huawei) supports R01 George (Ericsson) Ok R01 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501089 | CR | Approval | 23.228 CR1522R8 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon, China Telecom | Rel-19 | Revision of S2-2500717r01. Approved | Agreed | |
| 19.1.2 | S2-2500627 | CR | Approval | 23.228 CR1521R4 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | China Mobile, China Telecom, [NTT DOCOMO, Nokia] | Rel-19 | Revision of S2-2412672. WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | George (Ericsson) provides comments Amy (vivo) proposes a SOH on this P-CSCF sending RE-INVITE option in CC#1 Haris(Qualcomm) comments Yi (China Mobile) replies. George (Ericsson) provides response Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== Saubhagya (Nokia) propose to note the CR George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500628 | CR | Approval | 23.228 CR1522R4 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | China Mobile, China Telecom [NTT DOCOMO, Nokia] | Rel-19 | Revision of S2-2412673. WI Code should be 5GSAT_Ph3-ARC! Noted in e-mail session | George (Ericsson) provides comments Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500700 | CR | Approval | 23.228 CR1476R3 (Rel-19, 'B'): Functional descriptions of UE-satellite-UE communications when satellite changes | Vivo | Rel-19 | Revision of S2-2411888. Noted in e-mail session | George (Ericsson) proposes to merge this into 0718. Also a lot of the information is already described in 23.501 and don't need to be repeated here. Haris(Qualcomm) comments Atsushi (NTT DOCOMO) proposes to merge this into 0718. ==== General Revisions Deadline ==== Saubhagya (Nokia) propose to note the CR George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500767 | CR | Approval | 23.228 CR1521R7 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | [NTT DOCOMO], vivo | Rel-19 | Revision of S2-2412672. Noted in e-mail session | George (Ericsson) proposes to note the CR. This is not needed and just repeating the same procedure again. Hucheng (CATT) proposes to NOTE this paper based on the result of SOH. ==== General Revisions Deadline ==== Saubhagya (Nokia) propose to note the CR George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | S2-2500768 | CR | Approval | 23.228 CR1522R7 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | [NTT DOCOMO], vivo | Rel-19 | Revision of S2-2412673. Noted in e-mail session | George (Ericsson) proposes to note the CR. Amy (vivo) disagrees to NOTE considering the dependency on SOH result, and proposes to discuss SOH in CC#1 George (Ericsson) provides response Amy (vivo) replies to George (Ericsson), Haris (Qualcomm) George (Ericsson) proposes to note the paper since this option is not selected. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.1.2 | - | - | - | Mobility support - 5GS | - | - | Docs:=2 | - | |
| 19.1.2 | S2-2500699 | CR | Approval | 23.501 CR5518R7 (Rel-19, 'B'): Support of UE-satellite-UE communications when serving satellite changes | Vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO, China Telecom | Rel-19 | Revision of S2-2412905. r04 agreed. Revised in e-mail session to S2-2501090. | George (Ericsson) provides comments and asks question Amy (vivo) provides r02 and replies to George (Ericsson) Saubhagya (Nokia) asks for clarification Amy (vivo) replies Saubhagya (Nokia) provide comments Saubhagya (Nokia) agree with Atsushi (NTT DOCOMO) the DNAI info is not needed during mobility Atsushi (NTT DOCOMO) provides comments Amy (vivo) replies to Saubhagya (Nokia) and Atsushi (NTT DOCOMO), and proposes to sync the DNAI usage to the call setup procedure Saubhagya (Nokia) answers to Amy (vivo) queries Guanglei (Huawei) comments on DNAI usage Amy (vivo) replies to Saubhagya (Nokia) and Guanglei (Huaiwei) Saubhagya (Nokia) comments Amy (vivo) provides r03 and replies Guanglei (Huawei) further comments on DNAI usage and traffic routing Amy (vivo) provides r04 and replies ==== General Revisions Deadline ==== Saubhagya (Nokia) OK with R04 Guanglei (Huawei) supports R04 George (Ericsson) Ok with R04 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501090 | CR | Approval | 23.501 CR5518R8 (Rel-19, 'B'): Support of UE-satellite-UE communications when serving satellite changes | Vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO, China Telecom | Rel-19 | Revision of S2-2500699r04. Approved | Agreed | |
| 19.1.2 | - | - | - | Early media support - IMS layer | - | - | Docs:=3 | - | |
| 19.1.2 | S2-2500293 | CR | Approval | 23.228 CR1520R3 (Rel-19, 'B'): Call setup of UE-Satellite-UE communication with early media in IMS | Vivo, China Telecom | Rel-19 | Revision of S2-2412907. r01 agreed. Revised in e-mail session to S2-2501091. | George (Ericsson) provides comments Zhenhua (vivo) replies to George (Ericsson) and provides r01 George (Ericsson) provides comments inline Haris(Qualcomm) asks questions for clarification Zhenhua (vivo) replies to Haris(Qualcomm) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501091 | CR | Approval | 23.228 CR1520R4 (Rel-19, 'B'): Call setup of UE-Satellite-UE communication with early media in IMS | Vivo, China Telecom | Rel-19 | Revision of S2-2500293r01. Approved | Agreed | |
| 19.1.2 | S2-2500294 | CR | Approval | 23.228 CR1547 (Rel-19, 'B'): Call setup of UE-Satellite-UE communication with early media with two AGWs allocated | Vivo, China Telecom | Rel-19 | Noted in e-mail session | Hucheng (CATT) proposes to NOTE this paper. Heng(China Telecom ) is OK to not handle this CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.1.2 | - | - | - | Update for UE-Satellite-UE communication | - | - | Docs:=7 | - | |
| 19.1.2 | S2-2500719 | CR | Approval | 23.228 CR1562 (Rel-19, 'B'): Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia | Rel-19 | Approved | Agreed | |
| 19.1.2 | S2-2500785 | CR | Approval | 23.228 CR1564 (Rel-19, 'B'): Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | Huawei, HiSilicon, NTT DOCOMO, China Telecom, CATT | Rel-19 | r04 agreedrevised in e-mail session to S2-2501092. | George (Ericsson) provides comments Guanglei (Huawei) provides r01 Sushmit (NTT DOCOMO) provides comments Guanglei (Huawei) replies to Sushmit (NTT DOCOMO) and will provide a revision later Guanglei (Huawei) provides r02 to fix editorial issue Guanglei (Huawei) provides r03 Guanglei (Huawei) provides r04 ==== General Revisions Deadline ==== Saubhagya (Nokia) OK with r04 George (Ericsson) OK R04 Sushmit (NTT DOCOMO) OK with R04 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501092 | CR | Approval | 23.228 CR1564R1 (Rel-19, 'B'): Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | Huawei, HiSilicon, NTT DOCOMO, China Telecom, CATT | Rel-19 | Revision of S2-2500785r04. Approved | Agreed | |
| 19.1.2 | S2-2500861 | CR | Approval | 23.502 CR5129R3 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, China Telecom, Samsung | Rel-19 | Revision of S2-2412675. Confirm CR Revision - CR states 32! Confirm Spec version used - CR states {19.21.0}! WI Code should be 5GSAT_Ph3-ARC! r02 agreed. Revised in e-mail session to S2-2501093. | George (Ericsson) provides comments Sushmit (NTT DOCOMO) responds to George (Ericsson) and provides revision r01 George (Ericsson) asks a question Sushmit (NTT DOCOMO) responds to George (Ericsson) and provides revision r02 ==== General Revisions Deadline ==== George (Ericsson) can live with R02. Please see additional comments. ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501093 | CR | Approval | 23.502 CR5129R4 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, China Telecom, Samsung | Rel-19 | Revision of S2-2500861r02. Approved | Agreed | |
| 19.1.2 | S2-2500864 | CR | Approval | 23.503 CR1429R3 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, Samsung, China Telecom | Rel-19 | Revision of S2-2412676. Confirm CR Revision - CR states 32! Confirm Spec version used - CR states {19.21.0}! WI Code should be 5GSAT_Ph3-ARC! r03 agreed. Revised in e-mail session to S2-2501094. | George (Ericsson) provides comments Guanglei (Huawei) provides comments Sushmit (NTT DOCOMO) responds to George (Ericsson) and provides revision r01 Sushmit (NTT DOCOMO) responds to Guanglei (Huawei) and provides revision r01 Guanglei (Huawei) provides comments on r01 Sushmit (NTT DOCOMO) responds to Guanglei (Huawei) and provides revision r02 Mirko (Huawei) provides comments. Sushmit (NTT DOCOMO) responds to Mirko (Huawei) and provides revision r03 ==== General Revisions Deadline ==== Guanglei (Huawei) OK with r03 George (Ericsson) Ok with R03 ==== Comments Deadline ==== | Revised |
| 19.1.2 | S2-2501094 | CR | Approval | 23.503 CR1429R4 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, Samsung, China Telecom | Rel-19 | Revision of S2-2500864r03. Approved | Agreed | |
| 19.1.2 | - | - | - | Above quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
| 19.1.2 | - | - | - | KI#2a: List of satellite ID and S&F monitoring list | - | - | Docs:=8 | - | |
| 19.1.2 | S2-2500138 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Qualcomm | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500505 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store and foward operation | Xiaomi | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500538 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Nokia | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500549 | LS OUT | Approval | [DRAFT] LS Reply on LS on Satellite IDs for store-and-forward operation | LG Electronics | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500634 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | OPPO | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500729 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | vivo | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2500781 | LS OUT | Approval | [DRAFT] Reply to LS on Satellite IDs for store-and-forward operation | Huawei, HiSilicon | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | S2-2501035 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Samsung | Rel-19 | Response to S2-2500047 Not Handled | - | |
| 19.1.2 | - | - | - | KI#2c: Attach w/ PDN connection for Split MME | - | - | Docs:=1 | - | |
| 19.1.2 | S2-2500942 | DISCUSSION | Discussion | Discussion paper attach procedure with default PDN connection. | NEC | Rel-19 | Not Handled | - | |
| 19.1.2 | - | - | - | KI#2: Others | - | - | Docs:=2 | - | |
| 19.1.2 | S2-2500757 | DISCUSSION | Agreement | Discussion on the enhanced discontinuous network coverage for satellite access under S&F mode. | China Telecom | Rel-19 | Not Handled | - | |
| 19.1.2 | S2-2501030 | DISCUSSION | Discussion | Discussion on location determination for Full EPC onboard. | Samsung | Rel-19 | Not Handled | - | |
| 19.1.2 | - | - | - | KI#3:Mobility support - IMS layer | - | - | Docs:=1 | - | |
| 19.1.2 | S2-2500715 | DISCUSSION | Discussion | Discussion on whether IMS AS or P-CSCF initiates SIP re-INVITE. | NTT DOCOMO, Nokia | Rel-19 | Not Handled | - | |
| 19.1.2 | - | - | - | KI#1: Support of regenerative payload satellite access | - | - | Docs:=2 | - | |
| 19.1.2 | S2-2500247 | CR | Approval | 23.501 CR5908 (Rel-19, 'F'): AMF selection for regenerative payload | Ericsson | Rel-19 | Not Handled | - | |
| 19.1.2 | S2-2500618 | CR | Approval | 23.502 CR4994R3 (Rel-19, 'B'): Support of Regenerative Payload with NG-RAN Node Onboard Satellite | OPPO, Huawei, HiSilicon | Rel-19 | Revision of S2-2411702 Not Handled | - | |
| 19.2.1 | - | - | - | Study on system architecture for next generation real time communication services phase 2 (FS_NG_RTC_Ph2) | - | - | Docs:=0 | - | |
| 19.2.2 | - | - | - | System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2) | - | - | Docs:=58 | - | |
| 19.2.2 | - | - | - | General | - | - | Docs:=4 | - | |
| 19.2.2 | S2-2500065 | LS In | Action | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 (S4-242111) | Rel-19 | Not Handled. Postponed | Postponed | |
| 19.2.2 | S2-2500287 | CR | Approval | 23.228 CR1543 (Rel-19, 'D'): Abbreviations of ADC and BDC | Vivo | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500638 | CR | Approval | 23.228 CR1557 (Rel-19, 'B'): Clarification on DC Application Server | ZTE | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500895 | CR | Approval | 23.228 CR1573 (Rel-19, 'F'): Update IMS DC figures to align with other annex | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.2.2 | - | - | - | KI#8: IMS avatar communication | - | - | Docs:=11 | - | |
| 19.2.2 | S2-2500079 | LS In | Information | LS from SA WG3: LS on IMS support for AF authorization and IMS avatar communication | SA WG3 (S3-250170) | Postponed in e-mail session | DognYeon (Samsung) proposes to postpone this to the next meeting, since there is no input in SA2 so far. | Postponed | |
| 19.2.2 | S2-2500169 | CR | Approval | 23.228 CR1531 (Rel-19, 'C'): Resolving ENs on Avatar communication | Qualcomm Incorporated | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) replies to the comments. Hao (ZTE): similar view with DongYeon (Samsung), TS 26.264 is not a correct reference for Avatar ID list. Yi (China Mobile) provides comments and propose to merge call flows parts to other contributions. DongYeon (Samsung) is not OK with this CR, and provides comments George (Ericsson) provides comments George (Ericsson) provides response Yi (China Mobile) provides comments again. Kenny (Qualcomm) replies to Yi's comments. Hao (ZTE) comments on r01. Kenny (Qualcomm) provides r01, with removal of all changes against AC.11.3.1 and AC.11.3.3. Kenny (Qualcomm) replies Hao's comments. Hao (ZTE) responds to Kenny (Qualcomm). DongYeon (Samsung) provides comments, and proposes to note this paper if we cannot agree with personal asset information part. Kenny (Qualcomm) provides r02. Zhenhua (vivo) comments on r02. Hao (ZTE) proposes to Note this paper or mark it merged into 0635. George (Ericsson) provides revision 3, minor edits in Fuchsia Leo (Deutsche Telekom) objects to have a reference to 3GPP WG in a NOTE Kenny (Qualcomm) is OK with r03, provides reply to Hao and Zhenhua. Yi (China Mobile) comments. George (Ericsson) provides comment to Leo. Mu (Huawei) comments on r03 Kenny (Qualcomm) provides r04 to resolve Mu's comments. Yi (China Mobile) cpmments on r04. ==== General Revisions Deadline ==== George (Ericsson) Ericsson accepts r04 only. Yi (China Mobile) can live with agree r04 + adding 'based on instruction from DC AS' in step 5 of AC.11.3.2.2 + change the NOTE to EN. Kenny (Qualcomm) replies to Yi's comments and propose to keep the alignment via: agree r04 + adding 'based on instruction from DC AS' in step 5 of AC.11.3.2.2. Kenny (Qualcomm) can live with Yi's proposal. DongYeon (Samsung) can live with r04+change the new NOTE to EN 'Editor's Note: The information for the user selection in the avatar calls that can be included with the Avatar IDs in Avatar ID List will be defined in Stage 3.' Hao (ZTE) proposes to NOTE or POSTPONE the paper. Leo (Deutsche Telekom) can't accept r04 as it is now, changes are necessary. Kenny (Qualcomm) clarifies that the latest proposal (r04 + adding 'based on instruction from DC AS' in step 5 of AC.11.3.2.2 + change the NOTE to EN) can resolve Leo's concern. Leo (Deutsche Telekom) clarifies that the latest proposal (r04 + adding 'based on instruction from DC AS' in step 5 of AC.11.3.2.2 + change the NOTE to EN) resolves DT's concern. Kenny (Qualcomm) replies Hao's comments and proposed to agree r04 + adding 'based on instruction from DC AS' in step 5 of AC.11.3.2.2 + change the NOTE to EN. Hao (ZTE) responds: for me Avatar ID and its list is easy to understand, but Avatar Representation which used many times in TS 23.228 should be clarified either in text or in EN for SA4; and Samsung also listed several questions on this aspect. So it takes time to further consider it. Kenny (Qualcomm) clarifies the concern from ZTE has no overlap with this CR, which should be resolved via separate CRs. Hao (ZTE) responds: they are not separate topics, please check the normal text you removed. Kenny (Qualcomm) asks Hao for more clarification. George (Ericsson) Leos concern is unfounded. This CR has to be updated, and will be at the next meeting 100%. There is no chance it will stay as is. SO I think we need to be positive, as opposed to other easy options. Hao (ZTE) responds and proposes to POSTPONE the paper. ==== Comments Deadline ==== Kenny (Qualcomm) replies to Hao. | Noted |
| 19.2.2 | S2-2500205 | CR | Approval | 23.228 CR1537 (Rel-19, 'F'): KI#8: Update to Architecture for avatar communications | Ericsson | Rel-19 | Handle Not handled at CC#4. Postponed | George (Ericsson) provides response DongYeon (Samsung) proposes merge this paper to S2-2500794, or to postpone. Yi (China Mobile) provides comments. Mu (Huawei) provides comments. George (Ericsson) provides r01 George (Ericsson) provides comments George (Ericsson) provides r02 to remove the last EN Mu (Huawei) provides further comments. Leo (Deutsche Telekom) objects to Note Y having a reference to SA3 ==== General Revisions Deadline ==== George (Ericsson) OK with r02 Yi (China Mobile) is ok with r02. Kenny(Qualcomm) is OK with r02. DongYeon (Samsung) is ok with r02. Leo (Deutsche Telekom) is NOT ok with r02. The reference to SA3 needs to be removed from NOTE Y George (Ericsson) Yi, please bring this up tomorrow in the CC as this is not a technical reason. George (Ericsson) Is r02 + removing the Note completely ok. Mu (Huawei) support r02 + removing the note ==== Comments Deadline ==== DongYeon (Samsung) support r02 + removing the note + remove comma before 'via the referenced URL', and would like to co-sign. George (Ericsson) Ok if it gets approved in CC4. | Postponed |
| 19.2.2 | S2-2500206 | CR | Approval | 23.228 CR1538 (Rel-19, 'F'): KI#8: Update to Avatar Procedures | Ericsson | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) provides comments. George (Ericsson) provides response Yi (China Mobile) suggest to remove the first EN, take this contribution as the basis of receiving UE rendering procedure. DongYeon (Samsung) provides comments. George (Ericsson) provides comments Mu (Huawei) agrees with Yi, there is nothing FFS for. Yi (China Mobile) comments. Mu (Huawei) replies to George, we already have two ENs about SA3, why you need a third one for authorization? George (Ericsson) responds Yi (China Mobile) provides r01 Mu (Huawei) propose to note this CR, if you remove the EN then nothing changed from the original 23.228 ==== General Revisions Deadline ==== George (Ericsson) Objects to r01. We have nothing defined for media specification. This cant be implemented as is. It is useless Mu (Huawei) propose to note this CR, object r00 and r01 ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500635 | CR | Approval | 23.228 CR1554 (Rel-19, 'B'): Address EN on Avatar Representation | ZTE | Rel-19 | Noted in e-mail session | Hao (ZTE) responds to Kenny (Qualcomm) and DongYeon (Samsung). Kenny (Qualcomm) clarified no conflict between S2-2500635 and S2-2500169, we propose to merge the changes to 169. George (Ericsson) provides response DongYeon (Samsung) is not OK with this CR, and requests SoH on 'downloading Avatar Representation via BDC'. Yi (China Mobile) supports this contribution and propose to take as basis for removing EN of asset information and downaloding representation via BDC. Hao (ZTE) responds to George (Ericsson) and proposes to use this CR as baseline for EN of asset and downloading via BDC. George (Ericsson) propose to note the CR. See additional comments George (Ericsson) provides responds Hao (ZTE) responds. Yi (China Mobile) comments. Kenny (Qualcomm) replies to Hao. Kenny (Qualcomm) provides further detail comments. Yi (China Mobile) provides r01 trying to solve Kenny's concern. DongYeon (Samsung) provides comments on r01, proposes to note this paper if we cannot agree with personal asset information part. Kenny (Qualcomm) provides comments to r01. George (Ericsson) proposes to note this CR. We prefer to use 169 which covers exactly the same thing. ==== General Revisions Deadline ==== George (Ericsson) proposes to note the CR Kenny (Qualcomm) proposes the CR merged into 169. Hao (ZTE) agrees to NOTE or POSTPONE the paper. DongYeon (Samsung) proposes to note this CR. Defining format of Avatar Representation in SA4 is obvious, and does not need any NOTE in this specification. And that is not relevant with personal asset information mentioned in 169 discussions. ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500636 | CR | Approval | 23.228 CR1555 (Rel-19, 'B'): Address EN in UE Centric Avatar Communication Procedure | ZTE | Rel-19 | Noted in e-mail session | DongYeon (Samsung) is not ok with this paper, and provides comments. Yi (China Mobile) provide comments and propose to merge this cotribution into other contributions. George (Ericsson) proposes to note the CR. Please see additional comment ==== General Revisions Deadline ==== DongYeon (Samsung) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500772 | CR | Approval | 23.228 CR1563 (Rel-19, 'B'): Clarification on how DCSF fetch DC AS URL if not pre-configured | China Mobile | Rel-19 | Handle. Suggest to merge into S2-2500821 r04 agreedrevised in e-mail session to S2-2501095. | George (Ericsson) asks question DongYeon (Samsung) has the same question with Ericsson. Mu (Huawei) replies to DongYeon and George George (Ericsson) responds. Than please say so directly. It is transparent data stored in HSS and retrieved by DCSF Yi (China Mobile) provides r01. Rainer (Nokia) asks for clarification Hao (ZTE) comments. Mu (Huawei) replies inline. Yi (China Mobile) provides r02. DongYeon (Samsung) provides comments on r02. George (Ericsson) provides comments to Yi Yi (China Mobile) replies to DongYeon. Yi (China Mobile) replies to George and provides r03. Mu (Huawei) provide r04 George (Ericsson) asks a question Mu (Huawei) replies to George inline. ==== General Revisions Deadline ==== George (Ericsson) supports r04 Only Kenny (Qualcomm) can live with r04. Hao (ZTE) would like to co-sign the paper. DongYeon (Samsung) asks question on the new NOTE. The NOTE seems in scope of 3GPP. How can DC AS service provider know that its DC AS URL can be selected in promised condition by the DCSF? Mu (Huawei) support r04, and provide replies Kenny (Qualcomm) asks further question. Mu (Huawei) asks for clarification ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501095 | CR | Approval | 23.228 CR1563R1 (Rel-19, 'B'): Clarification on how DCSF fetch DC AS URL if not pre-configured | China Mobile | Rel-19 | Revision of S2-2500772r04. Approved | Agreed | |
| 19.2.2 | S2-2500794 | CR | Approval | 23.228 CR1565 (Rel-19, 'B'): KI#8: EN resolutions for Avatar communication | Samsung | Rel-19 | Postponed in e-mail session | Kenny (Qualcomm) provides comments. Yi (China Mobile) provides comments and ask questions. George (Ericsson) provides comments. This is a very unclear CR. DongYeon (Samsung) replies to comments from Qualcomm, China Mobile, and Ericsson, and provides r01. Yi (China Mobile) provides comment. Mu (Huawei) clarify the resource URL and ask some questions DongYeon (Samsung) replies to comments/questions from Ericsson, China Mobile, and Huawei. ==== General Revisions Deadline ==== George (Ericsson) proposes to postpone the CR until it is sufficiently clear Yi (China Mobile) propose to postpone the CR too. Kenny (Qualcomm) proposes to note or postpone the CR. DongYeon (Samsung) accepts to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2500821 | CR | Approval | 23.228 CR1567 (Rel-19, 'C'): Update procedure of Avatar Communication | Huawei, HiSilicon | Rel-19 | Handle as basis of network centric rendering? Not handled at CC#4. Postponed | Kenny (Qualcomm) provides comments. DongYeon (Samsung) proposes to merge this paper into 0794, and provides comments. Yi (China Mobile) provides comments and believe we need to decide which one to be taken as basis for network centric procedure between 0821 and 0794. George (Ericsson) provides comments Hao (ZTE) comments. George (Ericsson) please see inline George (Ericsson) asks a question Mu (Huawei) provides replies Yi (China Mobile) propose to use this contribution as the basis for network centric procedure and merge related changes from other cotributions. Mu (Huawei) replies to George inline. Mu (Huawei) provide r01, adopting all the comment so far. Rainer (Nokia) ask for clarification Mu (Huawei) replies inline. Yi (China Mobile) agree with Mu. DongYeon (Samsung) provides comment, r01 is still vague. Mu (Huawei) provide r02 according to George's comment, and reply to DongYeon inline. George (Ericsson) asks some questions ==== General Revisions Deadline ==== George (Ericsson) can live with r02 but questions are still not addressed. Yi (China Mobile) propose to agree r02 or r02+referencing to AC.11.1 in step 1. Kenny (Qualcomm) is not OK with r02. Hao (ZTE) would like to co-sign the paper. Mu (Huawei) replies to Kenny and George. Propose to approve r02 + change the reference in step 1 from AC 11.3.1 to AC.11.1 DongYeon (Samsung) can live with r02 + change reference in step 1 + and remove 'NOTE: Step 8-9 is out of scope of 3GPP. ' . George (Ericsson) provides response to Limu Kenny (Qualcomm) can live with r02 + change the reference in step 1 from AC 11.3.1 to AC.11.1 Mu (Huawei) replies to DongYeon and George George (Ericsson) provides response and suggestion to Limu Mu (Huawei) propose to approve r02 + change reference in step 1 to AC.11.1 + change the 'NOTE: Step 8-9 is out of scope of 3GPP.' to 'NOTE: Step 8-9 is out of scope of this release.'. George (Ericsson) is fine with the proposal. See comments in line ==== Comments Deadline ==== DongYeon (Samsung) the 'NOTE: the service operations for step 8-9 are out of scope of this release' can be work. | Postponed |
| 19.2.2 | S2-2501013 | CR | Approval | 23.228 CR1580 (Rel-19, 'F'): KI#8: Download of Avatar ID List | Nokia | Rel-19 | Noted in e-mail session | DongYeon (Samsung) is not ok with this paper, and provides comments. Yi (China Mobile) provides comments. George (Ericsson) Asks question Kenny (Qualcomm) provides comments. Rainer (Nokia) replies Zhenhua (vivo) comments George (Ericsson) asks a question. George (Ericsson) so it s basically implementation Rainer (Nokia) more or less ==== General Revisions Deadline ==== George (Ericsson) provides proposes to note the CR Yi (China Mobile) propose to note the CR and have further consideration. Rainer (Nokia) is ok to note the CR ==== Comments Deadline ==== | Noted |
| 19.2.2 | - | - | - | KI#7: Multiplex of DC apps over one SCTP conn | - | - | Docs:=8 | - | |
| 19.2.2 | S2-2500289 | DISCUSSION | Information | Multiplexing with duplicated stream ID. | Vivo | Noted in e-mail session | Noted | ||
| 19.2.2 | S2-2500290 | CR | Approval | 23.228 CR1545 (Rel-19, 'B'): De-multiplexing ADC in case same stream ID used by both UEs | Vivo | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) asks question for clarification. George (Ericsson) provides r01 with minor editorial comments Zhenhua (vivo) replies to Yi (China Mobile). Yi (China Mobile) provides comment. Zhenhua (vivo) replies to Kenny (Qualcomm) and provides r02 George (Ericsson) provides response Zhenhua (vivo) replies to DongYeon (Samsung) DongYeon (Samsung) proposes note this CR, the problem is not convinced. Zhenhua (vivo) provides r03. George (Ericsson) supports the proposal. Additional comments below. DongYeon (Samsung) provides comments, not OK with r00, r01, r02, r03. Mu (Huawei) asks for clarification Zhenhua (vivo) replies to Mu (Huawei) ==== General Revisions Deadline ==== George (Ericsson) accepts r04 Yi (China Mobile) can live with r03. DongYeon (Samsng) proposes to postpone to Athens meeting, objects to all revision. Mu (Huawei) comments Zhenhua (vivo) agree to postpone the CR to next meeting ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500624 | CR | Approval | 23.228 CR1552 (Rel-19, 'B'): Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile | Rel-19 | Handle r01 agreedrevised in e-mail session to S2-2501096. | Kenny (Qualcomm) provides comments. George (Ericsson) provides r01 with some edits George (Ericsson) provides response DongYeon (Samsung) provides comments on r00 and r01 Yi (China Mobile) replies to DongYeon and Kenny and provides r02. DognYeon (Samsung) provides comments with further questions on why two rejection options are needed. George (Ericsson) provides comments Yi (China Mobile) replies to DongYeon and provides r03. ==== General Revisions Deadline ==== George (Ericsson) accepts r01 only. It is not clear to me that the terminating network can use Feature capability at session establishment just as a UE does. This approach can be used for discover only Yi (China Mobile) propose to go with r02 but can live with r01. ask question to George. George (Ericsson) provides answer ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501096 | CR | Approval | 23.228 CR1552R1 (Rel-19, 'B'): Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile | Rel-19 | Revision of S2-2500624r01. Approved | Agreed | |
| 19.2.2 | S2-2500625 | CR | Approval | 23.228 CR1512R2 (Rel-19, 'B'): Service updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile | Rel-19 | Revision of S2-2411609. Postponed in e-mail session | George (Ericsson) provides comments DognYeon (Samsung) provides comments, the paper is written based on the wrong version of specification. ==== General Revisions Deadline ==== Yi (China Mobile) is ok to postpone the CR. George (Ericsson) proposes to postpone the CR to next meeting ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2500796 | CR | Approval | 23.228 CR1566 (Rel-19, 'B'): KI#7: Services for supporting multiplexing | Samsung | Rel-19 | Postponed in e-mail session | Yi (China Mobile) provides comment. George (Ericsson) proposes to note the CR. 625 captures much better the services DongYeon (Samsung) replies to China Mobile, Ericsson, vivo. Zhenhua (vivo) propose merging this CR into S2-2500625 or S2-2500624 as Yi (China Mobile) proposed. DongYeon (Samsung) provides r01. ==== General Revisions Deadline ==== Yi (China Mobile) propose to postpone the CR together with 0625. George (Ericsson) proposes postponing the CR to next mtg. DongYeon (Samsung) accepts to postpone. ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2500820 | LS OUT | Approval | [DRAFT] LS on IMS DC multiplexing | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | DongYeon (Samsung) provides r01. George (Ericsson) asks a question DongYeon (Samsung) comments. George (Ericsson) provides response to Samsung Mu (Huawei) is ok with r01 ==== General Revisions Deadline ==== Yi (China Mobile) is ok with r00 or r01 and think LS is helpful. DongYeon (Samsung) is ok only with r01 or postpone. George (Ericsson) proposes to postpone the CR. SA4 does already support multiplexing in its specifications. Mu (Huawei) asks where is this support in TS 26.114 Mu (Huawei) proposes to approve r01. ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2500883 | CR | Approval | 23.228 CR1572 (Rel-19, 'B'): Correction on DC multiplexing procedures | China Mobile | Rel-19 | Not Handled | - | |
| 19.2.2 | - | - | - | KI#2: IMS capability exposure for IMS DC | - | - | Docs:=16 | - | |
| 19.2.2 | S2-2500170 | CR | Approval | 23.228 CR1532 (Rel-19, 'F'): Correction on IMS data channel capability exposure | Qualcomm Incorporated | Rel-19 | Handle. Suggest to merge into S2-2501014, S2-2500209 Merged into S2-2501099 | Yi (China Mobile) propose to merge this contribution to 1014 and 0209. George (Ericsson) provides comments Kenny (Qualcomm) is OK to merge this CR with 1014 and 209. ==== General Revisions Deadline ==== George (Ericsson) propose to note the CR since it merged in other CRs ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500208 | CR | Approval | 23.228 CR1540 (Rel-19, 'F'): KI#2: Generalizing Information Retrieval | Ericsson | Rel-19 | Not Handle Not Handled | - | |
| 19.2.2 | S2-2500209 | CR | Approval | 23.228 CR1541 (Rel-19, 'C'): KI#2: Update to Network Capability Exposure Procedures | Ericsson | Rel-19 | Handle as basis for session termination? r04 agreedrevised in e-mail session to S2-2501097. | Yi (China Mobile) propose to take it as one of the basis and provides comment. George (Ericsson) provides r01 to remove parts that are addressed in 1014 George (Ericsson) provides response. Please see inline Jari (NTT DOCOMO) comments George (Ericsson) provides comments inline Mu (Huawei) provides comment George (Ericsson) provides r2 Jari (NTT DOCOMO) provides r3 Mu (Huawei) asks for clarification and propose to merge part of change in 0622 Rainer (Nokia) replies Ashok (Samsung) provides comments George (Ericsson) comments to Ashok. BTW the text that U are referring to below is now in 1014. George (Ericsson) responds to Ashok. Ashok (Samsung) responds to George (Ericsson) Yi (China Mobile) provides comment. Ashok (Samsung) provides r04 Leo (Deutsche Telekom) comments on r04 - cover sheet is not updated (clauses affected) ==== General Revisions Deadline ==== Yi (China Mobile) is ok with r04. George (Ericsson) Ericsson OK with Rev 04 Mu (Huawei) is OK with Rev 04 Rainer (Nokia) is ok with r04 ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501097 | CR | Approval | 23.228 CR1541R1 (Rel-19, 'C'): KI#2: Update to Network Capability Exposure Procedures | Ericsson, NTT DOCOMO | Rel-19 | Revision of S2-2500209r04. Approved | Agreed | |
| 19.2.2 | S2-2500210 | CR | Approval | 23.228 CR1542 (Rel-19, 'F'): KI#2: Udpdate to IMS AS Session Management Services | Ericsson | Rel-19 | Handle. Suggest to merge into S2-2500622 Merged into S2-2501098 | Yi (China Mobile) propose to merge this contribution into 0622 and provides comment. George (Ericsson) provides response ==== General Revisions Deadline ==== George (Ericsson) CR can be noted as it is merged. ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500621 | CR | Approval | 23.228 CR1549 (Rel-19, 'B'): Updates to IMS data channel capability exposure procedures | China Mobile | Rel-19 | Handle. Suggest to merge into S2-2501014, S2-2500209 Merged into S2-2501099 | Yi (China Mobile) is ok to merge thsi contribution to 0209 and 1014. George (Ericsson) provides comments ==== General Revisions Deadline ==== George (Ericsson) proposes to note the CR since it is merged ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500622 | CR | Approval | 23.228 CR1550 (Rel-19, 'B'): Updates to Nimsas_ImsSessionManagement Service | China Mobile | Rel-19 | Handle as basis for IMS AS service? r04 agreedrevised in e-mail session to S2-2501098, merging S2-2500210 | Yi (China Mobile) replies to George and proposes to use this contribution as the basis for service update. George (Ericsson) provides comments George (Ericsson) provides response Yi (China Mobile) provides r01. Mu (Huawei) propose to merge the corresponding parts in 0209 and 1014 in this CR Jari (NTT DOCOMO) provides r02, a merge from S2-2500967 Rainer (Nokia) asks for clarification George (Ericsson) asks a question in addition to what Nokia asked. Hao (ZTE) provides comments. Jari (NTT DOCOMO) comments George (Ericsson) can live with that. Please provide an update making it optional. Yi (China Mobile) replies to Rainer and provides r04. Yi (China Mobile) provides r03 to make session ID optional. Rainer (Nokia) comments George (Ericsson) first change is Ok but why U made it optional in the notification as well. ==== General Revisions Deadline ==== Yi (China Mobile) propose to go with r04 and can live with r03. Yi (China Mobile) confirm Jari's understanding. George (Ericsson) can live with r03 Jari (NTT DOCOMO) prefers r04 George (Ericsson) OK with R04, parameters are not properly aligned in both Rainer (Nokia) is ok with r04 but this needs further clarification iin next meeting ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501098 | CR | Approval | 23.228 CR1550R1 (Rel-19, 'B'): Updates to Nimsas_ImsSessionManagement Service | China Mobile, NTT DOCOMO | Rel-19 | Revision of S2-2500622r04, merging S2-2500210. Approved | Agreed | |
| 19.2.2 | S2-2500639 | CR | Approval | 23.228 CR1558 (Rel-19, 'B'): Clarification on DC Capability Exposure Procedure | ZTE | Rel-19 | Noted in e-mail session | George (Ericsson) proposes to note the CR. Ericsson CR covers these. ==== General Revisions Deadline ==== George (Ericsson) Please note the CR ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500823 | CR | Approval | 23.228 CR1568 (Rel-19, 'C'): Update Network Capability Exposure Procedure | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | George (Ericsson) proposes to note the CR ==== General Revisions Deadline ==== George (Ericsson) Please note the CR ==== Comments Deadline ==== | Noted |
| 19.2.2 | S2-2500950 | CR | Approval | 23.228 CR1576 (Rel-19, 'F'): HSS handling for subscription with IMS | Samsung | Rel-19 | Postponed in e-mail session | Yi (China Mobile) agree with George. George (Ericsson) proposes to postpone this CR ==== General Revisions Deadline ==== George (Ericsson) proposes to postpone the CR ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2500967 | CR | Approval | 23.228 CR1578 (Rel-19, 'B'): Complete the details for KI#2 | NTT DOCOMO | Rel-19 | Handle. Suggest to merge into S2-2501014, S2-2500209 Merged into S2-2501099 | Yi (China Mobile) propose to merge it into 1014, 0209 and 0622. George (Ericsson) proposes to use Nokia 1014 as a base and merge everything there. George (Ericsson) proposes to merge thin in 1014. Jari (NTT DOCOMO) is ok to merge it into 1014, 0209 and 0622. ==== General Revisions Deadline ==== George (Ericsson) proposes to note the CR as it is merged in other CRs. ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500971 | CR | Approval | 23.502 CR5311 (Rel-19, 'B'): Complete the details for KI#2 | NTT DOCOMO | Rel-19 | Postponed in e-mail session | George (Ericsson) provides r01 Yi (China Mobile) provides comment. Jari (NTT DOCOMO) responds ==== General Revisions Deadline ==== George (Ericsson) proposes to postpone the CR. Rainer (Nokia) needs to be postponed ==== Comments Deadline ==== | Postponed |
| 19.2.2 | S2-2501014 | CR | Approval | 23.228 CR1581 (Rel-19, 'F'): KI#2: Update of procedures | Nokia | Rel-19 | Handle as basis for updating and standalone DC r08 agreedrevised in e-mail session to S2-2501099, merging S2-2500170, S2-2500621 and S2-2500967 | George (Ericsson) provides r01 Jari (NTT DOCOMO) asks questions Jari (NTT DOCOMO) provides r02 George (Ericsson) provides comments Rainer (Nokia) provides r03 Rainer (Nokia) provides r04 Mu (Huawei) asks how to merge the changes on the service Rainer (Nokia) asks question on security concerns for KI2 Rainer (Nokia) provides r05 George (Ericsson) provides r06. Jari (NTT DOCOMO) comments George (Ericsson) request clarification George (Ericsson) Responds to Limu. Mu (Huawei) propose how to handle KI#2, and propose to only endorse 1014 George (Ericsson) responds to Ashok Ashok (Samsung) requests for clarification on r05 Yi (China Mobile) clarify the split of contributions of KI#2. Rainer (Nokia) replies and provides r07. Rainer (Nokia) repleis Ashok (Samsung) provides r08. George (Ericsson) All these 4 CRs can only be endorsed not approved. Far too may unchecked changes. George (Ericsson) provides response to Rainer Rainer (Nokia) is ok with r08 George (Ericsson) They are optional because we made them optional based on the the current service definition inclusion. We can chose to remove the optionality, and mandate that. 23.502 also made them optional Jari (NTT DOCOMO) responds to George George (Ericsson) We are talking about different things, I think. ==== General Revisions Deadline ==== George (Ericsson) is OK with R08 Yi (China Mobile) is ok with r08. Jari (NTT DOCOMO) is ok with r08. Mu (Huawei) is only OK to endorse r08 or any other version Rainer (Nokia) is ok to endorse r08 ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501099 | CR | Approval | 23.228 CR1581R1 (Rel-19, 'F'): KI#2: Update of procedures | Nokia, NTT DOCOMO, Ericsson | Rel-19 | Revision of S2-2501014r08, merging S2-2500170, S2-2500621 and S2-2500967. Endorsed | Endorsed | |
| 19.2.2 | S2-2501015 | CR | Approval | 23.502 CR5315 (Rel-19, 'F'): KI#2: Update the IMS session management service of NEF | Nokia | Rel-19 | Handle. Suggest to merge into S2-2500971 Proposed merged with S2-2500971 (postponed). Postponed | George (Ericsson) proposes to consider this CR merged in 971r01 where I included the Nokia change Rainer (Nokia) is k to merge 1015 into 971 ==== General Revisions Deadline ==== George (Ericsson) please note as the CR is merged with other CRs. Rainer (Nokia) is ok to mark 1015 as merged ==== Comments Deadline ==== | Postponed |
| 19.2.2 | - | - | - | KI#5: PS Data Off for services over IMS DC | - | - | Docs:=6 | - | |
| 19.2.2 | S2-2500171 | CR | Approval | 23.228 CR1533 (Rel-19, 'F'): Clarification on PS Data Off status change reporting to DCSF | Qualcomm Incorporated | Rel-19 | Handle r05 agreedrevised in e-mail session to S2-2501100, merging S2-2500626 and S2-2500637 | George (Ericsson) provides comments Ashok (Samsung) is not OK with the CR as questions are not answered yet. How IMS AS will inform to DCSF the 3GPP PS Data off status if it has lost the value because of IMS AS restart Kenny (Qualcomm) provides r01 to combine the changes from 626. Rainer (Nokia) provides r02 Ashok (Samsung) responds Mu (Huawei) comments on r02 Rainer (Nokia) replies Kenny (Qualcomm) replies comments from Rainer. Rainer (Nokia) replies to Kenny. Yi (China Mobile) provides comment and ask if 0637 should be merged in. Hao (ZTE) responds to Yi (CMCC): if group decides using this paper as baseline, 0637 from ZTE could be merged. Kenny (Qualcomm) provides r03 based comments from Rainer. Rainer (Nokia) is ok with r03 George (Ericsson) provides r04. Added the parameter in session establsihment event. Co-signed as well. Mu (Huawei) is OK with r04 and would like to co-sign Zhenhua (vivo) is OK with r04. Kenny (Qualcomm) is OK with r04. Rainer (Nokia) is ok with r04 George (Ericsson) please add Ericsson as co-signer Kenny (Qualcomm) provides r05 by adding more co-signers. Hao (ZTE) would like to co-sign the paper which merges the paper from ours. ==== General Revisions Deadline ==== George (Ericsson) OK with R04 Only Yi (China Mobile) is ok with r03 and not ok with r04 and r05. Kenny (Qualcomm) replies to Yi (China Mobile)'s comment. Mu (Huawei) is OK with r04 and r05, object to other revision Zhenhua (vivo) is OK with r04 and r05 Kenny(Qualcomm) proposes to agree r05 + adding ZTE as co-signer. Rainer (Nokia) agrees to agree r05 ==== Comments Deadline ==== | Revised |
| 19.2.2 | S2-2501100 | CR | Approval | 23.228 CR1533R1 (Rel-19, 'F'): Clarification on PS Data Off status change reporting to DCSF | Qualcomm Incorporated, Ericsson, Huawei, vivo, Nokia, ZTE | Rel-19 | Revision of S2-2500171r05, merging S2-2500626 and S2-2500637. Approved | Agreed | |
| 19.2.2 | S2-2500626 | CR | Approval | 23.228 CR1553 (Rel-19, 'B'): KI#5: Support of Data off feature for data channel | China Mobile | Rel-19 | Handle Merged into S2-2501100 | Kenny (Qualcomm) provides comments George (Ericsson) provides comments Yi (China Mobile) replies and explain by this solution notifying status during session establishment is not needed. Zhenhua (vivo) provides comments Kenny (Qualcomm) provides questions for clarification. Ashok (Samsung) provides comments Ashok (Samsung) provides response to George (Ericsson) Kenny (Qualcomm) provides comments and proposes to merge this CR with 171r01. Hao (ZTE) comments. George (Ericsson) provides comments inline Mu (Huawei) comments and propose to move forward with 0171 Yi (China Mobile) agrees to merge this CR into 0171. Ashok (Samsung) comments ==== General Revisions Deadline ==== George (Ericsson) proposes to note the CR. ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500637 | CR | Approval | 23.228 CR1556 (Rel-19, 'B'): Address EN on 3GPP PS Data Off Status Notification | ZTE | Rel-19 | Handle Merged into S2-2501100 | Kenny (Qualcomm) proposed comments. Hao (ZTE) proposes using this paper as baseline for PS Data Off handling. George (Ericsson) proposed to note the CR. The same is proposed in CMCC doc 626 Hao (ZTE) responds to Kenny (Qualcomm). Yi (China Mobile) provides comment. Hao (ZTE) responds to Yi (China mobile). Hao (ZTE) provides r01. Hao (ZTE) responds. Kenny (Qualcomm) provides comments. George (Ericsson) provides response Hao (ZTE) comments: if both event and parameter are needed for PS Data Off after discussion, this paper could be taken as baseline. Mu (Huawei) propose to merge this into 0626 ==== General Revisions Deadline ==== Kenny (Qualcomm) proposes the CR merged into 0171. George (Ericsson) proposes to note the CR. Hao (ZTE) agrees this paper merged into S2-2500171. ==== Comments Deadline ==== | Merged |
| 19.2.2 | S2-2500824 | CR | Approval | 23.228 CR1569 (Rel-19, 'D'): KI#5: Support of Data off feature for data channel | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500946 | CR | Approval | 23.228 CR1574 (Rel-19, 'F'): 3GPP PS Data off status for DCSF | Samsung | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) provides comments George (Ericsson) provides comments Zhenhua (vivo) share the same view as Kenny (Qualcomm) that HSS does not need to store PS Data Off status Yi (China Mobile) share the same view with Kenny and Zhenhua. Rainer (Nokia) shares the view of CMCC, QC, vivo Ashok (Samsung) provides response Mu (Huawei) comments Ashok (Samsung) responds to Mu (Huawei) Ashok (Samsung) comments George (Ericsson) provides comment. Kenny (Qualcomm) provides further comments. ==== General Revisions Deadline ==== Kenny (Qualcomm) proposes to note the CR. George (Ericsson) proposes to note the CR. Rainer (Nokia) agrees to note the CR Ashok (Samsung) agrees to note the CR ==== Comments Deadline ==== | Noted |
| 19.2.2 | - | - | - | KI#4: Authorization and authentication of third-party identities in IMS sessions | - | - | Docs:=3 | - | |
| 19.2.2 | S2-2500173 | CR | Approval | 23.228 CR1534 (Rel-19, 'F'): Clarification on third-party user ID provisioning procedure | Qualcomm Incorporated | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500949 | CR | Approval | 23.228 CR1575 (Rel-19, 'F'): Clarification on Third Party identity verification | Samsung | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2501012 | CR | Approval | 23.228 CR1579 (Rel-19, 'F'): KI#4: Update of procedure description | Nokia | Rel-19 | Not Handled | - | |
| 19.2.2 | - | - | - | KI#1: IMS events for DC communication | - | - | Docs:=4 | - | |
| 19.2.2 | S2-2500203 | CR | Approval | 23.228 CR1536 (Rel-19, 'F'): KI#1: Editorial updates to IMS Subscribe/Notify Framework Architecture | Ericsson | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500204 | CR | Approval | 23.502 CR5209 (Rel-19, 'F'): KI#1: Update to NEF Services | Ericsson | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500288 | CR | Approval | 23.228 CR1544 (Rel-19, 'F'): Adding more event filters for ADC media type | Vivo | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500620 | CR | Approval | 23.228 CR1548 (Rel-19, 'B'): Correction of detection criteria for event exposure | China Mobile | Rel-19 | Not Handled | - | |
| 19.2.2 | - | - | - | KI#3: Data channel interworking with MTSI UE | - | - | Docs:=3 | - | |
| 19.2.2 | S2-2500207 | CR | Approval | 23.228 CR1539 (Rel-19, 'F'): KI#3: Update to DC interworking with MTSI UE | Ericsson | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500291 | CR | Approval | 23.228 CR1465R2 (Rel-19, 'F'): Update on support of DC interworking | Vivo | Rel-19 | Revision of S2-2411943 Not Handled | - | |
| 19.2.2 | S2-2500623 | CR | Approval | 23.228 CR1551 (Rel-19, 'B'): Updates on procedure and service of DC interworking via DC AS | China Mobile | Rel-19 | Not Handled | - | |
| 19.2.2 | - | - | - | KI#6: Standalone IMS DC sessions | - | - | Docs:=3 | - | |
| 19.2.2 | S2-2500292 | CR | Approval | 23.228 CR1546 (Rel-19, 'D'): Modification on general description for standalone IMS DC session | Vivo | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500825 | CR | Approval | 23.228 CR1570 (Rel-19, 'F'): Correction on standalone data channel description | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.2.2 | S2-2500951 | CR | Approval | 23.228 CR1577 (Rel-19, 'F'): MMTel media removal clarification | Samsung | Rel-19 | Not Handled | - | |
| 19.3.1 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (FS_XRM_Ph2) | - | - | Docs:=0 | - | |
| 19.3.2 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2) | - | - | Docs:=140 | - | |
| 19.3.2 | - | - | - | LSs - Transport level marking based on PSI | - | - | Docs:=1 | - | |
| 19.3.2 | - | - | - | LSs - Transport level marking based on PSI | - | - | Docs:=1 | - | |
| 19.3.2 | S2-2500027 | LS In | Action | LS from CT WG4: Reply LS on Transport level marking based on PDU Set Importance | CT WG4 (C4-245408) | Rel-19 | Noted in e-mail session | Jinhua (Xiaomi) provides comments, proposes to Note this LS. SA2 Spec revised and no action required for CT4. | Noted |
| 19.3.2 | - | - | - | LSs - Roaming scenarios | - | - | Docs:=7 | - | |
| 19.3.2 | S2-2500011 | LS In | Action | LS from CT WG4: LS on Support of XRM services in Roaming scenarios | CT WG4 (C4-244534) | Rel-19 | Responses drafted in S2-2500127, S2-2500167, S2-2500380. Final response in S2-2501332. | Replied to | |
| 19.3.2 | S2-2500127 | LS OUT | Approval | [DRAFT] LS Reply on support of XRM services in Roaming scenarios | Nokia | Rel-18 | Baseline Response to S2-2500011. Revised in CC#4 to S2-2501332. | Dan Wang(China Mobile) provides r01 to only keep the attached document and remove all the detailed description. Please notice that this LS depends on the CR progress of S2-2500125/126 ==== General Revisions Deadline ==== Sebastian (Qualcomm) proposes to go with r00; objects to r01 as r01 is not sufficient given the discussion on the to-be-attached CR. Xiaowan(vivo) object to the original and revisions Xiaowan(vivo) for the sake of progress, revoke my objection ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501332 | LS OUT | Approval | LS Reply on support of XRM services in Roaming scenarios | SA WG2 | Rel-18 | Revision of S2-2500127. This LS OUT was approved | Approved | |
| 19.3.2 | S2-2500125 | CR | Approval | 23.501 CR5890 (Rel-18, 'F'): XRM services support in Roaming scenarios | Nokia | Rel-18 | r04 + changes agreed. Revised in CC#4 to S2-2501330. | Dan Wang(China Mobile) provides r01 to only support non-roaming and Local breakout roaming case. For HR roaming, I need more information to justify why it works. Lazaros Gkatzikis (Nokia) comments and proposes SoH in CC#01. Lazaros Gkatzikis (Nokia) provides r02. Mirko (Huawei) provides r03. Lazaros Gkatzikis (Nokia) provides r04 ==== General Revisions Deadline ==== Mirko (Huawei) replies and proposes to agree on r03. R04 is not acceptable to us. Sebastian (Qualcomm) can only accept r03 if the sentence 'XR services and interactive media services are supported in non-roaming, home-routed roaming and local breakout roaming scenarios.' is removed because we usually state if remaining is NOT supported); objects to other versions Georgios (Nokia) comments that this is discussed in wrong AI. Correct AI is 19.3.2 as in subject Lazaros Gkatzikis (Nokia) agrees with Sebastian and provides r05 as per proposal to keep only informative text. Xiaowan(vivo) object to the original version and all the revisions Xiaowan(vivo) for the sake of progress, revoke my objection ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501330 | CR | Approval | 23.501 CR5890R1 (Rel-18, 'F'): XRM services support in Roaming scenarios | Nokia | Rel-18 | Revision of S2-2500125r04 + changes. This CR was agreed | Agreed | |
| 19.3.2 | S2-2500126 | CR | Approval | 23.501 CR5891 (Rel-19, 'A'): XRM services support in Roaming scenarios-Mirror | Nokia | Rel-19 | Revised in CC#4 to S2-2501331. | Dan Wang(China Mobile) provides r01 to only support non-roaming and Local breakout roaming case. For HR roaming, I need more information to justify why it works. Sebastian (Qualcomm) replies ==== General Revisions Deadline ==== Sebastian (Qualcomm) comments that the mirror needs to be aligned with 125 ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501331 | CR | Approval | 23.501 CR5891R1 (Rel-19, 'A'): XRM services support in Roaming scenarios-Mirror | Nokia | Rel-19 | Revision of S2-2500126. This CR was agreed | Agreed | |
| 19.3.2 | - | - | - | LSs - Multiplexed Media Flows | - | - | Docs:=1 | - | |
| 19.3.2 | S2-2500023 | LS In | Action | LS from SA WG4: Reply LS on Introduction of Extensions to IP Packet Filters for Differentiated QoS Handling for Multiplexed Media Flows | SA WG4 (S4-242065) | Rel-19 | Postponed in e-mail session | Postponed | |
| 19.3.2 | - | - | - | LSs - Multimodality | - | - | Docs:=11 | - | |
| 19.3.2 | S2-2500014 | LS In | Action | LS from RAN WG2: Reply to SA2 LS on multi-modality awareness | RAN WG2 (R2-2409272) | Rel-19 | Responses drafted in S2-2500124, S2-2500162, S2-2500297, S2-2500752. Postponed in e-mail session | Postponed | |
| 19.3.2 | S2-2500015 | LS In | Action | LS from RAN WG3: Reply LS on multi-modality awareness at RAN | RAN WG3 (R3-245682) | Rel-19 | Postponed in e-mail session | Postponed | |
| 19.3.2 | S2-2500028 | LS In | Information | LS from SA WG4: LS Reply on multi-modality awareness | SA WG4 (S4-242223) | Rel-19 | Postponed in e-mail session | Postponed | |
| 19.3.2 | S2-2500050 | LS In | Action | LS from RAN WG3: Reply LS on multi-modality awareness | RAN WG3 (R3-247874) | Rel-19 | Response drafted in S2-2500540. Postponed in e-mail session | Postponed | |
| 19.3.2 | S2-2500074 | LS In | Action | LS from TSG SA: LS on multi-modality awareness | TSG SA (SP-241921) | Rel-19 | Responses drafted in S2-2500158, S2-2500447. Postponed in e-mail session | Postponed | |
| 19.3.2 | S2-2500162 | LS OUT | Approval | [DRAFT] Reply LS on multi-modality awareness | Qualcomm | Rel-19 | Response to S2-2500014. CC#4: Postponed | Dan Wang(China Mobile) provides r01 to only provide the CRs approved in SA2 to RAN2, to keep the LS simple. Mehrdad (Mediatek Inc.) is OK with r01 but objects to original version. Sebastian (Qualcomm) objects to r01 ==== General Revisions Deadline ==== Lazaros Gkatzikis (Nokia) provides r02 Mehrdad (Mediatek Inc.) provides r03 Paul (Ericsson) we can't agree to this revision. SA4 clarified that it is the application layer that deals with aspect of admission control and not any part of 5GS. Mehrdad (Mediatek Inc.) asks clarification from Ericsson whether you refer to r02 or r03. Note in r03 there is no reference to admission control Dan (China Mobile) can leave with r03, object r02, and think currently the CR is more important Sebastian (Qualcomm) provides r04 and objects to r03, r02, r01 Zhuoyun (vivo) only accepts r01. Jinhua (Xiaomi) provides comments, and support r03, Dan(China Mobile) only accept r01 and r03, object all the other version. Sebastian (Qualcomm) provides r05 on top of r04 to add RAN on the TO line; objects to r03, r02, r01 Mehrdad (Mediatek Inc.) is OK with r01 and r03 but objects to rest of revisions Sebastian (Qualcomm) replies to Mehrdad ==== Comments Deadline ==== Lazaros Gkatzikis (Nokia) provides r06 (result of offline discussions) Zhuoyun (vivo) comments on r06. | Postponed |
| 19.3.2 | S2-2500159 | CR | Approval | 23.501 CR5893 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | CC#4: Noted | Dan Wang(China Mobile) object to r00, and provides r01 Georgios (Nokia) replies to Dan Lazaros Gkatzikis (NOKIA) proposes to discuss the technical aspects of providing MMSID to RAN. Zhuoyun (vivo) prefers r01. Mengzhen (China Telecom) provides r02. Lazaros Gkatzikis (Nokia) provides comments and proposes SoH in CC#01. Mehrdad (Mediatek Inc.) prefers r01, can live with r02 but objects to original version. Sebastian (Qualcomm) objects to r01 Paul (Ericsson) provides r03 and aligns the text with the input provided by the SA LS. Youngkyo(Samsung) supports caring for joint admission control issue to solve SA4's concern. Mehrdad (Mediatek Inc.) prefers r03 to all revisions. This is the most accurate revision based on SA plenary outcome. Dan (China Mobile) provide r04 with only changing the NOTE. Dan(China Mobile) provides new Question for SoH. Xiaowan(vivo) request add Tdoc number for each SoH option and the corresponding Tdoc need refinement to align the vote option before the voting Georgios (Nokia) comments that we should first clarify technical topics as in offline discussion and copied also below Paul (Ericsson) provides comments reiterates that SA2 can specify MMSID provision to NG-RAN as per SA LS. John (Futurewei) shares the view from Paul (Ericsson) that MMSID to NG-RAN is sufficient. Mike (InterDigital) comments and provides a different interpretation of the SA LS. Sebastian (Qualcomm) agrees with Mike; asks Paul for clarification of comments on admission control John (Futurewei) is ok with r06. Mengzhen (China Telecom) prefers r06 Dan (China Mobile) support Paul that SA2 can specify MMSID provision to NG-RAN as per SA LS Dan(China Mobile) reply to Georgios about the question Boren (OPPO) provides clarification on single UE case Dan(China Mobile) reply to Mike Dan(China Mobile) OK with r06, and object r05 Dan (China Mobile) support SoH in this meeting CC#2 and move forward Youngkyo(Samsung) provides comment. Mike (InterDigital) asks questions and expresses concerns Sebastian (Qualcomm) objects to r01-r04 and provide r06 and r06 Jinhua (Xiaomi) provides technical comments, proposes to send MMSID with no more information. Georgios (Nokia) proposes a SoH on multimodality awareness at RAN in CC#2 unless meanwhile the team converges Georgios (Nokia) also agrees with Mike and Sebastian Svante (Sony) comments and propose a different wording on the NOTE. Zhuoyun (vivo) comments. Georgios (Nokia) there are more proposals now than on Monday in revisions, see the proposed slides Jari (NTT DOCOMO) provides r08 ==== General Revisions Deadline ==== Lazaros Gkatzikis (Nokia) provides r09 Dan (China Mobile) provides r10 Zhuoyun (vivo) comments on r09. Lazaros Gkatzikis (Nokia) replies to Dan. Dan(China Mobile) replies . Sebastian (Qualcomm) comments that we need to clearly rule out joint admission control in the CRs and LS to RAN2 as per SA4 feedback if there is no agreement to specify support for an AF to indicate that it wants joint admission control Lazaros Gkatzikis (Nokia) provides possible wording Dan (China Mobile)answer and propose possible wording Paul (Ericsson) we should work on a CR aligned with the SA LS. We do not agree to add more functionality. Dan(China Mobile) provide r11, only update the NOTE as below. Zhuoyun (vivo) is fine with r10, or r9 with the proposed wording by Dan or Lazaros on Note Y. Mehrdad (Mediatek Inc.) is OK with r11. Zhuoyun (vivo) is also OK with r11. Sebastian (Qualcomm) provides r12; can accept r12, r05, r06 and r00; objects to all other versions Paul (Ericsson) provides r13 and can only accept r03 and r13. Lazaros Gkatzikis (Nokia) proposes further compromise. Sebastian (Qualcomm) provides r14 Paul (Ericsson) provides r15. Dan (China Mobile) provides r16 based on r13 to correct the editorial issue Sebastian (Qualcomm) is fine with r15 Sebastian (Qualcomm) objects to r16 Ellen(Google) provides r17. we are OK r16, and r10 with title changes. Object r15/r14 and others that indicate what RAN can do or not do with this sentence: Joint admission control is not supported by 5GS based on MMSID. Sebastian (Qualcomm) objects to r17 Dan(China Mobile)object r15, prefer r16 Mehrdad (Mediatek Inc.) is OK with r11, r16 and r17 but objects to rest of revisions ==== Comments Deadline ==== Zhuoyun (vivo) is OK with r10, r11, r16 and r17, but objects to rest of revisions. Lazaros Gkatzikis (Nokia) provides r18 Paul (Ericsson) provides r19 as a compromise with a slightly modified NOTE wording: NOTE y: The Multi-modal Service ID provided by the AF can correspond to an agreement between an application provider represented by an AF and the 5GC operator. | Noted |
| 19.3.2 | S2-2500166 | CR | Approval | 23.503 CR1457 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile | Rel-19 | Noted in e-mail session | Yuang(ZTE) supports and would like to co-sign this CR. Dan(China Mobile) provide r01 with adding ZTE cosign. Paul (Ericsson) supports r02. Boren (OPPO) provides r02. Sebastian (Qualcomm) objects to all revisions, including r00 as we first need to agree the way forward on the 501 CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500262 | CR | Approval | 23.502 CR5225 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! Noted in e-mail session | Haley(Lenovo) asks for clarification. Mengzhen replies to Haley(Lenovo) and provide r01. Paul (Ericsson) provides r02 which is aligned with the scope of the SA LS. Sebastian (Qualcomm) objects to all revisions, including r00 as we first need to agree the way forward on the 501 CR and the align this CR accordingly ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500442 | DISCUSSION | Discussion | Discussion on providing multi-modal awareness to NG-RAN. | InterDigital Inc. | Rel-19 | Noted in e-mail session | Runze (Huawei) does not think the change is necessary. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500487 | DISCUSSION | Discussion | Discussion and proposals on multi-modal service awareness. | Samsung | Noted in e-mail session | Noted | ||
| 19.3.2 | - | - | - | KI#1: PDU Set based QoS handling enhancement | - | - | Docs:=12 | - | |
| 19.3.2 | S2-2500116 | CR | Approval | 23.503 CR1441R3 (Rel-19, 'B'): PDU Set support in QoS Notification Control and Alternative QoS | Nokia | Rel-19 | Baseline Revision of S2-2412652. r08 agreed. Revised in e-mail session to S2-2501101, merging S2-2501009 | Xiaowan ke(vivo) provides comments and doesn't see r01/r02/r03. Lazaros Gkatzikis (Nokia) provides r04 merging changes from the other 503 CRs. Georgios (Nokia) proposes to create a revision to merge 0307, 0899, 1009 Paul (Ericsson) provides comments and asks for clarification why the SMF needs to indicate to PCF what QoS parameters are used, what alternative QoS parameters are used and the direction. Georgios (Nokia) informs that r04 is the first available revision so please build on top of it and keep increasing the number to avoid confusion Lazaros Gkatzikis (Nokia) responds to questions and clarifies that r04 is the only revision available. Paul (Ericsson) provides r05 and removes changes where additional info is signalled to PCF/AF as no justification provided. Lazaros Gkatzikis (Nokia) provides extra context and asks for clarification by Paul. Paul (Ericsson) replies to Lazaros. Lazaros Gkatzikis (Nokia) replies to Paul. Dario (session chair): for clarity, r01, r02 and r03 were skipped and will not be available. Xiaowan(vivo) provides r06 Jinhua (Xiaomi) provides r07, and comments, Lazaros Gkatzikis (Nokia) provides r08 ==== General Revisions Deadline ==== Jinhua (Xiaomi) replies to Lazaros, and OK for r06,r07,r08 Paul (Ericsson) we can only accept r08 and r05 and object to all other revisions. Xiaowan(vivo) is ok with r08 Xiaowan(vivo) revoke the support on r08 and object to all the revision and the original version Lazaros Gkatzikis (Nokia) agrees to proceed with r08. ==== Comments Deadline ==== Xiaowan(vivo) for the sake of progress, revoke my objection | Revised |
| 19.3.2 | S2-2501101 | CR | Approval | 23.503 CR1441R5 (Rel-19, 'B'): PDU Set support in QoS Notification Control and Alternative QoS | Nokia, vivo, Huawei, HiSilicon, Xiaomi | Rel-19 | Revision of S2-2500116r08, merging S2-2501009. Approved | Agreed | |
| 19.3.2 | S2-2500307 | CR | Approval | 23.503 CR1465 (Rel-19, 'B'): KI#1, Support QoS Notification and AQP | Vivo | Rel-19 | Noted in e-mail session | Dario (Session Chair): @author, please confirm that this is merged into 00116 Paul (Ericsson) objects to any version for the sake of merging. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500899 | CR | Approval | 23.503 CR1417R2 (Rel-19, 'B'): Notification Control when PDU Set QoS parameters are available | Huawei, HiSilicon | Rel-19 | Revision of S2-2411914. Noted in e-mail session | Dario (Session Chair): @author, please confirm that this is merged into 00116 ==== General Revisions Deadline ==== Paul (Ericsson) object to all revisions of this CR. ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2501009 | CR | Approval | 23.503 CR1441R4 (Rel-19, 'B'): PDU Set support in QoS Notification Control and Alternative QoS | [Nokia], Xiaomi | Rel-19 | Merge into S2-2500116? Revision of S2-2412652. Merged into S2-2501101 | Dario (Session Chair): @author, please confirm that this is merged into 00116 Jinhua (Xiaomi) replies to Dario, confirmed that 01009 can be merged into 00116 for discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500706 | CR | Approval | 23.501 CR5524R6 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi | Rel-19 | Baseline Revision of S2-2412895. r10 agreed. Revised in e-mail session to S2-2501102, merging S2-2500115, S2-2500306 and S2-2501008 | Georgios (Nokia) proposes to create a revision to merge 0115, 0306, 0898 Jinhua (Xiaomi) provides comments, principle should be clarified when Set and normal QoS are applied for different direction. Xiaowan(vivo) replies to Jinhua (Xiaomi) Xiaowan(vivo) replies to Georgios (Nokia) Paul (Ericsson) provides r01. Jinhua (Xiaomi) replies to Xiaowan(vivo), Neutral for fulfilled QoS in profile (OP1) or across profiles (OP2), clarify the approach is necessary. Xiaowan(vivo) provides r02 Lazaros Gkatzikis (Nokia) agrees with Xiaowan's view, shares explanation and proposes to focus on the main part of the solution. Jinhua (Xiaomi) replies to Lazaros, Lazaros Gkatzikis (Nokia) replies to Jinhua Jinhua (Xiaomi) replies to Lazaros, clarification sentence is proposed. Jinhua (Xiaomi) replies to Xiaowan, Jinhua (Xiaomi) provides r07, Lazaros Gkatzikis (Nokia) provides r04 and r05 Xiaowan(vivo) give a compromise Xiaowan(vivo) object to r03, r04 and r05 and unexist r07 Xiaowan(vivo) clarifies and provide r06 Lazaros Gkatzikis (Nokia) objects to r06 and asks for clarification. Paul (Ericsson) asks question for clarification and provides r07. Chunshan(CATT) provides r08. Xiaowan(vivo) provide r10 ==== General Revisions Deadline ==== Lazaros Gkatzikis (Nokia) replies to Xiaowan Paul (Ericsson) we can only accept r01, r07 and r10 and object to all other revisions. Chunshan (CATT) can accept r10, r09, r08,r07, r00 and object r01,r02, r03, r04,r05,r06 Lazaros Gkatzikis (Nokia) agrees on r08 or r10 with the following changes. Xiaowan(vivo) replies to Lazaros Gkatzikis (Nokia) that disagree the change your request Lazaros Gkatzikis (Nokia) indicates that can live with r10 as is for the sake of progress. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501102 | CR | Approval | 23.501 CR5524R9 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi | Rel-19 | Revision of S2-2500706r10, merging S2-2500115, S2-2500306 and S2-2501008. Approved | Agreed | |
| 19.3.2 | S2-2500115 | CR | Approval | 23.501 CR5886 (Rel-19, 'B'): Suppport indication of PDU Set QoS in Notification Control | Nokia | Rel-19 | Merge into S2-2500706? Merged into S2-2501102 | Dario (Session Chair): @author, please confirm that this is merged into 00706 Paul (Ericsson) objects to any version for the sake of merging Lazaros Gkatzikis (Nokia) clarifies that the CR has been merged in 2500706r05. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500306 | CR | Approval | 23.501 CR5920 (Rel-19, 'B'): KI#1, Support QoS Notification and AQP | Vivo | Rel-19 | Merge into S2-2500706? Merged into S2-2501102 | Dario (Session Chair): @author, please confirm that this is merged into 00706 Xiaowan(vivo) confirm that this is merged into 00706 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500898 | CR | Approval | 23.501 CR5524R7 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | Huawei, HiSilicon [, CATT, Nokia, Tencent, vivo, Samsung, Xiaomi] | Rel-19 | Revision of S2-2412895. Noted in e-mail session | Dario (Session Chair): @author, please confirm that this is merged into 00706 ==== General Revisions Deadline ==== Paul (Ericsson) objects to that CR in all revisions. ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2501008 | CR | Approval | 23.501 CR5524R8 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | [CATT, Nokia, Tencent, vivo, Samsung,] Xiaomi | Rel-19 | Merge into S2-2500706? Revision of S2-2412895. Merged into S2-2501102 | Lazaros Gkatzikis (Nokia) objects and comments. Jinhua (Xiaomi) replies to Lazaros (Nokia), keep set separate from normal QoS is fine, but it is applied per direction. Always try to fulfil the QoS profile or AQP reselected should be clarified. Dario (Session Chair) points out that both 01008 and 00706 are revisions of the same CR5524 vs. TS 23.501, therefore only one of the two can be agreed. Jinhua (Xiaomi) replies to Dario, confirmed that 01008 can be merged into 00706 for discussion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2501003 | DISCUSSION | Approval | Discussion on one direction PDU Set support in Alternative QoS Profile . | Xiaomi | Rel-19 | Noted in e-mail session | Noted | |
| 19.3.2 | - | - | - | KI#2: Support for end-to-end encrypted traffic | - | - | Docs:=13 | - | |
| 19.3.2 | S2-2500183 | CR | Approval | 23.502 CR5081R5 (Rel-19, 'B'): Procedures for handling end-to-end encrypted XRM flows | Google, Futurewei, InterDigital Inc., China Mobile, Huawei, HiSilicon, Ericsson, Nokia | Rel-19 | Revision of S2-2412657. r10 agreed. Revised in e-mail session to S2-2501103, merging S2-2500224 | Laurent (Nokia): provides r01 Sudeep (Apple) has questions for clarification. Ellen (Google) provides r02 based on r01 and replies to Apple's questions Xinpeng(Huawei) provides r03. Laurent (Nokia): provides r04 Laurent (Nokia): provides r05 Xinpeng(Huawei) provides r07. Xinpeng(Huawei) replies to Ellen (Google) and Sudeep (Apple). Ellen (Google): provides r06 Ellen (Google) is fine with r07. Paul (Ericsson) provides r08. Laurent (Nokia): provides r09 Paul (Ericsson) provides r10. ==== General Revisions Deadline ==== Laurent (Nokia): Prefers R09/R10; Can live with R08 to R04 both included. Objects to other versions Laurent (Nokia): indicates a few typos that should be corrected when cleaning up the CR Ellen (Google) OK with R10 + fix typos indicated by Laurent (Nokia) Xinpeng(Huawei) is fine with r10,R9,R8,R7, and objects to all other revisions. Paul (Ericsson) object to r00, r01, r02, r03, r04, r05, r06, r07. We prefer r10 and can accept r08, r09. Dan (China Mobile) Paul object 0295 r02 because of the PDU session establishment procedure, which is involved the discussion of 0183 i.e. this paper, I suggest to handle this paper and 0295 together. Dan(China Mobile) object all versions of this paper , request to hanle this one with 0295 together because of Ericsson's behavior in 0295, request this paper to be discussed in CC#3 or C#4. Georgios (Nokia) acknowledges the request. Dario please be aware. CMCC, Ericsson could we find a way-out? Dan(China Mobile) withdraw the objection. since Paul withdraw the objection in 0295. Dan (China Mobile) this problem has be resolved. both objections have been withdraw. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501103 | CR | Approval | 23.502 CR5081R6 (Rel-19, 'B'): Procedures for handling end-to-end encrypted XRM flows | Google, Futurewei, InterDigital Inc., China Mobile, Huawei, HiSilicon, Ericsson, Nokia, Apple | Rel-19 | Revision of S2-2500183r10, merging S2-2500224. Approved | Agreed | |
| 19.3.2 | S2-2500224 | CR | Approval | 23.502 CR5213 (Rel-19, 'B'): Nnrf_NFDiscovery service enchancement for MoQ relay discovery | Huawei, HiSilicon | Rel-19 | Merge into S2-2500183? Merged into S2-2501103 | Laurent (Nokia): suggests to Note this Tdoc that is fully covered by 0183 Xinpeng(Huawei) proposes merged this CR into 0183. ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500295 | CR | Approval | 23.502 CR5027R2 (Rel-19, 'B'): Procedure of MoQ-based PDU Set Information identification for encrypted traffic | China Mobile | Rel-19 | Revision of S2-2411413. r02 agreed. Revised in e-mail session to S2-2501104. | Laurent (Nokia): suggests to concentrate on a single 23.502 CR about PDU session management procedures in Tdoc 0183 and makes technical comments Laurent (Nokia): provides R01 concentrating on § 4.17.6.1 Laurent (Nokia): provides R02 Dan (China Mobile) OK with r02 Paul (Ericsson) provides r03. Laurent (Nokia): changes to clause related with PDU session management (e.g. 4.3.3.2 ) should be in a single Tdoc 0183 (selected at last meeting) Dan (China Mobile) prefer r02 and let's discuss procedure in 0183 ==== General Revisions Deadline ==== Laurent (Nokia): objects to any R00 and R03 Dan (China Mobile) suggest to approve r02, Laurent just say object r00 and r03 Paul (Ericsson) can only accept r03 and object to r00, r01 and r02. Dan (China Mobile) cannot accept Paul object r02,it is unfair. we have said the procedure of this paper has been move to 0183, and now you object r02 because there is no procedure, I request this to be discussed in CC#3 or CC#4. Paul (Ericsson) withdraws the objection to r02. We can accept r03, r02 and object to r00, r01. Laurent (Nokia): objects to R00 and R03. Laurent can happily live with R01 and R02. Sorry for the confusion ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501104 | CR | Approval | 23.502 CR5027R3 (Rel-19, 'B'): Procedure of MoQ-based PDU Set Information identification for encrypted traffic | China Mobile | Rel-19 | Revision of S2-2500295r02. Approved | Agreed | |
| 19.3.2 | S2-2500296 | CR | Approval | 23.501 CR5917 (Rel-19, 'F'): Corrections for KI#2 Support of transferring media related information over N6 | China Mobile | Rel-19 | Coordinate with S2-2500957 if needed r07 agreedrevised in e-mail session to S2-2501105, merging S2-2500223, S2-2500405, S2-2500431 and S2-2501005 | Xinpeng(Huawei) provides r02. Dan(ChinaMobile) provides r03, to merge 0223, 0431, 1005, 0405 into this paper. Jari (NTT DOCOMO) provides r04 Xinpeng(Huawei) provides r05. Laurent (Nokia): provides r06 Xinpeng(Huawei) replies to Laurent(Nokia). Xinpeng(Huawei) objects to r06 and provides r07. Jinhua (Xiaomi) confirms proposl with 1005 merged in. R07 is preferred. Dan (China Mobile) OK with r07. ==== General Revisions Deadline ==== Mike (InterDigital) confirms support for r07 Xinpeng(Huawei) is fine with r07, r05, r02, objects to all other revison/origin version. Laurent (Nokia): is fine with R07, R06 ; objects to all other versions. Paul (Ericsson) we prefer r07, can accept r06 and object to r00, r01, r02, r03, r04, r05. Dan(China Mobile) suggest to go with r07. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501105 | CR | Approval | 23.501 CR5917R1 (Rel-19, 'F'): Corrections for KI#2 Support of transferring media related information over N6 | China Mobile, Huawei, Hisilicon, Interdigital, Xiaomi, Ericsson, NTT DOCOMO, Nokia | Rel-19 | Revision of S2-2500296r07, merging S2-2500223, S2-2500405, S2-2500431 and S2-2501005. Approved | Agreed | |
| 19.3.2 | S2-2500223 | CR | Approval | 23.501 CR5903 (Rel-19, 'F'): Clarifications for KI#2 | Huawei, Hisilicon | Rel-19 | Merge into S2-2500296? Merged into S2-2501105 | Xinpeng(Huawei) proposes merge this CR into 0296. Laurent (Nokia): objects to any version for the sake of merging Paul (Ericsson) provides r01. Paul (Ericsson) we are ok to merge 223 in 296. ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500431 | CR | Approval | 23.501 CR5951 (Rel-19, 'F'): Correcting a Reference | InterDigital Inc. | Rel-19 | Merge into S2-2500296? Merged into S2-2501105 | Xinpeng(Huawei) proposes merge this CR into 0296. Laurent (Nokia): objects to any version for the sake of merging ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2501005 | CR | Approval | 23.501 CR6051 (Rel-19, 'F'): XRM_Ph2_References corrections in Clause 5.37.9 | Xiaomi | Rel-19 | Merge into S2-2500296? Merged into S2-2501105 | Xinpeng(Huawei) proposes to merge this CR into 0296. Laurent (Nokia): objects to any version for the sake of merging Jinhua (Xiaomi) confirms the merged proposl with 0296, and reply to Laurent (Nokia). ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500405 | CR | Approval | 23.501 CR5940 (Rel-19, 'F'): Reference and editorial corrections to TS 23.501 | Ericsson | Rel-19 | Merge into S2-2500296? Merged into S2-2501105 | Xinpeng(Huawei) proposes to merge this CR into 0296. Paul (Ericsson) confirm merging of 405 into 0296. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500406 | CR | Approval | 23.503 CR1394R4 (Rel-19, 'B'): PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson [, InterDigital] | Rel-19 | Baseline Revision of S2-2412658. r06 agreed. Revised in e-mail session to S2-2501106. | Xinpeng(Huawei) comments and provides r01. Laurent (Nokia): provides r02 Sudeep (Apple) provides comments. Xinpeng(Huawei) provides r03 and replies to Laurent(Nokia). Ellen (Google) provides r04 to correct references. Laurent (Nokia): provides r05 Xinpeng(Huawei) provides r06. ==== General Revisions Deadline ==== Mike (InterDigital) confirms support for r06 Xinpeng(Huawei) is fine with r06, r05, r04, r03, and objects to all other revisions/original version. Laurent (Nokia): prefers R06 or R05, can live with R02 to R04 both included; Laurent objects to other versions Laurent (Nokia): suggests a correction at the end of R05/R06 Paul (Ericsson) we prefer r05 but can accept all revisions. Ellen (Google) OK for r06/05 ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501106 | CR | Approval | 23.503 CR1394R5 (Rel-19, 'B'): PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson [, InterDigital] Nokia, Google, Huawei, HiSilicon | Rel-19 | Revision of S2-2500406r06. Not handled at CC#4. Postponed | Postponed | |
| 19.3.2 | - | - | - | KI#3: DSCP marking over N3/N9 | - | - | Docs:=3 | - | |
| 19.3.2 | S2-2500909 | CR | Approval | 23.501 CR6035 (Rel-19, 'B'): Addressing differences in PDU Set importance usage for DSCP marking over N3/N9 in the transport network | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jinhua (Xiaomi) provides comments about PSI Range provision, and proposes to merge 0909 into S2-2501004 for discussion. Lazaros Gkatzikis (Nokia) questions CR usefulness and provides comments and revision r01. Paul (Ericsson) object to r00 and r01 of this CR. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2501004 | CR | Approval | 23.501 CR6050 (Rel-19, 'B'): XRM_Ph2_KI3 Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network | Intel, InterDigital Inc, China Telecom, Nokia, Tencent, Xiaomi | Rel-19 | Baseline r03 agreedrevised in e-mail session to S2-2501107. | Georgios (Nokia) proposes to create a revision to merge 0909 Mirko (Huawei) provides comments. Jinhua (Xiaomi) provides 1004r01 with 0909 merged in, and comments about PSI Range provision. Lazaros Gkatzikis (Nokia) provides r03 and r04 Paul (Ericsson) provides r02. ==== General Revisions Deadline ==== Jinhua (Xiaomi) replies to Lazaros, Paul and Mirko Paul (Ericsson) we prefer r02, can live with r02, r03 and r04 and we object to r00 and r01. Jinhua (Xiaomi) replies, and r03 is proposed. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501107 | CR | Approval | 23.501 CR6050R1 (Rel-19, 'B'): XRM_Ph2_KI3 Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network | Intel, InterDigital Inc, China Telecom, Nokia, Tencent, Xiaomi | Rel-19 | Revision of S2-2501004r03. Approved | Agreed | |
| 19.3.2 | - | - | - | KI#4: Traffic detections/QoS flow mapping for multiplexed data flows | - | - | Docs:=13 | - | |
| 19.3.2 | S2-2500410 | CR | Approval | 23.501 CR5942 (Rel-19, 'B'): KI#4 EN removal | Ericsson | Rel-19 | Postponed | Georgios (Nokia) objects to all revisions of this document. ==== Comments Deadline ==== | Postponed |
| 19.3.2 | S2-2500458 | CR | Approval | 23.501 CR5958 (Rel-19, 'F'): KI#4: Correct the RTCP MID for IP packet filter set | China Mobile, Lenovo | Rel-19 | r01 agreedrevised in e-mail session to S2-2501108. | Tianji (CMCC) provides r01 Georgios (Nokia) proposes to merge this to 0957 Paul (Ericsson) we prefer to have separate thread on both CRs. Tianji (CMCC) agrees with Ericsson and would like to keep #00458 and #00957 separate. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501108 | CR | Approval | 23.501 CR5958R1 (Rel-19, 'F'): KI#4: Correct the RTCP MID for IP packet filter set | China Mobile, Lenovo | Rel-19 | Revision of S2-2500458r01. Approved | Agreed | |
| 19.3.2 | S2-2500650 | CR | Approval | 23.503 CR1388R4 (Rel-19, 'B'): Traffic detection and QoS handling of multiplexed data flows | OPPO, Xiaomi, Lenovo, [Ericsson, Huawei, HiSilicon, Samsung,Nokia, NTT DOCOMO, vivo] | Rel-19 | Baseline Revision of S2-2412660. r05 agreed. Revised in e-mail session to S2-2501109, merging S2-2500999 and S2-2501036 | Boren (OPPO) provides r01 Georgios (Nokia) asks clarification on NOTE Y1 Boren (OPPO) comments Georgios (Nokia) replies on the NOTE Y1 Jari (NTT DOCOMO) proposes to merge with S2-2500999 Jari (NTT DOCOMO) comments Paul (Ericsson) comments and provides r02 Boren (OPPO) prefers to handle S2-2500650 separately which focuses on the unencrypted traffics, as per rapporteur's guidance. Georgios (Nokia) is OK with r02, further provides r03 Xiaowan(vivo) try to help for the definition of media flow Mengzhen(China Telecom) comments that we should have a clear definition of media flow. Tianji (CMCC) clarifies the purpose of 'NOTE Y1' and provides r04 Tianji (CMCC) suggests using S2-2500650 as the baseline to focus on the plaintext XR media traffics. Boren (OPPO) provides r05 Jari (NTT DOCOMO) comments: this one and S2-2500650 revise the same CR, so we cannot approve both. Jari (NTT DOCOMO) comments: S2-2500650 and S2-2500999 revise the same CR, so we cannot approve both. Ellen (Google) comments for downlink direction and provides r06 Tianji (CMCC) OK with the r05 Jari (NTT DOCOMO) responds to Ellen (Google) Boren (OPPO) provides clarification to Ellen (Google) ==== General Revisions Deadline ==== Ellen (Google) thanks for clarification from Jari (NTT DOCOMO) and Boren (oppo), and can live with r04 with this change: The PCF determines the PCC Rules and QoS requirements for the media flows under consideration of the UE support for (S)RTP Multiplexed Media Identification Information in IP Packet Filters as follows Boren (OPPO) suggests to go with r05 + change from Ellen (Google): The PCF determines the PCC Rules and QoS requirements for the media flows under consideration of the UE support for (S)RTP Multiplexed Media Identification Information in IP Packet Filters as follows Georgios (Nokia) is OK and supports the proposal as described below Paul (Ericsson) we object to r00, r01 and r04. We prefer r05 or r05 plus change as proposed by OPPO and we can accept all other revisions. Boren (OPPO) clarify the latest version is r05 + remove 'under consideration of the UE support for (S)RTP Multiplexed Media Identification Information in IP Packet Filters'. Tianji (CMCC) can accept r05, and 'r05 + remove 'under consideration of the UE support for (S)RTP Multiplexed Media Identification Information in IP Packet Filters'. Object r04. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501109 | CR | Approval | 23.503 CR1388R7 (Rel-19, 'B'): Traffic detection and QoS handling of multiplexed data flows | OPPO, Xiaomi, Lenovo, [Ericsson, Huawei, HiSilicon, Samsung], Nokia, [NTT DOCOMO, vivo] | Rel-19 | Revision of S2-2500650r05, merging S2-2500999 and S2-2501036. Not handled at CC#4. Postponed | Postponed | |
| 19.3.2 | S2-2501036 | CR | Approval | 23.503 CR1388R6 (Rel-19, 'B'): KI#4: Clarify the ambiguity of QoS requirements of media-flow vs. data-flow | [OPPO, Ericsson(?), Huawei(?), HiSilicon(?), Samsung, Nokia, NTT DOCOMO, Xiaomi, vivo, Lenovo], China Mobile | Rel-19 | Merge into S2-2500650? Revision of S2-2412660. Confirm Sources! Merged into S2-2501109 | Dario (Session Chair): @author, please confirm that this is merged into 00650. Tianji (CMCC) confirms the merge into 00650. Tianji (CMCC) proposes to merge this CR into #00650. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500703 | CR | Approval | 23.502 CR4927R5 (Rel-19, 'B'): Support multiplexing media traffic with additional Packet Filter | CATT, Nokia, OPPO, Lenovo, Samsung, Xiaomi | Rel-19 | Baseline Revision of S2-2412661. Not handled at CC#4. Postponed | Mengzhen (China Telecom) comments. Chunshan (CATT) replies the comments. Paul (Ericsson) provides additional comments. Chunshan (CATT) provides r01. Mirko (Huawei) provides comments. ==== General Revisions Deadline ==== Paul (Ericsson) we can accept r01. Mirko (Huawei) can accept r01 if the changes to clause 4.3.3.2 are taken out. Chunshan(CATT) thinks some changes are still needed in clause 4.3.3.2, it is accept to take the changes to clause 4.3.3.2. @Dario, please add this paper into CC#4 to remove the changes in clause 4.3.3.2. ==== Comments Deadline ==== | Postponed |
| 19.3.2 | S2-2500904 | CR | Approval | 23.503 CR1497 (Rel-19, 'F'): Event triggers related to QoS handling of multiplexed data flows | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Paul (Ericsson) provides comments. Mirko (Huawei) replies to the comments. ==== General Revisions Deadline ==== Paul (Ericsson) object to all revisions of that CR. ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500957 | CR | Approval | 23.501 CR6042 (Rel-19, 'B'): Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO | Rel-19 | Postponed in e-mail session | Xiaowan(vivo) provides r01 Tianji (CMCC) has concern of the technical validity to address encrypted multiplexed media flows Xinpeng(Huawei) provides r02. Georgios (Nokia) provides r03 Paul (Ericsson) asks to discuss flaws in the solutions captured in 0957 as observed in 0409 before moving forward with the CRs. We also ask in that context to discuss solution 0409 addressing these flaws. Dimitris (Lenovo) comments Tianji (CMCC) provides r04: remove 'MID' related changes; will change 'MID' part in #00458 Xinpeng(Huawei) replies to Georgios (Nokia). Paul (Ericsson) replies to Dimitris. ==== General Revisions Deadline ==== Georgios (Nokia) proposes to postpone the Tdoc for this meeting ==== Comments Deadline ==== | Postponed |
| 19.3.2 | S2-2500308 | CR | Approval | 23.501 CR5921 (Rel-19, 'B'): Support of DL Multiplexed Media Identification Information for end-to-end ciphered traffic | Vivo | Rel-19 | Merge into S2-2500957? Proposed merged with S2-2500957 (postponed). Postponed | Xiaowan(vivo) replies to Georgios (Nokia) Georgios (Nokia) asks for clarification on Track Alias. Resending removing text not needed from IETF draft in the previous message. Paul (Ericsson) asked if 308 was supposed to be merged into 957? Please clarify. Xiaowan(vivo) confirms S2-2500308 is merged into S2-2500957 <file:///E:/101%20SA2%20Meeting/SA2%23166AH%20202501/INBOX/Chair_Notes/Docs/S2-2500957.zip> ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.3.2 | S2-2500999 | CR | Approval | 23.503 CR1388R5 (Rel-19, 'B'): Traffic detection and QoS handling of multiplexed data flows | [OPPO, Ericsson, Huawei, HiSilicon, Samsung], NTT DOCOMO, Nokia, [Xiaomi, vivo, Lemovo] | Rel-19 | Baseline for encrypted multiplexed traffic Revision of S2-2412660. Merged into S2-2501109 | Boren (OPPO) proposes to merge this to 0650. Xiaowan(vivo) share the view with Boren (OPPO) to merge this to 0650 or remove the overlapped part with 0650 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500350 | DISCUSSION | Discussion | Discussion on Multiplexed Media Identification Information for end-to-end ciphered traffic. | Vivo | Rel-19 | Noted in e-mail session | Paul (Ericsson) provides comments. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.3.2 | S2-2500409 | DISCUSSION | Agreement | Solving KI#4 with N6 metadata using KI#2 mechanisms . | Ericsson | Noted in e-mail session | Noted | ||
| 19.3.2 | - | - | - | KI#5: QoS handling in case of dynamic traffic characteristics | - | - | Docs:=10 | - | |
| 19.3.2 | S2-2500309 | CR | Approval | 23.501 CR5922 (Rel-19, 'F'): KI#5, Update to data burst related | Vivo | Rel-19 | r01 agreedrevised in e-mail session to S2-2501110. | Paul (Ericsson) provides r01. ==== General Revisions Deadline ==== Jinhua (Xiaomi) provides comments, and OK for R01. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501110 | CR | Approval | 23.501 CR5922R1 (Rel-19, 'F'): KI#5, Update to data burst related | Vivo | Rel-19 | Revision of S2-2500309r01. Approved | Agreed | |
| 19.3.2 | S2-2500848 | CR | Approval | 23.501 CR5651R6 (Rel-19, 'B'): 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, CATT, China Telecom, Meta USA, CMCC, Xiaomi, Samsung, Huawei, HiSilicon, Ericsson, Nokia | Rel-19 | Baseline Revision of S2-2412944. CC#4: r05 + changes agreed. Revised in CC#4 to S2-2501353. | Chunshan (CATT) proposes some comments on N6 metadata mechanism. Sudeep (Apple) provides comment. Mirko (Huawei) provides comments and still disagrees with the detection of the non-boosted traffic based on ETI=False. Georgios (Nokia) replies to Mirko Paul (Ericsson) replies to Mirko, Sudeep and Georgios. Haley (Lenovo) replies. Lei (Tencent) provide comments and fine to follow the majority view to move forward. Mirko (Huawei) replies to the comments. Paul (Ericsson) replies to Mirko. Lei(Tencent) provides comments to Mirko (Huawei). Chunshan (CATT) provides r02. Haley (Lenovo) replies and provides r01. Lei(Tencent) provides comments and ask people's view about way forward in this meeting. Mirko (Huawei) provides r03. Paul (Ericsson) provides r04. Georgios (Nokia) is OK and supports r04 Haley(Lenovo) replies. Chunshan(CATT) provides r04. Haley(Lenovo) provides r06. Haley(Lenovo) provides r07 based on r05 and r06. ==== General Revisions Deadline ==== Sudeep (Apple) supports r07 and provides an additional suggestion to remove (70-99 decimal). Paul (Ericsson) we prefer r01, we can accept r00, r02, r04, r05, r06 and object to r03 and r07. Lei(Tencent) comments that there is very little difference between r06 and r07 thus it unclear why ok with r06 but object 07. Jinhua (Xiaomi) provides comments, and OK with r07/update by Sudeep. Mirko (Huawei) suggests a way forward. Haley (Lenovo) replies to Jinhua. Haley(Lenovo) explains that r07 is a combination of r05 and r06 and asks Paul why to object r07 but accept r05 and r06. Paul (Ericsson) replies to Mirko and Haley. Mirko (Huawei) replies to the Paul's comment. Paul (Ericsson) We agree to R06 plus 'remove (70-99 decimal) But we do not agree to add the EN saying 'Whether the ETI=False is used in the PCC rule for the non-expedited media flow is FFS.' Haley (Lenovo) replies to Mirko. Georgios (Nokia) is OK with r06 + remove (70-99 decimal) Chunshan (CATT) supports r05, r07 and plus 'remove (70-99 decimal)' , and objects r04,r06. Lei (Tencent) think as no objection to r05, so let's go with r05 plus 'remove (70-99 decimal)' , hope this is ok to all. Mirko (Huawei) replies to the Paul's comment. We are ok with r06 + remove (70-99 decimal) + an editor's note 'Whether the ETI=False is used in the PCC rule for the non-expedited media flow is FFS.' Haley (Lenovo) is ok to go with r05 plus 'remove (70-99 decimal)' trying to make progress. Georgios (Nokia) is also OK to go with r05 + remove (70-99 decimal). Haley(Lenovo) suggests to go with r05 plus removal of removal 70-99(decimal)+EN if no objection to EN. otherwise, go with r05+removal 70-99(decimal). Georgios (Nokia) objects to the EN. Can go with r05 or r06 and removal of 70-99 decimal ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501353 | CR | Approval | 23.501 CR5651R7 (Rel-19, 'B'): 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, CATT, China Telecom, Meta USA, CMCC, Xiaomi, Samsung, Huawei, HiSilicon, Ericsson, Nokia, Apple | Rel-19 | Revision of S2-2500848r05 + changes. This CR was agreed | Agreed | |
| 19.3.2 | S2-2500849 | CR | Approval | 23.502 CR5015R4 (Rel-19, 'B'): 23.502 Data boosting triggered by AS | Lenovo, Tencent, Tencent Cloud,CATT, China Telecom, Meta USA | Rel-19 | Baseline Revision of S2-2412712. CC#4: r02 agreed. Revised in CC#4 to S2-2501352. | Haley (Lenovo) provides r02. Haley (Lenovo) provides r01. ==== General Revisions Deadline ==== Paul (Ericsson) we prefer r02, can accept r00 and object r01. Mirko (Huawei) asks for taking out the change to clause 4.3.3.2 before agreeing the CR. Georgios (Nokia) accepts only r02. r00 has wrong references and it is objected. r01 is corrupted file and objected. Haley (Lenovo) replies to Mirko and is ok to go with r02+move out the change to clause 4.3.3.2. Lei(Tencent) is also ok to go with 'r02+move out the change to clause 4.3.3.2' to make progress. Georgios (Nokia) also accepts to remove impact to 4.3.3.2 from r02 Paul (Ericsson) replies to Mirko. Lei(Tencent) provides comments and think we can live with 'r02+move out the change to clause 4.3.3.2.' and do more refinement in next meeting. Mirko (Huawei) replies to Paul's comment. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501352 | CR | Approval | 23.502 CR5015R5 (Rel-19, 'B'): 23.502 Data boosting triggered by AS | Lenovo, Tencent, Tencent Cloud,CATT, China Telecom, Meta USA | Rel-19 | Revision of S2-2500849r02. This CR was agreed | Agreed | |
| 19.3.2 | S2-2500958 | CR | Approval | 23.503 CR1448R3 (Rel-19, 'B'): Enhancements for AF/AS triggered expedite data transfer | Nokia, [Xiaomi, Tencent, Tencent Cloud], InterDigital Inc. | Rel-19 | Baseline Revision of S2-2412713. r02 agreed. Revised in e-mail session to S2-2501111. | Paul (Ericsson) provides r01. Georgios (Nokia) is OK with r01 and provides a comment Paul (Ericsson) replies to Georgios. Georgios (Nokia) replies to Paul Georgios (Nokia) agrees with Paul's proposal Mike (InterDigital) also agreed with the proposal from Paul (Ericsson) and provides r02 ==== General Revisions Deadline ==== Lei(Tencent) prefers r01, also accept r02. Georgios (Nokia) prefers r02 and proposes to proceed with r02 Haley (Lenovo) is ok with both r01 and r02. Paul (Ericsson) we prefer r01, can accept r02 and object to r00. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501111 | CR | Approval | 23.503 CR1448R4 (Rel-19, 'B'): Enhancements for AF/AS triggered expedite data transfer | Nokia, Tencent, Tencent Cloud, InterDigital Inc. | Rel-19 | Revision of S2-2500958r02. Approved | Agreed | |
| 19.3.2 | S2-2500961 | CR | Approval | 23.502 CR5310 (Rel-19, 'F'): Support Time to Next Burst provisioning to NG-RAN | Nokia | Rel-19 | Approved | Agreed | |
| 19.3.2 | S2-2500847 | DISCUSSION | Information | Discussion on the remaining issues of expedited data transfer scheme. | Lenovo, Tencent, Tencent Cloud, Ericsson | Rel-19 | Noted in e-mail session | Noted | |
| 19.3.2 | - | - | - | KI#9: Information exposure - rate limitation | - | - | Docs:=7 | - | |
| 19.3.2 | S2-2500310 | CR | Approval | 23.503 CR1381R4 (Rel-19, 'B'): KI#9, Support of Rate limitation | Vivo, Meta USA, Tencent, Nokia | Rel-19 | Baseline Revision of S2-2412718. r02 agreed. Revised in e-mail session to S2-2501112, merging S2-2500408 | Paul (Ericsson) provides r01. Georgios (Nokia) provides r02 Xiaowan(vivo) replies Paul (Ericsson) replies to Xiaowan. Xiaowan(vivo) replies Paul (Ericsson) Xiaowan(vivo) privides r03 Lei(Tencent) provides comments and try to seek consensus, r04 is provided. Xiaowan(vivo) provide r05 Lei(Tencent) provides comments and fine to go with r05 as well. ==== General Revisions Deadline ==== Paul (Ericsson) we prefer r01, can accept r02 and object r00, r03, r04, r05. Xiaowan(vivo) agree to move forwards with r02 for progress Lei(Tencent) thanks to Xiaowan(vivo) and also fine to go with r02. Georgios (Nokia) agrees to move forward with r02, too ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501112 | CR | Approval | 23.503 CR1381R5 (Rel-19, 'B'): KI#9, Support of Rate limitation | Vivo, Meta USA, Tencent, Nokia | Rel-19 | Revision of S2-2500310r02, merging S2-2500408. Approved | Agreed | |
| 19.3.2 | S2-2500407 | CR | Approval | 23.501 CR5941 (Rel-19, 'B'): Exposure of rate limitation information | Ericsson | Rel-19 | Merged into S2-2501113 | Lei (Tencent) has provided S2-2500537r01 to merge S2-2500407. Lei(Tencent) asks if this should be considered as merged into S2-2500310 or not? Xiaowan(vivo) also think this paper can be merged in to 0310 Georgios (Nokia) assumes the proposal is for 0408 to be merged to 0310? 0407 is a 501 TDoc, merged to 0537? Lei(Tencent) replies to Georgios (Nokia) and agree 407 is merged to 0537. ==== General Revisions Deadline ==== Georgios (Nokia) asks Paul to confirm that 0407 is merged to 0537 Paul (Ericsson) confirms that 0407 is merged into 0537. ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500408 | CR | Approval | 23.503 CR1470 (Rel-19, 'B'): Exposure of rate limitation information | Ericsson | Rel-19 | Merged into S2-2501112 | Paul (Ericsson) please consider the S2-2500408 currently marked as Agreed to be merged into S2-2500310 Xiaowan(vivo) share the view with Paul (Ericsson) ==== Comments Deadline ==== | Merged |
| 19.3.2 | S2-2500537 | CR | Approval | 23.501 CR5867R6 (Rel-19, 'B'): KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta | Rel-19 | Baseline Revision of S2-2412951. r03 agreed. Revised in e-mail session to S2-2501113, merging S2-2500407 and S2-2500959 | Lei (Tencent) provides S2-2500537r01 by merging S2-2500407 and S2-2500959. Georgios (Nokia) comments on revision S2-2500537r01. Paul (Ericsson) provides response to Georgios and clarifies the UL/DL-maximum authorized bitrate are defined in clause 6.3 (PCC rule) in TS23.503 and not limited to GBR flows. Georgios (Nokia) further comments on Paul's reply Xiaowan(vivo) share the view with Georgios (Nokia) that MBR is only for GBR QoS flow Georgios (Nokia) shall provide a new revision unless a stage 3 reference is provided Paul (Ericsson) replies to Georgios and provides ref to stage 3. Lei(Tencent) agree with Paul (Ericsson). Mirko (Huawei) provides comments. Youngkyo(Samsung) provides comments. Lei(Tencent) provides comments and r02. ==== General Revisions Deadline ==== Lei (Tencent) ok to go with r03 as well, also fine with r00-r02. ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501113 | CR | Approval | 23.501 CR5867R8 (Rel-19, 'B'): KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta, Ericsson | Rel-19 | Revision of S2-2500537r03, merging S2-2500407 and S2-2500959. Approved | Agreed | |
| 19.3.2 | S2-2500959 | CR | Approval | 23.501 CR5867R7 (Rel-19, 'B'): KI#9, Support of Rate limitation | [Tencent, Tencent Cloud, vivo, Lenovo, CMCC], Nokia, [Meta] | Rel-19 | Revision of S2-2412951. Merged into S2-2501113 | Lei (Tencent) has provided S2-2500537r01 to merge S2-2500959. Georgios (Nokia): Proposes S2-2500959 to be marked as merged to S2-2500537r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.3.2 | - | - | - | KI#6: L4S for N3GPPA | - | - | Docs:=2 | - | |
| 19.3.2 | S2-2500471 | CR | Approval | 23.316 CR2143 (Rel-19, 'F'): L4S support in wireline access | Samsung | Rel-19 | r00 agreedrevised in e-mail session to S2-2501114. | Paul R. (Charter) comments for consideration. Youngkyo(Samsung) thanks for support and replies to comment. Paul R (Charter) OK with CR. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.3.2 | S2-2501114 | CR | Approval | 23.316 CR2143R1 (Rel-19, 'F'): L4S support in wireline access | Samsung | Rel-19 | Revision of S2-2500471. Approved | Agreed | |
| 19.3.2 | - | - | - | Exceeding quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
| 19.3.2 | - | - | - | LSs - Roaming scenarios | - | - | Docs:=2 | - | |
| 19.3.2 | S2-2500167 | LS OUT | Approval | [DRAFT] Reply LS on Support of XRM services in Roaming scenarios | Qualcomm | Rel-19 | Response to S2-2500011 Not Handled | - | |
| 19.3.2 | S2-2500380 | LS OUT | Approval | [DRAFT] LS reply on Support of XRM services in Roaming scenarios | China Mobile | Rel-19 | Response to S2-2500011 Not Handled | - | |
| 19.3.2 | - | - | - | LS: Multimodality | - | - | Docs:=33 | - | |
| 19.3.2 | S2-2500124 | LS OUT | Approval | [DRAFT] LS Reply on multi-modality awareness at RAN | Nokia | Rel-19 | Response to S2-2500014 Not Handled | - | |
| 19.3.2 | S2-2500158 | LS OUT | Approval | [DRAFT] LS reply on multi-modality awareness | ZTE | Rel-19 | Response to S2-2500074 Not Handled | - | |
| 19.3.2 | S2-2500297 | LS OUT | Approval | [DRAFT] Reply to LS on multi-modality awareness | China Mobile | Rel-19 | Revision of S2-2412650. Response to S2-2500014 Not Handled | - | |
| 19.3.2 | S2-2500447 | LS OUT | Approval | [DRAFT] LS on multi-modality awareness | InterDigital Inc. | Rel-19 | Response to S2-2500074 Not Handled | - | |
| 19.3.2 | S2-2500540 | LS OUT | Approval | [DRAFT] LS Reply on multi-modality awareness | Samsung | Rel-19 | Response to S2-2500050 Not Handled | - | |
| 19.3.2 | S2-2500752 | LS OUT | Approval | [DRAFT] LS on Multi-Modality awareness | Sony | Rel-19 | Response to S2-2500014 Not Handled | - | |
| 19.3.2 | S2-2500097 | CR | Approval | 23.501 CR5883 (Rel-19, 'B'): Optimization on Multi-modal service | ZTE | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500098 | CR | Approval | 23.503 CR1453 (Rel-19, 'B'): Optimization on Multi-modal service | ZTE | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500160 | CR | Approval | 23.502 CR5203 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500161 | CR | Approval | 23.503 CR1456 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500164 | CR | Approval | 23.501 CR5819R1 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, Xiaomi | Rel-19 | Revision of S2-2411417 Not Handled | - | |
| 19.3.2 | S2-2500165 | CR | Approval | 23.502 CR5204 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500261 | CR | Approval | 23.501 CR5910 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! Not Handled | - | |
| 19.3.2 | S2-2500263 | CR | Approval | 23.503 CR1464 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! Not Handled | - | |
| 19.3.2 | S2-2500298 | CR | Approval | 23.502 CR5236 (Rel-19, 'B'): 23.502 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500299 | CR | Approval | 23.501 CR5839R1 (Rel-19, 'B'): 23.501 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | Revision of S2-2411755 Not Handled | - | |
| 19.3.2 | S2-2500300 | CR | Approval | 23.503 CR1434R1 (Rel-19, 'B'): 23.503 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | Revision of S2-2411756 Not Handled | - | |
| 19.3.2 | S2-2500311 | CR | Approval | 23.501 CR5923 (Rel-19, 'B'): Support of multi-modality awareness | Vivo | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500312 | CR | Approval | 23.503 CR1466 (Rel-19, 'B'): Support of multi-modality awareness | Vivo | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500443 | CR | Approval | 23.501 CR5952 (Rel-19, 'B'): 23.501 CR5952: Providing Multi-Modal Awareness to NG-RAN | InterDigital Inc. | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500445 | CR | Approval | 23.503 CR1475 (Rel-19, 'B'): Providing Multi-Modal Awareness to NG-RAN | InterDigital Inc. | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500523 | CR | Approval | 23.501 CR5847R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411891 Not Handled | - | |
| 19.3.2 | S2-2500524 | CR | Approval | 23.502 CR5164R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411923 Not Handled | - | |
| 19.3.2 | S2-2500526 | CR | Approval | 23.503 CR1439R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411953 Not Handled | - | |
| 19.3.2 | S2-2500544 | CR | Approval | 23.501 CR5973 (Rel-19, 'B'): MMS ID to support Multi-modality awareness at RAN | LG Electronics | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500651 | CR | Approval | 23.501 CR5857R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412017 Not Handled | - | |
| 19.3.2 | S2-2500652 | CR | Approval | 23.502 CR5170R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412018 Not Handled | - | |
| 19.3.2 | S2-2500653 | CR | Approval | 23.503 CR1443R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412019 Not Handled | - | |
| 19.3.2 | S2-2500744 | CR | Approval | 23.501 CR5994 (Rel-19, 'B'): Multi-modality awareness | Sony | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500746 | CR | Approval | 23.503 CR1488 (Rel-19, 'B'): Multi-modality awareness | Sony | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500900 | CR | Approval | 23.501 CR5848R1 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | Revision of S2-2411920 Not Handled | - | |
| 19.3.2 | S2-2500901 | CR | Approval | 23.502 CR5302 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500902 | CR | Approval | 23.503 CR1436R1 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | Revision of S2-2411921 Not Handled | - | |
| 19.3.2 | - | - | - | KI#4: Traffic detections/QoS flow mapping for multiplexed data flows | - | - | Docs:=1 | - | |
| 19.3.2 | S2-2500903 | CR | Approval | 23.501 CR6034 (Rel-19, 'F'): Clarifications for support of mixed traffic handling | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.3.2 | - | - | - | KI#1: PDU Set information marking | - | - | Docs:=10 | - | |
| 19.3.2 | S2-2500042 | LS In | Action | LS from RAN WG2: Reply LS to SA2 on PDU set | RAN WG2 (R2-2411001) | Rel-19 | Not Handled. Postponed | Postponed | |
| 19.3.2 | S2-2500051 | LS In | Action | LS from RAN WG3: Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | RAN WG3 (R3-247875) | Rel-19 | Not Handled. Postponed | Postponed | |
| 19.3.2 | S2-2500117 | CR | Approval | 23.501 CR5887 (Rel-19, 'B'): DL PDU set information marking without (AF-provided) PDU set QoS params | Nokia | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500118 | CR | Approval | 23.502 CR5197 (Rel-19, 'B'): Procedures updates on DL PDU set information marking without (AF-provided) PDU set QoS params | Nokia | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500541 | CR | Approval | 23.501 CR5772R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411893 Not Handled | - | |
| 19.3.2 | S2-2500568 | CR | Approval | 23.502 CR5094R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411930 Not Handled | - | |
| 19.3.2 | S2-2500583 | CR | Approval | 23.503 CR1410R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411935 Not Handled | - | |
| 19.3.2 | S2-2500850 | CR | Approval | 23.502 CR5292 (Rel-19, 'B'): 23.502 PDU set based handling without PDU set QoS parameters | Lenovo | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500907 | CR | Approval | 23.501 CR5790R2 (Rel-19, 'B'): Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon | Rel-19 | Revision of S2-2411922 Not Handled | - | |
| 19.3.2 | S2-2500908 | CR | Approval | 23.503 CR1498 (Rel-19, 'B'): Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.3.2 | - | - | - | KI#1: AL-FEC | - | - | Docs:=8 | - | |
| 19.3.2 | S2-2500043 | LS In | Action | LS from RAN WG2: Reply LS on Application-Layer FEC Awareness at RAN | RAN WG2 (R2-2411002) | Rel-19 | Responses drafted in S2-2500482, S2-2500963. Not Handled. Postponed | Postponed | |
| 19.3.2 | S2-2500482 | LS OUT | Approval | [DRAFT] LS Reply on Application-Layer FEC Awareness at RAN | Samsung | Rel-19 | Response to S2-2500043 Not Handled | - | |
| 19.3.2 | S2-2500963 | LS OUT | Approval | [DRAFT] Reply LS on Application-Layer FEC Awareness at RAN | Nokia | Rel-19 | Response to S2-2500043 Not Handled | - | |
| 19.3.2 | S2-2500119 | CR | Approval | 23.501 CR5888 (Rel-19, 'B'): Support AL-FEC awareness at NG-RAN | Nokia, Qualcomm Incorporated, InterDigital Inc. | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2500120 | CR | Approval | 23.503 CR1454 (Rel-19, 'B'): Support AL-FEC awareness at NG-RAN | Nokia, Qualcomm Incorporated, InterDigital Inc. | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2501002 | DISCUSSION | Approval | Discussion on AL-FEC awareness at NG-RAN . | Xiaomi | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2501006 | CR | Approval | 23.502 CR5312 (Rel-19, 'B'): XRM_Ph2_KI1_AL-FEC support | Xiaomi | Rel-19 | Not Handled | - | |
| 19.3.2 | S2-2501007 | CR | Approval | 23.503 CR1502 (Rel-19, 'B'): XRM_Ph2_KI1_AL-FEC support | Xiaomi | Rel-19 | Check Affected Clauses! Not Handled | - | |
| 19.3.2 | - | - | - | KI#9: Information exposure - available data rate | - | - | Docs:=6 | - | |
| 19.3.2 | S2-2500048 | LS In | Information | LS from RAN WG2: LS on XR UL bit rate control | RAN WG2 (R2-2411218) | Rel-19 | Not Handled. Postponed | Postponed | |
| 19.3.2 | S2-2500704 | CR | Approval | 23.501 CR5525R3 (Rel-19, 'B'): The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo | Rel-19 | Revision of S2-2411978 Not Handled | - | |
| 19.3.2 | S2-2500705 | CR | Approval | 23.503 CR1396R2 (Rel-19, 'B'): The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo | Rel-19 | Revision of S2-2411979 Not Handled | - | |
| 19.3.2 | S2-2500905 | CR | Approval | 23.501 CR5794R2 (Rel-19, 'B'): Support of available data rate exposure | Huawei, HiSilicon, Nokia | Rel-19 | Revision of S2-2411916 Not Handled | - | |
| 19.3.2 | S2-2500906 | CR | Approval | 23.503 CR1419R2 (Rel-19, 'B'): Support of available data rate exposure | Huawei, HiSilicon | Rel-19 | Revision of S2-2411917 Not Handled | - | |
| 19.3.2 | S2-2500960 | CR | Approval | 23.502 CR5309 (Rel-19, 'B'): KI#9, Support of Available Data Rate | Nokia | Rel-19 | Not Handled | - | |
| 19.4.1 | - | - | - | Feasibility Study on 5GS Enhancement for Energy Efficiency and Energy Saving (FS_EnergySys) | - | - | Docs:=0 | - | |
| 19.4.2 | - | - | - | 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys) | - | - | Docs:=74 | - | |
| 19.4.2 | - | - | - | WT#1: Energy information collection (EIF) | - | - | Docs:=22 | - | |
| 19.4.2 | S2-2500175 | CR | Approval | 23.501 CR5897 (Rel-19, 'F'): Parameters for EIF selection | China Mobile | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501208. | Juan Zhang (Qualcomm) provides comments. Zhendong (ZTE) asks question for clarification . Dan (China Mobile) provides reply. Dan (China Mobile) reply. Marco (Huawei) ask further clarification Dan (China Mobile) provide r01 to reflect the previous discussion Marco (Huawei) comments r01 Juan Zhang (Qualcomm) provides comments to r01. Dan (China Mobile) provides r02 to reflect the comment. Alessio(Nokia) comments Magnus (Ericsson) provides comments LiMeng (Huawei) asks questions. dan(China Mobile) provide r03 to follow Alessio's suggestion. ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r03. Zhuoyun (vivo) prefers r03. Magnus O (Ericsson) is fine with r03 Marco (Huawei) OK 03, not accept R00-R02 Dan(China Mobile) OK with r03 ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501208 | CR | Approval | 23.501 CR5897R1 (Rel-19, 'F'): Parameters for EIF selection | China Mobile,vivo | Rel-19 | Revision of S2-2500175r03. Approved | Agreed | |
| 19.4.2 | S2-2500754 | CR | Approval | 23.501 CR5997 (Rel-19, 'F'): Update on NF function descriptions and EIF selection factors | Vivo | Rel-19 | Merge 6.3.27 to 2500175, and handle other changes? r06 agreed. Revised in e-mail session to S2-2501209. | Jungshin (Samsung) proposed to merge the changes for '6.3.27' in the CR to S2-2500175, and discuss other changes Zhuoyun Zhang (vivo) provides r01. LiMeng (Huawei) comments on r01. Juan Zhang (Qualcomm)provides comments on r01. Zhendong (ZTE) provides comments. Zhuoyun (vivo) provides r02. LiMeng (Huawei) asks questions. Zhuoyun (vivo) provides r03. Magnus O (Ericsson) provides r04 Zhuoyun (vivo) is fine with r04. Zhendong (ZTE) provides r05. Zhuoyun (vivo) provides r06. Alessio(Nokia) ok with r05. And r04 ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is ok with r06. LiMeng (Huawei) is OK to r06 and asks to co-sign the paper. Alessio(Nokia) is ok with r06. Magnus O (Ericsson) is ok with r06 Zhendong (ZTE) is fine with r06 and ask to co-sign . ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501209 | CR | Approval | 23.501 CR5997R1 (Rel-19, 'F'): Update on NF function descriptions and EIF selection factors | Vivo, Huawei, ZTE | Rel-19 | Revision of S2-2500754r06. Approved | Agreed | |
| 19.4.2 | S2-2500269 | CR | Approval | 23.501 CR5912 (Rel-19, 'F'): Resolve the ENs of energy consumption information collection and exposure for certain application | China Mobile | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500886 Marco (Huawei) proposes to take as basis for discussion on renewable energy, while application part related merged into 886 Zhendong (ZTE) provides r01. Marco (Huawei) provides r02 Dan(China Mobile) for Marco's comment, I suggest to merge this paper to S2-2500886 Zhuoyun (vivo) agrees with Dan and also suggests to merge this paper to S2-2500886. Marco (Huawei) ok to merge in 0886 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500789 | CR | Approval | 23.501 CR6000 (Rel-19, 'F'): Support of per-application energy consumption information | Samsung | Rel-19 | DRM File replaced. Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500886 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500886 | CR | Approval | 23.501 CR6028 (Rel-19, 'F'): Adding Application level Energy consumption collection, calculation and exposure | ZTE | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss the CR as baseline, and merge S2-2500269, S2-2500789, S2-2500840(EN about per AF), S2-2500747(EN about per AF), and S2-2500810(EN about per AF) Zhendong (ZTE) start the discussion. Marco (Huawei) comment on Application and formula Bahador (NTT DOCOMO) provides comments on the granularities Juan Zhang (Qualcomm) provides comments Dan(China Mobile) provides that support the per-UE-per-application Marco (Huawei) comments prefer per-UE-per-Application Josep (Deutsche Telekom) comments, provides some editorial improvements in r01 Marco (Huawei) provide r02 for Per-UE-per-Application version Zhendong (ZTE) provides response to Huawei. Zhendong (ZTE) provides response to Docomo. Juan Zhang (Qualcomm) provides comments to r02. Zhendong (ZTE) provides response to Qualcomm. Zhuoyun (vivo) comments. Zhendong (ZTE) provides r03. Alessio (Nokia) wonders whether we need data per application explicitly and provides comments (would prefer to note the CR), wonders whether this should have been part of exception agreement? Xiaoyan (CATT) support this CR and would like to cosign. Zhendong (ZTE) provides response to Nokia. Alessio(Nokia) suggests to postpone the issue and discuss the need of this further. Zhendong (ZTE) provides clarification to Nokia. ==== General Revisions Deadline ==== Marco (Huawei) agree with Zhedong (ZTE) Juan Zhang (Qualcomm) supports to postpone the CR. Zhuoyun (vivo) prefers r03 or suggest to endorse r03. Marco (Huawei) we are only OK with R03 (NOK R00, R01). If postponed, we suggest to consider R03 as basis for further revisions. Bahador (NTT DOCOMO) also supports r03 (at least endoresded as the baseline for the next meeting) Zhendong (ZTE) requests the CR endoresded as the baseline for the next meeting if Nokia and Qualcomm still disagree Dan(China Mobile) support r03 and suggest to approve it or at least endorse. Alessio(Nokia) believes that it is not necessary to endorse this paper, we can continue the discussion and by all mean companies interested can use this as baseline. ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500885 | DISCUSSION | Information | Discussion and proposal on the application level energy consumption information exposure. | ZTE | Rel-19 | Noted in e-mail session | Noted | |
| 19.4.2 | S2-2500840 | CR | Approval | 23.501 CR6014 (Rel-19, 'F'): Clarification on support of Energy Efficiency and Energy Saving | CATT | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500886 (EN about per AF) and to S2-S2-2500813 (table update) Marco (Huawei) agrees to merge Alessio(Nokia) proposes to just use this to correct typos in formula in annex T.2 and provides r01, so please unmerge. ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r01. LiMeng (Huawei) proposes to focus on the 0813, the equation in the revision is not technically correct. Cannot accept the revisions and the original CR. Xiaoyan (CATT) is fine with r01, and suggests either marking as merged into 886 and 813 (if revision of 813 or 886 agreed) or agree r01. Josep (Deutsche Telekom) is fine with r01 correcting just Annex T Alessio(Nokia) is encouraging to approve r01. Alessio(nokia) observes 813 should not be approved so proposes to LiMeng (Huawei) to approve r01 where in the formula he quoted .we use Eue and not Eue,gnb Marco (Huawei) object to R00 and R01 unless we make the formula for EC for UE correct <rtfimage://> Alessio(nokia) already proposed the change (minimal) to the text of r01 that makes the text correct. (i.e. remove gNB from EUE,gnb in the offending formula so it is Eue) LiMeng (Huawei) commented the r01 from Nokia is meaningless since the essence to calculate the ECue is based on the summary of EC pdu session. This Cr seems not introducing meaningful change proposal anyhow. We should not do big revisions now unless a document was urgent. We can discuss further in Athens. Alessio relies to LiMeng (Huawei) who commented the r01 from is meaningless since the essence to calculate the ECue is based on the summary of EC pdu session. Our comment is that this is Huawei opinion but this is what is in the TS now ?? so it is meaningless? ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500747 | CR | Approval | 23.501 CR5995 (Rel-19, 'F'): Update on energy consumption information collection and exposure to solve the Editor's notes | Vivo | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500886 (EN about per AF) and to S2-S2-2500813 (table update) Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500810 | CR | Approval | 23.501 CR6008 (Rel-19, 'F'): Clarification regarding energy collection and exposure | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500886 (EN about per AF) and to S2-S2-2500813 (table update) Marco (Huawei) provide r01 Zhendong (ZTE) provides r02. Dan (China Mobile) provides r03. Alessio(Nokia) prefers 840r01 for formula change and the text advising where to find the procedures is not needed, so, we can note this paper. ==== General Revisions Deadline ==== Alessio(Nokia) confirms proposal to note this paper and use prefers 840r01 for formula change ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500813 | CR | Approval | 23.501 CR6010 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss the CR as baseline, and merge S2-2500840(table update), S2-2500747(table update), S2-2500810(table update), and S2-2500884(table update). LiMeng (Huawei) provides r01 for the merger. Juan Zhang (Qualcomm) provides comments on r01. LiMeng (Huawei) undo the changes on service data flow and provides r02. Josep (Deutsche Telekom) comments on period T and energy consumption information collection, provides r03 LiMeng (Huawei) provides r04 on top of r03, move the text to the clause below. Changki (ETRI) provide r05 with comments. Marco (Huawei) comment on Event ID Changki (ETRI) reply to Marco(Huawei). Alessio(Nokia) cannot see anything in this CR that is progressing or resolving issues, there are cosmetic changes (changes on table are wrong though as we need to report the info of what the data collected is about), and the formula changes are difficult to read (I suspect they need proper review so a dedicated document explaining the issues is better for next meeting) and the change to monitoring event is incorrect as CIOT UP optimizations can use the UP. Propose to not pursue this paper further. Xiaoyan (CATT) provides comments. Zhuoyun (vivo) provides r06. LiMeng (Huawei) provides r08, and asks to ignore r07. Alessio(Nokia) has a problem to agree this paper as now the structure of the clause introduced seems confusing as from SMF we do not collect energy at all. We do not need subclauses. ==== General Revisions Deadline ==== LiMeng (Huawei) proposes to update the title of 5.51.2.2.2 to 'Information from SMF for user-plane energy consumption calculation' in r08, or 'removing the introduced sub-clause title and update the table number' in r08. Alessio(Nokia) asks to postpone this document as we better update this clause when we are done with the rest of changes that requires updating this. This Cr seems not introducing meaningful change proposal anyhow. We should not do big revisions now unless a document was urgent. We can discuss further in Athens. ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500884 | CR | Approval | 23.501 CR6027 (Rel-19, 'F'): Correcting the input and output of SMF and resolving the EN on roaming. | ZTE | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500810 (table update) and S2-2500189. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500818 | CR | Approval | 23.501 CR6013 (Rel-19, 'F'): EIF support of OAM interaction | Huawei, HiSilicon | Rel-19 | Missing CR Number - CR states -! Noted in e-mail session | Marco (Huawei) propose to merge discussion in S2-2500175 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500455 | CR | Approval | 23.501 CR5956 (Rel-19, 'F'): Support for S-NSSAI granularity energy consumption exposure | NEC | Rel-19 | Postponed in e-mail session | Marco (Huawei) ask clarification on the use case Josep (Deutsche Telekom) wonders whether it is not too late to add granularities. Bahador (NTT DOCOMO) requests for clarification. Iskren (NEC) replies to comments from NTT DOCOMO, DT and Huawei. Juan Zhang (Qualcomm) provides comments Iskren (NEC) replies to comment from Juan (Qualcomm) Juan Zhang (Qualcomm) provides further comment. Alessio(Nokia) would suggest that the client of this info can conceivably be the slice owner that also is the S-NSSAI, DNN owner , so the client can collect the per (S-NSSAI, DNN) info for the UE and aggregate across the DNNs for the S-NSSAI. This is what the EIF would have to do anyhow and additionally the client has per PDU session visibility in one go. So, I would not think this is needed for now, like the app level info that would follow same approach based on its QoS flows for the UE. So while I appreciate what NEC wants to do I would not be ready to go for it in this release, which for this work item is unfortunately frozen after SA#106 Iskren (NEC) answers comments from Juan (Qualcomm) and Alessio (Nokia) and provides r02. Juan Zhang (Qualcomm) provides comments to r02. Iskren (NEC) answers comment from Juan (Qualcomm) and provides r02. ==== General Revisions Deadline ==== Zhendong (ZTE) proposes to postpone this CR according to 0456 discussion Marco (Huawei) as per comment to 0456 (the twin document) suggests this should be postponed to a future release like matching CR (or Athens meeting if Iskren would like F2F opportunity) Iskren (NEC) answers comments from Marco (Huawei) and Zhendong (ZTE). Please note 0456 is postponed as it is a CR to TS23.502. We decided to handle in this meeting TS23.501 CR only. So, there are no issues with this CR to TS23.501 to be agreed at this meeting. Zhendong (ZTE) provides the response. ==== Comments Deadline ==== Iskren (NEC answers Zhendong (ZTE) That is not true Zhendong. The technical questions were asked in the 445 which is to TS23.501 and were answered with new revisions created. The 446 is against TS23.502 and it was suggested we concentrate on TS23.501 only at this meeting . And this is what we did. | Postponed |
| 19.4.2 | S2-2500369 | CR | Approval | 23.501 CR5935 (Rel-19, 'F'): Compliance to regional legislation concerning user privacy. | Nokia, Deutsche Telekom | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501210. | Marco (Huawei) ask clarifications Magnus O (Ericsson) provides r1 alessio (Nokia) provides r01 correct link. Nokia can live with r01 as a starting point, any further enhancements can depend from SA3 indeed. Responding to Marco Marco (Huawei) comments ==== General Revisions Deadline ==== Josep (Deutsche Telekom) replies to Marco's comments Bahador (NTT DOCOMO) supports r01 and would like to co-sign ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501210 | CR | Approval | 23.501 CR5935R1 (Rel-19, 'F'): Compliance to regional legislation concerning user privacy. | Nokia, Deutsche Telekom, NTT Docomo | Rel-19 | Revision of S2-2500369r01. Approved | Agreed | |
| 19.4.2 | S2-2500811 | CR | Approval | 23.501 CR6009 (Rel-19, 'F'): Updating the functionality impacts introduced by energy related features | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | LiMeng (Huawei) provides r01. Alessio (nokia) proposes to note this paper that only aims to change the clause title. We can live with current title this is hardly a CAT-F. Josep (Deutsche Telekom) objects to this CR. We would need to check for consistency in many places to accommodate this editorial change. ==== General Revisions Deadline ==== LiMeng (Huawei) is OK to note the paper although we don't really touch the 'efficiency' ?? ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500189 | CR | Approval | 23.501 CR5900 (Rel-19, 'F'): Clean up the architecture and interface for energysys | Qualcomm Incorporated | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss the changes for 4.2.7 and 4.2.18.1 of the CR, and merge other clauses to S2-2500175 and S2-2500748. Juan Zhang (Qualcomm) proposes r01 which only keeps the changes for 4.2.7 and 4.2.18.1 based on Rapporteur's suggestion . Marco (Huawei) proposed to discuss EIF in doc 0175. comment on PCF part removal to be decided based on conclusion on 503 related discussion. Proposed R02 Josep (Deutsche Telekom) is fine with r02. Co-signs Zhendong (ZTE) provides r04. Bahador (NTT DOCOMO) merges S2-2500356 and S2-2500357 into this CR and provides r03 Josep (Deutsche Telekom) comments, provides r05 Marco (Huawei) provides r06 Bahador (NTT DOCOMO) provides r07 and co-signs. Juan Zhang (Qualcomm) provides r08 to remove clause 4.2.7. Zhuoyun (vivo) comments. Magnus (Ericsson) comments Alessio(Nokia) asks question for clarification on why the PCF-EIF interface is needed if we have inaccurate information from EIF. What policy can be executed? are we going to number the Nx interfaces? Can we do it now? TS 28.550 is legacy stuff (following RPC style and not the model-driven approach). Hence we request to avoid adding reference to 28.550 (to get the TDoc updated to remove reference to 28.550). The functionality is replaced by 'PerfMetricJob' defined in 28.622. Juan Zhang (Qualcomm) provides r10 and asks to ignore r09. Zhuoyun (vivo) provides r11 and would like co-sign. Alessio(nokia) provides r12 removing PCF-EIF interface ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r11 and r12. Josep (Deutsche Telekom) is fine with r12 (also r11) Chia-Lin (MediaTek) is only fine with r11 Marco (Huawei) objects R12, OK R11 & R10 Alessio(Nokia() ok to postpone this pape unless r12 is agreeable as r11 not normatively just adds roaming is not supported... I am sure we can do better update of this by similar CR in Athens ??. The change in r12 is what would bring some progress of value. The rest is a note we can add in Athens (if needed in this clause). So we would not agree to make r11 an agreed paper that can go to SA plenary as is (so request to note this) Magnus (Ericsson) prefers r12 (can live with r11) Bahador (NTT DOCOMO) objects the original version of the CR also r01, r02 and r12, prefers r11 and can live with r08, r09, r10 Alessio(Nokia) requests to postpone this as already stated ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500356 | CR | Approval | 23.501 CR5929 (Rel-19, 'F'): Resolving Roaming editor's note in the architecture | NTT DOCOMO | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-500189 Bahador (NTT DOCOMO) merged this CR into S2-500189. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500357 | CR | Approval | 23.501 CR5930 (Rel-19, 'F'): Resolving editor's note on the interface between EIF and OAM | NTT DOCOMO | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-500189 Bahador (NTT DOCOMO) merged this CR into S2-500189. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500815 | CR | Approval | 23.501 CR6011 (Rel-19, 'F'): Reference architecture: Roaming support and OAM interface | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500189 Marco (Huawei) agree to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | - | - | - | WT#1: Procedure for Energy information collection | - | - | Docs:=17 | - | |
| 19.4.2 | S2-2500176 | CR | Approval | 23.502 CR5205 (Rel-19, 'F'): Parameters for EIF selection | China Mobile | Rel-19 | Noted in e-mail session | LiMeng (Huawei) comments that it is preferable to have discussion on principle in 501 relevant CRs. The 502 shall be aligned to 501. Dan (China Mobile) OK with Meng's proposal, I will update accordingly based on 501 Dan (China Mobile) provide r01 with only contain the EIF serving area information, which is alignment with 501. Josep (Deutsche Telekom) comments LiMeng (Huawei) asks questions. Marco (Huawei) the CR shall be aligned to 0175. Dan (China MObile) reply that. ==== General Revisions Deadline ==== Dan(China Mobile) OK to NOTE this one. LiMeng (Huawei) asks to note this paper. ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500283 | CR | Approval | 23.502 CR5234 (Rel-19, 'F'): Update on Energy Consumption information collection | ETRI | Rel-19 | Merge into S2-2500814? Merged into S2-2501211 | Jungshin (Samsung) proposed to merge the CR to S2-2500814 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500814 | CR | Approval | 23.502 CR5289 (Rel-19, 'F'): Clarification regarding energy collection and exposure | Huawei, HiSilicon | Rel-19 | Discuss as baseline and merge S2-2500283 and S2-2500178 (4.29.2)? r04 agreed. Revised in e-mail session to S2-2501211, merging S2-2500178, S2-2500282 and S2-2500283 | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500283 and S2-2500178 (4.29.2). LiMeng (Huawei) provides the comments and suggest to agree the basic principles firstly. Changki(ETRI) provides r01 with comments Zhendong (ZTE) provides comments. Changki(ETRI)provides comments. LiMeng (Huawei) responds, and would like to highlight that before changes in 502, it is preferable to have discussion on principle in 501 relevant CRs. The 502 shall be aligned to 501. Juan Zhang (Qualcomm) also proposed to focus on the discussion for 501 CR first. Josep (Deutsche Telekom) comments that NOTE 2 is not techncially correct and proposes to remove it. LiMeng (Huawei) responds, and fine to remove NOTE 2. R02 is provided to also merge S2-2500178. Dan (China Mobile) propose to merge S2-2500178 into this paper, to avoid the two 502 CRs email discussion, and we can focus on this email directly. Changki (ETRI) provides r03 with comments. Changki (ETRI) provides r05 with comments. Alessio(Nokia) provides r04. Alessio(Nokia) asks to postpone this paper since we cannot converge. Changki (ETRI) provides r06 with comments. ==== General Revisions Deadline ==== LiMeng (Huawei) can accept r04 - r06 and ask if we can go with r04 as the minimum set. Changki (ETRI) is Ok with r04 - r06 Alessio(Nokia) is Ok with r04 ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501211 | CR | Approval | 23.502 CR5289R1 (Rel-19, 'F'): Clarification regarding energy collection and exposure | Huawei, HiSilicon, ETRI | Rel-19 | Revision of S2-2500814r04, merging S2-2500178, S2-2500282 and S2-2500283. Approved | Agreed | |
| 19.4.2 | S2-2500841 | CR | Approval | 23.502 CR5160R1 (Rel-19, 'F'): Data collection for energy information calculation and exposure | CATT | Rel-19 | Revision of S2-2411859 Revision of S2-2411859. r04 agreed. Revised in e-mail session to S2-2501212. | LiMeng (Huawei) asks that if we need to have such wide impact on the UPF exposure. Changki (ETRI) provide comments Zhendong (ZTE) provides comments. Xiaoyan (CATT) provides r01. Changki (ETRI) reply to Xiaoyan (CATT) and provide r02 Marco (Huawei) concern on changes to UP path LiMeng (Huawei) proposes r04 Alessio(Nokia) proposes r03 ==== General Revisions Deadline ==== Changki (ETRI) is OK with r04. Juan Zhang (Qualcomm) is OK with r04. Magnus O (Ericsson) is ok with r04 Alessio(Nokia) wonders if now this is the only CR that may get approved impacting 5.2.8.1. if so can we undo the removal of such clause in r04 ? Otherwise we will need a separate CR next meeting. Zhendong (ZTE), 0814r04 cover the clause 5.2.8.1 ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501212 | CR | Approval | 23.502 CR5160R2 (Rel-19, 'F'): Data collection for energy information calculation and exposure | CATT, ETRI | Rel-19 | Revision of S2-2500841r04. Approved | Agreed | |
| 19.4.2 | S2-2500178 | CR | Approval | 23.502 CR5206 (Rel-19, 'F'): Correction of Energy Consumption information exposure procedure | China Mobile | Rel-19 | Discuss 4.29.1 only and merge S2-2500282. Merge 4.29.2 to S2-2500814? Merged into S2-2501211 | Changki(ETRI) provides r01 with comments Jungshin (Samsung) proposed to discuss 4.29.1 only and merge S2-2500282. And, merge 4.29.2 to S2-2500814. LiMeng (Huawei) comments that the requested granularity should be aligned with the discussion in 886, and whether the UE-granularity is needed for SMF-UPF interaction. Changki(ETRI) provides comments LiMeng (Huawei) is OK to merge, the merger is provided. Dan(China Mobile) suggest to merge this paper into S2-2500814 LiMeng (Huawei) explains to Alessio (Nokia) that all content of this paper is merged into 0814. This document can be marked as 'Merged into S2-2500814' Alessio(Nokia) asks if anyone is providing a revision of this document to docus on 4.29.1 only as the rest is merged in S2-2500814? Dan(China Mobile) Merged into S2-2500814 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500282 | CR | Approval | 23.502 CR5233 (Rel-19, 'F'): Update on Energy Consumption information exposure and consumer NF | ETRI | Rel-19 | Merge into S2-2500282? Merged into S2-2501211 | Jungshin (Samsung) proposed to merge the CR to S2-2500178 LiMeng (Huawei) suggests to merge this document into S2-2500814, as suggested in the email thread of 0178. The r02 of 0814 includes the proposal of 0282 and 0178 in general. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500887 | CR | Approval | 23.502 CR5299 (Rel-19, 'F'): Adding procedure for Application level Energy consumption collection and exposure | ZTE | Rel-19 | Postponed in e-mail session | LiMeng (Huawei) comments that the requested granularity should be aligned with the discussion in 886, and questioning on using the slicing. LiMeng (Huawei) agrees the principle to align with the conclusion of 501 on the new granularity, and comments. Zhendong (ZTE) provides r01. Dan (China Mobile) comments that this paper should only focus on the AF level procedure, i.e. the new procedure part, and merge the change of 4.29.2 into S2-2500814. Xiaoyan (CATT) provides comments. Alessio(Nokia) proposes to note this paper and to come back to any 23.502 aspects if we reach agreement on app level info. Zhendong (ZTE) provides r02. Alessio(Nokia) proposes to postpone this paper as also 886 is requested to be postponed. ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) also agrees to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500456 | CR | Approval | 23.502 CR5244 (Rel-19, 'F'): Support for S-NSSAI granularity energy consumption exposure | NEC | Rel-19 | Noted in e-mail session | LiMeng (Huawei) comments that calculating the slicing-level energy consumption is already supported by SA5, wonder the rationale of having it in SA2. Juan Zhang (Qualcomm) proposes to focus on the discussion for the 501 CR first. Zhendong (ZTE) provides comments. alessio (nokia) suggests this should be postponed to a future release like matching CR (or Athens meeting if Iskren would like F2F opportunity) ==== General Revisions Deadline ==== Marco (Huawei) agrees with Alessio (Nokia) Zhendong (ZTE), we should discuss the decision in the 0455 thread. ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500842 | CR | Approval | 23.288 CR1286R1 (Rel-19, 'F'): Data collection via DCCF for energy information calculation and exposure | CATT | Rel-19 | Revision of S2-2411860. Noted in e-mail session | Zhendong (ZTE) share similar view with LGe . LaeYoung (LGE) proposes to NOTE this CR because the proposal is out of Rel-19 scope. Josep (Deutsche Telekom) comments, suggests maybe TEI20? Marco (Huawei) provides comments Marco (Huawei) agrees with LGe Juan Zhang (Qualcomm ) also supports LaeYoung (LGE)'s proposal to NOTE this CR because the proposal is out of Rel-19 scope. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500358 | CR | Approval | 23.502 CR5239 (Rel-19, 'F'): Updating EIF service operations | NTT DOCOMO | Rel-19 | Discuss as baseline and merge S2-2500750 and S2-2500756? r04 agreed. Revised in e-mail session to S2-2501213, merging S2-2500750 and S2-2500756 | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500750 and S2-2500756. Juan Zhang (Qualcomm) provides comments. LiMeng (Huawei) agrees on Juan(Qualcomm), comments on the rationale of the segmentation. Zhendong (ZTE) provides r02. Bahador (NTT DOCOMO) supports the r01 and provides clarification. Josep (Deutsche Telekom) comments, co-signs, provides r01 Marco (Huawei) question on 0756. Wait merging for other comments, if any Bahador (NTT DOCOMO) is fine with r02 and provides clarification on the use-cases. Marco (Huawei) provides comments Bahador (NTT DOCOMO) requests for clarification. Xiaoyan (CATT) provides comments. LiMeng (Huawei) comments. Alessio(Nokia) provides r03 Josep (Deutsche Telekom) comments to LiMeng's (Huawei) comment Zhendong (ZTE) provides comments. Bahador (NTT DOCOMO) provides responses to Alessio (Nokia), LiMeng (Huawei), Josep (Deutsche Telekom), Xiaoyan (CATT), Zhendong (ZTE) Zhuoyun (vivo) supports r03 and would like to cosign it. Dan (China Mobile) supports this paper's idea and would like to co-sign. Zhendong (ZTE) provides response to Bahador . Bahador (NTT DOCOMO) provides r04 and further clarifications. ==== General Revisions Deadline ==== Zhuoyun (vivo) prefers r04 and r03. Xiaoyan (CATT) prefers to remove 'as Target of Event Reporting' from r04. Bahador (NTT DOCOMO) proposes to remove 'as Target of Event Reporting' from 'The following events can be subscribed by a NF consumer as Target of Event Reporting' and keep/add it in the '- Energy Consumption ...' bullet . Josep (Deutsche Telekom) coments on ,as Target of Event Reporting', is fine to remove it Marco (Huawei) we propose to postpone, since we are still not convinced by scenario and whether it is a correction. Bahador (NTT DOCOMO) to address Marco's (Huawei) concern suggests to remove changes in clause 5.2.28.2.2 and accept remaining changes. Marco (Huawei) agree with Bahador (NTT DOCOMO) way out to remove changes in clause 5.2.28.2.2 in R04. ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501213 | CR | Approval | 23.502 CR5239R1 (Rel-19, 'F'): Updating EIF service operations | NTT DOCOMO, Deutsche Telekom, Vivo, China Mobile | Rel-19 | Revision of S2-2500358r04, merging S2-2500750 and S2-2500756. Approved | Agreed | |
| 19.4.2 | S2-2500750 | CR | Approval | 23.502 CR5279 (Rel-19, 'F'): Resolving EN in Clause 5.2.28.1 | MediaTek Inc. | Rel-19 | Merge into S2-2500358? Merged into S2-2501213 | Jungshin (Samsung) proposed to merge the CR to S2-2500358. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500756 | CR | Approval | 23.502 CR5280 (Rel-19, 'F'): Update on EIF services to solve the Editor's notes | Vivo | Rel-19 | Merge into S2-2500358? Merged into S2-2501213 | Jungshin (Samsung) proposed to merge the CR to S2-2500358. Alessio (nokia) Ok to merge in 358r03 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500547 | CR | Approval | 23.502 CR5254 (Rel-19, 'F'): Update on Nsmf_EventExposure service for Energy Consumption information collection | ETRI | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500812. Changki (ETRI) reply to Marco (Huawei) Josep (Deutsche Telekom) asks about the reference to clause 4.49 in TS23.502, asks for clarification between the options Marco (Huawei) provides r01 merging 0574 & 0812, but the 2 proposals are mutually exclusive, so captured as option 1 & option 2. One option shall be selected for approval. Marco (Huawei) answers to questions Changki (ETRI) reply to Marco(Huawei). Marco (Huawei) answer to Changki (ETRI) Changki (ETRI) provide r02 with comments. Alessio(nokia) proposes to postpone this topic unless we find a common view (note also that we need to have a similar debate in 814 if I am not mistaken? There is also a common clause 5.2.8.1 with that CR! Remove from this one please ) Marco (Huawei) reply to Changki (ETRI) Dan (China Mobile) support to continue discuss this in next meeting. Alessio(Nokia) ok to postpone. ==== General Revisions Deadline ==== Changki (ETRI) is OK with r03, r02, r01. Alessio(Nokia) requests to postpone Marco (Huawei) Agree to postpone. Not OK with r00, r02 ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500812 | CR | Approval | 23.502 CR5288 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500547 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | - | - | - | WT#2: UE Subscription and Policy | - | - | Docs:=20 | - | |
| 19.4.2 | S2-2500344 | CR | Approval | 23.501 CR5927 (Rel-19, 'F'): Resolution of editor s note on whether the Energy Saving indicator is one value or multiple values. | Nokia, Deutsche Telekom | Rel-19 | Postponed in e-mail session | Marco (Huawei) asks clarification Iskren (NEC) comments DongYeon (Samsung) provides comments. Xiaoyan (CATT) provides comments. LaeYoung (LGE) has problem to understand how the ES indicator stored in UE subscription data is selected for each UE and based on what. Marco (Huawei) further question for clarification Alessio(Nokia) replies to DongYeon (Samsung) provides comments. Alessio(Nokia) replies to Iskren (NEC) comments Alessio(Nokia) replies Marco's questions Chia-Lin Lai (MediaTek) has same view as Xiaoyan (CATT) Marco (Huawei) share doubts and this proposal is beyond Cat F. Alessio(Nokia) replies to marco that the discussion on multiple vs single value was open as per EN Alessio (Nokia) replies to Xiaoyan (CATT) and LaeYoung (LGE) that the existence of this indicator is requiring mapping outside standards scope whether 1 value or multiple values are used ==== General Revisions Deadline ==== Zhuoyun (vivo) comments. Xiaoyan (CATT) replies to Alessio (Nokia) and cannot accept r00. Alessio(Nokia) ok to discuss this in Athens. But please consider the benefit of not having a single value as who wants a single value can still do it, while allowing those that want more to do so. Marco (Huawei) objects to any version Marco (Huawei) replies to Alessio(Nokia) that also EIF-PCF was open per EN so the same approach can apply ?? ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500227 | DISCUSSION | Discussion | Discussion on Energy Saving Indicator. | Nokia, Deutsche Telekom | Rel-19 | Noted in e-mail session | Noted | |
| 19.4.2 | S2-2500391 | CR | Approval | 23.501 CR5938 (Rel-19, 'F'): Resolving ENs about subscription information and policy control | LG Electronics | Rel-19 | Noted in e-mail session | Juan Zhang (Qualcomm) provides comments. LaeYoung (LGE) responds to Juan Zhang (Qualcomm). Marco (Huawei) expresses some doubts LaeYoung (LGE) responds to Marco (Huawei). LaeYoung (LGE) provides r01 and responds to Bahador (NTT DOCOMO). Bahador (NTT DOCOMO) requests for clarification. DongYeon (Samsung) provides comments. Zhendong (ZTE) provides comments. LaeYoung (LGE) answers to DongYeon (Samsung) and Zhendong (ZTE). Marco (Huawei) asks further clarification Bahador (NTT DOCOMO) provides r02. LaeYoung (LGE) agrees with the direction/changes made by Bahador (NTT DOCOMO), and responds to Marco (Huawei) and Bahador (NTT DOCOMO). Juan Zhang (Qualcomm) askes further comments for r02. Josep (Deutsche Telekom) proposes to NOTE, leave this to a further release. Marco (Huawei) comments r02 LaeYoung (LGE) responds to Juan (Qualcomm), Josep (Deutsche Telekom), Marco (Huawei) and Alessio (Nokia). Alessio agrees with Josep (Deutsche Telekom) who proposes to NOTE, leave this to a further release. Marco (Huawei) propose to note this CR and move discussion to next Rel ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500748 | CR | Approval | 23.501 CR5996 (Rel-19, 'F'): Resolving ENs in Clause 5.51.5 and 5.51.6 | MediaTek Inc. | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500771, S2-2500853, S2-2500888, S2-2500351, S2-2500793, and S2-2500889 Juan Zhang (Qualcomm) provides comments. Magnus O (Ericsson) Don't think that this doc is agreeable Chia-Lin (MediaTek) provides r01 based on the merged CRs assigned by Rapporteur and currently received comments Bahador (NTT DOCOMO) provides comment on the 'energy saving strategy' Juan Zhang (Qualcomm) provides comments to r02. Xiaoyan (CATT) provides r03. Zhendong (ZTE) provides r02. Alessio(nokia) agrees with Magnus: let's note this paper and use 351 as the way forward for PCF-EIF interface aspects. For subscription aspects we prefer a multiple values scalar as in 344. Chia-Lin (MediaTek) provides r04. Marco (Huawei) have concern for scalar value as commented to 0344, so disagree to R04. We support the part related to the EIF-PCF interaction. Juan Zhang (Qualcomm) can not agree with the EIF->PCF notification Magnus (Ericsson) is ok with the (r04) changes in 5.51.5 but not ok with the changes in 5.52.6 Zhuoyun (vivo) is ok with r04 and would like to cosign. Chia-Lin (MediaTek) provides r05 Alessio(Nokia) based on the inconclusive discussion proposes to postpone this paper. Magnus O (Ericsson) also proposes to postpone this paper ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) also proposes to postpone this paper Marco (Huawei) agrees to postpone Magnus O (Ericsson) also requests to postpone this CR Chia-Lin (MediaTek) agrees to postpone ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500771 | CR | Approval | 23.501 CR5999 (Rel-19, 'F'): Update on subscription information and policy control aspects | Vivo | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500816 | CR | Approval | 23.501 CR6012 (Rel-19, 'F'): Update of the subscription aspects for network energy saving | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Juan Zhang (Qualcomm) provides comments. DongYeon (Samsung) provides comments. Josep (Deutsche Telekom) comments, objects to this CR Marco (Huawei) considers 0816 and 0731 are mutually exclusive and eventually we will select one of the two. Mirko (Huawei) replies to the comments. Josep (Deutsche Telekom) comments, suggests to bring a r01 Juan Zhang (Qualcomm) provides further comments. Alessio(Nokia) proposes to note this paper for reasons similar to other companies with similar view Magnus (Ericsson) comments and proposes to Note this doc ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500853 | CR | Approval | 23.501 CR6015 (Rel-19, 'C'): Clarification on Energy Saving indicator | Samsung | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500888 | CR | Approval | 23.501 CR6029 (Rel-19, 'F'): Resolving the EN on the UE Energy saving Subscription | ZTE | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748 Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500351 | CR | Approval | 23.501 CR5928 (Rel-19, 'F'): Resolution of editor's note on PCF taking EIF information into account | Nokia | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748. Marco (Huawei) agrees to merge Alessio(Nokia) having reviewed 748 progress, prefers to use this paper for the PCF-EIF interface topic. So cannot agree to merge. ==== General Revisions Deadline ==== Marco (Huawei) objects to this document ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500793 | CR | Approval | 23.501 CR6001 (Rel-19, 'F'): Support of policy control based on energy information | Samsung | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500889 | CR | Approval | 23.501 CR6030 (Rel-19, 'F'): Clarification on the policy control for network energy saving | ZTE | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500748. Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500190, S2-2500890 and S2-2500843. Marco (Huawei) which is the fate of this document, merged or baseline? Zhendong (ZTE) prefer to handle this CR separately. Alessio(Nokia) would be ok to approve this CR. ==== General Revisions Deadline ==== Xiaoyan (CATT) cannot accept r00. Alessio(Nokia) believe the reason for change is good and there is no exception sheet to work on PCF-EIF interaction so not sure the comment from CATT is valid. Besides he needs to have consensus to add this interaction and there is not. Magnus O (Ericsson) supports r00 Marco (Huawei) objects to R00 Zhendong (ZTE) ask Marco (huawei) to re-consider. Marco (Huawei) comments that we can accept only a version keeping the second part of the EN 'Whether the notification for the energy related information from the EIF is provided to the PCF and what are the notification details, are FFS' ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500892 | CR | Approval | 23.501 CR6031 (Rel-19, 'F'): Clarification on the BDT based on network energy related information | ZTE | Rel-19 | Noted in e-mail session | LiMeng (Huawei) suggests this document be discussed together with other BDT documents (819 vs. 894). Zhendong (ZTE) provides response. Zhendong (ZTE) provides response to Nokia. Alessio(nokia) suggests to put a pause on this BDT topic and come back in athens. The changes in this CR are not agreeable to nokia. ==== General Revisions Deadline ==== Alessio(nokia) confirms this is not agreeable to nokia (to finalize status in chair notes). ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500191 | CR | Approval | 23.503 CR1458 (Rel-19, 'F'): Energy Saving Subscription management in PCF | Qualcomm Incorporated | Rel-19 | Merge into S2-2500731? Merged into S2-2501214 | Jungshin (Samsung) proposed to merge the CR to S2-2500731. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500731 | CR | Approval | 23.503 CR1486 (Rel-19, 'F'): Policy control with energy saving consideration. | Vivo | Rel-19 | Discuss as baseline and merge S2-2500191 and S2-2500753? r04 agreed. Revised in e-mail session to S2-2501214, merging S2-2500191, S2-2500753, S2-2500844 and S2-2500891 | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500191 and S2-2500753. Wen (vivo) provides r01 with merging 0191, 0753, 0891. Juan Zhang (Qualcomm) provides comments to r01. Magnus (Ericsson) Agrees with Qualcomm and propose to remove the EIF - PCF interactions in the CR. Wen (vivo) provides r02. LiMeng (Huawei) considers 0816 and this document are mutually exclusive and eventually we will select one of the two. Juan Zhang (Qualcomm) replies to LiMeng (Huawei). Wen(vivo) provides r03 with a small correction Alessio(Nokia) is ok with r02 Magnus O (Ericsson) r02 look ok to me Josep (Deutsche Telekom) comments, provides r04 with editorials/cover sheet Wen (vivo) is ok for r04. Genadi (Lenovo) is OK with r04. Juan Zhang (Qualcomm) is OK with r04. Magnus O (Ericsson) is also ok wit r04s Alessio(Nokia) then recommends we remove PCF-EIF interface in 189 ==== General Revisions Deadline ==== Xiaoyan (CATT) is fine with r04 and would like to cosign. Josep (Deutsche Telekom) would like to co-sign Alessio(Nokia) ok r04 Marco (Huawei) can accept only R04 with the change of the name of indicator to 'UE energy saving indicator' Magnus (Ericsson) is ok with r04 Wen (vivo) suggests to align the name (i.e., Energy Saving indicator) with 23.501 in this meeting DongYeon (Samsung) would like to co-sign on r04. Zhendong (ZTE) is fine with r04 and would like to co-sign. ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501214 | CR | Approval | 23.503 CR1486R1 (Rel-19, 'F'): Policy control with energy saving consideration. | Vivo, Qualcomm Incorporated, MediaTek Inc, ZTE, Deutsche Telekom, CATT, Samsung | Rel-19 | Revision of S2-2500731r04, merging S2-2500191, S2-2500753, S2-2500844 and S2-2500891. Approved | Agreed | |
| 19.4.2 | S2-2500753 | CR | Approval | 23.503 CR1489 (Rel-19, 'F'): Adding the changes for input data to PCF | MediaTek Inc. | Rel-19 | Merge into S2-2500731? Merged into S2-2501214 | Jungshin (Samsung) proposed to merge the CR to S2-2500731. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500891 | CR | Approval | 23.503 CR1495 (Rel-19, 'F'): Adding the Energy saving indicator to the AMF input | ZTE | Rel-19 | Discuss the second change 6.1.3.5 only? Merged into S2-2501214 | Jungshin (Samsung) proposed to discuss the second change 6.1.3.5 only to avoid overlap with other CR. Zhendong (ZTE) proposes to mark this CR as merged to 00731. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500844 | CR | Approval | 23.503 CR1403R2 (Rel-19, 'F'): Energy related subscription data and policy control | CATT | Rel-19 | Revision of S2-2411502? Revision of S2-2411502. Merged into S2-2501214 | Zhendong (ZTE) provides comments. Magnus O (Ericsson) proposes to Note the document. Marco (Huawei) expresses concern that some parts seems beyond correction Alessio(Nokia ) proposes to note the CR as we should document the impacts in existing clauses ==== General Revisions Deadline ==== Xiaoyan (CATT) proposes to mark the CR as merged in S2-2500731 ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500819 | CR | Approval | 23.503 CR1492 (Rel-19, 'F'): Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500894. Bahador (NTT DOCOMO) provides comments. Zhendong (ZTE) provides r01. Zhendong (ZTE) provides r02. Alessio(Nokia) indicats the CR should be noted as the existing text is better. The concept was energy indicator indicates to operator interest in energy saving but it is not really a trigger for this to be accepted or explored by the operator that is more than free to save energy via BDT policies without any indicator. Mirko (Huawei) responds to the comments. Bahador (NTT DOCOMO) provides r03. Alessio(Nokia) proposes to note the paper as it is suggesting restriction of data rate is a BDT measure that aims at energy saving, whish is not part of the original feature. We should keep this minimal and leave any policy to the operator and outside the standards discussion ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500894 | CR | Approval | 23.503 CR1496 (Rel-19, 'F'): Clarification on the BDT policy decision | ZTE | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500819. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | - | - | - | WT#2: Procedure UE Subscription and Policy | - | - | Docs:=11 | - | |
| 19.4.2 | S2-2500190 | CR | Approval | 23.502 CR5208 (Rel-19, 'F'): Clean up ENs about EnergySys | Qualcomm Incorporated | Rel-19 | Merge into S2-2500730 and S2-2500358? Merged into S2-2501215 | Jungshin (Samsung) proposed to merge the CR to S2-2500730 and S2-2500358. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500730 | CR | Approval | 23.502 CR5276 (Rel-19, 'F'): Energy saving subscription and AM policy. | Vivo | Rel-19 | Discuss as baseline and merge S2-2500190, S2-2500890 and S2-2500843? r02 agreed. Revised in e-mail session to S2-2501215, merging S2-2500190 and S2-2500890 | Wen (vivo) provides r01 with merging 0190, 0843, 0890. Magnus (Ericsson) provides r02 Marco (Huawei) asks clarification to r02 Alessio(Nokia) ok with r02 Magnus O (Ericsson) Responds to Marco ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r02 and asks co-sign the CR. Josep (Deutsche Telekom) would like to co-sign Marco (Huawei) can accept only R02 with the change of the name of indicator to 'UE energy saving indicator' Wen (vivo) suggests to align the name (i.e., Energy Saving indicator) with 23.501 in this meeting DongYeon (Samsung) would like to cosign to r02. Zhendong (ZTE) is fine r02 and would like to co-sign. ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501215 | CR | Approval | 23.502 CR5276R1 (Rel-19, 'F'): Energy saving subscription and AM policy. | Vivo, Qualcomm Incorporated, ZTE, Deutsche Telekom, CATT, Samsung | Rel-19 | Revision of S2-2500730r02, merging S2-2500190 and S2-2500890. Approved | Agreed | |
| 19.4.2 | S2-2500890 | CR | Approval | 23.502 CR5300 (Rel-19, 'F'): Adding Energy saving indicator to AM policy procedure | ZTE | Rel-19 | Merge into S2-2500730? Merged into S2-2501215 | Jungshin (Samsung) proposed to merge the CR to S2-2500730. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500843 | CR | Approval | 23.502 CR5133R1 (Rel-19, 'F'): Energy related subscription data and policy control | CATT | Rel-19 | Revision of S2-2411503. Noted in e-mail session | Jungshin (Samsung) proposed to discuss 5.2.12.2.1 only, and merge other changes to S2-2500730. Xiaoyan (CATT) provides r01, only keeping changes in clause 5.2.12.2.1. Zhendong (ZTE) provides comments. Alessio(Nokia) proposes to note as the first change is note needed (and actually incorrect if the data is AM subscription data) and the second seems a new feature to use this in policy data. Magnus (Ericsson) agrees with Zhendong and propose to either note or consider this doc merged into 0253. ==== General Revisions Deadline ==== Marco (Huawei) agrees to consider merged into 0253 or noted ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500253 | CR | Approval | 23.502 CR5144R1 (Rel-19, 'F'): Energy Saving indicator | Ericsson, AT&T | Rel-19 | Handle as baseline and merge S2-2500855? Revision of S2-2411715. CC#4: r05 + changes agreed. Revised in e-mail session to S2-2501216, merging S2-2500855 | Jungshin (Samsung) proposed to discuss the CR as baseline and merge S2-2500855. LaeYoung (LGE) comments. Magnus O (Ericsson) is ok with r01 Alessio(Nokia) provides r01 Josep (Deutsche Telekom) comments, provides r03, co-signs, uploaded r02 by mistake Magnus O (Ericsson) responds to Josep Josep (Deutsche Telekom) replies to Magnus, comments. Provides r04 Marco (Huawei) considering the pending answer from to RAN (LS OUT S2-2413034). An EN shall be added where the indicator is added, such as 'Editor's note: Whether and how the indicator is used in the NG-RAN is pending from RAN answer.' Or a similar text Alessio(Nokia is ok with r04 Magnus O (Ericsson) provides r05 Josep (Deutsche Telekom) is fine with r05 Alessio(Nokia) fine with r05 ==== General Revisions Deadline ==== LaeYoung (LGE) is also fine with r05. Juan Zhang (Qualcomm) is fine with r05. Xiaoyan (CATT) objects to all the revisions (including r00), can accept r05 with removing changes in step 21 of clause 4.2.2.2.2 and in clause 4.2.3.2. Iskren (NEC) is OK with r05. Marco (Huawei) can accept only R05 with the change of the name of indicator to 'UE energy saving indicator' Magnus O (Ericsson) proposes to agree r05 on the condition that RAN2/3 send a positive LS response Magnus O (Ericsson) responds to Marco Wen (vivo) suggests to align the name (i.e., Energy Saving indicator) with 23.501 in this meeting DongYeon (Samsung) would like to cosign. Alessio(Nokia) agrees with magnus we should agree r05 and we can then make the approval of the CR conditional to receiving positive RAN feedback for the RAN part. If we change name, I can only accept something like 'Energy Assistance Information' but we can do it by revising this at the next meeting once we reach agreement on a name. For now we keep what we have. ==== Comments Deadline ==== Xiaoyan (CATT) objects to all the revisions (including r00), can accept r05 with removing changes in step 21 of clause 4.2.2.2.2 and step 12 of clause 4.2.3.2. DongYeon (Samsung) supports agreeing r05 and revise the names overall in next meeting. Magnus O (Ericsson) proposes resolutions for CC#4 | Revised |
| 19.4.2 | S2-2501216 | CR | Approval | 23.502 CR5144R2 (Rel-19, 'F'): Energy Saving indicator | Ericsson, AT&T, Deutsche Telekom, NEC, Samsung | Rel-19 | Revision of S2-2500253r05 + changes, merging S2-2500855. This CR was agreed | Agreed | |
| 19.4.2 | S2-2500855 | CR | Approval | 23.502 CR5293 (Rel-19, 'C'): Procedure for delivering the Energy Saving information for the UE | Samsung | Rel-19 | Merge into S2-2500253? Merged into S2-2501216 | Jungshin (Samsung) proposed to merge the CR to S2-2500253. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.4.2 | S2-2500359 | CR | Approval | 23.502 CR5240 (Rel-19, 'F'): Negotiation for future background data transfer considering energy | NTT DOCOMO | Rel-19 | Postponed in e-mail session | Jungshin (Samsung) proposed to discuss the CR as baseline and merge S2-2500587 and S2-2500893. Juan Zhang (Qualcomm) provides comments. Zhendong (ZTE) provides comments. LaeYoung (LGE) asks a Q for clarification. Bahador (NTT DOCOMO) provides clarification. Zhendong (ZTE) proposes to focus on the 503 CR, then make the alignment LaeYoung (LGE) replies to Bahador (NTT DOCOMO). Juan Zhang (Qualcomm) provides further comments Magnus O (Ericsson) comments Bahador (NTT DOCOMO) request from Juan Zhang (Qualcomm), Magnus O (Ericsson), Alessio (Nokia) for technical reasons why the concepts already agreed in the previous meetings and documented in 501 and 503 should not be reflected in 502. Alessio(Nokia) agrees with Magnus O (Ericsson) request to postpone the document. it seems introducing too many aspects that deserve discussions F2F ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.4.2 | S2-2500587 | CR | Approval | 23.502 CR5256 (Rel-19, 'F'): Enhancement for BDT with Energy related information | KDDI | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500359. Marco (Huawei) agrees to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | S2-2500893 | CR | Approval | 23.502 CR5301 (Rel-19, 'F'): Adding Energy indication to BDT procedure and service operation | ZTE | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the CR to S2-2500359. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | - | - | - | WT#3 UP Path Adjustment | - | - | Docs:=1 | - | |
| 19.4.2 | S2-2500177 | CR | Approval | 23.501 CR5898 (Rel-19, 'F'): UP path selection by considering energy related information | China Mobile | Rel-19 | Noted in e-mail session | LaeYoung (LGE) proposes to NOTE this CR because this topic is out of scope in this release. Alessio(Nokia) supports LG electronics in their proposal to NOTE this CR because this topic is out of scope in this release. Magnus O (Ericsson) agrees with LGE and Nokia the document should be noted Juan Zhang (Qualcomm) also supports the previous comments to note the CR. Dan (China Mobile) OK to NOTE this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.4.2 | - | - | - | LS Out | - | - | Docs:=3 | - | |
| 19.4.2 | S2-2500776 | LS OUT | Approval | [DRAFT] LS on renewable energy information collection from OAM to EIF | vivo | Rel-19 | Discuss as baseline and merge S2-2500817? r03 agreed. Revised in e-mail session to S2-2501217. | Jungshin (Samsung) proposed to discuss the Tdoc as baseline and merge S2-2500817. Zhuoyun (vivo) provides r01 by merging S2-2500817. Bahador (NTT DOCOMO) provides comments. Marco (Huawei) provides r02 Zhuoyun (vivo) provides r03. ==== General Revisions Deadline ==== Marco (Huawei) OK with R03 ==== Comments Deadline ==== | Revised |
| 19.4.2 | S2-2501217 | LS OUT | Approval | LS on energy information collection from OAM to EIF | SA WG2 | Rel-19 | Revision of S2-2500776r03. Approved | Approved | |
| 19.4.2 | S2-2500817 | LS OUT | Approval | [DRAFT] LS on OAM energy information exposure | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jungshin (Samsung) proposed to merge the Tdoc to S2-2500776. Marco (Huawei) oK to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.5.1 | - | - | - | Study on MPS for IMS Messaging and SMS services (FS_MPS4msg) | - | - | Docs:=0 | - | |
| 19.5.2 | - | - | - | MPS for IMS Messaging and SMS services (MPS4msg) | - | - | Docs:=0 | - | |
| 19.6.1 | - | - | - | Study on Architecture Enhancements for Vehicle Mounted Relays Phase 2 (FS_VMR_Ph2) | - | - | Docs:=0 | - | |
| 19.6.2 | - | - | - | Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2) | - | - | Docs:=0 | - | |
| 19.7.1 | - | - | - | Study on System Enhancement for Proximity-based Services in 5GS – Phase 3 (FS_5G_ProSe_Ph3) | - | - | Docs:=0 | - | |
| 19.7.2 | - | - | - | System Enhancement for Proximity-based Services in 5GS – Phase 3 (5G_ProSe_Ph3) | - | - | Docs:=52 | - | |
| 19.7.2 | - | - | - | LS In and responses | - | - | Docs:=13 | - | |
| 19.7.2 | S2-2500045 | LS In | Action | LS from RAN WG2: LS to SA2 on relay discovery announcement | RAN WG2 (R2-2411184) | Rel-19 | Responses drafted in S2-2500323, S2-2500377, S2-2500390, S2-2500433, S2-2500502, S2-2500649. Final response in S2-2501334 | LaeYoung (LGE) replies to Hong (Qualcomm) and asks a Q. Hong (Qualcomm) comments. LaeYoung (LGE) proposes to discuss this issue in this thread to derive consensus. Fei (OPPO) comments Deng Qiang (CATT) shares similar view with QC and OPPO Hao (ZTE) provides comment. LaeYoung (LGE) replies to Hao (ZTE). Zhang (Huawei) support the view of QC and LGE Hong (Qualcomm) replies to LaeYoung (LGE). LaeYoung (LGE) suggests to use S2-2500390 as baseline reply LS and S2-2500324 as baseline CR for clarification to be attached in the reply LS. Shabnam (Ericsson): do not agree to functionally change the existing spec without justification why, 2500433 provides way forward that does not require LS, as per CC#1 move discussion to incoming LS 2500045. LaeYoung (LGE) answers to Shabnam (Ericsson). Shabnam (Ericsson) asks clarification, see below: LaeYoung (LGE) answers to Jungje (Interdigital). Jungje(Interdigital) comments LaeYoung (LGE) replies to Shabnam (Ericsson) and Donghao (ZTE). Hao (ZTE) comments. Shabnam (Ericsson) starts discussion on this LS since companies don't have common views, see further comments. Jungje(Interdigital) responds to LaeYoung (LGE) Fei (OPPO) is ok with LaeYoung(LGE)'s suggestion. LaeYoung (LGE) replies to JungJe (Interdigital) and Zhang (Huawei). Zhang (Huawei) prefer the way proposed by LaeYoung (LGE) Zhang (Huawei) provide comments LaeYoung (LGE) replies to Hong (Qualcomm). LaeYoung (LGE) answers to Zhang (Huawei). Shabnam (Ericsson) provides comments Ok with LGE proposal with minor update to the NOTE. LaeYoung (LGE) asks a Q for clarification to Shabnam (Ericsson). Shabnam (Ericsson) provides comments yes the intention was to say for some Layer-2 IM Relay it indicates 'YES' while for some other Layer-2 IM Relay it indicates 'NO'. | Replied to |
| 19.7.2 | S2-2500323 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | CATT | Rel-19 | Response to S2-2500045. Merged into S2-2501334 | Merged | |
| 19.7.2 | S2-2500377 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | OPPO | Rel-19 | Response to S2-2500045. Merged into S2-2501334 | Merged | |
| 19.7.2 | S2-2500390 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | LG Electronics | Rel-19 | Response to S2-2500045. CC#4: r04 agreed. Revised in CC#4 to S2-2501334, merging S2-2500323, S2-2500377, S2-2500433, S2-2500502 and S2-2500649 | LaeYoung (LGE) provides r01 to try to move foward. LaeYoung (LGE) provides r02 where the answer is YES. ==== General Revisions Deadline ==== LaeYoung (LGE) answers to Shabnam (Ericsson). Shabnam (Ericsson) provides comments that Ericsson position was it could be either yes or no. RAN2 question does not ask for Model A only right? So to me response is ambiguous. As in 5.1.4.1 provisioned in ME etc. Shabnam (Ericsson) provides comments that as terminology confusion occurs, can we also add the Model B aspects you indicated for completeness sake? Thanks Zhang (Huawei) suggest to only focus on Model A LaeYoung (LGE) provides r03 and answers to Shabnam (Ericsson) and Zhang (Huawei). Zhang (Huawei) clarify that Model B is not straight forward Zhang (Huawei) is OK with r00, r01, r02, object r03 Deng Qiang (CATT) also understand RAN2 question is only about Model A ==== Comments Deadline ==== Shabnam (Ericsson) even though I would have liked a bit more clarity that Model B does not require PC5 pre-established, I can live with r03, object to other revisions including original. LaeYoung (LGE) suggests to go with r03 to move forward. ?? I support LaeYoung's suggestion to go with r03 for moving forward. Shabnam (Ericsson) thanks LaeYoung (LGE) and Zhang (Huawei), indeed addresses my comments more accurately in r04, I agree we should go with r04 LaeYoung (LGE) provides r04 taking wording suggestion from Zhang (Huawei) and proposes to go with r04. Zhang (Huawei) object r03, ask for clarification what is going on? Zhang (Huawei) is OK with r04 and thanks LaeYoung and Shabnam LaeYoung (LGE) agrees with Zhang (Huawei) and thinks r04 can be approved. ?? | Revised |
| 19.7.2 | S2-2501334 | LS OUT | Approval | Reply LS on relay discovery announcement | SA WG2 | Rel-19 | Revision of S2-2500390r04, merging S2-2500323, S2-2500377, S2-2500433, S2-2500502 and S2-2500649. This LS OUT was approved | Approved | |
| 19.7.2 | S2-2500433 | LS OUT | Approval | [DRAFT] LS Reply on relay discovery announcement | Ericsson | Rel-19 | Response to S2-2500045. Merged into S2-2501334 | Merged | |
| 19.7.2 | S2-2500502 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | Qualcomm Incorporated | Rel-19 | Response to S2-2500045. Merged into S2-2501334 | Merged | |
| 19.7.2 | S2-2500649 | LS OUT | Approval | [DRAFT] Reply LS on Relay Discovery Announcement | ZTE | Rel-19 | Response to S2-2500045. Merged into S2-2501334 | Merged | |
| 19.7.2 | S2-2500022 | LS In | Action | LS from SA WG3: LS on Multi-hop U2N Relay Architecture Aspects | SA WG3 (S3-245259) | Rel-19 | Responses drafted in S2-2500128, S2-2500326, S2-2500518. FInal response in S2-2501335 | Replied to | |
| 19.7.2 | S2-2500128 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | KPN N.V. | Rel-19 | Response to S2-2500022. Revised in CC#4 to S2-2501335, merging S2-2500326 and S2-2500518 | Zhang(Huawei) suggest to use this LS as the baseline to reply S2-2500022 Hong (Qualcomm) comments. Shabnam (Ericsson) asks some clarification and comments Jungje(Interdigital) comments for Q1 Nassima (KPN N.V.) supports the view of QC Jungje(Interdigital) responds. Zhang (Huawei) provide comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501335 | LS OUT | Approval | Reply LS on Multi-hop U2N Relay Architecture Aspects | SA WG2 | Rel-19 | Revision of S2-2500128, merging S2-2500326 and S2-2500518. This LS OUT was approved | Approved | |
| 19.7.2 | S2-2500326 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | CATT | Rel-19 | Response to S2-2500022. Merged into S2-2501335 | Zhang(Huawei) suggest to merge this LS into S2-2500128 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.7.2 | S2-2500518 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | Qualcomm Incorporated | Rel-19 | Response to S2-2500022. Merged into S2-2501335 | Zhang(Huawei) suggest to merge this LS into S2-2500128 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.7.2 | - | - | - | General | - | - | Docs:=3 | - | |
| 19.7.2 | S2-2500130 | CR | Approval | 23.502 CR5188R1 (Rel-19, 'F'): Update ProSe subscription data to support multi-hop relay | KPN N.V. | Rel-19 | Revision of S2-2412269. Approved | Agreed | |
| 19.7.2 | S2-2500131 | CR | Approval | 23.304 CR0519R1 (Rel-19, 'D'): Editorial corrections | KPN N.V. | Rel-19 | Revision of S2-2412270. Approved | Agreed | |
| 19.7.2 | S2-2500435 | CR | Approval | 23.304 CR0491R2 (Rel-19, 'F'): Introduction of multi-hop in the specification | Ericsson | Rel-19 | Revision of S2-2412344. Approved | Agreed | |
| 19.7.2 | - | - | - | UE-to-UE Relay | - | - | Docs:=12 | - | |
| 19.7.2 | S2-2500103 | CR | Approval | 23.304 CR0522 (Rel-19, 'F'): Clarification on triggering the diffusion of DNS information via MANET when End UE is disconnected | Huawei, HiSilicon | Rel-19 | Approved | Agreed | |
| 19.7.2 | S2-2500106 | CR | Approval | 23.304 CR0524 (Rel-19, 'F'): Update on Multihop U2U Relay for non-IP type PDU | Huawei, HiSilicon | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501288, merging S2-2500325 | Zhang(Huawei) provide r01 to merge S2-2500325 Naman (Samsung) have concerns with r01; provides r02 Zhang (Huawei) provide r03 and comments ==== General Revisions Deadline ==== Naman (Samsung) asks for clarifications Zhang (Huawei) provide comments Naman (Samsung) proposes to go with r03 ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501288 | CR | Approval | 23.304 CR0524R1 (Rel-19, 'F'): Update on Multihop U2U Relay for non-IP type PDU | Huawei, HiSilicon, CATT, Samsung | Rel-19 | Revision of S2-2500106r03, merging S2-2500325. Approved | Agreed | |
| 19.7.2 | S2-2500107 | CR | Approval | 23.304 CR0525 (Rel-19, 'F'): Update on Discovery of U2U Multihop Relay for IP PDU | Huawei, HiSilicon | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501289. | Hong (Qualcomm) comments. Zhang (Huawei) provide responses to Hong (Qualcomm) Hong (Qualcomm) replies to Zhang (Huawei). Hong (Qualcomm) replies to Zhang (Huawei) and provides r01. Zhang (Huawei) provides response Zhang (Huawei) thanks Hong (QC) and Ok with r01 Naman (samsung) asks for clarification Zhang (Huawei) provide comments ==== General Revisions Deadline ==== Naman (Samsung) provides comments ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501289 | CR | Approval | 23.304 CR0525R1 (Rel-19, 'F'): Update on Discovery of U2U Multihop Relay for IP PDU | Huawei, HiSilicon | Rel-19 | Revision of S2-2500107r01. Approved | Agreed | |
| 19.7.2 | S2-2500314 | CR | Approval | 23.304 CR0529 (Rel-19, 'F'): Update on multihop U2U Relay reselection procedure for non-IP type | InterDigital Communications | Rel-19 | Approved | Hong (Qualcomm) comments. JungJe(Interdigital) responded to Hong(Qualcomm) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.7.2 | S2-2500316 | CR | Approval | 23.304 CR0531 (Rel-19, 'F'): Update on multihop ProSe U2U Relay for non-IP type PDU | InterDigital Communications | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501290. | Zhang(Huawei) provide comments Jungje(Interdigital) provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501290 | CR | Approval | 23.304 CR0531R1 (Rel-19, 'F'): Update on multihop ProSe U2U Relay for non-IP type PDU | InterDigital Communications | Rel-19 | Revision of S2-2500316r01. Approved | Agreed | |
| 19.7.2 | S2-2500325 | CR | Approval | 23.304 CR0533 (Rel-19, 'F'): Corrections on multi-hop U2U Relay discovery of non-IP PDU type | CATT | Rel-19 | Merged into S2-2501288 | Deng Qiang (CATT) replies to Zhang(Huawei) Zhang(Huawei) provides comments and suggest to merge the CR into S2-2500106 Zhang(Huawei) provide comments Deng Qiang (CATT) clarified that SA3 assumption on RSC is only applied to U2N Relay. Zhang (Huawei) provide comments Deng Qiang (CATT) responds to Zhang (Huawei) Zhang (Huawei) confirms the CR is merged into S2-2500106 Deng Qiang (CATT) is fine this CR to be merged. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.7.2 | S2-2500436 | CR | Approval | 23.304 CR0492R2 (Rel-19, 'F'): Expansion of 5G ProSe Layer-3 UE-to-UE Relay functionality | Ericsson | Rel-19 | Revision of S2-2412346. Approved | Agreed | |
| 19.7.2 | S2-2500764 | CR | Approval | 23.304 CR0539 (Rel-19, 'F'): Procedures for ProSe Multihop U2U Relay reselection for Non-IP | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! r02 agreed. Revised in e-mail session to S2-2501291. | Zhang(Huawei) provide r01 Heng(China Telecom) provide r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501291 | CR | Approval | 23.304 CR0539R1 (Rel-19, 'F'): Procedures for ProSe Multihop U2U Relay reselection for Non-IP | China Telecom | Rel-19 | Revision of S2-2500764r02. Approved | Agreed | |
| 19.7.2 | - | - | - | UE-to-Network Relay | - | - | Docs:=24 | - | |
| 19.7.2 | S2-2500104 | DISCUSSION | Discussion | Discussion about IP (re)allocation during Multi-hop U2N Relay Reselection. | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 19.7.2 | S2-2500105 | CR | Approval | 23.304 CR0523 (Rel-19, 'F'): Clarification on Multi-hop Relay Reselection | Huawei, HiSilicon | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501292, merging S2-2500763 | Zhang(Huawei) provide r01 Heng(China Telecom) provide r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501292 | CR | Approval | 23.304 CR0523R1 (Rel-19, 'F'): Clarification on Multi-hop Relay Reselection | Huawei, HiSilicon, China Telecom | Rel-19 | Revision of S2-2500105r02, merging S2-2500763. Approved | Agreed | |
| 19.7.2 | S2-2500129 | CR | Approval | 23.304 CR0527 (Rel-19, 'F'): Correction of UE-to-Network Model B Discovery | KPN N.V. | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501293. | Hong (Qualcomm) comments. Zhang (Huawei) provides comments Zhang (Huawei) provides r01 Ihab Guirguis (FirstNet) responds Zhang (Huawei) provide comments Nassima (KPN N.V.) responds Nassima (KPN N.V.) provides r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501293 | CR | Approval | 23.304 CR0527R1 (Rel-19, 'F'): Correction of UE-to-Network Model B Discovery | KPN N.V., Huawei, HiSilicon | Rel-19 | Revision of S2-2500129r02. Approved | Agreed | |
| 19.7.2 | S2-2500313 | CR | Approval | 23.304 CR0528 (Rel-19, 'F'): Update on multihop ProSe U2N Relay with model B discovery | InterDigital Communications | Rel-19 | Approved | Agreed | |
| 19.7.2 | S2-2500315 | CR | Approval | 23.304 CR0530 (Rel-19, 'F'): Update on multihop ProSe U2N Relay Discovery | InterDigital Communications | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501294. | Hong (Qualcomm) comments and suggests changes. Zhang (Huawei) has similar view as QC Jungje(Interdigital) revised to r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501294 | CR | Approval | 23.304 CR0530R1 (Rel-19, 'F'): Update on multihop ProSe U2N Relay Discovery | InterDigital Communications | Rel-19 | Revision of S2-2500315r01. Approved | Agreed | |
| 19.7.2 | S2-2500324 | CR | Approval | 23.304 CR0532 (Rel-19, 'F'): Corrections on multi-hop U2N Relay discovery with Model A procedure | CATT | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501295, merging S2-2500389 and S2-2500503 | Zhang(Huawei) propose to use this CR as baseline to address Intermediate relay connection to parent relay in model A procedure Deng Qiang (CATT) provides r01. LaeYoung (LGE) provides r02. Zhang (Huawei) co-sign the CR ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501295 | CR | Approval | 23.304 CR0532R1 (Rel-19, 'F'): Corrections on multi-hop U2N Relay discovery with Model A procedure | CATT, LG Electronics, Huawei | Rel-19 | Revision of S2-2500324r02, merging S2-2500389 and S2-2500503. Approved | Agreed | |
| 19.7.2 | S2-2500327 | CR | Approval | 23.304 CR0534 (Rel-19, 'F'): Corrections on multi-hop U2N Relay architecture aspects | CATT | Rel-19 | Check Affected Clauses! Noted in e-mail session | Hong (Qualcomm) comments and OBJECTS the CR. Deng Qiang (CATT) responds to Hong (Qualcomm). Hong (Qualcomm) comments. Nassima (KPN N.V.) comments. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.7.2 | S2-2500386 | CR | Approval | 23.304 CR0535 (Rel-19, 'F'): Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN | LG Electronics | Rel-19 | Approved | Agreed | |
| 19.7.2 | S2-2500387 | LS OUT | Approval | [DRAFT] LS on Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN | LG Electronics | Rel-19 | Revised in e-mail session to S2-2501296. | Revised | |
| 19.7.2 | S2-2501296 | LS OUT | Approval | LS on Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN | SA WG2 | Rel-19 | Revision of S2-2500387. Approved | Approved | |
| 19.7.2 | S2-2500388 | DISCUSSION | Discussion | Discussion on behavior of Intermediate U2N Relay related to Model A discovery. | LG Electronics | Rel-19 | Noted in e-mail session | Noted | |
| 19.7.2 | S2-2500389 | CR | Approval | 23.304 CR0536 (Rel-19, 'F'): Clarification on behavior of Intermediate U2N Relay related to Model A discovery | LG Electronics | Rel-19 | Merged into S2-2501295 | Zhang(Huawei) propose to merge this CR into S2-2500324 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.7.2 | S2-2500434 | CR | Approval | 23.304 CR0490R1 (Rel-19, 'F'): Adding Path Failure Detection for Relay Reselection | Ericsson, FirstNet, Qualcomm Inc., AT&T | Rel-19 | Revision of S2-2411480. r01 agreed. Revised in e-mail session to S2-2501297. | Zhang(Huawei) provide comments Nassima (KPN N.V.) comments Shabnam (Ericsson) provides response to KPN and r01 addressing Huawei comments Zhang (Huawei) is OK with r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501297 | CR | Approval | 23.304 CR0490R2 (Rel-19, 'F'): Adding Path Failure Detection for Relay Reselection | Ericsson, FirstNet, Qualcomm Inc., AT&T | Rel-19 | Revision of S2-2500434r01. Approved | Agreed | |
| 19.7.2 | S2-2500503 | CR | Approval | 23.304 CR0537 (Rel-19, 'F'): Correction on conditions for Intermediate Relay to send Relay Discovery Announcement message | Qualcomm Incorporated | Rel-19 | Merged into S2-2501295 | Hong (Qualcomm) comments that the CR should be considered merged into S2-2500324, as it is related to the discussion of LS response in the thread of S2-2500045. ==== Comments Deadline ==== | Merged |
| 19.7.2 | S2-2500762 | CR | Approval | 23.304 CR0513R1 (Rel-19, 'F'): Update on multi-hop U2N Relay Discovery with Model A | China Telecom | Rel-19 | Revision of S2-2412248. WI Code should be 5G_ProSe_Ph3! r02 agreed. Revised in e-mail session to S2-2501298. | Hong (Qualcomm) comments. Heng(China Telecom) reply to Shabnam (Ericsson) Shabnam (Ericsson) doesn't existing text & note already handles optional parameter so regardless of the discussion on the LS, I think the CR is not needed/correct? Also we should fix the note to remove 'may' ?? Zhang(Huawei) provides comments Heng(China Telecom) replies to Hong (Qualcomm) comments and provides r01. Heng(China Telecom) replies to Hong (Qualcomm) comments and provides r02. Hong (Qualcomm) comments on r01. ==== General Revisions Deadline ==== Hong (Qualcomm) can accept r02 (not r01). Zhang (Huawei) suggest to go with r02 ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501298 | CR | Approval | 23.304 CR0513R2 (Rel-19, 'F'): Update on multi-hop U2N Relay Discovery with Model A | China Telecom | Rel-19 | Revision of S2-2500762r02. Approved | Agreed | |
| 19.7.2 | S2-2500763 | CR | Approval | 23.304 CR0538 (Rel-19, 'F'): Update on ProSe Multihop U2N Relay reselection based on Model A discovery | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! Merged into S2-2501292 | Heng(China Telecom) is ok to merge the CR into S2-2500105 Zhang(Huawei) suggest to merge the CR into S2-2500105 Zhang (Huawei) confirms that the CR is merged into S2-2500105 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.7.2 | S2-2500765 | CR | Approval | 23.304 CR0540 (Rel-19, 'F'): Correction on ProSe Multihop U2N Relay reselection for Model B | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! r01 agreed. Revised in e-mail session to S2-2501299. | Heng(China Telecom) provide r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.7.2 | S2-2501299 | CR | Approval | 23.304 CR0540R1 (Rel-19, 'F'): Correction on ProSe Multihop U2N Relay reselection for Model B | China Telecom | Rel-19 | Revision of S2-2500765r01. Approved | Agreed | |
| 19.8.1 | - | - | - | Study on User Identities and Authentication Architecture (FS_UIA_ARC) | - | - | Docs:=0 | - | |
| 19.8.2 | - | - | - | Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC) | - | - | Docs:=63 | - | |
| 19.8.2 | - | - | - | Multiple Non-3GPP Devices and UDR Notification to the PCF | - | - | Docs:=5 | - | |
| 19.8.2 | S2-2500240 | CR | Approval | 23.502 CR5218 (Rel-19, 'F'): QoS differentiation for multiple Non-3GPP devices | Ericsson, AT&T | Rel-19 | Noted in e-mail session | Srinivas (Nokia) provides comments and proposes the changes Zhendong (ZTE) provides r01. Dimitris (Lenovo) has a question for clarification on the UE behaviour when receiving the 'granted indication' Ashok (Samsung) provides comments Jianning (Xiaomi) provides comments Yildirim (Charter) comments; and also points out that the outcome of this CR can impact S2-2501043. Marco (Huawei) the 0240 & 1034 shall be merged since they are touching the same steps and cover the same issues. Duplication of discussion. Marco (Huawei) ask clarifications on r02 Mike (InterDigital) comments Pavan (Google) asks for some clarification. Magnus (Ericsson) provides r01 Magnus (Ericsson) provides comments Pavan (Google) attempts to merge 0240 and 1034 in r03 Mike (InterDigital) comments and is ok with r02. Ashok (Samsung) comments on r03 Sudeep (Apple) has comments on the part from 1034 merged to r03. Pavan (Google) responds to Sudeep (Apple). Ashok (Samsung) provides r04, add Samsung as co-signer Sudeep (Apple) responds to Pavan (Google). We think the approach of indicating all connected non-3GPP identifiers is not quite optimal. Dimitris (Lenovo) provides r05 ==== General Revisions Deadline ==== Pavan (Google) responds to Sudeep (Apple) and Dimitris (Lenovo). Srinivas (Nokia) prefers04; Ok with r03, r02; objects to rest of the versions. Magnus (Ericsson) objects to r05, are ok to go with r04 Marco (Huawei) accepts R05 and objects any other versions Jianning (Xiaomi) only accepts r05, object any other versions Yildirim (Charter) can accept r02, objects other revisions as per reasoning described below. Rahil (CableLabs) accepts r02 only, objects to other revisions Pavan (Google) cannot accept r01 or r02, can accept any later revision (r03, r04, r05) Zhendong (ZTE) proposes to go with r05. Ashok (Samsung) objects to r05. Dimitris (Lenovo) propose to agree r05 ==== Comments Deadline ==== | Noted |
| 19.8.2 | S2-2500215 | CR | Approval | 23.502 CR5212 (Rel-19, 'F'): SM Policy Association Modification for Non-3GPP Device Identifiers | Nokia, InterDigital Inc. | Rel-19 | Approved | Srinivas (Nokia) provides r01 ==== General Revisions Deadline ==== Naman (Samsung) prefers r00 Srinivas (Nokia) prefers r01, Ok with r00 as well. Zhendong (ZTE) is fine with r00. Yildirim (Charter) can accept r01 by replacing '(e.g., add, update, delete) ' with' (e.g.., update, delete)' ; OK with r00. Naman (Samsung) can accept only r00. objects to r01 Rahil (CableLabs) accepts r01 (with the change '(e.g., add, update, delete)' to (e.g., update, delete)), or r00 (with the change 'the Non-3GPP Device Identifier Information change by invoking' to 'the Non-3GPP Device Identifier Information change (e.g., update, delete) by invoking') Mike (InterDigital) proposes to AGREE 'r00 + change 'the Non-3GPP Device Identifier Information change by invoking' to 'the Non-3GPP Device Identifier Information change (e.g., update, delete) by invoking'' Srinivas (Nokia) accepts the proposal from Mike. Ashok (Samsung) gives some technical explanation about (e.g. add update delete). Yildirim (Charter) OK with the proposal from Mike (InterDigital). Rahil (CableLabs) responds to Ashok ==== Comments Deadline ==== Ashok (Samsung) clarifies Rahil Ashok (Samsung) responds to Mike (InterDigital) proposal and suggest to go with r00 only without adding any example'' | Agreed |
| 19.8.2 | S2-2501034 | CR | Approval | 23.502 CR5319 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | Check Affected Clauses! Noted in e-mail session | Mike (InterDigital) comments and provides r01 Srinivas (Nokia) provides views and asks for clarification Zhendong (ZTE) provides the comments. Marco (Huawei) better to align 502 to 501 description whatever it will be in 501. Magnus (Ericsson) don't see the need for this CR Yildirim (Charter) comments and asks few questions for clarification. Marco (Huawei) the 0240 & 1034 shall be merged since they are touching the same steps and cover the same issues. Duplication of discussion. Mike (InterDigital) comments that he is consider merging a bit later with 0240 based on progress for this CR and the 0240 CR Pavan (Google) provides some feedback and r02. Rahil (CableLabs) provides comments Jianning (Xiaomi) provides comments Pavan (Google) responds to Yildirim (Charter), Marco (Huawei), and Jianning (Xiaomi). ==== General Revisions Deadline ==== Mike (InterDigital) proposes to mark this paper as MERGED with S2-2500240. Srinivas (Nokia) concurs of marking the paper as MERGED with S2-2500240 Rahil (CableLabs) proposes to mark this paper as merged with S2-2400240, if not merged should be marked as Noted Yildirim (Charter) propose Postpone the CR as it was discussed as part of 0240. Pavan (Google) is OK to merge with 0240. ==== Comments Deadline ==== | Noted | |
| 19.8.2 | S2-2501043 | CR | Approval | 23.502 CR5321 (Rel-19, 'F'): Clarification to SMF and PCF behaviour during Session modification for handling device identifiers | Samsung | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501219, merging S2-2500807 | Myungjune (LGE) provides comments. Zhendong (ZTE) provides proposal. Naman (Samsung) replies to Mike (InterDigital) Naman (Samsung) provides r01. Mike (InterDigital) proposes to merge the first change into S2-2500240 and the second change into S2-2500807. Zhendong (ZTE) provides response. Srinivas (Nokia) provides views and indicates that 'result of 240' impacting first change. Ashok (Samsung) provides response to Srinivas (Nokia) Srinivas (Nokia) comments and asks for further clarification Ashok (Samsung) responds to Srinivas (Nokia) Marco (Huawei) agree with Mike's proposal to avoid duplication of discussion in different CRs Naman (Samsung) provides response to ZTE and LGE Marco (Huawei) comment on ACK (success/failure/reject) to request in case of list Naman (Samsung) replies to Zhendong (ZTE) Naman (Samsung) provides r02 ==== General Revisions Deadline ==== Srinivas (Nokia) Ok with r02 but with changes related to '4.16.5.1' only. '4.3.3.2' is already being treated in S2-2500240 Zhendong (ZTE) proposes to merge this to 0807. Naman (Samsung) provides comments to Zhendong (ZTE) Naman (Samsung) responds to Srinivas (Nokia) Zhendong (ZTE) provides response to Naman (Samsung). Naman (Samsung) provides response to Zhendong (ZTE) Marco (Huawei) agrees with Sriniva (NOKIA) to agree r02 only with '4.16.5.1' only and remove the part related to '4.3.3.2' Rahil (CableLabs) accepts r02 with second change only (to clause 4.16.5.1), not the first change (to clause 4.3.3.2) Naman (Samsung) proposes to go with r02 including the first change (4.3.3.2) since there is no conclusion on 0240 and the changes in this CR is just an alignment to what is written in 503 Rahil (CableLabs) believes this CR is dependent on S2-2400240 - if 240 gets agreed, r02 with 2nd change only is acceptable; if 240 does not agreed, r02 as it is acceptable. Srinivas (Nokia) Ok with r02 but with changes related to '4.16.5.1' only. '4.3.3.2' are to be considered if 2500240 / 2501034 are not agreed. ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501219 | CR | Approval | 23.502 CR5321R1 (Rel-19, 'F'): Clarification to SMF and PCF behaviour during Session modification for handling device identifiers | Samsung | Rel-19 | Revision of S2-2501043r02, merging S2-2500807. Approved | Agreed | |
| 19.8.2 | - | - | - | Moving NOTE 14 | - | - | Docs:=2 | - | |
| 19.8.2 | S2-2501042 | CR | Approval | 23.502 CR5320 (Rel-19, 'F'): Clarification on AF provisioning of Non-3GPP device identifier information | Samsung | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501220. | Srinivas (Nokia) provides comment on the note placement Naman (Samsung) replies to Srinivas (Nokia) Zhendong (ZTE) provides proposal. Naman (Samsung) provides comments Magnus (Ericsson) provides comments Rahil (CableLabs) provides comments Naman (Samsung) asks for clarification of Cablelab's and Ericsson's preference Myungjune (LGE) provides comments on coversheet. Naman (Samsung) provides r01 ==== General Revisions Deadline ==== Naman (Samsung) proposes to accept r01 Rahil (CableLabs) accepts r01 ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501220 | CR | Approval | 23.502 CR5320R1 (Rel-19, 'F'): Clarification on AF provisioning of Non-3GPP device identifier information | Samsung | Rel-19 | Revision of S2-2501042r01. Approved | Agreed | |
| 19.8.2 | - | - | - | TS 23.316, Annex C, Editor’s Note | - | - | Docs:=2 | - | |
| 19.8.2 | S2-2500216 | CR | Approval | 23.316 CR2140 (Rel-19, 'F'): Resolving EN related to PCF initiated Policy Updates | Nokia, InterDigital Inc. | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501221. | Srinivas (Nokia) provides r01 based on inputs from CC Magnus (Ericsson) thinks we only need to remove EN Rahil (CableLabs) provides r02 Yildirim (Charter) also agrees with Rahil (CableLabs). Marco (Huawei) agrees with Rahil Jianning (Xiaomi) provides comments Mike (InterDigital) is ok with r02 and comments that the NOTE, which is in an informative annex, helps explain things. ==== General Revisions Deadline ==== Srinivas (Nokia) prefers r02. Ok with r01 and r00 as well. Yildirim (Charter) supports r02. Please add Charter Communications as a supporting company. Rahil (CableLabs) accepts r02 ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501221 | CR | Approval | 23.316 CR2140R1 (Rel-19, 'F'): Resolving EN related to PCF initiated Policy Updates | Nokia, InterDigital Inc., CableLabs, Charter Communications | Rel-19 | Revision of S2-2500216r02. Approved | Agreed | |
| 19.8.2 | - | - | - | TS 23.316, Annex C | - | - | Docs:=3 | - | |
| 19.8.2 | S2-2500450 | CR | Approval | 23.316 CR2141 (Rel-19, 'F'): QoS differentiation of non-3GPP devices behind 5G-RG | CableLabs, Charter Communications | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501222. | Myungjune (LGE) provides comments. Yishan (Huawei) provides comments and r02 Rahil (CableLabs) provides r01 Agree with Myungjune (LGE)'s comments Myungjune (LGE) provides comments on r02. Yishan (Huawei) answers to Myungjune (LGE) Ashok (Samsung) provides comments Myungjune (LGE) replies to Yishan (Huawei) and proposes to remove mapping. Yildirim (Charter) agrees with the comments from CableLabs and LGE that r02 & r03 add new aspects that have not been concluded. Yishan (Huawei) answers to Rahil (CableLabs) and Myungjune (LGE), and provides r03. Myungjune (LGE) replies to Yishan (Huawei). Rahil (CableLabs) provides comments Yishan (Huawei) provides clarifications and r04 Mike (InterDigital) comments that some (or all) of the revisions after r01 seem to be pushing in updates that are not in line with the topic of the original intent of the CR. We should stick with r01 and not try mix topics. Yishan (Huawei) answers to Mike (InterDigital) and Rahil (CableLabs) ==== General Revisions Deadline ==== Rahil (CableLabs) responds to Yishan (Huawei) Myungjune (LGE) is ok with r01 and objects other revisions. Pavan (Google) is fine with r01 and cannot accept later revisions. Srinivas (Nokia) is Ok with r01, objects to the rest of the versions. Yildirim (Charter) can accept r01; object others. Lets discuss any new aspects proposed in other revisions in normative clauses of the specs at next meeting. Rahil (CableLabs) can accept r01 only, objects to other revisions Pavan (Google) can only accept r01. ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501222 | CR | Approval | 23.316 CR2141R1 (Rel-19, 'F'): QoS differentiation of non-3GPP devices behind 5G-RG | CableLabs, Charter Communications, Nokia | Rel-19 | Revision of S2-2500450r01. Approved | Agreed | |
| 19.8.2 | S2-2500556 | DISCUSSION | Approval | Discussion on Identification of non-3GPP devices behind 5G-RG. | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Mike (InterDigital) comments that this discussion paper should be NOTED. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.8.2 | - | - | - | EN on PDU Session Establishment | - | - | Docs:=1 | - | |
| 19.8.2 | S2-2500804 | CR | Approval | 23.501 CR6006 (Rel-19, 'F'): Resolve the EN on the PDU session establishment and Reference correction | ZTE | Rel-19 | Approved | Marco (Huawei) proposes to consider merged in 0485 Zhendong (ZTE) clarified that this CR is different from the part discussed in 485 Mike (InterDigital) comments that this paper should NOT be merged proposes that it be approved. It is a standalone change. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.8.2 | - | - | - | Stopping QoS Differentiation | - | - | Docs:=5 | - | |
| 19.8.2 | S2-2500485 | CR | Approval | 23.501 CR5963 (Rel-19, 'F'): Definition of non-3GPP device connection information | Qualcomm Incorporated, InterDigital | Rel-19 | CC#4: r07 agreed. Revised in e-mail session to S2-2501223, merging S2-2500239 and S2-2500553 | Myungjune (LGE) provides comments on r01. Kenny (Qualcomm) merges the changes to clause 5.52.3 in S2-2500553, S2-2500239, and S2-2500806, and provides r01. We'd like to take S2-2500485r01 as the thread for all discussion against clause 5.52.3 in TS 23.501. Srinivas (Nokia) provide comments Kenny (Qualcomm) replies to Srinivas and Myungjune. Zhendong (ZTE) provides comments. Srinivas (Nokia) provide response to Kenny and asks for clarification Marco (Huawei) provides r02 Jianning (Xiaomi) provides comments Ashok (Samsung) provides comments Yildirim (Charter) comments and provides answer to Myungjune (LGE)'s question. Kenny (Qualcomm) replies Myungjune and Marco, provides r04. Myungjune (LGE) asks question for clarification. Marco (Huawei) disagree on remove the 'may' since the UE may also never send and therefore no UIA :-) Pavan (Google) provides some comments and r03. Rahil (CableLabs) provides comments Myungjune (LGE) clarifies question to Kenny (Qualcomm). Myungjune (LGE) responses to Yildirim (Charter). Kenny (Qualcomm) replies Myungjune. Magnus (Ericsson) provides comments Yang (OPPO )comments that 'add/delete operation' is not needed Myungjune (LGE) responses to Kenny (Qualcomm) and Magnus (Ericsson). Sudeep (Apple) provides comments. Sudeep (Apple) responds to Magnus (Ericsson). Kenny (Qualcomm) replies Zhendong's comments. Yang (OPPO) comments to use PDU session modification to remove QoS flow for N3DBU. Zhendong (ZTE) provides question to r06. Yildirim (Charter) provides r07 with rewording of the Note added in r06 and editorial corrections. Kenny (Qualcomm) provides r06 with adding a note for IPv4v6 clarification. Rahil (CableLabs) provides r05 Sudeep (Apple) responds to Magnus' (Ericsson) question on multiple device identifiers mapped to same QoS Flow. ==== General Revisions Deadline ==== Srinivas (Nokia) prefers r07 with the replacement of the new Note 2 to the below suggestion or remove new Note 2. Objects to the rest of the versions. 'If IPv4v6 PDU Session is applied, it is up to UE implementation to determine to use IPv4 or IPv6 or both Address/prefix(sub) based on the associated traffic of the non-3GPP device and the IP allocation by the network to the PDU Session'. Magnus (Ericsson) can only accept r02, objects to r00,r01,r03,r04,r05,r06,r07 Zhendong (ZTE) prefer r07. Marco (Huawei) can only accept R07 and objects any other versions Jianning (Xiaomi) is ok with r07, and also live with r07 with suggested NOTE replacement by Srinivas (Nokia) Yildirim (Charter) accepts r07. Ok with r06 with editorials incorporated from r07. Objects other revisions. Kenny (Qualcomm) proposes to agree: r07 + replacement of NOTE 2 with: 'If IPv4v6 PDU Session is applied, it is up to UE implementation to determine to use IPv4 or IPv6 or both Address/prefix(sub) based on the associated traffic of the non-3GPP device and the IP allocation by the network to the PDU Session'. Rahil (CableLabs) accepts r07, objects to other revisions Kenny (Qualcomm) proposes to agree r07+ removal of NOTE 2, due to no consensus on the NOTE. Myungjune (LGE) is ok with both r07 and r07+removeal of NOTE 2. Mike (InterDigital) proposes to AGREE r07 + replacement of NOTE 2 with: 'If IPv4v6 PDU Session is applied, it is up to UE implementation to determine to use IPv4 or IPv6 or both Address/prefix(sub) based on the associated traffic of the non-3GPP device and the IP allocation by the network to the PDU Session'. ==== Comments Deadline ==== Magnus (Ericsson) for the sake of progress I withdraw the objection on r07 | Revised |
| 19.8.2 | S2-2501223 | CR | Approval | 23.501 CR5963R1 (Rel-19, 'F'): Definition of non-3GPP device connection information | Qualcomm Incorporated, InterDigital, ETRI | Rel-19 | Revision of S2-2500485r07, merging S2-2500239 and S2-2500553. CC#4 r07 confirmed as agreed. This CR was agreed | Agreed | |
| 19.8.2 | S2-2500555 | CR | Approval | 23.502 CR5255 (Rel-19, 'F'): Removal of N3GPP device from UDR | Huawei, Hisilicon | Rel-19 | r06 agreed. Revised in e-mail session to S2-2501224. | Srinivas (Nokia) provide comments and proposes the change in text Marco (Huawei) answers to Srinivas (Nokia) and provides r01 Magnus (Ericsson) cannot accept any of the proposed updates in this CR Jianning (Xiaomi) provides comments Marco (Huawei) propose to merge in 0240 & 1034 discussion, since same issues and same discussion. Rahil (CableLabs) provides r02 Myungjune (LGE) provides comments. Mike (InterDigital) comments and provides r03 to only focus only on changing the user plane information and deletion of the information from the UDR. Marco (Huawei) is OK to limit the scope of the CR Magnus (Ericsson) can only accept r03 if change 2 is removed, objects to all previous revisions (r00,r01,r02) Yishan (Huawei) provides r04 on top of r03 to capture the comment from Myungjune (LGE) Srinivas (Nokia) comments on the first change 1a Yishan (Huawei) provides r05 to capture the comments from Srinivas (Nokia) Xiaoyan (CATT) provides comments Yishan (Huawei) answers to Xiaoyan (CATT) and provides r06 ==== General Revisions Deadline ==== Naman (Samsung) provides comments on r06 Magnus (Ericsson) objects to r00-r02 can only accept r03, r04,r05,r06 if 'change 2' is removed. I.e. Objects to any change of clause 4.15.6.2. Yishan (Huawei) is ok to go with r06 + removing the change 2 (i.e. removing clause 4.15.6.2) Srinivas (Nokia) is Ok only with r05, r06 with or without change 2. Jianning (Xiaomi) is Ok only with r05, r06 with or without change 2. Yildirim (Charter) Ok with only r06 Naman(Samsung) is Ok only r06 + removal of change 2 + change 'shall' to 'may' after PCF Yishan (Huawei) is ok with the suggestion from Naman(Samsung) to go with r06 + removal of change 2 + change 'shall' to 'may' after PCF Rahil (CableLabs) accepts r06 only, objects to other revisions ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501224 | CR | Approval | 23.502 CR5255R1 (Rel-19, 'F'): Removal of N3GPP device from UDR | Huawei, Hisilicon, China Telecom | Rel-19 | Revision of S2-2500555r06. Approved | Agreed | |
| 19.8.2 | S2-2500846 | CR | Approval | 23.503 CR1493 (Rel-19, 'F'): Clarification on policy control for non-3GPP devices connecting behind a UE | CATT | Rel-19 | Noted in e-mail session | Zhendong (ZTE) provides comments. Marco (Huawei) supports the proposals Jianning (Xiaomi) provides comments Srinivas (Nokia) provides comment ==== General Revisions Deadline ==== Naman (Samsung) objects to this CR and any revision of it Srinivas (Nokia) asks to Note the CR Rahil (CableLabs) proposes to Note this CR ==== Comments Deadline ==== | Noted |
| 19.8.2 | - | - | - | TS 23.501 Clause 5.52.3 Updates | - | - | Docs:=4 | - | |
| 19.8.2 | S2-2500553 | CR | Approval | 23.501 CR5975 (Rel-19, 'F'): User plane information related to N3GPP device within PDU session modification | Huawei, HiSilicon | Rel-19 | Merged into S2-2501223 | Kenny (Qualcomm) merged the changes to S2-2500485r01. Can we propose to mark this CR as merged? Srinivas (Nokia) provide comment on the CR Marco (Huawei) ok to considered merged into 0485r01. ==== General Revisions Deadline ==== Rahil (CableLabs) proposes to mark this as merged into S2-2500485 ==== Comments Deadline ==== | Merged |
| 19.8.2 | S2-2500806 | CR | Approval | 23.501 CR6007 (Rel-19, 'F'): Clarification on session management enhancement | ZTE | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501225. | Kenny (Qualcomm) merged the changes to S2-2500485r01. Can we propose to mark this CR as merged? Zhendong (ZTE) proposes it as separate. Srinivas (Nokia) asks for clarification on the CR Zhendong (ZTE) provides response to Nokia. Zhendong (ZTE) provides r01. ==== General Revisions Deadline ==== Marco (Huawei) OK with R01 Rahil (CableLabs) believes this CR is dependent on S2-2500240 - if 240 gets agreed, no revision of this CR is acceptable; if 240 does not get agreed, r01 is ok Mike (InterDigital) comments that it is clear that 0242 will not progress at this meeting. So that it is ok to AGREED r01. ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501225 | CR | Approval | 23.501 CR6007R1 (Rel-19, 'F'): Clarification on session management enhancement | ZTE | Rel-19 | Revision of S2-2500806r01. Approved | Agreed | |
| 19.8.2 | S2-2500239 | CR | Approval | 23.501 CR5905 (Rel-19, 'F'): Adding PDU session type IPv4v6 | Ericsson, AT&T | Rel-19 | Merged into S2-2501223 | Kenny (Qualcomm) merged the changes to S2-2500485r01. Can we propose to mark this CR as merged? Mike (InterDigital) proposes to merge this into S2-2500485. Magnus (Ericsson) agrees that it can be merged with 0485 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.8.2 | - | - | - | TS 23.501 Clause 5.52.2 Updates | - | - | Docs:=5 | - | |
| 19.8.2 | S2-2500461 | CR | Approval | 23.501 CR5960 (Rel-19, 'F'): Clarification on UE triggering request for change of QoS | Apple | Rel-19 | r06 agreed. Revised in e-mail session to S2-2501226. | Marco (Huawei) asks clarification Srinivas (Nokia) provides comment Sudeep (Apple) responds to questions. Mike (InterDigital) comments and provides r01 Jianning (Xiaomi) provides comments Mike (InterDigital) provides r05 which is an editorial fix on r04 Sudeep (Apple) provides r04. Sudeep (Apple) responds to Ashok (Samsung). Ashok (Samsung) thinks this CR is not needed but can live with r02. Not ok with r03 Sudeep (Apple) provides r03. Rahil (CableLabs) provides r02 Marco (Huawei) minor comments Rahil (CableLabs) provides r06 ==== General Revisions Deadline ==== Marco (Huawei) OK with R06 Ashok (Samsung)is OK with R06 Rahil (CableLabs) accepts r06, objects to other revisions ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501226 | CR | Approval | 23.501 CR5960R1 (Rel-19, 'F'): Clarification on UE triggering request for change of QoS | Apple | Rel-19 | Revision of S2-2500461r06. Approved | Agreed | |
| 19.8.2 | S2-2500854 | CR | Approval | 23.501 CR6016 (Rel-19, 'F'): Correction of description on support of N3GPP device behind UE | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) provides comments. Myungjune (LGE) provides comments. Srinivas (Nokia) provide comments Zhendong (ZTE) provides comments. Marco (Huawei) answer to the various comments and provides r01 Pavan (Google) provides some comments. Rahil (CableLabs) provides comments Marco (Huawei) provide r02 Srinivas (Nokia) provide comments to Marco ==== General Revisions Deadline ==== Srinivas (Nokia) asks to Note the paper Rahil (CableLabs) accepts r02 with the removal of 'as per definition in clause 5.52' Pavan (Google) can only accept r01. ==== Comments Deadline ==== | Noted |
| 19.8.2 | S2-2501022 | CR | Approval | 23.501 CR6053 (Rel-19, 'F'): Further details for QoS information | Xiaomi | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501227. | Marco (Huawei) proposes to move the changes in one of 503 CRs and refer to it Srinivas (Nokia) provides comment Yildirim (Charter) comments and asks clarification on the reference introduced in r01 Mike (InterDigital) comments and provides r01 Marco (Huawei) comments Jianning (Xiaomi) provides comments, and provide r02 Yildirim (Charter) provides r03 with minor correction. Mike (InterDigital) thanks Jianning (Xiaomi) and Yildirim (Charter) and supports r02. ==== General Revisions Deadline ==== Srinivas (Nokia) as indicated earlier this change is not required, but can live with only r03, object to rest of the revisions. Jianning (Xiaomi) is ok with r03 Marco (Huawei) I can live with R03, NOK to R00 Rahil (CableLabs) accepts r03 only, objects to other revisions ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501227 | CR | Approval | 23.501 CR6053R1 (Rel-19, 'F'): Further details for QoS information | Xiaomi | Rel-19 | Revision of S2-2501022r03. Approved | Agreed | |
| 19.8.2 | - | - | - | TS 23.501 Clause 5.52.1 Updates | - | - | Docs:=3 | - | |
| 19.8.2 | S2-2501021 | CR | Approval | 23.501 CR6052 (Rel-19, 'F'): Correction for UE SUPI | Xiaomi | Rel-19 | Noted in e-mail session | Marco (Huawei) disagrees with the proposal Magnus (Ericsson) provides comments Srinivas (Nokia) asks for clarification Kenny (Qualcomm) provides comments. Marco (Huawei) proposes to NOTE this document Jianning (Xiaomi) provides comments. The descriptions in both 501 and 502 are not aligned with each other. So it needs to be corrected. Naman (Samsung) proposes to note the CR ==== General Revisions Deadline ==== Srinivas (Nokia) asks to Note the CR ==== Comments Deadline ==== | Noted |
| 19.8.2 | S2-2500530 | CR | Approval | 23.501 CR5970 (Rel-19, 'F'): Clarification on roaming support for Non-3GPP Device Identifier | LG Electronics | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501228. | Myungjune (LGE) responses to Mike (InterDigital). Mike (InterDigital) comments that he is not ok with this CR and asks questions. Ashok (Samsung) comments. Myungjune (LGE) provides r01. Srinivas (Nokia) comments on the way forward Myungjune (LGE) responses to Srinivas (Nokia). Mike (InterDigital) objects to r00 and is ok with r01. ==== General Revisions Deadline ==== Myungjune (LGE) is OK with r01. ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501228 | CR | Approval | 23.501 CR5970R1 (Rel-19, 'F'): Clarification on roaming support for Non-3GPP Device Identifier | LG Electronics | Rel-19 | Revision of S2-2500530r01. Approved | Agreed | |
| 19.8.2 | - | - | - | TS 23.316 | - | - | Docs:=1 | - | |
| 19.8.2 | S2-2500462 | CR | Approval | 23.316 CR2142 (Rel-19, 'F'): Clarification on AF-5GC interaction for provisioning non-3GPP device identifiers | Apple | Rel-19 | Noted in e-mail session | Myungjune (LGE) responses to Rahil (CableLabs) and Yildirim (Charter). Yildirim (Charter) comments Rahil (CableLabs) provides comments Myungjune (LGE) provides comments. Rahil (CableLabs) responds to Sudeep (Apple) Sudeep (Apple) provides comments on r01. Rahil (CableLabs) provides r01 Sudeep (Apple) responds to the discussion and proposes a way forward. Sudeep (Apple) provides r02. Ashok (Samsung) comments that 461 paper revision is uploaded here Sudeep (Apple) thanks Ashok (Samsung) and provides the correct link for 462r02. Ashok (Samsung) comments on r02 and feels this CR is not needed Sudeep (Apple) responds to Ashok (Samsung) and explains that CR is clarifying AF-5GC interaction. Srinivas (Nokia) comments Sudeep (Apple) provides r03 and responds to Srinivas (Nokia). Ashok (Samsung) still believe this CR is not needed as 5G-RG and AF interaction is mentioned which is not in our scope Sudeep (Apple) responds to Ashok (Samsung). The same 5G-RG-AF interaction, which is out of 3GPP scope, is already mentioned in step 1. So we need this correction to make sense of this call flow. ==== General Revisions Deadline ==== Naman (Samsung) comments that changes are not acceptable Sudeep (Apple) responds to Naman (Samsung) and requests him to look back at the discussion that happened with r01 for this Tdoc. The revisions are based on inputs from other companies who see such an interaction between 5G-RG and AF possible. Myungjune (LGE) supports r03. Naman (Samsung) responds to Sudeep (Apple) assuring that the comments were made taking into account previous discussion; still have concerns with r01, r02, r03; can live with r00 + changing AF -> operator portal in Step 1 Sudeep (Apple) prefers r03 and provides answers to Naman (Samsung) requesting to reconsider position on r03 . Naman (Samsung) replies to Sudeep (Apple) Sudeep (Apple) provides additional clarifications to Naman (Samsung). Marco (Huawei) prefers R03 Naman (Samsung) objects to r00, r01,r02,r03, can accept r00 + 'AF'->'operator portal' in step 1 Yildirim (Charter) supports r03. Ok with r01 and r02. Objects r00. Sudeep (Apple) prefers r03, but can also live with r00+'AF'->'operator portal' in step 1 with the understanding that there is nothing preventing operator portal in the AF to get additional application layer information before responding to the user. Objects to r01 and r02. Rahil (CableLabs) accepts r03, objects to r00 ==== Comments Deadline ==== | Noted |
| 19.8.2 | - | - | - | TS 23.503 | - | - | Docs:=7 | - | |
| 19.8.2 | S2-2500242 | CR | Approval | 23.503 CR1462 (Rel-19, 'F'): QoS differentiation results per each Non-3GPP device | Ericsson, AT&T | Rel-19 | Postponed in e-mail session | Ashok (Samsung) is not OK with this CR Srinivas (Nokia) provides r02 Marco (Huawei) comments and alignment 502/503 discussion needs to be considered Mike (InterDigital) comments Magnus (Ericsson) provides r01 Magnus (Ericsson) provides r03 Srinivas (Nokia) provides r04 Srinivas (Nokia) comments and provides feedback to Magnus Jianning (Xiaomi) provides comments, and seek the clearification why to define new term 'Non-3GPP Device Identification Granted', to replace the agreed text. Thanks! Sudeep (Apple) provides comments. Marco (Huawei) disagree to r03 on different information in case of 1 N3GPP ID or multiple, since a list can have 1 entry Ashok (Samsung) responds to Marco (Huawei) Marco (Huawei) responds to Ashok (Samsung) Srinivas (Nokia) provides r05 Ashok (Samsung) comments on r05 and provides r06 Ashok (Samsung) clarifies to Marco (Huawei) Magnus (Ericsson) provides r07 Dimitris (Lenovo) raises concerns with including a new parameter 'Non-3GPP Device Connection Information Result'. Propose to postpone Ashok (Samsung) would like to Co-Sign if this paper progress as the changes of Samsung paper is handled. Otherwise Samsung 1044 paper will go through Srinivas (Nokia) tries to clarify to Dimitris and asks clarification Dimitris (Lenovo) responds to Srinivas Xiaoyan (CATT) provides comments. Srinivas (Nokia) responds to Dimitris Rahil (CableLabs) provides comments ==== General Revisions Deadline ==== Rahil (CableLabs) responds to Dimitris (Lenovo) Srinivas (Nokia) prefers r07, Ok with r06. The CR is only expanding from single identifier scenario to multiple identifier scenario. Dimitris (Lenovo) suggests a way forwards based on r07 Marco (Huawei) objects to any versions Jianning (Xiaomi) objects to any version, suggest to postpone this CR. Because we don't see the value to bring additional new things that is out of conclusion at this moment, to support a corner case. Yildirim (Charter) OK with r07. Objects other revisions. Changes in clause 6.1.3.1 clashes with S2-2501044. Rahil (CableLabs) is ok with r07 ==== Comments Deadline ==== | Postponed |
| 19.8.2 | S2-2500532 | CR | Approval | 23.503 CR1478 (Rel-19, 'F'): Clarification on UE behaviour when Non-3GPP Device Identifier is not associated with the UE | LG Electronics | Rel-19 | Noted in e-mail session | Ashok (Samsung) comments that CR is not ok with existing NOTE Srinivas (Nokia) comments on Note Myungjune (LGE) responses to Ashok (Samsung) and Srinivas (Nokia) Yildirim (Charter) comments and agrees with the comment noting the CR. ==== General Revisions Deadline ==== Myungjune (LGE) is ok to NOTE CR. ==== Comments Deadline ==== | Noted |
| 19.8.2 | S2-2500349 | CR | Approval | 23.503 CR1467 (Rel-19, 'F'): PCC enhancements for support of identified non-3GPP devices | China Mobile | Rel-19 | Approved | Agreed | |
| 19.8.2 | S2-2500554 | CR | Approval | 23.503 CR1480 (Rel-19, 'F'): PCC enhancements for support of identified non-3GPP devices | Huawei, HiSilicon | Rel-19 | r04 agreed. Revised in e-mail session to S2-2501229. | Srinivas (Nokia) provides comments Pavan (Google) provides r01 Magnus (Ericsson) provides r02 Srinivas (Nokia) provides comments on r02 Jianning (Xiaomi) provides comments Mike (InterDigital) comments and provides r03 so that we can still progress how to deal with the case where the non-3GPP device information is removed from the UDR. Marco (Huawei) expected that we discussed 503 before discussing 502 but we are working other way around. I withdraw the contribution and see 502 discussion. A 503 CR may be create for Athens, if needed. Marco (Huawei) is OK with R03 with limited scope. I undo my proposal to withdraw the contribution ?? Yishan (Huawei) provides r04 to add China Telecom as co-signing company. ==== General Revisions Deadline ==== Rahil (CableLabs) accepts r04 only ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501229 | CR | Approval | 23.503 CR1480R1 (Rel-19, 'F'): PCC enhancements for support of identified non-3GPP devices | Huawei, HiSilicon, China Telecom | Rel-19 | Revision of S2-2500554r04. Approved | Agreed | |
| 19.8.2 | S2-2501044 | CR | Approval | 23.503 CR1503 (Rel-19, 'F'): Corrections to PCR trigger and SM policy modification for Non-3GPP device identifier | Samsung | Rel-19 | Check Affected Clauses! r01 agreed. Revised in e-mail session to S2-2501230. | Srinivas (Nokia) asks for clarification on the CR and provides comments Naman (Samsung) replies and provides r01 Myungjune (LGE) asks question for clarification. ==== General Revisions Deadline ==== Marco (Huawei) OK for R01 Srinivas (Nokia) Ok with r01, but only with removal of changes in 6.2.1.2 Yildirim (Charter) is ok with r01 but the changes in clause 6.1.3.1 clashes with S2-2500242 that can be removed. Naman (Samsung) is ok with r01 + removal of changes in 6.2.1.2 as suggested by Nokia Mike (InterDigital) suggests to AGREE 'r01 + removal the changes in 6.2.1.2'. Rahil (CableLabs) believes this CR is dependent on S2-2400242 - if 242 gets agreed, r01 with the second change (to clause 6.1.3.31) removed is ok; if 242 does not agreed, r01 is ok. Mike (InterDigital) comments that it is clear that 0242 will not progress at this meeting. So it is ok to AGREE 'r01 + removal the changes in 6.2.1.2'. Yildirim (Charter) ok with the compromise proposal from Mike (InterDigital) ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501230 | CR | Approval | 23.503 CR1503R1 (Rel-19, 'F'): Corrections to PCR trigger and SM policy modification for Non-3GPP device identifier | Samsung | Rel-19 | Revision of S2-2501044r01. Approved | Agreed | |
| 19.8.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
| 19.8.2 | S2-2500533 | CR | Approval | 23.502 CR5252 (Rel-19, 'F'): Clarification on Provisioning of Non-3GPP Device Identifier(s) Information | LG Electronics | Rel-19 | Noted in e-mail session | Srinivas (Nokia) comments and provides r01 Magnus (Ericsson) don't agree with r00 and r01 Myungjune (LGE) provides r02 and responses to Srinivas (Nokia). Susan (Huawei) replies to Myungjune (LGE) and cannot agree to remove DNN/S-NSSAI. Myungjune (LGE) responses to Susan (Huawei). Susan (Huawei) responses to Myungjune (LGE). Naman (Samsung) provides comments Yaxin (OPPO) provides comments on DNN/S-NSSAI info. Myungjune (LGE) replies. Srinivas (Nokia) comments and responds to Myungjune Myungjune (LGE) response to Srinivas (Nokia). Srinivas (Nokia) replies to Myungjune ==== General Revisions Deadline ==== Myungjune (LGE) proposes to NOTE CR. Srinivas (Nokia) as concurred below, the CR is asked to be NOTED. ==== Comments Deadline ==== | Noted |
| 19.8.2 | S2-2500807 | CR | Approval | 23.502 CR5287 (Rel-19, 'F'): Modification to the SM Policy Association Modification procedure | ZTE | Rel-19 | Merged into S2-2501219 | Zhendong (ZTE) provides r01. ==== General Revisions Deadline ==== Naman (Samsung) considers this as merged to 1043 ==== Comments Deadline ==== Mike (InterDigital) proposes to mark this as MERGED with 1043. | Merged |
| 19.8.2 | - | - | - | SMF Selection | - | - | Docs:=1 | - | |
| 19.8.2 | S2-2500558 | CR | Approval | 23.501 CR5976 (Rel-19, 'F'): Support of SMF selection considering the Non-3GPP Device Identifier | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Kenny (Qualcomm) provides comments. Myungjune (LGE) provides comments. Srinivas (Nokia) provides comments Mike (InterDigital) comments Susan (Huawei) replies and provides r01 Ashok (Samsung) comments on r01 Myungjune (LGE) provides comments on r01. Srinivas (Nokia) asks for clarification based on the exception sheet which was not approved by plenary Susan (Huawei) replies to Ashok (Samsung) and Myungjune (LGE), and provides r02. Iskren (NEC) comments ==== General Revisions Deadline ==== Susan (Huawei) replies to Srinivas (Nokia). Susan (Huawei) replies to Myungjune (LGE). Srinivas (Nokia) comments on the clarification provided by Susan Susan (Huawei) replies to Kenny (Qualcomm). Kenny (Qualcomm) proposes to note the CR. Srinivas (Nokia) asks to Note this paper, considering the reasoning shared in the email chain. Myungjune (LGE) replies to Susan (Huawei) Iskren (NEC) proposes to agree r02 Zhendong (ZTE) proposes to postpone . Susan (Huawei) replies to Srinivas (Nokia) and asks questions for clarification. Susan (Huawei) replies to Zhendong (ZTE). Srinivas (Nokia) tries to clarify to Susan Rahil (CableLabs) proposes to Note this CR Susan (Huawei) replies to Rahil (CableLabs) and asks for his technical comments to postpone this 23.501 CR. ==== Comments Deadline ==== Srinivas (Nokia) replies to Susan | Noted |
| 19.8.2 | - | - | - | Clarifications on AF Provisioning | - | - | Docs:=3 | - | |
| 19.8.2 | S2-2500803 | CR | Approval | 23.501 CR6005 (Rel-19, 'F'): Clarification on AF provisioning | ZTE | Rel-19 | Approved | Agreed | |
| 19.8.2 | S2-2500805 | CR | Approval | 23.502 CR5286 (Rel-19, 'F'): Clarification on the AF provisioning procedure | ZTE | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501231. | Mike (InterDigital) comments and provides r01 Myungjune (LGE) provides r02. Zhendong (ZTE) provides response to r02. Magnus (Ericsson) provides comments Marco (Huawei) provides comments to r02 Myungjune (LGE) provides comments. Zhendong (ZTE) provides response to Ericsson. Zhendong (ZTE) provides response to Myungjune . Marco (Huawei) a revision 02 is needed. Zhendong (ZTE) provides response to Marco. Myungjune (LGE) is ok with r01 but some changes are needed. Marco (Huawei) answer to Zhendong (ZTE) Naman (Samsung) provides comments Zhendong (ZTE) provides response to Samsung. Zhendong (ZTE) provides r03. ==== General Revisions Deadline ==== Naman (Samsung) : r03 looks good ==== Comments Deadline ==== | Revised |
| 19.8.2 | S2-2501231 | CR | Approval | 23.502 CR5286R1 (Rel-19, 'F'): Clarification on the AF provisioning procedure | ZTE | Rel-19 | Revision of S2-2500805r03. Approved | Agreed | |
| 19.8.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=19 | - | |
| 19.8.2 | S2-2500448 | CR | Approval | 23.501 CR5954 (Rel-19, 'F'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia, Apple | Rel-19 | Not Handled | Dieter (Deutsche Telekom) thanks for this CR, supports the changes and would like to co-sign. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | - |
| 19.8.2 | S2-2500449 | CR | Approval | 23.502 CR5242 (Rel-19, 'F'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500451 | CR | Approval | 23.503 CR1476 (Rel-19, 'D'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500453 | CR | Approval | 23.502 CR5243 (Rel-19, 'F'): Handling of the scenerio where a non-3GPP device no longer requires QoS Differentiation | InterDigital Inc, Qualcomm, ETRI | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500454 | CR | Approval | 23.503 CR1477 (Rel-19, 'F'): Handling of the scenerio where a non-3GPP device no longer requires QoS Differentiation | InterDigital Inc., Qualcomm, ETRI | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500452 | CR | Approval | 23.501 CR5955 (Rel-19, 'F'): Resolving the Editorial Note on PDU Session Establishment | InterDigital Inc., Nokia | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500709 | CR | Approval | 23.502 CR5275 (Rel-19, 'F'): Support of SMF selection for Non-3GPP Device Identifer | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500557 | CR | Approval | 23.316 CR2146 (Rel-19, 'F'): Identifying non-3GPP devices behind 5G-RG | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500552 | CR | Approval | 23.316 CR2145 (Rel-19, 'F'): Identifying non-3GPP devices behind 5G-RG and NAUN3 devices | Huawei, Hisilicon | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500534 | CR | Approval | 23.502 CR5253 (Rel-19, 'F'): Clarification on Non-3GPP Device Connection Information reporting procedures | LG Electronics | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500529 | CR | Approval | 23.316 CR2144 (Rel-19, 'F'): Clarification on Non-3GPP Device Identifier reporting procedure | LG Electronics | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500531 | CR | Approval | 23.501 CR5971 (Rel-19, 'F'): Clarification on user plane address reporting associated with Non-3GPP Device Identifier | LG Electronics | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500808 | CR | Approval | 23.503 CR1491 (Rel-19, 'F'): Clarification on Policy control for non-3GPP devices connecting behind a UE | ZTE | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500809 | CR | Approval | 23.316 CR2149 (Rel-19, 'F'): Resolve the EN and correct the figure and options description | ZTE | Rel-19 | Check Affected Clauses! Not Handled | - | |
| 19.8.2 | S2-2501024 | CR | Approval | 23.501 CR6055 (Rel-19, 'F'): Max no of non-3GPP device identifier | Xiaomi | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2501023 | CR | Approval | 23.501 CR6054 (Rel-19, 'F'): Clarification for non-3GPP connection information | Xiaomi | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500214 | CR | Approval | 23.502 CR5211 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc. | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500241 | CR | Approval | 23.502 CR5219 (Rel-19, 'F'): Moving note from table to clause | Ericsson, AT&T | Rel-19 | Not Handled | - | |
| 19.8.2 | S2-2500845 | CR | Approval | 23.502 CR5080R2 (Rel-19, 'F'): PDU session management for identified non-3GPP Devices behind the UE | CATT | Rel-19 | Revision of S2-2411507 Not Handled | - | |
| 19.9.1 | - | - | - | Study on Enhancement of support for Edge Computing in 5G Core network — Phase 3 (FS_eEDGE_5GC_Ph3) | - | - | Docs:=0 | - | |
| 19.9.2 | - | - | - | Enhancement of support for Edge Computing in 5G Core network — Phase 3 (eEDGE_5GC_Ph3) | - | - | Docs:=66 | - | |
| 19.9.2 | - | - | - | KI#1: Offloading from central SMF | - | - | Docs:=0 | - | |
| 19.9.2 | - | - | - | AF Influence to I-SMF or not - Discussion papers | - | - | Docs:=1 | - | |
| 19.9.2 | S2-2500610 | DISCUSSION | Approval | KI#1: Further clarification on Local offloading traffic handling at I-SMF . | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 19.9.2 | - | - | - | EN on AF Influence to I-SMF or not - CRs | - | - | Docs:=10 | - | |
| 19.9.2 | S2-2500685 | CR | Approval | 23.548 CR0294 (Rel-19, 'F'): KI#1: Further clarification on Local offloading traffic handling at I-SMF | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Changhong (OPPO) proposes to use this paper as baseline to resolve the EN on AFTI transferred to I-SMF. Haiyang (Huawei) provides r01 as Changhong (OPPO) proposed. Please also tell me the option you prefer. Huazhang (China Mobile) prefers the I-SMF generates N4 rules directly... Tezcan (Nokia) provides comments and proposes a way forward on AF TI. Changhong (OPPO) proposes to use S2-2501063 as baseline not this paper to resolve the EN on AFTI to I-SMF. Haiyang (Huawei) provides r02, removing AF TI part. ==== General Revisions Deadline ==== Tezcan (Nokia) objects to r00, r01, r02 and proposes to Note this paper. Haiyang (Huawei) comments. Tezcan (Nokia) responds to Haiyang (Huawei). ==== Comments Deadline ==== | Noted |
| 19.9.2 | S2-2500488 | CR | Approval | 23.548 CR0280 (Rel-19, 'F'): KI#1 Remove EN on AF traffic influence information for I-SMF | Samsung | Rel-19 | Merge into S2-2500685? Proposed merged with S2-2500685 (noted). Noted | Fenqin (Huawei) clarify the below comment is to S2-2500882 Fenqin (Huawei) provides comment Changhong (OPPO) proposes to merge it into S2-2500685 and S2-2500882. Changhong (OPPO) proposes to use S2-2501063 as baseline for 23.548 to resolve the EN on AFTI to I-SMF. Hyesung (Samsung) is ok with the merge suggested by Changhong. Tezcan (Nokia) provides comments similar to 0489 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.9.2 | S2-2501063 | CR | Approval | 23.548 CR0298 (Rel-19, 'F'): Removal of Editor s Note on AF traffic influence | Nokia | Rel-19 | 6.10.3.1. Merge into S2-2500685? r01 agreedrevised in e-mail session to S2-2501115, merging S2-2500319 | Changhong (OPPO) proposes to merge it into S2-2500685. Changhong (OPPO) proposes to use this paper as the baseline for 23.548 CR to resolve the EN on AFTI to I-SMF. Tezcan (Nokia) provides r01 that merges on 6.10.3.1 ==== General Revisions Deadline ==== Hyesung (Samsung) suggests to go with r01, and please add Samsung as a co-source. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501115 | CR | Approval | 23.548 CR0298R1 (Rel-19, 'F'): Removal of Editor s Note on AF traffic influence | Nokia, Samsung, ZTE, CMCC | Rel-19 | Revision of S2-2501063r01, merging S2-2500319. Approved | Agreed | |
| 19.9.2 | S2-2500319 | CR | Approval | 23.548 CR0279 (Rel-19, 'F'): Correction on local offloading management | China Mobile | Rel-19 | Merge 6.10.1 and 6.10.3.1 into S2-2500256 and 6.10.2.2 into S2-2500685? Merged into S2-2501115 | Changhong (OPPO) proposes to merge it into S2-2500685 and S2-2500256. Dan (China Mobile) OK to merge. Changhong (OPPO) proposes to use S2-2501063 as baseline for 23.548 CR to resolve the EN on AFTI to I-SMF. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2500882 | CR | Approval | 23.548 CR0295 (Rel-19, 'F'): Resolve EN for policy provisioing for Local offloading management | ZTE | Rel-19 | Postponed in e-mail session | Fenqin (Huawei) provides comment Changhong (OPPO) proposes to use this paper as baseline for changes to clause 6.10.3.2. Jinguo(ZTE) provides r01 and response to Fenqin (Huawei) Tezcan (Nokia) agrees with Jinguo and provides further comments. Jinguo(ZTE) provides r02 Fenqin (Huawei) provides r03 Jinguo(ZTE) response to Fenqin (Huawei) Fenqin (Huawei) provides r04 Tezcan (Nokia) provides comments Jinguo(ZTE) provides r05 ==== General Revisions Deadline ==== Fenqin (Huawei) suggest to postpone this paper Jinguo(ZTE) response to Fenqin(Huawei) Tezcan (Nokia) prefers to postpone. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2500489 | CR | Approval | 23.502 CR5248 (Rel-19, 'F'): KI#1 AF traffic influence information for I-SMF | Samsung | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to use this paper as baseline for changes to clause 5.2.8.2.2. Hyesung (Samsung) agrees to merge clause 4.23.6.2 into S2-2500684 and provides r01. Changhong (OPPO) proposes to use S2-2501064 as baseline CR for 23.502 not this paper to resolve the EN on AFTI to I-SMF. Hyesung (Samsung) proposes to keep this CR as baseline for clause 5.2.8.2.2 while ok to merge other parts into S2-2501064. Tezcan (Nokia) provides comments and asks further clarifications Tezcan (Nokia) is OK to keep this CR on notification related parts and provides comments Hyesung (Samsung) replies ? ==== General Revisions Deadline ==== Tezcan (Nokia) suggests to postpone this CR ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2500684 | CR | Approval | 23.502 CR5272 (Rel-19, 'F'): KI#1: Further clarification on Local offloading traffic handling at I-SMF | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Hyesung (Samsung) provides comments. Changhong (OPPO) proposes to use it as baseline for changes to clause 4.23.6.2 and 5.2.8.2.3. Haiyang (Huawei) responses to Hyesung (Samsung). Tezcan (Nokia) provides comments and asks for clarification. Changhong (OPPO) proposes to use S2-2501064 as baseline not this paper to resolve the EN on AFTI to I-SMF for 23.502 CRs. Haiyang (Huawei) provides r01 to remove AFTI part. Tezcan (Nokia) provides comments. Haiyang (Huawei) provides r03. ==== General Revisions Deadline ==== Tezcan (Nokia) objects to r00-r03 and proposes to Note this paper. Hyesung (Samsung) proposes to postpone this and needs further discussion on the need of SDF transfer. ==== Comments Deadline ==== Fenqin (Huawei) give a feedback to Hyesung(Samsung). | Postponed |
| 19.9.2 | S2-2501064 | CR | Approval | 23.502 CR5332 (Rel-19, 'F'): Update on interaction between I-SMF and SMF to include delay-related AF requests | Nokia | Rel-19 | Merge changes to 4.23.6.2 and 5.2.8.2.3 into S2-2500684, and changes to 5.2.8.2.2 into S2-2500489? r00 agreedrevised in e-mail session to S2-2501116. | Changhong (OPPO) proposes to merge it into S2-2500684 and S2-2500489. Changhong (OPPO) proposes to use this paper as baseline for 23.502 CR to resolve the EN on AFTI to I-SMF. Fenqin (Huawei) proposes r01. Tezcan (Nokia) provides comments on r01 ==== General Revisions Deadline ==== Fenqin (Huawei) prefer r01 and can live with r00. Hyesung (Samsung) prefers r00, but can live with r01. Please add Samsung as co-source. Tezcan (Nokia) prefers r00, can live with r01. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501116 | CR | Approval | 23.502 CR5332R1 (Rel-19, 'F'): Update on interaction between I-SMF and SMF to include delay-related AF requests | Nokia, Samsung | Rel-19 | Revision of S2-2501064. Approved | Agreed | |
| 19.9.2 | - | - | - | EN on Local Offloading Policy handling at SMF | - | - | Docs:=5 | - | |
| 19.9.2 | S2-2500662 | CR | Approval | 23.502 CR5267 (Rel-19, 'F'): Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | Baseline r01 agreedrevised in e-mail session to S2-2501124, merging S2-2500492 | Changhong (OPPO) provides r01. ==== General Revisions Deadline ==== Hyesung (Samsung) is ok with r01. Please add Samsung as a co-source. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501124 | CR | Approval | 23.502 CR5267R1 (Rel-19, 'F'): Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | Revision of S2-2500662r01, merging S2-2500492. Approved | Agreed | |
| 19.9.2 | S2-2500492 | CR | Approval | 23.502 CR5249 (Rel-19, 'F'): Remove EN on Local Offloading Policy update | Samsung | Rel-19 | Not aligned with agreement vs 23.501 at SA2#166. Merge into S2-2500662? Merged into S2-2501124 | Changhong (OPPO) proposes to merge it into S2-2500662. Hyesung (Samsung) confirms that it is merged into S2-2500662 as per suggestion. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2500663 | CR | Approval | 23.548 CR0289 (Rel-19, 'F'): KI#1: Clarification on Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | r02 agreedrevised in e-mail session to S2-2501117. | Hyesung (Samsung) provides comments. Fenqin (Huawei) provides comments. Changhong (OPPO) replies to comments. Tezcan (Nokia) provides comments. Huazhang (CMCC) provides r01 Changhong (OPPO) replies to Huazhang. Changhong (OPPO) provides r02. Huazhang (CMCC) provides r03 based on r02 to add a note to clarify Changhong (OPPO) comments on r03. Huazhang (CMCC) provide r04 to clarify. ==== General Revisions Deadline ==== Tezcan (Nokia) is OK with r02 or r00, cannot accept r01, r03, r04. ==== Comments Deadline ==== Huazhang (CMCC) is OK this wayforward that we can add such note in next meeting to further clarify this. | Revised |
| 19.9.2 | S2-2501117 | CR | Approval | 23.548 CR0289R1 (Rel-19, 'F'): KI#1: Clarification on Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | Revision of S2-2500663r02. Approved | Agreed | |
| 19.9.2 | - | - | - | I-SMF change for LOM | - | - | Docs:=8 | - | |
| 19.9.2 | S2-2500611 | CR | Approval | 23.548 CR0288 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to revise this paper and S2-2501062 separately on technical improvement. Tezcan (Nokia) provides comments and asks further clarifications. Fenqin (Huawei) responds to Tezcan(Nokia). Tezcan (Nokia) responds to Fenqin (Huawei). Fenqin (Huawei) responds to Tezcan(Nokia) again. ==== General Revisions Deadline ==== Tezcan (Nokia) proposes to postpone this paper. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2501062 | CR | Approval | 23.548 CR0297 (Rel-19, 'F'): Clarification on SMF triggered I-SMF insertion or removal for Local Offloading Management | Nokia | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to revise this paper and S2-2500611 separately on technical improvement. Fenqin (Huawei) provides comment. Tezcan (Nokia) replies to Fenqin. Tezcan (Nokia) responds to Fenqin (Huawei). Fenqin (Huawei) replies to Tezcan Fenqin (Huawei) suggest to postpone this paper. ==== General Revisions Deadline ==== Tezcan (Nokia) is OK to postpone. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2500612 | CR | Approval | 23.501 CR5981 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to revise this paper and S2-2501062 separately on technical improvement. Tezcan (Nokia) provides comments and asks for further clarification. Fenqin (Huawei) provides feedback. ==== General Revisions Deadline ==== Tezcan (Nokia) proposes to note this CR. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2500613 | CR | Approval | 23.502 CR5265 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to revise this paper and S2-2501062 separately on technical improvement. Tezcan (Nokia) provides comments similar to 0611. ==== General Revisions Deadline ==== Tezcan (Nokia) proposes to postpone this paper. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2501056 | CR | Approval | 23.501 CR6058 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia | Rel-19 | Baseline for changes to clause 5.34.3. r01 agreedrevised in e-mail session to S2-2501118. | Changhong (OPPO) proposes to only focus on changes to clause 5.34.1 in this paper. Tezcan (Nokia) asks clarifications on Changhong request. Changhong (OPPO) replies to Tezcan and proposes to use this paper as baseline for clause 5.34.3. Magnus (Ericsson) provides r01 with including merge of clause 5.34.3 from 0254 Tezcan (Nokia) provides comments Fenqin (Huawei) provides comments Tezcan (Nokia) responds to Fenqin (Huawei) and is fine with r01 ==== General Revisions Deadline ==== Hyesung (Samsung) is fine with r01. Please add Samsung as co-source. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501118 | CR | Approval | 23.501 CR6058R1 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia, Ericsson, Samsung | Rel-19 | Revision of S2-2501056r01. Approved | Agreed | |
| 19.9.2 | S2-2501055 | CR | Approval | 23.502 CR5328 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia | Rel-19 | r02 agreedrevised in e-mail session to S2-2501119. | Fenqin (Huawei) provides comments. Tezcan (Nokia) responds Fenqin and provides r01. Fenqin (Huawei) provide R02 . Tezcan (Nokia) provides comments on r02 Fenqin (Huawei) provide feedback. ==== General Revisions Deadline ==== Fenqin (Huawei) for simplicity, let go with r02 and object r00/r01. Tezcan (Nokia) is OK with r02 ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501119 | CR | Approval | 23.502 CR5328R1 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia | Rel-19 | Revision of S2-2501055r02. Approved | Agreed | |
| 19.9.2 | - | - | - | UE Mobility for PDU Session supporting LOM | - | - | Docs:=10 | - | |
| 19.9.2 | S2-2500682 | CR | Approval | 23.502 CR5271 (Rel-19, 'F'): KI#1: UE mobility for PDU session supporting local offloading management | Huawei, HiSilicon | Rel-19 | Baseline for changes to clause 5.2.2.2.2. r04 agreedrevised in e-mail session to S2-2501120. | Hyesung (Samsung) asks to add Samsung as a co-source. Changhong (OPPO) proposes to use it as baseline for changes to clause 5.2.2.2.2. Tezcan (Nokia) provides comments. Tezcan (Nokia) provides comments to r01. Haiyang (Huawei) provides r01. Hongsuk (LGE) provides comments. Haiyang (Huawei) provides r02. Hongsuk (LGE) agrees to use similar wording and asks for further clarification. Tezcan (Nokia) provides r03 including Nokia as a co-source. Hongsuk (LGE) provides r04 including LGE as a co-source. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501120 | CR | Approval | 23.502 CR5271R1 (Rel-19, 'F'): KI#1: UE mobility for PDU session supporting local offloading management | Huawei, HiSilicon, Samsung, Nokia, LGE | Rel-19 | Revision of S2-2500682r04. Approved | Agreed | |
| 19.9.2 | S2-2501061 | CR | Approval | 23.548 CR0296 (Rel-19, 'F'): Corrections on the procedures defined for local offloading management | Nokia | Rel-19 | Baseline for changes to clause 6.10.2.4. r05 agreedrevised in e-mail session to S2-2501121, merging S2-2500278, S2-2500539 and S2-2500683 | Changhong (OPPO) proposes to use it as the baseline for changes to clause 6.10.1 and 6.10.2.4. Hongsuk(LGE) provides r01, to merge 0539(clause 6.10.2.4) into this paper. Tezcan (Nokia) provides r02 to merge 0539, 0683 and 0278 on clause 6.10.2.4 Haiyang (Huawei) provides r03. Hongsuk(LGE) provides r04, adding LGE as co-signer with minor editorial. Jinguo(ZTE) comments Haiyang (Huawei) is OK with r05. Tezcan (Nokia) provides r05 and responds to Jinguo (ZTE) Hongsuk (LGE) is OK with r05. ==== General Revisions Deadline ==== Jinguo(ZTE) is ok with r05 for this meeting and provide comment. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501121 | CR | Approval | 23.548 CR0296R1 (Rel-19, 'F'): Corrections on the procedures defined for local offloading management | Nokia, Huawei, LGE | Rel-19 | Revision of S2-2501061r05, merging S2-2500278, S2-2500539 and S2-2500683. Approved | Agreed | |
| 19.9.2 | S2-2500683 | CR | Approval | 23.548 CR0293 (Rel-19, 'F'): KI#1: UE mobility for PDU session supporting local offloading management | Huawei, HiSilicon | Rel-19 | Merge into S2-2501061? Merged into S2-2501121 | Changhong (OPPO) proposes to merge it into S2-2501061. ==== General Revisions Deadline ==== Haiyang (Huawei) confirms to merge it into S2-2501061. ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2500278 | CR | Approval | 23.548 CR0278 (Rel-19, 'F'): Correction of UE mobility for PDU session supporting Local Offloading Management | China Mobile | Rel-19 | Merge into S2-2501061? Merged into S2-2501121 | Changhong (OPPO) proposes to merge it into S2-2501061. Huazhang (cmcc) confirms this paper to merge it into S2-2501061. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2500539 | CR | Approval | 23.548 CR0287 (Rel-19, 'F'): Clarification and correction on the LOM Service Area | LG Electronics | Rel-19 | Confirm Spec version used - CR states {19.2.0}! Changes to clause 6.10.2.4 merged into S2-2501061? Changes to clause 6.10.1 on config. LOM service area in AMF should follow decision in S2-2500881. Confirm Spec version used - CR states {19.2.0}! Merged into S2-2501121 | Changhong (OPPO) proposes to merge it into S2-2501061 and S2-2500663. Hongsuk (LGE) confirms Rapporteur guidance to merge into S2-2501061 and S2-2500663. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2500256 | CR | Approval | 23.548 CR0274 (Rel-19, 'F'): Correcting and improving text for KI#1 | Ericsson | Rel-19 | Baseline for changes to clause 6.10.2.2. CC#4: r05 + changes agreed. Revised in CC#4 to S2-2501351, merging S2-2500493 | Changhong (OPPO) proposes to use it as baseline for changes to clause 6.10.2.2 and changes to clause 6.10.2.1, 6.10.2.3 and 6.7.2.2 can remain in this paper. Fenqin (Huawei) provide comment. Huazhang (China Mobile) ask questions Hyesung (Samsung) provide comment. Magnus (Ericsson) provides r01 Tezcan (Nokia) provides comments and asks for clarification. Jinguo(ZTE) asks clarification Magnus (Ericsson) provides comments Hongsuk (LGE) provides comments and asks for clarification. Tezcan (Nokia) responds to Magnus (Ericsson) Fenqin(Huawei) provides r02. Magnus (Ericsson) provides r03 Tezcan (Nokia) provides r04 Hyesung (Samsung) provides r05 ==== General Revisions Deadline ==== Hyesung (Samsung) suggests to go with r05. r00~r04 are not fine. Jinguo(ZTE) is ok with r05 and ask to cosign. Magnus (Ericsson) are OK with r05 Tezcan (Nokia) is OK with r05 and r04. Fenqin (Huawei) suggest to go with r05+ following two changes; 1) Local Offloading Management support allowed is changed to Local Offloading Management supported--- 2 place, i.e. undo the change. 2) The AMF may also have the Local Offloading Management service area configured. If the UE is within such an area, the AMF selects an I-SMF supporting Local Offloading Management and the SMF service area, and step 2 is executed. If the UE is not in the Local Offloading Management service area, step 2a is executed.. ==== Comments Deadline ==== Fenqin (Huawei) suggest to go with r05+ following two changes; 1) Local Offloading Management support allowed is changed to Local Offloading Management supported--- 2 place, i.e. undo the change. 2) The AMF may also have the Local Offloading Management service area configured. If the UE is within such an area, the AMF selects an I-SMF supporting Local Offloading Management and the SMF service area, and step 2 is executed. If the UE is not in the Local Offloading Management service area, step 2a is executed.. Fenqin (Huawei) suggest to go with r05+ following two changes; 1) Local Offloading Management support allowed is changed to Local Offloading Management supported--- 2 place, i.e. undo the change. 2) The AMF may also have the Local Offloading Management service area configured. If the UE is within such an area, the AMF selects an I-SMF supporting Local Offloading Management and the SMF service area, and step 2 is executed. If the UE is not in the Local Offloading Management service area, step 2a is executed.. | Revised |
| 19.9.2 | S2-2501351 | CR | Approval | 23.548 CR0274R1 (Rel-19, 'F'): Correcting and improving text for KI#1 | Ericsson | Rel-19 | Revision of S2-2500256r05 + changes, merging S2-2500493. This CR was agreed | Agreed | |
| 19.9.2 | S2-2500493 | CR | Approval | 23.548 CR0282 (Rel-19, 'F'): KI#1 Update PDU Session Establishment for Local Offloading Management | Samsung | Rel-19 | Merge into S2-2500256? Merged into S2-2501351 | Changhong (OPPO) proposes to merge it into S2-2500256. ==== General Revisions Deadline ==== Hyesung (Samsung) confirms that this CR is merged into S2-2500256. ==== Comments Deadline ==== | Merged |
| 19.9.2 | - | - | - | Local Offload Management service area configuration in AMF | - | - | Docs:=2 | - | |
| 19.9.2 | S2-2500881 | CR | Approval | 23.501 CR6026 (Rel-19, 'F'): Clarification on the local offloading management service area | ZTE | Rel-19 | To be decided whether AMF is configured with LOM service area or not. r01 agreedrevised in e-mail session to S2-2501122. | Changhong (OPPO) proposes to determine whether AMF is configured with LOM service area or not in this thread. Jinguo(ZTE) asks question for clarification Magnus (Ericsson) provides comments Hongsuk (LGE) comments Hyesung (Samsung) comments Jinguo(ZTE) response to Tezcan and Magnus Tezcan (Nokia) provides comments Jinguo(ZTE) provides r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501122 | CR | Approval | 23.501 CR6026R1 (Rel-19, 'F'): Clarification on the local offloading management service area | ZTE | Rel-19 | Revision of S2-2500881r01. Approved | Agreed | |
| 19.9.2 | - | - | - | I-SMF profile | - | - | Docs:=7 | - | |
| 19.9.2 | S2-2500255 | CR | Approval | 23.502 CR5221 (Rel-19, 'F'): Adding missing impacts for KI#1 | Ericsson | Rel-19 | Baseline for LOM service area. Merged into S2-2501350 | Changhong (OPPO) proposes to merge it into S2-2501057. Magnus (Ericsson) don't accept merge. We need to select either 1057 or 0255. We propose 0255 Changhong (OPPO) comments. ==== General Revisions Deadline ==== Magnus (Ericsson ) this is considered merged in1057r01 ==== Comments Deadline ==== | Merged |
| 19.9.2 | S2-2501057 | CR | Approval | 23.502 CR5329 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia | Rel-19 | Merge into S2-2501057? CC#4: r01 + changes agreed. Revised in CC#4 to S2-2501350, merging S2-2500255 | Changhong (OPPO) proposes to use it as baseline for changes to clause 5.2.7.2.2 and 5.2.7.3.2 on LOM service area.. Hyesung (Samsung) provides comments. Hongsuk (LGE) provides comments. Fenqin (Huawei) provides comments. Huazhang (China Mobile) ask question about the relationship between SMF service are, local offload area and UE location... Tezcan (Nokia) responds to the comments Jinguo(ZTE) provide comments Magnus (Ericsson) provides comments Tezcan (Nokia) responds to Jinguo (ZTE) and Magnus (Ericsson). Jinguo(ZTE) response Tezcan (Nokia) provides r01 to merge 0255. ==== General Revisions Deadline ==== Magnus (Ericsson) objects to r00 ask to co-sign r01 as it merges the intent of 0255 Fenqin (Huawei) suggest to go with r01 with the change remove 'the list of' in the 1st change Tezcan (Nokia) is OK with Fenqin (Huawei) suggestion on r01 related change ==== Comments Deadline ==== Hyesung (Samsung) is OK r01 + the suggested change. Please add Samsung as co-source | Revised |
| 19.9.2 | S2-2501350 | CR | Approval | 23.502 CR5329R1 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia, Ericsson | Rel-19 | Revision of S2-2501057r01 + changes, merging S2-2500255. This CR was agreed | Agreed | |
| 19.9.2 | S2-2500277 | CR | Approval | 23.502 CR5229 (Rel-19, 'F'): I-SMF capability registration | China Mobile | Rel-19 | Merge changes to clause 5.2.8.2.2 and 5.2.8.2.3 into S2-2501059? No conflict with S2-2500255 wrt clause 5.2.7.2.2 and 5.2.7.3.2. Can be revised separately. r05 agreedrevised in e-mail session to S2-2501123. | Changhong (OPPO) proposes to use is as the baseline for changes to clause 5.2.7.2.2 and 5.2.7.3.2 on LOM Capability. Huazhang (China Mobile) provides r01 Tezcan (Nokia) provides comments to r01. Huazhang (CMCC) provides r02. Huazhang (CMCC) provide r04 based on r03, add Samsung cosign Hyesung (Samsung) asks to add Samsung as a co-source. Hongsuk (LGE) provides r03 adding LGE as co-signer. Huazhang (CMCC) provide r05, revise summary of change and add Nokia as cosign ==== General Revisions Deadline ==== Fenqin (Huawei) we are ok with r05. You can add Huawei as supporter. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501123 | CR | Approval | 23.502 CR5229R1 (Rel-19, 'F'): I-SMF capability registration | China Mobile, LGE, Samsung, Nokia, Huawei | Rel-19 | Revision of S2-2500277r05. Approved | Agreed | |
| 19.9.2 | S2-2501058 | CR | Approval | 23.501 CR6059 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia | Rel-19 | r01 agreedrevised in e-mail session to S2-2501125. | Fenqin (Huawei) proposes comments. Tezcan (Nokia) responded Fenqin (Huawei) as part of 1057 discussion. Fenqin (Huawei) provides r01. Tezcan (Nokia) provides r02 ==== General Revisions Deadline ==== Fenqin (Huawei) provides feedback Tezcan (Nokia) responds Fenqin (Huawei) and ask further clarification Fenqin (Huawei) responds Tezcan (Huawei)for further question Tezcan (Nokia) replies to Fenqin (Huawei) Fenqin (Huawei) suggest to go with r01 for this meeting. Tezcan (Nokia) is OK with r01 for this meeting. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501125 | CR | Approval | 23.501 CR6059R1 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia | Rel-19 | Revision of S2-2501058r01. Approved | Agreed | |
| 19.9.2 | - | - | - | Other correction - 23.501 CRs | - | - | Docs:=4 | - | |
| 19.9.2 | S2-2500254 | CR | Approval | 23.501 CR5909 (Rel-19, 'F'): Correction and improvements related to EDGE_Ph3 KI#1 | Ericsson | Rel-19 | Revise only for changes in 5.6.7.1. Changes in 5.34.3 to be merged into S2-2501056? r01 agreedrevised in e-mail session to S2-2501126. | Changhong (OPPO) proposes to only keep changes to clause 5.6.7.1 in this paper. Magnus (Ericsson) provides r01 without changes to clause 5.34.3 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501126 | CR | Approval | 23.501 CR5909R1 (Rel-19, 'F'): Correction and improvements related to EDGE_Ph3 KI#1 | Ericsson | Rel-19 | Revision of S2-2500254r01. Approved | Agreed | |
| 19.9.2 | S2-2500276 | CR | Approval | 23.501 CR5914 (Rel-19, 'F'): AMF functional description of supporting local offloading | China Mobile | Rel-19 | r03 agreedrevised in e-mail session to S2-2501127. | Tezcan (Nokia) responds to Huazhang (CMCC) and clarifies the previous comment. Huazhang (CMCC) reply to Tezcan (Nokia) Tezcan (Nokia) provides comments. Huazhang (CMCC) provides r01 Tezcan (Nokia) provides comments on r01 Huazhang (CMCC) is ok with r03 Hongsuk (LGE) provides r03 Huazhang (CMCC) provides r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501127 | CR | Approval | 23.501 CR5914R1 (Rel-19, 'F'): AMF functional description of supporting local offload | China Mobile, LGE | Rel-19 | Revision of S2-2500276r03. Approved | Agreed | |
| 19.9.2 | - | - | - | Other correction - 23.502 CRs | - | - | Docs:=3 | - | |
| 19.9.2 | S2-2501060 | CR | Approval | 23.502 CR5331 (Rel-19, 'F'): Clarification on handling of traffic not subject to Local Offloading Management | Nokia | Rel-19 | Approved | Changhong (OPPO) proposes to revise it separately from S2-2500277 and S2-2501059. Magnus (Ericsson) ask for clarification Tezcan (Nokia) responds to Magnus (Ericsson) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.9.2 | S2-2501059 | CR | Approval | 23.502 CR5330 (Rel-19, 'F'): Corrections related to Local Offloading Management allowed indication | Nokia | Rel-19 | Baseline for clause 5.2.8.2.2 . Other changes merged into S2-2500277 and S2-2500682. r01 agreedrevised in e-mail session to S2-2501128. | Changhong (OPPO) proposes to use this paper as baseline for changes to clause 5.2.8.2.2 and 5.2.8.2.3 by merging S2-2500277. . Tezcan (Nokia) provides r01 that merges 0277. Fenqin (Huawei) provides r02. Tezcan (Nokia) responds to Fenqin (Huawei) on r02 ==== General Revisions Deadline ==== Fenqin (Huawei) is ok with R01 ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501128 | CR | Approval | 23.502 CR5330R1 (Rel-19, 'F'): Corrections related to Local Offloading Management allowed indication | Nokia, CMCC | Rel-19 | Revision of S2-2501059r01. Approved | Agreed | |
| 19.9.2 | - | - | - | Other correction - 23.548 CRs | - | - | Docs:=2 | - | |
| 19.9.2 | S2-2500490 | CR | Approval | 23.548 CR0281 (Rel-19, 'F'): KI#1 Handling application not matched with LOM policy | Samsung | Rel-19 | Postponed in e-mail session | Changhong (OPPO) proposes to revise it separately from S2-2500256. Haiyang (Huawei) seeks for clarification. Hyesung (Samsung) replies. Haiyang (Huawei) seeks for further clarification. Tezcan (Nokia) asks clarifications Tezcan (Nokia) asks further clarification Hyesung (Samsung) replies and provide r01. Tezcan (Nokia) comments and asks the Rapporteur to guide us on how to handle 0490 and 0256 on clause 6.10.2.3 ==== General Revisions Deadline ==== Haiyang (Huawei) suggests to postpone the paper or further revise r01. ==== Comments Deadline ==== | Postponed |
| 19.9.2 | S2-2500664 | CR | Approval | 23.548 CR0290 (Rel-19, 'F'): KI#1 Clarification on EAS Discovery using IP replacement to support Local Offloading Management | OPPO | Rel-19 | Postponed in e-mail session | Tezcan (Nokia) proposes to consider related changes as part of 0256 (baseline for changes on 6.10.2.2). Changhong (OPPO) replies to Tezcan. Tezcan (Nokia) provides comments. Fenqin (Huawei) provides r01. ==== General Revisions Deadline ==== Tezcan (Nokia) proposes to postpone. ==== Comments Deadline ==== Changhong (OPPO) is OK to postpone. | Postponed |
| 19.9.2 | - | - | - | KI#2: Supporting N6 delay measurement | - | - | Docs:=0 | - | |
| 19.9.2 | - | - | - | I-SMF supporting N6 delay measurement CRs | - | - | Docs:=4 | - | |
| 19.9.2 | S2-2500495 | CR | Approval | 23.548 CR0284 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | r02 agreedrevised in e-mail session to S2-2501129. | Fenqin (Huawei) suggest to clarify how the information is transferred to I-SMF from SMF. Tezcan (Nokia) proposes a modification and asks further clarification. Hyesung (Samsung) replies. Jinguo(ZTE) comments Tezcan (Nokia) provides comments Tezcan (Nokia) provides comments. Hyesung (Samsung) provides r01, r02 and replies. Fenqin (Huawei) provides comments. Tezcan (Nokia) agrees with Fenqin (Huawei) ==== General Revisions Deadline ==== Hyesung (Samsung) is ok to go with r02. Tezcan (Nokia) is OK with r02 only. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501129 | CR | Approval | 23.548 CR0284R1 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | Revision of S2-2500495r02. Approved | Agreed | |
| 19.9.2 | S2-2500880 | CR | Approval | 23.501 CR6025 (Rel-19, 'F'): N6 delay measurement for I-SMF case | ZTE | Rel-19 | r03 agreedrevised in e-mail session to S2-2501130. | Haiyang (Huawei) comments. Fenqin (Huawei) ask one question. Jinguo(ZTE) provides response to Fenqin Jinguo(ZTE) provide r01 Fenqin (Huawei) response to Jinguo Jinguo(ZTE) response to Tezcan and Fenqin Tezcan (Nokia) asks further clarification Tezcan (Nokia) provides r02 Jinguo(ZTE) is ok with r02 Fenqin (Huawei) provides r03 Hyesung (Samsung) is ok with r02, please add Samsung as co-source in r02 Jinguo(ZTE) provides r03 add Samsung as cosigner. ==== General Revisions Deadline ==== Hyesung (Samsung) suggests to go with r02. Dario (Session Chair): please notice that ZTE's version was not uploaded and r03 refers to Huawei's. Tezcan (Nokia) prefers r02, can live with r03. Fenqin (Huawei) suggest to go with r03. Jinguo(ZTE) is fine with r03 provided by Huawei. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501130 | CR | Approval | 23.501 CR6025R1 (Rel-19, 'F'): N6 delay measurement for I-SMF case | ZTE, Nokia, Samsung | Rel-19 | Revision of S2-2500880r03. Approved | Agreed | |
| 19.9.2 | - | - | - | Other correction - 23.548 CRs | - | - | Docs:=4 | - | |
| 19.9.2 | S2-2500272 | CR | Approval | 23.548 CR0275 (Rel-19, 'F'): UPF (re)selection considering N6 delay for for EAS discovery with local DNS server or resolver | China Mobile | Rel-19 | Noted in e-mail session | Tezcan (Nokia) asks for further clarifications. Dan(China Mobile)reply. Dan(China Mobile)reply further Magnus (Ericsson) provides comments Dan (China Mobile) reply ==== General Revisions Deadline ==== Magnus (Ericsson) objects to this CR ==== Comments Deadline ==== | Noted |
| 19.9.2 | S2-2500494 | CR | Approval | 23.548 CR0283 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | r01 agreedrevised in e-mail session to S2-2501131. | Tezcan (Nokia) provides comments and proposes a modification. Hyesung (Samsung) accepts the suggestion and provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501131 | CR | Approval | 23.548 CR0283R1 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | Revision of S2-2500494r01. Approved | Agreed | |
| 19.9.2 | S2-2501066 | CR | Approval | 23.548 CR0299 (Rel-19, 'F'): Alignment on L-PSA UPF re-selection and/or an edge relocation | Nokia | Rel-19 | Approved | Haiyang (Huawei) comments. Tezcan (Nokia) replies to Haiyang (Huawei) as part of 1065 discussion. Tezcan (Nokia) responds as part of 1065 discussion ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.9.2 | - | - | - | Other correction - 23.501 CRs | - | - | Docs:=5 | - | |
| 19.9.2 | S2-2500491 | CR | Approval | 23.501 CR5964 (Rel-19, 'F'): KI#1 Remove EN on AF traffic influence information for I-SMF | Samsung | Rel-19 | r02 agreedrevised in e-mail session to S2-2501132. | Tezcan (Nokia) provides comments. Hyesung (Samsung) provides r01. Jinguo(ZTE) comments Magnus (Ericsson) provides comments Hyesung (Samsung) provides r02. ==== General Revisions Deadline ==== Tezcan (Nokia) is OK with r01 and r02, and ask to co-sign. ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501132 | CR | Approval | 23.501 CR5964R1 (Rel-19, 'F'): Update general description of support for edge computing | Samsung, Nokia | Rel-19 | Revision of S2-2500491r02. Approved | Agreed | |
| 19.9.2 | S2-2500877 | CR | Approval | 23.501 CR6024 (Rel-19, 'F'): N6 delay measurement triggered by SMF | ZTE | Rel-19 | Approved | Changhong (OPPO) proposes to revise it separately from S2-2501065. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.9.2 | S2-2501065 | CR | Approval | 23.501 CR6060 (Rel-19, 'F'): Alignment on L-PSA UPF re-selection and/or an edge relocation | Nokia | Rel-19 | CC#4: r02 + changes agreed. Revised in CC#4 to S2-2501349. | Haiyang (Huawei) comments. Tezcan (Nokia) responds to Haiyang (Huawei). Jinguo(ZTE) comments Magnus (Ericsson) disagrees with changes in clause 6.2.2 and 6.3.3.3 Tezcan (Nokia) responds to Magnus (Ericsson) to clarify the use of delay measurements Haiyang (Huawei) further comments. Tezcan (Nokia) provides r01 Magnus (Ericsson) provides comments Tezcan (Nokia) responds and provides r02. Haiyang (Huawei) is OK with r02. ==== General Revisions Deadline ==== Magnus (Ericsson) objects to r00,r01 and can only accept r02 with the following updates: Clause 5.13: * The word 'measurement' is removed * Note is replaced with the following: 'NOTE: Latencies between 5GC AN and UPF(s) can be configured. If QoS monitoring has previously been performed, the delays of such measurements can also be used Clause 6.2.2 * The word 'measurement' is removed Clause 6.3.3.3 * The word 'measurement' is removed * Note is replaced with the following: 'NOTE: Latencies between 5GC AN and UPF(s) can be configured. If QoS monitoring has previously been performed, the delays of such measurements can also be used Tezcan (Nokia) is OK with Magnus (Ericsson) suggestions on r02 ==== Comments Deadline ==== | Revised |
| 19.9.2 | S2-2501349 | CR | Approval | 23.501 CR6060R1 (Rel-19, 'F'): Alignment on L-PSA UPF re-selection and/or an edge relocation | Nokia, Ericsson | Rel-19 | Revision of S2-2501065r02 + changes. This CR was agreed | Agreed | |
| 19.9.2 | - | - | - | Other correction - 23.502 CRs | - | - | Docs:=1 | - | |
| 19.9.2 | S2-2500275 | CR | Approval | 23.502 CR5228 (Rel-19, 'F'): Update on UPF reporting N6 delay measurement | China Mobile | Rel-19 | Approved | Fenqin (Huawei) provides r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 19.10.1 | - | - | - | Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3) | - | - | Docs:=0 | - | |
| 19.10.2 | - | - | - | Phase 3 for UAS, UAV and UAM (UAS_Ph3) | - | - | Docs:=22 | - | |
| 19.10.2 | - | - | - | Incoming LS | - | - | Docs:=1 | - | |
| 19.10.2 | S2-2500072 | LS In | Information | LS from SA WG6: Reply LS on clarification related to the QoS and QoE parameters for the support of real time UAV flight path monitoring assistance. | SA WG6 (S6-245642) | Rel-19 | Noted in e-mail session | LaeYoung (LGE) proposes to NOTE this LS because no action is needed. Runze (Huawei) supports LaeYoung (LGE) to NOTE this LS. | Noted |
| 19.10.2 | - | - | - | KI#1: NEF enhancements | - | - | Docs:=18 | - | |
| 19.10.2 | S2-2500438 | CR | Approval | 23.256 CR0162 (Rel-19, 'F'): Addressing the EN on border-crossing point | Ericsson | Rel-19 | Postponed in e-mail session | Stefano (Qualcomm) suggest using as way forward. Runze (Huawei) comments. Shabnam (Ericsson) provides comments to Huawei Runze (Huawei) replies to Shabnam (Ericsson). Runze (Huawei) requests a revision based on the discussion. Shabnam (Ericsson) provides comments and indicates again addressing EN terminology replacement nothing technical change and don't intend to do so, as such can't provide any revision LaeYoung (LGE) shares same view with Shabnam (Ericsson). ==== General Revisions Deadline ==== Runze (Huawei) replies to LaeYoung (LGE) and Shabnam (Ericsson) and suggest more discussion. LaeYoung (LGE) would like to ask Runze (Huawei) regarding whether we can go with 00385. LaeYoung (LGE) got realized Runze (Huawei) already commented that using LGE CR is OK. ?? Shabnam (Ericsson) Runze, unfortunately your 'understanding is 'border-crossing zone' is part of the UAV flight path segment' is not specification defined, so I can't defend my paper against your understanding nor revise ==== Comments Deadline ==== | Postponed |
| 19.10.2 | S2-2500475 | CR | Approval | 23.256 CR0167 (Rel-19, 'F'): Service operation update | CATT | Rel-19 | 4.4.1.1.3.1, 4.4.1.1.3.4, 4.4.1.1.3.5, 4.4.1.1.4.1, 4.4.1.1.4.2 r01 agreed. Revised in e-mail session to S2-2501300. | Shabnam (Ericsson) provides detailed comments, will require revision Yunjing (CATT) replies to Shabnam (Ericsson) and provides r01. ==== General Revisions Deadline ==== Yunjing (CATT) suggests to go with r01 and will correct the spelling error in the approved version. Shabnam (Ericsson) provides comments that needs a minor update revision due to spelling error, ' periodict' to 'periodicity' ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501300 | CR | Approval | 23.256 CR0167R1 (Rel-19, 'F'): Service operation update | CATT | Rel-19 | Revision of S2-2500475r01. Approved | Agreed | |
| 19.10.2 | S2-2500829 | CR | Approval | 23.256 CR0176 (Rel-19, 'F'): Correction on UAV service operation description | Huawei, HiSilicon | Rel-19 | 4.4.1.1.3.3, 4.4.1.1.3.5, 4.4.1.1.4.2 r01 agreed. Revised in e-mail session to S2-2501301. | Shabnam (Ericsson) provides comments will require update to the CR by the authors and explanation Runze (Huawei) provides r01 to Shabnam (Ericsson). ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501301 | CR | Approval | 23.256 CR0176R1 (Rel-19, 'F'): Correction on UAV service operation description | Huawei, HiSilicon | Rel-19 | Revision of S2-2500829r01. Approved | Agreed | |
| 19.10.2 | S2-2500831 | CR | Approval | 23.256 CR0178 (Rel-19, 'F'): Clarification of USS list provisioning | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Shabnam (Ericsson) provides comments and does not agree to the proposed changes Ashok (Samsung) propose to postpone the paper Runze (Huawei) disagrees with Shabnam (Ericsson), and insists the CR content is correct Jungje(Interdigital) support to postpone the paper. ==== General Revisions Deadline ==== Runze (Huawei) asks for clarification to Jungje(Interdigital) and Ashok (Samsung) and propose a way forward . Hello Ashok, you said 'In my view we should wait for SA3 to check their specification how they are doing their normative work and fitting to the call flow and then based on that if some alignment is needed we can do. Hence suggesting to postpone it.' I am not sure whether and how SA3 will address this issue. At least, what agreed by SA3 has potential overlapping/conflict with SA2 design. The intention of the CR is to clarify the issue from SA2 perspective. If you think SA3 will address this, I think we need to send an LS to SA3 to about SA2 view point. I can prepare the draft LS for your check and request a new tdoc number in CC#3. Shabnam (Ericsson) objects to all versions including original CR. ==== Comments Deadline ==== | Noted |
| 19.10.2 | S2-2500318 | CR | Approval | 23.256 CR0155 (Rel-19, 'F'): Clarification on reporting velocity in UAV location reporting procedure | China Mobile | Rel-19 | 5.3.2 r01 agreed. Revised in e-mail session to S2-2501302. | LaeYoung (LGE) asks a Q about impact. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501302 | CR | Approval | 23.256 CR0155R1 (Rel-19, 'F'): Clarification on reporting velocity in UAV location reporting procedure | China Mobile, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2500318r01. Approved | Agreed | |
| 19.10.2 | S2-2500830 | CR | Approval | 23.256 CR0177 (Rel-19, 'F'): Provisioning of static flight path information | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Stefano (Qualcomm) proposes to note Runze (Huawei) replies to Stefano (Qualcomm). ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.10.2 | S2-2500440 | CR | Approval | 23.256 CR0164 (Rel-19, 'F'): Indicating optional steps of the pre-flight procedure | Ericsson | Rel-19 | Approved | Agreed | |
| 19.10.2 | S2-2500828 | CR | Approval | 23.256 CR0175 (Rel-19, 'F'): Correction on USS changeover aspects | Huawei, HiSilicon | Rel-19 | 5.13.2 r01 agreed. Revised in e-mail session to S2-2501303. | Shabnam (Ericsson) provides comments and r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501303 | CR | Approval | 23.256 CR0175R1 (Rel-19, 'F'): Correction on USS changeover aspects | Huawei, HiSilicon | Rel-19 | Revision of S2-2500828r01. Approved | Agreed | |
| 19.10.2 | S2-2500385 | CR | Approval | 23.256 CR0156 (Rel-19, 'F'): Removing EN about border-crossing point | LG Electronics | Rel-19 | Approved | LaeYoung (LGE) proposes to merge this CR into S2-2500438. Stefano (Qualcomm) prefer to proceed with S2-2500438. ==== General Revisions Deadline ==== LaeYoung (LGE) proposes to APPROVE this CR instead of merging into S2-2500438. ==== Comments Deadline ==== | Agreed |
| 19.10.2 | S2-2500439 | CR | Approval | 23.256 CR0163 (Rel-19, 'F'): Correcting the USS changeover procedure | Ericsson | Rel-19 | Noted in e-mail session | Jungje (Interdigital) proposes to note this CR. Shabnam (Ericsson) provides comments and indicates this is under SA2 responsibility. Stefano (Qualcomm) provides a reality check to Interdigital. Jungje(Interdigital) responds. Jungje(Interdigital) responds to Stefano (Qualcomm) ==== General Revisions Deadline ==== Jungje(Interdigital) oppose the CR and propose to note it. Shabnam (Ericsson) provides comments that we already have many operations left to application layer for UAVs, and USS changeover as a whole is started and managed outside 3GPP scope, we help facilitate the process smoothly. ==== Comments Deadline ==== | Noted |
| 19.10.2 | S2-2500441 | CR | Approval | 23.256 CR0165 (Rel-19, 'F'): Timestamping UAV's altitude information reports | Ericsson | Rel-19 | 5.16.3 Not handled at CC#4. Postponed | Runze (Huawei) does not think the change is necessary. ==== General Revisions Deadline ==== Shabnam (Ericsson) since this was wrongly tagged I did not see this, I would like to discuss in CC#3, as this is to complete the work based on that we need the time and it seems RAN does not include it ==== Comments Deadline ==== Runze (Huawei) replies to Shabnam (Ericsson) that whole TS work should not impact RAN, said in UAS WID. Shabnam (Ericsson) this was identified together with the incoming LS from RAN3 triggered by CMCC input to RAN3 last meeting, we had the offline discussion, as we have no time in February and due to wrong tdoc use no chance to have the discussion there is not much I can do now. | Postponed |
| 19.10.2 | S2-2500513 | CR | Approval | 23.256 CR0171 (Rel-19, 'F'): Altitude reporting update | CATT | Rel-19 | 5.16.1, 5.16.2, 5.16.3, 5.16.x r03 agreed. Revised in e-mail session to S2-2501304. | LaeYoung (LGE) provides r01. Shabnam (Ericsson) provides comments that will require update of the CR further. Yunjing (CATT) replies to Shabnam (Ericsson) and provides r02. Yunjing (CATT) replies to LaeYoung (LGE). Yunjing (CATT) provides r03. ==== General Revisions Deadline ==== Shabnam (Ericsson) provides comments with r04 Shabnam (Ericsson) provides comments regarding latest revision (r04) LaeYoung (LGE) provides comment and suggests to go with r03. LaeYoung (LGE) proposes to go with r03 instead of r04. Yunjing (CATT) is fine to go with r03. ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501304 | CR | Approval | 23.256 CR0171R1 (Rel-19, 'F'): Altitude reporting update | CATT | Rel-19 | Revision of S2-2500513r03. Approved | Agreed | |
| 19.10.2 | S2-2500476 | CR | Approval | 23.502 CR5245 (Rel-19, 'F'): Update Namf_EventExposure | CATT | Rel-19 | Approved | Josep (Deutsche Telekom) comments ==== General Revisions Deadline ==== LaeYoung (LGE) thinks r00 can be Approved without revision. Yunjing (CATT) replies to Josep (Deutsche Telekom). ==== Comments Deadline ==== | Agreed |
| 19.10.2 | - | - | - | KI#3: NTZ | - | - | Docs:=3 | - | |
| 19.10.2 | S2-2500113 | CR | Approval | 23.256 CR0154 (Rel-19, 'F'): Clarifications to NTZ support | Qualcomm Incorporated | Rel-19 | 2, 5.15 r07 agreed. Revised in e-mail session to S2-2501305. | Josep (Deutsche Telekom) asks question for clarification regarding the removed and added normative text. Michele Zarri [Huawei] asks question for clarification. Jungje(Interdigital) comments. Stefano [Qualcomm] replies to Josep and Michele. Josep (Deutsche Telekom) provides r01 for further dicussion, comments Stefano (Qualcomm) responds to Jengje. Stefano (Qualcomm) replies, R01 seems acceptable Jungje(Interdigital) responds to Stefano. Stefano (Qualcomm) responds to Jungje. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.10.2 | S2-2501305 | CR | Approval | 23.256 CR0154R1 (Rel-19, 'F'): Clarifications to NTZ support | Qualcomm Incorporated | Rel-19 | Revision of S2-2500113r07. Approved | Agreed | |
| 19.10.2 | S2-2500114 | LS OUT | Approval | [DRAFT] LA on NTZ support in UAV UE | QUALCOMM Europe Inc. - Spain | Rel-19 | Noted in e-mail session | Ashok (Samsung) agree with Shabnam (Ericsson) and proposes to Note the LS since there is no need, other WGs should use approved CRs/spec to complete the work. Shabnam (Ericsson) proposes to Note the LS since there is no need, other WGs should use approved CRs/spec to complete the work. Chris (Vodafone) thinks that RAN 2 probably should be informed, e.g. in case they want to move some parts into their specifications. Also, RAN 5 do not normally look at SA2 specifications. Stefano (Qualcomm) agrees with Vodafone and this is the reason the LS was created. ==== General Revisions Deadline ==== Ashok (Samsung) propose to NOTE the LS. Shabnam (Ericsson) comments that as RAN informed SA2 already, there will be no specification work in RAN on this other than potential testing, that is where we are in Rel-19. Companies are welcome to try but no need for LS. ==== Comments Deadline ==== | Noted |
| 19.11.1 | - | - | - | Study on UPF enhancement for Exposure And SBA Phase 2 (FS_UPEAS_Ph2) | - | - | Docs:=0 | - | |
| 19.11.2 | - | - | - | UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2) | - | - | Docs:=30 | - | |
| 19.11.2 | - | - | - | KI#1 | - | - | Docs:=3 | - | |
| 19.11.2 | S2-2500873 | CR | Approval | 23.501 CR6021 (Rel-19, 'F'): Clarification on the Operator configurable UPF capabilities | ZTE | Rel-19 | Noted in e-mail session | Jinguo(ZTE) provide r01 to merge the changes on 5.8.2.21 in 1046 Magnus (Ericsson) cannot accept ' (e.g. type of NAT).' Jinguo(ZTE) request to ignore the previous comment from Jinguo(ZTE), and provide r03 Naman (Samsung) clarifies that r02 was already provided by Samsung, the link shared by ZTE also refers to the Samsung's r02 Jinguo(ZTE) provides r02 Naman (Samsung) provides r02 Josep (Deutsche Telekom) comments, provides r04, co-signs Jinguo(ZTE) asks question for clarification Josep (Deutsche Telekom) replies to Jinguo (ZTE) Naman (Samsung) provides comments Jinguo(ZTE) response to Naman and is OK with r04 Naman (Samsung) replies and provides r05, r06 Laurent (Nokia): provides r07 ==== General Revisions Deadline ==== Jinguo(ZTE) is ok with r07 Mohammad Soliman (Nokia) can only accept r07 Naman (Samsung) proposes to go with r07 + removal of 'non-standardized' from Note 2. Naman (Samsung) can accept only r07 + removal of 'non-standardized' from Note 2. objects to r00-r04, r07 Fenqin (Huawei) we are ok with r07 or the update as suggested by Naman, i.e. the change on NOTE 2. Magnus (Ericsson) objects to all revisions of this CR Jinguo(ZTE) agree with Naman (Samsung) , suggest to approve r07 + removal of 'non-standardized' from Note 2. Jinguo(ZTE) asks for CC#4 ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2501046 | CR | Approval | 23.501 CR6056 (Rel-19, 'F'): Clarification to UPF selection based on specific UPF functionalities | Samsung | Rel-19 | Focus on 6.2.3 and 6.3.3.3? r05 agreed. Revised in e-mail session to S2-2501232. | Jinguo(ZTE) propose to use this CR as basis and focus on 6.2.3 and 6.3.3.3 Mohammad Soliman (Nokia): provides r01 Zhao (Huawei) provides comments and r02. Naman (Samsung) responds and provides r03 Naman (Samsung) responds to Zhao (Huawei) Zhao (Huawei) provides comments on r03. Naman (Samsung) provides r04 Laurent (Nokia): provides r05 ==== General Revisions Deadline ==== Josep (Deutsche Telekom) is fine with r05 or r04, would like to co-sign Laurent (Nokia): objects to any version of this Tdoc but could easily live with R05 with a very small addition Zhao (Huawei) can only accept r05 with the removal of the changes in clause 6.3.3.3. Naman (Samsung) replies to Zhao (Huawei) that changes in 6.3.3.3 are needed to clarify the sentence and align with the 23.502 CR Zhao (Huawei) replies to Naman (Samsung) that the original text in clause 6.3.3.3 is clear enough, no need to be changed. Naman (Samsung) provides comments to Laurent (Nokia) Naman (Samsung) proposes to go with r05 + remove changes in clause 6.3.3.3 can be accepted ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501232 | CR | Approval | 23.501 CR6056R1 (Rel-19, 'F'): Clarification to UPF selection based on specific UPF functionalities | Samsung | Rel-19 | Revision of S2-2501046r05. Approved | Agreed | |
| 19.11.2 | - | - | - | KI#2 | - | - | Docs:=19 | - | |
| 19.11.2 | S2-2501045 | CR | Approval | 23.288 CR1368 (Rel-19, 'F'): Editorial Clarifications for AF retreival of UE public IP address | Samsung | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501233. | Huazhang (CMCC) have comments Zhao (Huawei) provides comments and r01. Naman (Samsung) responds and provides r02 Naman (Samsung) : r03 looks good Zhao (Huawei) provides r03. Laurent (Nokia): Comments, R03 OK but please update to make the line of NWDAF really vertical ==== General Revisions Deadline ==== Mohammad Soliman (Nokia) is OK with r03 ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501233 | CR | Approval | 23.288 CR1368R1 (Rel-19, 'F'): Editorial Clarifications for AF retreival of UE public IP address | Samsung | Rel-19 | Revision of S2-2501045r03. Approved | Agreed | |
| 19.11.2 | S2-2500163 | CR | Approval | 23.501 CR5894 (Rel-19, 'D'): Fix grammar and align text in clause 5.8.2.17 | Nokia | Rel-19 | Merge into S2-2500596? Merged into S2-2501235 | Jinguo(ZTE) propose to merge this CR into 0596 Mohammad Soliman (Nokia) Agree to merge this CR into 0596 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.11.2 | S2-2500285 | CR | Approval | 23.501 CR5916 (Rel-19, 'F'): Update on QoS monitoring and reporting during UPF relocation and PDU session release | ETRI | Rel-19 | r05 agreed. Revised in e-mail session to S2-2501234. | Magnus (Ericsson) provides r01 Naman (Samsung) has concerns with the proposal Changki(ETRI) reply to Naman(Samsung) Magnus (Ericsson) provides r02 Fenqin(Huawei) provides comment Naman(Samsung) replies to Changki(ETRI) Chang(ETRI) provide r04 Fenqin (Huawei) provides comments. Changki (ETRI) provides r03 with update. Changki (ETRI) reply to Fenqin (Huawei) and Naman (Samsung) Magnus (Ericsson) provides r05 ==== General Revisions Deadline ==== Changki (ETRI) is OK with r05. Laurent (Nokia): objects to R00, R03 and R04 Fenqin (Huawei) we are OK with r05. ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501234 | CR | Approval | 23.501 CR5916R1 (Rel-19, 'F'): Update on QoS monitoring and reporting during UPF relocation and PDU session release | ETRI | Rel-19 | Revision of S2-2500285r05. Approved | Agreed | |
| 19.11.2 | S2-2500596 | CR | Approval | 23.501 CR5980 (Rel-19, 'F'): Updates of UPF event exposure during N4 session release | Huawei, HiSilicon | Rel-19 | r06 agreed. Revised in e-mail session to S2-2501235, merging S2-2500163 | Magnus (Ericsson) provides r01 Zhao (Huawei) replies to Magnus (Ericsson) and provides r02 which merges the S2-2500163 per rapporteur's suggestion. Mohammad Soliman (Nokia) provides r03 and cosigning Magnus (Ericsson) provides r04 Zhao (Huawei) provides r05, we prefer r03 and can live with r05. Magnus (Ericsson) objects to r00,r01,r02,r03. Proposes to go with r05 Naman (Samsung) provides r06 Zhao (Huawei) is fine with r06. ==== General Revisions Deadline ==== Mohammad Soliman (Nokia) accepts r06 ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501235 | CR | Approval | 23.501 CR5980R1 (Rel-19, 'F'): Updates of UPF event exposure during N4 session release | Huawei, HiSilicon, Nokia, Samsung | Rel-19 | Revision of S2-2500596r06, merging S2-2500163. Approved | Agreed | |
| 19.11.2 | S2-2500237 | CR | Approval | 23.502 CR5216 (Rel-19, 'F'): Corrections for Any_UE and Group_ID data collection targets | Ericsson | Rel-19 | Noted in e-mail session | Mohammad Soliman (Nokia): provides r01 Huazhang (CMCC) provides comments Zhao (Huawei) provides comments. Jinguo(ZTE) provides r03 Huazhang (CMCC) provides comments to R02 Zhao (Huawei) provides r02 which merges 0597 and 0598 per rapporteur's suggestion. Mohammad Soliman (Nokia): provides r04 which merges 0956 per rapporteur's suggestion and cosigning Zhao (Huawei) provides comments and asks for clarification. Naman (Samsung) provides r05 on top of r03 Mohammad Soliman (Nokia): provides r06 which merges 0956 per rapporteur's suggestion, cosigning, and providing further comments Zhao (Huawei) provides comments and r08. Huazhang (CMCC): provides r07 based on r06 Magnus (Ericsson) have issues with r08 Zhao (Huawei) replies to Magnus (Ericsson). Laurent (Nokia): we have the same issues wrt r08 as Magnus (E///) Laurent (Nokia): provides r09 Naman (Samsung) provides r10 Zhao (Huawei) provides r11. ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc except R10 (best) and R09 Magnus (Ericsson) objects to r11 and for simplicity we object to r00-r08 and can only accept r09 or10 Naman (Samsung) proposes to accept r10, objects r00-r09 Zhao (Huawei) objects r00-r10, proposes to go with r10 + remove the changes regarding any UE in clause 4.15.4.5.6 (i.e., remove: When the UPF event consumer targets Any UE, the same procedure applies with the following changes: - In step 1 target is Any UE. - Step 2 and step 3 are performed for each of the UEs selected by the SMF to serve the request received in step 1. - Step 4 to step 8 may apply to any of the PDU sessions selected by the SMF to serve the request received in step 1. ). ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2500598 | CR | Approval | 23.502 CR5261 (Rel-19, 'F'): Clarification of any UE and group UE cases | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jinguo(ZTE) propose to merge this CR into 0237 Zhao (Huawei) agrees to merge this CR into 0237. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2501048 | CR | Approval | 23.502 CR5323 (Rel-19, 'F'): Clarification of UPF relocation and remaining data reporting and handling of Any UE case | Samsung | Rel-19 | Noted in e-mail session | Jinguo(ZTE) propose to merge this CR into 0237 Magnus (Ericsson) provides comments Naman (Samsung) responds Laurent (Nokia): Considers that this CR should not be discussed as proposed by jinguo and that discussion/work on 0237 suffices Naman (Samsung) agrees this CR can be considered merged to 0237 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2500286 | CR | Approval | 23.502 CR5235 (Rel-19, 'F'): Update on UPF event exposure service during UPF relocation and N4 session release | ETRI | Rel-19 | Remove 4.15.4.5.6 and 4.15.4.5.7? r05 agreed. Revised in e-mail session to S2-2501236. | Changki(ETRI) provides r01 with some clause removal Huazhang (China Mobile) provides comments and seek clarification. Zhao (Huawei) provides comments and r02. Changki(ETRI) provides comments. Huazhang (CMCC) reply to Changki (ETRI) Changki (ETRI) reply to Huazhong (CMCC) Huazhang (CMCC) reply to Changki(ETRI) Laurent (Nokia): Comments, shouldn't this debate be done about 0237 ? Mohammad Soliman (Nokia) provides r03 Chang(ETRI) provide r04 Fenqin (Huawei) provides comment Laurent (Nokia): provides r05 ==== General Revisions Deadline ==== Changki (ETRI) is OK with r05. Naman (Samsung) is OK with r05. Laurent (Nokia): objects to any version between R00 and R02 both included Fenqin (Huawei): we are ok with r05 ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501236 | CR | Approval | 23.502 CR5235R1 (Rel-19, 'F'): Update on UPF event exposure service during UPF relocation and N4 session release | ETRI | Rel-19 | Revision of S2-2500286r05. Approved | Agreed | |
| 19.11.2 | S2-2500597 | CR | Approval | 23.502 CR5260 (Rel-19, 'F'): Updates of UPF event exposure during N4 session release | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Jinguo(ZTE) propose to merge this CR into 0237 Zhao (Huawei) confirms that this CR merges into 0237. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2500874 | CR | Approval | 23.502 CR5296 (Rel-19, 'F'): Correction on UPF event exposure service via SMF during UPF relocation and PDU Session release | ZTE | Rel-19 | Noted in e-mail session | Jinguo(ZTE) propose to merge this CR into 0237 Laurent (Nokia): supports to not consider 874 but only 237 ==== General Revisions Deadline ==== Mohammad Soliman (Nokia) objects to this tdoc for the sake of merging ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2500956 | CR | Approval | 23.502 CR5308 (Rel-19, 'F'): Fix figure in clause 4.15.4.5.5 and align clauses 4.15.4.5.6, 4.15.4.5.7 | Nokia | Rel-19 | Noted in e-mail session | Jinguo(ZTE) propose to merge this CR into 0237 Mohammad Soliman (Nokia) agrees to merge this CR into 0237 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2501047 | CR | Approval | 23.502 CR5322 (Rel-19, 'F'): Correction to direct subscription of UPF event expsoure using UE IP address | Samsung | Rel-19 | Noted in e-mail session | Jinguo(ZTE) suggest not to merge this CR into 0237 and can be discussed separately Naman (Samsung) provides comments Naman (Samsung) responds to Fenqin (Huawei) Fenqin(Huawei) think this change is not needed Mohammad Soliman (Nokia) agrees with Fenqin (Huawei) comment Naman (Samsung) replies Laurent (Nokia): agrees with Fenqin that this change is not needed Naman (Samsung) requests for technical clarification as to why the change is not needed ==== General Revisions Deadline ==== Naman (Samsung) proposes to go with r00 Laurent (Nokia): objects to any version of this Tdoc Naman (Samsung) is OK to postpone it ==== Comments Deadline ==== | Noted |
| 19.11.2 | S2-2501049 | CR | Approval | 23.502 CR5324 (Rel-19, 'F'): Corrections to UPF event exposure service description for UE NAT mapping | Samsung | Rel-19 | Affected clauses Missing. Revised to S2-2501068 | Revised | |
| 19.11.2 | S2-2501068 | CR | Approval | 23.502 CR5324R1 (Rel-19, 'F'): Corrections to UPF event exposure service description for UE NAT mapping | Samsung | Rel-19 | Revision of S2-2501049. Check Affected Clauses! r02 agreed. Revised in e-mail session to S2-2501237. | Fenqin (Huawei) provides r01 Naman (Samsung) : changes in r01 looks OK Laurent (Nokia): provides r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501237 | CR | Approval | 23.502 CR5324R2 (Rel-19, 'F'): Corrections to UPF event exposure service description for UE NAT mapping | Samsung | Rel-19 | Revision of S2-2501068r02. Approved | Agreed | |
| 19.11.2 | - | - | - | KI#3 | - | - | Docs:=8 | - | |
| 19.11.2 | S2-2500236 | CR | Approval | 23.501 CR5904 (Rel-19, 'F'): Handling of Headers corrections | Ericsson, Nokia, ETRI | Rel-19 | r05 agreed. Revised in e-mail session to S2-2501238, merging S2-2500271 and S2-2500284 | Huazhang (CMCC) comments to original version Fenqin (Huawei) provides comments Magnus (Ericsson) provides r01 Huazhang (CMCC) ask clarification on r03 Huazhang (CMCC) provides r02 based on r01 Fenqin (Huawei) provides r03 Magnus (Ericsson) provides r04 Fenqin (Huawei) provides r05 ==== General Revisions Deadline ==== Changki (ETRI) is OK with r05. Magnus (Ericsson) are OK with r05, for the sake of simplicity we object to r00-r03 Fenqin (Huawei) accept r05 ,r03, object other version ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501238 | CR | Approval | 23.501 CR5904R1 (Rel-19, 'F'): Handling of Headers corrections | Ericsson, Nokia, ETRI | Rel-19 | Revision of S2-2500236r05, merging S2-2500271 and S2-2500284. Approved | Agreed | |
| 19.11.2 | S2-2500271 | CR | Approval | 23.501 CR5913 (Rel-19, 'F'): Update of the description of handling of Payload Headers | China Mobile | Rel-19 | Merge into S2-2500236? Merged into S2-2501238 | Jinguo(ZTE) propose to merge this CR into 0236 Mohammad Soliman (Nokia): Agree on merging this CR into 0236 with comments Magnus H (Ericsson) has same comment as Mohammad (Nokia) Mohammad Soliman (Nokia) provides comment clarification Huazhang (China Mobile) reply to Mohammad Soliman (Nokia) Fenqin (Huawei) also suggest to merget this paper to 0236 Huazhang (CMCC) agree to merge ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.11.2 | S2-2500284 | CR | Approval | 23.501 CR5915 (Rel-19, 'F'): Update on Handling of Payload Headers | ETRI | Rel-19 | Merge into S2-2500236? Merged into S2-2501238 | Jinguo(ZTE) propose to merge this CR into 0236 Laurent (Nokia): supports Jinguo(ZTE) proposal to merge this CR into 0236 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.11.2 | S2-2500238 | CR | Approval | 23.502 CR5217 (Rel-19, 'F'): Support of Handling of Headers | Ericsson, Nokia, ETRI | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501239. | Fenqin (Huawei) provides comments Magnus (Ericsson) provides r01 Huazhang (CMCC) reply the wrong email, and provides r02 based on r01 is paper 2500236, not 2500238, Fenqin (Huawei) provides r02 Huazhang (CMCC) provides r02 based on r01 ==== General Revisions Deadline ==== Changki (ETRI) is OK with r02, r01. Magnus (Ericsson) are OK with r02 Laurent (Nokia): suggests to go with R02 Fenqin (Huawei): accept r02, object other version ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501239 | CR | Approval | 23.502 CR5217R1 (Rel-19, 'F'): Support of Handling of Headers | Ericsson, Nokia, ETRI | Rel-19 | Revision of S2-2500238r02. Approved | Agreed | |
| 19.11.2 | S2-2500270 | CR | Approval | 23.502 CR5227 (Rel-19, 'F'): Adding supporting of handling of Payload Headers functionality in UPF provisioning information | China Mobile | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501240. | Mohammad Soliman (Nokia) provides comments Fenqin (Huawei) provides comments Fenqin (Huawei) reply to Huazhang(CMCC). Huazhang (CMCC) reply to Fenqin (Huawei) and Mohammad Soliman (Nokia) about the note in second change. the implict subscription in AF request should also be authenticated by NEF. Huazhang (CMCC) provides r01 Mohammad Soliman (Nokia) provides a comment on r01 Huazhang (CMCC) provides r02 ==== General Revisions Deadline ==== Josep (Deutsche Telekom) would like to co-sign Mohammad Soliman (Nokia) objects to r00 ==== Comments Deadline ==== | Revised |
| 19.11.2 | S2-2501240 | CR | Approval | 23.502 CR5227R1 (Rel-19, 'F'): Adding supporting of handling of Payload Headers functionality in UPF provisioning information | China Mobile, Deutsche Telekom | Rel-19 | Revision of S2-2500270r02. Approved | Agreed | |
| 19.12.1 | - | - | - | Study on System aspects of 5G NR Femto (FS_5G_Femto) | - | - | Docs:=0 | - | |
| 19.12.2 | - | - | - | System aspects of 5G NR Femto (5G_Femto) | - | - | Docs:=0 | - | |
| 19.13.1 | - | - | - | Study on Multi-Access (DualSteer and ATSSS_Ph4) (FS_MASSS) | - | - | Docs:=0 | - | |
| 19.13.2 | - | - | - | Multi-Access (ATSSS_Ph4) (MASSS) | - | - | Docs:=21 | - | |
| 19.13.2 | - | - | - | Use of MPQUIC-UDP when MPQUIC-IP is supported | - | - | Docs:=2 | - | |
| 19.13.2 | S2-2500245 | DISCUSSION | Discussion | Support for CONNECT-UDP with MPQUIC-only option. | Ericsson, Apple, Google | Noted in e-mail session | Noted | ||
| 19.13.2 | S2-2500246 | CR | Approval | 23.501 CR5907 (Rel-19, 'F'): Use of MPQUIC-UDP when MPQUIC-IP is supported | Ericsson, Apple, Google | Rel-19 | Noted in e-mail session | Pallab (Nokia) provides comments and raises concern with the proposal Naman (Samsung) supports the proposal in the CR Yishan (Huawei) provides comments Stefan (Ericsson) replies to Pallab and provides r01 Stefan (Ericsson) replies to Yishan Pallab (Nokia) responds to Stefan (Ericsson) Tianji (CMCC) has concern of the technical validity of the new category; and provide a way forward. Paul R. (Charter) provides comments Florin (CableLabs) supports the views from Charter, Nokia, Huawei, etc and proposes this contribution to be either POSTPONED or NOTED. Pallab (Nokia) responds to Krisztian (Apple) Yishan (Huawei) provides comments and asks for clarification Paul R (Charter) responds to Krisztian (Apple). Krisztian (Apple) responds to Paul R. (Charter). Krisztian (Apple) responds to Pallab (Nokia). Guanzhou (InterDigital) supports the motivation. Chia-Lin (MediaTek) provides comments and agree with Pallab (Nokia) and Yishan (Huawei) ==== General Revisions Deadline ==== Pallab (Nokia) proposes to NOTE this CR Florin (CableLabs) supports this CR to be NOTED. Yishan (Huawei) proposes to NOTE this CR Paul R (Charter) agrees to NOTE this CR, objects to r00 & r01 Paul R (Charter) correcting previous comment: supports agrees to NOTE this CR, objects to r00 & r01 ==== Comments Deadline ==== | Noted |
| 19.13.2 | - | - | - | Capability handling | - | - | Docs:=4 | - | |
| 19.13.2 | S2-2500243 | CR | Approval | 23.501 CR5906 (Rel-19, 'F'): Updates to the ATSSS capability handling | Ericsson, Apple, Google, AT&T | Rel-19 | r04 agreed. Revised in e-mail session to S2-2501306. | Pallab (Nokia) provides comments Myungjune (LGE) provides comments. Yishan (Huawei) provides comments Pallab (Nokia) provides r01 Stefan (Ericsson) replies to comments Myungjune (LGE) responses to Pallab (Nokia). Myungjune (LGE) responses to Stefan (Ericsson). Pallab (Nokia) responds Naman (Samsung) provides comments Myungjune (LGE) replies to Pallab (Nokia) Stefan (Ericsson) provides r02 Pallab (Nokia) provides r03 based on r02 Naman (Samsung) provides r04 ==== General Revisions Deadline ==== Yishan (Huawei) is ok with r04 and objects to r00. Krisztian (Apple) is OK with r04. Myungjune (LGE) is ok with r04. Pallab (Nokia) is OK to approve r04. Objects to r00 Florin (CableLabs) supports r04. ==== Comments Deadline ==== | Revised |
| 19.13.2 | S2-2501306 | CR | Approval | 23.501 CR5906R1 (Rel-19, 'F'): Updates to the ATSSS capability handling | Ericsson, Apple, Google, AT&T, Samsung | Rel-19 | Revision of S2-2500243r04. Approved | Agreed | |
| 19.13.2 | S2-2500244 | CR | Approval | 23.502 CR5220 (Rel-19, 'F'): Updates to the ATSSS capability handling | Ericsson, Apple, Google, AT&T | Rel-19 | Noted in e-mail session | Pallab (Nokia) provides comments. This CR depends on the corresponding 23.501 CR in S2-2500243 Yishan (Huawei) provides comments and agrees with Pallab (Nokia) Florin (CableLabs) supports the views from Nokia, Huawei and also points out that the dependency is on the corresponding 23.501 CR in S2-2500246 and not in S2-2500243. ==== General Revisions Deadline ==== Krisztian (Apple): this CR is dependent on 0243 and needs to be aligned with 0243r04. Should it be postponed as there was no revision before the deadline? Pallab (Nokia) proposes to NOTE this CR as the corresponding part related to accepting a MA PDU Session establishment request as a Single access PDU session is removed from 0243r04 Yishan (Huawei) proposes to NOTE this CR as downgrading a MA PDU Session to a Single access PDU session is unnecessary based on previous email discussion Stefan (Ericsson) OK to NOTE this 23.502 CR since the correspodning parts in the 23.501 CR were not agreed ==== Comments Deadline ==== | Noted |
| 19.13.2 | S2-2500615 | CR | Approval | 23.501 CR5983 (Rel-19, 'F'): Update of UE ATSSS capability | ETRI | Rel-19 | Noted in e-mail session | Jeounglak (ETRI) provides r02. Jeounglak (ETRI) provides r01. Pallab (Nokia) provides comments and raises concerns with the proposal Jeounglak (ETRI) replies to Pallab (Nokia) Yishan answers to Jeounglak (ETRI) and has concerns about changing the compromise. Jeounglak (ETRI) replies Yishan and Pallab. Naman (Samsung) provides comments Stefan (Ericsson) provides comments Krisztian (Apple) also proposes to NOTE this CR. Stefano (Qualcomm) respectfully reminds you that at least two companies indicate to note the paper and several indicate this is not acceptable. Jeounglak (ETRI) provides r03 with response. Zhuoyi (China Telecom) agrees with previous views that this CR changes the conclusion. Florin (CableLabs) supports previous views from Nokia, Charter, Qualcomm, etc. and also requests this document to be NOTED. Stefano (Qualcomm) responds to Jeounglak and Naman, and requests to note. Paul R (Charter) provides comments and raises concerns with the proposal Tianji (CMCC) provides comments and shares similar view; but can live with the NOTE as proposed by ETRI. ==== General Revisions Deadline ==== Florin (CableLabs) supports this CR to be NOTED and objects to all its revisions. Paul R. (Charter) agrees to Note this CR, objects to r00 through r03. Paul R. (Charter) correcting previous comment: supports agrees to Note this CR, objects to r00 through r03. ==== Comments Deadline ==== | Noted |
| 19.13.2 | - | - | - | QoS support | - | - | Docs:=3 | - | |
| 19.13.2 | S2-2500738 | CR | Approval | 23.501 CR5993 (Rel-19, 'F'): Correction on QoS Support | Huawei, HiSilicon | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501307, merging S2-2501050 | Stefan (Ericsson) provides comments Yishan (Huawei) answers to Stefan (Ericsson) and provides r01 ==== General Revisions Deadline ==== Stefan (Ericsson) is OK with r01. Not OK with r00. Florin (CableLabs) supports Stefan's (Ericsson) proposal in r01 and agrees to r01 and objects to r00. ==== Comments Deadline ==== | Revised |
| 19.13.2 | S2-2501307 | CR | Approval | 23.501 CR5993R1 (Rel-19, 'F'): Correction on QoS Support | Huawei, HiSilicon | Rel-19 | Revision of S2-2500738r01, merging S2-2501050. Approved | Agreed | |
| 19.13.2 | S2-2501050 | CR | Approval | 23.501 CR6057 (Rel-19, 'F'): Corrections for QoS support for MPQUIC-E functionality | Samsung | Rel-19 | Merged into S2-2501307 | Yishan (Huawei) proposes to merge S2-2501050 into S2-2500738 Naman (Samsung) agrees to merge it S2-2500738 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.13.2 | - | - | - | Other corrections | - | - | Docs:=12 | - | |
| 19.13.2 | S2-2501067 | CR | Approval | 23.503 CR1504 (Rel-19, 'F'): Clarification for PCF behaviour for generating matchall PCC rules for MA PDU Session | Samsung | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501308, merging S2-2500737 | Naman (Samsung) replies Yishan (Huawei) proposes to merge this (S2-2501067) into S2-2500737 Stefan (Ericsson) provides r01 but not clear whether this is considered merged into 0737 ==== General Revisions Deadline ==== Yishan (Huawei) is ok with r01 and is ok that 0737 is merged into 1067 Naman (Samsung) proposes to agree r01 Stefan (Ericsson) is ok with r01 and is ok that 0737 is merged into 1067 Florin (CableLabs) agrees with the merge of 0737 into this CR and supports r01. ==== Comments Deadline ==== | Revised |
| 19.13.2 | S2-2501308 | CR | Approval | 23.503 CR1504R1 (Rel-19, 'F'): Clarification for PCF behaviour for generating matchall PCC rules for MA PDU Session | Samsung | Rel-19 | Revision of S2-2501067r01, merging S2-2500737. Approved | Agreed | |
| 19.13.2 | S2-2500459 | CR | Approval | 23.501 CR5959 (Rel-19, 'F'): Some corrections in MPQUIC steering functionalities | China Mobile | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501309. | Stefan (Ericsson) provides r01 Yishan (Huawei) provides r02 Myungjune (LGE) provides comments. Tianji (CMCC) OK with the r01 Tianji (CMCC) provides r03 with minor changes from r02. Florin (CableLabs) kindly requests further information regarding the corrections proposed by this CR and the ones proposed by Apple in the Terminology alignment CRin S2-2501073. ==== General Revisions Deadline ==== Tianji (CMCC) provides clarification. Krisztian (Apple) proposes to agree r01 and delete NOTE4 from r01. Myungjune (LGE) is ok with r03. Tianji (CMCC) can accept r01 and delete NOTE4 from r01; also accept r03. Stefan (Ericsson) also OK to agree r01 and delete NOTE 4 from r01. Florin (CableLabs) agrees with Krisztian's (Apple) proposal and supports r01 and the removal of NOTE4 . Tianji (CMCC) provide a draft-revision for approval: 'r01 and delete the NOTE 4 from r01' ==== Comments Deadline ==== | Revised |
| 19.13.2 | S2-2501309 | CR | Approval | 23.501 CR5959R1 (Rel-19, 'F'): Some corrections in MPQUIC steering functionalities | China Mobile | Rel-19 | Revision of S2-2500459r01. Approved | Agreed | |
| 19.13.2 | S2-2500527 | CR | Approval | 23.501 CR5969 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | LG Electronics | Rel-19 | Noted in e-mail session | Pallab (Nokia) provides comments. Supports solution Alternative-2 in the CR Naman (Samsung) provides comments on alternate-2 Myungjune (LGE) asks question to Naman (Samsung). Naman (Samsung) replies to Myungjune (LG) Myungjune (LGE) replies to Naman (Samsung). Yishan (Huawei) provides comments Stefan (Ericsson) provides comments Naman (Samsung) provides r02 and provides comment on r01 Myungjune (LGE) provides r01. Tianji (CMCC) provides comments Pallab (Nokia) clarifies that r01 is based on Alternative-2 proposed in the original CR Myungjune (LGE) provides r03 based on Alternative 2, i.e. mandating UE IP capability. Naman (Samsung) replies, have similar concerns with r03 as with r01 Myungjune (LGE) answers to Zhuoyi (China Telecom). Zhuoyi (China Telecom) can accept Alternative-2. Myungjune (LGE) responses to Naman (Samsung). Stefano (Qualcomm) supports r03 based on Alternative 2, states that asking a Rel. 19 UE to support both protocol versions is not an issue in the real world. Florin (CableLabs) supports r03 based on Alternative 2. ==== General Revisions Deadline ==== Myungjune (LGE) proposes to agree r03. Tianji (CMCC) supports r03. Naman (samsung) objects to r00, r01 and r03, is ok with r02; Pallab (Nokia) also proposes to agree r03 Florin (CableLabs) supports r03 of this CR and objects to all the other previous revisions. Pallab (Nokia) responds to Naman (Samsung) Tianji (CMCC) OK r03 Yishan (Huawei) proposes to agree r03 and objects to r00, r01 and r02. Naman (Samsung) responds to Pallab (Nokia); sustains objection on r00, r01 and r03 Stefan (Ericsson) supports r03 and objects to r00, r01 and r02. ==== Comments Deadline ==== | Noted |
| 19.13.2 | S2-2500528 | CR | Approval | 23.502 CR5251 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E in procedure | LG Electronics | Rel-19 | Noted in e-mail session | Pallab (Nokia) provides same comments as in S2-2500527. Support solution Alternative-2 in the CR Myungjune (LGE) provides r01. Naman (Samsung) have same views on r01 as mentioned in 0527 thread; this paper depends on the progress of 0527 ==== General Revisions Deadline ==== Naman (Samsung) objects to r00 and r01, can live with r00 + removing the 'Alternate 2' section; also ok to postpone Pallab (Nokia) asks shall we POSTPONE this CR as there is no revision? R00 cannot be agreed as it has two Alternatives. Pallab (Nokia): Please ignore my previous comment on this CR as I missed the r01 document. OK to approve r01 if 0527r03 is approved. Yishan (Huawei) is OK to approve r01 if 0527r03 is approved, and objects to r00 since r00 includes two alternatives. Stefan (Ericsson) is OK with r01 and asks whether it is independent of the 23.501 CR (0527r03) since it does not talk about how UPF selects between v4 or v6. Naman (Samsung) comments that r01 cannot be accepted unless we have an over all agreement on 501 CR Myungjune (LGE) replies to Stefan (Ericsson) and provides draft revision. Myungjune (LGE) proposes to agree r01+cover sheet update to align with CR contents. Stefan (Ericsson) supports agreeing r01+cover sheet update to align with CR contents, as suggested by Myungjune. Naman (Samsung) objects to any version of this CR Florin (CableLabs) supports r01 plus cover sheet update and objects to r00. ==== Comments Deadline ==== | Noted |
| 19.13.2 | S2-2501073 | CR | Approval | 23.501 CR6061 (Rel-19, 'F'): Terminology alignment | Apple | Rel-19 | Not handled at CC#4. Postponed | Yishan (Huawei) provides r01 ==== General Revisions Deadline ==== Pallab (Nokia) points out that cover sheet changes (update clauses affected, untick ME impact) required before we approve r01 Krisztian (Apple) re-iterates to move forward with r00. Tianji (CMCC) can accept both r00 and r01. ==== Comments Deadline ==== Pallab (Nokia) indicates that r00 may need a revision as it looks like Figure 5.32.6.1-1 is deleted. Krisztian (Apple) indicates no changes needed to Figure 5.32.6.1-1. r00 should be revised to a new tdoc with this fix. | Postponed |
| 19.13.2 | S2-2500736 | CR | Approval | 23.501 CR5992 (Rel-19, 'F'): Editorial Correction on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | Not handled at CC#4. Postponed | Yishan (Huawei) provides r01 Stefan (Ericsson) provides comments Yishan (Huawei) thanks Stefan (Ericsson) for spotting the errors and provides r02 to correct them ==== General Revisions Deadline ==== Yishan (Huawei) thanks for the clarification from Krisztian (Apple) and would like to provide a way forward Krisztian (Apple) responds to Yishan (Huawei). Yishan (Huawei) requests Krisztian (Apple) to withdraw/reconsider the objection and can provide the comments before revision deadline Krisztian (Apple) proposes to NOTE this CR and move forward with 1073. Tianji (CMCC) like the way forward proposed by Yishan (Huawei) to address the gap among #00736, #01073, and potentially the impact to #00459 Krisztian (Apple) proposes to keep the Fourth Change from r02 (Change on 6.3.3.3) Tianji (CMCC) provides clarification on '...can re-visit it in the Feb meeting' ==== Comments Deadline ==== Yishan (Huawei) is ok to keep the Fourth Change from r02 (Change on 6.3.3.3) as compromise | Postponed |
| 19.13.2 | S2-2500616 | CR | Approval | 23.501 CR5984 (Rel-19, 'D'): Clarification on steering functionalities description | ETRI | Rel-19 | Approved | Agreed | |
| 19.13.2 | S2-2500739 | CR | Approval | 23.502 CR5277 (Rel-19, 'F'): Editorial Correction on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | Approved | Agreed | |
| 19.13.2 | S2-2500737 | CR | Approval | 23.503 CR1487 (Rel-19, 'F'): Clarification on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | Merged into S2-2501308 | Naman (Samsung) proposes to merge this into 1067 Tianji (CMCC) supports the merge of 00737 & 01067 Naman (Samsung) replies Florin (CableLabs) also supports Yishan (Huawei)'s proposal to have the Samsung CR in S2-2501067 merged into S2-2500737. Naman (Samsung) clarifies that S2-2500737 is being merged into Samsung's S2-2501067 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.13.2 | S2-2500617 | CR | Approval | 23.503 CR1485 (Rel-19, 'D'): Editorial changes on provisioning PCC rule for ATSSS | ETRI | Rel-19 | Approved | Agreed | |
| 19.14.1 | - | - | - | Study on Architecture support of Ambient power-enabled Internet of Things (FS_AmbientIoT) | - | - | Docs:=75 | - | |
| 19.14.1 | - | - | - | LS | - | - | Docs:=0 | - | |
| 19.14.1 | - | - | - | LS in for information | - | - | Docs:=5 | - | |
| 19.14.1 | S2-2500049 | LS In | Information | LS from RAN WG2: LS on RAN2 outcome of Ambient IoT study | RAN WG2 (R2-2411263) | Rel-19 | Noted in e-mail session | Runze (Huawei) proposes to note this LS, because SA2 is only CCed. Sang-Jun (Samsung) proposes to note the LS, as it does not require any SA2 actions. | Noted |
| 19.14.1 | S2-2500054 | LS In | Information | LS from RAN WG3: LS on RAN3 outcome of Ambient IoT study | RAN WG3 (R3-247923) | Rel-19 | Noted in e-mail session | Sang-Jun (Samsung) agrees to note the LS. Runze (Huawei) proposes to note this LS, because SA2 is only CCed. | Noted |
| 19.14.1 | S2-2500061 | LS In | Information | LS from SA WG1: Reply to LS on Further Clarification for Ambient IoT Security | SA WG1 (S1-244920) | Rel-19 | Noted in e-mail session | Sang-Jun (Samsung) agrees to note the LS. Runze (Huawei) proposes to note this LS, because SA2 is only CCed. | Noted |
| 19.14.1 | S2-2500021 | LS In | Information | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 (S3-245139) | Rel-19 | Noted in e-mail session | Sang-Jun (Samsung) agrees to note the LS. Runze (Huawei) proposes to note this LS, because the reply provided in the LS does not indicate any action to SA2. | Noted |
| 19.14.1 | S2-2500018 | LS In | Information | LS from RAN WG2: LS on assistance information from the CN to the Reader for A-IoT | RAN WG2 (R2-2409412) | Rel-19 | Noted in e-mail session | Sang-Jun (Samsung) agrees to note the LS. Runze (Huawei) proposes to note this LS, because SA2 has replied this LS in Orlando meeting. | Noted |
| 19.14.1 | - | - | - | LS from RAN WG2: LS on RAN2 agreements and assumptions for Ambient IoT | - | - | Docs:=3 | - | |
| 19.14.1 | S2-2500006 | LS In | Information | LS from RAN WG2: LS on RAN2 agreements and assumptions for Ambient IoT | RAN WG2 (R2-2406150) | Response drafted in S2-2500745. Noted in e-mail session | Noted | ||
| 19.14.1 | S2-2500745 | LS OUT | Approval | [DRAFT] Reply LS on RAN WG2 agreements and assumptions for Ambient IoT | Samsung | Response to S2-2500006. Noted in e-mail session | Fei (OPPO) provides responses to Dongjoo (Nokia) Dongjoo (Nokia) provides feedback to Fei (OPPO). Fei (OPPO) responds to Dongjoo (Nokia) Dongjoo (Nokia) proposes not to note this LS reply but modifies it so we properly reply to their questions. Fei (OPPO) proposed to note this reply LS. Dongjoo (Nokia) supports the view from Runze (Huawei) and provide more comments. Runze (Huawei) provides comments on the LS reply. Robbie (Ericsson) replies to Fei (OPPO) and Dongjoo (Nokia) Deng Qiang (CATT) proposed to NOTED this LS Runze (Huawei) replies and agrees to note the LS. Henrik N (NTT DOCOMO) provides comments, shares some views with Nokia, and propose further discussion before noting the LS. Fei (OPPO) replied to Henrik (NTT DOCOMO) Dongjoo (Nokia) provides r02. Sang-Jun (Samsung) provides r01. Henrik N (NTT DOCOMO) replies to OPPO Fei (OPPO) provides replies to Henrik (NTT DOCOMO) Lars (Sony) comments on r02 Dongjoo (Nokia) provides comments. Guanzhou (InterDigital) questions the necessity of this LS response and proposes to note this. Runze (Huawei) comments on r01 and r02. Genadi (Lenovo) comments on whether to keep this LS reply. ==== General Revisions Deadline ==== ==== Comments Deadline ==== Runze (Huawei) propose to note the LS reply, as it was covered by other LS, and also note the LS in S2-2500006 | Noted | |
| 19.14.1 | S2-2500007 | LS In | Information | LS from RAN WG1: Reply LS on Clarification of requirements for Ambient IoT | RAN WG1 (R1-2407364) | Noted in e-mail session | Sang-Jun (Samsung) agrees to note the LS. Runze (Huawei) proposes to note this LS. | Noted | |
| 19.14.1 | - | - | - | LS from RAN WG2: LS on data block sizes for Ambient IoT | - | - | Docs:=3 | - | |
| 19.14.1 | S2-2500008 | LS In | Action | LS from RAN WG2: LS on data block sizes for Ambient IoT | RAN WG2 (R2-2407831) | Response drafted in S2-2500743. Noted in e-mail session | Sang-Jun (Samsung) proposes to note the LS, as RAN2 has addressed this issue with the RAN1 reply. | Noted | |
| 19.14.1 | S2-2500012 | LS In | Action | LS from RAN WG1: Reply LS to RAN WG2 on data block sizes for Ambient IoT | RAN WG1 (R1-2409250) | Rel-19 | Noted in e-mail session | Sang-Jun (Samsung) proposes to note the LS, as SA2 is only CCed. | Noted |
| 19.14.1 | S2-2500743 | LS OUT | Approval | [DRAFT] Reply LS on data block sizes for Ambient IoT | Samsung | Response to S2-2500008. Noted in e-mail session | Dongjoo (Nokia) supports the view from Fei (OPPO). Fei (OPPO) also proposed to note this reply LS Runze (Huawei) provides comments on the LS reply, and suggests no need to reply to the LS in. Runze (Huawei) supports the view from Fei (OPPO) to NOTE the LS. Sebastian (Qualcomm) objects to the LS Sang-Jun (Samsung) accepts the proposals to note the LS. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 19.14.1 | - | - | - | LS from RAN WG2: Further LS on Assistance information from CN to the reader | - | - | Docs:=4 | - | |
| 19.14.1 | S2-2500078 | LS In | Action | LS from RAN WG2: Further LS on Assistance information from CN to the reader | RAN WG2 (R2-2411232) | Rel-19 | Responses drafted in S2-2500648, S2-2500938. FInal response in S2-2501241 | Replied to | |
| 19.14.1 | S2-2500648 | LS OUT | Approval | [DRAFT] Reply LS on Assistance Information from CN to the Reader | ZTE | Rel-19 | Response to S2-2500078. CC#4: r11 agreed. Revised in CC#4 to S2-2501241. | Sang-Jun (Samsung) has similar views to Runze (Huawei)'s and Fei(OPPO)'s. Answers to Q1 and Q2 are fine, but we don't have agreed views on Q3. Fei (OPPO) replied to Dongjoo (Nokia) Hao (ZTE) comments. Runze (Huawei) replies to Dongjoo (Nokia). Hao (ZTE) provides comments. Dongjoo (Nokia) replies to Fei (OPPO) Dongjoo (Nokia) replies to Runze (Huawei) Fei (OPPO) comments and supports Q1 and Q2 in the reply LS. Dongjoo (Nokia) provides comments Robbie (Ericsson) provides comments. Runze (Huawei) provides comments on the LS reply. Deng Qiang (CATT) comments on Q3 Henrik N (NTT DOCOMO) provides comments and supports sending the LS Guanzhou (InterDigital) provides comments Sebastian (Qualcomm) provides r01 Hao (ZTE) responds and provides r03. Hanyu Ding (HONOR) provides comments to Q3 in r02. Sang-Jun (Samsung) comments on r02 Guanzhou (InterDigital) provides r02 Lars (Sony) Propose to add a 'No' in the start of the answer to Q2. Sebastian (Qualcomm) objects to r00, r02 and r03 and provides r04 Lars (Sony) agrees with Sebastian and r04 Hanyu Ding (HONOR) is fine with the answer to Q3 and provides comments for the answer to Q1. Walter (Philips) provides comments to Q3. Henrik N (NTT DOCOMO) agrees with Philips and prefers r03 Guanzhou (InterDigital) objects to r04 and provides r05 Lars (Sony) comments on the latency discussion Dongjoo (Nokia) objects r01, r04, r05 and provides r06. Genadi (Lenovo) provides r07 including a new question to RAN1/RAN2 whether the whether the AIoT reader is required to know the frequency of operation of the AIoT device. Dongjoo (Nokia) comments. Hao (ZTE) provides r08. Runze (Huawei) comments. Henrik N (NTT DOCOMO) provides comments and supports r07 LaeYoung (LGE) comments that RAN1 should be in To list instead of Cc list because there is Action to RAN1. Hao (ZTE) responds. Dongjoo (Nokia) replies to Runze (Huawei). Xiaowan(vivo) provide r09 to update the FB question a bit ==== General Revisions Deadline ==== Dongjoo (Nokia) ask a question. Hao (ZTE) provides r10 only removing the new added FB question. Runze (Huawei) agrees with Hao (ZTE) that FB question should be discussed in 2500937. Sebastian (Qualcomm) can accept r04, objects to other versions; asks questions related to r10 Dongjoo (Nokia) can live with r08 to r10, objects any other revisions. r04 can be acceptable only if the answer Q3 is changed to 'SA2 has discussed this issue while no consensus has been reached so far' Runze (Huawei) agrees Dongjoo (Nokia) proposal that r04 can be acceptable only if the answer Q3 is changed to 'SA2 has discussed this issue while no consensus has been reached so far' Hao (ZTE) agrees to go with r04 + changing answer to Q3 as 'SA2 has discussed this issue while no consensus has been reached so far'. Fei (OPPO) supports this proposal suggested by Dongjoo Xiaowan(vivo) think no big difference between 1) r04(with Q3 answer 'no') and 2) Dongjoo's request r04+answer to Q3 as 'SA2 has discussed this issue while no consensus' and suggest to take Dongjoo request to move forwards, for the interest of progress Guanzhou (InterDigital) can't accept r04. Propose to go with r05 or r10. Chris (Vodafone) says we should at least help RAN 2 progress by answering Q1 and Q2. I think that R10 does that? Hao (ZTE) responds to Guanzhou (InterDigital). Guanzhou (InterDigital) responds to Hao (ZTE) Walter (Philips) can live with r08 to r10, objects any other revisions. r04 can only be acceptable if the answer Q3 is changed to 'SA2 has discussed this issue while no consensus has been reached so far' ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501241 | LS OUT | Approval | Reply LS on Assistance Information from CN to the Reader | SA WG2 | Rel-19 | Revision of S2-2500648r11. This LS OUT was approved | Approved | |
| 19.14.1 | S2-2500938 | LS OUT | Approval | [DRAFT] LS reply on Further LS on Assistance information from CN to the reader | Huawei, HiSilicon | Rel-19 | Response to S2-2500078. Noted in e-mail session | Runze (Huawei) proposes to merge this LS reply into S2-2500648. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | - | - | - | LS out from SA2 | - | - | Docs:=7 | - | |
| 19.14.1 | S2-2500329 | LS OUT | Approval | [DRAFT] LS on BS Reader selection | CATT | Rel-19 | Noted in e-mail session | Dongjoo (Nokia) asks a question for clarification. Runze (Huawei) proposes to merge the LS to 2500937. Deng Qiang (CATT) replies to Dongjoo (Nokia). Deng Qiang (CATT) replies to Runze (Huawei). Sebastian (Qualcomm) objects to the LS as is ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500330 | LS OUT | Approval | [DRAFT] LS on AIoT security aspects | CATT | Rel-19 | Noted in e-mail session | Runze (Huawei) asks for clarification. Deng Qiang (CATT) replies to Runze (Huawei). Runze (Huawei) replies to Deng Qiang (CATT). Robbie (Ericsson) asks Runze (Huawei) Fei (OPPO) comments Robbie (Ericsson) replies to Fei (OPPO) Xiaowan (vivo) agrees SA3 has follow the SA2 well and SA2 can align SA3 later and would like to note the LS. Lars (Sony) Comments and see no need for this LS. Dongjoo (Nokia) comments. Robbie (Ericsson) shares the similar view as Dongjoo (Nokia). Dongjoo (Nokia) provide feedback. Henrik N (NTT DOCOMO) agrees with Vivo and Sony and comments Lars (Sony) responds to Dongjoo. Henrik N (NTT DOCOMO) responds to Nokia and Ericsson Sang-Jun (Samsung) comments. ==== General Revisions Deadline ==== Sebastian (Qualcomm) objects to the LS ( no need for it as commented by others also) ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500429 | LS OUT | Approval | [DRAFT] LS on Indicator in A-IoT Paging | Ericsson | Rel-19 | Noted in e-mail session | Robbie (Ericsson) agrees with Fei (OPPO) Fei (OPPO) indicates that this LS is pending on outcome of discussion in S2-2500425. Sebastian (Qualcomm) objects to the LS ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500430 | LS OUT | Approval | [DRAFT] LS on Device Subscription Data | Ericsson | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501242. | Runze (Huawei) provides comments. Dongjoo (Nokia) comments. Robbie (Ericsson) replies to Runze (Huawei). Runze (Zhou) proposes way forward. Runze (Huawei) replies to Dongjoo (Nokia). Junan Peng( China Mobile) agrees with NTT DOCOMO and Huawei. Henrik N (NTT DOCOMO) agrees with Huawei and comments Henrik N (NTT DOCOMO) responds to Ericsson Robbie (Ericsson) provides r01 Dongjoo (Nokia) questions. Robbie (Ericsson) replies to Dongjoo (Nokia) Robbie (Ericsson) provides r02 to align with the latest discussion in S2-2500973 Dongjoo (Nokia) replies. ==== General Revisions Deadline ==== Dongjoo (Nokia) provides r03. ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501242 | LS OUT | Approval | LS on Device Subscription Data | SA WG2 | Rel-19 | Revision of S2-2500430r03. Approved | Approved | |
| 19.14.1 | S2-2500937 | LS OUT | Approval | [DRAFT] LS on further SA WG2 Ambient IoT TR conclusion update | Huawei, HiSilicon | Rel-19 | CC#4: r07 + changes agreed. Revised in CC#4 to S2-2501343. | Dongjoo (Nokia) asked if this LS can be revised after the revision deadline to reflect the outcome of this meeting and provides comments . ==== General Revisions Deadline ==== Runze (Huawei) provides r01. Genadi (Lenovo) provides r02 with some suggestions. Robbie (Ericsson) provides r03. Sebastian (Qualcomm) provides r04 to remove the question on frequency bands; objects to earlier versions; (note that I created r04 as r03 was already on the server) Runze (huawei) agrees to Sebastian (Qualcomm) update. Lars (Sony) provides r05 and objects to earlier versions. Genadi (Lenovo) comments to Runze (Huawei) and Sebastian (Qualcomm). Genadi (Lenovo) doesn't agree to the r05 provided by Lars (Sony). Lars (Sony) responds to Genadi (Lenovo). Runze (Huawei) prefers r04, but can live with r05. ==== Comments Deadline ==== Xiaowan(vivo) | Revised |
| 19.14.1 | S2-2501343 | LS OUT | Approval | LS on SA2 Ambient IoT TR conclusion update | SA WG2 | Rel-19 | Revision of S2-2500937r07 + changes. This LS OUT was approved | Approved | |
| 19.14.1 | - | - | - | TR contributions | - | - | Docs:=0 | - | |
| 19.14.1 | - | - | - | EN: Whether and how AIOTF selects BS readers or AIOT RAN nodes in topology 1 needs coordination between SA2 and RAN WG(s) | - | - | Docs:=4 | - | |
| 19.14.1 | S2-2500333 | P-CR | Approval | 23.700-13: Removing one EN related to BS reader selection in KI#1. | China Mobile | Rel-19 | Email thread for discussion? r16 agreed. Revised in e-mail session to S2-2501243, merging S2-2500345 and S2-2500712 | Runze (Huawei) propose to use this mail thread to discuss EN' Whether and how AIOTF selects BS readers or AIOT RAN nodes in topology 1 needs coordination between SA2 and RAN WG(s)'. Dongjoo (Nokia) provides comments. Hao (ZTE) comments. Lars (Sony) Request r01 with correct formatting. Junan Peng( China Mobile) comments. Junan Peng (China Mobile) provides comments. Runze (Huawei) suggests Junan Peng (China Mobile) to provide r01 for checking. Steve (Huawei) provides our understanding of the pCR and asks for confirmation on approach Xiaowan(vivo) comments Robbie (Ericsson) agrees with Deng Qiang (CATT) and replies to Dongjoo (Nokia) Deng Qiang (CATT) comments on the RAN3 dependency. Dongjoo (Nokia) suggests a new wording. Robbie (Ericsson) comments on r04. Dongjoo (Nokia) provides r04. Fei (OPPO) comments and provides r03. Runze (Huawei)replies to Guanzhou (InterDigital). Junan Peng (China Mobile) replies to Guanzhou (InterDigital) comments Junan Peng (China Mobile) replies to Steve (Huawei) Junan Peng (China Mobile) provides r02 based on r01 with some updates Lars (Sony) provides r01 based on r00 with just corrected formatting Runze (Huawei) suggest wording to Dongjoo (Nokia). Runze (Huawei) replies to Deng Qiang (CATT). Dongjoo (Nokia) provides feedback to Runze (Huawei). Junan (China Mobile) provides feedback to Dongjoo(Nokia) and Runze (Huawei). Runze (Huawei) replies to Dongjoo (Nokia). Junan Peng (China Mobile) provides r05. Lars (Sony) provides r06. Fei (OPPO) comments on r06 Lars (Sony responds to Fei. Runze (Huawei) replies to Lars (Sony) and supports Fei (OPPO) comments on r06 Fei (OPPO) provided further clarification to Lars (Sony) Junan Peng (China Mobile) provides r07. Lars (Sony responds to Runze. Lars (Sony) don't agree with r07. Sebastian (Qualcomm) agrees with Lars (Sony) and is not ok with r07 Sang-Jun (Samsung) comments on r07 and r06. Junan Peng (China Mobile) replies to Lars (Sony) Junan Peng (China Mobile ) replies to Lars (Sony). Xiaowan(vivo) provides r08 Robbie (Ericsson) provides comments Robbie (Ericsson) is fine with r12 Junan Peng (China Mobile) provides r12 and replies Dongjoo (Nokia) asks a question on r11. Robbie (Ericsson) provides r11 and replies Xiaowan(vivo) replies Junan Peng (China Mobile) provides r10 to address concerns about the 'AIoT service area.' Guanzhou (InterDigital) questions the definition of 'AIoT service area'. Steve (Huawei) provides r09 for cleanup and returning tracked changes and comments in readers moving Lars (Sony) has strong concerns with r07 - r12. Junan Peng (China Mobile) replies to Lars (Sony). Junan Peng (China Mobile) replies to Lars (Sony), changing the AIOT service area to BS reader's service area. And provides r13 Runze (Huawei) replies to Lars (Sony) and suggest a way forward. Dongjoo (Nokia) commens on r13 Chunhui (NEC) supports r13 provided by Junan (China Mobile). Junan Peng (China Mobile ) replies to Dongjoo (Nokia) Lars (Sony) responds to Runze and Junan. Dongjoo (Nokia) replies to Junan (China Mobile) Runze (Huawei) replies to Lars (Sony). Junan Peng (China Mobile) replies to Nokia and provides r14 Xiaowan(vivo) provide r14 Junan Peng (China Mobile) is ok with r14 from vivo Junan Peng (China Mobile) replies to Doogjoo (Nokia) , and provides r15 based on r14 from vivo Lars (Sony) provides r16 Sebastian (Qualcomm) provides r17 ==== General Revisions Deadline ==== Junan Peng (China Mobile) can live with r16 and r17 on the condition of additional change: The OAM may configure the AIOTF with BS Reader information including e.g., their corresponding service area when the BS Readers are integrated in the network. Guanzhou (InterDigital) can live with r15 on the condition of additional change: 'For topology 1, NGAP is terminated at an AIOT RAN node, and an AIOT RAN node, supporting one or more BS readers, reports AIoT RAN's supported service area list (i.e. service area of the BS reader supported by the RAN)'. Sang-Jun (Samsung) proposes to go foward with Junan Peng (China Mobile)'s proposal with r17+changes. Dongjoo (Nokia) supports r17 without any further changes and can live with r16. Dongjoo (Nokia) supports r17. Robbie (Ericsson) supports r17 without additional change. Junan Peng (China Mobile) replies to Dongjoo(Nokia) and Lars (Sony) Runze (Huawei) prefers r16, and objects to r17 unless the EN is converted to NOTE. Runze (Huawei) replies to Guanzhou (Interdigital). Dongjoo (Nokia) supports r16 and r17. Lars (Sony) supports r16 and r17. Sebastian (Qualcomm) prefers r17 as is (no additions); can also live with r16 as is (no additions); objects to other versions Junan Peng (China Mobile) supports r16 Hao (ZTE) supports r16 and would like to co-sign the paper. Guanzhou (InterDigital) objects to r16 and r17. Lars (Sony) we could also go with r06 which does not have service area... Guanzhou (InterDigital) responds to Runze (Huawei). Runze (Huawei) replied to Guanzhou (InterDigital). Junan Peng (China Mobile) replies to Guangzhou (Interdigital). Junan Peng (China Mobile) responds to Guanzhou (InterDigital). Deng Qiang (CATT) supports r16 and would like to co-sign the paper. Guanzhou (InterDigital) further comments. ==== Comments Deadline ==== Runze (Huawei) proposes to go with r16, after offline checking. Guanzhou (InterDigital) can live with r16. | Revised |
| 19.14.1 | S2-2501243 | P-CR | Approval | 23.700-13: Removing one EN related to BS reader selection in KI#1. | China Mobile, Samsung, CATT, ZTE, NEC | Rel-19 | Revision of S2-2500333r16, merging S2-2500345 and S2-2500712. Approved | Approved | |
| 19.14.1 | S2-2500712 | P-CR | Approval | 23.700-13: Topic#2, Conclusions on AIoT KI#1 for Topology 1. | Samsung | Rel-19 | Merged into S2-2501243 | Runze (Huawei) propose to merge this paper into S2-2500333. Sang-Jun (Samsung) agrees to merge this paper into S2-2500333. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500345 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#1 . | Vivo | Rel-19 | Merged into S2-2501243 | Runze (Huawei) propose to merge this paper into S2-2500333. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | - | - | - | EN: How the aggregation can be done is FFS | - | - | Docs:=4 | - | |
| 19.14.1 | S2-2500428 | P-CR | Approval | 23.700-13: KI#1#3 Conclusion Update of Aggregation. | Ericsson | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500463. Robbie (Ericsson) is fine to merge this paper into S2-2500463. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500463 | P-CR | Approval | 23.700-13: Conclusions for KI#1 on the aggregation aspects (Topic#3). | Nokia | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to use this mail thread to discuss EN ''How the aggregation can be done is FFS'. Steve (Huawei) comments on the criteria Fei (OPPO) also support to make it as an implementation option Deng Qiang (CATT) shares similar view as Guanzhou (InterDigital) to make it an implementation option. Dongjoo(Nokia) provides feedback Robbie (Ericsson) asks for clarification Dongjoo(Nokia) provides r03 Runze (Huawei) replies to Hao (ZTE) and suggest to use r02 for further discussion. Runze (Huawei) provides r02. Hao (ZTE) provides comments. Xiaowan(vivo) request to define it as general as report control rather than aggregation control and provids r01 Guanzhou (InterDigital) comments and proposes to simplify the aggregation conclusion Robbie (Ericsson) provides some suggestions. Runze (Huawei) in principle supports Dongjoo(Nokia) and r03 Dongjoo(Nokia) asks for clarification on the comment from Runze (Huawei) Runze (Huawei) suggests Fei (OPPO) to provides a rev showing the aggregation can be implementation option Runze (Huawei) replies to Dongjoo(Nokia). Dongjoo(Nokia) provides r04 Sang-Jun (Samsung) comments on r05 Runze (Huawei) replies to Sang-Jun (Samsung) and LiZhuo (Lenovo), and has concern on the EN in r05. Walter (Philips) disagrees with r06 and r07 Dongjoo (Nokia) shares the same view as Walter (Philips) and disagrees with r06 and r07 Sang-Jun (Samsung) supports r08, and the service id Robbie (Ericsson) provides r09 Steve (Huawei) comments on r09 - looks like a good set of clarifications Fei (OPPO) asks questions on the service id LaeYoung (LGE) asks same Q about service id as Fei (OPPO) asked and additional Q, and has concern on wording 'control'. Dongjoo (Nokia) responses and provides r10 Steve (Huawei) comments on RAN vs Reader doing aggregation ==== General Revisions Deadline ==== Sang-Jun (Samsung) is fine with r11. ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500585 | P-CR | Approval | 23.700-13: KI#1 Addressing EN on AIoT service responses aggregation. | Lenovo, Futurewei, NEC | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500463. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500646 | P-CR | Approval | 23.700-13: Address EN for Aggregation. | ZTE | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500463. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.1 | - | - | - | EN: It is FFS whether to support any other messages besides Inventory Response, Command (e.g. Read and Write) Request and Response over AIoT Device NAS layer | - | - | Docs:=5 | - | |
| 19.14.1 | S2-2500970 | P-CR | Approval | 23.700-13: Conclusion update on messages over AIoT device NAS. | InterDigital Inc. | Rel-19 | Merged into S2-2501244 | Runze (Huawei) propose to merge this paper into S2-2500710. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500426 | P-CR | Approval | 23.700-13: KI#3 Conclusion Update of AIoT Device NAS Layer. | Ericsson | Rel-19 | Merged into S2-2501244 | Runze (Huawei) propose to merge this paper into S2-2500710. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500769 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs of Topic4. | HONOR | Rel-19 | Merged into S2-2501244 | Runze (Huawei) propose to merge this paper into S2-2500710. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500710 | P-CR | Approval | 23.700-13: Topic #4, Conclusions on AIoT KI#1 for Messages. | Samsung | Rel-19 | Email thread for discussion? r08 agreed. Revised in e-mail session to S2-2501244, merging S2-2500426, S2-2500769 and S2-2500970 | Runze (Huawei) propose to use this mail thread to discuss EN 'It is FFS whether to support any other messages besides Inventory Response, Command (e.g. Read and Write) Request and Response over AIoT Device NAS layer'. Fei (OPPO) comments. Dongjoo (Nokia) provides comments. Lars (Sony) provides r01. Xiaowan (vivo) provides r02. Robbie (Ericsson) replies to Dongjoo(Nokia) and clarifies to Runze (Huawei) Deng Qiang (CATT) comments Dongjoo(Nokia) asks questions Runze (Huawei) supports r02. Runze (Huawei) disagrees to r03 Robbie (Ericsson) provides r03 Fei (OPPO) responds to Guanzhou (Interdigital) Guanzhou (InterDigital) comments Steve (Huawei) comments Fei (OPPO) responds to Robbie (Ericsson). Robbie (Ericsson) replies to Fei (OPPO) Runze (Huawei) provides observation on the different comments and avoid confusion. Sang-Jun (Samsung) comments Deng Qiang (CATT) comments. Robbie (Ericsson) provides r04. Sebastian (Qualcomm) agrees with Robbie (Ericsson) but proposes to slightly rephrase NOTE X Lars (Sony) comments on r04. Robbie (Ericsson) provides r05. Fei (OPPO) responds to Robbie (Ericsson) and Deng Qiang (CATT). Robbie (Ericsson) provides r06 and comments Steve (Huawei) comments on paging message contents. Steve (Huawei) comments further Robbie (Ericsson) comments Steve (Huawei) comments again Henrik N (NTT DOCOMO) provides comments Fei (OPPO) shares the same view as Henrik (NTT DOCOMO) Robbie (Ericsson) provides r07 Henrik N (NTT DOCOMO) provides questions to Robbie (Ericsson) Steve (Huawei) asks a question about the note Robbie (Ericsson) replies to Henrik N (NTT DOCOMO) Robbie (Ericsson) replies to Steve (Huawei) Steve (Huawei) replies about EN -> unrelated NOTE conversion Fei (OPPO) provides comments on r07 and indicate that clause 8.3.4 has the similar EN which is converted to note in S2-2500925 Robbie (Ericsson) provides r08 ==== General Revisions Deadline ==== Sang-Jun (Samsung) is fine with r08 Xiaowan(vivo) is fine with r08 Lars (Sony) is ok with r08. ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501244 | P-CR | Approval | 23.700-13: Topic #4, Conclusions on AIoT KI#1 for Messages. | Samsung, Ericsson | Rel-19 | Revision of S2-2500710r08, merging S2-2500426, S2-2500769 and S2-2500970. Approved | Approved | |
| 19.14.1 | - | - | - | EN: How this AIOT device related information is used is FFS and Where to store the AIOT device related information is FFS | - | - | Docs:=5 | - | |
| 19.14.1 | S2-2500340 | P-CR | Approval | 23.700-13: Removing two ENs related to Ambient device-related context storage in KI#1. | China Mobile | Rel-19 | Merged into S2-2501245 | Runze (Huawei) propose to merge this paper into S2-2500586. Junan Peng (China Mobile) agrees to merge this paper into S2-2500586. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500464 | P-CR | Approval | 23.700-13: Conclusions for KI#1 on the device context info (Topic#5). | Nokia | Rel-19 | Merged into S2-2501245 | Runze (Huawei) propose to merge this paper into S2-2500586. Dongjoo (Nokia) agree to merge this paper into S2-2500586. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500586 | P-CR | Approval | 23.700-13: KI#1 Addressing EN on AIoT device related information. | Lenovo, China Telecom | Rel-19 | Email thread for discussion? r07 agreed. Revised in e-mail session to S2-2501245, merging S2-2500340, S2-2500464 and S2-2500969 | Runze (Huawei) propose to use this mail thread to discuss EN 'How this AIOT device related information is used is FFS and Where to store the AIOT device related information is FFS'. ==== General Revisions Deadline ==== Sang-Jun (Samsung) is fine with r07. Yinhui (NTT DOCOMO) would like to cosign r07. Junan Peng (China Mobile) would like to cosign r07. ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501245 | P-CR | Approval | 23.700-13: KI#1 Addressing EN on AIoT device related information. | Lenovo, China Telecom, Nokia, CMCC, NTT DOCOMO | Rel-19 | Revision of S2-2500586r07, merging S2-2500340, S2-2500464 and S2-2500969. Approved | Approved | |
| 19.14.1 | S2-2500969 | P-CR | Approval | 23.700-13: Conclusion update on AIoT context information. | InterDigital Inc. | Rel-19 | Merged into S2-2501245 | Runze (Huawei) propose to merge this paper into S2-2500586. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | - | - | - | EN: The length of Identifier is fixed or dynamical is FFS | - | - | Docs:=3 | - | |
| 19.14.1 | S2-2500346 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#2 . | Vivo | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501246, merging S2-2500711 | Runze (Huawei) propose to use this mail thread to discuss 'EN: The length of Identifier is fixed or dynamical is FFS'. Dongjoo (Nokia) provides comments. Xiaowan(vivo) replies to Dongjoo (Nokia) and provides r01. Lars (Sony) Comment on r01. Sang-Jun (Samsung) supports the comments from Lars (Sony). Sebastian (Qualcomm) comments and raises concerns on r00 and r01 Xiaowan(vivo) replies and provides r02 Steve (Huawei) comments Sebastian (Qualcomm) has issues with r02 Steve (Huawei) on supporting masking Sebastian (Qualcomm) replies to Steve Xiaowan(vivo) provide r03 ==== General Revisions Deadline ==== Sang-Jun (Samsung) is fine with r03 Sebastian (Qualcomm) can only be ok with r03 if NOTE2 is re-instated as an Editor's note; objects to other versions Xiaowan(vivo) replies to Sebastian (Qualcomm) Steve (Huawei) is ok with r03 as is. Xiaowan(vivo) for the progress, is OK with the request from Sebastian (Qualcomm): r03 + NOTE2 is re-instated as the pervious Editor's note Steve (Huawei) is also ok with the this approach from Xiaowan(vivo) ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501246 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#2 . | Vivo | Rel-19 | Revision of S2-2500346r03, merging S2-2500711. Approved | Approved | |
| 19.14.1 | S2-2500711 | P-CR | Approval | 23.700-13: Topic #7, Conclusions on AIoT KI#2 Device ID. | Samsung | Rel-19 | Email thread for discussion? Merged into S2-2501246 | Runze (Huawei) propose to merge this paper into S2-2500346. Sang-Jun (Samsung) agrees to merge this paper into S2-2500346. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | - | - | - | EN: Where to store the AIoT device subscription is FFS | - | - | Docs:=3 | - | |
| 19.14.1 | S2-2500465 | P-CR | Approval | 23.700-13: Conclusions for KI#2 on the device subscription-like info (Topic#10). | Nokia | Rel-19 | Merged into S2-2501247 | Runze (Huawei) propose to merge this paper into S2-2500973. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500973 | P-CR | Approval | 23.700-13: Clarification on storage of Ambient IoT related subscription data. | NTT DOCOMO, Deutsche Telekom, T-Mobile USA, Huawei, HiSilicon | Rel-19 | Email thread for discussion? r10 agreed. Revised in e-mail session to S2-2501247, merging S2-2500465 | Runze (Huawei) propose to use this mail thread to discuss EN 'Where to store the AIoT device subscription is FFS'. Dongjoo (Nokia) provides r01, merging S2-2500465 in. Fei (OPPO) asks question on r01 Dongjoo (Nokia) responses to Fei (OPPO). Qianghua (Huawei) comments and provides r02 Lars (Sony) ask clarification r01 and r02 Yinhui (NTT DOCOMO) comments and ask clarification on r01 and r02 Dongjoo (Nokia) provides r04 Xiaowan(vivo) privides r03 Steve (Huawei) comments on different UDR instances Sang-Jun (Samsung) provides r05 Dieter (Deutsche Telekom) asks some questions for clarification and comments Yinhui (NTT DOCOMO) provides r06. Sebastian (Qualcomm) asks a question Serge (T-Mobile USA) comments and provides R07 Qianghua (Huawei) comments on the term and suggest not to use 'AIoT static information' in r06, r07 Robbie (Ericsson) comments Qianghua (Huawei) provides r08 to revert the term Junan Peng(China Mobile) comments Dongjoo (Nokia) questions on r08. Yinhui (NTT DOCOMO) comments on r08. Dieter (Deutsche Telekom) answers to Dongjoo (Nokia). Dongjoo (Nokia) replies to Dieter (Deutsche Telekom). Steve (Huawei) comments on storing Yinhui (NTT DOCOMO) provides r09 Dieter (Deutsche Telekom) replies to Dongjoo (Nokia). Dongjoo (Nokia) thanks to Dieter (Deutsche Telekom) for the clarification and agrees with the view. Dongjoo (Nokia) provides r10 Robbie (Ericsson) replies to Dongjoo (Nokia) Yinhui (NTT DOCOMO) replies to Dongjoo(Nokia) ==== General Revisions Deadline ==== Robbie (Ericsson) prefers r09, and can live with r10 Dieter (Deutsche Telekom) prefers r10, and can live with r09. Sang-Jun (Samsung) can accept r10 or r09. Chunhui (NEC) can accept r10 or r09, and NEC would like to cosign this paper. Dongjoo (Nokia) replies to Dieter (Deutsche Telekom) and Robbie (Ericsson). ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501247 | P-CR | Approval | 23.700-13: Clarification on storage of Ambient IoT related subscription data. | NTT DOCOMO, Deutsche Telekom, T-Mobile USA, Huawei, HiSilicon, Nokia, NEC, Lenovo, Samsung | Rel-19 | Revision of S2-2500973r10, merging S2-2500465. Approved | Approved | |
| 19.14.1 | - | - | - | EN: It is FFS whether and how to support enabling temporarily disabled AIoT devices | - | - | Docs:=6 | - | |
| 19.14.1 | S2-2500374 | P-CR | Approval | 23.700-13: KI#3, Conclusion update on enabling temporarily disabled AIoT devices. | OPPO | Rel-19 | Email thread for discussion? r02 agreed. Revised in CC#4 to S2-2501333. | Jungshin (Samsung) proposed to discuss as baseline and merge S2-2500771, S2-2500853, S2-2500888, S2-2500351, S2-2500793, and S2-2500889 Fei (OPPO) responds to Robbie (Ericsson) Robbie (Ericsson) suggests using S2-2500425 as baseline Deng Qiang (CATT) comments Robbie (Ericsson) replies to Fei (OPPO) and Deng Qiang (CATT) Fei (OPPO) comments and proposes to have a SoH in CC#1. Dongjoo (Nokia) asks questions that need to be clarified before conducting a SoH. Fei (OPPO) responds to Dongjoo (Nokia) Dongjoo (Nokia) asks further questions to Fei (OPPO). Xiaowan(vivo) agree Dongjoo (Nokia) to clarify the question for SoH firstly. Fei (OPPO) clarify it a bit Sang-Jun (Samsung) comments that SA2 can decide to support this feature, with Category 2 work (with NOTE regarding RAN alignment). Lars (Sony) comments on the topic. Henrik N (NTT DOCOMO) comments on the topic. Junan Peng(China Mobile) comments on the topic. Junan Peng (China Mobile) asks Fei (OPPO) further questions. Guanzhou (InterDigital) comments. Robbie (Ericsson) provides further views Fei (OPPO) provided responses and views Lars (Sony) further observations and comments Steve (Huawei) a couple of observations based on the discussion Walter (Philips) provides views and comments on wording Sebastian (Qualcomm) comments that the proposed explicit indicator is not acceptable Robbie (Ericsson) asks Sebastian (Qualcomm) Robbie (Ericsson) provides S2-2500425r01 to change the explicit indicator from AS layer to NAS layer Yicong Liu (China Telecom) comments on the topic. Deng Qiang (CATT) didn't see an agreeable solution so far and asks not to develop solutions online, proposed to drop this feature in Rel-19. Junan Peng (China Mobile) strongly proposed to drop this feature in Rel-19. Sang-Jun (Samsung) proposes to support this feature in Rel-19, either by 0374 or by 0425. Xiaowan(vivo) comments that the feature is not realistic r19(for device1 only) and welcome it in r20 study for the other kind of deivice Yicong Liu (China Telecom) proposes to support this feature in the Rel-19 TR phase, either by 0374 or by 0425. Fei (OPPO) clarified a bit on the security aspects Henrik N (NTT DOCOMO) provides further comments and proposes a way forward Runze (Huawei) replies to Yicong Liu (China Telecom). ==== General Revisions Deadline ==== Fei (OPPO) indicated that no comments and suggestions received on how to improve the wording and no revisions had not yet been provided Yicong Liu (China Telecom) replies to Runze (Huawei). Guanzhou (InterDigital) can't accept the solution as is. Propose to postpone it. Lars (Sony) How about making the temp disabling and enabling optional (individual device)? Xiaowan(vivo) still technically concern about the temp disabling and enabling (individual device) and prefer not support it r19 Lars (Sony) responds to Xiaowan. Xiaowan(vivo) replies to Lars (Sony) and Fei (OPPO), and thinking two options 1) postpone and send LS 2) not support the feature Henrik N (NTT DOCOMO) provides r01 and proposes a way forward Sebastian (Qualcomm) prefers r00 but can live with r01 Huawei prefers r01 Xiaowan(vivo) support r01 and cannot live with r00 this meeting Hao (ZTE) is fine with r01. Lufeng Han (Spreadtrum) prefers r01. Fei (OPPO) is ok to go with r01 for the progress. Walter (Philips) is not ok with r01 and proposes r02 Henrik N (NTT DOCOMO) responds to Walter (Philips) and supports r02 Xiaowan(vivo) also ok with r02 Runze (Huawei) supports r02. Junan Peng(China Mobile ) is also okay with r02 Yicong Liu (China Telecom) is ok for both r00 and r02. Guanzhou (InterDigital) is OK with r02. Chunhui (NEC) is OK with r02. Hao (ZTE) is ok with either r01 or r02. Robbie (Ericsson) expresses strong concerns on not having temporarily enable/disable function to fulfil management requirement in TS 22.369 in Rel-19 which we believe is beneficial Hanyu (HONOR) is ok with r02. Deng Qiang (CATT) supports either r01or r02. ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501333 | P-CR | Approval | 23.700-13: KI#3, Conclusion update on enabling temporarily disabled AIoT devices. | OPPO | Rel-19 | Revision of S2-2500374r02. This P-CR was approved | Approved | |
| 19.14.1 | S2-2500425 | P-CR | Approval | 23.700-13: KI#3 Conclusion Update of Enabling Temporarily Disabled AIoT devices. | Ericsson | Rel-19 | Noted in e-mail session | Robbie (Ericsson) provides r01 to change the explicit indicator from AS layer to NAS layer ==== General Revisions Deadline ==== Guanzhou (InterDigital) can't accept the solution as is. Propose to postpone it. Lars (Sony) Propose to Note this paper. Xiaowan(vivo) share the same view with Lars (Sony) and think there will be better way to handle the device better capability in r20 ==== Comments Deadline ==== | Noted |
| 19.14.1 | S2-2500968 | P-CR | Approval | 23.700-13: Conclusion update for enabling temporarily disabled AIoT device. | InterDigital Inc. | Rel-19 | Merged into S2-2501248 | Sang-Jun (Samsung) proposes to note 0968 or merge 0968 into 0347 ==== General Revisions Deadline ==== Sang-Jun (Samsung) proposes to note 0968 as discussions are going on 0374 ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500347 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#3 . | Vivo | Rel-19 | r02 agreed. Revised in e-mail session to S2-2501248, merging S2-2500968 | Lars (Sony) provides r01. Lars (Sony) provides r02. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501248 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#3 . | Vivo | Rel-19 | Revision of S2-2500347r02, merging S2-2500968. Approved | Approved | |
| 19.14.1 | - | - | - | EN: If the “command-only” case applies, pending SA3, if a command and paging can be performed in a single operation, then an AIoT specific NAS message may be included in the request | - | - | Docs:=2 | - | |
| 19.14.1 | S2-2500647 | P-CR | Approval | 23.700-13: Address EN Regarding Command-only Service Operation. | ZTE | Rel-19 | Email thread for discussion r01 agreed. Revised in e-mail session to S2-2501249. | Dongjoo (Nokia) asks questions. Runze (Huawei) shared the same view as Dongjoo (Nokia). Lars (Sony) provides r01. Hao (ZTE) responds and provides r02. Runze (Huawei) supports the comments from Lars (Sony). Runze (Huawei) thanks Lars (Sony) and supports r01. Xiaowan(vivo) comments and provides r03 Lars (Sony) comments and is not ok with r02. Dongjoo(Nokia) asks questions and provides comments. Fei (OPPO) comments and provides r04 Runze (Huawei) replies to Dongjoo (Nokia). Runze (Huawei) replies to Fei (OPPO). Fei (OPPO) clarified that we are also ok with r01 provided by Lars. Xiaowan(vivo) replies to Dongjoo(Nokia) Hao (ZTE) provides comments. Sang-Jun (Samsung) provides summary and comments Lars (Sony) responds to Sang-Jun. Walter (Philips) disagrees with r01 and r04 Sang-Jun (Samsung) responds to Lars (Sony) Xiaowan(vivo) thanks Sang-Jun (Samsung)'s clarification and suggest to move forward with r01 Runze (Huawei) replies to Walter (Philips). Runze (Huawei) dislikes r04, because term 'command-only' causes misunderstanding. Walter (Philips) comments to Runze (Huawei) Henrik N (NTT DOCOMO) comments to Huawei and prefers r01 Lars (Sony) comment on Walter's comment. Deng Qiang (CATT) clarified command-only. Dieter (Deutsche Telekom) comments and prefers r01 Steve (Huawei) comments on 'command-only', r01 is ok and clear when reading the complete procedure Guanzhou (InterDigital) comments. Walter (Philips) provides revision r05 Sang-Jun (Samsung) asks Walter (Philips) on r05 Runze (Huawei) suggests Walter (Philips) to re-consider the position Runze (huawei) comments on r05 Walter (Philips) clarifies to Runze (Huawei) and Sang-Jun (Samsung) Dongjoo (Nokia) sympathizes with Walter (Philips) but suggests not supporting the command-only case in R19. ==== General Revisions Deadline ==== Walter (Philips) provides (r06 and) r07 Runze (Huawei) thanks Walter (Philips) for the compromise. Fei (OPPO) replied to Guanzhou (InterDigital) Guanzhou (InterDigital) questions r05/r06/r07. Runze (Huawei) replies to Guanzhou (InterDigital) Xiaowan(vivo) agree r01 and thinks the other revisions and original version are not suitable Lars (Sony) propose to go with r01. Walter (Philips) replies to Guanzhou (InterDigital) and Lars (Sony) Sang-Jun (Samsung) proposes to postpone the paper. Sebastian (Qualcomm) is ok with r01, objects to other versions Runze (Huawei) disagrees to postpone the paper and proposes to approve r01. Hao (ZTE) proposes to go with R01. Dongjoo (Nokia) is okay with R01. Fei (OPPO) also supports r01. Robbie (Ericsson) is OK with r01 Walter (Philips) prefers r05 or r07, but will not object to r01 ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501249 | P-CR | Approval | 23.700-13: Address EN Regarding Command-only Service Operation. | ZTE | Rel-19 | Revision of S2-2500647r01. Approved | Approved | |
| 19.14.1 | - | - | - | Category 2 editor’ notes | - | - | Docs:=7 | - | |
| 19.14.1 | S2-2500925 | P-CR | Approval | 23.700-13: Editor s Notes resolutions during the normative phase or future releases (Cat-2 & Cat-3 ENs). | Huawei, HiSilicon | Rel-19 | Email thread for discussion. Focus on only category 2 EN r02 agreed. Revised in e-mail session to S2-2501250, merging S2-2500328 and S2-2500339 | Robbie (Ericsson) provides comments. Runze (Huawei) clarifies the paper content and potential handling. Dongjoo (Nokia) requests to revise this contribution to make it agreeable. Henrik N (NTT DOCOMO) disagrees with Nokia on authorization aspect and provides comments Guanzhou (InterDigital) questions about 'Notify' service Runze (Huawei) replies to Robbie (Ericsson) Runze (Huawei) provides r01. Lars (Sony) ask for a r02 with no overlap to other threads. Robbie (Ericsson) replies to Runze (Huawei). Runze (Huawei) agrees with Lars (Sony). Fei (OPPO) replied to Robbie (Ericsson) and Dongjoo (Nokia) Dongjoo (Nokia) provides feedback to Runze (Huawei). Xiaowan(vivo) suggests Runze (Huawei) replies to Dongjoo (Nokia) and asks for realistic action to take. Lars (Sony) reacts on Fei's suggestion. Runze (Huawei) replies to Lars (Sony). Runze (Huawei) replies to Dongjoo (Nokia). Sang-Jun (Samsung) provides comments Deng Qiang (CATT) suggests to convert this EN to NOTE and resolve this together with SA3 in normative phase. Also suggest to apply this rule to all ENs with other WGs dependencies. Junan Peng (China Mobile) provides comments to Ericsson and Nokia. Henrik N (NTT DOCOMO) provides further comments to Ericsson and Nokia Dongjoo (Nokia) responses to Runze (Huawei) Runze (Huawei) replies to Robbie (Ericsson). Dongjoo (Nokia) reminds us of the SA plenary guidance that normative work should focus only on aspects that have already been concluded. Lars (Sony) ask Robbie to check SA3 TR for technical details on temp ID solutions. Runze (Huawei) provides r02 and replies to Lars (Sony). Dongjoo (Nokia) objects all revisions and the original version as our comment has not been addressed. Runze (Huawei) replies to Dongjoo (Nokia), and we must not delay the progress. Dongjoo (Nokia) maintains the position. ==== General Revisions Deadline ==== Steve (Huawei) comments, provides r03 with the requested change to help discussion. Robbie (Ericsson) takes the same position as Nokia to request to revert the NOTE 4 in clause 8.2.1 to EN. Sang-Jun (Samsung) points out that r03 already reverted the NOTE 4 in clause 8.2.1 to EN. Dongjoo (Nokia) suggests to go with r02 with a change to revert NOTE 4 in 8.1.1 back to the original EN, otherwise we object this paper. Runze (Huawei) proposed a way forward, accept r02 + the change that 'reverted the NOTE 4 in clause 8.2.1 to EN.' Dongjoo (Nokia) agrees with the way forward proposed by Runze (Huawei). Sebastian (Qualcomm) is ok with r02 + 'the change that 'reverted the NOTE 4 in clause 8.2.1 to EN' only if also NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. how the AIOT-RAN identifies the appropriate AMF to which to forward UL messages); details will be determined during normative work' Robbie (Ericsson) is OK with r02 + the change that 'reverted the NOTE 4 in clause 8.2.1 to EN.' as suggested by Runze (Huawei) Dieter (Deutsche Telekom) is NOT OK with the NOTE 4, even if turned into EN. Propose to keep original EN. Lars (Sony) can live with r02 IF all proposals to convert EN to NOTE related to ID protection are reverted back to ENs. Those are found in clauses 8.1.1, 8.2.1 and 8.3.4 Runze (Huawei) propose to approve r02 + 'the change that 'reverted the NOTE 4 in clause 8.2.1 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Dieter (Deutsche Telekom) asks Runze for clarification on the proposed way forward. Dieter (Deutsche Telekom) objects to all versions of this pCR. Dieter (Deutsche Telekom) can live with r02 if 1. all proposals to convert EN to NOTE related to ID protection are reverted back to ENs. Those are found in clauses 8.1.1, 8.2.1 and 8.3.4 AND 2. original EN is reverted back to 'Editor's note: Whether and how the A-IoT Device Identification information will be security protected will be concluded by SA WG3. AND 3. And no addition of any NOTE or EN for privacy and security as being proposed instead or additionally, e.g. like NOTE4 Runze (Huawei) replied to Dieter (Deutsche Telekom) and kindly ask to reconsider. Runze (Huawei) proposes to Dieter (Deutsche Telekom) to accept the r02+ 'the change that 'reverted the NOTE 4 in clause 8.2.1 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Lars (Sony) ask Runze whether he is considering our comment on r02? ==== Comments Deadline ==== Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' Runze (Huawei) proposes to accept the r02+ 'reverted the ID protection related EN in clause 8.1.1, 8.2.1 and 8.3.4 to EN' + NOTE 5 in clause 8.1.2.3 is changed to 'NOTE 5: UL traffic is routed based on an AIoT correlation identifier (i.e. AIOT-RAN identifies the appropriate AMF to which to forward UL messages base on the association between AIoT correction identifier and the AMF); details will be determined during normative work' | Revised |
| 19.14.1 | S2-2501250 | P-CR | Approval | 23.700-13: Editor s Notes resolutions during the normative phase or future releases (Cat-2 & Cat-3 ENs). | Huawei, HiSilicon | Rel-19 | Revision of S2-2500925r02, merging S2-2500328 and S2-2500339. Approved | Approved | |
| 19.14.1 | S2-2500328 | P-CR | Approval | 23.700-13: Resolution of Editor s notes with other WGs dependencies. | CATT | Rel-19 | Merge into 2500925? Merged into S2-2501250 | Runze (Huawei) propose to merge this paper into S2- 2500925. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500545 | P-CR | Approval | 23.700-13: KI#1, Resolving ENs on AIoT assistance information. | Lenovo | Rel-19 | Discussion using email thread 0798? Merged into S2-2501251 | Runze (Huawei) propose to merge this paper into S2-2500798. Genadi (Lenovo) agrees with the rapporteur Runze (Huawei) proposal to merge this paper into S2-2500798. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | S2-2500798 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs about assistance information (Cat 2). | HONOR | Rel-19 | Email thread for discussion? Focus on EN ‘AIoT assistance information’ r05 agreed. Revised in e-mail session to S2-2501251, merging S2-2500545 | Hanyu Ding (HONOR) provides S2-2500798r01 by merging S2-2500545 (Lenovo). Lars (Sony) provides r02. Genadi (Lenovo) is OK with the provided S2-2500798r01 by Hanyu Ding (HONOR). Xiaowan(vivo) share the same view with Lars (Sony). LaeYoung (LGE) share the same view on Frequency Band with Xiaowan(vivo). Hanyu Ding (HONOR) provides comments to r02. Deng Qiang (CATT) also think FB should wait for RAN conclusion. Fei (OPPO) comments on the FB Lars (Sony) responds to Hanyu Ding. Sang-Jun (Samsung) also thinks FB should wait for RAN conclusion. Hanyu Ding (HONOR) provides r03 based on comments. Lars (Sony) r03 looks good. Genadi (Lenovo) comments on the FB. Dongjoo (Nokia) ask a question on the FB. Runze (Huawei) replies to Dongjoo (Nokia) and explains where we are now. Hanyu(HONOR) provides r04, agrees with Genadi(Lenovo) and Runze (Huawei). Dongjoo (Nokia) is fine with r04 and would like to co-sign. Hanyu (HONOR) provides r05 by adding Nokia as the co-signer. ==== General Revisions Deadline ==== Lars (Sony) we are ok with r05. Sang-Jun (Samsung) is fine with r05. Sebastian (Qualcomm) is ok with r05; objects to other versions ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501251 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs about assistance information (Cat 2). | HONOR, Nokia | Rel-19 | Revision of S2-2500798r05, merging S2-2500545. Approved | Approved | |
| 19.14.1 | S2-2500339 | P-CR | Approval | 23.700-13: Removing one EN related to How addressing works for UP traffic via AMF in KI#1. | China Mobile | Rel-19 | Merge into 2500925? Merged into S2-2501250 | Runze (Huawei) propose to merge this paper into S2-2500925. Junan Peng (China Mobile) agrees to merge this paper into S2-2500925. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.1 | - | - | - | Category 3 editor’ notes | - | - | Docs:=2 | - | |
| 19.14.1 | S2-2500375 | P-CR | Approval | 23.700-13: T2 conclusion clarification. | OPPO | Rel-19 | Email thread for discussion r02 agreed. Revised in e-mail session to S2-2501252. | Robbie (Ericsson) provides r01 Genadi (Lenovo) provides r02. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.14.1 | S2-2501252 | P-CR | Approval | 23.700-13: T2 conclusion clarification. | OPPO | Rel-19 | Revision of S2-2500375r02. Approved | Approved | |
| 19.14.1 | - | - | - | Contributions exceeding TU | - | - | Docs:=12 | - | |
| 19.14.1 | S2-2500338 | P-CR | Approval | 23.700-13: Conclusions on the KI#1 general part correcting NGAP description. | China Mobile | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500542 | P-CR | Approval | 23.700-13: KI#1, Nx transport layer association establishment in Topology 1. | Lenovo | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500713 | P-CR | Approval | 23.700-13: Topic #10, Conclusions on AIoT KI#2 for Subscription Management. | Samsung | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500720 | P-CR | Approval | 23.700-13: Topic #9, Conclusions on AIoT KI#3 for Command-only. | Samsung | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500721 | P-CR | Approval | 23.700-13: Topic #5, Conclusions on AIoT KI#1 for AIoT Device related Information. | Samsung | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500722 | P-CR | Approval | 23.700-13: Topic #3, Conclusions on AIoT KI#1 for aggregation. | Samsung | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500788 | P-CR | Approval | 23.700-13: KI#3 Conclusion update in clause 8.3.4. | HONOR | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500427 | P-CR | Approval | 23.700-13: KI#2 Conclusion Update of Device Subscription Data. | Ericsson | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500546 | P-CR | Approval | 23.700-13: KI#1, Document the cease of progress on Topology 2. | Lenovo | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500714 | P-CR | Approval | 23.700-13: Topic #8, Conclusions on AIoT KI#3 for enabling temporarily disabled AIoT devices . | Samsung | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500933 | P-CR | Approval | 23.700-13: Editor s Notes resolutions in the TR (Cat-1 ENs). | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.14.1 | S2-2500751 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs of Topic5. | HONOR | Rel-19 | Not Handled | - | |
| 19.14.2 | - | - | - | Architecture support of Ambient power-enabled Internet of Things (AmbientIoT) | - | - | Docs:=47 | - | |
| 19.14.2 | - | - | - | Contributions to be handled | - | - | Docs:=37 | - | |
| 19.14.2 | S2-2500378 | OTHER | Approval | Reference, Term and Abbreviations. | OPPO | Rel-19 | Baseline paper of clause 2, clause 3 r01 agreed. Revised in e-mail session to S2-2501253. | Lars (Sony) provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501253 | OTHER | Approval | Reference, Term and Abbreviations. | OPPO | Rel-19 | Revision of S2-2500378r01. Approved | Approved | |
| 19.14.2 | S2-2500379 | OTHER | Approval | NF description for AIoT. | OPPO | Rel-19 | Noted in e-mail session | Xiaowan(vivo) provides r02 Junan Peng(China Mobile) provided S2-2500379r01. Steve (Huawei) comments Sebastian (Qualcomm) comments that this requires more work Fei (OPPO) provides r03 Dongjoo (Nokia) provides r04 LaeYoung (LGE) asks a Q about aggregation and has concern on wording 'aggregation control information'. Genadi (Lenovo) provides r05 and comments to AIoT Reader vs. AIoT RAN. Dongjoo (Nokia) provides r06 ==== General Revisions Deadline ==== LaeYoung (LGE) CANNOT accept r06 due to wording aggregation *control* information Dongjoo (Nokia) suggests to approve r06 + changing 'control' to 'assistance' which is occurring three times. LaeYoung (LGE) is fine with suggestion from Dongjoo (Nokia), i.e. r06 + changing 'control' to 'assistance' which is occurring three times. Sebastian (Qualcomm) objects to all versions Fei (OPPO) suggests to go with r03 with updated EN in clause 4.5.2 'Editor's note: Whether to reuse exiting specifications or use a new specification will be decided later by RAN WGs. It is FFS whether to specify the relationship between AIoT RAN and AIoT Reader and which term to use in this TS. ' ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500466 | OTHER | Approval | PCR for KI#1 on the aggregation aspects (Topic#3). | Nokia | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500379. Dongjoo (Nokia) agree to merge this paper into S2-2500379. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500467 | OTHER | Approval | PCR for KI#1 on the device context info (Topic#5). | Nokia | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500379. Dongjoo (Nokia) agree to merge this paper into S2-2500379. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500468 | OTHER | Approval | PCR for KI#2 on the device subscription-like info (Topic#10). | Nokia | Rel-19 | Postponed in e-mail session | Sebastian (Qualcomm) strongly proposes to postpone Dongjoo (Nokia) agree to postpone this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.14.2 | S2-2500469 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | CATT | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500964. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500470 | OTHER | Approval | PCR to TS 23.xyz: Assistance Information used by AIoT RAN. | CATT | Rel-19 | Baseline paper of clause 5.4 ‘Assistance Information used by AIoT RAN’ r03 agreed. Revised in e-mail session to S2-2501254, merging S2-2500966 | Hao (ZTE) provides r01 merging content from S2-2500643 (ZTE) and co-signs the paper. Sang-Jun (Samsung) provides r02 and co-signs the paper. Lars (Sony) provides r03. Dongjoo (Nokia) is fine with r03 and would like to co-sign. ==== General Revisions Deadline ==== Sebastian (Qualcomm) is ok with r03 ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501254 | OTHER | Approval | PCR to TS 23.xyz: Assistance Information used by AIoT RAN. | CATT, ZTE, Samsung, Nokia | Rel-19 | Revision of S2-2500470r03, merging S2-2500966. Approved | Approved | |
| 19.14.2 | S2-2500477 | OTHER | Approval | PCR to TS 23.xyz: AIoT device Identifiers. | Vivo | Rel-19 | Postponed in e-mail session | Sebastian (Qualcomm) proposes to postpone Henrik N (NTT DOCOMO) provides r01 merging in S2-2500987 and comments Xiaowan(vivo) provided r02 replies to Sebastian (Qualcomm) Sang-Jun (Samsung) supports r02. Dieter (Deutsche Telekom) provides r03 and asks a question for clarification. Henrik N (NTT DOCOMO) provides r04 and comments Dongjoo (Nokia) has the same question as Henrik (NTT DOCOMO) does. What is the reason for removing 'in 5G system'? Xiaowan(vivo) replies and provide r05 ==== General Revisions Deadline ==== Sang-Jun (Samsung) can accept r05 Sebastian (Qualcomm) prefers to postpone the pCR (objects to prevent unwanted approval). Henrik N (NTT DOCOMO) asks Sebastian (Qualcomm) for clarifications ==== Comments Deadline ==== | Postponed |
| 19.14.2 | S2-2500481 | OTHER | Approval | PCR to TS 23.xyz: NFs Services. | Vivo | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500964. Sang-Jun (Samsung) asks for clarification whether Runze (Huawei)'s proposal is to merge this paper into S2-2500931, not S2-2500964. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500486 | OTHER | Approval | AIoT T1 Protocol Stack. | OPPO | Rel-19 | Baseline paper of clause 4.6.2 ‘Protocol Stack between Ambient IoT Device and AIOTF’ r04 agreed. Revised in e-mail session to S2-2501255. | Xiaowan (vivo) provides r01. Sebastian (Qualcomm) comments Lars (Sony) comments Changhong (OPPO) comments on r01. Steve (Huawei) provides r02 Lars (Sony) comments on r02 Dongjoo (Nokia) ask questions for clarification Sang-Jun (Samsung) asks Xiaowan(vivo) if r03 resolves the issues Xiaowan(vivo) replies we need a protocol stack in the view of AIoT device, in the view of AIoT device, only reader, not RAN Fei (OPPO) provides r03 Guanzhou (InterDigital) comments Dongjoo (Nokia) cannot accept r03 and proposes to postpone the paper if the raised questions cannot be clarified. Fei (OPPO) replied to Dongjoo (Nokia) and provided r04 Guanzhou (InterDigital) responds to Xiaowan (Vivo) ==== General Revisions Deadline ==== Dongjoo (Nokia) accepts r04. ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501255 | OTHER | Approval | AIoT T1 Protocol Stack. | OPPO, vivo | Rel-19 | Revision of S2-2500486r04. Approved | Approved | |
| 19.14.2 | S2-2500520 | OTHER | Approval | AMF Services for Ambient IoT service. | China Mobile | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500931. Junan Peng (China Mobile) agrees to merge this paper into S2-2500931. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 19.14.2 | S2-2500521 | OTHER | Approval | AMF function enhancement for Ambient IoT service. | China Mobile | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500379. Junan Peng (China Mobile) agrees to merge this paper into S2-2500379. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 19.14.2 | S2-2500522 | OTHER | Approval | Reader selection for Ambient IoT service request. | China Mobile | Postponed in e-mail session | Xiaowan(vivo) question whether postpone this paper? Runze (Huawei) replies to Xiaowan(vivo). Sebastian (Qualcomm) strongly suggests to postpone so that we can finish the discussion in the TR first Junan Peng (China Mobile) suggests postponing so that we can finish the discussion in the TR first ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed | |
| 19.14.2 | S2-2500642 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | ZTE | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500964. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500643 | OTHER | Approval | PCR to TS 23.xyz: Assistance Information Used by AIoT RAN. | ZTE | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500470. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500645 | OTHER | Approval | PCR to TS 23.xyz: AIoT Reader Selection. | ZTE | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500522. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500661 | OTHER | Approval | PCR to TS 23.xyz: Network Functions: AIOTF and AIOTDMF. | Vivo | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper partially into S2-2500379, and partially into S2-2500468. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500734 | OTHER | Approval | PCR to TS 23.xyz: NEF Services. | Samsung | Rel-19 | Postponed in e-mail session | Xiaowan (vivo) comments and provides r01. Qianghua (Huawei) ok to have NEF services in this doc, but this should align with other exposures service (number of service operations, parameters) in 0931 later Sang-Jun (Samsung) provides r02. ==== General Revisions Deadline ==== Lars (Sony) Suggest to postpone this document. Robbie (Ericsson) suggests to postpone this document Sebastian (Qualcomm) suggests to postpone ==== Comments Deadline ==== | Postponed |
| 19.14.2 | S2-2500735 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | Samsung | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500470. Sang-Jun (Samsung) agrees to merge S2-2500735 into S2-2500470. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500742 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | Samsung | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500964. Sang-Jun (Samsung) agrees to to merge this paper into S2-2500964. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500851 | OTHER | Approval | PCR to TS 23.xyz: AIoT Device entity. | Spreadtrum, UNISOC | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500379. Lufeng Han (Spreadtrum) agrees to merge this paper into S2-2500379. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500852 | OTHER | Approval | PCR to TS 23.xyz: AIoTF entity. | Spreadtrum, UNISOC | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500379. Lufeng Han (Spreadtrum) agrees to merge this paper into S2-2500379. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500931 | OTHER | Approval | PCR to TS 23.xyz: Network Functions Services. | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Xiaowan (vivo) provides r01. Qianghua (Huawei) provides replies to justify the proposal of separate new AMF ambient data transfer service, and prefer option 1 for AIoT exposure Services Fei (OPPO) comments Hao (ZTE) provides comments. Junan Peng (China Mobile) provides comments to the AMF part Xiaowan(vivo) replies Qianghua (Huawei) replies and provides r02 Sebastian (Qualcomm) comments that this paper has many details which have not been defined yet and/or that we are still discussing in the TR; suggests to postpone Lars (Sony) propose to postpone this document. Qianghua (Huawei) clarifies that the details parameters are almost from TR conclusion Dongjoo (Nokia) also suggests to postpone this paper. Xiaowan(vivo) replies to Qianghua (Huawei) ==== General Revisions Deadline ==== Lars (Sony) Suggest to postpone this document. Sebastian (Qualcomm) also suggests to postpone ==== Comments Deadline ==== | Postponed |
| 19.14.2 | S2-2500932 | OTHER | Approval | PCR to TS 23.xyz: Subscription Management for Ambient IoT Device. | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Xiaowan(vivo) comment and provides r01 Sebastian (Qualcomm) comments that it does not make sense to agree on TS changes on subscription storage while we are still debating the same concept for the TR; proposes to postpone the paper ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.14.2 | S2-2500935 | OTHER | Approval | TS skeleton of Ambient IoT specification. | Huawei, HiSilicon | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501256. | Dongjoo(Nokia) requests for a revision Sang-Jun (Samsung) requests for a revision Runze (Huawei) provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501256 | OTHER | Approval | TS skeleton of Ambient IoT specification. | Huawei, HiSilicon | Rel-19 | Revision of S2-2500935r01. Approved | Approved | |
| 19.14.2 | S2-2500936 | OTHER | Approval | PCR to TS 23.xyz: scope of Ambient IoT Specification. | Huawei, HiSilicon | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501257. | Dongjoo(Nokia) requests for a revision Steve (Huawei) provides r01 ==== General Revisions Deadline ==== Robbie (Ericsson) asks to remove 2nd paragraph Robbie (Ericsson) is OK with r01 + remove 2nd paragraph Steve (Huawei) is ok with r01 + removing 2nd paragraph ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501257 | OTHER | Approval | PCR to TS 23.xyz: scope of Ambient IoT Specification. | Huawei, HiSilicon | Rel-19 | Revision of S2-2500936r01. Approved | Approved | |
| 19.14.2 | S2-2500939 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Architecture model and concepts. | Huawei, HiSilicon | Rel-19 | Baseline paper of clause 4.1-4.4 r03 agreed. Revised in e-mail session to S2-2501258. | Sebastian (Qualcomm) objects and comments that this pCR is not ready for inclusion into the TS yet Steve (Huawei) provides r01 Steve (Huawei) provides r02 Dongjoo (Nokia) provides comments Steve (Huawei) replies to Dongjoo (Nokia) Lars (Sony comment on r02 Dongjoo (Nokia) provides feedback to Steve (Huawei) Xiaowan(vivo) replies Steve (Huawei) on Readers in RAN. Steve (Huawei) comments on EN suggestion Fei (OPPO) comments Xiaowan(vivo) comments Steve (Huawei) provides r03 ==== General Revisions Deadline ==== Sebastian (Qualcomm) is ok with r03 Dongjoo (Nokia) is okay with r03 Fei (OPPO) ok with r03 Robbie (Ericsson) is okay with r03 + take out clause 4.2.1 + remove 'Utilising Ambient IoT Reader functionality in RAN.' in clause 4.1 Steve (Huawei) is ok with r03 without 'Utilising Ambient IoT Reader functionality in RAN.' in clause 4.1, checks about 4.2.1 Robbie (Ericsson) explains to Steve (Huawei) Steve (Huawei) can live with r03 without 'Utilising Ambient IoT Reader functionality in RAN.' in clause 4.1 and removing content in clause 4.2.1. ==== Comments Deadline ==== | Revised |
| 19.14.2 | S2-2501258 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Architecture model and concepts. | Huawei, HiSilicon | Rel-19 | Revision of S2-2500939r03. Approved | Approved | |
| 19.14.2 | S2-2500964 | OTHER | Approval | Ambient IoT Services. | InterDigital Inc. | Postponed in e-mail session | Hao (ZTE) provides comments. Xiaowan(vivo) comment and provides r01 Guanzhou (InterDigital) respond to Hao(ZTE) comments. Hao (ZTE) provides r02. Robbie (Ericsson) asks questions Sebastian (Qualcomm) comments and suggests to postpone the paper Xiaowan(vivo) replies to Robbie (Ericsson) Guanzhou (InterDigital) respond to Robbie(Ericsson) questions and provides r03. Xiaowan(vivo) replies to Sebastian (Qualcomm) Dongjoo (Nokia) shares the view from Sebastian (Qualcomm) and propose to postpone the paper Walter (Philips) requests clarification Guanzhou (InterDigital) responds to Walter (Philips) questions. ==== General Revisions Deadline ==== Walter (Philips) provides r05 Guanzhou (InterDigital) comments on r05. ==== Comments Deadline ==== | Postponed | |
| 19.14.2 | S2-2500965 | OTHER | Approval | Ambient IoT Reader Selection. | InterDigital Inc. | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500522. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | S2-2500966 | OTHER | Approval | Assistance information for AIoT RAN. | InterDigital Inc. | Rel-19 | Merge into S2-2500470? Merged into S2-2501254 | Runze (Huawei) propose to merge this paper into S2-2500470. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.14.2 | S2-2500987 | OTHER | Approval | PCR to TS 23.xyz: Text on permanent Ambient IoT Identifiers. | NTT DOCOMO, Deutsche Telekom, T-Mobile USA | Rel-19 | Noted in e-mail session | Runze (Huawei) propose to merge this paper into S2-2500477. Henrik N (NTT DOCOMO) agrees to merger proposal provided by Huawei ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.14.2 | - | - | - | Contributions exceeding TU | - | - | Docs:=10 | - | |
| 19.14.2 | S2-2500478 | OTHER | Approval | PCR to TS 23.xyz: Protocol Stacks. | Vivo | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500479 | OTHER | Approval | PCR to TS 23.xyz: Procedure for inventory. | Vivo | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500480 | OTHER | Approval | PCR to TS 23.xyz: Procedure for inventory. | Vivo | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500644 | OTHER | Approval | PCR to TS 23.xyz: NEF Services. | ZTE | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500926 | OTHER | Approval | PCR for TS 23.xyz: Ambient IoT Device Identifier. | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500927 | OTHER | Approval | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500928 | OTHER | Approval | PCR to TS 23.xyz: Procedure for Ambient IoT Command Service. | Huawei, HiSilicon | Rel-19 | Not Handled | Henrik N (NTT DOCOMO) comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | - |
| 19.14.2 | S2-2500929 | OTHER | Approval | PCR to TS 23.xyz: Procedures for AIOTF and AIoT Reader Communication. | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500930 | OTHER | Approval | PCR to TS 23.xyz: AF Authorization for Ambient IoT Services. | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.14.2 | S2-2500940 | DRAFTCR | Approval | Ambient IoT interfaces and reference points | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.1 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (FS_AIML_CN) | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (AIML_CN) | - | - | Docs:=168 | - | |
| 19.15.2 | - | - | - | KI#1: AIML support for LMF positioning | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | Liaisons | - | - | Docs:=5 | - | |
| 19.15.2 | S2-2500005 | LS In | Information | LS from RAN WG1: Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | RAN WG1 (R1-2405578) | Postponed in e-mail session | Haiyang (Huawei) proposes to note the LS IN and wait for RAN(2) progress. David (Apple) comments, LS out is needed. Yuang (ZTE) comments, this LS out is needed. | Postponed | |
| 19.15.2 | S2-2500200 | LS OUT | Approval | [DRAFT] LS to RAN on AIML positioning | vivo | Rel-19 | r10 agreedrevised in e-mail session to S2-2501133. | Yuang(ZTE) supports to send this LS out and keep RAN 1 in the loop. David (Apple) comments. Belen (Ericsson) asks Vivo whether this LS covers questions on case 2b Mehrdad (MediaTek Inc.) asks a question for clarification to understand the scope of the LS to RAN Vivian (vivo) provides r01. Zhao (Huawei) provides comments. Dimitris (Lenovo) is supportive to send an LS provides r02 David (Apple) comments and provides r03 Vivian (vivo) is fine with r03. Yuang(ZTW) supports r03. Belen(ericsson) provides r04 with questions to RAN1 and RAN2. Zhao (Huawei) provides r05. Thomas (Nokia) provides r06. Bahador (NTT DOCOMO) provides r07. David (Apple) provides r08. Hyesung (Samsung) provides r09. Vivian(vivo) provides r10. ==== General Revisions Deadline ==== Belen (Ericsson) is okay with r10. Dimitris (Lenovo) is ok with r10 Zhao (Huawei) is ok with r10. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501133 | LS OUT | Approval | LS on LMF-based AI/ML Positioning for Case 2b | SA WG2 | Rel-19 | Revision of S2-2500200r10. Approved | Approved | |
| 19.15.2 | S2-2500399 | LS OUT | Approval | [DRAFT] LS on LMF-based AI/ML Positioning | Ericsson | Rel-19 | CC#4: r09 + changes agreed. Revised in e-mail session to S2-2501341. | Yuang(ZTE) supports to send this LS out and keep RAN 1 in the loop. David (Apple) comments, one LS out only is preferred. Belen (Ericsson) provides r01 addressing ZTE comments. The conference call on AIML concluded that separate LSs would be fine. Zhao (Huawei) provides comments. Belen (Ericsson) replies to Zhao (Huawei) Vivian (vivo) provides r02 based on comments from Apple and Huawei Belen (Ericsson) is okay with r02 Thomas(Nokia) provides r03 to also capture ENs about input data and request related feedback. Objects against r00, r01 and r02 Xiaoyan (CATT) provides comments Belen (Ericsson) replies that we prefer to attach the CR. David (Apple) provides r04 and comments. Hyesung (Samsung) comments and asks questions. ==== General Revisions Deadline ==== David (Apple) provides r06, prefers r04 then apply corrections suggested by Samsung Belen (Ericsson) is okay with r06 Belen (Ericsson) corrects previous error [it is not David (Apple)] provides r06, prefers r04 then apply corrections suggested by Samsung Vivian(vivo) prefers r06, since if action is only for RAN3, then RAN1 and RAN2 should only be in CC list. David (Apple) is OK with r06. Xiaoyan (CATT) requests to remove the attachments from the LS, otherwise cannot accept r06 and other revisions. Belen (Ericsson) is okay with r06, and also provides r07 with no CR attached (references to 23.273) David (Apple) comments on r07, provides r08. Thomas(Nokia) provides r05, objects against r04 Belen (Ericsson) comments on r08 to remove 'noting that the content of those clauses is still under discussion in SA2' Xiaoyan (CATT) comments on r08 David (Apple) comments. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501341 | LS OUT | Approval | LS on LMF-based AI/ML Positioning for case 3b | SA WG2 | Rel-19 | Revision of S2-2500399r09 + changes. This LS OUT was approved | Approved | |
| 19.15.2 | - | - | - | TS 23.273: General | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500194 | CR | Approval | 23.273 CR0640 (Rel-19, 'F'): Adding missing parts for AI/ML based positioning | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | Merged into S2-2501136 | Xiaoyan (CATT) suggests marking this CR as merged into revision of S2-2500228. David (Apple) supports the proposal from CATT Xiaobo (vivo) also support to merging this into revision of S2-2500228, thanks. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2501017 | CR | Approval | 23.273 CR0666 (Rel-19, 'F'): Adapting the data collection procedure for performance monitoring | Xiaomi | Rel-19 | Check Affected Clauses! Merged into S2-2501138 | Sihan (vivo) provides comments Zhao (Huawei) suggests merging the change in clause 6.22.4 into S2-2500588. Xiaoyan (CATT) suggests marking this CR as merged into S2-2500832 and S2-2500834. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | - | - | - | TS 23.273: Data Exposure/ NWDAF Input data collection | - | - | Docs:=6 | - | |
| 19.15.2 | S2-2500352 | CR | Approval | 23.273 CR0644 (Rel-19, 'C'): Updates to data exposure service for AI/ML-based positioning | Apple | Rel-19 | Merge into S2-2500588? (similar proposed changes for LMF data exposure service operation). Overlap in LMF data exposure service operation Proposed merged with S2-2500588 (postponed). Postponed | Zhao (Huawei) provides comments and proposes to merge this CR into S2-2500588 per rapporteur's guidance. Yuang(ZTE) provides comments. Vivian (vivo) provides comments for this paper, and if this CR is merged to other one, then these comments are applicable there. David (Apple) is OK to merge this paper into S2-2500588 and continue the discussion there. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500588 | CR | Approval | 23.273 CR0650 (Rel-19, 'B'): Updates of input data collection from LMF | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Yuang(ZTE) Supports this CR. Vivian (vivo) proposes comments to this CR, and asks to consider our comments for S2-2500352 if it is merged to this paper. Zhao (Huawei) replies to Vivian (vivo). Jiahui (China Telecom) provides comments. Zhao (Huawei) replies to Jiahui (China Telecom). David (Apple) provides comments. Juan Zhang (Qualcomm) provides comment. Zhao (Huawei) replies to David (Apple) and Juan (Qualcomm) and provides r01. Vivian (vivo) provides comments. David (Apple) would like to co-sign Zhao (Huawei) replies, and proposes to merge S2-2500629 into this CR, and provides r02. Juan Zhang (Qualcomm) provides comments for r02. Thomas(Nokia) provides r03. Zhao (Huawei) replies to Juan (Qualcomm) and Thomas (Nokia). Belen (Ericsson) provides r04 (based on r02) as r03 is not available. Xiaoyan (CATT) provides r05 based on r04. Zhao (Huawei) replies to Xiaoyan (CATT) and provides r06 based on r04. Jiahui (China Telecom) prefers r04. Dimitris (Lenovo) is OK with PRU indication request clarification for the 'quality indication' Yuang(ZTE) objects r05, support r04 Zhao (Huawei) replies to Dimitris (Lenovo). Yuang(ZTE) objects r05, support r04, and provide comments Dimitris (Lenovo) comments on the quality part Juan Zhang (Qualcomm) provides comments for all the version with both highest label quality indication and quality indicationx Zhao (Huawei) replies to Dimitris (Lenovo) and Juan (Qualcomm) and provides r07 which removes the clashes with 0834. Zhao (Huawei) also provides r08 which merges 0834. Vivian (vivo) doesn't think it is good to merge at this late time without checking with Xiaoyan, but provides r09 in case this CR taken as baseline. ==== General Revisions Deadline ==== Dimitris (Lenovo) comments on r08 Yuang (ZTE) supports on r07 Juan Zhang (Qualcomm) proposes to postpone the CR Belen (Ericsson) proposes to postpone the CR Zhao (Huawei) replies to Belen (Ericsson). Dimitris (Lenovo) ok to postpone ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500834 | CR | Approval | 23.273 CR0658 (Rel-19, 'F'): Clarification on model performance monitoring for LMF-based AIML Positioning | CATT | Rel-19 | Postponed in e-mail session | Xiaoyan (CATT) provides r01. Vivian(vivo) provides comments, and asks to pay attention about the overlap with S2-2501018. Dimitris (Lenovo) comments Xiaoyan (CATT) replies to Vivian(vivo). David (Apple) provides comments. Xiaoyan (CATT) replies to David (Apple). Vivian (vivo) provides comments. Vivian (vivo) provides further comments. Zhao (Huawei) provides comments. David (Apple) comments and raises a concern Jianning (Xiaomi) provides comments Xiaobo (vivo) also share the view that clause titles should not be modified at this stage to avoid any possible inconsistency, thanks. Thomas(Nokia) raises concerns Also comments that there a still clashes with 588. Jianning (Xiaomi) provides comments and question for clarification. Zhao (Huawei) replies to David (Apple) and reminds to avoid clashes with 0588 when preparing new version of this CR. Vivian (vivo) provides r02 to add data source type in this CR, and undo some changes which have clashes with S2-2500588. Vivian (vivo) provides r03, it objects to r02, r01 and initial version Xiaoyan (CATT) provides r04. Dimitris (Lenovo) objects to r03 Xiaoyan (CATT) replies to Belen (Ericsson). Zhao (Huawei) objects to r04. Belen (Ericsson) removes objection, please disregard r03 (provided by Ericsson, not by vivo) Thomas raises concerns that meaning of 'data type' (renamed to 'location measurement data types' in r04) is still unclear and suggest explaining or removing this parameter Yuang(ZTE) provides comment Belen (Ericsson) asks Xiaoyan (CATT) to use location estimation in step 5. Xiaoyan (CATT) replies to Thomas (Nokia) Xiaoyan (CATT) provides r05. Thomas (Nokia) replies to Xiaoyan (CATT) Xiaoyan (CATT) replies to Thomas (Nokia), and provides r06 Thomas (Nokia), is fine with r06 Jianning (Xiaomi) provides r07 wihtout 'data type' as one option ==== General Revisions Deadline ==== Jianning (Xiaomi) responses to Zhao (Huawei) Juan Zhang (Qualcomm) is fine with either r06 or r07. Vivian (vivo) is only fine with r06, not OK with r07. and asks Jianning if you can revert data source type if what you concern is data type, they are two different things if you follow the discussion. Dimitris (Lenovo) is ok with r06, objects to r07 Zhao (Huawei) cannot accept r06 and proposes to postpone this CR. Thomas(Nokia) can accept r06 or r07, objects to earlier revisions. OK to postpone. Vivian( vivo) still think data source type can be treated independently from RAN decision on case 2b and 3b as I commented in previous, asks people can you live with r06 with an EN about model ID proposed by Jianning? Xiaoyan (CATT) proposes r06 + EN on Model Identifier + undone the deletion of data source type in the existing EN. Zhao (Huawei) cannot accept Xiaoyan(CATT)'s proposal, still proposes to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2501018 | CR | Approval | 23.273 CR0667 (Rel-19, 'F'): Clarification on Data collection from LMF requested by NWDAF | Xiaomi | Rel-19 | Proposed merged with S2-2500834 (postponed). Postponed | Zhao (Huawei) provides comments. Vivian (vivo) provides comments. Xiaoyan (CATT) proposes to mark S2-2501018 as merged into S2-2500834. Dimitris (Lenovo) is also OK to use S2-2500834 as the basis for input data collection for ML model performance monitoring Jianning (Xiaomi) is ok to merge into S2-2500834 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500629 | CR | Approval | 23.273 CR0652 (Rel-19, 'B'): Updates on input data of AI/ML positioning model performance monitoring | China Telecom | Rel-19 | Overlap in LMF data exposure service operation Proposed merged with S2-2500588 (postponed). Postponed | Zhao (Huawei) provides comments. Yuang(ZTE) provides comments. Jiahui (China Telecom) replies. Zhao (Huawei) replies to Jiahui (China Telecom). Hyesung (Samsung) comments. David (Apple) provides comments. Juan Zhang (Qualcomm) provides comments. Jiahui (China Telecom) replies and provides r01. Zhao (Huawei) provides comments and proposes to merge this CR into S2-2500588. ==== General Revisions Deadline ==== Jiahui (China Telecom) agrees to merge this CR into S2-2500588. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500693 | CR | Approval | 23.273 CR0654 (Rel-19, 'C'): KI#1 - Further clarification on input data for ML model training for AI/ML positioning | Lenovo | Rel-19 | Postponed in e-mail session | Sihan (vivo) provides comments and support this CR. Juan Zhang (Qualcomm) provides comments. Dimitris (Lenovo) responds to Juan (Qualcomm) Zhao (Huawei) provides comments and supports this CR. Thomas (Nokia) provides r01. Juan Zhang (Qualcomm) objects r01. ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to postpone the CR. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | - | - | - | TS 23.273: General Description and Model Retrieval | - | - | Docs:=6 | - | |
| 19.15.2 | S2-2500083 | CR | Approval | 23.288 CR1302 (Rel-19, 'B'): Modifications on ML Model retrieval service | ZTE | Rel-19 | Approved | Agreed | |
| 19.15.2 | S2-2500088 | CR | Approval | 23.273 CR0635 (Rel-19, 'B'): ML Model retrieval from ADRF | ZTE | Rel-19 | Check Affected Clauses! Merged into S2-2501137 | Yuang(ZTE) propose to merge this CR to S2-2500833. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500228 | CR | Approval | 23.273 CR0642 (Rel-19, 'C'): Updates to AI/ML-based positioning general descriptions | Apple | Rel-19 | Focus on clause 5.18 r04 agreedrevised in e-mail session to S2-2501136, merging S2-2500194 | Xiaoyan (CATT) provides r01. Hyesung (Samsung) comments. Zhao (Huawei) provides comments. David (Apple) provides r02 Zhao (Huawei) provides r03. David (Apple) provides r04 correcting a few typos on the cover sheet. ==== General Revisions Deadline ==== Xiaoyan (CATT) provides comments. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501136 | CR | Approval | 23.273 CR0642R1 (Rel-19, 'C'): Updates to AI/ML-based positioning general descriptions | Apple, CATT | Rel-19 | Revision of S2-2500228r04, merging S2-2500194. Approved | Agreed | |
| 19.15.2 | S2-2500833 | CR | Approval | 23.273 CR0657 (Rel-19, 'F'): Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | CATT | Rel-19 | Clause 5.18 merge into S2-2500228? r04 agreedrevised in e-mail session to S2-2501137, merging S2-2500088 | Xiaoyan (CATT) provides r01. Yuang(ZTE) provides comments. David (Apple) provides r02. Xiaoyan (CATT) provides comments to r02. Vivian (vivo) provides comments and r03. Hyesung (Samsung) provides comments. Zhao (Huawei) provides comments. Yuang (ZTE) replies to Zhao(Huawei) and Hyesung(Samsung). Bahador (NTT DOCOMO) support Yuang (ZTE) explanation on model retrieval from ADRF. Xiaoyan (CATT) provides r04. ==== General Revisions Deadline ==== Yuang (ZTE) supports r04. Bahador (NTT DOCOMO) supports r04. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501137 | CR | Approval | 23.273 CR0657R1 (Rel-19, 'F'): Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | CATT, ZTE | Rel-19 | Revision of S2-2500833r04, merging S2-2500088. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.273: Data collection from RAN and UE | - | - | Docs:=7 | - | |
| 19.15.2 | S2-2500132 | CR | Approval | 23.273 CR0637 (Rel-19, 'B'): KI#1: Considering RAN load when collecting data to train model for positioning | Nokia | Rel-19 | Overlap in data collection from RAN and UE. Focus on RAN load related? CC#4:Postponed | Hyesung (Samsung) provides comments. Zhao (Huawei) provides comments. Yuang(ZTE) supports this CR. David (Apple) provides comments, agrees with Huawei and Samsung. Belen (Ericsson) provides comments. Thomas(Nokia) provides r01 to address comments of Belen and replies to other comments Mehrdad (Mediatek Inc.) provides comments on original version and r01 Belen replies to Mehrdad (Mediatek Inc.) David (Apple) provides further comments. Juan Zhang (Qualcomm) provides comments for r00 and r01. Sihan(vivo) provides comments for r02 Thomas(Nokia) provides r02 to address comments and replies to other comments Belen (Ericsson) replies to Mehrdad (Mediatek Inc.) Hyesung (Samsung) provides further comments. Thomas(Nokia) provides r03 to address comments and replies to other comments Juan Zhang (Qualcomm) provides comments on r03 Thomas(Nokia) replies to Zhang Tao (Sony) provides comments. David (Apple) still has concerns with r03. Thomas(Nokia) provides r04 to address comments ==== General Revisions Deadline ==== Ulises (InterDigital) supports this paper (i.e., r04), and he provides question for clarification. Belen (Ericsson) asks to remove references to NG-RAN load in step 6, then r04 can be accepted Thomas(Nokia) is fine with approving r04 plus removing 'when NG-RAN is not experiencing extensive load' in step 6 Hyesung (Samsung) proposes to postpone this CR. David (Apple) agrees postponing would be best. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500192 | CR | Approval | 23.273 CR0638 (Rel-19, 'F'): Clean up the ENs regarding AI/ML positioning | Qualcomm Incorporated | Rel-19 | Postponed in e-mail session | Vivian(vivo) proposes this CR only to focus on the discussion of maximum number of UEs per VC's chairman notes ,and provides comments. Zhao (Huawei) provides comments. David (Apple) comments. Hyesung (Samsung) comments. Mehrdad (MediaTek Inc.) asks to remove impact on UICC, ME and RAN from cover page. Juan Zhang (Qualcomm) provides r01 to remove the overlap change based on rapporteur's suggestion. ==== General Revisions Deadline ==== Zhao (Huawei) proposes to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500832 | CR | Approval | 23.273 CR0656 (Rel-19, 'F'): Clarification on data collection by LMF for LMF-based AIML Positioning | CATT | Rel-19 | Overlap in data collection from RAN and UE. Other ENs related? r07 agreedrevised in e-mail session to S2-2501138, merging S2-2501017 and S2-2501020 | Xiaoyan (CATT) provides r01. Zhao (Huawei) provides comments. Jianning (Xiaomi) provides comments on r01 Vivian (vivo) provides r02 to undo changes for clauses' title Belen (Ericsson) provides r03 that removes overlaps with S2-2501037 (Ericsson) as per rapporteur guidance. We object to initial version, r01, r02 Xiaoyan (CATT) replies to Belen (Ericsson). Belen (Ericsson) replies to Xiaoyan (CATT) David (Apple) provides r04. Xiaoyan (CATT) provides r05. Xiaoyan (CATT) provides r06. Jianning (Xiaomi) provides r07 ==== General Revisions Deadline ==== Belen (Ericsson) is okay with r07, prefers r06 Xiaoyan (CATT) replies to Jianning (Xiaomi) Jianning (Xiaomi) replies to Xiaoyan (CATT). Can only accept r07, or r07 with changes in step 1 as ' If the PRU(s) are pre-configured in LMF for AI model training or AI model performance monitoring, it assumed all the PRU(s) are served by same LMF. Step 2 and 3 are skip.' Instead of the removed green part. Hopt it acceptable as war forward Belen (Ericsson) cannot accept Jianning (Xiaomi) proposal, r07 is okay Xiaoyan (CATT) is fine with r07. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501138 | CR | Approval | 23.273 CR0656R1 (Rel-19, 'F'): Clarification on data collection by LMF for LMF-based AIML Positioning | CATT | Rel-19 | Revision of S2-2500832r07, merging S2-2501017 and S2-2501020. Approved | Agreed | |
| 19.15.2 | S2-2501020 | CR | Approval | 23.273 CR0668 (Rel-19, 'F'): To remove the EN on limit of number of UEs in clause 6.22.2 | Xiaomi | Rel-19 | Merge into S2-2500832. (similar proposed changes for clause 6.22.2). Overlap in data collection from RAN and UE Merged into S2-2501138 | Xiaobo (vivo) provides comments and proposes to merge S2-2501020 into S2-2500832 Jianning (Xiaomi) is ok to merge S2-2501020 into S2-2500832 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500229 | CR | Approval | 23.273 CR0643 (Rel-19, 'C'): Updates to AI/ML-based positioning procedures | Apple | Rel-19 | Baseline for user consent related? r08 agreedrevised in e-mail session to S2-2501139. | Vivian(vivo) asks only to focus on user consent aspect in this CR per Chairman note's guidance, and supports the related modifications on user consents. Juan Zhang (Qualcomm) provides comments Vivian (vivo) confirms to co-sign r01. David (Apple) provides r01. Bahador (NTT DOCOMO) provides comments. David (Apple) provides r02. Hyesung (Samsung) comments. Zhao (Huawei) provides comments. David (Apple) provides r03 Hyesung (Samsung) comments on user consent aspect David (Apple) provides r04 and replies to Lenovo Dimitris (Lenovo) has concerns with the proposal David (Apple) thanks Xiaomi for the support, but the new revision number and its link seem incorrect Jianning (Xiaomi) provides r03 Vivian(vivo) provides r05 to avoid clashes with S2-2500832 Dimitris (Lenovo) provides r06 Belen (Ericsson) provides r07 without clauses 6.22.3 on data collection from RAN as per rapporteur guidance. We objects to any revision that includes that clause as overlaps with S2-2501037 We want state that overlaps should be resolved place prior to the meeting start. David (Apple) provides r08. ==== General Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r08. Hyesung (Samsung) is fine with r08 while the cover page update is needed. Not ok with other versions. Belen (Ericsson) asks to remove user consent revoke sentence, then it is okay with r08 Belen (Ericsson) is okay with r08 Dimitris (Lenovo) is ok with r08 potentially with an added EN on user consent revocation ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501139 | CR | Approval | 23.273 CR0643R1 (Rel-19, 'C'): Updates to AI/ML-based positioning procedures | Apple, vivo | Rel-19 | Revision of S2-2500229r08. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.288 General | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2501037 | CR | Approval | 23.273 CR0669 (Rel-19, 'B'): Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | Ericsson | Rel-19 | Baseline for positioning case related? CC#4: r08 + changes agreed. Revised in CC#4 to S2-2501348. | Belen (Ericsson) provides r01 to follow rapporteur guidance on the scope and removing discussion on RAN load David (Apple) provides comments. Xiaoyan (CATT) provides r02 to avoid overlaps/conflicts with S2-2500832 & S2-2500228. David (Apple) comments and provides r03 Hyesung (Samsung) comments Hyesung (Samsung) provides further comments Zhao (Huawei) provides comments. Vivian (vivo) provides r04, to delete some clashes with S2-2500832 and S2-2500229. Belen (Ericsson) asks Vivo why they have removed the full CR if this is baseline for Baseline for positioning case related as per rapporteur guidelines Belen (Ericsson) provide r06 as Baseline for positioning case related as per rapporteur guidelines , addresses Samsung, Huawei and Apple comments David (Apple) comments and provides r07. Xiaoyan (CATT) comments. David (Apple) is OK with r08 as previously provided by Ericsson. Belen (Ericsson) comments on user consent and provides r8. Xiaoyan (CATT) requests to undone the change last 2nd paragraph. ==== General Revisions Deadline ==== Belen (Ericsson) provides comments to Xiaoyan Xiaoyan (CATT) replies Belen (Ericsson) Xiaobo (vivo) provide some clarification regarding rapporteur's suggestion about tdoc sorting/handling . Vivian (vivo) replies to Belen (Ericsson) Juan Zhang (Qualcomm) is OK with r08. Belen (Ericsson) replies to Xiaoyan (CATT) Xiaoyan (CATT) can accept r02, r05, objects to r00, r01, r03, r06, r07 and r08, can accept r08 with removing the added 'if step 1 was triggered by Nlmf_DataExposure service, the LMF provides the measurements and ground truth data to the consume' in clause 6.22.3. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501348 | CR | Approval | 23.273 CR0669R1 (Rel-19, 'B'): Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | Ericsson | Rel-19 | Revision of S2-2501037r08 + changes. This CR was agreed | Agreed | |
| 19.15.2 | - | - | - | TS 23.288 Performance monitoring | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500692 | CR | Approval | 23.288 CR1364 (Rel-19, 'C'): KI#1 - Further clarification on ML Model performance monitoring for AI/ML positioning | Lenovo | Rel-19 | CC#4: Postponed | Zhao (Huawei) asks for clarification. Dimitris (Lenovo) responds to Zhao (Huawei) Sihan (vivo) provides comments Dimitris (Lenovo) provides r01 David (Apple) provides comments. Dimitris (Lenovo) responds to David (Apple) Belen (Ericsson) provides comments. Zhao (Huawei) replies to Dimitris (Lenovo). David (Apple) explains and shares another concern Thomas (Nokia) comments on r02 wording Dimitris (Lenovo) responds to David and Zhao and provides r02 Dimitris (Lenovo) provides r03 Belen (Ericsson) restates comments on user consent revoke. Dimitris (Lenovo) provides r04 taking into account Belen's suggestions David (Apple) provides r05. ==== General Revisions Deadline ==== Belen (Ericsson) is okay with r04, objects to r05 too late to add new EN. David (Apple) objects to r04, is OK with r05, r03 and r02. Dimitris (Lenovo) is ok with r04 David (Apple) replies to Lenovo. Dimitris (Lenovo) responds to Apple. A way forward is to add an EN on top of r04. David (Apple) is OK with Lenovo's way forward proposal Zhao (Huawei) proposes to postpone this CR. Dimitris (Lenovo) propose to go with r04 + EN: Action of the LMF if the LMF is informed of user consent revocation is FFS Zhao (Huawei) can accept r04 + one more EN: Another option of collected data (i.e., measurement data and ground truth UE location) used for ML model performance monitoring for LMF-based AI/ML positioning is FFS. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | - | - | - | TS 23.501 and TS 23.502 | - | - | Docs:=5 | - | |
| 19.15.2 | S2-2500198 | CR | Approval | 23.501 CR5635R2 (Rel-19, 'B'): NWDAF model provision for AI positioning | Vivo | Rel-19 | Baseline for 23.501 of AI positioning related. Revision of S2-2411551. r04 agreed. Revised in e-mail session to S2-2501140. | Yuang(ZTE) provide comments. Zhao (Huawei) provides comments and r03. Yuang (ZTE) provides r02. Thomas (Nokia) provides r01. Bahador (NTT DOCOMO) supports r03 and co-signs. Vivian (vivo) provides r04. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501140 | CR | Approval | 23.501 CR5635R3 (Rel-19, 'B'): NWDAF model provision for AI positioning | Vivo, Nokia, ZTE | Rel-19 | Revision of S2-2500198r04. Approved | Agreed | |
| 19.15.2 | S2-2501019 | CR | Approval | 23.502 CR5316 (Rel-19, 'F'): Update UDM to support user consent of data collection for performance monitoring | Xiaomi | Rel-19 | Confirm Spec version used - CR states {19.1.0}! Noted in e-mail session | Zhao (Huawei) provides comments. David (Apple) provides comments. Bahador (NTT DOCOMO) requests for clarification. Vivian (vivo) provides comments. Belen (Ericsson) do not think that this CR is needed. Dimitris (Lenovo) prefers no changes to user consent mechanism for performance monitoring David (Apple) provides r01, disagrees with the view that data collection for performance monitoring does not require user consent Jianning (Xiaomi) responses to Bahador (NTT DOCOMO) Jianning (Xiaomi) responses to Dimitrios (Lonovo) and Belen (Ericsson) Jianning (Xiaomi) is ok with r01 as way forward, Thomas(Nokia) raises concerns against purpose 'model performance monitoring' David (Apple) replies to Nokia, insists this CR/r01 should be agreed. Bahador (NTT DOCOMO) requests for clarification on the difference between the 'model training' and 'model performance evaluation' (from the subscriber perspective). Belen (Ericsson) cannot accept r01 David (Apple) replies to Ericsson and Docomo. Belen (Ericsson) replies Bahador (NTT DOCOMO) agrees with the proposed way-forward to leave the EN and consider additional purpose for the user consent in the next meeting. David (Apple) provides r02. ==== General Revisions Deadline ==== Belen (Ericsson) objects to all revisions of this CR Jianning (Xiaomi) replies to Belen (Ericsson), R02 is good way forward, since current user consent only used for 23.288, at least we need to update the user consent also for 23.273. please re-consider your objection, thanks! Belen (Ericsson) replies to Jianning (Xiaomi) Thomas (Nokia) objects to all revisions of this CR Jianning (Xiaomi) responses to Belen (Ericsson) ==== Comments Deadline ==== | Noted |
| 19.15.2 | S2-2500199 | CR | Approval | 23.502 CR5011R2 (Rel-19, 'B'): NWDAF registration and discovery for AI positioning | Vivo | Rel-19 | Revision of S2-2411552. r02 agreed. Revised in e-mail session to S2-2501141. | Zhao (Huawei) provides comments and r01. Vivian (vivo) thanks Zhao for revising, and provides r02. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501141 | CR | Approval | 23.502 CR5011R3 (Rel-19, 'B'): NWDAF registration and discovery for AI positioning | Vivo | Rel-19 | Revision of S2-2500199r02. Approved | Agreed | |
| 19.15.2 | - | - | - | KI#2: Vertical Federated Learning | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | General | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500196 | CR | Approval | 23.288 CR1323 (Rel-19, 'F'): Remove ENs unrelated to the exception list | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | Postponed in e-mail session | Thomas (Nokia) raises concerns that the CR overlaps with multiple other CRs and that the ENs should not simply be removed without further clarifications. Thus suggest postponing this CR to see if any ENs are not resolved by other CRs after this meeting Xiaobo (vivo) fixed the email title and clarified this CR is to do some cleanup by deleting a few ENs which are not covered by the approved exception sheet (on behalf of rapporteur). Haven checked with other ongoing CRs, it seemed that all the ENs listed here have been resolved without introducing any Cat B/C CRs. Therefore I agree with you we better postpone the CR and revisited in in Feb meeting. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500195 | CR | Approval | 23.288 CR1322 (Rel-19, 'F'): Adding missing parts for VFL | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.288: Definitions | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500303 | CR | Approval | 23.288 CR1331 (Rel-19, 'B'): The related definitions for VFL and HFL | China Mobile | Rel-19 | r03 agreedrevised in e-mail session to S2-2501142. | Yuang(ZTE) supports and would like to co-sign this CR. Belen (Ericsson) provides comments, asks questions. Aihua(CMCC) provides r01. Thomas(Nokia) provides r02. Haiyang (Huawei) comments. Belen (Ericsson) objects to r02, it cannot accept to add HFL as definition as we refer to FL in 23.288 Yuang(ZTE) provides r03 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501142 | CR | Approval | 23.288 CR1331R1 (Rel-19, 'B'): The related definitions for VFL and HFL | China Mobile, ZTE, Nokia | Rel-19 | Revision of S2-2500303r03. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.288: Registration and Discovery | - | - | Docs:=4 | - | |
| 19.15.2 | S2-2500566 | CR | Approval | 23.288 CR1346 (Rel-19, 'B'): Update Registration and Discovery procedure to include trusted AF as server case | LG Electronics | Rel-19 | Merged into S2-2501143 | Xiaobo (vivo) thanks Jaewoo(LGE) for the offline effort and proposing merging Jaewoo (LGE) proposes to merge this CR into S2-2501070. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2501070 | CR | Approval | 23.288 CR1370 (Rel-19, 'F'): KI#2 update to registration and discovery procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! r13 agreed. Revised in e-mail session to S2-2501143, merging S2-2500267, S2-2500566 and S2-2500630 | Xiaobo (vivo) provides comments and proposes to focus on Issue #3 (VFL server registration) Belen (Ericsson) provides r01, also ask questions for clarification. Sohei (KDDI) reply to Jiahui and Belen, and support r03. Jiahui (China Telecom) provides comments. Ulises (InterDigital) replies to Belen's comments, and he provides r03. Belen (Ericsson) cannot accept r02, there are comments in r01 that are not included. Ulises (InterDigital) replies to Belen's question, and it provides r02. Haiyang (Huawei) provides r04. Haiyang (Huawei) provides r05. Belen (Ericsson) provide r06. Jingran (OPPO) provide r07. Vivian (vivo) provide r08. Jaewoo (LGE) provides r13 . Sohei (KDDI) support r12 Thomas(nokia) replies. Ulises (InterDigital) is fine with most of the updates in r011, but requests clarification on the added VFL capability in clause, 5.5, and he provides r12. David (Apple) provides r11. Thomas(nokia) provides r10. Ulises (InterDigital) provides additional comments and editorial changes on top of r08, and he provides r09. Ulises (InterDigital) is fine with r13, and thanks companies for the constructive effort. Jingran (OPPO) is ok with r13 and want to co-sign. ==== General Revisions Deadline ==== Jaewoo (LGE) is ok with r13 and would like to co-sign. Haiyang (Huawei) is ok with r13. Belen (Ericsson) is ok with r13, ask to cosign. Tingyu (Samsung) would like to co-sign ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501143 | CR | Approval | 23.288 CR1370R1 (Rel-19, 'F'): KI#2 update to registration and discovery procedure | InterDigital, Nokia, KDDI, OPPO, LGE, Ericsson, Samsung | Rel-19 | Revision of S2-2501070r13, merging S2-2500267, S2-2500566 and S2-2500630. Approved | Agreed | |
| 19.15.2 | S2-2500630 | CR | Approval | 23.288 CR1352 (Rel-19, 'B'): Updates on VFL server discovery and VFL preparation procedure | China Telecom | Rel-19 | Merged into S2-2501143 | Xiaobo (vivo) provides comments and proposes to focus on Issue #3 (VFL server registration) Jiahui (China Telecom) provides r01 merging with 1070 and 0267. Jingran(OPPO) provides comments for r01. Jiahui (China Telecom) agrees to merge this paper to S2-2501070. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | - | - | - | TS 23.288: VFL preparation | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500432 | CR | Approval | 23.288 CR1341 (Rel-19, 'B'): Sample ID intersection by NEF during the VFL preparation in untrusted AF VFL server scenario | Samsung, | Rel-19 | Noted in e-mail session | Xiaobo (vivo) provides comments and proposes to focus on Issue #5 Belen (Ericsson) provides comments, the procedure seems to be incorrect, no privacy issues exist, objections to this revision. Dimitris (Lenovo) comments Vivian (vivo) also supports changes in this CR, and provides views to Belen's comments. Tingyu (Samsung) provides r01, replies to Belen (Ericsson) and agrees with Vivian (vivo) and Dimitris (Lenovo). Jiahui (China Telecom) provides comment. Kohei (NTT DOCOMO) provides comment. David (Apple) provides comments. Sohei (KDDI) asks question and shares concerns about sample intersection at NEF. Thomas (Nokia) shares concerns about sample intersection at NEF. Suggest alternate solution for UE samples in r03. Belen (Ericsson) still objects to r02, r01 and initial version. Tingyu (Samsung) provides r02 and replies to David (Apple) and Kohei (NTT DOCOMO). Haiyang (Huawei) thinks sample intersection at NEF makes sense from sample ID hiding. Sohei (KDDI) asks question on the back ground of privacy concern Tingyu (Samsung) provides r04; replies to Belen (Ericsson), Sohei (KDDI) and Thomas (Nokia); and thanks Haiyang (Huawei) for the support. Jiahui (China Telecom) replies to Sohei and comments. Haiyang (Huawei) agrees with Jiahui. Vivian (vivo) supports NEF intersection work and provides r05, requesting to send LS to SA3 to check the security issue. Belen (Ericsson) objects to this CR, all revisions. Objects to sending any LS to SA3 Tingyu (Samsung) replies to Belen (Ericsson), provides r06 and r07 focusing on signalling aggregation by NEF only. Belen (Ericsson) cannot accept r06 or r07, asks to NOTE this CR Thomas(Nokia) replies to Vivian. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.15.2 | S2-2501071 | CR | Approval | 23.288 CR1371 (Rel-19, 'B'): KI#2 update to VFL preparation procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! CC#4: r04 + changes agreed. Revised in CC#4 to S2-2501347. | Yuang(ZTE) provides comments. Xiaobo (vivo) provides comments and proposes to focus on Issue #1 for preparation David (Apple) corrects the subject to comply with SA2 e-meeting guidelines. Ulises (InterDigital) replies to Yuang and Thomas comments, and he provides r02. Thomas (Nokia) provides r01. Jaewoo (LGE) provides comments on r02. Haiyang (Huawei) comments, agree with others . Ulises (InterDigital) replies to Jaewoo, he is OK with r04. Jaewoo (LGE) provides comments on r03 and provides r04. Ulises (InterDigital) replies to Jaewoo and Haiyang comments, and he provides r03. Belen (Ericsson) objects to the added step0, objects to revisions that include that step. ==== General Revisions Deadline ==== Ulises (InterDigital) replies to Belen, we are OK with removing step 0 and reinstate the note on this topic . Haiyang (Huawei) replies to Ulises (InterDigital), comment to remove 'required statistical properties of the data sample' as well. Belen (Ericsson) asks Ulises to remove step 0, as it still appears, it also asks to align step 1 Ulises (InterDigital) replies to Belen, I'm providing r06 to address Ericsson's concerns. Ulises (InterDigital) replies to Haiyang (Huawei) comments, and he provides r07. Abbas (Futurewei) supports r07 and would like to co-sign. Thomas(Nokia) suggest agreeing r07 + removal 'If needed, VFL Clients may evaluate data availability of sample UEs (e.g., through registration state)based on the required criteria for sample alignment,' + adding EN 'It is ffs whether VFL server or clients checks whether UEs are registered'. Objects against r07, r06, r05, r01 and original version ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501347 | CR | Approval | 23.288 CR1371R1 (Rel-19, 'B'): KI#2 update to VFL preparation procedure | InterDigital | Rel-19 | Revision of S2-2501071r04 + changes. This CR was agreed | Agreed | |
| 19.15.2 | - | - | - | TS 23.288: VFL training | - | - | Docs:=9 | - | |
| 19.15.2 | S2-2500301 | CR | Approval | 23.288 CR1330 (Rel-19, 'B'): Clarifications on VFL general procedure | China Mobile | Rel-19 | Confirm Spec version used - CR states {}! r02 agreed. Revised in e-mail session to S2-2501144. | Yuang(ZTE) supports and would like to co-sign this CR. Belen (Ericsson) objects to the initial version, provides r01 Dimitris (Lenovo) also objects to versions that remove EN on contribution weights without resolution Xiaobo (vivo) suggest merging this into S2-2500398 as the most changes are overlapping with S2-2500398 and other papers. Hopefully everyone can live with it. Aihua(CMCC) tends to keep S2-2500301 as standalone CR which goes to be stable without more comment. Dimitris (Lenovo) provides r02 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501144 | CR | Approval | 23.288 CR1330R1 (Rel-19, 'B'): Clarifications on VFL general procedure | China Mobile, Samsung | Rel-19 | Revision of S2-2500301r02. Approved | Agreed | |
| 19.15.2 | S2-2500335 | CR | Approval | 23.288 CR1334 (Rel-19, 'B'): Resolve some ENs in the vertical federated learning training procedure | OPPO | Rel-19 | Merged into S2-2501134 | Xiaobo (vivo) provides comments and proposes to focus on Issue #2 for training Jingran (OPPO) proposes and confirm the S2-2500335 can be merged into S2-2500398 Vivian (vivo) provides comments on VFL issue #2 for training. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500460 | CR | Approval | 23.288 CR1342 (Rel-19, 'C'): Sample update during VFL training | Apple | Rel-19 | CC#4: Postponed | Yuang(ZTE) provides comments. Xiaobo (vivo) provides comments and proposes to focus on Issue #3 for training David (Apple) replies to ZTE. Yuang (ZTE) replies to David (Apple) and can accept this CR. Belen (Ericsson) provides r01. Jingran (OPPO) provides r02. David (Apple) provides r03. Haiyang (Huawei) comments. David (Apple) replies to Huawei. Sihan(vivo) provides comments and r04 Dimitris (Lenovo) comments on the changes in clause 6.2H.3 Jiahui (China Telecom) provides comment. Yuang (ZTE) provides r05, prefer to agree r05. David (Apple) can live with r05, but the link shared is incorrect Thomas (Nokia) can live with r05 Yuang (ZTE) provide comments and can live with r05 Jingran (OPPO) is ok with r05 Vivian (vivo) asks to avoid overlap with S2-2500398 about 6.2H.3 David (Apple) clarifies to Vivian (vivo). Jihoon (ETRI) is also okay with r05. ==== General Revisions Deadline ==== Haiyang (Huawei) can only accept r05 + removing 'or a new list derived from the agreed list in the preparation phase' + removing '- (Optional), VFL server may indicate model status has to be saved as a checkpoint or if the training has to restart from the model status of a previous checkpoint (e.g. training iteration number).' + removing 'The VFL Server may provide checkpoint information according to clause 6.2H.3.'. David (Apple) raises the concern that Haiyan (Huawei) is asking for a major new revision well after revisions deadline is over without having provided comments since Tuesday UTC morning; can only live with one proposed change on top of r05 if chair and rest of companies are OK. Thomas(Nokia) support proposal of Haiyang (Huawei) Belen (Ericsson) is also okay with r05, ask to cosign. Tingyu (Samsung) is OK with r05 and would like to co-sign. Abbas (Futurewei) supports r05 and would like to co-sign. David (Apple) thanks companies for the support, checks with Huawei if they can live with r05 with the understanding that the CR can be revised in the Athens meeting. Thomas(Nokia) revokes previous agreement for r05, suggest agreeing r05 plus suggested additions David (Apple) requests the CR to be opened at CC4 since both Nokia and Huawei requested an unexpected revision after the revisions deadline. Nokia revoking its agreement to r05 close to the comments deadline is indeed quite unfortunate. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500631 | CR | Approval | 23.288 CR1353 (Rel-19, 'B'): Updates on VFL training and VFL inference to remove ENs | China Telecom | Rel-19 | CC#4: r05 + changes agreed. Revised in CC#4 to S2-2501346. | Xiaobo (vivo) provides comments and proposes to focus on Issue #4 for training Dimitris (Lenovo) provides r01 including aspects from S2-2500691 Jingran (OPPO) provides comments Yuang (ZTE) provides comments Yuang(ZTE) can accept r02 and co-sign the paper. Jiahui (China Telecom) replies and provides r02. Dimitris (Lenovo) supports r02 and request to co-sign Haiyang (Huawei) provides comments Thomas(nokia) is fine with technical content and would like to co-sign, However there are concernes about overlaps with 676 for inference. Perhaps inference part should be covered there. Yuang(ZTE) is OK with the content but raises concern on the confliction with vivo's S2-2500655 Jiahui (China Telecom) replies to Haiyang and provides r03. Yuang(ZTE) is OK with the content, but raises concern for CR confliction Jiahui (China Telecom) provides r04. Yuang (ZTE) provides r05. Jihoon (ETRI) supports r05 and would like to co-sign. ==== General Revisions Deadline ==== Yuang(ZTE) supports r05, OK with r04, object any other revisions and original CR Haiyang (Huawei) can only accept r05 + removing 'outlier data,' + removing 'The VFL server may optionally take account the local ML model accuracy monitoring information received from VFL client(s) when computing global ML Model metric.' Yuang(ZTE) replies Haiyang (Huawei) Jiahui (China Telecom) replies Haiyang (Huawei) and requests to reconsider r05 Belen (Ericsson) asks to postpone, objects to all revisions. Jiahui (Chine Telecom) replies Ericsson. Belen (Ericsson) asks to remove from r05, 'The NEF may gather the reports from untrusted AF VFL clients and send them together in one notification to the VFL server' and 'Each client may report local ML model accuracy monitoring information (e.g. local data volume, outlier data, rating of the local data) if ML model accuracy check flag is received in step 2' then it can be accepted.' ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501346 | CR | Approval | 23.288 CR1353R1 (Rel-19, 'B'): Updates on VFL training and VFL inference to remove ENs | China Telecom, ZTE, Lenovo, Nokia, ETRI | Rel-19 | Revision of S2-2500631r05 + changes. This CR was agreed | Agreed | |
| 19.15.2 | S2-2501069 | CR | Approval | 23.288 CR1369 (Rel-19, 'B'): KI#2 update to VFL training procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! Merged into S2-2501134 | Yuang(ZTE) provides comments. Dimitris (Lenovo) objects to remove EN on contribution weights without any solution Vivian (vivo) asks Ulises whether can agree to merge this CR into S2-2500398 because of many overlaps, otherwise please make sure to avoid any overlap. Ulises (InterDigital) replies to Vivian (Vivo), I'm OK with the merge onto 0398, please merge considering my answer to other comments as described below. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500398 | CR | Approval | 23.288 CR1338 (Rel-19, 'C'): Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, [OPPO] | Rel-19 | r16 agreedrevised in e-mail session to S2-2501134, merging S2-2500335 and S2-2501069 | Xiaobo (vivo) provides comments and proposes to focus on Issue #1 for training and Issue #2 for training Vivian (vivo) provides comments on VFL issue #2 for training. Jaewoo (LGE) provides r03 based on r02. Thomas(Nokia) raises concerns against previous versions, provides r02 Belen (Ericsson) replies to vivo, provides r01 Sohei (KDDI) provides comments Dimitris (Lenovo) supports r00, r01, has concerns with r02, r03 Belen (Ericsson) provides r04, replies to comments, has concerns with r02, r03 Vivian (vivo) provides r06 on top r04, which also merged the EN from Nokia in r05. Yuang (ZTE) raises concern on the CR confliction Yuang (ZTE) provides comments on r04. Thomas(Nokia) provides replies to Jaewoo Thomas (Nokia) provides r05, objects to previous revisions and original CR Jaewoo (LGE) provides comments on r04. Jiahui (China Telecom) merges part of 0631 to this paper and provides r07 on top r06. Haiyang (Huawei) provides r08. Yuang (ZTE) provides r09. David (Apple) provides r10. Yuang (ZTE) provides r11. Aihua(CMCC) supports r11. Jiahui (China Telecom) merges part of 0631 to this paper and provides r12 on top r11. Jaewoo (LGE) responds to Thomas (Nokia). Vivian (vivo) provides R13 to undo the EN about AnLF and MTLF splitting, because it has been covered by S2-2500268. Tingyu (Samsung) provides comments. Belen (Ericsson) provides r14, with some minor updates, replies to comments too. Tingyu (Samsung) provides r15 and co-sign. Jiahui (China Telecom) asks for clarification on r14 and r15. Belen (Ericsson) replies to China Telecom Belen (Ericsson) provides r16 Thomas (Nokia) provides r17, objects to previous revisions Belen (Ericsson) objects to r17, can accept r16, r15, r14 (may be more). Asks other companies to state their preferred revision and if there is support for certain revision would ask Xiaobo to bring this to the conference call? Jingran (OPPO) object to R17, accept r16. Yuang(ZTE) prefer r16. Tingyu (Samsung) prefers r16. Aihua(CMCC) provides r18 Haiyang (Huawei) comments ==== General Revisions Deadline ==== Jaewoo (LGE) provides comments on termination flag. Yuang(ZTE) prefers r16 + change provided by CMCC, can live with r17 + change provided by CMCC or r18, objects any other revisions and original CR. Sohei (KDDI) prefers r17, which was proposed by Nokia. Belen (Ericsson) objects to r18 and r17. It can accept r16 (including CMCC proposal for r18 and Huawei comments) ==== Comments Deadline ==== Haiyang (Huawei) supports to Belen (Ericsson) to go with r16 (including CMCC proposal for r18 and Huawei comments) | Revised |
| 19.15.2 | S2-2501134 | CR | Approval | 23.288 CR1338R1 (Rel-19, 'C'): Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, OPPO, Nokia | Rel-19 | Revision of S2-2500398r16, merging S2-2500335 and S2-2501069. Endorsed | Endorsed | |
| 19.15.2 | - | - | - | TS 23.288: Accuracy monitoring | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500655 | CR | Approval | 23.288 CR1355 (Rel-19, 'B'): Enhancements for the accuracy monitoring of VFL training | Vivo | Rel-19 | Postponed in e-mail session | Yuang(ZTE) provides comments. Sihan (vivo) provides r01 David (Apple) provides questions for clarification. Dimitris (Lenovo) has a question for clarification Sihan(vivo) provides r02 and replies to other comments Dimitris (Lenovo) provides further comments Yuang(ZTE) provides comments and raises concern on confliction between CRs Sihan(vivo) provides r03 and replies to other comments Yuang(ZTE) replies to Thomas(Nokia), support the note added by Sihan(vivo) Thomas(Nokia) raises technical concern Haiyang (Huawei) provides his view on the separation of accuracy CRs ==== General Revisions Deadline ==== Dimitris (Lenovo) propose to postpone Sihan(vivo) asks Dimitris (Lenovo) whether we can live with r03 + Editor's Note: whether the VFL server can indicate to the client which samples are used for accuracy monitoring is FFS? Dimitris (Lenovo) responds to Sihan Sihan(vivo) is okay with r03 removing normative changes + Editor's Note: whether the VFL server can indicate to the client which samples are used for accuracy monitoring is FFS Haiyang (Huawei) prefers to postpone if 'r04' after revision DDL only contains EN ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500677 | CR | Approval | 23.288 CR1362 (Rel-19, 'B'): VFL Accuracy Monitoring | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Belen (Ericsson) provides comments, suggests to postpone the CR Yuang(ZTE) provides comments Haiyang (Huawei) clarifies Haiyang (Huawei) provides r01 ==== General Revisions Deadline ==== Sihan(vivo) proposes to postpone this CR. Jingran(OPPO) also proposes to postpone this CR. Haiyang (Huawei) comments. Tingyu (Samsung) also proposes to postpone this CR. Belen (Ericsson) asks to postpone (or note if not part of the exception) ==== Comments Deadline ==== | Postponed |
| 19.15.2 | - | - | - | TS 23.288: Inference | - | - | Docs:=5 | - | |
| 19.15.2 | S2-2500334 | CR | Approval | 23.288 CR1333 (Rel-19, 'B'): Resolve some ENs in the vertical federated learning inference procedure | OPPO | Rel-19 | Issue #4 CC#4: r04 + EN agreed. Revised in CC#4 to S2-2501345, merging S2-2500140 | Xiaobo (vivo) provides comments and proposes to focus on Issue #3 for inference Thomas(Nokia) comments that it is not clear what topics are supposed to constitute issue 4 vs issue 3 and that a loft of conflicting changes are likely to be encountered as well as textual overlapps Suggest a merger for contributions related to inference. Jingran (OPPO) reply to Thomas(Nokia) and want to check whether Nokia is ok to merge S2-2500140 into S2-2500334 to use one CR for the VFL inference issue 3 discussion. Belen (Ericsson) supports this CR, suggests to use it as basis for VFL inference issue 3. Thomas (Nokia) provides r01 to merge S2-2500140 Jingran (OPPO) provides r02 Belen (Ericsson) provides r03 that includes a couple of questions Jingran (OPPO) provides r04 to update the cover page. Thomas(Nokia) is fine with r04 and asks to be added as source as a Nokia CR was merged ==== General Revisions Deadline ==== Belen (Ericsson) asks Jingran (OPPO) to add an EN on r04 Jingran (OPPO) is ok with r04 + Editor's Note: Parameters in the triggering of inference and Analytics is FFS Tingyu (Samsung) would like to co-sign ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501345 | CR | Approval | 23.288 CR1333R1 (Rel-19, 'B'): Resolve some ENs in the vertical federated learning inference procedure | OPPO, Nokia, Ericsson, Samsung | Rel-19 | Revision of S2-2500334r04 + EN, merging S2-2500140. This CR was agreed | Agreed | |
| 19.15.2 | S2-2501039 | CR | Approval | 23.288 CR1367 (Rel-19, 'B'): KI#2 update to VFL inference procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! Postponed in e-mail session | Xiaobo (vivo) provides comments and proposes to focus on Issue #1 for inference Jaewoo (LGE) provides comments. Jingran (OPPO) provides comments. Dimitris (Lenovo) comments Jaewoo (LGE) replies to Jingran (OPPO) and Dimitris (Lenovo). Thomas(Nokia) comments that the latest versions of 334 cover issue 1, but this CR hardly addresses it. Shares concerns about technical proposals in the CR Jingran (OPPO) replies to Jaewoo (LGE) Belen (Ericsson) raises concerns in this CR as well. Ulises (InterDigital) replies to Belen, Jingran and Jaewoo. ==== General Revisions Deadline ==== Belen (Ericsson) proposes to postpone or note this CR. No revision can be accepted. Ulises (InterDigital) replies to Belen, l agree to postpone this CR, let's have further offline discussions. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500140 | CR | Approval | 23.288 CR1315 (Rel-19, 'B'): KI#2: Updates to VFL inference procedures e.g to address trusted AF and handling of parameters from analytics request | Nokia | Rel-19 | Merged into S2-2501345 | Xiaobo (vivo) provides comments and proposes to focus on Issue #4 for inference Thomas (Nokia) corrects that he focuses on issue 3 Comments that CR contains nothing for issue 4. Issue Thomas (Nokia) provides r01 to focus on issue 4 Jingran (OPPO) provides r02 Thomas(Nokia) raises some concerns against r02 details Haiyang (Huawei) provides r03 to focus on parameters description Haiyang (Huawei) provides questions to some parameters Dimitris (Lenovo) has a question on the usage of the ADRF Belen (Ericsson) prefers to use 1 CR for the inference procedure, prefer S2-2500334 instead. Comments on added parameters and other topics. Thomas(Nokia) accepts merger into S2-2500334 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500676 | CR | Approval | 23.288 CR1361 (Rel-19, 'B'): Updates to VFL Inference Procedure | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Xiaobo (vivo) provides comments and proposes to focus on Issue #4 for inference Thomas(Nokia) comments that it is not clear what topics are supposed to constitute issue 4 vs issue 3 and that a loft of conflicting changes are likely to be encountered as well as textual overlapps Suggest a merger for contributions related to inference. Haiyang (Huawei) provides r01 to only focus on the procedure description Jingran (OPPO) provides comment Haiyang (Huawei) clarifies to Jingran (OPPO) Thomas(Nokia) provides r03, asks to ignore r02 provided by him in mistake, and raises concerns against previous versions Jingran (OPPO) reply to Haiyang (Huawei) and provides r04 Dimitris (Lenovo) comments Yuang(ZTE) provides comments Tingyu (Samsung) provides comments Jingran (OPPO) suggests to postpone this CR Haiyang (Huawei) provides r05 Jiahui (China Telecom) provides r06. Jingran (OPPO) provides r07. Sihan(vivo) supports r07 Yuang(ZTE) supports r07 Belen (Ericsson) raises objections to all revisions, mainly on step 1. Thomas (Nokia) provides r08 to revert controversial changes to step 1. Objects to all previous revisions apart from r03 Haiyang (Huawei) provides r09 ON TOP OF r08 Belen (Ericsson) replies to Huawei, r09 cannot be accepted, no revision can be accepted. Haiyang (Huawei) provides r10 ==== General Revisions Deadline ==== Belen (Ericsson) asks about r10 Haiyang(Huawei) replies to Belen (Ericsson) Belen (Ericsson) cannot accept r10, suggest to postpone the CR Tingyu (Samsung) cannot accept any revision and suggests postponing the CR ==== Comments Deadline ==== | Postponed |
| 19.15.2 | - | - | - | TS 23.288: Service Operations | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500145 | CR | Approval | 23.288 CR1236R5 (Rel-19, 'B'): KI#2: VFL services | Nokia | Rel-19 | Revision of S2-2412937. r03 agreed. Revised in e-mail session to S2-2501135. | Yuang(ZTE) provides comments and support this paper. Thomas (Nokia) provides r01. Belen (Ericsson) objects to r01, initial version, provides r02 Thomas (Nokia) objects to r02, provides r03 Belen (Ericsson) proposes to postpone the discussion on services, this will be easy to agree when procedures are stable. We object to r03 Yuang(ZTE) provide comments Belen (Ericsson) reiterates objections to r03, r01 and initial version, we can accept r02 Thomas(Nokia) raises concerns about postponing. This is a huge issue that would benefit from having two meetings. We should work with on service operations based on the latest TS version and not speculate on additional changes. ==== General Revisions Deadline ==== Aihua (CMCC) comments on r02. Thomas(Nokia) reiterates objection against r02. R02 contains additions that fundamentally change the service design and relate to additions to call flows which are not yet agreed. R03 tried a compromise by converting this to ENs. Suggsets discussing in CC ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501135 | CR | Approval | 23.288 CR1236R6 (Rel-19, 'B'): KI#2: VFL services | Nokia, Ericsson | Rel-19 | Revision of S2-2500145r03. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.288 General Description | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500268 | CR | Approval | 23.288 CR1329 (Rel-19, 'F'): EN removal for clarification of VFL high level description | KDDI | Rel-19 | Postponed in e-mail session | Yuang(ZTE) support this paper. Sohei (KDDI) provides r01 David (Apple) comments. Dimitris (Lenovo) supports comment from David (Apple) Tingyu (Samsung) shares the same view as David (Apple) and Dimitris (Lenovo). Sohei (KDDI) provides r03 Thomas (Nokia) provides r02 Thomas(Nokia) replies to Sohei, raises concerns against r03 Haiyang (Huawei) provides r04. Sohei (KDDI) provides r06. Yuang (ZTE) provides r05. Jaewoo (LGE) provides r07 to update coversheet. ==== General Revisions Deadline ==== Haiyang (Huawei) suggest to go with r07 with putting one EN back 'Editor's note: Accuracy monitoring in VFL is FFS'. Sohei(KDDI) is OK to add the EN proposed by Haiyang to r07 Belen (Ericsson) is okay with r03 and any previous revision, objects to all other revisions Thomas(Nokia) object r00 to r03, suggest postponing ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500565 | CR | Approval | 23.288 CR1345 (Rel-19, 'B'): Update of General Description for VFL | LG Electronics | Rel-19 | Proposed merged with S2-2500268 (postponed). Postponed | Jaewoo (LGE) is OK to merge this paper into S2-2500268. Xiaobo (vivo) provides comments and proposes to either postpone or merge into S2-2500268? ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.15.2 | - | - | - | TS 23.288 Multi procedures | - | - | Docs:=6 | - | |
| 19.15.2 | S2-2500232 | CR | Approval | 23.288 CR1327 (Rel-19, 'B'): Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, | Rel-19 | CC#4: Postponed | Yuang(ZTE) provides comment Haiyang (Huawei) provides comments, considering splitNN requires initial model distribution. Tingyu (Samsung) provides r01 and replies to Haiyang (Huawei) and Yuang (ZTE). Yuang (ZTE) replies Tingyu (Samsung), can accept this CR with or without the new note you proposed. Thomas(Nokia) raises concerns Tingyu (Samsung) provides r02, and replies to Thomas(Nokia) and thanks Yuang(ZTE) for the support. Haiyang (Huawei) provides concerns, suggests a way forward. Yuang(ZTE) replies Haiyang(Huawei) Tingyu (Samsung) replies to Haiyang (Huawei). Thomas (Nokia) provides r03, objects against previous revisions and original version Tingyu (Samsung) thanks Thomas (Nokia) for the support and provides r04. Belen (Ericsson) provides r05 with some EN on how aggregator is selected. Tingyu (Samsung) replies to Belen (Ericsson). Haiyang (Huawei) replies. ==== General Revisions Deadline ==== Thomas(Nokia) accepts r05 and supports Belen EN within David (Apple) would like to co-sign this CR. Yuang (ZTE) would like to co-sign this CR. Dimitris (Lenovo) also co-signs Jingran(OPPO) would like to co-sign this CR. Haiyang (Huawei) suggests to postpone. Tingyu (Samsung) cannot accept Haiyang (Huawei)'s LATE and wrong comments. Tingyu (Samsung) proposes to add an EN: whether and how the split ML models will be allocated to VFL clients that will share intermediate results with other VFL clients is FFS. ==== Comments Deadline ==== Haiyang (Huawei) comments, suggest to reword the EN as 'The feature of client sharing intermediate results relying on split ML models and distributed the splited model to the clients, how the split ML models will be allocated to VFL clients that will share intermediate results with other VFL clients is FFS'. Tingyu (Samsung) proposes a revised EN: The feature of client sharing intermediate results relying on For split ML models and distributed the splited model to the clients, how the split ML models will be allocated to VFL clients that will share intermediate results with other VFL clients is FFS | Postponed |
| 19.15.2 | S2-2500267 | CR | Approval | 23.288 CR1328 (Rel-19, 'B'): VFL procedure update for untrusted AF case. | KDDI | Rel-19 | Merged into S2-2501143 | Xiaobo (vivo) provides comments and proposes to focus on Issue #3 (VFL server discovery) Sohei (KDDI) proposes to merge to 1070. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500500 | CR | Approval | 23.288 CR1343 (Rel-19, 'B'): KI#2 Removing ENs regarding the roles of NEF | NTT DOCOMO | Rel-19 | Noted in e-mail session | Yuang(ZTE) provides comment Kohei (NTT DOCOMO) replies to Yuang (ZTE) Vivian(vivo) asks to merge or note this CR, since the two related ENs have been covered by other CRs Kohei (NTT DOCOMO) replies to Vivian (Vivo), and note is ok. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.15.2 | S2-2500567 | CR | Approval | 23.288 CR1347 (Rel-19, 'B'): Update Preparation and Training Procedure for VFL | LG Electronics | Rel-19 | Noted in e-mail session | Jaewoo (LGE) replies Xiaobo (vivo) and asks for clarification on Issue #3 for preparation or training. Xiaobo (vivo) provides comments and proposes to focus on Issue #3 for preparation Xiaobo (vivo) provides clarification and confirm to focus on Issue #3 for preparation instead of training. Jaewoo (LGE) replies to Xiaobo (vivo) and Thomas(Nokia). Thomas(Nokia) raises concerns that there are clashes with other CRs for preparation and training, e.g. S2-2500398 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.15.2 | S2-2500691 | CR | Approval | 23.288 CR1363 (Rel-19, 'B'): KI2: Addressing ENs for VFL . | Lenovo | Rel-19 | r02 agreedrevised in e-mail session to S2-2501145. | Xiaobo (vivo) provides comments and proposes to focus on Issue #5 Dimitris (Lenovo) comments Dimitris (Lenovo) provides r01 Thomas (Nokia) provides comments on r01 Dimitris (Lenovo) responds to Thomas Thomas (Nokia) provides r02. ==== General Revisions Deadline ==== Dimitris (Lenovo) is ok with r02 ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501145 | CR | Approval | 23.288 CR1363R1 (Rel-19, 'B'): KI2: Addressing ENs for VFL . | Lenovo | Rel-19 | Revision of S2-2500691r02. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500561 | CR | Approval | 23.501 CR5978 (Rel-19, 'B'): NWDAF discovery and selection parameters | LG Electronics | Rel-19 | r06 agreedrevised in e-mail session to S2-2501146. | Jaewoo (LGE) responds to Yuang(ZTE) and provides r01. Yuang(ZTE) provide comments. Yuang (ZTE) provides r04. Yuang (ZTE) would like to co-sign r03. Jaewoo (LGE) provides r03. Thomas (Nokia) provides r02. Belen (Ericsson) provides r05, objects to previous versions that needs updates Yuang (ZTE) supports r06. Sohei (KDDI) supports r06. Jaewoo (LGE) provides r06 based on r05. Thomas (Nokia) is fine with r06. Jihoon (ETRI) also supports r06 and would like to co-sign. ==== General Revisions Deadline ==== Jaewoo (LGE) is OK with r06. Belen (Ericsson) supports r06, ask to cosign. Haiyang (Huawei) supports r06. ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501146 | CR | Approval | 23.501 CR5978R1 (Rel-19, 'B'): NWDAF discovery and selection parameters | LG Electronics, Nokia, ZTE, KDDI, ETRI, Ericsson, Huawei | Rel-19 | Revision of S2-2500561r06. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.501 General description | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500081 | CR | Approval | 23.501 CR5882 (Rel-19, 'B'): KI#1 and KI#2 alignment | ZTE | Rel-19 | r04 agreedrevised in e-mail session to S2-2501147, merging S2-2500302 | Yuang(ZTE) provides r01. Yuang (ZTE) OK with r04. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501147 | CR | Approval | 23.501 CR5882R1 (Rel-19, 'B'): KI#2 alignment | ZTE, Nokia | Rel-19 | Revision of S2-2500081r04, merging S2-2500302. Approved | Agreed | |
| 19.15.2 | S2-2500302 | CR | Approval | 23.501 CR5918 (Rel-19, 'B'): VFL alignment in 23.501 | China Mobile | Rel-19 | Merged into S2-2501147 | Aihua(CMCC) is fine with the proposal of merging S2-2500302 into S2-2500081. Xiaobo (vivo) provides comments and proposes to merge S2-2500302 into S2-2500081 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500266 | CR | Approval | 23.502 CR5226 (Rel-19, 'B'): NRF enhancement for VFL inference service discovery | KDDI | Rel-19 | Merged into S2-2501148 | Sohei (KDDI) agrees to merge this CR to S2-2500660. Thomas (Nokia) comments that S2-2500660 contains similar changes and suggest a merger ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500660 | CR | Approval | 23.502 CR5266 (Rel-19, 'B'): Adding VFL related services supported by NEF and AF | Vivo | Rel-19 | r05 agreedrevised in e-mail session to S2-2501148, merging S2-2500266 | Belen (Ericsson) thinks that this CR is not needed, it overlaps with Nokia´s S2-2500145 to 23.288. Vivian (vivo) replies to Belen, and provide r01 to avoid overlap with S2-2500145. Sohei (KDDI) provides r03 and confirms merging S2-2500266 into S2-2500660. Thomas (Nokia) provides r02 Asks how to resolve overlap with S2-2500266 (merger?) Vivian (vivo) provides r04. Belen (Ericsson) comments that r04 and previous revisions are incomplete and should be aligned with S2-2500561 and S2-2501071 Vivian(vivo) provides r05, aligning with S2-2500561 and S2-2501071 ==== General Revisions Deadline ==== Haiyang (Huawei) suggest to add 'VFL interoperability indicator' in the NEF part for r05. Vivian (vivo) agrees 'VFL interoperability indicator' should also be added in the NEF part, sorry for missing that. Belen (Ericsson) objects to any revisions, as r05 does not include our comments, can accept it if fixed vivian (vivo) checked with related CRs(S2-25001070 and 0561), we have not approved 'NF type(s) and NWDAF Serving Area information and/or NF set ID(s) of the data source(s)' for trusted AF in 23.288 and 501, and asks whether Belen whether can live with r05 +'VFL interoperability indicator' in the NEF part in clause 5.2.7.2.5 Belen (Ericsson) accepts r05. vivian(vivo) then proposes to approve r05, other refinements we can leave to next meeting ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501148 | CR | Approval | 23.502 CR5266R1 (Rel-19, 'B'): Adding VFL related services supported by NEF and AF | Vivo, Nokia, KDDI | Rel-19 | Revision of S2-2500660r05, merging S2-2500266. Approved | Agreed | |
| 19.15.2 | - | - | - | KI#3: PCC related enhancements | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | TS 23.288 | - | - | Docs:=8 | - | |
| 19.15.2 | S2-2500188 | CR | Approval | 23.288 CR1321 (Rel-19, 'C'): Enabling QoS and Policy Assistance Analytics analyse and predict QoE for certain user plane latency | Verizon, Oracle | Rel-19 | WI Code should be AIML_CN! Merged into S2-2501149 | Tingyu (Samsung) proposes to merge S2-2500188 into S2-2500231 to have discussion under one email thread. ==== General Revisions Deadline ==== Zhang (Huawei) think the CR is already merged into S2-2500231 ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500231 | CR | Approval | 23.288 CR1326 (Rel-19, 'F'): Corrections on QoS and policy assistance analytics | Samsung, Ericsson | Rel-19 | r10 agreedrevised in e-mail session to S2-2501149, merging S2-2500188, S2-2500317, S2-2500353 and S2-2500402 | Tingyu (Samsung) provides r01 by merging S2-2500188, S2-2500317, S2-2500353, S2-2500402, per rapporteurs' guidance. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501149 | CR | Approval | 23.288 CR1326R1 (Rel-19, 'F'): Corrections on QoS and policy assistance analytics | Samsung, Ericsson, Verizon, Oracle, China Mobile, NTT DOCOMO, Huawei, HiSilicon, ETRI | Rel-19 | Revision of S2-2500231r10, merging S2-2500188, S2-2500317, S2-2500353 and S2-2500402. Approved | Agreed | |
| 19.15.2 | S2-2500317 | CR | Approval | 23.288 CR1332 (Rel-19, 'F'): Update of input data for QoS and Policy Assistance Analytics | China Mobile | Rel-19 | Merged into S2-2501149 | Tingyu (Samsung) proposes to merge S2-2500317 into S2-2500231 to have discussion under one email thread. Aihua(CMCC) is fine to merge S2-2500317 into S2-2500231. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500353 | CR | Approval | 23.288 CR1337 (Rel-19, 'F'): QoS and Policy Assistance Analytics update | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! Merged into S2-2501149 | Tingyu (Samsung) proposes to merge S2-2500353 into S2-2500231 to have discussion under one email thread. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500402 | CR | Approval | 23.288 CR1340 (Rel-19, 'F'): Resolving ENs for QoS and policy assistance analytics | Ericsson | Rel-19 | Merged into S2-2501149 | Tingyu (Samsung) proposes to merge S2-2500402 into S2-2500231 to have discussion under one email thread. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500838 | CR | Approval | 23.288 CR1255R2 (Rel-19, 'F'): Support of QoS policy assistance information analytics | CATT | Rel-19 | Revision of S2-2411512. r05 agreed. Revised in e-mail session to S2-2501150. | Jaewoo (LGE) provides comments on r01. Xiaoyan (CATT) provides r01. Xiaoyan (CATT) replies to Jaewoo (LGE). Zhang (Huawei) provide comments Jaewoo (LGE) replies Xiaoyan (CATT). Tingyu (Samsung) provides comments. Xiaoyan (CATT) provides r02. Bahador (NTT DOCOMO) provides comments. Tingyu (Samsung) provides comments and agrees with Bahador (NTT DOCOMO). Zhang (Huawei) provide comments and can live with r02 Changsik (ETRI) provides r03 Xiaoyan (CATT) replies and provides r05 as a cleanup. Tingyu (Samsung) is OK with r05. Belen (Ericsson) provides r06 Xiaoyan (CATT) replies to Belen (Ericsson). Tingyu (Samsung) replies. Belen (Ericsson) replies to Xiaoyan Belen (Ericsson) accepts r05 ==== General Revisions Deadline ==== Changsik (ETRI) is OK with r05 Jaewoo (LGE) is OK with r05. Zhang (Huawei) is OK with r05, r06 ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501150 | CR | Approval | 23.288 CR1255R3 (Rel-19, 'F'): Support of QoS policy assistance information analytics | CATT, ETRI | Rel-19 | Revision of S2-2500838r05. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.503 | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500230 | CR | Approval | 23.503 CR1328R3 (Rel-19, 'B'): Support for NWDAF-assisted policy control and QoS | Samsung | Rel-19 | Revision of S2-2411618. Merged into S2-2501151 | Xiaobo (vivo) provides comments and proposes to merge it into S2-2500401? Zhang (Huawei) also suggest to merge the CR into S2-2500401 Tingyu (Samsung) is OK to merge. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.15.2 | S2-2500401 | CR | Approval | 23.503 CR1303R3 (Rel-19, 'B'): PCF use of QoS and policy assistance information analytic | Ericsson | Rel-19 | Revision of S2-2411643. r04 agreed. Revised in e-mail session to S2-2501151, merging S2-2500230 | Zhang(Huawei) provides r01 Thomas(Nokia) provides r02 Tingyu (Samsung) would like to co-sign. Bahador (NTT DOCOMO) provides r03. Belen (Ericsson) provides r04 adding back the SDF template ==== General Revisions Deadline ==== Zhang (Huawei) is OK with r04 and co-sign ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501151 | CR | Approval | 23.503 CR1303R4 (Rel-19, 'B'): PCF use of QoS and policy assistance information analytic | Ericsson, Nokia, NTT DOCOMO | Rel-19 | Revision of S2-2500401r04, merging S2-2500230. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500354 | CR | Approval | 23.502 CR5237 (Rel-19, 'B'): QFI Change event | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! r01 agreed. Revised in e-mail session to S2-2501152. | Zhang(Huawei) provide comments Bahador (NTT DOCOMO) provides clarifications and r01 Belen (Ericsson) provides comments Tingyu (Samsung) provides comments. Bahador (NTT DOCOMO) provides comments. Zhang (Huawei) provides comments Bahador (NTT DOCOMO) provides r02. Zhang (Huawei) is OK with r02 Thomas(Nokia) raises concerns that application traffic 'change' is unclear Provides r03 to improve wording Bahador (NTT DOCOMO) provides clarification. Belen (Ericsson) comments Zhang (Huawei) share the view of Belen (E///) Bahador (NTT DOCOMO) responds Belen (Ericsson) and Zhang (Huawei) ==== General Revisions Deadline ==== Thomas(Nokia) replies Xiaoyan (CATT) objects to r02 and r03, prefer r00 or r01 or postponed. Bahador (NTT DOCOMO) replies Zhang (Huawei) propose to go for r01 ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501152 | CR | Approval | 23.502 CR5237R1 (Rel-19, 'B'): QFI Change event | NTT DOCOMO | Rel-19 | Revision of S2-2500354r01. Approved | Agreed | |
| 19.15.2 | - | - | - | KI#4: Signalling storm mitigation | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | TS 23.288 Signalling Storm Analytics | - | - | Docs:=4 | - | |
| 19.15.2 | S2-2500102 | CR | Approval | 23.288 CR1313 (Rel-19, 'F'): Clarifying Signalling Storm Analytics | Huawei, HiSilicon, China Telecom, SK Telecom, Verizon, NTT DOCOMO | Rel-19 | r01 agreedrevised in e-mail session to S2-2501153. | Magnus H (Ericsson) provides r01 Zhang (Huawei) is OK with r01 Yuang(ZTE) provide comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501153 | CR | Approval | 23.288 CR1313R1 (Rel-19, 'F'): Clarifying Signalling Storm Analytics | Huawei, HiSilicon, China Telecom, SK Telecom, Verizon, NTT DOCOMO | Rel-19 | Revision of S2-2500102r01. Approved | Agreed | |
| 19.15.2 | S2-2500633 | CR | Approval | 23.288 CR1354 (Rel-19, 'F'): Clarification and alignment on signalling storm analytics | China Telecom | Rel-19 | r01 agreedrevised in e-mail session to S2-2501154. | Zhang(Huawei) provide comments Jiahui (China Telecom) replies and provides r01. Zhang (Huawei) is OK with r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501154 | CR | Approval | 23.288 CR1354R1 (Rel-19, 'F'): Clarification and alignment on signalling storm analytics | China Telecom | Rel-19 | Revision of S2-2500633r01. Approved | Agreed | |
| 19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500153 | CR | Approval | 23.502 CR5200 (Rel-19, 'B'): KI#4 Resolve open issues for mitigation actions | Nokia | Rel-19 | r05 agreedrevised in e-mail session to S2-2501155. | Zhang(Huawei) provide comments Magnus H (Ericsson) cannot agree to make ENs to normative text Thomas (Nokia) provides r01. Zhang (Huawei) provides r02 Magnus (Ericsson) provides r03 Zhang (Huawei) object r03 and provides comments Magnus (Ericsson) objects to r00, r01,r02 Zhang (Huawei) provide r04 Thomas (Nokia) provide r05 ==== General Revisions Deadline ==== Zhang (Huawei) is OK with r05, r04, r02, object all other versions ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501155 | CR | Approval | 23.502 CR5200R1 (Rel-19, 'B'): KI#4 Resolve open issues for mitigation actions | Nokia | Rel-19 | Revision of S2-2500153r05. Approved | Agreed | |
| 19.15.2 | - | - | - | UE data collection related liasons | - | - | Docs:=8 | - | |
| 19.15.2 | S2-2500017 | LS In | Action | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-246299) | Rel-19 | Noted in e-mail session | Zhang (Huawei) suggests to NOTE the LS Hyesung (Samsung) also suggests to note this LS Yuang (ZTE) also suggests to note the LS Xiaobo (vivo) also propose to note this LS Yannick (Nokia) agrees to note this LS which has no specific action to SA2. Michael (Deutsche Telekom) also agrees to note this LS. | Noted |
| 19.15.2 | S2-2500020 | LS In | Information | LS from SA WG3: Reply LS on AIML data collection | SA WG3 (S3-245138) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Yannick (Nokia) agrees to note this LS which has no specific action to SA2. Michael (Deutsche Telekom) also agrees to note this LS. | Noted |
| 19.15.2 | S2-2500025 | LS In | Action | LS from RAN WG2: Reply LS to SA WG2 on AIML data collection | RAN WG2 (R2-2411152) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Xiaobo (vivo) propose to postpone this LS as it may be related to the discussion of R20 UE data collection Yannick (Nokia) suggests noting this LS which has no specific action to SA2 beyond taking information into account. The RAN2 feedback will need to be taken into account if and when we start studying the different options for UE data collection in SA2. One suggestion, to remind ourselves about this RAN2 feedback, would be to include the LS reference into the related work task(s) description in a potential SA2 SID. | Noted |
| 19.15.2 | S2-2500024 | LS In | Action | LS from RAN WG2: Reply LS to SA WG5 on AIML data collection | RAN WG2 (R2-2411114) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Xiaobo (vivo) also propose to note this LS Yannick (Nokia) agrees to note this LS which has no specific action to SA2. Michael (Deutsche Telekom) also agrees to note this LS. | Noted |
| 19.15.2 | S2-2500026 | LS In | Information | LS from RAN WG3: Reply LS on AIML data collection | RAN WG3 (R3-247801) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Yannick (Nokia) agrees to note this LS which has no specific action to SA2. | Noted |
| 19.15.2 | S2-2500055 | LS In | Action | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN (RP-243316) | Rel-19 | Postponed in e-mail session | Xiaobo (vivo) also propose to note this LS as there is no specific action to SA2 Mehrdad (Mediatek Inc.) suggests to postpone but NOT to note the LS. There is action required within the LS that may not happen in SA2 Rel-19 but we still have to consider the action in scoping for Rel-20. Zhang (Huawei) suggest to postpone the LS. RAN need to know SA2 timeline, we can only provide timeline information after SA plenary in March. Yannick (Nokia) also prefers to postpone this LS. | Postponed |
| 19.15.2 | S2-2500069 | LS In | Information | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-247219) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Yannick (Nokia) agrees to note this LS which has no specific action to SA2. | Noted |
| 19.15.2 | S2-2500071 | LS In | Information | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-247336) | Rel-19 | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) also proposes to NOTE the LS Xiaobo (vivo) also propose to note this LS. Yannick (Nokia) agrees to note this LS which has no specific action to SA2. | Noted |
| 19.15.2 | - | - | - | General | - | - | Docs:=7 | - | |
| 19.15.2 | S2-2500004 | LS In | Action | LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3186 (ex Y.IMT2020-DJLML) 'Requirements and framework for distributed joint learning to enable machine learning in future networks including IMT-2020' | ITU-T SG13 (SG13-LS170) | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) agrees to NOTE the LS | Noted | |
| 19.15.2 | S2-2500009 | LS In | Action | LS from SA WG5: LS reply on terminology definitions for AI-ML in NG-RAN | SA WG5 (S5-244660) | Noted in e-mail session | Zhang(Huawei) suggests to NOTE the LS Yuang(ZTE) agrees to NOTE the LS | Noted | |
| 19.15.2 | S2-2500041 | LS In | Information | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 (R1-2410922) | Rel-19 | Responses drafted in S2-2500320, S2-2500827. CC#4: Postponed | Yuang (ZTE) also proposes to note this LS in or sending a simple feedback that this is not in the scope of Rel-19. Hyesung (Samsung) also proposes to note this LS in. Haiyang (Huawei) proposes to note the LS IN and wait for RAN2 progress. David (Apple) comments, a reply LS is highly desirable to avoid the same problems as for UE-sided data collection in R19. Haiyang (Huawei) proposes to note this LS and wait for RAN(2) progress Thomas(Nokia) also proposes to note this LS Yuang(ZTE) also proposes to note this LS David (Apple) suggests to focus the discussion on S2-2500320 where different opinions have been expressed, and decide the disposition of this LS in according to the S2-2500320 result Juan Zhang (Qualcomm) also proposed to focus on the reply LS first and then we make the decision for this LS in. Zhang (Huawei) propose to postpone the LS | Postponed |
| 19.15.2 | S2-2500320 | LS OUT | Approval | [DRAFT] Reply LS on Signalling feasibility of data set and parameter sharing | Qualcomm Germany | Rel-19 | Response to S2-2500041. CC#4: Postponed | Hyesung (Samsung) also proposes to note this LS out. Yuang (ZTE) also proposes to note this LS out or sending a simple feedback that this is not in the scope of Rel-19. Haiyang (Huawei) proposes to note the LS OUT. Juan Zhang (Qualcomm) provides r01 based on the CC discussion. David (Apple) comments and provides r02. Mehrdad (Mediatek Inc.) comments on all revisions of this LS. We suggest to Postpone this LS reply until we get more feedback from RAN2. Haiyang (Huawei) suggests to note this LS OUT Belen (Ericsson) prefers to send an LS reply, both r01 or r02 are fine. Dimitris (Lenovo) support sending an LS reply Xiaobo (vivo) support to send the LS reply as it may have SA2 impact and SA2 should be involved as early as possible. Bahador (NTT DOCOMO) provides comments and r03. David (Apple) can live with r03 Juan Zhang (Qualcomm) is fine with r03. Yuang (ZTE) is fine with r03, object any other revisions. Yuang(ZTE) prefers r05, can live with r04 r03, object otther revisions Hyesung (Samsung) still does NOT think that LS reply is needed. Thomas(Nokia) provides r05. Mehrdad (Mediatek Inc.) provides r04 and objects to original version, r01, r02 and r03. Zhang (Huawei) object the LS Mehrdad (Mediatek Inc.) is ok with r04, r05 but objects to rest of revisions. David (Apple) cannot accept r05, provides r06. Juan Zhang (Qualcomm) prefer r03, r04, r06, can not agree with r05. ==== General Revisions Deadline ==== Yuang(ZTE) support r05, can live with r04, object any other revisions and original LS. Haiyang (Huawei) still see no need for the LS OUT, suggest to note. Hyesung (Samsung) objects to this LS. David (Apple) requests this LS to be opened at CC#3 or CC#4, finds objections to this LS OUT unreasonable. Zhang (Huawei) provides response to David (Apple) David (Apple) replies to Huawei. Juan Zhang (Qualcomm) supports David's (Apple) proposal to discussion at CC#3 or CC#4. Mehrdad (Mediatek Inc.) is only ok with r04, r05 but objects to rest of revisions. David (Apple) requests clarification from Mediatek on objection to r06. Mehrdad (Mediatek Inc.) replies to Apple. David (Apple) replies and provides r07. Mehrdad (Mediatek Inc.) is ok with r04, r05. Can live with r07 but objects to rest of revisions. ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500827 | LS OUT | Approval | [DRAFT] Reply LS on Signalling feasibility of data set and parameter sharing | Apple | Rel-19 | Response to S2-2500041. Proposed merged with S2-2500320 (postponed). Postponed | Hyesung (Samsung) also proposes to note this LS out. Yuang (ZTE) also proposes to note this LS out or sending a simple feedback that this is not in the scope of Rel-19. Haiyang (Huawei) proposes to note the LS OUT. David (Apple) suggests to mark this document as merged into S2-2500320. Mehrdad (Mediatek Inc.) suggest to Mark this LS reply as merged into S2-2500320 or noted . Haiyang (Huawei) suggest to note this LS OUT ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.15.2 | S2-2500501 | CR | Approval | 23.288 CR1344 (Rel-19, 'C'): Addition of delay threshold match indication | Verizon, Oracle | Rel-19 | WI Code should be AIML_CN! r02 agreed. Revised in e-mail session to S2-2501156. | Peretz (Verizon) provides r01 swapping 'N1' with 'Uu' for RAN delay. Zhang (Huawei) provide comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.15.2 | S2-2501156 | CR | Approval | 23.288 CR1344R1 (Rel-19, 'C'): Addition of delay threshold match indication | Verizon, Oracle | Rel-19 | Revision of S2-2500501r02. Approved | Agreed | |
| 19.15.2 | - | - | - | Exceeding quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | KI#1: AIML support for LMF positioning | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | TS 23.273 General | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500197 | CR | Approval | 23.273 CR0641 (Rel-19, 'B'): Resolution of editor s notes related to data collection and model retrieval | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500591 | CR | Approval | 23.273 CR0651 (Rel-19, 'F'): Updates of MTLF discovery and selection for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.273 Data Exposure/ NWDAF Input data collection | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500112 | CR | Approval | 23.273 CR0636 (Rel-19, 'B'): KI#1: Resolving open issues for LMF data exposure | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500654 | CR | Approval | 23.273 CR0653 (Rel-19, 'B'): Update input data to adapt model performance monitoring | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.273 Data collection from RAN and UE | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500193 | CR | Approval | 23.273 CR0639 (Rel-19, 'B'): KI#1 Addressing the leftovers in the WI Exception on whether and how LMF can take NG-RAN load into account when performing data collection | Sony | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 General | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500086 | CR | Approval | 23.288 CR1305 (Rel-19, 'B'): Clarification of Nnwdaf_MLModelProvision service | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500087 | CR | Approval | 23.288 CR1306 (Rel-19, 'B'): Adding new service consumer for ML Model monitoring in AIML based positioning | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500592 | CR | Approval | 23.288 CR1348 (Rel-19, 'F'): Updates of ML model provisioning services for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 Performance monitoring | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500593 | CR | Approval | 23.288 CR1349 (Rel-19, 'F'): Update of AI/ML model performance monitoring for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500835 | CR | Approval | 23.288 CR1365 (Rel-19, 'F'): Clarification on model performance monitoring for LMF-based AI/ML Positioning | CATT | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.501 | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500109 | CR | Approval | 23.501 CR5665R2 (Rel-19, 'B'): KI#1: New LMF Data Exposure service | Nokia | Rel-19 | Revision of S2-2411362 Not Handled | - | |
| 19.15.2 | S2-2500110 | CR | Approval | 23.501 CR5507R3 (Rel-19, 'B'): KI#1: Extending NWDAF description to cover model provisioning to LMF | Nokia | Rel-19 | Revision of S2-2411364 Not Handled | - | |
| 19.15.2 | S2-2500589 | CR | Approval | 23.501 CR5979 (Rel-19, 'B'): Enhancements of MTLF discovery and selection for LMF-based AIML Positioning | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500111 | CR | Approval | 23.502 CR5126R1 (Rel-19, 'B'): KI#1 AMF exposing RAN overload to LMF | Nokia | Rel-19 | Revision of S2-2411365 Not Handled | Yuang(ZTE) supports this CR. Thomas(Nokia) comments that this CR will not be handled | - |
| 19.15.2 | S2-2500590 | CR | Approval | 23.502 CR5257 (Rel-19, 'B'): Enhancements of MTLF discovery and selection for LMF-based AIML Positioning | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | KI#2: Vertical Federated Learning | - | - | Docs:=0 | - | |
| 19.15.2 | - | - | - | TS 23.288 Definitions | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500146 | CR | Approval | 23.288 CR1173R3 (Rel-19, 'B'): KI#2: VFL definitions | Nokia | Rel-19 | Revision of S2-2411376 Not Handled | - | |
| 19.15.2 | S2-2500082 | CR | Approval | 23.288 CR1301 (Rel-19, 'B'): VFL definitions | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 Registration and Discovery | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500336 | CR | Approval | 23.288 CR1335 (Rel-19, 'B'): Resolve some ENs related to the VFL server and client Registration and Discovery | OPPO | Rel-19 | Not Handled | Haiyang (Huawei) provides r01. | - |
| 19.15.2 | S2-2500141 | CR | Approval | 23.288 CR1316 (Rel-19, 'B'): KI#2: Updates to VFL discovery procedures e.g to address trusted AF | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500674 | CR | Approval | 23.288 CR1359 (Rel-19, 'B'): Update the Registration and Discovery procedures for VFL | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 VFL Preparation | - | - | Docs:=5 | - | |
| 19.15.2 | S2-2500142 | CR | Approval | 23.288 CR1317 (Rel-19, 'B'): KI#2: Updates to VFL preparation procedures e.g to address trusted AF | Nokia | Rel-19 | Revised to S2-2501016 | Revised | |
| 19.15.2 | S2-2501016 | CR | Approval | 23.288 CR1317R1 (Rel-19, 'B'): KI#2: Updates to VFL preparation procedures e.g to address trusted AF | Nokia | Rel-19 | Revision of S2-2500142 Not Handled | - | |
| 19.15.2 | S2-2500202 | CR | Approval | 23.288 CR1325 (Rel-19, 'B'): NEF work during VFL preparation procedure | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500673 | CR | Approval | 23.288 CR1358 (Rel-19, 'B'): Update the preparation procedure for VFL | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500337 | CR | Approval | 23.288 CR1336 (Rel-19, 'B'): Add the trusted AF as the server case in the VFL preparation procedure | OPPO | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 VFL Training | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500085 | CR | Approval | 23.288 CR1304 (Rel-19, 'B'): Clarifications on intermediate training result and intermediate model training information | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500139 | CR | Approval | 23.288 CR1314 (Rel-19, 'B'): KI#2: Updates to VFL training procedures e.g to address trusted AF | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500675 | CR | Approval | 23.288 CR1360 (Rel-19, 'B'): Updates to VFL Training Procedure | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 Accuracy monitoring | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500656 | DISCUSSION | Discussion | Discussion for the accuracy monitoring of VFL training | vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 VFL Inference | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500084 | CR | Approval | 23.288 CR1303 (Rel-19, 'B'): Clarifications on VFL inference | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 Service Operations | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500143 | DISCUSSION | Discussion | KI#2: New Services for VFL. | Nokia | Rel-19 | Revision of S2-2411373 Not Handled | - | |
| 19.15.2 | S2-2500657 | CR | Approval | 23.288 CR1356 (Rel-19, 'B'): Adding VFL related service operations | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500658 | CR | Approval | 23.288 CR1357 (Rel-19, 'B'): Update on the contents of VFL related services | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 General Description | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2501072 | CR | Approval | 23.288 CR1372 (Rel-19, 'B'): KI#2 update to VFL High Level Description | InterDigital | Rel-19 | Missing CR Number - CR states -! Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.288 Other | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500150 | CR | Approval | 23.288 CR1318 (Rel-19, 'F'): KI#2: Model training service is not applicable for VFL | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500201 | CR | Approval | 23.288 CR1324 (Rel-19, 'B'): Interaction between consumer and VFL server | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500233 | DISCUSSION | Discussion | Discussion on VFL model training and inference with client intermediate results sharing between VFL clients . | Samsung | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=3 | - | |
| 19.15.2 | S2-2500148 | CR | Approval | 23.501 CR5892 (Rel-19, 'B'): VFL support for the discovery of NWDAF, NEF, and AF instances | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500632 | CR | Approval | 23.501 CR5985 (Rel-19, 'B'): Support on registration and discovery of VFL server and client | China Telecom | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500659 | CR | Approval | 23.501 CR5986 (Rel-19, 'B'): Update for VFL related NF discovery | Vivo | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500144 | CR | Approval | 23.501 CR5676R2 (Rel-19, 'B'): KI#2: VFL services | Nokia | Rel-19 | Revision of S2-2411375 Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.501 General description | - | - | Docs:=1 | - | |
| 19.15.2 | S2-2500147 | CR | Approval | 23.501 CR5598R3 (Rel-19, 'B'): KI#2 NEF extensions for VFL | Nokia | Rel-19 | Revision of S2-2411378 Not Handled | - | |
| 19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500149 | CR | Approval | 23.502 CR5199 (Rel-19, 'B'): VFL support for the discovery of NWDAF, NEF, and AF instances | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500355 | CR | Approval | 23.502 CR5238 (Rel-19, 'F'): Exposure of control plane signalling information from NFs | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! Not Handled | Li(vivo) asks for revisions before approval. Bahador (NTT DOCOMO) clarified that the paper is not handled in this meeting. Magnus (Ericsson) agree with Li (vivo) and suggests a note | - |
| 19.15.2 | - | - | - | KI#3: PCC related enhancements | - | - | Docs:=9 | - | |
| 19.15.2 | S2-2500151 | CR | Approval | 23.288 CR1319 (Rel-19, 'B'): QoS and policy assistance analytics update and EN resolution | Nokia | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500348 | CR | Approval | 23.288 CR1131R3 (Rel-19, 'B'): Enhancements to Analytics IDs to support QoS and policy | Samsung, vivo, OPPO, SK Telecom, InterDigital Inc | Rel-19 | Revision of S2-2411620 Not Handled | - | |
| 19.15.2 | S2-2500603 | CR | Approval | 23.288 CR1350 (Rel-19, 'B'): KI#3: EN resolution for QoS and Policy Assistance analytics | ETRI | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500604 | CR | Approval | 23.288 CR1351 (Rel-19, 'F'): KI#3: Clarification on QoS and policy assistance analytics | ETRI | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500836 | CR | Approval | 23.288 CR1366 (Rel-19, 'F'): Corrections on QoS and Policy Assistance Analytics | CATT | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500152 | CR | Approval | 23.503 CR1427R1 (Rel-19, 'B'): Support of QoS and policy assistance analytics | Nokia | Rel-19 | Revision of S2-2411386 Not Handled | - | |
| 19.15.2 | S2-2500672 | CR | Approval | 23.503 CR1340R2 (Rel-19, 'F'): Update on Policy decisions based on network analytics | Huawei, HiSilicon | Rel-19 | Revision of S2-2409791 Not Handled | - | |
| 19.15.2 | S2-2500839 | CR | Approval | 23.503 CR1311R3 (Rel-19, 'F'): Policy decisions based on QoS policy assistance information analytics | CATT | Rel-19 | Revision of S2-2411513. Confirm Spec version used - CR states {19.1.0}! Not Handled | - | |
| 19.15.2 | S2-2500837 | CR | Approval | 23.502 CR5291 (Rel-19, 'F'): Event exposure for QoS and Policy Assistance Analytics | CATT | Rel-19 | Not Handled | - | |
| 19.15.2 | - | - | - | KI#4: Signalling storm mitigation | - | - | Docs:=2 | - | |
| 19.15.2 | S2-2500096 | CR | Approval | 23.288 CR1312 (Rel-19, 'B'): Adding data collection source | ZTE | Rel-19 | Not Handled | - | |
| 19.15.2 | S2-2500101 | CR | Approval | 23.501 CR5885 (Rel-19, 'F'): Correction on usage of signalling storm analytics for reliability of NF services | Huawei, HiSilicon | Rel-19 | Not Handled | - | |
| 19.16 | - | - | - | Indirect Network Sharing (TEI19_NetShare) | - | - | Docs:=12 | - | |
| 19.16 | S2-2500342 | CR | Approval | 23.501 CR5925 (Rel-19, 'F'): Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | China Unicom, Ericsson | Rel-19 | Not handled at CC#4. Postponed | Fenqin (Huawei) provide comments and prefer to have a solution defined to resolve this issue. Tianqi (China Unicom) prefers the N3GPP (e.g. via N3IWF) aspect should be resolved in the TEI19_NetShare by the clarification in NOTE. Tianqi (China Unicom) as the rapporteur to trigger the discussion on whether the N3GPP (e.g. via N3IWF) aspect should be resolved in the TEI19_NetShare by 1) clarification in NOTE or 2) new solution or 3) another view. Myungjune (LGE) prefers not to resolve this issue. Jinguo(ZTE) comments and agree the solutions need further discussion. Kundan (NEC) provide comments and prefer to have a solution defined to resolve this issue. Jinguo(ZTE) provides answer to Kundan Laurent (Nokia): provides r01 Tianqi (China Unicom) provided r02. Fenqin (Huawei) provided r03. Kundan (NEC) provides comment on r01. How the N3IWF knows the UE is currently registered to hosting network over 3GPP accesss? Haris(Qualcomm) comments on r02 Kundan(NEC) clarifies to Tianqi. Fenqin (Huawei) provides comments. Tianqi (China Unicom) comments on r08 and suggests to check r07. Tianqi (China Unicom) provides r07 and responses. Kundan(NEC) provides r08. Fenqin(Huawei) provides r06 Haris(Qualcomm) provides r05 Laurent (Nokia): provides r04 Laurent (Nokia): Answers and Comments further Fenqin(Huawei) responds to Kundan. Kundan(NEC) responds to Fenqin. Fenqin(Huawei) responds to Kundan again. Laurent (Nokia): provides r09 Tianqi (China Unicom) provides r10. Kundan (NEC): is fine with r09. Fenqin (Huawei) provides r11. Laurent (Nokia): provides r12 Kundan (NEC): responds to Laurent. Tianqi (China Unicom) provides r13 Kundan (NEC): provides r14. R14 = r11 + EN (CT grp will take care of Ens). Laurent (Nokia): provides r15 Tianqi (China Unicom) is not ok with r15 and give r16 based on r11. Haris(Qualcomm) objects to r16 Tianqi (China Unicom) provides r17 and r18 based on Haris comment. Laurent (Nokia): provides r19 Laurent (Nokia): provides r20 and R21 Kundan (NEC): fine with r20. Tianqi (China Unicom) provides r22 based on r21. Laurent (Nokia): provides r24 Tianqi (China Unicom) provides r25 based on r24. Omkar (CableLabs) comments. Laurent (Nokia): provides r26 Kundan (NEC): provides r27. R25+ normative text as EN Omkar (CableLabs) provides r28 Tianqi (China Unicom) provide r29 based on r25. ==== General Revisions Deadline ==== Fenqin (Huawei) provide r30 based on r29. Haris(Qualcomm) proposes alternative wording for EN Tianqi (China Unicom) refines the EN. Qian (Ericsson) provides comments and proposes (on top of r30): 1)Remove the EN, 2) add this text 'If none of these two options above can be used, the network can reject the UE access via non-3GPP access to 5GC of HPLMN with an existing cause value that will not allow access to HPLMN via non-3GPP access to 5GC when it detects the UE has been registered to its HPLMN ID over 3GPP access via Indirect Network Sharing.' in the NOTE. Kundan (NEC) have questions on r30. Myungjune (LGE) supports r31 in draft folder. Tianqi (China Unicom) prefers r31. Kundan (NEC) is fine with r31 in draft folder. Hope to see progress in CT groups. Qian (Ericsson) indicates (provided in previous comment as well) the r31 is based on top of r30 with following change: 1)Remove the EN, 2) add this text 'If none of these two options above can be used, the network can reject the UE access via non-3GPP access to 5GC of HPLMN with an existing cause value that will not allow access to HPLMN via non-3GPP access to 5GC when it detects the UE has been registered to its HPLMN ID over 3GPP access via Indirect Network Sharing.' in the NOTE. Haris(Qualcomm) object to r31 and proposes 3 alternative options for the proponents to choose Kundan(NEC) indicates that r31 is identical to r28 and r28 was uploaded in time. So we should consider r28. Haris(Qualcomm) objects to r28 (for same reasons as explained in email about r31) Kundan(NEC) is fine with option A and option B but prefers option A. Qian (Ericsson) is fine with 'modified' option C (i.e. removing the last sentence in the proposal) and 'modified' A (i.e. change 'shall reject' to 'rejects'). Fenqin (Huawei) is fine with R28 with the change as OPTION A as suggested below. Tianqi (China Unicom) can live with option A/B/C below and please share your preference. Tianqi (China Unicom) proposes to approve r30 with the change: 1) remove the EN; 2) add the normative text 'If none of these two options in the NOTE X can be used, the network rejects the UE access via non-3GPP access (e.g. via N3IWF) to 5GC of HPLMN with an existing cause value that will not allow access to HPLMN via non-3GPP access (e.g. via N3IWF) to 5GC when it detects the UE has been registered to its HPLMN ID over 3GPP access via Indirect Network Sharing.' below the NOTE X. Kundan(NEC) agrees with the proposal from Tianqi. Haris(Qualcomm) is ok with the proposal from Tianqi Laurent (Nokia):iss ok with the proposal from Tianqi: R30 minus EN+ normative text for rejection (option A of Haris) Fenqin(Huawei) is OK with the proposal from Tianqi(China Unicom) Laurent (Nokia): objects to any version where it is not specified that If none of these two options above can be used, the network shall reject the UE access via non-3GPP access to 5GC Qian (Ericsson) is ok with the proposed changes from Tianqi (China Unicom) below on top of r30 Jinguo(ZTE) is OK with the proposal from Tianqi(China Unicom) Omkar (CableLabs): We prefer r28. We can live with R30 minus EN+ normative text for rejection 'the network shall', however fail to understand why the rejection has to be specified for non-3GPP access and not be driven by operator policy. Tianqi (China Unicom) proposes to approve r30 with the change: 1) remove the EN; 2) add the normative text 'If none of these two options in the NOTE X can be used, the network shall reject the UE access via non-3GPP access (e.g. via N3IWF) to 5GC of HPLMN with an existing cause value that will not allow access to HPLMN via non-3GPP access (e.g. via N3IWF) to 5GC when it detects the UE has been registered to its HPLMN ID over 3GPP access via Indirect Network Sharing.' below the NOTE X. Qian (Ericsson) comments that we are not ok with the 'shall' since it's not logically correct and there area may be other means that we have not explored and can be achieved by operator deployment/implementation. Qian (Ericsson) comments that we object to any revision with 'shall' to mandate the rejection after the two methods in the note and excluding other potential implementation based solutions. ==== Comments Deadline ==== Qian (Ericsson) indicates R28 is ok as well. Laurent (Nokia): objects to R28. Can live with 'rejects' and 'shall reject' Haris(Qualcomm) ok with rejects instead of shall reject | Postponed |
| 19.16 | S2-2500343 | CR | Approval | 23.501 CR5926 (Rel-19, 'F'): Clarification on network slice in the case of Indirect Network Sharing | China Unicom, Huawei, ZTE | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501310. | Tianqi (China Unicom) responses. Laurent (Nokia): Comments Qian (Ericsson) asks questions Myungjune (LGE) responses to Fenqin (Huawei). Fenqin (Huawei) comments. Myungjune (LGE) comments. Tianqi (China Unicom) responses to prove the necessity of this CR. Myungjune (LGE) responses to Tianqi (China Unicom). Tianqi (China Unicom) provides r01 based on the comments. Tianqi (China Unicom) provides r03 and please ignore r02. ==== General Revisions Deadline ==== Myungjune (LGE) is ok with r03 Fenqin (Huawei) is ok with r03 Tianqi (China Unicom) is ok with r03 Jinguo(ZTE) is OK with r03 ==== Comments Deadline ==== | Revised |
| 19.16 | S2-2501310 | CR | Approval | 23.501 CR5926R1 (Rel-19, 'F'): Clarification on network slice in the case of Indirect Network Sharing | China Unicom, Huawei, ZTE | Rel-19 | Revision of S2-2500343r03. Approved | Agreed | |
| 19.16 | S2-2500614 | CR | Approval | 23.501 CR5982 (Rel-19, 'F'): Clarification of the UE registration in the INS case | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Laurent (Nokia): Proposes to merge in 0342 (not mine but Tdoc of the rapporteur) Fenqin (Huawei): Proposes r01 Qian (Ericsson): objects this paper and any normative text related to the handling of N3GPP aspect as it's not part of the scope. We continue the discussion in 0342 Fenqin (Huawei): Proposes r02 ==== General Revisions Deadline ==== Haris(Qualcomm) indicates that the NOTE in r02 is in conflict with 0342 hence we should resolve the text there. This CR should be noted Qian (Ericsson) indicates also the topic is addressed in 0342. This CR should be noted or considered merged Tianqi (China Unicom) suggests to merge this CR into 0342. Fenqin (Huawei) suggest to check r02 as it cover different direction comparing to 0342. ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500670 | CR | Approval | 23.503 CR1337R2 (Rel-19, 'F'): Correction on UE Policy from VPLMN in INS | Huawei, HiSilicon, ZTE | Rel-19 | Revision of S2-2408959. Noted in e-mail session | Tianqi (China Unicom) provided r01 Yang (OPPO) comments and provide r02 Tianqi (China Unicom) provided r03 and responses. Laurent (Nokia): Comments Tianqi (China Unicom) responses. Myungjune (LGE) provides comments. Yang (OPPO) further comments Haiyang(Huawei) seeks clarification from Haris(Qualcomm) Haris(Qualcomm) comments that the CR is likely not needed Qian (Ericsson) comments that this paper can be NOTED Haiyang(Huawei) replies, provide r04 Haris(Qualcomm) continues to think the CR is unecessary. R04 is not acceptable Myungjune (LGE) replies to Haiyang(Huawei) ==== General Revisions Deadline ==== Haiyang(Huawei) OK to note this paper ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500671 | CR | Approval | 23.502 CR5268 (Rel-19, 'F'): Update UE context for INS | Huawei, HiSilicon, China Unicom | Rel-19 | Noted in e-mail session | Tianqi (China Unicom) provides r01. Laurent (Nokia): Comments Haiyang (Huawei) replies to Laurent (Nokia) . Myungjune (LGE) asks question. Qian (Ericson) asks questions. Haiyang (Huawei) replies . ==== General Revisions Deadline ==== Haris(Qualcomm) thinks the CR is not needed Qian (Ericsson) propose to NOTE the paper Haiyang (Huawei) suggests to go with r01, replies to Myungjune, Qian and Haris . Myungjune (LGE) responses to Haiyang (Huawei). Myungjune (LGE) thinks that CR is not needed. Haiyang (Huawei) replies to Myungjune . Myungjune(LGE) replies to Haiyang (Huawei) Qian (Ericsson) propose to NOTE or POSTPONE this paper. ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500876 | CR | Approval | 23.501 CR6023 (Rel-19, 'F'): Clarification on non 3GPP access registration when the UE is registered for 3GPP access via indirect network sharing | ZTE | Rel-19 | Proposed merged with S2-2500342 (postponed). Postponed | Laurent (Nokia): Proposes to merge in 0342 (not mine but that of the rapporteur) Qian (Ericsson) propose also to merge this into 0342 ==== General Revisions Deadline ==== Tianqi (China Unicom) suggests to merge this CR into 0342. ==== Comments Deadline ==== | Postponed |
| 19.16 | S2-2500916 | DISCUSSION | Agreement | Discussion handling of 3GPP and non-3GPP access registration in INS | NEC Corporation | Rel-19 | Noted in e-mail session | Tianqi (China Unicom) suggests to note this Discussion Paper. ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500920 | CR | Approval | 23.501 CR6038 (Rel-19, 'F'): Handling of 3GPP and non-3GPP access registration in INS-option 1 | NEC | Rel-19 | Noted in e-mail session | Laurent (Nokia): Proposes to merge in 0342 (not mine but Tdoc of the rapporteur) Qian (Ericsson) proposes to NOTE this paper as this option has UE impact which is excluded from the WID. ==== General Revisions Deadline ==== Tianqi (China Unicom) proposes to NOTE this CR with the same view as others. ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500922 | CR | Approval | 23.501 CR6039 (Rel-19, 'F'): Handling of 3GPP and non-3GPP access registration in INS-option 2 | NEC | Rel-19 | Proposed merged with S2-2500342 (postponed). Postponed | Laurent (Nokia): Proposes to merge in 0342 (not mine but Tdoc of the rapporteur) Qian (Ericsson) supports the proposal of merging into 0342 ==== General Revisions Deadline ==== Tianqi (China Unicom) suggests to merge this CR into 0342. ==== Comments Deadline ==== | Postponed |
| 19.16 | S2-2500923 | CR | Approval | 23.501 CR6040 (Rel-19, 'F'): GUAMI allocation for indirect network sharing | NEC, Nokia | Rel-19 | Noted in e-mail session | Tianqi (China Unicom) provides r01. Qian (Ericsson) provides comments. Kundan (NEC) responds to Qian(Ericsson) . Kundan(NEC) is fine with r01. Qian(Ericsson) provides further comments and ask further questions. Kundan(NEC) provides further clarifications to Qian(Ericsson). Qian(Ericsson) comments. Haris(Qualcomm) thinks the CR is not needed ==== General Revisions Deadline ==== Qian (Ericsson) shares the same view that the CR can be NOTED. ==== Comments Deadline ==== | Noted |
| 19.16 | S2-2500991 | CR | Approval | 23.501 CR6044 (Rel-19, 'F'): Indirect Network Sharing and Non 3GPP access | Nokia | Rel-19 | Proposed merged with S2-2500342 (postponed). Postponed | Laurent (Nokia): provides r01 Josep (Deutsche Telekom) asks to add the AI to the subject Laurent (Nokia): Proposes to merge in 0342 (not mine but Tdoc of the rapporteur) ==== General Revisions Deadline ==== Tianqi (China Unicom) suggests to merge this CR into 0342. ==== Comments Deadline ==== | Postponed |
| 19.17 | - | - | - | Architecture support of roaming value-added services (TEI19_RVAS) | - | - | Docs:=0 | - | |
| 19.18 | - | - | - | Minimize the Number of Policy Associations (TEI19_MINPA) | - | - | Docs:=0 | - | |
| 19.19 | - | - | - | Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports (TEI19_DLPM) | - | - | Docs:=0 | - | |
| 19.20 | - | - | - | Providing per-subscriber VLAN instructions from UDM (TEI19_VLANSUB) | - | - | Docs:=0 | - | |
| 19.21 | - | - | - | Enhancing Parameter Provisioning with static UE IP address and UP security policy (TEI19_IP-SP-EXP) | - | - | Docs:=3 | - | |
| 19.21 | S2-2500395 | CR | Approval | 23.501 CR5939 (Rel-19, 'F'): Clarification on UPSec Policy provisioning | China Telecom, Ericsson | Rel-19 | Approved | Agreed | |
| 19.21 | S2-2500775 | CR | Approval | 23.502 CR5284 (Rel-19, 'F'): Avoding potential Static IP assignment | Samsung | Rel-19 | r04 agreed. Revised in e-mail session to S2-2501311. | Laurent (Nokia): provides r01 Stefan (Ericsson) provides r02 Jicheol (Samsung) provides r03. Laurent (Nokia): Where is 0775r03 ??? I Can't see it Jicheol (Samsung) provides r03 in the correct folder. Please check it again. Sorry for your inconvenience Zhuoyi (China Telecom) asks for clarification. Stefan (Ericsson) replies to Zhuoyi Zhuoyi (China Telecom) provides r04. ==== General Revisions Deadline ==== Jicheol (Samsung) is fine with r04. ==== Comments Deadline ==== | Revised |
| 19.21 | S2-2501311 | CR | Approval | 23.502 CR5284R1 (Rel-19, 'F'): Avoding potential Static IP assignment | Samsung | Rel-19 | Revision of S2-2500775r04. Approved | Agreed | |
| 19.22 | - | - | - | Spending Limits for UE Policies in Roaming scenario (TEI19_SLUPiR) | - | - | Docs:=0 | - | |
| 19.23 | - | - | - | Subscription control for reference time distribution in EPS (TEI19_TIME_SUB_EPS) | - | - | Docs:=0 | - | |
| 19.24 | - | - | - | On-demand broadcast of GNSS assistance data (TEI19_OBGAD) | - | - | Docs:=0 | - | |
| 19.25 | - | - | - | QoS monitoring (TEI19_QME) | - | - | Docs:=14 | - | |
| 19.25 | S2-2500995 | LS OUT | Approval | [DRAFT] LS on Clarification of the scope of QME | Nokia | Rel-19 | Response to S2-2500037. Merged into S2-2501312 | Laurent (Nokia): provides r01 and clarifies that this LS out is an answer to 0037 (not to 0036) Mengzhen(China Telecom) objects r01. Haiyang(Huawei) suggests to merge into 0862 ==== General Revisions Deadline ==== Laurent (Nokia): Agrees to merge in 0862 ==== Comments Deadline ==== | Merged |
| 19.25 | S2-2500037 | LS In | Action | LS from CT WG3: LS on Clarification of the scope of QME | CT WG3 (C3-246506) | Rel-19 | Responses drafted in S2-2500265, S2-2500304, S2-2500801, S2-2500862, S2-2500995. FInal response in S2-2501312 | Shabnam (Ericsson)please ignore the last email comment, sent on the wrong document thread. Shabnam (Ericsson) proposes to use this thread to discuss the issue first before any CR or LS response is chosen. | Replied to |
| 19.25 | S2-2500265 | LS OUT | Approval | [DRAFT] LS reply on clarification of the scope of QME | China Telecom Corporation Ltd. | Rel-19 | Response to S2-2500037. Merged into S2-2501312 | Mengzhen (China Telecom) provides S2-2400265r01. Shabnam (Ericsson) provides comments that the response is not in line with comments I provided Haiyang(Huawei) suggests to merge into 0862 ==== General Revisions Deadline ==== Mengzhen(China Telecom) confirms merging of 0265 into 0862. ==== Comments Deadline ==== | Merged |
| 19.25 | S2-2500304 | LS OUT | Approval | [DRAFT] Reply LS on CT WG3 LS to SA WG2 on QME | China Mobile Com. Corporation | Response to S2-2500037. Merged into S2-2501312 | Haiyang(Huawei) suggests to merge into 0862 ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version for the sake of merging Aihua(CMCC) is fine to merge into 0862 ==== Comments Deadline ==== | Merged | |
| 19.25 | S2-2500801 | LS OUT | Approval | [DRAFT] Reply LS on Clarification of the scope of QME | ZTE | Rel-19 | Response to S2-2500037. Merged into S2-2501312 | Laurent (Nokia): objects to any version for the sake of merging ==== Comments Deadline ==== | Merged |
| 19.25 | S2-2500862 | LS OUT | Approval | [DRAFT] LS Reply to C3-246506 on clarification of the scope of QME | Huawei, HiSilicon | Rel-19 | Response to S2-2500037. CC#4: r04 agreed. Revised in CC#4 to S2-2501312, merging S2-2500265, S2-2500304, S2-2500801 and S2-2500995 | Haiyang (Huawei) provides r01 Zhendong (ZTE) provides r02. ==== General Revisions Deadline ==== Shabnam (Ericsson) provides comments that r02 does not capture the discussion on 0040 thread. It has been messy and confusing due to wrong tdoc thread. Zhendong (ZTE) provides resposne to Ericsson. Zhendong (ZTE) we can discuss in this thread. Laurent (Nokia): provides r03 Zhendong (ZTE) is fine with r03. Haiyang (Huawei) is OK with r03 ==== Comments Deadline ==== Haiyang (Huawei) UPLOAD r04 in CC4 folder, which is r03+ and each can be active or not active independently. Shabnam (Ericsson) provides comments that the LS reply need to be open in CC#4 to add that each monitoring need to be independently controlled, I have provided this comment many times now on many thread, object to all revisions and original proposed addition: 'QME scope is limited to QoS monitoring. Currently RAN QoS monitoring capability report should consider only Packet delay and congestion and each can be active or not active independently.' | Revised |
| 19.25 | S2-2501312 | LS OUT | Approval | LS Reply on Clarification of the scope of QME | SA WG2 | Rel-19 | Revision of S2-2500862r04, merging S2-2500265, S2-2500304, S2-2500801 and S2-2500995. This LS OUT was approved | Approved | |
| 19.25 | S2-2500040 | LS In | Action | LS from CT WG4: Reply LS on RAN support of QoS monitoring capability | CT WG4 (C4-245437) | Rel-19 | CC#4: Postponed | Mengzhen (China Telecom) comments and proposes to choose S2-2400264 as the baseline CR. Haiyang (Huawei) proposes to use this thread to discuss the LS OUT and related CR. Zhendong (ZTE) provides comments. Mengzhen (China Telecom) proposes the way forward and provides S2-2400264r01 and S2-2400265r01 in other threads. Laurent (Nokia): suggests that before discussing about holding the pen for CRs and creating revisions we first agree on the way to go Haiyang (Huawei) drafts the context of the LS OUT based on discussion Mengzhen (China Telecom) replys to Shannam (Ericsson) Zhendong (ZTE) provides response to Ericsson. Shabnam (Ericsson) indicates that it seems wrong LS in used for the discussion? Seems the discussion content original email used 0037 but the title for 0040? Shabnam (Ericsson) proposes to use this thread to discuss the issue first before any CR or LS response is chosen. Aihua(CMCC) comments. Laurent (Nokia): I am lost wrt which thread to use (0037 would have been the correct thread but OK to use 0040) + technical Comments Zhendong (ZTE) provides comments to Nokia. Mengzhen(China Telecom) comments. Haiyang (Huawei) shares view from Zhendong Zhendong (ZTE) provides response to Laurent. Laurent (Nokia): answers | Postponed |
| 19.25 | S2-2500264 | CR | Approval | 23.501 CR5911 (Rel-19, 'C'): Clarifications of QoS monitoring capability configuration and transfer within 5GC | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! r01 agreed. | Mengzhen (China Telecom) provides S2-2400264r01. Laurent (Nokia): suggests that before holding the pen for CRs and creating revisions we first agree on the way to go in the thread of 0040as has been proposed Mengzhen (China Telecom) clarifies that 0264r01 is independent on the LS reply to CT3. Mengzhen (China Telecom) clarifies. Shabnam (Ericsson) does not see the need to this CR as it is already addressed, see comments below. ==== General Revisions Deadline ==== Mengzhen (China Telecom) suggests to approve r01. ==== Comments Deadline ==== Laurent (Nokia): objects to any version (resent as sent by mistake to a wrong list BUT on time) Mengzhen (China Telecom) further replies. Mengzhen (China Telecom) can accept 0264r01 be marked as Noted. | Noted |
| 19.25 | S2-2500305 | CR | Approval | 23.501 CR5919 (Rel-19, 'B'): QME clarification on Reply LS on CT WG3 LS to SA WG2 | China Mobile | Rel-19 | WI Code seems to be AIML_CN, not TEI19_QME! Merged into S2-2501337 | Haiyang(Huawei) suggests to merge into 0802 ==== General Revisions Deadline ==== Laurent (Nokia): objects to any version for the sake of merging Aihua(CMCC) is fine to merge into 0802 ==== Comments Deadline ==== | Merged |
| 19.25 | S2-2500800 | DISCUSSION | Discussion | Discussion on the QME capability issue from CT WG3. | ZTE | Rel-19 | Noted in e-mail session | Noted | |
| 19.25 | S2-2500802 | CR | Approval | 23.501 CR6004 (Rel-19, 'F'): Clarification on the Qos monitoring capability | ZTE | Rel-19 | CC#4: r01 + changes agreed. Revised in CC#4 to S2-2501337, merging S2-2500305 and S2-2500863 | Shabnam (Ericsson) this CR cannot be approved until we resolve the LS out and also the NOTE contains a 'may' that needs to be fixed. As agreed in CC#1 principle we first resolve the LS then CRs. Laurent (Nokia): objects to r00 Laurent (Nokia): provides r01 ==== Comments Deadline ==== zhendong (ZTE). We have reached consensus. The changes are r00 + 1) change Note 1 to 'The AMF is not meant to create dedicated signalling to warn SMF about a change of support of a QoS monitoring feature (by all NG RAN nodes in an area)'. 2) Change 'AMF knows that' to 'AMF may know whether' 3) Adding 'each of' before 'Packet delay'. Adding 'corresponding' before 'QoS monitoring capability' | Revised |
| 19.25 | S2-2501337 | CR | Approval | 23.501 CR6004R1 (Rel-19, 'F'): Clarification on the Qos monitoring capability | ZTE | Rel-19 | Revision of S2-2500802r01 + changes, merging S2-2500305 and S2-2500863. This CR was agreed | Agreed | |
| 19.25 | S2-2500863 | CR | Approval | 23.501 CR6017 (Rel-19, 'F'): Clarification of the scope of QME | Huawei, HiSilicon | Rel-19 | Merged into S2-2501337 | Haiyang (Huawei) provides r01 Zhendong (ZTE) proposes to use the 0802 as attached CR. Mengzhen (China Telecom) asks questions. Zhendong (ZTE) provides response. Haiyang (Huawei) Ok to merge to 0802 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.26 | - | - | - | NF discovery and selection by target PLMN (TEI19_NFsel_by_tPLMN) | - | - | Docs:=3 | - | |
| 19.26 | S2-2500182 | CR | Approval | 23.502 CR5207 (Rel-19, 'F'): Corrections for SMF selection by target PLMN | Nokia | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501314. | Fenqin (Huawei) ask one question for clarification Thomas(Nokia) replies to Fenqin Fenqin (Huawei) replies to Thomas and provides r01 Thomas(nokia) is fine with r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.26 | S2-2501314 | CR | Approval | 23.502 CR5207R1 (Rel-19, 'F'): Corrections for SMF selection by target PLMN | Nokia | Rel-19 | Revision of S2-2500182r01. Approved | Agreed | |
| 19.26 | S2-2500279 | CR | Approval | 23.502 CR5230 (Rel-19, 'F'): Correction on delegated NF service discovery flow | China Mobile | Rel-19 | WI Code should be TEI19_NFsel_by_tPLMN! Noted in e-mail session | Magnus (Ericsson) provides comments Dan (China Mobile) provides reply Thomas(Nokia) comments Dan(China Mobile) comments Thomas replies to Dan(China Mobile) ==== General Revisions Deadline ==== Dan(China Mobile) Thanks Thomas Magnus (Ericsson) objects to this CR Dan (China Mobile) ask for the reason of objection ==== Comments Deadline ==== | Noted |
| 19.27 | - | - | - | Roaming traffic offloading via session breakout in HPLMN (TEI19_HSBO) | - | - | Docs:=3 | - | |
| 19.27 | S2-2500341 | CR | Approval | 23.501 CR5924 (Rel-19, 'F'): Clarification on DNS server information provisioning and editorial updates | Samsung | Rel-19 | Merged into S2-2501315 | Laurent (Nokia): Comments and suggests to merge 0341 in 0990 Hyesung (Samsung) is fine with the merge and replies to the comments. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.27 | S2-2500990 | CR | Approval | 23.501 CR6043 (Rel-19, 'F'): Correction to when and how the UPF can provide the SMF with DNS server information | Nokia | Rel-19 | r04 agreed. Revised in e-mail session to S2-2501315, merging S2-2500341 | Laurent (Nokia): provides r01 Hyesung (Samsung) provides r02 Laurent (Nokia): provides r01 -resending with correct mail title (including Tdoc name) Laurent (Nokia): provides r03 Hyesung (Samsung) is fine with r03. Stefan (Ericsson) provides r04 ==== General Revisions Deadline ==== Hyesung (Samsung) suggests to go with r04 or r03. Not fine with r00 and r01. Fenqin (Huawei) we are ok with r04. ==== Comments Deadline ==== | Revised |
| 19.27 | S2-2501315 | CR | Approval | 23.501 CR6043R1 (Rel-19, 'F'): Correction to when and how the UPF can provide the SMF with DNS server information | Nokia, Samsung | Rel-19 | Revision of S2-2500990r04, merging S2-2500341. Approved | Agreed | |
| 19.28 | - | - | - | Multiple Location Procedure for Emergency LCS Routing (TEI19_MLR4RTR) | - | - | Docs:=2 | - | |
| 19.28 | S2-2500976 | CR | Approval | 23.273 CR0665 (Rel-19, 'F'): LCS Client alignment to Routing Entities using HELD in Emergency LCS | Nokia, Nokia Shanghai Bell | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501316. | Richard (Ericsson) provides comments Richard (Ericsson) provides r01 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.28 | S2-2501316 | CR | Approval | 23.273 CR0665R1 (Rel-19, 'F'): LCS Client alignment to Routing Entities using HELD in Emergency LCS | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2500976r01. Approved | Agreed | |
| 19.29 | - | - | - | Support for ProSe services in NPNs (TEI19_ProSe_NPN) | - | - | Docs:=0 | - | |
| 19.30 | - | - | - | MSISDN verification operation support to Nnef_UEId Service (TEI19_MVOSNS) | - | - | Docs:=1 | - | |
| 19.30 | S2-2500865 | CR | Approval | 23.502 CR5294 (Rel-19, 'D'): Editorial correction | AT&T | Rel-19 | Approved | Agreed | |
| 19.31 | - | - | - | ATSSS Rule Provisioning via 3GPP access connected to EPC (TEI19_ARP3E) | - | - | Docs:=0 | - | |
| 19.32 | - | - | - | Network Controlled Network Slice Selection (TEI19_ SliceSel) | - | - | Docs:=14 | - | |
| 19.32 | S2-2500211 | CR | Approval | 23.501 CR5901 (Rel-19, 'F'): Update to Support of Slice change based on AF request | Ericsson | Rel-19 | Noted in e-mail session | Ashok (Samsung) does not agree with the CR and requests for clarification Jinguo(ZTE) suggests to use 870 as basis and merge this CR into 870 Alessio (nokia) agrees we should not remove the replaced NSSAI from configured NSSAI and proposes to use the rejected S-NSSAI approach which is more friendly to the system. Proposes to proceed based on the CR in S2-2500870 or merge these two CRs into one of the CRs as they seem rather aligned. I would propose merging this in S2-2500870. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR. ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500212 | CR | Approval | 23.502 CR5210 (Rel-19, 'F'): Update to 23.502 AF requested network slicing replacement | Ericsson | Rel-19 | Merged into S2-2501318 | Ashok (Samsung) requests for clarification Jinguo(ZTE) suggests to use 953 as basis and merge this CR into 953 Iskren (NEC) also suggest to use as baseline the CR in S2-2500953 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.32 | S2-2500213 | CR | Approval | 23.503 CR1459 (Rel-19, 'F'): Update to 23.503 Support of network slice replacement based on AF request | Ericsson | Rel-19 | Postponed in e-mail session | Jinguo(ZTE) provides r01, editorial changes Alessio(Nokia) ok with r01 George (Ericsson) asks a question George (Ericsson) provides r02. Just restored the original wording for the trigger to make it generic for all types ==== General Revisions Deadline ==== Jinguo(ZTE) comments on r02, can't agree r02 and prefer r01+further revision Myungjune (LGE) comments that new PCRT should be moved to other table. George (Ericsson) ) proposes to accept r02. George (Ericsson) provides comments Jinguo(ZTE) propose to approve r02 with the following update 1) change the 'S-NSSAI Replacement' to 'network slice replacement' 2) move the PCRT from Table 6.1.2.5-1 to Table 6.1.2.5-1a George (Ericsson) is OK with this proposal Myungjune (LGE) support Jinguo (ZTE)'s proposal. Alessio can accept r02 with the wording change as in body of my message but not move 2) move the PCRT from Table 6.1.2.5-1 to Table 6.1.2.5-1a as not even the change of allowed NSSAI is in that table. Myungjune (LGE) responses to Alessio (Nokia) Alessio(Nokia) is not sure the upgrade will apply equally to 3GPP and non 3GPP access as the slice upgrade may use NG-RAN feature. So for now we assume it is a 3GPP access only feature unless we find stage one to do otherwise. Myungjune (LGE) cannot accept any revision including original version and proposes to postpone this. ==== Comments Deadline ==== | Postponed |
| 19.32 | S2-2500457 | CR | Approval | 23.501 CR5957 (Rel-19, 'F'): Network controlled slice replacement cleanup | NEC | Rel-19 | Noted in e-mail session | George (Ericsson) provides comments Jinguo(ZTE) supports Ericsson and propose to note this CR. Alessio(Nokia) agrees with George (ericsson) and would suggest the approach proposed here is not to be pursued. In particular the Cr proposes a PCRT that is activated during the notification of slice replacement, we should not do this, as PCRTs should be activated during AM policy association. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500535 | CR | Approval | 23.501 CR5972 (Rel-19, 'F'): Resolving remaining editor's notes | LG Electronics | Rel-19 | Noted in e-mail session | George (Ericsson) provides comments Jinguo(ZTE) suggests to use 870 as basis and merge this CR into 870 Ashok (Samsung) supports this CR Ashok (Samsung) provides comments Alessio(Nokia) agrees with Ashok. The CR should be rather noted and 870 used as abasis of progress. Ashok (Samsung) comments Fenqin(Huawei) provides comments Jinguo(ZTE) provides comments Myungjune (LGE) disagree to merge into 870. Myungjune (LGE) responses to JInguo (ZTE) and Fenqin (Huawei). Jinguo(ZTE) response Alessio(Nokia) states that if Myungjune (LGE) disagree to merge into 870 it then can be noted. Jinguo(ZTE) provides answer to Myungjune(LGE) Myungjune (LGE) answers to Jniguo (ZTE) Jinguo(ZTE) asks question to Myungjune(LGE) George (Ericsson) provides response Myungjune (LGE) provides further response to George (Ericsson). George (Ericsson) provides answers in line and more question as well in line. In general please details the complete sequence of events so the point is clear. Myungjune (LGE) responses to George (Ericsson). Myungjune(LGE) responses to Jinguo (ZTE) and asks question. Alessio(Nokia) If an operator uses this feature it is likely they will upgrade their network to make it work wherever they want it to work. So indeed general support is expected where the feature is supposed to work. Alessio(Nokia) proposes to resolve the issue of non-uniform support with a note assuming the support is there where the feature needs to operate. We should not work in standards to support scenarios that are not really in scope of a sound deployment. Jinguo(ZTE) response to Myungjune(LGE) Alessio(Nokia) assumes this is now merged in 870, can this be confirmed? Myungjune (LGE) answers to Jinguo(ZTE) Myungjune (LGE) is ok to merge into S2-2500870 and S2-2500952. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500536 | CR | Approval | 23.503 CR1479 (Rel-19, 'F'): Clarification on event notification on outcome of AF requested Network Slice Replacement | LG Electronics | Rel-19 | Noted in e-mail session | Jinguo(ZTE) suggests to use 213 as basis and merge this CR into 213 Ashok (Samsung) requests for clarification Alessio(Nokia) agrees that reusing change of allowed NSSAI PCRT is not ok ==== General Revisions Deadline ==== Myungjune (LGE) is ok to NOTE CR. George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500870 | CR | Approval | 23.501 CR6020 (Rel-19, 'F'): Resolvement of EN in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE, Nokia | Rel-19 | r11 agreed. Revised in e-mail session to S2-2501317. | George (Ericsson) provides comments Alessio(Nokia) replies to George (Ericsson) on the aspect of partially allowed S-NSSAI. Jinguo(ZTE) provides response to Geroge, and Myunjune, and provide r01 George (Ericsson) provides response to Alessio Myungjune (LGE) provides comments. Myungjune (LGE) responses to Jinguo (ZTE). Jinguo(ZTE) response Myungjune (LGE) replies to Jinguo (ZTE). Jinguo(ZTE) ask whether it is acceptable to notify the outcome when the PDU session to alternative S-NSSAI is successfully established Alessio(Nokia) comments that the slice replacement is a RM event so it cannot be confirmed by a SM event taking place at a future unknown time. The AMF shall execute the removal of the replaced s-NSSAI from allowed/partially allowed and replacement with the alternative S-NSSAI and if that cannot take place it indicates why it could not take place (e.g. UE unreachable?), and if successful indication is provided. Ashok (Samsung) comments to discuss the removal of replaced S-NSSAI from Configured NSSAI on 952 as suggested by Jinguo. Alessio(nokia) comments the removal of replaced S-NSSAI from Configured NSSAI is to be resolved based on 870 as it has no UDM impact so no point to discuss it in 952 which we have requested to note. Myungjune (LGE) is OK with NOTE 2 but still need to discuss Rejected/Configured NSSAI aspect. Ashok (Samsung) comments on r02 Jinguo(ZTE) provides r02 Myungjune (LGE) comments that partially allowed should be removed. Jinguo(ZTE) provides r03 Myungjune (LGE) provides r04. Alessio(nokia) replies to Myungjune (LGE) comments Alessio replies to Ashok (Samsung) comments on r02 Alessio(Nokia) believes that r02 is not preferable, the original version is still the best. Alessio(Nokia) provides r05 which improves editorially r04. Alessio(Nokia) provides r06 which removes the added text by LG in some other versions I did not catch the UE releases locally the PDU session (the aMF has to anyhow trigger that by PDU session status in a reg accept or an explicit release if done via UCU). Not sure why the text was added on UE locally releasing the session. alessio(Nokia) assumes now the partial slice support issue is for a future meeting Ashok (Samsung) provides r08 on top of r06. Ashok (Samsung) provides r08 on top of r06 along with the link Alessio(Nokia) disagrees technically with r08 and can live with the proposed r06 as compromise at this meeting Ashok (Samsung) responds to George (Ericsson) Ashok (Samsung) objects to all the revision and accept only r08 George (Ericsson) provides response to Ashok George (Ericsson) asks a question. Jinguo(ZTE) provides r09 Ashok (Samsung) replies to George (Ericsson) Ashok (Samsung) provides r10 Jinguo(ZTE) response to Ashok(Samsung) George (Ericsson) provides r11. Added Ericsson as co-signer ==== General Revisions Deadline ==== Myungjune (LGE) is ok with r08, r09, r10, r11. George (Ericsson) Accepts R11 ONLY Alessio(Nokia) can live with r11 but I assume this will be revised at next meeting as we still have one outstanding eN Fenqin (Huawei) we are ok with r11. Ashok (Samsung) is OK with r11. ==== Comments Deadline ==== | Revised |
| 19.32 | S2-2501317 | CR | Approval | 23.501 CR6020R1 (Rel-19, 'F'): Resolvement of EN in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE, Nokia, Ericsson | Rel-19 | Revision of S2-2500870r11. Approved | Agreed | |
| 19.32 | S2-2500871 | CR | Approval | 23.502 CR5295 (Rel-19, 'F'): Clarification on the AF requested network slice replacement | ZTE | Rel-19 | Merged into S2-2501318 | Jinguo(ZTE) suggests to use 953 as basis and merge this CR into 953 ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Merged |
| 19.32 | S2-2500872 | CR | Approval | 23.503 CR1494 (Rel-19, 'F'): PCRT for outcome of network slice replacement triggered by AF | ZTE | Rel-19 | Noted in e-mail session | George (Ericsson) provides comments Jinguo(ZTE) suggests to use 213 as basis and merge this CR into 213 Myungjune (LGE) provides comments. ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500952 | CR | Approval | 23.501 CR6041 (Rel-19, 'F'): Addressing EN for AF requested slice selection | Samsung | Rel-19 | WI Code should be TEI19_SliceSel! Noted in e-mail session | George (Ericsson) provides comments Jinguo(ZTE) agreed with Ericsson, propose to note this CR Alessio(nokia) agrees with Jinguo(ZTE who) agreed with Ericsson and proposed to note this CR Ashok (Samsung) provides response Alessio replies to Ashok (Samsung) indicating that rel-18 features have problems as indicated by our CR aligning the approach to use rejected S-NSSAIs. we do not like the UDM based approach used by Samsung to solve the issue as this also would need to be there for rel-18 features and it is too complex and would require stage three impact in CT specs. Ashok (Samsung) comments Alessio(Nokia) replies to Ashok (Samsung) comments Ashok (Samsung) responds to Alessio(Nokia) Jinguo(ZTE) suggest to use this CR to discuss the Configured NSSAI part Myungjune (LGE) supports this CR and proposes to merge into S2-2500535. Myungjune (LGE) responses to JInguo (ZTE). Ashok (Samsung) responds to JInguo Ashok (Samsung) provides r01 with justification adding in TS coversheet that there is no issue even if UE is deregistered state if existing mechanism of removing replaced S-NSSAI from Configured NSSAI is used Myungjune (LGE) wants to cosign. Alesio(Nokia) disagrees technically with r01 as the scenario is misconstrued and proposes to note it as well as any revisions of this paper. Ashok (Samsung) comments that Alessio agreed after explanation that the steps are technically correct Alessio(Nokia) comments and keeps the already expressed position Jinguo(ZTE) response to Ashok(Samsung) Jinguo(ZTE) provides r02 George (Ericsson) asks a question line Ashok (Samsung) clarifies to Jinguo(ZTE) George (Ericsson) We are using 870 as a base so this one should be merged in there. Jinguo(ZTE) response to George(Ericsson) Ashok (Samsung) provides r03 on top of r01 and added LG Electronics as co-signer George (Ericsson) is that registration by the UE considered as initial registration by the AMF and assuming it has no context ? George (Ericsson) will only support 870 at this meeting. George (Ericsson) provides response Ashok (Samsung) replies to George George (Ericsson) repeat the same question again Ashok (Samsung) provides answer ==== General Revisions Deadline ==== Alessio(Nokia) I think we can now note this paper Myungjune (LGE) supports r03. George (Ericsson) ) proposes to note the CR Alessio (Nokia) supports George (Ericsson) and proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.32 | S2-2500953 | CR | Approval | 23.502 CR5305 (Rel-19, 'F'): Clarification for AF requested slice selection | Samsung | Rel-19 | WI Code should be TEI19_SliceSel! r04 agreed. Revised in e-mail session to S2-2501318, merging S2-2500212 and S2-2500871 | George (Ericsson) provides comments Jinguo(ZTE) suggests to use 953 as basis for 502 CR. Ashok (Samsung) provides response to Jinguo(ZTE) Iskren (NEC) comments Myungjune (LGE) provides comments. Jinguo(ZTE) suggests to remove the UDR part since it doesn't work Ashok (Samsung) provides r01 George (Ericsson) asks a question Ashok (Samsung) provides r01 and hope it works Alessio comments r01 does not work as the issue is the with UE configured NSSAI and since the AP slice replacement can happen also using clause 4.15.6.9.2 this is not resolved by keeping policies in UDR as indicated in the text in r01 as in this case UDR is not impacted. We strongly recommend using the approach in 870 Jinguo(ZTE) comments and provide r02 Alessio(Nokia) would not agree to mandate AF to use only 4.15.6.9.3 since the existing usage of rejected S-NSSAI in the existing text is compatible with4.15.6.9.2 Ashok (Samsung) explains to Alessio that r01 works as we will mandate AF to use only 4.15.6.9.3 procedure for AF slice replacement termination. Though both 4.15.6.9.2 and 4.15.6.9.3 procedure we have agreed but ideally 4.15.6.9.2 procedure will not work for AF slice replacement feature because AF will not be knowing whether UE is registered or not, if not registered, there won't be any PCF to handle the AF request. Hence only 4.15.6.9.3 procedure will be used Fenqin (Huawei) provides comments Ashok (Samsung) responds to Fenqin (Huawei) Fenqin (Huawei) provides feedback to Ashok(Samsung) Alessio(Nokia) can live with r02 Iskren (NEC) agrees with r02 and would like to co-sign. George (Ericsson) provides r03 Ashok (Samsung) provides r04, only change is NEC as co-signer ==== General Revisions Deadline ==== Jinguo(ZTE) is ok with r04, and point that impact clause needs to be updated, also the split tag between changes need to be added. Myungjune (LGE) is ok with r04. George (Ericsson) OK with R04 Iskren (NEC) is ok with r04. Alessio(Nokia) is ok with r04, and requests to add in meeting notes that clause affected needs to include 4.15.6.9.2 and also the between changed clauses separators are needed. Fenqin (Huawei) we are ok with r04. ==== Comments Deadline ==== | Revised |
| 19.32 | S2-2501318 | CR | Approval | 23.502 CR5305R1 (Rel-19, 'F'): Clarification for AF requested slice selection | Samsung | Rel-19 | Revision of S2-2500953r04, merging S2-2500212 and S2-2500871. Approved | Agreed | |
| 19.32 | S2-2500983 | CR | Approval | 23.503 CR1501 (Rel-19, 'F'): Network controlled slice replacement cleanup | NEC | Rel-19 | Noted in e-mail session | George (Ericsson) provides comments Jinguo(ZTE) agreed with Ericsson and propose to NOTE this CR Alessio(Nokia) agrees with Jinguo(ZTE) who agreed with Ericsson and propose to NOTE this CR ==== General Revisions Deadline ==== George (Ericsson) ) proposes to note the CR ==== Comments Deadline ==== | Noted |
| 19.33 | - | - | - | PRU Usage Extension supported by Core Network (TEI19_PRUE) | - | - | Docs:=0 | - | |
| 19.49 | - | - | - | Generic Rel-19 LSs | - | - | Docs:=39 | - | |
| 19.49 | - | - | - | VMR_Ph2 related - MWAB mobility | - | - | Docs:=15 | - | |
| 19.49 | S2-2500053 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | RAN WG3 (R3-247910) | Rel-19 | Responses drafted in S2-2500221, S2-2500366, S2-2500514, S2-2500580. Final response in S2-2501336 | Hong (Qualcomm) suggests discussing the response in thread for S2-2500221. Yunjing (CATT) proposes to postpone the LS. | Replied to |
| 19.49 | S2-2500222 | DISCUSSION | Discussion | Discussion on Incoming LS S2-2500053/R3-247910 on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility). | Nokia | Rel-19 | Noted in e-mail session | Noted | |
| 19.49 | S2-2500367 | DISCUSSION | Agreement | MWAB mobility analysis . | Ericsson | Rel-19 | Noted in e-mail session | Noted | |
| 19.49 | S2-2500579 | DISCUSSION | Discussion | Discussion on AMF re-allocation with a single logical WAB-gNB | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 19.49 | S2-2500220 | CR | Approval | 23.501 CR5902 (Rel-19, 'F'): On MWAB mobility | Nokia | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501319, merging S2-2500515 | Alessio(Nokia) provides r01 to remove CM- replaced to RRC- Qian (Ericsson) provides r02 LiMeng (Huawei) provides r03. Alessio(nokia) ok with r03. Qian (Ericsson) is ok with r03. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501319 | CR | Approval | 23.501 CR5902R1 (Rel-19, 'F'): On MWAB mobility | Nokia | Rel-19 | Revision of S2-2500220r03, merging S2-2500515. Approved | Agreed | |
| 19.49 | S2-2500368 | CR | Approval | 23.501 CR5934 (Rel-19, 'F'): MWAB Mobility handling clarification | Ericsson | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501320. | Alessio(Nokia) provides r01 focusing on the clarification of new AMF/old AMF configuration Qian (Ericsson) provides r02 LiMeng (Huawei) provides r03 Alessio(Nokia)can live with r03 but prefers still r01 Qian (Ericsson) is ok with r03 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501320 | CR | Approval | 23.501 CR5934R1 (Rel-19, 'F'): MWAB Mobility handling clarification | Ericsson | Rel-19 | Revision of S2-2500368r03. Approved | Agreed | |
| 19.49 | S2-2500515 | CR | Approval | 23.501 CR5967 (Rel-19, 'F'): Sove the editor s note related to mobility support | CATT | Rel-19 | Merged into S2-2501319 | Alessio(Nokia) prefers to use 220r01 just removing the EN, suggest to merge this paper into 22r01 or note it. ==== General Revisions Deadline ==== Yunjing (CATT) is fine to merge this paper into S2-2500220. ==== Comments Deadline ==== | Merged |
| 19.49 | S2-2500516 | CR | Approval | 23.502 CR5250 (Rel-19, 'F'): Add use case related to MWAB for intra-NG-RAN handover to be performed by the Inter NG-RAN node N2 based handover procedure | CATT | Rel-19 | Noted in e-mail session | Alessio(Nokia) prefers to note this paper ==== General Revisions Deadline ==== Yunjing(CATT) is fine to note this paper ==== Comments Deadline ==== | Noted |
| 19.49 | S2-2500221 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | Nokia | Rel-19 | Response to S2-2500053. CC#4: r05 agreed. Revised in CC#4 to S2-2501336. | Hong (Qualcomm) suggests using this document as the basis for discussing the response to S2-2500053. Yunjing (CATT) provides r01. LaeYoung (LGE) provides comment that the two logical gNBs option is sufficient. Zhendong (ZTE) provides comments on the single gNB option.. Hong (Qualcomm) comments. Alessio(Nokia) comments that we prefer the original version as r01 sort of does not warn of potential issues. Also seems like they are fine with two gNB option and the one gNB option seems more a deployment /configuration choice than a standard impacting one. And actually Qian seems to outline the issue that normally no gNB is deployed over two AMF regions LiMeng (Huawei) can accept to have two logic gNB solution. R02 and 03 are OK. LaeYoung (LGE) provides r03. Qian (Ericsson) provides r02. Yunjing (CATT) provides r04. LiMeng (Huawei) comments on r04 and prefer to have two logic gNBs as the information provided to RAN3. Zhendong (ZTE) agree with Limeng that r02 or r03 is preferred Alessio (Nokia) suggests to proceed with r03 Yunjing(CATT) prefers r04. Qian (Ericsson) supports to go with r03. ==== General Revisions Deadline ==== LaeYoung (LGE) also supports to go with r03 (Of course ??). Zhendong (ZTE) supports r03. Hong (Qualcomm) prefers r03 as well. Yunjing(CATT) provides r05 Qian (Ericsson) responds. Yunjing (CATT) replies to Qian (Ericsson). Qian (Ericsson) provides further comments. Qian (Ericsson) cannot accept r05, still prefer r03. But can comprise to add a sentence in the end of the answer for sol#2, on top of r03: 'It's up to RAN3 to discuss if there is any other benefit of one logic gNB solution.' Qian (Ericsson) can only accept r02/r03, prefer r03. But can comprise to add a sentence in the end of the answer for sol#2, on top of r03: 'It's up to RAN3 to discuss if there is any other benefit of one logic gNB solution.' Alessio(Nokia) can live with 'It's up to RAN3 to discuss if there is any benefit of one logic gNB solution as long as it has no CN impacts.' Qian (Ericsson) supports the addition proposal from Alessio (Nokia) Yunjing (CATT) proposes to postpone the draft LS reply. LiMeng (Huawei) can live with the wording proposed by Alessio, or r02/03, object to other versions. Zhendong (ZTE) supports the proposal by Alessio (Nokia). LaeYoung (LGE) cannot accept 'r03 + the text suggested by Alessio' and prefer to go with r03. ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501336 | LS OUT | Approval | Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | SA WG2 | Rel-19 | Revision of S2-2500221r05. This LS OUT was approved | Approved | |
| 19.49 | S2-2500366 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 Solution impacts on RAN (MWAB mobility) | Ericsson | Rel-19 | Response to S2-2500053. Noted in e-mail session | Alessio (Nokia) suggests to proceed with 221 and note this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.49 | S2-2500514 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | CATT | Rel-19 | Response to S2-2500053. Noted in e-mail session | Alessio (Nokia) suggests to proceed with 221 and note this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.49 | S2-2500580 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Mobility) | Huawei, HiSilicon | Rel-19 | Response to S2-2500053. Noted in e-mail session | Alessio (Nokia) suggests to proceed with 221 and note this paper. LiMeng (Huawei) is OK to Note this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.49 | - | - | - | VMR_Ph2 related - Additional ULI & multi-hop prevention | - | - | Docs:=12 | - | |
| 19.49 | S2-2500052 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) | RAN WG3 (R3-247909) | Rel-19 | Responses drafted in S2-2500363, S2-2500582. Final response in S2-2501324 | Hong (Qualcomm) suggests discussing the response in thread for S2-2500363. | Replied to |
| 19.49 | S2-2500364 | DISCUSSION | Agreement | Analysis on MWAB Access control and Additional ULI. | Ericsson | Rel-19 | Noted in e-mail session | Alessio(Nokia) asks to note the discussion paper, our comments are provided as part of the discussion of LS reply in 363 and related CRs ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.49 | S2-2500581 | DISCUSSION | Discussion | Discussion on Additional ULI | Huawei, HiSilicon | Rel-19 | Noted in e-mail session | Noted | |
| 19.49 | S2-2500365 | CR | Approval | 23.501 CR5933 (Rel-19, 'F'): MWAB configuration and Additional ULI Clarification | Ericsson | Rel-19 | r05 agreed. Revised in e-mail session to S2-2501321. | Alessio(Nokia) provides r01 focusing on the note editorial aspects, for other clauses we can use S2-2500220 and S2-2500517 as commented in the CR changes. LiMeng (Huawei) agrees with LaeYoung (LGE). LaeYoung (LGE) asks a Q. Sang-Jun (Samsung) provides r03 Qian (Ericsson) provides r02. LaeYoung (LGE) provides r04 and thanks to LiMeng (Huawei) for explanation and view. Alessio(Nokia) provides r05 removing ambiguous text from r04/3 etc on the MWAB-gNB support of the slices for mwab operation Qian (Ericsson) provides r06. Alessio Nokia) asks question Qian (Ericsson) responds Alessio(Nokia) based on replies from Qian (Ericsson) cannot agree with r06 as it it's the target gNB (in this case MWAB) that fails the HO.we should proceed with r05. Qian (Ericsson) asks questions. Qian (Ericsson) provides comments and consider r06 is correct one. ==== General Revisions Deadline ==== LiMeng (Huawei) comments Qian (Ericsson) responds and propose to go with r06 LiMeng (Huawei) asks further questions. Qian (Ericsson) responds. Sang-Jun (Samsung) is fine with r06 LiMeng (Huawei) is fine with r06. Alessio(Nokia) cannot agree to r06 and would like to proceed based on r05 Alessio(Nokia) provides further comments to Qian Qian (Ericsson) indicates that r06 is preferred, but ok with r05 as comprise. Hong (Qualcomm) can only accept r02/r03; or a later revision with the second part of the NOTE 2 added back. Qian (Ericsson) comments. Alessio(Nokia) is ok to go r05 with 'The support at a MWAB-gNB of S-NSSAIs dedicated to MWAB UE BH PDU sessions in the MWAB Broadcasted PLMN/SNPN would mean that the MWAB-gNB could support serving the MWAB UEs' BH-PDU Session(s) in the broadcasted PLMN/SNPN' added back to NOTE2 Hong (Qualcomm) replies to Qian and confirms the understanding regarding r05 + 2nd part of NOTE 2. Qian (Ericsson) is ok to go with the proposal from Alessio (Nokia). LaeYoung (LGE) is also fine to go r05 with 'The support at a MWAB-gNB of S-NSSAIs dedicated to MWAB UE BH PDU sessions in the MWAB Broadcasted PLMN/SNPN would mean that the MWAB-gNB could support serving the MWAB UEs' BH-PDU Session(s) in the broadcasted PLMN/SNPN' added back to NOTE2. ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501321 | CR | Approval | 23.501 CR5933R1 (Rel-19, 'F'): MWAB configuration and Additional ULI Clarification | Ericsson, Samsung | Rel-19 | Revision of S2-2500365r05. Approved | Agreed | |
| 19.49 | S2-2500517 | CR | Approval | 23.501 CR5968 (Rel-19, 'F'): Solve the Editor s Note related to the Additional ULI | CATT | Rel-19 | r07 agreed. Revised in e-mail session to S2-2501322. | Alessio(Nokia) provides r01 LiMeng (Huawei) provides r04 Hong (Qualcomm) provides r03 Sang-Jun (Samsung) provides corret link for r02. Alessio(Nokia) provides r02 Alessio(Nokia) provides r05, would still prefer r01 Qian (Ericsson) comments and provides r06 Yunjing (CATT) provides r06. Yunjing (CATT) revokes her previous comment. Alessio(Nokia) can only accept r05 as it is fully clear and not incorrect. R06 seems engineered to not let people understand option 3 is valid. Yunjing (CATT) suggests a wayforward. Alessio(Nokia) provides r07 ==== General Revisions Deadline ==== Yunjing (CATT) is fine with r07. Hong (Qualcomm) prefers r07, as it corrected the typo in r05. Qian (Ericsson) prefers r06, but can live with r05 Nokia(Alessio) We also prefer r07 to r05 as r05 has a typo while conceptually the same. I think no one had problems with the Che CR with typo so we should approve the one without the typo Qian (Ericsson) is ok with 07 ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501322 | CR | Approval | 23.501 CR5968R1 (Rel-19, 'F'): Solve the Editor s Note related to the Additional ULI | CATT, Ericsson | Rel-19 | Revision of S2-2500517r07. Approved | Agreed | |
| 19.49 | S2-2500755 | CR | Approval | 23.501 CR5998 (Rel-19, 'B'): MWAB-UE Mobility Restriction | Samsung | Rel-19 | r01 agreed. Revised in e-mail session to S2-2501323. | Alessio(Nokia) prefers to note this paper or simplify it as in r01 which we provide . Sang-Jun (Samsung) accepts r01 provided by Alessio(Nokia), and cosign 0365 as Qian (Ericsson) pointed out Qian (Ericsson) prefers to note this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501323 | CR | Approval | 23.501 CR5998R1 (Rel-19, 'B'): MWAB-UE Mobility Restriction | Samsung | Rel-19 | Revision of S2-2500755r01. Approved | Agreed | |
| 19.49 | S2-2500363 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 Solution impacts on RAN (Access Control and Additional ULI) | Ericsson | Rel-19 | Response to S2-2500052. r05 agreed. Revised in e-mail session to S2-2501324. | Hong (Qualcomm) suggests using this document as the basis for discussing the response to S2-2500052. Alessio(Nokia) provides r01. Qian (Ericsson) provides comments. Alessio(Nokia) replies that we should use the approaches in S2-2500220r01 and S2-2500517r01 . the benefit of referring to rAN specs is it does not create the need to also agree other CRs like Samsungs on IAB and MBSR multihop considerations. Let RAN handle that. LiMeng (Huawei) prefers to keep the description on option3. Qian (Ericsson) provides r02. Alessio(Nokia) provides text we can live with in r03 Qian (Ericsson) comments and provides r04 Yunjing (CATT) suggests a wayforward. Alessio(Nokia) provides r05 Chris (Vodafone) prefers a simple solution that uses the PLMN ID, TAC and Cell ID that are broadcast by the cell serving the MWAB UE (I think that is option 3) ==== General Revisions Deadline ==== Qian (Ericsson) is ok with r05 ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501324 | LS OUT | Approval | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) | SA WG2 | Rel-19 | Revision of S2-2500363r05. Approved | Approved | |
| 19.49 | S2-2500582 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | Huawei, HiSilicon | Rel-19 | Response to S2-2500052. Noted in e-mail session | Alessio (Nokia) suggests to proceed with 363 and note this paper. LiMeng (Huawei) is OK to note this paper. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.49 | - | - | - | Other topics | - | - | Docs:=5 | - | |
| 19.49 | S2-2500032 | LS In | Action | LS from CT WG1: LS on priority IMS registration | CT WG1 (C1-246939) | Rel-19 | Response drafted in S2-2500186. FInal response in S2-2501325 | Replied to | |
| 19.49 | S2-2500186 | LS OUT | Approval | [DRAFT] LS Reply on priority IMS registration | Peraton Labs | Rel-19 | Response to S2-2500032. r01 agreed. Revised in e-mail session to S2-2501325. | Revised | |
| 19.49 | S2-2501325 | LS OUT | Approval | Reply LS on priority IMS registration | SA WG2 | Rel-19 | Revision of S2-2500186r01. Approved | Approved | |
| 19.49 | S2-2500185 | CR | Approval | 23.228 CR1535 (Rel-19, 'F'): Priority IMS Registration | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon | Rel-19 | r03 agreed. Revised in e-mail session to S2-2501326. | Rainer (Nokia) provides r01. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501326 | CR | Approval | 23.228 CR1535R1 (Rel-19, 'F'): Priority IMS Registration | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon, Nokia, Ericsson | Rel-19 | Revision of S2-2500185r03. Approved | Agreed | |
| 19.49 | - | - | - | LS on Time Synchronization for MBS | - | - | Docs:=6 | - | |
| 19.49 | S2-2500066 | LS In | Action | LS from SA WG4: LS on Time Synchronization for MBS | SA WG4 (S4-242169) | Rel-19 | Responses drafted in S2-2500135, S2-2500252, S2-2500576, S2-2500799. FInal response in S2-2501327 | Robbie (Ericsson) is replies to Zhendong (ZTE) Zhendong (ZTE) provides comments. LiMeng (Huawei) is fine to discuss here and use S2-2500252 as the selected LS reply. Robbie (Ericsson) suggests discussing in this email thread. Zhendong (ZTE) provides response to Robbie. Robbie (Ericsson) replies to Zhendong (ZTE) LiMeng (Huawei) considers this will not affect the answer. Robbie (Ericsson) agrees with LiMeng (Huawei) Haris(Qualcomm) responds and indicates that information about SIB9/SIB16 is irrelevant since access to the clock that is used for SIB9/SIB16 configuration in RAN is not guaranteed by the 5GC NF that sends the service description Robbie (Ericsson) asks Haris(Qualcomm) Thomas(Nokia) responds Robbie (Ericsson) replies to Thomas(Nokia) and Harris (Qualcomm) Zhendong (ZTE) provides the response. Robbie (Ericsson) provides r01 in S2-2500252 and suggests discussing there. Thomas(Nokia) comments. | Replied to |
| 19.49 | S2-2500135 | LS OUT | Approval | [DRAFT] Reply LS on Time Synchronization for MBS | Qualcomm | Rel-19 | Response to S2-2500066. Merged into S2-2501327 | Merged | |
| 19.49 | S2-2500252 | LS OUT | Approval | [DRAFT] Reply LS on Time Synchronization for MBS | Ericsson | Rel-19 | Response to S2-2500066. r03 agreed. Revised in e-mail session to S2-2501327, merging S2-2500135, S2-2500576 and S2-2500799 | Robbie (Ericsson) provides r01. Haris(Qualcomm) provides r02 Robbie (Ericsson) is fine with r02 Robbie (Ericsson) is OK with r03 LiMeng (Huawei) is fine with r03 Thomas(Nokia) provides r03 Haris(Qualcomm) is ok with r03 Zhendong (ZTE) is fine with r03. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 19.49 | S2-2501327 | LS OUT | Approval | Reply LS on Time Synchronization for MBS | SA WG2 | Rel-19 | Revision of S2-2500252r03, merging S2-2500135, S2-2500576 and S2-2500799. Approved | Approved | |
| 19.49 | S2-2500576 | LS OUT | Approval | [DRAFT] Response on Time synchronisation for MBS | Huawei, HiSilicon | Rel-19 | Response to S2-2500066. Merged into S2-2501327 | Merged | |
| 19.49 | S2-2500799 | LS OUT | Approval | [DRAFT] Reply LS from SA WG4: LS on Time Synchronization for MBS | ZTE | Response to S2-2500066. Merged into S2-2501327 | Merged | ||
| 19.49 | - | - | - | LS for information | - | - | Docs:=1 | - | |
| 19.49 | S2-2500031 | LS In | Information | LS from CT WG1: Reply LS on FS_IMS_RES outcome and future work plan | CT WG1 (C1-246921) | Rel-19 | Noted in e-mail session | Noted | |
| 19.50 | - | - | - | Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=25 | - | |
| 19.50 | S2-2500981 | CR | Approval | 23.247 CR0372R4 (Rel-19, 'B'): MBS broadcast support for NTN | Nokia, Qualcomm | Rel-19 | Revision of S2-2500154. Confirm CR Revision - CR states 3! r04 agreed. Revised in e-mail session to S2-2501328, merging S2-2500577 | Thomas (Nokia) provides r01. LiMeng (Huawei) provides r02. Robbie (Ericsson) asks. Yuxin (Xiaomi) provides r03 and asks for clarification LiMeng (Huawei) provides r04 to address the comments. Robbie (Ericsson) is fine with r04 Thomas (Nokia) is fine with r04 and thanks contributing companies ==== General Revisions Deadline ==== Zhendong (ZTE) is finw with r04. ==== Comments Deadline ==== | Revised |
| 19.50 | S2-2501328 | CR | Approval | 23.247 CR0372R5 (Rel-19, 'B'): MBS broadcast support for NTN | Nokia, Qualcomm, Xiaomi, Ericsson, Huawei, HiSilicon | Rel-19 | Revision of S2-2500981r04, merging S2-2500577. Approved | Agreed | |
| 19.50 | - | - | - | LS on supporting MBS broadcast service for NR NTN | - | - | Docs:=2 | - | |
| 19.50 | S2-2500046 | LS In | Action | LS from RAN WG2: Reply LS on supporting MBS broadcast service for NR NTN | RAN WG2 (R2-2411196) | Rel-19 | Response drafted in S2-2500578. FInal response in S2-2501329 | Thomas (Nokia) clarifies that LS can be marked as 'replied to' if revision of S2-2500504 is agreed | Replied to |
| 19.50 | S2-2500578 | LS OUT | Approval | [DRAFT] Reply on LS on Supporting MBS broadcast service for NR NTN | Huawei, HiSilicon | Rel-19 | Response to S2-2500046. Merged into S2-2501329 | Zhendong (ZTE) is fine with single LS response. LiMeng (Huawei) is fine to merge this document into S2-2500504. LiMeng (Huawei) is fine to merge this LS to the other LSs for responding RAN3 (155 or 504). Robbie (Ericsson) provides comments ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.50 | - | - | - | LS on emergency services and eDRX | - | - | Docs:=6 | - | |
| 19.50 | S2-2500044 | LS In | Action | LS from RAN WG2: LS on emergency services and eDRX | RAN WG2 (R2-2411041) | Rel-17 | Responses drafted in S2-2500362, S2-2500698, S2-2501001. Postponed in e-mail session | Postponed | |
| 19.50 | S2-2500362 | LS OUT | Approval | [DRAFT] Reply LS on emergency services and eDRX | Ericsson | Rel-17 | Response to S2-2500044. Postponed in e-mail session | Haris(Qualcomm) objects to any LS response from this meeting and until the conditions for MT signalling within the emergency PDU session are clarified by CT1 Haris(Qualcomm) objects to any LS response from this meeting until the conditions of receiving MT signalling/traffic within the emergency PDU session are clarified Haris(Qualcomm) objects to this LS response until the conditions for receiving MT signalling/traffic in emergency PDU session are clarified by CT1 Qian (Ericsson) provides comments related to this emergency service and eDRX topic (multiple LS outs: 0362, 0698, 1001, 0134) Haris(Qualcomm) responds Dongjoo(Nokia) provides comments. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.50 | S2-2500698 | LS OUT | Approval | [DRAFT] LS Reply on emergency services and eDRX | Huawei, HiSilicon | Rel-17 | Response to S2-2500044. Postponed in e-mail session | Haris(Qualcomm) objects to any LS response from this meeting and until the conditions for MT signalling within the emergency PDU session are clarified by CT1 Haris(Qualcomm) objects to any LS response from this meeting until the conditions for receiving MT signalling/traffic within the IMS PDU session are clarified and why special conditions are needed re eDRX and other related functionalities Haris(Qualcomm) objects to any LS response from this meeting until the conditions of receiving MT signalling/traffic within the emergency PDU session are clarified ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.50 | S2-2501001 | LS OUT | Approval | [DRAFT] LS reply on emergency services and eDRX | Nokia | Rel-17 | Response to S2-2500044. Postponed in e-mail session | Haris(Qualcomm) objects to any LS response from this meeting until the conditions for receiving MT signalling/traffic within the IMS PDU session are clarified and why special conditions are needed re eDRX and other related functionalities Haris(Qualcomm) objects to any LS response from this meeting until the conditions of receiving MT signalling/traffic within the emergency PDU session are clarified Dongjoo(Nokia) provides feedback to Haris(Qualcomm) ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 19.50 | S2-2500133 | DISCUSSION | Approval | Emergency call back and delayed paging. | Qualcomm Incorporated | Rel-19 | Noted in e-mail session | Noted | |
| 19.50 | S2-2500134 | LS OUT | Approval | [DRAFT] LS on emergency call back and paging | Qualcomm | Rel-19 | Postponed in e-mail session | Dongjoo(Nokia) provides comments Qian (Ericsson) provides comments Dongjoo(Nokia) provides responses to Qian (Ericsson) Dongjoo(Nokia) re-sends feedback to Qian (Ericsson) and provide responses to Haris (Qualcomm) Haris(Qualcomm) asks question to Qian and responds to Dongjoo Qian (Ericsson) provides response to Dongjoo (Nokia) and Haris (Qualcomm) Mehrdad (Mediatek Inc.) suggests to postpone this LS for further discussion but not clear why this stops addressing RAN LS in S2-2500044? Dongjoo(Nokia) provides comments. Qian (Ericsson) provides comments and proposes the way forward. Mehrdad (Mediatek Inc.) agrees with Ericsson proposal. We suggest we continue discussion on LS reply to RAN in S2-2500362 thread independent from outcome of this thread. Dongjoo(Nokia) provides further comments. Haris(Qualcomm) responds Dongjoo(Nokia) provides feedback to Haris (Qualcomm). Dongjoo(Nokia) provides feedback to Haris (Qualcomm) and Qian (Ericsson). Qian (Ericsson) provides further comments Steve (Huawei) comments on what do we do with the LSout? Haris(Qualcomm) suggests to send the LS to CT1 to make some progress but ok also to NOTE if everyone agrees with the analysis in S2-2500133 and there is no need to disable eDRX when emergency PDU session is active Qian (Ericsson) proposes to postpone the LS discussion as well considering the we don't have unified view on the problem and exact questions we need inputs from other groups Dongjoo(Nokia) is fine to postpone this LS. Steve (Huawei) is ok to postpone as well ==== General Revisions Deadline ==== Qian (Ericsson) provides some comments. Mehrdad (Mediatek Inc.) suggests to postpone this LS. ==== Comments Deadline ==== | Postponed |
| 19.50 | - | - | - | LS on Supporting MBS broadcast service for NR NTN | - | - | Docs:=5 | - | |
| 19.50 | S2-2500016 | LS In | Action | LS from RAN WG3: LS on Supporting MBS broadcast service for NR NTN | RAN WG3 (R3-245844) | Rel-19 | Responses drafted in S2-2500155, S2-2500504. Final response in S2-2501329 | Replied to | |
| 19.50 | S2-2500155 | LS OUT | Approval | [DRAFT] Reply LS on Supporting MBS broadcast service for NR NTN | Nokia | Rel-19 | Revision of S2-2411327. Response to S2-2500016. Merged into S2-2501329 | Robbie (Ericsson) suggests merging it to S2-2500504 Thomas (Nokia) is fine with merging to S2-2500504 ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.50 | S2-2500504 | LS OUT | Approval | [DRAFT] Reply LS on Supporting MBS broadcast service for NR NTN | Xiaomi | Rel-19 | Response to S2-2500016. r03 agreed. Revised in e-mail session to S2-2501329, merging S2-2500155 and S2-2500578 | LiMeng (Huawei) is fine for the merger. Robbie (Ericsson) suggests merging S2-2500155 and S2-2500578 into this one Yuxin (Xiaomi) is fine for the merger. Yuxin (Xiaomi) provides r01 Robbie (Ericsson) provides r02 Yuxin (Xiaomi) is fine with r02 ==== General Revisions Deadline ==== Haris(Qualcomm) SA2#167 finishes on 21 Feb. not 22 Feb. Needs to be corrected in final version Thomas(Nokia) provides r03 to fix date of Athens meeting Yuxin(Xiaomi) thanks Haris and Thomas for pointing out and will fix the meeting data in final version ==== Comments Deadline ==== | Revised |
| 19.50 | S2-2501329 | LS OUT | Approval | Reply LS on Supporting MBS broadcast service for NR NTN | SA WG2 | Rel-19 | Revision of S2-2500504r03, merging S2-2500155 and S2-2500578. Approved | Approved | |
| 19.50 | S2-2500577 | CR | Approval | 23.247 CR0372R3 (Rel-19, 'B'): MBS broadcast support for NTN | [Nokia?] Huawei, HiSilicon [, Qualcomm? Ericsson? Xiaomi?] | Rel-19 | Revision of S2-2412570. Confirm Sources! WI Code should be NR_NTN_Ph3-Core! Merged into S2-2501328 | Robbie (Ericsson) replies to LiMeng (Huawei) LiMeng (Huawei) provides comments. Robbie (Ericsson) suggests discussing in this thread Thomas(Nokia) provides comments, Suggests to merge this CR into S2-2500981 Yuxin(Xiaomi) share the view to rule out location-dependent service for NTN LiMeng (Huawei) is fine for merging this CR into S2-2500981, the revision of 0981 is provided. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 19.50 | - | - | - | LS for information | - | - | Docs:=10 | - | |
| 19.50 | S2-2500058 | LS In | Information | LS from SA WG1: Reply LS on PWS support for NB-IoT NTN | SA WG1 (S2-244757) | Rel-19 | Noted in e-mail session | Noted | |
| 19.50 | S2-2500070 | LS In | Information | LS from SA WG5: LS reply on OAM requirements to support regenerative payload | SA WG5 (S5-247311) | Rel-19 | Noted in e-mail session | Noted | |
| 19.50 | S2-2500013 | LS In | Information | LS from RAN WG2: LS on PWS support for NB-IoT NTN | RAN WG2 (R2-2409243) | Rel-19 | Noted in e-mail session | Noted | |
| 19.50 | S2-2500154 | CR | Approval | 23.247 CR0372R2 (Rel-19, 'B'): MBS broadcast support for NTN | Nokia | Rel-19 | Revision of S2-2412570. Revised to S2-2500981 | Revised | |
| 19.50 | S2-2500695 | CR | Approval | 23.501 CR5989 (Rel-17, 'F'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-17 | WI Code should be ARCH_NR_REDCAP! Noted in e-mail session | Haris(Qualcomm) objects to this CR until the conditions for receiving MT signalling/traffic are clarified by CT1 Qian (Ericsson) objects to this CR as we consider RAN is aware of EMC PDU session as stated in the 0134 thread ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.50 | S2-2500696 | CR | Approval | 23.501 CR5990 (Rel-18, 'A'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-18 | WI Code should be ARCH_NR_REDCAP! Noted in e-mail session | Noted | |
| 19.50 | S2-2500697 | CR | Approval | 23.501 CR5991 (Rel-19, 'A'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-19 | WI Code should be ARCH_NR_REDCAP! Noted in e-mail session | Noted | |
| 19.50 | S2-2500997 | CR | Approval | 23.501 CR6047 (Rel-17, 'C'): EDRX for emergency PDU Sessions | Nokia | Rel-17 | Noted in e-mail session | Haris(Qualcomm) objects to the CR in this meeting until the conditions of receiving MT signalling/traffic within the emergency PDU session are clarified Qian (Ericsson) objects to this CR as we consider RAN is aware of EMC PDU session as stated in the 0134 thread ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 19.50 | S2-2500998 | CR | Approval | 23.501 CR6048 (Rel-18, 'A'): EDRX for emergency PDU Sessions | Nokia | Rel-18 | Noted in e-mail session | Noted | |
| 19.50 | S2-2501000 | CR | Approval | 23.501 CR6049 (Rel-19, 'A'): EDRX for emergency PDU Sessions | Nokia | Rel-19 | Noted in e-mail session | Noted | |
| 30 | - | - | - | Project Planning and Management | - | - | Docs:=0 | - | |
| 30.1 | - | - | - | New and Revised Study/Work Items | - | - | Docs:=3 | - | |
| 30.1 | S2-2500543 | SID NEW | Information | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | KPN N.V. | Rel-20 | Noted in e-mail session | Laurent (Nokia): Objects to any version of this Tdoc which is not at the agenda Nassima (KPN N.V.) requests to note/withdraw this Tdoc ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 30.1 | S2-2500787 | WID REVISED | Approval | Revised WID on Energy Efficiency and Energy Saving. | Samsung, Lenovo (Rapporteurs) | Rel-19 | Postponed in e-mail session | Marco (Huawei) provide r01 Alessio(Nokia) suggests to postpone this to Athens meeting as it sems people want to cherry pick the updates now, unless we approve what the rapporteur submitted. Jungshin (Samsung) agrees to postpone the WID discussion to the Feb. meeting. LaeYoung (LGE) also suggests to POSTPONE this revised WID to February meeting. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 30.1 | S2-2500934 | WID NEW | Information | New WID on Architecture support of Ambient power-enabled Internet of Things. | Huawei, HiSilicon | Rel-19 | Postponed in e-mail session | Dongjoo(Nokia) ) suggests to postpone this to Athens meeting as we should conclude the study first. ==== General Revisions Deadline ==== Sebastian (Qualcomm) supports postponement ==== Comments Deadline ==== | Postponed |
| 30.2 | - | - | - | Submissions for TEI20 | - | - | Docs:=0 | - | |
| 30.3 | - | - | - | TR and TS Cover sheets | - | - | Docs:=1 | - | |
| 30.3 | S2-2500376 | TS OR TR COVER | Approval | Cover sheet for presentation of TR 23.700-13 to TSG SA for Approval | OPPO | Rel-19 | Postponed in e-mail session | Dongjoo(Nokia) supports the view from Shabnam (Ericsson) that this paper is pre-mature to be discussed in this meeting. Shabnam (Ericsson) proposes to note the cover sheet and handle the document when the content and status/dependency are clearer during/at SA2#167, we have one meeting before plenary. ==== General Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 30.4 | - | - | - | WID Status Reports | - | - | Docs:=0 | - | |
| 30.5 | - | - | - | Review of the Work Plan | - | - | Docs:=4 | - | |
| 30.5 | S2-2500080 | OTHER | Discussion | Structure of WID Names & Acronyms | MCC Work Plan Manager | Rel-19 | CC#3: Noted | Noted | |
| 30.5 | S2-2500984 | WORK PLAN | Endorsement | SA WG2#166 AHE Work Planning slides | SA WG2 Chair | Revised to S2-2501074. | Revised | ||
| 30.5 | S2-2501074 | WORK PLAN | Endorsement | SA WG2#166 AHE Work Planning slides | SA WG2 Chair | Revision of S2-2500984. CC#2: Endorsed | Endorsed | ||
| 30.5 | S2-2500986 | WORK PLAN | Endorsement | SA WG2#166AHE Work Planning spreadsheet | SA WG2 Chair | CC#2: Noted | Noted | ||
| 30.6 | - | - | - | Planning future meetings | - | - | Docs:=3 | - | |
| 30.6 | S2-2500989 | OTHER | Information | SA Plenary outcomes and guidance to SA WG2 | SA WG2 Chair | WITHDRAWN | Withdrawn | ||
| 30.6 | S2-2500996 | OTHER | Information | Rel-20 5GA NWM discussion guidance and plan | SA WG2 Chair | Revised to S2-2501075. | Revised | ||
| 30.6 | S2-2501075 | OTHER | Information | Rel-20 5GA NWM discussion guidance and plan | SA WG2 Chair | Revision of S2-2500996. CC#2: Endorsed | Andy (Samsung) provides updated Rel-20 5GA NWM discussion guidance and plan based on discussions during CC#2 in S2-2501075. ==== Comments Deadline ==== | Endorsed | |
| 30.7 | - | - | - | 5GA SIDs/WIDs for Rel-20 | - | - | Docs:=0 | - | |
| 30.8 | - | - | - | 6G SID(s) for Rel-20 | - | - | Docs:=0 | - | |
| 30.9 | - | - | - | Exception sheets | - | - | Docs:=0 | - | |
| 31 | - | - | - | Close of meeting | - | - | Docs:=0 | - | |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=73 | - | |
| 99 | S2-2501313 | Other | Approval | Clarifications of QoS monitoring capability configuration and transfer within 5GC | China Telecom | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500924 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Samsung | Rel-17 | Response to S2-2500039. WITHDRAWN | Withdrawn | |
| 99 | S2-2500822 | CR | Approval | 23.502 CR5290 (Rel-19, 'B'): Update NEF services to align with IMS AS services | Huawei, HiSilicon | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500826 | CR | Approval | 23.228 CR1571 (Rel-19, 'B'): Correction on IMS data channel interworking | Huawei, HiSilicon | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500187 | CR | Approval | 23.288 CR1320 (Rel-19, 'C'): Enabling OSE data Analytics analyse user plane latency | Verizon Switzerland AG | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500400 | CR | Approval | 23.288 CR1339 (Rel-19, 'F'): KI#1 Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note | Ericsson | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500993 | CR | Approval | 23.501 CR6045 (Rel-18, 'F'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500994 | CR | Approval | 23.501 CR6046 (Rel-19, 'A'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2501029 | CR | Approval | 23.502 CR5317 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | WITHDRAWN | Withdrawn | ||
| 99 | S2-2501032 | CR | Approval | 23.502 CR5318 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | WITHDRAWN | Withdrawn | ||
| 99 | S2-2501051 | CR | Approval | 23.502 CR5325 (Rel-19, 'F'): Clarification for PCF behaviour for generating matchall PCC rules for MA PDU Session | Samsung | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500564 | CR | Approval | 23.503 CR1483 (Rel-19, 'D'): Editorial changes on provisioning PCC rule for ATSSS | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500550 | CR | Approval | 23.501 CR5974 (Rel-19, 'F'): Update of UE ATSSS capability | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500560 | CR | Approval | 23.501 CR5977 (Rel-19, 'D'): Clarification on steering functionalities description | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500099 | CR | Approval | 23.501 CR5884 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | Nokia, NTT Docomo | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500217 | CR | Approval | 23.503 CR1460 (Rel-18, 'F'): URSP Guidelines updates of GSMA | Nokia | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500218 | CR | Approval | 23.503 CR1461 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500563 | CR | Approval | 23.503 CR1482 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500444 | CR | Approval | 23.501 CR5953 (Rel-19, 'B'): Providing Multi-Modal Awareness to NG-RAN | InterDigital Pennsylvania | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500174 | CR | Approval | 23.501 CR5896 (Rel-19, 'F'): Definition of non-3GPP device connection information | Qualcomm Incorporated, InterDigital | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500473 | CR | Approval | 23.256 CR0166 (Rel-19, 'F'): Altitude reporting update | Datang Mobile Com. Equipment | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500331 | P-CR | Approval | 23.700-13: PCR to TS 23.xyz: Ambient IoT Services. | CATT | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500332 | P-CR | Approval | 23.700-13: PCR to TS 23.xyz: Assistance Information used by AIoT RAN. | CATT | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500701 | CR | Approval | 23.228 CR1521R5 (Rel-19, 'B'): 23228 Mobility procedure when satellite changes - continuation | NTT DOCOMO, [vivo] | Rel-19 | Revision of S2-2412672. WITHDRAWN | Withdrawn | |
| 99 | S2-2500702 | CR | Approval | 23.228 CR1522R5 (Rel-19, 'B'): 23228 Mobility procedure when satellite changes - ground fallback | NTT DOCOMO, [vivo] | Rel-19 | Revision of S2-2412673. WITHDRAWN | Withdrawn | |
| 99 | S2-2500749 | CR | Approval | 23.502 CR5278 (Rel-19, 'B'): MWAB-UE Mobility Restriction | Samsung | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500791 | CR | Approval | 23.503 CR1490 (Rel-19, 'F'): Clarification on EIF functionality | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500795 | CR | Approval | 23.501 CR6002 (Rel-19, 'F'): Support of NF selection based on energy information | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2500797 | CR | Approval | 23.501 CR6003 (Rel-19, 'F'): Support of UPF (re)-selection based on energy information | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn |