IPR call reminder:
I draw your attention to your obligations under the 3GPP Partner Organizations’ IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP. Delegates are asked to take note that they are thereby invited:
|
Antitrust policy Reminder:
I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this TSG/WG/SWG meeting including the Chair and Vice Chairs. In case of question I recommend that you contact your legal counsel. The leadership shall conduct the present meeting with impartiality and in the interests of 3GPP. Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG/SWG meetings is important to allow for full and fair consideration of such matters. |
AI | TD# | Type | Doc For | Subject | Source | Rel | Comments | e-mail_Discussion | Result |
0 | - | - | - | All Agenda Items | - | - | Docs:=0 | - | |
1.1 | - | - | - | Opening of the meeting | - | - | Docs:=0 | - | |
2 | - | - | - | Agenda | - | - | Docs:=2 | - | |
2 | S2-2500001 | AGENDA | Approval | SA2#166 Ad Hoc-e meeting Agenda | SA WG2 Chair | ||||
2 | S2-2500002 | AGENDA | Information | SA2#166 Ad Hoc-e meeting Schedule | SA WG2 Chair | ||||
2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
3 | - | - | - | SA2#166 Meeting report | - | - | Docs:=1 | - | |
3 | S2-2500003 | REPORT | Approval | Draft Report of SA WG2 meeting #166 | SA WG2 Secretary | ||||
4 | - | - | - | General | - | - | Docs:=0 | - | |
4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=19 | - | |
4.1 | - | - | - | LS in for information - propose to note | - | - | Docs:=6 | - | |
4.1 | S2-2500059 | LS In | Information | LS from SA WG1: Reply LS on UAV regulation | SA WG1 (S1-244759) | Rel-19 | |||
4.1 | S2-2500030 | LS In | Information | LS from ITU-D SG2: Liaison statement from ITU-D Study Group 2 Question 4/2 to IEEE, ISO, IEC, ETSI, 3GPP, GSMA, IETF, Wi-Fi Alliance, International Laboratory Accreditation Cooperation, and International Accreditation Forum on draft final report of ITU-D | ITU-D SG2 (D22-SG02-C-0342) | ||||
4.1 | S2-2500073 | LS In | Information | LS from SA WG6: Reply LS on clarifications on consent management | SA WG6 (S6-245716) | Rel-18 | |||
4.1 | S2-2500075 | LS In | Information | LS from TSG SA: Reply LS on clarifications on consent management. | TSG SA (SP-241934) | Rel-18 | |||
4.1 | S2-2500029 | LS In | Information | LS from 5G-ACIA: 5G-ACIA LS on Enhancements for 5G System Operating as Logical (TSN) Bridge(s) in Integrated IEEE/3GPP Networks | 5G-ACIA (5G-ACIA-LS-2024-008) | ||||
4.1 | S2-2500076 | LS In | Information | LS from ETSI TC CYBER: Update on ETSI TC Cyber middlebox work | ETSI TC CYBER (CYBER(24)39d006r1) | ||||
4.1 | - | - | - | LS on CENs requirements for eCall over IMS | - | - | Docs:=2 | - | |
4.1 | S2-2500033 | LS In | Action | LS from CT WG1: Reply to Reply LS on CENs requirements for eCall over IMS | CT WG1 (C1-246950) | Rel-19 | |||
4.1 | S2-2500057 | LS In | Action | LS from SA WG1: Reply LS on CEN requirements for eCall over IMS | SA WG1 (S1-244755) | Rel-19 | |||
4.1 | - | - | - | LS on Clarification request on usage and control of UE Local Configuration | - | - | Docs:=5 | - | |
4.1 | S2-2500034 | LS In | Action | LS from CT WG1: Reply LS on Clarification request on usage and control of UE Local Configuration | CT WG1 (C1-247121) | Rel-19 | Responses drafted in S2-2500219, S2-2500519, S2-2500778, S2-2501027 | ||
4.1 | S2-2500219 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Nokia | Rel-19 | Response to S2-2500034 | ||
4.1 | S2-2500519 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Qualcomm Incorporated | Rel-15 | Response to S2-2500034 | ||
4.1 | S2-2500778 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Samsung | Response to S2-2500034 | |||
4.1 | S2-2501027 | LS OUT | Approval | [DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration | Rel-19 | Response to S2-2500034 | |||
4.1 | - | - | - | LS on support of multiple access technologies based on the IMS service type | - | - | Docs:=3 | - | |
4.1 | S2-2500060 | LS In | Action | LS from SA WG1: Reply LS on support of multiple access technologies based on the IMS service type | SA WG1 (S1-244916) | Rel-20 | Responses drafted in S2-2500786, S2-2500943 | ||
4.1 | S2-2500786 | LS OUT | Approval | [DRAFT] Reply LS on support of multiple access technologies based on the IMS service type | China Telecom | Rel-20 | Response to S2-2500060 | ||
4.1 | S2-2500943 | LS OUT | Approval | [DRAFT] Reply LS on support of multiple access technologies based on the IMS service type | Samsung | Rel-20 | Response to S2-2500060 | ||
4.1 | - | - | - | LS on Usage of Charging Characteristics and CHF Group ID | - | - | Docs:=1 | - | |
4.1 | S2-2500067 | LS In | Action | LS from SA WG5: LS on Usage of Charging Characteristics and CHF Group ID | SA WG5 (S5-246956) | Rel-19 | |||
4.1 | - | - | - | LS from GSMA TSGNS: OSAppID usage by AppToken use case | - | - | Docs:=2 | - | |
4.1 | S2-2500077 | LS In | Information | LS from GSMA TSGNS: OSAppID usage by AppToken use case | GSMA TSGNS (TSGNS44_003v6) | Response drafted in S2-2500962 | |||
4.1 | S2-2500962 | LS OUT | Approval | [DRAFT] Reply LS for OSAppID usage by AppToken use case | China Mobile | Rel-19 | Response to S2-2500077 | ||
4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=0 | - | |
5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=0 | - | |
5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=0 | - | |
5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | Docs:=0 | - | |
5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | Docs:=0 | - | |
6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Docs:=0 | - | |
6.1 | - | - | - | General aspects, concepts and reference models | - | - | Docs:=3 | - | |
6.1 | S2-2500038 | LS In | Action | LS from CT WG4: Reply LS on slice mapping between the HPLMN and EHPLMN | CT WG4 (C4-245430) | Rel-18 | Responses drafted in S2-2500605, S2-2500867 | ||
6.1 | S2-2500605 | LS OUT | Approval | [DRAFT] Response LS on slice mapping between the HPLMN and EHPLMN | Huawei, HiSilicon | Rel-18 | Response to S2-2500038 | ||
6.1 | S2-2500867 | LS OUT | Approval | [DRAFT] LS Response on slice mapping between the HPLMN and EHPLMN | ZTE | Rel-18 | Response to S2-2500038 | ||
6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=3 | - | |
6.2 | S2-2500404 | CR | Approval | 23.502 CR5241 (Rel-19, 'F'): NSSAI update with RA change | Ericsson, AT&T | Rel-19 | |||
6.2 | S2-2500875 | CR | Approval | 23.501 CR6022 (Rel-19, 'F'): Clarification on NSAC for EHPLMN case | ZTE | Rel-19 | |||
6.2 | S2-2500918 | CR | Approval | 23.501 CR6037 (Rel-18, 'F'): Clarification on NSAC for EHPLMN case | ZTE | Rel-18 | |||
6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=0 | - | |
6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=2 | - | |
6.5 | S2-2500360 | CR | Approval | 23.501 CR5931 (Rel-18, 'F'): VPLMN QoS constraint clarification | Ericsson | Rel-18 | |||
6.5 | S2-2500361 | CR | Approval | 23.501 CR5932 (Rel-19, 'A'): VPLMN QoS contranit clarification | Ericsson | Rel-19 | |||
6.6 | - | - | - | Policy and charging control | - | - | Docs:=3 | - | |
6.6 | S2-2500258 | CR | Approval | 23.502 CR5223 (Rel-19, 'F'): Reporting PCF authorization failure to the AF | Ericsson, AT&T | Rel-19 | |||
6.6 | S2-2500259 | CR | Approval | 23.503 CR1463 (Rel-19, 'F'): Reporting PCF authorization failure to the AF | Ericsson, AT&T | Rel-19 | |||
6.6 | S2-2500260 | CR | Approval | 23.502 CR5224 (Rel-19, 'F'): Removing URSP rules upon UDR Policy Data removal | Ericsson, AT&T | Rel-19 | |||
6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
6.8 | - | - | - | Specific services support | - | - | Docs:=0 | - | |
6.9 | - | - | - | Interworking and Migration | - | - | Docs:=3 | - | |
6.9 | S2-2500606 | CR | Approval | 23.502 CR5262 (Rel-17, 'F'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-17 | |||
6.9 | S2-2500607 | CR | Approval | 23.502 CR5263 (Rel-18, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-18 | |||
6.9 | S2-2500608 | CR | Approval | 23.502 CR5264 (Rel-19, 'A'): SM context release in the IRAT handover procedure | Huawei, HiSilicon | Rel-19 | |||
6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
6.11 | - | - | - | Framework functions | - | - | Docs:=1 | - | |
6.11 | S2-2500168 | CR | Approval | 23.501 CR5820R1 (Rel-19, 'F'): Correction on network function service framework | China Mobile | Rel-19 | Revision of S2-2411419 | ||
7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Docs:=0 | - | |
7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | Docs:=1 | - | |
7.1 | S2-2500257 | CR | Approval | 23.502 CR5222 (Rel-19, 'F'): Correcting service specific parameter provisioning | Ericsson, AT&T | Rel-19 | |||
7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=0 | - | |
7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | Docs:=0 | - | |
7.4 | - | - | - | Cellular IoT support and evolution for the 5G System (5G_CIoT) | - | - | Docs:=0 | - | |
7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=0 | - | |
7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=10 | - | |
7.7 | S2-2500416 | DISCUSSION | Discussion | Discussion paper on missing Optional LLDP TLVs . | Nokia | ||||
7.7 | S2-2500417 | CR | Approval | 23.501 CR5945 (Rel-16, 'F'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-16 | |||
7.7 | S2-2500418 | CR | Approval | 23.501 CR5946 (Rel-17, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-17 | |||
7.7 | S2-2500419 | CR | Approval | 23.501 CR5947 (Rel-18, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-18 | |||
7.7 | S2-2500420 | CR | Approval | 23.501 CR5948 (Rel-19, 'A'): Addition of missing LLDP TLVs | Nokia, Samsung | Rel-19 | |||
7.7 | S2-2500766 | DISCUSSION | Discussion | PDU Session Modification for Port Management Information. | Samsung | ||||
7.7 | S2-2500770 | CR | Approval | 23.502 CR5281 (Rel-16, 'F'): PDU Session Modification for Port Management Information | Samsung | Rel-16 | |||
7.7 | S2-2500773 | CR | Approval | 23.502 CR5282 (Rel-17, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-17 | |||
7.7 | S2-2500774 | CR | Approval | 23.502 CR5283 (Rel-18, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-18 | |||
7.7 | S2-2500777 | CR | Approval | 23.502 CR5285 (Rel-19, 'A'): PDU Session Modification for Port Management Information | Samsung | Rel-19 | |||
7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | Docs:=0 | - | |
7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | Docs:=0 | - | |
7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | Docs:=0 | - | |
7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=0 | - | |
7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=0 | - | |
7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=0 | - | |
7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=0 | - | |
7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=0 | - | |
7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | Docs:=0 | - | |
7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | Docs:=0 | - | |
8 | - | - | - | Rel-17 Maintenance | - | - | Docs:=0 | - | |
8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=1 | - | |
8.1 | S2-2500095 | CR | Approval | 23.288 CR1311 (Rel-19, 'F'): Correction on MFAF related service | ZTE | Rel-19 | |||
8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=0 | - | |
8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=0 | - | |
8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=0 | - | |
8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=0 | - | |
8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=4 | - | |
8.6 | S2-2500381 | CR | Approval | 23.501 CR5936 (Rel-17, 'F'): Correction to specify UE and Network behaviour when steering capability do not match for a UE requested MA PDU Session | Nokia | Rel-17 | |||
8.6 | S2-2500382 | CR | Approval | 23.501 CR5937 (Rel-18, 'A'): Correction to specify UE and Network behaviour when steering capability do not match for a UE requested MA PDU Session | Nokia | Rel-18 | |||
8.6 | S2-2500383 | CR | Approval | 23.503 CR1468 (Rel-17, 'F'): Clarification on PCC Rule for 'match all' traffic when the MA PDU Session supports ATSSS-LL | Nokia | Rel-17 | |||
8.6 | S2-2500384 | CR | Approval | 23.503 CR1469 (Rel-18, 'A'): Clarification on PCC Rule for 'match all' traffic when the MA PDU Session supports ATSSS-LL | Nokia | Rel-18 | |||
8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=17 | - | |
8.7 | S2-2500039 | LS In | Action | LS from CT WG4: LS on UUAA Unsubscribe procedure | CT WG4 (C4-245436) | Rel-17 | Responses drafted in S2-2500437, S2-2500509, S2-2500602, S2-2500941 | ||
8.7 | S2-2500437 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Ericsson | Rel-17 | Response to S2-2500039 | ||
8.7 | S2-2500509 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | CATT | Rel-17 | Response to S2-2500039 | ||
8.7 | S2-2500602 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Nokia | Rel-17 | Response to S2-2500039 | ||
8.7 | S2-2500941 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Samsung | Rel-17 | Response to S2-2500039 | ||
8.7 | S2-2500392 | CR | Approval | 23.256 CR0157 (Rel-17, 'D'): Removing ENs for clean-up | LG Electronics | Rel-17 | |||
8.7 | S2-2500393 | CR | Approval | 23.256 CR0158 (Rel-18, 'A'): Removing ENs for clean-up | LG Electronics | Rel-18 | |||
8.7 | S2-2500394 | CR | Approval | 23.256 CR0159 (Rel-19, 'A'): Removing ENs for clean-up | LG Electronics | Rel-19 | |||
8.7 | S2-2500510 | CR | Approval | 23.256 CR0168 (Rel-17, 'F'): UUAA Unsubscribe | CATT | Rel-17 | |||
8.7 | S2-2500511 | CR | Approval | 23.256 CR0169 (Rel-18, 'A'): UUAA Unsubscribe | CATT | Rel-18 | |||
8.7 | S2-2500512 | CR | Approval | 23.256 CR0170 (Rel-19, 'A'): UUAA Unsubscribe | CATT | Rel-19 | |||
8.7 | S2-2500599 | CR | Approval | 23.256 CR0172 (Rel-17, 'F'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-17 | |||
8.7 | S2-2500600 | CR | Approval | 23.256 CR0173 (Rel-18, 'A'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-18 | |||
8.7 | S2-2500601 | CR | Approval | 23.256 CR0174 (Rel-19, 'A'): Correction to specify Nnef_Authentication Unsubscribe service operation | Nokia | Rel-19 | |||
8.7 | S2-2500917 | CR | Approval | 23.256 CR0179 (Rel-17, 'F'): Unsubscribe service operation with UAS NF | Samsung | Rel-17 | |||
8.7 | S2-2500919 | CR | Approval | 23.256 CR0180 (Rel-18, 'A'): Unsubscribe service operation with UAS NF | Samsung | Rel-18 | |||
8.7 | S2-2500921 | CR | Approval | 23.256 CR0181 (Rel-19, 'A'): Unsubscribe service operation with UAS NF | Samsung | Rel-19 | |||
8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=0 | - | |
8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=7 | - | |
8.9 | S2-2500249 | CR | Approval | 23.247 CR0378 (Rel-17, 'F'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-17 | |||
8.9 | S2-2500250 | CR | Approval | 23.247 CR0379 (Rel-18, 'A'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-18 | |||
8.9 | S2-2500251 | CR | Approval | 23.247 CR0380 (Rel-19, 'A'): The NEF/MBSF rejects the MBS session creation when handling MBS session creation request | Ericsson | Rel-19 | |||
8.9 | S2-2500571 | CR | Approval | 23.247 CR0381 (Rel-17, 'F'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-17 | |||
8.9 | S2-2500572 | CR | Approval | 23.247 CR0382 (Rel-18, 'A'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-18 | |||
8.9 | S2-2500573 | CR | Approval | 23.247 CR0383 (Rel-19, 'A'): Clarification on the Cell ID in MBS Service Area | Huawei, HiSilicon | Rel-19 | |||
8.9 | S2-2500988 | CR | Approval | 23.247 CR0386 (Rel-19, 'F'): Clarification about MBS service area encoding | Nokia | Rel-19 | |||
8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=0 | - | |
8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=0 | - | |
8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=0 | - | |
8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=0 | - | |
8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=0 | - | |
8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | Docs:=0 | - | |
8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | Docs:=0 | - | |
8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | Docs:=0 | - | |
8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | Docs:=0 | - | |
8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | Docs:=0 | - | |
8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | Docs:=4 | - | |
8.21 | S2-2500666 | CR | Approval | 23.503 CR1374R2 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon | Rel-18 | Revision of S2-2410723 | ||
8.21 | S2-2500667 | CR | Approval | 23.503 CR1375R2 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2410724 | ||
8.21 | S2-2500668 | CR | Approval | 23.502 CR5020R2 (Rel-18, 'F'): Correction on DCAMP | Huawei, HiSilicon | Rel-18 | Revision of S2-2410725 | ||
8.21 | S2-2500669 | CR | Approval | 23.502 CR5021R2 (Rel-19, 'A'): Correction on DCAMP | Huawei, HiSilicon | Rel-19 | Revision of S2-2410726 | ||
8.22 | - | - | - | IP address pool information from UDM (TEI17_IPU) | - | - | Docs:=0 | - | |
8.23 | - | - | - | Same PCF selection for AMF and SMF (TEI17-SPSFAS) | - | - | Docs:=0 | - | |
8.24 | - | - | - | Support of different slices over different Non-3GPP access (TEI17_N3SLICE) | - | - | Docs:=0 | - | |
8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=0 | - | |
8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=0 | - | |
8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=0 | - | |
8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=0 | - | |
9 | - | - | - | Rel-18 WIDs | - | - | Docs:=0 | - | |
9.1.2 | - | - | - | 5G System with Satellite Backhaul (5GSATB) | - | - | Docs:=0 | - | |
9.2.2 | - | - | - | Satellite access Phase 2 (5GSAT_Ph2) | - | - | Docs:=0 | - | |
9.3.2 | - | - | - | Personal IoT Networks (5G_PIN) | - | - | Docs:=2 | - | |
9.3.2 | S2-2500472 | CR | Approval | 23.501 CR5961 (Rel-18, 'F'): Fix on N3QAI | Samsung | Rel-18 | |||
9.3.2 | S2-2500474 | CR | Approval | 23.501 CR5962 (Rel-19, 'A'): Fix on N3QAI | Samsung | Rel-19 | |||
9.4.2 | - | - | - | Phase 2 for UAS, UAV and UAM (UAS_Ph2) | - | - | Docs:=3 | - | |
9.4.2 | S2-2500056 | DISCUSSION | Discussion | Integration of Lifi Features in UAS for IoT Application | IIT, Kharagpur | ||||
9.4.2 | S2-2500396 | CR | Approval | 23.256 CR0160 (Rel-18, 'D'): Cleaning-up EN | LG Electronics | Rel-18 | |||
9.4.2 | S2-2500397 | CR | Approval | 23.256 CR0161 (Rel-19, 'A'): Cleaning-up EN | LG Electronics | Rel-19 | |||
9.5.2 | - | - | - | Ranging based services and sidelink positioning (Ranging_SL) | - | - | Docs:=4 | - | |
9.5.2 | S2-2500068 | LS In | Action | LS from SA WG5: Reply LS on Ranging/Sidelink Positioning Charging | SA WG5 (S5-247001) | Rel-19 | |||
9.5.2 | S2-2500569 | CR | Approval | 23.273 CR0648 (Rel-18, 'F'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-18 | WI Code should be Ranging_SL! | ||
9.5.2 | S2-2500570 | CR | Approval | 23.273 CR0649 (Rel-19, 'A'): Correction on RangingSideLink positioning procedure | Huawei, HiSilicon | Rel-19 | WI Code should be Ranging_SL! | ||
9.5.2 | S2-2500732 | CR | Approval | 23.586 CR0156 (Rel-18, 'F'): Correction to V2X discovery for Ranging | Vivo | Rel-18 | |||
9.6.2 | - | - | - | 5GC LoCation Services Phase 3 (eLCS_Ph3) | - | - | Docs:=15 | - | |
9.6.2 | - | - | - | LS in | - | - | Docs:=3 | - | |
9.6.2 | S2-2500035 | LS In | Information | LS from CT WG1: LS on Requesting allocation of new TCP port for Location Services User Plane Protocol (LCS-UPP) | CT WG1 (C1-247157) | Rel-18 | |||
9.6.2 | S2-2500010 | LS In | Action | LS from CT WG1: LS on UEs user plane availability status for LCS-UPP | CT WG1 (C1-246023) | Rel-19 | Response drafted in S2-2500733 | ||
9.6.2 | S2-2500733 | LS OUT | Approval | [DRAFT] Reply LS on UE's user plane availability status for LCS-UPP | vivo | Rel-19 | Response to S2-2500010 | ||
9.6.2 | - | - | - | User plane positioning - LMF re-selection | - | - | Docs:=2 | - | |
9.6.2 | S2-2500859 | CR | Approval | 23.273 CR0661 (Rel-18, 'F'): Clarification on LMF re-selection of LCS UP positioning | Huawei, HiSilicon | Rel-18 | |||
9.6.2 | S2-2500860 | CR | Approval | 23.273 CR0662 (Rel-19, 'A'): Clarification on LMF re-selection of LCS UP positioning | Huawei, HiSilicon | Rel-19 | |||
9.6.2 | - | - | - | User plane positioning - number of LCS-UPP connections | - | - | Docs:=3 | - | |
9.6.2 | S2-2500370 | DISCUSSION | Discussion | Analysis on the number of LCS-UPP connections. | Ericsson | Rel-18 | |||
9.6.2 | S2-2500372 | CR | Approval | 23.273 CR0646 (Rel-19, 'A'): Clarify number of user plane connections for user plane positioning | Ericsson | Rel-19 | WI Code should be 5G_eLCS_Ph3! | ||
9.6.2 | S2-2500371 | CR | Approval | 23.273 CR0645 (Rel-18, 'F'): Clarify number of user plane connections for user plane positioning | Ericsson | Rel-18 | LATE DOC: | ||
9.6.2 | - | - | - | User plane positioning - paging | - | - | Docs:=1 | - | |
9.6.2 | S2-2500694 | CR | Approval | 23.273 CR0655 (Rel-18, 'B'): Supporting of Paging Policy Differentiation for Positioning Service | China Telecom | Rel-18 | WI Code should be 5G_eLCS_Ph3! | ||
9.6.2 | - | - | - | User plane positioning - charging | - | - | Docs:=3 | - | |
9.6.2 | S2-2500856 | CR | Approval | 23.273 CR0659 (Rel-18, 'F'): Clarification on charging aspects for LCS UP positioning | Huawei, HiSilicon | Rel-18 | |||
9.6.2 | S2-2500857 | CR | Approval | 23.273 CR0660 (Rel-19, 'A'): Clarification on charging aspects for LCS UP positioning | Huawei, HiSilicon | Rel-19 | |||
9.6.2 | S2-2500858 | LS OUT | Approval | [DRAFT] LS on Support of charing for LCS UP positioning | Huawei, HiSilicon | ||||
9.6.2 | - | - | - | Reference and editorial change | - | - | Docs:=3 | - | |
9.6.2 | S2-2500373 | CR | Approval | 23.273 CR0647 (Rel-19, 'F'): Move NOTE 2 back to the user plane positioning text | Ericsson | Rel-19 | |||
9.6.2 | S2-2500974 | CR | Approval | 23.273 CR0663 (Rel-18, 'F'): Emergency SUPL Reference Alignment with 23.271 | Nokia, Nokia Shanghai Bell | Rel-18 | |||
9.6.2 | S2-2500975 | CR | Approval | 23.273 CR0664 (Rel-19, 'A'): Emergency SUPL Reference Alignment with 23.271 | Nokia, Nokia Shanghai Bell | Rel-19 | |||
9.7.2 | - | - | - | Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | - | - | Docs:=4 | - | |
9.7.2 | S2-2500100 | CR | Approval | 23.304 CR0521 (Rel-19, 'A'): Clarification on DNS query during Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay | Huawei, HiSilicon | Rel-19 | |||
9.7.2 | S2-2500108 | CR | Approval | 23.304 CR0526 (Rel-18, 'F'): Clarification on DNS query during Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay | Huawei, HiSilicon | Rel-18 | |||
9.7.2 | S2-2500977 | CR | Approval | 23.304 CR0541 (Rel-18, 'F'): Remote UE emergency location fallback | Nokia, Nokia Shanghai Bell | Rel-18 | |||
9.7.2 | S2-2500978 | CR | Approval | 23.304 CR0542 (Rel-19, 'A'): Remote UE emergency location fallback | Nokia, Nokia Shanghai Bell | Rel-19 | |||
9.8.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | Docs:=2 | - | |
9.8.2 | S2-2500954 | CR | Approval | 23.502 CR5306 (Rel-19, 'F'): Fix wrong implementation of approved TDoc S2-2301807 | Nokia, Huawei, HiSilicon, Ericsson | Rel-19 | |||
9.8.2 | S2-2500955 | CR | Approval | 23.502 CR5307 (Rel-18, 'F'): Fix wrong implementation of approved TDoc S2-2301807 | Nokia, Huawei, HiSilicon, Ericsson | Rel-18 | |||
9.9.2 | - | - | - | System Support for AI/ML-based Services (AIMLsys) | - | - | Docs:=0 | - | |
9.10.2 | - | - | - | 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | - | - | Docs:=2 | - | |
9.10.2 | S2-2500574 | CR | Approval | 23.247 CR0384 (Rel-18, 'F'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon | Rel-18 | |||
9.10.2 | S2-2500575 | CR | Approval | 23.247 CR0385 (Rel-19, 'A'): Clarify the support of broadcast reception for eRedCap UEs | Huawei, HiSilicon | Rel-19 | |||
9.11.2 | - | - | - | Network Slicing Phase 3 (eNS_Ph3) | - | - | Docs:=15 | - | |
9.11.2 | S2-2500156 | CR | Approval | 23.502 CR5201 (Rel-18, 'F'): Allow NSSF to provide slice validity time during slice selection | Oracle, Verizon | Rel-18 | |||
9.11.2 | S2-2500157 | CR | Approval | 23.502 CR5202 (Rel-19, 'A'): Allow NSSF to provide slice validity time during slice selection | Oracle, Verizon | Rel-19 | |||
9.11.2 | S2-2500172 | CR | Approval | 23.501 CR5895 (Rel-18, 'F'): Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon | Rel-18 | |||
9.11.2 | S2-2500180 | CR | Approval | 23.501 CR5899 (Rel-19, 'A'): Prioritization between UDM, OAM and NSSF based slice validity time | Oracle, Verizon | Rel-19 | |||
9.11.2 | S2-2500665 | DISCUSSION | Endorsement | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia | Rel-18 | |||
9.11.2 | S2-2500686 | CR | Approval | 23.501 CR5987 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia | Rel-18 | |||
9.11.2 | S2-2500687 | CR | Approval | 23.501 CR5988 (Rel-19, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT Docomo, Nokia | Rel-19 | |||
9.11.2 | S2-2500689 | CR | Approval | 23.502 CR5273 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia. | Rel-18 | |||
9.11.2 | S2-2500690 | CR | Approval | 23.502 CR5274 (Rel-19, 'F'): Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia | Rel-19 | |||
9.11.2 | S2-2500868 | CR | Approval | 23.501 CR6018 (Rel-18, 'F'): Clarification on the removal of S-NSSAI from the Configured NSSAI | ZTE, Nokia | Rel-18 | |||
9.11.2 | S2-2500869 | CR | Approval | 23.501 CR6019 (Rel-19, 'A'): Clarification on the removal of S-NSSAI from the Configured NSSAI | ZTE, Nokia | Rel-19 | |||
9.11.2 | S2-2500896 | CR | Approval | 23.501 CR6032 (Rel-18, 'F'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-18 | |||
9.11.2 | S2-2500897 | CR | Approval | 23.501 CR6033 (Rel-19, 'A'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-19 | |||
9.11.2 | S2-2500914 | CR | Approval | 23.502 CR5303 (Rel-18, 'F'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-18 | |||
9.11.2 | S2-2500915 | CR | Approval | 23.502 CR5304 (Rel-19, 'A'): Slice deregistration inactvity timer for Alternative S-NSSAI | Samsung | Rel-19 | |||
9.12.2 | - | - | - | XR (Extended Reality) and media services (XRM) | - | - | Docs:=14 | - | |
9.12.2 | S2-2500089 | CR | Approval | 23.503 CR1451 (Rel-18, 'F'): Clarification on multi-modal service | ZTE | Rel-18 | |||
9.12.2 | S2-2500090 | CR | Approval | 23.503 CR1452 (Rel-19, 'A'): Clarification on multi-modal service | ZTE | Rel-19 | |||
9.12.2 | S2-2500411 | CR | Approval | 23.501 CR5943 (Rel-18, 'F'): Terminology corrections for the support of multimodal services | Ericsson | Rel-18 | |||
9.12.2 | S2-2500412 | CR | Approval | 23.501 CR5944 (Rel-19, 'A'): Terminology corrections for the support of multimodal services | Ericsson | Rel-19 | |||
9.12.2 | S2-2500413 | CR | Approval | 23.503 CR1471 (Rel-18, 'F'): Terminology corrections for the support of multimodal services | Ericsson | Rel-18 | |||
9.12.2 | S2-2500414 | CR | Approval | 23.503 CR1472 (Rel-19, 'A'): Terminology corrections for the support of multimodal services | Ericsson | Rel-19 | |||
9.12.2 | S2-2500483 | CR | Approval | 23.502 CR5246 (Rel-18, 'F'): UL Protocol Description provisioning to SMF from PCF | Samsung | Rel-18 | |||
9.12.2 | S2-2500484 | CR | Approval | 23.502 CR5247 (Rel-19, 'A'): UL Protocol Description provisioning to SMF from PCF | Samsung | Rel-19 | |||
9.12.2 | S2-2500707 | CR | Approval | 23.503 CR1280R3 (Rel-18, 'F'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-18 | Revision of S2-2411984 | ||
9.12.2 | S2-2500708 | CR | Approval | 23.503 CR1440R1 (Rel-19, 'A'): Averaging Window in Alternative QoS Parameter Set | CATT | Rel-19 | Revision of S2-2411985 | ||
9.12.2 | S2-2500910 | CR | Approval | 23.503 CR1499 (Rel-18, 'F'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon | Rel-18 | |||
9.12.2 | S2-2500911 | CR | Approval | 23.503 CR1500 (Rel-19, 'A'): Clarifications for activation of QoS monitoring | Huawei, HiSilicon | Rel-19 | |||
9.12.2 | S2-2500912 | CR | Approval | 23.501 CR5587R4 (Rel-18, 'F'): Correction on MDBV | Huawei, HiSilicon, Nokia | Rel-18 | Revision of S2-2410787 | ||
9.12.2 | S2-2500913 | CR | Approval | 23.501 CR6036 (Rel-19, 'A'): Correction on MDBV | Huawei, HiSilicon, Nokia | Rel-19 | Revision of S2-2410788. Confirm CR Number - CR states 5588!. Confirm CR Revision - CR states 3! | ||
9.13.2 | - | - | - | RedCap Phase 2 (NR_RedCAP_Ph2) | - | - | Docs:=0 | - | |
9.14.2 | - | - | - | Evolution of IMS multimedia telephony service (NG_RTC) | - | - | Docs:=7 | - | |
9.14.2 | S2-2500063 | LS In | Information | LS from SA WG4: Reply LS on request for IMS Data Channel related clarifications | SA WG4 (S4-242073) | Rel-18 | |||
9.14.2 | S2-2500064 | LS In | Action | LS from SA WG4: Reply LS on Binding Information | SA WG4 (S4-242110) | Rel-18 | |||
9.14.2 | S2-2500640 | CR | Approval | 23.228 CR1559 (Rel-18, 'F'): Clarification on ADC Setup Procedure | ZTE | Rel-18 | WI Code should be NG_RTC! | ||
9.14.2 | S2-2500641 | CR | Approval | 23.228 CR1560 (Rel-19, 'A'): Clarification on ADC Setup Procedure | ZTE | Rel-19 | WI Code should be NG_RTC! | ||
9.14.2 | S2-2500792 | DISCUSSION | Discussion | Discussion on DC Application Information mismatches. | Samsung | Rel-19 | |||
9.14.2 | S2-2500980 | CR | Approval | 23.228 CR1394R4 (Rel-18, 'F'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-18 | Revision of S2-2410688 | ||
9.14.2 | S2-2500985 | CR | Approval | 23.228 CR1501R2 (Rel-19, 'A'): Correlating the application DC with the bootstrap DC | NTT DOCOMO | Rel-19 | Revision of S2-2410689 | ||
9.15.2 | - | - | - | Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | - | - | Docs:=0 | - | |
9.16.2 | - | - | - | UPF enhancement for Exposure And SBA (UPEAS) | - | - | Docs:=13 | - | |
9.16.2 | S2-2500036 | LS In | Action | LS from CT WG3: LS on handling of Nsmf events targeting anyUe for I-SMF | CT WG3 (C3-246487) | Rel-18 | Responses drafted in S2-2500609, S2-2500866, S2-2500992, S2-2500995, S2-2501052 | ||
9.16.2 | S2-2500866 | LS OUT | Approval | [DRAFT] LS Response on handling of Nsmf events targeting anyUe for I-SMF | ZTE | Rel-18 | Response to S2-2500036 | ||
9.16.2 | S2-2500609 | LS OUT | Approval | [DRAFT] Response LS on handling of Nsmf events targeting anyUe for I-SMF | Huawei, HiSilicon | Rel-18 | Response to S2-2500036 | ||
9.16.2 | S2-2500992 | LS OUT | Approval | [DRAFT] LS on handling of Nsmf events targeting anyUe for I-SMF | Nokia | Rel-18 | Response to S2-2500036 | ||
9.16.2 | S2-2501052 | LS OUT | Approval | [DRAFT] Reply LS on handling of Nsmf events targeting anyUe for I-SMF | Samsung | Response to S2-2500036 | |||
9.16.2 | S2-2500280 | CR | Approval | 23.502 CR5231 (Rel-18, 'F'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-18 | Confirm Specification Number - CR states 23.501! | ||
9.16.2 | S2-2500281 | CR | Approval | 23.502 CR5232 (Rel-19, 'F'): Alignment of Subscription of UPF event via I-SMF | China Mobile | Rel-19 | Confirm Specification Number - CR states 23.501!. Confirm CR Number - CR states 5231! | ||
9.16.2 | S2-2500594 | CR | Approval | 23.502 CR5258 (Rel-18, 'F'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-18 | |||
9.16.2 | S2-2500595 | CR | Approval | 23.502 CR5259 (Rel-19, 'A'): Corrections for Group UE and Any UE cases | Huawei, HiSilicon | Rel-19 | |||
9.16.2 | S2-2500878 | CR | Approval | 23.502 CR5297 (Rel-18, 'F'): Clarification on subscription of UPF event via I-SMF | ZTE | Rel-18 | |||
9.16.2 | S2-2500879 | CR | Approval | 23.502 CR5298 (Rel-19, 'A'): Clarification on subscription of UPF event via I-SMF | ZTE | Rel-19 | |||
9.16.2 | S2-2501010 | CR | Approval | 23.502 CR5313 (Rel-18, 'F'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-18 | |||
9.16.2 | S2-2501011 | CR | Approval | 23.502 CR5314 (Rel-19, 'A'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-19 | Confirm Spec version used - CR states {18.8.0}! Check TEI19 WI Code, if a mirror CR! | ||
9.17.2 | - | - | - | Edge Computing Phase 2 (EDGE_Ph2) | - | - | Docs:=14 | - | |
9.17.2 | S2-2500225 | CR | Approval | 23.548 CR0272 (Rel-18, 'F'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-18 | |||
9.17.2 | S2-2500226 | CR | Approval | 23.548 CR0273 (Rel-19, 'A'): Clarification for policy and same private UE IP addresses issues in HR-SBO | Huawei, HiSilicon | Rel-19 | |||
9.17.2 | S2-2500273 | CR | Approval | 23.548 CR0276 (Rel-18, 'F'): Correction of DNS message handling rule | China Mobile | Rel-18 | |||
9.17.2 | S2-2500274 | CR | Approval | 23.548 CR0277 (Rel-19, 'A'): Correction of DNS message handling rule | China Mobile | Rel-19 | |||
9.17.2 | S2-2500496 | CR | Approval | 23.548 CR0285 (Rel-18, 'F'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-18 | |||
9.17.2 | S2-2500497 | CR | Approval | 23.548 CR0286 (Rel-19, 'A'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-19 | |||
9.17.2 | S2-2500498 | CR | Approval | 23.501 CR5965 (Rel-18, 'F'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-18 | |||
9.17.2 | S2-2500499 | CR | Approval | 23.501 CR5966 (Rel-19, 'A'): SMF failure notification to AF on simultaneous connectivity during edge relocation | Samsung | Rel-19 | |||
9.17.2 | S2-2500678 | CR | Approval | 23.548 CR0291 (Rel-18, 'F'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-18 | |||
9.17.2 | S2-2500679 | CR | Approval | 23.548 CR0292 (Rel-19, 'A'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-19 | |||
9.17.2 | S2-2500680 | CR | Approval | 23.502 CR5269 (Rel-18, 'F'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-18 | |||
9.17.2 | S2-2500681 | CR | Approval | 23.502 CR5270 (Rel-19, 'A'): AF triggered EAS rediscovery via HPLMN for HR-SBO | Huawei, HiSilicon | Rel-19 | |||
9.17.2 | S2-2501053 | CR | Approval | 23.502 CR5326 (Rel-18, 'F'): Correction on HR-SBO allowed indication and AF TI container transfer | Nokia | Rel-18 | |||
9.17.2 | S2-2501054 | CR | Approval | 23.502 CR5327 (Rel-19, 'A'): Correction on HR-SBO allowed indication and AF TI container transfer | Nokia | Rel-19 | |||
9.18.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | Docs:=0 | - | |
9.19.2 | - | - | - | Vehicle Mounted Relays (VMR) | - | - | Docs:=0 | - | |
9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) | - | - | Docs:=2 | - | |
9.20.2 | S2-2500740 | CR | Approval | 23.316 CR2147 (Rel-18, 'F'): R18 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon | Rel-18 | |||
9.20.2 | S2-2500741 | CR | Approval | 23.316 CR2148 (Rel-19, 'F'): R19 Correction on PCRT applicable for 5WWC | Huawei, HiSilicon | Rel-19 | |||
9.21 | - | - | - | Stage 2 of MPS_WLAN (MPS_WLAN) | - | - | Docs:=0 | - | |
9.22.2 | - | - | - | 5G AM Policy (AMP) | - | - | Docs:=0 | - | |
9.23.2 | - | - | - | Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | - | - | Docs:=4 | - | |
9.23.2 | S2-2500091 | CR | Approval | 23.288 CR1307 (Rel-18, 'F'): Correction on ML Model monitoring service operation | ZTE | Rel-18 | |||
9.23.2 | S2-2500092 | CR | Approval | 23.288 CR1308 (Rel-19, 'A'): Correction on ML Model monitoring service operation | ZTE | Rel-19 | |||
9.23.2 | S2-2500093 | CR | Approval | 23.288 CR1309 (Rel-18, 'F'): Implement agreed ML Model update parameter | ZTE | Rel-18 | |||
9.23.2 | S2-2500094 | CR | Approval | 23.288 CR1310 (Rel-19, 'A'): Implement agreed ML Model update parameter | ZTE | Rel-19 | |||
9.24.2 | - | - | - | Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | - | - | Docs:=0 | - | |
9.25.2 | - | - | - | Enhancement of 5G UE Policy (eUEPO) | - | - | Docs:=7 | - | |
9.25.2 | S2-2500181 | CR | Approval | 23.503 CR1314R3 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson | Rel-18 | Revision of S2-2409501 | ||
9.25.2 | S2-2500184 | CR | Approval | 23.503 CR1315R2 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.503 | Oracle, Verizon, Ericsson | Rel-19 | Revision of S2-2408923 | ||
9.25.2 | S2-2500234 | CR | Approval | 23.502 CR5214 (Rel-18, 'F'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-18 | |||
9.25.2 | S2-2500235 | CR | Approval | 23.502 CR5215 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-19 | Revised to S2-2500415 | Revised | |
9.25.2 | S2-2500415 | CR | Approval | 23.502 CR5215R1 (Rel-19, 'A'): Correction to Awareness of URSP Rule Enforcement 23.502 | Oracle, Verizon, Ericsson | Rel-19 | Revision of S2-2500235 | ||
9.25.2 | S2-2500562 | CR | Approval | 23.503 CR1481 (Rel-18, 'F'): URSP Guidelines updates of GSMA | Nokia | Rel-18 | |||
9.25.2 | S2-2500584 | CR | Approval | 23.503 CR1484 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | |||
9.26.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | Docs:=0 | - | |
9.27.2 | - | - | - | Extensions to the TSC Framework to support DetNet (DetNet) | - | - | Docs:=4 | - | |
9.27.2 | S2-2500421 | CR | Approval | 23.501 CR5949 (Rel-18, 'F'): Updated reference for DetNet RFC | Ericsson | Rel-18 | |||
9.27.2 | S2-2500422 | CR | Approval | 23.501 CR5950 (Rel-19, 'A'): Updated reference for DetNet RFC | Ericsson | Rel-19 | |||
9.27.2 | S2-2500423 | CR | Approval | 23.503 CR1473 (Rel-18, 'F'): Updated reference for DetNet RFC | Ericsson | Rel-18 | |||
9.27.2 | S2-2500424 | CR | Approval | 23.503 CR1474 (Rel-19, 'A'): Updated reference for DetNet RFC | Ericsson | Rel-19 | |||
9.28.2 | - | - | - | Seamless UE context recovery (SUECR) | - | - | Docs:=0 | - | |
9.29 | - | - | - | Multiple location report for MT-LR Immediate Location Request for regulatory services (TEI18_MLR) | - | - | Docs:=0 | - | |
9.30 | - | - | - | Secondary DN Authentication and authorization in EPC IWK cases (TEI18_SDNAEPC) | - | - | Docs:=0 | - | |
9.31 | - | - | - | MBS support for V2X services (TEI18_MBS4V2X) | - | - | Docs:=0 | - | |
9.32 | - | - | - | Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) | - | - | Docs:=0 | - | |
9.33 | - | - | - | Enhancement of application detection event exposure (TEI18_ADEE) | - | - | Docs:=0 | - | |
9.34 | - | - | - | General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) | - | - | Docs:=0 | - | |
9.35 | - | - | - | New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18_DCAMP_Ph2) | - | - | Docs:=0 | - | |
9.36 | - | - | - | Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | - | - | Docs:=0 | - | |
9.37 | - | - | - | Generic Rel-18 LSs | - | - | Docs:=0 | - | |
9.38 | - | - | - | Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=0 | - | |
19 | - | - | - | Rel-19 SIDs and WIDs | - | - | Docs:=0 | - | |
19.1.1 | - | - | - | Study on Integration of satellite components in the 5G architecture Phase III (FS_5GSAT_Ph3_ARCH) | - | - | Docs:=0 | - | |
19.1.2 | - | - | - | Integration of satellite components in the 5G architecture Phase III (5GSAT_Ph3-ARC) | - | - | Docs:=79 | - | |
19.1.2 | - | - | - | KI#2 Support of S&F satellite operation | - | - | Docs:=0 | - | |
19.1.2 | - | - | - | General LS | - | - | Docs:=6 | - | |
19.1.2 | S2-2500062 | LS In | Action | LS from SA WG3-LI: Reply LS on FS_5GSAT_Ph3_ARCH conclusions | SA WG3-LI (S3i240703) | Rel-19 | Response drafted in S2-2500760 | ||
19.1.2 | S2-2500019 | LS In | Action | LS from SA WG3-LI: Reply LS on FS_5GSAT_Ph3_ARCH conclusions | SA WG3-LI (S3i240703) | Rel-19 | Responses drafted in S2-2500506, S2-2501033 | ||
19.1.2 | S2-2500760 | LS OUT | Approval | [DRAFT] Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | China Telecommunications | Rel-19 | Response to S2-2500062 | ||
19.1.2 | S2-2500506 | LS OUT | Approval | [DRAFT] Reply LS to s3i240703 | Xiaomi | Rel-19 | Response to S2-2500019 | ||
19.1.2 | S2-2501033 | LS OUT | Approval | [DRAFT] Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | Samsung | Rel-19 | Revision of S2-2412294. Response to S2-2500019 | ||
19.1.2 | S2-2500761 | CR | Approval | 23.401 CR3865 (Rel-19, 'B'): New features in Split MME architecture to support requirement of SA WG3_LI | China Telecom | Rel-19 | |||
19.1.2 | - | - | - | Issue#2a: List of satellite ID and S&F monitoring list | - | - | Docs:=21 | - | |
19.1.2 | S2-2500979 | DISCUSSION | Discussion | On the purpose and criticality of the List of Satellite IDs and S&F Monitored List and proposal to specify separate lists. . | Sateliot, Thales, Novamint | Rel-19 | |||
19.1.2 | S2-2500780 | DISCUSSION | Approval | S&F Monitoring List and transition between S&F mode and normal mode | Huawei, HiSilicon | Rel-19 | |||
19.1.2 | S2-2501025 | DISCUSSION | Discussion | Discussion on List of satelliteID(s). | Samsung | Rel-19 | |||
19.1.2 | S2-2500136 | DISCUSSION | Approval | On the use of monitoring list and wait time for S&F. | Qualcomm Incorporated | Rel-19 | |||
19.1.2 | S2-2500972 | CR | Approval | 23.401 CR3874 (Rel-19, 'B'): Support for S&F Serving Satellite List and S&F Monitoring Satellite List | Sateliot, Novamint, Thales | Rel-19 | |||
19.1.2 | S2-2500782 | CR | Approval | 23.401 CR3867 (Rel-19, 'B'): Support of S&F Monitoring List in S&F Mode | Huawei, HiSilicon | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500525 | CR | Approval | 23.401 CR3852 (Rel-19, 'B'): Support of S&F Monitoring List | Nokia | Rel-19 | |||
19.1.2 | S2-2500548 | CR | Approval | 23.401 CR3853 (Rel-19, 'B'): Resolving an EN about List of satelliteID(s) and S&F Monitoring List | LG Electronics | Rel-19 | |||
19.1.2 | S2-2500723 | CR | Approval | 23.401 CR3858 (Rel-19, 'B'): S&F list handling for EN resolving | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500179 | CR | Approval | 23.401 CR3845 (Rel-19, 'B'): Update Introduction of Store and Forward feature in EPC | China Mobile | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500619 | CR | Approval | 23.401 CR3856 (Rel-19, 'B'): Support of S&F Monitoring list and S&F Wait Timer | OPPO | Rel-19 | |||
19.1.2 | S2-2500688 | CR | Approval | 23.401 CR3857 (Rel-19, 'B'): S&F monitoring list | Xiaomi | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500779 | CR | Approval | 23.401 CR3866 (Rel-19, 'B'): Handling of List of Satellite IDs for S&F satellite operation | CATT | Rel-19 | |||
19.1.2 | S2-2501028 | CR | Approval | 23.401 CR3877 (Rel-19, 'B'): Handling list of satellite IDs (Opt-2) | Samsung | Rel-19 | |||
19.1.2 | S2-2500728 | CR | Approval | 23.401 CR3863 (Rel-19, 'B'): Some clarifications on S&F timer and S&F list usage | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2501026 | CR | Approval | 23.401 CR3876 (Rel-19, 'B'): Handling list of satellite IDs (Opt-1) | Samsung | Rel-19 | |||
19.1.2 | S2-2500137 | CR | Approval | 23.401 CR3844 (Rel-19, 'B'): Support for S&F Monitoring List and Wait Timer | Qualcomm Incorporated | Rel-19 | Confirm CR Number - CR states 3804! | ||
19.1.2 | S2-2500726 | CR | Approval | 23.401 CR3861 (Rel-19, 'B'): Procedure updates for S&F | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500783 | CR | Approval | 23.401 CR3868 (Rel-19, 'B'): Procedure updates to support S&F Monitoring List | Huawei, HiSilicon | Rel-19 | |||
19.1.2 | S2-2500047 | LS In | Action | LS from RAN WG2: LS on Satellite IDs for store-and-forward operation | RAN WG2 (R2-2411197) | Rel-19 | Responses drafted in S2-2500138, S2-2500505, S2-2500538, S2-2500549, S2-2500634, S2-2500729, S2-2500781, S2-2500790, S2-2501035 | ||
19.1.2 | S2-2500790 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | CATT | Rel-19 | Response to S2-2500047 | ||
19.1.2 | - | - | - | Issue#2b: Expected UE and network behaviour for mode transition | - | - | Docs:=6 | - | |
19.1.2 | S2-2501041 | CR | Approval | 23.401 CR3881 (Rel-19, 'C'): Transition between S&F Mode and Normal Mode | Qualcomm Incorporated | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500446 | CR | Approval | 23.401 CR3831R2 (Rel-19, 'B'): UE determination for S&F mode operation or power saving | Rel-19 | Revision of S2-2412317 | |||
19.1.2 | S2-2500321 | CR | Approval | 23.401 CR3847 (Rel-19, 'B'): Applicability of the S&F Wait Timer | MediaTek Inc. | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500322 | CR | Approval | 23.401 CR3848 (Rel-19, 'B'): No Necessity to define UE in S&F mode | MediaTek Inc. | Rel-19 | |||
19.1.2 | S2-2500559 | CR | Approval | 23.401 CR3855 (Rel-19, 'F'): Transitioning between operation in S&F mode and normal mode | LG Electronics | Rel-19 | |||
19.1.2 | S2-2500724 | CR | Approval | 23.401 CR3859 (Rel-19, 'B'): UE and NW behaviour transition between SF and normal | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | - | - | - | Issue#2c: Support of Attach with PDN connection for Split MME option | - | - | Docs:=7 | - | |
19.1.2 | S2-2500551 | CR | Approval | 23.401 CR3854 (Rel-19, 'B'): Support of Attach with PDN connection for split MME architecture | LG Electronics | Rel-19 | |||
19.1.2 | S2-2500944 | CR | Approval | 23.401 CR3870 (Rel-19, 'C'): Support of attach with PDN connection in S&F mode of operation-option 1 | NEC | Rel-19 | |||
19.1.2 | S2-2500982 | CR | Approval | 23.401 CR3875 (Rel-19, 'B'): Description of procedures for split-MME architecture in informative annex | Sateliot, Novamint, Thales | Rel-19 | |||
19.1.2 | S2-2500248 | CR | Approval | 23.401 CR3846 (Rel-19, 'B'): Split MME handling of UE attach with PDN connection | Ericsson | Rel-19 | |||
19.1.2 | S2-2500784 | CR | Approval | 23.401 CR3869 (Rel-19, 'B'): Information about ESM procedures in Split MME S&F Example | Huawei, HiSilicon | Rel-19 | |||
19.1.2 | S2-2500945 | CR | Approval | 23.401 CR3871 (Rel-19, 'F'): Support of attach with PDN connection in S&F mode of operation-option 2 | NEC | Rel-19 | |||
19.1.2 | S2-2500725 | CR | Approval | 23.401 CR3860 (Rel-19, 'B'): PDN connection handling under S&F mode | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | - | - | - | Others | - | - | Docs:=10 | - | |
19.1.2 | S2-2500403 | CR | Approval | 23.401 CR3849 (Rel-19, 'F'): Terminology correction and clarification for Store and Forward Satellite Operation | Ericsson | Rel-19 | |||
19.1.2 | S2-2500758 | CR | Approval | 23.401 CR3864 (Rel-19, 'B'): Update on S&F Satellite Operation for UE and MME | China Telecom | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2501031 | CR | Approval | 23.401 CR3878 (Rel-19, 'F'): Location determination for S&F | Samsung | Rel-19 | |||
19.1.2 | S2-2501038 | CR | Approval | 23.401 CR3879 (Rel-19, 'F'): Clarifications related to S&F aspects | Samsung | Rel-19 | |||
19.1.2 | S2-2501040 | CR | Approval | 23.401 CR3880 (Rel-19, 'F'): UE Detach for S&F Mode Access | Qualcomm Incorporated | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500507 | CR | Approval | 23.401 CR3850 (Rel-19, 'F'): Clarification on timestamp processing and editoral modification | Xiaomi | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500947 | CR | Approval | 23.401 CR3872 (Rel-19, 'F'): Correction to the S&F procedure | NEC | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500508 | CR | Approval | 23.401 CR3851 (Rel-19, 'B'): Procedure update for Store and Forward operations | Xiaomi | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500727 | CR | Approval | 23.401 CR3862 (Rel-19, 'B'): Service request procedure update for S&F | Vivo | Rel-19 | WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500759 | CR | Approval | 23.401 CR3843R1 (Rel-19, 'B'): Update on procedures of PDN connection to support S&F Satellite Operation | China Telecom | Rel-19 | Revision of S2-2412239. WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | - | - | - | KI#3 Support of UE-satellite-UE communication | - | - | Docs:=0 | - | |
19.1.2 | - | - | - | Mobility support - IMS layer | - | - | Docs:=8 | - | |
19.1.2 | S2-2500718 | CR | Approval | 23.228 CR1561 (Rel-19, 'B'): Addition of mobility functionality for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia | Rel-19 | |||
19.1.2 | S2-2500716 | CR | Approval | 23.228 CR1521R6 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon | Rel-19 | Revision of S2-2412672 | ||
19.1.2 | S2-2500717 | CR | Approval | 23.228 CR1522R6 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | NTT DOCOMO, Nokia, vivo, Huawei, HiSilicon | Rel-19 | Revision of S2-2412673 | ||
19.1.2 | S2-2500627 | CR | Approval | 23.228 CR1521R4 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | China Mobile, China Telecom, [NTT DOCOMO, Nokia] | Rel-19 | Revision of S2-2412672. WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500628 | CR | Approval | 23.228 CR1522R4 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | China Mobile, China Telecom [NTT DOCOMO, Nokia] | Rel-19 | Revision of S2-2412673. WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500700 | CR | Approval | 23.228 CR1476R3 (Rel-19, 'B'): Functional descriptions of UE-satellite-UE communications when satellite changes | Vivo | Rel-19 | Revision of S2-2411888 | ||
19.1.2 | S2-2500767 | CR | Approval | 23.228 CR1521R7 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS continuation of optimized media routing | [NTT DOCOMO], vivo | Rel-19 | Revision of S2-2412672 | ||
19.1.2 | S2-2500768 | CR | Approval | 23.228 CR1522R7 (Rel-19, 'B'): Mobility procedure for UE-Satellite-UE communication in IMS ground fallback | [NTT DOCOMO], vivo | Rel-19 | Revision of S2-2412673 | ||
19.1.2 | - | - | - | Mobility support - 5GS | - | - | Docs:=1 | - | |
19.1.2 | S2-2500699 | CR | Approval | 23.501 CR5518R7 (Rel-19, 'B'): Support of UE-satellite-UE communications when serving satellite changes | Vivo, CSCN, Tencent, Honor, Thales, CATT, NTT DOCOMO, China Telecom | Rel-19 | Revision of S2-2412905 | ||
19.1.2 | - | - | - | Early media support - IMS layer | - | - | Docs:=2 | - | |
19.1.2 | S2-2500293 | CR | Approval | 23.228 CR1520R3 (Rel-19, 'B'): Call setup of UE-Satellite-UE communication with early media in IMS | Vivo, China Telecom | Rel-19 | Revision of S2-2412907 | ||
19.1.2 | S2-2500294 | CR | Approval | 23.228 CR1547 (Rel-19, 'B'): Call setup of UE-Satellite-UE communication with early media with two AGWs allocated | Vivo, China Telecom | Rel-19 | |||
19.1.2 | - | - | - | Update for UE-Satellite-UE communication | - | - | Docs:=4 | - | |
19.1.2 | S2-2500719 | CR | Approval | 23.228 CR1562 (Rel-19, 'B'): Clean-up of functionality at call setup for Support of UE-Satellite-UE communication in IMS | NTT DOCOMO, Nokia | Rel-19 | |||
19.1.2 | S2-2500785 | CR | Approval | 23.228 CR1564 (Rel-19, 'B'): Call setup update for UE-Satellite-UE communication in IMS with IMS-AGW on board | Huawei, HiSilicon, NTT DOCOMO, China Telecom, CATT | Rel-19 | |||
19.1.2 | S2-2500861 | CR | Approval | 23.502 CR5129R3 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, China Telecom, Samsung | Rel-19 | Revision of S2-2412675. Confirm CR Revision - CR states 32!. Confirm Spec version used - CR states {19.21.0}! WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | S2-2500864 | CR | Approval | 23.503 CR1429R3 (Rel-19, 'B'): Procedure update for UE-Satellite-UE communication | NTT DOCOMO, Samsung, China Telecom | Rel-19 | Revision of S2-2412676. Confirm CR Revision - CR states 32!. Confirm Spec version used - CR states {19.21.0}! WI Code should be 5GSAT_Ph3-ARC! | ||
19.1.2 | - | - | - | Above quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
19.1.2 | - | - | - | KI#2a: List of satellite ID and S&F monitoring list | - | - | Docs:=8 | - | |
19.1.2 | S2-2500138 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Qualcomm | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500505 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store and foward operation | Xiaomi | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500538 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Nokia | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500549 | LS OUT | Approval | [DRAFT] LS Reply on LS on Satellite IDs for store-and-forward operation | LG Electronics | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500634 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | OPPO | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500729 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | vivo | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2500781 | LS OUT | Approval | [DRAFT] Reply to LS on Satellite IDs for store-and-forward operation | Huawei, HiSilicon | Rel-19 | Response to S2-2500047 | ||
19.1.2 | S2-2501035 | LS OUT | Approval | [DRAFT] Reply LS on Satellite IDs for store-and-forward operation | Samsung | Rel-19 | Response to S2-2500047 | ||
19.1.2 | - | - | - | KI#2c: Attach w/ PDN connection for Split MME | - | - | Docs:=1 | - | |
19.1.2 | S2-2500942 | DISCUSSION | Discussion | Discussion paper attach procedure with default PDN connection. | NEC | Rel-19 | |||
19.1.2 | - | - | - | KI#2: Others | - | - | Docs:=2 | - | |
19.1.2 | S2-2500757 | DISCUSSION | Agreement | Discussion on the enhanced discontinuous network coverage for satellite access under S&F mode. | China Telecom | Rel-19 | |||
19.1.2 | S2-2501030 | DISCUSSION | Discussion | Discussion on location determination for Full EPC onboard. | Samsung | Rel-19 | |||
19.1.2 | - | - | - | KI#3:Mobility support - IMS layer | - | - | Docs:=1 | - | |
19.1.2 | S2-2500715 | DISCUSSION | Discussion | Discussion on whether IMS AS or P-CSCF initiates SIP re-INVITE. | NTT DOCOMO, Nokia | Rel-19 | |||
19.1.2 | - | - | - | KI#1: Support of regenerative payload satellite access | - | - | Docs:=2 | - | |
19.1.2 | S2-2500247 | CR | Approval | 23.501 CR5908 (Rel-19, 'F'): AMF selection for regenerative payload | Ericsson | Rel-19 | |||
19.1.2 | S2-2500618 | CR | Approval | 23.502 CR4994R3 (Rel-19, 'B'): Support of Regenerative Payload with NG-RAN Node Onboard Satellite | OPPO, Huawei, HiSilicon | Rel-19 | Revision of S2-2411702 | ||
19.2.1 | - | - | - | Study on system architecture for next generation real time communication services phase 2 (FS_NG_RTC_Ph2) | - | - | Docs:=0 | - | |
19.2.2 | - | - | - | System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2) | - | - | Docs:=52 | - | |
19.2.2 | - | - | - | KI#8: IMS avatar communication | - | - | Docs:=10 | - | |
19.2.2 | S2-2500079 | LS In | Information | LS from SA WG3: LS on IMS support for AF authorization and IMS avatar communication | SA WG3 (S3-250170) | ||||
19.2.2 | S2-2500169 | CR | Approval | 23.228 CR1531 (Rel-19, 'C'): Resolving ENs on Avatar communication | Qualcomm Incorporated | Rel-19 | |||
19.2.2 | S2-2500205 | CR | Approval | 23.228 CR1537 (Rel-19, 'F'): KI#8: Update to Architecture for avatar communications | Ericsson | Rel-19 | |||
19.2.2 | S2-2500206 | CR | Approval | 23.228 CR1538 (Rel-19, 'F'): KI#8: Update to Avatar Procedures | Ericsson | Rel-19 | |||
19.2.2 | S2-2500635 | CR | Approval | 23.228 CR1554 (Rel-19, 'B'): Address EN on Avatar Representation | ZTE | Rel-19 | |||
19.2.2 | S2-2500794 | CR | Approval | 23.228 CR1565 (Rel-19, 'B'): KI#8: EN resolutions for Avatar communication | Samsung | Rel-19 | |||
19.2.2 | S2-2500636 | CR | Approval | 23.228 CR1555 (Rel-19, 'B'): Address EN in UE Centric Avatar Communication Procedure | ZTE | Rel-19 | |||
19.2.2 | S2-2500821 | CR | Approval | 23.228 CR1567 (Rel-19, 'B'): Update procedure of Avatar Communication | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | S2-2500772 | CR | Approval | 23.228 CR1563 (Rel-19, 'B'): Clarification on how DCSF fetch DC AS URL if not pre-configured | China Mobile | Rel-19 | |||
19.2.2 | S2-2501013 | CR | Approval | 23.228 CR1580 (Rel-19, 'F'): KI#8: Download of Avatar ID List | Nokia | Rel-19 | |||
19.2.2 | - | - | - | KI#7: Multiplex of DC apps over one SCTP conn | - | - | Docs:=6 | - | |
19.2.2 | S2-2500289 | DISCUSSION | Information | Multiplexing with duplicated stream ID. | Vivo | ||||
19.2.2 | S2-2500290 | CR | Approval | 23.228 CR1545 (Rel-19, 'B'): De-multiplexing ADC in case same stream ID used by both UEs | Vivo | Rel-19 | |||
19.2.2 | S2-2500624 | CR | Approval | 23.228 CR1552 (Rel-19, 'B'): Updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile | Rel-19 | |||
19.2.2 | S2-2500625 | CR | Approval | 23.228 CR1512R2 (Rel-19, 'B'): Service updates to support multiplexing multiple DC applications over single SCTP connection | China Mobile | Rel-19 | Revision of S2-2411609 | ||
19.2.2 | S2-2500796 | CR | Approval | 23.228 CR1566 (Rel-19, 'B'): KI#7: Services for supporting multiplexing | Samsung | Rel-19 | |||
19.2.2 | S2-2500820 | LS OUT | Approval | [DRAFT] LS on IMS DC multiplexing | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | - | - | - | KI#2: IMS capability exposure for IMS DC | - | - | Docs:=14 | - | |
19.2.2 | S2-2500170 | CR | Approval | 23.228 CR1532 (Rel-19, 'F'): Correction on IMS data channel capability exposure | Qualcomm Incorporated | Rel-19 | |||
19.2.2 | S2-2500209 | CR | Approval | 23.228 CR1541 (Rel-19, 'C'): KI#2: Update to Network Capability Exposure Procedures | Ericsson | Rel-19 | |||
19.2.2 | S2-2500210 | CR | Approval | 23.228 CR1542 (Rel-19, 'F'): KI#2: Udpdate to IMS AS Session Management Services | Ericsson | Rel-19 | |||
19.2.2 | S2-2500288 | CR | Approval | 23.228 CR1544 (Rel-19, 'F'): Adding more event filters for ADC media type | Vivo | Rel-19 | |||
19.2.2 | S2-2500620 | CR | Approval | 23.228 CR1548 (Rel-19, 'B'): Correction of detection criteria for event exposure | China Mobile | Rel-19 | |||
19.2.2 | S2-2500621 | CR | Approval | 23.228 CR1549 (Rel-19, 'B'): Updates to IMS data channel capability exposure procedures | China Mobile | Rel-19 | |||
19.2.2 | S2-2500622 | CR | Approval | 23.228 CR1550 (Rel-19, 'B'): Updates to Nimsas_ImsSessionManagement Service | China Mobile | Rel-19 | |||
19.2.2 | S2-2500639 | CR | Approval | 23.228 CR1558 (Rel-19, 'B'): Clarification on DC Capability Exposure Procedure | ZTE | Rel-19 | |||
19.2.2 | S2-2500823 | CR | Approval | 23.228 CR1568 (Rel-19, 'B'): Update Network Capability Exposure Procedure | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | S2-2500950 | CR | Approval | 23.228 CR1576 (Rel-19, 'F'): HSS handling for subscription with IMS | Samsung | Rel-19 | |||
19.2.2 | S2-2500967 | CR | Approval | 23.228 CR1578 (Rel-19, 'B'): Complete the details for KI#2 | NTT DOCOMO | Rel-19 | |||
19.2.2 | S2-2500971 | CR | Approval | 23.502 CR5311 (Rel-19, 'B'): Complete the details for KI#2 | NTT DOCOMO | Rel-19 | |||
19.2.2 | S2-2501014 | CR | Approval | 23.228 CR1581 (Rel-19, 'F'): KI#2: Update of procedures | Nokia | Rel-19 | |||
19.2.2 | S2-2501015 | CR | Approval | 23.502 CR5315 (Rel-19, 'F'): KI#2: Update the IMS session management service of NEF | Nokia | Rel-19 | |||
19.2.2 | - | - | - | KI#5: PS Data Off for services over IMS DC | - | - | Docs:=4 | - | |
19.2.2 | S2-2500171 | CR | Approval | 23.228 CR1533 (Rel-19, 'F'): Clarification on PS Data Off status change reporting to DCSF | Qualcomm Incorporated | Rel-19 | |||
19.2.2 | S2-2500626 | CR | Approval | 23.228 CR1553 (Rel-19, 'B'): KI#5: Support of Data off feature for data channel | China Mobile | Rel-19 | |||
19.2.2 | S2-2500637 | CR | Approval | 23.228 CR1556 (Rel-19, 'B'): Address EN on 3GPP PS Data Off Status Notification | ZTE | Rel-19 | |||
19.2.2 | S2-2500946 | CR | Approval | 23.228 CR1574 (Rel-19, 'F'): 3GPP PS Data off status for DCSF | Samsung | Rel-19 | |||
19.2.2 | - | - | - | Not in scope of e-meeting | - | - | Docs:=0 | - | |
19.2.2 | - | - | - | KI#7: Multiplex of DC apps over one SCTP conn | - | - | Docs:=1 | - | |
19.2.2 | S2-2500883 | CR | Approval | 23.228 CR1572 (Rel-19, 'F'): Correction on DC multiplexing procedures | China Mobile | Rel-19 | |||
19.2.2 | - | - | - | KI#2: IMS capability exposure for IMS DC | - | - | Docs:=1 | - | |
19.2.2 | S2-2500208 | CR | Approval | 23.228 CR1540 (Rel-19, 'F'): KI#2: Generalizing Information Retrieval | Ericsson | Rel-19 | |||
19.2.2 | - | - | - | KI#5: PS Data Off for services over IMS DC | - | - | Docs:=1 | - | |
19.2.2 | S2-2500824 | CR | Approval | 23.228 CR1569 (Rel-19, 'B'): KI#5: Support of Data off feature for data channel | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | - | - | - | General | - | - | Docs:=4 | - | |
19.2.2 | S2-2500065 | LS In | Action | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 (S4-242111) | Rel-19 | |||
19.2.2 | S2-2500287 | CR | Approval | 23.228 CR1543 (Rel-19, 'D'): Abbreviations of ADC and BDC | Vivo | Rel-19 | |||
19.2.2 | S2-2500638 | CR | Approval | 23.228 CR1557 (Rel-19, 'B'): Clarification on DC Application Server | ZTE | Rel-19 | |||
19.2.2 | S2-2500895 | CR | Approval | 23.228 CR1573 (Rel-19, 'F'): Update IMS DC figures to align with other annex | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | - | - | - | KI#4: Authorization and authentication of third-party identities in IMS sessions | - | - | Docs:=3 | - | |
19.2.2 | S2-2500173 | CR | Approval | 23.228 CR1534 (Rel-19, 'F'): Clarification on third-party user ID provisioning procedure | Qualcomm Incorporated | Rel-19 | |||
19.2.2 | S2-2500949 | CR | Approval | 23.228 CR1575 (Rel-19, 'F'): Clarification on Third Party identity verification | Samsung | Rel-19 | |||
19.2.2 | S2-2501012 | CR | Approval | 23.228 CR1579 (Rel-19, 'F'): KI#4: Update of procedure description | Nokia | Rel-19 | |||
19.2.2 | - | - | - | KI#1: IMS events for DC communication | - | - | Docs:=2 | - | |
19.2.2 | S2-2500203 | CR | Approval | 23.228 CR1536 (Rel-19, 'F'): KI#1: Editorial updates to IMS Subscribe/Notify Framework Architecture | Ericsson | Rel-19 | |||
19.2.2 | S2-2500204 | CR | Approval | 23.502 CR5209 (Rel-19, 'F'): KI#1: Update to NEF Services | Ericsson | Rel-19 | |||
19.2.2 | - | - | - | KI#3: Data channel interworking with MTSI UE | - | - | Docs:=2 | - | |
19.2.2 | S2-2500207 | CR | Approval | 23.228 CR1539 (Rel-19, 'F'): KI#3: Update to DC interworking with MTSI UE | Ericsson | Rel-19 | |||
19.2.2 | S2-2500291 | CR | Approval | 23.228 CR1465R2 (Rel-19, 'F'): Update on support of DC interworking | Vivo | Rel-19 | Revision of S2-2411943 | ||
19.2.2 | - | - | - | KI#6: Standalone IMS DC sessions | - | - | Docs:=4 | - | |
19.2.2 | S2-2500292 | CR | Approval | 23.228 CR1546 (Rel-19, 'D'): Modification on general description for standalone IMS DC session | Vivo | Rel-19 | |||
19.2.2 | S2-2500623 | CR | Approval | 23.228 CR1551 (Rel-19, 'B'): Updates on procedure and service of DC interworking via DC AS | China Mobile | Rel-19 | |||
19.2.2 | S2-2500825 | CR | Approval | 23.228 CR1570 (Rel-19, 'F'): Correction on standalone data channel description | Huawei, HiSilicon | Rel-19 | |||
19.2.2 | S2-2500951 | CR | Approval | 23.228 CR1577 (Rel-19, 'F'): MMTel media removal clarification | Samsung | Rel-19 | |||
19.3.1 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (FS_XRM_Ph2) | - | - | Docs:=0 | - | |
19.3.2 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2) | - | - | Docs:=121 | - | |
19.3.2 | - | - | - | LSs - Transport level marking based on PSI | - | - | Docs:=1 | - | |
19.3.2 | - | - | - | LSs - Transport level marking based on PSI | - | - | Docs:=1 | - | |
19.3.2 | S2-2500027 | LS In | Action | LS from CT WG4: Reply LS on Transport level marking based on PDU Set Importance | CT WG4 (C4-245408) | Rel-19 | |||
19.3.2 | - | - | - | LSs - Roaming scenarios | - | - | Docs:=4 | - | |
19.3.2 | S2-2500011 | LS In | Action | LS from CT WG4: LS on Support of XRM services in Roaming scenarios | CT WG4 (C4-244534) | Rel-19 | Responses drafted in S2-2500127, S2-2500167, S2-2500380 | ||
19.3.2 | S2-2500127 | LS OUT | Approval | [DRAFT] LS Reply on support of XRM services in Roaming scenarios | Nokia | Rel-18 | Response to S2-2500011 | ||
19.3.2 | S2-2500125 | CR | Approval | 23.501 CR5890 (Rel-18, 'F'): XRM services support in Roaming scenarios | Nokia | Rel-18 | |||
19.3.2 | S2-2500126 | CR | Approval | 23.501 CR5891 (Rel-19, 'A'): XRM services support in Roaming scenarios-Mirror | Nokia | Rel-19 | |||
19.3.2 | - | - | - | LSs - Multiplexed Media Flows | - | - | Docs:=1 | - | |
19.3.2 | S2-2500023 | LS In | Action | LS from SA WG4: Reply LS on Introduction of Extensions to IP Packet Filters for Differentiated QoS Handling for Multiplexed Media Flows | SA WG4 (S4-242065) | Rel-19 | |||
19.3.2 | - | - | - | LSs - Multimodality | - | - | Docs:=11 | - | |
19.3.2 | S2-2500014 | LS In | Action | LS from RAN WG2: Reply to SA2 LS on multi-modality awareness | RAN WG2 (R2-2409272) | Rel-19 | Responses drafted in S2-2500124, S2-2500162, S2-2500297, S2-2500752 | ||
19.3.2 | S2-2500015 | LS In | Action | LS from RAN WG3: Reply LS on multi-modality awareness at RAN | RAN WG3 (R3-245682) | Rel-19 | |||
19.3.2 | S2-2500028 | LS In | Information | LS from SA WG4: LS Reply on multi-modality awareness | SA WG4 (S4-242223) | Rel-19 | |||
19.3.2 | S2-2500050 | LS In | Action | LS from RAN WG3: Reply LS on multi-modality awareness | RAN WG3 (R3-247874) | Rel-19 | Response drafted in S2-2500540 | ||
19.3.2 | S2-2500074 | LS In | Action | LS from TSG SA: LS on multi-modality awareness | TSG SA (SP-241921) | Rel-19 | Responses drafted in S2-2500158, S2-2500447 | ||
19.3.2 | S2-2500162 | LS OUT | Approval | [DRAFT] Reply LS on multi-modality awareness | Qualcomm | Rel-19 | Response to S2-2500014 | ||
19.3.2 | S2-2500159 | CR | Approval | 23.501 CR5893 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | |||
19.3.2 | S2-2500166 | CR | Approval | 23.503 CR1457 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile | Rel-19 | |||
19.3.2 | S2-2500262 | CR | Approval | 23.502 CR5225 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! | ||
19.3.2 | S2-2500442 | DISCUSSION | Discussion | Discussion on providing multi-modal awareness to NG-RAN. | InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2500487 | DISCUSSION | Discussion | Discussion and proposals on multi-modal service awareness. | Samsung | ||||
19.3.2 | - | - | - | KI#1: PDU Set based QoS handling enhancement | - | - | Docs:=10 | - | |
19.3.2 | S2-2500116 | CR | Approval | 23.503 CR1441R3 (Rel-19, 'B'): PDU Set support in QoS Notification Control and Alternative QoS | Nokia | Rel-19 | Revision of S2-2412652 | ||
19.3.2 | S2-2500307 | CR | Approval | 23.503 CR1465 (Rel-19, 'B'): KI#1, Support QoS Notification and AQP | Vivo | Rel-19 | |||
19.3.2 | S2-2500899 | CR | Approval | 23.503 CR1417R2 (Rel-19, 'B'): Notification Control when PDU Set QoS parameters are available | Huawei, HiSilicon | Rel-19 | Revision of S2-2411914 | ||
19.3.2 | S2-2501009 | CR | Approval | 23.503 CR1441R4 (Rel-19, 'B'): PDU Set support in QoS Notification Control and Alternative QoS | [Nokia], Xiaomi | Rel-19 | Revision of S2-2412652 | ||
19.3.2 | S2-2500706 | CR | Approval | 23.501 CR5524R6 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | CATT, Nokia, Tencent, vivo, Samsung, Xiaomi | Rel-19 | Revision of S2-2412895 | ||
19.3.2 | S2-2500115 | CR | Approval | 23.501 CR5886 (Rel-19, 'B'): Suppport indication of PDU Set QoS in Notification Control | Nokia | Rel-19 | |||
19.3.2 | S2-2500306 | CR | Approval | 23.501 CR5920 (Rel-19, 'B'): KI#1, Support QoS Notification and AQP | Vivo | Rel-19 | |||
19.3.2 | S2-2500898 | CR | Approval | 23.501 CR5524R7 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | Huawei, HiSilicon [, CATT, Nokia, Tencent, vivo, Samsung, Xiaomi] | Rel-19 | Revision of S2-2412895 | ||
19.3.2 | S2-2501008 | CR | Approval | 23.501 CR5524R8 (Rel-19, 'B'): Support Alternative QoS profile with PDU Set QoS and Notification Control | [CATT, Nokia, Tencent, vivo, Samsung,] Xiaomi | Rel-19 | Revision of S2-2412895 | ||
19.3.2 | S2-2501003 | DISCUSSION | Approval | Discussion on one direction PDU Set support in Alternative QoS Profile . | Xiaomi | Rel-19 | |||
19.3.2 | - | - | - | KI#2: Support for end-to-end encrypted traffic | - | - | Docs:=9 | - | |
19.3.2 | S2-2500183 | CR | Approval | 23.502 CR5081R5 (Rel-19, 'B'): Procedures for handling end-to-end encrypted XRM flows | Google, Futurewei, InterDigital Inc., China Mobile, Huawei, HiSilicon, Ericsson, Nokia | Rel-19 | Revision of S2-2412657 | ||
19.3.2 | S2-2500224 | CR | Approval | 23.502 CR5213 (Rel-19, 'B'): Nnrf_NFDiscovery service enchancement for MoQ relay discovery | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | S2-2500295 | CR | Approval | 23.502 CR5027R2 (Rel-19, 'B'): Procedure of MoQ-based PDU Set Information identification for encrypted traffic | China Mobile | Rel-19 | Revision of S2-2411413 | ||
19.3.2 | S2-2500296 | CR | Approval | 23.501 CR5917 (Rel-19, 'F'): Corrections for KI#2 Support of transferring media related information over N6 | China Mobile | Rel-19 | |||
19.3.2 | S2-2500223 | CR | Approval | 23.501 CR5903 (Rel-19, 'F'): Clarifications for KI#2 | Huawei, Hisilicon | Rel-19 | |||
19.3.2 | S2-2500431 | CR | Approval | 23.501 CR5951 (Rel-19, 'F'): Correcting a Reference | InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2501005 | CR | Approval | 23.501 CR6051 (Rel-19, 'F'): XRM_Ph2_References corrections in Clause 5.37.9 | Xiaomi | Rel-19 | |||
19.3.2 | S2-2500405 | CR | Approval | 23.501 CR5940 (Rel-19, 'F'): Reference and editorial corrections to TS 23.501 | Ericsson | Rel-19 | |||
19.3.2 | S2-2500406 | CR | Approval | 23.503 CR1394R4 (Rel-19, 'B'): PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - PCC part | Ericsson [, InterDigital] | Rel-19 | Revision of S2-2412658 | ||
19.3.2 | - | - | - | KI#3: DSCP marking over N3/N9 | - | - | Docs:=2 | - | |
19.3.2 | S2-2500909 | CR | Approval | 23.501 CR6035 (Rel-19, 'B'): Addressing differences in PDU Set importance usage for DSCP marking over N3/N9 in the transport network | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | S2-2501004 | CR | Approval | 23.501 CR6050 (Rel-19, 'B'): XRM_Ph2_KI3 Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network | Intel, InterDigital Inc, China Telecom, Nokia, Tencent, Xiaomi | Rel-19 | |||
19.3.2 | - | - | - | KI#4: Traffic detections/QoS flow mapping for multiplexed data flows | - | - | Docs:=11 | - | |
19.3.2 | S2-2500410 | CR | Approval | 23.501 CR5942 (Rel-19, 'B'): KI#4 EN removal | Ericsson | Rel-19 | |||
19.3.2 | S2-2500458 | CR | Approval | 23.501 CR5958 (Rel-19, 'F'): KI#4: Correct the RTCP MID for IP packet filter set | China Mobile, Lenovo | Rel-19 | |||
19.3.2 | S2-2500650 | CR | Approval | 23.503 CR1388R4 (Rel-19, 'B'): Traffic detection and QoS handling of multiplexed data flows | OPPO, Xiaomi, Lenovo, [Ericsson, Huawei, HiSilicon, Samsung,Nokia, NTT DOCOMO, vivo] | Rel-19 | Revision of S2-2412660 | ||
19.3.2 | S2-2501036 | CR | Approval | 23.503 CR1388R6 (Rel-19, 'B'): KI#4: Clarify the ambiguity of QoS requirements of media-flow vs. data-flow | [OPPO, Ericsson(?), Huawei(?), HiSilicon(?), Samsung, Nokia, NTT DOCOMO, Xiaomi, vivo, Lenovo], China Mobile | Rel-19 | Revision of S2-2412660. Confirm Sources! | ||
19.3.2 | S2-2500703 | CR | Approval | 23.502 CR4927R5 (Rel-19, 'B'): Support multiplexing media traffic with additional Packet Filter | CATT, Nokia, OPPO, Lenovo, Samsung, Xiaomi | Rel-19 | Revision of S2-2412661 | ||
19.3.2 | S2-2500904 | CR | Approval | 23.503 CR1497 (Rel-19, 'B'): Event triggers related to QoS handling of multiplexed data flows | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | S2-2500957 | CR | Approval | 23.501 CR6042 (Rel-19, 'B'): Support Differentiated QoS handling for encrypted multiplexed media flows | Nokia, NTT DOCOMO | Rel-19 | |||
19.3.2 | S2-2500308 | CR | Approval | 23.501 CR5921 (Rel-19, 'B'): Support of DL Multiplexed Media Identification Information for end-to-end ciphered traffic | Vivo | Rel-19 | |||
19.3.2 | S2-2500999 | CR | Approval | 23.503 CR1388R5 (Rel-19, 'B'): Traffic detection and QoS handling of multiplexed data flows | [OPPO, Ericsson, Huawei, HiSilicon, Samsung], NTT DOCOMO, Nokia, [Xiaomi, vivo, Lemovo] | Rel-19 | Revision of S2-2412660 | ||
19.3.2 | S2-2500350 | DISCUSSION | Discussion | Discussion on Multiplexed Media Identification Information for end-to-end ciphered traffic. | Vivo | Rel-19 | |||
19.3.2 | S2-2500409 | DISCUSSION | Agreement | Solving KI#4 with N6 metadata using KI#2 mechanisms . | Ericsson | ||||
19.3.2 | - | - | - | KI#5: QoS handling in case of dynamic traffic characteristics | - | - | Docs:=6 | - | |
19.3.2 | S2-2500309 | CR | Approval | 23.501 CR5922 (Rel-19, 'F'): KI#5, Update to data burst related | Vivo | Rel-19 | |||
19.3.2 | S2-2500848 | CR | Approval | 23.501 CR5651R6 (Rel-19, 'B'): 23.501 Data boosting triggered by AS/AF | Lenovo, Tencent, Tencent Cloud, CATT, China Telecom, Meta USA, CMCC, Xiaomi, Samsung, Huawei, HiSilicon, Ericsson, Nokia | Rel-19 | Revision of S2-2412944 | ||
19.3.2 | S2-2500849 | CR | Approval | 23.502 CR5015R4 (Rel-19, 'B'): 23.502 Data boosting triggered by AS | Lenovo, Tencent, Tencent Cloud,CATT, China Telecom, Meta USA | Rel-19 | Revision of S2-2412712 | ||
19.3.2 | S2-2500958 | CR | Approval | 23.503 CR1448R3 (Rel-19, 'B'): Enhancements for AF/AS triggered expedite data transfer | Nokia, [Xiaomi, Tencent, Tencent Cloud], InterDigital Inc. | Rel-19 | Revision of S2-2412713 | ||
19.3.2 | S2-2500961 | CR | Approval | 23.502 CR5310 (Rel-19, 'F'): Support Time to Next Burst provisioning to NG-RAN | Nokia | Rel-19 | |||
19.3.2 | S2-2500847 | DISCUSSION | Information | Discussion on the remaining issues of expedited data transfer scheme. | Lenovo, Tencent, Tencent Cloud, Ericsson | Rel-19 | |||
19.3.2 | - | - | - | KI#9: Information exposure - rate limitation | - | - | Docs:=5 | - | |
19.3.2 | S2-2500310 | CR | Approval | 23.503 CR1381R4 (Rel-19, 'B'): KI#9, Support of Rate limitation | Vivo, Meta USA, Tencent, Nokia | Rel-19 | Revision of S2-2412718 | ||
19.3.2 | S2-2500407 | CR | Approval | 23.501 CR5941 (Rel-19, 'B'): Exposure of rate limitation information | Ericsson | Rel-19 | |||
19.3.2 | S2-2500408 | CR | Approval | 23.503 CR1470 (Rel-19, 'B'): Exposure of rate limitation information | Ericsson | Rel-19 | |||
19.3.2 | S2-2500537 | CR | Approval | 23.501 CR5867R6 (Rel-19, 'B'): KI#9, Support of Rate limitation | Tencent, Tencent Cloud, vivo, Lenovo, CMCC, Nokia, Meta | Rel-19 | Revision of S2-2412951 | ||
19.3.2 | S2-2500959 | CR | Approval | 23.501 CR5867R7 (Rel-19, 'B'): KI#9, Support of Rate limitation | [Tencent, Tencent Cloud, vivo, Lenovo, CMCC], Nokia, [Meta] | Rel-19 | Revision of S2-2412951 | ||
19.3.2 | - | - | - | KI#6: L4S for N3GPPA | - | - | Docs:=1 | - | |
19.3.2 | S2-2500471 | CR | Approval | 23.316 CR2143 (Rel-19, 'F'): L4S support in wireline access | Samsung | Rel-19 | |||
19.3.2 | - | - | - | Exceeding quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
19.3.2 | - | - | - | LSs - Roaming scenarios | - | - | Docs:=2 | - | |
19.3.2 | S2-2500167 | LS OUT | Approval | [DRAFT] Reply LS on Support of XRM services in Roaming scenarios | Qualcomm | Rel-19 | Response to S2-2500011 | ||
19.3.2 | S2-2500380 | LS OUT | Approval | [DRAFT] LS reply on Support of XRM services in Roaming scenarios | China Mobile | Rel-19 | Response to S2-2500011 | ||
19.3.2 | - | - | - | LS: Multimodality | - | - | Docs:=33 | - | |
19.3.2 | S2-2500124 | LS OUT | Approval | [DRAFT] LS Reply on multi-modality awareness at RAN | Nokia | Rel-19 | Response to S2-2500014 | ||
19.3.2 | S2-2500158 | LS OUT | Approval | [DRAFT] LS reply on multi-modality awareness | ZTE | Rel-19 | Response to S2-2500074 | ||
19.3.2 | S2-2500297 | LS OUT | Approval | [DRAFT] Reply to LS on multi-modality awareness | China Mobile | Rel-19 | Revision of S2-2412650. Response to S2-2500014 | ||
19.3.2 | S2-2500447 | LS OUT | Approval | [DRAFT] LS on multi-modality awareness | InterDigital Inc. | Rel-19 | Response to S2-2500074 | ||
19.3.2 | S2-2500540 | LS OUT | Approval | [DRAFT] LS Reply on multi-modality awareness | Samsung | Rel-19 | Response to S2-2500050 | ||
19.3.2 | S2-2500752 | LS OUT | Approval | [DRAFT] LS on Multi-Modality awareness | Sony | Rel-19 | Response to S2-2500014 | ||
19.3.2 | S2-2500097 | CR | Approval | 23.501 CR5883 (Rel-19, 'B'): Optimization on Multi-modal service | ZTE | Rel-19 | |||
19.3.2 | S2-2500098 | CR | Approval | 23.503 CR1453 (Rel-19, 'B'): Optimization on Multi-modal service | ZTE | Rel-19 | |||
19.3.2 | S2-2500160 | CR | Approval | 23.502 CR5203 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | |||
19.3.2 | S2-2500161 | CR | Approval | 23.503 CR1456 (Rel-19, 'B'): Joint admission control for multi-modal services | Qualcomm, Nokia | Rel-19 | |||
19.3.2 | S2-2500164 | CR | Approval | 23.501 CR5819R1 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile, Xiaomi | Rel-19 | Revision of S2-2411417 | ||
19.3.2 | S2-2500165 | CR | Approval | 23.502 CR5204 (Rel-19, 'B'): Support of providing MMSID from 5GC to NG-RAN through NGAP | China Mobile | Rel-19 | |||
19.3.2 | S2-2500261 | CR | Approval | 23.501 CR5910 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! | ||
19.3.2 | S2-2500263 | CR | Approval | 23.503 CR1464 (Rel-19, 'B'): Support of multi-modal awareness at NG-RAN | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! | ||
19.3.2 | S2-2500298 | CR | Approval | 23.502 CR5236 (Rel-19, 'B'): 23.502 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | |||
19.3.2 | S2-2500299 | CR | Approval | 23.501 CR5839R1 (Rel-19, 'B'): 23.501 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | Revision of S2-2411755 | ||
19.3.2 | S2-2500300 | CR | Approval | 23.503 CR1434R1 (Rel-19, 'B'): 23.503 Support of sending MMSID from CN to the RAN | Lenovo | Rel-19 | Revision of S2-2411756 | ||
19.3.2 | S2-2500311 | CR | Approval | 23.501 CR5923 (Rel-19, 'B'): Support of multi-modality awareness | Vivo | Rel-19 | |||
19.3.2 | S2-2500312 | CR | Approval | 23.503 CR1466 (Rel-19, 'B'): Support of multi-modality awareness | Vivo | Rel-19 | |||
19.3.2 | S2-2500443 | CR | Approval | 23.501 CR5952 (Rel-19, 'B'): 23.501 CR5952: Providing Multi-Modal Awareness to NG-RAN | InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2500445 | CR | Approval | 23.503 CR1475 (Rel-19, 'B'): Providing Multi-Modal Awareness to NG-RAN | InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2500523 | CR | Approval | 23.501 CR5847R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411891 | ||
19.3.2 | S2-2500524 | CR | Approval | 23.502 CR5164R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411923 | ||
19.3.2 | S2-2500526 | CR | Approval | 23.503 CR1439R1 (Rel-19, 'B'): Joint admission control for multi-modal QoS flows | Samsung | Rel-19 | Revision of S2-2411953 | ||
19.3.2 | S2-2500544 | CR | Approval | 23.501 CR5973 (Rel-19, 'B'): MMS ID to support Multi-modality awareness at RAN | LG Electronics | Rel-19 | |||
19.3.2 | S2-2500651 | CR | Approval | 23.501 CR5857R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412017 | ||
19.3.2 | S2-2500652 | CR | Approval | 23.502 CR5170R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412018 | ||
19.3.2 | S2-2500653 | CR | Approval | 23.503 CR1443R1 (Rel-19, 'B'): Multi-modality awareness at RAN | OPPO | Rel-19 | Revision of S2-2412019 | ||
19.3.2 | S2-2500744 | CR | Approval | 23.501 CR5994 (Rel-19, 'B'): Multi-modality awareness | Sony | Rel-19 | |||
19.3.2 | S2-2500746 | CR | Approval | 23.503 CR1488 (Rel-19, 'B'): Multi-modality awareness | Sony | Rel-19 | |||
19.3.2 | S2-2500900 | CR | Approval | 23.501 CR5848R1 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | Revision of S2-2411920 | ||
19.3.2 | S2-2500901 | CR | Approval | 23.502 CR5302 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | S2-2500902 | CR | Approval | 23.503 CR1436R1 (Rel-19, 'B'): Provision of the MMSID for NG-RAN | Huawei, HiSilicon | Rel-19 | Revision of S2-2411921 | ||
19.3.2 | - | - | - | KI#4: Traffic detections/QoS flow mapping for multiplexed data flows | - | - | Docs:=1 | - | |
19.3.2 | S2-2500903 | CR | Approval | 23.501 CR6034 (Rel-19, 'B'): Clarifications for support of mixed traffic handling | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | - | - | - | KI#1: PDU Set information marking | - | - | Docs:=10 | - | |
19.3.2 | S2-2500042 | LS In | Action | LS from RAN WG2: Reply LS to SA2 on PDU set | RAN WG2 (R2-2411001) | Rel-19 | |||
19.3.2 | S2-2500051 | LS In | Action | LS from RAN WG3: Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | RAN WG3 (R3-247875) | Rel-19 | |||
19.3.2 | S2-2500117 | CR | Approval | 23.501 CR5887 (Rel-19, 'B'): DL PDU set information marking without (AF-provided) PDU set QoS params | Nokia | Rel-19 | |||
19.3.2 | S2-2500118 | CR | Approval | 23.502 CR5197 (Rel-19, 'B'): Procedures updates on DL PDU set information marking without (AF-provided) PDU set QoS params | Nokia | Rel-19 | |||
19.3.2 | S2-2500541 | CR | Approval | 23.501 CR5772R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411893 | ||
19.3.2 | S2-2500568 | CR | Approval | 23.502 CR5094R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411930 | ||
19.3.2 | S2-2500583 | CR | Approval | 23.503 CR1410R2 (Rel-19, 'B'): Support PDU Set based handling without DL PDU Set QoS parameters | Samsung | Rel-19 | Revision of S2-2411935 | ||
19.3.2 | S2-2500850 | CR | Approval | 23.502 CR5292 (Rel-19, 'B'): 23.502 PDU set based handling without PDU set QoS parameters | Lenovo | Rel-19 | |||
19.3.2 | S2-2500907 | CR | Approval | 23.501 CR5790R2 (Rel-19, 'B'): Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon | Rel-19 | Revision of S2-2411922 | ||
19.3.2 | S2-2500908 | CR | Approval | 23.503 CR1498 (Rel-19, 'B'): Support of PDU Set based handling when no DL PDU Set QoS parameters are received | Huawei, HiSilicon | Rel-19 | |||
19.3.2 | - | - | - | KI#1: AL-FEC | - | - | Docs:=8 | - | |
19.3.2 | S2-2500043 | LS In | Action | LS from RAN WG2: Reply LS on Application-Layer FEC Awareness at RAN | RAN WG2 (R2-2411002) | Rel-19 | Responses drafted in S2-2500482, S2-2500963 | ||
19.3.2 | S2-2500482 | LS OUT | Approval | [DRAFT] LS Reply on Application-Layer FEC Awareness at RAN | Samsung | Rel-19 | Response to S2-2500043 | ||
19.3.2 | S2-2500963 | LS OUT | Approval | [DRAFT] Reply LS on Application-Layer FEC Awareness at RAN | Nokia | Rel-19 | Response to S2-2500043 | ||
19.3.2 | S2-2500119 | CR | Approval | 23.501 CR5888 (Rel-19, 'B'): Support AL-FEC awareness at NG-RAN | Nokia, Qualcomm Incorporated, InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2500120 | CR | Approval | 23.503 CR1454 (Rel-19, 'B'): Support AL-FEC awareness at NG-RAN | Nokia, Qualcomm Incorporated, InterDigital Inc. | Rel-19 | |||
19.3.2 | S2-2501002 | DISCUSSION | Approval | Discussion on AL-FEC awareness at NG-RAN . | Xiaomi | Rel-19 | |||
19.3.2 | S2-2501006 | CR | Approval | 23.502 CR5312 (Rel-19, 'B'): XRM_Ph2_KI1_AL-FEC support | Xiaomi | Rel-19 | |||
19.3.2 | S2-2501007 | CR | Approval | 23.503 CR1502 (Rel-19, 'B'): XRM_Ph2_KI1_AL-FEC support | Xiaomi | Rel-19 | Check Affected Clauses! | ||
19.3.2 | - | - | - | KI#9: Information exposure - available data rate | - | - | Docs:=6 | - | |
19.3.2 | S2-2500048 | LS In | Information | LS from RAN WG2: LS on XR UL bit rate control | RAN WG2 (R2-2411218) | Rel-19 | |||
19.3.2 | S2-2500704 | CR | Approval | 23.501 CR5525R3 (Rel-19, 'B'): The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo | Rel-19 | Revision of S2-2411978 | ||
19.3.2 | S2-2500705 | CR | Approval | 23.503 CR1396R2 (Rel-19, 'B'): The available UL and/or DL Data Rate exposure to AF | CATT, Lenovo | Rel-19 | Revision of S2-2411979 | ||
19.3.2 | S2-2500905 | CR | Approval | 23.501 CR5794R2 (Rel-19, 'B'): Support of available data rate exposure | Huawei, HiSilicon, Nokia | Rel-19 | Revision of S2-2411916 | ||
19.3.2 | S2-2500906 | CR | Approval | 23.503 CR1419R2 (Rel-19, 'B'): Support of available data rate exposure | Huawei, HiSilicon | Rel-19 | Revision of S2-2411917 | ||
19.3.2 | S2-2500960 | CR | Approval | 23.502 CR5309 (Rel-19, 'B'): KI#9, Support of Available Data Rate | Nokia | Rel-19 | |||
19.4.1 | - | - | - | Feasibility Study on 5GS Enhancement for Energy Efficiency and Energy Saving (FS_EnergySys) | - | - | Docs:=0 | - | |
19.4.2 | - | - | - | 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys) | - | - | Docs:=64 | - | |
19.4.2 | - | - | - | WT#1: Energy information collection (EIF) | - | - | Docs:=19 | - | |
19.4.2 | S2-2500175 | CR | Approval | 23.501 CR5897 (Rel-19, 'F'): Parameters for EIF selection | China Mobile | Rel-19 | |||
19.4.2 | S2-2500754 | CR | Approval | 23.501 CR5997 (Rel-19, 'F'): Update on NF function descriptions and EIF selection factors | Vivo | Rel-19 | |||
19.4.2 | S2-2500269 | CR | Approval | 23.501 CR5912 (Rel-19, 'F'): Resolve the ENs of energy consumption information collection and exposure for certain application | China Mobile | Rel-19 | |||
19.4.2 | S2-2500789 | CR | Approval | 23.501 CR6000 (Rel-19, 'F'): Support of per-application energy consumption information | Samsung | Rel-19 | DRM File replaced | ||
19.4.2 | S2-2500886 | CR | Approval | 23.501 CR6028 (Rel-19, 'F'): Adding Application level Energy consumption collection, calculation and exposure | ZTE | Rel-19 | |||
19.4.2 | S2-2500885 | DISCUSSION | Information | Discussion and proposal on the application level energy consumption information exposure. | ZTE | Rel-19 | |||
19.4.2 | S2-2500840 | CR | Approval | 23.501 CR6014 (Rel-19, 'F'): Clarification on support of Energy Efficiency and Energy Saving | CATT | Rel-19 | |||
19.4.2 | S2-2500747 | CR | Approval | 23.501 CR5995 (Rel-19, 'F'): Update on energy consumption information collection and exposure to solve the Editor's notes | Vivo | Rel-19 | |||
19.4.2 | S2-2500810 | CR | Approval | 23.501 CR6008 (Rel-19, 'F'): Clarification regarding energy collection and exposure | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500813 | CR | Approval | 23.501 CR6010 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500884 | CR | Approval | 23.501 CR6027 (Rel-19, 'F'): Correcting the input and output of SMF and resolving the EN on roaming. | ZTE | Rel-19 | |||
19.4.2 | S2-2500818 | CR | Approval | 23.501 CR6013 (Rel-19, 'F'): EIF support of OAM interaction | Huawei, HiSilicon | Rel-19 | Missing CR Number - CR states -! | ||
19.4.2 | S2-2500455 | CR | Approval | 23.501 CR5956 (Rel-19, 'F'): Support for S-NSSAI granularity energy consumption exposure | NEC | Rel-19 | |||
19.4.2 | S2-2500369 | CR | Approval | 23.501 CR5935 (Rel-19, 'F'): Compliance to regional legislation concerning user privacy. | Nokia, Deutsche Telekom | Rel-19 | |||
19.4.2 | S2-2500811 | CR | Approval | 23.501 CR6009 (Rel-19, 'F'): Updating the functionality impacts introduced by energy related features | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500189 | CR | Approval | 23.501 CR5900 (Rel-19, 'F'): Clean up the architecture and interface for energysys | Qualcomm Incorporated | Rel-19 | |||
19.4.2 | S2-2500356 | CR | Approval | 23.501 CR5929 (Rel-19, 'F'): Resolving Roaming editor's note in the architecture | NTT DOCOMO | Rel-19 | |||
19.4.2 | S2-2500357 | CR | Approval | 23.501 CR5930 (Rel-19, 'F'): Resolving editor's note on the interface between EIF and OAM | NTT DOCOMO | Rel-19 | |||
19.4.2 | S2-2500815 | CR | Approval | 23.501 CR6011 (Rel-19, 'F'): Reference architecture: Roaming support and OAM interface | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | - | - | - | WT#1: Procedure for Energy information collection | - | - | Docs:=14 | - | |
19.4.2 | S2-2500176 | CR | Approval | 23.502 CR5205 (Rel-19, 'F'): Parameters for EIF selection | China Mobile | Rel-19 | |||
19.4.2 | S2-2500283 | CR | Approval | 23.502 CR5234 (Rel-19, 'F'): Update on Energy Consumption information collection | ETRI | Rel-19 | |||
19.4.2 | S2-2500814 | CR | Approval | 23.502 CR5289 (Rel-19, 'F'): Clarification regarding energy collection and exposure | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500841 | CR | Approval | 23.502 CR5160R1 (Rel-19, 'F'): Data collection for energy information calculation and exposure | CATT | Rel-19 | Revision of S2-2411859 | ||
19.4.2 | S2-2500178 | CR | Approval | 23.502 CR5206 (Rel-19, 'F'): Correction of Energy Consumption information exposure procedure | China Mobile | Rel-19 | |||
19.4.2 | S2-2500282 | CR | Approval | 23.502 CR5233 (Rel-19, 'F'): Update on Energy Consumption information exposure and consumer NF | ETRI | Rel-19 | |||
19.4.2 | S2-2500887 | CR | Approval | 23.502 CR5299 (Rel-19, 'F'): Adding procedure for Application level Energy consumption collection and exposure | ZTE | Rel-19 | |||
19.4.2 | S2-2500456 | CR | Approval | 23.502 CR5244 (Rel-19, 'F'): Support for S-NSSAI granularity energy consumption exposure | NEC | Rel-19 | |||
19.4.2 | S2-2500842 | CR | Approval | 23.288 CR1286R1 (Rel-19, 'F'): Data collection via DCCF for energy information calculation and exposure | CATT | Rel-19 | Revision of S2-2411860 | ||
19.4.2 | S2-2500358 | CR | Approval | 23.502 CR5239 (Rel-19, 'F'): Updating EIF service operations | NTT DOCOMO | Rel-19 | |||
19.4.2 | S2-2500750 | CR | Approval | 23.502 CR5279 (Rel-19, 'F'): Resolving EN in Clause 5.2.28.1 | MediaTek Inc. | Rel-19 | |||
19.4.2 | S2-2500756 | CR | Approval | 23.502 CR5280 (Rel-19, 'F'): Update on EIF services to solve the Editor's notes | Vivo | Rel-19 | |||
19.4.2 | S2-2500547 | CR | Approval | 23.502 CR5254 (Rel-19, 'F'): Update on Nsmf_EventExposure service for Energy Consumption information collection | ETRI | Rel-19 | |||
19.4.2 | S2-2500812 | CR | Approval | 23.502 CR5288 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | - | - | - | WT#2: UE Subscription and Policy | - | - | Docs:=19 | - | |
19.4.2 | S2-2500344 | CR | Approval | 23.501 CR5927 (Rel-19, 'F'): Resolution of editor s note on whether the Energy Saving indicator is one value or multiple values. | Nokia, Deutsche Telekom | Rel-19 | |||
19.4.2 | S2-2500227 | DISCUSSION | Discussion | Discussion on Energy Saving Indicator. | Nokia, Deutsche Telekom | Rel-19 | |||
19.4.2 | S2-2500391 | CR | Approval | 23.501 CR5938 (Rel-19, 'F'): Resolving ENs about subscription information and policy control | LG Electronics | Rel-19 | |||
19.4.2 | S2-2500748 | CR | Approval | 23.501 CR5996 (Rel-19, 'F'): Resolving ENs in Clause 5.51.5 and 5.51.6 | MediaTek Inc. | Rel-19 | |||
19.4.2 | S2-2500771 | CR | Approval | 23.501 CR5999 (Rel-19, 'F'): Update on subscription information and policy control aspects | Vivo | Rel-19 | |||
19.4.2 | S2-2500816 | CR | Approval | 23.501 CR6012 (Rel-19, 'F'): Update of the subscription aspects for network energy saving | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500853 | CR | Approval | 23.501 CR6015 (Rel-19, 'C'): Clarification on Energy Saving indicator | Samsung | Rel-19 | |||
19.4.2 | S2-2500888 | CR | Approval | 23.501 CR6029 (Rel-19, 'F'): Resolving the EN on the UE Energy saving Subscription | ZTE | Rel-19 | |||
19.4.2 | S2-2500351 | CR | Approval | 23.501 CR5928 (Rel-19, 'F'): Resolution of editor's note on PCF taking EIF information into account | Nokia | Rel-19 | |||
19.4.2 | S2-2500793 | CR | Approval | 23.501 CR6001 (Rel-19, 'F'): Support of policy control based on energy information | Samsung | Rel-19 | |||
19.4.2 | S2-2500889 | CR | Approval | 23.501 CR6030 (Rel-19, 'F'): Clarification on the policy control for network energy saving | ZTE | Rel-19 | |||
19.4.2 | S2-2500892 | CR | Approval | 23.501 CR6031 (Rel-19, 'F'): Clarification on the BDT based on network energy related information | ZTE | Rel-19 | |||
19.4.2 | S2-2500191 | CR | Approval | 23.503 CR1458 (Rel-19, 'F'): Energy Saving Subscription management in PCF | Qualcomm Incorporated | Rel-19 | |||
19.4.2 | S2-2500731 | CR | Approval | 23.503 CR1486 (Rel-19, 'F'): Policy control with energy saving consideration. | Vivo | Rel-19 | |||
19.4.2 | S2-2500753 | CR | Approval | 23.503 CR1489 (Rel-19, 'F'): Adding the changes for input data to PCF | MediaTek Inc. | Rel-19 | |||
19.4.2 | S2-2500891 | CR | Approval | 23.503 CR1495 (Rel-19, 'F'): Adding the Energy saving indicator to the AMF input | ZTE | Rel-19 | |||
19.4.2 | S2-2500844 | CR | Approval | 23.503 CR1403R2 (Rel-19, 'F'): Energy related subscription data and policy control | CATT | Rel-19 | Revision of S2-2411502 | ||
19.4.2 | S2-2500819 | CR | Approval | 23.503 CR1492 (Rel-19, 'F'): Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon | Rel-19 | |||
19.4.2 | S2-2500894 | CR | Approval | 23.503 CR1496 (Rel-19, 'F'): Clarification on the BDT policy decision | ZTE | Rel-19 | |||
19.4.2 | - | - | - | WT#2: Procedure UE Subscription and Policy | - | - | Docs:=9 | - | |
19.4.2 | S2-2500190 | CR | Approval | 23.502 CR5208 (Rel-19, 'F'): Clean up ENs about EnergySys | Qualcomm Incorporated | Rel-19 | |||
19.4.2 | S2-2500730 | CR | Approval | 23.502 CR5276 (Rel-19, 'F'): Energy saving subscription and AM policy. | Vivo | Rel-19 | |||
19.4.2 | S2-2500890 | CR | Approval | 23.502 CR5300 (Rel-19, 'F'): Adding Energy saving indicator to AM policy procedure | ZTE | Rel-19 | |||
19.4.2 | S2-2500843 | CR | Approval | 23.502 CR5133R1 (Rel-19, 'F'): Energy related subscription data and policy control | CATT | Rel-19 | Revision of S2-2411503 | ||
19.4.2 | S2-2500253 | CR | Approval | 23.502 CR5144R1 (Rel-19, 'F'): Energy Saving indicator | Ericsson, AT&T | Rel-19 | Revision of S2-2411715 | ||
19.4.2 | S2-2500855 | CR | Approval | 23.502 CR5293 (Rel-19, 'C'): Procedure for delivering the Energy Saving information for the UE | Samsung | Rel-19 | |||
19.4.2 | S2-2500359 | CR | Approval | 23.502 CR5240 (Rel-19, 'F'): Negotiation for future background data transfer considering energy | NTT DOCOMO | Rel-19 | |||
19.4.2 | S2-2500587 | CR | Approval | 23.502 CR5256 (Rel-19, 'B'): Enhancement for BDT with Energy related information | KDDI | Rel-19 | |||
19.4.2 | S2-2500893 | CR | Approval | 23.502 CR5301 (Rel-19, 'F'): Adding Energy indication to BDT procedure and service operation | ZTE | Rel-19 | |||
19.4.2 | - | - | - | WT#3 UP Path Adjustment | - | - | Docs:=1 | - | |
19.4.2 | S2-2500177 | CR | Approval | 23.501 CR5898 (Rel-19, 'B'): UP path selection by considering energy related information | China Mobile | Rel-19 | |||
19.4.2 | - | - | - | LS Out | - | - | Docs:=2 | - | |
19.4.2 | S2-2500776 | LS OUT | Approval | [DRAFT] LS on renewable energy information collection from OAM to EIF | vivo | Rel-19 | |||
19.4.2 | S2-2500817 | LS OUT | Approval | [DRAFT] LS on OAM energy information exposure | Huawei, HiSilicon | Rel-19 | |||
19.5.1 | - | - | - | Study on MPS for IMS Messaging and SMS services (FS_MPS4msg) | - | - | Docs:=0 | - | |
19.5.2 | - | - | - | MPS for IMS Messaging and SMS services (MPS4msg) | - | - | Docs:=0 | - | |
19.6.1 | - | - | - | Study on Architecture Enhancements for Vehicle Mounted Relays Phase 2 (FS_VMR_Ph2) | - | - | Docs:=0 | - | |
19.6.2 | - | - | - | Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2) | - | - | Docs:=0 | - | |
19.7.1 | - | - | - | Study on System Enhancement for Proximity-based Services in 5GS – Phase 3 (FS_5G_ProSe_Ph3) | - | - | Docs:=0 | - | |
19.7.2 | - | - | - | System Enhancement for Proximity-based Services in 5GS – Phase 3 (5G_ProSe_Ph3) | - | - | Docs:=38 | - | |
19.7.2 | - | - | - | LS In and responses | - | - | Docs:=11 | - | |
19.7.2 | S2-2500045 | LS In | Action | LS from RAN WG2: LS to SA2 on relay discovery announcement | RAN WG2 (R2-2411184) | Rel-19 | Responses drafted in S2-2500323, S2-2500377, S2-2500390, S2-2500433, S2-2500502, S2-2500649 | ||
19.7.2 | S2-2500323 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | CATT | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500377 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | OPPO | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500390 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | LG Electronics | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500433 | LS OUT | Approval | [DRAFT] LS Reply on relay discovery announcement | Ericsson | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500502 | LS OUT | Approval | [DRAFT] Reply LS on relay discovery announcement | Qualcomm Incorporated | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500649 | LS OUT | Approval | [DRAFT] Reply LS on Relay Discovery Announcement | ZTE | Rel-19 | Response to S2-2500045 | ||
19.7.2 | S2-2500022 | LS In | Action | LS from SA WG3: LS on Multi-hop U2N Relay Architecture Aspects | SA WG3 (S3-245259) | Rel-19 | Responses drafted in S2-2500128, S2-2500326, S2-2500518 | ||
19.7.2 | S2-2500128 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | KPN N.V. | Rel-19 | Response to S2-2500022 | ||
19.7.2 | S2-2500326 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | CATT | Rel-19 | Response to S2-2500022 | ||
19.7.2 | S2-2500518 | LS OUT | Approval | [DRAFT] Reply LS on Multi-hop U2N Relay Architecture Aspects | Qualcomm Incorporated | Rel-19 | Response to S2-2500022 | ||
19.7.2 | - | - | - | General | - | - | Docs:=3 | - | |
19.7.2 | S2-2500130 | CR | Approval | 23.502 CR5188R1 (Rel-19, 'F'): Update ProSe subscription data to support multi-hop relay | KPN N.V. | Rel-19 | Revision of S2-2412269 | ||
19.7.2 | S2-2500131 | CR | Approval | 23.304 CR0519R1 (Rel-19, 'D'): Editorial corrections | KPN N.V. | Rel-19 | Revision of S2-2412270 | ||
19.7.2 | S2-2500435 | CR | Approval | 23.304 CR0491R2 (Rel-19, 'F'): Introduction of multi-hop in the specification | Ericsson | Rel-19 | Revision of S2-2412344 | ||
19.7.2 | - | - | - | UE-to-UE Relay | - | - | Docs:=8 | - | |
19.7.2 | S2-2500103 | CR | Approval | 23.304 CR0522 (Rel-19, 'F'): Clarification on triggering the diffusion of DNS information via MANET when End UE is disconnected | Huawei, HiSilicon | Rel-19 | |||
19.7.2 | S2-2500106 | CR | Approval | 23.304 CR0524 (Rel-19, 'F'): Update on Multihop U2U Relay for non-IP type PDU | Huawei, HiSilicon | Rel-19 | |||
19.7.2 | S2-2500107 | CR | Approval | 23.304 CR0525 (Rel-19, 'F'): Update on Discovery of U2U Multihop Relay for IP PDU | Huawei, HiSilicon | Rel-19 | |||
19.7.2 | S2-2500314 | CR | Approval | 23.304 CR0529 (Rel-19, 'F'): Update on multihop U2U Relay reselection procedure for non-IP type | InterDigital Communications | Rel-19 | |||
19.7.2 | S2-2500316 | CR | Approval | 23.304 CR0531 (Rel-19, 'F'): Update on multihop ProSe U2U Relay for non-IP type PDU | InterDigital Communications | Rel-19 | |||
19.7.2 | S2-2500325 | CR | Approval | 23.304 CR0533 (Rel-19, 'F'): Corrections on multi-hop U2U Relay discovery of non-IP PDU type | CATT | Rel-19 | |||
19.7.2 | S2-2500436 | CR | Approval | 23.304 CR0492R2 (Rel-19, 'F'): Expansion of 5G ProSe Layer-3 UE-to-UE Relay functionality | Ericsson | Rel-19 | Revision of S2-2412346 | ||
19.7.2 | S2-2500764 | CR | Approval | 23.304 CR0539 (Rel-19, 'F'): Procedures for ProSe Multihop U2U Relay reselection for Non-IP | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! | ||
19.7.2 | - | - | - | UE-to-Network Relay | - | - | Docs:=16 | - | |
19.7.2 | S2-2500104 | DISCUSSION | Discussion | Discussion about IP (re)allocation during Multi-hop U2N Relay Reselection. | Huawei, HiSilicon | Rel-19 | |||
19.7.2 | S2-2500105 | CR | Approval | 23.304 CR0523 (Rel-19, 'F'): Clarification on Multi-hop Relay Reselection | Huawei, HiSilicon | Rel-19 | |||
19.7.2 | S2-2500129 | CR | Approval | 23.304 CR0527 (Rel-19, 'F'): Correction of UE-to-Network Model B Discovery | KPN N.V. | Rel-19 | |||
19.7.2 | S2-2500313 | CR | Approval | 23.304 CR0528 (Rel-19, 'F'): Update on multihop ProSe U2N Relay with model B discovery | InterDigital Communications | Rel-19 | |||
19.7.2 | S2-2500315 | CR | Approval | 23.304 CR0530 (Rel-19, 'F'): Update on multihop ProSe U2N Relay Discovery | InterDigital Communications | Rel-19 | |||
19.7.2 | S2-2500324 | CR | Approval | 23.304 CR0532 (Rel-19, 'F'): Corrections on multi-hop U2N Relay discovery with Model A procedure | CATT | Rel-19 | |||
19.7.2 | S2-2500327 | CR | Approval | 23.304 CR0534 (Rel-19, 'F'): Corrections on multi-hop U2N Relay architecture aspects | CATT | Rel-19 | Check Affected Clauses! | ||
19.7.2 | S2-2500386 | CR | Approval | 23.304 CR0535 (Rel-19, 'F'): Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN | LG Electronics | Rel-19 | |||
19.7.2 | S2-2500387 | LS OUT | Approval | [DRAFT] LS on Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN | LG Electronics | Rel-19 | |||
19.7.2 | S2-2500388 | DISCUSSION | Discussion | Discussion on behavior of Intermediate U2N Relay related to Model A discovery. | LG Electronics | Rel-19 | |||
19.7.2 | S2-2500389 | CR | Approval | 23.304 CR0536 (Rel-19, 'F'): Clarification on behavior of Intermediate U2N Relay related to Model A discovery | LG Electronics | Rel-19 | |||
19.7.2 | S2-2500434 | CR | Approval | 23.304 CR0490R1 (Rel-19, 'F'): Adding Path Failure Detection for Relay Reselection | Ericsson, FirstNet, Qualcomm Inc., AT&T | Rel-19 | Revision of S2-2411480 | ||
19.7.2 | S2-2500503 | CR | Approval | 23.304 CR0537 (Rel-19, 'F'): Correction on conditions for Intermediate Relay to send Relay Discovery Announcement message | Qualcomm Incorporated | Rel-19 | |||
19.7.2 | S2-2500762 | CR | Approval | 23.304 CR0513R1 (Rel-19, 'F'): Update on multi-hop U2N Relay Discovery with Model A | China Telecom | Rel-19 | Revision of S2-2412248. WI Code should be 5G_ProSe_Ph3! | ||
19.7.2 | S2-2500763 | CR | Approval | 23.304 CR0538 (Rel-19, 'F'): Update on ProSe Multihop U2N Relay reselection based on Model A discovery | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! | ||
19.7.2 | S2-2500765 | CR | Approval | 23.304 CR0540 (Rel-19, 'F'): Correction on ProSe Multihop U2N Relay reselection for Model B | China Telecom | Rel-19 | WI Code should be 5G_ProSe_Ph3! | ||
19.8.1 | - | - | - | Study on User Identities and Authentication Architecture (FS_UIA_ARC) | - | - | Docs:=0 | - | |
19.8.2 | - | - | - | Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC) | - | - | Docs:=50 | - | |
19.8.2 | - | - | - | Multiple Non-3GPP Devices and UDR Notification to the PCF | - | - | Docs:=4 | - | |
19.8.2 | S2-2500240 | CR | Approval | 23.502 CR5218 (Rel-19, 'F'): QoS differentiation for multiple Non-3GPP devices | Ericsson, AT&T | Rel-19 | |||
19.8.2 | S2-2500215 | CR | Approval | 23.502 CR5212 (Rel-19, 'F'): SM Policy Association Modification for Non-3GPP Device Identifiers | Nokia, InterDigital Inc. | Rel-19 | |||
19.8.2 | S2-2501034 | CR | Approval | 23.502 CR5319 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | Check Affected Clauses! | |||
19.8.2 | S2-2501043 | CR | Approval | 23.502 CR5321 (Rel-19, 'F'): Clarification to SMF and PCF behaviour during Session modification for handling device identifiers | Samsung | Rel-19 | |||
19.8.2 | - | - | - | Moving NOTE 14 | - | - | Docs:=1 | - | |
19.8.2 | S2-2501042 | CR | Approval | 23.502 CR5320 (Rel-19, 'F'): Clarification on AF provisioning of Non-3GPP device identifier information | Samsung | Rel-19 | |||
19.8.2 | - | - | - | TS 23.316, Annex C, Editor’s Note | - | - | Docs:=1 | - | |
19.8.2 | S2-2500216 | CR | Approval | 23.316 CR2140 (Rel-19, 'F'): Resolving EN related to PCF initiated Policy Updates | Nokia, InterDigital Inc. | Rel-19 | |||
19.8.2 | - | - | - | TS 23.316, Annex C | - | - | Docs:=2 | - | |
19.8.2 | S2-2500450 | CR | Approval | 23.316 CR2141 (Rel-19, 'F'): QoS differentiation of non-3GPP devices behind 5G-RG | CableLabs, Charter Communications | Rel-19 | |||
19.8.2 | S2-2500556 | DISCUSSION | Approval | Discussion on Identification of non-3GPP devices behind 5G-RG. | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | - | - | - | EN on PDU Session Establishment | - | - | Docs:=1 | - | |
19.8.2 | S2-2500804 | CR | Approval | 23.501 CR6006 (Rel-19, 'F'): Resolve the EN on the PDU session establishment and Reference correction | ZTE | Rel-19 | |||
19.8.2 | - | - | - | Stopping QoS Differentiation | - | - | Docs:=3 | - | |
19.8.2 | S2-2500485 | CR | Approval | 23.501 CR5963 (Rel-19, 'F'): Definition of non-3GPP device connection information | Qualcomm Incorporated, InterDigital | Rel-19 | |||
19.8.2 | S2-2500555 | CR | Approval | 23.502 CR5255 (Rel-19, 'F'): Removal of N3GPP device from UDR | Huawei, Hisilicon | Rel-19 | |||
19.8.2 | S2-2500846 | CR | Approval | 23.503 CR1493 (Rel-19, 'F'): Clarification on policy control for non-3GPP devices connecting behind a UE | CATT | Rel-19 | |||
19.8.2 | - | - | - | TS 23.501 Clause 5.52.3 Updates | - | - | Docs:=3 | - | |
19.8.2 | S2-2500553 | CR | Approval | 23.501 CR5975 (Rel-19, 'F'): User plane information related to N3GPP device within PDU session modification | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | S2-2500806 | CR | Approval | 23.501 CR6007 (Rel-19, 'F'): Clarification on session management enhancement | ZTE | Rel-19 | |||
19.8.2 | S2-2500239 | CR | Approval | 23.501 CR5905 (Rel-19, 'F'): Adding PDU session type IPv4v6 | Ericsson, AT&T | Rel-19 | |||
19.8.2 | - | - | - | TS 23.501 Clause 5.52.2 Updates | - | - | Docs:=3 | - | |
19.8.2 | S2-2500461 | CR | Approval | 23.501 CR5960 (Rel-19, 'F'): Clarification on UE triggering request for change of QoS | Apple | Rel-19 | |||
19.8.2 | S2-2500854 | CR | Approval | 23.501 CR6016 (Rel-19, 'F'): Correction of description on support of N3GPP device behind UE | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | S2-2501022 | CR | Approval | 23.501 CR6053 (Rel-19, 'F'): Further details for QoS information | Xiaomi | Rel-19 | |||
19.8.2 | - | - | - | TS 23.501 Clause 5.52.1 Updates | - | - | Docs:=2 | - | |
19.8.2 | S2-2501021 | CR | Approval | 23.501 CR6052 (Rel-19, 'F'): Correction for UE SUPI | Xiaomi | Rel-19 | |||
19.8.2 | S2-2500530 | CR | Approval | 23.501 CR5970 (Rel-19, 'F'): Clarification on roaming support for Non-3GPP Device Identifier | LG Electronics | Rel-19 | |||
19.8.2 | - | - | - | TS 23.316 | - | - | Docs:=1 | - | |
19.8.2 | S2-2500462 | CR | Approval | 23.316 CR2142 (Rel-19, 'F'): Clarification on AF-5GC interaction for provisioning non-3GPP device identifiers | Apple | Rel-19 | |||
19.8.2 | - | - | - | TS 23.503 | - | - | Docs:=5 | - | |
19.8.2 | S2-2500242 | CR | Approval | 23.503 CR1462 (Rel-19, 'F'): QoS differentiation results per each Non-3GPP device | Ericsson, AT&T | Rel-19 | |||
19.8.2 | S2-2500532 | CR | Approval | 23.503 CR1478 (Rel-19, 'F'): Clarification on UE behaviour when Non-3GPP Device Identifier is not associated with the UE | LG Electronics | Rel-19 | |||
19.8.2 | S2-2500349 | CR | Approval | 23.503 CR1467 (Rel-19, 'F'): PCC enhancements for support of identified non-3GPP devices | China Mobile | Rel-19 | |||
19.8.2 | S2-2500554 | CR | Approval | 23.503 CR1480 (Rel-19, 'F'): PCC enhancements for support of identified non-3GPP devices | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | S2-2501044 | CR | Approval | 23.503 CR1503 (Rel-19, 'F'): Corrections to PCR trigger and SM policy modification for Non-3GPP device identifier | Samsung | Rel-19 | Check Affected Clauses! | ||
19.8.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
19.8.2 | S2-2500533 | CR | Approval | 23.502 CR5252 (Rel-19, 'F'): Clarification on Provisioning of Non-3GPP Device Identifier(s) Information | LG Electronics | Rel-19 | |||
19.8.2 | S2-2500807 | CR | Approval | 23.502 CR5287 (Rel-19, 'F'): Modification to the SM Policy Association Modification procedure | ZTE | Rel-19 | |||
19.8.2 | - | - | - | SMF Selection | - | - | Docs:=1 | - | |
19.8.2 | S2-2500558 | CR | Approval | 23.501 CR5976 (Rel-19, 'F'): Support of SMF selection considering the Non-3GPP Device Identifier | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | - | - | - | Clarifications on AF Provisioning | - | - | Docs:=2 | - | |
19.8.2 | S2-2500803 | CR | Approval | 23.501 CR6005 (Rel-19, 'F'): Clarification on AF provisioning | ZTE | Rel-19 | |||
19.8.2 | S2-2500805 | CR | Approval | 23.502 CR5286 (Rel-19, 'F'): Clarification on the AF provisioning procedure | ZTE | Rel-19 | |||
19.8.2 | - | - | - | Documents exceeding TU budget | - | - | Docs:=19 | - | |
19.8.2 | S2-2500448 | CR | Approval | 23.501 CR5954 (Rel-19, 'F'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia, Apple | Rel-19 | |||
19.8.2 | S2-2500449 | CR | Approval | 23.502 CR5242 (Rel-19, 'F'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia | Rel-19 | |||
19.8.2 | S2-2500451 | CR | Approval | 23.503 CR1476 (Rel-19, 'D'): Editorial Fixes and Corrections Related to UIA_ARC | InterDigital Inc., Nokia | Rel-19 | |||
19.8.2 | S2-2500453 | CR | Approval | 23.502 CR5243 (Rel-19, 'F'): Handling of the scenerio where a non-3GPP device no longer requires QoS Differentiation | InterDigital Inc, Qualcomm, ETRI | Rel-19 | |||
19.8.2 | S2-2500454 | CR | Approval | 23.503 CR1477 (Rel-19, 'F'): Handling of the scenerio where a non-3GPP device no longer requires QoS Differentiation | InterDigital Inc., Qualcomm, ETRI | Rel-19 | |||
19.8.2 | S2-2500452 | CR | Approval | 23.501 CR5955 (Rel-19, 'F'): Resolving the Editorial Note on PDU Session Establishment | InterDigital Inc., Nokia | Rel-19 | |||
19.8.2 | S2-2500709 | CR | Approval | 23.502 CR5275 (Rel-19, 'F'): Support of SMF selection for Non-3GPP Device Identifer | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | S2-2500557 | CR | Approval | 23.316 CR2146 (Rel-19, 'F'): Identifying non-3GPP devices behind 5G-RG | Huawei, HiSilicon | Rel-19 | |||
19.8.2 | S2-2500552 | CR | Approval | 23.316 CR2145 (Rel-19, 'F'): Identifying non-3GPP devices behind 5G-RG and NAUN3 devices | Huawei, Hisilicon | Rel-19 | |||
19.8.2 | S2-2500534 | CR | Approval | 23.502 CR5253 (Rel-19, 'F'): Clarification on Non-3GPP Device Connection Information reporting procedures | LG Electronics | Rel-19 | |||
19.8.2 | S2-2500529 | CR | Approval | 23.316 CR2144 (Rel-19, 'F'): Clarification on Non-3GPP Device Identifier reporting procedure | LG Electronics | Rel-19 | |||
19.8.2 | S2-2500531 | CR | Approval | 23.501 CR5971 (Rel-19, 'F'): Clarification on user plane address reporting associated with Non-3GPP Device Identifier | LG Electronics | Rel-19 | |||
19.8.2 | S2-2500808 | CR | Approval | 23.503 CR1491 (Rel-19, 'F'): Clarification on Policy control for non-3GPP devices connecting behind a UE | ZTE | Rel-19 | |||
19.8.2 | S2-2500809 | CR | Approval | 23.316 CR2149 (Rel-19, 'F'): Resolve the EN and correct the figure and options description | ZTE | Rel-19 | Check Affected Clauses! | ||
19.8.2 | S2-2501024 | CR | Approval | 23.501 CR6055 (Rel-19, 'F'): Max no of non-3GPP device identifier | Xiaomi | Rel-19 | |||
19.8.2 | S2-2501023 | CR | Approval | 23.501 CR6054 (Rel-19, 'F'): Clarification for non-3GPP connection information | Xiaomi | Rel-19 | |||
19.8.2 | S2-2500214 | CR | Approval | 23.502 CR5211 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc. | Rel-19 | |||
19.8.2 | S2-2500241 | CR | Approval | 23.502 CR5219 (Rel-19, 'F'): Moving note from table to clause | Ericsson, AT&T | Rel-19 | |||
19.8.2 | S2-2500845 | CR | Approval | 23.502 CR5080R2 (Rel-19, 'F'): PDU session management for identified non-3GPP Devices behind the UE | CATT | Rel-19 | Revision of S2-2411507 | ||
19.9.1 | - | - | - | Study on Enhancement of support for Edge Computing in 5G Core network — Phase 3 (FS_eEDGE_5GC_Ph3) | - | - | Docs:=0 | - | |
19.9.2 | - | - | - | Enhancement of support for Edge Computing in 5G Core network — Phase 3 (eEDGE_5GC_Ph3) | - | - | Docs:=45 | - | |
19.9.2 | - | - | - | KI#1: Offloading from central SMF | - | - | Docs:=0 | - | |
19.9.2 | - | - | - | AF Influence to I-SMF or not - Discussion papers | - | - | Docs:=1 | - | |
19.9.2 | S2-2500610 | DISCUSSION | Approval | KI#1: Further clarification on Local offloading traffic handling at I-SMF . | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | - | - | - | EN on AF Influence to I-SMF or not - CRs | - | - | Docs:=8 | - | |
19.9.2 | S2-2500685 | CR | Approval | 23.548 CR0294 (Rel-19, 'F'): KI#1: Further clarification on Local offloading traffic handling at I-SMF | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | S2-2500488 | CR | Approval | 23.548 CR0280 (Rel-19, 'F'): KI#1 Remove EN on AF traffic influence information for I-SMF | Samsung | Rel-19 | |||
19.9.2 | S2-2501063 | CR | Approval | 23.548 CR0298 (Rel-19, 'F'): Removal of Editor s Note on AF traffic influence | Nokia | Rel-19 | |||
19.9.2 | S2-2500319 | CR | Approval | 23.548 CR0279 (Rel-19, 'F'): Correction on local offloading management | China Mobile | Rel-19 | |||
19.9.2 | S2-2500882 | CR | Approval | 23.548 CR0295 (Rel-19, 'F'): Resolve EN for policy provisioing for Local offloading management | ZTE | Rel-19 | |||
19.9.2 | S2-2500489 | CR | Approval | 23.502 CR5248 (Rel-19, 'F'): KI#1 AF traffic influence information for I-SMF | Samsung | Rel-19 | |||
19.9.2 | S2-2500684 | CR | Approval | 23.502 CR5272 (Rel-19, 'F'): KI#1: Further clarification on Local offloading traffic handling at I-SMF | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | S2-2501064 | CR | Approval | 23.502 CR5332 (Rel-19, 'F'): Update on interaction between I-SMF and SMF to include delay-related AF requests | Nokia | Rel-19 | |||
19.9.2 | - | - | - | EN on Local Offloading Policy handling at SMF | - | - | Docs:=3 | - | |
19.9.2 | S2-2500662 | CR | Approval | 23.502 CR5267 (Rel-19, 'F'): Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | |||
19.9.2 | S2-2500492 | CR | Approval | 23.502 CR5249 (Rel-19, 'F'): Remove EN on Local Offloading Policy update | Samsung | Rel-19 | |||
19.9.2 | S2-2500663 | CR | Approval | 23.548 CR0289 (Rel-19, 'F'): KI#1: Clarification on Local Offloading Management Policy handling at SMF | OPPO | Rel-19 | |||
19.9.2 | - | - | - | I-SMF change for LOM | - | - | Docs:=6 | - | |
19.9.2 | S2-2500611 | CR | Approval | 23.548 CR0288 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | |||
19.9.2 | S2-2501062 | CR | Approval | 23.548 CR0297 (Rel-19, 'F'): Clarification on SMF triggered I-SMF insertion or removal for Local Offloading Management | Nokia | Rel-19 | |||
19.9.2 | S2-2500612 | CR | Approval | 23.501 CR5981 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | |||
19.9.2 | S2-2500613 | CR | Approval | 23.502 CR5265 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | S2-2501056 | CR | Approval | 23.501 CR6058 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia | Rel-19 | |||
19.9.2 | S2-2501055 | CR | Approval | 23.502 CR5328 (Rel-19, 'F'): Correction on I-SMF insertion/removal for local offloading management | Nokia | Rel-19 | |||
19.9.2 | - | - | - | UE Mobility for PDU Session supporting LOM | - | - | Docs:=7 | - | |
19.9.2 | S2-2500682 | CR | Approval | 23.502 CR5271 (Rel-19, 'F'): KI#1: UE mobility for PDU session supporting local offloading management | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | S2-2501061 | CR | Approval | 23.548 CR0296 (Rel-19, 'F'): Corrections on the procedures defined for local offloading management | Nokia | Rel-19 | |||
19.9.2 | S2-2500683 | CR | Approval | 23.548 CR0293 (Rel-19, 'F'): KI#1: UE mobility for PDU session supporting local offloading management | Huawei, HiSilicon | Rel-19 | |||
19.9.2 | S2-2500278 | CR | Approval | 23.548 CR0278 (Rel-19, 'F'): Correction of UE mobility for PDU session supporting Local Offloading Management | China Mobile | Rel-19 | |||
19.9.2 | S2-2500539 | CR | Approval | 23.548 CR0287 (Rel-19, 'F'): Clarification and correction on the LOM Service Area | LG Electronics | Rel-19 | Confirm Spec version used - CR states {19.2.0}! | ||
19.9.2 | S2-2500256 | CR | Approval | 23.548 CR0274 (Rel-19, 'F'): Correcting and improving text for KI#1 | Ericsson | Rel-19 | |||
19.9.2 | S2-2500493 | CR | Approval | 23.548 CR0282 (Rel-19, 'F'): KI#1 Update PDU Session Establishment for Local Offloading Management | Samsung | Rel-19 | |||
19.9.2 | - | - | - | Local Offload Management service area configuration in AMF | - | - | Docs:=1 | - | |
19.9.2 | S2-2500881 | CR | Approval | 23.501 CR6026 (Rel-19, 'F'): Clarification on the local offloading management service area | ZTE | Rel-19 | |||
19.9.2 | - | - | - | I-SMF profile | - | - | Docs:=4 | - | |
19.9.2 | S2-2500255 | CR | Approval | 23.502 CR5221 (Rel-19, 'F'): Adding missing impacts for KI#1 | Ericsson | Rel-19 | |||
19.9.2 | S2-2501057 | CR | Approval | 23.502 CR5329 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia | Rel-19 | |||
19.9.2 | S2-2500277 | CR | Approval | 23.502 CR5229 (Rel-19, 'F'): I-SMF capability registration | China Mobile | Rel-19 | |||
19.9.2 | S2-2501058 | CR | Approval | 23.501 CR6059 (Rel-19, 'F'): Clarification on NF profile for (I-)SMF regarding local offloading management | Nokia | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.501 CRs | - | - | Docs:=2 | - | |
19.9.2 | S2-2500254 | CR | Approval | 23.501 CR5909 (Rel-19, 'F'): Correction and improvements related to EDGE_Ph3 KI#1 | Ericsson | Rel-19 | |||
19.9.2 | S2-2500276 | CR | Approval | 23.501 CR5914 (Rel-19, 'F'): AMF functional description of supporting local offloading | China Mobile | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.502 CRs | - | - | Docs:=2 | - | |
19.9.2 | S2-2501060 | CR | Approval | 23.502 CR5331 (Rel-19, 'F'): Clarification on handling of traffic not subject to Local Offloading Management | Nokia | Rel-19 | |||
19.9.2 | S2-2501059 | CR | Approval | 23.502 CR5330 (Rel-19, 'F'): Corrections related to Local Offloading Management allowed indication | Nokia | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.548 CRs | - | - | Docs:=2 | - | |
19.9.2 | S2-2500490 | CR | Approval | 23.548 CR0281 (Rel-19, 'F'): KI#1 Handling application not matched with LOM policy | Samsung | Rel-19 | |||
19.9.2 | S2-2500664 | CR | Approval | 23.548 CR0290 (Rel-19, 'F'): KI#1 Clarification on EAS Discovery using IP replacement to support Local Offloading Management | OPPO | Rel-19 | |||
19.9.2 | - | - | - | KI#2: Supporting N6 delay measurement | - | - | Docs:=0 | - | |
19.9.2 | - | - | - | I-SMF supporting N6 delay measurement CRs | - | - | Docs:=2 | - | |
19.9.2 | S2-2500495 | CR | Approval | 23.548 CR0284 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | |||
19.9.2 | S2-2500880 | CR | Approval | 23.501 CR6025 (Rel-19, 'F'): N6 delay measurement for I-SMF case | ZTE | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.548 CRs | - | - | Docs:=3 | - | |
19.9.2 | S2-2500272 | CR | Approval | 23.548 CR0275 (Rel-19, 'F'): UPF (re)selection considering N6 delay for for EAS discovery with local DNS server or resolver | China Mobile | Rel-19 | |||
19.9.2 | S2-2500494 | CR | Approval | 23.548 CR0283 (Rel-19, 'F'): I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | |||
19.9.2 | S2-2501066 | CR | Approval | 23.548 CR0299 (Rel-19, 'F'): Alignment on L-PSA UPF re-selection and/or an edge relocation | Nokia | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.501 CRs | - | - | Docs:=3 | - | |
19.9.2 | S2-2500491 | CR | Approval | 23.501 CR5964 (Rel-19, 'F'): KI#1 Remove EN on AF traffic influence information for I-SMF | Samsung | Rel-19 | |||
19.9.2 | S2-2500877 | CR | Approval | 23.501 CR6024 (Rel-19, 'F'): N6 delay measurement triggered by SMF | ZTE | Rel-19 | |||
19.9.2 | S2-2501065 | CR | Approval | 23.501 CR6060 (Rel-19, 'F'): Alignment on L-PSA UPF re-selection and/or an edge relocation | Nokia | Rel-19 | |||
19.9.2 | - | - | - | Other correction - 23.502 CRs | - | - | Docs:=1 | - | |
19.9.2 | S2-2500275 | CR | Approval | 23.502 CR5228 (Rel-19, 'F'): Update on UPF reporting N6 delay measurement | China Mobile | Rel-19 | |||
19.10.1 | - | - | - | Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3) | - | - | Docs:=0 | - | |
19.10.2 | - | - | - | Phase 3 for UAS, UAV and UAM (UAS_Ph3) | - | - | Docs:=16 | - | |
19.10.2 | - | - | - | Incoming LS | - | - | Docs:=1 | - | |
19.10.2 | S2-2500072 | LS In | Information | LS from SA WG6: Reply LS on clarification related to the QoS and QoE parameters for the support of real time UAV flight path monitoring assistance. | SA WG6 (S6-245642) | Rel-19 | |||
19.10.2 | - | - | - | KI#1: NEF enhancements | - | - | Docs:=13 | - | |
19.10.2 | S2-2500438 | CR | Approval | 23.256 CR0162 (Rel-19, 'F'): Addressing the EN on border-crossing point | Ericsson | Rel-19 | |||
19.10.2 | S2-2500475 | CR | Approval | 23.256 CR0167 (Rel-19, 'F'): Service operation update | CATT | Rel-19 | |||
19.10.2 | S2-2500829 | CR | Approval | 23.256 CR0176 (Rel-19, 'F'): Correction on UAV service operation description | Huawei, HiSilicon | Rel-19 | |||
19.10.2 | S2-2500831 | CR | Approval | 23.256 CR0178 (Rel-19, 'F'): Clarification of USS list provisioning | Huawei, HiSilicon | Rel-19 | |||
19.10.2 | S2-2500318 | CR | Approval | 23.256 CR0155 (Rel-19, 'F'): Clarification on reporting velocity in UAV location reporting procedure | China Mobile | Rel-19 | |||
19.10.2 | S2-2500830 | CR | Approval | 23.256 CR0177 (Rel-19, 'F'): Provisioning of static flight path information | Huawei, HiSilicon | Rel-19 | |||
19.10.2 | S2-2500440 | CR | Approval | 23.256 CR0164 (Rel-19, 'F'): Indicating optional steps of the pre-flight procedure | Ericsson | Rel-19 | |||
19.10.2 | S2-2500828 | CR | Approval | 23.256 CR0175 (Rel-19, 'F'): Correction on USS changeover aspects | Huawei, HiSilicon | Rel-19 | |||
19.10.2 | S2-2500385 | CR | Approval | 23.256 CR0156 (Rel-19, 'F'): Removing EN about border-crossing point | LG Electronics | Rel-19 | |||
19.10.2 | S2-2500439 | CR | Approval | 23.256 CR0163 (Rel-19, 'F'): Correcting the USS changeover procedure | Ericsson | Rel-19 | |||
19.10.2 | S2-2500441 | CR | Approval | 23.256 CR0165 (Rel-19, 'F'): Timestamping UAV's altitude information reports | Ericsson | Rel-19 | |||
19.10.2 | S2-2500513 | CR | Approval | 23.256 CR0171 (Rel-19, 'F'): Altitude reporting update | CATT | Rel-19 | |||
19.10.2 | S2-2500476 | CR | Approval | 23.502 CR5245 (Rel-19, 'F'): Update Namf_EventExposure | CATT | Rel-19 | |||
19.10.2 | - | - | - | KI#3: NTZ | - | - | Docs:=2 | - | |
19.10.2 | S2-2500113 | CR | Approval | 23.256 CR0154 (Rel-19, 'F'): Clarifications to NTZ support | Qualcomm Incorporated | Rel-19 | |||
19.10.2 | S2-2500114 | LS OUT | Approval | [DRAFT] LA on NTZ support in UAV UE | QUALCOMM Europe Inc. - Spain | Rel-19 | |||
19.11.1 | - | - | - | Study on UPF enhancement for Exposure And SBA Phase 2 (FS_UPEAS_Ph2) | - | - | Docs:=0 | - | |
19.11.2 | - | - | - | UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2) | - | - | Docs:=21 | - | |
19.11.2 | - | - | - | KI#1 | - | - | Docs:=2 | - | |
19.11.2 | S2-2500873 | CR | Approval | 23.501 CR6021 (Rel-19, 'F'): Clarification on the Operator configurable UPF capabilities | ZTE | Rel-19 | |||
19.11.2 | S2-2501046 | CR | Approval | 23.501 CR6056 (Rel-19, 'F'): Clarification to UPF selection based on specific UPF functionalities | Samsung | Rel-19 | |||
19.11.2 | - | - | - | KI#2 | - | - | Docs:=14 | - | |
19.11.2 | S2-2501045 | CR | Approval | 23.288 CR1368 (Rel-19, 'F'): Editorial Clarifications for AF retreival of UE public IP address | Samsung | Rel-19 | |||
19.11.2 | S2-2500163 | CR | Approval | 23.501 CR5894 (Rel-19, 'D'): Fix grammar and align text in clause 5.8.2.17 | Nokia | Rel-19 | |||
19.11.2 | S2-2500285 | CR | Approval | 23.501 CR5916 (Rel-19, 'F'): Update on QoS monitoring and reporting during UPF relocation and PDU session release | ETRI | Rel-19 | |||
19.11.2 | S2-2500596 | CR | Approval | 23.501 CR5980 (Rel-19, 'F'): Updates of UPF event exposure during N4 session release | Huawei, HiSilicon | Rel-19 | |||
19.11.2 | S2-2500237 | CR | Approval | 23.502 CR5216 (Rel-19, 'F'): Corrections for Any_UE and Group_ID data collection targets | Ericsson | Rel-19 | |||
19.11.2 | S2-2500598 | CR | Approval | 23.502 CR5261 (Rel-19, 'F'): Clarification of any UE and group UE cases | Huawei, HiSilicon | Rel-19 | |||
19.11.2 | S2-2501048 | CR | Approval | 23.502 CR5323 (Rel-19, 'F'): Clarification of UPF relocation and remaining data reporting and handling of Any UE case | Samsung | Rel-19 | |||
19.11.2 | S2-2500286 | CR | Approval | 23.502 CR5235 (Rel-19, 'F'): Update on UPF event exposure service during UPF relocation and N4 session release | ETRI | Rel-19 | |||
19.11.2 | S2-2500597 | CR | Approval | 23.502 CR5260 (Rel-19, 'F'): Updates of UPF event exposure during N4 session release | Huawei, HiSilicon | Rel-19 | |||
19.11.2 | S2-2500874 | CR | Approval | 23.502 CR5296 (Rel-19, 'F'): Correction on UPF event exposure service via SMF during UPF relocation and PDU Session release | ZTE | Rel-19 | |||
19.11.2 | S2-2500956 | CR | Approval | 23.502 CR5308 (Rel-19, 'F'): Fix figure in clause 4.15.4.5.5 and align clauses 4.15.4.5.6, 4.15.4.5.7 | Nokia | Rel-19 | |||
19.11.2 | S2-2501047 | CR | Approval | 23.502 CR5322 (Rel-19, 'F'): Correction to direct subscription of UPF event expsoure using UE IP address | Samsung | Rel-19 | |||
19.11.2 | S2-2501049 | CR | Approval | 23.502 CR5324 (Rel-19, 'F'): Corrections to UPF event exposure service description for UE NAT mapping | Samsung | Rel-19 | Affected clauses Missing. Revised to S2-2501068 | Revised | |
19.11.2 | S2-2501068 | CR | Approval | 23.502 CR5324R1 (Rel-19, 'F'): Corrections to UPF event exposure service description for UE NAT mapping | Samsung | Rel-19 | Revision of S2-2501049. Check Affected Clauses! | ||
19.11.2 | - | - | - | KI#3 | - | - | Docs:=5 | - | |
19.11.2 | S2-2500236 | CR | Approval | 23.501 CR5904 (Rel-19, 'F'): Handling of Headers corrections | Ericsson, Nokia, ETRI | Rel-19 | |||
19.11.2 | S2-2500271 | CR | Approval | 23.501 CR5913 (Rel-19, 'F'): Update of the description of handling of Payload Headers | China Mobile | Rel-19 | |||
19.11.2 | S2-2500284 | CR | Approval | 23.501 CR5915 (Rel-19, 'F'): Update on Handling of Payload Headers | ETRI | Rel-19 | |||
19.11.2 | S2-2500238 | CR | Approval | 23.502 CR5217 (Rel-19, 'F'): Support of Handling of Headers | Ericsson, Nokia, ETRI | Rel-19 | |||
19.11.2 | S2-2500270 | CR | Approval | 23.502 CR5227 (Rel-19, 'F'): Adding supporting of handling of Payload Headers functionality in UPF provisioning information | China Mobile | Rel-19 | |||
19.12.1 | - | - | - | Study on System aspects of 5G NR Femto (FS_5G_Femto) | - | - | Docs:=0 | - | |
19.12.2 | - | - | - | System aspects of 5G NR Femto (5G_Femto) | - | - | Docs:=0 | - | |
19.13.1 | - | - | - | Study on Multi-Access (DualSteer and ATSSS_Ph4) (FS_MASSS) | - | - | Docs:=0 | - | |
19.13.2 | - | - | - | Multi-Access (ATSSS_Ph4) (MASSS) | - | - | Docs:=17 | - | |
19.13.2 | - | - | - | Use of MPQUIC-UDP when MPQUIC-IP is supported | - | - | Docs:=2 | - | |
19.13.2 | S2-2500245 | DISCUSSION | Discussion | Support for CONNECT-UDP with MPQUIC-only option. | Ericsson, Apple, Google | ||||
19.13.2 | S2-2500246 | CR | Approval | 23.501 CR5907 (Rel-19, 'F'): Use of MPQUIC-UDP when MPQUIC-IP is supported | Ericsson, Apple, Google | Rel-19 | |||
19.13.2 | - | - | - | Capability handling | - | - | Docs:=3 | - | |
19.13.2 | S2-2500243 | CR | Approval | 23.501 CR5906 (Rel-19, 'F'): Updates to the ATSSS capability handling | Ericsson, Apple, Google, AT&T | Rel-19 | |||
19.13.2 | S2-2500244 | CR | Approval | 23.502 CR5220 (Rel-19, 'F'): Updates to the ATSSS capability handling | Ericsson, Apple, Google, AT&T | Rel-19 | |||
19.13.2 | S2-2500615 | CR | Approval | 23.501 CR5983 (Rel-19, 'F'): Update of UE ATSSS capability | ETRI | Rel-19 | |||
19.13.2 | - | - | - | QoS support | - | - | Docs:=2 | - | |
19.13.2 | S2-2500738 | CR | Approval | 23.501 CR5993 (Rel-19, 'F'): Correction on QoS Support | Huawei, HiSilicon | Rel-19 | |||
19.13.2 | S2-2501050 | CR | Approval | 23.501 CR6057 (Rel-19, 'F'): Corrections for QoS support for MPQUIC-E functionality | Samsung | Rel-19 | |||
19.13.2 | - | - | - | Other corrections | - | - | Docs:=10 | - | |
19.13.2 | S2-2501067 | CR | Approval | 23.503 CR1504 (Rel-19, 'F'): Clarification for PCF behaviour for generating matchall PCC rules for MA PDU Session | Samsung | Rel-19 | |||
19.13.2 | S2-2500459 | CR | Approval | 23.501 CR5959 (Rel-19, 'F'): Some corrections in MPQUIC steering functionalities | China Mobile | Rel-19 | |||
19.13.2 | S2-2500527 | CR | Approval | 23.501 CR5969 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | LG Electronics | Rel-19 | |||
19.13.2 | S2-2500528 | CR | Approval | 23.502 CR5251 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E in procedure | LG Electronics | Rel-19 | |||
19.13.2 | S2-2501073 | CR | Approval | 23.501 CR6061 (Rel-19, 'F'): Terminology alignment | Apple | Rel-19 | |||
19.13.2 | S2-2500736 | CR | Approval | 23.501 CR5992 (Rel-19, 'F'): Editorial Correction on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | |||
19.13.2 | S2-2500616 | CR | Approval | 23.501 CR5984 (Rel-19, 'D'): Clarification on steering functionalities description | ETRI | Rel-19 | |||
19.13.2 | S2-2500739 | CR | Approval | 23.502 CR5277 (Rel-19, 'F'): Editorial Correction on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | |||
19.13.2 | S2-2500737 | CR | Approval | 23.503 CR1487 (Rel-19, 'F'): Clarification on ATSSS feature in R19 | Huawei, HiSilicon | Rel-19 | |||
19.13.2 | S2-2500617 | CR | Approval | 23.503 CR1485 (Rel-19, 'D'): Editorial changes on provisioning PCC rule for ATSSS | ETRI | Rel-19 | |||
19.14.1 | - | - | - | Study on Architecture support of Ambient power-enabled Internet of Things (FS_AmbientIoT) | - | - | Docs:=61 | - | |
19.14.1 | - | - | - | LS | - | - | Docs:=0 | - | |
19.14.1 | - | - | - | LS in for information | - | - | Docs:=5 | - | |
19.14.1 | S2-2500049 | LS In | Information | LS from RAN WG2: LS on RAN2 outcome of Ambient IoT study | RAN WG2 (R2-2411263) | Rel-19 | |||
19.14.1 | S2-2500054 | LS In | Information | LS from RAN WG3: LS on RAN3 outcome of Ambient IoT study | RAN WG3 (R3-247923) | Rel-19 | |||
19.14.1 | S2-2500061 | LS In | Information | LS from SA WG1: Reply to LS on Further Clarification for Ambient IoT Security | SA WG1 (S1-244920) | Rel-19 | |||
19.14.1 | S2-2500021 | LS In | Information | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 (S3-245139) | Rel-19 | |||
19.14.1 | S2-2500018 | LS In | Information | LS from RAN WG2: LS on assistance information from the CN to the Reader for A-IoT | RAN WG2 (R2-2409412) | Rel-19 | |||
19.14.1 | - | - | - | LS from RAN WG2: LS on RAN2 agreements and assumptions for Ambient IoT | - | - | Docs:=3 | - | |
19.14.1 | S2-2500006 | LS In | Information | LS from RAN WG2: LS on RAN2 agreements and assumptions for Ambient IoT | RAN WG2 (R2-2406150) | Response drafted in S2-2500745 | |||
19.14.1 | S2-2500745 | LS OUT | Approval | [DRAFT] Reply LS on RAN WG2 agreements and assumptions for Ambient IoT | Samsung | Response to S2-2500006 | |||
19.14.1 | S2-2500007 | LS In | Information | LS from RAN WG1: Reply LS on Clarification of requirements for Ambient IoT | RAN WG1 (R1-2407364) | ||||
19.14.1 | - | - | - | LS from RAN WG2: LS on data block sizes for Ambient IoT | - | - | Docs:=3 | - | |
19.14.1 | S2-2500008 | LS In | Action | LS from RAN WG2: LS on data block sizes for Ambient IoT | RAN WG2 (R2-2407831) | Response drafted in S2-2500743 | |||
19.14.1 | S2-2500012 | LS In | Action | LS from RAN WG1: Reply LS to RAN WG2 on data block sizes for Ambient IoT | RAN WG1 (R1-2409250) | Rel-19 | |||
19.14.1 | S2-2500743 | LS OUT | Approval | [DRAFT] Reply LS on data block sizes for Ambient IoT | Samsung | Response to S2-2500008 | |||
19.14.1 | - | - | - | LS from RAN WG2: Further LS on Assistance information from CN to the reader | - | - | Docs:=3 | - | |
19.14.1 | S2-2500078 | LS In | Action | LS from RAN WG2: Further LS on Assistance information from CN to the reader | RAN WG2 (R2-2411232) | Rel-19 | Responses drafted in S2-2500648, S2-2500938. | ||
19.14.1 | S2-2500648 | LS OUT | Approval | [DRAFT] Reply LS on Assistance Information from CN to the Reader | ZTE | Rel-19 | Response to S2-2500078 | ||
19.14.1 | S2-2500938 | LS OUT | Approval | [DRAFT] LS reply on Further LS on Assistance information from CN to the reader | Huawei, HiSilicon | Rel-19 | Response to S2-2500078 | ||
19.14.1 | - | - | - | LS out from SA2 | - | - | Docs:=5 | - | |
19.14.1 | S2-2500329 | LS OUT | Approval | [DRAFT] LS on BS Reader selection | CATT | Rel-19 | |||
19.14.1 | S2-2500330 | LS OUT | Approval | [DRAFT] LS on AIoT security aspects | CATT | Rel-19 | |||
19.14.1 | S2-2500429 | LS OUT | Approval | [DRAFT] LS on Indicator in A-IoT Paging | Ericsson | Rel-19 | |||
19.14.1 | S2-2500430 | LS OUT | Approval | [DRAFT] LS on Device Subscription Data | Ericsson | Rel-19 | |||
19.14.1 | S2-2500937 | LS OUT | Approval | [DRAFT] LS on further SA WG2 Ambient IoT TR conclusion update | Huawei, HiSilicon | Rel-19 | |||
19.14.1 | - | - | - | TR contributions | - | - | Docs:=0 | - | |
19.14.1 | - | - | - | EN: Whether and how AIOTF selects BS readers or AIOT RAN nodes in topology 1 needs coordination between SA2 and RAN WG(s) | - | - | Docs:=3 | - | |
19.14.1 | S2-2500333 | P-CR | Approval | 23.700-13: Removing one EN related to BS reader selection in KI#1. | China Mobile | Rel-19 | |||
19.14.1 | S2-2500712 | P-CR | Approval | 23.700-13: Topic#2, Conclusions on AIoT KI#1 for Topology 1. | Samsung | Rel-19 | |||
19.14.1 | S2-2500345 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#1 . | Vivo | Rel-19 | |||
19.14.1 | - | - | - | EN: How the aggregation can be done is FFS | - | - | Docs:=4 | - | |
19.14.1 | S2-2500428 | P-CR | Approval | 23.700-13: KI#1#3 Conclusion Update of Aggregation. | Ericsson | Rel-19 | |||
19.14.1 | S2-2500463 | P-CR | Approval | 23.700-13: Conclusions for KI#1 on the aggregation aspects (Topic#3). | Nokia | Rel-19 | |||
19.14.1 | S2-2500585 | P-CR | Approval | 23.700-13: KI#1 Addressing EN on AIoT service responses aggregation. | Lenovo, Futurewei, NEC | Rel-19 | |||
19.14.1 | S2-2500646 | P-CR | Approval | 23.700-13: Address EN for Aggregation. | ZTE | Rel-19 | |||
19.14.1 | - | - | - | EN: It is FFS whether to support any other messages besides Inventory Response, Command (e.g. Read and Write) Request and Response over AIoT Device NAS layer | - | - | Docs:=4 | - | |
19.14.1 | S2-2500970 | P-CR | Approval | 23.700-13: Conclusion update on messages over AIoT device NAS. | InterDigital Inc. | Rel-19 | |||
19.14.1 | S2-2500426 | P-CR | Approval | 23.700-13: KI#3 Conclusion Update of AIoT Device NAS Layer. | Ericsson | Rel-19 | |||
19.14.1 | S2-2500769 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs of Topic4. | HONOR | Rel-19 | |||
19.14.1 | S2-2500710 | P-CR | Approval | 23.700-13: Topic #4, Conclusions on AIoT KI#1 for Messages. | Samsung | Rel-19 | |||
19.14.1 | - | - | - | EN: How this AIOT device related information is used is FFS and Where to store the AIOT device related information is FFS | - | - | Docs:=4 | - | |
19.14.1 | S2-2500340 | P-CR | Approval | 23.700-13: Removing two ENs related to Ambient device-related context storage in KI#1. | China Mobile | Rel-19 | |||
19.14.1 | S2-2500464 | P-CR | Approval | 23.700-13: Conclusions for KI#1 on the device context info (Topic#5). | Nokia | Rel-19 | |||
19.14.1 | S2-2500586 | P-CR | Approval | 23.700-13: KI#1 Addressing EN on AIoT device related information. | Lenovo, China Telecom | Rel-19 | |||
19.14.1 | S2-2500969 | P-CR | Approval | 23.700-13: Conclusion update on AIoT context information. | InterDigital Inc. | Rel-19 | |||
19.14.1 | - | - | - | EN: The length of Identifier is fixed or dynamical is FFS | - | - | Docs:=2 | - | |
19.14.1 | S2-2500346 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#2 . | Vivo | Rel-19 | |||
19.14.1 | S2-2500711 | P-CR | Approval | 23.700-13: Topic #7, Conclusions on AIoT KI#2 Device ID. | Samsung | Rel-19 | |||
19.14.1 | - | - | - | EN: Where to store the AIoT device subscription is FFS | - | - | Docs:=2 | - | |
19.14.1 | S2-2500465 | P-CR | Approval | 23.700-13: Conclusions for KI#2 on the device subscription-like info (Topic#10). | Nokia | Rel-19 | |||
19.14.1 | S2-2500973 | P-CR | Approval | 23.700-13: Clarification on storage of Ambient IoT related subscription data. | NTT DOCOMO, Deutsche Telekom, T-Mobile USA, Huawei, HiSilicon | Rel-19 | |||
19.14.1 | - | - | - | EN: It is FFS whether and how to support enabling temporarily disabled AIoT devices | - | - | Docs:=4 | - | |
19.14.1 | S2-2500374 | P-CR | Approval | 23.700-13: KI#3, Conclusion update on enabling temporarily disabled AIoT devices. | OPPO | Rel-19 | |||
19.14.1 | S2-2500425 | P-CR | Approval | 23.700-13: KI#3 Conclusion Update of Enabling Temporarily Disabled AIoT devices. | Ericsson | Rel-19 | |||
19.14.1 | S2-2500968 | P-CR | Approval | 23.700-13: Conclusion update for enabling temporarily disabled AIoT device. | InterDigital Inc. | Rel-19 | |||
19.14.1 | S2-2500347 | P-CR | Approval | 23.700-13: Conclusion update to fix the category1 ENs for KI#3 . | Vivo | Rel-19 | |||
19.14.1 | - | - | - | EN: If the “command-only” case applies, pending SA3, if a command and paging can be performed in a single operation, then an AIoT specific NAS message may be included in the request | - | - | Docs:=1 | - | |
19.14.1 | S2-2500647 | P-CR | Approval | 23.700-13: Address EN Regarding Command-only Service Operation. | ZTE | Rel-19 | |||
19.14.1 | - | - | - | Category 2 editor’ notes | - | - | Docs:=5 | - | |
19.14.1 | S2-2500925 | P-CR | Approval | 23.700-13: Editor s Notes resolutions during the normative phase or future releases (Cat-2 & Cat-3 ENs). | Huawei, HiSilicon | Rel-19 | |||
19.14.1 | S2-2500328 | P-CR | Approval | 23.700-13: Resolution of Editor s notes with other WGs dependencies. | CATT | Rel-19 | |||
19.14.1 | S2-2500545 | P-CR | Approval | 23.700-13: KI#1, Resolving ENs on AIoT assistance information. | Lenovo | Rel-19 | |||
19.14.1 | S2-2500798 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs about assistance information (Cat 2). | HONOR | Rel-19 | |||
19.14.1 | S2-2500339 | P-CR | Approval | 23.700-13: Removing one EN related to How addressing works for UP traffic via AMF in KI#1. | China Mobile | Rel-19 | |||
19.14.1 | - | - | - | Category 3 editor’ notes | - | - | Docs:=1 | - | |
19.14.1 | S2-2500375 | P-CR | Approval | 23.700-13: T2 conclusion clarification. | OPPO | Rel-19 | |||
19.14.1 | - | - | - | Contributions exceeding TU | - | - | Docs:=12 | - | |
19.14.1 | S2-2500338 | P-CR | Approval | 23.700-13: Conclusions on the KI#1 general part correcting NGAP description. | China Mobile | Rel-19 | |||
19.14.1 | S2-2500542 | P-CR | Approval | 23.700-13: KI#1, Nx transport layer association establishment in Topology 1. | Lenovo | Rel-19 | |||
19.14.1 | S2-2500713 | P-CR | Approval | 23.700-13: Topic #10, Conclusions on AIoT KI#2 for Subscription Management. | Samsung | Rel-19 | |||
19.14.1 | S2-2500720 | P-CR | Approval | 23.700-13: Topic #9, Conclusions on AIoT KI#3 for Command-only. | Samsung | Rel-19 | |||
19.14.1 | S2-2500721 | P-CR | Approval | 23.700-13: Topic #5, Conclusions on AIoT KI#1 for AIoT Device related Information. | Samsung | Rel-19 | |||
19.14.1 | S2-2500722 | P-CR | Approval | 23.700-13: Topic #3, Conclusions on AIoT KI#1 for aggregation. | Samsung | Rel-19 | |||
19.14.1 | S2-2500788 | P-CR | Approval | 23.700-13: KI#3 Conclusion update in clause 8.3.4. | HONOR | Rel-19 | |||
19.14.1 | S2-2500427 | P-CR | Approval | 23.700-13: KI#2 Conclusion Update of Device Subscription Data. | Ericsson | Rel-19 | |||
19.14.1 | S2-2500546 | P-CR | Approval | 23.700-13: KI#1, Document the cease of progress on Topology 2. | Lenovo | Rel-19 | |||
19.14.1 | S2-2500714 | P-CR | Approval | 23.700-13: Topic #8, Conclusions on AIoT KI#3 for enabling temporarily disabled AIoT devices . | Samsung | Rel-19 | |||
19.14.1 | S2-2500933 | P-CR | Approval | 23.700-13: Editor s Notes resolutions in the TR (Cat-1 ENs). | Huawei, HiSilicon | Rel-19 | |||
19.14.1 | S2-2500751 | P-CR | Approval | 23.700-13: KI#1 Conclusion update to address the ENs of Topic5. | HONOR | Rel-19 | |||
19.14.2 | - | - | - | Architecture support of Ambient power-enabled Internet of Things (AmbientIoT) | - | - | Docs:=41 | - | |
19.14.2 | - | - | - | Contributions to be handled | - | - | Docs:=31 | - | |
19.14.2 | S2-2500378 | OTHER | Approval | Reference, Term and Abbreviations. | OPPO | Rel-19 | |||
19.14.2 | S2-2500379 | OTHER | Approval | NF description for AIoT. | OPPO | Rel-19 | |||
19.14.2 | S2-2500466 | OTHER | Approval | PCR for KI#1 on the aggregation aspects (Topic#3). | Nokia | Rel-19 | |||
19.14.2 | S2-2500467 | OTHER | Approval | PCR for KI#1 on the device context info (Topic#5). | Nokia | Rel-19 | |||
19.14.2 | S2-2500468 | OTHER | Approval | PCR for KI#2 on the device subscription-like info (Topic#10). | Nokia | Rel-19 | |||
19.14.2 | S2-2500469 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | CATT | Rel-19 | |||
19.14.2 | S2-2500470 | OTHER | Approval | PCR to TS 23.xyz: Assistance Information used by AIoT RAN. | CATT | Rel-19 | |||
19.14.2 | S2-2500477 | OTHER | Approval | PCR to TS 23.xyz: AIoT device Identifiers. | Vivo | Rel-19 | |||
19.14.2 | S2-2500481 | OTHER | Approval | PCR to TS 23.xyz: NFs Services. | Vivo | Rel-19 | |||
19.14.2 | S2-2500486 | OTHER | Approval | AIoT T1 Protocol Stack. | OPPO | Rel-19 | |||
19.14.2 | S2-2500520 | OTHER | Approval | AMF Services for Ambient IoT service. | China Mobile | ||||
19.14.2 | S2-2500521 | OTHER | Approval | AMF function enhancement for Ambient IoT service. | China Mobile | ||||
19.14.2 | S2-2500522 | OTHER | Approval | Reader selection for Ambient IoT service request. | China Mobile | ||||
19.14.2 | S2-2500642 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | ZTE | Rel-19 | |||
19.14.2 | S2-2500643 | OTHER | Approval | PCR to TS 23.xyz: Assistance Information Used by AIoT RAN. | ZTE | Rel-19 | |||
19.14.2 | S2-2500645 | OTHER | Approval | PCR to TS 23.xyz: AIoT Reader Selection. | ZTE | Rel-19 | |||
19.14.2 | S2-2500661 | OTHER | Approval | PCR to TS 23.xyz: Network Functions: AIOTF and AIOTDMF. | Vivo | Rel-19 | |||
19.14.2 | S2-2500734 | OTHER | Approval | PCR to TS 23.xyz: NEF Services. | Samsung | Rel-19 | |||
19.14.2 | S2-2500735 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | Samsung | Rel-19 | |||
19.14.2 | S2-2500742 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Services. | Samsung | Rel-19 | |||
19.14.2 | S2-2500851 | OTHER | Approval | PCR to TS 23.xyz: AIoT Device entity. | Spreadtrum, UNISOC | Rel-19 | |||
19.14.2 | S2-2500852 | OTHER | Approval | PCR to TS 23.xyz: AIoTF entity. | Spreadtrum, UNISOC | Rel-19 | |||
19.14.2 | S2-2500931 | OTHER | Approval | PCR to TS 23.xyz: Network Functions Services. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500932 | OTHER | Approval | PCR to TS 23.xyz: Subscription Management for Ambient IoT Device. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500935 | OTHER | Approval | TS skeleton of Ambient IoT specification. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500936 | OTHER | Approval | PCR to TS 23.xyz: scope of Ambient IoT Specification. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500939 | OTHER | Approval | PCR to TS 23.xyz: Ambient IoT Architecture model and concepts. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500964 | OTHER | Approval | Ambient IoT Services. | InterDigital Inc. | ||||
19.14.2 | S2-2500965 | OTHER | Approval | Ambient IoT Reader Selection. | InterDigital Inc. | Rel-19 | |||
19.14.2 | S2-2500966 | OTHER | Approval | Assistance information for AIoT RAN. | InterDigital Inc. | Rel-19 | |||
19.14.2 | S2-2500987 | OTHER | Approval | PCR to TS 23.xyz: Text on permanent Ambient IoT Identifiers. | NTT DOCOMO, Deutsche Telekom, T-Mobile USA | Rel-19 | |||
19.14.2 | - | - | - | Contributions exceeding TU | - | - | Docs:=10 | - | |
19.14.2 | S2-2500478 | OTHER | Approval | PCR to TS 23.xyz: Protocol Stacks. | Vivo | Rel-19 | |||
19.14.2 | S2-2500479 | OTHER | Approval | PCR to TS 23.xyz: Procedure for inventory. | Vivo | Rel-19 | |||
19.14.2 | S2-2500480 | OTHER | Approval | PCR to TS 23.xyz: Procedure for inventory. | Vivo | Rel-19 | |||
19.14.2 | S2-2500644 | OTHER | Approval | PCR to TS 23.xyz: NEF Services. | ZTE | Rel-19 | |||
19.14.2 | S2-2500926 | OTHER | Approval | PCR for TS 23.xyz: Ambient IoT Device Identifier. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500927 | OTHER | Approval | PCR to TS 23.xyz: Procedure for Ambient IoT Inventory Service. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500928 | OTHER | Approval | PCR to TS 23.xyz: Procedure for Ambient IoT Command Service. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500929 | OTHER | Approval | PCR to TS 23.xyz: Procedures for AIOTF and AIoT Reader Communication. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500930 | OTHER | Approval | PCR to TS 23.xyz: AF Authorization for Ambient IoT Services. | Huawei, HiSilicon | Rel-19 | |||
19.14.2 | S2-2500940 | DRAFTCR | Approval | Ambient IoT interfaces and reference points | Huawei, HiSilicon | Rel-19 | |||
19.15.1 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (FS_AIML_CN) | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (AIML_CN) | - | - | Docs:=139 | - | |
19.15.2 | - | - | - | KI#1: AIML support for LMF positioning | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | Liaisons | - | - | Docs:=3 | - | |
19.15.2 | S2-2500005 | LS In | Information | LS from RAN WG1: Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | RAN WG1 (R1-2405578) | ||||
19.15.2 | S2-2500200 | LS OUT | Approval | [DRAFT] LS to RAN on AIML positioning | vivo | Rel-19 | |||
19.15.2 | S2-2500399 | LS OUT | Approval | [DRAFT] LS on LMF-based AI/ML Positioning | Ericsson | Rel-19 | |||
19.15.2 | - | - | - | TS 23.273: General | - | - | Docs:=3 | - | |
19.15.2 | S2-2500194 | CR | Approval | 23.273 CR0640 (Rel-19, 'F'): Adding missing parts for AI/ML based positioning | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | |||
19.15.2 | S2-2500229 | CR | Approval | 23.273 CR0643 (Rel-19, 'C'): Updates to AI/ML-based positioning procedures | Apple | Rel-19 | |||
19.15.2 | S2-2501017 | CR | Approval | 23.273 CR0666 (Rel-19, 'F'): Adapting the data collection procedure for performance monitoring | Xiaomi | Rel-19 | Check Affected Clauses! | ||
19.15.2 | - | - | - | TS 23.273: Data Exposure/ NWDAF Input data collection | - | - | Docs:=6 | - | |
19.15.2 | S2-2500352 | CR | Approval | 23.273 CR0644 (Rel-19, 'C'): Updates to data exposure service for AI/ML-based positioning | Apple | Rel-19 | |||
19.15.2 | S2-2500588 | CR | Approval | 23.273 CR0650 (Rel-19, 'B'): Updates of input data collection from LMF | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | S2-2500834 | CR | Approval | 23.273 CR0658 (Rel-19, 'F'): Clarification on model performance monitoring for LMF-based AIML Positioning | CATT | Rel-19 | |||
19.15.2 | S2-2501018 | CR | Approval | 23.273 CR0667 (Rel-19, 'F'): Clarification on Data collection from LMF requested by NWDAF | Xiaomi | Rel-19 | |||
19.15.2 | S2-2500629 | CR | Approval | 23.273 CR0652 (Rel-19, 'B'): Updates on input data of AI/ML positioning model performance monitoring | China Telecom | Rel-19 | |||
19.15.2 | S2-2500693 | CR | Approval | 23.273 CR0654 (Rel-19, 'C'): KI#1 - Further clarification on input data for ML model training for AI/ML positioning | Lenovo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.273: General Description and Model Retrieval | - | - | Docs:=4 | - | |
19.15.2 | S2-2500083 | CR | Approval | 23.288 CR1302 (Rel-19, 'B'): Modifications on ML Model retrieval service | ZTE | Rel-19 | |||
19.15.2 | S2-2500088 | CR | Approval | 23.273 CR0635 (Rel-19, 'B'): ML Model retrieval from ADRF | ZTE | Rel-19 | Check Affected Clauses! | ||
19.15.2 | S2-2500228 | CR | Approval | 23.273 CR0642 (Rel-19, 'C'): Updates to AI/ML-based positioning general descriptions | Apple | Rel-19 | |||
19.15.2 | S2-2500833 | CR | Approval | 23.273 CR0657 (Rel-19, 'F'): Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF | CATT | Rel-19 | |||
19.15.2 | - | - | - | TS 23.273: Data collection from RAN and UE | - | - | Docs:=4 | - | |
19.15.2 | S2-2500132 | CR | Approval | 23.273 CR0637 (Rel-19, 'B'): KI#1: Considering RAN load when collecting data to train model for positioning | Nokia | Rel-19 | |||
19.15.2 | S2-2500192 | CR | Approval | 23.273 CR0638 (Rel-19, 'F'): Clean up the ENs regarding AI/ML positioning | Qualcomm Incorporated | Rel-19 | |||
19.15.2 | S2-2500832 | CR | Approval | 23.273 CR0656 (Rel-19, 'F'): Clarification on data collection by LMF for LMF-based AIML Positioning | CATT | Rel-19 | |||
19.15.2 | S2-2501020 | CR | Approval | 23.273 CR0668 (Rel-19, 'F'): To remove the EN on limit of number of UEs in clause 6.22.2 | Xiaomi | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 General | - | - | Docs:=1 | - | |
19.15.2 | S2-2501037 | CR | Approval | 23.273 CR0669 (Rel-19, 'B'): Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note. | Ericsson | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 Performance monitoring | - | - | Docs:=1 | - | |
19.15.2 | S2-2500692 | CR | Approval | 23.288 CR1364 (Rel-19, 'C'): KI#1 - Further clarification on ML Model performance monitoring for AI/ML positioning | Lenovo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 and TS 23.502 | - | - | Docs:=3 | - | |
19.15.2 | S2-2500198 | CR | Approval | 23.501 CR5635R2 (Rel-19, 'B'): NWDAF model provision for AI positioning | Vivo | Rel-19 | Revision of S2-2411551 | ||
19.15.2 | S2-2501019 | CR | Approval | 23.502 CR5316 (Rel-19, 'F'): Update UDM to support user consent of data collection for performance monitoring | Xiaomi | Rel-19 | Confirm Spec version used - CR states {19.1.0}! | ||
19.15.2 | S2-2500199 | CR | Approval | 23.502 CR5011R2 (Rel-19, 'B'): NWDAF registration and discovery for AI positioning | Vivo | Rel-19 | Revision of S2-2411552 | ||
19.15.2 | - | - | - | KI#2: Vertical Federated Learning | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | General | - | - | Docs:=2 | - | |
19.15.2 | S2-2500196 | CR | Approval | 23.288 CR1323 (Rel-19, 'F'): Remove ENs unrelated to the exception list | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | |||
19.15.2 | S2-2500195 | CR | Approval | 23.288 CR1322 (Rel-19, 'F'): Adding missing parts for VFL | Vivo(rapporteur), MediaTek Inc(rapporteur) | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: Definitions | - | - | Docs:=2 | - | |
19.15.2 | S2-2500082 | CR | Approval | 23.288 CR1301 (Rel-19, 'B'): VFL definitions | ZTE | Rel-19 | |||
19.15.2 | S2-2500303 | CR | Approval | 23.288 CR1331 (Rel-19, 'B'): The related definitions for VFL and HFL | China Mobile | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: Registration and Discovery | - | - | Docs:=4 | - | |
19.15.2 | S2-2500336 | CR | Approval | 23.288 CR1335 (Rel-19, 'B'): Resolve some ENs related to the VFL server and client Registration and Discovery | OPPO | Rel-19 | |||
19.15.2 | S2-2500566 | CR | Approval | 23.288 CR1346 (Rel-19, 'B'): Update Registration and Discovery procedure to include trusted AF as server case | LG Electronics | Rel-19 | |||
19.15.2 | S2-2501070 | CR | Approval | 23.288 CR1370 (Rel-19, 'B'): KI#2 update to registration and discovery procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! | ||
19.15.2 | S2-2500630 | CR | Approval | 23.288 CR1352 (Rel-19, 'B'): Updates on VFL server discovery and VFL preparation procedure | China Telecom | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: VFL preparation | - | - | Docs:=3 | - | |
19.15.2 | S2-2500337 | CR | Approval | 23.288 CR1336 (Rel-19, 'B'): Add the trusted AF as the server case in the VFL preparation procedure | OPPO | Rel-19 | |||
19.15.2 | S2-2500432 | CR | Approval | 23.288 CR1341 (Rel-19, 'B'): Sample ID intersection by NEF during the VFL preparation in untrusted AF VFL server scenario | Samsung, | Rel-19 | |||
19.15.2 | S2-2501071 | CR | Approval | 23.288 CR1371 (Rel-19, 'B'): KI#2 update to VFL preparation procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! | ||
19.15.2 | - | - | - | TS 23.288: VFL training | - | - | Docs:=6 | - | |
19.15.2 | S2-2500301 | CR | Approval | 23.288 CR1330 (Rel-19, 'B'): Clarifications on VFL general procedure | China Mobile | Rel-19 | Confirm Spec version used - CR states {}! | ||
19.15.2 | S2-2500335 | CR | Approval | 23.288 CR1334 (Rel-19, 'B'): Resolve some ENs in the vertical federated learning training procedure | OPPO | Rel-19 | |||
19.15.2 | S2-2500460 | CR | Approval | 23.288 CR1342 (Rel-19, 'C'): Sample update during VFL training | Apple | Rel-19 | |||
19.15.2 | S2-2500631 | CR | Approval | 23.288 CR1353 (Rel-19, 'B'): Updates on VFL training and VFL inference to remove ENs | China Telecom | Rel-19 | |||
19.15.2 | S2-2501069 | CR | Approval | 23.288 CR1369 (Rel-19, 'B'): KI#2 update to VFL training procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! | ||
19.15.2 | S2-2500398 | CR | Approval | 23.288 CR1338 (Rel-19, 'C'): Resolving ENs for VFL | Ericsson, Lenovo, InterDigital, [OPPO] | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: Accuracy monitoring | - | - | Docs:=2 | - | |
19.15.2 | S2-2500655 | CR | Approval | 23.288 CR1355 (Rel-19, 'B'): Enhancements for the accuracy monitoring of VFL training | Vivo | Rel-19 | |||
19.15.2 | S2-2500677 | CR | Approval | 23.288 CR1362 (Rel-19, 'B'): VFL Accuracy Monitoring | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: Inference | - | - | Docs:=4 | - | |
19.15.2 | S2-2500334 | CR | Approval | 23.288 CR1333 (Rel-19, 'B'): Resolve some ENs in the vertical federated learning inference procedure | OPPO | Rel-19 | |||
19.15.2 | S2-2501039 | CR | Approval | 23.288 CR1367 (Rel-19, 'B'): KI#2 update to VFL inference procedure | InterDigital | Rel-19 | Missing CR Number - CR states -! | ||
19.15.2 | S2-2500140 | CR | Approval | 23.288 CR1315 (Rel-19, 'B'): KI#2: Updates to VFL inference procedures e.g to address trusted AF and handling of parameters from analytics request | Nokia | Rel-19 | |||
19.15.2 | S2-2500676 | CR | Approval | 23.288 CR1361 (Rel-19, 'B'): Updates to VFL Inference Procedure | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288: Service Operations | - | - | Docs:=1 | - | |
19.15.2 | S2-2500145 | CR | Approval | 23.288 CR1236R5 (Rel-19, 'B'): KI#2: VFL services | Nokia | Rel-19 | Revision of S2-2412937 | ||
19.15.2 | - | - | - | TS 23.288 General Description | - | - | Docs:=2 | - | |
19.15.2 | S2-2500268 | CR | Approval | 23.288 CR1329 (Rel-19, 'F'): EN removal for clarification of VFL high level description | KDDI | Rel-19 | |||
19.15.2 | S2-2500565 | CR | Approval | 23.288 CR1345 (Rel-19, 'B'): Update of General Description for VFL | LG Electronics | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 Multi procedures | - | - | Docs:=5 | - | |
19.15.2 | S2-2500232 | CR | Approval | 23.288 CR1327 (Rel-19, 'B'): Support of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, | Rel-19 | |||
19.15.2 | S2-2500267 | CR | Approval | 23.288 CR1328 (Rel-19, 'B'): VFL procedure update for untrusted AF case. | KDDI | Rel-19 | |||
19.15.2 | S2-2500500 | CR | Approval | 23.288 CR1343 (Rel-19, 'B'): KI#2 Removing ENs regarding the roles of NEF | NTT DOCOMO | Rel-19 | |||
19.15.2 | S2-2500567 | CR | Approval | 23.288 CR1347 (Rel-19, 'B'): Update Preparation and Training Procedure for VFL | LG Electronics | Rel-19 | |||
19.15.2 | S2-2500691 | CR | Approval | 23.288 CR1363 (Rel-19, 'B'): KI2: Addressing ENs for VFL . | Lenovo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=1 | - | |
19.15.2 | S2-2500561 | CR | Approval | 23.501 CR5978 (Rel-19, 'B'): NWDAF discovery and selection parameters | LG Electronics | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 General description | - | - | Docs:=1 | - | |
19.15.2 | S2-2500302 | CR | Approval | 23.501 CR5918 (Rel-19, 'B'): VFL alignment in 23.501 | China Mobile | Rel-19 | |||
19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
19.15.2 | S2-2500266 | CR | Approval | 23.502 CR5226 (Rel-19, 'B'): NRF enhancement for VFL inference service discovery | KDDI | Rel-19 | |||
19.15.2 | S2-2500660 | CR | Approval | 23.502 CR5266 (Rel-19, 'B'): Adding VFL related services supported by NEF and AF | Vivo | Rel-19 | |||
19.15.2 | - | - | - | KI#3: PCC related enhancements | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | TS 23.288 | - | - | Docs:=6 | - | |
19.15.2 | S2-2500188 | CR | Approval | 23.288 CR1321 (Rel-19, 'C'): Enabling QoS and Policy Assistance Analytics analyse and predict QoE for certain user plane latency | Verizon, Oracle | Rel-19 | WI Code should be AIML_CN! | ||
19.15.2 | S2-2500231 | CR | Approval | 23.288 CR1326 (Rel-19, 'F'): Corrections on QoS and policy assistance analytics | Samsung, Ericsson | Rel-19 | |||
19.15.2 | S2-2500317 | CR | Approval | 23.288 CR1332 (Rel-19, 'B'): Update of input data for QoS and Policy Assistance Analytics | China Mobile | Rel-19 | |||
19.15.2 | S2-2500353 | CR | Approval | 23.288 CR1337 (Rel-19, 'F'): QoS and Policy Assistance Analytics update | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! | ||
19.15.2 | S2-2500402 | CR | Approval | 23.288 CR1340 (Rel-19, 'F'): Resolving ENs for QoS and policy assistance analytics | Ericsson | Rel-19 | |||
19.15.2 | S2-2500838 | CR | Approval | 23.288 CR1255R2 (Rel-19, 'F'): Support of QoS policy assistance information analytics | CATT | Rel-19 | Revision of S2-2411512 | ||
19.15.2 | - | - | - | TS 23.503 | - | - | Docs:=2 | - | |
19.15.2 | S2-2500230 | CR | Approval | 23.503 CR1328R3 (Rel-19, 'B'): Support for NWDAF-assisted policy control and QoS | Samsung | Rel-19 | Revision of S2-2411618 | ||
19.15.2 | S2-2500401 | CR | Approval | 23.503 CR1303R3 (Rel-19, 'B'): PCF use of QoS and policy assistance information analytic | Ericsson | Rel-19 | Revision of S2-2411643 | ||
19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=1 | - | |
19.15.2 | S2-2500354 | CR | Approval | 23.502 CR5237 (Rel-19, 'B'): QFI Change event | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! | ||
19.15.2 | - | - | - | KI#4: Signalling storm mitigation | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | TS 23.288 Signalling Storm Analytics | - | - | Docs:=2 | - | |
19.15.2 | S2-2500102 | CR | Approval | 23.288 CR1313 (Rel-19, 'F'): Clarifying Signalling Storm Analytics | Huawei, HiSilicon, China Telecom, SK Telecom, Verizon, NTT DOCOMO | Rel-19 | |||
19.15.2 | S2-2500633 | CR | Approval | 23.288 CR1354 (Rel-19, 'F'): Clarification and alignment on signalling storm analytics | China Telecom | Rel-19 | |||
19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
19.15.2 | S2-2500355 | CR | Approval | 23.502 CR5238 (Rel-19, 'F'): Exposure of control plane signalling information from NFs | NTT DOCOMO | Rel-19 | WI Code should be AIML_CN! | ||
19.15.2 | S2-2500153 | CR | Approval | 23.502 CR5200 (Rel-19, 'B'): KI#4 Resolve open issues for mitigation actions | Nokia | Rel-19 | |||
19.15.2 | - | - | - | UE data collection related liasons | - | - | Docs:=8 | - | |
19.15.2 | S2-2500017 | LS In | Action | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-246299) | Rel-19 | |||
19.15.2 | S2-2500020 | LS In | Information | LS from SA WG3: Reply LS on AIML data collection | SA WG3 (S3-245138) | Rel-19 | |||
19.15.2 | S2-2500025 | LS In | Action | LS from RAN WG2: Reply LS to SA WG2 on AIML data collection | RAN WG2 (R2-2411152) | Rel-19 | |||
19.15.2 | S2-2500024 | LS In | Action | LS from RAN WG2: Reply LS to SA WG5 on AIML data collection | RAN WG2 (R2-2411114) | Rel-19 | |||
19.15.2 | S2-2500026 | LS In | Information | LS from RAN WG3: Reply LS on AIML data collection | RAN WG3 (R3-247801) | Rel-19 | |||
19.15.2 | S2-2500055 | LS In | Action | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN (RP-243316) | Rel-19 | |||
19.15.2 | S2-2500069 | LS In | Information | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-247219) | Rel-19 | |||
19.15.2 | S2-2500071 | LS In | Information | LS from SA WG5: Reply LS on AIML Data Collection | SA WG5 (S5-247336) | Rel-19 | |||
19.15.2 | - | - | - | General | - | - | Docs:=7 | - | |
19.15.2 | S2-2500004 | LS In | Action | LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3186 (ex Y.IMT2020-DJLML) 'Requirements and framework for distributed joint learning to enable machine learning in future networks including IMT-2020' | ITU-T SG13 (SG13-LS170) | ||||
19.15.2 | S2-2500009 | LS In | Action | LS from SA WG5: LS reply on terminology definitions for AI-ML in NG-RAN | SA WG5 (S5-244660) | ||||
19.15.2 | S2-2500041 | LS In | Information | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 (R1-2410922) | Rel-19 | Responses drafted in S2-2500320, S2-2500827 | ||
19.15.2 | S2-2500320 | LS OUT | Approval | [DRAFT] Reply LS on Signalling feasibility of data set and parameter sharing | Qualcomm Germany | Rel-19 | Response to S2-2500041 | ||
19.15.2 | S2-2500827 | LS OUT | Approval | [DRAFT] Reply LS on Signalling feasibility of data set and parameter sharing | Apple | Rel-19 | Response to S2-2500041 | ||
19.15.2 | S2-2500081 | CR | Approval | 23.501 CR5882 (Rel-19, 'B'): KI#1 and KI#2 alignment | ZTE | Rel-19 | |||
19.15.2 | S2-2500501 | CR | Approval | 23.288 CR1344 (Rel-19, 'C'): Addition of delay threshold match indication | Verizon, Oracle | Rel-19 | WI Code should be AIML_CN! | ||
19.15.2 | - | - | - | Exceeding quota or not in scope of e-meeting | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | KI#1: AIML support for LMF positioning | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | TS 23.273 General | - | - | Docs:=2 | - | |
19.15.2 | S2-2500197 | CR | Approval | 23.273 CR0641 (Rel-19, 'B'): Resolution of editor s notes related to data collection and model retrieval | Vivo | Rel-19 | |||
19.15.2 | S2-2500591 | CR | Approval | 23.273 CR0651 (Rel-19, 'F'): Updates of MTLF discovery and selection for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.273 Data Exposure/ NWDAF Input data collection | - | - | Docs:=2 | - | |
19.15.2 | S2-2500112 | CR | Approval | 23.273 CR0636 (Rel-19, 'B'): KI#1: Resolving open issues for LMF data exposure | Nokia | Rel-19 | |||
19.15.2 | S2-2500654 | CR | Approval | 23.273 CR0653 (Rel-19, 'B'): Update input data to adapt model performance monitoring | Vivo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.273 Data collection from RAN and UE | - | - | Docs:=1 | - | |
19.15.2 | S2-2500193 | CR | Approval | 23.273 CR0639 (Rel-19, 'B'): KI#1 Addressing the leftovers in the WI Exception on whether and how LMF can take NG-RAN load into account when performing data collection | Sony | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 General | - | - | Docs:=3 | - | |
19.15.2 | S2-2500086 | CR | Approval | 23.288 CR1305 (Rel-19, 'B'): Clarification of Nnwdaf_MLModelProvision service | ZTE | Rel-19 | |||
19.15.2 | S2-2500087 | CR | Approval | 23.288 CR1306 (Rel-19, 'B'): Adding new service consumer for ML Model monitoring in AIML based positioning | ZTE | Rel-19 | |||
19.15.2 | S2-2500592 | CR | Approval | 23.288 CR1348 (Rel-19, 'F'): Updates of ML model provisioning services for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 Performance monitoring | - | - | Docs:=2 | - | |
19.15.2 | S2-2500593 | CR | Approval | 23.288 CR1349 (Rel-19, 'F'): Update of AI/ML model performance monitoring for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | S2-2500835 | CR | Approval | 23.288 CR1365 (Rel-19, 'F'): Clarification on model performance monitoring for LMF-based AI/ML Positioning | CATT | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 | - | - | Docs:=3 | - | |
19.15.2 | S2-2500109 | CR | Approval | 23.501 CR5665R2 (Rel-19, 'B'): KI#1: New LMF Data Exposure service | Nokia | Rel-19 | Revision of S2-2411362 | ||
19.15.2 | S2-2500110 | CR | Approval | 23.501 CR5507R3 (Rel-19, 'B'): KI#1: Extending NWDAF description to cover model provisioning to LMF | Nokia | Rel-19 | Revision of S2-2411364 | ||
19.15.2 | S2-2500589 | CR | Approval | 23.501 CR5979 (Rel-19, 'B'): Enhancements of MTLF discovery and selection for LMF-based AIML Positioning | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=2 | - | |
19.15.2 | S2-2500111 | CR | Approval | 23.502 CR5126R1 (Rel-19, 'B'): KI#1 AMF exposing RAN overload to LMF | Nokia | Rel-19 | Revision of S2-2411365 | ||
19.15.2 | S2-2500590 | CR | Approval | 23.502 CR5257 (Rel-19, 'B'): Enhancements of MTLF discovery and selection for LMF-based AIML Positioning | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | KI#2: Vertical Federated Learning | - | - | Docs:=0 | - | |
19.15.2 | - | - | - | TS 23.288 Definitions | - | - | Docs:=1 | - | |
19.15.2 | S2-2500146 | CR | Approval | 23.288 CR1173R3 (Rel-19, 'B'): KI#2: VFL definitions | Nokia | Rel-19 | Revision of S2-2411376 | ||
19.15.2 | - | - | - | TS 23.288 Registration and Discovery | - | - | Docs:=2 | - | |
19.15.2 | S2-2500141 | CR | Approval | 23.288 CR1316 (Rel-19, 'B'): KI#2: Updates to VFL discovery procedures e.g to address trusted AF | Nokia | Rel-19 | |||
19.15.2 | S2-2500674 | CR | Approval | 23.288 CR1359 (Rel-19, 'B'): Update the Registration and Discovery procedures for VFL | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 VFL Preparation | - | - | Docs:=4 | - | |
19.15.2 | S2-2500142 | CR | Approval | 23.288 CR1317 (Rel-19, 'B'): KI#2: Updates to VFL preparation procedures e.g to address trusted AF | Nokia | Rel-19 | Revised to S2-2501016 | Revised | |
19.15.2 | S2-2501016 | CR | Approval | 23.288 CR1317R1 (Rel-19, 'B'): KI#2: Updates to VFL preparation procedures e.g to address trusted AF | Nokia | Rel-19 | Revision of S2-2500142 | ||
19.15.2 | S2-2500202 | CR | Approval | 23.288 CR1325 (Rel-19, 'B'): NEF work during VFL preparation procedure | Vivo | Rel-19 | |||
19.15.2 | S2-2500673 | CR | Approval | 23.288 CR1358 (Rel-19, 'B'): Update the preparation procedure for VFL | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 VFL Training | - | - | Docs:=3 | - | |
19.15.2 | S2-2500085 | CR | Approval | 23.288 CR1304 (Rel-19, 'B'): Clarifications on intermediate training result and intermediate model training information | ZTE | Rel-19 | |||
19.15.2 | S2-2500139 | CR | Approval | 23.288 CR1314 (Rel-19, 'B'): KI#2: Updates to VFL training procedures e.g to address trusted AF | Nokia | Rel-19 | |||
19.15.2 | S2-2500675 | CR | Approval | 23.288 CR1360 (Rel-19, 'B'): Updates to VFL Training Procedure | Huawei, HiSilicon | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 Accuracy monitoring | - | - | Docs:=1 | - | |
19.15.2 | S2-2500656 | DISCUSSION | Discussion | Discussion for the accuracy monitoring of VFL training | vivo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 VFL Inference | - | - | Docs:=1 | - | |
19.15.2 | S2-2500084 | CR | Approval | 23.288 CR1303 (Rel-19, 'B'): Clarifications on VFL inference | ZTE | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 Service Operations | - | - | Docs:=3 | - | |
19.15.2 | S2-2500143 | DISCUSSION | Discussion | KI#2: New Services for VFL. | Nokia | Rel-19 | Revision of S2-2411373 | ||
19.15.2 | S2-2500657 | CR | Approval | 23.288 CR1356 (Rel-19, 'B'): Adding VFL related service operations | Vivo | Rel-19 | |||
19.15.2 | S2-2500658 | CR | Approval | 23.288 CR1357 (Rel-19, 'B'): Update on the contents of VFL related services | Vivo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.288 General Description | - | - | Docs:=1 | - | |
19.15.2 | S2-2501072 | CR | Approval | 23.288 CR1372 (Rel-19, 'B'): KI#2 update to VFL High Level Description | InterDigital | Rel-19 | Missing CR Number - CR states -! | ||
19.15.2 | - | - | - | TS 23.288 Other | - | - | Docs:=3 | - | |
19.15.2 | S2-2500150 | CR | Approval | 23.288 CR1318 (Rel-19, 'F'): KI#2: Model training service is not applicable for VFL | Nokia | Rel-19 | |||
19.15.2 | S2-2500201 | CR | Approval | 23.288 CR1324 (Rel-19, 'B'): Interaction between consumer and VFL server | Vivo | Rel-19 | |||
19.15.2 | S2-2500233 | DISCUSSION | Discussion | Discussion on VFL model training and inference with client intermediate results sharing between VFL clients . | Samsung | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=3 | - | |
19.15.2 | S2-2500148 | CR | Approval | 23.501 CR5892 (Rel-19, 'B'): VFL support for the discovery of NWDAF, NEF, and AF instances | Nokia | Rel-19 | |||
19.15.2 | S2-2500632 | CR | Approval | 23.501 CR5985 (Rel-19, 'B'): Support on registration and discovery of VFL server and client | China Telecom | Rel-19 | |||
19.15.2 | S2-2500659 | CR | Approval | 23.501 CR5986 (Rel-19, 'B'): Update for VFL related NF discovery | Vivo | Rel-19 | |||
19.15.2 | - | - | - | TS 23.501 discovery and selection parameters | - | - | Docs:=1 | - | |
19.15.2 | S2-2500144 | CR | Approval | 23.501 CR5676R2 (Rel-19, 'B'): KI#2: VFL services | Nokia | Rel-19 | Revision of S2-2411375 | ||
19.15.2 | - | - | - | TS 23.501 General description | - | - | Docs:=1 | - | |
19.15.2 | S2-2500147 | CR | Approval | 23.501 CR5598R3 (Rel-19, 'B'): KI#2 NEF extensions for VFL | Nokia | Rel-19 | Revision of S2-2411378 | ||
19.15.2 | - | - | - | TS 23.502 | - | - | Docs:=1 | - | |
19.15.2 | S2-2500149 | CR | Approval | 23.502 CR5199 (Rel-19, 'B'): VFL support for the discovery of NWDAF, NEF, and AF instances | Nokia | Rel-19 | |||
19.15.2 | - | - | - | KI#3: PCC related enhancements | - | - | Docs:=9 | - | |
19.15.2 | S2-2500151 | CR | Approval | 23.288 CR1319 (Rel-19, 'B'): QoS and policy assistance analytics update and EN resolution | Nokia | Rel-19 | |||
19.15.2 | S2-2500348 | CR | Approval | 23.288 CR1131R3 (Rel-19, 'B'): Enhancements to Analytics IDs to support QoS and policy | Samsung, vivo, OPPO, SK Telecom, InterDigital Inc | Rel-19 | Revision of S2-2411620 | ||
19.15.2 | S2-2500603 | CR | Approval | 23.288 CR1350 (Rel-19, 'B'): KI#3: EN resolution for QoS and Policy Assistance analytics | ETRI | Rel-19 | |||
19.15.2 | S2-2500604 | CR | Approval | 23.288 CR1351 (Rel-19, 'F'): KI#3: Clarification on QoS and policy assistance analytics | ETRI | Rel-19 | |||
19.15.2 | S2-2500836 | CR | Approval | 23.288 CR1366 (Rel-19, 'F'): Corrections on QoS and Policy Assistance Analytics | CATT | Rel-19 | |||
19.15.2 | S2-2500152 | CR | Approval | 23.503 CR1427R1 (Rel-19, 'B'): Support of QoS and policy assistance analytics | Nokia | Rel-19 | Revision of S2-2411386 | ||
19.15.2 | S2-2500672 | CR | Approval | 23.503 CR1340R2 (Rel-19, 'F'): Update on Policy decisions based on network analytics | Huawei, HiSilicon | Rel-19 | Revision of S2-2409791 | ||
19.15.2 | S2-2500839 | CR | Approval | 23.503 CR1311R3 (Rel-19, 'F'): Policy decisions based on QoS policy assistance information analytics | CATT | Rel-19 | Revision of S2-2411513. Confirm Spec version used - CR states {19.1.0}! | ||
19.15.2 | S2-2500837 | CR | Approval | 23.502 CR5291 (Rel-19, 'F'): Event exposure for QoS and Policy Assistance Analytics | CATT | Rel-19 | |||
19.15.2 | - | - | - | KI#4: Signalling storm mitigation | - | - | Docs:=2 | - | |
19.15.2 | S2-2500096 | CR | Approval | 23.288 CR1312 (Rel-19, 'B'): Adding data collection source | ZTE | Rel-19 | |||
19.15.2 | S2-2500101 | CR | Approval | 23.501 CR5885 (Rel-19, 'F'): Correction on usage of signalling storm analytics for reliability of NF services | Huawei, HiSilicon | Rel-19 | |||
19.16 | - | - | - | Indirect Network Sharing (TEI19_NetShare) | - | - | Docs:=11 | - | |
19.16 | S2-2500342 | CR | Approval | 23.501 CR5925 (Rel-19, 'F'): Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment | China Unicom, Ericsson | Rel-19 | |||
19.16 | S2-2500343 | CR | Approval | 23.501 CR5926 (Rel-19, 'F'): Clarification on network slice in the case of Indirect Network Sharing | China Unicom, Huawei, ZTE | Rel-19 | |||
19.16 | S2-2500614 | CR | Approval | 23.501 CR5982 (Rel-19, 'F'): Clarification of the UE registration in the INS case | Huawei, HiSilicon | Rel-19 | |||
19.16 | S2-2500670 | CR | Approval | 23.503 CR1337R2 (Rel-19, 'F'): Correction on UE Policy from VPLMN in INS | Huawei, HiSilicon, ZTE | Rel-19 | Revision of S2-2408959 | ||
19.16 | S2-2500671 | CR | Approval | 23.502 CR5268 (Rel-19, 'F'): Update UE context for INS | Huawei, HiSilicon, China Unicom | Rel-19 | |||
19.16 | S2-2500876 | CR | Approval | 23.501 CR6023 (Rel-19, 'F'): Clarification on non 3GPP access registration when the UE is registered for 3GPP access via indirect network sharing | ZTE | Rel-19 | |||
19.16 | S2-2500916 | DISCUSSION | Agreement | Discussion handling of 3GPP and non-3GPP access registration in INS | NEC Corporation | Rel-19 | |||
19.16 | S2-2500920 | CR | Approval | 23.501 CR6038 (Rel-19, 'F'): Handling of 3GPP and non-3GPP access registration in INS-option 1 | NEC | Rel-19 | |||
19.16 | S2-2500922 | CR | Approval | 23.501 CR6039 (Rel-19, 'F'): Handling of 3GPP and non-3GPP access registration in INS-option 2 | NEC | Rel-19 | |||
19.16 | S2-2500923 | CR | Approval | 23.501 CR6040 (Rel-19, 'F'): GUAMI allocation for indirect network sharing | NEC, Nokia | Rel-19 | |||
19.16 | S2-2500991 | CR | Approval | 23.501 CR6044 (Rel-19, 'F'): Indirect Network Sharing and Non 3GPP access | Nokia | Rel-19 | |||
19.17 | - | - | - | Architecture support of roaming value-added services (TEI19_RVAS) | - | - | Docs:=0 | - | |
19.18 | - | - | - | Minimize the Number of Policy Associations (TEI19_MINPA) | - | - | Docs:=0 | - | |
19.19 | - | - | - | Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports (TEI19_DLPM) | - | - | Docs:=0 | - | |
19.20 | - | - | - | Providing per-subscriber VLAN instructions from UDM (TEI19_VLANSUB) | - | - | Docs:=0 | - | |
19.21 | - | - | - | Enhancing Parameter Provisioning with static UE IP address and UP security policy (TEI19_IP-SP-EXP) | - | - | Docs:=2 | - | |
19.21 | S2-2500395 | CR | Approval | 23.501 CR5939 (Rel-19, 'F'): Clarification on UPSec Policy provisioning | China Telecom, Ericsson | Rel-19 | |||
19.21 | S2-2500775 | CR | Approval | 23.502 CR5284 (Rel-19, 'F'): Avoding potential Static IP assignment | Samsung | Rel-19 | |||
19.22 | - | - | - | Spending Limits for UE Policies in Roaming scenario (TEI19_SLUPiR) | - | - | Docs:=0 | - | |
19.23 | - | - | - | Subscription control for reference time distribution in EPS (TEI19_TIME_SUB_EPS) | - | - | Docs:=0 | - | |
19.24 | - | - | - | On-demand broadcast of GNSS assistance data (TEI19_OBGAD) | - | - | Docs:=0 | - | |
19.25 | - | - | - | QoS monitoring (TEI19_QME) | - | - | Docs:=12 | - | |
19.25 | S2-2500995 | LS OUT | Approval | [DRAFT] LS on Clarification of the scope of QME | Nokia | Rel-19 | Response to S2-2500036 | ||
19.25 | S2-2500037 | LS In | Action | LS from CT WG3: LS on Clarification of the scope of QME | CT WG3 (C3-246506) | Rel-19 | Responses drafted in S2-2500265, S2-2500304, S2-2500801, S2-2500862 | ||
19.25 | S2-2500265 | LS OUT | Approval | [DRAFT] LS reply on clarification of the scope of QME | China Telecom Corporation Ltd. | Rel-19 | Response to S2-2500037 | ||
19.25 | S2-2500304 | LS OUT | Approval | [DRAFT] Reply LS on CT WG3 LS to SA WG2 on QME | China Mobile Com. Corporation | Response to S2-2500037 | |||
19.25 | S2-2500801 | LS OUT | Approval | [DRAFT] Reply LS on Clarification of the scope of QME | ZTE | Rel-19 | Response to S2-2500037 | ||
19.25 | S2-2500862 | LS OUT | Approval | [DRAFT] LS Reply to C3-246506 on clarification of the scope of QME | Huawei, HiSilicon | Rel-19 | Response to S2-2500037 | ||
19.25 | S2-2500040 | LS In | Action | LS from CT WG4: Reply LS on RAN support of QoS monitoring capability | CT WG4 (C4-245437) | Rel-19 | |||
19.25 | S2-2500264 | CR | Approval | 23.501 CR5911 (Rel-19, 'C'): Clarifications of QoS monitoring capability configuration and transfer within 5GC | China Telecom | Rel-19 | Confirm CR Revision - CR states 1! | ||
19.25 | S2-2500305 | CR | Approval | 23.501 CR5919 (Rel-19, 'F'): QME clarification on Reply LS on CT WG3 LS to SA WG2 | China Mobile | Rel-19 | WI Code seems to be AIML_CN, not TEI19_QME! | ||
19.25 | S2-2500800 | DISCUSSION | Discussion | Discussion on the QME capability issue from CT WG3. | ZTE | Rel-19 | |||
19.25 | S2-2500802 | CR | Approval | 23.501 CR6004 (Rel-19, 'F'): Clarification on the Qos monitoring capability | ZTE | Rel-19 | |||
19.25 | S2-2500863 | CR | Approval | 23.501 CR6017 (Rel-19, 'F'): Clarification of the scope of QME | Huawei, HiSilicon | Rel-19 | |||
19.26 | - | - | - | NF discovery and selection by target PLMN (TEI19_NFsel_by_tPLMN) | - | - | Docs:=2 | - | |
19.26 | S2-2500182 | CR | Approval | 23.502 CR5207 (Rel-19, 'F'): Corrections for SMF selection by target PLMN | Nokia | Rel-19 | |||
19.26 | S2-2500279 | CR | Approval | 23.502 CR5230 (Rel-19, 'F'): Correction on delegated NF service discovery flow | China Mobile | Rel-19 | WI Code should be TEI19_NFsel_by_tPLMN! | ||
19.27 | - | - | - | Roaming traffic offloading via session breakout in HPLMN (TEI19_HSBO) | - | - | Docs:=2 | - | |
19.27 | S2-2500341 | CR | Approval | 23.501 CR5924 (Rel-19, 'F'): Clarification on DNS server information provisioning and editorial updates | Samsung | Rel-19 | |||
19.27 | S2-2500990 | CR | Approval | 23.501 CR6043 (Rel-19, 'F'): Correction to when and how the UPF can provide the SMF with DNS server information | Nokia | Rel-19 | |||
19.28 | - | - | - | Multiple Location Procedure for Emergency LCS Routing (TEI19_MLR4RTR) | - | - | Docs:=1 | - | |
19.28 | S2-2500976 | CR | Approval | 23.273 CR0665 (Rel-19, 'F'): LCS Client alignment to Routing Entities using HELD in Emergency LCS | Nokia, Nokia Shanghai Bell | Rel-19 | |||
19.29 | - | - | - | Support for ProSe services in NPNs (TEI19_ProSe_NPN) | - | - | Docs:=0 | - | |
19.30 | - | - | - | MSISDN verification operation support to Nnef_UEId Service (TEI19_MVOSNS) | - | - | Docs:=1 | - | |
19.30 | S2-2500865 | CR | Approval | 23.502 CR5294 (Rel-19, 'D'): Editorial correction | AT&T | Rel-19 | |||
19.31 | - | - | - | ATSSS Rule Provisioning via 3GPP access connected to EPC (TEI19_ARP3E) | - | - | Docs:=0 | - | |
19.32 | - | - | - | Network Controlled Network Slice Selection (TEI19_ SliceSel) | - | - | Docs:=12 | - | |
19.32 | S2-2500211 | CR | Approval | 23.501 CR5901 (Rel-19, 'F'): Update to Support of Slice change based on AF request | Ericsson | Rel-19 | |||
19.32 | S2-2500212 | CR | Approval | 23.502 CR5210 (Rel-19, 'F'): Update to 23.502 AF requested network slicing replacement | Ericsson | Rel-19 | |||
19.32 | S2-2500213 | CR | Approval | 23.503 CR1459 (Rel-19, 'F'): Update to 23.503 Support of network slice replacement based on AF request | Ericsson | Rel-19 | |||
19.32 | S2-2500457 | CR | Approval | 23.501 CR5957 (Rel-19, 'F'): Network controlled slice replacement cleanup | NEC | Rel-19 | |||
19.32 | S2-2500535 | CR | Approval | 23.501 CR5972 (Rel-19, 'F'): Resolving remaining editor's notes | LG Electronics | Rel-19 | |||
19.32 | S2-2500536 | CR | Approval | 23.503 CR1479 (Rel-19, 'F'): Clarification on event notification on outcome of AF requested Network Slice Replacement | LG Electronics | Rel-19 | |||
19.32 | S2-2500870 | CR | Approval | 23.501 CR6020 (Rel-19, 'F'): Resolvement of EN in AF Requested modification of the Set of Network Slice(s) for a UE | ZTE, Nokia | Rel-19 | |||
19.32 | S2-2500871 | CR | Approval | 23.502 CR5295 (Rel-19, 'F'): Clarification on the AF requested network slice replacement | ZTE | Rel-19 | |||
19.32 | S2-2500872 | CR | Approval | 23.503 CR1494 (Rel-19, 'F'): PCRT for outcome of network slice replacement triggered by AF | ZTE | Rel-19 | |||
19.32 | S2-2500952 | CR | Approval | 23.501 CR6041 (Rel-19, 'F'): Addressing EN for AF requested slice selection | Samsung | Rel-19 | WI Code should be TEI19_SliceSel! | ||
19.32 | S2-2500953 | CR | Approval | 23.502 CR5305 (Rel-19, 'F'): Clarification for AF requested slice selection | Samsung | Rel-19 | WI Code should be TEI19_SliceSel! | ||
19.32 | S2-2500983 | CR | Approval | 23.503 CR1501 (Rel-19, 'F'): Network controlled slice replacement cleanup | NEC | Rel-19 | |||
19.33 | - | - | - | PRU Usage Extension supported by Core Network (TEI19_PRUE) | - | - | Docs:=0 | - | |
19.49 | - | - | - | Generic Rel-19 LSs | - | - | Docs:=29 | - | |
19.49 | - | - | - | VMR_Ph2 related - MWAB mobility | - | - | Docs:=12 | - | |
19.49 | S2-2500053 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | RAN WG3 (R3-247910) | Rel-19 | Responses drafted in S2-2500221, S2-2500366, S2-2500514, S2-2500580 | ||
19.49 | S2-2500222 | DISCUSSION | Discussion | Discussion on Incoming LS S2-2500053/R3-247910 on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility). | Nokia | Rel-19 | |||
19.49 | S2-2500367 | DISCUSSION | Agreement | MWAB mobility analysis . | Ericsson | Rel-19 | |||
19.49 | S2-2500579 | DISCUSSION | Discussion | Discussion on AMF re-allocation with a single logical WAB-gNB | Huawei, HiSilicon | Rel-19 | |||
19.49 | S2-2500220 | CR | Approval | 23.501 CR5902 (Rel-19, 'F'): On MWAB mobility | Nokia | Rel-19 | |||
19.49 | S2-2500368 | CR | Approval | 23.501 CR5934 (Rel-19, 'F'): MWAB Mobility handling clarification | Ericsson | Rel-19 | |||
19.49 | S2-2500515 | CR | Approval | 23.501 CR5967 (Rel-19, 'F'): Sove the editor s note related to mobility support | CATT | Rel-19 | |||
19.49 | S2-2500516 | CR | Approval | 23.502 CR5250 (Rel-19, 'F'): Add use case related to MWAB for intra-NG-RAN handover to be performed by the Inter NG-RAN node N2 based handover procedure | CATT | Rel-19 | |||
19.49 | S2-2500221 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | Nokia | Rel-19 | Response to S2-2500053 | ||
19.49 | S2-2500366 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 Solution impacts on RAN (MWAB mobility) | Ericsson | Rel-19 | Response to S2-2500053 | ||
19.49 | S2-2500514 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | CATT | Rel-19 | Response to S2-2500053 | ||
19.49 | S2-2500580 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Mobility) | Huawei, HiSilicon | Rel-19 | Response to S2-2500053 | ||
19.49 | - | - | - | VMR_Ph2 related - Additional ULI & multi-hop prevention | - | - | Docs:=8 | - | |
19.49 | S2-2500052 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) | RAN WG3 (R3-247909) | Rel-19 | Responses drafted in S2-2500363, S2-2500582 | ||
19.49 | S2-2500364 | DISCUSSION | Agreement | Analysis on MWAB Access control and Additional ULI. | Ericsson | Rel-19 | |||
19.49 | S2-2500581 | DISCUSSION | Discussion | Discussion on Additional ULI | Huawei, HiSilicon | Rel-19 | |||
19.49 | S2-2500365 | CR | Approval | 23.501 CR5933 (Rel-19, 'F'): MWAB configuration and Additional ULI Clarification | Ericsson | Rel-19 | |||
19.49 | S2-2500517 | CR | Approval | 23.501 CR5968 (Rel-19, 'F'): Solve the Editor s Note related to the Additional ULI | CATT | Rel-19 | |||
19.49 | S2-2500755 | CR | Approval | 23.501 CR5998 (Rel-19, 'B'): MWAB-UE Mobility Restriction | Samsung | Rel-19 | |||
19.49 | S2-2500363 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 Solution impacts on RAN (Access Control and Additional ULI) | Ericsson | Rel-19 | Response to S2-2500052 | ||
19.49 | S2-2500582 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | Huawei, HiSilicon | Rel-19 | Response to S2-2500052 | ||
19.49 | - | - | - | Other topics | - | - | Docs:=3 | - | |
19.49 | S2-2500032 | LS In | Action | LS from CT WG1: LS on priority IMS registration | CT WG1 (C1-246939) | Rel-19 | Response drafted in S2-2500186 | ||
19.49 | S2-2500186 | LS OUT | Approval | [DRAFT] LS Reply on priority IMS registration | Peraton Labs | Rel-19 | Response to S2-2500032 | ||
19.49 | S2-2500185 | CR | Approval | 23.228 CR1535 (Rel-19, 'F'): Priority IMS Registration | Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon | Rel-19 | |||
19.49 | - | - | - | LS on Time Synchronization for MBS | - | - | Docs:=5 | - | |
19.49 | S2-2500066 | LS In | Action | LS from SA WG4: LS on Time Synchronization for MBS | SA WG4 (S4-242169) | Rel-19 | Responses drafted in S2-2500135, S2-2500252, S2-2500576, S2-2500799 | ||
19.49 | S2-2500135 | LS OUT | Approval | [DRAFT] Reply LS on Time Synchronization for MBS | Qualcomm | Rel-19 | Response to S2-2500066 | ||
19.49 | S2-2500252 | LS OUT | Approval | [DRAFT] Reply LS on Time Synchronization for MBS | Ericsson | Rel-19 | Response to S2-2500066 | ||
19.49 | S2-2500576 | LS OUT | Approval | [DRAFT] Response on Time synchronisation for MBS | Huawei, HiSilicon | Rel-19 | Response to S2-2500066 | ||
19.49 | S2-2500799 | LS OUT | Approval | [DRAFT] Reply LS from SA WG4: LS on Time Synchronization for MBS | ZTE | Response to S2-2500066 | |||
19.49 | - | - | - | LS for information | - | - | Docs:=1 | - | |
19.49 | S2-2500031 | LS In | Information | LS from CT WG1: Reply LS on FS_IMS_RES outcome and future work plan | CT WG1 (C1-246921) | Rel-19 | |||
19.50 | - | - | - | Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=23 | - | |
19.50 | S2-2500981 | CR | Approval | 23.247 CR0372R4 (Rel-19, 'B'): MBS broadcast support for NTN | Nokia, Qualcomm | Rel-19 | Revision of S2-2500154. Confirm CR Revision - CR states 3! | ||
19.50 | - | - | - | LS on supporting MBS broadcast service for NR NTN | - | - | Docs:=2 | - | |
19.50 | S2-2500046 | LS In | Action | LS from RAN WG2: Reply LS on supporting MBS broadcast service for NR NTN | RAN WG2 (R2-2411196) | Rel-19 | Response drafted in S2-2500578 | ||
19.50 | S2-2500578 | LS OUT | Approval | [DRAFT] Reply on LS on Supporting MBS broadcast service for NR NTN | Huawei, HiSilicon | Rel-19 | Response to S2-2500046 | ||
19.50 | - | - | - | LS on emergency services and eDRX | - | - | Docs:=6 | - | |
19.50 | S2-2500044 | LS In | Action | LS from RAN WG2: LS on emergency services and eDRX | RAN WG2 (R2-2411041) | Rel-17 | Responses drafted in S2-2500362, S2-2500698, S2-2501001 | ||
19.50 | S2-2500362 | LS OUT | Approval | [DRAFT] Reply LS on emergency services and eDRX | Ericsson | Rel-17 | Response to S2-2500044 | ||
19.50 | S2-2500698 | LS OUT | Approval | [DRAFT] LS Reply on emergency services and eDRX | Huawei, HiSilicon | Rel-17 | Response to S2-2500044 | ||
19.50 | S2-2501001 | LS OUT | Approval | [DRAFT] LS reply on emergency services and eDRX | Nokia | Rel-17 | Response to S2-2500044 | ||
19.50 | S2-2500133 | DISCUSSION | Approval | Emergency call back and delayed paging. | Qualcomm Incorporated | Rel-19 | |||
19.50 | S2-2500134 | LS OUT | Approval | [DRAFT] LS on emergency call back and paging | Qualcomm | Rel-19 | |||
19.50 | - | - | - | LS on Supporting MBS broadcast service for NR NTN | - | - | Docs:=4 | - | |
19.50 | S2-2500016 | LS In | Action | LS from RAN WG3: LS on Supporting MBS broadcast service for NR NTN | RAN WG3 (R3-245844) | Rel-19 | Responses drafted in S2-2500155, S2-2500504 | ||
19.50 | S2-2500155 | LS OUT | Approval | [DRAFT] Reply LS on Supporting MBS broadcast service for NR NTN | Nokia | Rel-19 | Revision of S2-2411327. Response to S2-2500016 | ||
19.50 | S2-2500504 | LS OUT | Approval | [DRAFT] Reply LS on Supporting MBS broadcast service for NR NTN | Xiaomi | Rel-19 | Response to S2-2500016 | ||
19.50 | S2-2500577 | CR | Approval | 23.247 CR0372R3 (Rel-19, 'B'): MBS broadcast support for NTN | [Nokia?] Huawei, HiSilicon [, Qualcomm? Ericsson? Xiaomi?] | Rel-19 | Revision of S2-2412570. Confirm Sources! WI Code should be NR_NTN_Ph3-Core! | ||
19.50 | - | - | - | LS for information | - | - | Docs:=10 | - | |
19.50 | S2-2500058 | LS In | Information | LS from SA WG1: Reply LS on PWS support for NB-IoT NTN | SA WG1 (S2-244757) | Rel-19 | |||
19.50 | S2-2500070 | LS In | Information | LS from SA WG5: LS reply on OAM requirements to support regenerative payload | SA WG5 (S5-247311) | Rel-19 | |||
19.50 | S2-2500013 | LS In | Information | LS from RAN WG2: LS on PWS support for NB-IoT NTN | RAN WG2 (R2-2409243) | Rel-19 | |||
19.50 | S2-2500154 | CR | Approval | 23.247 CR0372R2 (Rel-19, 'B'): MBS broadcast support for NTN | Nokia | Rel-19 | Revision of S2-2412570. Revised to S2-2500981 | Revised | |
19.50 | S2-2500695 | CR | Approval | 23.501 CR5989 (Rel-17, 'F'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-17 | WI Code should be ARCH_NR_REDCAP! | ||
19.50 | S2-2500696 | CR | Approval | 23.501 CR5990 (Rel-18, 'A'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-18 | WI Code should be ARCH_NR_REDCAP! | ||
19.50 | S2-2500697 | CR | Approval | 23.501 CR5991 (Rel-19, 'A'): EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon | Rel-19 | WI Code should be ARCH_NR_REDCAP! | ||
19.50 | S2-2500997 | CR | Approval | 23.501 CR6047 (Rel-17, 'C'): EDRX for emergency PDU Sessions | Nokia | Rel-17 | |||
19.50 | S2-2500998 | CR | Approval | 23.501 CR6048 (Rel-18, 'A'): EDRX for emergency PDU Sessions | Nokia | Rel-18 | |||
19.50 | S2-2501000 | CR | Approval | 23.501 CR6049 (Rel-19, 'A'): EDRX for emergency PDU Sessions | Nokia | Rel-19 | |||
30 | - | - | - | Project Planning and Management | - | - | Docs:=0 | - | |
30.1 | - | - | - | New and Revised Study/Work Items | - | - | Docs:=3 | - | |
30.1 | S2-2500543 | SID NEW | Information | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | KPN N.V. | Rel-20 | |||
30.1 | S2-2500787 | WID REVISED | Approval | Revised WID on Energy Efficiency and Energy Saving. | Samsung, Lenovo (Rapporteurs) | Rel-19 | |||
30.1 | S2-2500934 | WID NEW | Information | New WID on Architecture support of Ambient power-enabled Internet of Things. | Huawei, HiSilicon | Rel-19 | |||
30.2 | - | - | - | Submissions for TEI20 | - | - | Docs:=0 | - | |
30.3 | - | - | - | TR and TS Cover sheets | - | - | Docs:=1 | - | |
30.3 | S2-2500376 | TS OR TR COVER | Approval | Cover sheet for presentation of TR 23.700-13 to TSG SA for Approval | OPPO | Rel-19 | |||
30.4 | - | - | - | WID Status Reports | - | - | Docs:=0 | - | |
30.5 | - | - | - | Review of the Work Plan | - | - | Docs:=3 | - | |
30.5 | S2-2500080 | OTHER | Action | Structure of WID Names & Acronyms | MCC Work Plan Manager | Rel-19 | |||
30.5 | S2-2500984 | WORK PLAN | Endorsement | SA WG2#166 AHE Work Planning slides | SA WG2 Chair | ||||
30.5 | S2-2500986 | WORK PLAN | Endorsement | SA WG2#166AHE Work Planning spreadsheet | SA WG2 Chair | ||||
30.6 | - | - | - | Planning future meetings | - | - | Docs:=2 | - | |
30.6 | S2-2500989 | OTHER | Information | SA Plenary outcomes and guidance to SA WG2 | SA WG2 Chair | ||||
30.6 | S2-2500996 | OTHER | Information | Rel-20 5GA NWM discussion guidance and plan | SA WG2 Chair | ||||
30.7 | - | - | - | 5GA SIDs/WIDs for Rel-20 | - | - | Docs:=0 | - | |
30.8 | - | - | - | 6G SID(s) for Rel-20 | - | - | Docs:=0 | - | |
30.9 | - | - | - | Exception sheets | - | - | Docs:=0 | - | |
31 | - | - | - | Close of meeting | - | - | Docs:=0 | - | |
99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=32 | - | |
99 | S2-2500924 | LS OUT | Approval | [DRAFT] Reply LS on UUAA Unsubscribe procedure | Samsung | Rel-17 | Response to S2-2500039. WITHDRAWN | Withdrawn | |
99 | S2-2500822 | CR | Approval | 23.502 CR5290 (Rel-19, 'B'): Update NEF services to align with IMS AS services | Huawei, HiSilicon | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500826 | CR | Approval | 23.228 CR1571 (Rel-19, 'B'): Correction on IMS data channel interworking | Huawei, HiSilicon | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500187 | CR | Approval | 23.288 CR1320 (Rel-19, 'C'): Enabling OSE data Analytics analyse user plane latency | Verizon Switzerland AG | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500400 | CR | Approval | 23.288 CR1339 (Rel-19, 'F'): KI#1 Procedures to collect data from the UE and from NG-RAN, resolution of Editor s Note | Ericsson | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500993 | CR | Approval | 23.501 CR6045 (Rel-18, 'F'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-18 | WITHDRAWN | Withdrawn | |
99 | S2-2500994 | CR | Approval | 23.501 CR6046 (Rel-19, 'A'): Avoiding duplication of SMF notifications for SMF&UPF event reporting targeting Any UE | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2501029 | CR | Approval | 23.502 CR5317 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | WITHDRAWN | Withdrawn | ||
99 | S2-2501032 | CR | Approval | 23.502 CR5318 (Rel-19, 'F'): Updating device identifier information in PDU session modification request | Rel-19 | WITHDRAWN | Withdrawn | ||
99 | S2-2501051 | CR | Approval | 23.502 CR5325 (Rel-19, 'F'): Clarification for PCF behaviour for generating matchall PCC rules for MA PDU Session | Samsung | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500564 | CR | Approval | 23.503 CR1483 (Rel-19, 'D'): Editorial changes on provisioning PCC rule for ATSSS | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500550 | CR | Approval | 23.501 CR5974 (Rel-19, 'F'): Update of UE ATSSS capability | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500560 | CR | Approval | 23.501 CR5977 (Rel-19, 'D'): Clarification on steering functionalities description | ETRI | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500099 | CR | Approval | 23.501 CR5884 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | Nokia, NTT Docomo | Rel-18 | WITHDRAWN | Withdrawn | |
99 | S2-2500217 | CR | Approval | 23.503 CR1460 (Rel-18, 'F'): URSP Guidelines updates of GSMA | Nokia | Rel-18 | WITHDRAWN | Withdrawn | |
99 | S2-2500218 | CR | Approval | 23.503 CR1461 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500563 | CR | Approval | 23.503 CR1482 (Rel-19, 'A'): URSP Guidelines updates of GSMA | Nokia | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500444 | CR | Approval | 23.501 CR5953 (Rel-19, 'B'): Providing Multi-Modal Awareness to NG-RAN | InterDigital Pennsylvania | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500174 | CR | Approval | 23.501 CR5896 (Rel-19, 'F'): Definition of non-3GPP device connection information | Qualcomm Incorporated, InterDigital | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500473 | CR | Approval | 23.256 CR0166 (Rel-19, 'F'): Altitude reporting update | Datang Mobile Com. Equipment | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500331 | P-CR | Approval | 23.700-13: PCR to TS 23.xyz: Ambient IoT Services. | CATT | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500332 | P-CR | Approval | 23.700-13: PCR to TS 23.xyz: Assistance Information used by AIoT RAN. | CATT | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500701 | CR | Approval | 23.228 CR1521R5 (Rel-19, 'B'): 23228 Mobility procedure when satellite changes - continuation | NTT DOCOMO, [vivo] | Rel-19 | Revision of S2-2412672. WITHDRAWN | Withdrawn | |
99 | S2-2500702 | CR | Approval | 23.228 CR1522R5 (Rel-19, 'B'): 23228 Mobility procedure when satellite changes - ground fallback | NTT DOCOMO, [vivo] | Rel-19 | Revision of S2-2412673. WITHDRAWN | Withdrawn | |
99 | S2-2500749 | CR | Approval | 23.502 CR5278 (Rel-19, 'B'): MWAB-UE Mobility Restriction | Samsung | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500791 | CR | Approval | 23.503 CR1490 (Rel-19, 'F'): Clarification on EIF functionality | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500795 | CR | Approval | 23.501 CR6002 (Rel-19, 'F'): Support of NF selection based on energy information | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn | |
99 | S2-2500797 | CR | Approval | 23.501 CR6003 (Rel-19, 'F'): Support of UPF (re)-selection based on energy information | Samsung Electronics France SA | Rel-19 | WITHDRAWN | Withdrawn |