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 meeting including the
Chairman and Vice Chairman. In case of question I recommend that you contact
your legal counsel. The
leadership shall conduct the present meeting with impartiality and in the
interests of 3GPP. Furthermore,
I would like to remind you that timely submission of work items in advance of
TSG/WG meetings is important to allow for full and fair consideration of such
matters." |
| AI | TD# | Type | Doc For | Subject | Source | Rel | Comments | e-mail_Discussion | Result |
| 0 | - | - | - | All Agenda Items | - | - | Docs:=0 | - | |
| 1.1 | - | - | - | Opening of the meeting | - | - | Docs:=0 | - | |
| 2 | - | - | - | Agenda | - | - | Docs:=1 | - | |
| 2 | S2-2108249 | AGENDA | Approval | SA WG2 #148E Meeting Agenda | SA WG2 Chair | Approved | Approved | ||
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#147E Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2108250 | REPORT | Approval | Auto-Generated Report of SA WG2 meeting #147E | SA WG2 Secretary | Approved | Approved | ||
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=37 | - | |
| 4.1 | S2-2108251 | LS In | Action | LS from SA WG6: Reply LS on IP address to GPSI translation | SA WG6 (S6-211082) | Rel-17 | Revision of S2-2106990 from S2#147E. Noted | Tao(VC) suggest to NOTE this LS since there seems no specific action needed and be postponed for 3 meetings since May this year. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108256 | LS In | Action | Reply LS on IP address to GPSI translation | SA WG3 (S3-212355) | Rel-17 | Revision of S2-2107003 from S2#147E. Noted | Tao(VC) suggest to NOTE this LS since there seems no specific action needed. It lasted in SA2 for 3 meetings and can be referred later on if needed. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108257 | LS In | Action | LS from GSMA 5GJA: LS on Traffic Categories in URSP | GSMA 5GJA (5GJA17_104) | - | Revision of S2-2107006 from S2#147E. Response drafted in S2-2108979. Postponed | Postponed | |
| 4.1 | S2-2108979 | LS OUT | Approval | [DRAFT] Reply LS to GSMA NG 5GJA on Traffic Categories in URSP | Apple | Rel-18 | Response to S2-2108257. Noted | Haiyang (Huawei) provides r01 Krisztian (Apple) provides r02. Chia-Lin (MediaTek) suggest to postpone LS ==== Revisions Deadline ==== Krisztian (Apple) proposes to send this LS as an interim update on the SA2 progress. SA2 can further update GSMA with new information, once available. Tao (VC) check can we go with r02 Chia-Lin (MediaTek) still think no rush to send LS OUT to GSMA and sugges to send out a LS to SA to ask SA to handle this feedbeack to GSMA once SA has done with all the Rel-18 SID prioritization ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108268 | LS In | Action | LS from CT WG4: LS on creating a new stage 2 TS for SMS-SBI | CT WG4 (C4-214540) | Rel-17 | Revision of S2-2107033 from S2#147E. Final response in S2-2109340 | Tao(VC) asked people view whether we confirm this with response or we NOTE this LS. ==== Revisions Deadline ==== Hannu (Nokia) comments that CT4 depends on answers from the other groups, CT1 have already replied in S2-2108275 and SA2 DRAFT reply with similar contents was already shared but not processed due to lack of time in SA2 #147E. Hannu shares draft LS out that was already technically reviewed last time and proposes that a tdoc number should be assigned to it so that it can be handled in CC#2. Leo (Deutsche Telekom) supports Nokia's proposal. SA2 should send a reply LS at this SA2 meeting. The version in the DRAFTS folder is fine and can be approved. ==== Comments Deadline ==== Hannu (Nokia) requests LS In S2-2108268 to be marked up for CC in order to assign a tdoc number for the proposed reply. | Replied to |
| 4.1 | S2-2109340 | LS OUT | Approval | Reply LS on creating a new stage 2 TS for SMS-SBI | SA WG2 | - | Created at CC#2. Response to S2-2108268. This LS was approved. | Approved | |
| 4.1 | S2-2108272 | LS In | Action | LS from RAN WG3: Reply LS on RACS capability detection with S1 and NG handover | RAN WG3 (R3-214373) | Rel-16 | Revision of S2-2107052 from S2#147E. Noted | Alessio (Nokia): We propose to not this incoming LS. we have corresponding CR in AI#7.12 'Optimisations on UE radio capability signalling (RACS)' ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108275 | LS In | Information | Reply LS on creating a new stage 2 TS for SMS-SBI | CT WG1 (C1-216043) | Rel-17 | Noted | Hannu (Nokia) proposes to note the LS in. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108289 | LS In | Information | LS from ETSI TC LI: Reply LS on PSCELL ID availability in SGW CDR | ETSI TC LI (LI(21)P58049r1) | Noted | Hannu (Nokia) proposes to note the LS in as there is no SA2 action remaining. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 4.1 | S2-2108291 | LS In | Information | LS from APT Wireless Group: APT REPORT ON EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS | APT Wireless Group (AWG28_OUT03 (Rev.1)) | Noted | Noted | ||
| 4.1 | S2-2108293 | LS In | Information | LS from SA WG5: Reply LS to GSMA on new whitepaper E2E Network Slicing Architecture | SA WG5 (S5-215083) | Rel-17 | Noted | Peter (Ericsson) propose to note the incoming LS ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108295 | LS In | Information | LS from SA WG6: LS on network slice management service consumption | SA WG6 (S6-212460) | Rel-18 | Noted | Peter (Ericsson) propose to note the incoming LS ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108312 | DISCUSSION | Discussion | Discussion of Open-Source-Defined Multi-Access Edge Computing | Xidian University | Noted | Juan Zhang (Qualcomm) clarifies that the discussion paper was not from Qualcomm. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 4.1 | S2-2108986 | DISCUSSION | Discussion | NRF Profile documentation | Nokia, Nokia Shanghai-Bell | Noted | Josep (DT) prefers option 2. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 4.1 | S2-2108384 | DISCUSSION | Agreement | Documentation Handling on NF profile. | Ericsson | Rel-17 | Noted | Noted | |
| 4.1 | S2-2108385 | CR | Approval | 23.501 CR3369 (Rel-17, 'F'): Documentation handling for description of NF profile | Ericsson | Rel-17 | Noted | Josep (DT) thinks that this is a bad idea. Option 2 in 8986 is a better way. Judy (Ericsson) asks Josep (DT) for clarification and comments Josep (DT) replies. Shabnam (Ericsson) replies Josep (DT) replies. Better current duplication than partial duplication Judy (Ericsson) provides r01 and comment Devaki (Nokia) objects to the CR and its revisions. This CR is basically introducing text to state that the section is 'incomplete' thus unnecessary, furthermore, it disregards NF registration using OA&M. Judy (Ericsson) is not sure how Devaki (Nokia) concludes 'the section is 'incomplete' thus unnecessary'. The intent of the CR is to state that 6.2.6 is incomplete, and we complete it trying to avoid duplication. Please see a revision in r02 and request Devaki (Nokia) to reconsider. ==== Revisions Deadline ==== Devaki (Nokia) comments that the crux of our concern is in the statement quoted by Judy 'The intent of the CR is to state that 6.2.6 is incomplete' (as our preference is to complete it), open to rediscuss the split between different specs until January meeting. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108386 | CR | Approval | 23.502 CR3135R1 (Rel-17, 'F'): SMF+PGW-C assigned PDU Session ID | Ericsson | Rel-17 | Revision of (Postponed) S2-2107164 from S2#147E. Source to WG incorrect. CC#2: Noted | Judy (Ericsson) provide r01 based on the discussion in 8267 thread. Susan (Huawei) provides comments. Irfan (Cisco) raises technical concern with r01. Zhendong (ZTE): provides response. Irfan (Cisco) retracts his previous comment on r01. Zhendong (ZTE): provides r02 Susan (Huawei) replies to Zhendong (ZTE). Irfan (Cisco) provides r03 Laurent (Nokia): provides r04 Judy (Ericsson) provide r05 Zhendong (ZTE): provides r06 Zhendong (ZTE): provides r07 Susan (Huawei) objects to all revisions of this CR, i.e. r01 to r07, can accept the original one. Laurent (Nokia): answers ==== Revisions Deadline ==== Tao(VC) check whether r00 agreeable or not. Judy (Ericsson) accepts r00, r01, r02, r05, r07 and object to other revisions, and responds to Laurent (Nokia) Irfan (Cisco) accepts r07 Sebastian (Qualcomm) objects to r00 Sebastian (Qualcomm) proposes to establish a WA based on r07 in CC#2 Zhendong (ZTE): accept r07 Laurent (Nokia): supports a WA at CC2 based on R07 Judy (Ericsson) responds to Laurent (Nokia) ==== Comments Deadline ==== Zhuoyi (China Telecom) proposes to postpone this CR. Irfan (Cisco) proposes to atleast technically endorse r07. | Noted |
| 4.1 | S2-2108412 | CR | Approval | 23.501 CR2385R6 (Rel-17, 'C'): Support of the mapping from IP addressing information provided to an AF to the user identity | [Nokia, Nokia Shanghai Bell], Ericsson | Rel-17 | Revision of (Postponed) S2-2107653 from S2#147E. r05 agreed. Revised to S2-2109140, merging S2-2108923 | Laurent (Nokia): provides r01 Dario (Qualcomm) privides r02 Magnus O (Ericsson) provides r03 Jari (NTT DOCOMO) questions for clarification Saso (Intel) seeks clarification on UE address. Magnus O (Ericsson) provides r04 Jari (NTT DOCOMO) comments Magnus O (Ericsson) replies Laurent (Nokia): answers and provides r05 Magnus O (Ericsson) is fine with r05 ==== Revisions Deadline ==== Dario (Qualcomm) is OK with r05 Hui (Huawei) is OK with r05 ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2109140 | CR | Approval | 23.501 CR2385R8 (Rel-17, 'C'): Support of the mapping from IP addressing information provided to an AF to the user identity | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108412r05, merging S2-2108923. Approved | Agreed | |
| 4.1 | S2-2108413 | CR | Approval | 23.502 CR2926R3 (Rel-17, 'B'): AF specific UE ID retrieval | Ericsson | Rel-17 | Revision of (Postponed) S2-2107248 from S2#147E. r06 agreed. Revised to S2-2109141, merging S2-2108924 | Laurent (Nokia): provides r01 Magnus O (Ericsson) comments Saso (Intel) seeks clarification on UE address. Dario (Qualcomm) provides r02 and asks further questions. Hyesung (Samsung) provides r03 and asks questions. Magnus O (Ericsson) provides r04 Jari (NTT DOCOMO) comments Magnus O (Ericsson) replies Dario (Qualcomm) provides r05 Saso (Intel) comments. Laurent (Nokia): provides r06 = r05+ support of MAC address Florin(Broadcom) supports having the support for the MAC address and as a result r06 provided by Laurent. Magnus O (Ericsson) is fine with r06 Hui (Huawei) fine with supporting MAC address. ==== Revisions Deadline ==== Laurent (Nokia): I have concerns with not supporting MAC address and thus prefers MUCH r06 wrt R04 or R05 Hyesung (Samsung) is fine with r04, r05, 06 Dario (Qualcomm) is OK with r06 ==== Comments Deadline ==== | Revised |
| 4.1 | S2-2109141 | CR | Approval | 23.502 CR2926R4 (Rel-17, 'B'): AF specific UE ID retrieval | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108413r06, merging S2-2108924. Approved | Agreed | |
| 4.1 | S2-2108267 | LS In | Action | LS from CT WG3: LS on PDU Session ID assignment for the Interworking scenario | CT WG3 (C3-214527) | Rel-17 | Revision of S2-2107031 from S2#147E. Responses drafted in S2-2108589 and S2-2108853. Postponed | Judy (Ericsson) follows Zhendong suggestion to use this thread to discuss different proposals (in e.g. 8486, 8591 and 8386). Zhendong (ZTE): provides the response Judy (Ericsson) responds to Zhendong (ZTE). Zhendong (ZTE): provides the repsonse Zhendong (ZTE): ask for clarification Susan (Huawei) provides comments. Laurent (Nokia): Comments Irfan (Cisco) comments, supports UDM based approach Sebastian (Qualcomm) comments that the scenario at hand is realistic and supports a UDM based approach Judy (Ericsson) provide r01 based on the discussion in 8267 thread. Zhendong (ZTE): provides clarification Zhendong (ZTE): provides comments. Judy (Ericsson) clarifies Zhendong (ZTE): provides response Judy (Ericsson) asks Tao (chair) to ignore r01 which is not intended for this paper (but for 8386), and responds to Zhendong (ZTE). Zhendong (ZTE): respond to judy Susan (Huawei): Cannot agree with the UDM based solution. Judy (Ericsson) responds to Susan (Huawei) Susan (Huawei) responds to Judy (Huawei) Laurent (Nokia): we can easily live with Judy's approach !! ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 4.1 | S2-2108589 | LS OUT | Approval | [DRAFT] Reply LS on PDU Session ID assignment for the Interworking scenario | Huawei, HiSilicon | Rel-16 | Revision of (Postponed) S2-2107485 from S2#147E. Response to S2-2108267. Noted | Laurent (Nokia): Objects to any revision of this Tdoc Zhendong (ZTE): simillar concern,and propose to discuss in 8267 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108853 | LS OUT | Approval | [DRAFT] LS on PDU Session ID assignment for the Interworking scenario | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2108267. Noted | Judy (Ericsson) prepared two revisions: r01 replies with a solution, and r02 replies that no consensus reached on the solution ==== Revisions Deadline ==== Tao(VC) check whether r01 or r02 agreeable based on the discussion under 8267 Judy (Ericsson) assumes we can go for r01 if any revision of 8386 can be agreed, otherwise r02 if we don't want to delay the response further. Tao(VC) let's check r01 agreeable or not then Sebastian (Qualcomm) is ok with r01 but objects to r02; we need to solve this issue Zhendong (ZTE): agree with r01 Susan (Huawei) is ok with r02, object to r01 unless r00 of S2-2108386 can be agreeable. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108486 | CR | Approval | 23.502 CR3249 (Rel-17, 'F'): PDU Session ID assignment for non N1-NAS UEs | Cisco Systems, Nokia, Nokia Shanghai Bell, ZTE | Rel-17 | Noted | Judy (Ericsson) has major concern on the proposal that UDM allocate PDU Session ID, explained Zhendong (ZTE): propose to discuss in the 8267 ==== Revisions Deadline ==== Susan (Huawei) objects to this CR. ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108497 | DISCUSSION | Discussion | Discussion and proposal on PDU session ID issue in CT WG3 LS. | ZTE, Nokia, Nokia Shanghai Bell, Cisco Systems | Rel-17 | Noted | Noted | |
| 4.1 | S2-2108590 | DISCUSSION | Agreement | Discussion on PDU Session ID assignment for interworking scenario. | Huawei, HiSilicon | Noted | Noted | ||
| 4.1 | S2-2108591 | CR | Approval | 23.502 CR3190R1 (Rel-16, 'F'): Correction on PDU Session ID assignment by SMF+PGW-C | Huawei, HiSilicon | Rel-16 | Revision of (Postponed) S2-2107486 from S2#147E. Noted | Laurent (Nokia): Objects to any revision of this Tdoc Zhendong (ZTE): simillar concern, and propose to discuss in 8267 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108592 | CR | Approval | 23.502 CR3191R1 (Rel-17, 'A'): Correction on PDU Session ID assignment by SMF+PGW-C | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107487 from S2#147E. Noted | Laurent (Nokia): Objects to any revision of this Tdoc Zhendong (ZTE): simillar concern, and propose to discuss in 8267 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2108923 | CR | Approval | 23.501 CR2385R7 (Rel-17, 'F'): Support of the mapping from IP addressing information provided to an AF to the user identity | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2107653 from S2#147E. Merged into S2-2109140 | Laurent (Nokia): asks 8923 (my Tdoc) to be merged in 8412 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 4.1 | S2-2108924 | CR | Approval | 23.502 CR2329R5 (Rel-17, 'F'): Support of the mapping from IP addressing information provided to an AF to the user identity | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2107654 from S2#147E. Merged into S2-2109141 | Magnus O (Ericsson) propose to merge into 8413 Laurent (Nokia): Oups I forgot to tell my willingness to merge, yes ok to merge ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 4.1 | S2-2108296 | LS In | Information | LS from GSMA NRG: LS from NRG to 3GPP on Emergency Communication Improvement | GSMA NRG (NRG_012_200) | Response drafted in S2-2108981. Noted | Leo (Deutsche Telekom) proposes to Note the incoming LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 4.1 | S2-2108981 | LS OUT | Approval | [DRAFT] Reply LS on Emergency Communication Improvement | Orange | Response to S2-2108296. Noted | Leo (Deutsche Telekom) proposes to Note this reply LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 4.1 | S2-2108980 | SID NEW | Approval | New WID on Study on Emergency Short Message Service . | Orange | Rel-18 | Noted | Antoine (Orange) proposes to Note this WID. Leo (Deutsche Telekom) agrees to Note this WID. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 4.1 | S2-2109006 | LS In | Information | LS from RAN WG3: LS On Source IP address clarifications | RAN WG3 (R3-216139) | Rel-16 | Noted | Noted | |
| 4.1 | S2-2109007 | LS In | Action | LS from RAN WG3: Reply to Reply LS On ACL support for Indirect Data Forwarding | RAN WG3 (R3-216140) | Rel-16 | Postponed | Qian (Ericsson) proposes to POSTPONE the paper since no action can be agreed. ==== Comments Deadline ==== | Postponed |
| 4.1 | S2-2109010 | LS In | Information | LS from RAN WG3: Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces | RAN WG3 (R3-216233) | Rel-17 | Noted | Noted | |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=1 | - | |
| 4.2 | S2-2108884 | CR | Approval | 23.501 CR3313R2 (Rel-17, 'F'): Corrections on TSCTSF selection and residence time calculation | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2108138 from S2#147E. Approved | Agreed | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=6 | - | |
| 5.1 | S2-2108352 | CR | Approval | 23.032 CR0020 (Rel-16, 'F'): Introducing new high accuracy GAD shape with scalable uncertainty | Ericsson, T-Mobile USA | Rel-16 | r03 agreed. Revised to S2-2109024. | Guillaume (MediaTek Inc.) provides r01. Richard (Ericsson) provides r02. Richard (Ericsson) provides r03. ==== Revisions Deadline ==== Stephen (Qualcomm) comments the r03 is fine with us ==== Comments Deadline ==== | Revised |
| 5.1 | S2-2109024 | CR | Approval | 23.032 CR0020R1 (Rel-16, 'F'): Introducing new high accuracy GAD shape with scalable uncertainty | Ericsson, T-Mobile USA | Rel-16 | Revision of S2-2108352r03. Approved | Agreed | |
| 5.1 | S2-2108353 | CR | Approval | 23.032 CR0021 (Rel-17, 'A'): Introducing new high accuracy GAD shape with scalable uncertainty | Ericsson, T-Mobile USA | Rel-17 | r00 agreed. Revised to S2-2109025. | Guillaume (MediaTek Inc.) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.1 | S2-2109025 | CR | Approval | 23.032 CR0021R1 (Rel-17, 'A'): Introducing new high accuracy GAD shape with scalable uncertainty | Ericsson, T-Mobile USA | Rel-17 | Revision of S2-2108353r00. Approved | Agreed | |
| 5.1 | S2-2108767 | CR | Approval | 23.303 CR0330R1 (Rel-17, 'F'): TS 23.303 corrections discovered when working on 5G ProSe | Nokia, Nokia Shanghai Bell, LG Electronics | Rel-17 | Revision of (Postponed) S2-2107565 from S2#147E. r02 agreed. Revised to S2-2109026. | Judy (Ericsson) comments and provide r01 LaeYoung (LGE) provide r02. Judy (Ericsson) is fine with r02 Hannu (Nokia) supports r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.1 | S2-2109026 | CR | Approval | 23.303 CR0330R2 (Rel-17, 'F'): TS 23.303 corrections discovered when working on 5G ProSe | Nokia, Nokia Shanghai Bell, LG Electronics, Ericsson | Rel-17 | Revision of S2-2108767r02. Approved | Agreed | |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=11 | - | |
| 5.2 | S2-2108346 | CR | Approval | 23.503 CR0671 (Rel-16, 'F'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-16 | r04 agreed. Revised to S2-2109027. | Pallab (Nokia) comments. Belen (Ericsson) replies to comments. Mirko (Huawei) comments. Belen (Ericsson) accpets the proposal to use predefined PCC Rules Belen (Ericsson) provides r01 Pallab (Nokia) provides r02 Belen (Ericsson) cannot accept r02, provides r03 Pallab (Nokia) is OK with r03 Mirko (Huawei) provides r04. Pallab (Nokia) is OK with r04 and would like to co-sign. Belen (Ericsson) okay with r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.2 | S2-2109027 | CR | Approval | 23.503 CR0671R1 (Rel-16, 'F'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia, Nokia | Rel-16 | Revision of S2-2108346r04. Approved | Agreed | |
| 5.2 | S2-2108347 | CR | Approval | 23.203 CR1137 (Rel-16, 'F'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-16 | r02 + changes agreed. Revised to S2-2109332. | Pallab (Nokia) has same comments as in 8346. Belen (Ericsson) suggests to discuss S2-2108346 first and reuse the same text here. Belen (Ericsson) provides r01. Belen (Ericsson) provides r02 ==== Revisions Deadline ==== Pallab (Nokia) comments on r02 Belen (Ericsson) ask to add this CR to CC#2 ==== Comments Deadline ==== | Revised |
| 5.2 | S2-2109332 | CR | Approval | 23.203 CR1137R1 (Rel-16, 'F'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-16 | Revision of S2-2108347r02 + changes. Approved | Agreed | |
| 5.2 | S2-2108348 | CR | Approval | 23.503 CR0672 (Rel-17, 'A'): Access network info request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-17 | r00 agreed. Revised to S2-2109028. | Belen (Ericsson) suggests to discuss S2-2108346 first and reuse the same text here. Belen (Ericsson) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.2 | S2-2109028 | CR | Approval | 23.503 CR0672R1 (Rel-17, 'A'): Access network info request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-17 | Revision of S2-2108348r00. Approved | Agreed | |
| 5.2 | S2-2108349 | CR | Approval | 23.203 CR1138 (Rel-17, 'A'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-17 | r01 + changes agreed. Revised to S2-2109333. | Belen (Ericsson) suggests to discuss S2-2108346 first and reuse the same text here. Belen (Ericsson) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.2 | S2-2109333 | CR | Approval | 23.203 CR1138R1 (Rel-17, 'A'): Access network information request without PCC rules | Ericsson, AT&T, Deutsche Telekom, Telecom Italia | Rel-17 | Revision of S2-2108349r01 + changes. Approved | Agreed | |
| 5.2 | S2-2108350 | DISCUSSION | Agreement | Support for LI in SMS and Location Retrieval. | Ericsson | Rel-16 | Noted | Noted | |
| 5.2 | S2-2108387 | CR | Approval | 23.401 CR3670 (Rel-17, 'F'): Correction to MME handling EPS bearer QoS | Ericsson | Rel-17 | r01 agreed. Revised to S2-2109029. | Mirko (Huawei) provides r01. Judy (Ericsson) thanks Mirko (Huawei) for the revision and is fine with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 5.2 | S2-2109029 | CR | Approval | 23.401 CR3670R1 (Rel-17, 'F'): Correction to MME handling EPS bearer QoS | Ericsson | Rel-17 | Revision of S2-2108387r01. Approved | Agreed | |
| 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:=9 | - | |
| 6.1 | S2-2108298 | LS in | Action | LS from GSMA 5GJA: Reply LS from 5GJA to CT WG4 and SA WG3 on Using N32 for Interconnect Scenarios | GSMA 5GJA (5GJA#18 a Doc 112_r2) | Response drafted in S2-2109015. Final response in S2-2109334 | Leo (Deutsche Telekom): proposes to change the 'Result' for this TD from 'OPEN' to 'Replied to' when S2-2109015 is approved. ==== Comments Deadline ==== | Replied to | |
| 6.1 | S2-2109015 | LS OUT | Approval | [DRAFT] Reply LS on Using N32 for Interconnect Scenarios | NTT DOCOMO | Created at CC#1. Response to S2-2108298. r01 agreed. Revised to S2-2109334. | Leo (Deutsche Telekom) provides r01. Atsushi (NTT Docomo) is fine with r01. ==== Revisions Deadline ==== Laurent (Nokia): Comments ==== Comments Deadline ==== | Revised | |
| 6.1 | S2-2109334 | LS OUT | Approval | Reply LS on Using N32 for Interconnect Scenarios | SA WG2 | - | Revision of S2-2109015r01. Approved | Approved | |
| 6.1 | S2-2108796 | CR | Approval | 23.501 CR3429 (Rel-17, 'F'): Clarification on rejected S-NSSAI andEquivalent PLMNs TAIs in the RA | Nokia, Nokia Shanghai Bell. | Rel-17 | Noted | Peter (Ericsson) provides comments and propose to note the CR and focus on the NSAC issue as done by other CRs in 8.4 Jinguo(ZTE) agree with Peter. Lets focus on the LS from CT1 ==== Revisions Deadline ==== alessio(Nokia) it is a pity this was requested to be noted. no one questions the network side sends for the current PLMN but then if it includes TAIs of other PLMNs in RA the UE behavior is not specified. alessio(Nokia) BTW if Ericsson or ZTE prefer to continue discussing this now I am ok. we need to eventually have some text like this one. ==== Comments Deadline ==== | Noted |
| 6.1 | S2-2108962 | CR | Approval | 23.501 CR3460 (Rel-15, 'F'): Clarifications on SEPP | Deutsche Telekom | Rel-15 | Noted | Laurent (Nokia): provides r01 and is not sure this is FASMO Fenqin (Huawei): comments Leo (Deutsche Telekom): move to AI#6.1 Leo (Deutsche Telekom): is fine to NOTE the CR for Rel-15 and do error correction from Rel-16 onwards Peter Hedman (Ericsson) provides r05 Leo (Deutsche Telekom) clarifies that the proposed changes are in S2-2108964r05 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.1 | S2-2108964 | CR | Approval | 23.501 CR3461 (Rel-16, 'A'): Clarifications on SEPP | Deutsche Telekom | Rel-16 | r05 agreed. Revised to S2-2109030. | Laurent (Nokia): provides R01 and r02 (same content but small 'r' in zip name) Leo (Deutsche Telekom): move to AI#6.1 Leo (Deutsche Telekom): comments and provides r03 Leo (Deutsche Telekom): provides r04 Leo (Deutsche Telekom): is fine with r05 provided by Ericsson ==== Revisions Deadline ==== Leo (Deutsche Telekom): r05 shall be approved. It is no longer a mirror, it is now a CAT-F CR. ==== Comments Deadline ==== | Revised |
| 6.1 | S2-2109030 | CR | Approval | 23.501 CR3461R1 (Rel-16, 'F'): Clarifications on SEPP | Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson | Rel-16 | Revision of S2-2108964r05. Approved | Agreed | |
| 6.1 | S2-2108970 | CR | Approval | 23.501 CR3462 (Rel-17, 'A'): Clarifications on SEPP | Deutsche Telekom | Rel-17 | r01 agreed. Revised to S2-2109031. | Qianghua (Huawei) provides comments Leo (Deutsche Telekom) provides r01 which is no longer a mirror. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.1 | S2-2109031 | CR | Approval | 23.501 CR3462R1 (Rel-17, 'F'): Clarifications on SEPP | Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108970r01. Approved | Agreed | |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=10 | - | |
| 6.2 | S2-2108374 | CR | Approval | 23.502 CR3150R2 (Rel-17, 'F'): Clarification on rerouted Registration Request message | Ericsson, Huawei, HiSilicon, NEC | Rel-17 | Revision of (Endorsed) S2-2107865 from S2#147E. Technically endorsed | Alessio(Nokia) proposes to postpone this CR till we receive reply LS from SA3. if it comes in this week we can check it (not sure we will get one). for now it should remain with same status as last meeting. ==== Revisions Deadline ==== Qian (Ericsson) propose to mark it as Technically Endorsed (same as last meeting) due to lack of LS response. ==== Comments Deadline ==== | Endorsed |
| 6.2 | S2-2108442 | CR | Approval | 23.502 CR3237 (Rel-17, 'F'): UE SM context fetch in registration procedure during inter-network mobility | Samsung | Rel-17 | CC#2: Postponed | Youngkyo(Samsung) provides a revision r01. Myungjune (LGE) proposes to merge this CR into S2-2108462 (AI#8.2). Youngkyo(Samsung) replies and proposes to merge S2-2108462 (AI#8.2) into this CR. Peter Hedman (Ericsson) provides comments and technically prefer 08642. Qianghua (Huawei) prefers S2-2108462 Hannu (Nokia) is OK to merge this CR into S2-2108462 and would have comments if 8442 is expected to continue Youngkyo(Samsung) is okay to merge this CR into S2-2108462. ==== Revisions Deadline ==== Youngkyo(Samsung) requests to take all the proposal of S2-2108462r03(AI#8.2) into the S2-2108462, which is marked as merged into S2-2108462 . Myungjune (LGE) supports Youngkyo's suggestion ==== Comments Deadline ==== | Postponed |
| 6.2 | S2-2108470 | CR | Approval | 23.502 CR3245 (Rel-17, 'F'): Updating AMF with new Routing Indicator Data if re-registration is not triggered | Ericsson | Rel-17 | Postponed | Susan (Huawei) provides comments and r01. Fei (OPPO) asks questions. Josep (DT) prefers the approach in r01. Provides r02 adding AUSF Peter Hedman (Ericsson) provides replies and comments that r01 does not work Susan (Huawei) replies to Peter Hedman (Ericsson). ==== Revisions Deadline ==== Peter Hedman (Ericsson) provides reply Susan (Huawei) replies to Peter Hedman (Ericsson) and propose to postpone the CR to next meeting. Hannu (Nokia) supports the proposal to postpone. Peter Hedman (Ericsson) provides replies that error then remains in the TS ==== Comments Deadline ==== | Postponed |
| 6.2 | S2-2108613 | CR | Approval | 23.502 CR3262 (Rel-16, 'F'): AMF re-allocation during inter PLMN mobility | ZTE | Rel-16 | r01 agreed. Revised to S2-2109335. | Fenqin (Huawei) comments Jinguo(ZTE) response and suggest to take majority views. Alessio(Nokia) proposes this CR can be used as basis of a simple clarification where we say that there is no reallocation in connected mode. this may need to go back to the earlier releases too. Jinguo(ZTE) provides r01 ==== Revisions Deadline ==== Fenqin (Huawei) We can only accept the r01+ cover page update. The cover page of this CR need be updated to align with 8615r01. alessio (Nokia) ok with r01 Jinguo(ZTE) asks for CC#2. ==== Comments Deadline ==== | Revised |
| 6.2 | S2-2109335 | CR | Approval | 23.502 CR3262R1 (Rel-16, 'F'): AMF re-allocation during inter PLMN mobility | ZTE | Rel-16 | Revision of S2-2108613r01. Approved | Agreed | |
| 6.2 | S2-2108614 | CR | Approval | 23.501 CR3402 (Rel-16, 'F'): AMF re-allocation in CM connected state | ZTE | Rel-16 | Noted | Alessio(Nokia) proposes to note the paper or to update it with the detail to ALWAYS include NSSAI in the RRC connection establishment MSG 5. Jinguo(ZTE) asks question Alessio(Nokia) comments Jinguo(ZTE) response ==== Revisions Deadline ==== Jinguo(ZTE) suggests to approve r01 Jinguo(ZTE) suggests to approve r00, the original version. There is no r01 Fenqin(Huawei)propose to Note this paper alessio(Nokia) proposes a way forward to approve the original document after removing in CC#2 'and/or new UE requested NSSAI received from UE in CM Connected state,' Jinguo(ZTE) agree with alessio(Nokia), lets check at CC#2 ==== Comments Deadline ==== Fenqin(Huawei) comments | Noted |
| 6.2 | S2-2108615 | CR | Approval | 23.502 CR3263 (Rel-17, 'F'): AMF re-allocation during inter PLMN mobility | ZTE | Rel-17 | r01 agreed. Revised to S2-2109336. | Fenqin (Huawei) comments Jinguo(ZTE) provides r01 ==== Revisions Deadline ==== alessio (Nokia) ok with r01 ==== Comments Deadline ==== | Revised |
| 6.2 | S2-2109336 | CR | Approval | 23.502 CR3263R1 (Rel-17, 'A'): AMF re-allocation during inter PLMN mobility | ZTE | Rel-17 | Revision of S2-2108615r01. Approved | Agreed | |
| 6.2 | S2-2108616 | CR | Approval | 23.501 CR3403 (Rel-17, 'F'): AMF re-allocation in CM connected state | ZTE | Rel-17 | Noted | Fenqin(Huawei)propose to Note this paper alessio(Nokia) proposes a way forward to approve the original document after removing in CC#2 'and/or new UE requested NSSAI received from UE in CM Connected state,' Jinguo(ZTE) agree with alessio(Nokia). Lets check it at CC#2. I can remove 'and/or new UE requested NSSAI received from UE in CM Connected state,' and update the cover page accordingly. ==== Comments Deadline ==== | Noted |
| 6.2 | S2-2108676 | CR | Approval | 23.502 CR3271 (Rel-17, 'F'): Inter PLMN handover procedure | Huawei, HiSilicon | Rel-17 | Noted | Qian (Ericsson) comments Fenqin (Huawei) responds Jinguo (ZTE) comments Qian (Ericsson) responds Alessio(Nokia) proposes to note this CR and handle this topic in rel-18 Fenqin (Huawei) I agree that this need some change at the existing specification. But this is R17 :) . ==== Revisions Deadline ==== Qian (Ericsson) propose to NOTE the paper and go with the decision in 8615 . ==== Comments Deadline ==== | Noted |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=5 | - | |
| 6.3 | S2-2108388 | DISCUSSION | Agreement | Service Request and PCF interaction. | Ericsson | Rel-16 | Postponed | Fenqin (Huawei) comments Judy (Ericsson) responds to Fenqin (Huawei) Fenqin (Huawei) responds Myungjune (LGE) provides comments. Judy (Ericsson) responds to Myungjune (LGE) and Fenqin (Huawei) Jinguo (ZTE) provides comments. Judy (Ericsson) responds to Jinguo (ZTE)'s that his comments are addressed in the paper as well as in previous responses. Fenqin (Huawei) comments. Judy (Ericsson) ask Fenqin (Huawei) for clarification Fenqin (Huawei) comments and propose to postpone this issue. Laurent (Nokia): we support Fenqin's request to postpone ==== Revisions Deadline ==== Judy (Ericsson) is OK to postpone to allow more time for discussion. ==== Comments Deadline ==== | Postponed |
| 6.3 | S2-2108389 | CR | Approval | 23.502 CR3230 (Rel-16, 'F'): Service Request and PCF interaction | Ericsson | Rel-16 | Postponed | Fenqin (Huawei) comments ==== Revisions Deadline ==== Laurent (Nokia): we support Fenqin's request to postpone ==== Comments Deadline ==== | Postponed |
| 6.3 | S2-2108390 | CR | Approval | 23.502 CR3231 (Rel-17, 'A'): Service Request and PCF interaction | Ericsson | Rel-17 | Postponed | Fenqin (Huawei) comments ==== Revisions Deadline ==== Laurent (Nokia): we support Fenqin's request to postpone ==== Comments Deadline ==== | Postponed |
| 6.3 | S2-2108512 | CR | Approval | 23.501 CR3382 (Rel-17, 'F'): Supplementation of L2TP tunnel applicable senario | China Mobile | Rel-17 | r03 agreed. Revised to S2-2109032. | Laurent (Nokia): provides r Laurent (Nokia): provides r01 Stefan (Ericsson) supports r01 Haris(Qualcomm) provides r02 Dan(China Mobile) is ok with r02 and provide r03 to clear the text. ==== Revisions Deadline ==== Laurent (Nokia): objects to R00 and R02, Dan (China Mobile): suggest to go with r03 ==== Comments Deadline ==== | Revised |
| 6.3 | S2-2109032 | CR | Approval | 23.501 CR3382R1 (Rel-17, 'F'): Supplementation of L2TP tunnel applicable senario | China Mobile | Rel-17 | Revision of S2-2108512r03. Approved | Agreed | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=0 | - | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=26 | - | |
| 6.6 | S2-2108269 | LS In | Action | LS from CT WG6: LS to SA2 on mandatory SSC modes supported by UE | CT WG6 (C6-210258) | Rel-15 | Revision of S2-2107035 from S2#147E. Responses drafted in S2-2108322, S2-2108368, S2-2108583 and S2-2108782. Final response in S2-2109345 | Replied to | |
| 6.6 | S2-2108322 | LS OUT | Approval | [DRAFT] LS Reply to CT WG6 on mandatory SSC modes supported by UE | T-Mobile USA Inc. | Rel-17 | Response to S2-2108269 To be Merged into S2-2109345 | Pallab (Nokia) suggests to move the LSOut discussion to a single email thread in S2-2108368. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 6.6 | S2-2108368 | LS OUT | Approval | [DRAFT] Reply LS on mandatory SSC modes supported by UE | Ericsson | Rel-15 | Response to S2-2108269. CC#2: r10 agreed. Revised to S2-2109345, merging S2-2108322, S2-2108583 and S2-2108782 | Hui (Huawei) asks for clarification. Pallab (Nokia) comments and suggests that we discuss the LS Response in this thread. Dan (China Mobile) provide consideration. Irfan (Cisco) provides comments. Irfan (Cisco) adds Dan's comment to this thread to keep discussion one thread Fei (OPPO) comments. Haris(Qualcomm) objects to this LS response since it is not supported by stage-3 text and would create UE impacts in frozen releases Haris (Qualcomm) provides comments. Guillaume (MediaTek Inc.) comments. Stefan (Ericsson) provides questions to Haris Haris(Qualcomm) comments Irfan (Cisco) provides response to Harris Haris(Qualcomm) replies Krisztian (Apple) supports Qualcomm's and Mediatek's view that currently all SSC modes are considered optional for the UE to support. We have no problem to make SSC mode 1 mandatory for all UEs. We can't accept making SSC modes 2 and 3 mandatory for the UE to support. Guillaume (MediaTek) adds further comments Irfan (Cisco) comments on SSC Mode 2 optional for UE Hui(Huawei) comments Haris(Qualcomm) comments and provides r01 Guillaume (MediaTek Inc.) replies to Pallab (Nokia). Magnus H (Ericsson) comments Saso (Intel) comments Stefan (Ericsson) comments Irfan (Cisco) comments and provides r02 Pallab (Nokia) responds to Irfan (Cisco) and requests for clarification Irfan (Cisco) responds to Pallab (Nokia) Magnus H (Ericsson) provides r03 Dan (China Mobile) object to any version which one without saying the SSC mode 1 should be mandatory supported by UE Haris(Qualcomm) provides r04 Serge (T-Mobile USA) supports r03 or r04 and comments Saso (Intel) replies to Magnus H (Ericsson) on N26 Magnus H (Ericsson) withdraws comment on N26 Magnus H (Ericsson) comment related to no N26 support. Dan (China Mobile) provide r05 Haris(Qualcomm) is ok but if we go with r05 we should also approve a CR to back up our assertions Pallab (Nokia) asks for clarification on r05. Irfan (Cisco) is also OK with r05 Pallab (Nokia) agrees with Fei (OPPO). Pallab (Nokia) provides r06 Guillaume (MediaTek Inc.) provides r07 ==== Revisions Deadline ==== Stefan (Ericsson) cannot agree r07. Uploaded r08 and r09 in DRAFTS folder. Another alternative is to postpone the LS. Irfan (Cisco) supports r08 Haris(Qualcomm) indicates that is ok with r08 and comments on suggestion from Irfan Guillaume (MediaTek Inc.): ok with r08 Fei (OPPO) ok with r09 or postpone the LS. Hui (Huawei) ok with r09 or postpone the LS. Haris(Qualcomm) objects to r09 Stefan (Ericsson) OK with r08, r09 or postponing the LS ==== Comments Deadline ==== Stefan (Ericsson) uploaded r08 to CC#2 folder | Revised |
| 6.6 | S2-2109345 | LS OUT | Approval | Reply LS on mandatory SSC modes supported by UE | SA WG2 | Rel-15 | Revision of S2-2108368r10, merging S2-2108322, S2-2108583 and S2-2108782. Approved | Approved | |
| 6.6 | S2-2108583 | LS OUT | Approval | [DRAFT] Reply LS to SA WG2 on mandatory SSC modes supported by UE | OPPO | Rel-15 | Response to S2-2108269 To be Merged into S2-2109345 | Pallab (Nokia) suggests to move the LSOut discussion to a single email thread in S2-2108368. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 6.6 | S2-2108782 | LS OUT | Approval | [DRAFT] Reply LS to SA WG2 on mandatory SSC modes supported by UE | Qualcomm | Rel-15 | Response to S2-2108269 To be Merged into S2-2109345 | Pallab (Nokia) suggests to move the LSOut discussion to a single email thread in S2-2108368. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 6.6 | S2-2108320 | DISCUSSION | Discussion | Mandatory SSC Modes. | T-Mobile USA | Rel-17 | Noted | Noted | |
| 6.6 | S2-2108890 | DISCUSSION | Discussion | Mandatory SSC Mode Support for UE. | Cisco Systems | Rel-16 | Noted | Noted | |
| 6.6 | S2-2108891 | CR | Approval | 23.501 CR3452 (Rel-16, 'F'): SSC Mode support by UE | Cisco Systems | Rel-16 | Noted | Josep (DT) asks a question for clarification. Irfan (Cisco) responds and provides r01 Haris (Qualcomm) objects to the CR (all revisions) Hui(Huawei) provides comments Krisztian (Apple) also objects this CR. We can't accept making SSC mode 2 mandatory for all UEs to support. Pallab (Nokia) provides r02. Stefan (Ericsson) comments and provides r03 Pallab (Nokia) comments on r03. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108892 | CR | Approval | 23.501 CR3453 (Rel-17, 'A'): SSC Mode support by UE | Cisco Systems | Rel-17 | Noted | Noted | |
| 6.6 | S2-2108629 | DISCUSSION | Agreement | SSC modes and optional functionalities in URSP. | Qualcomm Incorporated | Noted | Noted | ||
| 6.6 | S2-2108645 | CR | Approval | 23.501 CR3412 (Rel-15, 'F'): Support for SSC modes | Qualcomm Incorporated | Rel-15 | Postponed | Irfan (Cisco) corrects the tdoc number and provides r01 Haris(Qualcomm) cannot accept r01 since it creates ambiguity re the requirement for SSC mode 2 Pallab (Nokia) provides r02. Hui (Huawei) provides r03. Irfan (Cisco) provide r03 based on update to r01 Chris (Vodafone) prefers r03 to r0, but expects that further work is needed. Haris(Qualcomm) objects to r03 Magnus H (Ericsson) suggest further work needed Guillaume (MediaTek Inc.): ok with r03 ==== Revisions Deadline ==== Irfan (Cisco) uploads r04 to draft folder. Cisco is ok with r03 or r04 (in drafts folder) Haris(Qualcomm) comments on r04 Stefan (Ericsson) proposes to postpone the CR Haris(Qualcomm) comments and proposes a WF Hui (Huawei) fine with postpone the CR Fei (OPPO) is fine with r04 and r00 Stefan (Ericsson) comments on WF and uploaded LS revisions on the 8368 thread Hui (Huawei) asks to postpone the CR. ==== Comments Deadline ==== | Postponed |
| 6.6 | S2-2108772 | CR | Approval | 23.501 CR3425 (Rel-16, 'A'): Support for SSC modes | Qualcomm Incorporated | Rel-16 | Postponed | Postponed | |
| 6.6 | S2-2108780 | CR | Approval | 23.501 CR3426 (Rel-17, 'A'): Support for SSC modes | Qualcomm Incorporated | Rel-17 | Postponed | Postponed | |
| 6.6 | S2-2108554 | CR | Approval | 23.503 CR0676 (Rel-15, 'F'): Clarifications on SSC mode 3 | Samsung | Rel-15 | Noted | Belen (Ericsson) asks question for clarification Dongeun (Samsung) clarifies. Chia-Lin (MediaTek) considers this is not essential correction and Rel-15 has been frozen for a long time. The CR is not needed. Belen (Ericsson) is okay with the clarifications, ask a question. Dongeun (Samsung) provides r01 (also for and replies to Belen (Ericsson) and Chia-Lin (MediaTek) Chia-Lin (MediaTek) provides comments and still considers the CR is not needed Dongeun (Samsung) replies to Chia-Lin (MediaTek) ==== Revisions Deadline ==== Chia-Lin (MediaTek) suggest to note the CR ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108562 | CR | Approval | 23.503 CR0677 (Rel-16, 'A'): Clarifications on SSC mode 3 | Samsung | Rel-16 | Noted | Dongeun (Samsung) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108584 | CR | Approval | 23.503 CR0679 (Rel-17, 'A'): Clarifications on SSC mode 3 | Samsung | Rel-17 | Noted | Dongeun (Samsung) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108902 | CR | Approval | 23.502 CR3305 (Rel-16, 'F'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-16 | Noted | Susan (Huawei) provides comments and don't think this CR is needed. Dongeun (Samsung) comments. Belen (Ericsson) states that the CR is needed to cover the case of SMF relocation and same PCF. Susan (Huawei) replies and is not convinced why the changes in this CR are needed. Belen (Ericsson) responds to Samsung Dongeun (Samsung) comments again. Belen (Ericsson) replies to Samsung and Huawei ==== Revisions Deadline ==== Belen (Ericsson) aks if r00 is acceptable by Samsung and Huawei Dongeu (Samsung) suggests to postpone the CR. Susan (Huawei) replies to Belen (Ericsson) and asks questions for clarification. ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108903 | CR | Approval | 23.502 CR3306 (Rel-17, 'A'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-17 | Noted | Susan (Huawei) provides comments and don't think this CR is needed. Belen (Ericsson) states that the CR is needed to cover the case of SMF relocation and same PCF. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108913 | CR | Approval | 23.502 CR3308 (Rel-17, 'F'): SM policy association in SSC mode #3 | NTT DOCOMO | Rel-17 | Noted | Susan (Huawei) provides comments and don't think this CR is needed. Pallab (Nokia) requests for clarification. Belen (Ericsson) provides comments Riccardo (NTT DOCOMO) replies to Susan, provides revision 1 and clarifies the need for it. Riccardo (NTT DOCOMO) replies to Pallab. Riccardo (NTT DOCOMO) replies to Belen. Pallab (Nokia) replies to Riccardo (NTT DOCOMO) and asks for further clarification. Riccardo (NTT DOCOMO) replies to Pallab (Nokia). Susan (Huawei) replies to Riccardo. Pallab (Nokia) responds to Riccardo (NTT DOCOMO) and still not convinced that the CR is needed. Riccardo (NTT DOCOMO) replies to Susan. Riccardo (NTT DOCOMO) responds to Pallab (Nokia). Pallab (Nokia) responds to Riccardo (NTT DOCOMO) and proposes to NOTE the CR. Riccardo (NTT DOCOMO) asks clarifications to Pallab (Nokia) Pallab (Nokia) responds to Riccardo (NTT DOCOMO). Belen (Ericsson) replies to DOCOMO and also thinks the CR can be POSTPONE ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108914 | CR | Approval | 23.503 CR0690 (Rel-17, 'F'): SM policy association in SSC mode #3 | NTT DOCOMO | Rel-17 | Noted | Susan (Huawei) provides comments and don't think this CR is needed. Pallab (Nokia) has same comments as in 8913 Riccardo (NTT DOCOMO) replies to Susan and clarify the need for this CR. Riccardo (NTT DOCOMO) replied in the 8913 thread. Pallab (Nokia) proposes to NOTE the CR as commented in 8913 Riccardo (NTT DOCOMO) commented in 8913 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108736 | CR | Approval | 23.503 CR0685 (Rel-17, 'D'): Alignment of PCC input parameter documentation | Huawei, HiSilicon | Rel-17 | Approved | Agreed | |
| 6.6 | S2-2108649 | CR | Approval | 23.503 CR0683 (Rel-16, 'F'): Clarifications on Support for Application Functions supporting Rx interface | Samsung | Rel-16 | Approved | Agreed | |
| 6.6 | S2-2108663 | CR | Approval | 23.503 CR0684 (Rel-17, 'A'): Clarifications on Support for Application Functions supporting Rx interface | Samsung | Rel-17 | Approved | Agreed | |
| 6.6 | S2-2108420 | CR | Approval | 23.502 CR3234 (Rel-17, 'F'): BSF service update for session binding information update | China Mobile | Rel-17 | Noted | Pallab (Nokia) requests for clarification Dan (China Mobile) provide response Belen (Ericsson) asks questions for clarification Pallab (Nokia) responds to Dan (China Mobile) Dan (China Mobile) responds to Pallab and Belen Pallab (Nokia) responds to Dan (China Mobile) and questions the need for the CR Dan (China Mobile) reply Pallab (Nokia) requests for further clarification Dan (China Mobile) response Pallab (Nokia) comments and proposes to NOTE the CR Dan (China Mobile) response and suggest whether we can endorse this one Belen (Ericsson) proposes to NOTE or POSTPONE this CR Belen (Ericsson) replies to Dan ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.6 | S2-2108421 | CR | Approval | 23.503 CR0673 (Rel-17, 'F'): BSF service update for session binding information update | China Mobile | Rel-17 | Noted | Pallab (Nokia) has same comments as in 8420 Pallab (Nokia) proposes to NOTE the CR as commented in 8420 dan (China mobile) proposes whether we can endorse this one and see further update in next emeeting Belen (Ericsson) supports to NOTE or POSTPONE this CR, it cannot accept to endorse it ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=5 | - | |
| 6.7 | S2-2108375 | CR | Approval | 23.501 CR3367 (Rel-17, 'F'): NG-RAN location report clarification in RRC Inactive | Ericsson | Rel-17 | Approved | Agreed | |
| 6.7 | S2-2108376 | CR | Approval | 23.502 CR3229 (Rel-17, 'F'): NG-RAN location report clarification in RRC Inactive | Ericsson | Rel-17 | Approved | Agreed | |
| 6.7 | S2-2108377 | CR | Approval | 23.401 CR3669R1 (Rel-17, 'C'): ACL support for S1 HO with Indirect Data Forwarding | Ericsson, Deutsche Telekom | Rel-17 | Revision of (Noted) S2-2107770 from S2#147E. Noted | Fenqin (Huawei) suggest to postpone this paper. Laurent (Nokia): has concerns with the approach in this Tdoc Juan Zhang (Qualcomm) shares the same concern with Laurent (Nokia). Qian (Ericsson) provides comments and asks quesitons. Fenqin (Huawei) shares the same view as Juan and Laurent. ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc Fenqin (Huawei): Propose to note this paper Juan Zhang (Qualcomm) Proposes to note this paper ==== Comments Deadline ==== | Noted |
| 6.7 | S2-2108378 | CR | Approval | 23.502 CR3218R1 (Rel-17, 'C'): ACL support for NGAP HO with Indirect Data Forwarding | Ericsson, Deutsche Telekom | Rel-17 | Revision of (Noted) S2-2107771 from S2#147E. Noted | Fenqin (Huawei) suggest to postpone this paper. Laurent (Nokia): has concerns with the approach in this Tdoc Juan Zhang (Qualcomm) shares the same concern with Laurent (Nokia). Qian (Ericsson) provides comments and asks question. Fenqin (Huawei) share the same view as Laurent and Juan Juan Zhang (Qualcomm) replies to Qian (Ericsson) ==== Revisions Deadline ==== Laurent (Nokia): objects to any version of this Tdoc Fenqin (Huawei): Propose to note this paper Juan Zhang (Qualcomm) Proposes to note this paper ==== Comments Deadline ==== | Noted |
| 6.7 | S2-2109008 | LS In | Action | LS on indication of direct data forwarding availability | RAN WG3 (R3-216176) | Rel-16 | Postponed | Qian (Ericsson) proposes to Postpone the paper since no contribution submitted on this in the meeting ==== Comments Deadline ==== | Postponed |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=2 | - | |
| 6.8 | S2-2108869 | CR | Approval | 23.502 CR3301 (Rel-17, 'F'): TAU with active flag in case the entire PDU session is rejected | Qualcomm Incorporated | Rel-17 | r02 agreed. Revised to S2-2109033. | Hannu (Nokia) asks question to understand what is being proposed and suggests that a revision would be needed to clarify when the new text applies? Haris(Qualcomm) provides r01 Hannu (Nokia) replies to Haris and provides r02 ==== Revisions Deadline ==== Qian (Ericsson) prefer r01 Hannu (Nokia) can either agree r02 or postpone the CR. The previous revisions are not acceptable as they do not work. Qian (Ericsson) comments. Haris(Qualcomm) commments ==== Comments Deadline ==== Hannu (Nokia) thanks Haris for explanation. I still prefer r01 but based on your explanation I can now live with r02 which leads to the correct outcome even if the reader of the QoS flow rejection text fails to see the new text added in this CR. | Revised |
| 6.8 | S2-2109033 | CR | Approval | 23.502 CR3301R1 (Rel-17, 'F'): TAU with active flag in case the entire PDU session is rejected | Qualcomm Incorporated | Rel-17 | Revision of S2-2108869r02. Approved | Agreed | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=6 | - | |
| 6.9 | S2-2108303 | CR | Approval | 23.501 CR3355 (Rel-17, 'F'): Clarification on mobility from NG-RAN to GERAN/UTRAN | Nokia, Nokia Shanghai Bell | Rel-17 | Confirm CR Number - CR states 3335! Postponed | Qian (Ericsson) provides comments and express concerns. Alessio(Nokia) provides r01 Alessio(Nokia) hopes r01 clarified the questions by Ericsson Qian (Ericsson) provides further comments Qian (Ericsson) comments alessio (nokia) comments Qian (Ericsson) responds Alessio(Nokia) comments Qian (Ericsson) comments further Haris(Qualcomm) re 'providing UE service' asks if there are implications in T-ADS if we don't approve the CR Qian (Ericsson) responds to Haris (Qualcomm) Fenqin (Huawei) share the similar view as Qian alessio(nokia) asks a question alessio(Nokia) requests to escalate this to CC#2 if ericsson does not graciously agree that SR applies when the UE moves to 2/3G. ==== Revisions Deadline ==== Alessio (Nokia) proposes to mark this as postponed as clearly this is not approvable at this meeting. we will work offline with interested companies till SA2#149e ==== Comments Deadline ==== | Postponed |
| 6.9 | S2-2108624 | CR | Approval | 23.502 CR3265 (Rel-16, 'F'): EPS fallback for a UE moving from EPS to 5GS with a bearer for IMS voice . | Samsung | Rel-16 | Noted | Zhendong (ZTE): provides the comments Qian (Ericsson) asks questions Alessio(Nokia) agrees with ZTE we can note this CR as the scenario that underlies it is incorrect. Haris(Qualcomm) proposes to note the CR Myungjune (LGE) proposes to note the CR DongYeon (Samsung) replies to Zhendong (ZTE), Qian (Ericsson), Alessio (Nokia), Haris (Qualcomm), and Myungjune (LGE). Fenqin (Huawei) comments DongYeon (Samsung) replies to Fenqin (Huawei). Fenqin (Huawei) responds. Myungjune (LGE) comments DongYeon (Samsung) provides r01, and r02 as way forward. Myungjune (LGE) comments on r01/r02 DongYeon (Samsung) provides r03 above r01, and replies to Myungjune (LGE). Myungjune (LGE) proposes to note this CR ==== Revisions Deadline ==== DongYeon (Samsung) asks if we can agree Rel-17 CR(S2-2108625r01) with updated as same as S2-2108624r03, and provides S2-2108625r01. Qian (Ericsson) supports to NOTE the paper. DongYeon (Samsung) proposes to postpone this CR. ==== Comments Deadline ==== | Noted |
| 6.9 | S2-2108625 | CR | Approval | 23.502 CR3266 (Rel-17, 'A'): EPS fallback for a UE moving from EPS to 5GS with a bearer for IMS voice . | Samsung | Rel-17 | Noted | DongYeon (Samsung) asks if we can agree Rel-17 CR(S2-2108625r01) with updated as same as S2-2108624r03, and provides S2-2108625r01. Myungjune (LGE) comments Qian (LGE) comments and suggests to NOTE the paper. Qian (Ericsson) comments and suggests to NOTE the paper. Qian also indicates the source should be 'Ericsson' in previous comment (instead of LGE). DongYeon (Samsung) asks if we can agree r01 with update the if not approved field as: Voice calls served by the EPS fallback can be dropped when the UE goes into idle mode and the UE comes back to 5GS. DongYeon (Samsung) asks if we can agree r01 with update the if not approved field as: Voice calls served by the EPS fallback can be dropped when the UE goes into idle mode and the UE comes back to 5GS and, revise the note as: The E-UTRAN can be configured to set a longer timer for the UE with a dedicated bearer for IMS voice, so that the UE does not become RRC_IDLE. DongYeon (Samsung) comments. Myungjune (LGE) propose to Note this CR Qian (Ericsson) provides comments. ==== Comments Deadline ==== | Noted |
| 6.9 | S2-2108631 | DISCUSSION | Agreement | Discussion on EPS fallback for a UE moving from EPS to 5GS with a bearer for IMS voice. | Samsung | Noted | Alessio(Nokia) proposes to note this paper with a remark the described scenario seems unclear and actually not something Nokia believes can happen and deserve handling. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 6.9 | S2-2108677 | CR | Approval | 23.502 CR3272 (Rel-17, 'F'): Tunnel info release for inter system mobility with N26 | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109034. | Qian (Ericsson) provides comments Fenqin (Huawei) responds Qian (Ericsson) provides further comments alessio(Nokia) requests to note this CR and all is revisions Fenqin (Huawei) responds and provides r01 Alessio(nokia) thinks r01 also is not agreeable. Fenqin (Huawei) responds and provides r02 ==== Revisions Deadline ==== Fenqin (Huawei) suggest to go with r02 Qian (Ericsson) is ok with r02 ==== Comments Deadline ==== | Revised |
| 6.9 | S2-2109034 | CR | Approval | 23.502 CR3272R1 (Rel-17, 'F'): Tunnel info release for inter system mobility with N26 | Huawei, HiSilicon | Rel-17 | Revision of S2-2108677r02. Approved | Agreed | |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=15 | - | |
| 6.10 | S2-2108728 | CR | Approval | 23.501 CR3419 (Rel-16, 'F'): R16 23.501 Clarification on security mechanism applied for non-3GPP access | Huawei, HiSilicon | Rel-16 | Noted | Stefano (Qualcomm) suggests noting this paper since it is not FASMO ==== Revisions Deadline ==== Laurent (Nokia): we support stefano (non FASMO) and object to any version of this tdoc ==== Comments Deadline ==== | Noted |
| 6.10 | S2-2108729 | CR | Approval | 23.501 CR3420 (Rel-17, 'A'): R17 23.501 Clarification on security mechanism applied for non-3GPP access | Huawei, HiSilicon | Rel-17 | Noted | Stefano (Qualcomm) suggests noting this paper since it is not FASMO ==== Revisions Deadline ==== Laurent (Nokia): we support Stefano (non FASMO) and object to any version of this tdoc ==== Comments Deadline ==== | Noted |
| 6.10 | S2-2108733 | CR | Approval | 23.502 CR3282 (Rel-17, 'A'): Correction on handover procedure and non-3GPP access | Huawei, HiSilicon | Rel-17 | Noted | Laurent (Nokia): Suggests to merge this typos correction in 8927 that updates the same clauses Marco (Huawei): we prefer to keep separate since the scope is different even if they modify the same clause and the change are not overallaping ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.10 | S2-2108734 | CR | Approval | 23.502 CR3283 (Rel-16, 'F'): Correction on handover procedure and non-3GPP access | Huawei, HiSilicon | Rel-16 | Noted | Laurent (Nokia): Suggests to merge this typo corrections in 8927 that updates the same clauses Apostolis (Lenovo) comments that this CR corrects editorial errors and could be merged into 8926. Hualin (Huawei) disagree to merge and question why changes in the same clause should be merged? ==== Revisions Deadline ==== Laurent (Nokia): objects to this Typo correction in a frozen release (I suggested to merge...) Hualin(Huawei) question why Typo correction can' be correct. ==== Comments Deadline ==== | Noted |
| 6.10 | S2-2108860 | CR | Approval | 23.501 CR3441 (Rel-16, 'F'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-16 | r01 agreed. Revised to S2-2109035. | Marco (Huawei) comments and provides r01 Fenqin (Huawei) provides r01 with an attempt to merge suggestion from 8977r01 Thomas (Nokia) comments that new version is incomplete and split into two versions not possible suggest to focus the discussion in the 8977 thread Laurent (Nokia): warns for a thread mismatch ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.10 | S2-2109035 | CR | Approval | 23.501 CR3441R1 (Rel-16, 'F'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-16 | Revision of S2-2108860r01. Approved | Agreed | |
| 6.10 | S2-2108861 | CR | Approval | 23.501 CR3442 (Rel-17, 'A'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-17 | r00 agreed. Revised to S2-2109036. | Revised | |
| 6.10 | S2-2109036 | CR | Approval | 23.501 CR3442R1 (Rel-17, 'A'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-17 | Revision of S2-2108861r00. Approved | Agreed | |
| 6.10 | S2-2108862 | CR | Approval | 23.502 CR3298 (Rel-16, 'F'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-16 | r01 agreed. Revised to S2-2109037. | Stefan (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.10 | S2-2109037 | CR | Approval | 23.502 CR3298R1 (Rel-16, 'F'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-16 | Revision of S2-2108862r01. Approved | Agreed | |
| 6.10 | S2-2108863 | CR | Approval | 23.502 CR3299 (Rel-17, 'A'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-17 | r00 agreed. Revised to S2-2109038. | Revised | |
| 6.10 | S2-2109038 | CR | Approval | 23.502 CR3299R1 (Rel-17, 'A'): Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, | Rel-17 | Revision of S2-2108863r00. Approved | Agreed | |
| 6.10 | S2-2108925 | DISCUSSION | Discussion | Corrections to to procedures for Handover of a PDU Session between 3GPP and untrusted non-3GPP access. | Nokia, Nokia Shanghai Bell | Noted | Noted | ||
| 6.10 | S2-2108926 | CR | Approval | 23.502 CR3310 (Rel-16, 'F'): Corrections to procedures for Handover of a PDU Session between 3GPP and untrusted non-3GPP access | Nokia, Nokia Shanghai Bell | Rel-16 | Approved | Agreed | |
| 6.10 | S2-2108927 | CR | Approval | 23.502 CR3311 (Rel-17, 'A'): Corrections to Handover of a PDU Session procedure between 3GPP and untrusted non-3GPP access | Nokia, Nokia Shanghai Bell | Rel-17 | Confirm CR Number - CR states 3310! Approved | Laurent (Nokia): provides r01 Apostolis (Lenovo) notes that is a mirror to 8926 but it has a different title than 8926. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=4 | - | |
| 6.11 | S2-2108316 | CR | Approval | 23.502 CR3221 (Rel-15, 'F'): Missing UDM service operations | Nokia, Nokia Shanghai Bell | Rel-15 | Noted | Fenqin (Huawei) Propose to note this paper. Pallab (Nokia) responds to Fenqin (Huawei) Pallab (Nokia) OK to NOTE the CR. The corresponding mirror from R17 will be changed to Cat F ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.11 | S2-2108317 | CR | Approval | 23.502 CR3222 (Rel-16, 'A'): Missing UDM service operations (Mirror) | Nokia, Nokia Shanghai Bell | Rel-16 | Noted | Fenqin (Huawei) Propose to note this paper. Pallab (Nokia) OK to NOTE the CR. The corresponding mirror from R17 will be changed to Cat F ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 6.11 | S2-2108318 | CR | Approval | 23.502 CR3223 (Rel-17, 'A'): Missing UDM service operations (Mirror) | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2109039. | Fenqin (Huawei) Propose to update this paper. Pallab (Nokia) provides r01 with cover page changes only. CR category changed from A to F as related R15/16 CRs are not agreed. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 6.11 | S2-2109039 | CR | Approval | 23.502 CR3223R1 (Rel-17, 'F'): Missing UDM service operations | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108318r01. 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:=8 | - | |
| 7.1 | S2-2108340 | CR | Approval | 23.287 CR0170 (Rel-17, 'F'): V2X Policy provisioning request | Ericsson | Rel-17 | Noted | LaeYoung (LGE) proposes to discuss this issue first under AI#8.8 with the related tdocs to derive agreement/outcome. Belen (Ericsson) agrees with LGE proposal ==== Revisions Deadline ==== LaeYoung (LGE) proposes to NOTE this CR at this stage. If some updates are deemed necessary, let's do it in the next meeting. Belen (Ericsson) replies to LGE that if no conclusion is reached on this topic all related CRs should be noted. LaeYoung (LGE) responds to Belen (Ericsson). LaeYoung (LGE) replies to Belen (Ericsson). Leo (Deutsche Telekom) agrees to to NOTE this CR at this stage. When necessary, it can be done in the next meeting ==== Comments Deadline ==== | Noted |
| 7.1 | S2-2108581 | CR | Approval | 23.287 CR0174 (Rel-17, 'F'): UE Policy Container with V2X Policy Provisioning Request | OPPO | Rel-17 | Noted | LaeYoung (LGE) proposes to discuss this issue first under AI#8.8 with the related tdocs to derive agreement/outcome. Fei (OPPO) is fine to discuss this issue in AI#8.8 first. Steve (Huawei) comments on relationship with discussion in S2-2108284. LaeYoung (LGE) answers to Steve (Huawei). ==== Revisions Deadline ==== LaeYoung (LGE) proposes to NOTE this CR at this stage. If some updates are deemed necessary, let's do it in the next meeting. Leo (Deutsche Telekom) agrees to to NOTE this CR at this stage. When necessary, let's do it in the next meeting. ==== Comments Deadline ==== | Noted |
| 7.1 | S2-2108415 | CR | Approval | 23.502 CR3233 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | r02 agreed. Revised to S2-2109040. | Steve (Huawei) asks questions LaeYoung (LGE) provides r01. Judy (Ericsson) provides r02 based on r00+'may' and responds to LaeYoung (LGE) and Steve (Huawei) ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r02. Steve (Huawei) is ok with r02. ==== Comments Deadline ==== | Revised |
| 7.1 | S2-2109040 | CR | Approval | 23.502 CR3233R1 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | Revision of S2-2108415r02. Approved | Agreed | |
| 7.1 | S2-2108673 | CR | Approval | 23.287 CR0175 (Rel-17, 'F'): Correction to UE triggered Policy provisioning Procedure for V2X | Huawei, HiSilicon | Rel-17 | Covered by S2-2108392 | LaeYoung (LGE) proposes to merge this CR into S2-2108392 (Ericsson). Judy (Ericsson) support LaeYoung (LGE)'s proposal and comment this is a mirror CR LiMeng (Huawei) agrees with the merging proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.1 | S2-2108674 | CR | Approval | 23.287 CR0176 (Rel-16, 'F'): Correction to UE triggered Policy provisioning Procedure for V2X | Huawei, HiSilicon | Rel-16 | Covered by S2-2108391 | LaeYoung (LGE) proposes to merge this CR into S2-2108391 (Ericsson). Judy (Ericsson) support LaeYoung (LGE)'s proposal to merge this paper to 8391 and comments LiMeng (Huawei) is fine with the merging proposal. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.1 | S2-2108391 | CR | Approval | 23.287 CR0171 (Rel-16, 'F'): Correction to UE triggered Policy provisioning Procedure | Ericsson | Rel-16 | Approved | Agreed | |
| 7.1 | S2-2108392 | CR | Approval | 23.287 CR0172 (Rel-17, 'A'): Correction to UE triggered Policy provisioning Procedure | Ericsson | Rel-17 | Approved | Agreed | |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=14 | - | |
| 7.2 | S2-2108290 | LS In | Information | LS from BBF: Reply to your liaison S2-2106577 | BBF (LIAISE-474) | Response drafted in S2-2108362. Final response in S2-2109041 | Replied to | ||
| 7.2 | S2-2108362 | LS OUT | Approval | [DRAFT] Reply LS on MTU and other topics | Ericsson | Rel-17 | Response to S2-2108290. r00 agreed. Revised to S2-2109041. | Revised | |
| 7.2 | S2-2109041 | LS OUT | Approval | Reply LS on MTU and other topics | SA WG2 | Rel-17 | Revision of S2-2108362r00. Approved | Approved | |
| 7.2 | S2-2108361 | CR | Approval | 23.316 CR2061 (Rel-17, 'F'): MTU value for wireline access | Ericsson | Rel-17 | r01 agreed. Revised to S2-2109042. | Laurent (Nokia): provides r01 Stefan (Ericsson) is OK with r01 Marco (Huawei) provides r02 ==== Revisions Deadline ==== Laurent (Nokia): I MUCH prefer r01 and have issues with r02 and r00 that are too limitative Stefan (Ericsson) suggest to agree r01 Marco (Huawei) I prefer r02 but I can survive to r01 ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2109042 | CR | Approval | 23.316 CR2061R1 (Rel-17, 'F'): MTU value for wireline access | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108361r01. Approved | Agreed | |
| 7.2 | S2-2108299 | LS in | Information | LS from BBF: EAP-5G changes | BBF (LIAISE-477) | Response drafted in S2-2108363. Final response in S2-2109043 | Replied to | ||
| 7.2 | S2-2108363 | LS OUT | Approval | [DRAFT] Reply LS on EAP-5G changes | Ericsson | Rel-17 | Response to S2-2108299. r00 agreed. Revised to S2-2109043. | Marco (Huawei) provides comments and r01 Apostolis (Lenovo) asks questions on r01 Marco (Huawei) answers to Apostolis (Lenovo) Stefan (Ericsson) comments Marco answers to Stefan (Ericsson) and Apostolis (Lenovo) Stefan (Ericsson) provides r02, but prefers r00 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2109043 | LS OUT | Approval | Reply LS on EAP-5G changes | SA WG2 | Rel-17 | Revision of S2-2108363r00. Approved | Approved | |
| 7.2 | S2-2108833 | CR | Approval | 23.502 CR3294 (Rel-16, 'F'): Providing UE's address to AMF during registration via trusted Non-3GPP access | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom | Rel-16 | r01 agreed. Revised to S2-2109044. | Marco (Huawei) asks clarification Apostolis (Lenovo) responds to Marco (Huawei). Stefan (Ericsson) provides r01 Apostolis (Lenovo) is fine with r01 Marco (Huawei) comments further Apostolis (Lenovo) is fine with r01 Errata Corrige last comment: Marco (Huawei) comments further Apostolis (Lenovo) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2109044 | CR | Approval | 23.502 CR3294R1 (Rel-16, 'F'): Providing UE's address to AMF during registration via trusted Non-3GPP access | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, Ericsson | Rel-16 | Revision of S2-2108833r01. Approved | Agreed | |
| 7.2 | S2-2108848 | CR | Approval | 23.502 CR3295 (Rel-17, 'A'): Providing UE's address to AMF during registration via trusted Non-3GPP access | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom | Rel-17 | r00 agreed. Revised to S2-2109045. | Apostolis (Lenovo) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2109045 | CR | Approval | 23.502 CR3295R1 (Rel-17, 'A'): Providing UE's address to AMF during registration via trusted Non-3GPP access | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, Ericsson | Rel-17 | Revision of S2-2108848r00. Approved | Agreed | |
| 7.2 | S2-2108929 | CR | Approval | 23.316 CR2062 (Rel-17, 'F'): Applicability of ATSSS to 5G-RG in Rel-17 | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109046. | Apostolis (Lenovo) asks for clarification. Marco (Huawei) answers to Apostolis (Lenovo) Stefan (Ericsson) provides comments Marco (Huawei) answers to Stefan (Ericsson) Stefan (Ericsson) replies to Marco and provides r01 Marco (Huawei) replies to Stefan (Ericsson) Apostolis (Lenovo) asks questions. Marco (Huawei) answers to Apostolis (Lenovo). Apostolis (Lenovo) asks question for clarification. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.2 | S2-2109046 | CR | Approval | 23.316 CR2062R1 (Rel-17, 'F'): Applicability of ATSSS to 5G-RG in Rel-17 | Huawei, HiSilicon | Rel-17 | Revision of S2-2108929r01. Approved | Agreed | |
| 7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | Docs:=2 | - | |
| 7.3 | S2-2108732 | CR | Approval | 23.501 CR3423 (Rel-16, 'F'): Correction on PMF protocol stack for non-3GPP access | Huawei, HiSilicon | Rel-16 | r01 agreed. Revised to S2-2109047. | Dario S. Tonesi (Qualcomm) asks if this is a FASMO CR and why? Hualin(Huawei) replied to Dario S. Tonesi (Qualcomm). Dario (Qualcomm) asks about mirror Rel-17 CR agreed in October currently marked as Cat. F Marco (Huawei) answer to Dario (Qualcomm) Dario (Qualcomm) replies to Marco. Marco (Huawei) agreed to approve this R16 and to proposed a revision of last meeting approved R17 to align and to make CR 'A' directly to SA plenary as company contribution ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.3 | S2-2109047 | CR | Approval | 23.501 CR3423R1 (Rel-16, 'F'): Correction on PMF protocol stack for non-3GPP access | Huawei, HiSilicon | Rel-16 | Revision of S2-2108732r01. Approved | Agreed | |
| 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:=4 | - | |
| 7.5 | S2-2108531 | CR | Approval | 23.288 CR0473 (Rel-16, 'F'): Add the description of Wrong destination address | Huawei, HiSilicon | Rel-16 | r04 agreed. Revised to S2-2109048. | Zhang (Ericsson) ask for clarification Wang Yuan (Huawei) replies to Zhang(Ericsson). Zhang (Ericsson) ask further clarification Yannick (Nokia): Nokia provides comments. Wang Yuan (Huawei) replies to Zhang(Ericsson)/Yannick(Nokia) and provides r01. Yannick (Nokia): Nokia questions the change in r01. Wang Yuan (Huawei) replies to Zhang(Ericsson) and Yannick (Nokia), and provides r02. Zhang (Ericsson) provides comments Wang Yuan (Huawei) replies to Zhang(Ericsson), and provides r04. Zhang (Ericsson) is OK with r04 Yannick (Nokia): Nokia is ok with r04 but also understands that the use case of wrong destination address detection is not fully specified in TS 23.288. ==== Revisions Deadline ==== Wang Yuan (Huawei) replies to Zhang(Ericsson)/Yannick(Nokia). ==== Comments Deadline ==== | Revised |
| 7.5 | S2-2109048 | CR | Approval | 23.288 CR0473R1 (Rel-16, 'F'): Add the description of Wrong destination address | Huawei, HiSilicon | Rel-16 | Revision of S2-2108531r04. Approved | Agreed | |
| 7.5 | S2-2108532 | CR | Approval | 23.288 CR0474 (Rel-17, 'A'): Add the description of Wrong destination address | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2109049. | Wang Yuan (Huawei) provides r01 (the mirror CR) based on S2-2108531r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.5 | S2-2109049 | CR | Approval | 23.288 CR0474R1 (Rel-17, 'A'): Add the description of Wrong destination address | Huawei, HiSilicon | Rel-17 | Revision of S2-2108532r00. Approved | Agreed | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=26 | - | |
| 7.6 | S2-2108354 | CR | Approval | 23.273 CR0193R2 (Rel-16, 'F'): Clarification on use of service type and service identity in MO-LR procedure | Ericsson | Rel-16 | Revision of (Endorsed) S2-2107864 from S2#147E. r01 agreed. Revised to S2-2109050. | Yunjing (CATT) provides r01. Cai Simon (Nokia) provides comments Runze (Huawei) supports Simon(Nokia)'s View Åke (Ericsson) provides clarification to Simon and Runze ==== Revisions Deadline ==== Cai Simon (Nokia) provides further comments Stephen (Qualcomm) prefers the r01 and comments on Service Type vs Service Identity Åke (Ericsson) Also prefers r01 Runze(Huawei)thanks Ake for the clarification, and supports r01. Åke (Ericsson) supports r01 ==== Comments Deadline ==== Cai Simon (Nokia) prefers to note the CR | Revised |
| 7.6 | S2-2109050 | CR | Approval | 23.273 CR0193R3 (Rel-16, 'F'): Clarification on use of service type and service identity in MO-LR procedure | Ericsson | Rel-16 | Revision of S2-2108354r01. Approved | Agreed | |
| 7.6 | S2-2108355 | CR | Approval | 23.273 CR0194R1 (Rel-17, 'A'): Clarification on use of service type and service identity in MO-LR procedure | Ericsson | Rel-17 | Revision of (Postponed) S2-2107125 from S2#147E. r00 agreed. Revised to S2-2109051. | Revised | |
| 7.6 | S2-2109051 | CR | Approval | 23.273 CR0194R2 (Rel-17, 'A'): Clarification on use of service type and service identity in MO-LR procedure | Ericsson | Rel-17 | Revision of S2-2108355r00. Approved | Agreed | |
| 7.6 | S2-2108837 | CR | Approval | 23.273 CR0214 (Rel-16, 'F'): Update MO-LR procedure | Huawei, HiSilicon | Rel-16 | r04 agreed. Revised to S2-2109052. | Åke (Ericsson) Comments CR is not needed. Runze (Huawei) replies to Ake (Ericsson) and provides r01 Åke (Ericsson) Comments CR still not needed and r02 incorrect Runze (Huawei) replies to Ake, and provides r03. Åke (Ericsson) acknowledge need of clarification and provides r04 ==== Revisions Deadline ==== Runze (Huawei) supports r04 ==== Comments Deadline ==== | Revised |
| 7.6 | S2-2109052 | CR | Approval | 23.273 CR0214R1 (Rel-16, 'F'): Update MO-LR procedure | Huawei, HiSilicon | Rel-16 | Revision of S2-2108837r04. Approved | Agreed | |
| 7.6 | S2-2108838 | CR | Approval | 23.273 CR0215 (Rel-17, 'A'): Update MO-LR procedure | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2109053. | Revised | |
| 7.6 | S2-2109053 | CR | Approval | 23.273 CR0215R1 (Rel-17, 'A'): Update MO-LR procedure | Huawei, HiSilicon | Rel-17 | Revision of S2-2108838r00. Approved | Agreed | |
| 7.6 | S2-2108356 | CR | Approval | 23.273 CR0203 (Rel-16, 'F'): Remove SUPI in response to Nudm_SDM | Ericsson | Rel-16 | Approved | Agreed | |
| 7.6 | S2-2108357 | CR | Approval | 23.273 CR0204 (Rel-17, 'A'): Remove SUPI in response to Nudm_SDM | Ericsson | Rel-17 | Approved | Agreed | |
| 7.6 | S2-2108751 | CR | Approval | 23.273 CR0207 (Rel-16, 'F'): Correct the allowed access type for event report | CATT | Rel-16 | Approved | Agreed | |
| 7.6 | S2-2108752 | CR | Approval | 23.273 CR0208 (Rel-17, 'A'): Correct the allowed access type for event report | CATT | Rel-17 | Approved | Agreed | |
| 7.6 | S2-2108754 | CR | Approval | 23.273 CR0210 (Rel-16, 'F'): Update the location service operations to add service identity and service type | CATT | Rel-16 | Confirm Specification Number - CR states 23.502!. Confirm Spec version used - CR states 16.10.0! r01 agreed. Revised to S2-2109054. | Åke (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.6 | S2-2109054 | CR | Approval | 23.502 CR3315 (Rel-16, 'F'): Update the location service operations to add service identity and service type | CATT, Ericsson | Rel-16 | Revision of S2-2108754r01. Approved | Agreed | |
| 7.6 | S2-2108755 | CR | Approval | 23.273 CR0211 (Rel-17, 'A'): Update the location service operations to add service identity and service type | CATT | Rel-17 | Confirm Specification Number - CR states 23.502! Revised to S2-2109055. | Revised | |
| 7.6 | S2-2109055 | CR | Approval | 23.502 CR3316 (Rel-17, 'A'): Update the location service operations to add service identity and service type | CATT | Rel-17 | Revision of S2-2108755. Approved | Agreed | |
| 7.6 | S2-2108835 | CR | Approval | 23.273 CR0212 (Rel-16, 'F'): Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event | Huawei, HiSilicon | Rel-16 | r01 agreed. Revised to S2-2109056. | Stephen (Qualcomm) provides comments and an r01 Åke (Ericsson) Support r01 provided by Qualcomm Stephen (Qualcomm) provide a correction for AI#7.6 Runze (Huawei) supports R01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.6 | S2-2109056 | CR | Approval | 23.273 CR0212R1 (Rel-16, 'F'): Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event | Huawei, HiSilicon | Rel-16 | Revision of S2-2108835r01. Approved | Agreed | |
| 7.6 | S2-2108836 | CR | Approval | 23.273 CR0213 (Rel-17, 'A'): Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event | Huawei, HiSilicon | Rel-17 | WI Code should be 5G_eLCS for mirror CR. r00 agreed. Revised to S2-2109057. | Revised | |
| 7.6 | S2-2109057 | CR | Approval | 23.273 CR0213R1 (Rel-17, 'A'): Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event | Huawei, HiSilicon | Rel-17 | Revision of S2-2108836r00. Approved | Agreed | |
| 7.6 | S2-2108839 | CR | Approval | 23.273 CR0216 (Rel-16, 'F'): Clarification on support of SNPN for R16 LCS | Huawei, HiSilicon | Rel-16 | CC#2: Noted | Yunjing (CATT) provides comments. Josep (DT) comments. Walter Dees (Philips) requests clarification Yunjing (CATT) replies to Walter Dees (Philips). Stephen (Qualcomm) provides comments Josep (DT) objects to this CR. Runze (Huawei) replies to Josep. ==== Revisions Deadline ==== Josep (DT) replies that there is no problem to solve for R16. Cai Simon (Nokia) agrees with Stephen (Qualcomm) for precise R17 only statement Runze (Huawei) proposes a revision, and the content aligns with the R17 CR 2108753r05 Yunjing (CATT) is fine with r01. ==== Comments Deadline ==== | Noted |
| 7.6 | S2-2108840 | CR | Approval | 23.273 CR0217 (Rel-17, 'A'): Clarification on support of SNPN for R16 LCS | Huawei, HiSilicon | Rel-17 | CC#2: Noted | Josep (DT) objects to this (mirror) CR. ==== Revisions Deadline ==== Runze (Huawei) proposes to merge this CR into S2-2108357. Yunjing (CATT) is fine to merge this CR into S2-2108753. ==== Comments Deadline ==== | Noted |
| 7.6 | S2-2108843 | CR | Approval | 23.273 CR0219 (Rel-16, 'F'): Removal of description that LMF ID is provided by UE | Huawei, HiSilicon | Rel-16 | r02 agreed. Revised to S2-2109058. | Åke (Ericsson) Suggest CR not needed Runze (Huawei) replies to Ake. Stephen (Qualcomm) provides comments Runze (Huawei) provides r01 Stephen (Qualcomm) can agree the r01 Åke (Ericsson) Provide r02 with editorial improvements Runze (Huawei) agrees with R02 ==== Revisions Deadline ==== Stephen (Qualcomm) can agree the r02 ==== Comments Deadline ==== | Revised |
| 7.6 | S2-2109058 | CR | Approval | 23.273 CR0219R1 (Rel-16, 'F'): Removal of description that LMF ID is provided by UE | Huawei, HiSilicon | Rel-16 | Revision of S2-2108843r02. Approved | Agreed | |
| 7.6 | S2-2108844 | CR | Approval | 23.273 CR0220 (Rel-17, 'A'): Removal of description that LMF ID is provided by UE | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2109059. | Revised | |
| 7.6 | S2-2109059 | CR | Approval | 23.273 CR0220R1 (Rel-17, 'A'): Removal of description that LMF ID is provided by UE | Huawei, HiSilicon | Rel-17 | Revision of S2-2108844r00. Approved | Agreed | |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=31 | - | |
| 7.7 | S2-2108307 | CR | Approval | 23.501 CR3356 (Rel-16, 'F'): Deletion of selected enrties in UMIC/PMIC data structures | Intel, NTT DOCOMO | Rel-16 | r03 agreed. Revised to S2-2109060. | Devaki (Nokia) comments and wonders if this CR is really FASMO for Rel-16? Saso (Intel) replies to Devaki (Nokia); provides r01. Sang-Jun (Samsung) asks for clarification whether S2-2107615 in reason for change is also applied to Rel-16. Saso (Intel) replies to Sang-Jun (Samsung). Sebastian (Qualcomm) comments Saso (Intel) provides r02. Zhendong (ZTE): ask qusetion for clarification Saso (Intel) replie to Zhendong (ZTE); provides r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109060 | CR | Approval | 23.501 CR3356R1 (Rel-16, 'F'): Deletion of selected enrties in UMIC/PMIC data structures | Intel, NTT DOCOMO | Rel-16 | Revision of S2-2108307r03. Approved | Agreed | |
| 7.7 | S2-2108319 | CR | Approval | 23.501 CR3360 (Rel-16, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO | Rel-16 | Noted | Chunshan (Tencent) provides comments. Devaki (Nokia) objects as this CR is NOT a FASMO CR, also proposal seems unnecessary. Jari (NTT DOCOMO responds. Jari (NTT DOCOMO) responds and disagrees with Devaki Devaki (Nokia) replies. Jari (NTT DOCOMO) responds to Devaki. Chunshan (Tencent) responses to Jari (NTT DOCOMO) and comments that the proposed solution cannot work. Chunshan (Tencent) response to Jari (NTT DOCOMO) Jari (NTT DOCOMO) responds to Chunshan Chunshan (Tencent) asks Jari (NTT DOCOMO) to check further. Sebastian (Qualcomm) comments Chunshan (Tencent) responses to Sebastian (Qualcomm) comments. Sebastian (Qualcomm) replies to Tencent Chunshan (Tencent) responses to Sebastian (Qualcomm) . Sebastian (Qualcomm) replies to Chunshan Jari (NTT DOCOMO) replies to Chunshan Chunshan (Tencent) responses to Jari (NTT DOCOMO) . Shabnam (Ericsson) supports position explained by Qualcomm and DoCoMo delegates in this discussion. Zhendong (ZTE): provides comments Jari (NTT DOCOMO) replies to Zhendong ==== Revisions Deadline ==== Chunshan (Tencent) objects this CR and all revisions. Jari (NTT DOCOMO) seeks clarification from Chunshan Chunshan (Tencent) responses to Jari (NTT DOCOMO). Jari (NTT DOCOMO) proposes to discuss this in CC#2, responds to Chunshan Jari (NTT DOCOMO )responds to Chunshan Chunshan (Tencent) responses inline to Jari (NTT DOCOMO) . Jari (NTT DOCOMO) responds to Chunshan. ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2108695 | CR | Approval | 23.501 CR3414 (Rel-17, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO | Rel-17 | Noted | Chunshan (Tencent) provides the same comments on the S2-2108319, let us discuss the same issues in S2-2108319. Shabnam (Ericsson) provides r01, to add 'For TSN' in the newly added text. Jari (NTT DOCOMO) comments Jari (NTT DOCOMO) provides r02 ==== Revisions Deadline ==== Chunshan (Tencent) objects this CR and all revisions. ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2108321 | CR | Approval | 23.502 CR3224 (Rel-16, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO | Rel-16 | Noted | Chunshan (Tencent) provides the same comments on the S2-2108319, let us discuss the same issues in S2-2108319. Devaki (Nokia) objects as this CR is NOT a FASMO CR, also proposal seems unnecessary. Same reason as for 8319 Shabnam (Ericsson) thinks it is useful clarification to have, specially seeing the discussion in parallel for 23.501 CR, which shows there is potential for error. Shabnam (Ericsson) provides r01, correcting TSN working domain to TSN time domain in one place and cosigning. ==== Revisions Deadline ==== Chunshan (Tencent) objects this CR and all revisions. ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2108323 | CR | Approval | 23.502 CR3225 (Rel-17, 'A'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO | Rel-17 | Noted | Devaki (Nokia) objects as this CR is NOT a FASMO CR, also proposal seems unnecessary also for Rel-17 in our view. Same reason as for 8319/21. Jari (NTT DOCOMO) disagrees with Devaki, the same reason as for 8319/21. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 7.7 | S2-2108459 | CR | Approval | 23.502 CR3241 (Rel-16, 'F'): RID Update for SNPN UEs | Ericsson | Rel-16 | r02 agreed. Revised to S2-2109061. | Devaki (Nokia) provides r01, supportive of the proposal. Fei (OPPO) provides r02. Peter Hedman (Ericsson) provides comment ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109061 | CR | Approval | 23.502 CR3241R1 (Rel-16, 'F'): RID Update for SNPN UEs | Ericsson, Nokia, Nokia Shanghai Bell, OPPO | Rel-16 | Revision of S2-2108459r02. Approved | Agreed | |
| 7.7 | S2-2108460 | CR | Approval | 23.502 CR3242 (Rel-17, 'A'): RID Update for SNPN UEs | Ericsson | Rel-17 | r00 agreed. Revised to S2-2109062. | Devaki (Nokia) supports the CR, wish to cosign. Peter Hedman (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109062 | CR | Approval | 23.502 CR3242R1 (Rel-17, 'A'): RID Update for SNPN UEs | Ericsson, Nokia, Nokia Shanghai Bell, OPPO | Rel-17 | Revision of S2-2108460r00. Approved | Agreed | |
| 7.7 | S2-2108565 | CR | Approval | 23.501 CR3392 (Rel-16, 'F'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-16 | r04 agreed. Revised to S2-2109063. | George Foti (Ericsson) provides r01. Minor clarifications and co-signed as well Fei (OPPO) provides r02. Devaki (Nokia) comments. Qianghua (Huawei) provides r03 George (Ericsson) provides r04. Did some minor editorial linguistic changes. The sentence is too long. Fei (OPPO) is fine with r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109063 | CR | Approval | 23.501 CR3392R1 (Rel-16, 'F'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon, Ericsson, OPPO, Nokia, Nokia Shanghai Bell | Rel-16 | Revision of S2-2108565r04. Approved | Agreed | |
| 7.7 | S2-2108566 | CR | Approval | 23.501 CR3393 (Rel-17, 'A'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2109064. | Revised | |
| 7.7 | S2-2109064 | CR | Approval | 23.501 CR3393R1 (Rel-17, 'A'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon, Ericsson, OPPO, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108566r00. Approved | Agreed | |
| 7.7 | S2-2108567 | CR | Approval | 23.502 CR3255 (Rel-16, 'F'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-16 | r01 agreed. Revised to S2-2109065. | Devaki (Nokia) comments that this CR is not needed as existing Note 3 covers the scenario already. Qianghua (Huawei) replies Haris(Qualcomm) provides r01 Qianghua (Huawei) OK with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109065 | CR | Approval | 23.502 CR3255R1 (Rel-16, 'F'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-16 | Revision of S2-2108567r01. Approved | Agreed | |
| 7.7 | S2-2108568 | CR | Approval | 23.502 CR3256 (Rel-17, 'A'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2109066. | Devaki (Nokia) comments that this CR is not needed as existing Note 3 covers the scenario already. Same comment as 8567. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109066 | CR | Approval | 23.502 CR3256R1 (Rel-17, 'A'): Correction for CAG restrictions with emergency services | Huawei, HiSilicon | Rel-17 | Revision of S2-2108568r00. Approved | Agreed | |
| 7.7 | S2-2108846 | CR | Approval | 23.501 CR3437 (Rel-16, 'F'): Adding AdminCycleTimeExtension and PSFPAdminCycleTimeExtension to PMIC | Qualcomm | Rel-16 | Approved | Devaki (Nokia) wonders if the CR is FASMO really as the added parameters are extension parameters and it could be added from Rel-17 only? Sebastian (Qualcomm) explains why the CR is FASMO Zhendong (ZTE): provides comments. Sebastian (Qualcomm) replies to ZTE ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 7.7 | S2-2108864 | CR | Approval | 23.501 CR3443 (Rel-17, 'A'): Adding AdminCycleTimeExtension and PSFPAdminCycleTimeExtension to PMIC | Qualcomm | Rel-17 | Approved | Agreed | |
| 7.7 | S2-2108867 | CR | Approval | 23.501 CR3444 (Rel-16, 'F'): Time conversion for Tick granularity and PSFPTickGranularity | Qualcomm | Rel-16 | Postponed | Chunshan (Tencent) have some questions. Jari (NTT DOCOMO) proposes to note Sebastian (Qualcomm) replies to Tencent Chunshan (Tencent) responses to Sebastian (Qualcomm) Sebastian (Qualcomm) replies to Jari and provides r01 Chunshan (Tencent) responses to Sebastian (Qualcomm). ==== Revisions Deadline ==== Devaki (Nokia) proposes to postpone the paper (objects to the revisions). Sebastian (Qualcomm) replies to Nokia ==== Comments Deadline ==== | Postponed |
| 7.7 | S2-2108870 | CR | Approval | 23.501 CR3445 (Rel-17, 'A'): Time conversion for Tick granularity and PSFPTickGranularity | Qualcomm | Rel-17 | Postponed | Postponed | |
| 7.7 | S2-2108871 | CR | Approval | 23.501 CR3446 (Rel-16, 'F'): Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided | Qualcomm Incorporated | Rel-16 | r02 agreed. Revised to S2-2109067. | Devaki (Nokia) objects to the CR as assuming per UE configuration in the network would be wrong. Sebastian (Qualcomm) responds to Nokia and clarifies that the CR does not propose per UE configuration Jari (NTT DOCOMO) comments Sebastian (Qualcomm) replies to NTT DOCOMO Devaki (Nokia) replies. Sebastian (Qualcomm) replies to Nokia Sebastian (Qualcomm) replies and provides r01 Devaki (Nokia) fine with r01. Zhendong (ZTE): provides comments Qianghua (Huawei) comments Sebastian (Qualcomm) replies to ZTE Sebastian (Qualcomm) replies to Huawei and provides r02 Sebastian (Qualcomm) replies to Devaki ==== Revisions Deadline ==== Qianghua (Huawei) fine with r02 ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109067 | CR | Approval | 23.501 CR3446R1 (Rel-16, 'F'): Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided | Qualcomm Incorporated | Rel-16 | Revision of S2-2108871r02. Approved | Agreed | |
| 7.7 | S2-2108872 | CR | Approval | 23.501 CR3447 (Rel-17, 'A'): Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided | Qualcomm Incorporated | Rel-17 | r00 agreed. Revised to S2-2109068. | Devaki (Nokia) objects to the CR, same reason as 8871. Sebastian (Qualcomm) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109068 | CR | Approval | 23.501 CR3447R1 (Rel-17, 'A'): Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided | Qualcomm Incorporated | Rel-17 | Revision of S2-2108872r00. Approved | Agreed | |
| 7.7 | S2-2108873 | CR | Approval | 23.502 CR3302 (Rel-16, 'F'): Include TSN time domain into bridge information reporting procedure | Qualcomm | Rel-16 | r02 agreed. Revised to S2-2109069. | Devaki (Nokia) comments. Sebastian (Qualcomm) provides r02 (please ignore r01) ==== Revisions Deadline ==== Devaki (Nokia) comments that chair notes should be updated to ask 'r02 for approval'. Sebastian (Qualcomm) confirms that r02 should be marked for approval ==== Comments Deadline ==== | Revised |
| 7.7 | S2-2109069 | CR | Approval | 23.502 CR3302R1 (Rel-16, 'F'): Include TSN time domain into bridge information reporting procedure | Qualcomm | Rel-16 | Revision of S2-2108873r02. Approved | Agreed | |
| 7.7 | S2-2108874 | CR | Approval | 23.502 CR3303 (Rel-17, 'A'): Include TSN time domain into bridge information reporting procedure | Qualcomm | Rel-17 | r00 agreed. Revised to S2-2109070. | Revised | |
| 7.7 | S2-2109070 | CR | Approval | 23.502 CR3303R1 (Rel-17, 'A'): Include TSN time domain into bridge information reporting procedure | Qualcomm | Rel-17 | Revision of S2-2108874r00. Approved | Agreed | |
| 7.7 | S2-2109004 | LS In | Action | LS from RAN WG3: Reply LS on Clarification of UE with CAG information in UE subscription | RAN WG3 (R3-216064) | Rel-16 | Noted | Qianghua (Huawei) proposes to note this LS, this is for information, no action requires for SA2 ==== Comments Deadline ==== | Noted |
| 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:=4 | - | |
| 7.11 | S2-2108468 | CR | Approval | 23.502 CR3243 (Rel-16, 'F'): SUPI in Notifications from NSSAAF | Ericsson | Rel-16 | Postponed | Haiyang (Huawei) comments and show concerns. Josep (DT) comments. Alessio(Nokia) also thinks this is not a category F CR, rather a category B CR. We do not agree to this additional feature as it seems there is no problem to solve ... ==== Revisions Deadline ==== Josep (DT) proposes to at least postpone. Peter Hedman (Ericsson) provides replies Haiyang (Huawei) agrees with Josep (DT), suggests to note/postpone this paper. ==== Comments Deadline ==== | Postponed |
| 7.11 | S2-2108469 | CR | Approval | 23.502 CR3244 (Rel-17, 'A'): SUPI in Notifications from NSSAAF | Ericsson | Rel-17 | Postponed | Haiyang (Huawei) comments and show concerns. Alessio(Nokia) also thinks this is not a category F CR, rather a category B CR. We do not agree to this additional feature as it seems there is no problem to solve ... ==== Revisions Deadline ==== Peter Hedman (Ericsson) provides replies Haiyang (Huawei) suggests to note/postpone this CR. ==== Comments Deadline ==== | Postponed |
| 7.11 | S2-2108709 | CR | Approval | 23.502 CR3276 (Rel-17, 'F'): The update for Nnrf_NFDiscovery_Request service operation | China Mobile | Rel-17 | r01 agreed. Revised to S2-2109071. | Aihua (CMCC) provides r01 based on offline discussion. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.11 | S2-2109071 | CR | Approval | 23.502 CR3276R1 (Rel-17, 'C'): The update for Nnrf_NFDiscovery_Request service operation | China Mobile | Rel-17 | Revision of S2-2108709r01. Approved | Agreed | |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=2 | - | |
| 7.12 | S2-2108304 | CR | Approval | 23.501 CR2524R1 (Rel-16, 'F'): On alignment of RACS capability detection with RAN WG3 | Nokia, Nokia Shanghai bell, Qualcomm Inc., Ericsson | Rel-16 | Revision of (Postponed) S2-2100063 from S2#143E. Approved | Agreed | |
| 7.12 | S2-2108305 | CR | Approval | 23.401 CR3617R1 (Rel-16, 'F'): On alignment of RACS capability detection with RAN WG3 | Nokia, Nokia Shanghai Bell,Qualcomm Inc, Ericsson | Rel-16 | Revision of (Postponed) S2-2100064 from S2#143E. Approved | Agreed | |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=2 | - | |
| 7.13 | S2-2108297 | LS In | Action | LS from GSMA 5GJA: LS to 3GPP on IMS Data Channel Architecture | GSMA 5GJA (5GJA18_109r1) | Responses drafted in S2-2108901 and S2-2108907. Postponed | Leo (Deutsche Telekom) proposes to postpone the LS to the next SA2 meeting. ==== Comments Deadline ==== | Postponed | |
| 7.13 | S2-2108907 | LS OUT | Approval | [DRAFT] Reply LS on IMS Data Channel Architecture | China Mobile | Response to S2-2108297. Postponed | Leo (Deutsche Telekom) provides r01. Chia-Lin (MediaTek) suggest to postpone LS ==== Revisions Deadline ==== Leo (Deutsche Telekom) agrees to postpone the reply LS to the next SA2 meeting. ==== Comments Deadline ==== | Postponed | |
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=0 | - | |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=9 | - | |
| 7.15 | S2-2108364 | CR | Approval | 23.501 CR3365 (Rel-16, 'F'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-16 | Approved | Agreed | |
| 7.15 | S2-2108365 | CR | Approval | 23.501 CR3366 (Rel-17, 'A'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-17 | Approved | Agreed | |
| 7.15 | S2-2108366 | CR | Approval | 23.502 CR3226 (Rel-16, 'F'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-16 | r02 agreed. Revised to S2-2109072. | Laurent (Nokia): provides r01 Stefan (Ericsson) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 7.15 | S2-2109072 | CR | Approval | 23.502 CR3226R1 (Rel-16, 'F'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-16 | Revision of S2-2108366r02. Approved | Agreed | |
| 7.15 | S2-2108367 | CR | Approval | 23.502 CR3227 (Rel-17, 'A'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-17 | r00 agreed. Revised to S2-2109073. | Revised | |
| 7.15 | S2-2109073 | CR | Approval | 23.502 CR3227R1 (Rel-17, 'A'): V-SMF change at inter-PLMN mobility | Ericsson | Rel-17 | Revision of S2-2108367r00. Approved | Agreed | |
| 7.15 | S2-2108678 | CR | Approval | 23.502 CR3273 (Rel-17, 'F'): N9 forwarding tunnel between ULCLs controlled by I-SMF | Huawei, HiSilicon | Rel-17 | Postponed | Laurent (Nokia): Comments Fenqin (Huawei): Comments Laurent (Nokia): answers to Fenqin Laurent (Nokia): provides r01 Fenqin (Huawei): provides r02 Stefan (Ericsson) provides question Laurent (Nokia): proposes to postpone 8678 Fenqin (Huawei) responds Stefan (Ericsson) supports to postone ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.15 | S2-2108856 | CR | Approval | 23.502 CR2894R1 (Rel-16, 'F'): L-PSA and I-SMF release during mobiity procedure with I-SMF change or removal | Nokia, Nokia Shanghai Bell | Rel-16 | Revision of (Merged and Agreed) S2-2105353 from S2#146E. Postponed | Fenqin (Huawei) propose to note this paper Laurent (Nokia): provides r01 Fenqin (Huawei): propose to Note this paper Stefan (Ericsson) supports to note this rel-16 CR and only do change in rel-17 Laurent (Nokia): OK note or withdraw this rel-16 CR and only do change in rel-17 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 7.15 | S2-2108857 | CR | Approval | 23.502 CR2895R1 (Rel-17, 'A'): L-PSA and I-SMF release during mobiity procedure with I-SMF change or removal | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2105354 from S2#146E. Postponed | Fenqin (Huawei) comment and suggest to merge this paper to 8678 Laurent (Nokia): provides r01 Fenqin (Huawei): propose to postpone 8857 Stefan (Ericsson) supports to postpone Laurent (Nokia): Let's postpone both 8678 and 8857 then ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 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 WID | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=67 | - | |
| 8.1 | - | - | - | General | - | - | Docs:=14 | - | |
| 8.1 | S2-2108647 | CR | Approval | 23.288 CR0481 (Rel-17, 'F'): Term alignment of Target of Analytics Reporting and Analytics Filter Information | China Mobile | Rel-17 | r01 agreed. Revised to S2-2109074. | Yannick (Nokia): Nokia provides r01. Aihua(China Mobile) replies to Yannick(Nokia). Yannick (Nokia): Nokia replies to China Mobile. Aihua(China Mobile) replies to Nokia. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109074 | CR | Approval | 23.288 CR0481R1 (Rel-17, 'F'): Term alignment of Target of Analytics Reporting and Analytics Filter Information | China Mobile | Rel-17 | Revision of S2-2108647r01. Approved | Agreed | |
| 8.1 | S2-2108682 | CR | Approval | 23.288 CR0467R3 (Rel-17, 'F'): Miscellaneous corrections for TS 23.288 on eNA_ph2 | Vivo, Huawei, Ericsson, Nokia, LG Electronics, CATT, Intel | Rel-17 | Revision of (Agreed) S2-2107803 from S2#147E. Approved | Agreed | |
| 8.1 | S2-2108683 | CR | Approval | 23.501 CR3320R2 (Rel-17, 'F'): Miscellaneous correction for eNA Ph2 on TS 23.501 | Vivo, Huawei, HiSilicon, Nokia, LG Electronics, Intel | Rel-17 | Revision of (Agreed) S2-2107804 from S2#147E. Noted | Yannick (Nokia): Nokia notes that this CR is identical to SA2#147E agreed CR, and comments that there is also another revision for the SA2#147E agreed CR in S2-2108711. Vivian (vivo) reply to Yannick(Nokia) and propose to focus on S2-2108683. Yannick (Nokia): Nokia replies to Vivo. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2108684 | CR | Approval | 23.502 CR3196R1 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 on TS 23.502 | Vivo, Huawei, HiSilicon, LG Electronics | Rel-17 | Revision of (Agreed) S2-2107596 from S2#147E. Noted | Yannick (Nokia): Nokia understands that this CR is identical to SA2#147E agreed CR, and comments that there is also another revision for the SA2#147E agreed CR in S2-2108714. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2108685 | CR | Approval | 23.503 CR0664R1 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 on TS 23.503 | Vivo, Huawei, HiSilicon, LG Electronics | Rel-17 | Revision of (Agreed) S2-2107597 from S2#147E. Approved | Agreed | |
| 8.1 | S2-2108711 | CR | Approval | 23.501 CR3320R3 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 on TS 23.501 | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107804 from S2#147E. r04 agreed. Revised to S2-2109075. | Wang Yuan (Huawei) comments that this CR should be aligned with the outcome of S2-2108537/8538/8707. Yannick (Nokia): Nokia provides r01 to address comments from Ericsson on other proposal in S2-2108714. Changes in the CR are related to discussion on S2-2108537/8538 (Huawei), S2-2108707 (Nokia) and S2-2108708 (Lenovo). Wang Yuan (Huawei) cosigns this CR and provide r02. Soohwan (ETRI) provides r03. Yannick (Nokia): Nokia provides r04. Suggests to limit changes in TS 23.501 to the minimum and refer to clause 5.2 from TS 23.288. Wang Yuan (Huawei) is fine with r04 and confirms the cosign of this CR. ==== Revisions Deadline ==== Soohwan (ETRI) okay with r04. ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109075 | CR | Approval | 23.501 CR3320R4 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 | Vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Intel | Rel-17 | Revision of S2-2108711r04. Approved | Agreed | |
| 8.1 | S2-2108714 | CR | Approval | 23.502 CR3196R2 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 on TS 23.502 | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107596 from S2#147E. r04 agreed. Revised to S2-2109076. | Zhang (Ericsson) provides comments Wang Yuan (Huawei) comments that the last three changes in the CR should be aligned with the outcome of S2-2108537/8538/8707. Yannick (Nokia): Nokia provides r01 to address comments from Ericsson. Zhang (Ericsson) is OK with r01 Wang Yuan (Huawei) cosigns this CR and provide r02. Soohwan (ETRI) provides r03. Yannick (Nokia): Nokia provides r04. Suggests to limit changes in TS 23.502 to the minimum and refer to clause 5.2 from TS 23.288. Wang Yuan (Huawei) is fine with r04 and confirms the cosign of this CR. ==== Revisions Deadline ==== Soohwan (ETRI) is okay with r04. Zhang (Ericsson) is OK with r04 and co-sign ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109076 | CR | Approval | 23.502 CR3196R3 (Rel-17, 'F'): Miscellaneous correction for eNA_Ph2 | Vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108714r04. Approved | Agreed | |
| 8.1 | S2-2108966 | CR | Approval | 23.288 CR0492 (Rel-17, 'F'): Resolve normative wording in notes | Nokia, Nokia Shanghai Bell | Rel-17 | r02 agreed. Revised to S2-2109078. | Zhang (Ericsson) provides r01 Mehrdad (Samsung) comments on all revisions and suggests to remove changes of clause 6.1.3 and 6.1A.3.1 from this CR in case it will be handled. Gerald (Nokia): Nokia provides r02 Zhang (Ericsson) is fine with r02 and co-sign Mehrdad (Samsung) comments on r02 and asks for clarification from Ericsson. Zhang (Ericsson) provides comments Gerald (Nokia): Nokia clarifies to Samsung ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109078 | CR | Approval | 23.288 CR0492R1 (Rel-17, 'F'): Resolve normative wording in notes | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108966r02. Approved | Agreed | |
| 8.1 | S2-2108952 | CR | Approval | 23.288 CR0491 (Rel-17, 'F'): Clarification on interaction between timers and supported analytics Delay | Samsung | Rel-17 | r06 agreed. Revised to S2-2109077. | Antoine (Orange) provides r01. Chi (China Unicom) asks question for clarification. Mehrdad (Samsung) is OK with r01 and replies to China Unicom. Chi (China Unicom) provides further comments. Mehrdad (Samsung) replies to China Unicom and provides r02 and r03. Please ignore r02 as it has typo. Gerald (Nokia): Nokia comments on r03 and asks for clarification Mehrdad (Samsung) replies to Nokia and provides r04. Chi (China Unicom) asks question on 'revised waiting time'. Mehrdad (Samsung) replies to China Unicom and provides r05. Zhang (Ericsson) provides comments Mehrdad (Samsung) replies to Ericsson and provides r06. Mehrdad (Samsung) replies to Ericsson. Zhang (Ericsson) is OK with r06 ==== Revisions Deadline ==== Chi (China Unicom) is ok with r06. Gerald (Nokia): Nokia is okay with r05 and r06 ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109077 | CR | Approval | 23.288 CR0491R1 (Rel-17, 'F'): Clarification on interaction between timers and supported analytics Delay | Samsung | Rel-17 | Revision of S2-2108952r06. Approved | Agreed | |
| 8.1 | - | - | - | KI#1 | - | - | Docs:=6 | - | |
| 8.1 | S2-2108537 | DISCUSSION | Agreement | Discussion on ML Model Filter Information during the NWDAF containing MTLF registration. | Huawei, HiSilicon | Rel-17 | Noted | Noted | |
| 8.1 | S2-2108538 | CR | Approval | 23.288 CR0477 (Rel-17, 'F'): Clarify the ML Model Filter Information during the NWDAF containing MTLF registration | Huawei, HiSilicon | Rel-17 | Merged into S2-2109079 | Wang Yuan (Huawei) confirms that this CR is merged into S2-2108707 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.1 | S2-2108650 | CR | Approval | 23.288 CR0461R2 (Rel-17, 'F'): Clarify the NWDAF (MTLF) and NWDAF (AnLF) | China Mobile, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107805 from S2#147E. Noted | Yannick (Nokia): Nokia comments that this CR is related to discussion on other CRs in S2-2108538 from Huawei, S2-2108708 from Lenovo and S2-2108707 from Nokia. Aihua(CMCC) replies to Yannick(Nokia) and provides r01. ==== Revisions Deadline ==== Yannick (Nokia): Nokia proposes to note this document under the assumption that a revision for S2-2108707 would be approved in this meeting. Aihua(China Mobile) suggests to agree r01. Yannick (Nokia): Nokia prefers to note this CR. ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2108707 | CR | Approval | 23.288 CR0486 (Rel-17, 'F'): Corrections to discovery for NWDAF containing MTLF | Nokia, Nokia Shanghai Bell | Rel-17 | r09 agreed. Revised to S2-2109079, merging S2-2108538 and S2-2108708 | Zhang (Ericsson) provides comments Wang Yuan (Huawei) provides comments. Yannick (Nokia): Nokia provides r01. Nokia notes that there are three CRs on the same issue, S2-2108538 (Huawei), S2-2108708 (Lenovo) and S2-2108707 (Nokia). Wang Yuan (Huawei) replies to Yannick (Nokia) and provides r03. Soohwan (ETRI) provides r04. Malla (NTT DOCOMO) provided r05. Yannick (Nokia): Nokia provides r06. Dimitris (Lenovo) provides r07 Yannick (Nokia): Nokia is fine with r07. Yannick (Nokia): Nokia suggests a wording for NOTE Y. Wang Yuan (Huawei) provides r08 and co-signs this CR. Yannick (Nokia): Nokia is ok with r08 Malla (NTT DOCOMO) provided r09 Yannick (Nokia): Nokia is ok with r09. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109079 | CR | Approval | 23.288 CR0486R1 (Rel-17, 'F'): Corrections to discovery for NWDAF containing MTLF | Nokia, Nokia Shanghai Bell, Huawei, NTT DOCOMO, Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2108707r09, merging S2-2108538 and S2-2108708. Approved | Agreed | |
| 8.1 | S2-2108708 | CR | Approval | 23.288 CR0487 (Rel-17, 'F'): ML model provisioning information in NRF | Lenovo, Motorola Mobility | Rel-17 | Merged into S2-2109079 | Yannick (Nokia): Nokia provides comments. Nokia notes that there are three CRs on the same issue, S2-2108538 (Huawei), S2-2108708 (Lenovo) and S2-2108707 (Nokia). Dimitris (Lenovo) is ok to use S2-2108707 as the basis for this discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.1 | - | - | - | KI#2 | - | - | Docs:=11 | - | |
| 8.1 | S2-2108436 | CR | Approval | 23.288 CR0448R1 (Rel-17, 'F'): CR to resolve conflicts in ML model transferring | ETRI, Huawei?, Nokia? | Rel-17 | Revision of (Postponed) S2-2107321 from S2#147E. Confirm Sources! Postponed | Xiaoyan (CATT) objects to r00 (the original CR) and provides r01. Soohwan (ETRI) objects to r01 and proposes a way forward Malla (NTT DOCOMO) asks whether this CR is considered as merged into S2-2108536 Gerald (Nokia): Nokia clarifies that this CR is not merged into S2-2108536. Disagrees with r01. Soohwan provides r02 and comments. Xiaoyan (CATT) provides r03. Xiaoyan (CATT) objects to r02. Soohwan (ETRI) provides r04 and r05 based on the discussion and Soohwan (ETRI) prefers to go with r05. Gerald (Nokia): Nokia disagrees with r03, r04. Asks whether r04 and r05 also merge 8713r04? Soohwan (ETRI) confirms that r04 and r05 capture the content in 8713r04. Xiaoyan (CATT) objects to r05 and r04 too, based on the discussions in S2-2108536 and this thread. Dimitris (Lenovo) comments Gerald (Nokia): Nokia responds to Lenovo. Proposes alternative. Soohwan (ETRI) objects to r03 and the futher revisions which include ML model file address(es) without proposed NOTE and normative text in r04. ==== Revisions Deadline ==== Soohwan (ETRI) proposes to postpone this CR Xiaoyan (CATT) suggests that this CR be marked as merged to S2-2108713. Soohwan (ETRI) disagrees to merge this CR into S2-2108713 and asks to postpone. ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2108536 | DISCUSSION | Agreement | Discussion on ML model transferring during the analytics context transfer. | Huawei, HiSilicon, ETRI | Rel-17 | Noted | Wang Yuan (Huawei) provides r01 based on offline discussions. Xiaoyan (CATT) propose to note this discussion paper and focus on discussions in S2-2108436 thread. Soohwan (ETRI) supports proposal 1 and concerns with proposal 2. Gerald (Nokia): Nokia disagrees with proposal 2 in r00 and r01 Dimitris (Lenovo) suggests to agree first on the ML model transfer procedure then work on the related CRs Xiaoyan (CATT) disagrees with the view of Gerald(Nokia). Wang Yuan (Huawei) also support proposal 1 based on the R17 conclusion for ML model sharing. Xiaoyan (CATT) provides comments to the proposals. Gerald (Nokia): Nokia responds to earlier CATT response Xiaoyan (CATT) provides clarification to Gerald(Nokia). Dimitris (Lenovo) comments Xiaoyan (CATT) responds to Dimitris (Lenovo). Gerald (Nokia): Nokia responds to Xiaoyan (CATT) Dimitris (Lenovo) responds to Xiaoyan (CATT) Soohwan (ETRI) provides comments Xiaoyan (CATT) responds to Gerald (Nokia). Xiaoyan (CATT) replies to Soohwan (ETRI). Soohwan (ETRI) replies to Xiaoyan. Wang Yuan (Huawei) replies to earlier CATT questions. Xiaoyan (CATT) replies to Wang Yuan (Huawei). Soohwan (ETRI) asks any way forward. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2108551 | CR | Approval | 23.288 CR0478 (Rel-17, 'F'): Clarification on external triggers and clean up the UE mobility analytics | CATT | Rel-17 | r07 agreed. Revised to S2-2109080. | Zhang (Ericsson) provides comments Jiahui (China Telecom) provides comments Gerald (Nokia): Nokia provides comments on original Yingying(CATT) replies to Zhang Fu(Ericsson) and Jiahui (China Telecom), and provides r01. Yingying(CATT) replies to Gerald (Nokia), and provides r02. Gerald (Nokia): Nokia comments on r02 Yingying(CATT) agrees with Zhang(Ericsson) and provides r03. Gerald (Nokia): Nokia comments on r03 Yingying(CATT) replies to Gerald (Nokia) and provides r04. Zhang (Ericsson) provides r05 Gerald (Nokia): Nokia objects to r05, is okay with r04 Zhang (Ericsson) provides comments and r06 Gerald (Nokia): Nokia disagrees with r06 and provides r07 Yingying(CATT) agrees with Gerald (Nokia), is okay with r07, and provides r08. Gerald (Nokia): Nokia replies to Zhang (E///) Yingying(CATT) replies to Zhang (Ericsson). Yingying(CATT) provides clarification to Zhang (Ericsson) . Zhang (Ericsson) provides comments and r09 Yingying(CATT) provides r10 and prefers to r04 or r08, is okay with r07. Gerald (Nokia): Nokia comments on r09 and r10 Yingying(CATT) provides r11. ==== Revisions Deadline ==== Gerald (Nokia): Nokia is okay with r04/r08 and r07; objects to other revisions and original Zhang (Ericsson) is OK with r07; objects to other versions ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109080 | CR | Approval | 23.288 CR0478R1 (Rel-17, 'F'): Clarification on external triggers and clean up the UE mobility analytics | CATT, Ericsson | Rel-17 | Revision of S2-2108551r07. Approved | Agreed | |
| 8.1 | S2-2108664 | CR | Approval | 23.288 CR0463R2 (Rel-17, 'F'): Clarify the UE aggregated mobility analytics exposure to NF | China Mobile | Rel-17 | Revision of (Agreed) S2-2107813 from S2#147E. r02 agreed. Revised to S2-2109081. | Gerald (Nokia): Nokia does not see need for this CR revision Aihua(China Mobile) replies to Antoine (Orange) and Gerald (Nokia). Gerald (Nokia): Nokia responds to China Mobile Aihua(China Mobile) replies to Gerald (Nokia) and provides r01. Gerald (Nokia): Nokia responds to Aihua (China Mobile) and comments on r01 Aihua(China Mobile) replies to Gerald (Nokia) and provides r02. ==== Revisions Deadline ==== Gerald (Nokia): Nokia is okay with r02 ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109081 | CR | Approval | 23.288 CR0463R3 (Rel-17, 'F'): Clarify the UE aggregated mobility analytics exposure to NF | China Mobile | Rel-17 | Revision of S2-2108664r02. Approved | Agreed | |
| 8.1 | S2-2108713 | CR | Approval | 23.288 CR0488 (Rel-17, 'F'): Clarification of transferring ML model during analytics transfer | Lenovo, Motorola Mobility | Rel-17 | Postponed | Soohwan (ETRI) asks to have discussion regarding on this CR in S2-2108546 thread. Xiaoyan (CATT) suggest that this CR be merged into S2-2108436. Dimitris (Lenovo) provides r01 Gerald (Nokia): Nokia comments on r01 Dimitris (Lenovo) provides r02 Xiaoyan (CATT) provides r03. Gerald (Nokia): Nokia provides r04 Soohwan (ETRI) proposes to merge this CR into S2-2108436. Dimitris (Lenovo) suggests to keep CRs separate for now Soohwan (ETRI) replies to Dimitris. Xiaoyan (CATT) objects to r04. Dimitris (Lenovo) provides r05 Gerald (Nokia): Nokia comments on r05 Dimitris (Lenovo) provides r06 ==== Revisions Deadline ==== Soohwan(ETRI) proposes to postpone this CR. Xiaoyan (CATT) support r06 with small modifications to address Soohwan (ETRI) comments. Soohwan (ETRI) objects to approve this CR. Xiaoyan (CATT) clarifies to Soohwan (ETRI) and support approving r06 with small modifications. Dimitris (Lenovo) is ok with r04 or r06 with the modifications proposed by Xiaoyan (CATT). Propose to discuss in CC2 Dimitris (Lenovo) suggests to go with r04 or r06 if acceptable Soohwan (ETRI) disagrees to approve r04 and r06. Gerald (Nokia): Nokia is only okay with r04, otherwise suggests to POSTPONE Dimitris (Lenovo) asks Soohwan (ETRI) to reconsider agreeing r04 Soohwan (ETRI) revokes the objection on r04 and confirms that r04 is okay to us. Also, Soohwan (ETRI) asks to add ETRI as co-source company in r04. Wang Yuan (Huawei) is fine with r04. Xiaoyan (CATT) can only accept r06 or r05 with small modifications, objects to other revisions (including r00); otherwise fine to postpone. Dimitris (Lenovo) requests clarification from Xiaoyan (CATT) Xiaoyan (CATT) replies to Dimitris (Lenovo). ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2108735 | CR | Approval | 23.288 CR0490 (Rel-17, 'F'): Alignment and corrections related to prepared analytics transfer | OPPO | Rel-17 | r03 agreed. Revised to S2-2109082. | Gerald (Nokia): Nokia disagrees with CR Jungshin (Samsung) asks for clarification. Boren (OPPO) replies to Nokia and Samsung. Gerald (Nokia): Nokia responds to OPPO Boren (OPPO) replies to Nokia and provides a r01. Gerald (Nokia): Nokia provides r02 Boren (OPPO) provides r03. Gerald (Nokia): Nokia is okay with r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109082 | CR | Approval | 23.288 CR0490R1 (Rel-17, 'F'): Alignment and corrections related to prepared analytics transfer | OPPO, Nokia | Rel-17 | Revision of S2-2108735r03. Approved | Agreed | |
| 8.1 | S2-2108984 | CR | Approval | 23.288 CR0457R2 (Rel-17, 'F'): Clarifications on transfer of analytics context and analytics subscription | CATT, Samsung | Rel-17 | Revision of (Agreed) S2-2107810 from S2#147E. r04 agreed. Revised to S2-2109083. CC#4: CATT sustained objection to r04. Postponed | Aihua(China Mobile) provides r01. Gerald (Nokia): Nokia provides r02 Aihua(China Mobile) provides comments and r03. Jungshin (Samsung): We can accept both r02 and r03. Gerald (Nokia): Nokia comments on r03 and provides r04. Aihua(China Mobile) comments and provides r05. ==== Revisions Deadline ==== Gerald (Nokia): Nokia prefers r04 Aihua(China Mobile) clarifies and thinks r05 is correct. Xiaoyan (CATT) prefers r05. Gerald (Nokia): Nokia clarifies the issue in r05. Prefers r04. Okay to stay with previous revision S2-2107810 agreed in last meeting. Gerald (Nokia): Nokia replies to CATT Zhang (Ericsson) asks for clarification Aihua(China Mobile) proposes rewording. Xiaoyan (CATT) replies to Nokia. Aihua(China Mobile) clarifies to Zhang (Ericsson). Xiaoyan (CATT) provides clarification to Zhang (Ericsson). Zhang (Ericsson) provides comments Gerald (Nokia): Nokia replies to China Mobile Zhang (Ericsson) prefers r04 and object r05 Gerald (Nokia): Nokia objects r05. Xiaoyan (CATT) objects r04. ==== Comments Deadline ==== Jungshin (Samsung) proposes a revised text Aihua(CMCC) can live with the revised text from Jungshin. | Postponed |
| 8.1 | S2-2109083 | CR | Approval | 23.288 CR0457R3 (Rel-17, 'F'): Clarifications on transfer of analytics context and analytics subscription | CATT, Samsung | Rel-17 | Revision of S2-2108984r04. CC#2: WITHDRAWN | Withdrawn | |
| 8.1 | - | - | - | KI#4 | - | - | Docs:=3 | - | |
| 8.1 | S2-2108425 | CR | Approval | 23.288 CR0472 (Rel-17, 'F'): Clarification on input and output of slice load level analytics | China Telecom | Rel-17 | Postponed | Belen (Ericsson) provides comments Jiahui (China Telecom) replies to Belen (Ericsson) Jiahui (China Telecom) provides r02. ==== Revisions Deadline ==== Belen (Ericsson) objects, given that its comments are not addressed. Propose to POSTPONE Jiahui (China Telecom) agrees to POSTPONE and asks for clarification. ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2108534 | CR | Approval | 23.288 CR0476 (Rel-17, 'F'): Clarify the resource usage for a network slice instance | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109084. | Belen (Ericsson) provides comments David (Samsung) provides r01 and comments Wang Yuan (Huawei) replies to Belen (Ericsson) and David (Samsung), and provides r02. ==== Revisions Deadline ==== Antoine (Orange) asks a question. Wang Yuan (Huawei) replies to Antoine(Orange). Belen (Ericsson) asks to POSPONE given that comments were not addressed. Wang Yuan (Huawei) suggest to approve r01 which addressed Belen(Ericsson)'s comments. Belen (Ericsson) is okay with r01 David (Samsung) would also like to co-source r01. Thanks. ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109084 | CR | Approval | 23.288 CR0476R1 (Rel-17, 'F'): Clarify the resource usage for a network slice instance | Huawei, HiSilicon, Ericsson, Samsung | Rel-17 | Revision of S2-2108534r01. Approved | Agreed | |
| 8.1 | - | - | - | KI#8 | - | - | Docs:=8 | - | |
| 8.1 | S2-2108285 | LS In | Information | LS from CT WG3: LS on question and feedback about the EVEX Work Item | CT WG3 (C3-215316) | Rel-17 | Noted | Yannick (Nokia): Nokia provides comments. Juan Zhang (Qualcomm) replies to Yannick (Nokia). Mehrdad (Samsung) replies to Nokia and Qualcomm. Yannick (Nokia): Nokia replies to Qualcomm and Samsung. Agrees that no LS reply is needed, we can follow-up in SA2 once SA4 has made some progress. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to note the LS. ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2109022 | LS In | Information | LS from SA WG4: Reply LS to CT3 Questions and Feedback on EVEX | SA WG4 (S4-211647) | Rel-17 | Postponed | Yannick (Nokia): Nokia suggests to postpone this LS from SA4 which was received during our meeting. ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2109023 | LS In | Action | LS from SA WG4: Reply LS to SA WG2 on UE Data Collection and Reporting | SA WG4 (S4-211648) | Rel-17 | Postponed | Yannick (Nokia): Nokia agrees to postpone this LS from SA4 which was received during our meeting. The LS is for action to SA2. The proposal from SA4 on a 3-way teleconference among SA2, SA4 and CT3 can probably be answered outside of LS exchange considering the proposed date of December 9th. ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2108597 | CR | Approval | 23.502 CR3258 (Rel-17, 'F'): Update to NF services for UE data collection | CATT | Rel-17 | Approved | Agreed | |
| 8.1 | S2-2108598 | CR | Approval | 23.288 CR0479 (Rel-17, 'F'): Clarifications for UE data collection | CATT | Rel-17 | r03 agreed. Revised to S2-2109085. | Antoine (Orange) provides r01. Yannick (Nokia): Nokia provides r02. Mehrdad (Samsung) comments on original version and all revisons. Xiaoyan (CATT) provides r03. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109085 | CR | Approval | 23.288 CR0479R1 (Rel-17, 'F'): Clarifications for UE data collection | CATT | Rel-17 | Revision of S2-2108598r03. Approved | Agreed | |
| 8.1 | S2-2108696 | CR | Approval | 23.288 CR0455R2 (Rel-17, 'F'): Restriction for 5GC to provide UE IP address to untrusted AF | OPPO | Rel-17 | Revision of (Agreed) S2-2107818 from S2#147E. r03 agreed. Revised to S2-2109086. | Yannick (Nokia): Nokia provides r01. Belen (Ericsson) provides r02 Juan Zhang (Qualcomm) prefers r01. Yang (OPPO) also prefer r01. Provides a clean-up version r03 based on r01. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to approve r03. ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109086 | CR | Approval | 23.288 CR0455R3 (Rel-17, 'F'): Restriction for 5GC to provide UE IP address to untrusted AF | OPPO | Rel-17 | Revision of S2-2108696r03. Approved | Agreed | |
| 8.1 | - | - | - | KI#10 | - | - | Docs:=1 | - | |
| 8.1 | S2-2108665 | CR | Approval | 23.288 CR0462R1 (Rel-17, 'F'): Clarify the Redundant Transmission Experience related analytics | China Mobile, Huawei | Rel-17 | Revision of (Postponed) S2-2107536 from S2#147E. Postponed | Zhang (Ericsson) provides comments Susan (Huawei) provides r01. Hyunsook (LGE) provides comments Susan (Huawei) replies. Susan (Huawei) further clarifies. Susan (Huawei) replies to Hyunsook (LGE). Gerald (Nokia): Nokia provides comments Susan (Huawei): replies and provides r02. Susan (Huawei) provides r03. Gerald (Nokia): Nokia asks for clarification Susan (Huawei) replies to Gerald (Nokia). Gerald (Nokia): Nokia comments on r03 Susan (Huawei) replies to Gerald (Nokia) and provides r04. ==== Revisions Deadline ==== Hyunsook (LGE) prefers to keep ''Observed/Predicted Redundant Transmission Experience value', and have a concern on r04 removing it. Susan (Huawei) propose to move forward with r03 for this meeting. Gerald (Nokia): Nokia suggests to POSTPONE Zhang (Ericsson) is OK with r03 or postpone Hyunsook (LGE) is OK with r03 or postpone. ==== Comments Deadline ==== | Postponed |
| 8.1 | - | - | - | KI#11 | - | - | Docs:=5 | - | |
| 8.1 | S2-2108533 | CR | Approval | 23.288 CR0475 (Rel-17, 'F'): Clarifications for Ndccf services and Nnwdaf_DataManagement services | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109087. | Yannick (Nokia): Nokia provides r01. Wang Yuan (Huawei) agree r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109087 | CR | Approval | 23.288 CR0475R1 (Rel-17, 'F'): Clarifications for Ndccf services and Nnwdaf_DataManagement services | Huawei, HiSilicon | Rel-17 | Revision of S2-2108533r01. Approved | Agreed | |
| 8.1 | S2-2108686 | CR | Approval | 23.288 CR0482 (Rel-17, 'F'): Adding a list to enumerate NF services for enhanced procedures data collection | Vivo | Rel-17 | r01 agreed. Revised to S2-2109088. | Zhang (Ericsson) provides comments Vivian(vivo) replies to Zhang(Ericsson) and provides r01. Zhang (Ericsson) is OK with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109088 | CR | Approval | 23.288 CR0482R1 (Rel-17, 'F'): Adding a list to enumerate NF services for enhanced procedures data collection | Vivo | Rel-17 | Revision of S2-2108686r01. Approved | Agreed | |
| 8.1 | S2-2108687 | CR | Approval | 23.288 CR0483 (Rel-17, 'F'): Clarification for MFAF to be deployed or trusted by the operator | Vivo | Rel-17 | Noted | Antoine (Orange) doesn't see the need for this CR. Zhang (Ericsson) provides comments Vivian (vivo) replies to Zhang(Ericsson) and Antoine(Orange) Yannick (Nokia): Nokia comments on r00 and r01. Malla (NTT DOCOMO) agrees with Antoine (Orange) and we also see no need for this CR. Yannick (Nokia): Nokia provides comments. Malla (NTT DOCOMO) object the CR. Vivian (vivo) replies to all comments and agrees to note this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.1 | - | - | - | KI#12 | - | - | Docs:=4 | - | |
| 8.1 | S2-2108273 | LS In | Action | LS from SA WG6: Reply LS on RAT type for network monitoring | SA WG6 (S6-212146) | Rel-17 | Revision of S2-2107075 from S2#147E. Noted | Yannick (Nokia): Nokia proposes to note this incoming LS. Jungshin (Samsung) proposes to note the LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.1 | S2-2108314 | CR | Approval | 23.503 CR0656R1 (Rel-17, 'F'): Clarification on PCF behaviour based on OSE analytics | China Telecom, Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107224 from S2#147E. Postponed | Yannick (Nokia): Nokia provides comments. Belen (Ericsson) provides comments. Zhuoyi (China Telecom) China Telecom replies to Yannick and Belen, and provide r01. Belen (Ericsson) asks China Telecom for clarifications Zhuoyi (China Telecom) replies to Ericsson's question. Belen (Ericsson) asks questions and think the CR needs futher work. Zhuoyi (China Telecom) replies to Ericsson. Belen (Ericsson) asks to POSTPONE this CR ==== Revisions Deadline ==== Zhuoyi (China Telecom) agrees to POSTPONE this CR ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2108443 | CR | Approval | 23.288 CR0453R2 (Rel-17, 'F'): Clarification on Per-UE Service Experience Request Procedure | Tencent, Tencent Cloud, Huawei, Nokia | Rel-17 | Revision of (Agreed) S2-2107824 from S2#147E. Approved | Belen (Ericsson) asks what the changes are compared with the agreed CR Yannick (Nokia): Nokia clarifies that the CR revision is only for coversheet updates. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 8.1 | S2-2108716 | CR | Approval | 23.288 CR0489 (Rel-17, 'F'): Clarification on including location information for OSE analytics | Lenovo, Motorola Mobility | Rel-17 | Postponed | Wang Yuan (Huawei) comments on original and provides r01. Gerald (Nokia): Nokia is okay with r00, comments on r01 and responds to Huawei Belen (Ericsson) provides comments. Dimitris (Lenovo) responds and provides r02 Malla (NTT DOCOMO) provided suggestions for note. David (Samsung) provides r03, disagrees to aspects of r02. Dimitris (Lenovo) responds to David (Samsung) Belen (Ericsson) cannot accept restrictions to 1 UE only. Belen (Ericsson) asks about r03, prefers r02 David (Samsung) asks for clarifications from Ericsson, still disagrees to r02 . Belen (Ericsson) clarifies to Samsung David (Samsung) comments. Gerald (Nokia): Nokia prefers r02 over r03 Dimitris (Lenovo) provides r04 with a compromise proposal to include Group of UEs Gerald (Nokia): Nokia provides r05 Belen (Ericsson) respond to Samsung, and comments on r04. David (Samsung) provides r06 Belen (Ericsson) prefers r05, r06 cannot be accepted since the use of the Analytics subset is already defined. Dimitris (Lenovo) prefers r05 ==== Revisions Deadline ==== David (Samsung) objects to r05, r04 and r02. Samsung cannot understand why r06 is not agreeable. Dimitris (Lenovo) can agree r06 but further clarifications would be needed on the next meeting David (Samsung) agrees with Lenovo to work on clarifications needed for next meeting Belen (Ericsson) objects to r06, is okay to work for next meeting. David (Samsung) is OK to completely remove the change of cl. 6.4.1 in r06 Gerald (Nokia): Nokia proposes to POSTPONE Dimitris (Lenovo) comments ==== Comments Deadline ==== | Postponed |
| 8.1 | - | - | - | KI#15 | - | - | Docs:=13 | - | |
| 8.1 | S2-2108995 | LS In | Information | LS from SA WG3: Reply LS on NTN specific User Consent | SA WG3 (S3-214349) | Rel-17 | Noted | Noted | |
| 8.1 | S2-2108254 | LS In | Action | LS from SA WG3: LS on User consent | SA WG3 (S3-212123) | Rel-17 | Revision of S2-2107001 from S2#147E. Response drafted in S2-2108969. Final response in S2-2109089 | Belen (Ericsson) asks to NOTE ==== Comments Deadline ==== | Replied to |
| 8.1 | S2-2108969 | LS OUT | Approval | [DRAFT] LS Reply on user consent | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2108254. r02 agreed. Revised to S2-2109089. | Malla (NTT DOCOMO) pointed that LS out text need to align with the approved CRs. Gerald (Nokia): Nokia will provide a revision today afternoon Gerald (Nokia): Nokia provides r01. R02 is expected based on outcome of the KI#15 discussions. Gerald (Nokia): Nokia provides r02. Additional changes might be required based on final outcome of this meeting. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109089 | LS OUT | Approval | Reply LS on user consent | SA WG2 | Rel-17 | Revision of S2-2108969r02. CC#2: Remove Editor's note. Approved | Approved | |
| 8.1 | S2-2108599 | CR | Approval | 23.288 CR0480 (Rel-17, 'F'): User consent for analytics and model training | CATT | Rel-17 | r12 agreed. Revised to S2-2109090. | Xiaoyan (CATT) provides r01 to merge changes in clause 6.2.9 of S2-2108689 into this CR. Gerald (Nokia): Nokia supports the CR and provides r02 Mehrdad (Samsung) comments on original version r01 and r02. Xiaoyan (CATT) provides r03. Vivian(vivo) replies to Xiaoyan (CATT) and provides r04 and asks for co-sign. Gerald (Nokia): Nokia provides r05 Malla (NTT DOCOMO) asks for clarification and raise a concern. Mehrdad (Samsung) comments on r05 Xiaoyan (CATT) replies to Malla (NTT DOCOMO). Xiaoyan (CATT) provides r06. Xiaoyan (CATT) provides additional clarification to Malla (NTT DOCOMO). Vivian (vivo) provides comment about Xiaoyan's(CATT) considering below and provides r07. Wang Yuan (Huawei) has concerns for r07, provides r08 and also cosigns this CR. Malla (NTT DOCOMO) provided comment. Vivian(vivo)replies to Wang Yuan (Huawei) and provides r09. Belen (Ericsson) provides r10, objects to previous revisions and initial document Malla (NTT DOCOMO) provides r11 Gerald (Nokia): Nokia comments on r10 and r11 Belen (Ericsson) is okay with r11. Gerald (Nokia): Nokia comments on r11 Xiaoyan (CATT) provides r12 to fix the editorial as commented by Gerald (Nokia). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109090 | CR | Approval | 23.288 CR0480R1 (Rel-17, 'F'): User consent for analytics and model training | CATT, Nokia, vivo, Huawei | Rel-17 | Revision of S2-2108599r12. Approved | Agreed | |
| 8.1 | S2-2108688 | CR | Approval | 23.288 CR0484 (Rel-17, 'F'): Termination request or rejection of NWDAF data managment service due to user consent not granted | Vivo | Rel-17 | r04 agreed. Revised to S2-2109091. | Gerald (Nokia): Nokia comments on original Vivian (vivo) replies to Gerald's (Nokia) comments and provides r01. Malla (NTT DOCOMO) provided comment. Vivian(vivo) replies to Malla's (NTT DOCOMO) comment. Vivian(vivo) apologizes for the wrong r02 and provides r03. Gerald (Nokia): Nokia provides r04 ==== Revisions Deadline ==== Vivian(vivo) thanks to Gerald (Nokia) and is OK with r04 ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109091 | CR | Approval | 23.288 CR0484R1 (Rel-17, 'F'): Termination request or rejection of NWDAF data managment service due to user consent not granted | Vivo | Rel-17 | Revision of S2-2108688r04. Approved | Agreed | |
| 8.1 | S2-2108689 | CR | Approval | 23.288 CR0485 (Rel-17, 'F'): Termination request or rejection of NWDAF ML model provision service due to user consent not granted | Vivo | Rel-17 | Not Handled | XIaoyan (CATT) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | - |
| 8.1 | S2-2108967 | CR | Approval | 23.288 CR0493 (Rel-17, 'B'): DCCF-based user consent checking | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2109092. | Vivian (vivo) comments on original. Gerald (Nokia): Nokia is okay with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109092 | CR | Approval | 23.288 CR0493R1 (Rel-17, 'B'): DCCF-based user consent checking | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108967r01. Approved | Agreed | |
| 8.1 | S2-2108968 | CR | Approval | 23.288 CR0446R1 (Rel-17, 'B'): Tracking of distribution and usage of data subject to user consent | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2107295 from S2#147E. r02 agreed. Revised to S2-2109093. CC#2: Postponed | Malla (NTT DOCOMO) provided comment and proposed that ADRF tracking functionality is studied in R18. Vivian(vivo) provides comments. Belen (Ericsson) objects to this contribution. Gerald (Nokia): Nokia provides r01 Belen (Ericsson) objects to r01, initial version too. Gerald (Nokia): Nokia disagrees with E// view on CatB CRs. Provides r02 ==== Revisions Deadline ==== Aihua (CMCC): suggests to postpone this CR. Gerald (Nokia): Nokia clarifies that r02 was changed to Cat. F Aihua (CMCC): replies and suggests to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 8.1 | S2-2109093 | CR | Approval | 23.288 CR0446R2 (Rel-17, 'B'): Tracking of distribution and usage of data subject to user consent | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108968r02. CC#2: WITHDRAWN | Withdrawn | |
| 8.1 | - | - | - | KI#18 | - | - | Docs:=27 | - | |
| 8.1 | - | - | - | KI#19 | - | - | Docs:=2 | - | |
| 8.1 | S2-2108535 | CR | Approval | 23.288 CR0450R2 (Rel-17, 'F'): Clarify the content of ML model provisioning | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107827 from S2#147E. r06 agreed. Revised to S2-2109094. | Zhang (Ericsson) provides r01 and co-sign Wang Yuan (Huawei) replies to Zhang (Ericsson) and provides r02. Soohwan (ETRI) provides r03. Zhang (Ericsson) provides comments Gerald (Nokia): Nokia provides r04 Wang Yuan (Huawei) replies to Zhang(Ericsson)/Gerald(Nokia) and provides r05. Zhang (Ericsson) is OK with r05 Gerald (Nokia): Nokia prefers r04 over r05 Wang Yuan (Huawei) provides r06 based on Gerald(Nokia)'s comments. Zhang (Ericsson) is OK for both r05 and r06 ==== Revisions Deadline ==== Gerald (Nokia): Nokia is okay with r06 ==== Comments Deadline ==== | Revised |
| 8.1 | S2-2109094 | CR | Approval | 23.288 CR0450R3 (Rel-17, 'F'): Clarify the content of ML model provisioning | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, CATT | Rel-17 | Revision of S2-2108535r06. Approved | Agreed | |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=56 | - | |
| 8.2 | S2-2108264 | LS In | Action | LS from CT WG1: LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | CT WG1 (C1-215137) | Rel-16 | Revision of S2-2107026 from S2#147E. Responses drafted in S2-2108829 and S2-2108905. Postponed | Postponed | |
| 8.2 | S2-2108829 | LS OUT | Approval | [DRAFT] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | MediaTek Inc. | Rel-17 | Response to S2-2108264. Noted | Devaki (Nokia) comments. Josep (DT) requires clarifications to make the answer clearer, provides r01. Chia-Lin (MediaTek) provides r02 on only change of 'a' to 'an' SNPN ==== Revisions Deadline ==== Devaki (Nokia) supports the LS out, any version is good. (sorry my earlier comment was for 8876 URSP LS out). Peter Hedman (Ericsson) provides comments and objects to r01 and r02, and proposes a simple change. Josep (DT) asks the reasoning behind the proposed change (removal of 'within'). Josep (DT) objects to r00. Peter Hedman (Ericsson) provides reply Josep (DT) states that NSSAA as part of CH has not been agreed. Peter Hedman (Ericsson) provides reply that NSSAA in subscribed network is the only reasonable option for NSSAA ==== Comments Deadline ==== Yi (China Mobile) accept r02, objects r00 and r03. | Noted |
| 8.2 | S2-2108905 | LS OUT | Approval | [DRAFT] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | China Mobile | Response to S2-2108264. Noted | Peter (Ericsson) provides comments, and propose to use S2-2108829 as basis ==== Revisions Deadline ==== Devaki (Nokia) is not aligned with SoH outcome on Monday, objects to the LS out. ==== Comments Deadline ==== | Noted | |
| 8.2 | S2-2108265 | LS In | Action | LS from CT WG1: LS on network slice admission control for SNPN onboarding | CT WG1 (C1-215159) | Revision of S2-2107028 from S2#147E. Response drafted in S2-2108571. Final response in S2-2109257 | Replied to | ||
| 8.2 | S2-2108571 | LS OUT | Approval | [DRAFT] Reply LS on network slice admission control for SNPN onboarding | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107415 from S2#147E. Response to S2-2108265. r02 agreed. Revised to S2-2109257. | Antoine (Orange) provides r01. Qianghua (Huawei) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109257 | LS OUT | Approval | Reply LS on network slice admission control for SNPN onboarding | SA WG2 | Rel-17 | Revision of S2-2108571r02. Approved | Approved | |
| 8.2 | S2-2108277 | LS In | Information | LS from CT WG1: Reply LS on limited service availability of an SNPN | CT WG1 (C1-216096) | Rel-17 | Response drafted in S2-2108330. Final response in S2-2109254 | Replied to | |
| 8.2 | S2-2108330 | LS OUT | Approval | [DRAFT] Reply LS on limited service availability of an SNPN | Qualcomm | Rel-17 | Response to S2-2108277. r00 agreed. Revised to S2-2109254. | Revised | |
| 8.2 | S2-2109254 | LS OUT | Approval | Reply LS on limited service availability of an SNPN | SA WG2 | Rel-17 | Revision of S2-2108330r00. Approved | Approved | |
| 8.2 | S2-2108282 | LS In | Action | LS from CT WG1: LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | CT WG1 (C1-216294) | Rel-17 | Responses drafted in S2-2108827 and S2-2108876. Postponed | Postponed | |
| 8.2 | S2-2108827 | LS OUT | Approval | [DRAFT] Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth. | MediaTek Inc. | Rel-17 | Response to S2-2108282. Noted | Josep (DT) assumes that the discussion thread is S2-2108876. Sebastian (Qualcomm) objects to the LS for reasons given for S2-2108828 ==== Revisions Deadline ==== Chia-Lin (MediaTek) proposes this LS to be merged to S2-2108876 for easier maintaining discussion ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108876 | LS OUT | Approval | [DRAFT] Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | Qualcomm | Rel-17 | Response to S2-2108282. Noted | Devaki (Nokia) comments. Josep (DT) disagrees that dynamic policies and CH were in scope of the TR. Provides r01 Peter Hedman (Ericsson) provides comments Josep (DT) replies. Peter Hedman (Ericsson) provides reply Antoine (Orange) provides r02. Sebastian (Qualcomm) provides r03 and objects to r01 and r02 Antoine (Orange) provides r04. Chia-Lin (MediaTek) provides comments on r04 Sebastian (Qualcomm) objects to r04 Antoine (Orange) provides r05. Sebastian (Qualcomm) provides r06 ==== Revisions Deadline ==== Antoine (Orange) comments on r06. Devaki (Nokia) comments against r06, believes answer to Q1 is wrong, no common understanding. Chia-Lin (MediaTek) cannot accept r06 and other versions including the original one since no agreements are made for two questions Josep (DT) comments. Agrees that there seems to be no agreement. ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108328 | CR | Approval | 23.501 CR3314R1 (Rel-17, 'F'): Support for emergency calls in limited service state | Qualcomm Incorporated | Rel-17 | Revision of (Noted) S2-2107528 from S2#147E. r07 agreed. Revised to S2-2109259, merging S2-2108595 | Rainer (Nokia) provides r01. Peter Hedman (Ericsson) provides r02 Peter Hedman (Ericsson) provides correct link to the r02 Hualin(Huawei) comments. Huan(vivo) merge S2-2108595 and provides r03. Josep (DT) co-signs, provides r04 with minor editorials. Haris(Qualcomm) asks question for text removal in r03 and r04 Josep (DT) comments, provides r05. Huan (vivo) provides feedback and willing to cosign Jianning (Xiaomi) provide r06, and co-sign Rainer (Nokia) is ok with r05. Josep (DT) provides r07 with minor (English) editorials. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109259 | CR | Approval | 23.501 CR3314R2 (Rel-17, 'F'): Support for emergency calls in limited service state | Qualcomm Incorporated, Ericsson, Deutsche Telekom, Xiaomi, vivo | Rel-17 | Revision of S2-2108328r07, merging S2-2108595. Approved | Agreed | |
| 8.2 | S2-2108444 | DISCUSSION | Agreement | Discussion on UE ID of SNPN UE used for accessing emergency services in PLMN | vivo | Rel-17 | Noted | Noted | |
| 8.2 | S2-2108445 | CR | Approval | 23.501 CR3371 (Rel-17, 'F'): Correct the UE ID of SNPN UE used for accessing emergency services in PLMN | Vivo | Rel-17 | Noted | George Foti (Ericsson) provides comments. It is not clear what problem the CR is solving. What breaks if the ES is treated like a UE in limited service with no UICC. Will such a session not be established. This additional complexity is not required Xiaowan(vivo) replies George Foti (Ericsson) and thinks S2-2108444 discussion slides can help to understand the problem Kisuk (Samsung) agree with Ericsson's comments Fei (OPPO) asks questions. Xiaowan vivo(vivo) replies to Fei (OPPO) and seek further clarification. Fei (OPPO) responds to Xiaowan (vivo) Josep (DT) asks questions for clarification. Rainer (Nokia) comments that the scenario is unclear. Jianning (Xiaomi) provides view Haris (Qualcomm) proposes to note the CR Xiaowan (vivo) replies and provides r01 Josep (DT) comments. Proposes to formulate as a NOTE. Rainer (Nokia) proposes to note 8445. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108446 | CR | Approval | 23.502 CR3238 (Rel-17, 'F'): Correct the UE ID of SNPN UE used for accessing emergency services in PLMN | Vivo | Rel-17 | Noted | George Foti (Ericsson) please see comments on 8445 Xiaowan(vivo) replies George Foti (Ericsson) and thinks S2-2108444 discussion slides can help to understand the problem Rainer (Nokia) same as for 8445. Haris(Qualcomm) proposes to note the CR Xiaowan replies to Haris(Qualcomm) Haris(Qualcomm) comments Xiaowan(vivo) replies to Haris(Qualcomm) and also seek view from Antoine (ORANGE) whether authentication is possible or not when a SNPN UE access to PLMN for emergency service Antoine (Orange) provides view. Xiaowan(vivo) provides r01 and replies Haris(Qualcomm) comments on r01 Josep (DT) proposes to send an LS to CT1 to clarify the behavior. George (Ericsson) comments. What is the purpose of the LS. It is clear that this case can be treated like a UE without UICC. Is there anything else needed. Or are U proposing to send an LS with this clarification? Xiaowan(vivo) provides Haris(Qualcomm) Xiawan(vivo) doubts 'this case can be treated like a UE without UICC.' and thinks a LS to SA3 is helpful Josep (DT) clarifies. Fei (OPPO) comments. ==== Revisions Deadline ==== Antoine (Orange) asks a question. Josep (DT) comments. Proposes to postpone. Haris(Qualcomm) objects to this CR (all revisions) Rainer (Nokia) proposes to note 8446. ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108461 | CR | Approval | 23.501 CR3256R2 (Rel-17, 'F'): UE onboarding architecture | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo, Motorola Mobility, Huawei | Rel-17 | Revision of (Agreed) S2-2108095 from S2#147E. Not Handled | - | |
| 8.2 | S2-2108462 | CR | Approval | 23.502 CR3137R1 (Rel-17, 'F'): PDU session handling for inter-AMF mobility | Ericsson | Rel-17 | Revision of (unhandled) S2-2107186 from S2#147E. Not Handled | Youngkyo(Samsung) proposes to merge this CR into S2-2108442 (AI#6.2). Peter Hedman (Ericsson) provides comments and technically prefer 08642. Youngkyo(Samsung) is okay to have this CR as a baseline and provides a r01. Qianghua (Huawei) comments Youngkyo(Samsung) replies to Qianghua(Huawei). Devaki (Nokia) comments. Youngkyo(Samsung) provides a revision r02. Peter Hedman (Ericsson) provides r03 ==== Revisions Deadline ==== Youngkyo(Samsung) prefers r02 but is okay with r03. Youngkyo(Samsung) requests to take all the proposal of S2-2108462r03 into the S2-2108462, which is marked as merged into S2-2108462(AI#6.2) . ==== Comments Deadline ==== | - |
| 8.2 | S2-2108465 | CR | Approval | 23.501 CR3257R2 (Rel-17, 'D'): Rapporteur's editorial cleanup for eNPN | Ericsson, [Nokia, Nokia Shanghai Bell, vivo, Deutsche Telekom] | Rel-17 | Revision of (Agreed) S2-2108090 from S2#147E. r02 agreed. Revised to S2-2109256. | Josep (DT) provides r01. Josep (DT) forgot to format one bullet point. Provides r02 Jianning (Xiaomi) provides comment Josep (DT) replies. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109256 | CR | Approval | 23.501 CR3257R3 (Rel-17, 'D'): Rapporteur's editorial cleanup for eNPN | Ericsson, Nokia, Nokia Shanghai Bell, vivo, Deutsche Telekom | Rel-17 | Revision of S2-2108465r02. Approved | Agreed | |
| 8.2 | S2-2108466 | CR | Approval | 23.501 CR3373 (Rel-17, 'F'): Corrections for CH using AUSF/UDM | Ericsson | Rel-17 | r05 agreed. Revised to S2-2109260, merging S2-2108811 | Kisuk (Samsung) comments. Huan (vivo) comments and ask for clarifications Josep (DT) asks questions for clarification. Jianning (Xiaomi) provides comment Qianghua (Huawei) provides comments Sebastian (Qualcomm) provides r01 Josep (DT) provides r02. Peter Hedman (Ericsson) provides replies Antoine (Orange) provides r03. Jianning (Xiaomi) provides r04 Peter Hedman (Ericsson) provides r05 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109260 | CR | Approval | 23.501 CR3373R1 (Rel-17, 'F'): Corrections for CH using AUSF/UDM | Ericsson | Rel-17 | Revision of S2-2108466r05, merging S2-2108811. Approved | Agreed | |
| 8.2 | S2-2108467 | CR | Approval | 23.501 CR3374 (Rel-17, 'F'): Correction to AMF Onboarding Configuration Data | Ericsson | Rel-17 | r03 agreed. Revised to S2-2109261. | Rainer (Nokia) provides r01. Jihoon (ETRI) provides r02. Jianning (Xiaomi) provides comment Peter Hedman (Ericsson) provides reply Jianning (Xiaomi) replies to Peter (Ericsson), Peter Hedman (Ericsson) provides r03 ==== Revisions Deadline ==== Jianning (Xiaomi) is ok with r03 Rainer (Nokia) is ok with r03. Jihoon (ETRI) is also ok with r03. ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109261 | CR | Approval | 23.501 CR3374R1 (Rel-17, 'F'): Correction to AMF Onboarding Configuration Data | Ericsson, ETRI | Rel-17 | Revision of S2-2108467r03. Approved | Agreed | |
| 8.2 | S2-2108472 | CR | Approval | 23.501 CR3241R1 (Rel-17, 'F'): Network slice admission control for SNPN onboarding | Ericsson, MediaTek Inc, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2107118 from S2#147E. Approved | Agreed | |
| 8.2 | S2-2108473 | CR | Approval | 23.501 CR3240R1 (Rel-17, 'F'): Network Slicing scope in relation to SNPNs | Ericsson, Qualcomm, MediaTek Inc, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2107116 from S2#147E. CC#2: r01 agreed. Revised to S2-2109346. | Josep (DT) objects to r00. Provides r01 Peter Hedman (Ericsson) provides comments Yi (China Mobile) objects to the CR and ask for clarification. Hualin(Huawei) comments this CR should also consider the Discussion paper S2-2108918. Devaki (Nokia) responds to Hualin. Chia-Lin (MediaTek) provides r02 Hualin(Huawei) provides r03 and r04. Chia-Lin (MediaTek) cannot accept r04 and has concerns on r03 Fei (OPPO) comments on r03. Rainer (Nokia) comments. Hualin(Huawei) object r02, r01 and the original version. ==== Revisions Deadline ==== Josep (DT) objects to r00, r02, r03, r04, r05. Devaki (Nokia) supports r00, r02, can live with r03 as well. Haris(Qualcomm) prefers r00, can live with r01 (better than nothing), suggests WF for r03 Josep (DT) is OK to document in the minutes 'Prose is not supported for SNPNs'. Chia-Lin (MediaTek) prefers with r00 and r02 and supports WF for r03. Can live with r01 since this aligns with the LS in S2-2108829 Fei (OPPO) is also ok to document in the minutes 'ProSe is not supported for NPNs' Haris(Qualcomm) proposes to agree to r01 instead of noting the CR Chia-Lin (MediaTek) supports Haris's suggestion to agree on r01 Peter Hedman (Ericsson) CR is related to the SoH at CC#1, i.e. proposes to agree e.g. r03 or try a WA, and if not possible ok with r01 Hualin (Huawei) can live with r01 in this meeting. ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109346 | CR | Approval | 23.501 CR3240R2 (Rel-17, 'F'): Network Slicing scope in relation to SNPNs | Ericsson, Qualcomm, MediaTek Inc, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108473r01. Approved | Agreed | |
| 8.2 | S2-2108569 | CR | Approval | 23.501 CR3394 (Rel-17, 'F'): Clarification for QoS differentiation for User Plane IPsec Child SA in underlay network | Huawei, HiSilicon | Rel-17 | Postponed. CC#2: r02 agreed. Revised to S2-2109352. | Peter (Ericsson) provides comments and r01 Qianghua (Huawei) replies Qianghua (Huawei) provides r02 Peter Hedman (Ericsson) provides reply ==== Revisions Deadline ==== Devaki (Nokia) comments. Devaki (Nokia) prefers to go with r01. Qianghua (Huawei) prefers to go with r02 and replies Peter Hedman (Ericsson) propose to POSTPONE the CR Qianghua (Huawei) proposes to go r02 and replies ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109352 | CR | Approval | 23.501 CR3394R1 (Rel-17, 'F'): Clarification for QoS differentiation for User Plane IPsec Child SA in underlay network | Huawei, HiSilicon | Rel-17 | CC#2: Revision of S2-2108569r02. Approved | Agreed | |
| 8.2 | S2-2108570 | LS OUT | Approval | [DRAFT] LS on support of DCS variants in UE Onboarding Architecture | Huawei, HiSilicon | Rel-17 | r06 agreed. Revised to S2-2109258. | Rainer (Nokia) proposes to note the LS in 8570. Qianghua (Huawei) replies Rainer (Nokia) replies and asks for clarification. Peter Hedman (Ericsson) provides comment that the SA3 is aware and no need for any LS Rainer (Nokia) provides r01. Qianghua (Huawei) provides r02 Fei (OPPO) provides r03. Saso (Intel) provides r04. Rainer (Nokia) provides r05. Peter Hedman (Ericsson) provides r06 Rainer (Nokia) replies, is ok with r06. ==== Revisions Deadline ==== Megha (Intel) provides comments. Qianghua (Huawei) OK with r06 Megha (Intel) OK with r06. Fei (OPPO) is fine with r06. ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109258 | LS OUT | Approval | LS on support of DCS variants in UE Onboarding Architecture | SA WG2 | Rel-17 | Revision of S2-2108570r06. Approved | Approved | |
| 8.2 | S2-2108572 | CR | Approval | 23.501 CR3395 (Rel-17, 'F'): Clarification for SNPN access using CH credentials and NSAC for onboarding slice | Huawei, HiSilicon | Rel-17 | Covered by S2-2108472 | Peter (Ericsson) provides comments Devaki (Nokia) objects to the first change in this paper, proposes to merge second change with 8472 thus the CR can be noted or partially merged. Qianghua (Huawei) replies Antoine (Orange) comments and asks a question. Qianghua (Huawei) replies and agrees to merge this paper into 08472 ==== Revisions Deadline ==== Devaki (Nokia) comments, proposes to consider the paper merged. ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108595 | CR | Approval | 23.501 CR3397 (Rel-17, 'F'): Correction on emergency service support in SNPN access mode | Vivo | Rel-17 | Merged into S2-2109259 | Peter (Ericsson) provides comments and propose to mark CR as merged into 108328 Huan(vivo) is OK to merge S2-2108595 into 108328. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2108596 | CR | Approval | 23.501 CR3398 (Rel-17, 'F'): Clarification of access PLMN service via SNPN and vice versa | Vivo | Rel-17 | Noted | Sebastian (Qualcomm) objects to the CR Myungjune (LGE) proposes to note the CR Kisuk (Samsung) proposes to note the CR Huan (vivo) clarify and do not think the scenarios proposed by Qualcomm are within the scope of R16 and R17 NPN ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108704 | CR | Approval | 23.501 CR3417 (Rel-17, 'F'): Correction on realm part of SNPN NAI SUPI | Deutsche Telekom | Rel-17 | Noted | Devaki (Nokia) provides r01. Jianning (Xiaomi) prefers r01, rather than deleting the existing requirement. Josep (DT) can live with the proposed r01. Provides r02 with fixed cover sheet fitting r01 changes Sebastian (Qualcomm) objects to the CR; all versions Kisuk (Samsung) agrees with Qualcomm's opinion. Peter Hedman (Ericsson) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108706 | CR | Approval | 23.501 CR3256R3 (Rel-17, 'F'): UE onboarding architecture | [Ericsson, ]Nokia, Nokia Shanghai Bell[, Qualcomm, Lenovo, Motorola Mobility, Huawei] | Rel-17 | Revision of (Agreed) S2-2108095 from S2#147E. Postponed | Huan (vivo) comments and ask for clarifications Rainer (Nokia) replies to Huan (vivo). Haris(Qualcomm) asks question for clarification Rainer (Nokia) replies. Haris(Qualcomm) provides r01 Rainer (Nokia) provides r02. Haris(Qualcomm) replies to Huan (vivo) Megha (Intel) provides r03 and comments Peter Hedman (Ericsson) provides comment and propose to notet he CR as it seems it would not work to support both DCS options with same HNI. Fei (OPPO) agree with Peter (Ericsson). Fei (OPPO) comments and provides r04. Haris(Qualcomm) comments on r04 and asks whether to ask this question to SA3 Qianghua (Huawei) replies Fei (OPPO) responds Peter Hedman (Ericsson) provides comments Megha (Intel) provides r05 and comments Megha (Intel) provides comments Huan (vivo) provides comments Hualin (Huawei) comments. Peter Hedman (Ericsson) provides comment that LS to SA3 would be useful ==== Revisions Deadline ==== Peter Hedman (Ericsson) proposes to postpone THIS CR revision Megha (Intel) proposes to postpone this CR. Rainer (Nokia) is ok to postpone 8706. ==== Comments Deadline ==== | Postponed |
| 8.2 | S2-2108710 | CR | Approval | 23.501 CR3274R2 (Rel-17, 'F'): ENPN corrections to clarify use of DNN and S-NSSAI for onboarding, AUSF discovery | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE | Rel-17 | Revision of (Agreed) S2-2108101 from S2#147E. CC#2: r02 agreed. Revised to S2-2109349 | Qianghua (Huawei) provides r01 Huan (vivo) comments and provides r02 Rainer (Nokia) cannot accept r02. Rainer (Nokia) is ok with r01. Fei (OPPO) shares concern raised by Huan (vivo). Rainer (Nokia) replies. Fei (OPPO) can live with it. Huan (vivo) comments and ask whether need to be discussed in CC ==== Revisions Deadline ==== Huan (vivo) comments and can only accept r02 Qianghua (Huawei) replies and suggests for r01 Huan (vivo) asks for clarfication Rainer (Nokia) prefers r01. Huan (vivo) provides comments Ashok (Samsung) requests for clarification from Huan (vivo) and also prefers r01 Peter Hedman (Ericsson) prefers r01 ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109349 | CR | Approval | 23.501 CR3274R3 (Rel-17, 'F'): ENPN corrections to clarify use of DNN and S-NSSAI for onboarding, AUSF discovery | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE | Rel-17 | Revision of S2-2108710r02. CC#2: Approved | Agreed | |
| 8.2 | S2-2108715 | CR | Approval | 23.503 CR0661R2 (Rel-17, 'F'): Clarification for PVS address formats | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE | Rel-17 | Revision of (Agreed) S2-2108107 from S2#147E. Approved | Agreed | |
| 8.2 | S2-2108726 | CR | Approval | 23.502 CR3280 (Rel-17, 'F'): 23.502 Clarification on NF discovery by NRF in Onboarding or external authentication scenario | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2109262. | Josep (DT) proposes to NOTE. Hualin(Huawei) replied to Josep (DT) and provide r01. Peter Hedman (Ericsson) provides r02 Josep (DT) comments, provides r03. Hualin(Huawei) is ok with r03. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109262 | CR | Approval | 23.502 CR3280R1 (Rel-17, 'F'): 23.502 Clarification on NF discovery by NRF in Onboarding or external authentication scenario | Huawei, HiSilicon | Rel-17 | Revision of S2-2108726r03. Approved | Agreed | |
| 8.2 | S2-2108727 | CR | Approval | 23.502 CR3281 (Rel-17, 'F'): 23.502 Update procedure of Registration with Onboarding SNPN | Huawei, HiSilicon | Rel-17 | r04 agreed. Revised to S2-2109263. | Rainer (Nokia) provides r01. Jianning (Xiaomi) provides comment Hualin(Huawei) replied to Jianning (Xiaomi). Peter Hedman (Ericsson) provides r02 Jianning (Xiaomi) provide comment Hualin(Huawei) provide r03 based on the comments. Rainer (Nokia) replies, cannot accept r03. Hualin(Huawei) provide r04. ==== Revisions Deadline ==== Rainer (Nokia) replies. Hualin(Huawei) replies. Rainer (Nokia) is ok with r04. Peter Hedman (Ericsson) ok with r04 ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109263 | CR | Approval | 23.502 CR3281R1 (Rel-17, 'F'): 23.502 Update procedure of Registration with Onboarding SNPN | Huawei, HiSilicon | Rel-17 | Revision of S2-2108727r04. Approved | Agreed | |
| 8.2 | S2-2108783 | CR | Approval | 23.502 CR3206R2 (Rel-17, 'F'): Adding PVS information as imput to SMF and PCF sevice operation. | ZTE, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of (Agreed) S2-2108106 from S2#147E. CC#2: Revised to remove the change to Step 1 in S2-2109350 | Ashok (Samsung) comments ==== Revisions Deadline ==== Zhendong (ZTE): provides the repsonse ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109350 | CR | Approval | 23.502 CR3206R3 (Rel-17, 'F'): Adding PVS information as imput to SMF and PCF sevice operation. | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung | Rel-17 | CC#2: Revision of S2-2108783, removing change to Step 1. Approved | Agreed | |
| 8.2 | S2-2108810 | CR | Approval | 23.501 CR3431 (Rel-17, 'F'): Correction for switching 3GPP access between SNPN and PLMN | Xiaomi | Rel-17 | Confirm CR Number - CR states 8810! r03 agreed. Revised to S2-2109264. | Devaki (Nokia) comments that the CR seems unnecessary, also do not see the need to introduce non-SNPN AM for PLMN case. Youngkyo(Samsung) shares the same view with Devaki (Nokia). Josep (DT) supports this CR, provides r01 and co-signs. Jianning (Xiaomi) is fine with r01, and replies to Youngkyo(Samsung) and Devaki (Nokia) Sebastian (Qualcomm) objects to the CR; all versions Jianning (Xiaomi) replies to Sebastian (Qualcomm) Josep (DT) fully agrees with Jianning (Xiaomi). Jianning (Xiaomi) provides r02 Peter Hedman (Ericsson) provides r03 ==== Revisions Deadline ==== Jianning (Xiaomi) can live with r03 Dieter (Deutsche Telekom) comments. Can update following below still? Otherwise it is not consistent and may be interpreted incorrect? We can also do it next meeting, i.e. can postpone for this meeting. Jianning (Xiaomi) replies to Dieter (DT), propose to approve r03 + add 'the network selection is performed as specified in TS 23.122[17],' in second paragraph as Dieter suggested, in CC#2 Dieter (Deutsche Telekom) that is agreeable. ==== Comments Deadline ==== | Revised |
| 8.2 | S2-2109264 | CR | Approval | 23.501 CR3431R1 (Rel-17, 'F'): Correction for switching 3GPP access between SNPN and PLMN | Xiaomi, Deutsche Telekom | Rel-17 | Revision of S2-2108810r03. Approved | Agreed | |
| 8.2 | S2-2108811 | CR | Approval | 23.501 CR3432 (Rel-17, 'F'): Clarification for Credential Holder | Xiaomi | Rel-17 | Merged into S2-2109260 | Devaki (Nokia) provides r01 (although need for the CR is unclear, if it remains, r01 proposes correction to the statement). Kisuk (Samsung) comments. Jianning (Xiaomi) is fine with r01 Qianghua (Huawei) comments Sebastian (Qualcomm) proposes to merge with S2-2108466 Peter Hedman (Ericsson) agree that 108466 is more complete i.e. better to mark this as merged into 108466 Jianning (Xiaomi) is fine to merge with 8466 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.2 | S2-2108828 | CR | Approval | 23.503 CR0688 (Rel-17, 'F'): URSP associatied to registered SNPN | MediaTek Inc. | Rel-17 | Postponed | Devaki (Nokia) provides r01. Josep (DT) objects to this CR. Jianning (Xiaomi) provides view Antoine (Orange) replies. Jianning (Xiaomi) replies Chia-Lin (MediaTek) replies and provides r02 Josep (DT) comments, provides r03. Chia-Lin (MediaTek) provides more clarification Antoine (Orange) provides r04. Josep (DT) agrees with r04. Sebastian (Qualcomm) objects to the CR (all versions) Antoine (Orange) . Devaki (Nokia) comments. Chia-Lin (MediaTek) provides comments and r05 Josep (DT) supports to postpone. Sebastian (Qualcomm) replies to Josef Josep (DT) replies. ==== Revisions Deadline ==== Chia-Lin (MediaTek) provides to postpone the CR since we cannot have any consensus on this Chia-Lin (MediaTek) provides the understadng from our side and hope we can some feedback on this for next meeting Josep (DT) comments. ==== Comments Deadline ==== Chia-Lin (MediaTek) provides the reference content from TS 24.526 below | Postponed |
| 8.2 | S2-2108887 | CR | Approval | 23.501 CR3451 (Rel-17, 'F'): Update architecture figure for access to SNPNs using credentials from Credentials Holder using AUSF and UDM | Qualcomm | Rel-17 | Noted | Josep (DT) objects to this CR. Antoine (Orange) objects to this CR. Sebastian (Qualcomm) asks a question Antoine (Orange) replies. Devaki (Nokia) supports the CR (thought I had commented earlier, seems my email was lost!). Josep (DT) comments. Sebastian (Qualcomm) replies Peter Hedman (Ericsson) provides comments and supports the CR ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108906 | CR | Approval | 23.501 CR3308R2 (Rel-17, 'F'): Network slicing support for SNPN | China Mobile | Rel-17 | Revision of (Noted) S2-2107501 from S2#147E. Confirm CR Revision - CR states 1! Noted | Peter (Ericsson) provides comments and propose to note this CR ==== Revisions Deadline ==== Devaki (Nokia) is not aligned with SoH outcome on Monday, objects to the CR. ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108908 | CR | Approval | 23.228 CR1249 (Rel-17, 'F'): Correction on IMS service provided to SNPN by independent IMS provider | China Mobile | Rel-17 | Noted | Rainer (Nokia) provides r01. Haris(Qualcomm) asks question for clarification Rainer (Nokia) replies to Haris (Qualcomm), agrees that 8908 is not needed. Yi (China Mobile) replies to Haris and provides r02. Antoine (Orange) also agrees that the CR is not needed. ==== Revisions Deadline ==== Yi (China Mobile) replies to Antoine. Antoine (Orange) objects this CR (all versions). ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2108916 | CR | Approval | 23.501 CR3256R4 (Rel-17, 'F'): UE onboarding architecture | [Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo, Motorola Mobility, Huawei],Intel | Rel-17 | Revision of (Agreed) S2-2108095 from S2#147E. CC#2: Postponed | Peter (Ericsson) provides a questions and a comment Qianghua (Huawei) provides comments Rainer (Nokia) comments. Megha (Intel) provides r01 and comments Rainer (Nokia) asks for clarification. Peter Hedman (Ericsson) prefers that there is an understanding of how the changes works before accepting them. Qianghua (Huawei) replies Hualin(Huawei) provide comments. Rainer (Nokia) replies. Saso (Intel) replies. Haris(Qualcomm) comments Haris(Qualcomm) provides r02 Saso (Intel) comments on r02 Rainer (Nokia) cannot accept r02. Haris(Qualcomm) asks question on the SA3 agreement Peter Hedman (Ericsson) provides comments and propose to add the questions raised here to the LS to SA3 Hualin(Huawei) is confused and comments. Megha (Intel) provides r03 and comments Peter Hedman (Ericsson) provides question Megha (Intel) provides further comments ==== Revisions Deadline ==== Haris(Qualcomm) objects to this CR (all revisions inc the one I provided) Saso (Intel) points out that Haris's (Qualcomm) comment is misleading. Proposes to approve r03. Peter Hedman (Ericsson) provides comments and propose to postpone the CR and mark that SA2 alignment with SA3 is to be done at the next SA2 meeting Haris(Qualcomm) reiterates objection Saso (Intel) replies to Peter Hedman (Ericsson) and Haris (Qualcomm); reiterates to approved r03 based on the provided clarifications. Megha (Intel) requests to mark this document for CC#2. ==== Comments Deadline ==== Haris(Qualcomm) suggests revision to be discussed in CC#2 | Postponed |
| 8.2 | S2-2108918 | DISCUSSION | Approval | Support of 5G ProSe in PNI NPNs. | Huawei, HiSilicon | Rel-17 | Noted | Josep (DT) asks questions for clarification. Marco (Huawei) answers to Josep (DT) Peter Hedman (Ericsson) provides comments Josep (DT) comments. Haris(Qualcomm) comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.2 | S2-2109020 | LS In | Action | LS from SA WG3: LS on conclusions of authentication methods for initial access for onboarding. | SA WG3 (S3-214334) | Rel-17 | Postponed | Postponed | |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=52 | - | |
| 8.3 | - | - | - | General | - | - | Docs:=3 | - | |
| 8.3 | S2-2108294 | LS In | Information | LS from SA WG6: Reply LS on the definition of EAS and EAS context | SA WG6 (S6-212391) | Rel-17 | Noted | Dario S. Tonesi (Qualcomm) suggests to note this LS. Hui (Huawei) support to note this LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108719 | CR | Approval | 23.548 CR0018R2 (Rel-17, 'F'): Mega CR for minor fixes to TS 23.548 | Huawei (Rapporteur) | Rel-17 | Revision of (Agreed) S2-2108108 from S2#147E. r01 agreed. Revised to S2-2109265. | Hui (Huawei) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109265 | CR | Approval | 23.548 CR0018R3 (Rel-17, 'F'): Mega CR for minor fixes to TS 23.548 | Huawei (Rapporteur) | Rel-17 | Revision of S2-2108719r01. Approved | Agreed | |
| 8.3 | - | - | - | EAS discovery | - | - | Docs:=16 | - | |
| 8.3 | S2-2108408 | CR | Approval | 23.548 CR0001R2 (Rel-17, 'F'): Correction related to uniqueness of Update related to a buffered DNS message in EASDF | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Endorsed) S2-2108111 from S2#147E. r02 agreed. Revised to S2-2109266. | Xinpeng(Huawei) provides r02. Tingfang Tang (Lenovo) provides r01. ==== Revisions Deadline ==== Tingfang Tang (Lenovo) is OK with r01, r02, object r00. Magnus H (Ericsson) we are ok with r02 as proposed by chairman ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109266 | CR | Approval | 23.548 CR0001R3 (Rel-17, 'F'): Correction related to uniqueness of Update related to a buffered DNS message in EASDF | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108408r02. Approved | Agreed | |
| 8.3 | S2-2108422 | CR | Approval | 23.548 CR0017R2 (Rel-17, 'F'): Updates on EAS Discovery Procedure with EASDF | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Ericsson, Tencent, Samsung, China Mobile, | Rel-17 | Revision of (Agreed) S2-2108116 from S2#147E. CC#2: r05 + changes agreed. Revised to S2-2109267, merging S2-2108621 | Magnus H (Ericsson) provides r01 Dan(China Mobile) provides r02 Xinpeng(Huawei) provides r03. Magnus H (Ericsson) comments Dan (China Mobile) ask a question Tingfang Tang (Lenovo) replies and provides r04 Magnus H (Ericsson) provides r05 ==== Revisions Deadline ==== Dan(China Mobile) is OK with r05 Xinpeng(Huawei) agrees with r05. Laurent (Nokia): we shall remove the 5th change in the final version Dan(China Mobile) request Laurent to maybe provide the exact part which we should correct Magnus H (Ericsson) agrees with r05, but the indicated deletion under 5th change of clause 6.2.3.4.1 is not to be done. We see this as an editorial cleanup of the CR since CR has an updated part of 6.2.3.4.1 under second change Xinpeng(Huawei) based on r05, suggests to change 'External Group Identifier' to 'External Group Identifier/Internal Group Identifier' in Table 6.2.3.4-1 Description of EAS Deployment Information. Dan(China Mobile) understand the meaning of the 5th change now, the 6.2.3.4 and 6.2.3.4.1 will not be shown in the CR to avoid the misunderstanding in final version. Also request to change 'External Group Identifier' to 'External Group Identifier/Internal Group Identifier' in Table 6.2.3.4-1 .If needed we can do this in CC#2. Just small correction. ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109267 | CR | Approval | 23.548 CR0017R4 (Rel-17, 'F'): Updates on EAS Discovery Procedure with EASDF | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Ericsson, Tencent, Samsung, China Mobile, | Rel-17 | CC#2: Revision of S2-2108422r05 + changes, merging S2-2108621. Approved | Agreed | |
| 8.3 | S2-2108621 | CR | Approval | 23.548 CR0017R3 (Rel-17, 'F'): Updates on EAS Discovery Procedure with EASDF | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Ericsson, Tencent, Samsung | Rel-17 | Revision of (Agreed) S2-2108116 from S2#147E. Merged into S2-2109267 | Hui (Huawei) suggests to merge this paper to S2-2108422. Laurent (Nokia): suggests merging 8422 and 8621 that are revisions of the same CR from last meeting. ==== Revisions Deadline ==== Xinpeng(Huawei) confirms 8621 is merged into 8422. ==== Comments Deadline ==== | Merged |
| 8.3 | S2-2108622 | CR | Approval | 23.501 CR3299R2 (Rel-17, 'F'): 501 EASDF Service correction | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2108118 from S2#147E. Approved | Agreed | |
| 8.3 | S2-2108790 | CR | Approval | 23.502 CR3185R2 (Rel-17, 'F'): Update Nnef_EASDeployment services | Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Ericsson, CATT, Lenovo, Motorola Mobility, China Mobile | Rel-17 | Revision of (Agreed) S2-2108119 from S2#147E. CC#2: r03 + changes agreed. Revised to S2-2109268. | Laurent (Nokia): provides r01 Xinpeng(Huawei) provides r02. Magnus H (Ericsson) provides r03 ==== Revisions Deadline ==== Dan (China Mobile) is OK with r03 Xinpeng(Huawei) only agrees with r03, and not ok for any other revisions. Laurent (Nokia): I have a slight concern with R02 and R03 (removal of EAS Deployment Information reference) Xinpeng(Huawei) replies to Laurent(Nokia). Magnus H (Ericsson) comments Xinpeng(Huawei) provides comments. Magnus H (Ericsson) update previous comment Xinpeng(Huawei) replies. Tingfang Tang (Lenovo) asks question about r02 and r03 about EAS Deployment Information reference . Magnus H (Ericsson) answers Tingfang (Lenovo) Dan (China Mobile) request this for CC#2 with updating 5.2.6.26.4 by moving 'S-NSSAI, DNN' from input optional to input required. Xinpeng(Huawei) replies to Magnus H (Ericsson). Xinpeng(Huawei) provides further comments. Tingfang Tang (Lenovo) comments . Laurent (Nokia): Comments. I have reached my goal, the Tdoc needs a small update Dan(China Mobile) provide an update summary Magnus H (Ericsson) concludes that we are still discussing and that it would be best if CR is postponed to next meeting ==== Comments Deadline ==== Dan(China Mobile) do not agree to postpond this paper, and I would like to point it, your discussion is not related with what we want to do for group level EDI,postpond this paper the original cr will be sent to SA plenary as well. Laurent (Nokia): suggests we approve 8790r03 with SA2 meeting notes that tell that work on the EDI API parameters (e.g. which parameters are Mandatory and which optional ) may take place at next meeting | Revised |
| 8.3 | S2-2109268 | CR | Approval | 23.502 CR3185R3 (Rel-17, 'F'): Update Nnef_EASDeployment services | Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Ericsson, CATT, Lenovo, Motorola Mobility, China Mobile | Rel-17 | CC#2: Revision of S2-2108790r03 + changes. Approved | Agreed | |
| 8.3 | S2-2108978 | CR | Approval | 23.502 CR3313 (Rel-17, 'F'): Corrections to AF Requests and Notification Procedures | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Tingfang Tang (Lenovo) provides r01. Shubhranshu (Nokia) provides r02 Tingfang Tang (Lenovo) replies to Shubhranshu. Shubhranshu (Nokia) provides r03 ==== Revisions Deadline ==== Hui (Huawei) fine with r03 Magnus H (Ericsson) objects to all revisions except r01 Tingfang Tang (Lenovo) objects r02, accepts r01, can live with r03. Shubhranshu (Nokia) proposes to agree r03 ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108409 | CR | Approval | 23.548 CR0036 (Rel-17, 'F'): Improvements and correction to annex C | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm incorporated | Rel-17 | r06 agreed. Revised to S2-2109269. | Hui (Huawei) provides r01. Dario (Qualcomm) asks question on r01 Changhong (Intel) comments. Tingfang Tang (Lenovo) provides r02. Magnus H (Ericsson) comments Hui (Huawei) replies to Dario Magnus H (Ericsson) provides r03 Changhong (Intel) provides r04 Hui (Huawei) supports r04 Dario (Qualcomm) provides r05 Magnus H (Ericsson) provides r06 ==== Revisions Deadline ==== Dario (Qualcomm) is OK with r06 ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109269 | CR | Approval | 23.548 CR0036R1 (Rel-17, 'F'): Improvements and correction to annex C | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm incorporated | Rel-17 | Revision of S2-2108409r06. Approved | Agreed | |
| 8.3 | S2-2108411 | CR | Approval | 23.548 CR0005R1 (Rel-17, 'F'): Not all EC scenarios requires EASDF | Ericsson | Rel-17 | Revision of (unhandled) S2-2107239 from S2#147E. Approved | Agreed | |
| 8.3 | S2-2108508 | CR | Approval | 23.548 CR0038 (Rel-17, 'F'): Change of DNS server address during EPC IWK | Samsung | Rel-17 | r02 agreed. Revised to S2-2109270. | Dario S. Tonesi (Qualcomm) asks question Jicheol answers to the question of Dario (Qualcomm). Magnus H (Ericsson) ask questions Hui (Huawei) provide comments Changhong (Intel) comments. Jicheol explains the scenario. Jicheol comment. Hui (Huawei) provides r01. Jicheol (Samsung) is okay with r01. Dario (Qualcomm) provides r02 ==== Revisions Deadline ==== Jicheol (Samsung) is okay with r02. ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109270 | CR | Approval | 23.548 CR0038R1 (Rel-17, 'F'): Change of DNS server address during EPC IWK | Samsung | Rel-17 | Revision of S2-2108508r02. Approved | Agreed | |
| 8.3 | S2-2108511 | CR | Approval | 23.548 CR0039 (Rel-17, 'F'): Alignment of EASDF functional description | Samsung | Rel-17 | r05 agreed. Revised to S2-2109271. | Hui (Huawei) asks for clarification Xinpeng(Huawei) Provides r01. Magnus H (Ericsson) provides r02 Xinpeng(Huawei) ask for clarification. Magnus H (Ericsson) comments Dario (Qualcomm) provides r04 and asks to ignore r03. Xinpeng(Huawei) provides r05. Hui(Huawei) provides r06. ==== Revisions Deadline ==== Xinpeng(Huawei) only agrees with r05, and objects to any other revisions. Magnus H (Ericsson) r05 is OK ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109271 | CR | Approval | 23.548 CR0039R1 (Rel-17, 'F'): Alignment of EASDF functional description | Samsung | Rel-17 | Revision of S2-2108511r05. Approved | Agreed | |
| 8.3 | - | - | - | Usage of MNO DNS related | - | - | Docs:=13 | - | |
| 8.3 | S2-2108775 | CR | Approval | 23.548 CR0030R2 (Rel-17, 'C'): EAS rediscovery: Edge DNS Client based EAS (re-)discovery | Qualcomm Incorporated, Vodafone, Deutsche Telekom, Telefonica, Verizon, NTT DoCoMo, Telecom Italia, AT&T, Charter, Telstra, KDDI, Matrixx, Convida Wireless, InterDigital, T-Mobile USA, Rogers, Facebook, Orange, Rakuten Mobile, KPN, TNO, Ericsson, China Mo | Rel-17 | Revision of (Endorsed) S2-2108177 from S2#147E. CC#2: r33 agreed. Revised to S2-2109347, merging S2-2108865 | Hui (Huawei) suggests to take this paper to discuss basic EDC solution. Hui (Huawei) provides r01 based on offline discussion. Dario (Qualcomm) provides r02 Riccardo (NTT DOCOMO) provides r02. Saso (Intel) comments on r03. Dario (Qualcomm) comments on r03 Hui(Huawei) provides summary for further discussion Zhuoyun (Tencent) comments. Riccardo (NTT DOCOMO) replies on r03. Tingfang Tang (Lenovo) provides r04 and r05. Saso (Intel) replies to Riccardo. Riccardo (NTT DOCOMO) replies to Saso. Huazhang (vivo) ask a question. Riccardo (NTT DOCOMO) replies to Huazhang and Saso. Sudeep (Apple) provides r07. Saso (Intel) comments that r04 and r06/r07 are two competing proposals. Dario (Qualcomm) comments and provide r08. Hui (Huawei) provides r10 based on r08. Dario (Qualcomm) provides r11 Zhuoyun (Tencent) provides r12. Huazhang (vivo) provides r13 based on r12 and merge the content from paper 8547 Hui (Huawei) comments to r11 Hui (Huawei) asks question to Zhuoyun. Zhuoyun (Tencent) replies to Hui. Hui (Huawei) replies to Zhuoyun. Riccardo (NTT DOCOMO) is fine with r11 and does not like r12/r13. Yang (OPPO) support Tencent's comment and ask question to Huawei. Huazhang (vivo) provide r14 based on r11 Hui(Huawei) responses and proposes a way forward. Yang (OPPO) further comments. Susana (Vodafone) comments and provides r15 on the top of r11. Yang (OPPO) uploads r17 removing 'force' indication. Sudeep (Apple) comments on r15. Huazhang (vivo) don't accept to remove the UE capability of support EDC in this paper Riccardo (NTT DOCOMO) comments on Hui's proposed way forward Svante (Sony) comments on r15 Huazhang (vivo) provides r19 based on r10, to add the EDC function is a UE capability Josep (DT) asks for clarification whether r18, r19 are unclaimed, proposes wording for NOTE 4. Hui (Huawei) provides r20 Susana (Vodafone) replies to Svante and Sudeep Dario (Qualcomm) provides r22 and r23 Hui(Huawei) suggests to continue the discussion using r20. Zhuoyun (Tencent) provides r24. Tingfang Tang (Lenovo) comments and provides r25. Huazhang (vivo) provides r26 to combine 22,23 and 20, and move forward, r26 is a minimum sets of our agreements in EDC to end this long long discussions. but R24 is also ok to me. I didn't find r25 in email. Zhuoyun (Tencent) provides r28. Dario (Qualcomm) provides r29 ==== Revisions Deadline ==== Yang (OPPO) doubt the value of voting in CC until the technical concern can be resolved. Object r29 and any version including 'force' indication Hui(Huawei) provides draft r30v1 for discussion. Zhuoyun (Tencent) objects all the versions with introducing the feature of forcing the EDC usage for all the applications within certain PDU session. We prefer r12, is also fine with r04, r16, r17, r24, r26, r28, and object other versions. Riccardo (NTT DOCOMO) prefers r23 and can accept r29/r30. Objects: r12, r13, r16, r17, r24, r26, r28. Sudeep (Apple) comments on draftr30v1. Huazhang (vivo) can only accept r14, objects any version. But Huazhang can live with r26 r28 r29 and r30 add this sentence: A UE that hosts EDC function may indicate this UE capability in the PCO during the PDU session establishment procedure that the 5GC determines the DNS query triggered in this PDU session is guaranteed to be sent to DNS server indicated by MNO. And the EDC functionality includes the following functionalities: XXXXX Xiaobo Yu (Alibaba) can live with r12 and objects to any other revision. Dario (Qualcomm) provides r31 for discussion in CC#2 Yang (OPPO) comments. Dario (Qualcomm) provides r31b to be used with r31 in CC#2. Svante (Sony) provide additional comments and accept r31b, r28 and r24. We object to r29, r26, r23, r22 and all other versions there the UE enforce that the application uses the EDC. ==== Comments Deadline ==== Xiaobo Yu (Alibaba) provides r31c base on the r31 for CC#2. Yang (OPPO) provides 31d and responds to Xiaobo and Riccardo. Riccardo (NTT DOCOMO) is positive on r31c. Susana (Vodafone) can live with r31c Hui (Huawei) thanks Xiaobo and Yang for the compromise proposal and asks whether we can go with r31c. Jinhua(Xiaomi) agree with Yang, we prefer 8775r31d, Both 8775r31d and 8775r31c are OK for us. Zhuoyun (Tencent) prefers r31d, can also go with r31c. Sudeep (Apple) comments on r31c. Huazhang (vivo) prefers r31d, can also go with r31c to finally solve the EDC issues in this year Svante (Sony) Thanks for the compromised versions. We accepts the r31c version to be able to move forward. Yang (OPPO) thanks for people's work and can live with r33. | Revised |
| 8.3 | S2-2109347 | CR | Approval | 23.548 CR0030R4 (Rel-17, 'C'): EAS rediscovery: Edge DNS Client based EAS (re-)discovery | Qualcomm Incorporated, Vodafone, Deutsche Telekom, Telefonica, Verizon, NTT DoCoMo, Telecom Italia, AT&T, Charter, Telstra, KDDI, Matrixx, Convida Wireless, InterDigital, T-Mobile USA, Rogers, Facebook, Orange, Rakuten Mobile, KPN, TNO, Ericsson, China Mobile, Nokia, Nokia Shanghai Bell, Reliance Jio, China Unicom, Huawei, HiSilicon, NEC, Sandvine, Amdocs, SK Telekom, Xiaomi | Rel-17 | CC#2: Revision of S2-2108775r33, merging S2-2108865. Approved | Agreed | |
| 8.3 | S2-2108694 | DISCUSSION | Agreement | Way forward for criteria to use the EDC functionality | NTT DOCOMO | Rel-17 | Noted | Dario S. Tonesi (Qualcomm) comments Riccardo (NTT DOCOMO) clarifies this is a DP. Dario (Qualcomm) thanks Riccardo and withdraws his previous comment. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108865 | CR | Approval | 23.548 CR0030R3 (Rel-17, 'C'): EAS rediscovery: Edge DNS Client based EAS (re-)discovery | NTT DOCOMO | Rel-17 | Revision of (Endorsed) S2-2108177 from S2#147E Merged into S2-2109347 | Hui (Huawei) suggests to consider this paper as merged into S2-2108775.. Riccardo (NTT DOCOMO) is fine to merge this tdoc into S2-2108775. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.3 | S2-2108776 | DISCUSSION | Endorsement | Considerations on trigger conditions for EDC usage. | Qualcomm Incorporated | Rel-17 | Noted | Hui (Huawei) proposes to note this discussion paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108777 | CR | Approval | 23.548 CR0031R2 (Rel-17, 'F'): UE authorization for 5GC assisted EAS discovery | Qualcomm Incorporated, Vodafone, Telstra, NTT DoCoMo, Deutsche Telekom, T-Mobile USA, AT&T, Verizon, Orange, Matrixx, Rakuten Mobile, KPN, TNO, China Mobile, Amdocs | Rel-17 | Revision of (Endorsed) S2-2108110 from S2#147E. r03 agreed. Revised to S2-2109272. | Tingfang Tang (Lenovo) provides r01. Magnus O (Ericsson) comments Dario (Qualcomm) provides r02 to address Magnus' comments. Sudeep (Apple) comments on r02. Magnus O (Ericsson) provides r03 Dario (Qualcomm) is OK with r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109272 | CR | Approval | 23.548 CR0031R3 (Rel-17, 'F'): UE authorization for 5GC assisted EAS discovery | Qualcomm Incorporated, Vodafone, Telstra, NTT DoCoMo, Deutsche Telekom, T-Mobile USA, AT&T, Verizon, Orange, Matrixx, Rakuten Mobile, KPN, TNO, China Mobile, Amdocs | Rel-17 | Revision of S2-2108777r03. Approved | Agreed | |
| 8.3 | S2-2108547 | CR | Approval | 23.548 CR0041 (Rel-17, 'F'): A new UE capability to support EDC | Vivo | Rel-17 | Noted | Dario S. Tonesi (Qualcomm) comments Huazhang (vivo) reply to Dario(QC) Dario (Qualcomm) replies to Huazhang. Huazhang (vivo) replies to Dario that the content of this paper has been reflected in 8775r13 ==== Revisions Deadline ==== Dario (Qualcomm) objects this CR Huazhang (vivo) merge this CR to S2-2108775 that the UE capability has been written in 8775 ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108548 | CR | Approval | 23.502 CR3254 (Rel-17, 'F'): A new UE capability to support EDC | Vivo | Rel-17 | Noted | Dario S. Tonesi (Qualcomm) think that, as for 8547, 8548 is not needed. Huazhang (vivo) replys to Dario and provide r01 ==== Revisions Deadline ==== Dario (Qualcomm) objects to r00 and r01 ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108506 | CR | Approval | 23.548 CR0037 (Rel-17, 'F'): EAS re-discovery indication and its procedure performed by EDC | Samsung | Rel-17 | Noted | Dario S. Tonesi (Qualcomm) comments Jicheol (Samsung) comments Tingfang Tang (Lenovo) comments. Susana (Vodafone) agrees with Lenovo and Qualcomm that nothing needs to be added. Proposal to note this document Dario (Qualcomm) supports to note this paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108544 | CR | Approval | 23.548 CR0020R1 (Rel-17, 'B'): Provision of DNS server IP address to applications independent of UE OS capability | Vivo | Rel-17 | Revision of (Postponed) S2-2107537 from S2#147E. Noted | Dario S. Tonesi (Qualcomm) asks questions for clarification. Huazhang (vivo) response to Dario and provide r01 Magnus H (Ericsson) comments: Not comfortable with cat B CR at this point in time Huazhang (vivo) clarify the reason to Magnus(Ericsson) Dario (Qualcomm) asks an additional question Huazhang (vivo) reply to Dario and provide r02 Changhong (Intel) comments. Huazhang (vivo) replys to Changhong Huazhang (vivo) reply to Magnus and provide r03, put the details to Annex, I don't want to put forward such new features Huazhang (vivo) provides r04 ==== Revisions Deadline ==== Dario (Qualcomm): all revisions (including r0) have problems and that he cannot be accepted. Magnus H (Ericsson) objects to this CR ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108971 | LS OUT | Approval | [DRAFT] LS on Defining test cases for E2E verification of Edge Application Server Discovery | Apple | r00 agreed. Revised to S2-2109255. | Revised | ||
| 8.3 | S2-2109255 | LS OUT | Approval | Defining test cases for E2E verification of Edge Application Server Discovery | SA WG2 | - | Revision of S2-2108971r00. Approved | Approved | |
| 8.3 | - | - | - | Edge Relocation | - | - | Docs:=6 | - | |
| 8.3 | S2-2108311 | CR | Approval | 23.548 CR0035 (Rel-17, 'F'): Corrections on enabling EAS IP Replacement procedure by AF | China Unicom | Rel-17 | r02 agreed. Revised to S2-2109273. | Changhong (Intel) provides r01 and cosigns. Shubhranshu (Nokia) comments Tianqi (China Unicom) provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109273 | CR | Approval | 23.548 CR0035R1 (Rel-17, 'F'): Corrections on enabling EAS IP Replacement procedure by AF | China Unicom, Intel | Rel-17 | Revision of S2-2108311r02. Approved | Agreed | |
| 8.3 | S2-2108351 | CR | Approval | 23.501 CR3363 (Rel-17, 'F'): Additional information/parameter for AF Influence request | Oracle | Rel-17 | Noted | Shubhranshu (Nokia) asks for clarifications Tingfang Tang (Lenovo) asks questions. Changhong (Intel) comments. Magnus H (Ericsson) comments Hui (Huawei) comments Tingfang Tang (Lenovo) comments. ==== Revisions Deadline ==== Changhong (Intel) has concern with this paper. Shubhranshu (Nokia) also has concerns and do not agree to this CR Changhong (Intel) also proposes to NOTE the CR, we need more time to think about it. ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108410 | CR | Approval | 23.548 CR0006R1 (Rel-17, 'F'): Correction related to AF request for simultaneous connectivity over source and target PSA at edge relocation | Ericsson | Rel-17 | Revision of (Noted) S2-2107240 from S2#147E. Noted | Dario S. Tonesi (Qualcomm) asks question for clarification Changhong (Intel) comments. Dan (China Mobile) support Changhong's comments. Magnus H (Ericsson) provides r01 Susana (Vodafone) asks question for clarification Hui (Huawei) don't think we need this CR. Magnus H (Ericsson) comments Hui (Huawei) provides further comments and proposes to note the paper. Magnus H (Ericsson) comment and proposes not to note this paper. Hui (Huawei) replies. ==== Revisions Deadline ==== Magnus H (Ericsson) replies to Hui Hui (Huawei) replies to Magnus ==== Comments Deadline ==== | Noted |
| 8.3 | S2-2108545 | CR | Approval | 23.548 CR0040 (Rel-17, 'F'): Added the situation of AF relocation to uplink Packet Buffer | Vivo, NTT DOCOMO | Rel-17 | r03 agreed. Revised to S2-2109274. | Shubhranshu (Nokia) asks for clarifications Huazhang (vivo) reply to Shubhranshu and provides r01 Magnus O (Ericsson) comments Huazhang (vivo) provide r02 and response to Magnus Shubhranshu (Nokia) provides r03 Huazhang(vivo) reply to Shubhranshu (Nokia) r03 is ok ==== Revisions Deadline ==== Huazhang(vivo) is ok to go ahead with r03 Magnus O (Ericsson) is ok with r03 ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109274 | CR | Approval | 23.548 CR0040R1 (Rel-17, 'F'): Added the situation of AF relocation to uplink Packet Buffer | Vivo, NTT DOCOMO | Rel-17 | Revision of S2-2108545r03. Approved | Agreed | |
| 8.3 | - | - | - | Local Exposure | - | - | Docs:=6 | - | |
| 8.3 | S2-2108549 | DISCUSSION | Information | Unclear issues in local NEF discovery and way forward | vivo | Rel-17 | Noted | Noted | |
| 8.3 | S2-2108546 | CR | Approval | 23.548 CR0022R1 (Rel-17, 'F'): Local NEF selection | Vivo | Rel-17 | Revision of (Noted) S2-2107539 from S2#147E. Merged into S2-2109348 | Haiyang (Huawei) suggests to use S2-2108675 as baseline (i.e. mark this paper merged into 8675 or noted) Laurent (Nokia): suggests to take this paper 8546 as the baseline Laurent (Nokia): provides r01 Magnus H (Ericsson) provides r02 Haiyang (Huawei) suggests to note this CR (all revisions) Huazhang (vivo) replys to Haiyang, and could you please clarify the technique reason of why you don't like the procedure Yang (OPPO) consider the procedure is needed Haiyang (Huawei) replies to Yang (OPPO) Laurent (Nokia): answers ==== Revisions Deadline ==== Huazhang (vivo) merge this paper to 8675, due to we will go ahead on 8675 of local NEF selection ==== Comments Deadline ==== | Merged |
| 8.3 | S2-2108675 | CR | Approval | 23.548 CR0042 (Rel-17, 'F'): Local NEF selection | China Mobile | Rel-17 | CC#2: r09 + changes agreed. Revised to S2-2109348, merging S2-2108546 and S2-2108858 | Haiyang (Huawei) provides r01. Laurent (Nokia): Comments and suggests to take either 8546 or 8858 as baseline for this topic Huazhang (vivo): Comments and suggests to take either 8546 or 8858 as baseline for this topic Dan (China Mobile)response Laurent (Nokia): answers, proposes to merge in this paper into 8546 (not mine) Dan(China Mobile)provide r02 Magnus H (Ericsson) provides r03 Haiyang (Huawei) can only accept r01. Huazhang (vivo) replys and provide r04 based on r03, move some of the content in 8546 into r04. Also, provides the unsolved things in local NEF selection, which we can't avoid and don't solve. Dan (China Mobile) provide r05 based on r01 Huazhang (vivo) provide r06 based on r05 Haiyang (Huawei) provides r07 based on r06 Huazhang (vivo) provides r08 based on r07 Laurent (Nokia): answers with concerns Haiyang (Huawei) provides r09 Laurent (Nokia): provides r11 and r12 Haiyang (Huawei) comments Dan(China Mobile) provide r13 based on r11 with changing internal/external to trust/untrust. Haiyang (Huawei) comments if it is trusted AF, there is no need for NEF at all based on current specs Laurent (Nokia): provides r14 Dan(China Mobile) provide r14 to reflect Haiyang's comment Dan(China Mobile) provide r15 to reflect Haiyang's comment Dan(China Mobile) provide r16 based on R14 laurent provide with some correction for AF Haiyang (Huawei) comments that even if the AF cannot provide DNAI, the NEF could get it based on local configuration. Dan (China Mobile) ask, Huazhang(vivo) provide r17 based on R16 as compromise Haiyang(Huawei) replies to Dan(China Mobile) ==== Revisions Deadline ==== Haiyang(Huawei) can only accept r01, r07 or r09, and objects to all other versions. Huazhang (vivo) propose we go with r09 because this topic has been discussed so long and no results, firstly we can reach some agreements in some area. Dan (China Mobile) OK we go with r09 Laurent (Nokia): objects to R00, R01, R03, R04, R05, R06, R07, R08, R09, R15 Magnus H (Ericsson) prefers r09 over the non objected revisions (r01 and r07). Dan (China Mobile) check all the versions, I would like to let people to check whether r14 is OK , we can accept r14 Dan (China Mobile) take it back the previous email, and suggest people to check r11. Huazhang (vivo) can accept r14 Magnus H (Ericsson) cannot accept r14, if we are not going with r09, r03 is proposed. Dan (China Mobile) would like to clarify something and suggest to endorse r09 Laurent (Nokia): We need to discuss this at CC2 Dan(China Mobile): agree that we should work together and in CC#2, with a suitable NOTE adding, maybe we can get consensus. ==== Comments Deadline ==== Huazhang (vivo): provides r18 based on r09 to move forward for the trigger of local NEF selection and AF request redirect. I delete all of the controversal parts to move ahead. Dan (China Mobile) suggest we can move forward based on Huazhang r18 | Revised |
| 8.3 | S2-2109348 | CR | Approval | 23.548 CR0042R1 (Rel-17, 'F'): Local NEF selection | China Mobile | Rel-17 | CC#2: Revision of S2-2108675r09 + changes, merging S2-2108546 and S2-2108858. Approved | Agreed | |
| 8.3 | S2-2108858 | CR | Approval | 23.548 CR0025R1 (Rel-17, 'F'): Procedure for local NEF selection | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2107646 from S2#147E. Merged into S2-2109348 | Haiyang (Huawei) suggests to use S2-2108675 as baseline (i.e. mark this paper merged into 8675 or noted) Laurent (Nokia): Suggests to take 8546 (not mine) as a baseline so merges 8858 into 8546 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.3 | S2-2108859 | CR | Approval | 23.502 CR3204R1 (Rel-17, 'F'): Procedure for local NEF selection | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2107647 from S2#147E. Noted | Haiyang (Huawei) suggests to note this paper. Magnus H (Ericsson) comments Laurent (Nokia): answers ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.3 | - | - | - | Service specific information provisioning | - | - | Docs:=3 | - | |
| 8.3 | S2-2108503 | CR | Approval | 23.502 CR3155R2 (Rel-17, 'B'): Correction of UE Policies delivery notification | Samsung | Rel-17 | Revision of (Agreed) S2-2108113 from S2#147E. r01 agreed. Revised to S2-2109275, merging S2-2108976 | Shubhranshu (Nokia) provides r01 Jicheol (Samsng) provide r02. Jicheol (Samsung) is okay with both r01 and r02. Shubhranshu (Nokia) is NOT ok to r02 and r00 ==== Revisions Deadline ==== Hui(Huawei) fine with r01 ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109275 | CR | Approval | 23.502 CR3155R4 (Rel-17, 'B'): Correction of UE Policies delivery notification | Samsung, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108503r01, merging S2-2108976. Approved | Agreed | |
| 8.3 | S2-2108976 | CR | Approval | 23.502 CR3155R3 (Rel-17, 'B'): Correction of UE Policies delivery notification | Nokia, Nokia Shanghai Bell, [Samsung?] | Rel-17 | Revision of (Agreed) S2-2108113 from S2#147E. Confirm Sources! Merged into S2-2109275 | Jicheol (Samsung) asks a question for clarification Jicheol (Samsung) also suggests to merge (or discuss) this CR in S2-2108503 since the proposal is conflicted. Shubhranshu (Nokia) responds Shubhranshu (Nokia) is ok to merge this paper into S2-2108503 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.3 | - | - | - | DNAI-based (I-)SMF selection | - | - | Docs:=4 | - | |
| 8.3 | S2-2108717 | CR | Approval | 23.502 CR3277 (Rel-17, 'F'): I-SMF removal triggered by removal of target DNAI | Huawei, HiSilicon | Rel-17 | CC#2: r04 + changes agreed. Revised to S2-2109276 | Tingfang Tang (Lenovo) provides r01. Shubhranshu (Nokia) comments and asks for clarifications Hui (Huawei) replies and prefers to r00. Tingfang Tang (Lenovo) comments. Yuan Tao (CATT) comments. Yuan Tao responds to Tingfang Tang (Lenovo). Hui(Huawei) supports Yuan's view. Tingfang Tang (Lenovo) replies and can accept the original version. Magnus O (Ericsson) comments Hui (Huawei) provides r02 Shubhranshu (Nokia) provides r03 Hui (Huawei) provides r04 Shubhranshu (Nokia) asks for clarification ==== Revisions Deadline ==== Hui (Huawei) replies. Yuan Tao (CATT) replies to Hui (Huawei). Yuan Tao (CATT) replies. Hui (Huawei) provides r05 and asks for discussing on CC#2. ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109276 | CR | Approval | 23.502 CR3277R1 (Rel-17, 'F'): I-SMF removal triggered by removal of target DNAI | Huawei, HiSilicon | Rel-17 | CC#2: Revision of S2-2108717r04 + changes. Approved | Agreed | |
| 8.3 | S2-2108718 | CR | Approval | 23.501 CR3418 (Rel-17, 'F'): I-SMF removal triggered by removal of target DNAI | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2109277. | Tingfang Tang (Lenovo) provides r01. Shubhranshu (Nokia) comments Hui (Huawei) still prefers to r00 and replies. Tingfang Tang (Lenovo) replies and can accept the original version. Magnus O (Ericsson) comments Hui (Huawei) replies to Magnus O (Ericsson) Shubhranshu (Nokia) provides r02 Hui (Huawei) fine with r02 Magnus O (Ericsson) comments again Hui (Huawei) provides r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.3 | S2-2109277 | CR | Approval | 23.501 CR3418R1 (Rel-17, 'F'): I-SMF removal triggered by removal of target DNAI | Huawei, HiSilicon | Rel-17 | Revision of S2-2108718r03. Approved | Agreed | |
| 8.3 | - | - | - | ECS provisioning | - | - | Docs:=1 | - | |
| 8.3 | S2-2108778 | CR | Approval | 23.502 CR3212R2 (Rel-17, 'F'): Correction of ECS Address Configuration Information | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of (Agreed) S2-2108120 from S2#147E. Approved | Agreed | |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=69 | - | |
| 8.4 | - | - | - | LS in/LS out | - | - | Docs:=22 | - | |
| 8.4 | S2-2108286 | LS In | Information | LS from CT WG4: Reply LS on back-off timer handling when NSSAA is not completed | CT WG4 (C4-215491) | Rel-17 | Noted | Jinguo(ZTE) suggest to note this LS since it is for information ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108789 | DISCUSSION | Agreement | Discussion on NSAC for Network Slice Subject to NSSAA. | Xiaomi | Noted | Alessio (Nokia) proposes to note this paper with no specific agreement reached other than the current text in the TS is enough ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 8.4 | S2-2108335 | LS OUT | Approval | [DRAFT] LS on order of NSSAA and NSAC procedure | Ericsson | Noted | Iskren (NEC) - the answer in the LS is in conflict with the SA2 spec. Peter Hedman (Ericsson) provides reply George (Ericsson) provides a comment to Iskren. The yellow text does not mandate whether NSAC is done before NSSAA or after. In this case, there is UCU and as such the yellow text does not apply; there is no Registration response with an Allowed S-NSSAI; where the highlighted yellow text applies . So U extending the interpretation. If what U are saying is true then we would not have received an LS asking clarification. Iskren (NEC) answers George George (Ericsson) comment. The yellow text does not cover the NSSAA. That's all I said. Otherwise why are CT groups seeking clarification. Iskren (NEC) answers George. George (Ericsson) comments. We agree to disagree. Alessio(Nokia) provides r01 George (Ericsson) comments. This LS is the right approach and we should stop this discussion. It is going nowhere. Jinhua(Xiaomi) comments. 8335r01 is OK for me, and we can revise the state in 502 e.g.'the AMF can be configured to trigger NSSAA before or after NSAC, when EAC active' , same as Peter's proposal. Iskren (NEC) - the original and r01 are not acceptable as they do not interpret correctly the order between the NSAC and NSSAA defined in the SA2 spec. ==== Revisions Deadline ==== Jinhua replies to Iskren, propose to state the order can be decided by AMF as the operator decision Peter Hedman (Ericsson) provides question why r00 is not acceptable by NEC, while we are fine with r01 as well as main purpose is to ask whether SA3 has any concerns as such Iskren (NEC) answers Peter Hedman (Ericsson) Tao(VC) then let's try to agree r00 with the condition 8886 r06 approved. George (Ericsson) comments . R06 can only be Ok with the changes Peter requested. That was clear alessio(nokia) can only agree r01 as the spec clearly says that NSAC does not happen till after UE configuration update when EAC is not active. ==== Comments Deadline ==== | Noted | |
| 8.4 | S2-2108786 | CR | Approval | 23.502 CR3178R1 (Rel-17, 'F'): TS23.502 Correction of NSAC for network slice subject to NSSAA | NEC(?), Ericsson(?), Xiaomi | Rel-17 | Revision of (Postponed) S2-2107427 from S2#147E. Confirm Sources! Noted | Peter (Ericsson) provides comments and r01 Iskren (NEC) - this CR shall be considered as merged to S2-2108886 Fenqin (Huawei) ask a question for clarification Ashok (Samsung) comments Jinhua (Xiaomi) proposes to merge 8786 into 8886 for further discussion. Jinhua(Xiaomi) replies to Ashok Fenqin and Peter, Fenqin (Huawei) responds alessio(nokia) requests to note this CR. Jinhua(Xiaomi) replies to Alessio, 8786 was merged into 8886 for further discussion. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108886 | CR | Approval | 23.502 CR3178R2 (Rel-17, 'F'): TS23.502 Correction of NSAC for network slice subject to NSSAA | NEC, Huawei, NTT DOCOMO | Rel-17 | Revision of (Postponed) S2-2107427 from S2#147E. Confirm CR Revision - CR states 1! Noted | Stefano (Qualcomm) provides r01 Jinhua (Xiaomi) provides comments, and proposes to merge 8786 into 8886 for further discussion. Peter (Ericsson) provides comments George (Ericsson) Just one additional comment. If the NSAC is done after UE configuration update and the slice was congested, then AMF would have to undo everything and we would have wasted radio resources. Iskren (NEC) answers question from George (Ericsson) Iskren (NEC) provides r02 George (Ericsson) comments. George (Ericsson) comments. We are not OK with r02. Jinhua (Xiaomi) provides r03. George (Ericsson) comments. This can't be a note. The note itself contradicts the normative text. So this is NOT OK either. Jinhua(Xiaomi) replies to George. Srisakul (NTT DOCOMO) asks question for clarification to George (Ericsson) and Jinhua (Xiaomi). George (Ericsson) respond. We would have it done after NSAC regardless, or leave it as implementation not an operator policy. This will work either way, and has no interworking impact. Fenqin (Huawei) comments. Jinhua(Xiaomi) respond to Srisakul for clarification. Peter Hedman (Ericsson) provides comment and a proposal Jinhua(Xiaomi) replies to Peter, Alessio(Nokia) proposes to note this CR Iskren (NEC) provides r04 Srisakul (NTT DOCOMO) comments. ==== Revisions Deadline ==== Iskren (NEC) can agree with r02 or r06 Peter Hedman (Ericsson) proposes to Approve r06 with additional changes i.e. removing the normative paragraph and change 'may' to 'can' in the added note. Iskren (NEC) answers Peter Hedman (Ericsson) and proposes to Approve r06 Alessio(nokia) proposes to note this CR as it is not providing any improvement and as noted by Peter it is quite confusing Jinhua(Xiaomi) proposes to approve r02/r06 for progress. ==== Comments Deadline ==== Peter Hedman (Ericsson) provides reply that approving only text in the note as normative text is ok | Noted |
| 8.4 | S2-2108287 | LS In | Action | LS from CT WG4: LS on Parameter adding in UEContext to support NSSRG feature | CT WG4 (C4-215492) | Rel-17 | Responses drafted in S2-2108643, S2-2108759 and S2-2108894. Final response in S2-2109142 | Replied to | |
| 8.4 | S2-2108643 | LS OUT | Approval | [DRAFT] LS Reply on Parameter adding in UEContext to support NSSRG feature | Huawei, HiSilicon | Rel-17 | Response to S2-2108287. r03 agreed. Revised to S2-2109142, merging S2-2108759 and S2-2108894 | Yunjing (CATT) proposes to merge this draft LS into S2-2108759. Haiyang (Huawei) is OK to merge and discuss it in the 8759 thread. Ashok (Samsung) comments Peter (Ericsson) provides comments and r01 Haiyang (Huawei) is OK with r01 Ashok (Samsung) is fine with r01 alessio (nokia) provides r02 to restrict the question to rel-17 parameters only Jinhua (Xiaomi) provides comments and r03 Haiyang (Huawei) prefers r01 ==== Revisions Deadline ==== Peter Hedman (Ericsson) prefer r01, but can live with r03 as well. alessio (Nokia) can accept r02 and r03. ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109142 | LS OUT | Approval | LS Reply on Parameter adding in UEContext to support NSSRG feature | SA WG2 | Rel-17 | Revision of S2-2108643r03, merging S2-2108759 and S2-2108894. Approved | Approved | |
| 8.4 | S2-2108759 | LS OUT | Approval | [DRAFT] Response LS on parameter adding in UEContext to support NSSRG feature | CATT | Rel-17 | Response to S2-2108287. Merged into S2-2109142 | Peter (Ericsson) provides comments and suggest to mark as merged into S2-2108643 Yunjing (CATT) is fine to merge this paper into S2-2108643 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.4 | S2-2108894 | LS OUT | Approval | [DRAFT] Reply LS on Parameter adding in UEContext to support NSSRG feature | China Mobile | Rel-17 | Response to S2-2108287. Merged into S2-2109142 | Yunjing (CATT) proposes to merge this draft LS into S2-2108759. Dan (China Mobile) is OK for merging this paper into S2-2108759. Peter (Ericsson) provides comments and suggest to mark it merged into S2-2108643 ==== Revisions Deadline ==== Dan(China Mobile) OK to mark it merged into S2-2108643 ==== Comments Deadline ==== | Merged |
| 8.4 | S2-2108758 | CR | Approval | 23.502 CR3285 (Rel-17, 'F'): Update UE context transferred between AMFs | CATT | Rel-17 | Noted | Peter (Ericsson) provides comments and propose to mark it as merged into S2-2108895. Yunjing (CATT) is fine to merge this CR into S2-2108895. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108895 | CR | Approval | 23.502 CR3304 (Rel-17, 'F'): Correct the UDM indication and RFSP index in UE Context in AMF table | China Mobile | Rel-17 | r01 agreed. Revised to S2-2109143. | Yunjing (CATT) proposes to merge this CR into S2-2108758. Peter (Ericsson) provides comments and r01 Dan (China Mobile) provides r02 Alessio(Nokia) is ok with r02 ==== Revisions Deadline ==== Dan(China Mobile) is ok with r02 Haiyang (Huawei) prefers r01, objects r02 Ashok (Samsung) agrees with Haiyang (Huawei) and prefers r01, objects r02 Dan (China Mobile) OK with r01, and r02, but give a suggestion. Peter Hedman (Ericsson) ok with any of r01 and r02. alessio(Nokia) prefers r02. can live with r01 ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109143 | CR | Approval | 23.502 CR3304R1 (Rel-17, 'F'): Correct the UDM indication and RFSP index in UE Context in AMF table | China Mobile, Ericsson | Rel-17 | Revision of S2-2108895r01. Approved | Agreed | |
| 8.4 | S2-2108262 | LS In | Action | LS from CT WG1: LS on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | CT WG1 (C1-214895) | Rel-17 | Revision of S2-2107020 from S2#147E. Responses drafted in S2-2108607, S2-2108762, S2-2108806 and S2-2108958. Final response in S2-2109364 | Replied to | |
| 8.4 | S2-2108763 | DISCUSSION | Agreement | Discussion on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs. | Huawei, HiSilicon | Rel-17 | Noted | Noted | |
| 8.4 | S2-2108607 | LS OUT | Approval | [DRAFT] LS Reply on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | ZTE | Rel-17 | Response to S2-2108262. Noted | Haiyang (Huawei) provides comments. alessio(Nokia) proposes to note this LS as it is mandating a behavior in the CN that is not something that should happen by default. Jinguo(ZTE) provides r01. alessio (nokia) repeats we need to take a holistic decision for all the features and not one that works for NSAC and not for others...hence we proposed a generic CR and LS response. Jinguo(ZTE) replies no agreement that this is a generic issue for other cause value in both SA2 and CT1. alessio(Nokia) also believes the way this is worded is wrong. objects to this LS text. Jinguo(ZTE) provides r02 ==== Revisions Deadline ==== Stefano (Qualcomm) does not see how we can agree R02. Tao(VC) check the way forward of the LS OUT, whether 8806 can be approved Jinguo(ZTE) suggest to go with 8607r02 Haiyang (Huawei) suggests to postpone this LS as discussed in 8608 thread.(i.e. objects to r00, r01 and r02) alessio(nokia) objects to r00, r01 and r02 Stefano (Qualcomm) thanks Jinguo for the effort but clearly 8607 (and the related CR) cannot be agreed any more than 8806 and the related CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108762 | LS OUT | Approval | [DRAFT] LS Reply on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | Huawei, HiSilicon | Rel-17 | Response to S2-2108262. Noted | Peter (Ericsson) provides comments and question the proposed way forward proposed. Haiyang (Huawei) replies to Peter (Ericsson). Stefano (Qualcomm) expresses concerns about underlying assumptions. Haiyang (Huawei) explains the original assumption should be the Allowed NSSAI should be valid in the whole RA. Peter Hedman (Ericsson) provides comments and still have issues with the LS proposal. Haiyang (Huawei) seeks clarification from Peter Hedman (Ericsson). Alessio(Nokia) suggest we use the Nokia LS and CR approach as the discussion has generic validity. We do not want to have a behaviour that is specific for each feature. ==== Revisions Deadline ==== Haiyang (Huawei) suggests to go with the original version. Jinguo(ZTE) suggest to merge this LS into 8607 ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108806 | LS OUT | Approval | [DRAFT] LS Reply on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2108262. CC#2: This was left for review at CC#3. CC#3: r02 agreed. Revised to S2-2109364 | Jinguo(ZTE) suggests merge 8806 into 8607 Peter Hedman (Ericsson) propose to mark the LS as noted alessio(Nokia) can only accepted the text in the formally agreed LS OUT ( without referring to the CR, we can remove the CR reference if the text in there is agreable). if despite this was approved people object to it, we put on hold any LS on this. Alessio(nokia) comments that this LS was not receiving any comment so it is agreed per process technically. we can remove any reference to the CR but the technical content seems not challenged. I can work on an update text removing the CR reference and focus on the feedback in bullets 1 AND 2. Jinguo(ZTE) asks discussion at CC#2 ==== Comments Deadline ==== Alessio( Nokia) provides a modified text that keeps the 'agreed' concepts but removes reference to a CR. add the text as proposed by peter. Asks Jinguo(ZTE) and TAO to insist in obtaining discussion at CC#2 | Revised |
| 8.4 | S2-2109364 | LS OUT | Approval | LS Reply on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | SA WG2 | Rel-17 | Revision of S2-2108806r02. Approved | Approved | |
| 8.4 | S2-2108958 | LS OUT | Approval | [DRAFT] LS Reply on rejected NSSAI for the maximum number of UE reached when TAIs belonging to different PLMNs | QUALCOMM Europe Inc. - Italy | Rel-17 | Response to S2-2108262. Noted | Haiyang (Huawei) suggests to note this paper. Peter Hedman (Ericsson) provides reply. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108334 | CR | Approval | 23.502 CR3129R1 (Rel-17, 'F'): Rejected NSSAI for NSAC | Ericsson, Qualcomm | Rel-17 | Revision of (unhandled) S2-2107120 from S2#147E. Noted | Haiyang (Huawei) suggests to note this paper. Alessio(Nokia) also proposes to note this CR Peter Hedman (Ericsson) provides reply Alessio(Nokia) replies ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108608 | CR | Approval | 23.502 CR3261 (Rel-17, 'F'): Clarification on Equivalent PLMN for NSAC | ZTE | Rel-17 | Postponed | Peter (Ericsson) provides comments Haiyang (Huawei) provides comments. Jinguo(ZTE) provides response and asks question Jinguo(ZTE) provides r01 Peter Hedman (Ericsson) provides comments Jinguo (ZTE) response alessio(Nokia) objects to this CR Jinguo(ZTE) reply that the objection has no basis. Peter Hedman (Ericsson) provides comments and concerns on applying NSAC on each ePLMN as well as assuming there is some common NSAC quota Jinguo(ZTE) response Jinguo(ZTE) provides r02 Haiyang (Huawei) comments on r01 ==== Revisions Deadline ==== Jinguo(ZTE) replies to Haiyang. Haiyang(Huawei) questions to Jinguo(ZTE). Haiyang(Huawei) comments. Jinguo(ZTE) response. Haiyang(Huawei)also suggests to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 8.4 | - | - | - | General | - | - | Docs:=6 | - | |
| 8.4 | S2-2108605 | CR | Approval | 23.501 CR3401 (Rel-17, 'F'): Clarification on Multiple NSACFs for S-NSSAI | ZTE, NTT DOCOMO, Lenovo, Motorola Mobility | Rel-17 | r04 agreed. Revised to S2-2109144. | Genadi (Lenovo) provides r01 to merge some changes from S2-2108922. Jinguo (ZTE) provides r02 George (Ericsson) comments Jinguo(ZTE) provides r03 Genadi (Lenovo) is fine with r03. Jinhua (Xiaomi) provides r04. ==== Revisions Deadline ==== Srisakul (NTT DOCOMO) ok with r04. Jinguo (ZTE) ok with r04. George (Ericsson) OK with r04 ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109144 | CR | Approval | 23.501 CR3401R1 (Rel-17, 'F'): Clarification on Multiple NSACFs for S-NSSAI | ZTE, NTT DOCOMO, Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2108605r04. Approved | Agreed | |
| 8.4 | S2-2108921 | CR | Approval | 23.502 CR3309 (Rel-17, 'F'): Clarification on the NSACF result parameter sent to AMF | Lenovo, Motorola Mobility | Rel-17 | r02 agreed. Revised to S2-2109145. | George Foti (Ericsson) provides r01. This CR provides good clarification But I think we should remove completely the availability status. The original CR questions its usefulness as well https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/INBOX/Revisions/S2-2108921r01.zip Genadi (Lenovo) agrees with r01 provided by George Foti (Ericsson). Provides r02 to update the cover page. ==== Revisions Deadline ==== George (Ericsson) OK r02 ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109145 | CR | Approval | 23.502 CR3309R1 (Rel-17, 'F'): Clarification on the NSACF result parameter sent to AMF | Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2108921r02. Approved | Agreed | |
| 8.4 | S2-2108644 | CR | Approval | 23.501 CR3411 (Rel-17, 'F'): NSAC for priority services | Huawei, HiSilicon | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. With support for session continuity ensured for slices subject to NSAC during EPC IWK and inter AMF mobility, this is not needed. Haiyang (Huawei) indicates this paper is needed in case we cannot have a general solution for session continuity ensured for slices subject to NSAC during EPC IWK and inter AMF mobility this meeting (as already shown in the cover page). Hoyeon (Samsung) provides a comment. Haiyang (Huawei) clarifies to Hoyeon (Samsung). Genadi (Lenovo) provides comments to Haiyang (Huawei). Srisakul (NTT DOCOMO) provides comments. George (Ericsson) comments. Adding such an indication serves no purpose. The PDU session is already accepted and is guaranteed NSAC bypass based on the existing specification. So the SMF will do nothing with it, unless U can explain how will the SMF use it. Haiyang (Huawei) provides r01. Hoyeon (Samsung) provides comments and proposes to address it as a part of session continuity. Haiyang (Huawei) replies to Hoyeon (Samsung). ==== Revisions Deadline ==== George (Ericsson) objects to all revisions Haiyang (Huawei) thinks George (Ericsson)'s objection is not valid George (Ericsson) respond. I already stated that the session has been admitted and is guaranteed SC because it is high priority. So what is the purpose of telling SMF this is a high priority session, after the session is already admitted. There is no use for it anymore. Haiyang (Huawei) responds to George (Ericsson) George (Ericsson) respond. The session is already anchored. So it is subject to handover based on existing procedures and the session should survive unless the handover fails. U miss the point that there is no additional admission in this case. If the session is lost then this UE is subject to regular procedures. Nothing is broken. The case U are citing below is incorrect. There is no additional admission in an already established session regardless of EPC counting or lack there of. The UE may not be able to register but that's different. Haiyang (Huawei) further responds to George (Ericsson) George (Ericsson) respond. No for the simple reason that we have to look into support for SC for this one. I don't want what I would label a 'hack' of telling the AMF, please exempt the user because he is engaged in high priority session. I have a fundamental problem with this approach which is not sound. Haiyang (Huawei) does not think SC could be guaranteed when EPS counting is not required currently. There is additional admission control in an already established session when EPS counting is not required George (Ericsson) SC is guaranteed as the SMF anchors the sessions. Lets not debate that. It is mute issue. If the UE is not MPS than he may not be allowed to register when the UE registers in 5GC if the slice is subject to NSAC. Now the UE can emergency register in 5GC in this case, and we are good to go. Otherwise we can mandate that slices used for MPS should not be subject to NSAC regardless of EPC or 5GC. We don't need to hack the system for a corner case, and for one session only for the UE; now elevating him to MPS for the session duration. Haiyang (Huawei) thinks the comment from George (Ericsson) is unfounded. It is clearly stated that in TS 23.501 clause 5.15.11.5 that 'Mobility from EPC to 5GC does not guarantee all active PDU Session(s) can be transferred to the 5GC in certain circumstances when either the current number of UE registration or the current number of PDU sessions would exceed the maximum number when the UE moves from EPC to 5GC.'. Besides, Invocation-related Priority Mechanism is not corner case but a fundamental mechanism of MPS/MCS George (Ericsson) comment. I will not discuss the session as I said it is mute. I already provided answer on the Registration that U did not address. Furthermore, we have to resolve this within the context of support for SC for slices admission. So we have to wait. Haiyang (Huawei) responds to George (Ericsson): I think for number of UEs we could wait. But for sessions the ongoing discussion is not related to the case when EPS counting is not required currently. Besides, a lie repeated a thousand times is still a lie. Your comment is opposite to the current spec. George (Ericsson) comment. Obviously U don't read ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108922 | CR | Approval | 23.501 CR3345R2 (Rel-17, 'F'): Clarifications of NSAC and NSAC for roaming cases including Emergency and Priority Services | Peraton Labs, CISA ECD, Ericsson, Verizon | Rel-17 | Revision of (Agreed) S2-2107943 from S2#147E. Postponed | Hoyeon (Samsung) provides a comment, and proposes to discuss this CR together with session continuity. Genadi (Lenovo) provides comments and r01 to remove changes overlapping with S2-2108605. George (Ericsson) comments Haiyang (Huawei) seeks for clarification. ==== Revisions Deadline ==== Genadi (Lenovo) can live with r01. Provides further comments that further work is needed in the next meeting. ==== Comments Deadline ==== | Postponed |
| 8.4 | - | - | - | Access type | - | - | Docs:=8 | - | |
| 8.4 | S2-2108516 | CR | Approval | 23.501 CR3261R2 (Rel-17, 'F'): NSAC clarification | Samsung, Ericsson | Rel-17 | Revision of (Postponed) S2-2107226 from S2#147E. Approved | Agreed | |
| 8.4 | S2-2108517 | CR | Approval | 23.502 CR3252 (Rel-17, 'F'): NSAC clarification | Samsung | Rel-17 | r03 agreed. Revised to S2-2109146. | George Foti (Ericsson) provides comments. Please provide an update replacing 'and access type(s) applicable to NSAC' with 'applicable access type' Hoyeon (Samsung) provides r01. Fenqin (Huawei) ask a question Yunjing (CATT) has similar question as Fenqin. Hoyeon (Samsung) replies. Fenqin (Huawei) responds. Hoyeon (Samsung) replies to Fenqin (Huawei). Genadi (Lenovo) supports the proposal, but probably alignment with S2-2108921 may be needed. Fenqin (Huawei) comments Genadi (Lenovo) comments to Fenqin (Huawei). Yunjing (CATT) comments Jinguo(ZTE) response George (Ericsson) comments. Please explain what requirements U are trying to fulfil with this rather big change. We are not OK with this change. There seens to be adhoc changes combined with the MA-PDU CR 8818. Hoyeon (Samsung) provides comments Fenqin (Huawei) provides comments Hoyeon (Samsung) provides r02. George (Ericsson) is not OK with r02, and provides comments Hoyeon (Samsung) clarifies that this CR is nothing related to session counting, and asks some questions to George (Ericsson) Fenqin (Huawei) responds and provides r03 George (Ericsson) responds. The discussion about MA-PDU is addressed elsewhere. Introducing access types as a plural is not OK in this CR as there is no such case for regular PDU sessions. If MA-PDU decides on multiple access types, then we may introduce some categorization, rather than a plural term. This forces U to include the response the access type that is impacted with what is proposed. So move the discussion into MA-PDU thread. We don't need this CR. George (Ericsson) we are OK with r03 ==== Revisions Deadline ==== Hoyeon (Samsung) we can accept r03 for the progress. ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109146 | CR | Approval | 23.502 CR3252R1 (Rel-17, 'F'): NSAC clarification | Samsung | Rel-17 | Revision of S2-2108517r03. Approved | Agreed | |
| 8.4 | S2-2108606 | CR | Approval | 23.502 CR3260 (Rel-17, 'F'): Clarification on Access Type for NSAC | ZTE,Ericsson | Rel-17 | r06 agreed. Revised to S2-2109147, merging S2-2108830 | Ashok (Samsung) have few concerns with the CR and object to it. Yunjing (CATT) provides comments. Jinguo (ZTE) response and provides r01 Ashok (Samsung) comments and not OK with r01 Yunjing (CATT) asks a question to Ashok. Jinguo (ZTE) responses to Ashok. Ashok (Samsung) responds to Jinguo and Yunjing Fenqin (Huawei) comments George (Ericsson) comments. It is needed but we have to look at the different types of sessions. Jinguo(ZTE) response and provides r02 Fenqin (Huawei) comment and provides r03 Srisakul (NTT DOCOMO) provides comments. George (Ericsson) provide comments. Genadi (Lenovo) provides comments. Srisakul (NTT DOCOMO) provide comments. Srisakul (NTT DOCOMO) agrees with Genadi's comments. We would need more parameter rather than just 'skip indicator' as proposed. George (Ericsson) I would be OK with this. But this does not handle the case if one AT is congested for MA-PDU case. Just to remind folks that Fenqin remove which is clearly incorrect, when he provided his update. So the CR needs clearly more work, but at least we seem to be converging Ashok (Samsung) need clarification Jinguo(ZTE) suggest to add new value for update flag. Genadi (Lenovo) agrees with Jinguo's proposal to introduce a new 'update' value of the update flag. Jinguo(ZTE) provides r04 to introduce a new 'update' value of the update flag. Ashok (Samsung) need one clarification from Jinguo(ZTE) : Why NSACF has to consider AT while counting the PDU? Hyunsook (LGE) asks the clarifications. Jinguo(ZTE) responses. Jinguo(ZTE) asks which sentence are you refereing to? Ashok (Samsung) responds to Jinguo(ZTE) alessio(Nokia) believes this Cr now is not adding anything to normal behaviour as it says the SMF updates the NSACF by decreasing AT count of the leg that is released and increase the one of the leg that is added. so what is new? iff I understood correctly then I ask the CR to be noted. Genadi (Lenovo) provides r05 to describe the meaning of the 'update flag' in bulleted list for easier reading. Jinguo(ZTE) reply that alessio(Nokia) understanding is incorrect. Alessio(Nokia) can live with r05 as it is clear what it means now ??. suggest it is a category C Jinguo(ZTE) is fine with r05 Ashok ( Samsung) comments Jinguo(ZTE) replies to Ashok ( Samsung) George (Ericsson) provide comment. Some cases are still not supported in the CR r05. Additional comments below on what is missing George (Ericsson) comment. I don't see access type at all in this rev. 05 Please point me to where it is. Jinguo(ZTE) reply. George (Ericsson) comments. U said a minute ago everything is supported. I don't see access types in the service definition either. We need to have one CR handling all issues related to a session including MA-PDU. Genadi (Lenovo) responds to George (Ericsson). The access type related enhancements are in 8818 and 8830. George (Ericsson) Can we handle everything here under that thread. It is not efficient this distributed discussion. Why cant we have one CR for the whole topic Genadi (Lenovo) comments on the counting in NSACF. George (Ericsson) comment. I am flexible. I just want one CR discussing all PDU aspects, including MA-PDU. We need to make sure that we dot overlook something by prematurely agreeing to bits and pieces George (Ericsson) comments. The anchor SMF increases the count only at session initiation. AS such the described problem does not exist if U read the text. Genadi (Lenovo) responds to George (Ericsson). I quickly checked 8606r05 and 8830 - there seems to be no contradictions. However, if merging is desirable, I can try to provide a merge version (but I can only provide in 1 hour from now). George (Ericsson) provide a consolidate one using Jinguo 8606 rev 05. Yes merging is desirable and essential to see the whole picture ?? ==== Revisions Deadline ==== Genadi (Lenovo) provides r06 including the changes from S2-2108830. Srisakul (NTT DOCOMO) ok with r06 and comments. George (Ericsson) comments. I think this is Ok. If we need to do more clarification we can do it that later. I would support this revision. Genadi (Lenovo) responds to Srisakul (NTT DOCOMO). George (Ericsson) comment. The response must include the result per access type in support of MA-PDU. I believe this is a stage 2 discussion. We can add it later or add an EN, but it needs to be added. Srisakul (NTT DOCOMO) ok with r06. Agrees to George that it would be better to clarify the issue in stage 2 spec, and we can add these details to resolve the issue in the next SA2 meeting. ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109147 | CR | Approval | 23.502 CR3260R1 (Rel-17, 'F'): Clarification on Access Type for NSAC | ZTE,Ericsson, Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2108606r06, merging S2-2108830. Approved | Agreed | |
| 8.4 | S2-2108757 | CR | Approval | 23.502 CR3284 (Rel-17, 'F'): NSAC result applied access type | CATT | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. The response retuned from NSACF applies only to that request, and can't be used for other purpose. It is possible that quota has been increased or PDU sessions has been released freeing quotas, etc.. Ashok (Samsung) comments Yunjing (CATT) replies. George (Ericsson) comments. This seems to be an optimization. I assume it can be done without any normative next added. We would therefore propose to not the CR. Alessio(Nokia) supports ericsson: we should not start proliferating the NSAC policies across NFs in the CN. Let's note this. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108818 | CR | Approval | 23.501 CR3269R2 (Rel-17, 'F'): Clarification on Access Type for NSAC | ZTE, Lenovo, Motorola Mobility | Rel-17 | Revision of (Agreed) S2-2107949 from S2#147E. Approved | George Foti (Ericsson) proposes to note the CR. See comments on 8830 Jinguo(ZTE) is fine with this CR. Ashok (Samsung) comments Jinguo(ZTE) response Genadi (Lenovo) responds to Ashok (Samsung). Genadi (Lenovo) responds to George Foti (Ericsson). George (Ericsson) comments Hyunsook (LGE) provides a comment. Genadi (Lenovo) comments to Hyunsook (LGE) and George (Ericsson). Ashok (Samsung) does not agree with the CR Genadi (Lenovo) replies to Ashok (Samsung) and provides alternative text. Ashok (Samsung) responds to Genadi (Lenovo) Genadi (Lenovo) replies to Ashok (Samsung) and provides a view that the MA-PDU Session is counted once in the NSACF. Fenqin (Huawei) comments. Jinguo(ZTE) response. Genadi (Lenovo) responds to question from Fenqin (Huawei). George (Ericsson) comments. Can we have one CR based on Jinguo's CR 8606. This distributed discussion does not help. ==== Revisions Deadline ==== George (Ericsson) to be noted. Addressed in 8606 Genadi (Lenovo) does not agree with George (Ericsson). 8818 is NOT addressed in 8606. The CR is 8606 is against 23.502, whereas the CR in 8818 is against 23.501. George (Ericsson) respond. Ok U are right. I missed that one. Ericsson is OK with this one Tao(VC) Let's check whether to approve r00 or not George (Ericsson) Yes for Ericsson Genadi (Lenovo) responds to Tao: yes, as this CR (to 23.501) is complimentary to the agreeable one in 8606 (to 23.502). ==== Comments Deadline ==== | Agreed |
| 8.4 | S2-2108830 | CR | Approval | 23.502 CR3292 (Rel-17, 'F'): Clarification on Access Type for NSAC | Lenovo, Motorola Mobility, ZTE | Rel-17 | Merged into S2-2109147 | George Foti (Ericsson) proposes not to handle MA-PDU in Relese 17. Please see additional comments Jinguo(ZTE) support this paper Genadi (Lenovo) responds to George (Ericsson). George (Ericsson) comments. I don't believe the logic has to be in the NSACF. The NSAF maintains counts for admissions; and that's it. This can be its only role. It cannot be aware of session type. We have all sorts of session types; We have MBMS as well for example. So the approach in my view is incorrect beside the missing cases. We have to choose a future proof approach. The SMFs are aware of the logic. This will require updating the interface to handle these cases so NSACF stay clean. Ashok (Samsung) does not agree with the CR. It propose NSACF to mention the AT in its output to SMF while accepting or rejecting the PDU session. In our view the admission and rejection is based on PDU threshold which is irrespective of AT. Genadi (Lenovo) replies to Ashok (Samsung). Ashok (Samsung) responds to Genadi (Lenovo) Genadi (Lenovo) replies to Ashok (Samsung) and provides a view that the MA-PDU Session is counted once in the NSACF. Genadi (Lenovo) comments to George (Ericsson). ==== Revisions Deadline ==== George (Ericsson) to be noted. Addressed in 8606 Genadi (Lenovo) agrees to be noted as merged into 8606r06. ==== Comments Deadline ==== | Merged |
| 8.4 | - | - | - | Roaming | - | - | Docs:=4 | - | |
| 8.4 | S2-2108603 | CR | Approval | 23.502 CR3259 (Rel-17, 'F'): Roaming support for NSAC | ZTE,China Unicom | Rel-17 | Noted | George Foti (Ericsson) provides r01. Minor editorial changes Jinguo(ZTE) is fine with r01. Alessio(nokia) cannot agree to this CR ==== Revisions Deadline ==== Jinguo(ZTE) suggest to go with r01 Fenqin(Huawei) propose to note this CR. Alessio(Nokia) still objects and the only sensible way forward is to come back in Q1 next year to remove roaming support from the feature at this stage. we can work on it in rel-18 ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108563 | CR | Approval | 23.501 CR3391 (Rel-17, 'F'): Roaming support for NSAC with HPLMN control | China Telecom, Huawei, HiSilicon | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. For Release 17 what we have is sufficient. Any additional capabilities have to be checked with GSMA. Fenqin (Huawei) ask a question for clarification George (Ericsson) responds. Nothing is missing. In HR cases, the SMF in the HPLMN interacts with the NSACF and apply NSAC. Now there will be an NSACF dedicated for outbound-roamers as the service area has no meaning here. SO what is missing that stops U from doing based on what I stated Ouerdia (Orange) agrees with Fenqin (Huawei) George (Ericsson) provides comments. Kaisu (Nokia) adds a comment George (Ericsson) comments. The claim was that we have to get requirement from GSMA, and this what we can agree to in Release 17. We cannot invent our own requirements on a topic that is clearly within the realm of GSMA and its support for roaming agreements, which can be static, dynamic or no support at all depending on what they agree on. Let lay the known facts and not more than that. Fenqin(Huawei) comments and provides r01 George (Ericsson) provides comment. Oh yes there is a need for GSMA requirements. This whole work item was triggered by GSMA. U can make Ur case there. Ouerdia (Orange) comments. From an operator point of view, it is not easy to define in advance the quota of roamers to allot for each PLMN partner in the SLA, it will be a hard exercise. So, it is better to have a single quota and perform admission control at HPLMN level, in real time and for all PLMNs (home and partners). No need to wait for a requirements from GSMA. George (Ericsson) objects to R01, and supporting any dynamic control while roaming without explicit requirements from GSMA. We can agree to send an LS to GSMA. I will also bring the issue up at the next meeting. If there are GSMA requirements to that effect we will support that. Heng(China Telecom) support r01 George (Ericsson) comments. If U want HPLMN control roaming don't invoke an NSACF in the VPLMN. Just do everything in HPLMN. But that requires roaming agreement to allow that. This is the logical way to do this. Invoking an NSACF in VPLMN in this HPLMN control accomplishes nothing and create some unclear communication between NSACFs with no idea what is it about or for what purpose, nor any documentation on what it does; on the fly. This is why we are not supporting this adhoc proposals. Alessio(Nokia) is supportive of introducing this. we also have this in our CRs. we can discuss which one should be used as basis. Yan (China Mobile) tend to support the idea of this paper supporting HPLMN control for roaming UE. Heng(China Telecom) reply to Geroge George (Ericsson) responds. Please specify the roaming requirements, when it comes to slices subject to NSAC, that U want to support. Static, dynamic, VPLN, HPLMN and these buzz words provide no requirement; they are wishes. What are the roles in each network, and how does the roaming agreement fits in here. So provide the above information first, then we can see how to fulfill them. Fenqin(Huawei) comments and suggest to go r01 George (Ericsson) Please provide the requirements, and not a solution. We object to all revisions ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108576 | CR | Approval | 23.502 CR3257 (Rel-17, 'F'): Roaming support for NSAC with HPLMN control | China Telecom, Huawei, HiSilicon | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. Please see comments in 8563 Alessio(Nokia) is supportive of introducing this. we also have this in our CRs. we can discuss which one should be used as basis. ==== Revisions Deadline ==== George (Ericsson) objects to the CR Orange (Ouerdia) supports the CR ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108602 | CR | Approval | 23.501 CR3399 (Rel-17, 'F'): Roaming for NSAC | ZTE,China Unicom | Rel-17 | Postponed | George Foti (Ericsson) provides comments Jinguo (ZTE) provides r01 George (Ericsson) comments. Please see inline I don't understand what U are trying to achieve. Ouerdia (Orange) proposes to note the CR. HPLMN is not able to count the registered UEs and/or perform admission control of its roamers, if required, with this proposal Heng (China Telecom) ask a technical issue Jinguo (ZTE) response and provides r02 Jinguo (ZTE) provides r03 as backup if S2-2108563((inter NSACF communication)) cannot be agreed Alessio(nokia) cannot agree to this CR Fenqin(Huawei) comments ==== Revisions Deadline ==== Jinguo (ZTE) provides r04, but propose to go with 8563r01 first if it is agreeable. George (Ericsson) we are Ok with r04 Fenqin(Huawei) object r04 Jinguo(ZTE) replies to Fenqin and asks for CC#2 Jinguo(ZTE) is ok to postpone at this meeting ==== Comments Deadline ==== | Postponed |
| 8.4 | - | - | - | Session continuity | - | - | Docs:=10 | - | |
| 8.4 | S2-2108331 | CR | Approval | 23.501 CR3239R1 (Rel-17, 'F'): Support for Session Continuity for EPC 5GC IWK, and inter-AMF Mobility | Ericsson | Rel-17 | Revision of (Noted) S2-2107112 from S2#147E. Noted | Hoyeon (Samsung) provides a comment. George (Ericsson) respond. Fenqin (Huawei) comments George (Ericsson) provides response. Hoyeon (Samsung) sees some lack of logic about the proposal. George (Ericsson) please sees a response in line. Also Ur solution puts a new system behavior where a slice is rejected but have a PDU session established. That is not allowed today. So U are allowing the UE to continue the session, claiming this supports SC, without being registered. That breaks Release 15, 16, and 17. U also create a regulation problem with emergency and MPS users, without a solution. Fenqin (Huawei) provides response and r01 George (Ericsson) Ericsson object to r01. Explain what will the NSACF communication solve the problem, and how. Please put down what U want in details. Explaining my statement: if the UE is roaming in a different service area and U don't count it as being there but rather being counted in some other service area potentially than U are miscounting. The SMF++PGW-C at home is counting the UE as being in EPC, while the UE is in 5G. Fenqin (Huawei) responds. George (Ericsson) comment. So U now want to extend this to every congested NSACF. That's new. Also help me understand how will reporting this to a central node eliminate congestion in the NSACF having a congestion. Will the central now return a response that is to be relayed by the NSACF to the UE. If so, then the NSACF has to now hold a state that this UE state is in a different node, potentially only for one slice, while other requested slices are OK. There are so many details that U are just ignoring, which shows the holes in this solution. Hoyeon (Samsung) thinks George (Ericsson) misunderstood Samsung proposal. There is no proposal like 'a new system behavior where a slice is rejected but have a PDU session established.' Jinguo(ZTE) provides r02 George (Ericsson) asks a question. How is the rejection of new PDU sessions over that slice help the over quota situation. Also what if that same UE registers other slices unrelated to the IWK slice and establish new PDU sessions. Please answer these 2 questions separately. Of course the question is directed of proponents of this approach in case of over congestion. Additional comments below Jinguo (ZTE) responses George (Ericsson) comments. So if the UE maintains this lone allowed PDU session indefinitely than the over quota situation is not helped. If the same UE uses other slices the over quota is not helped. DO U agree with the above statements ? Iskren (NEC) - r02 is not acceptable Jinguo(ZTE) response Jinguo(ZTE) response to Iskren (NEC) George (Ericsson) comments. I am a bit perplexed that U guys are arguing for a solution that does not resolve the quota issue over other solutions that also does not resolve it but U are complaining about it !!. More comments in line and trying to find a possible path forward. Iskren (NEC) provides r03 which does not allow the UE registrations or PDU Sessions to increase to infinity in EPC interworking. George (Ericsson) comments. Jinguo, this has nothing to do with attractiveness., U acknowledged it does not solve the over quota. It's the argument over it that is rather strange. I proposed few options as a way forward. I think these are pragmatic and provides control. It is also solution neutral. We can have some show of hand as well if need be. This is becoming a show stopper at this time. The other option is we don't support EPC counting, and we remove it completely. I see no other way. George (Ericsson) comments. I would be OK with that, and once we have a consensus we can update the 502 one. Iskren (NEC) answers Jinguo (ZTE) George (Ericsson) responds. No it is guaranteed for those operators who don't configure anything in their NSACF expect reserve a pool for SC users. U have not proposed any solution either expect through the magic of NSACF2NSACF communication. So to support SC, VPLMN1 updates some node (there could be many) in an HPLMN where the is counted there and that UE is not counted in the VPLMN, even though the UE using the VPLMN resources, and overloading the corresponding slice quota in the VPLMN without counting or knowing it; that's under reporting. Alessio(Nokia) proposes to note this CR Hoyeon (Samsung) asks a question for new proposal. George (Ericsson) responds. Some stated that the over quota is infinite. We tried to introduce a maximum over quota limit that the operator configures in the NSAC based on policy if he so chooses. Once that configured over quota is reached SC is not guaranteed. This provides the operator control and as well avoid the infinite issue that U and Fenqin raised. There is no silver bullet here. No one has presented one and there will be none in a distributed environment unless U complicate things to an extreme for a rare event. IF folks want to go to a centralized node then we scrap service areas. Fenqin (Huawei) proposed to note this paper George (Ericsson) provides r04. This is a last ditch effort before NSACF gets formally canned from Release 17. Jinguo(ZTE) provides r05. However propose to go with r04 first if it is agreeable ==== Revisions Deadline ==== George (Ericsson) comments. The note must become normative and with the following text added at the end 'except by implementation specific means' Fenqin(Huawei) propose to note this paper as view are not converged. Jinguo(ZTE) asks for CC#2. Hoyeon (Samsung) we can only accept r01 or r05. Objects to other revisions. George (Ericsson) Ericsson objects to all revision beyond the original Iskren (NEC) supports r02 but can also accept r04. Iskren (NEC) - Sorry, correction:). We can accept r00, r03, r04 only. Alessio(Nokia) Objects to all revisions and the original one ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108332 | CR | Approval | 23.502 CR3126R1 (Rel-17, 'F'): Support for Session Continuity for EPC 5GC IWK, and inter-AMF Mobility | Ericsson | Rel-17 | Revision of (Noted) S2-2107108 from S2#147E. Noted | Hoyeon (Samsung) provides a comment. Please see our comment on S2-2108331. Fenqin (Huawei) same comment as our comment on S2-2108331. Alessio(Nokia) proposes to note this CR George Foti (Ericsson) provides r01 adding the operator policy to manage over quota. Iskren (NEC) provides r02. Fenqin (Huawei) same comment as 8331. alessio(Nokia) keeps their concerns. George (Ericsson) provides r04. The only thing we will be able to agree upon, if any, is to leave it to implementation to ensure SC while not going over the quota. More comments ==== Revisions Deadline ==== Fenqin (Huawei) propose to note this paper due to same reason as 8331. Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108520 | CR | Approval | 23.501 CR3384 (Rel-17, 'F'): NSAC mechanism for session continuity | Samsung | Rel-17 | Noted | George Foti (Ericsson) provides comments Hoyeon (Samsung) replies to George Foti (Ericsson). George (Ericsson) provides comments in line. U have to clarify what objectives U are trying to achieve and why. What U are proposing is new behavior and solves nothing. Ur proposal does not solve the fact that the maximum number of registered UEs has been reached. Not to mention that the quotas are unrelated as U heard it from others as well. Hoyeon (Samsung) thinks George (Ericsson) misunderstood Samsung proposal. There is no proposal like 'a new system behavior where a slice is rejected but have a PDU session established.' George (Ericsson) please respond to the question on the purpose of this limitation. How will it get rid of the over quota situation. Alessio(Nokia) proposes to note this CR Dan(China Mobile) tend to support this idea of this paper Hoyeon (Samsung) provides r01 to accommodate Dan(China Mobile)'s comment. George (Ericsson) responds. There is nothing temporary as Jinguo confirmed, the UE can keep the session indefinitely, the UE can request new slices and new sessions. So this provides no solution to the basic problem of uncontrolled over quota as U call it. Iskren (NEC) - this CR to be Noted or considered as merged to S2-210331 by Ericsson. ==== Revisions Deadline ==== Fenqin (Huawei) - propose to note this CR as it also not solve the over quota issue. Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108521 | CR | Approval | 23.502 CR3253 (Rel-17, 'F'): NSAC mechanism for session continuity | Samsung | Rel-17 | Noted | George Foti (Ericsson) Please see comments on S2-2108520. The CR is Not OK Alessio(Nokia) proposes to note this CR Iskren (NEC) - this CR to be Noted or considered as merged to S2-210332 by Ericsson. ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108817 | CR | Approval | 23.501 CR3434 (Rel-17, 'F'): Clarification of NSAC | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | George Foti (Ericsson) objects to the CR and to the gross misclassification of it as being a Cat F CR. The CR creates more issues, missed cases, and even what it provides is non-scalable. Not to mention the lack of any basis for these major functional change. Additional comments below. Jinguo(ZTE) comments that this CR is not aligned with GSMA requirement. Fenqin (Huawei) comments. George (Ericsson) comments. Ur view of proxying is completely misaligned with what is in the CR as a starter. The CR specification of proxying is about routing and nothing more. Iskren (NEC) expresses concerns with this CR. Alessio(Nokia) replies Hoyeon (Samsung) proposes to note this CR Iskren (NEC) proposes to note this CR Alessio(nokia) replies to Hoyeon(SS) ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note the CR. At least, SC related proposal should be noted. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108831 | CR | Approval | 23.502 CR3293 (Rel-17, 'F'): Clarification of NSAC | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | George Foti (Ericsson) objects to the CR. Please see comments on 8817. Iskren (NEC) expresses concerns with this CR. Alessio(Nokia) replies George (Ericsson) provides a response. The NSACF proxying is an even bigger issue. We can resort to a single node and simplify everything eliminating all problems; but to create NSACF for the sole purpose of proxying is rather strange as an architecture choice given that there is only a central node responsible for Counting. Furthermore with roaming, EPC IWK, and proxying as a package we will end up counting the UE in the PLMN where he initiated the session, and not the current one he is accessing. Alessio(Nokia) replies that like NSSF and NRF, the NSACF can play the role of prosy between VPLMN and HPLMN. So we do not understand the issue. George (Ericsson) comments. NSSF and NRF are not proxies. They are used for policies regarding slicing, and discovery. With that said, is the sole purpose of NSACF proxy routing towards the central node, or does it have another role. Also for intra-PLMN role what role beside routing is the NSACF playing. That is 95% of the traffic. Do NSACF perform anything when it comes to admission. I came to the conclusion that it is pure routing. All the admission, state creation, etc.. are managed up in the single node. Hoyeon (Samsung) expresses concerns with this CR Iskren (NEC) proposes to Note this CR. ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note the CR. At least, SC related proposal should be noted. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108832 | CR | Approval | 23.501 CR3347R1 (Rel-17, 'F'): NSAC for maximum number of PDU Sessions for EPC IWK | Lenovo, Motorola Mobility, NTT DOCOMO, NEC | Rel-17 | Revision of (Postponed) S2-2107735 from S2#147E. Noted | George Foti (Ericsson) provides comments Hoyeon (Samsung) provides comments. Genadi (Lenovo) provides r01 and replies to comments. Fenqin (Huawei) ask question Alessio(nokia) comments and requests to note this CR as it is going down an unworkable path for EPC counting Hoyeon (Samsung) provides a comment. Genadi (Lenovo) replies to Alessio (Nokia) that the CR works if the final conclusion is to go with the proposal in 8331. ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108888 | CR | Approval | 23.501 CR3058R3 (Rel-17, 'F'): TS23.501 Correction to the NSAC to maintain service continuity | NEC | Rel-17 | Revision of (Noted) S2-2107456 from S2#147E. Noted | George Foti (Ericsson) provides comments. The CR does not distinguish the case when EPS counting is performed vs the case where EPS counting is not performed. It leaves everything to operator policy which is nit aligned with existing text. Jinguo(ZTE) suggest to merge this CR into 8331 to have single thread discussion Alessio(Nokia) asks to note this CR ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108889 | CR | Approval | 23.502 CR2950R4 (Rel-17, 'F'): TS23.502 Correction to the NSAC to maintain service continuity | NEC | Rel-17 | Revision of (Noted) S2-2107478 from S2#147E. Noted | George Foti (Ericsson) provides comments Jinguo(ZTE) suggest to merge this CR into 8332 to have single thread discussion Alessio(nokia) asks to note this CR ==== Revisions Deadline ==== Hoyeon (Samsung) proposes to note this CR. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108928 | CR | Approval | 23.501 CR3348R1 (Rel-17, 'F'): SMF+PGW-C behaviour during UE mobility between 5GC and EPC | Lenovo, Motorola Mobility | Rel-17 | Revision of (Postponed) S2-2107736 from S2#147E. Noted | George Foti (Ericsson) provides comments Genadi (Lenovo) provides r01 based on comment from George Foti (Ericsson). Alessio(Nokia) requests to note this CR Jinguo(ZTE) supports this CR Hoyeon (Samsung) is OK with the proposal, asks a question for clarification. Alessio(Nokia) the conflict is because it affects same text. in clause. Genadi (Lenovo) replies to Hoyeon (Samsung). Genadi (Lenovo) replies to Alessio (Nokia) and provides r02. ==== Revisions Deadline ==== George (Ericsson) OK rev 02 Hoyeon (Samsung) is OK with r02. Fenqin (Huawei) comments. Genadi (Lenovo) comments Fenqin (Huawei). Fenqin (Huawei) comments and suggest bring this to CC#2 Genadi (Lenovo) suggests to bring this CR to CC#2. Alessio(Nokia) cannot agree to this CR which highlights the issues with the current model. we need to discuss this thing until next meeting. Alessio(Nokia) provides further info on why there is no point to discuss in CC#2 ==== Comments Deadline ==== | Noted |
| 8.4 | - | - | - | KI#3 U-Slice-MBR | - | - | Docs:=3 | - | |
| 8.4 | S2-2108336 | CR | Approval | 23.503 CR0667 (Rel-17, 'F'): Correction to UE-Slice-MBR support | Ericsson | Rel-17 | Noted | Alessio(Nokia) objects to this CR Paul (Ericsson) replies to Alessio (Nokia). Alessio(Nokia) repeats Nokia concerns with this and cannot agree this is needed. Paul (Ericsson) replies to Alessio (Nokia). Please provide technical reasons for Nokia's objection. Alessio (Nokia) says he has already provided the reason. Paul (Ericsson) provides r01. ==== Revisions Deadline ==== alessio(Nokia) objects to r01 ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108380 | CR | Approval | 23.501 CR3368 (Rel-17, 'F'): Correction to UE-Slice-MBR support | Ericsson | Rel-17 | Noted | Dongeun (Samsung) asks a question Heng(China Telecom) has the same concern as Dongeun Paul (Ericsson) replies to Dongeun (Samsung) and Heng(China Telecom). Heng(China Telecom) has a comment under the reply Jinguo(ZTE) think the second change is not needed Haiyang (Huawei) shares similar view with Heng (China Telecom). Paul (Ericsson) replies to Jinguo (ZTE). alessio (Nokia) objects to this CR Paul (Ericsson) replies to Alessio (Nokia). This CR is needed as otherwise CN has no visibility that a policy intended required) to be enforced is not followed. This breaks this functionality. Alessio(Nokia) comments that we have a different understanding of how to choose between PCF based and RAN based and we do not see the need of this feature proposed after release is frozen. Paul (Ericsson) replies to Alessio (Nokia). The feature is broken if CN is left unaware of whether the policy is actually enforced. No technical reasons to objection are provided. Alessio (Nokia) says he has already provided the reason. Jinguo(ZTE) comments Paul (Ericsson) provides r01. ==== Revisions Deadline ==== Jinguo(ZTE) is ok with first change in r01 but not ok with second change. alessio(Nokia) objects to r01 ==== Comments Deadline ==== Paul (Ericsson) asks question for clarification. Can Nokia clarify what is expected to happen/happens when enforcement of UE-Slice-MBR in RAN is not feasible? | Noted |
| 8.4 | S2-2108527 | CR | Approval | 23.502 CR3151R1 (Rel-17, 'F'): UE-Slice-MBR enforcement during SSC mode 3 operation | Samsung | Rel-17 | Revision of (Postponed) S2-2107268 from S2#147E. Noted | Belen (Ericsson) objects to this CR. Dongeun (Samsung) replies. Jinguo(ZTE) objects to this CR Dongeun(Samsung) responds to ZTE. Jinguo(ZTE) responds. Dongeun (Samsung) responds to ZTE Jinguo(ZTE) reply alessio(Nokia) objects to this CR as already discussed at last meeting Belen (Ericsson) does not think this CR is needed. Dongeun (Samsung) replies to Belen (Ericsson) ==== Revisions Deadline ==== Belen (Ericsson) replies to Samsung ==== Comments Deadline ==== | Noted |
| 8.4 | - | - | - | KI#4 slice info exposure | - | - | Docs:=9 | - | |
| 8.4 | S2-2108313 | CR | Approval | 23.502 CR3220 (Rel-17, 'D'): Correction for the figure of Number of UEs and PDU Sessions per network slice status retrieval by AF procedure | KDDI | Rel-17 | Noted | George Foti (Ericsson)proposes to note the CR. This section will have to be completely removed. ==== Revisions Deadline ==== ==== Comments Deadline ==== Koji Saito(KDDI) provides comment. | Noted |
| 8.4 | S2-2108333 | CR | Approval | 23.502 CR3128R1 (Rel-17, 'F'): Using Immediate reply in conjunction with NSACF related events | Ericsson | Rel-17 | Revision of (Noted) S2-2107114 from S2#147E. CC#2: r05 with restoration of changes in step 7 agreed. Revised to S2-2109341, merging S2-2108721, S2-2108423 and S2-2108642 | George Foti (Ericsson) provides r01 merging changes from 8642 into r01. See comments on 8642. George (Ericsson) provides r02. I included 8721 in here. In response to Genadi about including the S-NSSAI in event filer. I saw no way to do it as this is only for this event, and nothing else. Jinhua (Xiaomi) provides comments. Srisakul (NTT DOCOMO) provides r03 and comments. George (Ericsson) is OK with r03 Kaisu (Nokia) provides r04, which also includes content from 8423rev01. George (Ericsson) comment, We object to r04. Why are U sneaking in the geographical area now ?. We can add a note only for that part . The period chosen is selected by the NEF based on its internal logic, or implementation Please see additional comments George (Ericsson) provides r05. We created a Note for setting up period. Removed geographical area being new function not belonging in a Cat F CR, immature, and not completely thought out and incomplete. Cleaned up step 8. Jinguo(ZTE) supports the georgraphic area George (Ericsson) Is this additional function in the exception report? Jinhua(Xiaomi) provides comments, r05 is fine, and replies to Srisakul about the trusted AF communicate directly Dan(China Mobile) provides r06 and object to r05 George (Ericsson) This is a new feature and incorrectly specified. U can bring it in a call. We object to r06 that introduces new features Srisakul (NTT DOCOMO) replies to Jinhua's comment. OK for both r05 and r06. Jinhua(Xiaomi) replies to Srisakul, the NOTE2 in table 5.2.21.1-1 is sufficient for now. both r05 and r06 is OK for me. Iskren (NEC) - none of the revisions of this CR are acceptable. NEC objects to it as it has gone much beyond its purpose. George (Ericsson) comment. U misunderstood the additions that are necessary to handle service identifier for untrusted AF, and to support single NSACF vs multiple NSACFs deployments. These will have to be in regardless. They will never be out, in any version that U conceive will make U happy unless U eliminate the requirements. They are essential requirements not optional today. ==== Revisions Deadline ==== Jinguo(ZTE) agree with George (Ericsson) that we should go with r05 or r06 and ask for CC#2. George (Ericsson) for us r06 is Not OK. The geographical support is a new feature and is only 10% specified; yes that's it, not well though at all, but I will not discuss any technical issues now or on the call. That's for another day. We need to have a stable revision first, and that's what matters now. George (Ericsson) comments. Jinguo U should bring this up on CC#2. George (Ericsson) comments. I don't understand what merging are U talking about. What is missing here in this procedure. It's a simple question. We did not touch the NSACF procedure. U cannot subscribe for both Registered UEs and PDU sessions in a single request if that is what U imply by merge. Fenqin (Huawei) we are fine with r05 or r06. Thanks! Kaisu (Nokia) we support r06. Dan (China Mobile) we support r06. Iskren (NEC) objects to all versions of this CR unless the bellow highlighted essential text from the current spec is restored. 7. The NSACF sends the Nnsacf_SliceEvent Exposure_Notify (Event ID, Event Filter, Event Reporting information) message to the NEF. If the subscription is for event based notification (e.g. based on the monitored event reaching a threshold value), the Event Reporting information parameter contains confirmation for the event fulfilment. If the subscription is for periodic notification or for immediate reporting, the Event Reporting information parameter provides information for the current number of UEs registered with a network slice (e.g. represented in percentage of the maximum number of the UEs registered with the network slice), information for the current number of PDU Sessions on a network slice (e.g. represented in percentage of the maximum number of the UEs established on the network slice) or both. Genadi (Lenovo) supports r05 or r06 in order to make progress. Clean-ups are needed in CC#2 or in the next meeting. Iskren (NEC) answers Genadi (Lenovo) George (Ericsson) Ericsson accepts only r05. Srisakul (NTT DOCOMO) is fine for both r05 and r06. Ok to restore texts in step#7 as proposed by Iskren. ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109341 | CR | Approval | 23.502 CR3128R2 (Rel-17, 'F'): Using Immediate reply in conjunction with NSACF related events | Ericsson, NTT DOCOMO | Rel-17 | Revision of S2-2108333r05 + changes, merging S2-2108721, S2-2108423 and S2-2108642. Approved | Agreed | |
| 8.4 | S2-2108419 | CR | Approval | 23.501 CR3259R1 (Rel-17, 'F'): AF request for specific area slice status report when multiple NSACFs existing in network | China Mobile | Rel-17 | Revision of (Noted) S2-2107222 from S2#147E. Noted | George Foti (Ericsson) proposes to note the CR. The request is for slices or service identifiers but not for service areas. Genadi (Lenovo) provides comments. Dan(China Mobile) provides reply. Iskren (NEC) provides comments. Ashok (Samsung) shares same view as Iskren (NEC) Srisakul (NTT DOCOMO) comments and agrees to Iskren (NEC). George (Ericsson) provides comments. This is an enhancement that has to be done separately. It is not within the scope of the exception report. Dan (China Mobile) provides r01 George (Ericsson) objects to the CR Kaisu (Nokia) supports rev01 ==== Revisions Deadline ==== TAO(VC) check whether r01 agreeable Iskren (NEC) supports r01 George (Ericsson) comments Ericsson objects to all revisions. George (Ericsson) Ericsson objects. This adds new feature that is not on the table under a CAT F CR, and with no support at all in 23.502. Dan (China Mobile) comments George (Ericsson) 's objection is not based on technical reason, which is unacceptable. Dan (China Mobile) we request for CC#2 Srisakul (NTT DOCOMO) supports r01. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108423 | CR | Approval | 23.502 CR3143R2 (Rel-17, 'F'): AF request for specific area slice status report when multiple NSACFs existing in network | China Mobile | Rel-17 | Revision of (Postponed) S2-2107221 from S2#147E. Merged into S2-2109341 | George Foti (Ericsson) proposes to note the CR. See S2-2108419 Genadi (Lenovo) proposes to discuss first the proposal in S2-2108419 to 23.501. Iskren (NEC) provides comments. Dan (China Mobile) provides r01 Iskren (NEC) answers Dan (China Mobile) and provides r02 with some editorials. George (Ericsson) objects to including additional functionality under a Cat F CR and not covered in the exception report. George (Ericsson) comments. We don't agree to CAT F CRs adding functionality not in the exception sheet. Iskren (NEC) - In my opinion it is not a new feature as we already have the service area as an input for NSACF discovery. George (Ericsson) SA is not geographical area. We have to stop this adhoc addition of things. This is what got this work item in trouble. There is no relation to the study item anymore. Kaisu (Nokia) informs that she has merged 8423rev01 to document 8333rev04 ==== Revisions Deadline ==== Dan (China Mobile)suggest mark this merged into S2-2108333 if SA2 WG approve S2-2108333 r06. ==== Comments Deadline ==== | Merged |
| 8.4 | S2-2108641 | CR | Approval | 23.501 CR3410 (Rel-17, 'F'): Corrections on Nnsacf_SliceStatus and Nnef_SliceStatus services | Huawei, HiSilicon | Rel-17 | Approved | Agreed | |
| 8.4 | S2-2108642 | CR | Approval | 23.502 CR3270 (Rel-17, 'F'): Corrections on Nnsacf_SliceStatus and Nnef_SliceStatus services | Huawei, HiSilicon | Rel-17 | Merged into S2-2109341 | George Foti (Ericsson) proposes to note the CR and incorporate the changes in 5.2.21, 5.2.21.4.2, 5.2.21.4.4, 5.2.21.5 in 8333r01. Additional comments below. ==== Revisions Deadline ==== Haiyang (Huawei) is OK to merge this paper into 8333. ==== Comments Deadline ==== | Merged |
| 8.4 | S2-2108721 | CR | Approval | 23.502 CR3278 (Rel-17, 'F'): Clarification for network slice notification procedure for untrusted AF case | NTT DOCOMO | Rel-17 | CC#2: Merged into S2-2109341 | George Foti (Ericsson) provide r01 just clarifying that Notification to trusted AF includes the service identifier. This CR fits nicely with Ericsson CR S2-2108333 Ashok (Samsung) comments Srisakul (NTT DOCOMO) ok with r01 and provides responses to comments. Genadi (Lenovo) supports the concept, but proposes to move the changes as normative text to clause 4.15.3.2.10. Provides r02. Ashok (Samsung) thanks Genadi (Lenovo) for r02 George (Ericsson) comments. This is not the right place for that. I will provide an update of my CR merging this in 8333 which is the one that should be updated. Genadi (Lenovo) provides comments to George (Ericsson). Srisakul (NTT DOCOMO) provides comments. ==== Revisions Deadline ==== Srisakul (NTT DOCOMO) suggests to mark this tdoc as 'Merged into S2-2108333, if SA2 WG approves any revision from r03 of S2-2108333. Otherwise, let's consider r02 to be approved.' ==== Comments Deadline ==== | Merged |
| 8.4 | S2-2108785 | CR | Approval | 23.501 CR3428 (Rel-17, 'F'): Correction for External Exposure of Network Capability | Xiaomi, | Rel-17 | Approved | Agreed | |
| 8.4 | - | - | - | KI#5 PCF based monitoring | - | - | Docs:=4 | - | |
| 8.4 | S2-2108737 | CR | Approval | 23.503 CR0663R1 (Rel-17, 'F'): Correction for PCF based monitoring of the data rate per network slice | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of (Noted) S2-2107509 from S2#147E. Noted | Belen (Ericsson) proposes to merge this CR into S2-2108737 Jinhua(Xiaomi) replies to Belen, Alessio(Nokia) asks to note the CR and all its revisions as per discussion we already had at SA2#147 Mirko (Huawei) responds to Alessio. Belen (Ericsson) supports this CR. ==== Revisions Deadline ==== Tao(VC) further check whether it is agreeable per clarification from Huawei and Ericsson. Alessio(Nokia) does not understand why we need this separate value given the quota is not separate. maintains the objection as there is no reason to assume that we starve Non GBR unless statisticaly almost all requests are GBR, which then means that GBR is most important category to be served. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108787 | CR | Approval | 23.503 CR0687 (Rel-17, 'F'): Correction for PCF Based Monitoring of the Slice Data Rate | Xiaomi, | Rel-17 | Noted | alessio(Nokia) provides r01 Mirko (Huawei) comments. Belen (Ericsson) comments. alessio(Nokia) clarifies that the maximum data rate defined by GSMA includes GBR and NON GBR. ==== Revisions Deadline ==== Belen (Ericsson) cannot accept r01 and objects, provides a rephrasing if acceptable Tao(VC) check whether Belen's text proposal acceptable or not Jinhua(Xiaomi) is OK with Belen's proposal, that r01 can be approved without the addition of 'exceeding the Maximum Slice Data Rate'. Alessio(Nokia) does not understand why we need this separate value given the quota is not separate. maintains the objection as there is no reason to assume that we starve Non GBR unless statistically almost all requests are GBR, which then means that GBR is most important category to be served. ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108788 | CR | Approval | 23.503 CR0652R2 (Rel-17, 'F'): Selection of the PCF for network slice related policy control | Ericsson(?), Xiaomi | Rel-17 | Revision of (Agreed) S2-2107952 from S2#147E. Confirm Sources! r02 agreed. Revised to S2-2109148. | Belen (Ericsson) confirms support to this CR Jinhua(Xiaomi) replies to Belen and provides r01, Mirko (Huawei) provides r02. Jinhua(Xiaomi) replies to Mirko, r02 is OK. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.4 | S2-2109148 | CR | Approval | 23.503 CR0652R3 (Rel-17, 'F'): Selection of the PCF for network slice related policy control | Ericsson, Xiaomi | Rel-17 | Revision of S2-2108788r02. Approved | Agreed | |
| 8.4 | - | - | - | KI#7 configured NSSAI | - | - | Docs:=3 | - | |
| 8.4 | S2-2108310 | CR | Approval | 23.501 CR3359 (Rel-17, 'F'): Alignment with RAN conclusion on providing Configured NSSAI to the RAN | Convida Wireless LLC, Nokia, Nokia Shanghai Bell, Orange, Verizon | Rel-17 | Noted | Jinguo(ZTE) proposed to note this CR Peter Hedman (Ericsson) proposed to note this CR Dieter (Deutsche Telekom) proposes to note this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.4 | S2-2108604 | CR | Approval | 23.501 CR3400 (Rel-17, 'F'): Removal of Editor's Note on Configured NSSAI | ZTE, Huawei, Samsung, Ericsson | Rel-17 | Approved | Alessio (Nokia) comments this is still discussed offline so let's hold approval till we take one last round of discussions following the SoH ==== Revisions Deadline ==== Jinguo(ZTE) suggest to approve the original version. ==== Comments Deadline ==== | Agreed |
| 8.4 | S2-2108893 | DISCUSSION | Agreement | On providing Configured NSSAI to the RAN | Nokia, Nokia Shanghai Bell, Convida Wireless | Rel-17 | Noted | Noted | |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=64 | - | |
| 8.5 | - | - | - | LSs | - | - | Docs:=3 | - | |
| 8.5 | S2-2108276 | LS In | Action | Reply LS on more efficient PMIC/UMIC signalling exchange for time synchronization | CT WG1 (C1-216069) | Rel-17 | Postponed | Postponed | |
| 8.5 | S2-2108288 | LS In | Information | LS from CT WG4: Reply LS on UPF reporting for redundant transmission on transport layer | CT WG4 (C4-215505) | Rel-17 | Noted | Sang-Jun (Samsung) proposes to move it to 7.10 5G_URLLC or to note the LS since no action is required to SA2. ==== Revisions Deadline ==== Qianghua (Huawei) agrees with Samsung ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108292 | LS In | Information | LS from IEEE: RE: LS on Correction Field update for Transparent Clock | IEEE (Reply to 3GPP liaison correction field) | Noted | Chunshan(Tencent) has provided related CR S2-2108539 based on this LS . Devaki (Nokia) proposes to note the LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 8.5 | - | - | - | CRs | - | - | Docs:=61 | - | |
| 8.5 | S2-2108308 | CR | Approval | 23.501 CR3357 (Rel-17, 'F'): Deletion of selected enrties in UMIC/PMIC data structures | Intel, NTT DOCOMO | Rel-17 | r02 agreed. Revised to S2-2109278. | Saso (Intel) provides r01 Saso (Intel) provides r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109278 | CR | Approval | 23.501 CR3357R1 (Rel-17, 'F'): Deletion of selected enrties in UMIC/PMIC data structures | Intel, NTT DOCOMO | Rel-17 | Revision of S2-2108308r02. Approved | Agreed | |
| 8.5 | S2-2108309 | CR | Approval | 23.501 CR3358 (Rel-17, 'F'): Clarification on Static Filtering Entries | Intel, NTT DOCOMO, Ericsson | Rel-17 | r05 agreed. Revised to S2-2109279. | Devaki (Nokia) provides r01. Qianghua (Huawei) object r00, provides r02 Saso (Intel) objects r02; provides r03 on top of r01. Qianghua (Huawei) provides r04, object r03 Saso (Intel) provides r05 on top of r04. Zhendong (ZTE): prefer r04 Saso (Intel) replies to Zhendong that r05 is better because it lifts unnecessary restrictions for UPF implementations. ==== Revisions Deadline ==== Qianghua (Huawei) objects r00, r01, r03 given the reasons expressed before, OK with the other revisions (prefer r04) Zhendong (ZTE): also prefer r04 Jari (NTT DOCOMO) prefers r05. r04 is not consistent. Saso (Intel) prefers r05. Agrees with Jari that r04 is inconsistent. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109279 | CR | Approval | 23.501 CR3358R1 (Rel-17, 'F'): Clarification on Static Filtering Entries | Intel, NTT DOCOMO, Ericsson | Rel-17 | Revision of S2-2108309r05. Approved | Agreed | |
| 8.5 | S2-2108315 | CR | Approval | 23.501 CR3242R2 (Rel-17, 'F'): Improved PTP instance configuration management | Intel, NTT DOCOMO, Ericsson | Rel-17 | Revision of (Agreed) S2-2108126 from S2#147E. r02 agreed. Revised to S2-2109280. | Devaki (Nokia) supports the CR, happy to cosign. Minor correction is needed in the annex. Saso (Intel) provides r01 Sebastian (Qualcomm) provides r02 Saso (Intel) is OK with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109280 | CR | Approval | 23.501 CR3242R3 (Rel-17, 'F'): Improved PTP instance configuration management | Intel, NTT DOCOMO, Ericsson, Nokia | Rel-17 | Revision of S2-2108315r02. Approved | Agreed | |
| 8.5 | S2-2108426 | CR | Approval | 23.502 CR3131R1 (Rel-17, 'F'): Updating the description of UE-DS-TT Residence Time delivery to the PCF | Ericsson, [Nokia, Nokia Shanghai Bell, CATT] | Rel-17 | Revision of (revised and approved) S2-2107132 from S2#147E. Merged into S2-2109285 | Devaki (Nokia) proposes to merge this paper with 8478 as that address the discovery part, also this paper seems to still assume the old discovery (not aligned with SoH). György (Ericsson) proposes r01. Qianghua (Huawei) provides r02 Jari (NTT DOCOMO) comments Devaki (Nokia) provides r03 (although we still prefer 8478). Qianghua (Huawei) comments for r03 Zhendong (ZTE): provides comments and prefer use 8478 as baseline György (Ericsson) merges the CR into 8478. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108427 | CR | Approval | 23.503 CR0674 (Rel-17, 'F'): Parameter handling for an AF requesting a specific QoS | Ericsson | Rel-17 | Merged into S2-2109286 | Chunshan(Tencent) provides r01. Jari (NTT DOCOMO) question for clarification Shabnam (Ericsson) provides r02. Mirko (Huawei) comments. Devaki (Nokia) proposes to consider this as merged with a revision of 8479 due to many overlapping changes (although they are quite aligned technically overall). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108428 | CR | Approval | 23.501 CR3370 (Rel-17, 'F'): Completing funtional description for TSC | Ericsson | Rel-17 | Confirm Specification Number - CR states 23.503! Merged into S2-2109296 | Devaki (Nokia) provides r01. Mirko (Huawei) comments and suggests to use S2-2108739 for documenting the support of time sensitive communication. Shabnam (Ericsson) I would like to keep this separate from the CR you mention at this time. Let's see where we end up. Shabnam (Ericsson) provides r02 removing changes in clause 6.1.3.22 and reinstated the model. Devaki (Nokia) can live without the CR but cannot accept the model ( as it is not defined nor necessary for regular IP PDU Sessions/TSC services. Shabnam (Ericsson) comments and provides r03, Maurice as the CR was taken on wrong spec number, if agreed I will need a new CR# on 23.503. ==== Revisions Deadline ==== Mirko (Huawei) proposes to note this CR and to use S2-2108739r01 for documenting the support of time sensitive communication. Shabnam (Ericsson) considers this CR to be merged into 8739 and requests cosigning 8739. ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108429 | CR | Approval | 23.502 CR3235 (Rel-17, 'F'): Adding Trusted AF in Time Synchronization procedures | Ericsson | Rel-17 | r01 agreed. Revised to S2-2109281. | Zhendong (ZTE): provides r01 Devaki (Nokia) comments. Shabnam (Ericsson) responds ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109281 | CR | Approval | 23.502 CR3235R1 (Rel-17, 'F'): Adding Trusted AF in Time Synchronization procedures | Ericsson | Rel-17 | Revision of S2-2108429r01. Approved | Agreed | |
| 8.5 | S2-2108434 | CR | Approval | 23.503 CR0660R2 (Rel-17, 'F'): Policy for Handling of PMIC exchange with UE(s) in idle mode | Samsung[, Huawei, Ericsson] | Rel-17 | Revision of (Agreed) S2-2108136 from S2#147E. Merged into S2-2109296 | Devaki (Nokia) proposes to merge this with 8428. Sebastian (Qualcomm) objects to the CR Shabnam (Ericsson) comments that we need to also withdraw the CR version that was approved last meeting, contents are now in 8428. Zhendong (ZTE): proposes to merge this with 8428/8739 Sang-Jun (Samsung) agrees that the CR is merged to 8428. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108475 | CR | Approval | 23.501 CR3375 (Rel-17, 'F'): 23.501: TSCTSF Discovery and Selection | Nokia, Nokia Shangai Bell, Huawei, HiSilicon | Rel-17 | Revised to S2-2108961 | Revised | |
| 8.5 | S2-2108961 | CR | Approval | 23.501 CR3375R1 (Rel-17, 'F'): 23.501: TSCTSF Discovery and Selection | Nokia, Nokia Shangai Bell, Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108475. r05 agreed. Revised to S2-2109282. | Jari (NTT DOCOMO) objects to the CR Qianghua (Huawei) replies Jari (NTT DOCOMO) responds Devaki (Nokia) replies. Based on the SoH outcome and recommended way forward, hope we can constructively progress. Jari (NTT DOCOMO) provides r01 György (Ericsson) comments. György (Ericsson) responds Devaki (Nokia) thanks for the constructive progress and the revision, provides r03. Jari (NTT DOCOMO) comments Jari (NTT DOCOMO) provides r04 Zhendong (ZTE): provides r05 Zhendong (ZTE): provides response Devaki (Nokia) comments. Zhendong (ZTE): agree with devaki ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109282 | CR | Approval | 23.501 CR3375R2 (Rel-17, 'F'): 23.501: TSCTSF Discovery and Selection | Nokia, Nokia Shangai Bell, Huawei, HiSilicon, Ericsson, ZTE | Rel-17 | Revision of S2-2108961r05. Approved | Agreed | |
| 8.5 | S2-2108476 | CR | Approval | 23.502 CR3246 (Rel-17, 'F'): 23.502: TSCTSF Discovery and Selection | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2109283. | Jari (NTT DOCOMO) questions for clarification György (Ericsson) comments. Jari (NTT DOCOMO) responds to György Qianghua (Huawei) provides r01 Jari (NTT DOCOMO) comments, r01 does not address my previous questions Jari (NTT DOCOMO) proposes to merge with S2-2108477 GYörgy (Ericsson) responds to Jari. Devaki (Nokia) provides r02, comments that this CR cannot be marked as merged with 8477 as they are addressing completely different sections: 8476r01: 4.16.5.1, 5.2.5.1, 5.2.5.3.1, 5.2.5.3.3, 5.2.6.9.2, 5.2.6.9.5, 5.2.27.3.2, 5.2.27.3.3; 8477r01: 4.15.9.2, 4.16.5.1 Devaki (Nokia) provides r03. Devaki (Nokia) provides r04. Jari (NTT DOCOMO) provides r05. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109283 | CR | Approval | 23.502 CR3246R1 (Rel-17, 'F'): 23.502: TSCTSF Discovery and Selection | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108476r05. Approved | Agreed | |
| 8.5 | S2-2108477 | CR | Approval | 23.502 CR3247 (Rel-17, 'F'): 23.502: Time Sync exposure procedure | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2109284. | Jari (NTT DOCOMO) objects to the CR Devaki (Nokia) provides r01 based on comments received. Based on SoH outcome for TSCTSF discovery, hope we can constructively move forward by using this as the basis and providing revisions. Jari (NTT DOCOMO) comments Devaki (Nokia) provides r03. Jari (NTT DOCOMO) objects all revisions György (Ericsson) provides r04. György (Ericsson) provides r05 Devaki (Nokia) replies. György (Ericsson) responds. ==== Revisions Deadline ==== Sebastian (Qualcomm) objects to r05; would be ok with r05 if 'If time synchronization capability information from the DS-TT or NW-TT is available at the PCF, the PCF reports the capabilities to the TSCTSF invoking Npcf_PolicyAuthorization_Notify. ' can be changed to 'If PMIC/UMIC information from the DS-TT or NW-TT is available at the PCF, the PCF reports it to the TSCTSF invoking Npcf_PolicyAuthorization_Notify. '' Devaki (Nokia) agrees with Sebastian's proposed update to r05. György (Ericsson) OK with Sebastian's proposed update to r05. ==== Comments Deadline ==== Qianghua (Huawei) OK with Sebastian's proposal | Revised |
| 8.5 | S2-2109284 | CR | Approval | 23.502 CR3247R1 (Rel-17, 'F'): 23.502: Time Sync exposure procedure | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108477r05. Approved | Agreed | |
| 8.5 | S2-2108478 | CR | Approval | 23.502 CR3248 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell | Rel-17 | r05 agreed. Revised to S2-2109285, merging S2-2108426 and S2-2108819 | György (Ericsson) comments. Devaki (Nokia) provides r01 addressing the comments. György (Ericsson) responds. Jari (NTT DOCOMO) objects all revisions György (Ericsson) provides r02 Qianghua (Huawei) provides r03 Jari (NTT DOCOMO) comments György (Ericsson) provides r04. György (Ericsson) provides r05 and comments. Jari (NTT DOCOMO) proposes to postpone Devaki (Nokia) comments. Jari (NTT DOCOMO) comments. Zhendong (ZTE): proposes to agree in this meeitng ==== Revisions Deadline ==== Qianghua (Huawei) also prefers to make some progress, and we are open to make other additional changes if possible next meeting Devaki (Nokia) proposes updates on top of r05 to address Jari's concern and discussion with Gyorgy regarding Alt. QoS. Uploaded as r07 in DRAFTS folder. Changes listed below explicitly Qianghua (Huawei) OK with r07 György (Ericsson) provides r08 in the drafts folder to correct some minor aspects. Devaki (Nokia) is fine with r08 to move forward. ==== Comments Deadline ==== Devaki (Nokia) requests r08 to be marked for CC#2 (changes on top of r05 stated below). Devaki (Nokia) requests that this is brought up for CC#2 to approve r08 (= agreed changes on top of r05). | Revised |
| 8.5 | S2-2109285 | CR | Approval | 23.502 CR3248R1 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, ZTE | Rel-17 | Revision of S2-2108478r05, merging S2-2108426 and S2-2108819. CC#2: Approved | Agreed | |
| 8.5 | S2-2108479 | CR | Approval | 23.503 CR0675 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell | Rel-17 | r04 agreed. Revised to S2-2109286, merging S2-2108427 and S2-2108740 | György (Ericsson) comments. Devaki (Nokia) provides r01. Devaki (Nokia) provides r02 (merging changes from 8427). György (Ericsson) provides r03. György (Ericsson) provides r04. ==== Revisions Deadline ==== Devaki (Nokia) proposes to move forward with r02 as r03 removes critical aspects (i.e. AF can no longer provide individual QoS parameters that can be used to determine Alt. QoS profile). György (Ericsson) cannot accept r00-r02. Devaki (Nokia) cannot accept r03, r04. György (Ericsson) proposes to go with r04 (objects to r00-r02). Clarifies that r04 does not include the controversial aspects. Devaki (Nokia) can accept r04 based on updates discussed also for TS 23.502 in r07. Zhendong (ZTE): is fine with r04 ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109286 | CR | Approval | 23.503 CR0675R1 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell, Ericsson, ZTE | Rel-17 | Revision of S2-2108479r04, merging S2-2108427 and S2-2108740. Approved | Agreed | |
| 8.5 | S2-2108539 | CR | Approval | 23.501 CR3386 (Rel-17, 'F'): Update the correction field for the end-to-end Transparent Clock | Tencent, Tencent Cloud, CATT | Rel-17 | r07 agreed. Revised to S2-2109287. | Devaki (Nokia) provides r01. Jari (NTT DOCOMO) question for clarification Chunshan (Tencent) question for clarification Sebastian (Qualcomm) comments Chunshan(Tencent) responses to Sebastian (Qualcomm). Chunshan(Tencent) provides r02. Chunshan(Tencent) provides r03. Shabnam (Ericsson) provides comments and have concerns as introduces serious issues, I provide r04 but may need to further update. Chunshan(Tencent) responses to Shabnam (Ericsson). Chunshan(Tencent) provides r05. Shabnam (Ericsson) provides r06, based on r04 and objects to all other revisions Chunshan(Tencent) provides r07. ==== Revisions Deadline ==== Devaki (Nokia) comments that the cover sheet shall clarify CR#3260 should not be approved by SA plenary. Chunshan (Tencent) responses to Devaki (Nokia) that the content of the CR#3260 is not included in the r06/r07 anymore. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109287 | CR | Approval | 23.501 CR3386R1 (Rel-17, 'F'): Update the correction field for the end-to-end Transparent Clock | Tencent, Tencent Cloud, CATT | Rel-17 | Revision of S2-2108539r07. Approved | Agreed | |
| 8.5 | S2-2108540 | CR | Approval | 23.501 CR3286R1 (Rel-17, 'F'): Time Synchronization of the 5GS as IEEE 1588 Boundary Clock | Tencent, Tencent Cloud, CATT | Rel-17 | Revision of (Noted) S2-2107343 from S2#147E. Noted | Devaki (Nokia) provides r01. Sang-Jun (Samsung) asks for clarification why 5.27.1.1 and 5.27.1.2.2.2 are different. Jari (NTT DOCOMO) proposes to postpone Saso (Intel) points out that there is an alternative proposal in S2-2108877. It is fine to use this thread for the discussion. Jari (NTT DOCOMO) responds to Saso (Intel) Chunshan (Tencent) responses to Jari. Chunshan (Tencent) comments 8877 on this thread. Saso (intel) replies to Chunshan (Tencent). Chunshan (Tencent) comments on Saso (intel). Sebastian (Qualcomm) objects to the CR for the reason that we should first wait for the feedback from SMPTE before we make changes as the ones proposed in this CR Chunshan (Tencent) points out that the CR is to solve the conflict between the TS and IEEE 1588 and is not related with the LS of SMPTE, and wants to say that Sebastian (Qualcomm) objection is not reasonable. Chunshan (Tencent) provides r02. Sang-Jun (Samsung) confirms changes of r02 are fine. Chunshan (Tencent) responses to Saso (Intel) that solutions of 8870 is incomplete. Chunshan (Tencent) response to Saso (Intel). Chunshan (Tencent) responses to Saso (Intel). Shabnam (Ericsson) maintains objection to this CR, provides detailed comments Chunshan (Tencent) responses to Shabnam (Ericsson). Shabnam (Ericsson) maintains objection to this CR, provides responses ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108626 | CR | Approval | 23.501 CR3404 (Rel-17, 'F'): Principle for Handling of PMIC exchange with UE(s) in idle mode | Samsung | Rel-17 | Noted | Devaki (Nokia) proposes to note the CR. Sang-Jun (Samsung) replies to Devaki (Nokia). Sebastian (Qualcomm) objects to the CR Zhendong (ZTE): similar view with nokia Sang-Jun (Samsung) provides r01. Sebastian (Qualcomm) objects to r01 (reasons already given) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108627 | CR | Approval | 23.502 CR3267 (Rel-17, 'F'): Procedure for Handling of PMIC exchange with UE(s) in idle mode | Samsung | Rel-17 | Noted | Devaki (Nokia) proposes to note the CR. Sang-Jun (Samsung) replies to Devaki (Nokia). Sebastian (Qualcomm) objects to the CR Haiyang (Huawei) provides r01 Sang-Jun (Samsung) can accept r01. Sebastian (Qualcomm) objects to r01 (reasons already given) Shabnam (Ericsson) objects to original and r01 (reasons already given by Nokia and Qualcomm) ==== Revisions Deadline ==== Sang-Jun (Samsung) points out that r01 is listing some examples to the existing description on ATC for clarification. ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108630 | CR | Approval | 23.501 CR3405 (Rel-17, 'F'): Relationship between Sync Exposure and Time Distribution | Samsung | Rel-17 | r03 agreed. Revised to S2-2109288. | Devaki (Nokia) provides r01 Shabnam (Ericsson) asks clarification to the proposed changes, don't believe this CR is needed. Sang-Jun (Samsung) provides r02. Shabnam (Ericsson) comments that it is already described in the same clause so no reason for duplication? ==== Revisions Deadline ==== Sang-Jun (Samsung) can accept r03 provided by Shabnam (Ericsson). Devaki (Nokia) comments that r03 is not correct for ASTI. Shabnam (Ericsson) comments that on high level without going into all parameters and first sentence of the clause reading, r03 is correct, and that is why prefer not to duplicate between specs. Proposes to approve r03 and not r02 as marked in chair's notes. Sang-Jun (Samsung) can accept r00, r02 and r03, and comments that r03 can work. Devaki (Nokia) comments that the parameters should not have been included i.e. using the DNN and S-NSSAI. R03 is ok only if the parameters are removed. Otherwise, can accept r01 only. Devaki (Nokia) comments that the ASTI procedure for a single UE is sent using UE ID and not DNN/S-NSSAI (rather DNN/S-NSSAI is a special case only for any UE). OK with r03 if DNN/S-NSSAI is removed. Sang-Jun (Samsung) can accept r03 without 'using the DNN and S-NSSAI'. Jari (NTT DOCOMO) accept r02, or can accept r03 without 'using the DNN and S-NSSAI'. Sang-Jun (Samsung) provides r03+update in CC#2 folder in case we need to confirm. r03 is before deadline, and update is deleting 'using the DNN and S-NSSAI'. Shabnam (Ericsson) OK with Samsung revision of r03+update deleting 'using the DNN and S-NSSAI' and approve at CC#2. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109288 | CR | Approval | 23.501 CR3405R1 (Rel-17, 'F'): Relationship between Sync Exposure and Time Distribution | Samsung, Ericsson | Rel-17 | Revision of S2-2108630r03. Approved | Agreed | |
| 8.5 | S2-2108632 | CR | Approval | 23.503 CR0680 (Rel-17, 'F'): Correction on 5G access stratum time distribution parameters | Huawei, HiSilicon | Rel-17 | r04 agreed. Revised to S2-2109289. | Devaki (Nokia) provides r01. Jari (NTT DOCOMO) question for clarification Zhendong (ZTE): provides r02 Haiyang (Huawei): provides r03 on top of r02 Shabnam (Ericsson) has concerns on the revisions as they are not acceptable, comments Haiyang (Huawei) provides r04 ==== Revisions Deadline ==== Shabnam (Ericsson) Thanks Sunhaiyang, comments that NOTE 10 is not complete, we need to have a revision to fix that. Chunshan (Tencent) comments that a new revision is needed since the new added NOTE 10 is incomplete. Haiyang (Huawei) suggests to go with [r04 + add 'enabled' in NOTE 10], (may need confirmation at CC#2) ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109289 | CR | Approval | 23.503 CR0680R1 (Rel-17, 'F'): Correction on 5G access stratum time distribution parameters | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108632r04. Approved | Agreed | |
| 8.5 | S2-2108633 | CR | Approval | 23.501 CR3406 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109290, merging S2-2108821 | Devaki (Nokia) provides r01. Zhendong (ZTE): agree with nokia Shabnam (Ericsson) agrees with Nokia updates but requires additional corrections and provides via r02 Haiyang (Huawei) has questions on r01/r02 Devaki (Nokia) replies. Haiyang (Huawei) replies Zhendong (ZTE): provides response Haiyang (Huawei) replies to Zhendong (ZTE) and provides r03 Shabnam (Ericsson) does not agree to r03, provides comment ==== Revisions Deadline ==== Haiyang (Huawei) can live with r02 ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109290 | CR | Approval | 23.501 CR3406R1 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | Revision of S2-2108633r02, merging S2-2108821. Approved | Agreed | |
| 8.5 | S2-2108634 | CR | Approval | 23.502 CR3268 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | Noted | Shabnam (Ericsson) comments regarding the NOTE in clause 4.15.9.1 and 4.15.9.3.2 step 6, last paragraph. Haiyang (Huawei) replies to Shabnam (Ericsson). ==== Revisions Deadline ==== Jar (NTT DOCOMO) proposes to note ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108635 | CR | Approval | 23.502 CR3269 (Rel-17, 'F'): Clarifications on the use of DS-TT port MAC address | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109291. | Chunshan(Tencent) provides r01 and comments . Zhendong (ZTE): provides comments Haiyang (Huawei) provides r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109291 | CR | Approval | 23.502 CR3269R1 (Rel-17, 'F'): Clarifications on the use of DS-TT port MAC address | Huawei, HiSilicon | Rel-17 | Revision of S2-2108635r02. Approved | Agreed | |
| 8.5 | S2-2108636 | CR | Approval | 23.503 CR0681 (Rel-17, 'F'): Clarifications on the use of DS-TT port MAC address | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109292. | Chunshan(Tencent) proposes to note this paper. Jari (NTT DOCOMO) agrees with Chunshan, proposes to note this paper. Haiyang (Huawei) indicates this paper is the alignment with agreed 501 CR S2-2108128 and is only related to the binding. Jari (NTT DOCOMO) comments György (Ericsson) comments Jari (NTT DOCOMO) provides r01 Haiyang (Huawei) is OK with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109292 | CR | Approval | 23.503 CR0681R1 (Rel-17, 'F'): Clarifications on the use of DS-TT port MAC address | Huawei, HiSilicon | Rel-17 | Revision of S2-2108636r01. Approved | Agreed | |
| 8.5 | S2-2108646 | CR | Approval | 23.503 CR0682 (Rel-17, 'F'): Clarifications on Policy for AF | Samsung | Rel-17 | r01 agreed. Revised to S2-2109293. | Mirko (Huawei) comments. Sang-Jun (Samsung) provides r01 as per Mirko (Huawei)' comments. Yuan Tao (CATT) comments. Shabnam (Ericsson) agrees with CATT, the content of 6.2.10 needs to be moved under 6.2.3. Sang-Jun (Samsung) provides r03. ==== Revisions Deadline ==== Mirko (Huawei) can only accept r01 and objects to all other versions. Sang-Jun (Samsung) can accept r01 and r03. Yuan Tao (CATT) prefer r03. Mirko (Huawei) responds. Yuan Tao (CATT) can accept r01. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109293 | CR | Approval | 23.503 CR0682R1 (Rel-17, 'F'): Clarifications on Policy for AF | Samsung | Rel-17 | Revision of S2-2108646r01. Approved | Agreed | |
| 8.5 | S2-2108705 | CR | Approval | 23.501 CR3322R1 (Rel-17, 'F'): Processing (g)PTP messages for domain numbers and while in Disabled state | NTT DOCOMO, Intel | Rel-17 | Revision of (Postponed) S2-2107617 from S2#147E. r01 agreed. Revised to S2-2109294. | Chunshan(Tencent) provides r01 and comments. Haiyang (Huawei) agrees with Chunshan (Tencent). Yuan Tao (CATT) agrees with Tencent and Huawei. Zhendong (ZTE): provides comments Jari (NTT DOCOMO) responds to Zhendong ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109294 | CR | Approval | 23.501 CR3322R2 (Rel-17, 'F'): Processing (g)PTP messages for domain numbers and while in Disabled state | NTT DOCOMO, Intel | Rel-17 | Revision of S2-2108705r01. Approved | Agreed | |
| 8.5 | S2-2108738 | CR | Approval | 23.501 CR3107R3 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon | Rel-17 | Revision of (Endorsed) S2-2108139 from S2#147E. r04 agreed. Revised to S2-2109295. | Devaki (Nokia) objects to r00, provides r01. Zhendong (ZTE): prefer go with approved CR in the last meeting Sebastian (Qualcomm) provides r02 Mirko (Huawei) responds. Shabnam (Ericsson) supports Qualcomm's r02. Sang-Jun (Samsung) provides r03. Sang-Jun (Samsung) provides r04. Mirko (Huawei) can accept r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109295 | CR | Approval | 23.501 CR3107R4 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon | Rel-17 | Revision of S2-2108738r04. Approved | Agreed | |
| 8.5 | S2-2108739 | CR | Approval | 23.503 CR0634R3 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon, Samsung | Rel-17 | Revision of (Endorsed) S2-2108140 from S2#147E. r01 agreed. Revised to S2-2109296, merging S2-2108428 and S2-2108434 | Jari (NTT DOCOMO) comments Mirko (Huawei) responds. Shabnam (Ericsson) comments that the new clause repeats requirements from 23.501 and prefer to rather use reference instead towards 23.501/23.502. Jari (NTT DOCOMO) provides r01 ==== Revisions Deadline ==== Devaki (Nokia) prefers r01 (straight forward overview of the new clause), does not prefer r0 with listing exceptions. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109296 | CR | Approval | 23.503 CR0634R4 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon, Samsung, Ericsson | Rel-17 | Revision of S2-2108739r01, merging S2-2108428 and S2-2108434. Approved | Agreed | |
| 8.5 | S2-2108740 | CR | Approval | 23.503 CR0686 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon | Rel-17 | Merged into S2-2109286 | Shabnam (Ericsson) comments on a number of aspects for this CR that requires first clarification before approval or revision Devaki (Nokia) has concerns with the CR as they are not corrections, propose to merge with 8479 and use that as baseline to start with essential updates to this section. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108819 | CR | Approval | 23.502 CR3208R1 (Rel-17, 'F'): Fix the EN on the priority in the AF session with required QoS procedure | ZTE | Rel-17 | Revision of (Postponed) S2-2107661 from S2#147E. Merged into S2-2109285 | Devaki (Nokia) comments. Zhendong (ZTE): provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== György (Ericsson) proposes to consider this merged into 8478 (similar change is made there). Zhendong (ZTE): agree with György | Merged |
| 8.5 | S2-2108820 | CR | Approval | 23.501 CR3330R1 (Rel-17, 'F'): Clarification on the time synchronization | ZTE | Rel-17 | Revision of (Postponed) S2-2107664 from S2#147E. Approved | Agreed | |
| 8.5 | S2-2108821 | CR | Approval | 23.501 CR3435 (Rel-17, 'F'): Removing the PDU session description in 5G access stratum time synchronization distribution method | ZTE | Rel-17 | Merged into S2-2109290 | Haiyang (Huawei) suggests to merge this paper into S2-2108633 Zhendong (ZTE): is fine with merge proposal ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.5 | S2-2108847 | CR | Approval | 23.501 CR3438 (Rel-17, 'F'): Multiple PTP instances supported in 5GS | Tencent, Tencent Cloud | Rel-17 | r01 agreed. Revised to S2-2109297. | Devaki (Nokia) comments that this CR is a duplicate of 8541. Mark this as merged or the other one as merged. Same technical concerns apply. Chunshan (Tencent) provides r02. Jari (NTT DOCOMO) provides r02 Chunshan (Tencent) provides the r04. Jari (NTT DOCOMO) provides r03 in the previous comment. György (Ericsson) comments and prefers r01. Chunshan (Tencent) response to György (Ericsson). Sang-Jun (Samsung) comments. Devaki (Nokia) can also accept only r01. ==== Revisions Deadline ==== Devaki (Nokia) can accept r01 (objects to other revisions for reasons stated earlier). ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109297 | CR | Approval | 23.501 CR3438R1 (Rel-17, 'F'): Multiple PTP instances supported in 5GS | Tencent, Tencent Cloud | Rel-17 | Revision of S2-2108847r01. Approved | Agreed | |
| 8.5 | S2-2108849 | CR | Approval | 23.502 CR3296 (Rel-17, 'F'): Clarifications regarding TSCTSF discovery and selection | NTT DOCOMO | Rel-17 | Noted | Devaki (Nokia) objects to the CR and its revisions as the proposed approach to define discovery and selection per service is way too complex for little benefit. Qianghua (Huawei) proposes to note this CR Jari (NTT DOCOMO) responds György (Ericsson) suggests to note this document given the SoH outcome on Monday. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108850 | CR | Approval | 23.502 CR3297 (Rel-17, 'F'): Updates on AS time distribution | CATT | Rel-17 | Noted | Devaki (Nokia) has objections to the CR as it is technically wrong - ASTI service cannot use a PTP instance reference as ID. Yuan Tao replies to Devaki (Nokia) and ask for clarification. Jari (NTT DOCOMO) agrees with Nokia, CR is incorrect Sebastian (Qualcomm) objects to the CR (PTP Instance IDs do not make sense for ASTI as commented by others also) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108851 | CR | Approval | 23.503 CR0689 (Rel-17, 'F'): Clafication on bridge information notification | CATT | Rel-17 | r02 agreed. Revised to S2-2109298. | György (Ericsson) comments. Yuan Tao (CATT) provides r01. Mirko (Huawei) comments. Sang-Jun (samsung) confirms 8646 is updated to remove clause 6.2.10 from 23.503. Yuan Tao (CATT) replies to Mirko (Huawei). Jari (NTT DOCOMO) responds to Mirko Yuan Tao (CATT) provides r02. Mirko (Huawei) provides r03. Yuan Tao responses to Mirko (Huawei). ==== Revisions Deadline ==== Yuan Tao (CATT) suggests to approve r02. Mirko (Huawei) is ok with r02. ==== Comments Deadline ==== | Revised |
| 8.5 | S2-2109298 | CR | Approval | 23.503 CR0689R1 (Rel-17, 'F'): Clafication on bridge information notification | CATT | Rel-17 | Revision of S2-2108851r02. Approved | Agreed | |
| 8.5 | S2-2108852 | CR | Approval | 23.501 CR3439 (Rel-17, 'F'): Update on configuration for Sync and Announce reception timeouts | CATT | Rel-17 | Approved | Agreed | |
| 8.5 | S2-2108877 | CR | Approval | 23.501 CR3448 (Rel-17, 'F'): Correction on PTP message handling in Boundary Clock | Intel | Rel-17 | Noted | Chunshan(Tencent) proposes this paper to be merged into paper S2-2108540. Saso (Intel) is happy to discuss on the 8540 thread, but disagrees with the merger. Chunshan (Tencent) comments to Saso (Intel) that your paper is not complete. ==== Revisions Deadline ==== Chunshan (Tencent) objects this CR. ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108933 | CR | Approval | 23.501 CR3456 (Rel-17, 'F'): Clarifications regarding TSCTSF discovery and selection | NTT DOCOMO | Rel-17 | Noted | Devaki (Nokia) proposes to merge this CR with 8971/8476. Sang-Jun (Samsung) also proposes this CR and 8961/8476 should be merged, and corrects the number 8971 to be 8961 in Nokia's comemnt. Jari (NTT DOCOMO) does not agree to merge Qianghua (Huawei) proposes to go with 08961. György (Ericsson) suggests to note this document given the SoH outcome on Monday. ==== Revisions Deadline ==== Devaki (Nokia) proposes to note the document based on Monday SoH outcome (or mark it as merged with 8961). ==== Comments Deadline ==== | Noted |
| 8.5 | S2-2108822 | CR | Approval | 23.502 CR3291 (Rel-18, 'F'): Clarification on the Ntsctsf_QoSandTSCAssistance related service operation | ZTE | Rel-18 | Approved | Agreed | |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=5 | - | |
| 8.6 | S2-2108480 | CR | Approval | 23.503 CR0654R2 (Rel-17, 'F'): Extending MA PDU Session Control information in the PCC Rule | [Ericsson, Lenovo, Motorola Mobility], LG Electronics | Rel-17 | Revision of (Agreed) S2-2107828 from S2#147E. r06 agreed. Revised to S2-2109095, merging S2-2108795 | Rainer (Nokia) asks for clarification. Myungjune (LGE) replies to Rainer (Nokia). Belen (Ericsson) objects to this revision Dario (Qualcomm) comments. Apostolis (Lenovo) has also concerns with this CR. Myungjune (LGE) provides r01. Apostolis (Lenovo) provides further comments. Myungjune (LGE) provides r03. Rainer (Nokia) provides r04. Myungjune (LGE) is ok with r04 Apostolis (Lenovo) is also OK with r04 Belen (Ericsson) provides r05 and objects to previous revision and initial version. Apostolis (Lenovo) responds to Belen. Belen (Ericsson) disagrees with Apostolis proposal. Dario (Qualcomm) supports r04 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.6 | S2-2109095 | CR | Approval | 23.503 CR0654R4 (Rel-17, 'F'): Extending MA PDU Session Control information in the PCC Rule | Ericsson, Lenovo, Motorola Mobility, LG Electronics | Rel-17 | Revision of S2-2108480r06, merging S2-2108795. Approved | Agreed | |
| 8.6 | S2-2108730 | CR | Approval | 23.501 CR3421 (Rel-17, 'F'): 23.501 Clarification on threshold values | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109096. | Dario S. Tonesi (Qualcomm) provides r01 Apostolis (Lenovo) provides r02 Rainer (Nokia) is ok with r02. Hualin (Huawei) is ok with r02. Dario (Qualcomm) is OK with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.6 | S2-2109096 | CR | Approval | 23.501 CR3421R1 (Rel-17, 'F'): Clarification on threshold values | Huawei, HiSilicon, Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2108730r02. Approved | Agreed | |
| 8.6 | S2-2108795 | CR | Approval | 23.503 CR0654R3 (Rel-17, 'F'): Extending MA PDU Session Control information in the PCC Rule | [Ericsson, Lenovo, Motorola Mobility], Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107828 from S2#147E. Merged into S2-2109095 | Rainer (Nokia) asks for clarification. Apostolis (Lenovo) proposes to merge this into 8480. Susan (Huawei) replies to Rainer (Nokia) and is ok to merge to 8480. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=39 | - | |
| 8.7 | S2-2108281 | LS In | Information | LS on GTP-C cause value used for UAS services | CT WG1 (C1-216293) | Rel-17 | Noted | DongYeon (Samsung) proposes NOTE this LS, since no action required from SA2. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2109369 | LS In | Action | LS from CT WG1: LS on EPS requirements for ID_UAS | CT WG1 (C1-217131) | Rel-17 | CC#2: Response drafted in S2-2109342. Final response in S2-2109342. | Replied to | |
| 8.7 | S2-2109342 | LS OUT | Approval | Reply LS on EPS requirements for ID_UAS | SA WG2 | Rel-17 | CC#2: Created at CC#2. Response to S2-2109369. This was left for review at CC#3. CC#3: Approved | Approved | |
| 8.7 | S2-2108431 | CR | Approval | 23.256 CR0031R2 (Rel-17, 'F'): TS 23.256: Rapporteur Editorial CR | Qualcomm Incorporated, Ericsson | Rel-17 | Revision of (Agreed) S2-2107971 from S2#147E. r03 agreed. Revised to S2-2109149. | Guanglei (Huawei) provides r01 Stefano (Qualcomm) provides r02, cannot accept r01 Guanglei (Huawei) provides r03 ==== Revisions Deadline ==== Stefano (Qualcomm) ok with r03. ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109149 | CR | Approval | 23.256 CR0031R3 (Rel-17, 'F'): TS 23.256: Rapporteur Editorial CR | Qualcomm Incorporated, Ericsson, Huawei, Hisilicon | Rel-17 | Revision of S2-2108431r03. Approved | Agreed | |
| 8.7 | S2-2108430 | CR | Approval | 23.256 CR0032 (Rel-17, 'F'): Correction of UUAA when aerial subscription is missing | Ericsson | Rel-17 | r06 agreed. Revised to S2-2109150. | DongYeon (Samsung) asks a question for clarification. Stefano (Qualcomm) provides comments. Ashok (Samsung) comments Shabnam (Ericsson) responds and provides r01. Ashok (Samsung) comments and provides r02 with way forward Stefano (Qualcomm) provides comments, not Ok with r02, has questions on r01. Ashok (Samsung) responds to Stefano (Qualcomm) Guanzhou (InterDigital) can't accept r02. Shabnam (Ericsson) provides r03 addressing Qualcomm comment and adding cosigning company. Tricci (OPPO) provides r04 to update the latest descriptions regarding the actual reason of the indication. Ashok (Samsung) is OK with r04. Dimitris (Lenovo) provides r06 Shabnam (Ericsson) agrees with r06. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109150 | CR | Approval | 23.256 CR0032R1 (Rel-17, 'F'): Correction of UUAA when aerial subscription is missing | Ericsson, Qualcomm Inc. | Rel-17 | Revision of S2-2108430r06. Approved | Agreed | |
| 8.7 | S2-2108438 | CR | Approval | 23.256 CR0033 (Rel-17, 'F'): Correction on C2 authorization procedure | InterDigital | Rel-17 | Noted | Jaewoo (LGE) provides comment. Pallab (Nokia) comments and raises concern with the proposed changes. Dimitris (Lenovo) agrees with the views from Pallab (Nokia) Guanzhou (InterDigital) responds to Jaewoo (LGE) comment. Guanzhou (InterDigital) responds to Pallab(Nokia) comments. Shabnam (Ericsson) expresses concerns and don't believe the CR as is agreeable, comments. Dimitris (Lenovo) comments Guanzhou (InterDigital) provides further response. Guanzhou (InterDigital) provides r01 for consistent service name. ==== Revisions Deadline ==== Pallab (Nokia) comments and proposes to NOTE the CR Shabnam (Ericsson) objects to all versions, proposes to discuss offline further if there is an issue and can be solved via, e.g., Ericsson proposed changes in steps within current procedures. Pallab (Nokia) responds to Jaewoo (LGE) ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108456 | CR | Approval | 23.502 CR3240 (Rel-17, 'F'): UASNF registration and discovery | Samsung | Rel-17 | r02 agreed. Revised to S2-2109151. | Dimitris (Lenovo) provides r01 Shabnam (Ericsson) agrees with Lenovo proposed revision in r01, also asks to update the CR cover sheet to reflect the proposed changes. Ashok (Samsung) provides r02 Dimitris (Lenovo) is ok with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109151 | CR | Approval | 23.502 CR3240R1 (Rel-17, 'F'): UASNF registration and discovery | Samsung | Rel-17 | Revision of S2-2108456r02. Approved | Agreed | |
| 8.7 | S2-2108457 | CR | Approval | 23.256 CR0009R2 (Rel-17, 'F'): UUAA-MM Procedure Updates | Samsung,OPPO | Rel-17 | Revision of (Agreed) S2-2108173 from S2#147E. Noted | Stefano (Qualcomm) objects to this paper since the solution is not necessary, as discussed at the last meeting and offline. Ashok (Samsung) does not agree with Stefano (Qualcomm) and need clarification for objection Stefano (Qualcomm) re-iterates that the solution is not necessary. Ashok (Samsung) responds to Stefano (Qualcomm) Dimitris (Lenovo) agrees with QCOM that solution is not needed and already addressed in stage 3 Ashok (Samsung) responds to Dimitris (Lenovo) Guanzhou (InterDigital) shares the position of Stefano (Qualcomm) Ashok (Samsung) responds to Guanzhou (InterDigital) Ashok (Samsung) is OK to NOTE the paper ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108458 | DISCUSSION | Information | Discussion on UE impact because of change in Aerial subscription. | Samsung | Rel-17 | Noted | Noted | |
| 8.7 | S2-2108542 | CR | Approval | 23.256 CR0035 (Rel-17, 'F'): Clean up for UUAA-MM procedure | LG Electronics | Rel-17 | Confirm CR Number - CR states | Shabnam (Ericsson) comments asking clarification. Jaewoo (LGE) responds to Shabnam (Ericsson) and provides r01. DongYeon (Samsung) comments. Jaewoo (LGE) responds to DongYeon (Samsung) and provides r02. ==== Revisions Deadline ==== DongYeon (Samsung) is okay with r02 and r00, and objects to r01. ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109152 | CR | Approval | 23.256 CR0035R1 (Rel-17, 'F'): Clean up for UUAA-MM procedure | LG Electronics | Rel-17 | Revision of S2-2108542r02. Approved | Agreed | |
| 8.7 | S2-2108564 | CR | Approval | 23.256 CR0037 (Rel-17, 'F'): Clarification for UUAA-SM procedure when UUAA-MM performed | LG Electronics | Rel-17 | Confirm CR Number - CR states | Pallab (Nokia) comments and asks for clarification. Raises concern with some of the changes. Dimitris (Lenovo) comments Jaewoo (LGE) responds to Pallab (Nokia) and Dimitris (Lenovo). Pallab (Nokia) responds to Jaewoo (LGE) Jaewoo (LGE) responds to Pallab (Nokia). Guanglei(Huawei) provides comments. Jaewoo (LGE) responds to Guanglei (Huawei). Guanzhou (InterDigital) comments and provides r01. Guanzhou (InterDigital) corrects its previous comment that no r01 was provided. Shabnam (Ericsson) provides comments and shares others concerns Jaewoo (LGE) responds to Guanzhou (InterDigital) and Shabnam (Ericsson). Guanglei(Huawei) kindly reminds that it is already possible for NEF to receive DNN and S-NSSAI parameters from AF, besides mapping from AF identifier to DNN and S-NSSAI by NEF. Jaewoo (LGE) responds to Pallab (Nokia) and Guanglei (Huawei). Ashok (Samsung) responds to Jaewoo Stefano (Qualcomm) comments, not convinced this solution is needed at all. Jaewoo (LGE) proposes to note this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108703 | CR | Approval | 23.256 CR0011R2 (Rel-17, 'F'): Clarify the implicit subscription during the UUAA procedure | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107959 from S2#147E. Approved | Agreed | |
| 8.7 | S2-2108761 | CR | Approval | 23.256 CR0043 (Rel-17, 'F'): Network Initiated UUAA Revocation | Samsung, InterDigital, SK Telecom, LG Uplus | Rel-17 | Postponed | DongYeon (Samsung) provides r01, AT&T is added in source. Dimitris (Lenovo) comments Pallab (Nokia) agrees with the comments from Dimitris (Lenovo) and also feels that the changes proposed in the CR are not needed Guanglei (Huawei) also thinks this CR is not correct. Guanzhou (InterDigital) responds to Dimitris (Lenovo) and Pallab (Nokia) comments. DongYeon (Samsung) replies to Dimitris (Lenovo) and Pallab (Nokia). DongYeon (Samsung) replies to Guanglei (Huawei) Dimitris (Lenovo) responds DongYeon (Samsung) replies. Guanzhou (InterDigital) further comments. Pallab (Nokia) comments and proposes to NOTE the CR Guanzhou (InterDigital) responds to Pallab (Nokia) and thinks this issue should be addressed in R17. ==== Revisions Deadline ==== Pallab (Nokia) responds to Guanzhou (InterDigital) and maintains objection DongYeon (Samsung) proposes to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2108623 | CR | Approval | 23.256 CR0038 (Rel-17, 'F'): Clarifications on UUAA context during revocation procedure | Samsung | Rel-17 | r01 agreed. Revised to S2-2109153. | Shabnam (Ericsson) provides r01 correcting 'response' to 'respond' Guanglei (Huawei) provides comments. DongYeon (Samsung) is Okay with r01, and replies to Guanglei (Huawei). Guanglei (Huawei) replies. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109153 | CR | Approval | 23.256 CR0038R1 (Rel-17, 'F'): Clarifications on UUAA context during revocation procedure | Samsung | Rel-17 | Revision of S2-2108623r01. Approved | Agreed | |
| 8.7 | S2-2108550 | CR | Approval | 23.256 CR0036 (Rel-17, 'F'): Replace of the term pairing authorization | LG Electronics | Rel-17 | Confirm CR Number - CR states | Jaewoo (LGE) provides r01. Guanglei (Huawei) provides comments and r02 Jaewoo (LGE) responds to Guanglei (Huawei) and is fine with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109154 | CR | Approval | 23.256 CR0036R1 (Rel-17, 'F'): Replace of the term pairing authorization | LG Electronics | Rel-17 | Revision of S2-2108550r02. Approved | Agreed | |
| 8.7 | S2-2108553 | CR | Approval | 23.256 CR0002R1 (Rel-17, 'F'): Clarification and EN resolution for SMF Services | LG Electronics | Rel-17 | Revision of (Noted) S2-2107150 from S2#147E. Remove Revision Marks from CR Cover! r01 agreed. Revised to S2-2109155. | Jaewoo (LGE) provides r01. ==== Revisions Deadline ==== Guanzhou (InterDigital) objects to the original version and is OK with r01. ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109155 | CR | Approval | 23.256 CR0002R2 (Rel-17, 'F'): Clarification and EN resolution for SMF Services | LG Electronics | Rel-17 | Revision of S2-2108553r01. Approved | Agreed | |
| 8.7 | S2-2108628 | CR | Approval | 23.256 CR0039 (Rel-17, 'F'): Clarifications and corrections on UAV Re-authentication and the Networked Remote ID terminology | China Mobile | Rel-17 | r02 agreed. Revised to S2-2109156. | Stefano (Qualcomm) objects to this paper if networked Remote ID is removed. Aihua(CMCC) asks Stefano (Qualcomm) for clarification. Tricci (OPPO) prefers to keep the PDU Session IP and would like to propose to NOTE this CR because the changes are not needed. Guanglei (Huawei) provides comments and thinks at least one change is needed and provides r01. Pallab (Nokia) comments that changes in r01 is also not correct Guanglei (Huawei) replies to Pallab(Nokia) and provides r02 to reflect Pallab's opinion Stefano (Qualcomm) provides responses. Guanglei (Huawei) thanks Stefano's (Qualcomm) clarification and propose to discuss r01 and r02. Tricci (OPPO) thanks Guanglei (Huawei) for the update and withdraws previous objection. Aihua(CMCC) suggests to proceed with r02. ==== Revisions Deadline ==== Stefano (Qualcomm) ok with r02, indicates to chair r00 is not acceptable. ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109156 | CR | Approval | 23.256 CR0039R1 (Rel-17, 'F'): Clarifications and corrections on UAV Re-authentication | China Mobile, Huawei, HiSilicon | Rel-17 | Revision of S2-2108628r02. Approved | Agreed | |
| 8.7 | S2-2108911 | CR | Approval | 23.502 CR3307 (Rel-17, 'F'): Correction on CAA-level UAV ID in AMF UE context | China Mobile | Rel-17 | Noted | Pallab (Nokia) has the similar comments as in 8910. We need to first agree if AMF stores CAA-Level UAV Id in its context Pallab (Nokia) provides r01 where CAA-Level UAV ID is changed to Service Level Device Identity. This is a revision to correct the identifier name. This should not be considered as Nokia's acceptance of the CR. Pallab (Nokia) proposes to NOTE the CR based on objections in 8910. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108699 | CR | Approval | 23.256 CR0040 (Rel-17, 'F'): Correction on UAS NF discovery and UAS NF functionality | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2109157. | Stefano (Qualcomm) expresses concerns on the sentence wrt the use of USS Address for USS discovery and provides R01. Guanglei (Huawei) replies and provides r02 Tricci (OPPO) asks Huawei for the further clarification for the proposed change from this CR Guanglei (Huawei) replies to Tricci(OPPO) Tricci (OPPO) thanks Guanglei (Huawei) reply and provides suggestion for the changes. Guanglei (Huawei) provides r03 Dimitris (Lenovo) has a question on r03 Pallab (Nokia) asks for clarification on r03 Guanglei (Huawei) replies to Pallab(Nokia) and Demitris(Lenovo) Tricci (OPP) understands the concern from Pallab (Nokia) and proposes further suggestions to the revised text. Guanglei (Huawei) provides r04 to revise the UAS NF functionality. Pallab (Nokia) comments. Guanglei(Huawei) replies to Pallab (Nokia). Guanglei(Huawei) provides r05 to remove the text about UAS NF storing subscription from USS Tricci (OPPO) responds to Pallab (Nokia) comments. Pallab (Nokia) is OK with r05. ==== Revisions Deadline ==== Tricci (OPPO) agrees to approve r05. ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109157 | CR | Approval | 23.256 CR0040R1 (Rel-17, 'F'): Correction on UAS NF discovery and UAS NF functionality | Huawei, HiSilicon | Rel-17 | Revision of S2-2108699r05. Approved | Agreed | |
| 8.7 | S2-2108909 | CR | Approval | 23.256 CR0044 (Rel-17, 'F'): Corrections on usage of Nnef_AFsessionWithQoS service for UAS | China Mobile | Rel-17 | Approved | Guanglei(Huawei) ask for clarification. Yi (China Mobile) reponds to Guanglei. ==== Revisions Deadline ==== Guanglei (Huawei) thanks Yi's clarification and is fine with r00 ==== Comments Deadline ==== | Agreed |
| 8.7 | S2-2108700 | CR | Approval | 23.501 CR3416 (Rel-17, 'F'): Correction on UAS NF discovery and update UAS related AF and NEF service | Huawei, HiSilicon | Rel-17 | Confirm CR Number - CR states | Shabnam (Ericsson) comments that we need to first agree if USS information is to be used or not for UAS NF discovery. If this mechanism is kept, then we need to convert the NOTE into normative as the text is normative in the NOTE. Guanglei(Huawei) replies to Shabnam (Ericsson). Ashok (Samsung) comments Tricci (OPPO) provides comments. Pallab (Nokia) comments and suggests that capability of AMF/SMF to discover UAS NF/NEF based on UE provided USS address may be required in future. Tricci (OPPO) would like to reiterate our preference to keep the existing NOTE - no issue to leverage the AF address (e.g. FQDN) to discover UAS NF. Stefano (Qualcomm) asks whether there is a revision or what. Guanglei(Huawei) provides r01 Pallab (Nokia) is OK with r01 and points out that cover page is missing CR number. Pallab (Nokia) provides r02 to change the normative text in NOTE 'may' to 'can'. Also with cover page changes. Dimitris (Lenovo) has concerns with using USS address for UAS NF/NEF discovery as it is not a complete solution Pallab (Nokia) reminds that using USS address for UAS NF/NEF discovery is not the only option. It is an additional option that the AMF/SMF can use. Besides NEF already supports registering to NRF with domain names served by the NEF. Shabnam (Ericsson) supports the latest version of the CR and clarifies that the function already exists in the spec as 'may' so changing to 'can' softens requirement. Stefano (Qualcomm) proposes to postpone 8700 and 8701 together with 8724 until we have a complete view of the options and solutions. Guanglei (Huawei) proposes to accept r01 ==== Revisions Deadline ==== Shabnam (Ericsson) and the NOTE should not have 'may' normative text, should fix that too and go with latest revision. We still stay 'status quo' I believe. Guanglei (Huawei) re-proposes to accept r02 Tricci (OPPO) supports to accept r02 ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109158 | CR | Approval | 23.501 CR3416R1 (Rel-17, 'F'): Correction on UAS NF discovery and update UAS related AF and NEF service | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108700r02. Approved | Agreed | |
| 8.7 | S2-2108701 | CR | Approval | 23.502 CR3275 (Rel-17, 'F'): Correction on NEF discovery | Huawei, HiSilicon | Rel-17 | Postponed | Pallab (Nokia) indicates that this CR depends on the discussion in S2-2108700 Stefano (Qualcomm) asks whether there is a revision based on discussion of S2-2108700. Pallab (Nokia) provides r01 to make the NOTE a normative text. Dimitris (Lenovo) has concerns with r01 Stefano (Qualcomm) proposes to postpone 8700 and 8701 together with 8724 until we have a complete view of the options and solutions. ==== Revisions Deadline ==== Guanglei (Huawei) is fine to postpone ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2108702 | CR | Approval | 23.256 CR0010R2 (Rel-17, 'F'): Clarification and Correction on AF and NEF authentication service | Huawei, HiSilicon, [Nokia, Nokia Shanghai Bell?], [LG Electronics?] | Rel-17 | Revision of (Agreed) S2-2107963 from S2#147E. Confirm Sources! r01 agreed. Revised to S2-2109159. | Jaewoo (LGE) would like to co-sign and provides r01. Pallab (Nokia) OK with r01 and would like to co-sign. DongYeon (Samsung) comments. Jaewoo (LGE) responds to DongYeon (Samsung). ==== Revisions Deadline ==== Guanglei (Huawei) is ok with r01 ==== Comments Deadline ==== | Revised |
| 8.7 | S2-2109159 | CR | Approval | 23.256 CR0010R3 (Rel-17, 'F'): Clarification and Correction on AF and NEF authentication service | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, LG Electronics | Rel-17 | Revision of S2-2108702r01. Approved | Agreed | |
| 8.7 | S2-2108724 | CR | Approval | 23.256 CR0042 (Rel-17, 'F'): Clarification on discovering a UAS NF/NEF during UUAA-MM/UUAA-SM | Lenovo, Motorola Mobility, | Rel-17 | Noted | Ashok (Samsung) comments and proposed to merge to S2-2108699 Stefano (Qualcomm) does not see the need to merge with S2-2108699 Ashok (Samsung) responds to Stefano (Qualcomm) Guanglei (Huawei) provides comments and provides r01 Tricci (OPPO) also raised concern of the proposal for proposing to leverage CAA Level ID for AMF/SMF to discover UAS NF. Pallab (Nokia) also raises concern on the proposal for using CAA Level ID for AMF/SMF to discover UAS NF. Shabnam (Ericsson) shares similar view as Nokia and would be ok with 'AMF/SMF can discover based on local configuration or use UAS NF capability indication when discovering the NEF using NRF'. Dimitris (Lenovo) can accept r01 provided by Guanglei (Huawei) Pallab (Nokia) proposes to NOTE the CR. As discussed in 8700, we think it is good to keep the option of AMF/SMF discover UAS NF/NEF based on USS address provided by UE. Hence propose to NOTE this CR Dimitris (Lenovo) points as described in 8700 that UAS NF/NEF discovery using USS address is not a complete solution Pallab (Nokia) reminds that it is well defined how NEF is discovered based of AF address Dimitris (Lenovo) responds to Pallab (Nokia) Pallab (Nokia) responds to Dimitris (Lenovo) Dimitris (Lenovo) further responds Stefano (Qualcomm) OK to postpone the discussion on 8724 but will request to postpone 8700 and 8701 also. ==== Revisions Deadline ==== Tricci (OPPO) prefers to NOTE this CR based on the reason below. Stefano (Qualcomm) comments. ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108725 | CR | Approval | 23.502 CR3279 (Rel-17, 'F'): Clarification on discovering a UAS NF/NEF based on the USS address | Lenovo, Motorola Mobility, | Rel-17 | Noted | Pallab (Nokia) indicates that this CR is identical with S2-2108701 and should be merged. Also the CR depends on the discussion in 8700. ==== Revisions Deadline ==== Guanglei (Huawei) proposes to postpone Tricci (OPPO) proposes to NOTE this CR for the same reason for 8724. ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108723 | CR | Approval | 23.256 CR0041 (Rel-17, 'F'): Clarification on USS subscribing to a PDU session status event | Lenovo, Motorola Mobility, | Rel-17 | Postponed | Guanglei (Huawei) ask for clarification. Shabnam (Ericsson) supports the intent of the CR and provides r01 correcting some editorials and normative language. Guanglei(Huawei) provides comments. Dimitris (Lenovo) responds Guanglei(Huawei) kindly reminds that Stage 3 now supports PDU session status event via N33 interface. Dimitris (Lenovo) provides clarifications Guanglei(Huawei) replies Dimitris (Lenovo) responds and provides r02 Guanglei (Huawei) thinks r02 is still not correct Dimitris (Lenovo) disagrees with Huawei comment Guanglei (Huawei) further clarifies Dimitris (Lenovo) suggests to ask CT3 how the PDN Connectivity Status monitoring event is implemented in stage 3 Guanglei (Huawei) replies to Dimitris(Lenovo) ==== Revisions Deadline ==== Guanglei (Huawei) proposes to Postpone or Note Dimitris (Lenovo) is ok to postpone, provided a draft LS out in the drafts folder Guanglei (Huawei) re-proposes to NOTE and objects to send the LS just asking a simple question ==== Comments Deadline ==== | Postponed |
| 8.7 | S2-2108910 | CR | Approval | 23.256 CR0045 (Rel-17, 'F'): Clarification on AMF determined re-authentication | China Mobile | Rel-17 | Noted | Guanzhou (InterDigital) comments. Yi (China Mobile) reponds to Guanzhou and provides r01. Ashok (Samsung) comments whether AMF initiated reauth is valid scenario? Pallab (Nokia) has the same question as Samsung. Yi (China Mobile) replies. Pallab (Nokia) objects to the CR and comments for further clarification Ashok (Samsung) objects to the CR and all the revisions ==== Revisions Deadline ==== Guanzhou (InterDigital) comments and supports r01 Ashok (Samsung) responds to Yi ==== Comments Deadline ==== | Noted |
| 8.7 | S2-2108919 | CR | Approval | 23.256 CR0046 (Rel-17, 'F'): UE behaviour when AMF rejects registration due to missing aerial subscription | Lenovo, Motorola Mobility, | Rel-17 | Noted | Ashok (Samsung) proposes to NOTE Stefano (Qualcomm) fully supports the CR and would like to cosign. Ashok (Samsung) comments Dimitris (Lenovo) responds Ashok (Samsung) responds to Dimitris (Lenovo) and comments this CR is not needed Tricci (OPPO) asks for clarification on why this CR is category 'F'? Pallab (Nokia) suggests that the NOTE text needs to be revised based on updates in 8430 (if 8430 is agreed) Tricci (OPPO) propose to NOTE this CR because it does not provide any added value or solve any issue. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=51 | - | |
| 8.8 | - | - | - | UE POLICY PROVISIONING REQUEST | - | - | Docs:=12 | - | |
| 8.8 | S2-2108992 | LS In | Action | LS from RAN WG2: Reply LS on discovery and relay (re)selection | RAN WG2 (R2-2111583) | Rel-17 | Noted | Deng Qiang (CATT) asks Tao (VC) to move this reply LS to another sub-topic. ==== Revisions Deadline ==== Deng Qiang (CATT) this reply LS can be NOTED. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108284 | LS In | Action | LS from CT WG1: LS on UE POLICY PROVISIONING REQUEST message | CT WG1 (C1-216298) | Rel-17 | Responses drafted in S2-2108339, S2-2108453 and S2-2108582. Postponed | Deng Qiang (CATT) proposed using this thread to discuss CT1 question first, before making CR revisions. Hong (Qualcomm) comments. Changhong (Intel) supports Qiang and Hong's proposal to start from what SA2 specification has. Xiaoyan Shi (Interdigital) shares same view with Changhong, Qiang and Hong. Belen (Ericsson) also shares the view that CT1 should follow SA2 design, and that is defined in 23.503, policy framework. Changhong (Intel) asks Belen a question on Push and Pull mode. Belen (Ericsson) replies to Intel Dimitris (Lenovo) supports a solution that is backwards compatible Susan (Huawei) cannot agree with the new proposal from Belen (Ericsson), and asks questions to Changhong (Intel). Belen (Ericsson) comments to QC interpretation of the ANDSP support indicator. Changhong (Intel) replies to Susan and Belen, proposes to use S2-2108453 as baseline for LS Reply to CT1. Deng Qiang (CATT) comments. Susan (Huawei) replies asks questions for clarification. LaeYoung (LGE) replies to Susan (Huawei). Sherry (Xiaomi) comments. Hannu (Nokia) supports the proposal to take S2-2108453 as the way forward and replies to Sherry. Hong (Qualcomm) replies to Susan. Susan (Huawei) replies to LaeYoung (LGE). Belen (Ericsson) agrees with Susan (Huawei). ==== Revisions Deadline ==== Changhong (Intel) comments and asks to stop challenging the design of having two separate indication for MM and UE Policy Container. Susan (Huawei) replies to Sherry (Xiaomi). Deng Qiang (CATT) provides spec for reference. Yang (OPPO) comments Belen (Ericsson) asks to POSPONE this LS given that no agreement on the answer and related CRs has been reached. Susan (Huawei) replies to Deng Qiang (CATT). Susan (Huawei) replies to Yang (OPPO). Sherry (Xiaomi) replies. Sherry (Xiaomi) replies to Hannu. ==== Comments Deadline ==== | Postponed |
| 8.8 | S2-2109373 | LS In | Action | LS response on PC5 DRX for ProSe | RAN WG2 (R2-2111433) | Rel-17 | Postponed | Postponed | |
| 8.8 | S2-2108339 | LS OUT | Approval | [DRAFT] Reply LS on UE POLICY PROVISIONING REQUEST message | Ericsson | Rel-17 | Response to S2-2108284. Noted | Steve (Huawei) comments on relationship with discussion in S2-2108284, so can't be approved yet. ==== Revisions Deadline ==== Deng Qiang (CATT) this reply LS can be NOTED. Changhong (Intel) objects to this LS OUT paper since no agreement has been reached yet. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108453 | LS OUT | Approval | [DRAFT] LS Reply to C1-216298 on UE Policy provisioning request | Intel Corporation (UK) Ltd | Rel-17 | Response to S2-2108284. Noted | Sherry (Xiaomi) provides r01. Changhong (Intel) provides r02. Hannu (Nokia) provides r03 and points out that a revision of the related CR S2-2108452 is also needed to correct the CR number. ==== Revisions Deadline ==== Changhong (Intel) provides r04 with corrected CR number for the attachment. Belen (Ericsson) objects to this LS reply given that the discussion took place in S2-2108284 and no conclusion was reached on the way forward. Yang (OPPO) suggests to note or postpone the LS as no agreement is made in this meeting Belen (Ericsson) asks Tao (VC) the reason to propose r03 and ask to NOTE this LS as is related to the same topic. Tao (VC) change the status as Noted? For further checking ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108582 | LS OUT | Approval | [DRAFT] Reply LS on UE POLICY PROVISIONING REQUEST message | OPPO | Rel-17 | Response to S2-2108284. Noted | Steve (Huawei) comments on relationship with discussion in S2-2108284. Hannu (Nokia) comments that S2-2108582 and S2-2108453 are draft replies to the same LS and proposes to reply based on S2-2108453r03. ==== Revisions Deadline ==== Changhong (Intel) objects to this paper since no agreement has been reached yet. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108341 | CR | Approval | 23.304 CR0042 (Rel-17, 'F'): ProSE policy provisioning request | Ericsson | Rel-17 | Noted | Steve (Huawei) comments on relationship with discussion in S2-2108284. ==== Revisions Deadline ==== Deng Qiang (CATT) this CR not aligned with way-forward proposal discussed in 8284, and thus should be NOTED. Belen (Ericsson) disagrees that there is a way forward agreed. If this CR is NOTED, then all related CRs to 8284 should also be NOTED Deng Qiang (CATT) is fine to postponed or noted all the CRs related to the CT1 reply LS. Changhong (Intel) objects to this paper since no agreement has been reached yet on the LS OUT. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108342 | CR | Approval | 23.503 CR0668 (Rel-17, 'F'): Removal of the V2X or ProSe policy request at Registration | Ericsson | Rel-17 | Noted | Mirko (Huawei) provides r01. Steve (Huawei) comments on relationship with discussion in S2-2108284. Hong (Qualcomm) comments on r01. LaeYoung (LGE) comments on r01. ==== Revisions Deadline ==== Changhong (Intel) Objects to this paper. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108452 | CR | Approval | 23.304 CR0044 (Rel-17, 'F'): Correction for UE Policy Container | Intel, Qualcomm Incorporated | Rel-17 | Confirm Specification Number - CR states 23.502!. Confirm Spec version used - CR states 17.2.1! r00 agreed. Revised to S2-2109139. | Hannu (Nokia) proposes that the CR must be revised to correct the CR number and possibly also the title as the CR number for this TS 23.502 CR is not drawn from the CR number range of the target specification (but possibly from the CR number range of TS 23.304?) ==== Revisions Deadline ==== Tao(VC) check the status of this paper Changhong (Intel) comments. Changhong (Intel) revised the paper into S2-2109139, the newly allocated CR number is 3314 . Belen (Ericsson) objects to this CR as is related to S2-2108284 that reached no conclusions | Revised |
| 8.8 | S2-2109139 | CR | Approval | 23.502 CR3314 (Rel-17, 'F'): Correction for UE Policy Container | Intel, Qualcomm Incorporated | Rel-17 | Revision of S2-2108452r00. WITHDRAWN | Withdrawn | |
| 8.8 | S2-2108579 | CR | Approval | 23.304 CR0052 (Rel-17, 'F'): UE Policy Container with ProSe Policy Provisioning Request | OPPO | Rel-17 | Noted | Steve (Huawei) comments on relationship with discussion in S2-2108284. Hannu (Nokia) proposes to note this CR and proceed as shown in draft LS out S2-2108453r03. ==== Revisions Deadline ==== Belen (Ericsson) supports this CR, there is no agreement to go for draft LS out S2-2108453. Changhong (Intel) objects to this paper since no agreement has been reached yet on the LS OUT. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108580 | CR | Approval | 23.503 CR0678 (Rel-17, 'F'): UE Policy Container with V2X and ProSe Policy Provisioning Request | OPPO | Rel-17 | Noted | Steve (Huawei) comments on relationship with discussion in S2-2108284. Hannu (Nokia) proposes to note this CR and proceed as shown in draft LS out S2-2108453r03. ==== Revisions Deadline ==== Changhong (Intel) objects to this paper since no agreement has been reached yet on the LS OUT. ==== Comments Deadline ==== | Noted |
| 8.8 | - | - | - | Mobility restriction | - | - | Docs:=3 | - | |
| 8.8 | S2-2108382 | CR | Approval | 23.304 CR0027R2 (Rel-17, 'F'): EN resolve for mobility restriction | [vivo, Samsung, Nokia, Nokia Shanghai Bell,] Ericsson | Rel-17 | Revision of (Agreed) S2-2107978 from S2#147E. Noted | Steve (Huawei) comments on overlap between S2-2108382, S2-2108949 & S2-2108956 Mehrdad (Samsung) suggests to use either S2-2108949 or S2-2108956 as the baseline. Xiaoyan Shi (Interdigital) proposes to discuss mobility restriction in thread of S2-2108956. Judy (Ericsson) is OK to have the discussion in 8956 to avoid same discussion in multiple threads. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108949 | CR | Approval | 23.304 CR0027R3 (Rel-17, 'F'): EN resolve for mobility restriction | Samsung | Rel-17 | Revision of (Agreed) S2-2107978 from S2#147E. Noted | Steve (Huawei) comments on overlap between S2-2108382, S2-2108949 & S2-2108956 Xiaoyan Shi (Interdigital) would suggest to merge this CR to S2-2108956. Mehrdad (Samsung) is OK if we continue discussions in S2-2108956. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108956 | CR | Approval | 23.304 CR0027R4 (Rel-17, 'F'): EN resolve for mobility restriction | Interdigital Inc | Rel-17 | Revision of (Agreed) S2-2107978 from S2#147E. Confirm CR Revision - CR states 2! Noted | Fei (OPPO) comments. Steve (Huawei) comments on overlap between S2-2108382, S2-2108949 & S2-2108956 Xiaoyan Shi (Interigital) replies to Fei. Judy (Ericsson) comments LaeYoung (LGE) provides comment. Fei (OPPO) responds to Xiaoyan (Interdigital) Deng Qiang (CATT) provides comment. Wen (vivo) provides comment. Jianning (Xiaomi) shares the view from Qiang (CATT) Xiaoyan Shi (Interdigital) comments Hong (Qualcomm) comments. Mehrdad (Samsung) comments Judy (Ericsson) provides r01 to reflect the proposal in 8382: L2 Relay UE in Non-allowed not performing relay operations, and emergency/priority access from Remote UE via Relay UE in Non-allowed area to be studied in Rel-18. Xiaoyan Shi (Interdigital) objects r01and provides r02. R01 overthrows agreement in last meeting and Xiaoyan Shi have not identified any technical reason to block NW relay service in Non-allowed area. Judy (Ericsson) is not sure what agreement that Xiaoyan Shi (Interdigital) refers to considering there was a misunderstanding of revisions last meeting as discussed offline. r01 is just one of the alternatives under discussion. Fei (OPPO) comments and provides r03. Wen (vivo) comments and provides r04. Mehrdad (Samsung) provides r05. Steve (Huawei) comments on r05, and in general. ==== Revisions Deadline ==== Hong (Qualcomm) replies. Mehrdad (Samsung) replies. Xiaoyan Shi (Interdigital) replies. Hong (Qualcomm) replies to Xiaoyan. LaeYoung (LGE) accepts only r01 and objects all other versions including r00. Judy (Ericsson) comments accepts only r01 and objects all other versions including r00. Mehrdad (Samsung) objects to r01. We can not agree with that. Fei (OPPO) asks if no revision can be agreed in this meeting, whether the 2107978 is still agreed. Mehrdad (Samsung) is not clear on OPPO's question Steve (Huawei) looks like mutual objections to all revisions, so no update this meeting. Fei (OPPO) thanks for Steve's clarification. ==== Comments Deadline ==== | Noted |
| 8.8 | - | - | - | RDAI message | - | - | Docs:=4 | - | |
| 8.8 | S2-2108522 | CR | Approval | 23.304 CR0019R2 (Rel-17, 'F'): Clarification on Relay Discovery Additional Information message | CATT, ZTE, Intel | Rel-17 | Revision of (Agreed) S2-2107974 from S2#147E. Remove Revision Marks from CR Cover! r08 agreed. Revised to S2-2109160, merging S2-2108488 and S2-2108558 | Zhang (Ericsson) asks clarification Deng Qiang (CATT) replies to Zhang (Ericsson) and provides r01 that merged 8558. Wen (vivo) comments on r01. Fei (OPPO) asks questions. Deng Qiang (CATT) replies to Fei (OPPO) and Wen (vivo). Wen (vivo) replies to Deng Qiang (CATT) Zhang (Ericsson) is OK with r01 and co-sign Zhang (Ericsson) provides comments Steve (Huawei) comments Mehrdad (Samsung) comments on original version and r01. Hong (Qualcomm) replies to Wen. Wen (vivo) is ok to merge to 8522. Deng Qiang (CATT) provides r02 based on Mehrdad (Samsung) constructure proposal. LaeYoung (LGE) provides r03. Fei (OPPO) provides r04. Deng Qiang (CATT) replies to LaeYoung (LGE). LaeYoung (LGE) replies to Deng Qiang (CATT). Hao Dong (ZTE) provides version r05 with some editorial changes in clause 6.5.1.3. Steve (Huawei) provides r07 Hao Dong (ZTE) responds to Zhang (Ericsson). Fei (OPPO) responds to Zhang (Ericsson). Wen (vivo) comments. Xiaoyan Shi (Interdigital) provides comments Deng Qiang (CATT) provides r08. Mehrdad (Samsung) asks a question for clarification Deng Qiang (CATT) replies to Mehrdad (Samsung). Hannu (Nokia) points out that new LS in from RAN2 in S2-2108992 (sent from RAN2 last week) would be related with this. Fei (OPPO) responds to Mehrdad (Samsung) Hannu (Nokia) replies to Mehrdad. Can accept either approach as long as SA2 and RAN2 are aligned. Deng Qiang (CATT) replies to Mehrdad (Samsung) and Hannu (Nokia). ==== Revisions Deadline ==== Zhang (Ericsson) is fine with r08 LaeYoung (LGE) is also fine with r08. LaeYoung (LGE) responds to Zhang (Ericsson). Hong (Qualcomm) comments. ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109160 | CR | Approval | 23.304 CR0019R4 (Rel-17, 'F'): Clarification on Relay Discovery Additional Information message | CATT, ZTE, Intel, Huawei, HiSilicon, Ericsson, Samsung, vivo, LG Electronics | Rel-17 | Revision of S2-2108522r08, merging S2-2108488 and S2-2108558. Approved | Agreed | |
| 8.8 | S2-2108558 | CR | Approval | 23.304 CR0019R3 (Rel-17, 'F'): Clarification on Relay Discovery Additional Information message | Based on [CATT, ZTE, Intel], vivo | Rel-17 | Revision of (Agreed) S2-2107974 from S2#147E. Merged into S2-2109160 | Zhang (Ericsson) provides comments and r01 Hao Dong (ZTE) proposes to merge this CR into S2-2108522 since both of them are based on the same agreed CR (S2-2107974) from the last SA2 meeting. Deng Qiang (CATT) proposes to merge this CR into S2-2108522r01. Mehrdad (Samsung) proposes to merge this CR S2-2108522. Xiaoyan Shi (Interdigital) proposes to merge it to S2-2108522. Wen (vivo) is ok to merge this paper into 8522. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.8 | S2-2108488 | CR | Approval | 23.304 CR0045 (Rel-17, 'F'): TAI announcement procedure | LG Electronics | Rel-17 | Merged into S2-2109160 | Zhang (Ericsson) propose the merge the paper with S2-2108522 LaeYoung (LGE) responds to Zhang (Ericsson). Hong (Qualcomm) replies to Laeyoung. LaeYoung (LGE) responds to Hong (Qualcomm) and is fine to merge this CR to S2-2108522. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.8 | - | - | - | UE-to-Network Relay | - | - | Docs:=16 | - | |
| 8.8 | S2-2108324 | CR | Approval | 23.304 CR0032R1 (Rel-17, 'B'): Security procedures for L3 relaying | Nokia, Nokia Shanghai Bell, Interdigital Inc., LG Electronics | Rel-17 | Revision of (Postponed) S2-2107566 from S2#147E. Postponed | Zhang (Ericsson) provides comments Fei (OPPO) comments this should be postponed until SA3 has documented the detailed procedure. Deng Qiang (CATT) proposed this CR postponed. Steve (Huawei) waiting for SA3 was also my understanding Hannu (Nokia) comments on behalf of CR proponents and agrees to wait for SA3 guidance. ==== Revisions Deadline ==== Steve (Huawei) thanks Hannu for the clarification, should be postponed. ==== Comments Deadline ==== | Postponed |
| 8.8 | S2-2108381 | CR | Approval | 23.304 CR0013R1 (Rel-17, 'F'): Removing the EN of policy control for L3 U2N Relay | OPPO, Ericsson, LG Electronics | Rel-17 | Revision of (Agreed) S2-2107325 from S2#147E. Approved | Agreed | |
| 8.8 | S2-2108451 | CR | Approval | 23.304 CR0012R2 (Rel-17, 'F'): Clarification for the PC5 QoS parameters and PC5 QoS rule | OPPO, Ericsson | Rel-17 | Revision of (Agreed) S2-2107990 from S2#147E. Approved | Steve (Huawei) asks some questions Yali (OPPO) replies to Steve ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 8.8 | S2-2108802 | CR | Approval | 23.304 CR0055 (Rel-17, 'F'): Update on Unicast link profile for UE-to-Network Relay | Huawei, HiSilicon | Rel-17 | Approved | Fei (OPPO) asks questions. Hao Dong (ZTE) comments. Zhang (Ericsson) provides comments Hao Dong (ZTE) responds to Zhang (Ericsson). Steve (Huawei) replies to Fei. Steve (Huawei) comments on explicit reference for direct comms ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 8.8 | S2-2108523 | CR | Approval | 23.304 CR0046 (Rel-17, 'F'): Resolve some ENs | CATT | Rel-17 | Noted | Fei (OPPO) comments. Deng Qiang (CATT) this CR can be NOTED as it is covered by other CRs. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108801 | CR | Approval | 23.304 CR0054 (Rel-17, 'F'): Updates and alignments based on further RAN WG2 feedback | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2109161, merging S2-2108560 | Zhang (Ericsson) provides comments and ask for clarification Wen (vivo) provides comments Steve (Huawei) replies Steve (Huawei) comments Xiaoyan Shi (Interdigital) have same question with Zhang Fu Hong (Qualcomm) replies to Steve. Deng Qiang (CATT) comments. Fei (OPPO) comments. Steve (Huawei) provides r01 Hong (Qualcomm) comments. Hannu (Nokia) comments and provides r02. Steve (Huawei) provides r03 ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r03 ==== Comments Deadline ==== Hannu (Nokia) thanks Steve and supports r03 | Revised |
| 8.8 | S2-2109161 | CR | Approval | 23.304 CR0054R1 (Rel-17, 'F'): Updates and alignments based on further RAN WG2 feedback | Huawei, HiSilicon | Rel-17 | Revision of S2-2108801r03, merging S2-2108560. Approved | Agreed | |
| 8.8 | S2-2108559 | CR | Approval | 23.304 CR0047 (Rel-17, 'F'): Registration Procedure to enter CM_CONNECTED for L2 relay | Vivo | Rel-17 | Noted | Fei (OPPO) commets. Wen (vivo) replies. Judy (Ericsson) comments. Wen (vivo) replies to Judy (Ericsson). Judy (Ericsson) responds to Wen (vivo) Deng Qiang (CATT) comments. Wen (vivo)responds to Judy (Ericsson) and Deng Qiang (CATT) Fei (OPPO) comments Wen (vivo)responds to Fei(OPPO) Hong (Qualcomm) repleis to Wen. Jianning (Xiaomi) provides view Wen (vivo) repleis to Hong (Qualcomm). Hong (Qaulcomm) replies to Wen. Wen (vivo) replies to Hong (Qaulcomm). Wen (vivo) further provides r01. Hannu (Nokia) still can't see the justification for this CR even in r01. Proposes to note the CR. Wen (vivo) replies to Hannu (Nokia) and don't agree with NOTE . Hong (Qualcomm) comments. Wen (vivo) replies to Hong. ==== Revisions Deadline ==== Hong (Qualcomm) replies to Wen. Wen (vivo) replies to Hong (Qualcomm). Judy (Ericsson) also propose to NOTE this paper which is based on a misundersanding of the spec. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108560 | CR | Approval | 23.304 CR0048 (Rel-17, 'F'): Clarification on CM_CONNECTED state for L2 relay | Vivo | Rel-17 | Merged into S2-2109161 | Deng Qiang (CATT) propose to be merged with S2-2108801. Steve (Huawei) Should be NOTED or considered merged to S2-2108801. Wen (vivo) is ok to merge this paper to S2-2108801. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.8 | S2-2108578 | CR | Approval | 23.304 CR0051 (Rel-17, 'F'): PC5 link release and CM state update for L2 U2N relay | OPPO | Rel-17 | r07 agreed. Revised to S2-2109162. | LaeYoung (LGE) provides r01. Wen (vivo) comments. Fei (OPPO) provides r02. Wen (vivo) provides r03. Lars (Sony) asks questions Fei (OPPO) responds to Lars (Sony). Steve (Huawei) comments Wen (vivo) replies to Steve (Huawei) Hong (Qualcomm) comments. Steve (Huawei) thanks for the clarifications Wen (vivo) replies to Hong (Qualcomm). Fei (OPPO) comments. Fei (OPPO) responds and provides r04. Wen (vivo) comments and provides r05. Fei (OPPO) responds and provides r06. Steve (Huawei) provides r07 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109162 | CR | Approval | 23.304 CR0051R1 (Rel-17, 'F'): PC5 link release and CM state update for L2 U2N relay | OPPO | Rel-17 | Revision of S2-2108578r07. Approved | Agreed | |
| 8.8 | S2-2108722 | CR | Approval | 23.304 CR0053 (Rel-17, 'F'): Clarification on Parameters Used in UE-to-Network Relay Discovery Message | ZTE | Rel-17 | Noted | Fei (OPPO) comments. Hao Dong (ZTE) responds to Fei (OPPO). Fei (OPPO) responds to Hao (ZTE) LaeYoung (LGE) provides comment. Hao Dong (ZTE) thanks for clarification and confirms the CR could be NOTED. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108804 | CR | Approval | 23.304 CR0031R2 (Rel-17, 'F'): PDU Session release for L3 U2N Relay on authorisation revocation | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107987 from S2#147E. Noted | Judy (Ericsson) comments Steve (Huawei) replies Mehrdad replies to Huawei and Ericsson. Judy (Ericsson) comments the update in 8804 seems not absolutely necessary, and provides r01 as an alternative Steve (Huawei) is ok with r01. Hannu (Nokia) provides even simpler r02 and comments. Steve (Huawei) comments ==== Revisions Deadline ==== Hannu (Nokia) complains about premature revision deadline and shows what was left not done in r01. Hannu (Nokia) requests to disregard his previous comment on 8804 as document 8951 was targeted. Sorry for confusion when rushing to meet the deadline (and still failed) Steve (Huawei) wrong CR? Hannu (Nokia) replies to Steve that the CR is probably right but my one of my two comments with the same words was wrong ?? Judy (Ericsson) assumes this paper can be NOTED based on the discussion, i.e. 7987 agreed in SA2#147E will be kept unchanged. Steve (Huawei) can be NOTED, thanks for the discussion. ==== Comments Deadline ==== | Noted |
| 8.8 | S2-2108807 | DISCUSSION | Agreement | Discussion on Dual PDU session for the IPsec connection to N3IWF. | Sony | Rel-17 | Noted | Noted | |
| 8.8 | S2-2108816 | CR | Approval | 23.304 CR0057 (Rel-17, 'F'): N3IWF connection via Dual PDU sessions | Sony | Rel-17 | r02 agreed. Revised to S2-2109163. | Yali (OPPO) comments Lars (Sony) provides r01 Steve (Huawei) comments, let's not add ENs now! Zhang (Ericsson) provides r02 Lars (Sony) r02 looks good. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109163 | CR | Approval | 23.304 CR0057R1 (Rel-17, 'F'): N3IWF connection via Dual PDU sessions | Sony | Rel-17 | Revision of S2-2108816r02. Approved | Agreed | |
| 8.8 | - | - | - | Miscellaneous corrections | - | - | Docs:=16 | - | |
| 8.8 | S2-2108414 | CR | Approval | 23.502 CR3232 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | r01 agreed. Revised to S2-2109164. | Steve (Huawei) asks questions Judy (Ericsson) provides r01 and responds to Steve (Huawei) ==== Revisions Deadline ==== Steve (Huawei) is ok with r01. ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109164 | CR | Approval | 23.502 CR3232R1 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | Revision of S2-2108414r01. Approved | Agreed | |
| 8.8 | S2-2108489 | CR | Approval | 23.501 CR3378 (Rel-17, 'F'): Fix reference for Naf_ProSe | LG Electronics | Rel-17 | r02 agreed. Revised to S2-2109165. | Fei (OPPO) comments. LaeYoung (LGE) provides r01. Judy (Ericsson) provides r02 Fei (OPPO) is ok with r01 and r02. LaeYoung (LGE) is fine with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109165 | CR | Approval | 23.501 CR3378R1 (Rel-17, 'F'): Fix reference for Naf_ProSe | LG Electronics | Rel-17 | Revision of S2-2108489r02. Approved | Agreed | |
| 8.8 | S2-2108561 | CR | Approval | 23.304 CR0049 (Rel-17, 'F'): Miscellaneous clarifications and corrections | Vivo | Rel-17 | r01 agreed. Revised to S2-2109166. | Hao Dong (ZTE) provides revision r01. Wen (vivo) is ok with r01. Hannu (Nokia) provides r02. E-UTRAN should be kept as it is included for cross-carrier operation. Wen (vivo) replies to Hannu and comments on r02. Steve (Huawei) comments on E-UTRAN ==== Revisions Deadline ==== Wen (vivo) proposes r01 should be agreed and can live with r00. Hao Dong (ZTE) supports r01. Steve (Huawei) supports r01. Fei (OPPO) supports r01 as well. ==== Comments Deadline ==== Hannu (Nokia) asks for technical explanation why r02 is not correct? | Revised |
| 8.8 | S2-2109166 | CR | Approval | 23.304 CR0049R1 (Rel-17, 'F'): Miscellaneous clarifications and corrections | Vivo | Rel-17 | Revision of S2-2108561r01. Approved | Agreed | |
| 8.8 | S2-2108577 | CR | Approval | 23.304 CR0050 (Rel-17, 'F'): Clarification on the ID for Group discovery | OPPO | Rel-17 | r03 agreed. Revised to S2-2109330. | Zhang (Ericsson) provides comments and r01 and co-sign the paper Fei (OPPO) is ok with r01. Hao Dong (ZTE) comments. Fei (OPPO) responds to Hao (ZTE) and provides r02. Hao Dong (ZTE) thanks for the revision and is fine with r02. Fei (OPPO) responds to Zhang (Ericsson). Zhang (Ericsson) provides r03 Hao Dong (ZTE) comments on r03. Steve (Huawei) asks for clarification on optional. Fei (OPPO) responds to Steve (Huawei) Steve (Huawei) thanks, quick follow up. Steve (Huawei) thanks for the clarification. ==== Revisions Deadline ==== Changhong (Intel) comments on the 'Reason for Change'. Fei (OPPO) responds to request from Changhong (Intel) Changhong (Intel) asks to keep it open for CC#2. I am OK with Fei proposed text for the Reason for Change and ask Fei to provide a revision. Fei (OPPO) provides r03+ version in the drafts folder to add one sentence in the reason for change. ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109330 | CR | Approval | 23.304 CR0050R1 (Rel-17, 'F'): Clarification on the ID for Group discovery | OPPO, Ericsson | Rel-17 | Revision of S2-2108577r03. Approved | Agreed | |
| 8.8 | S2-2108985 | CR | Approval | 23.304 CR0059 (Rel-17, 'F'): User Info ID clarifications | Philips International B.V, Ericsson, Interdigital Inc. | Rel-17 | r03 agreed. Revised to S2-2109167. | Steve (Huawei) comments Hao Dong (ZTE) comments. Walter Dees (Philips) responds to the comments from Huawei and ZTE Hong (Qualcomm) comments. Walter (Philips) provides comments and requests clarification. Fei (OPPO) comments. Xiaoyan Shi (Interdigital) provides r01. Changhong (Intel) provides r02. Walter Dees (Philips) prefers r00 or r01 Walter Dees (Philips) provides revision r03. ==== Revisions Deadline ==== Changhong (Intel) is OK with r03. Steve (Huawei) supports r02, stage 3 in general is fine. R03 is too specific. Zhang (Ericsson) is OK with r00, 01, 03 Steve (Huawei) comments. Steve (Huawei) clarifies can live with other versions, but prefers r02 ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109167 | CR | Approval | 23.304 CR0059R1 (Rel-17, 'F'): User Info ID clarifications | Philips International B.V, Ericsson, Interdigital Inc. | Rel-17 | Revision of S2-2108985r03. Approved | Agreed | |
| 8.8 | S2-2108803 | CR | Approval | 23.304 CR0056 (Rel-17, 'F'): Clarification on subscription information to 5G ProSe | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109168. | Judy (Ericsson) provide r01 Guanglei (Huawei) replies to Judy(Ericsson) Mehrdad (Samsung) also agrees with r01 from Ericsson. Guanglei(Huawei) replies to Mehrdad(Samsung). Hannu (Nokia) supports r01 as the initial version is not correct. ==== Revisions Deadline ==== Guanglei (Huawei) is fine with r01 ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109168 | CR | Approval | 23.304 CR0056R1 (Rel-17, 'F'): Clarification on subscription information to 5G ProSe | Huawei, HiSilicon | Rel-17 | Revision of S2-2108803r01. Approved | Agreed | |
| 8.8 | S2-2108948 | CR | Approval | 23.304 CR0058 (Rel-17, 'F'): Clarification about path selection policy | Xiaomi | Rel-17 | r01 agreed. Revised to S2-2109169. | Zhang (Ericsson) provides comments Steve (Huawei) comments Mehrdad (Samsung) provides r01 and co-sources r01 Hong (Qualcomm) comments. Changhong (Intel) has concern with r00, but can live with r01. Sherry (Xiaomi) comments. Fei (OPPO) comments. Mehrdad (Samsung) replies to Huawei. Hong (Qualcomm) replies to Steve. Sherry (Xiaomi) replies Steve (Huawei) thanks everyone. ==== Revisions Deadline ==== Zhang (Ericsson) is OK with r01 Steve (Huawei) is ok with r01. Mehrdad (Samsung) supports r01. r01 is OK with us but objects to the original version. ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109169 | CR | Approval | 23.304 CR0058R1 (Rel-17, 'F'): Clarification about path selection policy | Xiaomi, Samsung | Rel-17 | Revision of S2-2108948r01. Approved | Agreed | |
| 8.8 | S2-2108951 | CR | Approval | 23.304 CR0038R1 (Rel-17, 'F'): Update to Groupcast mode 5G ProSe Direct Communication | Samsung, LG Electronics, Interdigital Inc. | Rel-17 | Revision of (Postponed) S2-2107713 from S2#147E. r01 agreed. Revised to S2-2109170. | Zhang (Ericsson) provides comments Fei (OPPO) comments. Mehrdad (Samsung) provides r01. Zhang (Ericsson) is OK with r01 Fei (OPPO) is fine with r01. ==== Revisions Deadline ==== Hannu (Nokia) complains about premature revision deadline and shows what was left not done in r01. Mehrdad (Samsung) suggest move forward with r01 and do any other changes in the next meeting. ==== Comments Deadline ==== | Revised |
| 8.8 | S2-2109170 | CR | Approval | 23.304 CR0038R2 (Rel-17, 'F'): Update to Groupcast mode 5G ProSe Direct Communication | Samsung, LG Electronics, Interdigital Inc. | Rel-17 | Revision of S2-2108951r01. Approved | Agreed | |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=90 | - | |
| 8.9 | - | - | - | LSs in and related documents | - | - | Docs:=9 | - | |
| 8.9 | S2-2108278 | LS In | Action | LS from CT WG1: LS on maximum number of MBS sessions that can be associated to a PDU session | CT WG1 (C1-216247) | Rel-17 | Response drafted in S2-2108404. Final response in S2-2109171 | Replied to | |
| 8.9 | S2-2108934 | CR | Approval | 23.247 CR0070 (Rel-17, 'F'): Maximum of 4 Multicast sessions in one associated PDU session | Qualcomm Incorporated | Rel-17 | Postponed | Miguel (Qualcomm) proposes as author to postpone this CR in favor of outgoing LS, as per offline discussion. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2108404 | LS OUT | Approval | [DRAFT] Reply LS on maximum number of MBS sessions that can be associated to a PDU session | Ericsson | Rel-17 | Response to S2-2108278. r06 agreed. Revised to S2-2109171. | Robbie (Ericsson) provides r01 based on offline CC discussion. Thomas (Nokia) provides r02. Robbie (Ericsson) provides r03. Xiaoyan (CATT) provides r04. Robbie asks Xiaoyan (CATT). Xiaoyan (CATT) provides r05. Robbie (Ericsson) provides r06. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109171 | LS OUT | Approval | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | SA WG2 | Rel-17 | Revision of S2-2108404r06. Approved | Approved | |
| 8.9 | S2-2108991 | LS In | Action | LS from RAN WG2: Further reply on MBS broadcast service continuity | RAN WG2 (R2-2111511) | Rel-17 | Noted | Thomas (Nokia) suggest to Note this LS because the issue is addressed in outgoing LS S2-2108670 ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2109002 | LS In | Action | LS from RAN WG3: Reply LS on MBS broadcast service continuity and MBS session identification | RAN WG3 (R3-215977) | Rel-17 | Postponed | Postponed | |
| 8.9 | S2-2109009 | LS In | Action | LS from RAN WG3: LS on Feedback on data forwarding solutions for MBS | RAN WG3 (R3-216195) | Rel-17 | Response drafted in S2-2109013. Postponed | Postponed | |
| 8.9 | S2-2109013 | LS OUT | Approval | [DRAFT] Reply LS on Feedback on data forwarding solutions for MBS | Nokia | Rel-17 | Created at CC#1. Response to S2-2109009. CC#2: r04 agreed. Revised to S2-2109351. | Thomas (Nokia) provides original version (r00) Pau (Ericsson) objects to r00. Thomas(Nokia) replies to Paul. Provides r01 Paul (Ericsson) provides r02 and objects to r01. ==== Revisions Deadline ==== LiMeng (Huawei) provides r03 for this LS. Paul (Ericsson) provides r04. Thomas(Nokia) comments that timely r02 or late r03 are acceptable, but not late r04. Paul (Ericsson) can only accept r04. Thomas(Nokia) asks Paul if he rejects his own revision r02? Paul (Ericsson) replies Thomas (Nokia), yes, object to r02. Thomas(Nokia) can live with r04. Tao(VC) Let's still check r02 since r04 provided after revision and r02 is provided by Paul ==== Comments Deadline ==== Thomas(Nokia) suggests bringing this to CC#2 as late r04 (but this is an LS) seems finally agreeable LiMeng (Huawei) agrees Thomas to bring this to CC#2. | Revised |
| 8.9 | S2-2109351 | LS OUT | Approval | Reply LS on Feedback on data forwarding solutions for MBS | SA WG2 | Rel-17 | CC#2: Revision of S2-2109013r04. Approved | Approved | |
| 8.9 | - | - | - | User plane management | - | - | Docs:=6 | - | |
| 8.9 | S2-2108397 | CR | Approval | 23.247 CR0009R1 (Rel-17, 'F'): Dynamic Policy Control for 5GC Individual MBS Traffic Delivery | Ericsson | Rel-17 | Revision of (unhandled) S2-2107207 from S2#147E. Merged into S2-2109173 | Judy (Ericsson) propose to merge this paper (i.e. 8397) to 8881. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108398 | CR | Approval | 23.501 CR3055R2 (Rel-17, 'F'): MBS Packet detection and forwarding | Ericsson | Rel-17 | Revision of (unhandled) S2-2107206 from S2#147E. r01 agreed. Revised to S2-2109172, merging S2-2108880 | LiMeng (Huawei) suggests to merge this document into S2-2108880. Judy (Ericsson) propose to use this paper (i.e. 8398) as base and merge 8880 and comments Fenqin (Huawei) comments Judy (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109172 | CR | Approval | 23.501 CR3055R3 (Rel-17, 'F'): MBS Packet detection and forwarding | Ericsson, ZTE | Rel-17 | Revision of S2-2108398r01, merging S2-2108880. Approved | Agreed | |
| 8.9 | S2-2108880 | CR | Approval | 23.501 CR3450 (Rel-17, 'F'): Clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery | ZTE | Rel-17 | Confirm Spec version used - CR states <17.2.0>! Merged into S2-2109172 | Judy (Ericsson) propose to merge this paper (i.e. 8880) to 8398 and comment Zhendong (ZTE): is fine to merge 8880 to 8398 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108881 | CR | Approval | 23.247 CR0068 (Rel-17, 'F'): Clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery | ZTE | Rel-17 | r04 agreed. Revised to S2-2109173, merging S2-2108397 | LiMeng (Huawei) suggests to merge this document into S2-2108397. Judy (Ericsson) propose to use this paper (i.e. 8881) as base and merge 8397 and comments LiMeng (Huawei) is fine with Judy's proposal on S2-2108397, S2-2108398, S2-2108880 and S2-2108881. Judy (Ericsson) provide r01 Fenqin (Huawei) provide r02 Judy (Ericsson) is fine with r02 Thomas (Nokia) provides r03 Mirko (Huawei) provides r04. ==== Revisions Deadline ==== Judy (Ericsson) thanks Mirko (Huawei) for further improvement, I'm fine with r04. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109173 | CR | Approval | 23.247 CR0068R1 (Rel-17, 'F'): Clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery | ZTE, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2108881r04, merging S2-2108397. Approved | Agreed | |
| 8.9 | - | - | - | General | - | - | Docs:=13 | - | |
| 8.9 | S2-2108403 | CR | Approval | 23.247 CR0026R2 (Rel-17, 'F'): Micellaneous corrections | Huawei, HiSilicon, Ericsson, [ZTE,] Tencent, CATT [, vivo], Samsung | Rel-17 | Revision of (Agreed) S2-2107997 from S2#147E. r03 agreed. Revised to S2-2109174, merging S2-2108526 | Youngkyo(Samsung) provides a revision r01. Chen Ying(TD Tech) provides a revision r02. Thomas(Nokia) provides r03. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109174 | CR | Approval | 23.247 CR0026R3 (Rel-17, 'F'): Micellaneous corrections | Huawei, HiSilicon, Ericsson, ZTE, Tencent, CATT , vivo, Samsung, Nokia, Nokia Shanghai-Bell, TD-Tech | Rel-17 | Revision of S2-2108403r03, merging S2-2108526. Approved | Agreed | |
| 8.9 | S2-2108972 | CR | Approval | 23.247 CR0015R2 (Rel-17, 'F'): Clarifications on functional entities | [CATT, Ericsson], Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of (Endorsed) S2-2108001 from S2#147E. r02 agreed. Revised to S2-2109175. | Judy (Ericsson) provide r01 Thomas (Nokia) accepts changes in r01 and provides r02 to add Ericsson back as source ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109175 | CR | Approval | 23.247 CR0015R3 (Rel-17, 'F'): Clarifications on functional entities | CATT, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2108972r02. Approved | Agreed | |
| 8.9 | S2-2108974 | CR | Approval | 23.247 CR0019R2 (Rel-17, 'F'): NRF service operation for broadcast service | [Samsung], Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2108022 from S2#147E. Approved | Judy (Ericsson) comments this paper depends on the MBS SAI discussion what type of location will be used for AMF discovery for broadcast MBS session. Zhendong (ZTE): propsoe to complete the SAI first. then consider this LiMeng (Huawei) wonders the reason why this document is related to SAI. ==== Revisions Deadline ==== Thomas(Nokia) comments that if we do not agree the update but keep the version from the last meeting, it would only fit if we decide to use SAI for routing Judy (Ericsson) responds that proposed removal of cell id is correct thus I'm fine with r00. ==== Comments Deadline ==== | Agreed |
| 8.9 | S2-2108651 | CR | Approval | 23.247 CR0002R2 (Rel-17, 'F'): MBS Session Management vs Configuration | Based on (Ericsson, vivo), vivo | Rel-17 | Revision of (Agreed) S2-2107998 from S2#147E. r01 agreed. Revised to S2-2109176. | LiMeng (Huawei) suggests to keep the 'NULL' state we currently defined. Zhenhua (vivo) responds to LiMeng (Huawei). Judy (Ericsson) comments Zhendong (ZTE): similar view with limeng Zhenhua (vivo) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109176 | CR | Approval | 23.247 CR0002R3 (Rel-17, 'F'): MBS Session Management vs Configuration | Ericsson, vivo | Rel-17 | Revision of S2-2108651r01. Approved | Agreed | |
| 8.9 | S2-2108653 | CR | Approval | 23.247 CR0038R2 (Rel-17, 'F'): Replacement reference architecture figures | Based on (BBC, Ericsson), vivo | Rel-17 | Revision of (Agreed) S2-2108000 from S2#147E. r03 agreed. Revised to S2-2109177. | LiMeng (Huawei) asks whether we need to clarify the interfaces in this document as well. Judy (Ericsson) does not see the need of this paper, cross-line with little half-circle is sufficiently clear. Zhenhua (vivo) answers to Judy (Ericsson) that it is only editorial for good looking without introducing any bad thing. LiMeng (Huawei) provides r01. Thomas (Nokia) provides r02 and asks to ignore it Judy (Ericsson) comment that the 'good-looking' (in Zhenhua's eye) figure may cause confusion that MBSF is between NEF and AF, and provides r03 on top of r01. LiMeng (Huawei) thanks Judy for the revison, and asks a question for clarification. Judy (Ericsson) responds to LiMeng (Huawei) ==== Revisions Deadline ==== Judy (Ericsson) accepts only r03, objects to other revisions including r00 to avoid potential confusion on the relationships between NFs in the architecture ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109177 | CR | Approval | 23.247 CR0038R3 (Rel-17, 'F'): Replacement reference architecture figures | [BBC], Ericsson, vivo | Rel-17 | Revision of S2-2108653r03. Approved | Agreed | |
| 8.9 | S2-2108656 | CR | Approval | 23.247 CR0061 (Rel-17, 'D'): Editorial modification on name of Session Update | Vivo Mobile Communications Co. LTD | Rel-17 | Noted | Judy (Ericsson) comments there is misunderstanding of MBS Session update procedure, and the update is not editorial at all as the CR Cat indicates Zhenhua (vivo) replies to Judy (Ericsson) ==== Revisions Deadline ==== Judy (Ericsson) propse to NOTE this paper and clarify if needed next meeting using a proper CR Cat ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108672 | CR | Approval | 23.247 CR0066 (Rel-17, 'F'): Clarification on Annex A for transport mode | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109178. | Robbie (Ericsson) provides r01. Thomas (Nokia) provides r02. Robbie (Ericsson) is fine with r02. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109178 | CR | Approval | 23.247 CR0066R1 (Rel-17, 'F'): Clarification on Annex A for transport mode | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108672r02. Approved | Agreed | |
| 8.9 | S2-2109014 | LS OUT | Approval | [DRAFT] LS on Interworking with eMBMS for Transport Only Mode | Ericsson | Rel-17 | Created at CC#1. Noted | Robbie (Ericsson) provides r00. LiMeng (Huawei) comments Robbie (Ericsson) responds to LiMeng (Huawei) LiMeng (Huawei) provides r01. ==== Revisions Deadline ==== Thomas(Nokia) raises concerns against r01 and questions need for the LS ==== Comments Deadline ==== | Noted |
| 8.9 | - | - | - | Multicast Session Management | - | - | Docs:=18 | - | |
| 8.9 | S2-2108402 | CR | Approval | 23.247 CR0029R2 (Rel-17, 'F'): Updates on cases that SMF rejects UE join request | [Huawei, HiSilicon,] Ericsson | Rel-17 | Revision of (Agreed) S2-2108007 from S2#147E. Merged into S2-2109179 | Youngkyo(Samsung) proposes to merge this CR into S2-2108500. Judy (Ericsson) agrees to Youngkyo(Samsung)'s merging proposal (8402->8500) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108500 | CR | Approval | 23.247 CR0029R3 (Rel-17, 'F'): Updates on cases that SMF rejects UE join request | Samsung,Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2108007 from S2#147E. r06 agreed. Revised to S2-2109179, merging S2-2108402 | Judy (Ericsson) provides r01 merging 8402 into this paper (i.e. 8500) Youngkyo(Samsung) provides r02 LiMeng (Huawei) provides r03. Judy (Ericsson) is fine with r03 Youngkyo(Samsung) is fine with r03 also Thomas (Nokia) provides r04. Xiaoyan (CATT) provides r05. LiMeng (Huawei) provides r06. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109179 | CR | Approval | 23.247 CR0029R4 (Rel-17, 'F'): Updates on cases that SMF rejects UE join request | Huawei, HiSilicon, Samsung, Ericsson | Rel-17 | Revision of S2-2108500r06, merging S2-2108402. Approved | Agreed | |
| 8.9 | S2-2108879 | CR | Approval | 23.247 CR0067 (Rel-17, 'F'): Fixing the EN and Nmbsmf_MBSSession service operation parameters. | ZTE, Ericsson | Rel-17 | r01 agreed. Revised to S2-2109180. | Thomas (Nokia) provides r01 Judy (Ericsson) is fine with r01 and corrects the doc link ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109180 | CR | Approval | 23.247 CR0067R1 (Rel-17, 'F'): Fixing the EN and Nmbsmf_MBSSession service operation parameters. | ZTE, Ericsson | Rel-17 | Revision of S2-2108879r01. Approved | Agreed | |
| 8.9 | S2-2108666 | CR | Approval | 23.247 CR0063 (Rel-17, 'F'): On the issue of user plane activation | Huawei, HiSilicon | Rel-17 | Noted | Paul (Ericsson) provides comments and objects to this CR in all revisions. Thomas (Nokia) provides r01 Wonders whether Paul has a crystal ball to reject future revisions ?? No crystal ball needed ??, Paul (Ericsson) objects to r01. The acknowledged RAN resource impacts issue is not being addressed and thus the EN can't be removed. ==== Revisions Deadline ==== Paul (Ericsson) objects to this CR in r00. The acknowledged RAN resource impacts issue is not being addressed and thus the EN can't be removed. ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108401 | CR | Approval | 23.247 CR0014R2 (Rel-17, 'F'): Multicast session leave and session release | CATT, [ZTE, Huawei, HiSilicon,] Ericsson | Rel-17 | Revision of (Agreed) S2-2108005 from S2#147E. r01 agreed. Revised to S2-2109181. | Zhendong (ZTE): provides comments Judy (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109181 | CR | Approval | 23.247 CR0014R3 (Rel-17, 'F'): Multicast session leave and session release | CATT, ZTE, Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108401r01. Approved | Agreed | |
| 8.9 | S2-2108504 | CR | Approval | 23.247 CR0055 (Rel-17, 'F'): Minimize multicast service interruption caused by unintended PDU session release | Samsung | Rel-17 | r09 agreed. Revised to S2-2109182. | LaeYoung (LGE) proposes to NOTE this CR because didn't see any value compared to impacts on UE, NG-RAN and CN. Youngkyo(Samsung) replies to LaeYoung (LGE). Judy (Ericsson) comments LaeYoung (LGE) replies to Youngkyo (Samsung). Youngkyo (Samsung) provides a revision r01. LaeYoung (LGE) provides r02. Youngkyo (Samsung) provides comments on r02. LaeYoung (LGE) answers to Youngkyo (Samsung). Judy (Ericsson) provide r03 LaeYoung (LGE) is fine with r03. Youngkyo (Samsung) suggests another wording. LaeYoung (LGE) comments. Zhenhua (vivo) provides r04. Zhendong (ZTE): provides r05 Youngkyo(Samsung) provides r06. Thomas(Nokia) provides r07. Fenqin (Huawei) provides r08. LaeYoung (LGE) asks a Q for clarification on r07/r08 about 'the UE can use an existing PDU Session' part. Xiaoyan (CATT) provides r09. Thomas (Nokia) is fine with r09 and answers questions of LaeYoung LaeYoung (LGE) thanks to Thomas (Nokia) for his answer. ==== Revisions Deadline ==== Youngkyo(Samsung) is okay with r09. LaeYoung (LGE) is fine with r09. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109182 | CR | Approval | 23.247 CR0055R1 (Rel-17, 'F'): Minimize multicast service interruption caused by unintended PDU session release | Samsung | Rel-17 | Revision of S2-2108504r09. Approved | Agreed | |
| 8.9 | S2-2108507 | CR | Approval | 23.247 CR0056 (Rel-17, 'F'): Paging strategy handling for multicast MBS session | Samsung | Rel-17 | Noted | Judy (Ericsson) comments Youngkyo(Samsung) replies. Zhendong (ZTE): provides comments Thomas (Nokia) shares the concern of Zhendong Fenqin (Huawei) comments Youngkyo(Samsung) replies and provide a revision r01. Fenqin (Huawei) responds Fenqin (Huawei) replies Judy (Ericsson) provide r02 including only the group paging in paging strategy handling. Just to remind, all new text should have track changes. Youngkyo(Samsung) provides r03. Judy (Ericsson) provides r04 removing the note on AMF delaying the individual paging Fenqin (Huawei) provide r05 Youngkyo(Samsung) provide r06. ==== Revisions Deadline ==== Judy (Ericsson) accepts r02, r04, r05, objects to other revisions including r00 and responds to Youngkyo(Samsung) Youngkyo(Samsung) replies and accept r03 and r06 and objects the other revision. ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108612 | CR | Approval | 23.247 CR0022R2 (Rel-17, 'F'): Leftover issue for MBS session activation and deactivation | Based on [Huawei, HiSilicon, vivo], CATT | Rel-17 | Revision of (Agreed) S2-2108011 from S2#147E. r06 agreed. Revised to S2-2109183, merging S2-2108654 | Zhenhua (vivo) provides r01 to merge 8654. Judy (Ericsson) ask question Zhendong (ZTE): provides r02 Thomas (Nokia): provides r03 Thomas (Nokia): provides r04, Asks to disregard r03 Fenqin (Huawei): provides r05 Zhenhua (vivo) provides r06 ==== Revisions Deadline ==== Judy (Ericsson) responds to Zhenhua (vivo) and ask question Zhenhua (vivo) responds to Judy (Ericsson) Judy (Ericsson) ask further question Fenqin (Huawei) comments. Judy (Ericsson) comments Fenqin (Huawei) responds. Zhenhua (vivo) replies to Judy (Ericsson) Thomas(Nokia) replies to Judy Judy (Ericsson) responds to Thomas(Nokia) Thomas(Nokia) can accept r04, r05 and r06, objects to earlier revisions including r00 Thomas(Nokia) replies to Judy (Ericsson) Xiaoyan (CATT) sugguest to agree r04 or r00. Fenqin (Huawei) only accept r05 or r06. Tao(VC) we still check r06 to agreeable or not then Zhendong (ZTE): provides response Xiaoyan (CATT) can accept r05 or r06. Judy (Ericsson) responds to Fenqin (Huawei) that NOTE 1 allows both options thus the procedure should clarify both, but can live with r04-r06 to progress ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109183 | CR | Approval | 23.247 CR0022R4 (Rel-17, 'F'): Leftover issue for MBS session activation and deactivation | Huawei, HiSilicon, vivo, CATT | Rel-17 | Revision of S2-2108612r06, merging S2-2108654. Approved | Agreed | |
| 8.9 | S2-2108654 | CR | Approval | 23.247 CR0022R3 (Rel-17, 'F'): Leftover issue for MBS session activation and deactivation | Based on (Huawei, HiSilicon), vivo | Rel-17 | Revision of (Agreed) S2-2108011 from S2#147E. Merged into S2-2109183 | Fenqin (Huawei) suggest to merget this paper into 8612 Zhenhua (vivo) agrees to merge into 8612 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108657 | CR | Approval | 23.247 CR0062 (Rel-17, 'F'): Editorial modification on activation procedure | Vivo Mobile Communications Co. LTD | Rel-17 | r03 agreed. Revised to S2-2109184. | Judy (Ericsson) provide r01 taking out the part overlapping with 8935 (on list of UE to RAN) and remove 'editorial' from the title which is contradictory with Cat F. Thomas (Nokia) comments against this CR Zhenhua (vivo) asks Thomas (Nokia) to reconsider r01 Zhendong (ZTE): provides r02 Thomas (Nokia): provides r03 ==== Revisions Deadline ==== Judy (Ericsson) support Thomas (Nokia) on the removal of 'per UE' in r03. Zhendong (ZTE): is fine with r03 Zhendong (ZTE): clarify Judy (Ericsson) responds to Zhendong (ZTE) Zhendong (ZTE): provides the response. Thomas (Nokia) is fine with r03, objects against r00 and r02 Fenqin (Huawei) we are also fine with r03 ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109184 | CR | Approval | 23.247 CR0062R1 (Rel-17, 'F'): Modification on activation procedure | Vivo Mobile Communications Co. LTD, Ericsson | Rel-17 | Revision of S2-2108657r03. Approved | Agreed | |
| 8.9 | S2-2108935 | CR | Approval | 23.247 CR0047R1 (Rel-17, 'C'): Alignment with RAN WG2 for Multicast paging in service activation | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2107752 from S2#147E. Postponed | Robbie (Ericsson) proposes to postpone this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2108988 | CR | Approval | 23.247 CR0012R2 (Rel-17, 'F'): Multicast session join and session establishment | [CATT, Qualcomm, Huawei, HiSilicon, ZTE, vivo], Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of (Agreed) S2-2108006 from S2#147E. Noted | Zhenhua (vivo) provides r01 Youngkyo(Samsung) provides r02. Judy (Ericsson) provides r03 to remove the indication from SMF to RAN as the MBS session related info (including status) is already provided by MB-SMF. Xiaoyan (CATT) provides r04. ==== Revisions Deadline ==== Youngkyo(Samsung) is okay with r04 and happy to cosign. Thomas(Nokia) objects against r03 and r04 Judy (Ericsson) objects to r00, r01, r02, accept r03 & r04 Thomas(Nokia) replies to Judy ==== Comments Deadline ==== | Noted |
| 8.9 | - | - | - | Local MBS | - | - | Docs:=9 | - | |
| 8.9 | S2-2108399 | CR | Approval | 23.247 CR0010R1 (Rel-17, 'F'): Local MBS service and Location dependent MBS service | Ericsson | Rel-17 | Revision of (unhandled) S2-2107208 from S2#147E. r02 agreed. Revised to S2-2109185. | Zhenhua (vivo) ask Q Judy (Ericsson) responds to Zhenhua (vivo) Thomas(Nokia) suggests to note this CR and check is some related enhancements are required in S2-2108680 Judy (Ericsson) proposes r01: keeping the update in 3.1, 6.2.4 & 6.2.5 in this paper and merge the rest to 8680 to avoid overlapping, and responds to Thomas(Nokia) that 2 out of 3 comments are not valid and the remaining 1 can be discussed. Thomas (Nokia) proposes r02 Judy (Ericsson) thanks Thomas (Nokia) for the revision and is fine with r02 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109185 | CR | Approval | 23.247 CR0010R2 (Rel-17, 'F'): Local MBS service and Location dependent MBS service | Ericsson | Rel-17 | Revision of S2-2108399r02. Approved | Agreed | |
| 8.9 | S2-2108490 | CR | Approval | 23.247 CR0054 (Rel-17, 'F'): Clarification on local multicast | LG Electronics | Rel-17 | Approved | Agreed | |
| 8.9 | S2-2108652 | CR | Approval | 23.247 CR0006R2 (Rel-17, 'F'): Multicast MBS Session: resolving ENs and cleanup | Based on (Ericsson, CATT, vivo, Nokia, Nokia Shanghai-Bell, ZTE), vivo | Rel-17 | Revision of (Agreed) S2-2108002 from S2#147E. Noted | Thomas (Nokia) raises concerns against this CR update. Suggest noting it Zhenhua (vivo) replies to Thomas (Nokia) and ask Thomas to reconsider the position. Thomas (Nokia) replies to Zhenhua. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108679 | DISCUSSION | Agreement | Mobility in local MBS service. | Huawei, HiSilicon | Rel-17 | Noted | Noted | |
| 8.9 | S2-2108680 | CR | Approval | 23.247 CR0021R2 (Rel-17, 'F'): Clarification of the local MBS service | Huawei, HiSilicon, [LG Electronics, Nokia, Nokia Shanghai-Bell, Samsung, ZTE,vivo] | Rel-17 | Revision of (Agreed) S2-2108014 from S2#147E. CC#2: r12 + changes agreed. Revised to S2-2109343, merging S2-2108977 | Fenqin (Huawei) provides r01 with an attempt to merge suggestion from 8977r01 Zhenhua (vivo) ask why 7.2.4.X is removed Thomas (Nokia) comments that new version is incomplete and split into two versions not possible suggest to focus the discussion in the 8977 thread Fenqin (Huawei) provides r02 Thomas Nokia provides r03 Agrees to focus discussion on this thread and regard 8977 as merged. Fenqin (Huawei) provides r04 and suggest to take this as basic for Local MBS discussion Thomas (Nokia) provides r05 Fenqin (Huawei) provides r06 Judy (Ericsson) provide r07 based on r05 Fenqin (Huawei) provide r08 Judy (Ericsson) provide r09 Thomas (Nokia) objects against r07 Thomas (Nokia) objects against r08 Fenqin (Huawei) provides r10 Judy (Ericsson) responds to Thomas (Nokia) Thomas(Nokia) provides r11 Thomas(Nokia) asks Judy to clarify her position regarding autonomous switching at RAN node Judy (Ericsson) responds to Thomas(Nokia) that we do support the intra-RAN mobility but does not see the need to introduce new terms 'autonomous switching' and 'combined service area'. Fenqin(Huawei) provides r12 ==== Revisions Deadline ==== Thomas(Nokia) asks Judy for more clarifications. Nokia objects against r00, r01, r02, r04, r07, r08 and r09 Judy (Ericsson) accepts r07, r09, cannot accept r11 as is and request to remove 'combined service area' and 'autonomous' (see below), objects to other revisions and responds to Thomas(Nokia) Fenqin (Huawei) provides r13, which is based on R12 + change suggested by Judy(Ericsson) Judy (Ericsson) responds to Fenqin (Huawei) Fenqin (Huawei) provides r14 and suggest bring this to CC#2. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109343 | CR | Approval | 23.247 CR0021R4 (Rel-17, 'F'): Clarification of the local MBS service | Huawei, HiSilicon, LG Electronics, Nokia, Nokia Shanghai-Bell,Samsung, ZTE,vivo | Rel-17 | CC#2: Revision of S2-2108680r12 + changes, merging S2-2108977. Approved | Agreed | |
| 8.9 | S2-2108975 | DISCUSSION | Approval | Location based services | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Noted | |
| 8.9 | S2-2108977 | CR | Approval | 23.247 CR0021R3 (Rel-17, 'F'): Clarification of the local MBS service | [Huawei, HiSilicon, LG Electronics,] Nokia, Nokia Shanghai-Bell, [Samsung, ZTE, vivo] | Rel-17 | Revision of (Agreed) S2-2108014 from S2#147E. Merged into S2-2109343 | Thomas (Nokia) provides r01 with an attempt to merge 8680 Fenqin (Huawei) comments and suggest this update focus on the three call flow Thomas (Nokia) provides r02 with more changes discussed with Fenqin Thomas(Nokia) agrees to merge this contribution into 8680 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.9 | - | - | - | MBS PCC | - | - | Docs:=8 | - | |
| 8.9 | S2-2108396 | CR | Approval | 23.247 CR0004R1 (Rel-17, 'F'): Policy Control for MBS Session | Ericsson | Rel-17 | Revision of (Noted) S2-2107193 from S2#147E. Noted | Thomas (Nokia) object against this CR Zhendong (ZTE): similar view with thomas Judy (Ericsson) would like to remind Zhendong (ZTE) and Thomas (Nokia) that, in addition to the unnecessary complexity on the AF and 5GC NFs without any clear benefit (see more in 8407), the current MBS PCC solution does not work for multiple MBS QoS Flows, thus request to reconsider their position. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108405 | LS OUT | Approval | [DRAFT] LS on AF/MBSF handling MBS Session when dynamic PCC is deployed | Ericsson | Rel-17 | Noted | Thomas (Nokia) objects against this LS ==== Revisions Deadline ==== Judy (Ericsson) responds to Thomas (Nokia) that we believe it is part of the SA2 work asking for feedback from WGs (SA4/SA6 in our case), particularly when additional/unreasonable requirements are added to MBSF and AF. ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108407 | DISCUSSION | Agreement | Policy Control for MBS Session . | Ericsson | Rel-17 | Noted | Noted | |
| 8.9 | S2-2108882 | CR | Approval | 23.247 CR0039R1 (Rel-17, 'F'): Calrification on the initial MBS session configuration and update | ZTE | Rel-17 | Revision of (Postponed) S2-2107739 from S2#147E. Noted | Judy (Ericsson) comments that the EN in 7.1.1.3 is removed without providing a working solution. ==== Revisions Deadline ==== Judy (Ericsson) objecst to this paper as commented previously ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108883 | CR | Approval | 23.247 CR0040R1 (Rel-17, 'F'): Update to the Removal of MBS session configuration with PCC and related service operation. | ZTE | Rel-17 | Revision of (Postponed) S2-2107740 from S2#147E. Confirm CR Revision - CR states 0! Noted | Judy (Ericsson) comments this paper is related to general MBS PCC discussion Zhendong (ZTE): clarify this CR is not related to general PCC. ==== Revisions Deadline ==== Judy (Ericsson) objects to this paper as the proposed update is based on a PCC solution that does not work for multiple MBS QoS Flows. ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108983 | CR | Approval | 23.247 CR0050R1 (Rel-17, 'F'): PCC related MBS corrections | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2107780 from S2#147E. r03 agreed. Revised to S2-2109186. | Judy (Ericsson) comments that the EN is removed without providing a working solution. More comments below Thomas (Nokia) replies to Judy and provides r01 Judy (Ericsson) provide r02 and responds Mirko (Huawei) provide r03. Thomas (Nokia) provides r04. ==== Revisions Deadline ==== Judy (Ericsson) accepts r02&r03, object to other revisions including r00. Thomas(Nokia) can accept r03. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109186 | CR | Approval | 23.247 CR0050R2 (Rel-17, 'F'): PCC related MBS corrections | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108983r03. Approved | Agreed | |
| 8.9 | S2-2108600 | CR | Approval | 23.247 CR0059 (Rel-17, 'F'): MBS session update related procedures | CATT | Rel-17 | Noted | Judy (Ericsson) does not see the justification why MBS Session Update with service area update should go via PCF Xiaoyan (Xiaoyan) provides r01. Xiaoyan (CATT) provides r01. Judy (Ericsson) comments there is still no justification provided, and proposed update does not resolve the issue of the current MBS PCC solution. Fenqin (Huawei) also suggest not to touch the update with PCC. Xiaoyan (CATT) provides r02. ==== Revisions Deadline ==== Judy (Ericsson) objects to this paper (all revisions including r00) which does not solve the issue in a systematic way but bring new problem ==== Comments Deadline ==== | Noted |
| 8.9 | - | - | - | MBS SAI | - | - | Docs:=10 | - | |
| 8.9 | S2-2108394 | CR | Approval | 23.247 CR0007R1 (Rel-17, 'F'): Introducing MBS SAI and updating MBS service area | Ericsson | Rel-17 | Revision of (unhandled) S2-2107197 from S2#147E. Postponed | Thomas (Nokia) raises concerns against this CR Robbie (Ericsson) responds to Thomas (Nokia) ==== Revisions Deadline ==== Robbie (Ericsson) proposes to postpone this CR which is related with MBS SAI discussion LiMeng (Huawei) agrees to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2108395 | CR | Approval | 23.502 CR3139R1 (Rel-17, 'F'): Introducing MBS SAI and updating MBS service area | Ericsson | Rel-17 | Revision of (unhandled) S2-2107199 from S2#147E. Postponed | Thomas (Nokia) comments that this CR needs to be postponed LiMeng (Huawei) agrees that this CR needs to be postponed, sorry for not providing a timely comment. Robbie (Ericsson) agrees with LiMeng (Huawei) and Thomas (Nokia) to postpone this CR. ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2108406 | DISCUSSION | Agreement | MBS SAI Discussion. | Ericsson | Rel-17 | Noted | Robbie (Ericsson) proposes to use this paper for MBS SAI discussion to avoid the same discussion in multiple threads and asks company's view on the options discussed in offline CC. Zhendong (ZTE): provides feedback LiMeng (Huawei) suggests a way forward regarding the SAI. Robbie (Ericsson) is supportive for the suggestion from LiMeng (Huawei). Thomas (Nokia): provides feedback Thomas(Nokia) replies to the proposals of Limeng LiMeng (Huawei) replies to Thomas. Robbie (Ericsson) replies to Thomas (Nokia) ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108668 | CR | Approval | 23.247 CR0065 (Rel-17, 'F'): On the support of SAI in Rel-17 MBS | Huawei, HiSilicon | Rel-17 | Postponed | Robbie (Ericsson) raises concerns against this CR ==== Revisions Deadline ==== Robbie (Ericsson) proposes to postpone this CR which is related with MBS SAI discussion LiMeng (Huawei) is fine with postponing this document. ==== Comments Deadline ==== | Postponed |
| 8.9 | S2-2108670 | LS OUT | Approval | [DRAFT] LS on SAI usage | Huawei,HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109187. | LiMeng (Huawei) suggests to provide a revision on this after we have a concrete idea on SAI. Robbie (Ericsson) asks LiMeng (Huawei) whether this one can be used to respond S2-2108991 (R2-2111511) ==== Revisions Deadline ==== LiMeng (Huawei) agrees that the content can be used to respond, but this one is a separated document and suggests to approved it. Tao(VC) let's check to approve r01 then. ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109187 | LS OUT | Approval | LS on MBS broadcast service continuity and MBS session identification | SA WG2 | Rel-17 | Revision of S2-2108670r01. Approved | Approved | |
| 8.9 | S2-2108953 | CR | Approval | 23.247 CR0072 (Rel-17, 'F'): Adding the MBS SAI definition and description | ZTE | Rel-17 | Merged into S2-2109331 | Thomas (Nokia) raises concerns against this CR ==== Revisions Deadline ==== Zhendong (ZTE): proposes this CR is merged to 8965 ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108963 | DISCUSSION | Approval | New identifier for broadcast in SIBs | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Noted | |
| 8.9 | S2-2108965 | CR | Approval | 23.247 CR0074 (Rel-17, 'F'): Broadcast Frequency selection Identifier | Nokia, Nokia Shanghai Bell | Rel-17 | r07 agreed. Revised to S2-2109331, merging S2-2108953 | Robbie (Ericsson) raises concerns against this CR Thomas(Nokia) replies to Robbie Thomas(Nokia) provides r01 maintaining only the general description in an attempt to document agreeable principles Robbie (Ericsson) provides r02 to keep the minimum agreeable scope Zhendong (ZTE): provides r03 Robbie (Ericsson) objects to r03. LiMeng (Huawei) provides r04. Zhendong (ZTE): provides response Robbie (Ericsson) provides r05 based on r04. Thomas (Nokia) provides r06. Zhendong (ZTE): provides r07 ==== Revisions Deadline ==== Robbie (Ericsson) provides r08 to update coversheet. LiMeng (Huawei) is fine with r07 or r08. The coversheet can be modified by Thomas before uploading the documents if r07 is agreed. Robbie (Ericsson) is not fine with r00-r07 due to wrong coversheet. Suggest to bring to CC#2 for coversheet update on top of r07 (as indicated in r08) LiMeng (Huawei) is fine to bring it to CC#2. Thomas (Nokia) is fine with updated cover sheet as in r08 and bringing this to CC#2 Formally we should agree r07 + 'Summary of change is updated to 'Introduce MBS XXX ID (a temporary name).' ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109331 | CR | Approval | 23.247 CR0074R1 (Rel-17, 'F'): Broadcast Frequency selection Identifier | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Huawei, HiSilicon | Rel-17 | Revision of S2-2108965r07, merging S2-2108953. Approved | Agreed | |
| 8.9 | - | - | - | NF Services | - | - | Docs:=7 | - | |
| 8.9 | S2-2108502 | CR | Approval | 23.502 CR3192R2 (Rel-17, 'F'): Correction on NRF service operations for MBS | Samsung | Rel-17 | Revision of (Agreed) S2-2108023 from S2#147E. Noted | Zhendong (ZTE): provides comments Thomas(Nokia) suggest to note this revision ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108601 | CR | Approval | 23.247 CR0060 (Rel-17, 'F'): Updates to NF services for MBS | CATT | Rel-17 | r02 agreed. Revised to S2-2109188. | Zhendong (ZTE): provides comments Thomas (Nokia) provides r01 Xiaoyan (CATT) provides r02 Judy (Ericsson) comments that both 8601 (CATT) and 8867 (Huawei) update clause 9 and there are some overlapping. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109188 | CR | Approval | 23.247 CR0060R1 (Rel-17, 'F'): Updates to NF services for MBS | CATT | Rel-17 | Revision of S2-2108601r02. Approved | Agreed | |
| 8.9 | S2-2108667 | CR | Approval | 23.247 CR0064 (Rel-17, 'F'): Clarification on NF services | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109189. | Judy (Ericsson) comments that both 8867 (Huawei) and 8601 (CATT) update clause 9 and there are some overlapping to be resolved. LiMeng (Huawei) provides r01 to remove the overlapping clauses. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109189 | CR | Approval | 23.247 CR0064R1 (Rel-17, 'F'): Clarification on NF services | Huawei, HiSilicon | Rel-17 | Revision of S2-2108667r01. Approved | Agreed | |
| 8.9 | S2-2108955 | CR | Approval | 23.247 CR0073 (Rel-17, 'F'): Clarification on the input of PCF/NEF/MB-SMF service operation | ZTE | Rel-17 | r02 agreed. Revised to S2-2109190. | Thomas (Nokia) provides r01 Judy (Ericsson) provide r02 with only cleanup in cover sheet. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109190 | CR | Approval | 23.247 CR0073R1 (Rel-17, 'F'): Clarification on the input of PCF/NEF/MB-SMF service operation | ZTE | Rel-17 | Revision of S2-2108955r02. Approved | Agreed | |
| 8.9 | - | - | - | Broadcast | - | - | Docs:=2 | - | |
| 8.9 | S2-2108526 | CR | Approval | 23.247 CR0058 (Rel-17, 'F'): Modification on Broadcast service timeline | TD Tech | Rel-17 | Merged into S2-2109174 | LiMeng (Huawei) suggests to merge this document into the Mega CR S2-2108403. Chen Ying(TD Tech) agrees to LiMeng (Huawei)'s merging this document into the Mega CR S2-2108403. I can give a new version of the Mega CR S2-2108403 later. Thomas (Nokia) proposes to note this contribution ==== Revisions Deadline ==== Chen Ying(TD Tech) The CR has been modifed and merged into the the Mega CR S2-2108403. ==== Comments Deadline ==== | Merged |
| 8.9 | S2-2108617 | CR | Approval | 23.247 CR0051R2 (Rel-17, 'F'): Corrections to MBS Broadcast Session Establishment | Based on [Nokia, Nokia Shanghai Bell, Huawei], CATT | Rel-17 | Revision of (Agreed) S2-2108004 from S2#147E. Noted | Robbie (Ericsson) asks a question Fenqin (Huawei) also question on the 4th change. Thomas (Nokia) provides r01 Judy (Ericsson) provides r02 and comments ==== Revisions Deadline ==== Thomas (Nokia) objects against r02 and comments Judy (Ericsson) does not accept r00&r01, provide late r03 (based on r02) to add 'MBS service area' from AMF to RAN. Thomas(Nokia) replies to Judy and also has concerns against late r03 Fenqin (Huawei) agree with Thomas and object r02 /r03. Xiaoyan (CATT) replies to Judy (Ericsson) and suggest to agree r01. Judy (Ericsson) responds to Fenqin (Huawei) and Xiaoyan (CATT) ==== Comments Deadline ==== | Noted |
| 8.9 | - | - | - | Handover | - | - | Docs:=2 | - | |
| 8.9 | S2-2108655 | CR | Approval | 23.247 CR0035R2 (Rel-17, 'F'): Modification on handover procedures | Vivo Mobile Communications Co. LTD | Rel-17 | Revision of (Endorsed) S2-2108015 from S2#147E. Approved | Agreed | |
| 8.9 | S2-2108931 | CR | Approval | 23.247 CR0069 (Rel-17, 'B'): Multicast Data Forwarding between RAN nodes supporting MBS | Qualcomm Incorporated | Rel-17 | Noted | Zhenhua (vivo) ask Q Paul (Ericsson) provides comments and objects to this CR in all revisions. Miguel (Qualcomm) responds to Paul: my understanding is a compromise way forward was agreed in RAN3? Miguel (Qualcomm) responds to Zhenhua Thomas(Nokia) support the CR and comments on RAN3 status LiMeng (Huawei) considers the CR is helpful and agrees the RAN3 status mentioned by Thomas. Paul (Ericsson) clarifies that there is no agreement in RAN3 on data forwarding at mobility between MBS supporting RAN nodes.. ==== Revisions Deadline ==== LiMeng (Huawei) clarifies and comments that we can keep the 1st added paragraph of the document. Paul (Ericsson) provides comments. Paul (Ericsson) objects r00, the original revision. ==== Comments Deadline ==== | Noted |
| 8.9 | - | - | - | Others | - | - | Docs:=6 | - | |
| 8.9 | S2-2108400 | CR | Approval | 23.247 CR0008R1 (Rel-17, 'F'): Interworking with MBMS over E-UTRAN for broadcast service | Ericsson | Rel-17 | Revision of (Agreed) S2-2107204 from S2#147E. r04 agreed. Revised to S2-2109191. | Thomas (Nokia) provides r01 Robbie (Ericsson) provides r02 Thomas (Nokia) accepts r02 Fenqin (Huawei) provides r03 Robbie (Ericsson) provides r04 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109191 | CR | Approval | 23.247 CR0008R2 (Rel-17, 'F'): Interworking with MBMS over E-UTRAN for broadcast service | Ericsson | Rel-17 | Revision of S2-2108400r04. Approved | Agreed | |
| 8.9 | S2-2108509 | CR | Approval | 23.247 CR0057 (Rel-17, 'F'): Multicast MBS service for SNPN | Samsung | Rel-17 | r01 agreed. Revised to S2-2109192. | Josep (DT) objects to this CR. Youngkyo(Samsung) replies to Josep(DT) and request withdrawal of objection. Zhendong (ZTE): provides comments Youngkyo(Samsung) provides a revision r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.9 | S2-2109192 | CR | Approval | 23.247 CR0057R1 (Rel-17, 'F'): Multicast MBS service for SNPN | Samsung | Rel-17 | Revision of S2-2108509r01. Approved | Agreed | |
| 8.9 | S2-2108945 | DISCUSSION | Agreement | Discussion on support of satellite access in 5MBS. | Xiaomi | Rel-17 | Noted | Sherry (Xiaomi) provides r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.9 | S2-2108946 | CR | Approval | 23.247 CR0071 (Rel-17, 'F'): Clarification on the support of satellite access for Local MBS service and Location dependent MBS service | Xiaomi | Rel-17 | Noted | Sherry (Xiaomi) provides r01. Sherry (Xiaomi) explains that this CR is drafted under the assumption that satellite access is already supported for 5MBS for R17. Thomas(Nokia) suggest noting the CR. Sherry(Xiaomi) has no problem to note the CR as long as we agree to revisit this issue in R18. Jean Yves (Thales) also ok to note the CR as long as we agree to revisit this issue in R18 Relja (TNO) supports to revisit this issue in R18 as part of 'New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2'. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=46 | - | |
| 8.10 | S2-2108258 | LS In | Action | LS from RAN WG2: Reply LS on NAS-based busy indication | RAN WG2 (R2-2108855) | Rel-17 | Revision of S2-2107010 from S2#147E. Noted | Alessio(Nokia) proposes to note this incoming LS as there is no further action for us. Lalith(Samsung) agrees with Alessio and proposes to note this incoming LS as there is no further action for us. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108263 | LS In | Information | LS from CT WG1: Reply LS on NAS-based busy indication | CT WG1 (C1-214917) | Rel-17 | Revision of S2-2107021 from S2#147E. Noted | Alessio(Nokia) proposes to note this incoming LS as there is no action for us. (we are in CC) Lalith(Samsung) agrees with Alessio and proposes to note this incoming LS as there is no further action for us. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108447 | CR | Approval | 23.501 CR3335R2 (Rel-17, 'F'): On Connection Release and Paging Restriction during a Mobility Registration Update in a TA outside the current Registration Area | Based on (Nokia, Nokia Shanghai Bell, Intel), vivo | Rel-17 | Revision of (Agreed) S2-2108152 from S2#147E. Merged into S2-2109308 | Alessio(Nokia) asks to note this CR as it is a revision of an agreed CR that does not need this further revision. Saso (Intel) proposes to MERGE this CR into S2-2108917. Saso (Intel) replies to Alessio. Qian (Ericsson) comments. Xiaowan(vivo) replies and is OK to merge it into 2108917. Saso (Intel) replies to Qian (Ericsson). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108448 | CR | Approval | 23.501 CR3235R2 (Rel-17, 'F'): Enabling of paging reception for 5GS | Based on (Intel, Sony, Ericsson, Apple), vivo | Rel-17 | Revision of (Agreed) S2-2108145 from S2#147E. Merged into S2-2109308 and S2-2109310 | Qian (Ericsson) comments and propose to merge with 8917 and 8941 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108449 | CR | Approval | 23.501 CR3372 (Rel-17, 'F'): MUSIM features for Emergency Registration | Vivo | Rel-17 | Noted | Guillaume (MediaTek Inc.) asks for clarification Alessio(Nokia) comments Qian (Ericsson) comments Xiaowan(vivo) replies alessio(nokia) comments and objects to all CRs on emergency at this meeting as they are not really what we need. Juan Zhang (Qualcomm) provides comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108450 | CR | Approval | 23.502 CR3239 (Rel-17, 'F'): MUSIM features for Emergency Registration | Vivo | Rel-17 | r03 agreed. Revised to S2-2109299. | Alessio(Nokia) requests to note this paper Xiaowan(vivo) replies Alessio(Nokia) Alessio(Nokia) comments that indeed we need to indicate how to not hinder callback in general Lalith(Samsung) seeks clarification. Xiaowan(vivo) replies Lalith(Samsung) Xiaowan (vivo) is fine with Alessio(Nokia)'s update. Saso (Intel) comments Alessio(Nokia)'s update. Xiaowan (vivo) provides r01 and comment for choice1 provided by Saso (Intel) Lalith(Samsung) comments. Saso (Intel) replies to Xiaowan. Object to r01. Lalith(Samsung) is OK. Xiaowan(vivo) replies to Saso (Intel) and seek clarification for your comment Xiaowan(vivo) provides r02 Qian (Ericsson) asks question Saso (Intel) is OK with r02. Editorial fixes needed Xiaowan(vivo) replies to Qian (Ericsson) Xiaowan (vivo) provides r03 to renumber NOTEs. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r03. alessio (Nokia) is fine with r03. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109299 | CR | Approval | 23.502 CR3239R1 (Rel-17, 'F'): MUSIM features for Emergency Registration | Vivo | Rel-17 | Revision of S2-2108450r03. Approved | Agreed | |
| 8.10 | S2-2108483 | DISCUSSION | Discussion | Discussion on paging restrictions and signalling. | LG Electronics | Rel-17 | Noted | Lalith (Samsung) seeks clarification. Myungjune (LGE) replies to Lalith (Samsung) Steve (Huawei) this discussion document should be NOTED. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108484 | CR | Approval | 23.401 CR3672 (Rel-17, 'F'): Clarification on paging restrictions and signalling | LG Electronics | Rel-17 | Merged into S2-2109306 | Steve (Huawei) should be NOTED or marked as merged to S2-2108875 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108485 | CR | Approval | 23.501 CR3377 (Rel-17, 'F'): Clarification on paging restrictions and signalling | LG Electronics | Rel-17 | Merged into S2-2109306 | Steve (Huawei) should be NOTED or marked as merged to S2-2108878 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108791 | DISCUSSION | Information | Discussion About Paging Restriction Information Handling. | Qualcomm Incorporated | Rel-17 | Noted | Steve (Huawei) this discussion document should be NOTED. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108792 | CR | Approval | 23.501 CR3258R1 (Rel-17, 'F'): Clarification on paging restrictions | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2107220 from S2#147E. Merged into S2-2109306 | Alessio(Nokia) proposes to merge this in S2-2108878 Saso (Intel) proposes to use the DISCUSSIONS list to discuss the four options on the table. Steve (Huawei) should be NOTED or marked as merged to S2-2108878 Juan Zhang (Qualcomm) agrees this CR is merged to S2-2108875 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108793 | CR | Approval | 23.401 CR3660R1 (Rel-17, 'F'): Clarification on paging restrictions | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2107219 from S2#147E. Merged into S2-2109306 | Alessio(Nokia) proposes to merge this in S2-2108875 Saso (Intel) proposes to use the DISCUSSIONS list to discuss the four options on the table. Steve (Huawei) should be NOTED or marked as merged to S2-2108875 Juan Zhang (Qualcomm) agrees this CR is merged to S2-2108875. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108794 | CR | Approval | 23.502 CR3287 (Rel-17, 'F'): Clarification on paging restrictions | Qualcomm Incorporated | Rel-17 | r02 agreed. Revised to S2-2109300. | Alessio(Nokia) provides r01 Juan Zhang (Qualcomm) is fine with r01. Steve (Huawei) asks a question Juan Zhang (Qualcomm) replies to Steve (Huawei). Juan Zhang (Qualcomm) provides r02. Steve (Huawei) Juan Zhang (Qualcomm) ==== Revisions Deadline ==== alessio(Nokia)ok with r02. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109300 | CR | Approval | 23.502 CR3287R1 (Rel-17, 'F'): Clarification on paging restrictions | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108794r02. Approved | Agreed | |
| 8.10 | S2-2108797 | DISCUSSION | Agreement | Discussion on Paging Cause Indication in the RRC Inactive Assistance Info. | Sony, Ericsson, Samsung | Rel-17 | Noted | Noted | |
| 8.10 | S2-2108799 | CR | Approval | 23.501 CR3430 (Rel-17, 'F'): Adding Paging Cause Indication for Voice Service Supported in the RRC Inactive AI | Sony, Ericsson, Samsung | Rel-17 | r03 agreed. Revised to S2-2109301. | Alessio(Nokia)provides r01 Juan Zhang (Qualcomm) thinks r01 is good and we support the idea to include the paging cause in RRC_Inactive assistance information. Jianning (Xiaomi) provides comment Lars (Sony) r01 is good Lars (Sony) responds to Jianning Jianning (Xiaomi) replies to Lars (Sony) Lars (Sony) replies to Jianning Steve (Huawei) provides r02 Lars (Sony) provides r03 Jianning (Xiaomi) replies to Lars (Sony), and propose way forward on r04 Lars (Sony) provides r05 Xiaowan (vivo) comments . Lars (Sony) provides r06. Jianning (Xiaomi) comment on r05/06, suggest to go with r04 Steve (Huawei) is the clause consistent before the changes? Lars (Sony) responds to Jianning does not think r04 is the way to go ==== Revisions Deadline ==== Lars (Sony) responds to Jianning. Juan Zhang (Qualcomm) prefers r06. Jianning (Xiaomi) asks clarification to Juan (Qaulcomm) Jianning (Xiaomi) seeks clarification from Lars (Sony) Lars (Sony) provides clarification. Alessio(Nokia) would like to suggest we approve r06 Jianning (Xiaomi) replies to Lars (Sony) , propose new way forward with acceptance that PC indication in RRC Inactive Assistance Information Lars (Sony) asks Jianning to please consider r06. Lars (Sony) asks Jianning to please consider r03 which may be even closer to your r07. Lars (Sony) can we approve either r03 or r06? Jianning (Xiaomi) replies to Lars (Snoy), r06 is not clear version for us, suggest to go with r07 in CC#2 Jianning (Xiaomi) replies to Lars (Sony), the r03 or r06 still contains something that we cannot accept, suggest to go r07 in CC#2 Lars (Sony) I will then ask to approve r03 + update second change with replacing 'The RRC Inactive Assistance Information also includes information ' with 'The Paging Cause Indication for Voice Service is used' Lars (Sony) asks to handle this tdoc in CC#2. Jianning (Xiaomi) agree with lars (Sony)'s new proposal based on r03, by replacing 'The RRC Inactive Assistance Information also includes information ' with 'The Paging Cause Indication for Voice Service is used' ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109301 | CR | Approval | 23.501 CR3430R1 (Rel-17, 'F'): Adding Paging Cause Indication for Voice Service Supported in the RRC Inactive AI | Sony, Ericsson, Samsung, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108799r03. Approved | Agreed | |
| 8.10 | S2-2108800 | CR | Approval | 23.502 CR3288 (Rel-17, 'F'): Paging Cause Indication for Voice Services Supported in the RRC Inactive AI | Sony, Ericsson, Samsung | Rel-17 | r01 agreed. Revised to S2-2109302. | Alessio(Nokia) asks whether we really need this CR and whether this CR is correct. Lars (Sony) responds to Alessio(Nokia). Alessio(Nokia). provides r01 Jianning (Xiaomi) provide r02 Lars (Sony) responds to Jianning and is not ok with r02 Jianning (Xiaomi) replise to Lars (Sony) Xiaowan (vivo) provides r03. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) provides comments to r02 and r03. Jianning (Xiaomi) provide comment Lars (Sony) ask Jianning provide a reference to when 'Paging Cause Supported' in sent in the N2 initial UE context setup during SR Lars (Sony) suggest to approve r01. Juan Zhang (Qualcomm) supports to approve r01. Juan Zhang (Qualcomm) replies to Jianning (Xiaomi) Xiaowan(vivo) is OK to use r01 as basis but replace the change in step 23a by 'If the Multi-USIM UE has indicated support for the Paging Cause Indication for Voice Service feature, and the network supports the Paging Cause Indication for Voice Service, the AMF shall include an indication in the RRC Inactive Assistance Information that the UE supports the Paging Cause Indication for Voice Service to NG-RAN to enable NG-RAN to apply the Paging Cause Indication for Voice Service feature for RAN based paging'. Jianning (Xiaomi) replies to Juan (Qaulcomm) Jianning (Xiaomi) replies to Lars (Sony), that may be the new potential update for SR procedure, if PC indication is not in the RRC inactive AI. Lars (Sony) is ok to approve r01 + the update suggested by Xiaowan. alessio(Nokia) is ok to approve r01 + the update suggested by Xiaowan. this should be discussed in CC#2 then. Lars (Sony) asks to handle this tdoc in CC#2. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109302 | CR | Approval | 23.502 CR3288R1 (Rel-17, 'F'): Paging Cause Indication for Voice Services Supported in the RRC Inactive AI | Sony, Ericsson, Samsung, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108800r01. Approved | Agreed | |
| 8.10 | S2-2108805 | LS OUT | Approval | [DRAFT] LS on Paging Cause Indication for Voice Service Supported in RRC Inactive | Sony | Rel-17 | r01 agreed. Revised to S2-2109303. | Steve (Huawei) provides r01 Lars (Sony) ok with r01 ==== Revisions Deadline ==== Jianning (Xiaomi) trying to provide r02, if it is not too late. Alessio(Nokia)) ok with r01 Jianning (Xiaomi) agree to go r01, as the consensus is made to include PC indication in RRC Inactive Assistance Information ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109303 | LS OUT | Approval | LS on Paging Cause Indication for Voice Service Supported in RRC Inactive assistance information | SA WG2 | Rel-17 | Revision of S2-2108805r01. Approved | Approved | |
| 8.10 | S2-2108808 | CR | Approval | 23.502 CR3289 (Rel-17, 'F'): Example conditions to remove paging restrictions | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109304. CC#2: Noted | Alessio(Nokia) proposes to note this paper as there is no FASMO issue this identifies and solves. Steve (Huawei) fully rejects the comment from Alessio, the exact opposite is true. Lars (Sony) comments Steve (Huawei) comments Lars (Sony)responds to Steve Saso (Intel) comments Steve (Huawei) provides r01 Lars (Sony) provides r02 Steve (Huawei) comments on r02, it removes the useful guidance. R01 is better. Juan Zhang (Qualcomm) prefers r02. Xiaowan (vivo) thinks r02 is OK and provides comment. Steve (Huawei) comments, prefers r01. R02 loses essential guidance. ==== Revisions Deadline ==== Steve (Huawei) objects to r02. alessio(Nokia) can live with r02 but also with no change (all revisions including the original version are non-essential correction, meaning nothing breaks without the change) ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2109304 | CR | Approval | 23.502 CR3289R1 (Rel-17, 'F'): Example conditions to remove paging restrictions | Huawei, HiSilicon | Rel-17 | Revision of S2-2108808r02. CC#2: WITHDRAWN | Withdrawn | |
| 8.10 | S2-2108809 | CR | Approval | 23.401 CR3675 (Rel-17, 'F'): Example conditions to remove paging restrictions | Huawei, HiSilicon | Rel-17 | Noted | Alessio(Nokia) proposes to note this paper as there is no FASMO issue this identifies and solves. Steve (Huawei) fully rejects the comment from Alessio, the exact opposite is true. Lars (Sony) comments Saso (Intel) comments Steve (Huawei) provides r01 Lars (Sony) provides r02 Steve (Huawei) comments on r02, it removes the useful guidance. R01 is better. Juan Zhang (Qualcomm) prefers r02. ==== Revisions Deadline ==== Steve (Huawei) objects to r02. alessio(Nokia) can live with r02 but also with no change (all revisions including the original version are non-essential correction, meaning nothing breaks without the change) R01 is not ok ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108812 | CR | Approval | 23.501 CR3433 (Rel-17, 'F'): Exception of Paging Restriction for important system signalling | Xiaomi | Rel-17 | Merged into S2-2109307 | Lars (Sony) comments on new option (e) and suggest not to add (e). Steve (Huawei) comments Alessio(Nokia) believes the current understanding is that in mode a) the network is not expected to page at all (as the text says) and the UE is not required to monitor paging . in mode A the network should not be in a hurry to configure or reach the UE as anyhow the UE is not available for any MT service in the USIM. the next time the UE comes back to life for the USIM, the network by all means can catch up. proposes to note this CR (there is nothing FASMO here) Jianning (Xiaomi) replies to Lars(Sony) Jianning (Xiaomi) replies to Alessio (Nokia), actully the main issue is for PR-b), c) and d) whether the paging of control plane signaling is allowed or not, several CRs are trying to solve this issue. And people seems to agree the PR-a) is used to restrict all the paging (including paging of control plane signaling). It is too early to NOTE this paper, suggest to discuss further together with other CRs to see what can be achieved. Lalith (Samsung) comments Steve (Huawei) should be NOTED or marked as merged to S2-2108878 Jianning (Xiaomi) is ok to merge into 8878 for futher progress ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108813 | CR | Approval | 23.401 CR3676 (Rel-17, 'F'): Exception of Paging Restriction for important system signalling | Xiaomi | Rel-17 | Merged into S2-2109306 | Alessio(Nokia) asks to note this CR (there is nothing FASMO here) Jianning (Xiaomi) replies to Alessio (Nokia), this CR openly proivdes three possible options to correct the potential issue for PR feature what we have discussed in previous meeting. it is FASMO issue. There are also other CRs to fix this issue. It is too early to NOTE the paper, there is still more time for further discussion to see what we can achieve. Lalith (Samsung) comments Steve (Huawei) should be NOTED or marked as merged to S2-2108875 Jianning (Xiaomi) is ok to merge into 8875 for futher progress ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.10 | S2-2108814 | CR | Approval | 23.502 CR3290 (Rel-17, 'F'): Exception of Paging Restriction for important system signalling | Xiaomi | Rel-17 | Noted | Alessio(Nokia) proposes to note this paper as there is no FASMO issue this identifies and solves Jianning (Xiaomi) replies to Alessio (Nokia), this CR openly proivdes three possible options to correct the potential issue for PR feature what we have discussed in previous meeting. it is FASMO issue. There are also other CRs to fix this issue. It is too early to NOTE the paper, there is still more time for further discussion to see what we can achieve. Saso (Intel) proposes to use the DISCUSSIONS list to discuss the four options on the table. Steve (Huawei) should be NOTED Jianning (Xiaomi) is ok to NOTE, as there is no impact on 502 per discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108815 | DISCUSSION | Discussion | Discussion on exception for paging of control plane signalling when using PR. | Xiaomi | Rel-17 | Noted | Alessio(Nokia) proposes to note this paper as there is no FASMO issue this identifies. Jianning (Xiaomi) replies to Alessio (Nokia), this CR openly proivdes three possible options to correct the potential issue for PR feature what we have discussed in previous meeting. it is FASMO issue. There are also other CRs to fix this issue. It is too early to NOTE the paper, there is still more time for further discussion to see what we can achieve. Steve (Huawei) this discussion document should be NOTED. Jianning (Xiaomi) is ok to NOTE this Discussion paper. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.10 | S2-2108834 | CR | Approval | 23.401 CR3677 (Rel-17, 'F'): Adding Alternative IMSI to the MM Context in the MME | Sony | Rel-17 | r06 agreed. Revised to S2-2109305. | Saso (Intel) points out that the LS IN from RAN2 (8997) indicates their preference for calculating the Alternative IMS in AS, also aligned with CT1. Lars (Sony) comments Steve (Huawei) comments on UE vs network side. Saso (Intel) withdraws comment. Lars (Sony) comment and ask do we need an LS reply?. Qian (Ericsson) provides comments. Lars (Sony) provides r01 Steve (Huawei) LSout would be useful. Saso (Intel) thinks that an LS OUT is not urgent. Lars (Sony) LS OUT should be possible to send from this meeting. Juan Zhang (Qualcomm) thinks it is useful to send the reply LS. Saso (Intel) is not opposed to sending LS OUT from this meeting, but not sure if this is possible. Steve (Huawei) good for me. Lars (Sony) have requested a tdoc number now for an LS. Lars (Sony) We can get an tdoc# only if we have consensus on the LS and it is urgent. Jianning (Xiaomi) supports to try this LSout in this meeting. Juan Zhang (Qualcomm) replies the comment Steve (Huawei) provides r02. Lars (Sony) asks Steve on r02. Steve (Huawei) replies to Lars Saso (Intel) comments on the LS. Lars (Sony) provides r03 fixing the reference Xiaowan(vivo) clarifies the reason of misalignment and propose a way forward Lars (Sony) responds to Xiaowan Xiaowan provide r04 Steve (Huawei) does not like r04 Lars (Sony) comments on r04 and provides r05. Xiaowan(vivo) replies Steve (Huawei) Xiaowan(vivo) replies to Lars (Sony). Steve (Huawei) provides r06 ==== Revisions Deadline ==== Lars (Sony) supports r06. Juan Zhang (Qualcomm) is OK with r06. Xiaowan(vivo) OK with r06. Lars (Sony) When making the final update, I will add Vivo as supporting company. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109305 | CR | Approval | 23.401 CR3677R1 (Rel-17, 'F'): Adding Alternative IMSI to the MM Context in the MME | Sony, Vivo | Rel-17 | Revision of S2-2108834r06. Approved | Agreed | |
| 8.10 | S2-2108875 | CR | Approval | 23.401 CR3678 (Rel-17, 'F'): Clarification on paging restrictions | Nokia, Nokia Shanghai Bell | Rel-17 | r08 agreed. Revised to S2-2109306, merging S2-2108484, S2-2108485, S2-2108792, S2-2108793 and S2-2108813 | Lalith(Samsung) seeks clarification. alessio (Nokia) provides r01 based on offline discussion Myungjune (LGE) provides r02 to update coversheet Lalith (Samsung) provides r03 Krisztian (Apple) provides r04. Jianning (Xiaomi) comments on r03/04 Lalith(Samsung) replies to Jianning (Xiaomi) Myungjune (LGE) comments on r03/r04 Juan Zhang (Qualcomm) asks to co-sign the CR. Lalith(Samsung) replies to Myungjune (LGE) Alessio(Nokia) ok with r04 Myungjune (LGE) replies to Lalith(Samsung) Lalith(Samsung) replies to Myungjune(LGE) Jianning (Xiaomi) share the concerns with Myungjune (LGE) on r03/04 Lalith(Samsung) comments. Jianning (Xiaomi) replies to Lalith (Samsung), provide r05 Myungjune (LGE) provides r06 Lalith(Samsung) is OK with r05 and r06 Steve (Huawei) comments on r04, r05 and r06, provides r07. Jianning (Xiaomi) is ok with r07 Myungjune (LGE) provides r08 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109306 | CR | Approval | 23.401 CR3678R1 (Rel-17, 'F'): Clarification on paging restrictions | Nokia, Nokia Shanghai Bell, LG Electronics, Apple | Rel-17 | Revision of S2-2108875r08, merging S2-2108484, S2-2108485, S2-2108792, S2-2108793 and S2-21088. Approved | Agreed | |
| 8.10 | S2-2108878 | CR | Approval | 23.501 CR3449 (Rel-17, 'F'): Clarification on paging restrictions | Nokia, Nokia Shanghai Bell | Rel-17 | r07 agreed. Revised to S2-2109307, merging S2-2108812 | Lalith(Samsung) seeks clarification. Alessio(Nokia) provides r01 based on offline discussion Myungjune (LGE) provides r02 to update coversheet Lalith (Samsung) provides r03 Krisztian (Apple) provides r04 matching changes in 8875r04. Jianning (Xiaomi) comments on r03/04 Alessio(Nokia) ok with r04. Myungjune (LGE) provides r06 Xiaowan(vivo) comment Myungjune (LGE) provides r07 ==== Revisions Deadline ==== Jianning (Xiaomi) is ok with r07 ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109307 | CR | Approval | 23.501 CR3449R1 (Rel-17, 'F'): Clarification on paging restrictions | Nokia, Nokia Shanghai Bell, LG Electronics, Apple | Rel-17 | Revision of S2-2108878r07, merging S2-2108812. Approved | Agreed | |
| 8.10 | S2-2108917 | CR | Approval | 23.501 CR3235R3 (Rel-17, 'F'): Enabling of paging reception for 5GS | Intel, [Sony, Ericsson, Apple] | Rel-17 | Revision of (Agreed) S2-2108145 from S2#147E. r01 agreed. Revised to S2-2109308, merging S2-2108447 and S2-2108448 | Xiaowan (vivo) provides r01 Lars (Sony)we are fine with r01, and supports the update so the brackets around Sony can be removed. Saso (Intel) is OK with r01. Krisztian (Apple) is fine with r01. Jianning (Xiaomi) is ok with r01 Qian (Ericsson) is fine with r01, and supports the update so the brackets for Ericsson can be removed. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109308 | CR | Approval | 23.501 CR3235R4 (Rel-17, 'F'): Enabling of paging reception for 5GS | Intel, Sony, Ericsson, Apple, vivo | Rel-17 | Revision of S2-2108917r01, merging S2-2108447 and S2-2108448. Approved | Agreed | |
| 8.10 | S2-2108939 | CR | Approval | 23.401 CR3658R1 (Rel-17, 'F'): MUSIM capabilities in Emergency Attach | Intel, [Apple] | Rel-17 | Revision of (Noted) S2-2107101 from S2#147E. r07 agreed. Revised to S2-2109309. | Alessio(Nokia) requests to note this paper Saso (Intel) clarifies that this CR is needed to enable stage 3 work. Qian (Ericsson) comments and supports the CR. Xiaowan (vivo) comments and provides r01. Saso (Intel) comments on r01. Prefers r00. Xiaowan(vivo) replies to Saso (Intel) Saso (Intel) provides r02. Still prefers r00. R01 is not acceptable. Krisztian (Apple) provides r03 (equivalent with r02 but without brackets in Source). We are OK with r00 as well but r01 is not acceptable. Krisztian (Apple) provides r04 that fixes the missing updates to the signaling flow in 5.3.2.1 Lars (Sony) provides r05. Saso (Intel) provides r06. Objects to r05. Lars (Sony) we are ok with r06. Juan Zhang (Qualcomm) is ok with r06. Xiaowan (vivo) provides r07 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r07. Lars (Sony) is fine with r07. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109309 | CR | Approval | 23.401 CR3658R2 (Rel-17, 'F'): MUSIM capabilities in Emergency Attach | Intel, Apple | Rel-17 | Revision of S2-2108939r07. Approved | Agreed | |
| 8.10 | S2-2108941 | CR | Approval | 23.501 CR3237R1 (Rel-17, 'F'): MUSIM capabilities in Emergency Registration | [Apple,] Intel | Rel-17 | Revision of (Noted) S2-2107102 from S2#147E. r03 agreed. Revised to S2-2109310, merging S2-2108448. | Alessio(Nokia) requests to note this paper Saso (Intel) clarifies that this CR is needed to enable stage 3 work. Proposes to keep the discussion on the 8939 thread. Qian (Ericsson) comments and supports the CR. Xiaowan (vivo) comments and provides r01. Saso (Intel) comments on r01. Prefers r00. Krisztian (Apple) provides r02 that matches the changes in 8939r04. Saso (Intel) is OK with r02. Juan Zhang (Qualcomm) is OK with r02. Xiaowan (vivo) provides r03 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r03. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109310 | CR | Approval | 23.501 CR3237R2 (Rel-17, 'F'): MUSIM capabilities in Emergency Registration | Apple, Intel | Rel-17 | Revision of S2-2108941r03, merging S2-2108448. Approved | Agreed | |
| 8.10 | S2-2108942 | CR | Approval | 23.502 CR3124R1 (Rel-17, 'F'): MUSIM capabilities in Emergency Registration | Intel, [Apple] | Rel-17 | Revision of (Postponed) S2-2107103 from S2#147E. r03 agreed. Revised to S2-2109311. | Alessio(Nokia) proposes to note this CR Saso (Intel) clarifies that this CR is needed to enable stage 3 work. Proposes to keep the discussion on the 8939 thread. Nokia sees no reason why this is needed still Saso (Intel) replies to Alessio Qian (Ericsson) comments and supports the CR. Xiaowan (vivo) comments and provides r01. Saso (Intel) comments on r01. Prefers r00. Krisztian (Apple) provides r02 that matches the changes in 8939r04. Saso (Intel) is OK with r02. Juan Zhang (Qualcomm) is OK with r02. Xiaowan (vivo) provides r03 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r03. ==== Comments Deadline ==== | Revised |
| 8.10 | S2-2109311 | CR | Approval | 23.502 CR3124R2 (Rel-17, 'F'): MUSIM capabilities in Emergency Registration | Intel, Apple | Rel-17 | Revision of S2-2108942r03. Approved | Agreed | |
| 8.10 | S2-2108950 | DISCUSSION | Agreement | On the need of MUSIM capabilities for Emergency Attach/Registration. | Intel | Rel-17 | Noted | Noted | |
| 8.10 | S2-2108997 | LS In | Action | LS from RAN WG2: Reply LS on RAN2 agreements for MUSIM | RAN WG2 (R2-2111329) | Rel-17 | Postponed | Postponed | |
| 8.10 | S2-2108998 | LS In | Action | LS from RAN WG2: LS on RAN2 agreements for paging with service indication | RAN WG2 (R2-2111330) | Rel-17 | Postponed | Postponed | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=45 | - | |
| 8.11 | S2-2108274 | LS In | Action | LS from RAN WG1: Reply LS on PDB for new 5QI | RAN WG1 (R1-2106331) | Rel-17 | Revision of S2-2107076 from S2#147E. Noted | Stefan (Ericsson) proposes to NOTE the LS. Sherry (Xiaomi) agrees to NOTE the LS. DongYeon (Samsung) agrees to NOTE this LS. Jean Yves (Thales) ok to NOTE the LS ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108252 | LS In | Action | LS from CT WG1: LS reply on multiple TACs per PLMN | CT WG1 (C1-213965) | Rel-17 | Revision of S2-2106993 from S2#147E. CC#2: Postponed | Postponed | |
| 8.11 | S2-2108255 | LS In | Action | LS from SA WG3: Reply LS on UE location aspects in NTN | SA WG3 (S3-212306) | Rel-17 | Revision of S2-2107002 from S2#147E. CC#2: Postponed | Postponed | |
| 8.11 | S2-2108260 | LS In | Action | LS from RAN WG2: Response LS on Multiple TACs per PLMN | RAN WG2 (R2-2108888) | Rel-17 | Revision of S2-2107015 from S2#147E. CC#2: Postponed | Postponed | |
| 8.11 | S2-2108994 | LS In | Information | LS from SA WG1: Reply LS on Indication of country of UE location and its use in PLMN selection | SA WG1 (S1-214208) | Rel-17 | Noted | DongYeon (Samsung) proposes to NOTE this LS, The content of LS is noticed and the related discussion has done in S2-2108329. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108279 | LS In | Action | Reply LS on UE location aspects in NTN | CT WG1 (C1-216250) | Rel-17 | Response drafted in S2-2108697. Final response in S2-2109337 | Replied to | |
| 8.11 | S2-2108697 | LS OUT | Approval | [DRAFT] Reply LS on UE location aspects in NTN | OPPO | Rel-17 | Response to S2-2108279. Merged into S2-2109337 | Stefan (Ericsson) comments that there are two overlapping LSs Jean Yves (Thales) proposes 8510 r01 merging 2 LSs out (8510 and 8697) ==== Revisions Deadline ==== Jingran (OPPO) is ok to merge. ==== Comments Deadline ==== | Merged |
| 8.11 | S2-2108681 | CR | Approval | 23.501 CR3413 (Rel-17, 'C'): Multiple TACs handling for NR satellite access | OPPO | Rel-17 | Merged into S2-2109097 | Stefan (Ericsson) provides comments Jean Yves (Thales) provides comment and proposes to focus on 8360 ==== Revisions Deadline ==== Jingran (OPPO) replies. Stephen (Qualcomm) proposes merger of this CR into S2-2108360 ==== Comments Deadline ==== | Merged |
| 8.11 | S2-2108693 | CR | Approval | 23.502 CR3274 (Rel-17, 'C'): Multiple TACs handling for NR Satellite Access | OPPO | Rel-17 | Noted | Stefan (Ericsson) provides comments. ==== Revisions Deadline ==== Stephen (Qualcomm) believes the CR can be noted ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108359 | DISCUSSION | Approval | Tracking Area handling for moving cells . | Ericsson | Noted | Stephen (Qualcomm) provides comments Hucheng (CATT) comments and gives a proposal. Yuxin (Xiaomi) provides comments Stefan (Ericsson) replies to Yuxin and Stephen Stefan (Ericsson) replies to Hucheng Hannu (Nokia) replies and prefers option B, C or E Jean Yves (Thales) comments and propose to move forward with option C+D (opt) Stephen (Qualcomm) provides more comments Stefan (Ericsson) provides comments Wanqiang (Huawei) provides comments Guillaume (MediaTek Inc.) comments Stephen (Qualcomm) comments again Stefan (Ericsson) provides more comments Wanqiang (Huawei) provides more comments ==== Revisions Deadline ==== Hannu (Nokia) comments in favour of minimum number of procedures. ==== Comments Deadline ==== | Noted | |
| 8.11 | S2-2108360 | CR | Approval | 23.501 CR3364 (Rel-17, 'F'): TA handling for moving cells in satellite access | Ericsson | Rel-17 | r09 agreed. Revised to S2-2109097, merging S2-2108495, S2-2108496 and S2-2108681 | Stephen (Qualcomm) provides comments and an r01 Jingran (OPPO) provides comments. Hucheng (CATT) comments. Stephen (Qualcomm) replies to previous comments Stefan (Ericsson) replies and provides r02 Wanqiang (Huawei) comments. Hannu (Nokia) comments and shares r03. Hucheng (CATT) replies to Stephen (Qualcomm). Stephen (Qualcomm) provides an r04 and more comments Hucheng (CATT) provides r05. Yuxin (Xiaomi) provides r06. Guillaume (MediaTek Inc.) provides r07 Stefan (Ericsson) provides r08 Yuxin (Xiaomi) replies to Stefan (Ericsson) Stefan (Ericsson) replies to Yuxin and provides r09 ==== Revisions Deadline ==== Stephen (Qualcomm) prefers r09 followed by r08, r05, r04, r07, r06 in that order Yuxin (Xiaomi) is fine with r09 Jean Yves (Thales) is fine with r09. Thank you all for this good discussion. Hannu (Nokia) can live with r09 but points out it's still not perfect. ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109097 | CR | Approval | 23.501 CR3364R1 (Rel-17, 'F'): TA handling for moving cells in satellite access | Ericsson | Rel-17 | Revision of S2-2108360r09, merging S2-2108495, S2-2108496 and S2-2108681. Approved | Agreed | |
| 8.11 | S2-2108501 | DISCUSSION | Discussion | Resolution of Support for TACs, SAs, FAs for NR Satellite Access. | Qualcomm Incorporated | Rel-17 | Noted | Noted | |
| 8.11 | S2-2108746 | DISCUSSION | Discussion | Discussion on Supporting Multiple TACs for Satellite Access. | Huawei, HiSilicon | Rel-17 | Revision of (Noted) S2-2107618 from S2#147E. Noted | Noted | |
| 8.11 | S2-2108747 | CR | Approval | 23.501 CR3323R1 (Rel-17, 'C'): Support multiple TACs for satellite access | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107619 from S2#147E. r04 agreed. Revised to S2-2109098. | Stefan (Ericsson) provides comments and suggests to merge this into 8360 and 8499 Wanqiang (Huawei) provides feedback and r01 Stephen (Qualcomm) provides an r02 Wanqiang (Huawei) comments on r02 Stefan (Ericsson) provides r03 Wanqiang (Huawei) provides r04 ==== Revisions Deadline ==== Stephen (Qualcomm) prefers r04 followed by r03 Stefan (Ericsson) ok with r04 Jean Yves (Thales) ok with r04 Hannu (Nokia) supports r04 Relja (TNO) supports r04. ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109098 | CR | Approval | 23.501 CR3323R2 (Rel-17, 'C'): Support multiple TACs for satellite access | Huawei, HiSilicon | Rel-17 | Revision of S2-2108747r04. Approved | Agreed | |
| 8.11 | S2-2108748 | CR | Approval | 23.502 CR3197R1 (Rel-17, 'C'): Support multiple TACs for satellite access | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107620 from S2#147E. Covered by S2-2108499 | Stefan (Ericsson) provides comments Stephen (Qualcomm) comments that the CR seems unneeded Stefan (Ericsson) comments and provides r01, but also ok to note CR Wanqiang (Huawei) is ok with r01. ==== Revisions Deadline ==== Wanqiang (Huawei) propose to agree r01 if there is no other view. Also S2-2108693 Stephen (Qualcomm) proposes merger into S2-2108499 Wanqiang (Huawei) OK to merge. ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108496 | CR | Approval | 23.501 CR3381 (Rel-17, 'B'): Support of TAI indication in a ULI for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Merged into S2-2109097 | Wanqiang (Huawei) comments to merge into S2-2108360 ==== Revisions Deadline ==== Stephen (Qualcomm) agrees to merge into S2-2108360 ==== Comments Deadline ==== | Merged |
| 8.11 | S2-2108499 | CR | Approval | 23.502 CR3251 (Rel-17, 'B'): Support of NG-RAN Location Reporting for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Approved | Agreed | |
| 8.11 | S2-2108494 | CR | Approval | 23.501 CR3379 (Rel-17, 'B'): Indicating a last visited TAI in a Registration for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Approved | Agreed | |
| 8.11 | S2-2108498 | CR | Approval | 23.502 CR3250 (Rel-17, 'B'): Indicating a last visited TAI in a Registration for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Approved | Agreed | |
| 8.11 | S2-2108495 | CR | Approval | 23.501 CR3380 (Rel-17, 'B'): Support of Service Areas and Forbidden Areas for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Merged into S2-2109097 | Wanqiang (Huawei) comments to merge into S2-2108360 Stefan (Ericsson) supports to merge into 8360 ==== Revisions Deadline ==== Stephen (Qualcomm) agrees to merge into S2-2108360 ==== Comments Deadline ==== | Merged |
| 8.11 | S2-2108510 | LS OUT | Approval | [DRAFT] LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Response to S2-2105283 (Replied to at S2#147E). r02 agreed. Revised to S2-2109337, merging S2-2108697 | Stefan (Ericsson) comments that there are two overlapping LSs Jean Yves (Thales) proposes 8510 r01 merging 2 LSs out (8510 and 8697) Stefan (Ericsson) provides r02 ==== Revisions Deadline ==== Jingran (OPPO) is ok with r02 Wanqiang (Huawei) ask to add the S2-2108747 in the attachment on top of rev2 Stephen (Qualcomm) can agree the r02 and with adding S2-2108747 as another attachment Yuxin (Xiaomi) is fine with r02 ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109337 | LS OUT | Approval | LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | SA WG2 | Rel-17 | Revision of S2-2108510r02, merging S2-2108697. Approved | Approved | |
| 8.11 | S2-2108530 | CR | Approval | 23.501 CR3301R1 (Rel-17, 'C'): Support of selecting a single TAI | CATT | Rel-17 | Revision of (Postponed) S2-2107446 from S2#147E. Noted | Hucheng (CATT) provides r01. ==== Revisions Deadline ==== Stephen (Qualcomm) proposes merger of this CR into S2-2108360 Jean Yves (Thales) propose to note the CR ==== Comments Deadline ==== Hucheng (CATT) is OK to either merge this paper into S2-2108360 or note it, slightly prefers the merger. | Noted |
| 8.11 | S2-2108514 | DISCUSSION | Approval | Discussion on Registration Update handling when broadcasting more than one TACs. | Xiaomi | Rel-17 | Noted | Noted | |
| 8.11 | S2-2108515 | CR | Approval | 23.501 CR3383 (Rel-17, 'C'): Mobility Registration Update handling | Xiaomi | Rel-17 | Noted | Stefan (Ericsson) comments and questions the need for the CR Hannu (Nokia) can't see why NR satellite access specific requirement for Mobility Registration Update would be needed? Yuxin (Xiaomi) clarification request to Stefan (Ericsson) comments Yuxin (Xiaomi) answers Hannu (Nokia) questions Stephen (Qualcomm) comments Guillaume (MediaTek) agrees with Stefan (Ericsson) ==== Revisions Deadline ==== Stephen (Qualcomm) proposes to note the CR Yuxin (Xiaomi) agrees to note the CR ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108947 | CR | Approval | 23.501 CR3458 (Rel-17, 'F'): AMF selection for Intra NG-RAN node N2 based handover | Xiaomi | Rel-17 | Noted | DongYeon (Samsung) provides r01. Hannu (Nokia) provides r02 simplifying the CR even further. Wanqiang (Huawei) comments. Stefan (Ericsson) comments Sherry (Xiaomi) provides r03. Sherry (Xiaomi) provides r04. Stefan (Ericsson) asks whether any CR is needed Chris (Vodafone) tends to agree with Ericsson ==== Revisions Deadline ==== Hannu (Nokia) supports the view that CR is not needed and can be noted. ==== Comments Deadline ==== Sherry (Xiaomi) replies to Hannu, Chris and Stefan. | Noted |
| 8.11 | S2-2108325 | CR | Approval | 23.501 CR3284R2 (Rel-17, 'F'): Editorial correction in TS 23.501 | Xiaomi, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107836 from S2#147E. r02 agreed. Revised to S2-2109099. | DongYeon (Samsung) provides r01. Yuxin (Xiaomi) comments to r01. Hucheng (CATT) comments. Hannu (Nokia) supports Yuxin and prefers the previous version of the CR before r01. Yuxin (Xiaomi) replies and prefers to use r00. Stephen (Qualcomm) also prefers the r00 Stefan (Ericsson) also prefers r00 Yuxin (Xiaomi) agrees with Stephen (Qualcomm) and provides r02 ==== Revisions Deadline ==== Stephen (Qualcomm) prefers the r02 but the r00 is also acceptable Jean Yves (Thales) prefers the r02 also Hannu (Nokia) also supports r02 as the way forward. Can also live with the original version. ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109099 | CR | Approval | 23.501 CR3284R3 (Rel-17, 'F'): Editorial correction in TS 23.501 | Xiaomi, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108325r02. Approved | Agreed | |
| 8.11 | S2-2108326 | CR | Approval | 23.502 CR3161R2 (Rel-17, 'F'): Editorial correction in TS 23.502 | Xiaomi, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107837 from S2#147E. Approved | Agreed | |
| 8.11 | S2-2108327 | CR | Approval | 23.503 CR0659R2 (Rel-17, 'F'): Editorial correction in TS 23.503 | Xiaomi, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107838 from S2#147E. r01 agreed. Revised to S2-2109100. | Stephen (Qualcomm) comments Yuxin (Xiaomi) agrees with Stephen (Qualcomm) comments and provides r01 ==== Revisions Deadline ==== Stephen (Qualcomm) agrees the r01 Hannu (Nokia) supports r01 and thanks Stephen for the comment and Yuxin for providing the revision. ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109100 | CR | Approval | 23.503 CR0659R3 (Rel-17, 'F'): Editorial correction in TS 23.503 | Xiaomi, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108327r01. Approved | Agreed | |
| 8.11 | S2-2108698 | CR | Approval | 23.501 CR3415 (Rel-17, 'C'): Mobility Registration Update trigger clarification | Xiaomi | Rel-17 | r01 agreed. Revised to S2-2109101. | Stefan (Ericsson) provides r01 Hannu (Nokia) prefers r01 Yuxin (Xiaomi) agrees with r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109101 | CR | Approval | 23.501 CR3415R1 (Rel-17, 'C'): Mobility Registration Update trigger clarification | Xiaomi | Rel-17 | Revision of S2-2108698r01. Approved | Agreed | |
| 8.11 | S2-2108329 | CR | Approval | 23.501 CR3030R3 (Rel-17, 'F'): UE location verification handling | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Agreed) S2-2107835 from S2#147E. r02 agreed. Revised to S2-2109338. | DongYeon (Samsung) asks for clarification. Hannu (Nokia) answers to DongYeon and provides r01 to update the cover page. DongYeon (Samsung) comments.. Stephen (Qualcomm) provides comments and an r02 Guillaume (MediaTek Inc.) comments. Stephen (Qualcomm) provides comments on the SA1 LS DongYeon (Samsung) proposes to NOTE this CR. Jean Yves (Thales) provides comments on the SA1 LS and supports r02 DongYeon (Samsung) provides r03. ==== Revisions Deadline ==== Stephen (Qualcomm) prefers r03 followed by r02 Jean Yves (Thales) ok with r02 and r03 DongYeon (Samsung) prefers r03. Hannu (Nokia) can only agree r02. r03 breaks the TS 23.501 and 23.502 CRs that move UE location verification to clause 5.4.11.4 meaning that also the previous versions of this 23.501 CR in S2-2107835 and S2-2107231 agreed in SA2 #147E shall be rejected in order to reverse the whole removal of duplication of text between TS 23.501 and TS 23.502. DongYeon (Samsung) prefers r03, but not object to r02. Hannu (Nokia) requests that this CR is marked up for CC. SA2 needs to decide which versions (if any) of S2-2108329, S2-2107835 and S2-2107231 to send for plenary approval. ==== Comments Deadline ==== Hannu (Nokia) withdraws his request to bring this CR to CC if r02 can be agreed. | Revised |
| 8.11 | S2-2109338 | CR | Approval | 23.501 CR3030R4 (Rel-17, 'F'): UE location verification handling | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108329r02. CC#2: Approved | Agreed | |
| 8.11 | S2-2108481 | CR | Approval | 23.501 CR3376 (Rel-17, 'F'): Clarification on IAB support for NR satellite access | Rakuten Mobile, Inc | Rel-17 | Approved | Agreed | |
| 8.11 | S2-2108482 | CR | Approval | 23.401 CR3671 (Rel-17, 'F'): Clarification on IAB support for NR satellite access | Rakuten Mobile, Inc | Rel-17 | Noted | Stefan (Ericsson) provides comments and questions the need for the CR Hannu (Nokia) shares the concern of Stefan that this CR is not appropriate under the present work item scope. Aoken (Rakuten Mobile) provide the comment. Stephen (Qualcomm) comments ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.11 | S2-2108513 | CR | Approval | 23.501 CR3318R1 (Rel-17, 'F'): Limited service PLMN selection for emergency | Nokia, Nokia Shanghai Bell, Xiaomi | Rel-17 | Revision of (Agreed) S2-2107568 from S2#147E. r01 agreed. Revised to S2-2109102. | Stephen (Qualcomm) provides comments and an r01 ==== Revisions Deadline ==== Jean Yves (Thales) agrees with r01 Yuxin (Xiaomi) agrees with r01 Hannu (Nokia) agrees r01 ==== Comments Deadline ==== | Revised |
| 8.11 | S2-2109102 | CR | Approval | 23.501 CR3318R2 (Rel-17, 'F'): Limited service PLMN selection for emergency | Nokia, Nokia Shanghai Bell, Xiaomi | Rel-17 | Revision of S2-2108513r01. Approved | Agreed | |
| 8.11 | S2-2109000 | LS In | Action | LS from RAN WG2: Reply LS on UE location aspects in NTN | RAN WG2 (R2-2111547) | Rel-17 | CC#2: Postponed | Postponed | |
| 8.11 | S2-2109001 | LS In | Information | LS from RAN WG2: Reply LS on extended NAS supervision timers at satellite access | RAN WG2 (R2-2111612) | Rel-17 | Noted | Noted | |
| 8.11 | S2-2109005 | LS In | Action | LS from RAN WG3: Reply LS on UE Location Aspects in NTN | RAN WG3 (R3-216067) | Rel-17 | CC#2: Postponed | Postponed | |
| 8.11 | S2-2109018 | LS In | Action | Reply LS on UE location aspects in NTN | SA WG3 (S3-214394) | Rel-17 | CC#2: Postponed | Postponed | |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=4 | - | |
| 8.12 | S2-2108300 | CR | Approval | 23.287 CR0165R2 (Rel-17, 'B'): NR Tx Profile | LG Electronics, Deutsche Telekom, ZTE, Tencent, vivo, Intel, CATT, Lenovo, Motorola Mobility, OPPO | Rel-17 | Revision of (Agreed) S2-2107841 from S2#147E. r01 agreed. Revised to S2-2109103. | Zhang (Ericsson) provides r01 LaeYoung (LGE) is fine with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.12 | S2-2109103 | CR | Approval | 23.287 CR0165R3 (Rel-17, 'B'): NR Tx Profile | LG Electronics, Deutsche Telekom, ZTE, Tencent, vivo, Intel, CATT, Lenovo, Motorola Mobility, OPPO, Ericsson | Rel-17 | Revision of S2-2108300r01. Approved | Agreed | |
| 8.12 | S2-2108301 | CR | Approval | 23.287 CR0169 (Rel-17, 'F'): Resolution of ENs related to PC5 DRX | LG Electronics, Deutsche Telekom, ZTE, Tencent | Rel-17 | Approved | Agreed | |
| 8.12 | S2-2109372 | LS In | Action | Reply LS on Tx Profile | RAN WG2 (R2-2111432) | Rel-17 | Postponed | Postponed | |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=21 | - | |
| 8.14 | S2-2108253 | LS In | Information | LS from RAN WG1: LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN WG1 (R1-2106326) | Rel-17 | Revision of S2-2106995 from S2#147E. Response drafted in S2-2108756. Final response in S2-2109105 | Runze (Huawei) proposes to NOTE the LS. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Replied to |
| 8.14 | S2-2108756 | LS OUT | Approval | [DRAFT] Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | CATT | Rel-17 | Response to S2-2108253. r02 agreed. Revised to S2-2109105. | Stephen (Qualcomm) provides comments and an r01 Sherry (Xiaomi) comments. Yunjing (CATT) replies to Sherry. Runze (Huawei) replies and suggest to merge into S2-2109017.. Yunjing (CATT) thinks the two draft LSs are replied to different LSs came from different RAN WGs and prefers to keep the two LSs separate. Runze (Huawei) replies. Cai Simon (Nokia) supports Yunjing (CATT) with two separate LS replies Sherry (Xiaomi) agrees with Runze to have merged LS reply. Yunjing (CATT) prefers separate LS replies to different LSs from different RAN WGs and provides r02. ==== Revisions Deadline ==== Runze (Huawei) is fine to send this LS and suggest to align the response in 2017. Stephen (Qualcomm) can agree r02 or r01 but not r00 Sherry (Xiaomi) still thinks 9017 already included enough information for RAN1 and RAN2 to understand SA2 position on this issue, but if she is the only one having concern, she can live with r02. Guillaume (MediaTek Inc.) supports r01/r02 only. ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109105 | LS OUT | Approval | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | SA WG2 | Rel-17 | Revision of S2-2108756r02. Approved | Approved | |
| 8.14 | S2-2108270 | LS In | Action | LS from RAN WG2: Reply LS on determination of location estimates in local co-ordinates | RAN WG2 (R2-2108957) | Rel-17 | Revision of S2-2107040 from S2#147E. Responses drafted in S2-2108358 and S2-2108505. Postponed | Postponed | |
| 8.14 | S2-2108358 | LS OUT | Approval | [DRAFT] Response LS on determination of location estimates in local co-ordinates | Ericsson | Rel-17 | Response to S2-2108270. Noted | Yunjing (CATT) provides r01 to merge S2-2108505 into this draft LS. Runze (Huawei) objects r01 and provides r02. Åke (Ericsson)finds r01 acceptable Stephen (Qualcomm) provides an r03 ==== Revisions Deadline ==== Runze (Huawei) objects R03 and propose to agree r02. Stephen (Qualcomm) can agree r03 but not any other version ==== Comments Deadline ==== | Noted |
| 8.14 | S2-2108505 | LS OUT | Approval | [DRAFT] LS Response to Reply LS on determination of location estimates in local co-ordinates | Qualcomm Incorporated | Rel-17 | Response to S2-2108270. Noted | Runze (Huawei) comments and suggests this paper merge into S2-2108358.. Yunjing (CATT) suggests this paper merge into S2-2108358. ==== Revisions Deadline ==== Stephen (Qualcomm) agrees to a merger into S2-2108358 ==== Comments Deadline ==== | Noted |
| 8.14 | S2-2108491 | CR | Approval | 23.273 CR0205 (Rel-17, 'F'): Addition of Exception Procedures | Qualcomm Incorporated | Rel-17 | Postponed | Åke (Ericsson) Provides comments Yunjing (CATT) Provides comments Stephen (Qualcomm) replies to comments and provides an r01 Runze (Huawei) provides comments. Cai Simon (Nokia) provides further comments Yunjing (CATT) provides comments. Stephen (Qualcomm) provides an r02 and replies to previous comments Yunjing (CATT) replies. ==== Revisions Deadline ==== Yunjing (CATT) supports Cai Simon (Nokia), especially when SLT is introduced. Stephen (Qualcomm) agrees to postpone the CR ==== Comments Deadline ==== | Postponed |
| 8.14 | S2-2108493 | CR | Approval | 23.273 CR0151R5 (Rel-17, 'B'): Addition of a Scheduled Location Time | Qualcomm Incorporated | Rel-17 | Revision of (Postponed) S2-2107787 from S2#147E. r03 agreed. Revised to S2-2109106, merging S2-2108841 | Leo (Deutsche Telekom) provides r01. Runze (Huawei) objects to r00 and r01, and provides r02. Stephen (Qualcomm) provides an r03 Runze (Huawei) can live with r03 ==== Revisions Deadline ==== Åke (Ericsson) accept r02 and r03 ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109106 | CR | Approval | 23.273 CR0151R6 (Rel-17, 'B'): Addition of a Scheduled Location Time | Qualcomm Incorporated | Rel-17 | Revision of S2-2108493r03, merging S2-2108841. Approved | Agreed | |
| 8.14 | S2-2108841 | CR | Approval | 23.273 CR0199R1 (Rel-17, 'B'): Addition of a Scheduled Location Time | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107681 from S2#147E. Merged into S2-2109106 | Stephen (Qualcomm) provides comments Åke (Ericsson) Support comment from Qualcomm. ==== Revisions Deadline ==== Runze (Huawei) proposes to merge the CR into S2-2108493 ==== Comments Deadline ==== | Merged |
| 8.14 | S2-2108750 | CR | Approval | 23.273 CR0206 (Rel-17, 'F'): Editorial changes for eLCS_Ph2 | CATT | Rel-17 | r03 agreed. Revised to S2-2109107. | Åke (Ericsson) provides r01 and a question Yunjing(CATT) replies to Åke (Ericsson). Leo (Deutsche Telekom) provides comments on r01. Yunjing (CATT) replies to Leo (Deutsche Telekom) and provides r02. Leo (Deutsche Telekom) is fine with r02, thanks. Yunjing (CATT) provides r03. Åke (Ericsson) is fine with r03 Leo (Deutsche Telekom) is fine with r03 ==== Revisions Deadline ==== Runze (Huawei) supports r03 ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109107 | CR | Approval | 23.273 CR0206R1 (Rel-17, 'F'): Editorial changes for eLCS_Ph2 | CATT, Ericsson | Rel-17 | Revision of S2-2108750r03. Approved | Agreed | |
| 8.14 | S2-2108753 | CR | Approval | 23.273 CR0209 (Rel-17, 'F'): Location Services applicable to SNPN(s) | CATT, Ericsson | Rel-17 | r05 agreed. Revised to S2-2109108. | Josep (DT) requests clarification(s). Not clear whether SNPN support clarification is needed. Yunjing (CATT) replies to Josep (DT). Josep (DT) comments, provides r01. Yunjing (CATT) provides r02. Josep (DT) comments that there are no requirements for integrating further functionality in the CH. Objects to r02. Yunjing (CATT) replies to Josep (DT) and provides r03. Josep (DT) provides r04. Antoine (Orange) provides r05. Walter Dees (Philips) provides r06 Yunjing (CATT) replies to Walter Dees (Philips) Åke (Ericsson) Comments reply from Yunjing (CATT) Walter Dees (Philips) responds to Yunjing (CATT) ==== Revisions Deadline ==== Josep (DT) objects to all revisions except r05 Yunjing (CATT) agrees with Åke (Ericsson). Yunjing (CATT) replies to Walter Dees (Philips). Yunjing (CATT) can accept r05. ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109108 | CR | Approval | 23.273 CR0209R1 (Rel-17, 'F'): Location Services applicable to SNPN(s) | CATT, Ericsson | Rel-17 | Revision of S2-2108753r05. Approved | Agreed | |
| 8.14 | S2-2108842 | CR | Approval | 23.273 CR0218 (Rel-17, 'F'): Update AMF functionality for satellite access UE | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109109. | Sherry (Xiaomi) provides r01. Runze (Huawei) comments on r01, and prefers original CR. Sherry (Xiaomi) prefers r01. Runze (Huawei) can live with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109109 | CR | Approval | 23.273 CR0218R1 (Rel-17, 'F'): Update AMF functionality for satellite access UE | Huawei, HiSilicon | Rel-17 | Revision of S2-2108842r01. Approved | Agreed | |
| 8.14 | S2-2108999 | LS In | Action | LS from RAN WG2: Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN WG2 (R2-2111488) | Rel-17 | Response drafted in S2-2109017. Final response in S2-2109104 | Replied to | |
| 8.14 | S2-2109017 | LS OUT | Approval | [DRAFT] Reply LS on Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Huawei | Rel-17 | Created at CC#1. Response to S2-2108999. r03 agreed. Revised to S2-2109104. | Stephen (Qualcomm) provides comments and an r01 Runze (Huawei) provides r02. Leo (Deutsche Telekom) provides r03. Runze (Huawei) agrees r03. Stephen (Qualcomm) can also agree the r03 ==== Revisions Deadline ==== Stephen (Qualcomm) notes that r00 is not acceptable (in case there is an objection to other rev.s) ==== Comments Deadline ==== | Revised |
| 8.14 | S2-2109104 | LS OUT | Approval | Reply LS on Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | SA WG2 | Rel-17 | Revision of S2-2109017r03. Approved | Approved | |
| 8.14 | S2-2109003 | LS In | Information | LS from RAN WG3: Reply LS to RAN2 on the misalignment in SRS configuration | RAN WG3 (R3-216009) | Rel-16 | Noted | Yunjing (CATT) proposes to note the LS. ==== Revisions Deadline ==== Runze (Huawei) proposes to note the LS. ==== Comments Deadline ==== | Noted |
| 8.14 | S2-2109011 | LS In | Action | LS from RAN WG3: Reply LS on location estimates in local co-ordinates | RAN WG3 (R3-216235) | Rel-17 | Noted | Yunjing (CATT) proposes to note the LS. ==== Revisions Deadline ==== Runze (Huawei) proposes to note the LS. ==== Comments Deadline ==== | Noted |
| 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:=4 | - | |
| 8.17 | S2-2108930 | CR | Approval | 23.501 CR3455 (Rel-17, 'F'): Support of GERAN/UTRAN access: Annex L alignment to CR 2970r1 to TS 23.501 | Vodafone | Rel-17 | r01 agreed. Revised to S2-2109312. | Haris(Qualcomm) asks question for clarification Chris (Vodafone) provides r1. Haris(Qualcomm) comments that r01 is ok ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.17 | S2-2109312 | CR | Approval | 23.501 CR3455R1 (Rel-17, 'F'): Support of GERAN/UTRAN access: Annex L alignment to CR 2970r1 to TS 23.501 | Vodafone | Rel-17 | Revision of S2-2108930r01. Approved | Agreed | |
| 8.17 | S2-2108932 | CR | Approval | 23.502 CR3312 (Rel-17, 'F'): Support of GERAN/UTRAN access: Annex G alignment to CR 2970r1 to TS 23.501 | Vodafone | Rel-17 | r01 agreed. Revised to S2-2109313. | Haris(Qualcomm) asks question for clarification Chris (Vodafone) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.17 | S2-2109313 | CR | Approval | 23.502 CR3312R1 (Rel-17, 'F'): Support of GERAN/UTRAN access: Annex G alignment to CR 2970r1 to TS 23.501 | Vodafone | Rel-17 | Revision of S2-2108932r01. Approved | Agreed | |
| 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-2108266 | LS In | Action | LS from CT WG3: LS on DCAMP related issues | CT WG3 (C3-214425) | Rel-17 | Revision of S2-2107029 from S2#147E. Responses drafted in S2-2108343 and S2-2108585. Final response in S2-2109193 | Belen (Ericsson) proposes to merge LS into S2-2108343 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Replied to |
| 8.21 | S2-2108343 | LS OUT | Approval | [DRAFT] LS reply on DCAMP related issues | Ericsson | Rel-17 | Response to S2-2108266. r01 agreed. Revised to S2-2109193, merging S2-2108585 | Pallab (Nokia) proposes to have the LSout discussion in this thread. Belen (Ericsson) is okay to use this thread and ask Huawei and Nokia. Belen (Ericsson) provides r01. Susan (Huawei) is ok with r01. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.21 | S2-2109193 | LS OUT | Approval | LS reply on DCAMP related issues | SA WG2 | Rel-17 | Revision of S2-2108343r01, merging S2-2108585. Approved | Approved | |
| 8.21 | S2-2108585 | LS OUT | Approval | [DRAFT] Reply LS on DCAMP related issues | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107480 from S2#147E. Response to S2-2108266. Merged into S2-2109193 | Pallab (Nokia) suggests to move the LSOut discussion to a single email thread in S2-2108343. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.21 | S2-2108338 | CR | Approval | 23.501 CR3362 (Rel-17, 'F'): Align BSF NF profile in NRF (23.501) with BSF related information in NRF services (23.502) | Oracle | Rel-17 | Approved | Agreed | |
| 8.21 | S2-2108586 | CR | Approval | 23.502 CR3189R1 (Rel-17, 'F'): Correction to AF-triggered dynamically changing AM policies | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2107481 from S2#147E. r04 agreed. Revised to S2-2109194. | Pallab (Nokia) comments and thinks that the proposed changes are not needed. Susan (Huawei) replies to Pallab (Nokia). Pallab (Nokia) responds to Susan (Huawei). Belen (Ericsson) is okay with the CR. Pallab (Nokia) responds to Belen (Ericsson) Belen (Ericsson) asks for clarification. Belen (Ericsson) replies. Pallab (Nokia) comments. Belen (Ericsson) replies to Nokia Pallab (Nokia) responds to Belen (Ericsson). Belen (Ericsson) replies to Nokia. Pallab (Nokia) replies to Susan (Huawei). Belen (Ericsson) is okay with r03. Susan (Huawei) provides r04 with the only change on the cover sheet to add Oracle as supporting company. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.21 | S2-2109194 | CR | Approval | 23.502 CR3189R2 (Rel-17, 'F'): Correction to AF-triggered dynamically changing AM policies | Huawei, HiSilicon, Oracle | Rel-17 | Revision of S2-2108586r04. Approved | Agreed | |
| 8.21 | S2-2108587 | CR | Approval | 23.503 CR0662R2 (Rel-17, 'F'): Correction to AF-triggered dynamically changing AM policies | Huawei, HiSilicon | Rel-17 | Revision of (Revised and Agreed) S2-2107482 from S2#147E. Noted | Pallab (Nokia) has same comments as in 8586 and thinks that the proposed changes are not needed. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 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:=4 | - | |
| 8.24 | S2-2108731 | CR | Approval | 23.501 CR3422 (Rel-17, 'F'): Clarification on support of slicing in TWIF scenario | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2109314. | Stefan (Ericsson) provides r01 Marco (Huawei) ok with r01 Myungjune (LGE) comments Myungjune (LGE) provides r02 Marco (Huawei) answers to Myungjune (LGE) and disagrees with r02 Myungjune (LGE) replies to Marco (Huawei) Marco (Huawei) replies to Myungjune (LGE) Stefan (Ericsson) comments ==== Revisions Deadline ==== Myungjune (LGE) prefer r02 Marco (Huawei) comment and R02 is ok ==== Comments Deadline ==== | Revised |
| 8.24 | S2-2109314 | CR | Approval | 23.501 CR3422R1 (Rel-17, 'F'): Clarification on support of slicing in TWIF scenario | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2108731r02. Approved | Agreed | |
| 8.24 | S2-2108854 | CR | Approval | 23.501 CR3440 (Rel-17, 'F'): Removal of a now obsolete sentence about non-3GPP Access being forbidden in a PLMN | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2109315. | Stefan (Ericsson) provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.24 | S2-2109315 | CR | Approval | 23.501 CR3440R1 (Rel-17, 'F'): Removal of a now obsolete sentence about non-3GPP Access being forbidden in a PLMN | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108854r01. Approved | Agreed | |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=20 | - | |
| 8.25 | S2-2108283 | LS In | Information | LS from CT WG1: LS on system information extensions for minimization of service interruption (MINT) | CT WG1 (C1-216297) | Rel-17 | Response drafted in S2-2108637. Noted | Hyunsook (LGE) proposes to note this LS for information. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.25 | S2-2108637 | LS OUT | Approval | [DRAFT] LS OUT on system information extensions for minimization of service interruption (MINT) | Huawei, HiSilicon | Rel-17 | Response to S2-2108283. Noted | Hyunsook (LGE) proposes to note it. Qian (Ericsson) supports to note this. Haiyang (Huawei) responds. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.25 | S2-2108371 | CR | Approval | 23.501 CR3264R2 (Rel-17, 'F'): MINT Updates | Ericsson | Rel-17 | Revision of (Agreed) S2-2107848 from S2#147E. r01 agreed. Revised to S2-2109316. | Hyunsook (LGE) has a comment and proposes to note it in this meeting. Haiyang (Huawei) agrees with Hyunsook (LGE) to note this paper in this meeting. Qian (Ericsson) comments. Haris(Qualcomm) provides r01 Hyunsook (LGE) provides r02. ==== Revisions Deadline ==== Hyunsook (LGE) can accept r01 (with CT1 CR dependency) and r02. Qian (Ericsson) propose to go with r01. Lalith(Samsung) OK with r01 or r02. Haris(Qualcomm) propose to go with r01 Haiyang (Huawei) is OK with r02 or postpone, but not ok with r00/r01. Qian (Ericsson) provides r03 in DRAFT folder on top of r01 with these changes: 1) 'after' -> 'during and after'. 2) delete 'in the roamed country' 3) Delete 'SOR' in cover sheet. 4) adding 'This CR is to synch with the agreement in C1-216752'. Qian also asks this to be handled in CC#2 with the above changes. ==== Comments Deadline ==== Haiyang (Huawei) is OK with [r01+the updated part provided by Qian(Ericsson)]. | Revised |
| 8.25 | S2-2109316 | CR | Approval | 23.501 CR3264R3 (Rel-17, 'F'): MINT Updates | Ericsson, LG Electronics | Rel-17 | Revision of S2-2108371r01. Approved | Agreed | |
| 8.25 | S2-2108372 | CR | Approval | 23.502 CR3146R1 (Rel-17, 'C'): Registration procedure improvement for MINT | Ericsson | Rel-17 | Revision of (Postponed) S2-2107253 from S2#147E. r01 agreed. Revised to S2-2109317. | Hyunsook (LGE) proposes to note it in this meeting. Haiyang (Huawei) agrees with Hyunsook (LGE) to note this paper. Qian (Ericsson) comments. Qian (Ericsson) provides r01. ==== Revisions Deadline ==== Hyunsook (LGE) can accept r01 only in case if S2-2108371r01 is agreed, otherwise, propose to postpone it. Qian (Ericsson) propose to go with r01. Haiyang (Huawei) is OK with r01. ==== Comments Deadline ==== | Revised |
| 8.25 | S2-2109317 | CR | Approval | 23.502 CR3146R2 (Rel-17, 'C'): Registration procedure improvement for MINT | Ericsson, LG Electronics | Rel-17 | Revision of S2-2108372r01. Approved | Agreed | |
| 8.25 | S2-2108373 | CR | Approval | 23.502 CR3228 (Rel-17, 'C'): UE configuration procedure update and SoR update for MINT | Ericsson | Rel-17 | r03 agreed. Revised to S2-2109318. | Hyunsook (LGE) proposes to note it in this meeting. Haiyang (Huawei) agrees with Hyunsook (LGE) to note this paper. Qian (Ericsson) comments. Lalith(Samsung) comments. Qian (Ericsson) provides r01. Lalith(Samsung) provides r02 Hyunsook (LGE) doesn't want to make a progress on this CR. Haris(Qualcomm) comments on r01 and r02 and provides r03 ==== Revisions Deadline ==== Hyunsook (LGE) can accept r03 only in case if S2-2108371r01 is agreed, otherwise, propose to postpone it. Qian (Ericsson) propose to go with r03. Lalith (Samsung) also propose to agree r03. Haris(Qualcomm) propose to agree r03 Haiyang (Huawei) is OK with r03 but request the author to delete the SoR related description in the cover page if it is finally agreed. ==== Comments Deadline ==== | Revised |
| 8.25 | S2-2109318 | CR | Approval | 23.502 CR3228R1 (Rel-17, 'C'): UE configuration procedure update for MINT | Ericsson, LG Electronics | Rel-17 | Revision of S2-2108373r03. Approved | Agreed | |
| 8.25 | S2-2108440 | CR | Approval | 23.502 CR3133R1 (Rel-17, 'B'): Authentication and Subscription information checking for Disaster Roaming service | LG Electronics, KT Corp., LG Uplus, SK Telecom, Ericsson, vivo | Rel-17 | Revision of (Postponed) S2-2107160 from S2#147E. Postponed | Haiyang (Huawei) suggests to postpone this paper. Alessio(Nokia) is also OK to postpone this paper. ==== Revisions Deadline ==== Hyunsook (LGE) is O.K. to postpone it in this meeting. ==== Comments Deadline ==== | Postponed |
| 8.25 | S2-2108441 | CR | Approval | 23.502 CR3236 (Rel-17, 'F'): Session management related subscription information during Disaster Roaming | LG Electronics | Rel-17 | Postponed | Haiyang (Huawei) suggests to postpone/note this paper. ==== Revisions Deadline ==== Hyunsook (LGE) is O.K. to postpone it in this meeting. ==== Comments Deadline ==== | Postponed |
| 8.25 | S2-2108555 | CR | Approval | 23.501 CR3388 (Rel-17, 'F'): Clarification on the pre-conditions for DC roaming | Vivo | Rel-17 | Noted | Hyunsook (LGE) proposes to note it Wen (vivo) replies to Hyunsook (LGE) Qian (Ericsson) comments Wen (vivo) replies and provides r01 Hyunsook (LGE) provides r02. Wen (vivo) replies. Lalith(Samsung) objects r00, r02 Haris(Qualcomm) proposes to note the CR (r00 or r01) alessio(nokia) also agrees it is wise to note the CR. ==== Revisions Deadline ==== Hyunsook (LGE) can accept only r02, and also o.k. to note this CR. Qian (Ericsson) is ok with r02 or NOTE. Wen (vivo) is ok with r02 as well. ==== Comments Deadline ==== | Noted |
| 8.25 | S2-2108556 | CR | Approval | 23.501 CR3389 (Rel-17, 'F'): Handling of DC is no longer applicable | Vivo | Rel-17 | r02 agreed. Revised to S2-2109319. | Lalith(Samsung) comments. Wen(vivo) replies to Lalith(Samsung). Lalith(Samsung) replies to Wen(Vivo) Wen(vivo) replies and provides r01 Hyunsook (LGE) provides a comment on r01 Wen (vivo) replies and provides r02 ==== Revisions Deadline ==== Hyunsook (LGE) can accept only r02. Qian (Ericsson) is ok with r02. ==== Comments Deadline ==== | Revised |
| 8.25 | S2-2109319 | CR | Approval | 23.501 CR3389R1 (Rel-17, 'F'): Handling of DC is no longer applicable | Vivo | Rel-17 | Revision of S2-2108556r02. Approved | Agreed | |
| 8.25 | S2-2108557 | CR | Approval | 23.501 CR3390 (Rel-17, 'F'): Handling of preventing signalling overload | Vivo | Rel-17 | Noted | Hyunsook (LGE) proposes to note it Wen (vivo) replies to Hyunsook (LGE) Qian (Ericsson) comments Wen (vivo) replies to Qian (Ericsson) Hyunsook (LGE) still has a concern. Wen (vivo) replies to Hyunsook (LGE) and provides r01. Haris(Qualcomm) objects to the CR alessio(Nokia) also objects to the CR Wen (vivo) replies and provides r02 Hyunsook (LGE) provides a comment on r02 Hyunsook (LGE) replies. ==== Revisions Deadline ==== Hyunsook (LGE) objects r00 and all revisions. Wen (vivo) is ok to be NOTED but still keep this concern which the PLMN providing DC service still broadcasts of providing DC service even if it is under congestion control, then make the DC UEs have high priority to access to this PLMN then be rejected by the network . Qian (Ericsson) supports to NOTE the paper. ==== Comments Deadline ==== | Noted |
| 8.25 | S2-2108638 | CR | Approval | 23.501 CR3407 (Rel-17, 'F'): Alignment on system information extensions for minimization of service interruption | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2109320. | Hyunsook (LGE) cheeked it has a conflict with S2-2107848 which was approved at SA2#147E. Haiyang (Huawei) provides r01. Qian (Ericsson) provides comments. Hyunsook (LGE) provides a comment. Haiyang (Huawei) provides some information to Qian (Ericsson). Lalith(Samsung) comments. Haiyang (Huawei) replies to Lalith(Samsung) that r01 does not change the parameter themselves. Lalith(Samsung) objects r00 and is OK with r01 ==== Revisions Deadline ==== Hyunsook (LGE) can accept r01, if agreed. Qian (Ericsson) is ok with r01. ==== Comments Deadline ==== | Revised |
| 8.25 | S2-2109320 | CR | Approval | 23.501 CR3407R1 (Rel-17, 'F'): Alignment on system information extensions for minimization of service interruption | Huawei, HiSilicon | Rel-17 | Revision of S2-2108638r01. Approved | Agreed | |
| 8.25 | S2-2108639 | CR | Approval | 23.501 CR3408 (Rel-17, 'F'): Emergency Services for Disaster Inbound Roamers | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2109321. | Hyunsook (LGE) provides r01. Haiyang (Huawei) replies. Qian (Ericsson) comments. Haiyang (Huawei) replies and prefers r00. Hyunsook (LGE) provides a comment. Lalith (Samsung) comments. Haris(Qualcomm) proposes to note the CR (all revisions) Haiyang (Huawei) disagrees with Haris(Qualcomm) 's view Haris(Qualcomm) comments Lalith(Samsung) supports NOTE from Haris(Qualcomm) Hyunsook (LGE) can agree to add new NOTE suggested by Haris. Haiyang (Huawei) can live with the new note. Qian (Ericsson) is also ok with the proposal adding a note. Haiyang (Huawei) provides r02. Hyunsook (LGE) provides r03 with cover page update and applying NOTE style. ==== Revisions Deadline ==== Hyunsook (LGE) can accept r03. Qian (Ericsson) is ok with r03. Haiyang (Huawei) is ok with r03. ==== Comments Deadline ==== | Revised |
| 8.25 | S2-2109321 | CR | Approval | 23.501 CR3408R1 (Rel-17, 'F'): Emergency Services for Disaster Inbound Roamers | Huawei, HiSilicon | Rel-17 | Revision of S2-2108639r03. Approved | Agreed | |
| 8.25 | S2-2108640 | CR | Approval | 23.501 CR3409 (Rel-17, 'F'): Implicit Deregistration in the PLMN with Disaster Condition | Huawei, HiSilicon | Rel-17 | Noted | Hyunsook (LGE) proposes to note it. Haiyang (Huawei) clarifies. Qian (Ericsson) comments and supports LGE's view. Lalith(Samsung) shares view of Qian (Ericsson) and Hyunsook (LGE) and proposes to note. Alessio(Nokia) also supports noting this CR. Haris(Qualcomm) also proposes to note the CR Haiyang (Huawei) is OK to note this CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.25 | S2-2109019 | LS In | Action | Reply LS on LS on MINT functionality for Disaster Roaming | SA WG3 (S3-214342) | Rel-17 | Postponed | Postponed | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=5 | - | |
| 8.26 | S2-2108648 | CR | Approval | 23.501 CR3316R1 (Rel-17, 'B'): EDRX enhancement for 10.24s cycle for RedCap | China Mobile | Rel-17 | Revision of (Postponed) S2-2107554 from S2#147E. r04 agreed. Revised to S2-2109322, merging S2-2108940 | Hannu (Nokia) provides r01 to merge the whole contents of S2-2108940 into this CR. Qian (Ericsson) comments and provides r02. Miguel (Qualcomm) ok with r02. Aihua (China Mobile) provides r03. Qian (Ericsson) comments on r03 and consider r02 is more correct. Wanqiang (Huawei) comments and provides r04. ==== Revisions Deadline ==== ==== Comments Deadline ==== Tricci (OPPO) supports r02 provided by Qian (Ericsson). | Revised |
| 8.26 | S2-2109322 | CR | Approval | 23.501 CR3316R2 (Rel-17, 'B'): EDRX enhancement for 10.24s cycle for RedCap | China Mobile, Qualcomm Inc | Rel-17 | Revision of S2-2108648r04, merging S2-2108940. Approved | Agreed | |
| 8.26 | S2-2108741 | CR | Approval | 23.501 CR3324R2 (Rel-17, 'B'): Capabilities for NR RedCap UE | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107855 from S2#147E. Approved | Qian (Ericsson) asks a question Steve (Huawei) replies Hannu (Nokia) supports approval of this revision for the sake of clarity (to send this clean version for plenary approval). Miguel (Qualcomm) agrees this revision is needed for clean CR implementation of what was agreed last meeting, i.e. clause 5.6.1 is untouched. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Agreed |
| 8.26 | S2-2108912 | CR | Approval | 23.501 CR3454 (Rel-17, 'F'): RAT type determination on AMF for NR Redcap | China Mobile | Rel-17 | Approved | Agreed | |
| 8.26 | S2-2108940 | CR | Approval | 23.501 CR3457 (Rel-17, 'F'): Handling of PTW for eDRX = 10.24s | Qualcomm Incorporated | Rel-17 | Merged into S2-2109322 | Qian (Ericsson) propose to merge this into 8648 Hannu (Nokia) supports Qian's proposal to merge this into 8648 as there is one overlapping change. Miguel (Qualcomm) ok to merge into 8648 to continue discussion in one thread and one CR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=18 | - | |
| 8.27 | S2-2108261 | LS In | Action | LS on EPS support for IoT NTN in Rel-17 | TSG RAN (RP-212617) | Rel-17 | Revision of S2-2107017 from S2#147E. Response drafted in S2-2108823. Final response in S2-2109344 | Replied to | |
| 8.27 | S2-2108823 | LS OUT | Approval | [DRAFT] Reply LS on EPS support for IoT NTN in Rel-17 | MediaTek Inc. | Rel-17 | Response to S2-2108261. CC#2: r05 agreed. Revised to S2-2109344. | Hannu (Nokia) points out the obvious for the comment feed, that this proposes LS Out cannot be evaluated before conclusion on all related CRs. ==== Revisions Deadline ==== Guillaume (MediaTek Inc.) provides r01 in drafts. Haris(Qualcomm) comments on r01 in DRAFTS and proposes additions Guillaume (MediaTek Inc.) provide r02 in drafts. Tao(VC) check can we live with the proposal by Haris Sherry (Xiaomi) replies. Sherry (Xiaomi) provides r03 in the draft folder. Jean Yves (Thales) supports r03. Wanqiang (Huawei) prefer r02. R03 does not really reflect the status Guillaume (MediaTek Inc.) prefers r02 Jean Yves (Thales) is ok with r02 also. Sherry (Xiaomi) comments and prefers r03. Wanqiang (Huawei) think r03 is wrong, and we have to take r02. ==== Comments Deadline ==== Sherry (Xiaomi) can't accept r02. Sherry (Xiaomi) provides r04. Guillaume (MediaTek Inc.) comments Guillaume (MediaTek Inc.) provides r05 with the correct TDoc# (8823 not 8937). OK with r02, not r03/r04. Chris (Vodafone) says that r05 looks good. Sherry (Xiaomi) is fine with r05. Hannu (Nokia) thanks Guillaume for the update and supports r05. | Revised |
| 8.27 | S2-2109344 | LS OUT | Approval | Reply LS on EPS support for IoT NTN in Rel-17 | SA WG2 | Rel-17 | CC#2: Revision of S2-2108823r05. Approved | Approved | |
| 8.27 | S2-2108271 | LS In | Action | LS from RAN WG2: LS on supporting discontinuous coverage in IoT NTN | RAN WG2 (R2-2109213) | Rel-17 | Revision of S2-2107047 from S2#147E. Postponed | Postponed | |
| 8.27 | S2-2108712 | CR | Approval | 23.401 CR3673 (Rel-17, 'C'): Multiple TACs handling for IoT NTN | OPPO | Rel-17 | Postponed | DongYeon (Samsung) comments. Haris(Qualcomm) proposes to postpone this CR to February SA2 meeting Guillaume (MediaTek Inc.) proposes to merge 8712 into 8824. Jean Yves (Thales) comments on 8.11 & 8.27 synchronization and propose to postpone this CR. Jingran (OPPO) is ok to postpone. Stefan (Ericsson) supports to postpone Sherry (Xiaomi) proposes to postpone this CR to align with the conclusion on the same issue under 8.11. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.27 | S2-2108742 | CR | Approval | 23.401 CR3674 (Rel-17, 'C'): Support of discontinuous coverage in IoT NTN | Huawei, HiSilicon | Rel-17 | Postponed | Haris(Qualcomm) comments Stefan (Ericsson) provides comments Wanqiang (Huawei) provides feedback on the technical issues Chris (Vodafone) asks on technical issues Sherry (Xiaomi) comments and prefers to study the issue in R18. Hannu (Nokia) supports the proposal to postpone. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.27 | S2-2108743 | CR | Approval | 23.682 CR0488 (Rel-17, 'C'): Support of discontinuous coverage in IoT NTN | Huawei, HiSilicon | Rel-17 | Postponed | Haris(Qualcomm) comments Stefan (Ericsson) provides comments Sherry (Xiaomi) has the same comments as to 8742. Hannu (Nokia) supports the proposal to postpone. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.27 | S2-2108744 | CR | Approval | 23.271 CR0436R2 (Rel-17, 'B'): LCS enhancement for IoT NTN in EPS | Huawei, HiSilicon, MediaTek Inc. | Rel-17 | Revision of (Agreed) S2-2108026 from S2#147E. r01 agreed. Revised to S2-2109195. | Stefan (Ericsson) provides r01 Hannu (Nokia) asks why this EPS CR needs to be treated under NR satellite access WID and AI? Stefan (Ericsson) used the wrong AI# in subject. Has been resent with correct AI# Hannu (Nokia) prefers r01 but can also live with the original version of the CR. ==== Revisions Deadline ==== Guillaume (MediaTek Inc.) ok with r01 Tyler (OTD) prefers r01 Steve (Huawei) is ok with r01. ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2109195 | CR | Approval | 23.271 CR0436R3 (Rel-17, 'B'): LCS enhancement for IoT NTN in EPS | Huawei, HiSilicon, MediaTek Inc. | Rel-17 | Revision of S2-2108744r01. Approved | Agreed | |
| 8.27 | S2-2108745 | CR | Approval | 23.682 CR0487R1 (Rel-17, 'B'): Support IoT NTN in EPS | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107624 from S2#147E. r02 agreed. Revised to S2-2109196. | Stefan (Ericsson) provides r01 Hannu (Nokia) asks why this EPS CR is moved to NR satellite access WI and AI? Stefan (Ericsson) provides comments Steve (Huawei) is ok with r01 Hannu (Nokia) agrees r01 but asks a question on the new sub clause title and EPS satellite access. Chris provides r02 as editorial alignment of r01 ==== Revisions Deadline ==== Guillaume (MediaTek): ok with r02. Steve (Huawei) is ok with r02. ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2109196 | CR | Approval | 23.682 CR0487R2 (Rel-17, 'B'): Support IoT NTN in EPS | Huawei, HiSilicon | Rel-17 | Revision of S2-2108745r02. Approved | Agreed | |
| 8.27 | S2-2108784 | CR | Approval | 23.203 CR1136R2 (Rel-17, 'B'): Support policy and QoS control for satellite access | Huawei, HiSilicon, Qualcomm | Rel-17 | Revision of (Agreed) S2-2108028 from S2#147E. Approved | Agreed | |
| 8.27 | S2-2108824 | CR | Approval | 23.401 CR3663R2 (Rel-17, 'B'): Introduction of Satellite support for Cellular IoT | MediaTek Inc., Deutsche Telekom, Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2108025 from S2#147E. r05 agreed. Revised to S2-2109197. | Fei (OPPO) provides r01. Stefan (Ericsson) provides r02 Guillaume (MediaTek Inc.): ok with r02 Sherry (Xiaomi) comments. Hannu (Nokia) provides r03. Hannu (Nokia) replies to Sherry on the indication of 'country'. Guillaume (MediaTek Inc.) provides r04. Sherry (Xiaomi) replies to Hannu. Haris(Qualcomm) provides r05 ==== Revisions Deadline ==== Guillaume (MediaTek): ok with r05 Steve (Huawei) is ok with r05. Sherry (Xiaomi) is ok with r05. ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2109197 | CR | Approval | 23.401 CR3663R3 (Rel-17, 'B'): Introduction of Satellite support for Cellular IoT | MediaTek Inc., Deutsche Telekom, Huawei, HiSilicon, Nokia. Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2108824r05. Approved | Agreed | |
| 8.27 | S2-2108825 | WID REVISED | Approval | Revised WID: 'Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS' [IoT_SAT_ARCH_EPS]. | MediaTek Inc. | Rel-17 | r03 agreed. Revised to S2-2109198. | Hannu (Nokia) provides r01 of the WID. Guillaume (MediaTek Inc.) replies to Hannu (Nokia). Guillaume (MediaTek Inc.) provides r01 in the rev folder Haris(Qualcomm) proposes WID revision in DRAFTS Stefan (Ericsson) provides r02 in rev folder Guillaume (MediaTek Inc.) provides r03 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2109198 | WID REVISED | Approval | Revised WID: 'Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS' [IoT_SAT_ARCH_EPS]. | MediaTek Inc. | Rel-17 | Revision of S2-2108825r03. Approved | Approved | |
| 8.27 | S2-2108937 | CR | Approval | 23.401 CR3667R1 (Rel-17, 'C'): Support for IoT NTN with discontinuous coverage | Vodafone, MediaTek Inc., Sateliot, Novamint | Rel-17 | Revision of (Postponed) S2-2107723 from S2#147E. r04 agreed. Revised to S2-2109199. | Haris(Qualcomm) objects to the CR Vodafone (Chris) answers the technical questions from Qualcomm Haris(Qualcomm) provides further comments Sherry(Xiaomi) comments Hannu (Nokia) responds to Haris and supports this CR. Chris (Vodafone) answers the Xiaomi comments Haris(Qualcomm) comments Haris(Qualcomm) provides r02 Sherry(Xiaomi) provides r03. Chris (Vodafone) provides r04. ==== Revisions Deadline ==== Guillaume (MediaTek Inc.) supports r04 Jean Yves (Thales) supports r04 Sherry (Xiaomi) supports r04 Haris(Qualcomm) is ok with r04 Wanqiang (Huawei) is ok with r04 as progress ==== Comments Deadline ==== | Revised |
| 8.27 | S2-2109199 | CR | Approval | 23.401 CR3667R2 (Rel-17, 'C'): Support for IoT NTN with discontinuous coverage | Vodafone, MediaTek Inc., Sateliot, Novamint | Rel-17 | Revision of S2-2108937r04. Approved | Agreed | |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=19 | - | |
| 8.28 | S2-2108280 | LS In | Action | LS on Slice list and priority information for cell reselection | CT WG1 (C1-216256) | Rel-17 | CC#2: Postponed | Postponed | |
| 8.28 | S2-2108996 | LS In | Action | Reply LS on Slice list and priority information for cell reselection | RAN WG2 (R2-2111310) | Rel-17 | Response drafted in S2-2109016. Postponed | Postponed | |
| 8.28 | S2-2109016 | LS OUT | Approval | [DRAFT] Reply LS on Slice list and priority information for cell reselection | China Mobile | Rel-17 | Created at CC#1. Response to S2-2108996. CC#2: The related CRs were not agreed and this LS was noted. | Dan (China Mobile) provides LS in revision folder alessio(Nokia) provides revision 01 Peter Hedman (Ericsson) provides r02. ==== Revisions Deadline ==== Guillaume (MediaTek Inc.) suggests to keep this open as it is dependent on the conflicting CRs ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2109012 | LS In | Action | LS from RAN WG3: LS on Clarification of SCG outside RA for slicing | RAN WG3 (R3-216237) | Rel-17 | Postponed | Postponed | |
| 8.28 | S2-2108471 | CR | Approval | 23.501 CR3317R1 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes | Ericsson, China Mobile | Rel-17 | Revision of (Noted) S2-2107556 from S2#147E. Noted | Alessio(Nokia) as already commented for the document S2-2108798 we suggest to postpone handling of priority topic to eNS_Ph3, cannot accept the approach in this CR. Peter Hedman (Ericsson) provides comments Guillaume (MediaTek Inc.) comments and asks for misc. clarification. Dieter (Deutsche Telekom) comments. Peter Hedman (Ericsson) provides r01 Dan(China Mobile) comments. Peter Hedman (Ericsson) provides r02 Dan (China Mobile) provides reply to Guillaume Alessio(Nokia) sees no rush to approve CRs at this meeting.in particular the topic of priority is contentious for this release (some see it contentious even for rel-18 I have just seen !) Guillaume (MediaTek Inc.) responds to Peter (Ericsson) and provide r03 Peter Hedman (Ericsson) provides r04 Dongeun (Samsung) provides r05 Alessio(Nokia) proposes to merge this in 8845 that only covers the group assignment topic. it is not feasible to agree on priority discussion in this release. ==== Revisions Deadline ==== alessio(Nokia) objects to any CR including priority topic Guillaume (MediaTek) proposed to postpone or note this CR (and 8845) Peter Hedman (Ericsson) provides reply to Dongeun (Samsung) and do not think there is a need for separate list of groups per TA as in r05. Dongeun (Samsung) provides reply to Peter (Ericsson) Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. Dan (China Mobile) propose we should work on this and try to get some conclusoin in R17 ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108618 | DISCUSSION | Agreement | Discussion on the Granularity of Slice Groups for Cell Re-selection. | Samsung | Rel-17 | Noted | Noted | |
| 8.28 | S2-2108620 | CR | Approval | 23.502 CR3264 (Rel-17, 'B'): Support Slice group for cell re-selection | Samsung | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Dieter (Deutsche Telekom) comments. ==== Revisions Deadline ==== Peter Hedman (Ericsson) object to any CR that only covers slice grouping and not the priority handling Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108781 | CR | Approval | 23.501 CR3427 (Rel-17, 'B'): Support Slice group for cell re-selection | Samsung | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Dieter (Deutsche Telekom) comments. ==== Revisions Deadline ==== Peter Hedman (Ericsson) object to any CR that only covers slice grouping and not the priority handling Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108764 | CR | Approval | 23.501 CR3424 (Rel-17, 'F'): Slice Group ID Management | Huawei | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Alessio(Nokia) this is not far apart from what we proposes and suggests to merge this into S2-2108845 Dieter (Deutsche Telekom) comments. Haiyang (Huawei) is ok to merge into S2-2108845 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108765 | CR | Approval | 23.502 CR3286 (Rel-17, 'F'): Slice Group ID management | Huawei, HiSilicon | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Dieter (Deutsche Telekom) comments. ==== Revisions Deadline ==== Peter Hedman (Ericsson) object to any CR that only covers slice grouping and not the priority handling Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108798 | CR | Approval | 23.502 CR3194R1 (Rel-17, 'B'): Support of slice priority and slice group information for cell (re)selection | China Mobile | Rel-17 | Revision of (Noted) S2-2107535 from S2#147E. Noted | Dan (China Mobile) provides r01 Alessio(Nokia) comments and suggest to postpone handling of priority topic to eNS_Ph3, cannot accept r01 nor r00 and proposes to merge into S2-2108866 Dieter (Deutsche Telekom) comments. Dan (China Mobile) provide r02 Alessio(Nokia) sees no rush to approve CRs at this meeting.in particular the topic of priority is contentious for this release (some see it contentious even for rel-18 I have just seen !) Dan (China Mobile) provide r03 with removing Allowed NSSAI related parameters Dongeun (Samsung) provides r04. This is an 23.502 alignment with 23.501 CR (8471r05) alessio(Nokia) proposes to merge this into the nokia et al CR in S2-2108866 which is addressing only the group aspect. we prefer to note this one ==== Revisions Deadline ==== alessio(Nokia) objects to any CR revision including priority topic ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108943 | CR | Approval | 23.501 CR3319R2 (Rel-17, 'B'): Support for Paging Early Indication | Qualcomm Inc. | Rel-17 | Revision of (Revised and Agreed) S2-2107584 from S2#147E. Merged into S2-2109339 | Hannu (Nokia) comments proposes to merge the agreeable parts of this CR to S2-2108959. Guillaume (MediaTek Inc.) proposed to merge 8943 in 8959 Miguel (Qualcomm) responds to Hannu Miguel (Qualcomm) ok to merge in S2-2108959 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Merged |
| 8.28 | S2-2108959 | CR | Approval | 23.501 CR3319R3 (Rel-17, 'B'): Support for Paging Early Indication | Vodafone [rev 1 was MediaTek Inc., Qualcomm Inc., OPPO, Apple, Ericsson, Huawei, HiSilicon] | Rel-17 | Revision of (Agreed) S2-2107857 from S2#147E. r08 agreed. Revised to S2-2109339, merging S2-2108943 | Qian (Ericsson) provides comments and asks questions Hannu (Nokia) provides r01 and proposes to take this CR as the template for further work. Guillaume (MediaTek Inc.) provides r02. Chris (Vodafone) answers Ericsson. Qian (Ericsson) provides comments and r03 Tricci (OPPO) provides r04 to add an EN to clarify that the support for the paging probability info is subject to RAN2 agreement. Chris (Vodafone) provides r05 in order to avoid this feature INCREASING UE power consumption. Qian (Ericsson) comments on r05 and express concerns. Steve (Huawei) comments Chris (Vodafone) answers Ericsson and Huawei. Guillaume (MediaTek Inc.) provides r06 (pls ignore) and r07 Qian (Ericsson) comments on provides r07. Qian (Ericsson) indicates that r08 is provided (instead of r07 as in previous comment). ==== Revisions Deadline ==== As a basis for further work Chris (Vodafone) can accept r08 with the cover sheet tidied up to remove the 'r03 updates...' Miguel (Qualcomm) is ok with r08. Guillaume (MediaTek Inc.) provides r09 in drafts - basic clean-ups. Steve (Huawei) is ok with r08 + coversheet clean-up. ==== Comments Deadline ==== Hannu (Nokia) request this for CC and asks whether there was any discussion on re-inserting the UE assistance info (in the form of paging assistance data) since r01? Chris (Vodafone) answers Nokia. Guillaume (MediaTek Inc.) confirms the paging probability information was indeed discussed explicitly before yesterday's deadline and was not rediscussed today. An EN was added by Tricci/Oppo. Hannu (Nokia) thanks Chris and Guillaume for their explanation on the UE provided paging probability topic. Tricci (OPPO) thanks Guillaume (MediaTek) great work for the merge and clarifications. Tricci (OPPO) can support r08 + coversheet clean-up. | Revised |
| 8.28 | S2-2109339 | CR | Approval | 23.501 CR3319R4 (Rel-17, 'B'): Support for Paging Early Indication | MediaTek Inc., Qualcomm Inc., OPPO, Apple, Ericsson, Huawei, HiSilicon, Vodafone, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2108959r08, merging S2-2108943. Approved | Agreed | |
| 8.28 | S2-2108944 | CR | Approval | 23.502 CR3216R2 (Rel-17, 'B'): Support of Paging subgrouping | Qualcomm Incorporated | Rel-17 | Revision of (Agreed) S2-2107858 from S2#147E. CC#2: This was left for further update for decision at CC#3. CC#3: Postponed | Hannu (Nokia) proposes to note this CR. Miguel (Qualcomm) responds to Hannu, prefers to keep open and dependent on the 23.501 discussion, e.g. S2-2108959 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Postponed |
| 8.28 | S2-2108866 | CR | Approval | 23.502 CR3300 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Jinhua(Xiaomi) provides r01, Dongeun (Samsung) provides r02 Dieter (Deutsche Telekom) comments. Peter Hedman (Ericsson) provides comments Alessio(Nokia) can live with r02 Jinhua(Xiaomi) provides r03, Alessio(Nokia) thanks Jinhua(Xiaomi) who provided r03, which is acceptable to us. ==== Revisions Deadline ==== Peter Hedman (Ericsson) object to any CR that only covers slice grouping and not the priority handling Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2108845 | CR | Approval | 23.501 CR3436 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Peter (Ericsson) provides comments and propose we should cover both group aspects and the priority handling Dongeun (Samsung) provides comments Alessio(Nokia) this is moved to AI#8.28 Alessio(Nokia) despite it is in 8.28, I can reply to Dongeun (Samsung) that we are happy to consider enhancements to cover the per TA granularity. Dongeun (Samsung) provides r01 and comments Dieter (Deutsche Telekom) comments. Peter Hedman (Ericsson) provides comments Alessio(Nokia) would then be ok to postpone this to rel-18 as the topic of priority is contentious for this release (some see it contentious even for rel-18I have just seen !) Alessio(nokia) can live with r01 Haiyang (Huawei) provides r02 ==== Revisions Deadline ==== Jinhua(Xiaomi) prefer r02, agree with Haiyang, Guillaume (MediaTek) proposed to note or postpone this CR Peter Hedman (Ericsson) object to any CR that only covers slice grouping and not the priority handling Dieter (Deutsche Telekom) proposes to postpone or note this CR as per previous comment. alessio(Nokia) replies and would welcome a change of heart by Mediatek Genadi (Lenovo) supports the r02. Guillaume (MediaTek Inc.) replies ==== Comments Deadline ==== Tricci (OPPO) supports the r02 to align with RAN2 conclusions. | Noted |
| 8.28 | S2-2108259 | LS In | Action | LS from RAN WG2: Reply LS on Cell reselection with band-specific network slices | RAN WG2 (R2-2108868) | Rel-17 | Revision of S2-2107011 from S2#147E. Noted | Tao(VC) suggest to NOTE this LS suppose this has been acknowledged after 3 meetings. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 8.28 | S2-2109371 | LS In | Action | LS from RAN WG2: LS on paging subgrouping and PEI | RAN WG2 (R2-2111415) | Rel-17 | Postponed | Steve (Huawei) Suggests postponing. Guillaume (MediaTek Inc.) agrees this should be postponed. ==== Comments Deadline ==== | Postponed |
| 9 | - | - | - | Project Planning and Managemen | - | - | Docs:=0 | - | |
| 9.1 | - | - | - | New and Revised Work Items, TS/TR Cover sheets, Exception Sheets | - | - | Docs:=0 | - | |
| 9.1.1 | - | - | - | Rel-17 new and revised Work Items | - | - | Docs:=1 | - | |
| 9.1.1 | S2-2108417 | WID NEW | Approval | New WID on 5G Architecture Enhancements for RAN Slicing for NR. | China Mobile | Rel-17 | Revision of (Noted) S2-2107273 from S2#147E. Noted | Alessio(Nokia) expects we do not need a new WID, soe we can note this. We can reuse eNS_Ph2 WID and update it to cover alignment with NR_Slice-Core RAN WI as an objective. this can be an updated WID for SA#94 the rapporteur or another company can submit. ==== Revisions Deadline ==== Dan(China Mobile) OK to note this wid and we can try to update the eNS_Ph2 WID in SA plenary. ==== Comments Deadline ==== | Noted |
| 9.1.2 | - | - | - | TS/TR Cover sheets | - | - | Docs:=0 | - | |
| 9.1.3 | - | - | - | Revision of Rel-18 SID/WID proposal POSTPONED at SA2#147E | - | - | Docs:=56 | - | |
| 9.1.3 | S2-2108369 | SID NEW | Approval | New SID: Study on enhanced support of NR RedCap with long eDRX for RRC INACTIVE State. | Ericsson, Deutsche Telekom, Verizon, Xiaomi, Sony, Nokia, Nokia Shanghai Bell, MediaTek, AT&T, Apple, Qualcomm, Vodafone, InterDigital, China Mobile. | Rel-18 | r02 agreed. Revised to S2-2109323. | Jinsook (DISH Network) provides r01. Qian (Ericsson) comments that r01 is not uploaded by rapporteur and rapporteur will upload a new revision with more supporting companies. Hannu (Nokia) supports r01 as reasonable clarification of the wording and looks forward to the rapporteur version. Qian (Ericsson) comments and provides r02 on top of r01. Wanqiang (Huawei) ok with r02. ==== Revisions Deadline ==== Lars (Sony) ok with r02. Sherry (Xiaomi) is fine with r02 and using TR for the study. Jinsook (DISH Network) is also fine with r02 and using TR. ==== Comments Deadline ==== Hannu (Nokia) can live with his own r01 but prefers subsequent r02 | Revised |
| 9.1.3 | S2-2109323 | SID NEW | Approval | New SID: Study on enhanced support of NR RedCap with long eDRX for RRC INACTIVE State. | Ericsson, Deutsche Telekom, Verizon, Xiaomi, Sony, Nokia, Nokia Shanghai Bell, MediaTek, AT&T, Apple, Qualcomm, Vodafone, InterDigital, China Mobile, OPPO, DISH Network. | Rel-18 | Revision of S2-2108369r02. Approved | Approved | |
| 9.1.3 | S2-2108370 | DISCUSSION | Agreement | Discussion on NR RedCap with long eDRX in RRC Inactive SID handling and summary of the reviewed solutions. | Ericsson | Rel-18 | Noted | Hannu (Nokia) requests that whichever way the candidate solutions are documented, SA2 must leave a quotable document on the conclusions. Dieter (Deutsche Telekom) also prefers a TR. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108379 | WID NEW | Approval | New WID on Use of L4S in 5GS (5G_L4S) . | Ericsson | Rel-18 | CC#3: 5 objections. Noted | Hui (Huawei) objects r00 and provides r01. Youngkyo(Samsung) provides some questions for understanding. Hui (Huawei) objects r00, provides draft r01. Hucheng (CATT) comments. Paul (Ericsson) replies to Hui (Huawei). Paul (Ericsson) replies to Youngkyo(Samsung) and Hucheng (CATT). Hui (Huawei) replies to Paul (Ericsson). Youngkyo(Samsung) provides further comment and question. Antoine (Orange) supports r00 i.e a Study is not needed. Curt (Charter) supports Antoine (Orange) Jinguo (ZTE) supports to have study first Dieter (Deutsche Telekom) also supports original WID, i.e. no study is needed. Paul (Ericsson) replies to Youngkyo(Samsung). Sriram (CableLabs) supports original WID, i.e. no study is needed. Devaki (Nokia) supports L4S as a WID (r00) to keep the work focused. Krisztian (Apple) supports r00, there's no need to convert this into a SID. Youngkyo(Samsung) replies. Paul (Ericsson) replies to Jinguo (ZTE). Jinguo(ZTE) replies Patrice (Huawei) reminds that the argument for a direct WID only works when there is a complete WG consensus on the proposed solution, and therefore a SID is the only appropriate approach in this case. And even if there were a full consensus on the exact solution (which is not the case), this should be then dealt as a TEI18, therefore not part of the agenda at this meeting. Yali (OPPO) comments and shares the view from Jinguo(ZTE). Paul (Ericsson) replies to Youngkyo (Samsung). Paul (Ericsson) replies to Jinguo (ZTE) and Yali (OPPO). Yali (OPPO) replies to Paul (Ericsson). Paul (Ericsson) replies to Yali (OPPO). Paul (Ericsson) thanks Huawei for the lesson on how it works, maybe we can help your understanding that since there is no full consensus as you say on details, that is why it is a WI. Patrice (Huawei) thanks Paul (Ericsson) on his compliment regarding the lesson on how it works, and clarifies that since there is no full consensus (and not on details only), that is why it has to be a SID. Gerry (Verizon) supports r00 and we also do not see the need for a study. ==== Revisions Deadline ==== Farooq (AT&T) also supports r00 and we also do not see the need for a study. Jinsook (DISH Network) We also support original WID, no need any study phase. Serge M (T-Mobile USA) also supports r00 and we also do not see the need for a study. Guillaume (MediaTek Inc.) supports r00 Paul (Ericsson) provides a proposal. This feature has been discussed since 2 years now, in that time its specification in IETF also further matured. L4S is becoming well established in the industry and a there is a high interest for its introduction in 3GPP. The WID has a clear and well defined scope and a wide support in SA2 to be progressed in Rel-18. Given all technical comments and questions being addressed, we propose to approve this Rel-18 WID r00 at this meeting. Jinguo(ZTE) asks why UE is excluded to support L4S? Lars (Sony) also supports r00 Hui (Huawei) insists that a study item is needed.. ==== Comments Deadline ==== Shabnam (Ericsson) asks to discuss at CC#2 to find a reasonable way forward, for a mature technology with nothing to study but reflect how 3GPP system can enable this feature option, reusing 3GPP existing architecture and mechanism. Paul (Ericsson) provides r01 to the CC#2. Hui(Huawei) disagree with r01 provided by Paul. | Noted |
| 9.1.3 | S2-2108463 | SID NEW | Approval | New SID: Study on enhanced support of Non-Public Networks phase 2. | Ericsson, Futurewei, Convida Wireless, Charter, China Unicom, ETRI; Cisco, China Mobile, Lenovo, Motorola Mobility, Qualcomm, ZTE, Philips, Intel, Matrixx, SHARP, InterDigital, LG Electronics, NEC, Samsung, OPPO, T-Mobile USA, NICT | Rel-18 | CC#3: r05 agreed. Revised to S2-2109353. | Peter Hedman (Ericsson) provides r01 Sebastian (Qualcomm) comments Curt (Charter) comments Qianghua (Huawei) provides comments Saso (Intel) comments Peter Hedman (Ericsson) provides replies. Marco (Huawei) comments Marco (Huawei) answers to Curt (Charter) comment Peter Hedman (Ericsson) provides r02 Dieter (Deutsche Telekom) comments. Hualin(Huawei) have similar comments as Sebastian (Qualcomm) to go back to 'non-3GPP' ==== Revisions Deadline ==== Sebastian (Qualcomm) objects to r00 - r02 for reasons given earlier Peter Hedman (Ericsson) provides reply and ok to change back objective 2 as proposed, r03 in draft folder Rainer (Nokia) comments. Sebastian (Qualcomm) is ok with r03 in draft folder ==== Comments Deadline ==== Jarmo (KPN) would like to support the study. Peter Hedman (Ericsson) provides r05 (and r04) in CC#3 folder | Revised |
| 9.1.3 | S2-2109353 | SID NEW | Approval | New SID: Study on enhanced support of Non-Public Networks phase 2. | Ericsson, Futurewei, Convida Wireless, Charter, China Unicom, ETRI; Cisco, China Mobile, Lenovo, Motorola Mobility, Qualcomm, ZTE, Philips, Intel, MATRIXX Software, SHARP, InterDigital, LG Electronics, NEC, Samsung, OPPO, T-Mobile USA, NICT, DISH Network, vivo, KPN, CableLabs | Rel-18 | Revision of S2-2108463r05. Approved | Approved | |
| 9.1.3 | S2-2108518 | DISCUSSION | Information | Discussion paper on Network & Computing Power integration | China Telecom | Revision of (Noted) S2-2107563 from S2#147E. Noted | Laurent (Nokia): proposes to Note this discussion paper (objects to it) and to concentrate on the SID discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 9.1.3 | S2-2108519 | SID NEW | Approval | New SID on Study on integration of network and computing power in 5GS . | China Telecom | Revision of (Postponed) S2-2107562 from S2#147E. Noted | Guliang (Inspur) support the SID and would like to co-source it. Laurent (Nokia): expresses serious concerns Haris(Qualcomm) objects to this SID Saso (Intel) objects to this SID Shabnam (Ericsson) shares same view as expressed during MED and similar to Intel, Qualcomm, Nokia, as such objects to this SI. Jungshin (Samsung) objects to this SID.. Yifan (China Telecom) provides r01. Laurent (Nokia): objects to any version of this SID ==== Revisions Deadline ==== Yifan (China Telecom) replies. ==== Comments Deadline ==== | Noted | |
| 9.1.3 | S2-2108529 | SID NEW | Approval | New SID on Study on Support of Satellite Backhauling in 5GS . | CATT | Rel-18 | Revision of (Postponed) S2-2107429 from S2#147E. CC#3: r04 agreed. Revised to S2-2109354. | Stefan (Ericsson) provides comments and a revision in DRAFTS Haris(Qualcomm) Wanqiang (Huawei) provides a revision in DRAFTS Hucheng (CATT) responds to the comments. Hannu (Nokia) comments that the original version is definitely not acceptable and may come back with comments on the proposed revisions later. Hucheng (CATT) provides r01 based on the draft revisions from Ericsson, Qualcomm and Huawei. Leo (Deutsche Telekom) provides comments. Hucheng (CATT) replies to Leo (Deutsche Telekom). Hannu (Nokia) shares Leo's concern on charging. Hucheng (CATT) clarifies the charging aspect to Hannu (Nokia). Hucheng (CATT) provides r02 based on the comments. Hannu (Nokia) provides revision in drafts area and asks question on the justification for WT#4. Hucheng (CATT) thanks for Hannu's revision and clarifies the use cases for WT#4. Stefan (Ericsson) comments and provided a revision in DRAFTS Leo (Deutsche Telekom) comments Hucheng (CATT) replies to Stefan (Ericsson)'s comments and provided r03. ==== Revisions Deadline ==== Haris(Qualcomm) comments Hucheng (CATT) replies to Haris(Qualcomm) Hucheng (CATT) replies to Leo. Hucheng (CATT) replies to Stefan (Ericsson) and points out that there is a SA1 requirement related to limited bandwidth. Hucheng (CATT) replies to Haris(Qualcomm) and provides r04 and r05 into draft folder, but prefer r04. Wanqiang (Huawei) prefers r04. Haris(Qualcomm) is ok with either r04 or r05 Jean Yves (Thales) ok also with either r04 or r05 Stefan (Ericsson) prefers r05 ==== Comments Deadline ==== Hannu (Nokia) prefers r05 | Revised |
| 9.1.3 | S2-2109354 | SID NEW | Approval | New SID on Study on Support of Satellite Backhauling in 5GS . | CATT | Rel-18 | Revision of S2-2108529r04. Approved | Approved | |
| 9.1.3 | S2-2108543 | DISCUSSION | Discussion | The Discussion on the motivation of Passive IoT | China Mobile | Rel-18 | Revision of (Noted) S2-2107559 from S2#147E. Noted | Hannu (Nokia) comments that since the corresponding SA1 SID is not approved and it's targeting Rel-19, it is not possible to plan the SA2 work in Rel-18. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108573 | DISCUSSION | Information | Moderated email discussion on FS_GMEC. | Huawei/Samsung (moderator) | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108574 | SID NEW | Approval | New SID on generic group management, exposure and communication enhancements. | Huawei, HiSilicon, Samsung, CATT, China Mobile, China Telecom, China Unicom, ZTE, Juniper, SK Telecom, KT Corp, LG Uplus, KPN, Siemens, Robert Bosch GmbH, LGE, Spreadtrum Communications, ETRI, CAICT, China Southern Power Grid, CEPRI, CBN, SIA | Rel-18 | Revision of (Postponed) S2-2108163 from S2#147E. CC#3: r09 was agreed. Revised to S2-2109355. | Antoine (Orange) provides r01. Dieter (Deutsche Telekom) agrees with Orange's comment on WT1.2 and in addition comments. Stefan (Ericsson) provides comments and questions Qianghua (Huawei) replies Sebastian (Qualcomm) provides revision in drafts folder Rainer (Nokia) comments. Qianghua (Huawei) provides r02 and responses Rainer (Nokia) proposes updates to WT1.1 and WT1.2. Stefan (Ericsson) provides replies Qianghua (Huawei) provides r03 and responses Qianghua (Huawei) provides r04 Sebastian (Qualcomm) provides r07 in drafts/GMEC Rainer (Nokia) replies and prefers to split the SI in two parts. Rainer (Nokia) replies, cannot accept removing of WT1.1 sub-bullet. Stefan (Ericsson) also prefers separate studies on group management and traffic handling aspects, as was commented already last SA2 meeting Qianghua (Huawei) replies and provide r05, and proposes that we follow the summary and way proposal resulting from MED progress Sebastian (Qualcomm) replies to Nokia and Huawei Qianghua (Huawei) provides r06 Sebastian (Qualcomm) comments on r05 ==== Revisions Deadline ==== Rainer (Nokia) cannot accept r06. Sebastian (Qualcomm) objects to any revision that includes the WT '- create/modify/delete groups for other purposes besides group communication' because there is nothing to be done except from some Edge scenario, which overlaps with a WT in the already approved Edge SID Sang-Jun (Samsung) prefers not to split, and reminds Rainer (Nokia) that the MED already showed 15 of 18 companies prefer not to split. Chi (China Unicom) prefers not to split as CUC has shown the opinion during the MED. Heng (China Telecom) prefers not to split. Wonjung (LG Uplus) prefers not to split. Patrice (Huawei) comments regarding the relation with Edge computing ph2 work. DongJin Lee (SK Telecom) prefers not to split. Sebastian (Qualcomm) replies to Patrice; objects to r00-r06, provides r07 in drafts/GMEC Stefan (Ericsson) comments again on WT#4 artificially restricted to 5G VN and provides update in DRAFTS Qianghua (Huawei) provides r08draft in DRAFTS Sebastian (Qualcomm) comments that r08draft in DRAFTS is ok ==== Comments Deadline ==== Qianghua (Huawei) provides r09 in DRAFTS, only change on r08draft is 'Enhance group attribute management' Qianghua (Huawei) proposes to take r09 in DRAFTS in CC#2 for confirmation | Revised |
| 9.1.3 | S2-2109355 | SID NEW | Approval | New SID on generic group management, exposure and communication enhancements. | Huawei, HiSilicon, Samsung, CATT, China Mobile, China Telecom, China Unicom, ZTE, Juniper, SK Telecom, KT Corp, LG Uplus, KPN, Siemens, Robert Bosch GmbH, LGE, Spreadtrum Communications, ETRI, CAICT, China Southern Power Grid, CEPRI, CBN, SIA, DISH Network, Volkswagen AG, Quectel | Rel-18 | Revision of S2-2108574r09. Approved | Approved | |
| 9.1.3 | S2-2108575 | SID NEW | Approval | Study on Interworking of Non-3GPP Multicast and Broadcast Networks with 3GPP 5G System. | Saankhya Labs, Ligado Networks, ONE Media 3.0, Fraunhofer IIS, CEWiT, Tejas Networks, IIT Bombay, IIT Kanpur, IIT Madras, IIT Hyderabad, IIT Kharagpur | Rel-18 | Revision of (Postponed) S2-2107129 from S2#147E. CC#3: Noted | Antoine (Orange) asks what kind of impacts to UICC apps are envisionned. Anindya Saha (SaankhyaLabs) responds to the Question on 'Elaboration of what kind of impacts to UICC apps are envisioned?' Miguel (Qualcomm) has concerns with this SID, that the service requirements are not clear, there is no SA1 related work. Stefan (Ericsson) comments that stage 1 requirements are missing Dieter (Deutsche Telekom) we share the concerns expressed by Qualcomm and Ericsson. Thomas (Nokia) also shares the concerns expressed by Qualcomm and Ericsson. Comments that objectives read like TR working procedures and would also require improvements First objective reads like stage 1 work Wanqiang (Huawei) shares the same concern, and on this non-3GPP multicast and broadcast integration to 5GC, we need more broad requirement level discussion first to consolidate what 3GPP can offer. Anindya Saha (SaankhyaLabs) responds to the concerns raised by Stefan (Ericsson), Miguel (Qualcomm), Dieter (Deutsche Telekom), Thomas (Nokia) and Wanqiang (Huawei). ==== Revisions Deadline ==== Anindya Saha (SaankhyaLabs) observes that the requirements and use cases for multicast/broadcast services as captured in 3GPP stage 1 document TS 22.261, TS 22.101, and TS 22.246 already allow for Interworking of non-3GPP satellite networks and non-3GPP DTT networks with 5GS. Miguel (Qualcomm) objects to this SID Stefan (Ericsson) objects to SID and restates concerns Anindya Saha (SaankhyaLabs) seeks detailed clarifications to the objections from Miguel (Qualcomm), and Stefan (Ericsson) citing sections from as captured in 3GPP stage 1 documents TS 22.261 which clearly mention non-3GPP Access for Satellite Communication. Dieter (Deutsche Telekom) objects to SID and replies to Anindya Saha (SaankhyaLabs). Clive Packer, Ligado Networks Services such as Firmware-Over-The-Air (FOTA) might be delivered very efficiently via satellite broadcast due to the pervasive coverage provided by it. Another example of a service that may be considered part of critical infrastructure is satellite delivery of augmentation services for high precision GNSS; this is already part of the planning for automated driving in the future. Multimode, satellite-terrestrial delivery of such services is likely to optimize both the cost and the geographic coverage of such services. Apparently, there is no plan in 3GPP as yet to issue standards for satellite multicast/broadcast over NBIoT and eMTC air interfaces until Release 3GPP 18. Until such services are launched, FOTA & GNSS augmentation (mentioned as examples) could be carried over a multimode 3GPP-cellular/non-3GPP-satellite broadcast network, at least as a gap filler. Therefore, it would be helpful for 3GPP to enable the proposed work. Anindya Saha (SaankhyaLabs) responds to objections raised by Dieter (Deutsche Telekom) and observes that the TS22.261 (3GPP Stage 1 Requirements) has been misunderstood with respect to the proposed SID objectives. ==== Comments Deadline ==== Pranav (IIT Bombay) supports the SID and replies to Dieter (Deutsche Telekom) Anindya Saha (SaankhyaLabs) provides a revision r01 of the SID based on the comments received. Anindya Saha (SaankhyaLabs) provides a revision r02 of the SID and seeks feedback. Anindya Saha (SaankhyaLabs) provides a revision r03 of the SID and seeks feedback. | Noted |
| 9.1.3 | S2-2108594 | SID NEW | Approval | New Study on enhancement of support for Separation and Isolation of NF and data in 5GC. | China Telecom | Rel-18 | Noted | Haris(Qualcomm) comments that the scope of this SID remains unclear and provides justification Rainer (Nokia) comments, asking for clarification. Yubing (China Telecom) replies to Haris (Qualcomm), Rainer (Nokia) and provides r01. Saso (Intel) thinks that this proposal should be considered for SA3. Saso (Intel) objects to this SID. Rainer (Nokia) agrees with Intel to note the SI. Yubing (China Telecom) replies to Saso (Intel). ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108609 | SID NEW | Approval | Study on Enhancement of Network Slicing Phase 3 . | ZTE, LG Electronics, Samsung, Alibaba, Apple, AT&T, CATT, China Telecom, China Unicom, Convida Wireless LLC, Ericsson, Intel, InterDigital, KDDI, Lenovo, Matrixx, MITRE, Motorola Mobility, NEC , Nokia, Nokia Shanghai Bell , NTT Docomo, OPPO, Oracle, Orang | CC#3: r13 endorsed. Revised to S2-2109356. | Antoine (Orange): Obj. 7 needs to be clarified . Jinguo (ZTE) response and provides r01 Patrice (Huawei) comments on the updated r01, with the following considerations. We can likely accept WT1 with some refinements, we object to WT4.2 as it is irrealistic as proposed. We object to WT5 as the (unclear) justification requires either GSMA input, SA1 requirements, or should be done in eUEPO. We have concerns with WT7, especially the lack of SA1 service requirements, and the current WT7 could be acceptable if the additional SA1 requirements can be clearly identified. Further minor updates are indicated in the comments. Myungjune (LGE) replies to Patrice (Huawei) on WT7 Alessio(Nokia) supports the r01 by Jinguo with small changes Kundan (NEC) does not support 4.2 in r01which has lot of system/RAN impact. alessio(Nokia) comments Kundan (NEC) responds to Alessio alessio(Nokia) comments this will need to work only for UEs that are capable of simultaneous registrations.... i.e. with dual RX/TX. Srisakul (NTT DOCOMO) comments and suggests some minor change in WT1. Jinguo(ZTE) response Patrice (Huawei) thanks Myungjune for his clarification and proposes an update to WT7 accordingly. Patrice (Huawei) comments on Jinguo (ZTE)'s rewording. Jinguo(ZTE) provides r02. Ashok (Samsung) comments on WT1 Peter Hedman (Ericsson) provides comments. Alessio(Nokia) supports the wording and comments by Peter(ericsson) Jinguo(ZTE) provides r03 Chia-Lin (MediaTek) provides the comments and ask to remove Obj. 7. alessio(Nokia) cannot live with removal of 4.2 Jinguo(ZTE) response and think WT4.2 is out of scope this study. Genadi (Lenovo) comments on WT1 in r03. Patrice (Huawei) thanks Jinguo (ZTE) for the update, which is mostly fine except that objective 5 needs to be removed. Jinguo(ZTE) replies to Genadi (Lenovo). Dieter (Deutsche Telekom) asks questions for clarification on objective 1. Patrice (Huawei) comments, confirms his objection to any version of the SID that includes WT4.2 in one form or another. Jinguo(ZTE) replies to Dieter (Deutsche Telekom) Myungjune (LGE) replies to Chia-Lin (MediaTek). Jinguo (ZTE) replies to Chia-Lin (MediaTek). Dongeun (Samsung) supports Obj5 provided by Peter (Ericsson) Jinguo(ZTE) provides r04 Patrice (Huawei) objects all revisions so far including r04, due to the presence of WT5. This includes objection to technical endorsement. Once WT5 is removed, barring other changes, we will support the SID. ==== Revisions Deadline ==== Alessio(Nokia comments) Jinguo(ZTE) asks for CC#2 or CC#3. Lets see if we can agree the wording in obj 5. Chia-Lin (MediaTek) provides comments Jinguo(ZTE) provides r05 in draft folder, and replies to Chia-Lin (MediaTek) Chia-Lin (MediaTek) still think Ojb.7 should have nothing to do with the UE and should be removed Jinguo(ZTE) replies to Chia-Lin (MediaTek) Chia-Lin (MediaTek) replies alessio(Nokia) would certainly like this 'by the UE' bit to be removed. Myungjune (LGE) replies to Chia-Lin (MediaTek) and Alessio (Nokia) Patrice (Huawei) requests that WT7 is left as is (i.e. keep the 'by the UE'), as it is what answers the SA1 requirement with the clarification from Myungjune (LGE). Chia-Lin (MediaTek) provides more comments and insists to remove Obj. 7 Patrice (Huawei) proposes further minimal rewording on WT5 to make it acceptable. Chia-Lin (MediaTek) responds to Myungjune (LGE) Jinguo(ZTE) provides r06 in draft folder Chia-Lin (MediaTek) responds to Myungjune(LGE) and considers Obj. 7 is not needed as explained below Myungjune(LGE) responds to Chia-Lin (MediaTek) alessio(Nokia) proposes we discuss on CC#2 the latest version of the SID by Jinguo. Patrice (Huawei) comments, and cannot accept WT7 wording in latest versions, questions the 'e.g.' in WT5. I am still looking for a revision that I can accept (none so far are acceptable). Jinguo(ZTE) provides r07 in draft folder Dieter (Deutsche Telekom) support removing WT7. Patrice (Huawei) thanks Jinguo (ZTE) for r07, is OK with r07, and would like to add Huawei and HiSilicon to this version. Peter Hedman (Ericsson) Support r05 and objects to r07, r06 and any revision with objective 5 restricted to NSAC Patrice (Huawei) (for the records) objects to all versions except r07. Guillaume (MediaTek) responds to Myungjune (LGE) Jinguo (ZTE) provides r08 and clarifies that solutions for obj5 may also be workable for other scenarios. Patrice (Huawei) cannot accept r08, as we don't know what we are going to study now in obj5. Dieter (Deutsche Telekom) supports removing WT5. ==== Comments Deadline ==== Alessio(Nokia) Support r05 but cannot live with an objective that is just NSAC oriented as the operator wants to control the UE behaviour irrespective of that (i.e. also in networks without NSAC). Gerry Libunao (Verizon) supports r05 and objects to r07, r06 and any revision with objective 5 restricted to NSAC. Jinguo(ZTE) propose a way forward on obj 5 alessio(Nokia) comments that bj5 should be reinstated like it was in the MED. it is not possible to keep churning things like it has been done. it was very clear the goal was controlling the UE behaviour in registration and PDU session establishment. this received wide support. we can now check who object on the call and who supports that one... Peter Hedman (Ericsson) provides comments and proposal for objective 5 Jarmo (KPN) would like to support the study. | Revised | |
| 9.1.3 | S2-2109356 | SID NEW | Approval | Study on Enhancement of Network Slicing Phase 3 . | ZTE, LG Electronics, Samsung, Alibaba, Apple, AT&T, CATT, China Telecom, China Unicom, Convida Wireless LLC, Ericsson, Intel, InterDigital, KDDI, Lenovo, Matrixx, MITRE, Motorola Mobility, NEC , Nokia, Nokia Shanghai Bell , NTT Docomo, OPPO, Oracle, Orange, Qualcomm, Sanechips, Sharp, T-Mobile USA, Spreadtrum, Tencent, Verizon UK Ltd, Xiaomi | - | Revision of S2-2108609r13. CC#3: Technically Endorsed with an objection from Huawei. | Endorsed | |
| 9.1.3 | S2-2108611 | REPORT | Information | Summary of Email discussion on FS_eNS_Ph3 | ZTE(rapporteur) | Noted | Noted | ||
| 9.1.3 | S2-2108619 | DISCUSSION | Endorsement | Motivation of supporting UPF on-board | CATT | Rel-18 | Noted | Hannu (Nokia) proposes to note the discussion paper and comments on the contents. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108658 | DISCUSSION | Information | E-mail discussion on Personal IoT Network (PIN). | Zhenhua Xie / vivo | Noted | Laurent (Nokia): proposes to Note this discussion paper (objects to any of version of this Tdoc) and to concentrate on the SID discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 9.1.3 | S2-2108659 | DISCUSSION | Information | Updated discussion on SID of Personal IoT Network architecture | vivo | Noted | Laurent (Nokia): proposes to Note this discussion paper (objects to any of version of this Tdoc) and to concentrate on the SID discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted | |
| 9.1.3 | S2-2108660 | SID NEW | Approval | New SID on Personal IoT Network architecture. | Vivo Mobile Communications Ltd, CATT, China Telecom, Convida Wireless, InterDigital, KPN, OPPO, Philips, Spreadtrum Communications, T-Mobile USA, Tencent | CC#3: r14 agreed. Revised to S2-2109357. | Antoine (Orange) comments on WT#2. Zhenhua (vivo) responds to Antoine (Orange) and provides r01. Laurent (Nokia): Comments and suggests some changes Sherry (Xiaomi) Comments. Stefan (Ericsson) comments Guliang (Inspur) support this SID and would like to co-source the SID. Laurent (Nokia): suggests a revision with only WT1, WT2, and WT3 and Neither WT4 nor WT5 (as in the S2-2108660-SID-PIN - Nokia version put in /drafts) Zhenhua (vivo) provides r02 Zhenhua (vivo) asks Laurent (Nokia) whether r02 is OK, which removed WT5 Antoine (Orange) requests further edition of WT#2.1. Amanda ( Futurewei ): provide r03 to add identifying PIN in WT#1.2 and WT#2.1 Zhenhua (vivo) provide r04 Zhenhua (vivo) provides r05 to add more supporter and co-source. Zhenhua (vivo) provides r06 Zhenhua (vivo) provides r07 to correct the dependency in TU estimates. Walter Dees (Philips) does not agree with the sentence that no changes to ProSe and non-3GPP access can be assumed, and proposes revision r08. Laurent (Nokia): Zhenhua do you endorse this r08? asks also a question to Walter Walter (Philips) apologizes for sending the revision r08 instead of a company revision Hualin(Huawei) disagree with Walter (Philips)'s comments. Zhenhua (vivo): Clarified r08 is not provided by rapporteur, and responds. Sherry(Xiaomi) comments. ==== Revisions Deadline ==== Walter (Philips) responds to Hualin (Huawei) and Sherry(Xiaomi). Zhenhua (vivo) provides r09 in draft folder based on r07 to only add new supporter and co-source company. Laurent (Nokia): Comments: What is problematic is NOTE 1 Zhenhua (vivo) replies to Laurent (Nokia) Walter Dees (Philips) cannot agree with revisions r02, r03, r04, r05, r06, r07 and r09 if the last sentence in the second to last NOTE is not removed or updated. Propose to discuss in CC#3 unless some agreement can be reached beforehand. Zhenhua (vivo) thanks Walter (Philips) to provides suggestion on the NOTE modification. Hualin(Huawei) can't agree the revised NOTE. Laurent (Nokia): objects to any version between R00 and R05 both included. Can live with R06/R07 but wants first Note 1 to be clean and then to have a look at the TU numbers that heavily depend on Note 1. If ProSe WT about non 3GPP support is agreed, reusing ProSe solution is Mandatory Hong (Qualcomm) comments. Hualin(Huawei) support the way proposed by Nokia Sherry(Xiaomi) supports the way forward proposed by Laurent. ==== Comments Deadline ==== Zhenhua (vivo) provides a wording proposal for the NOTE. Zhenhua (vivo) provides r10 in CC#2 folder. Hong (Qualcomm) propose some new wording for the NOTE. Zhenhua (vivo) provides r11 in CC#2 folder to adopt wording to the NOTE proposed by Hong (Qualcomm). Walter Dees (Philips) proposes a change to the wording of the NOTE. Sherry (Xiaomi) is fine with Hong's wording and Walter's proposal to the NOTE. Zhenhua (vivo) provides r12 in CC#3 folder. Zhenhua (vivo) provides r13 in CC#3 folder | Revised | |
| 9.1.3 | S2-2109357 | SID NEW | Approval | New SID on Personal IoT Network architecture. | Vivo Mobile Communications Co. Ltd, CATT, China Mobile, China Telecom, Convida Wireless, InterDigital, KPN, OPPO, Philips, Spreadtrum Communications, T-Mobile USA, Tencent, Futurewei, Xiaomi, Inspur, Guangdong Genius, Apple | - | Revision of S2-2108660r14. Approved | Approved | |
| 9.1.3 | S2-2108661 | DISCUSSION | Information | Updated discussion on SID of UE Aggregation for Industry with Multi-connectivity | vivo | Noted | Noted | ||
| 9.1.3 | S2-2108662 | SID NEW | Approval | New SID on UE Aggregation for Industry with Multi-connectivity. | Vivo Mobile Communications Ltd, China Telecom, China Unicom, CATT, Spreadtrum Communications | CC#3: Noted | LaeYoung (LGE) asks a Q for clarification. Qian (LGE) provides comments. LaeYoung (LGE) just wants to clarify that Qian is not from LGE but from Ericsson. ^__^ Qian (Ericsson) re-sends the mail to indication the source company is 'Ericsson' (Copy/Paste mistake). Haris(Qualcomm) proposes revision in DRAFTS folder Saso (Intel) seeks clarification. Saso (Intel) provides additional comment. Antoine (Orange) comments. Devaki (Nokia) provides _revNokia (on top of _revQC). Devaki requests to ignore r01 as it was provided by mistake. We are also supportive of 5GC based solution to be studied (without impacting RAN for UE aggr) in Rel-18. Fei (OPPO) comments. Zhenhua (vivo) responds Zhenhua (vivo) responds to Qian (Ericsson). Dieter (Deutsche Telekom) has strong concerns with the proposal. Marco (Huawei) objects to the new WT addition. Haris(Qualcomm) asks question to Marco (Huawei) Zhenhua (vivo) provides r02 Qian (Ericsson) comments and expresses concerns Guillaume (MediaTek Inc.) comments Marco (Huawei) replies to Haris (Qualcomm) Haris(Qualcomm) comments Saso (Intel) objects to this SID. Jinsook (DISH Network) comments Marco (Huawei) comments Zhenhua (vivo) provides r03 Zhenhua (vivo) replies ==== Revisions Deadline ==== Jinsook (DISH Network) as a clarification Saso (Intel) replies. Devaki (Nokia) objects to all the SID versions (as long as RAN impact is ticked). As commented earlier, we are ok with studying system solutions for the objectives proposed but not ok with RAN impact. Zhenhua (vivo) replies to Jinsook (DISH Network) Zhenhua (vivo) replies to Saso (Intel). LaeYoung (LGE) proposes to NOTE this SID and objects to all versions. Dieter (Deutsche Telekom) objects to this SID as per previous comments. Marco (Huawei) objects to r02 and r03 as per previous comments. Saso (Intel) replies to Zhenhua (vivo). Haris(Qualcomm) objects to r03 Antoine (Orange) objects to r02. ==== Comments Deadline ==== Devaki (Nokia) can also accept r02 (removing RAN impact or at least marking it as don't know). | Noted | |
| 9.1.3 | S2-2108671 | SID NEW | Approval | New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2. | Huawei, HiSilicon | Rel-18 | Revision of (Postponed) S2-2107550 from S2#147E. CC#3: r10 agreed. Revised to S2-2109362. | Antoine (Orange) objects to WT 1.3. Dieter (Deutsche Telekom) objects to WT1.3. Robbie (Ericsson) provides r00-Ericsson in DRAFTS folder. Miguel (Qualcomm) objects to WT 1.3, still has concerns with WT 1.2. Thomas (Nokia) comments against changes suggested by Robbie. Thomas (Nokia) points to requirements for WT 1.2 and WT 1.3 in TS 22.101 Miguel (Qualcomm) responds to Thomas, the referenced requirements do not apply Dieter (Deutsche Telekom) answers to Thomas. LiMeng (Huawei) answers and clarifies. LaeYoung (LGE) provides comment while pointing out that LiMeng (Huawei) provided r01 previously. Robbie (Ericsson) disagree with Thomas (Nokia) and also asks whether 8:5 is a clear majority. Zhenhua (vivo) questions on TU of WT2, and suggest to split WT4. Robbie (Ericsson) provides r01-Ericsson in DRAFTS folder, reinstate WT#4.3 which is important for public safety use cases, and asks why this valid requirement is removed Zhuoyi (China Telecom) supports the SID and would like to co-source it. Kaixin (CBN) answers to Antoine and Dieter. LaeYoung (LGE) asks a Q to Kaixin (CBN). Sherry (Xiaomi) provides a revision on top of r01-Ericsson in DRAFTS folder Kaixin (CBN) answers to LaeYoung. Dieter (Deutsche Telekom) answers Kaixin(CBN). Wanqiang (Huawei) comments. LaeYoung (LGE) thanks to Kaixin (CBN). Relja (TNO) supports this SID and would like to be added to the list of supporting companies. Some comments are also provided. LiMeng (Huawei) thanks for sharing the views and provides r02 and r03. ==== Revisions Deadline ==== Robbie (Ericsson) reiterates that WT#4.3 is important for public safety, which is also shown in MED. As such, propose to be included in the SID. Miguel (Qualcomm) objects to r02 and any revision with WT 1.3. Thomas(Nokia) supports r02. Relja(TNO) supports r02. Robbie (Ericsson) provides r02-Ericsson and r03-Ericsson in DRAFTS folder, reinstate WT#4.3 on top of r02 and r03 provided by Rapporteur. We believe this WT is important for scalability of MBS and building more complex features on top of Rel-17 architecture. Antoine (Orange) objects r00, r01 and r02. Ihab (FirstNet) We support Ericsson and we would like to see WT#4.3 in the scope of the WID since it is important for public safety. Miguel (Qualcomm) objects to r03, due to the addition of this statement in Justification 'In addition, the FTA-type data reception (i.e., broadcast reception by devices with no subscription or with 3rd party content provider subscription only) for NR can be supported in Rel-17 by configuring reception information at UE side.' We can accept r03 if that sentence is removed. James (AT&T) supports Ericsson and FirstNet to include WT#4.3 in the scope of the WID since it is important for public safety. Thomas(Nokia) has concerns about extra objective suggested by Robbie. Reminds Robbie of the results of moderated email discussion and that we are already above the time budget, LiMeng (Huawei) provides r04 with removing the sentence highlighted by Miguel, and asks to check r02 and r04 in CC#2. Robbie (Ericsson) objects to all revisions without WT#4.3. Dieter (Deutsche Telekom) we also insist on removing the sentence highlighted by Miguel. Zhendong (ZTE): r02 is better ==== Comments Deadline ==== | Revised |
| 9.1.3 | S2-2109362 | SID NEW | Approval | New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2. | Huawei, HiSilicon | Rel-18 | Revision of S2-2108671r10. Approved | Approved | |
| 9.1.3 | S2-2108692 | DISCUSSION | Information | Discussion about Uu based sensing | vivo | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108760 | SID NEW | Approval | Study on Passive Internet of Things (Passive IoT) for 5G Advanced . | China Mobile, Spreadtrum Communications, Huawei, HiSilicon, China Telecom, China Unicom, CATT, Tencent, vivo, Quanray, NTT DOCOMO, Vodafone, Alibaba, CAICT | Rel-18 | Noted | Chunhui (Spreadtrum) provides the revision(r01) with 2 additional supporting companies. Hannu (Nokia) comments that since the corresponding SA1 SID is not approved and it's targeting Rel-19, it is not possible to plan the SA2 work in Rel-18. LaeYoung (LGE) proposes to NOTE this SID because she believes that use cases, scenarios, service requirements and performance requirements need to be identified in SA1 first. This will be able to put the studies in downstream groups in the right direction. Leo (Deutsche Telekom) objects this SID for SA2 in Rel-18. Hannu (Nokia) supports the proposal to note this SID in Rel-18 due to lack of service requirements. Saad (Interdigital) proposes to note this SID. Miguel (Qualcomm) proposes to NOTE this SID proposal, in favor of a proper study in SA1 Guillaume (MediaTek Inc.) provides comments. Chunhui(Spreadtrum) replies Guillaume (MediaTek Inc.)'s comments. Chunhui(Spreadtrum) replies LaeYoung (LGE)'s comments. LaeYoung (LGE) does not get the answer from Chunhui (Spreadtrum). Chunhui (Spreadtrum) answers LaeYoung (LGE). LaeYoung (LGE) responds to Chunhui (Spreadtrum). Guillaume (MediaTek Inc.) responds. Chunhui(Spreadtrum) responds to Guillaume (MediaTek Inc.). ==== Revisions Deadline ==== Miguel (Qualcomm) objects to this SID in all revisions. ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108766 | SID NEW | Approval | New SID: Study on Seamless UE context recovery. | Samsung, NEC, CableLabs, Cisco, InterDigital Inc. | Rel-18 | Revision of (Postponed) S2-2107383 from S2#147E. r01 agreed. Revised to S2-2109324. | Haris(Qualcomm) comments Laurent (Nokia): Comments Lalith(Samsung) agrees with Haris and Laurent and provides r01 ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.1.3 | S2-2109324 | SID NEW | Approval | New SID: Study on Seamless UE context recovery. | Samsung, NEC, CableLabs, Cisco, InterDigital Inc. | Rel-18 | Revision of S2-2108766r01. Approved | Approved | |
| 9.1.3 | S2-2108768 | OTHER | Information | Email discussion on Passive IoT SID. | China Mobile, Spreadtrum Communications | Rel-18 | Noted | Hannu (Nokia) comments that the proposed way forward is not acceptable as it does not reflect the outcome of the moderated email discussion. Miguel (Qualcomm) fully agrees with Hannu (Nokia) that the moderator proposed way forward does not reflect the company positions expressed in the MED, and cannot accept proposed way froward. Guillaume (MediaTek Inc.) proposes to just note this document and not to endorse the WF proposals ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108769 | SID NEW | Approval | New SID on 5G Architecture enhancements for Harmonized Communication and Sensing service. | Huawei, HiSilicon, vivo, CAICT, China Unicom, China Mobile, China Telecom, CATT, ZTE, OPPO, ROBERT BOSCH GmbH, NTT DOCOMO, TCL, Philips, Xiaomi, Lenovo, China Security and Protection Industry Association | Rel-18 | Revision of (Postponed) S2-2107636 from S2#147E. Noted | Antoine (Orange) asks clarification about RAN impacts. Wanqiang (Huawei) feedback and clarify the way how to decouple from the RAN1/2 work. Leo (Deutsche Telekom) objects to all versions/revisions of the SID. LaeYoung (LGE) proposes to NOTE this SID because she believes that use cases, scenarios, service requirements and performance requirements need to be identified in SA1 first. This will be able to put the studies in downstream groups in the right direction. Hong (Qualcomm) comments about the RAN dependency. Shabnam (Ericsson) sharing same concerns as given before, as well we do not see what only CN based sensing architecture study would benefit without actual service requirements. As such, objects to the study proposal in Rel-18. Guillaume (MediaTek Inc.) comments Saso (Intel) maintains the same position of previous meeting and proposes to note this SID. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108770 | DISCUSSION | Information | Moderated email discussion summary on FS_HCS. | Huawei (moderator) | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108771 | DISCUSSION | Discussion | Harmonized Communication and Sensing service (HCS) | Huawei, Hisilicon, vivo, CAICT, China Unicom, China Mobile, China Telecom, ZTE, CATT, China Security and Protection Industry Association | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108773 | SID NEW | Approval | New SID about AF control of 5GC groups. | Nokia, Nokia Shanghai Bell | Rel-18 | CC#3: This was noted. | Sang-Jun (Samsung) proposes that 8773 should be merged to 8574. The objectives of 8574 seem to include those of 8773. Rainer (Nokia) replies to Sang-Jun (Samsung). Sang-Jun (Samsung) asks Rainer (Nokia) a question. Sebastian (Qualcomm) asks a question Rainer (Nokia) replies. Qianghua (Huawei) prefers one SID for group management and group communication ==== Revisions Deadline ==== Sebastian (Qualcomm) objects to the SID; would be ok if WT4 was removed ==== Comments Deadline ==== Susana (Vodafone) supports this SID and comments Sebastian (Qualcomm) replies to Rainer and provides r01 in drafts folder Rainer (Nokia) replies and provides r01 to CC#3 folder. | Noted |
| 9.1.3 | S2-2108774 | SID NEW | Approval | New SID on 5G support for Femto. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Hualin(Huawei) still have strong concerns as in last meeting, since there is RAN work on this so far. So, we propose to note this SID. Rainer (Nokia) replies. Stefan (Ericsson) has same concerns as Hualin (Huawei) Dieter (Deutsche Telekom) has also concerns with the proposal ==== Revisions Deadline ==== Stefan (Ericsson) objects to this SID ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108779 | DISCUSSION | Discussion | Sensing capability for support of Low-Altitude intelligent network in UAV industry | CSPIA (China Security and Protection Industry Association) | Rel-18 | WITHDRAWN | Withdrawn | |
| 9.1.3 | S2-2108855 | SID NEW | Approval | New SID: new Study on the support for 5WWC, Phase 2. | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Deutsche Telekom, Broadcom, Lenovo, Motorola Mobility, Qualcomm, KPN, China Telecom, CableLabs | CC#3: r09 agreed. Revised to S2-2109363. | Laurent (Nokia): Comments Laurent (Nokia): Comments and provides r01 Marco (Huawei): provided Huawei's position on WTs in draft folder. Huawei proposals for revision of 5WWC SID are included in S2-2108936. Stefan (Ericsson) provided 5WWC poll paper in DRAFTS folder Farooq (AT&T) provides 5WWC poll paper in DRAFTS folder (adds to E/// input) Myungjune (LGE) comments on WT 3a Laurent (Nokia): answers Sebastian (Qualcomm) provides Qualcomm comments for 5WWC poll paper Marco (Huawei) proposes to prepare a revision with only non controversial objectives as minimum basis Curt (Charter) provides comments for 5WWC poll paper Myungjune (LGE) provides comments for 5WWC poll paper Dieter (Deutsche Telekom) provides comments for 5WWC poll paper. Laurent (Nokia): provides the result of the polling about 5WWC Laurent (Nokia): provides the result of the polling about 5WWC with a summary for each WT, provides R02 and r03 (fairly minimalistic) Dieter (Deutsche Telekom) comments on WT2 d) Support of emergency calls, for UE(s) connected behind the 5G RG. Saso (Intel) comments on WT#2a and WT#2b. Proposes to remove them. Hualin(Huawei) object r02 and r03. We propose to remove objective 2d and 2e based on r02 as further revision r04. Laurent (Nokia): asks Hualin whether he is sure to object to r03, this is about emergency calls Tyler (OTD) comments on WT#2b, supports keeping it. Laurent (Nokia): provides r04 that should replace r03 (corrects a bug in TU calculation) Saso (Intel) replies. Laurent (Nokia): provides r05 Marco (Huawei) comments WT2a Hualin(Huawei) answers Hualin(Huawei) suggest to remove emergency calls. But not very insistent. Hualin (Huawei) comments on r05. Laurent (Nokia): provides r06 Laurent (Nokia): provides r07 Laurent (Nokia): provides r08 ==== Revisions Deadline ==== Curt (Charter) comments on WT selection process Laurent (Nokia): with BBF and CL we have worked via LS in the past and need to go on that way Laurent (Nokia): answers: WT07/WT08 had a an overwhelming majority of concerns 8 against 1 support Curt (Charter): Charter can only support R02 or any version post and including R04 that is updated to also contain WT2e and WT2f. Sebastian (Qualcomm) objects to r00 to r02; is ok with other versions; flexible on WT2e and WT2f Laurent (Nokia): is happy to support R04, R06 or R07 with WT2e, WT2f (added back to any of R04, R06 or R07). Suggest that we consider discussing R07 with WT2e, WT2f being readded during the CC2 Marco (Huawei) can only support r03,04,05,06 that are updated also containing WT3d (No r00, r01, r02, r07, r08) Dieter (Deutsche Telekom) can only support r04, 06 with or without adding WT4b, but not more. Objects to all other versions. . Stefan (Ericsson) can only support r04, r06 as is. (R03, R05 in principle OK but they have same objectives as r04, r06 respectively). Objects to other versions. Sriram (CableLabs): is happy to support R04 with WT2e, WT2f added back. marco (Huawei): if further discussion in CC2, also Wt3d Laurent (Nokia): is happy to support R04, R06 or R07 with WT2e, WT2f (added back to any of R04, R06 or R07). Suggest that during the CC2 we consider discussing R06 with (WT2e + WT2f +W3d) being readded and the package being agreed! ==== Comments Deadline ==== Aditya (Comcast): Comcast shares the views expressed by Charter and Nokia. We will support R02 or any version post Laurent (Nokia): I have put a .pptx for the SoH in Inbox/CC/CC2 | Revised | |
| 9.1.3 | S2-2109363 | SID NEW | Approval | New SID: new Study on the support for 5WWC, Phase 2. | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Deutsche Telekom, Broadcom, Lenovo, Motorola Mobility, Qualcomm, KPN, China Telecom, CableLabs, Charter, Apple | - | Revision of S2-2108855r09. Approved | Approved | |
| 9.1.3 | S2-2108868 | SID NEW | Approval | New SID on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. | Lenovo, Motorola Mobility, ZTE, Broadcom, Apple, Alibaba, Tencent, China Mobile, Convida Wireless, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Samsung, Interdigital, Matrixx, Cisco Systems, Charter Communications, CableLabs, Comcast, CATT, Intelsat, Viv | Rel-18 | Revision of (Postponed) S2-2107635 from S2#147E. CC#3: r03 endorsed. Revised to S2-2109358. | Marco (Huawei) per techical comments in S2-2108920, we confirm objection to WT5.2. Marco (Huawei) comment and proposed revision of WT5.1 in folder INBOX/DRAFTS/ ATSSS_ph3_discussion. Tricci (OPPO) shares the same concern with Marco (Huawei) for objective 5.2 and has further questions on other objectives. Dieter (Deutsche Telekom) maintains objection from last meeting to WT5.2. Huan (vivo) shares the same concern with previous comments to WT5.2. Rainer (Nokia) replies. Apostolis (Lenovo) responds to Tricci (OPPO). Dario (Qualcomm) replies Marco (Huawei) comments to Dario (Qualcomm) Marco (Huawei) point out that revision of WT5.1 as in folder INBOX/DRAFTS/ ATSSS_ph3_discussion are essential to make WT 5.1 acceptable. Marco (Huawei) asks clarification on WT 5.3 Apostolis (Lenovo) confirms that the changes to WT5.1 requested by Marco (Huawei) will be implemented in r01. Dieter (Deutsche Telekom) answers to Dario . Omkar (CableLabs) agrees with Qualcomm's view and indicates support for WT#5.2. Stefan (Ericsson) expresses concerns with WT#5.2 Farooq (AT&T) also expresses concern on WT5.2. Apostolis (Lenovo) provides r01 Apostolis (Lenovo) responds to Marco (Huawei) on WT5.3. Marco (Huawei) proposes revision of WT5. Marco (Huawei) proposes a revision of WT5 (to himself). Apostolis (Lenovo) comments on WT#5.2. Dario (Qualcomm) replies to Apostolis Apostolis (Lenovo) provides r02. Marco (Huawei) comments and confirm concern on 5.2 Farooq (AT&T) asks question for clarification ==== Revisions Deadline ==== Farooq (AT&T) suggests adding a Note to the objectives Apostolis (Lenovo) responds to Farooq (AT&T). Farooq (AT&T)responds to Apostolis (Lenovo) Omkar (CableLabs) responds on removal of WT#5.2 Apostolis (Lenovo) comments that the Note suggested by Farooq (AT&T) is only needed if we keep WT#5.2. Marco (Huawei) objects R00, R01. OK with r02 with comment for clarification DongYeon (Samsung) supports keeping WT#5.2. Rainer (Nokia) supports also keeping WT5.2 Spencer (Tencent) also supports keeping WT5.2. Apostolis (Lenovo) supports keeping WT5.2 with a clarification Note. Rainer (Nokia) is ok with the Note. Stefan (Ericsson) objects to r00, r01. OK with r02. Dieter (Deutsche Telekom) objects to r00, r01. OK with r02. Tyler (OTD) supports r02. Dario (Qualcomm) is OK with r00, r01 (also with NOTE by Farooq) and objects to r02 Omkar (CableLabs) is OK with r00, r01 and objects to r02 ==== Comments Deadline ==== Spencer (Tencent) agrees with Dario (Qualcomm). Tricci (OPPO) supports ONLY r02 with the NOTE (see below) suggested by Farooq. | Revised |
| 9.1.3 | S2-2109358 | SID NEW | Approval | New SID on Access Traffic Steering, Switching and Splitting support in the 5G system architecture; Phase 3. | Lenovo, Motorola Mobility, ZTE, Broadcom, Apple, Alibaba, Tencent, China Mobile, Convida Wireless, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Samsung, Interdigital, MATRIXX Software, Cisco Systems, Charter Communications, CableLabs, Comcast, CATT, Intelsat, Vivo, BT, Thales, HPE, Tessares, Telefonica, KPN, Orange, MediaTek Inc., Rogers Communications Canada, Huawei, Xiaomi, Bouygues Telecom, US Cellular, ETRI | Rel-18 | Revision of S2-2108868r03. CC#3: Technically Endorsed with an objection from Qualcomm | Endorsed | |
| 9.1.3 | S2-2108896 | SID NEW | Approval | New SID on Study on Architecture Enhancements for Vehicle Mounted Relays . | Qualcomm Incorporated, Sony, InterDigital Inc. AT&T, Verizon UK Ltd, ZTE Corporation, Telstra, vivo Mobile Communications Ltd, Volkswagen AG, Philips International B.V., Xiaomi, SyncTechno Inc., FirstNet, Lenovo/Motorola Mobility, LG Electronics, Rakuten | Rel-18 | Revision of (Postponed) S2-2107310 from S2#147E. r03 agreed. Revised to S2-2109325. | Laurent (Nokia): Comments Lars (Sony) asks Laurent (Nokia) Laurent (Nokia): answers Hong (Qualcomm) provides r01. Wanqiang (Huawei): Comments on the new added 'NOTE 1: The study aims to avoid introducing new RAN architectures.' Hong (Qualcomm) provides r02. Wanqiang (Huawei) feedback the update does not work. Hong (Qualcomm) replies to Wanqiang. Wanqiang (Huawei) replies to Hong. Hong (Qualcomm) provide r03 and r04. Sherry (Xiaomi) comments. Hong (Qualcomm) provides r05 (based on r03) and r06 (based on r04). Shabnam (Ericsson) proposes to continue on r05 path. Wanqiang (Huawei) comments on r05. Laurent (Nokia): we have reservation/concern on the approach in R04 and R06 Relja (TNO) would like to be added to the list of supporting companies. TNO finds r05 as a good basis. Relja responds to Wanqiang (Huawei) and pose a question to Hong(Qualcomm). ==== Revisions Deadline ==== Hong (Qualcomm) replies to Relja. Laurent (Nokia): objects to R00, R01,R02, R04, R06 Hong (Qualcomm) replies to Laurent. Wanqiang (Huawei) proposes to go with r03. Laurent (Nokia): answers to Hong Hong (Qualcomm) replies and fine with either r03 or r05 route. Lars (Sony) fine with r03. Sherry (Xiaomi) is fine with either r03 or r05. LaeYoung (LGE) is fine with r03. Relja (TNO) is fine with both r03 and r05. Jean Yves (Thales) is fine also with either r03 or r05. ==== Comments Deadline ==== | Revised |
| 9.1.3 | S2-2109325 | SID NEW | Approval | New SID on Study on Architecture Enhancements for Vehicle Mounted Relays . | Qualcomm Incorporated, Sony, InterDigital Inc. AT&T, Verizon UK Ltd, ZTE Corporation, Telstra, vivo Mobile Communications Ltd, Volkswagen AG, Philips International B.V., Xiaomi, SyncTechno Inc., FirstNet, Lenovo/Motorola Mobility, LG Electronics, Rakuten Mobile Inc., Thales, TNO, Apple | Rel-18 | Revision of S2-2108896r03. Approved | Approved | |
| 9.1.3 | S2-2108904 | SID REVISED | Approval | New SID: Study on system architecture for next generation real time communication services. | China Mobile, China Unicom, Huawei, Hisilicon, ZTE, CATT, Vivo, Deutsche Telekom, T-Mobile USA, Ericsson, AT&T | Rel-18 | Revision of (Approved) S2-2108165 from S2#147E. Approved | Mario (TI) Telecom Italia supports this study. ==== Comments Deadline ==== Jarmo (KPN) also supports this study. Susana (Vodafone) supports the study. | Approved |
| 9.1.3 | S2-2108915 | REPORT | Information | Moderated Email Discussion summary for FS_VMR_ARC | Qualcomm Incorporated | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108920 | DISCUSSION | Approval | Consideration on ATSSS WT #5 objectives. | Huawei, HiSilicon | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108936 | DISCUSSION | Approval | Considerations on 5WWC SID objectives. | Huawei, HiSilicon | Rel-18 | Noted | Laurent (Nokia): proposes to Note this discussion paper (objects to any of version of this Tdoc) and to concentrate on the SID discussion Marco (Huawei): This paper provides the motivations for all Huawei's comments to the 5WWC SID, hence this information will be used directly in SID email discussion ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108938 | SID NEW | Approval | New Study on Service-based N2. | Intel, Qualcomm Incorporated, Deutsche Telekom, Verizon UK Ltd., AT&T, Microsoft, Orange, Cisco, InterDigital, Broadcom | Rel-18 | Revision of (Postponed) S2-2107100 from S2#147E. Noted | Laurent (Nokia): Objects to this Tdoc and any of its revisions Shabnam (Ericsson) objects to this SI, already stated reasons during SA2#147E and additional NOTE adds more confusion and concern as it seems the study extends on discussing AN/CN functional split. Wanqiang (Huawei) maintains the same position of previous meeting and proposes to note this SID. Jicheol (Samsung) share the same view with Nokia, Ericsson and Huawei. Jinguo(ZTE) shares the same view with Nokia, Ericsson, Huawei, and Samsung. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108960 | DISCUSSION | Endorsement | FS_ATSSS_Ph3: Dual 3GPP access for PLMN + SNPN and PLMN + PLMN | Qualcomm Incorporated | Rel-18 | Noted | Marco (Huawei) propose to note the DP ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.3 | S2-2108973 | SID NEW | Approval | New SID: PWS over non-3GPP access. | Apple, Verizon UK Ltd, Broadcom, Convida Wireless | Rel-18 | Revision of (Postponed) S2-2107773 from S2#147E. CC#3: Noted | Haris(Qualcomm) objects to this SID since there are no regulatory and SA1 requirements Krisztian (Apple) has a concern regarding Qualcomm's objection as it is not based on technical ground. There's at least one operator (Verizon) interested to study PWS over WLAN as a service improvement without regulatory mandate. The increased probability of successful warning message delivery (e.g. in indoor environment) is a clear improvement to PWS service resulting in better user experience. In addition, it's unclear what kind of new SA1 service requirements are necessary to make PWS service available over non-3GPP access. We think there are architectural and protocol impacts but PWS service experience remains the same for the user. Hence, we still think the work can start from SA2. ==== Revisions Deadline ==== Haris(Qualcomm) comments that the objection is absolutely based on technical grounds since there are no regulatory and service requirements for SA2 to accomplish Krisztian (Apple) responds: as commented before, TS 22.268 states that PWS, ETWS and CMAS deployment depends on operator decision or national regulations. National regulations are not the only driving force to improve the service, it is up to operator decision. There's operator interest to deploy PWS service improvement. Furthermore, PWS requirements in TS 22.268 are not dependent on access technology. We are proposing to re-create the same service experience on non-3GPP access that is already available on 3GPP access using the existing PWS service requirements present in TS 22.268. Hence, the objection by Qualcomm has no ground. Dieter (Deutsche Telekom) propose to note the SID as PWS is not in SA2 responsibility. ==== Comments Deadline ==== Krisztian (Apple) asks to make a decision at CC#2 regarding this proposal. CT1 owns Stage-2 Cell Broadcast Service (CBS) for 3GPP access, TS 23.041 is called 'Technical realization of Cell Broadcast Service (CBS)'. The proposal here is PWS over non-3GPP access that can't be based on CBS. SA2 is the group to tackle new work with architectural impacts. Offloading work to CT1 is of course a possible way forward but that's for SA to decide during prioritization. Krisztian (Apple) asks to make a decision at CC#2 regarding this proposal. CT1 owns Stage-2 Cell Broadcast Service (CBS) for 3GPP access, TS 23.041 is called 'Technical realization of Cell Broadcast Service (CBS)'. The proposal here is PWS over non-3GPP access that can't be based on CBS. SA2 is the group to tackle new work with architectural impacts. Offloading work to CT1 is of course a possible way forward but that's for SA to decide during prioritization. Krisztian (Apple) asks to make a decision at CC#2 regarding this proposal. CT1 owns Stage-2 Cell Broadcast Service (CBS) for 3GPP access, TS 23.041 is called 'Technical realization of Cell Broadcast Service (CBS)'. The proposal here is PWS over non-3GPP access that can't be based on CBS. SA2 is the group to tackle new work with architectural impacts. Offloading work to CT1 is of course a possible way forward but that's for SA to decide during prioritization. | Noted |
| 9.1.3 | S2-2108982 | DISCUSSION | Discussion | Sensing capability for support of Low-Altitude intelligent network in UAV industry. | CSPIA (China Security & Protection Industry Association) | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108987 | DISCUSSION | Discussion | DISC On AMF relocation in connected mode. | NEC, | Rel-18 | Noted | Noted | |
| 9.1.3 | S2-2108989 | REPORT | Information | Moderated email discussion summary on FS_INCP | China Telecom (moderator) | Noted | Noted | ||
| 9.1.3 | S2-2108990 | REPORT | Information | Moderated Email Discussion summary for FS_ESSIND | China Telecom | Noted | Noted | ||
| 9.1.4 | - | - | - | Revision of Rel-18 SID/WID proposal TECHNCIALLY ENDORSED at SA2#147E | - | - | Docs:=7 | - | |
| 9.1.4 | S2-2108433 | SID NEW | Approval | New SID on Enhancement to the 5GC LoCation Services Phase 3. | CATT, Huawei | Rel-18 | Revision of (Endorsed) S2-2108170 from S2#147E. r02 agreed. Revised to S2-2109326. | Ming (CATT) provides r01. Ming (CATT) provides r02, with one more supporting company, two WT merge and better WT#7 wording. Jingran (OPPO) provides comments on some WTs. Ming(CATT) reply to Jingran (OPPO). Relja(TNO) would like to be added to the list of supporting companies. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.1.4 | S2-2109326 | SID NEW | Approval | New SID on Enhancement to the 5GC LoCation Services Phase 3. | CATT, Huawei | Rel-18 | Revision of S2-2108433r02. Approved | Approved | |
| 9.1.4 | S2-2108474 | SID NEW | Approval | New SID on Study on 5G Timing Resiliency and TSC enhancements . | Nokia, Nokia Shanghai Bell, Verizon, AT&T, Sennheiser, Huawei, HiSilicon, Matrixx, ZTE, China Unicom, Vivo, NTT Docomo, ETRI, Xiaomi, Orange, China Mobile, KDDI, Tencent, T-Mobile USA, Interdigital, Samsung, CATT, Deutsche Telekom, Ericsson, Denso, BMWi, | Rel-18 | Approved | Susan (Huawei) provides a revision. Sebastian (Qualcomm) raises concerns for the draft revision provided by Huawei György (Ericsson) comments. Devaki (Nokia) comments. Susan (Huawei) replies to Sebastian (Qualcomm). Susan (Huawei) replies to György (Ericsson). Devaki (Nokia) provides r01. Susan (Huawei) replies to Devaki (Nokia). Susan (Huawei) is ok with r01. ==== Revisions Deadline ==== György (Ericsson) replies to Huawei. György (Ericsson) objects to r01, proposes to go with original version. Devaki (Nokia) asks if we can go with the original version r00? Susan (Huawei) replies to Devaki (Nokia) and accept to move with the original version r00. Devaki (Nokia) thanks Susan (Huawei) for the understanding and accepting r0. ==== Comments Deadline ==== | Approved |
| 9.1.4 | S2-2108525 | SID NEW | Approval | New WID on Study on System enhancement for Proximity based Services in 5GS - Phase 2 . | CATT, OPPO | Rel-18 | Revision of (Endorsed) S2-2108162 from S2#147E. CC#3: r06 endorsed. Revised to S2-2109359. | Judy (Ericsson) comments Fei (OPPO) responds to Judy (Ericsson) Judy (Ericsson) responds to Fei (OPPO) Hannu (Nokia) supports Judy's comment on WT#2 TUs and provides a draft revision. Steve (Huawei) comments Mehrdad (Samsung) does not agree with the view shared on removing WT#4 and WT#9. Hong (Qualcomm) comments and share the view of Samsung. Ihab (FirstNet) FistNet does not agree with removing WT5 & WT6 for multi-hop support since it is an important feature for Public Safety James Hu (AT&T) comment that removing WT4, WT5 and WT6 are not acceptable to us. These WTs shall stay within this SID. Heng (China Telecom) dose not agree the removal of WT4 and WT9 Deng Qiang (CATT) responds and provides r01. LaeYoung (LGE) comments on r01. Deng Qiang (CATT) provides r02. Mehrdad (Samsung) comments on r02 Deng Qiang (CATT) provides r03 and r04. Fei (OPPO) comments. Fei (OPPO) responds to Steve (Huawei) Ihab (FirstNet) FistNet will object to any revisions of the SID that propose the removal of WT5 & WT6 for multi-hop support ==== Revisions Deadline ==== James Hu (AT&T) provides comments: we are ok with r03 with WT5 and WT6 included and object r04 and all revisions without multi-hops support. Hannu (Nokia) has got sympathy with WT#5 and #6, but SA2 is the wrong place for this battle. Since RAN has already de-prioritised these topics out of Rel-18, there is no point to include them in SA2 study either. Hannu (Nokia) still doesn't see the need for WT#9 but can live with revision where the service continuity aspect is removed from WT#4. Hannu (Nokia) does not oppose the SID but requests it to be handled in CC due to high number of budgeted TUs. Asks also why is WT#9 still included in the draft SID when 10 companies spoke against it in MED process? Steve (Huawei) objects to any revision that includes WT#9 (all so far, r00, r01, r02, r03, r04). Mehrdad (Samsung) suggests to take r03 and r04 to CC#3. We prefer r04 and object to any revisions without WT#9 Hong (Qualcomm) replies to Steve. Hannu (Nokia) objects to r03 and r04, but proposes to take r04 as the template for further work. WT4, 5, 6 and 9 have all been challenged so r05 with all of them removed would give us a subset of the SID that probably nobody would object based on what it includes. (some might object it based on what it does not, though) Mehrdad (Samsung) does not agree on removing WT#4 and WT#9 and objects to any new revisions based on this ==== Comments Deadline ==== James (AT&T) understands RAN dependency with WT#5 and #6. RAN has NOT decided to exclude this feature yet for R18, it is premature to exclude it in this SID. Our position stands. Steve (Huawei) comments. | Revised |
| 9.1.4 | S2-2109359 | SID NEW | Approval | New WID on Study on System enhancement for Proximity based Services in 5GS - Phase 2 . | CATT, OPPO | Rel-18 | Revision of S2-2108525r06. CC#3: Technically Endorsed with an objection from Nokia on WT#4 | Endorsed | |
| 9.1.4 | S2-2108593 | DISCUSSION | Agreement | Discussion on enhancement for URLLC. | Huawei, HiSilicon | Noted | Noted | ||
| 9.1.4 | S2-2108690 | DISCUSSION | Decision | Discusson about AI based positioning | vivo | Rel-18 | Noted | Noted | |
| 9.1.5 | - | - | - | Revision of Rel-18 SID/WID proposal APPROVED at SA2#147E | - | - | Docs:=13 | - | |
| 9.1.5 | S2-2108416 | SID NEW | Approval | New SID on Study on architecture enhancement for XR and media services . | China Mobile, Huawei, Hisilicon, Tencent, Xiaomi | Rel-18 | Revision of (Approved) S2-2108156 from S2#147E. r07 agreed. Revised to S2-2109360. | Paul (Ericsson) provides comments and questions for clarification. Dario S. Tonesi (Qualcomm) provides S2-2108416_Qualcomm in the draft folder. Dan (China Mobile) provides r02 and please ignore r01 Devaki (Nokia) provides -revNokia in the DRAFTS folder. Hui (Huawei) replies to Paul (Ericsson) . Hui (Huawei) fine with Devaki's proposal. Paul (Ericsson) asks questions for clarifications and provides comments. Paul (Ericsson) asks Hui (Huawei) questions for clarification. Hui (Huawei) replies. Dan(China Mobile) provides r03 Paul (Ericsson) replies to Hui (Huawei) and asks questions for clarifications. Hui(Huawei) replies.. Paul (Ericsson) replies to Hui (Huawei). Hui(Huawei) replies to Paul (Ericsson). Dario (Qualcomm) thanks and provides S2-2108416r02_QC in the draft folder. Dan(China Mobile) provide r04 to reflect Hui's update. Dan (China Mobile) thanks Dario's mention and provide r05,and thanks for Yang(oppo)'s offline comment and provide r06 ==== Revisions Deadline ==== Dan (China Mobile) suggest to accept r06 Dario (Qualcomm) objects to r03, 4, 5, 6. Can accept r02 + TU adjustment. ==== Comments Deadline ==== Devaki (Nokia) comments that r01 based on _Nokia revision is missing. Requests that the SID is brought up to CC#2/#3 as it has a pending EN, TU(s) do not match thus changes have to be done. Original version cannot be approved due to pending issues that have not been resolved yet. Dan(China Mobile) provide update r06 in CC#2 | Revised |
| 9.1.5 | S2-2109360 | SID NEW | Approval | New SID on Study on architecture enhancement for XR and media services . | China Mobile, Huawei, Hisilicon, Tencent, Xiaomi | Rel-18 | Revision of S2-2108416r07. Approved | Approved | |
| 9.1.5 | S2-2108424 | DISCUSSION | Discussion | Discussion on Topic for NWDAF-assisted RFSP Index Selection in R18. | China Telecom | Rel-18 | Noted | Belen (Ericsson) disagree to add this objective to eNA_Ph3 as it would need their own SID. Leo (Deutsche Telekom) has similar concerns as Ericsson, eNA should not be extended to be applicable to EPC. Yannick (Nokia): Nokia provides comments and share concerns expressed already on this proposed eNA_Ph3 work task. Zhuoyi (China Telecom): China Telecom replies to Yannick and Belen. Belen (Ericsson) replies to China Telecom, still disagrees to add this objective to eNA_Ph3 SID. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.1.5 | S2-2108437 | SID NEW | Approval | New SID on enhancement of 5G AM Policy. | China Telecom | Rel-18 | Revision of (Approved) S2-2108155 from S2#147E. r02 agreed. Revised to S2-2109327. | Sicheng (SGCC) supports the SID and would like to co-sign it. Kaixin (CBN) supports the SID. Jing (CAICT) supports the SID and would like to co-sign it. Zhuoyi (China Telecom) provides r01 with new supporting companies. Guliang (INSPUR) supports this SID and please add Inpurt as supporting companies. Zhuoyi (China Telecom) provides r02 with Inspur as new supporting company. ==== Revisions Deadline ==== ==== Comments Deadline ==== Susana (Vodafone) supports this SID and asks to be included as supporting company. Zhuoyi(China Telecom) provides drafting r03 with Vodafone in supporting company. | Revised |
| 9.1.5 | S2-2109327 | SID NEW | Approval | New SID on enhancement of 5G AM Policy. | China Telecom | Rel-18 | Revision of S2-2108437r02. Approved | Approved | |
| 9.1.5 | S2-2108455 | SID REVISED | Approval | New SID: Study on enhancement of 5G UE Policy. | Intel, Qualcomm Incorporated, OPPO, ZTE, NTT Docomo, vivo, Telecom Italia, China Unicom, Huawei, HiSilicon, Vodafone, CATT, MediaTek, KPN, China Telecom, CMCC, KDDI, Xiaomi, Apple, Verizon UK Ltd, Samsung, Lenovo, Motorola Mobility, LG Electronics, Rakute | Rel-18 | r02 agreed. Revised to S2-2109328. | Changhong (Intel) provides r01 to be consistent the new SID template. Changhong (Intel) provides r02 to add DISH Network as supporting company. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Revised |
| 9.1.5 | S2-2109328 | SID REVISED | Approval | New SID: Study on enhancement of 5G UE Policy. | Intel, Qualcomm Incorporated, OPPO, ZTE, NTT Docomo, vivo, Telecom Italia, China Unicom, Huawei, HiSilicon, Vodafone, CATT, MediaTek, KPN, China Telecom, CMCC, KDDI, Xiaomi, Apple, Verizon UK Ltd, Samsung, Lenovo, Motorola Mobility, LG Electronics, Rakuten Mobile Inc., Ericsson, Convida Wireless, Orange, DISH Network | Rel-18 | Revision of S2-2108455r02. Approved | Approved | |
| 9.1.5 | S2-2108552 | SID NEW | Approval | New SID on Enhancement of support for Edge Computing in 5G Core network - phase 2 | Huawei, HiSilicon, Alibaba, China Unicom, Convida Wireless, Intel, Toyota, vivo, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (Approved) S2-2108166 from S2#147E. r01 agreed. Revised to S2-2109329. | Samsung supports this SID. Guliang(Inspur) supports this SID and please add Inspur as supporting company. Patrice (Huawei) thanks Jicheol (Samsung) and Guliang (Inspur) for their support. Jarmo (KPN) thanks for support given to add the proposed objective in a new revision S2-2108552 and replies to whether to include the objective to WT7 or to add a new WT9 Zhuoyun (Tencent) supports the SID. Patrice (Huawei) thanks Zhuoyun (Tencent) for their support and provides r01 with the additional supporting companies and the content of S2-2108897. ==== Revisions Deadline ==== ==== Comments Deadline ==== Susana (Vodafone) supports this SID | Revised |
| 9.1.5 | S2-2109329 | SID NEW | Approval | New SID on Enhancement of support for Edge Computing in 5G Core network — phase 2 . | Huawei, HiSilicon, Alibaba, China Unicom, Convida Wireless, Intel, Toyota, vivo, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2108552r01. Approved | Approved | |
| 9.1.5 | S2-2108749 | SID NEW | Approval | Study on Enablers for Network Automation for 5G - phase 3. | China Mobile, vivo | Rel-18 | CC#3: r08 agreed. Revised to S2-2109361. | Antoine (Orange) provides r01. Aihua(CMCC) replies and provides r02. Aihua(CMCC) provides r03 to make alignment between the first column and the last on the WT tag . Xiaobo(vivo) replies and provides r04. Yannick (Nokia): Nokia provides comments. Nokia cannot agree to reduce the TU estimates agreed in SA2#147E without changing the work tasks description. Nokia cannot agree to remove WT#3.1 and WT#3.5. Farooq (AT&T) provides proposal on down scoping the study Guliang (Inspur) support the SID and would like to co-source it. Belen (Ericsson) objects to all revisions presented so far, supports AT&T proposal to discuss thos WT that start with 'whether and how' for downscoping. Juan Zhang (Qualcomm) supports to trigger a discussion for down scoping but not just simply reduce the total number. LaeYoung (LGE) also thinks that down-scoping is needed instead of just down-sizing to unrealistic TUs. David (Samsung) supports avoiding plain down-sizing without adjustments in the scope. Dimitris (Lenovo) supports the view that any changes to TU would require adjustments in the scope Antoine (Orange) provides r05. Aihua (CMCC) replies and provides r06. Malla (NTT DOCOMO) object r06. Malla (NTT DOCOMO) further comment. Belen (Ericsson) objects to r06 Juan Zhang (Qualcomm) proposes to start a moderate email discussion. David (Samsung) comments. Aihua(CMCC) comments and provides r07 as the basis for potential MED. Belen (Ericsson) comments on r07 and ask for updates ==== Revisions Deadline ==== Xiaobo(vivo) reply Belen's comments. Yang (OPPO) provides the rewording suggestion. Belen (Ericsson) still objects to r07. Provides a rewording suggestion Yannick (Nokia): Nokia objects to all revisions that attempt to remove some work tasks (r01, r02, r03, r04, r06) and to initial version that reduces the TU estimates without appropriate down-scoping for the work. We should have proper moderated email discussion to further reduce the number of work tasks and suggest to discuss the details for this at a CC during this meeting. Xiaobo(vivo) support the proposal from Yannick(Nokia) to reword WT#3.8. ==== Comments Deadline ==== Aihua(CMCC) provides drafting r08 for further check. | Revised |
| 9.1.5 | S2-2109361 | SID NEW | Approval | Study on Enablers for Network Automation for 5G - phase 3. | China Mobile, vivo | Rel-18 | Revision of S2-2108749r08. Approved. It was noted that the TU Budget for this needs further off-line work. | Approved | |
| 9.1.5 | S2-2108993 | LS In | Action | LS from 5GAA: LS on Enhancements on QoS Sustainability analytics in the context of the Study on Enablers for Network Automation for 5G - phase 3 (FS_eNA_Ph3) | 5GAA (5GAA_S-210186) | Postponed | Postponed | ||
| 9.1.5 | S2-2108897 | DISCUSSION | Agreement | DP on new objective for FS_eEDGE_5GC_ph2: potential solutions for the AF to be able to obtain/determine the DNAI in Release 18. | KPN, Huawei | Rel-18 | Noted | Patrice (Huawei) proposes to endorse S2-2108897 and include the proposed objective in a revision of S2-2108552. ==== Revisions Deadline ==== ==== Comments Deadline ==== | Noted |
| 9.2 | - | - | - | Review of the Work Plan, Rel-17 WID Status Reports | - | - | Docs:=25 | - | |
| 9.2 | S2-2108492 | WORK PLAN | Information | Work_plan_3gpp_211001_Filtered_SA2 | MCC | Noted | Noted | ||
| 9.2 | S2-2108302 | WI STATUS REPORT | Information | EV2XARC_Ph2 status report | LG Electronics | Rel-17 | Revised to S2-2109374. | Revised | |
| 9.2 | S2-2109374 | WI STATUS REPORT | Information | EV2XARC_Ph2 status report | LG Electronics | Rel-17 | Revision of S2-2108302. Noted | Noted | |
| 9.2 | S2-2108435 | WI STATUS REPORT | Information | SA WG2 Status report for eLCS_Ph2 | CATT | Rel-17 | Noted | Noted | |
| 9.2 | S2-2108439 | WI STATUS REPORT | Information | MINT Status Report | LG Electronics | Rel-17 | Revised to S2-2109379. | Revised | |
| 9.2 | S2-2109379 | WI STATUS REPORT | Information | MINT Status Report | LG Electronics | Rel-17 | Revision of S2-2108439. Noted | Noted | |
| 9.2 | S2-2108464 | WI STATUS REPORT | Information | ENPN Status Report | Ericsson (rapporteur) | Noted | Noted | ||
| 9.2 | S2-2108487 | WI STATUS REPORT | Approval | IIoT Status report | Nokia, Nokia Shanghai Bell (Rapporteur) | Rel-17 | Noted | Noted | |
| 9.2 | S2-2108524 | WI STATUS REPORT | Information | 5G_ProSe Status Report | CATT | Rel-17 | Revised to S2-2109375. | Revised | |
| 9.2 | S2-2109375 | WI STATUS REPORT | Information | 5G_ProSe Status Report | CATT | Rel-17 | Revision of S2-2108524. Noted | Noted | |
| 9.2 | S2-2108610 | WI STATUS REPORT | Information | ENS_Ph2 status report | ZTE | Rel-17 | Revised to S2-2109376. | Revised | |
| 9.2 | S2-2109376 | WI STATUS REPORT | Information | ENS_Ph2 status report | ZTE | Rel-17 | Revision of S2-2108610. Noted | Noted | |
| 9.2 | S2-2109377 | WI STATUS REPORT | Information | eEdge_5GC status report | Huawei | Rel-17 | Revision of S2-2108720. Noted | Noted | |
| 9.2 | S2-2108669 | WI STATUS REPORT | Information | 5MBS Status Report | Huawei,HiSilicon | Rel-17 | Revised to S2-2109380. | Revised | |
| 9.2 | S2-2109380 | WI STATUS REPORT | Information | 5MBS Status Report | Huawei,HiSilicon | Rel-17 | Revision of S2-2108669. Noted | Noted | |
| 9.2 | S2-2108691 | WI STATUS REPORT | Information | Report_eNA_ph2 | vivo | Rel-17 | Revised to S2-2109378. | Aihua(CMCC) provides r01. | Revised |
| 9.2 | S2-2109378 | WI STATUS REPORT | Information | Report_eNA_ph2 | vivo | Rel-17 | Revision of S2-2108691. Noted | Noted | |
| 9.2 | S2-2108720 | WI STATUS REPORT | Information | eEdge_5GC status report | Huawei | Rel-17 | Revised to S2-2109377 | Revised | |
| 9.2 | S2-2108826 | WI STATUS REPORT | Discussion | IoT_SAT_ARCH_EPS Status Report | MediaTek Inc. | Rel-17 | r01 Revised to S2-2109382. | Guillaume (MediaTek Inc.) provides r01. | Revised |
| 9.2 | S2-2109382 | WI STATUS REPORT | Discussion | IoT_SAT_ARCH_EPS Status Report | MediaTek Inc. | Rel-17 | Revision of S2-2108826r01. Noted | Noted | |
| 9.2 | S2-2108957 | WI STATUS REPORT | Information | SA WG2 Status report for MUSIM | Intel (rapporteur) | Rel-17 | Revised to S2-2109381. | Revised | |
| 9.2 | S2-2109381 | WI STATUS REPORT | Information | SA WG2 Status report for MUSIM | Intel (rapporteur) | Rel-17 | Revision of S2-2108957. Noted | Noted | |
| 9.2 | S2-2109021 | WI STATUS REPORT | Information | WI Status Report for ARCH_NR_REDCAP | China Mobile (rapporteur) | Rel-17 | Noted | Aihua(CMCC) provides status report for ARCH_NR_REDCAP. | Noted |
| 9.2 | S2-2109370 | WI STATUS REPORT | Information | ID_UAS status report | Qualcomm (Rapporteur) | Rel-17 | Noted | Noted | |
| 9.2 | S2-2109383 | WI STATUS REPORT | Information | SA WG2 Status report for 5GSAT_ARCH | Thales (Rapporteur) | Noted | Noted | ||
| 9.3 | - | - | - | Planning future meetings | - | - | Docs:=0 | - | |
| 11 | - | - | - | Close of e-meeting | - | - | Docs:=0 | - | |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=105 | - | |
| 99 | S2-2108901 | LS OUT | Approval | [DRAFT] Reply LS on IMS Data Channel Architecture | China Mobile | Response to S2-2108297. WITHDRAWN | Withdrawn | ||
| 99 | S2-2108899 | LS OUT | Approval | [DRAFT] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | China Mobile | Response to S2-2108264. WITHDRAWN | Withdrawn | ||
| 99 | S2-2108900 | CR | Approval | 23.501 CR3308R1 (Rel-17, 'F'): Network slicing support for SNPN | China Mobile | Rel-17 | Revision of (Noted) S2-2107501 from S2#147E. WITHDRAWN | Withdrawn | |
| 99 | S2-2108898 | SID REVISED | Approval | Study on system architecture for next generation real time communication services | China Mobile, China Unicom, Huawei, Hisilicon, ZTE, CATT, Vivo, Deutsche Telekom, T-Mobile USA, Ericsson, AT&T | Rel-18 | Revision of (Approved) S2-2108165 from S2#147E. WITHDRAWN | Withdrawn | |
| 99 | S2-2108306 | CR | Approval | 23.401 CR3617R2 (Rel-16, 'F'): On alignment of RACS capability detection with RAN WG3 | Nokia, Nokia Shanghai Bell,Qualcomm Inc, Ericsson | Rel-16 | Revision of (Postponed) S2-2100064 from S2#143E. WITHDRAWN | Withdrawn | |
| 99 | S2-2108337 | CR | Approval | 23.501 CR3361 (Rel-17, 'F'): Correction to UE-Slice-MBR support | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108954 | CR | Approval | 23.501 CR3459 (Rel-17, 'F'): Clarification on the input of PCF/NEF/MB-SMF service operation | ZTE | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108344 | CR | Approval | 23.503 CR0669 (Rel-16, 'F'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-16 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108345 | CR | Approval | 23.503 CR0670 (Rel-17, 'A'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-17 | WITHDRAWN | Irfan (Cisco) provides r01 Haris(Qualcomm) cannot accept r01 since it creates ambiguity re the requirement for SSC mode 2 | Withdrawn |
| 99 | S2-2108588 | CR | Approval | 23.501 CR3396 (Rel-17, 'F'): Extending MA PDU Session Control information in the PCC Rule | Huawei, HiSilicon | Rel-17 | Revision of (Agreed) S2-2107828 from S2#147E. WITHDRAWN | Withdrawn | |
| 99 | S2-2108885 | DISCUSSION | Approval | DP on new objective for FS_eEDGE_5GC_ph2: potential solutions for the AF to be able to obtain/determine the DNAI in Release 18. | KPN, Huawei | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108541 | CR | Approval | 23.501 CR3387 (Rel-17, 'F'): Multiple PTP instances supported in 5GS | Tencent, Tencent Cloud | Rel-17 | WITHDRAWN | Devaki (Nokia) has concerns with the CR. Sang-Jun (Samsung) comments that 8847 replaces 8541. | Withdrawn |
| 99 | S2-2108528 | CR | Approval | 23.501 CR3385 (Rel-17, 'F'): Clarification for NSAC of home-routed PDU Sessions | China Unicom | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108393 | CR | Approval | 23.287 CR0173 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108418 | CR | Approval | 23.502 CR3143R1 (Rel-17, 'F'): Network slice status notifications when multiple NSACFs exist for one S-NSSAI | China Mobile | Rel-17 | Revision of (Postponed) S2-2107221 from S2#147E. WITHDRAWN | Withdrawn | |
| 99 | S2-2108454 | CR | Approval | 23.256 CR0034 (Rel-17, 'F'): Clarification on UUAA-SM optimization procedures | Samsung | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108383 | CR | Approval | 23.304 CR0043 (Rel-17, 'F'): Update to Nnrf_NFManagement_NFRegister service operation | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2108432 | SID NEW | Approval | New SID on Enhancement to the 5GC LoCation Services Phase 3. | CATT, Huawei | Rel-18 | Revision of (revised and endorsed) S2-2107083 from S2#147E. WITHDRAWN | Withdrawn |